Issue resetting miles to next service on R1250RT

[BMWDetroit]

I had problems resetting the "miles to service" on a 2019 R1250RT. I would set the miles to 90000 but then it would only change it to around 8500. Tried several times, reset device, etc. and there is no pattern to the problem. The best I could do is change it to 80000 miles and it would change it to around 39000 on the bike. Date changes fine to 2030. I have changed both a 2016 & 2017 R1200RT to 90000 without any problems. Anyone else experience this or have any input? GS-911 system version is 0.254 - 0.184. Thanks, Mark

[WayneC]

Mark

That sounds odd, I assume you were using the browser interface not the PC App ?

I would suggest logging a support ticket with Hexcode, https://www.hexcode.co.za/contact-us-1

[BMWDetroit]

Thanks Wayne. I did a quick look at the site and didn't see a place to log a ticket so thanks for the link. And, yes, I should have mentioned that I am using the WIFI version with cloud service functionality.

[Wilco]

You're getting overflow errors, which is why the results look all over the place.

The specified distance is internally converted to kilometres, and the difference to the odo is calculated. This is then communicated to the bike via a two-byte value.
Two bytes can go up to (roughly) 64 000 if it's unsigned or 32 000 if it's signed. I'd be surprised if it were signed.

Long and the short is that you cannot set your next service more than 64 000 km (40 000 miles) into the future.
The limit is on the bike, not GS911.

I'll log a dev ticket to catch the overflow and set to max.

[BMWDetroit]

Thanks Wilco. This makes sense even though my programming days are way behind me. So I could set the max to 40721 miles which converts to 65535 km which converts to 16 bits (two bytes) @ 1 (Hex FFFF). Correct?

A max limit message / option with available km / mi to max would be helpful.

I checked the 2016 RT that I set to 90k miles but the odometer was already over 50k miles so the "distance to next service" was below the ~40k miles max.

Has this overflow issue come up before? I am new here so maybe I missed an earlier post. To me it's easier to set the limits way out and just track service manually instead of constantly resetting the service reminder.

Thanks again.

[Wilco]

Your figures are correct, yes.

Feature freeze for the next release is already in place, so the max limit message will be in the following release.