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

Last modified by Mengting Qiu on 2025/07/14 09:59

From 20.1 to 20.2 From 44.1 to 44.2

From version 20.2

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

Change comment: There is no comment for this version

To version 44.1

edited by Xiaoling
on 2022/06/02 16:53

Change comment: Uploaded new attachment "image-20220602165351-7.png", version {1}

Raw
Rendered

Summary

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

Details

Page properties

Content

@@ -18,40 +18,42 @@
  (((
  (((
--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.
++The Dragino RS485-LN is a (% style="color:blue" %)**RS485 to LoRaWAN Converter**(%%). It converts the RS485 signal into LoRaWAN wireless signal which simplify the IoT installation and reduce the installation/maintaining cost.
  )))
  (((
--RS485-LN allows user to 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-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.
  )))
  (((
--For data uplink, RS485-LN sends user-defined commands to RS485 devices and gets the return from the RS485 devices. RS485-LN will process these returns according to user-define rules to get the final payload and upload to LoRaWAN server.
++(% style="color:blue" %)**For data 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.
++(% style="color:blue" %)**For data downlink**(%%), RS485-LN runs in LoRaWAN Class C. When there downlink commands from LoRaWAN server, RS485-LN will forward the commands from LoRaWAN server to RS485 devices.
++
++(% style="color:blue" %)**Demo Dashboard for RS485-LN**(%%) connect to two energy meters: [[https:~~/~~/app.datacake.de/dashboard/d/58844a26-378d-4c5a-aaf5-b5b5b153447a>>url:https://app.datacake.de/dashboard/d/58844a26-378d-4c5a-aaf5-b5b5b153447a]]
  )))
  )))
  [[image:1653267211009-519.png||height="419" width="724"]]
++
  == 1.2 Specifications ==
++
  **Hardware System:**
  * STM32L072CZT6 MCU
--* SX1276/78 Wireless Chip
++* SX1276/78 Wireless Chip
  * Power Consumption (exclude RS485 device):
  ** Idle: 32mA@12v
--
--*
  ** 20dB Transmit: 65mA@12v
  **Interface for Model:**
  * RS485
--* Power Input 7~~ 24V DC.
++* Power Input 7~~ 24V DC.
  **LoRa Spec:**
@@ -98,6 +98,7 @@
  [[RS485-LN Image files – Download link and Change log>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/]]
++
  == 1.6 Hardware Change log ==
  (((
@@ -105,6 +105,8 @@
  v1.2: Add External Interrupt Pin.
  v1.0: Release
++
++
  )))
  )))
@@ -116,9 +116,13 @@
  * Power Source VIN to RS485-LN VIN+
  * Power Source GND to RS485-LN VIN-
++(((
  Once there is power, the RS485-LN will be on.
++)))
  [[image:1653268091319-405.png]]
++
++
  )))
  = 3. Operation Mode =
@@ -126,7 +126,9 @@
  == 3.1 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.
++The RS485-LN is configured as LoRaWAN OTAA Class C mode by default. It has OTAA keys to join network. To connect a local LoRaWAN network, user just need to input the OTAA keys in the network server and power on the RS485-LN. It will auto join the network via OTAA.
++
++
  )))
  == 3.2 Example to join LoRaWAN network ==
@@ -133,27 +133,37 @@
  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:1652953414711-647.png||height="337" width="723"]]
++[[image:1653268155545-638.png||height="334" width="724"]]
++
  (((
--The RS485-BL in this example connected to two RS485 devices for demonstration, user can connect to other RS485 devices via the same method.
++(((
++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 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:
++485A+ and 485B- of the sensor are connected to RS485A and RA485B of RS485-LN respectively.
  )))
++[[image:1653268227651-549.png||height="592" width="720"]]
++
  (((
--**Step 1**: Create a device in TTN V3 with the OTAA keys from RS485-BL.
++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:
  )))
  (((
--Each RS485-BL is shipped with a sticker with unique device EUI:
++**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:
  )))
@@ -160,13 +160,11 @@
  (((
  Add APP EUI in the application.
  )))
++)))
--
--
--
  [[image:image-20220519174512-1.png]]
--[[image:image-20220519174512-2.png||height="328" width="731"]]
++[[image:image-20220519174512-2.png||height="323" width="720"]]
  [[image:image-20220519174512-3.png||height="556" width="724"]]
@@ -182,44 +182,43 @@
  (((
--**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.
++**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.
  )))
  [[image:1652953568895-172.png||height="232" width="724"]]
++
  == 3.3 Configure Commands to read data ==
  (((
--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.
++(((
++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.
  )))
--=== 3.3.1 onfigure UART settings for RS485 or TTL communication ===
++(((
++(% 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
--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:**
++=== 3.3.1 onfigure UART settings for RS485 or TTL communication ===
--AT+MOD=1 ~/~/ Support RS485-MODBUS type sensors. User can connect multiply RS485 , Modbus sensors to the A / B pins.
++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:
--**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" %)
--|(((
++(% border="1" style="background-color:#ffffcc; color:green; width:782px" %)
++|(% style="width:128px" %)(((
  **AT Commands**
--)))|(% style="width:285px" %)(((
++)))|(% style="width:305px" %)(((
  **Description**
--)))|(% style="width:347px" %)(((
++)))|(% style="width:346px" %)(((
  **Example**
  )))
--|(((
++|(% style="width:128px" %)(((
  AT+BAUDR
--)))|(% style="width:285px" %)(((
++)))|(% style="width:305px" %)(((
  Set the baud rate (for RS485 connection). Default Value is: 9600.
--)))|(% style="width:347px" %)(((
++)))|(% style="width:346px" %)(((
  (((
  AT+BAUDR=9600
  )))
@@ -228,18 +228,12 @@
  Options: (1200,2400,4800,14400,19200,115200)
  )))
  )))
--|(((
++|(% style="width:128px" %)(((
  AT+PARITY
--)))|(% style="width:285px" %)(((
--(((
++)))|(% style="width:305px" %)(((
  Set UART parity (for RS485 connection)
--)))
--
++)))|(% style="width:346px" %)(((
  (((
--Default Value is: no parity.
--)))
--)))|(% style="width:347px" %)(((
--(((
  AT+PARITY=0
  )))
@@ -247,17 +247,17 @@
  Option: 0: no parity, 1: odd parity, 2: even parity
  )))
  )))
--|(((
++|(% style="width:128px" %)(((
  AT+STOPBIT
--)))|(% style="width:285px" %)(((
++)))|(% style="width:305px" %)(((
  (((
  Set serial stopbit (for RS485 connection)
  )))
  (((
--Default Value is: 1bit.
++
  )))
--)))|(% style="width:347px" %)(((
++)))|(% style="width:346px" %)(((
  (((
  AT+STOPBIT=0 for 1bit
  )))
@@ -274,12 +274,10 @@
  === 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**.
--)))
--
  (((
--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.
++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" %)
  |**AT Commands**|(% style="width:418px" %)**Description**|(% style="width:256px" %)**Example**
@@ -291,82 +291,37 @@
  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 ===
  (((
--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 confirm what commands we need to send to the RS485 sensors to read data. After the RS485 sensors send back the value, it normally include some bytes and we only need a few from them for a shorten payload.
--(((
--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.
--)))
++During each sampling, the RS485-LN 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.
--)))
++**Each RS485 commands include two parts:**
--(((
--**Handle return from sensors to RS485-BL**:
--)))
++~1. What commands RS485-LN will send to the RS485 sensors. There are total 15 commands from **AT+COMMAD1**, **ATCOMMAND2**,…, to **AT+COMMANDF**. All commands are of same grammar.
--(((
--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**
--)))
++2. How to get wanted value the from RS485 sensors returns from by 1). There are total 15 AT Commands to handle the return, commands are **AT+DATACUT1**,**AT+DATACUT2**,…, **AT+DATACUTF** corresponding to the commands from 1). All commands are of same grammar.
--* (((
--**AT+DATACUT**
--)))
++3. Some RS485 device might has longer delay on reply, so user can use AT+CMDDL to set the timeout for getting reply after the RS485 command is sent. For example **AT+CMDDL1=1000** to send the open time to 1000ms
--(((
--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.
--**AT+COMMANDx : **This command will be sent to RS485/TTL devices during each sampling, Max command length is 14 bytes. The grammar is:
--(% border="1" class="table-bordered" %)
--|(((
++**AT+COMMANDx : **This command will be sent to RS485 devices during each sampling, Max command length is 14 bytes. The grammar is:
++
++(% border="1" style="background-color:#4bacc6; color:white; width:499px" %)
++|(% style="width:496px" %)(((
  **AT+COMMANDx=xx xx xx xx xx xx xx xx xx xx xx xx,m**
  **xx xx xx xx xx xx xx xx xx xx xx xx: The RS485 command to be sent**
@@ -376,43 +376,13 @@
  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.
++In the RS485-LN, 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" %)
--|(((
--**AT+SEARCHx=aa,xx xx xx xx xx**
--
--* **aa: 1: prefix match mode; 2: prefix and suffix match mode**
--* **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
--
--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 2e 30 58 5f 36 41 30 31 00 49
--
--[[image:1652954654347-831.png]]
--
--
--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 2e 30 58 5f 36 41 30
--
--[[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.
--|(((
++(% border="1" style="background-color:#4bacc6; color:white; width:725px" %)
++|(% style="width:722px" %)(((
  **AT+DATACUTx=a,b,c**
  * **a: length for the return of AT+COMMAND**
@@ -420,242 +420,183 @@
  * **c: define the position for valid value.  **
  )))
--Examples:
++**Examples:**
  * Grab bytes:
--[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image015.png]]
++[[image:image-20220602153621-1.png]]
++
  * Grab a section.
--[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image016.png]]
++[[image:image-20220602153621-2.png]]
++
  * Grab different sections.
--[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image017.png]]
++[[image:image-20220602153621-3.png]]
++
++)))
--Note:
++=== 3.3.4 Compose the uplink payload ===
--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
--
--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
--
--String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49
--
--Valid payload after DataCUT command: 2e 30 58 5f 36
--
--[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image018.png]]
--
--
--
--
--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.**
++
++)))
--**Examples: AT+DATAUP=0**
++(((
++(% style="color:#037691" %)**Examples: AT+DATAUP=0**
--Compose the uplink payload with value returns in sequence and send with **A SIGNLE UPLINK**.
++
++)))
++(((
++Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**A SIGNLE UPLINK**.
++)))
++
++(((
  Final Payload is
++)))
--Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx
++(((
++(% 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.
++)))
--[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image019.png]]
++[[image:1653269759169-150.png||height="513" width="716"]]
++(% style="color:#037691" %)**Examples: AT+DATAUP=1**
--**Examples: AT+DATAUP=1**
--Compose the uplink payload with value returns in sequence and send with **Multiply UPLINKs**.
++Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**Multiply UPLINKs**.
  Final Payload is
--Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA
++(% style="color:#4f81bd" %)**Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA**
--1. Battery Info (2 bytes): Battery voltage
--1. PAYVER (1 byte): Defined by AT+PAYVER
--1. PAYLOAD COUNT (1 byte): Total how many uplinks of this sampling.
--1. 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*!>>path:#max_byte]]) for each uplink so each uplink <= 11 bytes. For the last uplink, DATA will might less than 6 bytes
++1. PAYVER: Defined by AT+PAYVER
++1. PAYLOAD COUNT: Total how many uplinks of this sampling.
++1. PAYLOAD#: Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT)
++1. DATA: Valid value: max 8 bytes for each uplink so each uplink <= 11 bytes. For the last uplink, DATA will might less than 8 bytes
--[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image020.png]]
++[[image:image-20220602155039-4.png]]
--So totally there will be 3 uplinks for this sampling, each uplink includes 6 bytes DATA
++So totally there will be 3 uplinks for this sampling, each uplink include 8 bytes DATA
--DATA1=RETURN1 Valid Value = 20 20 0a 33 90 41
++DATA1=RETURN1 Valid Value + the first two of Valid value of RETURN10= **20 20 0a 33 90 41 02 aa**
--DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10= 02 aa 05 81 0a 20
++DATA2=3^^rd^^ ~~ 10^^th^^ byte of Valid value of RETURN10= **05 81 0a 20 20 20 20 2d**
--DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 = 20 20 20 2d 30
++DATA3=the rest of Valid value of RETURN10= **30**
++(% style="color:red" %)Notice: In firmware v1.3, the Max bytes has been changed according to the max bytes in different Frequency Bands for lowest SF. As below:
--Below are the uplink payloads:
++   ~* For AU915/AS923 bands, if UplinkDwell time=0, max 51 bytes for each uplink.
--[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image021.png]]
++   * For AU915/AS923 bands, if UplinkDwell time=0, max 11 bytes for each uplink.
++   * For US915 band, max 11 bytes for each uplink.
--Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:
++   ~* For all other bands: max 51 bytes for each uplink.
--   ~* 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).
++Below are the uplink payloads:
--   * For US915 band, max 11 bytes for each uplink ( so 11 -5 = 6 max valid date).
++[[image:1654157178836-407.png]]
--   ~* For all other bands: max 51 bytes for each uplink  ( so 51 -5 = 46 max valid date).
++=== 3.3.5 Uplink on demand ===
++Except uplink periodically, RS485-LN is able to uplink on demand. The server send downlink command to RS485-LN and RS485 will uplink data base on the command.
--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:
--[[0x08 command>>path:#downlink_08]]: Poll an uplink with current command set in RS485-BL.
++**0x08 command**: Poll an uplink with current command set in RS485-LN.
--[[0xA8 command>>path:#downlink_A8]]: Send a command to RS485-BL and uplink the output from sensors.
++**0xA8 command**: Send a command to RS485-LN and uplink the output from sensors.
--1.
--11.
--111. Uplink on Interrupt
++=== 3.3.6 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]]
++RS485-LN support external Interrupt uplink since hardware v1.2 release.
--AT+INTMOD=0  Disable Interrupt
++[[image:1654157342174-798.png]]
--AT+INTMOD=1  Interrupt trigger by rising or falling edge.
++Connect the Interrupt pin to RS485-LN INT port and connect the GND pin to V- port. When there is a high voltage (Max 24v) on INT pin. Device will send an uplink packet.
--AT+INTMOD=2  Interrupt trigger by falling edge. ( Default Value)
--AT+INTMOD=3  Interrupt trigger by rising edge.
++== 3.4 Uplink Payload ==
--
--1.
--11. Uplink Payload
--
--|**Size(bytes)**|**2**|**1**|**Length depends on the return from the commands**
--|Value|(((
++(% border="1" style="background-color:#4bacc6; color:white; width:734px" %)
++|**Size(bytes)**|(% style="width:120px" %)**2**|(% style="width:116px" %)**1**|(% style="width:386px" %)**Length depends on the return from the commands**
++|Value|(% style="width:120px" %)(((
  Battery(mV)
  &
  Interrupt _Flag
--)))|(((
++)))|(% style="width:116px" %)(((
  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.
++)))|(% style="width:386px" %)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.
  Below is the decoder for the first 3 bytes. The rest bytes are dynamic depends on different RS485 sensors.
--function Decoder(bytes, port) {
++== 3.5 Configure RS485-BL via AT or Downlink ==
--~/~/Payload Formats of RS485-BL Deceive
++User can configure RS485-LN via AT Commands or LoRaWAN Downlink Commands
--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],
--
--    };
--
--  }
--
--
--
--
--
--
--
--TTN V3 uplink screen shot.
--
--[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png]]
--
--1.
--11. Configure RS485-BL via AT or Downlink
--
--User can configure RS485-BL via [[AT Commands >>path:#_Using_the_AT]]or LoRaWAN Downlink Commands
--
  There are two kinds of Commands:
--* **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
++* (% style="color:#4f81bd" %)**Common Commands**(%%): They should be available for each sensor, such as: change uplink interval, reset device. For firmware v1.3, user can find what common commands it supports: [[End Device AT Commands and Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]]
--* **Sensor Related Commands**: These commands are special designed for RS485-BL.  User can see these commands below:
++* (% style="color:#4f81bd" %)**Sensor Related Commands**(%%): These commands are special designed for RS485-LN.  User can see these commands below:
--1.
--11.
--111. Common Commands:
++=== 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: [[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]]
++They should be available for each of Dragino Sensors, such as: change uplink interval, reset device. For firmware v1.3, user can find what common commands it supports: [[End Device AT Commands and Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]]
--1.
--11.
--111. Sensor related commands:
++=== 3.5.2 Sensor related commands ===
--==== Choose Device Type (RS485 or TTL) ====
++Response feature is added to the server's downlink, a special package with a FPort of 200 will be uploaded immediately after receiving the data sent by the server.
--RS485-BL can connect to either RS485 sensors or TTL sensor. User need to specify what type of sensor need to connect.
++[[image:image-20220602163333-5.png||height="263" width="1160"]]
--* AT Command
++The first byte of this package represents whether the configuration is successful, 00 represents failure, 01 represents success. Except for the first byte, the other is the previous downlink. (All commands except A8 type commands are applicable)
--**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.
++=== 3.5.3 Sensor related commands ===
++====   ====
--* Downlink Payload
++==== **RS485 Debug Command** ====
--**0A aa**     à same as AT+MOD=aa
++This command is used to configure the RS485 devices; they won’t be used during sampling.
++* **AT Command**
++(% class="box infomessage" %)
++(((
++**AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m**
++)))
--==== [[RS485 Debug Command>>path:#downlink_A8]] (AT+CFGDEV) ====
++m: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
--This command is used to configure the RS485 or TTL sensors; they won’t be used during sampling.
++* **Downlink Payload**
--* AT Command
--
--AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
--
--m: 0: no CRC; 1: add CRC-16/MODBUS in the end of this command.
--
--
--
--* Downlink Payload
--
  Format: A8 MM NN XX XX XX XX YY
  Where:
@@ -663,9 +663,12 @@
  * 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
++* YY: How many bytes will be uplink from the return of this RS485 command,
++** if YY=0, RS485-LN will execute the downlink command without uplink;
++** if YY>0, RS485-LN will uplink total YY bytes from the output of this RS485 command; Fport=200
++** if YY=FF, RS485-LN will uplink RS485 output with the downlink command content; Fport=200.
--**Example 1:**
++**Example 1** ~-~-> Configure without ask for uplink (YY=0)
  To connect a Modbus Alarm with below commands.
@@ -675,59 +675,76 @@
  So if user want to use downlink command to control to RS485 Alarm, he can use:
--**A8 01 06 0A 05 00 04 00 01 00**: to activate the RS485 Alarm
++(% style="color:#4f81bd" %)**A8 01 06 0A 05 00 04 00 01 00**(%%): to activate the RS485 Alarm
--**A8 01 06 0A 05 00 04 00 00 00**: to deactivate the RS485 Alarm
++(% style="color:#4f81bd" %)**A8 01 06 0A 05 00 04 00 00 00**(%%): to deactivate the RS485 Alarm
  A8 is type code and 01 means add CRC-16/MODBUS at the end, the 3^^rd^^ byte is 06, means the next 6 bytes are the command to be sent to the RS485 network, the final byte 00 means this command don’t need to acquire output.
--**Example 2:**
++**Example 2** ~-~-> Configure with requesting uplink and original downlink command (**YY=FF**)
--Check TTL Sensor return:
++User in IoT server send a downlink command: (% style="color:#4f81bd" %)**A8 01 06 0A 08 00 04 00 01 YY**
--[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image024.png]]
++RS485-LN got this downlink command and send (% style="color:#4f81bd" %)**0A 08 00 04 00 01 **(%%)to Modbus network. One of the RS485 sensor in the network send back Modbus reply **0A 08 00 04 00 00**. RS485-LN get this reply and combine with the original downlink command and uplink. The uplink message is:
++   **A8** (% style="color:#4f81bd" %)**0A 08 00 04 00  **(% style="color:red" %)**01 06** ** **(% style="color:green" %)**0A 08 00 04 00 00**
++ [[image:1654159460680-153.png]]
--==== Set Payload version ====
++
++==== **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 Command:**
--AT+PAYVER: Set PAYVER field = 1
++(% class="box infomessage" %)
++(((
++**AT+PAYVER: Set PAYVER field = 1**
++)))
--* Downlink Payload:
++* **Downlink Payload:**
--0xAE 01   à Set PAYVER field =  0x01
++**0xAE 01**   ~-~-> Set PAYVER field =  0x01
--0xAE 0F   à Set PAYVER field =  0x0F
++**0xAE 0F**   ~-~-> Set PAYVER field =  0x0F
--==== Set RS485 Sampling Commands ====
++==== **Set RS485 Sampling Commands** ====
++
  AT+COMMANDx, AT+DATACUTx and AT+SEARCHx
--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]].
++These three commands are used to configure how the RS485-BL polling data from Modbus device. Detail of usage please see : [[polling RS485 device>>||anchor="H3.3.3Configurereadcommandsforeachsampling"]].
--* AT Command:
++* **AT Command:**
--AT+COMMANDx: Configure RS485 read command to sensor.
++(% class="box infomessage" %)
++(((
++**AT+COMMANDx: Configure RS485 read command to sensor.**
++)))
--AT+DATACUTx: Configure how to handle return from RS485 devices.
++(% class="box infomessage" %)
++(((
++**AT+DATACUTx: Configure how to handle return from RS485 devices.**
++)))
--AT+SEARCHx: Configure search command
++(% class="box infomessage" %)
++(((
++**AT+SEARCHx: Configure search command**
++)))
--* Downlink Payload:
++* **Downlink Payload:**
--0xAF downlink command can be used to set AT+COMMANDx or AT+DATACUTx.
++**0xAF** downlink command can be used to set AT+COMMANDx or AT+DATACUTx.
--Note: if user use AT+COMMANDx to add a new command, he also need to send AT+DATACUTx downlink.
++(% style="color:red" %)**Note**(%%): if user use AT+COMMANDx to add a new command, he also need to send AT+DATACUTx downlink.
  Format: AF MM NN LL XX XX XX XX YY
@@ -734,23 +734,23 @@
  Where:
  * 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
++* 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.
++* 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:
++**Example:**
--**AF 03 01 06 0A 05 00 04 00 01 00**: Same as AT+COMMAND3=0A 05 00 04 00 01,1
++(% style="color:#037691" %)**AF 03 01 06 0A 05 00 04 00 01 00**(%%): Same as AT+COMMAND3=0A 05 00 04 00 01,1
--**AF 03 02 06 10 01 05 06 09 0A 00**: Same as AT+DATACUT3=**16**,**1**,**5+6+9+10**
++(% style="color:#037691" %)**AF 03 02 06**(% style="color:orange" %)** 10 **(% style="color:red" %)**01 **(% style="color:green" %)**05 06 09 0A**(% style="color:#037691" %)** 00**(%%): Same as AT+DATACUT3=(% style="color:orange" %)**16**(%%),(% style="color:red" %)**1**(%%),(% style="color:green" %)**5+6+9+10**
--**AF 03 02 06 0B 02 05 07 08 0A 00**: Same as AT+DATACUT3=**11**,**2**,**5~~7+8~~10**
++(% style="color:#037691" %)**AF 03 02 06 **(% style="color:orange" %)**0B**(% style="color:red" %)** 02 **(% style="color:green" %)**05 07 08 0A **(% style="color:#037691" %)**00**(%%): Same as AT+DATACUT3=(% style="color:orange" %)**11**(%%),(% style="color:red" %)**2**(%%),(% style="color:green" %)**5~~7+8~~10**
--0xAB downlink command can be used for set AT+SEARCHx
++**0xAB** downlink command can be used for set AT+SEARCHx
--Example: **AB aa 01 03 xx xx xx** (03 here means there are total 3 bytes after 03) So
++**Example:** **AB aa 01 03 xx xx xx** (03 here means there are total 3 bytes after 03) So
  * 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
@@ -758,145 +758,164 @@
  **AB aa 02 03 xx xx xx 02 yy yy**  same as **AT+SEARCHaa=2,xx xx xx+yy yy**
--==== Fast command to handle MODBUS device ====
++==== **Fast command to handle MODBUS device** ====
++
  AT+MBFUN is valid since v1.3 firmware version. The command is for fast configure to read Modbus devices. It is only valid for the devices which follow the [[MODBUS-RTU protocol>>url:https://www.modbustools.com/modbus.html]].
  This command is valid since v1.3 firmware version
--AT+MBFUN has only two value:
++**AT+MBFUN has only two value:**
--* AT+MBFUN=1: Enable Modbus reading. And get response base on the MODBUS return
++* **AT+MBFUN=1**: Enable Modbus reading. And get response base on the MODBUS return
  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.
--* AT+MBFUN=0: Disable Modbus fast reading.
++* **AT+MBFUN=0**: Disable Modbus fast reading.
--Example:
++**Example:**
  * 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.
--[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image025.png]]
++[[image:1654133913295-597.png]]
--[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image026.png]]
++[[image:1654133954153-643.png]]
--* Downlink Commands:
++* **Downlink Commands:**
--A9 aa -à Same as AT+MBFUN=aa
++**A9 aa** ~-~-> Same as AT+MBFUN=aa
--==== RS485 command timeout ====
++==== **RS485 command timeout** ====
++
  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.
  Default value: 0, range:  0 ~~ 5 seconds
--* AT Command:
++* **AT Command:**
--AT+CMDDLaa=hex(bb cc)
++(% class="box infomessage" %)
++(((
++**AT+CMDDLaa=hex(bb cc)**
++)))
--Example:
++**Example:**
  **AT+CMDDL1=1000** to send the open time to 1000ms
--* Downlink Payload:
++* **Downlink Payload:**
 x AA aa bb cc
  Same as: AT+CMDDLaa=hex(bb cc)
--   Example:
++   **Example:**
--   0xAA 01 03 E8  à Same as **AT+CMDDL1=1000 ms**
++   **0xAA 01 03 E8**  ~-~-> Same as **AT+CMDDL1=1000 ms**
--==== [[Uplink>>path:#downlink_A8]] payload mode ====
++==== **Uplink payload mode** ====
++
  Define to use one uplink or multiple uplinks for the sampling.
--The use of this command please see: [[Compose Uplink payload>>path:#DataUP]]
++The use of this command please see: [[Compose Uplink payload>>||anchor="H3.3.4Composetheuplinkpayload"]]
--* AT Command:
++* **AT Command:**
--AT+DATAUP=0
++(% class="box infomessage" %)
++(((
++**AT+DATAUP=0**
++)))
--AT+DATAUP=1
++(% class="box infomessage" %)
++(((
++**AT+DATAUP=1**
++)))
--* Downlink Payload:
++* **Downlink Payload:**
--0xAD 00   à Same as AT+DATAUP=0
++**0xAD 00**   **~-~->** Same as AT+DATAUP=0
--0xAD 01   à Same as AT+DATAUP=1
++**0xAD 01**   **~-~->** Same as AT+DATAUP=1
--==== Manually trigger an Uplink ====
++==== **Manually trigger an Uplink** ====
++
  Ask device to send an uplink immediately.
--* Downlink Payload:
++* **Downlink Payload:**
--0x08 FF, RS485-BL will immediately send an uplink.
++**0x08 FF**, RS485-BL will immediately send an uplink.
--==== Clear RS485 Command ====
++==== **Clear RS485 Command** ====
++
  The AT+COMMANDx and AT+DATACUTx settings are stored in special location, user can use below command to clear them.
--* AT Command:
++* **AT Command:**
--**AT+CMDEAR=mm,nn**   mm: start position of erase ,nn: stop position of erase
++(% style="color:#037691" %)**AT+CMDEAR=mm,nn** (%%)    mm: start position of erase ,nn: stop position of erase Etc. AT+CMDEAR=1,10 means erase AT+COMMAND1/AT+DATACUT1 to AT+COMMAND10/AT+DATACUT10
--Etc. AT+CMDEAR=1,10 means erase AT+COMMAND1/AT+DATACUT1 to AT+COMMAND10/AT+DATACUT10
--
  Example screen shot after clear all RS485 commands.
--
  The uplink screen shot is:
--[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png]]
++[[image:1654134704555-320.png]]
--* Downlink Payload:
++* **Downlink Payload:**
--0x09 aa bb  same as AT+CMDEAR=aa,bb
++**0x09 aa bb**  same as AT+CMDEAR=aa,bb
--==== Set Serial Communication Parameters ====
++==== **Set Serial Communication Parameters** ====
++
  Set the Rs485 serial communication parameters:
--* AT Command:
++* **AT Command:**
  Set Baud Rate:
--AT+BAUDR=9600    ~/~/ Options: (1200,2400,4800,14400,19200,115200)
++(% class="box infomessage" %)
++(((
++**AT+BAUDR=9600**    ~/~/ Options: (1200,2400,4800,14400,19200,115200)
++)))
++Set UART Parity
--Set UART parity
++(% class="box infomessage" %)
++(((
++**AT+PARITY=0**    ~/~/ Option: 0: no parity, 1: odd parity, 2: even 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
++(% class="box infomessage" %)
++(((
++**AT+STOPBIT=0**    ~/~/ Option: 0 for 1bit; 1 for 1.5 bit ; 2 for 2 bits
++)))
--* Downlink Payload:
++* **Downlink Payload:**
--A7 01 aa bb: Same  AT+BAUDR=hex(aa bb)*100
++**A7 01 aa bb**: Same  AT+BAUDR=hex(aa bb)*100
--Example:
++**Example:**
  * A7 01 00 60   same as AT+BAUDR=9600
  * A7 01 04 80     same as AT+BAUDR=115200
@@ -906,287 +906,22 @@
  A7 03 aa: Same as  AT+STOPBIT=aa  (aa value: 00 , 01 or 02)
--==== Control output power duration ====
++==== **Control output power duration** ====
++
  User can set the output power duration before each sampling.
--* AT Command:
++* **AT Command:**
--Example:
++**Example:**
--AT+3V3T=1000 ~/~/ 3V3 output power will open 1s before each sampling.
++**AT+3V3T=1000**  ~/~/ 3V3 output power will open 1s before each sampling.
--AT+5VT=1000 ~/~/ +5V output power will open 1s before each sampling.
++**AT+5VT=1000**  ~/~/ +5V output power will open 1s before each sampling.
--* LoRaWAN Downlink Command:
++* **LoRaWAN Downlink Command:**
--07 01 aa bb  Same as AT+5VT=(aa bb)
++**07 01 aa bb**  Same as AT+5VT=(aa bb)
--07 02 aa bb  Same as AT+3V3T=(aa bb)
--
--
--
--
--1.
--11. Buttons
--
--|**Button**|**Feature**
--|**RST**|Reboot RS485-BL
--
--1.
--11. +3V3 Output
--
--RS485-BL has a Controllable +3V3 output, user can use this output to power external sensor.
--
--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.
--
--
--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.
--
--
--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.
--
--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.
--
--
--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.
--
--
--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**
--|**LED1**|Blink when device transmit a packet.
--
--1.
--11. Switch Jumper
--
--|**Switch Jumper**|**Feature**
--|**SW1**|(((
--ISP position: Upgrade firmware via UART
--
--Flash position: Configure device, check running status.
--)))
--|**SW2**|(((
--5V position: set to compatible with 5v I/O.
--
--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.
--
--[[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
--
--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.
--
--[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image027.png]]
--
--
--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:
--
--[[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
--111. Multi-channel ABP mode (Use with SX1301/LG308)
--
--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)
--
--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:**
--
--1. Make sure the device is set to ABP mode in the IoT Server.
--1. Make sure the LG01/02 gateway RX frequency is exactly the same as AT+CHS setting.
--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.
--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
--
--[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image029.png]]
--
--
--1. FAQ
--11. How to upgrade the image?
--
--The RS485-BL LoRaWAN Controller is shipped with a 3.5mm cable, the cable is used to upload image to RS485-BL to:
--
--* Support new features
--* For bug fix
--* Change LoRaWAN bands.
--
--Below shows the hardware connection for how to upload an image to RS485-BL:
--
--[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image030.png]]
--
--**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]].
--
--**Step2**: Download the [[LT Image files>>url:http://www.dragino.com/downloads/index.php?dir=LT_LoRa_IO_Controller/LT33222-L/image/]].
--
--**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]]
--
--
--[[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?
--
--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?
--
--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?
--
--Please see this link for debug:
--
--[[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?
--
--It might about the channels mapping. Please see for detail.
--
--[[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
--* **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
--
--1. Packing Info
--
--**Package Includes**:
--
--* RS485-BL x 1
--* Stick Antenna for LoRa RF part x 1
--* Program cable x 1
--
--**Dimension and weight**:
--
--* 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
--
--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.
--* Provide as much information as possible regarding your enquiry (product models, accurately describe your problem and steps to replicate it etc) and send a mail to
--
--[[support@dragino.com>>url:file:///D:/市场资料/说明书/LoRa/LT系列/support@dragino.com]]
++**07 02 aa bb**  Same as AT+3V3T=(aa bb)

1653268155545-638.png

Author

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

Size

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

Content

1653268227651-549.png

Author

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

Size

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

Content

1653269403619-508.png

Author

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

Size

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

Content

1653269438444-278.png

Author

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

Size

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

Content

1653269551753-223.png

Author

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

Size

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

Content

1653269568276-930.png

Author

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

Size

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

Content

1653269593172-426.png

Author

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

Size

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

Content

1653269618463-608.png

Author

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

Size

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

Content

1653269759169-150.png

Author

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

Size

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

Content

1653269916228-732.png

Author

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

Size

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

Content

1653270130359-810.png

Author

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

Size

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

Content

1654157178836-407.png

Author

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

Size

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

Content

1654157342174-798.png

Author

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

Size

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

Content

1654158783574-851.png

Author

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

Size

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

Content

1654159460680-153.png

Author

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

Size

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

Content

image-20220602153621-1.png

Author

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

Size

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

Content

image-20220602153621-2.png

Author

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

Size

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

Content

image-20220602153621-3.png

Author

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

Size

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

Content

image-20220602155039-4.png

Author

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

Size

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

Content

image-20220602163333-5.png

Author

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

Size

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

Content

image-20220602165351-6.png

Author

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

Size

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

Content

image-20220602165351-7.png

Author

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

Size

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

Content

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

Summary

Details

Applications

Navigation