Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Richard230]

Today I managed to update my firmware and everything seemed to work well.  After the update installed the lights turned off, but the instrument panel kept flashing until I cycled the ignition switch.  My cell phone said that there was an error during the download as the system "timed out", but that didn't affect the operation. My app now says that my bike's firmware is up to date. The only big change that I have noticed so far is that there was a 50 mile jump in the estimated range upon riding off with a full charge and traveling for a few miles at 25 mph.  The range estimator said that I had 224 miles to empty, which dropped to 140 miles once I hit the freeway and started traveling at 65 mph. I arrived home after traveling 38 miles and the projected range was still 100 miles. So all is good - so far.    

[Richard230]

The updated BMS firmware seems to have resulted in a slight improvement, too.  At least for me.  After a full charge my app is showing a battery capacity of 15.312 kWh, compared with 15.138, previously.  The app now shows 132 AH capacity and voltage remains at 116 volts. Also when I pulled my charger cord the charging light and display went blank, instead of staying on continuously as it had done before. So that is a real plus for me, if it continues to do so.

[Richard230]

Since I have a theory about everything, I'll relay my theory why new downloads don't always work well with the older (say pre-2017) model Zeros.  My guess is that the Zero engineers are creating revised firmware to help improve their new models, such as the 2018 bikes, and perhaps those revisions play poorly with the older model year bikes' BMS and MMB firmware and that is what is causing difficulties for some owners. 

[originalspacerob]

Hello Richard. Great to hear you were able to update the firmware. My 2017 still wont let me update as of yet. It says I need to bring it to the dealer. Maybe after the MBB is updated again it will allow the app to update the bike. When I connected the app yesterday it says I’m on MBB rev 19 and needs to be updated.


Sent from my iPhone using Tapatalk

[SebfromBE]

Hi,

It has been the same with my S 2017. I first had to bring it to the dealer to get the latest revision of the MBB (22). Then from 22 to 23 I could do it myself. There is likely a critical revision from where you can start your own update. Or maybe critical/sensitive update they still prefer to do them at the dealer... Who knows :-)

[originalspacerob]

That is some great info. Ill be giving the dealer a call to schedule and update in the next week. Would have been nice if Zero let us know that. Even the dealer didn’t know anything when I had it there for the 600 mile check.


Sent from my iPhone using Tapatalk

[hubert]

Since I have a theory about everything, ... perhaps those revisions play poorly with the older model year bikes' BMW

You'r right, a Zero firmware may not be the best thing to load into an old BMW bike! 

[Richard230]

Since I have a theory about everything, ... perhaps those revisions play poorly with the older model year bikes' BMW

You'r right, a Zero firmware may not be the best thing to load into an old BMW bike! 

Good catch!     The BMW is now a BMS.   

[BrianTRice@gmail.com]

For what it's worth, I sifted through Zero's Android app and learned that the signon for checking for firmware updates and getting new firmware is authenticated over HTTPS mainly by the user's Google account email address, suggesting that their customer database must be whitelisting those with 2017+ model year bikes for the service.

This may or may not explain certain firmware check failures on Android - your email there might need to match Zero's email on file for you.