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

Last modified by Bei Jinggeng on 2025/01/16 11:36

From version < 58.6 >

edited by Xiaoling
on 2022/06/06 11:21

To version < 57.48 >

edited by Xiaoling
on 2022/06/06 11:01

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)
- image-20220606110929-1.png

Details

Page properties

Content

@@ -327,8 +327,6 @@
  mm: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
  )))|(% style="width:190px" %)AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
--
--
  === 3.3.3 Configure read commands for each sampling ===
  (((
@@ -501,35 +501,33 @@
  == 3.4 Uplink Payload ==
++(% border="1" style="background-color:#4bacc6; color:white; width:734px" %)
++|**Size(bytes)**|(% style="width:120px" %)**2**|(% style="width:116px" %)**1**|(% style="width:386px" %)**Length depends on the return from the commands**
++|Value|(% style="width:120px" %)(((
++Battery(mV)
--[[image:image-20220606110929-1.png]]
++&
++Interrupt _Flag
++)))|(% style="width:116px" %)(((
++PAYLOAD_VER
++
++
++)))|(% style="width:386px" %)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.
  == 3.5 Configure RS485-BL via AT or Downlink ==
--(((
  User can configure RS485-LN 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: [[AT Commands and Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]]
--)))
++* (% 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: [[AT Commands and Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]]
--* (((
--(% style="color:#4f81bd" %)**Sensor Related Commands**(%%): These commands are special designed for RS485-LN.  User can see these commands below:
--)))
++* (% style="color:#4f81bd" %)**Sensor Related Commands**(%%): These commands are special designed for RS485-LN.  User can see these commands below:
--(((
--
--)))
--
--
  === 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]]
@@ -548,159 +548,82 @@
--
  ==== **RS485 Debug Command** ====
--(((
  This command is used to configure the RS485 devices; 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**
  )))
--)))
--(((
  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:
--)))
--* (((
--MM: 1: add CRC-16/MODBUS ; 0: no CRC
--)))
--* (((
--NN: The length of RS485 command
--)))
--* (((
--XX XX XX XX: RS485 command total NN bytes
--)))
--* (((
--(((
--YY: How many bytes will be uplink from the return of this RS485 command,
--)))
++* MM: 1: add CRC-16/MODBUS ; 0: no CRC
++* NN: The length of RS485 command
++* 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-LN will execute the downlink command without uplink;
++** if YY>0, RS485-LN will uplink total YY bytes from the output of this RS485 command; Fport=200
++** if YY=FF, RS485-LN will uplink RS485 output with the downlink command content; Fport=200.
--* (((
--if YY=0, RS485-LN will execute the downlink command without uplink;
--)))
--* (((
--if YY>0, RS485-LN will uplink total YY bytes from the output of this RS485 command; Fport=200
--)))
--* (((
--if YY=FF, RS485-LN will uplink RS485 output with the downlink command content; Fport=200.
--)))
--)))
--
--(((
  **Example 1** ~-~-> Configure without ask for uplink (YY=0)
--)))
--(((
  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:#4f81bd" %)**A8 01 06 0A 05 00 04 00 01 00**(%%): to activate the RS485 Alarm
--)))
--(((
  (% style="color:#4f81bd" %)**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.
--)))
--(((
--
--)))
--(((
  **Example 2** ~-~-> Configure with requesting uplink and original downlink command (**YY=FF**)
--)))
--(((
  User in IoT server send a downlink command: (% style="color:#4f81bd" %)**A8 01 06 0A 08 00 04 00 01 YY**
--)))
--(((
--
--)))
--(((
  RS485-LN got this downlink command and send (% style="color:#4f81bd" %)**0A 08 00 04 00 01 **(%%)to Modbus network. One of the RS485 sensor in the network send back Modbus reply **0A 08 00 04 00 00**. RS485-LN get this reply and combine with the original downlink command and uplink. The uplink message is:
--)))
--(((
     **A8** (% style="color:#4f81bd" %)**0A 08 00 04 00  **(% style="color:red" %)**01 06** ** **(% style="color:green" %)**0A 08 00 04 00 00**
--)))
--(((
   [[image:1654159460680-153.png]]
--)))
  ==== **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**
  )))
--)))
--* (((
--**Downlink Payload:**
--)))
++* **Downlink Payload:**
--(((
  **0xAE 01**   ~-~-> Set PAYVER field =  0x01
--)))
--(((
  **0xAE 0F**   ~-~-> Set PAYVER field =  0x0F
--)))
--
  ==== **Set RS485 Sampling Commands** ====
  AT+COMMANDx or AT+DATACUTx

image-20220606110929-1.png

Author

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

Size

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

Content

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

Summary

Details

Applications

Navigation