@Daniel-Ryu same here. Please let me know if you figured it out.

@paul-foley , we do not have a repository for images.

My suggestions would be:

try using training sets from other sources (as you have been trying), but I don't have a specific reference in order to better match the 3rd party datasets to your use case, you should try to do the following: transform the 3rd party images to make them look more similar to what you are looking for (crop, zoom, resize, adjust color, etc). This can be automated transform the images collected on Starling to some standard, for example you can perform fisheye un-distortion to make them look more like the images taken from non-fisheye cameras from your training set, similarly adjust color if needed (white balance).

In general, if you can somehow standardize your images, and convert the 3rd party images to the same standard, you can greatly benefit from the large data sets that you could find online. The only down side that when running the model online, you will need to transform your images in real time, but that should not be a big deal. If you need to, I can help you with some GPU-based examples to do image transformation very quickly, but you should first make sure that this approach will work for you first (and optimize later 🙂 )

I hope this helps..

Alex

@groupo , can you please provide some more details:

are you using voxl-streamer to stream an h264 / h265 encoded stream (generated by voxl-camera-server) or is voxl-streamer consuming raw frames (raw8 or yuv) and encoding them to h264 / h265? If the input to voxl-streamer is not encoded, then voxl-streamer will encode them (using hardware video encoder) voxl-streamer is not set up to resize the image, so the image size is defined by the source that is providing the images or encoded video stream (most likely voxl-camera-server). you can modify your /etc/modalai/voxl-camera-server.conf to change the resolution of the stream that you are feeding into voxl-streamer (such as preview, small_video, large_video, etc) and that should automatically be reflected in the resolution that voxl-streamer outputs.

Feel free to provide more specific details about which exact stream (name) you are feeding into voxl-streamaer or let me know if you have any other questions.

Alex

@Jeremy-Frederick Those aux channels are implemented differently when getting manual control messages from QGC. The only one that is mapped is aux1 that comes from the "buttons" field of the corresponding MANUAL CONTROL Mavlink message.

@Jeremy-Frederick , the FPV ESC currently supports two pwm outputs, it can be tested using the following test script:

https://docs.modalai.com/voxl-fpv-esc-datasheet/#pwm-inputs--outputs (docs) https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-esc/-/blob/dev/voxl-esc-tools/voxl-esc-pwm.py (test script) make sure ESC firmware is 39.18 or later, as specified in documentation

The python script tells you which ESC boards support pwm output:

# PWM support on ModalAi ESCs: # M0049, M0117, M0134, M0129 : IDs 0, 1, 2, 3 # M0138: IDs 0, 3 only # All boards use pin A2 for PWM output

by changing the --id argument between 0 and 3 you should be able to use this test script to control PWM outputs of the two test points of M0138 ESC . Please be careful soldering to the test points as they are small and avoid pulling on the wires (use strain relief).

We are also working on enabling a 3rd pwm output on the output that is currently used for the Neopixel LED (this output is also pwm capable).

In terms of integration, standalone testing can be done using this python script, but sending pwm commands have to go through PX4, and we are working on integration.

You can use the following tool which will send a message to PX4, which will get forwarded to the ESC:
https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-mpa-tools/-/blob/sdk-1.3.4/tools/voxl-send-esc-pwm-cmd.c . Note that this tool has been moved to another repo after sdk 1.3.4 , but you should be able to use this tool to control pwm from voxl2 command line while the px4 is running and talking to the ESC.

The new repo for the tools is here : https://gitlab.com/voxl-public/voxl-sdk/services/voxl-io-server/-/tree/dev/tools and I believe it should be doing the same thing, although i have not personally confirmed it yet.

Try it out!

Long term, we do plan to provide the support for this (this is not a temporary feature), so we are working on cleaning up the tools for that.

Alex

HI @TomP
Please remove all products off of the ESD static bags.
This bags are only used for unpowered storage/shipping when outside of a controlled ESD Work Area.
This site has a few good books you can try to pick up so your team is well prepared for ESD handling: https://www.techni-tool.com/category/Static-Protection/ESD-Training-And-Awareness-Materials

The Starling 2 and Starling 2 Max will be supported for the foreseeable future. The Sentinel is less popular, so it is likely to be deprecated in 2025 but is currently marked as "Active Production" on its website

Dash speed, or burst speed, is the airframes capability when full throttle is applied for a short period of time. Batteries are typically able to discharge more current when first applied, but not for a sustained period of time.

@david-moro We have not used that specific radio before, only the nano and mini

@Viktor-Gal If you've already removed the board then sending in just the board as an RMA is fine

We have added support of the following barometers to voxl-dev branch of px4-firmware repo and you should be able to pick up the change tomorrow in the latest nightly build:

bmp280 bmp388 ms5611

http://voxl-packages.modalai.com/dists/qrb5165/dev/binary-arm64/ (look for voxl-px4 and check build date).

the new barometers can be enabled connected to J19 (px4 i2c port 1, so -b 1) and modifying voxl-px4-start script:

qshell bmp280 start -X -b 1 qshell bmp388 start -X -b 1 qshell ms5611 start -X -b 1

You should disable the onboard barometer icp101xx, otherwise there may be a conflict where two barometers are publishing under the same instance (at least when viewed with px4-listener). We will investigate this issue.

Alex

@soraminds VOXL 2 is a Linux computer so you can just run Apache or any other standard web server. But be aware that voxl-portal is also a running web server so you would have to stop it or, even better, run your server on a different port.

@mkriesel,

For global shutter camera like AR0144, the center of exposure will happen at the time that you suggested:

int64_t center_of_exposure_ns = start_of_exposure_ns + exposure_time_ns / 2;

For rolling shutter cameras, this is not true because different lines are exposed at different times. In this case, the center of exposure, which means the center of exposure of the middle line ( 🙂 ) will be:

int64_t center_of_exposure_ns = start_of_exposure_ns + (exposure_time_ns + readout_time_ns)/2;

This means that you will need to know the readout_time (which is time it takes for the full image to be transferred from the camera). It is not currently exposed in camera server or the camera metadata.

Take a look at this resource, it should help understand the rolling shutter case if you need : https://www.1stvision.com/cameras/IDS/IDS-manuals/en/basics-shutter-mode.html , specifically:

shutter_global.png

shutter_rolling.png

Alex

@FIREBIRD

VOXL2:
https://www.modalai.com/products/voxl-2?variant=39914779836467
https://docs.modalai.com/voxl2-datasheets/

M0130 add-on board (1 USB 3.0 + 2 USB 2.0s):
https://www.modalai.com/collections/voxl-2-add-ons/products/m0130-3?variant=48186331693360
https://docs.modalai.com/lte-io-breakout-usb-hub-datasheet/

@Gary-Holmgren Thanks for the update!

@svempati Are you trying to access the mavlink data from VOXL 2 itself or from an offboard computer / ground station?

@Alex-Kushleyev Thanks, everything looks alright now that I've removed the other cameras from the config file

@Jeremy-Frederick Okay, well then you will need to add support for such an external Mavlink enabled peripheral into voxl-mavlink-server. We don't currently support that.

@griffin Unless you have your network setup to manually cycle IP addresses every so often then your PC's IP address should stay the same. They're usually logged by mac address

@Shivam-Sehgal , it seems you are using VOXL SDK that is more than one year old, please upgrade to the latest 1.3.5.

If you are not able to upgrade, then please try the following:

reduce the width/ height of hires camera large video stream to 3840x2160, if that does not help, reduce the FPS of hires camera to 25Hz disable snapshot if you are not using that feature try starting voxl-camera-server manually and assign upper cores 2-7 to the process, which helps with stability stop camera server running in the background (if applicable) : systemctl stop voxl-camera-server run camera server and assign cpu affinity using taskset : taskset -c 2-7 /usr/bin/voxl-camera-server

Alex