BMW M5 Forum and M6 Forums banner

SOS Call System Failure!

1 reading
89K views 12 replies 10 participants last post by  Zipnguyen  
#1 ·
Hi, this is so exciting, my first problem with a car.

I was immediately presented with a yellow telephone icon with a stripe through it with the following text, 'SOS Call System Failure!'.

The car seems to drive as normal, I-Drive reset to default and was extremely sluggish, plus the CD system wasn't playing game.

So I search the forum and did the reset thing (pressed the DVD, CD and volume button together), I get the same SOS message but I-Drive is back to normal response levels. The message is not in the user manual and the BMW contact has no idea what it means!?!

So maybe my M6board buddies can shed some light?

SupraTT
 
#2 ·
Hi, this is so exciting, my first problem with a car.

I was immediately presented with a yellow telephone icon with a stripe through it with the following text, 'SOS Call System Failure!'.

The car seems to drive as normal, I-Drive reset to default and was extremely sluggish, plus the CD system wasn't playing game.

So I search the forum and did the reset thing (pressed the DVD, CD and volume button together), I get the same SOS message but I-Drive is back to normal response levels. The message is not in the user manual and the BMW contact has no idea what it means!?!

So maybe my M6board buddies can shed some light?

SupraTT
I had a similar message at the start of my CCC failure.

http://www.m5board.com/vbulletin/showpost.php?p=1049463&postcount=1

Good luck.
 
#3 ·
Hi,

I spoke with a large BMW garage in Germany and they were extremely helpful. They said the message most likely relates to an issue with the bluetooth connectivity and that I needed to remove my mobile from the iDrive and re-connect and phew, it was indeed the issue.

So, for the record, if you get such a message (SOS Call System Failure!) and it additionally messes up your iDrive, action the following steps:

1. Depress the CD eject, DVD eject and CD volume knob simultaneously until the iDrive screen blanks out.
2. After iDrive reinitialisation, remove your bluetooth mobile from the iDrive menu
3. Switch off, not sure it's necessary but that's what I did.
3. Switch back on and re-config your mobile back into the iDrive.

My journey back home tonight will consist of turning up the CD volume and listening to 'ATB - These Days' in repeat! That song was made for the M6!

Thanks for your response Paul.

Ian
 
#4 ·
Hi,

Currently I have the same problem. After turning on the car iDrive says "SOS call system failure". And after the error goes away when I'm trying to access the telephone in Communication, the system says that "Mobile phone not installed", however it's possible to call from the phone tube. This appeared after my car was for service in dealer... there was no problems before. They don't want to accept their fault. Now trying to get proof for this to get back all stuff working.

Best wishes,

Karl
 
#5 ·
Sorry, but I went one better.
After driving the little one back from school the idrive went completely blank, and no recovery what so ever.
No radio, cd, nav, etc.
Tried rebooting and nothing happens.
Booked the car in for tomorrow morning, and at the same time I will get the oil and filter changed and also fit an ipod connection too. I will drop in a line once I get the car back to let you know what was wrong, but as suspected it is the ccc.
 
#6 · (Edited)
i'm having the same issue, car has been back to service 3 times to fix this. I have not tried the fix that is listed in this thread so i'm hopeing that works.

Just a note: mine locks up for about 15 min then it resets on its own. Also i didnt have this problem till i upgraded to version 27 software.

just checked and i dont even have bluetooth on and still having the same exact problem.
 
#7 ·
I don't think that is relevant RedM6, it is it's time to go, and it just started happening now.
Mine was upgraded to V27 last March, with no problems at all until now, and then all of a sudden ...darkness!
When you go in the BMW garage tell them that it also happend to a friend and it was the ccc unit that had to be changed.
They will change it under warantee, I hope, I will find out on Saturday morning when I pick it up.
 
#8 ·
Could be this:
<TABLE cellPadding=4 width=720 bgColor=white><TBODY><TR><TD bgColor=white>
Image
</TD><TD vAlign=top width=394>SI B 84 16 07
Communication Systems
</TD><TD vAlign=top width=240>September 2007
Technical Service
</TD></TR></TBODY></TABLE>
Image

Image
designates changes to this revision

SUBJECT
Erroneous SOS Inactive Warning Message


MODEL
E60, E61 (5 Series) with SA609 (Navigation) up to 8/07 production

E63, E64 (6 Series) up to 8/07 production

E70 (X5) vehicles equipped with ZPP ( Premium Package) or SA639 (BMW Assist) and Navigation

(SA609) up to 9/07 production

E90, E91, E92, E93 (3 Series) vehicles equipped with ZPP (Premium Package) or SA639 (BMW Assist) up to 8/07 production


SITUATION
An erroneous check control message stating the 'SOS inactive' is displayed. The BMW Assist™ system functions normally.

Image
KOMBI Fault Code: A54 (Alive Phone) stored in fault memory when using DIS V51 or higher.

CAUSE
Software error in the RAD2 or CCC.

PROCEDURE

  1. Verify the customer complaint. Make sure the customer's complaint is not related to SI B84 17 07 (SOS Inactive Warning Message, No Communication with TCU). Refer to SI B84 17 07 for any of the complaints below:
    • The Telematics Control Unit (TCU) is NOT identified when performing a short test using the DISplus or GT1.
    • If the SOS button is pressed the call connects but the radio is not muted. The BMW Assist™ phone calls audio comes from the emergency speaker.
    • Bluetooth: An approved Bluetooth® enabled handset that previously worked no longer connects to the vehicle. The Bluetooth menus for pairing a device to the vehicle are unavailable.
    • RAD2 vehicles: The BMW Assist icon and phone icon are missing from the Radio display.
    • CCC vehicles: Enable Services is grayed out.
  2. Perform a short test using the DISplus or GT1.
  3. Work through any Telematics Control Unit (TCU) and MOST-bus communication faults. Diagnose and repair as necessary.
or this

<TABLE cellPadding=4 width=720 bgColor=white><TBODY><TR><TD bgColor=white>
Image
</TD><TD vAlign=top width=394>SI B 84 17 07
Communication Systems
</TD><TD vAlign=top width=240>September 2007
Technical Service
</TD></TR></TBODY></TABLE>
Image

This Service Information bulletin supersedes S.I. B84 17 07 dated August 2007.

Image
designates changes to this revision

SUBJECT
SOS Inactive Warning Message, No Communication with TCU


MODEL
E60, E61 (5 Series)

E63, E64 (6 Series)

Image
E65, E66 (7 Series)

E70 (X5) vehicles equipped with ZPP (Premium Package) or SA639 (BMW Assist)

E90, E91, E92, E93 (3 Series) vehicles equipped with ZPP (Premium Package) or SA639 (BMW Assist)


SITUATION
A check control message stating the 'SOS inactive' is displayed.

  • The Telematics Control Unit (TCU) is NOT identified when performing a short test using the DISplus or GT1.
  • If the SOS button is pressed the call connects but the radio is not muted. The BMW Assist™ phone calls audio comes from the emergency speaker.
  • Bluetooth: An approved Bluetooth® enable handset which previously worked no longer connects to the vehicle. The Bluetooth menus for pairing a device to the vehicle are unavailable.
  • RAD2 vehicles: The BMW Assist icon and phone icon are missing from the Radio display.
  • CCC vehicles: Enable Services is grayed out.
CAUSE

  • TCU Hardware failure.
  • MOST-bus communication issue.
  • Incompatible handset paired to the vehicle.
PROCEDURE

  1. Duplicate the complaint.
  2. Does the customer have a Bluetooth handset paired to the vehicle?
    • If no, proceed to step 3.
    • If yes, obtain the following information:
      • Manufacturer of the handset
      • Handset model number
      • Software number
      • Does the problem only occur when a handset is paired to the vehicle?
Note: Pairing on an incompatible handset can have adverse affects. Please refer to the 'Compatible Handset Information' section of this bulletin for more information.

  1. Check the BMW Assist account status on DCSnet. The BMW Assist services expiration date and the TCU activation status can be checked on DCSnet under Service/Vehicle History Inquiry. Refer to SI B02 01 06 (Updated DCSnet Vehicle History Inquiry information on BMW Assist) for more information.
    • If the customer has an active BMW Assist services account, test the BMW Assist services following the information outlined in 'Testing of BMW Assist Services' section of this bulletin.
  2. Perform a short test using the DISplus or GT1.
  3. Is the TCU identified when performing a short test?
    • Yes, proceed to step 6.
    • No, are any other MOST-bus modules identified?
      • Yes, check power, ground and the MOST-bus at the TCU.
      • No, perform a MOST-bus system analysis.
  4. Work through any MOST-bus communication faults. Diagnose and repair as necessary.
    • Check the MOST bus splice point for connection problems.
    • Check the MOST-bus optical connection. E.g. were the OPS/OPPS head is connected.
    • If anything was retrofitted on the MOST-bus (E.g. CDC, i-Pod, S-DARS, etc.) check the connections at the module that was retrofitted.
  5. If you can not duplicate the customer complaint and there are no MOST-bus communication faults, refer to SI B84 16 07 (Erroneous SOS Inactive Warning Messages).
  6. If the DISplus/GT1 cannot communicate with the TCU, power and ground are OK at the TCU and the MOST-bus communication is OK; the TCU should be replaced. Proceed to step 9.
TCU REPLACEMENT PROCEDURE

  1. It is NOT necessary to obtain a Part Replacement Authorization (TeileClearing) for this specific issue. Refer to the Warranty section of this bulletin for more details. Additional information can be found in SI B84 23 05 (Enhanced Support for BMW Assist Telematics Control Unit (TCU) with Bluetooth & CPT9000 Phone Systems).
  2. Refer to TIS (RA 84 11...) for the TCU replacement procedure.
  3. Before installing the new TCU, remove one copy of the Electronic Serial Number (ESN) label and place it on the repair order for reference during warranty claim entry. You will be asked for the new TCU "ESN" when submitting a claim via DCSnet. Refer to SI B01 10 05 for more details.
<TABLE cellSpacing=2 cellPadding=5 width=610 border=0><TBODY><TR><TD>
Image


</TD><TD>
  1. The second ESN label of the TCU should be affixed over the existing label in the Owner's Manual insert (P/N 01 49 0 157 963).
</TD></TR></TBODY></TABLE>
  1. Complete the TCU installation
  2. Using Progman V26.01.00 or higher, program the complete vehicle. Refer to SI B09 05 01 "Coding, Individualization and Programming", Procedure A.
  3. Initialize BMW Assist following the procedure starting at step 16.
Not entire bulletins but enough to help in search.

Entire bulletins in adobe here:
 

Attachments

#9 ·
Cobradave you are DA MAN!!!!! I'm printing that out and taking it with me to service.

I swear this is the best car club board i have ever been on.

Thanks again guys!

Dan<SCRIPT type=text/javascript> vbmenu_register("postmenu_1179789", true); </SCRIPT>
 
#11 ·
Just a follow up on this problem.
I had it too. Had a service appt booked and everything.

Then I did a brake fluid flush and cleared the associated maintence service warning for the flush. Somehow that cleared the SOS warning, and all my music/ etc is working again.

Long story short, try clearing your codes, and that might fix your problem.

I found this thread while searching for the issue on my e70 x5. Thought it might help others.
 
#12 ·
What a coincidence, I just had this SOS error pop-up over the weekend for the first time and here is a thread revived about just that subject.

The SOS warning came on and the radio would not work. I didn't check the Nav screen, I just did what I always do when Idrive acts funky, I did the handy mute/eject/eject three-finger punch and all was well after the reset. I had just chalked it up as another one of those quirky Idrive moments. I have had many over my 4 years, is it weird that I had pretty much forgotten the whole incident until this thread jogged my memory? I am gettin numb to such things.

Now I watch to see if it is an impending hardware failure.