@Aidan-Dempster I will send you an email.

Thanks @Aidan-Dempster, that worked.

@Veldrovive No, 1.11 is not supported and it would likely be a lot of effort to make it work.

@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

It is because port 53 is already in use Jun 23 18:12:02 m0054 dnsmasq[3420]: failed to create listening socket for port 53: Address already in use Jun 23 18:12:02 m0054 dnsmasq[3420]: FAILED to start up Jun 23 18:12:02 m0054 systemd[1]: dnsmasq.service: Control process exited, code=exited status=2 Jun 23 18:12:02 m0054 systemd[1]: dnsmasq.service: Failed with result 'exit-code'. Jun 23 18:12:02 m0054 systemd[1]: Failed to start dnsmasq - A lightweight DHCP and caching DNS server.

duplicate perhaps, see https://forum.modalai.com/topic/2313/no-gps-lock-for-vehicle

@Eric-Katzfey Oh, ha. I could have sworn it wasn't outputting my custom module status message. Checking again I see it though. That's silly.

@Aaky I sent you a link in email

@wilkinsaf Yup, this guy: https://www.modalai.com/products/voxl-lte?variant=39300535681075

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.

@wilkinsaf This is good insight, thanks!

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

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

@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.

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.