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

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

From 29.12 to 29.13 From 29.41 to 29.42

From version 29.13

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

Change comment: There is no comment for this version

To version 29.41

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

Change comment: There is no comment for this version

Raw
Rendered

Summary

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

Details

Page properties

Content

@@ -25,19 +25,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.
  )))
  (((
@@ -54,8 +54,11 @@
  [[image:1652953304999-717.png||height="424" width="733"]]
++
++
  == 1.2 Specifications ==
++
  **Hardware System:**
  * STM32L072CZT6 MCU
@@ -62,8 +62,6 @@
  * SX1276/78 Wireless Chip
  * Power Consumption (exclude RS485 device):
  ** Idle: 6uA@3.3v
--
--*
  ** 20dB Transmit: 130mA@3.3v
  **Interface for Model:**
@@ -93,8 +93,6 @@
  * 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)
@@ -106,8 +106,6 @@
  * Support Modbus protocol
  * Support Interrupt uplink
--
--
  == 1.4 Applications ==
  * Smart Buildings & Home Automation
@@ -117,8 +117,6 @@
  * 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);"]]
@@ -127,6 +127,8 @@
  == 1.6 Hardware Change log ==
  (((
++
++
  v1.4
  )))
@@ -209,8 +209,6 @@
  )))
--
--
  [[image:image-20220519174512-1.png]]
  [[image:image-20220519174512-2.png||height="328" width="731"]]
@@ -234,6 +234,7 @@
  [[image:1652953568895-172.png||height="232" width="724"]]
++
  == 3.3 Configure Commands to read data ==
  (((
@@ -340,8 +340,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 ===
  (((
@@ -439,7 +439,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)
@@ -447,7 +447,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
@@ -466,16 +466,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"]]
@@ -518,6 +518,7 @@
  [[image:1653271763403-806.png]]
++
  === 3.3.4 Compose the uplink payload ===
  (((
@@ -525,7 +525,7 @@
  )))
  (((
--(% style="color:#4f81bd" %)**Examples: AT+DATAUP=0**
++(% style="color:#037691" %)**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,8 +546,12 @@
  [[image:1653272787040-634.png||height="515" width="719"]]
++
++
  (((
--(% style="color:#4f81bd" %)**Examples: AT+DATAUP=1**
++(% style="color:#037691" %)**Examples: AT+DATAUP=1**
++
++
  )))
  (((
@@ -559,7 +559,7 @@
  )))
  (((
--(% style="color:#4f81bd" %)Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA
++(% style="color:#4f81bd" %)**Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA**
  )))
 . (((
@@ -582,6 +582,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
@@ -588,10 +588,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)
@@ -602,6 +602,8 @@
     ~* For all other bands: max 51 bytes for each uplink  ( so 51 -5 = 46 max valid date).
++
++
  === 3.3.5 Uplink on demand ===
  (((
@@ -618,6 +618,8 @@
  (((
  **0xA8 command**: Send a command to RS485-BL and uplink the output from sensors.
++
++
  )))
  === 3.3.6 Uplink on Interrupt ===
@@ -626,6 +626,7 @@
  [[image:1653273818896-432.png]]
++
  (((
  AT+INTMOD=0  Disable Interrupt
  )))
@@ -640,6 +640,8 @@
  (((
  AT+INTMOD=3  Interrupt trigger by rising edge.
++
++
  )))
  == 3.4 Uplink Payload ==
@@ -667,47 +667,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],}}}
  )))
  (((
--    };
++{{{    }; }}}
  )))
  (((
--  }
++}
++
++
  )))
  (((
@@ -716,29 +716,30 @@
  [[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 >>path:#_Using_the_AT]]or LoRaWAN Downlink Commands
++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:
--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: ===
++(% class="wikigeneratedid" %)
++====   ====
++
++==== **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
@@ -1040,13 +1040,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.
@@ -1064,7 +1064,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.
@@ -1084,13 +1084,13 @@
--1.
++1.
 . LEDs
  |**LEDs**|**Feature**
  |**LED1**|Blink when device transmit a packet.
--1.
++1.
 . Switch Jumper
  |**Switch Jumper**|**Feature**
@@ -1136,7 +1136,7 @@
--1.
++1.
 . Common AT Command Sequence
 . Multi-channel ABP mode (Use with SX1301/LG308)
@@ -1155,8 +1155,8 @@
  ATZ
--1.
--11.
++1.
++11.
 . Single-channel ABP mode (Use with LG01/LG02)
  AT+FDR   Reset Parameters to Factory Default, Keys Reserve
@@ -1231,7 +1231,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.
@@ -1238,7 +1238,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]].
@@ -1255,7 +1255,7 @@
--1.
++1.
 . Why I can’t join TTN V3 in US915 /AU915 bands?
  It might about the channels mapping. Please see for detail.