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

Arming and RXLOSS #3

Open
darebear opened this issue Jun 2, 2022 · 1 comment
Open

Arming and RXLOSS #3

darebear opened this issue Jun 2, 2022 · 1 comment

Comments

@darebear
Copy link

darebear commented Jun 2, 2022

Hello again,

Two things:

  1. On line 14 of MultiWiiNode.cpp, the baud-rate should be 115200.
  2. I've been trying to figure out why my system won't arm, do you have any insight into how to prevent the RXLOSS flag from being evoked by the system? I noticed that in the ROS1 implementation, you used ros::Rate, was that to keep the flight computer from evoking the RXLOSS or similar dis-arming flags?

Thank you.

@christianrauch
Copy link
Owner

the baud-rate should be 115200.

Thanks. That must have been a typo. This is fixed now on master.

do you have any insight into how to prevent the RXLOSS flag from being evoked by the system?

The only way to prevent the system from disarming the FCU is to periodically send commands to the FCU. In the msp library, this means you have to call setRc periodically, depending on your timeout value. For the node, this means that you have to send messages to either the rc/override or the rc/override/raw topic.

If you have a joystick or gamepad, you can use https://github.com/christianrauch/rc_joystick to send these commands. Some receivers, e.g. the FrSky Taranis Q X7 can be connected via USB and appear as joysticks in the system. I tested the rc_joystick node in this mode.

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