A whoop racing buddy sent me a link to this, and I have to send a big THANK YOU for the info! Your idea will likely save me from adding 10sec to a lap due to messing up in the heat of the moment. I'm now at the drawing board untangling the logic needed to make this even better. My idea is to make a true "1 touch turtle"... no disarm/rearm required. The idea is after crashing, don't even disarm... just hold the button to flip it, and let go to get back in the race. I also want to add something that takes care of not having throttle low. Of course, I'll share if/when I get it all working.
That would be cool if you could make that. I do know Betaflight will require the disarm first to enable turtle mode but it could be automated with a Lua script but this is only something I heard as a theory... I've yet to see anyone make one work!
AYO!..THANK YOU! I can't stand the turtle mode button dance! That shit takes too damn long and can be confusing when you're panicking! This method is sooooooo much more faster and easier!!! I just lost my quad the other day in a moving truck bed while flying in traffic...couldn't turtle mode quick enough! 🤬😓
I just found this video, nice tip! I was wondering why you jump up to full value for turtle mode, then back down to arm+turtle , effectively sweeping through the arm range before coming back down. Why not reverse that - go to 50 weight first (turtle), delay 0.1, then += another 50 into the higher range for arm+turtle. It just seems more logical that way to me (even if it makes no technical difference), but I can't test it right now. I also wondered about what ViV_fpv suggested (no delay) but still have turtle mode's range in BFLT be lower (start earlier) than the secondary arm range?
The delay is there because on some protocols like Flysky, it won't work. I think on ELRS, this setup isn't necessarily required but I didn't want to make a separate video for each protocol out there. Like I said, there's probably a lot of other ways to get this to work and this is not the only way. If you have a better, easier way to do this, please share with everyone here on the details of the setup, thanks!
@@marblekitfpv Yea I appreciate that explanation. My bad that I said 2 separate things in my comment. My primary point above was the sequencing with the delay. It just seems more logical to step up +50, delay, step up +50. But like you said, there's more than one way and I didn't mean to imply my way is any better :). Thanks for the video. This shortcut was one of those "why didn't I think of that" moments for me!
Great video, I already assign turtle mode to a toggle switch so this method can reduce arm-disarm without less confusion from conventional way. BTW is there any reason to set the arm range in medium value (16xx--1900)? Setting (BF) AUX5 arm range on high value (1900--max), and (controller) AUX5 as SE = max x 0.5, += (0.1sec delay) max x 0.5 seems to work?
Nice tip! Question though, should you use AUX1 to be designated for arming when running ELRS? The site strongly suggest to use AUX1 high as the arm position due to how the software was written for safety and performance. As far as I know, AUX1 was made priority and is sent for every packet going out and is most reliable. I know it might not matter so much in practice, especially for whoops, but am genuinely curious. Happy to be corrected.
That's what the ELRS devs recommend so I'd just go with that. I have been using AUX4 for years now without a single issue with arming/disarming. Perhaps the situation where it would be an issue hasn't come up for me yet.
@@marblekitfpv IIRC from my readings, the main reason to use ch5 is it's supposed to be a 2 position only channel. I have not tried using 5 for proportional or 3-way though, so not sure if that's true, but I've always used 5 for arm/disarm to make sure I have that extra proportional channel if needed for stuff like OSD profile, VTx power, Rate profile, etc.
That delayed negative offset is totally unnecessary. You can get the same effect by setting the same channel range for Turtle and Arm. It's that simple.
@ViV_fpv It might not be necessary if you use ELRS but I think I saw it was needed for other protocols like Frsky or Spektrum. Forgot where I saw this but I think that's why the delay is needed.
This method doesn't work for me. Sometimes it just arms and does not go into turtle mode. Sometimes it just goes into turtle mode without arming. I think that delay is needed because it goes into turtle mode first THEN arms but does it very quickly.
Great tutorial and very detailed. Thanks!
A whoop racing buddy sent me a link to this, and I have to send a big THANK YOU for the info! Your idea will likely save me from adding 10sec to a lap due to messing up in the heat of the moment. I'm now at the drawing board untangling the logic needed to make this even better. My idea is to make a true "1 touch turtle"... no disarm/rearm required. The idea is after crashing, don't even disarm... just hold the button to flip it, and let go to get back in the race. I also want to add something that takes care of not having throttle low. Of course, I'll share if/when I get it all working.
That would be cool if you could make that. I do know Betaflight will require the disarm first to enable turtle mode but it could be automated with a Lua script but this is only something I heard as a theory... I've yet to see anyone make one work!
We need more tutorials that give away ALL the secrets!
You've pissed off the pro tiny whoop racers... now you've done it! ROFLMAO!!
Great Video ,its easy to assume that everyone knows all the little details when you have been immersed in a particular field for years 👍🏻
Awesome tutorial. Would never have thought that was a thing, nor figured it out on my own. Thanks for sharing. 👍😎
Great tutorial, thanks for the video.
WOW Nice switches for me though
AYO!..THANK YOU! I can't stand the turtle mode button dance! That shit
takes too damn long and can be confusing when you're panicking! This
method is sooooooo much more faster and easier!!! I just lost my quad
the other day in a moving truck bed while flying in traffic...couldn't turtle
mode quick enough! 🤬😓
Thanks for the tutorial and all the info, Albert! 😃
Stay safe there with your family! 🖖😊
Where did you get that radio?
I just found this video, nice tip! I was wondering why you jump up to full value for turtle mode, then back down to arm+turtle , effectively sweeping through the arm range before coming back down. Why not reverse that - go to 50 weight first (turtle), delay 0.1, then += another 50 into the higher range for arm+turtle. It just seems more logical that way to me (even if it makes no technical difference), but I can't test it right now. I also wondered about what ViV_fpv suggested (no delay) but still have turtle mode's range in BFLT be lower (start earlier) than the secondary arm range?
The delay is there because on some protocols like Flysky, it won't work. I think on ELRS, this setup isn't necessarily required but I didn't want to make a separate video for each protocol out there. Like I said, there's probably a lot of other ways to get this to work and this is not the only way. If you have a better, easier way to do this, please share with everyone here on the details of the setup, thanks!
@@marblekitfpv Yea I appreciate that explanation. My bad that I said 2 separate things in my comment. My primary point above was the sequencing with the delay. It just seems more logical to step up +50, delay, step up +50. But like you said, there's more than one way and I didn't mean to imply my way is any better :). Thanks for the video. This shortcut was one of those "why didn't I think of that" moments for me!
Great video, I already assign turtle mode to a toggle switch so this method can reduce arm-disarm without less confusion from conventional way.
BTW is there any reason to set the arm range in medium value (16xx--1900)? Setting (BF) AUX5 arm range on high value (1900--max), and (controller) AUX5 as SE = max x 0.5, += (0.1sec delay) max x 0.5 seems to work?
There's probably a lot of different ways that would work.
Good stuff! I've gotten pretty fast with the traditional method, I feel like this would feel weird to me lol
I've been using this method for a few months now and almost can't use the old way anymore. Takes me like 20 seconds on the old way. Haha...
@@marblekitfpv I'll definitely give it a shot!
Nice tip! Question though, should you use AUX1 to be designated for arming when running ELRS? The site strongly suggest to use AUX1 high as the arm position due to how the software was written for safety and performance. As far as I know, AUX1 was made priority and is sent for every packet going out and is most reliable. I know it might not matter so much in practice, especially for whoops, but am genuinely curious. Happy to be corrected.
That's what the ELRS devs recommend so I'd just go with that. I have been using AUX4 for years now without a single issue with arming/disarming. Perhaps the situation where it would be an issue hasn't come up for me yet.
@@marblekitfpv IIRC from my readings, the main reason to use ch5 is it's supposed to be a 2 position only channel. I have not tried using 5 for proportional or 3-way though, so not sure if that's true, but I've always used 5 for arm/disarm to make sure I have that extra proportional channel if needed for stuff like OSD profile, VTx power, Rate profile, etc.
nice idea...
Screw pilots that are trying to hide time saving valuable tips. If they want to win races that badly, they just suck.
That delayed negative offset is totally unnecessary. You can get the same effect by setting the same channel range for Turtle and Arm. It's that simple.
Has something changed recently? When I first set this up about 5 months ago, sometimes it wouldn't arm unless the delay was put in.
@@marblekitfpv I'm not sure! But when I picked up a Pocket about 3 months ago, that's how I set it up, and I haven't had a problem.
@ViV_fpv It might not be necessary if you use ELRS but I think I saw it was needed for other protocols like Frsky or Spektrum. Forgot where I saw this but I think that's why the delay is needed.
@ViV_fpv I just tried your simple setup and it doesn't seem to work. It doesn't arm. What's your setup exactly? I think I'm more confused now.
This method doesn't work for me. Sometimes it just arms and does not go into turtle mode. Sometimes it just goes into turtle mode without arming. I think that delay is needed because it goes into turtle mode first THEN arms but does it very quickly.