Last modified by Xiaoling on 2025/04/23 15:56
<
From version < 31.2 >
edited by Xiaoling
on 2022/05/23 09:47
To version < 49.1 >
edited by Xiaoling
on 2022/06/02 17:32
>
Change comment: Uploaded new attachment "1654162368066-342.png", version {1}

Summary

Details

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