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

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

From 32.16 to 32.17 From 73.2 to 73.3

From version 32.17

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

Change comment: There is no comment for this version

To version 73.2

edited by Xiaoling
on 2022/09/12 10:35

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (2 modified, 0 added, 0 removed)
Attachments (0 modified, 27 added, 0 removed)

Details

Page properties

Title

@@ -1,1 +1,1 @@
--RS485-LN – RS485 to LoRaWAN Converter
++RS485-LN – RS485 to LoRaWAN Converter User Manual

Content

@@ -1,48 +1,80 @@
--(% style="text-align:center" %)
--[[image:1653266934636-343.png||height="385" width="385"]]
++(% aria-label="1653266934636-343.png image widget" contenteditable="false" role="region" tabindex="-1" %)
++(((
++(% data-widget="image" style="text-align:center" %)
++[[image:1653266934636-343.png||height="385" width="385"]](% title="Click and drag to resize" %)
++(% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||height="15" role="presentation" title="Click and drag to move" width="15"]]
++)))
--**RS485-LN – RS485 to LoRaWAN Converter User Manual**
++
++
++
  **Table of Contents:**
++{{toc/}}
++(% aria-label="macro:toc widget" contenteditable="false" role="region" tabindex="-1" %)
++(((
++(% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||height="15" role="presentation" title="Click and drag to move" width="15"]]
++)))
++
++
++
++
++
  = 1.Introduction =
++
  == 1.1 What is RS485-LN 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.
  )))
++)))
  (((
++(((
  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.
  )))
++)))
  (((
++(((
  (% 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.
  )))
++)))
  (((
++(((
  (% 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"]]
++(% aria-label="1653267211009-519.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:1653267211009-519.png||data-widget="image" height="419" width="724"]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %)
++
  == 1.2 Specifications ==
--**Hardware System:**
++(% style="color:#037691" %)**Hardware System:**
  * STM32L072CZT6 MCU
  * SX1276/78 Wireless Chip
@@ -50,13 +50,17 @@
  ** Idle: 32mA@12v
  ** 20dB Transmit: 65mA@12v
--**Interface for Model:**
++
++(% style="color:#037691" %)**Interface for Model:**
++
  * RS485
  * Power Input 7~~ 24V DC.
--**LoRa Spec:**
++
++(% style="color:#037691" %)**LoRa Spec:**
++
  * Frequency Range:
  ** Band 1 (HF): 862 ~~ 1020 Mhz
  ** Band 2 (LF): 410 ~~ 528 Mhz
@@ -74,14 +74,16 @@
  * Preamble detection.
  * 127 dB Dynamic Range RSSI.
  * Automatic RF Sense and CAD with ultra-fast AFC.
--* Packet engine up to 256 bytes with CRC.
++* Packet engine up to 256 bytes with CRC
++
  == 1.3 Features ==
++
  * LoRaWAN Class A & Class C protocol (default Class C)
--* Frequency Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915/IN865/RU864
++* Frequency Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915/IN865/RU864/MA869
  * AT Commands to change parameters
  * Remote configure parameters via LoRa Downlink
  * Firmware upgradable via program port
@@ -91,8 +91,10 @@
++
  == 1.4 Applications ==
++
  * Smart Buildings & Home Automation
  * Logistics and Supply Chain Management
  * Smart Metering
@@ -102,19 +102,28 @@
++
  == 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/]]
++
  == 1.6 Hardware Change log ==
++
  (((
  (((
++(((
  v1.2: Add External Interrupt Pin.
++)))
++(((
  v1.0: Release
++)))
++
  )))
  )))
@@ -121,6 +121,7 @@
  = 2. Power ON Device =
++
  (((
  The RS485-LN can be powered by 7 ~~ 24V DC power source. Connection as below
@@ -131,26 +131,33 @@
  Once there is power, the RS485-LN will be on.
  )))
--[[image:1653268091319-405.png]]
++(% aria-label="1653268091319-405.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:1653268091319-405.png||data-widget="image"]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %)
++
  )))
  = 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.
++)))
++
  )))
  == 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>>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"]]
++(% aria-label="1653268155545-638.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:1653268155545-638.png||data-widget="image" height="334" width="724"]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %)
  (((
@@ -162,14 +162,17 @@
 A+ and 485B- of the sensor are connected to RS485A and RA485B of RS485-LN respectively.
  )))
--[[image:1653268227651-549.png||height="592" width="720"]]
++(% aria-label="1653268227651-549.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:1653268227651-549.png||data-widget="image" height="592" width="720"]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %)
++
  (((
--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:
++The LG308 is already set to connect to [[TTN V3 network >>path:https://www.thethingsnetwork.org/]]. So what we need to now is only configure the TTN V3:
++
++
  )))
  (((
--**Step 1**: Create a device in TTN V3 with the OTAA keys from RS485-LN.
++(% style="color:blue" %)**Step 1**(%%): Create a device in TTN V3 with the OTAA keys from RS485-LN.
  )))
  (((
@@ -177,8 +177,9 @@
  )))
  )))
--[[image:1652953462722-299.png]]
++(% aria-label="1652953462722-299.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:1652953462722-299.png||data-widget="image"]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %)
++
  (((
  (((
  User can enter this key in their LoRaWAN Server portal. Below is TTN V3 screen shot:
@@ -185,65 +185,75 @@
  )))
  (((
--Add APP EUI in the application.
++**Add APP EUI in the application.**
  )))
  )))
--[[image:image-20220519174512-1.png]]
++(% aria-label="image-20220519174512-1.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:image-20220519174512-1.png||data-widget="image"]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %)
--[[image:image-20220519174512-2.png||height="323" width="720"]]
++(% aria-label="image-20220519174512-2.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:image-20220519174512-2.png||data-widget="image" height="323" width="720"]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %)
--[[image:image-20220519174512-3.png||height="556" width="724"]]
++(% aria-label="image-20220519174512-3.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:image-20220519174512-3.png||data-widget="image" height="556" width="724"]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %)
--[[image:image-20220519174512-4.png]]
++(% aria-label="image-20220519174512-4.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:image-20220519174512-4.png||data-widget="image"]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %)
  You can also choose to create the device manually.
--[[image:1652953542269-423.png||height="710" width="723"]]
++(% aria-label="1652953542269-423.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:1652953542269-423.png||data-widget="image" height="710" width="723"]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %)
--Add APP KEY and DEV EUI
--[[image:1652953553383-907.png||height="514" width="724"]]
++**Add APP KEY and DEV EUI**
++(% aria-label="1652953553383-907.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:1652953553383-907.png||data-widget="image" height="514" width="724"]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %)
++
++
  (((
--**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.
++(% style="color:blue" %)**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"]]
++(% aria-label="1652953568895-172.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:1652953568895-172.png||data-widget="image" height="232" width="724"]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %)
++
  == 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 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>>||anchor="H3.5ConfigureRS485-LNviaATorDownlink"]] or LoRaWAN Downlink Command to configure what commands RS485-LN should send for each sampling and how to handle the return from RS485 devices.
  )))
++)))
  (((
--(% style="color:red" %)Note: below description and commands are for firmware version >v1.1, if you have firmware version v1.0. Please check the [[user manual v1.0>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/&file=RS485-LN_UserManual_v1.0.1.pdf]] or upgrade the firmware to v1.1
++(((
++(% 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 ===
++=== 3.3.1 Configure 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:
--(% border="1" style="background-color:#ffffcc; color:green; width:782px" %)
--|(% style="width:128px" %)(((
++(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)
++|=(% style="width: 110px;" %)(((
  **AT Commands**
--)))|(% style="width:305px" %)(((
++)))|=(% style="width: 190px;" %)(((
  **Description**
--)))|(% style="width:346px" %)(((
++)))|=(% style="width: 190px;" %)(((
  **Example**
  )))
--|(% style="width:128px" %)(((
++|(% style="width:110px" %)(((
  AT+BAUDR
--)))|(% style="width:305px" %)(((
++)))|(% style="width:190px" %)(((
  Set the baud rate (for RS485 connection). Default Value is: 9600.
--)))|(% style="width:346px" %)(((
++)))|(% style="width:190px" %)(((
  (((
  AT+BAUDR=9600
  )))
@@ -252,11 +252,11 @@
  Options: (1200,2400,4800,14400,19200,115200)
  )))
  )))
--|(% style="width:128px" %)(((
++|(% style="width:110px" %)(((
  AT+PARITY
--)))|(% style="width:305px" %)(((
++)))|(% style="width:190px" %)(((
  Set UART parity (for RS485 connection)
--)))|(% style="width:346px" %)(((
++)))|(% style="width:190px" %)(((
  (((
  AT+PARITY=0
  )))
@@ -265,9 +265,9 @@
  Option: 0: no parity, 1: odd parity, 2: even parity
  )))
  )))
--|(% style="width:128px" %)(((
++|(% style="width:110px" %)(((
  AT+STOPBIT
--)))|(% style="width:305px" %)(((
++)))|(% style="width:190px" %)(((
  (((
  Set serial stopbit (for RS485 connection)
  )))
@@ -275,7 +275,7 @@
  (((
  )))
--)))|(% style="width:346px" %)(((
++)))|(% style="width:190px" %)(((
  (((
  AT+STOPBIT=0 for 1bit
  )))
@@ -289,909 +289,1287 @@
  )))
  )))
--
  === 3.3.2 Configure sensors ===
++
  (((
  (((
--Some sensors might need to configure before normal operation. User can configure such sensor via PC and RS485 adapter or through RS485-LN AT Commands (% style="color:#4f81bd" %)**AT+CFGDEV**(%%). Each (% style="color:#4f81bd" %)**AT+CFGDEV **(%%)equals to send a RS485 command to sensors. This command will only run when user input it and won’t run during each sampling.
++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**
--|AT+CFGDEV|(% style="width:418px" %)(((
++(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)
++|=(% style="width: 110px;" %)**AT Commands**|=(% style="width: 190px;" %)**Description**|=(% style="width: 190px;" %)**Example**
++|AT+CFGDEV|(% style="width:110px" %)(((
++(((
  This command is used to configure the RS485/TTL devices; they won’t be used during sampling.
++)))
++(((
  AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,
++)))
++(((
  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
++)))
++)))|(% style="width:190px" %)AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
--
--
  === 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 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.
--)))
++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.
--(((
  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:**
++
++(% style="color:#037691" %)**Each RS485 commands include two parts:**
++
++~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.
++
++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.
++
++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
++
++
++After we got the valid value from each RS485 commands, we need to combine them together with the command **AT+DATAUP**.
++
++Below are examples for the how above AT Commands works.
++
++
++(% style="color:#037691" %)**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" %)(((
++(% style="color:#037691" %)**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**
++
++**m: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command**
  )))
--(((
--RS485-BL can send out pre-set max 15 strings via **AT+COMMAD1**, **ATCOMMAND2**,…, to **AT+COMMANDF** . All commands are of same grammar.
++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-LN, we should use this command AT+COMMAND1=01 03 0B B8 00 02,1 for the same.
++
++
++(% style="color:#037691" %)**AT+DATACUTx **(%%)**: **This command defines how to handle the return from AT+COMMANDx, max return length is 100 bytes.
++
++(% border="1" style="background-color:#4bacc6; color:white; width:510px" %)
++|(% style="width:510px" %)(((
++**AT+DATACUTx=a,b,c**
++
++* **a: length for the return of AT+COMMAND**
++* **b:1: grab valid value by byte, max 6 bytes. 2: grab valid value by bytes section, max 3 sections.**
++* **c: define the position for valid value.  **
  )))
--(((
--**Handle return from sensors to RS485-BL**:
++**Examples:**
++
++* (% style="color:#037691" %)**Grab bytes**
++
++(% aria-label="image-20220602153621-1.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:image-20220602153621-1.png||data-widget="image"]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %)
++
++
++
++* (% style="color:#037691" %)**Grab a section**
++
++(% aria-label="image-20220602153621-2.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:image-20220602153621-2.png||data-widget="image"]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %)
++
++
++
++* (% style="color:#037691" %)**Grab different sections**
++
++(% aria-label="image-20220602153621-3.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:image-20220602153621-3.png||data-widget="image"]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %)
++
++
++
  )))
++=== 3.3.4 Compose the uplink payload ===
++
++
  (((
--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**
--)))
++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.**
--* (((
--**AT+DATACUT**
++
  )))
  (((
--When the return value from sensor have fix length and we know which position the valid value we should get, we can use AT+DATACUT command.
--)))
++(% style="color:#037691" %)**Examples: AT+DATAUP=0**
--* (((
--**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.
++Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**A SIGNLE UPLINK**.
  )))
  (((
--**Define wait timeout:**
++Final Payload is
  )))
  (((
--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
++(% style="color:#4f81bd" %)**Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx**
  )))
  (((
--After we got the valid value from each RS485 commands, we need to combine them together with the command **AT+DATAUP**.
++Where PAYVER is defined by AT+PAYVER, below is an example screen shot.
  )))
--**Examples:**
++(% aria-label="1653269759169-150.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:1653269759169-150.png||data-widget="image" height="513" width="716"]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %)
--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:
++(% style="color:#037691" %)**Examples: AT+DATAUP=1**
--(% border="1" class="table-bordered" %)
--|(((
--**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**
++Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**Multiply UPLINKs**.
--**m: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command**
--)))
++Final Payload is
++(% style="color:#4f81bd" %)**Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA**
++
++
++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
++
++(% aria-label="image-20220602155039-4.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:image-20220602155039-4.png||data-widget="image"]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %)
++
++
++So totally there will be 3 uplinks for this sampling, each uplink include 8 bytes DATA
++
++DATA1=RETURN1 Valid Value + the first two of Valid value of RETURN10= **20 20 0a 33 90 41 02 aa**
++
++DATA2=3^^rd^^ ~~ 10^^th^^ byte of Valid value of RETURN10= **05 81 0a 20 20 20 20 2d**
++
++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:**
++
++   ~* For AU915/AS923 bands, if UplinkDwell time=0, max 51 bytes for each uplink.
++
++   * For AU915/AS923 bands, if UplinkDwell time=0, max 11 bytes for each uplink.
++
++   * For US915 band, max 11 bytes for each uplink.
++
++   ~* For all other bands: max 51 bytes for each uplink.
++
++(% style="color:red" %)*** When AT+DATAUP=1, the maximum number of segments is 15, and the maximum total number of bytes is 1500;**
++
++(% style="color:red" %)**   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)**
++
++
++(% style="color:#4f81bd" %)**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.
++
++[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/test/WebHome/image-20220824114359-3.png?width=1106&height=297&rev=1.1||alt="image-20220824114359-3.png" height="297" width="1106"]]
++
++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.
++
++[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/test/WebHome/image-20220824114330-2.png?rev=1.1||alt="image-20220824114330-2.png"]]
++
++
++Below are the uplink payloads:
++
++(% aria-label="1654157178836-407.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:1654157178836-407.png||data-widget="image"]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %)
++
++
++
++=== 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.
++
++Downlink control command:
++
++**0x08 command**: Poll an uplink with current command set in RS485-LN.
++
++**0xA8 command**: Send a command to RS485-LN and uplink the output from sensors.
++
++
++
++=== 3.3.6 Uplink on Interrupt ===
++
++
++RS485-LN support external Interrupt uplink since hardware v1.2 release.
++
++(% aria-label="1654157342174-798.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:1654157342174-798.png||data-widget="image"]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %)
++
++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.
++
++
++
++== 3.4 Uplink Payload ==
++
++
++(% aria-label="image-20220606110929-1.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:image-20220606110929-1.png||data-widget="image"]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %)
++
++Below is the decoder for the first 3 bytes. The rest bytes are dynamic depends on different RS485 sensors.
++
++
++
++== 3.5 Configure RS485-LN via AT or Downlink ==
++
++
  (((
--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.
++User can configure RS485-LN via AT Commands or LoRaWAN Downlink Commands
  )))
  (((
--In the RS485-BL, we should use this command AT+COMMAND1=01 03 0B B8 00 02,1 for the same.
++There are two kinds of Commands:
  )))
--(((
--**AT+SEARCHx**: This command defines how to handle the return from AT+COMMANDx.
++* (((
++(% 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: [[AT Commands and Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]]
  )))
--(% border="1" class="table-bordered" %)
--|(((
--**AT+SEARCHx=aa,xx xx xx xx xx**
++* (((
++(% style="color:#4f81bd" %)**Sensor Related Commands**(%%): These commands are special designed for RS485-LN.  User can see these commands below:
++)))
--* **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)
++=== 3.5.1 Common Commands ===
--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**
--[[image:1653269403619-508.png]]
++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]]
--2. 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**
++=== 3.5.2 Downlink Response(Since firmware v1.4) ===
--[[image:1653269438444-278.png]]
--**AT+DATACUTx : **This command defines how to handle the return from AT+COMMANDx, max return length is 45 bytes.
++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.
--|(((
--**AT+DATACUTx=a,b,c**
++(% aria-label="image-20220602163333-5.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:image-20220602163333-5.png||data-widget="image" height="263" width="1160"]](% title="Click and drag to resize" %)
--* **a: length for the return of AT+COMMAND**
--* **b:1: grab valid value by byte, max 6 bytes. 2: grab valid value by bytes section, max 3 sections.**
--* **c: define the position for valid value.  **
--)))
++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)
--Examples:
--* Grab bytes:
--[[image:1653269551753-223.png||height="311" width="717"]]
++=== 3.5.3 Sensor related commands ===
--* Grab a section.
--[[image:1653269568276-930.png||height="325" width="718"]]
--* Grab different sections.
--[[image:1653269593172-426.png||height="303" width="725"]]
++==== (% style="color:blue" %)**RS485 Debug Command**(%%) ====
--(% style="color:red" %)**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.
++(((
++This command is used to configure the RS485 devices; they won't be used during sampling.
++)))
--Example:
++* (((
++(% style="color:#037691" %)**AT Command**
--(% style="color:red" %)AT+COMMAND1=11 01 1E D0,0
++(((
++**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
++)))
++)))
--(% style="color:red" %)AT+SEARCH1=1,1E 56 34
++(((
++
++)))
--(% style="color:red" %)AT+DATACUT1=0,2,1~~5
++* (((
++(% style="color:#037691" %)**Downlink Payload**
++)))
--(% style="color:red" %)Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
++(((
++Format: A8 MM NN XX XX XX XX YY
++)))
--(% style="color:red" %)String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49
++(((
++Where:
++)))
--(% style="color:red" %)Valid payload after DataCUT command: 2e 30 58 5f 36
++* (((
++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,
++)))
--[[image:1653269618463-608.png]]
++* (((
++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.
++)))
++)))
--=== 3.3.4 Compose the uplink payload ===
++(((
++
++(% style="color:blue" %)**Example 1:**  (%%)  ~-~-> Configure without ask for uplink (YY=0)
++)))
++
  (((
--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.**
++To connect a Modbus Alarm with below commands.
  )))
++* (((
++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.
++)))
++
  (((
--(% style="color:#4f81bd" %)**Examples: AT+DATAUP=0**
++
++
++So if user want to use downlink command to control to RS485 Alarm, he can use:
  )))
  (((
--Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**A SIGNLE UPLINK**.
++(% style="color:#4f81bd" %)**A8 01 06 0A 05 00 04 00 01 00**(%%): to activate the RS485 Alarm
  )))
  (((
--Final Payload is
++(% style="color:#4f81bd" %)**A8 01 06 0A 05 00 04 00 00 00**(%%): to deactivate the RS485 Alarm
  )))
  (((
--(% style="color:#4f81bd" %)**Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx**
++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.
  )))
  (((
--Where PAYVER is defined by AT+PAYVER, below is an example screen shot.
++
  )))
--[[image:1653269759169-150.png||height="513" width="716"]]
++(((
++(% style="color:blue" %)**Example 2:**  (%%)      ~-~-> Configure with requesting uplink and original downlink command (**YY=FF**)
++)))
--(% style="color:#4f81bd" %)**Examples: AT+DATAUP=1**
++(((
++User in IoT server send a downlink command: (% style="color:#4f81bd" %)**A8 01 06 0A 08 00 04 00 01 YY**
++)))
--Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**Multiply UPLINKs**.
++(((
++
++)))
--Final Payload is
++(((
++(((
++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**
++)))
--(% 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*!) for each uplink so each uplink <= 11 bytes. For the last uplink, DATA will might less than 6 bytes
++(((
++ (% aria-label="1654159460680-153.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:1654159460680-153.png||data-widget="image"]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %)
++)))
--[[image:1653269916228-732.png||height="433" width="711"]]
--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
++==== (% style="color:blue" %)**Set Payload version**(%%) ====
--DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10=(% style="background-color:green; color:white" %) 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
++(((
++This is the first byte of the uplink payload. RS485-LN can connect to different sensors. User can set the PAYVER field to tell server how to decode the current payload.
++)))
--Below are the uplink payloads:
++* (((
++(% style="color:#037691" %)**AT Command:**
--[[image:1653270130359-810.png]]
++**AT+PAYVER:    **Set PAYVER field = 1
++
++)))
++* (((
++(% style="color:#037691" %)**Downlink Payload:**
++)))
--(% style="color:red" %)**Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:**
++(((
++**0xAE 01**   ~-~->     Set PAYVER field =  0x01
++)))
--   ~* For AU915/AS923 bands, if UplinkDwell time=0, max 51 bytes for each uplink ( so 51 -5 = 46 max valid date)
++(((
++**0xAE 0F**   ~-~->     Set PAYVER field =  0x0F
++)))
--   * 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).
++1)Add the interrupt flag at the highest bit of the Payver byte, that is, Byte7 of the first byte. (Since v1.4.0)[[image:image-20220824145428-2.png||height="168" width="1300"]]
--   ~* For all other bands: max 51 bytes for each uplink  ( so 51 -5 = 46 max valid date).
--=== 3.3.5 Uplink on demand ===
++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 FFs.
--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.
++[[image:image-20220824145428-3.png||height="308" width="1200"]]
--Downlink control command:
--[[0x08 command>>path:#downlink_08]]: Poll an uplink with current command set in RS485-BL.
++==== (% style="color:blue" %)**Set RS485 Sampling Commands**(%%) ====
--[[0xA8 command>>path:#downlink_A8]]: Send a command to RS485-BL and uplink the output from sensors.
++(((
++AT+COMMANDx or AT+DATACUTx
++)))
++(((
++These three commands are used to configure how the RS485-LN polling data from Modbus device. Detail of usage please see : [[polling RS485 device>>||anchor="H3.3.3Configurereadcommandsforeachsampling"]].
++)))
--1.
--11.
--111. 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]]
++* (((
++(% style="color:#037691" %)**AT Command:**
++)))
--AT+INTMOD=0  Disable Interrupt
++**AT+COMMANDx:    **Configure RS485 read command to sensor.
--AT+INTMOD=1  Interrupt trigger by rising or falling edge.
++**AT+DATACUTx:        **Configure how to handle return from RS485 devices.
--AT+INTMOD=2  Interrupt trigger by falling edge. ( Default Value)
--AT+INTMOD=3  Interrupt trigger by rising edge.
++* (((
++(% style="color:#037691" %)**Downlink Payload:**
++)))
++(((
++**0xAF** downlink command can be used to set AT+COMMANDx or AT+DATACUTx.
--1.
--11. Uplink Payload
++
++)))
--|**Size(bytes)**|**2**|**1**|**Length depends on the return from the commands**
--|Value|(((
--Battery(mV)
++(((
++(% style="color:red" %)**Note**(%%): if user use AT+COMMANDx to add a new command, he also need to send AT+DATACUTx downlink.
--&
++
++)))
--Interrupt _Flag
--)))|(((
--PAYLOAD_VER
++(((
++Format: AF MM NN LL XX XX XX XX YY
++)))
--
--)))|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.
++(((
++Where:
++)))
--Below is the decoder for the first 3 bytes. The rest bytes are dynamic depends on different RS485 sensors.
++* (((
++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-LN will execute the downlink command without uplink; if YY=1, RS485-LN will execute an uplink after got this command.
++)))
++(((
++
--function Decoder(bytes, port) {
++**Example:**
++)))
--~/~/Payload Formats of RS485-BL Deceive
++(((
++(% 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
++)))
--return {
++(((
++(% 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**
++)))
--    ~/~/Battery,units:V
++(((
++(% 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**
++)))
--    BatV:((bytes[0]<<8 | bytes[1])&0x7fff)/1000,
--    ~/~/GPIO_EXTI
--    EXTI_Trigger:(bytes[0] & 0x80)? "TRUE":"FALSE",
--    ~/~/payload of version
++==== (% style="color:blue" %)**Fast command to handle MODBUS device**(%%) ====
--    Pay_ver:bytes[2],
--    };
++(((
++**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 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.
++)))
++(((
++
++)))
++(((
++**Example:**
++)))
++* (((
++AT+MBFUN=1 and AT+DATACUT1/AT+DATACUT2  are not configure (0,0,0). So RS485-LN.
++)))
++* (((
++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.
++
++)))
++(% aria-label="image-20220602165351-6.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:image-20220602165351-6.png||data-widget="image"]](% title="Click and drag to resize" %)
--TTN V3 uplink screen shot.
++(% aria-label="image-20220602165351-7.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:image-20220602165351-7.png||data-widget="image"]](% title="Click and drag to resize" %)
--[[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:
++==== (% style="color:blue" %)**RS485 command timeout**(%%) ====
--* **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
--* **Sensor Related Commands**: These commands are special designed for RS485-BL.  User can see these commands below:
++(((
++Some Modbus device has slow action to send replies. This command is used to configure the RS485-LN to use longer time to wait for their action.
++)))
--1.
--11.
--111. Common Commands:
++(((
++Default value: 0, range:  0 ~~ 65 seconds
++)))
--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]]
++* (((
++(% style="color:#037691" %)** AT Command:**
++**AT+CMDDLaa=hex(bb cc)*1000**
++)))
--1.
--11.
--111. Sensor related commands:
++(((
++
--==== Choose Device Type (RS485 or TTL) ====
++**Example:**
++)))
--RS485-BL can connect to either RS485 sensors or TTL sensor. User need to specify what type of sensor need to connect.
++(((
++**AT+CMDDL1=1000** to send the open time to 1000ms
++)))
--* AT Command
++(((
++
++)))
--**AT+MOD=1** ~/~/ Set to support RS485-MODBUS type sensors. User can connect multiply RS485 , Modbus sensors to the A / B pins.
++* (((
++(% style="color:#037691" %)** Downlink Payload:**
++)))
--**AT+MOD=2** ~/~/ Set to support TTL Level sensors, User can connect one TTL Sensor to the TXD/RXD/GND pins.
++(((
++**0x AA aa bb cc**
++)))
++(((
++Same as: AT+CMDDLaa=hex(bb cc)*1000
++)))
--* Downlink Payload
++(((
++**Example:**
++)))
--**0A aa**     à same as AT+MOD=aa
++(((
++**0xAA 01 00 01**    ~-~-> Same as  **AT+CMDDL1=1000 ms**
++)))
++==== (% style="color:blue" %)**Uplink payload mode**(%%) ====
--==== [[RS485 Debug Command>>path:#downlink_A8]] (AT+CFGDEV) ====
--This command is used to configure the RS485 or TTL sensors; they won’t be used during sampling.
++(((
++Define to use one uplink or multiple uplinks for the sampling.
++)))
--* AT Command
++(((
++The use of this command please see: [[Compose Uplink payload>>||anchor="H3.3.4Composetheuplinkpayload"]]
--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.
++* (((
++(% style="color:#037691" %)** AT Command:**
++**AT+DATAUP=0**
++**AT+DATAUP=1**
--* Downlink Payload
++
++)))
--Format: A8 MM NN XX XX XX XX YY
++**0xAD 01 00 00 14**   **~-~->** Same as AT+DATAUP=1，20000 ~/~/(00 00 14 is 20 seconds)
--Where:
++Each uplink is sent to the server at 20-second intervals when segmented.
--* 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
--**Example 1:**
++* (((
++(% style="color:#037691" %)** Downlink Payload:**
++)))
--To connect a Modbus Alarm with below commands.
++**0xAD 00**   **~-~->** Same as AT+DATAUP=0
--* 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.
++**0xAD 01**   **~-~->** Same as AT+DATAUP=1  ~/~/Each uplink is sent to the server one after the other as it is segmented.
--* 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.
--So if user want to use downlink command to control to RS485 Alarm, he can use:
++* (((
++(% style="color:#037691" %)** AT Command:**
++)))
--**A8 01 06 0A 05 00 04 00 01 00**: to activate the RS485 Alarm
++**AT+DATAUP=1,Timeout**
--**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.
++* (((
++(% style="color:#037691" %)** Downlink Payload:**
++)))
++**0xAD 01 00 00 14**   **~-~->** Same as AT+DATAUP=1，20000 ~/~/(00 00 14 is 20 seconds)
--**Example 2:**
++Each uplink is sent to the server at 20-second intervals when segmented.
--Check TTL Sensor return:
++==== (% style="color:blue" %)**Manually trigger an Uplink**(%%) ====
--[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image024.png]]
++(((
++Ask device to send an uplink immediately.
++)))
++* (((
++(% style="color:#037691" %)** AT Command:**
++)))
++(((
++No AT Command for this, user can press the [[ACT button>>||anchor="H3.7Buttons"]] for 1 second for the same.
++)))
--==== 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.
++* (((
++(% style="color:#037691" %)** Downlink Payload:**
++)))
--* AT Command:
++(((
++**0x08 FF**, RS485-LN will immediately send an uplink.
++)))
--AT+PAYVER: Set PAYVER field = 1
--* Downlink Payload:
--0xAE 01   à Set PAYVER field =  0x01
++==== (% style="color:blue" %)**Clear RS485 Command**(%%) ====
--0xAE 0F   à Set PAYVER field =  0x0F
++(((
++The AT+COMMANDx and AT+DATACUTx settings are stored in special location, user can use below command to clear them.
--==== Set RS485 Sampling Commands ====
++
++)))
--AT+COMMANDx, AT+DATACUTx and AT+SEARCHx
++* (((
++(% style="color:#037691" %)** AT Command:**
++)))
--These three commands are used to configure how the RS485-BL polling data from Modbus device. Detail of usage please see : [[polling RS485 device>>path:#polling_485]].
++(((
++**AT+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
++)))
--* AT Command:
++(((
++Example screen shot after clear all RS485 commands.
++)))
--AT+COMMANDx: Configure RS485 read command to sensor.
++(((
++
++)))
--AT+DATACUTx: Configure how to handle return from RS485 devices.
++(((
++The uplink screen shot is:
++)))
--AT+SEARCHx: Configure search command
++(% aria-label="1654160691922-496.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:1654160691922-496.png||data-widget="image"]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %)
--* Downlink Payload:
++* (((
++(% style="color:#037691" %)** Downlink Payload:**
++)))
--0xAF downlink command can be used to set AT+COMMANDx or AT+DATACUTx.
++(((
++**0x09 aa bb**  same as AT+CMDEAR=aa,bb
++)))
--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
--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
--* 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.
++==== (% style="color:blue" %)**Set Serial Communication Parameters**(%%) ====
--Example:
--**AF 03 01 06 0A 05 00 04 00 01 00**: Same as AT+COMMAND3=0A 05 00 04 00 01,1
++(((
++Set the Rs485 serial communication parameters:
--**AF 03 02 06 10 01 05 06 09 0A 00**: Same as AT+DATACUT3=**16**,**1**,**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" %)** AT Command:**
++)))
++(((
++* Set Baud Rate
++)))
--0xAB downlink command can be used for set AT+SEARCHx
++**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 400ms), otherwise data will be lost
--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
++(((
++* Set UART Parity
++)))
--**AB aa 02 03 xx xx xx 02 yy yy**  same as **AT+SEARCHaa=2,xx xx xx+yy yy**
++**AT+PARITY=0**    ~/~/ Option: 0: no parity, 1: odd parity, 2: even parity
--==== Fast command to handle MODBUS device ====
++(((
++* Set STOPBIT
++)))
--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]].
++**AT+STOPBIT=0**    ~/~/ Option: 0 for 1bit; 1 for 1.5 bit ; 2 for 2 bits
--This command is valid since v1.3 firmware version
--AT+MBFUN has only two value:
++* (((
++(% style="color:#037691" %)** Downlink Payload:**
++)))
--* AT+MBFUN=1: Enable Modbus reading. And get response base on the MODBUS return
++(((
++**A7 01 aa bb**:     Same  AT+BAUDR=hex(aa bb)*100
++)))
--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.
++(((
++**Example:**
++)))
--* AT+MBFUN=0: Disable Modbus fast reading.
++* (((
++A7 01 00 60   same as AT+BAUDR=9600
++)))
++* (((
++A7 01 04 80     same as AT+BAUDR=115200
++)))
--Example:
++(((
++A7 02 aa:    Same as  AT+PARITY=aa  (aa value: 00 , 01 or 02)
++)))
--* 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.
++(((
++A7 03 aa:    Same as  AT+STOPBIT=aa  (aa value: 00 , 01 or 02)
++)))
--[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image025.png]]
++==== (% style="color:blue" %)**Encrypted payload**(%%) ====
--[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image026.png]]
++(((
++
++)))
++* (((
++(% style="color:#037691" %)** AT Command:**
++)))
--* Downlink Commands:
++**AT+DECRYPT=1  **~/~/ The payload is uploaded without encryption
--A9 aa -à Same as AT+MBFUN=aa
++**AT+DECRYPT=0  **~/~/Encrypt when uploading payload (default)
--==== RS485 command timeout ====
++==== (% style="color:blue" %)**Get sensor value**(%%) ====
--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
++* (((
++(% style="color:#037691" %)** AT Command:**
++)))
++**AT+GETSENSORVALUE=0  **~/~/ The serial port gets the reading of the current sensor
--* AT Command:
++**AT+GETSENSORVALUE=1  **~/~/The serial port gets the current sensor reading and uploads it.
--AT+CMDDLaa=hex(bb cc)
--Example:
++==== (% style="color:blue" %)**Resets the downlink packet count**(%%) ====
--**AT+CMDDL1=1000** to send the open time to 1000ms
++* (((
++(% style="color:#037691" %)** AT Command:**
++)))
--* Downlink Payload:
++**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)
--0x AA aa bb cc
++**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.
--Same as: AT+CMDDLaa=hex(bb cc)
--   Example:
++==== (% style="color:blue" %)**When the limit bytes are exceeded, upload in batches**(%%) ====
--   0xAA 01 03 E8  à Same as **AT+CMDDL1=1000 ms**
++* (((
++(% style="color:#037691" %)** AT Command:**
++)))
--==== [[Uplink>>path:#downlink_A8]] payload mode ====
++ **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)
--Define to use one uplink or multiple uplinks for the sampling.
++ **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.
--The use of this command please see: [[Compose Uplink payload>>path:#DataUP]]
--* AT Command:
++* (((
++(% style="color:#037691" %)** Downlink Payload:**
++)))
--AT+DATAUP=0
++**0x21 00 01 **         ~/~/ Set  the DISMACANS=1
--AT+DATAUP=1
++==== (% style="color:blue" %)** Copy downlink to uplink **(%%) ====
--* Downlink Payload:
--0xAD 00   à Same as AT+DATAUP=0
++* (((
++(% style="color:#037691" %)** AT Command:**
++)))
--0xAD 01   à Same as AT+DATAUP=1
++**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.
--==== Manually trigger an Uplink ====
++[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LSN50%20%26%20LSN50-V2%20-%20LoRaWAN%20Sensor%20Node%20User%20Manual/WebHome/image-20220823173747-6.png?width=1124&height=165&rev=1.1||alt="image-20220823173747-6.png"]]
--Ask device to send an uplink immediately.
++For example, sending 11 22 33 44 55 66 77 will return invalid configuration 00 11 22 33 44 55 66 77.
--* Downlink Payload:
++[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LSN50%20%26%20LSN50-V2%20-%20LoRaWAN%20Sensor%20Node%20User%20Manual/WebHome/image-20220823173833-7.png?width=1124&height=149&rev=1.1||alt="image-20220823173833-7.png"]]
--0x08 FF, RS485-BL will immediately send an uplink.
++For example, if 01 00 02 58 is issued, a valid configuration of 01 01 00 02 58 will be returned.
--==== Clear RS485 Command ====
++==== (% style="color:blue" %)**Query version number and frequency band 、TDC**(%%) ====
--The AT+COMMANDx and AT+DATACUTx settings are stored in special location, user can use below command to clear them.
++* (((
++(% style="color:#037691" %)**Downlink Payload:**
--* AT Command:
++**26 01  **  ~/~/ Downlink 26 01 can query device upload frequency, frequency band, software version number, TDC time.
++)))
--**AT+CMDEAR=mm,nn**   mm: start position of erase ,nn: stop position of erase
++Example：
--Etc. AT+CMDEAR=1,10 means erase AT+COMMAND1/AT+DATACUT1 to AT+COMMAND10/AT+DATACUT10
++[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LSN50%20%26%20LSN50-V2%20-%20LoRaWAN%20Sensor%20Node%20User%20Manual/WebHome/image-20220823173929-8.png?width=1205&height=76&rev=1.1||alt="image-20220823173929-8.png"]]
--Example screen shot after clear all RS485 commands.
++====   ====
++==== (% style="color:blue" %)** Monitor RS485 communication of other devices**(%%) ====
--The uplink screen shot is:
++* (((
++(% style="color:#037691" %)** AT Command:**
++)))
--[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png]]
++**~ AT+RXMODE=1,10**        ~/~/ When the RS485-LN receives more than 10 bytes from the RS485, it immediately sends the uplink of the received data.
++**~ AT+RXMODE=2,500    **  ~/~/RS485-LN uploads data as uplink from the first byte received by RS485 to the data received within 500ms after that.
--* Downlink Payload:
++ **AT+RXMODE=0,0  **        ~/~/Disable this mode (default)
--0x09 aa bb  same as AT+CMDEAR=aa,bb
++* (((
++(% style="color:#037691" %)**Downlink Payload:**
++)))
--==== Set Serial Communication Parameters ====
++**A6 aa bb bb                   ** ~/~/same as AT+RXMODE=aa,bb
--Set the Rs485 serial communication parameters:
++[[image:image-20220824144240-1.png]]
--* AT Command:
--Set Baud Rate:
--AT+BAUDR=9600    ~/~/ Options: (1200,2400,4800,14400,19200,115200)
++== 3.6 Listening mode for RS485 network ==
--Set UART parity
++(((
++This feature support since firmware v1.4
++)))
--AT+PARITY=0    ~/~/ Option: 0: no parity, 1: odd parity, 2: even parity
++(((
++RS485-LN supports listening mode, it can listen the RS485 network packets and send them via LoRaWAN uplink. Below is the structure. The blue arrow shows the RS485 network packets to RS485-LN.
++
++)))
--Set STOPBIT
++(% aria-label="image-20220602171200-8.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:image-20220602171200-8.png||data-widget="image" height="567" width="1007"]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %)
--AT+STOPBIT=0    ~/~/ Option: 0 for 1bit; 1 for 1.5 bit ; 2 for 2 bits
++(((
++To enable the listening mode, use can run the command AT+RXMODE.
++)))
++(((
++
++)))
--* Downlink Payload:
++(% border="1" cellspacing="10" style="background-color:#ffffcc; width:500px" %)
++|=(% style="width: 100px;" %)(((
++**Command example**
++)))|=(% style="width: 400px;" %)(((
++**Function**
++)))
++|(% style="width:100px" %)(((
++AT+RXMODE=1,10
++)))|(% style="width:400px" %)(((
++Enable listening mode 1, if RS485-LN has received more than 10 RS485 commands from the network. RS485-LN will send these commands via LoRaWAN uplinks.
++)))
++|(% style="width:100px" %)(((
++AT+RXMODE=2,500
++)))|(% style="width:400px" %)(((
++Enable listening mode 2, RS485-LN will capture and send a 500ms content once from the first detect of character. Max value is 65535 ms
++)))
++|(% style="width:100px" %)(((
++AT+RXMODE=0,0
++)))|(% style="width:400px" %)(((
++Disable listening mode. This is the default settings.
++)))
++|(% style="width:100px" %)(((
++
++)))|(% style="width:400px" %)(((
++A6 aa bb cc  same as AT+RXMODE=aa,(bb<<8 | cc)
++)))
--A7 01 aa bb: Same  AT+BAUDR=hex(aa bb)*100
++(((
++(% style="color:#037691" %)** Downlink Command:**
++)))
--Example:
++(((
++**0xA6 aa bb cc ** same as AT+RXMODE=aa,(bb<<8 | cc)
++)))
--* A7 01 00 60   same as AT+BAUDR=9600
--* A7 01 04 80     same as AT+BAUDR=115200
++(((
++
++)))
--A7 02 aa: Same as  AT+PARITY=aa  (aa value: 00 , 01 or 02)
++(((
++**Example**:
++)))
--A7 03 aa: Same as  AT+STOPBIT=aa  (aa value: 00 , 01 or 02)
++(((
++The RS485-LN is set to AT+RXMODE=2,1000
++)))
++(((
++There is a two Modbus commands in the RS485 network as below:
++)))
--==== Control output power duration ====
++(((
++The Modbus master send a command: (% style="background-color:#ffc000" %)01 03 00 00 00 02 c4 0b
++)))
--User can set the output power duration before each sampling.
++(((
++And Modbus slave reply with: (% style="background-color:green" %)01 03 04 00 00 00 00 fa 33
++)))
--* AT Command:
++(((
++RS485-LN will capture both and send the uplink: (% style="background-color:#ffc000" %)01 03 00 00 00 02 c4 0b  (% style="background-color:green" %)01 03 04 00 00 00 00 fa 33
++)))
--Example:
++(((
++(% aria-label="image-20220602171200-9.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:image-20220602171200-9.png||data-widget="image"]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %)
++)))
--AT+3V3T=1000 ~/~/ 3V3 output power will open 1s before each sampling.
++(((
++
++)))
--AT+5VT=1000 ~/~/ +5V output power will open 1s before each sampling.
++(((
++(((
++(% style="color:red" %)**Notice: Listening mode can work with the default polling mode of RS485-LN. When RS485-LN is in to send the RS485 commands (from AT+COMMANDx), the listening mode will be interrupt for a while.**
++)))
++)))
--* LoRaWAN Downlink Command:
--07 01 aa bb  Same as AT+5VT=(aa bb)
++== 3.7 Buttons ==
--07 02 aa bb  Same as AT+3V3T=(aa bb)
++(% border="1" cellspacing="10" style="background-color:#f7faff; width:430px" %)
++|=(% style="width: 50px;" %)**Button**|=(% style="width: 361px;" %)**Feature**
++|(% style="width:50px" %)**ACT**|(% style="width:361px" %)If RS485 joined in network, press this button for more than 1 second, RS485 will upload a packet, and the SYS LED will give a (% style="color:blue" %)**Blue blink**
++|(% style="width:50px" %)**RST**|(% style="width:361px" %)Reboot RS485
++|(% style="width:50px" %)**PRO**|(% style="width:361px" %)Use for upload image, see [[How to Update Image>>||anchor="H6.1Howtoupgradetheimage3F"]]
++== 3.8 LEDs ==
--1.
--11. Buttons
++(% border="1" cellspacing="10" style="background-color:#f7faff; width:430px" %)
++|=(% style="width: 50px;" %)**LEDs**|=(% style="width: 380px;" %)**Feature**
++|**PWR**|Always on if there is power
++|**SYS**|After device is powered on, the SYS will (% style="color:green" %)**fast blink in GREEN**(%%) for 5 times, means RS485-LN start to join LoRaWAN network. If join success, SYS will be (% style="color:green" %)**on GREEN for 5 seconds** (%%)**. **SYS will (% style="color:green" %)**blink Blue**(%%) on every upload and (% style="color:green" %)**blink Green**(%%) once receive a downlink message.
--|**Button**|**Feature**
--|**RST**|Reboot RS485-BL
++= 4. Case Study =
--1.
--11. +3V3 Output
--RS485-BL has a Controllable +3V3 output, user can use this output to power external sensor.
++User can check this URL for some case studies: [[APP RS485 COMMUNICATE WITH SENSORS>>doc:Main.Application Note \: Communicate with Different Sensors ----- RS485-LN  RS485-BL.WebHome]]
--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.
++= 5. Use 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.
++== 5.1 Access AT Command ==
--By default, the AT+3V3T=0. This is a special case, means the +3V3 output is always on at any time
++(((
++RS485-LN supports AT Command set. User can use a USB to TTL adapter plus the 3.5mm Program Cable to connect to RS485-LN to use AT command, as below.
++)))
++(% aria-label="1654162355560-817.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:1654162355560-817.png||data-widget="image"]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %)
--1.
--11. +5V Output
--RS485-BL has a Controllable +5V output, user can use this output to power external sensor.
++(((
++In PC, User needs to set (% style="color:blue" %)**serial tool**(%%)(such as [[putty>>url:https://www.chiark.greenend.org.uk/~~sgtatham/putty/latest.html]], SecureCRT) baud rate to (% style="color:green" %)**9600**(%%) to access to access serial console of RS485-LN. The default password is 123456. Below is the output for reference:
++)))
--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.
++(% aria-label="1654162368066-342.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:1654162368066-342.png||data-widget="image"]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %)
--The 5V output time can be controlled by AT Command.
++(((
++More detail AT Command manual can be found at [[AT Command Manual>>https://www.dragino.com/downloads/index.php?dir=LT_LoRa_IO_Controller/LT33222-L/]]
++)))
--**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.
++== 5.2 Common AT Command Sequence ==
--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.
++=== 5.2.1 Multi-channel ABP mode (Use with SX1301/LG308) ===
++If device has not joined network yet:
--1.
--11. LEDs
++* (% style="color:#037691" %)**AT+FDR**
++* (% style="color:#037691" %)**AT+NJM=0**
++* (% style="color:#037691" %)**ATZ**
--|**LEDs**|**Feature**
--|**LED1**|Blink when device transmit a packet.
++(((
++
--1.
--11. Switch Jumper
++If device already joined network:
--|**Switch Jumper**|**Feature**
--|**SW1**|(((
--ISP position: Upgrade firmware via UART
++* (% style="color:#037691" %)**AT+NJM=0**
++* (% style="color:#037691" %)**ATZ**
--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.
++=== 5.5.2 Single-channel ABP mode (Use with LG01/LG02) ===
--1. Case Study
--User can check this URL for some case studies.
++(% style="background-color:#dcdcdc" %)**AT+FDR** (%%)          Reset Parameters to Factory Default, Keys Reserve
--[[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]]
++(% style="background-color:#dcdcdc" %)**AT+NJM=0 **(%%)   Set to ABP mode
++(% style="background-color:#dcdcdc" %)**AT+ADR=0** (%%)   Set the Adaptive Data Rate Off
++(% style="background-color:#dcdcdc" %)**AT+DR=5**   (%%)   Set Data Rate
++(% style="background-color:#dcdcdc" %)**AT+TDC=60000** (%%)                 Set transmit interval to 60 seconds
--1. Use AT Command
--11. Access AT Command
++(% style="background-color:#dcdcdc" %)**AT+CHS=868400000**(%%)          Set transmit frequency to 868.4Mhz
--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.
++(% style="background-color:#dcdcdc" %)**AT+RX2FQ=868400000** (%%)     Set RX2Frequency to 868.4Mhz (according to the result from server)
--[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image027.png]]
++(% style="background-color:#dcdcdc" %)**AT+RX2DR=5**  (%%)                    Set RX2DR to match the downlink DR from server. see below
++(% style="background-color:#dcdcdc" %)**AT+DADDR=26** (%%)                  01 1A F1 Set Device Address to 26 01 1A F1, this ID can be found in the LoRa Server portal.
--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:
++(% style="background-color:#dcdcdc" %)**ATZ**       (%%)                                Reset MCU
--[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image028.png]]
++(% style="color:red" %)**Note:**
++(((
++(% style="color:red" %)1. Make sure the device is set to ABP mode in the IoT Server.
++2. Make sure the LG01/02 gateway RX frequency is exactly the same as AT+CHS setting.
++3. 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.
++4. 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
--More detail AT Command manual can be found at [[AT Command Manual>>path:#AT_COMMAND]]
++
++)))
++(% aria-label="1654162478620-421.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:1654162478620-421.png||data-widget="image"]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %)
--1.
--11. Common AT Command Sequence
--111. Multi-channel ABP mode (Use with SX1301/LG308)
--If device has not joined network yet:
++= 6. FAQ =
--AT+FDR
--AT+NJM=0
++== 6.1 How to upgrade the image? ==
--ATZ
++(((
++The RS485-LN LoRaWAN Controller is shipped with a 3.5mm cable, the cable is used to upload image to RS485-LN to:
++)))
--If device already joined network:
++* (((
++Support new features
++)))
++* (((
++For bug fix
++)))
++* (((
++Change LoRaWAN bands.
++)))
--AT+NJM=0
++(((
++Below shows the hardware connection for how to upload an image to RS485-LN:
++)))
--ATZ
++(% aria-label="1654162535040-878.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:1654162535040-878.png||data-widget="image"]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]]
--1.
--11.
--111. Single-channel ABP mode (Use with LG01/LG02)
++(% title="Click and drag to resize" %)
--AT+FDR   Reset Parameters to Factory Default, Keys Reserve
++(((
++(% style="color:blue" %)**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]].
++)))
--AT+NJM=0 Set to ABP mode
++(((
++(% style="color:blue" %)**Step2**(%%)**:** Download the [[LT Image files>>url:https://www.dropbox.com/sh/g99v0fxcltn9r1y/AACP33wo_ZQLsxW2MJ70oUoba/RS485-LN/Firmware?dl=0&subfolder_nav_tracking=1]].
++)))
--AT+ADR=0 Set the Adaptive Data Rate Off
++(((
++(% style="color:blue" %)**Step3**(%%)**: **Open flashloader; choose the correct COM port to update.
++)))
--AT+DR=5  Set Data Rate
++(((
++(((
++(((
++(% style="color:blue" %) Hold down the PRO button and then momentarily press the RST reset button and the SYS led will change from OFF to ON, While SYS LED is RED ON, it means the RS485-LN is ready to be program.
++)))
++)))
++)))
--AT+TDC=60000  Set transmit interval to 60 seconds
--AT+CHS=868400000 Set transmit frequency to 868.4Mhz
++(% aria-label="image-20220602175818-12.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:image-20220602175818-12.png||data-widget="image"]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %)
--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
++(% aria-label="image-20220602175848-13.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:image-20220602175848-13.png||data-widget="image"]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %)
--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
++(% aria-label="image-20220602175912-14.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:image-20220602175912-14.png||data-widget="image"]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %)
--**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
++(% style="color:red" %)**Notice**: **In case user has lost the program cable. User can hand made one from a 3.5mm cable. The pin mapping is:**
--[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image029.png]]
++(% aria-label="image-20220602175638-10.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:image-20220602175638-10.png||data-widget="image"]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %)
--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:
++== 6.2 How to change the LoRa Frequency Bands/Region? ==
--* Support new features
--* For bug fix
--* Change LoRaWAN bands.
--Below shows the hardware connection for how to upload an image to RS485-BL:
++User can follow the introduction for [[how to upgrade image>>||anchor="H6.1Howtoupgradetheimage3F"]]. When download the images, choose the required image file for download.
--[[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/]].
++== 6.3 How many RS485-Slave can RS485-LN connects? ==
--**Step3: **Open flashloader; choose the correct COM port to update.
++The RS485-LN can support max 32 RS485 devices. Each uplink command of RS485-LN can support max 16 different RS485 command. So RS485-LN 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>>||anchor="H3.3.3Configurereadcommandsforeachsampling"]].
--|(((
--HOLD PRO then press the RST button, SYS will be ON, then click next
--)))
--|(((
--Board detected
--)))
--|(((
--
--)))
++== 6.4 Compatible question to ChirpStack and TTI LoRaWAN server ? ==
--[[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]]
++When user need to use with ChirpStack or TTI. Please set AT+RPL=4.
++Detail info check this link: [[Set Packet Receiving Response Level>>doc:Main.End Device AT Commands and Downlink Command.WebHome||anchor="H7.23SetPacketReceivingResponseLevel"]]
--[[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]]
++== 6.5 Can i use point to point communication for RS485-LN? ==
--1.
--11. How to change the LoRa Frequency Bands/Region?
++Yes, please refer [[Point to Point Communication for RS485-LN>>Point to Point Communication for RS485-LN]].
--User can follow the introduction for [[how to upgrade image>>path:#upgrade_image]]. When download the images, choose the required image file for download.
++== 6.6 How to Use RS485-LN  to connect to RS232 devices? ==
--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]].
++[[Use RS485-BL or RS485-LN to connect to RS232 devices. - DRAGINO>>url:http://8.211.40.43:8080/xwiki/bin/view/Main/RS485%20to%20RS232/]]
++= 7. Trouble Shooting =
--1. Trouble Shooting
--11. Downlink doesn’t work, how to solve it?
--Please see this link for debug:
++== 7.1 Downlink doesn't work, how to solve it? ==
--[[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]]
++Please see this link for debug: [[LoRaWAN Communication Debug>>doc:Main.LoRaWAN Communication Debug.WebHome]]
--1.
--11. Why I can’t join TTN V3 in US915 /AU915 bands?
--It might about the channels mapping. Please see for detail.
++== 7.2 Why I can't join TTN V3 in US915 /AU915 bands? ==
--[[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]]
++It might about the channels mapping. Please see for detail: [[Notice of Frequency band>>doc:Main.LoRaWAN Communication Debug.WebHome||anchor="H2.NoticeofUS9152FCN4702FAU915Frequencyband"]]
--1. Order Info
--**Part Number: RS485-BL-XXX**
++= 8. Order Info =
--**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
++(% style="color:blue" %)**Part Number: RS485-LN-XXX**
--1. Packing Info
++(% style="color:blue" %)**XXX:**
++* (% style="color:red" %)**EU433**(%%):  frequency bands EU433
++* (% style="color:red" %)**EU868**(%%):  frequency bands EU868
++* (% style="color:red" %)**KR920**(%%):  frequency bands KR920
++* (% style="color:red" %)**CN470**(%%):  frequency bands CN470
++* (% style="color:red" %)**AS923**(%%):  frequency bands AS923
++* (% style="color:red" %)**AU915**(%%):  frequency bands AU915
++* (% style="color:red" %)**US915**(%%):  frequency bands US915
++* (% style="color:red" %)**IN865**(%%):   frequency bands IN865
++* (% style="color:red" %)**RU864**(%%):  frequency bands RU864
++* (% style="color:red" %)**KZ865**(%%):  frequency bands KZ865
++
++= 9.Packing Info =
++
++
  **Package Includes**:
--* RS485-BL x 1
++* RS485-LN x 1
  * Stick Antenna for LoRa RF part x 1
  * Program cable x 1
@@ -1202,9 +1202,68 @@
  * Package Size / pcs : 14.5 x 8 x 5 cm
  * Weight / pcs : 170g
--1. Support
++= 10. FCC Caution for RS485LN-US915 =
--* 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]]
++(((
++Any Changes or modifications not expressly approved by the party responsible for compliance could void the user's authority to operate the equipment.
++)))
++
++(((
++This device complies with part 15 of the FCC Rules. Operation is subject to the following two conditions: (1) This device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation.
++)))
++
++(((
++
++)))
++
++(((
++(% style="color:red" %)**IMPORTANT NOTE:**
++)))
++
++(((
++(% style="color:red" %)**Note: **(%%)This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses and can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications. However, there is no guarantee that interference will not occur in a particular installation. If this equipment does cause harmful interference to radio or television reception, which can be determined by turning the equipment off and on, the user is encouraged to try to correct the interference by one or more of the following measures:
++)))
++
++(((
++—Reorient or relocate the receiving antenna.
++)))
++
++(((
++—Increase the separation between the equipment and receiver.
++)))
++
++(((
++—Connect the equipment into an outlet on a circuit different from that to which the receiver is connected.
++)))
++
++(((
++—Consult the dealer or an experienced radio/TV technician for help.
++)))
++
++(((
++
++)))
++
++(((
++(% style="color:red" %)**FCC Radiation Exposure Statement:**
++)))
++
++(((
++This equipment complies with FCC radiation exposure limits set forth for an uncontrolled environment.This equipment should be installed and operated with minimum distance 20cm between the radiator& your body.
++)))
++
++
++
++= 11. 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]].
++
++
++
++)))

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

1654160691922-496.png

Author

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

Size

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

Content

1654162355560-817.png

Author

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

Size

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

Content

1654162368066-342.png

Author

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

Size

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

Content

1654162478620-421.png

Author

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

Size

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

Content

1654162535040-878.png

Author

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

Size

...	...	@@ -1,0 +1,1 @@
	1	+670.0 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

image-20220602171200-8.png

Author

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

Size

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

Content

image-20220602171200-9.png

Author

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

Size

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

Content

image-20220602175638-10.png

Author

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

Size

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

Content

image-20220602175743-11.png

Author

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

Size

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

Content

image-20220602175818-12.png

Author

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

Size

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

Content

image-20220602175848-13.png

Author

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

Size

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

Content

image-20220602175912-14.png

Author

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

Size

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

Content

image-20220606110929-1.png

Author

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

Size

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

Content

image-20220824144240-1.png

Author

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

Size

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

Content

image-20220824145428-2.png

Author

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

Size

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

Content

image-20220824145428-3.png

Author

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

Size

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

Content