Changes for page RS485-LN – RS485 to LoRaWAN Converter User Manual
Last modified by Karry Zhuang on 2025/03/06 16:34
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 7 added, 0 removed)
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:** ... ... @@ -284,8 +284,6 @@ 284 284 mm: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command 285 285 )))|(% style="width:256px" %)AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m 286 286 287 -Detail of AT+CFGDEV command see [[AT+CFGDEV detail>>path:#AT_CFGDEV]]. 288 - 289 289 === 3.3.3 Configure read commands for each sampling === 290 290 291 291 ((( ... ... @@ -367,11 +367,17 @@ 367 367 **m: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command** 368 368 ))) 369 369 368 +((( 370 370 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 +((( 372 372 In the RS485-BL, we should use this command AT+COMMAND1=01 03 0B B8 00 02,1 for the same. 374 +))) 373 373 376 +((( 374 374 **AT+SEARCHx**: This command defines how to handle the return from AT+COMMANDx. 378 +))) 375 375 376 376 (% border="1" class="table-bordered" %) 377 377 |((( ... ... @@ -383,26 +383,24 @@ 383 383 384 384 ))) 385 385 386 -Examples: 390 +**Examples:** 387 387 388 -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 389 389 390 390 If we set AT+SEARCH1=1,1E 56 34. (max 5 bytes for prefix) 391 391 392 -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** 393 393 394 -[[image:16529 54654347-831.png]]398 +[[image:1653269403619-508.png]] 395 395 400 +2. For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49 396 396 397 -1. For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49 398 - 399 399 If we set AT+SEARCH1=2, 1E 56 34+31 00 49 400 400 401 -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** 402 402 403 -[[image: file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image014.png]]406 +[[image:1653269438444-278.png]] 404 404 405 - 406 406 **AT+DATACUTx : **This command defines how to handle the return from AT+COMMANDx, max return length is 45 bytes. 407 407 408 408 |((( ... ... @@ -417,58 +417,63 @@ 417 417 418 418 * Grab bytes: 419 419 420 -[[image: file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image015.png]]422 +[[image:1653269551753-223.png||height="311" width="717"]] 421 421 422 422 * Grab a section. 423 423 424 -[[image: file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image016.png]]426 +[[image:1653269568276-930.png||height="325" width="718"]] 425 425 426 426 * Grab different sections. 427 427 428 -[[image: file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image017.png]]430 +[[image:1653269593172-426.png||height="303" width="725"]] 429 429 432 +(% style="color:red" %)**Note:** 430 430 431 -Note: 432 - 433 433 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. 434 434 435 435 Example: 436 436 437 -AT+COMMAND1=11 01 1E D0,0 438 +(% style="color:red" %)AT+COMMAND1=11 01 1E D0,0 438 438 439 -AT+SEARCH1=1,1E 56 34 440 +(% style="color:red" %)AT+SEARCH1=1,1E 56 34 440 440 441 -AT+DATACUT1=0,2,1~~5 442 +(% style="color:red" %)AT+DATACUT1=0,2,1~~5 442 442 443 -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 444 444 445 -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 446 446 447 -Valid payload after DataCUT command: 2e 30 58 5f 36 448 +(% style="color:red" %)Valid payload after DataCUT command: 2e 30 58 5f 36 448 448 449 -[[image: file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image018.png]]450 +[[image:1653269618463-608.png]] 450 450 452 +=== 3.3.4 Compose the uplink payload === 451 451 452 - 453 - 454 -1. 455 -11. 456 -111. Compose the uplink payload 457 - 454 +((( 458 458 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 +))) 459 459 458 +((( 459 +(% style="color:#4f81bd" %)**Examples: AT+DATAUP=0** 460 +))) 460 460 461 -**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 +))) 462 462 463 -Compose the uplink payload with value returns in sequence and send with **A SIGNLE UPLINK**. 464 - 466 +((( 465 465 Final Payload is 468 +))) 466 466 467 -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 +))) 468 468 474 +((( 469 469 Where PAYVER is defined by AT+PAYVER, below is an example screen shot. 476 +))) 470 470 471 -[[image: file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image019.png]]478 +[[image:1653269759169-150.png||height="513" width="716"]] 472 472 473 473 474 474 ... ... @@ -516,8 +516,8 @@ 516 516 517 517 518 518 519 -1. 520 -11. 526 +1. 527 +11. 521 521 111. Uplink on demand 522 522 523 523 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. ... ... @@ -530,8 +530,8 @@ 530 530 531 531 532 532 533 -1. 534 -11. 540 +1. 541 +11. 535 535 111. Uplink on Interrupt 536 536 537 537 Put the interrupt sensor between 3.3v_out and GPIO ext.[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image022.png]] ... ... @@ -545,7 +545,7 @@ 545 545 AT+INTMOD=3 Interrupt trigger by rising edge. 546 546 547 547 548 -1. 555 +1. 549 549 11. Uplink Payload 550 550 551 551 |**Size(bytes)**|**2**|**1**|**Length depends on the return from the commands** ... ... @@ -607,15 +607,15 @@ 607 607 608 608 * **Sensor Related Commands**: These commands are special designed for RS485-BL. User can see these commands below: 609 609 610 -1. 611 -11. 617 +1. 618 +11. 612 612 111. Common Commands: 613 613 614 614 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]] 615 615 616 616 617 -1. 618 -11. 624 +1. 625 +11. 619 619 111. Sensor related commands: 620 620 621 621 ==== Choose Device Type (RS485 or TTL) ==== ... ... @@ -921,13 +921,13 @@ 921 921 922 922 923 923 924 -1. 931 +1. 925 925 11. Buttons 926 926 927 927 |**Button**|**Feature** 928 928 |**RST**|Reboot RS485-BL 929 929 930 -1. 937 +1. 931 931 11. +3V3 Output 932 932 933 933 RS485-BL has a Controllable +3V3 output, user can use this output to power external sensor. ... ... @@ -945,7 +945,7 @@ 945 945 By default, the AT+3V3T=0. This is a special case, means the +3V3 output is always on at any time 946 946 947 947 948 -1. 955 +1. 949 949 11. +5V Output 950 950 951 951 RS485-BL has a Controllable +5V output, user can use this output to power external sensor. ... ... @@ -965,13 +965,13 @@ 965 965 966 966 967 967 968 -1. 975 +1. 969 969 11. LEDs 970 970 971 971 |**LEDs**|**Feature** 972 972 |**LED1**|Blink when device transmit a packet. 973 973 974 -1. 981 +1. 975 975 11. Switch Jumper 976 976 977 977 |**Switch Jumper**|**Feature** ... ... @@ -1017,7 +1017,7 @@ 1017 1017 1018 1018 1019 1019 1020 -1. 1027 +1. 1021 1021 11. Common AT Command Sequence 1022 1022 111. Multi-channel ABP mode (Use with SX1301/LG308) 1023 1023 ... ... @@ -1036,8 +1036,8 @@ 1036 1036 1037 1037 ATZ 1038 1038 1039 -1. 1040 -11. 1046 +1. 1047 +11. 1041 1041 111. Single-channel ABP mode (Use with LG01/LG02) 1042 1042 1043 1043 AT+FDR Reset Parameters to Factory Default, Keys Reserve ... ... @@ -1112,7 +1112,7 @@ 1112 1112 [[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]] 1113 1113 1114 1114 1115 -1. 1122 +1. 1116 1116 11. How to change the LoRa Frequency Bands/Region? 1117 1117 1118 1118 User can follow the introduction for [[how to upgrade image>>path:#upgrade_image]]. When download the images, choose the required image file for download. ... ... @@ -1119,7 +1119,7 @@ 1119 1119 1120 1120 1121 1121 1122 -1. 1129 +1. 1123 1123 11. How many RS485-Slave can RS485-BL connects? 1124 1124 1125 1125 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]]. ... ... @@ -1136,7 +1136,7 @@ 1136 1136 1137 1137 1138 1138 1139 -1. 1146 +1. 1140 1140 11. Why I can’t join TTN V3 in US915 /AU915 bands? 1141 1141 1142 1142 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