Last modified by Kilight Cao on 2024/12/31 16:38
<
From version < 82.3 >
edited by Xiaoling
on 2023/04/20 17:18
To version < 97.1 >
edited by Kilight Cao
on 2024/07/12 09:36
>
Change comment: Uploaded new attachment "image-20240712093532-1.png", version {1}

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.Kilight
Content
... ... @@ -55,6 +55,7 @@
55 55  
56 56  (% class="box" %)
57 57  (((
58 +(% 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)
... ... @@ -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  
... ... @@ -215,7 +215,6 @@
215 215  Once the Ethernet of the Wi-Fi network is unavailable where the gateway network will switch to a Cell network from Ethernet or Wi-Fi.
216 216  
217 217  
218 -
219 219  **Enable Cellular and connect Ethernet at the same time**
220 220  
221 221  ETH icon is displayed as ​​​ [[image:1658135519305-444.png||height="18" width="19"]] Indicates that Ethernet is the main working network.
... ... @@ -266,23 +266,38 @@
266 266  
267 267  = 5. How does the gateway view the International Mobile Equipment Identity (IMEI) =
268 268  
265 +== For LIG16,LPS8, LPS8N, LG308, LG308N, DLOS8, DLOS8N view the International Mobile Equipment Identity (IMEI) ==
269 269  
267 +
270 270  Users can get the IMEI via Linux command, but you have to access the gateway CLI.
271 271  
272 272  (% class="box infomessage" %)
273 273  (((
274 -**root@dragino-1b7c4c:~~# comgt -d /dev/ttyModemAT -s /etc/gcom/getimsi.gcom **
272 +**root@dragino-24b3c8:~~# comgt -d /dev/ttyModemAT -s /etc/gcom/getimei.gcom **
275 275  )))
276 276  
277 -[[image:image-20221027140604-1.png||height="330" width="707"]]
275 +[[image:image-20231218095203-4.png]]
278 278  
279 279  
280 -[[image:image-20221027151146-2.png||height="554" width="1000"]]
278 +[[image:image-20231218095426-6.jpeg||height="466" width="990"]]
281 281  
282 282  
283 -== **How does the gateway access the Quetel module directly (to send AT commands)** ==
281 +== For LPS8v2 view the International Mobile Equipment Identity (IMEI) ==
284 284  
283 +(% class="box infomessage" %)
284 +(((
285 +**root@dragino-e4e891:~~# /usr/local/dragino/cell/getinfo.sh**
286 +)))
285 285  
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 +
286 286  Users can access the gateway CLI and run the minicom command to get the configuration interface.
287 287  
288 288  (((
... ... @@ -314,7 +314,7 @@
314 314  [[image:image-20220527154154-7.png]]
315 315  
316 316  
317 -=== **International Mobile Equipment Identity (IMEI)** ===
328 +== International Mobile Equipment Identity (IMEI) ==
318 318  
319 319  
320 320  (((
... ... @@ -335,7 +335,7 @@
335 335  [[image:image-20220527154231-8.png]]
336 336  
337 337  
338 -=== **Integrated Circuit Card Identifier (ICCID)** ===
349 +== Integrated Circuit Card Identifier (ICCID) ==
339 339  
340 340  
341 341  (((
... ... @@ -483,43 +483,64 @@
483 483  
484 484  = 7. How to reduce data traffic =
485 485  
486 -== 7.1 Reduce Status Uplink Interval ==
497 +== 7.1 How the gateway will consume data traffic ==
487 487  
499 +Below list the place where the data traffic will use.
488 488  
489 -**The gateways will use the data traffic below two places.**
501 +* Valid uplink data to LoRaWAN server or IoT server. ( We can't reduce this as they are the data we want)
502 +* Invalid uplink sensor data to LoRaWAN serevr. ( See Filter unwanted packets)
503 +* LoRaWAN Status push or polling data to LoRaWAN server . ( We can reduce this part , see below for discussion)
504 +* System Keep Alive data. ( To ensure the system is more robust, can be disabled)
505 +* system Time synchronization Checking
506 +* Auto update ( Software auto update, can be disabled)
490 490  
508 +=== 7.1.1 LoRaWAN Status push or polling data to LoRaWAN server ===
491 491  
492 -~1. There is the data traffic from LoRa package Forward which were the gateway status package and sensor end node uplink/downlink.
493 493  
494 -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 +When gateway connect to LoRaWAN server via LoRaWAN protocol, besides the sensor data uplink/downlink. gateway will still need to:
495 495  
513 +* Uplink self-status to the LoRaWAN server every 30s. the users can adjust **Keep Alive Period** as below
514 +* 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.
515 +
496 496  [[image:image-20220527155108-13.png]]
497 497  
498 498  
519 +=== 7.1.2 System Keep Alive data ===
499 499  
500 -2. There is the data traffic from the gateway check self-network status. by default, the gateway will check the network per 15s.
501 501  
502 -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 +System Keep Alive Data is used to check gateway-network status and fix possible issue. Gateway will check every 15 seconds and generate traffic.
503 503  
504 -[[image:image-20220527155358-16.png]]
524 +Base on 15 seconds per check, the data traffic is about 2M data traffic per day. Users can adjust **Keepalive Interval** as below.
505 505  
506 -System General interface
526 +[[image:image-20220527155229-15.png||height="511" width="986"]]
507 507  
508 508  
509 -[[image:image-20220527155229-15.png]]
529 +=== 7.1.3 Auto update ===
510 510  
511 -Keepalive script interval time settings
512 512  
532 +Gateway will check for update every day for new configure or software. User can disable them by below method.
513 513  
514 -== 7.2 Filter unwanted packets ==
515 515  
535 +=== 7.1.4 Filter unwanted packets ===
516 516  
537 +
538 +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.
539 +
517 517  See [[How to filter unwanted packets>>doc:Main.Filter unwanted LoRaWAN packets.WebHome]]
518 518  
519 519  
520 -== 7.3 Usage statistics ==
543 +== 7.2 Usage statistics ==
521 521  
545 +=== 7.2.1 How does Openwrt usage statistics ===
522 522  
547 +
548 +This is a general instruction for the use of Openwrt of Dragino devices. Current models include:
549 +
550 +* LPS8,LPS8N
551 +* LG308,LG308N
552 +* DLOS8,DLOS8N
553 +* LIG16
554 +
523 523  ~1. Activate LuCI and connect to SSH following [[these instructions>>doc:Main.Install Luci in the new UI firmware.WebHome]]
524 524  
525 525  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
image-20240712093532-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +145.5 KB
Content

Applications

Navigation

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