Starling 2 Max is designed for 4S batteries only (two 2S Li-Ion battery packs, which are connected in series inside the vehicle). The Mini ESC, which also acts as a power source for VOXL2 inside the Starling 2 Max, is rated at least for 4S input (depending on the version of the ESC). There are several versions of the Mini ESC to provide the users some flexibility, in particular the voltage of the VOXL2 regulator (5V for VOXL2 and 3.8V for VOXL2 Mini). Since Starling2 Max uses a VOXL2, the ESC part number will be either M0129-5 or M0129-65. An updated (6S) version of the Mini ESC was released after the release of Starling 2 Max (new ESC part numbers: M0129-63, M0129-65). This ESC update extended the supported voltage for the ESC (not for Starling 2 Max) from 4S to 6S. The 4S version of the ESC has been phased out because the 6S version outperforms the original version even at 4S voltages (due to better Mosfets), so the 6S version is an improvement over the original 4S version of the ESC, while being fully backwards compatible. Using the 6S-rated ESC in the 4S-rated Starling 2 Max is completely safe. If you use the Mini ESC outside of the Starling 2 Max, you need to verify the part number / sticker on the ESC before plugging in 6S battery (M0129-63, M0129-65 only) The ESC variants and part numbers are documented here : https://docs.modalai.com/voxl-mini-esc-datasheet/ Alex

@JB1 Our voxl-remote-id software with WiFi dongle is intended only for reference and is not meant to be a commercially ready system for our customers who need a remote id solution for their VOXL2 based drone products. Integration, testing, validation, and FAA registration with desired hardware is up to the end user. At a minimum the manufacturer id would need to be changed from ModalAI's id to your companies issued manufacturer id.

Hi @Nikola-Rudjer , The forum is for technical support -- for sales questions, please reach out to us via https://www.modalai.com/pages/contact-us Alex

@chengyouzen , have you tried building OpenSSL from source (you should be able to do it directly on VOXL1)? That may be the only way.. Alex

@Tutu-Wen No, stinger has no GPS Yes Yes, all compute is onboard and the VOXL SDK is open source:https://gitlab.com/voxl-public/voxl-sdk

Hello @daz_22 , The ideal intrinsics of the IMX412 camera module (M0161) are as follows: Full resolution: focal length : 1999 (~2000) pixels principal points: 2028, 1520 (for full frame image, such as 4056x3040 or 4040x3040) 2x2 Binned resolution focal length : 1000 pixels principal points : 2028/2, 1520/2 For other resolutions, you can adjust the principal points to be half of the width and height because the cropped image (in case of 3840x2160 or 1920x1080) will be centered. The lens model is fisheye and you should set the distortion coefficients to zeros unless you calibrate them. If you are going to calibrate the camera using voxl-calibrate-camera, it is very slow at full resolution, so i suggest calibrating at half resolution. Here is an old calibration result I found for one of these cameras, just for reference: %YAML:1.0 --- M: !!opencv-matrix rows: 3 cols: 3 dt: d data: [ 999.5391440104593, 0.0, 1016.522606127024, 0.0, 998.2572561064064, 750.2875966666587, 0.0, 0.0, 1.0 ] D: !!opencv-matrix rows: 4 cols: 1 dt: d data: [ -0.02176119101007071, 0.01025514886831165, -0.01688007838706262, 0.006525270203215156 ] reprojection_error: 0.72238 width: 2020 height: 1520 distortion_model: fisheye calibration_time: "2024-11-15 16:38:58"

@tom Thanks Tom. I already checked the link. I understand that for gpu delegate "gpu" needs to be specified in /etc/modalai/voxl-tflite-server.conf. My question is what value needs to be used in this configuration file to trigger npu deployment. According to my exploration, specifying "npu" is the same as specifying "gpu". cpu monitoring reports there are 8 cpus for sentinel. Which of the 8 cpus are opus? Looking forward to hearing from you.

Hi, were you able to find a solution I ran into the same problem.