@qqa , we have document how to achieve folder-level encryption on VOXL2 here : https://docs.modalai.com/enabling-file-encryption/ . Please let us know if you have any other questions.

@Irfan-Usman Sure, see these documents VOXL 1 & VOXL CAM: https://docs.modalai.com/how-to-connect-voxl-to-pixhawk/ VOXL 2 (recommended): https://docs.modalai.com/voxl2-external-flight-controller/

see https://forum.modalai.com/topic/3640/ardupilot-on-voxl2

Hi @jacobcayetano1 There are still over 500k units in available distribution which we can access. I would not worry at all at this time and I fully expect we can still build FCv2 as is for years to come. Our parts sourcing expertise is top notch! (not sure if you recall but during the parts shortage craziness of 2020-21 we were one of the few vendors who still had product in-stock and shipping!!) If you had a large order in mind, any head's up is appreciated so we can be sure to have sufficient stock. Thanks!

@Alexander-Saunders Looks better now. What does the dsp_hitl start command look like now? Seems like it is setup for VIO only.

@Samuel-Bryan Sure, source is here: https://gitlab.com/voxl-public/voxl-sdk/services/voxl-portal

@Moderator Hello, Thank you very much for your prompt response and for providing the link to the datasheet for the VOXL 1 connectors. This information is exactly what I needed. I appreciate your assistance and support.

@Joshua-Ermias yes that would be the easiest way. You can either restart the service with systemctl restart voxl-camera-server or just power cycle your VOXL

@Vinny @Moderator Thank you for the response. The reason why we suspected a power issue is that the Flight Core PX4 logs have gaps in data. My apologies as I should have included that info initially. Here is an example from manual setpoint data. [image: 1716303716023-6b5c0659-91f0-424d-93ae-6f5fb178bcb8-image.png] Here is a scatterplot for throttle manual setpoint data to show that those straight lines on the line graph are indeed gaps in data and not inhumanly smooth setpoint changes. [image: 1716303554866-bdc82181-0b10-4f33-a424-a91274f00989-image.png] These gaps are consistent across all the data in the log, which led us to hypothesize that power was lost during these instances. We are using a custom controller that employs SBUS joystick protocol through QGC. Let me know if this info sparks any other ideas or is reminiscent of another issue.

@viralp https://docs.modalai.com/image-sensor-flexes-adapters/#extending-mipi-image-sensor-cable-lengths

Unbricked! Here's some context/advice for anyone trying to do the same. If you purchased a cheapo STLINK V2 from Amazon as I did. Picture below... [image: 61TfQhFysAL._AC_SX679_.jpg] $0 Fix: What may very well happen to ya, is the RESET pin doesn't work. In this case you will need a friend. With said friend, you must dilligently connect to the board using Under Reset Mode and Hardware Reset. The second your homie clicks the connect button, you, the bricker of the board must move your jumper cable from the RESET pin which is 3.3V to an open Ground, leave it for exactly 1 second, then move it back to RESET. This should work like a charm, but may require one or two tries to get the right timing. See instructions below. [image: raiders.jpg] $10 Fix: Program a Pico/Arduino to do your 1 second ground for you. $78 Fix: Buy the real STLINK V2.

@Alex-Kushleyev I figured it why the orientation estimator wasn't running after reading through this post, where that user had the same (plus a few more) problems: https://forum.modalai.com/topic/1755/setup-problems-on-new-boards-sensors-and-qgc-connection-problems/18 Basically the problem is that the firmware as-shipped assumes you have at least one active mag, but that the built-in one isn't active. The documentation didn't say how to change the PX4 parameters to make it work without one. The default build does not start the built-in mag, so if you don't have an external plugged in (as in my use case), then EKF2 gets stuck while looking for the reading for one without any error printout, making it unclear what the problem is. I initially tried the version of activating it by adding the boot line to the etc folder of the sd card, and that worked once, but then it got deleted on the next reboot for unknown reasons. That is an easy enough fix with just a firmware rebuild where the magnetometer is started by default. That really is the version you should ship unless you are going to specify in your documentation that the as-shipped version will need an external mag to function. With the firmware as-is, you have to change two parameters on PX4 to make it work, specifically you have to turn off EKF2 magnetometer fusion and whether or not the system has a mag at all. Ie. EKF2_MAG_TYPE to NONE and SYS_HAS_MAG to Disabled. After doing that it will run. Still haven't sorted out the issue with the telem lockout. I'll see if that got fixed with EKF2 now running normally.

@boga Sorry, yes, I was referring to VOXL 2.

@Amin-Bassiri There will always be some reprojection error when computing a homography, as long as the error is below 0.5 (which it looks like yours is) you should be totally fine. Let me know if you have any other questions! Thomas