Skip to Content
Last modified by Xiaoling on 2025/04/23 15:57
From version 15.5
edited by Xiaoling
on 2022/05/19 17:52
Change comment: There is no comment for this version
To version 27.1
edited by Xiaoling
on 2022/05/23 10:28
Change comment: Uploaded new attachment "1653272901032-107.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -60,7 +60,7 @@
60 60  * Power Consumption (exclude RS485 device):
61 61  ** Idle: 6uA@3.3v
62 62  
63 -*
63 +*
64 64  ** 20dB Transmit: 130mA@3.3v
65 65  
66 66  **Interface for Model:**
... ... @@ -303,88 +303,102 @@
303 303  )))
304 304  )))
305 305  
306 +=== 3.3.2 Configure sensors ===
306 306  
308 +(((
309 +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**.
310 +)))
307 307  
312 +(((
313 +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.
314 +)))
308 308  
309 -1.
310 -11.
311 -111. Configure sensors
312 -
313 -Some sensors might need to configure before normal operation. User can configure such sensor via PC or through RS485-BL AT Commands AT+CFGDEV.
314 -
315 -
316 -When user issue an AT+CFGDEV command, Each 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.
317 -
318 -|**AT Commands**|**Description**|**Example**
319 -|AT+CFGDEV|(((
316 +(% border="1" style="background-color:#ffffcc; color:green; width:806px" %)
317 +|**AT Commands**|(% style="width:418px" %)**Description**|(% style="width:256px" %)**Example**
318 +|AT+CFGDEV|(% style="width:418px" %)(((
320 320  This command is used to configure the RS485/TTL devices; they won’t be used during sampling.
321 321  
322 -AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
321 +AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,
323 323  
324 -m: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
325 -)))|AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
323 +mm: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
324 +)))|(% style="width:256px" %)AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
326 326  
327 327  Detail of AT+CFGDEV command see [[AT+CFGDEV detail>>path:#AT_CFGDEV]].
328 328  
328 +=== 3.3.3 Configure read commands for each sampling ===
329 329  
330 -
331 -
332 -
333 -1.
334 -11.
335 -111. Configure read commands for each sampling
336 -
330 +(((
337 337  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.
332 +)))
338 338  
339 -
334 +(((
340 340  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.
336 +)))
341 341  
342 -
338 +(((
343 343  To save the LoRaWAN network bandwidth, we might need to read data from different sensors and combine their valid value into a short payload.
340 +)))
344 344  
345 -
342 +(((
346 346  This section describes how to achieve above goals.
344 +)))
347 347  
348 -
346 +(((
349 349  During each sampling, the RS485-BL can support 15 commands to read sensors. And combine the return to one or several uplink payloads.
348 +)))
350 350  
351 -
350 +(((
352 352  **Command from RS485-BL to Sensor:**
352 +)))
353 353  
354 +(((
354 354  RS485-BL can send out pre-set max 15 strings via **AT+COMMAD1**, **ATCOMMAND2**,…, to **AT+COMMANDF** . All commands are of same grammar.
356 +)))
355 355  
356 -
358 +(((
357 357  **Handle return from sensors to RS485-BL**:
360 +)))
358 358  
362 +(((
359 359  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**
364 +)))
360 360  
366 +* (((
367 +**AT+DATACUT**
368 +)))
361 361  
362 -* **AT+DATACUT**
363 -
370 +(((
364 364  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.
372 +)))
365 365  
374 +* (((
375 +**AT+SEARCH**
376 +)))
366 366  
367 -* **AT+SEARCH**
368 -
378 +(((
369 369  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.
380 +)))
370 370  
371 -
382 +(((
372 372  **Define wait timeout:**
384 +)))
373 373  
386 +(((
374 374  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
388 +)))
375 375  
376 -
390 +(((
377 377  After we got the valid value from each RS485 commands, we need to combine them together with the command **AT+DATAUP**.
392 +)))
378 378  
379 -
380 380  **Examples:**
381 381  
382 382  Below are examples for the how above AT Commands works.
383 383  
384 -
385 385  **AT+COMMANDx : **This command will be sent to RS485/TTL devices during each sampling, Max command length is 14 bytes. The grammar is:
386 386  
387 -|(((
400 +(% border="1" class="table-bordered" style="background-color:#4f81bd; color:white; width:501px" %)
401 +|(% style="width:498px" %)(((
388 388  **AT+COMMANDx=xx xx xx xx xx xx xx xx xx xx xx xx,m**
389 389  
390 390  **xx xx xx xx xx xx xx xx xx xx xx xx: The RS485 command to be sent**
... ... @@ -396,41 +396,38 @@
396 396  
397 397  In the RS485-BL, we should use this command AT+COMMAND1=01 03 0B B8 00 02,1 for the same.
398 398  
399 -
400 400  **AT+SEARCHx**: This command defines how to handle the return from AT+COMMANDx.
401 401  
402 -|(((
415 +(% border="1" class="table-bordered" style="background-color:#4f81bd; color:white; width:580px" %)
416 +|(% style="width:577px" %)(((
403 403  **AT+SEARCHx=aa,xx xx xx xx xx**
404 404  
405 405  * **aa: 1: prefix match mode; 2: prefix and suffix match mode**
406 406  * **xx xx xx xx xx: match string. Max 5 bytes for prefix and 5 bytes for suffix**
407 -
408 -
409 409  )))
410 410  
411 -Examples:
423 +**Examples:**
412 412  
413 413  1. 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 415  If we set AT+SEARCH1=1,1E 56 34.      (max 5 bytes for prefix)
416 416  
417 -The valid data will be all bytes after 1E 56 34 , so it is 2e 30 58 5f 36 41 30 31 00 49
429 +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**
418 418  
419 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image013.png]]
431 +[[image:1653271044481-711.png]]
420 420  
421 -
422 422  1. For a return string from AT+COMMAND1:  16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
423 423  
424 424  If we set AT+SEARCH1=2, 1E 56 34+31 00 49
425 425  
426 -Device will search the bytes between 1E 56 34 and 31 00 49. So it is 2e 30 58 5f 36 41 30
437 +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**
427 427  
428 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image014.png]]
439 +[[image:1653271276735-972.png]]
429 429  
430 -
431 431  **AT+DATACUTx : **This command defines how to handle the return from AT+COMMANDx, max return length is 45 bytes.
432 432  
433 -|(((
443 +(% style="background-color:#4f81bd; color:white; width:729px" %)
444 +|(% style="width:726px" %)(((
434 434  **AT+DATACUTx=a,b,c**
435 435  
436 436  * **a: length for the return of AT+COMMAND**
... ... @@ -442,85 +442,123 @@
442 442  
443 443  * Grab bytes:
444 444  
445 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image015.png]]
456 +[[image:1653271581490-837.png||height="313" width="722"]]
446 446  
447 447  * Grab a section.
448 448  
449 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image016.png]]
460 +[[image:1653271648378-342.png||height="326" width="720"]]
450 450  
451 451  * Grab different sections.
452 452  
453 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image017.png]]
464 +[[image:1653271657255-576.png||height="305" width="730"]]
454 454  
466 +(((
467 +(% style="color:red" %)**Note:**
468 +)))
455 455  
456 -Note:
457 -
470 +(((
458 458  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.
472 +)))
459 459  
460 -Example:
474 +(((
475 +**Example:**
476 +)))
461 461  
462 -AT+COMMAND1=11 01 1E D0,0
478 +(((
479 +(% style="color:red" %)AT+COMMAND1=11 01 1E D0,0
480 +)))
463 463  
464 -AT+SEARCH1=1,1E 56 34
482 +(((
483 +(% style="color:red" %)AT+SEARCH1=1,1E 56 34
484 +)))
465 465  
466 -AT+DATACUT1=0,2,1~~5
486 +(((
487 +(% style="color:red" %)AT+DATACUT1=0,2,1~~5
488 +)))
467 467  
468 -Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
490 +(((
491 +(% style="color:red" %)Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
492 +)))
469 469  
470 -String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49
494 +(((
495 +(% style="color:red" %)String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49
496 +)))
471 471  
472 -Valid payload after DataCUT command: 2e 30 58 5f 36
498 +(((
499 +(% style="color:red" %)Valid payload after DataCUT command: 2e 30 58 5f 36
500 +)))
473 473  
474 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image018.png]]
502 +[[image:1653271763403-806.png]]
475 475  
504 +=== 3.3.4 Compose the uplink payload ===
476 476  
477 -
478 -
479 -1.
480 -11.
481 -111. Compose the uplink payload
482 -
506 +(((
483 483  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.**
508 +)))
484 484  
510 +(((
511 +(% style="color:#4f81bd" %)**Examples: AT+DATAUP=0**
512 +)))
485 485  
486 -**Examples: AT+DATAUP=0**
514 +(((
515 +Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**A SIGNLE UPLINK**.
516 +)))
487 487  
488 -Compose the uplink payload with value returns in sequence and send with **A SIGNLE UPLINK**.
489 -
518 +(((
490 490  Final Payload is
520 +)))
491 491  
492 -Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx
522 +(((
523 +(% style="color:#4f81bd" %)Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx
524 +)))
493 493  
526 +(((
494 494  Where PAYVER is defined by AT+PAYVER, below is an example screen shot.
528 +)))
495 495  
496 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image019.png]]
530 +[[image:1653272787040-634.png||height="515" width="719"]]
497 497  
532 +(((
533 +(% style="color:#4f81bd" %)**Examples: AT+DATAUP=1**
534 +)))
498 498  
536 +(((
537 +Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**Multiply UPLINKs**.
538 +)))
499 499  
500 -**Examples: AT+DATAUP=1**
501 -
502 -Compose the uplink payload with value returns in sequence and send with **Multiply UPLINKs**.
503 -
540 +(((
504 504  Final Payload is
542 +)))
505 505  
506 -Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA
544 +(((
545 +(% style="color:#4f81bd" %)Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA
546 +)))
507 507  
508 -1. Battery Info (2 bytes): Battery voltage
509 -1. PAYVER (1 byte): Defined by AT+PAYVER
510 -1. PAYLOAD COUNT (1 byte): Total how many uplinks of this sampling.
511 -1. PAYLOAD# (1 byte): Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT)
512 -1. DATA: Valid value: max 6 bytes(US915 version here, [[Notice*!>>path:#max_byte]]) for each uplink so each uplink <= 11 bytes. For the last uplink, DATA will might less than 6 bytes
548 +1. (((
549 +Battery Info (2 bytes): Battery voltage
550 +)))
551 +1. (((
552 +PAYVER (1 byte): Defined by AT+PAYVER
553 +)))
554 +1. (((
555 +PAYLOAD COUNT (1 byte): Total how many uplinks of this sampling.
556 +)))
557 +1. (((
558 +PAYLOAD# (1 byte): Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT)
559 +)))
560 +1. (((
561 +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
562 +)))
513 513  
514 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image020.png]]
564 +[[image:1653272817147-600.png||height="437" width="717"]]
515 515  
516 -
517 517  So totally there will be 3 uplinks for this sampling, each uplink includes 6 bytes DATA
518 518  
519 -DATA1=RETURN1 Valid Value = 20 20 0a 33 90 41
568 +DATA1=RETURN1 Valid Value = ~(% style="background-color:#4f81bd;color:white" %)(% style="display:none" %) (%%)20 20 0a 33 90 41
520 520  
521 -DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10= 02 aa 05 81 0a 20
570 +DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10= ~(% style="background-color:#4f81bd;color:white" %)(% style="display:none" %) (%%)02 aa 05 81 0a 20
522 522  
523 -DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 = 20 20 20 2d 30
572 +DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 =~(% style="background-color:#4f81bd;color:white" %)(% style="display:none" %) (%%) 20 20 20 2d 30
524 524  
525 525  
526 526  
... ... @@ -541,8 +541,8 @@
541 541  
542 542  
543 543  
544 -1.
545 -11.
593 +1.
594 +11.
546 546  111. Uplink on demand
547 547  
548 548  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.
... ... @@ -555,8 +555,8 @@
555 555  
556 556  
557 557  
558 -1.
559 -11.
607 +1.
608 +11.
560 560  111. Uplink on Interrupt
561 561  
562 562  Put the interrupt sensor between 3.3v_out and GPIO ext.[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image022.png]]
... ... @@ -570,7 +570,7 @@
570 570  AT+INTMOD=3  Interrupt trigger by rising edge.
571 571  
572 572  
573 -1.
622 +1.
574 574  11. Uplink Payload
575 575  
576 576  |**Size(bytes)**|**2**|**1**|**Length depends on the return from the commands**
... ... @@ -632,15 +632,15 @@
632 632  
633 633  * **Sensor Related Commands**: These commands are special designed for RS485-BL.  User can see these commands below:
634 634  
635 -1.
636 -11.
684 +1.
685 +11.
637 637  111. Common Commands:
638 638  
639 639  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]]
640 640  
641 641  
642 -1.
643 -11.
691 +1.
692 +11.
644 644  111. Sensor related commands:
645 645  
646 646  ==== Choose Device Type (RS485 or TTL) ====
... ... @@ -946,13 +946,13 @@
946 946  
947 947  
948 948  
949 -1.
998 +1.
950 950  11. Buttons
951 951  
952 952  |**Button**|**Feature**
953 953  |**RST**|Reboot RS485-BL
954 954  
955 -1.
1004 +1.
956 956  11. +3V3 Output
957 957  
958 958  RS485-BL has a Controllable +3V3 output, user can use this output to power external sensor.
... ... @@ -970,7 +970,7 @@
970 970  By default, the AT+3V3T=0. This is a special case, means the +3V3 output is always on at any time
971 971  
972 972  
973 -1.
1022 +1.
974 974  11. +5V Output
975 975  
976 976  RS485-BL has a Controllable +5V output, user can use this output to power external sensor.
... ... @@ -990,13 +990,13 @@
990 990  
991 991  
992 992  
993 -1.
1042 +1.
994 994  11. LEDs
995 995  
996 996  |**LEDs**|**Feature**
997 997  |**LED1**|Blink when device transmit a packet.
998 998  
999 -1.
1048 +1.
1000 1000  11. Switch Jumper
1001 1001  
1002 1002  |**Switch Jumper**|**Feature**
... ... @@ -1042,7 +1042,7 @@
1042 1042  
1043 1043  
1044 1044  
1045 -1.
1094 +1.
1046 1046  11. Common AT Command Sequence
1047 1047  111. Multi-channel ABP mode (Use with SX1301/LG308)
1048 1048  
... ... @@ -1061,8 +1061,8 @@
1061 1061  
1062 1062  ATZ
1063 1063  
1064 -1.
1065 -11.
1113 +1.
1114 +11.
1066 1066  111. Single-channel ABP mode (Use with LG01/LG02)
1067 1067  
1068 1068  AT+FDR   Reset Parameters to Factory Default, Keys Reserve
... ... @@ -1137,7 +1137,7 @@
1137 1137  [[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]]
1138 1138  
1139 1139  
1140 -1.
1189 +1.
1141 1141  11. How to change the LoRa Frequency Bands/Region?
1142 1142  
1143 1143  User can follow the introduction for [[how to upgrade image>>path:#upgrade_image]]. When download the images, choose the required image file for download.
... ... @@ -1144,7 +1144,7 @@
1144 1144  
1145 1145  
1146 1146  
1147 -1.
1196 +1.
1148 1148  11. How many RS485-Slave can RS485-BL connects?
1149 1149  
1150 1150  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]].
... ... @@ -1161,7 +1161,7 @@
1161 1161  
1162 1162  
1163 1163  
1164 -1.
1213 +1.
1165 1165  11. Why I can’t join TTN V3 in US915 /AU915 bands?
1166 1166  
1167 1167  It might about the channels mapping. Please see for detail.
1652954654347-831.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +138.7 KB
Content
1653271044481-711.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +27.8 KB
Content
1653271276735-972.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +26.6 KB
Content
1653271581490-837.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +138.7 KB
Content
1653271648378-342.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +131.4 KB
Content
1653271657255-576.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +142.6 KB
Content
1653271763403-806.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +27.7 KB
Content
1653272787040-634.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +294.0 KB
Content
1653272817147-600.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +143.3 KB
Content
1653272901032-107.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +197.8 KB
Content