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, 2 removed)
Details
- Page properties
-
- Content
-
... ... @@ -6,18 +6,12 @@ 6 6 **RS485-LN – RS485 to LoRaWAN Converter User Manual** 7 7 8 8 9 - 10 - 11 11 **Table of Contents:** 12 12 13 -{{toc/}} 14 14 15 15 16 16 17 17 18 - 19 - 20 - 21 21 = 1.Introduction = 22 22 23 23 == 1.1 What is RS485-LN RS485 to LoRaWAN Converter == ... ... @@ -80,9 +80,8 @@ 80 80 * Preamble detection. 81 81 * 127 dB Dynamic Range RSSI. 82 82 * Automatic RF Sense and CAD with ultra-fast AFC. 83 -* Packet engine up to 256 bytes with CRC 77 +* Packet engine up to 256 bytes with CRC. 84 84 85 - 86 86 == 1.3 Features == 87 87 88 88 * LoRaWAN Class A & Class C protocol (default Class C) ... ... @@ -94,7 +94,6 @@ 94 94 * Support Modbus protocol 95 95 * Support Interrupt uplink (Since hardware version v1.2) 96 96 97 - 98 98 == 1.4 Applications == 99 99 100 100 * Smart Buildings & Home Automation ... ... @@ -104,7 +104,6 @@ 104 104 * Smart Cities 105 105 * Smart Factory 106 106 107 - 108 108 == 1.5 Firmware Change log == 109 109 110 110 [[RS485-LN Image files – Download link and Change log>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/]] ... ... @@ -168,7 +168,7 @@ 168 168 [[image:1653268227651-549.png||height="592" width="720"]] 169 169 170 170 ((( 171 -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:162 +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: 172 172 ))) 173 173 174 174 ((( ... ... @@ -220,7 +220,7 @@ 220 220 221 221 ((( 222 222 ((( 223 -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.214 +There are plenty of RS485 devices in the market and each device has different command to read the valid data. To support these devices in flexible, RS485-LN supports flexible command set. User can use [[AT Commands>>path:#AT_COMMAND]] or LoRaWAN Downlink Command to configure what commands RS485-LN should send for each sampling and how to handle the return from RS485 devices. 224 224 ))) 225 225 226 226 ((( ... ... @@ -292,8 +292,6 @@ 292 292 ))) 293 293 ))) 294 294 295 - 296 - 297 297 === 3.3.2 Configure sensors === 298 298 299 299 ((( ... ... @@ -312,8 +312,6 @@ 312 312 mm: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command 313 313 )))|(% style="width:256px" %)AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m 314 314 315 - 316 - 317 317 === 3.3.3 Configure read commands for each sampling === 318 318 319 319 ((( ... ... @@ -429,7 +429,6 @@ 429 429 430 430 (% style="color:#4f81bd" %)**Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA** 431 431 432 - 433 433 1. PAYVER: Defined by AT+PAYVER 434 434 1. PAYLOAD COUNT: Total how many uplinks of this sampling. 435 435 1. PAYLOAD#: Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT) ... ... @@ -529,8 +529,8 @@ 529 529 530 530 === 3.5.3 Sensor related commands === 531 531 518 +==== ==== 532 532 533 - 534 534 ==== **RS485 Debug Command** ==== 535 535 536 536 This command is used to configure the RS485 devices; they won’t be used during sampling. ... ... @@ -745,6 +745,7 @@ 745 745 **0x08 FF**, RS485-LN will immediately send an uplink. 746 746 747 747 734 +==== ==== 748 748 749 749 ==== **Clear RS485 Command** ==== 750 750 ... ... @@ -862,7 +862,6 @@ 862 862 |**RST**|(% style="width:1420px" %)Reboot RS485 863 863 |**PRO**|(% style="width:1420px" %)Use for upload image, see [[How to Update Image>>path:#upgrade_image]] 864 864 865 - 866 866 == 3.8 LEDs == 867 867 868 868 (% border="1" style="background-color:#f7faff; width:500px" %) ... ... @@ -870,7 +870,6 @@ 870 870 |**PWR**|Always on if there is power 871 871 |**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. 872 872 873 - 874 874 = 4. Case Study = 875 875 876 876 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]] ... ... @@ -984,16 +984,14 @@ 984 984 985 985 (% 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. 986 986 972 +[[image:image-20220602102605-1.png]] 987 987 988 -[[image:image-20220602175818-12.png]] 989 989 975 +[[image:image-20220602102637-2.png]] 990 990 991 -[[image:image-20220602175848-13.png]] 992 992 978 +[[image:image-20220602102715-3.png]] 993 993 994 -[[image:image-20220602175912-14.png]] 995 - 996 - 997 997 **Notice**: In case user has lost the program cable. User can hand made one from a 3.5mm cable. The pin mapping is: 998 998 999 999 [[image:image-20220602175638-10.png]] ... ... @@ -1045,7 +1045,6 @@ 1045 1045 * (% style="color:blue" %)**RU864**(%%): frequency bands RU864 1046 1046 * (% style="color:blue" %)**KZ865**(%%): frequency bands KZ865 1047 1047 1048 - 1049 1049 = 9.Packing Info = 1050 1050 1051 1051 ... ... @@ -1062,7 +1062,6 @@ 1062 1062 * Package Size / pcs : 14.5 x 8 x 5 cm 1063 1063 * Weight / pcs : 170g 1064 1064 1065 - 1066 1066 = 10. FCC Caution for RS485LN-US915 = 1067 1067 1068 1068 Any Changes or modifications not expressly approved by the party responsible for compliance could void the user's authority to operate the equipment.
- image-20220602175848-13.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -250.9 KB - Content
- image-20220602175912-14.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -176.1 KB - Content