auto reset applies to trip 2 only on my bike and even then, will only auto reset after 7hrs/overnight. My mpg data can randomly reset several times in one day.
If you read the thread through, all is clear
TFT Average Fuel Consumption Problem
- Thread starter MIKE R
- Start date
If you read the thread through, all is clear
I could write everything down om a piece of paper at every petrol stop and do the sume when I get home. Much rather just press a button to get the results.
It's a function on the TFT and, like all other functions on the bike, should work
Mike
Hi, it’s been a long time since I posted on this thread and I thought I should conclude my query with a final update.
1. My dealer requested I reset the TFT to factory defaults - this did nothing and the issue persisted. More lately, it started doing really weird stuff and even transferred data from trip 1 to Trip 2 and not just zeroing c the mpg figures.
2. The dealer suggested they would try reinstalling the bike’s firmware and so had the bike for a whole day back in May - problem sorted. . . . I’ve not looked back.
This led me to wonder why I had the issue and whether or not it was due to me and something I had done.
When I took delivery of the bike, I installed an Optimate/Accumate pigtail on the battery so that I could charge directly since
a. I didn’t want to bother disconnecting the battery and
b. I didn’t own a canbus-compatible charger. My Accumate is from 2005 and so rather old.
The manual specifically warns against charging the battery in this way without disconnecting it as it can “damage the electronics”. I have always done it this way and so naturally thought it was BMW BS.
I researched it pretty carefully and it isn’t BS and indeed, the risk is very real and especially with canbus BMWs.
Anyway - I’m not prepared to take the risk and so now charge via the DIN socket using a new BMW canbus charger. . . . No issues in 4K miles and 6 months.
.
1. My dealer requested I reset the TFT to factory defaults - this did nothing and the issue persisted. More lately, it started doing really weird stuff and even transferred data from trip 1 to Trip 2 and not just zeroing c the mpg figures.
2. The dealer suggested they would try reinstalling the bike’s firmware and so had the bike for a whole day back in May - problem sorted. . . . I’ve not looked back.
This led me to wonder why I had the issue and whether or not it was due to me and something I had done.
When I took delivery of the bike, I installed an Optimate/Accumate pigtail on the battery so that I could charge directly since
a. I didn’t want to bother disconnecting the battery and
b. I didn’t own a canbus-compatible charger. My Accumate is from 2005 and so rather old.
The manual specifically warns against charging the battery in this way without disconnecting it as it can “damage the electronics”. I have always done it this way and so naturally thought it was BMW BS.
I researched it pretty carefully and it isn’t BS and indeed, the risk is very real and especially with canbus BMWs.
Anyway - I’m not prepared to take the risk and so now charge via the DIN socket using a new BMW canbus charger. . . . No issues in 4K miles and 6 months.
.
Interesting to know and thanks for the update. It could have been your charger, as I've used my Optimate 4 via the flying SAE lead on 3 GS' and now my 1250RS since 2016 without any issues at all, but this might serve as a warning for anyone thinking of using an older charger, rather than getting an up to date version
I have a very old optimate which must be around 25 + years old, had it fitted to my 2018 1200gs directly to the battery and never had any problems.
But I don’t leave it continuously switched on for months at a time I only use it every couple of weeks & before I use it I flatten the battery untill the low voltage warning pops up on the TFT ,
But I don’t leave it continuously switched on for months at a time I only use it every couple of weeks & before I use it I flatten the battery untill the low voltage warning pops up on the TFT ,
Hi Clutchspring . . . my Accumate was purchased new around 2005 and is a maintainer and supposedly can be left unattended. I only ever leave it on for 2-3 days and thereafter check the voltage every month when the bike is sorned etc. I have used it like this on my 2008 Tiger, 2019 Speed Triple RS and 2015 S1000RR but none of those bikes contained the warning in the manual about disconnecting the battery before charging. Your GS may not be canbus but I suspect it most likely is. I can't be sure this is what corrupted my firmware but I suspect there is a good chance. Also, reading various posts on this and other forums, I am not alone with the corruption/random mpg resets etc and so there is a commonality somewhere. It is easier to me to believe that the issue is caused by the owners rather than random issues with the initial install, not least because I suspect the firmware would be checked for integrity at installation. The battery charging is a definite candidate and particularly, given the highly specific warning in the owners manual.I have a very old optimate which must be around 25 + years old, had it fitted to my 2018 1200gs directly to the battery and never had any problems.
But I don’t leave it continuously switched on for months at a time I only use it every couple of weeks & before I use it I flatten the battery untill the low voltage warning pops up on the TFT ,
When I investigated, I found out that connecting direct to the battery still means the canbus is connected and the damage can result from voltage spikes which are created by some charges attempting to "recover" a seriously discharged or sulphated battery. Another cause can be if the owner forgets the charger is attached and attempts to start the bike with the charger still attached.
Some modern chargers will protect against both these scenarios but the only way to be completely sure is to remove/disconnect the battery when charging or use a canbus-compatible charger, connected via the DIN socket. I wanted to remove all doubt and so went this route . . . the other advantage is that when charged via the DIN socket, the canbus system also serves to protect the bike and will "insulate" the electronics against voltage spikes caused by either of the above situations and likewise, a compatible charger will do the same and so double protection.
Who knows . . . maybe tomorrow I will go for a ride and the whole thing will turn mammaries up once again but so far . . . so good!!
The main purpose of posting was for those who rather naively think that connecting via a pigtail is perfectly safe because the bike is turned off and with the charger connected direct to the battery, the bike's wiring/bus etc is in no way implicated . . . . sadly, this is not the case and I would advise caution
Colin_S
Registered user
I had, and still have the same issue. I'm quietly confident that the issue started after a firmware update when the bike was relatively new, probably at it's running in or first service (2018 bike). I did call and log the fault but covid came and cranked getting the bike in for a service and it never got looked at again and I just live with it, along with having to re-pair my headset on a less regular basis.Hi, it’s been a long time since I posted on this thread and I thought I should conclude my query with a final update.
1. My dealer requested I reset the TFT to factory defaults - this did nothing and the issue persisted. More lately, it started doing really weird stuff and even transferred data from trip 1 to Trip 2 and not just zeroing c the mpg figures.
2. The dealer suggested they would try reinstalling the bike’s firmware and so had the bike for a whole day back in May - problem sorted. . . . I’ve not looked back.
This led me to wonder why I had the issue and whether or not it was due to me and something I had done.
When I took delivery of the bike, I installed an Optimate/Accumate pigtail on the battery so that I could charge directly since
a. I didn’t want to bother disconnecting the battery and
b. I didn’t own a canbus-compatible charger. My Accumate is from 2005 and so rather old.
The manual specifically warns against charging the battery in this way without disconnecting it as it can “damage the electronics”. I have always done it this way and so naturally thought it was BMW BS.
I researched it pretty carefully and it isn’t BS and indeed, the risk is very real and especially with canbus BMWs.
Anyway - I’m not prepared to take the risk and so now charge via the DIN socket using a new BMW canbus charger. . . . No issues in 4K miles and 6 months.
.
Regarding your worries about charging your battery, I never needed to do this as my bike was my daily commute so I can pretty much guarantee that adding a charger was not what caused this issue. It most definitely wasn't in my case.
Thanks for your comments.
I thought that reinstalling the firmware on my bike had solved the issue but it has reset the mpg on Trip 2 on one occasion and later the same day, when I filled up with fuel and reset Trip 1, it also reset Trip 2. Prior to reinstalling the bike's firmware, it was playing games like this almost daily but this has only happened the once as of now. I will be keeping a close eye on it. I am of the opinion the software on the bike is glitchy and buggy . . . either that, or the hardware is of poor quality. I suspect it's flaky, unstable software. I won't be taking it back to the dealers though - if it keeps happening, then much like you, I will learn to live with it.
As you suggest . . . does reduce the chances of it being anything to do with the charging method, although I would still be wary of charging direct to the battery whilst connected - no point inviting even more grief!!
