Go with your wife is more important than our cars.

I've got the same problem ;-)

Trapdoor - thanks, I think I'll try the recoding option first, but with regard to my point about downgrading, how is this achieved?

KJ - any suggestions on my i-Bus access questions above?

>> I've noticed a few other unused similar 3-pin plugs on various wiring looms in the area of the CD & Nav units, are all these i-Bus connectors?

If the plug has a white/grey/yellow wire, then that wire is the ibus.

The ibus is always white with grey stripe and yellow spots.

Hi Keith

>A scan of my car provides this (I have DVD nav, dual tuner BM24, 16:9

You audio scan looks good.
You do not have the latest software version loaded into your Mk4 nav unit.
You have 4-1/80 at the moment, I recommend you update to 4-1/91, which is a bug-fix release. You will find 4-1/91 on the V29 and V30 OS discs.

>Side effects are all the time I have NavCoder running the Bordmonitor
>screen is blank and can not be used, to correct this requires
>disconnecting the laptop and cycling the ignition and sometimes a
>battery off reset

The issues you are experiencing are due to data collision on the databus.

I have implemented a carrier-sense multiple-access collision-avoidance (CSMACD) algorithm that is good, but not perfect. It could be better :-)

On some cars with very busy data-busses, data collision can occur.

My car, which is my main NavCoder test bed, does not have as busy a databus as an E46 or, apparently, a Rover.

Given my limited test lab capabilities - ie: my own car - I am limited in what I can implement and test.

Also, my CSMACD is something that is working quite well now, but if I break it creates a lot of headache to get working again. It took me months to implement the current CSMACD version :-)

You issues are however temporary, and I wouldn't worry about them. I don't. If a collision occurs and things go strange, just reset (re-boot) the car (ign off, or battery off). It'll be fine afterwards. Just like Microsoft Windows, sometimes a reboot is required :-)

>The shareware version obviously does not let me code the TV tuner so
>I have no idea if that will work

It WILL work. I have never found a video module that is non-compliant. The coding works on all modules.

>when I disconnected my laptop I noticed my TV tuner came back to life
>with German menus!

It simply reset to language 00, which is German. Change the language to whatever you want.

>Now this is talking to my car I am interested in coding MG rover
>units with the BMW firmware did you get the Rover OS CD I sent you or shall
>I upload one to somewhere like MegaUpload?

Yes, I got the CD - thanks. I have used it in my testing with an original LRO nav unit. However, extensive tests reveal that the locking to LRO (land rover) OS software is buried deep in the flash EEPROM and I cannot find how to change it. I have since sold my LRO nav - the one and only LRO nav I have ever seen :-)

>It would also be nice to code Mono Rover units to colour as well if
>poss

Yes, this should be possible. I have never seen a mono LRO nav. Can you tell me what output mode it uses?
Use NavCoder, and read the output mode. This is important for me to understand the difference between LRO colour and LRO mono boot loader.
Colour = LROC01O, but what boot loader is the mono LRO nav?

>I would like to see if unlocking TV in motion works in the Rover
>eventually

Yep, works fine.

Regards, Jochen

As Rolf's interface unit hasn't arrived yet I elected to go with upgrading the software, firstly rolling back to v21.1 and then upgrading to v30. After doing so I went into the Telematics Settings screen and noted that the Vehicle Type had changed from from X3 (from where my MKIV unit originated) to 7er, and the VIN number had disappeared. However, the end result is that the Distance and Arrival Time functions are working once again, I'll simply code the above boxes when I get the interface unit, so all is good.

Jochen - whilst doing the above software changes I had a quick look at one of the unused 3-pin plugs and noted the wires were red, brown, and red/yellow, so I guess it's not an i-Bus plug, however, now I know the correct colours I can check out some of the other unused 3-pin plugs when I delve deeper.

On the NavTweak front, whenever I try to open navtweak.exe I get an error message similar to another member - This application has failed to start because libgdk-win32-2.0-0.dll was not found.

I'll Google that to try and see where the problem is.

I bet you get the 'not found' message because the gdk library was not found :-)

If you read the NavTweak instructions, you will note that it states you have to install the GDK library

Can you guess what you have to do now....??

Hi Jochen
I haven't upgrade to Ver whatever the latest is because it means creating a new splash screen disk and I got lazy

Have you looked into if Navcoder can alter 4:3 Tv Tuners to 16:9 is that possible or does that require a Hardware mod instead?

__________________
Keith Alexander
Rover 75 CDT Connoisseur Se, MG ZT+T 190, MG ZT 260
Ellesmere Shropshire England

The change from 4:3 to 16:9 is not a coding option, so NavCoder cannot do it.

It requires new firmware to be loaded into the video module

There is a company in Germany that does this for about 100 Euros.... or you might just like to buy a replacement 16:9 video module.

GDK library installed, Navcoder serviceable.