Changes for page RS485-LN – RS485 to LoRaWAN Converter User Manual
Last modified by Mengting Qiu on 2025/07/14 09:59
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 24 added, 0 removed)
- 1654157178836-407.png
- 1654157342174-798.png
- 1654158783574-851.png
- 1654159460680-153.png
- 1654160691922-496.png
- 1654162355560-817.png
- 1654162368066-342.png
- 1654162478620-421.png
- 1654162535040-878.png
- image-20220602153621-1.png
- image-20220602153621-2.png
- image-20220602153621-3.png
- image-20220602155039-4.png
- image-20220602163333-5.png
- image-20220602165351-6.png
- image-20220602165351-7.png
- image-20220602171200-8.png
- image-20220602171200-9.png
- image-20220602175638-10.png
- image-20220602175743-11.png
- image-20220602175818-12.png
- image-20220602175848-13.png
- image-20220602175912-14.png
- image-20220606110929-1.png
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,26 +18,40 @@ 18 18 19 19 ((( 20 20 ((( 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. 27 +((( 28 +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 ((( 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. 33 +((( 34 +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 ((( 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. 39 +((( 40 +(% 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 ((( 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. 45 +((( 46 +(% 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 34 ))) 48 + 49 +((( 50 +(% 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]] 35 35 ))) 52 +))) 53 +))) 36 36 37 37 [[image:1653267211009-519.png||height="419" width="724"]] 38 38 57 + 39 39 == 1.2 Specifications == 40 40 60 + 41 41 **Hardware System:** 42 42 43 43 * STM32L072CZT6 MCU ... ... @@ -44,8 +44,6 @@ 44 44 * SX1276/78 Wireless Chip 45 45 * Power Consumption (exclude RS485 device): 46 46 ** Idle: 32mA@12v 47 - 48 -* 49 49 ** 20dB Transmit: 65mA@12v 50 50 51 51 **Interface for Model:** ... ... @@ -72,7 +72,7 @@ 72 72 * Preamble detection. 73 73 * 127 dB Dynamic Range RSSI. 74 74 * Automatic RF Sense and CAD with ultra-fast AFC. 75 -* Packet engine up to 256 bytes with CRC .93 +* Packet engine up to 256 bytes with CRC 76 76 77 77 == 1.3 Features == 78 78 ... ... @@ -98,15 +98,22 @@ 98 98 99 99 [[RS485-LN Image files – Download link and Change log>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/]] 100 100 119 + 101 101 == 1.6 Hardware Change log == 102 102 103 103 ((( 104 104 ((( 124 +((( 105 105 v1.2: Add External Interrupt Pin. 126 +))) 106 106 128 +((( 107 107 v1.0: Release 108 108 ))) 131 + 132 + 109 109 ))) 134 +))) 110 110 111 111 = 2. Power ON Device = 112 112 ... ... @@ -121,6 +121,8 @@ 121 121 ))) 122 122 123 123 [[image:1653268091319-405.png]] 149 + 150 + 124 124 ))) 125 125 126 126 = 3. Operation Mode = ... ... @@ -128,9 +128,13 @@ 128 128 == 3.1 How it works? == 129 129 130 130 ((( 158 +((( 131 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. 132 132 ))) 133 133 162 + 163 +))) 164 + 134 134 == 3.2 Example to join LoRaWAN network == 135 135 136 136 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. ... ... @@ -137,15 +137,20 @@ 137 137 138 138 [[image:1653268155545-638.png||height="334" width="724"]] 139 139 171 + 140 140 ((( 173 +((( 141 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: 175 +))) 142 142 177 +((( 143 143 485A+ and 485B- of the sensor are connected to RS485A and RA485B of RS485-LN respectively. 179 +))) 144 144 145 145 [[image:1653268227651-549.png||height="592" width="720"]] 146 146 147 147 ((( 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: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: 149 149 ))) 150 150 151 151 ((( ... ... @@ -192,35 +192,42 @@ 192 192 193 193 [[image:1652953568895-172.png||height="232" width="724"]] 194 194 231 + 195 195 == 3.3 Configure Commands to read data == 196 196 197 197 ((( 198 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. 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. 200 200 ))) 239 +))) 201 201 202 202 ((( 242 +((( 203 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 204 ))) 245 + 246 + 205 205 ))) 248 +))) 206 206 207 207 === 3.3.1 onfigure UART settings for RS485 or TTL communication === 208 208 209 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: 210 210 211 -(% border="1" style="background-color:#ffffcc; color:green; width: 795px" %)212 -|((( 254 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %) 255 +|=(% style="width: 110px;" %)((( 213 213 **AT Commands** 214 -)))|(% style="width: 285px" %)(((257 +)))|=(% style="width: 190px;" %)((( 215 215 **Description** 216 -)))|(% style="width: 347px" %)(((259 +)))|=(% style="width: 190px;" %)((( 217 217 **Example** 218 218 ))) 219 -|((( 262 +|(% style="width:110px" %)((( 220 220 AT+BAUDR 221 -)))|(% style="width: 285px" %)(((264 +)))|(% style="width:190px" %)((( 222 222 Set the baud rate (for RS485 connection). Default Value is: 9600. 223 -)))|(% style="width: 347px" %)(((266 +)))|(% style="width:190px" %)((( 224 224 ((( 225 225 AT+BAUDR=9600 226 226 ))) ... ... @@ -229,11 +229,11 @@ 229 229 Options: (1200,2400,4800,14400,19200,115200) 230 230 ))) 231 231 ))) 232 -|((( 275 +|(% style="width:110px" %)((( 233 233 AT+PARITY 234 -)))|(% style="width: 285px" %)(((277 +)))|(% style="width:190px" %)((( 235 235 Set UART parity (for RS485 connection) 236 -)))|(% style="width: 347px" %)(((279 +)))|(% style="width:190px" %)((( 237 237 ((( 238 238 AT+PARITY=0 239 239 ))) ... ... @@ -242,9 +242,9 @@ 242 242 Option: 0: no parity, 1: odd parity, 2: even parity 243 243 ))) 244 244 ))) 245 -|((( 288 +|(% style="width:110px" %)((( 246 246 AT+STOPBIT 247 -)))|(% style="width: 285px" %)(((290 +)))|(% style="width:190px" %)((( 248 248 ((( 249 249 Set serial stopbit (for RS485 connection) 250 250 ))) ... ... @@ -252,7 +252,7 @@ 252 252 ((( 253 253 254 254 ))) 255 -)))|(% style="width: 347px" %)(((298 +)))|(% style="width:190px" %)((( 256 256 ((( 257 257 AT+STOPBIT=0 for 1bit 258 258 ))) ... ... @@ -266,6 +266,7 @@ 266 266 ))) 267 267 ))) 268 268 312 + 269 269 === 3.3.2 Configure sensors === 270 270 271 271 ((( ... ... @@ -274,90 +274,48 @@ 274 274 ))) 275 275 ))) 276 276 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" %)(((321 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %) 322 +|=(% style="width: 110px;" %)**AT Commands**|=(% style="width: 190px;" %)**Description**|=(% style="width: 190px;" %)**Example** 323 +|AT+CFGDEV|(% style="width:110px" %)((( 280 280 This command is used to configure the RS485/TTL devices; they won’t be used during sampling. 281 281 282 282 AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx, 283 283 284 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,m329 +)))|(% style="width:190px" %)AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m 286 286 331 + 287 287 === 3.3.3 Configure read commands for each sampling === 288 288 289 289 ((( 290 -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 -))) 335 +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. 292 292 293 -((( 294 -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 -))) 296 - 297 -((( 298 298 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 -))) 300 300 301 -((( 302 302 This section describes how to achieve above goals. 303 -))) 304 304 305 -((( 306 -During each sampling, the RS485-BL can support 15 commands to read sensors. And combine the return to one or several uplink payloads. 307 -))) 341 +During each sampling, the RS485-LN can support 15 commands to read sensors. And combine the return to one or several uplink payloads. 308 308 309 -((( 310 -**Command from RS485-BL to Sensor:** 311 -))) 312 312 313 -((( 314 -RS485-BL can send out pre-set max 15 strings via **AT+COMMAD1**, **ATCOMMAND2**,…, to **AT+COMMANDF** . All commands are of same grammar. 315 -))) 344 +**Each RS485 commands include two parts:** 316 316 317 -((( 318 -**Handle return from sensors to RS485-BL**: 319 -))) 346 +~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. 320 320 321 -((( 322 -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 -))) 348 +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. 324 324 325 -* ((( 326 -**AT+DATACUT** 327 -))) 350 +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 328 328 329 -((( 330 -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 -))) 332 332 333 -* ((( 334 -**AT+SEARCH** 335 -))) 336 - 337 -((( 338 -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 -))) 340 - 341 -((( 342 -**Define wait timeout:** 343 -))) 344 - 345 -((( 346 -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 -))) 348 - 349 -((( 350 350 After we got the valid value from each RS485 commands, we need to combine them together with the command **AT+DATAUP**. 351 -))) 352 352 353 -**Examples:** 354 354 355 355 Below are examples for the how above AT Commands works. 356 356 357 -**AT+COMMANDx : **This command will be sent to RS485/TTL devices during each sampling, Max command length is 14 bytes. The grammar is: 358 358 359 -(% border="1" class="table-bordered" %) 360 -|((( 359 +**AT+COMMANDx : **This command will be sent to RS485 devices during each sampling, Max command length is 14 bytes. The grammar is: 360 + 361 +(% border="1" style="background-color:#4bacc6; color:white; width:499px" %) 362 +|(% style="width:496px" %)((( 361 361 **AT+COMMANDx=xx xx xx xx xx xx xx xx xx xx xx xx,m** 362 362 363 363 **xx xx xx xx xx xx xx xx xx xx xx xx: The RS485 command to be sent** ... ... @@ -365,49 +365,15 @@ 365 365 **m: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command** 366 366 ))) 367 367 368 -((( 369 369 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. 370 -))) 371 371 372 -((( 373 -In the RS485-BL, we should use this command AT+COMMAND1=01 03 0B B8 00 02,1 for the same. 374 -))) 372 +In the RS485-LN, we should use this command AT+COMMAND1=01 03 0B B8 00 02,1 for the same. 375 375 376 -((( 377 -**AT+SEARCHx**: This command defines how to handle the return from AT+COMMANDx. 378 -))) 379 379 380 -(% border="1" class="table-bordered" %) 381 -|((( 382 -**AT+SEARCHx=aa,xx xx xx xx xx** 383 - 384 -* **aa: 1: prefix match mode; 2: prefix and suffix match mode** 385 -* **xx xx xx xx xx: match string. Max 5 bytes for prefix and 5 bytes for suffix** 386 - 387 - 388 -))) 389 - 390 -**Examples:** 391 - 392 -~1. For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49 393 - 394 -If we set AT+SEARCH1=1,1E 56 34. (max 5 bytes for prefix) 395 - 396 -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** 397 - 398 -[[image:1653269403619-508.png]] 399 - 400 -2. For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49 401 - 402 -If we set AT+SEARCH1=2, 1E 56 34+31 00 49 403 - 404 -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** 405 - 406 -[[image:1653269438444-278.png]] 407 - 408 408 **AT+DATACUTx : **This command defines how to handle the return from AT+COMMANDx, max return length is 45 bytes. 409 409 410 -|((( 377 +(% border="1" style="background-color:#4bacc6; color:white; width:510px" %) 378 +|(% style="width:510px" %)((( 411 411 **AT+DATACUTx=a,b,c** 412 412 413 413 * **a: length for the return of AT+COMMAND** ... ... @@ -415,48 +415,37 @@ 415 415 * **c: define the position for valid value. ** 416 416 ))) 417 417 418 -Examples: 386 +**Examples:** 419 419 420 420 * Grab bytes: 421 421 422 -[[image: 1653269551753-223.png||height="311" width="717"]]390 +[[image:image-20220602153621-1.png]] 423 423 392 + 424 424 * Grab a section. 425 425 426 -[[image: 1653269568276-930.png||height="325" width="718"]]395 +[[image:image-20220602153621-2.png]] 427 427 397 + 428 428 * Grab different sections. 429 429 430 -[[image: 1653269593172-426.png||height="303" width="725"]]400 +[[image:image-20220602153621-3.png]] 431 431 432 -(% style="color:red" %)**Note:** 402 + 403 +))) 433 433 434 -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. 435 - 436 -Example: 437 - 438 -(% style="color:red" %)AT+COMMAND1=11 01 1E D0,0 439 - 440 -(% style="color:red" %)AT+SEARCH1=1,1E 56 34 441 - 442 -(% style="color:red" %)AT+DATACUT1=0,2,1~~5 443 - 444 -(% style="color:red" %)Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49 445 - 446 -(% style="color:red" %)String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49 447 - 448 -(% style="color:red" %)Valid payload after DataCUT command: 2e 30 58 5f 36 449 - 450 -[[image:1653269618463-608.png]] 451 - 452 452 === 3.3.4 Compose the uplink payload === 453 453 454 454 ((( 455 455 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.** 409 + 410 + 456 456 ))) 457 457 458 458 ((( 459 -(% style="color:#4f81bd" %)**Examples: AT+DATAUP=0** 414 +(% style="color:#037691" %)**Examples: AT+DATAUP=0** 415 + 416 + 460 460 ))) 461 461 462 462 ((( ... ... @@ -477,8 +477,10 @@ 477 477 478 478 [[image:1653269759169-150.png||height="513" width="716"]] 479 479 480 -(% style="color:#4f81bd" %)**Examples: AT+DATAUP=1** 481 481 438 +(% style="color:#037691" %)**Examples: AT+DATAUP=1** 439 + 440 + 482 482 Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**Multiply UPLINKs**. 483 483 484 484 Final Payload is ... ... @@ -485,704 +485,1029 @@ 485 485 486 486 (% style="color:#4f81bd" %)**Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA** 487 487 488 -1. Battery Info (2 bytes): Battery voltage 489 -1. PAYVER (1 byte): Defined by AT+PAYVER 490 -1. PAYLOAD COUNT (1 byte): Total how many uplinks of this sampling. 491 -1. PAYLOAD# (1 byte): Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT) 492 -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 493 493 494 -[[image:1653269916228-732.png||height="433" width="711"]] 448 +1. PAYVER: Defined by AT+PAYVER 449 +1. PAYLOAD COUNT: Total how many uplinks of this sampling. 450 +1. PAYLOAD#: Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT) 451 +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 495 495 453 +[[image:image-20220602155039-4.png]] 496 496 497 -So totally there will be 3 uplinks for this sampling, each uplink includes 6 bytes DATA 498 498 499 - DATA1=RETURN1Valid Value=(%style="background-color:green;color:white"%)20200a 33 90 41456 +So totally there will be 3 uplinks for this sampling, each uplink include 8 bytes DATA 500 500 501 -DATA 2=1^^st^^~~6^^th^^byteof Valid value of RETURN10=(%style="background-color:green; color:white" %)02 aa0581 0a20458 +DATA1=RETURN1 Valid Value + the first two of Valid value of RETURN10= **20 20 0a 33 90 41 02 aa** 502 502 503 -DATA 3=7^^th^^ ~~ 11^^th^^ bytesof Valid value of RETURN10(%style="background-color:green;color:white"%)20 20 20 2d30460 +DATA2=3^^rd^^ ~~ 10^^th^^ byte of Valid value of RETURN10= **05 81 0a 20 20 20 20 2d** 504 504 505 - Belowareheuplinkpayloads:462 +DATA3=the rest of Valid value of RETURN10= **30** 506 506 507 -[[image:1653270130359-810.png]] 508 508 465 +(% 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: 509 509 510 - (%style="color:red"%)**Notice:theMaxbytes is accordingto the maxsupportbytesin differentFrequencyBands forlowest SF.As below:**467 + ~* For AU915/AS923 bands, if UplinkDwell time=0, max 51 bytes for each uplink. 511 511 512 - ~*51 bytes for each uplink( so 51 -5 = 46 max valid date)469 + * For AU915/AS923 bands, if UplinkDwell time=0, max 11 bytes for each uplink. 513 513 514 - * For AU915/AS923bands,if UplinkDwell time=1, max 11 bytes( so 11 -5 = 6 max valid date).471 + * For US915 band, max 11 bytes for each uplink. 515 515 516 - * US915band,max 11bytes( so 11 -5 = 6 max valid date).473 + ~* For all other bands: max 51 bytes for each uplink. 517 517 518 - ~* For all other bands: max 51 bytes for each uplink ( so 51 -5 = 46 max valid date). 519 519 476 +Below are the uplink payloads: 520 520 478 +[[image:1654157178836-407.png]] 521 521 522 -1. 523 -11. 524 -111. Uplink on demand 525 525 526 - Exceptuplink periodically, RS485-BLis able to uplink on demand.The server sends downlink command to RS485-BL and RS485 will uplink data base on the command.481 +=== 3.3.5 Uplink on demand === 527 527 483 +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. 484 + 528 528 Downlink control command: 529 529 530 - [[0x08 command>>path:#downlink_08]]:Poll an uplink with current command set in RS485-BL.487 +**0x08 command**: Poll an uplink with current command set in RS485-LN. 531 531 532 - [[0xA8 command>>path:#downlink_A8]]:Send a command to RS485-BL and uplink the output from sensors.489 +**0xA8 command**: Send a command to RS485-LN and uplink the output from sensors. 533 533 534 534 535 535 536 -1. 537 -11. 538 -111. Uplink on Interrupt 493 +=== 3.3.6 Uplink on Interrupt === 539 539 540 - Put theinterruptsensorbetween3.3v_outand GPIOext.[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image022.png]]495 +RS485-LN support external Interrupt uplink since hardware v1.2 release. 541 541 542 - AT+INTMOD=0 DisableInterrupt497 +[[image:1654157342174-798.png]] 543 543 544 - AT+INTMOD=1Interrupt triggerbyrising orfallingedge.499 +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. 545 545 546 -AT+INTMOD=2 Interrupt trigger by falling edge. ( Default Value) 547 547 548 - AT+INTMOD=3Interrupt trigger by risingedge.502 +== 3.4 Uplink Payload == 549 549 550 550 551 -1. 552 -11. Uplink Payload 505 +[[image:image-20220606110929-1.png]] 553 553 554 -|**Size(bytes)**|**2**|**1**|**Length depends on the return from the commands** 555 -|Value|((( 556 -Battery(mV) 557 - 558 -& 559 - 560 -Interrupt _Flag 561 -)))|((( 562 -PAYLOAD_VER 563 - 564 - 565 -)))|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. 566 - 567 567 Below is the decoder for the first 3 bytes. The rest bytes are dynamic depends on different RS485 sensors. 568 568 569 569 570 -fu nctionDecoder(bytes,port){510 +== 3.5 Configure RS485-BL via AT or Downlink == 571 571 572 -~/~/Payload Formats of RS485-BL Deceive 512 +((( 513 +User can configure RS485-LN via AT Commands or LoRaWAN Downlink Commands 514 +))) 573 573 574 -return { 575 - 576 - ~/~/Battery,units:V 577 - 578 - BatV:((bytes[0]<<8 | bytes[1])&0x7fff)/1000, 579 - 580 - ~/~/GPIO_EXTI 581 - 582 - EXTI_Trigger:(bytes[0] & 0x80)? "TRUE":"FALSE", 583 - 584 - ~/~/payload of version 585 - 586 - Pay_ver:bytes[2], 587 - 588 - }; 589 - 590 - } 591 - 592 - 593 - 594 - 595 - 596 - 597 - 598 -TTN V3 uplink screen shot. 599 - 600 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png]] 601 - 602 -1. 603 -11. Configure RS485-BL via AT or Downlink 604 - 605 -User can configure RS485-BL via [[AT Commands >>path:#_Using_the_AT]]or LoRaWAN Downlink Commands 606 - 516 +((( 607 607 There are two kinds of Commands: 518 +))) 608 608 609 -* **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 520 +* ((( 521 +(% 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]] 522 +))) 610 610 611 -* **Sensor Related Commands**: These commands are special designed for RS485-BL. User can see these commands below: 524 +* ((( 525 +(% style="color:#4f81bd" %)**Sensor Related Commands**(%%): These commands are special designed for RS485-LN. User can see these commands below: 526 +))) 612 612 613 - 1.614 - 11.615 - 111. Common Commands:528 +((( 529 + 530 +))) 616 616 617 -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]] 618 618 533 +=== 3.5.1 Common Commands === 619 619 620 -1. 621 -11. 622 -111. Sensor related commands: 535 +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]] 623 623 624 -==== Choose Device Type (RS485 or TTL) ==== 625 625 626 - RS485-BLcan connect to either RS485sensorsorTTL sensor. User need to specify whattypeof sensor needtoconnect.538 +=== 3.5.2 Sensor related commands === 627 627 628 - *ATCommand540 +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. 629 629 630 - **AT+MOD=1** ~/~/ Set to support RS485-MODBUS type sensors. User can connectmultiply RS485 , Modbus sensorsto the A / B pins.542 +[[image:image-20220602163333-5.png||height="263" width="1160"]] 631 631 632 - **AT+MOD=2** ~/~/ Set to supportTTLLevel sensors,Usercan connect oneTTLSensortotheTXD/RXD/GNDpins.544 +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) 633 633 634 634 635 - *DownlinkPayload547 +=== 3.5.3 Sensor related commands === 636 636 637 -**0A aa** à same as AT+MOD=aa 638 638 639 639 640 640 641 -==== [[RS485 Debug Command>>path:#downlink_A8]](AT+CFGDEV)====552 +==== **RS485 Debug Command** ==== 642 642 643 -This command is used to configure the RS485 or TTL sensors; they won’t be used during sampling. 554 +((( 555 +This command is used to configure the RS485 devices; they won’t be used during sampling. 556 +))) 644 644 645 -* AT Command 558 +* ((( 559 +**AT Command** 560 +))) 646 646 647 -AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m 562 +(% class="box infomessage" %) 563 +((( 564 +((( 565 +**AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m** 566 +))) 567 +))) 648 648 649 -m: 0: no CRC; 1: add CRC-16/MODBUS in the end of this command. 569 +((( 570 +m: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command 571 +))) 650 650 573 +* ((( 574 +**Downlink Payload** 575 +))) 651 651 652 - 653 -* Downlink Payload 654 - 577 +((( 655 655 Format: A8 MM NN XX XX XX XX YY 579 +))) 656 656 581 +((( 657 657 Where: 583 +))) 658 658 659 -* MM: 1: add CRC-16/MODBUS ; 0: no CRC 660 -* NN: The length of RS485 command 661 -* XX XX XX XX: RS485 command total NN bytes 662 -* 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 585 +* ((( 586 +MM: 1: add CRC-16/MODBUS ; 0: no CRC 587 +))) 588 +* ((( 589 +NN: The length of RS485 command 590 +))) 591 +* ((( 592 +XX XX XX XX: RS485 command total NN bytes 593 +))) 594 +* ((( 595 +((( 596 +YY: How many bytes will be uplink from the return of this RS485 command, 597 +))) 663 663 664 -**Example 1:** 599 +* ((( 600 +if YY=0, RS485-LN will execute the downlink command without uplink; 601 +))) 602 +* ((( 603 +if YY>0, RS485-LN will uplink total YY bytes from the output of this RS485 command; Fport=200 604 +))) 605 +* ((( 606 +if YY=FF, RS485-LN will uplink RS485 output with the downlink command content; Fport=200. 607 +))) 608 +))) 665 665 610 +((( 611 +**Example 1** ~-~-> Configure without ask for uplink (YY=0) 612 +))) 613 + 614 +((( 666 666 To connect a Modbus Alarm with below commands. 616 +))) 667 667 668 -* 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 +* ((( 619 +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. 620 +))) 669 669 670 -* 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 +* ((( 623 +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. 624 +))) 671 671 626 +((( 672 672 So if user want to use downlink command to control to RS485 Alarm, he can use: 628 +))) 673 673 674 -**A8 01 06 0A 05 00 04 00 01 00**: to activate the RS485 Alarm 630 +((( 631 +(% style="color:#4f81bd" %)**A8 01 06 0A 05 00 04 00 01 00**(%%): to activate the RS485 Alarm 632 +))) 675 675 676 -**A8 01 06 0A 05 00 04 00 00 00**: to deactivate the RS485 Alarm 634 +((( 635 +(% style="color:#4f81bd" %)**A8 01 06 0A 05 00 04 00 00 00**(%%): to deactivate the RS485 Alarm 636 +))) 677 677 638 +((( 678 678 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. 640 +))) 679 679 642 +((( 643 + 644 +))) 680 680 681 -**Example 2:** 646 +((( 647 +**Example 2** ~-~-> Configure with requesting uplink and original downlink command (**YY=FF**) 648 +))) 682 682 683 -Check TTL Sensor return: 650 +((( 651 +User in IoT server send a downlink command: (% style="color:#4f81bd" %)**A8 01 06 0A 08 00 04 00 01 YY** 652 +))) 684 684 685 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image024.png]] 654 +((( 655 + 656 +))) 686 686 658 +((( 659 +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: 660 +))) 687 687 662 +((( 663 + **A8** (% style="color:#4f81bd" %)**0A 08 00 04 00 **(% style="color:red" %)**01 06** ** **(% style="color:green" %)**0A 08 00 04 00 00** 664 +))) 688 688 666 +((( 667 + [[image:1654159460680-153.png]] 668 +))) 689 689 690 -==== Set Payload version ==== 691 691 671 + 672 + 673 +==== **Set Payload version** ==== 674 + 675 +((( 692 692 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. 677 +))) 693 693 694 -* AT Command: 679 +* ((( 680 +**AT Command:** 681 +))) 695 695 696 -AT+PAYVER: Set PAYVER field = 1 683 +(% class="box infomessage" %) 684 +((( 685 +((( 686 +**AT+PAYVER: Set PAYVER field = 1** 687 +))) 688 +))) 697 697 690 +* ((( 691 +**Downlink Payload:** 692 +))) 698 698 699 -* Downlink Payload: 694 +((( 695 +**0xAE 01** ~-~-> Set PAYVER field = 0x01 696 +))) 700 700 701 -0xAE 01 à Set PAYVER field = 0x01 698 +((( 699 +**0xAE 0F** ~-~-> Set PAYVER field = 0x0F 700 +))) 702 702 703 -0xAE 0F à Set PAYVER field = 0x0F 704 704 705 705 706 -==== Set RS485 Sampling Commands ==== 707 707 708 - AT+COMMANDx,AT+DATACUTxandAT+SEARCHx705 +==== **Set RS485 Sampling Commands** ==== 709 709 710 -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]]. 707 +((( 708 +AT+COMMANDx or AT+DATACUTx 709 +))) 711 711 711 +((( 712 +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"]]. 713 +))) 712 712 713 -* AT Command: 715 +((( 716 + 717 +))) 714 714 715 -AT+COMMANDx: Configure RS485 read command to sensor. 719 +* ((( 720 +**AT Command:** 721 +))) 716 716 717 -AT+DATACUTx: Configure how to handle return from RS485 devices. 723 +(% class="box infomessage" %) 724 +((( 725 +((( 726 +**AT+COMMANDx: Configure RS485 read command to sensor.** 727 +))) 728 +))) 718 718 719 -AT+SEARCHx: Configure search command 730 +(% class="box infomessage" %) 731 +((( 732 +((( 733 +**AT+DATACUTx: Configure how to handle return from RS485 devices.** 734 +))) 735 +))) 720 720 737 +((( 738 + 739 +))) 721 721 722 -* Downlink Payload: 741 +* ((( 742 +**Downlink Payload:** 743 +))) 723 723 724 -0xAF downlink command can be used to set AT+COMMANDx or AT+DATACUTx. 745 +((( 746 +**0xAF** downlink command can be used to set AT+COMMANDx or AT+DATACUTx. 747 +))) 725 725 726 -Note: if user use AT+COMMANDx to add a new command, he also need to send AT+DATACUTx downlink. 749 +((( 750 +(% style="color:red" %)**Note**(%%): if user use AT+COMMANDx to add a new command, he also need to send AT+DATACUTx downlink. 751 +))) 727 727 753 +((( 728 728 Format: AF MM NN LL XX XX XX XX YY 755 +))) 729 729 757 +((( 730 730 Where: 759 +))) 731 731 732 -* MM: the ATCOMMAND or AT+DATACUT to be set. Value from 01 ~~ 0F, 733 -* NN: 0: no CRC; 1: add CRC-16/MODBUS ; 2: set the AT+DATACUT value. 734 -* LL: The length of AT+COMMAND or AT+DATACUT command 735 -* XX XX XX XX: AT+COMMAND or AT+DATACUT command 736 -* 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. 761 +* ((( 762 +MM: the ATCOMMAND or AT+DATACUT to be set. Value from 01 ~~ 0F, 763 +))) 764 +* ((( 765 +NN: 0: no CRC; 1: add CRC-16/MODBUS ; 2: set the AT+DATACUT value. 766 +))) 767 +* ((( 768 +LL: The length of AT+COMMAND or AT+DATACUT command 769 +))) 770 +* ((( 771 +XX XX XX XX: AT+COMMAND or AT+DATACUT command 772 +))) 773 +* ((( 774 +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. 775 +))) 737 737 738 -Example: 777 +((( 778 +**Example:** 779 +))) 739 739 740 -**AF 03 01 06 0A 05 00 04 00 01 00**: Same as AT+COMMAND3=0A 05 00 04 00 01,1 781 +((( 782 +(% 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 783 +))) 741 741 742 -**AF 03 02 06 10 01 05 06 09 0A 00**: Same as AT+DATACUT3=**16**,**1**,**5+6+9+10** 785 +((( 786 +(% 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** 787 +))) 743 743 744 -**AF 03 02 06 0B 02 05 07 08 0A 00**: Same as AT+DATACUT3=**11**,**2**,**5~~7+8~~10** 789 +((( 790 +(% 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** 791 +))) 745 745 746 746 747 -0xAB downlink command can be used for set AT+SEARCHx 748 748 749 -Example: **AB aa 01 03 xx xx xx** (03 here means there are total 3 bytes after 03) So 750 750 751 -* AB aa 01 03 xx xx xx same as AT+SEARCHaa=1,xx xx xx 752 -* 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 796 +==== **Fast command to handle MODBUS device** ==== 753 753 754 -**AB aa 02 03 xx xx xx 02 yy yy** same as **AT+SEARCHaa=2,xx xx xx+yy yy** 798 +((( 799 +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]]. 800 +))) 755 755 802 +((( 803 +This command is valid since v1.3 firmware version 804 +))) 756 756 757 -==== Fast command to handle MODBUS device ==== 806 +((( 807 +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. 808 +))) 758 758 759 -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]]. 810 +((( 811 + 812 +))) 760 760 761 -This command is valid since v1.3 firmware version 814 +((( 815 +**Example:** 816 +))) 762 762 818 +* ((( 819 +AT+MBFUN=1 and AT+DATACUT1/AT+DATACUT2 are not configure (0,0,0). So RS485-LN. 820 +))) 821 +* ((( 822 +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. 823 +))) 824 +* ((( 825 +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. 826 +))) 763 763 764 - AT+MBFUN has only two value:828 +[[image:image-20220602165351-6.png]] 765 765 766 - * AT+MBFUN=1: EnableModbus reading. And get response base on the MODBUS return830 +[[image:image-20220602165351-7.png]] 767 767 768 -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. 769 769 770 -* AT+MBFUN=0: Disable Modbus fast reading. 771 771 772 -Example: 773 773 774 -* AT+MBFUN=1 and AT+DATACUT1/AT+DATACUT2 are not configure (0,0,0). 775 -* 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. 776 -* 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. 835 +==== **RS485 command timeout** ==== 777 777 778 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image025.png]] 837 +((( 838 +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. 839 +))) 779 779 841 +((( 842 +Default value: 0, range: 0 ~~ 65 seconds 843 +))) 780 780 781 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image026.png]] 845 +* ((( 846 +**AT Command:** 847 +))) 782 782 849 +(% class="box infomessage" %) 850 +((( 851 +((( 852 +**AT+CMDDLaa=hex(bb cc)*1000** 853 +))) 854 +))) 783 783 784 -* Downlink Commands: 856 +((( 857 +**Example:** 858 +))) 785 785 786 -A9 aa -à Same as AT+MBFUN=aa 860 +((( 861 +**AT+CMDDL1=1000** to send the open time to 1000ms 862 +))) 787 787 864 +((( 865 + 866 +))) 788 788 789 -==== RS485 command timeout ==== 868 +* ((( 869 +**Downlink Payload:** 870 +))) 790 790 791 -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. 872 +((( 873 +**0x AA aa bb cc** 874 +))) 792 792 793 -Default value: 0, range: 0 ~~ 5 seconds 876 +((( 877 +Same as: AT+CMDDLaa=hex(bb cc)*1000 878 +))) 794 794 880 +((( 881 + **Example:** 882 +))) 795 795 796 -* AT Command: 884 +((( 885 + 0xAA 01 00 01 ~-~-> Same as **AT+CMDDL1=1000 ms** 886 +))) 797 797 798 -AT+CMDDLaa=hex(bb cc) 799 799 800 -Example: 801 801 802 -**AT+CMDDL1=1000** to send the open time to 1000ms 803 803 891 +==== **Uplink payload mode** ==== 804 804 805 -* Downlink Payload: 893 +((( 894 +Define to use one uplink or multiple uplinks for the sampling. 895 +))) 806 806 807 -0x AA aa bb cc 897 +((( 898 +The use of this command please see: [[Compose Uplink payload>>||anchor="H3.3.4Composetheuplinkpayload"]] 899 +))) 808 808 809 -Same as: AT+CMDDLaa=hex(bb cc) 901 +* ((( 902 +**AT Command:** 903 +))) 810 810 811 - Example: 905 +(% class="box infomessage" %) 906 +((( 907 +((( 908 +**AT+DATAUP=0** 909 +))) 910 +))) 812 812 813 - 0xAA 01 03 E8 à Same as **AT+CMDDL1=1000 ms** 912 +(% class="box infomessage" %) 913 +((( 914 +((( 915 +**AT+DATAUP=1** 916 +))) 917 +))) 814 814 919 +((( 920 + 921 +))) 815 815 816 -==== [[Uplink>>path:#downlink_A8]] payload mode ==== 923 +* ((( 924 +**Downlink Payload:** 925 +))) 817 817 818 -Define to use one uplink or multiple uplinks for the sampling. 927 +((( 928 +**0xAD 00** **~-~->** Same as AT+DATAUP=0 929 +))) 819 819 820 -The use of this command please see: [[Compose Uplink payload>>path:#DataUP]] 931 +((( 932 +**0xAD 01** **~-~->** Same as AT+DATAUP=1 933 +))) 821 821 822 -* AT Command: 823 823 824 -AT+DATAUP=0 825 825 826 -AT+DATAUP=1 827 827 938 +==== **Manually trigger an Uplink** ==== 828 828 829 -* Downlink Payload: 940 +((( 941 +Ask device to send an uplink immediately. 942 +))) 830 830 831 -0xAD 00 à Same as AT+DATAUP=0 944 +* ((( 945 +**AT Command:** 946 +))) 832 832 833 -0xAD 01 à Same as AT+DATAUP=1 948 +((( 949 +No AT Command for this, user can press the [[ACT button>>||anchor="H3.7Buttons"]] for 1 second for the same. 950 +))) 834 834 952 +((( 953 + 954 +))) 835 835 836 -==== Manually trigger an Uplink ==== 956 +* ((( 957 +**Downlink Payload:** 958 +))) 837 837 838 -Ask device to send an uplink immediately. 960 +((( 961 +**0x08 FF**, RS485-LN will immediately send an uplink. 962 +))) 839 839 840 -* Downlink Payload: 841 841 842 -0x08 FF, RS485-BL will immediately send an uplink. 843 843 844 844 845 -==== Clear RS485 Command ==== 967 +==== **Clear RS485 Command** ==== 846 846 969 +((( 847 847 The AT+COMMANDx and AT+DATACUTx settings are stored in special location, user can use below command to clear them. 971 +))) 848 848 973 +* ((( 974 +**AT Command:** 975 +))) 849 849 850 -* AT Command: 851 - 977 +((( 852 852 **AT+CMDEAR=mm,nn** mm: start position of erase ,nn: stop position of erase 979 +))) 853 853 981 +((( 854 854 Etc. AT+CMDEAR=1,10 means erase AT+COMMAND1/AT+DATACUT1 to AT+COMMAND10/AT+DATACUT10 983 +))) 855 855 985 +((( 856 856 Example screen shot after clear all RS485 commands. 987 +))) 857 857 989 +((( 990 + 991 +))) 858 858 859 - 993 +((( 860 860 The uplink screen shot is: 995 +))) 861 861 862 -[[image: file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png]]997 +[[image:1654160691922-496.png]] 863 863 864 864 865 -* Downlink Payload: 1000 +* ((( 1001 +**Downlink Payload:** 1002 +))) 866 866 867 -0x09 aa bb same as AT+CMDEAR=aa,bb 1004 +((( 1005 +**0x09 aa bb** same as AT+CMDEAR=aa,bb 1006 +))) 868 868 869 869 870 -==== Set Serial Communication Parameters ==== 871 871 1010 + 1011 +==== **Set Serial Communication Parameters** ==== 1012 + 1013 +((( 872 872 Set the Rs485 serial communication parameters: 1015 +))) 873 873 874 -* AT Command: 1017 +* ((( 1018 +**AT Command:** 1019 +))) 875 875 1021 +((( 876 876 Set Baud Rate: 1023 +))) 877 877 878 -AT+BAUDR=9600 ~/~/ Options: (1200,2400,4800,14400,19200,115200) 1025 +(% class="box infomessage" %) 1026 +((( 1027 +((( 1028 +**AT+BAUDR=9600** ~/~/ Options: (1200,2400,4800,14400,19200,115200) 1029 +))) 1030 +))) 879 879 1032 +((( 1033 +Set UART Parity 1034 +))) 880 880 881 -Set UART parity 1036 +(% class="box infomessage" %) 1037 +((( 1038 +((( 1039 +**AT+PARITY=0** ~/~/ Option: 0: no parity, 1: odd parity, 2: even parity 1040 +))) 1041 +))) 882 882 883 -AT+PARITY=0 ~/~/ Option: 0: no parity, 1: odd parity, 2: even parity 884 - 885 - 1043 +((( 886 886 Set STOPBIT 1045 +))) 887 887 888 -AT+STOPBIT=0 ~/~/ Option: 0 for 1bit; 1 for 1.5 bit ; 2 for 2 bits 1047 +(% class="box infomessage" %) 1048 +((( 1049 +((( 1050 +**AT+STOPBIT=0** ~/~/ Option: 0 for 1bit; 1 for 1.5 bit ; 2 for 2 bits 1051 +))) 1052 +))) 889 889 1054 +((( 1055 + 1056 +))) 890 890 891 -* Downlink Payload: 1058 +* ((( 1059 +**Downlink Payload:** 1060 +))) 892 892 893 -A7 01 aa bb: Same AT+BAUDR=hex(aa bb)*100 1062 +((( 1063 +**A7 01 aa bb**: Same AT+BAUDR=hex(aa bb)*100 1064 +))) 894 894 895 -Example: 1066 +((( 1067 +**Example:** 1068 +))) 896 896 897 -* A7 01 00 60 same as AT+BAUDR=9600 898 -* A7 01 04 80 same as AT+BAUDR=115200 1070 +* ((( 1071 +A7 01 00 60 same as AT+BAUDR=9600 1072 +))) 1073 +* ((( 1074 +A7 01 04 80 same as AT+BAUDR=115200 1075 +))) 899 899 1077 +((( 900 900 A7 02 aa: Same as AT+PARITY=aa (aa value: 00 , 01 or 02) 1079 +))) 901 901 1081 +((( 902 902 A7 03 aa: Same as AT+STOPBIT=aa (aa value: 00 , 01 or 02) 1083 +))) 903 903 904 904 905 -==== Control output power duration ==== 906 906 907 -User can set the output power duration before each sampling. 908 908 909 - *ATCommand:1088 +== 3.6 Listening mode for RS485 network == 910 910 911 -Example: 1090 +((( 1091 +This feature support since firmware v1.4 1092 +))) 912 912 913 -AT+3V3T=1000 ~/~/ 3V3 output power will open 1s before each sampling. 1094 +((( 1095 +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. 1096 +))) 914 914 915 - AT+5VT=1000~/~/ +5V output power will open1s before eachsampling.1098 +[[image:image-20220602171200-8.png||height="567" width="1007"]] 916 916 1100 +((( 1101 +To enable the listening mode, use can run the command AT+RXMODE. 1102 +))) 917 917 918 -* LoRaWAN Downlink Command: 1104 +((( 1105 + 1106 +))) 919 919 920 -07 01 aa bb Same as AT+5VT=(aa bb) 1108 +(% border="1" cellspacing="10" style="background-color:#ffffcc; width:500px" %) 1109 +|=(% style="width: 100px;" %)((( 1110 +**Command example** 1111 +)))|=(% style="width: 400px;" %)((( 1112 +**Function** 1113 +))) 1114 +|(% style="width:100px" %)((( 1115 +AT+RXMODE=1,10 1116 +)))|(% style="width:400px" %)((( 1117 +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. 1118 +))) 1119 +|(% style="width:100px" %)((( 1120 +AT+RXMODE=2,500 1121 +)))|(% style="width:400px" %)((( 1122 +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 1123 +))) 1124 +|(% style="width:100px" %)((( 1125 +AT+RXMODE=0,0 1126 +)))|(% style="width:400px" %)((( 1127 +Disable listening mode. This is the default settings. 1128 +))) 1129 +|(% style="width:100px" %)((( 1130 + 1131 +)))|(% style="width:400px" %)((( 1132 +A6 aa bb cc same as AT+RXMODE=aa,(bb<<8 | cc) 1133 +))) 921 921 922 -07 02 aa bb Same as AT+3V3T=(aa bb) 1135 +((( 1136 +**Downlink Command:** 1137 +))) 923 923 1139 +((( 1140 +**0xA6 aa bb cc ** same as AT+RXMODE=aa,(bb<<8 | cc) 1141 +))) 924 924 1143 +((( 1144 + 1145 +))) 925 925 1147 +((( 1148 +**Example**: 1149 +))) 926 926 927 -1. 928 -11. Buttons 1151 +((( 1152 +The RS485-LN is set to AT+RXMODE=2,1000 1153 +))) 929 929 930 -|**Button**|**Feature** 931 -|**RST**|Reboot RS485-BL 1155 +((( 1156 +There is a two Modbus commands in the RS485 network as below: 1157 +))) 932 932 933 -1. 934 -11. +3V3 Output 1159 +((( 1160 +The Modbus master send a command: (% style="background-color:#ffc000" %)01 03 00 00 00 02 c4 0b 1161 +))) 935 935 936 -RS485-BL has a Controllable +3V3 output, user can use this output to power external sensor. 1163 +((( 1164 +And Modbus slave reply with: (% style="background-color:green" %)01 03 04 00 00 00 00 fa 33 1165 +))) 937 937 938 -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. 1167 +((( 1168 +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 1169 +))) 939 939 1171 +((( 1172 +[[image:image-20220602171200-9.png]] 1173 +))) 940 940 941 -The +3V3 output time can be controlled by AT Command. 1175 +((( 1176 + 1177 +))) 942 942 943 -**AT+3V3T=1000** 1179 +((( 1180 +(% 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. 1181 +))) 944 944 945 -Means set +3v3 valid time to have 1000ms. So, the real +3v3 output will actually have 1000ms + sampling time for other sensors. 946 946 1184 +== 3.7 Buttons == 947 947 948 -By default, the AT+3V3T=0. This is a special case, means the +3V3 output is always on at any time 949 949 1187 +(% border="1" cellspacing="10" style="background-color:#f7faff; width:400px" %) 1188 +|=(% style="width: 50px;" %)**Button**|=(% style="width: 350px;" %)**Feature** 1189 +|(% 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** 1190 +|(% style="width:50px" %)**RST**|(% style="width:350px" %)Reboot RS485 1191 +|(% style="width:50px" %)**PRO**|(% style="width:350px" %)Use for upload image, see [[How to Update Image>>||anchor="H6.1Howtoupgradetheimage3F"]] 950 950 951 -1. 952 -11. +5V Output 953 953 954 - RS485-BLhasa Controllable +5V output, user can use this output to power external sensor.1194 +== 3.8 LEDs == 955 955 956 -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. 957 957 1197 +(% border="1" cellspacing="10" style="background-color:#f7faff; width:430px" %) 1198 +|=(% style="width: 50px;" %)**LEDs**|=(% style="width: 380px;" %)**Feature** 1199 +|**PWR**|Always on if there is power 1200 +|**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. 958 958 959 -The 5V output time can be controlled by AT Command. 960 960 961 - **AT+5VT=1000**1203 += 4. Case Study = 962 962 963 - Meansset5Vvalidtimeto have1000ms. So,thereal5Voutputwillactually have 1000ms + samplingtimeforothersensors.1205 +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]] 964 964 965 965 966 - Bydefault, the AT+5VT=0.If the externalsensorwhichrequire 5v and require more time to get stable state, user can use this commandto increase the power ON duration for this sensor.1208 += 5. Use AT Command = 967 967 1210 +== 5.1 Access AT Command == 968 968 1212 +((( 1213 +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. 1214 +))) 969 969 1216 +[[image:1654162355560-817.png]] 970 970 971 -1. 972 -11. LEDs 973 973 974 -|**LEDs**|**Feature** 975 -|**LED1**|Blink when device transmit a packet. 1219 +((( 1220 +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: 1221 +))) 976 976 977 -1. 978 -11. Switch Jumper 1223 +[[image:1654162368066-342.png]] 979 979 980 -|**Switch Jumper**|**Feature** 981 -|**SW1**|((( 982 -ISP position: Upgrade firmware via UART 983 983 984 -Flash position: Configure device, check running status. 1226 +((( 1227 +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/]] 985 985 ))) 986 -|**SW2**|((( 987 -5V position: set to compatible with 5v I/O. 988 988 989 -3.3v position: set to compatible with 3.3v I/O., 990 -))) 991 991 992 -+3.3V: is always ON 993 993 994 - +5V:Onlyopen before every sampling.Thetime is bydefault, it is AT+5VT=0. Max opentime.5000 ms.1232 +== 5.2 Common AT Command Sequence == 995 995 996 - 1.CaseStudy1234 +=== 5.2.1 Multi-channel ABP mode (Use with SX1301/LG308) === 997 997 998 - Usercan checkthisURL forsomecasestudies.1236 +If device has not joined network yet: 999 999 1000 -[[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]] 1238 +(% class="box infomessage" %) 1239 +((( 1240 +**AT+FDR** 1241 +))) 1001 1001 1243 +(% class="box infomessage" %) 1244 +((( 1245 +**AT+NJM=0** 1246 +))) 1002 1002 1248 +(% class="box infomessage" %) 1249 +((( 1250 +**ATZ** 1251 +))) 1003 1003 1004 1004 1005 -1. Use AT Command 1006 -11. Access AT Command 1254 +If device already joined network: 1007 1007 1008 -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. 1256 +(% class="box infomessage" %) 1257 +((( 1258 +**AT+NJM=0** 1259 +))) 1009 1009 1010 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image027.png]] 1261 +(% class="box infomessage" %) 1262 +((( 1263 +**ATZ** 1264 +))) 1011 1011 1012 1012 1013 - InPC,User needs to set **serialtool**(suchs [[putty>>url:https://www.chiark.greenend.org.uk/~~sgtatham/putty/latest.html]],SecureCRT)baudrateto **9600** to access to accessserial console of RS485-BL. Thedefault password is123456.Below is the output for reference:1267 +=== 5.5.2 Single-channel ABP mode (Use with LG01/LG02) === 1014 1014 1015 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image028.png]] 1016 1016 1270 +(% style="background-color:#dcdcdc" %)**AT+FDR** (%%) Reset Parameters to Factory Default, Keys Reserve 1017 1017 1272 +(% style="background-color:#dcdcdc" %)**AT+NJM=0 **(%%)Set to ABP mode 1018 1018 1019 - MoredetailAT Commandmanualanbefound at[[AT CommandManual>>path:#AT_COMMAND]]1274 +(% style="background-color:#dcdcdc" %)**AT+ADR=0** (%%)Set the Adaptive Data Rate Off 1020 1020 1276 +(% style="background-color:#dcdcdc" %)**AT+DR=5** (%%)Set Data Rate 1021 1021 1278 +(% style="background-color:#dcdcdc" %)**AT+TDC=60000** (%%) Set transmit interval to 60 seconds 1022 1022 1023 -1. 1024 -11. Common AT Command Sequence 1025 -111. Multi-channel ABP mode (Use with SX1301/LG308) 1280 +(% style="background-color:#dcdcdc" %)**AT+CHS=868400000**(%%) Set transmit frequency to 868.4Mhz 1026 1026 1027 - Ifdevicehasnotjoinednetworkyet:1282 +(% style="background-color:#dcdcdc" %)**AT+RX2FQ=868400000** (%%) Set RX2Frequency to 868.4Mhz (according to the result from server) 1028 1028 1029 -AT+ FDR1284 +(% style="background-color:#dcdcdc" %)**AT+RX2DR=5** (%%) Set RX2DR to match the downlink DR from server. see below 1030 1030 1031 -AT+ NJM=01286 +(% 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. 1032 1032 1033 -ATZ 1288 +(% style="background-color:#dcdcdc" %)**ATZ** (%%) Reset MCU 1034 1034 1035 1035 1036 - Ifdevice alreadyjoined network:1291 +(% style="color:red" %)**Note:** 1037 1037 1038 -AT+NJM=0 1293 +(% style="color:red" %)1. Make sure the device is set to ABP mode in the IoT Server. 1294 +2. Make sure the LG01/02 gateway RX frequency is exactly the same as AT+CHS setting. 1295 +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. 1296 +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 1039 1039 1040 - ATZ1298 +[[image:1654162478620-421.png]] 1041 1041 1042 -1. 1043 -11. 1044 -111. Single-channel ABP mode (Use with LG01/LG02) 1045 1045 1046 - AT+FDRResetParameters toFactoryDefault, Keys Reserve1301 += 6. FAQ = 1047 1047 1048 - AT+NJM=0SettoABPmode1303 +== 6.1 How to upgrade the image? == 1049 1049 1050 -AT+ADR=0 Set the Adaptive Data Rate Off 1305 +((( 1306 +The RS485-LN LoRaWAN Controller is shipped with a 3.5mm cable, the cable is used to upload image to RS485-LN to: 1307 +))) 1051 1051 1052 -AT+DR=5 Set Data Rate 1309 +* ((( 1310 +Support new features 1311 +))) 1312 +* ((( 1313 +For bug fix 1314 +))) 1315 +* ((( 1316 +Change LoRaWAN bands. 1317 +))) 1053 1053 1054 -AT+TDC=60000 Set transmit interval to 60 seconds 1319 +((( 1320 +Below shows the hardware connection for how to upload an image to RS485-LN: 1321 +))) 1055 1055 1056 - AT+CHS=868400000 Set transmit frequency to868.4Mhz1323 +[[image:1654162535040-878.png]] 1057 1057 1058 - AT+RX2FQ=868400000SetRX2Frequencyto868.4Mhz(accordingtoheresultver)1325 +**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]]. 1059 1059 1060 - AT+RX2DR=5SetRX2DRtomatchthe downlink DRfrom server.see below1327 +**Step2**: Download the [[LT Image files>>url:http://www.dragino.com/downloads/index.php?dir=LT_LoRa_IO_Controller/LT33222-L/image/]]. 1061 1061 1062 - AT+DADDR=26 01 1A F1SetDeviceAddressto 26 01 1A F1, thisID can befound intheLoRa Server portal.1329 +**Step3: **Open flashloader; choose the correct COM port to update. 1063 1063 1064 -ATZ Reset MCU 1331 +((( 1332 +((( 1333 +(% 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. 1334 +))) 1335 +))) 1065 1065 1066 -**Note:** 1067 1067 1068 -1. Make sure the device is set to ABP mode in the IoT Server. 1069 -1. Make sure the LG01/02 gateway RX frequency is exactly the same as AT+CHS setting. 1070 -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. 1071 -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 1338 +[[image:image-20220602175818-12.png]] 1072 1072 1073 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image029.png]] 1074 1074 1341 +[[image:image-20220602175848-13.png]] 1075 1075 1076 -1. FAQ 1077 -11. How to upgrade the image? 1078 1078 1079 - The RS485-BL LoRaWAN Controlleris shipped with a 3.5mm cable, the cableis used to upload imageto RS485-BL to:1344 +[[image:image-20220602175912-14.png]] 1080 1080 1081 -* Support new features 1082 -* For bug fix 1083 -* Change LoRaWAN bands. 1084 1084 1085 - Belowshows thehardware connection forhowto uploadanimageto RS485-BL:1347 +**Notice**: In case user has lost the program cable. User can hand made one from a 3.5mm cable. The pin mapping is: 1086 1086 1087 -[[image: file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image030.png]]1349 +[[image:image-20220602175638-10.png]] 1088 1088 1089 -**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]]. 1090 1090 1091 - **Step2**:Downloadthe[[LT Imagefiles>>url:http://www.dragino.com/downloads/index.php?dir=LT_LoRa_IO_Controller/LT33222-L/image/]].1352 +== 6.2 How to change the LoRa Frequency Bands/Region? == 1092 1092 1093 - **Step3:**Openflashloader;choose thecorrectCOMportto update.1354 +User can follow the introduction for [[how to upgrade image>>||anchor="H6.1Howtoupgradetheimage3F"]]. When download the images, choose the required image file for download. 1094 1094 1095 1095 1096 -|((( 1097 -HOLD PRO then press the RST button, SYS will be ON, then click next 1098 -))) 1357 +== 6.3 How many RS485-Slave can RS485-BL connects? == 1099 1099 1100 -|((( 1101 -Board detected 1102 -))) 1359 +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"]]. 1103 1103 1104 -|((( 1105 - 1106 -))) 1107 1107 1108 - [[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]]1362 +== 6.4 Compatible question to ChirpStack and TTI LoRaWAN server ? == 1109 1109 1364 +When user need to use with ChirpStack or TTI. Please set AT+RPL=4. 1110 1110 1366 +Detail info check this link: [[Set Packet Receiving Response Level>>doc:Main.End Device AT Commands and Downlink Command.WebHome||anchor="H7.23SetPacketReceivingResponseLevel"]] 1111 1111 1112 -[[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]] 1113 1113 1369 += 7. Trouble Shooting = 1114 1114 1115 - [[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]]1371 +== 7.1 Downlink doesn’t work, how to solve it? == 1116 1116 1373 +Please see this link for debug: [[LoRaWAN Communication Debug>>doc:Main.LoRaWAN Communication Debug.WebHome]] 1117 1117 1118 -1. 1119 -11. How to change the LoRa Frequency Bands/Region? 1120 1120 1121 - Usercanfollow theintroductionfor[[howto upgradeimage>>path:#upgrade_image]]. Whendownloadtheimages, choose the required image file for download.1376 +== 7.2 Why I can’t join TTN V3 in US915 /AU915 bands? == 1122 1122 1378 +It might about the channels mapping. Please see for detail: [[Notice of Frequency band>>doc:Main.LoRaWAN Communication Debug.WebHome||anchor="H2.NoticeofUS9152FCN4702FAU915Frequencyband"]] 1123 1123 1124 1124 1125 -1. 1126 -11. How many RS485-Slave can RS485-BL connects? 1381 += 8. Order Info = 1127 1127 1128 - TheRS485-BL cansupportmax 32 RS485 devices. Each uplink commandof RS485-BL can support max 16 differentRS485command. So RS485-BLcan 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]].1383 +(% style="color:blue" %)**Part Number: RS485-LN-XXX** 1129 1129 1385 +(% style="color:blue" %)**XXX:** 1130 1130 1387 +* (% style="color:blue" %)**EU433**(%%): frequency bands EU433 1388 +* (% style="color:blue" %)**EU868**(%%): frequency bands EU868 1389 +* (% style="color:blue" %)**KR920**(%%): frequency bands KR920 1390 +* (% style="color:blue" %)**CN470**(%%): frequency bands CN470 1391 +* (% style="color:blue" %)**AS923**(%%): frequency bands AS923 1392 +* (% style="color:blue" %)**AU915**(%%): frequency bands AU915 1393 +* (% style="color:blue" %)**US915**(%%): frequency bands US915 1394 +* (% style="color:blue" %)**IN865**(%%): frequency bands IN865 1395 +* (% style="color:blue" %)**RU864**(%%): frequency bands RU864 1396 +* (% style="color:blue" %)**KZ865**(%%): frequency bands KZ865 1131 1131 1398 += 9.Packing Info = 1132 1132 1133 -1. Trouble Shooting 1134 -11. Downlink doesn’t work, how to solve it? 1135 1135 1136 -P leasesee this link fordebug:1401 +**Package Includes**: 1137 1137 1138 -[[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]] 1403 +* RS485-LN x 1 1404 +* Stick Antenna for LoRa RF part x 1 1405 +* Program cable x 1 1139 1139 1407 +**Dimension and weight**: 1140 1140 1409 +* Device Size: 13.5 x 7 x 3 cm 1410 +* Device Weight: 105g 1411 +* Package Size / pcs : 14.5 x 8 x 5 cm 1412 +* Weight / pcs : 170g 1141 1141 1142 -1. 1143 -11. Why I can’t join TTN V3 in US915 /AU915 bands? 1414 += 10. FCC Caution for RS485LN-US915 = 1144 1144 1145 -It might about the channels mapping. Please see for detail. 1416 +((( 1417 +Any Changes or modifications not expressly approved by the party responsible for compliance could void the user's authority to operate the equipment. 1418 +))) 1146 1146 1147 -[[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]] 1420 +((( 1421 +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. 1422 +))) 1148 1148 1424 +((( 1425 + 1426 +))) 1149 1149 1428 +((( 1429 +**IMPORTANT NOTE:** 1430 +))) 1150 1150 1151 -1. Order Info 1432 +((( 1433 +**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: 1434 +))) 1152 1152 1153 -**Part Number: RS485-BL-XXX** 1436 +((( 1437 +—Reorient or relocate the receiving antenna. 1438 +))) 1154 1154 1155 -**XXX:** 1440 +((( 1441 +—Increase the separation between the equipment and receiver. 1442 +))) 1156 1156 1157 -* **EU433**: frequency bands EU433 1158 -* **EU868**: frequency bands EU868 1159 -* **KR920**: frequency bands KR920 1160 -* **CN470**: frequency bands CN470 1161 -* **AS923**: frequency bands AS923 1162 -* **AU915**: frequency bands AU915 1163 -* **US915**: frequency bands US915 1164 -* **IN865**: frequency bands IN865 1165 -* **RU864**: frequency bands RU864 1166 -* **KZ865: **frequency bands KZ865 1444 +((( 1445 +—Connect the equipment into an outlet on a circuit different from that to which the receiver is connected. 1446 +))) 1167 1167 1168 -1. Packing Info 1448 +((( 1449 +—Consult the dealer or an experienced radio/TV technician for help. 1450 +))) 1169 1169 1170 -**Package Includes**: 1452 +((( 1453 + 1454 +))) 1171 1171 1172 - * RS485-BL x 11173 -* Stick AntennaforLoRaRF partx 11174 - * Program cable x 11456 +((( 1457 +**FCC Radiation Exposure Statement:** 1458 +))) 1175 1175 1176 -**Dimension and weight**: 1460 +((( 1461 +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. 1462 +))) 1177 1177 1178 -* Device Size: 13.5 x 7 x 3 cm 1179 -* Device Weight: 105g 1180 -* Package Size / pcs : 14.5 x 8 x 5 cm 1181 -* Weight / pcs : 170g 1182 1182 1183 -1. Support 1465 += 11. Support = 1184 1184 1185 -* 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. 1186 -* 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 1187 - 1188 -[[support@dragino.com>>url:file:///D:/市场资料/说明书/LoRa/LT系列/support@dragino.com]] 1467 +* ((( 1468 +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. 1469 +))) 1470 +* ((( 1471 +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]]. 1472 +)))
- 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