Changes for page RS485-BL – Waterproof RS485 to LoRaWAN Converter

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

From 40.24 to 40.25 From 44.11 to 44.12

From version 40.25

edited by Xiaoling
on 2022/06/06 09:46

Change comment: There is no comment for this version

To version 44.11

edited by Xiaoling
on 2022/06/14 10:05

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-20220606105412-1.png

Details

Page properties

Content

@@ -1,13 +1,9 @@
  (% style="text-align:center" %)
--[[image:1652947681187-144.png||height="385" width="385"]]
++[[image:1652947681187-144.png||height="404" width="404"]]
--**RS485-BL – Waterproof RS485 to LoRaWAN Converter User Manual**
--
--
--
  **Table of Contents:**
  {{toc/}}
@@ -67,6 +67,7 @@
  ** Idle: 6uA@3.3v
  ** 20dB Transmit: 130mA@3.3v
++
  **Interface for Model:**
  * 1 x RS485 Interface
@@ -76,6 +76,7 @@
  * 1 x Interrupt Interface
  * 1 x Controllable 5V output, max
++
  **LoRa Spec:**
  * Frequency Range:
@@ -96,6 +96,7 @@
++
  == 1.3 Features ==
  * LoRaWAN Class A & Class C protocol (default Class A)
@@ -109,6 +109,7 @@
++
  == 1.4 Applications ==
  * Smart Buildings & Home Automation
@@ -120,6 +120,7 @@
++
  == 1.5 Firmware Change log ==
  [[RS485-BL Image files – Download link and Change log>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/RS485-BL/Firmware/||style="background-color: rgb(255, 255, 255);"]]
@@ -130,29 +130,47 @@
  (((
++(((
  v1.4
  )))
++)))
  (((
++(((
  ~1. Change Power IC to TPS22916
  )))
++)))
++(((
++
++)))
  (((
++(((
  v1.3
  )))
++)))
  (((
++(((
  ~1. Change JP3 from KF350-8P to KF350-11P, Add one extra interface for I2C and one extra interface for one-wire
  )))
++)))
++(((
++
++)))
  (((
++(((
  v1.2
  )))
++)))
  (((
++(((
  Release version
++)))
  )))
@@ -185,6 +185,7 @@
  [[image:1652953414711-647.png||height="337" width="723"]]
++
  (((
  The RS485-BL in this example connected to two RS485 devices for demonstration, user can connect to other RS485 devices via the same method.
  )))
@@ -194,7 +194,7 @@
  )))
  (((
--**Step 1**: Create a device in TTN V3 with the OTAA keys from RS485-BL.
++**(% style="color:blue" %)Step 1**(%%): Create a device in TTN V3 with the OTAA keys from RS485-BL.
  )))
  (((
@@ -203,12 +203,13 @@
  [[image:1652953462722-299.png]]
++
  (((
  User can enter this key in their LoRaWAN Server portal. Below is TTN V3 screen shot:
  )))
  (((
--Add APP EUI in the application.
++**Add APP EUI in the application.**
  )))
@@ -220,17 +220,20 @@
  [[image:image-20220519174512-4.png]]
++
  You can also choose to create the device manually.
  [[image:1652953542269-423.png||height="710" width="723"]]
++
  Add APP KEY and DEV EUI
  [[image:1652953553383-907.png||height="514" width="724"]]
++
  (((
--**Step 2**: Power on RS485-BL and it will auto join to the TTN V3 network. After join success, it will start to upload message to TTN V3 and user can see in the panel.
++**(% style="color:blue" %)Step 2**(%%): Power on RS485-BL and it will auto join to the TTN V3 network. After join success, it will start to upload message to TTN V3 and user can see in the panel.
  )))
  [[image:1652953568895-172.png||height="232" width="724"]]
@@ -246,84 +246,130 @@
  === 3.3.1 onfigure UART settings for RS485 or TTL communication ===
++(((
  RS485-BL can connect to either RS485 sensors or TTL sensor. User need to specify what type of sensor need to connect.
++)))
++(((
  **~1. RS485-MODBUS mode:**
++)))
++(((
  AT+MOD=1 ~/~/ Support RS485-MODBUS type sensors. User can connect multiply RS485 , Modbus sensors to the A / B pins.
++)))
++(((
  **2. TTL mode:**
++)))
++(((
  AT+MOD=2 ~/~/ Support TTL Level sensors, User can connect one TTL Sensor to the TXD/RXD/GND pins.
++)))
++(((
  RS485-BL default UART settings is **9600, no parity, stop bit 1**. If the sensor has a different settings, user can change the RS485-BL setting to match.
++)))
--(% border="1" style="background-color:#ffffcc; color:green; width:795px" %)
--|(((
++(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)
++|=(% style="width: 80px;" %)(((
++(((
  **AT Commands**
--)))|(% style="width:285px" %)(((
++)))
++)))|=(% style="width: 210px;" %)(((
++(((
  **Description**
--)))|(% style="width:347px" %)(((
++)))
++)))|=(% style="width: 210px;" %)(((
++(((
  **Example**
  )))
--|(((
++)))
++|(% style="width:80px" %)(((
++(((
  AT+BAUDR
--)))|(% style="width:285px" %)(((
++)))
++)))|(% style="width:210px" %)(((
++(((
  Set the baud rate (for RS485 connection). Default Value is: 9600.
--)))|(% style="width:347px" %)(((
++)))
++)))|(% style="width:210px" %)(((
  (((
++(((
  AT+BAUDR=9600
  )))
++)))
  (((
++(((
  Options: (1200,2400,4800,14400,19200,115200)
  )))
  )))
--|(((
++)))
++|(% style="width:80px" %)(((
++(((
  AT+PARITY
--)))|(% style="width:285px" %)(((
++)))
++)))|(% style="width:210px" %)(((
  (((
++(((
  Set UART parity (for RS485 connection)
  )))
++)))
  (((
++(((
  Default Value is: no parity.
  )))
--)))|(% style="width:347px" %)(((
++)))
++)))|(% style="width:210px" %)(((
  (((
++(((
  AT+PARITY=0
  )))
++)))
  (((
++(((
  Option: 0: no parity, 1: odd parity, 2: even parity
  )))
  )))
--|(((
++)))
++|(% style="width:80px" %)(((
++(((
  AT+STOPBIT
--)))|(% style="width:285px" %)(((
++)))
++)))|(% style="width:210px" %)(((
  (((
++(((
  Set serial stopbit (for RS485 connection)
  )))
++)))
  (((
++(((
  Default Value is: 1bit.
  )))
--)))|(% style="width:347px" %)(((
++)))
++)))|(% style="width:210px" %)(((
  (((
++(((
  AT+STOPBIT=0 for 1bit
  )))
++)))
  (((
++(((
  AT+STOPBIT=1 for 1.5 bit
  )))
++)))
  (((
++(((
  AT+STOPBIT=2 for 2 bits
  )))
  )))
++)))
--
--
  === 3.3.2 Configure sensors ===
  (((
@@ -334,19 +334,26 @@
  When user issue an (% style="color:#4f81bd" %)**AT+CFGDEV**(%%) command, Each (% style="color:#4f81bd" %)**AT+CFGDEV**(%%) equals to send a command to the RS485 or TTL sensors. This command will only run when user input it and won’t run during each sampling.
  )))
--(% border="1" style="background-color:#ffffcc; color:green; width:806px" %)
--|**AT Commands**|(% style="width:418px" %)**Description**|(% style="width:256px" %)**Example**
--|AT+CFGDEV|(% style="width:418px" %)(((
++(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)
++|=(% style="width: 80px;" %)**AT Commands**|=(% style="width: 210px;" %)**Description**|=(% style="width: 210px;" %)**Example**
++|AT+CFGDEV|(% style="width:80px" %)(((
++(((
  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:210px" %)AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
  Detail of AT+CFGDEV command see [[AT+CFGDEV detail>>||anchor="HRS485DebugCommand28AT2BCFGDEV29"]].
++
  === 3.3.3 Configure read commands for each sampling ===
  (((
@@ -413,117 +413,213 @@
  After we got the valid value from each RS485 commands, we need to combine them together with the command **AT+DATAUP**.
  )))
++(((
  **Examples:**
++)))
++(((
  Below are examples for the how above AT Commands works.
++)))
++(((
  **AT+COMMANDx : **This command will be sent to RS485/TTL devices during each sampling, Max command length is 14 bytes. The grammar is:
++)))
--(% border="1" class="table-bordered" style="background-color:#4f81bd; color:white; width:501px" %)
++(% border="1" class="table-bordered" style="background-color:#4f81bd; color:white; width:500px" %)
  |(% style="width:498px" %)(((
++(((
  **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**
  )))
++)))
++(((
  For example, if we have a RS485 sensor. The command to get sensor value is: 01 03 0B B8 00 02 46 0A. Where 01 03 0B B8 00 02 is the Modbus command to read the register 0B B8 where stored the sensor value. The 46 0A is the CRC-16/MODBUS which calculate manually.
++)))
++(((
  In the RS485-BL, we should use this command AT+COMMAND1=01 03 0B B8 00 02,1 for the same.
++)))
++(((
++
++)))
++
++(((
  **AT+SEARCHx**: This command defines how to handle the return from AT+COMMANDx.
++)))
--(% border="1" class="table-bordered" style="background-color:#4f81bd; color:white; width:580px" %)
++(% border="1" class="table-bordered" style="background-color:#4f81bd; color:white; width:500px" %)
  |(% style="width:577px" %)(((
++(((
  **AT+SEARCHx=aa,xx xx xx xx xx**
++)))
--* **aa: 1: prefix match mode; 2: prefix and suffix match mode**
--* **xx xx xx xx xx: match string. Max 5 bytes for prefix and 5 bytes for suffix**
++* (((
++**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:**
++)))
++(((
 ）For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
++)))
++(((
  If we set AT+SEARCH1=1,1E 56 34.      (max 5 bytes for prefix)
++)))
++(((
  The valid data will be all bytes after 1E 56 34 , so it is (% style="background-color:yellow" %)**2e 30 58 5f 36 41 30 31 00 49**
++)))
++(((
  [[image:1653271044481-711.png]]
++)))
++(((
 ）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**
++)))
++(((
  [[image:1653271276735-972.png]]
++)))
++(((
  **AT+DATACUTx : **This command defines how to handle the return from AT+COMMANDx, max return length is 45 bytes.
++)))
--(% style="background-color:#4f81bd; color:white; width:729px" %)
++(% style="background-color:#4f81bd; color:white; width:510px" %)
  |(% style="width:726px" %)(((
++(((
  **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.  **
++* (((
++**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.  **
++)))
++)))
++(((
  **Examples:**
++)))
--* Grab bytes:
++* (((
++Grab bytes:
++)))
++(((
  [[image:1653271581490-837.png||height="313" width="722"]]
++)))
++(((
++
++)))
--* Grab a section.
++* (((
++Grab a section.
++)))
++(((
  [[image:1653271648378-342.png||height="326" width="720"]]
++)))
++(((
++
++)))
--* Grab different sections.
++* (((
++Grab different sections.
++)))
++(((
  [[image:1653271657255-576.png||height="305" width="730"]]
++)))
  (((
++(((
  (% 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.
  )))
++)))
  (((
++(((
  **Example:**
  )))
++)))
  (((
++(((
  (% style="color:red" %)AT+COMMAND1=11 01 1E D0,0
  )))
++)))
  (((
++(((
  (% style="color:red" %)AT+SEARCH1=1,1E 56 34
  )))
++)))
  (((
++(((
  (% style="color:red" %)AT+DATACUT1=0,2,1~~5
  )))
++)))
  (((
++(((
  (% style="color:red" %)Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
  )))
++)))
  (((
++(((
  (% style="color:red" %)String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49
  )))
++)))
  (((
++(((
  (% style="color:red" %)Valid payload after DataCUT command: 2e 30 58 5f 36
  )))
++)))
++(((
  [[image:1653271763403-806.png]]
++)))
  === 3.3.4 Compose the uplink payload ===
@@ -530,10 +530,14 @@
  (((
  Through AT+COMMANDx and AT+DATACUTx we got valid value from each RS485 commands, Assume these valid value are RETURN1, RETURN2, .., to RETURNx. The next step is how to compose the LoRa Uplink Payload by these RETURNs. The command is **AT+DATAUP.**
++
++
  )))
  (((
  (% style="color:#037691" %)**Examples: AT+DATAUP=0**
++
++
  )))
  (((
@@ -666,26 +666,8 @@
  == 3.4 Uplink Payload ==
--(% border="1" style="background-color:#4f81bd; color:white; width:850px" %)
--|**Size(bytes)**|(% style="width:130px" %)**2**|(% style="width:93px" %)**1**|(% style="width:509px" %)**Length depends on the return from the commands**
--|Value|(% style="width:130px" %)(((
--(((
--Battery(mV)
--)))
++[[image:image-20220606105412-1.png]]
--(((
--&
--)))
--
--(((
--Interrupt _Flag
--)))
--)))|(% style="width:93px" %)(((
--PAYLOAD_VER
--
--
--)))|(% style="width:509px" %)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.
  (((
@@ -743,16 +743,22 @@
  == 3.5 Configure RS485-BL via AT or Downlink ==
++(((
  User can configure RS485-BL 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: [[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-BL.  User can see these commands below:
++* (((
++(% style="color:#4f81bd" %)**Sensor Related Commands**(%%): These commands are special designed for RS485-BL.  User can see these commands below:
++)))
--
--
  === 3.5.1 Common Commands: ===
  They should be available for each of Dragino Sensors, such as: change uplink interval, reset device. For firmware v1.3, user can find what common commands it supports: [[End Device AT Commands and Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]]
@@ -761,6 +761,7 @@
  === 3.5.2 Sensor related commands: ===
++
  ==== **Choose Device Type (RS485 or TTL)** ====
  RS485-BL can connect to either RS485 sensors or TTL sensor. User need to specify what type of sensor need to connect.
@@ -784,57 +784,109 @@
++
  ==== **RS485 Debug Command (AT+CFGDEV)** ====
++(((
  This command is used to configure the RS485 or TTL sensors; 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-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
++* (((
++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:**
++)))
++(((
  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:#037691" %)**A8 01 06 0A 05 00 04 00 01 00**(%%): to activate the RS485 Alarm
++)))
++(((
  (% style="color:#037691" %)**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:**
++)))
++(((
  Check TTL Sensor return:
++)))
++(((
  [[image:1654132684752-193.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.
@@ -855,87 +855,171 @@
++
  ==== **Set RS485 Sampling Commands** ====
++(((
  AT+COMMANDx, AT+DATACUTx and AT+SEARCHx
++)))
++(((
  These three commands are used to configure how the RS485-BL polling data from Modbus device. Detail of usage please see : [[polling RS485 device>>||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.**
  )))
++)))
  (% class="box infomessage" %)
  (((
++(((
  **AT+SEARCHx: Configure search command**
  )))
++)))
++(((
++
++)))
--* **Downlink Payload:**
++* (((
++**Downlink Payload:**
++)))
++(((
  **0xAF** downlink command can be used to set AT+COMMANDx or AT+DATACUTx.
++)))
++(((
  (% 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-BL 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-BL 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**
++)))
++(((
++
++)))
++(((
  **0xAB** downlink command can be used for set AT+SEARCHx
++)))
++(((
  **Example:** **AB aa 01 03 xx xx xx** (03 here means there are total 3 bytes after 03) So
++)))
--* 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
++* (((
++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
++)))
++(((
  **AB aa 02 03 xx xx xx 02 yy yy**  same as **AT+SEARCHaa=2,xx xx xx+yy yy**
++)))
++
  ==== **Fast command to handle MODBUS device** ====
++(((
  AT+MBFUN is valid since v1.3 firmware version. The command is for fast configure to read Modbus devices. It is only valid for the devices which follow the [[MODBUS-RTU protocol>>url:https://www.modbustools.com/modbus.html]].
++)))
++(((
  This command is valid since v1.3 firmware version
++)))
++(((
++
++)))
++(((
  **AT+MBFUN has only two value:**
++)))
--* **AT+MBFUN=1**: Enable Modbus reading. And get response base on the MODBUS return
++* (((
++**AT+MBFUN=1**: Enable Modbus reading. And get response base on the MODBUS return
++)))
++(((
  AT+MBFUN=1, device can auto read the Modbus function code: 01, 02, 03 or 04. AT+MBFUN has lower priority vs AT+DATACUT command. If AT+DATACUT command is configured, AT+MBFUN will be ignore.
++)))
--* **AT+MBFUN=0**: Disable Modbus fast reading.
++* (((
++**AT+MBFUN=0**: Disable Modbus fast reading.
++)))
++(((
  **Example:**
++)))
--* 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.
++* (((
++AT+MBFUN=1 and AT+DATACUT1/AT+DATACUT2 are not configure (0,0,0).
++)))
++* (((
++AT+COMMAND1= 01 03 00 10 00 08,1 ~-~-> read slave address 01 , function code 03, start address 00 01, quantity of registers 00 08.
++)))
++* (((
++AT+COMMAND2= 01 02 00 40 00 10,1 ~-~-> read slave address 01 , function code 02, start address 00 40, quantity of inputs 00 10.
++)))
  [[image:1654133913295-597.png]]
@@ -943,67 +943,120 @@
  [[image:1654133954153-643.png]]
--* **Downlink Commands:**
++* (((
++**Downlink Commands:**
++)))
++(((
  **A9 aa** ~-~-> Same as AT+MBFUN=aa
++)))
++
  ==== **RS485 command timeout** ====
++(((
  Some Modbus device has slow action to send replies. This command is used to configure the RS485-BL to use longer time to wait for their action.
++)))
++(((
  Default value: 0, range:  0 ~~ 5 seconds
++)))
++(((
++
++)))
--* **AT Command:**
++* (((
++**AT Command:**
++)))
  (% class="box infomessage" %)
  (((
++(((
  **AT+CMDDLaa=hex(bb cc)**
  )))
++)))
++(((
  **Example:**
++)))
++(((
  **AT+CMDDL1=1000** to send the open time to 1000ms
++)))
++(((
++
++)))
--* **Downlink Payload:**
++* (((
++**Downlink Payload:**
++)))
++(((
 x AA aa bb cc
++)))
++(((
  Same as: AT+CMDDLaa=hex(bb cc)
++)))
++(((
     **Example:**
++)))
++(((
     **0xAA 01 03 E8**  ~-~-> 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
++)))
@@ -1021,132 +1021,229 @@
  ==== **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:**
++)))
++(((
  (% style="color:#037691" %)**AT+CMDEAR=mm,nn** (%%)    mm: start position of erase ,nn: stop position of erase Etc. AT+CMDEAR=1,10 means erase AT+COMMAND1/AT+DATACUT1 to AT+COMMAND10/AT+DATACUT10
++)))
++(((
  Example screen shot after clear all RS485 commands.
++)))
++(((
++
++)))
++(((
  The uplink screen shot is:
++)))
++(((
  [[image:1654134704555-320.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)
++)))
++
  ==== **Control output power duration** ====
++(((
  User can set the output power duration before each sampling.
++)))
--* **AT Command:**
++* (((
++**AT Command:**
++)))
++(((
  **Example:**
++)))
++(((
  **AT+3V3T=1000**  ~/~/ 3V3 output power will open 1s before each sampling.
++)))
++(((
  **AT+5VT=1000**  ~/~/ +5V output power will open 1s before each sampling.
++)))
++(((
++
++)))
--* **LoRaWAN Downlink Command:**
++* (((
++**LoRaWAN Downlink Command:**
++)))
++(((
  **07 01 aa bb**  Same as AT+5VT=(aa bb)
++)))
++(((
  **07 02 aa bb**  Same as AT+3V3T=(aa bb)
++)))
  == 3.6 Buttons ==
--(% border="1" style="background-color:#ffffcc; color:green; width:233px" %)
++(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:233px" %)
  |=(% style="width: 89px;" %)**Button**|=(% style="width: 141px;" %)**Feature**
  |(% style="width:89px" %)**RST**|(% style="width:141px" %)Reboot RS485-BL
--
  == 3.7 +3V3 Output ==
++(((
  RS485-BL has a Controllable +3V3 output, user can use this output to power external sensor.
++)))
++(((
  The +3V3 output will be valid for every sampling. RS485-BL will enable +3V3 output before all sampling and disable the +3V3 after all sampling.
++)))
++(((
  The +3V3 output time can be controlled by AT Command.
++)))
++(((
++
++)))
++(((
  (% style="color:#037691" %)**AT+3V3T=1000**
++)))
++(((
++
++)))
++(((
  Means set +3v3 valid time to have 1000ms. So, the real +3v3 output will actually have 1000ms + sampling time for other sensors.
++)))
++(((
  By default, the AT+3V3T=0. This is a special case, means the +3V3 output is always on at any time
++)))
  == 3.8 +5V Output ==
++(((
  RS485-BL has a Controllable +5V output, user can use this output to power external sensor.
++)))
++(((
  The +5V output will be valid for every sampling. RS485-BL will enable +5V output before all sampling and disable the +5v after all sampling.
++)))
++(((
  The 5V output time can be controlled by AT Command.
++)))
++(((
++
++)))
++(((
  (% style="color:#037691" %)**AT+5VT=1000**
++)))
++(((
++
++)))
++(((
  Means set 5V valid time to have 1000ms. So, the real 5V output will actually have 1000ms + sampling time for other sensors.
++)))
++(((
  By default, the AT+5VT=0. If the external sensor which require 5v and require more time to get stable state, user can use this command to increase the power ON duration for this sensor.
++)))
++
  == 3.9 LEDs ==
  (% border="1" style="background-color:#ffffcc; color:green; width:332px" %)
@@ -1153,26 +1153,22 @@
  |=**LEDs**|=(% style="width: 274px;" %)**Feature**
  |**LED1**|(% style="width:274px" %)Blink when device transmit a packet.
--
--
  == 3.10 Switch Jumper ==
--(% border="1" style="background-color:#ffffcc; color:green; width:515px" %)
--|=(% style="width: 124px;" %)**Switch Jumper**|=(% style="width: 388px;" %)**Feature**
--|(% style="width:124px" %)**SW1**|(% style="width:388px" %)(((
--ISP position: Upgrade firmware via UART
--
++(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:463px" %)
++|=(% style="width: 123px;" %)**Switch Jumper**|=(% style="width: 336px;" %)**Feature**
++|(% style="width:123px" %)**SW1**|(% style="width:336px" %)ISP position: Upgrade firmware via UART
  Flash position: Configure device, check running status.
--)))
--|(% style="width:124px" %)**SW2**|(% style="width:388px" %)(((
--5V position: set to compatible with 5v I/O.
--
++|(% style="width:123px" %)**SW2**|(% style="width:336px" %)5V position: set to compatible with 5v I/O.
 .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.
++)))
  = 4. Case Study =
@@ -1184,17 +1184,23 @@
  == 5.1 Access AT Command ==
++(((
  RS485-BL supports AT Command set. User can use a USB to TTL adapter plus the 3.5mm Program Cable to connect to RS485-BL to use AT command, as below.
++)))
  [[image:1654135840598-282.png]]
++(((
  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-BL. The default password is 123456. Below is the output for reference:
++)))
  [[image:1654136105500-922.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>>||anchor="H3.5ConfigureRS485-BLviaATorDownlink"]]
++)))
  == 5.2 Common AT Command Sequence ==
@@ -1206,20 +1206,14 @@
  (% class="box infomessage" %)
  (((
  **AT+FDR**
--)))
--
--(% class="box infomessage" %)
--(((
  **AT+NJM=0**
--)))
--
--(% class="box infomessage" %)
--(((
  **ATZ**
  )))
++(((
  If device already joined network:
++)))
  (% class="box infomessage" %)
  (((
@@ -1258,10 +1258,12 @@
  (% style="color:red" %)**Note:**
++(((
  (% style="color:red" %)1. Make sure the device is set to ABP mode in the IoT Server.
 . Make sure the LG01/02 gateway RX frequency is exactly the same as AT+CHS setting.
 . 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.
 . The command AT+RX2FQ and AT+RX2DR is to let downlink work. to set the correct parameters, user can check the actually downlink parameters to be used. As below. Which shows the RX2FQ should use 868400000 and RX2DR should be 5
++)))
  [[image:1654136435598-589.png]]
@@ -1270,13 +1270,23 @@
  == 6.1 How to upgrade the image? ==
++(((
  The RS485-BL LoRaWAN Controller is shipped with a 3.5mm cable, the cable is used to upload image to RS485-BL to:
++)))
--* Support new features
--* For bug fix
--* Change LoRaWAN bands.
++* (((
++Support new features
++)))
++* (((
++For bug fix
++)))
++* (((
++Change LoRaWAN bands.
++)))
++(((
  Below shows the hardware connection for how to upload an image to RS485-BL:
++)))
  [[image:1654136646995-976.png]]
@@ -1298,13 +1298,17 @@
  == 6.2 How to change the LoRa Frequency Bands/Region? ==
++(((
  User can follow the introduction for [[how to upgrade image>>||anchor="H6.1Howtoupgradetheimage3F"]]. When download the images, choose the required image file for download.
++)))
  == 6.3 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>>||anchor="H3.3.3Configurereadcommandsforeachsampling"]].
++)))
@@ -1338,7 +1338,6 @@
  * (% style="color:blue" %)**RU864**(%%): frequency bands RU864
  * (% style="color:blue" %)**KZ865**(%%): frequency bands KZ865
--
  = 9. Packing Info =
  (((
@@ -1376,5 +1376,9 @@
  = 10. Support =
--* Support is provided Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different timezones we cannot offer live support. However, your questions will be answered as soon as possible in the before-mentioned schedule.
--* Provide as much information as possible regarding your enquiry (product models, accurately describe your problem and steps to replicate it etc) and send a mail to [[support@dragino.com>>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-20220606105412-1.png

Author

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

Size

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

Content