NefMoto

Here is version 1.9.2.3 of the NefMoto software.

New in this version:

• New premium feature to detect the maximum and all communication baud rates supported by the ECU.
• Improved premium feature for fast flash reading and writing to improve the speed of the full flash read and write.
• Support for falling back to slower communication baud rates if the desired rate doesn't work.
• Allow users to continue reading or writing flash memory if the memory layout validation fails.
• Better support for starting diagnostic sessions on ECUs that return unexpected error codes.
• Better support for starting communication using slow-init on ECUs that don't accept the StartCommunication message.
• Added support for verifying if flash erasing actually failed when the incorrectly ECU reports it has failed.
• Changed the file format of the ECU Info files to better handle entries that generate invalid XML.
• Crash fix for connecting in boot mode when the ECU responds incorrectly.

This version has also changed the format of the premium license files. If you had previously purchased a premium license, then the updated license file should already be waiting for you in your email inbox. If you have any problems with the new license files, or if you didn't not receive an updated license, just let me know.

Attached is the installer for the NefMoto software, and as always the FTDI USB drivers if you don't already have them.

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

I'll give it a spin shortly and thank you for license email.

I have yet to be successful reading from an immo car. Am i missing the point, or doing it wrong.

Are you reading in the car or on the bench?
Can you post your log file?

I repeated the process tonight and everything installed properly.

Thanks Tony.

I just added a new version updated from 1.9.2.0 to 1.9.2.1 that includes a bunch of small fixes for EDC15. You should only care about this small update if you are testing with EDC15.

if i use the detect supported baudrates button, my ecu responds to 200.000+baud, which is awesome, and the flashing speed is VERY nice, BUT, if i close the program and then open it again it reverts back to 124800 since this is the highest value available in the drop down box..
..and so i need to to another detection to enable this 200.000+ baud-rate.. which is rather counter-productive since the detection takes longer time then to just flash at 124800.. is it possible to fix this so that the program remembers the last detected value for my deviceID when closing and reopening it? =)

It is supposed to remember the supported baud rates. There may be an issue with it resetting the detected speeds if the USB cable is not connected when the program opens. I will try to do a small update to fix this issue.

I updated the installer in the original post to version 1.9.2.2. This updated version has a few more fixes for the EDC15 guys.

Will this program work with a KWP2000+?  I have tried and cannot get it to connect with the ECU?

->http://www.nefariousmotorsports.com/wiki/index.php/NefMoto_ECU_Flashing_Software (http://www.nefariousmotorsports.com/wiki/index.php/NefMoto_ECU_Flashing_Software)

Maybe this is a dumb ?, but all new releases here on out of the Nefmoto software will be Windows XP compatible? Thanks :P

Yup, all new releases are compatible with Windows XP SP2 and later.

Hi Tony,

I can't seem to get the logger working.

I've got an Audi A4 binary that is not working with Setzi's ME7Info program to find the RAM variable addresses.  Does anyone know how to find these addresses in the binary itself using WinOLS or other programs?

Using another binary that does work with the ME7Info I can find a lot of references to those addresses in the code but I'm really looking for a more concentrated table.  Are there other techniques people are using to find the addresses?

Thanks

Right now everyone is using Setzi's ME7Logger to generate variable locations. Doing it manually is very very hard.

Thanks Tony. Awesome.

I just posted another small update and bumped the version number to 1.9.2.3.

The update includes a bug fix for the premium feature licensing system when used on Windows XP SP2.

Hello!
I'm trying to read an ecu 1ML 906 032 of a seat leon. this ecu has inside the 95040 file of my audi S3 (putted with me7 95040 software). the car starts and run without problems. whe I want to read ecu with nefmoto software, I read ecu information and when I try to read flash file (with memory layout 29F800, 29F800BB or 29F800BT), the software go in error for IMMOBILIZER NOT AUTHENTICATED: what can I do???

I'm not sure what I am doing wrong but any help would be appreciated.  When I run the program it will connect with fast init but when I try to do anything the program just disappears.  If I click slow inti the program disappears????????????  Any ideas.

Check the nefmoto log file and event viewer in control panel/administrative tools for anything abnormal?

I looked and did not see any errors.  I am not a computer guru so not exactly sure what I am looking for.  I wonder if it could be because I have the FT232BN chip instead of the FT232R chip????

Does the flasher not work w/ 1.8T's?

I get the following error:

Validation failed, ECU reports RequestUpload service is not supported. RequestUpload may have been disabled by aftermarket engine software.
100% complete.

Work fine with my 1.8T (AUQ).

Maybe try flashing back to stock first?

Both the current own and I are fairly certain it is stock... and the previous owner says 100% that the car was never flashed.

I will have to try a bench flash

Also just got a call from my buddy... he said the CEL came on after he drove home last night... scanned code shows something along the lines of (software programming not complete) and he says there is no boost and the car is very slow.

I never even tried a write... only read and that failed.

hey Tony - i believe i bricked my ecu today, not real sure.  the car starts and then immediately shuts off.  the check engine light and epc light flash even with the engine off yet the ignition turned to on.  here's the error i'm getting from your program, which is a bit strange, because it looks like its connecting but not allowing writing.  please let me know what to do from here.  i've never bricked the ecu in over a year of using your software, so a bit nervous here... lol

any idea?

just checked the log and here's the output from today:

27/Feb/2012 06:19:01.591: LOG: Setting Address: 0x01 KeyByte1: 0x6B KeyByte2: 0x0F
27/Feb/2012 06:19:01.640: LOG: Opened FTDI device.
27/Feb/2012 06:19:01.641: LOG: FTDI device info - Description: FT232R USB UART Serial Number: A800ecWH Device Type: FT_DEVICE_232R ID: 0x4036001 Device Flags: 0x0
27/Feb/2012 06:19:01.641: LOG: FTDI ChipID DLL is loaded, checking chip ID...
27/Feb/2012 06:19:01.650: LOG: FTDI device chip ID: 0x3302ADF1
27/Feb/2012 06:19:01.698: USER: Validated FTDI device is in dumb mode.
27/Feb/2012 06:19:01.749: LOG: Starting send receive thread.
27/Feb/2012 06:19:01.750: LOG: Send receive thread now started.
27/Feb/2012 06:19:01.780: USER: Disconnected
27/Feb/2012 06:19:01.802: LOG: Setting communication timings to defaults.
27/Feb/2012 06:19:01.802: LOG: Set timing parameters to defaults.
27/Feb/2012 06:19:01.802: USER: Connecting...
27/Feb/2012 06:19:01.824: LOG: Setting communication timings to defaults.
27/Feb/2012 06:19:01.824: USER: Starting fast init connection.
27/Feb/2012 06:19:01.824: USER: Connecting to address 0x01.
27/Feb/2012 06:19:04.556: USER: Fast init sent, sending start communication request.
27/Feb/2012 06:19:04.596: LOG: Received message with service ID: StartCommunicationPositiveResponse
27/Feb/2012 06:19:04.596: LOG: Setting Address: 0x01 KeyByte1: 0x6F KeyByte2: 0x0F
27/Feb/2012 06:19:04.596: USER: Switching to KWP2000 session.
27/Feb/2012 06:19:04.597: USER: Connected
27/Feb/2012 06:19:07.073: LOG: Sent message with service ID TesterPresent
27/Feb/2012 06:19:09.076: LOG: Message received no replies.
27/Feb/2012 06:19:09.076: LOG: Resending message. Send attempts: 2
27/Feb/2012 06:19:09.095: LOG: Sent message with service ID TesterPresent
27/Feb/2012 06:19:11.098: LOG: Message received no replies.
27/Feb/2012 06:19:11.099: LOG: Resending message. Send attempts: 3
27/Feb/2012 06:19:11.117: LOG: Sent message with service ID TesterPresent
27/Feb/2012 06:19:13.120: LOG: Message received no replies.
27/Feb/2012 06:19:13.121: LOG: Failed to send message 3 times, message send failed.
27/Feb/2012 06:19:13.121: USER: Disconnecting because no response was received for the Tester Present message.
27/Feb/2012 06:19:13.122: USER: Disconnected
27/Feb/2012 06:19:13.188: LOG: Closing FTDI device.
27/Feb/2012 06:19:13.198: LOG: Send receive thread now terminated.
27/Feb/2012 06:19:32.886: LOG: Closing NefMoto VW Audi ME7 Flasher Logger1.9.2.2


also here's the log of the last flash which occured right before the issue:
27/Feb/2012 06:01:58.993: LOG: Received negative response for service ID: RequestRoutineResultsByLocalIdentifier, with response code: RoutineNotCompleteOrServiceInProgress
27/Feb/2012 06:01:58.995: LOG: Sent message with service ID RequestRoutineResultsByLocalIdentifier
27/Feb/2012 06:01:59.012: LOG: Received message with service ID: RequestRoutineResultsByLocalIdentifierPositiveResponse
27/Feb/2012 06:01:59.013: LOG: Checksum is correct.
27/Feb/2012 06:01:59.014: USER: Flash checksum matches new data, flashing was successful.
27/Feb/2012 06:01:59.014: USER: Disconnecting from ECU to force it to recognize successful completion of flash write.
27/Feb/2012 06:01:59.026: USER: Writing ECU flash memory succeeded. Wrote 19 of 19 sectors in flash memory.
Flashing time was 00:00:54.
27/Feb/2012 06:02:00.245: USER: Restoring Windows sleep mode.
27/Feb/2012 06:02:00.305: USER: Disconnecting...

I've had that happen to me a few times.. it's always been a checksum issue... If you're using the MTX plug in, use another way to correct your files or at least check them after using the MTX-plug in

definitely always use me7checker after the mtx-auto-write for tuner pro.  this time it said no problem as usual.  a strange new thing is occuring now.  the throttle body is making nasty clicking noises, like its recalibrating.  the epc and CEL are flashing slowly but consistently.  headed out to try vagcom now, maybe clear a code or perform an adaptation of the tb, fingers crossed.  any idea?

other then flashing back a different program, no.

but your experience is identical to mine, and it was always a checksum issue from the MTX plug in... WinOLS would find an invalid checksum on the file that did that to me.

I had to use my Galletto cable in boot mode to recover FWIW.

I cant get the utility to read my ecm.  I want to save the current tune just in case and it just gets hung up "negotiating communication timings"

LOG:
28/Feb/2012 07:55:19.898: LOG: Sent message with service ID TesterPresent
28/Feb/2012 07:55:19.913: LOG: Received message with service ID: TesterPresentPositiveReponse
28/Feb/2012 07:55:22.403: LOG: Sent message with service ID TesterPresent
28/Feb/2012 07:55:22.416: LOG: Received message with service ID: TesterPresentPositiveReponse
28/Feb/2012 07:55:24.908: LOG: Sent message with service ID TesterPresent
28/Feb/2012 07:55:24.920: LOG: Received message with service ID: TesterPresentPositiveReponse
28/Feb/2012 07:55:27.413: LOG: Sent message with service ID TesterPresent
28/Feb/2012 07:55:27.424: LOG: Received message with service ID: TesterPresentPositiveReponse
28/Feb/2012 07:55:29.917: LOG: Sent message with service ID TesterPresent
28/Feb/2012 07:55:29.929: LOG: Received message with service ID: TesterPresentPositiveReponse
28/Feb/2012 07:55:30.964: USER: Disabling Windows sleep mode.
28/Feb/2012 07:55:30.978: USER: Reading ECU flash memory.
28/Feb/2012 07:55:31.054: LOG: Reading ECU identification option: 0x9C
28/Feb/2012 07:55:31.057: LOG: Sent message with service ID ReadECUIdentification
28/Feb/2012 07:55:31.080: LOG: Received message with service ID: ReadECUIdentificationPositiveResponse
28/Feb/2012 07:55:31.094: LOG: Read ECU identification option: 0x9C
28/Feb/2012 07:55:31.094: LOG: Successfully read ECU identification information
28/Feb/2012 07:55:31.100: USER: ECU reports programming session preconditions have been met.
28/Feb/2012 07:55:31.101: USER: Negotiating communication timings.
28/Feb/2012 07:55:31.101: LOG: Reading current communication timings.
28/Feb/2012 07:55:31.107: LOG: Sent message with service ID AccessTimingParameters
28/Feb/2012 07:55:31.132: LOG: Received message with service ID: AccessTimingParametersPositiveResponse
28/Feb/2012 07:55:31.132: LOG: Setting communication timing to defaults.
28/Feb/2012 07:55:31.137: LOG: Sent message with service ID AccessTimingParameters
28/Feb/2012 07:55:31.156: LOG: Received message with service ID: AccessTimingParametersPositiveResponse
28/Feb/2012 07:55:31.156: LOG: Reading current communication timings.
28/Feb/2012 07:55:31.161: LOG: Sent message with service ID AccessTimingParameters
28/Feb/2012 07:55:31.212: LOG: Received message with service ID: AccessTimingParametersPositiveResponse
28/Feb/2012 07:55:31.212: USER: Successfully changed to new communication timings.
28/Feb/2012 07:55:31.214: USER: Requesting security access.
28/Feb/2012 07:55:31.217: LOG: Sent message with service ID SecurityAccess
28/Feb/2012 07:55:31.257: LOG: Received message with service ID: NegativeResponse
28/Feb/2012 07:55:31.258: LOG: Received negative response for service ID: SecurityAccess, with response code: GeneralReject
28/Feb/2012 07:55:31.260: USER: ECU reports that security access request was rejected.
28/Feb/2012 07:55:31.260: LOG: Starting ProgrammingSession diagnostic session with 124800 baud rate.
28/Feb/2012 07:55:31.261: USER: Starting diagnostic session.
28/Feb/2012 07:55:31.264: LOG: Sent message with service ID StartDiagnosticSession
28/Feb/2012 07:55:31.309: LOG: Received message with service ID: NegativeResponse
28/Feb/2012 07:55:31.310: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending
28/Feb/2012 07:55:31.349: LOG: Received message with service ID: NegativeResponse
28/Feb/2012 07:55:31.350: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending
28/Feb/2012 07:55:31.389: LOG: Received message with service ID: NegativeResponse
28/Feb/2012 07:55:31.390: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending
28/Feb/2012 07:55:31.429: LOG: Received message with service ID: NegativeResponse
28/Feb/2012 07:55:31.430: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending
28/Feb/2012 07:55:31.469: LOG: Received message with service ID: NegativeResponse
28/Feb/2012 07:55:31.470: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending
28/Feb/2012 07:55:31.505: LOG: Received message with service ID: NegativeResponse
28/Feb/2012 07:55:31.505: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending
28/Feb/2012 07:55:31.545: LOG: Received message with service ID: NegativeResponse
28/Feb/2012 07:55:31.545: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending
28/Feb/2012 07:55:31.583: LOG: Received message with service ID: StartDiagnosticSessionPositiveResponse
28/Feb/2012 07:55:31.584: LOG: Setting communication timings to defaults.
28/Feb/2012 07:55:31.584: LOG: Set timing parameters to defaults.
28/Feb/2012 07:55:31.584: LOG: Changed diagnostic session type to: ProgrammingSession
28/Feb/2012 07:55:31.584: LOG: ECU requesting specific baud rate: 124800
28/Feb/2012 07:55:31.587: USER: Successfully started diagnostic session.
28/Feb/2012 07:55:31.588: USER: Negotiating communication timings.
28/Feb/2012 07:55:31.588: LOG: Reading current communication timings.
28/Feb/2012 07:55:31.656: LOG: Sent message with service ID AccessTimingParameters
28/Feb/2012 07:55:31.929: LOG: Could not construct valid message from received data: InvalidChecksum
28/Feb/2012 07:55:31.929: LOG: Removing first byte from the receive buffer to try to create a valid message. Removed: 0x07
28/Feb/2012 07:55:31.958: LOG: Could not construct valid message from received data: InvalidChecksum
28/Feb/2012 07:55:31.958: LOG: Removing first byte from the receive buffer to try to create a valid message. Removed: 0x07
28/Feb/2012 07:55:31.988: LOG: Could not construct valid message from received data: InvalidChecksum
28/Feb/2012 07:55:31.989: LOG: Removing first byte from the receive buffer to try to create a valid message. Removed: 0x07
28/Feb/2012 07:55:32.018: LOG: Could not construct valid message from received data: InvalidChecksum
28/Feb/2012 07:55:32.018: LOG: Removing first byte from the receive buffer to try to create a valid message. Removed: 0x07
28/Feb/2012 07:55:32.048: LOG: Could not construct valid message from received data: InvalidChecksum
28/Feb/2012 07:55:32.049: LOG: Removing first byte from the receive buffer to try to create a valid message. Removed: 0x07
28/Feb/2012 07:55:32.078: LOG: Could not construct valid message from received data: InvalidChecksum
28/Feb/2012 07:55:32.080: LOG: Removing first byte from the receive buffer to try to create a valid message. Removed: 0x07
28/Feb/2012 07:55:32.108: LOG: Could not construct valid message from received data: InvalidChecksum
28/Feb/2012 07:55:32.108: LOG: Removing first byte from the receive buffer to try to create a valid message. Removed: 0x07
28/Feb/2012 07:55:32.138: LOG: Could not construct valid message from received data: InvalidChecksum
28/Feb/2012 07:55:32.138: LOG: Removing first byte from the receive buffer to try to create a valid message. Removed: 0x07
28/Feb/2012 07:55:32.168: LOG: Could not construct valid message from received data: InvalidChecksum
28/Feb/2012 07:55:32.168: LOG: Removing first byte from the receive buffer to try to create a valid message. Removed: 0x07
28/Feb/2012 07:55:32.200: LOG: Could not construct valid message from received data: InvalidChecksum
28/Feb/2012 07:55:32.200: LOG: Removing first byte from the receive buffer to try to create a valid message. Removed: 0x07

Just bringing this to your attention tony... this issue still exists:  http://nefariousmotorsports.com/forum/index.php?topic=633.0title=

In my case the car starts, but all I did was try to validate the memory and after this appeared:

18089 -  Control Module Programming Not Finished
            P1681 - 35-00 -   -

I figured it out after reading soemone elses post in this thread.  I changed the baud rate to 52800. 

Tony,

This tool just continues to get better and better, please keep up the great work.

I tried out the logging feature tonight and it really didn't work quite right for me..... It made log files but without live data. I know this new feature is still a work in progress.

Anyway, what I really wanted to comment on was the use of XML files for logs; XML files like this log have a significant amount of overhead. This will result in massive log files. Perhaps a simple CSV or a JSON file might be better suited?

that happened on old versions if you forgot to disconnect.  this new one auto disconnects after flashing.  maybe that function is goofing at times?

Not sure, since I wasn't able to even do a read/verify... I just connected but none of the functions would work.

After disconnecting and turning on the car the above error appeared.

China galletto cables arent supported by nefmoto ecu flasher?
Mouseover shows the this cable is compatible for premium license.
Trying to connect with KWP2000 without success (No FTDI response).

You cannot use a galletto cable w/ NefMoto.

Read this thread for recommended cables: http://nefariousmotorsports.com/forum/index.php?topic=325.0title=

Hi, i try to read and flash a Me7.5 but it doesn't work, when the read of flash begin "immobilizer not recognized"
It's normal? thanks

-

-

So the boot mode is not working yet or? I have a bricked allroad ecu (communication error during flash) and can not get nef to connect to it with the pads or pin 24 shorted. any suggestions?

im going to have to remove my s4's ecu and swap it in to the allroad so it can be driven, its my wifes moms car.

EDIT: and im retarded, i did some reading and found that boot mode should connect but i wouldnt have been able to do anything.

UPDATE: Removed power for 30+ mins and was able to flash a new file on. Car runs now. Thanks for making a good tool Tony.

So this error code was stored after you tried to read the ECU and the ECU reported that reading wasn't supported?

You didn't try doing a "Check If Flash Matches" operation did you?

This error code could be getting stored because the software uses a checksum operation to determine if a memory sector needs to be read before reading the sector. If the ECU doesn't support reading but does support checksum calculations, then it is possible the checksum calculation causes the error code to be stored. Then since you can't read the ECU there is no way to complete the read operation which would clear the error code.

I just posted the next release of the NefMoto software here: http://nefariousmotorsports.com/forum/index.php?topic=1686.0

This release adds fast data logging using the same method as the ME7 Logger software.