ALDL Droid '91 ZR-1 with BFXBG chip - CHECKSUM MISMATCH

[MuRCieLaGo]

Hello guys,

Just received my ALDL module from 1320 Electronics. I can't read data because I get the "CHECKSUM MISMATCH" error. Is it something to do with Marc Haibeck's chip?

I'm using the provided LT5 adx file.

[KPW]

I had a similar issue when I unboxed mine last year. I contacted John Wales from 1320electronics and he was able to get me new software versions for the tool and get me up and running. Very helpful.


Sent from my iPhone using ZR-1 Net Registry (http://r.tapatalk.com/byo?rid=90383)

[XfireZ51]

Hello guys,

Just received my ALDL module from 1320 Electronics. I can't read data because I get the "CHECKSUM MISMATCH" error. Is it something to do with Marc Haibeck's chip?

I'm using the provided LT5 adx file.

Sounds like you are using the wrong .adx

[KPW]

I do also seem to remember needing an updated .adx as well.


Sent from my iPhone using ZR-1 Net Registry (http://r.tapatalk.com/byo?rid=90383)

[XfireZ51]

Not to be picky, but the .adx doesn't get updated. Its a matter of using the correct one for the aldl datastream in ur car. The OEMs don't change that once the programming is done for that powertrain. Not trying to be a smarta**, just want to clarify the difference.

[BlackZR1]

Hello guys,

Just received my ALDL module from 1320 Electronics. I can't read data because I get the "CHECKSUM MISMATCH" error. Is it something to do with Marc Haibeck's chip?

I'm using the provided LT5 adx file.

I also had the issue you described with my Samsung S4 phone. Problem occurred every few seconds intermittently and I would get a bogus set of data in the middle of a log. After checking all my settings including talking with John at 1320 and Sebastien at ALDLdroid I never did find a solution.

Then for the heck of it I tried it on my Dell Android Tablet and it worked perfectly first time with no other changes.

[Billy Mild]

I have issues with my Nexus 6p phone, but it works great with my first gen Nexus 7 tablet.

[MuRCieLaGo]

I also had the issue you described with my Samsung S4 phone. Problem occurred every few seconds intermittently and I would get a bogus set of data in the middle of a log. After checking all my settings including talking with John at 1320 and Sebastien at ALDLdroid I never did find a solution.

Then for the heck of it I tried it on my Dell Android Tablet and it worked perfectly first time with no other changes.

Pretty much the same problem here!

Jeff from the forum here was nice enough to send me his "updated" adx file via email. However, I've got the same issue than before.

Works almost perfectly the first 4 seconds, then I get a bunch of checksum mismatches and the app becomes kind of crazy.

Using Samsung Galaxy S7...

I already contacted John Wales last year about the issue, I really feel like he did his best (what an awesome service). He sent me a couple of adx files, without success.

Sébastien Giroux (creator of ALDLdroid) couldn't really help me he said.

[XfireZ51]

I use a $70 ASUS tablet and it works great. Sometimes I will need to restart the app but then it works rather flawlessly. I recently worked w Ccmano on tuning his LT5 remotely and Hans used ALDLdroid very consistently.

[Ccmano]

I’m running it on a $49 Amazon Fire7 tablet. Works great. I do find sometimes I have turn the Bluetooth adapter on and off a few times or reboot the APP to get rid of the checksum errors.
H
:cheers:

[MuRCieLaGo]

I use a $70 ASUS tablet and it works great. Sometimes I will need to restart the app but then it works rather flawlessly. I recently worked w Ccmano on tuning his LT5 remotely and Hans used ALDLdroid very consistently.

I’m running it on a $49 Amazon Fire7 tablet. Works great. I do find sometimes I have turn the Bluetooth adapter on and off a few times or reboot the APP to get rid of the checksum errors.
H
:cheers:

Well I'm the third guy here having issues using the app with a cell phone. A tablet is definitely worth a try. I'll go buy one at Walmart tomorrow, that would be so great!

[-=Jeff=-]

Make sure the dip settings are correct on the 1320 box. I have also found that sometime with Bluetooth you need to restart the process to connect, I personally prefer the cable, but the Bluetooth is nice.

I shipping example with ALDLdroid is for a 1990. I worked with Sebastian when he was developing the app. Works on my Nexus 7 first and second generations


Sent from my iPhone using ZR-1 Net Registry (http://r.tapatalk.com/byo?rid=90383)

[MuRCieLaGo]

Update:

Tried a cheap RCA Voyager III tablet this morning and it works flawlessly! For some reason it doesn't seem to work on most cell phones...

[MuRCieLaGo]

On GearHead EFI forum, there is a big thread about the app (http://www.gearhead-efi.com/Fuel-Injection/showthread.php?2318-ALDLdroid) but nothing seems to be covering the issue here.

Maybe it could be interesting to create a compatibility list like this one:

Green works fine.
Red doesn't work.

Amazon Fire 7
Google Nexus 6P
Google Nexus 7 1st Gen
Google Nexus 7 2nd Gen
RCA Voyager III
Samsung Galaxy S4
Samsung Galaxy S7

[Ccmano]

I have found Samsung phone products to be glitchy in general. Had a few a couple years ago when they were touted as the greatest thing since sliced bread. Nothing but problems. Went back to my iPhone and IPad. I really wish the app had been developed for iPad.
H

[Jagdpanzer]

Resurrecting this post from last year.
I recently acquired a 1320 ALDL Bluetooth Adapter for use with a Samsung Galaxy Tab A (2016) model SM-T280 tablet and ALDLDroid app. Tried a few ADX files from the internet and still having a lot of
“Checksum Mismatch/incorrect response length from the ECU”
errors along with garbage data being displayed.
I've gone through the tips members have provided here on the forum and also contacting John Wales at 1320 but so far no success. For reference this setup appears to work fine using the 1320 ALDL Scan app.
Anyone have an idea what could be going wrong? Car is a 1994 ZR-1.

[XfireZ51]

Phil,

Are u using the $F0 adx? Also, under settings, u need to disable the checksum.
I have been using an ASUS tablet for several years w the Red Devil BT ALDL.
WORKS FINE. A few times I may need to restart but once it connects, its pretty flawless. Also have found that It works well after disabling WiFi and enabling BT.
Sometimes a stray network will interrupt logging so I shut it off while driving.

Give me a shout Phil if ur still having an issue. I visited w Gary in WI who was having similar issue using Samsung. Turned out it was his Samsung phone he was trying to use. Perhaps Samsung’s “version” of Android could be an issue.

[MuRCieLaGo]

Resurrecting this post from last year.
I recently acquired a 1320 ALDL Bluetooth Adapter for use with a Samsung Galaxy Tab A (2016) model SM-T280 tablet and ALDLDroid app. Tried a few ADX files from the internet and still having a lot of
“Checksum Mismatch/incorrect response length from the ECU”
errors along with garbage data being displayed.
I've gone through the tips members have provided here on the forum and also contacting John Wales at 1320 but so far no success. For reference this setup appears to work fine using the 1320 ALDL Scan app.
Anyone have an idea what could be going wrong? Car is a 1994 ZR-1.

As I mentioned, I had LOTS of emails with John Wales/Sébastien Giroux and we never managed to get it working correctly on my Samsung S7.

[-=Jeff=-]

Whose ADX file are you using?

[Jagdpanzer]

Jeff,
I’ve tried the FO adx file you posted up a while back and one John Wall sent me.