You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am trying to connect my RC system (FrSky X9 Lite S and Archer GR8) to the Pixhawk 6X flight controller with PX4 Pro v1.15.2. The receiver is bound to the transmitter using the ACCESS protocol, and I can see a valid SBUS signal on the oscilloscope at the RC port, but QGroundControl fails to recognize the RC input signal during calibration. Additionally, using the MAVLink console command rc_input status shows that RC input is not running. Manually starting the service still results in the system "searching for signal," despite a visible SBUS signal.
To Reproduce
Power on the Pixhawk 6X connected to a Pixhawk Mini Baseboard.
Bind the FrSky X9 Lite S transmitter with the FrSky Archer GR8 receiver (using ACCESS protocol).
Connect the receiver's SBUS OUT and Ground pins to the RC port's SBUS IN and Ground on the Pixhawk Mini Baseboard.
Power the receiver with 5V from a BEC.
Open QGroundControl, flash the firmware (PX4 Pro v1.15.2), and attempt to calibrate the radio in the "Radio" tab.
Observe no signal during calibration.
Test the RC port with an oscilloscope to verify an SBUS signal.
Use the MAVLink console to execute rc_input status and observe the state as "not running" or "searching for signal."
Expected behavior
The RC signal from the Archer GR8 receiver should be recognized by the Pixhawk 6X, and calibration in QGroundControl should proceed as expected.
Screenshot / Media
Flight Log
No flight log is available as the issue occurs during initial setup.
Software Version
PX4 Pro v1.15.2
Flight controller
Pixhawk 6X with Pixhawk Mini Baseboard
Vehicle type
Multicopter
How are the different components wired up (including port information)
Receiver (FrSky Archer GR8):
Powered via 5V BEC.
SBUS OUT connected to SBUS IN on the RC port of the Pixhawk Mini Baseboard.
Ground connected to Ground on the RC port.
Oscilloscope:
Connected to RC port's SBUS IN and Ground pins to verify signal presence.
Additional context
Tested the system with another receiver (FrSky RX6R) and simulated a PPM signal with Arduino Uno. Both cases produced valid signals on the oscilloscope, but no recognition by the Pixhawk 6X.
Used MAVLink console commands to check the RC port:
rc_input status initially returned "not running."
Starting the RC input service on ttyS5 showed "searching for signal," despite a valid SBUS signal.
Verified hardware functionality and firmware updates:
Receiver firmware: Archer 2.1.14
Transmitter firmware: ISRM-X 2.2.10
I suspect the issue might be related to configuration or firmware handling of the RC port. Any guidance or resolution would be greatly appreciated.
The text was updated successfully, but these errors were encountered:
Describe the bug
I am trying to connect my RC system (FrSky X9 Lite S and Archer GR8) to the Pixhawk 6X flight controller with PX4 Pro v1.15.2. The receiver is bound to the transmitter using the ACCESS protocol, and I can see a valid SBUS signal on the oscilloscope at the RC port, but QGroundControl fails to recognize the RC input signal during calibration. Additionally, using the MAVLink console command rc_input status shows that RC input is not running. Manually starting the service still results in the system "searching for signal," despite a visible SBUS signal.
To Reproduce
Expected behavior
The RC signal from the Archer GR8 receiver should be recognized by the Pixhawk 6X, and calibration in QGroundControl should proceed as expected.
Screenshot / Media
Flight Log
No flight log is available as the issue occurs during initial setup.
Software Version
PX4 Pro v1.15.2
Flight controller
Pixhawk 6X with Pixhawk Mini Baseboard
Vehicle type
Multicopter
How are the different components wired up (including port information)
Receiver (FrSky Archer GR8):
Oscilloscope:
Additional context
Tested the system with another receiver (FrSky RX6R) and simulated a PPM signal with Arduino Uno. Both cases produced valid signals on the oscilloscope, but no recognition by the Pixhawk 6X.
Used MAVLink console commands to check the RC port:
Verified hardware functionality and firmware updates:
I suspect the issue might be related to configuration or firmware handling of the RC port. Any guidance or resolution would be greatly appreciated.
The text was updated successfully, but these errors were encountered: