ALDL Droid
03-26-2017, 03:18 PM
#1
Burning Brakes
Thread Starter
ALDL Droid
Has anyone noticed connectivity issues with their different phones? I have an old Nexus 7 tablet that seems to work great with ALDL droid and my bluetooth adapter. My Nexus 6p has all kinds of connectivity issues. Constantly drops connection to ECU and what not. Is this normal to vary from phone/tablet to phone/tablet?
03-26-2017, 06:35 PM
#2
Le Mans Master
No problems here.
I bought one of the cheapest units (under $10 shipped) to try it out. It connects fine to my Samsung phone. No drop outs either. I haven't tried it on my '96 Corvette, but it works with my Impala and 300.
I bought one of the cheapest units (under $10 shipped) to try it out. It connects fine to my Samsung phone. No drop outs either. I haven't tried it on my '96 Corvette, but it works with my Impala and 300.
03-27-2017, 06:04 PM
#3
Race Director
I did have some funky connection problems when I first started using it, and didn't know wtf I was doing. Is your OBD port clean, and tight connection? If yes, I would try it on another android device and see if it still acts up. Are you sure you have the correct ECM file for your car?
03-27-2017, 06:44 PM
#4
Team Owner
I'm curious. How do you have the right ECM file for your car if it is modified? I have a 91 auto. What would be the right file if my ECM has an EPROM that has been wiped out and reprogrammed?
03-28-2017, 08:15 AM
#7
Team Owner
03-28-2017, 09:05 AM
#8
Team Owner
Any difference between ALDL Droid and ALDL Scan?
03-28-2017, 11:27 AM
#9
Race Director
It's pretty much the same from what I've seen. Just that aldl droid is easier to read, you can put whatever readouts you want etc. And I believe better recordings of data logs. As in, better laid out. You could tune from aldl droid as well, but I have not fooled with that.
07-09-2017, 10:44 PM
#10
Instructor
ALDLscan "must be used with 1320electronics.com BT adapter". ALDLdroid may not be limited in the same way. I'm using ALDLdroid with moates.net APU1 autoprom USB connection.
FWIW - when connecting tunerpro on a laptop to datalog, there was a setting to adjust to help with intermittent connection.
FWIW - when connecting tunerpro on a laptop to datalog, there was a setting to adjust to help with intermittent connection.
07-09-2017, 11:59 PM
#11
Race Director
1320 BT Adapter will work with ALDLDroid.. I have that adapter, it works with my Nexus 7 Tablet..
With my current Android radio the Bluetooth if particular and I need to use a cable..
With my current Android radio the Bluetooth if particular and I need to use a cable..
The following users liked this post:
ryank9398 (07-11-2017)
07-11-2017, 08:58 AM
#13
Race Director
Also to answer the question of files to use.. While a tuner might have created a new BIN file with tweaks, it is based off of the model year you have. The model year is the definition
for example. .my 1990 ZR-1 uses a $8EA mask. so I have a $8EA.xdf (for tunerPro and ALDLDroid)
the XDF defines the parameters in the BIN file that is burned on your MEMCAL (Chip)
there is and ADX file, this is what TunerPro and ALDLDroid use to SCAN the parameters, the Tuners don't typically change this output. for my car I created a $8EA.ADX to scan with, which also will silence the CCM, I have created the ADX for all the ZR-1 years, as well as the 90-91 L98 and 92-93 LT1. Many here use my 92-93 ADX file for their cars.
for example. .my 1990 ZR-1 uses a $8EA mask. so I have a $8EA.xdf (for tunerPro and ALDLDroid)
the XDF defines the parameters in the BIN file that is burned on your MEMCAL (Chip)
there is and ADX file, this is what TunerPro and ALDLDroid use to SCAN the parameters, the Tuners don't typically change this output. for my car I created a $8EA.ADX to scan with, which also will silence the CCM, I have created the ADX for all the ZR-1 years, as well as the 90-91 L98 and 92-93 LT1. Many here use my 92-93 ADX file for their cars.
Last edited by -=Jeff=-; 07-11-2017 at 09:13 AM.
07-11-2017, 02:01 PM
#15
Instructor
Also to answer the question of files to use.. While a tuner might have created a new BIN file with tweaks, it is based off of the model year you have. The model year is the definition
for example. .my 1990 ZR-1 uses a $8EA mask. so I have a $8EA.xdf (for tunerPro and ALDLDroid)
the XDF defines the parameters in the BIN file that is burned on your MEMCAL (Chip)
there is and ADX file, this is what TunerPro and ALDLDroid use to SCAN the parameters, the Tuners don't typically change this output. for my car I created a $8EA.ADX to scan with, which also will silence the CCM, I have created the ADX for all the ZR-1 years, as well as the 90-91 L98 and 92-93 LT1. Many here use my 92-93 ADX file for their cars.
for example. .my 1990 ZR-1 uses a $8EA mask. so I have a $8EA.xdf (for tunerPro and ALDLDroid)
the XDF defines the parameters in the BIN file that is burned on your MEMCAL (Chip)
there is and ADX file, this is what TunerPro and ALDLDroid use to SCAN the parameters, the Tuners don't typically change this output. for my car I created a $8EA.ADX to scan with, which also will silence the CCM, I have created the ADX for all the ZR-1 years, as well as the 90-91 L98 and 92-93 LT1. Many here use my 92-93 ADX file for their cars.
07-11-2017, 02:11 PM
#16
Race Director
Jeff - while we are on the topic of creating a datastream definition would you please comment on how a person might have adapted an 7727 ecu to input data other than from stock sensors? For example, i've read about people trying to input their wideband analog in the datastream using the AC sensor sender or EGR analog location? How about teaching the ECU to interpret a 2 bar map sensor in place of the standard? Is this done with manipulation of the datastream?
Changing the datastream is somewhere in the BIN file mentioned earlier. I have heard about all you mentioned, but above my pay grade
meaning you need to find where the pointer is in the datastream code that points for the EGR, and change that to the unused input you attached the Wideband to.
the MAP sensor is also code changes in the BIN file
07-11-2017, 07:14 PM
#17
Drifting
Also to answer the question of files to use.. While a tuner might have created a new BIN file with tweaks, it is based off of the model year you have. The model year is the definition
for example. .my 1990 ZR-1 uses a $8EA mask. so I have a $8EA.xdf (for tunerPro and ALDLDroid)
the XDF defines the parameters in the BIN file that is burned on your MEMCAL (Chip)
there is and ADX file, this is what TunerPro and ALDLDroid use to SCAN the parameters, the Tuners don't typically change this output. for my car I created a $8EA.ADX to scan with, which also will silence the CCM, I have created the ADX for all the ZR-1 years, as well as the 90-91 L98 and 92-93 LT1. Many here use my 92-93 ADX file for their cars.
for example. .my 1990 ZR-1 uses a $8EA mask. so I have a $8EA.xdf (for tunerPro and ALDLDroid)
the XDF defines the parameters in the BIN file that is burned on your MEMCAL (Chip)
there is and ADX file, this is what TunerPro and ALDLDroid use to SCAN the parameters, the Tuners don't typically change this output. for my car I created a $8EA.ADX to scan with, which also will silence the CCM, I have created the ADX for all the ZR-1 years, as well as the 90-91 L98 and 92-93 LT1. Many here use my 92-93 ADX file for their cars.
If I'm reading this correctly the ADX file that you created for 92-93 can be used to SCAN parameters regardless of what is burned on the MEMCAL? Meaning if one vehicle has a stock MEMCAL and tune, and another has an aftermarket MEMCAL piggybacked off the stock (i.e PCM for less mail order) they can both use the ADX file you created?
07-11-2017, 09:05 PM
#18
Race Director
Yes. All that a tuner changed are variables for timing, fuels and other things. The main fabric remains the same. They are not redefining different areas of the file to use