Last modified by Karry Zhuang on 2025/03/06 16:34
<
From version < 22.1 >
edited by Xiaoling
on 2022/05/23 09:10
To version < 30.2 >
edited by Xiaoling
on 2022/05/23 09:40
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -41,17 +41,17 @@
41 41  **Hardware System:**
42 42  
43 43  * STM32L072CZT6 MCU
44 -* SX1276/78 Wireless Chip
44 +* SX1276/78 Wireless Chip 
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:**
52 52  
53 53  * RS485
54 -* Power Input 7~~ 24V DC.
54 +* Power Input 7~~ 24V DC. 
55 55  
56 56  **LoRa Spec:**
57 57  
... ... @@ -138,24 +138,29 @@
138 138  [[image:1653268155545-638.png||height="334" width="724"]]
139 139  
140 140  (((
141 -The RS485-BL in this example connected to two RS485 devices for demonstration, user can connect to other RS485 devices via the same method.
142 -)))
141 +The RS485-LN in this example connected to two RS485 devices for demonstration, user can connect to other RS485 devices via the same method. The connection is as below:
143 143  
143 +485A+ and 485B- of the sensor are connected to RS485A and RA485B of RS485-LN respectively.
144 +
145 +[[image:1653268227651-549.png||height="592" width="720"]]
146 +
144 144  (((
145 -The LG308 is already set to connect to [[TTN V3 network >>url:https://www.thethingsnetwork.org/]]. So what we need to now is only configure the TTN V3:
148 +The LG308 is already set to connect to [[TTN V3 network >>path:eu1.cloud.thethings.network/]]. So what we need to now is only configure the TTN V3:
146 146  )))
147 147  
148 148  (((
149 -**Step 1**: Create a device in TTN V3 with the OTAA keys from RS485-BL.
152 +**Step 1**: Create a device in TTN V3 with the OTAA keys from RS485-LN.
150 150  )))
151 151  
152 152  (((
153 -Each RS485-BL is shipped with a sticker with unique device EUI:
156 +Each RS485-LN is shipped with a sticker with unique device EUI:
154 154  )))
158 +)))
155 155  
156 156  [[image:1652953462722-299.png]]
157 157  
158 158  (((
163 +(((
159 159  User can enter this key in their LoRaWAN Server portal. Below is TTN V3 screen shot:
160 160  )))
161 161  
... ... @@ -162,13 +162,11 @@
162 162  (((
163 163  Add APP EUI in the application.
164 164  )))
170 +)))
165 165  
166 -
167 -
168 -
169 169  [[image:image-20220519174512-1.png]]
170 170  
171 -[[image:image-20220519174512-2.png||height="328" width="731"]]
174 +[[image:image-20220519174512-2.png||height="323" width="720"]]
172 172  
173 173  [[image:image-20220519174512-3.png||height="556" width="724"]]
174 174  
... ... @@ -184,7 +184,7 @@
184 184  
185 185  
186 186  (((
187 -**Step 2**: Power on RS485-BL 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.
190 +**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.
188 188  )))
189 189  
190 190  [[image:1652953568895-172.png||height="232" width="724"]]
... ... @@ -192,23 +192,19 @@
192 192  == 3.3 Configure Commands to read data ==
193 193  
194 194  (((
195 -There are plenty of RS485 and TTL level devices in the market and each device has different command to read the valid data. To support these devices in flexible, RS485-BL supports flexible command set. User can use [[AT Commands or LoRaWAN Downlink>>path:#AT_COMMAND]] Command to configure how RS485-BL should read the sensor and how to handle the return from RS485 or TTL sensors.
198 +(((
199 +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>>path:#AT_COMMAND]] or LoRaWAN Downlink Command to configure what commands RS485-LN should send for each sampling and how to handle the return from RS485 devices.
196 196  )))
197 197  
202 +(((
203 +(% 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
204 +)))
205 +)))
206 +
198 198  === 3.3.1 onfigure UART settings for RS485 or TTL communication ===
199 199  
200 -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:
201 201  
202 -**~1. RS485-MODBUS mode:**
203 -
204 -AT+MOD=1 ~/~/ Support RS485-MODBUS type sensors. User can connect multiply RS485 , Modbus sensors to the A / B pins.
205 -
206 -**2. TTL mode:**
207 -
208 -AT+MOD=2 ~/~/ Support TTL Level sensors, User can connect one TTL Sensor to the TXD/RXD/GND pins.
209 -
210 -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.
211 -
212 212  (% border="1" style="background-color:#ffffcc; color:green; width:795px" %)
213 213  |(((
214 214  **AT Commands**
... ... @@ -233,13 +233,7 @@
233 233  |(((
234 234  AT+PARITY
235 235  )))|(% style="width:285px" %)(((
236 -(((
237 237  Set UART parity (for RS485 connection)
238 -)))
239 -
240 -(((
241 -Default Value is: no parity.
242 -)))
243 243  )))|(% style="width:347px" %)(((
244 244  (((
245 245  AT+PARITY=0
... ... @@ -257,7 +257,7 @@
257 257  )))
258 258  
259 259  (((
260 -Default Value is: 1bit.
253 +
261 261  )))
262 262  )))|(% style="width:347px" %)(((
263 263  (((
... ... @@ -276,12 +276,10 @@
276 276  === 3.3.2 Configure sensors ===
277 277  
278 278  (((
279 -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**.
280 -)))
281 -
282 282  (((
283 -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.
284 284  )))
275 +)))
285 285  
286 286  (% border="1" style="background-color:#ffffcc; color:green; width:806px" %)
287 287  |**AT Commands**|(% style="width:418px" %)**Description**|(% style="width:256px" %)**Example**
... ... @@ -293,8 +293,6 @@
293 293  mm: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
294 294  )))|(% style="width:256px" %)AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
295 295  
296 -Detail of AT+CFGDEV command see [[AT+CFGDEV detail>>path:#AT_CFGDEV]].
297 -
298 298  === 3.3.3 Configure read commands for each sampling ===
299 299  
300 300  (((
... ... @@ -376,11 +376,17 @@
376 376  **m: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command**
377 377  )))
378 378  
368 +(((
379 379  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 +)))
380 380  
372 +(((
381 381  In the RS485-BL, we should use this command AT+COMMAND1=01 03 0B B8 00 02,1 for the same.
374 +)))
382 382  
376 +(((
383 383  **AT+SEARCHx**: This command defines how to handle the return from AT+COMMANDx.
378 +)))
384 384  
385 385  (% border="1" class="table-bordered" %)
386 386  |(((
... ... @@ -392,26 +392,24 @@
392 392  
393 393  )))
394 394  
395 -Examples:
390 +**Examples:**
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
392 +~1. For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
398 398  
399 399  If we set AT+SEARCH1=1,1E 56 34.      (max 5 bytes for prefix)
400 400  
401 -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**
402 402  
403 -[[image:1652954654347-831.png]]
398 +[[image:1653269403619-508.png]]
404 404  
400 +2. For a return string from AT+COMMAND1:  16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
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
407 -
408 408  If we set AT+SEARCH1=2, 1E 56 34+31 00 49
409 409  
410 -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**
411 411  
412 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image014.png]]
406 +[[image:1653269438444-278.png]]
413 413  
414 -
415 415  **AT+DATACUTx : **This command defines how to handle the return from AT+COMMANDx, max return length is 45 bytes.
416 416  
417 417  |(((
... ... @@ -426,76 +426,79 @@
426 426  
427 427  * Grab bytes:
428 428  
429 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image015.png]]
422 +[[image:1653269551753-223.png||height="311" width="717"]]
430 430  
431 431  * Grab a section.
432 432  
433 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image016.png]]
426 +[[image:1653269568276-930.png||height="325" width="718"]]
434 434  
435 435  * Grab different sections.
436 436  
437 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image017.png]]
430 +[[image:1653269593172-426.png||height="303" width="725"]]
438 438  
432 +(% style="color:red" %)**Note:**
439 439  
440 -Note:
441 -
442 442  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.
443 443  
444 444  Example:
445 445  
446 -AT+COMMAND1=11 01 1E D0,0
438 +(% style="color:red" %)AT+COMMAND1=11 01 1E D0,0
447 447  
448 -AT+SEARCH1=1,1E 56 34
440 +(% style="color:red" %)AT+SEARCH1=1,1E 56 34
449 449  
450 -AT+DATACUT1=0,2,1~~5
442 +(% style="color:red" %)AT+DATACUT1=0,2,1~~5
451 451  
452 -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
453 453  
454 -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
455 455  
456 -Valid payload after DataCUT command: 2e 30 58 5f 36
448 +(% style="color:red" %)Valid payload after DataCUT command: 2e 30 58 5f 36
457 457  
458 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image018.png]]
450 +[[image:1653269618463-608.png]]
459 459  
452 +=== 3.3.4 Compose the uplink payload ===
460 460  
461 -
462 -
463 -1.
464 -11.
465 -111. Compose the uplink payload
466 -
454 +(((
467 467  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 +)))
468 468  
458 +(((
459 +(% style="color:#4f81bd" %)**Examples: AT+DATAUP=0**
460 +)))
469 469  
470 -**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 +)))
471 471  
472 -Compose the uplink payload with value returns in sequence and send with **A SIGNLE UPLINK**.
473 -
466 +(((
474 474  Final Payload is
468 +)))
475 475  
476 -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 +)))
477 477  
474 +(((
478 478  Where PAYVER is defined by AT+PAYVER, below is an example screen shot.
476 +)))
479 479  
480 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image019.png]]
478 +[[image:1653269759169-150.png||height="513" width="716"]]
481 481  
480 +(% style="color:#4f81bd" %)**Examples: AT+DATAUP=1**
482 482  
482 +Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**Multiply UPLINKs**.
483 483  
484 -**Examples: AT+DATAUP=1**
485 -
486 -Compose the uplink payload with value returns in sequence and send with **Multiply UPLINKs**.
487 -
488 488  Final Payload is
489 489  
490 -Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA
486 +(% style="color:#4f81bd" %)**Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA**
491 491  
492 492  1. Battery Info (2 bytes): Battery voltage
493 493  1. PAYVER (1 byte): Defined by AT+PAYVER
494 494  1. PAYLOAD COUNT (1 byte): Total how many uplinks of this sampling.
495 495  1. PAYLOAD# (1 byte): Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT)
496 -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
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
497 497  
498 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image020.png]]
494 +[[image:1653269916228-732.png]]
499 499  
500 500  
501 501  So totally there will be 3 uplinks for this sampling, each uplink includes 6 bytes DATA
... ... @@ -525,8 +525,8 @@
525 525  
526 526  
527 527  
528 -1.
529 -11.
524 +1.
525 +11.
530 530  111. Uplink on demand
531 531  
532 532  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.
... ... @@ -539,8 +539,8 @@
539 539  
540 540  
541 541  
542 -1.
543 -11.
538 +1.
539 +11.
544 544  111. Uplink on Interrupt
545 545  
546 546  Put the interrupt sensor between 3.3v_out and GPIO ext.[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image022.png]]
... ... @@ -554,7 +554,7 @@
554 554  AT+INTMOD=3  Interrupt trigger by rising edge.
555 555  
556 556  
557 -1.
553 +1.
558 558  11. Uplink Payload
559 559  
560 560  |**Size(bytes)**|**2**|**1**|**Length depends on the return from the commands**
... ... @@ -616,15 +616,15 @@
616 616  
617 617  * **Sensor Related Commands**: These commands are special designed for RS485-BL.  User can see these commands below:
618 618  
619 -1.
620 -11.
615 +1.
616 +11.
621 621  111. Common Commands:
622 622  
623 623  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]]
624 624  
625 625  
626 -1.
627 -11.
622 +1.
623 +11.
628 628  111. Sensor related commands:
629 629  
630 630  ==== Choose Device Type (RS485 or TTL) ====
... ... @@ -930,13 +930,13 @@
930 930  
931 931  
932 932  
933 -1.
929 +1.
934 934  11. Buttons
935 935  
936 936  |**Button**|**Feature**
937 937  |**RST**|Reboot RS485-BL
938 938  
939 -1.
935 +1.
940 940  11. +3V3 Output
941 941  
942 942  RS485-BL has a Controllable +3V3 output, user can use this output to power external sensor.
... ... @@ -954,7 +954,7 @@
954 954  By default, the AT+3V3T=0. This is a special case, means the +3V3 output is always on at any time
955 955  
956 956  
957 -1.
953 +1.
958 958  11. +5V Output
959 959  
960 960  RS485-BL has a Controllable +5V output, user can use this output to power external sensor.
... ... @@ -974,13 +974,13 @@
974 974  
975 975  
976 976  
977 -1.
973 +1.
978 978  11. LEDs
979 979  
980 980  |**LEDs**|**Feature**
981 981  |**LED1**|Blink when device transmit a packet.
982 982  
983 -1.
979 +1.
984 984  11. Switch Jumper
985 985  
986 986  |**Switch Jumper**|**Feature**
... ... @@ -1026,7 +1026,7 @@
1026 1026  
1027 1027  
1028 1028  
1029 -1.
1025 +1.
1030 1030  11. Common AT Command Sequence
1031 1031  111. Multi-channel ABP mode (Use with SX1301/LG308)
1032 1032  
... ... @@ -1045,8 +1045,8 @@
1045 1045  
1046 1046  ATZ
1047 1047  
1048 -1.
1049 -11.
1044 +1.
1045 +11.
1050 1050  111. Single-channel ABP mode (Use with LG01/LG02)
1051 1051  
1052 1052  AT+FDR   Reset Parameters to Factory Default, Keys Reserve
... ... @@ -1121,7 +1121,7 @@
1121 1121  [[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]]
1122 1122  
1123 1123  
1124 -1.
1120 +1.
1125 1125  11. How to change the LoRa Frequency Bands/Region?
1126 1126  
1127 1127  User can follow the introduction for [[how to upgrade image>>path:#upgrade_image]]. When download the images, choose the required image file for download.
... ... @@ -1128,7 +1128,7 @@
1128 1128  
1129 1129  
1130 1130  
1131 -1.
1127 +1.
1132 1132  11. How many RS485-Slave can RS485-BL connects?
1133 1133  
1134 1134  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]].
... ... @@ -1145,7 +1145,7 @@
1145 1145  
1146 1146  
1147 1147  
1148 -1.
1144 +1.
1149 1149  11. Why I can’t join TTN V3 in US915 /AU915 bands?
1150 1150  
1151 1151  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
1653269916228-732.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +143.3 KB
Content

Applications

Navigation

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