Hello!

I have a Peugeot 406 HDi 90 (the slowest 406 there is), and just to really complicate matters, it has the Siemens ECU.
Stop laughing. ;)

After 7 years of trouble free ownership I've kind of arrived at the conclusion that I want it remapping -- if only to satisfy my curiosity about remapping. I'll be paying through the nose for a company to do an off-the-shelf map because I know nothing. :oops:
Stop laughing. ;)

Which brings me to the reason for joining the forum: to learn about what a 'map' actually is, and maybe even a bit about how to tweak them.
I'm a mathematician :ugeek: and computer programmer (which pays the bills) -- so it can't be that hard ;)
So how do I get started?!
Example map and a 'how to read it' guide?
Any pointers much appreciated.

Richard.

Welcome Richard, we are glad you joined. You have great knowledge that will help you a lot.
Like all other things this goes step by step.

For beginning the best start is to take a picture of your ECU - the cover, and than read it with proper tool and post your original and picture here:
orginal-ecu-files

If you can not take a picture just write down HW and SW number of it.
Take a look some other original files posts for orientation.

For start you will need:
1. Locate your ECU, SW HW number
2. Proper tool to read the bin
3. WinOLS software to locate the graphs inside the bin
4. A lot of help ;)

hope this helps for start

I downloaded a couple of maps off here and opened them in WinOLS, and I see that by spotting increasing sequences of values in the file you can deduce the existence of a map graph.

But how do you determine what the graphs is showing?

What about non-graphical data such as DPF regeneration instructions?

Ta,
Richard.

Knowledge, datalogging and experience.
What axis look like rpm ?
What units is mass airflow measured in, is that unit scaled or offset, what are the realistic values for this airflow at this rpm from the datalogs....

As you can see you need to know hows the engine fuctions and what sensors are used by the ECU for what and when and how.
You need to know what parameters the ECU needs to know and how it interprets them and what it does with them.

Then their is the file structure of the binary itself.
Some ECUs have a ID for an axes by the tables
Some ECUs have the axes right next to the tables concerned.
ie a 16x16 table in EDC16 might be
16 16 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 600 800 1000 1250 1500 1750 2000 2250 2500 2750 3000 3500 4000 4500 4800 5000...
...followed by 256 values of 8192.

..bit more food for you anyway ;)