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 (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 8 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -RS485- BL –WaterproofRS485 to LoRaWAN Converter1 +RS485-LN – RS485 to LoRaWAN Converter - Content
-
... ... @@ -1,12 +1,11 @@ 1 1 (% style="text-align:center" %) 2 -[[image:165294 7681187-144.png||height="385" width="385"]]2 +[[image:1653266934636-343.png||height="385" width="385"]] 3 3 4 4 5 5 6 +**RS485-LN – RS485 to LoRaWAN Converter User Manual** 6 6 7 -**RS485-BL – Waterproof RS485 to LoRaWAN Converter User Manual** 8 8 9 - 10 10 **Table of Contents:** 11 11 12 12 ... ... @@ -15,42 +15,28 @@ 15 15 16 16 = 1.Introduction = 17 17 18 -== 1.1 What is RS485- BL RS485 to LoRaWAN Converter ==17 +== 1.1 What is RS485-LN RS485 to LoRaWAN Converter == 19 19 20 20 ((( 21 - 22 -))) 23 - 24 24 ((( 25 -The Dragino RS485- BL is a**RS485/ UARTto LoRaWAN Converter**forInternetof Things solutions.Usercan connectRS485or UARTsensortoRS485-BLconverter,andconfigureRS485-BLtoperiodicallyreadsensor dataand upload via LoRaWANnetworktoIoTserver.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. 26 26 ))) 27 27 28 28 ((( 29 -RS485- BLcaninterfaceto RS485sensor,3.3v/5vUARTsensor orinterruptsensor.RS485-BLprovides**a 3.3v output**and**a5voutput** topowerexternal sensors.Bothoutputvoltages arecontrollabletominimizethe totalsystempowerconsumption.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. 30 30 ))) 31 31 32 32 ((( 33 -RS485- BLisIP67 **waterproof**andpoweredby **8500mAhLi-SOCI2battery**,itisdesignedforlong termuseforseveral years.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. 34 34 ))) 35 35 36 36 ((( 37 -RS485- BL runsstandard**LoRaWAN1.0.3 inClassA**.It can reachlong transferrange andeasytointegrate withLoRaWANcompatiblegatewayandIoTserver.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. 38 38 ))) 39 - 40 -((( 41 -For data uplink, RS485-BL sends user-defined commands to RS485 devices and gets the return from the RS485 devices. RS485-BL will process these returns data according to user-define rules to get the final payload and upload to LoRaWAN server. 42 42 ))) 43 43 44 -((( 45 -For data downlink, RS485-BL runs in LoRaWAN Class A. When there is downlink commands from LoRaWAN server, RS485-BL will forward the commands from LoRaWAN server to RS485 devices. 46 -))) 37 +[[image:1653267211009-519.png||height="419" width="724"]] 47 47 48 -((( 49 -Each RS485-BL pre-load with a set of unique keys for LoRaWAN registration, register these keys to LoRaWAN server and it will auto connect after power on. 50 -))) 51 - 52 -[[image:1652953304999-717.png||height="424" width="733"]] 53 - 54 54 == 1.2 Specifications == 55 55 56 56 **Hardware System:** ... ... @@ -58,19 +58,15 @@ 58 58 * STM32L072CZT6 MCU 59 59 * SX1276/78 Wireless Chip 60 60 * Power Consumption (exclude RS485 device): 61 -** Idle: 6uA@3.3v46 +** Idle: 32mA@12v 62 62 63 63 * 64 -** 20dB Transmit: 130mA@3.3v49 +** 20dB Transmit: 65mA@12v 65 65 66 66 **Interface for Model:** 67 67 68 -* 1 x RS485 Interface 69 -* 1 x TTL Serial , 3.3v or 5v. 70 -* 1 x I2C Interface, 3.3v or 5v. 71 -* 1 x one wire interface 72 -* 1 x Interrupt Interface 73 -* 1 x Controllable 5V output, max 53 +* RS485 54 +* Power Input 7~~ 24V DC. 74 74 75 75 **LoRa Spec:** 76 76 ... ... @@ -79,27 +79,30 @@ 79 79 ** Band 2 (LF): 410 ~~ 528 Mhz 80 80 * 168 dB maximum link budget. 81 81 * +20 dBm - 100 mW constant RF output vs. 63 +* +14 dBm high efficiency PA. 82 82 * Programmable bit rate up to 300 kbps. 83 83 * High sensitivity: down to -148 dBm. 84 84 * Bullet-proof front end: IIP3 = -12.5 dBm. 85 85 * Excellent blocking immunity. 68 +* Low RX current of 10.3 mA, 200 nA register retention. 86 86 * Fully integrated synthesizer with a resolution of 61 Hz. 87 -* LoRa modulation. 70 +* FSK, GFSK, MSK, GMSK, LoRaTM and OOK modulation. 88 88 * Built-in bit synchronizer for clock recovery. 89 89 * Preamble detection. 90 90 * 127 dB Dynamic Range RSSI. 91 -* Automatic RF Sense and CAD with ultra-fast AFC. 74 +* Automatic RF Sense and CAD with ultra-fast AFC. 75 +* Packet engine up to 256 bytes with CRC. 92 92 93 93 == 1.3 Features == 94 94 95 -* LoRaWAN Class A & Class C protocol (default Class A)79 +* LoRaWAN Class A & Class C protocol (default Class C) 96 96 * Frequency Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915/IN865/RU864 97 97 * AT Commands to change parameters 98 -* Remote configure parameters via LoRa WANDownlink82 +* Remote configure parameters via LoRa Downlink 99 99 * Firmware upgradable via program port 100 100 * Support multiply RS485 devices by flexible rules 101 101 * Support Modbus protocol 102 -* Support Interrupt uplink 86 +* Support Interrupt uplink (Since hardware version v1.2) 103 103 104 104 == 1.4 Applications == 105 105 ... ... @@ -112,53 +112,39 @@ 112 112 113 113 == 1.5 Firmware Change log == 114 114 115 -[[RS485- BL Image files – Download link and Change log>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/RS485-BL/Firmware/||style="background-color: rgb(255, 255, 255);"]]99 +[[RS485-LN Image files – Download link and Change log>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/]] 116 116 117 117 == 1.6 Hardware Change log == 118 118 119 119 ((( 120 -v1.4 121 -))) 122 - 123 123 ((( 124 -~1. Change Power IC to TPS22916 125 -))) 105 +v1.2: Add External Interrupt Pin. 126 126 127 - 128 -((( 129 -v1.3 107 +v1.0: Release 130 130 ))) 131 - 132 -((( 133 -~1. Change JP3 from KF350-8P to KF350-11P, Add one extra interface for I2C and one extra interface for one-wire 134 134 ))) 135 135 111 += 2. Power ON Device = 136 136 137 137 ((( 138 -v1.2 139 -))) 114 +The RS485-LN can be powered by 7 ~~ 24V DC power source. Connection as below 140 140 116 +* Power Source VIN to RS485-LN VIN+ 117 +* Power Source GND to RS485-LN VIN- 118 + 141 141 ((( 142 - Releaseversion120 +Once there is power, the RS485-LN will be on. 143 143 ))) 144 144 145 -= 2. Pin mapping and Power ON Device = 146 - 147 -((( 148 -The RS485-BL is powered on by 8500mAh battery. To save battery life, RS485-BL is shipped with power off. User can put the jumper to power on RS485-BL. 123 +[[image:1653268091319-405.png]] 149 149 ))) 150 150 151 -[[image:1652953055962-143.png||height="387" width="728"]] 152 - 153 - 154 -The Left TXD and RXD are TTL interface for external sensor. TTL level is controlled by 3.3/5v Jumper. 155 - 156 156 = 3. Operation Mode = 157 157 158 158 == 3.1 How it works? == 159 159 160 160 ((( 161 -The RS485- BL is configured as LoRaWAN OTAA ClassAmode 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-BL. It will auto join the network via OTAA.131 +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. 162 162 ))) 163 163 164 164 == 3.2 Example to join LoRaWAN network == ... ... @@ -165,27 +165,32 @@ 165 165 166 166 Here shows an example for how to join the TTN V3 Network. Below is the network structure, we use [[LG308>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/140-lg308.html]] as LoRaWAN gateway here. 167 167 168 -[[image:1652 953414711-647.png||height="337" width="723"]]138 +[[image:1653268155545-638.png||height="334" width="724"]] 169 169 170 170 ((( 171 -The RS485-BL in this example connected to two RS485 devices for demonstration, user can connect to other RS485 devices via the same method. 172 -))) 141 +The RS485-LN in this example connected to two RS485 devices for demonstration, user can connect to other RS485 devices via the same method. The connection is as below: 173 173 143 +485A+ and 485B- of the sensor are connected to RS485A and RA485B of RS485-LN respectively. 144 + 145 +[[image:1653268227651-549.png||height="592" width="720"]] 146 + 174 174 ((( 175 -The LG308 is already set to connect to [[TTN V3 network >> url:https://www.thethingsnetwork.org/]]. So what we need to now is only configure the TTN V3:148 +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: 176 176 ))) 177 177 178 178 ((( 179 -**Step 1**: Create a device in TTN V3 with the OTAA keys from RS485- BL.152 +**Step 1**: Create a device in TTN V3 with the OTAA keys from RS485-LN. 180 180 ))) 181 181 182 182 ((( 183 -Each RS485- BL is shipped with a sticker with unique device EUI:156 +Each RS485-LN is shipped with a sticker with unique device EUI: 184 184 ))) 158 +))) 185 185 186 186 [[image:1652953462722-299.png]] 187 187 188 188 ((( 163 +((( 189 189 User can enter this key in their LoRaWAN Server portal. Below is TTN V3 screen shot: 190 190 ))) 191 191 ... ... @@ -192,13 +192,11 @@ 192 192 ((( 193 193 Add APP EUI in the application. 194 194 ))) 170 +))) 195 195 196 - 197 - 198 - 199 199 [[image:image-20220519174512-1.png]] 200 200 201 -[[image:image-20220519174512-2.png||height="32 8" width="731"]]174 +[[image:image-20220519174512-2.png||height="323" width="720"]] 202 202 203 203 [[image:image-20220519174512-3.png||height="556" width="724"]] 204 204 ... ... @@ -214,7 +214,7 @@ 214 214 215 215 216 216 ((( 217 -**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.190 +**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. 218 218 ))) 219 219 220 220 [[image:1652953568895-172.png||height="232" width="724"]] ... ... @@ -222,23 +222,19 @@ 222 222 == 3.3 Configure Commands to read data == 223 223 224 224 ((( 225 -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. 198 +((( 199 +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. 226 226 ))) 227 227 202 +((( 203 +(% 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 204 +))) 205 +))) 206 + 228 228 === 3.3.1 onfigure UART settings for RS485 or TTL communication === 229 229 230 -RS485- BLcan connect to eitherRS485sensorsorTTLsensor.User need to specifywhattype ofsensorneedtoconnect.209 +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: 231 231 232 -**~1. RS485-MODBUS mode:** 233 - 234 -AT+MOD=1 ~/~/ Support RS485-MODBUS type sensors. User can connect multiply RS485 , Modbus sensors to the A / B pins. 235 - 236 -**2. TTL mode:** 237 - 238 -AT+MOD=2 ~/~/ Support TTL Level sensors, User can connect one TTL Sensor to the TXD/RXD/GND pins. 239 - 240 -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. 241 - 242 242 (% border="1" style="background-color:#ffffcc; color:green; width:795px" %) 243 243 |((( 244 244 **AT Commands** ... ... @@ -263,13 +263,7 @@ 263 263 |((( 264 264 AT+PARITY 265 265 )))|(% style="width:285px" %)((( 266 -((( 267 267 Set UART parity (for RS485 connection) 268 -))) 269 - 270 -((( 271 -Default Value is: no parity. 272 -))) 273 273 )))|(% style="width:347px" %)((( 274 274 ((( 275 275 AT+PARITY=0 ... ... @@ -287,7 +287,7 @@ 287 287 ))) 288 288 289 289 ((( 290 - DefaultValue is: 1bit.253 + 291 291 ))) 292 292 )))|(% style="width:347px" %)((( 293 293 ((( ... ... @@ -303,87 +303,97 @@ 303 303 ))) 304 304 ))) 305 305 269 +=== 3.3.2 Configure sensors === 306 306 271 +((( 272 +((( 273 +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. 274 +))) 275 +))) 307 307 308 - 309 -1. 310 -11. 311 -111. Configure sensors 312 - 313 -Some sensors might need to configure before normal operation. User can configure such sensor via PC or through RS485-BL AT Commands AT+CFGDEV. 314 - 315 - 316 -When user issue an AT+CFGDEV command, Each 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. 317 - 318 -|**AT Commands**|**Description**|**Example** 319 -|AT+CFGDEV|((( 277 +(% border="1" style="background-color:#ffffcc; color:green; width:806px" %) 278 +|**AT Commands**|(% style="width:418px" %)**Description**|(% style="width:256px" %)**Example** 279 +|AT+CFGDEV|(% style="width:418px" %)((( 320 320 This command is used to configure the RS485/TTL devices; they won’t be used during sampling. 321 321 322 -AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx, m282 +AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx, 323 323 324 -m: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command 325 -)))|AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m 284 +mm: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command 285 +)))|(% style="width:256px" %)AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m 326 326 327 - DetailofAT+CFGDEVcommandee[[AT+CFGDEVdetail>>path:#AT_CFGDEV]].287 +=== 3.3.3 Configure read commands for each sampling === 328 328 329 - 330 - 331 - 332 - 333 -1. 334 -11. 335 -111. Configure read commands for each sampling 336 - 289 +((( 337 337 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. 291 +))) 338 338 339 - 293 +((( 340 340 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. 295 +))) 341 341 342 - 297 +((( 343 343 To save the LoRaWAN network bandwidth, we might need to read data from different sensors and combine their valid value into a short payload. 299 +))) 344 344 345 - 301 +((( 346 346 This section describes how to achieve above goals. 303 +))) 347 347 348 - 305 +((( 349 349 During each sampling, the RS485-BL can support 15 commands to read sensors. And combine the return to one or several uplink payloads. 307 +))) 350 350 351 - 309 +((( 352 352 **Command from RS485-BL to Sensor:** 311 +))) 353 353 313 +((( 354 354 RS485-BL can send out pre-set max 15 strings via **AT+COMMAD1**, **ATCOMMAND2**,…, to **AT+COMMANDF** . All commands are of same grammar. 315 +))) 355 355 356 - 317 +((( 357 357 **Handle return from sensors to RS485-BL**: 319 +))) 358 358 321 +((( 359 359 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** 323 +))) 360 360 325 +* ((( 326 +**AT+DATACUT** 327 +))) 361 361 362 -* **AT+DATACUT** 363 - 329 +((( 364 364 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. 331 +))) 365 365 333 +* ((( 334 +**AT+SEARCH** 335 +))) 366 366 367 -* **AT+SEARCH** 368 - 337 +((( 369 369 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. 339 +))) 370 370 371 - 341 +((( 372 372 **Define wait timeout:** 343 +))) 373 373 345 +((( 374 374 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 347 +))) 375 375 376 - 349 +((( 377 377 After we got the valid value from each RS485 commands, we need to combine them together with the command **AT+DATAUP**. 351 +))) 378 378 379 - 380 380 **Examples:** 381 381 382 382 Below are examples for the how above AT Commands works. 383 383 384 - 385 385 **AT+COMMANDx : **This command will be sent to RS485/TTL devices during each sampling, Max command length is 14 bytes. The grammar is: 386 386 359 +(% border="1" class="table-bordered" %) 387 387 |((( 388 388 **AT+COMMANDx=xx xx xx xx xx xx xx xx xx xx xx xx,m** 389 389 ... ... @@ -396,9 +396,9 @@ 396 396 397 397 In the RS485-BL, we should use this command AT+COMMAND1=01 03 0B B8 00 02,1 for the same. 398 398 399 - 400 400 **AT+SEARCHx**: This command defines how to handle the return from AT+COMMANDx. 401 401 374 +(% border="1" class="table-bordered" %) 402 402 |((( 403 403 **AT+SEARCHx=aa,xx xx xx xx xx** 404 404 ... ... @@ -416,7 +416,7 @@ 416 416 417 417 The valid data will be all bytes after 1E 56 34 , so it is 2e 30 58 5f 36 41 30 31 00 49 418 418 419 -[[image: file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image013.png]]392 +[[image:1652954654347-831.png]] 420 420 421 421 422 422 1. For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
- 1652954654347-831.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +138.7 KB - Content
- 1653266934636-343.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +176.5 KB - Content
- 1653267211009-519.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +138.7 KB - Content
- 1653268091319-405.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +399.3 KB - Content
- 1653268155545-638.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +113.7 KB - Content
- 1653268227651-549.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +1.3 MB - Content
- 1653269403619-508.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +27.8 KB - Content
- 1653269438444-278.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +26.6 KB - Content