Last modified by Karry Zhuang on 2025/03/06 16:34
<
From version < 58.1 >
edited by Xiaoling
on 2022/06/06 11:09
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,7 +90,7 @@
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 95  == 1.3 Features ==
96 96  
... ... @@ -103,7 +103,6 @@
103 103  * Support Modbus protocol
104 104  * Support Interrupt uplink (Since hardware version v1.2)
105 105  
106 -
107 107  == 1.4 Applications ==
108 108  
109 109  * Smart Buildings & Home Automation
... ... @@ -113,7 +113,6 @@
113 113  * Smart Cities
114 114  * Smart Factory
115 115  
116 -
117 117  == 1.5 Firmware Change log ==
118 118  
119 119  [[RS485-LN Image files – Download link and Change log>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/]]
... ... @@ -123,13 +123,9 @@
123 123  
124 124  (((
125 125  (((
126 -(((
127 127  v1.2: Add External Interrupt Pin.
128 -)))
129 129  
130 -(((
131 131  v1.0: Release
132 -)))
133 133  
134 134  
135 135  )))
... ... @@ -157,9 +157,7 @@
157 157  == 3.1 How it works? ==
158 158  
159 159  (((
160 -(((
161 161  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.
162 -)))
163 163  
164 164  
165 165  )))
... ... @@ -183,7 +183,7 @@
183 183  [[image:1653268227651-549.png||height="592" width="720"]]
184 184  
185 185  (((
186 -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:
187 187  )))
188 188  
189 189  (((
... ... @@ -235,7 +235,7 @@
235 235  
236 236  (((
237 237  (((
238 -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.
239 239  )))
240 240  
241 241  (((
... ... @@ -249,19 +249,19 @@
249 249  
250 250  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:
251 251  
252 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)
253 -|=(% style="width: 110px;" %)(((
228 +(% border="1" style="background-color:#ffffcc; color:green; width:782px" %)
229 +|(% style="width:128px" %)(((
254 254  **AT Commands**
255 -)))|=(% style="width: 190px;" %)(((
231 +)))|(% style="width:305px" %)(((
256 256  **Description**
257 -)))|=(% style="width: 190px;" %)(((
233 +)))|(% style="width:346px" %)(((
258 258  **Example**
259 259  )))
260 -|(% style="width:110px" %)(((
236 +|(% style="width:128px" %)(((
261 261  AT+BAUDR
262 -)))|(% style="width:190px" %)(((
238 +)))|(% style="width:305px" %)(((
263 263  Set the baud rate (for RS485 connection). Default Value is: 9600.
264 -)))|(% style="width:190px" %)(((
240 +)))|(% style="width:346px" %)(((
265 265  (((
266 266  AT+BAUDR=9600
267 267  )))
... ... @@ -270,11 +270,11 @@
270 270  Options: (1200,2400,4800,14400,19200,115200)
271 271  )))
272 272  )))
273 -|(% style="width:110px" %)(((
249 +|(% style="width:128px" %)(((
274 274  AT+PARITY
275 -)))|(% style="width:190px" %)(((
251 +)))|(% style="width:305px" %)(((
276 276  Set UART parity (for RS485 connection)
277 -)))|(% style="width:190px" %)(((
253 +)))|(% style="width:346px" %)(((
278 278  (((
279 279  AT+PARITY=0
280 280  )))
... ... @@ -283,9 +283,9 @@
283 283  Option: 0: no parity, 1: odd parity, 2: even parity
284 284  )))
285 285  )))
286 -|(% style="width:110px" %)(((
262 +|(% style="width:128px" %)(((
287 287  AT+STOPBIT
288 -)))|(% style="width:190px" %)(((
264 +)))|(% style="width:305px" %)(((
289 289  (((
290 290  Set serial stopbit (for RS485 connection)
291 291  )))
... ... @@ -293,7 +293,7 @@
293 293  (((
294 294  
295 295  )))
296 -)))|(% style="width:190px" %)(((
272 +)))|(% style="width:346px" %)(((
297 297  (((
298 298  AT+STOPBIT=0 for 1bit
299 299  )))
... ... @@ -307,8 +307,6 @@
307 307  )))
308 308  )))
309 309  
310 -
311 -
312 312  === 3.3.2 Configure sensors ===
313 313  
314 314  (((
... ... @@ -317,18 +317,16 @@
317 317  )))
318 318  )))
319 319  
320 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)
321 -|=(% style="width: 110px;" %)**AT Commands**|=(% style="width: 190px;" %)**Description**|=(% style="width: 190px;" %)**Example**
322 -|AT+CFGDEV|(% style="width:110px" %)(((
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" %)(((
323 323  This command is used to configure the RS485/TTL devices; they won’t be used during sampling.
324 324  
325 325  AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,
326 326  
327 327  mm: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
328 -)))|(% 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
329 329  
330 -
331 -
332 332  === 3.3.3 Configure read commands for each sampling ===
333 333  
334 334  (((
... ... @@ -374,8 +374,8 @@
374 374  
375 375  **AT+DATACUTx : **This command defines how to handle the return from AT+COMMANDx, max return length is 45 bytes.
376 376  
377 -(% border="1" style="background-color:#4bacc6; color:white; width:510px" %)
378 -|(% style="width:510px" %)(((
349 +(% border="1" style="background-color:#4bacc6; color:white; width:725px" %)
350 +|(% style="width:722px" %)(((
379 379  **AT+DATACUTx=a,b,c**
380 380  
381 381  * **a: length for the return of AT+COMMAND**
... ... @@ -444,7 +444,6 @@
444 444  
445 445  (% style="color:#4f81bd" %)**Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA**
446 446  
447 -
448 448  1. PAYVER: Defined by AT+PAYVER
449 449  1. PAYLOAD COUNT: Total how many uplinks of this sampling.
450 450  1. PAYLOAD#: Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT)
... ... @@ -524,43 +524,50 @@
524 524  
525 525  There are two kinds of Commands:
526 526  
527 -* (% 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]]
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]]
528 528  
529 529  * (% style="color:#4f81bd" %)**Sensor Related Commands**(%%): These commands are special designed for RS485-LN.  User can see these commands below:
530 530  
502 +
503 +
531 531  === 3.5.1 Common Commands ===
532 532  
533 533  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]]
534 534  
535 535  
536 -=== 3.5.2 Sensor related commands ===
509 +=== 3.5.2 Sensor related commands: ===
537 537  
538 -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) ====
539 539  
540 -[[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.
541 541  
542 -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
543 543  
517 +**AT+MOD=1** ~/~/ Set to support RS485-MODBUS type sensors. User can connect multiply RS485 , Modbus sensors to the A / B pins.
544 544  
545 -=== 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.
546 546  
547 547  
522 +* Downlink Payload
548 548  
549 -==== **RS485 Debug Command** ====
524 +**0A aa**     à same as AT+MOD=aa
550 550  
551 -This command is used to configure the RS485 devices; they won’t be used during sampling.
552 552  
553 -* **AT Command**
554 554  
555 -(% class="box infomessage" %)
556 -(((
557 -**AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m**
558 -)))
528 +==== [[RS485 Debug Command>>path:#downlink_A8]] (AT+CFGDEV) ====
559 559  
560 -m: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
530 +This command is used to configure the RS485 or TTL sensors; they won’t be used during sampling.
561 561  
562 -* **Downlink Payload**
532 +* AT Command
563 563  
534 +AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
535 +
536 +m: 0: no CRC; 1: add CRC-16/MODBUS in the end of this command.
537 +
538 +
539 +
540 +* Downlink Payload
541 +
564 564  Format: A8 MM NN XX XX XX XX YY
565 565  
566 566  Where:
... ... @@ -568,12 +568,9 @@
568 568  * MM: 1: add CRC-16/MODBUS ; 0: no CRC
569 569  * NN: The length of RS485 command
570 570  * XX XX XX XX: RS485 command total NN bytes
571 -* YY: How many bytes will be uplink from the return of this RS485 command,
572 -** if YY=0, RS485-LN will execute the downlink command without uplink;
573 -** if YY>0, RS485-LN will uplink total YY bytes from the output of this RS485 command; Fport=200
574 -** if YY=FF, RS485-LN will uplink RS485 output with the downlink command content; Fport=200.
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
575 575  
576 -**Example 1** ~-~-> Configure without ask for uplink (YY=0)
551 +**Example 1:**
577 577  
578 578  To connect a Modbus Alarm with below commands.
579 579  
... ... @@ -583,190 +583,184 @@
583 583  
584 584  So if user want to use downlink command to control to RS485 Alarm, he can use:
585 585  
586 -(% style="color:#4f81bd" %)**A8 01 06 0A 05 00 04 00 01 00**(%%): to activate the RS485 Alarm
561 +**A8 01 06 0A 05 00 04 00 01 00**: to activate the RS485 Alarm
587 587  
588 -(% style="color:#4f81bd" %)**A8 01 06 0A 05 00 04 00 00 00**(%%): to deactivate the RS485 Alarm
563 +**A8 01 06 0A 05 00 04 00 00 00**: to deactivate the RS485 Alarm
589 589  
590 590  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.
591 591  
592 592  
593 -**Example 2** ~-~-> Configure with requesting uplink and original downlink command (**YY=FF**)
568 +**Example 2:**
594 594  
595 -User in IoT server send a downlink command: (% style="color:#4f81bd" %)**A8 01 06 0A 08 00 04 00 01 YY**
570 +Check TTL Sensor return:
596 596  
572 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image024.png]]
597 597  
598 -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:
599 599  
600 - **A8** (% style="color:#4f81bd" %)**0A 08 00 04 00  **(% style="color:red" %)**01 06** ** **(% style="color:green" %)**0A 08 00 04 00 00**
601 601  
602 - [[image:1654159460680-153.png]]
603 603  
577 +==== Set Payload version ====
604 604  
605 -
606 -==== **Set Payload version** ====
607 -
608 608  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.
609 609  
610 -* **AT Command:**
581 +* AT Command:
611 611  
612 -(% class="box infomessage" %)
613 -(((
614 -**AT+PAYVER: Set PAYVER field = 1**
615 -)))
583 +AT+PAYVER: Set PAYVER field = 1
616 616  
617 -* **Downlink Payload:**
618 618  
619 -**0xAE 01**  ~-~-> Set PAYVER field =  0x01
586 +* Downlink Payload:
620 620  
621 -**0xAE 0F**   ~-~-> Set PAYVER field =  0x0F
588 +0xAE 01   à Set PAYVER field =  0x01
622 622  
590 +0xAE 0F   à Set PAYVER field =  0x0F
623 623  
624 624  
625 -==== **Set RS485 Sampling Commands** ====
593 +==== Set RS485 Sampling Commands ====
626 626  
627 -AT+COMMANDx or AT+DATACUTx
595 +AT+COMMANDx, AT+DATACUTx and AT+SEARCHx
628 628  
629 -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"]].
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]].
630 630  
631 631  
632 -* **AT Command:**
600 +* AT Command:
633 633  
634 -(% class="box infomessage" %)
635 -(((
636 -**AT+COMMANDx: Configure RS485 read command to sensor.**
637 -)))
602 +AT+COMMANDx: Configure RS485 read command to sensor.
638 638  
639 -(% class="box infomessage" %)
640 -(((
641 -**AT+DATACUTx: Configure how to handle return from RS485 devices.**
642 -)))
604 +AT+DATACUTx: Configure how to handle return from RS485 devices.
643 643  
606 +AT+SEARCHx: Configure search command
644 644  
645 -* **Downlink Payload:**
646 646  
647 -**0xAF** downlink command can be used to set AT+COMMANDx or AT+DATACUTx.
609 +* Downlink Payload:
648 648  
649 -(% style="color:red" %)**Note**(%%): if user use AT+COMMANDx to add a new command, he also need to send AT+DATACUTx downlink.
611 +0xAF downlink command can be used to set AT+COMMANDx or AT+DATACUTx.
650 650  
613 +Note: if user use AT+COMMANDx to add a new command, he also need to send AT+DATACUTx downlink.
614 +
651 651  Format: AF MM NN LL XX XX XX XX YY
652 652  
653 653  Where:
654 654  
655 655  * MM: the ATCOMMAND or AT+DATACUT to be set. Value from 01 ~~ 0F,
656 -* NN:  0: no CRC; 1: add CRC-16/MODBUS ; 2: set the AT+DATACUT value.
657 -* LL:  The length of AT+COMMAND or AT+DATACUT command
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
658 658  * XX XX XX XX: AT+COMMAND or AT+DATACUT command
659 -* 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.
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.
660 660  
661 -**Example:**
625 +Example:
662 662  
663 -(% 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
627 +**AF 03 01 06 0A 05 00 04 00 01 00**: Same as AT+COMMAND3=0A 05 00 04 00 01,1
664 664  
665 -(% 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**
629 +**AF 03 02 06 10 01 05 06 09 0A 00**: Same as AT+DATACUT3=**16**,**1**,**5+6+9+10**
666 666  
667 -(% 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**
631 +**AF 03 02 06 0B 02 05 07 08 0A 00**: Same as AT+DATACUT3=**11**,**2**,**5~~7+8~~10**
668 668  
669 669  
634 +0xAB downlink command can be used for set AT+SEARCHx
670 670  
671 -==== **Fast command to handle MODBUS device** ====
636 +Example: **AB aa 01 03 xx xx xx** (03 here means there are total 3 bytes after 03) So
672 672  
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
640 +
641 +**AB aa 02 03 xx xx xx 02 yy yy**  same as **AT+SEARCHaa=2,xx xx xx+yy yy**
642 +
643 +
644 +==== Fast command to handle MODBUS device ====
645 +
673 673  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]].
674 674  
675 675  This command is valid since v1.3 firmware version
676 676  
677 -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.
678 678  
651 +AT+MBFUN has only two value:
679 679  
680 -**Example:**
653 +* AT+MBFUN=1: Enable Modbus reading. And get response base on the MODBUS return
681 681  
682 -* AT+MBFUN=1 and AT+DATACUT1/AT+DATACUT2 are not configure (0,0,0). So RS485-LN.
683 -* 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.
684 -* 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.
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.
685 685  
686 -[[image:image-20220602165351-6.png]]
657 +* AT+MBFUN=0: Disable Modbus fast reading.
687 687  
688 -[[image:image-20220602165351-7.png]]
659 +Example:
689 689  
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.
690 690  
665 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image025.png]]
691 691  
692 -==== **RS485 command timeout** ====
693 693  
694 -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.
668 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image026.png]]
695 695  
696 -Default value: 0, range:  0 ~~ 65 seconds
697 697  
698 -* **AT Command:**
671 +* Downlink Commands:
699 699  
700 -(% class="box infomessage" %)
701 -(((
702 -**AT+CMDDLaa=hex(bb cc)*1000**
703 -)))
673 +A9 aa -à Same as AT+MBFUN=aa
704 704  
705 -**Example:**
706 706  
707 -**AT+CMDDL1=1000** to send the open time to 1000ms
676 +==== RS485 command timeout ====
708 708  
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.
709 709  
710 -* **Downlink Payload:**
680 +Default value: 0, range:  0 ~~ 5 seconds
711 711  
712 -**0x AA aa bb cc**
713 713  
714 -Same as: AT+CMDDLaa=hex(bb cc)*1000
683 +* AT Command:
715 715  
716 - **Example:**
685 +AT+CMDDLaa=hex(bb cc)
717 717  
718 - 0xAA 01 00 01  ~-~-> Same as **AT+CMDDL1=1000 ms**
687 +Example:
719 719  
689 +**AT+CMDDL1=1000** to send the open time to 1000ms
720 720  
721 721  
722 -==== **Uplink payload mode** ====
692 +* Downlink Payload:
723 723  
724 -Define to use one uplink or multiple uplinks for the sampling.
694 +0x AA aa bb cc
725 725  
726 -The use of this command please see: [[Compose Uplink payload>>||anchor="H3.3.4Composetheuplinkpayload"]]
696 +Same as: AT+CMDDLaa=hex(bb cc)
727 727  
728 -* **AT Command:**
698 + Example:
729 729  
730 -(% class="box infomessage" %)
731 -(((
732 -**AT+DATAUP=0**
733 -)))
700 + 0xAA 01 03 E8  à Same as **AT+CMDDL1=1000 ms**
734 734  
735 -(% class="box infomessage" %)
736 -(((
737 -**AT+DATAUP=1**
738 -)))
739 739  
703 +==== [[Uplink>>path:#downlink_A8]] payload mode ====
740 740  
741 -* **Downlink Payload:**
705 +Define to use one uplink or multiple uplinks for the sampling.
742 742  
743 -**0xAD 00**  **~-~->** Same as AT+DATAUP=0
707 +The use of this command please see: [[Compose Uplink payload>>path:#DataUP]]
744 744  
745 -**0xAD 01**  **~-~->** Same as AT+DATAUP=1
709 +* AT Command:
746 746  
711 +AT+DATAUP=0
747 747  
713 +AT+DATAUP=1
748 748  
749 -==== **Manually trigger an Uplink** ====
750 750  
751 -Ask device to send an uplink immediately.
716 +* Downlink Payload:
752 752  
753 -* **AT Command:**
718 +0xAD 00   à Same as AT+DATAUP=0
754 754  
755 -No AT Command for this, user can press the [[ACT button>>||anchor="H3.7Buttons"]] for 1 second for the same.
720 +0xAD 01   à Same as AT+DATAUP=1
756 756  
757 757  
758 -* **Downlink Payload:**
723 +==== Manually trigger an Uplink ====
759 759  
760 -**0x08 FF**, RS485-LN will immediately send an uplink.
725 +Ask device to send an uplink immediately.
761 761  
727 +* Downlink Payload:
762 762  
729 +0x08 FF, RS485-BL will immediately send an uplink.
763 763  
764 -==== **Clear RS485 Command** ====
765 765  
732 +==== Clear RS485 Command ====
733 +
766 766  The AT+COMMANDx and AT+DATACUTx settings are stored in special location, user can use below command to clear them.
767 767  
768 -* **AT Command:**
769 769  
737 +* AT Command:
738 +
770 770  **AT+CMDEAR=mm,nn**   mm: start position of erase ,nn: stop position of erase
771 771  
772 772  Etc. AT+CMDEAR=1,10 means erase AT+COMMAND1/AT+DATACUT1 to AT+COMMAND10/AT+DATACUT10
... ... @@ -774,50 +774,43 @@
774 774  Example screen shot after clear all RS485 commands. 
775 775  
776 776  
746 +
777 777  The uplink screen shot is:
778 778  
779 -[[image:1654160691922-496.png]]
749 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png]]
780 780  
781 781  
782 -* **Downlink Payload:**
752 +* Downlink Payload:
783 783  
784 -**0x09 aa bb** same as AT+CMDEAR=aa,bb
754 +0x09 aa bb same as AT+CMDEAR=aa,bb
785 785  
786 786  
757 +==== Set Serial Communication Parameters ====
787 787  
788 -==== **Set Serial Communication Parameters** ====
789 -
790 790  Set the Rs485 serial communication parameters:
791 791  
792 -* **AT Command:**
761 +* AT Command:
793 793  
794 794  Set Baud Rate:
795 795  
796 -(% class="box infomessage" %)
797 -(((
798 -**AT+BAUDR=9600**    ~/~/ Options: (1200,2400,4800,14400,19200,115200)
799 -)))
765 +AT+BAUDR=9600    ~/~/ Options: (1200,2400,4800,14400,19200,115200)
800 800  
801 -Set UART Parity
802 802  
803 -(% class="box infomessage" %)
804 -(((
805 -**AT+PARITY=0**    ~/~/ Option: 0: no parity, 1: odd parity, 2: even parity
806 -)))
768 +Set UART parity
807 807  
770 +AT+PARITY=0    ~/~/ Option: 0: no parity, 1: odd parity, 2: even parity
771 +
772 +
808 808  Set STOPBIT
809 809  
810 -(% class="box infomessage" %)
811 -(((
812 -**AT+STOPBIT=0**    ~/~/ Option: 0 for 1bit; 1 for 1.5 bit ; 2 for 2 bits
813 -)))
775 +AT+STOPBIT=0    ~/~/ Option: 0 for 1bit; 1 for 1.5 bit ; 2 for 2 bits
814 814  
815 815  
816 -* **Downlink Payload:**
778 +* Downlink Payload:
817 817  
818 -**A7 01 aa bb**: Same  AT+BAUDR=hex(aa bb)*100
780 +A7 01 aa bb: Same  AT+BAUDR=hex(aa bb)*100
819 819  
820 -**Example:**
782 +Example:
821 821  
822 822  * A7 01 00 60   same as AT+BAUDR=9600
823 823  * A7 01 04 80  same as AT+BAUDR=115200
... ... @@ -827,313 +827,287 @@
827 827  A7 03 aa: Same as  AT+STOPBIT=aa  (aa value: 00 , 01 or 02)
828 828  
829 829  
830 -== 3.6 Listening mode for RS485 network ==
792 +==== Control output power duration ====
831 831  
832 -This feature support since firmware v1.4
794 +User can set the output power duration before each sampling.
833 833  
834 -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.
796 +* AT Command:
835 835  
836 -[[image:image-20220602171200-8.png||height="567" width="1007"]]
798 +Example:
837 837  
838 -To enable the listening mode, use can run the command AT+RXMODE.
800 +AT+3V3T=1000 ~/~/ 3V3 output power will open 1s before each sampling.
839 839  
802 +AT+5VT=1000 ~/~/ +5V output power will open 1s before each sampling.
840 840  
841 -(% border="1" style="background-color:#ffffcc; width:500px" %)
842 -|=(% style="width: 161px;" %)**Command example:**|=(% style="width: 337px;" %)**Function**
843 -|(% 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.
844 -|(% 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
845 -|(% style="width:161px" %)AT+RXMODE=0,0|(% style="width:337px" %)Disable listening mode. This is the default settings.
846 -|(% style="width:161px" %) |(% style="width:337px" %)A6 aa bb cc  same as AT+RXMODE=aa,(bb<<8 ~| cc)
847 847  
848 -**Downlink Command:**
805 +* LoRaWAN Downlink Command:
849 849  
850 -**0xA6 aa bb cc ** same as AT+RXMODE=aa,(bb<<8 | cc)
807 +07 01 aa bb  Same as AT+5VT=(aa bb)
851 851  
809 +07 02 aa bb  Same as AT+3V3T=(aa bb)
852 852  
853 -**Example**:
854 854  
855 -The RS485-LN is set to AT+RXMODE=2,1000
856 856  
857 -There is a two Modbus commands in the RS485 network as below:
858 858  
859 -The Modbus master send a command: (% style="background-color:#ffc000" %)01 03 00 00 00 02 c4 0b
814 +1.
815 +11. Buttons
860 860  
861 -And Modbus slave reply with: (% style="background-color:green" %)01 03 04 00 00 00 00 fa 33
817 +|**Button**|**Feature**
818 +|**RST**|Reboot RS485-BL
862 862  
863 -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
820 +1.
821 +11. +3V3 Output
864 864  
865 -[[image:image-20220602171200-9.png]]
823 +RS485-BL has a Controllable +3V3 output, user can use this output to power external sensor.
866 866  
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. 
867 867  
868 -(% 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.
869 869  
828 +The +3V3 output time can be controlled by AT Command.
870 870  
871 -== 3.7 Buttons ==
830 +**AT+3V3T=1000**
872 872  
832 +Means set +3v3 valid time to have 1000ms. So, the real +3v3 output will actually have 1000ms + sampling time for other sensors.
873 873  
874 -(% border="1" style="background-color:#f7faff; width:500px" %)
875 -|=**Button**|=(% style="width: 1420px;" %)**Feature**
876 -|**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**
877 -|**RST**|(% style="width:1420px" %)Reboot RS485
878 -|**PRO**|(% style="width:1420px" %)Use for upload image, see [[How to Update Image>>||anchor="H6.1Howtoupgradetheimage3F"]]
879 879  
880 -== 3.8 LEDs ==
835 +By default, the AT+3V3T=0. This is a special case, means the +3V3 output is always on at any time
881 881  
882 -(% border="1" style="background-color:#f7faff; width:500px" %)
883 -|=**LEDs**|=**Feature**
884 -|**PWR**|Always on if there is power
885 -|**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.
886 886  
887 -= 4. Case Study =
838 +1.
839 +11. +5V Output
888 888  
889 -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]]
841 +RS485-BL has a Controllable +5V output, user can use this output to power external sensor.
890 890  
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. 
891 891  
892 -= 5. Use AT Command =
893 893  
894 -== 5.1 Access AT Command ==
846 +The 5V output time can be controlled by AT Command.
895 895  
896 -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.
848 +**AT+5VT=1000**
897 897  
898 -[[image:1654162355560-817.png]]
850 +Means set 5V valid time to have 1000ms. So, the real 5V output will actually have 1000ms + sampling time for other sensors.
899 899  
900 900  
901 -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:
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.
902 902  
903 -[[image:1654162368066-342.png]]
904 904  
905 905  
906 -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/]]
907 907  
858 +1.
859 +11. LEDs
908 908  
909 -== 5.2 Common AT Command Sequence ==
861 +|**LEDs**|**Feature**
862 +|**LED1**|Blink when device transmit a packet.
910 910  
911 -=== 5.2.1 Multi-channel ABP mode (Use with SX1301/LG308) ===
864 +1.
865 +11. Switch Jumper
912 912  
913 -If device has not joined network yet:
867 +|**Switch Jumper**|**Feature**
868 +|**SW1**|(((
869 +ISP position: Upgrade firmware via UART
914 914  
915 -(% class="box infomessage" %)
916 -(((
917 -**AT+FDR**
871 +Flash position: Configure device, check running status.
918 918  )))
873 +|**SW2**|(((
874 +5V position: set to compatible with 5v I/O.
919 919  
920 -(% class="box infomessage" %)
921 -(((
922 -**AT+NJM=0**
876 +3.3v position: set to compatible with 3.3v I/O.,
923 923  )))
924 924  
925 -(% class="box infomessage" %)
926 -(((
927 -**ATZ**
928 -)))
879 ++3.3V: is always ON
929 929  
881 ++5V: Only open before every sampling. The time is by default, it is AT+5VT=0.  Max open time. 5000 ms.
930 930  
931 -If device already joined network:
883 +1. Case Study
932 932  
933 -(% class="box infomessage" %)
934 -(((
935 -**AT+NJM=0**
936 -)))
885 +User can check this URL for some case studies.
937 937  
938 -(% class="box infomessage" %)
939 -(((
940 -**ATZ**
941 -)))
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]]
942 942  
943 943  
944 -=== 5.5.2 Single-channel ABP mode (Use with LG01/LG02) ===
945 945  
946 946  
947 -(% style="background-color:#dcdcdc" %)**AT+FDR** (%%) Reset Parameters to Factory Default, Keys Reserve
892 +1. Use AT Command
893 +11. Access AT Command
948 948  
949 -(% style="background-color:#dcdcdc" %)**AT+NJM=0 **(%%)Set to ABP mode
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.
950 950  
951 -(% style="background-color:#dcdcdc" %)**AT+ADR=0** (%%)Set the Adaptive Data Rate Off
897 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image027.png]]
952 952  
953 -(% style="background-color:#dcdcdc" %)**AT+DR=5**   (%%)Set Data Rate
954 954  
955 -(% style="background-color:#dcdcdc" %)**AT+TDC=60000** (%%) Set transmit interval to 60 seconds
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:
956 956  
957 -(% style="background-color:#dcdcdc" %)**AT+CHS=868400000**(%%) Set transmit frequency to 868.4Mhz
902 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image028.png]]
958 958  
959 -(% style="background-color:#dcdcdc" %)**AT+RX2FQ=868400000** (%%) Set RX2Frequency to 868.4Mhz (according to the result from server)
960 960  
961 -(% style="background-color:#dcdcdc" %)**AT+RX2DR=5**  (%%) Set RX2DR to match the downlink DR from server. see below
962 962  
963 -(% 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.
906 +More detail AT Command manual can be found at [[AT Command Manual>>path:#AT_COMMAND]]
964 964  
965 -(% style="background-color:#dcdcdc" %)**ATZ**       (%%) Reset MCU
966 966  
967 967  
968 -(% style="color:red" %)**Note:**
910 +1.
911 +11. Common AT Command Sequence
912 +111. Multi-channel ABP mode (Use with SX1301/LG308)
969 969  
970 -(% style="color:red" %)1. Make sure the device is set to ABP mode in the IoT Server.
971 -2. Make sure the LG01/02 gateway RX frequency is exactly the same as AT+CHS setting.
972 -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.
973 -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
914 +If device has not joined network yet:
974 974  
975 -[[image:1654162478620-421.png]]
916 +AT+FDR
976 976  
918 +AT+NJM=0
977 977  
978 -= 6. FAQ =
920 +ATZ
979 979  
980 -== 6.1 How to upgrade the image? ==
981 981  
982 -The RS485-LN LoRaWAN Controller is shipped with a 3.5mm cable, the cable is used to upload image to RS485-LN to:
923 +If device already joined network:
983 983  
984 -* Support new features
985 -* For bug fix
986 -* Change LoRaWAN bands.
925 +AT+NJM=0
987 987  
988 -Below shows the hardware connection for how to upload an image to RS485-LN:
927 +ATZ
989 989  
990 -[[image:1654162535040-878.png]]
929 +1.
930 +11.
931 +111. Single-channel ABP mode (Use with LG01/LG02)
991 991  
992 -**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]].
933 +AT+FDR   Reset Parameters to Factory Default, Keys Reserve
993 993  
994 -**Step2**: Download the [[LT Image files>>url:http://www.dragino.com/downloads/index.php?dir=LT_LoRa_IO_Controller/LT33222-L/image/]].
935 +AT+NJM=0 Set to ABP mode
995 995  
996 -**Step3: **Open flashloader; choose the correct COM port to update.
937 +AT+ADR=0 Set the Adaptive Data Rate Off
997 997  
998 -(((
999 -(% 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.
1000 -)))
939 +AT+DR=5  Set Data Rate
1001 1001  
941 +AT+TDC=60000  Set transmit interval to 60 seconds
1002 1002  
1003 -[[image:image-20220602175818-12.png]]
943 +AT+CHS=868400000 Set transmit frequency to 868.4Mhz
1004 1004  
945 +AT+RX2FQ=868400000 Set RX2Frequency to 868.4Mhz (according to the result from server)
1005 1005  
1006 -[[image:image-20220602175848-13.png]]
947 +AT+RX2DR=5  Set RX2DR to match the downlink DR from server. see below
1007 1007  
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.
1008 1008  
1009 -[[image:image-20220602175912-14.png]]
951 +ATZ          Reset MCU
1010 1010  
953 +**Note:**
1011 1011  
1012 -**Notice**: In case user has lost the program cable. User can hand made one from a 3.5mm cable. The pin mapping is:
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
1013 1013  
1014 -[[image:image-20220602175638-10.png]]
960 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image029.png]]
1015 1015  
1016 1016  
1017 -== 6.2 How to change the LoRa Frequency Bands/Region? ==
963 +1. FAQ
964 +11. How to upgrade the image?
1018 1018  
1019 -User can follow the introduction for [[how to upgrade image>>||anchor="H6.1Howtoupgradetheimage3F"]]. When download the images, choose the required image file for download.
966 +The RS485-BL LoRaWAN Controller is shipped with a 3.5mm cable, the cable is used to upload image to RS485-BL to:
1020 1020  
968 +* Support new features
969 +* For bug fix
970 +* Change LoRaWAN bands.
1021 1021  
1022 -== 6.3 How many RS485-Slave can RS485-BL connects? ==
972 +Below shows the hardware connection for how to upload an image to RS485-BL:
1023 1023  
1024 -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"]].
974 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image030.png]]
1025 1025  
976 +**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]].
1026 1026  
1027 -== 6.4 Compatible question to ChirpStack and TTI LoRaWAN server ? ==
978 +**Step2**: Download the [[LT Image files>>url:http://www.dragino.com/downloads/index.php?dir=LT_LoRa_IO_Controller/LT33222-L/image/]].
1028 1028  
1029 -When user need to use with ChirpStack or TTI. Please set AT+RPL=4.
980 +**Step3: **Open flashloader; choose the correct COM port to update.
1030 1030  
1031 -Detail info check this link: [[Set Packet Receiving Response Level>>doc:Main.End Device AT Commands and Downlink Command.WebHome||anchor="H7.23SetPacketReceivingResponseLevel"]]
1032 1032  
983 +|(((
984 +HOLD PRO then press the RST button, SYS will be ON, then click next
985 +)))
1033 1033  
1034 -= 7. Trouble Shooting =
987 +|(((
988 +Board detected
989 +)))
1035 1035  
1036 -== 7.1 Downlink doesn’t work, how to solve it? ==
991 +|(((
992 +
993 +)))
1037 1037  
1038 -Please see this link for debug: [[LoRaWAN Communication Debug>>doc:Main.LoRaWAN Communication Debug.WebHome]]
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]]
1039 1039  
1040 1040  
1041 -== 7.2 Why I can’t join TTN V3 in US915 /AU915 bands? ==
1042 1042  
1043 -It might about the channels mapping. Please see for detail: [[Notice of Frequency band>>doc:Main.LoRaWAN Communication Debug.WebHome||anchor="H2.NoticeofUS9152FCN4702FAU915Frequencyband"]]
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]]
1044 1044  
1045 1045  
1046 -= 8. Order Info =
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]]
1047 1047  
1048 -(% style="color:blue" %)**Part Number: RS485-LN-XXX**
1049 1049  
1050 -(% style="color:blue" %)**XXX:**
1005 +1.
1006 +11. How to change the LoRa Frequency Bands/Region?
1051 1051  
1052 -* (% style="color:blue" %)**EU433**(%%): frequency bands EU433
1053 -* (% style="color:blue" %)**EU868**(%%): frequency bands EU868
1054 -* (% style="color:blue" %)**KR920**(%%): frequency bands KR920
1055 -* (% style="color:blue" %)**CN470**(%%): frequency bands CN470
1056 -* (% style="color:blue" %)**AS923**(%%): frequency bands AS923
1057 -* (% style="color:blue" %)**AU915**(%%): frequency bands AU915
1058 -* (% style="color:blue" %)**US915**(%%): frequency bands US915
1059 -* (% style="color:blue" %)**IN865**(%%): frequency bands IN865
1060 -* (% style="color:blue" %)**RU864**(%%): frequency bands RU864
1061 -* (% style="color:blue" %)**KZ865**(%%): frequency bands KZ865
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.
1062 1062  
1063 1063  
1064 -= 9.Packing Info =
1065 1065  
1012 +1.
1013 +11. How many RS485-Slave can RS485-BL connects?
1066 1066  
1067 -**Package Includes**:
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]].
1068 1068  
1069 -* RS485-LN x 1
1070 -* Stick Antenna for LoRa RF part x 1
1071 -* Program cable x 1
1072 1072  
1073 -**Dimension and weight**:
1074 1074  
1075 -* Device Size: 13.5 x 7 x 3 cm
1076 -* Device Weight: 105g
1077 -* Package Size / pcs : 14.5 x 8 x 5 cm
1078 -* Weight / pcs : 170g
1079 1079  
1020 +1. Trouble Shooting     
1021 +11. Downlink doesn’t work, how to solve it?
1080 1080  
1081 -= 10. FCC Caution for RS485LN-US915 =
1023 +Please see this link for debug:
1082 1082  
1083 -(((
1084 -Any Changes or modifications not expressly approved by the party responsible for compliance could void the user's authority to operate the equipment.
1085 -)))
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]] 
1086 1086  
1087 -(((
1088 -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.
1089 -)))
1090 1090  
1091 -(((
1092 -
1093 -)))
1094 1094  
1095 -(((
1096 -**IMPORTANT NOTE:**
1097 -)))
1029 +1.
1030 +11. Why I can’t join TTN V3 in US915 /AU915 bands?
1098 1098  
1099 -(((
1100 -**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:
1101 -)))
1032 +It might about the channels mapping. Please see for detail.
1102 1102  
1103 -(((
1104 -—Reorient or relocate the receiving antenna.
1105 -)))
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]]
1106 1106  
1107 -(((
1108 -—Increase the separation between the equipment and receiver.
1109 -)))
1110 1110  
1111 -(((
1112 -—Connect the equipment into an outlet on a circuit different from that to which the receiver is connected.
1113 -)))
1114 1114  
1115 -(((
1116 -—Consult the dealer or an experienced radio/TV technician for help.
1117 -)))
1038 +1. Order Info
1118 1118  
1119 -(((
1120 -
1121 -)))
1040 +**Part Number: RS485-BL-XXX**
1122 1122  
1123 -(((
1124 -**FCC Radiation Exposure Statement:**
1125 -)))
1042 +**XXX:**
1126 1126  
1127 -(((
1128 -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.
1129 -)))
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
1130 1130  
1055 +1. Packing Info
1131 1131  
1132 -= 11. Support =
1057 +**Package Includes**:
1133 1133  
1134 -* (((
1135 -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.
1136 -)))
1137 -* (((
1138 -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]].
1139 -)))
1059 +* RS485-BL x 1
1060 +* Stick Antenna for LoRa RF part x 1
1061 +* Program cable x 1
1062 +
1063 +**Dimension and weight**:
1064 +
1065 +* Device Size: 13.5 x 7 x 3 cm
1066 +* Device Weight: 105g
1067 +* Package Size / pcs : 14.5 x 8 x 5 cm
1068 +* Weight / pcs : 170g
1069 +
1070 +1. Support
1071 +
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
1074 +
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

Applications

Navigation

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