NefMoto

So in addition to mapping out my 3.0 V6, I've also been mapping out a 8E0907560 ECU for my 4.2 V8 B6 S4.

Not 100% sure of all the axes, but I've made a pretty good dent in the major maps.

Enjoy

****** current map pack*******
NOTE, FOR THOSE WHO ARE USING ANY PRE FEB 24, 2016 .kp pack, i found out that I was 1 row off on the cam phasing maps. Please update to the latest .kp for the correct and validated (via logging) camp phasing maps.

More of the 1x1 and 1D maps found. FYI, there are duplicate maps if you choose the "hide my folders" option in Winols. However I tend to use the "my maps" section for faster look-up when I'm altering maps. Plus, I translated most of the map names in the "my maps" section, so I'm choosing to leave the duplicates in.

I also included the original binary for the 560G automatic transmission


-I've re-named most of them in English so you can understand what they all mean
-I've tried to leave the German name in the description section
-Some of the 8x8 maps don't have the axes numbered, however the constants are correct. You just need to find the actual address for the axis.
-I ended up tagging a bunch of one dimensional (1 by X) areas that could be an axis. These aren't necessarily maps, but at least you can use the address to check and see of they match up as an axis in one of the maps (way easier than trying to find the address later on).
-one other thing to note is that sometimes the smaller maps for oddball functions may not have the correct addresses for the axes as winOLS will give the option to select a target axis that matches the one from the DAMOS that I was using at the time. Not a huge deal unless you plan on rescaling the axis. However any of the major axes like ignition timing, cam phasing etc... are correct.


EDIT AUGUST 5, 2016: It looks like I got my RPM axes mixed up between the KFZW and ZWOPT maps, the latest map pack has them correctly assigned.

Latest version

see above

Where i found power on these cats is completely in kfnwse


I have pretty complete mappacks if u want any specific stuff.  I can locate it for ya.

totally agree that the cam timing maps make a huge difference.

It made a noticeable difference on my 3.0 V6 when I allowed for more intake advance between 3000-4000 RPM.

Any chance you could send me a copy (even a screen pic would work) of the values that you are using on your tune?

Also, how does the cam timing on these engines work? I know there is only an adjuster on the intake cam. so does that mean that the intake alone adjusts? Or do both the intake and exhaust advance/retard together?

I can pm it.

comments moved to post #1

added a new revision

What software version is this .kp for? Thanks for the update.

The software version is a 560G, tiptronic.

I included the original binary for reference, glad you're getting some use out of it.

Also, I have another update posted Jan 27, 2016.

Software version is

1037369591

Thanks for posting the original!

Importing that file you posted as "original" states it has checksum issues for some reason?

Interesting, what application are you using to determine that?

I thought that may be the case, but I downloaded the .bin that I posted right off the site, used ME7Check and it comes back clean.

I think that ORI came from my stock S4 ECU, but maybe it was another S4 binary that I had floating around and mistook for my original one.

As I said, let me know what application returned the checksum error. Maybe it's something specific to ME7.1.1 that isn't fatal?

Winols

IMPORTANT: I FOUND OUT THAT I WAS OFF BY ONE ROW ON THE CAM PHASING MAPS.

I've posted the corrected and updated .kp above

Hey, Mister. I assume you're using WinOLS as well. Do you get a checksum warning when importing that original?

The file is fine.

It's the OLS checksum version that's the issue.

Update posted

Thanks for the clarification, Daz.

how are you going about writing to this ECU? Is it only able thru boot mode and those Master/Slave tuning boxes?

Nope, I just use the Nefmoto software and an ebay cable. The trick is, that you need to pull the ECU out, read the 95040 coding, disable the immo and then you can flash to your heart's content.

Best bet is to buy a spare ECU, make a bench flasher and do all your flashing that way. At that point, you can always swap between the two and do your file revisions that way.

What I did was bought a plug in voltage adapter that puts out between 13.5-15v, then I plug in a power inverter to my cigarette lighter in my car. From there, I can log on the road, pull over with my laptop, make changes, plug in the voltage source to the inverter and hook up my bench flasher, flash the spare ECU while I'm on the side of the road and swap them out (takes all of 3-4 minutes). I've literally done hundreds of file revisions that way.

First off, Thanks alot for getting back to me! I was worried you were no longer on the forum.

So why do i need to pull the ECU? I can read it just fine. Also i don't see myself doing the whole spare ecu/bench flash bit. I'm just looking for a means to open flash files i receive from my tuner. I dont like having to rely on master/slave boxes.

Hey bud not to derail your thread but have you any thoughts on an issue i'm having seen here:

http://nefariousmotorsports.com/forum/index.php?topic=9438.0title=

Released latest revision

Please note, that it is about 90% complete. While there are some small areas which are not mapped out, any further revisions will be incremental.

I've successfully tuned my 560G based on this DAMOS, so anyone looking to tune an S4 should be well capable of doing so with what I've posted here.

Enjoy and as always, let me know if I need to correct anything or if you want to give me a hand, post up your revisions if you find any new map areas that I missed.

Is finding RAM variables the same tedious process as finding maps? I need to find some functions to log that aren't found by ME7L...