Skip to Content
Last modified by Mengting Qiu on 2025/07/14 09:59
From version 15.6
edited by Xiaoling
on 2022/05/19 17:59
Change comment: There is no comment for this version
To version 57.36
edited by Xiaoling
on 2022/06/06 09:32
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -RS485-BL – Waterproof RS485 to LoRaWAN Converter
1 +RS485-LN – RS485 to LoRaWAN Converter
Content
... ... @@ -1,76 +1,65 @@
1 1  (% style="text-align:center" %)
2 -[[image:1652947681187-144.png||height="385" width="385"]]
2 +[[image:1653266934636-343.png||height="385" width="385"]]
3 3  
4 4  
5 5  
6 +**RS485-LN – RS485 to LoRaWAN Converter User Manual**
6 6  
7 -**RS485-BL – Waterproof RS485 to LoRaWAN Converter User Manual**
8 8  
9 9  
10 +
10 10  **Table of Contents:**
11 11  
13 +{{toc/}}
12 12  
13 13  
14 14  
15 15  
18 +
19 +
20 +
16 16  = 1.Introduction =
17 17  
18 -== 1.1 What is RS485-BL RS485 to LoRaWAN Converter ==
23 +== 1.1 What is RS485-LN RS485 to LoRaWAN Converter ==
19 19  
20 20  (((
21 -
22 -)))
23 -
24 24  (((
25 -The Dragino RS485-BL is a **RS485 / UART to LoRaWAN Converter** for Internet of Things solutions. User can connect RS485 or UART sensor to RS485-BL converter, and configure RS485-BL to periodically read sensor data and upload via LoRaWAN network to IoT server.
27 +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.
26 26  )))
27 27  
28 28  (((
29 -RS485-BL can interface to RS485 sensor, 3.3v/5v UART sensor or interrupt sensor. RS485-BL provides **a 3.3v output** and** a 5v output** to power external sensors. Both output voltages are controllable to minimize the total system power consumption.
31 +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.
30 30  )))
31 31  
32 32  (((
33 -RS485-BL is IP67 **waterproof** and powered by **8500mAh Li-SOCI2 battery**, it is designed for long term use for several years.
35 +(% 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.
34 34  )))
35 35  
36 36  (((
37 -RS485-BL runs standard **LoRaWAN 1.0.3 in Class A**. It can reach long transfer range and easy to integrate with LoRaWAN compatible gateway and IoT server.
38 -)))
39 +(% 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.
39 39  
40 -(((
41 -For data uplink, RS485-BL sends user-defined commands to RS485 devices and gets the return from the RS485 devices. RS485-BL will process these returns data according to user-define rules to get the final payload and upload to LoRaWAN server.
41 +(% 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]]
42 42  )))
43 -
44 -(((
45 -For data downlink, RS485-BL runs in LoRaWAN Class A. When there is downlink commands from LoRaWAN server, RS485-BL will forward the commands from LoRaWAN server to RS485 devices.
46 46  )))
47 47  
48 -(((
49 -Each RS485-BL pre-load with a set of unique keys for LoRaWAN registration, register these keys to LoRaWAN server and it will auto connect after power on.
50 -)))
45 +[[image:1653267211009-519.png||height="419" width="724"]]
51 51  
52 -[[image:1652953304999-717.png||height="424" width="733"]]
53 53  
54 54  == 1.2 Specifications ==
55 55  
50 +
56 56  **Hardware System:**
57 57  
58 58  * STM32L072CZT6 MCU
59 59  * SX1276/78 Wireless Chip 
60 60  * Power Consumption (exclude RS485 device):
61 -** Idle: 6uA@3.3v
56 +** Idle: 32mA@12v
57 +** 20dB Transmit: 65mA@12v
62 62  
63 -*
64 -** 20dB Transmit: 130mA@3.3v
65 -
66 66  **Interface for Model:**
67 67  
68 -* 1 x RS485 Interface
69 -* 1 x TTL Serial , 3.3v or 5v.
70 -* 1 x I2C Interface, 3.3v or 5v.
71 -* 1 x one wire interface
72 -* 1 x Interrupt Interface
73 -* 1 x Controllable 5V output, max
61 +* RS485
62 +* Power Input 7~~ 24V DC. 
74 74  
75 75  **LoRa Spec:**
76 76  
... ... @@ -79,27 +79,30 @@
79 79  ** Band 2 (LF): 410 ~~ 528 Mhz
80 80  * 168 dB maximum link budget.
81 81  * +20 dBm - 100 mW constant RF output vs.
71 +* +14 dBm high efficiency PA.
82 82  * Programmable bit rate up to 300 kbps.
83 83  * High sensitivity: down to -148 dBm.
84 84  * Bullet-proof front end: IIP3 = -12.5 dBm.
85 85  * Excellent blocking immunity.
76 +* Low RX current of 10.3 mA, 200 nA register retention.
86 86  * Fully integrated synthesizer with a resolution of 61 Hz.
87 -* LoRa modulation.
78 +* FSK, GFSK, MSK, GMSK, LoRaTM and OOK modulation.
88 88  * Built-in bit synchronizer for clock recovery.
89 89  * Preamble detection.
90 90  * 127 dB Dynamic Range RSSI.
91 -* Automatic RF Sense and CAD with ultra-fast AFC. ​​​
82 +* Automatic RF Sense and CAD with ultra-fast AFC.
83 +* Packet engine up to 256 bytes with CRC
92 92  
93 93  == 1.3 Features ==
94 94  
95 -* LoRaWAN Class A & Class C protocol (default Class A)
87 +* LoRaWAN Class A & Class C protocol (default Class C)
96 96  * Frequency Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915/IN865/RU864
97 97  * AT Commands to change parameters
98 -* Remote configure parameters via LoRaWAN Downlink
90 +* Remote configure parameters via LoRa Downlink
99 99  * Firmware upgradable via program port
100 100  * Support multiply RS485 devices by flexible rules
101 101  * Support Modbus protocol
102 -* Support Interrupt uplink
94 +* Support Interrupt uplink (Since hardware version v1.2)
103 103  
104 104  == 1.4 Applications ==
105 105  
... ... @@ -112,53 +112,46 @@
112 112  
113 113  == 1.5 Firmware Change log ==
114 114  
115 -[[RS485-BL Image files – Download link and Change log>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/RS485-BL/Firmware/||style="background-color: rgb(255, 255, 255);"]]
107 +[[RS485-LN Image files – Download link and Change log>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/]]
116 116  
109 +
117 117  == 1.6 Hardware Change log ==
118 118  
119 119  (((
120 -v1.4
121 -)))
122 -
123 123  (((
124 -~1. Change Power IC to TPS22916
125 -)))
114 +v1.2: Add External Interrupt Pin.
126 126  
116 +v1.0: Release
127 127  
128 -(((
129 -v1.3
118 +
130 130  )))
131 -
132 -(((
133 -~1. Change JP3 from KF350-8P to KF350-11P, Add one extra interface for I2C and one extra interface for one-wire
134 134  )))
135 135  
122 += 2. Power ON Device =
136 136  
137 137  (((
138 -v1.2
139 -)))
125 +The RS485-LN can be powered by 7 ~~ 24V DC power source. Connection as below
140 140  
127 +* Power Source VIN to RS485-LN VIN+
128 +* Power Source GND to RS485-LN VIN-
129 +
141 141  (((
142 -Release version ​​​​​
131 +Once there is power, the RS485-LN will be on.
143 143  )))
144 144  
145 -= 2. Pin mapping and Power ON Device =
134 +[[image:1653268091319-405.png]]
146 146  
147 -(((
148 -The RS485-BL is powered on by 8500mAh battery. To save battery life, RS485-BL is shipped with power off. User can put the jumper to power on RS485-BL.
136 +
149 149  )))
150 150  
151 -[[image:1652953055962-143.png||height="387" width="728"]]
152 -
153 -
154 -The Left TXD and RXD are TTL interface for external sensor. TTL level is controlled by 3.3/5v Jumper.
155 -
156 156  = 3. Operation Mode =
157 157  
158 158  == 3.1 How it works? ==
159 159  
160 160  (((
161 -The RS485-BL is configured as LoRaWAN OTAA Class A 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-BL. It will auto join the network via OTAA.
144 +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.
145 +
146 +
162 162  )))
163 163  
164 164  == 3.2 Example to join LoRaWAN network ==
... ... @@ -165,27 +165,37 @@
165 165  
166 166  Here shows an example for how to join the TTN V3 Network. Below is the network structure, we use [[LG308>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/140-lg308.html]] as LoRaWAN gateway here. 
167 167  
168 -[[image:1652953414711-647.png||height="337" width="723"]]
153 +[[image:1653268155545-638.png||height="334" width="724"]]
169 169  
155 +
170 170  (((
171 -The RS485-BL in this example connected to two RS485 devices for demonstration, user can connect to other RS485 devices via the same method.
157 +(((
158 +The RS485-LN in this example connected to two RS485 devices for demonstration, user can connect to other RS485 devices via the same method. The connection is as below:
172 172  )))
173 173  
174 174  (((
175 -The LG308 is already set to connect to [[TTN V3 network >>url:https://www.thethingsnetwork.org/]]. So what we need to now is only configure the TTN V3:
162 +485A+ and 485B- of the sensor are connected to RS485A and RA485B of RS485-LN respectively.
176 176  )))
177 177  
165 +[[image:1653268227651-549.png||height="592" width="720"]]
166 +
178 178  (((
179 -**Step 1**: Create a device in TTN V3 with the OTAA keys from RS485-BL.
168 +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:
180 180  )))
181 181  
182 182  (((
183 -Each RS485-BL is shipped with a sticker with unique device EUI:
172 +**Step 1**: Create a device in TTN V3 with the OTAA keys from RS485-LN.
184 184  )))
185 185  
175 +(((
176 +Each RS485-LN is shipped with a sticker with unique device EUI:
177 +)))
178 +)))
179 +
186 186  [[image:1652953462722-299.png]]
187 187  
188 188  (((
183 +(((
189 189  User can enter this key in their LoRaWAN Server portal. Below is TTN V3 screen shot:
190 190  )))
191 191  
... ... @@ -192,13 +192,11 @@
192 192  (((
193 193  Add APP EUI in the application.
194 194  )))
190 +)))
195 195  
196 -
197 -
198 -
199 199  [[image:image-20220519174512-1.png]]
200 200  
201 -[[image:image-20220519174512-2.png||height="328" width="731"]]
194 +[[image:image-20220519174512-2.png||height="323" width="720"]]
202 202  
203 203  [[image:image-20220519174512-3.png||height="556" width="724"]]
204 204  
... ... @@ -214,44 +214,43 @@
214 214  
215 215  
216 216  (((
217 -**Step 2**: Power on RS485-BL 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.
210 +**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.
218 218  )))
219 219  
220 220  [[image:1652953568895-172.png||height="232" width="724"]]
221 221  
215 +
222 222  == 3.3 Configure Commands to read data ==
223 223  
224 224  (((
225 -There are plenty of RS485 and TTL level devices in the market and each device has different command to read the valid data. To support these devices in flexible, RS485-BL supports flexible command set. User can use [[AT Commands or LoRaWAN Downlink>>path:#AT_COMMAND]] Command to configure how RS485-BL should read the sensor and how to handle the return from RS485 or TTL sensors.
219 +(((
220 +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.
226 226  )))
227 227  
228 -=== 3.3.1 onfigure UART settings for RS485 or TTL communication ===
223 +(((
224 +(% 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
229 229  
230 -RS485-BL can connect to either RS485 sensors or TTL sensor. User need to specify what type of sensor need to connect.
226 +
227 +)))
228 +)))
231 231  
232 -**~1. RS485-MODBUS mode:**
230 +=== 3.3.1 onfigure UART settings for RS485 or TTL communication ===
233 233  
234 -AT+MOD=1 ~/~/ Support RS485-MODBUS type sensors. User can connect multiply RS485 , Modbus sensors to the A / B pins.
232 +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:
235 235  
236 -**2. TTL mode:**
237 -
238 -AT+MOD=2 ~/~/ Support TTL Level sensors, User can connect one TTL Sensor to the TXD/RXD/GND pins.
239 -
240 -RS485-BL default UART settings is **9600, no parity, stop bit 1**. If the sensor has a different settings, user can change the RS485-BL setting to match.
241 -
242 -(% border="1" style="background-color:#ffffcc; color:green; width:795px" %)
243 -|(((
234 +(% border="1" style="background-color:#ffffcc; color:green; width:782px" %)
235 +|(% style="width:128px" %)(((
244 244  **AT Commands**
245 -)))|(% style="width:285px" %)(((
237 +)))|(% style="width:305px" %)(((
246 246  **Description**
247 -)))|(% style="width:347px" %)(((
239 +)))|(% style="width:346px" %)(((
248 248  **Example**
249 249  )))
250 -|(((
242 +|(% style="width:128px" %)(((
251 251  AT+BAUDR
252 -)))|(% style="width:285px" %)(((
244 +)))|(% style="width:305px" %)(((
253 253  Set the baud rate (for RS485 connection). Default Value is: 9600.
254 -)))|(% style="width:347px" %)(((
246 +)))|(% style="width:346px" %)(((
255 255  (((
256 256  AT+BAUDR=9600
257 257  )))
... ... @@ -260,18 +260,12 @@
260 260  Options: (1200,2400,4800,14400,19200,115200)
261 261  )))
262 262  )))
263 -|(((
255 +|(% style="width:128px" %)(((
264 264  AT+PARITY
265 -)))|(% style="width:285px" %)(((
266 -(((
257 +)))|(% style="width:305px" %)(((
267 267  Set UART parity (for RS485 connection)
268 -)))
269 -
259 +)))|(% style="width:346px" %)(((
270 270  (((
271 -Default Value is: no parity.
272 -)))
273 -)))|(% style="width:347px" %)(((
274 -(((
275 275  AT+PARITY=0
276 276  )))
277 277  
... ... @@ -279,17 +279,17 @@
279 279  Option: 0: no parity, 1: odd parity, 2: even parity
280 280  )))
281 281  )))
282 -|(((
268 +|(% style="width:128px" %)(((
283 283  AT+STOPBIT
284 -)))|(% style="width:285px" %)(((
270 +)))|(% style="width:305px" %)(((
285 285  (((
286 286  Set serial stopbit (for RS485 connection)
287 287  )))
288 288  
289 289  (((
290 -Default Value is: 1bit.
276 +
291 291  )))
292 -)))|(% style="width:347px" %)(((
278 +)))|(% style="width:346px" %)(((
293 293  (((
294 294  AT+STOPBIT=0 for 1bit
295 295  )))
... ... @@ -306,12 +306,10 @@
306 306  === 3.3.2 Configure sensors ===
307 307  
308 308  (((
309 -Some sensors might need to configure before normal operation. User can configure such sensor via PC or through RS485-BL AT Commands (% style="color:#4f81bd" %)**AT+CFGDEV**.
310 -)))
311 -
312 312  (((
313 -When user issue an (% style="color:#4f81bd" %)**AT+CFGDEV**(%%) command, Each (% style="color:#4f81bd" %)**AT+CFGDEV**(%%) equals to send a command to the RS485 or TTL sensors. This command will only run when user input it and won’t run during each sampling.
296 +Some sensors might need to configure before normal operation. User can configure such sensor via PC and RS485 adapter or through RS485-LN AT Commands (% style="color:#4f81bd" %)**AT+CFGDEV**(%%). Each (% style="color:#4f81bd" %)**AT+CFGDEV **(%%)equals to send a RS485 command to sensors. This command will only run when user input it and won’t run during each sampling.
314 314  )))
298 +)))
315 315  
316 316  (% border="1" style="background-color:#ffffcc; color:green; width:806px" %)
317 317  |**AT Commands**|(% style="width:418px" %)**Description**|(% style="width:256px" %)**Example**
... ... @@ -323,81 +323,37 @@
323 323  mm: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
324 324  )))|(% style="width:256px" %)AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
325 325  
326 -Detail of AT+CFGDEV command see [[AT+CFGDEV detail>>path:#AT_CFGDEV]].
327 -
328 328  === 3.3.3 Configure read commands for each sampling ===
329 329  
330 330  (((
331 -RS485-BL is a battery powered device; it will sleep most of time. And wake up on each period and read RS485 / TTL sensor data and uplink.
332 -)))
313 +During each sampling, we need confirm what commands we need to send to the RS485 sensors to read data. After the RS485 sensors send back the value, it normally include some bytes and we only need a few from them for a shorten payload.
333 333  
334 -(((
335 -During each sampling, we need to confirm what commands we need to send to the sensors to read data. After the RS485/TTL sensors send back the value, it normally includes some bytes and we only need a few from them for a shorten payload.
336 -)))
337 -
338 -(((
339 339  To save the LoRaWAN network bandwidth, we might need to read data from different sensors and combine their valid value into a short payload.
340 -)))
341 341  
342 -(((
343 343  This section describes how to achieve above goals.
344 -)))
345 345  
346 -(((
347 -During each sampling, the RS485-BL can support 15 commands to read sensors. And combine the return to one or several uplink payloads.
348 -)))
319 +During each sampling, the RS485-LN can support 15 commands to read sensors. And combine the return to one or several uplink payloads.
349 349  
350 -(((
351 -**Command from RS485-BL to Sensor:**
352 -)))
353 353  
354 -(((
355 -RS485-BL can send out pre-set max 15 strings via **AT+COMMAD1**, **ATCOMMAND2**,…, to **AT+COMMANDF** . All commands are of same grammar.
356 -)))
322 +**Each RS485 commands include two parts:**
357 357  
358 -(((
359 -**Handle return from sensors to RS485-BL**:
360 -)))
324 +~1. What commands RS485-LN will send to the RS485 sensors. There are total 15 commands from **AT+COMMAD1**, **ATCOMMAND2**,…, to **AT+COMMANDF**. All commands are of same grammar.
361 361  
362 -(((
363 -After RS485-BL send out a string to sensor, RS485-BL will wait for the return from RS485 or TTL sensor. And user can specify how to handle the return, by **AT+DATACUT or AT+SEARCH commands**
364 -)))
326 +2. 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.
365 365  
366 -* (((
367 -**AT+DATACUT**
368 -)))
328 +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
369 369  
370 -(((
371 -When the return value from sensor have fix length and we know which position the valid value we should get, we can use AT+DATACUT command.
372 -)))
373 373  
374 -* (((
375 -**AT+SEARCH**
376 -)))
377 -
378 -(((
379 -When the return value from sensor is dynamic length and we are not sure which bytes the valid data is, instead, we know what value the valid value following. We can use AT+SEARCH to search the valid value in the return string.
380 -)))
381 -
382 -(((
383 -**Define wait timeout:**
384 -)))
385 -
386 -(((
387 -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
388 -)))
389 -
390 -(((
391 391  After we got the valid value from each RS485 commands, we need to combine them together with the command **AT+DATAUP**.
392 -)))
393 393  
394 -**Examples:**
395 395  
396 396  Below are examples for the how above AT Commands works.
397 397  
398 -**AT+COMMANDx : **This command will be sent to RS485/TTL devices during each sampling, Max command length is 14 bytes. The grammar is:
399 399  
400 -|(((
337 +**AT+COMMANDx : **This command will be sent to RS485 devices during each sampling, Max command length is 14 bytes. The grammar is:
338 +
339 +(% border="1" style="background-color:#4bacc6; color:white; width:499px" %)
340 +|(% style="width:496px" %)(((
401 401  **AT+COMMANDx=xx xx xx xx xx xx xx xx xx xx xx xx,m**
402 402  
403 403  **xx xx xx xx xx xx xx xx xx xx xx xx: The RS485 command to be sent**
... ... @@ -407,42 +407,13 @@
407 407  
408 408  For example, if we have a RS485 sensor. The command to get sensor value is: 01 03 0B B8 00 02 46 0A. Where 01 03 0B B8 00 02 is the Modbus command to read the register 0B B8 where stored the sensor value. The 46 0A is the CRC-16/MODBUS which calculate manually.
409 409  
410 -In the RS485-BL, we should use this command AT+COMMAND1=01 03 0B B8 00 02,1 for the same.
350 +In the RS485-LN, we should use this command AT+COMMAND1=01 03 0B B8 00 02,1 for the same.
411 411  
412 -**AT+SEARCHx**: This command defines how to handle the return from AT+COMMANDx.
413 413  
414 -|(((
415 -**AT+SEARCHx=aa,xx xx xx xx xx**
416 -
417 -* **aa: 1: prefix match mode; 2: prefix and suffix match mode**
418 -* **xx xx xx xx xx: match string. Max 5 bytes for prefix and 5 bytes for suffix**
419 -
420 -
421 -)))
422 -
423 -Examples:
424 -
425 -1. For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
426 -
427 -If we set AT+SEARCH1=1,1E 56 34.      (max 5 bytes for prefix)
428 -
429 -The valid data will be all bytes after 1E 56 34 , so it is 2e 30 58 5f 36 41 30 31 00 49
430 -
431 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image013.png]]
432 -
433 -
434 -1. For a return string from AT+COMMAND1:  16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
435 -
436 -If we set AT+SEARCH1=2, 1E 56 34+31 00 49
437 -
438 -Device will search the bytes between 1E 56 34 and 31 00 49. So it is 2e 30 58 5f 36 41 30
439 -
440 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image014.png]]
441 -
442 -
443 443  **AT+DATACUTx : **This command defines how to handle the return from AT+COMMANDx, max return length is 45 bytes.
444 444  
445 -|(((
355 +(% border="1" style="background-color:#4bacc6; color:white; width:725px" %)
356 +|(% style="width:722px" %)(((
446 446  **AT+DATACUTx=a,b,c**
447 447  
448 448  * **a: length for the return of AT+COMMAND**
... ... @@ -450,242 +450,184 @@
450 450  * **c: define the position for valid value.  **
451 451  )))
452 452  
453 -Examples:
364 +**Examples:**
454 454  
455 455  * Grab bytes:
456 456  
457 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image015.png]]
368 +[[image:image-20220602153621-1.png]]
458 458  
370 +
459 459  * Grab a section.
460 460  
461 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image016.png]]
373 +[[image:image-20220602153621-2.png]]
462 462  
375 +
463 463  * Grab different sections.
464 464  
465 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image017.png]]
378 +[[image:image-20220602153621-3.png]]
466 466  
380 +
381 +)))
467 467  
468 -Note:
383 +=== 3.3.4 Compose the uplink payload ===
469 469  
470 -AT+SEARCHx and AT+DATACUTx can be used together, if both commands are set, RS485-BL will first process AT+SEARCHx on the return string and get a temporary string, and then process AT+DATACUTx on this temporary string to get the final payload. In this case, AT+DATACUTx need to set to format AT+DATACUTx=0,xx,xx where the return bytes set to 0.
471 -
472 -Example:
473 -
474 -AT+COMMAND1=11 01 1E D0,0
475 -
476 -AT+SEARCH1=1,1E 56 34
477 -
478 -AT+DATACUT1=0,2,1~~5
479 -
480 -Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
481 -
482 -String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49
483 -
484 -Valid payload after DataCUT command: 2e 30 58 5f 36
485 -
486 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image018.png]]
487 -
488 -
489 -
490 -
491 -1.
492 -11.
493 -111. Compose the uplink payload
494 -
385 +(((
495 495  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.**
496 496  
388 +
389 +)))
497 497  
498 -**Examples: AT+DATAUP=0**
391 +(((
392 +(% style="color:#037691" %)**Examples: AT+DATAUP=0**
499 499  
500 -Compose the uplink payload with value returns in sequence and send with **A SIGNLE UPLINK**.
394 +
395 +)))
501 501  
397 +(((
398 +Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**A SIGNLE UPLINK**.
399 +)))
400 +
401 +(((
502 502  Final Payload is
403 +)))
503 503  
504 -Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx
405 +(((
406 +(% style="color:#4f81bd" %)**Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx**
407 +)))
505 505  
409 +(((
506 506  Where PAYVER is defined by AT+PAYVER, below is an example screen shot.
411 +)))
507 507  
508 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image019.png]]
413 +[[image:1653269759169-150.png||height="513" width="716"]]
509 509  
510 510  
416 +(% style="color:#037691" %)**Examples: AT+DATAUP=1**
511 511  
512 -**Examples: AT+DATAUP=1**
513 513  
514 -Compose the uplink payload with value returns in sequence and send with **Multiply UPLINKs**.
419 +Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**Multiply UPLINKs**.
515 515  
516 516  Final Payload is
517 517  
518 -Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA
423 +(% style="color:#4f81bd" %)**Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA**
519 519  
520 -1. Battery Info (2 bytes): Battery voltage
521 -1. PAYVER (1 byte): Defined by AT+PAYVER
522 -1. PAYLOAD COUNT (1 byte): Total how many uplinks of this sampling.
523 -1. PAYLOAD# (1 byte): Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT)
524 -1. DATA: Valid value: max 6 bytes(US915 version here, [[Notice*!>>path:#max_byte]]) for each uplink so each uplink <= 11 bytes. For the last uplink, DATA will might less than 6 bytes
525 525  
526 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image020.png]]
426 +1. PAYVER: Defined by AT+PAYVER
427 +1. PAYLOAD COUNT: Total how many uplinks of this sampling.
428 +1. PAYLOAD#: Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT)
429 +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
527 527  
431 +[[image:image-20220602155039-4.png]]
528 528  
529 -So totally there will be 3 uplinks for this sampling, each uplink includes 6 bytes DATA
530 530  
531 -DATA1=RETURN1 Valid Value = 20 20 0a 33 90 41
434 +So totally there will be 3 uplinks for this sampling, each uplink include 8 bytes DATA
532 532  
533 -DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10= 02 aa 05 81 0a 20
436 +DATA1=RETURN1 Valid Value + the first two of Valid value of RETURN10= **20 20 0a 33 90 41 02 aa**
534 534  
535 -DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 = 20 20 20 2d 30
438 +DATA2=3^^rd^^ ~~ 10^^th^^ byte of Valid value of RETURN10= **05 81 0a 20 20 20 20 2d**
536 536  
440 +DATA3=the rest of Valid value of RETURN10= **30**
537 537  
538 538  
539 -Below are the uplink payloads:
443 +(% 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:
540 540  
541 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image021.png]]
445 + ~* For AU915/AS923 bands, if UplinkDwell time=0, max 51 bytes for each uplink.
542 542  
447 + * For AU915/AS923 bands, if UplinkDwell time=0, max 11 bytes for each uplink.
543 543  
544 -Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:
449 + * For US915 band, max 11 bytes for each uplink.
545 545  
546 - ~* For AU915/AS923 bands, if UplinkDwell time=0, max 51 bytes for each uplink ( so 51 -5 = 46 max valid date)
451 + ~* For all other bands: max 51 bytes for each uplink.
547 547  
548 - * For AU915/AS923 bands, if UplinkDwell time=1, max 11 bytes for each uplink ( so 11 -5 = 6 max valid date).
549 549  
550 - * For US915 band, max 11 bytes for each uplink ( so 11 -5 = 6 max valid date).
454 +Below are the uplink payloads:
551 551  
552 - ~* For all other bands: max 51 bytes for each uplink  ( so 51 -5 = 46 max valid date).
456 +[[image:1654157178836-407.png]]
553 553  
554 554  
459 +=== 3.3.5 Uplink on demand ===
555 555  
556 -1.
557 -11.
558 -111. Uplink on demand
461 +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.
559 559  
560 -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.
561 -
562 562  Downlink control command:
563 563  
564 -[[0x08 command>>path:#downlink_08]]: Poll an uplink with current command set in RS485-BL.
465 +**0x08 command**: Poll an uplink with current command set in RS485-LN.
565 565  
566 -[[0xA8 command>>path:#downlink_A8]]: Send a command to RS485-BL and uplink the output from sensors.
467 +**0xA8 command**: Send a command to RS485-LN and uplink the output from sensors.
567 567  
568 568  
569 569  
570 -1.
571 -11.
572 -111. Uplink on Interrupt
471 +=== 3.3.6 Uplink on Interrupt ===
573 573  
574 -Put the interrupt sensor between 3.3v_out and GPIO ext.[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image022.png]]
473 +RS485-LN support external Interrupt uplink since hardware v1.2 release.
575 575  
576 -AT+INTMOD=0  Disable Interrupt
475 +[[image:1654157342174-798.png]]
577 577  
578 -AT+INTMOD=1  Interrupt trigger by rising or falling edge.
477 +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.
579 579  
580 -AT+INTMOD=2  Interrupt trigger by falling edge. ( Default Value)
581 581  
582 -AT+INTMOD=3  Interrupt trigger by rising edge.
480 +== 3.4 Uplink Payload ==
583 583  
584 -
585 -1.
586 -11. Uplink Payload
587 -
588 -|**Size(bytes)**|**2**|**1**|**Length depends on the return from the commands**
589 -|Value|(((
482 +(% border="1" style="background-color:#4bacc6; color:white; width:734px" %)
483 +|**Size(bytes)**|(% style="width:120px" %)**2**|(% style="width:116px" %)**1**|(% style="width:386px" %)**Length depends on the return from the commands**
484 +|Value|(% style="width:120px" %)(((
590 590  Battery(mV)
591 591  
592 592  &
593 593  
594 594  Interrupt _Flag
595 -)))|(((
490 +)))|(% style="width:116px" %)(((
596 596  PAYLOAD_VER
597 597  
598 598  
599 -)))|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.
494 +)))|(% 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.
600 600  
601 601  Below is the decoder for the first 3 bytes. The rest bytes are dynamic depends on different RS485 sensors.
602 602  
603 603  
604 -function Decoder(bytes, port) {
499 +== 3.5 Configure RS485-BL via AT or Downlink ==
605 605  
606 -~/~/Payload Formats of RS485-BL Deceive
501 +User can configure RS485-LN via AT Commands or LoRaWAN Downlink Commands
607 607  
608 -return {
609 -
610 - ~/~/Battery,units:V
611 -
612 - BatV:((bytes[0]<<8 | bytes[1])&0x7fff)/1000,
613 -
614 - ~/~/GPIO_EXTI 
615 -
616 - EXTI_Trigger:(bytes[0] & 0x80)? "TRUE":"FALSE",
617 -
618 - ~/~/payload of version
619 -
620 - Pay_ver:bytes[2],
621 -
622 - };
623 -
624 - }
625 -
626 -
627 -
628 -
629 -
630 -
631 -
632 -TTN V3 uplink screen shot.
633 -
634 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png]]
635 -
636 -1.
637 -11. Configure RS485-BL via AT or Downlink
638 -
639 -User can configure RS485-BL via [[AT Commands >>path:#_​Using_the_AT]]or LoRaWAN Downlink Commands
640 -
641 641  There are two kinds of Commands:
642 642  
643 -* **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
505 +* (% 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]]
644 644  
645 -* **Sensor Related Commands**: These commands are special designed for RS485-BL.  User can see these commands below:
507 +* (% style="color:#4f81bd" %)**Sensor Related Commands**(%%): These commands are special designed for RS485-LN.  User can see these commands below:
646 646  
647 -1.
648 -11.
649 -111. Common Commands:
509 +=== 3.5.1 Common Commands ===
650 650  
651 -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]]
511 +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]]
652 652  
653 653  
654 -1.
655 -11.
656 -111. Sensor related commands:
514 +=== 3.5.2 Sensor related commands ===
657 657  
658 -==== Choose Device Type (RS485 or TTL) ====
516 +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.
659 659  
660 -RS485-BL can connect to either RS485 sensors or TTL sensor. User need to specify what type of sensor need to connect.
518 +[[image:image-20220602163333-5.png||height="263" width="1160"]]
661 661  
662 -* AT Command
520 +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)
663 663  
664 -**AT+MOD=1** ~/~/ Set to support RS485-MODBUS type sensors. User can connect multiply RS485 , Modbus sensors to the A / B pins.
665 665  
666 -**AT+MOD=2** ~/~/ Set to support TTL Level sensors, User can connect one TTL Sensor to the TXD/RXD/GND pins.
523 +=== 3.5.3 Sensor related commands ===
667 667  
668 668  
669 -* Downlink Payload
670 670  
671 -**0A aa**     à same as AT+MOD=aa
527 +==== **RS485 Debug Command** ====
672 672  
529 +This command is used to configure the RS485 devices; they won’t be used during sampling.
673 673  
531 +* **AT Command**
674 674  
675 -==== [[RS485 Debug Command>>path:#downlink_A8]] (AT+CFGDEV) ====
533 +(% class="box infomessage" %)
534 +(((
535 +**AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m**
536 +)))
676 676  
677 -This command is used to configure the RS485 or TTL sensors; they won’t be used during sampling.
538 +m: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
678 678  
679 -* AT Command
540 +* **Downlink Payload**
680 680  
681 -AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
682 -
683 -m: 0: no CRC; 1: add CRC-16/MODBUS in the end of this command.
684 -
685 -
686 -
687 -* Downlink Payload
688 -
689 689  Format: A8 MM NN XX XX XX XX YY
690 690  
691 691  Where:
... ... @@ -693,9 +693,12 @@
693 693  * MM: 1: add CRC-16/MODBUS ; 0: no CRC
694 694  * NN: The length of RS485 command
695 695  * XX XX XX XX: RS485 command total NN bytes
696 -* 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
549 +* YY: How many bytes will be uplink from the return of this RS485 command,
550 +** if YY=0, RS485-LN will execute the downlink command without uplink;
551 +** if YY>0, RS485-LN will uplink total YY bytes from the output of this RS485 command; Fport=200
552 +** if YY=FF, RS485-LN will uplink RS485 output with the downlink command content; Fport=200.
697 697  
698 -**Example 1:**
554 +**Example 1** ~-~-> Configure without ask for uplink (YY=0)
699 699  
700 700  To connect a Modbus Alarm with below commands.
701 701  
... ... @@ -705,184 +705,190 @@
705 705  
706 706  So if user want to use downlink command to control to RS485 Alarm, he can use:
707 707  
708 -**A8 01 06 0A 05 00 04 00 01 00**: to activate the RS485 Alarm
564 +(% style="color:#4f81bd" %)**A8 01 06 0A 05 00 04 00 01 00**(%%): to activate the RS485 Alarm
709 709  
710 -**A8 01 06 0A 05 00 04 00 00 00**: to deactivate the RS485 Alarm
566 +(% style="color:#4f81bd" %)**A8 01 06 0A 05 00 04 00 00 00**(%%): to deactivate the RS485 Alarm
711 711  
712 712  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.
713 713  
714 714  
715 -**Example 2:**
571 +**Example 2** ~-~-> Configure with requesting uplink and original downlink command (**YY=FF**)
716 716  
717 -Check TTL Sensor return:
573 +User in IoT server send a downlink command: (% style="color:#4f81bd" %)**A8 01 06 0A 08 00 04 00 01 YY**
718 718  
719 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image024.png]]
720 720  
576 +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:
721 721  
578 + **A8** (% style="color:#4f81bd" %)**0A 08 00 04 00  **(% style="color:red" %)**01 06** ** **(% style="color:green" %)**0A 08 00 04 00 00**
722 722  
580 + [[image:1654159460680-153.png]]
723 723  
724 -==== Set Payload version ====
725 725  
726 -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.
727 727  
728 -* AT Command:
584 +==== **Set Payload version** ====
729 729  
730 -AT+PAYVER: Set PAYVER field = 1
586 +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.
731 731  
588 +* **AT Command:**
732 732  
733 -* Downlink Payload:
590 +(% class="box infomessage" %)
591 +(((
592 +**AT+PAYVER: Set PAYVER field = 1**
593 +)))
734 734  
735 -0xAE 01   à Set PAYVER field =  0x01
595 +* **Downlink Payload:**
736 736  
737 -0xAE 0F   à Set PAYVER field =  0x0F
597 +**0xAE 01**  ~-~-> Set PAYVER field =  0x01
738 738  
599 +**0xAE 0F**   ~-~-> Set PAYVER field =  0x0F
739 739  
740 -==== Set RS485 Sampling Commands ====
741 741  
742 -AT+COMMANDx, AT+DATACUTx and AT+SEARCHx
743 743  
744 -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]].
603 +==== **Set RS485 Sampling Commands** ====
745 745  
605 +AT+COMMANDx or AT+DATACUTx
746 746  
747 -* AT Command:
607 +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"]].
748 748  
749 -AT+COMMANDx: Configure RS485 read command to sensor.
750 750  
751 -AT+DATACUTx: Configure how to handle return from RS485 devices.
610 +* **AT Command:**
752 752  
753 -AT+SEARCHx: Configure search command
612 +(% class="box infomessage" %)
613 +(((
614 +**AT+COMMANDx: Configure RS485 read command to sensor.**
615 +)))
754 754  
617 +(% class="box infomessage" %)
618 +(((
619 +**AT+DATACUTx: Configure how to handle return from RS485 devices.**
620 +)))
755 755  
756 -* Downlink Payload:
757 757  
758 -0xAF downlink command can be used to set AT+COMMANDx or AT+DATACUTx.
623 +* **Downlink Payload:**
759 759  
760 -Note: if user use AT+COMMANDx to add a new command, he also need to send AT+DATACUTx downlink.
625 +**0xAF** downlink command can be used to set AT+COMMANDx or AT+DATACUTx.
761 761  
627 +(% style="color:red" %)**Note**(%%): if user use AT+COMMANDx to add a new command, he also need to send AT+DATACUTx downlink.
628 +
762 762  Format: AF MM NN LL XX XX XX XX YY
763 763  
764 764  Where:
765 765  
766 766  * MM: the ATCOMMAND or AT+DATACUT to be set. Value from 01 ~~ 0F,
767 -* NN: 0: no CRC; 1: add CRC-16/MODBUS ; 2: set the AT+DATACUT value.
768 -* LL: The length of AT+COMMAND or AT+DATACUT command
634 +* NN:  0: no CRC; 1: add CRC-16/MODBUS ; 2: set the AT+DATACUT value.
635 +* LL:  The length of AT+COMMAND or AT+DATACUT command
769 769  * XX XX XX XX: AT+COMMAND or AT+DATACUT command
770 -* 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.
637 +* 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.
771 771  
772 -Example:
639 +**Example:**
773 773  
774 -**AF 03 01 06 0A 05 00 04 00 01 00**: Same as AT+COMMAND3=0A 05 00 04 00 01,1
641 +(% 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
775 775  
776 -**AF 03 02 06 10 01 05 06 09 0A 00**: Same as AT+DATACUT3=**16**,**1**,**5+6+9+10**
643 +(% 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**
777 777  
778 -**AF 03 02 06 0B 02 05 07 08 0A 00**: Same as AT+DATACUT3=**11**,**2**,**5~~7+8~~10**
645 +(% 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**
779 779  
780 780  
781 -0xAB downlink command can be used for set AT+SEARCHx
782 782  
783 -Example: **AB aa 01 03 xx xx xx** (03 here means there are total 3 bytes after 03) So
649 +==== **Fast command to handle MODBUS device** ====
784 784  
785 -* AB aa 01 03 xx xx xx  same as AT+SEARCHaa=1,xx xx xx
786 -* 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
787 -
788 -**AB aa 02 03 xx xx xx 02 yy yy**  same as **AT+SEARCHaa=2,xx xx xx+yy yy**
789 -
790 -
791 -==== Fast command to handle MODBUS device ====
792 -
793 793  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]].
794 794  
795 795  This command is valid since v1.3 firmware version
796 796  
655 +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.
797 797  
798 -AT+MBFUN has only two value:
799 799  
800 -* AT+MBFUN=1: Enable Modbus reading. And get response base on the MODBUS return
658 +**Example:**
801 801  
802 -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.
803 -
804 -* AT+MBFUN=0: Disable Modbus fast reading.
805 -
806 -Example:
807 -
808 -* AT+MBFUN=1 and AT+DATACUT1/AT+DATACUT2 are not configure (0,0,0).
660 +* AT+MBFUN=1 and AT+DATACUT1/AT+DATACUT2 are not configure (0,0,0). So RS485-LN.
809 809  * 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.
810 810  * 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.
811 811  
812 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image025.png]]
664 +[[image:image-20220602165351-6.png]]
813 813  
666 +[[image:image-20220602165351-7.png]]
814 814  
815 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image026.png]]
816 816  
817 817  
818 -* Downlink Commands:
670 +==== **RS485 command timeout** ====
819 819  
820 -A9 aa -à Same as AT+MBFUN=aa
672 +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.
821 821  
674 +Default value: 0, range:  0 ~~ 65 seconds
822 822  
823 -==== RS485 command timeout ====
676 +* **AT Command:**
824 824  
825 -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.
678 +(% class="box infomessage" %)
679 +(((
680 +**AT+CMDDLaa=hex(bb cc)*1000**
681 +)))
826 826  
827 -Default value: 0, range:  0 ~~ 5 seconds
683 +**Example:**
828 828  
685 +**AT+CMDDL1=1000** to send the open time to 1000ms
829 829  
830 -* AT Command:
831 831  
832 -AT+CMDDLaa=hex(bb cc)
688 +* **Downlink Payload:**
833 833  
834 -Example:
690 +**0x AA aa bb cc**
835 835  
836 -**AT+CMDDL1=1000** to send the open time to 1000ms
692 +Same as: AT+CMDDLaa=hex(bb cc)*1000
837 837  
694 + **Example:**
838 838  
839 -* Downlink Payload:
696 + 0xAA 01 00 01  ~-~-> Same as **AT+CMDDL1=1000 ms**
840 840  
841 -0x AA aa bb cc
842 842  
843 -Same as: AT+CMDDLaa=hex(bb cc)
844 844  
845 - Example:
700 +==== **Uplink payload mode** ====
846 846  
847 - 0xAA 01 03 E8  à Same as **AT+CMDDL1=1000 ms**
702 +Define to use one uplink or multiple uplinks for the sampling.
848 848  
704 +The use of this command please see: [[Compose Uplink payload>>||anchor="H3.3.4Composetheuplinkpayload"]]
849 849  
850 -==== [[Uplink>>path:#downlink_A8]] payload mode ====
706 +* **AT Command:**
851 851  
852 -Define to use one uplink or multiple uplinks for the sampling.
708 +(% class="box infomessage" %)
709 +(((
710 +**AT+DATAUP=0**
711 +)))
853 853  
854 -The use of this command please see: [[Compose Uplink payload>>path:#DataUP]]
713 +(% class="box infomessage" %)
714 +(((
715 +**AT+DATAUP=1**
716 +)))
855 855  
856 -* AT Command:
857 857  
858 -AT+DATAUP=0
719 +* **Downlink Payload:**
859 859  
860 -AT+DATAUP=1
721 +**0xAD 00**  **~-~->** Same as AT+DATAUP=0
861 861  
723 +**0xAD 01**  **~-~->** Same as AT+DATAUP=1
862 862  
863 -* Downlink Payload:
864 864  
865 -0xAD 00   à Same as AT+DATAUP=0
866 866  
867 -0xAD 01   à Same as AT+DATAUP=1
727 +==== **Manually trigger an Uplink** ====
868 868  
729 +Ask device to send an uplink immediately.
869 869  
870 -==== Manually trigger an Uplink ====
731 +* **AT Command:**
871 871  
872 -Ask device to send an uplink immediately.
733 +No AT Command for this, user can press the [[ACT button>>||anchor="H3.7Buttons"]] for 1 second for the same.
873 873  
874 -* Downlink Payload:
875 875  
876 -0x08 FF, RS485-BL will immediately send an uplink.
736 +* **Downlink Payload:**
877 877  
738 +**0x08 FF**, RS485-LN will immediately send an uplink.
878 878  
879 -==== Clear RS485 Command ====
880 880  
881 -The AT+COMMANDx and AT+DATACUTx settings are stored in special location, user can use below command to clear them.
882 882  
742 +==== **Clear RS485 Command** ====
883 883  
884 -* AT Command:
744 +The AT+COMMANDx and AT+DATACUTx settings are stored in special location, user can use below command to clear them.
885 885  
746 +* **AT Command:**
747 +
886 886  **AT+CMDEAR=mm,nn**   mm: start position of erase ,nn: stop position of erase
887 887  
888 888  Etc. AT+CMDEAR=1,10 means erase AT+COMMAND1/AT+DATACUT1 to AT+COMMAND10/AT+DATACUT10
... ... @@ -890,43 +890,50 @@
890 890  Example screen shot after clear all RS485 commands. 
891 891  
892 892  
893 -
894 894  The uplink screen shot is:
895 895  
896 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png]]
757 +[[image:1654160691922-496.png]]
897 897  
898 898  
899 -* Downlink Payload:
760 +* **Downlink Payload:**
900 900  
901 -0x09 aa bb same as AT+CMDEAR=aa,bb
762 +**0x09 aa bb** same as AT+CMDEAR=aa,bb
902 902  
903 903  
904 -==== Set Serial Communication Parameters ====
905 905  
766 +==== **Set Serial Communication Parameters** ====
767 +
906 906  Set the Rs485 serial communication parameters:
907 907  
908 -* AT Command:
770 +* **AT Command:**
909 909  
910 910  Set Baud Rate:
911 911  
912 -AT+BAUDR=9600    ~/~/ Options: (1200,2400,4800,14400,19200,115200)
774 +(% class="box infomessage" %)
775 +(((
776 +**AT+BAUDR=9600**    ~/~/ Options: (1200,2400,4800,14400,19200,115200)
777 +)))
913 913  
779 +Set UART Parity
914 914  
915 -Set UART parity
781 +(% class="box infomessage" %)
782 +(((
783 +**AT+PARITY=0**    ~/~/ Option: 0: no parity, 1: odd parity, 2: even parity
784 +)))
916 916  
917 -AT+PARITY=0    ~/~/ Option: 0: no parity, 1: odd parity, 2: even parity
918 -
919 -
920 920  Set STOPBIT
921 921  
922 -AT+STOPBIT=0    ~/~/ Option: 0 for 1bit; 1 for 1.5 bit ; 2 for 2 bits
788 +(% class="box infomessage" %)
789 +(((
790 +**AT+STOPBIT=0**    ~/~/ Option: 0 for 1bit; 1 for 1.5 bit ; 2 for 2 bits
791 +)))
923 923  
924 924  
925 -* Downlink Payload:
794 +* **Downlink Payload:**
926 926  
927 -A7 01 aa bb: Same  AT+BAUDR=hex(aa bb)*100
796 +**A7 01 aa bb**: Same  AT+BAUDR=hex(aa bb)*100
928 928  
929 -Example:
798 +**Example:**
930 930  
931 931  * A7 01 00 60   same as AT+BAUDR=9600
932 932  * A7 01 04 80  same as AT+BAUDR=115200
... ... @@ -936,189 +936,169 @@
936 936  A7 03 aa: Same as  AT+STOPBIT=aa  (aa value: 00 , 01 or 02)
937 937  
938 938  
939 -==== Control output power duration ====
808 +== 3.6 Listening mode for RS485 network ==
940 940  
941 -User can set the output power duration before each sampling.
810 +This feature support since firmware v1.4
942 942  
943 -* AT Command:
812 +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.
944 944  
945 -Example:
814 +[[image:image-20220602171200-8.png||height="567" width="1007"]]
946 946  
947 -AT+3V3T=1000 ~/~/ 3V3 output power will open 1s before each sampling.
816 +To enable the listening mode, use can run the command AT+RXMODE.
948 948  
949 -AT+5VT=1000 ~/~/ +5V output power will open 1s before each sampling.
950 950  
819 +(% border="1" style="background-color:#ffffcc; width:500px" %)
820 +|=(% style="width: 161px;" %)**Command example:**|=(% style="width: 337px;" %)**Function**
821 +|(% style="width:161px" %)AT+RXMODE=1,10 |(% style="width:337px" %)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.
822 +|(% style="width:161px" %)AT+RXMODE=2,500|(% style="width:337px" %)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
823 +|(% style="width:161px" %)AT+RXMODE=0,0|(% style="width:337px" %)Disable listening mode. This is the default settings.
824 +|(% style="width:161px" %) |(% style="width:337px" %)A6 aa bb cc  same as AT+RXMODE=aa,(bb<<8 ~| cc)
951 951  
952 -* LoRaWAN Downlink Command:
826 +**Downlink Command:**
953 953  
954 -07 01 aa bb  Same as AT+5VT=(aa bb)
828 +**0xA6 aa bb cc ** same as AT+RXMODE=aa,(bb<<8 | cc)
955 955  
956 -07 02 aa bb  Same as AT+3V3T=(aa bb)
957 957  
831 +**Example**:
958 958  
833 +The RS485-LN is set to AT+RXMODE=2,1000
959 959  
835 +There is a two Modbus commands in the RS485 network as below:
960 960  
961 -1.
962 -11. Buttons
837 +The Modbus master send a command: (% style="background-color:#ffc000" %)01 03 00 00 00 02 c4 0b
963 963  
964 -|**Button**|**Feature**
965 -|**RST**|Reboot RS485-BL
839 +And Modbus slave reply with: (% style="background-color:green" %)01 03 04 00 00 00 00 fa 33
966 966  
967 -1.
968 -11. +3V3 Output
841 +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
969 969  
970 -RS485-BL has a Controllable +3V3 output, user can use this output to power external sensor.
843 +[[image:image-20220602171200-9.png]]
971 971  
972 -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. 
973 973  
846 +(% 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.
974 974  
975 -The +3V3 output time can be controlled by AT Command.
976 976  
977 -**AT+3V3T=1000**
849 +== 3.7 Buttons ==
978 978  
979 -Means set +3v3 valid time to have 1000ms. So, the real +3v3 output will actually have 1000ms + sampling time for other sensors.
980 980  
852 +(% border="1" style="background-color:#f7faff; width:500px" %)
853 +|=**Button**|=(% style="width: 1420px;" %)**Feature**
854 +|**ACT**|(% style="width:1420px" %)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**
855 +|**RST**|(% style="width:1420px" %)Reboot RS485
856 +|**PRO**|(% style="width:1420px" %)Use for upload image, see [[How to Update Image>>||anchor="H6.1Howtoupgradetheimage3F"]]
981 981  
982 -By default, the AT+3V3T=0. This is a special case, means the +3V3 output is always on at any time
983 983  
859 +== 3.8 LEDs ==
984 984  
985 -1.
986 -11. +5V Output
861 +(% border="1" style="background-color:#f7faff; width:500px" %)
862 +|=**LEDs**|=**Feature**
863 +|**PWR**|Always on if there is power
864 +|**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.
987 987  
988 -RS485-BL has a Controllable +5V output, user can use this output to power external sensor.
989 989  
990 -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. 
867 += 4. Case Study =
991 991  
869 +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]]
992 992  
993 -The 5V output time can be controlled by AT Command.
994 994  
995 -**AT+5VT=1000**
872 += 5. Use AT Command =
996 996  
997 -Means set 5V valid time to have 1000ms. So, the real 5V output will actually have 1000ms + sampling time for other sensors.
874 +== 5.1 Access AT Command ==
998 998  
876 +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.
999 999  
1000 -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.
878 +[[image:1654162355560-817.png]]
1001 1001  
1002 1002  
881 +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:
1003 1003  
883 +[[image:1654162368066-342.png]]
1004 1004  
1005 -1.
1006 -11. LEDs
1007 1007  
1008 -|**LEDs**|**Feature**
1009 -|**LED1**|Blink when device transmit a packet.
886 +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/]]
1010 1010  
1011 -1.
1012 -11. Switch Jumper
1013 1013  
1014 -|**Switch Jumper**|**Feature**
1015 -|**SW1**|(((
1016 -ISP position: Upgrade firmware via UART
889 +== 5.2 Common AT Command Sequence ==
1017 1017  
1018 -Flash position: Configure device, check running status.
891 +=== 5.2.1 Multi-channel ABP mode (Use with SX1301/LG308) ===
892 +
893 +If device has not joined network yet:
894 +
895 +(% class="box infomessage" %)
896 +(((
897 +**AT+FDR**
1019 1019  )))
1020 -|**SW2**|(((
1021 -5V position: set to compatible with 5v I/O.
1022 1022  
1023 -3.3v position: set to compatible with 3.3v I/O.,
900 +(% class="box infomessage" %)
901 +(((
902 +**AT+NJM=0**
1024 1024  )))
1025 1025  
1026 -+3.3V: is always ON
905 +(% class="box infomessage" %)
906 +(((
907 +**ATZ**
908 +)))
1027 1027  
1028 -+5V: Only open before every sampling. The time is by default, it is AT+5VT=0.  Max open time. 5000 ms.
1029 1029  
1030 -1. Case Study
911 +If device already joined network:
1031 1031  
1032 -User can check this URL for some case studies.
913 +(% class="box infomessage" %)
914 +(((
915 +**AT+NJM=0**
916 +)))
1033 1033  
1034 -[[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]]
918 +(% class="box infomessage" %)
919 +(((
920 +**ATZ**
921 +)))
1035 1035  
1036 1036  
924 +=== 5.5.2 Single-channel ABP mode (Use with LG01/LG02) ===
1037 1037  
1038 1038  
1039 -1. Use AT Command
1040 -11. Access AT Command
927 +(% style="background-color:#dcdcdc" %)**AT+FDR** (%%) Reset Parameters to Factory Default, Keys Reserve
1041 1041  
1042 -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.
929 +(% style="background-color:#dcdcdc" %)**AT+NJM=0 **(%%)Set to ABP mode
1043 1043  
1044 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image027.png]]
931 +(% style="background-color:#dcdcdc" %)**AT+ADR=0** (%%)Set the Adaptive Data Rate Off
1045 1045  
933 +(% style="background-color:#dcdcdc" %)**AT+DR=5**   (%%)Set Data Rate
1046 1046  
1047 -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:
935 +(% style="background-color:#dcdcdc" %)**AT+TDC=60000** (%%) Set transmit interval to 60 seconds
1048 1048  
1049 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image028.png]]
937 +(% style="background-color:#dcdcdc" %)**AT+CHS=868400000**(%%) Set transmit frequency to 868.4Mhz
1050 1050  
939 +(% style="background-color:#dcdcdc" %)**AT+RX2FQ=868400000** (%%) Set RX2Frequency to 868.4Mhz (according to the result from server)
1051 1051  
941 +(% style="background-color:#dcdcdc" %)**AT+RX2DR=5**  (%%) Set RX2DR to match the downlink DR from server. see below
1052 1052  
1053 -More detail AT Command manual can be found at [[AT Command Manual>>path:#AT_COMMAND]]
943 +(% 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.
1054 1054  
945 +(% style="background-color:#dcdcdc" %)**ATZ**       (%%) Reset MCU
1055 1055  
1056 1056  
1057 -1.
1058 -11. Common AT Command Sequence
1059 -111. Multi-channel ABP mode (Use with SX1301/LG308)
948 +(% style="color:red" %)**Note:**
1060 1060  
1061 -If device has not joined network yet:
950 +(% style="color:red" %)1. Make sure the device is set to ABP mode in the IoT Server.
951 +2. Make sure the LG01/02 gateway RX frequency is exactly the same as AT+CHS setting.
952 +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.
953 +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
1062 1062  
1063 -AT+FDR
955 +[[image:1654162478620-421.png]]
1064 1064  
1065 -AT+NJM=0
1066 1066  
1067 -ATZ
958 += 6. FAQ =
1068 1068  
960 +== 6.1 How to upgrade the image? ==
1069 1069  
1070 -If device already joined network:
962 +The RS485-LN LoRaWAN Controller is shipped with a 3.5mm cable, the cable is used to upload image to RS485-LN to:
1071 1071  
1072 -AT+NJM=0
1073 -
1074 -ATZ
1075 -
1076 -1.
1077 -11.
1078 -111. Single-channel ABP mode (Use with LG01/LG02)
1079 -
1080 -AT+FDR   Reset Parameters to Factory Default, Keys Reserve
1081 -
1082 -AT+NJM=0 Set to ABP mode
1083 -
1084 -AT+ADR=0 Set the Adaptive Data Rate Off
1085 -
1086 -AT+DR=5  Set Data Rate
1087 -
1088 -AT+TDC=60000  Set transmit interval to 60 seconds
1089 -
1090 -AT+CHS=868400000 Set transmit frequency to 868.4Mhz
1091 -
1092 -AT+RX2FQ=868400000 Set RX2Frequency to 868.4Mhz (according to the result from server)
1093 -
1094 -AT+RX2DR=5  Set RX2DR to match the downlink DR from server. see below
1095 -
1096 -AT+DADDR=26 01 1A F1 Set Device Address to 26 01 1A F1, this ID can be found in the LoRa Server portal.
1097 -
1098 -ATZ          Reset MCU
1099 -
1100 -**Note:**
1101 -
1102 -1. Make sure the device is set to ABP mode in the IoT Server.
1103 -1. Make sure the LG01/02 gateway RX frequency is exactly the same as AT+CHS setting.
1104 -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.
1105 -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
1106 -
1107 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image029.png]]
1108 -
1109 -
1110 -1. FAQ
1111 -11. How to upgrade the image?
1112 -
1113 -The RS485-BL LoRaWAN Controller is shipped with a 3.5mm cable, the cable is used to upload image to RS485-BL to:
1114 -
1115 1115  * Support new features
1116 1116  * For bug fix
1117 1117  * Change LoRaWAN bands.
1118 1118  
1119 -Below shows the hardware connection for how to upload an image to RS485-BL:
968 +Below shows the hardware connection for how to upload an image to RS485-LN:
1120 1120  
1121 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image030.png]]
970 +[[image:1654162535040-878.png]]
1122 1122  
1123 1123  **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]].
1124 1124  
... ... @@ -1126,84 +1126,77 @@
1126 1126  
1127 1127  **Step3: **Open flashloader; choose the correct COM port to update.
1128 1128  
1129 -
1130 -|(((
1131 -HOLD PRO then press the RST button, SYS will be ON, then click next
978 +(((
979 +(% 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.
1132 1132  )))
1133 1133  
1134 -|(((
1135 -Board detected
1136 -)))
1137 1137  
1138 -|(((
1139 -
1140 -)))
983 +[[image:image-20220602175818-12.png]]
1141 1141  
1142 -[[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]]
1143 1143  
986 +[[image:image-20220602175848-13.png]]
1144 1144  
1145 1145  
1146 -[[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]]
989 +[[image:image-20220602175912-14.png]]
1147 1147  
1148 1148  
1149 -[[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]]
992 +**Notice**: In case user has lost the program cable. User can hand made one from a 3.5mm cable. The pin mapping is:
1150 1150  
994 +[[image:image-20220602175638-10.png]]
1151 1151  
1152 -1.
1153 -11. How to change the LoRa Frequency Bands/Region?
1154 1154  
1155 -User can follow the introduction for [[how to upgrade image>>path:#upgrade_image]]. When download the images, choose the required image file for download.
997 +== 6.2 How to change the LoRa Frequency Bands/Region? ==
1156 1156  
999 +User can follow the introduction for [[how to upgrade image>>||anchor="H6.1Howtoupgradetheimage3F"]]. When download the images, choose the required image file for download.
1157 1157  
1158 1158  
1159 -1.
1160 -11. How many RS485-Slave can RS485-BL connects?
1002 +== 6.3 How many RS485-Slave can RS485-BL connects? ==
1161 1161  
1162 -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]].
1004 +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"]].
1163 1163  
1164 1164  
1007 +== 6.4 Compatible question to ChirpStack and TTI LoRaWAN server ? ==
1165 1165  
1009 +When user need to use with ChirpStack or TTI. Please set AT+RPL=4.
1166 1166  
1167 -1. Trouble Shooting     
1168 -11. Downlink doesn’t work, how to solve it?
1011 +Detail info check this link: [[Set Packet Receiving Response Level>>doc:Main.End Device AT Commands and Downlink Command.WebHome||anchor="H7.23SetPacketReceivingResponseLevel"]]
1169 1169  
1170 -Please see this link for debug:
1171 1171  
1172 -[[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]] 
1014 += 7. Trouble Shooting =
1173 1173  
1016 +== 7.1 Downlink doesn’t work, how to solve it? ==
1174 1174  
1018 +Please see this link for debug: [[LoRaWAN Communication Debug>>doc:Main.LoRaWAN Communication Debug.WebHome]]
1175 1175  
1176 -1.
1177 -11. Why I can’t join TTN V3 in US915 /AU915 bands?
1178 1178  
1179 -It might about the channels mapping. Please see for detail.
1021 +== 7.2 Why I can’t join TTN V3 in US915 /AU915 bands? ==
1180 1180  
1181 -[[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]]
1023 +It might about the channels mapping. Please see for detail: [[Notice of Frequency band>>doc:Main.LoRaWAN Communication Debug.WebHome||anchor="H2.NoticeofUS9152FCN4702FAU915Frequencyband"]]
1182 1182  
1183 1183  
1026 += 8. Order Info =
1184 1184  
1185 -1. Order Info
1028 +(% style="color:blue" %)**Part Number: RS485-LN-XXX**
1186 1186  
1187 -**Part Number: RS485-BL-XXX**
1030 +(% style="color:blue" %)**XXX:**
1188 1188  
1189 -**XXX:**
1032 +* (% style="color:blue" %)**EU433**(%%): frequency bands EU433
1033 +* (% style="color:blue" %)**EU868**(%%): frequency bands EU868
1034 +* (% style="color:blue" %)**KR920**(%%): frequency bands KR920
1035 +* (% style="color:blue" %)**CN470**(%%): frequency bands CN470
1036 +* (% style="color:blue" %)**AS923**(%%): frequency bands AS923
1037 +* (% style="color:blue" %)**AU915**(%%): frequency bands AU915
1038 +* (% style="color:blue" %)**US915**(%%): frequency bands US915
1039 +* (% style="color:blue" %)**IN865**(%%): frequency bands IN865
1040 +* (% style="color:blue" %)**RU864**(%%): frequency bands RU864
1041 +* (% style="color:blue" %)**KZ865**(%%): frequency bands KZ865
1190 1190  
1191 -* **EU433**: frequency bands EU433
1192 -* **EU868**: frequency bands EU868
1193 -* **KR920**: frequency bands KR920
1194 -* **CN470**: frequency bands CN470
1195 -* **AS923**: frequency bands AS923
1196 -* **AU915**: frequency bands AU915
1197 -* **US915**: frequency bands US915
1198 -* **IN865**: frequency bands IN865
1199 -* **RU864**: frequency bands RU864
1200 -* **KZ865: **frequency bands KZ865
1043 += 9.Packing Info =
1201 1201  
1202 -1. Packing Info
1203 1203  
1204 1204  **Package Includes**:
1205 1205  
1206 -* RS485-BL x 1
1048 +* RS485-LN x 1
1207 1207  * Stick Antenna for LoRa RF part x 1
1208 1208  * Program cable x 1
1209 1209  
... ... @@ -1214,9 +1214,32 @@
1214 1214  * Package Size / pcs : 14.5 x 8 x 5 cm
1215 1215  * Weight / pcs : 170g
1216 1216  
1217 -1. Support
1059 += 10. FCC Caution for RS485LN-US915 =
1218 1218  
1219 -* 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.
1220 -* 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
1061 +Any Changes or modifications not expressly approved by the party responsible for compliance could void the user's authority to operate the equipment.
1221 1221  
1222 -[[support@dragino.com>>url:file:///D:/市场资料/说明书/LoRa/LT系列/support@dragino.com]]
1063 +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.
1064 +
1065 +
1066 +**IMPORTANT NOTE:**
1067 +
1068 +**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:
1069 +
1070 +—Reorient or relocate the receiving antenna.
1071 +
1072 +—Increase the separation between the equipment and receiver.
1073 +
1074 +—Connect the equipment into an outlet on a circuit different from that to which the receiver is connected.
1075 +
1076 +—Consult the dealer or an experienced radio/TV technician for help.
1077 +
1078 +
1079 +**FCC Radiation Exposure Statement:**
1080 +
1081 +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.
1082 +
1083 +
1084 += 11. Support =
1085 +
1086 +* 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.
1087 +* 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]].
1652954654347-831.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +138.7 KB
Content
1653266934636-343.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +176.5 KB
Content
1653267211009-519.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +138.7 KB
Content
1653268091319-405.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +399.3 KB
Content
1653268155545-638.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +113.7 KB
Content
1653268227651-549.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +1.3 MB
Content
1653269403619-508.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +27.8 KB
Content
1653269438444-278.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +26.6 KB
Content
1653269551753-223.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +138.7 KB
Content
1653269568276-930.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +131.4 KB
Content
1653269593172-426.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +142.6 KB
Content
1653269618463-608.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +27.7 KB
Content
1653269759169-150.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +294.0 KB
Content
1653269916228-732.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +143.3 KB
Content
1653270130359-810.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +197.8 KB
Content
1654157178836-407.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +179.9 KB
Content
1654157342174-798.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +31.9 KB
Content
1654158783574-851.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +40.6 KB
Content
1654159460680-153.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +24.9 KB
Content
1654160691922-496.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +109.3 KB
Content
1654162355560-817.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +670.0 KB
Content
1654162368066-342.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +192.9 KB
Content
1654162478620-421.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +158.9 KB
Content
1654162535040-878.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +670.0 KB
Content
image-20220602153621-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +23.4 KB
Content
image-20220602153621-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +22.2 KB
Content
image-20220602153621-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +22.3 KB
Content
image-20220602155039-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +24.6 KB
Content
image-20220602163333-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +48.2 KB
Content
image-20220602165351-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +10.6 KB
Content
image-20220602165351-7.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +19.3 KB
Content
image-20220602171200-8.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +276.1 KB
Content
image-20220602171200-9.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +10.0 KB
Content
image-20220602175638-10.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +85.5 KB
Content
image-20220602175743-11.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +85.5 KB
Content
image-20220602175818-12.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +102.5 KB
Content
image-20220602175848-13.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +250.9 KB
Content
image-20220602175912-14.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +176.1 KB
Content