[Cali_MSport]

Just so this thread isn't here with no solution or outcome, I wanted to let it be known that I did update FRM2 using Winkfp and copied the CAS VO to NFRM using NSC, changed the build date and default coded the NFRM with success. After that I scanned for codes then cleared all codes When I start the car it still has ABS, Brake, the red car on a lift icon, steering wheel angle sensor lights on.

I am a cellphone technician by trade for almost 13 years and by chance or luck or maybe karma because I do a lot of nice things to help people...I got a call a couple weeks ago from a guy who owns an indy shop in my area needing his iPhone X screen fixed. Since than he and I have become friends and helped each other out a few times with different things .He was able to get the dealership in town to reprogram the entire car for $100 and we swapped out the DSC before dropping it off. Thats a sweet deal $100 I think he used to work there and knows all the guys. There's a few recalls that they are handling also while its at the dealer. I will post results soon as i get it back.

Meanwhile I found a 2008 for free wrecked in front but with good motor and tranny clean interior decent wheels and working modules and a bunch of good parts.. I need random shit for mine like door handles and some interior stuff. I will be picking it up in the morning.

Thank you to everyone whose offered advice to my newbie ass. I know how it is to say the same stuff over and over again to different people most of who never appreciate your time or bother to say thanks. Well I wasn't raised that way. I do appreciate it very much. THANK YOU! I do the same thing you guys do here on the cellphone forums. I have much respect for educated people and just those with knowledge in general.

[Cali_MSport]

So car was at the dealership and they said it won't program because it needs a new computer because it was programmed with data from a different model and it cannot be reversed. Is this true or ? Can this be the case ? I honestly do not believe this ? Couldn't the computer be refurbished at the very least ?

[sdbmwcoding]

Originally Posted by cali3series

So car was at the dealership and they said it won't program because it needs a new computer because it was programmed with data from a different model and it cannot be reversed. Is this true or ? Can this be the case ? I honestly do not believe this ? Couldn't the computer be refurbished at the very least ?

What "computer"? I thought you said you're sourced a used DSC and got it programmed? They said they can't code the used DSC?

[ctuna]

These guys aren't coders if they can't get it to run through a one
pass step try of ista p or the equivalent of what they have now they give up .
I would try Winkfp one module at a time as a next step.
Also which computer because essentialy all the modules are computers
to a certain extent.

I haven't played with winkfp but I believe it reads the hardware number
then make's suggestions with list of the appropriate files that go in that
particular module.

There is also an app in the bimmergeeks download called DrGini ( I think)
that does the same thing.)

[Cali_MSport]

Originally Posted by sd*********

What "computer"? I thought you said you're sourced a used DSC and got it programmed? They said they can't code the used DSC?

We replaced the DSC but did not do any programming to it only replaced it and dropped off the car. They said the dme is the problem that it was coded to another model of car and can't be undone.

[sdbmwcoding]

Originally Posted by cali3series

We replaced the DSC but did not do any programming to it only replaced it and dropped off the car. They said the dme is the problem that it was coded to another model of car and can't be undone.

That doesn't make sense, was the car functioning fine prior to the frm and dsc module failing? This is a easy job for any coder, I assume the dealer doesn't know what to do or how to program it via ISTA

If they can't communicate with any modules it could be JBE issue as well. Just saw one recently, client thought it was dme but turned out to be JBE. Flashed JBE via winkfp and I was able to communicate with the entire car again.

[Cali_MSport]

Car was communicating with all modules except the dsc last time I checked with ista and inpa
The DSC was red in the tree before this the footwell module gone out both were replaced car sentnto dealer and only because my friend who owns an Indy shop gets cars programmed for $100 there cuz he's got a connection there they. He's telling me car won't program needs a new computer because it was programmed to the wrong model and can not be undone. I'm trying to get more specifics

[sdbmwcoding]

Originally Posted by cali3series

Car was communicating with all modules except the dsc last time I checked with ista and inpa
The DSC was red in the tree before this the footwell module gone out both were replaced car sentnto dealer and only because my friend who owns an Indy shop gets cars programmed for $100 there cuz he's got a connection there they. He's telling me car won't program needs a new computer because it was programmed to the wrong model and can not be undone. I'm trying to get more specifics

Pull it out, it's clear they don't know what they're talking about lol. Contract a coder to code the dsc unit to the car and perform dsc calibration via ista. It's a fairly simple process

[Cali_MSport]

The owner of the Indy shop who towed my car to the dealer told me today that all of the modules communicate but the dme is keeping the car from being able to program because the prior program was for a different model that's the final word I received today. He said the programming cannot be undone we need to replace the. Dme in order to proceed. Anyone ???

[sdbmwcoding]

Originally Posted by cali3series

The owner of the Indy shop who towed my car to the dealer told me today that all of the modules communicate but the dme is keeping the car from being able to program because the prior program was for a different model that's the final word I received today. He said the programming cannot be undone we need to replace the. Dme in order to proceed. Anyone ???

As I said, pull the car out. That makes 0 sense to be honest. Contract a coder here on the forums or the hundred in the United States to remotely code the dsc unit, it's a super simple job. If you were able to code the frm unit on the car then nothing is stopping anyone from coding the dsc unit. I assume the Indy has 0 idea what they're talking about and not able to relay dealer information back correctly.

I also referenced back to your inpa UIF screen, the dme ZB number matches an n52 ZB number. When I decode your vin it says you have an n52. I believe the INDY isn't relaying the information back to you correctly. There's no dme problems from what I see. All that's needed is programming the new dsc unit into the car

[ctuna]

There are DME specialists that DME can be sent to .Recovery
process is sometimes similar to Frm revival where the eeproms
are replaced or reprogammed on the board I believe.

You can google for this stuff or

Contact: +1.985.492.0666 call/text or email GcodingBMW AT Gmail.COM
Facebook: www.facebook.com/GcodingBMW

I thought this guy was good with DME Cas modules.

Also what sdbmcoding makes more sense.
But in order to code the new DSC you need to be able to talk to it.

Dealers are not coders or software guys at all this comes up a lot.
It either go or no go on there setups.

[Cali_MSport]

@sd********* is there any possibility that you would be willing to help me out with this car ? It has been months already since I've been able to drive it. I will be happy to compensate you for you time. I'm not rich by any means but I can afford to pay you for your assistance and would greatly appreciate having someone with your coding ability / skill / knowledge helping with this situation. If not I do understand , and thank you regardless for your contribution thus far.

[Cali_MSport]

Also we replaced the DSC with one from another e90 it is possible that this module differs in some way that would cause the DME car in general to not be programmable. I read somewhere that were several variations of DSC Module for the e90. I haven't checked since the DSC was replaced but supposedly all modules do communicate now.

[icon2015]

I don't know if you got this sorted out already, but the bmw workshop can't program your dsc, as they use ISTA+ or ISTA/P to make the programming, and to do this with this software you have to program multiple ecus at the same time, and all the ecus have to be the same I-Step. Probably your DME is a different I-Step and hence their issue.

BUT, this is not the only way to program your replacement DSC, you can do this with WINKFP. From my experience this is not necessary. You can code it with NCS Expert and it will suffice. After the coding is done, you have to initialize both your DSC sensor and steering wheel sensor, this is done easy with ISTA.

There are a few variants of DSC indeed, but from my experience, for BMW E89, as long they are physically identical they are also bilaterally exchangeable.

Good Luck!

[Dfbpurcell]

Did you ever get this resolved? I have a ton of DSC codes, brake light, wipers always on and driver mirror/window not working as well as DSC being red just like you after an active steering rack swap. Have been going through the forums for weeks trying to find a resolution and this is the only thread that has the same symptoms.

[Tambohamilton]

Originally Posted by Dfbpurcell

Did you ever get this resolved? I have a ton of DSC codes, brake light, wipers always on and driver mirror/window not working as well as DSC being red just like you after an active steering rack swap. Have been going through the forums for weeks trying to find a resolution and this is the only thread that has the same symptoms.

Have you checked battery voltage?

[Dfbpurcell]

Originally Posted by Tambohamilton

Have you checked battery voltage?

yes, somebody told me to replace the battery so I did that and coded it. No change. Bought a multimeter and both batteries were fine. Tested everything coming out of the distribution box in the rear and it was all over 12.5v, so now I am looking at the FRM because it seems that the modules connected to it can't communicate with it

[sdbmwcoding]

Originally Posted by Dfbpurcell

Did you ever get this resolved? I have a ton of DSC codes, brake light, wipers always on and driver mirror/window not working as well as DSC being red just like you after an active steering rack swap. Have been going through the forums for weeks trying to find a resolution and this is the only thread that has the same symptoms.

Have you run a fault scan on the car?

[Dfbpurcell]

Originally Posted by sd*********

Have you run a fault scan on the car?

If you mean pulling the codes, yes - that's how I know I have a ton of DSC codes

[sdbmwcoding]

Originally Posted by Dfbpurcell

If you mean pulling the codes, yes - that's how I know I have a ton of DSC codes

Post a screenshot of all the codes

[Dfbpurcell]

Originally Posted by sd*********

Post a screenshot of all the codes

I believe the majority are caused by the FRM as it seems to be the gateway for connected modules.

KLIMA [IHKA87] | E71C: Message (speed, 0x1A0) faulty, receiver IHKA, transmitter DSC
KOMBI [KOMB87] | A3AC: Message (distance travelled, 0x1A6) faulty, receiver KOMBI, transmitter DSC
KOMBI [KOMB87] | A3B9: Sporadic fault (failure, DSC message, 0x19E) No repair measures available, receiver KOMBI, transmitter DSC
KOMBI [KOMB87] | A550: Message (speed, 0x1A0) faulty, receiver KOMBI, transmitter DSC
CAS [CAS] | A0B5: Fault, road speed signal
CAS [CAS] | A0B0: Input, brake lights, implausible
DME/DDE [MSD80] | CDAD: Message error (request, wheel torque, drivetrain, 0xBF), DME receiver, DSC / LDM transmitter
DME/DDE [MSD80] | CDA1: Message (steering wheel angle, 0xC4) incorrect, receiver DME, transmitter DSC
DME/DDE [MSD80] | CD98: Message error (DSC torque request, 0xB6), DME receiver, AHM / DSC transmitter
DME/DDE [MSD80] | CD9C: Message (speed, 0x1A0) incorrect, receiver DME, transmitter DSC
DME/DDE [MSD80] | CDA5: Message (status, DSC, 0x19E) incorrect, receiver DME, transmitter DSC
DME/DDE [MSD80] | CD95: Message (operation, cruise control/ACC, 0x194) incorrect, receiver DME, transmitter DSC / SZL / LWS / ACC
MOSTGW [CCCG60] | E18F: No description found
MOSTGW [CCCG60] | E18D: No description found
FRM [FRM_87] | 9CAC: Brake-light switch faulty
FRM [FRM_87] | 9CC1: Communication with mirror, driver's side, disturbed
FRM [FRM_87] | 9CCF: Communication with LIN operator unit disturbed
CID [CID_90] | A468: External open circuit (LVDS data line)
EGS [GS19D] | CF2B: No message from longitudinal dynamics management, receiver EGS, transmitter GWS/LDM
EGS [GS19D] | CF32: No description found
EGS [GS19D] | CF34: Message from the DSC, receiver EGS, transmitter DSC
MRS [MRS5] | 93FB: No message (vehicle speed) from DSC, ACSM receiver/MRS5, DSC transmitter
AFS [AFS_90] | 6142: ECO valve: fault
AFS [AFS_90] | CE96: Message (wheel circumferential velocity, 0x0CE) faulty, receiver active steering, transmitter DSC
AFS [AFS_90] | CE98: Message (intervention DSC, 0x11E) faulty, receiver active steering, transmitter DSC
AFS [AFS_90] | CE9C: Message (status, DSC, 0x19E) faulty, receiver active steering, transmitter DSC

[sdbmwcoding]

Originally Posted by Dfbpurcell

I believe the majority are caused by the FRM as it seems to be the gateway for connected modules.

KLIMA [IHKA87] | E71C: Message (speed, 0x1A0) faulty, receiver IHKA, transmitter DSC
KOMBI [KOMB87] | A3AC: Message (distance travelled, 0x1A6) faulty, receiver KOMBI, transmitter DSC
KOMBI [KOMB87] | A3B9: Sporadic fault (failure, DSC message, 0x19E) No repair measures available, receiver KOMBI, transmitter DSC
KOMBI [KOMB87] | A550: Message (speed, 0x1A0) faulty, receiver KOMBI, transmitter DSC
CAS [CAS] | A0B5: Fault, road speed signal
CAS [CAS] | A0B0: Input, brake lights, implausible
DME/DDE [MSD80] | CDAD: Message error (request, wheel torque, drivetrain, 0xBF), DME receiver, DSC / LDM transmitter
DME/DDE [MSD80] | CDA1: Message (steering wheel angle, 0xC4) incorrect, receiver DME, transmitter DSC
DME/DDE [MSD80] | CD98: Message error (DSC torque request, 0xB6), DME receiver, AHM / DSC transmitter
DME/DDE [MSD80] | CD9C: Message (speed, 0x1A0) incorrect, receiver DME, transmitter DSC
DME/DDE [MSD80] | CDA5: Message (status, DSC, 0x19E) incorrect, receiver DME, transmitter DSC
DME/DDE [MSD80] | CD95: Message (operation, cruise control/ACC, 0x194) incorrect, receiver DME, transmitter DSC / SZL / LWS / ACC
MOSTGW [CCCG60] | E18F: No description found
MOSTGW [CCCG60] | E18D: No description found
FRM [FRM_87] | 9CAC: Brake-light switch faulty
FRM [FRM_87] | 9CC1: Communication with mirror, driver's side, disturbed
FRM [FRM_87] | 9CCF: Communication with LIN operator unit disturbed
CID [CID_90] | A468: External open circuit (LVDS data line)
EGS [GS19D] | CF2B: No message from longitudinal dynamics management, receiver EGS, transmitter GWS/LDM
EGS [GS19D] | CF32: No description found
EGS [GS19D] | CF34: Message from the DSC, receiver EGS, transmitter DSC
MRS [MRS5] | 93FB: No message (vehicle speed) from DSC, ACSM receiver/MRS5, DSC transmitter
AFS [AFS_90] | 6142: ECO valve: fault
AFS [AFS_90] | CE96: Message (wheel circumferential velocity, 0x0CE) faulty, receiver active steering, transmitter DSC
AFS [AFS_90] | CE98: Message (intervention DSC, 0x11E) faulty, receiver active steering, transmitter DSC
AFS [AFS_90] | CE9C: Message (status, DSC, 0x19E) faulty, receiver active steering, transmitter DSC

It'd be best to run a test plan with ista and go through some of them but based off of what I see, your dsc module is offline/dead which is causing most of these errors. Frm ones look unrelated though for the window and mirror issue. Your frm is fine though, it's still communicating. If it were bad you wouldn't be able to see any frm module codes.

Did all these issues happen at one time randomly?