Code:
./kw1281test /dev/ttyUSB0 10400 17 ReadSoftwareVersion
It immediately throws an error trying to access the com port as it doesn't recognize 10400 as a valid baud rate.
Long story sort I got frustrated and just hooked the cable to my Win 10 laptop and now my windows go up and down with the fob. But if anyone wants to take up my linux struggle, feel free lol!
Taking up the mantle, although Greg did show how he has kw1281test working on raspi, and a proof of concept for android in between.
Late to the game here -- I only found out about this program a few months ago. And because I had to hunt through my collection of OBDII cables and buy one last one, to find one that had the FTDI chip instead of one of the anonymous others that would not work.
That aside, time to step up and contribute a little.
Many months ago, many pages ago (3...), Dhawk12 was trying to struggle with getting kw1281test to work on linux.
I noticed when Greg showcased using the program on a raspberry pi, presumably on either raspian or ubuntu for ARM, and showed it working well.
But the missing piece shown, but not shown how to get it: you use the
serial number of the FTDI cable instead of a COM port number, or the intuitive linux equivalent -- a /dev/ttyS0 or similar device path.
So, instead of
you use your cable's serial number
(My example is a similar length, but not an actual FTDI serial number
)
How do you find out what your serial number is on linux?
Here's how I found that out:
I used the console / command line, because... that's the universal method for linux. We're using a command line diagnostic tool, so why not more console based commands, anyway?
First I grabbed the drivers from FTDI, the D2xx drivers that Greg notes are needed for the program to communicate with VW instrument clusters.
Thankfully, FTDI made a great tutorial video showing how to install the drivers on linux (it's similar to their MacOS procedure)
Youtube: FTDI -- Linux d2xx Driver Installation Guide
If you didn't catch them displaying the serial number in installation and testing of the install to ensure the cable works:
The video linked up shows that part in around the 3-minute mark.
Code:
> cd /path/to/libftd2xx-x86_64-1.4.24/release/examples/
> make
(let make build the examples, and wait for the prompt to return)
> cd /path/to/libftd2xx-x86_64-1.4.24/release/examples/EEPROM/read/
> sudo ./read
Library version = 0x10424
Opening port 0
FT_Open succeeded. Handle is 0x5607e5ecdc40
FT_GetDeviceInfo succeeded. Device is type 5.
FT_EE_Read succeeded.
Signature1 = 0
Signature2 = -1
Version = 2
VendorId = 0x0403
ProductId = 0x6001
Manufacturer = FTDI
ManufacturerId = AB
Description = FT232R USB UART
SerialNumber = ACDCBLAH
MaxPower = 90
PnP = 1
SelfPowered = 0
RemoteWakeup = 1
232R:
-----
Here it is, in the output of the read example, in my case "
ACDCBLAH"
To run kw1281test, I just moved to the directory where I pulled down the source from Github, and ran:
Code:
> dotnet run ACDCACDC 10400 17 ReadSoftwareVersion
And now, you have access to Yesterday's Diagnostics... Today!
Finally:
Thank you to Greg for making an excellent piece of software, for free, no less.
Thank you to Mozambiquer for tipping me off about kw1281test, and this thread in the first place, a few months back in a Facecrack group discussion.
