ElectricMotorcycleForum.com
Makes And Models => Zero Motorcycles Forum | 2013+ => Topic started by: PhreaK on October 04, 2015, 05:26:55 PM
-
In lieu of a notification service from Zero, I thought I'd kick off a thread to keep track of current firmware releases so we can all keep an idea of when it might be a good time to head on into a dealer. If anyone's feeling kind, run your MBB logs through this (https://github.com/KimBurgess/zero-log-parser) and let us know what you're running. As time goes on, I'll do my best to keep this top post edited with the latest known releases.
Kicking off with what I have from the logs people had sent me figuring out the log file format
2013
MBB rev 1 - firmware v67
2014
MBB rev 1 - firmware v44
BMS rev 1 - firmware v43
2015
MBB rev 3 - firmware v25
-
I thought the bms also have there own version number as well?
-
Serial number 2015_mbb_ca1a29_00974
VIN 538SM7Z39FCG05xxx
Firmware rev. 25
Board rev. 3
Brought it home yesterday afternoon in Belgium.
-
2014 SR
MBB
Board Revision 1
Firmware Revision 44
BMS
Board Revision 1
Firmware Revision 43
-
I thought the bms also have there own version number as well?
I believe so - I haven't gotten into the BMS log structure yet. There's a lot of similarities with the MBB logs, but the static addresses are different. If anyone knows where to look, or has an data reaper extract along with the original that I can line up, would love to get my hands on it.
-
thanks for the updated code for python3. Here's my output:
2013 DS
Firmware rev. 62
Board rev. 1
Model b'DS'
looks like there may be newer firmware for my bike "65"? I suppose this requires a trip to the dealer?
-
Just got my 2013 DS firmware updated to:
Serial number 2013_mbb_ca1a29_00572
Firmware rev. 67
Board rev. 1
-
I just had a closer look at the log file (post update) and noticed a few weird lines where the date, time, and data (Voltage, SOC, RPM, ...) are wrong. I ran the script twice just in case and got the same result.
Have a look at lines 152, 155, and 207. Any idea where these come from? I'll try to re-import the log from the bike later today...
-
Please forgive my ignorance but why do these bikes need updating? What is there to be improved upon? Plug it in charge it unplug it ride off. Computers need updates for viruses and new programs that might get used on it but nothing about the bikes operation changes.
-
Please forgive my ignorance but why do these bikes need updating? What is there to be improved upon? Plug it in charge it unplug it ride off. Computers need updates for viruses and new programs that might get used on it but nothing about the bikes operation changes.
My very early 2014 S hasn't had a firmware update since it was built and it still works just fine. I haven't had a single problem with the bike since the power tank was replaced a couple of weeks after my initial purchase. So I would have to agree. Don't try to fix something that is working very well - especially when it is controlled by a computer. You may live to regret it. :o
-
@patrick nice catch! Can you shoot me the original bin file, I'll take a look to see if there's something odd going on.
@NEW2elec although the outwards facing operation may not change, you'll find that updates will occur to address items which may be causing excess strain on various system components, address edge cases that weren't identified during initial development and other scenarios that have been identified once the product experiences heavy use under 'real-world' conditions. People will generally fall into two polar opposite camps when it comes to then - update all the time, or don't update unless it's broken. Both have their merits. Personally, it would be awesome to see Zero publish a changelog with all firmware releases so that you can make an informed decision about which may you'd like to go.
-
Thanks Phreak so basically Zero is reoptimizing their preset parameters to what the real world wear and tear repairs show. Fair enough.