5 Attachment(s)
Help getting ALDLDroid working for an L67 1993 Bonneville
Hey All,
Wondering if anyone can give me a touch of guidance... I recently purchased ALDLDroid (Thank you for your work Sebastien!) and a Bluetooth ALDL adapter from Red Devil River, for use on my 3.8L L67 1993 Bonneville. I've spent a few evenings now trying to get some rational results out of ALDLDroid, and think I'm going to have to break down and ask for some help... I'd played with WinALDL in years gone by on a couple of 3rd Gen F-Bodies, always using a homemade interface, so I'm not a complete neophyte, but this one is dumbfounding me so far...
By all references, the PCM is using an A163 datastream @ 8192 baud, and I'm using the matching '1992 - 93 3800 NA & Supercharged (L27) & (L67) Buick & Pontiac $5B4.ADX' definition file from the Red Devil River supplied definitions. I've cross referenced the definition with the original A163.DS file, and it SEEMS correct, although I'm fairly new to the ADX format.
What's confusing me is, if I take the debug log from ALDLDroid and apply a set of regular expressions I came up with to align the data reply frames, then decode them manually (one parameter at a time) vs. the A163.DS specification, I get completely sensical data, that matches what I know to be true (RPM, coolant temps, etc). If I compare this to the data log from ALDLDroid, it doesn't make any sense.. the data log values are all over the map, making me think that the problem must be with how the ALDLDroid app is interpreting the .ADX file...
1. It seems to me that it cannot be a communitations problem with the ALDL-Bluetooth adapter, because the debug log is showing proper values, once I sort them out.
2. I tried modifying the .ADX file in a number of ways, both hand editing and via TunerPro RT, but I've not had any success. I had high hopes for defining the header byte string of the Mode 1 Reply, and setting the align to header option, because really this is all I'm doing to the debug log to make sense of it, but I didn't get any joy...
I know that one of the typical troubleshooting steps would be to ensure that things are working through TunerPro RT, but I'll admit that the only laptop I've got in the vicinity right now is running windows 8, and the combination of Windows 8, Bluetooth, emulated serial data stream, etc. is not something I've got working yet either... I figured I'd focus on one problem at a time.
I've uploaded the .adx file, the 163.ds that it was originally spawned from, the datalog, the debug log, and a version of the debug log showing only the result data after it's cleaned up and aligned using the following regular expression commands:
:g!/Got response/d
:%s/^.*ECU: //
:%s/\n/ /g
:%s/F4 57 01 00 B4\( ..\)\{67\}/\r\0\r/g
:g!/F4 57 01 00 B4/d
I would very much appreciate any help anyone (especially Sebastien, hint hint, nudge nudge) could offer in sorting out what might be going on...
Cheers and thanks,
...Steve...