@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
@shawn_ricardo Not really a better way at this point, I'd like to at some point just make the network interface able to be specified in the config file as opposed to hard-coded as eth0, but haven't gotten to that yet
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@greg_s Just pinged our support team, they're taking a look at it now
@Kiazoa-Joao At this point it's probably worth sending it in for an RMA: https://www.modalai.com/pages/rma
@tom Or if you don't want to reset all of them, you can just run voxl-configure-vision-hub factory_enable
@QSL I would run voxl-configure-mpa and it'll reset all config files to default
@greg_s Apologies, correct email is contact@modalai.com or fill out the form here: https://www.modalai.com/pages/contact-us
@Kiazoa-Joao Can you try the following on a native linux system:
sudo dmesg -wH
Power on and plug in m500 via USB
Monitor output from dmesg and post any relevant messages here
@greg_s You can reach out to support@modalai.com and they may be able to help you either purchase that piece or print your own if you're capable
@greg_s See here for upgrading the camera stack: https://www.modalai.com/products/m0173?variant=48528274391344
@Daniel-Rincon Others will likely chime in, but OVINS allows you to run multi-cam VIO which in general will be more accurate than single-cam which is all that QVIO can do
@Daniel-Rincon QVIO (voxl-qvio-server) and OVINS (voxl-open-vins-server) are two different VIO algorithms. Currently only one can be used at a time. If you take a look at /etc/modalai/voxl-vision-hub.conf you should be able to specify which to use.