You could also convert the script into a Windows batch file or some other Windows scripting language. But there are Debian specific things in the script file that you would need to convert to the Windows alternative. For example, there are package management commands (apt) that would need to be changed into something for Windows and you would need to use the Windows version of QEMU. This could be a challenging task!

If you can use a Docker container for you application then you can run Ubuntu or Alpine and get access to a lot of packages. If you run on target without a container then you are much more limited in what you can do to resolve dependencies. opkg isn't like apt-get where you can point to large package repositories to find your missing dependencies. In this case you will likely have to build and install libxslt yourself.

Thanks for the feedback! The documentation has been updated.

You should build up your Docker images with a Dockerfile and 'docker build'. However, if you make changes in the container that you want to keep then, yes, you can use 'docker commit'. There is a lot of good documentation on the Docker site about all of this.

gstreamer in a Docker also works

voxl-streamer is the recommended approach. Documentation for that is here: https://docs.modalai.com/voxl-streamer/

You can also run ffmpeg in a Docker to access a UVC camera.

@shlee853 Yes, voxl-streamer uses RTSP. What kind of wireless link are you using to stream the video? What application are you using to view the video? What kind of latency are you seeing with this setup? And, ultimately, what is your target latency? The answers to these questions will help guide potential solutions.

@Dean-Fortier The issue with the path was that, originally, it was specified as "hires/preview". This is where voxl-camera-server created the pipe and where voxl-streamer looked for it. In a newer version of voxl-camera-server, the name changed to "hires_preview". Until voxl-streamer was updated, you had to manually go into the configuration file and change it yourself. Now voxl-streamer has been updated and the manual change is no longer necessary. That is what is in 3.2.0-0.3.4-b. You can take a look at the directories yourself to see what voxl-camera-server is doing. After a power cycle and before you start voxl-camera-server you should see something like this:

yocto:/run/mpa# ls
imu0  imu1

And then after starting voxl-camera-server you will see the new directories:

yocto:/run/mpa# ls
hires_preview  imu0  imu1  stereo  tracking

If you don't see those directories then the problem is somewhere else.

@Arrowtec The issue is that the modem is held in reset until the Voxl software pulls it out of reset. Once it has been pulled out of reset it has to boot up and initialize it's interfaces before it is ready to set up a connection. So, it is important to start the process as early as possible in the startup sequence. Are you using a systemd service file to start your modem connection?

@Arrowtec Can you explain your use case a little more? Are you referring to the time it takes to get the initial Internet connection up or are you also including the time to connect to a VPN?