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

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

From 29.14 to 29.13 From 30.5 to 30.4

From version 30.4

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

Change comment: There is no comment for this version

To version 29.14

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

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, 1 removed)
- 1654132684752-193.png

Details

Page properties

Content

@@ -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.
  )))
  (((
@@ -58,7 +58,6 @@
  == 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:**
@@ -94,6 +94,8 @@
  * 127 dB Dynamic Range RSSI.
  * Automatic RF Sense and CAD with ultra-fast AFC.
++
++
  == 1.3 Features ==
  * LoRaWAN Class A & Class C protocol (default Class A)
@@ -105,6 +105,8 @@
  * Support Modbus protocol
  * Support Interrupt uplink
++
++
  == 1.4 Applications ==
  * Smart Buildings & Home Automation
@@ -114,6 +114,8 @@
  * Smart Cities
  * Smart Factory
++
++
  == 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);"]]
@@ -122,8 +122,6 @@
  == 1.6 Hardware Change log ==
  (((
--
--
  v1.4
  )))
@@ -206,6 +206,8 @@
  )))
++
++
  [[image:image-20220519174512-1.png]]
  [[image:image-20220519174512-2.png||height="328" width="731"]]
@@ -229,7 +229,6 @@
  [[image:1652953568895-172.png||height="232" width="724"]]
--
  == 3.3 Configure Commands to read data ==
  (((
@@ -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,7 +637,6 @@
  [[image:1653273818896-432.png]]
--
  (((
  AT+INTMOD=0  Disable Interrupt
  )))
@@ -652,8 +652,6 @@
  (((
  AT+INTMOD=3  Interrupt trigger by rising edge.
--
--
  )))
  == 3.4 Uplink Payload ==
@@ -681,49 +681,47 @@
  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],
  )))
  (((
--{{{    }; }}}
++    };
  )))
  (((
--}
--
--
++  }
  )))
  (((
@@ -732,67 +732,58 @@
  [[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
++User can configure RS485-BL via [[AT Commands >>path:#_Using_the_AT]]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]]
++* **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" %)**Sensor Related Commands**(%%): These commands are special designed for RS485-BL.  User can see these commands below:
++* **Sensor Related Commands**: These commands are special designed for RS485-BL.  User can see these commands below:
++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]]
--=== 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]]
++1.
++11.
++111. Sensor related commands:
++==== Choose Device Type (RS485 or TTL) ====
--=== 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.
--* **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:
@@ -802,20 +802,19 @@
  * 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
++**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.
@@ -824,32 +824,29 @@
  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>>path:#polling_485]].

1654132684752-193.png

Author

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

Size

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

Content