I have a reader/loader for ME7
I have an editor with checksums

I need to determine what maps are what... if anyone has known maps that they can post up address of or even if you can share Audi/Vw/etc. ME7 maps in picture form that might be enough to determine similar boost, timing, fuel maps for the Volvo models. I can't imagine a timing map from one model to another is so different it couldn't be identified by sight.

I believe I have a few already but I'm not 100% sure. Any help and I'm happy to post up plenty of Volvo Me7 bins if you need them.

Thanks all!

Sorry for my delayed reply, been out of the office this last week. Read the post you linked to from start to finish.
I believe this ME7 bin is closer to VAG but not 100% sure.

Here's my stock file https://rapidshare.com/files/2648065251/99_P80_B5244LT_US_Auto_AWD_LPT_XC.bin
And here's a tuned file that came on the ECU when I bought the car (unknown tune) https://rapidshare.com/files/819870954/99_P80_B5244LT_US_Auto_AWD_LPT_XC_Stage_1.bin

I believe I have identified 6 of the basic maps
KFKHFM Air mass correct at hex CB06
KFMIRL Target boost map at hex 11BCC
LDRXN Max load boost control at hex 18CEA
KFZW primary ignition map at hex C5EF
KFLBTS fuel enrichment map at hex 1CF72
KFPED Throttle map (accelerator pedal) at hex 116B2

Now I'm under the understanding that ME7 is torque limited so even if the boost is raised it won't make any more power if the torque limit is not increased as well. That map might be KFMIOP at hex 119EC
I am thinking this tuned file I've attached does not have torque limit raised in the early gears since it's stock boost until 3rd gear.

Any help would be a God send!
Thanks all

As I'm "out of office" I have no tools available but a HEX-editor, so this might not be 100% accurate (you have to check using WinOLS or equivalent)...

Ok, I would start from the stock file and not bother with the tuned file. There are basically a few maps that need to be modified for your stage 1.
A boost level of about 0.8-0.9 bar is appropriate for this engine.

First of all, adjust the LDRXN to support this level. LDRXN (16 bit) is found at 18EDE (16x1, factored 0,023438) with rpm-axis at 18EBE factored 0.25.
Stock LDRXN is:

110   115   116   114   114   113   113   113   113   113   115   118   120   112   108   106

My suggested LDRXN would be:

110   115   120   128   140   143   145   148   150   150   152   152   152   146   143   141

Next step is to check KFMIRL and how far it handles load. This map (16 bit) is found at 11BCC (12x16, factored 0,023438), rpm-axis at 11B94 factored 0.25, axis at 11BB4 factored 0,001526.
This map has plenty of room for more power, i.e. it needs no change. (This map is in your file extremely high, much higher than any of the LPT-versions I've come across earlier. Perhaps this is a result of a US spec car?)

KFMIOP (16 bit) is located at 119EC, factored 0,001526 and needs to be aligned properly with KFMIRL. (There is a separate thread for this in the forum, get them aligned properly or you will have torque intervention issues).

KFLDHBN (8 bit) is found at 1C11F (8x8). It can be FF'd to disable the function.

I would also ad a bit of fuel for this engine for higher loads/higher engine speeds. KFLBTS is at 1CF72, 8 bit, 16x12, factored 0,007813.

Also, stock ignition (8 bit, C5EF, factor 0.75) is very very safe in this file. If you are experiencing high EGT's, using timing advance rather than enrichment would probably do just fine.

Start off with these map changes and take it from there.


Good luck,

Don't rely on WinOLS being able to find the map properly. The adress I gave you is correct and it is 16x1. I've still got no WinOLS in front of me but from memory.. You can basically start of from the map you have, change the start adress to 18EDE, change Columns x rows to 16 x 1, set the organization to Onedimensional, change the factor from 1 to 0,023438. After that, go to the properties of the X-axis and change the start adress to 18EBE, signature byte 4A38 and factor with 0.25.

Furthermore... KFMIRL and KFMIOP are not aligned as you will change the workarea of KFMIRL. KFMIRL is a general calibration area used by several engine revisions, KFMIOP and LDRXN are specific for this calibration, i.e. changing LDRXN and thereby changing the workarea in KFMIRL, I'd be surprised if KFMIOP will still fit. With no WinOLS in front of me I have a hard time seeing this in just a HEX-editor, but I'm sure someone with WinOLS nearby can suggest a proper KFMIOP for you.

I'm a bit surprised about this. In all LPT cars that I've used this LDRXN curve, I've had slightly more boost than 10 PSI (which corresponds to about 0.7 bars of boost). your wastegate actuator, is it properly set up? Cracking pressure can not really be measured properly running the car without some tweaks to the software so I usually use a hand pump with a pressure gauge (connected to the wastegate actuator) to see when it starts to open while looking at the pressure reading. Anything below 0.25 bars (3.6 PSI) needs to be adjusted upwards as the spring generally degrades with age and mileage.

If you can find no issues with the actuator, increase the LDRXN to about 160 and examine if the boost follows accordingly. If not, your actuator might need replacement. (This can be checked by simply disconnecting the pressure hose to the actuator and then take it for a careful testdrive. Your boost sholud rise rapidly if everything is OK with the actuator. Be careful though and let go of the throttle when the boost starts to increase rapidly...)


Did you FF the entire KFLDHBN?

It is multiplied by ambient pressure prior to being converted to load to account for altitude.

Perfect. That was what I expected.
At this point you can now re-calibrate the function properly for your new boost levels.

From the factory this output (ldrlts_w iirc) will be higher than the other paths of the function at sea level and will not be used in rlmax because it always follows the minimum value. If you raise LDRXN and ldrlts_w becomes the lowest specified load than rlmax_w now will follow KFLDHBN.

FF'ing the table is the easist solution and a good way to identify the source of the issue, but KFLDHBN can be tuned to only intervene when required.