@stevet Thanks! We actually do have these, maybe we can just figure out the FOV of each camera from the respective data sheets.

This is all great, thanks so much for the quick response. I think our plan will be to get the VOXL CAM in its current state and get moving on development, and we'll be able to port to newer products soon after.

Do you have CAD models of the filed of view and placement for each camera on the VOXL CAM? Would help with our design a bit more

We're evaluating the VOXL product suite for our use case, and were hoping to get a few questions answered on here before we move forward with purchasing reference components. What follows is our best guess as to what we'd need to make our system function:

The system so far:

• 12 ESC-controlled thursters (12 PWM outputs)
• minimum 2 (potentially 4) actuators, servo-driven
• VOXL CAM, or most updated version of VIO hardware for complex computer vision-based flight control

The VOXL CAM itself seems to have the option to come with a full companion computer + flight controller: https://www.modalai.com/products/voxl-cam?variant=39593458860083. The main question here is whether we're going to be able to drive that many motors and actuators with the VOXL flight controller embedded in this package. If we can, it seems to make the most sense to buy the fully integrated hardware and have a full-fledged solution all in one place.

Additionally, it's unclear from the pictures how everything is packaged in the fully-integrated mode. Our fundamental concern is that to get the correct visual data from the onboard cameras on the VOXL CAM, we might have to attach it a little further away from the current center of mass of the chassis we're developing. If the whole package is in one piece, that might put a lot of mass at the end of a relatively long moment arm, which is something we'd like to avoid.

We would need full LTE/4G/5G support for this system, for BVLOS operation, so that's where the larger feature set of having the fully integrated companion computer is very attractive.

In addition, we've already purchased the M500 (https://docs.modalai.com/voxl-m500-quickstart/) as a reference for evaluating the full VOXL suite, and I was hoping to understand if we're able to leverage a lot of our learning/development/processes for the this VOXL CAM situation as well. Also, we received a marketing email regarding VOXL 2, and we're wondering if it's best to wait for that product to be released, or if there's a VOXL-2-based VOXL CAM system that's in the works.

Any insight you can provide would be much appreciated, looking forward to your reply!

I will try those steps ASAP. It looks like the RC radio is more of a nice-to-have failsafe in this mode, is that accurate? Thanks for the tip