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

Summary

Details

Page properties
Content
... ... @@ -18,19 +18,21 @@
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.
21 +The Dragino RS485-LN is a **RS485 to LoRaWAN Converter**. It converts the RS485 signal into LoRaWAN wireless signal which simplify the IoT installation and reduce the installation/maintaining cost.
22 22  )))
23 23  
24 24  (((
25 -RS485-LN allows user to monitor / control RS485 devices and reach extremely long ranges. It provides ultra-long range spread spectrum communication and high interference immunity whilst minimizing current consumption. It targets professional wireless sensor network applications such as irrigation systems, smart metering, smart cities, smartphone detection, building automation, and so on.
25 +RS485-LN allows user to **monitor / control RS485 devices** and reach extremely long ranges. It provides ultra-long range spread spectrum communication and high interference immunity whilst minimizing current consumption. It targets professional wireless sensor network applications such as irrigation systems, smart metering, smart cities, smartphone detection, building automation, and so on.
26 26  )))
27 27  
28 28  (((
29 -For data uplink, RS485-LN sends user-defined commands to RS485 devices and gets the return from the RS485 devices. RS485-LN will process these returns according to user-define rules to get the final payload and upload to LoRaWAN server.
29 +**For data uplink**, RS485-LN sends user-defined commands to RS485 devices and gets the return from the RS485 devices. RS485-LN will process these returns according to user-define rules to get the final payload and upload to LoRaWAN server.
30 30  )))
31 31  
32 32  (((
33 -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.
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.
34 +
35 +**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]]
34 34  )))
35 35  )))
36 36  
... ... @@ -206,18 +206,8 @@
206 206  
207 207  === 3.3.1 onfigure UART settings for RS485 or TTL communication ===
208 208  
209 -RS485-BL can connect to either RS485 sensors or TTL sensor. User need to specify what type of sensor need to connect.
211 +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 -**~1. RS485-MODBUS mode:**
212 -
213 -AT+MOD=1 ~/~/ Support RS485-MODBUS type sensors. User can connect multiply RS485 , Modbus sensors to the A / B pins.
214 -
215 -**2. TTL mode:**
216 -
217 -AT+MOD=2 ~/~/ Support TTL Level sensors, User can connect one TTL Sensor to the TXD/RXD/GND pins.
218 -
219 -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.
220 -
221 221  (% border="1" style="background-color:#ffffcc; color:green; width:795px" %)
222 222  |(((
223 223  **AT Commands**
... ... @@ -242,13 +242,7 @@
242 242  |(((
243 243  AT+PARITY
244 244  )))|(% style="width:285px" %)(((
245 -(((
246 246  Set UART parity (for RS485 connection)
247 -)))
248 -
249 -(((
250 -Default Value is: no parity.
251 -)))
252 252  )))|(% style="width:347px" %)(((
253 253  (((
254 254  AT+PARITY=0
... ... @@ -266,7 +266,7 @@
266 266  )))
267 267  
268 268  (((
269 -Default Value is: 1bit.
255 +
270 270  )))
271 271  )))|(% style="width:347px" %)(((
272 272  (((
... ... @@ -285,12 +285,10 @@
285 285  === 3.3.2 Configure sensors ===
286 286  
287 287  (((
288 -Some sensors might need to configure before normal operation. User can configure such sensor via PC or through RS485-BL AT Commands (% style="color:#4f81bd" %)**AT+CFGDEV**.
289 -)))
290 -
291 291  (((
292 -When user issue an (% style="color:#4f81bd" %)**AT+CFGDEV**(%%) command, Each (% style="color:#4f81bd" %)**AT+CFGDEV**(%%) equals to send a command to the RS485 or TTL sensors. This command will only run when user input it and won’t run during each sampling.
275 +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.
293 293  )))
277 +)))
294 294  
295 295  (% border="1" style="background-color:#ffffcc; color:green; width:806px" %)
296 296  |**AT Commands**|(% style="width:418px" %)**Description**|(% style="width:256px" %)**Example**
... ... @@ -302,8 +302,6 @@
302 302  mm: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
303 303  )))|(% style="width:256px" %)AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
304 304  
305 -Detail of AT+CFGDEV command see [[AT+CFGDEV detail>>path:#AT_CFGDEV]].
306 -
307 307  === 3.3.3 Configure read commands for each sampling ===
308 308  
309 309  (((
... ... @@ -385,11 +385,17 @@
385 385  **m: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command**
386 386  )))
387 387  
370 +(((
388 388  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.
372 +)))
389 389  
374 +(((
390 390  In the RS485-BL, we should use this command AT+COMMAND1=01 03 0B B8 00 02,1 for the same.
376 +)))
391 391  
378 +(((
392 392  **AT+SEARCHx**: This command defines how to handle the return from AT+COMMANDx.
380 +)))
393 393  
394 394  (% border="1" class="table-bordered" %)
395 395  |(((
... ... @@ -401,26 +401,24 @@
401 401  
402 402  )))
403 403  
404 -Examples:
392 +**Examples:**
405 405  
406 -1. For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
394 +~1. For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
407 407  
408 408  If we set AT+SEARCH1=1,1E 56 34.      (max 5 bytes for prefix)
409 409  
410 -The valid data will be all bytes after 1E 56 34 , so it is 2e 30 58 5f 36 41 30 31 00 49
398 +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**
411 411  
412 -[[image:1652954654347-831.png]]
400 +[[image:1653269403619-508.png]]
413 413  
402 +2. For a return string from AT+COMMAND1:  16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
414 414  
415 -1. For a return string from AT+COMMAND1:  16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
416 -
417 417  If we set AT+SEARCH1=2, 1E 56 34+31 00 49
418 418  
419 -Device will search the bytes between 1E 56 34 and 31 00 49. So it is 2e 30 58 5f 36 41 30
406 +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**
420 420  
421 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image014.png]]
408 +[[image:1653269438444-278.png]]
422 422  
423 -
424 424  **AT+DATACUTx : **This command defines how to handle the return from AT+COMMANDx, max return length is 45 bytes.
425 425  
426 426  |(((
... ... @@ -435,94 +435,95 @@
435 435  
436 436  * Grab bytes:
437 437  
438 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image015.png]]
424 +[[image:1653269551753-223.png||height="311" width="717"]]
439 439  
440 440  * Grab a section.
441 441  
442 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image016.png]]
428 +[[image:1653269568276-930.png||height="325" width="718"]]
443 443  
444 444  * Grab different sections.
445 445  
446 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image017.png]]
432 +[[image:1653269593172-426.png||height="303" width="725"]]
447 447  
434 +(% style="color:red" %)**Note:**
448 448  
449 -Note:
450 -
451 451  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.
452 452  
453 453  Example:
454 454  
455 -AT+COMMAND1=11 01 1E D0,0
440 +(% style="color:red" %)AT+COMMAND1=11 01 1E D0,0
456 456  
457 -AT+SEARCH1=1,1E 56 34
442 +(% style="color:red" %)AT+SEARCH1=1,1E 56 34
458 458  
459 -AT+DATACUT1=0,2,1~~5
444 +(% style="color:red" %)AT+DATACUT1=0,2,1~~5
460 460  
461 -Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
446 +(% style="color:red" %)Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
462 462  
463 -String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49
448 +(% style="color:red" %)String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49
464 464  
465 -Valid payload after DataCUT command: 2e 30 58 5f 36
450 +(% style="color:red" %)Valid payload after DataCUT command: 2e 30 58 5f 36
466 466  
467 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image018.png]]
452 +[[image:1653269618463-608.png]]
468 468  
454 +=== 3.3.4 Compose the uplink payload ===
469 469  
470 -
471 -
472 -1.
473 -11.
474 -111. Compose the uplink payload
475 -
456 +(((
476 476  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.**
458 +)))
477 477  
460 +(((
461 +(% style="color:#4f81bd" %)**Examples: AT+DATAUP=0**
462 +)))
478 478  
479 -**Examples: AT+DATAUP=0**
464 +(((
465 +Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**A SIGNLE UPLINK**.
466 +)))
480 480  
481 -Compose the uplink payload with value returns in sequence and send with **A SIGNLE UPLINK**.
482 -
468 +(((
483 483  Final Payload is
470 +)))
484 484  
485 -Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx
472 +(((
473 +(% style="color:#4f81bd" %)**Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx**
474 +)))
486 486  
476 +(((
487 487  Where PAYVER is defined by AT+PAYVER, below is an example screen shot.
478 +)))
488 488  
489 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image019.png]]
480 +[[image:1653269759169-150.png||height="513" width="716"]]
490 490  
482 +(% style="color:#4f81bd" %)**Examples: AT+DATAUP=1**
491 491  
484 +Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**Multiply UPLINKs**.
492 492  
493 -**Examples: AT+DATAUP=1**
494 -
495 -Compose the uplink payload with value returns in sequence and send with **Multiply UPLINKs**.
496 -
497 497  Final Payload is
498 498  
499 -Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA
488 +(% style="color:#4f81bd" %)**Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA**
500 500  
501 501  1. Battery Info (2 bytes): Battery voltage
502 502  1. PAYVER (1 byte): Defined by AT+PAYVER
503 503  1. PAYLOAD COUNT (1 byte): Total how many uplinks of this sampling.
504 504  1. PAYLOAD# (1 byte): Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT)
505 -1. DATA: Valid value: max 6 bytes(US915 version here, [[Notice*!>>path:#max_byte]]) for each uplink so each uplink <= 11 bytes. For the last uplink, DATA will might less than 6 bytes
494 +1. DATA: Valid value: max 6 bytes(US915 version here, Notice*!) for each uplink so each uplink <= 11 bytes. For the last uplink, DATA will might less than 6 bytes
506 506  
507 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image020.png]]
496 +[[image:1653269916228-732.png||height="433" width="711"]]
508 508  
509 509  
510 510  So totally there will be 3 uplinks for this sampling, each uplink includes 6 bytes DATA
511 511  
512 -DATA1=RETURN1 Valid Value = 20 20 0a 33 90 41
501 +DATA1=RETURN1 Valid Value = (% style="background-color:green; color:white" %)20 20 0a 33 90 41
513 513  
514 -DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10= 02 aa 05 81 0a 20
503 +DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10=(% style="background-color:green; color:white" %) 02 aa 05 81 0a 20
515 515  
516 -DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 = 20 20 20 2d 30
505 +DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 = (% style="background-color:green; color:white" %)20 20 20 2d 30
517 517  
518 -
519 -
520 520  Below are the uplink payloads:
521 521  
522 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image021.png]]
509 +[[image:1653270130359-810.png]]
523 523  
524 524  
525 -Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:
512 +(% style="color:red" %)**Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:**
526 526  
527 527   ~* For AU915/AS923 bands, if UplinkDwell time=0, max 51 bytes for each uplink ( so 51 -5 = 46 max valid date)
528 528  
... ... @@ -532,12 +532,8 @@
532 532  
533 533   ~* For all other bands: max 51 bytes for each uplink  ( so 51 -5 = 46 max valid date).
534 534  
522 +=== 3.3.5 Uplink on demand ===
535 535  
536 -
537 -1.
538 -11.
539 -111. Uplink on demand
540 -
541 541  Except uplink periodically, RS485-BL is able to uplink on demand. The server sends downlink command to RS485-BL and RS485 will uplink data base on the command.
542 542  
543 543  Downlink control command:
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
1653269551753-223.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +138.7 KB
Content
1653269568276-930.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +131.4 KB
Content
1653269593172-426.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +142.6 KB
Content
1653269618463-608.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +27.7 KB
Content
1653269759169-150.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +294.0 KB
Content
1653269916228-732.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +143.3 KB
Content
1653270130359-810.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +197.8 KB
Content

Applications

Navigation

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