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

Last modified by Karry Zhuang on 2025/03/06 16:34

From version < 57.3 >

edited by Xiaoling
on 2022/06/06 08:41

To version < 58.19 >

edited by Xiaoling
on 2022/06/06 11:24

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (1 modified, 0 added, 0 removed)
Attachments (0 modified, 1 added, 0 removed)
- image-20220606110929-1.png

Details

Page properties

Content

@@ -6,12 +6,18 @@
  **RS485-LN – RS485 to LoRaWAN Converter User Manual**
++
++
  **Table of Contents:**
++{{toc/}}
++
++
++
  = 1.Introduction =
  == 1.1 What is RS485-LN RS485 to LoRaWAN Converter ==
@@ -18,23 +18,33 @@
  (((
  (((
++(((
  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"]]
@@ -76,8 +76,6 @@
  * Automatic RF Sense and CAD with ultra-fast AFC.
  * Packet engine up to 256 bytes with CRC
--
--
  == 1.3 Features ==
  * LoRaWAN Class A & Class C protocol (default Class C)
@@ -90,7 +90,6 @@
  * Support Interrupt uplink (Since hardware version v1.2)
--
  == 1.4 Applications ==
  * Smart Buildings & Home Automation
@@ -100,6 +100,7 @@
  * Smart Cities
  * Smart Factory
++
  == 1.5 Firmware Change log ==
  [[RS485-LN Image files – Download link and Change log>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/]]
@@ -109,9 +109,13 @@
  (((
  (((
++(((
  v1.2: Add External Interrupt Pin.
++)))
++(((
  v1.0: Release
++)))
  )))
@@ -139,7 +139,9 @@
  == 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.
++)))
  )))
@@ -163,7 +163,7 @@
  [[image:1653268227651-549.png||height="592" width="720"]]
  (((
--The LG308 is already set to connect to [[TTN V3 network >>path:eu1.cloud.thethings.network/]]. So what we need to now is only configure the TTN V3:
++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:
  )))
  (((
@@ -215,7 +215,7 @@
  (((
  (((
--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-BLviaATorDownlink"]] or LoRaWAN Downlink Command to configure what commands RS485-LN should send for each sampling and how to handle the return from RS485 devices.
  )))
  (((
@@ -229,19 +229,19 @@
  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
  )))
@@ -250,11 +250,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
  )))
@@ -263,9 +263,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)
  )))
@@ -273,7 +273,7 @@
  (((
  )))
--)))|(% style="width:346px" %)(((
++)))|(% style="width:190px" %)(((
  (((
  AT+STOPBIT=0 for 1bit
  )))
@@ -287,6 +287,8 @@
  )))
  )))
++
++
  === 3.3.2 Configure sensors ===
  (((
@@ -295,16 +295,18 @@
  )))
  )))
--(% 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 ===
  (((
@@ -350,8 +350,8 @@
  **AT+DATACUTx : **This command defines how to handle the return from AT+COMMANDx, max return length is 45 bytes.
--(% border="1" style="background-color:#4bacc6; color:white; width:725px" %)
--|(% style="width:722px" %)(((
++(% 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**
@@ -420,6 +420,7 @@
  (% style="color:#4f81bd" %)**Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA**
++
 . PAYVER: Defined by AT+PAYVER
 . PAYLOAD COUNT: Total how many uplinks of this sampling.
 . PAYLOAD#: Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT)
@@ -476,33 +476,35 @@
  == 3.4 Uplink Payload ==
--(% border="1" style="background-color:#4bacc6; color:white; width:734px" %)
--|**Size(bytes)**|(% style="width:120px" %)**2**|(% style="width:116px" %)**1**|(% style="width:386px" %)**Length depends on the return from the commands**
--|Value|(% style="width:120px" %)(((
--Battery(mV)
--&
++[[image:image-20220606110929-1.png]]
--Interrupt _Flag
--)))|(% style="width:116px" %)(((
--PAYLOAD_VER
--
--
--)))|(% style="width:386px" %)If the valid payload is too long and exceed the maximum support payload length in server, server will show payload not provided in the LoRaWAN server.
--
  Below is the decoder for the first 3 bytes. The rest bytes are dynamic depends on different RS485 sensors.
  == 3.5 Configure RS485-BL via AT or Downlink ==
++(((
  User can configure RS485-LN via AT Commands or LoRaWAN Downlink Commands
++)))
++(((
  There are two kinds of Commands:
++)))
--* (% style="color:#4f81bd" %)**Common Commands**(%%): They should be available for each sensor, such as: change uplink interval, reset device. For firmware v1.3, user can find what common commands it supports: [[End Device AT Commands and Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]]
++* (((
++(% 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]]
++)))
--* (% style="color:#4f81bd" %)**Sensor Related Commands**(%%): These commands are special designed for RS485-LN.  User can see these commands below:
++* (((
++(% style="color:#4f81bd" %)**Sensor Related Commands**(%%): These commands are special designed for RS485-LN.  User can see these commands below:
++)))
++(((
++
++)))
++
++
  === 3.5.1 Common Commands ===
  They should be available for each of Dragino Sensors, such as: change uplink interval, reset device. For firmware v1.3, user can find what common commands it supports: [[End Device AT Commands and Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]]
@@ -519,144 +519,284 @@
  === 3.5.3 Sensor related commands ===
--====   ====
++
++
  ==== **RS485 Debug Command** ====
++(((
  This command is used to configure the RS485 devices; they won’t be used during sampling.
++)))
--* **AT Command**
++* (((
++**AT Command**
++)))
  (% class="box infomessage" %)
  (((
++(((
  **AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m**
  )))
++)))
++(((
  m: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
++)))
--* **Downlink Payload**
++* (((
++**Downlink Payload**
++)))
++(((
  Format: A8 MM NN XX XX XX XX YY
++)))
++(((
  Where:
++)))
--* 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-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.
++* (((
++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-LN will execute the downlink command without uplink;
++)))
++* (((
++if YY>0, RS485-LN will uplink total YY bytes from the output of this RS485 command; Fport=200
++)))
++* (((
++if YY=FF, RS485-LN will uplink RS485 output with the downlink command content; Fport=200.
++)))
++)))
++
++(((
  **Example 1** ~-~-> Configure without ask for uplink (YY=0)
++)))
++(((
  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 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.
++* (((
++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:#4f81bd" %)**A8 01 06 0A 05 00 04 00 01 00**(%%): to activate the RS485 Alarm
++)))
++(((
  (% style="color:#4f81bd" %)**A8 01 06 0A 05 00 04 00 00 00**(%%): to deactivate the RS485 Alarm
++)))
++(((
  A8 is type code and 01 means add CRC-16/MODBUS at the end, the 3^^rd^^ byte is 06, means the next 6 bytes are the command to be sent to the RS485 network, the final byte 00 means this command don’t need to acquire output.
++)))
++(((
++
++)))
++(((
  **Example 2** ~-~-> Configure with requesting uplink and original downlink command (**YY=FF**)
++)))
++(((
  User in IoT server send a downlink command: (% style="color:#4f81bd" %)**A8 01 06 0A 08 00 04 00 01 YY**
++)))
++(((
++
++)))
++(((
  RS485-LN got this downlink command and send (% style="color:#4f81bd" %)**0A 08 00 04 00 01 **(%%)to Modbus network. One of the RS485 sensor in the network send back Modbus reply **0A 08 00 04 00 00**. RS485-LN get this reply and combine with the original downlink command and uplink. The uplink message is:
++)))
++(((
     **A8** (% style="color:#4f81bd" %)**0A 08 00 04 00  **(% style="color:red" %)**01 06** ** **(% style="color:green" %)**0A 08 00 04 00 00**
++)))
++(((
   [[image:1654159460680-153.png]]
++)))
++
  ==== **Set Payload version** ====
++(((
  This is the first byte of the uplink payload. RS485-BL can connect to different sensors. User can set the PAYVER field to tell server how to decode the current payload.
++)))
--* **AT Command:**
++* (((
++**AT Command:**
++)))
  (% class="box infomessage" %)
  (((
++(((
  **AT+PAYVER: Set PAYVER field = 1**
  )))
++)))
--* **Downlink Payload:**
++* (((
++**Downlink Payload:**
++)))
++(((
  **0xAE 01**   ~-~-> Set PAYVER field =  0x01
++)))
++(((
  **0xAE 0F**   ~-~-> Set PAYVER field =  0x0F
++)))
++
  ==== **Set RS485 Sampling Commands** ====
++(((
  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"]].
++)))
++(((
++
++)))
--* **AT Command:**
++* (((
++**AT Command:**
++)))
  (% class="box infomessage" %)
  (((
++(((
  **AT+COMMANDx: Configure RS485 read command to sensor.**
  )))
++)))
  (% class="box infomessage" %)
  (((
++(((
  **AT+DATACUTx: Configure how to handle return from RS485 devices.**
  )))
++)))
++(((
++
++)))
--* **Downlink Payload:**
++* (((
++**Downlink Payload:**
++)))
++(((
  **0xAF** downlink command can be used to set AT+COMMANDx or AT+DATACUTx.
++)))
++(((
  (% style="color:red" %)**Note**(%%): if user use AT+COMMANDx to add a new command, he also need to send AT+DATACUTx downlink.
++)))
++(((
  Format: AF MM NN LL XX XX XX XX YY
++)))
++(((
  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-LN will execute an uplink after got this command.
++* (((
++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-LN will execute an uplink after got this command.
++)))
++(((
  **Example:**
++)))
++(((
  (% 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
++)))
++(((
  (% 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**
++)))
++(((
  (% 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**
++)))
++
  ==== **Fast command to handle MODBUS device** ====
++(((
  AT+MBFUN is valid since v1.3 firmware version. The command is for fast configure to read Modbus devices. It is only valid for the devices which follow the [[MODBUS-RTU protocol>>url:https://www.modbustools.com/modbus.html]].
++)))
++(((
  This command is valid since v1.3 firmware version
++)))
++(((
  AT+MBFUN 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.
++* (((
++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.
++)))
  [[image:image-20220602165351-6.png]]
@@ -664,145 +664,260 @@
++
  ==== **RS485 command timeout** ====
++(((
  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.
++)))
++(((
  Default value: 0, range:  0 ~~ 65 seconds
++)))
--* **AT Command:**
++* (((
++**AT Command:**
++)))
  (% class="box infomessage" %)
  (((
++(((
  **AT+CMDDLaa=hex(bb cc)*1000**
  )))
++)))
++(((
  **Example:**
++)))
++(((
  **AT+CMDDL1=1000** to send the open time to 1000ms
++)))
++(((
++
++)))
--* **Downlink Payload:**
++* (((
++**Downlink Payload:**
++)))
++(((
  **0x AA aa bb cc**
++)))
++(((
  Same as: AT+CMDDLaa=hex(bb cc)*1000
++)))
++(((
     **Example:**
++)))
++(((
 xAA 01 00 01  ~-~-> Same as **AT+CMDDL1=1000 ms**
++)))
++
  ==== **Uplink payload mode** ====
++(((
  Define to use one uplink or multiple uplinks for the sampling.
++)))
++(((
  The use of this command please see: [[Compose Uplink payload>>||anchor="H3.3.4Composetheuplinkpayload"]]
++)))
--* **AT Command:**
++* (((
++**AT Command:**
++)))
  (% class="box infomessage" %)
  (((
++(((
  **AT+DATAUP=0**
  )))
++)))
  (% class="box infomessage" %)
  (((
++(((
  **AT+DATAUP=1**
  )))
++)))
++(((
++
++)))
--* **Downlink Payload:**
++* (((
++**Downlink Payload:**
++)))
++(((
  **0xAD 00**   **~-~->** Same as AT+DATAUP=0
++)))
++(((
  **0xAD 01**   **~-~->** Same as AT+DATAUP=1
++)))
++
  ==== **Manually trigger an Uplink** ====
++(((
  Ask device to send an uplink immediately.
++)))
--* **AT Command:**
++* (((
++**AT Command:**
++)))
--No AT Command for this, user can press the [[ACT button>>path:#Button]] for 1 second for the same.
++(((
++No AT Command for this, user can press the [[ACT button>>||anchor="H3.7Buttons"]] for 1 second for the same.
++)))
++(((
++
++)))
--* **Downlink Payload:**
++* (((
++**Downlink Payload:**
++)))
++(((
  **0x08 FF**, RS485-LN will immediately send an uplink.
++)))
--====   ====
++
  ==== **Clear RS485 Command** ====
++(((
  The AT+COMMANDx and AT+DATACUTx settings are stored in special location, user can use below command to clear them.
++)))
--* **AT Command:**
++* (((
++**AT Command:**
++)))
++(((
  **AT+CMDEAR=mm,nn**   mm: start position of erase ,nn: stop position of erase
++)))
++(((
  Etc. AT+CMDEAR=1,10 means erase AT+COMMAND1/AT+DATACUT1 to AT+COMMAND10/AT+DATACUT10
++)))
++(((
  Example screen shot after clear all RS485 commands.
++)))
++(((
++
++)))
++(((
  The uplink screen shot is:
++)))
--[[image:1654160691922-496.png]][[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image001.png]]
++[[image:1654160691922-496.png]]
--* **Downlink Payload:**
++* (((
++**Downlink Payload:**
++)))
++(((
  **0x09 aa bb**  same as AT+CMDEAR=aa,bb
++)))
++
  ==== **Set Serial Communication Parameters** ====
++(((
  Set the Rs485 serial communication parameters:
++)))
--* **AT Command:**
++* (((
++**AT Command:**
++)))
++(((
  Set Baud Rate:
++)))
  (% class="box infomessage" %)
  (((
++(((
  **AT+BAUDR=9600**    ~/~/ Options: (1200,2400,4800,14400,19200,115200)
  )))
++)))
++(((
  Set UART Parity
++)))
  (% class="box infomessage" %)
  (((
++(((
  **AT+PARITY=0**    ~/~/ Option: 0: no parity, 1: odd parity, 2: even parity
  )))
++)))
++(((
  Set STOPBIT
++)))
  (% class="box infomessage" %)
  (((
++(((
  **AT+STOPBIT=0**    ~/~/ Option: 0 for 1bit; 1 for 1.5 bit ; 2 for 2 bits
  )))
++)))
++(((
++
++)))
--* **Downlink Payload:**
++* (((
++**Downlink Payload:**
++)))
++(((
  **A7 01 aa bb**: Same  AT+BAUDR=hex(aa bb)*100
++)))
++(((
  **Example:**
++)))
--* A7 01 00 60   same as AT+BAUDR=9600
--* A7 01 04 80     same as AT+BAUDR=115200
++* (((
++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)
++)))
++(((
  A7 03 aa: Same as  AT+STOPBIT=aa  (aa value: 00 , 01 or 02)
++)))
++
++
  == 3.6 Listening mode for RS485 network ==
  This feature support since firmware v1.4
@@ -851,7 +851,7 @@
  |=**Button**|=(% style="width: 1420px;" %)**Feature**
  |**ACT**|(% style="width:1420px" %)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**
  |**RST**|(% style="width:1420px" %)Reboot RS485
--|**PRO**|(% style="width:1420px" %)Use for upload image, see [[How to Update Image>>path:#upgrade_image]]
++|**PRO**|(% style="width:1420px" %)Use for upload image, see [[How to Update Image>>||anchor="H6.1Howtoupgradetheimage3F"]]
  == 3.8 LEDs ==
@@ -879,7 +879,7 @@
  [[image:1654162368066-342.png]]
--More detail AT Command manual can be found at [[AT Command Manual>>||anchor="3.5ConfigureRS485-BLviaATorDownlink"]]
++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/]]
  == 5.2 Common AT Command Sequence ==
@@ -971,7 +971,9 @@
  **Step3: **Open flashloader; choose the correct COM port to update.
++(((
  (% 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.
++)))
  [[image:image-20220602175818-12.png]]
@@ -1034,6 +1034,7 @@
  * (% style="color:blue" %)**RU864**(%%): frequency bands RU864
  * (% style="color:blue" %)**KZ865**(%%): frequency bands KZ865
++
  = 9.Packing Info =
@@ -1050,32 +1050,63 @@
  * Package Size / pcs : 14.5 x 8 x 5 cm
  * Weight / pcs : 170g
++
  = 10. FCC Caution for RS485LN-US915 =
++(((
  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.
++)))
++(((
++
++)))
++(((
  **IMPORTANT NOTE:**
++)))
++(((
  **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.
++)))
++(((
++
++)))
++(((
  **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]].
++* (((
++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]].
++)))

image-20220606110929-1.png

Author

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

Size

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

Content

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

Summary

Details

Applications

Navigation