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

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

From 28.1 to 27.1 From 29.32 to 29.31

From version 29.31

edited by Xiaoling
on 2022/06/02 08:55

Change comment: There is no comment for this version

To version 28.1

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

Change comment: Uploaded new attachment "1653273818896-432.png", version {1}

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 ===
@@ -316,8 +316,6 @@
  )))
  )))
--
--
  === 3.3.2 Configure sensors ===
  (((
@@ -338,9 +338,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 ===
  (((
@@ -438,7 +438,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)
@@ -446,7 +446,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
@@ -465,19 +465,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"]]
@@ -520,7 +520,6 @@
  [[image:1653271763403-806.png]]
--
  === 3.3.4 Compose the uplink payload ===
  (((
@@ -549,7 +549,6 @@
  [[image:1653272787040-634.png||height="515" width="719"]]
--
  (((
  (% style="color:#4f81bd" %)**Examples: AT+DATAUP=1**
  )))
@@ -586,18 +586,21 @@
  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
++DATA1=RETURN1 Valid Value = ~(% style="background-color:#4f81bd;color:white" %)(% style="display:none" %) (%%)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
++DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10= ~(% style="background-color:#4f81bd;color:white" %)(% style="display:none" %) (%%)02 aa 05 81 0a 20
--DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 =(% style="background-color:#4f81bd; color:white" %) 20 20 20 2d 30
++DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 =~(% style="background-color:#4f81bd;color:white" %)(% style="display:none" %) (%%) 20 20 20 2d 30
++
++
  Below are the uplink payloads:
--[[image:1653272901032-107.png]]
++[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image021.png]]
--(% style="color:red" %)Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:
++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)
     * For AU915/AS923 bands, if UplinkDwell time=1, max 11 bytes for each uplink ( so 11 -5 = 6 max valid date).
@@ -606,121 +606,90 @@
     ~* For all other bands: max 51 bytes for each uplink  ( so 51 -5 = 46 max valid date).
--=== 3.3.5 Uplink on demand ===
--(((
++
++1.
++11.
++111. Uplink on demand
++
  Except uplink periodically, RS485-BL is able to uplink on demand. The server sends downlink command to RS485-BL and RS485 will uplink data base on the command.
--)))
--(((
  Downlink control command:
--)))
--(((
--**0x08 command**: Poll an uplink with current command set in RS485-BL.
--)))
++[[0x08 command>>path:#downlink_08]]: Poll an uplink with current command set in RS485-BL.
--(((
--**0xA8 command**: Send a command to RS485-BL and uplink the output from sensors.
--)))
++[[0xA8 command>>path:#downlink_A8]]: Send a command to RS485-BL and uplink the output from sensors.
--=== 3.3.6 Uplink on Interrupt ===
--Put the interrupt sensor between 3.3v_out and GPIO ext.
--[[image:1653273818896-432.png]]
++1.
++11.
++111. Uplink on Interrupt
--(((
++Put the interrupt sensor between 3.3v_out and GPIO ext.[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image022.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" %)(((
--(((
++1.
++11. Uplink Payload
++
++|**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
--)))
--(((
  return {
--)))
--(((
      ~/~/Battery,units:V
--)))
--(((
      BatV:((bytes[0]<<8 | bytes[1])&0x7fff)/1000,
--)))
--(((
      ~/~/GPIO_EXTI
--)))
--(((
      EXTI_Trigger:(bytes[0] & 0x80)? "TRUE":"FALSE",
--)))
--(((
      ~/~/payload of version
--)))
--(((
      Pay_ver:bytes[2],
--)))
--(((
      };
--)))
--(((
    }
--)))
--(((
++
++
++
++
++
++
  TTN V3 uplink screen shot.
--)))
--[[image:1653274001211-372.png||height="192" width="732"]]
++[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png]]
--== 3.5 Configure RS485-BL via AT or Downlink ==
++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

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