using R.O.I to film a high altitude object, limits of the variables.

Hi Guys

I have a project, as indicated above, to track a high altitude object.

It appears to be feasible to use a gimbal inverted and set the ROI altitude to a large value. I have not yet discovered what the variable range allows. Mission planner lets me enter 35000000 metre's for example but that does not mean a mission would initiate. Too cold, wet and windy to prove it here.

Could someone point me in the direction of the code variable types or, hopefully, tell me you already have such a project ongoing.

Many thanks in advance

keith

Views: 215

Reply to This

Replies to This Discussion

If your talking about a High Altitude Balloon I'm interested. What is ROI? What are you trying to do exactly?

Hi Monroe

R.O.I means region of interest in this context.

Obviously this Mavlink parameter is normally used to point a camera at an object, a building typically, while flying a mission.Imagine circling the building while filming it.

My plan is to use this functionality to point at an object at high altitude while the craft is moving. Thus maintain a comms link from said high altitude object.

That makes some sense I use the antenna tracker to do that. I'm not familiar with that function of Mavlink or how it works. Can you enlighten me? Perhaps I can help.

Put simply, an auto mission created within mission planner would contain a line defined as "DO_SET_ROI". This takes 3 parameters Lat, lon and altitude.

The command would be contained within a body of other lines that would launch and set the copter off on its mission.

So long as the altitude parameter can cope with 35000000 metres i cannot think why this would not work.

Obviously the camera on the gimbal, which is typically what you would use this routine for would be replaced by a suitable antenna to recieve the signal.

What we do with the downlink data is not relevant to the success or otherwise of using the "DO_SET_ROI" capability

Reply to Discussion

RSS

© 2020   Created by Chris Anderson.   Powered by

Badges  |  Report an Issue  |  Terms of Service