Last modified by Xiaoling on 2025/04/23 15:56
<
From version < 31.1 >
edited by Xiaoling
on 2022/05/23 09:42
To version < 45.3 >
edited by Xiaoling
on 2022/06/02 17:05
>
Change comment: There is no comment for this version

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,175 +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]]
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 = 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= 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 = 20 20 20 2d 30
433 +DATA3=the rest of Valid value of RETURN10= **30**
504 504  
505 505  
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:
506 506  
507 -Below are the uplink payloads:
438 + ~* For AU915/AS923 bands, if UplinkDwell time=0, max 51 bytes for each uplink.
508 508  
509 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image021.png]]
440 + * For AU915/AS923 bands, if UplinkDwell time=0, max 11 bytes for each uplink.
510 510  
442 + * For US915 band, max 11 bytes for each uplink.
511 511  
512 -Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:
444 + ~* For all other bands: max 51 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)
515 515  
516 - * For AU915/AS923 bands, if UplinkDwell time=1, max 11 bytes for each uplink ( so 11 -5 = 6 max valid date).
447 +Below are the uplink payloads:
517 517  
518 - * For US915 band, max 11 bytes for each uplink ( so 11 -5 = 6 max valid date).
449 +[[image:1654157178836-407.png]]
519 519  
520 - ~* For all other bands: max 51 bytes for each uplink  ( so 51 -5 = 46 max valid date).
521 521  
452 +=== 3.3.5 Uplink on demand ===
522 522  
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.
523 523  
524 -1.
525 -11.
526 -111. Uplink on demand
527 -
528 -Except uplink periodically, RS485-BL is able to uplink on demand. The server sends downlink command to RS485-BL and RS485 will uplink data base on the command.
529 -
530 530  Downlink control command:
531 531  
532 -[[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.
533 533  
534 -[[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.
535 535  
536 536  
537 537  
538 -1.
539 -11.
540 -111. Uplink on Interrupt
464 +=== 3.3.6 Uplink on Interrupt ===
541 541  
542 -Put the interrupt sensor between 3.3v_out and GPIO ext.[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image022.png]]
466 +RS485-LN support external Interrupt uplink since hardware v1.2 release.
543 543  
544 -AT+INTMOD=0  Disable Interrupt
468 +[[image:1654157342174-798.png]]
545 545  
546 -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.
547 547  
548 -AT+INTMOD=2  Interrupt trigger by falling edge. ( Default Value)
549 549  
550 -AT+INTMOD=3  Interrupt trigger by rising edge.
473 +== 3.4 Uplink Payload ==
551 551  
552 -
553 -1.
554 -11. Uplink Payload
555 -
556 -|**Size(bytes)**|**2**|**1**|**Length depends on the return from the commands**
557 -|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" %)(((
558 558  Battery(mV)
559 559  
560 560  &
561 561  
562 562  Interrupt _Flag
563 -)))|(((
483 +)))|(% style="width:116px" %)(((
564 564  PAYLOAD_VER
565 565  
566 566  
567 -)))|If the valid payload is too long and exceed the maximum support payload length in server, server will show payload not provided in the LoRaWAN server.
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.
568 568  
569 569  Below is the decoder for the first 3 bytes. The rest bytes are dynamic depends on different RS485 sensors.
570 570  
571 571  
572 -function Decoder(bytes, port) {
492 +== 3.5 Configure RS485-BL via AT or Downlink ==
573 573  
574 -~/~/Payload Formats of RS485-BL Deceive
494 +User can configure RS485-LN via AT Commands or LoRaWAN Downlink Commands
575 575  
576 -return {
577 -
578 - ~/~/Battery,units:V
579 -
580 - BatV:((bytes[0]<<8 | bytes[1])&0x7fff)/1000,
581 -
582 - ~/~/GPIO_EXTI 
583 -
584 - EXTI_Trigger:(bytes[0] & 0x80)? "TRUE":"FALSE",
585 -
586 - ~/~/payload of version
587 -
588 - Pay_ver:bytes[2],
589 -
590 - };
591 -
592 - }
593 -
594 -
595 -
596 -
597 -
598 -
599 -
600 -TTN V3 uplink screen shot.
601 -
602 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png]]
603 -
604 -1.
605 -11. Configure RS485-BL via AT or Downlink
606 -
607 -User can configure RS485-BL via [[AT Commands >>path:#_​Using_the_AT]]or LoRaWAN Downlink Commands
608 -
609 609  There are two kinds of Commands:
610 610  
611 -* **Common Commands**: They should be available for each sensor, such as: change uplink interval, reset device. For firmware v1.3, user can find what common commands it supports: http:~/~/wiki.dragino.com/index.php?title=End_Device_AT_Commands_and_Downlink_Commands
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]]
612 612  
613 -* **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:
614 614  
615 -1.
616 -11.
617 -111. Common Commands:
502 +=== 3.5.1 Common Commands ===
618 618  
619 -They should be available for each of Dragino Sensors, such as: change uplink interval, reset device. For firmware v1.3, user can find what common commands it supports: [[http:~~/~~/wiki.dragino.com/index.php?title=End_Device_AT_Commands_and_Downlink_Commands>>url:http://wiki.dragino.com/index.php?title=End_Device_AT_Commands_and_Downlink_Commands]]
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]]
620 620  
621 621  
622 -1.
623 -11.
624 -111. Sensor related commands:
507 +=== 3.5.2 Sensor related commands ===
625 625  
626 -==== 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.
627 627  
628 -RS485-BL can connect to either RS485 sensors or TTL sensor. User need to specify what type of sensor need to connect.
511 +[[image:image-20220602163333-5.png||height="263" width="1160"]]
629 629  
630 -* 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)
631 631  
632 -**AT+MOD=1** ~/~/ Set to support RS485-MODBUS type sensors. User can connect multiply RS485 , Modbus sensors to the A / B pins.
633 633  
634 -**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 ===
635 635  
518 +==== ====
636 636  
637 -* Downlink Payload
520 +==== **RS485 Debug Command** ====
638 638  
639 -**0A aa**     à same as AT+MOD=aa
522 +This command is used to configure the RS485 devices; they won’t be used during sampling.
640 640  
524 +* **AT Command**
641 641  
526 +(% class="box infomessage" %)
527 +(((
528 +**AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m**
529 +)))
642 642  
643 -==== [[RS485 Debug Command>>path:#downlink_A8]] (AT+CFGDEV) ====
531 +m: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
644 644  
645 -This command is used to configure the RS485 or TTL sensors; they won’t be used during sampling.
533 +* **Downlink Payload**
646 646  
647 -* AT Command
648 -
649 -AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
650 -
651 -m: 0: no CRC; 1: add CRC-16/MODBUS in the end of this command.
652 -
653 -
654 -
655 -* Downlink Payload
656 -
657 657  Format: A8 MM NN XX XX XX XX YY
658 658  
659 659  Where:
... ... @@ -661,9 +661,12 @@
661 661  * MM: 1: add CRC-16/MODBUS ; 0: no CRC
662 662  * NN: The length of RS485 command
663 663  * XX XX XX XX: RS485 command total NN bytes
664 -* YY: How many bytes will be uplink from the return of this RS485 command, if YY=0, RS485-BL will execute the downlink command without uplink; if YY>0, RS485-BL will uplink total YY bytes from the output of this RS485 command
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.
665 665  
666 -**Example 1:**
547 +**Example 1** ~-~-> Configure without ask for uplink (YY=0)
667 667  
668 668  To connect a Modbus Alarm with below commands.
669 669  
... ... @@ -673,518 +673,290 @@
673 673  
674 674  So if user want to use downlink command to control to RS485 Alarm, he can use:
675 675  
676 -**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
677 677  
678 -**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
679 679  
680 680  A8 is type code and 01 means add CRC-16/MODBUS at the end, the 3^^rd^^ byte is 06, means the next 6 bytes are the command to be sent to the RS485 network, the final byte 00 means this command don’t need to acquire output.
681 681  
682 682  
683 -**Example 2:**
564 +**Example 2** ~-~-> Configure with requesting uplink and original downlink command (**YY=FF**)
684 684  
685 -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**
686 686  
687 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image024.png]]
688 688  
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:
689 689  
571 + **A8** (% style="color:#4f81bd" %)**0A 08 00 04 00  **(% style="color:red" %)**01 06** ** **(% style="color:green" %)**0A 08 00 04 00 00**
690 690  
573 + [[image:1654159460680-153.png]]
691 691  
692 -==== Set Payload version ====
693 693  
694 -This is the first byte of the uplink payload. RS485-BL can connect to different sensors. User can set the PAYVER field to tell server how to decode the current payload.
695 695  
696 -* AT Command:
577 +==== **Set Payload version** ====
697 697  
698 -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.
699 699  
581 +* **AT Command:**
700 700  
701 -* Downlink Payload:
583 +(% class="box infomessage" %)
584 +(((
585 +**AT+PAYVER: Set PAYVER field = 1**
586 +)))
702 702  
703 -0xAE 01   à Set PAYVER field =  0x01
588 +* **Downlink Payload:**
704 704  
705 -0xAE 0F   à Set PAYVER field =  0x0F
590 +**0xAE 01**  ~-~-> Set PAYVER field =  0x01
706 706  
592 +**0xAE 0F**   ~-~-> Set PAYVER field =  0x0F
707 707  
708 -==== Set RS485 Sampling Commands ====
709 709  
710 -AT+COMMANDx, AT+DATACUTx and AT+SEARCHx
711 711  
712 -These three commands are used to configure how the RS485-BL polling data from Modbus device. Detail of usage please see : [[polling RS485 device>>path:#polling_485]].
596 +==== **Set RS485 Sampling Commands** ====
713 713  
598 +AT+COMMANDx or AT+DATACUTx
714 714  
715 -* 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"]].
716 716  
717 -AT+COMMANDx: Configure RS485 read command to sensor.
718 718  
719 -AT+DATACUTx: Configure how to handle return from RS485 devices.
603 +* **AT Command:**
720 720  
721 -AT+SEARCHx: Configure search command
605 +(% class="box infomessage" %)
606 +(((
607 +**AT+COMMANDx: Configure RS485 read command to sensor.**
608 +)))
722 722  
610 +(% class="box infomessage" %)
611 +(((
612 +**AT+DATACUTx: Configure how to handle return from RS485 devices.**
613 +)))
723 723  
724 -* Downlink Payload:
725 725  
726 -0xAF downlink command can be used to set AT+COMMANDx or AT+DATACUTx.
616 +* **Downlink Payload:**
727 727  
728 -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.
729 729  
620 +(% style="color:red" %)**Note**(%%): if user use AT+COMMANDx to add a new command, he also need to send AT+DATACUTx downlink.
621 +
730 730  Format: AF MM NN LL XX XX XX XX YY
731 731  
732 732  Where:
733 733  
734 734  * MM: the ATCOMMAND or AT+DATACUT to be set. Value from 01 ~~ 0F,
735 -* NN: 0: no CRC; 1: add CRC-16/MODBUS ; 2: set the AT+DATACUT value.
736 -* LL: The length of AT+COMMAND or AT+DATACUT command
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
737 737  * XX XX XX XX: AT+COMMAND or AT+DATACUT command
738 -* YY: If YY=0, RS485-BL will execute the downlink command without uplink; if YY=1, RS485-BL will execute an uplink after got this command.
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.
739 739  
740 -Example:
632 +**Example:**
741 741  
742 -**AF 03 01 06 0A 05 00 04 00 01 00**: Same as AT+COMMAND3=0A 05 00 04 00 01,1
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
743 743  
744 -**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**
745 745  
746 -**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**
747 747  
748 748  
749 -0xAB downlink command can be used for set AT+SEARCHx
750 750  
751 -Example: **AB aa 01 03 xx xx xx** (03 here means there are total 3 bytes after 03) So
642 +==== **Fast command to handle MODBUS device** ====
752 752  
753 -* AB aa 01 03 xx xx xx  same as AT+SEARCHaa=1,xx xx xx
754 -* AB aa 02 03 xx xx xx 02 yy yy(03 means there are 3 bytes after 03, they are xx xx xx;02 means there are 2 bytes after 02, they are yy yy) so the commands
755 -
756 -**AB aa 02 03 xx xx xx 02 yy yy**  same as **AT+SEARCHaa=2,xx xx xx+yy yy**
757 -
758 -
759 -==== Fast command to handle MODBUS device ====
760 -
761 761  AT+MBFUN is valid since v1.3 firmware version. The command is for fast configure to read Modbus devices. It is only valid for the devices which follow the [[MODBUS-RTU protocol>>url:https://www.modbustools.com/modbus.html]].
762 762  
763 763  This command is valid since v1.3 firmware version
764 764  
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.
765 765  
766 -AT+MBFUN has only two value:
767 767  
768 -* AT+MBFUN=1: Enable Modbus reading. And get response base on the MODBUS return
651 +**Example:**
769 769  
770 -AT+MBFUN=1, device can auto read the Modbus function code: 01, 02, 03 or 04. AT+MBFUN has lower priority vs AT+DATACUT command. If AT+DATACUT command is configured, AT+MBFUN will be ignore.
771 -
772 -* AT+MBFUN=0: Disable Modbus fast reading.
773 -
774 -Example:
775 -
776 -* 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.
777 777  * AT+COMMAND1= 01 03 00 10 00 08,1 ~-~-> read slave address 01 , function code 03, start address 00 01, quantity of registers 00 08.
778 778  * AT+COMMAND2= 01 02 00 40 00 10,1 ~-~-> read slave address 01 , function code 02, start address 00 40, quantity of inputs 00 10.
779 779  
780 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image025.png]]
657 +[[image:image-20220602165351-6.png]]
781 781  
659 +[[image:image-20220602165351-7.png]]
782 782  
783 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image026.png]]
784 784  
785 785  
786 -* Downlink Commands:
663 +==== **RS485 command timeout** ====
787 787  
788 -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.
789 789  
667 +Default value: 0, range:  0 ~~ 65 seconds
790 790  
791 -==== RS485 command timeout ====
669 +* **AT Command:**
792 792  
793 -Some Modbus device has slow action to send replies. This command is used to configure the RS485-BL to use longer time to wait for their action.
671 +(% class="box infomessage" %)
672 +(((
673 +**AT+CMDDLaa=hex(bb cc)*1000**
674 +)))
794 794  
795 -Default value: 0, range:  0 ~~ 5 seconds
676 +**Example:**
796 796  
678 +**AT+CMDDL1=1000** to send the open time to 1000ms
797 797  
798 -* AT Command:
799 799  
800 -AT+CMDDLaa=hex(bb cc)
681 +* **Downlink Payload:**
801 801  
802 -Example:
683 +**0x AA aa bb cc**
803 803  
804 -**AT+CMDDL1=1000** to send the open time to 1000ms
685 +Same as: AT+CMDDLaa=hex(bb cc)*1000
805 805  
687 + **Example:**
806 806  
807 -* Downlink Payload:
689 + 0xAA 01 00 01  ~-~-> Same as **AT+CMDDL1=1000 ms**
808 808  
809 -0x AA aa bb cc
810 810  
811 -Same as: AT+CMDDLaa=hex(bb cc)
812 812  
813 - Example:
693 +==== **Uplink payload mode** ====
814 814  
815 - 0xAA 01 03 E8  à Same as **AT+CMDDL1=1000 ms**
695 +Define to use one uplink or multiple uplinks for the sampling.
816 816  
697 +The use of this command please see: [[Compose Uplink payload>>||anchor="H3.3.4Composetheuplinkpayload"]]
817 817  
818 -==== [[Uplink>>path:#downlink_A8]] payload mode ====
699 +* **AT Command:**
819 819  
820 -Define to use one uplink or multiple uplinks for the sampling.
701 +(% class="box infomessage" %)
702 +(((
703 +**AT+DATAUP=0**
704 +)))
821 821  
822 -The use of this command please see: [[Compose Uplink payload>>path:#DataUP]]
706 +(% class="box infomessage" %)
707 +(((
708 +**AT+DATAUP=1**
709 +)))
823 823  
824 -* AT Command:
825 825  
826 -AT+DATAUP=0
712 +* **Downlink Payload:**
827 827  
828 -AT+DATAUP=1
714 +**0xAD 00**  **~-~->** Same as AT+DATAUP=0
829 829  
716 +**0xAD 01**  **~-~->** Same as AT+DATAUP=1
830 830  
831 -* Downlink Payload:
832 832  
833 -0xAD 00   à Same as AT+DATAUP=0
834 834  
835 -0xAD 01   à Same as AT+DATAUP=1
720 +==== **Manually trigger an Uplink** ====
836 836  
722 +Ask device to send an uplink immediately.
837 837  
838 -==== Manually trigger an Uplink ====
724 +* **AT Command:**
839 839  
840 -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.
841 841  
842 -* Downlink Payload:
843 843  
844 -0x08 FF, RS485-BL will immediately send an uplink.
729 +* **Downlink Payload:**
845 845  
731 +**0x08 FF**, RS485-LN will immediately send an uplink.
846 846  
847 -==== Clear RS485 Command ====
848 848  
849 -The AT+COMMANDx and AT+DATACUTx settings are stored in special location, user can use below command to clear them.
734 +==== ====
850 850  
736 +==== **Clear RS485 Command** ====
851 851  
852 -* AT Command:
738 +The AT+COMMANDx and AT+DATACUTx settings are stored in special location, user can use below command to clear them.
853 853  
740 +* **AT Command:**
741 +
854 854  **AT+CMDEAR=mm,nn**   mm: start position of erase ,nn: stop position of erase
855 855  
856 856  Etc. AT+CMDEAR=1,10 means erase AT+COMMAND1/AT+DATACUT1 to AT+COMMAND10/AT+DATACUT10
857 857  
858 -Example screen shot after clear all RS485 commands. 
746 +Example screen shot after clear all RS485 commands.
859 859  
860 860  
861 -
862 862  The uplink screen shot is:
863 863  
864 -[[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]]
865 865  
866 866  
867 -* Downlink Payload:
754 +* **Downlink Payload:**
868 868  
869 -0x09 aa bb same as AT+CMDEAR=aa,bb
756 +**0x09 aa bb** same as AT+CMDEAR=aa,bb
870 870  
871 871  
872 -==== Set Serial Communication Parameters ====
873 873  
874 -Set the Rs485 serial communication parameters:
760 +==== **Clear RS485 Command** ====
875 875  
876 -* AT Command:
762 +The AT+COMMANDx and AT+DATACUTx settings are stored in special location, user can use below command to clear them.
877 877  
878 -Set Baud Rate:
879 879  
880 -AT+BAUDR=9600    ~/~/ Options: (1200,2400,4800,14400,19200,115200)
765 +* **AT Command:**
881 881  
767 +(% style="color:#037691" %)**AT+CMDEAR=mm,nn** (%%) mm: start position of erase ,nn: stop position of erase Etc. AT+CMDEAR=1,10 means erase AT+COMMAND1/AT+DATACUT1 to AT+COMMAND10/AT+DATACUT10
882 882  
883 -Set UART parity
769 +Example screen shot after clear all RS485 commands. 
884 884  
885 -AT+PARITY=0    ~/~/ Option: 0: no parity, 1: odd parity, 2: even parity
886 886  
772 +The uplink screen shot is:
887 887  
888 -Set STOPBIT
774 +[[image:1654134704555-320.png]]
889 889  
890 -AT+STOPBIT=0    ~/~/ Option: 0 for 1bit; 1 for 1.5 bit ; 2 for 2 bits
891 891  
777 +* **Downlink Payload:**
892 892  
893 -* Downlink Payload:
779 +**0x09 aa bb** same as AT+CMDEAR=aa,bb
894 894  
895 -A7 01 aa bb: Same  AT+BAUDR=hex(aa bb)*100
896 896  
897 -Example:
898 898  
899 -* A7 01 00 60   same as AT+BAUDR=9600
900 -* A7 01 04 80  same as AT+BAUDR=115200
783 +==== **Set Serial Communication Parameters** ====
901 901  
902 -A7 02 aa: Same as  AT+PARITY=aa  (aa value: 00 , 01 or 02)
785 +Set the Rs485 serial communication parameters:
903 903  
904 -A7 03 aa: Same as  AT+STOPBIT=aa  (aa value: 00 , 01 or 02)
787 +* **AT Command:**
905 905  
789 +Set Baud Rate:
906 906  
907 -==== Control output power duration ====
908 -
909 -User can set the output power duration before each sampling.
910 -
911 -* AT Command:
912 -
913 -Example:
914 -
915 -AT+3V3T=1000 ~/~/ 3V3 output power will open 1s before each sampling.
916 -
917 -AT+5VT=1000 ~/~/ +5V output power will open 1s before each sampling.
918 -
919 -
920 -* LoRaWAN Downlink Command:
921 -
922 -07 01 aa bb  Same as AT+5VT=(aa bb)
923 -
924 -07 02 aa bb  Same as AT+3V3T=(aa bb)
925 -
926 -
927 -
928 -
929 -1.
930 -11. Buttons
931 -
932 -|**Button**|**Feature**
933 -|**RST**|Reboot RS485-BL
934 -
935 -1.
936 -11. +3V3 Output
937 -
938 -RS485-BL has a Controllable +3V3 output, user can use this output to power external sensor.
939 -
940 -The +3V3 output will be valid for every sampling. RS485-BL will enable +3V3 output before all sampling and disable the +3V3 after all sampling. 
941 -
942 -
943 -The +3V3 output time can be controlled by AT Command.
944 -
945 -**AT+3V3T=1000**
946 -
947 -Means set +3v3 valid time to have 1000ms. So, the real +3v3 output will actually have 1000ms + sampling time for other sensors.
948 -
949 -
950 -By default, the AT+3V3T=0. This is a special case, means the +3V3 output is always on at any time
951 -
952 -
953 -1.
954 -11. +5V Output
955 -
956 -RS485-BL has a Controllable +5V output, user can use this output to power external sensor.
957 -
958 -The +5V output will be valid for every sampling. RS485-BL will enable +5V output before all sampling and disable the +5v after all sampling. 
959 -
960 -
961 -The 5V output time can be controlled by AT Command.
962 -
963 -**AT+5VT=1000**
964 -
965 -Means set 5V valid time to have 1000ms. So, the real 5V output will actually have 1000ms + sampling time for other sensors.
966 -
967 -
968 -By default, the AT+5VT=0. If the external sensor which require 5v and require more time to get stable state, user can use this command to increase the power ON duration for this sensor.
969 -
970 -
971 -
972 -
973 -1.
974 -11. LEDs
975 -
976 -|**LEDs**|**Feature**
977 -|**LED1**|Blink when device transmit a packet.
978 -
979 -1.
980 -11. Switch Jumper
981 -
982 -|**Switch Jumper**|**Feature**
983 -|**SW1**|(((
984 -ISP position: Upgrade firmware via UART
985 -
986 -Flash position: Configure device, check running status.
791 +(% class="box infomessage" %)
792 +(((
793 +**AT+BAUDR=9600**    ~/~/ Options: (1200,2400,4800,14400,19200,115200)
987 987  )))
988 -|**SW2**|(((
989 -5V position: set to compatible with 5v I/O.
990 990  
991 -3.3v position: set to compatible with 3.3v I/O.,
992 -)))
796 +Set UART Parity
993 993  
994 -+3.3V: is always ON
995 -
996 -+5V: Only open before every sampling. The time is by default, it is AT+5VT=0.  Max open time. 5000 ms.
997 -
998 -1. Case Study
999 -
1000 -User can check this URL for some case studies.
1001 -
1002 -[[http:~~/~~/wiki.dragino.com/index.php?title=APP_RS485_COMMUNICATE_WITH_SENSORS>>url:http://wiki.dragino.com/index.php?title=APP_RS485_COMMUNICATE_WITH_SENSORS]]
1003 -
1004 -
1005 -
1006 -
1007 -1. Use AT Command
1008 -11. Access AT Command
1009 -
1010 -RS485-BL supports AT Command set. User can use a USB to TTL adapter plus the 3.5mm Program Cable to connect to RS485-BL to use AT command, as below.
1011 -
1012 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image027.png]]
1013 -
1014 -
1015 -In PC, User needs to set **serial tool**(such as [[putty>>url:https://www.chiark.greenend.org.uk/~~sgtatham/putty/latest.html]], SecureCRT) baud rate to **9600** to access to access serial console of RS485-BL. The default password is 123456. Below is the output for reference:
1016 -
1017 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image028.png]]
1018 -
1019 -
1020 -
1021 -More detail AT Command manual can be found at [[AT Command Manual>>path:#AT_COMMAND]]
1022 -
1023 -
1024 -
1025 -1.
1026 -11. Common AT Command Sequence
1027 -111. Multi-channel ABP mode (Use with SX1301/LG308)
1028 -
1029 -If device has not joined network yet:
1030 -
1031 -AT+FDR
1032 -
1033 -AT+NJM=0
1034 -
1035 -ATZ
1036 -
1037 -
1038 -If device already joined network:
1039 -
1040 -AT+NJM=0
1041 -
1042 -ATZ
1043 -
1044 -1.
1045 -11.
1046 -111. Single-channel ABP mode (Use with LG01/LG02)
1047 -
1048 -AT+FDR   Reset Parameters to Factory Default, Keys Reserve
1049 -
1050 -AT+NJM=0 Set to ABP mode
1051 -
1052 -AT+ADR=0 Set the Adaptive Data Rate Off
1053 -
1054 -AT+DR=5  Set Data Rate
1055 -
1056 -AT+TDC=60000  Set transmit interval to 60 seconds
1057 -
1058 -AT+CHS=868400000 Set transmit frequency to 868.4Mhz
1059 -
1060 -AT+RX2FQ=868400000 Set RX2Frequency to 868.4Mhz (according to the result from server)
1061 -
1062 -AT+RX2DR=5  Set RX2DR to match the downlink DR from server. see below
1063 -
1064 -AT+DADDR=26 01 1A F1 Set Device Address to 26 01 1A F1, this ID can be found in the LoRa Server portal.
1065 -
1066 -ATZ          Reset MCU
1067 -
1068 -**Note:**
1069 -
1070 -1. Make sure the device is set to ABP mode in the IoT Server.
1071 -1. Make sure the LG01/02 gateway RX frequency is exactly the same as AT+CHS setting.
1072 -1. Make sure SF / bandwidth setting in LG01/LG02 match the settings of AT+DR. refer [[this link>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/&file=LoRaWAN%201.0.3%20Regional%20Parameters.xlsx]] to see what DR means.
1073 -1. The command AT+RX2FQ and AT+RX2DR is to let downlink work. to set the correct parameters, user can check the actually downlink parameters to be used. As below. Which shows the RX2FQ should use 868400000 and RX2DR should be 5
1074 -
1075 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image029.png]]
1076 -
1077 -
1078 -1. FAQ
1079 -11. How to upgrade the image?
1080 -
1081 -The RS485-BL LoRaWAN Controller is shipped with a 3.5mm cable, the cable is used to upload image to RS485-BL to:
1082 -
1083 -* Support new features
1084 -* For bug fix
1085 -* Change LoRaWAN bands.
1086 -
1087 -Below shows the hardware connection for how to upload an image to RS485-BL:
1088 -
1089 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image030.png]]
1090 -
1091 -**Step1:** Download [[flash loader>>url:https://www.st.com/content/st_com/en/products/development-tools/software-development-tools/stm32-software-development-tools/stm32-programmers/flasher-stm32.html]].
1092 -
1093 -**Step2**: Download the [[LT Image files>>url:http://www.dragino.com/downloads/index.php?dir=LT_LoRa_IO_Controller/LT33222-L/image/]].
1094 -
1095 -**Step3: **Open flashloader; choose the correct COM port to update.
1096 -
1097 -
1098 -|(((
1099 -HOLD PRO then press the RST button, SYS will be ON, then click next
798 +(% class="box infomessage" %)
799 +(((
800 +**AT+PARITY=0**    ~/~/ Option: 0: no parity, 1: odd parity, 2: even parity
1100 1100  )))
1101 1101  
1102 -|(((
1103 -Board detected
1104 -)))
803 +Set STOPBIT
1105 1105  
1106 -|(((
1107 -
805 +(% class="box infomessage" %)
806 +(((
807 +**AT+STOPBIT=0**    ~/~/ Option: 0 for 1bit; 1 for 1.5 bit ; 2 for 2 bits
1108 1108  )))
1109 1109  
1110 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image031.png]] [[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image032.png]]
1111 1111  
811 +* **Downlink Payload:**
1112 1112  
813 +**A7 01 aa bb**: Same  AT+BAUDR=hex(aa bb)*100
1113 1113  
1114 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image033.png]] [[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image034.png]]
815 +**Example:**
1115 1115  
817 +* A7 01 00 60   same as AT+BAUDR=9600
818 +* A7 01 04 80  same as AT+BAUDR=115200
1116 1116  
1117 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image035.png]] [[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image036.png]]
820 +A7 02 aa: Same as  AT+PARITY=aa  (aa value: 00 , 01 or 02)
1118 1118  
822 +A7 03 aa: Same as  AT+STOPBIT=aa  (aa value: 00 , 01 or 02)
1119 1119  
1120 -1.
1121 -11. How to change the LoRa Frequency Bands/Region?
1122 1122  
1123 -User can follow the introduction for [[how to upgrade image>>path:#upgrade_image]]. When download the images, choose the required image file for download.
1124 1124  
826 +==== **Control output power duration** ====
1125 1125  
828 +User can set the output power duration before each sampling.
1126 1126  
1127 -1.
1128 -11. How many RS485-Slave can RS485-BL connects?
830 +* **AT Command:**
1129 1129  
1130 -The RS485-BL can support max 32 RS485 devices. Each uplink command of RS485-BL can support max 16 different RS485 command. So RS485-BL can support max 16 RS485 devices pre-program in the device for uplink. For other devices no pre-program, user can use the [[downlink message (type code 0xA8) to poll their info>>path:#downlink_A8]].
832 +**Example:**
1131 1131  
834 +**AT+3V3T=1000**  ~/~/ 3V3 output power will open 1s before each sampling.
1132 1132  
836 +**AT+5VT=1000**  ~/~/ +5V output power will open 1s before each sampling.
1133 1133  
1134 1134  
1135 -1. Trouble Shooting     
1136 -11. Downlink doesn’t work, how to solve it?
839 +* **LoRaWAN Downlink Command:**
1137 1137  
1138 -Please see this link for debug:
841 +**07 01 aa bb**  Same as AT+5VT=(aa bb)
1139 1139  
1140 -[[http:~~/~~/wiki.dragino.com/index.php?title=Main_Page#LoRaWAN_Communication_Debug>>url:http://wiki.dragino.com/index.php?title=Main_Page#LoRaWAN_Communication_Debug]] 
1141 -
1142 -
1143 -
1144 -1.
1145 -11. Why I can’t join TTN V3 in US915 /AU915 bands?
1146 -
1147 -It might about the channels mapping. Please see for detail.
1148 -
1149 -[[http:~~/~~/wiki.dragino.com/index.php?title=LoRaWAN_Communication_Debug#Notice_of_US915.2FCN470.2FAU915_Frequency_band>>url:http://wiki.dragino.com/index.php?title=LoRaWAN_Communication_Debug#Notice_of_US915.2FCN470.2FAU915_Frequency_band]]
1150 -
1151 -
1152 -
1153 -1. Order Info
1154 -
1155 -**Part Number: RS485-BL-XXX**
1156 -
1157 -**XXX:**
1158 -
1159 -* **EU433**: frequency bands EU433
1160 -* **EU868**: frequency bands EU868
1161 -* **KR920**: frequency bands KR920
1162 -* **CN470**: frequency bands CN470
1163 -* **AS923**: frequency bands AS923
1164 -* **AU915**: frequency bands AU915
1165 -* **US915**: frequency bands US915
1166 -* **IN865**: frequency bands IN865
1167 -* **RU864**: frequency bands RU864
1168 -* **KZ865: **frequency bands KZ865
1169 -
1170 -1. Packing Info
1171 -
1172 -**Package Includes**:
1173 -
1174 -* RS485-BL x 1
1175 -* Stick Antenna for LoRa RF part x 1
1176 -* Program cable x 1
1177 -
1178 -**Dimension and weight**:
1179 -
1180 -* Device Size: 13.5 x 7 x 3 cm
1181 -* Device Weight: 105g
1182 -* Package Size / pcs : 14.5 x 8 x 5 cm
1183 -* Weight / pcs : 170g
1184 -
1185 -1. Support
1186 -
1187 -* Support is provided Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different timezones we cannot offer live support. However, your questions will be answered as soon as possible in the before-mentioned schedule.
1188 -* Provide as much information as possible regarding your enquiry (product models, accurately describe your problem and steps to replicate it etc) and send a mail to
1189 -
1190 -[[support@dragino.com>>url:file:///D:/市场资料/说明书/LoRa/LT系列/support@dragino.com]]
843 +**07 02 aa bb**  Same as AT+3V3T=(aa bb)
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

Applications

Navigation

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