NefMoto

hi all, thought id introduce myself, Im Adey. I have tinkered with most of my old cars using diy software to hack the ecus, mainly Nissan's and Honda but now i have got my self an s4 2.7. My search has found me here but Im really struggling with the Audi. All the other software has ended up basically giving me a setup similar to aftermarket ecu's that i found easy to use but the nefmoto stuff i cant even get to talk to the car.

Now my question is, is there a walk through guide? From all the reading iv'e done it seems to be people talking about it but they already know what they are doing. I'm willing to put in the time but just need a little heads up to get me going.

My first port of call i guess would be to pull the original the map off the car? or am i going completely wrong? a user guide for the program would be great if there is one?

Please ask away if there is anything i need to answer to help you guide me. The car is an early euro s4 so im assuming it has the A-box ecu? how can i find out what ecu i have and where do i go from there?

Cheers for the help people

Early euro S4 you won't be able to write with the tools on here.
And some you can not even flash in the car without pulling the ECU out onto the bench or running a separate K-Line.

What year is your car?
You can find your ECU number either on the ECU itself or if you connect diagnostics it will be there as well.
You have likely 551E, 551C or 551D.

ahh, ok then, is there anywhere else i can look? its a 1998/99 pre facelift s4. i have vagcam, can that show me the ecu? where in there can i look? i can pull the cover off the ecu tomorrow morning if i cant find it on vagcom

(http://i58.photobucket.com/albums/g278/adey1984/52ECEC92-9FE3-467F-AA8A-D1774C86BF70-3312-000004082AF38812.jpg)

thats my ecu, doesnt have a letter at the end though??

Yea you won't read this in the car unless you get an extra K-Line wire from the ECU connector to the OBD connector directly.
The problem is on these early pre-facelift S4's the instrument cluster is very badly behaved and just resets the communication all the time if you try to do anything over KWP2000.

So you can start with doing that I guess...

After that you can use MPPS to read and write your ECU and ME7Logger to log.

ok so if i find the correct pin and run it to the obd port i should have some joy? funny you say about the dash, its the only thing i cant adjust using vagcom or vag tacho? can i not swap the ecu for something more adaptable? a later unit?

cheers for all the help guys, keep it up really appreciate it  ;D

There is no point to swap the ECU. The ECU is not the problem here, the dash is.
Your ECU is 512k so you can't use any 1mb images.

You can swap it for a newer 1mb unit if you like, but that is really not needed to tune it and you won't really have any advantages.

ok cheers for that, can i swap the dash out, or pull a fuse for it while trying to connect to the ecu? is there a guide or how to with pin outs for the obd or the ecu itself?

once i get that what xdf do i need? all the ones i find are for ecu's with a suffix

have i been reading that wrong, do you mean a second k line as in to bypass everything else? so i doesnt go through the dash and such? sorry for all the questions

Yeah, exactly, that is what you will have to do.
No other way AFAIK.

time to raise this again, i now have a mapped c box ecu. id like to start tweaking it myself. is the only way without running more wires to bench flash? its not hard to get out so removing it isnt an issue

Try it, depends how well behaved your cars clocks are.
Some will let you log, some won't.

Im having connecting issue's with mine C Box, will it connect if i pull the fuse for the clocks??

No.

right having a little trouble trying to resolve my next issue. poped to the scrappy and got the plugs needed to make a bench harness like the one prj made it works great with vagcom, but nefmoto wont list a lead to work with. ive updated to the latest drivers but it just has an empty box. im still reading while writing this but if someone knows before i can find out please help. im edging closer and closer to getting it all working  ;D

i think i have a cable with the wrong chip in? i run an old 3.11 vagcom and it works great. thought id check with vcds and it wont work. could anyone confirm this?



update, opened it up and it has a ch340 chip in? guess i best get looking for a FT232R chipped one. Was really looking forward to doing my first pull on the ecu

Yeah wrong chip then.

VCDS will never work though, only VCDS Lite.

only loaded vcds to try it, i like my older fully working version. just got on ebay and ordered a cable with the fd232 chip in to get me started. a friend has a cable too so hes checking his so i might get on it sooner, cheers for the help

i have now got the cable that shows up in nefmoto  ;D time to try it all out. for just reading the map off the ecu do i need to go down the route of grounding the earth pin?

this is what im getting so far on my older 551 ecu

Connecting...
Starting slow init connection.
Connecting to address 0x01.
Slow init succeeded.
Switching to KWP1281 session.
KWP1281 connect info: 8D0907551   2,7l V6/5VT         D04

though im stuck on where to go to actually find the map to load into tuner pro.

if i click on read i get

Disabling Windows sleep mode.
Reading all ECU info.
Unable to validate programming session preconditions, attempting to continue.
Negotiating communication timings.
Successfully changed to new communication timings.
Starting diagnostic session.
Successfully started diagnostic session.
Negotiating communication timings.
Reading all ECU info failed.

please be gentle with me im still learning

looks like boot mode wont work with my new cable? wont connect atall if i put the ecu into boot?

Try bootmode with argdubs tool.

FAIL error=0x09 ?

right with a few tweeks i managed to pull a file using argdubs tool. so im getting there slowly, cheers for the info peeps. so is this the same info i would have if i was pulling a file using nefmoto or something slightly different?

No. The file you pulled with me7_95040 is from the eeprom, not the flash chip. It is much smaller @ 512bytes and contains adaptation settings and immobilizer data. The flash chip is much larger @ 1024kb, and contains everything responsible for engine management.

The eeprom also contains the SKC, so now you have that as well, but you'll need to get nefmoto working to do any tuning.

mine has the smaller memory, think thats where i was confused. ok so if i can pull info in boot mode should it work in nefmoto?

this is what im getting from nefmoto boot mode

Connecting...
Starting bootstrap loader upload.
Sent bootstrap init zero byte.
Received device ID response for init zero byte.
Successfully uploaded bootstrap loader.
Received bootstrap loader started status message.
Starting upload of bootmode runtime.
Uploaded bootmode runtime data.
Sent baud rate detection byte.
Bootmode runtime upload failed. Failed to receive baud rate detection response message.
Disconnected
Connecting...
Starting bootstrap loader upload.
Sent bootstrap init zero byte.
Sent bootstrap init zero byte.
Sent bootstrap init zero byte.
Bootstrap loader upload failed. Failed to receive device ID response for init zero byte.
Disconnected

Nefmoto won't read the ecu in bootmode, it'll simply connect allowing you to confirm the ecu is actually in bootmode.

You need the galletto software to read the bin in bootmode. What you DON'T need is the galletto cable, as long as you have an ftdi based cable that contains a serial number (232bm/245bm devices do not, whereas 232r do), you can edit the galletto executable to work with your cable.

http://nefariousmotorsports.com/forum/index.php?topic=639.msg22346#msg22346 (http://nefariousmotorsports.com/forum/index.php?topic=639.msg22346#msg22346)

You can also change the serial number embedded in the cable to match the galletto executable, however this is not a viable option if you have a premium nefmoto license. Neither way is better than the other, both take less than a minute once you know what you're doing.

nice one looking through it now, got the program and it says unable to open com port or something close. just working through checking and changing the serial numbers

Yessir. Until you change the serial Galletto will display an error, something along the lines of "failed to open com port". Once the serials match it should work, if not, use the galletto drivers.

hmmm changed the serial in the .exe using a hex editor to match the one on my cable. galetto just comes up with opening port impossible. any other tips? there doesnt seem to be a setup screen anywhere to select ports or anything in the program

thanks for requoting what you said, just incase i missed it first time. i did go through that and thats why i continued to post. cheers for the help though

Did you uninstall the standard FTDI drivers and install the galletto drivers? (Thus the quote).

indeed i few times over, also tried it in xp mode. will upload it to my desktop and try again on there, cheers for the help though.

Ok after a little reading on the net, it seems that 1260 doesn't work on the bench but 1250 does? Could this be the issue or have I read wrong?

They both work on the bench, however 1260 may also work via OBD (I say may because it has never worked for me).

I can post 1250 if you like, but if 1260 won't work I doubt 1250 will.

I'm using a bench harness I made with a female obd port and ecu plug, worked fine with vagcom up untill I just tried it, I'm now a little worried I've damaged the ecu. Ill find a copy of 1250 and try it. Cheers for all the help and patience

You did ground the correct pin right (to enter bootmode)? I find it helpful to tin the wire I'm using to prevent it from fraying and grounding adjacent pins.

yeah i have probe i use. usully count to 4, is this correct?

Some ecu's are apparently more stubborn than others. Power down the ecu, ground the bootpin, power on the ecu, count to 5(ish), and you should be good to go.

ok i think im doing something really stupid now. went back through and uninstalled everything, re installed the drivers again but the cable doesnt show up as a normal device that i can select its port on. its now shown as a usb controller with FTDI FT8U2XX device, every time i plug it in it comes up so now my old vagcom wont find the cable and i cant locate it on a comport? ive tried running a ftdi comport assignment program but it says there are none there even when i have it on the device manager screen as been there?

any quick tips while im searching the net on this, cheers

fingers crossed with your help i can get over this lol

little update, did everything i needed too, still cant galletto to open any connection. vag com works fine in car, nefmoto will also pull ecu info but not the map (it is a 551c in the car and it has a dash that disconnects alot) but that also works.

my bench/practice ecu nothing works with it anymore. im thinking ive done some damaged or locked it out? i dont want to risk my current ecu in the car so will see if i can get an ecu from the scrap yard and ill check the wiring on the bench harness. seems odd that originally i could pull ecu info from the 551 but now i cant get anything

cheers for all the help youve been giving me with this.

just to add galletto doesnt work in car (551c) either though im using the same cable with the galetto drivers fine with nefmoto and vagcom

ok, right its take a while but after spending alot of time getting cables and software that works i have now been able to pull my tuned 551c file (330bhp 541nm on MRC dyno). have just got hold of a 4B0 907 551F ecu that ive also pulled a bin from. (so say a 290bhp tune uk) so i have just flashed up an m box file too it. let the learning start. big thanks to all those who have hellped me so far i will now be pestering on the actual tuning side of thing  ;D

and it works and starts the car  ;D ;D ;D ;D ;D ;D ;D ;D ;D ;D ;D happy isnt the word

Post the 4b0907551f in original files please.

whats the best site for hosting or easiest way to upload it here?

The original files section works well, or email it to me. I'll make sure it gets where it's needed.

ddillenger84@gmail

.com? sent