Last modified by Xiaoling on 2025/04/23 15:56
<
From version < 32.2 >
edited by Xiaoling
on 2022/06/02 15:22
To version < 47.3 >
edited by Xiaoling
on 2022/06/02 17:31
>
Change comment: There is no comment for this version

Summary

Details

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

Applications

Navigation

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