Re: ALDLDroid Android App
Posted: Mon Jun 26, 2017 6:44 pm
Hi guys,
I tried the ALDLDroid app just now & have had a few issues. Went & downloaded three ADX files from here & saved them into the ALDLDroid adx folder on the tablet.
Hooked it all up & selected the connect to ecu tab. It then asked for a adx so I selected what I believed would be the right one for my vehicle. That being - VS 3 A6 Engine and trans TP5 v104.adx
The vehicle is my 4WD Hilux with the Ecotec V6 out of a VT. It is using a VT ecu without BCM via Marks 4WD Adapters engine loom conversion. I have logged before through my old tired Laptop & TunerPro V5 without problems.
Some history - The reason I selected that adx was because an earlier PM I had with VL400, when I bought one of his V2 loggers, I told him what vehicles I had & he loaded the adx's on the the SD card. I have not used his logger as yet but looked back at the PM to find which adx he had suggested I use.
To quote Ryan for the Toyota Hilux 4WD with ecotec V6 out of a VT model (no BCM) using the Marks 4WD adapters conversion engine loom - " This should use the A6_VS3A.adx ( essentially its a $A5 V6 ADX from a VT but does not look for the BCM). So that VS 3 A6 Engine and trans TP5 v104.adx was the closest I could see ??
Anyway it (ALDLDroid) has no connection to ecu & a message at bottom saying Checksum Mismatch.
If I disconnect from the ECU, I find when trying to reconnect I can't get an option to select another adx file. Thinking maybe when I was originally logging using TPV5 on this vehicle maybe I was using a VS adx like $51 VS V6 Engine and Trans v1.11 WB Innovate.adx, so was going to try with that one.
Is there some one here that could run through the settings on ALDLDroid I should or shouldn't have checked ? Also how to change the selected adx file ?
Pretty sure my OTG cable is working as when it first plugged in it asked if I wanted the USB connection to always go to ALDLDroid.
I tried the ALDLDroid app just now & have had a few issues. Went & downloaded three ADX files from here & saved them into the ALDLDroid adx folder on the tablet.
Hooked it all up & selected the connect to ecu tab. It then asked for a adx so I selected what I believed would be the right one for my vehicle. That being - VS 3 A6 Engine and trans TP5 v104.adx
The vehicle is my 4WD Hilux with the Ecotec V6 out of a VT. It is using a VT ecu without BCM via Marks 4WD Adapters engine loom conversion. I have logged before through my old tired Laptop & TunerPro V5 without problems.
Some history - The reason I selected that adx was because an earlier PM I had with VL400, when I bought one of his V2 loggers, I told him what vehicles I had & he loaded the adx's on the the SD card. I have not used his logger as yet but looked back at the PM to find which adx he had suggested I use.
To quote Ryan for the Toyota Hilux 4WD with ecotec V6 out of a VT model (no BCM) using the Marks 4WD adapters conversion engine loom - " This should use the A6_VS3A.adx ( essentially its a $A5 V6 ADX from a VT but does not look for the BCM). So that VS 3 A6 Engine and trans TP5 v104.adx was the closest I could see ??
Anyway it (ALDLDroid) has no connection to ecu & a message at bottom saying Checksum Mismatch.
If I disconnect from the ECU, I find when trying to reconnect I can't get an option to select another adx file. Thinking maybe when I was originally logging using TPV5 on this vehicle maybe I was using a VS adx like $51 VS V6 Engine and Trans v1.11 WB Innovate.adx, so was going to try with that one.
Is there some one here that could run through the settings on ALDLDroid I should or shouldn't have checked ? Also how to change the selected adx file ?
Pretty sure my OTG cable is working as when it first plugged in it asked if I wanted the USB connection to always go to ALDLDroid.