Skip to Content
Last modified by Mengting Qiu on 2025/07/14 09:59
From version 32.12
edited by Xiaoling
on 2022/06/02 15:26
Change comment: There is no comment for this version
To version 58.42
edited by Xiaoling
on 2022/06/06 13:34
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -6,12 +6,18 @@
6 6  **RS485-LN – RS485 to LoRaWAN Converter User Manual**
7 7  
8 8  
9 +
10 +
9 9  **Table of Contents:**
10 10  
13 +{{toc/}}
11 11  
12 12  
13 13  
14 14  
18 +
19 +
20 +
15 15  = 1.Introduction =
16 16  
17 17  == 1.1 What is RS485-LN RS485 to LoRaWAN Converter ==
... ... @@ -18,23 +18,33 @@
18 18  
19 19  (((
20 20  (((
27 +(((
21 21  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.
22 22  )))
30 +)))
23 23  
24 24  (((
33 +(((
25 25  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.
26 26  )))
36 +)))
27 27  
28 28  (((
39 +(((
29 29  (% 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.
30 30  )))
42 +)))
31 31  
32 32  (((
45 +(((
33 33  (% 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.
47 +)))
34 34  
49 +(((
35 35  (% 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]]
36 36  )))
37 37  )))
53 +)))
38 38  
39 39  [[image:1653267211009-519.png||height="419" width="724"]]
40 40  
... ... @@ -74,10 +74,9 @@
74 74  * Preamble detection.
75 75  * 127 dB Dynamic Range RSSI.
76 76  * Automatic RF Sense and CAD with ultra-fast AFC.
77 -* Packet engine up to 256 bytes with CRC.
93 +* Packet engine up to 256 bytes with CRC
78 78  
79 79  
80 -
81 81  == 1.3 Features ==
82 82  
83 83  * LoRaWAN Class A & Class C protocol (default Class C)
... ... @@ -90,7 +90,6 @@
90 90  * Support Interrupt uplink (Since hardware version v1.2)
91 91  
92 92  
93 -
94 94  == 1.4 Applications ==
95 95  
96 96  * Smart Buildings & Home Automation
... ... @@ -101,7 +101,6 @@
101 101  * Smart Factory
102 102  
103 103  
104 -
105 105  == 1.5 Firmware Change log ==
106 106  
107 107  [[RS485-LN Image files – Download link and Change log>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/]]
... ... @@ -111,9 +111,13 @@
111 111  
112 112  (((
113 113  (((
127 +(((
114 114  v1.2: Add External Interrupt Pin.
129 +)))
115 115  
131 +(((
116 116  v1.0: Release
133 +)))
117 117  
118 118  
119 119  )))
... ... @@ -141,7 +141,9 @@
141 141  == 3.1 How it works? ==
142 142  
143 143  (((
161 +(((
144 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.
163 +)))
145 145  
146 146  
147 147  )))
... ... @@ -152,15 +152,20 @@
152 152  
153 153  [[image:1653268155545-638.png||height="334" width="724"]]
154 154  
174 +
155 155  (((
176 +(((
156 156  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:
178 +)))
157 157  
180 +(((
158 158  485A+ and 485B- of the sensor are connected to RS485A and RA485B of RS485-LN respectively.
182 +)))
159 159  
160 160  [[image:1653268227651-549.png||height="592" width="720"]]
161 161  
162 162  (((
163 -The LG308 is already set to connect to [[TTN V3 network >>path:eu1.cloud.thethings.network/]]. So what we need to now is only configure the TTN V3:
187 +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:
164 164  )))
165 165  
166 166  (((
... ... @@ -207,35 +207,42 @@
207 207  
208 208  [[image:1652953568895-172.png||height="232" width="724"]]
209 209  
234 +
210 210  == 3.3 Configure Commands to read data ==
211 211  
212 212  (((
213 213  (((
214 -There are plenty of RS485 devices in the market and each device has different command to read the valid data. To support these devices in flexible, RS485-LN supports flexible command set. User can use [[AT Commands>>path:#AT_COMMAND]] or LoRaWAN Downlink Command to configure what commands RS485-LN should send for each sampling and how to handle the return from RS485 devices.
239 +(((
240 +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.
215 215  )))
242 +)))
216 216  
217 217  (((
245 +(((
218 218  (% 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
219 219  )))
248 +
249 +
220 220  )))
251 +)))
221 221  
222 222  === 3.3.1 onfigure UART settings for RS485 or TTL communication ===
223 223  
224 224  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:
225 225  
226 -(% border="1" style="background-color:#ffffcc; color:green; width:795px" %)
227 -|(((
257 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)
258 +|=(% style="width: 110px;" %)(((
228 228  **AT Commands**
229 -)))|(% style="width:285px" %)(((
260 +)))|=(% style="width: 190px;" %)(((
230 230  **Description**
231 -)))|(% style="width:347px" %)(((
262 +)))|=(% style="width: 190px;" %)(((
232 232  **Example**
233 233  )))
234 -|(((
265 +|(% style="width:110px" %)(((
235 235  AT+BAUDR
236 -)))|(% style="width:285px" %)(((
267 +)))|(% style="width:190px" %)(((
237 237  Set the baud rate (for RS485 connection). Default Value is: 9600.
238 -)))|(% style="width:347px" %)(((
269 +)))|(% style="width:190px" %)(((
239 239  (((
240 240  AT+BAUDR=9600
241 241  )))
... ... @@ -244,11 +244,11 @@
244 244  Options: (1200,2400,4800,14400,19200,115200)
245 245  )))
246 246  )))
247 -|(((
278 +|(% style="width:110px" %)(((
248 248  AT+PARITY
249 -)))|(% style="width:285px" %)(((
280 +)))|(% style="width:190px" %)(((
250 250  Set UART parity (for RS485 connection)
251 -)))|(% style="width:347px" %)(((
282 +)))|(% style="width:190px" %)(((
252 252  (((
253 253  AT+PARITY=0
254 254  )))
... ... @@ -257,9 +257,9 @@
257 257  Option: 0: no parity, 1: odd parity, 2: even parity
258 258  )))
259 259  )))
260 -|(((
291 +|(% style="width:110px" %)(((
261 261  AT+STOPBIT
262 -)))|(% style="width:285px" %)(((
293 +)))|(% style="width:190px" %)(((
263 263  (((
264 264  Set serial stopbit (for RS485 connection)
265 265  )))
... ... @@ -267,7 +267,7 @@
267 267  (((
268 268  
269 269  )))
270 -)))|(% style="width:347px" %)(((
301 +)))|(% style="width:190px" %)(((
271 271  (((
272 272  AT+STOPBIT=0 for 1bit
273 273  )))
... ... @@ -281,6 +281,8 @@
281 281  )))
282 282  )))
283 283  
315 +
316 +
284 284  === 3.3.2 Configure sensors ===
285 285  
286 286  (((
... ... @@ -289,90 +289,47 @@
289 289  )))
290 290  )))
291 291  
292 -(% border="1" style="background-color:#ffffcc; color:green; width:806px" %)
293 -|**AT Commands**|(% style="width:418px" %)**Description**|(% style="width:256px" %)**Example**
294 -|AT+CFGDEV|(% style="width:418px" %)(((
325 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)
326 +|=(% style="width: 110px;" %)**AT Commands**|=(% style="width: 190px;" %)**Description**|=(% style="width: 190px;" %)**Example**
327 +|AT+CFGDEV|(% style="width:110px" %)(((
295 295  This command is used to configure the RS485/TTL devices; they won’t be used during sampling.
296 296  
297 297  AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,
298 298  
299 299  mm: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
300 -)))|(% style="width:256px" %)AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
333 +)))|(% style="width:190px" %)AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
301 301  
302 302  === 3.3.3 Configure read commands for each sampling ===
303 303  
304 304  (((
305 -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.
306 -)))
338 +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.
307 307  
308 -(((
309 -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.
310 -)))
311 -
312 -(((
313 313  To save the LoRaWAN network bandwidth, we might need to read data from different sensors and combine their valid value into a short payload.
314 -)))
315 315  
316 -(((
317 317  This section describes how to achieve above goals.
318 -)))
319 319  
320 -(((
321 -During each sampling, the RS485-BL can support 15 commands to read sensors. And combine the return to one or several uplink payloads.
322 -)))
344 +During each sampling, the RS485-LN can support 15 commands to read sensors. And combine the return to one or several uplink payloads.
323 323  
324 -(((
325 -**Command from RS485-BL to Sensor:**
326 -)))
327 327  
328 -(((
329 -RS485-BL can send out pre-set max 15 strings via **AT+COMMAD1**, **ATCOMMAND2**,…, to **AT+COMMANDF** . All commands are of same grammar.
330 -)))
347 +**Each RS485 commands include two parts:**
331 331  
332 -(((
333 -**Handle return from sensors to RS485-BL**:
334 -)))
349 +~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.
335 335  
336 -(((
337 -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**
338 -)))
351 +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.
339 339  
340 -* (((
341 -**AT+DATACUT**
342 -)))
353 +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
343 343  
344 -(((
345 -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.
346 -)))
347 347  
348 -* (((
349 -**AT+SEARCH**
350 -)))
351 -
352 -(((
353 -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.
354 -)))
355 -
356 -(((
357 -**Define wait timeout:**
358 -)))
359 -
360 -(((
361 -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
362 -)))
363 -
364 -(((
365 365  After we got the valid value from each RS485 commands, we need to combine them together with the command **AT+DATAUP**.
366 -)))
367 367  
368 -**Examples:**
369 369  
370 370  Below are examples for the how above AT Commands works.
371 371  
372 -**AT+COMMANDx : **This command will be sent to RS485/TTL devices during each sampling, Max command length is 14 bytes. The grammar is:
373 373  
374 -(% border="1" class="table-bordered" %)
375 -|(((
362 +**AT+COMMANDx : **This command will be sent to RS485 devices during each sampling, Max command length is 14 bytes. The grammar is:
363 +
364 +(% border="1" style="background-color:#4bacc6; color:white; width:499px" %)
365 +|(% style="width:496px" %)(((
376 376  **AT+COMMANDx=xx xx xx xx xx xx xx xx xx xx xx xx,m**
377 377  
378 378  **xx xx xx xx xx xx xx xx xx xx xx xx: The RS485 command to be sent**
... ... @@ -380,49 +380,15 @@
380 380  **m: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command**
381 381  )))
382 382  
383 -(((
384 384  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.
385 -)))
386 386  
387 -(((
388 -In the RS485-BL, we should use this command AT+COMMAND1=01 03 0B B8 00 02,1 for the same.
389 -)))
375 +In the RS485-LN, we should use this command AT+COMMAND1=01 03 0B B8 00 02,1 for the same.
390 390  
391 -(((
392 -**AT+SEARCHx**: This command defines how to handle the return from AT+COMMANDx.
393 -)))
394 394  
395 -(% border="1" class="table-bordered" %)
396 -|(((
397 -**AT+SEARCHx=aa,xx xx xx xx xx**
398 -
399 -* **aa: 1: prefix match mode; 2: prefix and suffix match mode**
400 -* **xx xx xx xx xx: match string. Max 5 bytes for prefix and 5 bytes for suffix**
401 -
402 -
403 -)))
404 -
405 -**Examples:**
406 -
407 -~1. For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
408 -
409 -If we set AT+SEARCH1=1,1E 56 34.      (max 5 bytes for prefix)
410 -
411 -The valid data will be all bytes after 1E 56 34 , so it is (% style="background-color:yellow" %)** 2e 30 58 5f 36 41 30 31 00 49**
412 -
413 -[[image:1653269403619-508.png]]
414 -
415 -2. For a return string from AT+COMMAND1:  16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
416 -
417 -If we set AT+SEARCH1=2, 1E 56 34+31 00 49
418 -
419 -Device will search the bytes between 1E 56 34 and 31 00 49. So it is (% style="background-color:yellow" %)** 2e 30 58 5f 36 41 30**
420 -
421 -[[image:1653269438444-278.png]]
422 -
423 423  **AT+DATACUTx : **This command defines how to handle the return from AT+COMMANDx, max return length is 45 bytes.
424 424  
425 -|(((
380 +(% border="1" style="background-color:#4bacc6; color:white; width:510px" %)
381 +|(% style="width:510px" %)(((
426 426  **AT+DATACUTx=a,b,c**
427 427  
428 428  * **a: length for the return of AT+COMMAND**
... ... @@ -430,48 +430,37 @@
430 430  * **c: define the position for valid value.  **
431 431  )))
432 432  
433 -Examples:
389 +**Examples:**
434 434  
435 435  * Grab bytes:
436 436  
437 -[[image:1653269551753-223.png||height="311" width="717"]]
393 +[[image:image-20220602153621-1.png]]
438 438  
395 +
439 439  * Grab a section.
440 440  
441 -[[image:1653269568276-930.png||height="325" width="718"]]
398 +[[image:image-20220602153621-2.png]]
442 442  
400 +
443 443  * Grab different sections.
444 444  
445 -[[image:1653269593172-426.png||height="303" width="725"]]
403 +[[image:image-20220602153621-3.png]]
446 446  
447 -(% style="color:red" %)**Note:**
405 +
406 +)))
448 448  
449 -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.
450 -
451 -Example:
452 -
453 -(% style="color:red" %)AT+COMMAND1=11 01 1E D0,0
454 -
455 -(% style="color:red" %)AT+SEARCH1=1,1E 56 34
456 -
457 -(% style="color:red" %)AT+DATACUT1=0,2,1~~5
458 -
459 -(% style="color:red" %)Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
460 -
461 -(% style="color:red" %)String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49
462 -
463 -(% style="color:red" %)Valid payload after DataCUT command: 2e 30 58 5f 36
464 -
465 -[[image:1653269618463-608.png]]
466 -
467 467  === 3.3.4 Compose the uplink payload ===
468 468  
469 469  (((
470 470  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.**
412 +
413 +
471 471  )))
472 472  
473 473  (((
474 -(% style="color:#4f81bd" %)**Examples: AT+DATAUP=0**
417 +(% style="color:#037691" %)**Examples: AT+DATAUP=0**
418 +
419 +
475 475  )))
476 476  
477 477  (((
... ... @@ -492,8 +492,10 @@
492 492  
493 493  [[image:1653269759169-150.png||height="513" width="716"]]
494 494  
495 -(% style="color:#4f81bd" %)**Examples: AT+DATAUP=1**
496 496  
441 +(% style="color:#037691" %)**Examples: AT+DATAUP=1**
442 +
443 +
497 497  Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**Multiply UPLINKs**.
498 498  
499 499  Final Payload is
... ... @@ -500,700 +500,1027 @@
500 500  
501 501  (% style="color:#4f81bd" %)**Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA**
502 502  
503 -1. Battery Info (2 bytes): Battery voltage
504 -1. PAYVER (1 byte): Defined by AT+PAYVER
505 -1. PAYLOAD COUNT (1 byte): Total how many uplinks of this sampling.
506 -1. PAYLOAD# (1 byte): Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT)
507 -1. DATA: Valid value: max 6 bytes(US915 version here, Notice*!) for each uplink so each uplink <= 11 bytes. For the last uplink, DATA will might less than 6 bytes
508 508  
509 -[[image:1653269916228-732.png||height="433" width="711"]]
451 +1. PAYVER: Defined by AT+PAYVER
452 +1. PAYLOAD COUNT: Total how many uplinks of this sampling.
453 +1. PAYLOAD#: Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT)
454 +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
510 510  
456 +[[image:image-20220602155039-4.png]]
511 511  
512 -So totally there will be 3 uplinks for this sampling, each uplink includes 6 bytes DATA
513 513  
514 -DATA1=RETURN1 Valid Value = (% style="background-color:green; color:white" %)20 20 0a 33 90 41
459 +So totally there will be 3 uplinks for this sampling, each uplink include 8 bytes DATA
515 515  
516 -DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10=(% style="background-color:green; color:white" %) 02 aa 05 81 0a 20
461 +DATA1=RETURN1 Valid Value + the first two of Valid value of RETURN10= **20 20 0a 33 90 41 02 aa**
517 517  
518 -DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 = (% style="background-color:green; color:white" %)20 20 20 2d 30
463 +DATA2=3^^rd^^ ~~ 10^^th^^ byte of Valid value of RETURN10= **05 81 0a 20 20 20 20 2d**
519 519  
520 -Below are the uplink payloads:
465 +DATA3=the rest of Valid value of RETURN10= **30**
521 521  
522 -[[image:1653270130359-810.png]]
523 523  
468 +(% 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:
524 524  
525 -(% style="color:red" %)**Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:**
470 + ~* For AU915/AS923 bands, if UplinkDwell time=0, max 51 bytes for each uplink.
526 526  
527 - ~* For AU915/AS923 bands, if UplinkDwell time=0, max 51 bytes for each uplink ( so 51 -5 = 46 max valid date)
472 + * For AU915/AS923 bands, if UplinkDwell time=0, max 11 bytes for each uplink.
528 528  
529 - * For AU915/AS923 bands, if UplinkDwell time=1, max 11 bytes for each uplink ( so 11 -5 = 6 max valid date).
474 + * For US915 band, max 11 bytes for each uplink.
530 530  
531 - * For US915 band, max 11 bytes for each uplink ( so 11 -5 = 6 max valid date).
476 + ~* For all other bands: max 51 bytes for each uplink.
532 532  
533 - ~* For all other bands: max 51 bytes for each uplink  ( so 51 -5 = 46 max valid date).
534 534  
535 -=== 3.3.5 Uplink on demand ===
479 +Below are the uplink payloads:
536 536  
537 -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.
481 +[[image:1654157178836-407.png]]
538 538  
539 -Downlink control command:
540 540  
541 -[[0x08 command>>path:#downlink_08]]: Poll an uplink with current command set in RS485-BL.
484 +=== 3.3.5 Uplink on demand ===
542 542  
543 -[[0xA8 command>>path:#downlink_A8]]: Send a command to RS485-BL and uplink the output from sensors.
486 +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.
544 544  
488 +Downlink control command:
545 545  
490 +**0x08 command**: Poll an uplink with current command set in RS485-LN.
546 546  
547 -1.
548 -11.
549 -111. Uplink on Interrupt
492 +**0xA8 command**: Send a command to RS485-LN and uplink the output from sensors.
550 550  
551 -Put the interrupt sensor between 3.3v_out and GPIO ext.[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image022.png]]
552 552  
553 -AT+INTMOD=0  Disable Interrupt
554 554  
555 -AT+INTMOD=1  Interrupt trigger by rising or falling edge.
496 +=== 3.3.6 Uplink on Interrupt ===
556 556  
557 -AT+INTMOD=2  Interrupt trigger by falling edge. ( Default Value)
498 +RS485-LN support external Interrupt uplink since hardware v1.2 release.
558 558  
559 -AT+INTMOD=3  Interrupt trigger by rising edge.
500 +[[image:1654157342174-798.png]]
560 560  
502 +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.
561 561  
562 -1.
563 -11. Uplink Payload
564 564  
565 -|**Size(bytes)**|**2**|**1**|**Length depends on the return from the commands**
566 -|Value|(((
567 -Battery(mV)
505 +== 3.4 Uplink Payload ==
568 568  
569 -&
570 570  
571 -Interrupt _Flag
572 -)))|(((
573 -PAYLOAD_VER
508 +[[image:image-20220606110929-1.png]]
574 574  
575 -
576 -)))|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.
577 -
578 578  Below is the decoder for the first 3 bytes. The rest bytes are dynamic depends on different RS485 sensors.
579 579  
580 580  
581 -function Decoder(bytes, port) {
513 +== 3.5 Configure RS485-BL via AT or Downlink ==
582 582  
583 -~/~/Payload Formats of RS485-BL Deceive
515 +(((
516 +User can configure RS485-LN via AT Commands or LoRaWAN Downlink Commands
517 +)))
584 584  
585 -return {
586 -
587 - ~/~/Battery,units:V
588 -
589 - BatV:((bytes[0]<<8 | bytes[1])&0x7fff)/1000,
590 -
591 - ~/~/GPIO_EXTI 
592 -
593 - EXTI_Trigger:(bytes[0] & 0x80)? "TRUE":"FALSE",
594 -
595 - ~/~/payload of version
596 -
597 - Pay_ver:bytes[2],
598 -
599 - };
600 -
601 - }
602 -
603 -
604 -
605 -
606 -
607 -
608 -
609 -TTN V3 uplink screen shot.
610 -
611 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png]]
612 -
613 -1.
614 -11. Configure RS485-BL via AT or Downlink
615 -
616 -User can configure RS485-BL via [[AT Commands >>path:#_​Using_the_AT]]or LoRaWAN Downlink Commands
617 -
519 +(((
618 618  There are two kinds of Commands:
521 +)))
619 619  
620 -* **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
523 +* (((
524 +(% 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]]
525 +)))
621 621  
622 -* **Sensor Related Commands**: These commands are special designed for RS485-BL.  User can see these commands below:
527 +* (((
528 +(% style="color:#4f81bd" %)**Sensor Related Commands**(%%): These commands are special designed for RS485-LN.  User can see these commands below:
529 +)))
623 623  
624 -1.
625 -11.
626 -111. Common Commands:
531 +(((
532 +
533 +)))
627 627  
628 -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]]
629 629  
536 +=== 3.5.1 Common Commands ===
630 630  
631 -1.
632 -11.
633 -111. Sensor related commands:
538 +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]]
634 634  
635 -==== Choose Device Type (RS485 or TTL) ====
636 636  
637 -RS485-BL can connect to either RS485 sensors or TTL sensor. User need to specify what type of sensor need to connect.
541 +=== 3.5.2 Sensor related commands ===
638 638  
639 -* AT Command
543 +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.
640 640  
641 -**AT+MOD=1** ~/~/ Set to support RS485-MODBUS type sensors. User can connect multiply RS485 , Modbus sensors to the A / B pins.
545 +[[image:image-20220602163333-5.png||height="263" width="1160"]]
642 642  
643 -**AT+MOD=2** ~/~/ Set to support TTL Level sensors, User can connect one TTL Sensor to the TXD/RXD/GND pins.
547 +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)
644 644  
645 645  
646 -* Downlink Payload
550 +=== 3.5.3 Sensor related commands ===
647 647  
648 -**0A aa**     à same as AT+MOD=aa
649 649  
650 650  
651 651  
652 -==== [[RS485 Debug Command>>path:#downlink_A8]] (AT+CFGDEV) ====
555 +==== **RS485 Debug Command** ====
653 653  
654 -This command is used to configure the RS485 or TTL sensors; they won’t be used during sampling.
557 +(((
558 +This command is used to configure the RS485 devices; they won’t be used during sampling.
559 +)))
655 655  
656 -* AT Command
561 +* (((
562 +**AT Command**
563 +)))
657 657  
658 -AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
565 +(% class="box infomessage" %)
566 +(((
567 +(((
568 +**AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m**
569 +)))
570 +)))
659 659  
660 -m: 0: no CRC; 1: add CRC-16/MODBUS in the end of this command.
572 +(((
573 +m: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
574 +)))
661 661  
576 +* (((
577 +**Downlink Payload**
578 +)))
662 662  
663 -
664 -* Downlink Payload
665 -
580 +(((
666 666  Format: A8 MM NN XX XX XX XX YY
582 +)))
667 667  
584 +(((
668 668  Where:
586 +)))
669 669  
670 -* MM: 1: add CRC-16/MODBUS ; 0: no CRC
671 -* NN: The length of RS485 command
672 -* XX XX XX XX: RS485 command total NN bytes
673 -* 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
588 +* (((
589 +MM: 1: add CRC-16/MODBUS ; 0: no CRC
590 +)))
591 +* (((
592 +NN: The length of RS485 command
593 +)))
594 +* (((
595 +XX XX XX XX: RS485 command total NN bytes
596 +)))
597 +* (((
598 +(((
599 +YY: How many bytes will be uplink from the return of this RS485 command,
600 +)))
674 674  
675 -**Example 1:**
602 +* (((
603 +if YY=0, RS485-LN will execute the downlink command without uplink;
604 +)))
605 +* (((
606 +if YY>0, RS485-LN will uplink total YY bytes from the output of this RS485 command; Fport=200
607 +)))
608 +* (((
609 +if YY=FF, RS485-LN will uplink RS485 output with the downlink command content; Fport=200.
610 +)))
611 +)))
676 676  
613 +(((
614 +**Example 1** ~-~-> Configure without ask for uplink (YY=0)
615 +)))
616 +
617 +(((
677 677  To connect a Modbus Alarm with below commands.
619 +)))
678 678  
679 -* The command to active alarm is: 0A 05 00 04 00 01 4C B0. Where 0A 05 00 04 00 01 is the Modbus command to read the register 00 40 where stored the DI status. The 4C B0 is the CRC-16/MODBUS which calculate manually.
621 +* (((
622 +The command to active alarm is: 0A 05 00 04 00 01 4C B0. Where 0A 05 00 04 00 01 is the Modbus command to read the register 00 40 where stored the DI status. The 4C B0 is the CRC-16/MODBUS which calculate manually.
623 +)))
680 680  
681 -* The command to deactivate alarm is: 0A 05 00 04 00 00 8D 70. Where 0A 05 00 04 00 00 is the Modbus command to read the register 00 40 where stored the DI status. The 8D 70 is the CRC-16/MODBUS which calculate manually.
625 +* (((
626 +The command to deactivate alarm is: 0A 05 00 04 00 00 8D 70. Where 0A 05 00 04 00 00 is the Modbus command to read the register 00 40 where stored the DI status. The 8D 70 is the CRC-16/MODBUS which calculate manually.
627 +)))
682 682  
629 +(((
683 683  So if user want to use downlink command to control to RS485 Alarm, he can use:
631 +)))
684 684  
685 -**A8 01 06 0A 05 00 04 00 01 00**: to activate the RS485 Alarm
633 +(((
634 +(% style="color:#4f81bd" %)**A8 01 06 0A 05 00 04 00 01 00**(%%): to activate the RS485 Alarm
635 +)))
686 686  
687 -**A8 01 06 0A 05 00 04 00 00 00**: to deactivate the RS485 Alarm
637 +(((
638 +(% style="color:#4f81bd" %)**A8 01 06 0A 05 00 04 00 00 00**(%%): to deactivate the RS485 Alarm
639 +)))
688 688  
641 +(((
689 689  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.
643 +)))
690 690  
645 +(((
646 +
647 +)))
691 691  
692 -**Example 2:**
649 +(((
650 +**Example 2** ~-~-> Configure with requesting uplink and original downlink command (**YY=FF**)
651 +)))
693 693  
694 -Check TTL Sensor return:
653 +(((
654 +User in IoT server send a downlink command: (% style="color:#4f81bd" %)**A8 01 06 0A 08 00 04 00 01 YY**
655 +)))
695 695  
696 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image024.png]]
657 +(((
658 +
659 +)))
697 697  
661 +(((
662 +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:
663 +)))
698 698  
665 +(((
666 + **A8** (% style="color:#4f81bd" %)**0A 08 00 04 00  **(% style="color:red" %)**01 06** ** **(% style="color:green" %)**0A 08 00 04 00 00**
667 +)))
699 699  
669 +(((
670 + [[image:1654159460680-153.png]]
671 +)))
700 700  
701 -==== Set Payload version ====
702 702  
674 +
675 +
676 +==== **Set Payload version** ====
677 +
678 +(((
703 703  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.
680 +)))
704 704  
705 -* AT Command:
682 +* (((
683 +**AT Command:**
684 +)))
706 706  
707 -AT+PAYVER: Set PAYVER field = 1
686 +(% class="box infomessage" %)
687 +(((
688 +(((
689 +**AT+PAYVER: Set PAYVER field = 1**
690 +)))
691 +)))
708 708  
693 +* (((
694 +**Downlink Payload:**
695 +)))
709 709  
710 -* Downlink Payload:
697 +(((
698 +**0xAE 01**  ~-~-> Set PAYVER field =  0x01
699 +)))
711 711  
712 -0xAE 01   à Set PAYVER field =  0x01
701 +(((
702 +**0xAE 0F**   ~-~-> Set PAYVER field =  0x0F
703 +)))
713 713  
714 -0xAE 0F   à Set PAYVER field =  0x0F
715 715  
716 716  
717 -==== Set RS485 Sampling Commands ====
718 718  
719 -AT+COMMANDx, AT+DATACUTx and AT+SEARCHx
708 +==== **Set RS485 Sampling Commands** ====
720 720  
721 -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]].
710 +(((
711 +AT+COMMANDx or AT+DATACUTx
712 +)))
722 722  
714 +(((
715 +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"]].
716 +)))
723 723  
724 -* AT Command:
718 +(((
719 +
720 +)))
725 725  
726 -AT+COMMANDx: Configure RS485 read command to sensor.
722 +* (((
723 +**AT Command:**
724 +)))
727 727  
728 -AT+DATACUTx: Configure how to handle return from RS485 devices.
726 +(% class="box infomessage" %)
727 +(((
728 +(((
729 +**AT+COMMANDx: Configure RS485 read command to sensor.**
730 +)))
731 +)))
729 729  
730 -AT+SEARCHx: Configure search command
733 +(% class="box infomessage" %)
734 +(((
735 +(((
736 +**AT+DATACUTx: Configure how to handle return from RS485 devices.**
737 +)))
738 +)))
731 731  
740 +(((
741 +
742 +)))
732 732  
733 -* Downlink Payload:
744 +* (((
745 +**Downlink Payload:**
746 +)))
734 734  
735 -0xAF downlink command can be used to set AT+COMMANDx or AT+DATACUTx.
748 +(((
749 +**0xAF** downlink command can be used to set AT+COMMANDx or AT+DATACUTx.
750 +)))
736 736  
737 -Note: if user use AT+COMMANDx to add a new command, he also need to send AT+DATACUTx downlink.
752 +(((
753 +(% style="color:red" %)**Note**(%%): if user use AT+COMMANDx to add a new command, he also need to send AT+DATACUTx downlink.
754 +)))
738 738  
756 +(((
739 739  Format: AF MM NN LL XX XX XX XX YY
758 +)))
740 740  
760 +(((
741 741  Where:
762 +)))
742 742  
743 -* MM: the ATCOMMAND or AT+DATACUT to be set. Value from 01 ~~ 0F,
744 -* NN: 0: no CRC; 1: add CRC-16/MODBUS ; 2: set the AT+DATACUT value.
745 -* LL: The length of AT+COMMAND or AT+DATACUT command
746 -* XX XX XX XX: AT+COMMAND or AT+DATACUT command
747 -* 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.
764 +* (((
765 +MM: the ATCOMMAND or AT+DATACUT to be set. Value from 01 ~~ 0F,
766 +)))
767 +* (((
768 +NN:  0: no CRC; 1: add CRC-16/MODBUS ; 2: set the AT+DATACUT value.
769 +)))
770 +* (((
771 +LL:  The length of AT+COMMAND or AT+DATACUT command
772 +)))
773 +* (((
774 +XX XX XX XX: AT+COMMAND or AT+DATACUT command
775 +)))
776 +* (((
777 +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.
778 +)))
748 748  
749 -Example:
780 +(((
781 +**Example:**
782 +)))
750 750  
751 -**AF 03 01 06 0A 05 00 04 00 01 00**: Same as AT+COMMAND3=0A 05 00 04 00 01,1
784 +(((
785 +(% 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
786 +)))
752 752  
753 -**AF 03 02 06 10 01 05 06 09 0A 00**: Same as AT+DATACUT3=**16**,**1**,**5+6+9+10**
788 +(((
789 +(% 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**
790 +)))
754 754  
755 -**AF 03 02 06 0B 02 05 07 08 0A 00**: Same as AT+DATACUT3=**11**,**2**,**5~~7+8~~10**
792 +(((
793 +(% 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**
794 +)))
756 756  
757 757  
758 -0xAB downlink command can be used for set AT+SEARCHx
759 759  
760 -Example: **AB aa 01 03 xx xx xx** (03 here means there are total 3 bytes after 03) So
761 761  
762 -* AB aa 01 03 xx xx xx  same as AT+SEARCHaa=1,xx xx xx
763 -* 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
799 +==== **Fast command to handle MODBUS device** ====
764 764  
765 -**AB aa 02 03 xx xx xx 02 yy yy**  same as **AT+SEARCHaa=2,xx xx xx+yy yy**
801 +(((
802 +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]].
803 +)))
766 766  
805 +(((
806 +This command is valid since v1.3 firmware version
807 +)))
767 767  
768 -==== Fast command to handle MODBUS device ====
809 +(((
810 +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.
811 +)))
769 769  
770 -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]].
813 +(((
814 +
815 +)))
771 771  
772 -This command is valid since v1.3 firmware version
817 +(((
818 +**Example:**
819 +)))
773 773  
821 +* (((
822 +AT+MBFUN=1 and AT+DATACUT1/AT+DATACUT2 are not configure (0,0,0). So RS485-LN.
823 +)))
824 +* (((
825 +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.
826 +)))
827 +* (((
828 +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.
829 +)))
774 774  
775 -AT+MBFUN has only two value:
831 +[[image:image-20220602165351-6.png]]
776 776  
777 -* AT+MBFUN=1: Enable Modbus reading. And get response base on the MODBUS return
833 +[[image:image-20220602165351-7.png]]
778 778  
779 -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.
780 780  
781 -* AT+MBFUN=0: Disable Modbus fast reading.
782 782  
783 -Example:
784 784  
785 -* AT+MBFUN=1 and AT+DATACUT1/AT+DATACUT2 are not configure (0,0,0).
786 -* 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.
787 -* 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.
838 +==== **RS485 command timeout** ====
788 788  
789 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image025.png]]
840 +(((
841 +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.
842 +)))
790 790  
844 +(((
845 +Default value: 0, range:  0 ~~ 65 seconds
846 +)))
791 791  
792 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image026.png]]
848 +* (((
849 +**AT Command:**
850 +)))
793 793  
852 +(% class="box infomessage" %)
853 +(((
854 +(((
855 +**AT+CMDDLaa=hex(bb cc)*1000**
856 +)))
857 +)))
794 794  
795 -* Downlink Commands:
859 +(((
860 +**Example:**
861 +)))
796 796  
797 -A9 aa -à Same as AT+MBFUN=aa
863 +(((
864 +**AT+CMDDL1=1000** to send the open time to 1000ms
865 +)))
798 798  
867 +(((
868 +
869 +)))
799 799  
800 -==== RS485 command timeout ====
871 +* (((
872 +**Downlink Payload:**
873 +)))
801 801  
802 -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.
875 +(((
876 +**0x AA aa bb cc**
877 +)))
803 803  
804 -Default value: 0, range:  0 ~~ 5 seconds
879 +(((
880 +Same as: AT+CMDDLaa=hex(bb cc)*1000
881 +)))
805 805  
883 +(((
884 + **Example:**
885 +)))
806 806  
807 -* AT Command:
887 +(((
888 + 0xAA 01 00 01  ~-~-> Same as **AT+CMDDL1=1000 ms**
889 +)))
808 808  
809 -AT+CMDDLaa=hex(bb cc)
810 810  
811 -Example:
812 812  
813 -**AT+CMDDL1=1000** to send the open time to 1000ms
814 814  
894 +==== **Uplink payload mode** ====
815 815  
816 -* Downlink Payload:
896 +(((
897 +Define to use one uplink or multiple uplinks for the sampling.
898 +)))
817 817  
818 -0x AA aa bb cc
900 +(((
901 +The use of this command please see: [[Compose Uplink payload>>||anchor="H3.3.4Composetheuplinkpayload"]]
902 +)))
819 819  
820 -Same as: AT+CMDDLaa=hex(bb cc)
904 +* (((
905 +**AT Command:**
906 +)))
821 821  
822 - Example:
908 +(% class="box infomessage" %)
909 +(((
910 +(((
911 +**AT+DATAUP=0**
912 +)))
913 +)))
823 823  
824 - 0xAA 01 03 E8  à Same as **AT+CMDDL1=1000 ms**
915 +(% class="box infomessage" %)
916 +(((
917 +(((
918 +**AT+DATAUP=1**
919 +)))
920 +)))
825 825  
922 +(((
923 +
924 +)))
826 826  
827 -==== [[Uplink>>path:#downlink_A8]] payload mode ====
926 +* (((
927 +**Downlink Payload:**
928 +)))
828 828  
829 -Define to use one uplink or multiple uplinks for the sampling.
930 +(((
931 +**0xAD 00**  **~-~->** Same as AT+DATAUP=0
932 +)))
830 830  
831 -The use of this command please see: [[Compose Uplink payload>>path:#DataUP]]
934 +(((
935 +**0xAD 01**  **~-~->** Same as AT+DATAUP=1
936 +)))
832 832  
833 -* AT Command:
834 834  
835 -AT+DATAUP=0
836 836  
837 -AT+DATAUP=1
838 838  
941 +==== **Manually trigger an Uplink** ====
839 839  
840 -* Downlink Payload:
943 +(((
944 +Ask device to send an uplink immediately.
945 +)))
841 841  
842 -0xAD 00   à Same as AT+DATAUP=0
947 +* (((
948 +**AT Command:**
949 +)))
843 843  
844 -0xAD 01   à Same as AT+DATAUP=1
951 +(((
952 +No AT Command for this, user can press the [[ACT button>>||anchor="H3.7Buttons"]] for 1 second for the same.
953 +)))
845 845  
955 +(((
956 +
957 +)))
846 846  
847 -==== Manually trigger an Uplink ====
959 +* (((
960 +**Downlink Payload:**
961 +)))
848 848  
849 -Ask device to send an uplink immediately.
963 +(((
964 +**0x08 FF**, RS485-LN will immediately send an uplink.
965 +)))
850 850  
851 -* Downlink Payload:
852 852  
853 -0x08 FF, RS485-BL will immediately send an uplink.
854 854  
855 855  
856 -==== Clear RS485 Command ====
970 +==== **Clear RS485 Command** ====
857 857  
972 +(((
858 858  The AT+COMMANDx and AT+DATACUTx settings are stored in special location, user can use below command to clear them.
974 +)))
859 859  
976 +* (((
977 +**AT Command:**
978 +)))
860 860  
861 -* AT Command:
862 -
980 +(((
863 863  **AT+CMDEAR=mm,nn**   mm: start position of erase ,nn: stop position of erase
982 +)))
864 864  
984 +(((
865 865  Etc. AT+CMDEAR=1,10 means erase AT+COMMAND1/AT+DATACUT1 to AT+COMMAND10/AT+DATACUT10
986 +)))
866 866  
988 +(((
867 867  Example screen shot after clear all RS485 commands. 
990 +)))
868 868  
992 +(((
993 +
994 +)))
869 869  
870 -
996 +(((
871 871  The uplink screen shot is:
998 +)))
872 872  
873 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png]]
1000 +[[image:1654160691922-496.png]]
874 874  
875 875  
876 -* Downlink Payload:
1003 +* (((
1004 +**Downlink Payload:**
1005 +)))
877 877  
878 -0x09 aa bb same as AT+CMDEAR=aa,bb
1007 +(((
1008 +**0x09 aa bb** same as AT+CMDEAR=aa,bb
1009 +)))
879 879  
880 880  
881 -==== Set Serial Communication Parameters ====
882 882  
1013 +
1014 +==== **Set Serial Communication Parameters** ====
1015 +
1016 +(((
883 883  Set the Rs485 serial communication parameters:
1018 +)))
884 884  
885 -* AT Command:
1020 +* (((
1021 +**AT Command:**
1022 +)))
886 886  
1024 +(((
887 887  Set Baud Rate:
1026 +)))
888 888  
889 -AT+BAUDR=9600    ~/~/ Options: (1200,2400,4800,14400,19200,115200)
1028 +(% class="box infomessage" %)
1029 +(((
1030 +(((
1031 +**AT+BAUDR=9600**    ~/~/ Options: (1200,2400,4800,14400,19200,115200)
1032 +)))
1033 +)))
890 890  
1035 +(((
1036 +Set UART Parity
1037 +)))
891 891  
892 -Set UART parity
1039 +(% class="box infomessage" %)
1040 +(((
1041 +(((
1042 +**AT+PARITY=0**    ~/~/ Option: 0: no parity, 1: odd parity, 2: even parity
1043 +)))
1044 +)))
893 893  
894 -AT+PARITY=0    ~/~/ Option: 0: no parity, 1: odd parity, 2: even parity
895 -
896 -
1046 +(((
897 897  Set STOPBIT
1048 +)))
898 898  
899 -AT+STOPBIT=0    ~/~/ Option: 0 for 1bit; 1 for 1.5 bit ; 2 for 2 bits
1050 +(% class="box infomessage" %)
1051 +(((
1052 +(((
1053 +**AT+STOPBIT=0**    ~/~/ Option: 0 for 1bit; 1 for 1.5 bit ; 2 for 2 bits
1054 +)))
1055 +)))
900 900  
1057 +(((
1058 +
1059 +)))
901 901  
902 -* Downlink Payload:
1061 +* (((
1062 +**Downlink Payload:**
1063 +)))
903 903  
904 -A7 01 aa bb: Same  AT+BAUDR=hex(aa bb)*100
1065 +(((
1066 +**A7 01 aa bb**: Same  AT+BAUDR=hex(aa bb)*100
1067 +)))
905 905  
906 -Example:
1069 +(((
1070 +**Example:**
1071 +)))
907 907  
908 -* A7 01 00 60   same as AT+BAUDR=9600
909 -* A7 01 04 80  same as AT+BAUDR=115200
1073 +* (((
1074 +A7 01 00 60   same as AT+BAUDR=9600
1075 +)))
1076 +* (((
1077 +A7 01 04 80  same as AT+BAUDR=115200
1078 +)))
910 910  
1080 +(((
911 911  A7 02 aa: Same as  AT+PARITY=aa  (aa value: 00 , 01 or 02)
1082 +)))
912 912  
1084 +(((
913 913  A7 03 aa: Same as  AT+STOPBIT=aa  (aa value: 00 , 01 or 02)
1086 +)))
914 914  
915 915  
916 -==== Control output power duration ====
917 917  
918 -User can set the output power duration before each sampling.
919 919  
920 -* AT Command:
1091 +== 3.6 Listening mode for RS485 network ==
921 921  
922 -Example:
1093 +(((
1094 +This feature support since firmware v1.4
1095 +)))
923 923  
924 -AT+3V3T=1000 ~/~/ 3V3 output power will open 1s before each sampling.
1097 +(((
1098 +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.
1099 +)))
925 925  
926 -AT+5VT=1000 ~/~/ +5V output power will open 1s before each sampling.
1101 +[[image:image-20220602171200-8.png||height="567" width="1007"]]
927 927  
1103 +(((
1104 +To enable the listening mode, use can run the command AT+RXMODE.
1105 +)))
928 928  
929 -* LoRaWAN Downlink Command:
1107 +(((
1108 +
1109 +)))
930 930  
931 -07 01 aa bb  Same as AT+5VT=(aa bb)
1111 +(% border="1" cellspacing="10" style="background-color:#ffffcc; width:500px" %)
1112 +|=(% style="width: 161px;" %)(((
1113 +**Command example:**
1114 +)))|=(% style="width: 337px;" %)(((
1115 +**Function**
1116 +)))
1117 +|(% style="width:161px" %)(((
1118 +AT+RXMODE=1,10
1119 +)))|(% style="width:337px" %)(((
1120 +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.
1121 +)))
1122 +|(% style="width:161px" %)(((
1123 +AT+RXMODE=2,500
1124 +)))|(% style="width:337px" %)(((
1125 +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
1126 +)))
1127 +|(% style="width:161px" %)(((
1128 +AT+RXMODE=0,0
1129 +)))|(% style="width:337px" %)(((
1130 +Disable listening mode. This is the default settings.
1131 +)))
1132 +|(% style="width:161px" %)(((
1133 +
1134 +)))|(% style="width:337px" %)(((
1135 +A6 aa bb cc  same as AT+RXMODE=aa,(bb<<8 | cc)
1136 +)))
932 932  
933 -07 02 aa bb  Same as AT+3V3T=(aa bb)
1138 +(((
1139 +**Downlink Command:**
1140 +)))
934 934  
1142 +(((
1143 +**0xA6 aa bb cc ** same as AT+RXMODE=aa,(bb<<8 | cc)
1144 +)))
935 935  
1146 +(((
1147 +
1148 +)))
936 936  
1150 +(((
1151 +**Example**:
1152 +)))
937 937  
938 -1.
939 -11. Buttons
1154 +(((
1155 +The RS485-LN is set to AT+RXMODE=2,1000
1156 +)))
940 940  
941 -|**Button**|**Feature**
942 -|**RST**|Reboot RS485-BL
1158 +(((
1159 +There is a two Modbus commands in the RS485 network as below:
1160 +)))
943 943  
944 -1.
945 -11. +3V3 Output
1162 +(((
1163 +The Modbus master send a command: (% style="background-color:#ffc000" %)01 03 00 00 00 02 c4 0b
1164 +)))
946 946  
947 -RS485-BL has a Controllable +3V3 output, user can use this output to power external sensor.
1166 +(((
1167 +And Modbus slave reply with: (% style="background-color:green" %)01 03 04 00 00 00 00 fa 33
1168 +)))
948 948  
949 -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. 
1170 +(((
1171 +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
1172 +)))
950 950  
1174 +(((
1175 +[[image:image-20220602171200-9.png]]
1176 +)))
951 951  
952 -The +3V3 output time can be controlled by AT Command.
1178 +(((
1179 +
1180 +)))
953 953  
954 -**AT+3V3T=1000**
1182 +(((
1183 +(% 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.
1184 +)))
955 955  
956 -Means set +3v3 valid time to have 1000ms. So, the real +3v3 output will actually have 1000ms + sampling time for other sensors.
957 957  
1187 +== 3.7 Buttons ==
958 958  
959 -By default, the AT+3V3T=0. This is a special case, means the +3V3 output is always on at any time
960 960  
1190 +(% border="1" cellspacing="10" style="background-color:#f7faff; width:400px" %)
1191 +|=(% style="width: 50px;" %)**Button**|=(% style="width: 350px;" %)**Feature**
1192 +|(% style="width:50px" %)**ACT**|(% style="width:350px" %)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**
1193 +|(% style="width:50px" %)**RST**|(% style="width:350px" %)Reboot RS485
1194 +|(% style="width:50px" %)**PRO**|(% style="width:350px" %)Use for upload image, see [[How to Update Image>>||anchor="H6.1Howtoupgradetheimage3F"]]
961 961  
962 -1.
963 -11. +5V Output
1196 +== 3.8 LEDs ==
964 964  
965 -RS485-BL has a Controllable +5V output, user can use this output to power external sensor.
966 966  
967 -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. 
1199 +(% border="1" cellspacing="10" style="background-color:#f7faff; width:430px" %)
1200 +|=(% style="width: 50px;" %)**LEDs**|=(% style="width: 380px;" %)**Feature**
1201 +|**PWR**|Always on if there is power
1202 +|**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.
968 968  
1204 += 4. Case Study =
969 969  
970 -The 5V output time can be controlled by AT Command.
1206 +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]]
971 971  
972 -**AT+5VT=1000**
973 973  
974 -Means set 5V valid time to have 1000ms. So, the real 5V output will actually have 1000ms + sampling time for other sensors.
1209 += 5. Use AT Command =
975 975  
1211 +== 5.1 Access AT Command ==
976 976  
977 -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.
1213 +(((
1214 +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.
1215 +)))
978 978  
1217 +[[image:1654162355560-817.png]]
979 979  
980 980  
1220 +(((
1221 +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:
1222 +)))
981 981  
982 -1.
983 -11. LEDs
1224 +[[image:1654162368066-342.png]]
984 984  
985 -|**LEDs**|**Feature**
986 -|**LED1**|Blink when device transmit a packet.
987 987  
988 -1.
989 -11. Switch Jumper
990 -
991 -|**Switch Jumper**|**Feature**
992 -|**SW1**|(((
993 -ISP position: Upgrade firmware via UART
994 -
995 -Flash position: Configure device, check running status.
1227 +(((
1228 +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/]]
996 996  )))
997 -|**SW2**|(((
998 -5V position: set to compatible with 5v I/O.
999 999  
1000 -3.3v position: set to compatible with 3.3v I/O.,
1001 -)))
1002 1002  
1003 -+3.3V: is always ON
1004 1004  
1005 -+5V: Only open before every sampling. The time is by default, it is AT+5VT=0.  Max open time. 5000 ms.
1233 +== 5.2 Common AT Command Sequence ==
1006 1006  
1007 -1. Case Study
1235 +=== 5.2.1 Multi-channel ABP mode (Use with SX1301/LG308) ===
1008 1008  
1009 -User can check this URL for some case studies.
1237 +If device has not joined network yet:
1010 1010  
1011 -[[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]]
1239 +(% class="box infomessage" %)
1240 +(((
1241 +**AT+FDR**
1242 +)))
1012 1012  
1244 +(% class="box infomessage" %)
1245 +(((
1246 +**AT+NJM=0**
1247 +)))
1013 1013  
1249 +(% class="box infomessage" %)
1250 +(((
1251 +**ATZ**
1252 +)))
1014 1014  
1015 1015  
1016 -1. Use AT Command
1017 -11. Access AT Command
1255 +If device already joined network:
1018 1018  
1019 -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.
1257 +(% class="box infomessage" %)
1258 +(((
1259 +**AT+NJM=0**
1260 +)))
1020 1020  
1021 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image027.png]]
1262 +(% class="box infomessage" %)
1263 +(((
1264 +**ATZ**
1265 +)))
1022 1022  
1023 1023  
1024 -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:
1268 +=== 5.5.2 Single-channel ABP mode (Use with LG01/LG02) ===
1025 1025  
1026 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image028.png]]
1027 1027  
1271 +(% style="background-color:#dcdcdc" %)**AT+FDR** (%%) Reset Parameters to Factory Default, Keys Reserve
1028 1028  
1273 +(% style="background-color:#dcdcdc" %)**AT+NJM=0 **(%%)Set to ABP mode
1029 1029  
1030 -More detail AT Command manual can be found at [[AT Command Manual>>path:#AT_COMMAND]]
1275 +(% style="background-color:#dcdcdc" %)**AT+ADR=0** (%%)Set the Adaptive Data Rate Off
1031 1031  
1277 +(% style="background-color:#dcdcdc" %)**AT+DR=5**   (%%)Set Data Rate
1032 1032  
1279 +(% style="background-color:#dcdcdc" %)**AT+TDC=60000** (%%) Set transmit interval to 60 seconds
1033 1033  
1034 -1.
1035 -11. Common AT Command Sequence
1036 -111. Multi-channel ABP mode (Use with SX1301/LG308)
1281 +(% style="background-color:#dcdcdc" %)**AT+CHS=868400000**(%%) Set transmit frequency to 868.4Mhz
1037 1037  
1038 -If device has not joined network yet:
1283 +(% style="background-color:#dcdcdc" %)**AT+RX2FQ=868400000** (%%) Set RX2Frequency to 868.4Mhz (according to the result from server)
1039 1039  
1040 -AT+FDR
1285 +(% style="background-color:#dcdcdc" %)**AT+RX2DR=5**  (%%) Set RX2DR to match the downlink DR from server. see below
1041 1041  
1042 -AT+NJM=0
1287 +(% 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.
1043 1043  
1044 -ATZ
1289 +(% style="background-color:#dcdcdc" %)**ATZ**       (%%) Reset MCU
1045 1045  
1046 1046  
1047 -If device already joined network:
1292 +(% style="color:red" %)**Note:**
1048 1048  
1049 -AT+NJM=0
1294 +(% style="color:red" %)1. Make sure the device is set to ABP mode in the IoT Server.
1295 +2. Make sure the LG01/02 gateway RX frequency is exactly the same as AT+CHS setting.
1296 +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.
1297 +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
1050 1050  
1051 -ATZ
1299 +[[image:1654162478620-421.png]]
1052 1052  
1053 -1.
1054 -11.
1055 -111. Single-channel ABP mode (Use with LG01/LG02)
1056 1056  
1057 -AT+FDR   Reset Parameters to Factory Default, Keys Reserve
1302 += 6. FAQ =
1058 1058  
1059 -AT+NJM=0 Set to ABP mode
1304 +== 6.1 How to upgrade the image? ==
1060 1060  
1061 -AT+ADR=0 Set the Adaptive Data Rate Off
1306 +(((
1307 +The RS485-LN LoRaWAN Controller is shipped with a 3.5mm cable, the cable is used to upload image to RS485-LN to:
1308 +)))
1062 1062  
1063 -AT+DR=5  Set Data Rate
1310 +* (((
1311 +Support new features
1312 +)))
1313 +* (((
1314 +For bug fix
1315 +)))
1316 +* (((
1317 +Change LoRaWAN bands.
1318 +)))
1064 1064  
1065 -AT+TDC=60000  Set transmit interval to 60 seconds
1320 +(((
1321 +Below shows the hardware connection for how to upload an image to RS485-LN:
1322 +)))
1066 1066  
1067 -AT+CHS=868400000 Set transmit frequency to 868.4Mhz
1324 +[[image:1654162535040-878.png]]
1068 1068  
1069 -AT+RX2FQ=868400000 Set RX2Frequency to 868.4Mhz (according to the result from server)
1326 +**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]].
1070 1070  
1071 -AT+RX2DR=5  Set RX2DR to match the downlink DR from server. see below
1328 +**Step2**: Download the [[LT Image files>>url:http://www.dragino.com/downloads/index.php?dir=LT_LoRa_IO_Controller/LT33222-L/image/]].
1072 1072  
1073 -AT+DADDR=26 01 1A F1 Set Device Address to 26 01 1A F1, this ID can be found in the LoRa Server portal.
1330 +**Step3: **Open flashloader; choose the correct COM port to update.
1074 1074  
1075 -ATZ          Reset MCU
1332 +(((
1333 +(((
1334 +(% 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.
1335 +)))
1336 +)))
1076 1076  
1077 -**Note:**
1078 1078  
1079 -1. Make sure the device is set to ABP mode in the IoT Server.
1080 -1. Make sure the LG01/02 gateway RX frequency is exactly the same as AT+CHS setting.
1081 -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.
1082 -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
1339 +[[image:image-20220602175818-12.png]]
1083 1083  
1084 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image029.png]]
1085 1085  
1342 +[[image:image-20220602175848-13.png]]
1086 1086  
1087 -1. FAQ
1088 -11. How to upgrade the image?
1089 1089  
1090 -The RS485-BL LoRaWAN Controller is shipped with a 3.5mm cable, the cable is used to upload image to RS485-BL to:
1345 +[[image:image-20220602175912-14.png]]
1091 1091  
1092 -* Support new features
1093 -* For bug fix
1094 -* Change LoRaWAN bands.
1095 1095  
1096 -Below shows the hardware connection for how to upload an image to RS485-BL:
1348 +**Notice**: In case user has lost the program cable. User can hand made one from a 3.5mm cable. The pin mapping is:
1097 1097  
1098 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image030.png]]
1350 +[[image:image-20220602175638-10.png]]
1099 1099  
1100 -**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]].
1101 1101  
1102 -**Step2**: Download the [[LT Image files>>url:http://www.dragino.com/downloads/index.php?dir=LT_LoRa_IO_Controller/LT33222-L/image/]].
1353 +== 6.2 How to change the LoRa Frequency Bands/Region? ==
1103 1103  
1104 -**Step3: **Open flashloader; choose the correct COM port to update.
1355 +User can follow the introduction for [[how to upgrade image>>||anchor="H6.1Howtoupgradetheimage3F"]]. When download the images, choose the required image file for download.
1105 1105  
1106 1106  
1107 -|(((
1108 -HOLD PRO then press the RST button, SYS will be ON, then click next
1109 -)))
1358 +== 6.3 How many RS485-Slave can RS485-BL connects? ==
1110 1110  
1111 -|(((
1112 -Board detected
1113 -)))
1360 +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"]].
1114 1114  
1115 -|(((
1116 -
1117 -)))
1118 1118  
1119 -[[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]]
1363 +== 6.4 Compatible question to ChirpStack and TTI LoRaWAN server ? ==
1120 1120  
1365 +When user need to use with ChirpStack or TTI. Please set AT+RPL=4.
1121 1121  
1367 +Detail info check this link: [[Set Packet Receiving Response Level>>doc:Main.End Device AT Commands and Downlink Command.WebHome||anchor="H7.23SetPacketReceivingResponseLevel"]]
1122 1122  
1123 -[[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]]
1124 1124  
1370 += 7. Trouble Shooting =
1125 1125  
1126 -[[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]]
1372 +== 7.1 Downlink doesn’t work, how to solve it? ==
1127 1127  
1374 +Please see this link for debug: [[LoRaWAN Communication Debug>>doc:Main.LoRaWAN Communication Debug.WebHome]]
1128 1128  
1129 -1.
1130 -11. How to change the LoRa Frequency Bands/Region?
1131 1131  
1132 -User can follow the introduction for [[how to upgrade image>>path:#upgrade_image]]. When download the images, choose the required image file for download.
1377 +== 7.2 Why I can’t join TTN V3 in US915 /AU915 bands? ==
1133 1133  
1379 +It might about the channels mapping. Please see for detail: [[Notice of Frequency band>>doc:Main.LoRaWAN Communication Debug.WebHome||anchor="H2.NoticeofUS9152FCN4702FAU915Frequencyband"]]
1134 1134  
1135 1135  
1136 -1.
1137 -11. How many RS485-Slave can RS485-BL connects?
1382 += 8. Order Info =
1138 1138  
1139 -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]].
1384 +(% style="color:blue" %)**Part Number: RS485-LN-XXX**
1140 1140  
1386 +(% style="color:blue" %)**XXX:**
1141 1141  
1388 +* (% style="color:blue" %)**EU433**(%%): frequency bands EU433
1389 +* (% style="color:blue" %)**EU868**(%%): frequency bands EU868
1390 +* (% style="color:blue" %)**KR920**(%%): frequency bands KR920
1391 +* (% style="color:blue" %)**CN470**(%%): frequency bands CN470
1392 +* (% style="color:blue" %)**AS923**(%%): frequency bands AS923
1393 +* (% style="color:blue" %)**AU915**(%%): frequency bands AU915
1394 +* (% style="color:blue" %)**US915**(%%): frequency bands US915
1395 +* (% style="color:blue" %)**IN865**(%%): frequency bands IN865
1396 +* (% style="color:blue" %)**RU864**(%%): frequency bands RU864
1397 +* (% style="color:blue" %)**KZ865**(%%): frequency bands KZ865
1142 1142  
1399 += 9.Packing Info =
1143 1143  
1144 -1. Trouble Shooting     
1145 -11. Downlink doesn’t work, how to solve it?
1146 1146  
1147 -Please see this link for debug:
1402 +**Package Includes**:
1148 1148  
1149 -[[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]] 
1404 +* RS485-LN x 1
1405 +* Stick Antenna for LoRa RF part x 1
1406 +* Program cable x 1
1150 1150  
1408 +**Dimension and weight**:
1151 1151  
1410 +* Device Size: 13.5 x 7 x 3 cm
1411 +* Device Weight: 105g
1412 +* Package Size / pcs : 14.5 x 8 x 5 cm
1413 +* Weight / pcs : 170g
1152 1152  
1153 -1.
1154 -11. Why I can’t join TTN V3 in US915 /AU915 bands?
1415 += 10. FCC Caution for RS485LN-US915 =
1155 1155  
1156 -It might about the channels mapping. Please see for detail.
1417 +(((
1418 +Any Changes or modifications not expressly approved by the party responsible for compliance could void the user's authority to operate the equipment.
1419 +)))
1157 1157  
1158 -[[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]]
1421 +(((
1422 +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.
1423 +)))
1159 1159  
1425 +(((
1426 +
1427 +)))
1160 1160  
1429 +(((
1430 +**IMPORTANT NOTE:**
1431 +)))
1161 1161  
1162 -1. Order Info
1433 +(((
1434 +**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:
1435 +)))
1163 1163  
1164 -**Part Number: RS485-BL-XXX**
1437 +(((
1438 +—Reorient or relocate the receiving antenna.
1439 +)))
1165 1165  
1166 -**XXX:**
1441 +(((
1442 +—Increase the separation between the equipment and receiver.
1443 +)))
1167 1167  
1168 -* **EU433**: frequency bands EU433
1169 -* **EU868**: frequency bands EU868
1170 -* **KR920**: frequency bands KR920
1171 -* **CN470**: frequency bands CN470
1172 -* **AS923**: frequency bands AS923
1173 -* **AU915**: frequency bands AU915
1174 -* **US915**: frequency bands US915
1175 -* **IN865**: frequency bands IN865
1176 -* **RU864**: frequency bands RU864
1177 -* **KZ865: **frequency bands KZ865
1445 +(((
1446 +—Connect the equipment into an outlet on a circuit different from that to which the receiver is connected.
1447 +)))
1178 1178  
1179 -1. Packing Info
1449 +(((
1450 +—Consult the dealer or an experienced radio/TV technician for help.
1451 +)))
1180 1180  
1181 -**Package Includes**:
1453 +(((
1454 +
1455 +)))
1182 1182  
1183 -* RS485-BL x 1
1184 -* Stick Antenna for LoRa RF part x 1
1185 -* Program cable x 1
1457 +(((
1458 +**FCC Radiation Exposure Statement:**
1459 +)))
1186 1186  
1187 -**Dimension and weight**:
1461 +(((
1462 +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.
1463 +)))
1188 1188  
1189 -* Device Size: 13.5 x 7 x 3 cm
1190 -* Device Weight: 105g
1191 -* Package Size / pcs : 14.5 x 8 x 5 cm
1192 -* Weight / pcs : 170g
1193 1193  
1194 -1. Support
1466 += 11. Support =
1195 1195  
1196 -* 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.
1197 -* 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
1198 -
1199 -[[support@dragino.com>>url:file:///D:/市场资料/说明书/LoRa/LT系列/support@dragino.com]]
1468 +* (((
1469 +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.
1470 +)))
1471 +* (((
1472 +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]].
1473 +)))
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
image-20220606110929-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +13.9 KB
Content