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

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

From 28.2 to 28.1 From 32.1 to 31.2

From version 31.2

edited by Xiaoling
on 2022/06/02 09:38

Change comment: There is no comment for this version

To version 28.2

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

Change comment: There is no comment for this version

Raw
Rendered

Summary

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

Details

Page properties

Content

@@ -7,15 +7,12 @@
  **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 ==
@@ -25,19 +25,19 @@
  )))
  (((
--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.
++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.
  )))
  (((
--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 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 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 is IP67 **waterproof** and powered by **8500mAh Li-SOCI2 battery**, it is designed for long term use for several years.
  )))
  (((
--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.
++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.
  )))
  (((
@@ -54,11 +54,8 @@
  [[image:1652953304999-717.png||height="424" width="733"]]
--
--
  == 1.2 Specifications ==
--
  **Hardware System:**
  * STM32L072CZT6 MCU
@@ -65,6 +65,8 @@
  * SX1276/78 Wireless Chip
  * Power Consumption (exclude RS485 device):
  ** Idle: 6uA@3.3v
++
++*
  ** 20dB Transmit: 130mA@3.3v
  **Interface for Model:**
@@ -118,12 +118,9 @@
  [[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
  )))
@@ -147,8 +147,6 @@
  (((
  Release version
--
--
  )))
  = 2. Pin mapping and Power ON Device =
@@ -162,7 +162,6 @@
  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? ==
@@ -169,8 +169,6 @@
  (((
  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 ==
@@ -206,6 +206,8 @@
  )))
++
++
  [[image:image-20220519174512-1.png]]
  [[image:image-20220519174512-2.png||height="328" width="731"]]
@@ -229,13 +229,10 @@
  [[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>>||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.
--
--
++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.
  )))
  === 3.3.1 onfigure UART settings for RS485 or TTL communication ===
@@ -336,9 +336,8 @@
  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>>||anchor="HRS485DebugCommand28AT2BCFGDEV29"]].
++Detail of AT+CFGDEV command see [[AT+CFGDEV detail>>path:#AT_CFGDEV]].
--
  === 3.3.3 Configure read commands for each sampling ===
  (((
@@ -436,7 +436,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)
@@ -444,7 +444,7 @@
  [[image:1653271044481-711.png]]
--2）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=2, 1E 56 34+31 00 49
@@ -463,18 +463,16 @@
  * **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"]]
@@ -517,7 +517,6 @@
  [[image:1653271763403-806.png]]
--
  === 3.3.4 Compose the uplink payload ===
  (((
@@ -525,7 +525,7 @@
  )))
  (((
--(% style="color:#037691" %)**Examples: AT+DATAUP=0**
++(% style="color:#4f81bd" %)**Examples: AT+DATAUP=0**
  )))
  (((
@@ -537,7 +537,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
  )))
  (((
@@ -546,12 +546,8 @@
  [[image:1653272787040-634.png||height="515" width="719"]]
--
--
  (((
--(% style="color:#037691" %)**Examples: AT+DATAUP=1**
--
--
++(% style="color:#4f81bd" %)**Examples: AT+DATAUP=1**
  )))
  (((
@@ -563,7 +563,7 @@
  )))
  (((
--(% style="color:#4f81bd" %)**Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA**
++(% style="color:#4f81bd" %)Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA
  )))
 . (((
@@ -586,7 +586,6 @@
  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
@@ -593,12 +593,10 @@
  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)
@@ -609,8 +609,6 @@
     ~* For all other bands: max 51 bytes for each uplink  ( so 51 -5 = 46 max valid date).
--
--
  === 3.3.5 Uplink on demand ===
  (((
@@ -627,8 +627,6 @@
  (((
  **0xA8 command**: Send a command to RS485-BL and uplink the output from sensors.
--
--
  )))
  === 3.3.6 Uplink on Interrupt ===
@@ -637,160 +637,117 @@
  [[image:1653273818896-432.png]]
--
--(((
  AT+INTMOD=0  Disable Interrupt
--)))
--(((
  AT+INTMOD=1  Interrupt trigger by rising or falling edge.
--)))
--(((
  AT+INTMOD=2  Interrupt trigger by falling edge. ( Default Value)
--)))
--(((
  AT+INTMOD=3  Interrupt trigger by rising edge.
--
--)))
--
  == 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" %)(((
--(((
++|**Size(bytes)**|**2**|**1**|**Length depends on the return from the commands**
++|Value|(((
  Battery(mV)
--)))
--(((
  &
--)))
--(((
  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.
++)))|If the valid payload is too long and exceed the maximum support payload length in server, server will show payload not provided in the LoRaWAN server.
  Below is the decoder for the first 3 bytes. The rest bytes are dynamic depends on different RS485 sensors.
--(((
--{{{function Decoder(bytes, port) {}}}
--)))
--(((
--{{{//Payload Formats of RS485-BL Deceive}}}
--)))
++function Decoder(bytes, port) {
--(((
--{{{return {}}}
--)))
++~/~/Payload Formats of RS485-BL Deceive
--(((
--{{{    //Battery,units:V}}}
--)))
++return {
--(((
--{{{    BatV:((bytes[0]<<8 | bytes[1])&0x7fff)/1000,}}}
--)))
++    ~/~/Battery,units:V
--(((
--{{{    //GPIO_EXTI  }}}
--)))
++    BatV:((bytes[0]<<8 | bytes[1])&0x7fff)/1000,
--(((
--{{{    EXTI_Trigger:(bytes[0] & 0x80)? "TRUE":"FALSE",}}}
--)))
++    ~/~/GPIO_EXTI
--(((
--{{{    //payload of version}}}
--)))
++    EXTI_Trigger:(bytes[0] & 0x80)? "TRUE":"FALSE",
--(((
--{{{    Pay_ver:bytes[2],}}}
--)))
++    ~/~/payload of version
--(((
--{{{    }; }}}
--)))
++    Pay_ver:bytes[2],
--(((
--}
++    };
--
--)))
++  }
--(((
--TTN V3 uplink screen shot.
--)))
--[[image:1653274001211-372.png||height="192" width="732"]]
--== 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: [[End Device AT Commands and Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]]
++TTN V3 uplink screen shot.
--* (% style="color:#4f81bd" %)**Sensor Related Commands**(%%): These commands are special designed for RS485-BL.  User can see these commands below:
++[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png]]
--=== 3.5.1 Common Commands: ===
++1.
++11. Configure RS485-BL via AT or Downlink
--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]]
++User can configure RS485-BL via [[AT Commands >>path:#_Using_the_AT]]or LoRaWAN Downlink Commands
++There are two kinds of Commands:
--=== 3.5.2 Sensor related 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
--====   ====
++* **Sensor Related Commands**: These commands are special designed for RS485-BL.  User can see these commands below:
--==== **Choose Device Type (RS485 or TTL)** ====
++1.
++11.
++111. 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]]
++
++
++1.
++11.
++111. 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.
--* **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 (AT+CFGDEV)** ====
++==== [[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.
--* **AT Command**
++* AT Command
--(% class="box infomessage" %)
--(((
--**AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m**
--)))
++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:
@@ -804,15 +804,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:
--(% 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 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 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.
@@ -821,60 +821,48 @@
  Check TTL Sensor return:
--[[image:1654132684752-193.png]]
++[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image024.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:
--(% class="box infomessage" %)
--(((
--**AT+PAYVER: Set PAYVER field = 1**
--)))
++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>>||anchor="H3.3.3Configurereadcommandsforeachsampling"]].
++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 Command:**
++* AT Command:
--(% class="box infomessage" %)
--(((
--**AT+COMMANDx: Configure RS485 read command to sensor.**
--)))
++AT+COMMANDx: Configure RS485 read command to sensor.
--(% class="box infomessage" %)
--(((
--**AT+DATACUTx: Configure how to handle return from RS485 devices.**
--)))
++AT+DATACUTx: Configure how to handle return from RS485 devices.
--(% class="box infomessage" %)
--(((
--**AT+SEARCHx: Configure search command**
--)))
++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.
--(% style="color:red" %)**Note**(%%): if user use AT+COMMANDx to add a new command, he also need to send AT+DATACUTx downlink.
++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
@@ -881,23 +881,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:
--(% 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 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**
++**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" %)**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**
++**AF 03 02 06 0B 02 05 07 08 0A 00**: Same as AT+DATACUT3=**11**,**2**,**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
@@ -905,15 +905,14 @@
  **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
@@ -921,14 +921,13 @@
  * 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:1654133913295-597.png]]
++[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image025.png]]
  [[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image026.png]]
@@ -1077,13 +1077,13 @@
--1.
++1.
 . Buttons
  |**Button**|**Feature**
  |**RST**|Reboot RS485-BL
--1.
++1.
 . +3V3 Output
  RS485-BL has a Controllable +3V3 output, user can use this output to power external sensor.
@@ -1101,7 +1101,7 @@
  By default, the AT+3V3T=0. This is a special case, means the +3V3 output is always on at any time
--1.
++1.
 . +5V Output
  RS485-BL has a Controllable +5V output, user can use this output to power external sensor.
@@ -1121,13 +1121,13 @@
--1.
++1.
 . LEDs
  |**LEDs**|**Feature**
  |**LED1**|Blink when device transmit a packet.
--1.
++1.
 . Switch Jumper
  |**Switch Jumper**|**Feature**
@@ -1173,7 +1173,7 @@
--1.
++1.
 . Common AT Command Sequence
 . Multi-channel ABP mode (Use with SX1301/LG308)
@@ -1192,8 +1192,8 @@
  ATZ
--1.
--11.
++1.
++11.
 . Single-channel ABP mode (Use with LG01/LG02)
  AT+FDR   Reset Parameters to Factory Default, Keys Reserve
@@ -1268,7 +1268,7 @@
  [[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image035.png]]   [[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image036.png]]
--1.
++1.
 . How to change the LoRa Frequency Bands/Region?
  User can follow the introduction for [[how to upgrade image>>path:#upgrade_image]]. When download the images, choose the required image file for download.
@@ -1275,7 +1275,7 @@
--1.
++1.
 . 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]].
@@ -1292,7 +1292,7 @@
--1.
++1.
 . Why I can’t join TTN V3 in US915 /AU915 bands?
  It might about the channels mapping. Please see for detail.

1653274001211-372.png

Author

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

Size

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

Content

1654132684752-193.png

Author

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

Size

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

Content

1654133913295-597.png

Author

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

Size

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

Content

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

Summary

Details

Applications

Navigation