B

blue_cheese

Well-Known Member
Afternoon,

Got my Nanocom today, so have been eager to fiddle.
So far I've disabled the immobiliser to save myself from key issues, and also enabled dipped headlights on all the time.

One thing I noticed, was a setting for syncing the odometer.
Since I've had my P38, it always beeps with 'Odometer Error' on startup, and shows a mileage around ~85k
I clicked 'sync odometer' and my mileage jumped up to 104k. The error also went away.

I'm guessing that 104k is the actual milage, and someone before me fitted clocks with less miles? Or am I talking nonsense?

Also want to hear your other essential Nanocom changes/tips you've all done :)

Thanks
 
blue_cheese said:
Afternoon,

Got my Nanocom today, so have been eager to fiddle.
So far I've disabled the immobiliser to save myself from key issues, and also enabled dipped headlights on all the time.

One thing I noticed, was a setting for syncing the odometer.
Since I've had my P38, it always beeps with 'Odometer Error' on startup, and shows a mileage around ~85k
I clicked 'sync odometer' and my mileage jumped up to 104k. The error also went away.

I'm guessing that 104k is the actual milage, and someone before me fitted clocks with less miles? Or am I talking nonsense?

Also want to hear your other essential Nanocom changes/tips you've all done :)

Thanks
Click to expand...

Check past MoT test history and see.

If either the odometer or BECM doesn't match then it will jump to the higher figure. Cluster or BECM might have been changed.
 
blue_cheese said:
Good idea.

Just checked the MOT history, and it seems to align with the original figure of 85k.

Is what I've done reversible?
Click to expand...

Not easily. Might be possible with Faultmate MSV?

Need someone more knowledgeable about where and how the data is stored. If you can work out how to change one of them then change it to 999,999 and reinstall and sync. Drive a mile or two to take it round the clock. Change it to the right number (which will now be higher) and sync again.

Thinking aloud, I wonder if you keep changing between miles and kilometres if it changes the number up each time?!
 
blue_cheese said:
Good idea.

Just checked the MOT history, and it seems to align with the original figure of 85k.

Is what I've done reversible?
Click to expand...
Not with a nano.
Only with faultmate and the BECM expensive pack.
But it could have been sorted apparently if you hadn’t done what you done.

J
 
@martyuk could do it I think. It's a BECM and binnacle out job to fix though. Unless you're really keen, I'd just try and live with it.

I have my wipers set to "speed". They go intermittent wiping whilst stopped at the lights.
 
blue_cheese said:
Afternoon,

Got my Nanocom today, so have been eager to fiddle.
So far I've disabled the immobiliser to save myself from key issues, and also enabled dipped headlights on all the time.

One thing I noticed, was a setting for syncing the odometer.
Since I've had my P38, it always beeps with 'Odometer Error' on startup, and shows a mileage around ~85k
I clicked 'sync odometer' and my mileage jumped up to 104k. The error also went away.

I'm guessing that 104k is the actual milage, and someone before me fitted clocks with less miles? Or am I talking nonsense?

Also want to hear your other essential Nanocom changes/tips you've all done :)

Thanks
Click to expand...
Turn off EKA as well to avoid problems.
It sounds like the BECM has been changed at some time. Normally the mileage will auto adjust to which ever is the higher mileage BECM or instrument cluster.
Changing it back can be done but it's complicated without a Faultmate and the expensive direct access module.
 
blue_cheese said:
Number makes no difference to me, was just thinking it might look odd on the MOT history.

I'll live with it for the time being
Click to expand...
Just advise the MOT centre that the instrument cluster has been changed. Keep a note of the original mileage and the new mileage at the point it appeared, then the tester will be able to see how many miles you have covered.
 
You must log in or register to reply here.