Hi @Wei-Cui , If using system image 1.3 for the RB5 (865 platform), this means you now have the VOXL SDK, which uses voxl-streamer From https://developer.modalai.com/ You have: [image: 1661874180480-9e266117-f01e-4e9e-b407-8cf675abc131-image.png] Which at this point has this release: [image: 1661874097851-3a34a1d7-0ae6-4a80-809b-284733001bb6-image.png] This is a different architecture than the RB5 Flight SDK, which is not getting feature updates. The VOXL SDK is what our core software team is developing on and will continue to get all the new features and updates.

@Matt-Turi Ty, I used a different image(voxl cross image), it is working with the voxl emulator.

Hey @jamiek, If this error occurs, it will result in no map generation at the time of error. This is because we need to grab a pose from our ringbuffer (at the timestamp of our pointcloud) in order to insert each pointcloud correctly into the map. This is caused by either voxl-qvio-server or voxl-vision-px4 not properly publishing a pose estimate. You can monitor the output of voxl-qvio-server using voxl-inspect-qvio on voxl or viewing the qvio overlay in voxl-portal. If everything looks good there and qvio is properly publishing pose info, the next place to check is voxl-vision-px4. This error means that we are not receiving a fixed pose data out of voxl-vision-px4, so once you have verified qvio is not reporting any error codes, monitor the output of voxl-inspect-pose -f on voxl and make sure that you are receiving pose data.

yeah, just wanted a confirmation, thanks

WOW what a great thread, so on time for me Thanks Kris

Hey @ahmed-mustahid, You can view one camera stream at a time within the Mapper page of voxl-portal. The bottom left hand corner of the page includes a button (tv icon) to overlay an image stream on top of the map grid. Clicking on this tv icon will populate a list above of all available image topics, similar to the camera dropdown. Selecting one will overlay it on the page, where it can be resized via the bottom left corner of the stream and closed using the red x at the bottom left.

@Tamas-Pal-0 You can set parameters from the command line. Here is an example: modalai@modalai-XPS-15-9570:~$ adb shell voxl2:/$ px4-param set UART_ESC_RPM_MAX 10000 + UART_ESC_RPM_MAX: curr: 10500 -> new: 10000

Nevermind, I found it... voxl-fan...

@Tamas-Pal-0 No, it requires the FTDI cable.

@Alex-Gardner Thank you! That worked

Hi, I've been trying to deploy VVPX4 and still see some dependencies. I am using the VOXL Platform 3.8.0-0.7 and VOXL-Cross-2.1 docker image. voxl-vision-px4-master $./deploy_to_voxl.sh searching for ADB device checking VOXL for dpkg/opkg opkg detected voxl-vision-px4_1.2.0.ipk: 1 file pushed. 3.4 MB/s (105362 bytes in 0.029s) Reinstalling voxl-vision-px4 (1.2.0) on root. Configuring voxl-vision-px4. Collected errors: * satisfy_dependencies_for: Cannot satisfy the following dependencies for voxl-vision-px4: * libmodal-pipe (>= 2.4.0) * libmodal-cv (>= 0.1.0) * DONE Maybe I have to build the following in a specific directory but I am not sure which one: $ mkdir cross-workspace $ cd cross-workspace $ voxl-docker -i voxl-cross:V1.9 voxl-cross:~$ git clone https://gitlab.com/voxl-public/voxl-sdk/core-libs/libmodal-json.git voxl-cross:~$ cd libmodal-json/ voxl-cross:~$ ./build.sh qrb5165 Can I install or source these two dependencies separately?

@Jeff-Delaune try screen

@Eric-Katzfey Thanks. I got the VPN setup working fine. If I end up needing to transition over to that (and I get it working) I'll let you know...

And yes for PWM output --> https://www.modalai.com/products/flight-core-pwm-output-cable-and-break-out-board

@Eric-Katzfey @plusk01 Curious if you are still using tmux and able to run automatic tmux (or tmuxp) scripts. I have the issue explained here: https://forum.modalai.com/topic/1248/issue-running-tmux-or-tmux-scripts-on-voxl2 which seems related.