How can I monitor the Sierra Wireless modem's 5G signal quality or statistics? Ideally in real time, but in logging can be worked with also.

Thank you.

@Thomas-Eiszler That's the plan we're working towards also, I did make some tries with AT commands also, but had to put the work aside for other commitments in the past few weeks. The information from yourself and @groupo above helps a lot. It shouldn't be too hard to make a service out of a python script for this. I'd been pursuing getting the data direct from the Qualcomm chipset, but AT commands and gpsd queries seen to be the way to go.

@David-Smyth Would you be willing to share the .service files you created?

@guyzoler Don't set a default gateway on the interface with a static IP.

@pthomason Anyone have thoughts on correcting IP bindings, or the list of services that need to be restarted to notice a new 5G connection?

@pthomason restarting voxl-mavlink-server seems to have restored QGroundControl connectivity with the 5G already connected.

I just upgraded to VOXL SDK 1.3.3, and am trying to connect QGroundControl our Sentinel via a private 5G network. My ground control PC is able to SSH to the drone, but I'm not able to establish a MAVLink connection. voxl-mavlink-server, voxl-px4 and voxl-vision-hub are all running. I've noticed that voxl-my-ip returns the WiFi IP, not the 5G IP, so I'm wondering if the services are bound to the correct interface.

@Kiazoa-Joao Are you using the wall power adapter or full batteries? The power adapter doesn't have enough current to support the motors at full speed.

How can I monitor the Sierra Wireless modem's 5G signal quality or statistics? Ideally in real time, but in logging can be worked with also.

Thank you.

@tom

Well that's embarrassing, corrected and attached, n78 SA.
Thank you.

@tom
I believe the system is seeing the modem.
ifconfig

voxl2:/$ ifconfig
bond0: flags=5123<UP,BROADCAST,MASTER,MULTICAST>  mtu 1500
        ether e6:26:28:f5:c3:21  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

dummy0: flags=195<UP,BROADCAST,RUNNING,NOARP>  mtu 1500
        inet6 fe80::2000:8a54:2e31:b142  prefixlen 64  scopeid 0x20<link>
        ether 92:70:d1:73:86:6a  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 97  bytes 32086 (32.0 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 2248527  bytes 246402579 (246.4 MB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 2248527  bytes 246402579 (246.4 MB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 2312
        inet 192.168.8.1  netmask 255.255.255.0  broadcast 192.168.8.255
        inet6 fe80::206b:34a1:b142:1286  prefixlen 64  scopeid 0x20<link>
        ether 00:c0:ca:b5:ab:77  txqueuelen 1000  (Ethernet)
        RX packets 3750  bytes 541680 (541.6 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 154460  bytes 16419695 (16.4 MB)
        TX errors 0  dropped 122100 overruns 0  carrier 0  collisions 0

wwan0: flags=4291<UP,BROADCAST,RUNNING,NOARP,MULTICAST>  mtu 1500
        inet6 fe80::f520:d7f4:4c5:dc9f  prefixlen 64  scopeid 0x20<link>
        ether fe:c0:cf:f3:db:95  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 81  dropped 0 overruns 0  carrier 0  collisions 0

lsusb

voxl2:/$ lsusb
Bus 002 Device 003: ID 1199:90e3 Sierra Wireless, Inc.
Bus 002 Device 002: ID 0424:5744 Standard Microsystems Corp.
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 0424:2740 Standard Microsystems Corp.
Bus 001 Device 003: ID 0bda:0811 Realtek Semiconductor Corp.
Bus 001 Device 002: ID 0424:2744 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

lsusb -t

voxl2:/$ lsusb
Bus 002 Device 003: ID 1199:90e3 Sierra Wireless, Inc.
Bus 002 Device 002: ID 0424:5744 Standard Microsystems Corp.
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 0424:2740 Standard Microsystems Corp.
Bus 001 Device 003: ID 0bda:0811 Realtek Semiconductor Corp.
Bus 001 Device 002: ID 0424:2744 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub