-
Notifications
You must be signed in to change notification settings - Fork 13.7k
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
Use control group target from mavlink message. #8908
Conversation
The UART3 also have the I2C bus 2 functions so moving GPS to UART7 to have one additional I2C. To keep GPS working is also necessary update the FPGA RTL to version 0xC1 or higher.
Nothing use this define right now so lets remove it. Several other boards also have this defines that can also be removed.
Now that UART3 is no longer in use we can use this I2C bus.
This change plus the new FPGA RTL(version 0xC1 or higher) will make use of the new I2C bus, this new bus will be shared between aerofc_adc and ll40ls(if connected) and leaving the old bus just to IST8310.
This can help "unbrick" AeroFC when a bad firmware is loaded and it keeps rebooting or it spinning in some loop. No need to request to stay in booloader as it will stay in bootloader because the pin is set.
…based on tailsitter) * added new vtol type * kill switch causes automatically disarming * RC loss causes automatically disarming
* Add sitl mixer file * reversed standard_vtol mixer back
…, proper outputs) * cleaned up and simplyfied kitpower vtol controller * added neutral axes rotation when switching in fw mode * added motor shutdown when in fixedwing mode
@xgerrmann please check the CI failure (trivial formatting). |
@dagar Can you look into this, please? |
Looks correct, but don't we need more logic to handle group_mlx changing? There's nothing stopping you from sending the first set_actuator_control_target on group_mlx=0, which advertises and publishes actuator_controls_0, then the following message on group_mlx=1, but the publish will be broken. |
@julianoes, I've implemented your requested changes. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok looks correct now.
Has this been tested? |
Can you remove the extra commits and rebase on current master? |
@@ -1055,18 +1055,47 @@ MavlinkReceiver::handle_message_set_actuator_control_target(mavlink_message_t *m | |||
if (_control_mode.flag_control_offboard_enabled) { | |||
|
|||
actuator_controls.timestamp = hrt_absolute_time(); | |||
uint8_t control_group = set_actuator_control_target.group_mlx; | |||
static int8_t control_group_previous = -1; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you move the static into the class?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you remove the extra commits and rebase on current master?
NOTE: This has conflicts with #7477 as it solves the same issue |
@xgerrmann #7477 is merged with the master; Thus the problem this PR solves is no more. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Closing as stale. |
@dagar we should probably check if this can go in. |
Closing as stale. |
At stalebot, the fight is on! 😄 |
Ok thanks @AlexisTM |
Previously the control group 0 was used for publishing the control targets from the incoming mavlink messages. In the mavlink specification, it is possible to set a specific control group. This ensures the correct control group is targeted.
This PR, accompanies the DroneCore PR: mavlink/MAVSDK#277