Last modified by Kilight Cao on 2024/12/31 16:38
<
From version < 100.1 >
edited by Kilight Cao
on 2024/08/07 17:10
To version < 82.4 >
edited by Xiaoling
on 2023/04/20 17:28
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Kilight
1 +XWiki.Xiaoling
Content
... ... @@ -28,9 +28,8 @@
28 28  
29 29  If there is a problem with the cellular connection. Please check the below points:
30 30  
31 -== 2.1 For LPS8N/DLOS8N/LG308N ==
32 32  
33 -=== 2.1.1 Do you order the model with a cellular option ===
32 +== 2.1 Do you order the model with a cellular option ==
34 34  
35 35  
36 36  Make sure you order the model with the cellular option. Can check by command or via the Web UI.
... ... @@ -46,7 +46,7 @@
46 46  [[image:image-20220601110748-1.png]]
47 47  
48 48  
49 -=== 2.1.2 Do you input the SIM card correctly ===
48 +== 2.2 Do you input the SIM card correctly ==
50 50  
51 51  
52 52  **Below command can check if you have a SIM card inserted, or via Web UI**
... ... @@ -56,7 +56,6 @@
56 56  
57 57  (% class="box" %)
58 58  (((
59 -(% class="mark" %)**For Models: LPS8N, LG308N, DLOS8N**(%%)
60 60  //root@dragino-1dadd8:~~# **comgt -d /dev/ttyUSB3**
61 61  SIM ready
62 62  Waiting for Registration..(120 sec max)
... ... @@ -79,7 +79,7 @@
79 79  [[image:image-20220527153827-5.png]]
80 80  
81 81  
82 -=== 2.1.3 Check dialing info ===
80 +== 2.3 Check dialing info ==
83 83  
84 84  
85 85  run "**logread -f**" in gateway CLI。
... ... @@ -134,6 +134,7 @@
134 134  
135 135  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.
136 136  
135 +
137 137  [[image:image-20220718155937-1.png||height="562" width="497"]]
138 138  
139 139  
... ... @@ -142,6 +142,7 @@
142 142  
143 143  It should be SIM card no flow, users can insert SIM cards into the mobile phone for testing.
144 144  
144 +
145 145  [[image:1658131428288-728.png||height="538" width="494"]]
146 146  
147 147  
... ... @@ -150,6 +150,7 @@
150 150  
151 151  Users need to check whether the SIM card type is suitable for the EC25 module.
152 152  
153 +
153 153  [[image:1658131612484-845.png||height="549" width="499"]]
154 154  
155 155  
... ... @@ -158,6 +158,7 @@
158 158  
159 159  Users can insert SIM cards into the mobile phone for testing.
160 160  
162 +
161 161  [[image:image-20220718160804-3.png||height="602" width="500"]]
162 162  
163 163  
... ... @@ -263,38 +263,23 @@
263 263  
264 264  = 5. How does the gateway view the International Mobile Equipment Identity (IMEI) =
265 265  
266 -== For LIG16,LPS8, LPS8N, LG308, LG308N, DLOS8, DLOS8N view the International Mobile Equipment Identity (IMEI) ==
267 267  
268 -
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-24b3c8:~~# comgt -d /dev/ttyModemAT -s /etc/gcom/getimei.gcom **
273 +**root@dragino-1b7c4c:~~# comgt -d /dev/ttyModemAT -s /etc/gcom/getimsi.gcom **
274 274  )))
275 275  
276 -[[image:image-20231218095203-4.png]]
276 +[[image:image-20221027140604-1.png||height="330" width="707"]]
277 277  
278 278  
279 -[[image:image-20231218095426-6.jpeg||height="466" width="990"]]
279 +[[image:image-20221027151146-2.png||height="554" width="1000"]]
280 280  
281 281  
282 -== For LPS8v2 view the International Mobile Equipment Identity (IMEI) ==
282 +== **How does the gateway access the Quetel module directly (to send AT commands)** ==
283 283  
284 -(% class="box infomessage" %)
285 -(((
286 -**root@dragino-e4e891:~~# /usr/local/dragino/cell/getinfo.sh**
287 -)))
288 288  
289 -[[image:image-20231218094526-1.png]]
290 -
291 -
292 -[[image:image-20231218094741-3.png]]
293 -
294 -
295 -== How does the gateway access the Quetel module directly (to send AT commands) ==
296 -
297 -
298 298  Users can access the gateway CLI and run the minicom command to get the configuration interface.
299 299  
300 300  (((
... ... @@ -326,7 +326,7 @@
326 326  [[image:image-20220527154154-7.png]]
327 327  
328 328  
329 -== International Mobile Equipment Identity (IMEI) ==
316 +=== **International Mobile Equipment Identity (IMEI)** ===
330 330  
331 331  
332 332  (((
... ... @@ -347,7 +347,7 @@
347 347  [[image:image-20220527154231-8.png]]
348 348  
349 349  
350 -== Integrated Circuit Card Identifier (ICCID) ==
337 +=== **Integrated Circuit Card Identifier (ICCID)** ===
351 351  
352 352  
353 353  (((
... ... @@ -495,51 +495,43 @@
495 495  
496 496  = 7. How to reduce data traffic =
497 497  
498 -== 7.1 How the gateway will consume data traffic ==
485 +== 7.1 Reduce Status Uplink Interval ==
499 499  
500 -Below list the place where the data traffic will use.
501 501  
502 -* Valid uplink data to LoRaWAN server or IoT server. ( We can't reduce this as they are the data we want)
503 -* Invalid uplink sensor data to LoRaWAN serevr. ( See Filter unwanted packets)
504 -* LoRaWAN Status push or polling data to LoRaWAN server . ( We can reduce this part , see below for discussion)
505 -* System Keep Alive data. ( To ensure the system is more robust, can be disabled)
506 -* system Time synchronization Checking
507 -* Auto update ( Software auto update, can be disabled)
488 +**The gateways will use the data traffic below two places.**
508 508  
509 -=== 7.1.1 Uploading backup files to reduced data consumption ===
510 510  
491 +~1. There is the data traffic from LoRa package Forward which were the gateway status package and sensor end node uplink/downlink.
511 511  
512 -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"]]**
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.
513 513  
514 -[[image:image-20240712093532-1.png]]
495 +[[image:image-20220527155108-13.png]]
515 515  
516 516  
517 -=== 7.1.2 Auto update ===
518 518  
499 +2. There is the data traffic from the gateway check self-network status. by default, the gateway will check the network per 15s.
519 519  
520 -Gateway will check for update every day for new configure or software. User can disable them by below method.
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.
521 521  
503 +[[image:image-20220527155358-16.png]]
522 522  
523 -=== 7.1.3 Filter unwanted packets ===
505 +System General interface
524 524  
525 525  
526 -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.
508 +[[image:image-20220527155229-15.png]]
527 527  
528 -See [[How to filter unwanted packets>>doc:Main.Filter unwanted LoRaWAN packets.WebHome]]
510 +Keepalive script interval time settings
529 529  
530 530  
531 -== 7.2 Usage statistics ==
513 +== 7.2 Filter unwanted packets ==
532 532  
533 -=== 7.2.1 How does Openwrt usage statistics ===
534 534  
516 +See [[How to filter unwanted packets>>doc:Main.Filter unwanted LoRaWAN packets.WebHome]]
535 535  
536 -This is a general instruction for the use of Openwrt of Dragino devices. Current models include:
537 537  
538 -* LPS8,LPS8N
539 -* LG308,LG308N
540 -* DLOS8,DLOS8N
541 -* LIG16
519 +== 7.3 Usage statistics ==
542 542  
521 +
543 543  ~1. Activate LuCI and connect to SSH following [[these instructions>>doc:Main.Install Luci in the new UI firmware.WebHome]]
544 544  
545 545  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-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0