<
From version < 83.1 >
edited by Edwin Chen
on 2023/05/05 08:17
To version < 84.1 >
edited by Edwin Chen
on 2023/05/05 08:21
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -492,8 +492,6 @@
492 492  * System Keep Alive data. ( To ensure the system is more robust, can be disabled)
493 493  * Auto update ( Software auto update, can be disabled)
494 494  
495 -
496 -(% class="wikigeneratedid" %)
497 497  === 7.1.1 LoRaWAN Status push or polling data to LoRaWAN server ===
498 498  
499 499  When gateway connect to LoRaWAN server via LoRaWAN protocol, besides the sensor data uplink/downlink. gateway will still need to:
... ... @@ -510,7 +510,7 @@
510 510  
511 511  Base on 15 seconds per check, the data traffic is about 2M data traffic per day. Users can adjust **Keepalive Interval** as below.
512 512  
513 -[[image:image-20220527155229-15.png]]
511 +[[image:image-20220527155229-15.png||height="511" width="986"]]
514 514  
515 515  
516 516  === 7.1.3 Auto update ===
... ... @@ -520,6 +520,7 @@
520 520  
521 521  === 7.1.4 Filter unwanted packets ===
522 522  
521 +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.
523 523  
524 524  See [[How to filter unwanted packets>>doc:Main.Filter unwanted LoRaWAN packets.WebHome]]
525 525  
Copyright ©2010-2022 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0