@nekolny You should be able to use voxl-mavlink-server --help to see the various debug options available. You can stop voxl-mavlink-server from running as a service and then start it manually from the command line with the desired debug options to see which messages it is getting from the autopilot and what it is sending to QGC (and vice-versa). Then you can also use tcpdump to look at the IP traffic on both VOXL 1 and the QGC computer to see which messages are being sent.

@nekolny , you should use a linux PC to run voxl-esc tools in order to connect to the ESC and check / update the ESC firmware. VOXL1 does not have support for voxl-esc python tools to communicate directly with the ESC.

Alex

Thanks..

@Samuel-Lehman In this case you are setting up the voxl-streamer outputs. voxl-mavcam-manager simply informs QGC about which outputs are available to it. You don't need to do anything manually. Just set up a systemd service file for each instance of voxl-streamer. (for example: /etc/systemd/system/voxl-streamer.service)

Thanks a million @Alex-Kushleyev that certainly explains the effect - I really appreciate you taking the time

I understand now @Alex-Kushleyev thanks for the explanation

@Eric-Katzfey I had not since this discussion was the closest I could find to my issue. But I have created one now: Cannot see obstacle_distance_fused on QGC

Hello @Kiran , the only TOF sensor that we currently sell is the following:

https://www.modalai.com/products/m0178?variant=48528287793456

https://docs.modalai.com/M0178/

In terms of identifying unique features of individuals, you will have you decide whether this works for you. Here is a typical output of the this TOF sensor looking at a person. This is a depth image, but a point cloud output (for each frame) is also available. In order to build a map, you would need to use some mapper software (we provide a reference such as https://docs.modalai.com/voxl-mapper/). However you would need to be familiar with mapping algorithm(s) and learn how the software components work in order to get mapping to work well and tune it for your application.

9b4bee44-2643-4aed-a20f-4ec2592af56b-image.png

Alex

@AidanGallagher , I have updated the IMX412 drivers to support stable 4040x3040 60FPS.

Just for full disclosure, the camera in this mode is slightly overclocked from 2.1Gbps / lane to 2.2Gbps MIPI bit rate (voxl2 supports up to 2.5Gbps) in order to allow sufficient time between EOF and SOF. This is within 5% of the camera spec and seems to work fine.. If you do not feel comfortable using this mode, don't :). (only the specific 4040x3040 60fps mode has been changed).

We are going to continue testing this mode because it allows doing things like EIS at 4K60 without losing any vertical stabilization margin. If there are any issues with it, I will report back.

By the way, for best image quality, even if you don't need 4K output, but lets say 1080p, in the case of unstabilized video (no EIS), you should select 3840x2160 input and 1920x1080 output. The debayering process loses sharpness, so going from 1920x1080 RAW -> 1920x1080 RGB is going to be worse quality than 3840x2160 RAW -> 1920x1080 RGB. For unstabilized video you do not need the full frame because the top and bottom will be cropped out anyway, so reduce the waste and not select the full frame resolution (4040x3040). You can experiment using the different input resolutions to see what output quality (sharpness) you get. There is currently no option to do output sharpening when using MISP, but we will look into in the future. The down side of using higher resolution input is increased GPU usage (should not be an issue) and longer readout time (the rolling shutter artifacts will be more pronounced).

https://storage.googleapis.com/modalai_public/temp/imx412_test_bins/20250409/imx412_fps_eis_20250409_drivers.zip

- 4056x3040 @ 30 16.5ms readout time - 4040x3040 @ 30, 60 16.5ms readout time - 3840x2160 @ 30, 60, 80 11.8ms readout time - 1996x1520 @ 30, 60, 120 5.5ms readout time - 1936x1080 @ 30, 60, 90, 120, 240 4.0ms readout time - 1996x480 @ 30, 480 1.8ms readout time - 1996x240 @ 30, 800 0.9 - 1.0 ms readout time

@brahim Thanks for this advice!

I'm working on Windows with WSL and it is impossible for me to build the docker image by following the instructions on the voxl-docker-mavsdk README.

I'm still unsure why the image build on the VOXL and not on my WSL Ubuntu, but at least I got it to work.

@voxl-phoenix , this may be a hardware issue because VOXL2 will boot just fine without M0173 camera front end plugged in (if the hardware is OK). It is possible that one of the camera connectors (where M0173 plugs in) has broken off or is loose, causing a hardware failure. If you would like a better diagnosis, please share a video of the voxl2 not booting, so we can see the LEDs (i realize there are green leds on top and bottom, but the way your image shows, you can see both of them. Also, in this non-booting state, does the VOXL2 show up as any USB device when plugged into a linux machine using the main USB C connector?

Alex

@astro_phil , unfortunately if the device is not automatically being detected by VOXL2, you may be on your own in terms of building the kernel module for it. Please search the forum for building kernel modules, as some users have tried this. Specifically, this one : https://forum.modalai.com/topic/3841/voxl2-kernel-version/ and maybe a few others as well.

Alex

@newdroneflyer

The different operating TOF modes (for the TOF V2 sensor on Starling 2) are described here in terms of power usage and fps : https://docs.modalai.com/M0178/#irs2975-operating-modes . We do not have exact information, but the different modes emit different amount of IR power and using different modulation schemes. The operating modes are tuned for the different ranges as stated (ultra short, short, mid long), which means depending on your application, you can choose one or the other.

The number of sampling points per frame is the same for each mode, but FPS can be chosen based on what you need and it has to be within the provided specs (short range allows you to use higher fps).

We have not done specific studies to measure the performance of the sensor to the detail that you are asking about.

I can collect some data for you if you need. What format? There are also some tuning parameters, that can be tuned (can be found here with some comments : https://gitlab.com/voxl-public/voxl-sdk/services/voxl-camera-server/-/blob/master/src/tof_interface.cpp?ref_type=heads#L1033) . You would probably need to experiment yourself if you wanted to get the best performance out of the sensor.

Alex

@Ege-Yüceel You can find our warranty information at https://www.modalai.com/warranty

You can find the STEP file for the design here: https://docs.modalai.com/starling-2-datasheet/#starling-datasheet

Starling 2 replacement parts can be found here: https://www.modalai.com/products/starling-2-replacement-parts

If there is a part you need, we can make it available for purchase.

Hi @kestrelsystemsbp , the GPS interference is an ongoing investigation and there are several threads about this on the forum. For Starling 2, we found that moving the wifi dongle to a different location (or offsetting the GPS receiver) helps with interference (it is located right under the gps receiver). Also, elevating the gps receiver and shielding, should help. Please also read through the following discussion related to Starling 2 Max : https://forum.modalai.com/topic/4226/starling-2-max-no-gps-data/

I am not saying that you need such a big mast, but you may need to experiment a bit to figure out how to improve.

I am sorry for the inconvenience and let me know if you need any guidance for checking the signal strength, as described in the other thread. You do not have to use the live streaming plot for checking the individual signal strength -- you could do it directly using the terminal.

enable satellite info to be published from px4 (and start voxl-px4) param set GPS_SAT_INFO 1 query satellite info using px4-listener: px4-listener satellite_info TOPIC: satellite_info satellite_info timestamp: 2611309684 (0.868903 seconds ago) count: 13 svid: [5, 8, 10, 13, 15, 18, 23, 24, 27, 32, 131, 133, 138, 0, 0, 0, 0, 0, 0, 0] used: [1, 1, 1, 0, 1, 0, 1, 1, 0, 1, 1, 1, 1, 0, 0, 0, 0, 0, 0, 0] elevation: [11, 1, 30, 11, 47, 64, 68, 59, 13, 15, 27, 19, 33, 0, 0, 0, 0, 0, 0, 0] azimuth: [74, 232, 213, 36, 37, 138, 241, 85, 209, 172, 165, 173, 158, 0, 0, 0, 0, 0, 0, 0] snr: [0, 0, 26, 17, 32, 14, 29, 30, 15, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0] prn: [5, 8, 10, 13, 15, 18, 23, 24, 27, 32, 131, 133, 138, 0, 0, 0, 0, 0, 0, 0]

In open sky conditions, you should have a number of satellites above 40dB (which is not the case in this example i just pasted above). You can see the examples of the good and bad signal in the Starling 2 MAX thread i mentioned above.

Alex

@vjuliani , the tracking camera ( i assume ov7251 or AR0144) is monochrome, so you can not make the image colored. You can install the latest version of the voxl-streamer from dev (nightly builds) http://voxl-packages.modalai.com/dists/qrb5165/dev/binary-arm64/ and it should allow you to encode h265.

Alex

the fix has been committed to voxl-camera-server dev branch : https://gitlab.com/voxl-public/voxl-sdk/services/voxl-camera-server/-/commit/520bad13a573dde500d36cf1008e67102e0b6078 . I tested it for the rotated and non-rotated use case using voxl-streamer.

Alex

@jcai, I just tested this. I do see that "Removed 1 sessions" message comes in after ~1 min after the first disconnect, but my second session is not interrupted when this happens.

Please make sure you are using the latest version of voxl-streamer (you can try from nightly dev build). Also, something to double check, whether the two sessions are coming from the same or different port (maybe if you are using vpn or something, there new session starts from the same client port).

Alex

@Vinny
As per the parameters you provided, this sensor cannot operate at temperatures below 0 degrees Celsius.

Thank you!