@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.

@JB1 I'll look into your questions. There is no RTC on VOXL2.

@bschulzhf ,

I have just posted the drivers for testing here : https://storage.googleapis.com/modalai_public/temp/imx412_test_bins/20260529/imx412_drivers_20260529.zip

These have the mipi bit rate adjusted slightly from 2100Mbps to 2088Mbps as the latter has shown very little interference based on the prior tests.

These drivers have the following resolutions / modes -- note that two modes use higher bitrate (2200Mbps) in order to achieve the required throughput -- 2200 also seems safe.

Mbps: 2088, 4056x3040, 30.0 fps
Mbps: 2088, 4040x3040, 30.0 fps
Mbps: 2200, 4040x3040, 60.0 fps
Mbps: 2088, 3840x2160, 30.0 fps
Mbps: 2088, 3840x2160, 60.0 fps
Mbps: 2200, 3840x2160, 80.0 fps
Mbps: 2088, 2028x1520, 30.0 fps
Mbps: 2088, 1996x1520, 30.0 fps
Mbps: 2088, 1996x1520, 60.0 fps
Mbps: 2088, 1996x1520, 120.0 fps
Mbps: 2088, 1936x1080, 30.0 fps
Mbps: 2088, 1936x1080, 60.0 fps
Mbps: 2088, 1936x1080, 90.0 fps
Mbps: 2088, 1936x1080, 120.0 fps
Mbps: 2200, 1936x1080, 240.0 fps
Mbps: 2088, 1920x1080, 30.0 fps
Mbps: 2088, 1920x1080, 60.0 fps
Mbps: 2088, 1920x1080, 90.0 fps
Mbps: 2088, 1920x1080, 120.0 fps

In order to allow the system to use all the modes, please double check that the following setting is set correctly in /vendor/etc/camera/camxoverridesettings.txt:

maxRAWSizes=20

We will be doing more testing but most likely these updated drivers will become the official ones in an upcoming SDK release.

Alex

@jon And you can find a lot of detailed information about the agent, including the start options, here: https://docs.px4.io/main/en/middleware/uxrce_dds

@Michael-Hatton When you arm the drone it is in flight mode and the motors start to spin. It's that spinning of the motors that you don't want while plugged into a power supply. Only use your battery to actually spin the motors and fly.

@Eyal , sorry for the delay. Here is some additional information regarding Stinger FPV:

• https://docs.modalai.com/stinger-vision-datasheet/
• base weight with battery : ~570g
• maximum thrust per motor : 650g @ 15V, 2600g total theoretical
• theoretical max thrust to weight ratio: 4.5:1, lots of extra margin, but if you add a LOT of weight, will need to check motor temps, etc.
• CAD model for stinger (may be slightly outdated) : https://forum.modalai.com/topic/5180/looking-stinger-fpv-cad-models -- you can attach your payload to carbon fiber
• I think that Stinger will be easier to tune up with additional payload because of more responsive and powerful propulsion system than Starling 2.
• i dont know what your sensor package is so, it is hard to comment about which platform is better. Starling 2 has landing gear that offsets it from the floor. Stringer is much lower to the ground.

Alex

@jon you can edit the dds via updating systemctl service file and point it towards the serial UART instead of a udp socket/port - the og looks like this:

[Unit]
Description=voxl-microdds-agent
SourcePath=/usr/bin/MicroXRCEAgent
After=network.target
After=multi-user.target

[Service]
User=root
Type=simple
ExecStart=/usr/bin/MicroXRCEAgent udp4 -p 8888

[Install]
WantedBy=multi-user.target

You would replace the -p with whatever flag is used for serial and then put /dev/ttyHSX (X number depends on which uart you are plugged into) - you will most likely need to put in a baudrate as well. This file is stored in /etc/systemd/systemd/voxl-microdds-agent.service.

@Jskim This is the repo we use for support of UVC cameras: https://gitlab.com/voxl-public/voxl-sdk/services/voxl-uvc-server. I don't think it will work directly with Seek cameras but you can try. In my experience each new camera requires a bit of integration work and updates to that code.

@JB1 FYI: The code repo is here: https://gitlab.com/voxl-public/voxl-sdk/services/voxl-remote-id. You can see my commits on the dev branch.

@JB1 Yes, you are correct. It has been updated to use the 10 character ID. You can find the updated package here: http://voxl-packages.modalai.com/dists/qrb5165/dev/binary-arm64/voxl-remote-id_0.1.0-202605281019_arm64.deb