Sentinel 5G voxl-modem-start.sh error
-
This is the results from usb-devices:
T: Bus=02 Lev=02 Prnt=02 Port=00 Cnt=01 Dev#= 3 Spd=5000 MxCh= 0
D : Ver= 3.20 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 9 #Cfgs= 1
P: Vendor=2c7c ProdID=0800 Rev=04.14
S: Manufacturer=Quectel
S: Product=RM502Q-AE
S: SerialNumber=d0bdf96c
C : #Ifs= 5 Cfg#= 1 Atr=a0 MxPwr=896mA
I: If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=30 Driver=option
I: If#= 1 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=00 Driver=option
I: If#= 2 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=00 Driver=option
I: If#= 3 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=00 Driver=option
I: If#= 4 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=qmi_wwan -
Hi Justin
Does this SIM card work on your network already?
Have you configured the APN? It looks like you are using vzwinternet for your APN, is that the network you are trying to use?
Does this modem and SIM work on your network already?
-
@Chad-Sweet, we tried on the private 5G network first and it was a known good sim, we were able to see the modem on the networks dashboard but the ifconfig was showing no ip for it. also forced it to be a IPv4 to see if it would resolve the issue but it did not work.
Separately we have tried a known good Verizon sim and the same issue is seen.
I have ran the voxl-configure-modem, also tried disabling and stopping voxl-modem and used the quectel-CM -4 -s vzwnetwork for further troubleshooting. Also from the AT commands it looks like it is registering and populating everything correctly.
-
The maintainer is out on vacation. hopefully he can respond tomorrow.
One other thought, are there other networks configured in ifconfig that could be colliding? wifi for instance?
-
@Chad-Sweet i made sure there were no conflicts.
-
This post is deleted! -
@JustinDev23 What do you see with
quectel-CM -s vzwinternet? Do you get the same result? -
@tom correct same result,
[03-13_22:36:25:808] Quectel_QConnectManager_Linux_V1.6.0.24
[03-13_22:36:25:811] Find /sys/bus/usb/devices/2-1.1 idVendor=0x2c7c idProduct=0x800, bus=0x002, dev=0x003
[03-13_22:36:25:812] Auto find qmichannel = /dev/cdc-wdm0
[03-13_22:36:25:812] Auto find usbnet_adapter = wwan0
[03-13_22:36:25:812] netcard driver = qmi_wwan, driver version = 22-Aug-2005
[03-13_22:36:25:812] Modem works in QMI mode
[03-13_22:36:25:836] cdc_wdm_fd = 7
[03-13_22:36:25:926] Get clientWDS = 15
[03-13_22:36:25:958] Get clientDMS = 1
[03-13_22:36:25:989] Get clientNAS = 4
[03-13_22:36:26:022] Get clientUIM = 1
[03-13_22:36:26:053] Get clientWDA = 1
[03-13_22:36:26:086] requestBaseBandVersion RM502QAEAAR11A04M4G
[03-13_22:36:26:214] requestGetSIMStatus SIMStatus: SIM_READY
[03-13_22:36:26:214] requestSetProfile[1] vzwnetwork///0
[03-13_22:36:26:278] requestGetProfile[1] vzwnetwork///0
[03-13_22:36:26:310] requestRegistrationState2 MCC: 310, MNC: 260, PS: Detached, DataCap: UNKNOW
[03-13_22:36:26:342] requestQueryDataCall IPv4ConnectionStatus: DISCONNECTED
[03-13_22:36:26:342] ifconfig wwan0 0.0.0.0
[03-13_22:36:26:370] ifconfig wwan0 down -
@JustinDev23 Okay thanks, In the past I know Verizon didn't support this Quectel modem, I was following this thread to see if there was a resolution but it seems like there is some conflicting information: https://forums.quectel.com/t/rm502q-ae-is-not-supported-by-verizon/11882/7
Do you have any other SIM cards you can use? We use Google Fi for our internal use as it is quite easy to get a bunch of SIMs on data only contracts with them (it uses the T-Mobile mobile network)
-
@tom , this was what was provided to me, but we did see the same issue with a Private Celona 5G network. AT Commands showed it had registered and still didn't provide data connection.
-
@JustinDev23 What VOXL SDK do you have loaded for reference? If you could post the output of
voxl-version -
@tom
voxl2:/$ voxl-versionsystem-image: 1.4.1-M0054-14.1a-perf
kernel: #1 SMP PREEMPT Thu Oct 13 17:48:16 UTC 2022 4.19.125hw version: M0054
voxl-suite: 0.9.4
Packages:
Repo: http://voxl-packages.modalai.com/ ./dists/qrb5165/sdk-0.9/binary-arm64/
Last Updated: 2023-03-13 21:50:05
List:
libmodal-cv 0.2.3
libmodal-exposure 0.0.7
libmodal-journal 0.2.1
libmodal-json 0.4.3
libmodal-pipe 2.8.2
libqrb5165-io 0.1.0
libvoxl-cci-direct 0.1.5
libvoxl-cutils 0.1.1
mv-voxl 0.1-r0
qrb5165-bind 0.1-r0
qrb5165-dfs-server 0.1.0
qrb5165-imu-server 0.5.0
qrb5165-slpi-test-sig 01-r0
qrb5165-system-tweaks 0.1.5
qrb5165-tflite 2.8.0-2
voxl-bind 0.0.1
voxl-camera-calibration 0.2.3
voxl-camera-server 1.3.5
voxl-cpu-monitor 0.3.0
voxl-docker-support 1.2.4
voxl-gphoto2-server 0.0.10
voxl-jpeg-turbo 2.1.3-4
voxl-libgphoto2 0.0.4
voxl-libuvc 1.0.7
voxl-logger 0.3.4
voxl-mavlink 0.1.0
voxl-mavlink-server 0.3.0
voxl-modem 0.16.2-202210261800
voxl-mongoose 7.7.0-1
voxl-mpa-to-ros 0.3.6
voxl-mpa-tools 0.7.6
voxl-opencv 4.5.5-1
voxl-portal 0.4.2
voxl-px4 1.12.31
voxl-px4-imu-server 0.1.2
voxl-qvio-server 0.8.2
voxl-remote-id 0.0.5
voxl-streamer 0.4.1
voxl-suite 0.9.4
voxl-tag-detector 0.0.4
voxl-tflite-server 0.3.1
voxl-utils 1.2.2
voxl-uvc-server 0.1.3
voxl-vision-px4 1.4.0
voxl2-system-image 1.4.1-r0
voxl2-wlan 1.0-r0 -
I just loaded the voxl-modem package to a raspberry pi 3 with a sixfab carrier/quectel EG25G modem with the same verizon sim and it connected.
Not sure if that helps but i feel like it is a step in the right direction.
Is there a way to flush the voxl-modem package from voxl2 and reinstall it?
-
@JustinDev23 Well that's an entirely different set of hardware / modem so I'm not sure the two can really be compared.
I doubt you screwed up the package itself (quectel-CM is a standalone binary that is installed as part of the package) but if you really want to try that you can do
dpkg -r voxl-modemanddpkg -i /data/voxl-suite-offline-packages/voxl-modem*.deb -
@tom is there a way to force this removal?
voxl2:/$ dpkg -r voxl-modem
dpkg: dependency problems prevent removal of voxl-modem:
voxl-suite depends on voxl-modem (>= 0.16.1).dpkg: error processing package voxl-modem (--remove):
dependency problems - not removing
Errors were encountered while processing:
voxl-modem -
@tom i got it to remove with a force-all -r
-
@tom this resolved the issue. i also used the newer voxl-modem 0.16.2
-
@JustinDev23 So you are able to get a network connection going now?
-
@JustinDev23 v0.16.2 had a ton of Quectel related updates so it would makes since that things are working better now (I had timelines screwed up in my head so thought those were in 0.16.1)
-
good connection, tailscale is working, and all seems well on the benchtesting. thanks for the assist!
