Changes for page RS485-LN – RS485 to LoRaWAN Converter User Manual

Last modified by Karry Zhuang on 2025/03/06 16:34

From version < 32.11 >

edited by Xiaoling
on 2022/06/02 15:26

To version < 29.1 >

edited by Xiaoling
on 2022/05/23 09:35

Change comment: Uploaded new attachment "1653269759169-150.png", version {1}

Raw
Rendered

Summary

Page properties (1 modified, 0 added, 0 removed)
Attachments (0 modified, 0 added, 2 removed)
- 1653269916228-732.png
- 1653270130359-810.png

Details

Page properties

Content

@@ -18,30 +18,26 @@
  (((
  (((
--The Dragino RS485-LN is a (% style="color:blue" %)**RS485 to LoRaWAN Converter**(%%). It converts the RS485 signal into LoRaWAN wireless signal which simplify the IoT installation and reduce the installation/maintaining cost.
++The Dragino RS485-LN is a RS485 to LoRaWAN Converter. It converts the RS485 signal into LoRaWAN wireless signal which simplify the IoT installation and reduce the installation/maintaining cost.
  )))
  (((
--RS485-LN allows user to (% style="color:blue" %)**monitor / control RS485 devices**(%%) and reach extremely long ranges. It provides ultra-long range spread spectrum communication and high interference immunity whilst minimizing current consumption. It targets professional wireless sensor network applications such as irrigation systems, smart metering, smart cities, smartphone detection, building automation, and so on.
++RS485-LN allows user to monitor / control RS485 devices and reach extremely long ranges. It provides ultra-long range spread spectrum communication and high interference immunity whilst minimizing current consumption. It targets professional wireless sensor network applications such as irrigation systems, smart metering, smart cities, smartphone detection, building automation, and so on.
  )))
  (((
--(% style="color:blue" %)**For data uplink**(%%), RS485-LN sends user-defined commands to RS485 devices and gets the return from the RS485 devices. RS485-LN will process these returns according to user-define rules to get the final payload and upload to LoRaWAN server.
++For data uplink, RS485-LN sends user-defined commands to RS485 devices and gets the return from the RS485 devices. RS485-LN will process these returns according to user-define rules to get the final payload and upload to LoRaWAN server.
  )))
  (((
--(% style="color:blue" %)**For data downlink**(%%), RS485-LN runs in LoRaWAN Class C. When there downlink commands from LoRaWAN server, RS485-LN will forward the commands from LoRaWAN server to RS485 devices.
--
--(% style="color:blue" %)**Demo Dashboard for RS485-LN**(%%) connect to two energy meters: [[https:~~/~~/app.datacake.de/dashboard/d/58844a26-378d-4c5a-aaf5-b5b5b153447a>>url:https://app.datacake.de/dashboard/d/58844a26-378d-4c5a-aaf5-b5b5b153447a]]
++For data downlink, RS485-LN runs in LoRaWAN Class C. When there downlink commands from LoRaWAN server, RS485-LN will forward the commands from LoRaWAN server to RS485 devices.
  )))
  )))
  [[image:1653267211009-519.png||height="419" width="724"]]
--
  == 1.2 Specifications ==
--
  **Hardware System:**
  * STM32L072CZT6 MCU
@@ -48,6 +48,8 @@
  * SX1276/78 Wireless Chip
  * Power Consumption (exclude RS485 device):
  ** Idle: 32mA@12v
++
++*
  ** 20dB Transmit: 65mA@12v
  **Interface for Model:**
@@ -76,8 +76,6 @@
  * Automatic RF Sense and CAD with ultra-fast AFC.
  * Packet engine up to 256 bytes with CRC.
--
--
  == 1.3 Features ==
  * LoRaWAN Class A & Class C protocol (default Class C)
@@ -89,8 +89,6 @@
  * Support Modbus protocol
  * Support Interrupt uplink (Since hardware version v1.2)
--
--
  == 1.4 Applications ==
  * Smart Buildings & Home Automation
@@ -100,13 +100,10 @@
  * Smart Cities
  * Smart Factory
--
--
  == 1.5 Firmware Change log ==
  [[RS485-LN Image files – Download link and Change log>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/]]
--
  == 1.6 Hardware Change log ==
  (((
@@ -114,8 +114,6 @@
  v1.2: Add External Interrupt Pin.
  v1.0: Release
--
--
  )))
  )))
@@ -132,8 +132,6 @@
  )))
  [[image:1653268091319-405.png]]
--
--
  )))
  = 3. Operation Mode =
@@ -378,17 +378,11 @@
  **m: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command**
  )))
--(((
  For example, if we have a RS485 sensor. The command to get sensor value is: 01 03 0B B8 00 02 46 0A. Where 01 03 0B B8 00 02 is the Modbus command to read the register 0B B8 where stored the sensor value. The 46 0A is the CRC-16/MODBUS which calculate manually.
--)))
--(((
  In the RS485-BL, we should use this command AT+COMMAND1=01 03 0B B8 00 02,1 for the same.
--)))
--(((
  **AT+SEARCHx**: This command defines how to handle the return from AT+COMMANDx.
--)))
  (% border="1" class="table-bordered" %)
  |(((
@@ -400,24 +400,26 @@
  )))
--**Examples:**
++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)
--The valid data will be all bytes after 1E 56 34 , so it is (% style="background-color:yellow" %)** 2e 30 58 5f 36 41 30 31 00 49**
++The valid data will be all bytes after 1E 56 34 , so it is 2e 30 58 5f 36 41 30 31 00 49
--[[image:1653269403619-508.png]]
++[[image:1652954654347-831.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
--Device will search the bytes between 1E 56 34 and 31 00 49. So it is (% style="background-color:yellow" %)** 2e 30 58 5f 36 41 30**
++Device will search the bytes between 1E 56 34 and 31 00 49. So it is 2e 30 58 5f 36 41 30
--[[image:1653269438444-278.png]]
++[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image014.png]]
++
  **AT+DATACUTx : **This command defines how to handle the return from AT+COMMANDx, max return length is 45 bytes.
  |(((
@@ -432,95 +432,94 @@
  * Grab bytes:
--[[image:1653269551753-223.png||height="311" width="717"]]
++[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image015.png]]
  * Grab a section.
--[[image:1653269568276-930.png||height="325" width="718"]]
++[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image016.png]]
  * Grab different sections.
--[[image:1653269593172-426.png||height="303" width="725"]]
++[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image017.png]]
--(% style="color:red" %)**Note:**
++Note:
++
  AT+SEARCHx and AT+DATACUTx can be used together, if both commands are set, RS485-BL will first process AT+SEARCHx on the return string and get a temporary string, and then process AT+DATACUTx on this temporary string to get the final payload. In this case, AT+DATACUTx need to set to format AT+DATACUTx=0,xx,xx where the return bytes set to 0.
  Example:
--(% style="color:red" %)AT+COMMAND1=11 01 1E D0,0
++AT+COMMAND1=11 01 1E D0,0
--(% style="color:red" %)AT+SEARCH1=1,1E 56 34
++AT+SEARCH1=1,1E 56 34
--(% style="color:red" %)AT+DATACUT1=0,2,1~~5
++AT+DATACUT1=0,2,1~~5
--(% style="color:red" %)Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
++Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
--(% style="color:red" %)String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49
++String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49
--(% style="color:red" %)Valid payload after DataCUT command: 2e 30 58 5f 36
++Valid payload after DataCUT command: 2e 30 58 5f 36
--[[image:1653269618463-608.png]]
++[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image018.png]]
--=== 3.3.4 Compose the uplink payload ===
--(((
++
++
++1.
++11.
++111. Compose the uplink payload
++
  Through AT+COMMANDx and AT+DATACUTx we got valid value from each RS485 commands, Assume these valid value are RETURN1, RETURN2, .., to RETURNx. The next step is how to compose the LoRa Uplink Payload by these RETURNs. The command is **AT+DATAUP.**
--)))
--(((
--(% style="color:#4f81bd" %)**Examples: AT+DATAUP=0**
--)))
--(((
--Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**A SIGNLE UPLINK**.
--)))
++**Examples: AT+DATAUP=0**
--(((
++Compose the uplink payload with value returns in sequence and send with **A SIGNLE UPLINK**.
++
  Final Payload is
--)))
--(((
--(% style="color:#4f81bd" %)**Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx**
--)))
++Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx
--(((
  Where PAYVER is defined by AT+PAYVER, below is an example screen shot.
--)))
--[[image:1653269759169-150.png||height="513" width="716"]]
++[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image019.png]]
--(% style="color:#4f81bd" %)**Examples: AT+DATAUP=1**
--Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**Multiply UPLINKs**.
++**Examples: AT+DATAUP=1**
++
++Compose the uplink payload with value returns in sequence and send with **Multiply UPLINKs**.
++
  Final Payload is
--(% style="color:#4f81bd" %)**Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA**
++Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA
 . Battery Info (2 bytes): Battery voltage
 . PAYVER (1 byte): Defined by AT+PAYVER
 . PAYLOAD COUNT (1 byte): Total how many uplinks of this sampling.
 . PAYLOAD# (1 byte): Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT)
--1. DATA: Valid value: max 6 bytes(US915 version here, Notice*!) for each uplink so each uplink <= 11 bytes. For the last uplink, DATA will might less than 6 bytes
++1. DATA: Valid value: max 6 bytes(US915 version here, [[Notice*!>>path:#max_byte]]) for each uplink so each uplink <= 11 bytes. For the last uplink, DATA will might less than 6 bytes
--[[image:1653269916228-732.png||height="433" width="711"]]
++[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image020.png]]
  So totally there will be 3 uplinks for this sampling, each uplink includes 6 bytes DATA
--DATA1=RETURN1 Valid Value = (% style="background-color:green; color:white" %)20 20 0a 33 90 41
++DATA1=RETURN1 Valid Value = 20 20 0a 33 90 41
--DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10=(% style="background-color:green; color:white" %) 02 aa 05 81 0a 20
++DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10= 02 aa 05 81 0a 20
--DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 = (% style="background-color:green; color:white" %)20 20 20 2d 30
++DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 = 20 20 20 2d 30
++
++
  Below are the uplink payloads:
--[[image:1653270130359-810.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)
@@ -530,8 +530,12 @@
     ~* 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:
@@ -542,8 +542,8 @@
--1.
--11.
++1.
++11.
 . 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]]
@@ -557,7 +557,7 @@
  AT+INTMOD=3  Interrupt trigger by rising edge.
--1.
++1.
 . Uplink Payload
  |**Size(bytes)**|**2**|**1**|**Length depends on the return from the commands**
@@ -619,15 +619,15 @@
  * **Sensor Related Commands**: These commands are special designed for RS485-BL.  User can see these commands below:
--1.
--11.
++1.
++11.
 . 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.
++1.
++11.
 . Sensor related commands:
  ==== Choose Device Type (RS485 or TTL) ====
@@ -933,13 +933,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.
@@ -957,7 +957,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.
@@ -977,13 +977,13 @@
--1.
++1.
 . LEDs
  |**LEDs**|**Feature**
  |**LED1**|Blink when device transmit a packet.
--1.
++1.
 . Switch Jumper
  |**Switch Jumper**|**Feature**
@@ -1029,7 +1029,7 @@
--1.
++1.
 . Common AT Command Sequence
 . Multi-channel ABP mode (Use with SX1301/LG308)
@@ -1048,8 +1048,8 @@
  ATZ
--1.
--11.
++1.
++11.
 . Single-channel ABP mode (Use with LG01/LG02)
  AT+FDR   Reset Parameters to Factory Default, Keys Reserve
@@ -1124,7 +1124,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.
@@ -1131,7 +1131,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]].
@@ -1148,7 +1148,7 @@
--1.
++1.
 . Why I can’t join TTN V3 in US915 /AU915 bands?
  It might about the channels mapping. Please see for detail.

1653269916228-732.png

Author

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

Size

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

Content

1653270130359-810.png

Author

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

Size

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

Content

Changes for page RS485-LN – RS485 to LoRaWAN Converter User Manual

Summary

Details

Applications

Navigation