@ryan_meagher You should be able to do this using the /etc/network/interfaces approach you mentioned. voxl-modem uses that approach in order to set a static IP for Microhard on eth0. This is what the /etc/network/interfaces file looks like in that case:
# This file describes the network interfaces available on your system
# The primary network interface
auto eth0
iface eth0 inet static
address 192.168.168.100
netmask 255.255.255.0
gateway 192.168.168.1
@SmittyHalibut That page may be outdated. You definitely can set a static IP on eth0, it is required for Microhard usage. For example voxl-modem uses the interfaces file here for setting a static IP: https://gitlab.com/voxl-public/utilities/voxl-modem/-/blob/master/config/interfaces
It does require pulling down / up the interface on boot: https://gitlab.com/voxl-public/utilities/voxl-modem/-/blob/master/scripts/voxl-modem#L516 which may be a solution for @Sem-Andeweg
@Djalma-Ribeiro You can create a systemd service file and enable it to run on boot and have it execute the OpenVPN connection command.
Here is an example on how we have used it in the past on a VOXL:
[Unit]
After=voxl-time-sync.service
Requires=voxl-time-sync.service
[Service]
Type=forking
ExecStartPre=/bin/sleep 2
ExecStart=/usr/sbin/openvpn --script-security 2 --daemon --config /etc/openvpn/KEY_FILE
[Install]
WantedBy=default.target
Won't be exactly the same as above but that's the general idea.
@Nicholas-Hansen In order to set an IP address at boot you could create a systemd service that runs a script similar to this portion of the voxl-modem startup script:
You could probably highjack the doodle workflow if you really want to. It's pretty basic, it just waits for the network interface to enumerate and sets the IP address if it is different from what is set in the config file. It then monitors that interface and sets the IP again if it ever changes
echo -e "\nWaiting for eth0..."
rc=1
while [ $rc -ne 0 ]; do
ifconfig -s | grep eth0
rc=$?
sleep 1
done
echo -e "\neth0 initialized"
# loop and re-set IP if network interface goes down and back up
while true
do
# grab ip address from eth0
eth0_ip=$(ip -4 addr show eth0 | grep -oP '(?<=inet\s)\d+(\.\d+){3}' | head -1)
# if it's not what we expect, fix it
if [[ "$eth0_ip" != *"$DOODLE_IP"* ]]; then
echo "setting IP address to: $DOODLE_IP"
ifconfig eth0 $DOODLE_IP netmask 255.0.0.0 up
fi
sleep 1
done
@Steve-Sager We don't support using Windows for flashing. Do you have an Ubuntu machine you could use to flash? Preferably Ubuntu 18.04.
@wilkinsaf I came across this article from Logitech: https://www.logitech.com/en-us/video-collaboration/resources/think-tank/articles/taa-ndaa-compliant-products.html
Their webcams have worked well for us in the past so I'd think one of the mentioned products would work.
@Djalma-Ribeiro Awesome thank you, just wanted to make sure your RB5 had the SDK loaded properly, which it does.
It's not absolutely necessary to upgrade the SDK, if you do want to you can follow the steps here: https://docs.modalai.com/Qualcomm-Flight-RB5-sdk-installation/#how-to-upgrade
One note, if you try to upgrade the SDK while PX4 is running it will fail. So in order to upgrade the SDK you would have to disable PX4 from starting systemctl disable rb5-px4-start and then reboot your drone before upgrading your SDK.
I would rebuild using the master branch and do the following:
You can use the opkg server in order to install the dependencies.
In /etc/opkg/opkg.conf uncomment the line #src/gz dev http://voxl-packages.modalai.com/dev.
Then, call opkg update
opkg install libmodal_jsonopkg install voxl-mpa-tools./install-on-voxl.sh@Steve-Sager That's interesting, you can use vi to modify the file and enter the correct IP in the qgc_ip field, vi /etc/modalai/voxl-vision-px4.conf
@PawelJ It looks as though you are using the correct IP in your config file and voxl-vision-px4 is running correctly. Is it possible that you have some custom firewall setup on your host PC that is blocking traffic on that port?
@chris_macdonald @kitkatSG Here is an example of how to send an AT command to the Quectel modem:
echo -ne "AT+QNWPREFCFG=\"mode_pref\",LTE:NR5G\r" | busybox microcom -t 1000 /dev/ttyUSB2
The above gets ran as part of rb5-modem in order to set the network preference to allow both LTE and 5G.
Here is a link to the Quectel RM5* series modem AT command manual, you can probably find a relevant AT command to use there: https://www.quectel.com/wp-content/uploads/2021/05/Quectel_RG50xQRM5xxQ_Series_AT_Commands_Manual_V1.2.pdf
@Daniel-Ryu Check out the documentation here: https://docs.modalai.com/docker-on-voxl/
Try running voxl-configure-docker-support.sh
I would also make sure that you're able to ping your PC from your drone.
@Κωνσταντίνος-Κλέων-Χριστόπουλος No hardware reset but you can easily load the latest PX4 release through QGroundControl after downloading voxl_SDK_1.2.0.tar.gz from our downloads page (downloads.modalai.com) and finding the FCv1 .px4 file in the flight-core directory
@PawelJ There isn't an exact way to do that, if you want you could edit your initial question and add a [SOLVED] section at the top and describe the solution.
@nacho I'm seeing references to modallink-relink, that shouldn't be used in your configuration. I would run through voxl-configure-modem again and make sure you answer "no" to "Are you attempting to connect to ModalLink?".
Or you can disable it with systemctl disable modallink-relink and a reboot.
@jbruell94 I would look at the MAVSDK Python source examples here: https://github.com/mavlink/MAVSDK-Python/tree/main/examples
I believe it is one of the "MissionItem" params in the example here: https://github.com/mavlink/MAVSDK-Python/blob/edd21f4d95a5a37ca1a24fd7ffb97da5bfb9d86d/examples/mission.py#L27
We don't develop MAVSDK ourselves so those questions may be better suited for the PX4 forum / slack: https://discuss.px4.io/c/mavsdk/19