Last modified by Karry Zhuang on 2025/03/06 16:34
<
From version < 29.2 >
edited by Xiaoling
on 2022/05/23 09:37
To version < 29.1 >
edited by Xiaoling
on 2022/05/23 09:35
>
Change comment: Uploaded new attachment "1653269759169-150.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -45,7 +45,7 @@
45 45  * Power Consumption (exclude RS485 device):
46 46  ** Idle: 32mA@12v
47 47  
48 -*
48 +*
49 49  ** 20dB Transmit: 65mA@12v
50 50  
51 51  **Interface for Model:**
... ... @@ -365,17 +365,11 @@
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 373  In the RS485-BL, we should use this command AT+COMMAND1=01 03 0B B8 00 02,1 for the same.
374 -)))
375 375  
376 -(((
377 377  **AT+SEARCHx**: This command defines how to handle the return from AT+COMMANDx.
378 -)))
379 379  
380 380  (% border="1" class="table-bordered" %)
381 381  |(((
... ... @@ -387,24 +387,26 @@
387 387  
388 388  )))
389 389  
390 -**Examples:**
384 +Examples:
391 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
386 +1. For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
393 393  
394 394  If we set AT+SEARCH1=1,1E 56 34.      (max 5 bytes for prefix)
395 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**
390 +The valid data will be all bytes after 1E 56 34 , so it is 2e 30 58 5f 36 41 30 31 00 49
397 397  
398 -[[image:1653269403619-508.png]]
392 +[[image:1652954654347-831.png]]
399 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 401  
395 +1. For a return string from AT+COMMAND1:  16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
396 +
402 402  If we set AT+SEARCH1=2, 1E 56 34+31 00 49
403 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**
399 +Device will search the bytes between 1E 56 34 and 31 00 49. So it is 2e 30 58 5f 36 41 30
405 405  
406 -[[image:1653269438444-278.png]]
401 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image014.png]]
407 407  
403 +
408 408  **AT+DATACUTx : **This command defines how to handle the return from AT+COMMANDx, max return length is 45 bytes.
409 409  
410 410  |(((
... ... @@ -419,63 +419,58 @@
419 419  
420 420  * Grab bytes:
421 421  
422 -[[image:1653269551753-223.png||height="311" width="717"]]
418 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image015.png]]
423 423  
424 424  * Grab a section.
425 425  
426 -[[image:1653269568276-930.png||height="325" width="718"]]
422 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image016.png]]
427 427  
428 428  * Grab different sections.
429 429  
430 -[[image:1653269593172-426.png||height="303" width="725"]]
426 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image017.png]]
431 431  
432 -(% style="color:red" %)**Note:**
433 433  
429 +Note:
430 +
434 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 435  
436 436  Example:
437 437  
438 -(% style="color:red" %)AT+COMMAND1=11 01 1E D0,0
435 +AT+COMMAND1=11 01 1E D0,0
439 439  
440 -(% style="color:red" %)AT+SEARCH1=1,1E 56 34
437 +AT+SEARCH1=1,1E 56 34
441 441  
442 -(% style="color:red" %)AT+DATACUT1=0,2,1~~5
439 +AT+DATACUT1=0,2,1~~5
443 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
441 +Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
445 445  
446 -(% style="color:red" %)String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49
443 +String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49
447 447  
448 -(% style="color:red" %)Valid payload after DataCUT command: 2e 30 58 5f 36
445 +Valid payload after DataCUT command: 2e 30 58 5f 36
449 449  
450 -[[image:1653269618463-608.png]]
447 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image018.png]]
451 451  
452 -=== 3.3.4 Compose the uplink payload ===
453 453  
454 -(((
450 +
451 +
452 +1.
453 +11.
454 +111. Compose the uplink payload
455 +
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.**
456 -)))
457 457  
458 -(((
459 -(% style="color:#4f81bd" %)**Examples: AT+DATAUP=0**
460 -)))
461 461  
462 -(((
463 -Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**A SIGNLE UPLINK**.
464 -)))
459 +**Examples: AT+DATAUP=0**
465 465  
466 -(((
461 +Compose the uplink payload with value returns in sequence and send with **A SIGNLE UPLINK**.
462 +
467 467  Final Payload is
468 -)))
469 469  
470 -(((
471 -(% style="color:#4f81bd" %)**Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx**
472 -)))
465 +Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx
473 473  
474 -(((
475 475  Where PAYVER is defined by AT+PAYVER, below is an example screen shot.
476 -)))
477 477  
478 -[[image:1653269759169-150.png]]
469 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image019.png]]
479 479  
480 480  
481 481  
... ... @@ -523,8 +523,8 @@
523 523  
524 524  
525 525  
526 -1.
527 -11.
517 +1.
518 +11.
528 528  111. Uplink on demand
529 529  
530 530  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.
... ... @@ -537,8 +537,8 @@
537 537  
538 538  
539 539  
540 -1.
541 -11.
531 +1.
532 +11.
542 542  111. Uplink on Interrupt
543 543  
544 544  Put the interrupt sensor between 3.3v_out and GPIO ext.[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image022.png]]
... ... @@ -552,7 +552,7 @@
552 552  AT+INTMOD=3  Interrupt trigger by rising edge.
553 553  
554 554  
555 -1.
546 +1.
556 556  11. Uplink Payload
557 557  
558 558  |**Size(bytes)**|**2**|**1**|**Length depends on the return from the commands**
... ... @@ -614,15 +614,15 @@
614 614  
615 615  * **Sensor Related Commands**: These commands are special designed for RS485-BL.  User can see these commands below:
616 616  
617 -1.
618 -11.
608 +1.
609 +11.
619 619  111. Common Commands:
620 620  
621 621  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]]
622 622  
623 623  
624 -1.
625 -11.
615 +1.
616 +11.
626 626  111. Sensor related commands:
627 627  
628 628  ==== Choose Device Type (RS485 or TTL) ====
... ... @@ -928,13 +928,13 @@
928 928  
929 929  
930 930  
931 -1.
922 +1.
932 932  11. Buttons
933 933  
934 934  |**Button**|**Feature**
935 935  |**RST**|Reboot RS485-BL
936 936  
937 -1.
928 +1.
938 938  11. +3V3 Output
939 939  
940 940  RS485-BL has a Controllable +3V3 output, user can use this output to power external sensor.
... ... @@ -952,7 +952,7 @@
952 952  By default, the AT+3V3T=0. This is a special case, means the +3V3 output is always on at any time
953 953  
954 954  
955 -1.
946 +1.
956 956  11. +5V Output
957 957  
958 958  RS485-BL has a Controllable +5V output, user can use this output to power external sensor.
... ... @@ -972,13 +972,13 @@
972 972  
973 973  
974 974  
975 -1.
966 +1.
976 976  11. LEDs
977 977  
978 978  |**LEDs**|**Feature**
979 979  |**LED1**|Blink when device transmit a packet.
980 980  
981 -1.
972 +1.
982 982  11. Switch Jumper
983 983  
984 984  |**Switch Jumper**|**Feature**
... ... @@ -1024,7 +1024,7 @@
1024 1024  
1025 1025  
1026 1026  
1027 -1.
1018 +1.
1028 1028  11. Common AT Command Sequence
1029 1029  111. Multi-channel ABP mode (Use with SX1301/LG308)
1030 1030  
... ... @@ -1043,8 +1043,8 @@
1043 1043  
1044 1044  ATZ
1045 1045  
1046 -1.
1047 -11.
1037 +1.
1038 +11.
1048 1048  111. Single-channel ABP mode (Use with LG01/LG02)
1049 1049  
1050 1050  AT+FDR   Reset Parameters to Factory Default, Keys Reserve
... ... @@ -1119,7 +1119,7 @@
1119 1119  [[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]]
1120 1120  
1121 1121  
1122 -1.
1113 +1.
1123 1123  11. How to change the LoRa Frequency Bands/Region?
1124 1124  
1125 1125  User can follow the introduction for [[how to upgrade image>>path:#upgrade_image]]. When download the images, choose the required image file for download.
... ... @@ -1126,7 +1126,7 @@
1126 1126  
1127 1127  
1128 1128  
1129 -1.
1120 +1.
1130 1130  11. How many RS485-Slave can RS485-BL connects?
1131 1131  
1132 1132  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]].
... ... @@ -1143,7 +1143,7 @@
1143 1143  
1144 1144  
1145 1145  
1146 -1.
1137 +1.
1147 1147  11. Why I can’t join TTN V3 in US915 /AU915 bands?
1148 1148  
1149 1149  It might about the channels mapping. Please see for detail.

Applications

Navigation

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