ElectricMotorcycleForum.com
Makes And Models => Zero Motorcycles Forum | 2013+ => Topic started by: NervEasy on November 13, 2021, 02:32:13 AM
-
It seems V20 for the MBB is out. I do not know if this is also V20 for the BMS…
Does anyone have insight what the release notes are? Any dealer here that can tell us?
I haven’t pressed the update button as I want to wait until someone said the update went successfull with their bike.
Anyway fingers crossed this update brings some much needed fixes! Hopefully not only MY22 stuff?
-
My 2020 SR/S does not yet show any new firmware updates available, and the Zero Motorcycle website still shows V19 as the latest MBB and BMS firmware versions. Where did you get your information regarding V20?
-
Here you go. No BMS changes, so likely no SOC fixes or improvements:
November 10th, 2021
MY20/MY21/MY22 MBB: Rev 20 BMU Rev 20 BMS: Rev 19 SR/F SR/S SR
* Support for 22MY bikes and the new ZF14.4+ and ZF15.6+ batteries
* Support for Cypher III+ features
* Improve self cancelling turn signals to cancel based on bike angle and reduced total distance
* Rename Street Mode to Standard for all FST bikes
* Fix for Remote Data Connectivity when bike is not riding or charging
* Bug fixes for charge target functionality
* Various bug fixes and improvements
-
Thanks Auriga!
What do they mean with BMU?
-
Thanks Auriga!
What do they mean with BMU?
I'm led to believe the new BMS on the new 22MY batteries is called the BMU
-
So there should be a BMS 20 coming soon too hopefully..
-
It also added a new mode called "CANYON" which is a very odd name in my opinion. It seems this was just the default custom mode as when I reloaded my own one it was overwritten. I never saw what the settings were. One firmware addition that I feel would be useful and I can't imagine would be too difficult to implement would be to allow more than one custom mode on the bike.
-
Yeah, also had that. I think it’s the ride mode from a developer they forgot to not include. Being in all caps and such…?
-
I just tried it on my 2020 SR/F but no cigar: after about 25 minutes, out of the 30 it says it will take, the upgrade failed with an error 8 code.
Everything seems back to normal after that but it certainly did not take it on first attempt.
Will try again tomorrow. . .
-
I did the MBB V20 upgrade on my 2020 SR/S this evening with no problems. While the initial screen said it could take up to 45 minutes, it only took 15. This was probably the easiest firmware upgrade I've done since I bought my bike.
-
I just tried it on my 2020 SR/F but no cigar: after about 25 minutes, out of the 30 it says it will take, the upgrade failed with an error 8 code.
Everything seems back to normal after that but it certainly did not take it on first attempt.
Will try again tomorrow. . .
Unexpectedly, had time available to try again this evening and this time it went smooth.
I used my iPad to start the upgrade and this time it went by the book.
Wonder what made the first attempt fail. The bike was parked in the very same spot and absolutely nothing was changed in the configuration or charge level.
-
I also upgraded my 2021 SR/S without issues.
It had been in storage mode for 17 days when I heard about the upgrade, SoC went from 60% to 49% during that time. If it keeps discharging at that rate I'll be screwed when it gets really cold so I can't even charge anymore.
Anyway, so I plugged it in and the bike started to charge at about 5.5 kW but tapered down quickly after that. The charge target was set to 60% and at 58% it charged at only 1 kW. On a hunch, I increased the charge target to 95 and voila: it charged at 6 kW. I stopped at 60% to put the bike back into storage mode, but I don't understand why it can't just charge to 60% at full power and then stop? That's what my car would do. Before the upgrade it would charge to about 63%, now it takes forever to reach the target because it unnecessarily reduces the charging power? Great job, Zero...
It's too cold for me to further test the new firmware, but so far I'm not impressed.
-
You can plug the charger in while in storage mode, but it won't charge until SOC drops to 30, then it will charge to 60 and repeat.
-
I guess I could do that. It's just that I'm a bit frustrated with Zero. The manual states that the motorcycle will discharge at an extremely low rate (right, 11% in 17 days is "extremely low"?), yet it's losing energy at a rate that I would not expect in storage mode to put it mildly.
They also tell me to disconnect the charger and recharge when the SoC falls below 30%. Great idea, but temperatures routinely fall way below 0 °C in winter where I live which makes it impossible to charge the battery, at least according to the manual. Maybe they didn't get that part right either and I can recharge below 0 °C. I guess I'll have to see.
Right now it's above 0 °C and I'm thinking I should just charge the bike to 80% and let it sit there. After 30 days of inactivity it should automatically enter storage mode and discharge to 60%. At least that will buy me some more time.
I have a feeling I'll have to put an electric heater in my garage and cover the bike so the heat stays where I need it.
Just for comparison purposes: I had my Model 3 sitting in the garage for two weeks not long ago and lost only 1%. Pretty sure Zero could do a better job if they wanted to.
I like riding the bike, but there are so many small things I don't like about it. If Energica had a dealer in Ontario I'd switch in a heartbeat.
-
IIRC the Aerostich factory famously had a Zero FX and published their story about it "Zero below Zero"; was it a warming pad they used on the battery? Could be an option is to put a warming pad on the battery and sew up a neoprene cover for when you want to charge it in cold temps.
-
Before the upgrade it would charge to about 63%, now it takes forever to reach the target because it unnecessarily reduces the charging power? Great job, Zero...
It's too cold for me to further test the new firmware, but so far I'm not impressed.
Probably not unnecessary but i think the point where it starts to taper off is when it starts to balance the cells. Same thing happens at 95% (when charge target disabled) or so. Going from 95% -> 100% before the bike fully shuts off, generally takes about 15-20 mins. Hence there are 2 published charging numbers from Zero.
-
I updated my bike on saturday. Only worked after using the App, trying from the prompt at startup failed.
* Fix for Remote Data Connectivity when bike is not riding or charging
Since then the SoC was reported correctly from the online API.
* Improve self cancelling turn signals to cancel based on bike angle and reduced total distance
They cancel now within ~100 meters. Although a bit hit or miss if they detect the turn.
On a ride today(overcast clouds) I also noticed the display constantly switching between light and darkmode. Up to only ~2 Seconds between switching. Looked like the hysteresis wasn't working properly.
And a small thing: You can now choose to display RPM in one of the 4 dashboards.
-
Uram,
Interesting. I contacted Zero Customer Service/Tech Support today and was told the turn signals now cancel after 30 seconds of forward motion. No mention was made of lean angle. I've upgraded to V20 but cannot check it out yet due to weather here in the Northeast.
-
On a ride today(overcast clouds) I also noticed the display constantly switching between light and darkmode. Up to only ~2 Seconds between switching. Looked like the hysteresis wasn't working properly.
And a small thing: You can now choose to display RPM in one of the 4 dashboards.
Displaying the motor RPM was already possible with V19.
I originally had the same problem with light and dark mode switching back and forth before I permanently set it to light mode. This is a customizable option.
-
Just so you know, I upgraded FW to v20 yesterday and now my Android app is working again, the remote connection has been restored and I can see my SOC on the app again - plus ride capture etc is working. Thanks Zero :)
-
On a ride today(overcast clouds) I also noticed the display constantly switching between light and darkmode. Up to only ~2 Seconds between switching. Looked like the hysteresis wasn't working properly.
And a small thing: You can now choose to display RPM in one of the 4 dashboards.
Displaying the motor RPM was already possible with V19.
I originally had the same problem with light and dark mode switching back and forth before I permanently set it to light mode. This is a customizable option.
My 2012 Zero ZF9 had a button that you could press to display the motor rpms down to a single digit. It was pretty useless as the numbers changed faster than I could read them. BTW, you could also press the button to switch between Metric and English speed and distance displays.
-
Did V20 upgrade yesterday. All went fine and said it was completed successfully but turning it back on had an error code 8 upgrade failure. Cleared the code and checked current version of software and it is indeed V20. Not sure what happened but a little weird.
-
V20 went reasonably well for me. Did it via the app on iPhone. Upgrade took about 15 minutes, then the bike restarted and the app was stuck on a screen saying something like waiting for motorcycle. I left it like that for maybe 10 minutes before giving up and force closing the app and relaunching. Confirmed I'm on V20 and the app said no more updates available.
-
V20 went reasonably well for me. Did it via the app on iPhone. Upgrade took about 15 minutes, then the bike restarted and the app was stuck on a screen saying something like waiting for motorcycle. I left it like that for maybe 10 minutes before giving up and force closing the app and relaunching. Confirmed I'm on V20 and the app said no more updates available.
That is a similar response to a firmware update that I would have when updating my 2018 S since I bought it. However, the last update a few months ago did not exhibit that response. It downloaded quickly and didn't exhibit any weirdness. :) I wonder why? ??? Maybe things will improve once the need for regular updates fades.
-
This firmware upgrade has me INFURIATED.
I almost got rubbed out today merging on a high speed turnpike I use.
I went to pass to get off at an exit and there was no extra speed to be had. I was stuck at around 106MPH and barely made it past the car I was merging in front of, to the spot where I intended to be. I almost had to run off the road because I couldn't merge.
I looked down. What is wrong! I noticed the mode was no longer "Commute", my created mode, but "CANYON".
This mode had limited my speed to 108MPH. Surprise!!!!!!
I then attempted to re-enter my original mode. No matter what I do, it always defaults or resets to a maximum speed of 108MPH, which means in practice 105-106MPH.
I can enter a mode or update a created mode to any speed, but when I check again with the app it has set the maximum speed back to 108.
Maddening.
They better fix this fast. I'm very angry. Almost getting killed will do that to you.
"Latest and greatest". MY ASS
You almost killed me dudes. You changed my bike and didnt tell me. I almost got fucking killed.
-
So, er, doing 108mph on your morning commute doesn't ring any alarm bells either then...?
Cas :)
-
I don't see any problem with doing 108mph. However, having to do 108mph so you can cut in front of someone to just about make the exit? Your riding is what will perhaps get you or someone else killed.
-
I did some experiments last night and this morning. Any parameters I change in the custom mode will persist; display color, torque, traction control, regen, everything... but the max speed always reverts to 108mph. California is not open yet, I will call for help in a couple hours.
Don't be so quick to judge how fast I should be riding. I've been commuting on two wheels for almost 40 years and I'm still here.
On the portion of my commute I was commenting on, its a wide open highway where the average speed of everyone ranges from around 85 to 100 mph. Mom wagons with cheerios on the floor are sailing along faster than many people ever go. And in this part of that highway, the road has been straight and open with clear visibility for almost the last mile, so speeds pick up even more. That's the way it is. Such places do exist in the United States. Its not out of line at all to need to speed up to , say, an increase of 20mph vs the traffic just to get a spot to exit, and suddenly with no warning I was unable to do it.
On a road like this, having my speed limited to 106 is a liability. It limits my mobility to get out of people's way as well as to get where I want to go.
-
I was kind of hoping that Commuter's comment was a joke about being limited to 108 mph (says someone who's Zero is limited to 98 mph and never goes faster than 75). But I guess he is serious. In most U.S. states getting stopped by the cops doing over 100 mph will cause your bike to be towed and you needing a taxi ride home and also perhaps having your license suspended. While my time is valuable (at least to me) I don't think it is worth the risk to ride that fast in commute traffic.
Good luck with Zero. I am not sure how much sympathy you will get from them if you tell the story the way you did. You might want to tone it down a bit and just stick to questions regarding the parameters of the "canyon" programming and how to bypass it.
-
In other news, my SR/F seems to refuse to upgrade the firmware (over cellular)... Error code 8.
And I still can't pair the Pixel 4a with it. I've tried turning off every other wireless feature on the device too to minimise interference - WiFi, NFC, location, Nearby Share, Personal Safety, etc. - but no joy, it just won't pair. The bug's clearly in the shitty Zero Android app though because my Toyota, Alexa, and Interphone Avant all connect just fine.
Cas :)
-
I did some experiments last night and this morning. Any parameters I change in the custom mode will persist; display color, torque, traction control, regen, everything... but the max speed always reverts to 108mph. California is not open yet, I will call for help in a couple hours.
Is it possible that your battery/motor was getting too warm? (I realize this isn't a very warm time of year even in FL) Or maybe Zero added some temperature protection parameters that previously didn't exist?
You certainly should report it to Zero. Could be an error in the software that they don't know about or didn't intend.
-
@Cas,
I had exactly the same problem. I received error code 8 (over cellular and initiated from the dashboard). Pairing a Pixel 4a also does not work for me. No idea if this is a problem with the Android version (12) or with the HW. I can connect an older Samsung S7. But even if you connect the Android phone successfully: You will not see the Firmware Update Menu. This should be in "Performance" between "Dashboard Settings" and "Motorcycle Logs". Neither on my Pixel 4 a (Android 10, App V2.2.5 (1191)) nor on the Samsung S7 (Android 8, same App Version) I can see this menu.
Luckily, I also have an old iPad. The iOS Version shows the "Firmware Update" menu and the update works great and flawless.
@2020_SRS_Commuter, I also got the CANYON profile. My own profile was no longer available. But I was able to create a new profile with my old settings (speed limit to 120mph). I than have set this new profile as current. CANYON was than gone. CANYON was also not visible in "Inactive Custom Modes". It was just gone. I just double-checked my current profile. It still shows speed limit 120mph.
Update: I just double checked and compared with Sport mode. Sport mode shows max speed 127 mph. I think this translates to 200 km/h, the advertised max speed in Europe. In my custom mode I can't go beyond 120 mph - and I also find it strange that it shows the max speed in mph also I have set all units to metric. This would indeed reduce my max speed from 200 kmh to 193 kmh. No big deal, but still.... I live in Germany where it is legal to drive fast.
Thomas
-
Update on my install...
I updated to the most recent firmware as pushed out to the bike and app. After it was complete the ride modes have changed names and can not add custom modes at all. The one custom mode I had was renamed to canyon and that mode if you try and change anything on it the app crashes. If you try to add a mode it crashes. Very frustrating considering there is no other way to alter the ride modes as I was able to before. I finally had a ride mode that I fine tuned how I wanted it and it is gone.
Also at 100% SOC the range only shows 75 miles . This is at least 30 miles less than I normally would get from a full charge.
-
Further distaster... by fiddling with developer settings in the Pixel 4a I managed to get it to talk to the bike and pair properly and not drop the connection! The firmware menu appeared in the app! So I set about updating firmware. It did the first bit (agonisingly slowly), it got to 100% on the first bar, then the bike... switched itself off. App said "Waiting for motorcycle". Waited a good long time, gave up, keyed bike off and on again. "Street" mode, which I left it in, is now "STANDARD". Bluetooth now no longer works again. Gahhh. I have no idea what else it has buggered up.
Cas :)
-
Speaking of heat, I was interested to hear that the 2022 SR has two fans to keep it cool. It was unclear to me if they will only operate when the bike is charging or if they also function when the bike is moving. In any case, cooling fans are something that Zero probably should have installed some years ago, especially when some of the professional motorcycle reviewers started complaining about the charging system locking up on hot days after a spirited ride.
-
Update on my install...
I updated to the most recent firmware as pushed out to the bike and app. After it was complete the ride modes have changed names and can not add custom modes at all. The one custom mode I had was renamed to canyon and that mode if you try and change anything on it the app crashes. If you try to add a mode it crashes. Very frustrating considering there is no other way to alter the ride modes as I was able to before. I finally had a ride mode that I fine tuned how I wanted it and it is gone.
Also at 100% SOC the range only shows 75 miles . This is at least 30 miles less than I normally would get from a full charge.
I had the exact same problem. I went to the app settings in my phone and cleared all cache and data. This meant i had to re-login into the App. After this the app did not crash anymore and the app works as expected. Looks like real bad QA on this :-\
Try this out and hopefully this works for you!
Also this update would not affect the SoC/range numbers i think as this is not a BMS update.
-
Update on my install...
I updated to the most recent firmware as pushed out to the bike and app. After it was complete the ride modes have changed names and can not add custom modes at all. The one custom mode I had was renamed to canyon and that mode if you try and change anything on it the app crashes. If you try to add a mode it crashes. Very frustrating considering there is no other way to alter the ride modes as I was able to before. I finally had a ride mode that I fine tuned how I wanted it and it is gone.
Also at 100% SOC the range only shows 75 miles . This is at least 30 miles less than I normally would get from a full charge.
Did this and worked as you describe. Noticed some odd changes to the regular stock modes too.
I had the exact same problem. I went to the app settings in my phone and cleared all cache and data. This meant i had to re-login into the App. After this the app did not crash anymore and the app works as expected. Looks like real bad QA on this :-\
Try this out and hopefully this works for you!
Also this update would not affect the SoC/range numbers i think as this is not a BMSS update.
-
Got my first real ride in after updating to V20. The self cancelling signals worked perfectly for me the whole ride. They'd reliably turn off no more than 10 seconds after completing my turn.
In bad news my remote connection is no longer working, it worked fine in V19 for me. Oh well.
-
Got my first real ride in after updating to V20. The self cancelling signals worked perfectly for me the whole ride. They'd reliably turn off no more than 10 seconds after completing my turn.
In bad news my remote connection is no longer working, it worked fine in V19 for me. Oh well.
Win some lose some...
-
I did some experiments last night and this morning. Any parameters I change in the custom mode will persist; display color, torque, traction control, regen, everything... but the max speed always reverts to 108mph. California is not open yet, I will call for help in a couple hours.
Is it possible that your battery/motor was getting too warm? (I realize this isn't a very warm time of year even in FL) Or maybe Zero added some temperature protection parameters that previously didn't exist?
You certainly should report it to Zero. Could be an error in the software that they don't know about or didn't intend.
Just saw this, IDK why but I didn't get a notification for the thread.
The motor was not warm at all. This happens when the bike has been sitting overnight in garage at 70F.
I called Zero and a girl answered almost immediately, which was nice. She said an engineer would contact me. The next day I received an email from him asking for more info, which I provided, and advising to try clearing the app cache, and then if that didn't work try reinstalling the app. I tried both and the problem persists. I'm waiting to hear back from him again.
I bet lots of their problems along this line stem from the interface between the bike and people's phones. Just imagine the variables involved there.... different phones and all their variability. I would prefer that the mode feature was included on the motorcycle's display, and you could use the full spectrum of options without the use of a phone at all. Maybe some day they can do that. I hope so.
-
In CA, I find myself in a similar commuting situation as you. I’ve been too lazy to make a custom mode, I just switch between eco, street, and sport in traffic as I find that I need more or don’t need more speed and always keep a healthy buffer.
-
This morning I went riding to check firmware V20 to try to confirm some previously reported issues.
Custom Mode Max Speed: As others have reported, my custom mode defaulted back to 108 mph when checked after my ride.
Turn Signal Self-Cancel: In reply #2 Auriga reported that V20 changed the self-cancel criteria to one based on "bike angle and reduced total distance." In reply #17 I reported that, in a conversation with Zero Customer Service, I was told the criteria was 30 seconds of forward travel. It looks like the answer is both. If you signal a turn and keep riding straight, the turn signal will cancel in approximately 30 seconds. If you do turn, the signal cancels a fixed distance after you straighten up. Accelerate hard out of the turn and the signal cancels in just a few seconds. Accelerate slowly and it may take 10 or more seconds. I'm not sure yet just what the lean angle and distance criteria actually are.
-
Have not heard anything else since this from a couple days ago... bad time for our problem to crop up as its a holiday in the US now, so likely that will make getting a solution take longer. So it is. But I did get a reply directly back from one of the engineers. Pretty cool.
"
Hi XXXXXX,
Thank you for providing us with screenshots and the process you took for trying to troubleshoot. I have attached some of the pictures and included what processes were taken to try to resolve the issue to ticket for the app development team. They are aware of the issue and are currently attempting to resolve it.
I apologize for the inconvenience this issue may or may not be causing.
Please let me know if there are any other questions or concerns.
"
-
Great! Hopefully this is an issue with the App and will be fixed soon.
Also, i can confirm that i see the same 108mph top speed reset issue (co-incidentally this is probably what the new SR would top out at).
What is good to see is that the ChargeTarget feature now works as expected. I set it to 75% and once it reached >70%, the charge speed started to taper out until it reached 75% and continued to charge at <3kW for 3 minutes or so after that and stopped charging at that point. The SoC was exactly 75% when it stopped.
There is one weird issue where you might have to power cycle whenever you change the ChargeTarget for it to take effect. I could not consistently reproduce the issue though.
-
So it turns out at least part of the firmware update actually worked on my bike, when I came to have a go on it. I've got that pesky CANYON mode and it's renamed the other modes into capital letters etc etc. However it now steadfastly refuses to connect to my Pixel 4a's bluetooth whatsoever now, so I can't tweak the modes and I can't check all the firmware versions. I despair.
Cas :)
-
So it turns out at least part of the firmware update actually worked on my bike, when I came to have a go on it. I've got that pesky CANYON mode and it's renamed the other modes into capital letters etc etc. However it now steadfastly refuses to connect to my Pixel 4a's bluetooth whatsoever now, so I can't tweak the modes and I can't check all the firmware versions. I despair.
Cas :)
Lucky me. No new firmware updates lately for my 2018 S. :)
-
Further distaster... by fiddling with developer settings in the Pixel 4a I managed to get it to talk to the bike and pair properly and not drop the connection! The firmware menu appeared in the app! So I set about updating firmware. It did the first bit (agonisingly slowly), it got to 100% on the first bar, then the bike... switched itself off. App said "Waiting for motorcycle". Waited a good long time, gave up, keyed bike off and on again. "Street" mode, which I left it in, is now "STANDARD". Bluetooth now no longer works again. Gahhh. I have no idea what else it has buggered up.
Cas :)
Just in case you didnt try this, did you tell your bike to "forget" the previous bluetooth connection? Mine would not connect after I tried reinstalling the app until I did that. After which, it presented the connection code and I was able to pair the phone and bike again.
-
Tried every conceivable thing. Turned off the WiFi on the phone, emergency service stuff, location, and NFC too, to minimise any interference from anything. Checked app permissions, cleared caches and storage, etc, etc, etc.
Cas :)
-
Weird I did not have connection issues on my Pixel 3. But the App would crash when i tried to activate a custom mode. I had to clear cache and storage (so subsequently login to my account again) to get that to work.
-
My previous Pixel 4a - the one that only lasted a month before it flew out of the crap Ultimate Addons generic phone holder - worked perfectly.
Cas :)
-
Just to give some balance - so it doesn't seem like everything's completely broken - I had no problem updating and using V20 on my SR/F with a Pixel 5.
-
Just to let anyone know who is interested, I emailed the engineer again yesterday about the top speed issue and to his credit he wrote right back. Unfortunately he says the "app development team is still investigating" and he had no predictions or insight to make into when the problem will be resolved.
Having people repeatedly asking are you done yet is annoying so I am not going to ask again. But if you were also thinking of asking, I saved you the trouble.
I noticed if you have a custom mode inactive, its top speed can be 127. Make it active, it drops to 108. Move it back to inactive by making another one active and the speed returns to 127. Its only when its active that the speed limit is reduced. I've tried every combo of working with the app and the bike I could think of to try to defeat this thing and lost.
-
I did some experiments last night and this morning. Any parameters I change in the custom mode will persist; display color, torque, traction control, regen, everything... but the max speed always reverts to 108mph....
Is everyone having the Custom-Mode Top-Speed Issue?
Mine is normally 100, but I did try setting it to 127 and "saved" it to bike.
Then I cycled the key and re-connected and it still showed 127.
I then set it back to 100 :-[
@2020_SRS_Commuter is yours not doing that?
App did stall "waiting for motorcycle...." at end of Update Process, so I force quit the App.
Initially I had "Canyon" Mode (on the bike) but my Custom Mode was still present, in the App.
I slightly edited then "saved" my Custom Mode, back to the bike, and all was as before.
The weird thing is my Range Estimate dropped to 51mi @80% SOC (should be 80mi).
Maybe that "adjusts" after some riding?
My bike is 21 SR/S & upgraded from v19 > v20.
iPhone SE 2020
-
Mine always reverts to 108.
However, your post made me realize there is something I haven't tried yet!!!
One of my daughters has an Iphone 12. I'm going to unpair the bike from my phone, have HER install the app and try this. Maybe that will get my speed back up. My phone is a Samsung S10.
-
OK!
Mostly successful.
I unpaired my SRS from my Samsung S10. On an Iphone 12pro, we installed the app. Using her apple version of the app, I was able to set the top speed to maximum and keep it there. However, on her app, the maximum speed is 120mph. That's as high as the slider goes.
Does anyone else with an apple version of the app have a different maximum value on the speed slider than 120? Not that it works, but on my Samsung version the maximum value on the speed slider is 127. Lunerx says 127, my daughter's says 120.
Thanks for the inspiration btw, at least now the problem appears to be mostly resolved. I wont know for sure until I head back to work in a couple days. You've been more help than Zero's "We're Looking Into It" App Development Team.
-
OK!
Mostly successful.
I unpaired my SRS from my Samsung S10. On an Iphone 12pro, we installed the app. Using her apple version of the app, I was able to set the top speed to maximum and keep it there. However, on her app, the maximum speed is 120mph. That's as high as the slider goes.
Does anyone else with an apple version of the app have a different maximum value on the speed slider than 120? Not that it works, but on my Samsung version the maximum value on the speed slider is 127. Lunerx says 127, my daughter's says 120.
Thanks for the inspiration btw, at least now the problem appears to be mostly resolved. I wont know for sure until I head back to work in a couple days. You've been more help than Zero's "We're Looking Into It" App Development Team.
Glad to hear that helped.
However, I probably misspoke.....upon re-checking my app; it only allows a max of 120mph, for the Custom Mode.
(yeah, it used to allow 127mph on v19)
-
Here you go. No BMS changes, so likely no SOC fixes or improvements:
November 10th, 2021
MY20/MY21/MY22 MBB: Rev 20 BMU Rev 20 BMS: Rev 19 SR/F SR/S SR
* Support for 22MY bikes and the new ZF14.4+ and ZF15.6+ batteries
* Support for Cypher III+ features
* Improve self cancelling turn signals to cancel based on bike angle and reduced total distance
* Rename Street Mode to Standard for all FST bikes
* Fix for Remote Data Connectivity when bike is not riding or charging
* Bug fixes for charge target functionality
* Various bug fixes and improvements
Anyone able to get Battery SOC, via Remote Connect (using Factory Zero App)?
When I hit Remote Connect, I only get the map but the location isn't "live" (it's stuck at my house, regardless of where bike is).
However, the Zero NG [Hans Cappelle app] returns Battery SOC Instantly (as well as location).
So my Cellular Module must be working properly.
However, my Dash Menu shows Cellular "Not Connected".
-
:'(
106 was my top speed, tried today in an open place.... nothing changed.
I'll keep trying with my daughter's Iphone.
-
The engineer says there is now a work-around for the speed issue. It can be fixed by altering parameters on the MBB at your dealer. Thereafter, presumably until they update the app, its important to NOT connect via Bluetooth or the speed will revert. Remote connect is still ok.
I've scheduled for next Thursday at the dealer, and received an email that the engineer would be available to assist them at the appointment time.
-
Hey for anyone interested, I went to the dealer yesterday and they did their fix. An engineer from Zero emailed ahead of time to schedule so they could consult with the dealer while they did it. Something to do with parameters on the "MBB board".
I can still use remote connect but not Bluetooth, or the app will break it again.
Custom mode is now CANYON and it will go 124mph. I cant see the settings of CANYON, but power and torque are 100% or very close, it feels like. The off throttle regen is around 80-85%, and I suppose braking regen is a bit above that. I'd prefer 100% for that but oh well.
CANYON is set to Street Traction so I have to select Sport Traction for each ride. No big deal.
The schedule for charging is still in there and working, but unchangeable.
The dealer had a bill and asked to whom it should be directed. I assumed this was warranty work and told them so, and they let me go without paying. We shall see if they try to come after me for the money later. Seems to me Zero ought to pay since their app futzed it up.
So overall a very reasonable fix, that I hope is a temporary fix. I didn't have to wait long at the dealer and they got it right first try. Looking forward to a new app version I can use.
-
Hello,
Same problem for me since new firmware update middle of Feb (error when updating with android phone, bike was dead : nothing responding, key off too :( so second update done by dealer): limitation of speed at 172km/h, torque limitation (55%), and impossible to modify the custom mode.
Turn signals are now automatically disabled after 30 or 40 seconds (this is new with the firmware)
Remote connection not available since update :(
The dealer told me that they update SR firmware not SRF firmware the first time.
He made a new update this morning: the speed and torque are good from the first bluetooth connection with an Android phone.
After the 1st ride, the speed is limited again :( the remote connection is still not available.
I'm still waiting for news from my dealer.
I understand here, that the problem comes from the mobile app :(
-
Salvation
same problem for me, no cellular connection.
mbb21 didn't solve anything.
and I don't think it's from the android app.
my srs is at the dealership.
I hope to have news soon.
-
Any news on this? My 2021 SR/S still can't establish a cellular connection. The app tells me I have "the latest and greatest firmware" but so far I can only agree with the first part.
-
still the same, the 3g geolocation still doesn't work, the bike is still with the wrong dealer who broke my fairing fasteners, I hope to get it back this week.
the bike has been with these idiots since March 11, 2022
-
The problem with the remote cellular connection may be the cellular module failing on your bike. I made a post about this like a year ago. Here's the link:
https://www.electricmotorcycleforum.com/boards/index.php?topic=11192.msg105299#msg105299
I believe with firmware version 19 remote connection started working for me again (with a replaced cellular module). Remote connection works for me too in version 20.
-
I read that post (thanks for the link) but that was with an older version. The Zero app shows I'm on version 21 now and the problems started the moment I installed this firmware. It might still be the cellular module but my gut feeling tells me that they screwed up with the "latest and greatest firmware".
-
The cellular module is a bit tricky. There's pretty much four reasons it stops working for people.
1. It's firmware hung. It always has power, even when the bike is keyed off, so pulling the CCM fuse or disconnecting/reconnecting the module will reset it.
2. It's not configured correctly. Have you tried deleting and reregistering your account?
3. It's broken. If you've registered an account with the app, and reset it, and it still doesn't work, it could be broken. Happens sometimes, needs a replacement.
4. The app is broken. Pretty common for Zero, if you can see it updating in the unofficial app, but not the Zero one, than it's working and Zero's app is jut bad.
As for reduced top speed/riding modes, I was told there's a known issue where using any of Zero's apps with the bike will overwrite and corrupt the riding modes on your bike forever, reducing top speed/power. I'm told a fix is coming in the next few weeks to the bike itself via another update.
-
1. It's firmware hung. It always has power, even when the bike is keyed off, so pulling the CCM fuse or disconnecting/reconnecting the module will reset it.
I'll try that. I seem to remember that I disconnected the 12 V battery after the update, so there is a good chance that it won't help But anyways, it's worth a shot.
2. It's not configured correctly. Have you tried deleting and reregistering your account?
Hm... not sure why it would all out of a sudden be incorrectly configured just the moment I installed the latest firmware. Nevertheless, I unpaired my phone, deleted the app, re-installed it, paired my phone with the bike and it's still the same. I also tried deleting all of the apps data
3. It's broken. If you've registered an account with the app, and reset it, and it still doesn't work, it could be broken. Happens sometimes, needs a replacement.
That's why I was wondering if everybody has the same problem or if there are people who have the latest firmware installed and still can connect to their bike using the cellular connection.
4. The app is broken. Pretty common for Zero, if you can see it updating in the unofficial app, but not the Zero one, than it's working and Zero's app is jut bad.
It might be the app... what is the unofficial app? I haven't heard of that.
Thanks for all your help :).
-
I believe it's this one:
https://apps.apple.com/us/app/zerong/id1488172044
Not sure if there is an Android equivalent
-
Android alternative app is not available on playstore, I had to install APKPure and install ZeroNG from there. I like it becuase it shows the 12v battery level and from what I've read this seems to be a common problem.
-
This is the android alternative https://play.google.com/store/apps/details?id=be.hcpl.android.zengo
Also sources can be found at bitbucket https://bitbucket.org/cappelleh/zengo-android/ and https://bitbucket.org/cappelleh/zengo-ios/
-
Thanks, I have tried the unofficial app as well and it won't connect either. I pulled the fuse (I really wonder what kind of maniac would hide the fuses the way they did in the SR/S, but that's a different story), also to no avail. I guess there is not much else left other than the cell module itself. As update to version MBB 23 failed multiple times today. Since the cell module isn't working, the only way to install it is via the app and it failed every single time. Next time someone tells me how bad Windows is I'll have a story to tell...
-
My Zero app tells me there is a new firmware.
Currently on v21, and v23 is available.
Did the firmware update pre-check, and all is good to go,
So I hit the "update" buttom and the progress bar stops at ~60% done with "error".
Repeated multiple times with the same result.
Anyone knows how to complete the v23 update ?
Tried with mobile data and wifi - same result,
Android Pixel 5, Zero SR/F 2020, upgraded to v21 with succes last year, clear cache etc.
-
Same initial conditions as yourself. On a sunny day I took my bike out of the underground garage, within cell network range and bluetooth range of my Android phone which itself was located home and plugged in. It took 35 minutes and the update was successful in one go, luckily. I did it essentially because the previous firmware update had reduced the torque beyond what I found tolerable. MBB v23 restored it back from 160 to 190 nM. My bike still connects to the cloud as I can get the SoC and remaining required charging time on the app.
-
Do you also see higher fan speed while charging? Even if it cold: You should hear this at least at the beginning of the charging session. I am unsure, if this is a V23 feature or something independent and just with my bike.
-
Do you also see higher fan speed while charging? Even if it cold: You should hear this at least at the beginning of the charging session. I am unsure, if this is a V23 feature or something independent and just with my bike.
I finally got v23 installed.
Aside from the Full Speed Fan at onset of charging I didn't notice anything different, during the rest of the charging session.
The fan is mostly off during the charge session.
-
Cool! I'll try it tomorrow. Any changes in the charging speed?
-
Cool! I'll try it tomorrow. Any changes in the charging speed?
Hard to say.
Interestingly, the 1st Charge, after update, went to 100%, despite me only asking for 80% ???
Subsequent charges obeyed my 80% request and seemed to be somewhat fast.
I did a 80-95% Top-Up, before a longer ride, and it only took 29minutes (on my 2.8kW charger).
That might be slightly faster than previous, but hard to say.
I might not have a real gauge until I can do some 6kW charging in the wild (on a public charger).
I did get some magic charging, on that trip, after my 1st Stop.
It was more that the Estimate was lower than expected (before parking) and then it went back to the expected estimate (after parking).
Still monitoring it, as I only got v23 in a few days ago.
Torque is strong again (was very weak in v21).
-
To those having trouble w/ FW Updating....
Placing the Phone on top of the Charge Port, w/ Charge Port Door open, seemed to work best.
Also, you do need to wait (probably 3min, as the display says) after a failed attempt, before trying again.
Keying off the bike (between attempts) didn't seem to be necessary though.
After several quick failures, I finally got it to complete the transfer and do the update.
I even got a "Update Complete" after the "Waiting for Motorcycle" message at the end of the update (when the motorcycle power cycles itself).
With past updates, I always had to key off the bike as it hung endlessly on "Waiting for Motorcycle"
-
Cool! I'll try it tomorrow. Any changes in the charging speed?
Hard to say.
Interestingly, the 1st Charge, after update, went to 100%, despite me only asking for 80% ???
Subsequent charges obeyed my 80% request and seemed to be somewhat fast.
I did a 80-95% Top-Up, before a longer ride, and it only took 29minutes (on my 2.8kW charger).
That might be slightly faster than previous, but hard to say.
I might not have a real gauge until I can do some 6kW charging in the wild (on a public charger).
I did get some magic charging, on that trip, after my 1st Stop.
It was more that the Estimate was lower than expected (before parking) and then it went back to the expected estimate (after parking).
Still monitoring it, as I only got v23 in a few days ago.
Torque is strong again (was very weak in v21).
i guess the best way to know will be to look at the dash and note the current in Amps going into the battery from the charger. My guess is that the standard 3kW charger puts out a 28-29 amps by default. Would be interesting to know what it shows now..
-
To those having trouble w/ FW Updating....
Placing the Phone on top of the Charge Port, w/ Charge Port Door open, seemed to work best.
Hoping it would make a difference I tried this today... twice. Still no success. The Bluetooth Connection isn't really my problem. When the update fails I still have the Bluetooth icon on the dash. Yet, the update fails every single time without any explanation what went wrong.
I contacted Zero with this and a few other problems, eventually got a reply what they will do but that's weeks ago now and a reminder email I sent a week ago went unanswered.
The lack of customer service and programming skills at Zero never seizes to amaze me...
-
To those having trouble w/ FW Updating....
Placing the Phone on top of the Charge Port, w/ Charge Port Door open, seemed to work best.
Hoping it would make a difference I tried this today... twice. Still no success. The Bluetooth Connection isn't really my problem. When the update fails I still have the Bluetooth icon on the dash. Yet, the update fails every single time without any explanation what went wrong.
I contacted Zero with this and a few other problems, eventually got a reply what they will do but that's weeks ago now and a reminder email I sent a week ago went unanswered.
The lack of customer service and programming skills at Zero never seizes to amaze me...
Only 2 tries? ???
If you keep at it, it should eventually work.
Just wait enough time between tries.
Mine finally worked, somewhere shy of 10 tries.
Interestingly, it's the one try, where I walked away having nearly gave up on it.
Upon returning it had 70% progress and then finally completed.
Not sure if having the Kill Switch On or Off mattered.
It worked just as badly in either position, until it finally worked :-\
-
It took me about 20 tries to get it to work. I had a feeling it was not the connection between the app and the bike that was failing, but the app downloading the firmware update from the internet. (My internet connection is fine. I suspect it's just badly coded in the app and hosted somewhere with inadequate bandwidth.)
-
Yeah, I'm not going to try 20 times. Zero really needs to get their shit together. I need to go to the dealership anyways because of a dead cell module. Maybe that's the reason for the update failures? I dunno.
Problem is, my nearest dealer is Motoplex in St. Jerome, Quebec and ever since I bought the bike, they pretend not to speak English. It's impossible for me to make an appointment via phone and when I send them an email they just respond that I need to call. The nearest dealer in Ontario is 310 km away. I guess everyone here can see why driving 620 km in one day is a royal PITA with an electric motorcycle.
I am already in touch with the support department at the factory, but apparently they have problems communicating with the dealership, too.
-
Cool! I'll try it tomorrow. Any changes in the charging speed?
i guess the best way to know will be to look at the dash and note the current in Amps going into the battery from the charger. My guess is that the standard 3kW charger puts out a 28-29 amps by default. Would be interesting to know what it shows now..
It might be BS, but the bike does seem to charge at an impressive speed (maybe better than before ???).
These are my readings from the charge screen, while at a 7kW Public Charger.
It went from about 50% to 75% very quickly.
ChargePoint says it consumed 1.79kW in 17min.
I'm satisfied with the charging speed, it's just finding available Level 2 chargers, that adds anxiety.
Would be so nice if we had DCFC (as those are more available, because people don't like how much they cost ::)).
-
It went from about 50% to 75% very quickly.
Your bike can only get between 8-9% every 10 minutes. For 17 minutes that means you would have been able to get no more than 14%. CERTAINLY nowhere near 20%. Your bike's SoC is bugged as fuck.
-
It went from about 50% to 75% very quickly.
Your bike can only get between 8-9% every 10 minutes. For 17 minutes that means you would have been able to get no more than 14%. CERTAINLY nowhere near 20%. Your bike's SoC is bugged as fuck.
Agreed, I get the speed that lunarx mentioned with my 9kW charging capacity. So certainly some SoC issue.
-
Mine does the same. It does it on all 3 battery packs it has had. Watch it charge at full bore for more than an hour at 100%… :(
-
Mine does the same. It does it on all 3 battery packs it has had. Watch it charge at full bore for more than an hour at 100%… :(
To the tune of Spider-Man:
"Magic Charge,
Magic Charge,
Firmware bug
Still at large..."
-
Your bike can only get between 8-9% every 10 minutes. For 17 minutes that means you would have been able to get no more than 14%. CERTAINLY nowhere near 20%. Your bike's SoC is bugged as fuck.
Well that certainly confirms my suspicions.
Interestingly, I barely made it home w/ 70+% where I arrived with 50% (starting from 95%).
I was super conservative on the 48mi outbound and think the grade (although slight) worked against me on the 48mi return.
My instantaneous consumption was higher on the return, during the times I was at comparable speeds.
Still I do feel the SOC is all over the place (mostly after FW updates).
It may improve with some deeper charge/dis-charge cycles ::)
This latest FW did make the bike fun again w/ the restored Torque.
-
the ios and android versions of zero next gen 2.2.6 are available on the stores.
no change for me.
still no working 3g connection.
-
Same here. I didn't think the update would fix my dead cell module but since the release notes state
Inability to perform a successful firmware update on the motorcycle
Top-speed limited to 106MPH when setting custom ride modes
Remote connect issues
Inability to accept Legal Terms and Conditions
Inability to display ambient temperature on the dashboard
I was hoping to be able to finally install MMB version 23. Tried twice and I'm still getting the same error messages. During the first attempt while the progress bar slowly crawled forward the app told me to first connect to the bike. Duh... I have been connected the entire time. How else would I have started the firmware update?
The second time I got the good old "Firmware update has failed. Please stand next to your bike looking like an idiot while waiting three minutes."
I can only assume that the firmware update, even if performed via bluetooth, tries to access the CCM which in my case will cause the update to fail since the CCM isn't working.
On the plus side, after I came to accept that Motoplex Mirabel is unwilling and/or unable to provide service, I am now in touch with another dealer in Lakefield, ON. They have already ordered the parts I need and seem willing to do the necessaty work. It's gonna be a long trip for me, possibly with an overnight stay, but at least they seem to be able to help.
Good luck to everyone else. I hope the new version 2.2.6 will help you at least in some way.
-
Apparently MBB v24 and BMS v20 is now available. Auriga, can you please post release notes?
Curious to see what the new BMS update does!
-
Noticed that as well today when trying (and failing) to use the new app to update my firmware.
-
this surprise morning???
2 big huge update on the app.
MBB and BMS revision 24
I installed it, but nothing changed.
-
Did you have magic charging? And after the update do you still have magic charging?
-
Hi, I had the FW 23 on SRF, when I saw the fw 24 and BMS 20 I tried to update them, after 2 failed attempts I put the phone on the dashboard and magically it finished the two updates without any errors.
Maybe I was lucky or maybe the phone has to be very close to the bike to work well.
It is not clear what the improvements are, but the magic charging is still there.
-
the ios and android versions of zero next gen 2.2.6 are available on the stores.
no change for me.
still no working 3g connection.
Happy to report 2.2.6 fixed my iOS Remote Connection issue.
Although I'm surprised by the lack of Mileage Reading & 12V Batt Level (which the Alternative Zero App has).
In your case, I'm assuming you tried the Alternative Zero App and had no luck with that either?
Have you also tried disconnecting your 12V Battery, just to make sure the Cellular Module (& hopefully some other stuff) gets a Reset.
If you call Zero, they can tell you, if they see your bike reporting via the Cellular Network.
At least then you'd know if it's a Bike Problem vs an App Issue.
-
The new App version 2.2.6 on my Android can't find the new FW (seraches and seraches endlessly).
I tried a direct an unsuccessfull update by dashboard once. Now the second one is in work. If that fails also, I'll wait for the update for the next dealer visit.
The bike runs smooth so far, with the exeption of:
- crazy SOC showing up sometimes, especially when riding fast on the freeway: showing a fast drain of the battery with an SOC of 4%, 20 min. later, after giving the bike some rest, without charging, showing 17% (my main concern).
- crazy target charging (goal set to 80% it's charging to 100% but the next morning showing 81%).
- unable to set new customer mode. At least the CANYON mode can be adapted.
-
This morning my SR/F started asking me to update the firmware, also with a warning that it could take up to 30 minutes. I let the builtin update procedure begin, it kept going for about 10 minutes (bike display only), and then failed.
A couple of hours later I tried again, but this time using the firmware manager of the Android app. The app showed that updates were available for both the MBB (Main Bike Board) and the BMS (Battery Management System). The updating procedure took about 20-30 minutes for each, with apparently the app controlling the update process, and ended successfully twice. It now shows I have revision 24 for the MBB, revision 20 for the BMS.
https://www.zeromotorcycles.com/firmware
2020-22 SR/F & SR/S + 22 SR
MBB V24, BMU V5, BMS V20
- Improvements to BMU temperature monitoring.
- Improved timing for opening and closing the battery contactor.
- Resolved issue preventing proper timeout during charging faults.
-
Also reporting v24/v20 FW update went smoothly.
Placing Phone on Charge Port (w/ Door flipped open) has been working so far... (coincidence?)
Bike seems to run great.
Only done short trips, since updating, so no complaints at moment.
-
Did you have magic charging? And after the update do you still have magic charging?
I am also interested in knowing this. :)
-
Nothing before 33k, then I had several battery issues, one of them being magic charging. For my Zero dealer this clearly was a symptom of a defective battery pack. After pulling the logs and having them analyzed by Zero, I got an appointment for a battery replacement. As for today at 46k, I can sometimes observe a little upward SoC % adjustment when I power up after a long pause, but it remains below ~2%. So, from my own experience, I cannot link "magic charging" with the firmware.
-
Hi just to add my anecdote to the pile in case it helps, I was one of the ones who had the power and top speed limited by the last firmware and software.
The Zero engineer I was emailing with told me when the app was updated, to try the new firmware. I did and after about 30 tries the MBB update completed and said waiting for motorcycle, and that was it. It was not working anymore... dead motorcycle. I disconnected the 12v battery because the display would not go off, and called for a warranty repair.
The dealer did a pick up with their trailer for free, were nice enough to charge the bike so I could ride it home, and updated the MBB from 20 to 24 and BMS from 19 to 20.
Also the display firmware was changed and my display now has a different visual arrangement. Frankly I could have done without that, dont like it actually, but its not a big deal. Where before the display's high contrast mode thing switched as it should, now it will randomly at night go to high contrast which is blinding and annoying, so I had to disable that. I think some of the visual features are too small, like the power meter and time.
Happy to report my bike now has the proper speed and power I choose, and it seems that Zero has sorted all this out, for me at least. The only negative was the dealer broke the fairing holding tabs on the back of the headlight and lied about it, saying they were broken when they took it from me.. until I showed them my video I made while waiting for it to be picked up that showed it WASNT broken when they took it. Video FTW. They say they are ordering me a new headlight.
Also people were talking about charging... on mine what it has always done, particularly when ridden hard, is show about a 10% rise in SOC after it sits for a while. For example today after a highway trip to work I left it at 33%, and now it is at 46%. I always assumed that some sort of cell to cell balancing occurred after use that affected the reading.
-
Hi just to add my anecdote to the pile in case it helps, I was one of the ones who had the power and top speed limited by the last firmware and software.
The Zero engineer I was emailing with told me when the app was updated, to try the new firmware. I did and after about 30 tries the MBB update completed and said waiting for motorcycle, and that was it. It was not working anymore... dead motorcycle. I disconnected the 12v battery because the display would not go off, and called for a warranty repair.
The dealer did a pick up with their trailer for free, were nice enough to charge the bike so I could ride it home, and updated the MBB from 20 to 24 and BMS from 19 to 20.
Also the display firmware was changed and my display now has a different visual arrangement. Frankly I could have done without that, dont like it actually, but its not a big deal. Where before the display's high contrast mode thing switched as it should, now it will randomly at night go to high contrast which is blinding and annoying, so I had to disable that. I think some of the visual features are too small, like the power meter and time.
Happy to report my bike now has the proper speed and power I choose, and it seems that Zero has sorted all this out, for me at least. The only negative was the dealer broke the fairing holding tabs on the back of the headlight and lied about it, saying they were broken when they took it from me.. until I showed them my video I made while waiting for it to be picked up that showed it WASNT broken when they took it. Video FTW. They say they are ordering me a new headlight.
Also people were talking about charging... on mine what it has always done, particularly when ridden hard, is show about a 10% rise in SOC after it sits for a while. For example today after a highway trip to work I left it at 33%, and now it is at 46%. I always assumed that some sort of cell to cell balancing occurred after use that affected the reading.
Good thing you took a video before delivering it, how embarassing for the dealer to lie and be caught red handed like that!
About that rise in SOC after letting the bike stand for a while, I have the same issue, but that seems to be only the symptom of the problem in my case. The real problem is the range estimate in general is way lower than expected, something like 80-90km, when I expect at least 120km.
Have you tried to ride the bike to near 0% before? What odometer range did that max out to?
-
I went for a ride yesterday on my 2018 S with Power Tank to my daughter's home, which is 37 miles away. A half of the ride was at 65 mph and the other half was around 35 mph. When I arrived at my destination the SOC was showing 72% and the range estimator was showing 113 miles left to go.
-
Have you tried to ride the bike to near 0% before? What odometer range did that max out to?
Not deliberately. I think the lowest it ever got was 6%. I'm very careful about the battery, which is easy because its used for only one route, the same trip 5 days per week.
My routine is it arrives home after work around 30% SOC. It sits for an hour to cool and then a charge made with a timer on the garage wall brings it to about 60% and it stops. About an hour before work, the timer turns back on and charges to the 90% charge limit I set.
I ride to work and it sits at around 40% until right before its time to go home the scheduled charging starts, its rapidly charged to 90% and I ride home, where it is around 30% again.
The rise in SOC after parking isn't an issue for me, its a quirk I know happens and it doesn't matter. I hear its much worse for others and could cause issues. Not in my case.
My range is as terrible as you would expect given that the majority of the 32 miles each way is spent on a superslab going about 100mph, and wouldn't serve as a useful comparison for most people.
-
Not deliberately. I think the lowest it ever got was 6%. I'm very careful about the battery, which is easy because its used for only one route, the same trip 5 days per week.
My routine is it arrives home after work around 30% SOC. It sits for an hour to cool and then a charge made with a timer on the garage wall brings it to about 60% and it stops. About an hour before work, the timer turns back on and charges to the 90% charge limit I set.
I ride to work and it sits at around 40% until right before its time to go home the scheduled charging starts, its rapidly charged to 90% and I ride home, where it is around 30% again.
The rise in SOC after parking isn't an issue for me, its a quirk I know happens and it doesn't matter. I hear its much worse for others and could cause issues. Not in my case.
My range is as terrible as you would expect given that the majority of the 32 miles each way is spent on a superslab going about 100mph, and wouldn't serve as a useful comparison for most people.
Here's the thing, which is what I assume the leading question is about:
Zero took away the voltage readings from the average user. If and when Magic Charging hits, all bets are off regarding SoC. This is what Terry Hershner found out the hard way. Originally, when he got his SR/S, he praised the ability to ride around seemingly forever at 0%.
Then, after he realized something fishy was going on with the SoC, he ran a voltage tap from the DC-DC converter to a voltage reader. He then discovered that even though the bike was showing 0% SoC, the actual voltage was as high as 30%. However with the bug he was showing 0% and happily cruising around in limp mode in what he mistakenly assumed was range beyond 0%.
-
This magic charging problem wouldn't be so bad if zero didn't limit the bike's power so much after the battery is showing 0%. If the livewire can have sufficient power even to 0%, why can't zero do it?
-
Honestly that question has to do with powertrain design and capacity of inverters.
-
Wrt firmware updates - I consistently got failures when trying to update my SR/S until I drove it to an area where there was guaranteed no bluetooth interference and then the update process completed. Both BMS and MBB.
One thing that was a bit concerning during this process though is that in the first step, the app seemed to indefinitely stay at the "Waiting for bike" stage. This followed the entire update process on the bike including a reboot. The bt indicator in the dashboard was also lit up, indicating that the bike was connected to the app. After waiting for a few minutes in this state, I figured the process had actually completed and that there was a bug in the app.
So I carried on to the next update. The same thing happened there basically except that I waited even longer for the app to get out of the "waiting" stage. Several minutes. At some point, the bike then actually rebooted again and then the app responded. So I'm happy that I did... but it was close.
It's not clear to me what the implications could have been if I had assumed that the process had completed and it was simply that the app was buggy. It would have been pretty bad if I'd bricked the bike of course. But alas, things appear to be fine now. It's just that after years of the app being unreliable, I'm basically assuming bugs rather than things working correctly. The SR/S is my 3rd Zero bike btw and I think the bikes are awesome. But this aspect of it, a differentiator where things should really shine, could be executed better.
-
For me if I leave my phone near the bike it works perfectly.
-
For me if I leave my phone near the bike it works perfectly.
Same, if I ever try to multitask on the phone or move it around, it will always break the update. Leaving it in the locked glove compartment with the zero app open the whole time without touching it has always worked for me though.
-
Looks like I witnessed a miracle today. Not sure if it's because of the latest app version, pure luck or the fact that the bike was parked in a north-south orientation rather than east-west as it was before, but after many, many attempts the bike finally installed MBB version 24 and BMS version 20 without problems today.
I'll yet have to figure out if that changes anything. I tried to edit my custom mode (name, dashboard color and traction mode), then updated it but the bike doesn't show any of those changes, even after a restart. Would be great if they could perhaps publish something that actually works.
-
Same! I was in the garage working on my other bike, so I figured what the hell, I'll just try to update over and over again, even though it has always failed, even on the new app version.
I'll be damned but after 15 attempts I finally am on the latest MBB and BMS firmware!
-
Leaving it in the locked glove compartment with the zero app open the whole time without touching it has always worked for me though.
Thanks for the tip. After many failed updates, placing the phone inside the SR/F's storage compartment seemed to work for me. I didn't bother locking it in there and left the lid open. Maybe it was just a coincidence, but I had a flawless update of both the MBB and BMS (to v24 and v20).
-
I'm convinced it's just blind luck and all this "only update on a full moon while standing on one foot and breathing out your left nostril" stuff is just coincidence. When I finally got mine to update I did nothing differently than I had the previous dozen+ attempts.