<
From version < 92.1 >
edited by Kilight Cao
on 2023/12/18 09:52
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
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Kilight
1 +XWiki.Xiaoling
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,9 +128,9 @@
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  
136 136  [[image:image-20220718155937-1.png||height="562" width="497"]]
... ... @@ -139,7 +139,7 @@
139 139  === 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. ===
140 140  
141 141  
142 -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.//
143 143  
144 144  
145 145  [[image:1658131428288-728.png||height="538" width="494"]]
... ... @@ -148,7 +148,7 @@
148 148  === 2.4.3 The gateway can't read the SIM card, and the Internet is displayed as Fail. ===
149 149  
150 150  
151 -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.//
152 152  
153 153  
154 154  [[image:1658131612484-845.png||height="549" width="499"]]
... ... @@ -157,7 +157,7 @@
157 157  === 2.4.4 SIM display:~*~**SIM ERROR~*~** Check SIM is inserted test SIM in a mobile phone? ===
158 158  
159 159  
160 -Users can insert SIM cards into the mobile phone for testing.
160 +//Users can insert SIM cards into the mobile phone for testing.//
161 161  
162 162  
163 163  [[image:image-20220718160804-3.png||height="602" width="500"]]
... ... @@ -167,7 +167,7 @@
167 167  
168 168  
169 169  (((
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.
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.//
171 171  )))
172 172  
173 173  (% class="box" %)
... ... @@ -204,17 +204,18 @@
204 204  )))
205 205  
206 206  (((
207 -and run **/etc/init.d/firewall reload** or **reboot the device**.
207 +//and run **/etc/init.d/firewall reload** or reboot the device.//
208 208  
209 209  
210 210  = 4. Switching between Cellular and Ethernet and Wi-Fi networks =
211 211  
212 212  
213 -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.//
214 214  
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.
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 +
218 218  **Enable Cellular and connect Ethernet at the same time**
219 219  
220 220  ETH icon is displayed as ​​​ [[image:1658135519305-444.png||height="18" width="19"]] Indicates that Ethernet is the main working network.
... ... @@ -225,12 +225,12 @@
225 225  == 4.1 Switching between Cellular and Ethernet networks ==
226 226  
227 227  
228 -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//
229 229  
230 230  [[image:image-20220606140622-2.png||height="664" width="1106"]]
231 231  
232 232  
233 -**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.**//
234 234  
235 235  [[image:image-20220606140859-4.png||height="687" width="1107"]]
236 236  
... ... @@ -240,17 +240,17 @@
240 240  
241 241  
242 242  (% class="wikigeneratedid" %)
243 -Enable **Cellular** and connect **WiFi** at the same time
244 +//Enable **Cellular** and connect **WiFi** at the same time//
244 244  
245 -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.
246 246  
247 -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.//
248 248  
249 249  
250 250  [[image:image-20220606141113-7.png||height="678" width="1106"]]
251 251  
252 252  
253 -**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.**//
254 254  
255 255  [[image:image-20220606140932-5.png||height="687" width="1107"]]
256 256  
... ... @@ -282,12 +282,12 @@
282 282  == **How does the gateway access the Quetel module directly (to send AT commands)** ==
283 283  
284 284  
285 -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.//
286 286  
287 287  (((
288 288  
289 289  
290 -**Enter the minicom command, then select the option ''serial port setup".**
291 +**//Enter the minicom command, then select the option ''serial port setup".//**
291 291  )))
292 292  
293 293  (% class="box infomessage" %)
... ... @@ -308,7 +308,7 @@
308 308  )))
309 309  
310 310  
311 -(% 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**//
312 312  
313 313  [[image:image-20220527154154-7.png]]
314 314  
... ... @@ -317,11 +317,11 @@
317 317  
318 318  
319 319  (((
320 -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,//
321 321  )))
322 322  
323 323  (((
324 -**For example: (% style="color:#037691" %)860548042566627(%%)**
325 +//**For example: (% style="color:#037691" %)860548042566627(%%)**//
325 325  )))
326 326  
327 327  (% class="box infomessage" %)
... ... @@ -338,11 +338,11 @@
338 338  
339 339  
340 340  (((
341 -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,//
342 342  )))
343 343  
344 344  (((
345 -**For example: (% style="color:#037691" %)89860118005400261748(%%)**
346 +//**For example: (% style="color:#037691" %)89860118005400261748(%%)**//
346 346  
347 347  (% class="box infomessage" %)
348 348  (((
... ... @@ -358,22 +358,22 @@
358 358  == 6.1 Introduction ==
359 359  
360 360  
361 -(% 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//**
362 362  
363 363  (((
364 -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.//
365 365  
366 366  
367 367  )))
368 368  
369 369  (((
370 -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.//
371 371  )))
372 372  
373 373  (((
374 -This is not beginner-friendly due to too many protocols.
375 +//This is not beginner-friendly due to too many protocols.//
375 375  
376 -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]]//
377 377  
378 378  
379 379  )))
... ... @@ -381,10 +381,10 @@
381 381  == 6.2 How to use the USB Dongle at the gateway ==
382 382  
383 383  
384 -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.//
385 385  
386 386  (((
387 -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**.//
388 388  )))
389 389  
390 390  (% class="box" %)
... ... @@ -408,15 +408,15 @@
408 408  
409 409  
410 410  (((
411 -USB-Dongle plugs into the gateway USB port
412 +//USB-Dongle plugs into the gateway USB port//
412 412  )))
413 413  
414 414  (((
415 -Check the USB module via command (% style="color:#037691" %)**lsusb**
416 +//Check the USB module via command (% style="color:#037691" %)**lsusb**//
416 416  )))
417 417  
418 418  (((
419 -(% 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.**//
420 420  )))
421 421  
422 422  [[image:image-20220527154739-9.png]]
... ... @@ -425,7 +425,7 @@
425 425  === 6.3.2 Detection of new network interfaces added ===
426 426  
427 427  
428 -Check network configuration command line input:
429 +//Check network configuration command line input: //
429 429  
430 430  (% class="box infomessage" %)
431 431  (((
... ... @@ -436,9 +436,9 @@
436 436  
437 437  [[image:image-20220527154822-10.png]]
438 438  
439 -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**//
440 440  
441 -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**//
442 442  
443 443  
444 444  === 6.3.3 Add the new interface to the network configuration. ===
... ... @@ -466,7 +466,7 @@
466 466  
467 467  [[image:image-20220527155013-12.png]]
468 468  
469 -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.//
470 470  
471 471  
472 472  == 6.4 NCM mode ==
... ... @@ -477,65 +477,48 @@
477 477  === 6.5.1 The USB-Dongle interface cannot obtain the IP address. ===
478 478  
479 479  
480 -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.//
481 481  
482 482  
483 483  = 7. How to reduce data traffic =
484 484  
485 -== 7.1 How the gateway will consume data traffic ==
486 +== 7.1 Reduce Status Uplink Interval ==
486 486  
487 -Below list the place where the data traffic will use.
488 488  
489 -* Valid uplink data to LoRaWAN server or IoT server. ( We can't reduce this as they are the data we want)
490 -* Invalid uplink sensor data to LoRaWAN serevr. ( See Filter unwanted packets)
491 -* LoRaWAN Status push or polling data to LoRaWAN server . ( We can reduce this part , see below for discussion)
492 -* System Keep Alive data. ( To ensure the system is more robust, can be disabled)
493 -* system Time synchronization Checking
494 -* Auto update ( Software auto update, can be disabled)
489 +**//The gateways will use the data traffic below two places.//**
495 495  
496 -=== 7.1.1 LoRaWAN Status push or polling data to LoRaWAN server ===
497 497  
498 -When gateway connect to LoRaWAN server via LoRaWAN protocol, besides the sensor data uplink/downlink. gateway will still need to:
492 +//1. There is the data traffic from LoRa package Forward which were the gateway status package and sensor end node uplink/downlink.//
499 499  
500 -* Uplink self-status to the LoRaWAN server every 30s. the users can adjust **Keep Alive Period** as below
501 -* 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.
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.//
502 502  
503 503  [[image:image-20220527155108-13.png]]
504 504  
505 505  
506 -=== 7.1.2 System Keep Alive data ===
507 507  
508 -System Keep Alive Data is used to check gateway-network status and fix possible issue. Gateway will check every 15 seconds and generate traffic.
500 +//2. There is the data traffic from the gateway check self-network status. by default, the gateway will check the network per 15s.//
509 509  
510 -Base on 15 seconds per check, the data traffic is about 2M data traffic per day. Users can adjust **Keepalive Interval** as below.
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.//
511 511  
512 -[[image:image-20220527155229-15.png||height="511" width="986"]]
504 +[[image:image-20220527155358-16.png]]
513 513  
506 +//System General interface//
514 514  
515 -=== 7.1.3 Auto update ===
516 516  
517 -Gateway will check for update every day for new configure or software. User can disable them by below method.
509 +[[image:image-20220527155229-15.png]]
518 518  
511 +//Keepalive script interval time settings//
519 519  
520 -=== 7.1.4 Filter unwanted packets ===
521 521  
522 -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.
514 +== 7.2 Filter unwanted packets ==
523 523  
516 +
524 524  See [[How to filter unwanted packets>>doc:Main.Filter unwanted LoRaWAN packets.WebHome]]
525 525  
526 526  
527 -== 7.2 Usage statistics ==
520 +== 7.3 Usage statistics ==
528 528  
529 529  
530 -=== 7.2.1 How does Openwrt usage statistics ===
531 -
532 -This is a general instruction for the use of Openwrt of Dragino devices. Current models include:
533 -
534 -* LPS8,LPS8N
535 -* LG308,LG308N
536 -* DLOS8,DLOS8N
537 -* LIG16
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:
... ... @@ -553,7 +553,6 @@
553 553  
554 554  [[image:image-20221124135102-2.png]]
555 555  
556 -
557 557  4. View the graphs and statistics using by going to **Statistics > Graphs** **> Interfaces > 3g-cellullar**
558 558  
559 559  [[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
Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0