After connecting the VOXL2 Mini to an external flight controller as described here via J10 on VOXL2 Mini, MAVlink data was viewable from a VOXL Flight Core v2.

We are still having some troubles with viewing the streams, however now the stream/camera names are appearing in QGC with the video feed selector now that the above MAVlink connection has been established.

It seems like in order to route MAVlink data out of J3 on VOXL2 Mini via USB, we will need to look into MAVrouter or a similar solution. For now we will continue integration via J10.

Our goal with routing MAVlink data via USB on VOXL2 is to reduce the telem connections required on a flight controller for our product. We would like the ability to run multiple RTSP streams and MAVlink communication via a single USB connection (from J3 on VOXL2 Mini) to an external flight controller.

Is UART communication via J10 the preferred or only method of communicating with VOXL2 Mini over MAVlink?

Is there a way to do MAVlink routing with the VOXL SDK as I mentioned, or will this need to be custom implementation?

If the VOXL2 Mini is receiving MAVlink data via a UART connection from another device, will the VOXL2 Mini forward and receive MAVlink data to/from the MAVlink device through to a Flight Core via the external flight controller connection J10 on VOXL2 Mini?

Thank you for very much for your time and feedback on this topic.

@Vinny Thank you for the file sir.

The kit ordered is pictured below:

It would be nice to have 1.6mm or larger mount holes on the next rev of the backboard PCBA to interface with the Boson+ directly, without the need for a mounting bracket, if possible. Not a big deal, but it would be convenient.

As a follow up here, I was wondering if we have the proper hardware connections to support VOXL-Mavcam-Manager?

Our hardware setup is as follows: we have a VOXL2 Mini streaming video from the USB port (J3) on VOXL2 Mini to a USB to Ethernet converter connected to QGC.

We are hoping to utilize VOXL-Mavcam-Manager with just a single connection to the VOXL2 Mini via J3 as described above.

Would you be able to confirm that we can utilize VOXL-Mavcam-Manager with the above configuration please?

We are currently getting "nullMsg array" and "ERROR validating mavlink_message_t data received through pipe:...." as shown above in the previous post.

@Vinny thank you for the update sir.

As for the kit it was an MDK-M0153.

We do have a printer, would you mind sending that over in a .step format when you have the time please?

Hello,

After running voxl-inspect-mavlink hires412_large_encoded with the services running mentioned above we are seeing the following output:

ERROR validating mavlink_message_t data received through pipe: 56 of 56 packets failed
last magic number received was 38, expected MAVLINK_STX=253
ERROR validating mavlink_message_t data received through pipe: read partial packet
read 1312 bytes, but it should be a multiple of 44
ERROR validating mavlink_message_t data received through pipe: read partial packet
read 1272 bytes, but it should be a multiple of 44
ERROR validating mavlink_message_t data received through pipe: read partial packet
read 1384 bytes, but it should be a multiple of 44
ERROR validating mavlink_message_t data received through pipe: read partial packet
read 1624 bytes, but it should be a multiple of 44
ERROR validating mavlink_message_t data received through pipe: read partial packet
read 1704 bytes, but it should be a multiple of 44
ERROR validating mavlink_message_t data received through pipe: read partial packet
read 1624 bytes, but it should be a multiple of 44

Any idea of what may be the problem here?

@Vinny thank you very much for your prompt reply!

That drawing you are referencing is the minimum diameter of a 1.6mm thread. 1.2mm is the measurement on the most concave point of the thread.

The outer dimension for that thread at the most convex point is 1.6mm as shown in the below drawing from FLIR's CAD. For a m1.6 screw to pass through the PCBA and mount to the aluminum Boson housing, the through hole will need to be >1.6mm. I have a Boson unit on my desk and can confirm M0153 cannot mount to the Boson with the current mounting holes of 1.2mm.

Not a big deal, we made a nice lil hat for the backboard to hold it in place.

My feature request would be: Increase the thru holes to 2mm to accommodate for the m1.6 mount hardware.

Hopefully this is helpful feedback, thank you for your time and great products.

Hello,

Hardware:

VOXL2 Mini streaming via wired ethernet connection to QGC

SDK:

1.3

Summary:

We are working on getting multiple RTSP streams to appear on QGC's fly view without the need to enter in different RTSP endpoints manually with the use of VOXL-MAVCAM-MANAGER.

Currently, the two different streams can be viewed when the RTSP endpoint is manually changed in QGC, however when the RTSP endpoint is blank, the video feed is cut off.

Services Running:

voxl-wait-for-fs
voxl-streamer (RTSP stream 1 on port 8900)
voxl-streamer-2 (RTSP stream 2 on port 8901)
voxl-mavlink-server (auto IP set to "true")
voxl-mavcam-manager (config file has two streams defined with "default_uri" set to IP addresses that are confirmed streaming to those IP addresses)

Questions:

Is there an easy way to debug this similar to what this user is doing: https://forum.modalai.com/topic/3666/voxl-mavcam-manager-crashes-on-mav_cmd_video_start_capture-mavlink-command-when-trying-to-record-video?_=1722617227523?

Do you have any recommendations based on the summary?

Hello,

We are working with your M0153 and it appears that the thru holes on the M0153 are ~1.25mm. For M0153 to mount to a Boson sensor, the corresponding mounting holes are 1.6mm.

On the next rev, would you be able to increase the mounting holes to 2mm in diameter?

Hello,

I just recently reviewed the release notes for VOXL SDK v1.3 and noticed the M0173 PCBA is now supported.

• Is the M0173 compatible with VOXL 2 Mini at this time or are there plans to support M0173 on VOXL 2 Mini?

• What is the expected availability of M0173, as well as associated cables and sensors?

Hello @Moderator,

We are looking for the M0153 and M0162 CAD files and cannot find them in the ModalAI PCB Catalogue.

Would you be able to add those to the catalogue web page above?