Changes for page Cellular network connection details and tips
Last modified by Kilight Cao on 2024/12/31 16:38
Change comment:
Uploaded new attachment "Reduced_data_consumption.tar.gz", version {1}
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -28,9 +28,8 @@ 28 28 29 29 If there is a problem with the cellular connection. Please check the below points: 30 30 31 -== 2.1 For LPS8N/DLOS8N/LG308N == 32 32 33 -== =2.1.1Do you order the model with a cellular option ===32 +== 2.1 Do you order the model with a cellular option == 34 34 35 35 36 36 Make sure you order the model with the cellular option. Can check by command or via the Web UI. ... ... @@ -46,7 +46,7 @@ 46 46 [[image:image-20220601110748-1.png]] 47 47 48 48 49 -== =2.1.2 Do you input the SIM card correctly ===48 +== 2.2 Do you input the SIM card correctly == 50 50 51 51 52 52 **Below command can check if you have a SIM card inserted, or via Web UI** ... ... @@ -79,7 +79,7 @@ 79 79 [[image:image-20220527153827-5.png]] 80 80 81 81 82 -== =2.1.3 Check dialing info ===81 +== 2.3 Check dialing info == 83 83 84 84 85 85 run "**logread -f**" in gateway CLI。 ... ... @@ -506,21 +506,34 @@ 506 506 * system Time synchronization Checking 507 507 * Auto update ( Software auto update, can be disabled) 508 508 509 -=== 7.1.1 Uploadingbackupfilestoeduceddataconsumption===508 +=== 7.1.1 LoRaWAN Status push or polling data to LoRaWAN server === 510 510 511 511 512 - Users canuploadthis backupfile toreduce dataconsumptionin **System~-~->BackUp/RestoreConfig**,Downloadlink forbackupfile: **[[attach:Reduced_data_consumption.tar.gz||target="_blank"]]**511 +When gateway connect to LoRaWAN server via LoRaWAN protocol, besides the sensor data uplink/downlink. gateway will still need to: 513 513 514 -[[image:image-20240712093532-1.png]] 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 515 516 +[[image:image-20220527155108-13.png]] 516 516 517 -=== 7.1.2 Auto update === 518 518 519 +=== 7.1.2 System Keep Alive data === 519 519 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 + 520 520 Gateway will check for update every day for new configure or software. User can disable them by below method. 521 521 522 522 523 -=== 7.1. 3Filter unwanted packets ===535 +=== 7.1.4 Filter unwanted packets === 524 524 525 525 526 526 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.