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

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

From version < 60.6 >

edited by Xiaoling
on 2022/06/14 11:13

To version < 38.3 >

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

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (2 modified, 0 added, 0 removed)
Attachments (0 modified, 0 added, 18 removed)

Details

Page properties

Title

@@ -1,1 +1,1 @@
--RS485-LN – RS485 to LoRaWAN Converter User Manual
++RS485-LN – RS485 to LoRaWAN Converter

Content

@@ -3,20 +3,15 @@
++**RS485-LN – RS485 to LoRaWAN Converter User Manual**
--
--
  **Table of Contents:**
--{{toc/}}
--
--
--
  = 1.Introduction =
  == 1.1 What is RS485-LN RS485 to LoRaWAN Converter ==
@@ -23,37 +23,23 @@
  (((
  (((
--(((
--
--
  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.
  )))
--)))
  (((
--(((
  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.
  )))
--)))
  (((
--(((
  (% 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.
  )))
--)))
  (((
--(((
  (% 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]]
--
--
  )))
  )))
--)))
  [[image:1653267211009-519.png||height="419" width="724"]]
@@ -69,15 +69,11 @@
  ** Idle: 32mA@12v
  ** 20dB Transmit: 65mA@12v
--
--
  **Interface for Model:**
  * RS485
  * Power Input 7~~ 24V DC.
--
--
  **LoRa Spec:**
  * Frequency Range:
@@ -97,11 +97,8 @@
  * Preamble detection.
  * 127 dB Dynamic Range RSSI.
  * Automatic RF Sense and CAD with ultra-fast AFC.
--* Packet engine up to 256 bytes with CRC
++* Packet engine up to 256 bytes with CRC.
--
--
--
  == 1.3 Features ==
  * LoRaWAN Class A & Class C protocol (default Class C)
@@ -113,9 +113,6 @@
  * Support Modbus protocol
  * Support Interrupt uplink (Since hardware version v1.2)
--
--
--
  == 1.4 Applications ==
  * Smart Buildings & Home Automation
@@ -125,9 +125,6 @@
  * 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/]]
@@ -137,13 +137,9 @@
  (((
  (((
--(((
  v1.2: Add External Interrupt Pin.
--)))
--(((
  v1.0: Release
--)))
  )))
@@ -171,9 +171,7 @@
  == 3.1 How it works? ==
  (((
--(((
  The RS485-LN is configured as LoRaWAN OTAA Class C mode by default. It has OTAA keys to join network. To connect a local LoRaWAN network, user just need to input the OTAA keys in the network server and power on the RS485-LN. It will auto join the network via OTAA.
--)))
  )))
@@ -196,13 +196,12 @@
  [[image:1653268227651-549.png||height="592" width="720"]]
--
  (((
--The LG308 is already set to connect to [[TTN V3 network >>path:https://www.thethingsnetwork.org/]]. So what we need to now is only configure the TTN V3:
++The LG308 is already set to connect to [[TTN V3 network >>path:eu1.cloud.thethings.network/]]. So what we need to now is only configure the TTN V3:
  )))
  (((
--**(% style="color:blue" %)Step 1**(%%): Create a device in TTN V3 with the OTAA keys from RS485-LN.
++**Step 1**: Create a device in TTN V3 with the OTAA keys from RS485-LN.
  )))
  (((
@@ -212,7 +212,6 @@
  [[image:1652953462722-299.png]]
--
  (((
  (((
  User can enter this key in their LoRaWAN Server portal. Below is TTN V3 screen shot:
@@ -219,7 +219,7 @@
  )))
  (((
--**Add APP EUI in the application.**
++Add APP EUI in the application.
  )))
  )))
@@ -235,15 +235,13 @@
  [[image:1652953542269-423.png||height="710" width="723"]]
++Add APP KEY and DEV EUI
--
--**Add APP KEY and DEV EUI**
--
  [[image:1652953553383-907.png||height="514" width="724"]]
  (((
--**(% style="color:blue" %)Step 2**(%%): Power on RS485-LN and it will auto join to the TTN V3 network. After join success, it will start to upload message to TTN V3 and user can see in the panel.
++**Step 2**: Power on RS485-LN and it will auto join to the TTN V3 network. After join success, it will start to upload message to TTN V3 and user can see in the panel.
  )))
  [[image:1652953568895-172.png||height="232" width="724"]]
@@ -253,15 +253,11 @@
  (((
  (((
--(((
--There are plenty of RS485 devices in the market and each device has different command to read the valid data. To support these devices in flexible, RS485-LN supports flexible command set. User can use [[AT Commands>>||anchor="H3.5ConfigureRS485-BLviaATorDownlink"]] or LoRaWAN Downlink Command to configure what commands RS485-LN should send for each sampling and how to handle the return from RS485 devices.
++There are plenty of RS485 devices in the market and each device has different command to read the valid data. To support these devices in flexible, RS485-LN supports flexible command set. User can use [[AT Commands>>path:#AT_COMMAND]] or LoRaWAN Downlink Command to configure what commands RS485-LN should send for each sampling and how to handle the return from RS485 devices.
  )))
--)))
  (((
--(((
  (% style="color:red" %)Note: below description and commands are for firmware version >v1.1, if you have firmware version v1.0. Please check the [[user manual v1.0>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/&file=RS485-LN_UserManual_v1.0.1.pdf]] or upgrade the firmware to v1.1
--)))
  )))
@@ -271,19 +271,19 @@
  To use RS485-LN to read data from RS485 sensors, connect the RS485-LN A/B traces to the sensors. And user need to make sure RS485-LN use the match UART setting to access the sensors. The related commands for UART settings are:
--(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)
--|=(% style="width: 110px;" %)(((
++(% border="1" style="background-color:#ffffcc; color:green; width:782px" %)
++|(% style="width:128px" %)(((
  **AT Commands**
--)))|=(% style="width: 190px;" %)(((
++)))|(% style="width:305px" %)(((
  **Description**
--)))|=(% style="width: 190px;" %)(((
++)))|(% style="width:346px" %)(((
  **Example**
  )))
--|(% style="width:110px" %)(((
++|(% style="width:128px" %)(((
  AT+BAUDR
--)))|(% style="width:190px" %)(((
++)))|(% style="width:305px" %)(((
  Set the baud rate (for RS485 connection). Default Value is: 9600.
--)))|(% style="width:190px" %)(((
++)))|(% style="width:346px" %)(((
  (((
  AT+BAUDR=9600
  )))
@@ -292,11 +292,11 @@
  Options: (1200,2400,4800,14400,19200,115200)
  )))
  )))
--|(% style="width:110px" %)(((
++|(% style="width:128px" %)(((
  AT+PARITY
--)))|(% style="width:190px" %)(((
++)))|(% style="width:305px" %)(((
  Set UART parity (for RS485 connection)
--)))|(% style="width:190px" %)(((
++)))|(% style="width:346px" %)(((
  (((
  AT+PARITY=0
  )))
@@ -305,9 +305,9 @@
  Option: 0: no parity, 1: odd parity, 2: even parity
  )))
  )))
--|(% style="width:110px" %)(((
++|(% style="width:128px" %)(((
  AT+STOPBIT
--)))|(% style="width:190px" %)(((
++)))|(% style="width:305px" %)(((
  (((
  Set serial stopbit (for RS485 connection)
  )))
@@ -315,7 +315,7 @@
  (((
  )))
--)))|(% style="width:190px" %)(((
++)))|(% style="width:346px" %)(((
  (((
  AT+STOPBIT=0 for 1bit
  )))
@@ -337,21 +337,15 @@
  )))
  )))
--(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)
--|=(% style="width: 110px;" %)**AT Commands**|=(% style="width: 190px;" %)**Description**|=(% style="width: 190px;" %)**Example**
--|AT+CFGDEV|(% style="width:110px" %)(((
--(((
++(% border="1" style="background-color:#ffffcc; color:green; width:806px" %)
++|**AT Commands**|(% style="width:418px" %)**Description**|(% style="width:256px" %)**Example**
++|AT+CFGDEV|(% style="width:418px" %)(((
  This command is used to configure the RS485/TTL devices; they won’t be used during sampling.
--)))
--(((
  AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,
--)))
--(((
  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
++)))|(% 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 ===
@@ -398,8 +398,8 @@
  **AT+DATACUTx : **This command defines how to handle the return from AT+COMMANDx, max return length is 45 bytes.
--(% border="1" style="background-color:#4bacc6; color:white; width:510px" %)
--|(% style="width:510px" %)(((
++(% border="1" style="background-color:#4bacc6; color:white; width:725px" %)
++|(% style="width:722px" %)(((
  **AT+DATACUTx=a,b,c**
  * **a: length for the return of AT+COMMAND**
@@ -468,7 +468,6 @@
  (% style="color:#4f81bd" %)**Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA**
--
 . PAYVER: Defined by AT+PAYVER
 . PAYLOAD COUNT: Total how many uplinks of this sampling.
 . PAYLOAD#: Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT)
@@ -523,986 +523,641 @@
  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.
--== 3.4 Uplink Payload ==
++1.
++11. Uplink Payload
++|**Size(bytes)**|**2**|**1**|**Length depends on the return from the commands**
++|Value|(((
++Battery(mV)
--[[image:image-20220606110929-1.png]]
++&
++Interrupt _Flag
++)))|(((
++PAYLOAD_VER
++
++
++)))|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
--(((
++return {
++
++    ~/~/Battery,units:V
++
++    BatV:((bytes[0]<<8 | bytes[1])&0x7fff)/1000,
++
++    ~/~/GPIO_EXTI
++
++    EXTI_Trigger:(bytes[0] & 0x80)? "TRUE":"FALSE",
++
++    ~/~/payload of version
++
++    Pay_ver:bytes[2],
++
++    };
++
++  }
++
++
++
++
++
++
++
++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:
--)))
--* (((
--(% 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]]
--)))
++* **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-LN.  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 ===
++RS485-BL can connect to either RS485 sensors or TTL sensor. User need to specify what type of sensor need to connect.
--Response feature is added to the server's downlink, a special package with a FPort of 200 will be uploaded immediately after receiving the data sent by the server.
++* AT Command
--[[image:image-20220602163333-5.png||height="263" width="1160"]]
++**AT+MOD=1** ~/~/ Set to support RS485-MODBUS type sensors. User can connect multiply RS485 , Modbus sensors to the A / B pins.
--The first byte of this package represents whether the configuration is successful, 00 represents failure, 01 represents success. Except for the first byte, the other is the previous downlink. (All commands except A8 type commands are applicable)
++**AT+MOD=2** ~/~/ Set to support TTL Level sensors, User can connect one TTL Sensor to the TXD/RXD/GND pins.
--=== 3.5.3 Sensor related commands ===
++* Downlink Payload
++**0A aa**     à same as AT+MOD=aa
--==== **RS485 Debug Command** ====
++==== [[RS485 Debug Command>>path:#downlink_A8]] (AT+CFGDEV) ====
--(((
--This command is used to configure the RS485 devices; they won’t be used during sampling.
--)))
++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
--)))
++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-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
--* (((
--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:**
--(((
--**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
--)))
++**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 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**)
--)))
++**Example 2:**
--(((
--User in IoT server send a downlink command: (% style="color:#4f81bd" %)**A8 01 06 0A 08 00 04 00 01 YY**
--)))
++Check TTL Sensor return:
--(((
--
--)))
++[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image024.png]]
--(((
--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 ====
--
--
--==== **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:**
--)))
--(((
--**0xAE 01**   ~-~-> Set PAYVER field =  0x01
--)))
++* Downlink Payload:
--(((
--**0xAE 0F**   ~-~-> Set PAYVER field =  0x0F
--)))
++0xAE 01   à Set PAYVER field =  0x01
++0xAE 0F   à Set PAYVER field =  0x0F
++==== Set RS485 Sampling Commands ====
--==== **Set RS485 Sampling Commands** ====
++AT+COMMANDx, AT+DATACUTx and AT+SEARCHx
--(((
--AT+COMMANDx or AT+DATACUTx
--)))
++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]].
--(((
--These three commands are used to configure how the RS485-LN polling data from Modbus device. Detail of usage please see : [[polling RS485 device>>||anchor="H3.3.3Configurereadcommandsforeachsampling"]].
--)))
--(((
--
--)))
++* AT Command:
--* (((
--**AT Command:**
--)))
++AT+COMMANDx: Configure RS485 read command to sensor.
--(% class="box infomessage" %)
--(((
--(((
--**AT+COMMANDx: Configure RS485 read command to sensor.**
--)))
--)))
++AT+DATACUTx: Configure how to handle return from RS485 devices.
--(% class="box infomessage" %)
--(((
--(((
--**AT+DATACUTx: Configure how to handle return from RS485 devices.**
--)))
--)))
++AT+SEARCHx: Configure search command
--(((
--
--)))
--* (((
--**Downlink Payload:**
--)))
++* Downlink Payload:
--(((
--**0xAF** downlink command can be used to set AT+COMMANDx or AT+DATACUTx.
--)))
++0xAF downlink command can be used to set AT+COMMANDx or AT+DATACUTx.
--(((
--(% style="color:red" %)**Note**(%%): if user use AT+COMMANDx to add a new command, he also need to send AT+DATACUTx downlink.
--)))
++Note: if user use AT+COMMANDx to add a new command, he also need to send AT+DATACUTx downlink.
--(((
  Format: AF MM NN LL XX XX XX XX YY
--)))
--(((
  Where:
--)))
--* (((
--MM: the ATCOMMAND or AT+DATACUT to be set. Value from 01 ~~ 0F,
--)))
--* (((
--NN:  0: no CRC; 1: add CRC-16/MODBUS ; 2: set the AT+DATACUT value.
--)))
--* (((
--LL:   The length of AT+COMMAND or AT+DATACUT command
--)))
--* (((
--XX XX XX XX: AT+COMMAND or AT+DATACUT command
--)))
--* (((
--YY:   If YY=0, RS485-BL will execute the downlink command without uplink; if YY=1, RS485-LN will execute an uplink after got this command.
--)))
++* MM: the ATCOMMAND or AT+DATACUT to be set. Value from 01 ~~ 0F,
++* NN: 0: no CRC; 1: add CRC-16/MODBUS ; 2: set the AT+DATACUT value.
++* LL: The length of AT+COMMAND or AT+DATACUT command
++* XX XX XX XX: AT+COMMAND or AT+DATACUT command
++* YY: If YY=0, RS485-BL will execute the downlink command without uplink; if YY=1, RS485-BL will execute an uplink after got this command.
--(((
--**Example:**
--)))
++Example:
--(((
--(% style="color:#037691" %)**AF 03 01 06 0A 05 00 04 00 01 00**(%%): Same as AT+COMMAND3=0A 05 00 04 00 01,1
--)))
++**AF 03 01 06 0A 05 00 04 00 01 00**: Same as AT+COMMAND3=0A 05 00 04 00 01,1
--(((
--(% style="color:#037691" %)**AF 03 02 06**(% style="color:orange" %)** 10 **(% style="color:red" %)**01 **(% style="color:green" %)**05 06 09 0A**(% style="color:#037691" %)** 00**(%%): Same as AT+DATACUT3=(% style="color:orange" %)**16**(%%),(% style="color:red" %)**1**(%%),(% style="color:green" %)**5+6+9+10**
--)))
++**AF 03 02 06 10 01 05 06 09 0A 00**: Same as AT+DATACUT3=**16**,**1**,**5+6+9+10**
--(((
--(% style="color:#037691" %)**AF 03 02 06 **(% style="color:orange" %)**0B**(% style="color:red" %)** 02 **(% style="color:green" %)**05 07 08 0A **(% style="color:#037691" %)**00**(%%): Same as AT+DATACUT3=(% style="color:orange" %)**11**(%%),(% style="color:red" %)**2**(%%),(% style="color:green" %)**5~~7+8~~10**
--)))
++**AF 03 02 06 0B 02 05 07 08 0A 00**: Same as AT+DATACUT3=**11**,**2**,**5~~7+8~~10**
++0xAB downlink command can be used for set AT+SEARCHx
++Example: **AB aa 01 03 xx xx xx** (03 here means there are total 3 bytes after 03) So
--==== **Fast command to handle MODBUS device** ====
++* AB aa 01 03 xx xx xx  same as AT+SEARCHaa=1,xx xx xx
++* AB aa 02 03 xx xx xx 02 yy yy(03 means there are 3 bytes after 03, they are xx xx xx;02 means there are 2 bytes after 02, they are yy yy) so the commands
--(((
--AT+MBFUN is valid since v1.3 firmware version. The command is for fast configure to read Modbus devices. It is only valid for the devices which follow the [[MODBUS-RTU protocol>>url:https://www.modbustools.com/modbus.html]].
--)))
++**AB aa 02 03 xx xx xx 02 yy yy**  same as **AT+SEARCHaa=2,xx xx xx+yy yy**
--(((
--This command is valid since v1.3 firmware version
--)))
--(((
--AT+MBFUN can auto read the Modbus function code: 01, 02, 03 or 04. AT+MBFUN has lower priority vs AT+DATACUT command. If AT+DATACUT command is configured, AT+MBFUN will be ignore.
--)))
++==== Fast command to handle MODBUS device ====
--(((
--
--)))
++AT+MBFUN is valid since v1.3 firmware version. The command is for fast configure to read Modbus devices. It is only valid for the devices which follow the [[MODBUS-RTU protocol>>url:https://www.modbustools.com/modbus.html]].
--(((
--**Example:**
--)))
++This command is valid since v1.3 firmware version
--* (((
--AT+MBFUN=1 and AT+DATACUT1/AT+DATACUT2 are not configure (0,0,0). So RS485-LN.
--)))
--* (((
--AT+COMMAND1= 01 03 00 10 00 08,1 ~-~-> read slave address 01 , function code 03, start address 00 01, quantity of registers 00 08.
--)))
--* (((
--AT+COMMAND2= 01 02 00 40 00 10,1 ~-~-> read slave address 01 , function code 02, start address 00 40, quantity of inputs 00 10.
--)))
--[[image:image-20220602165351-6.png]]
++AT+MBFUN has only two value:
--[[image:image-20220602165351-7.png]]
++* AT+MBFUN=1: Enable Modbus reading. And get response base on the MODBUS return
++AT+MBFUN=1, device can auto read the Modbus function code: 01, 02, 03 or 04. AT+MBFUN has lower priority vs AT+DATACUT command. If AT+DATACUT command is configured, AT+MBFUN will be ignore.
++* AT+MBFUN=0: Disable Modbus fast reading.
++Example:
--==== **RS485 command timeout** ====
++* AT+MBFUN=1 and AT+DATACUT1/AT+DATACUT2 are not configure (0,0,0).
++* AT+COMMAND1= 01 03 00 10 00 08,1 ~-~-> read slave address 01 , function code 03, start address 00 01, quantity of registers 00 08.
++* AT+COMMAND2= 01 02 00 40 00 10,1 ~-~-> read slave address 01 , function code 02, start address 00 40, quantity of inputs 00 10.
--(((
--Some Modbus device has slow action to send replies. This command is used to configure the RS485-LN to use longer time to wait for their action.
--)))
++[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image025.png]]
--(((
--Default value: 0, range:  0 ~~ 65 seconds
--)))
--* (((
--**AT Command:**
--)))
++[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image026.png]]
--(% class="box infomessage" %)
--(((
--(((
--**AT+CMDDLaa=hex(bb cc)*1000**
--)))
--)))
--(((
--**Example:**
--)))
++* Downlink Commands:
--(((
--**AT+CMDDL1=1000** to send the open time to 1000ms
--)))
++A9 aa -à Same as AT+MBFUN=aa
--(((
--
--)))
--* (((
--**Downlink Payload:**
--)))
++==== RS485 command timeout ====
--(((
--**0x AA aa bb cc**
--)))
++Some Modbus device has slow action to send replies. This command is used to configure the RS485-BL to use longer time to wait for their action.
--(((
--Same as: AT+CMDDLaa=hex(bb cc)*1000
--)))
++Default value: 0, range:  0 ~~ 5 seconds
--(((
--   **Example:**
--)))
--(((
--   0xAA 01 00 01  ~-~-> Same as **AT+CMDDL1=1000 ms**
--)))
++* AT Command:
++AT+CMDDLaa=hex(bb cc)
++Example:
++**AT+CMDDL1=1000** to send the open time to 1000ms
--==== **Uplink payload mode** ====
--(((
--Define to use one uplink or multiple uplinks for the sampling.
--)))
++* Downlink Payload:
--(((
--The use of this command please see: [[Compose Uplink payload>>||anchor="H3.3.4Composetheuplinkpayload"]]
--)))
++0x AA aa bb cc
--* (((
--**AT Command:**
--)))
++Same as: AT+CMDDLaa=hex(bb cc)
--(% class="box infomessage" %)
--(((
--(((
--**AT+DATAUP=0**
--)))
--)))
++   Example:
--(% class="box infomessage" %)
--(((
--(((
--**AT+DATAUP=1**
--)))
--)))
++   0xAA 01 03 E8  à Same as **AT+CMDDL1=1000 ms**
--(((
--
--)))
--* (((
--**Downlink Payload:**
--)))
++==== [[Uplink>>path:#downlink_A8]] payload mode ====
--(((
--**0xAD 00**   **~-~->** Same as AT+DATAUP=0
--)))
++Define to use one uplink or multiple uplinks for the sampling.
--(((
--**0xAD 01**   **~-~->** Same as AT+DATAUP=1
--)))
++The use of this command please see: [[Compose Uplink payload>>path:#DataUP]]
++* AT Command:
++AT+DATAUP=0
++AT+DATAUP=1
--==== **Manually trigger an Uplink** ====
--(((
--Ask device to send an uplink immediately.
--)))
++* Downlink Payload:
--* (((
--**AT Command:**
--)))
++0xAD 00   à Same as AT+DATAUP=0
--(((
--No AT Command for this, user can press the [[ACT button>>||anchor="H3.7Buttons"]] for 1 second for the same.
--)))
++0xAD 01   à Same as AT+DATAUP=1
--(((
--
--)))
--* (((
--**Downlink Payload:**
--)))
++==== Manually trigger an Uplink ====
--(((
--**0x08 FF**, RS485-LN will immediately send an uplink.
--)))
++Ask device to send an uplink immediately.
++* Downlink Payload:
++0x08 FF, RS485-BL will immediately send an uplink.
--==== **Clear RS485 Command** ====
++==== Clear RS485 Command ====
--(((
  The AT+COMMANDx and AT+DATACUTx settings are stored in special location, user can use below command to clear them.
--)))
--* (((
--**AT Command:**
--)))
--(((
++* AT Command:
++
  **AT+CMDEAR=mm,nn**   mm: start position of erase ,nn: stop position of erase
--)))
--(((
  Etc. AT+CMDEAR=1,10 means erase AT+COMMAND1/AT+DATACUT1 to AT+COMMAND10/AT+DATACUT10
--)))
--(((
  Example screen shot after clear all RS485 commands.
--)))
--(((
--
--)))
--(((
++
  The uplink screen shot is:
--)))
--[[image:1654160691922-496.png]]
++[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png]]
--* (((
--**Downlink Payload:**
--)))
++* Downlink Payload:
--(((
--**0x09 aa bb**  same as AT+CMDEAR=aa,bb
--)))
++0x09 aa bb  same as AT+CMDEAR=aa,bb
++==== Set Serial Communication Parameters ====
--
--==== **Set Serial Communication Parameters** ====
--
--(((
  Set the Rs485 serial communication parameters:
--)))
--* (((
--**AT Command:**
--)))
++* AT Command:
--(((
  Set Baud Rate:
--)))
--(% class="box infomessage" %)
--(((
--(((
--**AT+BAUDR=9600**    ~/~/ Options: (1200,2400,4800,14400,19200,115200)
--)))
--)))
++AT+BAUDR=9600    ~/~/ Options: (1200,2400,4800,14400,19200,115200)
--(((
--Set UART Parity
--)))
--(% class="box infomessage" %)
--(((
--(((
--**AT+PARITY=0**    ~/~/ Option: 0: no parity, 1: odd parity, 2: even parity
--)))
--)))
++Set UART parity
--(((
++AT+PARITY=0    ~/~/ Option: 0: no parity, 1: odd parity, 2: even parity
++
++
  Set STOPBIT
--)))
--(% class="box infomessage" %)
--(((
--(((
--**AT+STOPBIT=0**    ~/~/ Option: 0 for 1bit; 1 for 1.5 bit ; 2 for 2 bits
--)))
--)))
++AT+STOPBIT=0    ~/~/ Option: 0 for 1bit; 1 for 1.5 bit ; 2 for 2 bits
--(((
--
--)))
--* (((
--**Downlink Payload:**
--)))
++* Downlink Payload:
--(((
--**A7 01 aa bb**: Same  AT+BAUDR=hex(aa bb)*100
--)))
++A7 01 aa bb: Same  AT+BAUDR=hex(aa bb)*100
--(((
--**Example:**
--)))
++Example:
--* (((
--A7 01 00 60   same as AT+BAUDR=9600
--)))
--* (((
--A7 01 04 80     same as AT+BAUDR=115200
--)))
++* A7 01 00 60   same as AT+BAUDR=9600
++* A7 01 04 80     same as AT+BAUDR=115200
--(((
  A7 02 aa: Same as  AT+PARITY=aa  (aa value: 00 , 01 or 02)
--)))
--(((
  A7 03 aa: Same as  AT+STOPBIT=aa  (aa value: 00 , 01 or 02)
--)))
++==== Control output power duration ====
++User can set the output power duration before each sampling.
--== 3.6 Listening mode for RS485 network ==
++* AT Command:
--(((
--This feature support since firmware v1.4
--)))
++Example:
--(((
--RS485-LN supports listening mode, it can listen the RS485 network packets and send them via LoRaWAN uplink. Below is the structure. The blue arrow shows the RS485 network packets to RS485-LN.
--)))
++AT+3V3T=1000 ~/~/ 3V3 output power will open 1s before each sampling.
--[[image:image-20220602171200-8.png||height="567" width="1007"]]
++AT+5VT=1000 ~/~/ +5V output power will open 1s before each sampling.
--(((
--To enable the listening mode, use can run the command AT+RXMODE.
--)))
--(((
--
--)))
++* LoRaWAN Downlink Command:
--(% border="1" cellspacing="10" style="background-color:#ffffcc; width:500px" %)
--|=(% style="width: 100px;" %)(((
--**Command example**
--)))|=(% style="width: 400px;" %)(((
--**Function**
--)))
--|(% style="width:100px" %)(((
--AT+RXMODE=1,10
--)))|(% style="width:400px" %)(((
--Enable listening mode 1, if RS485-LN has received more than 10 RS485 commands from the network. RS485-LN will send these commands via LoRaWAN uplinks.
--)))
--|(% style="width:100px" %)(((
--AT+RXMODE=2,500
--)))|(% style="width:400px" %)(((
--Enable listening mode 2, RS485-LN will capture and send a 500ms content once from the first detect of character. Max value is 65535 ms
--)))
--|(% style="width:100px" %)(((
--AT+RXMODE=0,0
--)))|(% style="width:400px" %)(((
--Disable listening mode. This is the default settings.
--)))
--|(% style="width:100px" %)(((
--
--)))|(% style="width:400px" %)(((
--A6 aa bb cc  same as AT+RXMODE=aa,(bb<<8 | cc)
--)))
++07 01 aa bb  Same as AT+5VT=(aa bb)
--(((
--**Downlink Command:**
--)))
++07 02 aa bb  Same as AT+3V3T=(aa bb)
--(((
--**0xA6 aa bb cc ** same as AT+RXMODE=aa,(bb<<8 | cc)
--)))
--(((
--
--)))
--(((
--**Example**:
--)))
--(((
--The RS485-LN is set to AT+RXMODE=2,1000
--)))
++1.
++11. Buttons
--(((
--There is a two Modbus commands in the RS485 network as below:
--)))
++|**Button**|**Feature**
++|**RST**|Reboot RS485-BL
--(((
--The Modbus master send a command: (% style="background-color:#ffc000" %)01 03 00 00 00 02 c4 0b
--)))
++1.
++11. +3V3 Output
--(((
--And Modbus slave reply with: (% style="background-color:green" %)01 03 04 00 00 00 00 fa 33
--)))
++RS485-BL has a Controllable +3V3 output, user can use this output to power external sensor.
--(((
--RS485-LN will capture both and send the uplink: (% style="background-color:#ffc000" %)01 03 00 00 00 02 c4 0b  (% style="background-color:green" %)01 03 04 00 00 00 00 fa 33
--)))
++The +3V3 output will be valid for every sampling. RS485-BL will enable +3V3 output before all sampling and disable the +3V3 after all sampling.
--(((
--[[image:image-20220602171200-9.png]]
--)))
--(((
--
--)))
++The +3V3 output time can be controlled by AT Command.
--(((
--(((
--(% style="color:red" %)Notice: Listening mode can work with the default polling mode of RS485-LN. When RS485-LN is in to send the RS485 commands (from AT+COMMANDx), the listening mode will be interrupt for a while.
--)))
--)))
++**AT+3V3T=1000**
++Means set +3v3 valid time to have 1000ms. So, the real +3v3 output will actually have 1000ms + sampling time for other sensors.
--== 3.7 Buttons ==
++By default, the AT+3V3T=0. This is a special case, means the +3V3 output is always on at any time
--(% border="1" cellspacing="10" style="background-color:#f7faff; width:430px" %)
--|=(% style="width: 50px;" %)**Button**|=(% style="width: 361px;" %)**Feature**
--|(% style="width:50px" %)**ACT**|(% style="width:361px" %)If RS485 joined in network, press this button for more than 1 second, RS485 will upload a packet, and the SYS LED will give a (% style="color:blue" %)**Blue blink**
--|(% style="width:50px" %)**RST**|(% style="width:361px" %)Reboot RS485
--|(% style="width:50px" %)**PRO**|(% style="width:361px" %)Use for upload image, see [[How to Update Image>>||anchor="H6.1Howtoupgradetheimage3F"]]
--== 3.8 LEDs ==
++1.
++11. +5V Output
++RS485-BL has a Controllable +5V output, user can use this output to power external sensor.
--(% border="1" cellspacing="10" style="background-color:#f7faff; width:430px" %)
--|=(% style="width: 50px;" %)**LEDs**|=(% style="width: 380px;" %)**Feature**
--|**PWR**|Always on if there is power
--|**SYS**|After device is powered on, the SYS will (% style="color:green" %)**fast blink in GREEN**(%%) for 5 times, means RS485-LN start to join LoRaWAN network. If join success, SYS will be (% style="color:green" %)**on GREEN for 5 seconds** (%%)**. **SYS will (% style="color:green" %)**blink Blue**(%%) on every upload and (% style="color:green" %)**blink Green**(%%) once receive a downlink message.
++The +5V output will be valid for every sampling. RS485-BL will enable +5V output before all sampling and disable the +5v after all sampling.
--= 4. Case Study =
--User can check this URL for some case studies: [[APP RS485 COMMUNICATE WITH SENSORS>>doc:Main.Application Note \: Communicate with Different Sensors ----- RS485-LN  RS485-BL.WebHome]]
++The 5V output time can be controlled by AT Command.
++**AT+5VT=1000**
--= 5. Use AT Command =
++Means set 5V valid time to have 1000ms. So, the real 5V output will actually have 1000ms + sampling time for other sensors.
--== 5.1 Access AT Command ==
--(((
--RS485-BL supports AT Command set. User can use a USB to TTL adapter plus the 3.5mm Program Cable to connect to RS485-BL to use AT command, as below.
--)))
++By default, the AT+5VT=0. If the external sensor which require 5v and require more time to get stable state, user can use this command to increase the power ON duration for this sensor.
--[[image:1654162355560-817.png]]
--(((
--In PC, User needs to set (% style="color:blue" %)**serial tool**(%%)(such as [[putty>>url:https://www.chiark.greenend.org.uk/~~sgtatham/putty/latest.html]], SecureCRT) baud rate to (% style="color:green" %)**9600**(%%) to access to access serial console of RS485-BL. The default password is 123456. Below is the output for reference:
--)))
--[[image:1654162368066-342.png]]
++1.
++11. LEDs
++|**LEDs**|**Feature**
++|**LED1**|Blink when device transmit a packet.
--(((
--More detail AT Command manual can be found at [[AT Command Manual>>https://www.dragino.com/downloads/index.php?dir=LT_LoRa_IO_Controller/LT33222-L/]]
++1.
++11. Switch Jumper
++
++|**Switch Jumper**|**Feature**
++|**SW1**|(((
++ISP position: Upgrade firmware via UART
++
++Flash position: Configure device, check running status.
  )))
++|**SW2**|(((
++5V position: set to compatible with 5v I/O.
++3.3v position: set to compatible with 3.3v I/O.,
++)))
+++3.3V: is always ON
--== 5.2 Common AT Command Sequence ==
+++5V: Only open before every sampling. The time is by default, it is AT+5VT=0.  Max open time. 5000 ms.
--=== 5.2.1 Multi-channel ABP mode (Use with SX1301/LG308) ===
++1. Case Study
--If device has not joined network yet:
++User can check this URL for some case studies.
--(% class="box infomessage" %)
--(((
--**AT+FDR**
--)))
++[[http:~~/~~/wiki.dragino.com/index.php?title=APP_RS485_COMMUNICATE_WITH_SENSORS>>url:http://wiki.dragino.com/index.php?title=APP_RS485_COMMUNICATE_WITH_SENSORS]]
--(% class="box infomessage" %)
--(((
--**AT+NJM=0**
--)))
--(% class="box infomessage" %)
--(((
--**ATZ**
--)))
--(((
--If device already joined network:
--)))
++1. Use AT Command
++11. Access AT Command
--(% class="box infomessage" %)
--(((
--**AT+NJM=0**
--)))
++RS485-BL supports AT Command set. User can use a USB to TTL adapter plus the 3.5mm Program Cable to connect to RS485-BL to use AT command, as below.
--(% class="box infomessage" %)
--(((
--**ATZ**
--)))
++[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image027.png]]
--=== 5.5.2 Single-channel ABP mode (Use with LG01/LG02) ===
++In PC, User needs to set **serial tool**(such as [[putty>>url:https://www.chiark.greenend.org.uk/~~sgtatham/putty/latest.html]], SecureCRT) baud rate to **9600** to access to access serial console of RS485-BL. The default password is 123456. Below is the output for reference:
++[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image028.png]]
--(% style="background-color:#dcdcdc" %)**AT+FDR** (%%)      Reset Parameters to Factory Default, Keys Reserve
--(% style="background-color:#dcdcdc" %)**AT+NJM=0 **(%%)Set to ABP mode
--(% style="background-color:#dcdcdc" %)**AT+ADR=0** (%%)Set the Adaptive Data Rate Off
++More detail AT Command manual can be found at [[AT Command Manual>>path:#AT_COMMAND]]
--(% style="background-color:#dcdcdc" %)**AT+DR=5**   (%%)Set Data Rate
--(% style="background-color:#dcdcdc" %)**AT+TDC=60000** (%%) Set transmit interval to 60 seconds
--(% style="background-color:#dcdcdc" %)**AT+CHS=868400000**(%%) Set transmit frequency to 868.4Mhz
++1.
++11. Common AT Command Sequence
++111. Multi-channel ABP mode (Use with SX1301/LG308)
--(% style="background-color:#dcdcdc" %)**AT+RX2FQ=868400000** (%%) Set RX2Frequency to 868.4Mhz (according to the result from server)
++If device has not joined network yet:
--(% style="background-color:#dcdcdc" %)**AT+RX2DR=5**  (%%) Set RX2DR to match the downlink DR from server. see below
++AT+FDR
--(% style="background-color:#dcdcdc" %)**AT+DADDR=26** (%%) 01 1A F1 Set Device Address to 26 01 1A F1, this ID can be found in the LoRa Server portal.
++AT+NJM=0
--(% style="background-color:#dcdcdc" %)**ATZ**       (%%)   Reset MCU
++ATZ
--(% style="color:red" %)**Note:**
++If device already joined network:
--(((
--(% style="color:red" %)1. Make sure the device is set to ABP mode in the IoT Server.
--2. Make sure the LG01/02 gateway RX frequency is exactly the same as AT+CHS setting.
--3. Make sure SF / bandwidth setting in LG01/LG02 match the settings of AT+DR. refer [[this link>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/&file=LoRaWAN%201.0.3%20Regional%20Parameters.xlsx]] to see what DR means.
--4. The command AT+RX2FQ and AT+RX2DR is to let downlink work. to set the correct parameters, user can check the actually downlink parameters to be used. As below. Which shows the RX2FQ should use 868400000 and RX2DR should be 5
--)))
++AT+NJM=0
--[[image:1654162478620-421.png]]
++ATZ
++1.
++11.
++111. Single-channel ABP mode (Use with LG01/LG02)
--= 6. FAQ =
++AT+FDR   Reset Parameters to Factory Default, Keys Reserve
--== 6.1 How to upgrade the image? ==
++AT+NJM=0 Set to ABP mode
--(((
--The RS485-LN LoRaWAN Controller is shipped with a 3.5mm cable, the cable is used to upload image to RS485-LN to:
--)))
++AT+ADR=0 Set the Adaptive Data Rate Off
--* (((
--Support new features
--)))
--* (((
--For bug fix
--)))
--* (((
--Change LoRaWAN bands.
--)))
++AT+DR=5  Set Data Rate
--(((
--Below shows the hardware connection for how to upload an image to RS485-LN:
--)))
++AT+TDC=60000  Set transmit interval to 60 seconds
--[[image:1654162535040-878.png]]
++AT+CHS=868400000 Set transmit frequency to 868.4Mhz
--(((
--**Step1:** Download [[flash loader>>url:https://www.st.com/content/st_com/en/products/development-tools/software-development-tools/stm32-software-development-tools/stm32-programmers/flasher-stm32.html]].
--)))
++AT+RX2FQ=868400000 Set RX2Frequency to 868.4Mhz (according to the result from server)
--(((
--**Step2**: Download the [[LT Image files>>url:http://www.dragino.com/downloads/index.php?dir=LT_LoRa_IO_Controller/LT33222-L/image/]].
--)))
++AT+RX2DR=5  Set RX2DR to match the downlink DR from server. see below
--(((
--**Step3: **Open flashloader; choose the correct COM port to update.
--)))
++AT+DADDR=26 01 1A F1 Set Device Address to 26 01 1A F1, this ID can be found in the LoRa Server portal.
--(((
--(((
--(((
--(% style="color:blue" %) Hold down the PRO button and then momentarily press the RST reset button and the SYS led will change from OFF to ON, While SYS LED is RED ON, it means the RS485-LN is ready to be program.
--)))
--)))
--)))
++ATZ          Reset MCU
++**Note:**
--[[image:image-20220602175818-12.png]]
++1. Make sure the device is set to ABP mode in the IoT Server.
++1. Make sure the LG01/02 gateway RX frequency is exactly the same as AT+CHS setting.
++1. Make sure SF / bandwidth setting in LG01/LG02 match the settings of AT+DR. refer [[this link>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/&file=LoRaWAN%201.0.3%20Regional%20Parameters.xlsx]] to see what DR means.
++1. The command AT+RX2FQ and AT+RX2DR is to let downlink work. to set the correct parameters, user can check the actually downlink parameters to be used. As below. Which shows the RX2FQ should use 868400000 and RX2DR should be 5
++[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image029.png]]
--[[image:image-20220602175848-13.png]]
++1. FAQ
++11. How to upgrade the image?
--[[image:image-20220602175912-14.png]]
++The RS485-BL LoRaWAN Controller is shipped with a 3.5mm cable, the cable is used to upload image to RS485-BL to:
++* Support new features
++* For bug fix
++* Change LoRaWAN bands.
--**Notice**: In case user has lost the program cable. User can hand made one from a 3.5mm cable. The pin mapping is:
++Below shows the hardware connection for how to upload an image to RS485-BL:
--[[image:image-20220602175638-10.png]]
++[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image030.png]]
++**Step1:** Download [[flash loader>>url:https://www.st.com/content/st_com/en/products/development-tools/software-development-tools/stm32-software-development-tools/stm32-programmers/flasher-stm32.html]].
--== 6.2 How to change the LoRa Frequency Bands/Region? ==
++**Step2**: Download the [[LT Image files>>url:http://www.dragino.com/downloads/index.php?dir=LT_LoRa_IO_Controller/LT33222-L/image/]].
--User can follow the introduction for [[how to upgrade image>>||anchor="H6.1Howtoupgradetheimage3F"]]. When download the images, choose the required image file for download.
++**Step3: **Open flashloader; choose the correct COM port to update.
--== 6.3 How many RS485-Slave can RS485-BL connects? ==
++|(((
++HOLD PRO then press the RST button, SYS will be ON, then click next
++)))
--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>>||anchor="H3.3.3Configurereadcommandsforeachsampling"]].
++|(((
++Board detected
++)))
++|(((
++
++)))
--== 6.4 Compatible question to ChirpStack and TTI LoRaWAN server ? ==
++[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image031.png]]            [[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image032.png]]
--When user need to use with ChirpStack or TTI. Please set AT+RPL=4.
--Detail info check this link: [[Set Packet Receiving Response Level>>doc:Main.End Device AT Commands and Downlink Command.WebHome||anchor="H7.23SetPacketReceivingResponseLevel"]]
++[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image033.png]]           [[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image034.png]]
--= 7. Trouble Shooting =
--== 7.1 Downlink doesn’t work, how to solve it? ==
++[[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]]
--Please see this link for debug: [[LoRaWAN Communication Debug>>doc:Main.LoRaWAN Communication Debug.WebHome]]
++1.
++11. How to change the LoRa Frequency Bands/Region?
--== 7.2 Why I can’t join TTN V3 in US915 /AU915 bands? ==
++User can follow the introduction for [[how to upgrade image>>path:#upgrade_image]]. When download the images, choose the required image file for download.
--It might about the channels mapping. Please see for detail: [[Notice of Frequency band>>doc:Main.LoRaWAN Communication Debug.WebHome||anchor="H2.NoticeofUS9152FCN4702FAU915Frequencyband"]]
--= 8. Order Info =
++1.
++11. How many RS485-Slave can RS485-BL connects?
--(% style="color:blue" %)**Part Number: RS485-LN-XXX**
++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]].
--(% style="color:blue" %)**XXX:**
--* (% style="color:blue" %)**EU433**(%%): frequency bands EU433
--* (% style="color:blue" %)**EU868**(%%): frequency bands EU868
--* (% style="color:blue" %)**KR920**(%%): frequency bands KR920
--* (% style="color:blue" %)**CN470**(%%): frequency bands CN470
--* (% style="color:blue" %)**AS923**(%%): frequency bands AS923
--* (% style="color:blue" %)**AU915**(%%): frequency bands AU915
--* (% style="color:blue" %)**US915**(%%): frequency bands US915
--* (% style="color:blue" %)**IN865**(%%): frequency bands IN865
--* (% style="color:blue" %)**RU864**(%%): frequency bands RU864
--* (% style="color:blue" %)**KZ865**(%%): frequency bands KZ865
--= 9.Packing Info =
++1. Trouble Shooting
++11. Downlink doesn’t work, how to solve it?
--**Package Includes**:
++Please see this link for debug:
--* RS485-LN x 1
--* Stick Antenna for LoRa RF part x 1
--* Program cable x 1
++[[http:~~/~~/wiki.dragino.com/index.php?title=Main_Page#LoRaWAN_Communication_Debug>>url:http://wiki.dragino.com/index.php?title=Main_Page#LoRaWAN_Communication_Debug]]
--**Dimension and weight**:
--* Device Size: 13.5 x 7 x 3 cm
--* Device Weight: 105g
--* Package Size / pcs : 14.5 x 8 x 5 cm
--* Weight / pcs : 170g
--= 10. FCC Caution for RS485LN-US915 =
++1.
++11. Why I can’t join TTN V3 in US915 /AU915 bands?
--(((
--Any Changes or modifications not expressly approved by the party responsible for compliance could void the user's authority to operate the equipment.
--)))
++It might about the channels mapping. Please see for detail.
--(((
--This device complies with part 15 of the FCC Rules. Operation is subject to the following two conditions: (1) This device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation.
--)))
++[[http:~~/~~/wiki.dragino.com/index.php?title=LoRaWAN_Communication_Debug#Notice_of_US915.2FCN470.2FAU915_Frequency_band>>url:http://wiki.dragino.com/index.php?title=LoRaWAN_Communication_Debug#Notice_of_US915.2FCN470.2FAU915_Frequency_band]]
--(((
--
--)))
--(((
--**IMPORTANT NOTE:**
--)))
--(((
--**Note: **This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses and can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications. However, there is no guarantee that interference will not occur in a particular installation. If this equipment does cause harmful interference to radio or television reception, which can be determined by turning the equipment off and on, the user is encouraged to try to correct the interference by one or more of the following measures:
--)))
++1. Order Info
--(((
--—Reorient or relocate the receiving antenna.
--)))
++**Part Number: RS485-BL-XXX**
--(((
--—Increase the separation between the equipment and receiver.
--)))
++**XXX:**
--(((
--—Connect the equipment into an outlet on a circuit different from that to which the receiver is connected.
--)))
++* **EU433**: frequency bands EU433
++* **EU868**: frequency bands EU868
++* **KR920**: frequency bands KR920
++* **CN470**: frequency bands CN470
++* **AS923**: frequency bands AS923
++* **AU915**: frequency bands AU915
++* **US915**: frequency bands US915
++* **IN865**: frequency bands IN865
++* **RU864**: frequency bands RU864
++* **KZ865: **frequency bands KZ865
--(((
--—Consult the dealer or an experienced radio/TV technician for help.
--)))
++1. Packing Info
--(((
--
--)))
++**Package Includes**:
--(((
--**FCC Radiation Exposure Statement:**
--)))
++* RS485-BL x 1
++* Stick Antenna for LoRa RF part x 1
++* Program cable x 1
--(((
--This equipment complies with FCC radiation exposure limits set forth for an uncontrolled environment.This equipment should be installed and operated with minimum distance 20cm between the radiator& your body.
--)))
++**Dimension and weight**:
++* Device Size: 13.5 x 7 x 3 cm
++* Device Weight: 105g
++* Package Size / pcs : 14.5 x 8 x 5 cm
++* Weight / pcs : 170g
--= 11. Support =
++1. Support
--* (((
--Support is provided Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different timezones we cannot offer live support. However, your questions will be answered as soon as possible in the before-mentioned schedule.
--)))
--* (((
--Provide as much information as possible regarding your enquiry (product models, accurately describe your problem and steps to replicate it etc) and send a mail to [[support@dragino.com>>url:file:///D:/市场资料/说明书/LoRa/LT系列/support@dragino.com]].
--)))
++* Support is provided Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different timezones we cannot offer live support. However, your questions will be answered as soon as possible in the before-mentioned schedule.
++* Provide as much information as possible regarding your enquiry (product models, accurately describe your problem and steps to replicate it etc) and send a mail to
++
++[[support@dragino.com>>url:file:///D:/市场资料/说明书/LoRa/LT系列/support@dragino.com]]

1654158783574-851.png

Author

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

Size

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

Content

1654159460680-153.png

Author

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

Size

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

Content

1654160691922-496.png

Author

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

Size

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

Content

1654162355560-817.png

Author

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

Size

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

Content

1654162368066-342.png

Author

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

Size

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

Content

1654162478620-421.png

Author

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

Size

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

Content

1654162535040-878.png

Author

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

Size

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

Content

image-20220602163333-5.png

Author

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

Size

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

Content

image-20220602165351-6.png

Author

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

Size

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

Content

image-20220602165351-7.png

Author

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

Size

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

Content

image-20220602171200-8.png

Author

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

Size

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

Content

image-20220602171200-9.png

Author

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

Size

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

Content

image-20220602175638-10.png

Author

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

Size

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

Content

image-20220602175743-11.png

Author

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

Size

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

Content

image-20220602175818-12.png

Author

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

Size

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

Content

image-20220602175848-13.png

Author

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

Size

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

Content

image-20220602175912-14.png

Author

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

Size

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

Content

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