@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.

@clarizza https://docs.modalai.com/flash-system-image/#flashing-a-voxl-sdk-release

@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:

https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-modem/-/blob/master/scripts/voxl-modem-start?ref_type=heads#L242

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

@Henry-Cappel See script here: https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-modem/-/blob/master/scripts/sierra-rpi-setup.sh

Pinouts are here: https://docs.modalai.com/lte-modem-v2-dongle-datasheet/#raspberrypi-4

Hi @jacksparkman ,

It looks as though you are running a Microhard connection. This may be interfering with your VOXL's ability to connect to the internet. You can disable the Microhard connection on startup by using systemctl disable voxl-modem and rebooting your VOXL. When you are ready to re-enable your Microhard connection you can use systemctl enable voxl-modem.

This may solve your issue. If not, are you using your VOXL's Wi-Fi in station mode and ssh'ing through your local network or in Soft AP mode and ssh'ing directly into VOXL?

You will need to have your VOXL in Station mode in order to SSH in as well as connect to the internet.

Thanks!
Tom

@Steve-Sager We don't support using Windows for flashing. Do you have an Ubuntu machine you could use to flash? Preferably Ubuntu 18.04.

@PawelJ Yep, it should be either 14550 or 14551.

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

• Install libmodal_json with opkg install libmodal_json
• Install voxl-mpa-tools with opkg install voxl-mpa-tools
• Back on your host pc, run ./install-on-voxl.sh

@soraminds Sounds good, if you have any questions in the future you know where to find answers! Our users often have plenty of processing power to spare when using VOXL 2.

@soraminds What do you mean by additional processor? What kind and how do you plan on passing data between this processor and VOXL 2? What kind of processing are you unable to do on VOXL 2?

@tom As we start our testing cycle and get close to release we will also start releasing "beta" SDKs which can be downloaded from the "platform-releases" bucket

@star123 Probably a couple weeks out.

We have nightly SDK's built with the latest off of the dev branch of each repo, here is last night's: https://storage.googleapis.com/platform-nightlies/voxl2/voxl2_SDK_nightly_20241118.tar.gz

You can find a new one published each day via date.

These are completely untested so can't guarantee any functionality but this will represent the tip of our development.

@soraminds https://www.modalai.com/products/mdk-m0090?variant=47319040327984

Sentinel may already have an M0090 in it, likely without the Sierra Wireless modem

@star123 Yes it is only using one tracking camera by default. Our next SDK release will switch VIO from QVIO to VINS which will use multi-cam input by default.

@mario Should be the same, if you're seeing that LED pattern then binding mode has started correctly

@perfx I'd recommend reaching out to Ascend Engineering, they're ModalAI product experts and they'll be able to help you out: https://www.ascendengineer.com/

@mario There should be only physical button on the receiver itself, pressing and holding it for a couple seconds within 30 seconds of powering on should put it into bind mode

@perfx Here's a good start for sw/hw implementation: https://docs.modalai.com/voxl2-external-flight-controller/