Changes for page Cellular network connection details and tips
Last modified by Xiaoling on 2024/08/08 09:05
Change comment:
Uploaded new attachment "image-20231218095203-4.png", version {1}
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 4 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Xiaoling1 +XWiki.Kilight - Content
-
... ... @@ -215,7 +215,6 @@ 215 215 Once the Ethernet of the Wi-Fi network is unavailable where the gateway network will switch to a Cell network from Ethernet or Wi-Fi. 216 216 217 217 218 - 219 219 **Enable Cellular and connect Ethernet at the same time** 220 220 221 221 ETH icon is displayed as [[image:1658135519305-444.png||height="18" width="19"]] Indicates that Ethernet is the main working network. ... ... @@ -483,43 +483,60 @@ 483 483 484 484 = 7. How to reduce data traffic = 485 485 486 -== 7.1 ReduceStatusUplinkInterval==485 +== 7.1 How the gateway will consume data traffic == 487 487 487 +Below list the place where the data traffic will use. 488 488 489 -**The gateways will use the data traffic below two places.** 489 +* Valid uplink data to LoRaWAN server or IoT server. ( We can't reduce this as they are the data we want) 490 +* Invalid uplink sensor data to LoRaWAN serevr. ( See Filter unwanted packets) 491 +* LoRaWAN Status push or polling data to LoRaWAN server . ( We can reduce this part , see below for discussion) 492 +* System Keep Alive data. ( To ensure the system is more robust, can be disabled) 493 +* system Time synchronization Checking 494 +* Auto update ( Software auto update, can be disabled) 490 490 496 +=== 7.1.1 LoRaWAN Status push or polling data to LoRaWAN server === 491 491 492 - ~1. ThereisthedatatrafficfromLoRapackageForwardwhichwerethegatewaystatuspackageandsensorendnodeuplink/downlink.498 +When gateway connect to LoRaWAN server via LoRaWAN protocol, besides the sensor data uplink/downlink. gateway will still need to: 493 493 494 -For this case, by default, the gateway will uplink self-status to the LoRaWAN server per the 30s. the users can adjust the interval time. 500 +* Uplink self-status to the LoRaWAN server every 30s. the users can adjust **Keep Alive Period** as below 501 +* 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. 495 495 496 496 [[image:image-20220527155108-13.png]] 497 497 498 498 506 +=== 7.1.2 System Keep Alive data === 499 499 500 - 2.There is thedatatrafficfromthe gatewaycheck self-network status.bydefault,thegateway will checkthenetworkper15s.508 +System Keep Alive Data is used to check gateway-network status and fix possible issue. Gateway will check every 15 seconds and generate traffic. 501 501 502 - Forthiscase,We havemonitored theloss ofdata traffic,which is theloss of2M data traffic per day.the users can adjustthetimefollowing screenshots.510 +Base on 15 seconds per check, the data traffic is about 2M data traffic per day. Users can adjust **Keepalive Interval** as below. 503 503 504 -[[image:image-20220527155 358-16.png]]512 +[[image:image-20220527155229-15.png||height="511" width="986"]] 505 505 506 -System General interface 507 507 515 +=== 7.1.3 Auto update === 508 508 509 - [[image:image-20220527155229-15.png]]517 +Gateway will check for update every day for new configure or software. User can disable them by below method. 510 510 511 -Keepalive script interval time settings 512 512 520 +=== 7.1.4 Filter unwanted packets === 513 513 514 - ==7.2Filterunwantedpackets==522 +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. 515 515 516 - 517 517 See [[How to filter unwanted packets>>doc:Main.Filter unwanted LoRaWAN packets.WebHome]] 518 518 519 519 520 -== 7. 3Usage statistics ==527 +== 7.2 Usage statistics == 521 521 522 522 530 +=== 7.2.1 How does Openwrt usage statistics === 531 + 532 +This is a general instruction for the use of Openwrt of Dragino devices. Current models include: 533 + 534 +* LPS8,LPS8N 535 +* LG308,LG308N 536 +* DLOS8,DLOS8N 537 +* LIG16 538 + 523 523 ~1. Activate LuCI and connect to SSH following [[these instructions>>doc:Main.Install Luci in the new UI firmware.WebHome]] 524 524 525 525 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