Last modified by Karry Zhuang on 2025/03/06 16:34
<
From version < 36.2 >
edited by Xiaoling
on 2022/06/02 15:54
To version < 45.4 >
edited by Xiaoling
on 2022/06/02 17:10
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -446,150 +446,92 @@
446 446  
447 447  Below are the uplink payloads:
448 448  
449 -[[image:1653270130359-810.png]]
449 +[[image:1654157178836-407.png]]
450 450  
451 451  
452 -(% style="color:red" %)**Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:**
453 -
454 - ~* For AU915/AS923 bands, if UplinkDwell time=0, max 51 bytes for each uplink ( so 51 -5 = 46 max valid date)
455 -
456 - * For AU915/AS923 bands, if UplinkDwell time=1, max 11 bytes for each uplink ( so 11 -5 = 6 max valid date).
457 -
458 - * For US915 band, max 11 bytes for each uplink ( so 11 -5 = 6 max valid date).
459 -
460 - ~* For all other bands: max 51 bytes for each uplink  ( so 51 -5 = 46 max valid date).
461 -
462 462  === 3.3.5 Uplink on demand ===
463 463  
464 -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.
454 +Except uplink periodically, RS485-LN is able to uplink on demand. The server send downlink command to RS485-LN and RS485 will uplink data base on the command.
465 465  
466 466  Downlink control command:
467 467  
468 -[[0x08 command>>path:#downlink_08]]: Poll an uplink with current command set in RS485-BL.
458 +**0x08 command**: Poll an uplink with current command set in RS485-LN.
469 469  
470 -[[0xA8 command>>path:#downlink_A8]]: Send a command to RS485-BL and uplink the output from sensors.
460 +**0xA8 command**: Send a command to RS485-LN and uplink the output from sensors.
471 471  
472 472  
473 473  
474 -1.
475 -11.
476 -111. Uplink on Interrupt
464 +=== 3.3.6 Uplink on Interrupt ===
477 477  
478 -Put the interrupt sensor between 3.3v_out and GPIO ext.[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image022.png]]
466 +RS485-LN support external Interrupt uplink since hardware v1.2 release.
479 479  
480 -AT+INTMOD=0  Disable Interrupt
468 +[[image:1654157342174-798.png]]
481 481  
482 -AT+INTMOD=1  Interrupt trigger by rising or falling edge.
470 +Connect the Interrupt pin to RS485-LN INT port and connect the GND pin to V- port. When there is a high voltage (Max 24v) on INT pin. Device will send an uplink packet.
483 483  
484 -AT+INTMOD=2  Interrupt trigger by falling edge. ( Default Value)
485 485  
486 -AT+INTMOD=3  Interrupt trigger by rising edge.
473 +== 3.4 Uplink Payload ==
487 487  
488 -
489 -1.
490 -11. Uplink Payload
491 -
492 -|**Size(bytes)**|**2**|**1**|**Length depends on the return from the commands**
493 -|Value|(((
475 +(% border="1" style="background-color:#4bacc6; color:white; width:734px" %)
476 +|**Size(bytes)**|(% style="width:120px" %)**2**|(% style="width:116px" %)**1**|(% style="width:386px" %)**Length depends on the return from the commands**
477 +|Value|(% style="width:120px" %)(((
494 494  Battery(mV)
495 495  
496 496  &
497 497  
498 498  Interrupt _Flag
499 -)))|(((
483 +)))|(% style="width:116px" %)(((
500 500  PAYLOAD_VER
501 501  
502 502  
503 -)))|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.
487 +)))|(% style="width:386px" %)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.
504 504  
505 505  Below is the decoder for the first 3 bytes. The rest bytes are dynamic depends on different RS485 sensors.
506 506  
507 507  
508 -function Decoder(bytes, port) {
492 +== 3.5 Configure RS485-BL via AT or Downlink ==
509 509  
510 -~/~/Payload Formats of RS485-BL Deceive
494 +User can configure RS485-LN via AT Commands or LoRaWAN Downlink Commands
511 511  
512 -return {
513 -
514 - ~/~/Battery,units:V
515 -
516 - BatV:((bytes[0]<<8 | bytes[1])&0x7fff)/1000,
517 -
518 - ~/~/GPIO_EXTI 
519 -
520 - EXTI_Trigger:(bytes[0] & 0x80)? "TRUE":"FALSE",
521 -
522 - ~/~/payload of version
523 -
524 - Pay_ver:bytes[2],
525 -
526 - };
527 -
528 - }
529 -
530 -
531 -
532 -
533 -
534 -
535 -
536 -TTN V3 uplink screen shot.
537 -
538 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png]]
539 -
540 -1.
541 -11. Configure RS485-BL via AT or Downlink
542 -
543 -User can configure RS485-BL via [[AT Commands >>path:#_​Using_the_AT]]or LoRaWAN Downlink Commands
544 -
545 545  There are two kinds of Commands:
546 546  
547 -* **Common Commands**: They should be available for each sensor, such as: change uplink interval, reset device. For firmware v1.3, user can find what common commands it supports: http:~/~/wiki.dragino.com/index.php?title=End_Device_AT_Commands_and_Downlink_Commands
498 +* (% style="color:#4f81bd" %)**Common Commands**(%%): They should be available for each sensor, such as: change uplink interval, reset device. For firmware v1.3, user can find what common commands it supports: [[End Device AT Commands and Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]]
548 548  
549 -* **Sensor Related Commands**: These commands are special designed for RS485-BL.  User can see these commands below:
500 +* (% style="color:#4f81bd" %)**Sensor Related Commands**(%%): These commands are special designed for RS485-LN.  User can see these commands below:
550 550  
551 -1.
552 -11.
553 -111. Common Commands:
502 +=== 3.5.1 Common Commands ===
554 554  
555 -They should be available for each of Dragino Sensors, such as: change uplink interval, reset device. For firmware v1.3, user can find what common commands it supports: [[http:~~/~~/wiki.dragino.com/index.php?title=End_Device_AT_Commands_and_Downlink_Commands>>url:http://wiki.dragino.com/index.php?title=End_Device_AT_Commands_and_Downlink_Commands]]
504 +They should be available for each of Dragino Sensors, such as: change uplink interval, reset device. For firmware v1.3, user can find what common commands it supports: [[End Device AT Commands and Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]]
556 556  
557 557  
558 -1.
559 -11.
560 -111. Sensor related commands:
507 +=== 3.5.2 Sensor related commands ===
561 561  
562 -==== Choose Device Type (RS485 or TTL) ====
509 +Response feature is added to the server's downlink, a special package with a FPort of 200 will be uploaded immediately after receiving the data sent by the server.
563 563  
564 -RS485-BL can connect to either RS485 sensors or TTL sensor. User need to specify what type of sensor need to connect.
511 +[[image:image-20220602163333-5.png||height="263" width="1160"]]
565 565  
566 -* AT Command
513 +The first byte of this package represents whether the configuration is successful, 00 represents failure, 01 represents success. Except for the first byte, the other is the previous downlink. (All commands except A8 type commands are applicable)
567 567  
568 -**AT+MOD=1** ~/~/ Set to support RS485-MODBUS type sensors. User can connect multiply RS485 , Modbus sensors to the A / B pins.
569 569  
570 -**AT+MOD=2** ~/~/ Set to support TTL Level sensors, User can connect one TTL Sensor to the TXD/RXD/GND pins.
516 +=== 3.5.3 Sensor related commands ===
571 571  
518 +==== ====
572 572  
573 -* Downlink Payload
520 +==== **RS485 Debug Command** ====
574 574  
575 -**0A aa**     à same as AT+MOD=aa
522 +This command is used to configure the RS485 devices; they won’t be used during sampling.
576 576  
524 +* **AT Command**
577 577  
526 +(% class="box infomessage" %)
527 +(((
528 +**AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m**
529 +)))
578 578  
579 -==== [[RS485 Debug Command>>path:#downlink_A8]] (AT+CFGDEV) ====
531 +m: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
580 580  
581 -This command is used to configure the RS485 or TTL sensors; they won’t be used during sampling.
533 +* **Downlink Payload**
582 582  
583 -* AT Command
584 -
585 -AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
586 -
587 -m: 0: no CRC; 1: add CRC-16/MODBUS in the end of this command.
588 -
589 -
590 -
591 -* Downlink Payload
592 -
593 593  Format: A8 MM NN XX XX XX XX YY
594 594  
595 595  Where:
... ... @@ -597,9 +597,12 @@
597 597  * MM: 1: add CRC-16/MODBUS ; 0: no CRC
598 598  * NN: The length of RS485 command
599 599  * XX XX XX XX: RS485 command total NN bytes
600 -* YY: How many bytes will be uplink from the return of this RS485 command, if YY=0, RS485-BL will execute the downlink command without uplink; if YY>0, RS485-BL will uplink total YY bytes from the output of this RS485 command
542 +* YY: How many bytes will be uplink from the return of this RS485 command,
543 +** if YY=0, RS485-LN will execute the downlink command without uplink;
544 +** if YY>0, RS485-LN will uplink total YY bytes from the output of this RS485 command; Fport=200
545 +** if YY=FF, RS485-LN will uplink RS485 output with the downlink command content; Fport=200.
601 601  
602 -**Example 1:**
547 +**Example 1** ~-~-> Configure without ask for uplink (YY=0)
603 603  
604 604  To connect a Modbus Alarm with below commands.
605 605  
... ... @@ -609,228 +609,242 @@
609 609  
610 610  So if user want to use downlink command to control to RS485 Alarm, he can use:
611 611  
612 -**A8 01 06 0A 05 00 04 00 01 00**: to activate the RS485 Alarm
557 +(% style="color:#4f81bd" %)**A8 01 06 0A 05 00 04 00 01 00**(%%): to activate the RS485 Alarm
613 613  
614 -**A8 01 06 0A 05 00 04 00 00 00**: to deactivate the RS485 Alarm
559 +(% style="color:#4f81bd" %)**A8 01 06 0A 05 00 04 00 00 00**(%%): to deactivate the RS485 Alarm
615 615  
616 616  A8 is type code and 01 means add CRC-16/MODBUS at the end, the 3^^rd^^ byte is 06, means the next 6 bytes are the command to be sent to the RS485 network, the final byte 00 means this command don’t need to acquire output.
617 617  
618 618  
619 -**Example 2:**
564 +**Example 2** ~-~-> Configure with requesting uplink and original downlink command (**YY=FF**)
620 620  
621 -Check TTL Sensor return:
566 +User in IoT server send a downlink command: (% style="color:#4f81bd" %)**A8 01 06 0A 08 00 04 00 01 YY**
622 622  
623 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image024.png]]
624 624  
569 +RS485-LN got this downlink command and send (% style="color:#4f81bd" %)**0A 08 00 04 00 01 **(%%)to Modbus network. One of the RS485 sensor in the network send back Modbus reply **0A 08 00 04 00 00**. RS485-LN get this reply and combine with the original downlink command and uplink. The uplink message is:
625 625  
571 + **A8** (% style="color:#4f81bd" %)**0A 08 00 04 00  **(% style="color:red" %)**01 06** ** **(% style="color:green" %)**0A 08 00 04 00 00**
626 626  
573 + [[image:1654159460680-153.png]]
627 627  
628 -==== Set Payload version ====
629 629  
630 -This is the first byte of the uplink payload. RS485-BL can connect to different sensors. User can set the PAYVER field to tell server how to decode the current payload.
631 631  
632 -* AT Command:
577 +==== **Set Payload version** ====
633 633  
634 -AT+PAYVER: Set PAYVER field = 1
579 +This is the first byte of the uplink payload. RS485-BL can connect to different sensors. User can set the PAYVER field to tell server how to decode the current payload.
635 635  
581 +* **AT Command:**
636 636  
637 -* Downlink Payload:
583 +(% class="box infomessage" %)
584 +(((
585 +**AT+PAYVER: Set PAYVER field = 1**
586 +)))
638 638  
639 -0xAE 01   à Set PAYVER field =  0x01
588 +* **Downlink Payload:**
640 640  
641 -0xAE 0F   à Set PAYVER field =  0x0F
590 +**0xAE 01**  ~-~-> Set PAYVER field =  0x01
642 642  
592 +**0xAE 0F**   ~-~-> Set PAYVER field =  0x0F
643 643  
644 -==== Set RS485 Sampling Commands ====
645 645  
646 -AT+COMMANDx, AT+DATACUTx and AT+SEARCHx
647 647  
648 -These three commands are used to configure how the RS485-BL polling data from Modbus device. Detail of usage please see : [[polling RS485 device>>path:#polling_485]].
596 +==== **Set RS485 Sampling Commands** ====
649 649  
598 +AT+COMMANDx or AT+DATACUTx
650 650  
651 -* AT Command:
600 +These three commands are used to configure how the RS485-LN polling data from Modbus device. Detail of usage please see : [[polling RS485 device>>||anchor="H3.3.3Configurereadcommandsforeachsampling"]].
652 652  
653 -AT+COMMANDx: Configure RS485 read command to sensor.
654 654  
655 -AT+DATACUTx: Configure how to handle return from RS485 devices.
603 +* **AT Command:**
656 656  
657 -AT+SEARCHx: Configure search command
605 +(% class="box infomessage" %)
606 +(((
607 +**AT+COMMANDx: Configure RS485 read command to sensor.**
608 +)))
658 658  
610 +(% class="box infomessage" %)
611 +(((
612 +**AT+DATACUTx: Configure how to handle return from RS485 devices.**
613 +)))
659 659  
660 -* Downlink Payload:
661 661  
662 -0xAF downlink command can be used to set AT+COMMANDx or AT+DATACUTx.
616 +* **Downlink Payload:**
663 663  
664 -Note: if user use AT+COMMANDx to add a new command, he also need to send AT+DATACUTx downlink.
618 +**0xAF** downlink command can be used to set AT+COMMANDx or AT+DATACUTx.
665 665  
620 +(% style="color:red" %)**Note**(%%): if user use AT+COMMANDx to add a new command, he also need to send AT+DATACUTx downlink.
621 +
666 666  Format: AF MM NN LL XX XX XX XX YY
667 667  
668 668  Where:
669 669  
670 670  * MM: the ATCOMMAND or AT+DATACUT to be set. Value from 01 ~~ 0F,
671 -* NN: 0: no CRC; 1: add CRC-16/MODBUS ; 2: set the AT+DATACUT value.
672 -* LL: The length of AT+COMMAND or AT+DATACUT command
627 +* NN:  0: no CRC; 1: add CRC-16/MODBUS ; 2: set the AT+DATACUT value.
628 +* LL:  The length of AT+COMMAND or AT+DATACUT command
673 673  * XX XX XX XX: AT+COMMAND or AT+DATACUT command
674 -* YY: If YY=0, RS485-BL will execute the downlink command without uplink; if YY=1, RS485-BL will execute an uplink after got this command.
630 +* YY:  If YY=0, RS485-BL will execute the downlink command without uplink; if YY=1, RS485-LN will execute an uplink after got this command.
675 675  
676 -Example:
632 +**Example:**
677 677  
678 -**AF 03 01 06 0A 05 00 04 00 01 00**: Same as AT+COMMAND3=0A 05 00 04 00 01,1
634 +(% style="color:#037691" %)**AF 03 01 06 0A 05 00 04 00 01 00**(%%): Same as AT+COMMAND3=0A 05 00 04 00 01,1
679 679  
680 -**AF 03 02 06 10 01 05 06 09 0A 00**: Same as AT+DATACUT3=**16**,**1**,**5+6+9+10**
636 +(% style="color:#037691" %)**AF 03 02 06**(% style="color:orange" %)** 10 **(% style="color:red" %)**01 **(% style="color:green" %)**05 06 09 0A**(% style="color:#037691" %)** 00**(%%): Same as AT+DATACUT3=(% style="color:orange" %)**16**(%%),(% style="color:red" %)**1**(%%),(% style="color:green" %)**5+6+9+10**
681 681  
682 -**AF 03 02 06 0B 02 05 07 08 0A 00**: Same as AT+DATACUT3=**11**,**2**,**5~~7+8~~10**
638 +(% style="color:#037691" %)**AF 03 02 06 **(% style="color:orange" %)**0B**(% style="color:red" %)** 02 **(% style="color:green" %)**05 07 08 0A **(% style="color:#037691" %)**00**(%%): Same as AT+DATACUT3=(% style="color:orange" %)**11**(%%),(% style="color:red" %)**2**(%%),(% style="color:green" %)**5~~7+8~~10**
683 683  
684 684  
685 -0xAB downlink command can be used for set AT+SEARCHx
686 686  
687 -Example: **AB aa 01 03 xx xx xx** (03 here means there are total 3 bytes after 03) So
642 +==== **Fast command to handle MODBUS device** ====
688 688  
689 -* AB aa 01 03 xx xx xx  same as AT+SEARCHaa=1,xx xx xx
690 -* AB aa 02 03 xx xx xx 02 yy yy(03 means there are 3 bytes after 03, they are xx xx xx;02 means there are 2 bytes after 02, they are yy yy) so the commands
691 -
692 -**AB aa 02 03 xx xx xx 02 yy yy**  same as **AT+SEARCHaa=2,xx xx xx+yy yy**
693 -
694 -
695 -==== Fast command to handle MODBUS device ====
696 -
697 697  AT+MBFUN is valid since v1.3 firmware version. The command is for fast configure to read Modbus devices. It is only valid for the devices which follow the [[MODBUS-RTU protocol>>url:https://www.modbustools.com/modbus.html]].
698 698  
699 699  This command is valid since v1.3 firmware version
700 700  
648 +AT+MBFUN can auto read the Modbus function code: 01, 02, 03 or 04. AT+MBFUN has lower priority vs AT+DATACUT command. If AT+DATACUT command is configured, AT+MBFUN will be ignore.
701 701  
702 -AT+MBFUN has only two value:
703 703  
704 -* AT+MBFUN=1: Enable Modbus reading. And get response base on the MODBUS return
651 +**Example:**
705 705  
706 -AT+MBFUN=1, device can auto read the Modbus function code: 01, 02, 03 or 04. AT+MBFUN has lower priority vs AT+DATACUT command. If AT+DATACUT command is configured, AT+MBFUN will be ignore.
707 -
708 -* AT+MBFUN=0: Disable Modbus fast reading.
709 -
710 -Example:
711 -
712 -* AT+MBFUN=1 and AT+DATACUT1/AT+DATACUT2 are not configure (0,0,0).
653 +* AT+MBFUN=1 and AT+DATACUT1/AT+DATACUT2 are not configure (0,0,0). So RS485-LN.
713 713  * AT+COMMAND1= 01 03 00 10 00 08,1 ~-~-> read slave address 01 , function code 03, start address 00 01, quantity of registers 00 08.
714 714  * AT+COMMAND2= 01 02 00 40 00 10,1 ~-~-> read slave address 01 , function code 02, start address 00 40, quantity of inputs 00 10.
715 715  
716 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image025.png]]
657 +[[image:image-20220602165351-6.png]]
717 717  
659 +[[image:image-20220602165351-7.png]]
718 718  
719 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image026.png]]
720 720  
721 721  
722 -* Downlink Commands:
663 +==== **RS485 command timeout** ====
723 723  
724 -A9 aa -à Same as AT+MBFUN=aa
665 +Some Modbus device has slow action to send replies. This command is used to configure the RS485-LN to use longer time to wait for their action.
725 725  
667 +Default value: 0, range:  0 ~~ 65 seconds
726 726  
727 -==== RS485 command timeout ====
669 +* **AT Command:**
728 728  
729 -Some Modbus device has slow action to send replies. This command is used to configure the RS485-BL to use longer time to wait for their action.
671 +(% class="box infomessage" %)
672 +(((
673 +**AT+CMDDLaa=hex(bb cc)*1000**
674 +)))
730 730  
731 -Default value: 0, range:  0 ~~ 5 seconds
676 +**Example:**
732 732  
678 +**AT+CMDDL1=1000** to send the open time to 1000ms
733 733  
734 -* AT Command:
735 735  
736 -AT+CMDDLaa=hex(bb cc)
681 +* **Downlink Payload:**
737 737  
738 -Example:
683 +**0x AA aa bb cc**
739 739  
740 -**AT+CMDDL1=1000** to send the open time to 1000ms
685 +Same as: AT+CMDDLaa=hex(bb cc)*1000
741 741  
687 + **Example:**
742 742  
743 -* Downlink Payload:
689 + 0xAA 01 00 01  ~-~-> Same as **AT+CMDDL1=1000 ms**
744 744  
745 -0x AA aa bb cc
746 746  
747 -Same as: AT+CMDDLaa=hex(bb cc)
748 748  
749 - Example:
693 +==== **Uplink payload mode** ====
750 750  
751 - 0xAA 01 03 E8  à Same as **AT+CMDDL1=1000 ms**
695 +Define to use one uplink or multiple uplinks for the sampling.
752 752  
697 +The use of this command please see: [[Compose Uplink payload>>||anchor="H3.3.4Composetheuplinkpayload"]]
753 753  
754 -==== [[Uplink>>path:#downlink_A8]] payload mode ====
699 +* **AT Command:**
755 755  
756 -Define to use one uplink or multiple uplinks for the sampling.
701 +(% class="box infomessage" %)
702 +(((
703 +**AT+DATAUP=0**
704 +)))
757 757  
758 -The use of this command please see: [[Compose Uplink payload>>path:#DataUP]]
706 +(% class="box infomessage" %)
707 +(((
708 +**AT+DATAUP=1**
709 +)))
759 759  
760 -* AT Command:
761 761  
762 -AT+DATAUP=0
712 +* **Downlink Payload:**
763 763  
764 -AT+DATAUP=1
714 +**0xAD 00**  **~-~->** Same as AT+DATAUP=0
765 765  
716 +**0xAD 01**  **~-~->** Same as AT+DATAUP=1
766 766  
767 -* Downlink Payload:
768 768  
769 -0xAD 00   à Same as AT+DATAUP=0
770 770  
771 -0xAD 01   à Same as AT+DATAUP=1
720 +==== **Manually trigger an Uplink** ====
772 772  
722 +Ask device to send an uplink immediately.
773 773  
774 -==== Manually trigger an Uplink ====
724 +* **AT Command:**
775 775  
776 -Ask device to send an uplink immediately.
726 +No AT Command for this, user can press the [[ACT button>>path:#Button]] for 1 second for the same.
777 777  
778 -* Downlink Payload:
779 779  
780 -0x08 FF, RS485-BL will immediately send an uplink.
729 +* **Downlink Payload:**
781 781  
731 +**0x08 FF**, RS485-LN will immediately send an uplink.
782 782  
783 -==== Clear RS485 Command ====
784 784  
785 -The AT+COMMANDx and AT+DATACUTx settings are stored in special location, user can use below command to clear them.
734 +==== ====
786 786  
736 +==== **Clear RS485 Command** ====
787 787  
788 -* AT Command:
738 +The AT+COMMANDx and AT+DATACUTx settings are stored in special location, user can use below command to clear them.
789 789  
740 +* **AT Command:**
741 +
790 790  **AT+CMDEAR=mm,nn**   mm: start position of erase ,nn: stop position of erase
791 791  
792 792  Etc. AT+CMDEAR=1,10 means erase AT+COMMAND1/AT+DATACUT1 to AT+COMMAND10/AT+DATACUT10
793 793  
794 -Example screen shot after clear all RS485 commands. 
746 +Example screen shot after clear all RS485 commands.
795 795  
796 796  
797 -
798 798  The uplink screen shot is:
799 799  
800 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png]]
751 +[[image:1654160691922-496.png]][[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image001.png]]
801 801  
802 802  
803 -* Downlink Payload:
754 +* **Downlink Payload:**
804 804  
805 -0x09 aa bb same as AT+CMDEAR=aa,bb
756 +**0x09 aa bb** same as AT+CMDEAR=aa,bb
806 806  
807 807  
808 -==== Set Serial Communication Parameters ====
809 809  
760 +==== **Set Serial Communication Parameters** ====
761 +
810 810  Set the Rs485 serial communication parameters:
811 811  
812 -* AT Command:
764 +* **AT Command:**
813 813  
814 814  Set Baud Rate:
815 815  
816 -AT+BAUDR=9600    ~/~/ Options: (1200,2400,4800,14400,19200,115200)
768 +(% class="box infomessage" %)
769 +(((
770 +**AT+BAUDR=9600**    ~/~/ Options: (1200,2400,4800,14400,19200,115200)
771 +)))
817 817  
773 +Set UART Parity
818 818  
819 -Set UART parity
775 +(% class="box infomessage" %)
776 +(((
777 +**AT+PARITY=0**    ~/~/ Option: 0: no parity, 1: odd parity, 2: even parity
778 +)))
820 820  
821 -AT+PARITY=0    ~/~/ Option: 0: no parity, 1: odd parity, 2: even parity
822 -
823 -
824 824  Set STOPBIT
825 825  
826 -AT+STOPBIT=0    ~/~/ Option: 0 for 1bit; 1 for 1.5 bit ; 2 for 2 bits
782 +(% class="box infomessage" %)
783 +(((
784 +**AT+STOPBIT=0**    ~/~/ Option: 0 for 1bit; 1 for 1.5 bit ; 2 for 2 bits
785 +)))
827 827  
828 828  
829 -* Downlink Payload:
788 +* **Downlink Payload:**
830 830  
831 -A7 01 aa bb: Same  AT+BAUDR=hex(aa bb)*100
790 +**A7 01 aa bb**: Same  AT+BAUDR=hex(aa bb)*100
832 832  
833 -Example:
792 +**Example:**
834 834  
835 835  * A7 01 00 60   same as AT+BAUDR=9600
836 836  * A7 01 04 80  same as AT+BAUDR=115200
... ... @@ -840,287 +840,5 @@
840 840  A7 03 aa: Same as  AT+STOPBIT=aa  (aa value: 00 , 01 or 02)
841 841  
842 842  
843 -==== Control output power duration ====
844 844  
845 -User can set the output power duration before each sampling.
846 -
847 -* AT Command:
848 -
849 -Example:
850 -
851 -AT+3V3T=1000 ~/~/ 3V3 output power will open 1s before each sampling.
852 -
853 -AT+5VT=1000 ~/~/ +5V output power will open 1s before each sampling.
854 -
855 -
856 -* LoRaWAN Downlink Command:
857 -
858 -07 01 aa bb  Same as AT+5VT=(aa bb)
859 -
860 -07 02 aa bb  Same as AT+3V3T=(aa bb)
861 -
862 -
863 -
864 -
865 -1.
866 -11. Buttons
867 -
868 -|**Button**|**Feature**
869 -|**RST**|Reboot RS485-BL
870 -
871 -1.
872 -11. +3V3 Output
873 -
874 -RS485-BL has a Controllable +3V3 output, user can use this output to power external sensor.
875 -
876 -The +3V3 output will be valid for every sampling. RS485-BL will enable +3V3 output before all sampling and disable the +3V3 after all sampling. 
877 -
878 -
879 -The +3V3 output time can be controlled by AT Command.
880 -
881 -**AT+3V3T=1000**
882 -
883 -Means set +3v3 valid time to have 1000ms. So, the real +3v3 output will actually have 1000ms + sampling time for other sensors.
884 -
885 -
886 -By default, the AT+3V3T=0. This is a special case, means the +3V3 output is always on at any time
887 -
888 -
889 -1.
890 -11. +5V Output
891 -
892 -RS485-BL has a Controllable +5V output, user can use this output to power external sensor.
893 -
894 -The +5V output will be valid for every sampling. RS485-BL will enable +5V output before all sampling and disable the +5v after all sampling. 
895 -
896 -
897 -The 5V output time can be controlled by AT Command.
898 -
899 -**AT+5VT=1000**
900 -
901 -Means set 5V valid time to have 1000ms. So, the real 5V output will actually have 1000ms + sampling time for other sensors.
902 -
903 -
904 -By default, the AT+5VT=0. If the external sensor which require 5v and require more time to get stable state, user can use this command to increase the power ON duration for this sensor.
905 -
906 -
907 -
908 -
909 -1.
910 -11. LEDs
911 -
912 -|**LEDs**|**Feature**
913 -|**LED1**|Blink when device transmit a packet.
914 -
915 -1.
916 -11. Switch Jumper
917 -
918 -|**Switch Jumper**|**Feature**
919 -|**SW1**|(((
920 -ISP position: Upgrade firmware via UART
921 -
922 -Flash position: Configure device, check running status.
923 -)))
924 -|**SW2**|(((
925 -5V position: set to compatible with 5v I/O.
926 -
927 -3.3v position: set to compatible with 3.3v I/O.,
928 -)))
929 -
930 -+3.3V: is always ON
931 -
932 -+5V: Only open before every sampling. The time is by default, it is AT+5VT=0.  Max open time. 5000 ms.
933 -
934 -1. Case Study
935 -
936 -User can check this URL for some case studies.
937 -
938 -[[http:~~/~~/wiki.dragino.com/index.php?title=APP_RS485_COMMUNICATE_WITH_SENSORS>>url:http://wiki.dragino.com/index.php?title=APP_RS485_COMMUNICATE_WITH_SENSORS]]
939 -
940 -
941 -
942 -
943 -1. Use AT Command
944 -11. Access AT Command
945 -
946 -RS485-BL supports AT Command set. User can use a USB to TTL adapter plus the 3.5mm Program Cable to connect to RS485-BL to use AT command, as below.
947 -
948 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image027.png]]
949 -
950 -
951 -In PC, User needs to set **serial tool**(such as [[putty>>url:https://www.chiark.greenend.org.uk/~~sgtatham/putty/latest.html]], SecureCRT) baud rate to **9600** to access to access serial console of RS485-BL. The default password is 123456. Below is the output for reference:
952 -
953 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image028.png]]
954 -
955 -
956 -
957 -More detail AT Command manual can be found at [[AT Command Manual>>path:#AT_COMMAND]]
958 -
959 -
960 -
961 -1.
962 -11. Common AT Command Sequence
963 -111. Multi-channel ABP mode (Use with SX1301/LG308)
964 -
965 -If device has not joined network yet:
966 -
967 -AT+FDR
968 -
969 -AT+NJM=0
970 -
971 -ATZ
972 -
973 -
974 -If device already joined network:
975 -
976 -AT+NJM=0
977 -
978 -ATZ
979 -
980 -1.
981 -11.
982 -111. Single-channel ABP mode (Use with LG01/LG02)
983 -
984 -AT+FDR   Reset Parameters to Factory Default, Keys Reserve
985 -
986 -AT+NJM=0 Set to ABP mode
987 -
988 -AT+ADR=0 Set the Adaptive Data Rate Off
989 -
990 -AT+DR=5  Set Data Rate
991 -
992 -AT+TDC=60000  Set transmit interval to 60 seconds
993 -
994 -AT+CHS=868400000 Set transmit frequency to 868.4Mhz
995 -
996 -AT+RX2FQ=868400000 Set RX2Frequency to 868.4Mhz (according to the result from server)
997 -
998 -AT+RX2DR=5  Set RX2DR to match the downlink DR from server. see below
999 -
1000 -AT+DADDR=26 01 1A F1 Set Device Address to 26 01 1A F1, this ID can be found in the LoRa Server portal.
1001 -
1002 -ATZ          Reset MCU
1003 -
1004 -**Note:**
1005 -
1006 -1. Make sure the device is set to ABP mode in the IoT Server.
1007 -1. Make sure the LG01/02 gateway RX frequency is exactly the same as AT+CHS setting.
1008 -1. Make sure SF / bandwidth setting in LG01/LG02 match the settings of AT+DR. refer [[this link>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/&file=LoRaWAN%201.0.3%20Regional%20Parameters.xlsx]] to see what DR means.
1009 -1. The command AT+RX2FQ and AT+RX2DR is to let downlink work. to set the correct parameters, user can check the actually downlink parameters to be used. As below. Which shows the RX2FQ should use 868400000 and RX2DR should be 5
1010 -
1011 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image029.png]]
1012 -
1013 -
1014 -1. FAQ
1015 -11. How to upgrade the image?
1016 -
1017 -The RS485-BL LoRaWAN Controller is shipped with a 3.5mm cable, the cable is used to upload image to RS485-BL to:
1018 -
1019 -* Support new features
1020 -* For bug fix
1021 -* Change LoRaWAN bands.
1022 -
1023 -Below shows the hardware connection for how to upload an image to RS485-BL:
1024 -
1025 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image030.png]]
1026 -
1027 -**Step1:** Download [[flash loader>>url:https://www.st.com/content/st_com/en/products/development-tools/software-development-tools/stm32-software-development-tools/stm32-programmers/flasher-stm32.html]].
1028 -
1029 -**Step2**: Download the [[LT Image files>>url:http://www.dragino.com/downloads/index.php?dir=LT_LoRa_IO_Controller/LT33222-L/image/]].
1030 -
1031 -**Step3: **Open flashloader; choose the correct COM port to update.
1032 -
1033 -
1034 -|(((
1035 -HOLD PRO then press the RST button, SYS will be ON, then click next
1036 -)))
1037 -
1038 -|(((
1039 -Board detected
1040 -)))
1041 -
1042 -|(((
1043 -
1044 -)))
1045 -
1046 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image031.png]] [[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image032.png]]
1047 -
1048 -
1049 -
1050 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image033.png]] [[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image034.png]]
1051 -
1052 -
1053 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image035.png]] [[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image036.png]]
1054 -
1055 -
1056 -1.
1057 -11. How to change the LoRa Frequency Bands/Region?
1058 -
1059 -User can follow the introduction for [[how to upgrade image>>path:#upgrade_image]]. When download the images, choose the required image file for download.
1060 -
1061 -
1062 -
1063 -1.
1064 -11. How many RS485-Slave can RS485-BL connects?
1065 -
1066 -The RS485-BL can support max 32 RS485 devices. Each uplink command of RS485-BL can support max 16 different RS485 command. So RS485-BL can support max 16 RS485 devices pre-program in the device for uplink. For other devices no pre-program, user can use the [[downlink message (type code 0xA8) to poll their info>>path:#downlink_A8]].
1067 -
1068 -
1069 -
1070 -
1071 -1. Trouble Shooting     
1072 -11. Downlink doesn’t work, how to solve it?
1073 -
1074 -Please see this link for debug:
1075 -
1076 -[[http:~~/~~/wiki.dragino.com/index.php?title=Main_Page#LoRaWAN_Communication_Debug>>url:http://wiki.dragino.com/index.php?title=Main_Page#LoRaWAN_Communication_Debug]] 
1077 -
1078 -
1079 -
1080 -1.
1081 -11. Why I can’t join TTN V3 in US915 /AU915 bands?
1082 -
1083 -It might about the channels mapping. Please see for detail.
1084 -
1085 -[[http:~~/~~/wiki.dragino.com/index.php?title=LoRaWAN_Communication_Debug#Notice_of_US915.2FCN470.2FAU915_Frequency_band>>url:http://wiki.dragino.com/index.php?title=LoRaWAN_Communication_Debug#Notice_of_US915.2FCN470.2FAU915_Frequency_band]]
1086 -
1087 -
1088 -
1089 -1. Order Info
1090 -
1091 -**Part Number: RS485-BL-XXX**
1092 -
1093 -**XXX:**
1094 -
1095 -* **EU433**: frequency bands EU433
1096 -* **EU868**: frequency bands EU868
1097 -* **KR920**: frequency bands KR920
1098 -* **CN470**: frequency bands CN470
1099 -* **AS923**: frequency bands AS923
1100 -* **AU915**: frequency bands AU915
1101 -* **US915**: frequency bands US915
1102 -* **IN865**: frequency bands IN865
1103 -* **RU864**: frequency bands RU864
1104 -* **KZ865: **frequency bands KZ865
1105 -
1106 -1. Packing Info
1107 -
1108 -**Package Includes**:
1109 -
1110 -* RS485-BL x 1
1111 -* Stick Antenna for LoRa RF part x 1
1112 -* Program cable x 1
1113 -
1114 -**Dimension and weight**:
1115 -
1116 -* Device Size: 13.5 x 7 x 3 cm
1117 -* Device Weight: 105g
1118 -* Package Size / pcs : 14.5 x 8 x 5 cm
1119 -* Weight / pcs : 170g
1120 -
1121 -1. Support
1122 -
1123 -* Support is provided Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different timezones we cannot offer live support. However, your questions will be answered as soon as possible in the before-mentioned schedule.
1124 -* Provide as much information as possible regarding your enquiry (product models, accurately describe your problem and steps to replicate it etc) and send a mail to
1125 -
1126 -[[support@dragino.com>>url:file:///D:/市场资料/说明书/LoRa/LT系列/support@dragino.com]]
803 +==== ====
1654157178836-407.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +179.9 KB
Content
1654157342174-798.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +31.9 KB
Content
1654158783574-851.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +40.6 KB
Content
1654159460680-153.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +24.9 KB
Content
1654160691922-496.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +109.3 KB
Content
image-20220602163333-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +48.2 KB
Content
image-20220602165351-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +10.6 KB
Content
image-20220602165351-7.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +19.3 KB
Content

Applications

Navigation

Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0