ElectricMotorcycleForum.com
Makes And Models => Zero Motorcycles Forum | 2013+ => Topic started by: ElectricZen on June 13, 2018, 03:13:19 AM
-
Hi everyone! It was suggested to me to make a post and thread regarding firmware issues where we can hopefully amass information and experiences to find a permanent resolution.
My experiences are as follows:
November 2016 - firmware updated at Hollywood Electrics, LA. No issues
May/June 2017 - recieved letter from Zero corporate suggesting that a firmware update should be considered part of regular maintenance.
August 2017 - firmware updated at Dayton Motorsports, Vancouver. Soc and range estimates become unreliable.
June 8, 2018 - firmware update at Daytona Motorsports, Vancouver. Odometer stops counting. Minor improvements noticed but it looks like underlying issues are still present.
I have not noticed any operational problems. I am told from the logs there are no errors in the battery or any codes generated.
I am also told that Zero cannot roll back to previous versions by tech. I wonder how they will problem solve this ODO problem without being able roll back.vOv
So some of the INFO that matters:
These problems are observed in BMS firmware REV 39+ for 2014-2016
REV 17+ for 2017-2018
I could have reworded this more accurately as , the last stable BMS firmware observed are REV 38 for 2014-2016 and REV 16 for 2017-2018
MBB is unaffected or irrelevant. SOURCE: DIGINOW
Primarily posted to provide information for the community.
Input, experiences, tips or corrections welcome!
Current resolution for myself would be a BMS firmware rollback to REV 38. *I hope*😁. It is possible ODO is not firmware related... Taking the bike to the dealer in an hour. Will update as more information becomes available.
-
Update: Odometer is firmware related, caused when the installed firmware doesn't recognize the bike. Symptom is in the Zero App, if the app is unable to identify bike ie. unknown bike.
Odo is running again!
Sent from my ASUS_Z01HD using Tapatalk
-
I'll piggyback on this thread instead of making a new one, as I think my question may benefit others.
I just got a new 2018 S, and there is a firmware update available on my app. Specifically, it says:
Battery Management System
Current Version: 29
New Version: 31
Main Bike Board
Current Version: 22
New Version 24
I have not performed the update because my bike is working fine and I am nervous about going in the wrong direction. However I know that Zero is advertising improvements to power pack life and recommends doing new updates.
I looked at the Unofficial Manual, and it indicates the latest version for the BMS might be 48, and the MBB might be 49 (potential source (http://home.hasslers.net/zerologparser/firmware-summary.php))? Does that mean I am potentially 20+ updates out of date on my brand new bike? Are the version numbers unique to the year?
All of it is very confusing. Does anyone have a list of updates, what they do, with numbers that match what I'm seeing?
And ultimately should I do this update?
-
I am completely confused regarding Zero's firmware revision numbers. The impression that I get is that they are different for each model year. The older bikes seemed to have revision numbers in the 50's, but my 2018 S is showing numbers similar to what is mentioned by Scotchman. ???
-
So if that is the case it sounds like we need to evaluate them on a case by case (year by year) basis.
Therefore my next question is is anyone running BMS 31 and MBB 24 on a 2018 and is it working? I'd like to know what the changes are but that may be too much to ask at this point.
-
They are definitely confusing, I see numbers thrown around that don't seem to match the log parser from the hundreds of files uploaded to it.
When I first got my 2014 my firmware, according to the log parser, was something like 44. It's been upgraded a few times - 47, 49, 52, 53, 54 now. These numbers make sense and are sequential.
For the most part, people with 2014-2016's seem to be in the same range, regardless of model or year.
But the newest bikes people are throwing out numbers much different from that series. Nobody has uploaded a 2018 log to the online parser utility yet, that I can tell, so I wonder if they're seeing it in the Zero app and if that is reporting the same number as the parser.
I should be picking up my 2018 FX this weekend and will piece it together. I'll look in the Zero app and upload a log and compare.
The link above to the latest firmwares is current. I think 54 is the latest MBB version for 2014-2016 or maybe even 2017. I just got it a week or two ago.
Note that I'm only speaking of MBB versions. BMS versions on my bike are lower, it was just upgraded from 27 to 31, supposedly 31 being the latest BMS from Zero.
-
Attached are the logs from my 2018 S that I sent to Zero two months ago in the hopes that they could tell me why my charger doesn't shut off automatically when it finishes charging and balancing my battery pack, after the charging power plug is disconnected. This requires me to turn it off manually by turning the ignition on and then off again. Not surprisingly, I have not yet received a reply to my question.
To tell the truth, I don't really understand the logs, but maybe they will make sense to you.
-
And here is one more that was too large for the previous post.
-
The last firmware update that I installed was apparently BMS version 31 and MBB version 24 (although it said 31 when I completed the download). If the new firmware made any changes to the bike's operation, I haven't been able to notice it. ???
-
Richard230, so that is the same version update I am being presented. Did your charger issue start after that update or do you believe it is unrelated?
-
Yeah the parser code doesn't deal with 2017+ headers very well, that's the issue, I forgot. So I don't think the version is correct:
https://home.hasslers.net/zerologparser/logs/538SMFZ59JCA09207_MBB_2018-03-11.txt
BMS:
https://home.hasslers.net/zerologparser/logs/538SMFZ59JCA09207_BMS1_2018-03-11.txt
-
My dealer did resolve the odometer issue somehow with help from Zero, but now the Bluetooth dosn't work. I have a 2016 Zero FXS.
-
Just updated to BMS 31 and MBB 24 on my 2018 S. Immediate observations:
- My Total kWh used reset
- My Avg watt hours per mile reset
- My charge cycles counter reset
- Unconfirmed: The clock on my dash is now within one second of my iPhone time. This may be a coincidence, if a couple others can confirm similar behavior we may be able to conclude this was a feature addition of synchronizing the clock. I will keep an eye on it and update this post as I learn more.
One other note (I would add this to the unofficial Manual, if you are reading this): the process is not explained well, and non tech-saavy people could get into a bad situation. The steps to upgrade are below:
- Ensure the bike and your phone have charged batteries (>80% is advisable), the bike is unplugged but on, the kill switch is off
- Connect to the bike, go to the "Help" section in the app (designated by an icon of a person wearing a headset) and select Firmware Update
- Press next until the update begins
- Don't touch anything. It is unclear if the bike can recover gracefully from an interruption.
- When the update completes, for me it lost connection to the bike, but I could see the bike was working again. The app instructs you to close the app and reconnect to the bike. Important: going to the home screen on your phone does NOT close it. Fully close the app (on iOS double tap the home button and swipe up on the Zero app. On Android, I believe there is a similar function using the applications button), then reconnect, then reopen Zero. It should open as normal, and if you check for another firmware update, indicate there are none.
If you don't do that final step correctly, by not fully closing the Zero app, but simply reconnecting to the bike and reopening the app while it is in the "updating" function, it starts the MBB update over again. This is fairly terrifying because if the bike doesn't accept receiving the same update again, you could get into a bad situation. The phone app is poorly designed to work this way. Fortunately it worked out for me but I am not sure this would be the case across all bikes, firmwares, and phones.
Hope this helps someone!
-
Richard230, so that is the same version update I am being presented. Did your charger issue start after that update or do you believe it is unrelated?
The charger irritation came that way from the factory. Apparently something that they don't check during the quality control inspection. :(
One additional observation that I can make after the BMS 31 and MBB 24 update, is that voltage showing on the app has dropped from 116V to 115V after the charger completely turns off and the display shows 100%. ??? I keep getting the feeling that most of these firmware revisions are aimed at extending the life of the battery pack.
-
Mine is showing 116v right now but its still balancing. It wouldn't be hugely surprising if that's their goal, and it does benefit us as well (particularly those looking for used bikes in several years).
-
Lead-in thoughts - Support, Support, and Support. Zero needs to get very serious about support whatever the issue e.g. repair, parts, app problems, etc. Concerning the app - How long have app problems existed? Why has Zero limited the amount of data on the latest app? If I used the latest app version, I don't have a clue what the my battery status is. Forget, forget, forget about model improvements. Zero needs to fix what’s wrong, hopefully quickly. JamieC on his thread - ‘My first real issue’, also expressed these very thoughts.
Both Peter and Patrick have both given away their bikes. Why? I can only surmise from their postings, parts failures and lack of support just became too much for them. There are numerous others that have documented their displeasure with support, i.e. dealers and Zero. To Zero’s credit, there are documented posts on this forum where Zero provided support far and above what was expected.
I have a lot invested in this bike. Yes, I know we owners are really Zero’s true R&D department. Being early adopters... - well, you know the rest. I have hopes, still have hopes, of doing things like Terry - get credit for an Iron Butt, riding cross country, being competitive in the Vetter Challenge, etc. Also like Ben Rich - all 48 states.
Just recently, with the Ver 54 update, additional problems surfaced from Ver 52. I began thinking about Peter and Patrick. Should I continue? So I e-mailed Zero - I’m currently in contact with Andrew and Aaron at Zero. It’s refreshing they have taken an interest in my current situation -but - I’m not sure what to do at this moment.
Sorry for getting a bit off-topic.
~~~~~~
14 SR w/PT (13.1 kwh)
My bike recently received the latest firmware update (Ver 54) on 2018.06.01.
Background:
Before the very first firmware update, the bike seemed fine.
I decided to update - it was expected to improve the battery longevity/performance. After updating (likely v52), the app data was very erroneous as well as the dash battery percentage indication. Updating to v54 has caused additional issues.
Ver 54 issues I'm experiencing (Thought - I wonder if there’s more.)
New issues, post 54
[1] Odometer is frozen.
[2] Eco top speed is now ‘65', was ‘70'. Why was it changed? Why???
[3] Dash battery percentage is beyond erroneous, App data is worse than when 52 was accomplished.
[4] Loss of range, now 70-80 miles, was 100 miles. (I think the battery is an issue, not the latest firmware issue. Why?? The old app data which seems ok shows the battery capacity fluctuating somewhere between 11.6 kwh and 12.6 kwh. I haven’t seen 13.1 kwh in sometime.)
Side note: Those who rely solely on their dash battery percentage - Don’t. Read-on - While riding Sunday, at about 65 mph, I experienced the dreaded non-responsive throttle experience. I knew immediately the battery was almost dead. The battery couldn’t be dead because it showed 51% (fifty-one percent). I’m thinking, Ver 54 was heralded by Zero as the final fix. Yep, I have an e-mail from Zero saying so. I immediately slowed way down, and luckily found a charging station about 1.5 miles away. Just before connecting, voltage = 93, dash battery percentage = 50%.
Improvement with Ver 54
The only improvement is - I can finally download the logs. Not once since owning the bike in three (3) have I ever been successful until Update 54. I haven’t looked at the three logs yet, but have attached them.
Final thoughts:
(1) Don't ever update.
(2) If I take Andrew up on his offer to have the bike reverted to per-firmware updates, I’ve decided to never update again.
-
Hi,
Just a small contribution about the versioning: I have a 2017 S and it does follow the same versioning as for the 2018. I guess this is linked to the move to a more advanced MBB with capability for within app update.
For the record, I am also on latest Rev (31 & 24) and nothing special to declare... Works fine.
Aside: when do we organize a petition to go to zero with a request for firmware changelog :-)
-
The 2014 S with PT that I gave my daughter is still running firmware version 32 (if I recall correctly), which was developed early in 2014. The bike continues to run just fine, with no obvious problems and the app still shows much more battery information then my app with its latest update does. Frankly, I just don't understand what Zero is trying to achieve with these app and firmware revisions. ??? They really should let the customer know what each update does, so that we will know what to expect. What would be the reason not to do this? And why are they limiting the battery condition information, such as the pack's kWh capacity, supplied by their recent app revisions?
-
I'm hoping someone can provide some insight on what firmware versions I'm currently running. When I go into the Zero app, the firmware update portal says my MBB is version 16 and I need to update to latest version 24. It does not say anything about the BMS version.
I pulled my MBB and BMS logs and the MBB log says the firmwars revision is 1536 and the board revision is 125. Unless I'm missing something, the BMS log does not indicate any version number.
PS - the bike is a 2017 DSR
Thanks
-
Thanks to everyone for their input! I recognize familiar symptoms described by others. With my ODO fix I also had an unexpected side affect. In less than a 24hr period my ODO jumped up 2000km(~1600miles) and now reads incorrectly. Obviously, there is NO way I covered that kind of distance without knowing about it[emoji16]. I still follow Voltage closely to keep eye on the "real" state of charge. I have sometimes felt the SOC was a bit low..1-3% then would notice at a light that the % would grow appropriately and vice versa. So obviously the algorithm is getting better. But Pre August 2017 firmware was considerably more reliable considering some stretches up here in Canada have me rolling into the ONLY ev station in the entire town at 00% [emoji23]. Fustrating would certainly be a good description how I feel. I was also told Zero CANNOT rollback firmware... Which just seems silly[emoji19]
Sent from my SM-T713 using Tapatalk
-
One day apart. Before second dealer visit to get the ODO running again. Dealer changed the ODO to 27600 (est of what I used over the weekend). They ran 2 km there in the shop to verify it was counting. Rode 80km from there as you can see, but 29682 is wrong. Very curious to see if this reoccurs for anyone else. Seems really random lol.(https://uploads.tapatalk-cdn.com/20180618/70004771b3ed3403c7585e49667a2475.jpg)(https://uploads.tapatalk-cdn.com/20180618/a25734fe5a4409d4c61296c0332bcb87.jpg)
Sent from my ASUS_Z01HD using Tapatalk
-
I thought government regulations made it illegal to have a vehicle odometer that could be altered. ??? If the odometer can be rolled back and forth just by a firmware update, that is something that DOT and your state DMV should know about. :o
-
I thought government regulations made it illegal to have a vehicle odometer that could be altered. ??? If the odometer can be rolled back and forth just by a firmware update, that is something that DOT and your state DMV should know about. :o
The odometer reading is easily changed via the MBB programming / variables and any dealer can do it.
I remember someone having to do it once when a update wiped the data after installing a new motor for example. ;)
-
ODO can be incremented yes. Are you saying it can be rolled back as well... I'd read the value is stored in multiple systems and the MBB takes whichever value is higher?
-
Hey guys. A quick update from me. After the firmware update V53 my ODO
was stuck too, and the range was not what I was used to. So after a while
I checked my logs and found out, that: a)
the ODO-Reading
in the logfiles
was lower than the number on the dash b)
Speed on dashboard was 7-10% to low! and
for that, the km driven also not accurate ("
range"
difference) c) on the top of the logfile
, the Model says
"
NON"
, instead of "
SR"
what was there before. d) Also I had a noticeably stronger regen
in custom mode, what I love (
but will lose again I guess:(
) Zero confirmed to my dealer, that the missing model is the problem. It seems to take a default value for things like sprocket size: Zeros answer: "
The ODO
reading is linked to the model due the sprocket size."
With the tool the zero dealers got in the shops, the dealer and I should be able to set the model of the bike. This is what I will try next Saturday. I will post my results afterwards. I hope it works, because the zero-technicians don't work at Saturday and me dealers knowledge is limited
-
Funny, seems I forgot to mention my MBB firmware is rev 53 BMS rev 41.
Clearly we are seeing similar behaviors. Well, that is reassuring. I have found via observing via Zero Voltage App for Android, that total calculated ah of the battery likes to drift about. Which will definitely cause bad range estimates. Remember everytime the firmware is updated the logs are uploaded and wiped from memory. So the "learning" starts over.
I have noticed small improvements in estimates the more I ride. But SOC will still climb and fall 2-3% randomly at a stop to better reflect where the battery voltage is. Voltage is still king, unfortunately Zero hasn't provided a reliable way to watch it.
That said, with my mixed highway and city riding, I am beginning to see the range driven versus SoC to appear more accurate.( Which indicates to me, no sign of battery degredation, yay!) Maybe at this rate we will see Pre-2017 reliability by 2020 🤣
PS. The rumor is ONLY diginow can roll back firmware...haha.
Sent from my ASUS_Z01HD using Tapatalk
-
Funny, seems I forgot to mention my MBB firmware is rev 53 BMS rev 41.
Clearly we are seeing similar behaviors. Well, that is reassuring. I have found via observing via Zero Voltage App for Android, that total calculated ah of the battery likes to drift about. Which will definitely cause bad range estimates. Remember everytime the firmware is updated the logs are uploaded and wiped from memory. So the "learning" starts over.
I have noticed small improvements in estimates the more I ride. But SOC will still climb and fall 2-3% randomly at a stop to better reflect where the battery voltage is. Voltage is still king, unfortunately Zero hasn't provided a reliable way to watch it.
That said, with my mixed highway and city riding, I am beginning to see the range driven versus SoC to appear more accurate.( Which indicates to me, no sign of battery degredation, yay!) Maybe at this rate we will see Pre-2017 reliability by 2020 🤣
PS. The rumor is ONLY diginow can roll back firmware...haha.
Sent from my ASUS_Z01HD using Tapatalk
The SoC estimate on my display used to do the same thing on my 2014 S. Every time I would stop and then restart, it would drop a point or two. However, that is not happening on my 2018 S - so far. Whatever the SoC reads when I turn the bike off remains the same when I turn it back on.
The other thing that my 2018 does not do that my 2014 did do is to have the regen go off and on for the first mile of riding on a full charge. I am pretty sure that is because the maximum voltage of my 2018's battery pack when fully charged is now 115 volts (it used to be 116 volts when new and with fewer firmware revisions ::) ), whereas the maximum voltage of my 2014 (when new) was 117 volts. ???
-
Ok, i've built a console cable for my Zero FXS, i can confirm that the model is set to NONE:
ZERO MBB> set
*************************************************************
* System Settings Menu *
*************************************************************
model - Model Name NONE
model_year - Model Year 2016
vin - VIN Number XXXXXXXXXXXXXXX
serial - Serial Number 2016_mbb_XXXXX_XXXXX
runtime - Total Run Time 00000:XX:XX:XX
test_mode - Test Mode : Off
Now, i guess that it is possible to change the model with the correct password...
-
I have a SR '15, had the new firmware updated in the middle of May (MBB rev 53), now I have the model set to NoN on the logs as well as directly from the MBB.
After the "upgrade" I get the following:
1- Odometer doesn't update
2- The App doesn't recognize my model SR, it says "unknown model"
3- Top speed is now 95
4- The speed is off by ~5mph
5- Range estimation is way down compare to previous firmware
6- Regen is much stronger than before
I will check with the dealer on Saturday, but he told me that the model is set automatically during the update....
Hopefully there is a new firmware fixing it ....
Giacomo
-
I will check with the dealer on Saturday, but he told me that the model is set automatically during the update....
should be set automatically.. ;)
u have all my "problems" too, i bet it's the missing model. But I'm sad that i will lose the strong regen:(
-
After the first FW update on my 2014 SR, the kW hrs used was zero'd out, and it still does not log any power usage. Any ideas how that happened?
-
I realize that this post outs me as a total newb ignoramus:
How does checking these various readouts change how your ride and care for your Zero? (Not asking about the bugs and fails, I get that.)
Thanks
-
I realize that this post outs me as a total newb ignoramus:
How does checking these various readouts change how your ride and care for your Zero? (Not asking about the bugs and fails, I get that.)
Thanks
The Zero app allow you to adjust certain parameters affecting performace, e.g. regen, max torque, top speed, etc.
Knowing that you can go twice as far at 50MPH as you can at 70MPH has the biggest effect on how I ride when going beyond the range of a single charge!
-
Sure, and I tinker with the custom settings all the time. But there many posts concering issues with battery care and feeding and other issues that are not on the first page of the custom settings. I'm (ignorantly) wondering just how much that stuff matters. It may be a lot, or not so much, I don't know.
-
What I miss most with this year's recent BMS and MBB firmware updates is the disappearance of the current battery pack kWh capacity information. I thought that was interesting and gave you a way to track the overall condition of the battery pack over time. Which is why that information was probably eliminated by Zero. ::)
-
I have a SR '15, had the new firmware updated in the middle of May (MBB rev 53), now I have the model set to NoN on the logs as well as directly from the MBB.
After the "upgrade" I get the following:
1- Odometer doesn't update
2- The App doesn't recognize my model SR, it says "unknown model"
3- Top speed is now 95
4- The speed is off by ~5mph
5- Range estimation is way down compare to previous firmware
6- Regen is much stronger than before
I will check with the dealer on Saturday, but he told me that the model is set automatically during the update....
Hopefully there is a new firmware fixing it ....
Giacomo
Hello,
problem fixed, same Rev 53 but they had to manually change the model to the correct one....
Sent from my SM-G950U1 using Tapatalk
-
What I miss most with this year's recent BMS and MBB firmware updates is the disappearance of the current battery pack kWh capacity information. I thought that was interesting and gave you a way to track the overall condition of the battery pack over time. Which is why that information was probably eliminated by Zero. ::)
I agree! I miss it too, for better or worse I personally expect there to be some degredation and would rather Zero be "adult" about it and show us this info. I always found it reassuring since 100% Soc wavers a bit... 114.8v to the 116.4v. wihich could mean the difference of no small amount of miles. It certainly seems like Zero is trying to hide or "leave out" important info.
Sent from my Nexus 9 using Tapatalk
-
problem fixed, same Rev 53 but they had to manually change the model to the correct one....
Worked for me as well. I think they gave us a wrong firmware last time. Because the regen off throttle was at 10 and regen on breaking on was 15. Max for SR should be 10. After setting the model to SR, it was on 6 and 10 again, and i was not able to set it higher with our user :(
So i'm back to really weak regen, what sucks. But at least me ODO jumped back and speed is back to normal (odo reading in logfiles before/after were 8.7% apart). Range should feel better now too
-
I think they might onto how to fix most of these problems now...as has been stated, the model has to be manually set. My odometer quit after last update although I didn’t notice as I tend to view the trip meter. This was the clue for my dealer who had just fixed a couple of others. Brought the bike in, they did their thing and the Odo was corrected.
Immediately upon returning to the highway I saw similar usage rates to what I had before this fiasco started over a year ago. I have not had time to ride my test routes yet but things really looked better.
I had theorized a model problem all along since my SR was performing as a S with the small battery and my app did not ID the model. Haven’t verified the app yet. Will get back to you all with more info later.
Sent from my iPhone using Tapatalk
-
Perhaps it's finally safe to upgrade. Still running my stock firmware on my '16 DSR. Thanks to all for paving the way on a bumpy road!
Steve
-
Perhaps it's finally safe to upgrade. Still running my stock firmware on my '16 DSR. Thanks to all for paving the way on a bumpy road!
Steve
I think “if you like the way your bike operates, leave it alone†still applies. Mine appears improved but I’m not certain I’m back to pre-update performance yet.
Sent from my iPhone using Tapatalk
-
Perhaps it's finally safe to upgrade. Still running my stock firmware on my '16 DSR. Thanks to all for paving the way on a bumpy road!
Steve
I think “if you like the way your bike operates, leave it alone†still applies. Mine appears improved but I’m not certain I’m back to pre-update performance yet.
Sent from my iPhone using Tapatalk
^this...
Sent from my SM-T713 using Tapatalk
-
is that a snide remark about apple users?
-
I thought this might be a good place to report an oddity with the SOC gauge on my 2017 DSR. I commute to work every day on my DSR which normally uses from 6% - 7% charge each way. I noticed the other day that when I got to work after charging up to 100% at home, the gauge read 92% which was about normal. However, when I left work that day the gauge read 98%. I thought okay that's cool, I'm not going to complain about gaining 6% extra charge for free. But on the way home I noticed that once I hit something like 94% charge, the gauge dropped to 87% in a very short period of time. After that point, the gauge seemed to function properly without any sudden fluctuations.
I'm just wondering if anyone else has experienced this issue and if this is one of the glitches with the later versions of firmware. I have not updated the firmware since taking delivery of the bike in March of this year.
-
I thought this might be a good place to report an oddity with the SOC gauge on my 2017 DSR. I commute to work every day on my DSR which normally uses from 6% - 7% charge each way. I noticed the other day that when I got to work after charging up to 100% at home, the gauge read 92% which was about normal. However, when I left work that day the gauge read 98%. I thought okay that's cool, I'm not going to complain about gaining 6% extra charge for free. But on the way home I noticed that once I hit something like 94% charge, the gauge dropped to 87% in a very short period of time. After that point, the gauge seemed to function properly without any sudden fluctuations.
I'm just wondering if anyone else has experienced this issue and if this is one of the glitches with the later versions of firmware. I have not updated the firmware since taking delivery of the bike in March of this year.
My 2018 S has the latest firmware installed and it hasn't exhibited that issue yet. The battery gauge is very stable.
-
I thought this might be a good place to report an oddity with the SOC gauge on my 2017 DSR. I commute to work every day on my DSR which normally uses from 6% - 7% charge each way. I noticed the other day that when I got to work after charging up to 100% at home, the gauge read 92% which was about normal. However, when I left work that day the gauge read 98%. I thought okay that's cool, I'm not going to complain about gaining 6% extra charge for free. But on the way home I noticed that once I hit something like 94% charge, the gauge dropped to 87% in a very short period of time. After that point, the gauge seemed to function properly without any sudden fluctuations.
I'm just wondering if anyone else has experienced this issue and if this is one of the glitches with the later versions of firmware. I have not updated the firmware since taking delivery of the bike in March of this year.
2016 DSR. And what you described is basically "life" for me with my firmware. Having been through a few versions of firmware and having put some milage with all of them with slow and fast charging, this is "normal". It is important to note the following:
- battery voltage is the only true and reliable way to determine the state of charge of a battery(any battery ironically). But battery voltage slides about a bit if you watch it. If you are using, putting in or letting sit at rest the voltage will be different in all those scenarios.
-soc or state of charge is a porportional representation. Ie. A fraction. So it is only applicable with a known total or max. As we all, I'm sure, have experienced different ranges under different temperatures, various environmental conditions etc. So "full" is really a subjective term, for example "when is a ballon full? Before it pops? But if you fill it with cold air then move to a warm environment, it pops". You get the idea.
-on the software end, it is observable using the zero voltage app to see the "total ah capacity" slide around a lot. The zero motorcycles app no longer displays total kwh. Voltage time amps equals watts... It is very likely a much more complicated problem than it seems. Since really what we all want to know is "how far can I go under the current conditions"
-lastly the top 10% of any battery is a bit subjective, I have noticed this in all the versions of frimware I have used. 10km and soc hasn't moved. Then 1km a % then back to normal sub 90%.
Now, with that all said! It doesn't mean that this isn't fustrating for those afflicted. I think we are all afflicted to a degree, the question is when is it going to show itself. I have travelled a week with completely normal behaviour with the most afflicted and worse version of firmware I have seen. Then suddenly without warning, seemingly completely random it would resume it's erratic behaviour. The latest is better but still no where as reliable as the pre June 2017 version. The soc will eventually find the correct representation, but sitting at a stop, gaining or loosing %'s still unnerves me. Remember this seems to be strictly BMS firmware related. Hopefully new bikes and newer battery packs are immune to these problems.
Morale of the story:. Watch your battery voltage! Whether you are noticing soc reporting problems or not! Just make sure it's not crazy! 100v is about 20% and 112v is about 80%. Its pretty linear between those two. 0%-20% and 80%-100% follow a different curve. 116.4v is full and 96v is empty.
Hope this helps someone! #chargeriderepeat
Sent from my SM-T713 using Tapatalk
-
The firmware on my Chevy Bolt is spot on, range remaining estimates are generally perfect. I trust it. I don't with my Zero. Why can't Zero get a license from a major manufacturer with proven accurate software?
-
Thanks to ElectricZen for a little perspective here, and everyone else for expressing your observations and valid frustrations.
Otherwise, I will admit that in editing zeromanual.com, I have carefully avoided trying to say anything about firmware revisions. And I’ve avoided this thread and this topic with care.
Honestly, I wish I could establish knowledge about this topic. But I have no realistic way to approach the problem without dealer software licensing, only owning a pre-2017 bike which locks me out of firmware checks, and only being able to piece together manufacturer perspective from various secondhand perspectives who themselves are probably cut out of any unambiguous information.
The idea that the firmware version range overlaps between newer models and older ones is... on its face, extremely inexplicable, to put it kindly.
To be clear, I’ve a ton of experience in the software industry and a minor amount of firmware experience and consulting, and this is really baffling. Putting a piece of software on an NHTSA regulated machine that can’t unambiguously explain itself or trace its provenance seems foolish.
I have even heard the perspective of an insider who realized they had no way of knowing what version identifiers they see that correspond to version numbers that we see. This isn’t right.
Remember regarding logs that Zero can shut off our ability to decode them by refusing to provide us with copies of decoded log files. For this reason, the header change and lack of newer confirmed decoded logs concerns me. We have to maintain this ability if Zero bikes are to be serviceable outside of the shops of their licensed dealers.
Zero has a tendency to lock information down when it feels that its livelihood is threatened in the unarticulated framing it uses regarding its livelihood. If it does this fully, we’ll be cut off and beholden to an opaque manufacturer and their invisible reasoning about what our bikes should do. I don’t want that and would abandon any manufacturer that did.
I’m tired of working so many contacts to get reasonable information from Zero, and often getting condescension when finally interviewing primary sources. Zero motorcycles are literally less valuable because they can’t work out how to communicate reasonably with the public.
And I’ll say this: the 2014 dash design was and is terrible, and I knew the moment I saw it at Seattle’s IMS show in 2014 and told the then-CEO. SoC as a two digit percentage leading the display is horrifyingly bad. The display needs to be able to cycle through every value that could shut the bike off. Indications are worthless if you can’t act on them reasonably.
The app as compensatory interface doesn’t even come close to being a reasonable fallback.
Let’s face it: Zero has no idea what to show its owners on its primary onboard display, or no money to redesign it and has decided to pressure its engineers to make SoC live up to entirely unreasonable expectations.
-
> ...
> Remember regarding logs that Zero can shut off our ability to decode them by refusing to provide us with copies of decoded log files. For this reason, the header change and lack of newer confirmed decoded logs concerns me. We have to maintain this ability if Zero bikes are to be serviceable outside of the shops of their licensed dealers.
>
> Zero has a tendency to lock information down when it feels that its livelihood is threatened in the unarticulated framing it uses regarding its livelihood. If it does this fully, we’ll be cut off and beholden to an opaque manufacturer and their invisible reasoning about what our bikes should do.
That's what you get with an Energica or an Alta, right? At least so far?
> I don’t want that and would abandon any manufacturer that did.
...
I would too. I'm sticking with Zero because they are the most open manufacturer in spite of their faults. If that were to change for the worse, I would consider the faults an insurmountable risk. At least at present, I could theoretically ask my dealer to revert firmware or reprogram the sevcon if there's an issue. If an Energica or an Alta were to fail me, and the company wouldn't support me, I think I'd really be stuck. At least with Zero we have the benefit of some of the parts being relatively open, and we could still get some service on our old bikes if the company were to fail.
-
For whatever it is worth, I notice that after a relative flurry of firmware updates and revisions for my 2018 Zero S earlier this year, they seem to have tapered off and I haven't seen any updates being offered for the past few months. ??? Does that mean that the firmware is finally stable, or does that mean that Zero is holding back on additional firmware updates due to technical or legal concerns? ???
One thing is for sure, concerns like that hasn't stopped Microsoft from updating my Windows 10 computer system every time I turn it on. ???
-
The comparison is a little tenuous, as Zero should only be updating firmware to fix bugs or make improvements based on new information. Microsoft is patching a much more complicated set of software for security vulnerabilities that are being discovered daily.
In other words, I consider Zero doing a good job if there is one or two updates a year, and Microsoft doing a good job if there are weekly updates. Either one going in the other direction would be worrisome for me.
-
I have opened a thread here
http://electricmotorcycleforum.com/boards/index.php?topic=8133.0
The idea is to build an index of all our firmware versions and link them with some problems (or no problems) of our bikes.
-
Interesting, since the last firmware update my bike won't fully charge anymore overnight, it's stuck at 87%(111V).
-
Interesting, since the last firmware update my bike won't fully charge anymore overnight, it's stuck at 87%(111V).
Zero evidently has a growing problem with their firmware change control/test/QA/release/documentation processes. They need to prioritize this and get a handle on it before customers stop accepting upgrades and before it costs a lot in recalls. It would be hard to recover from that level of mistrust. At this point, I've seen enough reports that I wouldn't want to upgrade my perfectly functioning bike, and might even be leery of taking it in for dealer service for fear that they might force upgrade or enforce it for warranty.
-
Brought my 16' SR in today for a display problem and they are going to update software. Am I screwed? I got the recall update last summer and while bike works fine, the SOC accuracy has never been the same.
-
Brought my 16' SR in today for a display problem and they are going to update software. Am I screwed? I got the recall update last summer and while bike works fine, the SOC accuracy has never been the same.
I have heard that the latest revisions will be better than what you've experienced. This is just hearsay to me, though.
-
Interesting, since the last firmware update my bike won't fully charge anymore overnight, it's stuck at 87%(111V).
Zero evidently has a growing problem with their firmware change control/test/QA/release/documentation processes. They need to prioritize this and get a handle on it before customers stop accepting upgrades and before it costs a lot in recalls. It would be hard to recover from that level of mistrust. At this point, I've seen enough reports that I wouldn't want to upgrade my perfectly functioning bike, and might even be leery of taking it in for dealer service for fear that they might force upgrade or enforce it for warranty.
Hmm it might just be my charger dying, coincidentally around the time that the firmware was upgraded. Good thing that I have an external these days because it's out of warranty period.
-
Brought my 16' SR in today for a display problem and they are going to update software. Am I screwed? I got the recall update last summer and while bike works fine, the SOC accuracy has never been the same.
I have heard that the latest revisions will be better than what you've experienced. This is just hearsay to me, though.
I hope so. Wasnt having problems with last update other than the dash percent was acting vastly different than before and sandbagging.
-
Hi all, here is my experience (also posted under new thread); the firmware update completely trashed my 2014 DS, its been at the dealer since nov 2017 as they are trying (slowly) to replace every board on the bike! They even shipped a new battery, still not working, waiting for new main board now! Anyway, I am sick and tired of it, have contact the after sales service manager josef morat and the new CEO sam paschel and told them to buy this rubbish motorcycle back from me! Zero is going to fail spectacularly, sorry to disappoint you all but one of the past directors told me that zero had to buy back all their 2012 bikes because they became impossible to maintain! They keep boasting that these bikes have lower maintenance than an ICE bike but that is a blatant lie! If an electronic board fails, one cant fix it, one has to buy a new one, and then its firmware is not compatible with the rest of the bike! Compare that to buying and replacing a failed spark plug!? It is a no-brainer! Farewell EVs, they are doomed.
-
Hi all, here is my experience (also posted under new thread); the firmware update completely trashed my 2014 DS, its been at the dealer since nov 2017 as they are trying (slowly) to replace every board on the bike! They even shipped a new battery, still not working, waiting for new main board now! Anyway, I am sick and tired of it, have contact the after sales service manager josef morat and the new CEO sam paschel and told them to buy this rubbish motorcycle back from me! Zero is going to fail spectacularly, sorry to disappoint you all but one of the past directors told me that zero had to buy back all their 2012 bikes because they became impossible to maintain! They keep boasting that these bikes have lower maintenance than an ICE bike but that is a blatant lie! If an electronic board fails, one cant fix it, one has to buy a new one, and then its firmware is not compatible with the rest of the bike! Compare that to buying and replacing a failed spark plug!? It is a no-brainer! Farewell EVs, they are doomed.
It continues to be a mystery to me how the same vehicle can be so different over time. My daughter's 2014 S (that I used to own) still runs great and only has a problem which started about a year ago, where it will no longer charge the battery pack to 100%. Now it stops at 92% unless you leave the charger connected for about a week. Otherwise no other problems. I just don't understand how the same vehicle, with the same design and the same components can be so different after time. With so many parts being replaced by gorw's dealer, you would think that some improvement would have resulted. All I can imagine is that there was some sort of assembly problem in the wiring hidden away in the innards of the bike that is causing his problem. It certainly would be interesting to find out what would cause such a terrible situation for both gorw, his dealer and Zero. If I was Zero I would buy back the bike, give it to their engineers and let them play with it in their spare time until they found the problem(s) so that something like this could be avoided in the future.
I might add that when my 2014 S Power Tank was installed by my retail dealer when the bike was originally sold to me, they couldn't get the main board to recognize that the PT had been installed. A Zero technician visited the shop and, after a couple of hours, discovered that the original PT was defective. Installing a new PT still didn't solve the problem, however he eventually discovered (a twofer) that a couple of pins in a large wiring connector had been bent when the bike was assembled at the factory. Once he straightened out those connecting pins the PT came on line and has worked well ever since. Sometimes a single damaged connector can cause all sorts of problems. One or more wiring connectors could certainly have been damaged by the shop during the process of removing and replacing parts over and over again and that might be causing all of these issues. ???
If I was Zero I would (or should) be concerned about how their dealer is feeling about the trouble this bike is causing their repair shop - especially during the busy summer riding season. These sort of problems tend to be talked about at motorcycle dealer conventions and might result in other dealerships not wanting to take on the franchise in the future. :(
-
Fair comment Richard, but I wonder how many people know that Zero's electronic boards come with conventional PCB edge connectors which they try to seal with silicon grease ::). If you look at any other vehicle (ICE or EV), the reputable ones have proper robust IP66 or better casings with air, dust and water proof connectors! Zero will have to complete redesign and manufacture (or get their suppliers to) proper electronic systems to increase their integrity and reliability!
-
Hi all, here is my experience (also posted under new thread); the firmware update completely trashed my 2014 DS, its been at the dealer since nov 2017 as they are trying (slowly) to replace every board on the bike! They even shipped a new battery, still not working, waiting for new main board now! Anyway, I am sick and tired of it, have contact the after sales service manager josef morat and the new CEO sam paschel and told them to buy this rubbish motorcycle back from me! Zero is going to fail spectacularly, sorry to disappoint you all but one of the past directors told me that zero had to buy back all their 2012 bikes because they became impossible to maintain! They keep boasting that these bikes have lower maintenance than an ICE bike but that is a blatant lie! If an electronic board fails, one cant fix it, one has to buy a new one, and then its firmware is not compatible with the rest of the bike! Compare that to buying and replacing a failed spark plug!? It is a no-brainer! Farewell EVs, they are doomed.
It continues to be a mystery to me how the same vehicle can be so different over time. My daughter's 2014 S (that I used to own) still runs great and only has a problem which started about a year ago, where it will no longer charge the battery pack to 100%. Now it stops at 92% unless you leave the charger connected for about a week. Otherwise no other problems. I just don't understand how the same vehicle, with the same design and the same components can be so different after time. With so many parts being replaced by gorw's dealer, you would think that some improvement would have resulted. All I can imagine is that there was some sort of assembly problem in the wiring hidden away in the innards of the bike that is causing his problem. It certainly would be interesting to find out what would cause such a terrible situation for both gorw, his dealer and Zero. If I was Zero I would buy back the bike, give it to their engineers and let them play with it in their spare time until they found the problem(s) so that something like this could be avoided in the future.
This is quality (quality assurance coupled with quality control) in a nutshell, and why I'm not inherently enthusiastic about Energica or other boutique manufacturers necessarily seeming like better bikes right now just because they have better components. Quality is a process with an intentional feedback loop.
I'm pretty sure those engineers don't have spare time. Or they need to reprioritize engineering time to get ahead of this, and delay revising the bike design another year.
I might add that when my 2014 S Power Tank was installed by my retail dealer when the bike was originally sold to me, they couldn't get the main board to recognize that the PT had been installed. A Zero technician visited the shop and, after a couple of hours, discovered that the original PT was defective. Installing a new PT still didn't solve the problem, however he eventually discovered (a twofer) that a couple of pins in a large wiring connector had been bent when the bike was assembled at the factory. Once he straightened out those connecting pins the PT came on line and has worked well ever since. Sometimes a single damaged connector can cause all sorts of problems. One or more wiring connectors could certainly have been damaged by the shop during the process of removing and replacing parts over and over again and that might be causing all of these issues. ???
This is what a robust set of troubleshooting procedures is supposed to surface.
Anyone involved with an electric motorcycle necessarily must be able to perform basic fault isolation, but be able to certify through testing what definitely is working right up to that component so that the component swap leads to a predictable result.
I think some of this might require dealership tooling where they can mock out any part of the major system components to check connectivity and interactions. Complicated wiring harnesses are valid subjects of scrutiny [/size]during troubleshooting[/size][size=78%].[/size]
Fair comment Richard, but I wonder how many people know that Zero's electronic boards come with conventional PCB edge connectors which they try to seal with silicon grease ::) . If you look at any other vehicle (ICE or EV), the reputable ones have proper robust IP66 or better casings with air, dust and water proof connectors! Zero will have to complete redesign and manufacture (or get their suppliers to) proper electronic systems to increase their integrity and reliability!
Yeah, Zero's connectors are sometimes underbuilt or underguarded, for their cost and weight.
If you're thinking of the BMS on 2013-2014, that was revised after that with a more robust connector.
If you're thinking of the DC-DC connector, it's what Sevcon makes (I know there are other vendors but have no idea about their suitability) and definitely deserves a baffle or guard to keep dirt from accumulating in the connector. Sevcon seems kind of lethargic when you consider how many of their products haven't changed in 5 years.
-
Hi,
can anybody comment these values of my BMS?
After the latest firmware update I still have no exact values of SOC and Range.
What means "Pack Capacity Remaining : xxx Ah"?
Should be less than the 100 Ah capacity, shouldn't it?
************* BMS #0 ***************
- BMS Board Rev : 03
- BMS Firmware Rev : 43
- BMS Serial Number : 2015_bms...
- Battery Serial Number : 15...
Some days ago:
- Pack SOC : 35%
- Fuel Gauge : 32%
- Model Year : 2015
- Pack Capacity : 100 AH
- Pack Capacity Remaining : 136 AH
- Total Energy Used : 13 KWH
- Number Of Bricks : 4
Today:
- Pack SOC : 28%
- Fuel Gauge : 25%
- Model Year : 2015
- Pack Capacity : 100 AH
- Pack Capacity Remaining : 174 AH
- Total Energy Used : 42 KWH
- Number Of Bricks : 4
Greetings,
Uwe
-
do you have the diagram how you built the console cable?
-
do you have the diagram how you built the console cable?
This topic has all the information about that cable https://www.electricmotorcycleforum.com/boards/index.php?topic=10424.msg95446#msg95446
-
Thanks for the video guys
https://youtu.be/CjIXCD2-CdU
-
A bit long winded and heavy on the drama... but the point is valid. Zero keeps dropping the ball on software updates. Even their apps for their bikes are a bit of a hot mess. Don’t see it changing anytime soon as in my opinion the CEO is bussy with a big brand/marketing push. I have never seen them move fast to fix some of these things.
-
Wow, this guy shows the Amp Hour issue from 2018...
Hi,
can anybody comment these values of my BMS?
After the latest firmware update I still have no exact values of SOC and Range.
What means "Pack Capacity Remaining : xxx Ah"?
Should be less than the 100 Ah capacity, shouldn't it?
************* BMS #0 ***************
- BMS Board Rev : 03
- BMS Firmware Rev : 43
- BMS Serial Number : 2015_bms...
- Battery Serial Number : 15...
Some days ago:
- Pack SOC : 35%
- Fuel Gauge : 32%
- Model Year : 2015
- Pack Capacity : 100 AH
- Pack Capacity Remaining : 136 AH
- Total Energy Used : 13 KWH
- Number Of Bricks : 4
Today:
- Pack SOC : 28%
- Fuel Gauge : 25%
- Model Year : 2015
- Pack Capacity : 100 AH
- Pack Capacity Remaining : 174 AH
- Total Energy Used : 42 KWH
- Number Of Bricks : 4
Greetings,
Uwe
-
Hi,
I've recently upgraded my SR/F from firmware v14 to v18 (end of October). Since this upgrade I have problems with the mobile App (Zero Next Gen on a Sony Xperia XZ, Android 8.0.0) :
- I can't get datas whithin the app when I'm far from the vehicule, all that's indicated is "battery 30%" which is not the correct value
- When paired with the bike, I can start/stop a trip record, but nothing is recorded
The upgrade of the App to v2.2.3 (beginning of decembre) didn't solve anything. I also tried the ZeroNG app but it displays the same battery level as the official app.
Anybody noticed something similar ?
-
Does your bike show cellular connected when parked outside in clear sky with good cell reception? There were some reports of failing cellular modules on reddit which would explain out of date information on the cloud service. Also you can check the timestamp of latest update it the zero ng app.
-
Hi All, I updated to v18 when I got my 2020 red SR/F. My bike has never connected to a cellular network. It still shows the bike in the US. On the bike at cellular it shows 'not connected' Is this a common problem? I see Ooook has also the issue of not connecting remotely? v19 firmware did not fix it...
-
I've seen several other reports of this issue. So it might be just another Firmware issue. Here for example on the facebook group
https://www.facebook.com/groups/zmcowners/permalink/3728073170595197/
My own experience in a nutshell:
On my own bike FW v17 on dash it shows "connected" and I get all the location updates.
On a loaner SRF I have with FW v19 it shows "not connected" and also the CCM config confirms that. I can't however check what the API reports as this is not my own bike.
Also reported on reddit btw https://www.reddit.com/r/ZeroMotorcycles/comments/kgyeh1/zero_moto_cellular_not_connected/
-
And a quick update after having firmware version 19 installed on my own SRF. I can confirm it breaks the remote connect function. Both soc and location are stuck since a few days at the point where the update was executed (dealer).
Never had this issue before on the bike and even still got the notification of bike being moved and route afterwards towards dealer. Moving it back didn't trigger that notification nor any other update.
-
Hi everyone,
Just thought i would add my two cents to this discussion.
I just bought a second hand SR/F this weekend and have the same issue : Cellular Shows Not Connected.
I have the app and the bike is connecting via bluetooth.
Firmware was on version 17 when i got the bike, i thought that might be the issue so i upgraded to 19 via bluetooth, the update worked, but the cellular is still not connected.
When trying to connected Remotely, it shows me data from 11 month ago at the original dealership.
My bike was outside when i tried this and i live in a well covered area so definitely not a network issue.
IF anyone finds a solution let me know I would really like to know the status of my bike/charge when I am not next to it.
NB: this is my first ever post on this forum, thanks all of you for your earlier posts, they helped me make my decision to purchase the bike. And thanks @Hans2183, all your youtube videos where very instructive, I wish you all the best with your channel !
-
My 2018 S only seems happy when it connects over the internet to my home WiFi system, which is fine with me as I don't have cell service at my home.
-
Hi NeoRider
I had the same issue for me: just go to your dealer, he will take contact with Zero support, and they will connect to your bike and correct the Cellular connexion.
-
And a quick update after having firmware version 19 installed on my own SRF. I can confirm it breaks the remote connect function. Both soc and location are stuck since a few days at the point where the update was executed (dealer).
Never had this issue before on the bike and even still got the notification of bike being moved and route afterwards towards dealer. Moving it back didn't trigger that notification nor any other update.
Just got my bike updated by the dealer to V19. Same result :-(.
Now I will let them know, what you guys already have found out (great forum!).
-
I just spent several months getting a new CCM fitted (under warranty). It had to be coded to the bike which unfortunately the first that Zero sent out was not. But after successful replacement it updates the Cloud status fine, but after the bike is keyed off for a couple of hours (next CCM update basically) then the SOC goes to 0%. Key the bike on and leave for an update to occur and it is correct again.
It feels as though this is an issue with the new CCM sending back the wrong status when the bike is off. But the dealer is stating this is a known issue with the App (Zero NextGen app that is).
Anyone else with any further info on this issue? I can't help but feel it's a simple config problem. :o
-
I just spent several months getting a new CCM fitted (under warranty). It had to be coded to the bike which unfortunately the first that Zero sent out was not. But after successful replacement it updates the Cloud status fine, but after the bike is keyed off for a couple of hours (next CCM update basically) then the SOC goes to 0%. Key the bike on and leave for an update to occur and it is correct again.
It feels as though this is an issue with the new CCM sending back the wrong status when the bike is off. But the dealer is stating this is a known issue with the App (Zero NextGen app that is).
Anyone else with any further info on this issue? I can't help but feel it's a simple config problem. :o
That's exactly how Remote Connect, on my 21 SR/S, works with v19.
(I don't have any experience with it, on v18 for comparison.)
Not completely sure, but SOC, via Remote Connect, also seems to work;
When Actively Charging?
For a short time, after plugging in a Charge Cord?
Does that match anyone else experience?
-
Greetings! How did you solve the problem with undercharging the battery to 100%? I have Zero S 2014 and it has a problem too...
-
I just spent several months getting a new CCM fitted (under warranty). It had to be coded to the bike which unfortunately the first that Zero sent out was not. But after successful replacement it updates the Cloud status fine, but after the bike is keyed off for a couple of hours (next CCM update basically) then the SOC goes to 0%. Key the bike on and leave for an update to occur and it is correct again.
It feels as though this is an issue with the new CCM sending back the wrong status when the bike is off. But the dealer is stating this is a known issue with the App (Zero NextGen app that is).
Anyone else with any further info on this issue? I can't help but feel it's a simple config problem. :o
my ccm is faulty from the beginning ( february ) and i have open a ticket to my dealer, and i call it every week for status... but at today nothing.
my current ccm have 2 problems, it never report soc % and charge status to the server,
but the worst problem is that after a server position update ( with bike in motion) it hang, simply ccm go to low power mode and never wakeup, to fix this you need to disconnect 12v battery.
if bike is stationary it update server position without issues every time you turn on key.
running a canbus trace on the communication lines, the bike send soc % and fw ver to the ccm every sec, and ccm send back the info you see in the diagnostic.
as soon it hang it disconnect from bus and all the data transmitted from mbb is not captured.
i have also found canbus messages (id253) with soc 0% sent to the ccm at key on, this is likely the cause of the bad soc% reported to the server (if ccm update the server with this value)...and i think it will be addressed by a new MBB firmware soon or later... (i'm running MBB v24)
p.s you can check the real data sent from ccm to the server with the following info https://www.electricmotorcycleforum.com/boards/index.php?topic=9520.0
cause app can be bugged too :'(
-
Model Year 2022 Zero SR/F/S CCM Firmware Update
Service Campaign
https://dot.report/bulletins/10216888
this is the real explanation, i hope this will fix CCM :o
-
Hello from Portugal, just by the way on my 2016 FX which i use since 2019 i never made an Update. And everything is working well. Although whole power untill around 30% SOC. Maybe it is a Friday-Weekend production. When i read all this things i wonder little bit, why people make updates with this expiriences. Ánd what is the problem with good Software Engineers around CA ? I m be anxious how long my Bike is running. Range is going down... Is it right that 2017 Modells available with Modular and Longbrick ? Ola, Alter
-
Just an update on my own CCM issues / situation.
I tried time and again to prompt the dealer, and Zero UK, I received silence. I think these units are temperamental and so I suspect there are many root causes to what is the same symptom (no connectivity).
I decided to go in and investigate myself. I had previously removed the 5v fuse to the CCM with no luck whatsoever. The bike still reports “Cellular” status as “Not Connected”. So I proceeded and removed the tank plastics (easily done) and removed the CCM module, which is just behind the ignition switch and secured with cable tied. I just cut those and then removed the rubber boot that prevents water ingress. The plastic housing is held closed by a single small screw. Removing this I can see there is a sim. I popped this out, then put it all back together and connected to the bike.
Keying the bike on and the status showed as “Connected”. I had forgotten to put a little internal plastic cover back on and when I did so it reported “Not Connected”. I took apart and reassembled (all whilst connected to the bike and keyed on) and it flipped to “Connected” again. Loose wire connections? Flaky cellular connection? Unit upside down? I’ve no idea. After a few hours the bike is staying in a “Not Connected” state when keyed off and “Connected” when keyed on. I remember a firmware fix was supposed to resolve loss of connectivity when the bike was off and not charging. I’ll continue to monitor, fingers crossed I at least have connectivity when it’s charging - that’s the bit I miss; ie when should I go back to the bike if I’m not in Bluetooth range.
Paul.
-
what crap this ccm, on my srs/s 2021, it hasn't worked since January 2022.
my bad dealer, can't do anything about it, they don't want to bother.
I would have been curious to see the photos of the open ccm...
-
There is a decent post on Facebook with good photos. Hence I didn’t feel the need to. It’s referenced in the ZeroManual unofficial site.
https://m.facebook.com/groups/zmcowners/permalink/2965139423555246/