EFILive V4 EVAL and ALDL - USB cable problems.

[Daniele84]

Hello

I have a problem with my ALDL-USB cable

The cable is this:

http://www.aldlcable.com/sc/details.asp?item=aldlobd1u

This cable is for Daewoo Lanos 1.6 with ALDL connector.

but when open EFILive V4 EVAL and push on AUTOMATICALLY DETECT CHATTER or push of any MACRO the programm crash, why ? Have tried DAEWOO.XML, LANOS.XML and NUBIRA.XML setting, but the program crash ever.

The cable is settings on COM5, i'm us Windows XP SP3.

Thanks.

[Blacky]

I don't know why the software would crash, try re-installing it (sorry that's the only thing I can think of right now).

Regards
Paul

[Blacky]

Have you set up the EFILive V4 software to look for the cable on COM 5?

Regards
Paul

[Daniele84]

the cable is already set to COM5

i trie to com1 to com8, but nothing.

but when start a macro and key is in IGNITION position and immediately turn the key of ON position, appears this:

28.57.145: Initialising...
28.58.786: Opening COM5 8228,8,N,1
28.59.070: Ready.
29.33.143: Start macro: Get engine data and DTCs: DATADTC
29.33.143: Send: $F4,$57,$01,$00,$B4
29.37.142: Error: Max232 echo: $40,$57,$53,$5B,$BB did not match command: $F4,$57,$01,$00,$B4
29.37.158: Recv: $41,$56,$AA,$BF

and program crash.

[Daniele84]

tried to other different pc with OS windows xp and seven, but don't work. im try setting the cable on the com1 to com8, the program crash ever.

[Blacky]

Try un-checking the Max232 Echo option (shown in the image in my previous post).

Regards
Paul

[Daniele84]

for me the problem is the cable, but i read on the ftdi-chip site is possible change the I/O option of the cable with mprog 3.5, is possible ?

i tried to un-checking max232 echo but the proram crash. sigh sob.

[Blacky]

If it crashes when you select the "detect chatter" option then there is probably a serious problem with the V4 software. Maybe it has been corrupted somehow or a dll is faulty or the wrong version. I can't think of anything that would cause it to crash when it is just detecting chatter.

Maybe try uninstalling, delete the original download file and re-download the V4 software from our web site. Then delete the C:\Program Files\EFILive\V4 folder and re-install.

Also, when you select the detect chatter option, does anything get displayed in the V4 console before it crashes? If so a screen shot of that would be useful.

Even more useful would be if you could turn on View->Show I/O before attempting to detect chatter. That will show more detailed information about what is happening.

Regards
Paul

[Daniele84]

ok problem solved in part, the problem is the cable, have install mprog 3.5 and reflash the cable with correct settings now the macro work perfectly, efilive recognizes the cable, in the macro window when push on "automatically detect chatter" appears "detected interface ok" in green after the program write "check interface vehicle" and program crash, but the macro work however.

[southaussie]

what were the correct settings? when i load mprog 3.5 up it says i have 1 blank eeprom ~