NefMoto

Everywhere I've looked everyone talks about flashing and tuning, but I haven't seen what tools are used to read. I know nefmoto can read set memory maps, but my ecu has been flashed by apr and I'd like to have a backup before I mess with it.

Thanks

you can do a blind read with bootmode, but there is no guarantee it will work again if you flash it back, depending on what kind of apr chip it is.

if you are really worried about it, i would get a spare ecu...

You need multiple things.

1. A backup of your eeprom. Might as well do this in bootmode as well, with argdubs tool. Read about it in the "Understanding/retrofitting immobilizer" sticky.
2. A bootmode read with galletto. Get the software, and read about how to use it in the "Galletto software edited with proper English" sticky.

Make sure to read, understand, then do these in the order shown above. Please do not post either of these files on the site, and understand that you should not distribute them or otherwise abuse them.

Welcome, and good luck.

#1 is done. Fairly straight forward. Why does arp bother flashing the immo if my car doesn't have it from the factory.

Galletto is a no go for me. My ebay cable is a 232bl with no serial, so I can't program the cable, nor modify galletto to work. I have an official hex-can cable if that opens other options for me.



I'm not worried, but it's always nice to have a backup. I have a spare ecu that I'm playing with. I've already flashed it with the vlmspec mbox file. Surprisingly no cluster error codes. The apr tune I have is weird. It's a K box with an untouched f800BB, but no map switching via cruise control. VCDS shows an egt code, but there's no CEL for it (egt delete?)

If anyone could point me in the right direction for more information about readiness and CEL codes, it would be greatly appreciated. I've already read the S4 tuning wiki.


Once again thanks for the quick replies and awesome community.

Yes, you can hexedit the galletto to use the hex-can cable. The serial # is probably something like RT000001


If that is the case, a bootmode blind read is likely sufficient backup if you have an eeprom backup to go with it.


There are several different threads about this on nef, but I realize the search function can be a bit ... frustrating to use. If you have specific questions, there are a lot of people (ahem, dd) here who are helpful and are likely able to guide you in the right direction.

If you read the final page of the Galletto thread you'll see that the address is included to use it without serial number verification :)

As for the eeprom, it's not for the immobilizer, APR locks their files to the eeprom. If you don't have a backup, you can't restore your APR file. It simply will not run :(

Flashing with nefmoto overwrites parts of the eeprom, so it's important to make a backup before doing anything.

LMK if you need anything else!

LOL. I never got that far.

Do you have a patched version of your corrected English exe we can simply put in the first post?

I just want to make sure I'm understanding this right. The f800 holds all the tables, maps, etc. The eeprom (95040 chip) holds a checkbit, number, something of that nature that the Immo (or in my case APR) verifies before letting the vehicle run. If nefmoto's purpose is to read/write to the F800, why does it write to the eeprom?

In order to write via OBD the tool doing the programming must sign the eeprom in order to complete and close out the flashing process. That tool must leave a 6 digit identifier near the bottom of the page. Your APR eeprom will be signed "NEFMTO", which CAN render it inoperable.

Also, I have updated the Galletto thread accordingly.

:)

I just patched mine and threw out the 4 other copies of the .exe i had.

No more pesky wire to deal with

http://imgur.com/9RGuYMl.jpg


Still having a problem with reading in boot mode.

ebay cable + nefmoto- works
ebay cable + nefmoto + bootmode- crashes(proves that it can connect to boot mode ecu)
ebay cable + galletto(patched, admin, compat mode ) + bootmode - boot mode inactive

Hex-can(smart mode) + nefmoto- can't connect (to be expected)
Hex-can(dumb mode) + nefmoto- works
Hex-can(dumb mode) + nefmoto + bootmode- can't connnect
Hex-can(dumb mode) + galletto(patched, admin, compat mode ) + bootmode - boot mode inactive

I've deleted all drivers and re-installed. Going to have to dust off the old laptop with xp and give it another go. I can understand galletto refusing to work due to win7, drivers, etc. But the hex-can cable not getting a reaction from nefmoto while in boot mode is giving me high doubts about it working in galletto.

I cracked open the cables and there's a ft232bl in the ebay cable and a ft232rq in the hex-can. On FTD's website they have VCP and D2XX drivers on seperate pages, but the downloadable is the same???

"boot mode inactive" is a good sign. It means your cable and galletto are working; you just failed to put the ECU in bootmode :)

I see  in your picture you have resistor or other thing under heat shrink tubing ?

What is the ohms value of that ?

I never use resistor on ME7.x and boot mode great all time.

What year is your ecu? What care are we talking about?

The resistor value is irrelevant. it's just easier to solder to a pin than a wire  ;D


Sadly it's still an issue with galletto. I can consistently enter boot mode, even easier now with the button. Galletto doesn't even try to communicate with the ecu. Here's how I found out.

put ecu in boot mode> connect nefmotor(bootmode) > nefmoto crashes > restart nefmoto > try connecting nefmoto(bootmode) >nefmoto keeps pinging ecu

So I have a theory- you can only connect to the ecu once in bootmode. subsequent tries will be denied.

So I tried it a bit different.

put ecu in boot mode> connect nefmotor(bootmode) > nefmoto crashes > restart nefmoto > try connecting nefmoto(kwp2000) >nefmoto keeps pinging ecu

I did it multiple times to confirm. You can only connect to it once.

put ecu in boot mode> run galletto > get boot mode inactive error > exit galletto > connect nefmoto(bootmode) > nefmoto crashes

I've repeated it multiple times, changed to com#1. Same outcome. I believe it's the win7 environment. WinXp will be tried soon.


I just tried Argdub's 95040 reader. It works with the ebay cable to read the eeprom, but has a "no echo from cable" error when using the hex-can. Yes it's in dumb mode. Confirmed by successfully connecting using nefmoto.


Everything is being done to my spare ecu. F800BB. 4b0 907 551 Q flashed to an M-box.

Your issue may be voltage related.

ebay galletto is very picky with voltage.
Mine wont work over 12.5V at all.
No matter if its with galletto software or me7EEprom tool.
The cable itself just wont work over 12.5V

My MPPS works up around 14.5 V just fine.

Well I tried a virgin w7 pc (no previous usb-serial drivers) and XP(all old drivers deleted) with the same results. Boot mode not active error and immediately afterwards I can read the eeprom. I even tried the new galletto in case I messed up while patching it. What drivers are you guys using? I have 2.08.30 which is the latest from here http://www.ftdichip.com/Drivers/VCP.htm


http://imgur.com/pJhFDYb

My Galletto works fine with ~10V but its still a pain in the ...
mpps is much better, havent used galletto since months.

try it with lower voltage

I have galletto(version in the forum) with blue KKL cable(FT232rl), on XPsp3 , FTDI 2.06x. My voltage are set to 13.5. No problem to go in bootmode. If you use resistor, be sure to put 5K ohms or higher value.