@Eric-Katzfey OK good to know. Thanks for looking into that. Is there a good email I can reach out to discuss further with you?

Hi @Nishkala , With the warning that I've not yet tried in python but I'm sure it will work This is the source code for our voxl-inspect-qvio tool, and from there we can see it's looking for a pipe QVIO_EXTENDED_LOCATION https://gitlab.com/voxl-public/voxl-sdk/services/voxl-qvio-server/-/blob/master/clients/voxl-inspect-qvio.c#L51 That's defined here: https://gitlab.com/voxl-public/voxl-sdk/services/voxl-qvio-server/-/blob/master/common/voxl_qvio_server.h#L64 The other place to look for defines is in libmodal-pipe: https://gitlab.com/voxl-public/voxl-sdk/core-libs/libmodal-pipe/-/blob/master/library/include This is where the inspect tool consumes data: https://gitlab.com/voxl-public/voxl-sdk/services/voxl-qvio-server/-/blob/master/clients/voxl-inspect-qvio.c#L259 Here's where we parse and print the info: https://gitlab.com/voxl-public/voxl-sdk/services/voxl-qvio-server/-/blob/master/clients/voxl-inspect-qvio.c#L184

@Alex-Gardner Ok, thanks much for running that. Since it built clean for you, that made it clear that there was something bad about my environment (the whole reason I'm down this rabbit hole!). Anyway, my typical configuration is to ssh into my Linux machine from a W10 box using Cygwin/SSH. Apparently something in the build.sh script doesn't like that; hence my failures. When I build directly through the console of that Linux machine the build completes successfully. Sorry for the confusion, and thanks to all for the responses.

@CY-1992 said in Building new docker image error - Cmake version not good: ubuntu:20.04 Thanks @CY-1992 is working just fine!

Thank you Alex!

Glad to hear someone's building our packages themselves! Yes, we're most of the way through migrating to a more platform independent build system that will let us use these packages on the qrb5165 platform as well. This is one of the things we've had to change, the next voxl system image will have a tweak allowing these packages, but if you want to install them in the meantime, you can manually add the tweak by adding the line arch arm64 7 to /etc/opkg/arch.conf on your voxl and running opkg update

https://gitlab.com/voxl-public/voxl-sdk/services/voxl-portal/-/blob/master/src/video_manager.cpp#L77 Is an example of allocating a buffer and copying the frame into it. There are some other good examples in that file as well for processing frames and converting them to various formats within the callback. Hope that helps!

@Eric-Katzfey Ok thanks for the fast answer.

@Philemon-Benner Our qrb5165 based platforms put 64 bit libraries into /usr/lib. On Voxl the 64 bit libraries go into /usr/lib64. So the 64 bit support is specifically for our qrb5165 based platforms (e.g. RB5 Flight).

@Matt-Turi Thank you

Hey @Michael-Shomin, The non-cached files in voxl-portal for font + images were purged in these two commits: https://gitlab.com/voxl-public/modal-pipe-architecture/voxl-portal/-/commit/d79786562275bcc11a41a1ebdf8c4c4de6ce5432 https://gitlab.com/voxl-public/modal-pipe-architecture/voxl-portal/-/commit/96259ed613f336ea4f2ac88ecd7a79918d8494a1 These changes are in the dev release, but you can pull them into your version if doing anything custom.

Thanks for the answer! it worked great after the upgrades. what I am trying to do now is to run the deeplab dnn, but I am having some issues. I tried to run the 865 build but i couldn't run any tflite dnn. then I tried to run the 820 build which worked perfectly and than added manually the deeplab dnn. eventually i received the error: [image: 1646902913214-screenshot-from-2022-03-10-10-55-20.png] do you have any suggestions?

We have example Python code in voxl-modem to control the B2B GPIO ## All GPIO pins need to be exported before they can be used # def gpio_export(num): subprocess.call("echo " + num + " > /sys/class/gpio/export", stderr=FNULL, shell=True) ## Each GPIO has to have its direction set prior to use # @param num pin number # @param direction 'in' or 'out' # def gpio_direction_map(num, direction): subprocess.call("echo " + direction + " > /sys/class/gpio/gpio" \ + num + "/direction", stderr=FNULL, shell=True) ## Set a value to an 'out' gpio # def set_gpio(num, value): subprocess.call("echo " + value + " > /sys/class/gpio/gpio" + num + "/value", stderr=FNULL, shell=True) ## Reads a GPIO pin # @apram pin # pin number # @return # integer value [0,1] def gpio_read_int(pin_int): gpio_file = '/sys/class/gpio/gpio' + str(pin_int) + '/value' value = subprocess.check_output(['cat', gpio_file]).strip() return int(value)

@Philemon-Benner You can only connect one client at a time. But you can run multiple instances of voxl-streamer and give them different ports for clients to connect to. However, the best way to allow multiple clients is to setup a media server of some sort (eg Live555) so that you only have one stream going over the wireless link to the media server and then it can replicate it as needed over a wired network.

The emulator is meant to be a build environment and not for running code, this is likely the source of the issue, does your code encounter this problem when running on a voxl?

@hmlow Yes, PX4's obstacle avoidance and Collision Prevention are separate features. We only support the Collision Prevention functionality which is governed by the PX4 CP_DIST and similar parameters. Make sure the COM_OBS_AVOID parameter is OFF (0) in PX4 James

@Chad-Sweet I'm trying to read some sensor data using UART/I2C, from within a Docker container. I will look into libmodal_pipe , thanks.

This is essentially the point of MPA (Modal Pipe Architecture, our interprocess communications standard). We publish FIFOs to /run/mpa with the data (standard FIFOs use the filesystem as a handle, not for actually transferring the data, the kernel will pass the data directly from process to process). voxl-uvc-server will pull the data from the camera and write it out to a pipe in /run/mpa, which can easily be mounted in a docker image and read there. You can use the libmodal_pipe(or manually request a pipe and open the FIFO, though this will be less reliable than our extensively tested library) to read it in a docker image (or images as MPA allows numerous clients).