03-23-2025, 11:12 AM
Hello
Im joining the forum because I recently inherited my first BMW.
A 2006 Gen 1 X3 E83 with 114K miles.
It is very well maintained and in excellent condition.
I have performed all critical 100K mile PM replacement components.
I currently have ONE fly in the ointment that I have put dozens of debugging hours on:
A possible "self Induced" problem that caused the DSC lamp to come on after using PASoft 1.40 to reset my transfer case after changing oil and putting in a new plastic gear as a preventative action.
BMW Tools INPA is finding:
DSC (DXC8) module = 5EB3 = Received ID not equal to last calibration
LEW (SAS) module = 0B LWS ID Falsch
LWS EEPROM has CHECKSUM error 2C48
Live Analog DATA status:
Steering angle reads 0 deg with straight ahead alignment, wheel sensors respond normally.
If I clear the two codes and start the car from the ignition on position and drive a few hundred feet the DSC lamp goes off.
I can drive around for hours and the DSC lamp stays out.
Once the ignition is turned off for more and 5-10 seconds the DSC lamp comes on again at next start up.
Im guessing this is a boot up initialization test of DSC system finding what may be "latched soft faults"?
The LEW EEPROM file has the correct last 7 VIN characters in the FGSTNR field and 00 plus last 4 vin numbers in ADFG filed.
Line 0x90 has 2C48 in end column. I can read and write the EEPROM file using PASoft 1.40
I beleive the issue is that the process for calibrating the steering angle involes SAS (LEW) module coding before calibration.
This is why any attempt I make to recalibrate the steering angle with my XTOOL or Foxwell scanner fails "unsuccesful".
This may be some form of software lockout designed to prevent a novice from perfroming "dealer level" maintanence?
I was trying to use Tool32 to recalculate the EEPROM to clear the CHECSUM error but hit anaother dead end.
I cannot find DSC_E83.prg file in my C:\EDIABAS\ECU folder.
Seems that there may be a file support "donut hole" for my car which has a 6/6/06 production date.
I am ready to cry UNCLE on this problem. I can tear down and rebuild any mechanical part of a car.
I own and drive classic cars and trucks that are not idiot proof but can be maintained by an idiot.
Last resort will be to disable DSC and block out the warning lamp with electrical tape.
Any advice from forum mambers would be highly appreciated.
Kind Regards
TVRNUT
Im joining the forum because I recently inherited my first BMW.
A 2006 Gen 1 X3 E83 with 114K miles.
It is very well maintained and in excellent condition.
I have performed all critical 100K mile PM replacement components.
I currently have ONE fly in the ointment that I have put dozens of debugging hours on:
A possible "self Induced" problem that caused the DSC lamp to come on after using PASoft 1.40 to reset my transfer case after changing oil and putting in a new plastic gear as a preventative action.
BMW Tools INPA is finding:
DSC (DXC8) module = 5EB3 = Received ID not equal to last calibration
LEW (SAS) module = 0B LWS ID Falsch
LWS EEPROM has CHECKSUM error 2C48
Live Analog DATA status:
Steering angle reads 0 deg with straight ahead alignment, wheel sensors respond normally.
If I clear the two codes and start the car from the ignition on position and drive a few hundred feet the DSC lamp goes off.
I can drive around for hours and the DSC lamp stays out.
Once the ignition is turned off for more and 5-10 seconds the DSC lamp comes on again at next start up.
Im guessing this is a boot up initialization test of DSC system finding what may be "latched soft faults"?
The LEW EEPROM file has the correct last 7 VIN characters in the FGSTNR field and 00 plus last 4 vin numbers in ADFG filed.
Line 0x90 has 2C48 in end column. I can read and write the EEPROM file using PASoft 1.40
I beleive the issue is that the process for calibrating the steering angle involes SAS (LEW) module coding before calibration.
This is why any attempt I make to recalibrate the steering angle with my XTOOL or Foxwell scanner fails "unsuccesful".
This may be some form of software lockout designed to prevent a novice from perfroming "dealer level" maintanence?
I was trying to use Tool32 to recalculate the EEPROM to clear the CHECSUM error but hit anaother dead end.
I cannot find DSC_E83.prg file in my C:\EDIABAS\ECU folder.
Seems that there may be a file support "donut hole" for my car which has a 6/6/06 production date.
I am ready to cry UNCLE on this problem. I can tear down and rebuild any mechanical part of a car.
I own and drive classic cars and trucks that are not idiot proof but can be maintained by an idiot.
Last resort will be to disable DSC and block out the warning lamp with electrical tape.
Any advice from forum mambers would be highly appreciated.
Kind Regards
TVRNUT
![[-]](https://www.bimmerscene.com/images/collapse.png)
![[Image: image.png]](https://static.wixstatic.com/media/eaba4e_4161f6a5d1eb444c976c438b7565cf87~mv2.png/v1/fill/w_122,h_84,al_c,usm_0.66_1.00_0.01,enc_auto/image.png)
