ModalAI Forum

We got it to work by just navigating to the launch file and invoking the roslaunch command from there (and excluding the package name): roslaunch voxl_mpa_to_ros.launch. Thanks, @Alex-Gardner!

Thank your for your reply. The command is pip3 install opencv-contrib-python-headless (=title of the question). Ubuntu docker is a good but not enough . I need this (opencv python package) on the target board, again like supported by modalai's python numpy package. Please help me to create/ download/install this python package on a voxl board. I need it for later using as ROS node (written in python)

If there are not a lot of file operations, it is pretty rare. It can happen during development as folks are making changes on the board and then pulling power. Linux has a setting for how often the flash is committed to reduce the risk, but of course there could be different side effects. You can see a writeup on the topic here, as it is common in all of this type of single board computers Your smartphone fixes this by making you press the poweroff button before shutting off power.

The Qualcomm Flight RB5 5G is our flagship 5G product at the moment. We do expect VOXL to support 5G directly by the end of CY '21 with a new add-on.

Hey @colerose, What was the voxl-streamer output when you tried to start the second stream? I was able to successfully start a stream with both the hires and tflite-overlay cameras, however voxl-streamer is very resource intensive when we have multiple streams running. Have you considered using voxl-portal to view both? [image: 1631730040501-dual_camera_streams.png]

@Matt-Turi Great thanks! I'll give it a shot now!

We don't sell any platforms with the M0024 sensor onboard by default. If you're just trying to use it for color fpv/more general inspection I'd suggest just VHB taping it to the front, if you're trying to use it for hyper-accurate detections you'll have to modify one of our platforms or design your own (as most of our platforms are meant to serve as reference designs and not full production hardware).

It looks like your machine does not have QEMU support or is missing ARM support on your host machine. Please try instructions here : https://www.stereolabs.com/docs/docker/building-arm-container-on-x86/ (which also show you how to run ARM64 docker images on x86)

@Jae-Park You should ship out the entire drone so that the team can verify that all of the components are functional, fix anything else that you may not have seen, and do a final flight test before sending back.

Actually, I don't think it's possible because two identical PMD sensors will have the same I2C ids and communication will interfere. All cameras, with the exception of right stereo (if stereo flex is used) are communicating on the same (primary) i2c bus. The right stereo camera uses the secondary i2c bus. If it were possible to change the I2C id of the PMD sensor, then it could work, but I am not sure if that's an option.

@modaltb i am using win10. i can ping to voxl. Pinging 192.168.8.1 with 32 bytes of data: Reply from 192.168.8.1: bytes=32 time=3ms TTL=64 Reply from 192.168.8.1: bytes=32 time=3ms TTL=64 Reply from 192.168.8.1: bytes=32 time=3ms TTL=64 Reply from 192.168.8.1: bytes=32 time=3ms TTL=64 Ping statistics for 192.168.8.1: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 3ms, Maximum = 3ms, Average = 3ms C:\Users\David>ping 192.168.8.1 Pinging 192.168.8.1 with 32 bytes of data: Reply from 192.168.8.1: bytes=32 time=3ms TTL=64 Reply from 192.168.8.1: bytes=32 time=4ms TTL=64 Reply from 192.168.8.1: bytes=32 time=3ms TTL=64 Reply from 192.168.8.1: bytes=32 time=3ms TTL=64 Ping statistics for 192.168.8.1: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 3ms, Maximum = 4ms, Average = 3ms i have turned windows firewall off. qgroundcontrol still no response

Although a majority of our testing is at the higher baud, we've used lower without problems, so it should be fine.

The kernel build is posted at https://gitlab.com/voxl-public/system-image-build/voxl-build

@Chad-Sweet Thanks for your reply. This is the exact answer I was looking for. The flight core is perfect but here at our company we need to use different Pixhawk board for some specific application.

This is a known bug that was fixed in voxl-vision-px4 v0.8.8 which is currently on the development repo, scheduled to be merged into the stable repo in a week or so. The bug is not caused by PX4, it was due the the handling of the specific mavlink packet containing console data. It should behave normally when not using the PX4 console.

@Chad-Sweet has anyone tested the negative temp rating. Hoping to see a -20 c.

@PawelJ There isn't an exact way to do that, if you want you could edit your initial question and add a [SOLVED] section at the top and describe the solution.

Hi Nikhil, Sorry for our delayed response on this. I just recently joined our forum to help out with more HW centric question. As Chad mentioned, this does require HW mods if you do not want the SW driver timestamp method (which would be our recommendation/preference). The Lepton signal VSYNC (on GPIO3 most likely is what you are referring to) is running at the VIO voltage of 2.8V to 3.1V per Lepton specs. Our camera sensors are MIPI based, and as such all of those I/Os are at 1.8V, so a level translator would be required which makes connecting these a bit tricky, especially if you need bi-directional support with another sync controller/snoop device. This would need to be something done on a custom interface between the Lepton and the stereo sensors. We do not have such module but would be happy to give further guidance if you need it. Thanks! Vinny