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, 0 added, 7 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:** ... ... @@ -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 49386 +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:165 3269403619-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,95 +419,94 @@ 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,0435 +AT+COMMAND1=11 01 1E D0,0 439 439 440 - (% style="color:red" %)AT+SEARCH1=1,1E 56 34437 +AT+SEARCH1=1,1E 56 34 441 441 442 - (% style="color:red" %)AT+DATACUT1=0,2,1~~5439 +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 49441 +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 49443 +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 36445 +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||height="513" width="716"]]469 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image019.png]] 479 479 480 -(% style="color:#4f81bd" %)**Examples: AT+DATAUP=1** 481 481 482 -Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**Multiply UPLINKs**. 483 483 473 +**Examples: AT+DATAUP=1** 474 + 475 +Compose the uplink payload with value returns in sequence and send with **Multiply UPLINKs**. 476 + 484 484 Final Payload is 485 485 486 - (% style="color:#4f81bd" %)**Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA**479 +Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA 487 487 488 488 1. Battery Info (2 bytes): Battery voltage 489 489 1. PAYVER (1 byte): Defined by AT+PAYVER 490 490 1. PAYLOAD COUNT (1 byte): Total how many uplinks of this sampling. 491 491 1. PAYLOAD# (1 byte): Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT) 492 -1. 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 485 +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 493 493 494 -[[image: 1653269916228-732.png||height="433" width="711"]]487 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image020.png]] 495 495 496 496 497 497 So totally there will be 3 uplinks for this sampling, each uplink includes 6 bytes DATA 498 498 499 -DATA1=RETURN1 Valid Value = (% style="background-color:green; color:white" %)20 20 0a 33 90 41492 +DATA1=RETURN1 Valid Value = 20 20 0a 33 90 41 500 500 501 -DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10= (%style="background-color:green; color:white" %)02 aa 05 81 0a 20494 +DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10= 02 aa 05 81 0a 20 502 502 503 -DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 = (%style="background-color:green; color:white" %)20 20 20 2d 30496 +DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 = 20 20 20 2d 30 504 504 498 + 499 + 505 505 Below are the uplink payloads: 506 506 507 -[[image: 1653270130359-810.png]]502 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image021.png]] 508 508 509 509 510 - (% style="color:red" %)**Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:**505 +Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below: 511 511 512 512 ~* For AU915/AS923 bands, if UplinkDwell time=0, max 51 bytes for each uplink ( so 51 -5 = 46 max valid date) 513 513 ... ... @@ -519,8 +519,8 @@ 519 519 520 520 521 521 522 -1. 523 -11. 517 +1. 518 +11. 524 524 111. Uplink on demand 525 525 526 526 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. ... ... @@ -533,8 +533,8 @@ 533 533 534 534 535 535 536 -1. 537 -11. 531 +1. 532 +11. 538 538 111. Uplink on Interrupt 539 539 540 540 Put the interrupt sensor between 3.3v_out and GPIO ext.[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image022.png]] ... ... @@ -548,7 +548,7 @@ 548 548 AT+INTMOD=3 Interrupt trigger by rising edge. 549 549 550 550 551 -1. 546 +1. 552 552 11. Uplink Payload 553 553 554 554 |**Size(bytes)**|**2**|**1**|**Length depends on the return from the commands** ... ... @@ -610,15 +610,15 @@ 610 610 611 611 * **Sensor Related Commands**: These commands are special designed for RS485-BL. User can see these commands below: 612 612 613 -1. 614 -11. 608 +1. 609 +11. 615 615 111. Common Commands: 616 616 617 617 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]] 618 618 619 619 620 -1. 621 -11. 615 +1. 616 +11. 622 622 111. Sensor related commands: 623 623 624 624 ==== Choose Device Type (RS485 or TTL) ==== ... ... @@ -924,13 +924,13 @@ 924 924 925 925 926 926 927 -1. 922 +1. 928 928 11. Buttons 929 929 930 930 |**Button**|**Feature** 931 931 |**RST**|Reboot RS485-BL 932 932 933 -1. 928 +1. 934 934 11. +3V3 Output 935 935 936 936 RS485-BL has a Controllable +3V3 output, user can use this output to power external sensor. ... ... @@ -948,7 +948,7 @@ 948 948 By default, the AT+3V3T=0. This is a special case, means the +3V3 output is always on at any time 949 949 950 950 951 -1. 946 +1. 952 952 11. +5V Output 953 953 954 954 RS485-BL has a Controllable +5V output, user can use this output to power external sensor. ... ... @@ -968,13 +968,13 @@ 968 968 969 969 970 970 971 -1. 966 +1. 972 972 11. LEDs 973 973 974 974 |**LEDs**|**Feature** 975 975 |**LED1**|Blink when device transmit a packet. 976 976 977 -1. 972 +1. 978 978 11. Switch Jumper 979 979 980 980 |**Switch Jumper**|**Feature** ... ... @@ -1020,7 +1020,7 @@ 1020 1020 1021 1021 1022 1022 1023 -1. 1018 +1. 1024 1024 11. Common AT Command Sequence 1025 1025 111. Multi-channel ABP mode (Use with SX1301/LG308) 1026 1026 ... ... @@ -1039,8 +1039,8 @@ 1039 1039 1040 1040 ATZ 1041 1041 1042 -1. 1043 -11. 1037 +1. 1038 +11. 1044 1044 111. Single-channel ABP mode (Use with LG01/LG02) 1045 1045 1046 1046 AT+FDR Reset Parameters to Factory Default, Keys Reserve ... ... @@ -1115,7 +1115,7 @@ 1115 1115 [[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]] 1116 1116 1117 1117 1118 -1. 1113 +1. 1119 1119 11. How to change the LoRa Frequency Bands/Region? 1120 1120 1121 1121 User can follow the introduction for [[how to upgrade image>>path:#upgrade_image]]. When download the images, choose the required image file for download. ... ... @@ -1122,7 +1122,7 @@ 1122 1122 1123 1123 1124 1124 1125 -1. 1120 +1. 1126 1126 11. How many RS485-Slave can RS485-BL connects? 1127 1127 1128 1128 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]]. ... ... @@ -1139,7 +1139,7 @@ 1139 1139 1140 1140 1141 1141 1142 -1. 1137 +1. 1143 1143 11. Why I can’t join TTN V3 in US915 /AU915 bands? 1144 1144 1145 1145 It might about the channels mapping. Please see for detail.
- 1653269551753-223.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -138.7 KB - Content
- 1653269568276-930.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -131.4 KB - Content
- 1653269593172-426.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -142.6 KB - Content
- 1653269618463-608.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -27.7 KB - Content
- 1653269759169-150.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -294.0 KB - Content
- 1653269916228-732.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -143.3 KB - Content
- 1653270130359-810.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -197.8 KB - Content