RS485-BL – Waterproof RS485 to LoRaWAN Converter

The Dragino RS485-BL is a **RS485 / UART to LoRaWAN Converter** for Internet of Things solutions. User can connect RS485 or UART sensor to RS485-BL converter, and configure RS485-BL to periodically read sensor data and upload via LoRaWAN network to IoT server.

22

23

24

RS485-BL can interface to RS485 sensor, 3.3v/5v UART sensor or interrupt sensor. RS485-BL provides **a 3.3v output** and** a 5v output** to power external sensors. Both output voltages are controllable to minimize the total system power consumption.

25

26

27

RS485-BL is IP67 **waterproof** and powered by **8500mAh Li-SOCI2 battery**, it is designed for long term use for several years.

28

29

30

RS485-BL runs standard **LoRaWAN 1.0.3 in Class A**. It can reach long transfer range and easy to integrate with LoRaWAN compatible gateway and IoT server.

31

32

33

For data uplink, RS485-BL sends user-defined commands to RS485 devices and gets the return from the RS485 devices. RS485-BL will process these returns data according to user-define rules to get the final payload and upload to LoRaWAN server.

34

35

36

For data downlink, RS485-BL runs in LoRaWAN Class A. When there is downlink commands from LoRaWAN server, RS485-BL will forward the commands from LoRaWAN server to RS485 devices.

37

38

39

Each RS485-BL pre-load with a set of unique keys for LoRaWAN registration, register these keys to LoRaWAN server and it will auto connect after power on.

40

41

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

1.

11. Specifications

**Hardware System:**

* STM32L072CZT6 MCU

* SX1276/78 Wireless Chip

51

* Power Consumption (exclude RS485 device):

** Idle: 6uA@3.3v

*

** 20dB Transmit: 130mA@3.3v

56

57

58

**Interface for Model:**

59

60

* 1 x RS485 Interface

61

* 1 x TTL Serial , 3.3v or 5v.

62

* 1 x I2C Interface, 3.3v or 5v.

63

* 1 x one wire interface

64

* 1 x Interrupt Interface

65

* 1 x Controllable 5V output, max

**LoRa Spec:**

* Frequency Range:

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

72

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

73

* 168 dB maximum link budget.

74

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

75

* Programmable bit rate up to 300 kbps.

76

* High sensitivity: down to -148 dBm.

77

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

78

* Excellent blocking immunity.

79

* Fully integrated synthesizer with a resolution of 61 Hz.

80

* LoRa modulation.

81

* Built-in bit synchronizer for clock recovery.

82

* Preamble detection.

83

* 127 dB Dynamic Range RSSI.

84

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

*

*1. Features

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

90

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

91

* AT Commands to change parameters

92

* Remote configure parameters via LoRaWAN Downlink

93

* Firmware upgradable via program port

94

* Support multiply RS485 devices by flexible rules

95

* Support Modbus protocol

96

* Support Interrupt uplink

*

*1. Applications

* Smart Buildings & Home Automation

102

* Logistics and Supply Chain Management

* Smart Metering

* Smart Agriculture

* Smart Cities

* Smart Factory

1.

11. Firmware Change log

111

112

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

1.

11. Hardware Change log

v1.4

~1. Change Power IC to TPS22916

v1.3

~1. Change JP3 from KF350-8P to KF350-11P, Add one extra interface for I2C and one extra interface for one-wire

v1.2

Release version

1. Pin mapping and Power ON Device

138

139

The RS485-BL is powered on by 8500mAh battery. To save battery life, RS485-BL is shipped with power off. User can put the jumper to power on RS485-BL.

140

141

142

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

The Left TXD and RXD are TTL interface for external sensor. TTL level is controlled by 3.3/5v Jumper.

1. Operation Mode

11. How it works?

The RS485-BL is configured as LoRaWAN OTAA Class A 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-BL. It will auto join the network via OTAA.

1.

11. Example to join LoRaWAN network

161

162

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.

163

164

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

165

166

167

The RS485-BL in this example connected to two RS485 devices for demonstration, user can connect to other RS485 devices via the same method.

168

169

170

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

171

172

**Step 1**: Create a device in TTN V3 with the OTAA keys from RS485-BL.

173

174

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

175

176

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

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

182

183

Add APP EUI in the application.

184

185

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

186

187

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

188

189

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

190

191

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

You can also choose to create the device manually.

|(((

)))

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

218

219

Add APP KEY and DEV EUI

220

221

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

222

223

224

**Step 2**: 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.

225

226

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

1.

11. Configure Commands to read data

233

234

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

1.

11.

111. Configure UART settings for RS485 or TTL communication

240

241

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

242

243

1. RS485-MODBUS mode:

244

245

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

1. TTL mode:

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

251

252

253

RS485-BL default UART settings is **9600, no parity, stop bit 1**. If the sensor has a different settings, user can change the RS485-BL setting to match.

254

255

256

|**AT Commands**|**Description**|**Example**

257

|AT+BAUDR|Set the baud rate (for RS485 connection). Default Value is: 9600.|(((

258

AT+BAUDR=9600

259

260

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

261

)))

262

|AT+PARITY|(((

263

Set UART parity (for RS485 connection)

264

265

Default Value is: no parity.

)))|(((

AT+PARITY=0

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

270

)))

271

|AT+STOPBIT|(((

272

Set serial stopbit (for RS485 connection)

273

274

Default Value is: 1bit.

275

)))|(((

276

AT+STOPBIT=0 for 1bit

277

278

AT+STOPBIT=1 for 1.5 bit

279

280

AT+STOPBIT=2 for 2 bits

)))

1.

11.

111. Configure sensors

290

291

Some sensors might need to configure before normal operation. User can configure such sensor via PC or through RS485-BL AT Commands AT+CFGDEV.

292

293

294

When user issue an AT+CFGDEV command, Each AT+CFGDEV equals to send a command to the RS485 or TTL sensors. This command will only run when user input it and won’t run during each sampling.

295

296

|**AT Commands**|**Description**|**Example**

297

|AT+CFGDEV|(((

298

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

299

300

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

301

302

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

303

)))|AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m

304

305

Detail of AT+CFGDEV command see [[AT+CFGDEV detail>>path:#AT_CFGDEV]].

1.

11.

111. Configure read commands for each sampling

314

315

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.

316

317

318

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.

319

320

321

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

322

323

324

This section describes how to achieve above goals.

325

326

327

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

328

329

330

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

331

332

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

333

334

335

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

336

337

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.

348

349

350

**Define wait timeout:**

351

352

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

353

354

355

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.

361

362

363

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

364

365

|(((

366

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

367

368

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

369

370

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

371

)))

372

373

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.

374

375

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

376

377

378

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

379

380

|(((

381

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

382

383

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

384

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

392

393

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

394

395

The valid data will be all bytes after 1E 56 34 , so it is 2e 30 58 5f 36 41 30 31 00 49

396

397

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

398

399

400

1. 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 2e 30 58 5f 36 41 30

405

406

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

407

408

409

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

410

411

|(((

412

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

413

414

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

415

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

416

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

)))

Examples:

* Grab bytes:

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

* Grab a section.

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

428

429

* Grab different sections.

430

431

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

Note:

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:

AT+COMMAND1=11 01 1E D0,0

441

442

AT+SEARCH1=1,1E 56 34

AT+DATACUT1=0,2,1~~5

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

447

448

String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49

449

450

Valid payload after DataCUT command: 2e 30 58 5f 36

451

452

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

1.

11.

111. Compose the uplink payload

460

461

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

462

463

464

**Examples: AT+DATAUP=0**

465

466

Compose the uplink payload with value returns in sequence and send with **A SIGNLE UPLINK**.

Final Payload is

Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx

471

472

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

473

474

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

**Examples: AT+DATAUP=1**

479

480

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

Final Payload is

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

485

486

1. Battery Info (2 bytes): Battery voltage

487

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

488

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

489

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

490

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

491

492

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

493

494

495

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

496

497

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

498

499

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

500

501

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

Below are the uplink payloads:

506

507

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

508

509

510

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

511

512

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

513

514

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

515

516

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

517

518

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

1.

11.

111. Uplink on demand

525

526

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.

527

528

Downlink control command:

529

530

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

531

532

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

1.

11.

111. Uplink on Interrupt

539

540

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

541

542

AT+INTMOD=0 Disable Interrupt

543

544

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

545

546

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

547

548

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.

567

568

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

569

570

571

function Decoder(bytes, port) {

572

573

~/~/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",

584

585

~/~/payload of version

Pay_ver:bytes[2],

};

}

TTN V3 uplink screen shot.

600

601

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

602

603

1.

604

11. Configure RS485-BL via AT or Downlink

605

606

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

607

608

There are two kinds of Commands:

609

610

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

611

612

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

1.

11.

111. Common Commands:

618

619

620

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:

626

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.

672

673

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

674

675

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

676

677

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

678

679

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

680

681

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

682

683

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:

689

690

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

==== Set Payload version ====

696

697

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

707

708

0xAE 0F à Set PAYVER field = 0x0F

709

710

711

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

712

713

AT+COMMANDx, AT+DATACUTx and AT+SEARCHx

714

715

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.

721

722

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

723

724

AT+SEARCHx: Configure search command

* Downlink Payload:

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

730

731

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

732

733

Format: AF MM NN LL XX XX XX XX YY

Where:

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

738

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

739

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

740

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

741

* 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

746

747

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

748

749

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

750

751

752

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

753

754

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

755

756

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

757

* 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

758

759

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

760

761

762

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

763

764

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

765

766

This command is valid since v1.3 firmware version

767

768

769

AT+MBFUN has only two value:

770

771

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

772

773

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.

774

775

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

Example:

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

781

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

782

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

783

784

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

785

786

787

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

* Downlink Commands:

A9 aa -à Same as AT+MBFUN=aa

793

794

795

==== RS485 command timeout ====

796

797

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.

798

799

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

820

821

822

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

823

824

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

825

826

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

838

839

0xAD 01 à Same as AT+DATAUP=1

840

841

842

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

843

844

Ask device to send an uplink immediately.

* Downlink Payload:

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

849

850

851

==== Clear RS485 Command ====

852

853

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

859

860

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

861

862

Example screen shot after clear all RS485 commands.

The uplink screen shot is:

867

868

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

* Downlink Payload:

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

874

875

876

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

877

878

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

904

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

905

906

907

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

908

909

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

910

911

912

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

913

914

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.

921

922

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

923

924

925

* LoRaWAN Downlink Command:

926

927

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

928

929

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

1.

11. Buttons

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

939

|**RST**|Reboot RS485-BL

1.

11. +3V3 Output

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

946

947

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.

948

949

950

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.

955

956

957

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.

964

965

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.

966

967

968

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.

973

974

975

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

984

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

1.

11. Switch Jumper

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

991

|**SW1**|(((

992

ISP position: Upgrade firmware via UART

993

994

Flash position: Configure device, check running status.

995

)))

996

|**SW2**|(((

997

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

998

999

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.

1010

1011

[[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

1018

1019

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.

1020

1021

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

1022

1023

1024

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:

1025

1026

[[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

1036

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

1037

1038

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)

1056

1057

AT+FDR Reset Parameters to Factory Default, Keys Reserve

1058

1059

AT+NJM=0 Set to ABP mode

1060

1061

AT+ADR=0 Set the Adaptive Data Rate Off

1062

1063

AT+DR=5 Set Data Rate

1064

1065

AT+TDC=60000 Set transmit interval to 60 seconds

1066

1067

AT+CHS=868400000 Set transmit frequency to 868.4Mhz

1068

1069

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

1070

1071

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

1072

1073

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.

1080

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

1081

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.

1082

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

1083

1084

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

1. FAQ

11. How to upgrade the image?

1089

1090

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

1091

1092

* Support new features

1093

* For bug fix

1094

* Change LoRaWAN bands.

1095

1096

1097

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

1098

1099

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

1100

1101

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

1102

1103

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

1104

1105

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

1125

1126

1127

[[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?

1132

1133

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?

1139

1140

1141

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?

1148

1149

Please see this link for debug:

1150

1151

[[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?

1157

1158

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

1159

1160

[[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

1172

* **EU868**: frequency bands EU868

1173

* **KR920**: frequency bands KR920

1174

* **CN470**: frequency bands CN470

1175

* **AS923**: frequency bands AS923

1176

* **AU915**: frequency bands AU915

1177

* **US915**: frequency bands US915

1178

* **IN865**: frequency bands IN865

1179

* **RU864**: frequency bands RU864

1180

* **KZ865: **frequency bands KZ865

1. Packing Info

**Package Includes**:

1186

1187

* RS485-BL x 1

1188

* Stick Antenna for LoRa RF part x 1

* Program cable x 1

**Dimension and weight**:

1193

1194

* Device Size: 13.5 x 7 x 3 cm

1195

* Device Weight: 105g

1196

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

1197

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

1203

* 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

1204

1205

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

Wiki source code of RS485-BL – Waterproof RS485 to LoRaWAN Converter

Applications

Navigation