Summary

• Page properties (1 modified, 0 added, 0 removed)
• Attachments (0 modified, 0 added, 3 removed)
  • Reduced_data_consumption.tar.gz
  • image-20240712093532-1.png
  • image-20241205150916-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**
...	...	@@ -57,7 +57,6 @@
57	57
58	58	(% class="box" %)
59	59	(((
60		-(% class="mark" %)**For Models: LPS8N, LG308N, DLOS8N**(%%)
61	61	//root@dragino-1dadd8:~~# **comgt -d /dev/ttyUSB3**
62	62	SIM ready
63	63	Waiting for Registration..(120 sec max)
...	...	@@ -80,7 +80,7 @@
80	80	[[image:image-20220527153827-5.png]]
81	81
82	82
83		-=== 2.1.3 Check dialing info ===
	80	+== 2.3 Check dialing info ==
84	84
85	85
86	86	run "**logread -f**" in gateway CLI。
...	...	@@ -135,6 +135,7 @@
135	135
136	136	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.
137	137
	135	+
138	138	[[image:image-20220718155937-1.png||height="562" width="497"]]
139	139
140	140
...	...	@@ -143,6 +143,7 @@
143	143
144	144	It should be SIM card no flow, users can insert SIM cards into the mobile phone for testing.
145	145
	144	+
146	146	[[image:1658131428288-728.png||height="538" width="494"]]
147	147
148	148
...	...	@@ -151,6 +151,7 @@
151	151
152	152	Users need to check whether the SIM card type is suitable for the EC25 module.
153	153
	153	+
154	154	[[image:1658131612484-845.png||height="549" width="499"]]
155	155
156	156
...	...	@@ -159,6 +159,7 @@
159	159
160	160	Users can insert SIM cards into the mobile phone for testing.
161	161
	162	+
162	162	[[image:image-20220718160804-3.png||height="602" width="500"]]
163	163
164	164
...	...	@@ -264,38 +264,23 @@
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) ==
268	268
269		-
270	270	Users can get the IMEI via Linux command, but you have to access the gateway CLI.
271	271
272	272	(% class="box infomessage" %)
273	273	(((
274		-**root@dragino-24b3c8:~~# comgt -d /dev/ttyModemAT -s /etc/gcom/getimei.gcom **
	273	+**root@dragino-1b7c4c:~~# comgt -d /dev/ttyModemAT -s /etc/gcom/getimsi.gcom **
275	275	)))
276	276
277		-[[image:image-20231218095203-4.png]]
	276	+[[image:image-20221027140604-1.png||height="330" width="707"]]
278	278
279	279
280		-[[image:image-20231218095426-6.jpeg||height="466" width="990"]]
	279	+[[image:image-20221027151146-2.png||height="554" width="1000"]]
281	281
282	282
283		-== For LPS8v2 view the International Mobile Equipment Identity (IMEI) ==
	282	+== **How does the gateway access the Quetel module directly (to send AT commands)** ==
284	284
285		-(% class="box infomessage" %)
286		-(((
287		-**root@dragino-e4e891:~~# /usr/local/dragino/cell/getinfo.sh**
288		-)))
289	289
290		-[[image:image-20231218094526-1.png]]
291		-
292		-
293		-[[image:image-20231218094741-3.png]]
294		-
295		-
296		-== How does the gateway access the Quetel module directly (to send AT commands) ==
297		-
298		-
299	299	Users can access the gateway CLI and run the minicom command to get the configuration interface.
300	300
301	301	(((
...	...	@@ -327,7 +327,7 @@
327	327	[[image:image-20220527154154-7.png]]
328	328
329	329
330		-== International Mobile Equipment Identity (IMEI) ==
	316	+=== **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) ==
	337	+=== **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,25 +508,32 @@
508	508	* system Time synchronization Checking
509	509	* Auto update ( Software auto update, can be disabled)
510	510
	496	+=== 7.1.1 LoRaWAN Status push or polling data to LoRaWAN server ===
511	511
	498	+When gateway connect to LoRaWAN server via LoRaWAN protocol, besides the sensor data uplink/downlink. gateway will still need to:
512	512
513		-=== 7.1.1 Uploading backup files to reduced data consumption ===
	500	+* Uplink self-status to the LoRaWAN server every 30s. the users can adjust **Keep Alive Period** as below
	501	+* 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
	503	+[[image:image-20220527155108-13.png]]
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"]]**
517	517
518		-[[image:image-20240712093532-1.png]]
	506	+=== 7.1.2 System Keep Alive data ===
519	519
	508	+System Keep Alive Data is used to check gateway-network status and fix possible issue. Gateway will check every 15 seconds and generate traffic.
520	520
521		-=== 7.1.2 Auto update ===
	510	+Base on 15 seconds per check, the data traffic is about 2M data traffic per day. Users can adjust **Keepalive Interval** as below.
522	522
	512	+[[image:image-20220527155229-15.png||height="511" width="986"]]
523	523
524		-Gateway will check for update every day for new configure or software. User can disable them by below method.
525	525
	515	+=== 7.1.3 Auto update ===
526	526
527		-=== 7.1.3 Filter unwanted packets ===
	517	+Gateway will check for update every day for new configure or software. User can disable them by below method.
528	528
529	529
	520	+=== 7.1.4 Filter unwanted packets ===
	521	+
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.
531	531
532	532	See [[How to filter unwanted packets>>doc:Main.Filter unwanted LoRaWAN packets.WebHome]]
...	...	@@ -534,9 +534,9 @@
534	534
535	535	== 7.2 Usage statistics ==
536	536
	529	+
537	537	=== 7.2.1 How does Openwrt usage statistics ===
538	538
539		-
540	540	This is a general instruction for the use of Openwrt of Dragino devices. Current models include:
541	541
542	542	* LPS8,LPS8N

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

image-20241205150916-1.png

Author

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

Size

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

Content