The NEXUS Flybarless (FBL) control unit has been designed from the ground up based on the Rotorflight 2.0 reference design. All aspects of the NEXUS have been planned and tested for optimum performance and compatibility, ensuring the best out-of-the-box Rotorflight experience on the market today.
Rotorflight is a Flight Control software suite designed for single-rotor helicopters. It consists of: Rotorflight Flight Controller Firmware. Rotorflight Configurator, for flashing and configuring the flight controller
With its advanced STM32F722 MCU and the TDK ICM-42688-P 6-axis MEMS motion tracking device, which combines a 3-axis gyroscope and a 3-axis accelerometer, the NEXUS flight controller ensures precision control and flight. A large 128MB of onboard flash memory ensures you can log all your flights for fine-tuning and adjustment.
Our Plug’n’Play solder-free RP3-H ExpressLRS receivers feature a locking connector system to ensure a stable connection between the control unit and receiver. DSM and S.BUS ports are also available for use with your selected receiver type. The NEXUS also features multi-function ports for future expansion.
The NEXUS features a CNC machined aluminum case as standard, which looks great, protects the control unit, and dissipates heat for the F722 processor.
After more than 12 months of R&D, the NEXUS has been tested, tuned, and tested again by not only the developers at Rotorflight but also a team of experienced helicopter pilots who took part in our beta testing program. We would like to thank the Rotorflight team and the Beta testing team for making the NEXUS possible!
warning
R/C helicopters are not toys. R/C helicopter utilize various high-tech products and technologies to provide superior performance.Improper use of this product can result in serious injury or even death. Please read this manual carefully before using and make sure to be conscious of your own personal safety and the safety of others and your environment when operating all RC Helicopter products. I assume no liability for the operation or the use of this product. Intended for use only by adults with experience flying remote control helicopters at a legal flying field.
tip
Safety is paramount. Always follow safety guidelines, such as not flying near people, animals, or obstacles. Maintain a safe distance from other RC enthusiasts. Wear safety glasses to protect your eyes from debris.
tip
I translated the Rotorfligh configurator to French, took me 30h to complete. https://github.com/rotorflight/rotorflight-configurator/pull/82
Features
https://www.radiomasterrc.com/products/nexus-helicopter-flight-controller
ELRS
- non-ELRS users don’t need to deal with dangling antennas.
- ELRS users have a plug-and-play option with the RP3-H.
Update ELRS
ELRS RX version MUST match the ELRS TX version!
Using the WiFi method is the easiest.
- Plug the NEXUS with USB-C without LiPo and wait for 60s
- Download ExpressLRS configurator
- Build
- Connect to “ExpressLrs RX”
- Upload bin file
Mounting
WIP
Setup
Radiomaster Tx16s setup
use
Detailled Rotorflight setup
more https://www.youtube.com/watch?v=VcOebsyBGqM&list=PLy3TC1ILJYTht1pKEBHK4f_E6sJRLNp4vor
Fast Rotorflight setup in 14 min
FAQs
Motors are not spooling
Does it spool if you use override? YES look at the arming flag to locate issue ( https://www.rotorflight.org/docs/Tutorial-Setup/Status#arming) , NO! you may need to calibrate ESC
Throttle position is higher than the min arm position
- Lower the throttle in your TX
- If you can’t make your throttle go lower on your TX you can increase the throttle channel value for Armin on the receiver tab
F.Port Support
If you want to connect f.port to sbus port then you need to switch the resources from rx to tx F.port is one wire only You connect it to SBUS slot Then in CLI you switch the resources
resource SERIAL_RX 2 NONE
resource SERIAL_TX 2 A03
Then in configurator you enable these two
Tips
- A, B, C are nearly identical expansion ports
- You can use the S.BUS port for ESC telemetry, if you are not using it for S.BUS or F.Port. You can use the S.BUS port for F.Port, and use the DSM port for ESC telemetry Or you can use any of the expansion ports for ESC telemetry