Summary

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

Details

Page properties

Content

...	...	@@ -1,11 +1,11 @@
1		-**Table of Contents:**
	1	+
2	2
	3	+**Table of Contents：**
	4	+
3	3	{{toc/}}
4	4
5	5
6	6
7		-
8		-
9	9	= 1. Enable Cellular Connection =
10	10
11	11
...	...	@@ -29,11 +29,9 @@
29	29	If there is a problem with the cellular connection. Please check the below points:
30	30
31	31
32		-== 2.1 For LPS8N/DLOS8N/LG308N ==
	32	+== 2.1 Do you order the model with a cellular option ==
33	33
34		-=== 2.1.1 Do you order the model with a cellular option ===
35	35
36		-
37	37	Make sure you order the model with the cellular option. Can check by command or via the Web UI.
38	38
39	39	(% class="box" %)
...	...	@@ -47,7 +47,7 @@
47	47	[[image:image-20220601110748-1.png]]
48	48
49	49
50		-=== 2.1.2 Do you input the SIM card correctly ===
	48	+== 2.2 Do you input the SIM card correctly ==
51	51
52	52
53	53	**Below command can check if you have a SIM card inserted, or via Web UI**
...	...	@@ -80,7 +80,7 @@
80	80	[[image:image-20220527153827-5.png]]
81	81
82	82
83		-=== 2.1.3 Check dialing info ===
	81	+== 2.3 Check dialing info ==
84	84
85	85
86	86	run "**logread -f**" in gateway CLI。
...	...	@@ -264,7 +264,7 @@
264	264
265	265	= 5. How does the gateway view the International Mobile Equipment Identity (IMEI) =
266	266
267		-== For LIG16,LPS8, LPS8N, LG308, LG308N, DLOS8, DLOS8N view the International Mobile Equipment Identity (IMEI) ==
	265	+=== For LIG16,LPS8, LPS8N, LG308, LG308N, DLOS8, DLOS8N view the International Mobile Equipment Identity (IMEI) ===
268	268
269	269
270	270	Users can get the IMEI via Linux command, but you have to access the gateway CLI.
...	...	@@ -280,7 +280,7 @@
280	280	[[image:image-20231218095426-6.jpeg||height="466" width="990"]]
281	281
282	282
283		-== For LPS8v2 view the International Mobile Equipment Identity (IMEI) ==
	281	+=== For LPS8v2 view the International Mobile Equipment Identity (IMEI) ===
284	284
285	285	(% class="box infomessage" %)
286	286	(((
...	...	@@ -293,7 +293,7 @@
293	293	[[image:image-20231218094741-3.png]]
294	294
295	295
296		-== How does the gateway access the Quetel module directly (to send AT commands) ==
	294	+=== How does the gateway access the Quetel module directly (to send AT commands) ===
297	297
298	298
299	299	Users can access the gateway CLI and run the minicom command to get the configuration interface.
...	...	@@ -327,7 +327,7 @@
327	327	[[image:image-20220527154154-7.png]]
328	328
329	329
330		-== International Mobile Equipment Identity (IMEI) ==
	328	+=== International Mobile Equipment Identity (IMEI) ===
331	331
332	332
333	333	(((
...	...	@@ -348,7 +348,7 @@
348	348	[[image:image-20220527154231-8.png]]
349	349
350	350
351		-== Integrated Circuit Card Identifier (ICCID) ==
	349	+=== Integrated Circuit Card Identifier (ICCID) ===
352	352
353	353
354	354	(((
...	...	@@ -498,7 +498,6 @@
498	498
499	499	== 7.1 How the gateway will consume data traffic ==
500	500
501		-
502	502	Below list the place where the data traffic will use.
503	503
504	504	* Valid uplink data to LoRaWAN server or IoT server. ( We can't reduce this as they are the data we want)
...	...	@@ -508,23 +508,34 @@
508	508	* system Time synchronization Checking
509	509	* Auto update ( Software auto update, can be disabled)
510	510
	508	+=== 7.1.1 LoRaWAN Status push or polling data to LoRaWAN server ===
511	511
512	512
513		-=== 7.1.1 Uploading backup files to reduced data consumption ===
	511	+When gateway connect to LoRaWAN server via LoRaWAN protocol, besides the sensor data uplink/downlink. gateway will still need to:
514	514
	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		-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"]]**
	516	+[[image:image-20220527155108-13.png]]
517	517
518		-[[image:image-20240712093532-1.png]]
519	519
	519	+=== 7.1.2 System Keep Alive data ===
520	520
521		-=== 7.1.2 Auto update ===
522	522
	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	+
524	524	Gateway will check for update every day for new configure or software. User can disable them by below method.
525	525
526	526
527		-=== 7.1.3 Filter unwanted packets ===
	535	+=== 7.1.4 Filter unwanted packets ===
528	528
529	529
530	530	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,1 +1,0 @@
1		-XWiki.Kilight

Size

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

Content

image-20240712093532-1.png

Author

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

Size

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

Content