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