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.Kilight
	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**
...	...	@@ -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,23 +265,38 @@
265	265
266	266	= 5. How does the gateway view the International Mobile Equipment Identity (IMEI) =
267	267
	267	+== For LIG16,LPS8, LPS8N, LG308, LG308N, DLOS8, DLOS8N view the International Mobile Equipment Identity (IMEI) ==
268	268
	269	+
269	269	Users can get the IMEI via Linux command, but you have to access the gateway CLI.
270	270
271	271	(% class="box infomessage" %)
272	272	(((
273		-**root@dragino-1b7c4c:~~# comgt -d /dev/ttyModemAT -s /etc/gcom/getimsi.gcom **
	274	+**root@dragino-24b3c8:~~# comgt -d /dev/ttyModemAT -s /etc/gcom/getimei.gcom **
274	274	)))
275	275
276		-[[image:image-20221027140604-1.png||height="330" width="707"]]
	277	+[[image:image-20231218095203-4.png]]
277	277
278	278
279		-[[image:image-20221027151146-2.png||height="554" width="1000"]]
	280	+[[image:image-20231218095426-6.jpeg||height="466" width="990"]]
280	280
281	281
282		-== **How does the gateway access the Quetel module directly (to send AT commands)** ==
	283	+== For LPS8v2 view the International Mobile Equipment Identity (IMEI) ==
283	283
	285	+(% class="box infomessage" %)
	286	+(((
	287	+**root@dragino-e4e891:~~# /usr/local/dragino/cell/getinfo.sh**
	288	+)))
284	284
	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	+
285	285	Users can access the gateway CLI and run the minicom command to get the configuration interface.
286	286
287	287	(((
...	...	@@ -313,7 +313,7 @@
313	313	[[image:image-20220527154154-7.png]]
314	314
315	315
316		-=== **International Mobile Equipment Identity (IMEI)** ===
	330	+== International Mobile Equipment Identity (IMEI) ==
317	317
318	318
319	319	(((
...	...	@@ -334,7 +334,7 @@
334	334	[[image:image-20220527154231-8.png]]
335	335
336	336
337		-=== **Integrated Circuit Card Identifier (ICCID)** ===
	351	+== Integrated Circuit Card Identifier (ICCID) ==
338	338
339	339
340	340	(((
...	...	@@ -484,6 +484,7 @@
484	484
485	485	== 7.1 How the gateway will consume data traffic ==
486	486
	501	+
487	487	Below list the place where the data traffic will use.
488	488
489	489	* Valid uplink data to LoRaWAN server or IoT server. ( We can't reduce this as they are the data we want)
...	...	@@ -493,32 +493,25 @@
493	493	* system Time synchronization Checking
494	494	* Auto update ( Software auto update, can be disabled)
495	495
496		-=== 7.1.1 LoRaWAN Status push or polling data to LoRaWAN server ===
497	497
498		-When gateway connect to LoRaWAN server via LoRaWAN protocol, besides the sensor data uplink/downlink. gateway will still need to:
499	499
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.
	513	+=== 7.1.1 Uploading backup files to reduced data consumption ===
502	502
503		-[[image:image-20220527155108-13.png]]
504	504
	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"]]**
505	505
506		-=== 7.1.2 System Keep Alive data ===
	518	+[[image:image-20240712093532-1.png]]
507	507
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.
509	509
510		-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 ===
511	511
512		-[[image:image-20220527155229-15.png||height="511" width="986"]]
513	513
514		-
515		-=== 7.1.3 Auto update ===
516		-
517	517	Gateway will check for update every day for new configure or software. User can disable them by below method.
518	518
519	519
520		-=== 7.1.4 Filter unwanted packets ===
	527	+=== 7.1.3 Filter unwanted packets ===
521	521
	529	+
522	522	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.
523	523
524	524	See [[How to filter unwanted packets>>doc:Main.Filter unwanted LoRaWAN packets.WebHome]]
...	...	@@ -526,9 +526,9 @@
526	526
527	527	== 7.2 Usage statistics ==
528	528
529		-
530	530	=== 7.2.1 How does Openwrt usage statistics ===
531	531
	539	+
532	532	This is a general instruction for the use of Openwrt of Dragino devices. Current models include:
533	533
534	534	* 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