ModalAI Forum

@wilkinsaf This is good insight, thanks!

Thanks @Aidan-Dempster, that worked.

@tom said in Sentinel VOXL2 Ubuntu Upgrade: @Adeeb-Abbas We haven't implemented ros2 ourselves yet so I can't give a definitive answer, however it's on our list Oh interesting. The marketing material repeatedly said "ROS / ROS 2" so I just assumed there's some level of ROS2 support. https://www.modalai.com/products/sentinel-development-drone?variant=40446488805427 says the following - Software Features PX4, ROS 1 / 2, Ubuntu 18.04, Open CV, MAVROS, MAVSDK Open Source Linux kernel, cross-compilers Docker build environment for CPU, GPU (OpenCL) and DSP (Hexagon SDK) heterogeneous computer vision and deep learning processing

@tom Thank you. A factory reset did fix the problem.

Hi @Abdullah01 I can try to help you with the hardware side. The FrSky RC receivers are a little confusing. They have several SBUS denoted ports on the module. This diagram shows which pins are utilized for our setup with the Voxl2 I/O board: https://docs.modalai.com/cable-datasheets/#mcbl-00065 Apologies we do not have the MCBL-00065 for sale yet (it had an error we have yet to address), but if you are handy with a set of tweezers, and are willing to try these steps here to make your own, it's not that hard to pin the side needed for Voxl2 I/O with a 4-pin JST GH shroud. https://docs.modalai.com/cable-userguides/ You can use a cable like this for starter material: https://docs.modalai.com/cable-datasheets/#mcbl-00015 and splice into the FrSky cable that came with your unit. Hope this helps!

@Aidan-Dempster You are correct on the mavlink console. This is not currently supported on VOXL2. You would have to log into the VOXL2 directly using adb (on the benchtop) or ssh (while flying) in order to interact directly with px4 shell.

@Vaibhav-Usapkar Your ls showing it in the file system is showing it outside of the docker container. You will need to run the base docker container and do ls there to see what is in that directory. How did you get the gcc-linaro-7.5.0-2019.12-x86_64_aarch64-linux-gnu.tar file? That shouldn't be in your local directory.

@Aaky I sent you a link in email

We do not have any feature to share at this point.

@tom Thank you. It works well now with above workaround. Also on seperate I have opened one more ticket regarding voxl-streamer over here, please respond on that as well since it is also related to new beta image.

JK found it https://forum.modalai.com/post/4746 (with a link to the quectel AT commands) https://forum.modalai.com/topic/401/lte-modem-works-but-cannot-ping/23 Had to change my search topic to title AND posts

Similar to you both: voxl-camera-server | Enabled | Running | 71.1% voxl-cpu-monitor | Enabled | Running | 0.1% voxl-dfs-server | Disabled | Not Running | voxl-feature-tracker | Disabled | Not Running | voxl-flow-server | Disabled | Not Running | voxl-imu-server | Enabled | Running | 1.5% voxl-lepton-server | Disabled | Not Running | voxl-mavcam-manager | Disabled | Not Running | voxl-mavlink-server | Enabled | Running | 0.2% voxl-modem | Disabled | Not Running | voxl-portal | Enabled | Running | 60.1% This is with HIRES, Tracking, Stereo on SDK 1.0. I also disabled large encoding on the HIRES from the camera server. Just bumping to see if this is expected.

@Aidan-Dempster Yes, HITL support will be migrated to the voxl-dev branch as well.

@Zachary-Lowell-0 Ah, yes I see what you mean. The secondary steps of updating gazebo's plugin path and loading a world with a model that uses the sitl plugins. Ok, well in that case my only roadblock is building PX4 on my mac which, as far as I can tell, is a PX4 problem and not a VOXL problem so thank you for your help.

@Eric-Katzfey In my case I am receiving data as @Alex-Kushleyev explains with stty -F /dev/ttyHS2 115200 cat /dev/ttyHS2 [image: 1739568773345-e1b7860f-60b8-4441-a7f9-c4147a44b66c-image.png] and in the script in /usr/bin/voxl-px4-start I see that section @Eric-Katzfey [image: 1739568629179-6bd3d8f4-b89b-4fa6-ad40-5c58260d333b-image.png] but when it comes to running voxl-px4 it autodetects with different bauds to the GPS. Is it necessary to change it somewhere else? [image: 1739568685057-e7941c5d-6d4b-4a0c-b5ab-a9e4130ef09b-image.png] I have no problems with the MAG. It detects it perfectly. I have the RX and TX of the GPS connected exclusively to the J9 of the 5G, and the rest, to the J19. I also have the RX and TX of the IO Board connected to the RX and TX of the J19. I have also tried disconnecting the IO Board and leaving only the GPS on the J9. SOLVED: I change in the file voxl-px4-start from M0052 to M0054. Thanks!!!