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

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

From 29.1 to 29.2 From 33.5 to 33.6

From version 29.2

edited by Xiaoling
on 2022/05/23 10:47

Change comment: There is no comment for this version

To version 33.5

edited by Xiaoling
on 2022/06/02 10:01

Change comment: There is no comment for this version

Raw
Rendered

Summary

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

Details

Page properties

Content

@@ -7,12 +7,15 @@
  **RS485-BL – Waterproof RS485 to LoRaWAN Converter User Manual**
++
  **Table of Contents:**
++{{toc/}}
++
  = 1.Introduction =
  == 1.1 What is RS485-BL RS485 to LoRaWAN Converter ==
@@ -22,19 +22,19 @@
  )))
  (((
--The Dragino RS485-BL is a **RS485 / UART to LoRaWAN Converter** for Internet of Things solutions. User can connect RS485 or UART sensor to RS485-BL converter, and configure RS485-BL to periodically read sensor data and upload via LoRaWAN network to IoT server.
++The Dragino RS485-BL is a (% style="color:blue" %)**RS485 / UART to LoRaWAN Converter**(%%) for Internet of Things solutions. User can connect RS485 or UART sensor to RS485-BL converter, and configure RS485-BL to periodically read sensor data and upload via LoRaWAN network to IoT server.
  )))
  (((
--RS485-BL can interface to RS485 sensor, 3.3v/5v UART sensor or interrupt sensor. RS485-BL provides **a 3.3v output** and** a 5v output** to power external sensors. Both output voltages are controllable to minimize the total system power consumption.
++RS485-BL can interface to RS485 sensor, 3.3v/5v UART sensor or interrupt sensor. RS485-BL provides (% style="color:blue" %)**a 3.3v output**(%%) and** (% style="color:blue" %)a 5v output(%%)** to power external sensors. Both output voltages are controllable to minimize the total system power consumption.
  )))
  (((
--RS485-BL is IP67 **waterproof** and powered by **8500mAh Li-SOCI2 battery**, it is designed for long term use for several years.
++RS485-BL is IP67 (% style="color:blue" %)**waterproof**(%%) and powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), it is designed for long term use for several years.
  )))
  (((
--RS485-BL runs standard **LoRaWAN 1.0.3 in Class A**. It can reach long transfer range and easy to integrate with LoRaWAN compatible gateway and IoT server.
++RS485-BL runs standard (% style="color:blue" %)**LoRaWAN 1.0.3 in Class A**(%%). It can reach long transfer range and easy to integrate with LoRaWAN compatible gateway and IoT server.
  )))
  (((
@@ -51,8 +51,11 @@
  [[image:1652953304999-717.png||height="424" width="733"]]
++
++
  == 1.2 Specifications ==
++
  **Hardware System:**
  * STM32L072CZT6 MCU
@@ -59,8 +59,6 @@
  * SX1276/78 Wireless Chip
  * Power Consumption (exclude RS485 device):
  ** Idle: 6uA@3.3v
--
--*
  ** 20dB Transmit: 130mA@3.3v
  **Interface for Model:**
@@ -114,9 +114,12 @@
  [[RS485-BL Image files – Download link and Change log>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/RS485-BL/Firmware/||style="background-color: rgb(255, 255, 255);"]]
++
  == 1.6 Hardware Change log ==
  (((
++
++
  v1.4
  )))
@@ -140,6 +140,8 @@
  (((
  Release version
++
++
  )))
  = 2. Pin mapping and Power ON Device =
@@ -153,6 +153,7 @@
  The Left TXD and RXD are TTL interface for external sensor. TTL level is controlled by 3.3/5v Jumper.
++
  = 3. Operation Mode =
  == 3.1 How it works? ==
@@ -159,6 +159,8 @@
  (((
  The RS485-BL is configured as LoRaWAN OTAA Class A mode by default. It has OTAA keys to join network. To connect a local LoRaWAN network, user just need to input the OTAA keys in the network server and power on the RS485-BL. It will auto join the network via OTAA.
++
++
  )))
  == 3.2 Example to join LoRaWAN network ==
@@ -194,8 +194,6 @@
  )))
--
--
  [[image:image-20220519174512-1.png]]
  [[image:image-20220519174512-2.png||height="328" width="731"]]
@@ -219,10 +219,13 @@
  [[image:1652953568895-172.png||height="232" width="724"]]
++
  == 3.3 Configure Commands to read data ==
  (((
--There are plenty of RS485 and TTL level devices in the market and each device has different command to read the valid data. To support these devices in flexible, RS485-BL supports flexible command set. User can use [[AT Commands or LoRaWAN Downlink>>path:#AT_COMMAND]] Command to configure how RS485-BL should read the sensor and how to handle the return from RS485 or TTL sensors.
++There are plenty of RS485 and TTL level devices in the market and each device has different command to read the valid data. To support these devices in flexible, RS485-BL supports flexible command set. User can use [[AT Commands or LoRaWAN Downlink>>||anchor="H3.5ConfigureRS485-BLviaATorDownlink"]] Command to configure how RS485-BL should read the sensor and how to handle the return from RS485 or TTL sensors.
++
++
  )))
  === 3.3.1 onfigure UART settings for RS485 or TTL communication ===
@@ -323,8 +323,9 @@
  mm: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
  )))|(% style="width:256px" %)AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
--Detail of AT+CFGDEV command see [[AT+CFGDEV detail>>path:#AT_CFGDEV]].
++Detail of AT+CFGDEV command see [[AT+CFGDEV detail>>||anchor="HRS485DebugCommand28AT2BCFGDEV29"]].
++
  === 3.3.3 Configure read commands for each sampling ===
  (((
@@ -422,7 +422,7 @@
  **Examples:**
--1. For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
++1）For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
  If we set AT+SEARCH1=1,1E 56 34.      (max 5 bytes for prefix)
@@ -430,7 +430,7 @@
  [[image:1653271044481-711.png]]
--1. For a return string from AT+COMMAND1:  16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
++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
@@ -449,16 +449,18 @@
  * **c: define the position for valid value.  **
  )))
--Examples:
++**Examples:**
  * Grab bytes:
  [[image:1653271581490-837.png||height="313" width="722"]]
++
  * Grab a section.
  [[image:1653271648378-342.png||height="326" width="720"]]
++
  * Grab different sections.
  [[image:1653271657255-576.png||height="305" width="730"]]
@@ -501,6 +501,7 @@
  [[image:1653271763403-806.png]]
++
  === 3.3.4 Compose the uplink payload ===
  (((
@@ -508,7 +508,7 @@
  )))
  (((
--(% style="color:#4f81bd" %)**Examples: AT+DATAUP=0**
++(% style="color:#037691" %)**Examples: AT+DATAUP=0**
  )))
  (((
@@ -520,7 +520,7 @@
  )))
  (((
--(% style="color:#4f81bd" %)Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx
++(% style="color:#4f81bd" %)**Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx**
  )))
  (((
@@ -529,8 +529,12 @@
  [[image:1653272787040-634.png||height="515" width="719"]]
++
++
  (((
--(% style="color:#4f81bd" %)**Examples: AT+DATAUP=1**
++(% style="color:#037691" %)**Examples: AT+DATAUP=1**
++
++
  )))
  (((
@@ -542,7 +542,7 @@
  )))
  (((
--(% style="color:#4f81bd" %)Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA
++(% style="color:#4f81bd" %)**Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA**
  )))
 . (((
@@ -565,6 +565,7 @@
  So totally there will be 3 uplinks for this sampling, each uplink includes 6 bytes DATA
++
  DATA1=RETURN1 Valid Value = (% style="background-color:#4f81bd; color:white" %) 20 20 0a 33 90 41
  DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10= (% style="background-color:#4f81bd; color:white" %)02 aa 05 81 0a 20
@@ -571,10 +571,12 @@
  DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 =(% style="background-color:#4f81bd; color:white" %) 20 20 20 2d 30
++
  Below are the uplink payloads:
  [[image:1653272901032-107.png]]
++
  (% style="color:red" %)Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:
     ~* For AU915/AS923 bands, if UplinkDwell time=0, max 51 bytes for each uplink ( so 51 -5 = 46 max valid date)
@@ -585,6 +585,8 @@
     ~* For all other bands: max 51 bytes for each uplink  ( so 51 -5 = 46 max valid date).
++
++
  === 3.3.5 Uplink on demand ===
  (((
@@ -601,6 +601,8 @@
  (((
  **0xA8 command**: Send a command to RS485-BL and uplink the output from sensors.
++
++
  )))
  === 3.3.6 Uplink on Interrupt ===
@@ -609,6 +609,7 @@
  [[image:1653273818896-432.png]]
++
  (((
  AT+INTMOD=0  Disable Interrupt
  )))
@@ -623,6 +623,8 @@
  (((
  AT+INTMOD=3  Interrupt trigger by rising edge.
++
++
  )))
  == 3.4 Uplink Payload ==
@@ -650,47 +650,49 @@
  Below is the decoder for the first 3 bytes. The rest bytes are dynamic depends on different RS485 sensors.
  (((
--function Decoder(bytes, port) {
++{{{function Decoder(bytes, port) {}}}
  )))
  (((
--~/~/Payload Formats of RS485-BL Deceive
++{{{//Payload Formats of RS485-BL Deceive}}}
  )))
  (((
--return {
++{{{return {}}}
  )))
  (((
--    ~/~/Battery,units:V
++{{{    //Battery,units:V}}}
  )))
  (((
--    BatV:((bytes[0]<<8 | bytes[1])&0x7fff)/1000,
++{{{    BatV:((bytes[0]<<8 | bytes[1])&0x7fff)/1000,}}}
  )))
  (((
--    ~/~/GPIO_EXTI
++{{{    //GPIO_EXTI  }}}
  )))
  (((
--    EXTI_Trigger:(bytes[0] & 0x80)? "TRUE":"FALSE",
++{{{    EXTI_Trigger:(bytes[0] & 0x80)? "TRUE":"FALSE",}}}
  )))
  (((
--    ~/~/payload of version
++{{{    //payload of version}}}
  )))
  (((
--    Pay_ver:bytes[2],
++{{{    Pay_ver:bytes[2],}}}
  )))
  (((
--    };
++{{{    }; }}}
  )))
  (((
--  }
++}
++
++
  )))
  (((
@@ -699,59 +699,65 @@
  [[image:1653274001211-372.png||height="192" width="732"]]
--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
++== 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:
--* **Common Commands**: They should be available for each sensor, such as: change uplink interval, reset device. For firmware v1.3, user can find what common commands it supports: http:~/~/wiki.dragino.com/index.php?title=End_Device_AT_Commands_and_Downlink_Commands
++* (% style="color:#4f81bd" %)**Common Commands**(%%): They should be available for each sensor, such as: change uplink interval, reset device. For firmware v1.3, user can find what common commands it supports: [[End Device AT Commands and Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]]
--* **Sensor Related Commands**: These commands are special designed for RS485-BL.  User can see these commands below:
++* (% style="color:#4f81bd" %)**Sensor Related Commands**(%%): These commands are special designed for RS485-BL.  User can see these commands below:
--1.
--11.
--111. Common Commands:
++=== 3.5.1 Common Commands: ===
--They should be available for each of Dragino Sensors, such as: change uplink interval, reset device. For firmware v1.3, user can find what common commands it supports: [[http:~~/~~/wiki.dragino.com/index.php?title=End_Device_AT_Commands_and_Downlink_Commands>>url:http://wiki.dragino.com/index.php?title=End_Device_AT_Commands_and_Downlink_Commands]]
++They should be available for each of Dragino Sensors, such as: change uplink interval, reset device. For firmware v1.3, user can find what common commands it supports: [[End Device AT Commands and Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]]
--1.
--11.
--111. Sensor related commands:
++=== 3.5.2 Sensor related commands: ===
--==== Choose Device Type (RS485 or TTL) ====
++====   ====
++==== **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.
--* AT Command
++* **AT Command**
++(% class="box infomessage" %)
++(((
  **AT+MOD=1** ~/~/ Set to support RS485-MODBUS type sensors. User can connect multiply RS485 , Modbus sensors to the A / B pins.
++)))
++(% class="box infomessage" %)
++(((
  **AT+MOD=2** ~/~/ Set to support TTL Level sensors, User can connect one TTL Sensor to the TXD/RXD/GND pins.
++)))
--* Downlink Payload
++* **Downlink Payload**
--**0A aa**     à same as AT+MOD=aa
++**0A aa**     ~-~->  same as AT+MOD=aa
--==== [[RS485 Debug Command>>path:#downlink_A8]] (AT+CFGDEV) ====
++==== **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**
--AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
++(% 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:
@@ -765,15 +765,15 @@
  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:
--**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 01 00**(%%): to activate the RS485 Alarm
--**A8 01 06 0A 05 00 04 00 00 00**: to deactivate 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.
@@ -782,48 +782,60 @@
  Check TTL Sensor return:
--[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image024.png]]
++[[image:1654132684752-193.png]]
++==== **Set Payload version** ====
--==== Set Payload version ====
--
  This is the first byte of the uplink payload. RS485-BL can connect to different sensors. User can set the PAYVER field to tell server how to decode the current payload.
--* AT Command:
++* **AT Command:**
--AT+PAYVER: Set PAYVER field = 1
++(% class="box infomessage" %)
++(((
++**AT+PAYVER: Set PAYVER field = 1**
++)))
--* Downlink Payload:
++* **Downlink Payload:**
--0xAE 01   à Set PAYVER field =  0x01
++**0xAE 01**   ~-~-> Set PAYVER field =  0x01
--0xAE 0F   à Set PAYVER field =  0x0F
++**0xAE 0F**   ~-~-> Set PAYVER field =  0x0F
--==== Set RS485 Sampling Commands ====
++==== **Set RS485 Sampling Commands** ====
++
  AT+COMMANDx, AT+DATACUTx and AT+SEARCHx
--These three commands are used to configure how the RS485-BL polling data from Modbus device. Detail of usage please see : [[polling RS485 device>>path:#polling_485]].
++These three commands are used to configure how the RS485-BL polling data from Modbus device. Detail of usage please see : [[polling RS485 device>>||anchor="H3.3.3Configurereadcommandsforeachsampling"]].
--* AT Command:
++* **AT Command:**
--AT+COMMANDx: Configure RS485 read command to sensor.
++(% class="box infomessage" %)
++(((
++**AT+COMMANDx: Configure RS485 read command to sensor.**
++)))
--AT+DATACUTx: Configure how to handle return from RS485 devices.
++(% class="box infomessage" %)
++(((
++**AT+DATACUTx: Configure how to handle return from RS485 devices.**
++)))
--AT+SEARCHx: Configure search command
++(% class="box infomessage" %)
++(((
++**AT+SEARCHx: Configure search command**
++)))
--* Downlink Payload:
++* **Downlink Payload:**
--0xAF downlink command can be used to set AT+COMMANDx or AT+DATACUTx.
++**0xAF** downlink command can be used to set AT+COMMANDx or AT+DATACUTx.
--Note: if user use AT+COMMANDx to add a new command, he also need to send AT+DATACUTx downlink.
++(% style="color:red" %)**Note**(%%): if user use AT+COMMANDx to add a new command, he also need to send AT+DATACUTx downlink.
  Format: AF MM NN LL XX XX XX XX YY
@@ -830,23 +830,23 @@
  Where:
  * MM: the ATCOMMAND or AT+DATACUT to be set. Value from 01 ~~ 0F,
--* NN: 0: no CRC; 1: add CRC-16/MODBUS ; 2: set the AT+DATACUT value.
--* LL: The length of AT+COMMAND or AT+DATACUT command
++* NN:  0: no CRC; 1: add CRC-16/MODBUS ; 2: set the AT+DATACUT value.
++* LL:   The length of AT+COMMAND or AT+DATACUT command
  * XX XX XX XX: AT+COMMAND or AT+DATACUT command
--* YY: If YY=0, RS485-BL will execute the downlink command without uplink; if YY=1, RS485-BL will execute an uplink after got this command.
++* YY:   If YY=0, RS485-BL will execute the downlink command without uplink; if YY=1, RS485-BL will execute an uplink after got this command.
--Example:
++**Example:**
--**AF 03 01 06 0A 05 00 04 00 01 00**: Same as AT+COMMAND3=0A 05 00 04 00 01,1
++(% style="color:#037691" %)**AF 03 01 06 0A 05 00 04 00 01 00**(%%): Same as AT+COMMAND3=0A 05 00 04 00 01,1
--**AF 03 02 06 10 01 05 06 09 0A 00**: Same as AT+DATACUT3=**16**,**1**,**5+6+9+10**
++(% style="color:#037691" %)**AF 03 02 06**(% style="color:orange" %)** 10 **(% style="color:red" %)**01 **(% style="color:green" %)**05 06 09 0A**(% style="color:#037691" %)** 00**(%%): Same as AT+DATACUT3=(% style="color:orange" %)**16**(%%),(% style="color:red" %)**1**(%%),(% style="color:green" %)**5+6+9+10**
--**AF 03 02 06 0B 02 05 07 08 0A 00**: Same as AT+DATACUT3=**11**,**2**,**5~~7+8~~10**
++(% style="color:#037691" %)**AF 03 02 06 **(% style="color:orange" %)**0B**(% style="color:red" %)** 02 **(% style="color:green" %)**05 07 08 0A **(% style="color:#037691" %)**00**(%%): Same as AT+DATACUT3=(% style="color:orange" %)**11**(%%),(% style="color:red" %)**2**(%%),(% style="color:green" %)**5~~7+8~~10**
--0xAB downlink command can be used for set AT+SEARCHx
++**0xAB** downlink command can be used for set AT+SEARCHx
--Example: **AB aa 01 03 xx xx xx** (03 here means there are total 3 bytes after 03) So
++**Example:** **AB aa 01 03 xx xx xx** (03 here means there are total 3 bytes after 03) So
  * AB aa 01 03 xx xx xx  same as AT+SEARCHaa=1,xx xx xx
  * AB aa 02 03 xx xx xx 02 yy yy(03 means there are 3 bytes after 03, they are xx xx xx;02 means there are 2 bytes after 02, they are yy yy) so the commands
@@ -854,145 +854,164 @@
  **AB aa 02 03 xx xx xx 02 yy yy**  same as **AT+SEARCHaa=2,xx xx xx+yy yy**
--==== Fast command to handle MODBUS device ====
++==== **Fast command to handle MODBUS device** ====
++
  AT+MBFUN is valid since v1.3 firmware version. The command is for fast configure to read Modbus devices. It is only valid for the devices which follow the [[MODBUS-RTU protocol>>url:https://www.modbustools.com/modbus.html]].
  This command is valid since v1.3 firmware version
--AT+MBFUN has only two value:
++**AT+MBFUN has only two value:**
--* AT+MBFUN=1: Enable Modbus reading. And get response base on the MODBUS return
++* **AT+MBFUN=1**: Enable Modbus reading. And get response base on the MODBUS return
  AT+MBFUN=1, device can auto read the Modbus function code: 01, 02, 03 or 04. AT+MBFUN has lower priority vs AT+DATACUT command. If AT+DATACUT command is configured, AT+MBFUN will be ignore.
--* AT+MBFUN=0: Disable Modbus fast reading.
++* **AT+MBFUN=0**: Disable Modbus fast reading.
--Example:
++**Example:**
  * AT+MBFUN=1 and AT+DATACUT1/AT+DATACUT2 are not configure (0,0,0).
  * AT+COMMAND1= 01 03 00 10 00 08,1 ~-~-> read slave address 01 , function code 03, start address 00 01, quantity of registers 00 08.
  * AT+COMMAND2= 01 02 00 40 00 10,1 ~-~-> read slave address 01 , function code 02, start address 00 40, quantity of inputs 00 10.
--[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image025.png]]
++[[image:1654133913295-597.png]]
--[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image026.png]]
++[[image:1654133954153-643.png]]
--* Downlink Commands:
++* **Downlink Commands:**
--A9 aa -à Same as AT+MBFUN=aa
++**A9 aa** ~-~-> Same as AT+MBFUN=aa
--==== RS485 command timeout ====
++==== **RS485 command timeout** ====
++
  Some Modbus device has slow action to send replies. This command is used to configure the RS485-BL to use longer time to wait for their action.
  Default value: 0, range:  0 ~~ 5 seconds
--* AT Command:
++* **AT Command:**
--AT+CMDDLaa=hex(bb cc)
++(% class="box infomessage" %)
++(((
++**AT+CMDDLaa=hex(bb cc)**
++)))
--Example:
++**Example:**
  **AT+CMDDL1=1000** to send the open time to 1000ms
--* Downlink Payload:
++* **Downlink Payload:**
 x AA aa bb cc
  Same as: AT+CMDDLaa=hex(bb cc)
--   Example:
++   **Example:**
--   0xAA 01 03 E8  à Same as **AT+CMDDL1=1000 ms**
++   **0xAA 01 03 E8**  ~-~-> Same as **AT+CMDDL1=1000 ms**
--==== [[Uplink>>path:#downlink_A8]] payload mode ====
++==== **Uplink payload mode** ====
++
  Define to use one uplink or multiple uplinks for the sampling.
--The use of this command please see: [[Compose Uplink payload>>path:#DataUP]]
++The use of this command please see: [[Compose Uplink payload>>||anchor="H3.3.4Composetheuplinkpayload"]]
--* AT Command:
++* **AT Command:**
--AT+DATAUP=0
++(% class="box infomessage" %)
++(((
++**AT+DATAUP=0**
++)))
--AT+DATAUP=1
++(% class="box infomessage" %)
++(((
++**AT+DATAUP=1**
++)))
--* Downlink Payload:
++* **Downlink Payload:**
--0xAD 00   à Same as AT+DATAUP=0
++**0xAD 00**   **~-~->** Same as AT+DATAUP=0
--0xAD 01   à Same as AT+DATAUP=1
++**0xAD 01**   **~-~->** Same as AT+DATAUP=1
--==== Manually trigger an Uplink ====
++==== **Manually trigger an Uplink** ====
++
  Ask device to send an uplink immediately.
--* Downlink Payload:
++* **Downlink Payload:**
--0x08 FF, RS485-BL will immediately send an uplink.
++**0x08 FF**, RS485-BL will immediately send an uplink.
--==== Clear RS485 Command ====
++==== **Clear RS485 Command** ====
++
  The AT+COMMANDx and AT+DATACUTx settings are stored in special location, user can use below command to clear them.
--* AT Command:
++* **AT Command:**
--**AT+CMDEAR=mm,nn**   mm: start position of erase ,nn: stop position of erase
++(% style="color:#037691" %)**AT+CMDEAR=mm,nn** (%%)    mm: start position of erase ,nn: stop position of erase Etc. AT+CMDEAR=1,10 means erase AT+COMMAND1/AT+DATACUT1 to AT+COMMAND10/AT+DATACUT10
--Etc. AT+CMDEAR=1,10 means erase AT+COMMAND1/AT+DATACUT1 to AT+COMMAND10/AT+DATACUT10
--
  Example screen shot after clear all RS485 commands.
--
  The uplink screen shot is:
--[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png]]
++[[image:1654134704555-320.png]]
--* Downlink Payload:
++* **Downlink Payload:**
--0x09 aa bb  same as AT+CMDEAR=aa,bb
++**0x09 aa bb**  same as AT+CMDEAR=aa,bb
--==== Set Serial Communication Parameters ====
++==== **Set Serial Communication Parameters** ====
++
  Set the Rs485 serial communication parameters:
--* AT Command:
++* **AT Command:**
  Set Baud Rate:
--AT+BAUDR=9600    ~/~/ Options: (1200,2400,4800,14400,19200,115200)
++(% class="box infomessage" %)
++(((
++**AT+BAUDR=9600**    ~/~/ Options: (1200,2400,4800,14400,19200,115200)
++)))
++Set UART Parity
--Set UART parity
++(% class="box infomessage" %)
++(((
++**AT+PARITY=0**    ~/~/ Option: 0: no parity, 1: odd parity, 2: even parity
++)))
--AT+PARITY=0    ~/~/ Option: 0: no parity, 1: odd parity, 2: even parity
--
--
  Set STOPBIT
--AT+STOPBIT=0    ~/~/ Option: 0 for 1bit; 1 for 1.5 bit ; 2 for 2 bits
++(% class="box infomessage" %)
++(((
++**AT+STOPBIT=0**    ~/~/ Option: 0 for 1bit; 1 for 1.5 bit ; 2 for 2 bits
++)))
--* Downlink Payload:
++* **Downlink Payload:**
--A7 01 aa bb: Same  AT+BAUDR=hex(aa bb)*100
++**A7 01 aa bb**: Same  AT+BAUDR=hex(aa bb)*100
--Example:
++**Example:**
  * A7 01 00 60   same as AT+BAUDR=9600
  * A7 01 04 80     same as AT+BAUDR=115200
@@ -1002,54 +1002,52 @@
  A7 03 aa: Same as  AT+STOPBIT=aa  (aa value: 00 , 01 or 02)
--==== Control output power duration ====
++==== **Control output power duration** ====
++
  User can set the output power duration before each sampling.
--* AT Command:
++* **AT Command:**
--Example:
++**Example:**
--AT+3V3T=1000 ~/~/ 3V3 output power will open 1s before each sampling.
++**AT+3V3T=1000**  ~/~/ 3V3 output power will open 1s before each sampling.
--AT+5VT=1000 ~/~/ +5V output power will open 1s before each sampling.
++**AT+5VT=1000**  ~/~/ +5V output power will open 1s before each sampling.
--* LoRaWAN Downlink Command:
++* **LoRaWAN Downlink Command:**
--07 01 aa bb  Same as AT+5VT=(aa bb)
++**07 01 aa bb**  Same as AT+5VT=(aa bb)
--07 02 aa bb  Same as AT+3V3T=(aa bb)
++**07 02 aa bb**  Same as AT+3V3T=(aa bb)
++== 3.6 Buttons ==
++(% border="1" 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
--1.
--11. Buttons
--|**Button**|**Feature**
--|**RST**|Reboot RS485-BL
++== 3.7 +3V3 Output ==
--1.
--11. +3V3 Output
--
  RS485-BL has a Controllable +3V3 output, user can use this output to power external sensor.
  The +3V3 output will be valid for every sampling. RS485-BL will enable +3V3 output before all sampling and disable the +3V3 after all sampling.
--
  The +3V3 output time can be controlled by AT Command.
--**AT+3V3T=1000**
--Means set +3v3 valid time to have 1000ms. So, the real +3v3 output will actually have 1000ms + sampling time for other sensors.
++(% 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
--1.
--11. +5V Output
++== 3.8 +5V Output ==
  RS485-BL has a Controllable +5V output, user can use this output to power external sensor.
@@ -1058,7 +1058,7 @@
  The 5V output time can be controlled by AT Command.
--**AT+5VT=1000**
++(% 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.
@@ -1067,15 +1067,12 @@
++== 3.9 LEDs ==
--1.
--11. LEDs
--
  |**LEDs**|**Feature**
  |**LED1**|Blink when device transmit a packet.
--1.
--11. Switch Jumper
++== 3.10 Switch Jumper ==
  |**Switch Jumper**|**Feature**
  |**SW1**|(((

1654132684752-193.png

Author

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

Size

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

Content

1654133913295-597.png

Author

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

Size

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

Content

1654133954153-643.png

Author

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

Size

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

Content

1654134704555-320.png

Author

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

Size

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

Content

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

Summary

Details

Applications

Navigation