@황인호 It isn't required to use voxl-modem to interact with the modems if you'd like to do a custom config. In your case, I'd recommend using voxl-configure-modem with the quectel option to handle Quectel bringup and then creating a custom script / service file (or modifying the existing one) to handle doodle bringup. Although doodle bringup is very basic, if you follow the code path here in the startup script: https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-modem/-/blob/master/scripts/voxl-modem-start#L99 it monitors the eth0 network interface and if the IP address isn't what is specified in the config file then it assigns said IP address. This could be broken out into a different script

@I_Dwyer I have been down the rabbit hole here. It seems that qualcomm has not used any of the standard network management tools like Netplan. They use a hybrid of Systemd-Networkd and a wide range of complex scripts to manage all the interfaces. None of the scripts are standard. I am at the point of possibly stripping all of that out, and replacing it with either Ifupdown or Netplan and creating a firmware build that works better for our use case. There are a number of problems with the older Qualcomm network scripts, such as the DHCP management you are encountering. For example I have noticed that if WWAN0 has an IP, then WLAN0 will NOT get an IP from the DHCP server, even thought the wifi is connected to the local AP! To get around that I added an ifconfig statement issuing a static IP to wlan0 every time the drone boots, but this is a hacky solution. Would like to see ModalAI replace the entire Network Management stack with something better and easier to maintain.

@afdrus the relocalization is external to the VIO EKF. You can trace this code path here: https://gitlab.com/voxl-public/voxl-sdk/services/voxl-vision-hub/-/blob/master/src/tag_manager.c#L110

@tom Yes, thanks! That is a good idea. I will do that. I was looking at the release page of the system image and saw this line with 1.5.3 internal release: HLOS Added service file that changes SLPI restart level to avoid board crash when SLPI crashes What is SLPI and could you describe a little bit more what kind of issues you saw when SLPI crashed? I also sometimes saw px4io io_reg_get(4,0,15): data error -5 in the logging so maybe that could be related?

@Chad-Sweet Thank you for getting back to me. The radio we are leaning to use has an SPI interface. However, I am not opposed to switching radios if there is an easier to use I/O on the VOXL. We are leaning to using Adafruit RFM95W based on the SX1276 LoRa module with SPI interface.

@Chad-Sweet Thanks for reply, I am just triggering via python subprocess voxl-send-command hires_snapshot snapshot able to get snapshots. will try to look into mavsdk also.

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