Would your tool work with the OBDKey hardware? OBDKey supports the KW1281 protocol using AT commands. May be of interest?
Hi,
last days i've played around with VAG Diagnostic, and created some fuse interface.
features:
* read controler info
* read dataGroups
* read controler errorstorage
* reset controler errorstorage
* read (some) dataWords
It's not finished yet, but working with the 2000' audi tt cluster on my table
what you need:
* amd64 linux with fuse support (ask for x86 version, if you want to test it before source release)
* obd diagnostic cable which supports kw1281 and is supported by linux, most cheap cables comes with ftdi rs232 converter and work fine (search amazon.com for B007PACPYW, costs about 10$)
USE AT YOUR OWN RISK
it is possible to modify data by the kw1281 protocol, functions are not implented, but bugs can come to features... (i don't think so, but be warned)
installation, do this as root!
edit /etc/fstab and add some line like this:Code:# cd /tmp # wget http://www.royal-society.us/carosOBD.tgz # tar xzvf carosOBD.tgz # mv carosOBD/carosOBD /usr/bin # mkdir /usr/share/caros # mv carosOBD/obd_dtc* /usr/share/caros # mv carosOBD/caros.obd /etc # rmdir carosOBD
ttyUSB0 change this to your serial deviceCode:carosOBD#/dev/ttyUSB0 /tmp/obd fuse user,noauto,noatime 0 0
/tmp/obd change this to your prefered mount path (keep sure the directory exists)
now you can test it:
# mkdir /tmp/obd
# mount /tmp/obd
# cat /tmp/obd
should return:
Code:airbags brakes climatronic cluster comfort ecu synced_with_idnow you can test, try to get controler info with:
result:Code:# cat /tmp/obd/cluster/info
Code:part-id: 8N1919880E component: KOMBI+WEGFAHRS. M73 D30
read errorcodes from the controlers:
result:Code:# cat /tmp/obd/cluster/errors # cat /tmp/obd/ecu/errors
Code:(00771-030) Kraftstoffanzeige-sensor -G - Stromkreisunterbrechung/Kurzschluss gegen Plus (00779-030) Außenlufttemperaturgeber -G17 - Stromkreisunterbrechung/Kurzschluss gegen Plus (01128-035) Lesespule Wegfahrsperre - (01176-007) Schlüssel - Signal zu schwach. (01176-193) Schlüssel - Nicht befugt
remove errors from controler
result:Code:# echo true > /tmp/obd/cluster/errors_reset
Code:returns nothing if success returns something like "write error: Permission denied" if reset fails
or read dataGroups:
result:Code:# cat /tmp/obd/cluster/dataGroups/1 # cat /tmp/obd/cluster/dataGroups/2 .... # cat /tmp/obd/cluster/dataGroups/256
known dataWords for controllers will be added soonCode:0x07 0x64 0x00 0x01 0xc8 0x00 0x25 0x00 0x1e 0x2c 0x0c 0x0d
(you can for now read some cluster datawords)
should return something like this:Code:# cat /tmp/obd/cluster/dataWords/*
you have to read the related dataGroups first, this will be automated later, for cluster do this before you read the dataWords:Code:duty_cycleA: 4% duty_cycleB: 0% mileage: 53240km mileage_trip: 0km oilpressure: 0 resistor: 300ohm rpm: 0rpm speed: 0km/h tank: 0l temp_cooling: 0 temp_out: -99
Code:# cat /tmp/obd/cluster/dataGroups/1 && cat /tmp/obd/cluster/dataGroups/2
q&a
problem:
"error while loading shared libraries: libfuse.so.2"
solution:
try carosOBDx86-binary instead of carosOBD-binary
problem:
it hangs
solution:
kill it with:
# killall -9 carosOBD
problem:
controller xy isn't in the filesystem
solution:
edit caros.obd and add controller
adress id is decimal, so if cluster adress is 0x17, you have to add 23 to your configuration.
problem:
# carosOBD /dev/ttyUSB0 /tmp/obd
fuse: device not found, try 'modprobe fuse' first
solution:
as id says, try
# modprobe fuse
or/and check if fuse module is loaded
# lsmod | grep fuse
if it's not working you need a kernel with fuse support, if you know how to build your own, you can find fuse @file system support
suggestions for the tool are welcome
would be nice if someone can support me with language files of the error-/statuscodes
Last edited by BennY-; 04-19-2012 at 08:25 PM. Reason: update ;)
Would your tool work with the OBDKey hardware? OBDKey supports the KW1281 protocol using AT commands. May be of interest?
hi, i think they should work when at least firmware 1.40 is on the OBDKey device. But this is no guarantee
Their product homepage says that with firmware 1.40 they introduced the following (necessary) features:
Originally Posted by http://www.obdkey.com/firmwareupdate.asp
Bookmarks