Printable View
Has anyone used this to parse and echo data streams via Linux? https://github.com/dominickpastore/aldl_echo
Looks like this program was written specifically for a 1994 1/2 ton model with the L05 engine (5.7L V8 TBI, VIN=K) and 4L60E transmission but it doesn't look like it would be that difficult to add definitions for any other GM vehicle with 8192 baud data stream.
looks straightfoward, haven't used it but i'm sure it'd work fine.
writing datastream definitions for such tools is usually easy, you can save time by not even bothering adding stuff you don't care about.
one tricky thing is getting the kernel serial device into 8192 baud. this thing is python so it probably uses some python library that (hopefully) has that figured out.
i wrote another aldl thing for linux, https://github.com/resfilter/aldl
it's 'driverless' so instead of using linux's serial driver, it accesses your raw FTDI usb device and does all the heavy lifting itself, meaning it can not only set arbitrary baud rates but nail down perfect serial timing. lots of people have written definitions for other vehicles for it too (it's more for hacky linux-based dashboards, has an ncurses interface and logs to CSV full time)
alternatively you can run tunerpro in a windows virtual machine with a usb interface, done that a few times works just great if you want to
I actually tried that one first, I haven't been able to get the ftdi_sio driver to successfully rmmod or blacklist. Though this was from a raspi using a TTL-234X cable with wired ends connecting directly to the ALDL, I'll attempt again later today via laptop and see if I get better results.Quote:
Originally Posted by steveo
should work fine on a pi with that device. just need to get rid of the kernel's driver from 'taking over' the device somehow so we can use raw USB instead.
what os are you running on it? debian? have you tried simply running the debian-config.sh script that comes with it? (if not running it, read it to see what steps i went through to get it working)
another more insane alternative might be to move the ftdi_sio driver module right out of the module tree so it can't find it.
Debian Stretch, I have gone through and run the script. If on a GMT400 instead of LT1, does the LT1.conf need to be edited?Quote:
Originally Posted by steveo
yeah you totally rewrite the config file for a different engine
everything in the config examples should be gone through
the consoleif.conf needs to be updated with names of the stuff you want to display too unless you disable the consoleif it in aldl.conf
the config files are pretty hacky i wrote my own shoddy parser since i was bored, you need PARAMETER=value at the beginning of a line and everything else is ignored
i almost recommend you don't use this thing since it's not so user friendly and documentation isn't that great. but once you get it working its actually pretty useable
here is a dude that got it working with a truck (7060 ecm): http://www.thesecretdecoderring.com/aldl-io/
ALDL Scan Tool is a pretty trouble free app for android. Android is Linux too. The only problem I have is If I hit the data stream too fast after it connects it freezes the phone. Wait ten seconds and it golden.
https://play.google.com/store/apps/d....scan&hl=en_US
android isn't gnu/linux it just uses a linux based kernel. things that run on android don't run on linux and vise versa, they're completely different operating systems.Quote:
Originally Posted by donf
.. but for android, aldldroid is hands down way better than aldl scan tool
I really dont care, it works great for data logging. That was the intent of the thread