Usb aldl cable "issues"

Lets begin with saying the uber-easy usb aldl is just that. Thanks to robertsaar for his work and input on the subject.

Now the issue(s) at hand are as follows.

1. Driver driver driver.
Connection seems to be inconsistent using older ftdi chips with later drivers. Usually requires an uninstall and reinstallation of the desired driver.

2. Found an odd issue concerning the use of my inverter plugged into my laptop. Would not connect with inverter making power, connect with it u plugged. Now it doesnt do this on every vehicle but just a thought if u run into this situation.

3. Comm ports comm ports comm ports.

It seems my setup likes com 3. But, when i verify cable on com 3 it doesnt recognize/find the cable. However, if i change the setting to com 4 it finds the cable but will not connect. After i figured all this out it works well oveall.

For the price of admission this is the way to go. Mine isnt necssarily the prettiest but several revisions later it is in a "box" with adequate cable lengt and it works quite well 95% of the time.

Thanks for reading my rant today. Stay tuned for more missdventures ;)

i've never had an issue with an inverter being active... that is the only way i log, unless i'm on a ~5 minute trip. could your inverter be noisy enough to prevent a solid connection?

Some inverters don't have good ooutput filtering and will cause issues like this, especillay where there are two paths for ground, the one through the inverter, and the other through the ALDL cable. One needs to float, and can be difficult to do sometimes.

I assumed it was due to the ground path/emi. No biggie as its only on my friends truck. ;)

Eaglemark, the xdf for '299 $99 leaves a bit to be desired. Make this clear i am not bashing u or whoever put that xdf together. Just stating my opinion. ;)

i like the 7747 aside from the slow baud. Its easy to tune, cheap and plentiful ;)

you know what, tunerpro RT needs to have a built in libftdi option, since most usb serial interfaces these days are FTDI anyway

i've done a lot of work with libftdi now, and it's slick, i think every program that does serial should be able to select between ordinary serial and libftdi.

- 100x easier to program and debug
- uses direct usb i/o to the ftdi chip instead of trying to be a windows serial device
- no compatibility issues with any ftdi interface
- automatic detection of connected ftdi interfaces, no com port selection, etc
- select arbitrary baud rates (like 8192) with no problems

Quote:

---

Originally Posted by buddrow

Eaglemark, the xdf for '299 $99 leaves a bit to be desired. Make this clear i am not bashing u or whoever put that xdf together. Just stating my opinion. ;)

---

It's a basic that came from? What I was trying to say is there is a dissasembly that can be used to make the XDF better. Then using all of TunerPros features it could be as good if not better then 7747.

I have literally 100s of hours into the $42 XDF, it was just as bad as the 299 when I started.

Quote:

---

Originally Posted by steveo

you know what, tunerpro RT needs to have a built in libftdi option, since most usb serial interfaces these days are FTDI anyway

i've done a lot of work with libftdi now, and it's slick, i think every program that does serial should be able to select between ordinary serial and libftdi.

- 100x easier to program and debug
- uses direct usb i/o to the ftdi chip instead of trying to be a windows serial device
- no compatibility issues with any ftdi interface
- automatic detection of connected ftdi interfaces, no com port selection, etc
- select arbitrary baud rates (like 8192) with no problems

---

Suggest it on the TunerPro forum!

Eaglemark, i may delve into the assembly for 299 at some point but right now im takin the easy way out with the 7747 and $42 you have so generously put together. ;) i like the $42 xdf and my only complaint is the slow baud/data refresh rate. I appreciate your hard work as it has made this endeavor easier for me.

Yes, a direct to FTDI interface option for connection would be VERY helpful. I'm having a connection issue with an AVT-852 interface and XP64, and Windows 7. I'm wondering if anyone else is using a 64 bit OS with an FTDI driver successfully. See the thread here:

http://www.gearhead-efi.com/Fuel-Inj...-issues-64-bit

Thanks

i have never had problems of any sort in any software with an ftdi device on a 64 bit os using whatever driver i downloaded from the cable mfr, whether it be linux, windows, libftdi, generic serial, whatever.

i can't remember off the top of my head which ftdi chipset i have in my cable, though.

it's a premade aldlcables.com jobby.

Thanks for the response steveo. At least that's one data point for 64 bit working.

I have quite a few FTDI based devices that work on my 64 bit systems (I use 64 bit exclusively).

I have not used the cable you have though.

I am currently using a win xp machine as my tuner/datalogger. Havent tried it on win 7 64 bit yet. From what i can tell about the chip on my device is its an older chip i forget the vintage at the moment and since its semi-permanently mounted in my truck...;) but overall I am very pleased with the ftdi chip. Just noting a few issues, which seem to be common, in my own way.

Mark, i will look i think i may have the 299 disassembly to take a look at. Ill be off the entire week of Christmas so i will have a little free time. But no promises. I do have a 6 yr okd daughter that commands a large portion of my time so we'll see lol.

Anywho, just my rant for the moment. Thanks for reading and stay tuned for the future adventures of Tunerman lol