NefMoto

Here is version 1.9.1.2 of the NefMoto software.

New in this version:
-Support for Windows XP SP2 and later
-Nice user interface for error codes and ECU info
-Removed "Validate Memory Layout" because it can cause error codes to be stored on some ECUs. Reading and writing operations already automatically validate the memory layout, so everything is still "safe".

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 intend to extend the existing wiki entry with more software details and release info.... stay tuned.

Hi Tony,
unfortunately this version will not start/run on Win7 x64 :(
Nothing in event log, no errormessage appear, the process just stops immediately.

same here.  doesn't work in Win7 x64 SP1.

cheers,

d

have a brand new XP SP3 (x86) install and NefMoto works fine there...

running as a VM

d

I just posted a new version of the NefMoto software. There was a bug in the last version that only affected Windows 7. This should work for everyone now.

thanks tony.

just set up a win7 32 bit virtual machine and the 1.9.1.0 fixed version works.  could you modify the version string to represent the change?  (e.g. 1.9.1.a or something)

thanks,

D

One more problem, can't import my license file.

18.dets.2011 05:58:40.474: USER: Checking if connected FTDI devices support premium feature licensing:
18.dets.2011 05:58:40.479: USER: Device 0 supports premium feature licensing.
18.dets.2011 05:58:48.100: USER: There are no licenses installed.
18.dets.2011 05:59:09.806: USER: Failed to import license file.
18.dets.2011 05:59:39.327: LOG: Closing NefMoto VW Audi ME7 ECU Flasher BETA 1.9.1.0

Boo-urns... Things never go easily. I didn't think to test the licensing system with this release. I think a benign change to tidy up the code has change the signatures of the licenses. I will try to get this sorted out now.

Ha. I know that feeling.

I posted another release of the NefMoto software. The version number is now 1.9.1.1 and the problem with importing license files should now be fixed. I don't think there can be any problems left... :P

Great Job. Thx :)

Thanks for XP support, Tony !
Is possible to use HW COM port ? FTDI works OK, but I like my COM1 too  ;D 

I just updated the release of the software to version 1.9.1.2. Another bug was found that prevented saving of the FTDI device info to a file. Hopefully that is the last bug in this release... fingers crossed.

Adding support for COM ports intead of FTDI devices is on the long term list, but nothing scheduled currently.

Sorry but why it says "No FTDI USB device detected"? I use a usual eBay cable with included FTDI driver but nothing happens when I run Nefmoto, plug the cable and turn ON the ignition.. Where is my mistake?

The system is WinXP SP2

Did you try pressing the "Refresh" button in the top right?
Is the ebay cable a USB cable?
If you look in the control panel in Windows, and look at the properties for your USB cable, does it say that is an FTDI device?

Yes, but Refresh wasn't making any difference, same effect as if I press if while away from car with a cable disconnected.
The cable is USB, it creates a virtual com port (it set to COM port 6).
I checked then twice, reinstalled drivers - yes, it clearly says that cable is a FTDI device.
I tried different buads, fast\slow but still it's like the program doesn't react on any action  :-[

i tried connecting it to 4B0907551T ECU and no luck cant get it into bootmode

Thanks for the great software!

On my xp home laptop latest version 1.9.1.2 doesnt start at all, laptop is a fairly recent install so works fine. Nothing in the logs either except the 1st start message.

Do you know if you have .NET 3.5 and Windows XP SP2 installed?

Can you post your log file?

You installed the FTDI drivers attached to the first post in this thread?

These two utilities from FTDI should be able to detect the FTDI device if it is installed properly.
http://www.ftdichip.com/Support/Utilities/usbview.zip
http://www.ftdichip.com/Support/Utilities/MProg3.5.zip

I am not sure about .NET decided too reinstall with vista and now my vista disk is stuffed.....

Ditch Vista and go straight to Windows 7 Pro!  You won't regret it!

I would if I could get my MPPPS v5 running under windows 7, thats the battle I am having at the moment MPPS on XP, my vag-com only on 32bit xp, nefmoto (was) not XP

A lot of people including myself run Windows XP in a virtual machine under our main OS.

Hmm, it's crashing hard when I try to connect to ME7.5 in bootmode:

Problem signature:
  Problem Event Name:   CLR20r3
  Problem Signature 01:   ecuflasherhost.exe
  Problem Signature 02:   0.0.0.0
  Problem Signature 03:   4ef2b19d
  Problem Signature 04:   Communication
  Problem Signature 05:   1.9.0.0
  Problem Signature 06:   4ef2b17c
  Problem Signature 07:   165
  Problem Signature 08:   6f
  Problem Signature 09:   System.NullReferenceException
  OS Version:   6.1.7600.2.0.0.256.48
  Locale ID:   1033

Any thoughts?

Thanks for letting me know that happened. I haven't seen that problem before. I will double check the code and see if I can find any place I was lazy. The boot mode code has been tested very little.

This is as far as it gets...

09/Jan/2012 04:19:19.420: USER: Connecting...
09/Jan/2012 04:19:19.443: USER: Starting bootstrap loader upload.
09/Jan/2012 04:19:19.454: USER: Sent bootstrap init zero byte.
09/Jan/2012 04:19:19.455: USER: Received device ID response for init zero byte.
09/Jan/2012 04:19:19.476: USER: Successfully uploaded bootstrap loader.
09/Jan/2012 04:19:19.477: USER: Received bootstrap loader started status message.
09/Jan/2012 04:19:19.478: USER: Starting upload of bootmode runtime.
09/Jan/2012 04:19:19.478: USER: Uploaded bootmode runtime data.
09/Jan/2012 04:19:19.482: USER: Sent baud rate detection byte.

That log helps. I will get this fixed for the next release.

Thanks for the hard work!

No prob. Although I make a huge effort to ignore everyone who sends me messages and emails, so I can focus on coding, it is nice to know people actually like and use the code I release.  ;D

If this tool flashed ME7 Porsche and MED9 I'd pretty much be all set :)

ME7 Porsche probably wouldn't be that hard to support. MED9 would be a bit trickier. Do you have access to an ME7 Porsche for testing?

Yup. And I just need to modify my bench harness here at home and I've got a spare 997 DME that I can use even w/o the car. The security procedure is a bit different for in-car but I'd even be happy to just be able to flash on the bench.

Now I ran successfully the NefMoto flasher on a WinXP machine, everything smooth, no problems encountered.
Tony, thanks a lot for enabling your software also to the poor XP users!

I would have taken care of you poor XP users sooner if I knew there were so many of you. ;D

After setzi tested out the NefMoto software, he suggested a small change I could make in the communication settings. The result, the next release of the NefMoto software will have a 25% increase in speed. This means faster flashing and data logging.

As soon as setzi sends me his FTDI device info, he gets a free premium license.  ;D

Making a bench harness tonight.

(http://media.firstrule.net/u/19/porsche_me72__me78__me78min_162_orig.jpg)

Version 1.9.2.0 of the NefMoto software is now available here: http://nefariousmotorsports.com/forum/index.php?topic=1446.0

Hello!
 To me it is the same!
 NET I have a 4 and installed Win XP SP2
 NET 4 ¿Remove and install the 3.5?

Tnks!!

Can you post your log file? You can find it in the %APPDATA% directory inside Nefarious Motorsports.

Goodnight Tony!
I just installed Win XP, and install the NET 3.5 and now opened!

Thanks for this great work and support!

Hi,

I'm not able to get the software running.

XP sp3 with .net 3.5

klicking the icon but nothing happens...  ???

This software works on my S4 B5 with stock 8d0907551d box.
I was able to connect and read the full flash. I didnt try out more yet.

But i was confused, directly after reading out the flash and disconnecting and shutting down thenefmoto flasher, I tryed to read fault codes etc with vag com, it showed me not the number of my ecu in the first field. It was sth. like "THi-SS I..." or so. Also fault codes have not been supported. Is that normal?
I was afraid that Ive messed up my ecu :D.

After I turned off and on the ignition, everything was fine and as it should be.
Fault codes are shown (If there are) and everything elsa as it has to be. I started the car for a test, and it started as it should.
So everything seems to be fine.

This is what it to be expected. To read/write flash, the ecu is set into programming mode.
This runs the ecu from RAM to allow flash erasing. After read/write flash, the ecu still continues
in the programming mode (ram program) until you cycle the ignition.

Good to know.
So ignition cycle will now always be done first after beeing in programming mode.

I didnt flash anything yet, but maybe the d-box can now be listed up at the nefmoto software under tested vehicles, because i think if reading is possible, flashing should also be, doesnt it?

Hi ,

I get this error pack when trying to read my me7,5 ecu . I have no clue if this ecu is stock or not. The previous owner said that it might have a tune - he was not sure ..

29/May/2012 11:10:55.531: USER: ECU reports programming session preconditions have been met.
29/May/2012 11:10:55.531: USER: Negotiating communication timings.
29/May/2012 11:10:55.531: LOG: Reading current communication timings.
29/May/2012 11:10:55.593: LOG: Sent message with service ID AccessTimingParameters
29/May/2012 11:10:55.640: LOG: Received message with service ID: AccessTimingParametersPositiveResponse
29/May/2012 11:10:55.640: LOG: Set timing parameters to new values.
29/May/2012 11:10:55.640: LOG: Setting communication timing to defaults.
29/May/2012 11:10:55.703: LOG: Sent message with service ID AccessTimingParameters
29/May/2012 11:10:55.750: LOG: Received message with service ID: AccessTimingParametersPositiveResponse
29/May/2012 11:10:55.750: LOG: Reading current communication timings.
29/May/2012 11:10:55.812: LOG: Sent message with service ID AccessTimingParameters
29/May/2012 11:10:55.859: LOG: Received message with service ID: AccessTimingParametersPositiveResponse
29/May/2012 11:10:55.859: USER: Successfully changed to new communication timings.
29/May/2012 11:10:55.859: USER: Requesting security access.
29/May/2012 11:10:55.890: LOG: Sent message with service ID SecurityAccess
29/May/2012 11:10:55.937: LOG: Received message with service ID: NegativeResponse
29/May/2012 11:10:55.937: LOG: Received negative response for service ID: SecurityAccess, with response code: GeneralReject
29/May/2012 11:10:55.937: USER: ECU reports that security access request was rejected.
29/May/2012 11:10:55.937: LOG: Starting ProgrammingSession diagnostic session with 124800 baud rate.
29/May/2012 11:10:55.937: USER: Starting diagnostic session.
29/May/2012 11:10:55.968: LOG: Sent message with service ID StartDiagnosticSession
29/May/2012 11:10:56.031: LOG: Received message with service ID: NegativeResponse
29/May/2012 11:10:56.031: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending
29/May/2012 11:10:56.062: LOG: Received message with service ID: NegativeResponse
29/May/2012 11:10:56.062: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending
29/May/2012 11:10:56.109: LOG: Received message with service ID: NegativeResponse
29/May/2012 11:10:56.109: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending
29/May/2012 11:10:56.140: LOG: Received message with service ID: NegativeResponse
29/May/2012 11:10:56.140: LOG: Received negative response for service ID: StartDiagnosticSession, with response code: RequestCorrectlyReceived_ResponsePending
29/May/2012 11:10:58.218: LOG: Double checking receive buffer for embedded messages before flushing receive buffer due to P1 ECU response inter byte time out.
29/May/2012 11:10:58.218: LOG: Flushing 3 bytes from receive buffer due to P1 ECU response inter byte time out.
29/May/2012 11:11:06.000: LOG: Sent message with service ID TesterPresent
29/May/2012 11:11:06.109: LOG: Message received no replies.
29/May/2012 11:11:06.109: LOG: Resending message. Send attempts: 2
29/May/2012 11:11:06.125: LOG: Sent message with service ID TesterPresent
29/May/2012 11:11:06.234: LOG: Message received no replies.
29/May/2012 11:11:06.234: LOG: Resending message. Send attempts: 3
29/May/2012 11:11:06.250: LOG: Sent message with service ID TesterPresent
29/May/2012 11:11:06.359: LOG: Message received no replies.
29/May/2012 11:11:06.359: LOG: Failed to send message 3 times, message send failed.
29/May/2012 11:11:06.359: USER: Disconnecting because no response was received for the Tester Present message.
29/May/2012 11:11:06.359: USER: Disconnected
29/May/2012 11:11:06.359: USER: Reading ECU flash memory failed.
29/May/2012 11:11:06.875: LOG: Closing FTDI device.
29/May/2012 11:11:06.875: LOG: Send receive thread now terminated.
29/May/2012 11:11:08.906: USER: 100% complete.
29/May/2012 11:11:08.906: USER: Restoring Windows sleep mode.

Version 1.9.3.2 of the software is now available here: http://nefariousmotorsports.com/forum/index.php?topic=2200.0