Skip to Content
Last modified by Xiaoling on 2025/04/23 15:57
From version 19.1
edited by Xiaoling
on 2022/05/23 10:01
Change comment: Uploaded new attachment "1653271276735-972.png", version {1}
To version 29.13
edited by Xiaoling
on 2022/06/01 18:02
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -7,12 +7,15 @@
7 7  **RS485-BL – Waterproof RS485 to LoRaWAN Converter User Manual**
8 8  
9 9  
10 +
10 10  **Table of Contents:**
11 11  
13 +{{toc/}}
12 12  
13 13  
14 14  
15 15  
18 +
16 16  = 1.Introduction =
17 17  
18 18  == 1.1 What is RS485-BL RS485 to LoRaWAN Converter ==
... ... @@ -90,6 +90,8 @@
90 90  * 127 dB Dynamic Range RSSI.
91 91  * Automatic RF Sense and CAD with ultra-fast AFC. ​​​
92 92  
96 +
97 +
93 93  == 1.3 Features ==
94 94  
95 95  * LoRaWAN Class A & Class C protocol (default Class A)
... ... @@ -101,6 +101,8 @@
101 101  * Support Modbus protocol
102 102  * Support Interrupt uplink
103 103  
109 +
110 +
104 104  == 1.4 Applications ==
105 105  
106 106  * Smart Buildings & Home Automation
... ... @@ -110,10 +110,13 @@
110 110  * Smart Cities
111 111  * Smart Factory
112 112  
120 +
121 +
113 113  == 1.5 Firmware Change log ==
114 114  
115 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);"]]
116 116  
126 +
117 117  == 1.6 Hardware Change log ==
118 118  
119 119  (((
... ... @@ -140,6 +140,8 @@
140 140  
141 141  (((
142 142  Release version ​​​​​
153 +
154 +
143 143  )))
144 144  
145 145  = 2. Pin mapping and Power ON Device =
... ... @@ -153,6 +153,7 @@
153 153  
154 154  The Left TXD and RXD are TTL interface for external sensor. TTL level is controlled by 3.3/5v Jumper.
155 155  
168 +
156 156  = 3. Operation Mode =
157 157  
158 158  == 3.1 How it works? ==
... ... @@ -159,6 +159,8 @@
159 159  
160 160  (((
161 161  The RS485-BL is configured as LoRaWAN OTAA Class A 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-BL. It will auto join the network via OTAA.
175 +
176 +
162 162  )))
163 163  
164 164  == 3.2 Example to join LoRaWAN network ==
... ... @@ -222,7 +222,9 @@
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.
240 +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>>||anchor="H3.5ConfigureRS485-BLviaATorDownlink"]] Command to configure how RS485-BL should read the sensor and how to handle the return from RS485 or TTL sensors.
241 +
242 +
226 226  )))
227 227  
228 228  === 3.3.1 onfigure UART settings for RS485 or TTL communication ===
... ... @@ -397,7 +397,7 @@
397 397  
398 398  **AT+COMMANDx : **This command will be sent to RS485/TTL devices during each sampling, Max command length is 14 bytes. The grammar is:
399 399  
400 -(% border="1" class="table-bordered" style="background-color:#ffffcc; color:green; width:501px" %)
417 +(% border="1" class="table-bordered" style="background-color:#4f81bd; color:white; width:501px" %)
401 401  |(% style="width:498px" %)(((
402 402  **AT+COMMANDx=xx xx xx xx xx xx xx xx xx xx xx xx,m**
403 403  
... ... @@ -412,7 +412,7 @@
412 412  
413 413  **AT+SEARCHx**: This command defines how to handle the return from AT+COMMANDx.
414 414  
415 -(% border="1" class="table-bordered" style="background-color:#ffffcc; color:green; width:580px" %)
432 +(% border="1" class="table-bordered" style="background-color:#4f81bd; color:white; width:580px" %)
416 416  |(% style="width:577px" %)(((
417 417  **AT+SEARCHx=aa,xx xx xx xx xx**
418 418  
... ... @@ -430,7 +430,6 @@
430 430  
431 431  [[image:1653271044481-711.png]]
432 432  
433 -
434 434  1. For a return string from AT+COMMAND1:  16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
435 435  
436 436  If we set AT+SEARCH1=2, 1E 56 34+31 00 49
... ... @@ -437,12 +437,12 @@
437 437  
438 438  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**
439 439  
440 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image014.png]]
456 +[[image:1653271276735-972.png]]
441 441  
442 -
443 443  **AT+DATACUTx : **This command defines how to handle the return from AT+COMMANDx, max return length is 45 bytes.
444 444  
445 -|(((
460 +(% style="background-color:#4f81bd; color:white; width:729px" %)
461 +|(% style="width:726px" %)(((
446 446  **AT+DATACUTx=a,b,c**
447 447  
448 448  * **a: length for the return of AT+COMMAND**
... ... @@ -454,95 +454,130 @@
454 454  
455 455  * Grab bytes:
456 456  
457 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image015.png]]
473 +[[image:1653271581490-837.png||height="313" width="722"]]
458 458  
459 459  * Grab a section.
460 460  
461 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image016.png]]
477 +[[image:1653271648378-342.png||height="326" width="720"]]
462 462  
463 463  * Grab different sections.
464 464  
465 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image017.png]]
481 +[[image:1653271657255-576.png||height="305" width="730"]]
466 466  
483 +(((
484 +(% style="color:red" %)**Note:**
485 +)))
467 467  
468 -Note:
469 -
487 +(((
470 470  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.
489 +)))
471 471  
472 -Example:
491 +(((
492 +**Example:**
493 +)))
473 473  
474 -AT+COMMAND1=11 01 1E D0,0
495 +(((
496 +(% style="color:red" %)AT+COMMAND1=11 01 1E D0,0
497 +)))
475 475  
476 -AT+SEARCH1=1,1E 56 34
499 +(((
500 +(% style="color:red" %)AT+SEARCH1=1,1E 56 34
501 +)))
477 477  
478 -AT+DATACUT1=0,2,1~~5
503 +(((
504 +(% style="color:red" %)AT+DATACUT1=0,2,1~~5
505 +)))
479 479  
480 -Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
507 +(((
508 +(% style="color:red" %)Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
509 +)))
481 481  
482 -String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49
511 +(((
512 +(% style="color:red" %)String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49
513 +)))
483 483  
484 -Valid payload after DataCUT command: 2e 30 58 5f 36
515 +(((
516 +(% style="color:red" %)Valid payload after DataCUT command: 2e 30 58 5f 36
517 +)))
485 485  
486 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image018.png]]
519 +[[image:1653271763403-806.png]]
487 487  
521 +=== 3.3.4 Compose the uplink payload ===
488 488  
489 -
490 -
491 -1.
492 -11.
493 -111. Compose the uplink payload
494 -
523 +(((
495 495  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.**
525 +)))
496 496  
527 +(((
528 +(% style="color:#4f81bd" %)**Examples: AT+DATAUP=0**
529 +)))
497 497  
498 -**Examples: AT+DATAUP=0**
531 +(((
532 +Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**A SIGNLE UPLINK**.
533 +)))
499 499  
500 -Compose the uplink payload with value returns in sequence and send with **A SIGNLE UPLINK**.
501 -
535 +(((
502 502  Final Payload is
537 +)))
503 503  
504 -Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx
539 +(((
540 +(% style="color:#4f81bd" %)Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx
541 +)))
505 505  
543 +(((
506 506  Where PAYVER is defined by AT+PAYVER, below is an example screen shot.
545 +)))
507 507  
508 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image019.png]]
547 +[[image:1653272787040-634.png||height="515" width="719"]]
509 509  
549 +(((
550 +(% style="color:#4f81bd" %)**Examples: AT+DATAUP=1**
551 +)))
510 510  
553 +(((
554 +Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**Multiply UPLINKs**.
555 +)))
511 511  
512 -**Examples: AT+DATAUP=1**
513 -
514 -Compose the uplink payload with value returns in sequence and send with **Multiply UPLINKs**.
515 -
557 +(((
516 516  Final Payload is
559 +)))
517 517  
518 -Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA
561 +(((
562 +(% style="color:#4f81bd" %)Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA
563 +)))
519 519  
520 -1. Battery Info (2 bytes): Battery voltage
521 -1. PAYVER (1 byte): Defined by AT+PAYVER
522 -1. PAYLOAD COUNT (1 byte): Total how many uplinks of this sampling.
523 -1. PAYLOAD# (1 byte): Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT)
524 -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
565 +1. (((
566 +Battery Info (2 bytes): Battery voltage
567 +)))
568 +1. (((
569 +PAYVER (1 byte): Defined by AT+PAYVER
570 +)))
571 +1. (((
572 +PAYLOAD COUNT (1 byte): Total how many uplinks of this sampling.
573 +)))
574 +1. (((
575 +PAYLOAD# (1 byte): Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT)
576 +)))
577 +1. (((
578 +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
579 +)))
525 525  
526 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image020.png]]
581 +[[image:1653272817147-600.png||height="437" width="717"]]
527 527  
528 -
529 529  So totally there will be 3 uplinks for this sampling, each uplink includes 6 bytes DATA
530 530  
531 -DATA1=RETURN1 Valid Value = 20 20 0a 33 90 41
585 +DATA1=RETURN1 Valid Value = (% style="background-color:#4f81bd; color:white" %) 20 20 0a 33 90 41
532 532  
533 -DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10= 02 aa 05 81 0a 20
587 +DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10= (% style="background-color:#4f81bd; color:white" %)02 aa 05 81 0a 20
534 534  
535 -DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 = 20 20 20 2d 30
589 +DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 =(% style="background-color:#4f81bd; color:white" %) 20 20 20 2d 30
536 536  
537 -
538 -
539 539  Below are the uplink payloads:
540 540  
541 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image021.png]]
593 +[[image:1653272901032-107.png]]
542 542  
595 +(% style="color:red" %)Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:
543 543  
544 -Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:
545 -
546 546   ~* For AU915/AS923 bands, if UplinkDwell time=0, max 51 bytes for each uplink ( so 51 -5 = 46 max valid date)
547 547  
548 548   * For AU915/AS923 bands, if UplinkDwell time=1, max 11 bytes for each uplink ( so 11 -5 = 6 max valid date).
... ... @@ -551,90 +551,121 @@
551 551  
552 552   ~* For all other bands: max 51 bytes for each uplink  ( so 51 -5 = 46 max valid date).
553 553  
605 +=== 3.3.5 Uplink on demand ===
554 554  
555 -
556 -1.
557 -11.
558 -111. Uplink on demand
559 -
607 +(((
560 560  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.
609 +)))
561 561  
611 +(((
562 562  Downlink control command:
613 +)))
563 563  
564 -[[0x08 command>>path:#downlink_08]]: Poll an uplink with current command set in RS485-BL.
615 +(((
616 +**0x08 command**: Poll an uplink with current command set in RS485-BL.
617 +)))
565 565  
566 -[[0xA8 command>>path:#downlink_A8]]: Send a command to RS485-BL and uplink the output from sensors.
619 +(((
620 +**0xA8 command**: Send a command to RS485-BL and uplink the output from sensors.
621 +)))
567 567  
623 +=== 3.3.6 Uplink on Interrupt ===
568 568  
625 +Put the interrupt sensor between 3.3v_out and GPIO ext.
569 569  
570 -1.
571 -11.
572 -111. Uplink on Interrupt
627 +[[image:1653273818896-432.png]]
573 573  
574 -Put the interrupt sensor between 3.3v_out and GPIO ext.[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image022.png]]
575 -
629 +(((
576 576  AT+INTMOD=0  Disable Interrupt
631 +)))
577 577  
633 +(((
578 578  AT+INTMOD=1  Interrupt trigger by rising or falling edge.
635 +)))
579 579  
637 +(((
580 580  AT+INTMOD=2  Interrupt trigger by falling edge. ( Default Value)
639 +)))
581 581  
641 +(((
582 582  AT+INTMOD=3  Interrupt trigger by rising edge.
643 +)))
583 583  
645 +== 3.4 Uplink Payload ==
584 584  
585 -1.
586 -11. Uplink Payload
587 -
588 -|**Size(bytes)**|**2**|**1**|**Length depends on the return from the commands**
589 -|Value|(((
647 +(% border="1" style="background-color:#4f81bd; color:white; width:850px" %)
648 +|**Size(bytes)**|(% style="width:130px" %)**2**|(% style="width:93px" %)**1**|(% style="width:509px" %)**Length depends on the return from the commands**
649 +|Value|(% style="width:130px" %)(((
650 +(((
590 590  Battery(mV)
652 +)))
591 591  
654 +(((
592 592  &
656 +)))
593 593  
658 +(((
594 594  Interrupt _Flag
595 -)))|(((
660 +)))
661 +)))|(% style="width:93px" %)(((
596 596  PAYLOAD_VER
597 597  
598 598  
599 -)))|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.
665 +)))|(% style="width:509px" %)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.
600 600  
601 601  Below is the decoder for the first 3 bytes. The rest bytes are dynamic depends on different RS485 sensors.
602 602  
603 -
669 +(((
604 604  function Decoder(bytes, port) {
671 +)))
605 605  
673 +(((
606 606  ~/~/Payload Formats of RS485-BL Deceive
675 +)))
607 607  
677 +(((
608 608  return {
679 +)))
609 609  
681 +(((
610 610   ~/~/Battery,units:V
683 +)))
611 611  
685 +(((
612 612   BatV:((bytes[0]<<8 | bytes[1])&0x7fff)/1000,
687 +)))
613 613  
689 +(((
614 614   ~/~/GPIO_EXTI 
691 +)))
615 615  
693 +(((
616 616   EXTI_Trigger:(bytes[0] & 0x80)? "TRUE":"FALSE",
695 +)))
617 617  
697 +(((
618 618   ~/~/payload of version
699 +)))
619 619  
701 +(((
620 620   Pay_ver:bytes[2],
703 +)))
621 621  
705 +(((
622 622   };
707 +)))
623 623  
709 +(((
624 624   }
711 +)))
625 625  
626 -
627 -
628 -
629 -
630 -
631 -
713 +(((
632 632  TTN V3 uplink screen shot.
715 +)))
633 633  
634 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png]]
717 +[[image:1653274001211-372.png||height="192" width="732"]]
635 635  
636 -1.
637 -11. Configure RS485-BL via AT or Downlink
719 +== 3.5 Configure RS485-BL via AT or Downlink ==
638 638  
639 639  User can configure RS485-BL via [[AT Commands >>path:#_​Using_the_AT]]or LoRaWAN Downlink Commands
640 640  
1653271581490-837.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +138.7 KB
Content
1653271648378-342.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +131.4 KB
Content
1653271657255-576.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +142.6 KB
Content
1653271763403-806.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +27.7 KB
Content
1653272787040-634.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +294.0 KB
Content
1653272817147-600.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +143.3 KB
Content
1653272901032-107.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +197.8 KB
Content
1653273818896-432.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +31.6 KB
Content
1653274001211-372.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +91.4 KB
Content