Rotorflight is The future. it honstly was not hard to set up between the main wiki page this channel and the discord. It just makes since, sure my first heli took me about 3-4 hours to set up but my second heli only took me about 15-30 min start to finish. I cant wait for this system to start winning the big heli events. then maybe people will actually give it a chance.
Just want to say how much I appreciate your videos on setting up the Nexus on the TX-16. I was JR user for 20 years when I got the RadioMaster TX16s a few years ago. I knew nothing about OpenTX but after many hours of reading instructions;watching a lot of videos,and a lot of frustration, I have become quite adept at programming the radio. Now I am in the same boat with ELRS and RotorFlight. Your videos have helped a great deal as my initial introduction to ELRS and RotorFlight software.
Thank you John, without your content and personal support I could not have got going with Nexus as i was stuck in reverse gear ..... amazing support plus content and all very well explained...just what the RC community needs...and what Radiomaster needs in order to be able to sell their product due to its complexity around setup. THANK YOU
@laurentlapassade4149 suggested Configuration - Set a UART to GPS i.e. UART3 and under Features turn on GPS. I can confirm after doing these two things, Altitude showed up as a sensor with "discover new"
With some help from Rob, I figured the telemetry thing out: In the CLI sensors stop sending. That's why they went red in the video. While I entered the telemetry reuse command, I didn't "save" my changes in the CLI, instead I typed "exit". So my telemetry re-use change did not take effect. I can confirm that after entering the command and saving the change in CLI the altitude sensor does show up.
At the 8:30 mark, you have an offset to Channel 9, it shows: -100% SA Profil All the others are a positive 100% value, am I not connecting some dots that are obvious to others?
At the end of the video, I had the same problem with the RPM not showing up. In rotoflight, I typed save into the command prompt and exited. On reboot, the radior fired up the ALT sensor and I changed it to RPM.
On the motor setup on the hobbywing esc there is a single wire for the bec and a 3 wire servo type plug that goes into the nexus esc port correct. Where does the single bec wire go.
A BEC cannot be single wire. By definition, a BEC requires + and - to operate. Usually the + and - of the BEC are on the same 3 pin connector as the ESC signal wire and get plugged in to the THR port. That's what I did on my Raw 700.
I understand thank you. I have a castle creation 120amp esc it does have a 3 wire servo plug that goes into the throttle port on the nexus. There is one wire that has a single wire that is use as the bec for back up power uf you lose the esc. If you don't use that wire you leave it unplugged and use a battery backup. Or is that single wire for telemetry for rmp. Thank you for your help. I hope I have explained right.
Its done in Rotoflight after you get the basic inputs. Its like setting up for a flight simulator....you dont need to do the mixing on the radio....just activate the channels to a switch and something else handles the mixing.
Excellent video/tutorial. I’m still having an issue arming the motor. I assume it’s because I’m not below 1000. I’m able to change my CH3 (PitCol) however I’m not able to change the Aux 1 below 1000. Any tips?
Set Motor Stop Throttle PWM = 1000 Set 0% Throttle PWM = 1033 That should do it. More info in this video ruclips.net/user/liveth88LiJYs-Y?si=4eOqpX1fUkG8abiN&t=792
@@RCVideoReviewsthanks for the tips. I made the changes and watched the motor setup video. I left a question on that tutorial. Still running into a wall here. 😅
Hello John, so many thanks for this great video very helpfull. I just received a FlyDraggon F722 V2, that I ordered 3 days before RM announced their Nexus ;o( I'm still waiting for a hobbywing RPM sensor. Just a question about elrs packet rates, I saw people telling the best to use with RF is D500. What is your recommandation? At this moment I set to 333Hz full and switch mode 16/2 channels. About your issue to get alt on the telemetry, I had to enable gps in the configuration but also to set a uart to GPS, if not then gps goes automaticly to disable even after saving parameters.
I was originally using 333Hz Full with all my helis, but I realized LoRA 500 (not D500) is better. Lower latency, more stick resolution. Plus, you only really need full resolution on channels 1-4 anyway. Using a wide channel (128-position) works great for throttle on Channel 6.
I used 333hz. I've done a lot of testing with different rates/resolutions and have come to the conclusion I cannot discern a difference in latency/resolution of anything higher. The FC may perform better with higher refresh rates, so no harm in trying.
@@laurentlapassade4159 Can't go wrong with 333Hz Full for any fixed wing or heli application. John is probably right about not being able to feel the latency/resolution improvements of the 500Hz mode.
Will be interested to hear what you learn. Just like a quad and as Mike said, you only need 4 full res channels. So definitely feel free to experiment.
I had a similar issue with the latest version of EdgeTX Centurion, where the altitude telemetry wasn't being discovered. After reverting to the previous EdgeTX version it worked again. Could this be an issue with EdgeTX?
Great video again. I'm on Ethos but it's pretty similar to edge so it helps a lot! The only thing is I want to use 3 idle up modes and autorotarion bailout (esc governor) so I have to break my head over some mixing that change the throttle hold and output values when switching the arm swith.
Well, you're in luck. I just posted my RF and Edge configs in discord that do exactly this. I separated idle up and motor control. Motor control now has cut/auto-rotate/arm and IU now has three headspeeds.
@@RCVideoReviews nice I'll check those out! Don't have the Nexus yet but I think using logic switching I achieved the same thing. Weather it works has to be seen lol
I thought about logic too, but RF has a cutoff percentage option which transfers throttle control direct to ESC and it works pretty well. So no logic is really necessary. I started thinking about logic too, but after mapping it out, I think the config would have been too complex and there's already too much noise in the system about complexity. The dual switch option is very straight forward: 1) ARM for ELRS/RF - SH 2) Enable Motor - SG 3) Idle Up - SA Of course you can use whatever switches you want, but it is simple to understand.
@@RCVideoReviews I made 3 logic switches now. One cuts the throttle fully when RF isn't armed so you can arm, this overrides throttle hold. The nest has the same value allowing throttle hold to be used to start the motor. Probably going into soft start every time it's used. And the 3d position raises the min throttle to 27% allowing for a autorotarion bailout. One switch being 3 profiles in RF. One throttle hold (I like to keep using that one because surely otherwise I'll mess up with one of my other heli's not on RF) and a 3pos switch for disarmed-armed-armed bailout. Great to see RF has such a active community. I'm sure it'll be the future of fbl systems
The nexus is too big for my Rotorflight project, so I won't enter your competition. However, I really appreciate your series & Radiomaster getting into Rotorflight.,
Just wondering why you made it so confusing with the throttle , why not just put it with the arm switch and not worry about having it on a 3 position switch and add all that confusion. Yes it works , but I feel very unnecessary. Unless I’m missing something .
Do you have a video on here that shows how to set up elrs with a sbus compatible flight controller ? No rotorflight . Would the channels be close to the same ?
The radio setup is pretty brain dead simple. I mean honestly, 4 inputs and 9 mix lines which includes IU/RATES/RESCUE/ARMING and are nothing more than 3pos switches.
The radio setup is pretty brain dead simple. I mean honestly, 4 inputs and 9 mix lines which includes IU/RATES/RESCUE/ARMING and are nothing more than 3pos switches. You will never see Spektrum on this channel.
Rotorflight is The future. it honstly was not hard to set up between the main wiki page this channel and the discord. It just makes since, sure my first heli took me about 3-4 hours to set up but my second heli only took me about 15-30 min start to finish. I cant wait for this system to start winning the big heli events. then maybe people will actually give it a chance.
It's going to take some awareness, just like ELRS and EdgeTX. I agree though, it's clear to me this is the future for FBLs.
Just want to say how much I appreciate your videos on setting up the Nexus on the TX-16.
I was JR user for 20 years when I got the RadioMaster TX16s a few years ago. I knew nothing about OpenTX but after many hours of reading instructions;watching a lot of videos,and a lot of frustration, I have become quite adept at programming the radio.
Now I am in the same boat with ELRS and RotorFlight. Your videos have helped a great deal as my initial introduction to ELRS and RotorFlight software.
Makes me happy to hear this. It's why I put in the time. Glad to help. Thanks for the note.
Thank you John, without your content and personal support I could not have got going with Nexus as i was stuck in reverse gear ..... amazing support plus content and all very well explained...just what the RC community needs...and what Radiomaster needs in order to be able to sell their product due to its complexity around setup. THANK YOU
Always glad to help.
@laurentlapassade4149 suggested
Configuration - Set a UART to GPS i.e. UART3 and under Features turn on GPS.
I can confirm after doing these two things, Altitude showed up as a sensor with "discover new"
With some help from Rob, I figured the telemetry thing out:
In the CLI sensors stop sending. That's why they went red in the video.
While I entered the telemetry reuse command, I didn't "save" my changes in the CLI, instead I typed "exit". So my telemetry re-use change did not take effect.
I can confirm that after entering the command and saving the change in CLI the altitude sensor does show up.
Are you using the latest EdgeTX Centurion?
Well done RF. However wish if can use more "friendly" term instead extreme technical term such as PID
At the 8:30 mark, you have an offset to Channel 9, it shows: -100% SA Profil
All the others are a positive 100% value, am I not connecting some dots that are obvious to others?
At the end of the video, I had the same problem with the RPM not showing up. In rotoflight, I typed save into the command prompt and exited. On reboot, the radior fired up the ALT sensor and I changed it to RPM.
On the motor setup on the hobbywing esc there is a single wire for the bec and a 3 wire servo type plug that goes into the nexus esc port correct. Where does the single bec wire go.
A BEC cannot be single wire. By definition, a BEC requires + and - to operate. Usually the + and - of the BEC are on the same 3 pin connector as the ESC signal wire and get plugged in to the THR port. That's what I did on my Raw 700.
I understand thank you. I have a castle creation 120amp esc it does have a 3 wire servo plug that goes into the throttle port on the nexus. There is one wire that has a single wire that is use as the bec for back up power uf you lose the esc. If you don't use that wire you leave it unplugged and use a battery backup. Or is that single wire for telemetry for rmp.
Thank you for your help. I hope I have explained right.
Hi I'm really confused, I don't see any references to throttle curves and collective (Pitch) curve. Is this not necessary in Nexus.?
Its done in Rotoflight after you get the basic inputs. Its like setting up for a flight simulator....you dont need to do the mixing on the radio....just activate the channels to a switch and something else handles the mixing.
Excellent video/tutorial. I’m still having an issue arming the motor. I assume it’s because I’m not below 1000. I’m able to change my CH3 (PitCol) however I’m not able to change the Aux 1 below 1000. Any tips?
Watch my motor setup video. It’s covered there.
Set Motor Stop Throttle PWM = 1000
Set 0% Throttle PWM = 1033
That should do it. More info in this video ruclips.net/user/liveth88LiJYs-Y?si=4eOqpX1fUkG8abiN&t=792
@@RCVideoReviewsthanks for the tips. I made the changes and watched the motor setup video. I left a question on that tutorial. Still running into a wall here. 😅
Join discord and ask there.
Joined last night. Now to figure out Discord. 😂
Hello John, so many thanks for this great video very helpfull.
I just received a FlyDraggon F722 V2, that I ordered 3 days before RM announced their Nexus ;o(
I'm still waiting for a hobbywing RPM sensor.
Just a question about elrs packet rates, I saw people telling the best to use with RF is D500. What is your recommandation? At this moment I set to 333Hz full and switch mode 16/2 channels.
About your issue to get alt on the telemetry, I had to enable gps in the configuration but also to set a uart to GPS, if not then gps goes automaticly to disable even after saving parameters.
I was originally using 333Hz Full with all my helis, but I realized LoRA 500 (not D500) is better. Lower latency, more stick resolution. Plus, you only really need full resolution on channels 1-4 anyway. Using a wide channel (128-position) works great for throttle on Channel 6.
I used 333hz. I've done a lot of testing with different rates/resolutions and have come to the conclusion I cannot discern a difference in latency/resolution of anything higher. The FC may perform better with higher refresh rates, so no harm in trying.
@@RCVideoReviews thanks, this is also my feeling. I 'll try first with 333 Hz, then perhaps tested Mike recommandations once I'll have a good setup.
@@laurentlapassade4159 Can't go wrong with 333Hz Full for any fixed wing or heli application. John is probably right about not being able to feel the latency/resolution improvements of the 500Hz mode.
Will be interested to hear what you learn. Just like a quad and as Mike said, you only need 4 full res channels. So definitely feel free to experiment.
I had a similar issue with the latest version of EdgeTX Centurion, where the altitude telemetry wasn't being discovered. After reverting to the previous EdgeTX version it worked again. Could this be an issue with EdgeTX?
One of the other recommendations was to enable GPS and assign a UART before ALT showed up. I'll try that first.
Great video again. I'm on Ethos but it's pretty similar to edge so it helps a lot! The only thing is I want to use 3 idle up modes and autorotarion bailout (esc governor) so I have to break my head over some mixing that change the throttle hold and output values when switching the arm swith.
Well, you're in luck. I just posted my RF and Edge configs in discord that do exactly this. I separated idle up and motor control. Motor control now has cut/auto-rotate/arm and IU now has three headspeeds.
@@RCVideoReviews nice I'll check those out! Don't have the Nexus yet but I think using logic switching I achieved the same thing. Weather it works has to be seen lol
I thought about logic too, but RF has a cutoff percentage option which transfers throttle control direct to ESC and it works pretty well. So no logic is really necessary. I started thinking about logic too, but after mapping it out, I think the config would have been too complex and there's already too much noise in the system about complexity. The dual switch option is very straight forward:
1) ARM for ELRS/RF - SH
2) Enable Motor - SG
3) Idle Up - SA
Of course you can use whatever switches you want, but it is simple to understand.
@@RCVideoReviews I made 3 logic switches now. One cuts the throttle fully when RF isn't armed so you can arm, this overrides throttle hold. The nest has the same value allowing throttle hold to be used to start the motor. Probably going into soft start every time it's used. And the 3d position raises the min throttle to 27% allowing for a autorotarion bailout. One switch being 3 profiles in RF. One throttle hold (I like to keep using that one because surely otherwise I'll mess up with one of my other heli's not on RF) and a 3pos switch for disarmed-armed-armed bailout.
Great to see RF has such a active community. I'm sure it'll be the future of fbl systems
Would love to try this on my 420Raw Build. Would it work with Futaba SBus? Thank you Sir!
Yes, SBUS is supported.
How did you assign the Collective pitch on Channel 3 along with throttle ?
I also havee the same issue
great video due you have the zip file to download your tx16s settings many thanks for your help
On my discord.
The nexus is too big for my Rotorflight project, so I won't enter your competition. However, I really appreciate your series & Radiomaster getting into Rotorflight.,
Thanks for the note. Glad to do it.
Just wondering why you made it so confusing with the throttle , why not just put it with the arm switch and not worry about having it on a 3 position switch and add all that confusion. Yes it works , but I feel very unnecessary. Unless I’m missing something .
Do you have a video on here that shows how to set up elrs with a sbus compatible flight controller ? No rotorflight . Would the channels be close to the same ?
To enable auto rotation and auto bailout modes.
Yes
@@RCVideoReviews okay , that makes a lot of sense . Thank you for the clarification!.
Too confusing they should have made the tx set up easier
I would like to change to rotorflight
The radio setup is pretty brain dead simple. I mean honestly, 4 inputs and 9 mix lines which includes IU/RATES/RESCUE/ARMING and are nothing more than 3pos switches.
Schade ich kann kein Englisch und es ist zu kompliziert. Ich hoffe es gibt was auf deutsch das ich das ganze setup verstehe.
Or better still it would be simpler if like spectrum or even futaba
The radio setup is pretty brain dead simple. I mean honestly, 4 inputs and 9 mix lines which includes IU/RATES/RESCUE/ARMING and are nothing more than 3pos switches.
You will never see Spektrum on this channel.
@@RCVideoReviews Thank you for forward thinking! So tired of all the copy/paste spektrum foam fliers stuck in decades past.