Thread: New instrument cluster - won't sync with Nanocom

Did you try to disable the odometer warning first then synk odometer to BCU?, insist only on this, make the odometer to not flash first by disableing the warning then synk odometer to BCU, not vice-versa... if no joy it means the BCU's EEPROM got mixed up by those mutiple attempts especially if you tryed to synk BCU to odometer first and it got lower reading which is against the protocol

IMO this particular side of the system is quite unstable both ways odometer or BCU so you might have to live with it.

I tried searching for the odometer warning flash setting but couldn't find it! Will have another look and then try to sync again.

I think the wording is terrible and ambiguous for both options.

While you're here, what is the "reset the new flag" setting? Cannot find any documentation on it at all!

Sent from my HTC_0P6B using AULRO mobile app

I just found it on my settings map. Under transm-lock-warn in settings of the bcu. Will give that a shot when I get home.

What the hell is bathrobe lock option!? Lol!

Sent from my HTC_0P6B using AULRO mobile app

not very important down under

Bathrobe lock option: When bathrobe locking is enabled, the engine can then be started
and then the vehicle locked with a spare key. This allows the vehicle interior to reach the
desired temperature without the driver needing to be present. It should be noted that the
vehicle security system is not set during this procedure; only the central door locking is
activated. This feature is very desirable in cold countries

Originally Posted by sierrafery

not very important down under

What sort of a WUS would need that???!!!
I just wear my jocks (underpants).
Only joking!

Ok I got home, stopped it from flashing. Still no love with the sync Tried both options to sync each way too.

I've uploaded a video of what it does, it's like it doesn't try.

[ame="http://youtu.be/ixrNbHOhD0A"]http://youtu.be/ixrNbHOhD0A[/ame]

Trying to update firmware to 1.29 (currently 1.09) but struggling because the nanocom ID was previously registered to another member! Doh!

May be your Nanacom is playing up?
I have had this happen that it chucks a razz and looses communication during a process

I've tried connection various ways. Ignition on, ignition off, going to "write settings" in settings after pressing sync.
My only thought is that the revision on the firmware is buggy. So frustrating!

Sent from my HTC_0P6B using AULRO mobile app