badmyan

I now have the new sftware on my A8L, and it seems to have addressed the reboot issue, at least for me. I need to keep an eye on it, but pror to the upgrade playing with the MMI while driving always crashed it. Now it's really happy and I like the new clock.

It really was not that bad of an issue, but it still needed to be fixed. I'm very glad I did have it addressed

So racerxj8, stop whining and maybe you to can have it fixed.

For everyone else, I will keep you posted on how it is oer the next little bit. I really do reccomend the upgrade, it certianly did not hurt anything, and even if it turns out that the problem is not 100% fixed it is better with the upgrade.

Paldi

So.. Monday turned out to be a Good Day for you afterall! :-)

badmyan

Paul,

In answer to the following
'It's a digital signal, transmitted continuously at a frequency of 210 MHZ. The voltage difference between the dominant and recessive (I take that to be the 1's and 0's) is less than 0.5V (does not specify if it is AC or DC).

It monitors if the system is good or not, if the signal is bad, it sends a code to the display control head, and a fault can be pulled.

It also states "The signal cannot be checked with measuirng instruments that are currently available".....what the heck does that mean???'

You need a scope to see that signal, the use of a meter is out of the question. Also at 210MHz, you need a moderatly expensive scope to see the signal. I have a DSO - Techtronics TDS2024 (four channel 200MHz per channel + trigger) which probably could do the job. A 300MHz scope is really required though.

I you really really want to pursue it further let me know. I amy be able to capture the signal for you.

I don't belive the system reboots in general are related to bad connections etc. This type of signal not going to tolerate bad connections, and if it for some reson is intermittent, I would expect error correction or retransmit. The problem from the best I can tell is an incompatbility issue between the higher level software and the firmware causing a trap.

badmyan

Contary to popular belif, the Nav disk does appear to contain software. It looks very much like the Nav system boots from the Nav disk.

From the descriptions I was given, it seems there is a software bug which is corrected with the new Nav disk which caused a problem with the Nav unit communicating on one of the system buses. Which one I'm not sure but it could have been CAN.

badmyan

In a way, it was still after all a Monday!

Randy Welch

The nav disk has software, but it's specific to the NAV unit itself, not the whole MMI system.

badmyan

If the interface software is buggy, the MMI communications with it is buggy, and therefore unreliable/troublesome.

PaulW

Thanks for the info