ElectricMotorcycleForum.com
Makes And Models => Zero Motorcycles Forum | 2013+ => Topic started by: jnef on August 28, 2016, 11:02:02 AM
-
Has anyone seen this? I'm at about 1500-ish miles on my 2016 SR. Tonight when I was plugging it in, I noticed (panicked) the odometer is a little off, by most of a Megamile. (It reads 899,157). Several of the app values are way off too. Haven't done anything other than use the built in charger and quiq; and the official phone app to look at things.
Any ideas? Any way to force a reboot other than turning off the key?
(http://uploads.tapatalk-cdn.com/20160828/ceb3167e89f1a60b444aad2f80574bf7.jpg)(http://uploads.tapatalk-cdn.com/20160828/e23d2f12e33dc654aba0613371842574.jpg)
Sent from my iPhone using Tapatalk
-
Cool...you saved over $118 million!! haha
Try resetting the BMS on the front of the bike/battery. Instructions here:
http://zeromanual.com/index.php/Unofficial_Service_Manual#Battery_Management_System_.28BMS.29 (http://zeromanual.com/index.php/Unofficial_Service_Manual#Battery_Management_System_.28BMS.29)
-
Good idea, just tried it, but it didn't work.
Tried both hard and soft restarts on the BMS. Same odometer reading.
BMS lights look normal -- when off, rightmost light single flashing; when on, just the red light (since it is low on charge right now.)
-
Try pulling all the fuses under the seat and then put them back in after a minute.
Sent from my Nexus 6P using Tapatalk
-
Thanks for the further ideas, but... Nope... Still the same thing. It doesn't appear that anything relevant goes through that fusebox though. (ABS, accessory, just the backlight for the odometer)
Starting to feel like this is going to be bad news.
-
Your SR has a secret new battery chemistry, or so it seems, that will enable you to do that kind of mileage in a short period?
But serously, keep us posted when visiting the dealer. Good luck!
-
Downloaded the log file... Here is the gem:
07909 08/27/2016 21:31:08 b'Dash ODO 2147483648km > MBB ODO 2894km. Setting MBB to 2147483648km'
No amount of turning it off/on is probably going to fix that.
Turns out that 2147483648 is a number that has bitten me before, more easily identified as 2^31... Someone responsible for programming the MBB might need to learn about handling signed/unsigned integers and error flags correctly. :P My guess is that the MBB code here looks to align itself with the ODO regularly, but in this case, the ODO didn't know what was up, or a communication failure happened, etc, and it got a -1, but instead of handling it as -1 or an error flag, handled it as a positive number, and then later rewrote it back to the ODO...
I guess I could try riding it forward for a mile and see if it goes to zero, or if it starts counting backwards. Regardless, I highly doubt it will go back to the right number without help of someone with the secret commands.
-
Wow, crazy bug!
Please keep up posted on how it was resolved.
-
Good catch on the #! Probably something overflowed - that # is the biggest integer with a sign that a 32 bit binary can express. So the dash must be a 32 bit device that got confused or not initialized properly... or maybe Zero is missing a 0 somewhere ;)
https://en.wikipedia.org/wiki/2147483647_(number)#In_computing
-
In case this is later helpful for anyone else... Dealer isn't open until tomorrow.
Rode it today a little bit; reset trip 2 as it was a crazy large number too. ODO doesn't change when moving, so it appears to understand it is at its max. Trip 2 counts up normally. Trip 1 was meaningless numbers, and doesn't reset automatically, but now at least seems to count up normally. Trip wh/mi numbers are 0 (since mi is infinitely large)... Poor thing is confused; I'm hoping that they can just clear and reset it.
Also very interesting- if I change it to km, the ODO shows 0, and the trip numbers get smaller rather than larger...
Sent from my iPhone using Tapatalk
-
You bike is possessed! Forget the dealer...take it to an exorcist!!
Haha
-
I think if you get this issue put up to the proper people at Zero, they will jump on fixing it ASAP. Incorrect Odometer readings are a big oopsie in the eyes of the federal government.
-
They are shipping out a new dash unit. Apparently they have to replace the whole thing.
Sent from my iPhone using Tapatalk
-
Update: Got the bike back yesterday. They replaced the dash unit with a new one. The MBB had remembered the incorrect info from the ODO. They upgraded the MBB firmware to 49; and performed a full reset to defaults. Lastly, they had to get on the phone with Zero for the secret commands to set the ODO to the right number. Everything looks good again now. Lifetime Wh/mi values are now significantly low (it was always about 20% low anyway), but the trip wh/mi and range works again. Very happy with Zero and the dealer (Rocket in San Diego).
-
Update: Got the bike back yesterday. They replaced the dash unit with a new one. The MBB had remembered the incorrect info from the ODO. They upgraded the MBB firmware to 49; and performed a full reset to defaults. Lastly, they had to get on the phone with Zero for the secret commands to set the ODO to the right number. Everything looks good again now. Lifetime Wh/mi values are now significantly low (it was always about 20% low anyway), but the trip wh/mi and range works again. Very happy with Zero and the dealer (Rocket in San Diego).
Its awesome that they can reset the ODO to the proper miles... most bikes cant do that.
-
I have a similar problem but not as serious. I set the sprocket numbers to the actual values (don't ask how ;)) and this happened. Can I undo? Maybe not. Mileage went from 2075 to 9588. Oops..
spfront - Sprocket Teeth Front : 25
sprear - Sprocket Teeth Rear : 132
rwhcirc - Rear Wheel Circum : 2038 mm
spfront was set to 11
INFO: Dash ODO 3340km > MBB ODO 1470km. Setting MBB to 3340km
spfront - Sprocket Teeth Front : 11
sprear - Sprocket Teeth Rear : 132
rwhcirc - Rear Wheel Circum : 2038 mm
sprear was set to 65
spfront - Sprocket Teeth Front : 11
sprear - Sprocket Teeth Rear : 65
rwhcirc - Rear Wheel Circum : 2038 mm
spfront was set to 25
sprear was set to 132
INFO: Dash ODO 15427km > MBB ODO 7597km. Setting MBB to 15427km
spfront - Sprocket Teeth Front : 25
sprear - Sprocket Teeth Rear : 132
rwhcirc - Rear Wheel Circum : 2038 mm
-
Since I am trying the 11/65T ratio chain, how off will the readings be, if I don't tweak the parameters?
And with this in mind, how do you tweak the numbers to the correct gear ratio?
Sent from my XT1585 using Tapatalk
-
About 2 months ago had just ridden to Los Angeles and back to Santa Cruz in the same 24 hour period and was at my last charge stop using 4 Diginow superchargers from dual J plugs and saw my odometer and was very confused. I can't remember the last time I really looked at the mileage but I thought it was about 34,000 last I remembered not 735,000. But I hadn't slept in 2 days and was trying to think if I fell asleep and just logged a bunch of miles. The math potential of that quickly hit even in my sleep deprived state and realized there must be a glitch somewhere. I went by Zero the next day and Aaron in Customer Service reset it to 35k for me (34k plus the trip to LA and back) and its been fine ever since. But glad to know you can go into the logs and see exactly the line that the dash can over ride the MBB mileage. Seems like it shouldn't be able to do that without a confirmation from the user or a dealer. Can anyone see a situation where that automatic function would be needed? If there is a MBB replacement you can manually confirm that the dash can set the mileage to the MBB. Oh well, if there are only 2 known cases in a few million miles or more of Zero owner mileage it probably is too infrequent to worry about.
edit:
Not sure why the picture is upside down, it wasn't that way when I uploaded it.
-
The stock FX ratio is 132/25 = 5.28. With the Zero chain kit it becomes 65/12 = 5.41. So the odometer is changed by 2.6% from stock. Going to 11T makes the ratio 65/11 = 5.909 which is 11.9% from stock, pretty significant. That's why I wanted to get it right. Maybe there is a sequence of setting changes that fixes it. Off I go to find out, wish me luck. My dealer is more than 100 miles away, so it's a big deal to take it there. But I am due for firmware and timing so I might do that.
-
I can't remember the last time I really looked at the mileage but I thought it was about 34,000 last I remembered not 735,000.
Not sure what that number means, but mine was binary -1 or (2^31), sign ignored, in km, truncated and converted from km to miles became 899157. My logs showed the full number in km, which is where it was clear. It would have been interesting to see the logs on yours when it happened. They couldn't reset the ODO on mine, so they replaced it and then reset the MBB and ODO value. I still have some remnant of that somewhere as my total efficiency isn't computable, but that doesn't bother me.
Sent from my iPhone using Tapatalk
-
I tried to fix it and of course made it worse. I had only two ideas after sleeping on it. First I tried an overall reset to defaults and got "you are not authorized to change it." OK, one other possibility, set the rear sprocket and then the front, the opposite sequence of my first attempt. My reward: INFO: Dash ODO 31328km > MBB ODO 13785km. Setting MBB to 31328km So now it shows 19466 miles while it is was 2075 miles yesterday morning. It is a one way valve, only increases the odometer, it never decreases. I can see motor revs as currently 90834150, 8620021 was the number of revs when I first connected so that has increased by a factor of 10.5 thanks to software madness. The dealer installed the chain kit before delivery so the settings have never been correct, then I changed the front from 12 to 11 and then I tried to fix the settings. Surely many dealers have fallen down this rabbit hole too. :(
-
I'll try to write this up for the wiki. jnef and Keith, please let me know any details that jumped out later now that this all settled down, as far as troubleshooting.
-
I'll try to write this up for the wiki. jnef and Keith, please let me know any details that jumped out later now that this all settled down, as far as troubleshooting.
Yeah, don't mess with those settings if you aren't a dealer...
Specifically the interaction between the MBB and ODO only allows for increases in the mileage at every step. The MBB code appears to compare it's calculated mileage to the ODO and sets relevant variables in both to the maximum value. Oh and if you manage to roll over a 32bit signed integer or have a badly timed comm error, you'll really be hosed.
Sent from my iPhone using Tapatalk