@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@Andrew-Martin Okay cool, confirmed you have an M0054-1 so that is correct.
With SDK 1.4.5, can you try running the full install.sh script?
@justin-sentinel Can you be more specific with your question? Firmware for what? the Transmitter? The drone?
@Andrew-Martin I would stick with SDK 1.4.5, what is the serial number of your drone? I can make sure you're choosing the correct kernel option when flashing.
Serial number is on a sticker in the form MXX00000XXX
@taiwohazeez No problem, it would also be helpful to know what SDK version is loaded on your drone. You can check this with voxl-version
@taiwohazeez I recommend connecting the drone to QGroundControl via WiFi and then seeing what PX4 pre-arm checks are failing
@Muqing-Cao Stinger runs the same VOXL SDK that is ran on starling and other platforms. Absolutely open for development and capable of autonomous command in the same way
@Hector-Gutierrez You can use them concurrently, just specify which to run like so voxl-docker -i voxl-cross:V2.7
If you don't specify which version to use it'll default to whichever is tagged with latest
@tom I believe we're also still building voxl-vision-hub with voxl-cross:V2.7, we're in a bit of a transition period of moving packages to the newer voxl-cross and I don't think voxl-vision-hub has been moved over yet
@taiwohazeez I unfortunately don't have any knowledge that isn't on our public docs link that I shared
@Hector-Gutierrez Your VOXL2 is running Ubuntu 20 or your host machine is Ubuntu 20?
We don't build voxl-vision-hub for ubuntu 20 so that isn't correct