Trip Computer Option On High-line

[scoubix]

Had forgotten about this thread and my commitment to check on my launch car, just did tonight and I have the same HW/SW rev as Thomas (which kind of makes sense considering both of our launch cars are quite close to each other, VIN-wise)



As mentioned previously, I do believe that the HW/SW revisions of the IPK itself might be a factor here. It would be interesting if those who have already contributed on this thread could also check their IPK revisions using the diagnostics menu.
You're looking for the following values :

1.2 Cluster Part Number
1.3 Coding (04)/diagnosis (52)/bus index (10)
1.4 Week of manufacture (eg. 1200 = week 12)/year of manufacture (eg. 2000) 1.5 Hardware number (eg. 09) and Software number (eg. 11600 = 16.0) of IPK.

Here are my own values :
1.2 Cluster Part Number



1.3 Coding (04)/diagnosis (52)/bus index (10)



1.4 Week of manufacture (eg. 1200 = week 12)/year of manufacture (eg. 2000)



1.5 Hardware number (eg. 09) and Software number (eg. 11600 = 16.0) of IPK

[vfr16v]

SW 41
HW 41

Retrofitted, i've the trip computer in my IPK. It appears when i tested my setup for the first time... after a restart, it disappeared.

[RichardP]

I'm pretty sure the option to display the Trip Computer is the result of a message from the IKE (Cluster).

Anyone have an Intravee that does NOT have the Trip Computer option? I may be able to prove it by sending the message directly.

[frodobaggins]

SW 42 HW 42 no trip computer on Highline but have it on IPK

[scoubix]

Originally Posted by RichardP

I'm pretty sure the option to display the Trip Computer is the result of a message from the IKE (Cluster).

Anyone have an Intravee that does NOT have the Trip Computer option? I may be able to prove it by sending the message directly.

I kinda fit the profile
As reported above, my Trip Computer option is there, but everything inside it has no values at all. Mind you, my drive is MKIV so not the original Rover one...

[Mr_Shed]

Originally Posted by scoubix

I kinda fit the profile

As reported above, my Trip Computer option is there, but everything inside it has no values at all. Mind you, my drive is MKIV so not the original Rover one...

That's interesting, since I installed the click module from Duncan the computer option has come up. But as per yours Scoubix there is no values in the relevant boxes.

[RichardP]

Originally Posted by Mr_Shed

That's interesting, since I installed the click module from Duncan the computer option has come up. But as per yours Scoubix there is no values in the relevant boxes.

Yep, that's what I'd expect.

When the Nav sees a message from the IKE it enables the Trip Computer display, the Clock module sends a time message to the GT (Graphics Device) as if it's from the IKE to tell it the time.

The Nav then sends messages to the IKE requesting the values to display on the Trip Computer screen, but your IKE does not respond so the values remain blank.

It may be that the IKE just does not know about the GT device, so does not respond to requests from it, it may respond to the same messages from another address, for example the DIG (Diagnostic) address.

It may not respond at all to these requests as the earlier clusters don't know about the Nav system. If that's the case then only a replacement cluster or a software update will be the only options.

[scoubix]

Richard, just a little technical background on this so you better understand this discussion.
75 cars fitted with the nav system from factory (so-called hiline navigation in 75 litterature) have this trip computer option which, as you mentioned, is an interaction between the cluster and the nav system. 75s have never been fitted with a clock module on the Kbus so it acts without one. What we've all come to realize is that some early production cars, such as mine, which are among the first few hundreds to come out of the factory, do not have this trip computer option showing up at all...even though it was documented even in pre-release technical material.
As I had the opportunity to look at the very first production car, which resides now with the Heritage Centre museum at Gaydon, I can confirm that this car doesn't have it as well.

My suspicion is that a cluster revision was introduced very early in the production to enable this feature, which my car and a few others missed.

Now it shows up on my nav because, as Mr_Shed pointed out, we have both fitted out a clock module to our systems. Didn't think there was a relation between the two, but it makes sense. Yet this doesn't obviously allow the feature to work...
The feature only works from factory or if the hiline system has been properly retrofitted, including the "message centre" cluster IPK and the car gone through the Rover diagnostic tool (T4) to enable both navigation and message centre options...
Those options are enabled on my car, and the system was fitted from factory. So the only possible explanation is indeed that cluster revision.

Reebs started this thread because it was suggested the the HW/SW revision of the boardmonitor itself might be at cause. To me it's likely to be irrelevant, as the monitor is just what it is...a monitor.

[RichardP]

Scoubix, what you are saying sounds entirely plausible and fits in with what I know of the way the Nav system interacts with the cluster.

For what it's worth, the possible requests for data from the Nav to the cluster are as follows :

Time Request
3B 05 80 41 01 01 FF

Date Request
3B 05 80 41 02 01 FC

Outside Temp Request
3B 05 80 41 03 01 FD

Consumption 1 Request
3B 05 80 41 04 01 FA

Consumption 2 Request
3B 05 80 41 05 01 FB

Range Request
3B 05 80 41 06 01 F8

Distance Request
3B 05 80 41 07 01 F9

Arrival Time Request
3B 05 80 41 08 01 F6

Limit Request
3B 05 80 41 09 01 F7

Average Speed Request
3B 05 80 41 0A 01 F4

Memo State Request
3B 05 80 41 0C 01 F2

Code Request
3B 05 80 41 0D 01 F3

Stopwatch Request
3B 05 80 41 0E 01 F0

Timer 1 Request
3B 05 80 41 0F 01 F1

Timer 2 Request
3B 05 80 41 10 01 EE

Aux Heating Off Time Request
3B 05 80 41 11 01 EF

Aux Heating On Time Request
3B 05 80 41 12 01 EC

Aux Vent Off Time Request
3B 05 80 41 13 01 ED

Aux Vent On Time Request
3B 05 80 41 14 01 EA

3B is the GT address, 80 is the cluster. If the problem is simply that the cluster does not recognise the GT device then it's possible it may respond to requests from, for example, the GM (00) or Body Electronics (09).

It would be interesting to see if the Cluster responded to any of these. For example, I know the cluster holds the outside temperature, the Intravee displays it as a result of a broadcast from the cluster. So if the message

00 05 80 41 03 01 C6

or

09 05 80 41 03 01 CF

is sent, does the cluster respond?

[scoubix]

Well I don't know if the cluster actually replies to queries for the outside temperature, but one thing for sure is that the only thing that actually works within the Trip Computer on the nav, is the outside temp, which is accurately reported
My car currently is at my garage, getting some paint work and reverse sensors fitting, should get it back on Friday evening, and will try to get some kBus logs for you. I'm doing a 2hr drive and back on saturday so I might take this opportunity to do a long iBus log.
If you were to have a look at it, is it OK if I take this log with Navcoder? I'm more familiar with it than with the IV downloader...