RS485-LN – RS485 to LoRaWAN Converter User Manual

(% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||height="15" role="presentation" title="Click and drag to move" width="15"]]

20

)))

21

= 1. Introduction =

== 1.1 What is RS485-LN RS485 to LoRaWAN Converter ==

(((

The Dragino RS485-LN is a (% style="color:blue" %)**RS485 to LoRaWAN Converter**(%%). It converts the RS485 signal into LoRaWAN wireless signal which simplify the IoT installation and reduce the installation/maintaining cost.

)))

(((

RS485-LN allows user to (% style="color:blue" %)**monitor / control RS485 devices**(%%) and reach extremely long ranges. It provides ultra-long range spread spectrum communication and high interference immunity whilst minimizing current consumption. It targets professional wireless sensor network applications such as irrigation systems, smart metering, smart cities, building automation, and so on.

)))

(((

(% style="color:blue" %)**For data uplink**(%%), RS485-LN sends user-defined commands to RS485 devices and gets the return from the RS485 devices. RS485-LN will process these returns according to user-define rules to get the final payload and upload to LoRaWAN server.

)))

(((

(% style="color:blue" %)**For data downlink**(%%), RS485-LN runs in LoRaWAN Class C. When there downlink commands from LoRaWAN server, RS485-LN will forward the commands from LoRaWAN server to RS485 devices.

)))

(((

(% style="color:blue" %)**Demo Dashboard for RS485-LN**(%%) connect to two energy meters: [[https:~~/~~/app.datacake.de/dashboard/d/58844a26-378d-4c5a-aaf5-b5b5b153447a>>url:https://app.datacake.de/dashboard/d/58844a26-378d-4c5a-aaf5-b5b5b153447a]](% title="Click and drag to resize" %)

)))

== 1.2 Specifications ==

55

56

57

(% style="color:#037691" %)**Hardware System:**

58

59

* STM32L072xxxx MCU

60

* SX1276/78 Wireless Chip

61

* Power Consumption (exclude RS485 device):

62

** Idle: 32mA@12v

63

** 20dB Transmit: 65mA@12v

64

65

(% style="color:#037691" %)**Interface for Model:**

66

67

* RS485

68

* Power Input 7~~ 24V DC.

69

70

(% style="color:#037691" %)**LoRa Spec:**

71

72

* Frequency Range:

73

** Band 1 (HF): 862 ~~ 1020 Mhz

74

** Band 2 (LF): 410 ~~ 528 Mhz

75

* 168 dB maximum link budget.

76

* +20 dBm - 100 mW constant RF output vs.

77

* +14 dBm high efficiency PA.

78

* Programmable bit rate up to 300 kbps.

79

* High sensitivity: down to -148 dBm.

80

* Bullet-proof front end: IIP3 = -12.5 dBm.

81

* Excellent blocking immunity.

82

* Low RX current of 10.3 mA, 200 nA register retention.

83

* Fully integrated synthesizer with a resolution of 61 Hz.

84

* FSK, GFSK, MSK, GMSK, LoRaTM and OOK modulation.

85

* Built-in bit synchronizer for clock recovery.

86

* Preamble detection.

87

* 127 dB Dynamic Range RSSI.

88

* Automatic RF Sense and CAD with ultra-fast AFC.

89

* Packet engine up to 256 bytes with CRC

== 1.3 Features ==

* LoRaWAN Class A & Class C protocol (default Class C)

95

* Frequency Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915/IN865/RU864/MA869

96

* AT Commands to change parameters

97

* Remote configure parameters via LoRa Downlink

98

* Firmware upgradable via program port

99

* Support multiply RS485 devices by flexible rules

100

* Support Modbus protocol

101

* Support Interrupt uplink (Since hardware version v1.2)

102

103

== 1.4 Applications ==

104

105

106

* Smart Buildings & Home Automation

107

* Logistics and Supply Chain Management

* Smart Metering

* Smart Agriculture

* Smart Cities

* Smart Factory

== 1.5 Firmware Change log ==

114

115

116

[[RS485-LN Image files – Download link and Change log>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/]]

117

118

119

== 1.6 Hardware Change log ==

(((

(((

(((

v1.2: Add External Interrupt Pin.

)))

(((

v1.0: Release

)))

== 1.7 Pin Definitions ==

135

136

137

The following diagram shows the V1.2 hardware version.

138

139

[[image:image-20240928101253-2.jpeg||height="542" width="542"]]

140

141

[[image:image-20240925161157-2.jpeg||height="367" width="545"]]

)))

)))

= 2. Power ON Device =

(((

The RS485-LN can be powered by 7 ~~ 24V DC power source. Connection as below

152

153

* Power Source VIN to RS485-LN VIN+

154

* Power Source GND to RS485-LN VIN-

155

156

(((

157

Once there is power, the RS485-LN will be on.

158

)))

159

160

(% aria-label="1653268091319-405.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:1653268091319-405.png]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %)

)))

= 3. Operation Mode =

166

167

== 3.1 How it works? ==

(((

(((

The RS485-LN is configured as LoRaWAN OTAA Class C mode by default. It has OTAA keys to join network. To connect a local LoRaWAN network, user just need to input the OTAA keys in the network server and power on the RS485-LN. It will auto join the network via OTAA.

)))

)))

== 3.2 Example to join LoRaWAN network ==

179

180

181

Here shows an example for how to join the TTN V3 Network. Below is the network structure, we use [[LG308>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/140-lg308.html]] as LoRaWAN gateway here.

182

183

[[image:image-20240928102637-3.png||height="522" width="917"]]

184

185

(% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]]

(((

(((

The RS485-LN in this example connected to two RS485 devices for demonstration, user can connect to other RS485 devices via the same method. The connection is as below:

)))

(((

485A+ and 485B- of the sensor are connected to RS485A and RA485B of RS485-LN respectively.

194

)))

195

196

(% aria-label="1653268227651-549.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:1653268227651-549.png||height="592" width="720"]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %)

(((

The LG308 is already set to connect to [[TTN V3 network >>path:https://www.thethingsnetwork.org/]]. So what we need to now is only configure the TTN V3:

)))

(((

(% style="color:blue" %)**Step 1**(%%): Create a device in TTN V3 with the OTAA keys from RS485-LN.

)))

(((

Each RS485-LN is shipped with a sticker with unique device EUI:

)))

)))

(% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]][[image:image-20230425175410-2.png]](% title="Click and drag to resize" %)[[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LDS25-LBLDS25-LS--LoRaWAN_LiDAR_Distance_Auto-Clean_Sensor_User_Manual/WebHome/image-20230426084152-1.png?width=502&height=233&rev=1.1||alt="图片-20230426084152-1.png"]]

215

216

217

You can enter this key in the LoRaWAN Server portal. Below is TTN screen shot:

218

219

**Create the application.**

220

221

[[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/SAC01L_LoRaWAN_Temperature%26Humidity_Sensor_User_Manual/WebHome/image-20250423093843-1.png?width=756&height=264&rev=1.1||alt="image-20250423093843-1.png"]]

222

223

[[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LTC2-LB--LoRaWAN_Temperature_Transmitter_User_Manual/WebHome/image-20240907111305-2.png?width=1000&height=572&rev=1.1||alt="image-20240907111305-2.png"]]

224

225

**Add devices to the created Application.**

226

227

[[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LTC2-LB--LoRaWAN_Temperature_Transmitter_User_Manual/WebHome/image-20240907111659-3.png?width=977&height=185&rev=1.1||alt="image-20240907111659-3.png"]]

228

229

[[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LTC2-LB--LoRaWAN_Temperature_Transmitter_User_Manual/WebHome/image-20240907111820-5.png?width=975&height=377&rev=1.1||alt="image-20240907111820-5.png"]]

230

231

232

**Enter end device specifics manually.**

233

234

[[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LTC2-LB--LoRaWAN_Temperature_Transmitter_User_Manual/WebHome/image-20240907112136-6.png?width=697&height=687&rev=1.1||alt="image-20240907112136-6.png"]]

235

236

**Add DevEUI and AppKey.**

237

238

**Customize a platform ID for the device.**

239

240

[[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LTC2-LB--LoRaWAN_Temperature_Transmitter_User_Manual/WebHome/image-20240907112427-7.png?rev=1.1||alt="image-20240907112427-7.png"]]

241

242

243

(% style="color:blue" %)**Step 2**(%%): Add decoder.

244

245

In TTN, user can add a custom payload so it shows friendly reading.

246

247

Click this link to get the decoder: [[https:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/>>url:https://github.com/dragino/dragino-end-node-decoder/tree/main/]]

248

249

Below is TTN screen shot:

250

251

[[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LDS25-LBLDS25-LS--LoRaWAN_LiDAR_Distance_Auto-Clean_Sensor_User_Manual/WebHome/image-20241009140556-1.png?width=1184&height=488&rev=1.1||alt="image-20241009140556-1.png" height="488" width="1184"]]

252

253

[[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LDS25-LBLDS25-LS--LoRaWAN_LiDAR_Distance_Auto-Clean_Sensor_User_Manual/WebHome/image-20241009140603-2.png?width=1168&height=562&rev=1.1||alt="image-20241009140603-2.png" height="562" width="1168"]]

254

255

256

(% style="color:blue" %)**Step 3**(%%): Activate on RS485-LN.

257

258

Press the button for 5 seconds to activate the RS485-LN. Power on RS485-BL and it will auto join to the TTN V3 network. After join success, it will start to upload message to TTN V3 and user can see in the panel.

259

260

(% aria-label="1652953568895-172.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:1652953568895-172.png||height="232" width="724"]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %)

261

262

263

== 3.3 Configure Device to Read RS485 Sensors ==

264

265

266

There are plenty of RS485 and TTL level devices in the market and each device has different commands to read the valid data. To support these devices in most flexible, RS485-LN supports flexible command set. User can use [[Dragino RS485 Tool>>url:https://www.dropbox.com/sh/us9qecn39fwt8n1/AABREdqUCzEmJMRrfuWuXasoa?dl=0]], [[AT Commands or LoRaWAN Downlink>>url:http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/RS485-LB_Waterproof_RS485UART_to_LoRaWAN_Converter/#H3.5ConfigureRS485-LBviaATorDownlink]] Command to configure how RS485-LN should read the sensor and how to handle the return from RS485 or TTL sensors.

(((

(((

(((

(% style="color:red" %)**Note: below description and commands are for firmware version >v1.1, if you have firmware version v1.0. Please check the [[user manual v1.0>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/&file=RS485-LN_UserManual_v1.0.1.pdf]] or upgrade the firmware to v1.1**

)))

=== 3.3.1 Method 1 ~-~- via RS485 Configure Tool ===

278

279

280

Use the RS485 Configure tool is the recommand method. Please see the instruction of how to use the tool:

281

282

* **[[RS485 Configure Tool Instruction>>url:http://wiki.dragino.com/xwiki/bin/view/Main/RS485_Configure_Tool/]]**

283

284

[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/RS485-LB_Waterproof_RS485UART_to_LoRaWAN_Converter/WebHome/image-20231127144411-1.png?width=494&height=368&rev=1.1||alt="image-20231127144411-1.png" height="368" width="494"]]

285

286

287

=== 3.3.2 Method 2 ~-~- via AT Commands ===

)))

)))

==== 3.3.2.1 Configure UART settings for RS485 communication ====

292

293

294

To use RS485-LN to read data from RS485 sensors, connect the RS485-LN A/B traces to the sensors. The related commands for UART settings are:

295

296

(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)

297

|=(% style="width: 126px; background-color:#4F81BD;color:white" %)(((

298

**AT Commands**

299

)))|=(% style="width: 187px; background-color:#4F81BD;color:white" %)(((

300

**Description**

301

)))|=(% style="width: 197px;background-color:#4F81BD;color:white" %)(((

302

**Example**

303

)))

304

|(% style="width:126px" %)(((

(((

AT+BAUDR

)))

)))|(% style="width:177px" %)(((

311

Set the baud rate (for RS485 connection). Default Value is: 9600.

312

)))|(% style="width:193px" %)(((

(((

AT+BAUDR=9600

)))

(((

Options: (1200,2400,4800,

14400,19200,115200)

)))

)))

|(% style="width:126px" %)(((

323

AT+PARITY

324

)))|(% style="width:177px" %)(((

325

Set UART parity (for RS485 connection)

326

)))|(% style="width:193px" %)(((

(((

AT+PARITY=0

)))

(((

Option: 0: no parity,

1: odd parity,

2: even parity

)))

)))

|(% style="width:126px" %)(((

338

AT+STOPBIT

339

)))|(% style="width:177px" %)(((

340

(((

341

Set serial stopbit (for RS485 connection)

342

)))

343

)))|(% style="width:193px" %)(((

344

(((

345

AT+STOPBIT=0 for 1bit

)))

(((

AT+STOPBIT=1 for 1.5 bit

)))

(((

AT+STOPBIT=2 for 2 bits

)))

)))

=== 3.3.3 Configure sensors ===

(((

Some sensors might need to configure before normal operation. User can configure such sensor via PC and RS485 adapter or through RS485-LN AT Commands (% style="color:#4f81bd" %)**AT+CFGDEV**(%%). Each (% style="color:#4f81bd" %)**AT+CFGDEV **(%%)equals to send a RS485 command to sensors. This command will only run when user input it and won't run during each sampling.

362

)))

363

364

(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)

365

|=(% style="width: 122px; background-color:#4F81BD;color:white" %)**AT Commands**|=(% style="width: 198px; background-color:#4F81BD;color:white" %)**Description**|=(% style="width: 190px;background-color:#4F81BD;color:white" %)**Example**

366

|(% style="width:122px" %)AT+CFGDEV|(% style="width:196px" %)(((

367

(((

368

This command is used to configure the RS485/TTL devices; they won’t be used during sampling.

)))

(((

AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,

)))

(((

mm: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command

377

)))

378

)))|(% style="width:190px" %)AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m

379

380

=== 3.3.4 Configure read commands for each sampling ===

(((

During each sampling, we need confirm what commands we need to send to the RS485 sensors to read data. After the RS485 sensors send back the value, it normally include some bytes and we only need a few from them for a shorten payload.

385

386

To save the LoRaWAN network bandwidth, we might need to read data from different sensors and combine their valid value into a short payload.

387

388

This section describes how to achieve above goals.

389

390

During each sampling, the RS485-LN can support 15 commands to read sensors. And combine the return to one or several uplink payloads.

391

392

393

(% style="color:#037691" %)**Each RS485 commands include two parts:**

394

395

396

~1. What commands RS485-LN will send to the RS485 sensors. There are total 15 commands from **AT+COMMAD1**, **ATCOMMAND2**,…, to **AT+COMMANDF**. All commands are of same grammar.

397

398

2. How to get wanted value the from RS485 sensors returns from by 1). There are total 15 AT Commands to handle the return, commands are **AT+DATACUT1**,**AT+DATACUT2**,…, **AT+DATACUTF** corresponding to the commands from 1). All commands are of same grammar.

399

400

3. Some RS485 device might has longer delay on reply, so user can use AT+CMDDL to set the timeout for getting reply after the RS485 command is sent. For example **AT+CMDDL1=1000** to send the open time to 1000ms

401

402

403

After we got the valid value from each RS485 commands, we need to combine them together with the command **AT+DATAUP**.

404

405

Below are examples for the how above AT Commands works.

406

407

408

(% style="color:#037691" %)**AT+COMMANDx **(%%)**: **This command will be sent to RS485 devices during each sampling, Max command length is 14 bytes. The grammar is:

409

410

(% border="1" style="background-color:#f2f2f2; width:499px" %)

411

|(% style="width:496px" %)(((

412

**AT+COMMANDx=xx xx xx xx xx xx xx xx xx xx xx xx,m**

413

414

**xx xx xx xx xx xx xx xx xx xx xx xx: The RS485 command to be sent**

415

416

**m: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command**

417

)))

418

419

For example, if we have a RS485 sensor. The command to get sensor value is: 01 03 0B B8 00 02 46 0A. Where 01 03 0B B8 00 02 is the Modbus command to read the register 0B B8 where stored the sensor value. The 46 0A is the CRC-16/MODBUS which calculate manually.

420

421

In the RS485-LN, we should use this command AT+COMMAND1=01 03 0B B8 00 02,1 for the same.

422

423

424

If a single command exceeds 14 bytes, you can use the command splicing function.

425

426

When AT+CMDDLx=1, the commands of AT+COMMANDx and AT+COMMAND(x+1) will be merged.

427

428

429

**Examples:** To send 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F data it should be configured:

430

431

AT+COMMAND1=00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D,0

AT+COMMAND1=1

AT+COMMAND2=0E 0F,0

(% style="color:#037691" %)**AT+DATACUTx **(%%)**: **This command defines how to handle the return from AT+COMMANDx, max return length is 100 bytes.

439

440

(% border="1" style="background-color:#f2f2f2; width:510px" %)

441

|(% style="width:510px" %)(((

442

**AT+DATACUTx=a,b,c**

443

444

* **a: length for the return of AT+COMMAND**

445

* **b:1: grab valid value by byte, max 6 bytes. 2: grab valid value by bytes section, max 3 sections.**

446

* **c: define the position for valid value. **

)))

**Examples:**

* (% style="color:#037691" %)**Grab bytes**

453

454

(% aria-label="image-20220602153621-1.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:image-20220602153621-1.png]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %)

* (% style="color:#037691" %)**Grab a section**

459

460

(% aria-label="image-20220602153621-2.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:image-20220602153621-2.png]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %)

* (% style="color:#037691" %)**Grab different sections**

465

466

(% aria-label="image-20220602153621-3.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:image-20220602153621-3.png]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %)

)))

=== 3.3.5 Compose the uplink payload ===

(((

Through AT+COMMANDx and AT+DATACUTx we got valid value from each RS485 commands, Assume these valid value are RETURN1, RETURN2, .., to RETURNx. The next step is how to compose the LoRa Uplink Payload by these RETURNs. The command is **AT+DATAUP.**

)))

(((

(% style="color:#037691" %)**Examples: AT+DATAUP=0**

)))

(((

Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**A SIGNLE UPLINK**.

)))

(((

Final Payload is (% style="color:#4f81bd" %)**Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx**

)))

(((

Where PAYVER is defined by AT+PAYVER, below is an example screen shot.

496

)))

497

498

[[image:image-20220929111027-1.png||height="509" width="685"]](% title="Click and drag to resize" %)

499

500

501

(% style="color:#037691" %)**Examples: AT+DATAUP=1**

502

503

504

Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**Multiply UPLINKs**.

505

506

Final Payload is (% style="color:#4f81bd" %)**PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA**

507

508

509

~1. PAYVER: Defined by AT+PAYVER

510

511

2. PAYLOAD COUNT: Total how many uplinks of this sampling.

512

513

3. PAYLOAD#: Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT)

514

515

4. DATA: Valid value: max 8 bytes for each uplink so each uplink <= 11 bytes. For the last uplink, DATA will might less than 8 bytes

516

517

518

(% aria-label="image-20220602155039-4.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:image-20220602155039-4.png]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %)

519

520

521

So totally there will be 3 uplinks for this sampling, each uplink include 8 bytes DATA

522

523

DATA1=RETURN1 Valid Value + the first two of Valid value of RETURN10= **20 20 0a 33 90 41 02 aa**

524

525

DATA2=3^^rd^^ ~~ 10^^th^^ byte of Valid value of RETURN10= **05 81 0a 20 20 20 20 2d**

526

527

DATA3=the rest of Valid value of RETURN10= **30**

528

529

530

(% style="color:red" %)**Notice: In firmware v1.3, the Max bytes has been changed according to the max bytes in different Frequency Bands for lowest SF. As below:**

531

532

533

~* For AU915/AS923 bands, if UplinkDwell time=0, max 51 bytes for each uplink.

534

535

* For AU915/AS923 bands, if UplinkDwell time=0, max 11 bytes for each uplink.

536

537

* For US915 band, max 11 bytes for each uplink.

538

539

~* For all other bands: max 51 bytes for each uplink.

540

541

542

(% style="color:red" %)** When AT+DATAUP=1, the maximum number of segments is 15, and the maximum total number of bytes is 1500;**

543

544

(% style="color:red" %)** When AT+DATAUP=1 and AT+ADR=0, the maximum number of bytes of each payload is determined by the DR value. (Since v1.4.0)**

545

546

547

Below are the uplink payloads:

548

549

(% aria-label="1654157178836-407.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:1654157178836-407.png]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %)

550

551

552

=== 3.3.6 Uplink on demand ===

553

554

555

Except uplink periodically, RS485-LN is able to uplink on demand. The server send downlink command to RS485-LN and RS485 will uplink data base on the command.

556

557

(% style="color:blue" %)**Downlink control command:**

558

559

(% style="color:#4472c4" %)** 0x08 command**(%%): Poll an uplink with current command set in RS485-LN.

560

561

(% style="color:#4472c4" %)** 0xA8 command**(%%): Send a command to RS485-LN and uplink the output from sensors.

562

563

564

=== 3.3.7 Uplink on Interrupt ===

565

566

567

RS485-LN support external Interrupt uplink since hardware v1.2 release.

568

569

(% aria-label="1654157342174-798.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:1654157342174-798.png]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]]

570

571

572

==== 3.3.7.1 Set Interrupt Mode ====

573

574

575

Before using the interrupt function of the **INT** pin, users can set the interrupt triggering mode as required.

576

577

(% style="color:blue" %)**AT command:**

578

579

* (% style="color:#037691" %)**AT+INTMOD **(%%) ~/~/ Set the trigger interrupt mode

580

581

* (% style="color:#037691" %)**AT+INTMOD=0 **(%%) ~/~/ Disable Interrupt

582

583

* (% style="color:#037691" %)**AT+INTMOD=1 **(%%) ~/~/ Trigger by rising and falling edge

584

585

* (% style="color:#037691" %)**AT+INTMOD=2 **(%%) ~/~/ Trigger by falling edge **(default)**

586

587

* (% style="color:#037691" %)**AT+INTMOD=3 **(%%) ~/~/ Trigger by rising edge

588

589

(% style="color:blue" %)**Downlink Commands: **(% style="color:#037691" %)**0x06**

590

591

Format: Command Code (0x06) followed by 3 bytes.

592

593

Example1: Downlink Payload: **06 00 00 01 **~/~/ AT+INTMOD=1

594

595

Example2: Downlink Payload: **06 00 00 03 **~/~/AT+INTMOD=3

596

597

598

==== 3.3.7.2 Practical application ====

599

600

601

The following uses the default interrupt triggering mode (% style="color:blue" %)**(AT+INTMOD=2)**(%%) as an example to show the interrupt function of (% style="color:blue" %)**INT**(%%):

602

603

When a high voltage is given to the INT pin and then the level of the (% style="color:blue" %)**INT**(%%) pin changes from high to low, the interrupt is triggered by a falling edge and the RS485-LN sends an uplink data.

604

605

(% style="color:red" %)**Note: The level that triggers the interrupt ranges from 3.3V to 24V. Generally, it is recommended to use less than 12V.**

**Example:**

* Use a dry contact to connect the (% style="color:blue" %)**INT**(%%) pin and (% style="color:blue" %)**VIN+**(%%) pin of the RS485-LN.

610

611

When the dry contact is closed, INT and VIN+ conduct and INT is high.

612

613

Disconnecting the dry contact, the level of the INT pin changes from high to low, triggering an interrupt (triggered along the falling edge), and the RS485-LN sends an uplink data.

614

615

[[image:image-20240925174124-5.jpeg||height="439" width="703"]]

616

617

* Use a regulated power supply or a wet contact to connect the 485-LN to trigger the interruption.(This section uses a regulated power supply as an example.)

618

619

The positive pole of the stabilized power supply is connected to the (% style="color:blue" %)**INT**(%%) pin of RS485-LN, and the negative pole of the stabilized power supply is connected to the (% style="color:blue" %)**VIN-**(%%) pin of RS485-LN.

620

621

When the regulated power supply is operating, a high voltage is given to the INT pin and the INT level is high. When the regulated power supply is turned off, the level of the INT pin changes from

622

623

high to low, at which time an interrupt is triggered (triggered along the falling edge), and the device will send an uplink data.

624

625

[[image:image-20240925173243-4.jpeg||height="404" width="900"]]

626

627

* Example of interrupt data in TTN.

628

629

The first byte of the payload of the interrupted packet is (% style="color:blue" %)**0x81**(%%).

630

631

[[image:image-20240925181010-1.png||height="348" width="953"]]

632

633

634

== 3.4 Uplink Payload ==

635

636

637

(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)

638

|(% style="background-color:#4f81bd; color:white; width:70px" %)(((

639

**Size(bytes)**

640

)))|(% style="background-color:#4f81bd; color:white; width:80px" %)**1**|(% style="background-color:#4f81bd; color:white; width:360px" %)(((

641

**Length depends on the return from the commands**

642

)))

643

|(% style="width:90px" %)(((

644

Value

645

)))|(% style="width:114px" %)(((

646

PAYLOAD_VER

647

)))|(% style="width:353px" %)(((

648

If the valid payload is too long and exceed the maximum

649

650

support payload length in server, server will show payload not

651

652

provided in the LoRaWAN server.

653

)))

654

655

(% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](%%)Below is the decoder for the first 3 bytes. The rest bytes are dynamic depends on different RS485 sensors.

656

657

658

== 3.5 Configure RS485-LN via AT or Downlink ==

(((

User can configure RS485-LN via AT Commands or LoRaWAN Downlink Commands

)))

(((

There are two kinds of Commands:

)))

* (((

(% style="color:#4f81bd" %)**Common Commands**(%%): They should be available for each sensor, such as: change uplink interval, reset device. For firmware v1.3, user can find what common commands it supports: [[AT Commands and Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]]

)))

* (((

(% style="color:#4f81bd" %)**Sensor Related Commands**(%%): These commands are special designed for RS485-LN. User can see these commands below:

)))

(((

)))

=== 3.5.1 Common Commands ===

684

685

686

They should be available for each of Dragino Sensors, such as: change uplink interval, reset device. For firmware v1.3, user can find what common commands it supports: [[End Device AT Commands and Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]]

687

688

689

=== 3.5.2 Downlink Response(Since firmware v1.4) ===

690

691

692

Response feature is added to the server's downlink, a special package with a FPort of 200 will be uploaded immediately after receiving the data sent by the server.

693

694

695

(% aria-label="image-20220602163333-5.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:image-20220602163333-5.png||height="263" width="1160"]]

696

697

(% title="Click and drag to resize" %)

698

699

The first byte of this package represents whether the configuration is successful, 00 represents failure, 01 represents success. Except for the first byte, the other is the previous downlink. (All commands except A8 type commands are applicable)

700

701

702

=== 3.5.3 Sensor related commands ===

==== (% style="color:blue" %)**RS485 Debug Command**(%%) ====

(((

This command is used to configure the RS485 devices; they won't be used during sampling. Max Length of AT+CFGDEV is **40 bytes**.

)))

(((

* (% style="color:#037691" %)**AT Command**

715

716

(((

717

(% style="color:#4472c4" %)** AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m** (%%) m: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command

)))

)))

(((

)))

* (((

(% style="color:#037691" %)**Downlink Payload**

)))

(((

Format: (% style="color:#4472c4" %)** A8 MM NN XX XX XX XX YY**

)))

(((

Where:

)))

* (((

MM: 1: add CRC-16/MODBUS ; 0: no CRC

739

)))

740

* (((

741

NN: The length of RS485 command

742

)))

743

* (((

744

XX XX XX XX: RS485 command total NN bytes

)))

* (((

(((

YY: How many bytes will be uplink from the return of this RS485 command,

)))

* (((

if YY=0, RS485-LN will execute the downlink command without uplink;

753

)))

754

* (((

755

if YY>0, RS485-LN will uplink total YY bytes from the output of this RS485 command; Fport=200

756

)))

757

* (((

758

if YY=FF, RS485-LN will uplink RS485 output with the downlink command content; Fport=200.

)))

)))

(((

(% style="color:blue" %)**Example 1:** (%%) ~-~-> Configure without ask for uplink (YY=0)

)))

(((

To connect a Modbus Alarm with below commands.

)))

* (((

The command to active alarm is: 0A 05 00 04 00 01 4C B0. Where 0A 05 00 04 00 01 is the Modbus command to read the register 00 40 where stored the DI status. The 4C B0 is the CRC-16/MODBUS which calculate manually.

)))

* (((

The command to deactivate alarm is: 0A 05 00 04 00 00 8D 70. Where 0A 05 00 04 00 00 is the Modbus command to read the register 00 40 where stored the DI status. The 8D 70 is the CRC-16/MODBUS which calculate manually.

)))

(((

So if user want to use downlink command to control to RS485 Alarm, he can use:

)))

(((

(% style="color:#4f81bd" %)**A8 01 06 0A 05 00 04 00 01 00**(%%): to activate the RS485 Alarm

)))

(((

(% style="color:#4f81bd" %)**A8 01 06 0A 05 00 04 00 00 00**(%%): to deactivate the RS485 Alarm

)))

(((

A8 is type code and 01 means add CRC-16/MODBUS at the end, the 3^^rd^^ byte is 06, means the next 6 bytes are the command to be sent to the RS485 network, the final byte 00 means this command don’t need to acquire output.

)))

(((

)))

(((

(% style="color:blue" %)**Example 2:** (%%)

)))

(((

Check TTL Sensor return:

)))

(((

(((

[[image:http://8.211.40.43/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/test/WebHome/1654132684752-193.png?rev=1.1||alt="1654132684752-193.png"]](% title="Click and drag to resize" %)

)))

)))

==== (% style="color:blue" %)**Set Payload version**(%%) ====

(((

This is the first byte of the uplink payload. RS485-LN can connect to different sensors. User can set the PAYVER field to tell server how to decode the current payload.

)))

(((

* (% style="color:#037691" %)**AT Command:**

828

829

(% style="color:#4472c4" %)** AT+PAYVER: ** (%%) Set PAYVER field = 1

)))

* (((

(% style="color:#037691" %)**Downlink Payload:**

)))

(((

(% style="color:#4472c4" %)** 0xAE 01** (%%) ~-~-> Set PAYVER field = 0x01

)))

(((

(% style="color:#4472c4" %)** 0xAE 0F** (%%) ~-~-> Set PAYVER field = 0x0F

)))

**1 ) Add the interrupt flag at the highest bit of the Payver byte, that is, Byte7 of the first byte. (Since v1.4.0)**

849

850

851

[[image:image-20220824145428-2.png||height="168" width="1300"]]

852

853

854

**2 ) if the data intercepted by AT+DATACUT or AT+MBFUN is empty, it will display NULL, and the payload will be filled with n FFs.**

855

856

857

[[image:image-20220824145428-3.png||height="308" width="1200"]]

==== (% style="color:blue" %)**Set RS485 Sampling Commands**(%%) ====

(((

AT+COMMANDx or AT+DATACUTx

)))

(((

These three commands are used to configure how the RS485-LN polling data from Modbus device. Detail of usage please see : [[polling RS485 device>>||anchor="H3.3.3Configurereadcommandsforeachsampling"]].

)))

(((

)))

* (((

(% style="color:#037691" %)**AT Command:**

878

)))

879

880

(% style="color:#4472c4" %)** AT+COMMANDx: ** (%%) Configure RS485 read command to sensor.

881

882

(% style="color:#4472c4" %)** AT+DATACUTx: **(%%) Configure how to handle return from RS485 devices.

* (((

(% style="color:#037691" %)**Downlink Payload:**

)))

(((

(% style="color:#4472c4" %)** 0xAF**(%%) downlink command can be used to set AT+COMMANDx or AT+DATACUTx.

)))

(((

(% style="color:red" %)**Note : if user use AT+COMMANDx to add a new command, he also need to send AT+DATACUTx downlink.**

)))

(((

Format: (% style="color:#4472c4" %)** AF MM NN LL XX XX XX XX YY**

)))

(((

Where:

)))

* (((

MM: the ATCOMMAND or AT+DATACUT to be set. Value from 01 ~~ 0F,

911

)))

912

* (((

913

NN: 0: no CRC; 1: add CRC-16/MODBUS ; 2: set the AT+DATACUT value.

914

)))

915

* (((

916

LL: The length of AT+COMMAND or AT+DATACUT command

917

)))

918

* (((

919

XX XX XX XX: AT+COMMAND or AT+DATACUT command

920

)))

921

* (((

922

YY: If YY=0, RS485-LN will execute the downlink command without uplink; if YY=1, RS485-LN will execute an uplink after got this command.

)))

(((

**Example:**

)))

(((

(% style="color:#037691" %)**AF 03 01 06 0A 05 00 04 00 01 00**(%%): Same as AT+COMMAND3=0A 05 00 04 00 01,1

)))

(((

(% style="color:#037691" %)**AF 03 02 06**(% style="color:orange" %)** 10 **(% style="color:red" %)**01 **(% style="color:green" %)**05 06 09 0A**(% style="color:#037691" %)** 00**(%%): Same as AT+DATACUT3=(% style="color:orange" %)**16**(%%),(% style="color:red" %)**1**(%%),(% style="color:green" %)**5+6+9+10**

)))

(((

(% style="color:#037691" %)**AF 03 02 06 **(% style="color:orange" %)**0B**(% style="color:red" %)** 02 **(% style="color:green" %)**05 07 08 0A **(% style="color:#037691" %)**00**(%%): Same as AT+DATACUT3=(% style="color:orange" %)**11**(%%),(% style="color:red" %)**2**(%%),(% style="color:green" %)**5~~7+8~~10**

)))

==== (% style="color:blue" %)**Fast command to handle MODBUS device**(%%) ====

(((

(% style="color:#4472c4" %)** AT+MBFUN**(%%) is valid since v1.3 firmware version. The command is for fast configure to read Modbus devices. It is only valid for the devices which follow the [[MODBUS-RTU protocol>>url:https://www.modbustools.com/modbus.html]].

)))

(((

This command is valid since v1.3 firmware version

)))

(((

AT+MBFUN can auto read the Modbus function code: 01, 02, 03 or 04. AT+MBFUN has lower priority vs AT+DATACUT command. If AT+DATACUT command is configured, AT+MBFUN will be ignore.

)))

(((

)))

(((

**Example:**

)))

* (((

AT+MBFUN=1 and AT+DATACUT1/AT+DATACUT2 are not configure (0,0,0). So RS485-LN.

971

)))

972

* (((

973

AT+COMMAND1= 01 03 00 10 00 08,1 ~-~-> read slave address 01 , function code 03, start address 00 01, quantity of registers 00 08.

974

)))

975

* (((

976

AT+COMMAND2= 01 02 00 40 00 10,1 ~-~-> read slave address 01 , function code 02, start address 00 40, quantity of inputs 00 10.

)))

(% aria-label="image-20220602165351-6.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:image-20220602165351-6.png]]

982

983

(% title="Click and drag to resize" %)

984

985

(% aria-label="image-20220602165351-7.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:image-20220602165351-7.png]](% title="Click and drag to resize" %)

986

987

* (((

988

(% style="color:#037691" %)**Downlink Command:**

989

)))

990

991

**~ (% style="color:#4472c4" %)A9 aa(%%)** ~-~-> Same as AT+MBFUN=aa

992

993

994

==== (% style="color:blue" %)**RS485 command timeout**(%%) ====

(((

Some Modbus device has slow action to send replies. This command is used to configure the RS485-LN to use longer time to wait for their action.

)))

(((

Default value: 0, range: 0 ~~ 65 seconds

)))

(((

* (% style="color:#037691" %)** AT Command:**

1007

1008

(% style="color:#4472c4" %)** AT+CMDDLaa=hex(bb cc)*1000**

)))

(((

**Example:**

)))

(((

(% style="color:#4472c4" %)** AT+CMDDL1=1000** (%%)to send the open time to 1000ms

)))

(((

)))

* (((

(% style="color:#037691" %)** Downlink Payload:**

)))

(((

(% style="color:#4472c4" %)** 0x AA aa bb cc**(%%) Same as: AT+CMDDLaa=hex (bb cc)

)))

(((

**Example:**

)))

(((

**0xAA 01 03 E8** ~-~-> Same as **AT+CMDDL1=1000 ms**

)))

==== (% style="color:blue" %)**Uplink payload mode**(%%) ====

(((

Define to use one uplink or multiple uplinks for the sampling.

)))

(((

The use of this command please see: [[Compose Uplink payload>>||anchor="H3.3.4Composetheuplinkpayload"]]

)))

(((

* (% style="color:#037691" %)** AT Command:**

1061

1062

(% style="color:#4472c4" %)** AT+DATAUP=0**

1063

1064

(% style="color:#4472c4" %)** AT+DATAUP=1**

)))

(% style="color:#4472c4" %)** 0xAD 01 00 00 14** (%%) **~-~->** Same as AT+DATAUP=1，20000 ~/~/ (00 00 14 is 20 seconds)

1070

1071

Each uplink is sent to the server at 20-second intervals when segmented.

* (((

(% style="color:#037691" %)** Downlink Payload:**

1076

)))

1077

1078

(% style="color:#4472c4" %)** 0xAD 00** (%%) **~-~->** Same as AT+DATAUP=0

1079

1080

(% style="color:#4472c4" %)** 0xAD 01** (%%) **~-~->** Same as AT+DATAUP=1 ~/~/Each uplink is sent to the server one after the other as it is segmented.

1081

1082

1083

(Since firmware v1.4.0)

1084

1085

* (((

1086

(% style="color:#037691" %)** AT Command:**

1087

)))

1088

1089

(% style="color:#4472c4" %)** AT+DATAUP=1,Timeout**

* (((

(% style="color:#037691" %)** Downlink Payload:**

1094

)))

1095

1096

(% style="color:#4472c4" %)** 0xAD 01 00 00 14** (%%) **~-~->** Same as AT+DATAUP=1，20000 ~/~/ (00 00 14 is 20 seconds)

1097

1098

Each uplink is sent to the server at 20-second intervals when segmented.

1099

1100

1101

==== (% style="color:blue" %)**Cut data separation processing(Since Version 1.4.2)**(%%) ====

1102

1103

1104

AT+NEWLINE command, which only takes effect when AT+DATAUP=1 or AT+DATAUP=1, timeout.

1105

1106

When not set, each part of AT+DATAUP is sent according to the maximum number of bytes of DR.

1107

1108

When setting, each part of AT+DATAUP is sent according to the value set by AT+NEWLINE.

* (((

(% style="color:#037691" %)** AT Command:**

1113

)))

1114

1115

(% style="color:#4472c4" %)//**AT+NEWLINE=ALL**//(%%)// //The data cut out by each AT+COMMANDx command is sent separately as an uplink.

1116

1117

(% style="color:#4472c4" %)//**AT+NEWLINE=ALL**//(%%)// equal： (% style="color:#4472c4" %)**AT+NEWLINE=1+2+3+4+5+6+7+8+9+10+11+12+13+14+15**//

1118

1119

1120

(% style="color:#4472c4" %)//**AT+NEWLINE=a+b+c**//(%%)// //The data returned by all commands is divided into three parts, COMMAND(1~~a) is the first part, COMMAND(a+1~~b) is the second part,COMMAND(b+1~~c) is the third part.

1121

1122

1123

(% style="color:#4472c4" %)//**AT+NEWLINE=NULL**//(%%)// //Turn off the functionality of this AT command.

* (((

(% style="color:#037691" %)** Downlink Payload:**

1128

)))

1129

1130

//AT+NEWLINE=ALL ~-~--> (% style="color:#4472c4" %)**0xAC 01**//

1131

1132

// AT+NEWLINE= NULL ~-~--> (% style="color:#4472c4" %)**0xAC 00**//

1133

1134

//AT+NEWLINE= a+b+c ~-~--> (% style="color:#4472c4" %)**0xAC number of bytes a b c**//

1135

1136

//AT+NEWLINE= 1+5+15 ~-~--> (% style="color:#4472c4" %)**0xAC 03 01 05 0F**//

1137

1138

1139

==== (% style="color:blue" %)**Manually trigger an Uplink**(%%) ====

(((

Ask device to send an uplink immediately.

)))

* (((

(% style="color:#037691" %)** AT Command:**

)))

(((

No AT Command for this, user can press the [[ACT button>>||anchor="H3.7Buttons"]] for 1 second for the same.

)))

(((

)))

* (((

(% style="color:#037691" %)** Downlink Payload:**

)))

(((

(% style="color:#4472c4" %)** 0x08 FF**(%%), RS485-LN will immediately send an uplink.

)))

==== (% style="color:blue" %)**Clear RS485 Command**(%%) ====

(((

The AT+COMMANDx and AT+DATACUTx settings are stored in special location, user can use below command to clear them.

)))

* (((

(% style="color:#037691" %)** AT Command:**

)))

(((

(% style="color:#4472c4" %)** AT+CMDEAR=mm,nn** (%%) mm: start position of erase ,nn: stop position of erase

)))

(((

Etc. AT+CMDEAR=1,10 means erase AT+COMMAND1/AT+DATACUT1 to AT+COMMAND10/AT+DATACUT10

)))

(((

Example screen shot after clear all RS485 commands.

)))

(((

)))

(((

The uplink screen shot is:

1202

)))

1203

1204

(% aria-label="1654160691922-496.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:1654160691922-496.png]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %)

* (((

(% style="color:#037691" %)** Downlink Payload:**

)))

(((

(% style="color:#4472c4" %)** 0x09 aa bb** (%%) same as AT+CMDEAR=aa,bb

)))

==== (% style="color:blue" %)**Set Serial Communication Parameters**(%%) ====

(((

Set the Rs485 serial communication parameters:

)))

(((

(% style="color:#037691" %)**AT Command:**

)))

(((

* Set Baud Rate

)))

(% style="color:#4472c4" %)** AT+BAUDR=9600** (%%) ~/~/ Options: (200~~115200) When using low baud rate or receiving multiple bytes, you need to use AT+CMDDL to increase the receive timeout (the default receive timeout is 400ms), otherwise data will be lost

(((

* Set UART Parity

)))

(% style="color:#4472c4" %)** AT+PARITY=0** (%%) ~/~/ Option: 0: no parity, 1: odd parity, 2: even parity

(((

* Set STOPBIT

)))

(% style="color:#4472c4" %)** AT+STOPBIT=0** (%%) ~/~/ Option: 0 for 1bit; 1 for 1.5 bit ; 2 for 2 bits

(((

(% style="color:#037691" %)**Downlink Payload:**

)))

(((

(% style="color:#4472c4" %)** A7 01 aa bb**: (%%) Same AT+BAUDR=hex(aa bb)*100

)))

(((

**Example:**

)))

* (((

A7 01 00 60 same as AT+BAUDR=9600

1264

)))

1265

* (((

1266

A7 01 04 80 same as AT+BAUDR=115200

)))

(((

* A7 02 aa: Same as AT+PARITY=aa (aa value: 00 , 01 or 02)

)))

(((

* A7 03 aa: Same as AT+STOPBIT=aa (aa value: 00 , 01 or 02)

)))

==== (% style="color:blue" %)**Configure Databit (Since Version 1.4.0)**(%%) ====

* (((

(% style="color:#037691" %)** AT Command:**

1286

)))

1287

1288

(% style="color:#4472c4" %)** AT+DATABIT=7 **(%%)~/~/ Set the data bits to 7

1289

1290

(% style="color:#4472c4" %)** AT+DATABIT=8 **(%%)~/~/ Set the data bits to 8

1291

1292

* (((

1293

(% style="color:#037691" %)**Downlink Payload:**

1294

)))

1295

1296

(% style="color:#4472c4" %)** A7 04 07**(%%): Same as AT+DATABIT=7

1297

1298

(% style="color:#4472c4" %)** A7 04 08**(%%): Same as AT+DATABIT=8

==== (% style="color:blue" %)**Encrypted payload(Since Version 1.4.0)**(%%) ====

(((

)))

* (((

(% style="color:#037691" %)** AT Command:**

1310

)))

1311

1312

(% style="color:#4472c4" %)** AT+DECRYPT=1 ** (%%) ~/~/ The payload is uploaded without encryption

1313

1314

(% style="color:#4472c4" %)** AT+DECRYPT=0 ** (%%) ~/~/ Encrypt when uploading payload (default)

==== (% style="color:blue" %)**Get sensor value(Since Version 1.4.0)**(%%) ====

* (((

(% style="color:#037691" %)** AT Command:**

1323

)))

1324

1325

(% style="color:#4472c4" %)** AT+GETSENSORVALUE=0 **(%%) ~/~/ The serial port gets the reading of the current sensor

1326

1327

(% style="color:#4472c4" %)** AT+GETSENSORVALUE=1 **(%%) ~/~/ The serial port gets the current sensor reading and uploads it.

==== (% style="color:blue" %)**Resets the downlink packet count(Since Version 1.4.0)**(%%) ====

* (((

(% style="color:#037691" %)** AT Command:**

1336

)))

1337

1338

(% style="color:#4472c4" %)** AT+DISFCNTCHECK=0 **(%%) ~/~/ When the downlink packet count sent by the server is less than the node downlink packet count or exceeds 16384, the node will no longer receive downlink packets (default)

1339

1340

(% style="color:#4472c4" %)** AT+DISFCNTCHECK=1 **(%%) ~/~/ When the downlink packet count sent by the server is less than the node downlink packet count or exceeds 16384, the node resets the downlink packet count and keeps it consistent with the server downlink packet count.

==== (% style="color:blue" %)**When the limit bytes are exceeded, upload in batches(Since Version 1.4.0)**(%%) ====

* (((

(% style="color:#037691" %)** AT Command:**

1349

)))

1350

1351

(% style="color:#4472c4" %)** AT+DISMACANS=0** (%%) ~/~/ When the MACANS of the reply server plus the payload exceeds the maximum number of bytes of 11 bytes (DR0 of US915, DR2 of AS923, DR2 of AU195), the node will send a packet with a payload of 00 and a port of 4. (default)

1352

1353

(% style="color:#4472c4" %)** AT+DISMACANS=1** (%%) ~/~/ When the MACANS of the reply server plus the payload exceeds the maximum number of bytes of the DR, the node will ignore the MACANS and not reply, and only upload the payload part.

* (((

(% style="color:#037691" %)** Downlink Payload:**

1358

)))

1359

1360

(% style="color:#4472c4" %)** 0x21 00 01 ** (%%) ~/~/ Set the DISMACANS=1

==== (% style="color:blue" %)**Copy downlink to uplink (Since Version 1.4.0)**(%%) ====

* (((

(% style="color:#037691" %)** AT Command:**

1369

)))

1370

1371

(% style="color:#4472c4" %)** AT+RPL=5** (%%) ~/~/ After receiving the package from the server, it will immediately upload the content of the package to the server, the port number is 100.

1372

1373

Example：**aa xx xx xx xx** ~/~/ aa indicates whether the configuration has changed, 00 is yes, 01 is no; xx xx xx xx are the bytes sent.

1374

1375

1376

[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LSN50%20%26%20LSN50-V2%20-%20LoRaWAN%20Sensor%20Node%20User%20Manual/WebHome/image-20220823173747-6.png?width=1124&height=165&rev=1.1||alt="image-20220823173747-6.png"]]

1377

1378

For example, sending 11 22 33 44 55 66 77 will return invalid configuration 00 11 22 33 44 55 66 77.

[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LSN50%20%26%20LSN50-V2%20-%20LoRaWAN%20Sensor%20Node%20User%20Manual/WebHome/image-20220823173833-7.png?width=1124&height=149&rev=1.1||alt="image-20220823173833-7.png"]]

1383

1384

For example, if 01 00 02 58 is issued, a valid configuration of 01 01 00 02 58 will be returned.

==== (% style="color:blue" %)**Query version number and frequency band 、TDC(Since Version 1.4.0)**(%%) ====

(((

* (% style="color:#037691" %)**Downlink Payload:**

1393

1394

(% style="color:#4472c4" %)** 26 01 ** (%%) ~/~/ Downlink 26 01 can query device upload frequency, frequency band, software version number, TDC time.

)))

Example：

[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LSN50%20%26%20LSN50-V2%20-%20LoRaWAN%20Sensor%20Node%20User%20Manual/WebHome/image-20220823173929-8.png?width=1205&height=76&rev=1.1||alt="image-20220823173929-8.png"]]

==== (% style="color:blue" %)** Monitor RS485 communication of other devices(Since Version 1.4.0)**(%%) ====

* (((

(% style="color:#037691" %)** AT Command:**

1409

)))

1410

1411

(% style="color:#4472c4" %)**AT+RXMODE=1,10** (%%) ~/~/ When the RS485-LN receives more than 10 bytes from the RS485, it immediately sends the uplink of the received data.

1412

1413

(% style="color:#4472c4" %)**AT+RXMODE=2,500 ** (%%) ~/~/ RS485-LN uploads data as uplink from the first byte received by RS485 to the data received within 500ms after that.

1414

1415

(% style="color:#4472c4" %)**AT+RXMODE=0,0 ** (%%) ~/~/ Disable this mode (default)

* (((

(% style="color:#037691" %)**Downlink Payload:**

1420

)))

1421

1422

(% style="color:#4472c4" %)** A6 aa bb bb ** (%%) ~/~/ same as AT+RXMODE=aa,bb

1423

1424

[[image:image-20220824144240-1.png]]

1425

1426

1427

== 3.6 Listening mode for RS485 network ==

(((

This feature support since firmware v1.4

)))

(((

RS485-LN supports listening mode, it can listen the RS485 network packets and send them via LoRaWAN uplink. Below is the structure. The blue arrow shows the RS485 network packets to RS485-LN.

1436

1437

[[image:image-20240928104143-6.png||height="487" width="797"]]

1438

)))

1439

1440

(% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]]

1441

1442

(% title="Click and drag to resize" %)

1443

1444

(((

1445

To enable the listening mode, use can run the command (% style="color:#4472c4" %)** AT+RXMODE**.

1446

)))

1447

1448

(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)

1449

|=(% style="width: 156px; background-color:#4F81BD;color:white" %)(((

1450

**Command example**

1451

)))|=(% style="width: 355px; background-color:#4F81BD;color:white" %)(((

1452

**Function**

1453

)))

1454

|(% style="width:156px" %)(((

1455

AT+RXMODE=1,10

1456

)))|(% style="width:352px" %)(((

1457

Enable listening mode 1, if RS485-LN has received more than 10 RS485 commands from the network. RS485-LN will send these commands via LoRaWAN uplinks.

1458

)))

1459

|(% style="width:156px" %)(((

1460

AT+RXMODE=2,500

1461

)))|(% style="width:352px" %)(((

1462

Enable listening mode 2, RS485-LN will capture and send a 500ms content once from the first detect of character. Max value is 65535 ms

1463

)))

1464

|(% style="width:156px" %)(((

1465

AT+RXMODE=0,0

1466

)))|(% style="width:352px" %)(((

1467

Disable listening mode. This is the default settings.

1468

)))

1469

|(% style="width:156px" %)(((

1470

1471

)))|(% style="width:352px" %)(((

1472

A6 aa bb cc same as AT+RXMODE=aa,(bb<<8 | cc)

)))

(((

(% style="color:#037691" %)**Downlink Command:**

)))

(((

(% style="color:#4472c4" %)** 0xA6 aa bb cc **(%%) same as AT+RXMODE=aa,(bb<<8 | cc)

)))

(((

)))

(((

**Example**:

)))

(((

The RS485-LN is set to AT+RXMODE=2,1000

)))

(((

There is a two Modbus commands in the RS485 network as below:

)))

(((

The Modbus master send a command: (% style="background-color:#ffc000" %)**01 03 00 00 00 02 c4 0b**

)))

(((

And Modbus slave reply with: (% style="background-color:green" %)**01 03 04 00 00 00 00 fa 33**

)))

(((

RS485-LN will capture both and send the uplink: (% style="background-color:#ffc000" %)**01 03 00 00 00 02 c4 0b **(% style="background-color:green" %)**01 03 04 00 00 00 00 fa 33**

)))

(((

(% aria-label="image-20220602171200-9.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:image-20220602171200-9.png]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %)

)))

(((

(% style="color:red" %)**Notice: Listening mode can work with the default polling mode of RS485-LN. When RS485-LN is in to send the RS485 commands (from AT+COMMANDx), the listening mode will be interrupt for a while.**

)))

== 3.7 Buttons ==

(% border="1.5" cellspacing="4" style="background-color:#f2f2f2; width:430px" %)

1530

|=(% style="width: 50px;background-color:#4F81BD;color:white" %)**Button**|=(% style="width: 380px;background-color:#4F81BD;color:white" %)**Feature**

1531

|(% style="width:50px" %)ACT|(% style="width:361px" %)If RS485 joined in network, press this button for more than 1 second, RS485 will upload a packet, and the SYS LED will give a (% style="color:blue" %)**Blue blink**

1532

|(% style="width:50px" %)RST|(% style="width:361px" %)Reboot RS485

1533

|(% style="width:50px" %)PRO|(% style="width:361px" %)Use for upload image, see [[How to Update Image>>||anchor="H6.1Howtoupgradetheimage3F"]]

== 3.8 LEDs ==

(% border="1.5" cellspacing="4" style="background-color:#f2f2f2; width:430px" %)

1539

|=(% style="width: 50px;background-color:#4F81BD;color:white" %)**LEDs**|=(% style="width: 380px;background-color:#4F81BD;color:white" %)**Feature**

1540

|PWR|Always on if there is power

1541

|SYS|After device is powered on, the SYS will (% style="color:green" %)**fast blink in GREEN**(%%) for 5 times, means RS485-LN start to join LoRaWAN network. If join success, SYS will be (% style="color:green" %)**on GREEN for 5 seconds** (%%)**. **SYS will (% style="color:green" %)**blink Blue**(%%) on every upload and (% style="color:green" %)**blink Green**(%%) once receive a downlink message.

= 4. Case Study =

User can check this URL for some case studies: [[APP RS485 COMMUNICATE WITH SENSORS>>doc:Main.Application Note \: Communicate with Different Sensors ----- RS485-LN RS485-BL.WebHome]]

1547

1548

1549

= 5. Use AT Command =

1550

1551

== 5.1 Access AT Command ==

(((

RS485-LN supports AT Command set. User can use a USB to TTL adapter plus the 3.5mm Program Cable to connect to RS485-LN to use AT command, as below.

1556

)))

1557

1558

(% aria-label="1654162355560-817.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:1654162355560-817.png]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %)

(((

In PC, User needs to set (% style="color:blue" %)**serial tool**(%%)(such as [[putty>>url:https://www.chiark.greenend.org.uk/~~sgtatham/putty/latest.html]], SecureCRT) baud rate to (% style="color:green" %)**9600**(%%) to access to access serial console of RS485-LN. The default password is 123456. Below is the output for reference:

1563

)))

1564

1565

(% aria-label="1654162368066-342.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:1654162368066-342.png]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %)

(((

More detail AT Command manual can be found at [[AT Command Manual>>https://www.dragino.com/downloads/index.php?dir=LT_LoRa_IO_Controller/LT33222-L/]]

)))

== 5.2 Common AT Command Sequence ==

1574

1575

=== 5.2.1 Multi-channel ABP mode (Use with SX1301/LG308) ===

1576

1577

1578

If device has not joined network yet:

1579

1580

* (% style="color:#037691" %)**AT+FDR**

1581

* (% style="color:#037691" %)**AT+NJM=0**

1582

* (% style="color:#037691" %)**ATZ**

(((

If device already joined network:

1588

1589

* (% style="color:#037691" %)**AT+NJM=0**

1590

* (% style="color:#037691" %)**ATZ**

)))

=== 5.5.2 Single-channel ABP mode (Use with LG01/LG02) ===

1597

1598

1599

(% style="background-color:#dcdcdc" %)**AT+FDR** (%%) Reset Parameters to Factory Default, Keys Reserve

1600

1601

(% style="background-color:#dcdcdc" %)**AT+NJM=0 **(%%) Set to ABP mode

1602

1603

(% style="background-color:#dcdcdc" %)**AT+ADR=0** (%%) Set the Adaptive Data Rate Off

1604

1605

(% style="background-color:#dcdcdc" %)**AT+DR=5** (%%) Set Data Rate

1606

1607

(% style="background-color:#dcdcdc" %)**AT+TDC=60000** (%%) Set transmit interval to 60 seconds

1608

1609

(% style="background-color:#dcdcdc" %)**AT+CHS=868400000**(%%) Set transmit frequency to 868.4Mhz

1610

1611

(% style="background-color:#dcdcdc" %)**AT+RX2FQ=868400000** (%%) Set RX2Frequency to 868.4Mhz (according to the result from server)

1612

1613

(% style="background-color:#dcdcdc" %)**AT+RX2DR=5** (%%) Set RX2DR to match the downlink DR from server. see below

1614

1615

(% style="background-color:#dcdcdc" %)**AT+DADDR=26** (%%) 01 1A F1 Set Device Address to 26 01 1A F1, this ID can be found in the LoRa Server portal.

1616

1617

(% style="background-color:#dcdcdc" %)**ATZ** (%%) Reset MCU

1618

1619

1620

(% style="color:red" %)**Note:**

1621

1622

(((

1623

(% style="color:red" %)1. Make sure the device is set to ABP mode in the IoT Server.

1624

2. Make sure the LG01/02 gateway RX frequency is exactly the same as AT+CHS setting.

1625

3. Make sure SF / bandwidth setting in LG01/LG02 match the settings of AT+DR. refer [[this link>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/&file=LoRaWAN%201.0.3%20Regional%20Parameters.xlsx]] to see what DR means.

1626

4. The command AT+RX2FQ and AT+RX2DR is to let downlink work. to set the correct parameters, user can check the actually downlink parameters to be used. As below. Which shows the RX2FQ should use 868400000 and RX2DR should be 5

)))

(% aria-label="1654162478620-421.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:1654162478620-421.png]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %)

= 6. FAQ =

== 6.1 How to upgrade the image? ==

(((

The RS485-LN LoRaWAN Controller is shipped with a 3.5mm cable, the cable is used to upload image to RS485-LN to:

)))

* (((

Support new features

)))

* (((

For bug fix

)))

* (((

Change LoRaWAN bands.

)))

(((

Below shows the hardware connection for how to upload an image to RS485-LN:

1655

)))

1656

1657

(% aria-label="1654162535040-878.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:1654162535040-878.png]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]]

1658

1659

(% title="Click and drag to resize" %)

1660

1661

(((

1662

(% style="color:blue" %)**Step1**(%%)**:** Download [[flash loader>>url:https://www.st.com/content/st_com/en/products/development-tools/software-development-tools/stm32-software-development-tools/stm32-programmers/flasher-stm32.html]].

)))

(((

(% style="color:blue" %)**Step2**(%%)**:** Download the [[LT Image files>>url:https://www.dropbox.com/sh/g99v0fxcltn9r1y/AACP33wo_ZQLsxW2MJ70oUoba/RS485-LN/Firmware?dl=0&subfolder_nav_tracking=1]].

)))

(((

(% style="color:blue" %)**Step3**(%%)**: **Open flashloader; choose the correct COM port to update.

)))

(((

(((

(((

(% style="color:blue" %) Hold down the PRO button and then momentarily press the RST reset button and the SYS led will change from OFF to ON, While SYS LED is RED ON, it means the RS485-LN is ready to be program.

)))

)))

)))

(% aria-label="image-20220602175818-12.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:image-20220602175818-12.png]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %)

1689

1690

1691

(% aria-label="image-20220602175848-13.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:image-20220602175848-13.png]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %)

1692

1693

1694

(% aria-label="image-20220602175912-14.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:image-20220602175912-14.png]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %)

1695

1696

1697

(% style="color:red" %)**Users can select the new burning software STM32Cubeprogramer for firmware upgrade and follow the same connection steps to enter burning mode (until SYS LED is RED ON):**

1698

1699

[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H4.2.FirmwareupgradeusingSTM32Cubeprogramer>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H4.2.FirmwareupgradeusingSTM32Cubeprogramer]]

1700

1701

1702

(% style="color:red" %)**Notice**: **In case user has lost the program cable. User can hand made one from a 3.5mm cable. The pin mapping is:**

1703

1704

(% aria-label="image-20220602175638-10.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:image-20220602175638-10.png]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %)

1705

1706

1707

== 6.2 How to change the LoRa Frequency Bands/Region? ==

1708

1709

1710

User can follow the introduction for [[how to upgrade image>>||anchor="H6.1Howtoupgradetheimage3F"]]. When download the images, choose the required image file for download.

1711

1712

1713

== 6.3 How many RS485-Slave can RS485-LN connects? ==

1714

1715

1716

The RS485-LN can support max 32 RS485 devices. Each uplink command of RS485-LN can support max 15 different RS485 command. So RS485-LN can support max 15 RS485 devices pre-program in the device for uplink. For other devices no pre-program, user can use the [[downlink message (type code 0xA8) to poll their info>>||anchor="H3.3.3Configurereadcommandsforeachsampling"]].

1717

1718

1719

== 6.4 Compatible question to ChirpStack and TTI LoRaWAN server ? ==

1720

1721

1722

When user need to use with ChirpStack or TTI. Please set AT+RPL=4.

1723

1724

Detail info check this link: [[Set Packet Receiving Response Level>>doc:Main.End Device AT Commands and Downlink Command.WebHome||anchor="H7.23SetPacketReceivingResponseLevel"]]

1725

1726

1727

== 6.5 Can i use point to point communication for RS485-LN? ==

1728

1729

1730

Yes, please updating point-to-point [[firmware>>https://www.dropbox.com/sh/g99v0fxcltn9r1y/AACP33wo_ZQLsxW2MJ70oUoba/RS485-LN/Firmware?dl=0&subfolder_nav_tracking=1]]，then refer [[Point to Point Communication for RS485-LN>>Point to Point Communication for RS485-LN]].

1731

1732

1733

== 6.6 How to Use RS485-LN to connect to RS232 devices? ==

1734

1735

1736

[[Use RS485-BL or RS485-LN to connect to RS232 devices. - DRAGINO>>url:http://8.211.40.43:8080/xwiki/bin/view/Main/RS485%20to%20RS232/]]

1737

1738

1739

== 6.7 How to judge whether there is a problem with the set COMMAND ==

1740

1741

=== 6.7.1 Introduce: ===

1742

1743

1744

Users can use below the structure to fast debug the communication between RS485BL and RS485-LN. The principle is to put the PC in the RS485 network and sniff the packet between Modbus MTU and RS485-BL/LN. We can use this way to:

1745

1746

1. Test if Modbus-MTU works with PC commands.

1747

1. Check if RS485-LN sent the expected command to Mobus-MTU

1748

1. Check if Modbus-MTU return back the expected result to RS485-LN.

1749

1. If both b) and c) has issue, we can compare PC’s output and RS485-LN output.

1750

1751

[[image:image-20240816112950-1.png||height="382" width="731"]]

Example Connection:

[[image:image-20221130104310-2.png]]

1757

1758

1759

=== 6.7.2 Set up PC to monitor RS485 network With Serial tool ===

1760

1761

1762

(% style="color:red" %)**Note: Receive and send set to hex mode**

1763

1764

[[image:image-20221130104310-3.png||height="616" width="714"]]

1765

1766

1767

=== 6.7.3 With ModRSsim2: ===

1768

1769

1770

(% style="color:blue" %)**(1) Select serial port MODBUS RS-232**

1771

1772

[[image:image-20221130104310-4.png||height="390" width="865"]]

1773

1774

1775

(% style="color:blue" %)**(2) Click the serial port icon**

1776

1777

[[image:image-20221130104310-5.png||height="392" width="870"]]

1778

1779

1780

(% style="color:blue" %)**(3) After selecting the correct serial port and baud rate, click ok**

1781

1782

[[image:image-20221130104310-6.png]]

1783

1784

1785

(% style="color:blue" %)**(4) Click the comms.**

1786

1787

[[image:image-20221130104310-7.png||height="376" width="835"]]

1788

1789

(% class="wikigeneratedid" id="HRunRS485-LN2FBLcommandandmonitorifitiscorrect." %)

1790

**Run RS485-LN/BL command and monitor if it is correct.**

1791

1792

1793

=== 6.7.4 Example – Test the CFGDEV command ===

1794

1795

1796

RS485-LN sent below command:

1797

1798

(% style="color:blue" %)**AT+CFGDEV=01 03 00 20 00 01,1**(%%) to RS485 network, and PC is able to get this command and return commands from MTU to show in the serial tool.

1799

1800

1801

We can see the output from the Serial port tool to analyze. And check if they are expected result.

1802

1803

[[image:image-20221130104310-8.png||height="214" width="797"]]

1804

1805

1806

We can also use (% style="color:blue" %)**ModRSsim2**(%%) to see the output.

1807

1808

[[image:image-20221130104310-9.png||height="531" width="729"]]

1809

1810

1811

=== 6.7.5 Example – Test CMD command sets. ===

1812

1813

1814

Run (% style="color:blue" %)**AT+GETSENSORVALUE=1**(%%) to test the CMD commands set in RS485-LN.

1815

1816

1817

(% style="color:blue" %)**Serial port tool:**

1818

1819

[[image:image-20221130104310-10.png||height="339" width="844"]]

1820

1821

1822

(% style="color:blue" %)**ModRSsim2:**

1823

1824

[[image:image-20221130104310-11.png||height="281" width="962"]]

1825

1826

1827

=== 6.7.6 Test with PC ===

1828

1829

1830

If there is still have problem to set up correctly the commands between RS485-LN and MTU. User can test the correct RS485 command set in PC and compare with the RS485 command sent out via RS485-LN. as long as both commands are the same, the MTU should return correct result.

1831

1832

1833

Or User can send the working commands set in PC serial tool to Dragino Support to check what should be configured in RS485-LN.

1834

1835

(% style="color:blue" %)**Connection method：**

1836

1837

[[image:image-20221130104310-12.png]]

1838

1839

1840

(% style="color:blue" %)**Link situation:**

1841

1842

[[image:image-20221130104310-13.png||height="458" width="486"]]

1843

1844

1845

[[image:image-20221130104310-14.png||height="371" width="823"]]

1846

1847

1848

== 6.8 Where to get the decoder for RS485-LN? ==

1849

1850

1851

The decoder for RS485-LN needs to be written by yourself. Because the sensor to which the user is connected is custom, the read device data bytes also need custom parsing, so there is no universal decoder. We can only provide [[templates>>https://github.com/dragino/dragino-end-node-decoder/tree/main/RS485-LN]] for decoders (no intermediate data parsing part involved)

1852

1853

1854

== 6.9 How to configure RS485 commands more conveniently？ ==

1855

1856

1857

Dragino has developed an application for the RS485 series of products.

1858

1859

It can help you configure RS485 sensors more conveniently

1860

Please refer to the link below for specific usage：

1861

1862

[[RS485 Configure Tool - DRAGINO>>url:http://wiki.dragino.com/xwiki/bin/view/Main/RS485_Configure_Tool/#HTableofContentsFF1A]]

== 6.10 How to determine whether the returned data value FF is valid data or invalid data? ==

1867

1868

The address of the returned data can be used as a flag.

1869

1870

The customer uses the intercept command to intercept the first bit of the returned data (the slave address of the sensor) as a judgment flag.

**Invalid data:**

If the first bit and the data are both FF, it means the data is empty.

**Valid data:**

If the first bit is a normal slave address and the data is FF, it means the data is normal.

1879

1880

1881

= 7. Trouble Shooting =

1882

1883

== 7.1 Downlink doesn't work, how to solve it? ==

1884

1885

1886

Please see this link for debug: [[LoRaWAN Communication Debug>>doc:Main.LoRaWAN Communication Debug.WebHome]]

1887

1888

1889

== 7.2 Why customers can't join TTN V3 in US915 /AU915 bands? ==

1890

1891

1892

It might about the channels mapping. Please see for detail: [[Notice of Frequency band>>doc:Main.LoRaWAN Communication Debug.WebHome||anchor="H2.NoticeofUS9152FCN4702FAU915Frequencyband"]]

1893

1894

1895

== 7.3 Why can't customers see the device's data in the server when the data is too long? ==

1896

1897

1898

This is due to the limitation of the lorawan protocol, and the fixed DR needs to be adjusted to improve this problem.

1899

1900

Please refer to the following link for the number of bytes limited by different frequencies and different DRs in the lorawan protocol

1901

1902

[[lora-alliance.org/wp-content/uploads/2021/05/RP002-1.0.3-FINAL-1.pdf>>url:https://lora-alliance.org/wp-content/uploads/2021/05/RP002-1.0.3-FINAL-1.pdf]]

Example:

[[image:image-20240620145456-1.png]]

1907

1908

Please refer to the following command to fix DR

AT+ADR=0

AT+DR=3

Downlink command:

[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20AT%20Commands%20and%20Downlink%20Command/#H7.4DataRate>>http://wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20AT%20Commands%20and%20Downlink%20Command/#H7.4DataRate]]

= 8. Order Info =

(% style="color:blue" %)**Part Number: RS485-LN-XXX**

1923

1924

(% style="color:blue" %)**XXX:**

1925

1926

* (% style="color:red" %)**EU433**(%%): frequency bands EU433

1927

* (% style="color:red" %)**EU868**(%%): frequency bands EU868

1928

* (% style="color:red" %)**KR920**(%%): frequency bands KR920

1929

* (% style="color:red" %)**CN470**(%%): frequency bands CN470

1930

* (% style="color:red" %)**AS923**(%%): frequency bands AS923

1931

* (% style="color:red" %)**AU915**(%%): frequency bands AU915

1932

* (% style="color:red" %)**US915**(%%): frequency bands US915

1933

* (% style="color:red" %)**IN865**(%%): frequency bands IN865

1934

* (% style="color:red" %)**RU864**(%%): frequency bands RU864

1935

* (% style="color:red" %)**KZ865**(%%): frequency bands KZ865

= 9. Packing Info =

**Package Includes**:

1941

1942

* RS485-LN x 1

1943

* Stick Antenna for LoRa RF part x 1

1944

* Program cable x 1

1945

1946

**Dimension and weight**:

1947

1948

* Device Size: 13.5 x 7 x 3 cm

1949

* Device Weight: 105g

1950

* Package Size / pcs : 14.5 x 8 x 5 cm

1951

* Weight / pcs : 170g

1952

1953

= 10. FCC Caution for RS485LN-US915 =

(((

Any Changes or modifications not expressly approved by the party responsible for compliance could void the user's authority to operate the equipment.

)))

(((

This device complies with part 15 of the FCC Rules. Operation is subject to the following two conditions: (1) This device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation.

)))

(((

)))

(((

(% style="color:red" %)**IMPORTANT NOTE:**

)))

(((

(% style="color:red" %)**Note: **(%%)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:

)))

(((

—Reorient or relocate the receiving antenna.

)))

(((

—Increase the separation between the equipment and receiver.

)))

(((

—Connect the equipment into an outlet on a circuit different from that to which the receiver is connected.

)))

(((

—Consult the dealer or an experienced radio/TV technician for help.

)))

(((

)))

(((

(% style="color:red" %)**FCC Radiation Exposure Statement:**

)))

(((

This equipment complies with FCC radiation exposure limits set forth for an uncontrolled environment.This equipment should be installed and operated with minimum distance 20cm between the radiator& your body.

)))

= 11. Support =

* (((

Support is provided Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different timezones we cannot offer live support. However, your questions will be answered as soon as possible in the before-mentioned schedule.

2010

)))

2011

* (((

2012

Provide as much information as possible regarding your enquiry (product models, accurately describe your problem and steps to replicate it etc) and send a mail to [[support@dragino.com>>url:file:///D:/市场资料/说明书/LoRa/LT系列/support@dragino.com]].

)))

Wiki source code of RS485-LN – RS485 to LoRaWAN Converter User Manual

Applications

Navigation