Last modified by Kilight Cao on 2024/12/31 16:38
<
From version < 98.1 >
edited by Kilight Cao
on 2024/07/12 13:54
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,14 +48,13 @@
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  (((
58 -(% class="mark" %)**For Models: LPS8N, LG308N, DLOS8N**(%%)
59 59  //root@dragino-1dadd8:~~# **comgt -d /dev/ttyUSB3**
60 60  SIM ready
61 61  Waiting for Registration..(120 sec max)
... ... @@ -69,10 +69,10 @@
69 69  
70 70  
71 71  (% class="wikigeneratedid" %)
72 -**​​(% 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.**//
73 73  
74 74  (% class="wikigeneratedid" %)
75 -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.//
76 76  
77 77  (% class="wikigeneratedid" %)
78 78  [[image:image-20220527153827-5.png]]
... ... @@ -81,7 +81,7 @@
81 81  == 2.3 Check dialing info ==
82 82  
83 83  
84 -run "**logread -f**" in gateway CLI。
83 +//run "**logread -f**" in gateway CLI。//
85 85  
86 86  (% class="box" %)
87 87  (((
... ... @@ -129,10 +129,11 @@
129 129  === 2.4.1 The gateway can read the SIM card, But the Internet is displayed as Fail. ===
130 130  
131 131  
132 -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.//
133 133  
134 -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.//
135 135  
135 +
136 136  [[image:image-20220718155937-1.png||height="562" width="497"]]
137 137  
138 138  
... ... @@ -139,8 +139,9 @@
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 144  [[image:1658131428288-728.png||height="538" width="494"]]
145 145  
146 146  
... ... @@ -147,8 +147,9 @@
147 147  === 2.4.3 The gateway can't read the SIM card, and the Internet is displayed as Fail. ===
148 148  
149 149  
150 -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.//
151 151  
153 +
152 152  [[image:1658131612484-845.png||height="549" width="499"]]
153 153  
154 154  
... ... @@ -155,8 +155,9 @@
155 155  === 2.4.4 SIM display：~*~**SIM ERROR~*~** Check SIM is inserted test SIM in a mobile phone？ ===
156 156  
157 157  
158 -Users can insert SIM cards into the mobile phone for testing.
160 +//Users can insert SIM cards into the mobile phone for testing.//
159 159  
162 +
160 160  [[image:image-20220718160804-3.png||height="602" width="500"]]
161 161  
162 162  
... ... @@ -164,7 +164,7 @@
164 164  
165 165  
166 166  (((
167 -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.//
168 168  )))
169 169  
170 170  (% class="box" %)
... ... @@ -201,17 +201,18 @@
201 201  )))
202 202  
203 203  (((
204 -and run **/etc/init.d/firewall reload** or **reboot the device**.
207 +//and run **/etc/init.d/firewall reload** or reboot the device.//
205 205  
206 206  
207 207  = 4. Switching between Cellular and Ethernet and Wi-Fi networks =
208 208  
209 209  
210 -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.//
211 211  
212 -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.//
213 213  
214 214  
218 +
215 215  **Enable Cellular and connect Ethernet at the same time**
216 216  
217 217  ETH icon is displayed as ​​​ [[image:1658135519305-444.png||height="18" width="19"]] Indicates that Ethernet is the main working network.
... ... @@ -222,12 +222,12 @@
222 222  == 4.1 Switching between Cellular and Ethernet networks ==
223 223  
224 224  
225 -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//
226 226  
227 227  [[image:image-20220606140622-2.png||height="664" width="1106"]]
228 228  
229 229  
230 -**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.**//
231 231  
232 232  [[image:image-20220606140859-4.png||height="687" width="1107"]]
233 233  
... ... @@ -237,17 +237,17 @@
237 237  
238 238  
239 239  (% class="wikigeneratedid" %)
240 -Enable **Cellular** and connect **WiFi** at the same time
244 +//Enable **Cellular** and connect **WiFi** at the same time//
241 241  
242 -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.
243 243  
244 -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.//
245 245  
246 246  
247 247  [[image:image-20220606141113-7.png||height="678" width="1106"]]
248 248  
249 249  
250 -**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.**//
251 251  
252 252  [[image:image-20220606140932-5.png||height="687" width="1107"]]
253 253  
... ... @@ -262,44 +262,29 @@
262 262  
263 263  = 5. How does the gateway view the International Mobile Equipment Identity (IMEI) =
264 264  
265 -== For LIG16,LPS8, LPS8N, LG308, LG308N, DLOS8, DLOS8N view the International Mobile Equipment Identity (IMEI) ==
266 266  
267 -
268 268  Users can get the IMEI via Linux command, but you have to access the gateway CLI.
269 269  
270 270  (% class="box infomessage" %)
271 271  (((
272 -**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 **
273 273  )))
274 274  
275 -[[image:image-20231218095203-4.png]]
277 +[[image:image-20221027140604-1.png||height="330" width="707"]]
276 276  
277 277  
278 -[[image:image-20231218095426-6.jpeg||height="466" width="990"]]
280 +[[image:image-20221027151146-2.png||height="554" width="1000"]]
279 279  
280 280  
281 -== For LPS8v2 view the International Mobile Equipment Identity (IMEI) ==
283 +== **How does the gateway access the Quetel module directly (to send AT commands)** ==
282 282  
283 -(% class="box infomessage" %)
284 -(((
285 -**root@dragino-e4e891:~~# /usr/local/dragino/cell/getinfo.sh**
286 -)))
287 287  
288 -[[image:image-20231218094526-1.png]]
286 +//Users can access the gateway CLI and run the minicom command to get the configuration interface.//
289 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 -
297 -Users can access the gateway CLI and run the minicom command to get the configuration interface.
298 -
299 299  (((
300 300  
301 301  
302 -**Enter the minicom command, then select the option ''serial port setup".**
291 +**//Enter the minicom command, then select the option ''serial port setup".//**
303 303  )))
304 304  
305 305  (% class="box infomessage" %)
... ... @@ -320,20 +320,20 @@
320 320  )))
321 321  
322 322  
323 -(% 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**//
324 324  
325 325  [[image:image-20220527154154-7.png]]
326 326  
327 327  
328 -== International Mobile Equipment Identity (IMEI) ==
317 +=== **International Mobile Equipment Identity (IMEI)** ===
329 329  
330 330  
331 331  (((
332 -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,//
333 333  )))
334 334  
335 335  (((
336 -**For example: (% style="color:#037691" %)860548042566627(%%)**
325 +//**For example: (% style="color:#037691" %)860548042566627(%%)**//
337 337  )))
338 338  
339 339  (% class="box infomessage" %)
... ... @@ -346,15 +346,15 @@
346 346  [[image:image-20220527154231-8.png]]
347 347  
348 348  
349 -== Integrated Circuit Card Identifier (ICCID) ==
338 +=== **Integrated Circuit Card Identifier (ICCID)** ===
350 350  
351 351  
352 352  (((
353 -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,//
354 354  )))
355 355  
356 356  (((
357 -**For example: (% style="color:#037691" %)89860118005400261748(%%)**
346 +//**For example: (% style="color:#037691" %)89860118005400261748(%%)**//
358 358  
359 359  (% class="box infomessage" %)
360 360  (((
... ... @@ -370,22 +370,22 @@
370 370  == 6.1 Introduction ==
371 371  
372 372  
373 -(% 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//**
374 374  
375 375  (((
376 -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.//
377 377  
378 378  
379 379  )))
380 380  
381 381  (((
382 -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.//
383 383  )))
384 384  
385 385  (((
386 -This is not beginner-friendly due to too many protocols.
375 +//This is not beginner-friendly due to too many protocols.//
387 387  
388 -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]]//
389 389  
390 390  
391 391  )))
... ... @@ -393,10 +393,10 @@
393 393  == 6.2 How to use the USB Dongle at the gateway ==
394 394  
395 395  
396 -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.//
397 397  
398 398  (((
399 -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**.//
400 400  )))
401 401  
402 402  (% class="box" %)
... ... @@ -420,15 +420,15 @@
420 420  
421 421  
422 422  (((
423 -USB-Dongle plugs into the gateway USB port
412 +//USB-Dongle plugs into the gateway USB port//
424 424  )))
425 425  
426 426  (((
427 -Check the USB module via command (% style="color:#037691" %)**lsusb**
416 +//Check the USB module via command (% style="color:#037691" %)**lsusb**//
428 428  )))
429 429  
430 430  (((
431 -(% 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.**//
432 432  )))
433 433  
434 434  [[image:image-20220527154739-9.png]]
... ... @@ -437,7 +437,7 @@
437 437  === 6.3.2 Detection of new network interfaces added ===
438 438  
439 439  
440 -Check network configuration command line input:
429 +//Check network configuration command line input: //
441 441  
442 442  (% class="box infomessage" %)
443 443  (((
... ... @@ -448,9 +448,9 @@
448 448  
449 449  [[image:image-20220527154822-10.png]]
450 450  
451 -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**//
452 452  
453 -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**//
454 454  
455 455  
456 456  === 6.3.3 Add the new interface to the network configuration. ===
... ... @@ -478,7 +478,7 @@
478 478  
479 479  [[image:image-20220527155013-12.png]]
480 480  
481 -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.//
482 482  
483 483  
484 484  == 6.4 NCM mode ==
... ... @@ -489,69 +489,48 @@
489 489  === 6.5.1 The USB-Dongle interface cannot obtain the IP address. ===
490 490  
491 491  
492 -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.//
493 493  
494 494  
495 495  = 7. How to reduce data traffic =
496 496  
497 -== 7.1 How the gateway will consume data traffic ==
486 +== 7.1 Reduce Status Uplink Interval ==
498 498  
499 -Below list the place where the data traffic will use.
500 500  
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)
489 +**//The gateways will use the data traffic below two places.//**
507 507  
508 -=== 7.1.1 LoRaWAN Status push or polling data to LoRaWAN server ===
509 509  
492 +//1. There is the data traffic from LoRa package Forward which were the gateway status package and sensor end node uplink/downlink.//
510 510  
511 -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.//
512 512  
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 -
516 516  [[image:image-20220527155108-13.png]]
517 517  
518 518  
519 -=== 7.1.2 System Keep Alive data ===
520 520  
500 +//2. There is the data traffic from the gateway check self-network status. by default, the gateway will check the network per 15s.//
521 521  
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.
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.//
523 523  
524 -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]]
525 525  
526 -[[image:image-20220527155229-15.png||height="511" width="986"]]
506 +//System General interface//
527 527  
528 528  
529 -=== 7.1.3 Auto update ===
509 +[[image:image-20220527155229-15.png]]
530 530  
511 +//Keepalive script interval time settings//
531 531  
532 -Gateway will check for update every day for new configure or software. User can disable them by below method.
533 533  
514 +== 7.2 Filter unwanted packets ==
534 534  
535 -=== 7.1.4 Filter unwanted packets ===
536 536  
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 -
540 540  See [[How to filter unwanted packets>>doc:Main.Filter unwanted LoRaWAN packets.WebHome]]
541 541  
542 542  
543 -== 7.2 Usage statistics ==
520 +== 7.3 Usage statistics ==
544 544  
545 -=== 7.2.1 How does Openwrt usage statistics ===
546 546  
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 -
555 555  ~1. Activate LuCI and connect to SSH following [[these instructions>>doc:Main.Install Luci in the new UI firmware.WebHome]]
556 556  
557 557  2. Install luci-app-statistics using the following terminal commands:
... ... @@ -569,7 +569,6 @@
569 569  
570 570  [[image:image-20221124135102-2.png]]
571 571  
572 -
573 573  4. View the graphs and statistics using by going to **Statistics > Graphs** **> Interfaces > 3g-cellullar**
574 574  
575 575  [[image:image-20221124134927-1.png]]
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