ALDLDroid Android App

[Jayme]

id say thats the problem. ive only ever used it with an otg cable.

[kojab]

So a FTDI Android driver is not needed?

[Dylan]

The cable I use come from Jaycar about $10. Nothing special I thought just an adapter I've always assumed. Funny enough from the very first time I used it as soon as I plug it in to my VL400 spec interface it's opened ALDLdroid automatically.

[Dylan]

Last time I used it was an older version and I used to have to try to connect twice. First was always an error like yours and second time was a goer.

[Dylan]

USB OTG may be special cabes not jst an adapter as I thought.

http://m.instructables.com/id/Make-a-US ... -easy-way/

Pins need to be shorted to ground to ID it as a OTG cable.

[antus]

Yes, you do need an OTG cable, it switches the device in to a USB bus master mode instead of a client like it normally is for PC connectivity where PC is the master.

They are pretty cheap and commonly available. I would buy a couple incase one doesnt work. This is a random unverified seller but it gives you an idea whats out there. Then use the same cable you would to a PC with it.

http://www.ebay.com.au/itm/182009794068

[VK_3800]

I think I figured out the XDL issue. According to info here and my digging into the files, the structure of a frame is something like:

* 4 bytes next frame address
* 4 bytes timestamp
* 4 bytes message ID
* 57 bytes actual data as per ADX (for $12P)
* 6 bytes (not sure, not always there in Tunerpro logs but is in my ALDLDroid ones)

Whenever I open any of the ALDLDroid XDL log files in Tunerpro nothing useful happens. If you export it to CSV you get two samples only - the first is perfect, the second is rubbish - but, the timestamp on the second matches the data in the file if the frame did not include the last 6 bytes! Tunerpro doesn't seem to use the next frame address from the beginning of the frame, it uses a fixed length in the header. Comparing a Tunerpro log which has the 6 bytes versus one which doesn't, I see 0x39 (57) at position 0x44 and 0x48 for the one without, and 0x3F (63) for the one that includes it at those positions. The ALDLDroid log has a value of 57 here too, if I change it to 63 then suddenly everything works!

Before and after attached.

[Dylan]

Yes, you do need an OTG cable, it switches the device in to a USB bus master mode instead of a client like it normally is for PC connectivity where PC is the master.

They are pretty cheap and commonly available. I would buy a couple incase one doesnt work. This is a random unverified seller but it gives you an idea whats out there. Then use the same cable you would to a PC with it.

http://www.ebay.com.au/itm/182009794068

Am I reading correct, $1 buy it now and free delivery????

[HQ355]

Buy it, it's only a $1 find out !

[antus]

Yes thats right....

@VK_3800 - nice find about the file format! You should also send that to 3400tZ by PM if he doesnt see it in this thread.