Posts made by wilkinsaf

@wilkinsaf

A color AR0144 exists, but there is no current integration readily available

Hello,

We were curious if there is a way to integrate a color tracking camera (or if there is even a color tracking camera that exists).
The reason being, is that for extremely small UAVs it would be ideal to have 1 tracking camera that is

1. being used for VIO
2. being used as the FPV cam
3. Being used to collect data of surroundings

But, to be used as an FPV cam and data collection the camera would have to be color.

Thank you!

placed order via email

Hello, I would like to order the boards/connectors for integrating the FLIR Hadron

M0159
M0181
coax cables between those the boards
M0155

However, I can not seem to find them on the store.

These boards are also referenced in these docs: https://docs.modalai.com/voxl2-hadron/

@groupo We also had this issue, but we had modified the sentinel and was found to be more due to vibrations

https://discuss.px4.io/t/stopping-compass-mid-flight/42808

Nevermind, was being talked about in https://forum.modalai.com/topic/4121/compass-errors

@briandaniels15 Also, might get faster responses on PX4 related things if you post on the Dronecode forum or discord

@briandaniels15 Yes, we have seen this before, but not on a fresh sentinel. Can you upload the log file that you downloaded please

We were getting this error on voxl-streamer.

We thought it was an issue with something voxl oriented. Turns out We were using a busted version of VLC that was on ubuntu 24. switching to a different media player worked.

Posting here incase anyone runs into a similar issue. Thanks!

voxl2:/$ voxl-streamer
Waiting for pipe hires_small_color to appear
Found Pipe
detected following stats from pipe:
w: 1024 h: 768 fps: 30 format: NV12
Stream available at rtsp://127.0.0.1:8900/live
A new client rtsp://192.168.0.211:54134(null) has connected, total clients: 1
Camera server Connected
gbm_create_device(156): Info: backend name is: msm_drm
gbm_create_device(156): Info: backend name is: msm_drm
gbm_create_device(156): Info: backend name is: msm_drm
gbm_create_device(156): Info: backend name is: msm_drm
gbm_create_device(156): Info: backend name is: msm_drm
gbm_create_device(156): Info: backend name is: msm_drm
gbm_create_device(156): Info: backend name is: msm_drm
gbm_create_device(156): Info: backend name is: msm_drm
gbm_create_device(156): Info: backend name is: msm_drm
A new client rtsp://192.168.0.211:54148(null) has connected, total clients: 2
rtsp client disconnected, total clients: 1
rtsp client disconnected, total clients: 0
no more rtsp clients, closing source pipe intentionally
A new client rtsp://192.168.0.211:54150(null) has connected, total clients: 1
Camera server Connected
gbm_create_device(156): Info: backend name is: msm_drm
gbm_create_device(156): Info: backend name is: msm_drm
gbm_create_device(156): Info: backend name is: msm_drm
gbm_create_device(156): Info: backend name is: msm_drm
gbm_create_device(156): Info: backend name is: msm_drm
gbm_create_device(156): Info: backend name is: msm_drm
gbm_create_device(156): Info: backend name is: msm_drm
gbm_create_device(156): Info: backend name is: msm_drm
gbm_create_device(156): Info: backend name is: msm_drm
A new client rtsp://192.168.0.211:54158(null) has connected, total clients: 2
rtsp client disconnected, total clients: 1
rtsp client disconnected, total clients: 0
no more rtsp clients, closing source pipe intentionally
A new client rtsp://192.168.0.211:54166(null) has connected, total clients: 1
Camera server Connected
gbm_create_device(156): Info: backend name is: msm_drm
gbm_create_device(156): Info: backend name is: msm_drm
gbm_create_device(156): Info: backend name is: msm_drm
gbm_create_device(156): Info: backend name is: msm_drm
gbm_create_device(156): Info: backend name is: msm_drm
gbm_create_device(156): Info: backend name is: msm_drm
gbm_create_device(156): Info: backend name is: msm_drm
gbm_create_device(156): Info: backend name is: msm_drm
gbm_create_device(156): Info: backend name is: msm_drm
A new client rtsp://192.168.0.211:54180(null) has connected, total clients: 2
rtsp client disconnected, total clients: 1

(voxl-streamer:6325): GLib-GObject-WARNING **: 18:30:24.846: instance with invalid (NULL) class pointer

(voxl-streamer:6325): GLib-GObject-CRITICAL **: 18:30:24.846: g_signal_emit_by_name: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
rtsp client disconnected, total clients: 0
no more rtsp clients, closing source pipe intentionally
Camera server Connected
A new client rtsp://192.168.0.211:54188(null) has connected, total clients: 1
gbm_create_device(156): Info: backend name is: msm_drm
gbm_create_device(156): Info: backend name is: msm_drm
gbm_create_device(156): Info: backend name is: msm_drm
gbm_create_device(156): Info: backend name is: msm_drm
gbm_create_device(156): Info: backend name is: msm_drm
gbm_create_device(156): Info: backend name is: msm_drm
gbm_create_device(156): Info: backend name is: msm_drm
gbm_create_device(156): Info: backend name is: msm_drm
gbm_create_device(156): Info: backend name is: msm_drm
A new client rtsp://192.168.0.211:54196(null) has connected, total clients: 2
rtsp client disconnected, total clients: 1
rtsp client disconnected, total clients: 0

Hello,

Was wondering if there are any plans to integrate the IMX 327 Ultra low light.

Thanks!

@Judoor-0 Gotcha. Let me know if this doesnt answer your question.

you can use voxl mpa to ros2: https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-mpa-to-ros2
and this will allow you to access camera frame information

and video: https://www.youtube.com/watch?v=ysvpJdXFWaM

@Judoor-0

I do not have an suggestions for implementing this directly on voxl2. as mentioned the voxl-opencv might conflict with standard opencv. I have also seen other packages conflict and python versions conflict depending on the ROS version you are using.
Far easier and cleaner to use a docker image, and creates less headache in the long run.

when you say data for cameras, what do you mean? I do not believe Modal has a DIRECT model of the drone in RViz or Gazebo. But you can follow this guide to get HITL working in Gazebo with the voxl2 hardware: https://docs.modalai.com/voxl2-PX4-hitl/

For interfacing with docker, that is more about learning how docker works. you can start a container, attach to it, execute commands.
For interfacing with more voxl things (MPA pipelines, network connections) you will want to share volumes of what you want to have access to (-v /run/mpa:/run/mpa -v /usr/bin/voxl-list-pipes:/usr/bin/voxl-list-pipes) and give the container priviledged and host network --privileged --net=host. This information should be contained in the walkthrough I posted above.

To give you context as well, we usually run ROS on a docker image when running it on voxl.
Does this answer your question?

@Judoor-0

1. When you say voxl libraries do you mean the VOXL SDK? Probably not as ROS depends on specific packages to work together
2. There is a decent walkthrough here: https://docs.modalai.com/docker-on-voxl/#voxl-2. At the end of the day you can pull in a docker image that has ROS pre-installed here: https://hub.docker.com/_/ros. Noetic is included in that. You can either pull it down straight on your voxl if there is an internet connection, or (takes longer) pull it down on your local PC using docker, save it to a tar file, adb push it to your voxl, and load it up using docker on your voxl.

@James-Strawson This is perfect! Thank you James!

@Moderator Indoor

If I wanted to get 360 degree obstacle avoidance. What is the recommended path to do so?

front and back stereo depth? two TOF? outside sensor?

Shot in the dark. Would it be possible for one of the USB Fastboot addon boards (connected to voxl2 cause the USB on another advice to get fried?

I have had the USB on 3 doodles just stop working. All of them were connected to a voxl2. I am unsure why this keeps happening. I am just trying to narrow this down. THank you

maybe voxl-replay....