Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RC_Status and mavlink remote health #2522

Open
aminballoon opened this issue Mar 14, 2025 · 1 comment
Open

RC_Status and mavlink remote health #2522

aminballoon opened this issue Mar 14, 2025 · 1 comment

Comments

@aminballoon
Copy link
Contributor

MAVSDK RcStatus will return is_available = False while autopilot has can't be armed

PX4 manualControlCheck.cpp

In this case if Kill switch engaged RCStatus::is_available will be False* by this Flag

RC_OK Flag check const bool rc_ok = sys_status.onboard_control_sensors_health & MAV_SYS_STATUS_SENSOR_RC_RECEIVER;

In my opinion, when the kill switch is engaged, it doesn't mean that the RC is not available; it's available, but it just can't be armed.

The rc_ok Flag should not be check only MAV_SYS_STATUS_SENSOR_RC_RECEIVER or I need to contribute manualControlCheck in PX4 .

I can add proto Mavlink RC_CHANNELS_RAW for check the latest RC input by Timestamp and solve this issue.
What do you think about this issue and my solution ?

@julianoes
Copy link
Collaborator

Interesting. I would argue this needs changing/fixing on the PX4 side.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants