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

ACTUATOR_OUTPUT_STATUS MAVLink stream for ESCs #13145

Closed

Conversation

irsdkv
Copy link
Contributor

@irsdkv irsdkv commented Oct 9, 2019

Adding ACTUATOR_OUTPUT_STATUS Mavlink stream for UAVs with ESCs.

Test data / coverage
Tested with MAVSDK (This PR).

@julianoes julianoes requested a review from bkueng October 10, 2019 09:49
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.

Thanks @irsdkv.

esc_status_s esc_status;

if (_esc_status_sub->update(&_esc_status_time, &esc_status)) {
mavlink_actuator_output_status_t msg = {};
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@hamishwillee Is that message supposed to contain the feedback from the actuators? It's not clear to me from the message spec.

Copy link
Contributor Author

@irsdkv irsdkv Oct 10, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

IMO ACTUATOR_OUTPUT_STATUS message should provide feedback from the actuators because of we can receive controls with ACTUATOR_CONTROL_TARGET message.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@bkueng It is the updated version of SERVO_OUTPUT_RAW. Discussed in mavlink/mavlink#926

So my understanding is that this is just the raw PWM values we are outputing on all MAIN, AUX, whatever. Not feedback from actuator.

Can you review that chain and confirm you agree. If so, I will add note to it saying this.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That was my understanding as well.
However that means the implementation here is not correct.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@irsdkv ACTUATOR_CONTROL_TARGET contains the values before the mixing.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@bkueng Cool, Assigned you clarification for review: mavlink/mavlink#1252

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@bkueng so is this PR now correct or not? I'm confused.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@bkueng so is this PR now correct or not? I'm confused.

It's not. I thought I wrote that?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@irsdkv have you fixed the issue raised here?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@julianoes I'm still confused.
What I should fix?

@irsdkv
Copy link
Contributor Author

irsdkv commented Oct 16, 2019

Errors:
$ px4_fmu-v2_default.elf section .data will not fit in region flash
$ region flash overflowed by 168 bytes

Should I do anything else so that you can merge PR?

@ndepal
Copy link
Contributor

ndepal commented Nov 14, 2019

What's the status of this? Is a new mavlink message needed? Would be nice to have this in the release.

@bkueng
Copy link
Member

bkueng commented Nov 18, 2019

Is a new mavlink message needed?

Yes, I don't see anything existing.

@stale
Copy link

stale bot commented Feb 16, 2020

This issue has been automatically marked as stale because it has not had recent activity. Thank you for your contributions.

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

Successfully merging this pull request may close these issues.

6 participants