Search the Community

Hi guys, After having an EUC for 3 years, I still have bits to learn. I currently have my first wheel; MSuper V3 and my current wheel; MSX. I have my first two alarms and tiltback disabled on my MSX and haven't taken it to top speed at all, therefore, I haven't heard the warning beeps for my last alarm. What I was wondering is at 100 percent battery, it's possible to hit the last alarm at say 30mph (Not sure what it's set by default) and slow down, but if I had say 50 percent battery, would the alarm still come on at 30mph or relevant to the output power, warning you from overpowering? Is it just speed based alarms? Will the wheel allow you to overpower it, or will it always beep depending on what output it's giving? How do you know how much power output you have left, relevant to what battery percentage you have left? It's really hard to write what I'm asking haha, hopefully it comes across okay and someone can give me a solid answer. The scenario is, when I'm riding at full battery, I'm not concentrating fully on speed as I know the alarm will sound if I go too fast, whereas when the battery power is lower, I take note and slow down as I don't want to Overpower the wheel and not hear an alarm. I'm hoping the last alarm sounds when you're close to maximum output and not a set speed. If this wasn't the case, riding at 40 percent battery would be really dangerous as the wheel has less to give and possibly not even reach the speed your alarm is set at. Please can someone firstly fathom out what I'm trying to say and possibly come up with a clear answer! Thank you! Liam.

Lot of us had face plants in this forum. New and experienced. Some of them got seriously injured. I'm wondering if all of them recovered well and riding again. Generally we get posts soon after the unfortunate incidents but after that we don't hear from them again. I'm just curious to know if they still love EUCs.

Hi guys, I've just experienced my second shut off last week. I started the day full charged. Rode about 10miles (16km). Then I put the EUC on charge only for about 15min.(usually 99% of time I let it change completely). After that I went ridding for 1.5 miles (2.5km). I stopped for 30 min. Rode again for 1 mile(1.6km) when I passed over a small 2 inch(5cm) sidewalk, I went for another 3 feet(1m), I heard a bip and it shut off. The EUC just shut off no beeping on the ground. Luckily my speed was about 3-4mile/h (5-8km/h) when it happened. I turned the EUC back on and it worked, voltage was around 55. I still ride it, I don't feel any difference in behavior, it's running normal. But I don't feel save anymore. I will attach below my black box data the status highlighted in yellow shows the moment when the cut off occurred. I have had a motor replacement before at ~80 hours in. Since then I can see: ??(Controller) 218h 17m 21s 3 861 Hall1Òì³££¬Òì³£´ÎÊýΪ861 don't recall that something happened here ??(Controller) 386h 0m 39s 3 5506 Hall1Òì³££¬Òì³£´ÎÊýΪ5506 don't recall that something happened here ??(Controller) 497h 4m 24s 3 997 Hall1Òì³££¬Òì³£´ÎÊýΪ997 - this is where I experienced the shut off and lots of 17 code - which is an abnormal behavior of the motor but may be as a warning and doesn't trigger a shut off like 3s do ? "3" seems to be related with the Motor; What 861, 5506, 997 mean? Translated some of the last black box logs, the occurring frequency is quite often : ??(Controller) 472h 55m 44s 17 11620 Hall 1 signal is abnormal, the cumulative number of abnormalities is 45, and the abnormal condition is 6->4 ??(Controller) 482h 0m 0s 17 11841 Hall 1 signal is abnormal, the cumulative number of abnormalities is 46, and the abnormal condition is 4->1 ??(Controller) 482h 3m 18s 17 11796 Hall 1 signal is abnormal, the cumulative number of abnormalities is 46, and the abnormal condition is 1->4 ??(Controller) 482h 55m 19s 17 11875 Hall 1 signal is abnormal, the cumulative number of abnormalities is 46, and the abnormal condition is 6->3 ??(Controller) 485h 21m 53s 17 11825 Hall 1 signal is abnormal, the cumulative number of abnormalities is 46, and the abnormal condition is 3->1 ??(Controller) 497h 4m 24s 3 997 Hall1 exception, the number of exceptions is 997 ??(Controller) 497h 4m 24s 17 12128 Hall 1 signal is abnormal, the cumulative number of abnormalities is 47, and the abnormal condition is 6->0 ??(Controller) 498h 34m 22s 17 12050 Hall 1 signal is abnormal, the cumulative number of abnormalities is 47, and the abnormal condition is 1->2 ??(Controller) 505h 2m 5s 17 12065 Hall 1 signal is abnormal, the cumulative number of abnormalities is 47, and the abnormal condition is 2->1 ??(Controller) 519h 33m 6s 17 12068 Hall 1 signal is abnormal, the cumulative number of abnormalities is 47, and the abnormal condition is 2->4 Did anyone experienced this? Thanks everybody for reading this! Chris BlackData_2018-08-24-18-24-24_Fomart.csv

Has anyone ever practiced for a Power Shut Off? I understand the illimitable scenarios associated with riding that would make it virtually impossible to practice a cut off for every angle, slope, incline and speed encountered when riding but it would be nice to have some form of game plan second natured in my head if the need ever arises. I've had 2 engine cut offs when flying helicopters. The maneuvers to land in these situations was imprinted in my subconscious after repetitive practice. Both choppers sustained heavy damage upon landing but at least I walked away. I would love to practice for a EUC shut off if there is a sound method out there. Thanks!

Can this design be improved some how more elegantly to our regular EUCs? So, that extra small wheel prevents the main wheel to sink in, in case of sudden motor cut offs. So in regular usage it is 2 inches above the ground. When the motor cut off, the main wheel tilts forward making the small wheel touch the ground. I guess there still will be a great sudden jerk but hopes to safely jump off the wheel. I know it's not a great solution ( unless you ride in a strait line) but throwing the idea anyways.

In other post I've read that 1.2.2 had no issues with random cut off's and at the time my software was at 1.2.6 and I was experiencing random cut off's for no reason with plenty of battery life to spare going slow and going fast the unit would randomly turn off and send me flying forward. I am currently running the 1.3.0 software and have again experienced random cut off at around 40% battery life and at varying speeds. What do you guys think? Is it my specific unit or is it a problem that's bigger like the software or at the manufacturing?