Mileage out of sync (blinking)

[er-minio]

Ok. New one.
Still, while returning to the UK, going through check-in at the port, I had to start/stop the bike a few times in a row.
The battery is on its way out (lasted >6 years, can't complain) and during one of the last starts the bike really struggled, but I insisted as I had to vacate the passport control.

I noticed that my odometer started blinking.
From memory that happens when the dashboard (kombi) mileage data goes out of sync (>100km) with the mileage data stored in the ECU, and can be triggered by low battery voltage, etc.

I don't think this is something that can be fixed via Motoscan.
I disconnected the battery now and will leave the bike sit a few hours and then try and restart and see if it is still blinking.

Anyone been through this? Can it only be fixed via dealer?

 

[OnHellas]

I experienced the same some years ago on my F800GS.
The bike suffered from the ring antenna fault and that seemed to throw out the mileage. Nothing else was changed.

A visit to the local BMW dealer sorted it out. They plugged the bike in and all was well. They did question whether I’d changed the ECU.

That’s my experience, albeit from 2016.

 

[DJ123]

Ok. New one.
Still, while returning to the UK, going through check-in at the port, I had to start/stop the bike a few times in a row.
The battery is on its way out (lasted >6 years, can't complain) and during one of the last starts the bike really struggled, but I insisted as I had to vacate the passport control.

I noticed that my odometer started blinking.
From memory that happens when the dashboard (kombi) mileage data goes out of sync (>100km) with the mileage data stored in the ECU, and can be triggered by low battery voltage, etc.

I don't think this is something that can be fixed via Motoscan.
I disconnected the battery now and will leave the bike sit a few hours and then try and restart and see if it is still blinking.

Anyone been through this? Can it only be fixed via dealer?

There should be a code in the background telling you what is causing the mileage disconnect. Usually once that is solved the Bike should correct itself and work as usual.

 

[Pukmeister]

I had similar after disconnecting and then reconnecting the instruments. Pushing the multi plug fully home beneath the cluster sorted it.

 

[botus]

found a bit on Hex forum, a number of techs came back saying if you get a mismatch of >100 km between the cluster and the DME it will throw the error as described

dealers can re syn - but no one says they have managed with third party tools

 

[er-minio]

Yep, that's pretty much what I remembered too.
Makes sense they do not allow third party tools to re-sync as the blinking is actually an anti-tampering measure.

 

[botus]

if you have GS911 - I'd still pitch the question to them - for us its more about using second hand parts - you are not altering the the mileage (thats way harder) - in case unaware

across the entire motor industry its normally possible using dealer kit to wind cluster mileage forwards - but backwards is not possible - and going to max mileage and hoping to rollover to zero and then winding forwards is also locked out

the winding forward feature is to allow a new cluster to match the vehicle's actual mileage - (if the cluster has the correct VIN in there now, a helpful dealer might be able to help)

 

[er-minio]

No, just Motoscan.

 

[er-minio]

Resurfacing this one.
There is no options in Motoscan. I guess my only remaining option is a BMW dealer.

 

[botus]

many a good independent garage have become skilled at using their "copy" of dealer tools, finding them is the difficult bit - its much more common on the cars sadly

said copies go around dodgy website to download for free or ripping you off on ebay - but they tend to come with extras, and then you need the expensive multiplexer to connect to the bike - the aftermarket affordable tools tend to work on one comms session at a time (which cheap adapters cope with, such as turning on the heated grip symbol in the clutser), whereas dealer stuff for many years std practice is for their tools to operate on multiple different messaging strings across multiple networks all at once (hence the need for that multiplexer) - kind of saying to one module I'm doing this, stay awake or it will go wrong, or, if you say yes, and that module says yes I'm going blast this weird data across all networks, try not to self destruct your boot loader becasue this is not going to make any sense - for complex coding or programming its essential they're all communicating at the same time or the exact split second delay the manu determined or things go nasty

the world of cheap adapters is nearly able to do the posh multiplexing bit these days - but linking copies and aftermarket stuff till it behaves is a black art few like to talk about