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 29.43 to 29.42

From version 29.42

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

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, 1 removed)
- 1653274001211-372.png

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,128 +637,91 @@
  [[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]]
++1.
++11. Configure RS485-BL via AT or Downlink
--=== 3.5.1 Common Commands: ===
++User can configure RS485-BL via [[AT Commands >>path:#_Using_the_AT]]or LoRaWAN 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]]
++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
--=== 3.5.2 Sensor related commands: ===
++* **Sensor Related Commands**: These commands are special designed for RS485-BL.  User can see these commands below:
--(% class="wikigeneratedid" %)
--====   ====
++1.
++11.
++111. Common Commands:
--==== **Choose Device Type (RS485 or TTL)** ====
++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
  **AT+MOD=1** ~/~/ Set to support RS485-MODBUS type sensors. User can connect multiply RS485 , Modbus sensors to the A / B pins.
@@ -765,9 +765,9 @@
  **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

1653274001211-372.png

Author

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

Size

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

Content

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

Summary

Details

Applications

Navigation