T6 Aftermarket Digital Instrument Cluster

[sparkzer]

To add to the list of observations (that i assume are already being worked on, as they seem quite obvious and easy to occur)

I've had a few persistent (should be momentary, but wont clear until a ignition cycle) vehicle statuses..

For example:

'Depress Clutch' when starting (i expect i started cranking before i fully pressed the clutch)
'Start manually' when a stop/start stop has occurred, but for some reason it wants a manual crank (for example opened the drivers door)

I also think i had a 'engine starting' not go away after start....i think i rushed the display by unlocking, getting in and cranking before it had chance to wake up.

Nothing major and more of an annoyance than anything else, but a nice 'low hanging fruit' for a software engineer to rectify...im using the latest Jan release of firmware.

 

[catfood12]

Any news/firmware update to rectify the dropped character @antony.charnley ?

Rang
e

One of those little things that will end up driving me mad

I don't think this is fixable. The character string comes from the old dash; it's not generated by the new dash. The string was formatted to fit the old dash's MFD. The new dash has a different display format in terms of number of characters wide, and just displays what it is sent, and I guess the display driver does a character feed/new line when all the characters on a line are displayed.

The new dash just displays the string and doesn't reformat it. It would be a fair change in the code to recognise some messages and reformat or justify for the new dash display. Then there would doubtless be hidden service messages, odd control characters etc and differences between messages in old dash s/w & h/w versions etc..

You never know though, they might code a new routine to fix the for
mat issue.