Summary

• Page properties (1 modified, 0 added, 0 removed)
• Attachments (0 modified, 0 added, 6 removed)
  • image-20231218094526-1.png
  • image-20231218094728-2.png
  • image-20231218094741-3.png
  • image-20231218095203-4.png
  • image-20231218095257-5.png
  • image-20231218095426-6.jpeg

Details

Page properties

Content

...	...	@@ -132,6 +132,7 @@
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	+
135	135	[[image:image-20220718155937-1.png||height="562" width="497"]]
136	136
137	137
...	...	@@ -140,6 +140,7 @@
140	140
141	141	It should be SIM card no flow, users can insert SIM cards into the mobile phone for testing.
142	142
	144	+
143	143	[[image:1658131428288-728.png||height="538" width="494"]]
144	144
145	145
...	...	@@ -148,6 +148,7 @@
148	148
149	149	Users need to check whether the SIM card type is suitable for the EC25 module.
150	150
	153	+
151	151	[[image:1658131612484-845.png||height="549" width="499"]]
152	152
153	153
...	...	@@ -156,6 +156,7 @@
156	156
157	157	Users can insert SIM cards into the mobile phone for testing.
158	158
	162	+
159	159	[[image:image-20220718160804-3.png||height="602" width="500"]]
160	160
161	161
...	...	@@ -261,35 +261,20 @@
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) ===
265	265
266		-
267	267	Users can get the IMEI via Linux command, but you have to access the gateway CLI.
268	268
269	269	(% class="box infomessage" %)
270	270	(((
271		-**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 **
272	272	)))
273	273
274		-[[image:image-20231218095203-4.png]]
	276	+[[image:image-20221027140604-1.png||height="330" width="707"]]
275	275
276	276
277		-[[image:image-20231218095426-6.jpeg||height="466" width="990"]]
	279	+[[image:image-20221027151146-2.png||height="554" width="1000"]]
278	278
279	279
280		-=== For LPS8v2 view the International Mobile Equipment Identity (IMEI) ===
281		-
282		-(% class="box infomessage" %)
283		-(((
284		-**root@dragino-e4e891:~~# /usr/local/dragino/cell/getinfo.sh**
285		-)))
286		-
287		-[[image:image-20231218094526-1.png]]
288		-
289		-
290		-[[image:image-20231218094741-3.png]]
291		-
292		-
293	293	== **How does the gateway access the Quetel module directly (to send AT commands)** ==
294	294
295	295
...	...	@@ -493,64 +493,43 @@
493	493
494	494	= 7. How to reduce data traffic =
495	495
496		-== 7.1 How the gateway will consume data traffic ==
	485	+== 7.1 Reduce Status Uplink Interval ==
497	497
498		-Below list the place where the data traffic will use.
499	499
500		-* Valid uplink data to LoRaWAN server or IoT server. ( We can't reduce this as they are the data we want)
501		-* Invalid uplink sensor data to LoRaWAN serevr. ( See Filter unwanted packets)
502		-* LoRaWAN Status push or polling data to LoRaWAN server . ( We can reduce this part , see below for discussion)
503		-* System Keep Alive data. ( To ensure the system is more robust, can be disabled)
504		-* system Time synchronization Checking
505		-* Auto update ( Software auto update, can be disabled)
	488	+**The gateways will use the data traffic below two places.**
506	506
507		-=== 7.1.1 LoRaWAN Status push or polling data to LoRaWAN server ===
508	508
	491	+~1. There is the data traffic from LoRa package Forward which were the gateway status package and sensor end node uplink/downlink.
509	509
510		-When gateway connect to LoRaWAN server via LoRaWAN protocol, besides the sensor data uplink/downlink. gateway will still need to:
	493	+For this case, by default, the gateway will uplink self-status to the LoRaWAN server per the 30s. the users can adjust the interval time.
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		-
515	515	[[image:image-20220527155108-13.png]]
516	516
517	517
518		-=== 7.1.2 System Keep Alive data ===
519	519
	499	+2. There is the data traffic from the gateway check self-network status. by default, the gateway will check the network per 15s.
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.
	501	+For this case, We have monitored the loss of data traffic, which is the loss of 2M data traffic per day. the users can adjust the interval time following screenshots.
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.
	503	+[[image:image-20220527155358-16.png]]
524	524
525		-[[image:image-20220527155229-15.png||height="511" width="986"]]
	505	+System General interface
526	526
527	527
528		-=== 7.1.3 Auto update ===
	508	+[[image:image-20220527155229-15.png]]
529	529
	510	+Keepalive script interval time settings
530	530
531		-Gateway will check for update every day for new configure or software. User can disable them by below method.
532	532
	513	+== 7.2 Filter unwanted packets ==
533	533
534		-=== 7.1.4 Filter unwanted packets ===
535	535
536		-
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		-
539	539	See [[How to filter unwanted packets>>doc:Main.Filter unwanted LoRaWAN packets.WebHome]]
540	540
541	541
542		-== 7.2 Usage statistics ==
	519	+== 7.3 Usage statistics ==
543	543
544		-=== 7.2.1 How does Openwrt usage statistics ===
545	545
546		-
547		-This is a general instruction for the use of Openwrt of Dragino devices. Current models include:
548		-
549		-* LPS8,LPS8N
550		-* LG308,LG308N
551		-* DLOS8,DLOS8N
552		-* LIG16
553		-
554	554	~1. Activate LuCI and connect to SSH following [[these instructions>>doc:Main.Install Luci in the new UI firmware.WebHome]]
555	555
556	556	2. Install luci-app-statistics using the following terminal commands:

image-20231218094526-1.png

Author

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

Size

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

Content

image-20231218094728-2.png

Author

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

Size

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

Content

image-20231218094741-3.png

Author

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

Size

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

Content

image-20231218095203-4.png

Author

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

Size

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

Content

image-20231218095257-5.png

Author

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

Size

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

Content

image-20231218095426-6.jpeg

Author

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

Size

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

Content