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

Use control group target from mavlink message. #8908

Closed
wants to merge 31 commits into from
Closed

Use control group target from mavlink message. #8908

wants to merge 31 commits into from

Conversation

xgerrmann
Copy link

@xgerrmann xgerrmann commented Feb 18, 2018

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

zehortigoza and others added 24 commits August 5, 2017 11:04
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
@dagar
Copy link
Member

dagar commented Feb 18, 2018

@xgerrmann please check the CI failure (trivial formatting).

@xgerrmann
Copy link
Author

@dagar Can you look into this, please?
If you agree with the implementation, I'll rebase on demand.

@dagar
Copy link
Member

dagar commented Mar 6, 2018

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.

@xgerrmann
Copy link
Author

@julianoes, I've implemented your requested changes.

Copy link
Contributor

@julianoes julianoes left a 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.

@dagar
Copy link
Member

dagar commented Mar 30, 2018

Has this been tested?

@dagar
Copy link
Member

dagar commented May 23, 2018

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;
Copy link
Member

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?

Copy link
Member

@dagar dagar left a 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?

@AlexisTM
Copy link
Contributor

AlexisTM commented Aug 3, 2018

NOTE: This has conflicts with #7477 as it solves the same issue

@AlexisTM
Copy link
Contributor

AlexisTM commented Sep 26, 2018

@stale
Copy link

stale bot commented Jan 20, 2019

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.

@stale
Copy link

stale bot commented Feb 4, 2019

Closing as stale.

@stale stale bot closed this Feb 4, 2019
@julianoes julianoes reopened this Feb 4, 2019
@julianoes
Copy link
Contributor

@dagar we should probably check if this can go in.

@stale
Copy link

stale bot commented Feb 18, 2019

Closing as stale.

@stale stale bot closed this Feb 18, 2019
@julianoes julianoes reopened this Feb 18, 2019
@stale stale bot removed the Admin: Wont fix label Feb 18, 2019
@julianoes
Copy link
Contributor

At stalebot, the fight is on! 😄

@AlexisTM
Copy link
Contributor

AlexisTM commented Feb 18, 2019

This PR has been overseeded by #7477.

#7477 uses a different object for each topic.

@julianoes
Copy link
Contributor

Ok thanks @AlexisTM

@julianoes julianoes closed this Feb 18, 2019
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

Successfully merging this pull request may close these issues.

7 participants