Skip to Content
Last modified by Mengting Qiu on 2025/07/14 09:59
From version 29.1
edited by Xiaoling
on 2022/05/23 09:35
Change comment: Uploaded new attachment "1653269759169-150.png", version {1}
To version 57.10
edited by Xiaoling
on 2022/06/06 08:58
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -6,12 +6,18 @@
6 6  **RS485-LN – RS485 to LoRaWAN Converter User Manual**
7 7  
8 8  
9 +
10 +
9 9  **Table of Contents:**
10 10  
13 +{{toc/}}
11 11  
12 12  
13 13  
14 14  
18 +
19 +
20 +
15 15  = 1.Introduction =
16 16  
17 17  == 1.1 What is RS485-LN RS485 to LoRaWAN Converter ==
... ... @@ -18,26 +18,30 @@
18 18  
19 19  (((
20 20  (((
21 -The Dragino RS485-LN is a RS485 to LoRaWAN Converter. It converts the RS485 signal into LoRaWAN wireless signal which simplify the IoT installation and reduce the installation/maintaining cost.
27 +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.
22 22  )))
23 23  
24 24  (((
25 -RS485-LN allows user to 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.
31 +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.
26 26  )))
27 27  
28 28  (((
29 -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.
35 +(% 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.
30 30  )))
31 31  
32 32  (((
33 -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.
39 +(% 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.
40 +
41 +(% 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]]
34 34  )))
35 35  )))
36 36  
37 37  [[image:1653267211009-519.png||height="419" width="724"]]
38 38  
47 +
39 39  == 1.2 Specifications ==
40 40  
50 +
41 41  **Hardware System:**
42 42  
43 43  * STM32L072CZT6 MCU
... ... @@ -44,8 +44,6 @@
44 44  * SX1276/78 Wireless Chip 
45 45  * Power Consumption (exclude RS485 device):
46 46  ** Idle: 32mA@12v
47 -
48 -*
49 49  ** 20dB Transmit: 65mA@12v
50 50  
51 51  **Interface for Model:**
... ... @@ -72,8 +72,10 @@
72 72  * Preamble detection.
73 73  * 127 dB Dynamic Range RSSI.
74 74  * Automatic RF Sense and CAD with ultra-fast AFC.
75 -* Packet engine up to 256 bytes with CRC.
83 +* Packet engine up to 256 bytes with CRC
76 76  
85 +
86 +
77 77  == 1.3 Features ==
78 78  
79 79  * LoRaWAN Class A & Class C protocol (default Class C)
... ... @@ -85,6 +85,8 @@
85 85  * Support Modbus protocol
86 86  * Support Interrupt uplink (Since hardware version v1.2)
87 87  
98 +
99 +
88 88  == 1.4 Applications ==
89 89  
90 90  * Smart Buildings & Home Automation
... ... @@ -94,10 +94,13 @@
94 94  * Smart Cities
95 95  * Smart Factory
96 96  
109 +
110 +
97 97  == 1.5 Firmware Change log ==
98 98  
99 99  [[RS485-LN Image files – Download link and Change log>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/]]
100 100  
115 +
101 101  == 1.6 Hardware Change log ==
102 102  
103 103  (((
... ... @@ -105,6 +105,8 @@
105 105  v1.2: Add External Interrupt Pin.
106 106  
107 107  v1.0: Release
123 +
124 +
108 108  )))
109 109  )))
110 110  
... ... @@ -121,6 +121,8 @@
121 121  )))
122 122  
123 123  [[image:1653268091319-405.png]]
141 +
142 +
124 124  )))
125 125  
126 126  = 3. Operation Mode =
... ... @@ -129,6 +129,8 @@
129 129  
130 130  (((
131 131  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.
151 +
152 +
132 132  )))
133 133  
134 134  == 3.2 Example to join LoRaWAN network ==
... ... @@ -137,15 +137,20 @@
137 137  
138 138  [[image:1653268155545-638.png||height="334" width="724"]]
139 139  
161 +
140 140  (((
163 +(((
141 141  The RS485-LN in this example connected to two RS485 devices for demonstration, user can connect to other RS485 devices via the same method. The connection is as below:
165 +)))
142 142  
167 +(((
143 143  485A+ and 485B- of the sensor are connected to RS485A and RA485B of RS485-LN respectively.
169 +)))
144 144  
145 145  [[image:1653268227651-549.png||height="592" width="720"]]
146 146  
147 147  (((
148 -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:
174 +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:
149 149  )))
150 150  
151 151  (((
... ... @@ -192,6 +192,7 @@
192 192  
193 193  [[image:1652953568895-172.png||height="232" width="724"]]
194 194  
221 +
195 195  == 3.3 Configure Commands to read data ==
196 196  
197 197  (((
... ... @@ -201,6 +201,8 @@
201 201  
202 202  (((
203 203  (% 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
231 +
232 +
204 204  )))
205 205  )))
206 206  
... ... @@ -208,19 +208,19 @@
208 208  
209 209  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:
210 210  
211 -(% border="1" style="background-color:#ffffcc; color:green; width:795px" %)
212 -|(((
240 +(% border="1" style="background-color:#ffffcc; color:green; width:782px" %)
241 +|(% style="width:128px" %)(((
213 213  **AT Commands**
214 -)))|(% style="width:285px" %)(((
243 +)))|(% style="width:305px" %)(((
215 215  **Description**
216 -)))|(% style="width:347px" %)(((
245 +)))|(% style="width:346px" %)(((
217 217  **Example**
218 218  )))
219 -|(((
248 +|(% style="width:128px" %)(((
220 220  AT+BAUDR
221 -)))|(% style="width:285px" %)(((
250 +)))|(% style="width:305px" %)(((
222 222  Set the baud rate (for RS485 connection). Default Value is: 9600.
223 -)))|(% style="width:347px" %)(((
252 +)))|(% style="width:346px" %)(((
224 224  (((
225 225  AT+BAUDR=9600
226 226  )))
... ... @@ -229,11 +229,11 @@
229 229  Options: (1200,2400,4800,14400,19200,115200)
230 230  )))
231 231  )))
232 -|(((
261 +|(% style="width:128px" %)(((
233 233  AT+PARITY
234 -)))|(% style="width:285px" %)(((
263 +)))|(% style="width:305px" %)(((
235 235  Set UART parity (for RS485 connection)
236 -)))|(% style="width:347px" %)(((
265 +)))|(% style="width:346px" %)(((
237 237  (((
238 238  AT+PARITY=0
239 239  )))
... ... @@ -242,9 +242,9 @@
242 242  Option: 0: no parity, 1: odd parity, 2: even parity
243 243  )))
244 244  )))
245 -|(((
274 +|(% style="width:128px" %)(((
246 246  AT+STOPBIT
247 -)))|(% style="width:285px" %)(((
276 +)))|(% style="width:305px" %)(((
248 248  (((
249 249  Set serial stopbit (for RS485 connection)
250 250  )))
... ... @@ -252,7 +252,7 @@
252 252  (((
253 253  
254 254  )))
255 -)))|(% style="width:347px" %)(((
284 +)))|(% style="width:346px" %)(((
256 256  (((
257 257  AT+STOPBIT=0 for 1bit
258 258  )))
... ... @@ -287,77 +287,34 @@
287 287  === 3.3.3 Configure read commands for each sampling ===
288 288  
289 289  (((
290 -RS485-BL is a battery powered device; it will sleep most of time. And wake up on each period and read RS485 / TTL sensor data and uplink.
291 -)))
319 +During each sampling, we need confirm what commands we need to send to the RS485 sensors to read data. After the RS485 sensors send back the value, it normally include some bytes and we only need a few from them for a shorten payload.
292 292  
293 -(((
294 -During each sampling, we need to confirm what commands we need to send to the sensors to read data. After the RS485/TTL sensors send back the value, it normally includes some bytes and we only need a few from them for a shorten payload.
295 -)))
296 -
297 -(((
298 298  To save the LoRaWAN network bandwidth, we might need to read data from different sensors and combine their valid value into a short payload.
299 -)))
300 300  
301 -(((
302 302  This section describes how to achieve above goals.
303 -)))
304 304  
305 -(((
306 -During each sampling, the RS485-BL can support 15 commands to read sensors. And combine the return to one or several uplink payloads.
307 -)))
325 +During each sampling, the RS485-LN can support 15 commands to read sensors. And combine the return to one or several uplink payloads.
308 308  
309 -(((
310 -**Command from RS485-BL to Sensor:**
311 -)))
312 312  
313 -(((
314 -RS485-BL can send out pre-set max 15 strings via **AT+COMMAD1**, **ATCOMMAND2**,…, to **AT+COMMANDF** . All commands are of same grammar.
315 -)))
328 +**Each RS485 commands include two parts:**
316 316  
317 -(((
318 -**Handle return from sensors to RS485-BL**:
319 -)))
330 +~1. What commands RS485-LN will send to the RS485 sensors. There are total 15 commands from **AT+COMMAD1**, **ATCOMMAND2**,…, to **AT+COMMANDF**. All commands are of same grammar.
320 320  
321 -(((
322 -After RS485-BL send out a string to sensor, RS485-BL will wait for the return from RS485 or TTL sensor. And user can specify how to handle the return, by **AT+DATACUT or AT+SEARCH commands**
323 -)))
332 +2. How to get wanted value the from RS485 sensors returns from by 1). There are total 15 AT Commands to handle the return, commands are **AT+DATACUT1**,**AT+DATACUT2**,…, **AT+DATACUTF** corresponding to the commands from 1). All commands are of same grammar.
324 324  
325 -* (((
326 -**AT+DATACUT**
327 -)))
334 +3. Some RS485 device might has longer delay on reply, so user can use AT+CMDDL to set the timeout for getting reply after the RS485 command is sent. For example **AT+CMDDL1=1000** to send the open time to 1000ms
328 328  
329 -(((
330 -When the return value from sensor have fix length and we know which position the valid value we should get, we can use AT+DATACUT command.
331 -)))
332 332  
333 -* (((
334 -**AT+SEARCH**
335 -)))
336 -
337 -(((
338 -When the return value from sensor is dynamic length and we are not sure which bytes the valid data is, instead, we know what value the valid value following. We can use AT+SEARCH to search the valid value in the return string.
339 -)))
340 -
341 -(((
342 -**Define wait timeout:**
343 -)))
344 -
345 -(((
346 -Some RS485 device might has longer delay on reply, so user can use AT+CMDDL to set the timeout for getting reply after the RS485 command is sent. For example, AT+CMDDL1=1000 to send the open time to 1000ms
347 -)))
348 -
349 -(((
350 350  After we got the valid value from each RS485 commands, we need to combine them together with the command **AT+DATAUP**.
351 -)))
352 352  
353 -**Examples:**
354 354  
355 355  Below are examples for the how above AT Commands works.
356 356  
357 -**AT+COMMANDx : **This command will be sent to RS485/TTL devices during each sampling, Max command length is 14 bytes. The grammar is:
358 358  
359 -(% border="1" class="table-bordered" %)
360 -|(((
343 +**AT+COMMANDx : **This command will be sent to RS485 devices during each sampling, Max command length is 14 bytes. The grammar is:
344 +
345 +(% border="1" style="background-color:#4bacc6; color:white; width:499px" %)
346 +|(% style="width:496px" %)(((
361 361  **AT+COMMANDx=xx xx xx xx xx xx xx xx xx xx xx xx,m**
362 362  
363 363  **xx xx xx xx xx xx xx xx xx xx xx xx: The RS485 command to be sent**
... ... @@ -367,43 +367,13 @@
367 367  
368 368  For example, if we have a RS485 sensor. The command to get sensor value is: 01 03 0B B8 00 02 46 0A. Where 01 03 0B B8 00 02 is the Modbus command to read the register 0B B8 where stored the sensor value. The 46 0A is the CRC-16/MODBUS which calculate manually.
369 369  
370 -In the RS485-BL, we should use this command AT+COMMAND1=01 03 0B B8 00 02,1 for the same.
356 +In the RS485-LN, we should use this command AT+COMMAND1=01 03 0B B8 00 02,1 for the same.
371 371  
372 -**AT+SEARCHx**: This command defines how to handle the return from AT+COMMANDx.
373 373  
374 -(% border="1" class="table-bordered" %)
375 -|(((
376 -**AT+SEARCHx=aa,xx xx xx xx xx**
377 -
378 -* **aa: 1: prefix match mode; 2: prefix and suffix match mode**
379 -* **xx xx xx xx xx: match string. Max 5 bytes for prefix and 5 bytes for suffix**
380 -
381 -
382 -)))
383 -
384 -Examples:
385 -
386 -1. For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
387 -
388 -If we set AT+SEARCH1=1,1E 56 34.      (max 5 bytes for prefix)
389 -
390 -The valid data will be all bytes after 1E 56 34 , so it is 2e 30 58 5f 36 41 30 31 00 49
391 -
392 -[[image:1652954654347-831.png]]
393 -
394 -
395 -1. For a return string from AT+COMMAND1:  16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
396 -
397 -If we set AT+SEARCH1=2, 1E 56 34+31 00 49
398 -
399 -Device will search the bytes between 1E 56 34 and 31 00 49. So it is 2e 30 58 5f 36 41 30
400 -
401 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image014.png]]
402 -
403 -
404 404  **AT+DATACUTx : **This command defines how to handle the return from AT+COMMANDx, max return length is 45 bytes.
405 405  
406 -|(((
361 +(% border="1" style="background-color:#4bacc6; color:white; width:725px" %)
362 +|(% style="width:722px" %)(((
407 407  **AT+DATACUTx=a,b,c**
408 408  
409 409  * **a: length for the return of AT+COMMAND**
... ... @@ -411,242 +411,185 @@
411 411  * **c: define the position for valid value.  **
412 412  )))
413 413  
414 -Examples:
370 +**Examples:**
415 415  
416 416  * Grab bytes:
417 417  
418 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image015.png]]
374 +[[image:image-20220602153621-1.png]]
419 419  
376 +
420 420  * Grab a section.
421 421  
422 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image016.png]]
379 +[[image:image-20220602153621-2.png]]
423 423  
381 +
424 424  * Grab different sections.
425 425  
426 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image017.png]]
384 +[[image:image-20220602153621-3.png]]
427 427  
386 +
387 +)))
428 428  
429 -Note:
389 +=== 3.3.4 Compose the uplink payload ===
430 430  
431 -AT+SEARCHx and AT+DATACUTx can be used together, if both commands are set, RS485-BL will first process AT+SEARCHx on the return string and get a temporary string, and then process AT+DATACUTx on this temporary string to get the final payload. In this case, AT+DATACUTx need to set to format AT+DATACUTx=0,xx,xx where the return bytes set to 0.
432 -
433 -Example:
434 -
435 -AT+COMMAND1=11 01 1E D0,0
436 -
437 -AT+SEARCH1=1,1E 56 34
438 -
439 -AT+DATACUT1=0,2,1~~5
440 -
441 -Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
442 -
443 -String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49
444 -
445 -Valid payload after DataCUT command: 2e 30 58 5f 36
446 -
447 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image018.png]]
448 -
449 -
450 -
451 -
452 -1.
453 -11.
454 -111. Compose the uplink payload
455 -
391 +(((
456 456  Through AT+COMMANDx and AT+DATACUTx we got valid value from each RS485 commands, Assume these valid value are RETURN1, RETURN2, .., to RETURNx. The next step is how to compose the LoRa Uplink Payload by these RETURNs. The command is **AT+DATAUP.**
457 457  
394 +
395 +)))
458 458  
459 -**Examples: AT+DATAUP=0**
397 +(((
398 +(% style="color:#037691" %)**Examples: AT+DATAUP=0**
460 460  
461 -Compose the uplink payload with value returns in sequence and send with **A SIGNLE UPLINK**.
400 +
401 +)))
462 462  
403 +(((
404 +Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**A SIGNLE UPLINK**.
405 +)))
406 +
407 +(((
463 463  Final Payload is
409 +)))
464 464  
465 -Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx
411 +(((
412 +(% style="color:#4f81bd" %)**Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx**
413 +)))
466 466  
415 +(((
467 467  Where PAYVER is defined by AT+PAYVER, below is an example screen shot.
417 +)))
468 468  
469 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image019.png]]
419 +[[image:1653269759169-150.png||height="513" width="716"]]
470 470  
471 471  
422 +(% style="color:#037691" %)**Examples: AT+DATAUP=1**
472 472  
473 -**Examples: AT+DATAUP=1**
474 474  
475 -Compose the uplink payload with value returns in sequence and send with **Multiply UPLINKs**.
425 +Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**Multiply UPLINKs**.
476 476  
477 477  Final Payload is
478 478  
479 -Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA
429 +(% style="color:#4f81bd" %)**Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA**
480 480  
481 -1. Battery Info (2 bytes): Battery voltage
482 -1. PAYVER (1 byte): Defined by AT+PAYVER
483 -1. PAYLOAD COUNT (1 byte): Total how many uplinks of this sampling.
484 -1. PAYLOAD# (1 byte): Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT)
485 -1. DATA: Valid value: max 6 bytes(US915 version here, [[Notice*!>>path:#max_byte]]) for each uplink so each uplink <= 11 bytes. For the last uplink, DATA will might less than 6 bytes
431 +1. PAYVER: Defined by AT+PAYVER
432 +1. PAYLOAD COUNT: Total how many uplinks of this sampling.
433 +1. PAYLOAD#: Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT)
434 +1. DATA: Valid value: max 8 bytes for each uplink so each uplink <= 11 bytes. For the last uplink, DATA will might less than 8 bytes
486 486  
487 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image020.png]]
436 +[[image:image-20220602155039-4.png]]
488 488  
489 489  
490 -So totally there will be 3 uplinks for this sampling, each uplink includes 6 bytes DATA
439 +So totally there will be 3 uplinks for this sampling, each uplink include 8 bytes DATA
491 491  
492 -DATA1=RETURN1 Valid Value = 20 20 0a 33 90 41
441 +DATA1=RETURN1 Valid Value + the first two of Valid value of RETURN10= **20 20 0a 33 90 41 02 aa**
493 493  
494 -DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10= 02 aa 05 81 0a 20
443 +DATA2=3^^rd^^ ~~ 10^^th^^ byte of Valid value of RETURN10= **05 81 0a 20 20 20 20 2d**
495 495  
496 -DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 = 20 20 20 2d 30
445 +DATA3=the rest of Valid value of RETURN10= **30**
497 497  
498 498  
448 +(% style="color:red" %)Notice: In firmware v1.3, the Max bytes has been changed according to the max bytes in different Frequency Bands for lowest SF. As below:
499 499  
500 -Below are the uplink payloads:
450 + ~* For AU915/AS923 bands, if UplinkDwell time=0, max 51 bytes for each uplink.
501 501  
502 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image021.png]]
452 + * For AU915/AS923 bands, if UplinkDwell time=0, max 11 bytes for each uplink.
503 503  
454 + * For US915 band, max 11 bytes for each uplink.
504 504  
505 -Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:
456 + ~* For all other bands: max 51 bytes for each uplink.
506 506  
507 - ~* For AU915/AS923 bands, if UplinkDwell time=0, max 51 bytes for each uplink ( so 51 -5 = 46 max valid date)
508 508  
509 - * For AU915/AS923 bands, if UplinkDwell time=1, max 11 bytes for each uplink ( so 11 -5 = 6 max valid date).
459 +Below are the uplink payloads:
510 510  
511 - * For US915 band, max 11 bytes for each uplink ( so 11 -5 = 6 max valid date).
461 +[[image:1654157178836-407.png]]
512 512  
513 - ~* For all other bands: max 51 bytes for each uplink  ( so 51 -5 = 46 max valid date).
514 514  
464 +=== 3.3.5 Uplink on demand ===
515 515  
466 +Except uplink periodically, RS485-LN is able to uplink on demand. The server send downlink command to RS485-LN and RS485 will uplink data base on the command.
516 516  
517 -1.
518 -11.
519 -111. Uplink on demand
520 -
521 -Except uplink periodically, RS485-BL is able to uplink on demand. The server sends downlink command to RS485-BL and RS485 will uplink data base on the command.
522 -
523 523  Downlink control command:
524 524  
525 -[[0x08 command>>path:#downlink_08]]: Poll an uplink with current command set in RS485-BL.
470 +**0x08 command**: Poll an uplink with current command set in RS485-LN.
526 526  
527 -[[0xA8 command>>path:#downlink_A8]]: Send a command to RS485-BL and uplink the output from sensors.
472 +**0xA8 command**: Send a command to RS485-LN and uplink the output from sensors.
528 528  
529 529  
530 530  
531 -1.
532 -11.
533 -111. Uplink on Interrupt
476 +=== 3.3.6 Uplink on Interrupt ===
534 534  
535 -Put the interrupt sensor between 3.3v_out and GPIO ext.[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image022.png]]
478 +RS485-LN support external Interrupt uplink since hardware v1.2 release.
536 536  
537 -AT+INTMOD=0  Disable Interrupt
480 +[[image:1654157342174-798.png]]
538 538  
539 -AT+INTMOD=1  Interrupt trigger by rising or falling edge.
482 +Connect the Interrupt pin to RS485-LN INT port and connect the GND pin to V- port. When there is a high voltage (Max 24v) on INT pin. Device will send an uplink packet.
540 540  
541 -AT+INTMOD=2  Interrupt trigger by falling edge. ( Default Value)
542 542  
543 -AT+INTMOD=3  Interrupt trigger by rising edge.
485 +== 3.4 Uplink Payload ==
544 544  
545 -
546 -1.
547 -11. Uplink Payload
548 -
549 -|**Size(bytes)**|**2**|**1**|**Length depends on the return from the commands**
550 -|Value|(((
487 +(% border="1" style="background-color:#4bacc6; color:white; width:734px" %)
488 +|**Size(bytes)**|(% style="width:120px" %)**2**|(% style="width:116px" %)**1**|(% style="width:386px" %)**Length depends on the return from the commands**
489 +|Value|(% style="width:120px" %)(((
551 551  Battery(mV)
552 552  
553 553  &
554 554  
555 555  Interrupt _Flag
556 -)))|(((
495 +)))|(% style="width:116px" %)(((
557 557  PAYLOAD_VER
558 558  
559 559  
560 -)))|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.
499 +)))|(% 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.
561 561  
562 562  Below is the decoder for the first 3 bytes. The rest bytes are dynamic depends on different RS485 sensors.
563 563  
564 564  
565 -function Decoder(bytes, port) {
504 +== 3.5 Configure RS485-BL via AT or Downlink ==
566 566  
567 -~/~/Payload Formats of RS485-BL Deceive
506 +User can configure RS485-LN via AT Commands or LoRaWAN Downlink Commands
568 568  
569 -return {
570 -
571 - ~/~/Battery,units:V
572 -
573 - BatV:((bytes[0]<<8 | bytes[1])&0x7fff)/1000,
574 -
575 - ~/~/GPIO_EXTI 
576 -
577 - EXTI_Trigger:(bytes[0] & 0x80)? "TRUE":"FALSE",
578 -
579 - ~/~/payload of version
580 -
581 - Pay_ver:bytes[2],
582 -
583 - };
584 -
585 - }
586 -
587 -
588 -
589 -
590 -
591 -
592 -
593 -TTN V3 uplink screen shot.
594 -
595 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png]]
596 -
597 -1.
598 -11. Configure RS485-BL via AT or Downlink
599 -
600 -User can configure RS485-BL via [[AT Commands >>path:#_​Using_the_AT]]or LoRaWAN Downlink Commands
601 -
602 602  There are two kinds of Commands:
603 603  
604 -* **Common Commands**: They should be available for each sensor, such as: change uplink interval, reset device. For firmware v1.3, user can find what common commands it supports: http:~/~/wiki.dragino.com/index.php?title=End_Device_AT_Commands_and_Downlink_Commands
510 +* (% 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]]
605 605  
606 -* **Sensor Related Commands**: These commands are special designed for RS485-BL.  User can see these commands below:
512 +* (% style="color:#4f81bd" %)**Sensor Related Commands**(%%): These commands are special designed for RS485-LN.  User can see these commands below:
607 607  
608 -1.
609 -11.
610 -111. Common Commands:
514 +=== 3.5.1 Common Commands ===
611 611  
612 -They should be available for each of Dragino Sensors, such as: change uplink interval, reset device. For firmware v1.3, user can find what common commands it supports: [[http:~~/~~/wiki.dragino.com/index.php?title=End_Device_AT_Commands_and_Downlink_Commands>>url:http://wiki.dragino.com/index.php?title=End_Device_AT_Commands_and_Downlink_Commands]]
516 +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]]
613 613  
614 614  
615 -1.
616 -11.
617 -111. Sensor related commands:
519 +=== 3.5.2 Sensor related commands ===
618 618  
619 -==== Choose Device Type (RS485 or TTL) ====
521 +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.
620 620  
621 -RS485-BL can connect to either RS485 sensors or TTL sensor. User need to specify what type of sensor need to connect.
523 +[[image:image-20220602163333-5.png||height="263" width="1160"]]
622 622  
623 -* AT Command
525 +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)
624 624  
625 -**AT+MOD=1** ~/~/ Set to support RS485-MODBUS type sensors. User can connect multiply RS485 , Modbus sensors to the A / B pins.
626 626  
627 -**AT+MOD=2** ~/~/ Set to support TTL Level sensors, User can connect one TTL Sensor to the TXD/RXD/GND pins.
528 +=== 3.5.3 Sensor related commands ===
628 628  
530 +(% class="wikigeneratedid" id="H" %)
531 +
629 629  
630 -* Downlink Payload
631 631  
632 -**0A aa**     à same as AT+MOD=aa
534 +==== **RS485 Debug Command** ====
633 633  
536 +This command is used to configure the RS485 devices; they won’t be used during sampling.
634 634  
538 +* **AT Command**
635 635  
636 -==== [[RS485 Debug Command>>path:#downlink_A8]] (AT+CFGDEV) ====
540 +(% class="box infomessage" %)
541 +(((
542 +**AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m**
543 +)))
637 637  
638 -This command is used to configure the RS485 or TTL sensors; they won’t be used during sampling.
545 +m: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
639 639  
640 -* AT Command
547 +* **Downlink Payload**
641 641  
642 -AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
643 -
644 -m: 0: no CRC; 1: add CRC-16/MODBUS in the end of this command.
645 -
646 -
647 -
648 -* Downlink Payload
649 -
650 650  Format: A8 MM NN XX XX XX XX YY
651 651  
652 652  Where:
... ... @@ -654,9 +654,12 @@
654 654  * MM: 1: add CRC-16/MODBUS ; 0: no CRC
655 655  * NN: The length of RS485 command
656 656  * XX XX XX XX: RS485 command total NN bytes
657 -* YY: How many bytes will be uplink from the return of this RS485 command, if YY=0, RS485-BL will execute the downlink command without uplink; if YY>0, RS485-BL will uplink total YY bytes from the output of this RS485 command
556 +* YY: How many bytes will be uplink from the return of this RS485 command,
557 +** if YY=0, RS485-LN will execute the downlink command without uplink;
558 +** if YY>0, RS485-LN will uplink total YY bytes from the output of this RS485 command; Fport=200
559 +** if YY=FF, RS485-LN will uplink RS485 output with the downlink command content; Fport=200.
658 658  
659 -**Example 1:**
561 +**Example 1** ~-~-> Configure without ask for uplink (YY=0)
660 660  
661 661  To connect a Modbus Alarm with below commands.
662 662  
... ... @@ -666,184 +666,191 @@
666 666  
667 667  So if user want to use downlink command to control to RS485 Alarm, he can use:
668 668  
669 -**A8 01 06 0A 05 00 04 00 01 00**: to activate the RS485 Alarm
571 +(% style="color:#4f81bd" %)**A8 01 06 0A 05 00 04 00 01 00**(%%): to activate the RS485 Alarm
670 670  
671 -**A8 01 06 0A 05 00 04 00 00 00**: to deactivate the RS485 Alarm
573 +(% style="color:#4f81bd" %)**A8 01 06 0A 05 00 04 00 00 00**(%%): to deactivate the RS485 Alarm
672 672  
673 673  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.
674 674  
675 675  
676 -**Example 2:**
578 +**Example 2** ~-~-> Configure with requesting uplink and original downlink command (**YY=FF**)
677 677  
678 -Check TTL Sensor return:
580 +User in IoT server send a downlink command: (% style="color:#4f81bd" %)**A8 01 06 0A 08 00 04 00 01 YY**
679 679  
680 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image024.png]]
681 681  
583 +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:
682 682  
585 + **A8** (% style="color:#4f81bd" %)**0A 08 00 04 00  **(% style="color:red" %)**01 06** ** **(% style="color:green" %)**0A 08 00 04 00 00**
683 683  
587 + [[image:1654159460680-153.png]]
684 684  
685 -==== Set Payload version ====
686 686  
687 -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.
688 688  
689 -* AT Command:
591 +==== **Set Payload version** ====
690 690  
691 -AT+PAYVER: Set PAYVER field = 1
593 +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.
692 692  
595 +* **AT Command:**
693 693  
694 -* Downlink Payload:
597 +(% class="box infomessage" %)
598 +(((
599 +**AT+PAYVER: Set PAYVER field = 1**
600 +)))
695 695  
696 -0xAE 01   à Set PAYVER field =  0x01
602 +* **Downlink Payload:**
697 697  
698 -0xAE 0F   à Set PAYVER field =  0x0F
604 +**0xAE 01**  ~-~-> Set PAYVER field =  0x01
699 699  
606 +**0xAE 0F**   ~-~-> Set PAYVER field =  0x0F
700 700  
701 -==== Set RS485 Sampling Commands ====
702 702  
703 -AT+COMMANDx, AT+DATACUTx and AT+SEARCHx
704 704  
705 -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]].
610 +==== **Set RS485 Sampling Commands** ====
706 706  
612 +AT+COMMANDx or AT+DATACUTx
707 707  
708 -* AT Command:
614 +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"]].
709 709  
710 -AT+COMMANDx: Configure RS485 read command to sensor.
711 711  
712 -AT+DATACUTx: Configure how to handle return from RS485 devices.
617 +* **AT Command:**
713 713  
714 -AT+SEARCHx: Configure search command
619 +(% class="box infomessage" %)
620 +(((
621 +**AT+COMMANDx: Configure RS485 read command to sensor.**
622 +)))
715 715  
624 +(% class="box infomessage" %)
625 +(((
626 +**AT+DATACUTx: Configure how to handle return from RS485 devices.**
627 +)))
716 716  
717 -* Downlink Payload:
718 718  
719 -0xAF downlink command can be used to set AT+COMMANDx or AT+DATACUTx.
630 +* **Downlink Payload:**
720 720  
721 -Note: if user use AT+COMMANDx to add a new command, he also need to send AT+DATACUTx downlink.
632 +**0xAF** downlink command can be used to set AT+COMMANDx or AT+DATACUTx.
722 722  
634 +(% style="color:red" %)**Note**(%%): if user use AT+COMMANDx to add a new command, he also need to send AT+DATACUTx downlink.
635 +
723 723  Format: AF MM NN LL XX XX XX XX YY
724 724  
725 725  Where:
726 726  
727 727  * MM: the ATCOMMAND or AT+DATACUT to be set. Value from 01 ~~ 0F,
728 -* NN: 0: no CRC; 1: add CRC-16/MODBUS ; 2: set the AT+DATACUT value.
729 -* LL: The length of AT+COMMAND or AT+DATACUT command
641 +* NN:  0: no CRC; 1: add CRC-16/MODBUS ; 2: set the AT+DATACUT value.
642 +* LL:  The length of AT+COMMAND or AT+DATACUT command
730 730  * XX XX XX XX: AT+COMMAND or AT+DATACUT command
731 -* 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.
644 +* 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.
732 732  
733 -Example:
646 +**Example:**
734 734  
735 -**AF 03 01 06 0A 05 00 04 00 01 00**: Same as AT+COMMAND3=0A 05 00 04 00 01,1
648 +(% 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
736 736  
737 -**AF 03 02 06 10 01 05 06 09 0A 00**: Same as AT+DATACUT3=**16**,**1**,**5+6+9+10**
650 +(% 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**
738 738  
739 -**AF 03 02 06 0B 02 05 07 08 0A 00**: Same as AT+DATACUT3=**11**,**2**,**5~~7+8~~10**
652 +(% 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**
740 740  
741 741  
742 -0xAB downlink command can be used for set AT+SEARCHx
743 743  
744 -Example: **AB aa 01 03 xx xx xx** (03 here means there are total 3 bytes after 03) So
656 +==== **Fast command to handle MODBUS device** ====
745 745  
746 -* AB aa 01 03 xx xx xx  same as AT+SEARCHaa=1,xx xx xx
747 -* 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
748 -
749 -**AB aa 02 03 xx xx xx 02 yy yy**  same as **AT+SEARCHaa=2,xx xx xx+yy yy**
750 -
751 -
752 -==== Fast command to handle MODBUS device ====
753 -
754 754  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]].
755 755  
756 756  This command is valid since v1.3 firmware version
757 757  
662 +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.
758 758  
759 -AT+MBFUN has only two value:
760 760  
761 -* AT+MBFUN=1: Enable Modbus reading. And get response base on the MODBUS return
665 +**Example:**
762 762  
763 -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.
764 -
765 -* AT+MBFUN=0: Disable Modbus fast reading.
766 -
767 -Example:
768 -
769 -* AT+MBFUN=1 and AT+DATACUT1/AT+DATACUT2 are not configure (0,0,0).
667 +* AT+MBFUN=1 and AT+DATACUT1/AT+DATACUT2 are not configure (0,0,0). So RS485-LN.
770 770  * 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.
771 771  * 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.
772 772  
773 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image025.png]]
671 +[[image:image-20220602165351-6.png]]
774 774  
673 +[[image:image-20220602165351-7.png]]
775 775  
776 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image026.png]]
777 777  
778 778  
779 -* Downlink Commands:
677 +==== **RS485 command timeout** ====
780 780  
781 -A9 aa -à Same as AT+MBFUN=aa
679 +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.
782 782  
681 +Default value: 0, range:  0 ~~ 65 seconds
783 783  
784 -==== RS485 command timeout ====
683 +* **AT Command:**
785 785  
786 -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.
685 +(% class="box infomessage" %)
686 +(((
687 +**AT+CMDDLaa=hex(bb cc)*1000**
688 +)))
787 787  
788 -Default value: 0, range:  0 ~~ 5 seconds
690 +**Example:**
789 789  
692 +**AT+CMDDL1=1000** to send the open time to 1000ms
790 790  
791 -* AT Command:
792 792  
793 -AT+CMDDLaa=hex(bb cc)
695 +* **Downlink Payload:**
794 794  
795 -Example:
697 +**0x AA aa bb cc**
796 796  
797 -**AT+CMDDL1=1000** to send the open time to 1000ms
699 +Same as: AT+CMDDLaa=hex(bb cc)*1000
798 798  
701 + **Example:**
799 799  
800 -* Downlink Payload:
703 + 0xAA 01 00 01  ~-~-> Same as **AT+CMDDL1=1000 ms**
801 801  
802 -0x AA aa bb cc
803 803  
804 -Same as: AT+CMDDLaa=hex(bb cc)
805 805  
806 - Example:
707 +==== **Uplink payload mode** ====
807 807  
808 - 0xAA 01 03 E8  à Same as **AT+CMDDL1=1000 ms**
709 +Define to use one uplink or multiple uplinks for the sampling.
809 809  
711 +The use of this command please see: [[Compose Uplink payload>>||anchor="H3.3.4Composetheuplinkpayload"]]
810 810  
811 -==== [[Uplink>>path:#downlink_A8]] payload mode ====
713 +* **AT Command:**
812 812  
813 -Define to use one uplink or multiple uplinks for the sampling.
715 +(% class="box infomessage" %)
716 +(((
717 +**AT+DATAUP=0**
718 +)))
814 814  
815 -The use of this command please see: [[Compose Uplink payload>>path:#DataUP]]
720 +(% class="box infomessage" %)
721 +(((
722 +**AT+DATAUP=1**
723 +)))
816 816  
817 -* AT Command:
818 818  
819 -AT+DATAUP=0
726 +* **Downlink Payload:**
820 820  
821 -AT+DATAUP=1
728 +**0xAD 00**  **~-~->** Same as AT+DATAUP=0
822 822  
730 +**0xAD 01**  **~-~->** Same as AT+DATAUP=1
823 823  
824 -* Downlink Payload:
825 825  
826 -0xAD 00   à Same as AT+DATAUP=0
827 827  
828 -0xAD 01   à Same as AT+DATAUP=1
734 +==== **Manually trigger an Uplink** ====
829 829  
736 +Ask device to send an uplink immediately.
830 830  
831 -==== Manually trigger an Uplink ====
738 +* **AT Command:**
832 832  
833 -Ask device to send an uplink immediately.
740 +No AT Command for this, user can press the [[ACT button>>path:#Button]] for 1 second for the same.
834 834  
835 -* Downlink Payload:
836 836  
837 -0x08 FF, RS485-BL will immediately send an uplink.
743 +* **Downlink Payload:**
838 838  
745 +**0x08 FF**, RS485-LN will immediately send an uplink.
839 839  
840 -==== Clear RS485 Command ====
841 841  
842 -The AT+COMMANDx and AT+DATACUTx settings are stored in special location, user can use below command to clear them.
748 +==== ====
843 843  
750 +==== **Clear RS485 Command** ====
844 844  
845 -* AT Command:
752 +The AT+COMMANDx and AT+DATACUTx settings are stored in special location, user can use below command to clear them.
846 846  
754 +* **AT Command:**
755 +
847 847  **AT+CMDEAR=mm,nn**   mm: start position of erase ,nn: stop position of erase
848 848  
849 849  Etc. AT+CMDEAR=1,10 means erase AT+COMMAND1/AT+DATACUT1 to AT+COMMAND10/AT+DATACUT10
... ... @@ -851,43 +851,50 @@
851 851  Example screen shot after clear all RS485 commands. 
852 852  
853 853  
854 -
855 855  The uplink screen shot is:
856 856  
857 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png]]
765 +[[image:1654160691922-496.png]][[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image001.png]]
858 858  
859 859  
860 -* Downlink Payload:
768 +* **Downlink Payload:**
861 861  
862 -0x09 aa bb same as AT+CMDEAR=aa,bb
770 +**0x09 aa bb** same as AT+CMDEAR=aa,bb
863 863  
864 864  
865 -==== Set Serial Communication Parameters ====
866 866  
774 +==== **Set Serial Communication Parameters** ====
775 +
867 867  Set the Rs485 serial communication parameters:
868 868  
869 -* AT Command:
778 +* **AT Command:**
870 870  
871 871  Set Baud Rate:
872 872  
873 -AT+BAUDR=9600    ~/~/ Options: (1200,2400,4800,14400,19200,115200)
782 +(% class="box infomessage" %)
783 +(((
784 +**AT+BAUDR=9600**    ~/~/ Options: (1200,2400,4800,14400,19200,115200)
785 +)))
874 874  
787 +Set UART Parity
875 875  
876 -Set UART parity
789 +(% class="box infomessage" %)
790 +(((
791 +**AT+PARITY=0**    ~/~/ Option: 0: no parity, 1: odd parity, 2: even parity
792 +)))
877 877  
878 -AT+PARITY=0    ~/~/ Option: 0: no parity, 1: odd parity, 2: even parity
879 -
880 -
881 881  Set STOPBIT
882 882  
883 -AT+STOPBIT=0    ~/~/ Option: 0 for 1bit; 1 for 1.5 bit ; 2 for 2 bits
796 +(% class="box infomessage" %)
797 +(((
798 +**AT+STOPBIT=0**    ~/~/ Option: 0 for 1bit; 1 for 1.5 bit ; 2 for 2 bits
799 +)))
884 884  
885 885  
886 -* Downlink Payload:
802 +* **Downlink Payload:**
887 887  
888 -A7 01 aa bb: Same  AT+BAUDR=hex(aa bb)*100
804 +**A7 01 aa bb**: Same  AT+BAUDR=hex(aa bb)*100
889 889  
890 -Example:
806 +**Example:**
891 891  
892 892  * A7 01 00 60   same as AT+BAUDR=9600
893 893  * A7 01 04 80  same as AT+BAUDR=115200
... ... @@ -897,287 +897,287 @@
897 897  A7 03 aa: Same as  AT+STOPBIT=aa  (aa value: 00 , 01 or 02)
898 898  
899 899  
900 -==== Control output power duration ====
816 +== 3.6 Listening mode for RS485 network ==
901 901  
902 -User can set the output power duration before each sampling.
818 +This feature support since firmware v1.4
903 903  
904 -* AT Command:
820 +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.
905 905  
906 -Example:
822 +[[image:image-20220602171200-8.png||height="567" width="1007"]]
907 907  
908 -AT+3V3T=1000 ~/~/ 3V3 output power will open 1s before each sampling.
824 +To enable the listening mode, use can run the command AT+RXMODE.
909 909  
910 -AT+5VT=1000 ~/~/ +5V output power will open 1s before each sampling.
911 911  
827 +(% border="1" style="background-color:#ffffcc; width:500px" %)
828 +|=(% style="width: 161px;" %)**Command example:**|=(% style="width: 337px;" %)**Function**
829 +|(% 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.
830 +|(% 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
831 +|(% style="width:161px" %)AT+RXMODE=0,0|(% style="width:337px" %)Disable listening mode. This is the default settings.
832 +|(% style="width:161px" %) |(% style="width:337px" %)A6 aa bb cc  same as AT+RXMODE=aa,(bb<<8 ~| cc)
912 912  
913 -* LoRaWAN Downlink Command:
834 +**Downlink Command:**
914 914  
915 -07 01 aa bb  Same as AT+5VT=(aa bb)
836 +**0xA6 aa bb cc ** same as AT+RXMODE=aa,(bb<<8 | cc)
916 916  
917 -07 02 aa bb  Same as AT+3V3T=(aa bb)
918 918  
839 +**Example**:
919 919  
841 +The RS485-LN is set to AT+RXMODE=2,1000
920 920  
843 +There is a two Modbus commands in the RS485 network as below:
921 921  
922 -1.
923 -11. Buttons
845 +The Modbus master send a command: (% style="background-color:#ffc000" %)01 03 00 00 00 02 c4 0b
924 924  
925 -|**Button**|**Feature**
926 -|**RST**|Reboot RS485-BL
847 +And Modbus slave reply with: (% style="background-color:green" %)01 03 04 00 00 00 00 fa 33
927 927  
928 -1.
929 -11. +3V3 Output
849 +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
930 930  
931 -RS485-BL has a Controllable +3V3 output, user can use this output to power external sensor.
851 +[[image:image-20220602171200-9.png]]
932 932  
933 -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. 
934 934  
854 +(% 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.
935 935  
936 -The +3V3 output time can be controlled by AT Command.
937 937  
938 -**AT+3V3T=1000**
857 +== 3.7 Buttons ==
939 939  
940 -Means set +3v3 valid time to have 1000ms. So, the real +3v3 output will actually have 1000ms + sampling time for other sensors.
941 941  
860 +(% border="1" style="background-color:#f7faff; width:500px" %)
861 +|=**Button**|=(% style="width: 1420px;" %)**Feature**
862 +|**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**
863 +|**RST**|(% style="width:1420px" %)Reboot RS485
864 +|**PRO**|(% style="width:1420px" %)Use for upload image, see [[How to Update Image>>path:#upgrade_image]]
942 942  
943 -By default, the AT+3V3T=0. This is a special case, means the +3V3 output is always on at any time
944 944  
945 945  
946 -1.
947 -11. +5V Output
868 +== 3.8 LEDs ==
948 948  
949 -RS485-BL has a Controllable +5V output, user can use this output to power external sensor.
870 +(% border="1" style="background-color:#f7faff; width:500px" %)
871 +|=**LEDs**|=**Feature**
872 +|**PWR**|Always on if there is power
873 +|**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.
950 950  
951 -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. 
952 952  
953 953  
954 -The 5V output time can be controlled by AT Command.
877 += 4. Case Study =
955 955  
956 -**AT+5VT=1000**
879 +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]]
957 957  
958 -Means set 5V valid time to have 1000ms. So, the real 5V output will actually have 1000ms + sampling time for other sensors.
959 959  
882 += 5. Use AT Command =
960 960  
961 -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.
884 +== 5.1 Access AT Command ==
962 962  
886 +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.
963 963  
888 +[[image:1654162355560-817.png]]
964 964  
965 965  
966 -1.
967 -11. LEDs
891 +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:
968 968  
969 -|**LEDs**|**Feature**
970 -|**LED1**|Blink when device transmit a packet.
893 +[[image:1654162368066-342.png]]
971 971  
972 -1.
973 -11. Switch Jumper
974 974  
975 -|**Switch Jumper**|**Feature**
976 -|**SW1**|(((
977 -ISP position: Upgrade firmware via UART
896 +More detail AT Command manual can be found at [[AT Command Manual>>||anchor="3.5ConfigureRS485-BLviaATorDownlink"]]
978 978  
979 -Flash position: Configure device, check running status.
980 -)))
981 -|**SW2**|(((
982 -5V position: set to compatible with 5v I/O.
983 983  
984 -3.3v position: set to compatible with 3.3v I/O.,
985 -)))
899 +== 5.2 Common AT Command Sequence ==
986 986  
987 -+3.3V: is always ON
901 +=== 5.2.1 Multi-channel ABP mode (Use with SX1301/LG308) ===
988 988  
989 -+5V: Only open before every sampling. The time is by default, it is AT+5VT=0.  Max open time. 5000 ms.
903 +If device has not joined network yet:
990 990  
991 -1. Case Study
905 +(% class="box infomessage" %)
906 +(((
907 +**AT+FDR**
908 +)))
992 992  
993 -User can check this URL for some case studies.
910 +(% class="box infomessage" %)
911 +(((
912 +**AT+NJM=0**
913 +)))
994 994  
995 -[[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]]
915 +(% class="box infomessage" %)
916 +(((
917 +**ATZ**
918 +)))
996 996  
997 997  
921 +If device already joined network:
998 998  
923 +(% class="box infomessage" %)
924 +(((
925 +**AT+NJM=0**
926 +)))
999 999  
1000 -1. Use AT Command
1001 -11. Access AT Command
928 +(% class="box infomessage" %)
929 +(((
930 +**ATZ**
931 +)))
1002 1002  
1003 -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.
1004 1004  
1005 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image027.png]]
934 +=== 5.5.2 Single-channel ABP mode (Use with LG01/LG02) ===
1006 1006  
1007 1007  
1008 -In PC, User needs to set **serial tool**(such as [[putty>>url:https://www.chiark.greenend.org.uk/~~sgtatham/putty/latest.html]], SecureCRT) baud rate to **9600** to access to access serial console of RS485-BL. The default password is 123456. Below is the output for reference:
937 +(% style="background-color:#dcdcdc" %)**AT+FDR** (%%) Reset Parameters to Factory Default, Keys Reserve
1009 1009  
1010 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image028.png]]
939 +(% style="background-color:#dcdcdc" %)**AT+NJM=0 **(%%)Set to ABP mode
1011 1011  
941 +(% style="background-color:#dcdcdc" %)**AT+ADR=0** (%%)Set the Adaptive Data Rate Off
1012 1012  
943 +(% style="background-color:#dcdcdc" %)**AT+DR=5**   (%%)Set Data Rate
1013 1013  
1014 -More detail AT Command manual can be found at [[AT Command Manual>>path:#AT_COMMAND]]
945 +(% style="background-color:#dcdcdc" %)**AT+TDC=60000** (%%) Set transmit interval to 60 seconds
1015 1015  
947 +(% style="background-color:#dcdcdc" %)**AT+CHS=868400000**(%%) Set transmit frequency to 868.4Mhz
1016 1016  
949 +(% style="background-color:#dcdcdc" %)**AT+RX2FQ=868400000** (%%) Set RX2Frequency to 868.4Mhz (according to the result from server)
1017 1017  
1018 -1.
1019 -11. Common AT Command Sequence
1020 -111. Multi-channel ABP mode (Use with SX1301/LG308)
951 +(% style="background-color:#dcdcdc" %)**AT+RX2DR=5**  (%%) Set RX2DR to match the downlink DR from server. see below
1021 1021  
1022 -If device has not joined network yet:
953 +(% 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.
1023 1023  
1024 -AT+FDR
955 +(% style="background-color:#dcdcdc" %)**ATZ**       (%%) Reset MCU
1025 1025  
1026 -AT+NJM=0
1027 1027  
1028 -ATZ
958 +(% style="color:red" %)**Note:**
1029 1029  
960 +(% style="color:red" %)1. Make sure the device is set to ABP mode in the IoT Server.
961 +2. Make sure the LG01/02 gateway RX frequency is exactly the same as AT+CHS setting.
962 +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.
963 +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
1030 1030  
1031 -If device already joined network:
965 +[[image:1654162478620-421.png]]
1032 1032  
1033 -AT+NJM=0
1034 1034  
1035 -ATZ
968 += 6. FAQ =
1036 1036  
1037 -1.
1038 -11.
1039 -111. Single-channel ABP mode (Use with LG01/LG02)
970 +== 6.1 How to upgrade the image? ==
1040 1040  
1041 -AT+FDR   Reset Parameters to Factory Default, Keys Reserve
972 +The RS485-LN LoRaWAN Controller is shipped with a 3.5mm cable, the cable is used to upload image to RS485-LN to:
1042 1042  
1043 -AT+NJM=0 Set to ABP mode
974 +* Support new features
975 +* For bug fix
976 +* Change LoRaWAN bands.
1044 1044  
1045 -AT+ADR=0 Set the Adaptive Data Rate Off
978 +Below shows the hardware connection for how to upload an image to RS485-LN:
1046 1046  
1047 -AT+DR=5  Set Data Rate
980 +[[image:1654162535040-878.png]]
1048 1048  
1049 -AT+TDC=60000  Set transmit interval to 60 seconds
982 +**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]].
1050 1050  
1051 -AT+CHS=868400000 Set transmit frequency to 868.4Mhz
984 +**Step2**: Download the [[LT Image files>>url:http://www.dragino.com/downloads/index.php?dir=LT_LoRa_IO_Controller/LT33222-L/image/]].
1052 1052  
1053 -AT+RX2FQ=868400000 Set RX2Frequency to 868.4Mhz (according to the result from server)
986 +**Step3: **Open flashloader; choose the correct COM port to update.
1054 1054  
1055 -AT+RX2DR=5  Set RX2DR to match the downlink DR from server. see below
988 +(% 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.
1056 1056  
1057 -AT+DADDR=26 01 1A F1 Set Device Address to 26 01 1A F1, this ID can be found in the LoRa Server portal.
1058 1058  
1059 -ATZ          Reset MCU
991 +[[image:image-20220602175818-12.png]]
1060 1060  
1061 -**Note:**
1062 1062  
1063 -1. Make sure the device is set to ABP mode in the IoT Server.
1064 -1. Make sure the LG01/02 gateway RX frequency is exactly the same as AT+CHS setting.
1065 -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.
1066 -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
994 +[[image:image-20220602175848-13.png]]
1067 1067  
1068 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image029.png]]
1069 1069  
997 +[[image:image-20220602175912-14.png]]
1070 1070  
1071 -1. FAQ
1072 -11. How to upgrade the image?
1073 1073  
1074 -The RS485-BL LoRaWAN Controller is shipped with a 3.5mm cable, the cable is used to upload image to RS485-BL to:
1000 +**Notice**: In case user has lost the program cable. User can hand made one from a 3.5mm cable. The pin mapping is:
1075 1075  
1076 -* Support new features
1077 -* For bug fix
1078 -* Change LoRaWAN bands.
1002 +[[image:image-20220602175638-10.png]]
1079 1079  
1080 -Below shows the hardware connection for how to upload an image to RS485-BL:
1081 1081  
1082 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image030.png]]
1005 +== 6.2 How to change the LoRa Frequency Bands/Region? ==
1083 1083  
1084 -**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]].
1007 +User can follow the introduction for [[how to upgrade image>>||anchor="H6.1Howtoupgradetheimage3F"]]. When download the images, choose the required image file for download.
1085 1085  
1086 -**Step2**: Download the [[LT Image files>>url:http://www.dragino.com/downloads/index.php?dir=LT_LoRa_IO_Controller/LT33222-L/image/]].
1087 1087  
1088 -**Step3: **Open flashloader; choose the correct COM port to update.
1010 +== 6.3 How many RS485-Slave can RS485-BL connects? ==
1089 1089  
1012 +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"]].
1090 1090  
1091 -|(((
1092 -HOLD PRO then press the RST button, SYS will be ON, then click next
1093 -)))
1094 1094  
1095 -|(((
1096 -Board detected
1097 -)))
1015 +== 6.4 Compatible question to ChirpStack and TTI LoRaWAN server ? ==
1098 1098  
1099 -|(((
1100 -
1101 -)))
1017 +When user need to use with ChirpStack or TTI. Please set AT+RPL=4.
1102 1102  
1103 -[[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]]
1019 +Detail info check this link: [[Set Packet Receiving Response Level>>doc:Main.End Device AT Commands and Downlink Command.WebHome||anchor="H7.23SetPacketReceivingResponseLevel"]]
1104 1104  
1105 1105  
1022 += 7. Trouble Shooting =
1106 1106  
1107 -[[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]]
1024 +== 7.1 Downlink doesn’t work, how to solve it? ==
1108 1108  
1026 +Please see this link for debug: [[LoRaWAN Communication Debug>>doc:Main.LoRaWAN Communication Debug.WebHome]]
1109 1109  
1110 -[[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]]
1111 1111  
1029 +== 7.2 Why I can’t join TTN V3 in US915 /AU915 bands? ==
1112 1112  
1113 -1.
1114 -11. How to change the LoRa Frequency Bands/Region?
1031 +It might about the channels mapping. Please see for detail: [[Notice of Frequency band>>doc:Main.LoRaWAN Communication Debug.WebHome||anchor="H2.NoticeofUS9152FCN4702FAU915Frequencyband"]]
1115 1115  
1116 -User can follow the introduction for [[how to upgrade image>>path:#upgrade_image]]. When download the images, choose the required image file for download.
1117 1117  
1034 += 8. Order Info =
1118 1118  
1036 +(% style="color:blue" %)**Part Number: RS485-LN-XXX**
1119 1119  
1120 -1.
1121 -11. How many RS485-Slave can RS485-BL connects?
1038 +(% style="color:blue" %)**XXX:**
1122 1122  
1123 -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]].
1040 +* (% style="color:blue" %)**EU433**(%%): frequency bands EU433
1041 +* (% style="color:blue" %)**EU868**(%%): frequency bands EU868
1042 +* (% style="color:blue" %)**KR920**(%%): frequency bands KR920
1043 +* (% style="color:blue" %)**CN470**(%%): frequency bands CN470
1044 +* (% style="color:blue" %)**AS923**(%%): frequency bands AS923
1045 +* (% style="color:blue" %)**AU915**(%%): frequency bands AU915
1046 +* (% style="color:blue" %)**US915**(%%): frequency bands US915
1047 +* (% style="color:blue" %)**IN865**(%%): frequency bands IN865
1048 +* (% style="color:blue" %)**RU864**(%%): frequency bands RU864
1049 +* (% style="color:blue" %)**KZ865**(%%): frequency bands KZ865
1124 1124  
1125 1125  
1126 1126  
1053 += 9.Packing Info =
1127 1127  
1128 -1. Trouble Shooting     
1129 -11. Downlink doesn’t work, how to solve it?
1130 1130  
1131 -Please see this link for debug:
1056 +**Package Includes**:
1132 1132  
1133 -[[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]] 
1058 +* RS485-LN x 1
1059 +* Stick Antenna for LoRa RF part x 1
1060 +* Program cable x 1
1134 1134  
1062 +**Dimension and weight**:
1135 1135  
1064 +* Device Size: 13.5 x 7 x 3 cm
1065 +* Device Weight: 105g
1066 +* Package Size / pcs : 14.5 x 8 x 5 cm
1067 +* Weight / pcs : 170g
1136 1136  
1137 -1.
1138 -11. Why I can’t join TTN V3 in US915 /AU915 bands?
1139 1139  
1140 -It might about the channels mapping. Please see for detail.
1141 1141  
1142 -[[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]]
1071 += 10. FCC Caution for RS485LN-US915 =
1143 1143  
1073 +Any Changes or modifications not expressly approved by the party responsible for compliance could void the user's authority to operate the equipment.
1144 1144  
1075 +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.
1145 1145  
1146 -1. Order Info
1147 1147  
1148 -**Part Number: RS485-BL-XXX**
1078 +**IMPORTANT NOTE:**
1149 1149  
1150 -**XXX:**
1080 +**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:
1151 1151  
1152 -* **EU433**: frequency bands EU433
1153 -* **EU868**: frequency bands EU868
1154 -* **KR920**: frequency bands KR920
1155 -* **CN470**: frequency bands CN470
1156 -* **AS923**: frequency bands AS923
1157 -* **AU915**: frequency bands AU915
1158 -* **US915**: frequency bands US915
1159 -* **IN865**: frequency bands IN865
1160 -* **RU864**: frequency bands RU864
1161 -* **KZ865: **frequency bands KZ865
1082 +—Reorient or relocate the receiving antenna.
1162 1162  
1163 -1. Packing Info
1084 +—Increase the separation between the equipment and receiver.
1164 1164  
1165 -**Package Includes**:
1086 +—Connect the equipment into an outlet on a circuit different from that to which the receiver is connected.
1166 1166  
1167 -* RS485-BL x 1
1168 -* Stick Antenna for LoRa RF part x 1
1169 -* Program cable x 1
1088 +—Consult the dealer or an experienced radio/TV technician for help.
1170 1170  
1171 -**Dimension and weight**:
1172 1172  
1173 -* Device Size: 13.5 x 7 x 3 cm
1174 -* Device Weight: 105g
1175 -* Package Size / pcs : 14.5 x 8 x 5 cm
1176 -* Weight / pcs : 170g
1091 +**FCC Radiation Exposure Statement:**
1177 1177  
1178 -1. Support
1093 +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.
1179 1179  
1180 -* 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.
1181 -* 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
1182 1182  
1183 -[[support@dragino.com>>url:file:///D:/市场资料/说明书/LoRa/LT系列/support@dragino.com]]
1096 += 11. Support =
1097 +
1098 +* 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.
1099 +* 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]].
1653269916228-732.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +143.3 KB
Content
1653270130359-810.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +197.8 KB
Content
1654157178836-407.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +179.9 KB
Content
1654157342174-798.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +31.9 KB
Content
1654158783574-851.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +40.6 KB
Content
1654159460680-153.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +24.9 KB
Content
1654160691922-496.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +109.3 KB
Content
1654162355560-817.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +670.0 KB
Content
1654162368066-342.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +192.9 KB
Content
1654162478620-421.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +158.9 KB
Content
1654162535040-878.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +670.0 KB
Content
image-20220602153621-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +23.4 KB
Content
image-20220602153621-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +22.2 KB
Content
image-20220602153621-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +22.3 KB
Content
image-20220602155039-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +24.6 KB
Content
image-20220602163333-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +48.2 KB
Content
image-20220602165351-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +10.6 KB
Content
image-20220602165351-7.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +19.3 KB
Content
image-20220602171200-8.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +276.1 KB
Content
image-20220602171200-9.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +10.0 KB
Content
image-20220602175638-10.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +85.5 KB
Content
image-20220602175743-11.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +85.5 KB
Content
image-20220602175818-12.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +102.5 KB
Content
image-20220602175848-13.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +250.9 KB
Content
image-20220602175912-14.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +176.1 KB
Content