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

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

From 29.28 to 29.27 From 30.4 to 30.3

From version 30.3

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

Change comment: There is no comment for this version

To version 29.28

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

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)
- 1654132684752-193.png

Details

Page properties

Content

@@ -316,6 +316,8 @@
  )))
  )))
++
++
  === 3.3.2 Configure sensors ===
  (((
@@ -463,6 +463,7 @@
  * **c: define the position for valid value.  **
  )))
++
  **Examples:**
  * Grab bytes:
@@ -474,7 +474,6 @@
  [[image:1653271648378-342.png||height="326" width="720"]]
--
  * Grab different sections.
  [[image:1653271657255-576.png||height="305" width="730"]]
@@ -517,7 +517,6 @@
  [[image:1653271763403-806.png]]
--
  === 3.3.4 Compose the uplink payload ===
  (((
@@ -525,7 +525,7 @@
  )))
  (((
--(% style="color:#037691" %)**Examples: AT+DATAUP=0**
++(% style="color:#4f81bd" %)**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,12 +546,8 @@
  [[image:1653272787040-634.png||height="515" width="719"]]
--
--
  (((
--(% style="color:#037691" %)**Examples: AT+DATAUP=1**
--
--
++(% style="color:#4f81bd" %)**Examples: AT+DATAUP=1**
  )))
  (((
@@ -563,7 +563,7 @@
  )))
  (((
--(% style="color:#4f81bd" %)**Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA**
++(% style="color:#4f81bd" %)Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA
  )))
 . (((
@@ -586,7 +586,6 @@
  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
@@ -593,12 +593,10 @@
  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)
@@ -609,8 +609,6 @@
     ~* For all other bands: max 51 bytes for each uplink  ( so 51 -5 = 46 max valid date).
--
--
  === 3.3.5 Uplink on demand ===
  (((
@@ -627,8 +627,6 @@
  (((
  **0xA8 command**: Send a command to RS485-BL and uplink the output from sensors.
--
--
  )))
  === 3.3.6 Uplink on Interrupt ===
@@ -637,7 +637,6 @@
  [[image:1653273818896-432.png]]
--
  (((
  AT+INTMOD=0  Disable Interrupt
  )))
@@ -652,8 +652,6 @@
  (((
  AT+INTMOD=3  Interrupt trigger by rising edge.
--
--
  )))
  == 3.4 Uplink Payload ==
@@ -681,49 +681,47 @@
  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],
  )))
  (((
--{{{    }; }}}
++    };
  )))
  (((
--}
--
--
++  }
  )))
  (((
@@ -732,67 +732,58 @@
  [[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 or LoRaWAN Downlink Commands
++User can configure RS485-BL via [[AT Commands >>path:#_Using_the_AT]]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: [[End Device AT Commands and Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]]
++* **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" %)**Sensor Related Commands**(%%): These commands are special designed for RS485-BL.  User can see these commands below:
++* **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: ===
--
--====   ====
--
--==== **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 (AT+CFGDEV)** ====
++==== [[RS485 Debug Command>>path:#downlink_A8]] (AT+CFGDEV) ====
  This command is used to configure the RS485 or TTL sensors; 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**
--)))
++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:
@@ -802,20 +802,19 @@
  * 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:
--(% 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 01 00**: to activate the RS485 Alarm
--(% style="color:#037691" %)**A8 01 06 0A 05 00 04 00 00 00**(%%): to deactivate the RS485 Alarm
++**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.
@@ -824,27 +824,25 @@
  Check TTL Sensor return:
--[[image:1654132684752-193.png]]
++[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image024.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:
--(% class="box infomessage" %)
--(((
--**AT+PAYVER: Set PAYVER field = 1**
--)))
++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 ====
@@ -1068,13 +1068,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.
@@ -1092,7 +1092,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.
@@ -1112,13 +1112,13 @@
--1.
++1.
 . LEDs
  |**LEDs**|**Feature**
  |**LED1**|Blink when device transmit a packet.
--1.
++1.
 . Switch Jumper
  |**Switch Jumper**|**Feature**
@@ -1164,7 +1164,7 @@
--1.
++1.
 . Common AT Command Sequence
 . Multi-channel ABP mode (Use with SX1301/LG308)
@@ -1183,8 +1183,8 @@
  ATZ
--1.
--11.
++1.
++11.
 . Single-channel ABP mode (Use with LG01/LG02)
  AT+FDR   Reset Parameters to Factory Default, Keys Reserve
@@ -1259,7 +1259,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.
@@ -1266,7 +1266,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]].
@@ -1283,7 +1283,7 @@
--1.
++1.
 . Why I can’t join TTN V3 in US915 /AU915 bands?
  It might about the channels mapping. Please see for detail.

1654132684752-193.png

Author

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

Size

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

Content

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

Summary

Details

Applications

Navigation