Skip to Content
Version 343.1 by Kilight Cao on 2024/12/31 15:46
Show last authors
1 (% style="text-align:center" %)
2 [[image:image-20220620202334-2.png||height="467" width="809"]]
3
4
5 (((
6
7
8
9 )))
10
11 **Table of Contents:**
12
13 {{toc/}}
14
15
16
17
18
19 = 1. Introduction =
20
21 == (% data-sider-select-id="66d5195f-ab1f-47c7-83cb-b027d0903e53" %)1.1 What is LPS8v2(%%) ==
22
23
24 (((
25 (((
26 The LPS8v2 is an (% style="color:blue" %)**open-source LoRaWAN Gateway**(%%). It lets you bridge LoRa wireless network to an IP network via (% style="color:blue" %)**WiFi , Ethernet or Cellular Network**(%%) (via Optional 4G module). The LoRa wireless allows users to send data and reach extremely long ranges at low data rates.
27 )))
28
29 (((
30 The LPS8v2 is fully compatible with LoRaWAN protocol. It supports different kinds of LoRaWAN Network Connections such as: (% style="color:blue" %)**Semtech UDP Packet Forwarder, LoRaWAN Basic Station, ChirpStack MQTT Bridge**(%%), and so on. This makes LPS8V2 work with most LoRaWAN platforms in the market.
31 )))
32
33 (((
34 LPS8v2 also includes a (% style="color:blue" %)**built-in LoRaWAN Server and IoT server**(%%), which provide the possibility for the system integrator to deploy the IoT service without cloud service or 3rd servers.
35 )))
36
37 (((
38 Different countries use different LoRaWAN frequency bands. LPS8v2 has these bands pre-configured. Users can also customize the frequency bands to use in their own LoRa network.
39 )))
40
41 (((
42 LPS8v2 supports (% style="color:blue" %)**remote management**(%%). System Integrator can easy to remote monitor the gateway and maintain it.
43 )))
44
45
46 == 1.2 Specifications ==
47
48
49 (% style="color:#037691" %)**Hardware System:**
50
51 * CPU: Quad-core Cortex-A7 1.2Ghz
52 * RAM: 512MB
53 * eMMC: 4GB
54
55 (% style="color:#037691" %)**Interface:**
56
57 * 10M/100M RJ45 Ports x 1
58 * Multi-Channel LoRaWAN Wireless
59 * WiFi 802.11 b/g/n
60 * Sensitivity: -140dBm
61 * Max Output Power: 27dBm
62
63 (% style="color:#037691" %)**Operating Condition:**
64
65 * Work Temperature: -20 ~~ 70°C
66 * Storage Temperature: -20 ~~ 70°C
67 * Power Input: 5V, 2A, DC
68
69 == 1.3 Features ==
70
71
72 * Open Source Debian system
73 * Managed by Web GUI, SSH via WAN or WiFi
74 * Remote Management
75 * Auto-provisioning for batch deployment and management
76 * LoRaWAN Gateway
77 * 10 programmable parallel demodulation paths
78 * Pre-configured to support different LoRaWAN regional settings.
79 * Allow customizing LoRaWAN regional parameters.
80 * Different kinds of LoRaWAN Connections such as
81 ** Semtech UDP Packet Forwarder
82 ** LoRaWAN Basic Station
83 ** ChirpStack-Gateway-Bridge (MQTT)
84 * Built-in (% style="color:#037691" %)**ChirpStack**(%%) local LoRaWAN server
85 * Built-in  (% style="color:#037691" %)**Node-Red** (%%)local Application server
86
87 == 1.4 LED Indicators ==
88
89
90 LPS8-V2 has totally four LEDs, They are:
91
92
93 (% style="color:blue" %)**➢ Power LED**(%%): This RED LED will be solid if the device is properly powered
94
95 (% style="color:blue" %)**➢ ETH LED**(%%):  This RGB LED will blink GREEN when the ETH port is connecting
96
97 (% style="color:blue" %)**➢ SYS LED**(%%):  This RGB LED will show different colors in different states:
98
99 ✓  **SOLID GREEN:** The device is alive with a LoRaWAN server connection.
100
101 ✓  **BLINKING GREEN:** a) Device has internet connection but no LoRaWAN Connection. or b) Device is in booting stage, in this stage, it will BLINKING GREEN for several seconds and then with BLINKING GREEN together
102
103 ✓**  SOLID RED:** Device doesn't have an Internet connection.
104
105 (% style="color:blue" %)**➢ WIFI LED**(%%): This LED shows the WIFI interface connection status.
106
107
108 == 1.5 Button Instruction ==
109
110
111 LPS8-V2 has a black toggle button, which is:
112
113
114 (% style="color:blue" %)**//➢ //Long press 4-5s  : **(%%)the gateway will reload the Network and Initialize wifi configuration
115
116 // // **LED status: ** ETH LED will BLINKIND BULE Until the reload is finished.
117
118
119 (% style="color:blue" %)**➢ Long press more than 10s:**(%%)**    **the gateway will restore the factory settings.
120
121 **LED status: ** ETH LED will SOLID BULE Until the restore is finished.
122
123
124 (% style="color:red" %)**Note: Restoring factory Settings does not erase data from the LPS8-V2 built-in server**
125
126 See this link for steps on how to clear data from the built-in server: **[[How to reset the built-in server>>http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20All%20Gateway%20models/HP0C/#H9.6A0Howtoresetthebuilt-inserver]]**
127
128
129 When the gateway restores the factory settings is complete,
130
131 The WiFi configuration will enable WiFi Access Point by default.
132
133 The other configuration will be restored to the default configuration.
134
135
136 = 2. Quick Start =
137
138
139 The LPS8-V2 supports network access via Ethernet or Wi-Fi connection and runs without a network.
140
141 In most cases, the first thing you need to do is make the lps8-v2 accessible to the network.
142
143
144 == 2.1 Access and Configure LPS8-V2 ==
145
146 === 2.1.1 Find IP address of LPS8-V2 ===
147
148
149 ==== (% style="color:blue" %)**Method 1**(%%):  Connect via LPS8-V2 WiFi ====
150
151
152 Since software version **230524**,At the first boot of LPS8-V2, it will auto generate a WiFi network called (% style="color:green" %)**//dragino-xxxxxx //**(%%)with password:
153
154 (% style="background-color:yellow" %)**dragino+dragino**
155
156 User can use a PC to connect to this WiFi network. The PC will get an IP address 10.130.1.xxx and the LPS8-V2 has the default IP (% style="color:green" %)**10.130.1.1**
157
158 [[image:image-20230527084515-1.png]]
159
160 [[image:image-20230527085250-2.png||height="495" width="284"]]
161
162
163 ==== (% style="color:blue" %)**Method 2**(%%):  Connect via Ethernet with DHCP IP from the router ====
164
165
166 (((
167 Connect the LPS8-V2 Ethernet port to your router and LPS8-V2 can obtain an IP address from your router. In the router's management portal, you should be able to find what IP address the router has assigned to the LPS8-V2.
168 )))
169
170 (((
171 You can also use this IP to connect.
172 )))
173
174 [[image:image-20220622100129-1.png||height="332" width="1263"]]
175
176
177 ==== (% style="color:blue" %)**Method 3**(%%):  Connect via LPS8-V2 Fallback IP ====
178
179
180 [[image:image-20230107084650-2.png||height="310" width="839"]]
181
182
183 (% style="color:blue" %)**Steps to connect via fallback IP:**
184
185 ~1. Connect the PC's Ethernet port to LPS8-V2's WAN port
186
187 2. Configure PC's Ethernet port has IP: 172.31.255.253 and Netmask: 255.255.255.252
188
189
190 **Settings ~-~-> Network & Internet ~-~-> Ethernet ~-~-> Change advanced sharing options ~-~-> Double-click"Ethernet" ~-~-> Internet Protocol Version 4 (TCP/IPv4)**
191
192
193 As in the below photo:
194
195 [[image:image-20230413172038-1.png||height="732" width="1243"]]
196
197
198 Configure computer Ethernet port steps video: **[[attach:fallback ip.mp4||target="_blank"]]**
199
200 If you still can't access the LPS8-V2 fallback ip, follow this connection to debug : **[[Trouble Shooting>>http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20All%20Gateway%20models/HP0C/#H9.3A0FallbackIPdoesnotwork2Chowcanuserscheck]]**
201
202
203 3. In the PC, use IP address 172.31.255.254 to access the LPS8-V2 via Web or Console.
204
205 [[image:image-20230111094247-2.png||height="619" width="1250"]]
206
207
208 ==== (% style="color:blue" %)**Method 4**(%%):  Connect via WiFi with DHCP IP from the router ====
209
210 [[image:image-20220622100542-2.png||height="369" width="1256"]]
211
212
213 Fill in the WiFi information by checking the box and clicking (% style="color:red" %)**Save&Apply**
214
215
216 [[image:image-20241231151635-3.png||height="481" width="944"]]
217
218
219
220 **Wi-Fi configuration successful**
221
222 [[image:image-20241231151810-4.png||height="487" width="947"]]
223
224
225 [[image:image-20241231152015-6.png||height="506" width="1001"]]
226
227
228 === 2.1.2 Access Configure Web UI ===
229
230
231 **Web Interface**
232
233 Open a browser on the PC and type the LPS8-V2 ip address (depends on your connect method)
234
235
236 [[(% style="background-color:yellow" %)**//http:~~/~~/IP_ADDRESS //**>>http://IP_ADDRESS]](%%) or (% style="background-color:yellow" %)//**[[http:~~/~~/172.31.255.254>>http://172.31.255.254(]]**//(Fallback IP)
237
238 You will see the login interface of LPS8-V2 as shown below.
239
240 The account details for Web Login are:
241
242 (% style="color:blue" %)**User Name: root**
243
244 (% style="color:blue" %)**Password:   dragino**
245
246 [[image:image-20240318160845-1.png]]
247
248
249 == 2.2  Typical Network Setup ==
250
251 === 2.2.1  Overview ===
252
253
254 LPS8-V2 supports flexible network set up for different environment. This section describes the typical network topology can be set in LPS8-V2. The typical network set up includes:
255
256 * **WAN Port Internet Mode**
257
258 * **WiFi Client Mode**
259
260 * **Cellular Mode**
261
262 === 2.2.2  Use WAN port to access Internet ===
263
264
265 By default, the LPS8-V2 is set to use the WAN port to connect to an upstream network. When you connect the LPS8-V2's WAN port to an upstream router, LPS8-V2 will get an IP address from the router and have Internet access via the upstream router. The network status can be checked in the (% style="color:blue" %)**home page**(%%):
266
267
268 [[image:image-20230411100633-2.png||height="501" width="935"]]
269
270
271 === 2.2.3  Access the Internet as a WiFi Client ===
272
273
274 In the WiFi Client Mode, LPS8-V2 acts as a WiFi client and gets DHCP from an upstream router via WiFi.
275
276 The settings for WiFi Client is under page (% style="color:blue" %)**Network ~-~-> Wi-Fi**
277
278 [[image:image-20241231151512-2.png]]
279
280 In the WiFi Survey Choose the WiFi AP, and input the Passphrase then click(% style="color:blue" %)** Save & Apply**(%%) to connect.
281
282
283 === 2.2.4  Use built-in 4G modem for internet access ===
284
285
286 (% style="color:blue" %)**Since Hardware version HP0C 1.4**
287
288 Users can see whether LPS8v2 has EC25 on the label of the gateway to determine whether there is 3G/4G Cellular modem.
289
290
291 If the LPS8-V2 has 3G/4G Cellular modem, user can use it as main internet connection or back up.
292
293 First, install the Micro SIM card as below direction
294
295 Second, Power off/ ON LPS8-V2 to let it detect the SIM card.
296
297
298 [[image:image-20241231153425-1.jpeg||height="262" width="884"]]
299
300
301 The set up page is (% style="color:blue" %)**Network ~-~-> Cellular**
302
303 While use the cellular as Backup WAN, device will use Cellular for internet connection while WAN port or WiFi is not valid and switch back to WAN port or WiFi after they recover.
304
305
306 [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20All%20Gateway%20models/LPS8N%20-%20LoRaWAN%20Gateway%20User%20Manual/WebHome/1657090932270-444.png?rev=1.1||alt="1657090932270-444.png"]]
307
308
309 (% style="color:red" %)**Note: In most cases, the user simply types in the APN and checks the enable checkbox, without typing Pincode, Username, or Password settings.**
310
311
312 When cellular fails to connect or has problems, users can refer to this link to debug:**[[How to Debug if Cellular connection fails>>https://wiki.dragino.com/xwiki/bin/view/Main/Notes%20for%20cellular%20network%20connection/#H2.2ForLPS8v22FMS48-LR]]**
313
314
315 === 2.2.5  Check Internet connection ===
316
317
318 In the **home** page, we can check the Internet connection.
319
320 * GREEN Tick ​​​​ [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20All%20Gateway%20models/LPS8N%20-%20LoRaWAN%20Gateway%20User%20Manual/WebHome/1652436675869-206.png?width=15&height=14&rev=1.1||alt="1652436675869-206.png"]] : This interface has Internet connection.
321 * Yellow  Tick  [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20All%20Gateway%20models/LPS8N%20-%20LoRaWAN%20Gateway%20User%20Manual/WebHome/1652436705761-420.png?width=15&height=15&rev=1.1||alt="1652436705761-420.png"]] : This interface has IP address but don't use it for internet connection.
322 * RED Cross  [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20All%20Gateway%20models/LPS8N%20-%20LoRaWAN%20Gateway%20User%20Manual/WebHome/1652436787176-950.png?width=15&height=14&rev=1.1||alt="1652436787176-950.png"]] : This interface doesn't connected or no internet.
323
324 [[image:image-20230411101534-3.png||height="544" width="942"]]
325
326
327 == 2.3 The LPS8-V2 is registered and connected to The Things Network ==
328
329 === 2.3.1 Select your area frequency ===
330
331
332 (((
333 First, you need to set the frequency plan in LPS8-V2 to match the end node we use, so to receive the LoRaWAN packets from the LoRaWAN sensor.
334
335
336 )))
337
338 [[image:image-20220622103332-9.png||height="485" width="938"]]
339
340
341 === 2.3.2 Get the only gateway EUI ===
342
343
344 Every LPS8-V2 has a unique gateway id. The ID can be found on LoRaWAN Semtech page:
345
346
347 [[image:image-20220622103355-10.png||height="698" width="949"]]
348
349
350 (% style="color:red" %)**Note: Choose the cluster that corresponds to a specific Gateway server address**
351
352
353 **➢ Europe 1:**  corresponding Gateway server address:  **eu1.cloud.thethings.network**
354
355 **➢ North America 1:**  corresponding Gateway server address:  **nam1.cloud.thethings.network**
356
357 **➢ Australia 1: ** corresponding Gateway server address:  **au1.cloud.thethings.network**
358
359 **➢ Legacy V2 Console:** TTN v2 shuts down in December 2021
360
361
362 [[image:image-20220622103956-12.png]]
363
364
365 === 2.3.3 Register the gateway to The Things Network ===
366
367
368 **Login to The Things Network**
369
370 [[https:~~/~~/console.cloud.thethings.network/>>https://console.cloud.thethings.network/]]
371
372
373 **Add the gateway**
374
375 [[image:image-20220622104252-13.png||height="511" width="953"]]
376
377
378 **Get it online**
379
380
381 = 3. Web Configure Pages =
382
383 == 3.1 Home ==
384
385
386 Shows the system running status:
387
388 [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20All%20Gateway%20models/HP0C/WebHome/image-20220622102901-8.png?rev=1.1||alt="image-20220622102901-8.png" height="476" width="939"]]
389
390
391 == 3.2 LoRa Settings ==
392
393 === 3.2.1 LoRa ~-~-> LoRa ===
394
395
396 This page shows the LoRa Radio Settings. There is a set of default frequency bands according to LoRaWAN protocol, and users can customize the band* as well.
397
398 Different LPS8v2 hardware versions can support different frequency ranges:
399
400 * (% style="color:#0000ff" %)**868**(% style="color:black" %): valid frequency: 863Mhz ~~ 870Mhz. for bands EU868, RU864, IN865, or KZ865.
401 * (% style="color:#0000ff" %)**915**(% style="color:black" %): valid frequency: 902Mhz ~~ 928Mhz. for bands US915, AU915, AS923 or KR920
402
403 (% class="wikigeneratedid" %)
404 After the user choose the frequency plan,  the user can see the actual frequency is used by checking the page (% style="color:#037691" %)**LogRead ~-~-> LoRa Log**
405
406
407 (% class="wikigeneratedid" %)
408 [[image:image-20220616110739-1.png||height="457" width="836"]]
409
410
411 (((
412 (% style="color:red" %)//**Note *: See this instruction for how to customize the frequency band: **//(%%)**//__[[How to customized LoRaWAN frequency band - DRAGINO>>doc:Main.How to customized LoRaWAN frequency band.WebHome]]__//**
413 )))
414
415
416 == 3.3 LoRaWAN Settings ==
417
418 === 3.3.1 LoRaWAN ~-~-> LoRaWAN Semtech UDP ===
419
420
421 This page is for the connection set up to a general LoRaWAN Network server such as [[TTN>>url:http://www.thethingsnetwork.org/]], [[ChirpStack>>url:https://www.chirpstack.io/]], etc.
422
423
424 [[image:image-20220616111932-2.png||height="516" width="672"]]
425
426
427 === 3.3.2 LoRaWAN ~-~-> LoRaWAN Basic Station ===
428
429
430 This page is for the connection set up to the TTN Basic Station, AWS-IoT, etc.
431
432
433 [[image:image-20220616113246-3.png||height="396" width="672"]]
434
435
436 (((
437 Please see this instruction to know more detail and a demo for how to use of LoRaWAN Basic Station: __[[Use of LoRaWAN Basic Station - DRAGINO>>doc:Main.Use of LoRaWAN Basic Station.WebHome]]__
438
439
440 == (% style="color:inherit; font-family:inherit; font-size:26px" %)3.4  Forwarder(%%) ==
441 )))
442
443 === 3.4.1 Forwarder ~-~-> MQTT Forwarder ===
444
445
446 In the latest version, MQTT Forwarder functionality has been added to the LPS8V2 gateway by default
447
448 Users can configure the MQTT Forwarder on the **Forwarder~-~->MQTT** interface, and when the configuration is successful, it will forward the sensor data of the lorawan server chirpstack built in LPS8v2
449
450 For a detailed example of this feature, see this link:**[[MQTT Forward Instruction - DRAGINO>>http://wiki.dragino.com/xwiki/bin/view/Main/MQTT%20Forward%20Instruction/#H3.3A0UseLoRaWANProtocolforcommunication--ForLPS8V2]]**
451
452 (% class="wikigeneratedid" %)
453 [[image:image-20240902092034-1.png]]
454
455
456 == 3.5 Network Settings ==
457
458 === 3.5.1 Network ~-~-> WiFi ===
459
460 Users can configure the wifi WAN and enable Wifi Access Point on this interface
461
462 [[image:image-20241231151434-1.png||height="608" width="1195"]]
463
464
465 === 3.5.2 Network ~-~-> System Status ===
466
467
468 [[image:image-20220820134112-2.png||height="539" width="668"]]
469
470
471 === 3.5.3 Network ~-~-> Network ===
472
473
474 In the **Network ~-~-> Network** interface, Users can set the Ethernet WAN static ip address.
475
476 [[image:image-20230214093657-2.png||height="333" width="858"]]
477
478
479 === 3.5.4 Network ~-~-> Cellular ===
480
481
482 In the **Network ~-~-> Cellular** interface, Users can Enable Cellular WAN and configure Celluar.
483
484 (% style="color:red" %)**Note: APN cannot be empty.**
485
486 [[image:image-20230228115126-1.png]]
487
488
489 After the configuration is complete, return to the Home interface and put the mouse on the Cell icon to check the Cellular state.
490
491 [[image:image-20230228115535-2.png||height="478" width="888"]]
492
493
494 Note: Known bugs: 4g consumes a lot of data which has been fixed by the package: dragino-ui-230716
495
496 [[Reduce data method>>http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20All%20Gateway%20models/HP0C/#H8.3Howtoreducethe4gdataconsumed]]
497
498 (% class="wikigeneratedid" id="H5.MQTTForwarder" %)
499 (% id="cke_bm_4823S" style="display:none" %)
500
501
502 == 3.6 System ==
503
504 === 3.6.1 System ~-~-> System Overview ===
505
506
507 Shows the system info:
508
509 [[image:image-20231031162854-1.png]]
510
511
512 === 3.6.2 System ~-~-> System General ===
513
514
515 In the **System-> System General** interface, Users can customize the configuration System Password and set Timezone.
516
517 In addition, Users can customize the FallBack IP address.
518
519 [[image:image-20230214094058-3.png]]
520
521
522 === 3.6.3 System ~-~-> Backup/Restore ===
523
524
525 [[image:image-20231031162927-2.png]]
526
527 === 3.6.4 System ~-~-> Reboot / Reset ===
528
529 In the **System-> Reboot / Reset** interface, users can can restart or reset the gateway.
530
531 ETH LED will SOLID BULE Until the restore is finished.
532
533 When the gateway restores the factory settings is complete,
534
535 The WiFi configuration will enable WiFi Access Point by default.
536
537 The other configuration will be restored to the default configuration.
538
539 [[image:image-20240203172853-1.png||height="365" width="901"]]
540
541
542 === 3.6.5 System ~-~-> Remoteit ===
543
544
545 In the **System-> Remoteit** interface, users can configure the gateway to be accessed remotely via Remote.it.
546
547
548 the users can refer to this link to configure them: **[[Monitor & Remote Access Gateway>>http://wiki.dragino.com/xwiki/bin/view/Main/Monitor%20%26%20Remote%20Access%20Gateway/?Remote%20Access#H2.1A0RemoteAccessviaRemote.it.]]**
549
550 [[image:image-20221230092303-2.png]]
551
552
553 === 3.6.6 System ~-~-> Package Management ===
554
555
556 In the **System ~-~-> Package Management** interface, Users can check the current version of Core Packages.
557
558 [[image:image-20230214094316-4.png]]
559
560
561 == 3.7 Logread ==
562
563 === 3.7.1 LoRa Log ===
564
565
566 In the **Lograde ~-~-> LoRa Log page**, The users can view information about the gateway lora channel and the status of the IoT connection
567
568 [[image:image-20240416112509-1.png]]
569
570
571 === 3.7.2 Gateway Traffic ===
572
573 In the **Lograde ~-~-> Gateway Traffic page**, The users can view sensor packages about Recent LoRa uplink/downlink/Join requests
574
575 [[image:image-20240416112618-2.png||height="705" width="1122"]]
576
577
578 === 3.7.3 System Log ===
579
580 In the **Lograde ~-~-> System Log page**, The users can view information about the gateway system
581
582 [[image:image-20240416112649-3.png||height="820" width="1122"]]
583
584
585 === 3.7.4 Record Log ===
586
587 In the **Lograde ~-~-> Recod Log page**, The users can record the gateway curren running log.
588
589 [[image:image-20240416112712-4.png||height="319" width="1128"]]
590
591
592
593 = 4. Build-in Server =
594
595 After the v1.7-230606 version, the LPS8-V2 default factory pre-installed the LoRaWAN Server: (% style="color:blue" %)**ChirpStack-V4**(%%), Application Server: (% style="color:blue" %)**Node-Red**(%%).
596
597
598 == 1). LoRaWAN Network Server: (% style="color:blue" %)**ChirpStack-V4**(%%) ==
599
600 [[image:image-20231106180816-4.png||height="416" width="896"]]
601
602 [[image:image-20231201165904-1.png||height="466" width="899"]]
603
604 (% style="color:red" %)**Note:  The user can access the**(%%)** (% style="color:blue" %)ChirpStack-V4 (% style="color:red" %)via click the 'Launch' button, and the login account: admin/admin(%%)**
605
606 For more information on server operations see [[Register LPSV2 to the built-in Chirpstack>>||anchor="H2.3TheLPS8-V2isregisteredandconnectedtoTheThingsNetwork"]]
607
608
609
610 == 2). Application Network Server: (% style="color:blue" %)**Node-Red**(%%) ==
611
612
613 [[image:image-20230616175558-7.png||height="362" width="894"]]
614
615 [[image:image-20231201170355-2.png||height="536" width="899"]]
616
617 (% style="color:red" %)**Note:  The user can access the**(%%)** (% style="color:blue" %)Node-RED (% style="color:red" %)via click the 'Launch' button(%%)**
618
619
620
621 == **3). Troubleshooting:** ==
622
623
624 * (((
625 === ** If the URL does not jump properly.** ===
626 )))
627
628 For the ChirpStack, you can use the local IP address and the port is **8080** to access it.
629
630 For the Node-Red, you can use the local IP address and the port is **1880** to access it.
631
632
633 * (((
634 === ** How to install InfluxDB, Garfana.** ===
635 )))
636
637 The LPS8V2 is not pre-installed with InfluxDB and Garfana, the users can install them, see [[InfluxDB>>http://wiki.dragino.com/xwiki/bin/view/Main/Armbian%20OS%20instruction/#H2.6HowtoinstallGrafanaandinfluxdb]]
638
639
640 * (((
641 === ** How to upgrade the gateway node.js to the latest version.** ===
642 )))
643
644 The user can upgrade nodejs, see [[Upgrade Nodejs>>http://wiki.dragino.com/xwiki/bin/view/Main/Armbian%20OS%20instruction/#H2.5Howtoupgradethenodejsversiontothelatest.]]
645
646
647 * (((
648 === ** How to batch register device on the built-in Chirpstack network server** ===
649 )))
650
651 The user can register devices in batch on the gateway Web UI, see [[Batch Register>>http://wiki.dragino.com/xwiki/bin/view/Main/Notes%20for%20ChirpStack/#H11.A0HowtouseChirpstackAPItobatchregisterSensorNode2FGatewayinChistapstackServer]]
652
653
654 * (((
655 === ** Why my gateway is not Chirpstack?** ===
656 )))
657
658 After June '23, the default factory LPS8V2 pre-installed Chirpstack-V4 instead of The Things Stack, the users can migrate to Chistack-V4, see **[[Change TTN Stack v3 to ChirpStack>>http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20All%20Gateway%20models/HP0C/#H9.2Build-inTheThingsNetworkmigratetoChirpStack]]**
659
660
661 * (((
662 === ** How to disable the built-in server** ===
663 )))
664
665 (% class="box infomessage" %)
666 (((
667 Use the following commands to start and stop the TTNv3 service:**     **
668
669 **# start**
670 systemctl start ttnstack
671
672 **# stop**
673 systemctl stop ttnstack
674
675 **# enable**
676 systemctl enable ttnstack
677
678 **#disable**
679 systemctl disable ttnstack
680 )))
681
682 (% class="box infomessage" %)
683 (((
684 Use the following commands to start and stop the Node-Red service:
685
686 **# start**
687 systemctl start nodered
688
689 **# stop**
690 systemctl stop nodered
691
692 **# enable**
693 systemctl enable nodered
694
695 **#disable**
696 systemctl disable nodered
697 )))
698
699
700 * (((
701 === ** How to choose the Chirpstack server frequency SubBand** ===
702 )))
703
704 **~ ** The user has to choose a SubBand if using CN470, US915, AU915, or AS923.
705
706 Note: Since the subbands of the Chirpstack are counted from 0, us915_1 of the Chirpstack is equal to US915 FSB2, so if your LoRa Rdio is using the US915 FSB2 you have to choose the us915_1 as the Chirpstack FSB.
707
708 [[image:image-20230602140406-3.png||height="480" width="918"]]
709
710
711 When the configuration is complete, click** "Save&Apply"**.
712
713
714 (% style="color:red" %)**Note:**(%%) When adding the device profile, the selected Region configuration is also calculated from 0, so setting it to us915_1 corresponds to US915 Sub Band 2.
715
716 [[image:image-20230602143122-4.png||height="511" width="983"]]
717
718
719
720 = 5. Watch Dog =
721
722
723 The watchdog will guard the LPS8V2 to avoid the need to perform a reboot manually after down occurs
724
725
726 LPS8-V2 supports the Watch Dog but is not enabled by the previous releases(2023-11-24 )
727
728 The uses can be via the below method to enable Watch Dog:
729
730 (% class="box infomessage" %)
731 (((
732 wget -P /tmp/ http:~/~/repo.dragino.com/release/tool/watchdog/enable_watchdog.sh && chmod +x /tmp/enable_watchdog.sh && /tmp/enable_watchdog.sh
733 )))
734
735 [[image:image-20231124113209-1.png||height="470" width="1157"]]
736
737
738 = 6. How users can access LPS8-V2 using serial USB =
739
740
741 (% style="color:blue" %)**USB TTL to LPS8-V2  Connection:**
742
743 Port 1 of the UART on the LPS8-V2 is GND
744
745 (% class="box infomessage" %)
746 (((
747 **TXD  <~-~--> UART RXD (Gray line)**
748
749 **RXD  <~-~--> UART TXD (White line)**
750
751 **GND <~-~--> GND (Black line)**
752 )))
753
754 **LPS8v2 UART connection photo**
755
756 [[image:image-20230421094319-2.png||height="351" width="392"]]
757
758 In the PC,you can use the serial port tool(such as [[putty>>url:http://www.chiark.greenend.org.uk/~~sgtatham/putty/download.html]] in Windows), you need to set the serial baud rate to (% style="color:blue" %)**115200**(%%) to access the serial console for LPS8v2. LPS8v2 will output system info once power on as below:
759
760
761 [[image:image-20220804164928-3.png||height="320" width="332"]]
762
763
764 [[image:image-20220804164747-2.png||height="622" width="594"]]
765
766
767 = 7. OTA System Update =
768
769
770 LPS8v2 supports system auto-update via OTA, please see **[[this URL>>url:http://wiki.dragino.com/xwiki/bin/view/OTA%20Update/]]** for the detail of this feature.
771
772
773 == 7.1 Auto-update method ==
774
775
776 The default, each gateway will enable the auto-update function.
777
778 this function will be triggered every boot and every midnight.
779
780
781 Users can enable/disable it via Web Page
782
783 [[image:image-20230607094447-2.png]]
784
785
786 == 7.2 Manual upgrade method ==
787
788
789 1). Using the Linux command to upgrade the system
790
791 (% class="box infomessage" %)
792 (((
793 **apt update && apt install *dragino***
794 )))
795
796
797 2). Upgrade the system via the Web page button of "Manual Update"
798
799 (% style="color:red" %)**Note: this method needs about 10 mins, so you will get the log after 10 mins.  **
800
801 [[image:image-20230607093849-1.png]]
802
803
804 = (% data-sider-select-id="f31494a0-5f58-4b5c-820e-9cb1be76d96f" %)8 How do I view gateway logs(%%) =
805
806 === (% data-sider-select-id="2c782a3d-7138-45c4-bbdf-09c0e27ef896" %)8.1 LoRaWAN Log:(%%) ===
807
808
809 ==== Semtech UDP Log : ====
810
811 When the gateway starts LoRaWAN Semtech UDP, users can check the logs of the Semtech UDP in the **LogRead ~-~-> System Log** interface
812
813 [[image:image-20231017112115-2.png||height="611" width="821"]]
814
815
816 ==== Station Log: ====
817
818 When the gateway starts Basic Station, users can check the logs of the station in the **LogRead ~-~-> System Log** interface
819
820 [[image:image-20231017111606-1.png||height="622" width="821"]]
821
822
823 === (% data-sider-select-id="de76f982-b2e5-4327-aab4-8890814f5f53" %)8.2  4G Log(%%) ===
824
825
826 User needs to access the Linux console of the gateway and enter the following command:
827
828 (% class="box infomessage" %)
829 (((
830 cat /var/log/qmilog.txt
831 )))
832
833 [[image:image-20231017114417-3.png||height="543" width="679"]]
834
835
836 LPS8v2 use **quectel-CM** linux drive for dial up. The manual of this driver can be found here: [[**quectel-CM driver user manual**>>https://www.dropbox.com/scl/fi/73n2jl2c5r8h4i187to4n/Quectel_WCDMA_LTE_Linux_USB_Driver_User_Guide_V1.9-20190212.pdf?rlkey=j8834bw38d4neieisg54zngu9&st=kjsd4zx4&dl=0]].
837
838 Below are some commands as reference:
839
840 >Usage:  /usr/bin/quectel-CM [options]
841 > -s [apn [user password auth]]  Set apn/user/password/auth get from your network provider. auth: 1~~pap, 2~~chap
842 > -p pincode Verify sim card pin if sim card is locked
843 > -p [quectel-][qmi|mbim]-proxy  Request to use proxy
844 > -f logfilename Save log message of this program to file
845 > -u usbmonlog filename  Save usbmon log to file
846 > -i interface Specify which network interface to setup data call when multi-modems exits
847 > -4 Setup IPv4 data call (default)
848 > -6 Setup IPv6 data call
849 > -k pdn Specify which pdn to hangup data call (by send SIGINT to 'quectel-CM -n pdn')
850 > -m iface-idx Bind QMI data call to wwan0_<iface idx> when QMAP used. E.g '-n 7 -m 1' bind pdn-7 data call to wwan0_1
851 > -b Enable network interface bridge function (default 0)
852 > -v Verbose log mode, for debug purpose.[Examples]
853 >Example 1: /usr/bin/quectel-CM
854 >Example 2: /usr/bin/quectel-CM -s 3gnet
855 >Example 3: /usr/bin/quectel-CM -s 3gnet -v
856
857
858
859 === (% data-sider-select-id="ec43d85c-19ec-48b0-a4fc-0ecd76f17fc4" %)8.3 Dmesg Log(%%) ===
860
861
862 Users can check the logs of the Dmesg in the **LogRead ~-~-> System Log** interface:
863
864 [[image:image-20231017115330-5.png||height="565" width="740"]]
865
866
867 === (% data-sider-select-id="3a977a3e-9417-40fa-bdfb-2544a88744a9" %)8.4 Record Log(%%) ===
868
869
870 Users can record DMESG logs and LoRaWAN logs on the **LogRead ~-~->Record Log** interface
871
872 [[image:image-20231017115124-4.png||height="215" width="880"]]
873
874
875 === (% data-sider-select-id="b988f832-4b37-4a61-b951-ff2138ad9cba" %)8.5 View gateway logs via Linux Command(%%) ===
876
877
878 **Semtech UDP Log :**
879
880 (% class="box infomessage" %)
881 (((
882 **journalctl -u draginofwd -f**
883 )))
884
885 [[image:image-20231207144627-1.png||height="371" width="1017"]]
886
887
888 **Station Log:**
889
890 (% class="box infomessage" %)
891 (((
892 **tail -f /var/log/station.log **
893 )))
894
895 [[image:image-20231207144758-2.png||height="132" width="1022"]]
896
897
898 **Dmesg Log:**
899
900 (% class="box infomessage" %)
901 (((
902 **dmesg**
903 )))
904
905 [[image:image-20231207145210-3.png||height="310" width="1021"]]
906
907
908
909 (% data-sider-select-id="65e92cfb-62df-4513-8469-b74edd72dea5" %)
910 = (% data-sider-select-id="ce97a758-4348-4c0c-86eb-412b6b8d3996" %)9. More Services(%%) =
911
912 == (% data-sider-select-id="6b164b64-51ae-4144-8ffd-5cd725b3bb5f" %)9.1 NTP Service/Time Synchronization(%%) ==
913
914 The gateway time sync service is provided by chrony service
915
916
917 === 1). Modify the NTP server address: ===
918
919 (% class="box infomessage" %)
920 (((
921 Configuration file path:  /etc/chrony/chrony.conf
922 )))
923
924
925 === 2). Start/Stop/Enable/Disable NTP service: ===
926
927 (% class="box infomessage" %)
928 (((
929 systemctl start chrony
930 \\systemctl stop chrony
931 \\systemctl disable chrony
932 \\systemctl enable chrony
933 )))
934
935
936 (% data-sider-select-id="61881d06-3f91-437c-8b64-7032dea3c970" %)
937 = (% data-sider-select-id="fb64fcfa-81b6-41b5-ae81-81d94960d7dd" %)10. More features(%%) =
938
939 (% data-sider-select-id="692f00f1-a7cc-4954-ac62-0a5dddb0a0c6" %)
940 == (% data-sider-select-id="ec6a5e23-ba91-46d9-8042-1e4c6a7b3b36" %)10.1 Chirpstack MQTT Forwarder(%%) ==
941
942
943 ChirpStack MQTT Forwarder is a MQTT packet forwarder for LoRa gateways. By default it forwards packets in Protobuf binary format, optionally it can be configured to use JSON encoding for debugging. In contrast to the ChirpStack Gateway Bridge, this component must always be installed on the gateway.
944
945
946 (% data-sider-select-id="d2b54844-aad8-4198-9f17-841cd68db9b3" %)
947 === (% data-sider-select-id="fb64fcfa-81b6-41b5-ae81-81d94960d7dd" %)10(% data-sider-select-id="0870eb11-ff25-47fc-9e3c-80a68bbf3933" %).1.1 Configure Packet Forwarder(%%) ===
948
949 In the Dragino web-interface, you must configure the Packet Forwarder such that it forwards to localhost on port 1700.
950
951 (% data-sider-select-id="48576a4e-42ef-4ac9-83b4-122fc10c6629" %)
952 By default, the web-interface can be accessed by entering the following URL in your browser: (% data-sider-select-id="c2683c51-0bf8-4ac5-87be-c50edacc8f4b" %)**http:~/~/GATEWAY-IP-ADDRESS**(%%) (replace GATEWAY-IP-ADDRESS by the actual IP address of your gateway). The default credentials are root / dragino.
953
954 * In the **LoRaWAN** menu, click **LoRaWAN ~-~- Semtech UDP**
955 * Configure the following settings:
956 ** **Service Provider:** //Custom / Private LoRaWAN//
957 ** **Server Address:** localhost
958 ** **Uplink Port:** 1700
959 ** **Downlink Port:** 1700
960 * Click **Save & Apply**
961
962 [[image:image-20240518145929-2.png||height="652" width="727"]]
963
964
965 (% data-sider-select-id="716df9b1-d844-4797-bce9-9b1adf49b072" %)
966 === (% data-sider-select-id="fb64fcfa-81b6-41b5-ae81-81d94960d7dd" %)10(% data-sider-select-id="ffba644f-a9d5-4e93-a9da-9f9e49d596d9" %).1.2 Install ChirpStack MQTT Forwarder(%%) ===
967
968
969 (% data-sider-select-id="2a752131-c23e-4da4-b142-5880dd688c39" %)
970 (% data-sider-select-id="833bbe42-c175-4e13-ab7a-c8abc30378d0" %)**SSH login**
971
972 First you must login into the gateway using SSH:
973
974 (% class="box infomessage" data-sider-select-id="608a94b0-8dee-453d-9433-5fe12c6559e5" %)
975 (((
976 ssh root@GATEWAY-IP-ADDRESS
977 )))
978
979 (% data-sider-select-id="63adc977-8227-4585-ab1d-eea44a01c34c" %)
980 The default password is: (% data-sider-select-id="5fad2844-9bd3-49e2-979b-ffd184b923cf" %)**dragino**(%%).
981
982
983 (% data-sider-select-id="216fb9b4-6cee-4cb6-8b71-0a9cda3bd96a" %)
984 (% data-sider-select-id="914750d6-03c5-48fe-ad27-49e99d95d877" %)**Download **(% data-sider-select-id="94e274ee-d341-40dc-8ca8-dc3c3b4c4981" %)**package**
985
986 (% data-sider-select-id="f95485e3-b535-4ea2-b0aa-0c46b5254782" %)
987 Use the following commands to download the latest version of the ChirpStack MQTT Forwarder package:
988
989 (% class="box infomessage" data-sider-select-id="ab1338ab-a215-4185-8552-1efd6e067858" %)
990 (((
991 cd /tmp
992 wget https:~/~/artifacts.chirpstack.io/downloads/chirpstack-mqtt-forwarder/chirpstack-mqtt-forwarder_4.3.0_linux_armhf.deb
993 )))
994
995
996 (% data-sider-select-id="e59f1bad-427f-47b8-bc97-a818490576c4" %)
997 (% data-sider-select-id="1b512eaf-c564-4835-afac-548b9a6a7045" %)**Install **
998
999 Use the dpkg package-manager to install the downloaded package. Example:
1000
1001 (% class="box infomessage" data-sider-select-id="7e7ff0cf-c367-4ff0-9387-f4eb82f3c89e" %)
1002 (((
1003 dpkg -i chirpstack-mqtt-forwarder_4.3.0_linux_armhf.deb
1004 )))
1005
1006 [[image:image-20240518152148-4.png]]
1007
1008
1009 (% data-sider-select-id="69e4a485-6ea8-46e7-97a3-8666bc9423a7" %)
1010 **Configuration**
1011
1012 To connect the ChirpStack MQTT Forwarder to your MQTT broker, you must update the ChirpStack MQTT Forwarder configuration file.
1013
1014 (% data-sider-select-id="e98443ef-dcc1-4be1-ad3e-ec31b0a580b4" %)
1015 This file is located at: (% data-sider-select-id="60301edc-5082-44e9-a91a-688327092116" %)**/etc/chirpstack-mqtt-forwarder/chirpstack-mqtt-forwarder.toml**
1016
1017
1018 **ChirpStack MQTT Forwarder Setting:**
1019
1020 (% class="box" data-sider-select-id="1d70062d-64ab-410b-bd8e-476c73d5dd70" %)
1021 (((
1022 topic_prefix  ~-~->  This corresponds to the frequency of the ChirpStack server
1023
1024 server  ~-~->  Fill in the ChirpStack server address, Example: tcp:~/~/10.130.2.15:1883
1025 )))
1026
1027 username,password,ca_cert,tls_cert,tls_key parameters should be set as required.
1028
1029
1030 Use commands to modify configuration files:
1031
1032 (% class="box infomessage" data-sider-select-id="d552b27f-cfd2-4f5a-9b7f-b627f5dd3387" %)
1033 (((
1034 vim /etc/chirpstack-mqtt-forwarder/chirpstack-mqtt-forwarder.toml
1035 )))
1036
1037 [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20All%20Gateway%20models/LPS8N%20-%20LoRaWAN%20Gateway%20User%20Manual/WebHome/image-20240518141059-6.png?rev=1.1||alt="image-20240518141059-6.png"]]
1038
1039
1040 **(Re)start and stop commands**
1041
1042 Use the following commands to (re)start and stop the ChirpStack MQTT Forwarder service:
1043
1044 (% class="box infomessage" data-sider-select-id="61c3c343-2cb9-4b07-8741-5d5da2d88ec3" %)
1045 (((
1046 # start
1047
1048 (% data-sider-select-id="5482a31e-3aa0-403c-aec5-117839958068" %)
1049 systemctl start chirpstack-mqtt-forwarder
1050
1051 # stop
1052
1053 systemctl stop chirpstack-mqtt-forwarder
1054
1055 # restart
1056
1057 systemctl restart chirpstack-mqtt-forwarder
1058 )))
1059
1060 (% data-sider-select-id="1cea423f-9653-47e6-8022-aadcb684f191" %)
1061 (% data-sider-select-id="f385e712-68bc-48fd-8b94-67a0c7e7cb70" %)**Note: If the LPS8v2 built-in server is running, it will cause a port conflict**
1062
1063
1064 **Check result**
1065
1066 (% data-sider-select-id="43d1d40a-2620-4547-b00d-f78dd5427215" %)
1067 Use "** journalctl -u chirpstack-mqtt-forwarder -f(% data-sider-select-id="ab74df8a-b859-4afa-9c26-d0807e860e6c" %) (%%)**" to check the operation of ChirpStack MQTT Forwarder.
1068
1069 [[image:image-20240518154223-5.png]]
1070
1071 [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20All%20Gateway%20models/LPS8N%20-%20LoRaWAN%20Gateway%20User%20Manual/WebHome/image-20240518143050-8.png?width=1170&height=702&rev=1.1||alt="image-20240518143050-8.png"]]
1072
1073
1074 == (% data-sider-select-id="de90793f-d833-4885-8b59-d0880f7256e6" %)10.2 As a Data-only hotspot connect the helium blockchain(%%) ==
1075
1076
1077 (% class="box infomessage" %)
1078 (((
1079 (% data-sider-select-id="3359233b-fcc9-4415-9bee-4151919fbb2e" %)
1080 apt update && apt install helium-gateway
1081 )))
1082
1083
1084 == (% data-sider-select-id="de90793f-d833-4885-8b59-d0880f7256e6" %)10.3 (%%)How does LPS8v2 filter unwanted lorawan packets ==
1085
1086
1087 This feature is to filter the unwanted LoRaWAN packets. Purpose is to save the upstream traffic especially for a 4G cellular connection.
1088
1089 Please refer to the link below for specific usage：**[[Filter unwanted LoRaWAN packets>>https://wiki.dragino.com/xwiki/bin/view/Main/Filter%20unwanted%20LoRaWAN%20packets/]]**
1090
1091
1092 = (% data-sider-select-id="20d4ea6b-7328-46c6-bc97-f0050cfe382e" %)11. FAQ(%%) =
1093
1094 == (% data-sider-select-id="9fbcac50-3c87-43d9-8611-8d311fcb7820" %)11.1 How to change Hostname(%%) ==
1095
1096
1097 By default, Hostname is dragino-xxxxxx,If the user needs to change the hostname, the user needs to access the linux console of LPS8v2 and enter the following command:
1098
1099 (% class="box infomessage" %)
1100 (((
1101 hostnamectl set-hostname dragino-123456
1102 )))
1103
1104 [[image:image-20230517102429-1.png]]
1105
1106 After the configuration is complete, run "reboot" to restart the gateway.
1107
1108
1109 == (% data-sider-select-id="20d4ea6b-7328-46c6-bc97-f0050cfe382e" %)11(% data-sider-select-id="62cdc3f4-fb6f-4e4d-92a5-60449c8b462f" %).2 Build-in The Things Network migrate to ChirpStack(%%) ==
1110
1111
1112 Migrate guide:
1113
1114 To stabilize the completion of the migration, The users can migrate in one of the following ways
1115
1116 **Method 1. Using the Linux shell, **
1117
1118 **Method 2. Flash a new image with the Chirpstack**
1119
1120
1121 === Method 1: Using the Linux shell ===
1122
1123 (% class="box infomessage" %)
1124 (((
1125 wget -P /tmp [[http:~~/~~/repo.dragino.com/release/tool/chirpstack/migrate_chirpstack>>http://repo.dragino.com/release/tool/chirpstack/migrate_chirpstack]] && chmod +x /tmp/migrate_chirpstack && /tmp/migrate_chirpstack
1126 )))
1127
1128
1129 === Method 2: Flash a new image ===
1130
1131 Image flash steps: [[How to flash a new image(OS) to the gateway(LPS8V2)>>http://wiki.dragino.com/xwiki/bin/view/Main/Armbian%20OS%20instruction/#H2.3A0Howtoflashanewimage28OS29tothegateway28LPS8V229]]
1132
1133
1134 == (% data-sider-select-id="20d4ea6b-7328-46c6-bc97-f0050cfe382e" %)11(% data-sider-select-id="b2a44672-8abb-425d-a823-f2faa334cdb7" %).3 How to reduce the 4g data consumed(%%) ==
1135
1136
1137 1). The gateway will check the network via ping 1.1.1.1/8.8.8.8 which will consume a lot of data, you can set the interval time to reduce data consume.
1138
1139 [[image:image-20230719100239-1.png||height="724" width="994"]]
1140
1141
1142 2. Change the LoRa status package interval time: It does not affect the connection between the gateway and the server, just the status packet interval
1143
1144 [[image:image-20230719100332-2.png]]
1145
1146
1147 3. Disable the auto-update:
1148
1149 [[image:image-20230719100419-3.png||height="458" width="995"]]
1150
1151
1152 == (% data-sider-select-id="20d4ea6b-7328-46c6-bc97-f0050cfe382e" %)11(% data-sider-select-id="457c03ce-1aaa-44c6-bf8e-0298ca8045e4" %).4 How to change built-in LoRaWAN Server from ChirpStack v4 to TTN Stack v3.(%%) ==
1153
1154
1155 By default, the LPS8v2's built-in server is ChirpStack v4,
1156
1157 If the user needs to change the built-in server from ChirpStack v4 to TTN Stack v3, the User needs to download the image and flash it to the LPS8v2 gateway:
1158
1159 [[https:~~/~~/www.dropbox.com/scl/fi/qwtaw4i4dqonzramr93e4/dragino-LPS8V2-TTN-231124.rar?rlkey=nrftlkd1h8en6j07vzbhpj9ui&dl=0>>https://www.dropbox.com/scl/fi/qwtaw4i4dqonzramr93e4/dragino-LPS8V2-TTN-231124.rar?rlkey=nrftlkd1h8en6j07vzbhpj9ui&dl=0]]
1160
1161
1162 Image flash steps: [[How to flash a new image(OS) to the gateway(LPS8V2)>>http://wiki.dragino.com/xwiki/bin/view/Main/Armbian%20OS%20instruction/#H2.3A0Howtoflashanewimage28OS29tothegateway28LPS8V229]]
1163
1164
1165 == (% data-sider-select-id="20d4ea6b-7328-46c6-bc97-f0050cfe382e" %)11(% data-sider-select-id="457c03ce-1aaa-44c6-bf8e-0298ca8045e4" %).5 (%%)How to check my USB port dev/tty after i plug in USB device. ==
1166
1167
1168 When an external USB device is connected to LPS8v2, the user can access the Linux console of the LPS8v2 gateway and run the following command to check the USB port dev/tty:
1169
1170 (% class="box infomessage" %)
1171 (((
1172 dmesg
1173 )))
1174
1175 [[image:image-20240803095144-1.png]]
1176
1177
1178
1179 == (% data-sider-select-id="20d4ea6b-7328-46c6-bc97-f0050cfe382e" %)11(% data-sider-select-id="82550df9-987d-4f58-9877-86a0c5e621a4" %).6 DIN Mount Reference:(%%) ==
1180
1181
1182 [[image:image-20240318095605-1.jpeg||height="472" width="472"]]
1183
1184 [[image:image-20240318095617-2.png]]
1185
1186
1187
1188
1189 = (% data-sider-select-id="9b024263-b754-45b6-ac15-22f86a4e1436" %)12. Trouble Shooting(%%) =
1190
1191 == (% data-sider-select-id="cb7a0b2f-4144-4f58-86d0-64a15944840e" %)12.1  I can't log in to the built-in Server TTN Stack which shows '**Login failed**'.(%%) ==
1192
1193 [[image:image-20220920135918-1.png]]
1194
1195
1196 This is caused by the inconsistency between the built-in TTN-Stack domain configuration and your login URL.
1197
1198 By default, ttn-stack uses the gateway's domain name for URL resolution, but in some networks, they prefer to resolve IP-v4 addresses.
1199
1200
1201 So you can change the domain name of the TTN-Stack configuration to the IPv4 address.
1202
1203 **Click the update URL button to configure the URL with the current eth port address.**
1204
1205 [[image:image-20220920141936-2.png]]
1206
1207
1208 == (% data-sider-select-id="9b024263-b754-45b6-ac15-22f86a4e1436" %)12(% data-sider-select-id="f34b4950-25aa-4a6d-a2b4-4af0ec0010a7" %).2  The built-in TTN status is "Not Running" and the URI is "dragino-123456". How users fix this problem(%%) ==
1209
1210
1211 When this problem occurs, click "**Update To DEFAULT**" ,this problem will be fixed.
1212
1213 [[image:image-20230508171607-1.png]]
1214
1215
1216 == (% data-sider-select-id="9b024263-b754-45b6-ac15-22f86a4e1436" %)12(% data-sider-select-id="a7b8cd40-2ec5-4b4b-8220-d32ce0a303a0" %).3  Fallback IP does not work, how can users check(%%) ==
1217
1218
1219 When the computer has completed the above fallback IP configuration,the LPS8v2 Web UI is still not accessible via fallback IP.
1220
1221
1222 **~1. Check whether the configuration is correct**
1223
1224 Run the CMD command to ipconfig and ping 172.31.255.254.
1225
1226 If this fails, the user needs to reconfigure.
1227
1228 [[image:image-20230413170224-3.png||height="433" width="707"]]
1229
1230 [[image:image-20230413170246-4.png]]
1231
1232
1233 **2. Check whether the firewall is disabled**
1234
1235 If the firewall is not down, this will affect access to the gateway.
1236
1237
1238 == (% data-sider-select-id="9b024263-b754-45b6-ac15-22f86a4e1436" %)12(% data-sider-select-id="b7eec45b-ad8c-4621-a815-f457810d25f4" %).4  Click "Manual_Update", why there is no response?(%%) ==
1239
1240
1241 When you click "Manual_Update", the gateway will finish updating within 10 minutes and display the update log.
1242
1243
1244 [[image:image-20230527090555-3.png||height="660" width="832"]]
1245
1246
1247 == (% data-sider-select-id="9b024263-b754-45b6-ac15-22f86a4e1436" %)12(% data-sider-select-id="ac1f33b3-1f28-477d-880c-534ac36adcbe" %).5  Why the LPS8V2's Access Point does not do not appear & Fallback IP unable to access(%%) ==
1248
1249
1250 Earlier versions of the LPS8V2 which missing the AP driver and not installed the fallback package, so the users have to do an extra update.
1251
1252 (% class="box infomessage" %)
1253 (((
1254 apt update && apt install *dragino*
1255
1256 wget -P /tmp/ [[http:~~/~~/repo.dragino.com/release/hp0c-packages/linux-image-current-draginohp0z_22.05.2_armhf.deb>>http://repo.dragino.com/release/hp0c-packages/linux-image-current-draginohp0z_22.05.2_armhf.deb]] && dpkg -i /tmp/[[linux-image-current-draginohp0z_22.05.2_armhf.deb>>http://repo.dragino.com/release/hp0c-packages/linux-image-current-draginohp0z_22.05.2_armhf.deb]]
1257 )))
1258
1259
1260 == (% data-sider-select-id="9b024263-b754-45b6-ac15-22f86a4e1436" %)12(% data-sider-select-id="0621ef51-7fc1-47ca-86ee-cc1f28f6754b" %).6  How to reset the built-in server(%%) ==
1261
1262
1263 **1) Build-in The Things Network**
1264
1265 Refer to this link to delete the Built-in server's device.
1266
1267 [[Delete devices from Build-in The Things Network>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Delete%20devices%20from%20Build-in%20The%20Things%20Network/]]
1268
1269
1270 **2) Build-in Chirpstack**
1271
1272 Users need to click "Reset" on the Server~-~->NetServer interface, ChirpStack will be reset.
1273
1274 [[image:image-20231106180846-5.png||height="310" width="668"]]
1275
1276
1277 = (% data-sider-select-id="7e5e9cb1-c1dc-4ea9-a9f7-9da676c581a5" style="color:inherit; font-family:inherit; font-size:29px" %)13. Supports(%%) =
1278
1279
1280 (((
1281 If you are experiencing issues and can't solve them, you can send mail to [[support@dragino.com>>mailto:support@dragino.com]].
1282 )))
1283
1284 (((
1285 With your question as detailed as possible. We will reply and help you in the shortest.
1286
1287
1288 = (% data-sider-select-id="f8ca68c9-99ed-4795-97c5-3d0d259131e9" %)14. Reference(%%) =
1289
1290
1291 * Install Tago Core: Refer **Install Tago Core in LPS8v2** in[[ Instruction>>doc:Main.Tago\.IO.WebHome]].
1292 * [[Advance OS Reference Guide for LPS8v2>>doc:Main.Armbian OS instruction.WebHome]].
1293
1294
1295 )))
1296
1297 = (% data-sider-select-id="a056b4ad-7d05-42b4-ad74-7a3134f8010a" %)15. Order Info(%%) =
1298
1299
1300 (% style="color:#0000ff" %)**LPS8v2-XXX-YYY**
1301
1302 (% style="color:#0000ff" %)**XXX**(% style="color:black" %): Frequency Band
1303
1304 * (% style="color:red" %)**AS923**(%%): LoRaWAN AS923 band
1305
1306 * (% style="color:red" %)**AU915**(%%): LoRaWAN AU915 band
1307
1308 * (% style="color:red" %)**EU868**(%%): LoRaWAN EU868 band
1309
1310 * (% style="color:red" %)**KR920**(%%): LoRaWAN KR920 band
1311
1312 * (% style="color:red" %)**US915**(%%): LoRaWAN US915 band
1313
1314 * (% style="color:red" %)**IN865**(%%):  LoRaWAN IN865 band
1315
1316 (% style="color:#0000ff" %)**YYY**(% style="color:black" %): 4G Cellular Option
1317
1318 * (% style="color:red" %)**EC25-E**(% style="color:black" %):  EMEA, Korea, Thailand, India
1319
1320 * (% style="color:red" %)**EC25-AFX**(% style="color:black" %): America:Verizon, AT&T(FirstNet), U.S.Cellular; Canada:Telus
1321
1322 * (% style="color:red" %)**EC25-AUX**(% style="color:black" %): Latin America, New Zeland, Taiwan
1323
1324 * (% style="color:red" %)**EC25-J**(% style="color:black" %):  Japan, DOCOMO, SoftBank, KDDI
1325
1326 More info about valid bands, please see [[EC25-E product page>>url:https://www.quectel.com/product/ec25.htm]].
1327
1328
1329 = (% data-sider-select-id="a4433cd3-3bbc-4e6b-8b18-0bd2bc4d6904" %)16. Manufacturer Info(%%) =
1330
1331
1332 **Shenzhen Dragino Technology Development co. LTD**
1333
1334 Room 202, Block B, BCT Incubation Bases (BaoChengTai),  No.8 CaiYunRoad
1335
1336 LongCheng Street, LongGang District ; Shenzhen 518116,China
1337
1338
1339 = (% data-sider-select-id="b353afd6-b0f5-48e5-a114-3b5062cbf0d1" %)17. FCC Warning(%%) =
1340
1341
1342 (((
1343 This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates uses and can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications. However, there is no guarantee that interference will not occur in a particular installation. If this equipment does cause harmful interference to radio or television reception, which can be determined by turning the equipment off and on, the user is encouraged to try to correct the interference by one or more of the following measures:
1344 )))
1345
1346 (((
1347 ~-~- Reorient or relocate the receiving antenna.
1348 )))
1349
1350 (((
1351 ~-~- Increase the separation between the equipment and receiver.
1352 )))
1353
1354 (((
1355 ~-~- Connect the equipment into an outlet on a circuit different from that to which the receiver is connected.
1356 )))
1357
1358 (((
1359 ~-~- Consult the dealer or an experienced radio/TV technician for help.
1360 )))
1361
1362
1363 (((
1364 Changes or modifications not expressly approved by the party responsible for compliance could void the user's authority to operate the equipment.
1365 )))
1366
1367
1368 (((
1369 The antenna(s) used for this transmitter must be installed to provide a separation distance of at least 20 cm from all persons and must not be co-located or operating in conjunction with any other antenna or transmitter.
1370
1371
1372 )))
1373 )))