Skip to Content
Last modified by Xiaoling on 2025/04/23 15:57
From version 17.2
edited by Xiaoling
on 2022/05/19 18:05
Change comment: There is no comment for this version
To version 29.7
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 ==
... ... @@ -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.
165 +
166 +
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.
230 +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.
231 +
232 +
226 226  )))
227 227  
228 228  === 3.3.1 onfigure UART settings for RS485 or TTL communication ===
... ... @@ -397,8 +397,8 @@
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" %)
401 -|(((
407 +(% border="1" class="table-bordered" style="background-color:#4f81bd; color:white; width:501px" %)
408 +|(% style="width:498px" %)(((
402 402  **AT+COMMANDx=xx xx xx xx xx xx xx xx xx xx xx xx,m**
403 403  
404 404  **xx xx xx xx xx xx xx xx xx xx xx xx: The RS485 command to be sent**
... ... @@ -412,39 +412,36 @@
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" %)
416 -|(((
422 +(% border="1" class="table-bordered" style="background-color:#4f81bd; color:white; width:580px" %)
423 +|(% style="width:577px" %)(((
417 417  **AT+SEARCHx=aa,xx xx xx xx xx**
418 418  
419 419  * **aa: 1: prefix match mode; 2: prefix and suffix match mode**
420 420  * **xx xx xx xx xx: match string. Max 5 bytes for prefix and 5 bytes for suffix**
421 -
422 -
423 423  )))
424 424  
425 -Examples:
430 +**Examples:**
426 426  
427 427  1. For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
428 428  
429 429  If we set AT+SEARCH1=1,1E 56 34.      (max 5 bytes for prefix)
430 430  
431 -The valid data will be all bytes after 1E 56 34 , so it is 2e 30 58 5f 36 41 30 31 00 49
436 +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**
432 432  
433 -[[image:1652954654347-831.png]]
438 +[[image:1653271044481-711.png]]
434 434  
435 -
436 436  1. For a return string from AT+COMMAND1:  16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
437 437  
438 438  If we set AT+SEARCH1=2, 1E 56 34+31 00 49
439 439  
440 -Device will search the bytes between 1E 56 34 and 31 00 49. So it is 2e 30 58 5f 36 41 30
444 +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**
441 441  
442 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image014.png]]
446 +[[image:1653271276735-972.png]]
443 443  
444 -
445 445  **AT+DATACUTx : **This command defines how to handle the return from AT+COMMANDx, max return length is 45 bytes.
446 446  
447 -|(((
450 +(% style="background-color:#4f81bd; color:white; width:729px" %)
451 +|(% style="width:726px" %)(((
448 448  **AT+DATACUTx=a,b,c**
449 449  
450 450  * **a: length for the return of AT+COMMAND**
... ... @@ -456,95 +456,130 @@
456 456  
457 457  * Grab bytes:
458 458  
459 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image015.png]]
463 +[[image:1653271581490-837.png||height="313" width="722"]]
460 460  
461 461  * Grab a section.
462 462  
463 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image016.png]]
467 +[[image:1653271648378-342.png||height="326" width="720"]]
464 464  
465 465  * Grab different sections.
466 466  
467 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image017.png]]
471 +[[image:1653271657255-576.png||height="305" width="730"]]
468 468  
473 +(((
474 +(% style="color:red" %)**Note:**
475 +)))
469 469  
470 -Note:
471 -
477 +(((
472 472  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.
479 +)))
473 473  
474 -Example:
481 +(((
482 +**Example:**
483 +)))
475 475  
476 -AT+COMMAND1=11 01 1E D0,0
485 +(((
486 +(% style="color:red" %)AT+COMMAND1=11 01 1E D0,0
487 +)))
477 477  
478 -AT+SEARCH1=1,1E 56 34
489 +(((
490 +(% style="color:red" %)AT+SEARCH1=1,1E 56 34
491 +)))
479 479  
480 -AT+DATACUT1=0,2,1~~5
493 +(((
494 +(% style="color:red" %)AT+DATACUT1=0,2,1~~5
495 +)))
481 481  
482 -Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
497 +(((
498 +(% style="color:red" %)Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
499 +)))
483 483  
484 -String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49
501 +(((
502 +(% style="color:red" %)String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49
503 +)))
485 485  
486 -Valid payload after DataCUT command: 2e 30 58 5f 36
505 +(((
506 +(% style="color:red" %)Valid payload after DataCUT command: 2e 30 58 5f 36
507 +)))
487 487  
488 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image018.png]]
509 +[[image:1653271763403-806.png]]
489 489  
511 +=== 3.3.4 Compose the uplink payload ===
490 490  
491 -
492 -
493 -1.
494 -11.
495 -111. Compose the uplink payload
496 -
513 +(((
497 497  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.**
515 +)))
498 498  
517 +(((
518 +(% style="color:#4f81bd" %)**Examples: AT+DATAUP=0**
519 +)))
499 499  
500 -**Examples: AT+DATAUP=0**
521 +(((
522 +Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**A SIGNLE UPLINK**.
523 +)))
501 501  
502 -Compose the uplink payload with value returns in sequence and send with **A SIGNLE UPLINK**.
503 -
525 +(((
504 504  Final Payload is
527 +)))
505 505  
506 -Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx
529 +(((
530 +(% style="color:#4f81bd" %)Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx
531 +)))
507 507  
533 +(((
508 508  Where PAYVER is defined by AT+PAYVER, below is an example screen shot.
535 +)))
509 509  
510 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image019.png]]
537 +[[image:1653272787040-634.png||height="515" width="719"]]
511 511  
539 +(((
540 +(% style="color:#4f81bd" %)**Examples: AT+DATAUP=1**
541 +)))
512 512  
543 +(((
544 +Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**Multiply UPLINKs**.
545 +)))
513 513  
514 -**Examples: AT+DATAUP=1**
515 -
516 -Compose the uplink payload with value returns in sequence and send with **Multiply UPLINKs**.
517 -
547 +(((
518 518  Final Payload is
549 +)))
519 519  
520 -Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA
551 +(((
552 +(% style="color:#4f81bd" %)Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA
553 +)))
521 521  
522 -1. Battery Info (2 bytes): Battery voltage
523 -1. PAYVER (1 byte): Defined by AT+PAYVER
524 -1. PAYLOAD COUNT (1 byte): Total how many uplinks of this sampling.
525 -1. PAYLOAD# (1 byte): Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT)
526 -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
555 +1. (((
556 +Battery Info (2 bytes): Battery voltage
557 +)))
558 +1. (((
559 +PAYVER (1 byte): Defined by AT+PAYVER
560 +)))
561 +1. (((
562 +PAYLOAD COUNT (1 byte): Total how many uplinks of this sampling.
563 +)))
564 +1. (((
565 +PAYLOAD# (1 byte): Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT)
566 +)))
567 +1. (((
568 +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
569 +)))
527 527  
528 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image020.png]]
571 +[[image:1653272817147-600.png||height="437" width="717"]]
529 529  
530 -
531 531  So totally there will be 3 uplinks for this sampling, each uplink includes 6 bytes DATA
532 532  
533 -DATA1=RETURN1 Valid Value = 20 20 0a 33 90 41
575 +DATA1=RETURN1 Valid Value = (% style="background-color:#4f81bd; color:white" %) 20 20 0a 33 90 41
534 534  
535 -DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10= 02 aa 05 81 0a 20
577 +DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10= (% style="background-color:#4f81bd; color:white" %)02 aa 05 81 0a 20
536 536  
537 -DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 = 20 20 20 2d 30
579 +DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 =(% style="background-color:#4f81bd; color:white" %) 20 20 20 2d 30
538 538  
539 -
540 -
541 541  Below are the uplink payloads:
542 542  
543 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image021.png]]
583 +[[image:1653272901032-107.png]]
544 544  
585 +(% style="color:red" %)Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:
545 545  
546 -Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:
547 -
548 548   ~* For AU915/AS923 bands, if UplinkDwell time=0, max 51 bytes for each uplink ( so 51 -5 = 46 max valid date)
549 549  
550 550   * For AU915/AS923 bands, if UplinkDwell time=1, max 11 bytes for each uplink ( so 11 -5 = 6 max valid date).
... ... @@ -553,90 +553,121 @@
553 553  
554 554   ~* For all other bands: max 51 bytes for each uplink  ( so 51 -5 = 46 max valid date).
555 555  
595 +=== 3.3.5 Uplink on demand ===
556 556  
557 -
558 -1.
559 -11.
560 -111. Uplink on demand
561 -
597 +(((
562 562  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.
599 +)))
563 563  
601 +(((
564 564  Downlink control command:
603 +)))
565 565  
566 -[[0x08 command>>path:#downlink_08]]: Poll an uplink with current command set in RS485-BL.
605 +(((
606 +**0x08 command**: Poll an uplink with current command set in RS485-BL.
607 +)))
567 567  
568 -[[0xA8 command>>path:#downlink_A8]]: Send a command to RS485-BL and uplink the output from sensors.
609 +(((
610 +**0xA8 command**: Send a command to RS485-BL and uplink the output from sensors.
611 +)))
569 569  
613 +=== 3.3.6 Uplink on Interrupt ===
570 570  
615 +Put the interrupt sensor between 3.3v_out and GPIO ext.
571 571  
572 -1.
573 -11.
574 -111. Uplink on Interrupt
617 +[[image:1653273818896-432.png]]
575 575  
576 -Put the interrupt sensor between 3.3v_out and GPIO ext.[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image022.png]]
577 -
619 +(((
578 578  AT+INTMOD=0  Disable Interrupt
621 +)))
579 579  
623 +(((
580 580  AT+INTMOD=1  Interrupt trigger by rising or falling edge.
625 +)))
581 581  
627 +(((
582 582  AT+INTMOD=2  Interrupt trigger by falling edge. ( Default Value)
629 +)))
583 583  
631 +(((
584 584  AT+INTMOD=3  Interrupt trigger by rising edge.
633 +)))
585 585  
635 +== 3.4 Uplink Payload ==
586 586  
587 -1.
588 -11. Uplink Payload
589 -
590 -|**Size(bytes)**|**2**|**1**|**Length depends on the return from the commands**
591 -|Value|(((
637 +(% border="1" style="background-color:#4f81bd; color:white; width:850px" %)
638 +|**Size(bytes)**|(% style="width:130px" %)**2**|(% style="width:93px" %)**1**|(% style="width:509px" %)**Length depends on the return from the commands**
639 +|Value|(% style="width:130px" %)(((
640 +(((
592 592  Battery(mV)
642 +)))
593 593  
644 +(((
594 594  &
646 +)))
595 595  
648 +(((
596 596  Interrupt _Flag
597 -)))|(((
650 +)))
651 +)))|(% style="width:93px" %)(((
598 598  PAYLOAD_VER
599 599  
600 600  
601 -)))|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.
655 +)))|(% 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.
602 602  
603 603  Below is the decoder for the first 3 bytes. The rest bytes are dynamic depends on different RS485 sensors.
604 604  
605 -
659 +(((
606 606  function Decoder(bytes, port) {
661 +)))
607 607  
663 +(((
608 608  ~/~/Payload Formats of RS485-BL Deceive
665 +)))
609 609  
667 +(((
610 610  return {
669 +)))
611 611  
671 +(((
612 612   ~/~/Battery,units:V
673 +)))
613 613  
675 +(((
614 614   BatV:((bytes[0]<<8 | bytes[1])&0x7fff)/1000,
677 +)))
615 615  
679 +(((
616 616   ~/~/GPIO_EXTI 
681 +)))
617 617  
683 +(((
618 618   EXTI_Trigger:(bytes[0] & 0x80)? "TRUE":"FALSE",
685 +)))
619 619  
687 +(((
620 620   ~/~/payload of version
689 +)))
621 621  
691 +(((
622 622   Pay_ver:bytes[2],
693 +)))
623 623  
695 +(((
624 624   };
697 +)))
625 625  
699 +(((
626 626   }
701 +)))
627 627  
628 -
629 -
630 -
631 -
632 -
633 -
703 +(((
634 634  TTN V3 uplink screen shot.
705 +)))
635 635  
636 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png]]
707 +[[image:1653274001211-372.png||height="192" width="732"]]
637 637  
638 -1.
639 -11. Configure RS485-BL via AT or Downlink
709 +== 3.5 Configure RS485-BL via AT or Downlink ==
640 640  
641 641  User can configure RS485-BL via [[AT Commands >>path:#_​Using_the_AT]]or LoRaWAN Downlink Commands
642 642  
1653271044481-711.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +27.8 KB
Content
1653271276735-972.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +26.6 KB
Content
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