Skip to Content
Last modified by Xiaoling on 2025/04/23 15:57
From version 26.1
edited by Xiaoling
on 2022/05/23 10:26
Change comment: Uploaded new attachment "1653272817147-600.png", version {1}
To version 29.10
edited by Xiaoling
on 2022/06/01 18:01
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 ==
... ... @@ -114,6 +114,7 @@
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  
120 +
117 117  == 1.6 Hardware Change log ==
118 118  
119 119  (((
... ... @@ -140,6 +140,8 @@
140 140  
141 141  (((
142 142  Release version ​​​​​
147 +
148 +
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  
162 +
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.
169 +
170 +
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.
234 +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.
235 +
236 +
226 226  )))
227 227  
228 228  === 3.3.1 onfigure UART settings for RS485 or TTL communication ===
... ... @@ -501,64 +501,82 @@
501 501  
502 502  [[image:1653271763403-806.png]]
503 503  
515 +=== 3.3.4 Compose the uplink payload ===
504 504  
505 -
506 -
507 -1.
508 -11.
509 -111. Compose the uplink payload
510 -
517 +(((
511 511  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.**
519 +)))
512 512  
521 +(((
522 +(% style="color:#4f81bd" %)**Examples: AT+DATAUP=0**
523 +)))
513 513  
514 -**Examples: AT+DATAUP=0**
525 +(((
526 +Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**A SIGNLE UPLINK**.
527 +)))
515 515  
516 -Compose the uplink payload with value returns in sequence and send with **A SIGNLE UPLINK**.
517 -
529 +(((
518 518  Final Payload is
531 +)))
519 519  
520 -Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx
533 +(((
534 +(% style="color:#4f81bd" %)Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx
535 +)))
521 521  
537 +(((
522 522  Where PAYVER is defined by AT+PAYVER, below is an example screen shot.
539 +)))
523 523  
524 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image019.png]]
541 +[[image:1653272787040-634.png||height="515" width="719"]]
525 525  
543 +(((
544 +(% style="color:#4f81bd" %)**Examples: AT+DATAUP=1**
545 +)))
526 526  
547 +(((
548 +Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**Multiply UPLINKs**.
549 +)))
527 527  
528 -**Examples: AT+DATAUP=1**
529 -
530 -Compose the uplink payload with value returns in sequence and send with **Multiply UPLINKs**.
531 -
551 +(((
532 532  Final Payload is
553 +)))
533 533  
534 -Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA
555 +(((
556 +(% style="color:#4f81bd" %)Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA
557 +)))
535 535  
536 -1. Battery Info (2 bytes): Battery voltage
537 -1. PAYVER (1 byte): Defined by AT+PAYVER
538 -1. PAYLOAD COUNT (1 byte): Total how many uplinks of this sampling.
539 -1. PAYLOAD# (1 byte): Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT)
540 -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
559 +1. (((
560 +Battery Info (2 bytes): Battery voltage
561 +)))
562 +1. (((
563 +PAYVER (1 byte): Defined by AT+PAYVER
564 +)))
565 +1. (((
566 +PAYLOAD COUNT (1 byte): Total how many uplinks of this sampling.
567 +)))
568 +1. (((
569 +PAYLOAD# (1 byte): Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT)
570 +)))
571 +1. (((
572 +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
573 +)))
541 541  
542 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image020.png]]
575 +[[image:1653272817147-600.png||height="437" width="717"]]
543 543  
544 -
545 545  So totally there will be 3 uplinks for this sampling, each uplink includes 6 bytes DATA
546 546  
547 -DATA1=RETURN1 Valid Value = 20 20 0a 33 90 41
579 +DATA1=RETURN1 Valid Value = (% style="background-color:#4f81bd; color:white" %) 20 20 0a 33 90 41
548 548  
549 -DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10= 02 aa 05 81 0a 20
581 +DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10= (% style="background-color:#4f81bd; color:white" %)02 aa 05 81 0a 20
550 550  
551 -DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 = 20 20 20 2d 30
583 +DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 =(% style="background-color:#4f81bd; color:white" %) 20 20 20 2d 30
552 552  
553 -
554 -
555 555  Below are the uplink payloads:
556 556  
557 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image021.png]]
587 +[[image:1653272901032-107.png]]
558 558  
589 +(% style="color:red" %)Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:
559 559  
560 -Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:
561 -
562 562   ~* For AU915/AS923 bands, if UplinkDwell time=0, max 51 bytes for each uplink ( so 51 -5 = 46 max valid date)
563 563  
564 564   * For AU915/AS923 bands, if UplinkDwell time=1, max 11 bytes for each uplink ( so 11 -5 = 6 max valid date).
... ... @@ -567,90 +567,121 @@
567 567  
568 568   ~* For all other bands: max 51 bytes for each uplink  ( so 51 -5 = 46 max valid date).
569 569  
599 +=== 3.3.5 Uplink on demand ===
570 570  
571 -
572 -1.
573 -11.
574 -111. Uplink on demand
575 -
601 +(((
576 576  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.
603 +)))
577 577  
605 +(((
578 578  Downlink control command:
607 +)))
579 579  
580 -[[0x08 command>>path:#downlink_08]]: Poll an uplink with current command set in RS485-BL.
609 +(((
610 +**0x08 command**: Poll an uplink with current command set in RS485-BL.
611 +)))
581 581  
582 -[[0xA8 command>>path:#downlink_A8]]: Send a command to RS485-BL and uplink the output from sensors.
613 +(((
614 +**0xA8 command**: Send a command to RS485-BL and uplink the output from sensors.
615 +)))
583 583  
617 +=== 3.3.6 Uplink on Interrupt ===
584 584  
619 +Put the interrupt sensor between 3.3v_out and GPIO ext.
585 585  
586 -1.
587 -11.
588 -111. Uplink on Interrupt
621 +[[image:1653273818896-432.png]]
589 589  
590 -Put the interrupt sensor between 3.3v_out and GPIO ext.[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image022.png]]
591 -
623 +(((
592 592  AT+INTMOD=0  Disable Interrupt
625 +)))
593 593  
627 +(((
594 594  AT+INTMOD=1  Interrupt trigger by rising or falling edge.
629 +)))
595 595  
631 +(((
596 596  AT+INTMOD=2  Interrupt trigger by falling edge. ( Default Value)
633 +)))
597 597  
635 +(((
598 598  AT+INTMOD=3  Interrupt trigger by rising edge.
637 +)))
599 599  
639 +== 3.4 Uplink Payload ==
600 600  
601 -1.
602 -11. Uplink Payload
603 -
604 -|**Size(bytes)**|**2**|**1**|**Length depends on the return from the commands**
605 -|Value|(((
641 +(% border="1" style="background-color:#4f81bd; color:white; width:850px" %)
642 +|**Size(bytes)**|(% style="width:130px" %)**2**|(% style="width:93px" %)**1**|(% style="width:509px" %)**Length depends on the return from the commands**
643 +|Value|(% style="width:130px" %)(((
644 +(((
606 606  Battery(mV)
646 +)))
607 607  
648 +(((
608 608  &
650 +)))
609 609  
652 +(((
610 610  Interrupt _Flag
611 -)))|(((
654 +)))
655 +)))|(% style="width:93px" %)(((
612 612  PAYLOAD_VER
613 613  
614 614  
615 -)))|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.
659 +)))|(% 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.
616 616  
617 617  Below is the decoder for the first 3 bytes. The rest bytes are dynamic depends on different RS485 sensors.
618 618  
619 -
663 +(((
620 620  function Decoder(bytes, port) {
665 +)))
621 621  
667 +(((
622 622  ~/~/Payload Formats of RS485-BL Deceive
669 +)))
623 623  
671 +(((
624 624  return {
673 +)))
625 625  
675 +(((
626 626   ~/~/Battery,units:V
677 +)))
627 627  
679 +(((
628 628   BatV:((bytes[0]<<8 | bytes[1])&0x7fff)/1000,
681 +)))
629 629  
683 +(((
630 630   ~/~/GPIO_EXTI 
685 +)))
631 631  
687 +(((
632 632   EXTI_Trigger:(bytes[0] & 0x80)? "TRUE":"FALSE",
689 +)))
633 633  
691 +(((
634 634   ~/~/payload of version
693 +)))
635 635  
695 +(((
636 636   Pay_ver:bytes[2],
697 +)))
637 637  
699 +(((
638 638   };
701 +)))
639 639  
703 +(((
640 640   }
705 +)))
641 641  
642 -
643 -
644 -
645 -
646 -
647 -
707 +(((
648 648  TTN V3 uplink screen shot.
709 +)))
649 649  
650 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png]]
711 +[[image:1653274001211-372.png||height="192" width="732"]]
651 651  
652 -1.
653 -11. Configure RS485-BL via AT or Downlink
713 +== 3.5 Configure RS485-BL via AT or Downlink ==
654 654  
655 655  User can configure RS485-BL via [[AT Commands >>path:#_​Using_the_AT]]or LoRaWAN Downlink Commands
656 656  
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