Print

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

[gt13013]

I downloaded the logs through the Zero Android mobile app over bluetooth.
Do you use some other method?

Firmware rev.      32
Board rev.         2980
Model              FX
Initial date       Oct  5 2020 14:00:33

Also the intial date is rather strange, that was the date it went for a warranty claim and stayed there for 4 months

I download the logs the same way as you.

Thanks for sending me your MBB log. I have decoded it. It appears that

1) Concerning the log of your recent bike,
https://zero-motorcycle-community.github.io/browser-parse/zero-log-parser.html does not recognize Serial number, VIN, Firmware rev., Board rev.
http://home.hasslers.net/zerologparser/log_parser.php recognizes Serial number, VIN, Firmware rev., Board rev.

2) The "Initial date" that appears in the log seems to be the date of the firmware, since when I decode the logs of my bike I get
Before the firmware update :
Serial number      2016_mbb_ca1a29_02158
VIN                538XXAZA1GCJ06xxx
Firmware rev.      47
Board rev.         3
Model              FXS
Initial date       Apr 11 2016 13:57:48

After the firmware update:
Serial number      2016_mbb_ca1a29_02158
VIN                538XXAZA1GCJ06xxx
Firmware rev.      56
Board rev.         3
Model              FXS
Initial date       Sep 10 2019 10:56:47

3) Indeed, there is a difference between your long brick FXS and mine with 2 removable battery packs.
For the long brick, the MBB log shows that there is only one contactor, whereas the model with 2 removable batteries has duplicated BMS and contactors (they are inside each battery pack)

4) You should also keep an eye on the battery log (not only the MBB log). It gives more detailed information on the battery pack

5) If your model is a FXS, it is strange that the log reports a FX model. It should be checked by comparing to logs from bikes similar to yours. But perhaps the dealer replaced your firmware by another that is not exactly aimed for your bike. Many years ago, I tried to make a thread in order to have some examples of bikes and their firmware, but it had no success...

[Lj66]

Regarding the site https://zero-motorcycle-community.github.io/browser-parse/zero-log-parser.html, that was last updated on may 8th 2017 which is why it does not read recent logs which have had new firmware, the offsets for data are at the wrong positions, its still usefull for older unchanged bikes though. Here is some c code i cobbled together from the info in the python script behind the site http://home.hasslers.net/zerologparser/log_parser.php. If you cut and paste it into a C compiler it will produce a cmd line utility that attempts to give out log file header info.