ElectricMotorcycleForum.com

  • November 26, 2024, 01:23:13 PM
  • Welcome, Guest
Please login or register.

Login with username, password and session length
Advanced search  

News:

Electric Motorcycle Forum is live!

Pages: 1 [2]

Author Topic: 2016 SR SOC and bms capacity issues after moving from v49 to v51  (Read 1105 times)

anton

  • Jr. Member
  • **
  • Posts: 97
    • View Profile
Re: 2016 SR SOC and bms capacity issues after moving from v49 to v51
« Reply #15 on: October 26, 2017, 04:15:56 AM »

I have exactly the same problem with v51. Will attempt upgrading to new FW (if it's actually available) next Tuesday.
Logged

nevetsyad

  • Sr. Member
  • ****
  • Posts: 319
    • View Profile
Re: 2016 SR SOC and bms capacity issues after moving from v49 to v51
« Reply #16 on: October 26, 2017, 05:09:23 AM »

I disconnected the SCv2 for over a week and level 1 charged daily. SOC still random.
Logged
2023 Energica Experia
2022 Lightning Strike (reservation)
2021 Energica Eva Ribelle (For Sale)
2020 Zero SR/S (sold)
2018 Zero DSR (sold)
2015 Zero SR (Lets call it sold)

jnef

  • Not so newbie
  • Jr. Member
  • **
  • Posts: 66
    • View Profile
Re: 2016 SR SOC and bms capacity issues after moving from v49 to v51
« Reply #17 on: October 26, 2017, 06:10:06 AM »

I have exactly the same problem with v51. Will attempt upgrading to new FW (if it's actually available) next Tuesday.

I was in last week and there was no update past 51 for the 2016SR.  Let us know if there is a new one for you.

I disconnected the SCv2 for over a week and level 1 charged daily. SOC still random.

Ok, that's a big bummer, I guess I was just getting lucky for a little while.  Thanks for the datapoint.
Logged

Shadow

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 1085
  • 130,000mi electric since 2016
    • View Profile
Re: 2016 SR SOC and bms capacity issues after moving from v49 to v51
« Reply #18 on: October 26, 2017, 08:01:19 AM »

I disconnected the SCv2 for over a week and level 1 charged daily. SOC still random.
Seen something like this and it was corrupted data. Go get your BMS/MBB reflashed as a starting point for troubleshooting.
Logged
Pages: 1 [2]