Replies to This Discussion

Permalink Reply by James on June 28, 2012 at 11:56pm

michael,

now that youre back i wonder if youve seen this from a couple of weeks ago.

james

• ▶ Reply

DeveloperPermalink Reply by Michael Oborne on June 29, 2012 at 2:17am

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.

• ▶ Reply

Permalink Reply by James on July 12, 2012 at 6:17am

michael,

although i still have some hope that we will decide how best to implement more of the DO_SET_ROI specification, in the meantime i wonder if we can at least return to the functionality that we had in AC2.55 over MAVLink 0.9 (i dont remember exactly which version of MP)

i know the full specification is impossible with the current WP storage, but a DO_SET_ROI message with the parameters: [3, lat, long, alt] was working and is good enough for me to script some simple photography flights.

please, please, please!

james

• ▶ Reply

DeveloperPermalink Reply by Michael Oborne on July 12, 2012 at 6:25am

it doesnt still work?

• ▶ Reply

Permalink Reply by James on July 12, 2012 at 6:39am

no, it throws this error when writing waypoints:

Requested value 'DO_SET_ROI' was not found.

at ArdupilotMega.GCSViews.FlightPlanner.saveWPs(Object sender, ProgressWorkerEventArgs e)

at ArdupilotMega.Controls.ProgressReporterDialogue.RunBackgroundOperation(Object o)

james

• ▶ Reply

DeveloperPermalink Reply by Michael Oborne on July 12, 2012 at 6:53am

do set roi is no longer a valid command

nav_roi might work though.

• ▶ Reply

DeveloperPermalink Reply by Michael Oborne on July 12, 2012 at 6:56am

what is the new packet for this? is this part of the ap_mount library?

• ▶ Reply

Permalink Reply by James on July 12, 2012 at 7:13am

no this has been in AC for some time (no idea how long), using yaw to orientate the whole craft towards the ROI.

it should obviously be closely related to the new AP_Mount code, but i didnt have much luck getting any details of how that would be scripted.

im looking at the differences between MAV_CMD_DO_SET_ROI and MAV_CMD_NAV_ROI and while they are similar its not exactly the same.  will have to go through it in more detail this evening.

regards,

james

• ▶ Reply

DeveloperPermalink Reply by Michael Oborne on July 12, 2012 at 7:19am

               <entry value="80" name="MAV_CMD_NAV_ROI">
                    <description>Sets the region of interest (ROI) for a sensor set or the vehicle itself. This can then be used by the vehicles control system to control the vehicle attitude and the attitude of various sensors such as cameras.</description>
                    <param index="1">Region of intereset mode. (see MAV_ROI enum)</param>
                    <param index="2">MISSION index/ target ID. (see MAV_ROI enum)</param>
                    <param index="3">ROI index (allows a vehicle to manage multiple ROI's)</param>
                    <param index="4">Empty</param>
                    <param index="5">x the location of the fixed ROI (see MAV_FRAME)</param>
                    <param index="6">y</param>
                    <param index="7">z</param>
               </entry>

looks like what you want, which is just ROI in the planner the field names need changing though

• ▶ Reply

Permalink Reply by John Wiseman on July 12, 2012 at 10:30am

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...

• ▶ Reply

Permalink Reply by James on July 12, 2012 at 1:33pm

thanks john,

that certainly clears up the why its stopped working, where do you compare the mavlink definitions?

james

• ▶ Reply

DeveloperPermalink Reply by Michael Oborne on July 12, 2012 at 3:58pm

check

mavlink_mount_configure_t

• ▶ Reply