ALDLdroid

[3400tZ]

Can you please give me the exact error message in red, I don't believe ecu not connected is a message the app is displaying.

Thank you

[maxpowerta]

Sorry what it's actually saying at the bottom in red is no response from ECU, at the top left it says connected RPS 0.0 I have the debug log if you'd like to see also. Most of what's in there is this repeated over and over,
ERROR] (ECU) 05/17/22 11:34:49.043 Incorrect response length, expected 71 but got 0: [][DEBUG] (ECU) 05/17/22 11:34:49.043 Sending command "Mode 1 ALDL Dump Request Send" (80 56 01 29) and now listening for packet (71 bytes)
[DEBUG] (ECU) 05/17/22 11:34:49.044 Pause of 20ms
[DEBUG] (ECU) 05/17/22 11:34:49.603 Got response from ECU: ()
[ERROR] (ECU) 05/17/22 11:34:49.604 Incorrect response length, expected 71 but got 0: []
[DEBUG] (ECU) 05/17/22 11:34:49.607 Sending command "Mode 1 ALDL Dump Request Send" (80 56 01 29) and now listening for packet (71 bytes)

[3400tZ]

Looks like the app is receiving no data at all... could it be a bad connection at the ALDL connector or something ? The command that is being sent is fine but the data is getting lost between your ECU and the app somehow. Something is different than when you're using TunerPro it seems, not sure if you can pinpoint what exactly

[kur4o]

I tested some adx on an older version of the app.
The first attached adx opens fine.
second gives some error[Can`t parse the adx]

I did an in depth compare between the 2 adxs but couldn`t figure any out of place issue. The files do look almost identical. Even on hex compare.

[3400tZ]

I tested some adx on an older version of the app.
The first attached adx opens fine.
second gives some error[Can`t parse the adx]

I did an in depth compare between the 2 adxs but couldn`t figure any out of place issue. The files do look almost identical. Even on hex compare.

The MODE 4 BLM RESET bytestring looks weird in that MOD ADX, that's probably your problem, try reverting that part to like the original ADX file

[kur4o]

The MODE 4 BLM RESET bytestring looks weird in that MOD ADX, that's probably your problem, try reverting that part to like the original ADX file

That got some empty string for command out of nowhere. Thanks for spotting it. Now all loads fine.