Connection issue cable will not work with eehack

[hbomb2k]

I am a new tuner and I have really been looking forward to getting into the EEHack and getting to work. Unfortunately I have an error.

Here is my log:

EEHack Version 4.70
Current OS : Windows 10
Built with THROTTLE_MS=2
Opened serial port COM7 Description USB Serial Port MFR FTDI
START SILENCE ROUTINE
SERIAL: WAITED_TOO_LONG in serial_read_packet
SERIAL: WAITED_TOO_LONG in serial_read_packet
START SILENCE ROUTINE
SERIAL: WAITED_TOO_LONG in serial_read_packet
SERIAL: WAITED_TOO_LONG in serial_read_packet
START SILENCE ROUTINE
SERIAL: WAITED_TOO_LONG in serial_read_packet
SERIAL: WAITED_TOO_LONG in serial_read_packet
START SILENCE ROUTINE
SERIAL: WAITED_TOO_LONG in serial_read_packet
SERIAL: WAITED_TOO_LONG in serial_read_packet
START SILENCE ROUTINE
SERIAL: WAITED_TOO_LONG in serial_read_packet
SERIAL: WAITED_TOO_LONG in serial_read_packet
START SILENCE ROUTINE
SERIAL: WAITED_TOO_LONG in serial_read_packet
SERIAL: WAITED_TOO_LONG in serial_read_packet
START SILENCE ROUTINE
SERIAL: WAITED_TOO_LONG in serial_read_packet
SERIAL: WAITED_TOO_LONG in serial_read_packet

Not very experienced with serial communication protocol so I don't really have much to add.

Other than that my cable works perfect with Scan9495

Really excited to get into tuning but I really need a hand figuring this out. Thank you all.

[babywag]

go into settings and check com port selection

on all my laptops eehack defaults to com1
everytime i use eehack i have to change it to the correct com port.
usually com3 for my usb aldl adapter

[hbomb2k]

go into settings and check com port selection

on all my laptops eehack defaults to com1
everytime i use eehack i have to change it to the correct com port.
usually com3 for my usb aldl adapter

Sorry forgot to mention that I am certain I have the correct com selected.

Unless EEhack somehow lists it’s coms differently than Scan9495

[hbomb2k]

I figured it out!

My cable has a FT232BL chipset, this chipset will work with Scan9495 but not with flashing programs like TunerCat (and I am assuming EEhack)

What you need is a FT232RL chipset, this will work with Scan9495 AND flashing programs like TunerCat, EEhack, etc.

Per this post: http://gmlongroof.4umer.com/t14451-building-a-diy-aldl-cable-for-94-95-lt1-cars


This chipset distinction is the key to getting a properly functioning cable.

[steveo]

that's great you figured it out, i should look into WHY it does that

i'd never heard of the FT232BL

it has nothing to do with being a 'flashing program', i can promise you that, the serial comm requirements are identical for logging and flashing.

garydoug's scan9495 pretty much just uses visual basic's built in serial library, it doesn't really know what a serial port is or how it works on a low level

eehack uses QT's qserialport library, same difference, it doesn't really know what's going on beyond sending/recieving/opening the port. i used this layer so it'd work on any operating system that works with qserialport, including linux

i'm pretty sure that tunercat is written in visual c++ but i've never looked into it (just seems that way) and it's pretty closed source, so god knows what he's using

so basically we're all using an abstraction layer, and scan9495 uses one that supports that chip, and we don't. whats up with that...? we can only assume visual basic's serial layer knows something that ours does not

[steveo]

hey there mr. hbomb, i just had a thought

how about since this FT232BL chipset doesn't work for you anyways,

..... would you loan it to me for a few months so i can learn why it doesn't work with my software?

[hbomb2k]

PM sent!

[steveo]

pm replied, thank you for your contribution(s). i'll give it a good shot at making that chipset work with next eehack version, but it might take modifications to QT's serial layer

[spfautsch]

Interesting topic - I have to wonder if this is the FTDI chip used in the aldlcable piece.


i'm pretty sure that tunercat is written in visual c++ but i've never looked into it (just seems that way) and it's pretty closed source, so god knows what he's using

TunerCats and JetDST are built in VB6 - I found this out a long time ago when I found the encryption library he was using (and the key) for the definition files (equivalent to an .xdf file) for Jet. I always assumed he was using the VB serial abstraction control (mscomm32.ocx) but after installing it on a vm and testing I don't think it does. I suppose it's possible he used the windows apis directly.