NefMoto

Technical => NefMoto Software => Topic started by: Tony@NefMoto on July 04, 2012, 10:43:38 PM



Title: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: Tony@NefMoto on July 04, 2012, 10:43: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

[ed] Please see http://nefariousmotorsports.com/forum/index.php?topic=12861.0title= - nyet


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: nyet on July 05, 2012, 01:14:52 PM
If you see "Programming Not Finished"  P1681 or 18089 you may have a buggy ECU software version (generally ME7.1.1 and possibly ME7.5)

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

Currently known bad part numbers:

4Z7907551AA
4Z7907551S
4B0906018DQ?
8E0909518AM?

Please PM me or post if you know of others.

You should not see if if your ECU is ME7.1


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: nyet on July 06, 2012, 12:52:51 PM
Success. Uninstalled everything, including vcds.

set devmgr_show_nonpresent_devices=1

Went to manage devices, deleted ALL unused usb drivers

rebooted

reinstalled latest ftdi drivers (2.08.24)

rebooted

reinstalled nefmoto 1.9.3.2

backed down to 52800 baud (which is the setting on my xp laptop)

connected slow init

success.

Haven't tried 124800 baud yet. I think tony mentioned the baudrate shouldn't affect download, but perhaps there is something about negotiating the connection that is timing sensitive.


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: Tony@NefMoto on July 06, 2012, 03:07:00 PM
Let me know when you try 124800 baud.


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: nyet on July 06, 2012, 07:34:23 PM
Yup. 124800 baud is the source of the problem.

The thing is, in order for it to work again (after failing at 124800), I have to cycle both the ecu and close/restart the program, then use 52800 baud.

I never tried that before, because init never fails, even if you don't restart the program.


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: EnIgMa on July 07, 2012, 03:00:49 PM
Will be there any chance to use it with an Me7 on a fiat car?
In my case a Me7.9.10

if not, can you please explain in two words what's the difference from a me7 audi/vw and others manufacters?

thank you  :)


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: pusher on July 12, 2012, 01:20:18 PM
Hi! I am trying to Full Read flash on an ECU I got from a scrap yard.  I have built a desktop flashing setup which worked fine to disable the immobilizer,  read into it with VCDS and Galletto in boot mode, but I cannot get NefMoto to work.  I am new to working with ECU's and I am not sure if NefMoto should work using KWP2000 on a desktop setup?  Or if it is not working for some other reason,  I have only got NefMoto to work once with a Full Flash Read and that was in my friends S3 with his original ECU.  Log from reading into the ECU on the desk, I know the ECU works as it will run and drive a S3.

Code:
12/Jul/2012 08:56:31.860: LOG: Successfully read ECU identification information
12/Jul/2012 08:56:31.863: USER: 100% complete.
12/Jul/2012 08:56:31.874: USER: Read 4 ECU info entries:
12/Jul/2012 08:56:31.894: USER: 0x92, System Supplier ECU Hardware Number: 0261208221
12/Jul/2012 08:56:31.900: USER: 0x94, System Supplier ECU Software Number: 1037367220
12/Jul/2012 08:56:31.904: USER: 0x9B, Calibration Date: 1ML906032A  , 0001, 0x0000290E, 0x00000000, 0x0000, 1.8l R4/5VT    ,     
12/Jul/2012 08:56:31.910: USER: 0x9C, Calibration Equiment Software Number: 0x00000000
12/Jul/2012 08:56:31.914: USER: Restoring Windows sleep mode.
12/Jul/2012 08:56:34.339: LOG: Sent message with service ID TesterPresent
12/Jul/2012 08:56:34.356: LOG: Received message with service ID: TesterPresentPositiveReponse
12/Jul/2012 08:56:36.843: LOG: Sent message with service ID TesterPresent
12/Jul/2012 08:56:36.862: LOG: Received message with service ID: TesterPresentPositiveReponse
12/Jul/2012 08:56:38.240: LOG: User Prompt - Title: Confirm Full Read ECU Flash Memory Message: If you are ready to read, confirm the following things:
1) You have loaded a valid memory layout for the ECU.
2) The engine is not running.
Note: Some non-standard flash memory chips may prevent reading the flash memory.

Click OK to confirm, otherwise Cancel. Result: OK
12/Jul/2012 08:56:38.245: USER: Disabling Windows sleep mode.
12/Jul/2012 08:56:38.256: USER: Reading ECU flash memory.
12/Jul/2012 08:56:38.280: LOG: Reading ECU identification option: 0x9C
12/Jul/2012 08:56:38.284: LOG: Sent message with service ID ReadECUIdentification
12/Jul/2012 08:56:38.305: LOG: Received message with service ID: ReadECUIdentificationPositiveResponse
12/Jul/2012 08:56:38.307: LOG: Read ECU identification option: 0x9C
12/Jul/2012 08:56:38.310: LOG: Successfully read ECU identification information
12/Jul/2012 08:56:38.315: USER: ECU reports programming session preconditions have been met.
12/Jul/2012 08:56:38.318: USER: Negotiating communication timings.
12/Jul/2012 08:56:38.320: LOG: Reading current communication timings.
12/Jul/2012 08:56:38.323: LOG: Sent message with service ID AccessTimingParameters
12/Jul/2012 08:56:38.347: LOG: Received message with service ID: AccessTimingParametersPositiveResponse
12/Jul/2012 08:56:38.349: LOG: Setting communication timing to defaults.
12/Jul/2012 08:56:38.353: LOG: Sent message with service ID AccessTimingParameters
12/Jul/2012 08:56:38.371: LOG: Received message with service ID: AccessTimingParametersPositiveResponse
12/Jul/2012 08:56:38.373: LOG: Reading current communication timings.
12/Jul/2012 08:56:38.377: LOG: Sent message with service ID AccessTimingParameters
12/Jul/2012 08:56:38.427: LOG: Received message with service ID: AccessTimingParametersPositiveResponse
12/Jul/2012 08:56:38.429: USER: Successfully changed to new communication timings.
12/Jul/2012 08:56:38.432: USER: Requesting security access.
12/Jul/2012 08:56:38.435: LOG: Sent message with service ID SecurityAccess
12/Jul/2012 08:56:38.472: LOG: Received message with service ID: NegativeResponse
12/Jul/2012 08:56:38.475: LOG: Received negative response for service ID: SecurityAccess, with response code: GeneralReject
12/Jul/2012 08:56:38.478: USER: ECU reports that security access request was rejected.
12/Jul/2012 08:56:38.481: LOG: Starting ProgrammingSession diagnostic session with 124800 baud rate.
12/Jul/2012 08:56:38.483: USER: Starting diagnostic session.
12/Jul/2012 08:56:38.486: LOG: Sent message with service ID StartDiagnosticSession
12/Jul/2012 08:56:38.532: LOG: Received message with service ID: NegativeResponse
12/Jul/2012 08:56:38.535: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending
12/Jul/2012 08:56:38.574: LOG: Received message with service ID: NegativeResponse
12/Jul/2012 08:56:38.577: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending
12/Jul/2012 08:56:38.614: LOG: Received message with service ID: NegativeResponse
12/Jul/2012 08:56:38.616: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending
12/Jul/2012 08:56:38.654: LOG: Received message with service ID: NegativeResponse
12/Jul/2012 08:56:38.656: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending
12/Jul/2012 08:56:38.694: LOG: Received message with service ID: NegativeResponse
12/Jul/2012 08:56:38.696: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending
12/Jul/2012 08:56:48.487: LOG: Sent message with service ID TesterPresent
12/Jul/2012 08:56:50.490: LOG: Message received no replies.
12/Jul/2012 08:56:50.492: LOG: Resending message. Send attempts: 2
12/Jul/2012 08:56:50.495: LOG: Sent message with service ID TesterPresent
12/Jul/2012 08:56:52.497: LOG: Message received no replies.
12/Jul/2012 08:56:52.499: LOG: Resending message. Send attempts: 3
12/Jul/2012 08:56:52.501: LOG: Sent message with service ID TesterPresent
12/Jul/2012 08:56:54.503: LOG: Message received no replies.
12/Jul/2012 08:56:54.505: LOG: Failed to send message 3 times, message send failed.
12/Jul/2012 08:56:54.507: USER: Disconnecting because no response was received for the Tester Present message.
12/Jul/2012 08:56:54.509: USER: Disconnected
12/Jul/2012 08:56:54.521: USER: Reading ECU flash memory failed.
12/Jul/2012 08:56:54.531: LOG: Closing FTDI device.
12/Jul/2012 08:56:54.536: LOG: Send receive thread now terminated.
12/Jul/2012 08:56:55.593: LOG: User Prompt - Title: Reading ECU Flash Memory Complete Message: Reading ECU flash memory failed. Result: OK
12/Jul/2012 08:56:55.596: USER: 100% complete.
12/Jul/2012 08:56:55.603: USER: Restoring Windows sleep mode.

It fails shortly after saying "ECU reports that security access request was rejected."

Using a Ross-Tech HEX-USB cable in dumb mode.  Any help or advice would be greatly appreciated.


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: pvl on July 15, 2012, 06:00:12 AM
@ pusher:

use KWP2000+ interface and the specific ME7edition software from AMT cartech, if you want to read the ecu on the bench, without opening it up.
Galletto is a last resort, using bootmode. Not nescessary.

Nefmoto mainly fails with ME7.5 ecu's on the bench.

Cheers,

PvL


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: passuff on July 25, 2012, 12:18:25 PM
I tried to read "4B0 907 551 G" (29f800bb) ECU in Boot Mode but it failed. After that I tried over OBD and it worked.
Here is the log:

Code:
25.Jul.2012 09:03:36.640: LOG: FTDI device info - Description: FT232R USB UART Serial Number: A600K3R4 Device Type: FT_DEVICE_232R ID: 0x4036001 Device Flags: 0x0
25.Jul.2012 09:03:36.640: LOG: FTDI ChipID DLL is loaded, checking chip ID...
25.Jul.2012 09:03:36.656: LOG: FTDI device chip ID: 0x7D9A67C5
25.Jul.2012 09:03:36.687: LOG: Starting send receive thread.
25.Jul.2012 09:03:36.687: LOG: Send receive thread now started.
25.Jul.2012 09:03:36.687: USER: Disconnected
25.Jul.2012 09:03:36.703: USER: Connecting...
25.Jul.2012 09:03:36.718: USER: Starting bootstrap loader upload.
25.Jul.2012 09:03:36.734: USER: Sent bootstrap init zero byte.
25.Jul.2012 09:03:36.734: USER: Received device ID response for init zero byte.
25.Jul.2012 09:03:36.765: USER: Successfully uploaded bootstrap loader.
25.Jul.2012 09:03:36.765: USER: Received bootstrap loader started status message.
25.Jul.2012 09:03:36.765: USER: Starting upload of bootmode runtime.
25.Jul.2012 09:03:36.765: USER: Uploaded bootmode runtime data.
25.Jul.2012 09:03:36.765: USER: Sent baud rate detection byte.
25.Jul.2012 09:03:37.781: USER: Bootmode runtime upload failed. Failed to receive baud rate detection response message.
25.Jul.2012 09:03:37.781: USER: Disconnected
25.Jul.2012 09:03:37.796: USER: Connecting...
25.Jul.2012 09:03:37.812: USER: Starting bootstrap loader upload.
25.Jul.2012 09:03:37.828: USER: Sent bootstrap init zero byte.
25.Jul.2012 09:03:40.828: USER: Sent bootstrap init zero byte.
25.Jul.2012 09:03:43.828: USER: Sent bootstrap init zero byte.
25.Jul.2012 09:03:46.828: USER: Bootstrap loader upload failed. Failed to receive device ID response for init zero byte.
25.Jul.2012 09:03:46.828: USER: Disconnected
25.Jul.2012 09:03:46.859: USER: Connecting...
25.Jul.2012 09:03:46.875: USER: Starting bootstrap loader upload.
25.Jul.2012 09:03:46.875: USER: Sent bootstrap init zero byte.
25.Jul.2012 09:03:49.890: USER: Sent bootstrap init zero byte.
25.Jul.2012 09:03:51.890: USER: Sent bootstrap init zero byte.
25.Jul.2012 09:03:54.890: USER: Bootstrap loader upload failed. Failed to receive device ID response for init zero byte.
25.Jul.2012 09:03:54.890: USER: Disconnected
25.Jul.2012 09:03:54.906: LOG: Closing FTDI device.
25.Jul.2012 09:03:54.921: LOG: Send receive thread now terminated.
25.Jul.2012 09:04:38.796: LOG: Opened FTDI device.
25.Jul.2012 09:04:38.796: LOG: FTDI device info - Description: FT232R USB UART Serial Number: A600K3R4 Device Type: FT_DEVICE_232R ID: 0x4036001 Device Flags: 0x0
25.Jul.2012 09:04:38.796: LOG: FTDI ChipID DLL is loaded, checking chip ID...
25.Jul.2012 09:04:38.796: LOG: FTDI device chip ID: 0x7F0B3CF1
25.Jul.2012 09:04:38.828: LOG: Starting send receive thread.
25.Jul.2012 09:04:38.828: LOG: Send receive thread now started.
25.Jul.2012 09:04:38.843: USER: Disconnected
25.Jul.2012 09:04:38.843: USER: Connecting...
25.Jul.2012 09:04:38.859: USER: Starting bootstrap loader upload.
25.Jul.2012 09:04:38.875: USER: Sent bootstrap init zero byte.
25.Jul.2012 09:04:38.875: USER: Received device ID response for init zero byte.
25.Jul.2012 09:04:38.906: USER: Successfully uploaded bootstrap loader.
25.Jul.2012 09:04:38.906: USER: Received bootstrap loader started status message.
25.Jul.2012 09:04:38.906: USER: Starting upload of bootmode runtime.
25.Jul.2012 09:04:38.906: USER: Uploaded bootmode runtime data.
25.Jul.2012 09:04:38.921: USER: Sent baud rate detection byte.
25.Jul.2012 09:04:39.921: USER: Bootmode runtime upload failed. Failed to receive baud rate detection response message.
25.Jul.2012 09:04:39.921: USER: Disconnected
25.Jul.2012 09:04:39.937: USER: Connecting...
25.Jul.2012 09:04:39.953: USER: Starting bootstrap loader upload.
25.Jul.2012 09:04:39.953: USER: Sent bootstrap init zero byte.
25.Jul.2012 09:04:42.953: USER: Sent bootstrap init zero byte.
25.Jul.2012 09:04:44.968: USER: Sent bootstrap init zero byte.
25.Jul.2012 09:04:46.968: USER: Bootstrap loader upload failed. Failed to receive device ID response for init zero byte.
25.Jul.2012 09:04:46.968: USER: Disconnected
25.Jul.2012 09:04:46.984: USER: Connecting...
25.Jul.2012 09:04:47.000: USER: Starting bootstrap loader upload.
25.Jul.2012 09:04:47.015: USER: Sent bootstrap init zero byte.
25.Jul.2012 09:04:50.015: USER: Sent bootstrap init zero byte.
25.Jul.2012 09:04:53.015: USER: Sent bootstrap init zero byte.
25.Jul.2012 09:04:55.187: USER: Received device ID response for init zero byte.
25.Jul.2012 09:04:56.187: USER: Successfully uploaded bootstrap loader.
25.Jul.2012 09:04:57.187: USER: Failed to receive bootstrap loader started status message.
25.Jul.2012 09:04:57.187: USER: Disconnected
25.Jul.2012 09:04:57.218: LOG: Closing FTDI device.
25.Jul.2012 09:04:57.234: LOG: Send receive thread now terminated.
25.Jul.2012 09:05:24.875: LOG: Setting Address: 0x01 KeyByte1: 0x6B KeyByte2: 0x0F
25.Jul.2012 09:05:24.921: LOG: Opened FTDI device.
25.Jul.2012 09:05:24.921: LOG: FTDI device info - Description: FT232R USB UART Serial Number: A100enyw Device Type: FT_DEVICE_232R ID: 0x4036001 Device Flags: 0x0
25.Jul.2012 09:05:24.921: LOG: FTDI ChipID DLL is loaded, checking chip ID...
25.Jul.2012 09:05:24.937: LOG: FTDI device chip ID: 0x7F0B3CF1
25.Jul.2012 09:05:24.984: USER: Validated FTDI device is in dumb mode.
25.Jul.2012 09:05:25.000: LOG: Starting send receive thread.
25.Jul.2012 09:05:25.000: LOG: Send receive thread now started.
25.Jul.2012 09:05:25.000: USER: Disconnected
25.Jul.2012 09:05:25.031: LOG: Setting communication timings to defaults.
25.Jul.2012 09:05:25.031: LOG: Set timing parameters to defaults.
25.Jul.2012 09:05:25.031: USER: Connecting...
25.Jul.2012 09:05:25.046: LOG: Setting communication timings to defaults.
25.Jul.2012 09:05:25.046: USER: Starting slow init connection.
25.Jul.2012 09:05:27.656: USER: Connecting to address 0x01.
25.Jul.2012 09:05:29.828: USER: Slow init succeeded.
25.Jul.2012 09:05:29.828: LOG: Setting Address: 0x01 KeyByte1: 0x01 KeyByte2: 0x0A
25.Jul.2012 09:05:29.828: USER: Switching to KWP1281 session.
25.Jul.2012 09:05:30.000: LOG: KWP1281 read block
25.Jul.2012 09:05:30.062: LOG: KWP1281 sent block
25.Jul.2012 09:05:30.375: LOG: KWP1281 read block
25.Jul.2012 09:05:30.437: LOG: KWP1281 sent block
25.Jul.2012 09:05:30.609: LOG: KWP1281 read block
25.Jul.2012 09:05:30.687: LOG: KWP1281 sent block
25.Jul.2012 09:05:30.828: LOG: KWP1281 read block
25.Jul.2012 09:05:30.890: LOG: KWP1281 sent block
25.Jul.2012 09:05:30.921: LOG: KWP1281 read block
25.Jul.2012 09:05:31.000: LOG: KWP1281 sent block
25.Jul.2012 09:05:31.000: USER: KWP1281 connect info: 4B0907551G  2.7l V6/5VT         0001 ,ð 
25.Jul.2012 09:05:32.500: USER: Connecting to address 0x01.
25.Jul.2012 09:05:34.703: USER: Slow init succeeded.
25.Jul.2012 09:05:34.703: LOG: Setting Address: 0x01 KeyByte1: 0x6F KeyByte2: 0x0F
25.Jul.2012 09:05:34.703: USER: Switching to KWP2000 session.
25.Jul.2012 09:05:34.703: USER: Connected
2Jul.2012 09:08:56.453: LOG: Sent message with service ID TransferData
25.Jul.2012 09:08:56.484: LOG: Received message with service ID: TransferDataPositiveResponse
25.Jul.2012 09:08:57.625: LOG: Received message with service ID: TransferDataPositiveResponse
25.Jul.2012 09:08:57.625: USER: 100% complete.
25.Jul.2012 09:08:57.625: USER: Data transfer complete.
25.Jul.2012 09:08:57.625: USER: Requesting data transfer exit.
25.Jul.2012 09:08:57.625: LOG: Sent message with service ID RequestTransferExit
25.Jul.2012 09:08:57.656: LOG: Received message with service ID: RequestTransferExitPositiveResponse
25.Jul.2012 09:08:57.656: USER: Successfully exited data transfer.
25.Jul.2012 09:09:00.140: LOG: Sent message with service ID TesterPresent
25.Jul.2012 09:09:00.156: LOG: Received message with service ID: TesterPresentPositiveReponse
25.Jul.2012 09:09:02.640: LOG: Sent message with service ID TesterPresent
25.Jul.2012 09:09:02.656: LOG: Received message with service ID: TesterPresentPositiveReponse
25.Jul.2012 09:09:05.140: LOG: Sent message with service ID TesterPresent
25.Jul.2012 09:09:05.156: LOG: Received message with service ID: TesterPresentPositiveReponse
25.Jul.2012 09:09:07.640: LOG: Sent message with service ID TesterPresent
25.Jul.2012 09:09:07.671: LOG: Received message with service ID: TesterPresentPositiveReponse
25.Jul.2012 09:09:10.140: LOG: Sent message with service ID TesterPresent
25.Jul.2012 09:09:10.156: LOG: Received message with service ID: TesterPresentPositiveReponse
25.Jul.2012 09:09:12.656: LOG: Sent message with service ID TesterPresent
25.Jul.2012 09:09:12.671: LOG: Received message with service ID: TesterPresentPositiveReponse
25.Jul.2012 09:09:15.078: USER: Saved ECU flash memory to: C:\Dokumente und Einstellungen\Michi\Desktop\ori.bin
25.Jul.2012 09:09:15.125: USER: Reading ECU flash memory succeeded in: 00:02:50.
25.Jul.2012 09:09:15.156: LOG: Sent message with service ID TesterPresent
25.Jul.2012 09:09:15.171: LOG: Received message with service ID: TesterPresentPositiveReponse
25.Jul.2012 09:09:17.546: LOG: User Prompt - Title: Reading ECU Flash Memory Complete Message: Reading ECU flash memory succeeded in: 00:02:50. Result: OK
25.Jul.2012 09:09:17.546: USER: Restoring Windows sleep mode.
25.Jul.2012 09:09:17.656: LOG: Sent message with service ID TesterPresent



Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: scalp06 on July 31, 2012, 05:11:05 AM
Hi, I leave in France and I see few C Box with 29F400.

I can't see this ecu on supported ecu list from nefmoto software.

I can read and write in bootmode with Magpro tool, it's working great but I would write over OBD for win time. I already test the writing over OBD with my tool but the procedure crash after erasing flash and writing 4%... (thank to bootmode for recovery!)

I haven't see in this board anything about obd writing for this kind oh ecu.

Off topic: I have to test in this car the eeprom read with soft me7_95040 but no issue too...

For Nefarious, do you plan to support this ecu or it's not possible with hardware of this generation ecu?

Regards.


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: quattro85 on August 22, 2012, 01:59:45 PM
After failing while trying Full Read Flash - I try every speed, try with old VAG-COM cable also with VCDS 11.2 in dumb mode but no success. I can connect, and manage to read ECU info but can't read flash file.
Today I found original file from exactly same ECU version, and I make definition file with ME7info. After loading definitions I try to log some data but again with no success.
Any idea what to try next?


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: nyet on August 22, 2012, 03:10:36 PM
After failing while trying Full Read Flash - I try every speed

When you switch speeds you MAY have to quit Nefmoto and restart... I was fighting this issue for a long time. Might be a bug in the program.

Also, try cycling the ignition whenever you switch speeds as well.


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: quattro85 on August 23, 2012, 02:05:55 AM
Thank you nyet!
I'll try to cycle ignition, after choosing new speed. But I've noticed that regardless of chosen speed, when I connect again speed is again at maximum 124 800, and after that I can choose slower speed from drop down.

Another things that I've noticed - after attempt for Full Read Flash, ESP led on the dashboard is on, and both fuel trims was reset to 0 (like clearing fault codes in VCDS).

Here is a Nefmoto log with Read ECU info
Code:
09:41:06.187: LOG: Opened NefMoto VW Audi ME7 Flasher Logger 1.9.3.2
09:41:13.342: LOG: Setting Address: 0x01 KeyByte1: 0x6B KeyByte2: 0x0F
09:41:13.358: LOG: Opened FTDI device.
09:41:13.358: LOG: FTDI device info - Description: USB <-> Serial Serial Number:  Device Type: FT_DEVICE_BM ID: 0x4036001 Device Flags: 0x0
09:41:13.359: LOG: FTDI ChipID DLL is loaded, checking chip ID...
09:41:13.360: LOG: Unable to read FTDI device chip ID
09:41:13.376: USER: Validated FTDI device is in dumb mode.
09:41:13.379: LOG: Starting send receive thread.
09:41:13.387: LOG: Send receive thread now started.
09:41:13.389: USER: Disconnected
09:41:13.397: LOG: Setting communication timings to defaults.
09:41:13.398: LOG: Set timing parameters to defaults.
09:41:13.399: USER: Connecting...
09:41:13.407: LOG: Setting communication timings to defaults.
09:41:13.410: USER: Starting slow init connection.
09:41:16.011: USER: Connecting to address 0x01.
09:41:18.168: USER: Slow init succeeded.
09:41:18.169: LOG: Setting Address: 0x01 KeyByte1: 0x6F KeyByte2: 0x0F
09:41:18.169: USER: Switching to KWP2000 session.
09:41:18.170: USER: Connected
09:41:20.695: LOG: Sent message with service ID TesterPresent
09:41:20.730: LOG: Received message with service ID: TesterPresentPositiveReponse
09:41:23.121: USER: Disabling Windows sleep mode.
09:41:23.126: USER: Reading all ECU info.
09:41:23.177: LOG: Starting StandardSession diagnostic session with 124800 baud rate.
09:41:23.179: USER: Starting diagnostic session.
09:41:23.201: LOG: Sent message with service ID StartDiagnosticSession
09:41:23.241: LOG: Received message with service ID: NegativeResponse
09:41:23.242: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: SubFunctionNotSupported_InvalidFormat
09:41:23.247: LOG: Starting StandardSession diagnostic session with 52800 baud rate.
09:41:23.248: LOG: Start diagnostic session failed, ECU reports sub function not supported or invalid format. Trying again with a different format.
09:41:23.277: LOG: Sent message with service ID StartDiagnosticSession
09:41:23.321: LOG: Received message with service ID: NegativeResponse
09:41:23.321: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: SubFunctionNotSupported_InvalidFormat
09:41:23.322: LOG: Starting StandardSession diagnostic session with 38400 baud rate.
09:41:23.322: LOG: Start diagnostic session failed, ECU reports sub function not supported or invalid format. Trying again with a different format.
09:41:23.354: LOG: Sent message with service ID StartDiagnosticSession
09:41:23.391: LOG: Received message with service ID: NegativeResponse
09:41:23.391: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: SubFunctionNotSupported_InvalidFormat
09:41:23.392: LOG: Starting StandardSession diagnostic session with 10400 baud rate.
09:41:23.392: LOG: Start diagnostic session failed, ECU reports sub function not supported or invalid format. Trying again with a different format.
09:41:23.431: LOG: Sent message with service ID StartDiagnosticSession
09:41:23.472: LOG: Received message with service ID: NegativeResponse
09:41:23.472: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: SubFunctionNotSupported_InvalidFormat
09:41:23.473: LOG: Starting StandardSession diagnostic session with 9600 baud rate.
09:41:23.473: LOG: Start diagnostic session failed, ECU reports sub function not supported or invalid format. Trying again with a different format.
09:41:23.508: LOG: Sent message with service ID StartDiagnosticSession
09:41:23.552: LOG: Received message with service ID: NegativeResponse
09:41:23.552: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: SubFunctionNotSupported_InvalidFormat
09:41:23.552: LOG: Starting StandardSession diagnostic session without baud rate.
09:41:23.553: LOG: Start diagnostic session failed, ECU reports sub function not supported or invalid format. Trying again with a different format.
09:41:23.579: LOG: Sent message with service ID StartDiagnosticSession
09:41:23.621: LOG: Received message with service ID: NegativeResponse
09:41:23.622: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: SubFunctionNotSupported_InvalidFormat
09:41:23.622: LOG: Starting StandardSession diagnostic session without baud rate.
09:41:23.622: LOG: Start diagnostic session failed, ECU reports sub function not supported or invalid format. Trying again with a different format.
09:41:23.651: LOG: Sent message with service ID StartDiagnosticSession
09:41:23.691: LOG: Received message with service ID: NegativeResponse
09:41:23.692: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: SubFunctionNotSupported_InvalidFormat
09:41:23.692: LOG: Start diagnostic session failed, ECU reports sub function not supported or invalid format. Trying again with a different format.
09:41:23.718: LOG: Sent message with service ID StopDiagnosticSession
09:41:23.761: LOG: Received message with service ID: NegativeResponse
09:41:23.762: LOG: Received negative response for service ID: StopDiagnosticSession, with response code: ServiceNotSupported
09:41:23.762: USER: Unable to properly start diagnostic session, attempting to continue with current undefined session.
09:41:23.770: USER: Negotiating communication timings.
09:41:23.771: LOG: Reading current communication timings.
09:41:23.815: LOG: Sent message with service ID AccessTimingParameters
09:41:23.855: LOG: Received message with service ID: AccessTimingParametersPositiveResponse
09:41:23.858: LOG: Set timing parameters to new values.
09:41:23.858: LOG: Reading communication timing limits.
09:41:23.913: LOG: Sent message with service ID AccessTimingParameters
09:41:23.955: LOG: Received message with service ID: AccessTimingParametersPositiveResponse
09:41:23.956: LOG: Requesting communication at timing limits.
09:41:23.958: LOG: Sent message with service ID AccessTimingParameters
09:41:24.000: LOG: Received message with service ID: AccessTimingParametersPositiveResponse
09:41:24.000: USER: Successfully changed to new communication timings.
09:41:24.001: LOG: Reading ECU identification option: 0x81
09:41:24.002: LOG: Sent message with service ID ReadECUIdentification
09:41:24.044: LOG: Received message with service ID: ReadECUIdentificationPositiveResponse
09:41:24.045: LOG: Read ECU identification option: 0x81
09:41:24.045: LOG: Successfully read ECU identification information
09:41:24.051: USER: 0% complete.
09:41:24.051: LOG: Reading ECU identification option: 0x92
09:41:24.052: LOG: Sent message with service ID ReadECUIdentification
09:41:24.080: LOG: Received message with service ID: ReadECUIdentificationPositiveResponse
09:41:24.080: LOG: Read ECU identification option: 0x92
09:41:24.081: LOG: Successfully read ECU identification information
09:41:24.083: USER: 20% complete.
09:41:24.084: LOG: Reading ECU identification option: 0x94
09:41:24.086: LOG: Sent message with service ID ReadECUIdentification
09:41:24.110: LOG: Received message with service ID: ReadECUIdentificationPositiveResponse
09:41:24.110: LOG: Read ECU identification option: 0x94
09:41:24.111: LOG: Successfully read ECU identification information
09:41:24.111: USER: 40% complete.
09:41:24.111: LOG: Reading ECU identification option: 0x91
09:41:24.112: LOG: Sent message with service ID ReadECUIdentification
09:41:24.143: LOG: Received message with service ID: ReadECUIdentificationPositiveResponse
09:41:24.144: LOG: Read ECU identification option: 0x91
09:41:24.145: LOG: Successfully read ECU identification information
09:41:24.145: USER: 60% complete.
09:41:24.145: LOG: Reading ECU identification option: 0x9B
09:41:24.146: LOG: Sent message with service ID ReadECUIdentification
09:41:24.204: LOG: Received message with service ID: ReadECUIdentificationPositiveResponse
09:41:24.205: LOG: Read ECU identification option: 0x9B
09:41:24.205: LOG: Successfully read ECU identification information
09:41:24.206: USER: 80% complete.
09:41:24.207: LOG: Reading ECU identification option: 0x9C
09:41:24.209: LOG: Sent message with service ID ReadECUIdentification
09:41:24.234: LOG: Received message with service ID: ReadECUIdentificationPositiveResponse
09:41:24.235: LOG: Read ECU identification option: 0x9C
09:41:24.235: LOG: Successfully read ECU identification information
09:41:24.236: USER: 100% complete.
09:41:24.247: USER: Read 5 ECU info entries:
09:41:24.263: USER: 0x92, System Supplier ECU Hardware Number: 0261208228
09:41:24.267: USER: 0x94, System Supplier ECU Software Number: 1037369311
09:41:24.270: USER: 0x91, Vehicle Manufacturer ECU Hardware Number: 0x0D, 8E0909018A  , 0xFF
09:41:24.273: USER: 0x9B, Calibration Date: 8E0909518AL , 0003, 0x03002DBF, 0x0001010A, 0x81FE, 1.8L R4/5VT    ,  G  
09:41:24.287: USER: 0x9C, Calibration Equiment Software Number: 0x00004E00
09:41:24.295: USER: Restoring Windows sleep mode.



Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: quattro85 on August 23, 2012, 02:07:46 AM
And immediately after that attempt for Full Read Flash which failed

Code:
09:41:39.924: LOG: User Prompt - Title: Confirm Full Read ECU Flash Memory Message: If you are ready to read, confirm the following things:
1) You have loaded a valid memory layout for the ECU.
2) The engine is not running.
Note: Some non-standard flash memory chips may prevent reading the flash memory.

Click OK to confirm, otherwise Cancel. Result: OK
09:41:39.924: USER: Disabling Windows sleep mode.
09:41:39.939: USER: Reading ECU flash memory.
09:41:39.966: LOG: Reading ECU identification option: 0x9C
09:41:39.967: LOG: Sent message with service ID ReadECUIdentification
09:41:39.992: LOG: Received message with service ID: ReadECUIdentificationPositiveResponse
09:41:39.993: LOG: Read ECU identification option: 0x9C
09:41:39.993: LOG: Successfully read ECU identification information
09:41:39.997: USER: ECU reports programming session preconditions have been met.
09:41:39.997: USER: Negotiating communication timings.
09:41:39.998: LOG: Reading current communication timings.
09:41:39.999: LOG: Sent message with service ID AccessTimingParameters
09:41:40.023: LOG: Received message with service ID: AccessTimingParametersPositiveResponse
09:41:40.024: LOG: Setting communication timing to defaults.
09:41:40.026: LOG: Sent message with service ID AccessTimingParameters
09:41:40.048: LOG: Received message with service ID: AccessTimingParametersPositiveResponse
09:41:40.049: LOG: Reading current communication timings.
09:41:40.051: LOG: Sent message with service ID AccessTimingParameters
09:41:40.103: LOG: Received message with service ID: AccessTimingParametersPositiveResponse
09:41:40.104: USER: Successfully changed to new communication timings.
09:41:40.106: USER: Requesting security access.
09:41:40.108: LOG: Sent message with service ID SecurityAccess
09:41:40.152: LOG: Received message with service ID: SecurityAccessPositiveResponse
09:41:40.155: LOG: Received security seed, sending security key.
09:41:40.157: LOG: Sent message with service ID SecurityAccess
09:41:40.209: LOG: Received message with service ID: SecurityAccessPositiveResponse
09:41:40.210: USER: Security access granted.
09:41:40.210: LOG: Starting ProgrammingSession diagnostic session with 52800 baud rate.
09:41:40.210: USER: Starting diagnostic session.
09:41:40.212: LOG: Sent message with service ID StartDiagnosticSession
09:41:40.259: LOG: Received message with service ID: NegativeResponse
09:41:40.260: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending
09:41:40.299: LOG: Received message with service ID: NegativeResponse
09:41:40.299: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending
...
09:41:44.858: LOG: Received message with service ID: NegativeResponse
09:41:44.858: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending
09:41:44.891: LOG: Received message with service ID: StartDiagnosticSessionPositiveResponse
09:41:44.891: LOG: Setting communication timings to defaults.
09:41:44.892: LOG: Set timing parameters to defaults.
09:41:44.892: LOG: Sent message with service ID TesterPresent
09:41:44.893: LOG: Changed diagnostic session type to: ProgrammingSession
09:41:44.893: LOG: ECU requesting specific baud rate: 52800
09:41:44.894: USER: Successfully started diagnostic session.
09:41:44.894: USER: Negotiating communication timings.
09:41:44.894: LOG: Reading current communication timings.
09:41:46.894: LOG: Message received no replies.
09:41:46.894: LOG: Resending message. Send attempts: 2
09:41:46.910: LOG: Sent message with service ID TesterPresent
09:41:46.947: LOG: Received message with service ID: TesterPresentPositiveReponse
09:41:47.008: LOG: Sent message with service ID AccessTimingParameters
09:41:47.048: LOG: Received message with service ID: AccessTimingParametersPositiveResponse
09:41:47.048: LOG: Set timing parameters to new values.
09:41:47.049: LOG: Reading communication timing limits.
09:41:47.105: LOG: Sent message with service ID AccessTimingParameters
09:41:47.148: LOG: Received message with service ID: AccessTimingParametersPositiveResponse
09:41:47.148: LOG: Requesting communication at timing limits.
09:41:47.150: LOG: Sent message with service ID AccessTimingParameters
09:41:47.187: LOG: Received message with service ID: AccessTimingParametersPositiveResponse
09:41:47.187: USER: Successfully changed to new communication timings.
09:41:47.188: USER: Requesting security access.
09:41:47.189: LOG: Sent message with service ID SecurityAccess
09:41:47.208: LOG: Received message with service ID: SecurityAccessPositiveResponse
09:41:47.208: USER: Security access granted.
09:41:47.209: USER: Validating flash memory starts at 0x00800000 and ends at 0x00900000.
09:41:47.212: LOG: Sent message with service ID RequestUpload
09:41:47.227: LOG: Received message with service ID: NegativeResponse
09:41:47.227: LOG: Received negative response for service ID: RequestUpload, with response code: SecurityAccessDenied_SecurityAccessRequested
09:41:47.228: USER: Validation failed, ECU reports that security access is not granted.
09:41:47.229: USER: Memory layout validation failed.
09:41:49.715: LOG: Sent message with service ID TesterPresent
09:41:49.736: LOG: Received message with service ID: TesterPresentPositiveReponse
09:41:50.554: LOG: User Prompt - Title: Unable to validate memory layout Message: Unable to validate memory layout. Do you want to continue reading flash memory without validating the memory layout? Result: OK
09:41:50.555: USER: Starting to read data block.
09:41:50.557: USER: Requesting upload from ECU for address range 0x00800000 to 0x00803FFF.
09:41:50.558: LOG: Sent message with service ID RequestUpload
09:41:50.576: LOG: Received message with service ID: NegativeResponse
09:41:50.577: LOG: Received negative response for service ID: RequestUpload, with response code: SecurityAccessDenied_SecurityAccessRequested
09:41:50.579: USER: Request upload from ECU failed, ECU reports security access has not been granted.
09:41:50.580: USER: Reading ECU flash memory failed. Trying to force ECU to recognize read operation is complete.
09:41:50.581: LOG: Validating flashed data checksum for address range 0x00900000 to 0x00900001.
09:41:50.584: LOG: Sent message with service ID StartRoutineByLocalIdentifier
09:41:50.606: LOG: Received message with service ID: StartRoutineByLocalIdentifierPositiveResponse
09:41:50.611: LOG: Sent message with service ID RequestRoutineResultsByLocalIdentifier
09:41:50.626: LOG: Received message with service ID: NegativeResponse
09:41:50.627: LOG: Received negative response for service ID: RequestRoutineResultsByLocalIdentifier, with response code: BlockTransferDataChecksumError
09:41:50.627: LOG: Checksum is incorrect.
09:41:50.628: USER: Finished forcing ECU to recognize that failed read operation is complete.
09:41:50.632: USER: Reading ECU flash memory failed.
09:41:53.114: LOG: Sent message with service ID TesterPresent
09:41:53.135: LOG: Received message with service ID: TesterPresentPositiveReponse
09:41:53.625: LOG: User Prompt - Title: Reading ECU Flash Memory Complete Message: Reading ECU flash memory failed. Result: OK
09:41:53.626: USER: 100% complete.
09:41:53.639: USER: Restoring Windows sleep mode.


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: quattro85 on August 23, 2012, 02:27:24 AM
And here is other part with log attempt
Code:
09:49:01.968: LOG: Sent message with service ID TesterPresent
09:49:01.984: LOG: Received message with service ID: TesterPresentPositiveReponse
09:49:03.731: USER: Disabling Windows sleep mode.
09:49:03.739: USER: Starting variable reading.
09:49:03.753: LOG: Starting DevelopmentSession diagnostic session with 52800 baud rate.
09:49:03.754: USER: Starting diagnostic session.
09:49:03.755: LOG: Sent message with service ID StartDiagnosticSession
09:49:03.775: LOG: Received message with service ID: NegativeResponse
09:49:03.776: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: SecurityAccessDenied_SecurityAccessRequested
09:49:03.777: USER: Start diagnostic session failed, ECU reports security access is required.
09:49:03.783: USER: 100% complete.
09:49:03.785: USER: Stopped reading variables.
09:49:03.786: USER: Restoring Windows sleep mode.
09:49:06.257: LOG: Sent message with service ID TesterPresent
09:49:06.272: LOG: Received message with service ID: TesterPresentPositiveReponse
09:49:08.760: LOG: Sent message with service ID TesterPresent
09:49:08.772: LOG: Received message with service ID: TesterPresentPositiveReponse
09:49:09.693: USER: Disabling Windows sleep mode.
09:49:09.698: USER: Starting variable reading.
09:49:09.716: LOG: Starting DevelopmentSession diagnostic session with 52800 baud rate.
09:49:09.716: USER: Starting diagnostic session.
09:49:09.717: LOG: Sent message with service ID StartDiagnosticSession
09:49:09.734: LOG: Received message with service ID: NegativeResponse
09:49:09.735: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: SecurityAccessDenied_SecurityAccessRequested
09:49:09.735: USER: Start diagnostic session failed, ECU reports security access is required.
09:49:09.736: USER: 100% complete.
09:49:09.737: USER: Stopped reading variables.
09:49:09.737: USER: Restoring Windows sleep mode.
09:49:12.219: LOG: Sent message with service ID TesterPresent
09:49:12.232: LOG: Received message with service ID: TesterPresentPositiveReponse
09:49:14.721: LOG: Sent message with service ID TesterPresent
09:49:14.741: LOG: Received message with service ID: TesterPresentPositiveReponse
09:49:17.223: LOG: Sent message with service ID TesterPresent
09:49:17.241: LOG: Received message with service ID: TesterPresentPositiveReponse
09:49:19.727: LOG: Sent message with service ID TesterPresent
09:49:19.741: LOG: Received message with service ID: TesterPresentPositiveReponse
09:49:22.230: LOG: Sent message with service ID TesterPresent
09:49:22.251: LOG: Received message with service ID: TesterPresentPositiveReponse
09:49:22.843: USER: Disabling Windows sleep mode.
09:49:22.850: USER: Starting variable reading.
09:49:22.854: LOG: Starting DevelopmentSession diagnostic session with 52800 baud rate.
09:49:22.855: USER: Starting diagnostic session.
09:49:22.857: LOG: Sent message with service ID StartDiagnosticSession
09:49:22.872: LOG: Received message with service ID: NegativeResponse
09:49:22.872: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: SecurityAccessDenied_SecurityAccessRequested
09:49:22.873: USER: Start diagnostic session failed, ECU reports security access is required.
09:49:22.874: USER: 100% complete.

Now I noticed that reasons for failing in Read Flash and logging are different.
In 2-nd log I saw this
LOG: Sent message with service ID StartDiagnosticSession
 LOG: Received message with service ID: NegativeResponse
 LOG: Received negative response for service ID: StartDiagnosticSession, with response code: SecurityAccessDenied_SecurityAccessRequested
 USER: Start diagnostic session failed, ECU reports security access is required.


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: nyet on August 23, 2012, 08:45:30 AM
Thank you nyet!
I'll try to cycle ignition, after choosing new speed. But I've noticed that regardless of chosen speed, when I connect again speed is again at maximum 124 800, and after that I can choose slower speed from drop down.

Oh, i meant like this sequence

1) launch nefmoto
2) select speed, connect
3) try flashing
4) fails
5) ---- QUIT NEFMOTO ----
6) ---- RESTART NEFMOTO ----
7) select different speed, connect



Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: quattro85 on August 25, 2012, 02:25:09 AM
I try everything from above, even puling out some fuses (instrument & ABS/ESP - because I noticed that after unsuccessful Read I get ESP led on) and no success.
I try ME7logger and it works great every time with the same old VAG-COM cable.
May you suggest me any other tool to try reading flash? Maybe I should buy some MPPS clone?
 


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: professor on August 25, 2012, 02:35:17 AM
Try this if haven't so far:

1. Connect cable
2. Open nefmoto
3. Ignition on
4. Set baud rate and hit connect
5. After successful connection select again baud rate (mine is auto select after successful connection 128000 baud rate which dot work)
6. Select memory layout and if for flash the correct file to flash
7. Try full read/flash
8. If full reading after 100% progress give name to bin you just read.


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: quattro85 on August 27, 2012, 11:45:46 PM
Thank you!
Anyway I can't get NefMoto work for me in my car :(

Today I try it in a 1999 Audi TT with APP engine and it works from first time.
Just connect, change speed, choose layout and hit full read flash.

Definitely there is some problem with my B6, not the cable nor NefMoto but I can not solve it. :(


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: slowrideBC on September 05, 2012, 10:33:01 PM
ehhh figured most of it out...now I need the tune re-done since it was for a different ecu revesion....sorry...

thanks for the awesome program Tony...


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: DNK on September 07, 2012, 12:23:02 AM
Just connected with VagCom cable, selected layout and get the ECU info. Dowloaded flash .bin and uploaded new one. Without any problems.


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: em.Euro.R18 on September 11, 2012, 09:53:50 AM
I understand there are problems with the flasher reading ECU files(which may have aftermarket software possibly APR or REVO). When I select to read an error message pops up (may experience issues if the correct memory layout isn't selected, or something of the nature which I can't recall verbatim at this time).

~Which is understandable... so you proceed anyway? And hope It will not read "programming not finished"?


~Also the only way to recover the ecu is to upload another file in boot mode. Is it a must to have a copy of the same exact file or just another generic file for that ecu part #?


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: BlackCupra on September 20, 2012, 02:13:31 PM
Used it for flashing the Ibiza BBU ME7.5 now several times, very good :-)

Donation for Premium upgrade sent :-)

BR

Alex


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: BlackCupra on September 22, 2012, 10:51:23 AM
Thank you Tony for Premium license :-)

BR

Alex


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: professor on October 14, 2012, 07:32:22 AM
06A906032RP (EU seat ibiza cupra 1.8T 20V MK4), 06A906032QN (EU seat ibiza FR 1.8T 20V MK4), 1ML906032A (EU seat leon cupra 1.8T 20V BAM) are not in the wiki list (all ME7.5 AM29F800BB).
Tested by me and nefmoto can flash them successfully.


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: BlackCupra on October 14, 2012, 01:27:12 PM
I confirm it works perfectly on 06A906032RP, also fast write and read.

Fast write is about 1:30min :-)

BR

Alex


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: RaraK on October 16, 2012, 07:12:41 PM
06a906032S(K,M) gives P1581 programming not complete error, even on a READ.

Just a heads up Tony.


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: vtraudt on December 31, 2012, 02:05:42 PM
I just installed on my new computer (Win 7 -64 bit). Seems to work.
I want to try the logging feature first.
How do I select the parameters I want to log?
Or does it just log all parameters the ECU has to offer?


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: B5in on January 17, 2013, 12:56:27 PM
I just installed NefMoto but it won't open at all, it just does nothing, I have restarted just in case  ???

It's a Dell desktop running 32bit Win XP Pro SP3 and .NET 3.5


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: Drehkraft on March 15, 2013, 05:33:51 PM
Thanks Tony.  Worked like a charm first time out.  2001 Jetta AWW "DL" ECU.


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: ykchong4 on March 19, 2013, 08:21:54 AM
try to use this nefmoto ME7 with Ross-Tech KEY-USB cable 11.11.3, it just pop "failed to read test echo from FTDI device".
VCDS working great with this cable and the "boot in intelligent mode" have been turn off and saved. open the case of this cable confirm it is using FTDi chip inside.
This cable can't use the latest FTDI driver which is 2.08.28, it only can be detected by using 2.08.24.

In wiki tony said that "Old Ross-Tech KEY-USB (Does not support true dumb mode)". how to identify the version of the ross-tech cable support the me7 logger?


this car is audi TT 1.8.


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: ykchong4 on March 26, 2013, 08:20:37 AM
anywhere i'm already buy another cable from recommend ebay seller hope can solve it out...


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: ddillenger on March 26, 2013, 08:25:23 AM
anywhere i'm already buy another cable from recommend ebay seller hope can solve it out...

Order a galletto. AFAIK they all work with nefmotor flasher/logger.


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: tbm on April 04, 2013, 02:58:04 PM
Hi Guys,

Could someone advise me with the below:
I use "dump cable" and try to read flash from ME7.5 (06A906032HN). But I've faced with "Reading ECU flash memory failed." error. 29F800 memory layout was set.

Full log file attached.

Thanks in advance!

Regards.


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: vdubnation on April 04, 2013, 05:40:42 PM
i m not sure but i saw this in the log
"Some non-standard flash memory chips may prevent reading the flash memory."

Your ecu might be chipped and reading could be disabled

just a guess but not sure


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: tbm on April 04, 2013, 11:43:22 PM
i m not sure but i saw this in the log
"Some non-standard flash memory chips may prevent reading the flash memory."

Your ecu might be chipped and reading could be disabled

just a guess but not sure

I tried to read from two stock ECUs. Maybe I need to set some parameters for my cable and ECU in the "ME7 ECU Flasher".


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: tbm on April 07, 2013, 01:20:13 PM
I tried to read from two stock ECUs. Maybe I need to set some parameters for my cable and ECU in the "ME7 ECU Flasher".
I've noticed I faced "USER: Disconnecting because no response was received for the Tester Present message." error ONLY when I tried to read flash memory.


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: NOTORIOUS VR on May 31, 2013, 08:05:46 AM
Anyone else have issues flashing while getting the error "security access denied" or something to that matter?

I know it's immo related... the strange thing is I used to be able to use NefMoto flasher to flash my and other 1.8T cars just fine on the very first shot every time, but I decided to reformat my HDD and now it just doesn't work.

MPPS works fine though, don't have to pull fuses or anything.  quite annoying, wondering if anyone has a fix for it.  I would like to start using NefMoto flasher again.


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: ddillenger on May 31, 2013, 10:02:32 AM
Fast INIT.

Still flaky at best though.


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: NOTORIOUS VR on May 31, 2013, 12:49:28 PM
^^^ Hmmm... I'll try that, thanks for the tip!


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: Forcf3d on May 31, 2013, 03:03:40 PM
So i am able to connect while ignition is "on". But if i try connecting after the car has been started it won't. 2000 S4.

Any suggestions?


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: ddillenger on May 31, 2013, 03:09:31 PM
You're supposed to connect with the ignition ON but the car not running. Key On Engine Off.


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: Forcf3d on May 31, 2013, 03:17:22 PM
Then how do you use the logging function?


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: ddillenger on May 31, 2013, 03:27:54 PM
Never used the nefmoto logger, I use ME7Logger.


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: Forcf3d on May 31, 2013, 03:29:04 PM
Ok. Thanks. I'll try downloading that.


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: Forcf3d on May 31, 2013, 03:37:30 PM
So when I go to open ME7 logger, a window flashes open quick and then closes. Program won't open. I am on windows 7. That a problem?


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: ddillenger on May 31, 2013, 04:42:22 PM
Read the thread. It's a command line program. If you can't handle that, download the GUI. You'll find it with some searching.


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: NOTORIOUS VR on June 01, 2013, 12:54:53 PM
Fast INIT.

Still flaky at best though.

FWIW, FAST init didn't work for me at all..

I had to use Slow init and then choose the fastest baud rate (leaving it as undetected is what seemed to make it not work) and it works like a charm now.


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: userpike on June 04, 2013, 12:19:00 AM
FWIW, FAST init didn't work for me at all..

I had to use Slow init and then choose the fastest baud rate (leaving it as undetected is what seemed to make it not work) and it works like a charm now.
Is it a licensed version? no fast init at all without it. Just wondering how long it takes to complete a flash for you at a higher Baud rate?  I use 10800 with slow init and it takes 12minutes and 8seconds. I have the license but I'm scared to use fast init HA! I understand it only takes a couple minutes though.


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: ddillenger on June 04, 2013, 12:35:00 AM
Fast init is under connection options. You're confusing INIT with FLASH :)


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: phila_dot on June 04, 2013, 05:32:26 AM
Is it a licensed version? no fast init at all without it. Just wondering how long it takes to complete a flash for you at a higher Baud rate?  I use 10800 with slow init and it takes 12minutes and 8seconds. I have the license but I'm scared to use fast init HA! I understand it only takes a couple minutes though.

Fast init is not a premium feature and has nothing to do with how long it takes for the flash to complete.

Fast write is a premium feature and it's perfectly safe. It just skips regions that don't need to be rewritten.

If you have a premium license and are unsure about baud rate, just detect baud rates. I flash with a ridiculous baud rate on the bench in 20-30 seconds. More sane in the car, usually about 50 seconds.


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: Daviddoesntgaf on June 17, 2013, 07:51:52 AM
I'm running windows XP sp3 and when clicking on the ME7 icon nothing happens. no window blink or anything.


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: vdubnation on June 17, 2013, 07:54:09 AM
I'm running windows XP sp3 and when clicking on the ME7 icon nothing happens. no window blink or anything.

You cant just click it to log either you open it through command prompt or you download the GUI and use that.


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: vwaudiguy on August 01, 2013, 03:03:40 PM
Is a premium license needed to use the logging feature?


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: Hawkie on August 03, 2013, 01:16:18 PM
Would like to give a premium tip for those here that is just like me and uses several different cables as well as many types of software. To avoid driver crashes and software problems, I have installed Oracle Virtualbox and have created Windows XP SP3 virtual machine with all updates and so on. I then use this as clone for all my virtual working machines. As soon as a clone have been made i make sure it gets a new machine name (XP machine name) and then i create shared folders between this virtual machine and the host. When i insert a cable i DO NOT install any driver on the host machine for it, i just select to allow the virtual machine access to the "unknown device" and then installs the driver in the virtual machine. This way i can set up a virtual machine for each cable and install all software inside the virtual machine that works with this cable. It totally cleans it all up for me, and simplifies a lot.

This also makes it a lot easier to switch to a new laptop or other changes. Personally i have stored the virtul machines on a USB stick and loads it from there (as XP is not so hard to run from USB stick) on all my working machines, so when i have done a readout i just load the VM on the desktop and transfers binaries to the main machine, and then loads back when i am done.


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: S4dizzle219 on August 12, 2013, 06:26:49 PM
So I have a vcds ecu cord that I use quite often, simple straight forward and pretty cool! I have the newest version of me7 and when I try to even log it won't hook up am I doing something wrong or is this cord non compatible? Is me7 better than what I currently have. I am extremely interested in learning to read & diagnose logs to turn into home brew tunes & tweaks in the near future. I currently am running a JFONZ baby's stage 3 that I'm having some slight issues with.


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: hammersword on August 24, 2013, 12:05:46 PM
"Full Write Flash" means that the Nefmoto software writes from 0x000000 - 0x0FFFFF?


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: hammersword on August 25, 2013, 03:13:52 PM
checked.

It flashes full file


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: armageddon on January 26, 2014, 09:16:32 AM
Hi,

Today I tryed to read and write my G-box ECU.
On reading there was no problem, it took 2.30min to a full read.
Problem is on write, it fails to write.

What could be the problem? Immo? Baudrate?

log attached


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: armageddon on February 09, 2014, 08:18:45 AM
I still can't write, I have tried different baud rate and no luck, every time I'm getting the same error.
No problem at all when reading.

I will try defeat immo and flash on bench to see if it helps.


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: armageddon on February 13, 2014, 12:01:44 PM
So, I make immo off and still can not flash, every time the same error.

Also tryed galletto in boot mode and same problem, can't flash.

After that I download new version of galletto of ddillenger (no match serial) and can not get bootmode anymore.

need help please..



Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: ddillenger on February 13, 2014, 12:11:36 PM
Open your ecu and take a picture.


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: armageddon on February 13, 2014, 12:34:39 PM
Open your ecu and take a picture.

picture attached


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: ddillenger on February 13, 2014, 01:07:14 PM
Never seen an intel flash chip. Must use a different memory layout. Time to desolder it and put a stocker in.


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: nyet on February 13, 2014, 01:20:52 PM
Never seen an intel flash chip. Must use a different memory layout. Time to desolder it and put a stocker in.

Possibly. Would need a clearer picture and we can look up the datasheet.

Everybody and their mother made AM29F clones at the time.


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: buergi on February 13, 2014, 01:37:06 PM
Some days ago i found a intel 28F400 where a 29F400BB was supposed to be.
Modified memory layout didn't help me.
Wasn't possible to successfully erase this chip, so i desoldered it. Now with the AMD no problems at all.
Previous owner had a tuning chip installed which happened to be non-flashable in car...



Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: armageddon on February 13, 2014, 03:13:59 PM
The chip have this on top:

Intel
PA28F800
B5B70
U9280829B

So, you guys are saying that I need to replace the chip?

What chip will I need?

It doesn't seems to have been soldered/desoldered, although it has been remapped by previous owner.


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: ddillenger on February 13, 2014, 03:48:10 PM
29F800BB in order to write with nef or galletto.


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: armageddon on February 13, 2014, 04:03:46 PM
29F800BB in order to write with nef or galletto.

This:

http://www.chip-service.de/product_info.php?info=p96_AM29F800BB-55SF.html

or

http://www.chip-service.de/product_info.php?info=p420_AM29F800BB-70SE.html



Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: ddillenger on February 15, 2014, 02:43:36 PM
I run these:

http://www.ebay.com/itm/AMD-AM29F800BB-70SE-SOP-44-8-Megabit-1-M-x-8-Bit-512-K-x-/360848127868?pt=LH_DefaultDomain_0&hash=item540439777c

(well, not that seller, but that ic)


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: armageddon on February 16, 2014, 03:09:47 PM
I bought one of this (AM29F800BB-70SF):http://www.batronix.com/shop/chips/flash-eproms.html

probably next friday it will be here, so on the weekend I might be able to install it

from what I have read over here, on the first time I have to flash it in boot mode, am I right?


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: Marty on February 21, 2014, 11:09:08 AM
I bought one of this (AM29F800BB-70SF):http://www.batronix.com/shop/chips/flash-eproms.html

probably next friday it will be here, so on the weekend I might be able to install it

from what I have read over here, on the first time I have to flash it in boot mode, am I right?
Yes you must bootmode first time


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: armageddon on February 26, 2014, 03:09:53 PM
Sucess  :)

Thank you guys for all the help

soldered a new AM29F800BB-70SF and now finally I can flash


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: ddillenger on February 26, 2014, 06:20:19 PM
Congrats!


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: AudiMan85 on April 18, 2014, 08:06:43 AM
whats up guys, I wanted to know that since Tony has been MIA.

How do I purchase a license for the software and is it worth it if development stops. I don't really need paid version but would like to contribute and a faster write time would be great when I'm in a hurry.


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: adidascoin on April 30, 2014, 02:25:15 PM
Will this work at all on Volvo ME7.1? And did Dilemma's ME7.1 Normal mode flash tool ever get done????


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: PwrTuning on May 29, 2014, 11:31:32 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

I have tried to install it on my Windows 8.1 but I get the error message that I am attaching. What am I doing wrong? Please help!!
Thanks!!!


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: tjwasiak on May 30, 2014, 04:33:37 AM
Have you tried to run the installer as Administrator or how is it called in Windows 8.1?


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: The Great NY on July 09, 2014, 06:29:17 AM
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


hello,

I have installed the Nefmoto Software.  Im trying to setup to start reading and writing my S60R (ME7), but im having trouble even getting the the software to recognize my VAG KKL cable.  when the software is launched it just stays on the KWP2000 setting and refresh devices doesnt work or at least it doesnt show my device.

I've re-installed the FTDI drivers like four or five times and still have not gotten any improvements.

Any information on whats going on? maybe im doing something wrong, or missed a step.  Let me know, thanks.


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: The Great NY on July 09, 2014, 06:30:49 AM
also, wondering if i need to buy a license? if so how do I do that and where?


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: ljscodex on July 30, 2014, 11:34:13 AM
hi, thanks for your great work!

its Awesome!.

i need to read and flash (for immo off) 95040 of my A4 B6 with RB4, with this tool  can i do it?.

i was reading about me75_eeprom_95040 shell tool, but only for read via obd.

Thanks again!.


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: turboat on July 30, 2014, 01:42:37 PM
Nef cannot flash the 95040, you need to use argdubs tool for flashing that. http://nefariousmotorsports.com/forum/index.php?topic=1168.0title=


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: Bi-turbo on August 07, 2014, 12:26:34 AM
Will this ever be able to work with the 551C?


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: eliotroyano on August 31, 2014, 09:42:16 AM
Hi friends I have been trying to connect in bootmode but all the time I receive this error:
31/ago/2014 11:15:59.156: USER: Connecting...
31/ago/2014 11:15:59.187: USER: Starting bootstrap loader upload.
31/ago/2014 11:15:59.187: USER: Sent bootstrap init zero byte.
31/ago/2014 11:16:02.187: USER: Sent bootstrap init zero byte.
31/ago/2014 11:16:05.187: USER: Sent bootstrap init zero byte.
31/ago/2014 11:16:08.187: USER: Bootstrap loader upload failed. Failed to receive device ID response for init zero byte.
31/ago/2014 11:16:08.187: USER: Disconnected
ECU is 06A906032NL 0261208164 ME7.5. I am using WinXP SP3.
Can you help me?


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: ddillenger on August 31, 2014, 11:35:50 AM
Nefmoto doesn't do bootmode! That part was never finished.


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: Tony@NefMoto on September 02, 2014, 07:30:36 PM
Nefmoto doesn't do bootmode! That part was never finished.

Right now with the NefMoto software you should be able to connect in boot mode, but I never finished reading or writing. I do hope to finish that this year perhaps.:)


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: ddillenger on September 02, 2014, 07:53:00 PM
Right now with the NefMoto software you should be able to connect in boot mode, but I never finished reading or writing. I do hope to finish that this year perhaps.:)

I guess it works for TESTING bootmode, but once you query the ecu IN bootmode you have to shut it down and reinitialize anyway, so I don't even bother explaining that part-lol.

Just adds to the confusion.


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: TCSTigersClaw on September 03, 2014, 03:51:47 AM
Right now with the NefMoto software you should be able to connect in boot mode, but I never finished reading or writing. I do hope to finish that this year perhaps.:)

Will nefmoto be able to read other Ecus , like MED9 ?

I have ori tools ,but it is so fast with ME7.5 that I prefer it :)


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: Bi-turbo on September 24, 2014, 06:21:28 AM
Connecting to address 0x01.
Slow init succeeded.
Switching to KWP1281 session.
KWP1281 connect info: THIS-IS-THE-RAM-PROGRAM-           

The ECU is in programming mode, and needs the ignition turned off to reset.
If this does not end programming mode, the ECU likely believes the flash memory is not programmed correctly.
Reading all ECU info failed.   

Any ideas?



Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: ddillenger on September 24, 2014, 06:33:44 AM
Connecting to address 0x01.
Slow init succeeded.
Switching to KWP1281 session.
KWP1281 connect info: THIS-IS-THE-RAM-PROGRAM-           

The ECU is in programming mode, and needs the ignition turned off to reset.
If this does not end programming mode, the ECU likely believes the flash memory is not programmed correctly.
Reading all ECU info failed.   

Any ideas?



This has been covered 10000 times now.

You have to force the ecu into recognizing the programming session has ended. If it didn't do it after the flash, do a full read. If that doesn't work, you need to bootflash an eeprom backup taken before the problem.


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: Bi-turbo on September 24, 2014, 08:12:38 AM
It flashed on fine then I went back to read ecu info

How can you force the ecu to know it's been programmed?


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: Bi-turbo on September 24, 2014, 09:33:01 AM
Done a search and seems that I need to switch the ignition off and back on?

I'll have to stick a switch into the ignition wire in the bench loom.

Anything else to try?

I've put a different 95040 on it and flashed the file with galletto then tried to use nefmoto again and that's what it said


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: Bi-turbo on September 24, 2014, 02:15:30 PM
One D box file works fine and brings up the part number etc when I connect.

The other D box file keeps bringing up THIS IS THE RAM

Have got switch on the ignition power. No change

Have wrote another 95040. No change

What is the actual cause?

The file itself is fine as in a can read all the maps in tunerpro and its fine, have compared the hex dumps of both files and can't see anything out of place.


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: Bi-turbo on September 25, 2014, 12:26:58 AM
Could it be somthing in the flash .bin? as its a commercial tune?


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: turboat on September 25, 2014, 01:27:10 AM
It seems likely that nef is just reading back the ecu info, which in one of your bins is set to THIS IS THE RAM. Have you diff'd the files to see where they differ? Beyond compare is a useful tool for this.

Edit - just seen Tonys comments on the other thread, seems like it's still in programming mode. What do you get if you run me7check across the file?


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: Bi-turbo on September 25, 2014, 02:08:30 AM
me7check come back as fine.

In the location of the ecu number etc in the hex dump it is correct.

Cant see how to get around it? ive read all the searched threads on here and there isnt an actual answer.


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: turboat on September 25, 2014, 02:10:29 AM
Is this a 1.8t or 2.7t file?


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: Bi-turbo on September 25, 2014, 03:48:18 AM
551D 2.7T


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: ddillenger on September 25, 2014, 07:00:59 AM
Once you cycle the power after the flash, it should be normal again.

This assumes you are writing with nefmoto, not MPPS.


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: Bi-turbo on September 25, 2014, 07:14:51 AM
by cycling do you mean switching all power off and back on?

if so done that and still the same, flashed the file with nefmoto and galletto and both the same outcome.

as said i can put another file on and its fine but this file is causing issues but i dont know what issues


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: Bi-turbo on September 25, 2014, 01:26:10 PM
It's the .bin file

Put standard on it and its fine and vcds connects and all coding is there.

Just need to search for a decent .xdf as the LDRXN in the one I have is way off

The I'll copy and paste all the relevant maps, checksum, flash and see if that's goes on ok


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: ddillenger on September 25, 2014, 01:30:37 PM
It's the .bin file

Put standard on it and its fine and vcds connects and all coding is there.

Just need to search for a decent .xdf as the LDRXN in the one I have is way off

The I'll copy and paste all the relevant maps, checksum, flash and see if that's goes on ok

Don't copy and paste tune. If you're here, it should be to learn. Copying things from one file into another, then wondering why it doesn't work is unacceptable. Create your own file. If you can't explain EVERY SINGLE CHANGE to a file, you're not doing it right.


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: Bi-turbo on September 25, 2014, 10:32:14 PM
I no what and why things have been changed, I just need them in this ecu and the file has issues


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: Waltomatic on October 14, 2014, 04:22:13 PM
Can anyone tell me why the program I correctly installed simply does not open?

Windows XP SP3 + .NET 3.5


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: overspeed on October 15, 2014, 02:44:51 PM
Can anyone tell me why the program I correctly installed simply does not open?

Windows XP SP3 + .NET 3.5

Even if work, you can´t read ME3.1 with it... as said before bootmode was not implemented yet


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: em.Euro.R18 on October 15, 2014, 03:37:41 PM
Issue after full read attempt..... 4B0906018DQ car will not start after full read 52800 using a memory layout of 800BB?


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: ddillenger on October 15, 2014, 07:32:51 PM
P1681?


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: em.Euro.R18 on October 15, 2014, 07:50:35 PM
you got it! Luckly I got the full binary read and reflashed the binary I pulled everything is now fine but that was weird... All I did was a full read. ???


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: nyet on October 15, 2014, 08:30:07 PM
Add 4B0906018DQ to the blacklist?

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


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: MK2-VRT on November 07, 2014, 04:32:46 AM
I try to read a ME7.5 1.8T ecu with Arg dubb tool and with ME7gui,

I test with different Vag cables, test 50 times to read eeprom and bootmode, but 1 time i can read / write te eeprom, bootmode wont work, not with me7 and not with argdubb tool, try all the baudrates, no succes, read with mpps no problem, so bootmode isnt the problem.

Anyone a idea ?

In att a few pics,

Thx..


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: nyet on November 07, 2014, 10:15:01 AM
Please use alt-print-screen


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: turboat on November 08, 2014, 07:53:39 AM
Ok what cables have you been trying, what drivers, etc. are you reading on bench or in car?


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: MK2-VRT on November 10, 2014, 07:14:17 AM
I try with blue vag cable, but no succes..

Try with old usb 311 vagcom cable ( black ) and they not work.

I also try with a serial tacho soft cable, no luck.

With new Vcds it works ( Ftdi ), see att ( first post )

1 time i can read and write eeprom, after 50 times testing, nothing happends and no luck anymore..Also bootmode dont work ( error 07 )

Is the problem the cable or do i need something wrong with this prog ? I try in Win XP ( old xp )

Stefan



Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: ddillenger on November 10, 2014, 07:21:55 AM
I try with blue vag cable, but no succes..

Try with old usb 311 vagcom cable ( black ) and they not work.

I also try with a serial tacho soft cable, no luck.

With new Vcds it works ( Ftdi ), see att ( first post )

1 time i can read and write eeprom, after 50 times testing, nothing happends and no luck anymore..Also bootmode dont work ( error 07 )

Is the problem the cable or do i need something wrong with this prog ? I try in Win XP ( old xp )

Stefan



You have a late ME7.1.1 ecu with an ST10 processor. Nefmoto is unlikely to work.


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: MK2-VRT on November 10, 2014, 12:14:28 PM
No no, its a ME7.5 from a 1.8 20VT, not the ME7.1.1 file that i send you in pb.


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: morcegao on January 13, 2015, 06:21:19 AM
Hello everybody

I have VCDS 11.11.3 installed on my computer, it has FTDI and normally use to read and delete errors, just installing that software can read and write the ECU?


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: turboat on January 14, 2015, 03:34:43 AM
For a given set of ecus, yes.


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: vampirelo on January 27, 2015, 09:14:24 AM
Could you please advise what Layout need to be chosen for Seat Leon 1ML 906 032 ECU Reading?


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: vampirelo on March 04, 2015, 11:17:46 PM
Tryed to read ECU 022906032CN of Golf IV R32 by NefMoto VW Audi Flasher Logger 1.9.3.2
Chosen all types of Layouts and for everyone message like in attached screen shot.
Could you please suggest any advise how to read it?


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: nyet on March 04, 2015, 11:21:21 PM
Is the ECU stock? If not, bootmode it and overwrite it with a stock fie.


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: vampirelo on March 05, 2015, 01:05:36 AM
Is the ECU stock? If not, bootmode it and overwrite it with a stock fie.
There is no info about changed/tuned ECU.  :-\
And I have no stock ECU dump.


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: diagnosticator on May 04, 2015, 08:40:01 PM
@ pusher:

use KWP2000+ interface and the specific ME7edition software from AMT cartech, if you want to read the ecu on the bench, without opening it up.
Galletto is a last resort, using bootmode. Not nescessary.

Nefmoto mainly fails with ME7.5 ecu's on the bench.

Cheers,

PvL
3900 Pounds Sterling.


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: TLS4 on June 08, 2015, 02:55:18 PM
When I try to connect to my ECU it reports that it has connected and after a couple of seconds it disconnects with the message:
"Disconnecting because no response was received for the Tester Present message"
If I try to read the ECU before it disconnects it first reports:
"ECU reports that security access request was rejected" and then disconnects with the previous message.
I have not used the Nefmoto program previously so I may be doing somthing wrong.
I have tried to lower the baudrate to 57600 (and restarted the program and the ECU) without success.
My setup is a bit mixed with an A6 4B0907551S box, RS4 8D0907551Q software and a -98 euro S4 (which used to have a 8D0907551C box).
The cable is a cheap china blue.

Any ideas what I should try?

Here is the log file from the first test.

Code:
08-jun-2015 10:06:16.772: LOG: Opening NefMoto VW Audi ME7 Flasher Logger 1.9.3.2
08-jun-2015 10:06:17.483: LOG: Cannot load license file, file does not exist: C:\Documents and Settings\user\Application Data\Nefarious Motorsports\NefMoto VW Audi ME7 Flasher Logger\ImportedLicenses.License.dat
08-jun-2015 10:06:17.563: LOG: Opened NefMoto VW Audi ME7 Flasher Logger 1.9.3.2
08-jun-2015 10:06:31.022: LOG: Setting Address: 0x01 KeyByte1: 0x6B KeyByte2: 0x0F
08-jun-2015 10:06:31.113: LOG: Opened FTDI device.
08-jun-2015 10:06:31.113: LOG: FTDI device info - Description: FT232R USB UART Serial Number: A5026GPL Device Type: FT_DEVICE_232R ID: 0x4036001 Device Flags: 0x0
08-jun-2015 10:06:31.113: LOG: FTDI ChipID DLL is loaded, checking chip ID...
08-jun-2015 10:06:31.123: LOG: FTDI device chip ID: 0xF01B04DD
08-jun-2015 10:06:31.213: USER: Validated FTDI device is in dumb mode.
08-jun-2015 10:06:31.233: LOG: Starting send receive thread.
08-jun-2015 10:06:31.253: LOG: Send receive thread now started.
08-jun-2015 10:06:31.263: USER: Disconnected
08-jun-2015 10:06:31.343: LOG: Setting communication timings to defaults.
08-jun-2015 10:06:31.343: LOG: Set timing parameters to defaults.
08-jun-2015 10:06:31.353: USER: Connecting...
08-jun-2015 10:06:31.393: LOG: Setting communication timings to defaults.
08-jun-2015 10:06:31.393: USER: Starting slow init connection.
08-jun-2015 10:06:33.997: USER: Connecting to address 0x01.
08-jun-2015 10:06:36.210: USER: Slow init succeeded.
08-jun-2015 10:06:36.210: LOG: Setting Address: 0x01 KeyByte1: 0x01 KeyByte2: 0x0A
08-jun-2015 10:06:36.210: USER: Switching to KWP1281 session.
08-jun-2015 10:06:36.400: LOG: KWP1281 read block
08-jun-2015 10:06:36.460: LOG: KWP1281 sent block
08-jun-2015 10:06:36.781: LOG: KWP1281 read block
08-jun-2015 10:06:36.841: LOG: KWP1281 sent block
08-jun-2015 10:06:37.021: LOG: KWP1281 read block
08-jun-2015 10:06:37.081: LOG: KWP1281 sent block
08-jun-2015 10:06:37.231: LOG: KWP1281 read block
08-jun-2015 10:06:37.301: LOG: KWP1281 sent block
08-jun-2015 10:06:37.331: LOG: KWP1281 read block
08-jun-2015 10:06:37.402: LOG: KWP1281 sent block
08-jun-2015 10:06:37.402: USER: KWP1281 connect info: ¸D0907551Q  2.7l V6/5VT     G   0001 +Ö 
08-jun-2015 10:06:38.894: USER: Connecting to address 0x01.
08-jun-2015 10:06:41.107: USER: Slow init succeeded.
08-jun-2015 10:06:41.107: LOG: Setting Address: 0x01 KeyByte1: 0x6F KeyByte2: 0x0F
08-jun-2015 10:06:41.107: USER: Switching to KWP2000 session.
08-jun-2015 10:06:41.107: USER: Connected
08-jun-2015 10:06:43.701: LOG: Sent message with service ID TesterPresent
08-jun-2015 10:06:43.741: LOG: Received message with service ID: TesterPresentPositiveReponse
08-jun-2015 10:06:46.214: LOG: Sent message with service ID TesterPresent
08-jun-2015 10:06:46.264: LOG: Received message with service ID: TesterPresentPositiveReponse
08-jun-2015 10:06:48.738: LOG: Sent message with service ID TesterPresent
08-jun-2015 10:06:50.751: LOG: Message received no replies.
08-jun-2015 10:06:50.751: LOG: Resending message. Send attempts: 2
08-jun-2015 10:06:50.771: LOG: Sent message with service ID TesterPresent
08-jun-2015 10:06:52.774: LOG: Message received no replies.
08-jun-2015 10:06:52.774: LOG: Resending message. Send attempts: 3
08-jun-2015 10:06:52.794: LOG: Sent message with service ID TesterPresent
08-jun-2015 10:06:54.797: LOG: Message received no replies.
08-jun-2015 10:06:54.797: LOG: Failed to send message 3 times, message send failed.
08-jun-2015 10:06:54.797: USER: Disconnecting because no response was received for the Tester Present message.
08-jun-2015 10:06:54.797: USER: Disconnected
08-jun-2015 10:06:54.907: LOG: Closing FTDI device.
08-jun-2015 10:06:54.957: LOG: Send receive thread now terminated.
08-jun-2015 10:07:38.089: LOG: Closing NefMoto VW Audi ME7 Flasher Logger 1.9.3.2


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: TLS4 on June 08, 2015, 02:56:15 PM
And the second attempt:

Code:
08-jun-2015 10:08:42.522: LOG: Opening NefMoto VW Audi ME7 Flasher Logger 1.9.3.2
08-jun-2015 10:08:42.952: LOG: Cannot load license file, file does not exist: C:\Documents and Settings\user\Application Data\Nefarious Motorsports\NefMoto VW Audi ME7 Flasher Logger\ImportedLicenses.License.dat
08-jun-2015 10:08:43.032: LOG: Opened NefMoto VW Audi ME7 Flasher Logger 1.9.3.2
08-jun-2015 10:09:14.688: LOG: Setting Address: 0x01 KeyByte1: 0x6B KeyByte2: 0x0F
08-jun-2015 10:09:14.768: LOG: Opened FTDI device.
08-jun-2015 10:09:14.778: LOG: FTDI device info - Description: FT232R USB UART Serial Number: A5026GPL Device Type: FT_DEVICE_232R ID: 0x4036001 Device Flags: 0x0
08-jun-2015 10:09:14.778: LOG: FTDI ChipID DLL is loaded, checking chip ID...
08-jun-2015 10:09:14.788: LOG: FTDI device chip ID: 0xF01B04DD
08-jun-2015 10:09:14.878: USER: Validated FTDI device is in dumb mode.
08-jun-2015 10:09:14.898: LOG: Starting send receive thread.
08-jun-2015 10:09:14.918: LOG: Send receive thread now started.
08-jun-2015 10:09:14.928: USER: Disconnected
08-jun-2015 10:09:15.018: LOG: Setting communication timings to defaults.
08-jun-2015 10:09:15.018: LOG: Set timing parameters to defaults.
08-jun-2015 10:09:15.028: USER: Connecting...
08-jun-2015 10:09:15.068: LOG: Setting communication timings to defaults.
08-jun-2015 10:09:15.078: USER: Starting slow init connection.
08-jun-2015 10:09:17.682: USER: Connecting to address 0x01.
08-jun-2015 10:09:19.895: USER: Slow init succeeded.
08-jun-2015 10:09:19.895: LOG: Setting Address: 0x01 KeyByte1: 0x01 KeyByte2: 0x0A
08-jun-2015 10:09:19.895: USER: Switching to KWP1281 session.
08-jun-2015 10:09:20.096: LOG: KWP1281 read block
08-jun-2015 10:09:20.166: LOG: KWP1281 sent block
08-jun-2015 10:09:20.496: LOG: KWP1281 read block
08-jun-2015 10:09:20.566: LOG: KWP1281 sent block
08-jun-2015 10:09:20.736: LOG: KWP1281 read block
08-jun-2015 10:09:20.807: LOG: KWP1281 sent block
08-jun-2015 10:09:20.947: LOG: KWP1281 read block
08-jun-2015 10:09:21.017: LOG: KWP1281 sent block
08-jun-2015 10:09:21.047: LOG: KWP1281 read block
08-jun-2015 10:09:21.117: LOG: KWP1281 sent block
08-jun-2015 10:09:21.117: USER: KWP1281 connect info: ¸D0907551Q  2.7l V6/5VT     G   0001 +Ö 
08-jun-2015 10:09:22.619: USER: Connecting to address 0x01.
08-jun-2015 10:09:24.812: USER: Slow init succeeded.
08-jun-2015 10:09:24.812: LOG: Setting Address: 0x01 KeyByte1: 0x6F KeyByte2: 0x0F
08-jun-2015 10:09:24.812: USER: Switching to KWP2000 session.
08-jun-2015 10:09:24.812: USER: Connected
08-jun-2015 10:09:27.386: LOG: Sent message with service ID TesterPresent
08-jun-2015 10:09:27.436: LOG: Received message with service ID: TesterPresentPositiveReponse
08-jun-2015 10:09:29.910: LOG: Sent message with service ID TesterPresent
08-jun-2015 10:09:29.930: LOG: User Prompt - Title: Confirm Full Read ECU Flash Memory Message: If you are ready to read, confirm the following things:
1) You have loaded a valid memory layout for the ECU.
2) The engine is not running.
Note: Some non-standard flash memory chips may prevent reading the flash memory.

Click OK to confirm, otherwise Cancel. Result: OK
08-jun-2015 10:09:29.930: USER: Disabling Windows sleep mode.
08-jun-2015 10:09:29.970: USER: Reading ECU flash memory.
08-jun-2015 10:09:29.990: LOG: Received message with service ID: TesterPresentPositiveReponse
08-jun-2015 10:09:30.000: LOG: Reading ECU identification option: 0x9C
08-jun-2015 10:09:30.040: LOG: Sent message with service ID ReadECUIdentification
08-jun-2015 10:09:30.090: LOG: Received message with service ID: ReadECUIdentificationPositiveResponse
08-jun-2015 10:09:30.090: LOG: Read ECU identification option: 0x9C
08-jun-2015 10:09:30.090: LOG: Successfully read ECU identification information
08-jun-2015 10:09:30.120: USER: ECU reports programming session preconditions have been met.
08-jun-2015 10:09:30.120: USER: Negotiating communication timings.
08-jun-2015 10:09:30.120: LOG: Reading current communication timings.
08-jun-2015 10:09:30.210: LOG: Sent message with service ID AccessTimingParameters
08-jun-2015 10:09:30.260: LOG: Received message with service ID: AccessTimingParametersPositiveResponse
08-jun-2015 10:09:30.260: LOG: Set timing parameters to new values.
08-jun-2015 10:09:30.260: LOG: Setting communication timing to defaults.
08-jun-2015 10:09:30.320: LOG: Sent message with service ID AccessTimingParameters
08-jun-2015 10:09:30.360: LOG: Received message with service ID: AccessTimingParametersPositiveResponse
08-jun-2015 10:09:30.360: LOG: Reading current communication timings.
08-jun-2015 10:09:30.420: LOG: Sent message with service ID AccessTimingParameters
08-jun-2015 10:09:30.470: LOG: Received message with service ID: AccessTimingParametersPositiveResponse
08-jun-2015 10:09:30.470: USER: Successfully changed to new communication timings.
08-jun-2015 10:09:30.470: USER: Requesting security access.
08-jun-2015 10:09:30.500: LOG: Sent message with service ID SecurityAccess
08-jun-2015 10:09:30.551: LOG: Received message with service ID: NegativeResponse
08-jun-2015 10:09:30.551: LOG: Received negative response for service ID: SecurityAccess, with response code: GeneralReject
08-jun-2015 10:09:30.551: USER: ECU reports that security access request was rejected.
08-jun-2015 10:09:30.561: LOG: Starting ProgrammingSession diagnostic session with 124800 baud rate.
08-jun-2015 10:09:30.561: USER: Starting diagnostic session.
08-jun-2015 10:09:30.591: LOG: Sent message with service ID StartDiagnosticSession
08-jun-2015 10:09:30.641: LOG: Received message with service ID: NegativeResponse
08-jun-2015 10:09:30.641: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending
08-jun-2015 10:09:30.681: LOG: Received message with service ID: NegativeResponse
08-jun-2015 10:09:30.681: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending
08-jun-2015 10:09:30.721: LOG: Received message with service ID: NegativeResponse
08-jun-2015 10:09:30.721: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending
08-jun-2015 10:09:30.761: LOG: Received message with service ID: NegativeResponse
08-jun-2015 10:09:30.761: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending
08-jun-2015 10:09:40.615: LOG: Sent message with service ID TesterPresent
08-jun-2015 10:09:40.725: LOG: Message received no replies.
08-jun-2015 10:09:40.725: LOG: Resending message. Send attempts: 2
08-jun-2015 10:09:40.745: LOG: Sent message with service ID TesterPresent
08-jun-2015 10:09:40.855: LOG: Message received no replies.
08-jun-2015 10:09:40.855: LOG: Resending message. Send attempts: 3
08-jun-2015 10:09:40.865: LOG: Sent message with service ID TesterPresent
08-jun-2015 10:09:40.986: LOG: Message received no replies.
08-jun-2015 10:09:40.986: LOG: Failed to send message 3 times, message send failed.
08-jun-2015 10:09:40.986: USER: Disconnecting because no response was received for the Tester Present message.
08-jun-2015 10:09:40.986: USER: Disconnected
08-jun-2015 10:09:41.046: USER: Reading ECU flash memory failed.
08-jun-2015 10:09:41.146: LOG: Closing FTDI device.
08-jun-2015 10:09:41.196: LOG: Send receive thread now terminated.
08-jun-2015 10:09:49.257: LOG: User Prompt - Title: Reading ECU Flash Memory Complete Message: Reading ECU flash memory failed. Result: OK
08-jun-2015 10:09:49.257: USER: 100% complete.
08-jun-2015 10:09:49.288: USER: Restoring Windows sleep mode.


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: seany260 on July 05, 2015, 07:39:36 PM
having this issue with windows 8 x64 computer, works fine on my windows 7.
any idea why it would do this at 94%.

Bumping this post as I'm this computer full time now and it has this issue everytime I try to flash for the first time, when I select yes and it tries to flash again it works. Never seen this on my 32bit windows 7 computer.



Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: macxxx on September 10, 2015, 03:54:00 AM
Nefmoto Flasher doesn't see my KKL cable , newest drivers installed , reinstalled everything
 - no diffrence.

It's a new cable , a good quality one , made on FTDI 231x chip , maybe that's the problem? My recent cable ( a KKL on a 232BL chip ) worked like a charm.

Info from USBVIEW:

Code:
Device Descriptor:
bcdUSB:             0x0200
bDeviceClass:         0x00
bDeviceSubClass:      0x00
bDeviceProtocol:      0x00
bMaxPacketSize0:      0x08 (8)
idVendor:           0x0403 (Future Technology Devices International Limited)
idProduct:          0x6015
bcdDevice:          0x1000
iManufacturer:        0x01
0x0409: "FTDI"
iProduct:             0x02
0x0409: "FT231X USB UART"
0x0409: "FT231X USB UART"
iSerialNumber:        0x03
0x0409: "DA01G33D"
bNumConfigurations:   0x01

ConnectionStatus: DeviceConnected
Current Config Value: 0x01
Device Bus Speed:     Full
Device Address:       0x01
Open Pipes:              2

Endpoint Descriptor:
bEndpointAddress:     0x81  IN
Transfer Type:        Bulk
wMaxPacketSize:     0x0040 (64)
bInterval:            0x00

Endpoint Descriptor:
bEndpointAddress:     0x02  OUT
Transfer Type:        Bulk
wMaxPacketSize:     0x0040 (64)
bInterval:            0x00

Configuration Descriptor:
wTotalLength:       0x0020
bNumInterfaces:       0x01
bConfigurationValue:  0x01
iConfiguration:       0x00
bmAttributes:         0xA0 (Bus Powered Remote Wakeup)
MaxPower:             0x2D (90 Ma)

Interface Descriptor:
bInterfaceNumber:     0x00
bAlternateSetting:    0x00
bNumEndpoints:        0x02
bInterfaceClass:      0xFF
bInterfaceSubClass:   0xFF
bInterfaceProtocol:   0xFF
iInterface:           0x02
0x0409: "FT231X USB UART"
0x0409: "FT231X USB UART"

Endpoint Descriptor:
bEndpointAddress:     0x81  IN
Transfer Type:        Bulk
wMaxPacketSize:     0x0040 (64)
bInterval:            0x00

Endpoint Descriptor:
bEndpointAddress:     0x02  OUT
Transfer Type:        Bulk
wMaxPacketSize:     0x0040 (64)
bInterval:            0x00


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: macxxx on September 13, 2015, 04:28:29 AM
My cable works with vag-com , VCDS Lite , me7_95040.exe but no luck with nefmoto - what name or ID should it have to be seen by the ECU Flasher?





ok found a sollution - I bought a KKL cable based on 232R , works lika a charm :D


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: Perphide on March 31, 2016, 07:08:54 AM
Is it possible to get a CMD-line version of this software?


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: nyet on March 31, 2016, 10:37:15 AM
Is it possible to get a CMD-line version of this software?

I would LOVE to do this as well, but unfortunately, I do not have access to the source.



Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: Ionut on November 18, 2016, 12:38:46 PM
Is this software supported anymore?
The premium version can write just changed memory blocks? I`m tired of writing full flash for tests (dtc, readlines, small calibration changes, etc)
How much costs the premium license?


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: companyman95 on January 17, 2017, 07:26:10 PM
possible that I'm COMPLETELY retarded.... I cant seem to get the Ecu layouts to load... windows 10 laptop NefMoto's latest version. I just want to mess around with this stuff and am not sure how to get it going... help please.


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: phrozendub on April 06, 2017, 10:34:23 PM
possible that I'm COMPLETELY retarded.... I cant seem to get the Ecu layouts to load... windows 10 laptop NefMoto's latest version. I just want to mess around with this stuff and am not sure how to get it going... help please.

Post vehicle/ecu you are trying to connect to...


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: THANAS on April 13, 2017, 02:01:05 AM
I've used nefmoto flasher on many vehicles with success 99% of the time.  I've used various FTDI cables, one of which was listed in the recommended cables section.  However I end up with a problem on some vehicles with some of the cables:

Nefmoto Flasher get's stuck at "negotiating communication timings".  It will not progress further than this, regardless of how long I wait.  I close the program, cycle ignition and all is fine, no starting or programming not finished issues.  The common trend I find is the following:

The cable will work flawlessly at flashing the Mk4 GTi ecu (06A906032HP) - AUQ motor, but will not work on the Audi A3 1.8T (AUM) with the exact same bin layout, pretty much identical in every way to the Mk4, but it refuses to connect.  No problem on any vehicle with the cable using Me7Logger in FTDI mode.  It gives the same issue with some of the Polo GTis (06A906012M), some it works perfectly, some it gives 'negotiating communication timings' issues.  In the same breath, some cables will work perfectly will all of the above cars without hassle, same laptop, same drivers etc.

I get around it by using other tools, but I enjoy using Nefmoto flasher for its simplicity and speed.  Any ideas?


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: armageddon on April 13, 2017, 03:08:04 AM
Run a direct K-line and problem solved.


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: fukenbroken on April 13, 2017, 08:23:58 AM
set baud rate 38400
pull out cluster fuse after turning ignition on



Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: slappynuts 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.   


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: userpike 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.


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: slappynuts on April 29, 2017, 07:02:17 PM
The odd thing is that after a couple of tries I was able to read it.   


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: Phil_R 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


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: vwaudiguy 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.


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: Phil_R 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


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: milopl81 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



Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: 03GTI 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


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: kingnathi 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.


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: nyet on April 04, 2018, 06:33:23 PM
the msi in the first post?


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: mdlc805 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.


Title: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: nyet on September 03, 2018, 03:26:42 PM
which ross tech cable?


Title: Re: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: mdlc805 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



Title: Re: Re: NefMoto ME7 ECU Flasher and Data Logger Version 1.9.3.2
Post by: CTIGUY 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