Pages: 1 ... 8 9 [10]
Author Topic: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2  (Read 178416 times)
slappynuts
Jr. Member
**

Karma: +0/-0
Offline Offline

Posts: 48


« Reply #135 on: April 29, 2017, 03:46:29 PM »

Anyone ever seen anything like this? 021906018m ecu.



Connected
Disabling Windows sleep mode.
Writing ECU flash memory.
ECU reports programming session preconditions have been met.
Negotiating communication timings.
Successfully changed to new communication timings.
Requesting security access.
ECU reports that security access is not supported.
Starting diagnostic session.
Successfully started diagnostic session.
Negotiating communication timings.
Disconnecting because no response was received for the Tester Present message.
Disconnected
Writing ECU flash memory failed.
100% complete.
Restoring Windows sleep mode.   
Logged
userpike
Hero Member
*****

Karma: +21/-1
Offline Offline

Posts: 757


« Reply #136 on: April 29, 2017, 06:14:11 PM »

Anyone ever seen anything like this? 021906018m ecu.



Connected
Disabling Windows sleep mode.
Writing ECU flash memory.
ECU reports programming session preconditions have been met.
Negotiating communication timings.
Successfully changed to new communication timings.
Requesting security access.
ECU reports that security access is not supported.
Starting diagnostic session.
Successfully started diagnostic session.
Negotiating communication timings.
Disconnecting because no response was received for the Tester Present message.
Disconnected
Writing ECU flash memory failed.
100% complete.
Restoring Windows sleep mode.   

Is the ECU tuned? I'm thinking there is some kind of write protection. I'm only guessing though.
Logged
slappynuts
Jr. Member
**

Karma: +0/-0
Offline Offline

Posts: 48


« Reply #137 on: April 29, 2017, 07:02:17 PM »

The odd thing is that after a couple of tries I was able to read it.   
Logged
Phil_R
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 3


« Reply #138 on: August 24, 2017, 05:19:29 PM »

I'm unable to read or write the info from a 4.2 V8 ME7.1 4D0907560H 1mb ecu, have tried on the bench as well with the same result. Previously used on a 1.8T ME7.5 and it worked perfectly. I have attached the log file below and quoted where it fails.
I have tried changing the baud timing after disconnecting and reconnecting as suggested here and pulling cluster fuse but nothing seems to help, I have tried a different V8 ME7.1 ecu with 512kb and that also will not read or write. It still connects to the ME7.5 ecu easily.

Quote
25-Aug-2017 12:43:17.000: LOG: Received message with service ID: StartDiagnosticSessionPositiveResponse
25-Aug-2017 12:43:17.019: LOG: Setting communication timings to defaults.
25-Aug-2017 12:43:17.042: LOG: Set timing parameters to defaults.
25-Aug-2017 12:43:17.056: LOG: Changed diagnostic session type to: ProgrammingSession
25-Aug-2017 12:43:17.065: LOG: ECU requesting specific baud rate: 89600
25-Aug-2017 12:43:17.076: USER: Successfully started diagnostic session.
25-Aug-2017 12:43:17.086: USER: Negotiating communication timings.
25-Aug-2017 12:43:17.096: LOG: Reading current communication timings.
25-Aug-2017 12:43:17.158: LOG: Sent message with service ID AccessTimingParameters
25-Aug-2017 12:43:19.160: LOG: Message received no replies.
25-Aug-2017 12:43:19.180: LOG: Resending message. Send attempts: 2
25-Aug-2017 12:43:19.248: LOG: Sent message with service ID AccessTimingParameters
25-Aug-2017 12:43:21.249: LOG: Message received no replies.
25-Aug-2017 12:43:21.268: LOG: Resending message. Send attempts: 3
25-Aug-2017 12:43:21.334: LOG: Sent message with service ID AccessTimingParameters
25-Aug-2017 12:43:23.336: LOG: Message received no replies.
25-Aug-2017 12:43:23.355: LOG: Failed to send message 3 times, message send failed.
25-Aug-2017 12:43:23.373: LOG: Did not receive any replies to message.
25-Aug-2017 12:43:23.391: USER: Reading ECU flash memory failed.
25-Aug-2017 12:43:23.855: LOG: Sent message with service ID TesterPresent
25-Aug-2017 12:43:25.857: LOG: Message received no replies.
25-Aug-2017 12:43:25.875: LOG: Resending message. Send attempts: 2
25-Aug-2017 12:43:25.912: LOG: Sent message with service ID TesterPresent
25-Aug-2017 12:43:26.338: LOG: User Prompt - Title: Reading ECU Flash Memory Complete Message: Reading ECU flash memory failed. Result: OK
25-Aug-2017 12:43:26.349: USER: 100% complete.
25-Aug-2017 12:43:26.404: USER: Restoring Windows sleep mode.
25-Aug-2017 12:43:27.915: LOG: Message received no replies.
25-Aug-2017 12:43:27.935: LOG: Resending message. Send attempts: 3
25-Aug-2017 12:43:27.973: LOG: Sent message with service ID TesterPresent
25-Aug-2017 12:43:29.986: LOG: Message received no replies.
25-Aug-2017 12:43:29.986: LOG: Failed to send message 3 times, message send failed.
25-Aug-2017 12:43:30.002: USER: Disconnecting because no response was received for the Tester Present message.
25-Aug-2017 12:43:30.002: USER: Disconnected
Logged
vwaudiguy
Hero Member
*****

Karma: +47/-35
Offline Offline

Posts: 1963



« Reply #139 on: August 25, 2017, 04:56:00 PM »

I'm unable to read or write the info from a 4.2 V8 ME7.1 4D0907560H 1mb ecu, have tried on the bench as well with the same result. Previously used on a 1.8T ME7.5 and it worked perfectly. I have attached the log file below and quoted where it fails.
I have tried changing the baud timing after disconnecting and reconnecting as suggested here and pulling cluster fuse but nothing seems to help, I have tried a different V8 ME7.1 ecu with 512kb and that also will not read or write. It still connects to the ME7.5 ecu easily.


Fairly sure Nef won't work with that particular ecu. Most of the clone tools (which are better in some ways) won't work either.
Logged

"If you have a chinese turbo, that you are worried is going to blow up when you floor it, then LOL."
Phil_R
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 3


« Reply #140 on: September 11, 2017, 05:03:49 PM »

Fairly sure Nef won't work with that particular ecu. Most of the clone tools (which are better in some ways) won't work either.
I've just received an ecu I bought from the Usa, it's a ME7.1.1 4D0907560AE and that reads fine so I can start trying to convert it to a manual file and rewiring the loom to suit the new ecu
Logged
milopl81
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 4


« Reply #141 on: September 22, 2017, 02:24:22 AM »

Hi
I try flash ME7.1  551F(box) and have strange situation. I flashed my ECU ang on first time on 94% i have information as below. When I press YES application try erase ECU memory one more time and then I have message "Writing ECU flash memory succeeded. Wrote 19 of 19 sectors in flash memory. Flashing time was 00:21:13. Result: OK".
For me it is not comfortable because after change something I must wait more then 20 minuts for flash two times. First always with error and second erase OK.
Do you know why ?


INFO:
Sector Erase Failed Message: Failed to erase the memory sector. The new data being flashed likely conflicts with the ECU's persistent data. The persistent ECU data can be replaced by erasing the entire flash memory before programming. If the ECU may contains a non-standard flash memory chip, it could be causing the erase to fail.

Press Yes, to erase the entire ECU flash memory and restart the flashing process.
Press No, to skip flashing this sector and continue the flashing process.
Press Cancel, to abort the flashing process.

WARNING: Only erase the entire flash memory if you have a good communication connection with the ECU. If flashing fails after erasing the entire flash memory, it is likely the ECU will no longer boot, and will have to be reflashed on the bench using boot mode. This software does NOT support boot mode.



log:
16-wrz-2017 01:50:08.894: USER: Request download to ECU succeeded.
16-wrz-2017 01:50:08.894: USER: Starting data transfer.
16-wrz-2017 01:50:08.904: LOG: Sent message with service ID TransferData
16-wrz-2017 01:50:08.974: LOG: Received message with service ID: TransferDataPositiveResponse
16-wrz-2017 01:50:08.974: USER: 94% complete.
16-wrz-2017 01:50:08.974: USER: Data transfer complete.
16-wrz-2017 01:50:08.974: USER: Requesting data transfer exit.
.................
.................
16-wrz-2017 01:50:18.007: LOG: Received message with service ID: TesterPresentPositiveReponse
16-wrz-2017 01:50:18.778: LOG: User Prompt - Title: Sector Erase Failed Message: Failed to erase the memory sector. The new data being flashed likely conflicts with the ECU's persistent data. The persistent ECU data can be replaced by erasing the entire flash memory before programming. If the ECU may contains a non-standard flash memory chip, it could be causing the erase to fail.

Press Yes, to erase the entire ECU flash memory and restart the flashing process.
Press No, to skip flashing this sector and continue the flashing process.
Press Cancel, to abort the flashing process.

WARNING: Only erase the entire flash memory if you have a good communication connection with the ECU. If flashing fails after erasing the entire flash memory, it is likely the ECU will no longer boot, and will have to be reflashed on the bench using boot mode. This software does NOT support boot mode. Result: YES
.........
.........

16-wrz-2017 02:01:46.286: LOG: Sent message with service ID TesterPresent
16-wrz-2017 02:01:46.316: LOG: Received message with service ID: TesterPresentPositiveReponse
16-wrz-2017 02:01:47.458: LOG: User Prompt - Title: Writing ECU Flash Memory Complete Message: Writing ECU flash memory succeeded. Wrote 19 of 19 sectors in flash memory.
Flashing time was 00:21:13. Result: OK
16-wrz-2017 02:01:47.458: USER: Restoring Windows sleep mode.
16-wrz-2017 02:01:47.548: USER: Disconnecting...
16-wrz-2017 02:01:47.698: LOG: Sent message with service ID StopCommunication
16-wrz-2017 02:01:47.718: LOG: Received message with service ID: StopCommunicationPositiveResponse
16-wrz-2017 02:01:47.718: USER: Disconnected
16-wrz-2017 02:01:47.758: LOG: Closing FTDI device.
16-wrz-2017 02:01:47.768: LOG: Send receive thread now terminated.
16-wrz-2017 02:02:40.124: LOG: Closing NefMoto VW Audi ME7 Flasher Logger 1.9.3.2

Logged
03GTI
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 6


« Reply #142 on: February 06, 2018, 08:09:01 PM »

Can anyone help me please i have tried everything that is in this thread and nothing has worked...i dont know what to do anymore the ECU is no my Test Bench...

wired up from another thread on this site.
im using a HEX-CAN 12.12 VCDS cable i also have tried with a 12.10 VCDS cable...and a blue one but sadly its a CH340 or something like that..the seller lied to me...but i keep getting

Could not open FTDI device
or
Failed to read test echo from FTDI device

I have made sure that Boot in dumb mode was done and saved...
the VCP drivers from both VCDS and the VCP site have been tested to no avail...
the ECU number is one that is on the "good list"

it is
06A 906 032 DL
Logged
kingnathi
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 2


« Reply #143 on: April 04, 2018, 06:24:38 PM »

This is the version 1.9.3.2 release of the NefMoto software.

Changes in this version:
-Removed Validate Memory Layout operation because flashing operations already validate the layout, and it could cause Programming Not Complete errors on some ECUs.
-Made flash writing operations only validate sector checksums after flash writing has successfully started. This prevents Invalid Checksum errors on some ECUs that would enter programming mode but refuse to allow flash writing.
-Fixed a bug with overwriting a file when saving a read flash causing the program to freeze.
-Fixed a bug with negotiating timing parameters failing on some ECU types when entering programming mode.
-Added better support for detecting supported baud rates on ECUs that don't respond to messages on unsupported baud rates.

Fast data logging can read up to 84 variables at a time with samples rates as high as 50 samples per second. The sample rate defaults to 10 samples per second. High sample rates can overload the ECU and cause communication disconnections. This same problem effects the ME7 Logger when attempting to read too many variables with sample rates that are too high. I recommend only logging the variables you are interested in at sample rate you need. The data logging method that this software and ME7 Logger use are non-standard and as such are able to overload the ECU if used irresponsibly.

You can read about the software on the wiki: http://www.nefariousmotorsports.com/wiki/index.php/NefMoto_ECU_Flashing_Software

Also make sure you have the FTDI D2XX driver installed: http://www.ftdichip.com/Drivers/D2XX.htm

Bruh. Can I please get a direct download link to this software.
Logged
nyet
Administrator
Hero Member
*****

Karma: +423/-49
Offline Offline

Posts: 9466


WWW
« Reply #144 on: April 04, 2018, 06:33:23 PM »

the msi in the first post?
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.
mdlc805
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 2


« Reply #145 on: September 03, 2018, 01:22:13 PM »

can someone help me figure out what im doing wrong. im using ross tech cable and have unchecked intellegent boot. but nefmoto still wont recognize it is connected to the car. i checked in device manager and is says the cable is working properly. ive restarted nefmoto mutliple times and disconnected the cable and reconnected it multiple times aswell. im trying to pull my ecu file so i can start logging with the me7logger.
Logged
nyet
Administrator
Hero Member
*****

Karma: +423/-49
Offline Offline

Posts: 9466


WWW
« Reply #146 on: September 03, 2018, 03:26:42 PM »

which ross tech cable?
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.
mdlc805
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 2


« Reply #147 on: September 05, 2018, 07:54:49 AM »

which ross tech cable?
Thanks for the reply. I have a hex +can cable. The one with u limited vin

Sent from my SM-N920V using Tapatalk

Logged
CTIGUY
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 1


« Reply #148 on: April 09, 2019, 08:30:32 AM »

Thanks for the reply. I have a hex +can cable. The one with u limited vin

Sent from my SM-N920V using Tapatalk



Not sure if you got a reply, but perhaps have a look at this video. They talk about disabling intelligent mode and then updating to a different drive which allows the ECU to talk to the cable. You will also need to set it to the correct comport.

https://www.youtube.com/watch?v=GIlQd5VYseo

and more information here  on the step by step installation of Neftmoto

http://nefariousmotorsports.com/forum/index.php?topic=6537.0

Hope this helps
Logged
Pages: 1 ... 8 9 [10]
  Print  
 
Jump to:  

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