NefMoto

Please see the new 1.4.0.1 release at: http://nefariousmotorsports.com/forum/index.php?topic=145.0



Summary:
The NefMoto ME7 ECU flasher is a free tool that allows you to reprogram your ME7 ECU in car over the OBD port.

Features:
-ECUs can be programmed in car over the OBD port.
-Flashing of 1 megabyte 29F800 ECUs in about 4 minutes or less.
-User defined memory layouts allow for flashing any memory arrangement. Supplied with B5 Audi S4 ME7.1 layout for quick start.
-Flashing erases and programs one memory sector at a time to allow you to recover the ECU in case of failure.
-Flashed data is verified with checksums to insure data was flashed correctly.

This software does NOT:
-Does not update checksums or validate the file you are flashing in any way.
-Does not currently allow you to read the ECU. (coming next update)
-Does not allow you to edit any maps, value, etc. It is just for flashing.

Features coming soon:
-Reading the ECU flash memory (Planned for the week of July 19-25)
-Reading and clearing error codes (Hopefully by the end of July)

System requirements:
-32bit or 64bit Windows Vista or Newer
-.NET 3.5 (installed as part of install process)
-FTDI USB D2XX driver (installed as part of install process)
-3 megabytes of free hard drive space

Tested supported cables:
-eBay USB VAG KKL
-Ross-Tech HEX-KEY-CAN (operating in dumb mode)
-Any dumb OBDII cable using the FTDI USB chip

Test unsupported cables:
-Galletto
-KWP2000+ Flasher

ECUs known to be supported:
-2000/01/02 Audi S4 2.7t ME7.1
-2000/01/02 Audi A6 2.7t ME7.1

Tested supported ECUs using the B5 S4 2.7T ME7.1 29F800 memory layout:
-2000 Audi S4 6sp - 8D0907551A - software 1037 35 2345 - hardware 0261 206 110
-2000 Audi S4 tip - 8D0907551B - software 1037 35 2738 - hardware 0261 206 109
-2001 Audi S4 tip - 8D0907551L - software 1037 35 4145 - hardware 0261 207 004
-2001 Audi S4 6sp - 8D0907551H - software 1037 35 4774 - hardware 0261 206 774
-2001 Audi S4 6sp - 8D0907551M - software 1037 35 4837 - hardware 0261 207 143
-2001 Audi S4 6sp - 8D0907551M - software 1037 36 0857 - hardware 0261 207 143
-2002 Audi S4 tip - 8D0907551AA - software 1037 36 2276 - hardware 0261 207 453
-2002 Audi S4 6sp - 8D0907551T - software 1037 36 2558 - hardware 0261 207 452
-2000 Audi A6 tip - 4B0907551L - software 1037 35 2815 - hardware 0261 206 562
-2001 Audi A6 tip - 4B0907551T - software 1037 36 0864 - hardware 0261 207 005

Known issues:
-Sometimes it takes 3 or 4 connection attempts to successfully connect. This is because I have to use the old school slow init method to ensure I can connect to all ECUs, including ones that have been corrupted by incomplete flashing.

The MSI installer is attached at the bottom of this post, but you must be logged in to see it.

The day has come, Bravo!!!

(http://www.digital-kaos.co.uk/forums/images/smilies/congrats.gif)(http://www.digital-kaos.co.uk/forums/images/smilies/congrats.gif)(http://www.digital-kaos.co.uk/forums/images/smilies/congrats.gif)(http://www.digital-kaos.co.uk/forums/images/smilies/congrats.gif)


Any plan to include support for 1.8t?

agreed

Well done, can't wait to check this out! Good work, Thanks Tony!

only for vista?

 :(

Vista and newer versions of Windows has added a lot of nice features my software that XP doesn't support.

Windows 7 is worth upgrading for.

If there are enough users that still need XP support, I can look into supporting it in the future.

The software should already support the 1.8T. We just need to create the memory layout file for it.

If you tell me which flash memory chip the 1.8T ECU uses, we could easily create a new memory layout file and test it out.

The trick is depending on the model and year of car, they all use different flash chips like 29F800, 29F400, and 29F200. And to support flashing one sector at a time, you need to know which chip the ECU is using.

You could flash the entire chip at once, but then if you get have any failures, the ECU is bricked and need to be flashed in boot mode. By flashing one sector at a time, with most failures the ECU is smart enough to go into a fail safe programming recovery mode. This allows you to try to flash again without needing to do boot mode.

Memory layout seems fine to me, my chip is 800BB. I'm getting "programming preconditions have not been met" error.

It should also say which programming precondition was not met. Did it list one?

Maybe I will make it an option to try to flash the ECU anyway even when the ECU reports it is not ready.

I also started a wiki page on which ECUs use which flash chips:
http://nefariousmotorsports.com/wiki/index.php?title=Car_Specific_ECU_Info

Congratulations Tony!!

congatulations

the first 1.8T which came with ME7 has 400BB chip. The late has 800bb

99 - 2000 has 400bb / 2001+ has 800bb

;)

very nice. im going to be even more busy haha

I posted a new updated installer in the first post.

Version 1.3.1.1 allows you to attempt to program even if the the ECU reports that the flashing preconditions have not been met.

To upgrade, just uninstall the old version, and then run the installer for the new version.

Please let me know what problems or success your are having so I can make this better.  :D

Looks like the FTDI driver doesn't like W7 x64.  I downloaded the 64 bit installer for the D2XX drivers, but I'm going to guess that I need to change the VID and PID in the inf?

edit:  I changed the VID and PID in the 2.06.00 release from http://www.ftdichip.com/Drivers/D2XX.htm and all is well.  I attached the modified driver package.  You will have to agree to installing the unsigned driver as a result.  Unfortunately I can't test it as I don't want to overwrite my current flash.

So we can not download our current tune from the ecu to our computer with this version? Or did I read that wrong?

Josh

I succeeded flashing my 1.8t ecu using version 1.3.0.1, it took 4:05 to write whole flash, I wonder if it could even be writen in less time just skipping blocks that match ckecksum. Congratulations your software is amazing.
Also, found that the voltage needed to write the ecu is much lower than I thought. This morning when I realized that the passengers seat heater was turned on, the battery was discharged to the point of being unable to start the car and I could still flash the ecu at 9.5v :o.

Support for reading ECUs is coming in the next update that I will hopefully release next week. Stay tuned!  ;D

Awesome! Glad to hear my software works with the 1.8T! Can you post the year, and part number, etc for the ECU so I can update the list of supported ECUs?

Were you using version 1.3.1.1 that allows you to bypass the flash precondition check with the confirmation dialog? If so, can you tell me which precondition it says doesn't pass?

How does the 4 minute flash compare to Galletto or KWP2000?

You can flash the ECU by only updating the flash chip sectors that don't match. Doing it that way takes about 1 minute instead of 4. I just haven't enabled that feature in the current release.

Thank you for taking the time to investigat the x64 issue. I will try to test again on a Win7 x64 machine myself. I swear I already tested it, but maybe something changed. I would have thought that the VID and PID of the USB device would be the same regardless of being 32 or 64bit.

EDIT:

I looked at your modified driver files. It seems you changed the VID and PID values from the FTDI default to the values that are used for the Ross-Tech VAG-COM cable. I'm not sure if your issue has to do with running 64bit Windows, but instead may have to do with not having the Ross-Tech FTDI driver installed.

Actually, the issue I had was that dpinst.exe can't install the x64 drivers... this is what I first got when I launched the flash tool... sorry I forgot to attach before:

(http://gallery.trumpio.com/main.php?g2_view=core.DownloadItem&g2_itemId=42812&g2_serialNumber=1)

It will probably be a while before I can find one of my spare ECU's to test it.

Stupid DPInst.exe

DPInst is the Microsoft driver preinstaller. I will double check the configuration and try to find out the problem with installing the drivers on an x64 system.

Thanks for taking the time to give me the exact error message.

It will work on any post-2002 1.8T and perhaps in others as well. I will update this list later.
8N0906018AL
8N0906018AQ
8N0906018AM
8N0906018AP
06A906032HS
06A906032ML
06A906032HJ
06A906032KP
06A906032EN
06A906032HF
06A906032HN
06A906032HK
06A906032HR
06A906032HP
06A906032LP
06A906032LQ
06A906032PL

I was using version 1.3.0.1... "Precondition unknown" arised when I tried to flash the ecu on bench, same situation happens in the car if I pull the instrument panel fuse. I will report back after trying to flash on bench with version 1.3.1.1.

It's like day and night, kwp2000 needs 20 minutes to flash the ecu.

I would love to have that feature, when do you think it will be available?

Can you add support for XP? Most of my other OBD programs run on XP MCE so it would be nice to have this.
Will the option to read/save currect ECU file be available soon?

I got the same DPinst error on Win7 x64 system - hope you can fix it soon.
4-minute flashing time is still very fast compared to 25 minutes with ebay clone, but enabling the update by sector feature would be awesome.

I am hoping to release an update tonight that supports reading ECUs, and fixes the driver issue for 64 bit systems.

Supporting Windows XP is something that will take a few weeks of work. It would require me to rewrite one of my core systems. I will look into how feasible it is.

Did you test flashing all of these ECUs using the 29F800BB memory layout file, or do you just believe they should work?
Also some of these ECU numbers are for Volkswagen's, does that mean I can assume the flashing software is working for VWs too?

Does the issue with flashing preconditions only occur when flashing on the bench or with the instrument cluster fuse pulled? Does it report that all of the preconditions are met when flashing in the car?

Glad to hear it is working well. :D


As for the 1 minute ECU flash which updates only memory sectors that are different, I am hoping to release that feature in the future with a few other advanced features. And for that release I am planning on releasing my own USB OBDII cable.

having issues with the dll files.  any ideas?

(http://i97.photobucket.com/albums/l214/boomerw/failedtoloadftd2xxdll.jpg)

Looks like the FTDI drivers aren't installed. Check the latest release, and be sure to install attached 2.06.00 FTDI D2XX drivers.

Please see the newer 1.4.0.1 release at http://nefariousmotorsports.com/forum/index.php?topic=145.0

Sounds fair enough, thanks.