<
From version < 94.2 >
edited by Xiaoling
on 2023/12/20 17:26
To version < 82.2 >
edited by Xiaoling
on 2023/03/23 17:38
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -9,7 +9,7 @@
9 9  = 1. Enable Cellular Connection =
10 10  
11 11  
12 -If your device has a Cellular module, you can see the below screenshot. enable the cellular connection here.
12 +//If your device has a Cellular module, you can see the below screenshot. enable the cellular connection here.//
13 13  
14 14  [[image:image-20220601110850-2.png]]
15 15  
... ... @@ -17,7 +17,7 @@
17 17  
18 18  
19 19  (((
20 -If your device doesn't have a cellular module, you will see a cellular module not detected.
20 +//If your device doesn't have a cellular module, you will see a cellular module not detected.//
21 21  )))
22 22  
23 23  [[image:image-20220527153544-2.png]]
... ... @@ -26,13 +26,13 @@
26 26  = 2. How to Debug if Cellular connection fails =
27 27  
28 28  
29 -If there is a problem with the cellular connection. Please check the below points:
29 +//If there is a problem with the cellular connection. Please check the below points~://
30 30  
31 31  
32 32  == 2.1 Do you order the model with a cellular option ==
33 33  
34 34  
35 -Make sure you order the model with the cellular option. Can check by command or via the Web UI.
35 +//Make sure you order the model with the cellular option. Can check by command or via the Web UI.//
36 36  
37 37  (% class="box" %)
38 38  (((
... ... @@ -48,10 +48,10 @@
48 48  == 2.2 Do you input the SIM card correctly ==
49 49  
50 50  
51 -**Below command can check if you have a SIM card inserted, or via Web UI**
51 +**//Below command can check if you have a SIM card inserted, or via Web UI//**
52 52  
53 -* Make sure to Power Off when you insert the SIM card and power on the device. The device doesn't support auto-detect SIM card on power on
54 -* Make sure you have the correct direction to insert the SIM card. Every device has an example photo in the manual for the direction.
53 +* //Make sure to Power Off when you insert the SIM card and power on the device. The device doesn't support auto-detect SIM card on power on//
54 +* //Make sure you have the correct direction to insert the SIM card. Every device has an example photo in the manual for the direction.//
55 55  
56 56  (% class="box" %)
57 57  (((
... ... @@ -68,10 +68,10 @@
68 68  
69 69  
70 70  (% class="wikigeneratedid" %)
71 -**​​(% style="color:red" %)Note:(%%)**(% style="color:red" %) **If the icon is missing some information, like SIM, Network, or Signal, which may be due to the display bug.**
71 +//**​​(% style="color:red" %)Note:(%%)**(% style="color:red" %) **If the icon is missing some information, like SIM, Network, or Signal, which may be due to the display bug.**//
72 72  
73 73  (% class="wikigeneratedid" %)
74 -Please check the IP address is displayed and the Internet displays "OK", it works properly.
74 +//Please check the IP address is displayed and the Internet displays "OK", it works properly.//
75 75  
76 76  (% class="wikigeneratedid" %)
77 77  [[image:image-20220527153827-5.png]]
... ... @@ -80,7 +80,7 @@
80 80  == 2.3 Check dialing info ==
81 81  
82 82  
83 -run "**logread -f**" in gateway CLI。
83 +//run "**logread -f**" in gateway CLI。//
84 84  
85 85  (% class="box" %)
86 86  (((
... ... @@ -128,10 +128,11 @@
128 128  === 2.4.1 The gateway can read the SIM card, But the Internet is displayed as Fail. ===
129 129  
130 130  
131 -Users can check whether the APN matched by the SIM card is correct.
131 +//Users can check whether the APN matched by the SIM card is correct.//
132 132  
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.
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  
... ... @@ -138,8 +138,9 @@
138 138  === 2.4.2 The gateway can read the SIM card, But the Internet is displayed as Fail, and at the same time Network displays the carrier network. ===
139 139  
140 140  
141 -It should be SIM card no flow, users can insert SIM cards into the mobile phone for testing.
142 +//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  
... ... @@ -146,8 +146,9 @@
146 146  === 2.4.3 The gateway can't read the SIM card, and the Internet is displayed as Fail. ===
147 147  
148 148  
149 -Users need to check whether the SIM card type is suitable for the EC25 module.
151 +//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  
... ... @@ -154,8 +154,9 @@
154 154  === 2.4.4 SIM display:~*~**SIM ERROR~*~** Check SIM is inserted test SIM in a mobile phone? ===
155 155  
156 156  
157 -Users can insert SIM cards into the mobile phone for testing.
160 +//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  
... ... @@ -163,7 +163,7 @@
163 163  
164 164  
165 165  (((
166 -By default, the Cellular Network won't be shared with the WiFi or LAN clients. If users need to share with them, the user can modify the file.
170 +//By default, the Cellular Network won't be shared with the WiFi or LAN clients. If users need to share with them, the user can modify the file.//
167 167  )))
168 168  
169 169  (% class="box" %)
... ... @@ -200,17 +200,18 @@
200 200  )))
201 201  
202 202  (((
203 -and run **/etc/init.d/firewall reload** or **reboot the device**.
207 +//and run **/etc/init.d/firewall reload** or reboot the device.//
204 204  
205 205  
206 206  = 4. Switching between Cellular and Ethernet and Wi-Fi networks =
207 207  
208 208  
209 -By default, Cell is the backup WAN where the Ethernet or Wi-Fi network is used first if they are available.
213 +//By default, Cell is the backup WAN where the Ethernet or Wi-Fi network is used first if they are available.//
210 210  
211 -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.
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.//
212 212  
213 213  
218 +
214 214  **Enable Cellular and connect Ethernet at the same time**
215 215  
216 216  ETH icon is displayed as ​​​ [[image:1658135519305-444.png||height="18" width="19"]] Indicates that Ethernet is the main working network.
... ... @@ -221,12 +221,12 @@
221 221  == 4.1 Switching between Cellular and Ethernet networks ==
222 222  
223 223  
224 -When connecting to the AP WiFI of the gateway, users can access the Web UI of the gateway through the default address 10.130.1.1
229 +//When connecting to the AP WiFI of the gateway, users can access the Web UI of the gateway through the default address 10.130.1.1//
225 225  
226 226  [[image:image-20220606140622-2.png||height="664" width="1106"]]
227 227  
228 228  
229 -**Remove the network cable from the WAN port on the gateway, the gateway will switch to a Cellular network.**
234 +//**Remove the network cable from the WAN port on the gateway, the gateway will switch to a Cellular network.**//
230 230  
231 231  [[image:image-20220606140859-4.png||height="687" width="1107"]]
232 232  
... ... @@ -236,17 +236,17 @@
236 236  
237 237  
238 238  (% class="wikigeneratedid" %)
239 -Enable **Cellular** and connect **WiFi** at the same time
244 +//Enable **Cellular** and connect **WiFi** at the same time//
240 240  
241 -WiFi icon is displayed as ​​​[[image:1658135519305-444.png||height="23" width="24"]] Indicates that WiFi is the main working network.
246 +//WiFi icon is displayed as ​​​//[[image:1658135519305-444.png||height="23" width="24"]] Indicates that WiFi is the main working network.
242 242  
243 -Cell icon is displayed as  [[image:1658135500498-725.png||height="23" width="22"]] Indicates that Cellular is the backup WAN.
248 +//Cell icon is displayed as  //[[image:1658135500498-725.png||height="23" width="22"]]// Indicates that Cellular is the backup WAN.//
244 244  
245 245  
246 246  [[image:image-20220606141113-7.png||height="678" width="1106"]]
247 247  
248 248  
249 -**Close the WiFi WAN, the gateway will switch to a Cellular network.**
254 +//**Close the WiFi WAN, the gateway will switch to a Cellular network.**//
250 250  
251 251  [[image:image-20220606140932-5.png||height="687" width="1107"]]
252 252  
... ... @@ -261,44 +261,29 @@
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 **
274 +**root@dragino-1b7c4c:~~# comgt -d /dev/ttyModemAT -s /etc/gcom/getimsi.gcom **
272 272  )))
273 273  
274 -[[image:image-20231218095203-4.png]]
277 +[[image:image-20221027140604-1.png||height="330" width="707"]]
275 275  
276 276  
277 -[[image:image-20231218095426-6.jpeg||height="466" width="990"]]
280 +[[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  
296 -Users can access the gateway CLI and run the minicom command to get the configuration interface.
286 +//Users can access the gateway CLI and run the minicom command to get the configuration interface.//
297 297  
298 298  (((
299 299  
300 300  
301 -**Enter the minicom command, then select the option ''serial port setup".**
291 +**//Enter the minicom command, then select the option ''serial port setup".//**
302 302  )))
303 303  
304 304  (% class="box infomessage" %)
... ... @@ -319,7 +319,7 @@
319 319  )))
320 320  
321 321  
322 -(% style="color:red" %)**Note: Enter the corresponding letter to change the configuration, like A,B,C**
312 +(% style="color:red" %)//**Note: Enter the corresponding letter to change the configuration, like A,B,C**//
323 323  
324 324  [[image:image-20220527154154-7.png]]
325 325  
... ... @@ -328,11 +328,11 @@
328 328  
329 329  
330 330  (((
331 -Enter (% style="color:blue" %)**AT+GSN **(%%)in the interface to get the IMEI,
321 +//Enter (% style="color:blue" %)**AT+GSN **(%%)in the interface to get the IMEI,//
332 332  )))
333 333  
334 334  (((
335 -**For example: (% style="color:#037691" %)860548042566627(%%)**
325 +//**For example: (% style="color:#037691" %)860548042566627(%%)**//
336 336  )))
337 337  
338 338  (% class="box infomessage" %)
... ... @@ -349,11 +349,11 @@
349 349  
350 350  
351 351  (((
352 -Enter (% style="color:blue" %)**AT+QCCID **(%%)in the interface to get the ICCID,
342 +//Enter (% style="color:blue" %)**AT+QCCID **(%%)in the interface to get the ICCID,//
353 353  )))
354 354  
355 355  (((
356 -**For example: (% style="color:#037691" %)89860118005400261748(%%)**
346 +//**For example: (% style="color:#037691" %)89860118005400261748(%%)**//
357 357  
358 358  (% class="box infomessage" %)
359 359  (((
... ... @@ -369,22 +369,22 @@
369 369  == 6.1 Introduction ==
370 370  
371 371  
372 -(% style="color:red" %)**Prerequisite: Requires a USB 4G Dongle and a supported gateway firmware**
362 +(% style="color:red" %)**//Prerequisite: Requires a USB 4G Dongle and a supported gateway firmware//**
373 373  
374 374  (((
375 -This introduces a setup and configured gateway for using a USB 3g/UMTS-modem for WAN connection.
365 +//This introduces a setup and configured gateway for using a USB 3g/UMTS-modem for WAN connection.//
376 376  
377 377  
378 378  )))
379 379  
380 380  (((
381 -Many modes (and most **LTE**) USB modems provide **qmi**, **mbim**, **ncm**, **rndis** protocol for connection instead of legacy **ppp** protocol, they are faster and better, overall recommended.
371 +//Many modes (and most **LTE**) USB modems provide **qmi**, **mbim**, **ncm**, **rndis** protocol for connection instead of legacy **ppp** protocol, they are faster and better, overall recommended.//
382 382  )))
383 383  
384 384  (((
385 -This is not beginner-friendly due to too many protocols.
375 +//This is not beginner-friendly due to too many protocols.//
386 386  
387 -For more information: [[https:~~/~~/openwrt.org/docs/guide-user/network/wan/wwan/3gdongle>>url:https://openwrt.org/docs/guide-user/network/wan/wwan/3gdongle]]
377 +//For more information: [[https:~~/~~/openwrt.org/docs/guide-user/network/wan/wwan/3gdongle>>url:https://openwrt.org/docs/guide-user/network/wan/wwan/3gdongle]]//
388 388  
389 389  
390 390  )))
... ... @@ -392,10 +392,10 @@
392 392  == 6.2 How to use the USB Dongle at the gateway ==
393 393  
394 394  
395 -Most of the products can be used on the gateway, but because their protocols are different, they are not used in the same way.
385 +//Most of the products can be used on the gateway, but because their protocols are different, they are not used in the same way.//
396 396  
397 397  (((
398 -For example, the Huawei-E3372/E8372 is using **Hilink mode** or **NCM mode**.
388 +//For example, the Huawei-E3372/E8372 is using **Hilink mode** or **NCM mode**.//
399 399  )))
400 400  
401 401  (% class="box" %)
... ... @@ -419,15 +419,15 @@
419 419  
420 420  
421 421  (((
422 -USB-Dongle plugs into the gateway USB port
412 +//USB-Dongle plugs into the gateway USB port//
423 423  )))
424 424  
425 425  (((
426 -Check the USB module via command (% style="color:#037691" %)**lsusb**
416 +//Check the USB module via command (% style="color:#037691" %)**lsusb**//
427 427  )))
428 428  
429 429  (((
430 -(% style="color:red" %)**Note: Users need to that connect to the gateway command line via ssh.**
420 +(% style="color:red" %)//**Note: Users need to that connect to the gateway command line via ssh.**//
431 431  )))
432 432  
433 433  [[image:image-20220527154739-9.png]]
... ... @@ -436,7 +436,7 @@
436 436  === 6.3.2 Detection of new network interfaces added ===
437 437  
438 438  
439 -Check network configuration command line input:
429 +//Check network configuration command line input: //
440 440  
441 441  (% class="box infomessage" %)
442 442  (((
... ... @@ -447,9 +447,9 @@
447 447  
448 448  [[image:image-20220527154822-10.png]]
449 449  
450 -In the command, the output user can see that the new interface added is (% style="color:#037691" %)**eth2**
440 +//In the command, the output user can see that the new interface added is (% style="color:#037691" %)**eth2**//
451 451  
452 -Usually, the user can see that the new interface added is (% style="color:#037691" %)**eth2** (% style="color:black" %)or (% style="color:#037691" %)**wwan0**
442 +//Usually, the user can see that the new interface added is (% style="color:#037691" %)**eth2** (% style="color:black" %)or (% style="color:#037691" %)**wwan0**//
453 453  
454 454  
455 455  === 6.3.3 Add the new interface to the network configuration. ===
... ... @@ -477,7 +477,7 @@
477 477  
478 478  [[image:image-20220527155013-12.png]]
479 479  
480 -Now, Gateway is configured to access the internet on the LTE network.
470 +//Now, Gateway is configured to access the internet on the LTE network.//
481 481  
482 482  
483 483  == 6.4 NCM mode ==
... ... @@ -488,69 +488,48 @@
488 488  === 6.5.1 The USB-Dongle interface cannot obtain the IP address. ===
489 489  
490 490  
491 -Please try this USB dongle to access the internet on your PC, to make sure this USB dongle can normally access the internet.
481 +//Please try this USB dongle to access the internet on your PC, to make sure this USB dongle can normally access the internet.//
492 492  
493 493  
494 494  = 7. How to reduce data traffic =
495 495  
496 -== 7.1 How the gateway will consume data traffic ==
486 +== 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)
489 +**//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  
492 +//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:
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 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  
500 +//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.
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 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.
504 +[[image:image-20220527155358-16.png]]
524 524  
525 -[[image:image-20220527155229-15.png||height="511" width="986"]]
506 +//System General interface//
526 526  
527 527  
528 -=== 7.1.3 Auto update ===
509 +[[image:image-20220527155229-15.png]]
529 529  
511 +//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  
514 +== 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 ==
520 +== 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:
... ... @@ -568,7 +568,6 @@
568 568  
569 569  [[image:image-20221124135102-2.png]]
570 570  
571 -
572 572  4. View the graphs and statistics using by going to **Statistics > Graphs** **> Interfaces > 3g-cellullar**
573 573  
574 574  [[image:image-20221124134927-1.png]]
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
Copyright ©2010-2022 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0