Summary

• Page properties (1 modified, 0 added, 0 removed)
• Attachments (0 modified, 3 added, 0 removed)
  • Reduced_data_consumption.tar.gz
  • image-20240712093532-1.png
  • image-20241205150916-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。
...	...	@@ -132,7 +132,6 @@
132	132
133	133	Regarding what APN your SIM card should use, Users can search for the APN corresponding to the SIM card by Google or ask the carrier.
134	134
135		-
136	136	[[image:image-20220718155937-1.png||height="562" width="497"]]
137	137
138	138
...	...	@@ -141,7 +141,6 @@
141	141
142	142	It should be SIM card no flow, users can insert SIM cards into the mobile phone for testing.
143	143
144		-
145	145	[[image:1658131428288-728.png||height="538" width="494"]]
146	146
147	147
...	...	@@ -150,7 +150,6 @@
150	150
151	151	Users need to check whether the SIM card type is suitable for the EC25 module.
152	152
153		-
154	154	[[image:1658131612484-845.png||height="549" width="499"]]
155	155
156	156
...	...	@@ -159,7 +159,6 @@
159	159
160	160	Users can insert SIM cards into the mobile phone for testing.
161	161
162		-
163	163	[[image:image-20220718160804-3.png||height="602" width="500"]]
164	164
165	165
...	...	@@ -265,7 +265,7 @@
265	265
266	266	= 5. How does the gateway view the International Mobile Equipment Identity (IMEI) =
267	267
268		-=== 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) ==
269	269
270	270
271	271	Users can get the IMEI via Linux command, but you have to access the gateway CLI.
...	...	@@ -281,7 +281,7 @@
281	281	[[image:image-20231218095426-6.jpeg||height="466" width="990"]]
282	282
283	283
284		-=== For LPS8v2 view the International Mobile Equipment Identity (IMEI) ===
	283	+== For LPS8v2 view the International Mobile Equipment Identity (IMEI) ==
285	285
286	286	(% class="box infomessage" %)
287	287	(((
...	...	@@ -294,7 +294,7 @@
294	294	[[image:image-20231218094741-3.png]]
295	295
296	296
297		-== **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) ==
298	298
299	299
300	300	Users can access the gateway CLI and run the minicom command to get the configuration interface.
...	...	@@ -328,7 +328,7 @@
328	328	[[image:image-20220527154154-7.png]]
329	329
330	330
331		-=== **International Mobile Equipment Identity (IMEI)** ===
	330	+== International Mobile Equipment Identity (IMEI) ==
332	332
333	333
334	334	(((
...	...	@@ -349,7 +349,7 @@
349	349	[[image:image-20220527154231-8.png]]
350	350
351	351
352		-=== **Integrated Circuit Card Identifier (ICCID)** ===
	351	+== Integrated Circuit Card Identifier (ICCID) ==
353	353
354	354
355	355	(((
...	...	@@ -499,6 +499,7 @@
499	499
500	500	== 7.1 How the gateway will consume data traffic ==
501	501
	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,32 +508,25 @@
508	508	* system Time synchronization Checking
509	509	* Auto update ( Software auto update, can be disabled)
510	510
511		-=== 7.1.1 LoRaWAN Status push or polling data to LoRaWAN server ===
512	512
513		-When gateway connect to LoRaWAN server via LoRaWAN protocol, besides the sensor data uplink/downlink. gateway will still need to:
514	514
515		-* Uplink self-status to the LoRaWAN server every 30s. the users can adjust **Keep Alive Period** as below
516		-* 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.
	513	+=== 7.1.1 Uploading backup files to reduced data consumption ===
517	517
518		-[[image:image-20220527155108-13.png]]
519	519
	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"]]**
520	520
521		-=== 7.1.2 System Keep Alive data ===
	518	+[[image:image-20240712093532-1.png]]
522	522
523		-System Keep Alive Data is used to check gateway-network status and fix possible issue. Gateway will check every 15 seconds and generate traffic.
524	524
525		-Base on 15 seconds per check, the data traffic is about 2M data traffic per day. Users can adjust **Keepalive Interval** as below.
	521	+=== 7.1.2 Auto update ===
526	526
527		-[[image:image-20220527155229-15.png||height="511" width="986"]]
528	528
529		-
530		-=== 7.1.3 Auto update ===
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
	529	+
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.
538	538
539	539	See [[How to filter unwanted packets>>doc:Main.Filter unwanted LoRaWAN packets.WebHome]]
...	...	@@ -541,9 +541,9 @@
541	541
542	542	== 7.2 Usage statistics ==
543	543
544		-
545	545	=== 7.2.1 How does Openwrt usage statistics ===
546	546
	539	+
547	547	This is a general instruction for the use of Openwrt of Dragino devices. Current models include:
548	548
549	549	* LPS8,LPS8N

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

image-20241205150916-1.png

Author

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

Size

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

Content