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