Changes for page RS485-LN – RS485 to LoRaWAN Converter User Manual

Last modified by Xiaoling on 2025/04/23 15:56

From 18.1 to 17.3 From 32.15 to 32.14

From version 32.14

edited by Xiaoling
on 2022/06/02 15:26

Change comment: There is no comment for this version

To version 18.1

edited by Xiaoling
on 2022/05/23 08:48

Change comment: Uploaded new attachment "1653266934636-343.png", version {1}

Raw
Rendered

Summary

Page properties (1 modified, 0 added, 0 removed)
Attachments (0 modified, 0 added, 13 removed)

Details

Page properties

Content

@@ -1,11 +1,12 @@
  (% style="text-align:center" %)
--[[image:1653266934636-343.png||height="385" width="385"]]
++[[image:1652947681187-144.png||height="385" width="385"]]
--**RS485-LN – RS485 to LoRaWAN Converter User Manual**
++**RS485-BL – Waterproof RS485 to LoRaWAN Converter User Manual**
++
  **Table of Contents:**
@@ -14,46 +14,62 @@
  = 1.Introduction =
--== 1.1 What is RS485-LN RS485 to LoRaWAN Converter ==
++== 1.1 What is RS485-BL RS485 to LoRaWAN Converter ==
  (((
++
++)))
++
  (((
--The Dragino RS485-LN is a (% style="color:blue" %)**RS485 to LoRaWAN Converter**(%%). It converts the RS485 signal into LoRaWAN wireless signal which simplify the IoT installation and reduce the installation/maintaining cost.
++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.
  )))
  (((
--RS485-LN allows user to (% style="color:blue" %)**monitor / control RS485 devices**(%%) and reach extremely long ranges. It provides ultra-long range spread spectrum communication and high interference immunity whilst minimizing current consumption. It targets professional wireless sensor network applications such as irrigation systems, smart metering, smart cities, smartphone detection, building automation, and so on.
++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.
  )))
  (((
--(% style="color:blue" %)**For data uplink**(%%), RS485-LN sends user-defined commands to RS485 devices and gets the return from the RS485 devices. RS485-LN will process these returns according to user-define rules to get the final payload and upload to LoRaWAN server.
++RS485-BL is IP67 **waterproof** and powered by **8500mAh Li-SOCI2 battery**, it is designed for long term use for several years.
  )))
  (((
--(% style="color:blue" %)**For data downlink**(%%), RS485-LN runs in LoRaWAN Class C. When there downlink commands from LoRaWAN server, RS485-LN will forward the commands from LoRaWAN server to RS485 devices.
++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.
++)))
--(% style="color:blue" %)**Demo Dashboard for RS485-LN**(%%) connect to two energy meters: [[https:~~/~~/app.datacake.de/dashboard/d/58844a26-378d-4c5a-aaf5-b5b5b153447a>>url:https://app.datacake.de/dashboard/d/58844a26-378d-4c5a-aaf5-b5b5b153447a]]
++(((
++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.
  )))
++
++(((
++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.
  )))
--[[image:1653267211009-519.png||height="419" width="724"]]
++(((
++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.
++)))
++[[image:1652953304999-717.png||height="424" width="733"]]
  == 1.2 Specifications ==
--
  **Hardware System:**
  * STM32L072CZT6 MCU
  * SX1276/78 Wireless Chip
  * Power Consumption (exclude RS485 device):
--** Idle: 32mA@12v
--** 20dB Transmit: 65mA@12v
++** Idle: 6uA@3.3v
++*
++** 20dB Transmit: 130mA@3.3v
++
  **Interface for Model:**
--* RS485
--* Power Input 7~~ 24V DC.
++* 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:**
@@ -62,35 +62,28 @@
  ** Band 2 (LF): 410 ~~ 528 Mhz
  * 168 dB maximum link budget.
  * +20 dBm - 100 mW constant RF output vs.
--* +14 dBm high efficiency PA.
  * Programmable bit rate up to 300 kbps.
  * High sensitivity: down to -148 dBm.
  * Bullet-proof front end: IIP3 = -12.5 dBm.
  * Excellent blocking immunity.
--* Low RX current of 10.3 mA, 200 nA register retention.
  * Fully integrated synthesizer with a resolution of 61 Hz.
--* FSK, GFSK, MSK, GMSK, LoRaTM and OOK modulation.
++* 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.
--* Packet engine up to 256 bytes with CRC.
++* Automatic RF Sense and CAD with ultra-fast AFC.
--
--
  == 1.3 Features ==
--* LoRaWAN Class A & Class C protocol (default Class C)
++* LoRaWAN Class A & Class C protocol (default Class A)
  * Frequency Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915/IN865/RU864
  * AT Commands to change parameters
--* Remote configure parameters via LoRa Downlink
++* Remote configure parameters via LoRaWAN Downlink
  * Firmware upgradable via program port
  * Support multiply RS485 devices by flexible rules
  * Support Modbus protocol
--* Support Interrupt uplink (Since hardware version v1.2)
++* Support Interrupt uplink
--
--
  == 1.4 Applications ==
  * Smart Buildings & Home Automation
@@ -100,50 +100,55 @@
  * Smart Cities
  * Smart Factory
--
--
  == 1.5 Firmware Change log ==
--[[RS485-LN Image files – Download link and Change log>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/]]
++[[RS485-BL Image files – Download link and Change log>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/RS485-BL/Firmware/||style="background-color: rgb(255, 255, 255);"]]
--
  == 1.6 Hardware Change log ==
  (((
++v1.4
++)))
++
  (((
--v1.2: Add External Interrupt Pin.
++~1. Change Power IC to TPS22916
++)))
--v1.0: Release
--
++(((
++v1.3
  )))
++
++(((
++~1. Change JP3 from KF350-8P to KF350-11P, Add one extra interface for I2C and one extra interface for one-wire
  )))
--= 2. Power ON Device =
  (((
--The RS485-LN can be powered by 7 ~~ 24V DC power source. Connection as below
++v1.2
++)))
--* Power Source VIN to RS485-LN VIN+
--* Power Source GND to RS485-LN VIN-
--
  (((
--Once there is power, the RS485-LN will be on.
++Release version
  )))
--[[image:1653268091319-405.png]]
++= 2. Pin mapping and Power ON Device =
--
++(((
++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.
  )))
++[[image:1652953055962-143.png||height="387" width="728"]]
++
++
++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? ==
  (((
--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.
--
--
++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.
  )))
  == 3.2 Example to join LoRaWAN network ==
@@ -150,37 +150,27 @@
  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.
--[[image:1653268155545-638.png||height="334" width="724"]]
++[[image:1652953414711-647.png||height="337" width="723"]]
--
  (((
--(((
--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:
++The RS485-BL in this example connected to two RS485 devices for demonstration, user can connect to other RS485 devices via the same method.
  )))
  (((
--485A+ and 485B- of the sensor are connected to RS485A and RA485B of RS485-LN respectively.
++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:
  )))
--[[image:1653268227651-549.png||height="592" width="720"]]
--
  (((
--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-BL.
  )))
  (((
--**Step 1**: Create a device in TTN V3 with the OTAA keys from RS485-LN.
++Each RS485-BL is shipped with a sticker with unique device EUI:
  )))
--(((
--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:
  )))
@@ -187,11 +187,13 @@
  (((
  Add APP EUI in the application.
  )))
--)))
++
++
++
  [[image:image-20220519174512-1.png]]
--[[image:image-20220519174512-2.png||height="323" width="720"]]
++[[image:image-20220519174512-2.png||height="328" width="731"]]
  [[image:image-20220519174512-3.png||height="556" width="724"]]
@@ -207,28 +207,31 @@
  (((
--**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.
++**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.
  )))
  [[image:1652953568895-172.png||height="232" width="724"]]
--
  == 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.
++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.
  )))
--(((
--(% 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 ===
--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:
++RS485-BL can connect to either RS485 sensors or TTL sensor. User need to specify what type of sensor need to connect.
++**~1. RS485-MODBUS mode:**
++
++AT+MOD=1 ~/~/ Support RS485-MODBUS type sensors. User can connect multiply RS485 , Modbus sensors to the A / B pins.
++
++**2. TTL mode:**
++
++AT+MOD=2 ~/~/ Support TTL Level sensors, User can connect one TTL Sensor to the TXD/RXD/GND pins.
++
++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.
++
  (% border="1" style="background-color:#ffffcc; color:green; width:795px" %)
  |(((
  **AT Commands**
@@ -253,7 +253,13 @@
  |(((
  AT+PARITY
  )))|(% style="width:285px" %)(((
++(((
  Set UART parity (for RS485 connection)
++)))
++
++(((
++Default Value is: no parity.
++)))
  )))|(% style="width:347px" %)(((
  (((
  AT+PARITY=0
@@ -271,7 +271,7 @@
  )))
  (((
--
++Default Value is: 1bit.
  )))
  )))|(% style="width:347px" %)(((
  (((
@@ -290,10 +290,12 @@
  === 3.3.2 Configure sensors ===
  (((
++Some sensors might need to configure before normal operation. User can configure such sensor via PC or through RS485-BL AT Commands (% style="color:#4f81bd" %)**AT+CFGDEV**.
++)))
++
  (((
--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.
++When user issue an (% style="color:#4f81bd" %)**AT+CFGDEV**(%%) command, Each (% style="color:#4f81bd" %)**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.
  )))
--)))
  (% border="1" style="background-color:#ffffcc; color:green; width:806px" %)
  |**AT Commands**|(% style="width:418px" %)**Description**|(% style="width:256px" %)**Example**
@@ -305,6 +305,8 @@
  mm: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
  )))|(% style="width:256px" %)AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
++Detail of AT+CFGDEV command see [[AT+CFGDEV detail>>path:#AT_CFGDEV]].
++
  === 3.3.3 Configure read commands for each sampling ===
  (((
@@ -386,17 +386,11 @@
  **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.
--)))
  (% border="1" class="table-bordered" %)
  |(((
@@ -408,24 +408,26 @@
  )))
--**Examples:**
++Examples:
--~1. For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
++1. For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
  If we set AT+SEARCH1=1,1E 56 34.      (max 5 bytes for prefix)
--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**
++The valid data will be all bytes after 1E 56 34 , so it is 2e 30 58 5f 36 41 30 31 00 49
--[[image:1653269403619-508.png]]
++[[image:1652954654347-831.png]]
--2. For a return string from AT+COMMAND1:  16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
++1. For a return string from AT+COMMAND1:  16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
++
  If we set AT+SEARCH1=2, 1E 56 34+31 00 49
--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**
++Device will search the bytes between 1E 56 34 and 31 00 49. So it is 2e 30 58 5f 36 41 30
--[[image:1653269438444-278.png]]
++[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image014.png]]
++
  **AT+DATACUTx : **This command defines how to handle the return from AT+COMMANDx, max return length is 45 bytes.
  |(((
@@ -440,95 +440,94 @@
  * Grab bytes:
--[[image:1653269551753-223.png||height="311" width="717"]]
++[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image015.png]]
  * Grab a section.
--[[image:1653269568276-930.png||height="325" width="718"]]
++[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image016.png]]
  * Grab different sections.
--[[image:1653269593172-426.png||height="303" width="725"]]
++[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image017.png]]
--(% style="color:red" %)**Note:**
++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:
--(% style="color:red" %)AT+COMMAND1=11 01 1E D0,0
++AT+COMMAND1=11 01 1E D0,0
--(% style="color:red" %)AT+SEARCH1=1,1E 56 34
++AT+SEARCH1=1,1E 56 34
--(% style="color:red" %)AT+DATACUT1=0,2,1~~5
++AT+DATACUT1=0,2,1~~5
--(% style="color:red" %)Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
++Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
--(% style="color:red" %)String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49
++String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49
--(% style="color:red" %)Valid payload after DataCUT command: 2e 30 58 5f 36
++Valid payload after DataCUT command: 2e 30 58 5f 36
--[[image:1653269618463-608.png]]
++[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image018.png]]
--=== 3.3.4 Compose the uplink payload ===
--(((
++
++
++1.
++11.
++111. Compose the uplink payload
++
  Through AT+COMMANDx and AT+DATACUTx we got valid value from each RS485 commands, Assume these valid value are RETURN1, RETURN2, .., to RETURNx. The next step is how to compose the LoRa Uplink Payload by these RETURNs. The command is **AT+DATAUP.**
--)))
--(((
--(% style="color:#4f81bd" %)**Examples: AT+DATAUP=0**
--)))
--(((
--Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**A SIGNLE UPLINK**.
--)))
++**Examples: AT+DATAUP=0**
--(((
++Compose the uplink payload with value returns in sequence and send with **A SIGNLE UPLINK**.
++
  Final Payload is
--)))
--(((
--(% style="color:#4f81bd" %)**Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx**
--)))
++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.
--)))
--[[image:1653269759169-150.png||height="513" width="716"]]
++[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image019.png]]
--(% style="color:#4f81bd" %)**Examples: AT+DATAUP=1**
--Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**Multiply UPLINKs**.
++**Examples: AT+DATAUP=1**
++
++Compose the uplink payload with value returns in sequence and send with **Multiply UPLINKs**.
++
  Final Payload is
--(% style="color:#4f81bd" %)**Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA**
++Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA
 . Battery Info (2 bytes): Battery voltage
 . PAYVER (1 byte): Defined by AT+PAYVER
 . PAYLOAD COUNT (1 byte): Total how many uplinks of this sampling.
 . PAYLOAD# (1 byte): Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT)
--1. 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
++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
--[[image:1653269916228-732.png||height="433" width="711"]]
++[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image020.png]]
  So totally there will be 3 uplinks for this sampling, each uplink includes 6 bytes DATA
--DATA1=RETURN1 Valid Value = (% style="background-color:green; color:white" %)20 20 0a 33 90 41
++DATA1=RETURN1 Valid Value = 20 20 0a 33 90 41
--DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10=(% style="background-color:green; color:white" %) 02 aa 05 81 0a 20
++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 = (% style="background-color:green; color:white" %)20 20 20 2d 30
++DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 = 20 20 20 2d 30
++
++
  Below are the uplink payloads:
--[[image:1653270130359-810.png]]
++[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image021.png]]
--(% style="color:red" %)**Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:**
++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)
@@ -538,8 +538,12 @@
     ~* For all other bands: max 51 bytes for each uplink  ( so 51 -5 = 46 max valid date).
--=== 3.3.5 Uplink on demand ===
++
++1.
++11.
++111. Uplink on demand
++
  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.
  Downlink control command:
@@ -550,8 +550,8 @@
--1.
--11.
++1.
++11.
 . Uplink on Interrupt
  Put the interrupt sensor between 3.3v_out and GPIO ext.[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image022.png]]
@@ -565,7 +565,7 @@
  AT+INTMOD=3  Interrupt trigger by rising edge.
--1.
++1.
 . Uplink Payload
  |**Size(bytes)**|**2**|**1**|**Length depends on the return from the commands**
@@ -627,15 +627,15 @@
  * **Sensor Related Commands**: These commands are special designed for RS485-BL.  User can see these commands below:
--1.
--11.
++1.
++11.
 . 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: [[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.
++1.
++11.
 . Sensor related commands:
  ==== Choose Device Type (RS485 or TTL) ====
@@ -941,13 +941,13 @@
--1.
++1.
 . Buttons
  |**Button**|**Feature**
  |**RST**|Reboot RS485-BL
--1.
++1.
 . +3V3 Output
  RS485-BL has a Controllable +3V3 output, user can use this output to power external sensor.
@@ -965,7 +965,7 @@
  By default, the AT+3V3T=0. This is a special case, means the +3V3 output is always on at any time
--1.
++1.
 . +5V Output
  RS485-BL has a Controllable +5V output, user can use this output to power external sensor.
@@ -985,13 +985,13 @@
--1.
++1.
 . LEDs
  |**LEDs**|**Feature**
  |**LED1**|Blink when device transmit a packet.
--1.
++1.
 . Switch Jumper
  |**Switch Jumper**|**Feature**
@@ -1037,7 +1037,7 @@
--1.
++1.
 . Common AT Command Sequence
 . Multi-channel ABP mode (Use with SX1301/LG308)
@@ -1056,8 +1056,8 @@
  ATZ
--1.
--11.
++1.
++11.
 . Single-channel ABP mode (Use with LG01/LG02)
  AT+FDR   Reset Parameters to Factory Default, Keys Reserve
@@ -1132,7 +1132,7 @@
  [[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.
++1.
 . How to change the LoRa Frequency Bands/Region?
  User can follow the introduction for [[how to upgrade image>>path:#upgrade_image]]. When download the images, choose the required image file for download.
@@ -1139,7 +1139,7 @@
--1.
++1.
 . How many RS485-Slave can RS485-BL connects?
  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]].
@@ -1156,7 +1156,7 @@
--1.
++1.
 . Why I can’t join TTN V3 in US915 /AU915 bands?
  It might about the channels mapping. Please see for detail.

1653267211009-519.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-138.7 KB

Content

1653268091319-405.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-399.3 KB

Content

1653268155545-638.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-113.7 KB

Content

1653268227651-549.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-1.3 MB

Content

1653269403619-508.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-27.8 KB

Content

1653269438444-278.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-26.6 KB

Content

1653269551753-223.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-138.7 KB

Content

1653269568276-930.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-131.4 KB

Content

1653269593172-426.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-142.6 KB

Content

1653269618463-608.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-27.7 KB

Content

1653269759169-150.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-294.0 KB

Content

1653269916228-732.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-143.3 KB

Content

1653270130359-810.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-197.8 KB

Content