ALDLdroid

[EagleMark]

Nope! When I started work on the $42 ADX I used what was there from the old ADS.

[3400tZ]

Fair enough, I guess ignoring the header string is the right thing to do for 160 baud then :) Thx

[EagleMark]

Can you still bench test it? If not I'll go fire up the Suburban tomorrow...

[3400tZ]

Sure, I did, and it works great! But of course I won't say no if you want to try it on your side :)

[34blazer]

http://www.fiero.nl/forum/Forum1/HTM....html#lastpost

[3400tZ]

Yep! I've been talking to Timm, he's sending me a V2 of his Bluetooth adapter for testing :)

Jeff, is that you that sent a crash report about the tuning section ? Seems to be a table... If you could send me the XDF you used (or a link to it) and which table were you clicking on, it would be awesome. I can probably fix this easily for the next version.

Thanks

[-=Jeff=-]

Yep it was me :) I will email you the xdf I was using.

[3400tZ]

aldldroidapp AT gmail.com if you can :)

Thank you

[-=Jeff=-]

Yep! I've been talking to Timm, he's sending me a V2 of his Bluetooth adapter for testing :)


Thanks

Cool, interested to hear the results, I may get one of those, but will wait for the V2 report

[GaryDoug]

Got the adapter. These are the results using the "$EE_auto.adx":

Reading are very erratic. Message at the bottom flashing "Incorrect response length from ECU (xx vs 68)" where xx varies and is generally under 68. My data definition sheet shows this as 60 bytes (+3 for header and +1 for checksum).
Attached is a data sniffer log file that starts about 6 seconds before the Connect to ECU is performed and ends several seconds after the scanning starts. Transmit and receive strings are shown.
I see no silence commands (F4 56 08 cs) anywhere, but I do see PCM chatter (strings beginning with F0, 90, and 0A) before and after the data requests/returns for mode 1 address 0.
Could be more than one fault. Thanks

[EagleMark]

Got the adapter. These are the results using the "$EE_auto.adx":

That ADX is seriously flawed and has never worked on anything! I have offered Mark at TunerPro many ADX and XDF files we have all worked on but nothing has been updated for years. Always check here for updated XDF and ADX files!

This is the one I built and includes the HVAC silence needed for Buick Roadmaster LT1 but also works on others. $EE-16188051-V3.8.adx Check this post for even more updated LT1 XDF and ADX files from steveo, there is a link to where he keeps most up to date.
http://www.gearhead-efi.com/Fuel-Inj...ull=1#post3131

[3400tZ]

I was about to say that ADX is a bit weird. :)

Gary, are you using the latest version of ALDLdroid (0.18 ?) You're saying 0.1 so I wasn't sure. Looking at the log of what I'm sending to the ECM using version 0.18 of ALDLdroid, I'm seeing:

12-05 23:27:42.179: D/ECUCommsThread(7847): Sending command "Mode 8 Send" (f4 56 08 ae) and now listening for packet (7 bytes)
12-05 23:27:42.579: D/ECUCommsThread(7847): Sending command "Mode 1 Message 0 Send" (f4 57 01 00 b4) and now listening for packet (68 bytes)
12-05 23:27:43.009: D/ECUCommsThread(7847): Sending command "Mode 1 Message 0 Send" (f4 57 01 00 b4) and now listening for packet (68 bytes)
12-05 23:27:43.410: D/ECUCommsThread(7847): Sending command "Mode 1 Message 0 Send" (f4 57 01 00 b4) and now listening for packet (68 bytes)
12-05 23:27:43.830: D/ECUCommsThread(7847): Sending command "Mode 1 Message 0 Send" (f4 57 01 00 b4) and now listening for packet (68 bytes)
12-05 23:27:44.251: D/ECUCommsThread(7847): Sending command "Mode 1 Message 0 Send" (f4 57 01 00 b4) and now listening for packet (68 bytes)
12-05 23:27:44.661: D/ECUCommsThread(7847): Sending command "Mode 1 Message 0 Send" (f4 57 01 00 b4) and now listening for packet (68 bytes)


Which doesn't seems to match what you're seeing for some reason... Only thing I can think of is that the Mode 8 command get send before being fully connected somehow... maybe ? Unless you're using an older version of the app, please make sure you upgrade first :)

[GaryDoug]

That ADX is seriously flawed and has never worked on anything!

Mark,
That file works just fine for me when using TunerproRT. Is that not good enough? Is TunerproRT not "anything"?

Using the V3.8 file did not improve the results, although now it says the length is 69 bytes!

Sebastien,
68 (0r 69) bytes is the wrong number for this pcm. It is 60 bytes data for mode 1 address 0 (+4 for header and checksum=64). All the other modes and addresses are even shorter.

I am using version 0.18 now, was 0.16 at first. Results are identical.

Your data shows the silence request occurring only 0.4 seconds before the first data request (mode1, address0). My sniffer started 6 seconds before the first data request as you can see, so it should have appeared. Using a scope, I can clearly see the chatter occurring throughout the process.

Why are you looking for 7 bytes after sending the silence request? The response is exactly the request string, 4 bytes identical.

[EagleMark]

What ALDL.ds file are you looking at for the length?

[GaryDoug]

For the silence command and reply...

From $EE118051-V3.8.adx (currently being used):
(for all of these add 1 for the checksum = 4 total)
<ADXCSENDCOMMAND id="SILENCESEND" idhash="0x0D281E71" title="Silence Chatter Send">
<bytestring size="0x4">F45608AE</bytestring>
</ADXCSENDCOMMAND>

<ADXCLISTENPACKET id="SILENCEREPLY" idhash="0x77161740" title="Silence Chatter Reply" flags="0x00000004">
<desc>Process data unchecked</desc>
<listentimeout>400</listentimeout>
<packetbodylength>3</packetbodylength>
<packetoffsetinbody>0</packetoffsetinbody>
<packetsize>3</packetsize>
</ADXCLISTENPACKET

(packet size = 3, add the checksum byte = 4)

From the $EE_auto.adx:


<ADXCSENDCOMMAND id="COMMAND3" idhash="0xC579A6D3" title="Mode 8 Send">
<bytestring size="0x4">F45608AE</bytestring>
</ADXCSENDCOMMAND>


<ADXCLISTENPACKET id="COMMAND3RE" idhash="0xE6981C55" title="Mode 8 Reply" flags="0x00000005">
<listentimeout>400</listentimeout>
<packetbodylength>3</packetbodylength>
<packetoffsetinbody>0</packetoffsetinbody>
<packetsize>3</packetsize>
</ADXCLISTENPACKET>

Similar for the Mode 1 address 0 request/reply
From the $EE-118051-V3.8.adx:

<ADXCSENDCOMMAND id="COMMAND0" idhash="0xC579AD33" title="Engine Send">
<bytestring size="0x5">F4570100B4</bytestring>
</ADXCSENDCOMMAND>

<ADXCLISTENPACKET id="COMMAND0RE" idhash="0xE6B79C55" title="Engine Reply" flags="0x00000005">
<listentimeout>400</listentimeout>
<packetbodylength>64</packetbodylength>
<packetoffsetinbody>3</packetoffsetinbody>
<packetsize>60</packetsize>
</ADXCLISTENPACKET>