@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

@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

@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

@nickrobbins I would take at stinger as a place to start: https://www.modalai.com/products/stinger-vision-fpv?variant=48373207695664

It is on the Blue UAS list: https://www.diu.mil/blue-uas-cleared-list (Stinger Vision FPV)

@ahmettahsin We do not provide any water proofing solutions for this development drone.

There are third party 3d printable propellor guards available: https://www.printables.com/model/594819-modalai-starling-prop-guards

@Dmytro-Stolbovyi Here is the updated link: https://docs.modalai.com/voxl2-unbricking/

@greg_s Great! Sounds good

@greg_s Was this originally a starling 1 that was upgraded to a starling 2?

If so, you will need to re-calibrate the tracking cameras for this new drone.

See here: https://docs.modalai.com/calibrate-cameras/

@greg_s That looks normal to me. I would start by attempting a manual flight before doing any cv-based flights:

https://www.youtube.com/watch?v=Cpbbye3Z6co

@tom https://www.printables.com/model/594819-modalai-starling-prop-guards

@mamuncanada Looks like a third-party has done it: https://forum.modalai.com/topic/2696/3d-printable-prop-guard

@greg_s Okay you'll need to load a different kernel on your drone in order to support that camera configuration. (27) That is why it is not showing up in the list of supported configs.

You can do the following:

cd voxl2_SDK_1.4.5.tar.gz
cd system-image
adb reboot bootloader
fastboot flash boot_a m0054-1-var00.1-kernel.img
fastboot flash boot_b m0054-1-var00.1-kernel.img
fastboot reboot

Once rebooted, you can now run voxl-configure-cameras 27

@greg_s It's a different command, not the calibration command, voxl-configure-cameras