@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
@AnthoJack https://docs.modalai.com/configure-cameras/ You can start here and then modify
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@jmltt Apologies, context was lost. For clarity, sentinel was the last dev drone in which spektrum rc was supported and SDK 1.5.0 was the last SDK tested on said platform. Later SDKs have different gpio defaults which is why you're running into this issue
@jmltt The last ModalAI supported SDK on the Sentinel platform is SDK 1.5.0. Which doesn't mean that you won't success with newer SDKs, we just haven't tested with it.
@vmbasvi That appears to be a Microhard modem, not a WiFi dongle.
@Michael-Hatton Did you run through the voxl-configure-modem setup in order to configure APN, etc?
@Barry-Hammond https://docs.modalai.com/voxl-streamer/#how-to-stream-video-with-rtsp-on-voxl
Quality greatly depends on your LTE coverage and VPN performance. I recommend lowering the bitrate in /etc/modalai/voxl-streamer.conf until you're happy with the response rate.
Tailscale can add overhead as well and our recent LTE testing has involved hosting a custom WireGuard server.
@mkriesel It's possible the kernel you're flashing is incorrect. Can you provide the full terminal output of the install?
@Alan_S The voxl-vtx repository is currently private, the source code for both voxl-vtx and voxl-vrx are contained within.
@spiff You'll likely need to reach out to Sierra Wireless directly for debug help.