<
From version < 29.1 >
edited by Xiaoling
on 2022/05/23 09:35
To version < 29.3 >
edited by Xiaoling
on 2022/05/23 09:37
>
Change comment: There is no comment for this version

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,11 +365,17 @@
365 365  **m: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command**
366 366  )))
367 367  
368 +(((
368 368  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 +)))
369 369  
372 +(((
370 370  In the RS485-BL, we should use this command AT+COMMAND1=01 03 0B B8 00 02,1 for the same.
374 +)))
371 371  
376 +(((
372 372  **AT+SEARCHx**: This command defines how to handle the return from AT+COMMANDx.
378 +)))
373 373  
374 374  (% border="1" class="table-bordered" %)
375 375  |(((
... ... @@ -381,26 +381,24 @@
381 381  
382 382  )))
383 383  
384 -Examples:
390 +**Examples:**
385 385  
386 -1. For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
392 +~1. For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
387 387  
388 388  If we set AT+SEARCH1=1,1E 56 34.      (max 5 bytes for prefix)
389 389  
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
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**
391 391  
392 -[[image:1652954654347-831.png]]
398 +[[image:1653269403619-508.png]]
393 393  
400 +2. For a return string from AT+COMMAND1:  16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
394 394  
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 -
397 397  If we set AT+SEARCH1=2, 1E 56 34+31 00 49
398 398  
399 -Device will search the bytes between 1E 56 34 and 31 00 49. So it is 2e 30 58 5f 36 41 30
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**
400 400  
401 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image014.png]]
406 +[[image:1653269438444-278.png]]
402 402  
403 -
404 404  **AT+DATACUTx : **This command defines how to handle the return from AT+COMMANDx, max return length is 45 bytes.
405 405  
406 406  |(((
... ... @@ -415,58 +415,63 @@
415 415  
416 416  * Grab bytes:
417 417  
418 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image015.png]]
422 +[[image:1653269551753-223.png||height="311" width="717"]]
419 419  
420 420  * Grab a section.
421 421  
422 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image016.png]]
426 +[[image:1653269568276-930.png||height="325" width="718"]]
423 423  
424 424  * Grab different sections.
425 425  
426 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image017.png]]
430 +[[image:1653269593172-426.png||height="303" width="725"]]
427 427  
432 +(% style="color:red" %)**Note:**
428 428  
429 -Note:
430 -
431 431  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.
432 432  
433 433  Example:
434 434  
435 -AT+COMMAND1=11 01 1E D0,0
438 +(% style="color:red" %)AT+COMMAND1=11 01 1E D0,0
436 436  
437 -AT+SEARCH1=1,1E 56 34
440 +(% style="color:red" %)AT+SEARCH1=1,1E 56 34
438 438  
439 -AT+DATACUT1=0,2,1~~5
442 +(% style="color:red" %)AT+DATACUT1=0,2,1~~5
440 440  
441 -Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
444 +(% style="color:red" %)Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
442 442  
443 -String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49
446 +(% style="color:red" %)String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49
444 444  
445 -Valid payload after DataCUT command: 2e 30 58 5f 36
448 +(% style="color:red" %)Valid payload after DataCUT command: 2e 30 58 5f 36
446 446  
447 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image018.png]]
450 +[[image:1653269618463-608.png]]
448 448  
452 +=== 3.3.4 Compose the uplink payload ===
449 449  
450 -
451 -
452 -1.
453 -11.
454 -111. Compose the uplink payload
455 -
454 +(((
456 456  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 +)))
458 458  
459 -**Examples: AT+DATAUP=0**
462 +(((
463 +Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**A SIGNLE UPLINK**.
464 +)))
460 460  
461 -Compose the uplink payload with value returns in sequence and send with **A SIGNLE UPLINK**.
462 -
466 +(((
463 463  Final Payload is
468 +)))
464 464  
465 -Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx
470 +(((
471 +(% style="color:#4f81bd" %)**Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx**
472 +)))
466 466  
474 +(((
467 467  Where PAYVER is defined by AT+PAYVER, below is an example screen shot.
476 +)))
468 468  
469 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image019.png]]
478 +[[image:1653269759169-150.png||height="513" width="716"]]
470 470  
471 471  
472 472  
... ... @@ -514,8 +514,8 @@
514 514  
515 515  
516 516  
517 -1.
518 -11.
526 +1.
527 +11.
519 519  111. Uplink on demand
520 520  
521 521  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.
... ... @@ -528,8 +528,8 @@
528 528  
529 529  
530 530  
531 -1.
532 -11.
540 +1.
541 +11.
533 533  111. Uplink on Interrupt
534 534  
535 535  Put the interrupt sensor between 3.3v_out and GPIO ext.[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image022.png]]
... ... @@ -543,7 +543,7 @@
543 543  AT+INTMOD=3  Interrupt trigger by rising edge.
544 544  
545 545  
546 -1.
555 +1.
547 547  11. Uplink Payload
548 548  
549 549  |**Size(bytes)**|**2**|**1**|**Length depends on the return from the commands**
... ... @@ -605,15 +605,15 @@
605 605  
606 606  * **Sensor Related Commands**: These commands are special designed for RS485-BL.  User can see these commands below:
607 607  
608 -1.
609 -11.
617 +1.
618 +11.
610 610  111. Common Commands:
611 611  
612 612  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]]
613 613  
614 614  
615 -1.
616 -11.
624 +1.
625 +11.
617 617  111. Sensor related commands:
618 618  
619 619  ==== Choose Device Type (RS485 or TTL) ====
... ... @@ -919,13 +919,13 @@
919 919  
920 920  
921 921  
922 -1.
931 +1.
923 923  11. Buttons
924 924  
925 925  |**Button**|**Feature**
926 926  |**RST**|Reboot RS485-BL
927 927  
928 -1.
937 +1.
929 929  11. +3V3 Output
930 930  
931 931  RS485-BL has a Controllable +3V3 output, user can use this output to power external sensor.
... ... @@ -943,7 +943,7 @@
943 943  By default, the AT+3V3T=0. This is a special case, means the +3V3 output is always on at any time
944 944  
945 945  
946 -1.
955 +1.
947 947  11. +5V Output
948 948  
949 949  RS485-BL has a Controllable +5V output, user can use this output to power external sensor.
... ... @@ -963,13 +963,13 @@
963 963  
964 964  
965 965  
966 -1.
975 +1.
967 967  11. LEDs
968 968  
969 969  |**LEDs**|**Feature**
970 970  |**LED1**|Blink when device transmit a packet.
971 971  
972 -1.
981 +1.
973 973  11. Switch Jumper
974 974  
975 975  |**Switch Jumper**|**Feature**
... ... @@ -1015,7 +1015,7 @@
1015 1015  
1016 1016  
1017 1017  
1018 -1.
1027 +1.
1019 1019  11. Common AT Command Sequence
1020 1020  111. Multi-channel ABP mode (Use with SX1301/LG308)
1021 1021  
... ... @@ -1034,8 +1034,8 @@
1034 1034  
1035 1035  ATZ
1036 1036  
1037 -1.
1038 -11.
1046 +1.
1047 +11.
1039 1039  111. Single-channel ABP mode (Use with LG01/LG02)
1040 1040  
1041 1041  AT+FDR   Reset Parameters to Factory Default, Keys Reserve
... ... @@ -1110,7 +1110,7 @@
1110 1110  [[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]]
1111 1111  
1112 1112  
1113 -1.
1122 +1.
1114 1114  11. How to change the LoRa Frequency Bands/Region?
1115 1115  
1116 1116  User can follow the introduction for [[how to upgrade image>>path:#upgrade_image]]. When download the images, choose the required image file for download.
... ... @@ -1117,7 +1117,7 @@
1117 1117  
1118 1118  
1119 1119  
1120 -1.
1129 +1.
1121 1121  11. How many RS485-Slave can RS485-BL connects?
1122 1122  
1123 1123  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]].
... ... @@ -1134,7 +1134,7 @@
1134 1134  
1135 1135  
1136 1136  
1137 -1.
1146 +1.
1138 1138  11. Why I can’t join TTN V3 in US915 /AU915 bands?
1139 1139  
1140 1140  It might about the channels mapping. Please see for detail.
Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0