ALDLdroid

**3400tZ** · 06-14-2014

More and more interesting... What about real time tuning ?

I'm starting to think your AutoProm get categorized as chip programmer so it might not be in real time tuning. Is it ? I'm not sure what would be going on with ALDL tho. I really hope I won't have to buy an AutoProm to test all this but I might have to :P

Any chance you have a regular ALDL cable as well to try ?

Anyway the debugging log should help as well.

EDIT: WAIT! Does the AutoProm does the chip programming, real time tuning AND ALDL all with the same USB cable ? If so, I'm pretty sure I know what the problem is...

**Scrufdog** · 06-15-2014

Yup, one cable to rule them all.

**3400tZ** · 06-15-2014

Ok so if that is the case, the way the code is currently setup, only chip programming would work with the AutoProm. It seems to be exactly what's going on for you so now it makes sense. I already have the fix written, just need to make sure everything is fine. I don't have an AutoProm to test but I'm pretty confident it will fix the issue. Also, if it doesn't work, we will have the added debugging as least.

New Play release will be either tonight or tomorrow. Will update this thread once it happen.

**Scrufdog** · 06-15-2014

Cool. I will test when I see it.

**3400tZ** · 06-15-2014

New version is on Play, give it a try and let me know :)

**Scrufdog** · 06-15-2014

Debug sent. Getting closer. Seems to connect, says no response from ecu.

**3400tZ** · 06-15-2014

Replied to your email with a possible solution, let me know :)

**Scrufdog** · 06-15-2014

Replying here for public reference.

For the Apu to to do real time tuning and datalogging, I have my switches to Apu mode and 10k.

For datalogging only it's set to Bypass and Open, the open setting may change per ecu, older ones require 10k for datalogging only.

Aldldroid works when the Apu is in datalogging only mode for datalogging. And it can program when it's in Apu mode. So currently you have to change modes to switch between modes. Whereas TunerPro RT can do everything while in Apu mode.

Progress is being made.

Let me know if you want more testing.

**3400tZ** · 06-15-2014

Yep, I didn't know about this switch on the AutoProm until I found the documentation for it on Moates website yesterday night. So like you said, switch to APU1 to do chip programming and real time tuning and switch to pass-through mode to do data logging. Now, I really want to add support for data logging on APU1 mode because I can understand that's its a bit annoying the way it is. At least, it works for now.

I guess I really need to buy an AutoProm now to implements that custom protocol for data logging on APU1. I will see what I can do about that :)

I don't have anything else to test specifically, but if you run into any other issues, let me know. Thanks for your testing, much appreciated.

**EagleMark** · 06-15-2014

Originally Posted by Scrufdog

For datalogging only it's set to Bypass and Open, the open setting may change per ecu, older ones require 10k for datalogging only.

Very few need 10k to data log and some only need it to get data flowing! For others it will data log with switch set to 10k but data is skewed, it changes RPM and spark for diagnostic purposes!

HTH!

The 16197427, when I use my AutoProm both switches are in... as a matter of fact both switches are in for almost everything I do!

**Scrufdog** · 06-15-2014

I did notice that when trying to change buffer addresses in programming mode, if you try to change the address in hex, it only gives you a 0-9 keyboard, no way to enter A-F. Might be a device specific thing. May also be a flag or something in the code that requests a specific type of keyboard, instead of a full qwerty keyboard.

**3400tZ** · 06-15-2014

Good catch! You're right, it was the code requesting for a specific type of keyboard. I changed:

android:inputType="number"

For:

android:digits="0123456789ABCDEFabcdefx"
android:inputType="text"

And it seems good now. The fix will be in the next version.

Thanks!