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

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

From version < 38.4 >

edited by Xiaoling
on 2022/06/02 16:30

To version < 35.2 >

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

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, 3 removed)

Details

Page properties

Content

@@ -76,6 +76,8 @@
  * 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)
@@ -87,6 +87,8 @@
  * Support Modbus protocol
  * Support Interrupt uplink (Since hardware version v1.2)
++
++
  == 1.4 Applications ==
  * Smart Buildings & Home Automation
@@ -96,6 +96,8 @@
  * 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/]]
@@ -283,6 +283,8 @@
  )))
  )))
++
++
  === 3.3.2 Configure sensors ===
  (((
@@ -301,6 +301,8 @@
  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
++
++
  === 3.3.3 Configure read commands for each sampling ===
  (((
@@ -319,9 +319,11 @@
 . How to get wanted value the from RS485 sensors returns from by 1). There are total 15 AT Commands to handle the return, commands are **AT+DATACUT1**,**AT+DATACUT2**,…, **AT+DATACUTF** corresponding to the commands from 1). All commands are of same grammar.
--3. Some RS485 device might has longer delay on reply, so user can use AT+CMDDL to set the timeout for getting reply after the RS485 command is sent. For example **AT+CMDDL1=1000** to send the open time to 1000ms
++3. Some RS485 device might has longer delay on reply, so user can use AT+CMDDL to set the timeout for getting reply after the RS485 command is sent. For example
++**AT+CMDDL1=1000** to send the open time to 1000ms
++
  After we got the valid value from each RS485 commands, we need to combine them together with the command **AT+DATAUP**.
@@ -352,9 +352,10 @@
  * **a: length for the return of AT+COMMAND**
  * **b:1: grab valid value by byte, max 6 bytes. 2: grab valid value by bytes section, max 3 sections.**
--* **c: define the position for valid value.  **
++* **c: define the position for valid value.  **
  )))
++
  **Examples:**
  * Grab bytes:
@@ -370,8 +370,6 @@
  * Grab different sections.
  [[image:image-20220602153621-3.png]]
--
--
  )))
  === 3.3.4 Compose the uplink payload ===
@@ -378,14 +378,10 @@
  (((
  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:#037691" %)**Examples: AT+DATAUP=0**
--
--
++(% style="color:#4f81bd" %)**Examples: AT+DATAUP=0**
  )))
  (((
@@ -406,10 +406,8 @@
  [[image:1653269759169-150.png||height="513" width="716"]]
++(% style="color:#4f81bd" %)**Examples: AT+DATAUP=1**
--(% style="color:#037691" %)**Examples: AT+DATAUP=1**
--
--
  Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**Multiply UPLINKs**.
  Final Payload is
@@ -416,98 +416,138 @@
  (% style="color:#4f81bd" %)**Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA**
--1. PAYVER: Defined by AT+PAYVER
--1. PAYLOAD COUNT: Total how many uplinks of this sampling.
--1. PAYLOAD#: Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT)
--1. DATA: Valid value: max 8 bytes for each uplink so each uplink <= 11 bytes. For the last uplink, DATA will might less than 8 bytes
++1. Battery Info (2 bytes): Battery voltage
++1. PAYVER (1 byte): Defined by AT+PAYVER
++1. PAYLOAD COUNT (1 byte): Total how many uplinks of this sampling.
++1. 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
--[[image:image-20220602155039-4.png]]
++[[image:1653269916228-732.png||height="433" width="711"]]
--So totally there will be 3 uplinks for this sampling, each uplink include 8 bytes DATA
++So totally there will be 3 uplinks for this sampling, each uplink includes 6 bytes DATA
--DATA1=RETURN1 Valid Value + the first two of Valid value of RETURN10= **20 20 0a 33 90 41 02 aa**
++DATA1=RETURN1 Valid Value = (% style="background-color:green; color:white" %)20 20 0a 33 90 41
--DATA2=3^^rd^^ ~~ 10^^th^^ byte of Valid value of RETURN10= **05 81 0a 20 20 20 20 2d**
++DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10=(% style="background-color:green; color:white" %) 02 aa 05 81 0a 20
--DATA3=the rest of Valid value of RETURN10= **30**
++DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 = (% style="background-color:green; color:white" %)20 20 20 2d 30
++Below are the uplink payloads:
--(% style="color:red" %)Notice: In firmware v1.3, the Max bytes has been changed according to the max bytes in different Frequency Bands for lowest SF. As below:
++[[image:1653270130359-810.png]]
--   ~* For AU915/AS923 bands, if UplinkDwell time=0, max 51 bytes for each uplink.
--   * For AU915/AS923 bands, if UplinkDwell time=0, max 11 bytes for each uplink.
++(% style="color:red" %)**Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:**
--   * For US915 band, max 11 bytes for each uplink.
++   ~* For AU915/AS923 bands, if UplinkDwell time=0, max 51 bytes for each uplink ( so 51 -5 = 46 max valid date)
--   ~* For all other bands: max 51 bytes for each uplink.
++   * For AU915/AS923 bands, if UplinkDwell time=1, max 11 bytes for each uplink ( so 11 -5 = 6 max valid date).
++   * For US915 band, max 11 bytes for each uplink ( so 11 -5 = 6 max valid date).
--Below are the uplink payloads:
++   ~* For all other bands: max 51 bytes for each uplink  ( so 51 -5 = 46 max valid date).
--[[image:1654157178836-407.png]]
--
--
  === 3.3.5 Uplink on demand ===
--Except uplink periodically, RS485-LN is able to uplink on demand. The server send downlink command to RS485-LN and RS485 will uplink data base on the command.
++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:
--**0x08 command**: Poll an uplink with current command set in RS485-LN.
++[[0x08 command>>path:#downlink_08]]: Poll an uplink with current command set in RS485-BL.
--**0xA8 command**: Send a command to RS485-LN and uplink the output from sensors.
++[[0xA8 command>>path:#downlink_A8]]: Send a command to RS485-BL and uplink the output from sensors.
--=== 3.3.6 Uplink on Interrupt ===
++1.
++11.
++111. Uplink on Interrupt
--RS485-LN support external Interrupt uplink since hardware v1.2 release.
++Put the interrupt sensor between 3.3v_out and GPIO ext.[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image022.png]]
--[[image:1654157342174-798.png]]
++AT+INTMOD=0  Disable Interrupt
--Connect the Interrupt pin to RS485-LN INT port and connect the GND pin to V- port. When there is a high voltage (Max 24v) on INT pin. Device will send an uplink packet.
++AT+INTMOD=1  Interrupt trigger by rising or falling edge.
++AT+INTMOD=2  Interrupt trigger by falling edge. ( Default Value)
--== 3.4 Uplink Payload ==
++AT+INTMOD=3  Interrupt trigger by rising edge.
--(% 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" %)(((
++
++1.
++11. Uplink Payload
++
++|**Size(bytes)**|**2**|**1**|**Length depends on the return from the commands**
++|Value|(((
  Battery(mV)
  &
  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.
++)))|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 ==
++function Decoder(bytes, port) {
--User can configure RS485-LN via AT Commands or LoRaWAN Downlink Commands
++~/~/Payload Formats of RS485-BL Deceive
--There are two kinds of Commands:
++return {
--* (% 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]]
++    ~/~/Battery,units:V
--* (% style="color:#4f81bd" %)**Sensor Related Commands**(%%): These commands are special designed for RS485-LN.  User can see these commands below:
++    BatV:((bytes[0]<<8 | bytes[1])&0x7fff)/1000,
++    ~/~/GPIO_EXTI
++    EXTI_Trigger:(bytes[0] & 0x80)? "TRUE":"FALSE",
--=== 3.5.1 Common Commands ===
++    ~/~/payload of version
--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]]
++    Pay_ver:bytes[2],
++    };
--=== 3.5.2 Sensor related commands: ===
++  }
++
++
++
++
++
++
++TTN V3 uplink screen shot.
++
++[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png]]
++
++1.
++11. Configure RS485-BL via AT or Downlink
++
++User can configure RS485-BL via [[AT Commands >>path:#_Using_the_AT]]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
++
++* **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]]
++
++
++1.
++11.
++111. 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.

1654157178836-407.png

Author

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

Size

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

Content

1654157342174-798.png

Author

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

Size

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

Content

image-20220602155039-4.png

Author

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

Size

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

Content

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

Summary

Details

Applications

Navigation