Changes for page RS485-LN – RS485 to LoRaWAN Converter User Manual
Last modified by Xiaoling on 2025/04/23 15:56
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 18 removed)
- 1654157342174-798.png
- 1654158783574-851.png
- 1654159460680-153.png
- 1654160691922-496.png
- 1654162355560-817.png
- 1654162368066-342.png
- 1654162478620-421.png
- 1654162535040-878.png
- image-20220602163333-5.png
- image-20220602165351-6.png
- image-20220602165351-7.png
- image-20220602171200-8.png
- image-20220602171200-9.png
- image-20220602175638-10.png
- image-20220602175743-11.png
- image-20220602175818-12.png
- image-20220602175848-13.png
- image-20220602175912-14.png
Details
- Page properties
-
- Content
-
... ... @@ -6,18 +6,12 @@ 6 6 **RS485-LN – RS485 to LoRaWAN Converter User Manual** 7 7 8 8 9 - 10 - 11 11 **Table of Contents:** 12 12 13 -{{toc/}} 14 14 15 15 16 16 17 17 18 - 19 - 20 - 21 21 = 1.Introduction = 22 22 23 23 == 1.1 What is RS485-LN RS485 to LoRaWAN Converter == ... ... @@ -80,7 +80,7 @@ 80 80 * Preamble detection. 81 81 * 127 dB Dynamic Range RSSI. 82 82 * Automatic RF Sense and CAD with ultra-fast AFC. 83 -* Packet engine up to 256 bytes with CRC 77 +* Packet engine up to 256 bytes with CRC. 84 84 85 85 == 1.3 Features == 86 86 ... ... @@ -165,7 +165,7 @@ 165 165 [[image:1653268227651-549.png||height="592" width="720"]] 166 166 167 167 ((( 168 -The LG308 is already set to connect to [[TTN V3 network >>path: https://www.thethingsnetwork.org/]]. So what we need to now is only configure the TTN V3:162 +The LG308 is already set to connect to [[TTN V3 network >>path:eu1.cloud.thethings.network/]]. So what we need to now is only configure the TTN V3: 169 169 ))) 170 170 171 171 ((( ... ... @@ -217,7 +217,7 @@ 217 217 218 218 ((( 219 219 ((( 220 -There are plenty of RS485 devices in the market and each device has different command to read the valid data. To support these devices in flexible, RS485-LN supports flexible command set. User can use [[AT Commands>> ||anchor="H3.5ConfigureRS485-BLviaATorDownlink"]] or LoRaWAN Downlink Command to configure what commands RS485-LN should send for each sampling and how to handle the return from RS485 devices.214 +There are plenty of RS485 devices in the market and each device has different command to read the valid data. To support these devices in flexible, RS485-LN supports flexible command set. User can use [[AT Commands>>path:#AT_COMMAND]] or LoRaWAN Downlink Command to configure what commands RS485-LN should send for each sampling and how to handle the return from RS485 devices. 221 221 ))) 222 222 223 223 ((( ... ... @@ -289,7 +289,6 @@ 289 289 ))) 290 290 ))) 291 291 292 - 293 293 === 3.3.2 Configure sensors === 294 294 295 295 ((( ... ... @@ -308,7 +308,6 @@ 308 308 mm: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command 309 309 )))|(% style="width:256px" %)AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m 310 310 311 - 312 312 === 3.3.3 Configure read commands for each sampling === 313 313 314 314 ((( ... ... @@ -424,7 +424,6 @@ 424 424 425 425 (% style="color:#4f81bd" %)**Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA** 426 426 427 - 428 428 1. PAYVER: Defined by AT+PAYVER 429 429 1. PAYLOAD COUNT: Total how many uplinks of this sampling. 430 430 1. PAYLOAD#: Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT) ... ... @@ -470,78 +470,125 @@ 470 470 471 471 472 472 473 -=== 3.3.6 Uplink on Interrupt === 464 +1. 465 +11. 466 +111. Uplink on Interrupt 474 474 475 - RS485-LN supportexternalInterruptuplinksincehardwarev1.2release.468 +Put the interrupt sensor between 3.3v_out and GPIO ext.[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image022.png]] 476 476 477 - [[image:1654157342174-798.png]]470 +AT+INTMOD=0 Disable Interrupt 478 478 479 - ConnecttheInterruptpinto RS485-LN INT port and connect the GND pin to V- port.Whenthereisa highvoltage(Max 24v) on INT pin. Device willsend an uplinkpacket.472 +AT+INTMOD=1 Interrupt trigger by rising or falling edge. 480 480 474 +AT+INTMOD=2 Interrupt trigger by falling edge. ( Default Value) 481 481 482 -= =3.4UplinkPayload==476 +AT+INTMOD=3 Interrupt trigger by rising edge. 483 483 484 -(% border="1" style="background-color:#4bacc6; color:white; width:734px" %) 485 -|**Size(bytes)**|(% style="width:120px" %)**2**|(% style="width:116px" %)**1**|(% style="width:386px" %)**Length depends on the return from the commands** 486 -|Value|(% style="width:120px" %)((( 478 + 479 +1. 480 +11. Uplink Payload 481 + 482 +|**Size(bytes)**|**2**|**1**|**Length depends on the return from the commands** 483 +|Value|((( 487 487 Battery(mV) 488 488 489 489 & 490 490 491 491 Interrupt _Flag 492 -)))|( % style="width:116px" %)(((489 +)))|((( 493 493 PAYLOAD_VER 494 494 495 495 496 -)))| (% style="width:386px" %)If the valid payload is too long and exceed the maximum support payload length in server, server will show payload not provided in the LoRaWAN server.493 +)))|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. 497 497 498 498 Below is the decoder for the first 3 bytes. The rest bytes are dynamic depends on different RS485 sensors. 499 499 500 500 501 - == 3.5 Configure RS485-BL viaATorDownlink==498 +function Decoder(bytes, port) { 502 502 503 - UsercanconfigureRS485-LNvia AT Commands or LoRaWANDownlink Commands500 +~/~/Payload Formats of RS485-BL Deceive 504 504 502 +return { 503 + 504 + ~/~/Battery,units:V 505 + 506 + BatV:((bytes[0]<<8 | bytes[1])&0x7fff)/1000, 507 + 508 + ~/~/GPIO_EXTI 509 + 510 + EXTI_Trigger:(bytes[0] & 0x80)? "TRUE":"FALSE", 511 + 512 + ~/~/payload of version 513 + 514 + Pay_ver:bytes[2], 515 + 516 + }; 517 + 518 + } 519 + 520 + 521 + 522 + 523 + 524 + 525 + 526 +TTN V3 uplink screen shot. 527 + 528 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png]] 529 + 530 +1. 531 +11. Configure RS485-BL via AT or Downlink 532 + 533 +User can configure RS485-BL via [[AT Commands >>path:#_Using_the_AT]]or LoRaWAN Downlink Commands 534 + 505 505 There are two kinds of Commands: 506 506 507 -* (% 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:[[AT Commands and DownlinkCommand>>doc:Main.End.WebHome]]537 +* **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 508 508 509 -* (% style="color:#4f81bd" %)**Sensor Related Commands**(%%): These commands are special designed for RS485-LN. User can see these commands below:539 +* **Sensor Related Commands**: These commands are special designed for RS485-BL. User can see these commands below: 510 510 541 +1. 542 +11. 543 +111. Common Commands: 511 511 512 - ===3.5.1CommonCommands ===545 +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]] 513 513 514 -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]] 515 515 548 +1. 549 +11. 550 +111. Sensor related commands: 516 516 517 -=== 3.5.2 Sensorrelatedcommands===552 +==== Choose Device Type (RS485 or TTL) ==== 518 518 519 -R esponsefeatureisaddedtotheserver'sdownlink,aspecialpackagewithFPort of200 will beuploadedimmediatelyafterreceiving the data sent by theserver.554 +RS485-BL can connect to either RS485 sensors or TTL sensor. User need to specify what type of sensor need to connect. 520 520 521 - [[image:image-20220602163333-5.png||height="263" width="1160"]]556 +* AT Command 522 522 523 -T hefirstbyte ofthisackage representswhethertheconfiguration issuccessful,00 represents failure,01 representssuccess. Exceptforthe first byte,theotheris the previousdownlink. (All commandsexceptA8typecommandsareapplicable)558 +**AT+MOD=1** ~/~/ Set to support RS485-MODBUS type sensors. User can connect multiply RS485 , Modbus sensors to the A / B pins. 524 524 560 +**AT+MOD=2** ~/~/ Set to support TTL Level sensors, User can connect one TTL Sensor to the TXD/RXD/GND pins. 525 525 526 -=== 3.5.3 Sensor related commands === 527 527 563 +* Downlink Payload 528 528 565 +**0A aa** à same as AT+MOD=aa 529 529 530 -==== **RS485 Debug Command** ==== 531 531 532 -This command is used to configure the RS485 devices; they won’t be used during sampling. 533 533 534 - ***ATCommand**569 +==== [[RS485 Debug Command>>path:#downlink_A8]] (AT+CFGDEV) ==== 535 535 536 -(% class="box infomessage" %) 537 -((( 538 -**AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m** 539 -))) 571 +This command is used to configure the RS485 or TTL sensors; they won’t be used during sampling. 540 540 541 - m:0:noCRC, 1: add CRC-16/MODBUS in the endof this command573 +* AT Command 542 542 543 - * **DownlinkPayload**575 +AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m 544 544 577 +m: 0: no CRC; 1: add CRC-16/MODBUS in the end of this command. 578 + 579 + 580 + 581 +* Downlink Payload 582 + 545 545 Format: A8 MM NN XX XX XX XX YY 546 546 547 547 Where: ... ... @@ -549,12 +549,9 @@ 549 549 * MM: 1: add CRC-16/MODBUS ; 0: no CRC 550 550 * NN: The length of RS485 command 551 551 * XX XX XX XX: RS485 command total NN bytes 552 -* YY: How many bytes will be uplink from the return of this RS485 command, 553 -** if YY=0, RS485-LN will execute the downlink command without uplink; 554 -** if YY>0, RS485-LN will uplink total YY bytes from the output of this RS485 command; Fport=200 555 -** if YY=FF, RS485-LN will uplink RS485 output with the downlink command content; Fport=200. 590 +* YY: How many bytes will be uplink from the return of this RS485 command, if YY=0, RS485-BL will execute the downlink command without uplink; if YY>0, RS485-BL will uplink total YY bytes from the output of this RS485 command 556 556 557 -**Example 1** ~-~-> Configure without ask for uplink (YY=0)592 +**Example 1:** 558 558 559 559 To connect a Modbus Alarm with below commands. 560 560 ... ... @@ -564,190 +564,184 @@ 564 564 565 565 So if user want to use downlink command to control to RS485 Alarm, he can use: 566 566 567 - (% style="color:#4f81bd" %)**A8 01 06 0A 05 00 04 00 01 00**(%%): to activate the RS485 Alarm602 +**A8 01 06 0A 05 00 04 00 01 00**: to activate the RS485 Alarm 568 568 569 - (% style="color:#4f81bd" %)**A8 01 06 0A 05 00 04 00 00 00**(%%): to deactivate the RS485 Alarm604 +**A8 01 06 0A 05 00 04 00 00 00**: to deactivate the RS485 Alarm 570 570 571 571 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. 572 572 573 573 574 -**Example 2** ~-~-> Configure with requesting uplink and original downlink command (**YY=FF**)609 +**Example 2:** 575 575 576 - Userin IoTserver send a downlinkcommand: (% style="color:#4f81bd" %)**A8 01 06 0A 08 00 04 00 01 YY**611 +Check TTL Sensor return: 577 577 613 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image024.png]] 578 578 579 -RS485-LN got this downlink command and send (% style="color:#4f81bd" %)**0A 08 00 04 00 01 **(%%)to Modbus network. One of the RS485 sensor in the network send back Modbus reply **0A 08 00 04 00 00**. RS485-LN get this reply and combine with the original downlink command and uplink. The uplink message is: 580 580 581 - **A8** (% style="color:#4f81bd" %)**0A 08 00 04 00 **(% style="color:red" %)**01 06** ** **(% style="color:green" %)**0A 08 00 04 00 00** 582 582 583 - [[image:1654159460680-153.png]] 584 584 618 +==== Set Payload version ==== 585 585 586 - 587 -==== **Set Payload version** ==== 588 - 589 589 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. 590 590 591 -* **AT Command:**622 +* AT Command: 592 592 593 -(% class="box infomessage" %) 594 -((( 595 -**AT+PAYVER: Set PAYVER field = 1** 596 -))) 624 +AT+PAYVER: Set PAYVER field = 1 597 597 598 -* **Downlink Payload:** 599 599 600 -* *0xAE01**~-~-> SetPAYVER field= 0x01627 +* Downlink Payload: 601 601 602 - **0xAE 0F**~-~->Set PAYVER field = 0x0F629 +0xAE 01 à Set PAYVER field = 0x01 603 603 631 +0xAE 0F à Set PAYVER field = 0x0F 604 604 605 605 606 -==== **Set RS485 Sampling Commands**====634 +==== Set RS485 Sampling Commands ==== 607 607 608 -AT+COMMANDx orAT+DATACUTx636 +AT+COMMANDx, AT+DATACUTx and AT+SEARCHx 609 609 610 -These three commands are used to configure how the RS485-L Npolling data from Modbus device. Detail of usage please see : [[polling RS485 device>>||anchor="H3.3.3Configurereadcommandsforeachsampling"]].638 +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]]. 611 611 612 612 613 -* **AT Command:**641 +* AT Command: 614 614 615 -(% class="box infomessage" %) 616 -((( 617 -**AT+COMMANDx: Configure RS485 read command to sensor.** 618 -))) 643 +AT+COMMANDx: Configure RS485 read command to sensor. 619 619 620 -(% class="box infomessage" %) 621 -((( 622 -**AT+DATACUTx: Configure how to handle return from RS485 devices.** 623 -))) 645 +AT+DATACUTx: Configure how to handle return from RS485 devices. 624 624 647 +AT+SEARCHx: Configure search command 625 625 626 -* **Downlink Payload:** 627 627 628 -* *0xAF**downlinkcommandcan be used to set AT+COMMANDx or AT+DATACUTx.650 +* Downlink Payload: 629 629 630 - (%style="color:red"%)**Note**(%%):ifuseruse AT+COMMANDxtoadd a new command, he also need to sendAT+DATACUTxdownlink.652 +0xAF downlink command can be used to set AT+COMMANDx or AT+DATACUTx. 631 631 654 +Note: if user use AT+COMMANDx to add a new command, he also need to send AT+DATACUTx downlink. 655 + 632 632 Format: AF MM NN LL XX XX XX XX YY 633 633 634 634 Where: 635 635 636 636 * MM: the ATCOMMAND or AT+DATACUT to be set. Value from 01 ~~ 0F, 637 -* NN: 638 -* LL: 661 +* NN: 0: no CRC; 1: add CRC-16/MODBUS ; 2: set the AT+DATACUT value. 662 +* LL: The length of AT+COMMAND or AT+DATACUT command 639 639 * XX XX XX XX: AT+COMMAND or AT+DATACUT command 640 -* YY: Nwill execute an uplink after got this command.664 +* 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. 641 641 642 - **Example:**666 +Example: 643 643 644 - (% style="color:#037691" %)**AF 03 01 06 0A 05 00 04 00 01 00**(%%): Same as AT+COMMAND3=0A 05 00 04 00 01,1668 +**AF 03 01 06 0A 05 00 04 00 01 00**: Same as AT+COMMAND3=0A 05 00 04 00 01,1 645 645 646 - (% 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**670 +**AF 03 02 06 10 01 05 06 09 0A 00**: Same as AT+DATACUT3=**16**,**1**,**5+6+9+10** 647 647 648 - (% 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**672 +**AF 03 02 06 0B 02 05 07 08 0A 00**: Same as AT+DATACUT3=**11**,**2**,**5~~7+8~~10** 649 649 650 650 675 +0xAB downlink command can be used for set AT+SEARCHx 651 651 652 - ====**FastcommandtohandleMODBUSdevice**====677 +Example: **AB aa 01 03 xx xx xx** (03 here means there are total 3 bytes after 03) So 653 653 679 +* AB aa 01 03 xx xx xx same as AT+SEARCHaa=1,xx xx xx 680 +* 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 681 + 682 +**AB aa 02 03 xx xx xx 02 yy yy** same as **AT+SEARCHaa=2,xx xx xx+yy yy** 683 + 684 + 685 +==== Fast command to handle MODBUS device ==== 686 + 654 654 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]]. 655 655 656 656 This command is valid since v1.3 firmware version 657 657 658 -AT+MBFUN can auto read the Modbus function code: 01, 02, 03 or 04. AT+MBFUN has lower priority vs AT+DATACUT command. If AT+DATACUT command is configured, AT+MBFUN will be ignore. 659 659 692 +AT+MBFUN has only two value: 660 660 661 -* *Example:**694 +* AT+MBFUN=1: Enable Modbus reading. And get response base on the MODBUS return 662 662 663 -* AT+MBFUN=1 and AT+DATACUT1/AT+DATACUT2 are not configure (0,0,0). So RS485-LN. 664 -* 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. 665 -* 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. 696 +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. 666 666 667 - [[image:image-20220602165351-6.png]]698 +* AT+MBFUN=0: Disable Modbus fast reading. 668 668 669 - [[image:image-20220602165351-7.png]]700 +Example: 670 670 702 +* AT+MBFUN=1 and AT+DATACUT1/AT+DATACUT2 are not configure (0,0,0). 703 +* 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. 704 +* 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. 671 671 706 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image025.png]] 672 672 673 -==== **RS485 command timeout** ==== 674 674 675 - SomeModbus devicehaslowaction to send replies.This command isused toconfigure the RS485-LNto uselonger time to wait for theiraction.709 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image026.png]] 676 676 677 -Default value: 0, range: 0 ~~ 65 seconds 678 678 679 -* **ATCommand:**712 +* Downlink Commands: 680 680 681 -(% class="box infomessage" %) 682 -((( 683 -**AT+CMDDLaa=hex(bb cc)*1000** 684 -))) 714 +A9 aa -à Same as AT+MBFUN=aa 685 685 686 -**Example:** 687 687 688 - **AT+CMDDL1=1000**tosend the open timeto1000ms717 +==== RS485 command timeout ==== 689 689 719 +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. 690 690 691 - * **DownlinkPayload:**721 +Default value: 0, range: 0 ~~ 5 seconds 692 692 693 -**0x AA aa bb cc** 694 694 695 - Sameas:AT+CMDDLaa=hex(bb cc)*1000724 +* AT Command: 696 696 697 - **Example:**726 +AT+CMDDLaa=hex(bb cc) 698 698 699 - 0xAA 01 00 01 ~-~-> Sameas **AT+CMDDL1=1000 ms**728 +Example: 700 700 730 +**AT+CMDDL1=1000** to send the open time to 1000ms 701 701 702 702 703 - ====**Uplinkpayloadmode** ====733 +* Downlink Payload: 704 704 705 - Definetouseoneuplink or multiple uplinks for the sampling.735 +0x AA aa bb cc 706 706 707 - Theuse of this command please see:[[Compose Uplink payload>>||anchor="H3.3.4Composetheuplinkpayload"]]737 +Same as: AT+CMDDLaa=hex(bb cc) 708 708 709 - ***ATCommand:**739 + Example: 710 710 711 -(% class="box infomessage" %) 712 -((( 713 -**AT+DATAUP=0** 714 -))) 741 + 0xAA 01 03 E8 à Same as **AT+CMDDL1=1000 ms** 715 715 716 -(% class="box infomessage" %) 717 -((( 718 -**AT+DATAUP=1** 719 -))) 720 720 744 +==== [[Uplink>>path:#downlink_A8]] payload mode ==== 721 721 722 - * **DownlinkPayload:**746 +Define to use one uplink or multiple uplinks for the sampling. 723 723 724 - **0xAD00****~-~->**SameasAT+DATAUP=0748 +The use of this command please see: [[Compose Uplink payload>>path:#DataUP]] 725 725 726 -* *0xAD01** **~-~->** Sameas AT+DATAUP=1750 +* AT Command: 727 727 752 +AT+DATAUP=0 728 728 754 +AT+DATAUP=1 729 729 730 -==== **Manually trigger an Uplink** ==== 731 731 732 - Askdevice tosend an uplinkimmediately.757 +* Downlink Payload: 733 733 734 - * **ATCommand:**759 +0xAD 00 à Same as AT+DATAUP=0 735 735 736 - NoATCommandforthis, usercan pressthe [[ACTbutton>>path:#Button]] for1second for the same.761 +0xAD 01 à Same as AT+DATAUP=1 737 737 738 738 739 - ***DownlinkPayload:**764 +==== Manually trigger an Uplink ==== 740 740 741 - **0x08FF**, RS485-LN will immediatelysend an uplink.766 +Ask device to send an uplink immediately. 742 742 768 +* Downlink Payload: 743 743 770 +0x08 FF, RS485-BL will immediately send an uplink. 744 744 745 -==== **Clear RS485 Command** ==== 746 746 773 +==== Clear RS485 Command ==== 774 + 747 747 The AT+COMMANDx and AT+DATACUTx settings are stored in special location, user can use below command to clear them. 748 748 749 -* **AT Command:** 750 750 778 +* AT Command: 779 + 751 751 **AT+CMDEAR=mm,nn** mm: start position of erase ,nn: stop position of erase 752 752 753 753 Etc. AT+CMDEAR=1,10 means erase AT+COMMAND1/AT+DATACUT1 to AT+COMMAND10/AT+DATACUT10 ... ... @@ -755,50 +755,43 @@ 755 755 Example screen shot after clear all RS485 commands. 756 756 757 757 787 + 758 758 The uplink screen shot is: 759 759 760 -[[image: 1654160691922-496.png]][[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image001.png]]790 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png]] 761 761 762 762 763 -* **Downlink Payload:**793 +* Downlink Payload: 764 764 765 - **0x09 aa bb**same as AT+CMDEAR=aa,bb795 +0x09 aa bb same as AT+CMDEAR=aa,bb 766 766 767 767 798 +==== Set Serial Communication Parameters ==== 768 768 769 -==== **Set Serial Communication Parameters** ==== 770 - 771 771 Set the Rs485 serial communication parameters: 772 772 773 -* **AT Command:**802 +* AT Command: 774 774 775 775 Set Baud Rate: 776 776 777 -(% class="box infomessage" %) 778 -((( 779 -**AT+BAUDR=9600** ~/~/ Options: (1200,2400,4800,14400,19200,115200) 780 -))) 806 +AT+BAUDR=9600 ~/~/ Options: (1200,2400,4800,14400,19200,115200) 781 781 782 -Set UART Parity 783 783 784 -(% class="box infomessage" %) 785 -((( 786 -**AT+PARITY=0** ~/~/ Option: 0: no parity, 1: odd parity, 2: even parity 787 -))) 809 +Set UART parity 788 788 811 +AT+PARITY=0 ~/~/ Option: 0: no parity, 1: odd parity, 2: even parity 812 + 813 + 789 789 Set STOPBIT 790 790 791 -(% class="box infomessage" %) 792 -((( 793 -**AT+STOPBIT=0** ~/~/ Option: 0 for 1bit; 1 for 1.5 bit ; 2 for 2 bits 794 -))) 816 +AT+STOPBIT=0 ~/~/ Option: 0 for 1bit; 1 for 1.5 bit ; 2 for 2 bits 795 795 796 796 797 -* **Downlink Payload:**819 +* Downlink Payload: 798 798 799 - **A7 01 aa bb**: Same AT+BAUDR=hex(aa bb)*100821 +A7 01 aa bb: Same AT+BAUDR=hex(aa bb)*100 800 800 801 - **Example:**823 +Example: 802 802 803 803 * A7 01 00 60 same as AT+BAUDR=9600 804 804 * A7 01 04 80 same as AT+BAUDR=115200 ... ... @@ -808,279 +808,287 @@ 808 808 A7 03 aa: Same as AT+STOPBIT=aa (aa value: 00 , 01 or 02) 809 809 810 810 811 -== 3.6 ListeningmodeforRS485 network==833 +==== Control output power duration ==== 812 812 813 - Thisfeaturesupportsincefirmwarev1.4835 +User can set the output power duration before each sampling. 814 814 815 - RS485-LNsupports listening mode, it can listen the RS485 network packets and send them via LoRaWAN uplink. Below is the structure.Theblue arrow shows the RS485 network packets to RS485-LN.837 +* AT Command: 816 816 817 - [[image:image-20220602171200-8.png||height="567" width="1007"]]839 +Example: 818 818 819 -T oenablethelisteningmode,usecanrun the command AT+RXMODE.841 +AT+3V3T=1000 ~/~/ 3V3 output power will open 1s before each sampling. 820 820 843 +AT+5VT=1000 ~/~/ +5V output power will open 1s before each sampling. 821 821 822 -(% border="1" style="background-color:#ffffcc; width:500px" %) 823 -|=(% style="width: 161px;" %)**Command example:**|=(% style="width: 337px;" %)**Function** 824 -|(% style="width:161px" %)AT+RXMODE=1,10 |(% style="width:337px" %)Enable listening mode 1, if RS485-LN has received more than 10 RS485 commands from the network. RS485-LN will send these commands via LoRaWAN uplinks. 825 -|(% style="width:161px" %)AT+RXMODE=2,500|(% style="width:337px" %)Enable listening mode 2, RS485-LN will capture and send a 500ms content once from the first detect of character. Max value is 65535 ms 826 -|(% style="width:161px" %)AT+RXMODE=0,0|(% style="width:337px" %)Disable listening mode. This is the default settings. 827 -|(% style="width:161px" %) |(% style="width:337px" %)A6 aa bb cc same as AT+RXMODE=aa,(bb<<8 ~| cc) 828 828 829 -* *Downlink Command:**846 +* LoRaWAN Downlink Command: 830 830 831 - **0xA6aa bbcc ** same as AT+RXMODE=aa,(bb<<8 | cc)848 +07 01 aa bb Same as AT+5VT=(aa bb) 832 832 850 +07 02 aa bb Same as AT+3V3T=(aa bb) 833 833 834 -**Example**: 835 835 836 -The RS485-LN is set to AT+RXMODE=2,1000 837 837 838 -There is a two Modbus commands in the RS485 network as below: 839 839 840 -The Modbus master send a command: (% style="background-color:#ffc000" %)01 03 00 00 00 02 c4 0b 855 +1. 856 +11. Buttons 841 841 842 -And Modbus slave reply with: (% style="background-color:green" %)01 03 04 00 00 00 00 fa 33 858 +|**Button**|**Feature** 859 +|**RST**|Reboot RS485-BL 843 843 844 -RS485-LN will capture both and send the uplink: (% style="background-color:#ffc000" %)01 03 00 00 00 02 c4 0b (% style="background-color:green" %)01 03 04 00 00 00 00 fa 33 861 +1. 862 +11. +3V3 Output 845 845 846 - [[image:image-20220602171200-9.png]]864 +RS485-BL has a Controllable +3V3 output, user can use this output to power external sensor. 847 847 866 +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. 848 848 849 -(% style="color:red" %)Notice: Listening mode can work with the default polling mode of RS485-LN. When RS485-LN is in to send the RS485 commands (from AT+COMMANDx), the listening mode will be interrupt for a while. 850 850 869 +The +3V3 output time can be controlled by AT Command. 851 851 852 - ==3.7 Buttons==871 +**AT+3V3T=1000** 853 853 873 +Means set +3v3 valid time to have 1000ms. So, the real +3v3 output will actually have 1000ms + sampling time for other sensors. 854 854 855 -(% border="1" style="background-color:#f7faff; width:500px" %) 856 -|=**Button**|=(% style="width: 1420px;" %)**Feature** 857 -|**ACT**|(% style="width:1420px" %)If RS485 joined in network, press this button for more than 1 second, RS485 will upload a packet, and the SYS LED will give a (% style="color:blue" %)**Blue blink** 858 -|**RST**|(% style="width:1420px" %)Reboot RS485 859 -|**PRO**|(% style="width:1420px" %)Use for upload image, see [[How to Update Image>>path:#upgrade_image]] 860 860 861 - ==3.8LEDs==876 +By default, the AT+3V3T=0. This is a special case, means the +3V3 output is always on at any time 862 862 863 -(% border="1" style="background-color:#f7faff; width:500px" %) 864 -|=**LEDs**|=**Feature** 865 -|**PWR**|Always on if there is power 866 -|**SYS**|After device is powered on, the SYS will (% style="color:green" %)**fast blink in GREEN** (%%)for 5 times, means RS485-LN start to join LoRaWAN network. If join success, SYS will be (% style="color:green" %)**on GREEN for 5 seconds**(%%)**. **SYS will (% style="color:green" %)**blink Blue**(%%) on every upload and (% style="color:green" %)**blink Green**(%%) once receive a downlink message. 867 867 868 -= 4. Case Study = 879 +1. 880 +11. +5V Output 869 869 870 - UsercancheckthisURL forsome casestudies:[[APP RS485 COMMUNICATE WITH SENSORS>>doc:Main.ApplicationNote\: Communicatewith DifferentSensors ----- RS485-LN RS485-BL.WebHome]]882 +RS485-BL has a Controllable +5V output, user can use this output to power external sensor. 871 871 884 +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. 872 872 873 -= 5. Use AT Command = 874 874 875 - ==5.1AccessAT Command==887 +The 5V output time can be controlled by AT Command. 876 876 877 - RS485-BL supportsATCommand set. User can use a USB to TTL adapter plus the 3.5mm Program Cable to connect to RS485-BL to use ATcommand, as below.889 +**AT+5VT=1000** 878 878 879 - [[image:1654162355560-817.png]]891 +Means set 5V valid time to have 1000ms. So, the real 5V output will actually have 1000ms + sampling time for other sensors. 880 880 881 881 882 - InPC, User needs to set(% style="color:blue"%)**serialtool**(%%)(suchas [[putty>>url:https://www.chiark.greenend.org.uk/~~sgtatham/putty/latest.html]],SecureCRT)baud rateto(% style="color:green" %)**9600**(%%)toaccesstoaccessserialconsoleof RS485-BL. Thedefaultpasswordis123456. Belowisthe outputforreference:894 +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. 883 883 884 -[[image:1654162368066-342.png]] 885 885 886 886 887 -More detail AT Command manual can be found at [[AT Command Manual>>||anchor="3.5ConfigureRS485-BLviaATorDownlink"]] 888 888 899 +1. 900 +11. LEDs 889 889 890 -== 5.2 Common AT Command Sequence == 902 +|**LEDs**|**Feature** 903 +|**LED1**|Blink when device transmit a packet. 891 891 892 -=== 5.2.1 Multi-channel ABP mode (Use with SX1301/LG308) === 905 +1. 906 +11. Switch Jumper 893 893 894 -If device has not joined network yet: 908 +|**Switch Jumper**|**Feature** 909 +|**SW1**|((( 910 +ISP position: Upgrade firmware via UART 895 895 896 -(% class="box infomessage" %) 897 -((( 898 -**AT+FDR** 912 +Flash position: Configure device, check running status. 899 899 ))) 914 +|**SW2**|((( 915 +5V position: set to compatible with 5v I/O. 900 900 901 -(% class="box infomessage" %) 902 -((( 903 -**AT+NJM=0** 917 +3.3v position: set to compatible with 3.3v I/O., 904 904 ))) 905 905 906 -(% class="box infomessage" %) 907 -((( 908 -**ATZ** 909 -))) 920 ++3.3V: is always ON 910 910 922 ++5V: Only open before every sampling. The time is by default, it is AT+5VT=0. Max open time. 5000 ms. 911 911 912 - Ifdevicealreadyjoined network:924 +1. Case Study 913 913 914 -(% class="box infomessage" %) 915 -((( 916 -**AT+NJM=0** 917 -))) 926 +User can check this URL for some case studies. 918 918 919 -(% class="box infomessage" %) 920 -((( 921 -**ATZ** 922 -))) 928 +[[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]] 923 923 924 924 925 -=== 5.5.2 Single-channel ABP mode (Use with LG01/LG02) === 926 926 927 927 928 -(% style="background-color:#dcdcdc" %)**AT+FDR** (%%) Reset Parameters to Factory Default, Keys Reserve 933 +1. Use AT Command 934 +11. Access AT Command 929 929 930 - (%style="background-color:#dcdcdc"%)**AT+NJM=0**(%%)Setto ABPmode936 +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. 931 931 932 - (% style="background-color:#dcdcdc" %)**AT+ADR=0** (%%)Set theAdaptiveDataRateOff938 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image027.png]] 933 933 934 -(% style="background-color:#dcdcdc" %)**AT+DR=5** (%%)Set Data Rate 935 935 936 -( %style="background-color:#dcdcdc"%)**AT+TDC=60000**(%%)Settransmitinterval to 60seconds941 +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: 937 937 938 - (% style="background-color:#dcdcdc" %)**AT+CHS=868400000**(%%) Set transmit frequency to868.4Mhz943 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image028.png]] 939 939 940 -(% style="background-color:#dcdcdc" %)**AT+RX2FQ=868400000** (%%) Set RX2Frequency to 868.4Mhz (according to the result from server) 941 941 942 -(% style="background-color:#dcdcdc" %)**AT+RX2DR=5** (%%) Set RX2DR to match the downlink DR from server. see below 943 943 944 - (% style="background-color:#dcdcdc" %)**AT+DADDR=26** (%%) 01 1A F1 SetDeviceAddressto2601 1A F1, this IDcan be foundintheLoRaServer portal.947 +More detail AT Command manual can be found at [[AT Command Manual>>path:#AT_COMMAND]] 945 945 946 -(% style="background-color:#dcdcdc" %)**ATZ** (%%) Reset MCU 947 947 948 948 949 -(% style="color:red" %)**Note:** 951 +1. 952 +11. Common AT Command Sequence 953 +111. Multi-channel ABP mode (Use with SX1301/LG308) 950 950 951 -(% style="color:red" %)1. Make sure the device is set to ABP mode in the IoT Server. 952 -2. Make sure the LG01/02 gateway RX frequency is exactly the same as AT+CHS setting. 953 -3. 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. 954 -4. The command AT+RX2FQ and AT+RX2DR is to let downlink work. to set the correct parameters, user can check the actually downlink parameters to be used. As below. Which shows the RX2FQ should use 868400000 and RX2DR should be 5 955 +If device has not joined network yet: 955 955 956 - [[image:1654162478620-421.png]]957 +AT+FDR 957 957 959 +AT+NJM=0 958 958 959 - = 6. FAQ =961 +ATZ 960 960 961 -== 6.1 How to upgrade the image? == 962 962 963 - TheRS485-LN LoRaWAN Controlleris shipped with a 3.5mmcable,the cableis used to upload image toRS485-LN to:964 +If device already joined network: 964 964 965 -* Support new features 966 -* For bug fix 967 -* Change LoRaWAN bands. 966 +AT+NJM=0 968 968 969 - Below shows the hardware connection for how to upload an image to RS485-LN:968 +ATZ 970 970 971 -[[image:1654162535040-878.png]] 970 +1. 971 +11. 972 +111. Single-channel ABP mode (Use with LG01/LG02) 972 972 973 - **Step1:**Download[[flashloader>>url:https://www.st.com/content/st_com/en/products/development-tools/software-development-tools/stm32-software-development-tools/stm32-programmers/flasher-stm32.html]].974 +AT+FDR Reset Parameters to Factory Default, Keys Reserve 974 974 975 - **Step2**:Downloadthe[[LT Image files>>url:http://www.dragino.com/downloads/index.php?dir=LT_LoRa_IO_Controller/LT33222-L/image/]].976 +AT+NJM=0 Set to ABP mode 976 976 977 - **Step3:**Open flashloader; choosethecorrect COMport toupdate.978 +AT+ADR=0 Set the Adaptive Data Rate Off 978 978 979 - (% style="color:blue"%) Hold down the PRO button and then momentarily press the RST resetbuttonandthe SYS led will changefrom OFF to ON, While SYS LED isRED ON, it meanstheRS485-LN is ready to be program.980 +AT+DR=5 Set Data Rate 980 980 982 +AT+TDC=60000 Set transmit interval to 60 seconds 981 981 982 - [[image:image-20220602175818-12.png]]984 +AT+CHS=868400000 Set transmit frequency to 868.4Mhz 983 983 986 +AT+RX2FQ=868400000 Set RX2Frequency to 868.4Mhz (according to the result from server) 984 984 985 - [[image:image-20220602175848-13.png]]988 +AT+RX2DR=5 Set RX2DR to match the downlink DR from server. see below 986 986 990 +AT+DADDR=26 01 1A F1 Set Device Address to 26 01 1A F1, this ID can be found in the LoRa Server portal. 987 987 988 - [[image:image-20220602175912-14.png]]992 +ATZ Reset MCU 989 989 994 +**Note:** 990 990 991 -**Notice**: In case user has lost the program cable. User can hand made one from a 3.5mm cable. The pin mapping is: 996 +1. Make sure the device is set to ABP mode in the IoT Server. 997 +1. Make sure the LG01/02 gateway RX frequency is exactly the same as AT+CHS setting. 998 +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. 999 +1. The command AT+RX2FQ and AT+RX2DR is to let downlink work. to set the correct parameters, user can check the actually downlink parameters to be used. As below. Which shows the RX2FQ should use 868400000 and RX2DR should be 5 992 992 993 -[[image:image -20220602175638-10.png]]1001 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image029.png]] 994 994 995 995 996 -== 6.2 How to change the LoRa Frequency Bands/Region? == 1004 +1. FAQ 1005 +11. How to upgrade the image? 997 997 998 - Usercanfollowthe introduction for[[howto upgradeimage>>||anchor="H6.1Howtoupgradetheimage3F"]].Whendownloadtheimages,choose therequired imagefile fordownload.1007 +The RS485-BL LoRaWAN Controller is shipped with a 3.5mm cable, the cable is used to upload image to RS485-BL to: 999 999 1009 +* Support new features 1010 +* For bug fix 1011 +* Change LoRaWAN bands. 1000 1000 1001 - ==6.3 HowmanyRS485-Slavecan RS485-BLconnects? ==1013 +Below shows the hardware connection for how to upload an image to RS485-BL: 1002 1002 1003 - The RS485-BL can supportmax 32 RS485 devices. Each uplink command of RS485-BL can support max 16 differentRS485 command. So RS485-BLn supportmax 16 RS485 devicespre-program in the device for uplink. For other devices nopre-program, usercan use the [[downlinkmessage(type code0xA8) to poll their info>>||anchor="H3.3.3Configurereadcommandsforeachsampling"]].1015 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image030.png]] 1004 1004 1017 +**Step1:** Download [[flash loader>>url:https://www.st.com/content/st_com/en/products/development-tools/software-development-tools/stm32-software-development-tools/stm32-programmers/flasher-stm32.html]]. 1005 1005 1006 - ==6.4 CompatiblequestiontoChirpStack andTILoRaWAN server? ==1019 +**Step2**: Download the [[LT Image files>>url:http://www.dragino.com/downloads/index.php?dir=LT_LoRa_IO_Controller/LT33222-L/image/]]. 1007 1007 1008 - Whenuserneed tousewithChirpStackorTTI.Please setAT+RPL=4.1021 +**Step3: **Open flashloader; choose the correct COM port to update. 1009 1009 1010 -Detail info check this link: [[Set Packet Receiving Response Level>>doc:Main.End Device AT Commands and Downlink Command.WebHome||anchor="H7.23SetPacketReceivingResponseLevel"]] 1011 1011 1024 +|((( 1025 +HOLD PRO then press the RST button, SYS will be ON, then click next 1026 +))) 1012 1012 1013 -= 7. Trouble Shooting = 1028 +|((( 1029 +Board detected 1030 +))) 1014 1014 1015 -== 7.1 Downlink doesn’t work, how to solve it? == 1032 +|((( 1033 + 1034 +))) 1016 1016 1017 - Pleaseeethislinkfordebug:[[LoRaWAN Communication Debug>>doc:Main.LoRaWAN Communication Debug.WebHome]]1036 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image031.png]] [[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image032.png]] 1018 1018 1019 1019 1020 -== 7.2 Why I can’t join TTN V3 in US915 /AU915 bands? == 1021 1021 1022 - It mightbout thechannelsapping.Pleaseseefordetail:[[NoticeofFrequency band>>doc:Main.LoRaWAN Communication Debug.WebHome||anchor="H2.NoticeofUS9152FCN4702FAU915Frequencyband"]]1040 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image033.png]] [[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image034.png]] 1023 1023 1024 1024 1025 - = 8. OrderInfo=1043 +[[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]] 1026 1026 1027 -(% style="color:blue" %)**Part Number: RS485-LN-XXX** 1028 1028 1029 -(% style="color:blue" %)**XXX:** 1046 +1. 1047 +11. How to change the LoRa Frequency Bands/Region? 1030 1030 1031 -* (% style="color:blue" %)**EU433**(%%): frequency bands EU433 1032 -* (% style="color:blue" %)**EU868**(%%): frequency bands EU868 1033 -* (% style="color:blue" %)**KR920**(%%): frequency bands KR920 1034 -* (% style="color:blue" %)**CN470**(%%): frequency bands CN470 1035 -* (% style="color:blue" %)**AS923**(%%): frequency bands AS923 1036 -* (% style="color:blue" %)**AU915**(%%): frequency bands AU915 1037 -* (% style="color:blue" %)**US915**(%%): frequency bands US915 1038 -* (% style="color:blue" %)**IN865**(%%): frequency bands IN865 1039 -* (% style="color:blue" %)**RU864**(%%): frequency bands RU864 1040 -* (% style="color:blue" %)**KZ865**(%%): frequency bands KZ865 1049 +User can follow the introduction for [[how to upgrade image>>path:#upgrade_image]]. When download the images, choose the required image file for download. 1041 1041 1042 -= 9.Packing Info = 1043 1043 1044 1044 1045 -**Package Includes**: 1053 +1. 1054 +11. How many RS485-Slave can RS485-BL connects? 1046 1046 1047 -* RS485-LN x 1 1048 -* Stick Antenna for LoRa RF part x 1 1049 -* Program cable x 1 1056 +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]]. 1050 1050 1051 -**Dimension and weight**: 1052 1052 1053 -* Device Size: 13.5 x 7 x 3 cm 1054 -* Device Weight: 105g 1055 -* Package Size / pcs : 14.5 x 8 x 5 cm 1056 -* Weight / pcs : 170g 1057 1057 1058 -= 10. FCC Caution for RS485LN-US915 = 1059 1059 1060 -Any Changes or modifications not expressly approved by the party responsible for compliance could void the user's authority to operate the equipment. 1061 +1. Trouble Shooting 1062 +11. Downlink doesn’t work, how to solve it? 1061 1061 1062 - This device complies with part 15 of the FCC Rules. Operationissubject to thefollowingtwo conditions: (1) Thisdevice may not cause harmfulterference,and (2) this device must accept any interferencereceived, including interference that may cause undesired operation.1064 +Please see this link for debug: 1063 1063 1066 +[[http:~~/~~/wiki.dragino.com/index.php?title=Main_Page#LoRaWAN_Communication_Debug>>url:http://wiki.dragino.com/index.php?title=Main_Page#LoRaWAN_Communication_Debug]] 1064 1064 1065 -**IMPORTANT NOTE:** 1066 1066 1067 -**Note: **This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses and can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications. However, there is no guarantee that interference will not occur in a particular installation. If this equipment does cause harmful interference to radio or television reception, which can be determined by turning the equipment off and on, the user is encouraged to try to correct the interference by one or more of the following measures: 1068 1068 1069 -—Reorient or relocate the receiving antenna. 1070 +1. 1071 +11. Why I can’t join TTN V3 in US915 /AU915 bands? 1070 1070 1071 - —Increasetheseparationbetweentheequipmentandreceiver.1073 +It might about the channels mapping. Please see for detail. 1072 1072 1073 - —Connecthe equipmentntonoutlet ona circuitdifferent from thatowhich thereceiverisconnected.1075 +[[http:~~/~~/wiki.dragino.com/index.php?title=LoRaWAN_Communication_Debug#Notice_of_US915.2FCN470.2FAU915_Frequency_band>>url:http://wiki.dragino.com/index.php?title=LoRaWAN_Communication_Debug#Notice_of_US915.2FCN470.2FAU915_Frequency_band]] 1074 1074 1075 -—Consult the dealer or an experienced radio/TV technician for help. 1076 1076 1077 1077 1078 - **FCCRadiation ExposureStatement:**1079 +1. Order Info 1079 1079 1080 - This equipment complies with FCC radiation exposure limitsset forth for anuncontrolled environment.This equipment shouldbeinstalled and operatedwith minimum distance 20cm between the radiator& your body.1081 +**Part Number: RS485-BL-XXX** 1081 1081 1083 +**XXX:** 1082 1082 1083 -= 11. Support = 1085 +* **EU433**: frequency bands EU433 1086 +* **EU868**: frequency bands EU868 1087 +* **KR920**: frequency bands KR920 1088 +* **CN470**: frequency bands CN470 1089 +* **AS923**: frequency bands AS923 1090 +* **AU915**: frequency bands AU915 1091 +* **US915**: frequency bands US915 1092 +* **IN865**: frequency bands IN865 1093 +* **RU864**: frequency bands RU864 1094 +* **KZ865: **frequency bands KZ865 1084 1084 1096 +1. Packing Info 1097 + 1098 +**Package Includes**: 1099 + 1100 +* RS485-BL x 1 1101 +* Stick Antenna for LoRa RF part x 1 1102 +* Program cable x 1 1103 + 1104 +**Dimension and weight**: 1105 + 1106 +* Device Size: 13.5 x 7 x 3 cm 1107 +* Device Weight: 105g 1108 +* Package Size / pcs : 14.5 x 8 x 5 cm 1109 +* Weight / pcs : 170g 1110 + 1111 +1. Support 1112 + 1085 1085 * Support is provided Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different timezones we cannot offer live support. However, your questions will be answered as soon as possible in the before-mentioned schedule. 1086 -* Provide as much information as possible regarding your enquiry (product models, accurately describe your problem and steps to replicate it etc) and send a mail to [[support@dragino.com>>url:file:///D:/市场资料/说明书/LoRa/LT系列/support@dragino.com]]. 1114 +* Provide as much information as possible regarding your enquiry (product models, accurately describe your problem and steps to replicate it etc) and send a mail to 1115 + 1116 +[[support@dragino.com>>url:file:///D:/市场资料/说明书/LoRa/LT系列/support@dragino.com]]
- 1654157342174-798.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -31.9 KB - Content
- 1654158783574-851.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -40.6 KB - Content
- 1654159460680-153.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -24.9 KB - Content
- 1654160691922-496.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -109.3 KB - Content
- 1654162355560-817.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -670.0 KB - Content
- 1654162368066-342.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -192.9 KB - Content
- 1654162478620-421.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -158.9 KB - Content
- 1654162535040-878.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -670.0 KB - Content
- image-20220602163333-5.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -48.2 KB - Content
- image-20220602165351-6.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -10.6 KB - Content
- image-20220602165351-7.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -19.3 KB - Content
- image-20220602171200-8.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -276.1 KB - Content
- image-20220602171200-9.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -10.0 KB - Content
- image-20220602175638-10.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -85.5 KB - Content
- image-20220602175743-11.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -85.5 KB - Content
- image-20220602175818-12.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -102.5 KB - Content
- image-20220602175848-13.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -250.9 KB - Content
- image-20220602175912-14.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -176.1 KB - Content