Great, Thank you for your reply.

thank you

MV is Qualcomm's Machine Vision library. The source is not public, but the binaries are baked into the voxl system image and the voxl-emulator docker image, so you won't need to do anything special to build/run a custom qvio server.

Hi @Daniel-Ryu , This isn't something we currently support. The gimbal is primarily for stabilized video, but there's no autonomous control in or stack at this time. Thanks, Travis

Hey @Thomas-MacNamara , I totally hear you... We are reeeeal close to a big docs update...... Should be dropping on the server within days and hopefully we can clear things up. Appreciate the patience and please keep providing feedback as you have issues! -Travis

Sorry for the late response, I've been doing some testing. so I've narrowed it down to the error lying in the stereo cameras, I connected each sensor one at a time, reconfigured, and ran the voxl-streamer and was able to get footage for the hires and tracking, but when it came to the stereo it would not work. When I would reboot the system and inspect the services I would see that the voxl-camera-server is running, but once I tried to voxl-streamer -c stereo it would get stuck at the same place and the voxl-camera-server would stop running. I've confirmed that both of my extension cables are working by testing them with the hires camera. I checked the physcial connections on the stereo cameras and there are no creases in them, they look just as they were folded with the original setup, and I believe that if any of the connections were inverted then the VOXL wouldn't even start up.

The tracking camera (OV7251) is a grayscale camera, so it cannot sense color.

@DillonAllen Without WiFi, the only way you'll be able to debug VOXL related things is via. ADB so I would follow this guide: https://docs.modalai.com/setup-adb/ in order to setup ADB on your host computer.

Like Chad said, this depends on many factors. I just wanted to add a bit more details. TOF is not pushing nearly as much data as, say, 4K30 camera, so it is using CSI speeds vs 4K camera. There is a chance it may work with double extender. You should try it! Regarding Raspberry pi (and corresponding discussions), I have personally tried a few of those cables and found that some long cables (~50cm) with raspberry pi and pi camera and saw that long cables result in pixel noise in the image. But it looks kind of strange, since the raspberry pi ISP tries to de-noise the noise and image ends up being kind of noisy and more blurry at the same time and the colors are off. I don't remember exactly what the picture looks like, but the failure mode of long cables may not always be "no image" (no image in the worst case). On VOXL, I have seen some bad cables (occasionally) and I was seeing frame sync issues (image rolling up/down) or sometimes no image at all. I don't think you can damage the camera or VOXL by using too long of a cable, but at some length you will get corruptions and that length depends on the camera and its operating mode. Alex

Although we aren't VPN experts (yet), this is something I've seen myself. There are parameters that can be configured by VPN server/clients that may affect bandwidth (e.g. MTU). There are various types of client/servers out there so it varies how these could be setup. Also, depending on where the VPN server is located, you might be going to a server far away, and depending on the VPN server quality, they may or may be sharing resources with you.

The segfault error is an error that occurs when closing camera server, not while it's running. This is happening immediately after running camera server because systemctl detected the segfault and tried to rerun camera server (thus closing yours since only one instance of camera server can be running at a time). If you want to run camera server manually, make sure to run systemctl stop(or kill) voxl-camera-server first to make sure there's no background conflict. The generic hal3 error codes can be found here, the -19 is a qualcomm specific one that we've found to be equivalent to ERROR_DEVICE (though we have been unable to find its proper definition), and has indicated that there is an error with the device and it will be unable to process any more requests.

Hi Alex, this was very helpful - got it working and managed to get the docker image out. thank you for your help !

@Vinny no worries, I ended up just going to industrial hardware in SD and trying out a bunch of machine screws until I got one that fit nicely, cant recall the exact size. Here are the dimensions for mounting the M0026 in a part I made. Figured I would post it if it helps someone else out since I personally couldn't find a STEP file for this part. Dimensions are in mm, the camera is ~24.1mm from base to the tip of the lens from my caliper measurements. [image: 1625873711419-95a40f46-9f47-4afa-905a-da227061deff-image.png]

Thanks for your help. Yes, the ESCs use PWM. I may have had something configured wrong, so I'll try again.

@FourPointTwoMm correct, daisy chaining 2 will likely fail, this is what I've seen.... we've validated against the single extension only.

Hi Reg, we have not performed formal characterization of those modules yet. We expect them to perform well in typical consumer electronics environments, 0-55C for instance.

Nevermind, to use pymavlink we needed to not run MavSDK at the same time

@tom That was the solution, thanks!

Got it. The changes are now persisting through reboots - not sure why it didn't the first time (i did adb reboot), but seems to be stably working now. Thanks for your help!

Hello Mark, A few things to check.. make sure the voxl-camera-server is not running, since it cannot be used concurrently with voxl-rtsp (you can check what services are enabled using voxl-inspect-services when connecting via VLC, you should not use 0.0.0.0 address. 0.0.0.0 is an invalid address it is strange that voxl-rtsp reports that it's listening on 0.0.0.0. It looks like you have VOXL in AP mode (based on the IP address). Run ifconfig and see if it shows anything strange. The fact that you are able to ssh into VOXL using 192.168.8.1 means wifi AP is working fine.. just in case, try using it's actual ip address in the rtsp:// field - it looks like you already tried it in VLC? if you are able, please try compiling and using the latest version of voxl-rtsp here : https://gitlab.com/voxl-public/utilities/voxl-rtsp/-/tree/dev - it will also print some stats after you exit, just making sure the camera frames are actually coming in. There is a script build_in_docker.sh that makes it easier to compile voxl-rtsp, as long as you already have the voxl-emulator docker image