NefMoto

(http://www.nefariousmotorsports.com/hosted_files/NefMoto ME7 ECU Flasher 1.6.1.0 Screen Shot.jpg)

Summary:
The NefMoto ME7 ECU flasher is a free tool that allows you to read and write the flash memory in your ME7 ECU in car over the OBD port. All that is required is a FTDI based USB OBD cable that works in "dumb" mode. Dumb mode cables pass the raw serial data straight through without applying any higher level protocols.

Features:
-ECUs can be written through the OBD port in about three and half minutes.
-ECUs can be read through the OBD port in about five minutes.
-User defined memory layouts allow for flashing any memory arrangement.
-Writing erases and programs one memory sector at a time to allow you to recover the ECU in case of failure.
-Written and read data is verified with checksums to insure data was sent correctly.
-Reading and clearing error codes is also supported.

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

System requirements:
-32bit or 64bit Windows Vista or Newer (Will work if run inside a virtual Windows machine on Mac and Linux as well)
-.NET 3.5 (installed as part of install process)
-FTDI USB D2XX driver version 2.06.00 or later
-3 megabytes of free hard drive space

Tested supported cables:
-eBay USB VAG KKL using the FTDI D2XX standard driver
-Ross-Tech HEX-KEY-CAN using the Ross-Tech FTDI D2XX driver ("boot in intelligent mode" must be unchecked in the VCDS options screen)
-Any dumb OBDII cable using the FTDI USB chip

Tested unsupported cables:
-Galletto (Does not support dumb mode)
-KWP2000+ Flasher (Does not support dumb mode)
-Old Ross-Tech KEY-USB (Does not support true dumb mode)

Tested supported ECUs list on the wiki:
http://nefariousmotorsports.com/wiki/index.php?title=NefMoto_ECU_Flashing_Software

Known issues:
-No known issues. Please let me know if you find any.

How to install:
Please uninstall any previous versions of the NefMoto ME7 ECU Flasher before installing the latest version.
To install, download and run the attached file ECUFlasherHostInstaller 1.6.1.0.msi.
Then ensure that you have the FTD2XX driver installed for your specific cable.
If you have a generic cable, download CDM20600.zip, then extract it and install the generic FTDI D2XX driver.

What is new in this release:
-Better support for 2003/2004 VW and Audi.
-Better communication time outs that take USB latency into account.
-All buttons in the user interface now have tool tips explaining what they do and why they may be disabled.

UPDATE:
A new build of the 1.6.1.0 installer has been attached to the first post which resolves everyone's installation issues.

I installed 1.6.1.0 today and can't get it to launch.  Error I get is "The application was unable to start correctly (0xc0000142).  Click OK to close the application."

Previous version worked fine.  Uninstalled previous version first.  Uninstalled new version, reinstalled old version; works fine.

OS is Win 7 Ultimate x64

Tried read mode with 1.6.0.0  Car is '02 Jetta w/ 2.8 12V AFP code engine.  Bosch ME 7.1  ID is correct.  Everything worked except read never became enabled.  Slow init, fast init, ECU info, DTC's.  Using Ross-Tech HEX+CAN.  Here's the log file

BTW I can dump with Tacho 3.01 no problem.

Did you select a memory layout - that is required.

Vag Tacho can't dump the ecu flash, it may be able to read portions of the eeprom though.

I say dump I don't mean it can remove file.  But it reads to memory buffer and then I can view or save it.  I'll attach it as a .txt file here

Thanks about memory layout.  I'll have to look at it again tomorrow.  I still don't know why I can 't use the new one.

This not working on my laptop (Win7 Ulti x64).  I tried it on another running Vista Home Premium SP2.  Everything is up to date.  When I try to start it I get dependency errors.  Probably on my end, but thought you might like the error log.

(http://i1113.photobucket.com/albums/k514/ssgacc/startuperror.jpg?t=1293902892)

Broken here too...  "The application was unable to start correctly (0xc0000142).  Click OK to close the application.

I cleaned up the corrupt/missing dll's on the Vista machine.  Now I'm stuck at the same (0xc0000142) message on that machine too.  Seems it's a delay issue with ieframe.dll?

Is it only people on 64bit machines that are having a problem with the new release?

My next suggestion would be trying to install the .NET 3.5 full version.
http://www.microsoft.com/downloads/en/details.aspx?FamilyId=333325FD-AE52-4E35-B531-508D977D32A6&displaylang=en

Yeah, x64... no whammy on 2 machines, both up to date...

My laptop is Vista 32bit and getting the error "API-MS-Win-Core-ProcessThreads-L1-1-0.dll was not found".In my attempt to fix this I found that windows 7 has added a apiset stub for processes such as CreateProcessA. Simply downloading those .dll files to my vista machine did not work as it could not initialize the dll's. Has anyone managed to get this working on vista? Also may I ask why the use of .net rather than something that will require less dependancies?

Happy New Year Everyone!

I tested this new version in Windows 7 Starter Edition with all updates.  No problem launching the program.  I loaded the memory layout for my Audi 2003 A4 and got an error.  I press disconnect then connect and the problem was solved.  I used a Ross Tech USB compatible cable.

The program read the ECU in less than 4 minutes with no mistakes.  ALL PERFECT!

Writing a tuned file to the ECU was also successful although I got this error after 94%:

"Requesting flash memory erase for address range 0x008F0000 to 0x008F7FFF.
Failed to erase flash memory.
100% complete.
Writing ECU flash memory failed."

This is just a GREAT program.  I couldn't read or clear DTC's but it is near to perfection on the next version I think. 

How many of you modified your own original obtained files? 
Does the US have car shops that can tune or MOD the file you obtain?

Pretty sure they most be cheaper tha GIAC, Revo, APR or Unitronics I think.

Up-to-date Windows 7 Ultimate x64 w/ .NET 4.0 - getting the same unhandled exception as the other guys in this thread.

Runs fine here on a Windows 7 Enterprise fresh install.

But I still can't read the firmware or even test memory layout from my A8's ME7.1.
Software displays "no answer to Tester present message" or something, and the ECU records an error "clamp 30 voltage too low".
It seems that with my charger I cannot get voltage above about 12.3V .. even though the powercap in my trunk displayed 13.9 in this case. Does the ECU check voltage when entering programming mode, or could this be a side effect of some other issue?

I pulled the instrument cluster's fuse this time but it didn't make any difference..

You need to try it on the Bench.

My ECU refuses to be read in car.

Rick

I have attached a new version of the 1.6.1.0 release to the first post in the thread.

I am not sure what went wrong with the original release, but as far as I can tell it should be resolved now. Sorry for the inconvenience.

woohoo!  Installed and working fine on both machines that had problems before.

Loaded for me now also  :)

Were you able to resolve the issue on your A8? If not can you send me some log files?

im having connection problems,c box ecu o261206108 8d0907551c,i can connect to ecu on bench and read dtcs but cannot read flash,only'read ecu info-'read dtc's'-'clear dtc's' are highlighted,any ideas?reading with vagcom hex usb intelligent mode off

ahhh i didnt choose a memory layout,now im getting immobliser not auhenticated...

If it says immoblizer not authenticated, then that is most likely caused by trying to flash the ECU on the bench. When the ECU has the immobilizer enabled, it must be in communication with the immobilizer unit in the car, and the immobilizer data must be correct.

You will need to reinstall the ECU in the car, or disable the immobilizer data in the ECU.

thanks tony,il try reading in car,are the c box ecu,s supported?

S4 C box ECUs are supported assuming the ECU supports reading the flash memory. Some early S4 ECUs do not appear to support reading and writing the ECU flash memory via the KWP2000 protocol.

if i switch vagcom settings to kwp 1281 protocol and try and read it connects then re connects using kwp2000,it will allow access to fault codes but still not read access,i have tried reading in and out of the car with 3 different 8DO907551C ecus

Just was wondering about the addresses used to connect to the ecu and for communication.
I think the C-box uses 0x11 for connect and communication while other's use 0x10.

I use physical address 0x01 to start KWP1281 and physical address 0x11 to start KWP2000.

il give that a go,cheers

still getting immobiliser not authenticated messages,reading fails through obd too using optican and me7 flasher,any way to disable the immobiliser to gain read access?

Can you install the ECU in the car and pair it with the immobilizer?

i can reinstall and try to read but reading fails with optican at about 17% which is not even beginning to read at this point,with me7 flasher i cannot connect in the car

Tony,

when can I buy a premium version for faster flashing?

Rick

@ quattronutter :

'me7 flasher i cannot connect in the car' =  pull dashfuse, and it should communicate well.

Also disable virusscanner, and close as much as possible, cputime-hungry aps. Also the temp. disabling of the wificard (laptops) can be the solution. I had this situation. After that,
it worked perfectly (Audi S3 - 2003).

Afterwards, shut off ignition, put fuse back, turn ignition on, and with vagcom clear faultcodes, done !

Cheers,

PvL

In the Audi S3 models there are some differences between the year 99's and the 2000 models, the ESP is one of them.

Can the 99 cars be done by OBD ???

i can read 99 s3 via obd,me7 flasher will not read through obd on 8D0905771C ECU even with cluster fuse removed,i can read later me7 no problems

I keep getting distracted fixing bugs that people find. Hopefully in the next few weeks I will be able to add the premium fast flashing support.

What's the average time to flash an ECU when using NefMoto? It took me about 15 min... Will the new update be faster?

Take your time! Get it right :)

Fixing bugs should always take priority, imo

It should take about 4 minutes. Did you have the communication baud rate set to maximum?

Hi !

It's a pity the software requires Windows Vista...
Why cannot it be ran on Windows XP ?
Is there a chance the next version will support XP ?

It uses some Microsoft libraries that were only added in Windows Vista. To support Windows XP I would have to rewrite those modules without the newer Windows libraries.

Windows XP support is on my list, but fixing bugs and getting version 1 of flashing, data logging, etc keeps taking precedence.

Keep the good work up Tony U the Man!

Version 1.7.0.0 is now available:
http://www.nefariousmotorsports.com/forum/index.php?topic=413.0