|
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
|
|||
|
|||
MK4 responds twice to all i-bus input
This post may be way too technical, but hopefully there is someone on here that knows these units inside and out. Anyway, I picked up an MK4 to fit in the E39. It seems to function fine, will navigate, and it took my OS update to V32. However, it has 2 problems. 1----- The first, is that the unit does not seem to sleep properly. It will spin down and the power light will go out for a second before it boots back up again. If I close the car and lock it, the unit will eventually sleep, but it essentially hibernates, because it doesn't wake back up when car is unlocked or door opened or key in the ignition. Sometimes if I leave the trunk open (noticed this once or twice), I notice it will sleep after awhile (power LED off), but the eject button stays lit and will pulse. 2----- The second issue (which may be related or a cause of the first) is that, when up and running, it duplicates all I-bus commands. What I mean is that each turn of the knob translates to 2 movements on the screen. Each press of the knob translates to 2 clicks on the screen. Thus, I can't select certain menus and set certain things (such as the clock or DSP sliders). I can enter the nav secret menu, but get booted right out when I release the menu button because of the message duplication. Additionally, reading the unit in NavCoder causes all kinds of problems. When NavCoder requests OS mode, for example, the unit responds, but with 2 lines of identical code to each NavCoder request. Thus, NavCoder gets all messed up because the nav feeds it duplicate information for the wrong fields (just figured this out actually comparing the defective MK4 to my good MK4 in the E38). I know this is an internal unit thing because it does this in the E38 and E39. NavCoder shows only 1 command but the MK4 responds twice. One NavCoder request elicits two identical MK4 reponse messages. And the MK4 will occasionally poll the car for device status requests, but only outputs ONE status request. SO, this tells me something inside is causing an i-bus input message to duplicate. Anyone know the hardware on these boards? There are two Elmos 10020B chips, which I know are the I-bus interface for the drive. What I don't know is why two? And could they be both passing the same message somehow? Is it worth just changing them both? Thanks for the input. |
Sponsored Links | |
|
Bookmarks |
Thread Tools | |
Display Modes | |
|
|
|