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

Offboard velocity setpoints broken on master #1856

Closed
thomasgubler opened this issue Mar 1, 2015 · 8 comments
Closed

Offboard velocity setpoints broken on master #1856

thomasgubler opened this issue Mar 1, 2015 · 8 comments
Labels

Comments

@thomasgubler
Copy link
Contributor

We have reports that #1786 introduced a regression that disables offboard velocity setpoints.

More tests are needed.

@TarekTaha
Copy link
Contributor

@thomasgubler did you find a solution for this bug ?

@thomasgubler
Copy link
Contributor Author

No, I didn't see it directly in the code and I currently don't have the setup ant time to reproduce it.

@TarekTaha
Copy link
Contributor

No worries, I had a quick look at the code, nothing is obvious there, the logic is correct, it must be some hard to find bug.

@xuliren
Copy link

xuliren commented May 18, 2015

Hi, I'm testing the offboard velocity function under an indoor-vicon testbed. Currently the uav can do the offboard position control very well, but the velocity control are not working. After reading the source code, I found that https://github.com/PX4/Firmware/blob/master/src/modules/mc_pos_control/mc_pos_control_main.cpp#L715 is converting the velocity control into an position control, I think it might not that proper to to so.

@supermice
Copy link

@xuliren What's the status now? Does the master firmware fixed the velocity control problem?

@aerialhedgehog
Copy link
Contributor

I tried flying this yesterday and did not get any response from my hex
while sending velocity commands.

On Sat, Jun 27, 2015 at 10:27 PM, super_mice notifications@github.com
wrote:

@xuliren https://github.com/xuliren What's the status now? Does the
master firmware fixed the velocity control problem?


Reply to this email directly or view it on GitHub
#1856 (comment).

  • Trent Lukaczyk
    Stanford University Engineering
    Cornell University Engineering 2010
    twl26@stanford.edu

@aerialhedgehog
Copy link
Contributor

i was flying master, using the c_uart_interface example
https://github.com/mavlink/c_uart_interface_example

On Wed, Jul 1, 2015 at 1:27 PM, Trent Lukaczyk twl26@stanford.edu wrote:

I tried flying this yesterday and did not get any response from my hex
while sending velocity commands.

On Sat, Jun 27, 2015 at 10:27 PM, super_mice notifications@github.com
wrote:

@xuliren https://github.com/xuliren What's the status now? Does the
master firmware fixed the velocity control problem?


Reply to this email directly or view it on GitHub
#1856 (comment).

  • Trent Lukaczyk
    Stanford University Engineering
    Cornell University Engineering 2010
    twl26@stanford.edu

  • Trent Lukaczyk
    Stanford University Engineering
    Cornell University Engineering 2010
    twl26@stanford.edu

@AndreasAntener
Copy link
Member

I think I found the missing piece: #2527

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

No branches or pull requests

7 participants