Pages: [1]
Author Topic: Re: "failed to read test echo from FTDI device" error  (Read 1990 times)
EuroXs4
Full Member
***

Karma: +15/-1
Offline Offline

Posts: 171


« on: December 17, 2016, 09:43:01 PM »

I got the nefmoto to work.But now have a different issue.Cant connect to ecu with slow init.No matter what baud rate I use on the bench.
Logged
EuroXs4
Full Member
***

Karma: +15/-1
Offline Offline

Posts: 171


« Reply #1 on: December 22, 2016, 05:50:07 PM »

Ok so long story short I got another ecu.But for the life of me I still can get nefmoto to read it.This is what I have now.This is being done on the bench with immo disabled.Ecu is a me7.5 8e0919518ak stock ecu.

Validated FTDI device is in dumb mode.
Disconnected
Connecting...
Starting slow init connection.
Connecting to address 0x01.
Slow init succeeded.
Switching to KWP2000 session.
Connected
Disabling Windows sleep mode.
Reading ECU flash memory.
ECU reports programming session preconditions have been met.
Negotiating communication timings.
Successfully changed to new communication timings.
Requesting security access.
Security access granted.
Starting diagnostic session.
Disconnecting because no response was received for the Tester Present message.
Disconnected
Reading ECU flash memory failed.
100% complete.
Restoring Windows sleep mode.
Logged
nyet
Administrator
Hero Member
*****

Karma: +339/-40
Offline Offline

Posts: 7953


WWW
« Reply #2 on: December 22, 2016, 06:51:58 PM »

Probably not a stock flash.

Bootmode flash a stock AK file with galletto
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.
EuroXs4
Full Member
***

Karma: +15/-1
Offline Offline

Posts: 171


« Reply #3 on: December 24, 2016, 06:48:04 AM »

Already did.Then tried with nefmoto.Same thing.No change.The ecu I used I know was bone stock before i reflashed it with galletto.I cant communicate with the ecu even with vcds.Which leads me to believe either its bricked or stuck in bootmode??However when reading and writing in bootmode.No issues at all.Works fine.

Is it possible the ecu is stuck in bootmode???I read the flash with galletto.I DID NOT short pin 24 to ground.Just hooked up the ecu on the bench and read.Attached below.



« Last Edit: December 24, 2016, 09:37:43 AM by EuroXs4 » Logged
nyet
Administrator
Hero Member
*****

Karma: +339/-40
Offline Offline

Posts: 7953


WWW
« Reply #4 on: December 24, 2016, 11:15:53 AM »

That file is not stock

Code:
$ md5sum.exe bins/8E0909518AK-0003.bin 518AKnc.bin
de0521f258855661f27284d17dbc8907 *bins/8E0909518AK-0003.bin
bc80e7ef0e4cc918d7308be0edfd110f *518AKnc.bin
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.
Pages: [1]
  Print  
 
Jump to:  

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