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

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

From version < 42.3 >

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

To version < 40.1 >

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

Change comment: Uploaded new attachment "image-20220602163333-5.png", version {1}

Raw
Rendered

Summary

Page properties (1 modified, 0 added, 0 removed)
Attachments (0 modified, 0 added, 1 removed)
- 1654159460680-153.png

Details

Page properties

Content

@@ -499,39 +499,46 @@
  * (% 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]]
--=== 3.5.2 Sensor related commands ===
++=== 3.5.2 Sensor related commands: ===
--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.
++==== Choose Device Type (RS485 or TTL) ====
--[[image:image-20220602163333-5.png||height="263" width="1160"]]
++RS485-BL can connect to either RS485 sensors or TTL sensor. User need to specify what type of sensor need to connect.
--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 Command
++**AT+MOD=1** ~/~/ Set to support RS485-MODBUS type sensors. User can connect multiply RS485 , Modbus sensors to the A / B pins.
--=== 3.5.3 Sensor related commands ===
++**AT+MOD=2** ~/~/ Set to support TTL Level sensors, User can connect one TTL Sensor to the TXD/RXD/GND pins.
--====   ====
--==== **RS485 Debug Command** ====
++* Downlink Payload
--This command is used to configure the RS485 devices; they won’t be used during sampling.
++**0A aa**     à same as AT+MOD=aa
--* **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
++==== [[RS485 Debug Command>>path:#downlink_A8]] (AT+CFGDEV) ====
--* **Downlink Payload**
++This command is used to configure the RS485 or TTL sensors; they won’t be used during sampling.
++* AT Command
++
++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
++
  Format: A8 MM NN XX XX XX XX YY
  Where:
@@ -539,12 +539,9 @@
  * 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.
++* 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** ~-~-> Configure without ask for uplink (YY=0)
++**Example 1:**
  To connect a Modbus Alarm with below commands.
@@ -554,76 +554,59 @@
  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:**
++* 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>>||anchor="H3.3.3Configurereadcommandsforeachsampling"]].
++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]].
--* **AT Command:**
++* AT Command:
--(% class="box infomessage" %)
--(((
--**AT+COMMANDx: Configure RS485 read command to sensor.**
--)))
++AT+COMMANDx: Configure RS485 read command to sensor.
--(% class="box infomessage" %)
--(((
--**AT+DATACUTx: Configure how to handle return from RS485 devices.**
--)))
++AT+DATACUTx: Configure how to handle return from RS485 devices.
--(% class="box infomessage" %)
--(((
--**AT+SEARCHx: Configure search command**
--)))
++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
@@ -630,23 +630,23 @@
  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
++* 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.
++* 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
++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
++Example: **AB aa 01 03 xx xx xx** (03 here means there are total 3 bytes after 03) So
  * 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
@@ -654,164 +654,145 @@
  **AB aa 02 03 xx xx xx 02 yy yy**  same as **AT+SEARCHaa=2,xx xx xx+yy yy**
++==== Fast command to handle MODBUS device ====
--==== **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]].
  This command is valid since v1.3 firmware version
--**AT+MBFUN has only two value:**
++AT+MBFUN has only two value:
--* **AT+MBFUN=1**: Enable Modbus reading. And get response base on the MODBUS return
++* 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.
++* AT+MBFUN=0: Disable Modbus fast reading.
--**Example:**
++Example:
  * 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.
--[[image:1654133913295-597.png]]
++[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image025.png]]
--[[image:1654133954153-643.png]]
++[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image026.png]]
--* **Downlink Commands:**
++* Downlink Commands:
--**A9 aa** ~-~-> Same as AT+MBFUN=aa
++A9 aa -à Same as AT+MBFUN=aa
++==== RS485 command timeout ====
--==== **RS485 command timeout** ====
--
  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.
  Default value: 0, range:  0 ~~ 5 seconds
--* **AT Command:**
++* AT Command:
--(% class="box infomessage" %)
--(((
--**AT+CMDDLaa=hex(bb cc)**
--)))
++AT+CMDDLaa=hex(bb cc)
--**Example:**
++Example:
  **AT+CMDDL1=1000** to send the open time to 1000ms
--* **Downlink Payload:**
++* Downlink Payload:
 x AA aa bb cc
  Same as: AT+CMDDLaa=hex(bb cc)
--   **Example:**
++   Example:
--   **0xAA 01 03 E8**  ~-~-> Same as **AT+CMDDL1=1000 ms**
++   0xAA 01 03 E8  à Same as **AT+CMDDL1=1000 ms**
++==== [[Uplink>>path:#downlink_A8]] payload mode ====
--==== **Uplink payload mode** ====
--
  Define to use one uplink or multiple uplinks for the sampling.
--The use of this command please see: [[Compose Uplink payload>>||anchor="H3.3.4Composetheuplinkpayload"]]
++The use of this command please see: [[Compose Uplink payload>>path:#DataUP]]
--* **AT Command:**
++* AT Command:
--(% class="box infomessage" %)
--(((
--**AT+DATAUP=0**
--)))
++AT+DATAUP=0
--(% class="box infomessage" %)
--(((
--**AT+DATAUP=1**
--)))
++AT+DATAUP=1
--* **Downlink Payload:**
++* Downlink Payload:
--**0xAD 00**   **~-~->** Same as AT+DATAUP=0
++0xAD 00   à Same as AT+DATAUP=0
--**0xAD 01**   **~-~->** Same as AT+DATAUP=1
++0xAD 01   à Same as AT+DATAUP=1
++==== Manually trigger an Uplink ====
--==== **Manually trigger an Uplink** ====
--
  Ask device to send an uplink immediately.
--* **Downlink Payload:**
++* Downlink Payload:
--**0x08 FF**, RS485-BL will immediately send an uplink.
++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:
--(% style="color:#037691" %)**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
++**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:1654134704555-320.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
@@ -821,22 +821,287 @@
  A7 03 aa: Same as  AT+STOPBIT=aa  (aa value: 00 , 01 or 02)
++==== Control output power duration ====
--==== **Control output power duration** ====
--
  User can set the output power duration before each sampling.
--* **AT Command:**
++* AT Command:
--**Example:**
++Example:
--**AT+3V3T=1000**  ~/~/ 3V3 output power will open 1s before each sampling.
++AT+3V3T=1000 ~/~/ 3V3 output power will open 1s before each sampling.
--**AT+5VT=1000**  ~/~/ +5V output power will open 1s before each sampling.
++AT+5VT=1000 ~/~/ +5V output power will open 1s before each sampling.
--* **LoRaWAN Downlink Command:**
++* LoRaWAN Downlink Command:
--**07 01 aa bb**  Same as AT+5VT=(aa bb)
++07 01 aa bb  Same as AT+5VT=(aa bb)
--**07 02 aa bb**  Same as AT+3V3T=(aa bb)
++07 02 aa bb  Same as AT+3V3T=(aa bb)
++
++
++
++
++1.
++11. Buttons
++
++|**Button**|**Feature**
++|**RST**|Reboot RS485-BL
++
++1.
++11. +3V3 Output
++
++RS485-BL has a Controllable +3V3 output, user can use this output to power external sensor.
++
++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.
++
++
++The +3V3 output time can be controlled by AT Command.
++
++**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.
++
++
++By default, the AT+3V3T=0. This is a special case, means the +3V3 output is always on at any time
++
++
++1.
++11. +5V Output
++
++RS485-BL has a Controllable +5V output, user can use this output to power external sensor.
++
++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.
++
++
++The 5V output time can be controlled by AT Command.
++
++**AT+5VT=1000**
++
++Means set 5V valid time to have 1000ms. So, the real 5V output will actually have 1000ms + sampling time for other sensors.
++
++
++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.
++
++
++
++
++1.
++11. LEDs
++
++|**LEDs**|**Feature**
++|**LED1**|Blink when device transmit a packet.
++
++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
++
+++5V: Only open before every sampling. The time is by default, it is AT+5VT=0.  Max open time. 5000 ms.
++
++1. Case Study
++
++User can check this URL for some case studies.
++
++[[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]]
++
++
++
++
++1. Use AT Command
++11. 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.
++
++[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image027.png]]
++
++
++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]]
++
++
++
++More detail AT Command manual can be found at [[AT Command Manual>>path:#AT_COMMAND]]
++
++
++
++1.
++11. Common AT Command Sequence
++111. Multi-channel ABP mode (Use with SX1301/LG308)
++
++If device has not joined network yet:
++
++AT+FDR
++
++AT+NJM=0
++
++ATZ
++
++
++If device already joined network:
++
++AT+NJM=0
++
++ATZ
++
++1.
++11.
++111. Single-channel ABP mode (Use with LG01/LG02)
++
++AT+FDR   Reset Parameters to Factory Default, Keys Reserve
++
++AT+NJM=0 Set to ABP mode
++
++AT+ADR=0 Set the Adaptive Data Rate Off
++
++AT+DR=5  Set Data Rate
++
++AT+TDC=60000  Set transmit interval to 60 seconds
++
++AT+CHS=868400000 Set transmit frequency to 868.4Mhz
++
++AT+RX2FQ=868400000 Set RX2Frequency to 868.4Mhz (according to the result from server)
++
++AT+RX2DR=5  Set RX2DR to match the downlink DR from server. see below
++
++AT+DADDR=26 01 1A F1 Set Device Address to 26 01 1A F1, this ID can be found in the LoRa Server portal.
++
++ATZ          Reset MCU
++
++**Note:**
++
++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]]
++
++
++1. FAQ
++11. How to upgrade the image?
++
++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.
++
++Below shows the hardware connection for how to upload an image to RS485-BL:
++
++[[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]].
++
++**Step2**: Download the [[LT Image files>>url:http://www.dragino.com/downloads/index.php?dir=LT_LoRa_IO_Controller/LT33222-L/image/]].
++
++**Step3: **Open flashloader; choose the correct COM port to update.
++
++
++|(((
++HOLD PRO then press the RST button, SYS will be ON, then click next
++)))
++
++|(((
++Board detected
++)))
++
++|(((
++
++)))
++
++[[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]]
++
++
++
++[[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]]
++
++
++[[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.
++11. 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.
++
++
++
++1.
++11. 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]].
++
++
++
++
++1. Trouble Shooting
++11. Downlink doesn’t work, how to solve it?
++
++Please see this link for debug:
++
++[[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]]
++
++
++
++1.
++11. Why I can’t join TTN V3 in US915 /AU915 bands?
++
++It might about the channels mapping. Please see for detail.
++
++[[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]]
++
++
++
++1. Order Info
++
++**Part Number: RS485-BL-XXX**
++
++**XXX:**
++
++* **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
++
++1. Packing Info
++
++**Package Includes**:
++
++* RS485-BL x 1
++* Stick Antenna for LoRa RF part x 1
++* Program cable x 1
++
++**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
++
++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]]

1654159460680-153.png

Author

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

Size

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

Content

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

Summary

Details

Applications

Navigation