Summary

• Page properties (2 modified, 0 added, 0 removed)
• Attachments (0 modified, 2 added, 0 removed)
  • Reduced_data_consumption.tar.gz
  • image-20240712093532-1.png

Details

Page properties

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.Edwin
	1	+XWiki.Xiaoling

Content

...	...	@@ -1,11 +1,11 @@
1		-
	1	+**Table of Contents:**
2	2
3		-**Table of Contents：**
4		-
5	5	{{toc/}}
6	6
7	7
8	8
	7	+
	8	+
9	9	= 1. Enable Cellular Connection =
10	10
11	11
...	...	@@ -29,9 +29,11 @@
29	29	If there is a problem with the cellular connection. Please check the below points:
30	30
31	31
32		-== 2.1 Do you order the model with a cellular option ==
	32	+== 2.1 For LPS8N/DLOS8N/LG308N ==
33	33
	34	+=== 2.1.1 Do you order the model with a cellular option ===
34	34
	36	+
35	35	Make sure you order the model with the cellular option. Can check by command or via the Web UI.
36	36
37	37	(% class="box" %)
...	...	@@ -45,7 +45,7 @@
45	45	[[image:image-20220601110748-1.png]]
46	46
47	47
48		-== 2.2 Do you input the SIM card correctly ==
	50	+=== 2.1.2 Do you input the SIM card correctly ===
49	49
50	50
51	51	**Below command can check if you have a SIM card inserted, or via Web UI**
...	...	@@ -78,7 +78,7 @@
78	78	[[image:image-20220527153827-5.png]]
79	79
80	80
81		-== 2.3 Check dialing info ==
	83	+=== 2.1.3 Check dialing info ===
82	82
83	83
84	84	run "**logread -f**" in gateway CLI。
...	...	@@ -262,7 +262,7 @@
262	262
263	263	= 5. How does the gateway view the International Mobile Equipment Identity (IMEI) =
264	264
265		-=== For LIG16,LPS8, LPS8N, LG308, LG308N, DLOS8, DLOS8N view the International Mobile Equipment Identity (IMEI) ===
	267	+== For LIG16,LPS8, LPS8N, LG308, LG308N, DLOS8, DLOS8N view the International Mobile Equipment Identity (IMEI) ==
266	266
267	267
268	268	Users can get the IMEI via Linux command, but you have to access the gateway CLI.
...	...	@@ -278,7 +278,7 @@
278	278	[[image:image-20231218095426-6.jpeg||height="466" width="990"]]
279	279
280	280
281		-=== For LPS8v2 view the International Mobile Equipment Identity (IMEI) ===
	283	+== For LPS8v2 view the International Mobile Equipment Identity (IMEI) ==
282	282
283	283	(% class="box infomessage" %)
284	284	(((
...	...	@@ -291,7 +291,7 @@
291	291	[[image:image-20231218094741-3.png]]
292	292
293	293
294		-== **How does the gateway access the Quetel module directly (to send AT commands)** ==
	296	+== How does the gateway access the Quetel module directly (to send AT commands) ==
295	295
296	296
297	297	Users can access the gateway CLI and run the minicom command to get the configuration interface.
...	...	@@ -325,7 +325,7 @@
325	325	[[image:image-20220527154154-7.png]]
326	326
327	327
328		-=== **International Mobile Equipment Identity (IMEI)** ===
	330	+== International Mobile Equipment Identity (IMEI) ==
329	329
330	330
331	331	(((
...	...	@@ -346,7 +346,7 @@
346	346	[[image:image-20220527154231-8.png]]
347	347
348	348
349		-=== **Integrated Circuit Card Identifier (ICCID)** ===
	351	+== Integrated Circuit Card Identifier (ICCID) ==
350	350
351	351
352	352	(((
...	...	@@ -496,6 +496,7 @@
496	496
497	497	== 7.1 How the gateway will consume data traffic ==
498	498
	501	+
499	499	Below list the place where the data traffic will use.
500	500
501	501	* Valid uplink data to LoRaWAN server or IoT server. ( We can't reduce this as they are the data we want)
...	...	@@ -505,34 +505,23 @@
505	505	* system Time synchronization Checking
506	506	* Auto update ( Software auto update, can be disabled)
507	507
508		-=== 7.1.1 LoRaWAN Status push or polling data to LoRaWAN server ===
509	509
510	510
511		-When gateway connect to LoRaWAN server via LoRaWAN protocol, besides the sensor data uplink/downlink. gateway will still need to:
	513	+=== 7.1.1 Uploading backup files to reduced data consumption ===
512	512
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	+Users can upload this backup file to reduce data consumption in **System~-~->Back Up/Restore Config**, Download link for backup file: **[[attach:Reduced_data_consumption.tar.gz||target="_blank"]]**
517	517
	518	+[[image:image-20240712093532-1.png]]
518	518
519		-=== 7.1.2 System Keep Alive data ===
520	520
	521	+=== 7.1.2 Auto update ===
521	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	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		-
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		-=== 7.1.4 Filter unwanted packets ===
	527	+=== 7.1.3 Filter unwanted packets ===
536	536
537	537
538	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.

Reduced_data_consumption.tar.gz

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Kilight

Size

...	...	@@ -1,0 +1,1 @@
	1	+10.4 KB

Content

image-20240712093532-1.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Kilight

Size

...	...	@@ -1,0 +1,1 @@
	1	+145.5 KB

Content