Last modified by Xiaoling on 2024/08/08 09:05
<
From version < 99.1 >
edited by Kilight Cao
on 2024/07/12 13:58
To version < 86.1 >
edited by Kilight Cao
on 2023/05/06 10:44
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -55,7 +55,6 @@
55 55  
56 56  (% class="box" %)
57 57  (((
58 -(% class="mark" %)**For Models: LPS8N, LG308N, DLOS8N**(%%)
59 59  //root@dragino-1dadd8:~~# **comgt -d /dev/ttyUSB3**
60 60  SIM ready
61 61  Waiting for Registration..(120 sec max)
... ... @@ -133,6 +133,7 @@
133 133  
134 134  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.
135 135  
135 +
136 136  [[image:image-20220718155937-1.png||height="562" width="497"]]
137 137  
138 138  
... ... @@ -141,6 +141,7 @@
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 +
144 144  [[image:1658131428288-728.png||height="538" width="494"]]
145 145  
146 146  
... ... @@ -149,6 +149,7 @@
149 149  
150 150  Users need to check whether the SIM card type is suitable for the EC25 module.
151 151  
153 +
152 152  [[image:1658131612484-845.png||height="549" width="499"]]
153 153  
154 154  
... ... @@ -157,6 +157,7 @@
157 157  
158 158  Users can insert SIM cards into the mobile phone for testing.
159 159  
162 +
160 160  [[image:image-20220718160804-3.png||height="602" width="500"]]
161 161  
162 162  
... ... @@ -262,38 +262,23 @@
262 262  
263 263  = 5. How does the gateway view the International Mobile Equipment Identity (IMEI) =
264 264  
265 -== For LIG16,LPS8, LPS8N, LG308, LG308N, DLOS8, DLOS8N view the International Mobile Equipment Identity (IMEI) ==
266 266  
267 -
268 268  Users can get the IMEI via Linux command, but you have to access the gateway CLI.
269 269  
270 270  (% class="box infomessage" %)
271 271  (((
272 -**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 **
273 273  )))
274 274  
275 -[[image:image-20231218095203-4.png]]
276 +[[image:image-20221027140604-1.png||height="330" width="707"]]
276 276  
277 277  
278 -[[image:image-20231218095426-6.jpeg||height="466" width="990"]]
279 +[[image:image-20221027151146-2.png||height="554" width="1000"]]
279 279  
280 280  
281 -== For LPS8v2 view the International Mobile Equipment Identity (IMEI) ==
282 +== **How does the gateway access the Quetel module directly (to send AT commands)** ==
282 282  
283 -(% class="box infomessage" %)
284 -(((
285 -**root@dragino-e4e891:~~# /usr/local/dragino/cell/getinfo.sh**
286 -)))
287 287  
288 -[[image:image-20231218094526-1.png]]
289 -
290 -
291 -[[image:image-20231218094741-3.png]]
292 -
293 -
294 -== How does the gateway access the Quetel module directly (to send AT commands) ==
295 -
296 -
297 297  Users can access the gateway CLI and run the minicom command to get the configuration interface.
298 298  
299 299  (((
... ... @@ -325,7 +325,7 @@
325 325  [[image:image-20220527154154-7.png]]
326 326  
327 327  
328 -== International Mobile Equipment Identity (IMEI) ==
316 +=== **International Mobile Equipment Identity (IMEI)** ===
329 329  
330 330  
331 331  (((
... ... @@ -346,7 +346,7 @@
346 346  [[image:image-20220527154231-8.png]]
347 347  
348 348  
349 -== Integrated Circuit Card Identifier (ICCID) ==
337 +=== **Integrated Circuit Card Identifier (ICCID)** ===
350 350  
351 351  
352 352  (((
... ... @@ -502,28 +502,34 @@
502 502  * Invalid uplink sensor data to LoRaWAN serevr. ( See Filter unwanted packets)
503 503  * LoRaWAN Status push or polling data to LoRaWAN server . ( We can reduce this part , see below for discussion)
504 504  * System Keep Alive data. ( To ensure the system is more robust, can be disabled)
505 -* system Time synchronization Checking
506 506  * Auto update ( Software auto update, can be disabled)
507 507  
495 +=== 7.1.1 LoRaWAN Status push or polling data to LoRaWAN server ===
508 508  
509 -(% class="wikigeneratedid" %)
510 -=== 7.1.1 Uploading backup files to reduced data consumption ===
497 +When gateway connect to LoRaWAN server via LoRaWAN protocol, besides the sensor data uplink/downlink. gateway will still need to:
511 511  
499 +* Uplink self-status to the LoRaWAN server every 30s. the users can adjust **Keep Alive Period** as below
500 +* 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.
512 512  
513 -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"]]**
502 +[[image:image-20220527155108-13.png]]
514 514  
515 -[[image:image-20240712093532-1.png]]
516 516  
505 +=== 7.1.2 System Keep Alive data ===
517 517  
518 -=== 7.1.2 Auto update ===
507 +System Keep Alive Data is used to check gateway-network status and fix possible issue. Gateway will check every 15 seconds and generate traffic.
519 519  
509 +Base on 15 seconds per check, the data traffic is about 2M data traffic per day. Users can adjust **Keepalive Interval** as below.
520 520  
521 -Gateway will check for update every day for new configure or software. User can disable them by below method.
511 +[[image:image-20220527155229-15.png||height="511" width="986"]]
522 522  
523 523  
524 -=== 7.1.3 Filter unwanted packets ===
514 +=== 7.1.3 Auto update ===
525 525  
516 +Gateway will check for update every day for new configure or software. User can disable them by below method.
526 526  
518 +
519 +=== 7.1.4 Filter unwanted packets ===
520 +
527 527  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.
528 528  
529 529  See [[How to filter unwanted packets>>doc:Main.Filter unwanted LoRaWAN packets.WebHome]]
... ... @@ -531,9 +531,9 @@
531 531  
532 532  == 7.2 Usage statistics ==
533 533  
528 +
534 534  === 7.2.1 How does Openwrt usage statistics ===
535 535  
536 -
537 537  This is a general instruction for the use of Openwrt of Dragino devices. Current models include:
538 538  
539 539  * LPS8,LPS8N
... ... @@ -541,6 +541,7 @@
541 541  * DLOS8,DLOS8N
542 542  * LIG16
543 543  
538 +
544 544  ~1. Activate LuCI and connect to SSH following [[these instructions>>doc:Main.Install Luci in the new UI firmware.WebHome]]
545 545  
546 546  2. Install luci-app-statistics using the following terminal commands:
Reduced_data_consumption.tar.gz
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -10.4 KB
Content
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
image-20240712093532-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -145.5 KB
Content

Applications

Navigation

Copyright ©2010-2022 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0