@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

@wilkinsaf should be good now

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

@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

@local-ad What are you trying to do?

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

@swickliff Interesting, have you had success with this hardware setup before?

@swickliff Can you post a picture of your setup?

@KnightHawk06 That is the source, yes.

@GlennTee yes that's what I meant. You'll have to git clone the repo instead of just downloading it in order for that to work

@GlennTee You'll want to run that outside of the docker container, before running voxl-docker

@KnightHawk06 With VOXL 2 different kernels enable different camera configurations. You'll want to flash the kernel that supports camera configs 1-25,

I recommend downloading the latest SDK from downloads.modalai.com, running ./install.sh and when asked the following:

Detected OS: Linux
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
1. M0054-1 -> QRB5165M, Starling (D0005), Sentinel (D0006), FPV V4 (D0008), D0010, PX4 Dev Kit (D0011)
2. M0054-1 -> QRB5165M w/ M0173 Camera Breakout Board, Starling 2 Max (D0012), Starling 2 (D0014), FPV V5 (D0008)

Select your choice from the options above
or press [Enter] to continue with current config: 

Choose option 1 for M0054-1 -> QRB5165M, Starling (D0005), Sentinel (D0006), FPV V4 (D0008), D0010, PX4 Dev Kit (D0011)

@Jetson-Nano We have never used Microhard on windows but it's possible your firewall is blocking UDP data on that port

@pettertei I'd recommend filing an RMA and we can debug the issue: https://www.modalai.com/pages/rma

@Matthew-Wellner That isn't an error message. We manually set the cores voxl-camera-server is allowed to use in order to maximize performance

@GlennTee Thanks for the follow up!