@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
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@Κωνσταντίνος-Κλέων-Χριστόπουλος 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 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?
@DanielHviid The voxl-modem python script itself is not used for the 5G modem at all, nor is it meant to be run manually from the command line.
The modem should enumerate on boot regardless of any other voxl-modem processes running, check this with ifconfig wwan0
I recommend running voxl-configure-modem and selecting quectel from the options. It will then ask if you're connecting to ModalLink, choose no. Lastly it'll ask for the APN of your SIM card, choose from the list or enter a custom one.
Once this is complete, the voxl-modem systemd service will startup and attempt to connect to your 5G network, the status of this service can be monitored with systemctl status voxl-modem
@local-ad A couple bits of info for you:
I'm sure you've been looking at docs.modalai.com, but it has pages describing about anything you can do with VOXL. I can help point you in the right direction if you're confused.
As for the yocto / voxl prompt, that part doesn't matter at all, if you're running the bash shell on VOXL you will see the voxl prompt. All that gives you is some color output in the shell as well as autocomplete for some of the voxl-* commands.
For some about using docker on VOXL, checkout this doc here:
For flying / communicating with a ground control station over 4G, see the following docs:
Connecting to QGC in general:
@Daniel-Ryu Check out the documentation here: https://docs.modalai.com/docker-on-voxl/
Try running voxl-configure-docker-support.sh
@Κωνσταντίνος-Κλέων-Χριστόπουλος We only really use Ubuntu here so that would be a good thing to try.
I missed that you said the drone was in WiFi AP mode
You can SSH onto the drone by connecting to that wifi (password 1234567890) and running:
ssh root@192.168.8.1
the ssh password is oelinux123
@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.
@DanielHviid Ensure that both black board to board connectors (left side in pic) are fully seated, the board looks a little crooked. Also double check that the Quectel module itself is fully seated in the pci slot.
What software version are you running on your voxl2? You can check this with: voxl-version
@Joshua-Ermias yes that would be the easiest way. You can either restart the service with systemctl restart voxl-camera-server or just power cycle your VOXL
@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