@Eric-Katzfey Got it working about 50% of the time. It seems like most of the time it is just the uvc server trying to connect. I am going to see if I can create a service file around it. Maybe restarting on fail will get it to work with a bit of delay in between. A bandaid for the issue, but at least it will work

Hi Jeff, There's not so much a minimum height as a minimum amount for it to see. If you look at our seeker platform, the tracking camera is only 3cm above the ground, but to compensate for this the drone sits leaning back so that the camera is angled slightly upward when it's landed. If your drone sits on the body and the camera is facing down, you won't be able to take off with VIO, so you'll need to find some combination of height off the ground and angle that allows the camera to see a decent amount of its field of view in order to take off successfully.

Hi James, Thank you for your help! I am yet to inspect the VOXL flight deck for the connectors. I would like to test out the new branch. Thanks and regards, Mohammed Naveed

@Chad-Sweet Thanks Chad, and I will double-check the detail with OmniVision then.

@Alex-Gardner thank you very much

@Eric-Katzfey yep it worked! Thanks for the quick reply.

If you could run camera server manually with additional debug prints (i.e. voxl-camera-server -d 0) and paste the output here, you'll be able to see more info about whats going on that'll make it easier to debug

@Steve-Arias, Once you have voxl-portal started either via the command line or as a service, you can access the webserver on a device within the same network just by navigating to your voxl's IP address.

These are the dampeners we are using on VOXL Flight The dampening may needed to be tuned for your flight platform though, and can definitely be different depending on flight dynamics. We have had a lot of success sticking a piece of foam between the plate and the frame. https://www.amazon.com/gp/product/B073LPTHCL/ref=ppx_yo_dt_b_asin_title_o02_s00?ie=UTF8&psc=1

are you sure that this is the Vibration damper that you are using? cause your 3D cad model calls for a damper with different dimensions: [image: 1641735336418-b6107c8a-e568-4839-99d0-4387f6c68533-image.png] please advise which damper are you using in your Voxl flight deck.

It appears this happens when the sensors are not calibrated on the drone. voxl-vision-px4 picks up on sensor inconsistency and restarts PX4. So, calibrated the sensors. Looks better resolved

@omer-b thanks!! Added: [image: 1640270590811-5dc619fb-ca85-4b54-9d6a-e6e9c4567512-image.png]

Thank you.

@Shlok-Agarwal I assume you've taken a look at this page in our docs: https://docs.modalai.com/unbrick-voxl/ If not, give that a read through and it'll give you a bunch of good info. Were you able to ADB into the VOXL before you started the flashing process?

@Nirge You should use voxl-wifi for wlan0.

I found the QGC EKF2_AID_MASK parameter settings above (configuring to 280: Vision position fusion, vision yaw fusion, vision velocity fusion) to allow the seeker to enter position and off-board modes. Prior to configuring, QGC was receiving VIO but was still unable to enter position mode as referenced here To make the forum search engine happy: seeker position mode rejected