Seems like VIO hasn't started up, that's why x & y are zeroed out.

Try:

voxl-reset-qvio

Check to see if x & y have returned if not

Another method to try is this:

systemctl restart voxl-qvio-server

I'd have to defer you to the software team can answer that specific question, but there is additional 16GB in /data partition

Oh no, sorry to hear that. Let's see what we can do to resolve that.
So as not to be redundant and streamline the process, what have you attempted already to unbrick the VOXL's?
Could you also provide further information on the board as well as what you were attempting to do before the VOXL's bricked? eg. software version, setup, camera config, computer setup, usb cables, power management, etc. The more information you can provide, the better we can help you.

@rohitpillai It is possible that the mipi connection got unplugged. It would be faster to drop off the Sentinel so that we can look at it

@darwin-keem sorry to hear you're having issues. You may want to check the camera connections again. If one of the camera connections is not fully seated, it'll prevent full boot of the VOXL2.
You mentioned that you plugged in the TOF. That might be the cause. Unfortunately, TOF is not yet fully supported on the VOXL2. We'll keep you posted when it does.

@Kevin let's see how we can fix this. First I want to go over what you've done to get the drone ready for flight to rule out everything. Have all the sensors been calibrated?(May need to do that again). Is this flying indoors? If so, the indoor parameters need to be loaded.
Can you post a pic of the services running? Also what version is flashed?

@rohitpillai the screw size is M1.6 X 0.35mm thread X 8mm long
You can find it here on McMaster-Carr or similar at link

@Daniel-Ryu Would it be correct to say that you've already configure mpa? Looking at the output from voxl-inspect-services, it looks like mpa hasn't started.
Might want to try that out if you have't already did

@Kris before turning on the Seeker, QGC works fine? Are you able to navigate around the gui?
Hmm...You could try deleting the px4 parameters that were loaded onto the voxl. You'll have to calibrate all the sensors and load the correct parameters if you do choose to go this route.
It kinda seems like there's something with the obstacle avoidance. May first want to try disabling en_voa in vvpx4 (marking it false) as well as disabling dfs server before deleting px4 parameters

@Kris yeah, that's an older version of QGC. Would recommend updating, could be a mismatch of settings.
After updating, check again local_position_ned
If that doesn't work, try loading platform 1.12 seeker parameters
If that doesn't work, try I'd shift to system_image 3.3.0 to see if that would change it. Be sure to save the data partition when asks to wipe.

@Kris wouldn't hurt to update QGC with the latest

@Kris in the page, scroll to the bottom

@Kris all Seekers get test flown before shipping to validate functionality. They are loaded with VOXL Platform 3.3.0-0.5.0, test flown with px4 platform 1.11 seeker & helper files for seeker ekf_2_indoor & spektrum_dx6e_config.
You can try loading the platform 1.12 seeker to see if that helps