No wonder you have been busy! I figured out something similar to get all my desired modes, but I need three switches, one for arm/RTL and the other two for modes. Nice video!! (Actually I have a third 'aux' mode switch, say for autotune/autotrim/mission.)
Yeah, this and a couple of secret projects that will be revealed on Sunday have kept me busy. I’m similar. I have a switch for arm, a combination of a switch and the 6-way for modes, then a combination of 2 3-way switches for LEDs, launch, and the auto tuning stuff. Its fun working out the OpenTX stuff, especially when it’s a bit challenging.
Great OpenTX video (the other ones on your channel are too). Have a good Christmas and new year (as great as can be after Boris' announcement today) and I look forward to more great content in 2021.
Thanks Kevin. Yay tier 4. So long as people stay safe and free from CoViD, I’m not overly bothered. A safe and healthy family is all I want this year. Though the Crosswind Mini will help 😁. Happy Christmas to you too, and a much better 2021.
Hi there - very informative and thankyou. I'm looking for a way configure a switch that overides the throttle by say 3%. So if the throttle was at 50, or 80, or 100%, then by flicking the assigned switch, the throttle would change to 53, 83 or 103% respectively. Hope you can help ! - note im a newbie, and looking to apply this to EdgeTX in a Radiomaster Pocket.
Very useful. Thanks. OpenTX offers always multiple solutions. But your suggestions are very "clean". Very few programming lines... so I can understand after a year better what I did... :)
You’re welcome. Its usually best to use the KISS approach. However, what I’ve started doing for OpenTX models that do have a fair amount of logic is keeping a text file of what I do. I’ll have the line number and the function its performing, even if its simple. It just makes it much easier to get back to grips with it if you revisit it in the future. For example: L01 | Test to see if the throttle is low L02 | Test that the arm switch is in the arm position AND the throttle is low The uppercase AND shows that it is what is happening in the AND Switch column.
What version are you using, I've a Horus x12s on 2.3.10. Cant get the spectrum analyser showing, and no longer have option for external aerial. Any ideas
Yea I'm not a crossfire user, have not gone towards drones, mutlicopters just yet, I'm a simple fixed wing flyer, I've tried looking at 2.3.11, on the nightly builds, but for some reason my computer doesn't allow me to download it, keeps saying its blocked dame annoying as I really want the external back for extra range. Them the breaks I guess.
On the 9 position switches I seem to be missing the first two and last two positions in the INAV modes tab. In other words it is not registering. My percentages are moving correctly compared to yours but my US range is between 988us and 2012us. On the modes tab on INAV it expects 1000us to 2000us. Have I missed something?
Hi Mark. The 988 - 2012 range should be able to be picked up in the iNav modes just fine. Regular 3 position switches will be 988 - 1500 - 2012 as their microsecond values. If you go to the receiver page, do you see all 9 positions there? How does that compare to the channel monitor on the transmitter? Also, which RC link are you using?
@@MrD Hi Darren. I am only seeing 7 positions in the receiver tab. I have a Radiometer TX 16S with a Matek 2.4G ELRS Diversity RX. The 5 position switches works perfectly. Thats plenty to keep me going for a while. I will try the same again with a CRSF RX model.
Darren. Update. I swapped out the RX for a CRSF RX. It works perfectly on that. Can only conclude its a ELRS Rx issue. Sorry to have wasted your time. I hope there will not be an issue flying on 5 modes.
@@markholland2021 it’s possibly the ELRS. Have you tried using wide hybrid mode? It should work with that. Standard hybrid 8 would only have 7 positions on channels 6-11.
My question is, What's wrong with just using the channels that we already have. I mean I have 16 channels why not use them? I can understand your way as being convenient for some but if I have 6 switches 4 being 3 way and 2 being 2 way why not use them. I'd have to keep track what switch is activated and what's not the way you are showing. Is it an issue for INAV when we use separate channels for each flight mode or nav modes? Or is this just a preference thing? Thanks.
The problem with using multiple channels is that you are not issuing specific commands to iNav. You will be requesting 3 different modes to iNav, for example; and iNav chooses which one to use. So really, you don't know 100% what will be activated when you flip that switch. You know what that switch position is for. But whether it uses it or not depends on the other switches on the other channels. So you still have to keep track of which switch is activated. If one of them is in manual, it will block all the others, except for RTH. In contrast, if all the modes are on a single channel, you know that whichever mode you select on the transmitter, iNav will use. So long as it can due to hardware or safety blocks. But those will apply whichever method is uses. Another benefit of using 1 channel, is that it doesn't waste other channels. You say we have 16 channels. Some only have 12. Those channels can soon disappear too. Tuning, pan & tilt, camera switching, LEDs, OSD switching. That's 7 channels in that list. So we're already over the 12 channel limit of Crossfire.
@@MrD I understand what you are saying but I've always ran flight modes one say channel 5 for angle ,horizon on 3 pos switch. All switches up is Acro just so you no. Then I run say channel 6 for Cruise and autotune. Channel 7 for 3d Cruise and autotrim or autolevel. Then channel 8 for manual and RTH. I've never had an issue
Actually it seems to me the way you are doing it requires way more screwing around in opentx fiddling with switches. My way is I use the channels that are given to me. No messing about in already confusing Opentx configuration. I have voice tracks and osd that tells me what mode I'm on as well. Your explanation is more confusing than anything. Where you getting inav is not knowing what channels I'm using and it's not 100% as long as osd and my TX voice outs tell me then I'm pretty sure I'm in that Mode. Plus the INAV configurator tells me so as well. I need more explanation than what you are saying because to ME it seems it's a preference thing and just your opinion on being the best way. Sorry ,that's just way I see it.
Ok, so you put your switch on channel 8 in manual. Then you out your switch on channel 6 to cruise. What happens? It doesn’t change to cruise, it stays in manual because iNav is giving manual priority. With only 1 rc channel used, you choose the priority, not iNav. Its a simple matter of control. I agree, it adds a little complexity to OpenTX. But, not to the switches themselves. You could have one switch as angle, horizon, and cruise, another switch as course hold and cruise, and the last mode switch as RTH and Manual. Sounds pretty much the same as your example, but operating on one channel. It can all be set with an input and one logical switch too. So nothing complex. I’d personally put the autotune/trim and auto level on a separate switch (and channel) just to have more options with the tuning side. For example, I use auto level in angle or course hold. Auto trim can be used with anything except manual. At the end of the day, it’s what you feel comfortable with. But the single channel method is a better, and does have advantages.
@@MrD Ok. I think I now understand this. I appreciate you explaining it. I've just always run my modes on separate channels and used same switch configurations on all my builds and I just know where my modes are. Flight modes and nav modes including tuning. If I ever needed extra channels for say pan tilt or cam control I just used a breakout board which has just worked for me. I do kinda like your way now that I'm understanding it better and I'll probably set my Phoenix V2 2400 glider up the way you set up modes and see how things go.
Thank you Darren. Very helpful.
You’re welcome. I’m glad it helped 👍🏻
@@MrD I've learned a lot from your videos. Well done. The FPV community is lucky to have you.
This video was truly helpful. Thank you!
You’re welcome Dave. I’m glad it helped 👍🏻
Hi MrD,
Thank you for the explanation. I see that I can do more with the Open TX switches . I'm going to see how it works for me.
No problems Casper 👍🏻
Thanks Darren, the 9 combo out of 2 three way switches on one channel, was exactly what I was looking for. 👍
Glad it helped 👍🏻
Love the 9 pos mix.
Thanks. I can see it being more difficult to remember mode positions. But it gives more options, especially for transmitters with less switches.
The content you put out is amazing. Thanks Mr.D!
Thank you Corey 👍🏻
No wonder you have been busy! I figured out something similar to get all my desired modes, but I need three switches, one for arm/RTL and the other two for modes. Nice video!! (Actually I have a third 'aux' mode switch, say for autotune/autotrim/mission.)
Yeah, this and a couple of secret projects that will be revealed on Sunday have kept me busy.
I’m similar. I have a switch for arm, a combination of a switch and the 6-way for modes, then a combination of 2 3-way switches for LEDs, launch, and the auto tuning stuff. Its fun working out the OpenTX stuff, especially when it’s a bit challenging.
Great OpenTX video (the other ones on your channel are too). Have a good Christmas and new year (as great as can be after Boris' announcement today) and I look forward to more great content in 2021.
Thanks Kevin. Yay tier 4. So long as people stay safe and free from CoViD, I’m not overly bothered. A safe and healthy family is all I want this year. Though the Crosswind Mini will help 😁. Happy Christmas to you too, and a much better 2021.
I was just wondering how to get a bunch of different modes setup on one channel for Ardupilot. I knew you'd have my back 🙂
No problem Shane. Glad I could help.
Genius always learn something from your videos
Thanks Dave 👍🏻 I’m sure I’ll give a good demonstration on #landing soon 🤣
Hi there - very informative and thankyou. I'm looking for a way configure a switch that overides the throttle by say 3%. So if the throttle was at 50, or 80, or 100%, then by flicking the assigned switch, the throttle would change to 53, 83 or 103% respectively. Hope you can help ! - note im a newbie, and looking to apply this to EdgeTX in a Radiomaster Pocket.
Hi Darren , Brilliant vid .
Be nice to see how to set these switches up on the X20S ??
Very helpful on the switch but can you help with setting a pump on demand in open tx for a hydraulic excavator please
I really don’t have a clue what’s involved there.
Hello D. Awesome. thanks. How do I get each switch position to output a different sound notification
Thanks!!!
You’re welcome Horváth 👍🏻
Very useful. Thanks. OpenTX offers always multiple solutions. But your suggestions are very "clean". Very few programming lines... so I can understand after a year better what I did... :)
You’re welcome.
Its usually best to use the KISS approach. However, what I’ve started doing for OpenTX models that do have a fair amount of logic is keeping a text file of what I do. I’ll have the line number and the function its performing, even if its simple. It just makes it much easier to get back to grips with it if you revisit it in the future. For example:
L01 | Test to see if the throttle is low
L02 | Test that the arm switch is in the arm position AND the throttle is low
The uppercase AND shows that it is what is happening in the AND Switch column.
Sir. Would you know how to work with Altimeter for flying F5J Sailplane and install a safety Switch to start Motor up ?
What version are you using, I've a Horus x12s on 2.3.10. Cant get the spectrum analyser showing, and no longer have option for external aerial. Any ideas
I’m sure I’m on 2.3.9 on my Horus. I’ve purposely not updated to 2.3.10 because of the Crossfire bug.
Yea I'm not a crossfire user, have not gone towards drones, mutlicopters just yet, I'm a simple fixed wing flyer, I've tried looking at 2.3.11, on the nightly builds, but for some reason my computer doesn't allow me to download it, keeps saying its blocked dame annoying as I really want the external back for extra range. Them the breaks I guess.
@@russcole5685 2.3.9 works fine, unless there are specific features you need from .10?
On the 9 position switches I seem to be missing the first two and last two positions in the INAV modes tab. In other words it is not registering. My percentages are moving correctly compared to yours but my US range is between 988us and 2012us. On the modes tab on INAV it expects 1000us to 2000us. Have I missed something?
Hi Mark. The 988 - 2012 range should be able to be picked up in the iNav modes just fine. Regular 3 position switches will be 988 - 1500 - 2012 as their microsecond values.
If you go to the receiver page, do you see all 9 positions there? How does that compare to the channel monitor on the transmitter? Also, which RC link are you using?
@@MrD Hi Darren. I am only seeing 7 positions in the receiver tab. I have a Radiometer TX 16S with a Matek 2.4G ELRS Diversity RX. The 5 position switches works perfectly. Thats plenty to keep me going for a while. I will try the same again with a CRSF RX model.
Darren. Update. I swapped out the RX for a CRSF RX. It works perfectly on that. Can only conclude its a ELRS Rx issue. Sorry to have wasted your time. I hope there will not be an issue flying on 5 modes.
@@markholland2021 it’s possibly the ELRS. Have you tried using wide hybrid mode? It should work with that. Standard hybrid 8 would only have 7 positions on channels 6-11.
@@MrD Bingo. That works perfectly now. Bought you a coffee. Regards and thanks again.
My question is, What's wrong with just using the channels that we already have. I mean I have 16 channels why not use them? I can understand your way as being convenient for some but if I have 6 switches 4 being 3 way and 2 being 2 way why not use them. I'd have to keep track what switch is activated and what's not the way you are showing. Is it an issue for INAV when we use separate channels for each flight mode or nav modes? Or is this just a preference thing?
Thanks.
The problem with using multiple channels is that you are not issuing specific commands to iNav. You will be requesting 3 different modes to iNav, for example; and iNav chooses which one to use. So really, you don't know 100% what will be activated when you flip that switch. You know what that switch position is for. But whether it uses it or not depends on the other switches on the other channels. So you still have to keep track of which switch is activated. If one of them is in manual, it will block all the others, except for RTH.
In contrast, if all the modes are on a single channel, you know that whichever mode you select on the transmitter, iNav will use. So long as it can due to hardware or safety blocks. But those will apply whichever method is uses. Another benefit of using 1 channel, is that it doesn't waste other channels. You say we have 16 channels. Some only have 12. Those channels can soon disappear too. Tuning, pan & tilt, camera switching, LEDs, OSD switching. That's 7 channels in that list. So we're already over the 12 channel limit of Crossfire.
@@MrD I understand what you are saying but I've always ran flight modes one say channel 5 for angle ,horizon on 3 pos switch. All switches up is Acro just so you no. Then I run say channel 6 for Cruise and autotune. Channel 7 for 3d Cruise and autotrim or autolevel. Then channel 8 for manual and RTH.
I've never had an issue
Actually it seems to me the way you are doing it requires way more screwing around in opentx fiddling with switches. My way is I use the channels that are given to me. No messing about in already confusing Opentx configuration. I have voice tracks and osd that tells me what mode I'm on as well. Your explanation is more confusing than anything. Where you getting inav is not knowing what channels I'm using and it's not 100% as long as osd and my TX voice outs tell me then I'm pretty sure I'm in that Mode. Plus the INAV configurator tells me so as well. I need more explanation than what you are saying because to ME it seems it's a preference thing and just your opinion on being the best way. Sorry ,that's just way I see it.
Ok, so you put your switch on channel 8 in manual. Then you out your switch on channel 6 to cruise. What happens? It doesn’t change to cruise, it stays in manual because iNav is giving manual priority. With only 1 rc channel used, you choose the priority, not iNav. Its a simple matter of control.
I agree, it adds a little complexity to OpenTX. But, not to the switches themselves. You could have one switch as angle, horizon, and cruise, another switch as course hold and cruise, and the last mode switch as RTH and Manual. Sounds pretty much the same as your example, but operating on one channel.
It can all be set with an input and one logical switch too. So nothing complex. I’d personally put the autotune/trim and auto level on a separate switch (and channel) just to have more options with the tuning side. For example, I use auto level in angle or course hold. Auto trim can be used with anything except manual.
At the end of the day, it’s what you feel comfortable with. But the single channel method is a better, and does have advantages.
@@MrD Ok. I think I now understand this. I appreciate you explaining it. I've just always run my modes on separate channels and used same switch configurations on all my builds and I just know where my modes are. Flight modes and nav modes including tuning. If I ever needed extra channels for say pan tilt or cam control I just used a breakout board which has just worked for me.
I do kinda like your way now that I'm understanding it better and I'll probably set my Phoenix V2 2400 glider up the way you set up modes and see how things go.