ALDLDroid Android App

[3400tZ]

Sweet! Is the 4 bytes reply only what is expected as well ? antus, I'm asking because here is a log you sent me:

Code: Select all

00000004	0.00123781	[4656] writing block of 0x80 (0x0000 - 0x007F inclusive)	
00000005	0.00129443	[4656] writeEcuMemory writing 0x80 bytes to address 0x0000(0x8000)	
00000006	0.00141520	[4656] 00 12 01 01 02 50 8B 49 12 18 00 48 1F 18 00 48 1F 12 0A 10 01 08 FF EF 80 90 8A 1C 1A 10 00 28 8A 50 03 08 60 03 01 00 21 30 3C 4B 7D 04 9C 40 AB 06 00 72 FF D7 1C 0A 01 60 1C 50 0A 00 50 00 FF 39 39 FF 11 FF 05 28 FF 22 00 00 00 00 00 00 00 00 9B 00 00 52 44 44 44 3F 39 2E 23 1C 1C 1C 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 10 00 0B 39 39 44 44 2B 2B 2B 22 1C 1C 11 47 	
00000007	0.00145886	[4656] Calculating checksum for length=134	
00000008	0.00150043	[4656] Calculated 0x83	
00000009	0.00153928	[4656] getting lock....	
00000010	0.00157662	[4656] got it	
00000011	0.00161728	[4656] Sending 134 byte packet to device F4	
00000012	0.00166456	[4656] Packet length: 134	
00000013	0.00179196	[4656] F4 D8 0C 80 00 00 12 01 01 02 50 8B 49 12 18 00 48 1F 18 00 48 1F 12 0A 10 01 08 FF EF 80 90 8A 1C 1A 10 00 28 8A 50 03 08 60 03 01 00 21 30 3C 4B 7D 04 9C 40 AB 06 00 72 FF D7 1C 0A 01 60 1C 50 0A 00 50 00 FF 39 39 FF 11 FF 05 28 FF 22 00 00 00 00 00 00 00 00 9B 00 00 52 44 44 44 3F 39 2E 23 1C 1C 1C 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 10 00 0B 39 39 44 44 2B 2B 2B 22 1C 1C 11 47 83 	
00000014	0.07666419	[4656] handling echo	
00000015	0.07673255	[4656] Incoming 134 byte ALDL packet from device F4	
00000016	0.16866453	[4656] F4 D8 0C 80 00 00 12 01 01 02 50 8B 49 12 18 00 48 1F 18 00 48 1F 12 0A 10 01 08 FF EF 80 90 8A 1C 1A 10 00 28 8A 50 03 08 60 03 01 00 21 30 3C 4B 7D 04 9C 40 AB 06 00 72 FF D7 1C 0A 01 60 1C 50 0A 00 50 00 FF 39 39 FF 11 FF 05 28 FF 22 00 00 00 00 00 00 00 00 9B 00 00 52 44 44 44 3F 39 2E 23 1C 1C 1C 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 10 00 0B 39 39 44 44 2B 2B 2B 22 1C 1C 11 47 83 	
00000017	0.16871482	[4656] write complete, ok	
00000018	0.18455483	[4656] Incoming 4 byte ALDL packet from device F4	
00000019	0.18461265	[4656] releasing lock....	
00000020	0.18465813	[4656] Incoming ALDL has checksum AA	
00000021	0.18469848	[4656] Calculating checksum for length=4	
00000022	0.18474095	[4656] Calculated 0xAA	
00000023	0.18478040	[4656] RX: 	
00000024	0.18482196	[4656] F4 56 0C AA 	

And here is what I'm getting with my app:

Code: Select all

05-03 01:40:10.710: D/NVRAM(12829): Reading 128 bytes from local bin file /storage/emulated/0/ALDLdroid/bin/OSE $12P V112 APNX V6.BIN at offset 0
05-03 01:40:10.710: D/NVRAM(12829): Read 128 bytes
05-03 01:40:10.720: D/NVRAM(12829): Writing command to ALDL: f4 d8 0c 80 00 00 12 01 01 02 50 8b 49 12 18 00 48 1f 18 00 48 1f 12 0a 10 01 08 ff ef 80 90 8a 1c 1a 10 00 28 8a 50 03 ..........P.I...H...H...............(.P.
05-03 01:40:10.720: D/NVRAM(12829):  08 60 03 01 00 21 30 3c 4b 7d 04 9c 40 ab 06 00 72 ff d7 1c 0a 01 60 1c 50 0a 00 50 00 ff 39 39 ff 11 ff 05 28 ff 22 00 .`...!0<K}[email protected].....`.P..P..99....(.".
05-03 01:40:10.720: D/NVRAM(12829):  00 00 00 00 00 00 00 9b 00 00 52 44 44 44 3f 39 2e 23 1c 1c 1c 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 10 00 ..........RDDD?9.#......................
05-03 01:40:10.720: D/NVRAM(12829):  0b 39 39 44 44 2b 2b 2b 22 1c 1c 11 47 83                                                                               .99DD+++"...G.
05-03 01:40:13.370: D/NVRAM(12829): Got ECU response: f4 56 0c aa                                                                                                             .V..
05-03 01:40:13.590: D/NVRAM(12829): Reading 128 bytes from local bin file /storage/emulated/0/ALDLdroid/bin/OSE $12P V112 APNX V6.BIN at offset 128
05-03 01:40:13.590: D/NVRAM(12829): Read 128 bytes
05-03 01:40:13.590: D/NVRAM(12829): Writing command to ALDL: f4 d8 0c 80 80 53 50 44 44 3f 35 32 26 21 1f 50 5b 50 55 55 4a 39 37 2b 28 22 50 50 55 5a 5a 55 44 44 36 36 36 39 5a 64 .....SPDD?52&!.P[PUUJ97+("PPUZZUDD6669Zd
05-03 01:40:13.590: D/NVRAM(12829):  64 64 64 55 50 3f 3c 3c 2b 55 64 64 64 5b 4d 50 50 47 47 2b 4d 58 58 5b 5b 58 4d 4a 47 47 39 50 64 64 64 61 47 47 47 44 dddUP?<<+Uddd[MPPGG+MXX[[XMJGG9PdddaGGGD
05-03 01:40:13.590: D/NVRAM(12829):  44 39 4a 64 64 4d 41 3c 36 36 39 39 39 50 64 61 55 39 39 3c 39 3f 3f 39 55 69 66 55 3c 33 39 39 3f 3f 39 5b 6e 69 58 4a D9JddMA<66999PdaU99<9??9UifU<399??9[niXJ
05-03 01:40:13.590: D/NVRAM(12829):  47 47 4d 47 47 39 5b 6e 69 58 4a 47 47 09                                                                               GGMGG9[niXJGG.
05-03 01:40:16.200: D/NVRAM(12829): Got ECU response: f4 56 0c aa                                                                                                             .V..
05-03 01:40:16.280: D/NVRAM(12829): Reading 128 bytes from local bin file /storage/emulated/0/ALDLdroid/bin/OSE $12P V112 APNX V6.BIN at offset 256
05-03 01:40:16.280: D/NVRAM(12829): Read 128 bytes
05-03 01:40:16.290: D/NVRAM(12829): Writing command to ALDL: f4 d8 0c 81 00 4d 47 47 39 5b 6e 69 58 4a 47 47 4d 47 47 39 5b 6e 69 58 4a 47 47 4d 47 47 39 5b 6e 69 58 4a 47 47 4d 47 .....MGG9[niXJGGMGG9[niXJGGMGG9[niXJGGMG
05-03 01:40:16.290: D/NVRAM(12829):  47 39 5b 6e 69 58 4a 47 47 4d 47 47 39 5b 6e 69 58 4a 47 47 4d 47 47 39 5b 6e 69 58 4a 47 47 4d 47 47 39 5b 6e 69 58 4a G9[niXJGGMGG9[niXJGGMGG9[niXJGGMGG9[niXJ
05-03 01:40:16.290: D/NVRAM(12829):  47 47 4d 47 47 39 5b 6e 69 58 4a 47 47 4d 47 47 39 5b 6e 69 58 4a 47 47 4d 47 47 39 5b 6e 69 58 4a 47 47 4d 47 47 39 5b GGMGG9[niXJGGMGG9[niXJGGMGG9[niXJGGMGG9[
05-03 01:40:16.290: D/NVRAM(12829):  6e 69 58 4a 47 47 4d 47 47 10 00 0b 39 66                                                                               niXJGGMGG...9f
05-03 01:40:18.910: D/NVRAM(12829): Got ECU response: f4 56 0c aa                                                                                                             .V..
05-03 01:40:18.990: D/NVRAM(12829): Reading 128 bytes from local bin file /storage/emulated/0/ALDLdroid/bin/OSE $12P V112 APNX V6.BIN at offset 384
05-03 01:40:18.990: D/NVRAM(12829): Read 128 bytes
05-03 01:40:18.990: D/NVRAM(12829): Writing command to ALDL: f4 d8 0c 81 80 39 39 39 39 39 39 39 39 39 39 39 39 39 39 39 39 39 39 39 39 39 39 39 39 39 39 39 39 39 39 39 39 39 39 39 .....99999999999999999999999999999999999
05-03 01:40:18.990: D/NVRAM(12829):  39 39 39 39 39 39 39 39 39 39 39 39 39 39 39 39 39 39 39 39 39 39 39 39 39 39 39 39 39 39 39 39 39 39 39 39 39 39 39 39 9999999999999999999999999999999999999999
05-03 01:40:18.990: D/NVRAM(12829):  39 39 39 39 39 39 39 39 39 39 39 39 39 39 39 39 39 39 39 39 39 39 39 39 39 39 39 39 39 39 39 39 39 39 39 39 39 39 39 39 9999999999999999999999999999999999999999
05-03 01:40:18.990: D/NVRAM(12829):  39 39 39 39 39 39 39 39 39 39 39 39 39 a7                                                                               9999999999999.
05-03 01:40:21.590: D/NVRAM(12829): Got ECU response: f4 56 0c aa          

From what I understand from your log, you're getting the whole thing you've written back and the same 4 bytes reply as I'm after. Anyway, I will be able to verify that soon enough but I'm a bit curious right now

Thanks for the quick answer guys!

[Holden202T]

antus might have used a different interface that has echo ?

[3400tZ]

Very possible, yes

[antus]

Yes that is echo, from the interface.

OSEPlugin v2.xx code hides the echo, because as you found, it causes confusion and the content is the same as what is logged from the transmission.

[3400tZ]

Getting very close now...

[festy]

Looking good

[VL400]

Nice work! Starting to take shape.

[3400tZ]

Yep, now if I can just find one evening this week that I can work on this, I will push a version to Play for you guys to play with.

[ralcool]

Shit hot... Just finished reading your thread over at gearhead..all 71pages of it.

I better understand FTDI vs Prolific & ALDL vs OBD2 cables.. naturally I have all the wrong types.

Man, I was ripping out my hair asking myself why your app wouldn't connect to my ecu.... using a HTC One X to VS_V6_$51 Enhanced.adx
Simply using an incompatible aldl cable for the app.

I can see what you mean by Prolific being a PITA, I have two here. One works in TunerPro, one doesn't. Neither work in ALDLdroid..
no prolific support yet apparently.
Soon?

Amazingly the lead DO I use for tunerPro is chained usb-serial-aldl...using a Prolific ch340 driver. (Provider wch.cn v3.1.2009.6)
Never missed a beat.

The other lead is usb - aldl direct.. also ch340.. it detects and loads to a different Com port number .. and then doesn't work, never 'connects'
Although I suspect its wired to the obd pins in the plug, not aldl.

I've ordered a FT232RL - USB thing instead to whack into the 16 pin plug to replace the prolific pcb, and use your app!

Then there is a elm327 cable here that is a bit of an unknown... and I've learned it could possibly support aldl and obd2 if its internally complete. Never figured it out... don't need it.

A bluetooth obd2 adapter I finally used the other day on a friends VZ V6 with the Torque app. Worked perfectly. If you do add obd2 support, I can 'borrow' the car again to test.

Its rather annoying using a laptop to log.. battery life is the killer.. I've a small 400w inverter I sometimes use for longer drives.

Awesome work.

[festy]

CH340 is a WinChipHead bridge, not Prolific.