Last modified by Xiaoling on 2024/03/02 08:51
Show last authors
1
2
3 **Table of Contents：**
4
5 {{toc/}}
6
7
8
9 = 1. Enable Cellular Connection =
10
11
12 If your device has a Cellular module, you can see the below screenshot. enable the cellular connection here.
13
14 [[image:image-20220601110850-2.png]]
15
16 **//Enable Cellular Connection//**
17
18
19 (((
20 If your device doesn't have a cellular module, you will see a cellular module not detected.
21 )))
22
23 [[image:image-20220527153544-2.png]]
24
25
26 = 2. How to Debug if Cellular connection fails =
27
28
29 If there is a problem with the cellular connection. Please check the below points:
30
31
32 == 2.1 Do you order the model with a cellular option ==
33
34
35 Make sure you order the model with the cellular option. Can check by command or via the Web UI.
36
37 (% class="box" %)
38 (((
39 //root@dragino-1bbd90:~~# lsusb
40 Bus 001 Device 004: ID 2c7c:0125      ~-~-> This is the Cellular module
41 Bus 001 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub
42 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub//
43 )))
44
45 [[image:image-20220601110748-1.png]]
46
47
48 == 2.2 Do you input the SIM card correctly ==
49
50
51 **Below command can check if you have a SIM card inserted, or via Web UI**
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.
55
56 (% class="box" %)
57 (((
58 (% class="mark" %)**For Models: LPS8N, LG308N, DLOS8N**(%%)
59 //root@dragino-1dadd8:~~# **comgt -d /dev/ttyUSB3**
60 SIM ready
61 Waiting for Registration..(120 sec max)
62 Registered on Home network: "CHN-UNICOM",7
63 Signal Quality: 10,99//
64 )))
65
66
67 (% class="wikigeneratedid" %)
68 [[image:image-20220527153804-4.png]]
69
70
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.**
73
74 (% class="wikigeneratedid" %)
75 Please check the IP address is displayed and the Internet displays "OK", it works properly.
76
77 (% class="wikigeneratedid" %)
78 [[image:image-20220527153827-5.png]]
79
80
81 == 2.3 Check dialing info ==
82
83
84 run "**logread -f**" in gateway CLI。
85
86 (% class="box" %)
87 (((
88 Fri Feb  7 01:20:28 2020 daemon.notice pppd[29452]: pppd 2.4.7 started by root, uid 0
89 Fri Feb  7 01:20:29 2020 user.notice iot_keep_alive: Ping WAN
90 Fri Feb  7 01:20:29 2020 user.notice iot_keep_alive: Default interface is
91 Fri Feb  7 01:20:29 2020 user.notice iot_keep_alive: No internet at any interface
92 Fri Feb  7 01:20:29 2020 local2.info chat[29485]: abort on (BUSY)
93 Fri Feb  7 01:20:29 2020 local2.info chat[29485]: abort on (NO CARRIER)
94 Fri Feb  7 01:20:29 2020 local2.info chat[29485]: abort on (ERROR)
95 Fri Feb  7 01:20:29 2020 local2.info chat[29485]: report (CONNECT)
96 Fri Feb  7 01:20:29 2020 local2.info chat[29485]: timeout set to 10 seconds
97 Fri Feb  7 01:20:29 2020 local2.info chat[29485]: send (AT&F^M)
98 Fri Feb  7 01:20:29 2020 local2.info chat[29485]: expect (OK)
99 Fri Feb  7 01:20:29 2020 local2.info chat[29485]: AT&F^M^M
100 Fri Feb  7 01:20:29 2020 local2.info chat[29485]: OK
101 Fri Feb  7 01:20:29 2020 local2.info chat[29485]:  ~-~- got it
102 Fri Feb  7 01:20:29 2020 local2.info chat[29485]: send (ATE1^M)
103 Fri Feb  7 01:20:29 2020 local2.info chat[29485]: expect (OK)
104 Fri Feb  7 01:20:29 2020 local2.info chat[29485]: ^M
105 Fri Feb  7 01:20:29 2020 local2.info chat[29485]: ATE1^M^M
106 Fri Feb  7 01:20:29 2020 local2.info chat[29485]: OK
107 Fri Feb  7 01:20:29 2020 local2.info chat[29485]:  ~-~- got it
108 Fri Feb  7 01:20:29 2020 local2.info chat[29485]: send (AT+CGDCONT=1,"IP",""^M)
109 Fri Feb  7 01:20:30 2020 local2.info chat[29485]: timeout set to 30 seconds
110 Fri Feb  7 01:20:30 2020 local2.info chat[29485]: expect (OK)
111 Fri Feb  7 01:20:30 2020 local2.info chat[29485]: ^M
112 Fri Feb  7 01:20:30 2020 local2.info chat[29485]: AT+CGDCONT=1,"IP",""^M^M
113 Fri Feb  7 01:20:30 2020 local2.info chat[29485]: OK
114 Fri Feb  7 01:20:30 2020 local2.info chat[29485]:  ~-~- got it
115 (% style="color:#037691" %)**Fri Feb  7 01:20:30 2020 local2.info chat[29485]: send (ATD*99#^M)      ~-~-~-~--> In case the dialling process already reach here.
116 Normally the problem is with a provider, need to check if the SIM card has balance or other requirement from the cellular operator**(%%)
117 (% style="color:black" %)Fri Feb  7 01:20:30 2020 local2.info chat[29485]: expect (CONNECT)
118 Fri Feb  7 01:20:30 2020 local2.info chat[29485]: ^M
119 Fri Feb  7 01:20:30 2020 local2.info chat[29485]: ATD*99#^M^M
120 Fri Feb  7 01:20:30 2020 local2.info chat[29485]: CONNECT
121 Fri Feb  7 01:20:30 2020 local2.info chat[29485]:  ~-~- got it
122 Fri Feb  7 01:20:30 2020 local2.info chat[29485]: send ( ^M)
123 Fri Feb  7 01:20:30 2020 daemon.info pppd[29452]: Serial connection established.
124 )))
125
126
127 == 2.4 If the following situation occurs, how can users solve this problem? ==
128
129 === 2.4.1 The gateway can read the SIM card, But the Internet is displayed as Fail. ===
130
131
132 Users can check whether the APN matched by the SIM card is correct.
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.
135
136 [[image:image-20220718155937-1.png||height="562" width="497"]]
137
138
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
141
142 It should be SIM card no flow, users can insert SIM cards into the mobile phone for testing.
143
144 [[image:1658131428288-728.png||height="538" width="494"]]
145
146
147 === 2.4.3 The gateway can't read the SIM card, and the Internet is displayed as Fail. ===
148
149
150 Users need to check whether the SIM card type is suitable for the EC25 module.
151
152 [[image:1658131612484-845.png||height="549" width="499"]]
153
154
155 === 2.4.4 SIM display：~*~**SIM ERROR~*~** Check SIM is inserted test SIM in a mobile phone？ ===
156
157
158 Users can insert SIM cards into the mobile phone for testing.
159
160 [[image:image-20220718160804-3.png||height="602" width="500"]]
161
162
163 = 3. Share Cellular Network for WiFi & LAN clients =
164
165
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.
168 )))
169
170 (% class="box" %)
171 (((
172 (((
173 root@dragino-1d25dc:~~# cat /etc/config/firewall
174
175 config defaults
176 option syn_flood '1'
177 option input 'ACCEPT'
178 option output 'ACCEPT'
179 option forward 'REJECT'
180 config zone
181 option name 'lan'
182 list network 'lan'
183 option input 'ACCEPT'
184 option output 'ACCEPT'
185 option forward 'REJECT' 
186 config zone
187 option name 'wan'
188 list network 'wan'
189 list network 'wwan'
190 list network 'wan6'
191 list network 'cellular'   ~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~--> Add this line and reboot
192 option input 'REJECT'
193 option output 'ACCEPT'
194 option forward 'ACCEPT'
195 option masq '1'
196 option mtu_fix '1'
197 config forwarding
198 option src 'lan'
199 option dest 'wan'
200 )))
201 )))
202
203 (((
204 and run **/etc/init.d/firewall reload** or **reboot the device**.
205
206
207 = 4. Switching between Cellular and Ethernet and Wi-Fi networks =
208
209
210 By default, Cell is the backup WAN where the Ethernet or Wi-Fi network is used first if they are available.
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.
213
214
215 **Enable Cellular and connect Ethernet at the same time**
216
217 ETH icon is displayed as ​​​ [[image:1658135519305-444.png||height="18" width="19"]] Indicates that Ethernet is the main working network.
218
219 Cell icon is displayed as  [[image:1658135500498-725.png||height="17" width="17"]] Indicates that Cellular is the backup WAN.
220
221
222 == 4.1 Switching between Cellular and Ethernet networks ==
223
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
226
227 [[image:image-20220606140622-2.png||height="664" width="1106"]]
228
229
230 **Remove the network cable from the WAN port on the gateway, the gateway will switch to a Cellular network.**
231
232 [[image:image-20220606140859-4.png||height="687" width="1107"]]
233
234 (% style="display:none" %) (%%)
235
236 == 4.2 Switching between Cellular and WiFi networks ==
237
238
239 (% class="wikigeneratedid" %)
240 Enable **Cellular** and connect **WiFi** at the same time
241
242 WiFi icon is displayed as ​​​[[image:1658135519305-444.png||height="23" width="24"]] Indicates that WiFi is the main working network.
243
244 Cell icon is displayed as  [[image:1658135500498-725.png||height="23" width="22"]] Indicates that Cellular is the backup WAN.
245
246
247 [[image:image-20220606141113-7.png||height="678" width="1106"]]
248
249
250 **Close the WiFi WAN, the gateway will switch to a Cellular network.**
251
252 [[image:image-20220606140932-5.png||height="687" width="1107"]]
253
254
255 == 4.3 At the same time start Cellular and Ethernet and Wi-Fi networks ==
256
257
258 [[image:image-20220606140328-1.png||height="682" width="1108"]]
259
260
261 )))
262
263 = 5. How does the gateway view the International Mobile Equipment Identity (IMEI) =
264
265 == For LIG16,LPS8, LPS8N, LG308, LG308N, DLOS8, DLOS8N view the International Mobile Equipment Identity (IMEI) ==
266
267
268 Users can get the IMEI via Linux command, but you have to access the gateway CLI.
269
270 (% class="box infomessage" %)
271 (((
272 **root@dragino-24b3c8:~~# comgt -d /dev/ttyModemAT -s /etc/gcom/getimei.gcom **
273 )))
274
275 [[image:image-20231218095203-4.png]]
276
277
278 [[image:image-20231218095426-6.jpeg||height="466" width="990"]]
279
280
281 == For LPS8v2 view the International Mobile Equipment Identity (IMEI) ==
282
283 (% class="box infomessage" %)
284 (((
285 **root@dragino-e4e891:~~# /usr/local/dragino/cell/getinfo.sh**
286 )))
287
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
297 Users can access the gateway CLI and run the minicom command to get the configuration interface.
298
299 (((
300
301
302 **Enter the minicom command, then select the option ''serial port setup".**
303 )))
304
305 (% class="box infomessage" %)
306 (((
307 **root@dragino-1ef9ac:~~# minicom -s**
308 )))
309
310 [[image:image-20220527154132-6.png]]
311
312
313 And then, change the setting:
314
315 (% class="box infomessage" %)
316 (((
317 **Serial Device :** (% style="color:#037691" %)**/dev/ttyModemAT**
318
319 **Bps/Par/Bits :(% style="color:#037691" %) 9600 8N1(%%)**
320 )))
321
322
323 (% style="color:red" %)**Note: Enter the corresponding letter to change the configuration, like A,B,C**
324
325 [[image:image-20220527154154-7.png]]
326
327
328 == International Mobile Equipment Identity (IMEI) ==
329
330
331 (((
332 Enter (% style="color:blue" %)**AT+GSN **(%%)in the interface to get the IMEI,
333 )))
334
335 (((
336 **For example: (% style="color:#037691" %)860548042566627(%%)**
337 )))
338
339 (% class="box infomessage" %)
340 (((
341 (((
342 **AT+GSN**
343 )))
344 )))
345
346 [[image:image-20220527154231-8.png]]
347
348
349 == Integrated Circuit Card Identifier (ICCID) ==
350
351
352 (((
353 Enter (% style="color:blue" %)**AT+QCCID **(%%)in the interface to get the ICCID,
354 )))
355
356 (((
357 **For example: (% style="color:#037691" %)89860118005400261748(%%)**
358
359 (% class="box infomessage" %)
360 (((
361 **AT+QCCID**
362 )))
363 )))
364
365 [[image:1678675878256-777.png]]
366
367
368 = 6. How does the gateway connect to the network via a USB 4G Dongle =
369
370 == 6.1 Introduction ==
371
372
373 (% style="color:red" %)**Prerequisite: Requires a USB 4G Dongle and a supported gateway firmware**
374
375 (((
376 This introduces a setup and configured gateway for using a USB 3g/UMTS-modem for WAN connection.
377
378
379 )))
380
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.
383 )))
384
385 (((
386 This is not beginner-friendly due to too many protocols.
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]]
389
390
391 )))
392
393 == 6.2 How to use the USB Dongle at the gateway ==
394
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.
397
398 (((
399 For example, the Huawei-E3372/E8372 is using **Hilink mode** or **NCM mode**.
400 )))
401
402 (% class="box" %)
403 (((
404 Huawei-E3372/E8372
405 Check the (% style="color:#037691" %)**E3372**(% style="color:black" %) version to determine the mode.
406 The version numbers starting with 21 is NCM mode
407 The version numbers starting with 22 is Hilink mode
408 The E8372 only has Hilink mode
409 **~ **(% style="color:red" %)**Note： The e3372 in the vast majority of cases is Hilink mode**
410 )))
411
412
413 == 6.3 Hilink mode ==
414
415
416 //Gateway upgrade to the specified firmware:[[Hilink.mode~~-~~-build-v5.4.1625627505>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LG308-LG301/Firmware/USB-Dongle_firmware/Hilink.mode--build-v5.4.1625627505-20210707-1113/]]//
417
418
419 === 6.3.1 Plugs into the device ===
420
421
422 (((
423 USB-Dongle plugs into the gateway USB port
424 )))
425
426 (((
427 Check the USB module via command (% style="color:#037691" %)**lsusb**
428 )))
429
430 (((
431 (% style="color:red" %)**Note: Users need to that connect to the gateway command line via ssh.**
432 )))
433
434 [[image:image-20220527154739-9.png]]
435
436
437 === 6.3.2 Detection of new network interfaces added ===
438
439
440 Check network configuration command line input:
441
442 (% class="box infomessage" %)
443 (((
444 (((
445 **~ root@dragino-1ef9ac:~~# ifconfig -a**
446 )))
447 )))
448
449 [[image:image-20220527154822-10.png]]
450
451 In the command, the output user can see that the new interface added is (% style="color:#037691" %)**eth2**
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**
454
455
456 === 6.3.3 Add the new interface to the network configuration. ===
457
458
459 //Enter the configuration from the command line~://
460
461 (% class="box" %)
462 (((
463 uci set network.lte=interface
464 uci set network.lte.proto=dhcp
465 uci set network.lte.ifname=eth2    ~-~-~-~-~-~-~-~-->#This depend on the name of the new interface gateway add
466 uci commit network
467 uci set firewall.@zone[1].network="wan wwan wan6 lte"
468 uci commit firewall
469 /etc/init.d/network restart
470 )))
471
472 [[image:image-20220527154937-11.png]]
473
474
475 //**Checking Network Configurations**//
476
477 //Command-line input: (% style="color:#037691" %)**ifconfig**//
478
479 [[image:image-20220527155013-12.png]]
480
481 Now, Gateway is configured to access the internet on the LTE network.
482
483
484 == 6.4 NCM mode ==
485
486
487 == 6.5 Troubleshooting ==
488
489 === 6.5.1 The USB-Dongle interface cannot obtain the IP address. ===
490
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.
493
494
495 = 7. How to reduce data traffic =
496
497 == 7.1 How the gateway will consume data traffic ==
498
499 Below list the place where the data traffic will use.
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)
507
508 === 7.1.1 LoRaWAN Status push or polling data to LoRaWAN server ===
509
510
511 When gateway connect to LoRaWAN server via LoRaWAN protocol, besides the sensor data uplink/downlink. gateway will still need to:
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 [[image:image-20220527155108-13.png]]
517
518
519 === 7.1.2 System Keep Alive data ===
520
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.
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.
525
526 [[image:image-20220527155229-15.png||height="511" width="986"]]
527
528
529 === 7.1.3 Auto update ===
530
531
532 Gateway will check for update every day for new configure or software. User can disable them by below method.
533
534
535 === 7.1.4 Filter unwanted packets ===
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 See [[How to filter unwanted packets>>doc:Main.Filter unwanted LoRaWAN packets.WebHome]]
541
542
543 == 7.2 Usage statistics ==
544
545 === 7.2.1 How does Openwrt usage statistics ===
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 ~1. Activate LuCI and connect to SSH following [[these instructions>>doc:Main.Install Luci in the new UI firmware.WebHome]]
556
557 2. Install luci-app-statistics using the following terminal commands:
558
559 {{{opkg update
560 opkg install luci-app-statistics
561 opkg install collectd-mod-interface
562 /etc/init.d/collectd enable
563 reboot
564 }}}
565
566 3. Select the interface to be monitored by going to **Statistics > Setup **in the upper menu then **Network plugins > Interfaces. **Select **3g-cellular **in the list then save. You can select multiple interfaces by pressing the **ctrl key **while selecting the interfaces.
567
568 [[image:image-20221124133431-1.png]]
569
570 [[image:image-20221124135102-2.png]]
571
572
573 4. View the graphs and statistics using by going to **Statistics > Graphs** **> Interfaces > 3g-cellullar**
574
575 [[image:image-20221124134927-1.png]]
576
577

Applications

Navigation

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