Does anyone know why the reason might be that data may not be transferring via aldl obd1 usb cable? The cable is recognized in aldl droid and tunerpro but it shows it can't communicate with either. More of an ecu roadblock....
My regular scanner works fine and the bluetooth adapter I had before worked fine until it didn't work anymore.....
just this over and over again in aldl droid
[DEBUG] (ECU) 08/30/24 20:25:51.180 Got response from ECU: ()
[ERROR] (ECU) 08/30/24 20:25:51.181 Incorrect response length, expected 72 but got 0: []
[DEBUG] (ECU) 08/30/24 20:25:51.183 Sending command "Mode 1, Message 0 Send" (F4 57 01 00 B4) and now listening for packet (72 bytes)
[DEBUG] (ECU) 08/30/24 20:25:51.701 Got response from ECU: ()
[ERROR] (ECU) 08/30/24 20:25:51.702 Incorrect response length, expected 72 but got 0: []
[DEBUG] (ECU) 08/30/24 20:25:51.705 Sending command "Mode 1, Message 0 Send" (F4 57 01 00 B4) and now listening for packet (72 bytes)
My regular scanner works fine and the bluetooth adapter I had before worked fine until it didn't work anymore.....
just this over and over again in aldl droid
[DEBUG] (ECU) 08/30/24 20:25:51.180 Got response from ECU: ()
[ERROR] (ECU) 08/30/24 20:25:51.181 Incorrect response length, expected 72 but got 0: []
[DEBUG] (ECU) 08/30/24 20:25:51.183 Sending command "Mode 1, Message 0 Send" (F4 57 01 00 B4) and now listening for packet (72 bytes)
[DEBUG] (ECU) 08/30/24 20:25:51.701 Got response from ECU: ()
[ERROR] (ECU) 08/30/24 20:25:51.702 Incorrect response length, expected 72 but got 0: []
[DEBUG] (ECU) 08/30/24 20:25:51.705 Sending command "Mode 1, Message 0 Send" (F4 57 01 00 B4) and now listening for packet (72 bytes)