Changes for page RS485-LN – RS485 to LoRaWAN Converter User Manual
Last modified by Karry Zhuang on 2025/03/06 16:34
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 1 removed)
Details
- Page properties
-
- Content
-
... ... @@ -18,30 +18,26 @@ 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,6 +48,8 @@ 48 48 * 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:** ... ... @@ -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 ... ... @@ -132,8 +132,6 @@ 132 132 ))) 133 133 134 134 [[image:1653268091319-405.png]] 135 - 136 - 137 137 ))) 138 138 139 139 = 3. Operation Mode = ... ... @@ -490,37 +490,41 @@ 490 490 491 491 [[image:1653269759169-150.png||height="513" width="716"]] 492 492 493 -(% style="color:#4f81bd" %)**Examples: AT+DATAUP=1** 494 494 495 -Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**Multiply UPLINKs**. 496 496 482 +**Examples: AT+DATAUP=1** 483 + 484 +Compose the uplink payload with value returns in sequence and send with **Multiply UPLINKs**. 485 + 497 497 Final Payload is 498 498 499 - (% style="color:#4f81bd" %)**Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA**488 +Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA 500 500 501 501 1. Battery Info (2 bytes): Battery voltage 502 502 1. PAYVER (1 byte): Defined by AT+PAYVER 503 503 1. PAYLOAD COUNT (1 byte): Total how many uplinks of this sampling. 504 504 1. PAYLOAD# (1 byte): Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT) 505 -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 494 +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 506 506 507 -[[image: 1653269916228-732.png||height="433" width="711"]]496 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image020.png]] 508 508 509 509 510 510 So totally there will be 3 uplinks for this sampling, each uplink includes 6 bytes DATA 511 511 512 -DATA1=RETURN1 Valid Value = (% style="background-color:green; color:white" %)20 20 0a 33 90 41501 +DATA1=RETURN1 Valid Value = 20 20 0a 33 90 41 513 513 514 -DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10= (%style="background-color:green; color:white" %)02 aa 05 81 0a 20503 +DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10= 02 aa 05 81 0a 20 515 515 516 -DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 = (%style="background-color:green; color:white" %)20 20 20 2d 30505 +DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 = 20 20 20 2d 30 517 517 507 + 508 + 518 518 Below are the uplink payloads: 519 519 520 -[[image: 1653270130359-810.png]]511 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image021.png]] 521 521 522 522 523 - (% style="color:red" %)**Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:**514 +Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below: 524 524 525 525 ~* For AU915/AS923 bands, if UplinkDwell time=0, max 51 bytes for each uplink ( so 51 -5 = 46 max valid date) 526 526 ... ... @@ -530,8 +530,12 @@ 530 530 531 531 ~* For all other bands: max 51 bytes for each uplink ( so 51 -5 = 46 max valid date). 532 532 533 -=== 3.3.5 Uplink on demand === 534 534 525 + 526 +1. 527 +11. 528 +111. Uplink on demand 529 + 535 535 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. 536 536 537 537 Downlink control command:
- 1653270130359-810.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -197.8 KB - Content