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

vmount: Implement ROI_WPNEXT_OFFSET #9084

Merged
merged 5 commits into from
Mar 19, 2018
Merged

vmount: Implement ROI_WPNEXT_OFFSET #9084

merged 5 commits into from
Mar 19, 2018

Conversation

bkueng
Copy link
Member

@bkueng bkueng commented Mar 15, 2018

@DonLakeFlyer can you cross-test this?

Assumes the offset angle from the mavlink message is in degrees (the message does not specify it).

fixes #9082

@DonLakeFlyer
Copy link
Contributor

Awesome, will do.

@DonLakeFlyer
Copy link
Contributor

Testing using attached plan file and make posix gazebo_typhoon_h480. The plan sets the roi to a yaw offset of 90 degrees at waypoint 2 and turns it off at waypoint 4.

Results:

  • MIS_MNT_YAW_CTL Enabled - Gimbal yawed correctly to 90 degrees after WP 2. At WP 4 it also appeared to cancel and re-center. A little hard to tell since center gimbal on gazebo seems a little flaky positionally.
  • MIS_MNT_YAW_CTL DIsabled - Did not work. Vehicle did not yaw 90 degree. Continued pointing to next waypoint.

roi.plan.txt

@LorenzMeier
Copy link
Member

@DonLakeFlyer I don't fully understand the test result yet. Are you saying the first test was ok and the second test failed?

@DonLakeFlyer
Copy link
Contributor

There are two modes for ROI style commands. They depend on whether the gimbal on the vehicle supports yaw or not. If the vehicle has a gimbal with yaw support then MIS_MNT_YAW_CTL=Enabled specifies this. In that case any ROI command should just yaw the gimbal to point the camera the right way. The other case if that either the vehicle has no gimbal, or the gimbal it has does not support yaw. In that case the vehicle itself needs to turn to point camera to ROI. This is specified by MIS_MNT_YAW_CTL=Disabled.

The case where MIS_MNT_YAW_CTL=Disabled is not working. The vehicle does not yaw to the ROI offset.

@bkueng
Copy link
Member Author

bkueng commented Mar 16, 2018

@DonLakeFlyer I wasn't aware that MAV_CMD_DO_SET_ROI_WPNEXT_OFFSET is supposed to affect the vehicle's yaw depending on MIS_MNT_YAW_CTL. Anyways, I added that now in the last commit. Can you test it?
I cannot open the plan you provided, QGC tells me the mission file is not compatible (I'm using latest master).

@DonLakeFlyer
Copy link
Contributor

MIS_MNT_YAW_CTL DIsabled - working perfectly now.

I cannot open the plan you provided, QGC tells me the mission file is not compatible (I'm using latest master).

What error are you getting? I can open it in both Stable and master.

@bkueng
Copy link
Member Author

bkueng commented Mar 16, 2018

What error are you getting? I can open it in both Stable and master.

It turned out to be the file extension. The downloaded file from github was named roi.plan.txt. After renaming to roi.plan, it worked fine.

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.

Implement ROI_WPNEXT_OFFSET
3 participants