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

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

From 29.37 to 29.38 From 30.4 to 30.5

From version 29.38

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

Change comment: There is no comment for this version

To version 30.4

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

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (1 modified, 0 added, 0 removed)
Attachments (0 modified, 1 added, 0 removed)
- 1654132684752-193.png

Details

Page properties

Content

@@ -316,7 +316,6 @@
  )))
  )))
--
  === 3.3.2 Configure sensors ===
  (((
@@ -682,47 +682,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],}}}
  )))
  (((
--    };
++{{{    }; }}}
  )))
  (((
--  }
++}
++
++
  )))
  (((
@@ -731,58 +731,67 @@
  [[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: ===
--1.
--11.
--111. Sensor related 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]]
--==== Choose Device Type (RS485 or TTL) ====
++=== 3.5.2 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**
++(% class="box infomessage" %)
++(((
  **AT+MOD=1** ~/~/ Set to support RS485-MODBUS type sensors. User can connect multiply RS485 , Modbus sensors to the A / B pins.
++)))
++(% class="box infomessage" %)
++(((
  **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
--==== [[RS485 Debug Command>>path:#downlink_A8]] (AT+CFGDEV) ====
++==== **RS485 Debug Command (AT+CFGDEV)** ====
  This command is used to configure the RS485 or TTL sensors; they won’t be used during sampling.
--* AT Command
++* **AT Command**
--AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
++(% 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:
@@ -792,19 +792,20 @@
  * 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-BL will execute the downlink command without uplink; if YY>0, RS485-BL will uplink total YY bytes from the output of this RS485 command
++
  **Example 1:**
  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:
--**A8 01 06 0A 05 00 04 00 01 00**: to activate the RS485 Alarm
++(% style="color:#037691" %)**A8 01 06 0A 05 00 04 00 01 00**(%%): to activate the RS485 Alarm
--**A8 01 06 0A 05 00 04 00 00 00**: to deactivate the RS485 Alarm
++(% style="color:#037691" %)**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.
@@ -813,29 +813,32 @@
  Check TTL Sensor return:
--[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image024.png]]
++[[image:1654132684752-193.png]]
++==== **Set Payload version** ====
--==== 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:**
--AT+PAYVER: Set PAYVER field = 1
++(% class="box infomessage" %)
++(((
++**AT+PAYVER: Set PAYVER field = 1**
++)))
--* Downlink Payload:
++* **Downlink Payload:**
--0xAE 01   à Set PAYVER field =  0x01
++**0xAE 01**   ~-~-> Set PAYVER field =  0x01
--0xAE 0F   à Set PAYVER field =  0x0F
++**0xAE 0F**   ~-~-> Set PAYVER field =  0x0F
--==== Set RS485 Sampling Commands ====
++==== **Set RS485 Sampling Commands** ====
++
  AT+COMMANDx, AT+DATACUTx and AT+SEARCHx
  These three commands are used to configure how the RS485-BL polling data from Modbus device. Detail of usage please see : [[polling RS485 device>>path:#polling_485]].

1654132684752-193.png

Author

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

Size

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

Content

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

Summary

Details

Applications

Navigation