ElectricMotorcycleForum.com
Makes And Models => Zero Motorcycles Forum | 2013+ => Topic started by: Richard230 on January 29, 2020, 05:45:03 AM
-
Lately I have experienced a momentary power interruption every now and then when accelerating from a stop. There is seems to be no obvious pattern to the issue, other than it happens when leaving a stop and when my speed is about 10 mph. It happens perhaps every fifth ride and only lasts a for a fraction of a second. I originally thought that my glove was slipping on the throttle grip and that was causing the problem. But today I am pretty sure that my glove did not slip when it happened again. No big problem as long as it doesn't get worse. Today I was riding in light rain when it happened, but I did that yesterday and didn't experience the "glitch". Anyone have any thoughts? ???
-
Any error codes? Or can you pull the logs from the last few days?
-
Any error codes? Or can you pull the logs from the last few days?
I'll give that a try tomorrow.
-
Belt slipping maybe?
-
Belt slipping maybe?
Not my belt. It is as tight as a drum. Plus the interruption occurs under light throttle.
-
Could be an intermittent kickstand switch. When it happened to my bike, I realized the red light on the dashboard was flashing when it happened. Cleaned and re-jiggered the kickstand switch and it seems fine now. It's a magnetic switch so I've given some thought to gluing a magnet to it to disable it entirely...I don't think it's very useful for experienced riders. It only happens at low speed because (fortunately) the firmware won't cut off power when you've built up any speed at all.
-
I downloaded my logs and sent them to Zero, who responded back within two hours. The electrical engineer that looked at the logs said that he couldn't see any issue in the logs. No faults. He suggested that I take my bike into my Zero dealer and let them look at it. I doubt that would be very productive except to add a little profit to the shop's back room.
When the problem occurred, I didn't notice any warning lights flashing, which would likely have triggered a fault in the logs, I imagine. So the momentary power interruption remains a mystery. Hopefully it won't get any worse and pop up more frequently. Zero did create a case number for my inquiry. Case # 00059431. I wonder if the case numbers started at "1"?
-
Could be an intermittent kickstand switch. When it happened to my bike, I realized the red light on the dashboard was flashing when it happened. Cleaned and re-jiggered the kickstand switch and it seems fine now. It's a magnetic switch so I've given some thought to gluing a magnet to it to disable it entirely...I don't think it's very useful for experienced riders. It only happens at low speed because (fortunately) the firmware won't cut off power when you've built up any speed at all.
It's a good idea to have it in case the throttle gets bumped and you've forgotten to hit the kill switch (more likely when you don't need to kill the engine).
Zero did create a case number for my inquiry. Case # 00059431. I wonder if the case numbers started at "1"?
Probably, mine was 00056684 from nearly a month ago. I imagine it's an automated system so it's going to increase anytime someone downloads and sends the logs, whether they actually have an issue or not. I never heard back from Zero even after I replied to their email telling them what my issue was.
-
I downloaded my logs and sent them to Zero, who responded back within two hours. The electrical engineer that looked at the logs said that he couldn't see any issue in the logs. No faults. He suggested that I take my bike into my Zero dealer and let them look at it.
When the problem occurred, I didn't notice any warning lights flashing, which would likely have triggered a fault in the logs, I imagine. So the momentary power interruption remains a mystery. Hopefully it won't get any worse and pop up more frequently. Zero did create a case number for my inquiry. Case # 00059431. I wonder if the case numbers started at "1"?
Did you get a copy of your logs?
The case number could be an autoincrementing ID from 0 or 1 or it could be totally different. It's hard to tell without a large sample.
-
I downloaded my logs and sent them to Zero, who responded back within two hours. The electrical engineer that looked at the logs said that he couldn't see any issue in the logs. No faults. He suggested that I take my bike into my Zero dealer and let them look at it.
When the problem occurred, I didn't notice any warning lights flashing, which would likely have triggered a fault in the logs, I imagine. So the momentary power interruption remains a mystery. Hopefully it won't get any worse and pop up more frequently. Zero did create a case number for my inquiry. Case # 00059431. I wonder if the case numbers started at "1"?
Did you get a copy of your logs?
The case number could be an autoincrementing ID from 0 or 1 or it could be totally different. It's hard to tell without a large sample.
I have a copy of my logs, but my new Windows 10 computer (no problem with my old Windows 7 version) won't let me open them. In any case, I figure that an electrical engineer at Zero knows more about how to read them than I would. I might add that it took about 15 minutes to download the logs. I bet that my eyes would glaze over trying to understand them, anyway.
-
I downloaded my logs and sent them to Zero, who responded back within two hours. The electrical engineer that looked at the logs said that he couldn't see any issue in the logs. No faults. He suggested that I take my bike into my Zero dealer and let them look at it.
When the problem occurred, I didn't notice any warning lights flashing, which would likely have triggered a fault in the logs, I imagine. So the momentary power interruption remains a mystery. Hopefully it won't get any worse and pop up more frequently. Zero did create a case number for my inquiry. Case # 00059431. I wonder if the case numbers started at "1"?
Did you get a copy of your logs?
The case number could be an autoincrementing ID from 0 or 1 or it could be totally different. It's hard to tell without a large sample.
I have a copy of my logs, but my new Windows 10 computer (no problem with my old Windows 7 version) won't let me open them. In any case, I figure that an electrical engineer at Zero knows more about how to read them than I would. I might add that it took about 15 minutes to download the logs. I bet that my eyes would glaze over trying to understand them, anyway.
You don't have to be the only set of eyes that look for issues. You can publish them and get some feedback. Maybe we can learn something.
-
Well, since you asked, here they are. Fortunately, the log files are a lot smaller than I had expected from the time it took to download them. Here is the MBB log.
-
And here are two battery logs, which the Zero engineer also asked to review.
-
Well, I've decoded the logs, but they're too large to use as forum attachments. When is a good timeframe or set of timeframes to focus on?
For reference, logs are slow to download because of (1) Bluetooth data transfer rates, (2) firmware CPU speed, and (3) for BMS logs because the data get transmitted over CAN to the MBB and then over Bluetooth.
-
Well, I've decoded the logs, but they're too large to use as forum attachments. When is a good timeframe or set of timeframes to focus on?
For reference, logs are slow to download because of (1) Bluetooth data transfer rates, (2) firmware CPU speed, and (3) for BMS logs because the data get transmitted over CAN to the MBB and then over Bluetooth.
The power interruption occurred last Tuesday, about 8 miles after starting my ride that day. After parking the bike for a while, I then rode back home 10 miles. Upon returning home I washed the bike and rode it around for a couple of miles to dry it off, parked it and plugged in the charger. The next time I turned on the bike was yesterday when I downloaded the logs.
-
The power interruption occurred last Tuesday, about 8 miles after starting my ride that day. After parking the bike for a while, I then rode back home 10 miles. Upon returning home I washed the bike and rode it around for a couple of miles to dry it off, parked it and plugged in the charger. The next time I turned on the bike was yesterday when I downloaded the logs.
Not sure about the date, but in this section the bike thinks you went from riding, within 2 seconds put the kickstand down, and within 26 seconds later you're back to riding? Doug might have been right on here.
07136 01/27/2020 09:31:34 Riding PackTemp: h 15C, l 15C, PackSOC: 99%, Vpack: 115.35V, MotAmps: 58, BattAmps: 3, Mods: 11, MotTemp: 20C, CtrlTemp: 14C, AmbTemp: 11C, MotRPM: 128, Odo:10495km
07137 01/27/2020 09:32:35 Riding PackTemp: h 15C, l 15C, PackSOC: 99%, Vpack:115.853V, MotAmps: -53, BattAmps: -14, Mods: 11, MotTemp: 20C, CtrlTemp: 16C, AmbTemp: 9C, MotRPM:1221, Odo:10495km
07138 01/27/2020 09:33:35 Riding PackTemp: h 15C, l 15C, PackSOC: 99%, Vpack:115.292V, MotAmps: 0, BattAmps: 1, Mods: 11, MotTemp: 21C, CtrlTemp: 17C, AmbTemp: 9C, MotRPM: 102, Odo:10496km
07139 01/27/2020 09:33:37 Throttle Disabled: Kickstand Sw,
07140 01/27/2020 09:33:37 DEBUG: Module scheme changed from Running mode to Stopped mode
07141 01/27/2020 09:33:37 DEBUG: Module mode Change Does Not Require Disconnect
07142 01/27/2020 09:34:03 DEBUG: Module scheme changed from Stopped mode to Running mode
07143 01/27/2020 09:34:03 DEBUG: Module mode Change Does Not Require Disconnect
07144 01/27/2020 09:34:35 Riding PackTemp: h 15C, l 15C, PackSOC: 99%, Vpack:114.931V, MotAmps: 128, BattAmps: 16, Mods: 11, MotTemp: 22C, CtrlTemp: 17C, AmbTemp: 9C, MotRPM: 429, Odo:10496km
-
Here's the event in question for sure, and there's also a kickstand switch entry which I think is pretty definitive:
06958 01/21/2020 09:57:30 Disarmed PackTemp: h 17C, l 16C, PackSOC: 88%, Vpack:112.032V, MotAmps: 0, BattAmps: 1, Mods: 11, MotTemp: 29C, CtrlTemp: 17C, AmbTemp: 11C, MotRPM: 0, Odo:10467km
06959 01/21/2020 09:57:45 DEBUG: Module scheme changed from Stopped mode to Running mode
06960 01/21/2020 09:57:45 DEBUG: Module mode Change Does Not Require Disconnect
06961 01/21/2020 09:58:30 Riding PackTemp: h 17C, l 16C, PackSOC: 88%, Vpack:111.090V, MotAmps: 121, BattAmps: 40, Mods: 11, MotTemp: 26C, CtrlTemp: 18C, AmbTemp: 10C, MotRPM:1235, Odo:10467km
06962 01/21/2020 09:59:30 Riding PackTemp: h 17C, l 16C, PackSOC: 88%, Vpack:111.936V, MotAmps: 0, BattAmps: 1, Mods: 11, MotTemp: 30C, CtrlTemp: 18C, AmbTemp: 10C, MotRPM: 0, Odo:10468km
06963 01/21/2020 10:00:30 Riding PackTemp: h 17C, l 16C, PackSOC: 87%, Vpack:111.590V, MotAmps: 0, BattAmps: 1, Mods: 11, MotTemp: 30C, CtrlTemp: 19C, AmbTemp: 10C, MotRPM:2467, Odo:10468km
06964 01/21/2020 10:01:30 Riding PackTemp: h 17C, l 16C, PackSOC: 86%, Vpack:110.521V, MotAmps: 0, BattAmps: 3, Mods: 11, MotTemp: 33C, CtrlTemp: 22C, AmbTemp: 10C, MotRPM:3832, Odo:10469km
06965 01/21/2020 10:02:30 Riding PackTemp: h 17C, l 16C, PackSOC: 84%, Vpack:109.103V, MotAmps: 44, BattAmps: 34, Mods: 11, MotTemp: 38C, CtrlTemp: 22C, AmbTemp: 10C, MotRPM:3076, Odo:10471km
06966 01/21/2020 10:02:37 INFO: Max allowed voltage difference is 500mV
06967 01/21/2020 10:03:30 Riding PackTemp: h 17C, l 16C, PackSOC: 85%, Vpack:110.613V, MotAmps: 0, BattAmps: 1, Mods: 11, MotTemp: 38C, CtrlTemp: 22C, AmbTemp: 10C, MotRPM:1111, Odo:10471km
06968 01/21/2020 10:03:53 Throttle Disabled: Kickstand Sw,
06969 01/21/2020 10:03:53 DEBUG: Module scheme changed from Running mode to Stopped mode
06970 01/21/2020 10:03:53 DEBUG: Module mode Change Does Not Require Disconnect
06971 01/21/2020 10:03:55 Power Off Key Switch
06972 01/21/2020 10:03:55 Sevcon Turned Off
06973 01/21/2020 10:03:55 Module 00 Opening Contactor vmod: 110.770V, batt curr: 1A
06974 01/21/2020 10:03:55 Module 01 Opening Contactor vmod: 110.756V, batt curr: 0A
06975 01/21/2020 10:03:55 INFO: Disabling External Chg 0 Charger 2
06976 01/21/2020 10:03:55 INFO: Disabling External Chg 1 Charger 3
06977 01/21/2020 10:03:55 Turning OFF DCDC. Flags: 0x00
06978 0 DEBUG: Reset: Power-On
06979 0 Power On Key Switch
06980 0 Key On
06981 0 DEBUG: Module scheme changed from None mode to Running mode
06982 0 Module 00 Opening Contactor vmod: 0.000V, batt curr: 0A
06983 0 Module 01 Opening Contactor vmod: 0.000V, batt curr: 0A
06984 0 Turning ON DCDC
06985 0 Module 00 CAN Link Up
06986 0 Module 00 Registered serial: 17tb1038, vmod: 111.283V
06987 01/21/2020 10:12:42 Module 01 Registered serial: 18sg0107, vmod: 111.074V
06988 01/21/2020 10:12:42 Module 01 CAN Link Up
06989 01/21/2020 10:12:42 Sevcon Turned On
06990 01/21/2020 10:12:42 DEBUG: Module scheme changed from Running mode to Stopped mode
06991 01/21/2020 10:12:42 DEBUG: Module mode Change Does Not Require Disconnect
06992 01/21/2020 10:12:43 Sevcon CAN Link Up
06993 01/21/2020 10:12:43 DEBUG: Sevcon Contactor Drive ON.
06994 01/21/2020 10:12:43 Module 00 Closing Contactor vmod: 111.302V, maxsys: 111.302V, minsys: 111.048V, diff: 0.254V, vcap: 98.937V, prechg: 88%
06995 01/21/2020 10:12:44 Module 01 Closing Contactor vmod: 111.071V, maxsys: 111.339V, minsys: 111.071V, diff: 0.268V, vcap: 111.687V, prechg: 100%
06996 01/21/2020 10:12:44 DEBUG: Module 00 Contactor is now Closed
06997 01/21/2020 10:12:44 INFO: Enabling External Chg 0 Charger 2
06998 01/21/2020 10:12:44 INFO: Enabling External Chg 1 Charger 3
06999 01/21/2020 10:12:44 DEBUG: Module 01 Contactor is now Closed
07000 01/21/2020 10:12:51 Disarmed PackTemp: h 17C, l 16C, PackSOC: 85%, Vpack:111.242V, MotAmps: 0, BattAmps: 1, Mods: 11, MotTemp: 29C, CtrlTemp: 17C, AmbTemp: 11C, MotRPM: 0, Odo:10472km
07001 01/21/2020 10:12:57 DEBUG: Module scheme changed from Stopped mode to Running mode
07002 01/21/2020 10:12:57 DEBUG: Module mode Change Does Not Require Disconnect
07003 01/21/2020 10:13:52 Riding PackTemp: h 17C, l 16C, PackSOC: 85%, Vpack:111.191V, MotAmps: 0, BattAmps: 1, Mods: 11, MotTemp: 29C, CtrlTemp: 17C, AmbTemp: 10C, MotRPM: 0, Odo:10472km
07004 01/21/2020 10:14:52 Riding PackTemp: h 17C, l 16C, PackSOC: 84%, Vpack:106.944V, MotAmps: 126, BattAmps: 148, Mods: 11, MotTemp: 32C, CtrlTemp: 21C, AmbTemp: 10C, MotRPM:4277, Odo:10472km
07005 01/21/2020 10:15:52 Riding PackTemp: h 18C, l 16C, PackSOC: 82%, Vpack:109.100V, MotAmps: 0, BattAmps: 1, Mods: 11, MotTemp: 38C, CtrlTemp: 22C, AmbTemp: 10C, MotRPM:3730, Odo:10474km
07006 01/21/2020 10:16:52 Riding PackTemp: h 18C, l 16C, PackSOC: 80%, Vpack:105.912V, MotAmps: 113, BattAmps: 139, Mods: 11, MotTemp: 40C, CtrlTemp: 22C, AmbTemp: 10C, MotRPM:4468, Odo:10476km
07007 01/21/2020 10:17:52 Riding PackTemp: h 18C, l 17C, PackSOC: 79%, Vpack:106.011V, MotAmps: 112, BattAmps: 130, Mods: 11, MotTemp: 42C, CtrlTemp: 22C, AmbTemp: 9C, MotRPM:4043, Odo:10478km
-
Here's the event in question for sure, and there's also a kickstand switch entry which I think is pretty definitive:
I don't care what anybody says, I hate that thing.
-
So the problem is a flaky side stand switch? It sure doesn't cause a problem very often - yet. It is strange that Zero didn't pick that up when they reviewed my logs. Thanks, Brian for decoding the logs. :)
I wonder if the switch was affected by me riding on wet streets, which I was doing shortly before the problem? I think I had better give it a look-see and clean and lubricate the switch with WD-40. I haven't looked at it since I bought the bike over 2 years ago.
The side stand switch on my Royal Enfield was removed almost immediately upon the bike's purchase as they are of such poor quality that they can cause the bikes to stall as you leave the dealer. :o
BTW, I just realized that the date of my power interruption was 1-28-20. I did ride my bike on 1-21-20, but didn't notice any problem during that ride and the weather was dry that day. ???
-
The log entry 06968 appears normal since 2 seconds after the side stand is put down the key is turned off. There are 32 instances like that since September.
However, there are 7 instances where Kickstand events are not followed by Key Off events. They look like Riding -> Kickstand -> Stopped -> Running -> Riding. Now I suppose these could be part of some normal scenario as well. The time between Stopped to Running varies from 15 seconds to a minute. Maybe Richard is picking up the mail or something, but the distance ridden varies.
ENTRY DATE KEY ON KICKSTAND TIME INTO RIDE
00191 09/17 09:00:09 09:03:11 3min/before first km
01443 10/08 08:07:04 08:10:10 3min/1km into ride
01646 10/11 08:13:23 08:16:16 3min/1km into ride
03026 11/02 12:10:04 12:15:38 5min/3km into ride
04277 11/26 09:05:32 09:05:45 0min/before first km
04484 11/28 08:23:05 08:26:40 3min/2km into ride
07139 01/27 10:31:26 10:33:37 2min/2km into ride
Example from 04484:
04482 11/28/2019 08:25:14 Riding PackTemp: h 14C, l 14C, PackSOC: 99%, Vpack:113.321V, MotAmps: 131, BattAmps: 56, Mods: 11, MotTemp: 23C, CtrlTemp: 17C, AmbTemp: -1C, MotRPM:1616, Odo: 9912km
04483 11/28/2019 08:26:14 Riding PackTemp: h 14C, l 14C, PackSOC: 99%, Vpack:115.081V, MotAmps: 0, BattAmps: 1, Mods: 11, MotTemp: 24C, CtrlTemp: 16C, AmbTemp: -1C, MotRPM:1674, Odo: 9913km
04484 11/28/2019 08:26:40 Throttle Disabled: Kickstand Sw,
04485 11/28/2019 08:26:40 DEBUG: Module scheme changed from Running mode to Stopped mode
04486 11/28/2019 08:26:40 DEBUG: Module mode Change Does Not Require Disconnect
04487 11/28/2019 08:26:56 DEBUG: Module scheme changed from Stopped mode to Running mode
04488 11/28/2019 08:26:56 DEBUG: Module mode Change Does Not Require Disconnect
04489 11/28/2019 08:27:14 Riding PackTemp: h 14C, l 13C, PackSOC: 99%, Vpack:113.751V, MotAmps: 78, BattAmps: 44, Mods: 11, MotTemp: 25C, CtrlTemp: 17C, AmbTemp: -1C, MotRPM:2082, Odo: 9913km
04490 11/28/2019 08:28:14 Riding PackTemp: h 14C, l 13C, PackSOC: 98%, Vpack:113.084V, MotAmps: 158, BattAmps: 45, Mods: 11, MotTemp: 30C, CtrlTemp: 19C, AmbTemp: -1C, MotRPM:1023, Odo: 9914km
04491 11/28/2019 08:29:14 Riding PackTemp: h 14C, l 13C, PackSOC: 98%, Vpack:114.608V, MotAmps: 0, BattAmps: 2, Mods: 11, MotTemp: 28C, CtrlTemp: 17C, AmbTemp: -1C, MotRPM:2499, Odo: 9915km
-
Richard has to weigh in here to interpret these. I looked at the time period referenced and the length of time involved.
I missed the 2 second gap, but the fact that the bike was restarted after another 9 minutes suggests it was a trouble stop and not intentional.
This is one reason why having Zero customer service be the sole interpreter of the logs is flawed. The rider knows what was happening when, and logs are only software event triggers which could have any number of causes.
-
remembering the ODO reading on the dash when such an event happens would help tremendously as this narrows the search to just a few lines in the log.
-
remembering the ODO reading on the dash when such an event happens would help tremendously as this narrows the search to just a few lines in the log.
That is good advice and I will try to do that if the problem occurs again. (I will off on a ride to visit my daughter today and will look for any issues during my trip.)
The only time that I can think of when I leave the ignition on during a ride while the side stand is down is when I stop by a mail box to mail a letter. However, it is true that upon returning home after a ride I will stop the bike and extend the side stand with the ignition on while I zero out my trip meter. That could take about a minute or two as I struggle to push the button and wait for the zero to appear. ::)
I never have had a "trouble stop", but visiting the post office, picking up a newspaper from a rack, or doing something else like that could take a short period of time like 9 minutes. The reason that I really like my Zero is that I can take short trips here and there without worrying about discharging the battery or not warming up the oil of my ICE vehicles. :)
So far the only thing typical about the momentary stalling that I have experienced is that it occurs a few seconds after slowly leaving a stop at a speed of about 10 mph. Sometimes it happens a few minutes into my ride with the SOC reading 100% and sometimes later in the ride with the SOC around 90% (to the best of my recollection). I can't recall it ever happening when the SOC was below 90%, if that means anything. ???
Right now I believe that we have likely sucked as much information out of my logs regarding this incident as possible. From now on I intend to be more watchful about any further power disruptions (if any) and if it happens again I will download the logs and either post here again or start another thread, whichever you think would be best.
-
I think anytime we can come together to learn more about how logs can inform our rides is a good thing. That being said, one thing to look out for in the logs is the event trigger for your ignition switch in the middle of a ride. I posted a thread about a similar result, a momentary loss of power, but mine is potentially my ignition cable going bad. It’s intermittent so a little difficult to track, and it hasn’t happened in days. But does your power cut out pulling away in a straight line or on a turn? Mine does it on a slight turn, and the semi-consensus is the ignition cable can get trapped between the steering head and the frame, pinching it. Eventually it’ll cause enough damage to stop it from working.
-
I think anytime we can come together to learn more about how logs can inform our rides is a good thing. That being said, one thing to look out for in the logs is the event trigger for your ignition switch in the middle of a ride. I posted a thread about a similar result, a momentary loss of power, but mine is potentially my ignition cable going bad. It’s intermittent so a little difficult to track, and it hasn’t happened in days. But does your power cut out pulling away in a straight line or on a turn? Mine does it on a slight turn, and the semi-consensus is the ignition cable can get trapped between the steering head and the frame, pinching it. Eventually it’ll cause enough damage to stop it from working.
It always happens in a turn from a stop, both a left an right turn. So you may be on to something there. One more thing to check out. Are you talking of the wires leading to the ignition switch? That has been a problem on a some ICE bikes for years when they get some miles on the clock. The older they get the more likely something like that may show up. Thanks for the comment.
I rode 80 miles today without a problem.
-
Yes exactly!! In a pull away slight turn. At least I’m not alone there. The big difference is your log specifies kickstand switch, mine says ignition switch. Probably little change they’re wired through the same nexus of the wiring harness, but it’s possible that will become more of a weakness as our bikes enter decade 2+ of service.
-
......
It always happens in a turn from a stop, both a left an right turn. So you may be on to something there. One more thing to check out. Are you talking of the wires leading to the ignition switch? That has been a problem on a some ICE bikes for years when they get some miles on the clock. The older they get the more likely something like that may show up.
..........
This (intermittent loose wire @ ignition switch) happened to my 03 BMW RT.
Wire loom was installed with too many zip ties that resulted in a conductor severing resulting in intermittent excitement :o
-
That's an interesting hypothesis. The OP is testing the kickstand switch weather protection per his other thread, but harness tugging is a type of investigation we haven't really firmed up yet.
-
That's an interesting hypothesis. The OP is testing the kickstand switch weather protection per his other thread, but harness tugging is a type of investigation we haven't really firmed up yet.
I did check my ignition wires and didn't notice any problem or stress on the switch wires when the forks were turned side to side.
-
Lately I have experienced a momentary power interruption every now and then when accelerating from a stop. There is seems to be no obvious pattern to the issue, other than it happens when leaving a stop and when my speed is about 10 mph. It happens perhaps every fifth ride and only lasts a for a fraction of a second. I originally thought that my glove was slipping on the throttle grip and that was causing the problem. But today I am pretty sure that my glove did not slip when it happened again. No big problem as long as it doesn't get worse. Today I was riding in light rain when it happened, but I did that yesterday and didn't experience the "glitch". Anyone have any thoughts? ???
You may wish to check the kickstand sensor. Sounds like it may be jostled by the weight of the kickstand moving during initial acceleration.
-
Lately I have experienced a momentary power interruption every now and then when accelerating from a stop. There is seems to be no obvious pattern to the issue, other than it happens when leaving a stop and when my speed is about 10 mph. It happens perhaps every fifth ride and only lasts a for a fraction of a second. I originally thought that my glove was slipping on the throttle grip and that was causing the problem. But today I am pretty sure that my glove did not slip when it happened again. No big problem as long as it doesn't get worse. Today I was riding in light rain when it happened, but I did that yesterday and didn't experience the "glitch". Anyone have any thoughts? ???
You may wish to check the kickstand sensor. Sounds like it may be jostled by the weight of the kickstand moving during initial acceleration.
That is possible, but I doubt it. I checked the kickstand and it seems to have enough spring tension to keep that from happening.