Skip to Content
Last modified by Xiaoling on 2025/04/23 15:57
From version 21.1
edited by Xiaoling
on 2022/05/23 10:06
Change comment: Uploaded new attachment "1653271581490-837.png", version {1}
To version 29.9
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 ==
... ... @@ -140,6 +140,8 @@
140 140  
141 141  (((
142 142  Release version ​​​​​
146 +
147 +
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  
161 +
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.
168 +
169 +
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.
233 +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.
234 +
235 +
226 226  )))
227 227  
228 228  === 3.3.1 onfigure UART settings for RS485 or TTL communication ===
... ... @@ -438,10 +438,10 @@
438 438  
439 439  [[image:1653271276735-972.png]]
440 440  
441 -
442 442  **AT+DATACUTx : **This command defines how to handle the return from AT+COMMANDx, max return length is 45 bytes.
443 443  
444 -|(((
453 +(% style="background-color:#4f81bd; color:white; width:729px" %)
454 +|(% style="width:726px" %)(((
445 445  **AT+DATACUTx=a,b,c**
446 446  
447 447  * **a: length for the return of AT+COMMAND**
... ... @@ -453,95 +453,130 @@
453 453  
454 454  * Grab bytes:
455 455  
456 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image015.png]]
466 +[[image:1653271581490-837.png||height="313" width="722"]]
457 457  
458 458  * Grab a section.
459 459  
460 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image016.png]]
470 +[[image:1653271648378-342.png||height="326" width="720"]]
461 461  
462 462  * Grab different sections.
463 463  
464 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image017.png]]
474 +[[image:1653271657255-576.png||height="305" width="730"]]
465 465  
476 +(((
477 +(% style="color:red" %)**Note:**
478 +)))
466 466  
467 -Note:
468 -
480 +(((
469 469  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.
482 +)))
470 470  
471 -Example:
484 +(((
485 +**Example:**
486 +)))
472 472  
473 -AT+COMMAND1=11 01 1E D0,0
488 +(((
489 +(% style="color:red" %)AT+COMMAND1=11 01 1E D0,0
490 +)))
474 474  
475 -AT+SEARCH1=1,1E 56 34
492 +(((
493 +(% style="color:red" %)AT+SEARCH1=1,1E 56 34
494 +)))
476 476  
477 -AT+DATACUT1=0,2,1~~5
496 +(((
497 +(% style="color:red" %)AT+DATACUT1=0,2,1~~5
498 +)))
478 478  
479 -Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
500 +(((
501 +(% style="color:red" %)Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
502 +)))
480 480  
481 -String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49
504 +(((
505 +(% style="color:red" %)String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49
506 +)))
482 482  
483 -Valid payload after DataCUT command: 2e 30 58 5f 36
508 +(((
509 +(% style="color:red" %)Valid payload after DataCUT command: 2e 30 58 5f 36
510 +)))
484 484  
485 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image018.png]]
512 +[[image:1653271763403-806.png]]
486 486  
514 +=== 3.3.4 Compose the uplink payload ===
487 487  
488 -
489 -
490 -1.
491 -11.
492 -111. Compose the uplink payload
493 -
516 +(((
494 494  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.**
518 +)))
495 495  
520 +(((
521 +(% style="color:#4f81bd" %)**Examples: AT+DATAUP=0**
522 +)))
496 496  
497 -**Examples: AT+DATAUP=0**
524 +(((
525 +Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**A SIGNLE UPLINK**.
526 +)))
498 498  
499 -Compose the uplink payload with value returns in sequence and send with **A SIGNLE UPLINK**.
500 -
528 +(((
501 501  Final Payload is
530 +)))
502 502  
503 -Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx
532 +(((
533 +(% style="color:#4f81bd" %)Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx
534 +)))
504 504  
536 +(((
505 505  Where PAYVER is defined by AT+PAYVER, below is an example screen shot.
538 +)))
506 506  
507 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image019.png]]
540 +[[image:1653272787040-634.png||height="515" width="719"]]
508 508  
542 +(((
543 +(% style="color:#4f81bd" %)**Examples: AT+DATAUP=1**
544 +)))
509 509  
546 +(((
547 +Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**Multiply UPLINKs**.
548 +)))
510 510  
511 -**Examples: AT+DATAUP=1**
512 -
513 -Compose the uplink payload with value returns in sequence and send with **Multiply UPLINKs**.
514 -
550 +(((
515 515  Final Payload is
552 +)))
516 516  
517 -Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA
554 +(((
555 +(% style="color:#4f81bd" %)Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA
556 +)))
518 518  
519 -1. Battery Info (2 bytes): Battery voltage
520 -1. PAYVER (1 byte): Defined by AT+PAYVER
521 -1. PAYLOAD COUNT (1 byte): Total how many uplinks of this sampling.
522 -1. PAYLOAD# (1 byte): Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT)
523 -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
558 +1. (((
559 +Battery Info (2 bytes): Battery voltage
560 +)))
561 +1. (((
562 +PAYVER (1 byte): Defined by AT+PAYVER
563 +)))
564 +1. (((
565 +PAYLOAD COUNT (1 byte): Total how many uplinks of this sampling.
566 +)))
567 +1. (((
568 +PAYLOAD# (1 byte): Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT)
569 +)))
570 +1. (((
571 +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
572 +)))
524 524  
525 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image020.png]]
574 +[[image:1653272817147-600.png||height="437" width="717"]]
526 526  
527 -
528 528  So totally there will be 3 uplinks for this sampling, each uplink includes 6 bytes DATA
529 529  
530 -DATA1=RETURN1 Valid Value = 20 20 0a 33 90 41
578 +DATA1=RETURN1 Valid Value = (% style="background-color:#4f81bd; color:white" %) 20 20 0a 33 90 41
531 531  
532 -DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10= 02 aa 05 81 0a 20
580 +DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10= (% style="background-color:#4f81bd; color:white" %)02 aa 05 81 0a 20
533 533  
534 -DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 = 20 20 20 2d 30
582 +DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 =(% style="background-color:#4f81bd; color:white" %) 20 20 20 2d 30
535 535  
536 -
537 -
538 538  Below are the uplink payloads:
539 539  
540 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image021.png]]
586 +[[image:1653272901032-107.png]]
541 541  
588 +(% style="color:red" %)Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:
542 542  
543 -Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:
544 -
545 545   ~* For AU915/AS923 bands, if UplinkDwell time=0, max 51 bytes for each uplink ( so 51 -5 = 46 max valid date)
546 546  
547 547   * For AU915/AS923 bands, if UplinkDwell time=1, max 11 bytes for each uplink ( so 11 -5 = 6 max valid date).
... ... @@ -550,90 +550,121 @@
550 550  
551 551   ~* For all other bands: max 51 bytes for each uplink  ( so 51 -5 = 46 max valid date).
552 552  
598 +=== 3.3.5 Uplink on demand ===
553 553  
554 -
555 -1.
556 -11.
557 -111. Uplink on demand
558 -
600 +(((
559 559  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.
602 +)))
560 560  
604 +(((
561 561  Downlink control command:
606 +)))
562 562  
563 -[[0x08 command>>path:#downlink_08]]: Poll an uplink with current command set in RS485-BL.
608 +(((
609 +**0x08 command**: Poll an uplink with current command set in RS485-BL.
610 +)))
564 564  
565 -[[0xA8 command>>path:#downlink_A8]]: Send a command to RS485-BL and uplink the output from sensors.
612 +(((
613 +**0xA8 command**: Send a command to RS485-BL and uplink the output from sensors.
614 +)))
566 566  
616 +=== 3.3.6 Uplink on Interrupt ===
567 567  
618 +Put the interrupt sensor between 3.3v_out and GPIO ext.
568 568  
569 -1.
570 -11.
571 -111. Uplink on Interrupt
620 +[[image:1653273818896-432.png]]
572 572  
573 -Put the interrupt sensor between 3.3v_out and GPIO ext.[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image022.png]]
574 -
622 +(((
575 575  AT+INTMOD=0  Disable Interrupt
624 +)))
576 576  
626 +(((
577 577  AT+INTMOD=1  Interrupt trigger by rising or falling edge.
628 +)))
578 578  
630 +(((
579 579  AT+INTMOD=2  Interrupt trigger by falling edge. ( Default Value)
632 +)))
580 580  
634 +(((
581 581  AT+INTMOD=3  Interrupt trigger by rising edge.
636 +)))
582 582  
638 +== 3.4 Uplink Payload ==
583 583  
584 -1.
585 -11. Uplink Payload
586 -
587 -|**Size(bytes)**|**2**|**1**|**Length depends on the return from the commands**
588 -|Value|(((
640 +(% border="1" style="background-color:#4f81bd; color:white; width:850px" %)
641 +|**Size(bytes)**|(% style="width:130px" %)**2**|(% style="width:93px" %)**1**|(% style="width:509px" %)**Length depends on the return from the commands**
642 +|Value|(% style="width:130px" %)(((
643 +(((
589 589  Battery(mV)
645 +)))
590 590  
647 +(((
591 591  &
649 +)))
592 592  
651 +(((
593 593  Interrupt _Flag
594 -)))|(((
653 +)))
654 +)))|(% style="width:93px" %)(((
595 595  PAYLOAD_VER
596 596  
597 597  
598 -)))|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.
658 +)))|(% 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.
599 599  
600 600  Below is the decoder for the first 3 bytes. The rest bytes are dynamic depends on different RS485 sensors.
601 601  
602 -
662 +(((
603 603  function Decoder(bytes, port) {
664 +)))
604 604  
666 +(((
605 605  ~/~/Payload Formats of RS485-BL Deceive
668 +)))
606 606  
670 +(((
607 607  return {
672 +)))
608 608  
674 +(((
609 609   ~/~/Battery,units:V
676 +)))
610 610  
678 +(((
611 611   BatV:((bytes[0]<<8 | bytes[1])&0x7fff)/1000,
680 +)))
612 612  
682 +(((
613 613   ~/~/GPIO_EXTI 
684 +)))
614 614  
686 +(((
615 615   EXTI_Trigger:(bytes[0] & 0x80)? "TRUE":"FALSE",
688 +)))
616 616  
690 +(((
617 617   ~/~/payload of version
692 +)))
618 618  
694 +(((
619 619   Pay_ver:bytes[2],
696 +)))
620 620  
698 +(((
621 621   };
700 +)))
622 622  
702 +(((
623 623   }
704 +)))
624 624  
625 -
626 -
627 -
628 -
629 -
630 -
706 +(((
631 631  TTN V3 uplink screen shot.
708 +)))
632 632  
633 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png]]
710 +[[image:1653274001211-372.png||height="192" width="732"]]
634 634  
635 -1.
636 -11. Configure RS485-BL via AT or Downlink
712 +== 3.5 Configure RS485-BL via AT or Downlink ==
637 637  
638 638  User can configure RS485-BL via [[AT Commands >>path:#_​Using_the_AT]]or LoRaWAN Downlink Commands
639 639  
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