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