21 replies to this topic

[siztenboots]

Probably the best and clearest explanation about the motronic and a very good read

 

Taken from the nefmoto forum which is the mecca of motronic enthusiasts

 

https://dl.dropboxus...7.x (Rev 1).pdf

 

 

[slindborg]

Thank you, I shall be hurting the 500 in no time Unless DaveE wants me to have a fiddle first

[Nev]

Wowzers, that IS a good find Steve.

[siztenboots]

Going to use this thread to put up all the basics , rather than repeat them for each new request You should see the TVXR Workshop folder structure in dropbox , once you have your invite. you will want to install TunerPro softwareSetupTunerProRT_v500_8202 latest config file for Z20LET ( I will probably rename this folder structure to reflect all the engine projects going on ) Config filesExperimentalTunerPro-TVXR-Advanced-v1.025 and the ECU maps for z20LET Bin filesZ20LET "ORTH" maps are the original factory ones , so always compare back to them before doing an ecu flash. either use a OBD cable to read your ecu and them adjust it and flash it back (the flash software should recompute checksums), or begin with a good base map from a trusted source.

[Ormes]

The "bin" is a file that contains encoded ecu parameters.  The "xdf" is a file that contains a definition of parameters and the address of their values within the bin.

 

"Scalars" are name/value pairs and "Tables" are just that... a set of 2 dimensional parameters.

 

You will need a galletto or mpps cable to download from the ECU to a bin/upload to the ECU from a bin.  You can get them from ebay for £15+

 

(may as well add to the faq as a learn )

 

 

 

 

 

[siztenboots]

bin file, executable code, ( a boot loader , then the runtime code ) plus the calibration data. In effect its the memory map in ram. This is why I give you definitions of which bits to adjust, and not overwrite assembler opcode. "Scale/r" in the name, are what I use to allow you to adjust the axis values ( columns and rows ) , these are often shared by several map tables. e.g. , load and rpm are the usual ones to extend the high values scale, otherwise the ecu will interpolate

[siztenboots]

Documentation, I normally refer to DocumentationME 7.3.1H Alfa BTS.pdf , and its in english unlike most motronic docs.

[Ormes]

The "bin" is a file that contains encoded ecu parameters.  The "xdf" is a file that contains a definition of parameters and the address of their values within the bin.

 

"Scalars" are name/value pairs and "Tables" are just that... a set of 2 dimensional parameters.

 

You will need a galletto or mpps cable to download from the ECU to a bin/upload to the ECU from a bin.  You can get them from ebay for £15+

 

(may as well add to the faq as a learn )

 

 

 

 

 

 

 

bin file, executable code, ( a boot loader , then the runtime code ) plus the calibration data. In effect its the memory map in ram. This is why I give you definitions of which bits to adjust, and not overwrite assembler opcode. "Scale/r" in the name, are what I use to allow you to adjust the axis values ( columns and rows ) , these are often shared by several map tables. e.g. , load and rpm are the usual ones to extend the high values scale, otherwise the ecu will interpolate

Sorry if I gave bum information due to my interpretation not 100%... I didn't realise the bin also contained the executable.

 

Interesting to see that the stage 4 maps don't seem to change the scalar RPM to allow definition of values at a higher range?

 

Any idea... does our version of the motronic use CDKAT (codeword for cat diagnosis)?

 

Cheers

[siztenboots]

yes, active. I have added CDKAT to XDF 1.025 , so it can be changed ( project control flags category ). Refer to DKAT in the Alfa documentation pdf

[siztenboots]

there are lots of other rpm tables that have other axis scales defined. you can search for word "Scalar" in Title.

[siztenboots]

the important thing is always keep the original file, so you can use the compare tool to verify only the config you expected has changed between edits.

[Ormes]

yes, active. I have added CDKAT to XDF 1.025 , so it can be changed ( project control flags category ). Refer to DKAT in the Alfa documentation pdf

Thanks

[slindborg]

having fun with the ME7.9.1 :s seems tunerpro cant diff the two .ori files I have so I cant see what the chooooner did to a 500 calibration

[siztenboots]

strange its just doing a binary compare, and then matching the address back to a defined map. Make sure the tick box "limit search to defined items only" is unticked , and the end hex address is something sensible , ie.file length

[slindborg]

will check later when I get home.

Need to trawl netmofos for a 7.x.x xdf me thinks

[siztenboots]

Original file from Fiat 500 Abarth with Bosch Me7.9.10 ecu. Bosch number : 0261201756 Fiat number : 51832948 Sw number : 396778 TVXR workshopBin filesFiat 500 ME7.9.10abarth-me7.9.10-51832948-1037396778-0261201756.ori

[siztenboots]

another Original file from Fiat Abarth 500 140hp with Bosch Me7.9.10 ecu. Bosch number : 0261201756 Sw number : 400825 TVXR workshopBin filesFiat 500 ME7.9.10Fiat Abarth 500 0261201756 1037400825 Both 832Kb, but suspect quite different layout

[slindborg]

where do you find these

I saw that you had put two files on a while ago but these look to be better.

[siztenboots]

look very different sofar, assuming that upto 0x10000 is all vector tables and data. Just using plain hex editor HxD to look, not Winols then the from 0x10000 Realtime OS starts ERCOS , ERCSU v1.6.6 iirc, its LoHi 16bit address

[siztenboots]

just stuck the Fiat 500 "400825" through Winols and its found 51 Bosch structure maps

this looks like base ignition? KFZW