Skip to Content
Last modified by Kilight Cao on 2025/07/14 15:15
Show last authors
1 (% style="text-align:center" %)
2 (((
3 [[image:image-20231127105359-1.png||data-xwiki-image-style-alignment="center" _mstalt="430768" height="453" width="453"]]
4
5
6 (% style="display:none" %) (%%)
7
8
9
10 )))
11
12 **Table of Contents:**
13
14 {{toc/}}
15
16
17
18
19
20
21 = 1. Introduction =
22
23 == 1.1 What is MS48-LR ==
24
25
26 (((
27 (((
28 The MS48-LR  is an open-source LoRaWAN gateway that can (% style="color:blue" %)**convert LoRaWAN to Modbus RTU/TCP**(%%). 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.
29 )))
30
31 (((
32 The MS48-LR is fully compatible with LoRaWAN protocol. MS48-LR includes a (% style="color:blue" %)**built-in LoRaWAN Server and IoT server**(%%), User can connect virous LoRaWAN devices to MS48-LR, and use PLC to access these devices via Modbus network, MS48-LR eliminates the need to add additional lorawan gateways to implement (% style="color:blue" %)**LoRaWAN to Modbus RTU/TCP**(%%).
33 )))
34
35 (((
36 Different countries use different LoRaWAN frequency bands. MS48-LR has these bands pre-configured. Users can also customize the frequency bands to use in their own LoRa network.
37 )))
38
39 (((
40 MS48-LR supports (% style="color:blue" %)**remote management**(%%). System Integrator can easy to remote monitor the gateway and maintain it.
41
42
43 == 1.2 How does it work? ==
44
45
46 The MS48-LR can run as a Modbus RS485-RTU slave, which converts the LoRaWAN sensor upstream data into modbus data and writes it into the register of the 03 function code
47
48 [[image:image-20231111103753-1.png||_mstalt="427583" height="585" width="1031"]]
49
50
51 )))
52
53 == 1.3 Specifications ==
54
55
56 (% style="color:#037691" %)**Hardware System:**
57
58 * CPU: Quad-core Cortex-A7 1.2Ghz
59 * RAM: 512MB
60 * eMMC: 4GB
61
62 (% style="color:#037691" %)**Interface:**
63
64 * 10M/100M RJ45 Ports x 1
65 * Multi-Channel LoRaWAN Wireless
66 * WiFi 802.11 b/g/n
67 * USB 2.0 host connector x 1
68 * Mini-PCI E connector x 1
69 * RS485 Interface x 1
70 * RS232 Interface x 1
71
72 (% style="color:#037691" %)**LoRa Spec:**
73
74 * Up to -140 dBm sensitivity with SX1250 Tx/Rx front-end
75 * 70 dB CW interferer rejection at 1 MHz offset
76 * Able to operate with negative SNR, CCR up to 9dB
77 * 8 x 8 channels LoRa packet detectors,8 x SF5-SF12 LoRa demodulators,8 x SF5-SF10 LoRa demodulators,125/250/500 kHz LoRa demodulator and 1 x (G)FSK demodulator
78 * Dual digital TX & RX radio front-end interfaces
79 * 10 programmable parallel demodulation paths
80 * Dynamic data-rate (DDR) adaptation
81 * True antenna diversity or simultaneous dual-band operation
82
83 (% style="color:#037691" %)**Cellular 4G LTE (optional):**
84
85 * Quectel: [[**EC25 LTE module**>>url:https://www.quectel.com/product/ec25minipcie.htm||_mstmutation="1"]]
86 * Standard Size SIM Slot
87 * 2 x 4G Sticker Antenna.
88 * Up to 150Mbps downlink and 50Mbps uplink data rates
89 * Worldwide LTE,UMTS/HSPA+ and GSM/GPRS/EDGE coverage
90 * MIMO technology meets demands for data rate and link reliability in modem wireless communication systems
91
92 (% style="color:#037691" %)**Operating Condition:**
93
94 * Work Temperature: -20 ~~ 70°C
95 * Storage Temperature: -20 ~~ 70°C
96 * Power Input: 12V, 2A, DC
97
98 == 1.4 Features ==
99
100
101 * Open Source Debian system
102 * Managed by Web GUI, SSH via WAN or WiFi
103 * Remote Management
104 * Auto-provisioning for batch deployment and management
105 * LoRaWAN Gateway
106 * 10 programmable parallel demodulation paths
107 * Pre-configured to support different LoRaWAN regional settings.
108 * Allow customizing LoRaWAN regional parameters.
109 * Different kinds of LoRaWAN Connections such as
110 ** Semtech UDP Packet Forwarder
111 ** LoRaWAN Basic Station
112 ** ChirpStack-Gateway-Bridge (MQTT)
113 * Built-in (% style="color:#037691" %)**ChirpStack**(%%) local LoRaWAN server
114 * Built-in  (% style="color:#037691" %)**Node-Red**(%%) local Application server
115 * Act as Modbus Slave mode
116
117 == 1.5 LED Indicators ==
118
119
120 MS48-LR has totally four LEDs, They are:
121
122 (% style="color:blue" %)**➢ LED 1 (ETH LED):**(%%) This GREEN LED will blink GREEN when the ETH port is connecting
123
124 (% style="color:blue" %)**➢ LED 2 (RET LED):**(%%) This GREEN LED will show different colors in different states:
125
126 ✓  **SOLID GREEN:** When the Long press 4-5s Toggle button,the device will reload the Network and Initialize wifi configuration,This GREEN LED will SOLID GREEN Until the reload is finished.
127
128 ✓  **BLINKING GREEN:** When the Long press 10s Toggle button,the device will restore the factory settings,This GREEN LED will BLINKIND GREEN Until the restore is finished.
129
130 (% style="color:blue" %)**➢ LED 3:**(%%) This GREEN LED is undefined
131
132 (% style="color:blue" %)**➢ LED 4 (Power LED):**(%%) This GREEN LED will be solid if the device is properly powered
133
134 (% style="color:blue" %)**➢ LED 5 (WIFI LED): **(%%)This LED shows the WIFI interface connection status.
135
136 ✓  **SOLID GREEN:** The device enables the WiFi WAN Client and connects to the WiFi successfully.
137
138 ✓  **BLINKING GREEN:** The device's WiFi WAN Client connection is unsuccessful.
139
140 ✓**  OFF:** The device WiFi WAN Client is not enabled.
141
142 (% style="color:blue" %)**➢ LED 6 (SYS LED):**(%%) This GREEN LED will show different colors in different states:
143
144 ✓  **SOLID GREEN:** The device is alive with a LoRaWAN server connection.
145
146 ✓  **BLINKING GREEN:** a)  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
147
148 ✓**  OFF:** Device doesn't have an Internet connection.
149
150
151 == 1.6 RS485 & RS232 interface ==
152
153 [[image:image-20240108150505-1.png||_mstalt="428103" height="576" width="678"]]
154
155
156 == 1.7 Button Instruction ==
157
158
159 The MS48-LR has two black buttons, which are:
160
161
162 **RST: **Press and release, and the gateway will restart
163
164 **LED status: ** All LEDs are off except for the LED 4 (Power LED).
165
166
167 **Toggle:**
168
169 (% style="color:blue" %)**//➢ //Long press 4-5s :                     **(%%)the gateway will reload the Network and Initialize wifi configuration
170
171 // // (% _mstmutation="1" %)**LED status: **(%%) LED 2 (RET LED) will SOLID GREEN Until the reload is finished.
172
173 (% style="color:blue" %)**➢ Long press more than 10s:    **(%%)the gateway will restore the factory settings.
174
175 (% _mstmutation="1" %)**LED status: **(%%) LED 2 (RET LED) will BLINKIND GREEN Until the restore is finished.
176
177
178
179 == 1.8 Installation ==
180
181
182 [[image:image-20240122115220-1.png||_mstalt="425412"]]
183
184
185 = 2. Quick Start =
186
187
188 The MS48-LR supports network access via Ethernet or Wi-Fi connection and runs without a network.
189
190 In most cases, the first thing you need to do is make the MS48-LR accessible to the network.
191
192
193 == 2.1 Access and Configure MS48-LR ==
194
195 === 2.1.1 Find IP address of MS48-LR ===
196
197
198 ==== (% style="color:blue" %)**Method 1**(%%):  Connect via MS48-LR WiFi ====
199
200
201 At the first boot of MS48-LR, it will auto generate a WiFi network called (% style="color:green" %)**//dragino-xxxxxx //**(%%)with password:
202
203 (% style="background-color:yellow" %)**dragino+dragino**
204
205 User can use a PC to connect to this WiFi network. The PC will get an IP address 10.130.1.xxx and the MS48-LR has the default IP (% style="color:green" %)**10.130.1.1**
206
207
208
209 [[image:image-20240119093621-1.png||_mstalt="429988" height="365" width="850"]]
210
211 [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20All%20Gateway%20models/HP0C/WebHome/image-20230527085250-2.png?width=284&height=495&rev=1.1||alt="image-20230527085250-2.png" _mstalt="430508"]]
212
213
214 ==== (% style="color:blue" %)**Method 2**(%%):  Connect via Ethernet with DHCP IP from the router ====
215
216
217 (((
218 Connect the MS48-LR Ethernet port to your router and MS48-LR 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 MS48-LR.
219 )))
220
221 (((
222 You can also use this IP to connect.
223 )))
224
225
226 [[image:image-20240119093637-2.png||_mstalt="432705" height="372" width="1141"]]
227
228
229 ==== (% style="color:blue" %)**Method 3**(%%):  Connect via MS48-LR Fallback IP ====
230
231 [[image:image-20240119093652-3.png||_mstalt="432029"]]
232
233
234
235 (% style="color:blue" %)**Steps to connect via fallback IP:**
236
237 ~1. Connect the PC's Ethernet port to MS48-LR's WAN port
238
239 2. Configure PC's Ethernet port has IP: 172.31.255.253 and Netmask: 255.255.255.252
240
241
242 **Settings ~-~-> Network & Internet ~-~-> Ethernet ~-~-> Change advanced sharing options ~-~-> Double-click"Ethernet" ~-~-> Internet Protocol Version 4 (TCP/IPv4)**
243
244
245 As in the below photo:
246
247
248 [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20All%20Gateway%20models/HP0C/WebHome/image-20230413172038-1.png?width=1243&height=732&rev=1.1||alt="image-20230413172038-1.png" _mstalt="429143"]]
249
250 Configure computer Ethernet port steps video: **[[attach:fallback ip.mp4||target="_blank"]]**
251
252 If you still can't access the MS48-LR 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]]**
253
254
255 3. In the PC, use IP address 172.31.255.254 to access the MS48-LR via Web or Console.
256
257 [[image:image-20240119093803-4.png||_mstalt="431730" height="664" width="1217"]]
258
259
260 ==== (% style="color:blue" %)**Method 4**(%%):  Connect via WiFi with DHCP IP from the router ====
261
262
263 [[image:image-20240119093834-5.png||_mstalt="433407" height="336" width="1020"]]
264
265 Fill in the WiFi information by checking the box and clicking (% style="color:red" %)**Save&Apply**
266
267 [[image:image-20240119093902-6.png||_mstalt="432432" height="382" width="1082"]]
268
269
270 **Wi-Fi configuration successful**
271
272 [[image:image-20240119093944-7.png||_mstalt="434772" height="562" width="1093"]]
273
274
275 === 2.1.2 Access Configure Web UI ===
276
277
278 **Web Interface**
279
280 Open a browser on the PC and type the MS48-LR ip address (depends on your connect method)
281
282 [[**//http:~~/~~/IP_ADDRESS //**>>url:http://ip_address/]] or //**[[http:~~/~~/172.31.255.254>>url:http://172.31.255.254(/]]**//(Fallback IP)
283
284 You will see the login interface of MS48-LR as shown below.
285
286 The account details for Web Login are:
287
288 **User Name: root**
289
290 **Password:   dragino**
291
292 [[image:image-20240320134426-1.png||_mstalt="428285"]]
293
294
295 == 2.2  Typical Network Setup ==
296
297 === 2.2.1  Overview ===
298
299
300 MS48-LR supports flexible network set up for different environment. This section describes the typical network topology can be set in MS48-LR. The typical network set up includes:
301
302 * **WAN Port Internet Mode**
303
304 * **WiFi Client Mode**
305
306 * **Cellular Mode**
307
308 === 2.2.2  Use the WAN port to access the Internet ===
309
310
311 By default, the MS48-LR is set to use the WAN port to connect to an upstream network. When you connect the MS48-LR's WAN port to an upstream router, MS48-LR will get an IP address from the router and have Internet access via the upstream router. The network status can be checked on the (% style="color:blue" %)**home page**:
312
313 [[image:image-20240108114745-4.png||_mstalt="431171" height="471" width="912"]]
314
315
316 === 2.2.3  Access the Internet as a WiFi Client ===
317
318
319 In the WiFi Client Mode, MS48-LR acts as a WiFi client and gets DHCP from an upstream router via WiFi.
320
321 The settings for WiFi Client is under page (% style="color:blue" %)**Network ~-~-> Wi-Fi**
322
323 [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20All%20Gateway%20models/HP0C/WebHome/image-20230411095739-1.png?width=691&height=264&rev=1.1||alt="image-20230411095739-1.png" _mstalt="432341"]]
324
325
326 In the WiFi Survey Choose the WiFi AP, and input the Passphrase then click(% style="color:blue" %)** Save & Apply**(%%) to connect.
327
328 [[image:image-20240108114602-3.png||_mstalt="428181" height="477" width="925"]]
329
330
331 === 2.2.4  Use built-in 4G modem for internet access ===
332
333
334 Users can see whether MS48-LR has EC25 on the label of the gateway to determine whether there is 3G/4G Cellular modem.
335
336 If the MS48-LR has 3G/4G Cellular modem, user can use it as main internet connection or back up.
337
338 First, install the Micro SIM card as below direction
339
340 Second, Power off/ ON MS48-LR to let it detect the SIM card.
341
342 [[image:image-20240320134750-2.png||_mstalt="428532"]]
343
344
345 The set up page is (% style="color:blue" %)**Network ~-~-> Cellular**
346
347 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.
348
349 [[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" _mstalt="294190"]]
350
351
352 When cellular fails to connect or has problems, users can refer to this link to Trouble Shooting:**[[How to Trouble Shooting if Cellular connection fails>>https://wiki.dragino.com/xwiki/bin/view/Main/Notes%20for%20cellular%20network%20connection/#H2.2ForLPS8v22FMS48-LR]]**
353
354
355 === 2.2.5  Check Internet connection ===
356
357
358 In the (% style="color:blue" %)**Home**(%%) page, we can check the Internet connection.
359
360 * 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" _mstalt="297271"]] : This interface has Internet connection.
361 * 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" _mstalt="293215"]] : This interface has IP address but don't use it for internet connection.
362 * 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" _mstalt="297557"]] : This interface doesn't connected or no internet.
363
364 (% class="wikigeneratedid" %)
365 [[image:image-20240108115101-6.png||_mstalt="427674" height="467" width="905"]]
366
367
368 == 2.3 Bridge LoRaWAN network to Modbus network ==
369
370
371 By following the steps below in the configuration example, Users can convert the uplink data of the lorawan sensor to modbus RTU/TCP data
372
373 MS48-LR eliminates the need to add additional lorawan gateways to implement (% style="color:blue" %)**LoRaWAN to Modbus RTU/TCP**
374
375
376 === **Step 1: Configure the LoRa Radio to your area Frequency Plan** ===
377
378
379 The Frequency Plan has to be set the same as the Sensor node Frequency Plan.
380
381 [[image:image-20231108164616-1.png||_mstalt="430573" height="353" width="765"]]
382
383
384 === **Step 2: Copy the unique Gateway EUI & Configure the LoRaWAN Server address** ===
385
386
387 Users need to connect the MS48-LR configuration to the built-in lorawan server.
388
389 Every MS48-LR has a unique gateway EUI. The ID can be found on the LoRaWAN Semtech page:
390
391 [[image:image-20231110160659-1.png||_mstalt="429858" height="804" width="1004"]]
392
393
394 === **Step 3: Enable the Built-in LoRaWAN Network Server** ===
395
396
397 [[image:image-20231110163133-2.png||_mstalt="426881" height="522" width="1015"]]
398
399
400 === **Step 4: Logging to the Built-in LoRaWAN Network Server** ===
401
402
403 [[image:image-20231110170323-4.png||_mstalt="427297" height="526" width="1006"]]
404
405
406 === **Step 5: Register the gateway to the built-in ChirpStack** ===
407
408
409 Copy Gateway EUI from the previous step to the following interface:
410
411 [[image:image-20231110170802-5.png||_mstalt="428233" height="675" width="1011"]]
412
413
414 === **Step 6: Register the Sensor-node to the built-in ChirpStack** ===
415
416
417 The MS48-LR gateway is already set up to connect to the built-in ChirpStack network, so we now need to configure the sensor device to connect to the built-in ChirpStack.
418
419 First we need to add the Device Profiles and Application (ignore them if they are already done).
420
421
422 ==== **1) Add Device Profiles** ====
423
424 [[image:image-20231110172143-6.png||_mstalt="428649" height="641" width="1017"]]
425
426
427 ==== **2) Add End Node Device** ====
428
429
430 **Create an Application**
431
432 [[image:image-20231110172604-8.png||_mstalt="429975"]]
433
434
435 Add a device for the sensor node
436
437 [[image:image-20231109092517-2.png||_mstalt="431210" height="516" width="1000"]]
438
439
440 Enter Device EUI, Join EUI(APP EUI)and APPKEY of the node Device, and select the Device profile added in the previous step
441
442 [[image:image-20231110173714-9.png||_mstalt="431275" height="519" width="1002"]]
443
444
445 [[image:image-20231110175007-11.png||_mstalt="450762" height="660" width="1004"]]
446
447
448 === **Step 7: Configure Modbus RTU/TCP Slave** ===
449
450
451 The gateway can as a Modbus RTU slave to run, the user can set a range of the register to write a sensor node uplink data.
452
453
454 For example, there is a sensor node EUI is 70b3d57ed0051e22, the register start is 0xABCD and the register length is 14, which means the uplink data will be written to the register starting at 0xABCD register and the maximum write length not to exceed 14 registers.
455
456 So the sensor node 70b3d57ed0051e22 uplink data will be written to the 0xABCD - 0xABE1 register.
457
458 (% style="color:red" %)**Note: Since the length of the payload is the same for different sensor nodes if The length of the data is greater than the configuration length, the data will be replaced with FFFF.**
459
460 **Slave Setting:**
461
462 Slave Mode  ~-~--> Support both RTU and TCP mode
463
464 Enable Modbus Slave  ~-~--> Enable Slave
465
466 Slave Address/Port  ~-~--> Set the slave address/port
467
468 Show Sensor History  ~-~--> See the sensor data log
469
470
471 **Sensor Settings:**
472
473 Device EUI  ~-~--> Sensor node's EUI
474
475 Register Start  ~-~-->  Setting the start register address to write the sensor node's data
476
477 Register Length  ~-~-->  The maximum write length with register
478
479 (% style="color:red" %)**Note: Only 1 sensor can be written in the range set by the registers**
480
481 About how long the register needs to be configured:
482 In most cases, the payload length of Dragino's sensor is 11 bytes, which corresponds to a register length of 6.
483 The modbus data forwarded by the gateway will have the Dev Address, Fcnt, Rssi, Payload, and Date of the sensor.
484 **Dev Address** occupies 2, **Fcnt** occupies 1, **Rssi** occupies 1, **Date** occupies 2, so by default you need to configure the register length to be greater than or for 12.
485
486 User can check the payload length on the Event page:
487
488 [[image:image-20250207115927-2.png]]
489
490
491
492 ==== **1) RTU Mode**: ====
493
494 (% class="wikigeneratedid" id="H" %)
495 [[image:image-20240112143033-1.png||_mstalt="426140" height="755" width="1318"]]
496
497
498 After the sensor node is active at the built-in server Chirpstack, the user can add it to this page and enable the Modbus RS485-RTU Slave.
499
500 Then MS48-LR will write the uplink data to the 03 code register and record the uplink data.
501
502
503 **PLC read the MS48-LR register**
504
505 **Settings: **
506
507 **Function  : 03 code**
508
509 **Bit rate  :  9600**
510
511 **Parity bit : none**
512
513 **Stop bit  : 1**
514
515 **Response Timeout :  Greater than 3000ms**
516
517
518 ==== (% style="color:inherit; font-family:inherit; font-size:20px" %)**2) TCP Mode:**(%%) ====
519
520 (% class="wikigeneratedid" id="H-1" %)
521 [[image:image-20240112143439-2.png||_mstalt="429780" height="604" width="1065"]]
522
523
524 **PLC read the MS48-LR register**
525
526 **Settings: **
527
528 **Function  :  03 code**
529
530 **IP Address  :  Gateway IP Address**
531
532 **Server Port :  Slave Port**
533
534 **Connect Timeout :  Greater than 3000ms**
535
536
537 ==== **3) PLC(Modbus server/master) data show:** ====
538
539 [[image:image-20231111105300-3.png||_mstalt="425022"]]
540
541
542 **History Data:**
543
544 **Click the Show Sensor History will launch to this page**
545
546 [[image:image-20231111105548-4.png||_mstalt="430014" height="763" width="1054"]]
547
548
549 === **Step 8: Configure Sensor decode to Built-in Chirpstack** ===
550
551
552 ==== **1) Add Sensor's decode to Chirpstack** ====
553
554 Users can find the ChirpStack v4 decoder code for the Dragino End node in this link：
555
556 [[https:~~/~~/github.com/dragino/dragino-end-node-decoder>>url:https://github.com/dragino/dragino-end-node-decoder]]
557
558 **If the user's sensor is from another manufacturer, you need to search for the chirpstack decoder of the corresponding sensor on the official website of the corresponding manufacturer.**
559
560
561 The following example is to add the LHT65N decoder：
562
563 [[image:image-20240319145115-3.png||_mstalt="430092" height="815" width="1004"]]
564
565 [[image:image-20240319145749-4.png||_mstalt="434655" height="758" width="1005"]]
566
567
568 ==== **2) Check the decode on ChiprStack** ====
569
570 [[image:image-20240319145903-5.png||_mstalt="432315" height="705" width="1020"]]
571
572
573 === **Step 9: Configure Modbus RTU/TCP Slave Sensor Decode** ===
574
575
576 (% class="MsoNormal" %)
577 (% lang="EN-US" style="background-attachment:initial; background-clip:initial; background-image:initial; background-origin:initial; background-position:initial; background-repeat:initial; background-size:initial" %)For example, there is a sensor node EUI is(%%) a840411be186e411, the register start is 0x0000 and the register length is 14, which means the uplink data will be written to the register starting at 0x0000 register and the maximum write length not to exceed 14 registers.
578
579 (% class="MsoNormal" %)
580 (% lang="EN-US" style="background-attachment:initial; background-clip:initial; background-image:initial; background-origin:initial; background-position:initial; background-repeat:initial; background-size:initial" %)Add Decode Data TempC_SHT, the register start address is 0x000F and the register length is 2,(%%) which means the Decode Data TempC_(% lang="EN-US" style="background-attachment:initial; background-clip:initial; background-image:initial; background-origin:initial; background-position:initial; background-repeat:initial; background-size:initial" %)SHT(%%) will be written to the register starting at 0x000F register and the maximum write length not to exceed 2 registers.
581
582 (((
583
584 )))
585
586 (% class="MsoNormal" %)
587 (% lang="EN-US" style="background-attachment:initial; background-clip:initial; background-image:initial; background-origin:initial; background-position:initial; background-repeat:initial; background-size:initial" %)So the sensor node a840411be186e411 uplink data will be written to the 0x0000 - 0x000E register, and the Decode Data TempC_SHT will be written to the 0x000F - 0x0010 register.
588
589 (% class="MsoNormal" %)
590 (% style="color:red" %)**Note: Since the length of the payload is the same for different sensor nodes if The length of the data is greater than the configuration length, the data will be replaced with FFFF.**
591
592 (((
593
594 )))
595
596 (% style="margin: 0cm 0cm 7.5pt; background-image: initial; background-position: initial; background-size: initial; background-repeat: initial; background-attachment: initial; background-origin: initial; background-clip: initial;" %)
597 (% lang="EN-US" style="font-size:10.5pt" %)**Decode Data:**
598
599 (% style="margin: 0cm 0cm 7.5pt; background-image: initial; background-position: initial; background-size: initial; background-repeat: initial; background-attachment: initial; background-origin: initial; background-clip: initial;" %)
600 (% lang="EN-US" style="font-size:10.5pt" %)Device (%%)Type(% lang="EN-US" style="font-size:10.5pt" %)  ~-~-->  Sensor decoder data
601
602 (% style="margin: 0cm 0cm 7.5pt; background-image: initial; background-position: initial; background-size: initial; background-repeat: initial; background-attachment: initial; background-origin: initial; background-clip: initial;" %)
603 (% lang="EN-US" style="font-size:10.5pt" %)Register Start  ~-~-->  Setting the start register address to write the sensor node's decoder data
604
605 (% style="margin: 0cm 0cm 7.5pt; background-image: initial; background-position: initial; background-size: initial; background-repeat: initial; background-attachment: initial; background-origin: initial; background-clip: initial;" %)
606 (% lang="EN-US" style="font-size:10.5pt" %)Register Length  ~-~-->  The maximum write length with register
607
608 (((
609
610 )))
611
612 (% style="margin: 0cm 0cm 7.5pt; background-image: initial; background-position: initial; background-size: initial; background-repeat: initial; background-attachment: initial; background-origin: initial; background-clip: initial;" %)
613 (% lang="EN-US" style="color:red; font-size:10.5pt" %)**Note: Only 1 Data can be written in the range set by the registers**
614
615 (% style="margin: 0cm 0cm 7.5pt; background-image: initial; background-position: initial; background-size: initial; background-repeat: initial; background-attachment: initial; background-origin: initial; background-clip: initial;" %)
616 [[image:1710569938804-766.png||_mstalt="298597" height="656" width="917"]]
617
618 (((
619
620 )))
621
622 (% style="margin: 0cm 0cm 7.5pt; background-image: initial; background-position: initial; background-size: initial; background-repeat: initial; background-attachment: initial; background-origin: initial; background-clip: initial;" %)
623 ==== **PLC(Modbus server/master) data show:** ====
624
625
626 (% style="color:red" %)**Note: When the decoded data is a floating point number or a negative number, it will be encoded using IEEE754**
627
628 For example:  23.20(real data) ~-~--> 4037333333333333 [HEX](register show).
629
630 For example:  -23.20(real data) ~-~-->C037333333333333 [HEX] (register show).
631
632 For example:  23(real data)~-~->4037000000000000 [HEX](register show).
633
634 [[image:1710570017983-979.png||_mstalt="298571" height="694" width="531"]]
635
636
637 == 2.4 Accept data to registers for specified Fport ==
638
639
640 For example, there is a sensor node EUI is f4bbf5a0da6f4da5,
641
642 * the sensor payload uplink is using Fport=2
643 * the sensor status uplink is  using Fport=5
644
645 **//If the accept fport is not set, it may cause the registers to be written with 0 decoded data during status uplink, because status uplinks typically do not contain decoded data.//**
646
647
648 To avoid 0 data being written to the registers. the users can set accept Fport for the sensor,
649
650 i.e., the data will be written to the register only when the MS48-LR receives the uplink of the specified Fort
651
652
653 (% style="margin: 0cm 0cm 7.5pt; background-image: initial; background-position: initial; background-size: initial; background-repeat: initial; background-attachment: initial; background-origin: initial; background-clip: initial;" %)
654 **Accept Fport(% lang="EN-US" style="font-size:10.5pt" %):(%%)**
655
656 (% style="margin: 0cm 0cm 7.5pt; background-image: initial; background-position: initial; background-size: initial; background-repeat: initial; background-attachment: initial; background-origin: initial; background-clip: initial;" %)
657 (% lang="EN-US" style="font-size:10.5pt" %)DevEUI  ~-~-->  Sensor node DevEUI
658
659 (% style="margin: 0cm 0cm 7.5pt; background-image: initial; background-position: initial; background-size: initial; background-repeat: initial; background-attachment: initial; background-origin: initial; background-clip: initial;" %)
660 Accept FPort(% lang="EN-US" style="font-size:10.5pt" %)  ~-~-->  Setting the (%%)Accept Fport
661
662
663 [[image:image-20240606153055-1.png||_mstalt="429715"]]
664
665
666 === **PLC(Modbus server/master) data show:** ===
667
668 [[image:image-20240606155134-2.png||_mstalt="430001"]]
669
670
671 [[image:image-20240606155545-3.png||_mstalt="432276"]]
672
673
674 == 2.5 Modbus Downlink ==
675
676
677 The user can use Modbus downlink to send a payload to the sensor device
678
679 **Prerequisites:**
680
681 The preceding configurations are complete and the sensor data is forwarded properly
682
683
684 === **Step 1. Generate chirpstack API token** ===
685
686
687 Users can generate API tokens on the **API Keys** interface with built-in chirpstack
688
689 Copy and save the API token after it is generated.
690
691 [[image:image-20241230113013-6.png||height="345" width="1347"]]
692
693
694 === **Step 2. Configuring API tokens and reloading the modbus service** ===
695
696
697 Configure the API token from step 1 on the Downlink token and click "**Reload**"
698
699 [[image:image-20241230110939-2.jpeg]]
700
701
702 === **Step 3. Configure downlink registers for the device** ===
703
704
705 For example, there is a sensor node EUI is a84041a77259044c, the register start is 0x10 and the register length is 3, which means the downlink data will be written to the register starting at 0x10 register and the maximum write length not to exceed 3 registers.
706
707 So the sensor node a84041a77259044c downlink data will be written to the 0x10 - 0x13 register.
708
709
710 **Downlink Settings:**
711
712 Device EUI  ~-~--> Sensor node's EUI
713
714 Register Address(Start)  ~-~-->  Setting the start register address to write the downlink data
715
716 Register Length  ~-~-->  The maximum write length with register
717
718 (% style="color:red" %)**Note: Only 1 sensor can be written in the range set by the registers**
719
720 [[image:image-20241230113057-8.jpeg||height="431" width="1197"]]
721
722
723 === **Step 4. Sent downlink to the MS48** ===
724
725
726 For example, there is a sensor node EUI is a84041a77259044c, downlink is 2601
727
728 (% style="color:red" %)**Note: that you need to use 16 function codes to write downlink data for the registers**
729
730 It is required that the downlink registers do not hold data in existence, otherwise a large number of downlink will be generated
731
732 [[image:image-20241230112132-4.jpeg||height="720" width="1089"]]
733
734
735 By default, each register occupies 16 bits (2 bytes). Therefore, when the client sends data such as 030101, it is necessary to directly add FFFFF in the single register, for example: 0x0301, 0xFFFF, 0xFF01,
736
737 the gateway will automatically convert it to 030101 downlink
738
739 [[image:image-20250228092430-1.png||height="658" width="937"]]
740
741
742
743 === **Step 5. Check chirpstack Queue** ===
744
745
746 After the downlink is sent, the user can check whether the downlink queue is generated on the **Queue** page of the sensor device on the built-in chirpstack
747
748 [[image:image-20241230113037-7.jpeg||height="662" width="1226"]]
749
750
751 The above single-byte register downlink queue results
752
753 [[image:image-20250228092545-2.png||height="724" width="1227"]]
754
755 = 3. Web Configure Pages =
756
757 == 3.1 Home ==
758
759
760 Shows the system running status:
761
762
763 == 3.2 LoRa Settings ==
764
765 === 3.2.1 LoRa ~-~-> LoRa ===
766
767
768 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.
769
770 Different MS48-LR hardware versions can support different frequency ranges:
771
772 * **868**: valid frequency: 863Mhz ~~ 870Mhz. for bands EU868, RU864, IN865, or KZ865.
773 * **915**: valid frequency: 902Mhz ~~ 928Mhz. for bands US915, AU915, AS923 or KR920
774
775 After the user choose the frequency plan,  the user can see the actual frequency is used by checking the page **LogRead ~-~-> LoRa Log**
776
777 [[image:image-20231109145418-1.png||_mstalt="430612" height="372" width="761"]]
778
779
780 (% style="color:red" %)//**Note *: See this instruction for how to customize the frequency band:**//(%%)//** __[[How to customized LoRaWAN frequency band - DRAGINO>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20customized%20LoRaWAN%20frequency%20band/]]__**//
781
782
783 == 3.3 LoRaWAN Settings ==
784
785 === 3.3.1 LoRaWAN ~-~-> LoRaWAN Semtech UDP ===
786
787
788 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.
789
790 [[image:image-20231109145535-2.png||_mstalt="430924" height="577" width="666"]]
791
792
793 === 3.3.2 LoRaWAN ~-~-> LoRaWAN Basic Station ===
794
795
796 This page is for the connection set up to the TTN Basic Station, AWS-IoT, etc.
797
798 [[image:image-20231109145619-3.png||_mstalt="432302" height="438" width="668"]]
799
800 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>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Use%20of%20LoRaWAN%20Basic%20Station/]]__
801
802
803 == 3.4 Network Settings ==
804
805 === 3.4.1 Network ~-~-> WiFi ===
806
807
808 Users can configure the wifi WAN and enable Wifi Access Point on this interface
809
810 [[image:image-20231109145715-4.png||_mstalt="431626" height="282" width="774"]]
811
812
813 === 3.4.2 Network ~-~-> System Status ===
814
815
816 [[image:image-20231109145758-5.png||_mstalt="434304" height="535" width="772"]]
817
818
819 === 3.4.3 Network ~-~-> Network ===
820
821
822 In the **Network ~-~-> Network** interface, Users can set the Ethernet WAN static ip address.
823
824 [[image:image-20231109145841-6.png||_mstalt="432289" height="248" width="783"]]
825
826
827 === 3.4.4 Network ~-~-> Cellular ===
828
829
830 In the (% _mstmutation="1" %)**Network ~-~-> Cellular**(%%) interface, Users can Enable Cellular WAN and configure Celluar.(% style="display:none" %)
831
832 (% style="color:red" %)**Note: APN cannot be empty.**
833
834 [[image:image-20231109145928-7.png||_mstalt="434681" height="361" width="804"]]
835
836
837 After the configuration is complete, return to the Home interface and put the mouse on the Cell icon to check the Cellular state.
838
839 When cellular fails to connect or has problems, users can refer to this link to Trouble Shooting:**[[How to Trouble Shooting if Cellular connection fails>>https://wiki.dragino.com/xwiki/bin/view/Main/Notes%20for%20cellular%20network%20connection/#H2.2ForLPS8v22FMS48-LR]]**
840
841
842 == 3.5 System ==
843
844 === 3.5.1 System ~-~-> System Overview ===
845
846
847 Shows the system info:
848
849 [[image:image-20240108114851-5.png||_mstalt="430820" height="575" width="839"]]
850
851
852 === 3.5.2 System ~-~-> System General ===
853
854
855 There are two login for MS48-LR: (% style="color:blue" %)**root /dragino**(%%) or (% style="color:blue" %)**admin /dragino**(%%). Both root and admin has the same right for WEB access. But root user has also the right to access via SSH to Linux system. admin only able to access WEB interface.
856
857 This page can be used to set the password for them.
858
859 (% style="color:#037691" %)**__Timezone:  __**(%%)Set device timezone.
860
861 (% style="color:#037691" %)**__Time Synchronization Service: __**(%%) Set the time synchronization server.
862
863 (% style="color:#037691" %)**__HTTP Web Service:  __**(%%)Enable/Disable the HTTP service via WAN interface.
864
865 (% style="color:#037691" %)**__Terminal Service:  __**(%%)Enable/Disable the  SSH service via WAN interface.
866
867 (% style="color:#037691" %)**__Fallback Settings:  __**(%%)Enable/Disable the Fallback interface.
868
869 (% style="color:#037691" %)**__Keepalive_Script:  __**(%%)Set the keepalive_scrpt interval.
870
871
872 [[image:image-20240719152237-3.png||_mstalt="432055" height="701" width="833"]]
873
874
875 === 3.5.3 System ~-~-> Backup/Restore ===
876
877
878 [[image:image-20231109150130-9.png||_mstalt="429325" height="217" width="830"]]
879
880
881 === 3.5.4 System ~-~-> Remoteit ===
882
883
884 In the **System-> Remoteit** interface, users can configure the gateway to be accessed remotely via Remote.it.
885
886 the users can refer to this link to configure them: **[[Monitor & Remote Access Gateway>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Monitor%20%26%20Remote%20Access%20Gateway/?Remote%20Access#H2.1A0RemoteAccessviaRemote.it.]]**
887
888 [[image:image-20231109150415-10.png||_mstalt="451308" height="424" width="835"]]
889
890
891 === 3.5.5 System ~-~-> Package Management ===
892
893
894 In the **System ~-~-> Package Management** interface, Users can check the current version of Core Packages.
895
896 [[image:image-20231109150446-11.png||_mstalt="452998" height="566" width="840"]]
897
898
899 = 4. Build-in Server =
900
901
902 the default factory version of MS48-LR is installed with the built-in Applicant server: **Node-Red**, LoRaWAN Server: **ChirpStack**.
903
904 (% style="color:red" %)**Note:**
905
906 (% _mstmutation="1" %)**Path**(%%): Server ~-~-> Network Server
907
908 Server ~-~-> Application Server
909
910 (% style="color:blue" %)**Troubleshooting:**
911
912 **~ 1. URL does not jump properly**
913
914 For the ChirpStack, you can use the local IP address and the port is **8080** to access it.
915
916 For the Node-Red, you can use the local IP address and the port is **1880** to access it.
917
918
919 == 4.1 LoRaWAN Network Server ~-~- ChirpStack ==
920
921
922 You can access the gateway's built-in LNS server of **ChirpStack **via the URL( __**//http:~/~/<hostname>:8080 or http:~/~/<local-IPV4-address> //**__) in your browser.
923
924 Such as  __**//http:~/~/dragino-54ff12:8080  or http:~/~/<Local-IPV4-Address>//**__
925
926 (% style="color:blue" %)**Login account:**
927
928 **Username : ** **admin**
929
930 **Password: ** ** admin**
931
932 [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20All%20Gateway%20models/HP0C/WebHome/image-20230616175332-6.png?width=1029&height=519&rev=1.1||alt="image-20230616175332-6.png" _mstalt="432016"]]
933
934
935 == 4.2 Application Server ~-~- Node-Red ==
936
937
938 You can access the gateway's built-in AS server of **Node-Red **via the URL(__**//http:~/~/<hostname>:1880 or http:~/~/<local-IPV4-address>//**__) in your browser.
939
940 Such as __**//http:~/~/dragino-54ff12:1880  or [[http:~~/~~/<Local-IPV4-Address~>>>http://<Local-IPV4-Address>]]//**__
941
942 [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20All%20Gateway%20models/HP0C/WebHome/image-20220725172124-3.png?width=843&height=610&rev=1.1||alt="image-20220725172124-3.png" _mstalt="429767"]]
943
944
945 === **Using Node-Red, InfluxDB and Grafana** ===
946
947 The MS48-LR supports this combination, the default, Node-red is pre-installed but the InfluxDB and Grafana is not pre-installed.
948
949 the users can refer to this link to install them.
950
951 [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Armbian%20OS%20instruction/#H2.6HowtoinstallGrafanaandinfluxdb>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Armbian%20OS%20instruction/#H2.6HowtoinstallGrafanaandinfluxdb]]
952
953
954 === **Upgrade the node.js** ===
955
956 By default, the MS48-LR node.js uses the pre-install version v12 which is due to Debian the ultra-stable via ultra-old.
957
958 the users can refer to this link to upgrade them.
959
960 [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Armbian%20OS%20instruction/#H2.5Howtoupgradethenodejsversiontothelatest.>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Armbian%20OS%20instruction/#H2.5Howtoupgradethenodejsversiontothelatest.]]
961
962
963 = 5. Use RS232 Interface =
964
965
966 MS48-LR includes a local ChirpStack Server and Node-Red. This example shows how to configure LHT65N to use with the local Node-Red server. This example assumes users already have:
967
968 * LHT65N register on MS48-LR Built-In ChirpStack server already
969 * The user is able to see the data on the built-in ChirpStack server device page
970 * The RS232 relay is connected to the RS232 interface of the MS48-LR
971
972 The MS48-LR RS232 interface corresponds to (% style="color:blue" %)**/dev/ttyS2.**
973
974 Below are the steps for the MS48-LR read LHT65N's temperature control RS232 relay example:
975
976 [[image:image-20240115155839-1.png||_mstalt="432328" height="304" width="1036"]]
977
978 [[image:1705307593665-981.png||_mstalt="297804" height="526" width="691"]]
979
980
981 == 5.1 Link Node-Red to Local ChirpStack ==
982
983
984 Users can download the Node-Red decoder from this link and import it into the Node-Red platform: **[[MS48-LR read LHT65N's temperature control RS232 relay.json>>attach:MS48-LR read LHT65N's temperature control RS232 relay.json||target="_blank"]]**
985
986 For more information on importing Input Flow, check out this link: **[[Import Input Flow for Dragino Sensors>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/#H3.A0ImportInputFlowforDraginoSensors]]**
987
988 After importing the Input Flow is complete, the user needs to edit the MQTT in the node
989
990 The specific steps can be found at this link: **[[Example: Use Local Server ChirpStack and Node-Red>>http://wiki.dragino.com/xwiki/bin/view/Main/Notes%20for%20ChirpStack/#H12.A0Example:UseLocalServerChirpStackandNode-RedinLPS8v2]]**
991
992 [[image:image-20240115161940-2.png||_mstalt="429377" height="593" width="1149"]]
993
994
995 = 6. Use RS485 Interface =
996
997
998 The MS48-LR RS485 interface corresponds to (% style="color:blue" %)**/dev/ttyS1.**
999
1000 Below are the steps for the MS48-LR RS485 interface to manually send and receive data:
1001
1002 [[image:image-20240702105904-12.png||_mstalt="452595"]]
1003
1004 == 6.1 Initialize the GPIO21 ==
1005
1006
1007 Users need to run the following command to configure GPIO21：
1008
1009 (% class="box infomessage" %)
1010 (((
1011 **echo 21 > /sys/class/gpio/export
1012 echo "out" > /sys/class/gpio/gpio21/direction**
1013 )))
1014
1015
1016 == 6.2 Set the RS485 Tx Mode ==
1017
1018
1019 Set the MS48-LR RS485 port to Tx mode by lowering the GPIO21 level：
1020
1021 (% class="box infomessage" %)
1022 (((
1023 **echo "0" > /sys/class/gpio/gpio21/value**
1024 )))
1025
1026 Run the following command to send hexadecimal data:
1027
1028 (% class="box infomessage" %)
1029 (((
1030 **echo -en "\x01\x02\x03\x04\x05" > /dev/ttyS1**
1031 )))
1032
1033 [[image:image-20240702100108-8.jpeg||_mstalt="470652"]]
1034
1035
1036 Users can use the serial port tool to check the data sent by MS48-LR RS485:
1037
1038 [[image:image-20240702100337-9.png||_mstalt="430456" height="595" width="617"]]
1039
1040
1041 == 6.3 Set the RS485 Rx Mode ==
1042
1043
1044 Set the MS48-LR RS485 port to Rx mode by pulling up the GPIO21 level：
1045
1046 (% class="box infomessage" %)
1047 (((
1048 **echo "1" > /sys/class/gpio/gpio21/value**
1049 )))
1050
1051 Run the following command to check the data received by the MS48-LR RS485:
1052
1053 (% class="box infomessage" %)
1054 (((
1055 **cat /dev/ttyS1 | xxd -p -u**
1056 )))
1057
1058 [[image:image-20240702110051-13.png||_mstalt="449566"]]
1059
1060
1061 = 7. Power Analyze =
1062
1063
1064 Users can refer to and calculate the power consumption of the MS48-LR in this：
1065
1066 (% border="1" cellspacing="3" style="background-color:#f2f2f2; width:515px" %)
1067 |=(% style="width: 80px; background-color: rgb(79, 129, 189); color: white;" %)**Model**|=(% style="width: 80px; background-color: rgb(79, 129, 189); color: white;" %)**Input Power**|=(% style="width: 175px; background-color: rgb(79, 129, 189); color: white;" %)**Test Mode**|=(% style="width: 80px; background-color: rgb(79, 129, 189); color: white;" %)**Current(mA)**|=(% style="width: 100px; background-color: rgb(79, 129, 189); color: white;" %)**Power Consumption(W)**
1068 |(% colspan="1" rowspan="10" style="width:83px" %)**MS48-LR**|(% colspan="1" rowspan="10" style="width:105px" %)**(+12V)**
1069 |(% style="width:533px" %)Starting current|(% style="width:118px" %)90-190|(% style="width:195px" %)1.080-2.280
1070 |(% style="width:533px" %)No network|(% style="width:118px" %)179-210|(% style="width:195px" %)2.148-2.520
1071 |(% style="width:533px" %)wifi and internet connection(LORA Start)|(% style="width:118px" %)137-178|(% style="width:195px" %)1.644-2.136
1072 |(% style="width:533px" %)wifi and internet connection(LORA Start) and 4G|(% style="width:118px" %)144-201|(% style="width:195px" %)1.728-2.412
1073 |(% style="width:533px" %)wifi and internet connection(LORA Start) and 4G and 64g U disk|(% style="width:118px" %)172-225|(% style="width:195px" %)2.100-2.700
1074 |(% style="width:533px" %)4G connection(LORA Start)|(% style="width:118px" %)161-226|(% style="width:195px" %)1.932-2.712
1075 |(% style="width:533px" %)wifi and internet connection(LORA Start) and 64g U disk|(% style="width:118px" %)162-193|(% style="width:195px" %)1.956-2.316
1076 |(% style="width:533px" %)send manually|(% style="width:118px" %)377|(% style="width:195px" %)4.524
1077 |(% style="width:533px" %)accept manually|(% style="width:118px" %)175|(% style="width:195px" %)2.100
1078 )))
1079
1080
1081 = 8. More Services =
1082
1083 == 8.1 NTP Service/Time Synchronization ==
1084
1085
1086 The gateway time sync service is provided by chrony service.
1087
1088 === 1). Modify the NTP server address: ===
1089
1090 (% class="box infomessage" %)
1091 (((
1092 **Configuration file path:  /etc/chrony/chrony.conf **
1093 )))
1094
1095 === 2). Start/Stop/Enable/Disable NTP service: ===
1096
1097 (% class="box infomessage" %)
1098 (((
1099 **systemctl start chrony
1100 \\systemctl stop chrony
1101 \\systemctl disable chrony
1102 \\systemctl enable chrony**
1103 )))
1104
1105
1106 == 8.2 Back up the built-in server data and Restore backup ==
1107
1108
1109 The ms48-lr gateway has a built-in chirpstack server data backup function. Users can click "Generate_archive" on the **System~-~->Back up/Restore Config** page to generate a backup, and then download
1110
1111 [[image:1752134508337-300.png]]
1112 Users can upload backup files on other MS48-LRs and upload server data to this gateway
1113
1114 [[image:1752134554753-411.png||height="277" width="1158"]]
1115
1116 In this way, users can migrate the data of the backup server to other MS48-LR gateways.
1117
1118
1119 = 9. Trouble Shooting =
1120
1121 == 9.1 Click "Manual_Update", why there is no response? ==
1122
1123
1124 When you click "Manual_Update", the gateway will finish updating within 10 minutes and display the update log.
1125
1126 [[image:image-20250208141034-1.png]]
1127
1128
1129 == 9.2 How to reset the built-in server ==
1130
1131
1132 Users need to click "Reset" on the Server~-~->Network Server interface, ChirpStack will be reset.
1133
1134 [[image:image-20250208141159-2.png||height="441" width="1072"]]
1135
1136
1137 == 9.3 How does modbus tcp downlink single-byte register contents to sensor devices ==
1138
1139
1140 (% id="cke_bm_110537S" style="display:none" %) (%%)By default, each register occupies 16 bits (2 bytes). Therefore, when the client sends data such as **030101**, it is necessary to directly add **FFFFF** in the single register, for example:** 0x0301, 0xFFFF, 0xFF01,**
1141
1142 the gateway will automatically convert it to **030101** downlink
1143
1144 [[image:image-20250228092430-1.png||height="614" width="874"]]
1145
1146 [[image:image-20250228092545-2.png||height="724" width="1227"]]
1147
1148 == 9.4  How to check the Storage of the gateway ==
1149
1150
1151 Run the following command on the command line interface of the gateway to check the disk space usage:
1152
1153 (% class="box infomessage" %)
1154 (((
1155 df -sh
1156 )))
1157
1158 [[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20All%20Gateway%20models/HP0C/WebHome/image-20250207145702-2.png?rev=1.1||alt="image-20250207145702-2.png"]]
1159
1160 On the Linux console of the gateway, enter the following command to check the total disk space occupied by the files running on the gateway:
1161
1162 (% class="box infomessage" %)
1163 (((
1164 **du -sh /usr/local/ /usr/* /var/***
1165 )))
1166
1167 [[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20All%20Gateway%20models/HP0C/WebHome/image-20250207145617-1.png?rev=1.1||alt="image-20250207145617-1.png"]]
1168
1169 == 9.4  How to clear the local server cache of the gateway using the command ==
1170
1171
1172 = 10. Supports =
1173
1174
1175 If you are experiencing issues and can't solve them, you can send mail to [[support@dragino.com>>mailto:support@dragino.com]].
1176
1177 With your question as detailed as possible. We will reply and help you in the shortest.
1178
1179
1180 = (% data-sider-select-id="a056b4ad-7d05-42b4-ad74-7a3134f8010a" %)11. Order Info(%%) =
1181
1182
1183 (% style="color:#0000ff" %)**MS48-LR-XXX-YYY**
1184
1185 (% style="color:#0000ff" %)**XXX**(% style="color:black" %): Frequency Band
1186
1187 * (% style="color:red" %)**AS923**(%%): LoRaWAN AS923 band
1188
1189 * (% style="color:red" %)**AU915**(%%): LoRaWAN AU915 band
1190
1191 * (% style="color:red" %)**EU868**(%%): LoRaWAN EU868 band
1192
1193 * (% style="color:red" %)**KR920**(%%): LoRaWAN KR920 band
1194
1195 * (% style="color:red" %)**US915**(%%): LoRaWAN US915 band
1196
1197 * (% style="color:red" %)**IN865**(%%):  LoRaWAN IN865 band
1198
1199 (% style="color:#0000ff" %)**YYY**(% style="color:black" %): 4G Cellular Option
1200
1201 * (% style="color:red" %)**EC25-E**(% style="color:black" %):  EMEA, Korea, Thailand, India
1202
1203 * (% style="color:red" %)**EC25-AFX**(% style="color:black" %): America:Verizon, AT&T(FirstNet), U.S.Cellular; Canada:Telus
1204
1205 * (% style="color:red" %)**EC25-AUX**(% style="color:black" %): Latin America, New Zeland, Taiwan
1206
1207 * (% style="color:red" %)**EC25-J**(% style="color:black" %):  Japan, DOCOMO, SoftBank, KDDI
1208
1209 More info about valid bands, please see [[EC25-E product page>>url:https://www.quectel.com/product/ec25.htm]].
1210
1211
1212 = 12. Manufacturer Info =
1213
1214
1215 **Shenzhen Dragino Technology Development co. LTD**
1216
1217 Room 202, Block B, BCT Incubation Bases (BaoChengTai),  No.8 CaiYunRoad
1218
1219 LongCheng Street, LongGang District ; Shenzhen 518116,China
1220
1221
1222 = 13. FCC Warning =
1223
1224
1225 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:
1226
1227 ~-~- Reorient or relocate the receiving antenna.
1228
1229 ~-~- Increase the separation between the equipment and receiver.
1230
1231 ~-~- Connect the equipment into an outlet on a circuit different from that to which the receiver is connected.
1232
1233 ~-~- Consult the dealer or an experienced radio/TV technician for help.
1234
1235 Changes or modifications not expressly approved by the party responsible for compliance could void the user's authority to operate the equipment.
1236
1237 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.
1238
1239
1240