@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

Hi Zach, I just updated libmodal_pipe to 2.0.8 with a fix to cleanup the trailing characters from echoing a pipe name to the request pipe. Now you can run modal-hello-server in one window and see the output in another: yocto:/run/mpa/hello$ echo "test" > request && cat test hello160hello161hello162hello163hello164hello165hello166 Let me know if this is along the right path. I have no immediate intention for making a python library. Best, James

Hi Raj, Can you please be more specific with your question? Are you just referring to hardware connections or are you asking for software device detection? I'm not familiar with the Jetson systems, but from what I can tell, purely from a hardware viewpoint, there are a bunch of UARTs and I2C ports exposed on a Nano 40-pin header that can be connected to Voxl directly since Voxl is also at 3.3V logic levels for our external interfaces. https://docs.modalai.com/voxl-datasheet-connectors/ Now, how you expect to use the combined system is a more complicated SW systems question, so this is why I asked if you can elaborate more. How do you want the Voxl to interact with the Jetson? This will tell us if the bandwidth of the common interfaces (I2C, UART, SPI) are even suitable for your application(s). If a USB interface is more suited to your application for higher throughput, then it can get a bit harder. The Nano appears to have a variety of USB ports, as do our systems, but you'd need to understand who is the USB Host and USB Client/Device and connect them accordingly. Thanks! Vinny

Do you have a GPS/Mag plugged in? If not please try plugging in a GPS/Mag and set the PX4 parameter SYS_HAS_MAG to 1. There is a PX4 bug that prevents VIO-only operation if a magnetometer is missing, even if the magnetometer is not in use. We've been trying to get the bugfix approved and merged into PX4 master for over a year now but it seems to be a lost cause. For now our own branch of PX4 has the bugfix along with some custom tools for our ESCs. If your system starts working again with the magnetometer then we know somehow a standard PX4 image got onto your flight core instead of one of our own. Regards, James

Pasting a response I got from @Alex-Gardner (thanks!). "...download the new system image with full voxl-suite (voxl_platform_3-3-0-0.4.6-b.tar.gz) which will have all of these packages from https://developer.modalai.com/asset. If you extract the archive there will be an install script which will reflash the system image over adb (giving you the option to not wipe the data partition, if you have other things on the drone you should make sure to back them up) and then install the new voxl-suite."

@Alex-Gardner Thanks Alex, that helped narrow it down to a hardware issue, replaced the camera and it's good now. Cheers.

this is still an issue after trying voxlplatform_3.3.0 however, uninstalling avahi (opkg remove avahi and dependents) and install using https://gitlab.com/voxl-public/other/install-avahi works

@modaltb Thank you for helping I Tried it & Got following [image: 1624606884483-13dc3479-2fc3-439f-8f34-076c144200bc-image.png] I don't have the hardware (debug add-on board) with me now, Will receive probably in next week

You'd need to download yourself and then push to the target (or if VOXL is connected to the internet, download it and manually install). There's not an 'apt-get' like setup for opkg unfortunately. Sometimes this means you need to build from source.

Hi @a-w , If you're running on target, you'll need an arm64 container flavor (not x86/64), see this docker file as an example: https://gitlab.com/voxl-public/voxl-docker-images/voxl-docker-mavsdk-python/-/blob/master/Dockerfile#L1

@Kasum-Hussain actually sorry my mistake i thought i saw video2 but no if i go into dev folder there is no video2 only video0 video1 video32 video33

Thanks this fixed it. It was connected backwards. Maybe this can be marked a bit clearer in the docs, I think it’s quite unintuitive having the cable going inwards the board when not using the extension.