M5POST
BMW Garage BMW Meets Register Search Today's Posts Mark Forums Read

Go Back   M5POST - BMW M5 Forum > F10 M5 Forum > Navigation, iDrive, Audio, Video, Bluetooth, Phone, Coding

Post Reply
 
Thread Tools Search this Thread
      02-23-2014, 09:16 PM   #1
v3n0m
Lieutenant
57
Rep
451
Posts

Drives: 2013 MCB M5
Join Date: Apr 2013
Location: Vancouver, BC

iTrader: (0)

Errors in iDrive after Coding

Hey all. I just finished my coding session, and after coding some modules, the following errors popped up on idrive:
Chassis stabilization malfunction!
Start-off assistance inactive!
SOS call system malfunction!
Collision Detection Malfunction
Camera Malfunction
Lane Departure Malfunction
Active Blind Spot Malfunction
Speedometer Malfunction

There may have been more, but they've all gone away. Everything seems to be fine though. Does anyone know if this is normal? Is it just something that happens while those modules are coded and the system resets itself?

The engine was on while coding.
Appreciate 0
      02-23-2014, 10:28 PM   #2
Spinny02
Lieutenant Colonel
Spinny02's Avatar
United_States
124
Rep
1,840
Posts

Drives: '14 M5 CP Dinan Stage 2
Join Date: Jun 2013
Location: Houston, Tx

iTrader: (2)

Garage List
I did not get those. I did get an error when we changed the time/date functions and i just had to update time and date and it went away.

Who did you coding? If you need someone to take a look at it V12 does a great job.
Appreciate 0
      02-23-2014, 11:29 PM   #3
v3n0m
Lieutenant
57
Rep
451
Posts

Drives: 2013 MCB M5
Join Date: Apr 2013
Location: Vancouver, BC

iTrader: (0)

According to shawnsheridan, it's common to get these errors when coding KOMBI, HU or FRM (which were all modules I touched). Apparently they're nothing to be concerned about if they go away afterwards (which they did).

I was coding this myself. It was pretty straight forward.

Hope whomever stumbles upon this thread finds this info useful.
Appreciate 0
      02-23-2014, 11:31 PM   #4
v3n0m
Lieutenant
57
Rep
451
Posts

Drives: 2013 MCB M5
Join Date: Apr 2013
Location: Vancouver, BC

iTrader: (0)

I think the errors occurred because the modules reset themselves or were unavailable during the coding process, which made the system throw up malfunctions for the related functions.
Appreciate 0
      02-24-2014, 11:06 AM   #5
avlnch
Lieutenant Colonel
127
Rep
1,622
Posts

Drives: 2013 Individual M5
Join Date: Jul 2007
Location: South FL

iTrader: (0)

Normal for coding certain modules. Those errors go away quickly.
__________________
2013 BMW INDIVIDUAL ///M5 {Frozen Black/Amaro Brown/Amaro Brown Alcantara/White Contrast Stitching/Piano Black Trim}
Appreciate 0
Post Reply

Bookmarks

Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off



All times are GMT -5. The time now is 08:05 PM.




m5post
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2024, vBulletin Solutions Inc.
1Addicts.com, BIMMERPOST.com, E90Post.com, F30Post.com, M3Post.com, ZPost.com, 5Post.com, 6Post.com, 7Post.com, XBimmers.com logo and trademark are properties of BIMMERPOST