Last modified by Karry Zhuang on 2025/03/06 16:34
<
From version < 32.10 >
edited by Xiaoling
on 2022/06/02 15:26
To version < 22.3 >
edited by Xiaoling
on 2022/05/23 09:12
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -18,42 +18,40 @@
18 18  
19 19  (((
20 20  (((
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.
21 +The Dragino RS485-LN is a 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  )))
23 23  
24 24  (((
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.
25 +RS485-LN allows user to 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  )))
27 27  
28 28  (((
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.
29 +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  )))
31 31  
32 32  (((
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.
34 -
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]]
33 +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.
36 36  )))
37 37  )))
38 38  
39 39  [[image:1653267211009-519.png||height="419" width="724"]]
40 40  
41 -
42 42  == 1.2 Specifications ==
43 43  
44 -
45 45  **Hardware System:**
46 46  
47 47  * STM32L072CZT6 MCU
48 -* SX1276/78 Wireless Chip 
44 +* SX1276/78 Wireless Chip
49 49  * Power Consumption (exclude RS485 device):
50 50  ** Idle: 32mA@12v
47 +
48 +*
51 51  ** 20dB Transmit: 65mA@12v
52 52  
53 53  **Interface for Model:**
54 54  
55 55  * RS485
56 -* Power Input 7~~ 24V DC. 
54 +* Power Input 7~~ 24V DC.
57 57  
58 58  **LoRa Spec:**
59 59  
... ... @@ -76,8 +76,6 @@
76 76  * Automatic RF Sense and CAD with ultra-fast AFC.
77 77  * 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,13 +100,10 @@
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/]]
108 108  
109 -
110 110  == 1.6 Hardware Change log ==
111 111  
112 112  (((
... ... @@ -114,8 +114,6 @@
114 114  v1.2: Add External Interrupt Pin.
115 115  
116 116  v1.0: Release
117 -
118 -
119 119  )))
120 120  )))
121 121  
... ... @@ -198,7 +198,7 @@
198 198  
199 199  
200 200  (((
201 -**Step 2**: Power on RS485-LN and it will auto join to the TTN V3 network. After join success, it will start to upload message to TTN V3 and user can see in the panel.
190 +**Step 2**: Power on RS485-BL and it will auto join to the TTN V3 network. After join success, it will start to upload message to TTN V3 and user can see in the panel.
202 202  )))
203 203  
204 204  [[image:1652953568895-172.png||height="232" width="724"]]
... ... @@ -206,19 +206,23 @@
206 206  == 3.3 Configure Commands to read data ==
207 207  
208 208  (((
209 -(((
210 -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.
198 +There are plenty of RS485 and TTL level devices in the market and each device has different command to read the valid data. To support these devices in flexible, RS485-BL supports flexible command set. User can use [[AT Commands or LoRaWAN Downlink>>path:#AT_COMMAND]] Command to configure how RS485-BL should read the sensor and how to handle the return from RS485 or TTL sensors.
211 211  )))
212 212  
213 -(((
214 -(% 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
215 -)))
216 -)))
217 -
218 218  === 3.3.1 onfigure UART settings for RS485 or TTL communication ===
219 219  
220 -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:
203 +RS485-BL can connect to either RS485 sensors or TTL sensor. User need to specify what type of sensor need to connect.
221 221  
205 +**~1. RS485-MODBUS mode:**
206 +
207 +AT+MOD=1 ~/~/ Support RS485-MODBUS type sensors. User can connect multiply RS485 , Modbus sensors to the A / B pins.
208 +
209 +**2. TTL mode:**
210 +
211 +AT+MOD=2 ~/~/ Support TTL Level sensors, User can connect one TTL Sensor to the TXD/RXD/GND pins.
212 +
213 +RS485-BL default UART settings is **9600, no parity, stop bit 1**. If the sensor has a different settings, user can change the RS485-BL setting to match.
214 +
222 222  (% border="1" style="background-color:#ffffcc; color:green; width:795px" %)
223 223  |(((
224 224  **AT Commands**
... ... @@ -243,7 +243,13 @@
243 243  |(((
244 244  AT+PARITY
245 245  )))|(% style="width:285px" %)(((
239 +(((
246 246  Set UART parity (for RS485 connection)
241 +)))
242 +
243 +(((
244 +Default Value is: no parity.
245 +)))
247 247  )))|(% style="width:347px" %)(((
248 248  (((
249 249  AT+PARITY=0
... ... @@ -261,7 +261,7 @@
261 261  )))
262 262  
263 263  (((
264 -
263 +Default Value is: 1bit.
265 265  )))
266 266  )))|(% style="width:347px" %)(((
267 267  (((
... ... @@ -280,10 +280,12 @@
280 280  === 3.3.2 Configure sensors ===
281 281  
282 282  (((
282 +Some sensors might need to configure before normal operation. User can configure such sensor via PC or through RS485-BL AT Commands (% style="color:#4f81bd" %)**AT+CFGDEV**.
283 +)))
284 +
283 283  (((
284 -Some sensors might need to configure before normal operation. User can configure such sensor via PC and RS485 adapter or through RS485-LN AT Commands (% style="color:#4f81bd" %)**AT+CFGDEV**(%%). Each (% style="color:#4f81bd" %)**AT+CFGDEV **(%%)equals to send a RS485 command to sensors. This command will only run when user input it and won’t run during each sampling.
286 +When user issue an (% style="color:#4f81bd" %)**AT+CFGDEV**(%%) command, Each (% style="color:#4f81bd" %)**AT+CFGDEV**(%%) equals to send a command to the RS485 or TTL sensors. This command will only run when user input it and won’t run during each sampling.
285 285  )))
286 -)))
287 287  
288 288  (% border="1" style="background-color:#ffffcc; color:green; width:806px" %)
289 289  |**AT Commands**|(% style="width:418px" %)**Description**|(% style="width:256px" %)**Example**
... ... @@ -295,6 +295,8 @@
295 295  mm: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
296 296  )))|(% style="width:256px" %)AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
297 297  
299 +Detail of AT+CFGDEV command see [[AT+CFGDEV detail>>path:#AT_CFGDEV]].
300 +
298 298  === 3.3.3 Configure read commands for each sampling ===
299 299  
300 300  (((
... ... @@ -376,17 +376,11 @@
376 376  **m: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command**
377 377  )))
378 378  
379 -(((
380 380  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.
381 -)))
382 382  
383 -(((
384 384  In the RS485-BL, we should use this command AT+COMMAND1=01 03 0B B8 00 02,1 for the same.
385 -)))
386 386  
387 -(((
388 388  **AT+SEARCHx**: This command defines how to handle the return from AT+COMMANDx.
389 -)))
390 390  
391 391  (% border="1" class="table-bordered" %)
392 392  |(((
... ... @@ -398,24 +398,26 @@
398 398  
399 399  )))
400 400  
401 -**Examples:**
398 +Examples:
402 402  
403 -~1. For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
400 +1. For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
404 404  
405 405  If we set AT+SEARCH1=1,1E 56 34.      (max 5 bytes for prefix)
406 406  
407 -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**
404 +The valid data will be all bytes after 1E 56 34 , so it is 2e 30 58 5f 36 41 30 31 00 49
408 408  
409 -[[image:1653269403619-508.png]]
406 +[[image:1652954654347-831.png]]
410 410  
411 -2. For a return string from AT+COMMAND1:  16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
412 412  
409 +1. For a return string from AT+COMMAND1:  16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
410 +
413 413  If we set AT+SEARCH1=2, 1E 56 34+31 00 49
414 414  
415 -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**
413 +Device will search the bytes between 1E 56 34 and 31 00 49. So it is 2e 30 58 5f 36 41 30
416 416  
417 -[[image:1653269438444-278.png]]
415 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image014.png]]
418 418  
417 +
419 419  **AT+DATACUTx : **This command defines how to handle the return from AT+COMMANDx, max return length is 45 bytes.
420 420  
421 421  |(((
... ... @@ -430,95 +430,94 @@
430 430  
431 431  * Grab bytes:
432 432  
433 -[[image:1653269551753-223.png||height="311" width="717"]]
432 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image015.png]]
434 434  
435 435  * Grab a section.
436 436  
437 -[[image:1653269568276-930.png||height="325" width="718"]]
436 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image016.png]]
438 438  
439 439  * Grab different sections.
440 440  
441 -[[image:1653269593172-426.png||height="303" width="725"]]
440 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image017.png]]
442 442  
443 -(% style="color:red" %)**Note:**
444 444  
443 +Note:
444 +
445 445  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.
446 446  
447 447  Example:
448 448  
449 -(% style="color:red" %)AT+COMMAND1=11 01 1E D0,0
449 +AT+COMMAND1=11 01 1E D0,0
450 450  
451 -(% style="color:red" %)AT+SEARCH1=1,1E 56 34
451 +AT+SEARCH1=1,1E 56 34
452 452  
453 -(% style="color:red" %)AT+DATACUT1=0,2,1~~5
453 +AT+DATACUT1=0,2,1~~5
454 454  
455 -(% style="color:red" %)Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
455 +Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
456 456  
457 -(% style="color:red" %)String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49
457 +String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49
458 458  
459 -(% style="color:red" %)Valid payload after DataCUT command: 2e 30 58 5f 36
459 +Valid payload after DataCUT command: 2e 30 58 5f 36
460 460  
461 -[[image:1653269618463-608.png]]
461 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image018.png]]
462 462  
463 -=== 3.3.4 Compose the uplink payload ===
464 464  
465 -(((
464 +
465 +
466 +1.
467 +11.
468 +111. Compose the uplink payload
469 +
466 466  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.**
467 -)))
468 468  
469 -(((
470 -(% style="color:#4f81bd" %)**Examples: AT+DATAUP=0**
471 -)))
472 472  
473 -(((
474 -Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**A SIGNLE UPLINK**.
475 -)))
473 +**Examples: AT+DATAUP=0**
476 476  
477 -(((
475 +Compose the uplink payload with value returns in sequence and send with **A SIGNLE UPLINK**.
476 +
478 478  Final Payload is
479 -)))
480 480  
481 -(((
482 -(% style="color:#4f81bd" %)**Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx**
483 -)))
479 +Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx
484 484  
485 -(((
486 486  Where PAYVER is defined by AT+PAYVER, below is an example screen shot.
487 -)))
488 488  
489 -[[image:1653269759169-150.png||height="513" width="716"]]
483 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image019.png]]
490 490  
491 -(% style="color:#4f81bd" %)**Examples: AT+DATAUP=1**
492 492  
493 -Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**Multiply UPLINKs**.
494 494  
487 +**Examples: AT+DATAUP=1**
488 +
489 +Compose the uplink payload with value returns in sequence and send with **Multiply UPLINKs**.
490 +
495 495  Final Payload is
496 496  
497 -(% style="color:#4f81bd" %)**Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA**
493 +Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA
498 498  
499 499  1. Battery Info (2 bytes): Battery voltage
500 500  1. PAYVER (1 byte): Defined by AT+PAYVER
501 501  1. PAYLOAD COUNT (1 byte): Total how many uplinks of this sampling.
502 502  1. PAYLOAD# (1 byte): Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT)
503 -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
499 +1. DATA: Valid value: max 6 bytes(US915 version here, [[Notice*!>>path:#max_byte]]) for each uplink so each uplink <= 11 bytes. For the last uplink, DATA will might less than 6 bytes
504 504  
505 -[[image:1653269916228-732.png||height="433" width="711"]]
501 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image020.png]]
506 506  
507 507  
508 508  So totally there will be 3 uplinks for this sampling, each uplink includes 6 bytes DATA
509 509  
510 -DATA1=RETURN1 Valid Value = (% style="background-color:green; color:white" %)20 20 0a 33 90 41
506 +DATA1=RETURN1 Valid Value = 20 20 0a 33 90 41
511 511  
512 -DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10=(% style="background-color:green; color:white" %) 02 aa 05 81 0a 20
508 +DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10= 02 aa 05 81 0a 20
513 513  
514 -DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 = (% style="background-color:green; color:white" %)20 20 20 2d 30
510 +DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 = 20 20 20 2d 30
515 515  
512 +
513 +
516 516  Below are the uplink payloads:
517 517  
518 -[[image:1653270130359-810.png]]
516 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image021.png]]
519 519  
520 520  
521 -(% style="color:red" %)**Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:**
519 +Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:
522 522  
523 523   ~* For AU915/AS923 bands, if UplinkDwell time=0, max 51 bytes for each uplink ( so 51 -5 = 46 max valid date)
524 524  
... ... @@ -528,8 +528,12 @@
528 528  
529 529   ~* For all other bands: max 51 bytes for each uplink  ( so 51 -5 = 46 max valid date).
530 530  
531 -=== 3.3.5 Uplink on demand ===
532 532  
530 +
531 +1.
532 +11.
533 +111. Uplink on demand
534 +
533 533  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.
534 534  
535 535  Downlink control command:
1653269403619-508.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -27.8 KB
Content
1653269438444-278.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -26.6 KB
Content
1653269551753-223.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -138.7 KB
Content
1653269568276-930.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -131.4 KB
Content
1653269593172-426.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -142.6 KB
Content
1653269618463-608.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -27.7 KB
Content
1653269759169-150.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -294.0 KB
Content
1653269916228-732.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -143.3 KB
Content
1653270130359-810.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -197.8 KB
Content

Applications

Navigation

Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0