Here we go then.......
http://www.filedropper.com/413and506map ... s-17-11-02
Tons of little additions done to the sheet, I have put most of the things in the change log.
The Alpina BIN reveals a lot of interesting info. Key points:
- The code section is the same as the 413 silver label
- The table of tables is at the start of the maps not at the end
- The Maps are in the same order as the 506 and 413 silver label
- Only a few things are in the same location across all of the BINs.
This gives a few clues:
- Maps and the table of tables cannot be directly referenced as they were moved with no code changes.
- The Map section truly starts with the first map in the lookup table, by moving the table of tables they highlighted where they felt the start of the "maps section" was.
- Map order is important or they would have moved them around
- A lot more tables have been tuned than we currently have ID for, we need to look into those maps
- The EWS specific data stands out a bit now as we have EWS and non-EWS data that matches for all structures that are not related to the EWS.
- The data area is clearly broken into ~ 5 sections, We seem to have a Constants section, a DTC section, a transfer functions section, A maps section and a references section after the end of the check sum.
- The references section may be more important than it looks as it is always in exactly the same location across all the various BINs.
- Injector constant is not an injector constant at all. I does scale the injector pulses but not for the reasons we think, the 413, 506 and alpina all use the same constant with different injectors. (they do have identical MAF sensors though, is this figure actually a MAF constant?)
- The Alpina seems to turn on or off a host of trouble codes in the DTC section, maybe this will help puzzle out some more of those?
Mykk - While you may not be able to find things like we can it would be a huge help simply for someone to test things on a car and report back, even checking for errors, spelling mistakes and updates in the excel sheet would be awesome.
Some things are going to be hard for us to check and my M3.3.1 ECU is wired up onto an E30 M20 engine and I am not sure Olafu has a running car to test with at the moment?
We might see different behaviour than a running car sees.
Olafu - Would love a proper programmable signal generator, bit out of the budget at the moment though but I am tempted to see what I can get my hands on now I work in a Uni.
The trouble codes do have a frequency of occurrence associated with them, INPA reports the frequency when you scan the car.
I expect the DTC codes are going to have a format like the maps do, Something like 3 bytes giving the max trigger point, min trigger point, frequency.
For the 02 sensor - I have one fitted but just tied up to the side of the engine never to be used, if I get some time I will do horrible things to it and let you know how the codes trigger.
DTC 15 - You have this as "(ignition "spark" current signal?)" is this the one often reported as a knock sensor issue?
If so it is actually a secondary ignition circuit monitoring code.
The ECU has the secondary ignition coils wired back to one of the ECU earths via a big shunt resistor (240ohm) the ECU is looking for a 5v pulse on that earth for each coil firing. If it does not get the pulse then it thinks the coil has not fired or misfired and logs it. It is accurate and fast enough that the ECU uses it to find individual cylinder misfires.
It's always misreported as the info on the system is very poor on the net, I know because I had to do masses of digging to find the real issue. My E30 swap does it and I cannot get the voltage above 4.7 volts despite lots of work. I think it is due to the lower compression of the E30 no building up as large a resistance to the spark and thus less going back down the shunt.
If that is the trigger to turn that DTC code off then I will have to send you some local Cider!
![Cool 8)](./images/smilies/icon_cool.gif)