Changes for page RS485-LN – RS485 to LoRaWAN Converter User Manual
Last modified by Bei Jinggeng on 2025/01/10 15:06
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 10 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. ting1 +XWiki.Xiaoling - Content
-
... ... @@ -38,7 +38,7 @@ 38 38 ))) 39 39 40 40 ((( 41 -RS485-LN allows user to (% style="color:blue" %)**monitor / control RS485 devices**(%%) and reach extremely long ranges. It provides ultra-long range spread spectrum communication and high interference immunity whilst minimizing current consumption. It targets professional wireless sensor network applications such as irrigation systems, smart metering, smart cities, building automation, and so on. 41 +RS485-LN allows user to (% style="color:blue" %)**monitor / control RS485 devices**(%%) and reach extremely long ranges. It provides ultra-long range spread spectrum communication and high interference immunity whilst minimizing current consumption. It targets professional wireless sensor network applications such as irrigation systems, smart metering, smart cities, smartphone detection, building automation, and so on. 42 42 ))) 43 43 44 44 ((( ... ... @@ -94,6 +94,8 @@ 94 94 * Automatic RF Sense and CAD with ultra-fast AFC. 95 95 * Packet engine up to 256 bytes with CRC 96 96 97 + 98 + 97 97 == 1.3 Features == 98 98 99 99 ... ... @@ -106,6 +106,8 @@ 106 106 * Support Modbus protocol 107 107 * Support Interrupt uplink (Since hardware version v1.2) 108 108 111 + 112 + 109 109 == 1.4 Applications == 110 110 111 111 ... ... @@ -116,6 +116,8 @@ 116 116 * Smart Cities 117 117 * Smart Factory 118 118 123 + 124 + 119 119 == 1.5 Firmware Change log == 120 120 121 121 ... ... @@ -135,16 +135,6 @@ 135 135 v1.0: Release 136 136 ))) 137 137 138 - 139 -== 1.7 Pin Definitions == 140 - 141 - 142 -The following diagram shows the V1.2 hardware version. 143 - 144 -[[image:image-20240925161141-1.jpeg||height="412" width="405"]] 145 - 146 -[[image:image-20240925161157-2.jpeg||height="367" width="545"]] 147 - 148 148 149 149 ))) 150 150 ))) ... ... @@ -255,6 +255,7 @@ 255 255 (% aria-label="1652953553383-907.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:1652953553383-907.png||data-widget="image" height="514" width="724"]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %) 256 256 257 257 254 + 258 258 ((( 259 259 (% style="color:blue" %)**Step 2**(%%): Power on RS485-LN and it will auto join to the TTN V3 network. After join success, it will start to upload message to TTN V3 and user can see in the panel. 260 260 ... ... @@ -264,44 +264,38 @@ 264 264 (% aria-label="1652953568895-172.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:1652953568895-172.png||data-widget="image" height="232" width="724"]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %) 265 265 266 266 267 -== 3.3 Configure DevicetoReadRS485Sensors==264 +== 3.3 Configure Commands to read data == 268 268 269 269 270 -There are plenty of RS485 and TTL level devices in the market and each device has different commands to read the valid data. To support these devices in most flexible, RS485-LN supports flexible command set. User can use [[Dragino RS485 Tool>>url:https://www.dropbox.com/sh/us9qecn39fwt8n1/AABREdqUCzEmJMRrfuWuXasoa?dl=0]], [[AT Commands or LoRaWAN Downlink>>url:http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/RS485-LB_Waterproof_RS485UART_to_LoRaWAN_Converter/#H3.5ConfigureRS485-LBviaATorDownlink]] Command to configure how RS485-LN should read the sensor and how to handle the return from RS485 or TTL sensors. 267 +((( 268 +((( 269 +((( 270 +There are plenty of RS485 devices in the market and each device has different command to read the valid data. To support these devices in flexible, RS485-LN supports flexible command set. User can use [[AT Commands>>||anchor="H3.5ConfigureRS485-LNviaATorDownlink"]] or LoRaWAN Downlink Command to configure what commands RS485-LN should send for each sampling and how to handle the return from RS485 devices. 271 271 272 + 273 +))) 274 +))) 272 272 273 273 ((( 274 274 ((( 275 -((( 276 276 (% style="color:red" %)**Note: below description and commands are for firmware version >v1.1, if you have firmware version v1.0. Please check the [[user manual v1.0>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/&file=RS485-LN_UserManual_v1.0.1.pdf]] or upgrade the firmware to v1.1** 277 277 ))) 278 278 279 - 280 -=== 3.3.1 Method 1 ~-~- via RS485 Configure Tool === 281 - 282 - 283 -Use the RS485 Configure tool is the recommand method. Please see the instruction of how to use the tool: 284 - 285 -* **[[RS485 Configure Tool Instruction>>url:http://wiki.dragino.com/xwiki/bin/view/Main/RS485_Configure_Tool/]]** 286 - 287 -[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/RS485-LB_Waterproof_RS485UART_to_LoRaWAN_Converter/WebHome/image-20231127144411-1.png?width=494&height=368&rev=1.1||alt="image-20231127144411-1.png" height="368" width="494"]] 288 - 289 - 290 -=== 3.3.2 Method 2 ~-~- via AT Commands === 281 + 291 291 ))) 292 292 ))) 293 293 294 -=== =3.3.2.1 Configure UART settings for RS485 communication ====285 +=== 3.3.1 Configure UART settings for RS485 or TTL communication === 295 295 296 296 297 -To use RS485-LN to read data from RS485 sensors, connect the RS485-LN A/B traces to the sensors. The related commands for UART settings are: 288 +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: 298 298 299 -(% border="1" cellspacing=" 4" style="background-color:#f2f2f2; width:510px" %)300 -|=(% style="width: 126px; background-color:# 4F81BD;color:white" %)(((290 +(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:510px" %) 291 +|=(% style="width: 126px; background-color:#D9E2F3;color:#0070C0" %)((( 301 301 **AT Commands** 302 -)))|=(% style="width: 187px; background-color:# 4F81BD;color:white" %)(((293 +)))|=(% style="width: 187px; background-color:#D9E2F3;color:#0070C0" %)((( 303 303 **Description** 304 -)))|=(% style="width: 197px;background-color:# 4F81BD;color:white" %)(((295 +)))|=(% style="width: 197px;background-color:#D9E2F3;color:#0070C0" %)((( 305 305 **Example** 306 306 ))) 307 307 |(% style="width:126px" %)((( ... ... @@ -357,15 +357,17 @@ 357 357 ))) 358 358 ))) 359 359 360 -=== 3.3.3 Configure sensors === 361 361 362 362 353 +=== 3.3.2 Configure sensors === 354 + 355 + 363 363 ((( 364 364 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. 365 365 ))) 366 366 367 -(% border="1" cellspacing=" 4" style="background-color:#f2f2f2; width:510px" %)368 -|=(% style="width: 122px; background-color:# 4F81BD;color:white" %)**AT Commands**|=(% style="width: 198px; background-color:#4F81BD;color:white" %)**Description**|=(% style="width: 190px;background-color:#4F81BD;color:white" %)**Example**360 +(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:510px" %) 361 +|=(% style="width: 122px; background-color:#D9E2F3;color:#0070C0" %)**AT Commands**|=(% style="width: 198px; background-color:#D9E2F3;color:#0070C0" %)**Description**|=(% style="width: 190px;background-color:#D9E2F3;color:#0070C0" %)**Example** 369 369 |(% style="width:122px" %)AT+CFGDEV|(% style="width:196px" %)((( 370 370 ((( 371 371 This command is used to configure the RS485/TTL devices; they won’t be used during sampling. ... ... @@ -380,9 +380,11 @@ 380 380 ))) 381 381 )))|(% style="width:190px" %)AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m 382 382 383 -=== 3.3.4 Configure read commands for each sampling === 384 384 385 385 378 +=== 3.3.3 Configure read commands for each sampling === 379 + 380 + 386 386 ((( 387 387 During each sampling, we need confirm what commands we need to send to the RS485 sensors to read data. After the RS485 sensors send back the value, it normally include some bytes and we only need a few from them for a shorten payload. 388 388 ... ... @@ -424,20 +424,6 @@ 424 424 In the RS485-LN, we should use this command AT+COMMAND1=01 03 0B B8 00 02,1 for the same. 425 425 426 426 427 -If a single command exceeds 14 bytes, you can use the command splicing function. 428 - 429 -When AT+CMDDLx=1, the commands of AT+COMMANDx and AT+COMMAND(x+1) will be merged. 430 - 431 - 432 -**Examples:** To send 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F data it should be configured: 433 - 434 - AT+COMMAND1=00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D,0 435 - 436 - AT+COMMAND1=1 437 - 438 - AT+COMMAND2=0E 0F,0 439 - 440 - 441 441 (% style="color:#037691" %)**AT+DATACUTx **(%%)**: **This command defines how to handle the return from AT+COMMANDx, max return length is 100 bytes. 442 442 443 443 (% border="1" style="background-color:#f2f2f2; width:510px" %) ... ... @@ -471,7 +471,7 @@ 471 471 472 472 ))) 473 473 474 -=== 3.3. 5Compose the uplink payload ===455 +=== 3.3.4 Compose the uplink payload === 475 475 476 476 477 477 ((( ... ... @@ -556,7 +556,7 @@ 556 556 (% aria-label="1654157178836-407.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:1654157178836-407.png||data-widget="image"]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %) 557 557 558 558 559 -=== 3.3. 6Uplink on demand ===540 +=== 3.3.5 Uplink on demand === 560 560 561 561 562 562 Except uplink periodically, RS485-LN is able to uplink on demand. The server send downlink command to RS485-LN and RS485 will uplink data base on the command. ... ... @@ -568,87 +568,27 @@ 568 568 (% style="color:#4472c4" %)** 0xA8 command**(%%): Send a command to RS485-LN and uplink the output from sensors. 569 569 570 570 571 -=== 3.3. 7Uplink on Interrupt ===552 +=== 3.3.6 Uplink on Interrupt === 572 572 573 573 574 - 575 575 RS485-LN support external Interrupt uplink since hardware v1.2 release. 576 576 577 -(% aria-label="1654157342174-798.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:1654157342174-798.png||data-widget="image"]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]] 578 578 558 +(% aria-label="1654157342174-798.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:1654157342174-798.png||data-widget="image"]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %) 579 579 580 - ==== 3.3.7.1 Set InterruptMode====560 +Connect the Interrupt pin to RS485-LN INT port and connect the GND pin to V- port. When there is a high voltage (Max 24v) on INT pin. Device will send an uplink packet. 581 581 582 582 583 -Before using the interrupt function of the **INT** pin, users can set the interrupt triggering mode as required. 584 - 585 -(% style="color:blue" %)**AT command:** 586 - 587 -* (% style="color:#037691" %)**AT+INTMOD **(%%) ~/~/ Set the trigger interrupt mode 588 - 589 -* (% style="color:#037691" %)**AT+INTMOD=0 **(%%) ~/~/ Disable Interrupt 590 - 591 -* (% style="color:#037691" %)**AT+INTMOD=1 **(%%) ~/~/ Trigger by rising and falling edge 592 - 593 -* (% style="color:#037691" %)**AT+INTMOD=2 **(%%) ~/~/ Trigger by falling edge **(default)** 594 - 595 -* (% style="color:#037691" %)**AT+INTMOD=3 **(%%) ~/~/ Trigger by rising edge 596 - 597 -(% style="color:blue" %)**Downlink Commands: **(% style="color:#037691" %)**0x06** 598 - 599 -Format: Command Code (0x06) followed by 3 bytes. 600 - 601 -Example1: Downlink Payload: **06 00 00 01 **~/~/ AT+INTMOD=1 602 - 603 -Example2: Downlink Payload: **06 00 00 03 **~/~/AT+INTMOD=3 604 - 605 - 606 -==== 3.3.7.2 Practical application ==== 607 - 608 - 609 -The following uses the default interrupt triggering mode (% style="color:blue" %)**(AT+INTMOD=2)**(%%) as an example to show the interrupt function of (% style="color:blue" %)**INT**(%%): 610 - 611 -When a high voltage is given to the INT pin and then the level of the (% style="color:blue" %)**INT**(%%) pin changes from high to low, the interrupt is triggered by a falling edge and the RS485-LN sends an uplink data. 612 - 613 -(% style="color:red" %)**Note: The level that triggers the interrupt ranges from 3.3V to 24V. Generally, it is recommended to use less than 12V.** 614 - 615 -**Example:** 616 - 617 -* Use a dry contact to connect the (% style="color:blue" %)**INT**(%%) pin and (% style="color:blue" %)**VIN+**(%%) pin of the RS485-LN. 618 - 619 -When the dry contact is closed, INT and VIN+ conduct and INT is high. 620 - 621 -Disconnecting the dry contact, the level of the INT pin changes from high to low, triggering an interrupt (triggered along the falling edge), and the RS485-LN sends an uplink data. 622 - 623 -[[image:image-20240925174124-5.jpeg||height="439" width="703"]] 624 - 625 -* Use a regulated power supply or a wet contact to connect the 485-LN to trigger the interruption.(This section uses a regulated power supply as an example.) 626 - 627 -The positive pole of the stabilized power supply is connected to the (% style="color:blue" %)**INT**(%%) pin of RS485-LN, and the negative pole of the stabilized power supply is connected to the (% style="color:blue" %)**VIN-**(%%) pin of RS485-LN. 628 - 629 -When the regulated power supply is operating, a high voltage is given to the INT pin and the INT level is high. When the regulated power supply is turned off, the level of the INT pin changes from 630 - 631 -high to low, at which time an interrupt is triggered (triggered along the falling edge), and the device will send an uplink data. 632 - 633 -[[image:image-20240925173243-4.jpeg||height="404" width="900"]] 634 - 635 -* Example of interrupt data in TTN. 636 - 637 -The first byte of the payload of the interrupted packet is (% style="color:blue" %)**0x81**(%%). 638 - 639 -[[image:image-20240925181010-1.png||height="348" width="953"]] 640 - 641 - 642 642 == 3.4 Uplink Payload == 643 643 644 644 645 -(% border="1" cellspacing=" 4" style="background-color:#f2f2f2; width:510px" %)646 -|(% style="background-color:# 4f81bd;white; width:70px" %)(((647 - **Size(bytes)**648 -)))|(% style="background-color:# 4f81bd; color:white; width:80px" %)**1**|(% style="background-color:#4f81bd; color:white; width:360px" %)(((566 +(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:510px" %) 567 +|=(% scope="row" style="width: 70px;background-color:#D9E2F3;color:#0070C0" %)((( 568 +Size(bytes) 569 +)))|(% style="background-color:#d9e2f3; color:#0070c0; width:80px" %)**1**|(% style="background-color:#d9e2f3; color:#0070c0; width:360px" %)((( 649 649 **Length depends on the return from the commands** 650 650 ))) 651 -|(% style="width:90px" %)((( 572 +|=(% style="width: 90px;" %)((( 652 652 Value 653 653 )))|(% style="width:114px" %)((( 654 654 PAYLOAD_VER ... ... @@ -660,9 +660,13 @@ 660 660 provided in the LoRaWAN server. 661 661 ))) 662 662 663 -(% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]] (%%)Below is the decoder for the first 3 bytes. The rest bytes are dynamic depends on different RS485 sensors.584 +(% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]] 664 664 586 +(% title="Click and drag to resize" %) 665 665 588 +Below is the decoder for the first 3 bytes. The rest bytes are dynamic depends on different RS485 sensors. 589 + 590 + 666 666 == 3.5 Configure RS485-LN via AT or Downlink == 667 667 668 668 ... ... @@ -807,21 +807,31 @@ 807 807 ))) 808 808 809 809 ((( 810 -(% style="color:blue" %)**Example 2:** (%%) 735 +(% style="color:blue" %)**Example 2:** (%%) ~-~-> Configure with requesting uplink and original downlink command (**YY=FF**) 811 811 ))) 812 812 813 813 ((( 814 - CheckTTLSensorurn:739 +User in IoT server send a downlink command: (% style="color:#4f81bd" %)**A8 01 06 0A 08 00 04 00 01 YY** 815 815 ))) 816 816 817 817 ((( 743 + 744 +))) 745 + 818 818 ((( 819 -[[image:http://8.211.40.43/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/test/WebHome/1654132684752-193.png?rev=1.1||alt="1654132684752-193.png"]](% title="Click and drag to resize" %) 747 +((( 748 +RS485-LN got this downlink command and send (% style="color:#4f81bd" %)**0A 08 00 04 00 01 **(%%)to Modbus network. One of the RS485 sensor in the network send back Modbus reply **0A 08 00 04 00 00**. RS485-LN get this reply and combine with the original downlink command and uplink. The uplink message is: **A8** (% style="color:#4f81bd" %)**0A 08 00 04 00 **(% style="color:red" %)**01 06** ** **(% style="color:green" %)**0A 08 00 04 00 00** 820 820 ))) 750 + 751 + 821 821 ))) 822 822 754 +((( 755 + (% aria-label="1654159460680-153.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:1654159460680-153.png||data-widget="image"]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %) 756 +))) 823 823 824 824 759 + 825 825 ==== (% style="color:blue" %)**Set Payload version**(%%) ==== 826 826 827 827 ... ... @@ -989,13 +989,8 @@ 989 989 990 990 (% aria-label="image-20220602165351-7.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:image-20220602165351-7.png||data-widget="image"]](% title="Click and drag to resize" %) 991 991 992 -* ((( 993 -(% style="color:#037691" %)**Downlink Command:** 994 -))) 995 995 996 -**~ (% style="color:#4472c4" %)A9 aa(%%)** ~-~-> Same as AT+MBFUN=aa 997 997 998 - 999 999 ==== (% style="color:blue" %)**RS485 command timeout**(%%) ==== 1000 1000 1001 1001 ... ... @@ -1084,8 +1084,6 @@ 1084 1084 (% style="color:#4472c4" %)** 0xAD 01** (%%) **~-~->** Same as AT+DATAUP=1 ~/~/Each uplink is sent to the server one after the other as it is segmented. 1085 1085 1086 1086 1087 -(Since firmware v1.4.0) 1088 - 1089 1089 * ((( 1090 1090 (% style="color:#037691" %)** AT Command:** 1091 1091 ))) ... ... @@ -1102,44 +1102,7 @@ 1102 1102 Each uplink is sent to the server at 20-second intervals when segmented. 1103 1103 1104 1104 1105 -==== (% style="color:blue" %)**Cut data separation processing(Since Version 1.4.2)**(%%) ==== 1106 1106 1107 - 1108 -AT+NEWLINE command, which only takes effect when AT+DATAUP=1 or AT+DATAUP=1, timeout. 1109 - 1110 -When not set, each part of AT+DATAUP is sent according to the maximum number of bytes of DR. 1111 - 1112 -When setting, each part of AT+DATAUP is sent according to the value set by AT+NEWLINE. 1113 - 1114 - 1115 -* ((( 1116 -(% style="color:#037691" %)** AT Command:** 1117 -))) 1118 - 1119 -(% style="color:#4472c4" %)//**AT+NEWLINE=ALL**//(%%)// //The data cut out by each AT+COMMANDx command is sent separately as an uplink. 1120 - 1121 -(% style="color:#4472c4" %)//**AT+NEWLINE=ALL**//(%%)// equal: (% style="color:#4472c4" %)**AT+NEWLINE=1+2+3+4+5+6+7+8+9+10+11+12+13+14+15**// 1122 - 1123 - 1124 -(% style="color:#4472c4" %)//**AT+NEWLINE=a+b+c**//(%%)// //The data returned by all commands is divided into three parts, COMMAND(1~~a) is the first part, COMMAND(a+1~~b) is the second part,COMMAND(b+1~~c) is the third part. 1125 - 1126 - 1127 -(% style="color:#4472c4" %)//**AT+NEWLINE=NULL**//(%%)// //Turn off the functionality of this AT command. 1128 - 1129 - 1130 -* ((( 1131 -(% style="color:#037691" %)** Downlink Payload:** 1132 -))) 1133 - 1134 -//AT+NEWLINE=ALL ~-~--> (% style="color:#4472c4" %)**0xAC 01**// 1135 - 1136 -// AT+NEWLINE= NULL ~-~--> (% style="color:#4472c4" %)**0xAC 00**// 1137 - 1138 -//AT+NEWLINE= a+b+c ~-~--> (% style="color:#4472c4" %)**0xAC number of bytes a b c**// 1139 - 1140 -//AT+NEWLINE= 1+5+15 ~-~--> (% style="color:#4472c4" %)**0xAC 03 01 05 0F**// 1141 - 1142 - 1143 1143 ==== (% style="color:blue" %)**Manually trigger an Uplink**(%%) ==== 1144 1144 1145 1145 ... ... @@ -1447,10 +1447,12 @@ 1447 1447 To enable the listening mode, use can run the command (% style="color:#4472c4" %)** AT+RXMODE**. 1448 1448 ))) 1449 1449 1450 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %) 1451 -|=(% style="width: 156px; background-color:#4F81BD;color:white" %)((( 1341 + 1342 + 1343 +(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:510px" %) 1344 +|=(% style="width: 156px; background-color:#D9E2F3;color:#0070C0" %)((( 1452 1452 **Command example** 1453 -)))|=(% style="width: 355px; background-color:# 4F81BD;color:white" %)(((1346 +)))|=(% style="width: 355px; background-color:#D9E2F3;color:#0070C0" %)((( 1454 1454 **Function** 1455 1455 ))) 1456 1456 |(% style="width:156px" %)((( ... ... @@ -1529,19 +1529,23 @@ 1529 1529 1530 1530 1531 1531 (% border="1.5" cellspacing="4" style="background-color:#f2f2f2; width:430px" %) 1532 -|=(% style="width: 50px;background-color:# 4F81BD;color:white" %)**Button**|=(% style="width: 380px;background-color:#4F81BD;color:white" %)**Feature**1425 +|=(% style="width: 50px;background-color:#D9E2F3;color:#0070C0" %)**Button**|=(% style="width: 380px;background-color:#D9E2F3;color:#0070C0" %)**Feature** 1533 1533 |(% style="width:50px" %)ACT|(% style="width:361px" %)If RS485 joined in network, press this button for more than 1 second, RS485 will upload a packet, and the SYS LED will give a (% style="color:blue" %)**Blue blink** 1534 1534 |(% style="width:50px" %)RST|(% style="width:361px" %)Reboot RS485 1535 1535 |(% style="width:50px" %)PRO|(% style="width:361px" %)Use for upload image, see [[How to Update Image>>||anchor="H6.1Howtoupgradetheimage3F"]] 1536 1536 1430 + 1431 + 1537 1537 == 3.8 LEDs == 1538 1538 1539 1539 1540 1540 (% border="1.5" cellspacing="4" style="background-color:#f2f2f2; width:430px" %) 1541 -|=(% style="width: 50px;background-color:# 4F81BD;color:white" %)**LEDs**|=(% style="width: 380px;background-color:#4F81BD;color:white" %)**Feature**1436 +|=(% style="width: 50px;background-color:#D9E2F3;color:#0070C0" %)**LEDs**|=(% style="width: 380px;background-color:#D9E2F3;color:#0070C0" %)**Feature** 1542 1542 |PWR|Always on if there is power 1543 1543 |SYS|After device is powered on, the SYS will (% style="color:green" %)**fast blink in GREEN**(%%) for 5 times, means RS485-LN start to join LoRaWAN network. If join success, SYS will be (% style="color:green" %)**on GREEN for 5 seconds** (%%)**. **SYS will (% style="color:green" %)**blink Blue**(%%) on every upload and (% style="color:green" %)**blink Green**(%%) once receive a downlink message. 1544 1544 1440 + 1441 + 1545 1545 = 4. Case Study = 1546 1546 1547 1547 ... ... @@ -1700,12 +1700,6 @@ 1700 1700 (% aria-label="image-20220602175912-14.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:image-20220602175912-14.png||data-widget="image"]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %) 1701 1701 1702 1702 1703 - 1704 -(% style="color:red" %)**Users can select the new burning software STM32Cubeprogramer for firmware upgrade and follow the same connection steps to enter burning mode (until SYS LED is RED ON):** 1705 - 1706 -[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H4.2.FirmwareupgradeusingSTM32Cubeprogramer>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H4.2.FirmwareupgradeusingSTM32Cubeprogramer]] 1707 - 1708 - 1709 1709 (% style="color:red" %)**Notice**: **In case user has lost the program cable. User can hand made one from a 3.5mm cable. The pin mapping is:** 1710 1710 1711 1711 (% aria-label="image-20220602175638-10.png image widget" contenteditable="false" role="region" tabindex="-1" %)[[image:image-20220602175638-10.png||data-widget="image"]](% style="background-image:url(http://wiki.dragino.com/xwiki/webjars/wiki%3Axwiki/application-ckeditor-webjar/1.61/plugins/widget/images/handle.png); background:rgba(220,220,220,0.5); display:none" %)[[image:data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==||draggable="true" height="15" role="presentation" title="Click and drag to move" width="15"]](% title="Click and drag to resize" %) ... ... @@ -1755,7 +1755,7 @@ 1755 1755 1. Check if Modbus-MTU return back the expected result to RS485-LN. 1756 1756 1. If both b) and c) has issue, we can compare PC’s output and RS485-LN output. 1757 1757 1758 -[[image:image-202 40816112950-1.png||height="382" width="731"]]1649 +[[image:image-20221130104310-1.png||height="380" width="680"]] 1759 1759 1760 1760 1761 1761 Example Connection: ... ... @@ -1858,17 +1858,6 @@ 1858 1858 The decoder for RS485-LN needs to be written by yourself. Because the sensor to which the user is connected is custom, the read device data bytes also need custom parsing, so there is no universal decoder. We can only provide [[templates>>https://github.com/dragino/dragino-end-node-decoder/tree/main/RS485-LN]] for decoders (no intermediate data parsing part involved) 1859 1859 1860 1860 1861 -== 6.9 How to configure RS485 commands more conveniently? == 1862 - 1863 - 1864 -Dragino has developed an application for the RS485 series of products. 1865 - 1866 -It can help you configure RS485 sensors more conveniently 1867 -Please refer to the link below for specific usage: 1868 - 1869 -[[RS485 Configure Tool - DRAGINO>>url:http://wiki.dragino.com/xwiki/bin/view/Main/RS485_Configure_Tool/#HTableofContentsFF1A]] 1870 - 1871 - 1872 1872 = 7. Trouble Shooting = 1873 1873 1874 1874 == 7.1 Downlink doesn't work, how to solve it? == ... ... @@ -1877,36 +1877,12 @@ 1877 1877 Please see this link for debug: [[LoRaWAN Communication Debug>>doc:Main.LoRaWAN Communication Debug.WebHome]] 1878 1878 1879 1879 1880 -== 7.2 Why customerscan't join TTN V3 in US915 /AU915 bands? ==1760 +== 7.2 Why I can't join TTN V3 in US915 /AU915 bands? == 1881 1881 1882 1882 1883 1883 It might about the channels mapping. Please see for detail: [[Notice of Frequency band>>doc:Main.LoRaWAN Communication Debug.WebHome||anchor="H2.NoticeofUS9152FCN4702FAU915Frequencyband"]] 1884 1884 1885 1885 1886 -== 7.3 Why can't customers see the device's data in the server when the data is too long? == 1887 - 1888 -This is due to the limitation of the lorawan protocol, and the fixed DR needs to be adjusted to improve this problem. 1889 - 1890 -Please refer to the following link for the number of bytes limited by different frequencies and different DRs in the lorawan protocol 1891 - 1892 -[[lora-alliance.org/wp-content/uploads/2021/05/RP002-1.0.3-FINAL-1.pdf>>url:https://lora-alliance.org/wp-content/uploads/2021/05/RP002-1.0.3-FINAL-1.pdf]] 1893 - 1894 -Example: 1895 - 1896 -[[image:image-20240620145456-1.png]] 1897 - 1898 -Please refer to the following command to fix DR 1899 - 1900 -AT+ADR=0 1901 - 1902 -AT+DR=3 1903 - 1904 -Downlink command: 1905 - 1906 -[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20AT%20Commands%20and%20Downlink%20Command/#H7.4DataRate>>http://wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20AT%20Commands%20and%20Downlink%20Command/#H7.4DataRate]] 1907 - 1908 - 1909 - 1910 1910 = 8. Order Info = 1911 1911 1912 1912 ... ... @@ -1925,6 +1925,8 @@ 1925 1925 * (% style="color:red" %)**RU864**(%%): frequency bands RU864 1926 1926 * (% style="color:red" %)**KZ865**(%%): frequency bands KZ865 1927 1927 1784 + 1785 + 1928 1928 = 9. Packing Info = 1929 1929 1930 1930 ... ... @@ -1941,6 +1941,8 @@ 1941 1941 * Package Size / pcs : 14.5 x 8 x 5 cm 1942 1942 * Weight / pcs : 170g 1943 1943 1802 + 1803 + 1944 1944 = 10. FCC Caution for RS485LN-US915 = 1945 1945 1946 1946
- image-20240620145456-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -50.3 KB - Content
- image-20240816112950-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.karry - Size
-
... ... @@ -1,1 +1,0 @@ 1 -230.3 KB - Content
- image-20240925144019-1.jpeg
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.ting - Size
-
... ... @@ -1,1 +1,0 @@ 1 -1.6 MB - Content
- image-20240925145611-2.jpeg
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.ting - Size
-
... ... @@ -1,1 +1,0 @@ 1 -606.6 KB - Content
- image-20240925161141-1.jpeg
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.ting - Size
-
... ... @@ -1,1 +1,0 @@ 1 -1.6 MB - Content
- image-20240925161157-2.jpeg
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.ting - Size
-
... ... @@ -1,1 +1,0 @@ 1 -606.6 KB - Content
- image-20240925164510-3.jpeg
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.ting - Size
-
... ... @@ -1,1 +1,0 @@ 1 -850.5 KB - Content
- image-20240925173243-4.jpeg
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.ting - Size
-
... ... @@ -1,1 +1,0 @@ 1 -1.0 MB - Content
- image-20240925174124-5.jpeg
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.ting - Size
-
... ... @@ -1,1 +1,0 @@ 1 -857.8 KB - Content
- image-20240925181010-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.ting - Size
-
... ... @@ -1,1 +1,0 @@ 1 -60.5 KB - Content