Pages: [1] 2
Author Topic: 2004 B6 S4 4.2 8E0907560 definition file project  (Read 18048 times)
mister t
Sr. Member
****

Karma: +74/-18
Offline Offline

Posts: 343


« on: September 03, 2015, 01:24:14 AM »

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.
« Last Edit: August 05, 2016, 02:51:34 PM by mister t » Logged
mister t
Sr. Member
****

Karma: +74/-18
Offline Offline

Posts: 343


« Reply #1 on: September 24, 2015, 12:52:27 AM »

Latest version

see above
« Last Edit: November 29, 2015, 02:18:41 AM by mister t » Logged
smelly240
Full Member
***

Karma: +10/-0
Offline Offline

Posts: 102


« Reply #2 on: October 23, 2015, 10:47:13 AM »

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.

Logged
mister t
Sr. Member
****

Karma: +74/-18
Offline Offline

Posts: 343


« Reply #3 on: October 26, 2015, 03:01:49 PM »

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?
Logged
smelly240
Full Member
***

Karma: +10/-0
Offline Offline

Posts: 102


« Reply #4 on: November 18, 2015, 06:38:25 AM »

I can pm it.
Logged
mister t
Sr. Member
****

Karma: +74/-18
Offline Offline

Posts: 343


« Reply #5 on: November 29, 2015, 02:27:05 AM »

comments moved to post #1
« Last Edit: November 29, 2015, 05:43:48 PM by mister t » Logged
mister t
Sr. Member
****

Karma: +74/-18
Offline Offline

Posts: 343


« Reply #6 on: January 20, 2016, 09:34:50 PM »

added a new revision
Logged
vwaudiguy
Hero Member
*****

Karma: +53/-37
Offline Offline

Posts: 2024



« Reply #7 on: January 20, 2016, 09:47:47 PM »

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

"If you have a chinese turbo, that you are worried is going to blow up when you floor it, then LOL."
mister t
Sr. Member
****

Karma: +74/-18
Offline Offline

Posts: 343


« Reply #8 on: January 27, 2016, 04:08:03 PM »

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.
Logged
vwaudiguy
Hero Member
*****

Karma: +53/-37
Offline Offline

Posts: 2024



« Reply #9 on: January 27, 2016, 04:14:02 PM »

The software version is a 560G, tiptronic.

Software version is

1037369591

Thanks for posting the original!
Logged

"If you have a chinese turbo, that you are worried is going to blow up when you floor it, then LOL."
vwaudiguy
Hero Member
*****

Karma: +53/-37
Offline Offline

Posts: 2024



« Reply #10 on: January 27, 2016, 07:34:43 PM »

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

"If you have a chinese turbo, that you are worried is going to blow up when you floor it, then LOL."
mister t
Sr. Member
****

Karma: +74/-18
Offline Offline

Posts: 343


« Reply #11 on: February 01, 2016, 10:11:55 PM »

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?
Logged
vwaudiguy
Hero Member
*****

Karma: +53/-37
Offline Offline

Posts: 2024



« Reply #12 on: February 01, 2016, 11:53:39 PM »

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
Logged

"If you have a chinese turbo, that you are worried is going to blow up when you floor it, then LOL."
mister t
Sr. Member
****

Karma: +74/-18
Offline Offline

Posts: 343


« Reply #13 on: February 24, 2016, 02:21:10 AM »

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
Logged
vwaudiguy
Hero Member
*****

Karma: +53/-37
Offline Offline

Posts: 2024



« Reply #14 on: February 24, 2016, 06:47:48 PM »

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

"If you have a chinese turbo, that you are worried is going to blow up when you floor it, then LOL."
Pages: [1] 2
  Print  
 
Jump to:  

Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Page created in 0.02 seconds with 16 queries. (Pretty URLs adds 0s, 0q)