During the coding process, the application completely lost communication with the FRM and the FRM only. Despite disconnecting, clearing the cache, repairing with the adapter, reconnecting and checking for compatible modules, it still appears greyed out and the application cannot communicate with the FRM. Since it cannot connect with the FRM, I cannot revert back to the previous coding.

I just got back from the dealer and the FRM has suffered a permanent internal fault and requires replacement. The diagnostic software could not communicate with the FRM. They tried reconnecting it for a few minutes to no avail. It's going back in Wednesday for repair.

Currently, the following features do not function or are in reduced status:

- turn signals completely non-functional including hazard lights
- front side markers non-functional
- headlights and taillights permanently on (switch does not affect operation)
- Corona lights and DRLs non-functional
- interior instrument, HVAC, gear selector and iDrive knob lights on at full intensity
- overhead console, door switch(es), head light switch, parking brake switch and 'Auto-H' switch, CD/DVD player back lighting non-functional
- ambience lighting non-functional
- high-beam/bi-Xenon lights completely non-functional
- fog lights completely non-functional
- cornering lights non-functional
- dome lights and map lights completely non-functional
- vanity mirror lights non-functional
- Welcome and Follow Me lighting non-functional
- power windows non-functional
- no audible or visual indication of remote door lock/unlocking and/or alarm arming/disarming
- reverse lights may not be functioning (hard to check)
- Auto-H system malfunction

I didn't try them but the power seats/mirrors and/or key/seat/mirror memory might also be affected. **Power seats and memory seem to be functioning.**

I hesitate to blame the application but I have no way of knowing for sure unless someone else reports a similar issue using the same coding options I did. Obviously, it facilitated the current condition but I just don't think it caused it in and of itself. These are the hazards of these types of modifications.

Try to revive is using NCSExpert, see if you can read it and then code it using the profile that does not allow modification.

If that does not work, you may have to flash it with tool32. If you don't know how to do what I suggested, you have a lot of reading to do.

I'm an admitted non-expert on these programs but I know enough to do what I've needed to in the past, mostly on my E39 M5, though. Right now, the X5 is responding like the module doesn't even exist, like it's not connected, not even there. I had a similar fault on my E39 M5 but it was the airbag control module and it happened totally out of the blue while driving one day.

I just tried ordering from the BMWhat doggie and they cancelled my order. Do they not ship internationally?

They have a USA store on Amazon.
Chuck

FRM modules can be tricky sometimes in that they are sensitive, especially FRM3 modules.

Because I do not think that the BMWhat application caused my problem directly, I've moved the discussion of the problem with my FRM to another thread here: http://www.xoutpost.com/bmw-sav-foru...-problems.html

Once I get my X5 fixed I plan to use BMWhat to once again code desired options as I did before but with the engine running from now on. Although I successfully coded modules multiple times with the ignition on and engine off it seems that this last time battery voltage simply dropped below the safe threshold and interrupted the coding process while it was underway,

Just coded the HP/Torque meter on my nav, I used NCS Expert, BMWHat can't do this for now.Attachment 65461


Sent from my iPhone using Tapatalk

What variables need to be changed and what module? Thanks.

CIC. Module
EFF_DYN_SPORT_CID
EFF_DYN_SPORT_UNIT


Sent from my iPhone using Tapatalk