Last modified by Xiaoling on 2025/04/23 15:56
<
From version < 57.28 >
edited by Xiaoling
on 2022/06/06 09:21
To version < 37.1 >
edited by Xiaoling
on 2022/06/02 16:06
>
Change comment: Uploaded new attachment "1654157178836-407.png", version {1}

Summary

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

Applications

Navigation

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