Pages: 1 [2] 3 4
Author Topic: failed to read test echo from FTDI device ?  (Read 49728 times)
bigazz
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 21


« Reply #15 on: October 18, 2012, 05:16:51 AM »

Im still waiting for my blue cable to arrive. Must be on the slow boat from china Sad
Logged
professor
Sr. Member
****

Karma: +25/-0
Offline Offline

Posts: 409



« Reply #16 on: October 19, 2012, 04:29:19 AM »

Have you tried all usb ports?
Perhaps your laptop after short time goes into some kind of power save mode and disables usb power?
« Last Edit: October 19, 2012, 05:37:48 AM by professor » Logged

Seat Ibiza MK4 Cupra 1.8t 20V, stg3.
"Those 1.8T 20V machines are really tough" ©
chlippo
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 22


« Reply #17 on: November 11, 2012, 11:44:08 AM »

I am having the Same problem, I am not able to flash the ecu with the map provided by a member here.

I tried two cables i have and here are the messages i got when trying to connect:

First Cable:
Failed to read test echo from ftdi on Ross Tech cable

Second Cable:
Failed to setup ftdi

Car is a 2001 Audi S3 AMK, and I am using windows 7
Logged
professor
Sr. Member
****

Karma: +25/-0
Offline Offline

Posts: 409



« Reply #18 on: November 11, 2012, 12:31:56 PM »

Ross tech cable should be n dump moe to work with nefmoto tool.
Also choose the latest ftdi drivers to install for your cables, try in different usb ports and always double check baud rates  before flashing (prefer the 52800 speed).
Logged

Seat Ibiza MK4 Cupra 1.8t 20V, stg3.
"Those 1.8T 20V machines are really tough" ©
chlippo
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 22


« Reply #19 on: November 12, 2012, 10:56:06 PM »

Ross tech cable should be n dump moe to work with nefmoto tool.
Also choose the latest ftdi drivers to install for your cables, try in different usb ports and always double check baud rates  before flashing (prefer the 52800 speed).

It was set in dump mode, correct ftdi drivers. No matter what i do it wont work. I have read pretty much all the threads on this forum that are connected to my problem and still no solution.

My Ross tech is not original.

I guess i will try to get a blue cable from the recommended sellers, uninstall everything that is related to vcds from my pc, and try again.

All i need is the cable, ftdi drivers, and nefmoto software, right?
Logged
professor
Sr. Member
****

Karma: +25/-0
Offline Offline

Posts: 409



« Reply #20 on: November 13, 2012, 01:16:13 AM »

And the help of God of course.
Logged

Seat Ibiza MK4 Cupra 1.8t 20V, stg3.
"Those 1.8T 20V machines are really tough" ©
AARDQ
Sr. Member
****

Karma: +11/-0
Offline Offline

Posts: 338


« Reply #21 on: November 13, 2012, 11:33:00 AM »

Just to verify, you are closing VCDS after setting to dumb mode and before opening nefmoto?

You likely cannot have drivers for blue cable and Hex Can installed at the same time.  I couldn't, anyway.  After I made that mistake I had to blow out all drivers and only put one set back (for Hex Can in my case).

Logged
nyet
Administrator
Hero Member
*****

Karma: +604/-166
Offline Offline

Posts: 12234


WWW
« Reply #22 on: November 13, 2012, 01:08:02 PM »

Also, maybe borrow a known good ecu you can try to bench flash? You mentioned the AA is a bit finicky. Are you doing this in car, or on the bench?

If in car

1) try disconnecting the cluster
2) try a lower baud rate
Logged

ME7.1 tuning guide (READ FIRST)
ECUx Plot
ME7Sum checksum checker/corrrector for ME7.x

Please do not ask me for tunes. I'm here to help people make their own.

Do not PM me technical questions! Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your experience.
chlippo
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 22


« Reply #23 on: November 13, 2012, 01:17:53 PM »

I am doing this on the car via obdII. Ecu in the car

I always test the cable in dumb mode in vcds then close vcds and try to flash.

Maybe it is because I had more than one driver installed on this computer.

I never select baud speed, i usually leave it at unspecified baud. And i am using version 1.9.3.2
Logged
AARDQ
Sr. Member
****

Karma: +11/-0
Offline Offline

Posts: 338


« Reply #24 on: November 13, 2012, 01:37:52 PM »


For reference given that my Hex Can setup works, I'm using the VCP drivers (with VCP enabled - -default is not enabled) from the Ross-Tech site http://www.ross-tech.com/vag-com/usb/virtual-com-port.html  Not to say that the newer drivers from the ftdi Web site http://www.ftdichip.com/Drivers/VCP.htm don't work; just that these work for me.
Logged
professor
Sr. Member
****

Karma: +25/-0
Offline Offline

Posts: 409



« Reply #25 on: November 14, 2012, 01:05:48 AM »

Forgot to mention that i had same problem while battery on my laptop and ac adapter connected to 12V->220V converter.
When ac adapter removed and laptop was fed only via battery, ftdi was recognized without problem.
Logged

Seat Ibiza MK4 Cupra 1.8t 20V, stg3.
"Those 1.8T 20V machines are really tough" ©
papasound
Jr. Member
**

Karma: +1/-1
Offline Offline

Posts: 29


« Reply #26 on: February 19, 2013, 03:16:40 PM »

Exactly same problem here, setup:

Original HEX+CAN USB Ross tech 11.11.3,
Audi TT 1.8T
ECU ME7.5


Tried NefMoto 1.6, 1.8, 1.9.3.2
With all above tried FTDI VCP drivers (VCP enabled), Rosstech VCP drivers (VCP enabled)

intelligent mode unchecked, saved, vcds closed,

tried all possible BAUDs, all possible modes, actually there has left very little i haven't tried
no luck to connect to ecu at all, not a sign, tried select map layout before connecting too
always seeing same log:

19/Feb/2013 10:07:50.473: LOG: Opened NefMoto VW Audi ME7 Flasher Logger 1.9.3.2
19/Feb/2013 10:08:04.962: LOG: Setting Address: 0x01 KeyByte1: 0x6B KeyByte2: 0x0F
19/Feb/2013 10:08:05.007: LOG: Opened FTDI device.
19/Feb/2013 10:08:05.008: LOG: FTDI device info - Description: Ross-Tech HEX-USB Serial Number: RT000001 Device Type: FT_DEVICE_232R ID: 0x403FA30 Device Flags: 0x0
19/Feb/2013 10:08:05.008: LOG: FTDI ChipID DLL is loaded, checking chip ID...
19/Feb/2013 10:08:05.011: LOG: FTDI device chip ID: 0x829146C5
19/Feb/2013 10:08:06.041: USER: Failed to read test echo from FTDI device.
19/Feb/2013 10:08:26.692: LOG: Closing FTDI device.

Please help, i'm quite clueless at the moment
Logged

Friends will never leave friends on stock.
AARDQ
Sr. Member
****

Karma: +11/-0
Offline Offline

Posts: 338


« Reply #27 on: February 19, 2013, 05:33:20 PM »

You aren't even getting to the point where Nef will try to connect to the ECU.  Nef isn't communicating with the cable in essence.  Does VCDS work?

One thing you might try is connecting to the ECU using VCDS, look at DTCs or something, then close out of VCDS (need to be out of it before connecting with anything else, Nefmoto included) and then try Nefmoto.
Logged
papasound
Jr. Member
**

Karma: +1/-1
Offline Offline

Posts: 29


« Reply #28 on: February 19, 2013, 07:00:55 PM »

VCDS works just fine, there is couple of DTCS, Headlight motors, Level sensor
AND one that maybe blocking access is 'Incorrect Key Programming',  it appeared when i lost my keys
and had service guy to program new keys, it can't be deleted though
Logged

Friends will never leave friends on stock.
AARDQ
Sr. Member
****

Karma: +11/-0
Offline Offline

Posts: 338


« Reply #29 on: February 19, 2013, 08:41:34 PM »

VCDS works just fine, there is couple of DTCS, Headlight motors, Level sensor
AND one that maybe blocking access is 'Incorrect Key Programming',  it appeared when i lost my keys
and had service guy to program new keys, it can't be deleted though

I don't think so.  The FTDI echo message means that Nefmoto isn't playing nice with the cable.  Wish I could help more, except to suggest removing the drivers, reboot and try again.  Do you have another laptop you can try?
Logged
Pages: 1 [2] 3 4
  Print  
 
Jump to:  

Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Page created in 0.022 seconds with 16 queries. (Pretty URLs adds 0.001s, 0q)