streaming video to QGC over LTE

[groupo]

Re: RTSP Streaming (to QGC on Android) issues on VOXL Mini

Re: Streaming video over LTE

Along the same lines of the two replies above... I am trying to receive video from the drone in QGC over LTE.

I have a private LTE network and know the IPs of both my QGC and drone, thus can circumvent the VPN solution. I have already connected drone and QGC in this manner.

What I have tried:

I can set the rtsp link in QGC but in both the linux and android versions (both v4.4.0) but the second my Sentinel is connected via QGC the option to set anything in QGC goes away. if I disconnect my drone from QGC, the option reappears. I am not sure if this is 'taking'. I do not believe so as the QGC console always reports status messages looking for video stream from 192.168.8.1.

I have tried changing the default uri in voxl-mavcam-manager to the ip of my drone on the LTE network with the 8900 port, and tried disabling auto_ip as well.

I also tried to use VLC to open a rtsp stream to no avail. Likely I am not doing something proper in the config files

[groupo]

@groupo Hey I think I actually got this one on my own

1. I set default_uri in voxl-mavcam-manager.conf to the IP of my drone on the LTE network (rtsp://10.0.1.1:8900/live)

2. I had to modify /etc/modalai/network_interfaces_preferences.txt to include wwan0. I put it at the top of the list, but I believe so long as it is above wlan0 it should be fine for my use case.

Is there a better solution to this? Should wwan0 not be in that .txt? TIA

[groupo]

@groupo any traction on this? does step 1 actually impact anything with regard to the stream from voxl-streamer?

[groupo]

@groupo I updated to 1.3.3 and notice wwan0 is still not in network_interfaces_preferences.txt. Should it be?

[tom]

@groupo I'll add it, it's an uncommon use-case which is why it hasn't been in there.

[groupo]

@tom Thanks Tom!

[tom]

@groupo https://gitlab.com/voxl-public/voxl-sdk/utilities/voxl-utils/-/commit/562e196d9b7a74fbcda4405880062ab056fd1e3e

This change will make it into our next release (1.3.4)

[groupo]

@tom do you think it should go above wlan0? If someone was using the drone only via LTE (BVLOS) they may not have access to the WIFI network. Wlan0 by default exists as it comes up when the drone turns on (at least in ap mode, maybe not in station mode?) versus wwan0 which only comes up if it is connected to a network

[tom]

@groupo The problem is that wwan0 will also get an IP by default if a 5G modem is installed whether or not it is actually connected to a network so I wouldn't want that to take priority over wlan0.

Its tough to come up with a single solution that would work for each user so I have to choose the one that works for the majority of cases, some users may have to manually edit the file to fit their use case

[groupo]

@tom oh i see. I did not know it would happen either way. That makes sense then. I assume then eth0/usb0 are not given an Ip then because nothing is plugged into them?

[tom]

@groupo Exactly