NefMoto

This is release 1.9.0.0 of the NefMoto software. This release includes ME7 ECU KWP2000 flashing, KWP2000 memory address based data logging, and initial support for boot mode.

ECU flashing is the same as in previous versions, just with more bug fixes.

Boot mode only has the initial implementation. You can connect and disconnect, but that is it. Currently you can only use this to verify you can enter boot mode and nothing else.

Memory address based data logging is fully working, but doesn't not have any fancy graphs or gauges. You can load variable definition files in the NefMoto format or in the ME7 Logger format from Setzis program.

More info to come later when I have time to write some real documentation and post pics.

Thank you. For this software, this forum and this community.

x2!

Thank you Tony.
Unfortunately I can't connect when engine is running  :(
The logfile is attached. Setzi's logger does not work either.
What's wrong with my car/ecu?

i love you tony!

Thanks for the new version. ;D
Does it suport xp or not yet? ???

@Tony:

Great work !  Hopefully bootmode will soon also be completely added.

Time to test this version asap on a car. Hopefully you will also sort bench-
flashing soon...  That would be awesome.

Cheers,

PvL

Tony, respect, Your tool is a real state of the art!  :o

Awesome! Thanks Tony.

One request:

Awesome that you added ability to import ME7 logger's ECU definition file, that eliminates the worst set up "cost" I see with the Nefmoto's logger. Would it be possible for you to either supply a sample XML for "Read Variable" section or make your software capable of importing configs from Me7 logger?

You can ignore this request if you plan supplying appropriate files, which I would imagine you do plan for!, in short order.

Thanks!

The other variables are just hidden. You need to drag the window divider to make the window bigger than 0 and you'll see them. :)

Hello to all i saw in this version of the software that there are some "advanced settings" for the communication protocol. Can anyone post the optimal values for these settings? Thank you.

Forget my previous post, I actually really like the logging interface. I just had to pull down the variable information window. This revealed the variable list above it.

Can anyone write a guide for dataloging using the software?

Maybe I'm missing something but after setting up the variables and the data to be read, when I press "Start Reading"

All I get is:

Starting variable reading.
Starting diagnostic session.
Start diagnostic session failed, ECU reports security access is required.

Immo problem mayby?

anyone know why i cant get a few ECU's from a A6/Allroad with Infineon Processors to go into boot mode at all using this and galletto no luck

I posted in the other thread, you are shorting the pins right?

yes shorting pin 24 of the chip.  What else should i try?
Can you link me to the other thread

Is the 800 memory layout intended to be able to read both 800BB and 800BT?  Or is this a third type of layout?

If the answer is yes, then can the 800 be used to flash either of them or does it need to be more specific for flashing?

Thanks ;D

Try connecting with fast init to address 0x01 or 0x11. You can change the connection address on the settings tab.

No XP support in this version. Next version 1.9.1.0 supports XP and will be released sometime between now and a few days.

The 800 layout works with both 800BB and 800BT flash chip types. The 800BB and 800BT versions are included just in case some ECU type gets really picky for some unknown reason.

Version 1.9.1.0 with XP support is now available here: http://nefariousmotorsports.com/forum/index.php/topic,1270.0.html

very cool application thanks a lot
 I have a dumb question. I do have a VAGCOM cable with VCDS 11.11. I did the following set up and it works!

(http://farm8.staticflickr.com/7152/6662434623_ed766e2bf3.jpg) (http://www.flickr.com/photos/8175528@N06/6662434623/)
logger2 (http://www.flickr.com/photos/8175528@N06/6662434623/)

and I got this:
(http://farm8.staticflickr.com/7164/6662434357_af50d5d1bf.jpg) (http://www.flickr.com/photos/8175528@N06/6662434357/)
logger1 (http://www.flickr.com/photos/8175528@N06/6662434357/)

my question is how I can load variables xml? definitions file is OK I can import my ME7 bin file

thanks a lot for your feedback

You can create a variables definitions file for data logging by importing an ECU definition file created by setzi62's ME7Logger application.

Can't connect with fast init too. Log attached.
Anything else I can try?

It looks like your ECU 8D0907551G does not support the KWP2000 protocol. The NefMoto software and Setzis data logger both use the KWP2000 protocol. Your ECU starts the KWP1281 protocol correctly with slow init, but does not respond to a fast init or a double slow init with a KWP2000 protocol.

I would assume you cannot fix this without changing your ECU to a newer version. I don't know if you can flash the newer files to your ECU, because your ECU may be 512k flash size, while the newer ones are 1024k flash size.

551G is 1024k and its probably the latest one used on euro S4.
The car has cruise control fitted by dealer, not from factory. Could it be that they messed up some wires from/to ecu and that's why I can't connect?

The G-Box 0261206776, 1037360855, 0002 image supports KWP2000.
I think I remember that s4rmm already verified it is the instrument cluster problem -
by turning off ignition and then connecting ME7L (while ecu still running for some time).

The ECU does not appear to respond to the double slow init to address 0x01 with a KWP2000 session, and does not respond to a slow init to address 0x11. This is why I assumed that it did not support KWP2000.

It seems strange that the instrument cluster could prevent the fast init from succeeding. Although if the instrument cluster gateway is causing a problem passing the signals from the OBD port to the ECU, then that may be the culprit.

Yes, ME7L "works" when ignition is turned off. I can connect and it writes log-file.
So there's nothing I can do about it?

Then I don't belive the cables have been messed up when installing your cruise controller.
Seems you can communicate fine with your ECU when the instrument cluster is turned off.

The solution I have currently in use is a cable from ECU's K-line to a separate
diagnostics connector plus a switch to separate Ecu from the original K-line bus.
Until someone provides a binary of his instruments cluster flash memory for analysis,
I don't expect a software solution will come up for this problem.

Does anyone have the data logger version for Windows XP? thanks

http://nefariousmotorsports.com/forum/index.php/topic,1270.0.html