Posts made by wilkinsaf

Was curious if voxl-fan was taken out of SDK 1.5

@wilkinsaf

1. Yes this is definitely possible
2. You would need to modify flow-server and possibly feature-tracker to ensure this is pointed at the right pipe
3. Might also need a bit of calibration here and there
4. Have not tested having multiple versions of flow-server, but should be possible.
5. Would need to ensure this works with a downard facing tof for accurate height estimate

To get a rough draft of this working, would take ~2 days

Hello,

Had a general question about flow server

1. It appears that the flow server is optimized for the lepton, but was curious what the lift would be to get it working with another camera. I see I can change the pipeline:

Wondering if there are any more "gotchas" besides changing the camera pipe and resolution

2. multi-flow: I understand that voxl-flow-server only allows for one camera stream at a time. Is there anything preventing us from spinning up multiple instances of it in order to have multiple flows running?

Thank you!

@Rocio-Lopez Not sure.

You would have to ask Gremsy about that possibly

From James (the guy who set the parameter)

feel free to increase it. Starling 2 Max has a very high power to weight ratio so I artificially calmed it down by limiting throttle

Hello,

I am looking into increasing the max thrust on starling 2 max. Currently it is set to 60%. Wanted to increase it to 100%.
I IMAGINE that it is set to 60% to ensure that the motors do not overdraw from the LION batteries, but wanted to ensure that was the case.

Something is in the works

Hello,

So, we are able to do the voxl 2 mini to hadron. Which is awesome!

However, it would be even cooler to have a converter off of the gremsy hadron gimbal in order to add the voxl2 mini's power onto a smaller camera/gimbal setup.

Here is a video that better describes what I mean

https://www.loom.com/share/963815412dea4714877065b31c36428e?sid=e3c38cb5-1042-4592-90f7-9883b4b72265

@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