Jump to content

Search the Community

Showing results for tags 'cutoff'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • General Electric Unicycle Forums
    • Forum Rules (and topics relating to this forum)
    • General Discussion
    • Reviews
    • Mods, Repairs, & DIY
    • Riding Safety and Protective Gear
    • Local Group Meet Ups
    • Private Sales (secondhand)
    • Commercial Advertisements & Deals
    • Off Topic Discussion
  • Brand-Specific Forums (euc only)
    • Airwheel
    • Firewheel
    • Gotway
    • Inmotion
    • IPS
    • King Song
    • Ninebot
    • Rockwheel
    • Solowheel
    • Uniwheel
  • One-Wheeled Skateboards
    • One-Wheeled Skateboards
    • Advertisements (One-Wheeled Skateboards)
  • Two-Wheeled Self-Balancing PEVs
    • Hoverboard
    • Ninebot Mini, Segway MiniPRO, Xiaomi Mini, Airwheel S8 or equivalent
    • Segway (or equivalent)
    • Advertisements (Two-Wheeled Self-Balancing)
  • Non-Self-Balancing PEVs
    • e-Scooters
    • Other Non-Self-Balancing PEVs

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 6 results

  1. 5 reported accidents so far. my friend included. 20 ish kmh on flat road and the wheel just cut power after a few seconds with on and off. his face is not pretty right now. Could everyone with the same batchnumber report in and also if you had a problem. thanks Moderator notice, June 24th 2017: Apparently motorcode is not a reliable way to know if your wheel is affected, the motors might have numbers going back to 2016 (like 1608) and still be affected. Basically if you've bought an MSuper, ACM (and/or maybe Monster) since sometime in start of May 2017, your wheel might be affected. You need some other way to establish when the wheel was built, apparently there's another code somewhere, maybe on the box it was shipped with. 1705 (2017 05, 2017 May) seems to be the magic number, basically any way to make sure that your wheel was or wasn't built after beginning of May. So far it appears that the software goes haywire after riding over a bump. For some riders, this has happened at low speeds, but others report it only occurring at high speed. The wheel is reported to start oscillating back and forth and cut out soon after (maybe in a matter of <0.5 seconds), leading either to crash or the rider jumping off. There seems to be no warning before it happens. Gotway claimed the problem was solved and sent out new replacement boards that should have been OK. That was not the case, the problems still seems to remain, only maybe with higher speed now? At the time of this writing, apparently even brand new wheels still have the issue. Suggesting everyone with the affected wheels to stay off them until Gotway has fixed the firmware for sure, and your dealer gets the equipment and the binaries required to flash a fixed firmware to the board (or new boards with new firmware). This video was shot by @Marty Backe with a board that was supposed to be fixed:
  2. volavoile

    Safety speed with your EUC

    Hello, French Wheeler, but not as good as some other, I had a bad accident (broken shoulder, now with some metal!!) with my small ninebot one E+... and I spent some time in order to understant why we face cut out or accidents. So, on the forums, I could recognize 4 kind of accidents : 1- Pilot did ignore alarm.... nothing to say.... too optimistic, 2- driving accident (bumps....), 3- Sudden cut off.... (looks like my accident, but I'm not sure it wasn't a technical failure), 4- Technical failure. Rare since construcors did improve the safety...or correct bugs (BMS for instance). For the point 3, I did some calculation, that shows that specification of constructors seems to be far too optimistic, and the speed alarm does not consider the wheight of the pilot... which has a huge impact. What I did consider is a common case of accident : you run on flat road, no alarm, straight... and you have a small slope (not big, couple of meters long!). So immedialtely, since you do not consider you have to slow dow, your Wheel has to give all power in order to maintain the speed during the slope. In this condition, considering a 10% slope (not big at all, it is a 6° angle road), what is the maximum speed you can run? I did consider air drag, which has a big influence over 30 km/h), the solpe that I consider as a safety margin, and the wheight of the pilot. The power was considered as constant whaterver the speed is (optimistic), and, since nobody know the duration of the peak's power, 0,5 second for this peak (which is only use for bumps in fact!). Yield of the Wheel in order to transform electrical energy to mechanical energy is estimated at 75% (tests on some gotways). What do we calculate show that with a 500 W, at 25 km/h, you're not save at all... except if you are a kid. On a gotway ACM our MS3, 45 km/h is not a realistic speed since air drag consume most of the power... What do you think? Conclusions : - Power, and slow speed is the key for safety... - Adapt speed limit cosidering your wheight, - If you want to keep the hight speed limit, go quiet, and in all case, use protections!!! Of course, this is only my caclulation, an you can disagree! EUC safety speed.xlsx
  3. Firmware Issue 1.1.6 WARNING, NOT SAFE! CUT OFF if feet leave fotplates (see Yourube videos at bottom) Here is the list so far, PLEASE if anyone can do the "footplate test" (as on first video) on mainboard 1.1.7 and report if issue is solved. I would like to update mostly for the BMS, but I dont dare if the unsafe behaviour is still there. Lift vehicle while pressing on foot plate, wheels should spin as its lifted. Then release foot plate pressure. Wheels SHOULD free wheel to a stop - NOT STOP INSTANTLY by breaking like in 1.1.6 video. FW marked with * is the one I have now and includes my comments, other FW comments are from FW update screen *mainboard 1.0.8 - GOOD/SAFE, no cutoff if foot removed with wheels spinning (when off ground) - PROBLEM, adjusting steering sensitivity and ride sensitivity during an active ride, sent mine into steering freak mode and after stopping it was locked into left turn (constant turning). Turn back to "auto mode" again at standstill - problem solved, Now it can once again be set manually for sharper control (or softer if one likes that) - PROBLEM, tiltback and alarm at 19km/h in app - PROBLEM, 19-20km/h in app = 16km/h real speed (GPS show 16 when pushing it constantly) mainboard 1.1.6 WARNING, NOT SAFE! CUT OFF if feet leave fotplates (see videos below) mainboard 1.1.7 Optimized uplsope performance Optimized alarm in slope Other small known bugs MY WARNING - UNKNOWN IF SAFETY ISSUE FROM 1.1.6 IS RESOLVED *BLE 1.0.0 Ocasinal problems at "search again" (Huawei P8) BLE 1.0.1 IOS11 bluetooth connection fix *BMS 1.1.8 No known/noted yet BMS 1.2.0 Optimized cell balance function *Co-control 1.0.6 A bit confused when starting "not facing" remote Co-control 1.1.4 New function: - Optimized follow me performance *Follow 1.0.0 None noted, see co-control 1.0.6 Follow 1.0.X NO UPDATE AVAILABLE (have it been included in co-control in latest FW?) *Remote 1.0.3 None noted, remote and phone both work fine to remote control Remote 1.0.4 New function: - Fix that remote sometimes cant be charged - Optimize indication of remote control battery volume (level?) Gimbal N/A (dont have one) Likely this one also suffers from 1.1.6 FAST FORWARD to 00:20 for crash
  4. Oswald Valentine-Lopez

    Cutoff, but why?

    So I was headed home afterwork and took a detour to grab a drink before I got home. Luckily from work to home is only a 10 min ride max. Why is that luckily? At night I ride in the road because it's not as unridable as the sidewalk (ironically) plus at around 11 at night, not many people are on the road. Well there was a car coming up behind me so I usually ride into the shoulder till they pass, but there was a fairly large puddle (it was raining still) I barely saw and ended up riding through. About a minute later, I got the tiltback warning (which I assume was me reaching top speed like always, yes I need a faster wheel, haha), began to slow down and recover cruising when the wheel performed an action like it was confused adjusting to normal riding then giving me a tiltback feeling very rapidly within 3-4 seconds before it cut off and I safely ran off it. I was devistated afterwards when I picked up my wheel to find it wasn't turning on. I had just replaced a tire after procrastininating for weeks so it felt like i was wheel less again. After walking about 10 minutes back to my house, I sat it next to a heater for a few minutes than thought to try charging it and lo and behold it powered up once I plugged it to the wall. Battery level was the same and everthing works like before. Weird experience. Thought it's worth sharing.
  5. Wondering if any 9 Botters experienced the crash while they had the trolley handle on the wheel. I plan to buy one but because of the protruding design I'm hesitant to buy... Do you think it is likely to survive in the crash?
  6. johnc415

    KS GW cutoff

    Hi, I'd like to pose a question to those familiar with or have technical expertise on motor/battery engineering - while the "official" word is that KS units do not cut off when pressed past their speed max/battery output, has anyone tested this theory? When I asked GW about their lack of this feature, per the GW rep, there is no such thing as an EU that does not cutoff after exceeding max speed/battery output. While the pedal-rising feature may discourage further pursuit of higher speeds, it doesn't guarantee the KS units have a smart feature built in to prevent cutoff. I just want to clear up any misinformation that may be present - currently what I have to go off of is GW rep vs KS rep but we all know that testing it is the only true way to find out - or thru understanding how these motors/batteries work. Per GW rep, the new units will have an optional pedal-rising feature selected via their app - this was intentionally done for a couple reasons: in a situation where high speeds are reached and a cutoff is imminent, flat pedals are actually better than rising pedals for a user to bail. Either way, it won't be pretty but the idea is that should your feet be in an angle due to rising pedals, you can't jump off. Another reason: if you practice safe driving near the max speeds, you don't have to worry about the annoyance of the rising pedals. Having the option I think seems the best of both worlds. Not saying that beeping isn't annoying, bc we know it sure is!
×