Thrown off after nosedive with no pushback warning (nose dive, nose-dive)
poopmonkey Banned last edited by
@thegreck I feel you I'm just commenting on the video he posted it doesn't look like he did anything wrong albeit in a video it's hard to tell.
SeaP90d last edited by
Well said, thegreck, the only thing I'd add is it that it's happened once (but only once) to everyone here, and although we haven't definitively figured it out, it seems to be some combination of using the "classic" mode, going up hill, and we're thinking a barely perceptible bit of heel lift. One thing that seems to happen with everyone who's had this happen and then gets more experience is that in addition to no more classic mode, they perfect a loose ankle stance that keeps their feet soles firmly planted to the deck regardless of the board/body angle.
@SeaP90d Totally agree! I think they should get rid of Classic shaping because it just seems dangerous!
Luckily, I was reading the forums for 2 months while I waited for my board to arrive (those were the days!), and had already read many horror stories about Classic mode, so to this day I've never ridden in anything but Extreme.
Eliminating Classic mode, every board sport that's worth a damn has a learning curve, and they all have an element of risk. Without it, where would the fun be? Most surfers at some point have been gashed by their fins, but you'll never see them removing them.
ted last edited by ted
@SeaP90d You are right on about classic mode. But I wish you were right about the "only once" part. :) Took me several face-meets-asphalt before I moved out of classic. All good since then.
@thegreck It has taken me a while to fully understand your point about remaining centered over the board and using your feet (not weight shift) to change the angle of the board to accelerate/decelerate. I think its an important point that probably gets missed. When I am not carving, its relatively straight forward to accelerate/decelerate without shifting my weight. But, when carving aggressively, I find that I have to resist the temptation to shift my weight forward through a carving-turn.
(warning to OWers who also surf: the instinct to lean forward to generate speed by using the ramp of the wave is a quick ticket to the asphalt on a OW. OW riding can feel "surfy" sometimes but using the same instinctive moves that we use surfing will cause impact.)
coryg last edited by
@DavidJohn this happened to me too. I was starting up a small hill with a slight incline. I leaned forward to accelerate and the wheel locked up on me and fell forward landing on my shoulder. When I got up I tried to rotate the tire but couldn't. It was locked up so I turned to power off and back on again and tire was able to rotate. I think I just need to not lean forward as much to accelerate, especially starting up an incline. Any advice would be appreciated. Thanks
@coryg The tire doesn't rotate freely when the Onewheel is powered on, that's normal (otherwise you'd start rolling when you tried to mount it). If you have trouble riding uphill without hitting the nose of the board on the ground, try switching to Elevated mode, which will automatically lift the nose a few inches to give you more clearance in hilly areas.
wheeler last edited by
I wont ride in extreme anymore. They need to put pushback at 12 mph. Too dangerous
TonyGDTLA last edited by
@wheeler no it is not dangerous. Don't accelerate too fast. Be patient and let the machine work the way it is intended. The classic modes push black is WAY more dangerous cause I always went past it. Then felt like was losing control. But I learned to let the board rebalance on its own.
Subterfuge last edited by
I can understand if FM doesn't want to give rider's access to OWs sensor logs. But I would feel better knowing that logs were being collected for analysis by FM as the user-base grows and ride-miles accumulate. Many apps ask if logs can be transmitted back to HQ for analysis and I usually couldn't care less. This sounds like one app where the user-base would be really happy for their ride logs to be used to improve the experience.
kwatts last edited by
@Subterfuge and everyone else that this happened to -
I created an app for Android that will log all the stats to a file, it should help us get to the bottom of this. It's at https://play.google.com/store/apps/details?id=net.kwatts.powtools
Added stats include the sensor pads that are engaged and tilt/yaw/etc of the onewheel, current amps, etc. The app also displays all of these in one screen (and has buttons to set the ride mode and lights). I was riding and logging the other day and got the nosedive, stats showed going around 7 mph and both pads not engaged, although there wasn't a big spike in amps. Not enough data yet to figure out what is going on, but something is.
Hey, can you add a battery alert to your app? Something like @50% vibrate.. 😀
Tartopom last edited by
Seems an interesting app :-P can you just select the different mode or even create a new one? :-P
Cool how the app shows total miles and hours, kinda surprised I'm only at 250 miles, 1200 hours..
SeaP90d last edited by
kwatts, you are the greatest, maybe put your forensic nosedive app on a new thread so everyone sees it?
parrothd last edited by parrothd
That app is pretty useful..
Originally I thought the foot sensors were some sort of field sensing. They're actually pressure sensitive pads and only respond to pressure in a area 1in x 4in(parallel to the wheel) area per sensor. Explains why flat shoes are the best and how easily you can lose contact with them and nose dive...
The graphics on the sensor pad a very misleading, the sensor area is small and in the center only..
kwatts last edited by kwatts
@parrothd - Nice! You know, i was thinking of doing a red/green for the pad sensors, will use your findings to help put the location and scale. I'll also look into doing the battery alert for the next rev, thanks for the suggestion!
@tartopom - It looks like for "Riding Mode" only three settings would stick and ones we already know (1 - classic, 2 - extreme, 3 - climb/nose up). There are some unknown bluetooth/BLE characteristics that might be there for writing ride mode settings, hard to know what to send etc without documentation.
All - There are other attributes that I didn't display in the app, let me know any of these would be of interest and I'll put them in the next rev,
- Safety Headroom (some #, didn't really change, no idea what it is?)
- Trip regen and total amp hours (regen is amps that were regenerated from going downhill etc)
- icsu and icsv faults (?)
- if OW is charging (t/f although never seemed to change)
- battery low flags at 5% and 20% (will add this in per @parrothd request)
I'll also plan to add tasker integration.
Battery alert at %50 or whatever level you want would be awsome! I'm always worried on my trips I'm not gonna make it back.. Lol..
@kwatts Safety headroom?? Be interested to find out what that one is.
dcosmos last edited by
@kwatts Would you mind making an IOS app? I'd love to have this data, especially total miles and hours.