Changes for page RS485-BL – Waterproof RS485 to LoRaWAN Converter
Last modified by Xiaoling on 2025/04/23 15:57
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 17 added, 0 removed)
- 1653271044481-711.png
- 1653271276735-972.png
- 1653271581490-837.png
- 1653271648378-342.png
- 1653271657255-576.png
- 1653271763403-806.png
- 1653272787040-634.png
- 1653272817147-600.png
- 1653272901032-107.png
- 1653273818896-432.png
- 1653274001211-372.png
- 1654132684752-193.png
- 1654133913295-597.png
- 1654133954153-643.png
- 1654134704555-320.png
- 1654135840598-282.png
- 1654136105500-922.png
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 ((( ... ... @@ -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 -|((( 414 +(% border="1" class="table-bordered" style="background-color:#4f81bd; color:white; width:501px" %) 415 +|(% 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 -|((( 429 +(% border="1" class="table-bordered" style="background-color:#4f81bd; color:white; width:580px" %) 430 +|(% 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: 437 +**Examples:** 426 426 427 -1 .For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49439 +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 443 +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: file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image013.png]]445 +[[image:1653271044481-711.png]] 434 434 447 +2)For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49 435 435 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 - 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 451 +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]]453 +[[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 -|((( 457 +(% style="background-color:#4f81bd; color:white; width:729px" %) 458 +|(% style="width:726px" %)((( 448 448 **AT+DATACUTx=a,b,c** 449 449 450 450 * **a: length for the return of AT+COMMAND** ... ... @@ -452,98 +452,143 @@ 452 452 * **c: define the position for valid value. ** 453 453 ))) 454 454 455 -Examples: 466 +**Examples:** 456 456 457 457 * Grab bytes: 458 458 459 -[[image: file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image015.png]]470 +[[image:1653271581490-837.png||height="313" width="722"]] 460 460 472 + 461 461 * Grab a section. 462 462 463 -[[image: file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image016.png]]475 +[[image:1653271648378-342.png||height="326" width="720"]] 464 464 477 + 465 465 * Grab different sections. 466 466 467 -[[image: file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image017.png]]480 +[[image:1653271657255-576.png||height="305" width="730"]] 468 468 482 +((( 483 +(% style="color:red" %)**Note:** 484 +))) 469 469 470 -Note: 471 - 486 +((( 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. 488 +))) 473 473 474 -Example: 490 +((( 491 +**Example:** 492 +))) 475 475 476 -AT+COMMAND1=11 01 1E D0,0 494 +((( 495 +(% style="color:red" %)AT+COMMAND1=11 01 1E D0,0 496 +))) 477 477 478 -AT+SEARCH1=1,1E 56 34 498 +((( 499 +(% style="color:red" %)AT+SEARCH1=1,1E 56 34 500 +))) 479 479 480 -AT+DATACUT1=0,2,1~~5 502 +((( 503 +(% style="color:red" %)AT+DATACUT1=0,2,1~~5 504 +))) 481 481 482 -Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49 506 +((( 507 +(% style="color:red" %)Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49 508 +))) 483 483 484 -String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49 510 +((( 511 +(% style="color:red" %)String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49 512 +))) 485 485 486 -Valid payload after DataCUT command: 2e 30 58 5f 36 514 +((( 515 +(% style="color:red" %)Valid payload after DataCUT command: 2e 30 58 5f 36 516 +))) 487 487 488 -[[image: file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image018.png]]518 +[[image:1653271763403-806.png]] 489 489 490 490 521 +=== 3.3.4 Compose the uplink payload === 491 491 492 - 493 -1. 494 -11. 495 -111. Compose the uplink payload 496 - 523 +((( 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.** 525 +))) 498 498 527 +((( 528 +(% style="color:#037691" %)**Examples: AT+DATAUP=0** 529 +))) 499 499 500 -**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 +))) 501 501 502 -Compose the uplink payload with value returns in sequence and send with **A SIGNLE UPLINK**. 503 - 535 +((( 504 504 Final Payload is 537 +))) 505 505 506 -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 +))) 507 507 543 +((( 508 508 Where PAYVER is defined by AT+PAYVER, below is an example screen shot. 545 +))) 509 509 510 -[[image: file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image019.png]]547 +[[image:1653272787040-634.png||height="515" width="719"]] 511 511 512 512 513 513 514 -**Examples: AT+DATAUP=1** 551 +((( 552 +(% style="color:#037691" %)**Examples: AT+DATAUP=1** 515 515 516 -Compose the uplink payload with value returns in sequence and send with **Multiply UPLINKs**. 554 + 555 +))) 517 517 557 +((( 558 +Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**Multiply UPLINKs**. 559 +))) 560 + 561 +((( 518 518 Final Payload is 563 +))) 519 519 520 -Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA 565 +((( 566 +(% style="color:#4f81bd" %)**Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA** 567 +))) 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 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 +))) 527 527 528 -[[image: file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image020.png]]585 +[[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 534 534 535 -DATA 2=1^^st^^~~ 6^^th^^ byte ofValidvalue ofRETURN10=02aa05810a20590 +DATA1=RETURN1 Valid Value = (% style="background-color:#4f81bd; color:white" %) 20 20 0a 33 90 41 536 536 537 -DATA 3=7^^th^^ ~~11^^th^^ bytesof Valid value of RETURN10 =202020 2d 30592 +DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10= (% style="background-color:#4f81bd; color:white" %)02 aa 05 81 0a 20 538 538 594 +DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 =(% style="background-color:#4f81bd; color:white" %) 20 20 20 2d 30 539 539 540 540 541 541 Below are the uplink payloads: 542 542 543 -[[image: file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image021.png]]599 +[[image:1653272901032-107.png]] 544 544 545 545 546 -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: 547 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 ... ... @@ -555,139 +555,186 @@ 555 555 556 556 557 557 558 -1. 559 -11. 560 -111. Uplink on demand 614 +=== 3.3.5 Uplink on demand === 561 561 616 +((( 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. 618 +))) 563 563 620 +((( 564 564 Downlink control command: 622 +))) 565 565 566 -[[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 +))) 567 567 568 -[[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. 569 569 631 + 632 +))) 570 570 634 +=== 3.3.6 Uplink on Interrupt === 571 571 572 -1. 573 -11. 574 -111. Uplink on Interrupt 636 +Put the interrupt sensor between 3.3v_out and GPIO ext. 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]]638 +[[image:1653273818896-432.png]] 577 577 640 + 641 +((( 578 578 AT+INTMOD=0 Disable Interrupt 643 +))) 579 579 645 +((( 580 580 AT+INTMOD=1 Interrupt trigger by rising or falling edge. 647 +))) 581 581 649 +((( 582 582 AT+INTMOD=2 Interrupt trigger by falling edge. ( Default Value) 651 +))) 583 583 653 +((( 584 584 AT+INTMOD=3 Interrupt trigger by rising edge. 585 585 656 + 657 +))) 586 586 587 -1. 588 -11. Uplink Payload 659 +== 3.4 Uplink Payload == 589 589 590 -|**Size(bytes)**|**2**|**1**|**Length depends on the return from the commands** 591 -|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 +((( 592 592 Battery(mV) 666 +))) 593 593 668 +((( 594 594 & 670 +))) 595 595 672 +((( 596 596 Interrupt _Flag 597 -)))|((( 674 +))) 675 +)))|(% 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. 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. 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 683 +((( 684 +{{{function Decoder(bytes, port) {}}} 685 +))) 605 605 606 -function Decoder(bytes, port) { 687 +((( 688 +{{{//Payload Formats of RS485-BL Deceive}}} 689 +))) 607 607 608 -~/~/Payload Formats of RS485-BL Deceive 691 +((( 692 +{{{return {}}} 693 +))) 609 609 610 -return { 695 +((( 696 +{{{ //Battery,units:V}}} 697 +))) 611 611 612 - ~/~/Battery,units:V 699 +((( 700 +{{{ BatV:((bytes[0]<<8 | bytes[1])&0x7fff)/1000,}}} 701 +))) 613 613 614 - BatV:((bytes[0]<<8 | bytes[1])&0x7fff)/1000, 703 +((( 704 +{{{ //GPIO_EXTI }}} 705 +))) 615 615 616 - ~/~/GPIO_EXTI 707 +((( 708 +{{{ EXTI_Trigger:(bytes[0] & 0x80)? "TRUE":"FALSE",}}} 709 +))) 617 617 618 - EXTI_Trigger:(bytes[0] & 0x80)? "TRUE":"FALSE", 711 +((( 712 +{{{ //payload of version}}} 713 +))) 619 619 620 - ~/~/payload of version 715 +((( 716 +{{{ Pay_ver:bytes[2],}}} 717 +))) 621 621 622 - Pay_ver:bytes[2], 719 +((( 720 +{{{ }; }}} 721 +))) 623 623 624 - }; 723 +((( 724 +} 625 625 626 - } 726 + 727 +))) 627 627 628 - 629 - 630 - 631 - 632 - 633 - 729 +((( 634 634 TTN V3 uplink screen shot. 731 +))) 635 635 636 -[[image: file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png]]733 +[[image:1653274001211-372.png||height="192" width="732"]] 637 637 638 -1. 639 -11. Configure RS485-BL via AT or Downlink 640 640 641 - Usercanconfigure RS485-BL via[[ATCommands >>path:#_Using_the_AT]]orLoRaWANDownlinkCommands736 +== 3.5 Configure RS485-BL via AT or Downlink == 642 642 738 +User can configure RS485-BL via AT Commands or LoRaWAN Downlink Commands 739 + 643 643 There are two kinds of Commands: 644 644 645 -* **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_Commands742 +* (% 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]] 646 646 647 -* **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: 648 648 649 -1. 650 -11. 651 -111. Common Commands: 746 +=== 3.5.1 Common Commands: === 652 652 653 -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]] 654 654 655 655 656 -1. 657 -11. 658 -111. Sensor related commands: 751 +=== 3.5.2 Sensor related commands: === 659 659 660 -==== ChooseDeviceType (RS485 or TTL)====753 +==== ==== 661 661 755 +==== **Choose Device Type (RS485 or TTL)** ==== 756 + 662 662 RS485-BL can connect to either RS485 sensors or TTL sensor. User need to specify what type of sensor need to connect. 663 663 664 -* AT Command 759 +* **AT Command** 665 665 761 +(% class="box infomessage" %) 762 +((( 666 666 **AT+MOD=1** ~/~/ Set to support RS485-MODBUS type sensors. User can connect multiply RS485 , Modbus sensors to the A / B pins. 764 +))) 667 667 766 +(% class="box infomessage" %) 767 +((( 668 668 **AT+MOD=2** ~/~/ Set to support TTL Level sensors, User can connect one TTL Sensor to the TXD/RXD/GND pins. 769 +))) 669 669 670 670 671 -* Downlink Payload 772 +* **Downlink Payload** 672 672 673 -**0A aa** àsame as AT+MOD=aa774 +**0A aa** ~-~-> same as AT+MOD=aa 674 674 675 675 676 676 677 -==== [[RS485 Debug Command>>path:#downlink_A8]](AT+CFGDEV) ====778 +==== **RS485 Debug Command (AT+CFGDEV)** ==== 678 678 679 679 This command is used to configure the RS485 or TTL sensors; they won’t be used during sampling. 680 680 681 -* AT Command 782 +* **AT Command** 682 682 683 -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 +))) 684 684 685 685 m: 0: no CRC; 1: add CRC-16/MODBUS in the end of this command. 686 686 687 687 792 +* **Downlink Payload** 688 688 689 -* Downlink Payload 690 - 691 691 Format: A8 MM NN XX XX XX XX YY 692 692 693 693 Where: ... ... @@ -701,15 +701,15 @@ 701 701 702 702 To connect a Modbus Alarm with below commands. 703 703 704 -* 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. 705 705 706 -* 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. 707 707 708 708 So if user want to use downlink command to control to RS485 Alarm, he can use: 709 709 710 -**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 711 711 712 -**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 713 713 714 714 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. 715 715 ... ... @@ -718,48 +718,60 @@ 718 718 719 719 Check TTL Sensor return: 720 720 721 -[[image: file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image024.png]]824 +[[image:1654132684752-193.png]] 722 722 723 723 724 724 828 +==== **Set Payload version** ==== 725 725 726 -==== Set Payload version ==== 727 - 728 728 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. 729 729 730 -* AT Command: 832 +* **AT Command:** 731 731 732 -AT+PAYVER: Set PAYVER field = 1 834 +(% class="box infomessage" %) 835 +((( 836 +**AT+PAYVER: Set PAYVER field = 1** 837 +))) 733 733 734 734 735 -* Downlink Payload: 840 +* **Downlink Payload:** 736 736 737 -0xAE 01 àSet PAYVER field = 0x01842 +**0xAE 01** ~-~-> Set PAYVER field = 0x01 738 738 739 -0xAE 0F àSet PAYVER field = 0x0F844 +**0xAE 0F** ~-~-> Set PAYVER field = 0x0F 740 740 741 741 742 -==== Set RS485 Sampling Commands ==== 743 743 848 +==== **Set RS485 Sampling Commands** ==== 849 + 744 744 AT+COMMANDx, AT+DATACUTx and AT+SEARCHx 745 745 746 -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"]]. 747 747 748 748 749 -* AT Command: 855 +* **AT Command:** 750 750 751 -AT+COMMANDx: Configure RS485 read command to sensor. 857 +(% class="box infomessage" %) 858 +((( 859 +**AT+COMMANDx: Configure RS485 read command to sensor.** 860 +))) 752 752 753 -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 +))) 754 754 755 -AT+SEARCHx: Configure search command 867 +(% class="box infomessage" %) 868 +((( 869 +**AT+SEARCHx: Configure search command** 870 +))) 756 756 757 757 758 -* Downlink Payload: 873 +* **Downlink Payload:** 759 759 760 -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. 761 761 762 -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. 763 763 764 764 Format: AF MM NN LL XX XX XX XX YY 765 765 ... ... @@ -766,23 +766,23 @@ 766 766 Where: 767 767 768 768 * MM: the ATCOMMAND or AT+DATACUT to be set. Value from 01 ~~ 0F, 769 -* NN: 0: no CRC; 1: add CRC-16/MODBUS ; 2: set the AT+DATACUT value. 770 -* 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 771 771 * XX XX XX XX: AT+COMMAND or AT+DATACUT command 772 -* 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. 773 773 774 -Example: 889 +**Example:** 775 775 776 -**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 777 777 778 -**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** 779 779 780 -**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** 781 781 782 782 783 -0xAB downlink command can be used for set AT+SEARCHx 898 +**0xAB** downlink command can be used for set AT+SEARCHx 784 784 785 -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 786 786 787 787 * AB aa 01 03 xx xx xx same as AT+SEARCHaa=1,xx xx xx 788 788 * 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 ... ... @@ -790,145 +790,164 @@ 790 790 **AB aa 02 03 xx xx xx 02 yy yy** same as **AT+SEARCHaa=2,xx xx xx+yy yy** 791 791 792 792 793 -==== Fast command to handle MODBUS device ==== 794 794 909 +==== **Fast command to handle MODBUS device** ==== 910 + 795 795 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]]. 796 796 797 797 This command is valid since v1.3 firmware version 798 798 799 799 800 -AT+MBFUN has only two value: 916 +**AT+MBFUN has only two value:** 801 801 802 -* 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 803 803 804 804 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. 805 805 806 -* AT+MBFUN=0: Disable Modbus fast reading. 922 +* **AT+MBFUN=0**: Disable Modbus fast reading. 807 807 808 -Example: 924 +**Example:** 809 809 810 810 * AT+MBFUN=1 and AT+DATACUT1/AT+DATACUT2 are not configure (0,0,0). 811 811 * 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. 812 812 * 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. 813 813 814 -[[image: file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image025.png]]930 +[[image:1654133913295-597.png]] 815 815 816 816 817 -[[image: file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image026.png]]933 +[[image:1654133954153-643.png]] 818 818 819 819 820 -* Downlink Commands: 936 +* **Downlink Commands:** 821 821 822 -A9 aa - àSame as AT+MBFUN=aa938 +**A9 aa** ~-~-> Same as AT+MBFUN=aa 823 823 824 824 825 -==== RS485 command timeout ==== 826 826 942 +==== **RS485 command timeout** ==== 943 + 827 827 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. 828 828 829 829 Default value: 0, range: 0 ~~ 5 seconds 830 830 831 831 832 -* AT Command: 949 +* **AT Command:** 833 833 834 -AT+CMDDLaa=hex(bb cc) 951 +(% class="box infomessage" %) 952 +((( 953 +**AT+CMDDLaa=hex(bb cc)** 954 +))) 835 835 836 -Example: 956 +**Example:** 837 837 838 838 **AT+CMDDL1=1000** to send the open time to 1000ms 839 839 840 840 841 -* Downlink Payload: 961 +* **Downlink Payload:** 842 842 843 843 0x AA aa bb cc 844 844 845 845 Same as: AT+CMDDLaa=hex(bb cc) 846 846 847 - Example: 967 + **Example:** 848 848 849 - 0xAA 01 03 E8 àSame as **AT+CMDDL1=1000 ms**969 + **0xAA 01 03 E8** ~-~-> Same as **AT+CMDDL1=1000 ms** 850 850 851 851 852 -==== [[Uplink>>path:#downlink_A8]] payload mode ==== 853 853 973 +==== **Uplink payload mode** ==== 974 + 854 854 Define to use one uplink or multiple uplinks for the sampling. 855 855 856 -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"]] 857 857 858 -* AT Command: 979 +* **AT Command:** 859 859 860 -AT+DATAUP=0 981 +(% class="box infomessage" %) 982 +((( 983 +**AT+DATAUP=0** 984 +))) 861 861 862 -AT+DATAUP=1 986 +(% class="box infomessage" %) 987 +((( 988 +**AT+DATAUP=1** 989 +))) 863 863 864 864 865 -* Downlink Payload: 992 +* **Downlink Payload:** 866 866 867 -0xAD 00 àSame as AT+DATAUP=0994 +**0xAD 00** **~-~->** Same as AT+DATAUP=0 868 868 869 -0xAD 01 àSame as AT+DATAUP=1996 +**0xAD 01** **~-~->** Same as AT+DATAUP=1 870 870 871 871 872 -==== Manually trigger an Uplink ==== 873 873 1000 +==== **Manually trigger an Uplink** ==== 1001 + 874 874 Ask device to send an uplink immediately. 875 875 876 -* Downlink Payload: 1004 +* **Downlink Payload:** 877 877 878 -0x08 FF, RS485-BL will immediately send an uplink. 1006 +**0x08 FF**, RS485-BL will immediately send an uplink. 879 879 880 880 881 -==== Clear RS485 Command ==== 882 882 1010 +==== **Clear RS485 Command** ==== 1011 + 883 883 The AT+COMMANDx and AT+DATACUTx settings are stored in special location, user can use below command to clear them. 884 884 885 885 886 -* AT Command: 1015 +* **AT Command:** 887 887 888 -**AT+CMDEAR=mm,nn** 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 889 889 890 -Etc. AT+CMDEAR=1,10 means erase AT+COMMAND1/AT+DATACUT1 to AT+COMMAND10/AT+DATACUT10 891 - 892 892 Example screen shot after clear all RS485 commands. 893 893 894 894 895 - 896 896 The uplink screen shot is: 897 897 898 -[[image: file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png]]1024 +[[image:1654134704555-320.png]] 899 899 900 900 901 -* Downlink Payload: 1027 +* **Downlink Payload:** 902 902 903 -0x09 aa bb same as AT+CMDEAR=aa,bb 1029 +**0x09 aa bb** same as AT+CMDEAR=aa,bb 904 904 905 905 906 -==== Set Serial Communication Parameters ==== 907 907 1033 +==== **Set Serial Communication Parameters** ==== 1034 + 908 908 Set the Rs485 serial communication parameters: 909 909 910 -* AT Command: 1037 +* **AT Command:** 911 911 912 912 Set Baud Rate: 913 913 914 -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 +))) 915 915 1046 +Set UART Parity 916 916 917 -Set UART parity 1048 +(% class="box infomessage" %) 1049 +((( 1050 +**AT+PARITY=0** ~/~/ Option: 0: no parity, 1: odd parity, 2: even parity 1051 +))) 918 918 919 -AT+PARITY=0 ~/~/ Option: 0: no parity, 1: odd parity, 2: even parity 920 - 921 - 922 922 Set STOPBIT 923 923 924 -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 +))) 925 925 926 926 927 -* Downlink Payload: 1061 +* **Downlink Payload:** 928 928 929 -A7 01 aa bb: Same AT+BAUDR=hex(aa bb)*100 1063 +**A7 01 aa bb**: Same AT+BAUDR=hex(aa bb)*100 930 930 931 -Example: 1065 +**Example:** 932 932 933 933 * A7 01 00 60 same as AT+BAUDR=9600 934 934 * A7 01 04 80 same as AT+BAUDR=115200 ... ... @@ -938,127 +938,119 @@ 938 938 A7 03 aa: Same as AT+STOPBIT=aa (aa value: 00 , 01 or 02) 939 939 940 940 941 -==== Control output power duration ==== 942 942 1076 +==== **Control output power duration** ==== 1077 + 943 943 User can set the output power duration before each sampling. 944 944 945 -* AT Command: 1080 +* **AT Command:** 946 946 947 -Example: 1082 +**Example:** 948 948 949 -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. 950 950 951 -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. 952 952 953 953 954 -* LoRaWAN Downlink Command: 1089 +* **LoRaWAN Downlink Command:** 955 955 956 -07 01 aa bb Same as AT+5VT=(aa bb) 1091 +**07 01 aa bb** Same as AT+5VT=(aa bb) 957 957 958 -07 02 aa bb Same as AT+3V3T=(aa bb) 1093 +**07 02 aa bb** Same as AT+3V3T=(aa bb) 959 959 960 960 1096 +== 3.6 Buttons == 961 961 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 962 962 963 -1. 964 -11. Buttons 1102 +== 3.7 +3V3 Output == 965 965 966 -|**Button**|**Feature** 967 -|**RST**|Reboot RS485-BL 968 - 969 -1. 970 -11. +3V3 Output 971 - 972 972 RS485-BL has a Controllable +3V3 output, user can use this output to power external sensor. 973 973 974 974 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. 975 975 976 - 977 977 The +3V3 output time can be controlled by AT Command. 978 978 979 -**AT+3V3T=1000** 980 980 981 - Meansset+3v3 valid timetohave 1000ms. So, thereal+3v3output will actually have1000ms + sampling time for other sensors.1111 +(% style="color:#037691" %)**AT+3V3T=1000** 982 982 983 983 1114 +Means set +3v3 valid time to have 1000ms. So, the real +3v3 output will actually have 1000ms + sampling time for other sensors. 1115 + 984 984 By default, the AT+3V3T=0. This is a special case, means the +3V3 output is always on at any time 985 985 986 986 987 -1. 988 -11. +5V Output 1119 +== 3.8 +5V Output == 989 989 990 990 RS485-BL has a Controllable +5V output, user can use this output to power external sensor. 991 991 992 992 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. 993 993 994 - 995 995 The 5V output time can be controlled by AT Command. 996 996 997 -**AT+5VT=1000** 998 998 999 - Meansset5V valid timetohave 1000ms. So, thereal5Voutput will actually have1000ms + sampling time for other sensors.1128 +(% style="color:#037691" %)**AT+5VT=1000** 1000 1000 1001 1001 1131 +Means set 5V valid time to have 1000ms. So, the real 5V output will actually have 1000ms + sampling time for other sensors. 1132 + 1002 1002 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. 1003 1003 1004 1004 1136 +== 3.9 LEDs == 1005 1005 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. 1006 1006 1007 -1. 1008 -11. LEDs 1142 +== 3.10 Switch Jumper == 1009 1009 1010 -|**LEDs**|**Feature** 1011 -|**LED1**|Blink when device transmit a packet. 1012 - 1013 -1. 1014 -11. Switch Jumper 1015 - 1016 -|**Switch Jumper**|**Feature** 1017 -|**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" %)((( 1018 1018 ISP position: Upgrade firmware via UART 1019 1019 1020 1020 Flash position: Configure device, check running status. 1021 1021 ))) 1022 -|**SW2**|((( 1151 +|(% style="width:124px" %)**SW2**|(% style="width:388px" %)((( 1023 1023 5V position: set to compatible with 5v I/O. 1024 1024 1025 1025 3.3v position: set to compatible with 3.3v I/O., 1026 1026 ))) 1027 1027 1028 -+3.3V: is always ON 1157 +**+3.3V**: is always ON 1029 1029 1030 -+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. 1031 1031 1032 -1. Case Study 1033 1033 1034 - Usercancheck this URL for some casestudies.1162 += 4. Case Study = 1035 1035 1036 - [[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]] 1037 1037 1038 1038 1167 += 5. Use AT Command = 1039 1039 1169 +== 5.1 Access AT Command == 1040 1040 1041 -1. Use AT Command 1042 -11. Access AT Command 1043 - 1044 1044 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. 1045 1045 1046 -[[image: file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image027.png]]1173 +[[image:1654135840598-282.png]] 1047 1047 1048 1048 1049 -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: 1050 1050 1051 -[[image: file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image028.png]]1178 +[[image:1654136105500-922.png]] 1052 1052 1053 1053 1181 +More detail AT Command manual can be found at [[AT Command Manual>>||anchor="3.5ConfigureRS485-BLviaATorDownlink"]] 1054 1054 1055 -More detail AT Command manual can be found at [[AT Command Manual>>path:#AT_COMMAND]] 1056 1056 1057 1057 1185 +== 5.2 Common AT Command Sequence == 1058 1058 1059 -1. 1060 -11. Common AT Command Sequence 1061 -111. Multi-channel ABP mode (Use with SX1301/LG308) 1187 +=== 5.2.1 Multi-channel ABP mode (Use with SX1301/LG308) === 1062 1062 1063 1063 If device has not joined network yet: 1064 1064 ... ... @@ -1075,8 +1075,8 @@ 1075 1075 1076 1076 ATZ 1077 1077 1078 -1. 1079 -11. 1204 +1. 1205 +11. 1080 1080 111. Single-channel ABP mode (Use with LG01/LG02) 1081 1081 1082 1082 AT+FDR Reset Parameters to Factory Default, Keys Reserve ... ... @@ -1151,7 +1151,7 @@ 1151 1151 [[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]] 1152 1152 1153 1153 1154 -1. 1280 +1. 1155 1155 11. How to change the LoRa Frequency Bands/Region? 1156 1156 1157 1157 User can follow the introduction for [[how to upgrade image>>path:#upgrade_image]]. When download the images, choose the required image file for download. ... ... @@ -1158,7 +1158,7 @@ 1158 1158 1159 1159 1160 1160 1161 -1. 1287 +1. 1162 1162 11. How many RS485-Slave can RS485-BL connects? 1163 1163 1164 1164 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]]. ... ... @@ -1175,7 +1175,7 @@ 1175 1175 1176 1176 1177 1177 1178 -1. 1304 +1. 1179 1179 11. Why I can’t join TTN V3 in US915 /AU915 bands? 1180 1180 1181 1181 It might about the channels mapping. Please see for detail.
- 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
- 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