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 35.5
edited by Xiaoling
on 2022/06/02 10:20
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 ==
... ... @@ -22,19 +22,19 @@
22 22  )))
23 23  
24 24  (((
25 -The Dragino RS485-BL is a **RS485 / UART to LoRaWAN Converter** for Internet of Things solutions. User can connect RS485 or UART sensor to RS485-BL converter, and configure RS485-BL to periodically read sensor data and upload via LoRaWAN network to IoT server.
28 +The Dragino RS485-BL is a (% style="color:blue" %)**RS485 / UART to LoRaWAN Converter**(%%) for Internet of Things solutions. User can connect RS485 or UART sensor to RS485-BL converter, and configure RS485-BL to periodically read sensor data and upload via LoRaWAN network to IoT server.
26 26  )))
27 27  
28 28  (((
29 -RS485-BL can interface to RS485 sensor, 3.3v/5v UART sensor or interrupt sensor. RS485-BL provides **a 3.3v output** and** a 5v output** to power external sensors. Both output voltages are controllable to minimize the total system power consumption.
32 +RS485-BL can interface to RS485 sensor, 3.3v/5v UART sensor or interrupt sensor. RS485-BL provides (% style="color:blue" %)**a 3.3v output**(%%) and** (% style="color:blue" %)a 5v output(%%)** to power external sensors. Both output voltages are controllable to minimize the total system power consumption.
30 30  )))
31 31  
32 32  (((
33 -RS485-BL is IP67 **waterproof** and powered by **8500mAh Li-SOCI2 battery**, it is designed for long term use for several years.
36 +RS485-BL is IP67 (% style="color:blue" %)**waterproof**(%%) and powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), it is designed for long term use for several years.
34 34  )))
35 35  
36 36  (((
37 -RS485-BL runs standard **LoRaWAN 1.0.3 in Class A**. It can reach long transfer range and easy to integrate with LoRaWAN compatible gateway and IoT server.
40 +RS485-BL runs standard (% style="color:blue" %)**LoRaWAN 1.0.3 in Class A**(%%). It can reach long transfer range and easy to integrate with LoRaWAN compatible gateway and IoT server.
38 38  )))
39 39  
40 40  (((
... ... @@ -51,8 +51,11 @@
51 51  
52 52  [[image:1652953304999-717.png||height="424" width="733"]]
53 53  
57 +
58 +
54 54  == 1.2 Specifications ==
55 55  
61 +
56 56  **Hardware System:**
57 57  
58 58  * STM32L072CZT6 MCU
... ... @@ -59,8 +59,6 @@
59 59  * SX1276/78 Wireless Chip 
60 60  * Power Consumption (exclude RS485 device):
61 61  ** Idle: 6uA@3.3v
62 -
63 -*
64 64  ** 20dB Transmit: 130mA@3.3v
65 65  
66 66  **Interface for Model:**
... ... @@ -114,9 +114,12 @@
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  
121 +
117 117  == 1.6 Hardware Change log ==
118 118  
119 119  (((
125 +
126 +
120 120  v1.4
121 121  )))
122 122  
... ... @@ -140,6 +140,8 @@
140 140  
141 141  (((
142 142  Release version ​​​​​
150 +
151 +
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  
165 +
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.
172 +
173 +
162 162  )))
163 163  
164 164  == 3.2 Example to join LoRaWAN network ==
... ... @@ -194,8 +194,6 @@
194 194  )))
195 195  
196 196  
197 -
198 -
199 199  [[image:image-20220519174512-1.png]]
200 200  
201 201  [[image:image-20220519174512-2.png||height="328" width="731"]]
... ... @@ -219,10 +219,13 @@
219 219  
220 220  [[image:1652953568895-172.png||height="232" width="724"]]
221 221  
232 +
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.
236 +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.
237 +
238 +
226 226  )))
227 227  
228 228  === 3.3.1 onfigure UART settings for RS485 or TTL communication ===
... ... @@ -323,8 +323,9 @@
323 323  mm: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
324 324  )))|(% style="width:256px" %)AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
325 325  
326 -Detail of AT+CFGDEV command see [[AT+CFGDEV detail>>path:#AT_CFGDEV]].
339 +Detail of AT+CFGDEV command see [[AT+CFGDEV detail>>||anchor="HRS485DebugCommand28AT2BCFGDEV29"]].
327 327  
341 +
328 328  === 3.3.3 Configure read commands for each sampling ===
329 329  
330 330  (((
... ... @@ -422,7 +422,7 @@
422 422  
423 423  **Examples:**
424 424  
425 -1. For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
439 +1）For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
426 426  
427 427  If we set AT+SEARCH1=1,1E 56 34.      (max 5 bytes for prefix)
428 428  
... ... @@ -430,7 +430,7 @@
430 430  
431 431  [[image:1653271044481-711.png]]
432 432  
433 -1. For a return string from AT+COMMAND1:  16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
447 +2）For a return string from AT+COMMAND1:  16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
434 434  
435 435  If we set AT+SEARCH1=2, 1E 56 34+31 00 49
436 436  
... ... @@ -449,97 +449,143 @@
449 449  * **c: define the position for valid value.  **
450 450  )))
451 451  
452 -Examples:
466 +**Examples:**
453 453  
454 454  * Grab bytes:
455 455  
456 456  [[image:1653271581490-837.png||height="313" width="722"]]
457 457  
472 +
458 458  * Grab a section.
459 459  
460 460  [[image:1653271648378-342.png||height="326" width="720"]]
461 461  
477 +
462 462  * Grab different sections.
463 463  
464 464  [[image:1653271657255-576.png||height="305" width="730"]]
465 465  
482 +(((
466 466  (% style="color:red" %)**Note:**
484 +)))
467 467  
486 +(((
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.
488 +)))
469 469  
490 +(((
470 470  **Example:**
492 +)))
471 471  
494 +(((
472 472  (% style="color:red" %)AT+COMMAND1=11 01 1E D0,0
496 +)))
473 473  
498 +(((
474 474  (% style="color:red" %)AT+SEARCH1=1,1E 56 34
500 +)))
475 475  
502 +(((
476 476  (% style="color:red" %)AT+DATACUT1=0,2,1~~5
504 +)))
477 477  
506 +(((
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
508 +)))
479 479  
510 +(((
480 480  (% style="color:red" %)String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49
512 +)))
481 481  
514 +(((
482 482  (% style="color:red" %)Valid payload after DataCUT command: 2e 30 58 5f 36
516 +)))
483 483  
484 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image018.png]]
518 +[[image:1653271763403-806.png]]
485 485  
486 486  
521 +=== 3.3.4 Compose the uplink payload ===
487 487  
488 -
489 -1.
490 -11.
491 -111. Compose the uplink payload
492 -
523 +(((
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.**
525 +)))
494 494  
527 +(((
528 +(% style="color:#037691" %)**Examples: AT+DATAUP=0**
529 +)))
495 495  
496 -**Examples: AT+DATAUP=0**
531 +(((
532 +Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**A SIGNLE UPLINK**.
533 +)))
497 497  
498 -Compose the uplink payload with value returns in sequence and send with **A SIGNLE UPLINK**.
499 -
535 +(((
500 500  Final Payload is
537 +)))
501 501  
502 -Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx
539 +(((
540 +(% style="color:#4f81bd" %)**Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx**
541 +)))
503 503  
543 +(((
504 504  Where PAYVER is defined by AT+PAYVER, below is an example screen shot.
545 +)))
505 505  
506 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image019.png]]
547 +[[image:1653272787040-634.png||height="515" width="719"]]
507 507  
508 508  
509 509  
510 -**Examples: AT+DATAUP=1**
551 +(((
552 +(% style="color:#037691" %)**Examples: AT+DATAUP=1**
511 511  
512 -Compose the uplink payload with value returns in sequence and send with **Multiply UPLINKs**.
554 +
555 +)))
513 513  
557 +(((
558 +Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**Multiply UPLINKs**.
559 +)))
560 +
561 +(((
514 514  Final Payload is
563 +)))
515 515  
516 -Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA
565 +(((
566 +(% style="color:#4f81bd" %)**Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA**
567 +)))
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
569 +1. (((
570 +Battery Info (2 bytes): Battery voltage
571 +)))
572 +1. (((
573 +PAYVER (1 byte): Defined by AT+PAYVER
574 +)))
575 +1. (((
576 +PAYLOAD COUNT (1 byte): Total how many uplinks of this sampling.
577 +)))
578 +1. (((
579 +PAYLOAD# (1 byte): Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT)
580 +)))
581 +1. (((
582 +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
583 +)))
523 523  
524 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image020.png]]
585 +[[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
530 530  
531 -DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10= 02 aa 05 81 0a 20
590 +DATA1=RETURN1 Valid Value = (% style="background-color:#4f81bd; color:white" %) 20 20 0a 33 90 41
532 532  
533 -DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 = 20 20 20 2d 30
592 +DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10= (% style="background-color:#4f81bd; color:white" %)02 aa 05 81 0a 20
534 534  
594 +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 536  
537 537  Below are the uplink payloads:
538 538  
539 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image021.png]]
599 +[[image:1653272901032-107.png]]
540 540  
541 541  
542 -Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:
602 +(% style="color:red" %)Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:
543 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  
... ... @@ -551,139 +551,186 @@
551 551  
552 552  
553 553  
554 -1.
555 -11.
556 -111. Uplink on demand
614 +=== 3.3.5 Uplink on demand ===
557 557  
616 +(((
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.
618 +)))
559 559  
620 +(((
560 560  Downlink control command:
622 +)))
561 561  
562 -[[0x08 command>>path:#downlink_08]]: Poll an uplink with current command set in RS485-BL.
624 +(((
625 +**0x08 command**: Poll an uplink with current command set in RS485-BL.
626 +)))
563 563  
564 -[[0xA8 command>>path:#downlink_A8]]: Send a command to RS485-BL and uplink the output from sensors.
628 +(((
629 +**0xA8 command**: Send a command to RS485-BL and uplink the output from sensors.
565 565  
631 +
632 +)))
566 566  
634 +=== 3.3.6 Uplink on Interrupt ===
567 567  
568 -1.
569 -11.
570 -111. Uplink on Interrupt
636 +Put the interrupt sensor between 3.3v_out and GPIO ext.
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]]
638 +[[image:1653273818896-432.png]]
573 573  
640 +
641 +(((
574 574  AT+INTMOD=0  Disable Interrupt
643 +)))
575 575  
645 +(((
576 576  AT+INTMOD=1  Interrupt trigger by rising or falling edge.
647 +)))
577 577  
649 +(((
578 578  AT+INTMOD=2  Interrupt trigger by falling edge. ( Default Value)
651 +)))
579 579  
653 +(((
580 580  AT+INTMOD=3  Interrupt trigger by rising edge.
581 581  
656 +
657 +)))
582 582  
583 -1.
584 -11. Uplink Payload
659 +== 3.4 Uplink Payload ==
585 585  
586 -|**Size(bytes)**|**2**|**1**|**Length depends on the return from the commands**
587 -|Value|(((
661 +(% border="1" style="background-color:#4f81bd; color:white; width:850px" %)
662 +|**Size(bytes)**|(% style="width:130px" %)**2**|(% style="width:93px" %)**1**|(% style="width:509px" %)**Length depends on the return from the commands**
663 +|Value|(% style="width:130px" %)(((
664 +(((
588 588  Battery(mV)
666 +)))
589 589  
668 +(((
590 590  &
670 +)))
591 591  
672 +(((
592 592  Interrupt _Flag
593 -)))|(((
674 +)))
675 +)))|(% 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.
679 +)))|(% 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  
683 +(((
684 +{{{function Decoder(bytes, port) {}}}
685 +)))
601 601  
602 -function Decoder(bytes, port) {
687 +(((
688 +{{{//Payload Formats of RS485-BL Deceive}}}
689 +)))
603 603  
604 -~/~/Payload Formats of RS485-BL Deceive
691 +(((
692 +{{{return {}}}
693 +)))
605 605  
606 -return {
695 +(((
696 +{{{ //Battery,units:V}}}
697 +)))
607 607  
608 - ~/~/Battery,units:V
699 +(((
700 +{{{ BatV:((bytes[0]<<8 | bytes[1])&0x7fff)/1000,}}}
701 +)))
609 609  
610 - BatV:((bytes[0]<<8 | bytes[1])&0x7fff)/1000,
703 +(((
704 +{{{ //GPIO_EXTI }}}
705 +)))
611 611  
612 - ~/~/GPIO_EXTI 
707 +(((
708 +{{{ EXTI_Trigger:(bytes[0] & 0x80)? "TRUE":"FALSE",}}}
709 +)))
613 613  
614 - EXTI_Trigger:(bytes[0] & 0x80)? "TRUE":"FALSE",
711 +(((
712 +{{{ //payload of version}}}
713 +)))
615 615  
616 - ~/~/payload of version
715 +(((
716 +{{{ Pay_ver:bytes[2],}}}
717 +)))
617 617  
618 - Pay_ver:bytes[2],
719 +(((
720 +{{{ }; }}}
721 +)))
619 619  
620 - };
723 +(((
724 +}
621 621  
622 - }
726 +
727 +)))
623 623  
624 -
625 -
626 -
627 -
628 -
629 -
729 +(((
630 630  TTN V3 uplink screen shot.
731 +)))
631 631  
632 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png]]
733 +[[image:1653274001211-372.png||height="192" width="732"]]
633 633  
634 -1.
635 -11. Configure RS485-BL via AT or Downlink
636 636  
637 -User can configure RS485-BL via [[AT Commands >>path:#_​Using_the_AT]]or LoRaWAN Downlink Commands
736 +== 3.5 Configure RS485-BL via AT or Downlink ==
638 638  
738 +User can configure RS485-BL via AT Commands or LoRaWAN Downlink Commands
739 +
639 639  There are two kinds of Commands:
640 640  
641 -* **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
742 +* (% 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]]
642 642  
643 -* **Sensor Related Commands**: These commands are special designed for RS485-BL.  User can see these commands below:
744 +* (% style="color:#4f81bd" %)**Sensor Related Commands**(%%): These commands are special designed for RS485-BL.  User can see these commands below:
644 644  
645 -1.
646 -11.
647 -111. Common Commands:
746 +=== 3.5.1 Common Commands: ===
648 648  
649 -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]]
748 +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]]
650 650  
651 651  
652 -1.
653 -11.
654 -111. Sensor related commands:
751 +=== 3.5.2 Sensor related commands: ===
655 655  
656 -==== Choose Device Type (RS485 or TTL) ====
753 +==== ====
657 657  
755 +==== **Choose Device Type (RS485 or TTL)** ====
756 +
658 658  RS485-BL can connect to either RS485 sensors or TTL sensor. User need to specify what type of sensor need to connect.
659 659  
660 -* AT Command
759 +* **AT Command**
661 661  
761 +(% class="box infomessage" %)
762 +(((
662 662  **AT+MOD=1** ~/~/ Set to support RS485-MODBUS type sensors. User can connect multiply RS485 , Modbus sensors to the A / B pins.
764 +)))
663 663  
766 +(% class="box infomessage" %)
767 +(((
664 664  **AT+MOD=2** ~/~/ Set to support TTL Level sensors, User can connect one TTL Sensor to the TXD/RXD/GND pins.
769 +)))
665 665  
666 666  
667 -* Downlink Payload
772 +* **Downlink Payload**
668 668  
669 -**0A aa**     à same as AT+MOD=aa
774 +**0A aa**  ~-~->  same as AT+MOD=aa
670 670  
671 671  
672 672  
673 -==== [[RS485 Debug Command>>path:#downlink_A8]] (AT+CFGDEV) ====
778 +==== **RS485 Debug Command (AT+CFGDEV)** ====
674 674  
675 675  This command is used to configure the RS485 or TTL sensors; they won’t be used during sampling.
676 676  
677 -* AT Command
782 +* **AT Command**
678 678  
679 -AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
784 +(% class="box infomessage" %)
785 +(((
786 +**AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m**
787 +)))
680 680  
681 681  m: 0: no CRC; 1: add CRC-16/MODBUS in the end of this command.
682 682  
683 683  
792 +* **Downlink Payload**
684 684  
685 -* Downlink Payload
686 -
687 687  Format: A8 MM NN XX XX XX XX YY
688 688  
689 689  Where:
... ... @@ -697,15 +697,15 @@
697 697  
698 698  To connect a Modbus Alarm with below commands.
699 699  
700 -* The command to active alarm is: 0A 05 00 04 00 01 4C B0. Where 0A 05 00 04 00 01 is the Modbus command to read the register 00 40 where stored the DI status. The 4C B0 is the CRC-16/MODBUS which calculate manually.
807 +* The command to active alarm is: 0A 05 00 04 00 01 **4C B0**. Where 0A 05 00 04 00 01 is the Modbus command to read the register 00 40 where stored the DI status. The 4C B0 is the CRC-16/MODBUS which calculate manually.
701 701  
702 -* The command to deactivate alarm is: 0A 05 00 04 00 00 8D 70. Where 0A 05 00 04 00 00 is the Modbus command to read the register 00 40 where stored the DI status. The 8D 70 is the CRC-16/MODBUS which calculate manually.
809 +* The command to deactivate alarm is: 0A 05 00 04 00 00 **8D 70**. Where 0A 05 00 04 00 00 is the Modbus command to read the register 00 40 where stored the DI status. The 8D 70 is the CRC-16/MODBUS which calculate manually.
703 703  
704 704  So if user want to use downlink command to control to RS485 Alarm, he can use:
705 705  
706 -**A8 01 06 0A 05 00 04 00 01 00**: to activate the RS485 Alarm
813 +(% style="color:#037691" %)**A8 01 06 0A 05 00 04 00 01 00**(%%): to activate the RS485 Alarm
707 707  
708 -**A8 01 06 0A 05 00 04 00 00 00**: to deactivate the RS485 Alarm
815 +(% style="color:#037691" %)**A8 01 06 0A 05 00 04 00 00 00**(%%): to deactivate the RS485 Alarm
709 709  
710 710  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.
711 711  
... ... @@ -714,48 +714,60 @@
714 714  
715 715  Check TTL Sensor return:
716 716  
717 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image024.png]]
824 +[[image:1654132684752-193.png]]
718 718  
719 719  
720 720  
828 +==== **Set Payload version** ====
721 721  
722 -==== Set Payload version ====
723 -
724 724  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.
725 725  
726 -* AT Command:
832 +* **AT Command:**
727 727  
728 -AT+PAYVER: Set PAYVER field = 1
834 +(% class="box infomessage" %)
835 +(((
836 +**AT+PAYVER: Set PAYVER field = 1**
837 +)))
729 729  
730 730  
731 -* Downlink Payload:
840 +* **Downlink Payload:**
732 732  
733 -0xAE 01   à Set PAYVER field =  0x01
842 +**0xAE 01**  ~-~-> Set PAYVER field =  0x01
734 734  
735 -0xAE 0F   à Set PAYVER field =  0x0F
844 +**0xAE 0F**   ~-~-> Set PAYVER field =  0x0F
736 736  
737 737  
738 -==== Set RS485 Sampling Commands ====
739 739  
848 +==== **Set RS485 Sampling Commands** ====
849 +
740 740  AT+COMMANDx, AT+DATACUTx and AT+SEARCHx
741 741  
742 -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]].
852 +These three commands are used to configure how the RS485-BL polling data from Modbus device. Detail of usage please see : [[polling RS485 device>>||anchor="H3.3.3Configurereadcommandsforeachsampling"]].
743 743  
744 744  
745 -* AT Command:
855 +* **AT Command:**
746 746  
747 -AT+COMMANDx: Configure RS485 read command to sensor.
857 +(% class="box infomessage" %)
858 +(((
859 +**AT+COMMANDx: Configure RS485 read command to sensor.**
860 +)))
748 748  
749 -AT+DATACUTx: Configure how to handle return from RS485 devices.
862 +(% class="box infomessage" %)
863 +(((
864 +**AT+DATACUTx: Configure how to handle return from RS485 devices.**
865 +)))
750 750  
751 -AT+SEARCHx: Configure search command
867 +(% class="box infomessage" %)
868 +(((
869 +**AT+SEARCHx: Configure search command**
870 +)))
752 752  
753 753  
754 -* Downlink Payload:
873 +* **Downlink Payload:**
755 755  
756 -0xAF downlink command can be used to set AT+COMMANDx or AT+DATACUTx.
875 +**0xAF** downlink command can be used to set AT+COMMANDx or AT+DATACUTx.
757 757  
758 -Note: if user use AT+COMMANDx to add a new command, he also need to send AT+DATACUTx downlink.
877 +(% style="color:red" %)**Note**(%%): if user use AT+COMMANDx to add a new command, he also need to send AT+DATACUTx downlink.
759 759  
760 760  Format: AF MM NN LL XX XX XX XX YY
761 761  
... ... @@ -762,23 +762,23 @@
762 762  Where:
763 763  
764 764  * MM: the ATCOMMAND or AT+DATACUT to be set. Value from 01 ~~ 0F,
765 -* NN: 0: no CRC; 1: add CRC-16/MODBUS ; 2: set the AT+DATACUT value.
766 -* LL: The length of AT+COMMAND or AT+DATACUT command
884 +* NN:  0: no CRC; 1: add CRC-16/MODBUS ; 2: set the AT+DATACUT value.
885 +* LL:  The length of AT+COMMAND or AT+DATACUT command
767 767  * XX XX XX XX: AT+COMMAND or AT+DATACUT command
768 -* 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.
887 +* 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.
769 769  
770 -Example:
889 +**Example:**
771 771  
772 -**AF 03 01 06 0A 05 00 04 00 01 00**: Same as AT+COMMAND3=0A 05 00 04 00 01,1
891 +(% 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
773 773  
774 -**AF 03 02 06 10 01 05 06 09 0A 00**: Same as AT+DATACUT3=**16**,**1**,**5+6+9+10**
893 +(% 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**
775 775  
776 -**AF 03 02 06 0B 02 05 07 08 0A 00**: Same as AT+DATACUT3=**11**,**2**,**5~~7+8~~10**
895 +(% 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**
777 777  
778 778  
779 -0xAB downlink command can be used for set AT+SEARCHx
898 +**0xAB** downlink command can be used for set AT+SEARCHx
780 780  
781 -Example: **AB aa 01 03 xx xx xx** (03 here means there are total 3 bytes after 03) So
900 +**Example:** **AB aa 01 03 xx xx xx** (03 here means there are total 3 bytes after 03) So
782 782  
783 783  * AB aa 01 03 xx xx xx  same as AT+SEARCHaa=1,xx xx xx
784 784  * 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
... ... @@ -786,145 +786,164 @@
786 786  **AB aa 02 03 xx xx xx 02 yy yy**  same as **AT+SEARCHaa=2,xx xx xx+yy yy**
787 787  
788 788  
789 -==== Fast command to handle MODBUS device ====
790 790  
909 +==== **Fast command to handle MODBUS device** ====
910 +
791 791  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]].
792 792  
793 793  This command is valid since v1.3 firmware version
794 794  
795 795  
796 -AT+MBFUN has only two value:
916 +**AT+MBFUN has only two value:**
797 797  
798 -* AT+MBFUN=1: Enable Modbus reading. And get response base on the MODBUS return
918 +* **AT+MBFUN=1**: Enable Modbus reading. And get response base on the MODBUS return
799 799  
800 800  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.
801 801  
802 -* AT+MBFUN=0: Disable Modbus fast reading.
922 +* **AT+MBFUN=0**: Disable Modbus fast reading.
803 803  
804 -Example:
924 +**Example:**
805 805  
806 806  * AT+MBFUN=1 and AT+DATACUT1/AT+DATACUT2 are not configure (0,0,0).
807 807  * 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.
808 808  * 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.
809 809  
810 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image025.png]]
930 +[[image:1654133913295-597.png]]
811 811  
812 812  
813 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image026.png]]
933 +[[image:1654133954153-643.png]]
814 814  
815 815  
816 -* Downlink Commands:
936 +* **Downlink Commands:**
817 817  
818 -A9 aa -à Same as AT+MBFUN=aa
938 +**A9 aa** ~-~-> Same as AT+MBFUN=aa
819 819  
820 820  
821 -==== RS485 command timeout ====
822 822  
942 +==== **RS485 command timeout** ====
943 +
823 823  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.
824 824  
825 825  Default value: 0, range:  0 ~~ 5 seconds
826 826  
827 827  
828 -* AT Command:
949 +* **AT Command:**
829 829  
830 -AT+CMDDLaa=hex(bb cc)
951 +(% class="box infomessage" %)
952 +(((
953 +**AT+CMDDLaa=hex(bb cc)**
954 +)))
831 831  
832 -Example:
956 +**Example:**
833 833  
834 834  **AT+CMDDL1=1000** to send the open time to 1000ms
835 835  
836 836  
837 -* Downlink Payload:
961 +* **Downlink Payload:**
838 838  
839 839  0x AA aa bb cc
840 840  
841 841  Same as: AT+CMDDLaa=hex(bb cc)
842 842  
843 - Example:
967 + **Example:**
844 844  
845 - 0xAA 01 03 E8  à Same as **AT+CMDDL1=1000 ms**
969 + **0xAA 01 03 E8**  ~-~-> Same as **AT+CMDDL1=1000 ms**
846 846  
847 847  
848 -==== [[Uplink>>path:#downlink_A8]] payload mode ====
849 849  
973 +==== **Uplink payload mode** ====
974 +
850 850  Define to use one uplink or multiple uplinks for the sampling.
851 851  
852 -The use of this command please see: [[Compose Uplink payload>>path:#DataUP]]
977 +The use of this command please see: [[Compose Uplink payload>>||anchor="H3.3.4Composetheuplinkpayload"]]
853 853  
854 -* AT Command:
979 +* **AT Command:**
855 855  
856 -AT+DATAUP=0
981 +(% class="box infomessage" %)
982 +(((
983 +**AT+DATAUP=0**
984 +)))
857 857  
858 -AT+DATAUP=1
986 +(% class="box infomessage" %)
987 +(((
988 +**AT+DATAUP=1**
989 +)))
859 859  
860 860  
861 -* Downlink Payload:
992 +* **Downlink Payload:**
862 862  
863 -0xAD 00   à Same as AT+DATAUP=0
994 +**0xAD 00**  **~-~->** Same as AT+DATAUP=0
864 864  
865 -0xAD 01   à Same as AT+DATAUP=1
996 +**0xAD 01**  **~-~->** Same as AT+DATAUP=1
866 866  
867 867  
868 -==== Manually trigger an Uplink ====
869 869  
1000 +==== **Manually trigger an Uplink** ====
1001 +
870 870  Ask device to send an uplink immediately.
871 871  
872 -* Downlink Payload:
1004 +* **Downlink Payload:**
873 873  
874 -0x08 FF, RS485-BL will immediately send an uplink.
1006 +**0x08 FF**, RS485-BL will immediately send an uplink.
875 875  
876 876  
877 -==== Clear RS485 Command ====
878 878  
1010 +==== **Clear RS485 Command** ====
1011 +
879 879  The AT+COMMANDx and AT+DATACUTx settings are stored in special location, user can use below command to clear them.
880 880  
881 881  
882 -* AT Command:
1015 +* **AT Command:**
883 883  
884 -**AT+CMDEAR=mm,nn**   mm: start position of erase ,nn: stop position of erase
1017 +(% style="color:#037691" %)**AT+CMDEAR=mm,nn** (%%) mm: start position of erase ,nn: stop position of erase Etc. AT+CMDEAR=1,10 means erase AT+COMMAND1/AT+DATACUT1 to AT+COMMAND10/AT+DATACUT10
885 885  
886 -Etc. AT+CMDEAR=1,10 means erase AT+COMMAND1/AT+DATACUT1 to AT+COMMAND10/AT+DATACUT10
887 -
888 888  Example screen shot after clear all RS485 commands. 
889 889  
890 890  
891 -
892 892  The uplink screen shot is:
893 893  
894 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png]]
1024 +[[image:1654134704555-320.png]]
895 895  
896 896  
897 -* Downlink Payload:
1027 +* **Downlink Payload:**
898 898  
899 -0x09 aa bb same as AT+CMDEAR=aa,bb
1029 +**0x09 aa bb** same as AT+CMDEAR=aa,bb
900 900  
901 901  
902 -==== Set Serial Communication Parameters ====
903 903  
1033 +==== **Set Serial Communication Parameters** ====
1034 +
904 904  Set the Rs485 serial communication parameters:
905 905  
906 -* AT Command:
1037 +* **AT Command:**
907 907  
908 908  Set Baud Rate:
909 909  
910 -AT+BAUDR=9600    ~/~/ Options: (1200,2400,4800,14400,19200,115200)
1041 +(% class="box infomessage" %)
1042 +(((
1043 +**AT+BAUDR=9600**    ~/~/ Options: (1200,2400,4800,14400,19200,115200)
1044 +)))
911 911  
1046 +Set UART Parity
912 912  
913 -Set UART parity
1048 +(% class="box infomessage" %)
1049 +(((
1050 +**AT+PARITY=0**    ~/~/ Option: 0: no parity, 1: odd parity, 2: even parity
1051 +)))
914 914  
915 -AT+PARITY=0    ~/~/ Option: 0: no parity, 1: odd parity, 2: even parity
916 -
917 -
918 918  Set STOPBIT
919 919  
920 -AT+STOPBIT=0    ~/~/ Option: 0 for 1bit; 1 for 1.5 bit ; 2 for 2 bits
1055 +(% class="box infomessage" %)
1056 +(((
1057 +**AT+STOPBIT=0**    ~/~/ Option: 0 for 1bit; 1 for 1.5 bit ; 2 for 2 bits
1058 +)))
921 921  
922 922  
923 -* Downlink Payload:
1061 +* **Downlink Payload:**
924 924  
925 -A7 01 aa bb: Same  AT+BAUDR=hex(aa bb)*100
1063 +**A7 01 aa bb**: Same  AT+BAUDR=hex(aa bb)*100
926 926  
927 -Example:
1065 +**Example:**
928 928  
929 929  * A7 01 00 60   same as AT+BAUDR=9600
930 930  * A7 01 04 80  same as AT+BAUDR=115200
... ... @@ -934,169 +934,175 @@
934 934  A7 03 aa: Same as  AT+STOPBIT=aa  (aa value: 00 , 01 or 02)
935 935  
936 936  
937 -==== Control output power duration ====
938 938  
1076 +==== **Control output power duration** ====
1077 +
939 939  User can set the output power duration before each sampling.
940 940  
941 -* AT Command:
1080 +* **AT Command:**
942 942  
943 -Example:
1082 +**Example:**
944 944  
945 -AT+3V3T=1000 ~/~/ 3V3 output power will open 1s before each sampling.
1084 +**AT+3V3T=1000**  ~/~/ 3V3 output power will open 1s before each sampling.
946 946  
947 -AT+5VT=1000 ~/~/ +5V output power will open 1s before each sampling.
1086 +**AT+5VT=1000**  ~/~/ +5V output power will open 1s before each sampling.
948 948  
949 949  
950 -* LoRaWAN Downlink Command:
1089 +* **LoRaWAN Downlink Command:**
951 951  
952 -07 01 aa bb  Same as AT+5VT=(aa bb)
1091 +**07 01 aa bb**  Same as AT+5VT=(aa bb)
953 953  
954 -07 02 aa bb  Same as AT+3V3T=(aa bb)
1093 +**07 02 aa bb**  Same as AT+3V3T=(aa bb)
955 955  
956 956  
1096 +== 3.6 Buttons ==
957 957  
1098 +(% border="1" style="background-color:#ffffcc; color:green; width:233px" %)
1099 +|=(% style="width: 89px;" %)**Button**|=(% style="width: 141px;" %)**Feature**
1100 +|(% style="width:89px" %)**RST**|(% style="width:141px" %)Reboot RS485-BL
958 958  
959 -1.
960 -11. Buttons
1102 +== 3.7 +3V3 Output ==
961 961  
962 -|**Button**|**Feature**
963 -|**RST**|Reboot RS485-BL
964 -
965 -1.
966 -11. +3V3 Output
967 -
968 968  RS485-BL has a Controllable +3V3 output, user can use this output to power external sensor.
969 969  
970 970  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. 
971 971  
972 -
973 973  The +3V3 output time can be controlled by AT Command.
974 974  
975 -**AT+3V3T=1000**
976 976  
977 -Means set +3v3 valid time to have 1000ms. So, the real +3v3 output will actually have 1000ms + sampling time for other sensors.
1111 +(% style="color:#037691" %)**AT+3V3T=1000**
978 978  
979 979  
1114 +Means set +3v3 valid time to have 1000ms. So, the real +3v3 output will actually have 1000ms + sampling time for other sensors.
1115 +
980 980  By default, the AT+3V3T=0. This is a special case, means the +3V3 output is always on at any time
981 981  
982 982  
983 -1.
984 -11. +5V Output
1119 +== 3.8 +5V Output ==
985 985  
986 986  RS485-BL has a Controllable +5V output, user can use this output to power external sensor.
987 987  
988 988  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. 
989 989  
990 -
991 991  The 5V output time can be controlled by AT Command.
992 992  
993 -**AT+5VT=1000**
994 994  
995 -Means set 5V valid time to have 1000ms. So, the real 5V output will actually have 1000ms + sampling time for other sensors.
1128 +(% style="color:#037691" %)**AT+5VT=1000**
996 996  
997 997  
1131 +Means set 5V valid time to have 1000ms. So, the real 5V output will actually have 1000ms + sampling time for other sensors.
1132 +
998 998  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.
999 999  
1000 1000  
1136 +== 3.9 LEDs ==
1001 1001  
1138 +(% border="1" style="background-color:#ffffcc; color:green; width:332px" %)
1139 +|=**LEDs**|=(% style="width: 274px;" %)**Feature**
1140 +|**LED1**|(% style="width:274px" %)Blink when device transmit a packet.
1002 1002  
1003 -1.
1004 -11. LEDs
1142 +== 3.10 Switch Jumper ==
1005 1005  
1006 -|**LEDs**|**Feature**
1007 -|**LED1**|Blink when device transmit a packet.
1008 -
1009 -1.
1010 -11. Switch Jumper
1011 -
1012 -|**Switch Jumper**|**Feature**
1013 -|**SW1**|(((
1144 +(% border="1" style="background-color:#ffffcc; color:green; width:515px" %)
1145 +|=(% style="width: 124px;" %)**Switch Jumper**|=(% style="width: 388px;" %)**Feature**
1146 +|(% style="width:124px" %)**SW1**|(% style="width:388px" %)(((
1014 1014  ISP position: Upgrade firmware via UART
1015 1015  
1016 1016  Flash position: Configure device, check running status.
1017 1017  )))
1018 -|**SW2**|(((
1151 +|(% style="width:124px" %)**SW2**|(% style="width:388px" %)(((
1019 1019  5V position: set to compatible with 5v I/O.
1020 1020  
1021 1021  3.3v position: set to compatible with 3.3v I/O.,
1022 1022  )))
1023 1023  
1024 -+3.3V: is always ON
1157 +**+3.3V**: is always ON
1025 1025  
1026 -+5V: Only open before every sampling. The time is by default, it is AT+5VT=0.  Max open time. 5000 ms.
1159 +**+5V**: Only open before every sampling. The time is by default, it is AT+5VT=0.  Max open time. 5000 ms.
1027 1027  
1028 -1. Case Study
1029 1029  
1030 -User can check this URL for some case studies.
1162 += 4. Case Study =
1031 1031  
1032 -[[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]]
1164 +User can check this URL for some case studies: [[APP RS485 COMMUNICATE WITH SENSORS>>doc:Main.Application Note \: Communicate with Different Sensors ----- RS485-LN RS485-BL.WebHome]]
1033 1033  
1034 1034  
1167 += 5. Use AT Command =
1035 1035  
1169 +== 5.1 Access AT Command ==
1036 1036  
1037 -1. Use AT Command
1038 -11. Access AT Command
1039 -
1040 1040  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.
1041 1041  
1042 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image027.png]]
1173 +[[image:1654135840598-282.png]]
1043 1043  
1044 1044  
1045 -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:
1176 +In PC, User needs to set (% style="color:blue" %)**serial tool**(%%)(such as [[putty>>url:https://www.chiark.greenend.org.uk/~~sgtatham/putty/latest.html]], SecureCRT) baud rate to (% style="color:green" %)**9600**(%%) to access to access serial console of RS485-BL. The default password is 123456. Below is the output for reference:
1046 1046  
1047 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image028.png]]
1178 +[[image:1654136105500-922.png]]
1048 1048  
1049 1049  
1181 +More detail AT Command manual can be found at [[AT Command Manual>>||anchor="3.5ConfigureRS485-BLviaATorDownlink"]]
1050 1050  
1051 -More detail AT Command manual can be found at [[AT Command Manual>>path:#AT_COMMAND]]
1052 1052  
1184 +== 5.2 Common AT Command Sequence ==
1053 1053  
1186 +=== 5.2.1 Multi-channel ABP mode (Use with SX1301/LG308) ===
1054 1054  
1055 -1.
1056 -11. Common AT Command Sequence
1057 -111. Multi-channel ABP mode (Use with SX1301/LG308)
1058 -
1059 1059  If device has not joined network yet:
1060 1060  
1061 -AT+FDR
1190 +(% class="box infomessage" %)
1191 +(((
1192 +**AT+FDR**
1193 +)))
1062 1062  
1063 -AT+NJM=0
1195 +(% class="box infomessage" %)
1196 +(((
1197 +**AT+NJM=0**
1198 +)))
1064 1064  
1065 -ATZ
1200 +(% class="box infomessage" %)
1201 +(((
1202 +**ATZ**
1203 +)))
1066 1066  
1067 1067  
1068 1068  If device already joined network:
1069 1069  
1070 -AT+NJM=0
1208 +(% class="box infomessage" %)
1209 +(((
1210 +**AT+NJM=0**
1211 +)))
1071 1071  
1072 -ATZ
1213 +(% class="box infomessage" %)
1214 +(((
1215 +**ATZ**
1216 +)))
1073 1073  
1074 -1.
1075 -11.
1076 -111. Single-channel ABP mode (Use with LG01/LG02)
1077 1077  
1078 -AT+FDR   Reset Parameters to Factory Default, Keys Reserve
1219 +=== 5.5.2 Single-channel ABP mode (Use with LG01/LG02) ===
1079 1079  
1080 -AT+NJM=0 Set to ABP mode
1081 1081  
1082 -AT+ADR=0 Set the Adaptive Data Rate Off
1222 +(% style="background-color:#dcdcdc" %)**AT+FDR** (%%) Reset Parameters to Factory Default, Keys Reserve
1083 1083  
1084 -AT+DR=5  Set Data Rate
1224 +(% style="background-color:#dcdcdc" %)**AT+NJM=0 **(%%)Set to ABP mode
1085 1085  
1086 -AT+TDC=60000  Set transmit interval to 60 seconds
1226 +(% style="background-color:#dcdcdc" %)**AT+ADR=0** (%%)Set the Adaptive Data Rate Off
1087 1087  
1088 -AT+CHS=868400000 Set transmit frequency to 868.4Mhz
1228 +(% style="background-color:#dcdcdc" %)**AT+DR=5**  (%%)Set Data Rate
1089 1089  
1090 -AT+RX2FQ=868400000 Set RX2Frequency to 868.4Mhz (according to the result from server)
1230 +(% style="background-color:#dcdcdc" %)**AT+TDC=60000** (%%) Set transmit interval to 60 seconds
1091 1091  
1092 -AT+RX2DR=5  Set RX2DR to match the downlink DR from server. see below
1232 +(% style="background-color:#dcdcdc" %)**AT+CHS=868400000**(%%) Set transmit frequency to 868.4Mhz
1093 1093  
1094 -AT+DADDR=26 01 1A F1 Set Device Address to 26 01 1A F1, this ID can be found in the LoRa Server portal.
1234 +(% style="background-color:#dcdcdc" %)**AT+RX2FQ=868400000** (%%) Set RX2Frequency to 868.4Mhz (according to the result from server)
1095 1095  
1096 -ATZ          Reset MCU
1236 +(% style="background-color:#dcdcdc" %)**AT+RX2DR=5**  (%%) Set RX2DR to match the downlink DR from server. see below
1097 1097  
1098 -**Note:**
1238 +(% style="background-color:#dcdcdc" %)**AT+DADDR=26** (%%) 01 1A F1 Set Device Address to 26 01 1A F1, this ID can be found in the LoRa Server portal.
1099 1099  
1240 +(% style="background-color:#dcdcdc" %)**ATZ**       (%%) Reset MCU
1241 +
1242 +(% style="color:red" %)**Note:**
1243 +
1100 1100  1. Make sure the device is set to ABP mode in the IoT Server.
1101 1101  1. Make sure the LG01/02 gateway RX frequency is exactly the same as AT+CHS setting.
1102 1102  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.
... ... @@ -1147,7 +1147,7 @@
1147 1147  [[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]]
1148 1148  
1149 1149  
1150 -1.
1294 +1.
1151 1151  11. How to change the LoRa Frequency Bands/Region?
1152 1152  
1153 1153  User can follow the introduction for [[how to upgrade image>>path:#upgrade_image]]. When download the images, choose the required image file for download.
... ... @@ -1154,7 +1154,7 @@
1154 1154  
1155 1155  
1156 1156  
1157 -1.
1301 +1.
1158 1158  11. How many RS485-Slave can RS485-BL connects?
1159 1159  
1160 1160  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]].
... ... @@ -1171,7 +1171,7 @@
1171 1171  
1172 1172  
1173 1173  
1174 -1.
1318 +1.
1175 1175  11. Why I can’t join TTN V3 in US915 /AU915 bands?
1176 1176  
1177 1177  It might about the channels mapping. Please see for detail.
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
1654132684752-193.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +22.8 KB
Content
1654133913295-597.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +116.2 KB
Content
1654133954153-643.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +91.2 KB
Content
1654134704555-320.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +91.4 KB
Content
1654135840598-282.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +1.3 MB
Content
1654136105500-922.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +203.7 KB
Content