Last modified by Xiaoling on 2025/04/23 15:57

From version 40.23
edited by Xiaoling
on 2022/06/06 09:46
Change comment: There is no comment for this version
To version 41.35
edited by Xiaoling
on 2022/06/06 11:19
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -94,8 +94,6 @@
94 94  * 127 dB Dynamic Range RSSI.
95 95  * Automatic RF Sense and CAD with ultra-fast AFC. ​​​
96 96  
97 -
98 -
99 99  == 1.3 Features ==
100 100  
101 101  * LoRaWAN Class A & Class C protocol (default Class A)
... ... @@ -107,8 +107,6 @@
107 107  * Support Modbus protocol
108 108  * Support Interrupt uplink
109 109  
110 -
111 -
112 112  == 1.4 Applications ==
113 113  
114 114  * Smart Buildings & Home Automation
... ... @@ -118,8 +118,6 @@
118 118  * Smart Cities
119 119  * Smart Factory
120 120  
121 -
122 -
123 123  == 1.5 Firmware Change log ==
124 124  
125 125  [[RS485-BL Image files – Download link and Change log>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/RS485-BL/Firmware/||style="background-color: rgb(255, 255, 255);"]]
... ... @@ -130,29 +130,47 @@
130 130  (((
131 131  
132 132  
127 +(((
133 133  v1.4
134 134  )))
130 +)))
135 135  
136 136  (((
133 +(((
137 137  ~1. Change Power IC to TPS22916
138 138  )))
136 +)))
139 139  
138 +(((
139 +
140 +)))
140 140  
141 141  (((
143 +(((
142 142  v1.3
143 143  )))
146 +)))
144 144  
145 145  (((
149 +(((
146 146  ~1. Change JP3 from KF350-8P to KF350-11P, Add one extra interface for I2C and one extra interface for one-wire
147 147  )))
152 +)))
148 148  
154 +(((
155 +
156 +)))
149 149  
150 150  (((
159 +(((
151 151  v1.2
152 152  )))
162 +)))
153 153  
154 154  (((
165 +(((
155 155  Release version ​​​​​
167 +)))
156 156  
157 157  
158 158  )))
... ... @@ -246,81 +246,129 @@
246 246  
247 247  === 3.3.1 onfigure UART settings for RS485 or TTL communication ===
248 248  
261 +(((
249 249  RS485-BL can connect to either RS485 sensors or TTL sensor. User need to specify what type of sensor need to connect.
263 +)))
250 250  
265 +(((
251 251  **~1. RS485-MODBUS mode:**
267 +)))
252 252  
269 +(((
253 253  AT+MOD=1 ~/~/ Support RS485-MODBUS type sensors. User can connect multiply RS485 , Modbus sensors to the A / B pins.
271 +)))
254 254  
273 +(((
255 255  **2. TTL mode:**
275 +)))
256 256  
277 +(((
257 257  AT+MOD=2 ~/~/ Support TTL Level sensors, User can connect one TTL Sensor to the TXD/RXD/GND pins.
279 +)))
258 258  
281 +(((
259 259  RS485-BL default UART settings is **9600, no parity, stop bit 1**. If the sensor has a different settings, user can change the RS485-BL setting to match.
283 +)))
260 260  
261 -(% border="1" style="background-color:#ffffcc; color:green; width:795px" %)
262 -|(((
285 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)
286 +|=(% style="width: 120px;" %)(((
287 +(((
263 263  **AT Commands**
264 -)))|(% style="width:285px" %)(((
289 +)))
290 +)))|=(% style="width: 190px;" %)(((
291 +(((
265 265  **Description**
266 -)))|(% style="width:347px" %)(((
293 +)))
294 +)))|=(% style="width: 190px;" %)(((
295 +(((
267 267  **Example**
268 268  )))
269 -|(((
298 +)))
299 +|(% style="width:120px" %)(((
300 +(((
270 270  AT+BAUDR
271 -)))|(% style="width:285px" %)(((
302 +)))
303 +)))|(% style="width:190px" %)(((
304 +(((
272 272  Set the baud rate (for RS485 connection). Default Value is: 9600.
273 -)))|(% style="width:347px" %)(((
306 +)))
307 +)))|(% style="width:190px" %)(((
274 274  (((
309 +(((
275 275  AT+BAUDR=9600
276 276  )))
312 +)))
277 277  
278 278  (((
315 +(((
279 279  Options: (1200,2400,4800,14400,19200,115200)
280 280  )))
281 281  )))
282 -|(((
319 +)))
320 +|(% style="width:120px" %)(((
321 +(((
283 283  AT+PARITY
284 -)))|(% style="width:285px" %)(((
323 +)))
324 +)))|(% style="width:190px" %)(((
285 285  (((
326 +(((
286 286  Set UART parity (for RS485 connection)
287 287  )))
329 +)))
288 288  
289 289  (((
332 +(((
290 290  Default Value is: no parity.
291 291  )))
292 -)))|(% style="width:347px" %)(((
335 +)))
336 +)))|(% style="width:190px" %)(((
293 293  (((
338 +(((
294 294  AT+PARITY=0
295 295  )))
341 +)))
296 296  
297 297  (((
344 +(((
298 298  Option: 0: no parity, 1: odd parity, 2: even parity
299 299  )))
300 300  )))
301 -|(((
348 +)))
349 +|(% style="width:120px" %)(((
350 +(((
302 302  AT+STOPBIT
303 -)))|(% style="width:285px" %)(((
352 +)))
353 +)))|(% style="width:190px" %)(((
304 304  (((
355 +(((
305 305  Set serial stopbit (for RS485 connection)
306 306  )))
358 +)))
307 307  
308 308  (((
361 +(((
309 309  Default Value is: 1bit.
310 310  )))
311 -)))|(% style="width:347px" %)(((
364 +)))
365 +)))|(% style="width:190px" %)(((
312 312  (((
367 +(((
313 313  AT+STOPBIT=0 for 1bit
314 314  )))
370 +)))
315 315  
316 316  (((
373 +(((
317 317  AT+STOPBIT=1 for 1.5 bit
318 318  )))
376 +)))
319 319  
320 320  (((
379 +(((
321 321  AT+STOPBIT=2 for 2 bits
322 322  )))
323 323  )))
383 +)))
324 324  
325 325  
326 326  
... ... @@ -334,19 +334,20 @@
334 334  When user issue an (% style="color:#4f81bd" %)**AT+CFGDEV**(%%) command, Each (% style="color:#4f81bd" %)**AT+CFGDEV**(%%) equals to send a command to the RS485 or TTL sensors. This command will only run when user input it and won’t run during each sampling.
335 335  )))
336 336  
337 -(% border="1" style="background-color:#ffffcc; color:green; width:806px" %)
338 -|**AT Commands**|(% style="width:418px" %)**Description**|(% style="width:256px" %)**Example**
339 -|AT+CFGDEV|(% style="width:418px" %)(((
397 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)
398 +|=(% style="width: 120px;" %)**AT Commands**|=(% style="width: 190px;" %)**Description**|=(% style="width: 190px;" %)**Example**
399 +|AT+CFGDEV|(% style="width:120px" %)(((
340 340  This command is used to configure the RS485/TTL devices; they won’t be used during sampling.
341 341  
342 342  AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,
343 343  
344 344  mm: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
345 -)))|(% style="width:256px" %)AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
405 +)))|(% style="width:190px" %)AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
346 346  
347 347  Detail of AT+CFGDEV command see [[AT+CFGDEV detail>>||anchor="HRS485DebugCommand28AT2BCFGDEV29"]].
348 348  
349 349  
410 +
350 350  === 3.3.3 Configure read commands for each sampling ===
351 351  
352 352  (((
... ... @@ -413,117 +413,213 @@
413 413  After we got the valid value from each RS485 commands, we need to combine them together with the command **AT+DATAUP**.
414 414  )))
415 415  
477 +(((
416 416  **Examples:**
479 +)))
417 417  
481 +(((
418 418  Below are examples for the how above AT Commands works.
483 +)))
419 419  
485 +(((
420 420  **AT+COMMANDx : **This command will be sent to RS485/TTL devices during each sampling, Max command length is 14 bytes. The grammar is:
487 +)))
421 421  
422 -(% border="1" class="table-bordered" style="background-color:#4f81bd; color:white; width:501px" %)
489 +(% border="1" class="table-bordered" style="background-color:#4f81bd; color:white; width:500px" %)
423 423  |(% style="width:498px" %)(((
491 +(((
424 424  **AT+COMMANDx=xx xx xx xx xx xx xx xx xx xx xx xx,m**
493 +)))
425 425  
495 +(((
426 426  **xx xx xx xx xx xx xx xx xx xx xx xx: The RS485 command to be sent**
497 +)))
427 427  
499 +(((
428 428  **m: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command**
429 429  )))
502 +)))
430 430  
504 +(((
431 431  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.
506 +)))
432 432  
508 +(((
433 433  In the RS485-BL, we should use this command AT+COMMAND1=01 03 0B B8 00 02,1 for the same.
510 +)))
434 434  
512 +(((
513 +
514 +)))
515 +
516 +(((
435 435  **AT+SEARCHx**: This command defines how to handle the return from AT+COMMANDx.
518 +)))
436 436  
437 -(% border="1" class="table-bordered" style="background-color:#4f81bd; color:white; width:580px" %)
520 +(% border="1" class="table-bordered" style="background-color:#4f81bd; color:white; width:500px" %)
438 438  |(% style="width:577px" %)(((
522 +(((
439 439  **AT+SEARCHx=aa,xx xx xx xx xx**
524 +)))
440 440  
441 -* **aa: 1: prefix match mode; 2: prefix and suffix match mode**
442 -* **xx xx xx xx xx: match string. Max 5 bytes for prefix and 5 bytes for suffix**
526 +* (((
527 +**aa: 1: prefix match mode; 2: prefix and suffix match mode**
443 443  )))
529 +* (((
530 +**xx xx xx xx xx: match string. Max 5 bytes for prefix and 5 bytes for suffix**
531 +)))
532 +)))
444 444  
534 +(((
445 445  **Examples:**
536 +)))
446 446  
538 +(((
447 447  1)For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
540 +)))
448 448  
542 +(((
449 449  If we set AT+SEARCH1=1,1E 56 34.      (max 5 bytes for prefix)
544 +)))
450 450  
546 +(((
451 451  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**
548 +)))
452 452  
550 +(((
453 453  [[image:1653271044481-711.png]]
552 +)))
454 454  
554 +(((
455 455  2)For a return string from AT+COMMAND1:  16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
556 +)))
456 456  
558 +(((
457 457  If we set AT+SEARCH1=2, 1E 56 34+31 00 49
560 +)))
458 458  
562 +(((
459 459  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**
564 +)))
460 460  
566 +(((
461 461  [[image:1653271276735-972.png]]
568 +)))
462 462  
570 +(((
463 463  **AT+DATACUTx : **This command defines how to handle the return from AT+COMMANDx, max return length is 45 bytes.
572 +)))
464 464  
465 -(% style="background-color:#4f81bd; color:white; width:729px" %)
574 +(% style="background-color:#4f81bd; color:white; width:510px" %)
466 466  |(% style="width:726px" %)(((
576 +(((
467 467  **AT+DATACUTx=a,b,c**
578 +)))
468 468  
469 -* **a: length for the return of AT+COMMAND**
470 -* **b:1: grab valid value by byte, max 6 bytes. 2: grab valid value by bytes section, max 3 sections.**
471 -* **c: define the position for valid value.  **
580 +* (((
581 +**a: length for the return of AT+COMMAND**
472 472  )))
583 +* (((
584 +**b:1: grab valid value by byte, max 6 bytes. 2: grab valid value by bytes section, max 3 sections.**
585 +)))
586 +* (((
587 +**c: define the position for valid value.  **
588 +)))
589 +)))
473 473  
591 +(((
474 474  **Examples:**
593 +)))
475 475  
476 -* Grab bytes:
595 +* (((
596 +Grab bytes:
597 +)))
477 477  
599 +(((
478 478  [[image:1653271581490-837.png||height="313" width="722"]]
601 +)))
479 479  
603 +(((
604 +
605 +)))
480 480  
481 -* Grab a section.
607 +* (((
608 +Grab a section.
609 +)))
482 482  
611 +(((
483 483  [[image:1653271648378-342.png||height="326" width="720"]]
613 +)))
484 484  
615 +(((
616 +
617 +)))
485 485  
486 -* Grab different sections.
619 +* (((
620 +Grab different sections.
621 +)))
487 487  
623 +(((
488 488  [[image:1653271657255-576.png||height="305" width="730"]]
625 +)))
489 489  
490 490  (((
628 +(((
491 491  (% style="color:red" %)**Note:**
492 492  )))
631 +)))
493 493  
494 494  (((
634 +(((
495 495  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.
496 496  )))
637 +)))
497 497  
498 498  (((
640 +(((
499 499  **Example:**
500 500  )))
643 +)))
501 501  
502 502  (((
646 +(((
503 503  (% style="color:red" %)AT+COMMAND1=11 01 1E D0,0
504 504  )))
649 +)))
505 505  
506 506  (((
652 +(((
507 507  (% style="color:red" %)AT+SEARCH1=1,1E 56 34
508 508  )))
655 +)))
509 509  
510 510  (((
658 +(((
511 511  (% style="color:red" %)AT+DATACUT1=0,2,1~~5
512 512  )))
661 +)))
513 513  
514 514  (((
664 +(((
515 515  (% style="color:red" %)Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
516 516  )))
667 +)))
517 517  
518 518  (((
670 +(((
519 519  (% style="color:red" %)String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49
520 520  )))
673 +)))
521 521  
522 522  (((
676 +(((
523 523  (% style="color:red" %)Valid payload after DataCUT command: 2e 30 58 5f 36
524 524  )))
679 +)))
525 525  
681 +(((
526 526  [[image:1653271763403-806.png]]
683 +)))
527 527  
528 528  
529 529  === 3.3.4 Compose the uplink payload ===
... ... @@ -530,10 +530,14 @@
530 530  
531 531  (((
532 532  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.**
690 +
691 +
533 533  )))
534 534  
535 535  (((
536 536  (% style="color:#037691" %)**Examples: AT+DATAUP=0**
696 +
697 +
537 537  )))
538 538  
539 539  (((
... ... @@ -666,26 +666,8 @@
666 666  
667 667  == 3.4 Uplink Payload ==
668 668  
669 -(% border="1" style="background-color:#4f81bd; color:white; width:850px" %)
670 -|**Size(bytes)**|(% style="width:130px" %)**2**|(% style="width:93px" %)**1**|(% style="width:509px" %)**Length depends on the return from the commands**
671 -|Value|(% style="width:130px" %)(((
672 -(((
673 -Battery(mV)
674 -)))
830 +[[image:image-20220606105412-1.png]]
675 675  
676 -(((
677 -&
678 -)))
679 -
680 -(((
681 -Interrupt _Flag
682 -)))
683 -)))|(% style="width:93px" %)(((
684 -PAYLOAD_VER
685 -
686 -
687 -)))|(% style="width:509px" %)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.
688 -
689 689  Below is the decoder for the first 3 bytes. The rest bytes are dynamic depends on different RS485 sensors.
690 690  
691 691  (((
... ... @@ -729,7 +729,7 @@
729 729  )))
730 730  
731 731  (((
732 -**}**
875 +{{{}}}}
733 733  
734 734  
735 735  )))
... ... @@ -743,13 +743,21 @@
743 743  
744 744  == 3.5 Configure RS485-BL via AT or Downlink ==
745 745  
889 +(((
746 746  User can configure RS485-BL via AT Commands or LoRaWAN Downlink Commands
891 +)))
747 747  
893 +(((
748 748  There are two kinds of Commands:
895 +)))
749 749  
750 -* (% style="color:#4f81bd" %)**Common Commands**(%%): They should be available for each sensor, such as: change uplink interval, reset device. For firmware v1.3, user can find what common commands it supports: [[AT Commands and Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]]
897 +* (((
898 +(% style="color:#4f81bd" %)**Common Commands**(%%): They should be available for each sensor, such as: change uplink interval, reset device. For firmware v1.3, user can find what common commands it supports: [[AT Commands and Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]]
899 +)))
751 751  
752 -* (% style="color:#4f81bd" %)**Sensor Related Commands**(%%): These commands are special designed for RS485-BL.  User can see these commands below:
901 +* (((
902 +(% style="color:#4f81bd" %)**Sensor Related Commands**(%%): These commands are special designed for RS485-BL.  User can see these commands below:
903 +)))
753 753  
754 754  
755 755  
... ... @@ -761,6 +761,7 @@
761 761  === 3.5.2 Sensor related commands: ===
762 762  
763 763  
915 +
764 764  ==== **Choose Device Type (RS485 or TTL)** ====
765 765  
766 766  RS485-BL can connect to either RS485 sensors or TTL sensor. User need to specify what type of sensor need to connect.
... ... @@ -784,57 +784,109 @@
784 784  
785 785  
786 786  
939 +
787 787  ==== **RS485 Debug Command (AT+CFGDEV)** ====
788 788  
942 +(((
789 789  This command is used to configure the RS485 or TTL sensors; they won’t be used during sampling.
944 +)))
790 790  
791 -* **AT Command**
946 +* (((
947 +**AT Command**
948 +)))
792 792  
793 793  (% class="box infomessage" %)
794 794  (((
952 +(((
795 795  **AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m**
796 796  )))
955 +)))
797 797  
957 +(((
798 798  m: 0: no CRC; 1: add CRC-16/MODBUS in the end of this command.
959 +)))
799 799  
961 +(((
962 +
963 +)))
800 800  
801 -* **Downlink Payload**
965 +* (((
966 +**Downlink Payload**
967 +)))
802 802  
969 +(((
803 803  Format: A8 MM NN XX XX XX XX YY
971 +)))
804 804  
973 +(((
805 805  Where:
975 +)))
806 806  
807 -* MM: 1: add CRC-16/MODBUS ; 0: no CRC
808 -* NN: The length of RS485 command
809 -* XX XX XX XX: RS485 command total NN bytes
810 -* 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
977 +* (((
978 +MM: 1: add CRC-16/MODBUS ; 0: no CRC
979 +)))
980 +* (((
981 +NN: The length of RS485 command
982 +)))
983 +* (((
984 +XX XX XX XX: RS485 command total NN bytes
985 +)))
986 +* (((
987 +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
988 +)))
811 811  
990 +(((
812 812  **Example 1:**
992 +)))
813 813  
994 +(((
814 814  To connect a Modbus Alarm with below commands.
996 +)))
815 815  
816 -* The command to active alarm is: 0A 05 00 04 00 01 **4C B0**. Where 0A 05 00 04 00 01 is the Modbus command to read the register 00 40 where stored the DI status. The 4C B0 is the CRC-16/MODBUS which calculate manually.
998 +* (((
999 +The command to active alarm is: 0A 05 00 04 00 01 **4C B0**. Where 0A 05 00 04 00 01 is the Modbus command to read the register 00 40 where stored the DI status. The 4C B0 is the CRC-16/MODBUS which calculate manually.
1000 +)))
817 817  
818 -* The command to deactivate alarm is: 0A 05 00 04 00 00 **8D 70**. Where 0A 05 00 04 00 00 is the Modbus command to read the register 00 40 where stored the DI status. The 8D 70 is the CRC-16/MODBUS which calculate manually.
1002 +* (((
1003 +The command to deactivate alarm is: 0A 05 00 04 00 00 **8D 70**. Where 0A 05 00 04 00 00 is the Modbus command to read the register 00 40 where stored the DI status. The 8D 70 is the CRC-16/MODBUS which calculate manually.
1004 +)))
819 819  
1006 +(((
820 820  So if user want to use downlink command to control to RS485 Alarm, he can use:
1008 +)))
821 821  
1010 +(((
822 822  (% style="color:#037691" %)**A8 01 06 0A 05 00 04 00 01 00**(%%): to activate the RS485 Alarm
1012 +)))
823 823  
1014 +(((
824 824  (% style="color:#037691" %)**A8 01 06 0A 05 00 04 00 00 00**(%%): to deactivate the RS485 Alarm
1016 +)))
825 825  
1018 +(((
826 826  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.
1020 +)))
827 827  
1022 +(((
1023 +
1024 +)))
828 828  
1026 +(((
829 829  **Example 2:**
1028 +)))
830 830  
1030 +(((
831 831  Check TTL Sensor return:
1032 +)))
832 832  
1034 +(((
833 833  [[image:1654132684752-193.png]]
1036 +)))
834 834  
835 835  
836 836  
837 837  
1041 +
838 838  ==== **Set Payload version** ====
839 839  
840 840  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.
... ... @@ -855,87 +855,171 @@
855 855  
856 856  
857 857  
1062 +
858 858  ==== **Set RS485 Sampling Commands** ====
859 859  
1065 +(((
860 860  AT+COMMANDx, AT+DATACUTx and AT+SEARCHx
1067 +)))
861 861  
1069 +(((
862 862  These three commands are used to configure how the RS485-BL polling data from Modbus device. Detail of usage please see : [[polling RS485 device>>||anchor="H3.3.3Configurereadcommandsforeachsampling"]].
1071 +)))
863 863  
1073 +(((
1074 +
1075 +)))
864 864  
865 -* **AT Command:**
1077 +* (((
1078 +**AT Command:**
1079 +)))
866 866  
867 867  (% class="box infomessage" %)
868 868  (((
1083 +(((
869 869  **AT+COMMANDx: Configure RS485 read command to sensor.**
870 870  )))
1086 +)))
871 871  
872 872  (% class="box infomessage" %)
873 873  (((
1090 +(((
874 874  **AT+DATACUTx: Configure how to handle return from RS485 devices.**
875 875  )))
1093 +)))
876 876  
877 877  (% class="box infomessage" %)
878 878  (((
1097 +(((
879 879  **AT+SEARCHx: Configure search command**
880 880  )))
1100 +)))
881 881  
1102 +(((
1103 +
1104 +)))
882 882  
883 -* **Downlink Payload:**
1106 +* (((
1107 +**Downlink Payload:**
1108 +)))
884 884  
1110 +(((
885 885  **0xAF** downlink command can be used to set AT+COMMANDx or AT+DATACUTx.
1112 +)))
886 886  
1114 +(((
887 887  (% style="color:red" %)**Note**(%%): if user use AT+COMMANDx to add a new command, he also need to send AT+DATACUTx downlink.
1116 +)))
888 888  
1118 +(((
889 889  Format: AF MM NN LL XX XX XX XX YY
1120 +)))
890 890  
1122 +(((
891 891  Where:
1124 +)))
892 892  
893 -* MM: the ATCOMMAND or AT+DATACUT to be set. Value from 01 ~~ 0F,
894 -* NN:  0: no CRC; 1: add CRC-16/MODBUS ; 2: set the AT+DATACUT value.
895 -* LL:  The length of AT+COMMAND or AT+DATACUT command
896 -* XX XX XX XX: AT+COMMAND or AT+DATACUT command
897 -* 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.
1126 +* (((
1127 +MM: the ATCOMMAND or AT+DATACUT to be set. Value from 01 ~~ 0F,
1128 +)))
1129 +* (((
1130 +NN:  0: no CRC; 1: add CRC-16/MODBUS ; 2: set the AT+DATACUT value.
1131 +)))
1132 +* (((
1133 +LL:  The length of AT+COMMAND or AT+DATACUT command
1134 +)))
1135 +* (((
1136 +XX XX XX XX: AT+COMMAND or AT+DATACUT command
1137 +)))
1138 +* (((
1139 +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.
1140 +)))
898 898  
1142 +(((
899 899  **Example:**
1144 +)))
900 900  
1146 +(((
901 901  (% 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
1148 +)))
902 902  
1150 +(((
903 903  (% 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**
1152 +)))
904 904  
1154 +(((
905 905  (% 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**
1156 +)))
906 906  
1158 +(((
1159 +
1160 +)))
907 907  
1162 +(((
908 908  **0xAB** downlink command can be used for set AT+SEARCHx
1164 +)))
909 909  
1166 +(((
910 910  **Example:** **AB aa 01 03 xx xx xx** (03 here means there are total 3 bytes after 03) So
1168 +)))
911 911  
912 -* AB aa 01 03 xx xx xx  same as AT+SEARCHaa=1,xx xx xx
913 -* 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
1170 +* (((
1171 +AB aa 01 03 xx xx xx  same as AT+SEARCHaa=1,xx xx xx
1172 +)))
1173 +* (((
1174 +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
1175 +)))
914 914  
1177 +(((
915 915  **AB aa 02 03 xx xx xx 02 yy yy**  same as **AT+SEARCHaa=2,xx xx xx+yy yy**
1179 +)))
916 916  
917 917  
918 918  
1183 +
919 919  ==== **Fast command to handle MODBUS device** ====
920 920  
1186 +(((
921 921  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]].
1188 +)))
922 922  
1190 +(((
923 923  This command is valid since v1.3 firmware version
1192 +)))
924 924  
1194 +(((
1195 +
1196 +)))
925 925  
1198 +(((
926 926  **AT+MBFUN has only two value:**
1200 +)))
927 927  
928 -* **AT+MBFUN=1**: Enable Modbus reading. And get response base on the MODBUS return
1202 +* (((
1203 +**AT+MBFUN=1**: Enable Modbus reading. And get response base on the MODBUS return
1204 +)))
929 929  
1206 +(((
930 930  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.
1208 +)))
931 931  
932 -* **AT+MBFUN=0**: Disable Modbus fast reading.
1210 +* (((
1211 +**AT+MBFUN=0**: Disable Modbus fast reading.
1212 +)))
933 933  
1214 +(((
934 934  **Example:**
1216 +)))
935 935  
936 -* AT+MBFUN=1 and AT+DATACUT1/AT+DATACUT2 are not configure (0,0,0).
937 -* 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.
938 -* 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.
1218 +* (((
1219 +AT+MBFUN=1 and AT+DATACUT1/AT+DATACUT2 are not configure (0,0,0).
1220 +)))
1221 +* (((
1222 +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.
1223 +)))
1224 +* (((
1225 +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.
1226 +)))
939 939  
940 940  [[image:1654133913295-597.png]]
941 941  
... ... @@ -949,6 +949,7 @@
949 949  
950 950  
951 951  
1240 +
952 952  ==== **RS485 command timeout** ====
953 953  
954 954  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.
... ... @@ -980,6 +980,7 @@
980 980  
981 981  
982 982  
1272 +
983 983  ==== **Uplink payload mode** ====
984 984  
985 985  Define to use one uplink or multiple uplinks for the sampling.
... ... @@ -1026,7 +1026,9 @@
1026 1026  
1027 1027  * **AT Command:**
1028 1028  
1319 +(((
1029 1029  (% 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
1321 +)))
1030 1030  
1031 1031  Example screen shot after clear all RS485 commands. 
1032 1032  
... ... @@ -1042,6 +1042,7 @@
1042 1042  
1043 1043  
1044 1044  
1337 +
1045 1045  ==== **Set Serial Communication Parameters** ====
1046 1046  
1047 1047  Set the Rs485 serial communication parameters:
... ... @@ -1085,6 +1085,7 @@
1085 1085  
1086 1086  
1087 1087  
1381 +
1088 1088  ==== **Control output power duration** ====
1089 1089  
1090 1090  User can set the output power duration before each sampling.
... ... @@ -1108,7 +1108,7 @@
1108 1108  
1109 1109  == 3.6 Buttons ==
1110 1110  
1111 -(% border="1" style="background-color:#ffffcc; color:green; width:233px" %)
1405 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:233px" %)
1112 1112  |=(% style="width: 89px;" %)**Button**|=(% style="width: 141px;" %)**Feature**
1113 1113  |(% style="width:89px" %)**RST**|(% style="width:141px" %)Reboot RS485-BL
1114 1114  
... ... @@ -1116,39 +1116,75 @@
1116 1116  
1117 1117  == 3.7 +3V3 Output ==
1118 1118  
1413 +(((
1119 1119  RS485-BL has a Controllable +3V3 output, user can use this output to power external sensor.
1415 +)))
1120 1120  
1417 +(((
1121 1121  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. 
1419 +)))
1122 1122  
1421 +(((
1123 1123  The +3V3 output time can be controlled by AT Command.
1423 +)))
1124 1124  
1425 +(((
1426 +
1427 +)))
1125 1125  
1429 +(((
1126 1126  (% style="color:#037691" %)**AT+3V3T=1000**
1431 +)))
1127 1127  
1433 +(((
1434 +
1435 +)))
1128 1128  
1437 +(((
1129 1129  Means set +3v3 valid time to have 1000ms. So, the real +3v3 output will actually have 1000ms + sampling time for other sensors.
1439 +)))
1130 1130  
1441 +(((
1131 1131  By default, the AT+3V3T=0. This is a special case, means the +3V3 output is always on at any time
1443 +)))
1132 1132  
1133 1133  
1134 -
1135 1135  == 3.8 +5V Output ==
1136 1136  
1448 +(((
1137 1137  RS485-BL has a Controllable +5V output, user can use this output to power external sensor.
1450 +)))
1138 1138  
1452 +(((
1139 1139  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. 
1454 +)))
1140 1140  
1456 +(((
1141 1141  The 5V output time can be controlled by AT Command.
1458 +)))
1142 1142  
1460 +(((
1461 +
1462 +)))
1143 1143  
1464 +(((
1144 1144  (% style="color:#037691" %)**AT+5VT=1000**
1466 +)))
1145 1145  
1468 +(((
1469 +
1470 +)))
1146 1146  
1472 +(((
1147 1147  Means set 5V valid time to have 1000ms. So, the real 5V output will actually have 1000ms + sampling time for other sensors.
1474 +)))
1148 1148  
1476 +(((
1149 1149  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.
1478 +)))
1150 1150  
1151 1151  
1481 +
1152 1152  == 3.9 LEDs ==
1153 1153  
1154 1154  (% border="1" style="background-color:#ffffcc; color:green; width:332px" %)
... ... @@ -1172,9 +1172,13 @@
1172 1172  3.3v position: set to compatible with 3.3v I/O.,
1173 1173  )))
1174 1174  
1505 +(((
1175 1175  **+3.3V**: is always ON
1507 +)))
1176 1176  
1509 +(((
1177 1177  **+5V**: Only open before every sampling. The time is by default, it is AT+5VT=0.  Max open time. 5000 ms.
1511 +)))
1178 1178  
1179 1179  
1180 1180  = 4. Case Study =
... ... @@ -1186,17 +1186,23 @@
1186 1186  
1187 1187  == 5.1 Access AT Command ==
1188 1188  
1523 +(((
1189 1189  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.
1525 +)))
1190 1190  
1191 1191  [[image:1654135840598-282.png]]
1192 1192  
1193 1193  
1530 +(((
1194 1194  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:
1532 +)))
1195 1195  
1196 1196  [[image:1654136105500-922.png]]
1197 1197  
1198 1198  
1199 -More detail AT Command manual can be found at [[AT Command Manual>>||anchor="3.5ConfigureRS485-BLviaATorDownlink"]]
1537 +(((
1538 +More detail AT Command manual can be found at [[AT Command Manual>>||anchor="H3.5ConfigureRS485-BLviaATorDownlink"]]
1539 +)))
1200 1200  
1201 1201  
1202 1202  == 5.2 Common AT Command Sequence ==
... ... @@ -1221,7 +1221,9 @@
1221 1221  )))
1222 1222  
1223 1223  
1564 +(((
1224 1224  If device already joined network:
1566 +)))
1225 1225  
1226 1226  (% class="box infomessage" %)
1227 1227  (((
... ... @@ -1260,10 +1260,12 @@
1260 1260  
1261 1261  (% style="color:red" %)**Note:**
1262 1262  
1605 +(((
1263 1263  (% style="color:red" %)1. Make sure the device is set to ABP mode in the IoT Server.
1264 1264  2. Make sure the LG01/02 gateway RX frequency is exactly the same as AT+CHS setting.
1265 1265  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.
1266 1266  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
1610 +)))
1267 1267  
1268 1268  [[image:1654136435598-589.png]]
1269 1269  
... ... @@ -1272,13 +1272,23 @@
1272 1272  
1273 1273  == 6.1 How to upgrade the image? ==
1274 1274  
1619 +(((
1275 1275  The RS485-BL LoRaWAN Controller is shipped with a 3.5mm cable, the cable is used to upload image to RS485-BL to:
1621 +)))
1276 1276  
1277 -* Support new features
1278 -* For bug fix
1279 -* Change LoRaWAN bands.
1623 +* (((
1624 +Support new features
1625 +)))
1626 +* (((
1627 +For bug fix
1628 +)))
1629 +* (((
1630 +Change LoRaWAN bands.
1631 +)))
1280 1280  
1633 +(((
1281 1281  Below shows the hardware connection for how to upload an image to RS485-BL:
1635 +)))
1282 1282  
1283 1283  [[image:1654136646995-976.png]]
1284 1284  
... ... @@ -1300,13 +1300,17 @@
1300 1300  
1301 1301  == 6.2 How to change the LoRa Frequency Bands/Region? ==
1302 1302  
1657 +(((
1303 1303  User can follow the introduction for [[how to upgrade image>>||anchor="H6.1Howtoupgradetheimage3F"]]. When download the images, choose the required image file for download.
1659 +)))
1304 1304  
1305 1305  
1306 1306  
1307 1307  == 6.3 How many RS485-Slave can RS485-BL connects? ==
1308 1308  
1665 +(((
1309 1309  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"]].
1667 +)))
1310 1310  
1311 1311  
1312 1312  
... ... @@ -1341,6 +1341,7 @@
1341 1341  * (% style="color:blue" %)**KZ865**(%%): frequency bands KZ865
1342 1342  
1343 1343  
1702 +
1344 1344  = 9. Packing Info =
1345 1345  
1346 1346  (((
... ... @@ -1378,5 +1378,9 @@
1378 1378  
1379 1379  = 10. Support =
1380 1380  
1381 -* 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.
1382 -* Provide as much information as possible regarding your enquiry (product models, accurately describe your problem and steps to replicate it etc) and send a mail to [[support@dragino.com>>url:file:///D:/市场资料/说明书/LoRa/LT系列/support@dragino.com]]
1740 +* (((
1741 +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.
1742 +)))
1743 +* (((
1744 +Provide as much information as possible regarding your enquiry (product models, accurately describe your problem and steps to replicate it etc) and send a mail to [[support@dragino.com>>url:file:///D:/市场资料/说明书/LoRa/LT系列/support@dragino.com]]
1745 +)))
image-20220606105412-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +13.9 KB
Content