@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
@Gary-Holmgren Ah so that would be the issue, the default password of oelinux123 is hard-coded into the deploy_to_voxl.sh script
@saegsali What platform are you running? If you arm and get the drone in the air does the ov_overlay appear? This change was made to reduce CPU load on the ground, it can likely be turned off in /etc/modalai/voxl-open-vins-server.conf
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@mkriesel You'll need to re-flash the SDK and select the correct kernel option that supports C11.
When running ./install.sh you'll see the following options:
Would you like to continue with SDK install?
1) Yes, with questions along the way to configure VOXL 2
2) Yes, just update SDK keeping the same SKU configuration
3) No
Select, option 1, and you'll get the option to choose which kernel to flash
Detected: M0054-1 (QRB5165M)
Detected: Config 1 w/ M0173 Breakout Board (Starling 2 Max, Starling 2, FPV V5)
=======================================================================================================
In order to support all of VOXL's camera configurations, specific drones require differing kernel images.
Please select your drone hardware to proceed with flashing the appropriate kernel image.
=======================================================================================================
PLEASE SELECT WHICH KERNEL TO FLASH
0. M0054-1 -> QRB5165M, Starling (D0005), Sentinel (D0006), FPV V4 (D0008), D0010, PX4 Dev Kit (D0011)
1. M0054-1 -> QRB5165M w/ M0173 Camera Breakout Board, Starling 2 Max (D0012), Starling 2 (D0014), FPV V5 (D0008/D0019/D0020)
Select your choice from the options above
or press [Enter] to continue with current config:
For your use case, you'll want to select option 0 as you are not using an M0173 camera breakout board and the C11 camera config is inherited from the sentinel (D0006) platform.
@taiwohazeez What SDK version are you running? Can you post the output of voxl-version?
It seems as though some missing CPU stats are causing the values to by shifted by one, the 98.2% is likely from voxl-open-vins-server
@Ashish-Kumar This is very abnormal, I'd recommend submitting an RMA: https://www.modalai.com/pages/rma
@Ashish-Kumar Are you using the same USB-C cable and port on your host machine that worked before? Also are you running linux natively on your machine or in a VM?
@Ashish-Kumar Can you run the following and then plug in the board to your host machine after powering it on?
dmesg -wH
and then copy any relevant enumeration info here
@saegsali What platform are you running? If you arm and get the drone in the air does the ov_overlay appear? This change was made to reduce CPU load on the ground, it can likely be turned off in /etc/modalai/voxl-open-vins-server.conf
@kabumei I'd recommend reaching out to Ascend Engineering: https://www.ascendengineer.com/
@Ashish-Kumar What OS are you running on your host machine? If linux can you provide the output of lsusb with the board powered and plugged in?
@jmltt SDK testing for Sentinel ended at SDK 1.4.0
That doesn't mean that newer releases won't work, it just means we don't put it through the SW QA testing cycles that we do with our newer platforms.
You likely won't see any major performance improvements on Sentinel with newer SDK releases but there may be some nice quality of life additions such as helper scripts, voxl-portal updates and others.
If you have any questions about any specific packages feel free to ask.