@jakkkkobo

Hello,
We currently do not ship any mask files with our airframes, as they are normally not required. In addition, you should be able to use a mask with minor modifications on the server side, namely VoxlCam directory inside voxl-open-vins-server repo. (The mono camera case should be a good starting point, as we already have the masking logic for occluded cams during takeoff.)

Furthermore, as we use a custom interface/backend for OV, loading the mask as done in the traditional OV-ROS format won’t work as intended, i.e., via Yaml.

All the best,
ZBFT

@Aaky After that much use it could very well be ESD damage. It seems unlikely we would be able to fix via RMA.

@qubotics-admin Hi, we sell all of those components for companies to integrate into their products.

The Flir Hadron adapter (MDK-M0202-1-00) can be requested by reaching out to sales at https://modalai.com/contact

The rest of the components should be available to purchase at modalai.com

@JoonaR Hi Joona, the DP should work to drive an HDMI projector with the appropriate adapter. This adapter has been tested to work: https://www.amazon.com/Cable-Matters-48Gbps-Adapter-Supporting/dp/B08MSWMXT4?th=1

@Piyush-Singh Have you tried voxl-camera-server -d0 found here https://docs.modalai.com/voxl-camera-server/#troubleshooting ?

You cannot plug in cameras arbitrarily, you'll need to use one of the supported camera configurations: https://docs.modalai.com/voxl2-camera-configs/

@Rowan-Dempster thank you for sharing this! Does this mean you can create a custom data file partition that you can flash using fastboot? We have not explored this before but it has been asked a few times. This could be very helpful for other developers.

@colombe-ai currently 30 business days is quoted on the website: https://www.modalai.com/products/starling-2-max

It typically should ship more quickly than that though, likely 2-3 weeks

There is no overnight shipping option as all of the drones are built to order

@colombe-ai

You can find the batteries here: https://www.modalai.com/products/m10000538
Any 2S LiIon hobby charger will work. Something like this is all you need: https://www.amazon.com/ISDT-608PD-Battery-Charger-Discharger/dp/B0CM9BFQSX

Handheld transmitter depends on the configuration of the drone. You can order the drone with a pre-bound charger ready to fly from the website.

The main debugging cable is a standard USB-C cable

@YUUJI-INOUE
Hello there,
Here are a few things to be aware of:

• VVHUB "Error" for missing extrinsics for imu_body

This is not really an error, just tells you that the IMU in body frame and the body frame itself are connected by the identity. In other words, there's no transformation needed for the IMU data from VVHUB standpoint.

• Position Mode not engaging

Assuming you're able to get the drone arming in Manual/Altitude mode. Are you using VFC in your VVHUB conf or using the classic PX4 position mode? -- If your drone resembles the Stinger D0013, VFC is the suggested format. -- you can use the wizard to configure VVHUB accordingly. Can you confirm your VVHUB setup? Please attach your vision-hub and vfc .conf

• VIO not working

As you described, different frames, different noise characterization. You can change the IMU noise values inside the kalibr_imu_chain.yaml (in the directory you found estimator.yaml). Personally based on your description, I am inclined to believe your performance issue is rooted in your extrinsics values and VVHUB configuration. Did you use Kalibr? -- If you used Kalibr with imu_body pipe, all you have to do is to replace the SE(3) elements inside kalibr_imucam_chain.yaml and make sure the sync_config flag inside voxl-open-vins-server.conf is set to false. Otherwise, unless you have a proper CAD model, physically measured values will likely be inaccurate and cause the estimator to diverge. For future help, please attach all your VIO-related yamls and your voxl-open-vins-server.conf

All the best,
ZBFT

@Sarika-Sharma ,

The preview width and height parameters are always in the camera config file, so if you added them, they are duplicates (and will be ignored).

Please read through this thread as it has pretty detailed explanation how to configure the correct tof sensor (old or new) for a custom configuration.

Camera-server-config-helper is indeed helpful. If you use it correctly, you should not have to manually modify the resolution in the config file.

If you still cannot get this to work, please let me know what cameras you have plugged in (and which camera ports) on your voxl 2 mini.

Alex