Print

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

[odedmaz]

Is there a simple way to add a 12V port for accessories in the Redshift EX?

The Zero FX had one. Wonder about the Redshift.

Sent from my XT1585 using Tapatalk

[anterabae]

Just picked up this little beauty yesterday, and boy is she fun! Thought I'd finally say hi here now that I'm an owner. [emoji41]

Anyone else in the Toronto Canada area?

Sent from my HTC U11 using Tapatalk

[anterabae]

Just picked up this little beauty yesterday, and boy is she fun! Thought I'd finally say hi here now that I'm an owner. [emoji41]

Anyone else in the Toronto Canada area?

Sent from my HTC U11 using Tapatalk

[anterabae]

Just picked up this little beauty yesterday, and boy is she fun! Thought I'd finally say hi here now that I'm an owner. [emoji41]

Anyone else in the Toronto Canada area?

Sent from my HTC U11 using Tapatalk

[anterabae]

Just picked up this little beauty yesterday, and boy is she fun! Thought I'd finally say hi here now that I'm an owner. [emoji41]

Anyone else in the Toronto Canada area?

Sent from my HTC U11 using Tapatalk

[Neuer_User]

Anyone using Angel GTs on his Zero? They are apparently only available in bigger sizes (120 and 150 instead of 110 and 140), but I've heard that they would still fit.

The reviews on the tires are generally very good, so does anyone use them? What are your experiences with this setup?

[Neuer_User]

Anyone using Angel GTs on his Zero? They are apparently only available in bigger sizes (120 and 150 instead of 110 and 140), but I've heard that they would still fit.

The reviews on the tires are generally very good, so does anyone use them? What are your experiences with this setup?

[Neuer_User]

Anyone using Angel GTs on his Zero? They are apparently only available in bigger sizes (120 and 150 instead of 110 and 140), but I've heard that they would still fit.

The reviews on the tires are generally very good, so does anyone use them? What are your experiences with this setup?

[ElectricZen]

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*[emoji16]. It is possible ODO is not firmware related... Taking the bike to the dealer in an hour.  Will update as more information becomes available.

Sent from my SM-T713 using Tapatalk

[ElectricZen]

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*[emoji16]. It is possible ODO is not firmware related... Taking the bike to the dealer in an hour.  Will update as more information becomes available.

Sent from my SM-T713 using Tapatalk

[ElectricZen]

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*[emoji16]. It is possible ODO is not firmware related... Taking the bike to the dealer in an hour.  Will update as more information becomes available.

Sent from my SM-T713 using Tapatalk

[ElectricZen]

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*[emoji16]. It is possible ODO is not firmware related... Taking the bike to the dealer in an hour.  Will update as more information becomes available.

Sent from my SM-T713 using Tapatalk

[ElectricZen]

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*[emoji16]. It is possible ODO is not firmware related... Taking the bike to the dealer in an hour.  Will update as more information becomes available.

Sent from my SM-T713 using Tapatalk

[giacomo]

Hello,

Does anyone has modified their zero to accommodate small children?
In California the only requirement is that they are able to touch the rear foot pegs.
Does anyone has moved their foot peg in a S platform?

Thanks,
Giacomo

Sent from my SM-G950U1 using Tapatalk

[giacomo]

Hello,

Does anyone has modified their zero to accommodate small children?
In California the only requirement is that they are able to touch the rear foot pegs.
Does anyone has moved their foot peg in a S platform?

Thanks,
Giacomo

Sent from my SM-G950U1 using Tapatalk