RS485-LN – RS485 to LoRaWAN Converter

The Dragino RS485-LN is a RS485 to LoRaWAN Converter. It converts the RS485 signal into LoRaWAN wireless signal which simplify the IoT installation and reduce the installation/maintaining cost.

22

)))

23

24

(((

25

RS485-LN allows user to 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, smartphone detection, building automation, and so on.

)))

(((

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.

)))

(((

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.

)))

)))

[[image:1653267211009-519.png||height="419" width="724"]]

38

39

== 1.2 Specifications ==

**Hardware System:**

* STM32L072CZT6 MCU

* SX1276/78 Wireless Chip

45

* Power Consumption (exclude RS485 device):

** Idle: 32mA@12v

*

** 20dB Transmit: 65mA@12v

50

51

**Interface for Model:**

52

53

* RS485

54

* Power Input 7~~ 24V DC.

**LoRa Spec:**

* Frequency Range:

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

60

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

61

* 168 dB maximum link budget.

62

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

63

* +14 dBm high efficiency PA.

64

* Programmable bit rate up to 300 kbps.

65

* High sensitivity: down to -148 dBm.

66

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

67

* Excellent blocking immunity.

68

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

69

* Fully integrated synthesizer with a resolution of 61 Hz.

70

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

71

* Built-in bit synchronizer for clock recovery.

72

* Preamble detection.

73

* 127 dB Dynamic Range RSSI.

74

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

75

* Packet engine up to 256 bytes with CRC.

== 1.3 Features ==

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

80

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

81

* AT Commands to change parameters

82

* Remote configure parameters via LoRa Downlink

83

* Firmware upgradable via program port

84

* Support multiply RS485 devices by flexible rules

85

* Support Modbus protocol

86

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

87

88

== 1.4 Applications ==

89

90

* Smart Buildings & Home Automation

91

* Logistics and Supply Chain Management

* Smart Metering

* Smart Agriculture

* Smart Cities

* Smart Factory

== 1.5 Firmware Change log ==

98

99

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

100

101

== 1.6 Hardware Change log ==

(((

(((

v1.2: Add External Interrupt Pin.

v1.0: Release

)))

)))

= 2. Power ON Device =

112

113

(((

114

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

115

116

* Power Source VIN to RS485-LN VIN+

117

* Power Source GND to RS485-LN VIN-

118

119

(((

120

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

121

)))

122

123

[[image:1653268091319-405.png]]

124

)))

125

126

= 3. Operation Mode =

127

128

== 3.1 How it works? ==

129

130

(((

131

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.

132

)))

133

134

== 3.2 Example to join LoRaWAN network ==

135

136

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.

137

138

[[image:1653268155545-638.png||height="334" width="724"]]

139

140

(((

141

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:

142

143

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

144

145

[[image:1653268227651-549.png||height="592" width="720"]]

146

147

(((

148

The LG308 is already set to connect to [[TTN V3 network >>path:eu1.cloud.thethings.network/]]. So what we need to now is only configure the TTN V3:

)))

(((

**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:

)))

)))

[[image:1652953462722-299.png]]

(((

(((

User can enter this key in their LoRaWAN Server portal. Below is TTN V3 screen shot:

)))

(((

Add APP EUI in the application.

)))

)))

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

173

174

[[image:image-20220519174512-2.png||height="323" width="720"]]

175

176

[[image:image-20220519174512-3.png||height="556" width="724"]]

177

178

[[image:image-20220519174512-4.png]]

179

180

You can also choose to create the device manually.

181

182

[[image:1652953542269-423.png||height="710" width="723"]]

183

184

Add APP KEY and DEV EUI

185

186

[[image:1652953553383-907.png||height="514" width="724"]]

(((

**Step 2**: Power on RS485-LN 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.

191

)))

192

193

[[image:1652953568895-172.png||height="232" width="724"]]

194

195

== 3.3 Configure Commands to read data ==

(((

(((

There are plenty of RS485 devices in the market and each device has different command to read the valid data. To support these devices in flexible, RS485-LN supports flexible command set. User can use [[AT Commands>>path:#AT_COMMAND]] or LoRaWAN Downlink Command to configure what commands RS485-LN should send for each sampling and how to handle the return from RS485 devices.

)))

(((

(% 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 onfigure UART settings for RS485 or TTL communication ===

208

209

To use RS485-LN to read data from RS485 sensors, connect the RS485-LN A/B traces to the sensors. And user need to make sure RS485-LN use the match UART setting to access the sensors. The related commands for UART settings are:

210

211

(% border="1" style="background-color:#ffffcc; color:green; width:795px" %)

212

|(((

213

**AT Commands**

214

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

215

**Description**

216

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

**Example**

)))

|(((

AT+BAUDR

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

222

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

223

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

(((

AT+BAUDR=9600

)))

(((

Options: (1200,2400,4800,14400,19200,115200)

)))

)))

|(((

AT+PARITY

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

235

Set UART parity (for RS485 connection)

236

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

(((

AT+PARITY=0

)))

(((

Option: 0: no parity, 1: odd parity, 2: even parity

)))

)))

|(((

AT+STOPBIT

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

248

(((

249

Set serial stopbit (for RS485 connection)

)))

(((

)))

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

256

(((

257

AT+STOPBIT=0 for 1bit

)))

(((

AT+STOPBIT=1 for 1.5 bit

)))

(((

AT+STOPBIT=2 for 2 bits

)))

)))

=== 3.3.2 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.

)))

)))

(% border="1" style="background-color:#ffffcc; color:green; width:806px" %)

278

|**AT Commands**|(% style="width:418px" %)**Description**|(% style="width:256px" %)**Example**

279

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

280

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

281

282

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

283

284

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

285

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

286

287

=== 3.3.3 Configure read commands for each sampling ===

288

289

(((

290

RS485-BL is a battery powered device; it will sleep most of time. And wake up on each period and read RS485 / TTL sensor data and uplink.

)))

(((

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

)))

(((

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

)))

(((

This section describes how to achieve above goals.

)))

(((

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

)))

(((

**Command from RS485-BL to Sensor:**

)))

(((

RS485-BL can send out pre-set max 15 strings via **AT+COMMAD1**, **ATCOMMAND2**,…, to **AT+COMMANDF** . All commands are of same grammar.

)))

(((

**Handle return from sensors to RS485-BL**:

)))

(((

After RS485-BL send out a string to sensor, RS485-BL will wait for the return from RS485 or TTL sensor. And user can specify how to handle the return, by **AT+DATACUT or AT+SEARCH commands**

)))

* (((

**AT+DATACUT**

)))

(((

When the return value from sensor have fix length and we know which position the valid value we should get, we can use AT+DATACUT command.

)))

* (((

**AT+SEARCH**

)))

(((

When the return value from sensor is dynamic length and we are not sure which bytes the valid data is, instead, we know what value the valid value following. We can use AT+SEARCH to search the valid value in the return string.

)))

(((

**Define wait timeout:**

)))

(((

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

)))

(((

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

)))

**Examples:**

Below are examples for the how above AT Commands works.

356

357

**AT+COMMANDx : **This command will be sent to RS485/TTL devices during each sampling, Max command length is 14 bytes. The grammar is:

358

359

(% border="1" class="table-bordered" %)

360

|(((

361

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

362

363

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

364

365

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

)))

(((

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.

)))

(((

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

)))

(((

**AT+SEARCHx**: This command defines how to handle the return from AT+COMMANDx.

378

)))

379

380

(% border="1" class="table-bordered" %)

381

|(((

382

**AT+SEARCHx=aa,xx xx xx xx xx**

383

384

* **aa: 1: prefix match mode; 2: prefix and suffix match mode**

385

* **xx xx xx xx xx: match string. Max 5 bytes for prefix and 5 bytes for suffix**

)))

**Examples:**

~1. For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49

393

394

If we set AT+SEARCH1=1,1E 56 34. (max 5 bytes for prefix)

395

396

The valid data will be all bytes after 1E 56 34 , so it is (% style="background-color:yellow" %)** 2e 30 58 5f 36 41 30 31 00 49**

397

398

[[image:1653269403619-508.png]]

399

400

2. For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49

401

402

If we set AT+SEARCH1=2, 1E 56 34+31 00 49

403

404

Device will search the bytes between 1E 56 34 and 31 00 49. So it is (% style="background-color:yellow" %)** 2e 30 58 5f 36 41 30**

405

406

[[image:1653269438444-278.png]]

407

408

**AT+DATACUTx : **This command defines how to handle the return from AT+COMMANDx, max return length is 45 bytes.

409

410

|(((

411

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

412

413

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

414

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

415

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

)))

Examples:

* Grab bytes:

[[image:1653269551753-223.png||height="311" width="717"]]

* Grab a section.

[[image:1653269568276-930.png||height="325" width="718"]]

427

428

* Grab different sections.

429

430

[[image:1653269593172-426.png||height="303" width="725"]]

431

432

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

433

434

AT+SEARCHx and AT+DATACUTx can be used together, if both commands are set, RS485-BL will first process AT+SEARCHx on the return string and get a temporary string, and then process AT+DATACUTx on this temporary string to get the final payload. In this case, AT+DATACUTx need to set to format AT+DATACUTx=0,xx,xx where the return bytes set to 0.

Example:

(% style="color:red" %)AT+COMMAND1=11 01 1E D0,0

439

440

(% style="color:red" %)AT+SEARCH1=1,1E 56 34

441

442

(% style="color:red" %)AT+DATACUT1=0,2,1~~5

443

444

(% style="color:red" %)Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49

445

446

(% style="color:red" %)String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49

447

448

(% style="color:red" %)Valid payload after DataCUT command: 2e 30 58 5f 36

449

450

[[image:1653269618463-608.png]]

451

452

=== 3.3.4 Compose the uplink payload ===

453

454

(((

455

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:#4f81bd" %)**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.

476

)))

477

478

[[image:1653269759169-150.png]]

**Examples: AT+DATAUP=1**

483

484

Compose the uplink payload with value returns in sequence and send with **Multiply UPLINKs**.

Final Payload is

Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA

489

490

1. Battery Info (2 bytes): Battery voltage

491

1. PAYVER (1 byte): Defined by AT+PAYVER

492

1. PAYLOAD COUNT (1 byte): Total how many uplinks of this sampling.

493

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

494

1. DATA: Valid value: max 6 bytes(US915 version here, [[Notice*!>>path:#max_byte]]) for each uplink so each uplink <= 11 bytes. For the last uplink, DATA will might less than 6 bytes

495

496

[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image020.png]]

497

498

499

So totally there will be 3 uplinks for this sampling, each uplink includes 6 bytes DATA

500

501

DATA1=RETURN1 Valid Value = 20 20 0a 33 90 41

502

503

DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10= 02 aa 05 81 0a 20

504

505

DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 = 20 20 20 2d 30

Below are the uplink payloads:

510

511

[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image021.png]]

512

513

514

Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:

515

516

~* For AU915/AS923 bands, if UplinkDwell time=0, max 51 bytes for each uplink ( so 51 -5 = 46 max valid date)

517

518

* For AU915/AS923 bands, if UplinkDwell time=1, max 11 bytes for each uplink ( so 11 -5 = 6 max valid date).

519

520

* For US915 band, max 11 bytes for each uplink ( so 11 -5 = 6 max valid date).

521

522

~* For all other bands: max 51 bytes for each uplink ( so 51 -5 = 46 max valid date).

1.

11.

111. Uplink on demand

529

530

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

531

532

Downlink control command:

533

534

[[0x08 command>>path:#downlink_08]]: Poll an uplink with current command set in RS485-BL.

535

536

[[0xA8 command>>path:#downlink_A8]]: Send a command to RS485-BL and uplink the output from sensors.

1.

11.

111. Uplink on Interrupt

543

544

Put the interrupt sensor between 3.3v_out and GPIO ext.[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image022.png]]

545

546

AT+INTMOD=0 Disable Interrupt

547

548

AT+INTMOD=1 Interrupt trigger by rising or falling edge.

549

550

AT+INTMOD=2 Interrupt trigger by falling edge. ( Default Value)

551

552

AT+INTMOD=3 Interrupt trigger by rising edge.

1.

11. Uplink Payload

|**Size(bytes)**|**2**|**1**|**Length depends on the return from the commands**

|Value|(((

Battery(mV)

&

Interrupt _Flag

)))|(((

PAYLOAD_VER

)))|If the valid payload is too long and exceed the maximum support payload length in server, server will show payload not provided in the LoRaWAN server.

570

571

Below is the decoder for the first 3 bytes. The rest bytes are dynamic depends on different RS485 sensors.

572

573

574

function Decoder(bytes, port) {

575

576

~/~/Payload Formats of RS485-BL Deceive

return {

~/~/Battery,units:V

BatV:((bytes[0]<<8 | bytes[1])&0x7fff)/1000,

~/~/GPIO_EXTI

EXTI_Trigger:(bytes[0] & 0x80)? "TRUE":"FALSE",

587

588

~/~/payload of version

Pay_ver:bytes[2],

};

}

TTN V3 uplink screen shot.

603

604

[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png]]

605

606

1.

607

11. Configure RS485-BL via AT or Downlink

608

609

User can configure RS485-BL via [[AT Commands >>path:#_Using_the_AT]]or LoRaWAN Downlink Commands

610

611

There are two kinds of Commands:

612

613

* **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: http:~/~/wiki.dragino.com/index.php?title=End_Device_AT_Commands_and_Downlink_Commands

614

615

* **Sensor Related Commands**: These commands are special designed for RS485-BL. User can see these commands below:

1.

11.

111. Common Commands:

620

621

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: [[http:~~/~~/wiki.dragino.com/index.php?title=End_Device_AT_Commands_and_Downlink_Commands>>url:http://wiki.dragino.com/index.php?title=End_Device_AT_Commands_and_Downlink_Commands]]

1.

11.

111. Sensor related commands:

627

628

==== Choose Device Type (RS485 or TTL) ====

629

630

RS485-BL can connect to either RS485 sensors or TTL sensor. User need to specify what type of sensor need to connect.

* AT Command

**AT+MOD=1** ~/~/ Set to support RS485-MODBUS type sensors. User can connect multiply RS485 , Modbus sensors to the A / B pins.

635

636

**AT+MOD=2** ~/~/ Set to support TTL Level sensors, User can connect one TTL Sensor to the TXD/RXD/GND pins.

* Downlink Payload

**0A aa** à same as AT+MOD=aa

==== [[RS485 Debug Command>>path:#downlink_A8]] (AT+CFGDEV) ====

646

647

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

* AT Command

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

652

653

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

* Downlink Payload

Format: A8 MM NN XX XX XX XX YY

Where:

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

664

* NN: The length of RS485 command

665

* XX XX XX XX: RS485 command total NN bytes

666

* YY: How many bytes will be uplink from the return of this RS485 command, if YY=0, RS485-BL will execute the downlink command without uplink; if YY>0, RS485-BL will uplink total YY bytes from the output of this RS485 command

**Example 1:**

To connect a Modbus Alarm with below commands.

671

672

* 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.

673

674

* 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.

675

676

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

677

678

**A8 01 06 0A 05 00 04 00 01 00**: to activate the RS485 Alarm

679

680

**A8 01 06 0A 05 00 04 00 00 00**: to deactivate the RS485 Alarm

681

682

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.

**Example 2:**

Check TTL Sensor return:

688

689

[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image024.png]]

==== Set Payload version ====

695

696

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

* AT Command:

AT+PAYVER: Set PAYVER field = 1

* Downlink Payload:

0xAE 01 à Set PAYVER field = 0x01

706

707

0xAE 0F à Set PAYVER field = 0x0F

708

709

710

==== Set RS485 Sampling Commands ====

711

712

AT+COMMANDx, AT+DATACUTx and AT+SEARCHx

713

714

These three commands are used to configure how the RS485-BL polling data from Modbus device. Detail of usage please see : [[polling RS485 device>>path:#polling_485]].

* AT Command:

AT+COMMANDx: Configure RS485 read command to sensor.

720

721

AT+DATACUTx: Configure how to handle return from RS485 devices.

722

723

AT+SEARCHx: Configure search command

* Downlink Payload:

0xAF downlink command can be used to set AT+COMMANDx or AT+DATACUTx.

729

730

Note: if user use AT+COMMANDx to add a new command, he also need to send AT+DATACUTx downlink.

731

732

Format: AF MM NN LL XX XX XX XX YY

Where:

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

737

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

738

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

739

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

740

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

Example:

**AF 03 01 06 0A 05 00 04 00 01 00**: Same as AT+COMMAND3=0A 05 00 04 00 01,1

745

746

**AF 03 02 06 10 01 05 06 09 0A 00**: Same as AT+DATACUT3=**16**,**1**,**5+6+9+10**

747

748

**AF 03 02 06 0B 02 05 07 08 0A 00**: Same as AT+DATACUT3=**11**,**2**,**5~~7+8~~10**

749

750

751

0xAB downlink command can be used for set AT+SEARCHx

752

753

Example: **AB aa 01 03 xx xx xx** (03 here means there are total 3 bytes after 03) So

754

755

* AB aa 01 03 xx xx xx same as AT+SEARCHaa=1,xx xx xx

756

* AB aa 02 03 xx xx xx 02 yy yy(03 means there are 3 bytes after 03, they are xx xx xx;02 means there are 2 bytes after 02, they are yy yy) so the commands

757

758

**AB aa 02 03 xx xx xx 02 yy yy** same as **AT+SEARCHaa=2,xx xx xx+yy yy**

759

760

761

==== Fast command to handle MODBUS device ====

762

763

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]].

764

765

This command is valid since v1.3 firmware version

766

767

768

AT+MBFUN has only two value:

769

770

* AT+MBFUN=1: Enable Modbus reading. And get response base on the MODBUS return

771

772

AT+MBFUN=1, device 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.

773

774

* AT+MBFUN=0: Disable Modbus fast reading.

Example:

* AT+MBFUN=1 and AT+DATACUT1/AT+DATACUT2 are not configure (0,0,0).

779

* 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.

780

* 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.

781

782

[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image025.png]]

783

784

785

[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image026.png]]

* Downlink Commands:

A9 aa -à Same as AT+MBFUN=aa

791

792

793

==== RS485 command timeout ====

794

795

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

796

797

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

* AT Command:

AT+CMDDLaa=hex(bb cc)

Example:

**AT+CMDDL1=1000** to send the open time to 1000ms

* Downlink Payload:

0x AA aa bb cc

Same as: AT+CMDDLaa=hex(bb cc)

Example:

0xAA 01 03 E8 à Same as **AT+CMDDL1=1000 ms**

818

819

820

==== [[Uplink>>path:#downlink_A8]] payload mode ====

821

822

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

823

824

The use of this command please see: [[Compose Uplink payload>>path:#DataUP]]

* AT Command:

AT+DATAUP=0

AT+DATAUP=1

* Downlink Payload:

0xAD 00 à Same as AT+DATAUP=0

836

837

0xAD 01 à Same as AT+DATAUP=1

838

839

840

==== Manually trigger an Uplink ====

841

842

Ask device to send an uplink immediately.

* Downlink Payload:

0x08 FF, RS485-BL will immediately send an uplink.

847

848

849

==== Clear RS485 Command ====

850

851

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

* AT Command:

**AT+CMDEAR=mm,nn** mm: start position of erase ,nn: stop position of erase

857

858

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

859

860

Example screen shot after clear all RS485 commands.

The uplink screen shot is:

865

866

[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png]]

* Downlink Payload:

0x09 aa bb same as AT+CMDEAR=aa,bb

872

873

874

==== Set Serial Communication Parameters ====

875

876

Set the Rs485 serial communication parameters:

* AT Command:

Set Baud Rate:

AT+BAUDR=9600 ~/~/ Options: (1200,2400,4800,14400,19200,115200)

Set UART parity

AT+PARITY=0 ~/~/ Option: 0: no parity, 1: odd parity, 2: even parity

Set STOPBIT

AT+STOPBIT=0 ~/~/ Option: 0 for 1bit; 1 for 1.5 bit ; 2 for 2 bits

* Downlink Payload:

A7 01 aa bb: Same AT+BAUDR=hex(aa bb)*100

Example:

* A7 01 00 60 same as AT+BAUDR=9600

902

* A7 01 04 80 same as AT+BAUDR=115200

903

904

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

905

906

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

907

908

909

==== Control output power duration ====

910

911

User can set the output power duration before each sampling.

* AT Command:

Example:

AT+3V3T=1000 ~/~/ 3V3 output power will open 1s before each sampling.

918

919

AT+5VT=1000 ~/~/ +5V output power will open 1s before each sampling.

920

921

922

* LoRaWAN Downlink Command:

923

924

07 01 aa bb Same as AT+5VT=(aa bb)

925

926

07 02 aa bb Same as AT+3V3T=(aa bb)

1.

11. Buttons

|**Button**|**Feature**

935

|**RST**|Reboot RS485-BL

1.

11. +3V3 Output

RS485-BL has a Controllable +3V3 output, user can use this output to power external sensor.

941

942

The +3V3 output will be valid for every sampling. RS485-BL will enable +3V3 output before all sampling and disable the +3V3 after all sampling.

943

944

945

The +3V3 output time can be controlled by AT Command.

**AT+3V3T=1000**

Means set +3v3 valid time to have 1000ms. So, the real +3v3 output will actually have 1000ms + sampling time for other sensors.

950

951

952

By default, the AT+3V3T=0. This is a special case, means the +3V3 output is always on at any time

1.

11. +5V Output

RS485-BL has a Controllable +5V output, user can use this output to power external sensor.

959

960

The +5V output will be valid for every sampling. RS485-BL will enable +5V output before all sampling and disable the +5v after all sampling.

961

962

963

The 5V output time can be controlled by AT Command.

**AT+5VT=1000**

Means set 5V valid time to have 1000ms. So, the real 5V output will actually have 1000ms + sampling time for other sensors.

968

969

970

By default, the AT+5VT=0. If the external sensor which require 5v and require more time to get stable state, user can use this command to increase the power ON duration for this sensor.

1.

11. LEDs

|**LEDs**|**Feature**

979

|**LED1**|Blink when device transmit a packet.

1.

11. Switch Jumper

|**Switch Jumper**|**Feature**

985

|**SW1**|(((

986

ISP position: Upgrade firmware via UART

987

988

Flash position: Configure device, check running status.

989

)))

990

|**SW2**|(((

991

5V position: set to compatible with 5v I/O.

992

993

3.3v position: set to compatible with 3.3v I/O.,

)))

+3.3V: is always ON

+5V: Only open before every sampling. The time is by default, it is AT+5VT=0. Max open time. 5000 ms.

1. Case Study

User can check this URL for some case studies.

1003

1004

[[http:~~/~~/wiki.dragino.com/index.php?title=APP_RS485_COMMUNICATE_WITH_SENSORS>>url:http://wiki.dragino.com/index.php?title=APP_RS485_COMMUNICATE_WITH_SENSORS]]

1. Use AT Command

11. Access AT Command

1011

1012

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

1013

1014

[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image027.png]]

1015

1016

1017

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

1018

1019

[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image028.png]]

More detail AT Command manual can be found at [[AT Command Manual>>path:#AT_COMMAND]]

1.

11. Common AT Command Sequence

1029

111. Multi-channel ABP mode (Use with SX1301/LG308)

1030

1031

If device has not joined network yet:

AT+FDR

AT+NJM=0

ATZ

If device already joined network:

AT+NJM=0

ATZ

1.

11.

111. Single-channel ABP mode (Use with LG01/LG02)

1049

1050

AT+FDR Reset Parameters to Factory Default, Keys Reserve

1051

1052

AT+NJM=0 Set to ABP mode

1053

1054

AT+ADR=0 Set the Adaptive Data Rate Off

1055

1056

AT+DR=5 Set Data Rate

1057

1058

AT+TDC=60000 Set transmit interval to 60 seconds

1059

1060

AT+CHS=868400000 Set transmit frequency to 868.4Mhz

1061

1062

AT+RX2FQ=868400000 Set RX2Frequency to 868.4Mhz (according to the result from server)

1063

1064

AT+RX2DR=5 Set RX2DR to match the downlink DR from server. see below

1065

1066

AT+DADDR=26 01 1A F1 Set Device Address to 26 01 1A F1, this ID can be found in the LoRa Server portal.

ATZ Reset MCU

**Note:**

1. Make sure the device is set to ABP mode in the IoT Server.

1073

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

1074

1. 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.

1075

1. 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

1076

1077

[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image029.png]]

1. FAQ

11. How to upgrade the image?

1082

1083

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

1084

1085

* Support new features

1086

* For bug fix

1087

* Change LoRaWAN bands.

1088

1089

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

1090

1091

[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image030.png]]

1092

1093

**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]].

1094

1095

**Step2**: Download the [[LT Image files>>url:http://www.dragino.com/downloads/index.php?dir=LT_LoRa_IO_Controller/LT33222-L/image/]].

1096

1097

**Step3: **Open flashloader; choose the correct COM port to update.

|(((

HOLD PRO then press the RST button, SYS will be ON, then click next

)))

|(((

Board detected

)))

|(((

)))

[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image031.png]] [[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image032.png]]

[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image033.png]] [[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image034.png]]

1117

1118

1119

[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image035.png]] [[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image036.png]]

1.

11. How to change the LoRa Frequency Bands/Region?

1124

1125

User can follow the introduction for [[how to upgrade image>>path:#upgrade_image]]. When download the images, choose the required image file for download.

1.

11. How many RS485-Slave can RS485-BL connects?

1131

1132

The RS485-BL can support max 32 RS485 devices. Each uplink command of RS485-BL can support max 16 different RS485 command. So RS485-BL can support max 16 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>>path:#downlink_A8]].

1. Trouble Shooting

11. Downlink doesn’t work, how to solve it?

1139

1140

Please see this link for debug:

1141

1142

[[http:~~/~~/wiki.dragino.com/index.php?title=Main_Page#LoRaWAN_Communication_Debug>>url:http://wiki.dragino.com/index.php?title=Main_Page#LoRaWAN_Communication_Debug]]

1.

11. Why I can’t join TTN V3 in US915 /AU915 bands?

1148

1149

It might about the channels mapping. Please see for detail.

1150

1151

[[http:~~/~~/wiki.dragino.com/index.php?title=LoRaWAN_Communication_Debug#Notice_of_US915.2FCN470.2FAU915_Frequency_band>>url:http://wiki.dragino.com/index.php?title=LoRaWAN_Communication_Debug#Notice_of_US915.2FCN470.2FAU915_Frequency_band]]

1. Order Info

**Part Number: RS485-BL-XXX**

**XXX:**

* **EU433**: frequency bands EU433

1162

* **EU868**: frequency bands EU868

1163

* **KR920**: frequency bands KR920

1164

* **CN470**: frequency bands CN470

1165

* **AS923**: frequency bands AS923

1166

* **AU915**: frequency bands AU915

1167

* **US915**: frequency bands US915

1168

* **IN865**: frequency bands IN865

1169

* **RU864**: frequency bands RU864

1170

* **KZ865: **frequency bands KZ865

1. Packing Info

**Package Includes**:

1175

1176

* RS485-BL x 1

1177

* Stick Antenna for LoRa RF part x 1

1178

* Program cable x 1

1179

1180

**Dimension and weight**:

1181

1182

* Device Size: 13.5 x 7 x 3 cm

1183

* Device Weight: 105g

1184

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

1185

* Weight / pcs : 170g

1. 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.

1190

* 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

1191

1192

[[support@dragino.com>>url:file:///D:/市场资料/说明书/LoRa/LT系列/support@dragino.com]]

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

Applications

Navigation