@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@nekolny Hmm I would double check on another machine or with a different USB cable and if you still have issues issue an RMA:
@jbhines929 No problem, thanks for the patience!
@jbhines929 Hmm I would make sure you have the correct px4 parameter set loaded on your flight core, i.e. "outdoor_gps.params" from https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-px4-params/-/blob/master/params/v1.14/EKF2_helpers/outdoor_gps.params?ref_type=heads
@jbhines929 Interesting I wonder if that port is being blocked on your Ubuntu machine for some reason
@ashwin I don't have the info either but it's similar to VOXL2's weight which is 16g
@tom On VOXL make sure you've run voxl-configure-modem and selected microhard in the menu
@jbhines929 You'll want to establish a connection like this, where "Server Address" is the IP of the VOXL on the microhard network
You can check this with ifconfig on VOXL
@jbhines929 I would recommend loading the latest VOXL 1 SDK: 1.2.0 which can be downloaded from downloads.modalai.com
You'll want to follow the steps here: https://docs.modalai.com/flash-system-image/#flashing-a-voxl-sdk-release
@jbhines929 I'm curious what SDK is on that voxl-flight (It's been a while since I've worked with VOXL 1 personally so it'll take me a sec to get my brain aligned)
What do you see if you ADB in and run the following:
voxl-version
voxl-inspect-services
@nekolny It's possible we can still get ADB working for you. If you plug the voxl into your host machine (ideally linux) and run lsusb what do you see?
I'm wondering if it'll still enumerate