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 (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Kilight1 +XWiki.Edwin - 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 ... ... @@ -510,6 +510,7 @@ 510 510 511 511 === 7.1.1 LoRaWAN Status push or polling data to LoRaWAN server === 512 512 510 + 513 513 When gateway connect to LoRaWAN server via LoRaWAN protocol, besides the sensor data uplink/downlink. gateway will still need to: 514 514 515 515 * Uplink self-status to the LoRaWAN server every 30s. the users can adjust **Keep Alive Period** as below ... ... @@ -520,6 +520,7 @@ 520 520 521 521 === 7.1.2 System Keep Alive data === 522 522 521 + 523 523 System Keep Alive Data is used to check gateway-network status and fix possible issue. Gateway will check every 15 seconds and generate traffic. 524 524 525 525 Base on 15 seconds per check, the data traffic is about 2M data traffic per day. Users can adjust **Keepalive Interval** as below. ... ... @@ -529,11 +529,13 @@ 529 529 530 530 === 7.1.3 Auto update === 531 531 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 535 === 7.1.4 Filter unwanted packets === 536 536 537 + 537 537 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. 538 538 539 539 See [[How to filter unwanted packets>>doc:Main.Filter unwanted LoRaWAN packets.WebHome]] ... ... @@ -541,9 +541,9 @@ 541 541 542 542 == 7.2 Usage statistics == 543 543 544 - 545 545 === 7.2.1 How does Openwrt usage statistics === 546 546 547 + 547 547 This is a general instruction for the use of Openwrt of Dragino devices. Current models include: 548 548 549 549 * LPS8,LPS8N