Table of Contents:

• 1. Introduction
  • 1.1 What is RS485-BL RS485 to LoRaWAN Converter
  • 1.2 Specifications
  • 1.3 Features
  • 1.4 Applications
  • 1.5 Firmware Change log
  • 1.6 Hardware Change log
• 2. Pin mapping and Power ON Device
• 3. Operation Mode
  • 3.1 How it works?
  • 3.2 Example to join LoRaWAN network
  • 3.3 Configure Device to Read RS485 Sensor
    • 3.3.1 Method 1 -- via RS485 Configure Tool
    • 3.3.2 Method 2 -- via AT Commands
      • 3.3.2.1 Configure UART settings for RS485 or TTL communication(Since v1.3.3)
    • 3.3.3  Configure sensors
    • 3.3.4 Configure read commands for each sampling
    • 3.3.4 Compose the uplink payload
    • 3.3.5 Uplink on demand
    • 3.3.6 Uplink on Interrupt
  • 3.4 Uplink Payload
  • 3.5 Configure RS485-BL via AT or Downlink
    • 3.5.1 Common Commands:
    • 3.5.2 Sensor related commands:
      • Choose Device Type (RS485 or TTL) (Since v1.3.3)
      • RS485 Debug Command (AT+CFGDEV)
      • Set Payload version
      • Set RS485 Sampling Commands
      • Fast command to handle MODBUS device
      • RS485 command timeout
      • Uplink payload mode
      • Cut data separation processing(Since Version 1.4.2)
      • Manually trigger an Uplink
      • Clear RS485 Command
      • Set Serial Communication Parameters
      • Configure Databit(Since version 1.4.0)
      • Encrypted payload
      • Get sensor value
      • Resets the downlink packet count
      • When the limit bytes are exceeded, upload in batches
      • Copy downlink to uplink 
      • Query version number and frequency band 、TDC
      • Control output power duration
  • 3.6 Connect to external temperature sensor & counting sensor
  • 3.7 Buttons
  • 3.8 +3V3 Output (Since v1.3.3)
  • 3.9 +5V Output (Since v1.3.3)
  • 3.10 LEDs
  • 3.11 Switch Jumper
  • 3.12 Battery & Power Consumption
• 4. Case Study
• 5. Use AT Command
  • 5.1 Access AT Command
  • 5.2 Common AT Command Sequence
    • 5.2.1 Multi-channel ABP mode (Use with SX1301/LG308)
    • 5.5.2 Single-channel ABP mode (Use with LG01/LG02)
• 6. FAQ
  • 6.1 How to upgrade the image?
  • 6.2 How to change the LoRa Frequency Bands/Region?
  • 6.3 How many RS485-Slave can RS485-BL connects?
  • 6.4 How to Use RS485-BL  to connect to RS232 devices?
  • 6.5 How to judge whether there is a problem with the set COMMAND
    • 6.5.1 Introduce:
    • 6.5.2 Set up PC to monitor RS485 network With Serial tool
    • 6.5.3 With ModRSsim2:
    • 6.5.4 Example – Test the CFGDEV command
    • 6.5.5 Example – Test CMD command sets.
    • 6.5.6 Test with PC
  • 6.6 Where to get the decoder for RS485-BL?
  • 6.7 Why does my TTL sensor have returned data, but after using the command AT+DATACUT, the data in the payload is 0?
  • 6.8 Where can I get a decoder?
  • 6.9 How to configure RS485 commands more conveniently？
• 7. Trouble Shooting
  • 7.1 Downlink doesn't work, how to solve it?
  • 7.2 Why I can't join TTN V3 in US915 /AU915 bands?
  • 7.3 Possible reasons why the device is unresponsive：
• test
• 8. Order Info
• 9. Packing Info
• 10. Support

1. Introduction

1.1 What is RS485-BL RS485 to LoRaWAN Converter

1.2 Specifications

Operate Temperature:

• -40°C ~ 65°C

Hardware System:

• STM32L072xxxx MCU
• SX1276/78 Wireless Chip  
• Power Consumption (exclude RS485 device):
  • Idle: 6uA@3.3v
  • 20dB Transmit: 130mA@3.3v
• 5V sampling maximum current：500mA

Interface for Model:

• 1 x RS485 Interface
• 1 x TTL Serial , 3.3v or 5v.
• 1 x I2C Interface, 3.3v or 5v.
• 1 x one wire interface
• 1 x Interrupt Interface
• 1 x Controllable 5V output, max

LoRa Spec:

• Frequency Range:
  • Band 1 (HF): 862 ~ 1020 Mhz
  • Band 2 (LF): 410 ~ 528 Mhz
• 168 dB maximum link budget.
• +20 dBm - 100 mW constant RF output vs.
• Programmable bit rate up to 300 kbps.
• High sensitivity: down to -148 dBm.
• Bullet-proof front end: IIP3 = -12.5 dBm.
• Excellent blocking immunity.
• Fully integrated synthesizer with a resolution of 61 Hz.
• LoRa modulation.
• Built-in bit synchronizer for clock recovery.
• Preamble detection.
• 127 dB Dynamic Range RSSI.
• Automatic RF Sense and CAD with ultra-fast AFC.

​​​

1.3 Features

• LoRaWAN Class A & Class C protocol (default Class A)
• Frequency Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915/IN865/RU864/MA869
• AT Commands to change parameters
• Remote configure parameters via LoRaWAN Downlink
• Firmware upgradable via program port
• Support multiply RS485 devices by flexible rules
• Support Modbus protocol
• Support Interrupt uplink

1.4 Applications

• Smart Buildings & Home Automation
• Logistics and Supply Chain Management
• Smart Metering
• Smart Agriculture
• Smart Cities
• Smart Factory

1.5 Firmware Change log

RS485-BL Image files – Download link and Change log

1.6 Hardware Change log

2. Pin mapping and Power ON Device

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

3. Operation Mode

3.1 How it works?

3.2 Example to join LoRaWAN network

Here shows an example for how to join the TTN V3 Network. Below is the network structure, we use LG308 as LoRaWAN gateway here.  

You can also choose to create the device manually.

Add APP KEY and DEV EUI

3.3 Configure Device to Read RS485 Sensor

3.3.2 Method 2 -- via AT Commands

3.3.2.1 Configure UART settings for RS485 or TTL communication(Since v1.3.3)

Example(Soil three-parameter detector):

Wiring the UART sensor

Set the correct configuration:

AT+BAUDR=9600

AT+PARITY=0

AT+STOPBIT=1

If the sensor needs 5v. Need to move the switch position to 5v and then use the command

AT+5VT=30000

Configuration read command:

AT+CFGDEV=FE 03 00 00 00 03 11 C4,0

FE: Station address

03: Function code

00 00: Register start address

00 03: Number of registers

11 04:  Check code

 Use AT+COMMAND1 to set it as a command, and use AT+DATACUT1 to intercept the bytes I need

upload payload:

3.3.3  Configure sensors

Detail of AT+CFGDEV command see AT+CFGDEV detail.

3.3.4 Configure read commands for each sampling

• AT+DATACUT

• AT+SEARCH

• Grab bytes:

• Grab a section.

• Grab different sections.

3.3.4 Compose the uplink payload

1. Battery Info (2 bytes): Battery voltage

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

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

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

5. DATA: Valid value: max 6 bytes(US915 version here, Notice*!) for each uplink so each uplink <= 11 bytes. For the last uplink, DATA will might less than 6 bytes

    

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

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

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

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

Below are the uplink payloads:

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

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

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

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

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

   * When AT+DATAUP=1, the maximum number of segments is 15, and the maximum total number of bytes is 1500;

      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)

• If the data is empty, return to the display（Since v1.4.0）

1)  When AT+MOD=1, 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.

2)  When AT+MOD=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 00s.

3.3.5 Uplink on demand

3.3.6 Uplink on Interrupt

Put the interrupt sensor between 3.3v_out and GPIO ext.

3.4 Uplink Payload

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

function Decoder(bytes, port) {

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

    //payload of version

    Pay_ver:bytes[2],

    }; 

3.5 Configure RS485-BL via AT or Downlink

• 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

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

   

3.5.1 Common Commands:

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

3.5.2 Sensor related commands:

Choose Device Type (RS485 or TTL) (Since v1.3.3)

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.

 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 (AT+CFGDEV)

• Downlink Payload

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

• NN: The length of RS485 command

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

   

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

Set Payload version

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

 0xAE 0F   --> Set PAYVER field =  0x0F

Set RS485 Sampling Commands

• AT Command:

 AT+COMMANDx:    Configure RS485 read command to sensor.

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

 AT+SEARCHx:         Configure search command

• Downlink Payload:

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

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

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

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

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

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

• 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

Fast command to handle MODBUS device

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

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

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

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

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

• Downlink Commands:

RS485 command timeout

• Downlink Payload:

Uplink payload mode

• Downlink Payload:

• Downlink Payload:

Cut data separation processing(Since Version 1.4.2)

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

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

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

•  AT Command:

AT+NEWLINE=ALL   The data cut out by each AT+COMMANDx command is sent separately as an uplink.

AT+NEWLINE=ALL   equal：  AT+NEWLINE=1+2+3+4+5+6+7+8+9+10+11+12+13+14+15

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.

AT+NEWLINE=NULL  Turn off the functionality of this AT command.

•  Downlink Payload:

AT+NEWLINE=ALL         --->      0xAC 01

 AT+NEWLINE= NULL    --->      0xAC 00

AT+NEWLINE= a+b+c   --->      0xAC  number of bytes  a  b  c

AT+NEWLINE= 1+5+15 --->     0xAC 03 01 05 0F

Manually trigger an Uplink

Ask device to send an uplink immediately.

• Downlink Payload:

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

Clear RS485 Command

• AT Command:

• Downlink Payload:

Set Serial Communication Parameters

• AT Command:

 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 300ms), otherwise data will be lost

• 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 00 60   same as AT+BAUDR=9600

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

Configure Databit(Since version 1.4.0)

• AT Command:

 AT+DATABIT=7  // Set the data bits to 7

 AT+DATABIT=8  //Set the data bits to 8

• Downlink Payload:

 A7 04 07: Same as  AT+DATABIT=7

 A7 04 08: Same as  AT+DATABIT=8

Encrypted payload

• AT Command:

 AT+DECRYPT=1    // The payload is uploaded without encryption

 AT+DECRYPT=0   //  Encrypt when uploading payload (default)

Get sensor value

• AT Command:

 AT+GETSENSORVALUE=0    // The serial port gets the reading of the current sensor

 AT+GETSENSORVALUE=1    // The serial port gets the current sensor reading and uploads it.

Resets the downlink packet count

• AT Command:

 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)

 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.

When the limit bytes are exceeded, upload in batches

• AT Command:

        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)

        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.

• Downlink Payload

 0x21 00 01          // Set  the DISMACANS=1

Copy downlink to uplink 

• AT Command:

        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.

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.

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

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

Query version number and frequency band 、TDC

• Downlink Payload: 26 01    // Downlink 26 01 can query device upload frequency, frequency band, software version number, TDC time.

Example：

Control output power duration

Before v1.4.4, the maximum settable time of 3V3T and 5VT is 65535 milliseconds. After v1.4.4, the maximum settable time of 3V3T and 5VT is 180 seconds.

• AT Command:

• LoRaWAN Downlink Command:

  Example:

  When the delay is less than 65 seconds, Downlink can be controlled by 4 bytes or 5 bytes:

3.6 Connect to external temperature sensor & counting sensor

Note: This feature is only available for new unreleased firmware v1.4.5, please contact us for testing.

• AT Command:

AT+EXT=a,b,c 

a:    0: ignore I2C interface.                                                           1: Add SHT31 sensor support (4 bytes).
b:    0: ignore pulse interface ( doesn't effect interrupt ).             1: Add Counting Support (4 bytes).
c:    0: ignore one wire interface.                                                  1: add DS18B20 support (2 bytes).

Example:

AT+EXT=1,1,1

Device will add SHT31, counting, DS18B20 support.

The payload will be:
Battery(mV) & Interrupt _Flag + PAYLOAD_VER + *SHT31 temp + *SHT31 Hum + *counting + *DS18B20 + Length depends on the return from the commands

AT+EXT=0,1,0

Device will add counting support.

The payload will be:
Battery(mV) & Interrupt _Flag + PAYLOAD_VER + *counting + Length depends on the return from the commands

• AT Command:

AT+SETCNT=aa     //Set the pulse count value.

Example:

AT+SETCNT=0         //Set the pulse count to 0. 

Connect DS18B20 sensor

RED <---------> +3.3V

YELLOW <----> ONE_WIRE

BLACK <------> GND

Connect SHT31 sensor

RED <---------> +3.3V

YELLOW <----> SCL

GREEN <------> SDA

BLACK <------> GND

Connect counting sensor

The counting sensor cables are connected to the +3.3v pin and GPIO_EXTI pin of the RS485_BL motherboard.

3.7 Buttons

3.8 +3V3 Output (Since v1.3.3)

3.9 +5V Output (Since v1.3.3)

3.10 LEDs

3.11 Switch Jumper

3.12 Battery & Power Consumption

RS485-BL uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace.

Battery Info & Power Consumption Analyze .

4. Case Study

User can check this URL for some case studies:  APP RS485 COMMUNICATE WITH SENSORS

5. Use AT Command

5.1 Access AT Command

5.2 Common AT Command Sequence

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

If device has not joined network yet:

• AT+FDR
• AT+NJM=0
• ATZ

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

AT+FDR          Reset Parameters to Factory Default, Keys Reserve

AT+NJM=0    Set to ABP mode

AT+ADR=0    Set the Adaptive Data Rate Off

AT+DR=5       Set Data Rate

AT+TDC=60000                 Set transmit interval to 60 seconds

AT+CHS=868400000         Set transmit frequency to 868.4Mhz

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

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

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:

6. FAQ

6.1 How to upgrade the image?

• Support new features

• For bug fix

• Change LoRaWAN bands.

Step1: Download flash loader.

Step2: Download the LT Image files.

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

6.2 How to change the LoRa Frequency Bands/Region?

6.3 How many RS485-Slave can RS485-BL connects?

6.4 How to Use RS485-BL  to connect to RS232 devices?

Use RS485-BL or RS485-LN to connect to RS232 devices. - DRAGINO

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

6.5.1 Introduce:

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:

1. Test if Modbus-MTU works with PC commands.
2. Check if RS485-LN sent the expected command to Mobus-MTU
3. Check if Modbus-MTU return back the expected result to RS485-LN.
4. If both b) and c) has issue, we can compare PC’s output and RS485-LN output.

Example Connection: 

6.5.2 Set up PC to monitor RS485 network With Serial tool

Note: Receive and send set to hex mode

6.5.3 With ModRSsim2:

(1) Select serial port MODBUS RS-232

(2) Click the serial port icon

(3) After selecting the correct serial port and baud rate, click ok

(4) Click the comms.

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

6.5.4 Example – Test the CFGDEV command

RS485-LN sent below command:

AT+CFGDEV=01 03 20 00 01 85 c0,1 to RS485 network, and PC is able to get this command and return commands from MTU to show in the serial tool.

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

We can also use ModRSsim2 to see the output.

6.5.5 Example – Test CMD command sets.

Run AT+SENSORVALUE=1 to test the CMD commands set in RS485-LN.

Serial port tool:

ModRSsim2:

6.5.6 Test with PC

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.

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

Connection method：

Link situation:

6.6 Where to get the decoder for RS485-BL?

The decoder for RS485-BL 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 for decoders (no intermediate data parsing part involved)

6.7 Why does my TTL sensor have returned data, but after using the command AT+DATACUT, the data in the payload is 0?

In TTL mode, you cannot use the node to automatically calculate the check code, you need to manually add the check code.

6.8 Where can I get a decoder?

Provides two decoders:

dragino-end-node-decoder/RS485-BL at main · dragino/dragino-end-node-decoder (github.com)

https://github.com/zorbaproject/ArduinoModbusForDraginoRS485#payload-decoder-for-thethingsnetwork

6.9 How to configure RS485 commands more conveniently？

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

It can help you configure RS485 sensors more conveniently
Please refer to the link below for specific usage：

RS485 Configure Tool - DRAGINO

7. Trouble Shooting

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

Please see this link for debug: LoRaWAN Communication Debug

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

It might about the channels mapping. Please see for detail: Notice of Frequency band

7.3 Possible reasons why the device is unresponsive：

1. Check whether the battery voltage is lower than 2.8V
2. Check whether the jumper of the device is correctly connected

3. Check whether the switch here of the device is at the ISP（The switch can operate normally only when it is in RUN）

8. Order Info

Part Number: RS485-BL-XXX

XXX:

• EU433:   frequency bands EU433
• EU868:   frequency bands EU868
• KR920:   frequency bands KR920
• CN470:   frequency bands CN470
• AS923:   frequency bands AS923
• AU915:   frequency bands AU915
• US915:   frequency bands US915
• IN865:    frequency bands IN865
• RU864:   frequency bands RU864
• KZ865:   frequency bands KZ865

9. Packing Info

• RS485-BL x 1

• Stick Antenna for LoRa RF part x 1

• Program cable x 1

• Device Size: 13.5 x 7 x 3 cm

• Device Weight: 105g

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

• Weight / pcs : 170g

   

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

• 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