Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
Collapse
Brand Logo

ModalAI Forum

S

spiff

@spiff
Unfollow Follow
About
Posts
5
Topics
2
Shares
0
Groups
0
Followers
0
Following
0

Posts

Recent Best Controversial

  • 5G Modem Cannot Connect to Private 5G Network
    S spiff

    Hello,

    We have a sentinel drone with the EM9291 Sierra Wireless modem and are attempting to connect to a private 5G network. The modem seems to recognize the SIM, but has failed to reach out and attempt connecting to the network.

    voxl-modem.conf:

    voxl2:/$ cat /etc/modalai/voxl-modem.conf 
    {
    	"modem_type":	"em9291",
    	"apn":	"internet",
    	"world":	"false",
    	"microhard_ip": "192.168.168.100",
    	"dtc_ip": "192.168.0.100",
    	"doodle_ip": "10.223.0.100",
    	"modallink":	"false",
    	"placeholder": "hello world"
    }
    

    This is the output to voxl-modem-start:

    voxl2:/$ voxl-modem-start 
    
    qrb5165 based hardware detected...
    wwan0 is up!
    Sierra detected!
    
    Starting qmi network...
    error: couldn't start network: QMI protocol error (14): 'CallFailed'
    call end reason (3): generic-no-service
    verbose call end reason (3,2001): [cm] no-service
    [/dev/cdc-wdm0] Client ID not released:
    	Service: 'wds'
    	    CID: '44'
    Error detected! Retrying...
    error: couldn't start network: QMI protocol error (14): 'CallFailed'
    call end reason (3): generic-no-service
    verbose call end reason (3,2001): [cm] no-service
    [/dev/cdc-wdm0] Client ID not released:
    	Service: 'wds'
    	    CID: '45'
    

    I've noticed the SIM is listed as 'illegal' from the output of qmicli -d /dev/cdc-wdm0 --uim-get-card-status:

    voxl2:/$ qmicli -d /dev/cdc-wdm0 --uim-get-card-status
    [/dev/cdc-wdm0] Successfully got card status
    Provisioning applications:
    	Primary GW:   slot '1', application '1'
    	Primary 1X:   session doesn't exist
    	Secondary GW: session doesn't exist
    	Secondary 1X: session doesn't exist
    Slot [1]:
    	Card state: 'present'
    	UPIN state: 'not-initialized'
    		UPIN retries: '0'
    		UPUK retries: '0'
    	Application [1]:
    		Application type:  'usim (2)'
    		Application state: 'illegal'
    		Application ID:
    			A0:00:00:00:87:10:02:FF:FF:FF:FF:89:07:09:00:00
    		Personalization state: 'ready'
    		UPIN replaces PIN1: 'no'
    		PIN1 state: 'disabled'
    			PIN1 retries: '3'
    			PUK1 retries: '10'
    		PIN2 state: 'enabled-not-verified'
    			PIN2 retries: '3'
    			PUK2 retries: '10'
    	Application [2]:
    		Application type:  'isim (5)'
    		Application state: 'detected'
    		Application ID:
    			A0:00:00:00:87:10:04:FF:FF:FF:FF:89:07:09:00:00
    		Personalization state: 'unknown'
    		UPIN replaces PIN1: 'no'
    		PIN1 state: 'disabled'
    			PIN1 retries: '3'
    			PUK1 retries: '10'
    		PIN2 state: 'not-initialized'
    			PIN2 retries: '0'
    			PUK2 retries: '0'
    Slot [2]:
    	Card state: 'absent'
    	UPIN state: 'not-initialized'
    		UPIN retries: '0'
    		UPUK retries: '0'
    

    The system mode seems to be rotating through WCDMA, LTE, and NR5G based on the output from AT commands and qmicli -d /dev/cdc-wdm0 --nas-get-system-selection-preference:

    voxl2:/$ qmicli -d /dev/cdc-wdm0 --nas-get-system-selection-preference
    [/dev/cdc-wdm0] Successfully got system selection preference
    	Emergency mode: 'no'
    	Mode preference: 'cdma-1x, cdma-1xevdo, gsm, umts, lte, td-scdma'
    	Band preference: 'wcdma-2100, wcdma-pcs-1900, wcdma-1700-us, wcdma-850-us, wcdma-800, wcdma-900, wcdma-850-japan'
    	LTE band preference: '1, 2, 3, 4, 5, 7, 8, 12, 13, 14, 17, 18, 19, 20, 25, 26, 28, 29, 30, 34, 38, 39, 40, 41, 42, 43'
    	LTE band preference (extended): '1, 2, 3, 4, 5, 7, 8, 12, 13, 14, 17, 18, 19, 20, 25, 26, 28, 29, 30, 32, 34, 38, 39, 40, 41, 42, 43, 46, 48, 66, 71'
    	TD-SCDMA band preference: 'a, b, c, d, e, f'
    	Roaming preference: 'any'
    	Network selection preference: 'manual'
    	Service domain preference: 'cs-ps'
    	GSM/WCDMA acquisition order preference: 'automatic'
    	Acquisition order preference: (null), lte, umts
    
    voxl2:/$ busybox microcom /dev/ttyUSB0
    AT!ENTERCND="A710"
    OK
    AT!GSTATUS?
    !GSTATUS: 
    Current Time:  412688		Temperature: 40
    Thermal Mitigation Level: 0
    
    Reset Counter: 1		Mode:        ONLINE         
    System mode:   LTE        	PS state:    Not attached 
    LTE band:      No band		LTE bw:      1.4 MHz 
    LTE Rx chan:   ---		LTE Tx chan: ---
    EMM state:     ---            	---            
    RRC state:     DISCONNECTED    
    IMS reg state: NOT REGISTERED  	IMS mode:    Normal       
    IMS Srv State: UNKNOWN SMS,UNKNOWN VoIP
    
    PCC Rx0 RSSI:  --- 		PCC Rx0 RSRP:  --- 
    PCC Rx1 RSSI:  --- 		PCC Rx1 RSRP:  --- 
    PCC Rx2 RSSI:  --- 		PCC Rx2 RSRP:  --- 
    PCC Rx3 RSSI:  --- 		PCC Rx3 RSRP:  --- 
    PCC Tx Power:  ---		TAC:         ---
    RSRQ (dB):     ---		Cell ID:     ---
    SINR (dB):     0
    
    NR5G band:       ---		NR5G bw:         ---		
    NR5G Tx Power:   ---		NR5G Tx chan:    ---		
    NR5G Rx chan:    ---		NR5G RSRP (dBm): ---		
    NR5G RSRQ (dB):  ---		NR5G SINR (dB):  ---		
    
    
    OK
    AT!GSTATUS?
    !GSTATUS: 
    Current Time:  412694		Temperature: 40
    Thermal Mitigation Level: 0
    
    Reset Counter: 1		Mode:        ONLINE         
    System mode:   NR5G       	PS state:    Not attached 
    MM5G state:    Deregistered     Limited Service
    RRC state:     RRC Idle        
    IMS reg state: NOT REGISTERED  	IMS mode:    Normal       
    IMS Srv State: UNKNOWN SMS,UNKNOWN VoIP
    
    NR5G TAC:        000001        		NR5G Cell ID:    D15 (3349)
    NR5G band:       n78       		NR5G Carrier ID: 0
    NR5G dl bw:      100 MHz   		NR5G ul bw:      100 MHz   
    NR5G Tx Power:   ---        		NR5G Tx chan:    0
    NR5G Rx chan:    622260
    NR5G dl MIMO:    4         		NR5G ul MIMO:    1
    NR5G(sub6) Rx0 RSSI (dBm):   -51.8	NR5G(sub6) Rx1 RSSI (dBm):   -51.3
    NR5G(sub6) Rx2 RSSI (dBm):   ---  	NR5G(sub6) Rx3 RSSI (dBm):   ---	
    
    NR5G RSRP (dBm): -79			NR5G RSRQ (dB):  -11
    NR5G SINR (dB):  22.0
    
    
    OK
    AT+C5GREG?
    +C5GREG: 0,0
    
    OK
    AT!NRINFO?
    !NRINFO: 
    Connectivity Mode: SA
    
    NR5G Cell ID:    D15 (3349)
    NR5G band:       n78       		NR5G Carrier ID: 0
    NR5G dl bw:      100 MHz   		NR5G ul bw:      100 MHz   
    NR5G Tx Power:   ---        		NR5G Tx chan:    0
    NR5G Rx chan:    622260
    NR5G dl MIMO:    4         		NR5G ul MIMO:    1
    NR5G(sub6) Rx0 RSSI (dBm):   -51.8	NR5G(sub6) Rx1 RSSI (dBm):   -51.3
    NR5G(sub6) Rx2 RSSI (dBm):   ---  	NR5G(sub6) Rx3 RSSI (dBm):   ---	
    
    NR5G RSRP (dBm): -114			NR5G RSRQ (dB):  -25
    NR5G SINR (dB):  23.0
    
    
    OK
    
    at!selrat?
    !SELRAT: 00, Automatic
    
    
    OK
    at!band?
    Index, Name
    00, All bands,
    0 - GW:    100200000EC00000
    1 - LTE:   0000A7E2BB0F38DF 0000000000000042
    3 - NRNSA: 000081A03B0A38D7 0000000000007C62
    4 - NRSA:  000081A03B0A38D7 0000000000007C62
    
    OK
    at!sdpref?
    RATs : WCDMA,LTE,NR5G
    GWC  : B1,B2,B4,B5,B6,B8,B19
    LTE  : B1,B2,B3,B4,B5,B7,B8,B12,B13,B14,B17,B18,B19,B20,B25,B26,B28,B29,B30,B32,B34,B38,B39,B40,B41,B42,B43,B46,B48,B66,B71
    TDS  : 
    NRSA : n1,n2,n3,n5,n7,n8,n12,n13,n14,n18,n20,n25,n26,n28,n29,n30,n38,n40,n41,n48,n66,n70,n71,n75,n76,n77,n78,n79
    NRNSA: n1,n2,n3,n5,n7,n8,n12,n13,n14,n18,n20,n25,n26,n28,n29,n30,n38,n40,n41,n48,n66,n70,n71,n75,n76,n77,n78,n79
    
    OK
    
    Cellular Modems

  • Unbricking
    S spiff

    @tom Ah, I do see this! Maybe there was a cable issue:

    Bus 001 Device 034: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)
    

    This is with the switch ON, though I'm still getting the provisioning error.

    Sentinel

  • Unbricking
    S spiff

    @tom I've tried a few cables, all USB-C to USB-A, but I'm getting the same provisioning error. Does the QDL tool have any other logs I can look at to determine the issue?

    Sentinel

  • Unbricking
    S spiff

    I'm running Ubuntu natively on my laptop. I've tried a couple different USB cables, but I will try another. The drone is powered by the AC adapter.

    Sentinel

  • Unbricking
    S spiff

    I received a new Sentinel drone but haven't been able to connect from my (Ubuntu 24) machine via adb, and lsusb also doesn't show the device. Per the unbricking guide I opened the flight lid, flipped SW2, and attempted to use the QDL tool to flash the device, but I'm getting an error on the first "Provision" step -- the frontend throws this error:

    Provisioning UFS...
    Failed to provision UFS
    

    and the terminal shows:

    [12/Nov/2024 19:30:07] "GET /get-flat-builds/ HTTP/1.1" 200 28
    Internal Server Error: /provision-ufs/
    [12/Nov/2024 19:30:08] "POST /provision-ufs/ HTTP/1.1" 500 39
    
    Sentinel
  • Login

  • Don't have an account? Register

  • Login or register to search.
  • First post
    Last post
0
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups