ive just updated to AC2.6 and therefore started using APM planner MAV 1.0
ive been working recently with the DO_SET_ROI command (only Yaw_mode 3 currently supported by AC - i mean to get all the modes working), and have come across an error when trying to write a mission containg this command to APM:
Requested value 'DO_SET_ROI' was not found.
at ArdupilotMega.GCSViews.FlightPlanner.saveWPs(Object sender, ProgressWorkerEventArgs e)
at ArdupilotMega.Controls.ProgressReporterDialogue.RunBackgroundOperation(Object o)
in AC2.5.5 this worked, i have simply added the command to mavcmd.xml, as its in the documentation i think it should really be standard:
<DO_SET_ROI>
<P1>Yaw_mode</P1>
<P2>WP ROI #</P2>
<P3></P3>
<P4></P4>
<X>Lat</X>
<Y>Long</Y>
<Z>Alt</Z>
</DO_SET_ROI>
------------------------
and .. now that im on the subject ..
when creating a mission with a DO_SET_ROI command, once focus is lost from the command its made invisible in the map view. at least for yaw_mode = 3, which actually specifies a location to point at i think the command should stay visible on the map. obviously its not part of the route so it shouldnt really appear as a waypoint on the planned route, but a marker just like the waypoints in a different colour would be great.
any chance of looking into these points?
regards,
james
Replies
DO_SET_ROI is in mavlink 0.9, but not in mavlink 1.0. I'm not sure if it's intentional. See https://groups.google.com/group/mavlink/browse_thread/thread/508971...
the whole issue here is that set ROI hasnt been implemented, and ac and ap dont have the command space to store all the settings in eeprom.
michael,
now that youre back i wonder if youve seen this from a couple of weeks ago.
james