Summary

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

Details

Page properties

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**
...	...	@@ -55,6 +55,7 @@
55	55
56	56	(% class="box" %)
57	57	(((
	60	+(% class="mark" %)**For Models: LPS8N, LG308N, DLOS8N**(%%)
58	58	//root@dragino-1dadd8:~~# **comgt -d /dev/ttyUSB3**
59	59	SIM ready
60	60	Waiting for Registration..(120 sec max)
...	...	@@ -77,7 +77,7 @@
77	77	[[image:image-20220527153827-5.png]]
78	78
79	79
80		-== 2.3 Check dialing info ==
	83	+=== 2.1.3 Check dialing info ===
81	81
82	82
83	83	run "**logread -f**" in gateway CLI。
...	...	@@ -261,7 +261,7 @@
261	261
262	262	= 5. How does the gateway view the International Mobile Equipment Identity (IMEI) =
263	263
264		-=== 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) ==
265	265
266	266
267	267	Users can get the IMEI via Linux command, but you have to access the gateway CLI.
...	...	@@ -277,7 +277,7 @@
277	277	[[image:image-20231218095426-6.jpeg||height="466" width="990"]]
278	278
279	279
280		-=== For LPS8v2 view the International Mobile Equipment Identity (IMEI) ===
	283	+== For LPS8v2 view the International Mobile Equipment Identity (IMEI) ==
281	281
282	282	(% class="box infomessage" %)
283	283	(((
...	...	@@ -290,7 +290,7 @@
290	290	[[image:image-20231218094741-3.png]]
291	291
292	292
293		-== **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) ==
294	294
295	295
296	296	Users can access the gateway CLI and run the minicom command to get the configuration interface.
...	...	@@ -324,7 +324,7 @@
324	324	[[image:image-20220527154154-7.png]]
325	325
326	326
327		-=== **International Mobile Equipment Identity (IMEI)** ===
	330	+== International Mobile Equipment Identity (IMEI) ==
328	328
329	329
330	330	(((
...	...	@@ -345,7 +345,7 @@
345	345	[[image:image-20220527154231-8.png]]
346	346
347	347
348		-=== **Integrated Circuit Card Identifier (ICCID)** ===
	351	+== Integrated Circuit Card Identifier (ICCID) ==
349	349
350	350
351	351	(((
...	...	@@ -495,6 +495,7 @@
495	495
496	496	== 7.1 How the gateway will consume data traffic ==
497	497
	501	+
498	498	Below list the place where the data traffic will use.
499	499
500	500	* Valid uplink data to LoRaWAN server or IoT server. ( We can't reduce this as they are the data we want)
...	...	@@ -504,34 +504,23 @@
504	504	* system Time synchronization Checking
505	505	* Auto update ( Software auto update, can be disabled)
506	506
507		-=== 7.1.1 LoRaWAN Status push or polling data to LoRaWAN server ===
508	508
509	509
510		-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 ===
511	511
512		-* Uplink self-status to the LoRaWAN server every 30s. the users can adjust **Keep Alive Period** as below
513		-* 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.
514	514
515		-[[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"]]**
516	516
	518	+[[image:image-20240712093532-1.png]]
517	517
518		-=== 7.1.2 System Keep Alive data ===
519	519
	521	+=== 7.1.2 Auto update ===
520	520
521		-System Keep Alive Data is used to check gateway-network status and fix possible issue. Gateway will check every 15 seconds and generate traffic.
522	522
523		-Base on 15 seconds per check, the data traffic is about 2M data traffic per day. Users can adjust **Keepalive Interval** as below.
524		-
525		-[[image:image-20220527155229-15.png||height="511" width="986"]]
526		-
527		-
528		-=== 7.1.3 Auto update ===
529		-
530		-
531	531	Gateway will check for update every day for new configure or software. User can disable them by below method.
532	532
533	533
534		-=== 7.1.4 Filter unwanted packets ===
	527	+=== 7.1.3 Filter unwanted packets ===
535	535
536	536
537	537	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