New instrument cluster - won't sync with Nanocom

Quote:

---

Originally Posted by sierrafery

not very important down under

---

I have found it is useful for when the disco is parked in the sun in town and I use it to cool the inside down while I do other things or if I have the dog or cat in it while I have to leave it parked momentarily.
Cheers Scott

its great.
go to work, leave car running all day, finish work, drive home in perfect temperature.
sometimes need to gas up over lunch but its a small price to pay

Quote:

---

Originally Posted by xaymaca

I don't know what little cluster fairies visited last night, but they must have stuck in while I slept.
Started off on my camping weekend this morning and it's all synced up!? What the!

Sent from my HTC_0P6B using AULRO mobile app

---

May be the last process was . Switch off ignition after the sync. Once you did that on next start it syncs?

:Rolling::Rolling::Rolling::Rolling::Rolling::Roll ing::Rolling:

Quote:

---

Originally Posted by Eevo

its great.
go to work, leave car running all day, finish work, drive home in perfect temperature.
sometimes need to gas up over lunch but its a small price to pay

---

Quote:

---

Originally Posted by xaymaca

I don't know what little cluster fairies visited last night, but they must have stuck in while I slept.
Started off on my camping weekend this morning and it's all synced up!? What the!

Sent from my HTC_0P6B using AULRO mobile app

---

yes, after 16 consecutive wrong readings it should sync up itself automatically, maybe that was the 16'th ignition cycle:confused:

I don't know if you're serious about that or not haha

Sent from my HTC_0P6B using AULRO mobile app

I was, in RAVE is covered only the reverted action but it happens vice-versa too i've seen it

Quote:

---

Originally Posted by RAVE: BODY CONTROL UNIT - 86-3-32 DESCRIPTION AND OPERATION

....If the instrument pack odometer value is greater than the maximum allowed value, the maximum value is
assumed. The BCU odometer value is stored in EEPROM. If 16 identical values of the instrument pack odometer
reading is received consecutively, the instrument pack odometer value is compared with the BCU odometer value. If
the consecutive readings from the instrument pack differ, the BCU odometer value is incremented accordingly. If the
BCU odometer value is less than the instrument pack odometer value by up to 10 km, the BCU odometer value is set
equal to the instrument pack odometer value....

---

Haha that's crazy cool!

Also, I've noticed now that I get 6 chimes upon startup from the dash every time. No faults logged in nanocom.

Any more knowledge nuggets that could help me?

Sent from my HTC_0P6B using AULRO mobile app

Don't mind me! Was the seat belt chime. Didn't do it with the old cluster, read a post that suggested only the d2a chimes for the seatbelt!

Either way, now off 😊

Sent from my HTC_0P6B using AULRO mobile app

Yes, nanocom used to have a mind of it's own when it's connected to the BCU and it might have enabled the seatbelt audible warning or something without request... go again through all the settings to check and make sure that the seatbelt warning is disabled

EDIT: i was writing while you posted :)