|
||||||||
| 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
|
||||
|
||||
|
I have a 2001 330Ci with navigation and recently I started having problems with it. Well.., it is actually one problem. It won’t go into sleep mode after the car is turned off and locked. If I don’t drive the car for a couple of days the navi would drain the battery. I have an mk3 computer which is not the original unit but it worked without any problems for about 6-8 months. When I got the car I had to replace the original unit because it was dead. I have searched the net and many forums without any luck. Does anyone have any suggestions how to fix this problem? Any help will be greatly appreciated! |
| Sponsored Links | |
|
|
|
|
#2
|
|||
|
|||
|
My NavCOder software can help you diagnose the problem by showing the databus activity in real time. You can thus observe what is really happening , post the data logs here, and we can help you to diagnose the problem.
It could be another device that is not going to sleep, thus keeping the nav awake. |
|
#3
|
||||
|
||||
|
Jochen, thanks in advance!
I am attaching the most recent NavCoder log file. |
|
#4
|
|||
|
|||
|
Quote:
Perhaps you could tell me at what time you turned the key off ? EDIT: you never did. In the entire log file, the instrument cluster reported that the ignition was always on. That's why the nav can never turned off. If you actually did physically turn the ign off, then the symptoms indicate that the ignition switch is faulty, as the IKE is always reporting ign is in Position1 (Acc). EDIT2: I don't trust your log file. You have recorded lots of diagnostic activity, meaning that you were constantly asking for data. In such a case the nav won't go to sleep, because it is always active. Post another CLEAN log file showing nothing more than 1. Start logging 2. Turn key off 3. Close doors and lock car 4. Wait 5min 5. Stop logging A clean, listen-only log file. Post that file for further diagnosis Last edited by KiwiJochen; 11-05-2008 at 02:53 PM. |
|
#5
|
||||
|
||||
|
SORRY. I am still learning
I did the steps you described and here is the result: 11/5/2008 1:16:25 PM: NavCoder v2.5.31 logging started 11/5/2008 1:16:28 PM: MFL --> SES : Device status request 11/5/2008 1:16:28 PM: RAD --> CDC : Device status request 11/5/2008 1:16:28 PM: MFL --> TEL : Device status request 11/5/2008 1:16:30 PM: NAVE --> IKE : Time & date: UTC 21:11 05/11/2008 11/5/2008 1:16:30 PM: BMBT --> RAD : Device status request 11/5/2008 1:16:30 PM: RAD --> LOC : Device status ready 11/5/2008 1:16:30 PM: GT --> IKE : Device status request 11/5/2008 1:16:30 PM: IKE --> GLO : Device status ready 11/5/2008 1:16:33 PM: GM --> GLO : Doors/flaps status: Open: DvrDoorFr WndwPgrRr Boot Bonnet Ctrl_Locking: Unknown 11/5/2008 1:16:33 PM: GM --> GLO : Doors/flaps status: Open: DvrDoorFr WndwPgrRr Boot Bonnet Ctrl_Locking: Unknown 11/5/2008 1:16:33 PM: GM --> GLO : Doors/flaps status: Open: DvrDoorFr WndwDvr WndwPgrRr Boot Bonnet Ctrl_Locking: Unknown 11/5/2008 1:16:35 PM: RAD --> BMBT: Cassette control, Data="00" 11/5/2008 1:16:35 PM: IKE --> GLO : Ignition status: Off 11/5/2008 1:16:35 PM: GM --> GLO : Sunroof control: Lock 11/5/2008 1:16:36 PM: EWS --> GLO : Immobiliser status: Immobilisation_deactivated Vehicle_immobilised 11/5/2008 1:16:36 PM: ACM --> GLO : Remote control central locking status, Data="00 00 05" 11/5/2008 1:16:36 PM: ACM --> GLO : Remote control central locking status, Data="02 00 05" 11/5/2008 1:16:38 PM: GM --> GLO : Doors/flaps status: Open: WndwDvr WndwPgrRr Boot Bonnet Ctrl_Locking: Unknown 11/5/2008 1:16:39 PM: GM --> GLO : Doors/flaps status: Open: WndwPgrRr Boot Bonnet Ctrl_Locking: Unknown 11/5/2008 1:16:42 PM: GM --> GLO : Doors/flaps status: Open: WndwPgrRr Bonnet Ctrl_Locking: Unknown 11/5/2008 1:16:43 PM: GM --> GLO : ChkCtrl Remote Central Locking message: Bit1 Bit2 Bit4 11/5/2008 1:16:43 PM: GM --> GLO : Doors/flaps status: Open: WndwPgrRr Bonnet Ctrl_Locking: Unlocked 11/5/2008 1:16:43 PM: GM --> GLO : Doors/flaps status: Open: WndwPgrRr Bonnet Ctrl_Locking: Unlocked 11/5/2008 1:16:44 PM: GM --> EWS : Cmd_0x73, Data="00 00 80" 11/5/2008 1:16:44 PM: EWS --> GLO : Immobiliser status: Immobilisation_deactivated Vehicle_immobilised 11/5/2008 1:16:44 PM: GM --> GLO : ChkCtrl Remote Central Locking message: Bit1 Bit2 11/5/2008 1:16:45 PM: EWS --> GLO : Immobiliser status: No_key_detected Vehicle_immobilised 11/5/2008 1:26:01 PM: GM --> GLO : Device status ready 11/5/2008 1:26:01 PM: GM --> GLO : ChkCtrl Remote Central Locking message: Bit1 Bit2 11/5/2008 1:26:01 PM: GM --> GLO : Doors/flaps status: Open: WndwPgrRr Boot Bonnet Ctrl_Locking: Unlocked 11/5/2008 1:26:01 PM: EWS --> GLO : Immobiliser status: No_key_detected Vehicle_immobilised 11/5/2008 1:26:02 PM: IKE --> GLO : Device status ready 11/5/2008 1:26:02 PM: IKE --> GLO : Ignition status: Off 11/5/2008 1:26:06 PM: NavCoder logging stopped, NavCoder closed |
|
#6
|
|||
|
|||
|
OK, here's the kast ibus message:
11/5/2008 1:16:45 PM: EWS --> GLO : Immobiliser status: No_key_detected Vehicle_immobilised At around 1:17:45 the nav should have gone to sleep - did it? From 1:26:01 is when you did something again, my guess is you opened the boot Try the same again, with the boot open. Observe the red LED on the nav, it should go out 60s after the ibus activity stops. 11/5/2008 1:26:01 PM: GM --> GLO : Device status ready |
|
#7
|
||||
|
||||
|
Yes, 1:26:01 is when I opened the boot.
After looking at the log myself, I thought that the nav went into 'sleep' mode too; however, it was not the case, because when I turned the key to pos1 the screen went straight to showing the map (no splash screen, and no 'Accept' screen; that's how I knew it never turned off). Also, when the boot is open the red LED never goes out. I even folded the back seats so I can see into the trunk area, closed the doors and boot, locked the car, and checked the nav LED through the window. It stays ALWAYS ON. I think it is a really strange behavior. I am getting more and more frustrated with this nav system! |
|
#8
|
||||
|
||||
|
Is there maybe a relay or something that is responsible for switching off the electronics when the car is turned off?
Any suggestions? Comments? |
|
#9
|
|||
|
|||
|
Quote:
To determine if it is the nav, measure residual current drain when car has gone to sleep. Spec is about <20mA I believe If it is high, remove the nav fuse and then remeasure. You may simply have faulty nav hardware You could always try a full nav software reload... |
|
#10
|
||||
|
||||
|
Quote:
What do you mean by "full nav software reload"? I tried loading the v27 and v28 software. Even though it updates without any problems, the nav system still won't go to sleep. |
![]() |
| Bookmarks |
|
|
|
|