Changes for page Cellular network connection details and tips
Last modified by Kilight Cao on 2024/12/31 16:38
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 2 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -1,11 +1,11 @@ 1 - 1 +**Table of Contents:** 2 2 3 -**Table of Contents:** 4 - 5 5 {{toc/}} 6 6 7 7 8 8 7 + 8 + 9 9 = 1. Enable Cellular Connection = 10 10 11 11 ... ... @@ -29,9 +29,11 @@ 29 29 If there is a problem with the cellular connection. Please check the below points: 30 30 31 31 32 -== 2.1 Doyou orderthemodel with a cellular option==32 +== 2.1 For LPS8N/DLOS8N/LG308N == 33 33 34 +=== 2.1.1 Do you order the model with a cellular option === 34 34 36 + 35 35 Make sure you order the model with the cellular option. Can check by command or via the Web UI. 36 36 37 37 (% class="box" %) ... ... @@ -45,7 +45,7 @@ 45 45 [[image:image-20220601110748-1.png]] 46 46 47 47 48 -== 2.2 Do you input the SIM card correctly == 50 +=== 2.1.2 Do you input the SIM card correctly === 49 49 50 50 51 51 **Below command can check if you have a SIM card inserted, or via Web UI** ... ... @@ -78,7 +78,7 @@ 78 78 [[image:image-20220527153827-5.png]] 79 79 80 80 81 -== 2.3 Check dialing info == 83 +=== 2.1.3 Check dialing info === 82 82 83 83 84 84 run "**logread -f**" in gateway CLI。 ... ... @@ -124,6 +124,179 @@ 124 124 ))) 125 125 126 126 129 +== 2.2 For LPS8v2/MS48-LR == 130 + 131 +=== (% id="cke_bm_23549S" style="display:none" %) (%%)2.2.1 Do you order the model with a cellular option === 132 + 133 + 134 +Make sure you order the model with the cellular option. Can check by command or via the Web UI. 135 + 136 +(% class="box" %) 137 +((( 138 +//root@dragino-2d5d26:~~# lsusb 139 +Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub 140 +Bus 004 Device 002: ID 2c7c:0125 Quectel Wireless Solutions Co., Ltd. EC25 LTE modem ~-~-> This is the Cellular module 141 +Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub 142 +Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub 143 +Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub 144 +Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub 145 +Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub 146 +Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub 147 +Bus 001 Device 002: ID 0bda:f179 Realtek Semiconductor Corp. RTL8188FTV 802.11b/g/n 1T1R 2.4G WLAN Adapter 148 +Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub 149 +Bus 009 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub 150 +root@dragino-2d5d26:~~# // 151 +))) 152 + 153 +[[image:image-20241205150916-1.png]] 154 + 155 + 156 + 157 +=== 2.1.3 Check cellular info === 158 + 159 + 160 +run "**quectel-CM**" in gateway CLI 161 + 162 +(% class="box infomessage" %) 163 +((( 164 +Usage: /usr/bin/quectel-CM [options] 165 + -s [apn [user password auth]] Set apn/user/password/auth get from your network provider. auth: 1~~pap, 2~~chap 166 + -p pincode Verify sim card pin if sim card is locked 167 + -p [quectel-][qmi|mbim]-proxy Request to use proxy 168 + -f logfilename Save log message of this program to file 169 + -u usbmonlog filename Save usbmon log to file 170 + -i interface Specify which network interface to setup data call when multi-modems exits 171 + -4 Setup IPv4 data call (default) 172 + -6 Setup IPv6 data call 173 + -k pdn Specify which pdn to hangup data call (by send SIGINT to 'quectel-CM -n pdn') 174 + -m iface-idx Bind QMI data call to wwan0_<iface idx> when QMAP used. E.g '-n 7 -m 1' bind pdn-7 data call to wwan0_1 175 + -b Enable network interface bridge function (default 0) 176 + -v Verbose log mode, for debug purpose.[Examples] 177 +Example 1: /usr/bin/quectel-CM 178 +Example 2: /usr/bin/quectel-CM -s 3gnet 179 +Example 3: /usr/bin/quectel-CM -s 3gnet -v 180 +))) 181 + 182 + 183 +==== **The gateway cellular logs show SIMStatus: SIM_ABSENT** ==== 184 + 185 + 186 +If the SIM status is **SIM_ABSENT**, the SIM card is not detected. You need to check whether the SIM card is available and whether the device is powered off when the SIM card is installed. 187 + 188 +(% class="box" %) 189 +((( 190 +root@dragino-2d5d26:~~# quectel-CM -s 3gnet 191 +[12-05_07:12:08:451] Quectel_QConnectManager_Linux_V1.6.0.24 192 +[12-05_07:12:08:454] Find /sys/bus/usb/devices/4-1 idVendor=0x2c7c idProduct=0x125, bus=0x004, dev=0x002 193 +[12-05_07:12:08:455] Auto find qmichannel = /dev/cdc-wdm0 194 +[12-05_07:12:08:455] Auto find usbnet_adapter = wwan0 195 +[12-05_07:12:08:455] netcard driver = qmi_wwan, driver version = 5.15.43-draginohp0z 196 +[12-05_07:12:08:456] Modem works in QMI mode 197 +[12-05_07:12:08:516] cdc_wdm_fd = 7 198 +[12-05_07:12:08:613] Get clientWDS = 21 199 +[12-05_07:12:08:645] Get clientDMS = 1 200 +[12-05_07:12:08:676] Get clientNAS = 4 201 +[12-05_07:12:08:709] Get clientUIM = 2 202 +[12-05_07:12:08:741] Get clientWDA = 1 203 +[12-05_07:12:08:774] requestBaseBandVersion EC25EFAR06A16M4G 204 +[12-05_07:12:08:902] (% style="color:#037691" %)**requestGetSIMStatus SIMStatus: SIM_ABSENT ~-~-~-~--> This means that the SIM cannot be read**(%%) 205 +[12-05_07:12:08:902] requestSetProfile[1] 3gnet~/~//0 206 +[12-05_07:12:08:965] requestGetProfile[1] 3gnet~/~//0 207 +[12-05_07:12:08:997] requestRegistrationState2 MCC: 0, MNC: 0, PS: Detached, DataCap: UNKNOW 208 +[12-05_07:12:09:030] requestQueryDataCall IPv4ConnectionStatus: DISCONNECTED 209 +[12-05_07:12:09:030] ifconfig wwan0 0.0.0.0 210 +[12-05_07:12:09:043] ifconfig wwan0 down 211 +^C[12-05_07:12:18:311] QmiWwanThread exit 212 +[12-05_07:12:18:313] qmi_main exit 213 +))) 214 + 215 + 216 +==== **The gateway cellular logs show SIMStatus: SIM_PIN** ==== 217 + 218 + 219 +If the SIM status is **SIM_PIN**, it means that the SIM card is read but the Pincode needs to be filled in. 220 + 221 +(% class="box" %) 222 +((( 223 +root@dragino-2d5d26:~~# quectel-CM -s 3gnet 224 + 225 +[10-31_12:17:10:166] Find /sys/bus/usb/devices/2-1 idVendor=0x2c7c idProduct=0x125, bus=0x002, dev=0x002 226 +[10-31_12:17:10:168] Auto find qmichannel = /dev/cdc-wdm0 227 +[10-31_12:17:10:168] Auto find usbnet_adapter = wwan0 228 +[10-31_12:17:10:168] netcard driver = qmi_wwan, driver version = 5.15.43-draginohp0z 229 +[10-31_12:17:10:170] Modem works in QMI mode 230 +[10-31_12:17:10:234] cdc_wdm_fd = 8 231 +[10-31_12:17:10:325] Get clientWDS = 21 232 +[10-31_12:17:10:356] Get clientDMS = 1 233 +[10-31_12:17:10:389] Get clientNAS = 4 234 +[10-31_12:17:10:449] Get clientUIM = 2 235 +[10-31_12:17:10:489] Get clientWDA = 1 236 +[10-31_12:17:10:518] requestBaseBandVersion EC25EFAR06A16M4G 237 +[10-31_12:17:10:645] (% style="color:#037691" %)**requestGetSIMStatus SIMStatus: SIM_PIN ~-~-~-~--> This means you need to fill in the Pincode**(%%) 238 +[10-31_12:17:10:645] requestSetProfile[1] Telekom~/~//0 239 +[10-31_12:17:10:713] requestGetProfile[1] Telekom~/~//0 240 +[10-31_12:17:10:743] requestRegistrationState2 MCC: 262, MNC: 2, PS: Detached, DataCap: UNKNOW 241 +[10-31_12:17:10:773] requestQueryDataCall IPv4ConnectionStatus: DISCONNECTED 242 +[10-31_12:17:10:774] ifconfig wwan0 0.0.0.0 243 +[10-31_12:17:10:790] ifconfig wwan0 down 244 +[10-31_18:27:35:797] QmiWwanThread exit 245 +[10-31_18:27:35:798] qmi_main exit 246 +))) 247 + 248 + 249 +==== **The gateway cellular logs show SIMStatus: SIM_READY** ==== 250 + 251 + 252 +If the SIM status is **SIM_READY**,** ** it means that the SIM card is detected 253 + 254 +(% class="box" %) 255 +((( 256 +root@dragino-2d5d26:~~# quectel-CM 257 +[12-05_07:32:57:187] Quectel_QConnectManager_Linux_V1.6.0.24 258 +[12-05_07:32:57:191] Find /sys/bus/usb/devices/4-1 idVendor=0x2c7c idProduct=0x125, bus=0x004, dev=0x002 259 +[12-05_07:32:57:192] Auto find qmichannel = /dev/cdc-wdm0 260 +[12-05_07:32:57:193] Auto find usbnet_adapter = wwan0 261 +[12-05_07:32:57:198] netcard driver = qmi_wwan, driver version = 5.15.43-draginohp0z 262 +[12-05_07:32:57:199] Modem works in QMI mode 263 +[12-05_07:32:57:261] cdc_wdm_fd = 7 264 +[12-05_07:32:57:334] Get clientWDS = 20 265 +[12-05_07:32:57:366] Get clientDMS = 1 266 +[12-05_07:32:57:398] Get clientNAS = 4 267 +[12-05_07:32:57:431] Get clientUIM = 1 268 +[12-05_07:32:57:462] Get clientWDA = 1 269 +[12-05_07:32:57:495] requestBaseBandVersion EC25EFAR06A16M4G 270 +[12-05_07:32:57:623] (% style="color:#037691" %)**requestGetSIMStatus SIMStatus: SIM_READY**(%%) 271 +[12-05_07:32:57:655] requestGetProfile[1] 3gnet~/~//0 272 +[12-05_07:32:57:687] requestRegistrationState2 MCC: 460, MNC: 15, PS: Detached, DataCap: UNKNOW 273 +[12-05_07:32:57:719] requestQueryDataCall IPv4ConnectionStatus: DISCONNECTED 274 +[12-05_07:32:57:719] ifconfig wwan0 0.0.0.0 275 +[12-05_07:32:57:731] ifconfig wwan0 down 276 +[12-05_07:33:00:727] requestRegistrationState2 MCC: 0, MNC: 0, PS: Detached, DataCap: UNKNOW 277 +[12-05_07:33:15:895] requestRegistrationState2 MCC: 460, MNC: 0, PS: Detached, DataCap: UNKNOW 278 +[12-05_07:33:19:063] requestRegistrationState2 MCC: 460, MNC: 0, PS: Detached, DataCap: EDGE 279 +[12-05_07:33:19:095] requestRegistrationState2 MCC: 460, MNC: 0, PS: Detached, DataCap: EDGE 280 +[12-05_07:33:21:463] requestRegistrationState2 MCC: 460, MNC: 0, PS: Attached, DataCap: EDGE 281 +[12-05_07:33:22:359] requestSetupDataCall WdsConnectionIPv4Handle: 0x8728b3d0 282 +[12-05_07:33:22:488] ifconfig wwan0 up 283 +[12-05_07:33:22:504] busybox udhcpc -f -n -q -t 5 -i wwan0 284 +udhcpc: started, v1.30.1 285 +udhcpc: sending discover 286 +udhcpc: sending discover 287 +udhcpc: sending discover 288 +udhcpc: sending discover 289 +udhcpc: sending discover 290 +udhcpc: no lease, failing 291 +[12-05_07:33:38:103] File:ql_raw_ip_mode_check Line:136 udhcpc fail to get ip address, try next: 292 +[12-05_07:33:38:103] ifconfig wwan0 down 293 +[12-05_07:33:38:116] echo Y > /sys/class/net/wwan0/qmi/raw_ip 294 +[12-05_07:33:38:117] ifconfig wwan0 up 295 +[12-05_07:33:38:130] busybox udhcpc -f -n -q -t 5 -i wwan0 296 +udhcpc: started, v1.30.1 297 +udhcpc: sending discover 298 +udhcpc: sending select for 10.171.60.177 299 +udhcpc: lease of 10.171.60.177 obtained, lease time 7200 300 +))) 301 + 127 127 == 2.4 If the following situation occurs, how can users solve this problem? == 128 128 129 129 === 2.4.1 The gateway can read the SIM card, But the Internet is displayed as Fail. === ... ... @@ -496,6 +496,7 @@ 496 496 497 497 == 7.1 How the gateway will consume data traffic == 498 498 674 + 499 499 Below list the place where the data traffic will use. 500 500 501 501 * Valid uplink data to LoRaWAN server or IoT server. ( We can't reduce this as they are the data we want) ... ... @@ -505,34 +505,21 @@ 505 505 * system Time synchronization Checking 506 506 * Auto update ( Software auto update, can be disabled) 507 507 508 -=== 7.1.1 LoRaWANStatuspushorpollingdata toLoRaWAN server===684 +=== 7.1.1 Uploading backup files to reduced data consumption === 509 509 510 510 511 - WhengatewayconnecttoLoRaWAN serverviaLoRaWANprotocol,besidesthesensordata uplink/downlink.gatewaywill still need:687 +Users can upload this backup file to reduce data consumption in **System~-~->Back Up/Restore Config**, Download link for backup file: **[[attach:Reduced_data_consumption.tar.gz||target="_blank"]]** 512 512 513 -* Uplink self-status to the LoRaWAN server every 30s. the users can adjust **Keep Alive Period** as below 514 -* Check LoRaWAN server status every 5 seconds to see if there is valid downlink command to sensors. We don't provide WEB UI option to modify this time, because the modify of this settings will lead to fail on OTAA Join and Downlink commands. 689 +[[image:image-20240712093532-1.png]] 515 515 516 -[[image:image-20220527155108-13.png]] 517 517 692 +=== 7.1.2 Auto update === 518 518 519 -=== 7.1.2 System Keep Alive data === 520 520 521 - 522 -System Keep Alive Data is used to check gateway-network status and fix possible issue. Gateway will check every 15 seconds and generate traffic. 523 - 524 -Base on 15 seconds per check, the data traffic is about 2M data traffic per day. Users can adjust **Keepalive Interval** as below. 525 - 526 -[[image:image-20220527155229-15.png||height="511" width="986"]] 527 - 528 - 529 -=== 7.1.3 Auto update === 530 - 531 - 532 532 Gateway will check for update every day for new configure or software. User can disable them by below method. 533 533 534 534 535 -=== 7.1. 4Filter unwanted packets ===698 +=== 7.1.3 Filter unwanted packets === 536 536 537 537 538 538 When gateway connect to LoRaWAN server via LoRaWAN protocol , Gateway will by default get every possible LoRaWAN packets and forward to LoRaWAN server. If there are sensors from others in the same area, such sensor data will also be forward to LoRaWAN server ( they will be ignore by the server). This also consume data.
- Reduced_data_consumption.tar.gz
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Kilight - Size
-
... ... @@ -1,0 +1,1 @@ 1 +10.4 KB - Content
- image-20241205150916-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Kilight - Size
-
... ... @@ -1,0 +1,1 @@ 1 +37.3 KB - Content