E46 Fanatics Forum banner
281 - 300 of 316 Posts

· Super Moderator
'03 325iT Mystic Blau
Joined
·
6,882 Posts
You have done:
facelift sedan LCM on a touring. ✅ will work.
touring LCM on a facelift sedan. ❌ will not work

If you done a touring LCM (LL) on a facelift LCM (LH), then please share witch us. I did everything you said, I did everything in NCS...it not works.
I sold my touring LCM to another user who has it functioning in his sedan.
Why would there be a touring-specific LCM when for all intents and purposes they're identical cars?
 

· Registered
Joined
·
5 Posts
I thought it's because of the different (?) pinout because of the inner tailights and then the outer right tailight not working? Or is it solved just by defaulting the configuration of the new LCM to your car by writing the blank .man file?
 

· Registered
BMW 320i
Joined
·
7 Posts
I thought it's because of the different (?) pinout because of the inner tailights and then the outer right tailight not working? Or is it solved just by defaulting the configuration of the new LCM to your car by writing the blank .man file?
No I tried it and it don't work for me.
The right taillight is not working, if they are switched on. If I use the Coming Home feature, they are working.
I flashed a blank .man, but changed nothing.
I changed some setting, like:
PIN37_49_PARKL or PIN29_30_PARK

Original: BMW 6 936 826 (ECE SA dyn LH m FLC)
Flashed: BMW 6 936 825 (ECE SA dyn LL m FLC)
 

· Registered
Joined
·
909 Posts
This is a great tutorial, I was able to find a SW3.6 LCM and flash it and put it into my 2001 M3. I wrote the VIN and mileage with PA Soft since I don't have NCS Expert working. I also used PA Soft to disable bi-xennons.

OEM LED tails work, xenons work and level, no flickering or bulb out warnings.

Are there any issues I can run into since I didn't copy the VO over? My main concern is the PWM value for the LED tails (EF), but I think the donor LCM came from a car that would have had LED tails already.

I also have triple blink, fogs with high beams, and the euro hazard lights (although it's not a double blink, more like one quick blink then two quick blinks). Are these functions enabled because the donor LCM had them or does Terra's flash come with these enabled?
 

· Registered
Joined
·
28 Posts
I don't understand any of what you're saying.
LCMs can be used in any coupe/vert/sedan/touring/compact, it's in how they're coded that determines what pins are lit under what circumstances. IIRC the one that I currently have in my touring had originally been in facelift sedan, but I've had ones out of coupes in it in the past. I've been through a few before finding one with sw version 4.0 and the circuitry to drive the xenon leveling motors.
It is not fully correct. It worked like this with pre facelift LSZ (CI:26-CI:29) that all versions of one coding index had all same hardware and to change from halogen to xenon and vice versa it was OK just to change the front panel and recode the LSZ.
When LSZ2 (LSZ CI:31-CI:37) came after Y2K into production, there started the tendency to cut and save cost anywhere it is possible, so despite all LSZ2 was having the same "universal for all versions" PCB, they differed by the components soldered to the PCB.

The options that was possible to install/not install on the PCB included:
- driver for stepper motors controlling lights vertical aim adjustment
(missing in the AHL Xenon LSZ2 version for 2003/03+ Coupe and probably US LSZ2 versions)
- levelling sensors inputs conditioning parts [LSZ2 description contain "dyn"]
(missing in all but Xenon LSZ2 versions)
- LSZ2 pin 20 and pin 38 driver (the longest 28 pins chip on top of the PCB) [LSZ2 description contain "L" or "LL" when not installed and "H" or "LH" when installed]
(missing in all but Sedan or 2003/03+ Coupe LED rear tailights LSZ2 versions)
- front panel AHL ON indication LED driver
(missing in all but AHL LSZ2 version for 2003/03+ Coupe)

So, any AHL LSZ2 version will never control stepper motors directly in any of non-AHL E46 car despite properly coded, as there is no part to do it. There is AHL module that controls vertical and horizontal lights movement.

Any "LL" LSZ2 version will not control LSZ2 connector pins 20&38 (Sedan outer taillights or Coupe LED BFD lights despite properly coded, as there is no part to do it.

Any halogen or AHL LSZ2 version will not read any axle load levelling sensors despite properly coded, as there is no part to do it.

Any non-AHL LSZ2 version will not illuminate the AHL panel LED, when AHL panel attached to non-AHL LSZ2 version despite properly coded, as there is no part to do it. (I know it, I let desolder CPU pin grounding resistor off my PCB and let the driver, resistor and capacitor solder to PCB to allow it work on my non-AHL LSZ2.

When You are lucky and You find a LSZ2 with the most parts installed (ECE Xenon Sedan or 2003/03 Coupe version), You can use it in any other body version, but e.g. Touring or Compact LSZ2 version could not be used in Sedan properly.

The front panel with Automatic/Non-Automatic switch position can be exchanged with no issue. LSZ2 is ready for any front panel and when Automatic light contron position is chosen, it switches the lights ON when RLS is either missing or when present and it detects any lights ON conditions (dark, tunnel, rain, ...).

Most of this info discussed TerraPhantm here:

LSZ(2) pins to taillights assignement is here:
 

· Registered
Joined
·
28 Posts
LSZ2 CI:35 for Xenon and Sedan with RLS - this is the very right LSZ2 to use.

I guess You did it, but if not, please check all those hints.

  • Check and double check all the software and drivers version You installed. There should be the proper match between the system and the version of the SW (e.g. XP 32 bit version on WinXP 32bit computer).
  • Check and double check the location and proper soldering of the pins on LSZ2 PCB You soldered the wires to, proper wires assignement for flash tool connector, propper connection of the connector to flash tool (not reversed if the connector is DIL flat ribbon and not individual wires)
  • Check and double check jumper settings on the flash tools
  • If it still does not work, try to get/borrow another computer, e.g. with Windows XP and try to install all SW there, when installed, test it again
  • I always read the CPU first to test connection, if read successfuly, I save the result as well

If none of this helps, I do not know what to do next...
 

· Registered
04/2002 325ti
Joined
·
280 Posts
LSZ2 CI:35 for Xenon and Sedan with RLS - this is the very right LSZ2 to use.

I guess You did it, but if not, please check all those hints.

  • Check and double check all the software and drivers version You installed. There should be the proper match between the system and the version of the SW (e.g. XP 32 bit version on WinXP 32bit computer).
  • Check and double check the location and proper soldering of the pins on LSZ2 PCB You soldered the wires to, proper wires assignement for flash tool connector, propper connection of the connector to flash tool (not reversed if the connector is DIL flat ribbon and not individual wires)
  • Check and double check jumper settings on the flash tools
  • If it still does not work, try to get/borrow another computer, e.g. with Windows XP and try to install all SW there, when installed, test it again
  • I always read the CPU first to test connection, if read successfuly, I save the result as well

If none of this helps, I do not know what to do next...
Just curious how do I read cpu, you mean at " interface menu" and choose detect usbdm interface?
 

· Registered
Joined
·
28 Posts
You should do it with different program from the software pack, the USBDM Memory Dump.

Please see the original efc3 post with the USBDM LSZ2 guide at "Interest in updating LCMs to SW 4.0 or 4.5?", see post #51 of the thread.

 

· Registered
Joined
·
28 Posts
See efc3 post #51 for NOTE in step 4 about EEPROM write in the other thread. It was valid for the SW version 4.12 in 2016 when efc3 wrote it, I had downloaded that version back then and I follow the original guide to the letter. The current version of the USBDM software might have definition for MC9S12DJ64 EEPROM programming already included (I did not test it), so You can try it to follow post #1 here and if You still detect CI:35 LSZ2 after flash, it means no EEPROM was programmed and then follow the efc3 write step 4 NOTE to flash EEPROM to LSZ2 CPU as well (EEPROM contains new partnumber and coding index 37 values when read with diagnostic).

How to change the VIN in LSZ2 to Your car's VIN, storing of Your car's proper FA into LSZ2 and coding of the LSZ2 according Your car's proper FA is written here in post #1. Do not forget follow it as well. Then You can customize Your LSZ2 setting as You wish.
 

· Registered
Joined
·
28 Posts
Just to note, as I reffered to software versions (v4.12), it was always the version of the USBDM software version.

Do not mix it with the LSZ2 firmware version. They are those:

  • SW 3.6 for LSZ2 coding index 35 (source LSZ2)
  • SW 4.0 for LSZ2 coding index 36 (older CI, better move to the last one)
  • SW 4.5 for LSZ2 coding index 37 (FW made 2006-10-16, s19 file in original thread post #51 - see my link in post #295 above)
  • SW 4.7 for LSZ2 coding index 37 (FW made 2007-02-07, s19 file in this thread post #1)

Note, the LSZ2 coding index 37 has two version of firmware, v45 and v47. I cannot tell the difference in function (beside the 92 blocks that differ in S19 files), but I would recommend to use the last version v47. Let us assume, that the later version is a bugfix to the first release.
 
281 - 300 of 316 Posts
Top