@Tamilselvan Correct, for example take a look at our UVC camera server: https://docs.modalai.com/voxl-uvc-server/

Hi @JANG
The only time a power module is damaged is when a power supply is used to power the system and the motors are spun up, creating a voltage spike on the input rail that exceeds 28V, not a battery. So, this overall is very surprising to me.
You are welcome to use any 5V source for FCv2. It does not need much power (maybe 1-2Amps total) so our power module is overkill for a FCv2, but it helps by providing current and voltage readings to to PX4 or you FC SW of choice.

@paul-ammer If you aren't doing any VIO related flight you can disable voxl-qvio-server and voxl-imu-server. I believe you may still need voxl-vision-hub if you're communicating with a ground control station but not 100% positive on that, voxl-mavlink-server may be enough.

Hi @dan64
That is not the standalone Modem board variant and many other components are missing to make this work.
We do not currently sell the "standalone" version of the M0090 (5G) or M0130 (4G LTE), so sadly your efforts will hit a dead end.

@buem799 Yes, I think that one should work fine. But there's probably a bunch of configuration options for the receiver so you have to make sure that it has been setup properly to do CRSF.

@Samuel-Lehman I think the issue is with the tflite version running on voxl, which does not support v3 ops. An update to tflite on the voxl is being pushed but it will take some time to be merged into the main SDK. However, you can try tensorflow 2.17.1 from this branch.

Note that since it is not completely integrable, running it is slightly more complex. Make sure you are using the newest voxl-cross image to build voxl-tflite-server.

On Voxl, it cannot run directly, and you would have to run it via a Docker container. You can find a sample Dockerfile provided in docker_samples/ in the 'update_tf' branch. For further context on integrating opencl please refer to this.

Hopefully, the updated tflite will contain the necessary v3 op and it works smoothly.

@Moderator Sorry, I forgot to mention VOXL Mapper by using the TOF Sensor. I found a table that states it will be supportet in the future: https://docs.modalai.com/M0178/?utm_source=chatgpt.com
Do you know when we can expect it ?

@Eric-Katzfey thanks for the quick reply. Since 14550 is hard-coded into voxl-mavlink-server service, that answers my question re: customizing this port.

For additional context, I'm interested in replicating QGC's behavior of connecting to multiple UAVs simultaneously, each identified by their MAV_SYS_ID. As an example:

Set MAV_SYS_ID to "42" on one VOXL Leave MAV_SYS_ID as "1" on another VOXL Set secondary_static_gcs_ip to your GCS IP on both (/etc/modalai/voxl-mavlink-server.conf) QGC automatically connects to both and shows "Vehicle 42" and "Vehicle 1" in the dropdown in the top menu bar

I'm able to connect to my UAV using mavsdk at udp://:14550 but I can't tell which one connects since both are sending telemetry to my Mac's 14550.

Since posting this, I discovered https://github.com/mavlink-router/mavlink-router which may be what I'm looking for, but I'm still trying to get it working with my docker-compose setup. I was just wondering if there was a simpler configuration onboard the VOXL that I could easily change.

@buem799 Hi, no worries, I am also very new to this space. ffplay is separate thing, part of the ffmpeg program, not something inside VLC. This is the reddit link that I posted in the thread I listed above

https://www.reddit.com/r/reolink/comments/yzhlxp/found_a_solution_for_rtsp_blackno_video_in_vlc/#:~:text=In VLC%2C under the Tools,video stream in VLC player

If you read through it, the fix was for a windows machine, which I was using at the time. It states further down in the reddit post that live555 support was removed in newer versions of ubuntu (linux operating system). From your screenshots, it looks like you are using ubuntu, so it could make sense that VLC may not work. I believe it is more a ubuntu issue rather than VLC. Don't try to dig into that, especially if you are new to linux. I would install ffmpeg on your system and try to access the RTSP stream using that. I just asked ChatGPT for the commands to do that and will paste below:

sudo apt install ffmpeg

Id recommend asking Chat how to access an RTSP stream using ffplay, or read the documentation 🙂

The other thing you could do, if you had a windows laptop, you could connect the windows laptop to the drone wifi and try to access the RTSP stream via VLC on windows and do the fix included in the reddit link

@voxl-phoenix , I think you also mentioned that you tried swapping the cables between tracking and imx412 camera, right? If so, it seems something got damaged in the IMX412 camera during connecting / disconnecting. For disconnecting the cables, we suggest using a special tool, please see https://docs.modalai.com/micro-coax-user-guide/#-proper-cable-and-adapter-handling- .

Also, it is hard to say for sure where exactly the issue is - M0173 board or IMX412 camera. the only good way find the cause is to replace components one at a time.

Just to elaborate on the symptoms that you are seeing : voxl-camera-server -l command essentially probes all the cameras (based on the sensormodule files located in /usr/lib/camera). Probing involves turning the camera on via the reset GPIO and attempting to talk to the camera via I2c interface. If the camera responds, the probe is successful, otherwise failed. In your case, the probe of IMX412 failed, which means either the camera could not be turned on for various reasons or the i2c communication was not working.

If you have another tracking camera AR0144, you could connect it instead of the IMX412 and see if the probe succeeds. You would need to add /usr/share/modalai/chi-cdk/ar0144/com.qti.sensormodule.ar0144_1.bin file to /usr/lib/camera (which is the AR0144 sensormodule for the camera slot 1, where the IMX412 is currently connected). Then if you run voxl-camera-server -l and detect two AR0144 cameras (3 cameras total) then i2c communication and power should be working).

Alex

@yardy Folks recover using that tool all of the time. When it doesn't work, it's due to hardware damage. Often from ESD, or simply crashing the drone. See https://modalai.com/handling

placed order via email

@Aaron-Porter , the voxl-logger does not control what format the images are coming from voxl-camera-server. Currently, voxl-camera-server can output images in RAW8, YUV format and JPEG only in the case of a snapshot (not continuous). So, to answer your first question, the camera server does not support outputting PNG or JPEG in continuous streams.

voxl-logger already supports saving images in png or jpeg format, depending on the type of image that is being logged (RAW8 mono or YUV color, etc). You could tweak the behavior to your needs or add a flag to voxl-logger to force a logging format : https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-logger/-/blob/master/tools/voxl-logger.cpp?ref_type=heads#L1455 .

Alex

@Zachary-Lowell-0

What kind of upgrade is necessary for this Rb5? Should we upgrade the sdk?
we can run ros2 foxy with it. The dds is also working.

How did you build this ros2 packages and nodes
https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-mpa-to-ros2

Thank you

@GlennTee Good news! The program now runs, turns out I needed to add the .py extension to the file name when calling the run command, so it should be "ros2 run px4_ros_com offboard_control.py"

However, we experienced a lot of errors while running. The drone did arm (But only would do every even numbered attempt for some reason), however it did not fly. I'm working now to debug these errors.
image(1).png

@Alex-Kushleyev Can you provide me an EMAIL where I can share the video?

@wen-max On the datasheet it says take-off weight of 566g https://docs.modalai.com/starling-2-max-datasheet/

Take off weight includes the battery