DIY: Flash your LCM with Newer Software
301 - 316 of 316 Posts
Joined
·
29 Posts
See the end of Terra's post #1, the buletted list of actions. There are all the actions needed to accomodate the LSZ2 to Your car using the NCS Expert one step after another.
Any LSZ2 has the same firmware for all LSZ2 versions with the same coding index. They differ just by HW components installed and by different coding. This behaviour of freshly flashed LSZ2 can be result of US pre-coded data in flashed firmware (function SL_VO_ANSTEUERUNG is set to nicht_aktiv - not active 5W bulbs as there are no front position bulbs present in US headlights, they use dimmed turn indicators instead). After flashing firmware, You have to code the LSZ2 to work according to the specification (US or ECE versions, halogen or Xenon, etc.). When properly coded for ECE, front position lights start to function again.
---------------------------------------------------------------
The partnumber of LSZ2 is saved inside the EEPROM, at the start of that memory along with the rest of info as coding, diagnostic and bus index, week and year of LSZ2 production and short VIN. This all is changed when s19 file is flashed. If You know Your original CI:35 partnumber, You can use ETK (e.g. online on realoem) to find Your new partnumber (last superseded partnumber of Your original PN) and change it in Your LSZ2 (e.g. using PA soft BMW scanner).
For Your PN 6.936.826 of LSZ2 CI:35 there is the CI:37 equivalent PN 61.31-9.133.021 The PN is stored at bytes 04-07 of the EEPROM and is BCD. To set the LSZ2 PN to proper PN according the superseding chain, change the EEPROM content like this:
BB: old - new data
04: #06 - #09
05: #93 - #13
06: #68 - #30
07: #26 - #21
If You want to change the production date of the LSZ2 to current date (CW 3 of 2023), change two EEPROM bytes at address 10 and 11 dec (0A and 0B hex):
BB: old - new data
0A: #xx - #03 - production calender week 3 in BCD
0B: #yy - #23 - production year 2023 in BCD
After changing of PN or production date, read LSZ2 identification (INPA or PA Soft scanner) and check if You did it right. See here scan results CI:35 before flash, CI:37 after flash and CI:37 after modification of BMW PN and production date. CI:37 was still in virgin status before FA and VIN write and before recoding by FA.
Any LSZ2 has the same firmware for all LSZ2 versions with the same coding index. They differ just by HW components installed and by different coding. This behaviour of freshly flashed LSZ2 can be result of US pre-coded data in flashed firmware (function SL_VO_ANSTEUERUNG is set to nicht_aktiv - not active 5W bulbs as there are no front position bulbs present in US headlights, they use dimmed turn indicators instead). After flashing firmware, You have to code the LSZ2 to work according to the specification (US or ECE versions, halogen or Xenon, etc.). When properly coded for ECE, front position lights start to function again.
---------------------------------------------------------------
The partnumber of LSZ2 is saved inside the EEPROM, at the start of that memory along with the rest of info as coding, diagnostic and bus index, week and year of LSZ2 production and short VIN. This all is changed when s19 file is flashed. If You know Your original CI:35 partnumber, You can use ETK (e.g. online on realoem) to find Your new partnumber (last superseded partnumber of Your original PN) and change it in Your LSZ2 (e.g. using PA soft BMW scanner).
For Your PN 6.936.826 of LSZ2 CI:35 there is the CI:37 equivalent PN 61.31-9.133.021 The PN is stored at bytes 04-07 of the EEPROM and is BCD. To set the LSZ2 PN to proper PN according the superseding chain, change the EEPROM content like this:
BB: old - new data
04: #06 - #09
05: #93 - #13
06: #68 - #30
07: #26 - #21
If You want to change the production date of the LSZ2 to current date (CW 3 of 2023), change two EEPROM bytes at address 10 and 11 dec (0A and 0B hex):
BB: old - new data
0A: #xx - #03 - production calender week 3 in BCD
0B: #yy - #23 - production year 2023 in BCD
After changing of PN or production date, read LSZ2 identification (INPA or PA Soft scanner) and check if You did it right. See here scan results CI:35 before flash, CI:37 after flash and CI:37 after modification of BMW PN and production date. CI:37 was still in virgin status before FA and VIN write and before recoding by FA.
Code:
Data stored in this format by PA Soft BMW Scanner
Original CI:35 data, VIN removed
---------------------------------------------------------------------------------------------------------------------------
Unit BMWTNR HW SW-FSW CI DI BI/VI Date Odometer VIN ADFG Algorithm
---------------------------------------------------------------------------------------------------------------------------
LCM -> 6.936.826 25 36 35 30 14 05/04 148400 km AB12345 3D0000 HC912 - 4 (LSZ2)
Flashed CI:37 (with the older SW 4.5)
---------------------------------------------------------------------------------------------------------------------------
Unit BMWTNR HW SW-FSW CI DI BI/VI Date Odometer VIN ADFG Algorithm
---------------------------------------------------------------------------------------------------------------------------
LCM -> 9.133.027 01 45 37 30 14 18/08 0 km ..00000 000000 HC912 - 13 (LSZ2)
Modified CI:37 PN when I flashed it on Feb 2018
---------------------------------------------------------------------------------------------------------------------------
Unit BMWTNR HW SW-FSW CI DI BI/VI Date Odometer VIN ADFG Algorithm
---------------------------------------------------------------------------------------------------------------------------
LCM -> 9.133.021 01 45 37 30 14 06/18 0 km ..00000 000000 HC912 - 13 (LSZ2)Okay I have courage to have a look.
Can you show which line I have to change?
Can you show which line I have to change?
Attachments
Joined
·
29 Posts
The top line to
0x000 FF 37 30 47 09 13 30 21 01 14 06 23 09 46 56 38
The 09 13 30 27 bytes in first line is the partnumber from the flash file 9.133.027 and You change it to Your proper 9.133.021 according to ETK partnumbers' crossreference. The 18 08 is the week and year of production in flash, so You can change it to week 06 of 2023, as You flashed the LSZ2 on that date to CI:37 or You can revert it back to Your original date (e.g. week 14 to 17 of 2002 according to Your AT31 car production month April of 2002), if You remember it or You have log of Your original LSZ2 before flash or You have an EEPROM backup to search it in there (bytes 10 and 11/ #0A and #0B).
Before any write attempt, save the original LCM_eep.bin and LCM_hw01sw47.epb from the scanner directory (folder) to have a back-up files.
(EDIT: text color change)
0x000 FF 37 30 47 09 13 30 21 01 14 06 23 09 46 56 38
The 09 13 30 27 bytes in first line is the partnumber from the flash file 9.133.027 and You change it to Your proper 9.133.021 according to ETK partnumbers' crossreference. The 18 08 is the week and year of production in flash, so You can change it to week 06 of 2023, as You flashed the LSZ2 on that date to CI:37 or You can revert it back to Your original date (e.g. week 14 to 17 of 2002 according to Your AT31 car production month April of 2002), if You remember it or You have log of Your original LSZ2 before flash or You have an EEPROM backup to search it in there (bytes 10 and 11/ #0A and #0B).
Before any write attempt, save the original LCM_eep.bin and LCM_hw01sw47.epb from the scanner directory (folder) to have a back-up files.
(EDIT: text color change)
Joined
·
29 Posts
Change only the Bold and underlined bytes to those new values. I marked the data with different colors in previous post to better differ between individual data meanings
I do not know.
When I flashed my CI:35 to CI:37 with SW:45, the scanner version 1.4.0.9 automatically detected it as HC912 - 13 (LSZ2). See the code section few post above.
I do not know.
When I flashed my CI:35 to CI:37 with SW:45, the scanner version 1.4.0.9 automatically detected it as HC912 - 13 (LSZ2). See the code section few post above.
Thank so much.
I will try that version.
I will try that version.
No luck when changing bcd and click write eeprom. Pa is saying failed: 3 errors.
Is there any other methode to flash eeprom with changed bcd?
Is there any other methode to flash eeprom with changed bcd?
Can I change the top line of s19 file?
Attachments
Joined
·
29 Posts
Strange. Anyway, this is just a cosmetic mod, so no issue to proper function, when You have the LSZ2 with Your VIN, mileage and properly coded.
But If You want to try that over again I do it this way:
Done. This is how I did it already cca 20 times with CI:37 SW:45 for my friends and it worked always well.
P.S.: note that NCS instructions simplified to major steps only, many individual steps omited
But If You want to try that over again I do it this way:
- IGN ON and full scan of the car with the original LSZ2 CI:35 with NCS expert to save coding TRC and with scanner to read EEPROM and coding data, production date etc.(post #303 CODE part top lines) , IGN OFF, remove LSZ2 from car
- in realoem find CI:37 partnumber for actual CI:35 LSZ2 (e.g. from 6.936.826 to 9.133.021)
- flash LSZ2 to CI:37, it is in virgin state as s19 is prepared like this (=>VIN reads as ..0000 in scanner)
- put LSZ2 back to the car, IGN ON, full scan with scanner,
- then after full scan still in scanner open LSZ, read EEPROM, read coding data (post #303 CODE part middle lines), edit EEPROM to change LSZ2 PN from flashed 9.133.027 to previously found at realoem (e.g. 9.133.021) and production date back to original or to the actual week and year, then write EEPROM, it asks to save LCM_eep.bin or LCM_wr.bin and it writes changes
- exit LSZ window to main scanner page and reenter LSZ, now it should show new PN and production date (post #303 CODE part bottom lines), exit scanner
- start NCS expert with profile that allow MAN coding, select ZCS/FA from ECU, select E46 chassis, read FA from AKMB, and code the LSZ with empty FSW_PSW.MAN, this will save the car's VIN, the default coding and at the end of the coding it will save the FA to LSZ2 as well
- read coded LSZ again to update TRC with default values according to You FA just coded, copy it to FSW_PSW.MAN and compare it with the previously backed up CI:35 TRC, when different/custom coded, modify FSW_PSW.MAN with those original changes from CI:35, add You new wished mods (US DRL, tripleblink, more stages of BFD) and code the LSZ, exit NCS, IGN OFF
- next IGN ON will update the mileage in LSZ as well
Done. This is how I did it already cca 20 times with CI:37 SW:45 for my friends and it worked always well.
P.S.: note that NCS instructions simplified to major steps only, many individual steps omited
Joined
·
29 Posts
Yes, but You should update the checksum of the line then at least.
Hello guys ! Little question about these LCM’s…
I found this one in my area, but im wondering if triple blinkers will work on this unit since it is a HW0.1 ?
SW4.5 …
![Electronic instrument Font Electronic device Laptop accessory Personal computer hardware]()
Thanks in advance !
I found this one in my area, but im wondering if triple blinkers will work on this unit since it is a HW0.1 ?
SW4.5 …
Thanks in advance !
Attachments
Joined
·
29 Posts
Yes, it will when activated (coded) properly. It is LSZ2 produced from 12/2006 and it looks like to be CI:37 according to HW and SW version.
The 61.31 - 9 133 015 partnumber crossreferrence research in realoem shows it is version of LSZ2 for halogen headlights, front and rear fog lights, the lights switch has no automatic position and it is possible to install it in facelifted limousine (sedan) having chips on PCB for extra output pins used for bulbs in tail lights.
The 61.31 - 9 133 015 partnumber crossreferrence research in realoem shows it is version of LSZ2 for halogen headlights, front and rear fog lights, the lights switch has no automatic position and it is possible to install it in facelifted limousine (sedan) having chips on PCB for extra output pins used for bulbs in tail lights.
301 - 316 of 316 Posts
