ALDLDroid Android App

[Dylan]

Wonder why that was? I just plugged my lead straight in and the app even opened itself straight up.
Running 12P 112.

[Jayme]

not sure... I connected it up and put the adx files on it, and it wouldnt get any data. so I stopped and went and ticked cable echo in the adx and copied them on again, and it started working...

[3400tZ]

Quick update on the NVRAM support... antus have been extremely helpful with everything. I got the code all written now, we'll be at the testing stage soon. He's working on preparing some hardware to be shipped to me so that I can test my code. Hopefully everything will go smooth and I will be able to get a new version out with NVRAM support soon after I receive the hardware. Keep in mind that he has to get it ready, ship it to me (from Australia to Canada) and I have to get everything working after, so it will be some time but some progress is definitely getting made.

[Dylan]

Sounds good can't wait for the update.

Big thanks to Antus could not of been anymore helpfull! Top work.

[Jayme]

AVT LS1 DPID V1.01.adx

(54.38 KiB) Downloaded 560 times

got really excited today, with a thought... the attached ADX can use tunerpro to log an OBD2 ls1 through an avt 852 cable, which has an FTDI usb interface.... why should it not work with aldldroid?

anyway... it doesnt work .... I get values flicking around, but it complains about checksum error and the guages flicker. I suppose it could be that aldldroid doesnt handle the adx's in the same way... ive got a very complex macro with multiple send commands to set up the AVT and fill the dynamic PID's with the sensors I want, then 3 different send and receive commands in a macro to log each of the 3 x 6 byte dynamic PIDs... it could be going wrong anywhere....

[durahax]

I have a blutooth AVT-855, I'm willing to do whatever to get this working. I have a ton of OBDII PCMs laying around and a few vehicles that have J1850 and CAN. I have almost 500 extended PIDs for the Duramax LB7 and LLY, and working on CAN based PCMs atm. Just bought another 08 Duramax LMM a few days ago. I never tried again since I mentioned it here - http://pcmhacking.net/forums/viewtopic. ... =20#p39991 I'm gonna get everything back up and running tomorrow and I'll see what I get. The Tx side of things seemed to work fine when I tried, I was assuming at the time it wasn't parsing the Rx data properly. I'd love to get 4x on my tablet, such wasted bandwidth the way people log on Android. I have a punch list that makes me want to punch myself lol. I'm here to help just ask. I did contact Sebastian via email, but I never responded to his last email. I'm sorry you were super helpful and I just had so much going on at the time. I also tried on USB avt, it was a dead end. The ftdi chip used is a older usb-parallel, I even used the libs from ftdi. I still lurk on here frequently, but just been super busy.

[Jayme]

my usb 852 seemed to want to talk ... I mean the guages were flickering so it at least thought it was trying to read something? I dont have another 852 to see whats really going on unless there is some way to log the serial port in android to a file to see what the app is txing and rxing. I might try next to limit it to a single tx and rx and see if it works better then.... maybe even setup the avt commands in windows, then leave the avt powered up and plug to the phone and try again in case its a connect macro problem.

[durahax]

my usb 852 seemed to want to talk ... I mean the guages were flickering so it at least thought it was trying to read something? I dont have another 852 to see whats really going on unless there is some way to log the serial port in android to a file to see what the app is txing and rxing. I might try next to limit it to a single tx and rx and see if it works better then.... maybe even setup the avt commands in windows, then leave the avt powered up and plug to the phone and try again in case its a connect macro problem.

Just download a bluetooth terminal app, forget the one I used that supported hex terminal. I just tried and it definitely is working, I'm using a Nexus 7 on 5.0.1. Also the tn147 sample app has a precompiled apk in the zip http://www.ftdichip.com/Drivers/D2XX.htm Install it and you'll see its communicating fine. That's crazy I spent days trying to get it working before, even tried with root and all the libs. Just glad were talking with the AVT-852 now. Now it's just the checksum error, I'm gonna pull everything out tomorrow.

[3400tZ]

Just enable the debug logging in the settings section of the app. It will create a log file that should be somewhat useful, hopefully...

[Jayme]

I did a debug and can see data sending and receiving... im yet to compare the exact packets but cant see too much wrong.... I suspect the problem lies with me using the header detection in tunerpro, which I suspect is not set up in aldldroid, so its seeing the incorrect packet lengths as they are not subtracted like tunerpro does.

tomorrow ill turn off header detection, and set up the message lengths and see if it logs correctly then.