|
||||||||
| Xoutpost server transfer and maintenance is occurring.... |
| Xoutpost is currently undergoing a planned server migration.... stay tuned for new developments.... sincerely, the management |
|
|
LinkBack | Thread Tools | Display Modes |
|
#1
|
||||
|
||||
|
8/2011 xDrive35d FRM problems
To recap for those of you that have not been following the BMWwhat thread, while I was coding my FRM, the application appeared to lose communication with the vehicle and/or FRM. Since that time, I could not connect with the FRM so I could not revert back to the previous coding.
The following features did not function or were 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 non-functional - Auto-H system malfunction I took the vehicle to the dealer and they provided a report that the FRM had suffered an permanent internal fault and required replacement. All of the other modules could be read and connected to and appeared 'GREEN' but the FRM appeared 'RED'. They tried disconnecting it for a few minutes and then reattempting to connect to it to no avail. They ordered the FRM and I authorized the replacement. Today, they replaced the FRM and were able to update ALL of the modules which took several hours. At this point the FRM appeared 'YELLOW' and according to them, all features functioned normally. They attempted to encode the module. The FRM took the encoding, in that the encoding process completed without interruption but it still appeared 'YELLOW' afterwards. They then disconnected the battery for about at least 30 minutes. After reconnecting the battery everything was functioning as expected except the driver door window switches operate the wrong side windows. The driver side switches operate the passenger side windows and vice versa. The individual door switches on the other doors operate their respective windows normally. They attempted the encoding process again with the same results: FRM appears 'YELLOW' and the window switches are still malfunctioning. Apparently all other features are perfectly functional. They are keeping the X5 overnight and are going to work on it tomorrow. They did put me in a loaner car and the SA says he is going to try and get BMW to help out with the repair since I've already paid for a new module, installation and coding. I'm not counting on much if anything but it's a nice possibility. The SA said I shouldn't be out anything else unless additional parts are required. Oh boy, this could get expensive. Any thoughts from the board? EDIT: The coding was being accomplished with an Android phone using software and Bluetooth adapter purchased directly from iViNi. I'm assuming that the original problem occurred because battery voltage lowered to the point that the programming could not continue. I'm not sure what could be causing the current issue with the driver door switches. Maybe a bad door switch assembly.
__________________
8/2011 X5 xDrive35d Sport, Black Sapphire Metallic, Black Nevada Leather, Fine Burr Walnut Trim 2/2001 M5, Jet Black, Exclusive Complete Black Walk Nappa Point Heritage Leather, Black Cubic Trim Last edited by josiahg52; 01-16-2015 at 12:16 PM. |
| Bookmarks |
|
|
|
|