Last modified by Xiaoling on 2024/08/08 09:05
<
From version < 86.1 >
edited by Kilight Cao
on 2023/05/06 10:44
To version < 94.2 >
edited by Xiaoling
on 2023/12/20 17:26
>
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
... ... @@ -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,20 +265,35 @@
265 265  
266 266  = 5. How does the gateway view the International Mobile Equipment Identity (IMEI) =
267 267  
264 +=== For LIG16,LPS8, LPS8N, LG308, LG308N, DLOS8, DLOS8N view the International Mobile Equipment Identity (IMEI) ===
268 268  
266 +
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 **
271 +**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"]]
274 +[[image:image-20231218095203-4.png]]
277 277  
278 278  
279 -[[image:image-20221027151146-2.png||height="554" width="1000"]]
277 +[[image:image-20231218095426-6.jpeg||height="466" width="990"]]
280 280  
281 281  
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 +
282 282  == **How does the gateway access the Quetel module directly (to send AT commands)** ==
283 283  
284 284  
... ... @@ -490,10 +490,12 @@
490 490  * Invalid uplink sensor data to LoRaWAN serevr. ( See Filter unwanted packets)
491 491  * LoRaWAN Status push or polling data to LoRaWAN server . ( We can reduce this part , see below for discussion)
492 492  * System Keep Alive data. ( To ensure the system is more robust, can be disabled)
504 +* system Time synchronization Checking
493 493  * Auto update ( Software auto update, can be disabled)
494 494  
495 495  === 7.1.1 LoRaWAN Status push or polling data to LoRaWAN server ===
496 496  
509 +
497 497  When gateway connect to LoRaWAN server via LoRaWAN protocol, besides the sensor data uplink/downlink. gateway will still need to:
498 498  
499 499  * Uplink self-status to the LoRaWAN server every 30s. the users can adjust **Keep Alive Period** as below
... ... @@ -504,6 +504,7 @@
504 504  
505 505  === 7.1.2 System Keep Alive data ===
506 506  
520 +
507 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.
508 508  
509 509  Base on 15 seconds per check, the data traffic is about 2M data traffic per day. Users can adjust **Keepalive Interval** as below.
... ... @@ -513,11 +513,13 @@
513 513  
514 514  === 7.1.3 Auto update ===
515 515  
530 +
516 516  Gateway will check for update every day for new configure or software. User can disable them by below method.
517 517  
518 518  
519 519  === 7.1.4 Filter unwanted packets ===
520 520  
536 +
521 521  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.
522 522  
523 523  See [[How to filter unwanted packets>>doc:Main.Filter unwanted LoRaWAN packets.WebHome]]
... ... @@ -525,9 +525,9 @@
525 525  
526 526  == 7.2 Usage statistics ==
527 527  
528 -
529 529  === 7.2.1 How does Openwrt usage statistics ===
530 530  
546 +
531 531  This is a general instruction for the use of Openwrt of Dragino devices. Current models include:
532 532  
533 533  * LPS8,LPS8N
... ... @@ -535,7 +535,6 @@
535 535  * DLOS8,DLOS8N
536 536  * LIG16
537 537  
538 -
539 539  ~1. Activate LuCI and connect to SSH following [[these instructions>>doc:Main.Install Luci in the new UI firmware.WebHome]]
540 540  
541 541  2. Install luci-app-statistics using the following terminal commands:
image-20231218094526-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +23.3 KB
Content
image-20231218094728-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +38.2 KB
Content
image-20231218094741-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +47.5 KB
Content
image-20231218095203-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +18.5 KB
Content
image-20231218095257-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +73.0 KB
Content
image-20231218095426-6.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +53.7 KB
Content

Applications

Navigation

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