Changes for page Cellular network connection details and tips
Last modified by Kilight Cao on 2024/12/31 16:38
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 6 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -55,6 +55,7 @@ 55 55 56 56 (% class="box" %) 57 57 ((( 58 +(% class="mark" %)**For Models: LPS8N, LG308N, DLOS8N**(%%) 58 58 //root@dragino-1dadd8:~~# **comgt -d /dev/ttyUSB3** 59 59 SIM ready 60 60 Waiting for Registration..(120 sec max) ... ... @@ -132,7 +132,6 @@ 132 132 133 133 Regarding what APN your SIM card should use, Users can search for the APN corresponding to the SIM card by Google or ask the carrier. 134 134 135 - 136 136 [[image:image-20220718155937-1.png||height="562" width="497"]] 137 137 138 138 ... ... @@ -141,7 +141,6 @@ 141 141 142 142 It should be SIM card no flow, users can insert SIM cards into the mobile phone for testing. 143 143 144 - 145 145 [[image:1658131428288-728.png||height="538" width="494"]] 146 146 147 147 ... ... @@ -150,7 +150,6 @@ 150 150 151 151 Users need to check whether the SIM card type is suitable for the EC25 module. 152 152 153 - 154 154 [[image:1658131612484-845.png||height="549" width="499"]] 155 155 156 156 ... ... @@ -159,7 +159,6 @@ 159 159 160 160 Users can insert SIM cards into the mobile phone for testing. 161 161 162 - 163 163 [[image:image-20220718160804-3.png||height="602" width="500"]] 164 164 165 165 ... ... @@ -265,23 +265,38 @@ 265 265 266 266 = 5. How does the gateway view the International Mobile Equipment Identity (IMEI) = 267 267 265 +== For LIG16,LPS8, LPS8N, LG308, LG308N, DLOS8, DLOS8N view the International Mobile Equipment Identity (IMEI) == 268 268 267 + 269 269 Users can get the IMEI via Linux command, but you have to access the gateway CLI. 270 270 271 271 (% class="box infomessage" %) 272 272 ((( 273 -**root@dragino- 1b7c4c:~~# comgt -d /dev/ttyModemAT -s /etc/gcom/getimsi.gcom **272 +**root@dragino-24b3c8:~~# comgt -d /dev/ttyModemAT -s /etc/gcom/getimei.gcom ** 274 274 ))) 275 275 276 -[[image:image-2022102 7140604-1.png||height="330" width="707"]]275 +[[image:image-20231218095203-4.png]] 277 277 278 278 279 -[[image:image-202 21027151146-2.png||height="554" width="1000"]]278 +[[image:image-20231218095426-6.jpeg||height="466" width="990"]] 280 280 281 281 282 -== **HowdoesthegatewayaccesstheQuetelmoduledirectly(tosend AT commands)**==281 +== For LPS8v2 view the International Mobile Equipment Identity (IMEI) == 283 283 283 +(% class="box infomessage" %) 284 +((( 285 +**root@dragino-e4e891:~~# /usr/local/dragino/cell/getinfo.sh** 286 +))) 284 284 288 +[[image:image-20231218094526-1.png]] 289 + 290 + 291 +[[image:image-20231218094741-3.png]] 292 + 293 + 294 +== How does the gateway access the Quetel module directly (to send AT commands) == 295 + 296 + 285 285 Users can access the gateway CLI and run the minicom command to get the configuration interface. 286 286 287 287 ((( ... ... @@ -313,7 +313,7 @@ 313 313 [[image:image-20220527154154-7.png]] 314 314 315 315 316 -== =**International Mobile Equipment Identity (IMEI)**===328 +== International Mobile Equipment Identity (IMEI) == 317 317 318 318 319 319 ((( ... ... @@ -334,7 +334,7 @@ 334 334 [[image:image-20220527154231-8.png]] 335 335 336 336 337 -== =**Integrated Circuit Card Identifier (ICCID)**===349 +== Integrated Circuit Card Identifier (ICCID) == 338 338 339 339 340 340 ((( ... ... @@ -482,43 +482,64 @@ 482 482 483 483 = 7. How to reduce data traffic = 484 484 485 -== 7.1 ReduceStatusUplinkInterval==497 +== 7.1 How the gateway will consume data traffic == 486 486 499 +Below list the place where the data traffic will use. 487 487 488 -**The gateways will use the data traffic below two places.** 501 +* Valid uplink data to LoRaWAN server or IoT server. ( We can't reduce this as they are the data we want) 502 +* Invalid uplink sensor data to LoRaWAN serevr. ( See Filter unwanted packets) 503 +* LoRaWAN Status push or polling data to LoRaWAN server . ( We can reduce this part , see below for discussion) 504 +* System Keep Alive data. ( To ensure the system is more robust, can be disabled) 505 +* system Time synchronization Checking 506 +* Auto update ( Software auto update, can be disabled) 489 489 508 +=== 7.1.1 LoRaWAN Status push or polling data to LoRaWAN server === 490 490 491 -~1. There is the data traffic from LoRa package Forward which were the gateway status package and sensor end node uplink/downlink. 492 492 493 - For this case,by default, thegatewaywill uplink self-statustotheLoRaWAN server perhe30s.theuserscan adjusttheinterval time.511 +When gateway connect to LoRaWAN server via LoRaWAN protocol, besides the sensor data uplink/downlink. gateway will still need to: 494 494 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. 515 + 495 495 [[image:image-20220527155108-13.png]] 496 496 497 497 519 +=== 7.1.2 System Keep Alive data === 498 498 499 -2. There is the data traffic from the gateway check self-network status. by default, the gateway will check the network per 15s. 500 500 501 - For thiscase,Wehavemonitoredtheloss ofdatafic,whichistheloss of 2M datatrafficperday.theuserscan adjusttheintervaltime following screenshots.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. 502 502 503 - [[image:image-20220527155358-16.png]]524 +Base on 15 seconds per check, the data traffic is about 2M data traffic per day. Users can adjust **Keepalive Interval** as below. 504 504 505 - SystemGeneralinterface526 +[[image:image-20220527155229-15.png||height="511" width="986"]] 506 506 507 507 508 - [[image:image-20220527155229-15.png]]529 +=== 7.1.3 Auto update === 509 509 510 -Keepalive script interval time settings 511 511 532 +Gateway will check for update every day for new configure or software. User can disable them by below method. 512 512 513 -== 7.2 Filter unwanted packets == 514 514 535 +=== 7.1.4 Filter unwanted packets === 515 515 537 + 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. 539 + 516 516 See [[How to filter unwanted packets>>doc:Main.Filter unwanted LoRaWAN packets.WebHome]] 517 517 518 518 519 -== 7. 3Usage statistics ==543 +== 7.2 Usage statistics == 520 520 545 +=== 7.2.1 How does Openwrt usage statistics === 521 521 547 + 548 +This is a general instruction for the use of Openwrt of Dragino devices. Current models include: 549 + 550 +* LPS8,LPS8N 551 +* LG308,LG308N 552 +* DLOS8,DLOS8N 553 +* LIG16 554 + 522 522 ~1. Activate LuCI and connect to SSH following [[these instructions>>doc:Main.Install Luci in the new UI firmware.WebHome]] 523 523 524 524 2. Install luci-app-statistics using the following terminal commands:
- image-20231218094526-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Kilight - Size
-
... ... @@ -1,0 +1,1 @@ 1 +23.3 KB - Content
- image-20231218094728-2.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Kilight - Size
-
... ... @@ -1,0 +1,1 @@ 1 +38.2 KB - Content
- image-20231218094741-3.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Kilight - Size
-
... ... @@ -1,0 +1,1 @@ 1 +47.5 KB - Content
- image-20231218095203-4.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Kilight - Size
-
... ... @@ -1,0 +1,1 @@ 1 +18.5 KB - Content
- image-20231218095257-5.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Kilight - Size
-
... ... @@ -1,0 +1,1 @@ 1 +73.0 KB - Content
- image-20231218095426-6.jpeg
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Kilight - Size
-
... ... @@ -1,0 +1,1 @@ 1 +53.7 KB - Content