Last modified by Karry Zhuang on 2025/03/06 16:34
<
From version < 22.4 >
edited by Xiaoling
on 2022/05/23 09:15
To version < 29.2 >
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:**
... ... @@ -206,18 +206,8 @@
206 206  
207 207  === 3.3.1 onfigure UART settings for RS485 or TTL communication ===
208 208  
209 -RS485-BL can connect to either RS485 sensors or TTL sensor. User need to specify what type of sensor need to connect.
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 -**~1. RS485-MODBUS mode:**
212 -
213 -AT+MOD=1 ~/~/ Support RS485-MODBUS type sensors. User can connect multiply RS485 , Modbus sensors to the A / B pins.
214 -
215 -**2. TTL mode:**
216 -
217 -AT+MOD=2 ~/~/ Support TTL Level sensors, User can connect one TTL Sensor to the TXD/RXD/GND pins.
218 -
219 -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.
220 -
221 221  (% border="1" style="background-color:#ffffcc; color:green; width:795px" %)
222 222  |(((
223 223  **AT Commands**
... ... @@ -242,13 +242,7 @@
242 242  |(((
243 243  AT+PARITY
244 244  )))|(% style="width:285px" %)(((
245 -(((
246 246  Set UART parity (for RS485 connection)
247 -)))
248 -
249 -(((
250 -Default Value is: no parity.
251 -)))
252 252  )))|(% style="width:347px" %)(((
253 253  (((
254 254  AT+PARITY=0
... ... @@ -266,7 +266,7 @@
266 266  )))
267 267  
268 268  (((
269 -Default Value is: 1bit.
253 +
270 270  )))
271 271  )))|(% style="width:347px" %)(((
272 272  (((
... ... @@ -285,12 +285,10 @@
285 285  === 3.3.2 Configure sensors ===
286 286  
287 287  (((
288 -Some sensors might need to configure before normal operation. User can configure such sensor via PC or through RS485-BL AT Commands (% style="color:#4f81bd" %)**AT+CFGDEV**.
289 -)))
290 -
291 291  (((
292 -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.
273 +Some sensors might need to configure before normal operation. User can configure such sensor via PC and RS485 adapter or through RS485-LN AT Commands (% style="color:#4f81bd" %)**AT+CFGDEV**(%%). Each (% style="color:#4f81bd" %)**AT+CFGDEV **(%%)equals to send a RS485 command to sensors. This command will only run when user input it and won’t run during each sampling.
293 293  )))
275 +)))
294 294  
295 295  (% border="1" style="background-color:#ffffcc; color:green; width:806px" %)
296 296  |**AT Commands**|(% style="width:418px" %)**Description**|(% style="width:256px" %)**Example**
... ... @@ -302,8 +302,6 @@
302 302  mm: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
303 303  )))|(% style="width:256px" %)AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
304 304  
305 -Detail of AT+CFGDEV command see [[AT+CFGDEV detail>>path:#AT_CFGDEV]].
306 -
307 307  === 3.3.3 Configure read commands for each sampling ===
308 308  
309 309  (((
... ... @@ -385,11 +385,17 @@
385 385  **m: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command**
386 386  )))
387 387  
368 +(((
388 388  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 +)))
389 389  
372 +(((
390 390  In the RS485-BL, we should use this command AT+COMMAND1=01 03 0B B8 00 02,1 for the same.
374 +)))
391 391  
376 +(((
392 392  **AT+SEARCHx**: This command defines how to handle the return from AT+COMMANDx.
378 +)))
393 393  
394 394  (% border="1" class="table-bordered" %)
395 395  |(((
... ... @@ -401,26 +401,24 @@
401 401  
402 402  )))
403 403  
404 -Examples:
390 +**Examples:**
405 405  
406 -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
407 407  
408 408  If we set AT+SEARCH1=1,1E 56 34.      (max 5 bytes for prefix)
409 409  
410 -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**
411 411  
412 -[[image:1652954654347-831.png]]
398 +[[image:1653269403619-508.png]]
413 413  
400 +2. For a return string from AT+COMMAND1:  16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
414 414  
415 -1. For a return string from AT+COMMAND1:  16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
416 -
417 417  If we set AT+SEARCH1=2, 1E 56 34+31 00 49
418 418  
419 -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**
420 420  
421 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image014.png]]
406 +[[image:1653269438444-278.png]]
422 422  
423 -
424 424  **AT+DATACUTx : **This command defines how to handle the return from AT+COMMANDx, max return length is 45 bytes.
425 425  
426 426  |(((
... ... @@ -435,58 +435,63 @@
435 435  
436 436  * Grab bytes:
437 437  
438 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image015.png]]
422 +[[image:1653269551753-223.png||height="311" width="717"]]
439 439  
440 440  * Grab a section.
441 441  
442 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image016.png]]
426 +[[image:1653269568276-930.png||height="325" width="718"]]
443 443  
444 444  * Grab different sections.
445 445  
446 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image017.png]]
430 +[[image:1653269593172-426.png||height="303" width="725"]]
447 447  
432 +(% style="color:red" %)**Note:**
448 448  
449 -Note:
450 -
451 451  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.
452 452  
453 453  Example:
454 454  
455 -AT+COMMAND1=11 01 1E D0,0
438 +(% style="color:red" %)AT+COMMAND1=11 01 1E D0,0
456 456  
457 -AT+SEARCH1=1,1E 56 34
440 +(% style="color:red" %)AT+SEARCH1=1,1E 56 34
458 458  
459 -AT+DATACUT1=0,2,1~~5
442 +(% style="color:red" %)AT+DATACUT1=0,2,1~~5
460 460  
461 -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
462 462  
463 -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
464 464  
465 -Valid payload after DataCUT command: 2e 30 58 5f 36
448 +(% style="color:red" %)Valid payload after DataCUT command: 2e 30 58 5f 36
466 466  
467 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image018.png]]
450 +[[image:1653269618463-608.png]]
468 468  
452 +=== 3.3.4 Compose the uplink payload ===
469 469  
470 -
471 -
472 -1.
473 -11.
474 -111. Compose the uplink payload
475 -
454 +(((
476 476  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 +)))
477 477  
458 +(((
459 +(% style="color:#4f81bd" %)**Examples: AT+DATAUP=0**
460 +)))
478 478  
479 -**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 +)))
480 480  
481 -Compose the uplink payload with value returns in sequence and send with **A SIGNLE UPLINK**.
482 -
466 +(((
483 483  Final Payload is
468 +)))
484 484  
485 -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 +)))
486 486  
474 +(((
487 487  Where PAYVER is defined by AT+PAYVER, below is an example screen shot.
476 +)))
488 488  
489 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image019.png]]
478 +[[image:1653269759169-150.png]]
490 490  
491 491  
492 492  
... ... @@ -534,8 +534,8 @@
534 534  
535 535  
536 536  
537 -1.
538 -11.
526 +1.
527 +11.
539 539  111. Uplink on demand
540 540  
541 541  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.
... ... @@ -548,8 +548,8 @@
548 548  
549 549  
550 550  
551 -1.
552 -11.
540 +1.
541 +11.
553 553  111. Uplink on Interrupt
554 554  
555 555  Put the interrupt sensor between 3.3v_out and GPIO ext.[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image022.png]]
... ... @@ -563,7 +563,7 @@
563 563  AT+INTMOD=3  Interrupt trigger by rising edge.
564 564  
565 565  
566 -1.
555 +1.
567 567  11. Uplink Payload
568 568  
569 569  |**Size(bytes)**|**2**|**1**|**Length depends on the return from the commands**
... ... @@ -625,15 +625,15 @@
625 625  
626 626  * **Sensor Related Commands**: These commands are special designed for RS485-BL.  User can see these commands below:
627 627  
628 -1.
629 -11.
617 +1.
618 +11.
630 630  111. Common Commands:
631 631  
632 632  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]]
633 633  
634 634  
635 -1.
636 -11.
624 +1.
625 +11.
637 637  111. Sensor related commands:
638 638  
639 639  ==== Choose Device Type (RS485 or TTL) ====
... ... @@ -939,13 +939,13 @@
939 939  
940 940  
941 941  
942 -1.
931 +1.
943 943  11. Buttons
944 944  
945 945  |**Button**|**Feature**
946 946  |**RST**|Reboot RS485-BL
947 947  
948 -1.
937 +1.
949 949  11. +3V3 Output
950 950  
951 951  RS485-BL has a Controllable +3V3 output, user can use this output to power external sensor.
... ... @@ -963,7 +963,7 @@
963 963  By default, the AT+3V3T=0. This is a special case, means the +3V3 output is always on at any time
964 964  
965 965  
966 -1.
955 +1.
967 967  11. +5V Output
968 968  
969 969  RS485-BL has a Controllable +5V output, user can use this output to power external sensor.
... ... @@ -983,13 +983,13 @@
983 983  
984 984  
985 985  
986 -1.
975 +1.
987 987  11. LEDs
988 988  
989 989  |**LEDs**|**Feature**
990 990  |**LED1**|Blink when device transmit a packet.
991 991  
992 -1.
981 +1.
993 993  11. Switch Jumper
994 994  
995 995  |**Switch Jumper**|**Feature**
... ... @@ -1035,7 +1035,7 @@
1035 1035  
1036 1036  
1037 1037  
1038 -1.
1027 +1.
1039 1039  11. Common AT Command Sequence
1040 1040  111. Multi-channel ABP mode (Use with SX1301/LG308)
1041 1041  
... ... @@ -1054,8 +1054,8 @@
1054 1054  
1055 1055  ATZ
1056 1056  
1057 -1.
1058 -11.
1046 +1.
1047 +11.
1059 1059  111. Single-channel ABP mode (Use with LG01/LG02)
1060 1060  
1061 1061  AT+FDR   Reset Parameters to Factory Default, Keys Reserve
... ... @@ -1130,7 +1130,7 @@
1130 1130  [[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]]
1131 1131  
1132 1132  
1133 -1.
1122 +1.
1134 1134  11. How to change the LoRa Frequency Bands/Region?
1135 1135  
1136 1136  User can follow the introduction for [[how to upgrade image>>path:#upgrade_image]]. When download the images, choose the required image file for download.
... ... @@ -1137,7 +1137,7 @@
1137 1137  
1138 1138  
1139 1139  
1140 -1.
1129 +1.
1141 1141  11. How many RS485-Slave can RS485-BL connects?
1142 1142  
1143 1143  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]].
... ... @@ -1154,7 +1154,7 @@
1154 1154  
1155 1155  
1156 1156  
1157 -1.
1146 +1.
1158 1158  11. Why I can’t join TTN V3 in US915 /AU915 bands?
1159 1159  
1160 1160  It might about the channels mapping. Please see for detail.
1653269403619-508.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +27.8 KB
Content
1653269438444-278.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +26.6 KB
Content
1653269551753-223.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +138.7 KB
Content
1653269568276-930.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +131.4 KB
Content
1653269593172-426.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +142.6 KB
Content
1653269618463-608.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +27.7 KB
Content
1653269759169-150.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +294.0 KB
Content

Applications

Navigation

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