Fix For Error Code Reading on MSSFlasher CSL Tune

[terra]

The CSL binaries Paffy has on the MSSFlasher website do not have all the changes necessary to play 100% nice with the non-CSL bootloader. It mostly works, but notably the ability to read error codes is broken

Download a corrected program here

Flash only the program - leave your tune as is (the tune built into the file above is just a standard CSL tune).

Read off your tune and change 0xE002 from 00 to 01, then flash that tune back to your car.

That program also has the changes to trigger the alternator light over the CAN-bus. To enable that, you'd set 0x5968 (partial binary) to 01 05 0A and enable "GENERATOR_UEBER_CAN" in your instrument cluster. If you already have the direct wiring done, then you could leave it alone and things will function like they did before.

[nextelbuddy]

i always wondered why when using that version of the CSL software, in INPA trying to read error codes it would just freeze.

definitely saving this one. thanks!

[R3Z3N]

terra May we host your fixed full binay at github here?

[terra]

Yeah that's fine

[Steve]

awesome, thanks for this!

[PITTM3RR]

Awesome - thanks

[Tomba]

Thanks you very much. WIll try this.

[MpowerE36]

The CSL binaries Paffy has on the MSSFlasher website do not have all the changes necessary to play 100% nice with the non-CSL bootloader. It mostly works, but notably the ability to read error codes is broken

Download a corrected program here

Flash only the program - leave your tune as is (the tune built into the file above is just a standard CSL tune).

Read off your tune and change 0xE002 from 00 to 01, then flash that tune back to your car.

That program also has the changes to trigger the alternator light over the CAN-bus. To enable that, you'd set 0x5968 to 01 05 0A and enable "GENERATOR_UEBER_CAN" in your instrument cluster. If you already have the direct wiring done, then you could leave it alone and things will function like they did before.

terra Why do you change 0xE002 from 00 to 01 ?

Maybe I’m wrong but 0xE002-0xE003 is the word K_FR_T_ADAPT.

Original value : 000 150 => 150 word => 1,5sec
Tuned value : 001 150 => 406 word => 4,06sec

Why do you change K_FR_T_ADAPT value from 1,5sec to 4,06sec ?

[R3Z3N]

^With Terra's wording, XX is a BYTE. The xdfs have this as a WORD ie XXXX. Also the 0401 XDF has a conversion...so....reading TERRAS notes, it would be unwise to use the XDF to change this value.

[MpowerE36]

0xE002 must not be seen as a single byte, it is the most significant bits of the word 0xE002-0xE003. As you see below, the program confirms that it uses a word at the 0xE002 address. This word is K_FR_T_ADAPT and I don’t understant why we need to modify it.

[terra]

The modified program loads it as a byte instead of a word. The non-CSL bootsector sees E002 as K_FSP_CONCEPT. CSL bootloader has it at a different address (F002 I think). So to make the bootloader happy you need to change the value to 01. And to not change K_FR_T_ADAPT’s behavior, we load it as a byte and change the address to E003

[MpowerE36]

The modified program loads it as a byte instead of a word. The non-CSL bootsector sees E002 as K_FSP_CONCEPT. CSL bootloader has it at a different address (F002 I think). So to make the bootloader happy you need to change the value to 01. And to no not change K_FR_T_ADAPT’s behavior, we load it as a byte and change the address to E003

Thanks Terra it's clear

[R3Z3N]

terra I know when reading your posts to pay specific attention to your nomenclature ;-)

[sc_tr0jan_m3]

another happy customer of terra's updated file. just flashed it onto my HP DME and can confirm the IAT and MAP sensors are now activated and working and i'm able to pull the codes from the DME via INPA or an OBD2 reader. now time to optimize this tune!

[sc_tr0jan_m3]

looking for some confirmation from others. i just came home from just testing the csl upgrade and overall pretty happy. my only trouble were the AFRs that i saw when going WOT on an on-ramp. i saw them dip into 10.5 and hold steady around there.

i'm running a karbonius intake, stock cams, and the IAT/MAP sensors were installed and confirmed they're reading well, but i'm a bit concerned on those AFRs. i've also been battling a bank 1 too rich code that keeps coming back even after checking the engine mechanically. on the previous tune, it'd dip into the 12.5's and hold there.

any reactions to what i saw from my wideband on this new CSL tune? has anyone else seen the same?