<
From version < 59.14 >
edited by Xiaoling
on 2022/06/06 14:23
To version < 40.1 >
edited by Xiaoling
on 2022/06/02 16:33
>
Change comment: Uploaded new attachment "image-20220602163333-5.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 ==
... ... @@ -24,33 +24,23 @@
24 24  
25 25  (((
26 26  (((
27 -(((
28 28  The Dragino RS485-LN is a (% style="color:blue" %)**RS485 to LoRaWAN Converter**(%%). It converts the RS485 signal into LoRaWAN wireless signal which simplify the IoT installation and reduce the installation/maintaining cost.
29 29  )))
30 -)))
31 31  
32 32  (((
33 -(((
34 34  RS485-LN allows user to (% style="color:blue" %)**monitor / control RS485 devices**(%%) and reach extremely long ranges. It provides ultra-long range spread spectrum communication and high interference immunity whilst minimizing current consumption. It targets professional wireless sensor network applications such as irrigation systems, smart metering, smart cities, smartphone detection, building automation, and so on.
35 35  )))
36 -)))
37 37  
38 38  (((
39 -(((
40 40  (% style="color:blue" %)**For data uplink**(%%), RS485-LN sends user-defined commands to RS485 devices and gets the return from the RS485 devices. RS485-LN will process these returns according to user-define rules to get the final payload and upload to LoRaWAN server.
41 41  )))
42 -)))
43 43  
44 44  (((
45 -(((
46 46  (% style="color:blue" %)**For data downlink**(%%), RS485-LN runs in LoRaWAN Class C. When there downlink commands from LoRaWAN server, RS485-LN will forward the commands from LoRaWAN server to RS485 devices.
47 -)))
48 48  
49 -(((
50 50  (% style="color:blue" %)**Demo Dashboard for RS485-LN**(%%) connect to two energy meters: [[https:~~/~~/app.datacake.de/dashboard/d/58844a26-378d-4c5a-aaf5-b5b5b153447a>>url:https://app.datacake.de/dashboard/d/58844a26-378d-4c5a-aaf5-b5b5b153447a]]
51 51  )))
52 52  )))
53 -)))
54 54  
55 55  [[image:1653267211009-519.png||height="419" width="724"]]
56 56  
... ... @@ -90,10 +90,8 @@
90 90  * Preamble detection.
91 91  * 127 dB Dynamic Range RSSI.
92 92  * Automatic RF Sense and CAD with ultra-fast AFC.
93 -* Packet engine up to 256 bytes with CRC
77 +* Packet engine up to 256 bytes with CRC.
94 94  
95 -
96 -
97 97  == 1.3 Features ==
98 98  
99 99  * LoRaWAN Class A & Class C protocol (default Class C)
... ... @@ -105,8 +105,6 @@
105 105  * Support Modbus protocol
106 106  * Support Interrupt uplink (Since hardware version v1.2)
107 107  
108 -
109 -
110 110  == 1.4 Applications ==
111 111  
112 112  * Smart Buildings & Home Automation
... ... @@ -116,8 +116,6 @@
116 116  * Smart Cities
117 117  * Smart Factory
118 118  
119 -
120 -
121 121  == 1.5 Firmware Change log ==
122 122  
123 123  [[RS485-LN Image files – Download link and Change log>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/]]
... ... @@ -127,13 +127,9 @@
127 127  
128 128  (((
129 129  (((
130 -(((
131 131  v1.2: Add External Interrupt Pin.
132 -)))
133 133  
134 -(((
135 135  v1.0: Release
136 -)))
137 137  
138 138  
139 139  )))
... ... @@ -161,9 +161,7 @@
161 161  == 3.1 How it works? ==
162 162  
163 163  (((
164 -(((
165 165  The RS485-LN is configured as LoRaWAN OTAA Class C mode by default. It has OTAA keys to join network. To connect a local LoRaWAN network, user just need to input the OTAA keys in the network server and power on the RS485-LN. It will auto join the network via OTAA.
166 -)))
167 167  
168 168  
169 169  )))
... ... @@ -187,7 +187,7 @@
187 187  [[image:1653268227651-549.png||height="592" width="720"]]
188 188  
189 189  (((
190 -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:
191 191  )))
192 192  
193 193  (((
... ... @@ -239,15 +239,11 @@
239 239  
240 240  (((
241 241  (((
242 -(((
243 -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.
244 244  )))
245 -)))
246 246  
247 247  (((
248 -(((
249 249  (% style="color:red" %)Note: below description and commands are for firmware version >v1.1, if you have firmware version v1.0. Please check the [[user manual v1.0>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/&file=RS485-LN_UserManual_v1.0.1.pdf]] or upgrade the firmware to v1.1
250 -)))
251 251  
252 252  
253 253  )))
... ... @@ -257,19 +257,19 @@
257 257  
258 258  To use RS485-LN to read data from RS485 sensors, connect the RS485-LN A/B traces to the sensors. And user need to make sure RS485-LN use the match UART setting to access the sensors. The related commands for UART settings are:
259 259  
260 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)
261 -|=(% style="width: 110px;" %)(((
228 +(% border="1" style="background-color:#ffffcc; color:green; width:782px" %)
229 +|(% style="width:128px" %)(((
262 262  **AT Commands**
263 -)))|=(% style="width: 190px;" %)(((
231 +)))|(% style="width:305px" %)(((
264 264  **Description**
265 -)))|=(% style="width: 190px;" %)(((
233 +)))|(% style="width:346px" %)(((
266 266  **Example**
267 267  )))
268 -|(% style="width:110px" %)(((
236 +|(% style="width:128px" %)(((
269 269  AT+BAUDR
270 -)))|(% style="width:190px" %)(((
238 +)))|(% style="width:305px" %)(((
271 271  Set the baud rate (for RS485 connection). Default Value is: 9600.
272 -)))|(% style="width:190px" %)(((
240 +)))|(% style="width:346px" %)(((
273 273  (((
274 274  AT+BAUDR=9600
275 275  )))
... ... @@ -278,11 +278,11 @@
278 278  Options: (1200,2400,4800,14400,19200,115200)
279 279  )))
280 280  )))
281 -|(% style="width:110px" %)(((
249 +|(% style="width:128px" %)(((
282 282  AT+PARITY
283 -)))|(% style="width:190px" %)(((
251 +)))|(% style="width:305px" %)(((
284 284  Set UART parity (for RS485 connection)
285 -)))|(% style="width:190px" %)(((
253 +)))|(% style="width:346px" %)(((
286 286  (((
287 287  AT+PARITY=0
288 288  )))
... ... @@ -291,9 +291,9 @@
291 291  Option: 0: no parity, 1: odd parity, 2: even parity
292 292  )))
293 293  )))
294 -|(% style="width:110px" %)(((
262 +|(% style="width:128px" %)(((
295 295  AT+STOPBIT
296 -)))|(% style="width:190px" %)(((
264 +)))|(% style="width:305px" %)(((
297 297  (((
298 298  Set serial stopbit (for RS485 connection)
299 299  )))
... ... @@ -301,7 +301,7 @@
301 301  (((
302 302  
303 303  )))
304 -)))|(% style="width:190px" %)(((
272 +)))|(% style="width:346px" %)(((
305 305  (((
306 306  AT+STOPBIT=0 for 1bit
307 307  )))
... ... @@ -315,8 +315,6 @@
315 315  )))
316 316  )))
317 317  
318 -
319 -
320 320  === 3.3.2 Configure sensors ===
321 321  
322 322  (((
... ... @@ -325,24 +325,16 @@
325 325  )))
326 326  )))
327 327  
328 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)
329 -|=(% style="width: 110px;" %)**AT Commands**|=(% style="width: 190px;" %)**Description**|=(% style="width: 190px;" %)**Example**
330 -|AT+CFGDEV|(% style="width:110px" %)(((
331 -(((
294 +(% border="1" style="background-color:#ffffcc; color:green; width:806px" %)
295 +|**AT Commands**|(% style="width:418px" %)**Description**|(% style="width:256px" %)**Example**
296 +|AT+CFGDEV|(% style="width:418px" %)(((
332 332  This command is used to configure the RS485/TTL devices; they won’t be used during sampling.
333 -)))
334 334  
335 -(((
336 336  AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,
337 -)))
338 338  
339 -(((
340 340  mm: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
341 -)))
342 -)))|(% style="width:190px" %)AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
302 +)))|(% style="width:256px" %)AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
343 343  
344 -
345 -
346 346  === 3.3.3 Configure read commands for each sampling ===
347 347  
348 348  (((
... ... @@ -388,8 +388,8 @@
388 388  
389 389  **AT+DATACUTx : **This command defines how to handle the return from AT+COMMANDx, max return length is 45 bytes.
390 390  
391 -(% border="1" style="background-color:#4bacc6; color:white; width:510px" %)
392 -|(% style="width:510px" %)(((
349 +(% border="1" style="background-color:#4bacc6; color:white; width:725px" %)
350 +|(% style="width:722px" %)(((
393 393  **AT+DATACUTx=a,b,c**
394 394  
395 395  * **a: length for the return of AT+COMMAND**
... ... @@ -458,7 +458,6 @@
458 458  
459 459  (% style="color:#4f81bd" %)**Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA**
460 460  
461 -
462 462  1. PAYVER: Defined by AT+PAYVER
463 463  1. PAYLOAD COUNT: Total how many uplinks of this sampling.
464 464  1. PAYLOAD#: Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT)
... ... @@ -515,33 +515,33 @@
515 515  
516 516  == 3.4 Uplink Payload ==
517 517  
475 +(% border="1" style="background-color:#4bacc6; color:white; width:734px" %)
476 +|**Size(bytes)**|(% style="width:120px" %)**2**|(% style="width:116px" %)**1**|(% style="width:386px" %)**Length depends on the return from the commands**
477 +|Value|(% style="width:120px" %)(((
478 +Battery(mV)
518 518  
519 -[[image:image-20220606110929-1.png]]
480 +&
520 520  
482 +Interrupt _Flag
483 +)))|(% style="width:116px" %)(((
484 +PAYLOAD_VER
485 +
486 +
487 +)))|(% style="width:386px" %)If the valid payload is too long and exceed the maximum support payload length in server, server will show payload not provided in the LoRaWAN server.
488 +
521 521  Below is the decoder for the first 3 bytes. The rest bytes are dynamic depends on different RS485 sensors.
522 522  
523 523  
524 524  == 3.5 Configure RS485-BL via AT or Downlink ==
525 525  
526 -(((
527 527  User can configure RS485-LN via AT Commands or LoRaWAN Downlink Commands
528 -)))
529 529  
530 -(((
531 531  There are two kinds of Commands:
532 -)))
533 533  
534 -* (((
535 -(% 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]]
536 -)))
498 +* (% style="color:#4f81bd" %)**Common Commands**(%%): They should be available for each sensor, such as: change uplink interval, reset device. For firmware v1.3, user can find what common commands it supports: [[End Device AT Commands and Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]]
537 537  
538 -* (((
539 -(% style="color:#4f81bd" %)**Sensor Related Commands**(%%): These commands are special designed for RS485-LN.  User can see these commands below:
540 -)))
500 +* (% style="color:#4f81bd" %)**Sensor Related Commands**(%%): These commands are special designed for RS485-LN.  User can see these commands below:
541 541  
542 -(((
543 -
544 -)))
545 545  
546 546  
547 547  === 3.5.1 Common Commands ===
... ... @@ -549,888 +549,557 @@
549 549  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]]
550 550  
551 551  
552 -=== 3.5.2 Sensor related commands ===
509 +=== 3.5.2 Sensor related commands: ===
553 553  
554 -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.
511 +==== Choose Device Type (RS485 or TTL) ====
555 555  
556 -[[image:image-20220602163333-5.png||height="263" width="1160"]]
513 +RS485-BL can connect to either RS485 sensors or TTL sensor. User need to specify what type of sensor need to connect.
557 557  
558 -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)
515 +* AT Command
559 559  
517 +**AT+MOD=1** ~/~/ Set to support RS485-MODBUS type sensors. User can connect multiply RS485 , Modbus sensors to the A / B pins.
560 560  
561 -=== 3.5.3 Sensor related commands ===
519 +**AT+MOD=2** ~/~/ Set to support TTL Level sensors, User can connect one TTL Sensor to the TXD/RXD/GND pins.
562 562  
563 563  
522 +* Downlink Payload
564 564  
524 +**0A aa**     à same as AT+MOD=aa
565 565  
566 -==== **RS485 Debug Command** ====
567 567  
568 -(((
569 -This command is used to configure the RS485 devices; they won’t be used during sampling.
570 -)))
571 571  
572 -* (((
573 -**AT Command**
574 -)))
528 +==== [[RS485 Debug Command>>path:#downlink_A8]] (AT+CFGDEV) ====
575 575  
576 -(% class="box infomessage" %)
577 -(((
578 -(((
579 -**AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m**
580 -)))
581 -)))
530 +This command is used to configure the RS485 or TTL sensors; they won’t be used during sampling.
582 582  
583 -(((
584 -m: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
585 -)))
532 +* AT Command
586 586  
587 -* (((
588 -**Downlink Payload**
589 -)))
534 +AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
590 590  
591 -(((
536 +m: 0: no CRC; 1: add CRC-16/MODBUS in the end of this command.
537 +
538 +
539 +
540 +* Downlink Payload
541 +
592 592  Format: A8 MM NN XX XX XX XX YY
593 -)))
594 594  
595 -(((
596 596  Where:
597 -)))
598 598  
599 -* (((
600 -MM: 1: add CRC-16/MODBUS ; 0: no CRC
601 -)))
602 -* (((
603 -NN: The length of RS485 command
604 -)))
605 -* (((
606 -XX XX XX XX: RS485 command total NN bytes
607 -)))
608 -* (((
609 -(((
610 -YY: How many bytes will be uplink from the return of this RS485 command,
611 -)))
546 +* MM: 1: add CRC-16/MODBUS ; 0: no CRC
547 +* NN: The length of RS485 command
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, 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
612 612  
613 -* (((
614 -if YY=0, RS485-LN will execute the downlink command without uplink;
615 -)))
616 -* (((
617 -if YY>0, RS485-LN will uplink total YY bytes from the output of this RS485 command; Fport=200
618 -)))
619 -* (((
620 -if YY=FF, RS485-LN will uplink RS485 output with the downlink command content; Fport=200.
621 -)))
622 -)))
551 +**Example 1:**
623 623  
624 -(((
625 -**Example 1** ~-~-> Configure without ask for uplink (YY=0)
626 -)))
627 -
628 -(((
629 629  To connect a Modbus Alarm with below commands.
630 -)))
631 631  
632 -* (((
633 -The command to active alarm is: 0A 05 00 04 00 01 4C B0. Where 0A 05 00 04 00 01 is the Modbus command to read the register 00 40 where stored the DI status. The 4C B0 is the CRC-16/MODBUS which calculate manually.
634 -)))
555 +* The command to active alarm is: 0A 05 00 04 00 01 4C B0. Where 0A 05 00 04 00 01 is the Modbus command to read the register 00 40 where stored the DI status. The 4C B0 is the CRC-16/MODBUS which calculate manually.
635 635  
636 -* (((
637 -The command to deactivate alarm is: 0A 05 00 04 00 00 8D 70. Where 0A 05 00 04 00 00 is the Modbus command to read the register 00 40 where stored the DI status. The 8D 70 is the CRC-16/MODBUS which calculate manually.
638 -)))
557 +* The command to deactivate alarm is: 0A 05 00 04 00 00 8D 70. Where 0A 05 00 04 00 00 is the Modbus command to read the register 00 40 where stored the DI status. The 8D 70 is the CRC-16/MODBUS which calculate manually.
639 639  
640 -(((
641 641  So if user want to use downlink command to control to RS485 Alarm, he can use:
642 -)))
643 643  
644 -(((
645 -(% style="color:#4f81bd" %)**A8 01 06 0A 05 00 04 00 01 00**(%%): to activate the RS485 Alarm
646 -)))
561 +**A8 01 06 0A 05 00 04 00 01 00**: to activate the RS485 Alarm
647 647  
648 -(((
649 -(% style="color:#4f81bd" %)**A8 01 06 0A 05 00 04 00 00 00**(%%): to deactivate the RS485 Alarm
650 -)))
563 +**A8 01 06 0A 05 00 04 00 00 00**: to deactivate the RS485 Alarm
651 651  
652 -(((
653 653  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.
654 -)))
655 655  
656 -(((
657 -
658 -)))
659 659  
660 -(((
661 -**Example 2** ~-~-> Configure with requesting uplink and original downlink command (**YY=FF**)
662 -)))
568 +**Example 2:**
663 663  
664 -(((
665 -User in IoT server send a downlink command: (% style="color:#4f81bd" %)**A8 01 06 0A 08 00 04 00 01 YY**
666 -)))
570 +Check TTL Sensor return:
667 667  
668 -(((
669 -
670 -)))
572 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image024.png]]
671 671  
672 -(((
673 -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:
674 -)))
675 675  
676 -(((
677 - **A8** (% style="color:#4f81bd" %)**0A 08 00 04 00  **(% style="color:red" %)**01 06** ** **(% style="color:green" %)**0A 08 00 04 00 00**
678 -)))
679 679  
680 -(((
681 - [[image:1654159460680-153.png]]
682 -)))
683 683  
577 +==== Set Payload version ====
684 684  
685 -
686 -
687 -==== **Set Payload version** ====
688 -
689 -(((
690 690  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.
691 -)))
692 692  
693 -* (((
694 -**AT Command:**
695 -)))
581 +* AT Command:
696 696  
697 -(% class="box infomessage" %)
698 -(((
699 -(((
700 -**AT+PAYVER: Set PAYVER field = 1**
701 -)))
702 -)))
583 +AT+PAYVER: Set PAYVER field = 1
703 703  
704 -* (((
705 -**Downlink Payload:**
706 -)))
707 707  
708 -(((
709 -**0xAE 01**  ~-~-> Set PAYVER field =  0x01
710 -)))
586 +* Downlink Payload:
711 711  
712 -(((
713 -**0xAE 0F**   ~-~-> Set PAYVER field =  0x0F
714 -)))
588 +0xAE 01   à Set PAYVER field =  0x01
715 715  
590 +0xAE 0F   à Set PAYVER field =  0x0F
716 716  
717 717  
593 +==== Set RS485 Sampling Commands ====
718 718  
719 -==== **Set RS485 Sampling Commands** ====
595 +AT+COMMANDx, AT+DATACUTx and AT+SEARCHx
720 720  
721 -(((
722 -AT+COMMANDx or AT+DATACUTx
723 -)))
597 +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]].
724 724  
725 -(((
726 -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"]].
727 -)))
728 728  
729 -(((
730 -
731 -)))
600 +* AT Command:
732 732  
733 -* (((
734 -**AT Command:**
735 -)))
602 +AT+COMMANDx: Configure RS485 read command to sensor.
736 736  
737 -(% class="box infomessage" %)
738 -(((
739 -(((
740 -**AT+COMMANDx: Configure RS485 read command to sensor.**
741 -)))
742 -)))
604 +AT+DATACUTx: Configure how to handle return from RS485 devices.
743 743  
744 -(% class="box infomessage" %)
745 -(((
746 -(((
747 -**AT+DATACUTx: Configure how to handle return from RS485 devices.**
748 -)))
749 -)))
606 +AT+SEARCHx: Configure search command
750 750  
751 -(((
752 -
753 -)))
754 754  
755 -* (((
756 -**Downlink Payload:**
757 -)))
609 +* Downlink Payload:
758 758  
759 -(((
760 -**0xAF** downlink command can be used to set AT+COMMANDx or AT+DATACUTx.
761 -)))
611 +0xAF downlink command can be used to set AT+COMMANDx or AT+DATACUTx.
762 762  
763 -(((
764 -(% style="color:red" %)**Note**(%%): if user use AT+COMMANDx to add a new command, he also need to send AT+DATACUTx downlink.
765 -)))
613 +Note: if user use AT+COMMANDx to add a new command, he also need to send AT+DATACUTx downlink.
766 766  
767 -(((
768 768  Format: AF MM NN LL XX XX XX XX YY
769 -)))
770 770  
771 -(((
772 772  Where:
773 -)))
774 774  
775 -* (((
776 -MM: the ATCOMMAND or AT+DATACUT to be set. Value from 01 ~~ 0F,
777 -)))
778 -* (((
779 -NN:  0: no CRC; 1: add CRC-16/MODBUS ; 2: set the AT+DATACUT value.
780 -)))
781 -* (((
782 -LL:  The length of AT+COMMAND or AT+DATACUT command
783 -)))
784 -* (((
785 -XX XX XX XX: AT+COMMAND or AT+DATACUT command
786 -)))
787 -* (((
788 -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.
789 -)))
619 +* MM: the ATCOMMAND or AT+DATACUT to be set. Value from 01 ~~ 0F,
620 +* NN: 0: no CRC; 1: add CRC-16/MODBUS ; 2: set the AT+DATACUT value.
621 +* LL: The length of AT+COMMAND or AT+DATACUT command
622 +* XX XX XX XX: AT+COMMAND or AT+DATACUT command
623 +* 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.
790 790  
791 -(((
792 -**Example:**
793 -)))
625 +Example:
794 794  
795 -(((
796 -(% 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
797 -)))
627 +**AF 03 01 06 0A 05 00 04 00 01 00**: Same as AT+COMMAND3=0A 05 00 04 00 01,1
798 798  
799 -(((
800 -(% 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**
801 -)))
629 +**AF 03 02 06 10 01 05 06 09 0A 00**: Same as AT+DATACUT3=**16**,**1**,**5+6+9+10**
802 802  
803 -(((
804 -(% 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**
805 -)))
631 +**AF 03 02 06 0B 02 05 07 08 0A 00**: Same as AT+DATACUT3=**11**,**2**,**5~~7+8~~10**
806 806  
807 807  
634 +0xAB downlink command can be used for set AT+SEARCHx
808 808  
636 +Example: **AB aa 01 03 xx xx xx** (03 here means there are total 3 bytes after 03) So
809 809  
810 -==== **Fast command to handle MODBUS device** ====
638 +* AB aa 01 03 xx xx xx  same as AT+SEARCHaa=1,xx xx xx
639 +* 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
811 811  
812 -(((
813 -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]].
814 -)))
641 +**AB aa 02 03 xx xx xx 02 yy yy**  same as **AT+SEARCHaa=2,xx xx xx+yy yy**
815 815  
816 -(((
817 -This command is valid since v1.3 firmware version
818 -)))
819 819  
820 -(((
821 -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.
822 -)))
644 +==== Fast command to handle MODBUS device ====
823 823  
824 -(((
825 -
826 -)))
646 +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]].
827 827  
828 -(((
829 -**Example:**
830 -)))
648 +This command is valid since v1.3 firmware version
831 831  
832 -* (((
833 -AT+MBFUN=1 and AT+DATACUT1/AT+DATACUT2 are not configure (0,0,0). So RS485-LN.
834 -)))
835 -* (((
836 -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.
837 -)))
838 -* (((
839 -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.
840 -)))
841 841  
842 -[[image:image-20220602165351-6.png]]
651 +AT+MBFUN has only two value:
843 843  
844 -[[image:image-20220602165351-7.png]]
653 +* AT+MBFUN=1: Enable Modbus reading. And get response base on the MODBUS return
845 845  
655 +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.
846 846  
657 +* AT+MBFUN=0: Disable Modbus fast reading.
847 847  
659 +Example:
848 848  
849 -==== **RS485 command timeout** ====
661 +* AT+MBFUN=1 and AT+DATACUT1/AT+DATACUT2 are not configure (0,0,0).
662 +* 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.
663 +* 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.
850 850  
851 -(((
852 -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.
853 -)))
665 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image025.png]]
854 854  
855 -(((
856 -Default value: 0, range:  0 ~~ 65 seconds
857 -)))
858 858  
859 -* (((
860 -**AT Command:**
861 -)))
668 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image026.png]]
862 862  
863 -(% class="box infomessage" %)
864 -(((
865 -(((
866 -**AT+CMDDLaa=hex(bb cc)*1000**
867 -)))
868 -)))
869 869  
870 -(((
871 -**Example:**
872 -)))
671 +* Downlink Commands:
873 873  
874 -(((
875 -**AT+CMDDL1=1000** to send the open time to 1000ms
876 -)))
673 +A9 aa -à Same as AT+MBFUN=aa
877 877  
878 -(((
879 -
880 -)))
881 881  
882 -* (((
883 -**Downlink Payload:**
884 -)))
676 +==== RS485 command timeout ====
885 885  
886 -(((
887 -**0x AA aa bb cc**
888 -)))
678 +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.
889 889  
890 -(((
891 -Same as: AT+CMDDLaa=hex(bb cc)*1000
892 -)))
680 +Default value: 0, range:  0 ~~ 5 seconds
893 893  
894 -(((
895 - **Example:**
896 -)))
897 897  
898 -(((
899 - 0xAA 01 00 01  ~-~-> Same as **AT+CMDDL1=1000 ms**
900 -)))
683 +* AT Command:
901 901  
685 +AT+CMDDLaa=hex(bb cc)
902 902  
687 +Example:
903 903  
689 +**AT+CMDDL1=1000** to send the open time to 1000ms
904 904  
905 -==== **Uplink payload mode** ====
906 906  
907 -(((
908 -Define to use one uplink or multiple uplinks for the sampling.
909 -)))
692 +* Downlink Payload:
910 910  
911 -(((
912 -The use of this command please see: [[Compose Uplink payload>>||anchor="H3.3.4Composetheuplinkpayload"]]
913 -)))
694 +0x AA aa bb cc
914 914  
915 -* (((
916 -**AT Command:**
917 -)))
696 +Same as: AT+CMDDLaa=hex(bb cc)
918 918  
919 -(% class="box infomessage" %)
920 -(((
921 -(((
922 -**AT+DATAUP=0**
923 -)))
924 -)))
698 + Example:
925 925  
926 -(% class="box infomessage" %)
927 -(((
928 -(((
929 -**AT+DATAUP=1**
930 -)))
931 -)))
700 + 0xAA 01 03 E8  à Same as **AT+CMDDL1=1000 ms**
932 932  
933 -(((
934 -
935 -)))
936 936  
937 -* (((
938 -**Downlink Payload:**
939 -)))
703 +==== [[Uplink>>path:#downlink_A8]] payload mode ====
940 940  
941 -(((
942 -**0xAD 00**  **~-~->** Same as AT+DATAUP=0
943 -)))
705 +Define to use one uplink or multiple uplinks for the sampling.
944 944  
945 -(((
946 -**0xAD 01**  **~-~->** Same as AT+DATAUP=1
947 -)))
707 +The use of this command please see: [[Compose Uplink payload>>path:#DataUP]]
948 948  
709 +* AT Command:
949 949  
711 +AT+DATAUP=0
950 950  
713 +AT+DATAUP=1
951 951  
952 -==== **Manually trigger an Uplink** ====
953 953  
954 -(((
955 -Ask device to send an uplink immediately.
956 -)))
716 +* Downlink Payload:
957 957  
958 -* (((
959 -**AT Command:**
960 -)))
718 +0xAD 00   à Same as AT+DATAUP=0
961 961  
962 -(((
963 -No AT Command for this, user can press the [[ACT button>>||anchor="H3.7Buttons"]] for 1 second for the same.
964 -)))
720 +0xAD 01   à Same as AT+DATAUP=1
965 965  
966 -(((
967 -
968 -)))
969 969  
970 -* (((
971 -**Downlink Payload:**
972 -)))
723 +==== Manually trigger an Uplink ====
973 973  
974 -(((
975 -**0x08 FF**, RS485-LN will immediately send an uplink.
976 -)))
725 +Ask device to send an uplink immediately.
977 977  
727 +* Downlink Payload:
978 978  
729 +0x08 FF, RS485-BL will immediately send an uplink.
979 979  
980 980  
981 -==== **Clear RS485 Command** ====
732 +==== Clear RS485 Command ====
982 982  
983 -(((
984 984  The AT+COMMANDx and AT+DATACUTx settings are stored in special location, user can use below command to clear them.
985 -)))
986 986  
987 -* (((
988 -**AT Command:**
989 -)))
990 990  
991 -(((
737 +* AT Command:
738 +
992 992  **AT+CMDEAR=mm,nn**   mm: start position of erase ,nn: stop position of erase
993 -)))
994 994  
995 -(((
996 996  Etc. AT+CMDEAR=1,10 means erase AT+COMMAND1/AT+DATACUT1 to AT+COMMAND10/AT+DATACUT10
997 -)))
998 998  
999 -(((
1000 1000  Example screen shot after clear all RS485 commands. 
1001 -)))
1002 1002  
1003 -(((
1004 -
1005 -)))
1006 1006  
1007 -(((
746 +
1008 1008  The uplink screen shot is:
1009 -)))
1010 1010  
1011 -[[image:1654160691922-496.png]]
749 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png]]
1012 1012  
1013 1013  
1014 -* (((
1015 -**Downlink Payload:**
1016 -)))
752 +* Downlink Payload:
1017 1017  
1018 -(((
1019 -**0x09 aa bb** same as AT+CMDEAR=aa,bb
1020 -)))
754 +0x09 aa bb same as AT+CMDEAR=aa,bb
1021 1021  
1022 1022  
757 +==== Set Serial Communication Parameters ====
1023 1023  
1024 -
1025 -==== **Set Serial Communication Parameters** ====
1026 -
1027 -(((
1028 1028  Set the Rs485 serial communication parameters:
1029 -)))
1030 1030  
1031 -* (((
1032 -**AT Command:**
1033 -)))
761 +* AT Command:
1034 1034  
1035 -(((
1036 1036  Set Baud Rate:
1037 -)))
1038 1038  
1039 -(% class="box infomessage" %)
1040 -(((
1041 -(((
1042 -**AT+BAUDR=9600**    ~/~/ Options: (1200,2400,4800,14400,19200,115200)
1043 -)))
1044 -)))
765 +AT+BAUDR=9600    ~/~/ Options: (1200,2400,4800,14400,19200,115200)
1045 1045  
1046 -(((
1047 -Set UART Parity
1048 -)))
1049 1049  
1050 -(% class="box infomessage" %)
1051 -(((
1052 -(((
1053 -**AT+PARITY=0**    ~/~/ Option: 0: no parity, 1: odd parity, 2: even parity
1054 -)))
1055 -)))
768 +Set UART parity
1056 1056  
1057 -(((
770 +AT+PARITY=0    ~/~/ Option: 0: no parity, 1: odd parity, 2: even parity
771 +
772 +
1058 1058  Set STOPBIT
1059 -)))
1060 1060  
1061 -(% class="box infomessage" %)
1062 -(((
1063 -(((
1064 -**AT+STOPBIT=0**    ~/~/ Option: 0 for 1bit; 1 for 1.5 bit ; 2 for 2 bits
1065 -)))
1066 -)))
775 +AT+STOPBIT=0    ~/~/ Option: 0 for 1bit; 1 for 1.5 bit ; 2 for 2 bits
1067 1067  
1068 -(((
1069 -
1070 -)))
1071 1071  
1072 -* (((
1073 -**Downlink Payload:**
1074 -)))
778 +* Downlink Payload:
1075 1075  
1076 -(((
1077 -**A7 01 aa bb**: Same  AT+BAUDR=hex(aa bb)*100
1078 -)))
780 +A7 01 aa bb: Same  AT+BAUDR=hex(aa bb)*100
1079 1079  
1080 -(((
1081 -**Example:**
1082 -)))
782 +Example:
1083 1083  
1084 -* (((
1085 -A7 01 00 60   same as AT+BAUDR=9600
1086 -)))
1087 -* (((
1088 -A7 01 04 80  same as AT+BAUDR=115200
1089 -)))
784 +* A7 01 00 60   same as AT+BAUDR=9600
785 +* A7 01 04 80  same as AT+BAUDR=115200
1090 1090  
1091 -(((
1092 1092  A7 02 aa: Same as  AT+PARITY=aa  (aa value: 00 , 01 or 02)
1093 -)))
1094 1094  
1095 -(((
1096 1096  A7 03 aa: Same as  AT+STOPBIT=aa  (aa value: 00 , 01 or 02)
1097 -)))
1098 1098  
1099 1099  
792 +==== Control output power duration ====
1100 1100  
794 +User can set the output power duration before each sampling.
1101 1101  
1102 -== 3.6 Listening mode for RS485 network ==
796 +* AT Command:
1103 1103  
1104 -(((
1105 -This feature support since firmware v1.4
1106 -)))
798 +Example:
1107 1107  
1108 -(((
1109 -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.
1110 -)))
800 +AT+3V3T=1000 ~/~/ 3V3 output power will open 1s before each sampling.
1111 1111  
1112 -[[image:image-20220602171200-8.png||height="567" width="1007"]]
802 +AT+5VT=1000 ~/~/ +5V output power will open 1s before each sampling.
1113 1113  
1114 -(((
1115 -To enable the listening mode, use can run the command AT+RXMODE.
1116 -)))
1117 1117  
1118 -(((
1119 -
1120 -)))
805 +* LoRaWAN Downlink Command:
1121 1121  
1122 -(% border="1" cellspacing="10" style="background-color:#ffffcc; width:500px" %)
1123 -|=(% style="width: 100px;" %)(((
1124 -**Command example**
1125 -)))|=(% style="width: 400px;" %)(((
1126 -**Function**
1127 -)))
1128 -|(% style="width:100px" %)(((
1129 -AT+RXMODE=1,10
1130 -)))|(% style="width:400px" %)(((
1131 -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.
1132 -)))
1133 -|(% style="width:100px" %)(((
1134 -AT+RXMODE=2,500
1135 -)))|(% style="width:400px" %)(((
1136 -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
1137 -)))
1138 -|(% style="width:100px" %)(((
1139 -AT+RXMODE=0,0
1140 -)))|(% style="width:400px" %)(((
1141 -Disable listening mode. This is the default settings.
1142 -)))
1143 -|(% style="width:100px" %)(((
1144 -
1145 -)))|(% style="width:400px" %)(((
1146 -A6 aa bb cc  same as AT+RXMODE=aa,(bb<<8 | cc)
1147 -)))
807 +07 01 aa bb  Same as AT+5VT=(aa bb)
1148 1148  
1149 -(((
1150 -**Downlink Command:**
1151 -)))
809 +07 02 aa bb  Same as AT+3V3T=(aa bb)
1152 1152  
1153 -(((
1154 -**0xA6 aa bb cc ** same as AT+RXMODE=aa,(bb<<8 | cc)
1155 -)))
1156 1156  
1157 -(((
1158 -
1159 -)))
1160 1160  
1161 -(((
1162 -**Example**:
1163 -)))
1164 1164  
1165 -(((
1166 -The RS485-LN is set to AT+RXMODE=2,1000
1167 -)))
814 +1.
815 +11. Buttons
1168 1168  
1169 -(((
1170 -There is a two Modbus commands in the RS485 network as below:
1171 -)))
817 +|**Button**|**Feature**
818 +|**RST**|Reboot RS485-BL
1172 1172  
1173 -(((
1174 -The Modbus master send a command: (% style="background-color:#ffc000" %)01 03 00 00 00 02 c4 0b
1175 -)))
820 +1.
821 +11. +3V3 Output
1176 1176  
1177 -(((
1178 -And Modbus slave reply with: (% style="background-color:green" %)01 03 04 00 00 00 00 fa 33
1179 -)))
823 +RS485-BL has a Controllable +3V3 output, user can use this output to power external sensor.
1180 1180  
1181 -(((
1182 -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
1183 -)))
825 +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. 
1184 1184  
1185 -(((
1186 -[[image:image-20220602171200-9.png]]
1187 -)))
1188 1188  
1189 -(((
1190 -
1191 -)))
828 +The +3V3 output time can be controlled by AT Command.
1192 1192  
1193 -(((
1194 -(((
1195 -(% 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.
1196 -)))
1197 -)))
830 +**AT+3V3T=1000**
1198 1198  
832 +Means set +3v3 valid time to have 1000ms. So, the real +3v3 output will actually have 1000ms + sampling time for other sensors.
1199 1199  
1200 -== 3.7 Buttons ==
1201 1201  
835 +By default, the AT+3V3T=0. This is a special case, means the +3V3 output is always on at any time
1202 1202  
1203 -(% border="1" cellspacing="10" style="background-color:#f7faff; width:430px" %)
1204 -|=(% style="width: 50px;" %)**Button**|=(% style="width: 361px;" %)**Feature**
1205 -|(% style="width:50px" %)**ACT**|(% style="width:361px" %)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**
1206 -|(% style="width:50px" %)**RST**|(% style="width:361px" %)Reboot RS485
1207 -|(% style="width:50px" %)**PRO**|(% style="width:361px" %)Use for upload image, see [[How to Update Image>>||anchor="H6.1Howtoupgradetheimage3F"]]
1208 1208  
838 +1.
839 +11. +5V Output
1209 1209  
841 +RS485-BL has a Controllable +5V output, user can use this output to power external sensor.
1210 1210  
1211 -== 3.8 LEDs ==
843 +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. 
1212 1212  
1213 1213  
1214 -(% border="1" cellspacing="10" style="background-color:#f7faff; width:430px" %)
1215 -|=(% style="width: 50px;" %)**LEDs**|=(% style="width: 380px;" %)**Feature**
1216 -|**PWR**|Always on if there is power
1217 -|**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.
846 +The 5V output time can be controlled by AT Command.
1218 1218  
848 +**AT+5VT=1000**
1219 1219  
850 +Means set 5V valid time to have 1000ms. So, the real 5V output will actually have 1000ms + sampling time for other sensors.
1220 1220  
1221 -= 4. Case Study =
1222 1222  
1223 -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]]
853 +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.
1224 1224  
1225 1225  
1226 -= 5. Use AT Command =
1227 1227  
1228 -== 5.1 Access AT Command ==
1229 1229  
1230 -(((
1231 -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.
1232 -)))
858 +1.
859 +11. LEDs
1233 1233  
1234 -[[image:1654162355560-817.png]]
861 +|**LEDs**|**Feature**
862 +|**LED1**|Blink when device transmit a packet.
1235 1235  
864 +1.
865 +11. Switch Jumper
1236 1236  
1237 -(((
1238 -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:
867 +|**Switch Jumper**|**Feature**
868 +|**SW1**|(((
869 +ISP position: Upgrade firmware via UART
870 +
871 +Flash position: Configure device, check running status.
1239 1239  )))
873 +|**SW2**|(((
874 +5V position: set to compatible with 5v I/O.
1240 1240  
1241 -[[image:1654162368066-342.png]]
876 +3.3v position: set to compatible with 3.3v I/O.,
877 +)))
1242 1242  
879 ++3.3V: is always ON
1243 1243  
1244 -(((
1245 -More detail AT Command manual can be found at [[AT Command Manual>>https://www.dragino.com/downloads/index.php?dir=LT_LoRa_IO_Controller/LT33222-L/]]
1246 -)))
881 ++5V: Only open before every sampling. The time is by default, it is AT+5VT=0.  Max open time. 5000 ms.
1247 1247  
883 +1. Case Study
1248 1248  
885 +User can check this URL for some case studies.
1249 1249  
1250 -== 5.2 Common AT Command Sequence ==
887 +[[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]]
1251 1251  
1252 -=== 5.2.1 Multi-channel ABP mode (Use with SX1301/LG308) ===
1253 1253  
1254 -If device has not joined network yet:
1255 1255  
1256 -(% class="box infomessage" %)
1257 -(((
1258 -**AT+FDR**
1259 -)))
1260 1260  
1261 -(% class="box infomessage" %)
1262 -(((
1263 -**AT+NJM=0**
1264 -)))
892 +1. Use AT Command
893 +11. Access AT Command
1265 1265  
1266 -(% class="box infomessage" %)
1267 -(((
1268 -**ATZ**
1269 -)))
895 +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.
1270 1270  
897 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image027.png]]
1271 1271  
1272 -(((
1273 -If device already joined network:
1274 -)))
1275 1275  
1276 -(% class="box infomessage" %)
1277 -(((
1278 -**AT+NJM=0**
1279 -)))
900 +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:
1280 1280  
1281 -(% class="box infomessage" %)
1282 -(((
1283 -**ATZ**
1284 -)))
902 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image028.png]]
1285 1285  
1286 1286  
1287 -=== 5.5.2 Single-channel ABP mode (Use with LG01/LG02) ===
1288 1288  
906 +More detail AT Command manual can be found at [[AT Command Manual>>path:#AT_COMMAND]]
1289 1289  
1290 -(% style="background-color:#dcdcdc" %)**AT+FDR** (%%) Reset Parameters to Factory Default, Keys Reserve
1291 1291  
1292 -(% style="background-color:#dcdcdc" %)**AT+NJM=0 **(%%)Set to ABP mode
1293 1293  
1294 -(% style="background-color:#dcdcdc" %)**AT+ADR=0** (%%)Set the Adaptive Data Rate Off
910 +1.
911 +11. Common AT Command Sequence
912 +111. Multi-channel ABP mode (Use with SX1301/LG308)
1295 1295  
1296 -(% style="background-color:#dcdcdc" %)**AT+DR=5**   (%%)Set Data Rate
914 +If device has not joined network yet:
1297 1297  
1298 -(% style="background-color:#dcdcdc" %)**AT+TDC=60000** (%%) Set transmit interval to 60 seconds
916 +AT+FDR
1299 1299  
1300 -(% style="background-color:#dcdcdc" %)**AT+CHS=868400000**(%%) Set transmit frequency to 868.4Mhz
918 +AT+NJM=0
1301 1301  
1302 -(% style="background-color:#dcdcdc" %)**AT+RX2FQ=868400000** (%%) Set RX2Frequency to 868.4Mhz (according to the result from server)
920 +ATZ
1303 1303  
1304 -(% style="background-color:#dcdcdc" %)**AT+RX2DR=5**  (%%) Set RX2DR to match the downlink DR from server. see below
1305 1305  
1306 -(% 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.
923 +If device already joined network:
1307 1307  
1308 -(% style="background-color:#dcdcdc" %)**ATZ**       (%%) Reset MCU
925 +AT+NJM=0
1309 1309  
927 +ATZ
1310 1310  
1311 -(% style="color:red" %)**Note:**
929 +1.
930 +11.
931 +111. Single-channel ABP mode (Use with LG01/LG02)
1312 1312  
1313 -(((
1314 -(% style="color:red" %)1. Make sure the device is set to ABP mode in the IoT Server.
1315 -2. Make sure the LG01/02 gateway RX frequency is exactly the same as AT+CHS setting.
1316 -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.
1317 -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
1318 -)))
933 +AT+FDR   Reset Parameters to Factory Default, Keys Reserve
1319 1319  
1320 -[[image:1654162478620-421.png]]
935 +AT+NJM=0 Set to ABP mode
1321 1321  
937 +AT+ADR=0 Set the Adaptive Data Rate Off
1322 1322  
1323 -= 6. FAQ =
939 +AT+DR= Set Data Rate
1324 1324  
1325 -== 6.1 How to upgrade the image? ==
941 +AT+TDC=60000  Set transmit interval to 60 seconds
1326 1326  
1327 -(((
1328 -The RS485-LN LoRaWAN Controller is shipped with a 3.5mm cable, the cable is used to upload image to RS485-LN to:
1329 -)))
943 +AT+CHS=868400000 Set transmit frequency to 868.4Mhz
1330 1330  
1331 -* (((
1332 -Support new features
1333 -)))
1334 -* (((
1335 -For bug fix
1336 -)))
1337 -* (((
1338 -Change LoRaWAN bands.
1339 -)))
945 +AT+RX2FQ=868400000 Set RX2Frequency to 868.4Mhz (according to the result from server)
1340 1340  
1341 -(((
1342 -Below shows the hardware connection for how to upload an image to RS485-LN:
1343 -)))
947 +AT+RX2DR=5  Set RX2DR to match the downlink DR from server. see below
1344 1344  
1345 -[[image:1654162535040-878.png]]
949 +AT+DADDR=26 01 1A F1 Set Device Address to 26 01 1A F1, this ID can be found in the LoRa Server portal.
1346 1346  
1347 -(((
951 +ATZ          Reset MCU
952 +
953 +**Note:**
954 +
955 +1. Make sure the device is set to ABP mode in the IoT Server.
956 +1. Make sure the LG01/02 gateway RX frequency is exactly the same as AT+CHS setting.
957 +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.
958 +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
959 +
960 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image029.png]]
961 +
962 +
963 +1. FAQ
964 +11. How to upgrade the image?
965 +
966 +The RS485-BL LoRaWAN Controller is shipped with a 3.5mm cable, the cable is used to upload image to RS485-BL to:
967 +
968 +* Support new features
969 +* For bug fix
970 +* Change LoRaWAN bands.
971 +
972 +Below shows the hardware connection for how to upload an image to RS485-BL:
973 +
974 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image030.png]]
975 +
1348 1348  **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]].
1349 -)))
1350 1350  
1351 -(((
1352 1352  **Step2**: Download the [[LT Image files>>url:http://www.dragino.com/downloads/index.php?dir=LT_LoRa_IO_Controller/LT33222-L/image/]].
1353 -)))
1354 1354  
1355 -(((
1356 1356  **Step3: **Open flashloader; choose the correct COM port to update.
981 +
982 +
983 +|(((
984 +HOLD PRO then press the RST button, SYS will be ON, then click next
1357 1357  )))
1358 1358  
1359 -(((
1360 -(((
1361 -(((
1362 -(% 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.
987 +|(((
988 +Board detected
1363 1363  )))
990 +
991 +|(((
992 +
1364 1364  )))
1365 -)))
1366 1366  
995 +[[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]]
1367 1367  
1368 -[[image:image-20220602175818-12.png]]
1369 1369  
1370 1370  
1371 -[[image:image-20220602175848-13.png]]
999 +[[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]]
1372 1372  
1373 1373  
1374 -[[image:image-20220602175912-14.png]]
1002 +[[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]]
1375 1375  
1376 1376  
1377 -**Notice**: In case user has lost the program cable. User can hand made one from a 3.5mm cable. The pin mapping is:
1005 +1.
1006 +11. How to change the LoRa Frequency Bands/Region?
1378 1378  
1379 -[[image:image-20220602175638-10.png]]
1008 +User can follow the introduction for [[how to upgrade image>>path:#upgrade_image]]. When download the images, choose the required image file for download.
1380 1380  
1381 1381  
1382 -== 6.2 How to change the LoRa Frequency Bands/Region? ==
1383 1383  
1384 -User can follow the introduction for [[how to upgrade image>>||anchor="H6.1Howtoupgradetheimage3F"]]. When download the images, choose the required image file for download.
1012 +1.
1013 +11. How many RS485-Slave can RS485-BL connects?
1385 1385  
1015 +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]].
1386 1386  
1387 -== 6.3 How many RS485-Slave can RS485-BL connects? ==
1388 1388  
1389 -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"]].
1390 1390  
1391 1391  
1392 -== 6.4 Compatible question to ChirpStack and TTI LoRaWAN server ? ==
1020 +1. Trouble Shooting     
1021 +11. Downlink doesn’t work, how to solve it?
1393 1393  
1394 -When user need to use with ChirpStack or TTI. Please set AT+RPL=4.
1023 +Please see this link for debug:
1395 1395  
1396 -Detail info check this link: [[Set Packet Receiving Response Level>>doc:Main.End Device AT Commands and Downlink Command.WebHome||anchor="H7.23SetPacketReceivingResponseLevel"]]
1025 +[[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]] 
1397 1397  
1398 1398  
1399 -= 7. Trouble Shooting =
1400 1400  
1401 -== 7.1 Downlink doesn’t work, how to solve it? ==
1029 +1.
1030 +11. Why I can’t join TTN V3 in US915 /AU915 bands?
1402 1402  
1403 -Please see this link for debug: [[LoRaWAN Communication Debug>>doc:Main.LoRaWAN Communication Debug.WebHome]]
1032 +It might about the channels mapping. Please see for detail.
1404 1404  
1034 +[[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]]
1405 1405  
1406 -== 7.2 Why I can’t join TTN V3 in US915 /AU915 bands? ==
1407 1407  
1408 -It might about the channels mapping. Please see for detail: [[Notice of Frequency band>>doc:Main.LoRaWAN Communication Debug.WebHome||anchor="H2.NoticeofUS9152FCN4702FAU915Frequencyband"]]
1409 1409  
1038 +1. Order Info
1410 1410  
1411 -= 8. Order Info =
1040 +**Part Number: RS485-BL-XXX**
1412 1412  
1413 -(% style="color:blue" %)**Part Number: RS485-LN-XXX**
1042 +**XXX:**
1414 1414  
1415 -(% style="color:blue" %)**XXX:**
1044 +* **EU433**: frequency bands EU433
1045 +* **EU868**: frequency bands EU868
1046 +* **KR920**: frequency bands KR920
1047 +* **CN470**: frequency bands CN470
1048 +* **AS923**: frequency bands AS923
1049 +* **AU915**: frequency bands AU915
1050 +* **US915**: frequency bands US915
1051 +* **IN865**: frequency bands IN865
1052 +* **RU864**: frequency bands RU864
1053 +* **KZ865: **frequency bands KZ865
1416 1416  
1417 -* (% style="color:blue" %)**EU433**(%%): frequency bands EU433
1418 -* (% style="color:blue" %)**EU868**(%%): frequency bands EU868
1419 -* (% style="color:blue" %)**KR920**(%%): frequency bands KR920
1420 -* (% style="color:blue" %)**CN470**(%%): frequency bands CN470
1421 -* (% style="color:blue" %)**AS923**(%%): frequency bands AS923
1422 -* (% style="color:blue" %)**AU915**(%%): frequency bands AU915
1423 -* (% style="color:blue" %)**US915**(%%): frequency bands US915
1424 -* (% style="color:blue" %)**IN865**(%%): frequency bands IN865
1425 -* (% style="color:blue" %)**RU864**(%%): frequency bands RU864
1426 -* (% style="color:blue" %)**KZ865**(%%): frequency bands KZ865
1055 +1. Packing Info
1427 1427  
1428 -= 9.Packing Info =
1429 -
1430 -
1431 1431  **Package Includes**:
1432 1432  
1433 -* RS485-LN x 1
1059 +* RS485-BL x 1
1434 1434  * Stick Antenna for LoRa RF part x 1
1435 1435  * Program cable x 1
1436 1436  
... ... @@ -1441,62 +1441,9 @@
1441 1441  * Package Size / pcs : 14.5 x 8 x 5 cm
1442 1442  * Weight / pcs : 170g
1443 1443  
1444 -= 10. FCC Caution for RS485LN-US915 =
1070 +1. Support
1445 1445  
1446 -(((
1447 -Any Changes or modifications not expressly approved by the party responsible for compliance could void the user's authority to operate the equipment.
1448 -)))
1072 +* 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.
1073 +* 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
1449 1449  
1450 -(((
1451 -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.
1452 -)))
1453 -
1454 -(((
1455 -
1456 -)))
1457 -
1458 -(((
1459 -**IMPORTANT NOTE:**
1460 -)))
1461 -
1462 -(((
1463 -**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:
1464 -)))
1465 -
1466 -(((
1467 -—Reorient or relocate the receiving antenna.
1468 -)))
1469 -
1470 -(((
1471 -—Increase the separation between the equipment and receiver.
1472 -)))
1473 -
1474 -(((
1475 -—Connect the equipment into an outlet on a circuit different from that to which the receiver is connected.
1476 -)))
1477 -
1478 -(((
1479 -—Consult the dealer or an experienced radio/TV technician for help.
1480 -)))
1481 -
1482 -(((
1483 -
1484 -)))
1485 -
1486 -(((
1487 -**FCC Radiation Exposure Statement:**
1488 -)))
1489 -
1490 -(((
1491 -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.
1492 -)))
1493 -
1494 -
1495 -= 11. Support =
1496 -
1497 -* (((
1498 -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.
1499 -)))
1500 -* (((
1501 -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]].
1502 -)))
1075 +[[support@dragino.com>>url:file:///D:/市场资料/说明书/LoRa/LT系列/support@dragino.com]]
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-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
image-20220606110929-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -13.9 KB
Content
Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0