@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@tom I just ran the following successfully:
cd voxl-tflite-server
git checkout master
git pull
voxl-docker -i voxl-cross:V2.7
./install_build_deps.sh qrb5165 sdk-1.4
./build.sh qrb5165
./make_package.sh
here's a snippet
[ 60%] Building CXX object src/CMakeFiles/voxl-tflite-server.dir/model_helper/generic_object_detection_model_helper.cpp.o
[ 66%] Building CXX object src/CMakeFiles/voxl-tflite-server.dir/model_helper/yolov5_model_helper.cpp.o
[ 73%] Building CXX object src/CMakeFiles/voxl-tflite-server.dir/model_helper/posenet_model_helper.cpp.o
[ 80%] Building CXX object src/CMakeFiles/voxl-tflite-server.dir/model_helper/yolov8_model_helper.cpp.o
[ 86%] Building C object src/CMakeFiles/voxl-tflite-server.dir/resize.c.o
[ 93%] Building CXX object src/CMakeFiles/voxl-tflite-server.dir/utils.cpp.o
[100%] Linking CXX executable voxl-tflite-server
/usr/lib64//libtensorflow-lite.a(nnapi_delegate.cc.o): In function `tflite::delegate::nnapi::NNMemory::NNMemory(NnApi const*, char const*, unsigned long)':
nnapi_delegate.cc:(.text+0xd58): warning: the use of `tmpnam' is dangerous, better use `mkstemp'
[100%] Built target voxl-tflite-server
voxl-cross(2.7):~(master)(0.4.1)$ ls
CHANGELOG build include scripts
CMakeLists.txt build.sh install_build_deps.sh services
LICENSE clean.sh make_package.sh src
README.md debug_source.sh misc_files
bash_completions deploy_to_voxl.sh pkg
voxl-cross(2.7):~(master)(0.4.1)$ ./make_package.sh
Package Name: voxl-tflite-server
version Number: 0.4.1
Consolidate compiler generated dependencies of target voxl-tflite-server
[100%] Built target voxl-tflite-server
Install the project...
-- Install configuration: "DEBUG"
-- Installing: ../pkg/data/usr/bin/voxl-tflite-server
/home/root
starting building Debian Package
dpkg-deb: building package 'voxl-tflite-server' in 'voxl-tflite-server_0.4.1_arm64.deb'.
DONE
@Wondosen You're building voxl-tflite-server which is part of SDK 1.4.4, while calling install_build_deps.sh qrb5165 dev will pull the dependencies for a much newer version of voxl-tflite-server than you're using.
Try running ./install_build_deps.sh qrb5165 sdk-1.4
@Wondosen How are you running ./install_build_deps.sh?
@Muqing-Cao Yes that would work as well
@mkriesel I recommend connecting the drone to QGroundControl and using the spin tool through there to determine correct orientation. voxl-esc spin doesn't take into account anything px4 is doing to determine motor direction so won't be entirely accurate in term of what direction the motor will spin via the flight controller.
@Thomas-Müller you can read up on our "VOA" implementations here: https://docs.modalai.com/voa/
@Muqing-Cao If you don't want a bulky USB hub on there you can use a different add-on board like this one: https://www.modalai.com/products/m0130-3?variant=48186331693360
it has 1 USB 3.0 and 2 USB 2.0 ports
@Thomas-Müller See here for info on connecting an external flight controller to VOXL 2: https://docs.modalai.com/voxl2-external-flight-controller/
@Muqing-Cao On Starling 2 there is likely a wifi dongle in that port
@wilt From the production team, these should work for you: https://www.mcmaster.com/99461A923/