Last modified by Karry Zhuang on 2025/03/06 16:34
<
From version < 36.1 >
edited by Xiaoling
on 2022/06/02 15:50
To version < 32.2 >
edited by Xiaoling
on 2022/06/02 15:22
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -18,30 +18,28 @@
18 18  
19 19  (((
20 20  (((
21 -The Dragino RS485-LN is a (% style="color:blue" %)**RS485 to LoRaWAN Converter**(%%). It converts the RS485 signal into LoRaWAN wireless signal which simplify the IoT installation and reduce the installation/maintaining cost.
21 +The Dragino RS485-LN is a **RS485 to LoRaWAN Converter**. It converts the RS485 signal into LoRaWAN wireless signal which simplify the IoT installation and reduce the installation/maintaining cost.
22 22  )))
23 23  
24 24  (((
25 -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.
25 +RS485-LN allows user to **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.
26 26  )))
27 27  
28 28  (((
29 -(% style="color:blue" %)**For data uplink**(%%), RS485-LN sends user-defined commands to RS485 devices and gets the return from the RS485 devices. RS485-LN will process these returns according to user-define rules to get the final payload and upload to LoRaWAN server.
29 +**For data uplink**, RS485-LN sends user-defined commands to RS485 devices and gets the return from the RS485 devices. RS485-LN will process these returns according to user-define rules to get the final payload and upload to LoRaWAN server.
30 30  )))
31 31  
32 32  (((
33 -(% style="color:blue" %)**For data downlink**(%%), RS485-LN runs in LoRaWAN Class C. When there downlink commands from LoRaWAN server, RS485-LN will forward the commands from LoRaWAN server to RS485 devices.
33 +**For data downlink**, RS485-LN runs in LoRaWAN Class C. When there downlink commands from LoRaWAN server, RS485-LN will forward the commands from LoRaWAN server to RS485 devices.
34 34  
35 -(% style="color:blue" %)**Demo Dashboard for RS485-LN**(%%) connect to two energy meters: [[https:~~/~~/app.datacake.de/dashboard/d/58844a26-378d-4c5a-aaf5-b5b5b153447a>>url:https://app.datacake.de/dashboard/d/58844a26-378d-4c5a-aaf5-b5b5b153447a]]
35 +**Demo Dashboard for RS485-LN** connect to two energy meters: [[https:~~/~~/app.datacake.de/dashboard/d/58844a26-378d-4c5a-aaf5-b5b5b153447a>>url:https://app.datacake.de/dashboard/d/58844a26-378d-4c5a-aaf5-b5b5b153447a]]
36 36  )))
37 37  )))
38 38  
39 39  [[image:1653267211009-519.png||height="419" width="724"]]
40 40  
41 -
42 42  == 1.2 Specifications ==
43 43  
44 -
45 45  **Hardware System:**
46 46  
47 47  * STM32L072CZT6 MCU
... ... @@ -48,6 +48,8 @@
48 48  * SX1276/78 Wireless Chip 
49 49  * Power Consumption (exclude RS485 device):
50 50  ** Idle: 32mA@12v
49 +
50 +*
51 51  ** 20dB Transmit: 65mA@12v
52 52  
53 53  **Interface for Model:**
... ... @@ -100,7 +100,6 @@
100 100  
101 101  [[RS485-LN Image files – Download link and Change log>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/]]
102 102  
103 -
104 104  == 1.6 Hardware Change log ==
105 105  
106 106  (((
... ... @@ -108,8 +108,6 @@
108 108  v1.2: Add External Interrupt Pin.
109 109  
110 110  v1.0: Release
111 -
112 -
113 113  )))
114 114  )))
115 115  
... ... @@ -126,8 +126,6 @@
126 126  )))
127 127  
128 128  [[image:1653268091319-405.png]]
129 -
130 -
131 131  )))
132 132  
133 133  = 3. Operation Mode =
... ... @@ -136,8 +136,6 @@
136 136  
137 137  (((
138 138  The RS485-LN is configured as LoRaWAN OTAA Class C mode by default. It has OTAA keys to join network. To connect a local LoRaWAN network, user just need to input the OTAA keys in the network server and power on the RS485-LN. It will auto join the network via OTAA.
139 -
140 -
141 141  )))
142 142  
143 143  == 3.2 Example to join LoRaWAN network ==
... ... @@ -146,15 +146,10 @@
146 146  
147 147  [[image:1653268155545-638.png||height="334" width="724"]]
148 148  
149 -
150 150  (((
151 -(((
152 152  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:
153 -)))
154 154  
155 -(((
156 156  485A+ and 485B- of the sensor are connected to RS485A and RA485B of RS485-LN respectively.
157 -)))
158 158  
159 159  [[image:1653268227651-549.png||height="592" width="720"]]
160 160  
... ... @@ -206,7 +206,6 @@
206 206  
207 207  [[image:1652953568895-172.png||height="232" width="724"]]
208 208  
209 -
210 210  == 3.3 Configure Commands to read data ==
211 211  
212 212  (((
... ... @@ -216,8 +216,6 @@
216 216  
217 217  (((
218 218  (% 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
219 -
220 -
221 221  )))
222 222  )))
223 223  
... ... @@ -225,19 +225,19 @@
225 225  
226 226  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:
227 227  
228 -(% border="1" style="background-color:#ffffcc; color:green; width:782px" %)
229 -|(% style="width:128px" %)(((
213 +(% border="1" style="background-color:#ffffcc; color:green; width:795px" %)
214 +|(((
230 230  **AT Commands**
231 -)))|(% style="width:305px" %)(((
216 +)))|(% style="width:285px" %)(((
232 232  **Description**
233 -)))|(% style="width:346px" %)(((
218 +)))|(% style="width:347px" %)(((
234 234  **Example**
235 235  )))
236 -|(% style="width:128px" %)(((
221 +|(((
237 237  AT+BAUDR
238 -)))|(% style="width:305px" %)(((
223 +)))|(% style="width:285px" %)(((
239 239  Set the baud rate (for RS485 connection). Default Value is: 9600.
240 -)))|(% style="width:346px" %)(((
225 +)))|(% style="width:347px" %)(((
241 241  (((
242 242  AT+BAUDR=9600
243 243  )))
... ... @@ -246,11 +246,11 @@
246 246  Options: (1200,2400,4800,14400,19200,115200)
247 247  )))
248 248  )))
249 -|(% style="width:128px" %)(((
234 +|(((
250 250  AT+PARITY
251 -)))|(% style="width:305px" %)(((
236 +)))|(% style="width:285px" %)(((
252 252  Set UART parity (for RS485 connection)
253 -)))|(% style="width:346px" %)(((
238 +)))|(% style="width:347px" %)(((
254 254  (((
255 255  AT+PARITY=0
256 256  )))
... ... @@ -259,9 +259,9 @@
259 259  Option: 0: no parity, 1: odd parity, 2: even parity
260 260  )))
261 261  )))
262 -|(% style="width:128px" %)(((
247 +|(((
263 263  AT+STOPBIT
264 -)))|(% style="width:305px" %)(((
249 +)))|(% style="width:285px" %)(((
265 265  (((
266 266  Set serial stopbit (for RS485 connection)
267 267  )))
... ... @@ -269,7 +269,7 @@
269 269  (((
270 270  
271 271  )))
272 -)))|(% style="width:346px" %)(((
257 +)))|(% style="width:347px" %)(((
273 273  (((
274 274  AT+STOPBIT=0 for 1bit
275 275  )))
... ... @@ -304,34 +304,77 @@
304 304  === 3.3.3 Configure read commands for each sampling ===
305 305  
306 306  (((
307 -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.
292 +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.
293 +)))
308 308  
295 +(((
296 +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.
297 +)))
298 +
299 +(((
309 309  To save the LoRaWAN network bandwidth, we might need to read data from different sensors and combine their valid value into a short payload.
301 +)))
310 310  
303 +(((
311 311  This section describes how to achieve above goals.
305 +)))
312 312  
313 -During each sampling, the RS485-LN can support 15 commands to read sensors. And combine the return to one or several uplink payloads.
307 +(((
308 +During each sampling, the RS485-BL can support 15 commands to read sensors. And combine the return to one or several uplink payloads.
309 +)))
314 314  
311 +(((
312 +**Command from RS485-BL to Sensor:**
313 +)))
315 315  
316 -**Each RS485 commands include two parts:**
315 +(((
316 +RS485-BL can send out pre-set max 15 strings via **AT+COMMAD1**, **ATCOMMAND2**,…, to **AT+COMMANDF** . All commands are of same grammar.
317 +)))
317 317  
318 -~1. What commands RS485-LN will send to the RS485 sensors. There are total 15 commands from **AT+COMMAD1**, **ATCOMMAND2**,…, to **AT+COMMANDF**. All commands are of same grammar.
319 +(((
320 +**Handle return from sensors to RS485-BL**:
321 +)))
319 319  
320 -2. How to get wanted value the from RS485 sensors returns from by 1). There are total 15 AT Commands to handle the return, commands are **AT+DATACUT1**,**AT+DATACUT2**,…, **AT+DATACUTF** corresponding to the commands from 1). All commands are of same grammar.
323 +(((
324 +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**
325 +)))
321 321  
322 -3. 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
327 +* (((
328 +**AT+DATACUT**
329 +)))
323 323  
331 +(((
332 +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.
333 +)))
324 324  
335 +* (((
336 +**AT+SEARCH**
337 +)))
338 +
339 +(((
340 +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.
341 +)))
342 +
343 +(((
344 +**Define wait timeout:**
345 +)))
346 +
347 +(((
348 +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
349 +)))
350 +
351 +(((
325 325  After we got the valid value from each RS485 commands, we need to combine them together with the command **AT+DATAUP**.
353 +)))
326 326  
355 +**Examples:**
327 327  
328 328  Below are examples for the how above AT Commands works.
329 329  
359 +**AT+COMMANDx : **This command will be sent to RS485/TTL devices during each sampling, Max command length is 14 bytes. The grammar is:
330 330  
331 -**AT+COMMANDx : **This command will be sent to RS485 devices during each sampling, Max command length is 14 bytes. The grammar is:
332 -
333 -(% border="1" style="background-color:#4bacc6; color:white; width:499px" %)
334 -|(% style="width:496px" %)(((
361 +(% border="1" class="table-bordered" %)
362 +|(((
335 335  **AT+COMMANDx=xx xx xx xx xx xx xx xx xx xx xx xx,m**
336 336  
337 337  **xx xx xx xx xx xx xx xx xx xx xx xx: The RS485 command to be sent**
... ... @@ -339,15 +339,49 @@
339 339  **m: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command**
340 340  )))
341 341  
370 +(((
342 342  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.
372 +)))
343 343  
344 -In the RS485-LN, we should use this command AT+COMMAND1=01 03 0B B8 00 02,1 for the same.
374 +(((
375 +In the RS485-BL, we should use this command AT+COMMAND1=01 03 0B B8 00 02,1 for the same.
376 +)))
345 345  
378 +(((
379 +**AT+SEARCHx**: This command defines how to handle the return from AT+COMMANDx.
380 +)))
346 346  
382 +(% border="1" class="table-bordered" %)
383 +|(((
384 +**AT+SEARCHx=aa,xx xx xx xx xx**
385 +
386 +* **aa: 1: prefix match mode; 2: prefix and suffix match mode**
387 +* **xx xx xx xx xx: match string. Max 5 bytes for prefix and 5 bytes for suffix**
388 +
389 +
390 +)))
391 +
392 +**Examples:**
393 +
394 +~1. For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
395 +
396 +If we set AT+SEARCH1=1,1E 56 34.      (max 5 bytes for prefix)
397 +
398 +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**
399 +
400 +[[image:1653269403619-508.png]]
401 +
402 +2. For a return string from AT+COMMAND1:  16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
403 +
404 +If we set AT+SEARCH1=2, 1E 56 34+31 00 49
405 +
406 +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**
407 +
408 +[[image:1653269438444-278.png]]
409 +
347 347  **AT+DATACUTx : **This command defines how to handle the return from AT+COMMANDx, max return length is 45 bytes.
348 348  
349 -(% border="1" style="background-color:#4bacc6; color:white; width:725px" %)
350 -|(% style="width:722px" %)(((
412 +|(((
351 351  **AT+DATACUTx=a,b,c**
352 352  
353 353  * **a: length for the return of AT+COMMAND**
... ... @@ -355,37 +355,48 @@
355 355  * **c: define the position for valid value.  **
356 356  )))
357 357  
358 -**Examples:**
420 +Examples:
359 359  
360 360  * Grab bytes:
361 361  
362 -[[image:image-20220602153621-1.png]]
424 +[[image:1653269551753-223.png||height="311" width="717"]]
363 363  
364 -
365 365  * Grab a section.
366 366  
367 -[[image:image-20220602153621-2.png]]
428 +[[image:1653269568276-930.png||height="325" width="718"]]
368 368  
369 -
370 370  * Grab different sections.
371 371  
372 -[[image:image-20220602153621-3.png]]
432 +[[image:1653269593172-426.png||height="303" width="725"]]
373 373  
374 -
375 -)))
434 +(% style="color:red" %)**Note:**
376 376  
436 +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.
437 +
438 +Example:
439 +
440 +(% style="color:red" %)AT+COMMAND1=11 01 1E D0,0
441 +
442 +(% style="color:red" %)AT+SEARCH1=1,1E 56 34
443 +
444 +(% style="color:red" %)AT+DATACUT1=0,2,1~~5
445 +
446 +(% style="color:red" %)Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
447 +
448 +(% style="color:red" %)String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49
449 +
450 +(% style="color:red" %)Valid payload after DataCUT command: 2e 30 58 5f 36
451 +
452 +[[image:1653269618463-608.png]]
453 +
377 377  === 3.3.4 Compose the uplink payload ===
378 378  
379 379  (((
380 380  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.**
381 -
382 -
383 383  )))
384 384  
385 385  (((
386 -(% style="color:#037691" %)**Examples: AT+DATAUP=0**
387 -
388 -
461 +(% style="color:#4f81bd" %)**Examples: AT+DATAUP=0**
389 389  )))
390 390  
391 391  (((
... ... @@ -406,10 +406,8 @@
406 406  
407 407  [[image:1653269759169-150.png||height="513" width="716"]]
408 408  
482 +(% style="color:#4f81bd" %)**Examples: AT+DATAUP=1**
409 409  
410 -(% style="color:#037691" %)**Examples: AT+DATAUP=1**
411 -
412 -
413 413  Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**Multiply UPLINKs**.
414 414  
415 415  Final Payload is
... ... @@ -460,8 +460,8 @@
460 460  
461 461  
462 462  
463 -1.
464 -11.
534 +1.
535 +11.
465 465  111. Uplink on Interrupt
466 466  
467 467  Put the interrupt sensor between 3.3v_out and GPIO ext.[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image022.png]]
... ... @@ -475,7 +475,7 @@
475 475  AT+INTMOD=3  Interrupt trigger by rising edge.
476 476  
477 477  
478 -1.
549 +1.
479 479  11. Uplink Payload
480 480  
481 481  |**Size(bytes)**|**2**|**1**|**Length depends on the return from the commands**
... ... @@ -537,15 +537,15 @@
537 537  
538 538  * **Sensor Related Commands**: These commands are special designed for RS485-BL.  User can see these commands below:
539 539  
540 -1.
541 -11.
611 +1.
612 +11.
542 542  111. Common Commands:
543 543  
544 544  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]]
545 545  
546 546  
547 -1.
548 -11.
618 +1.
619 +11.
549 549  111. Sensor related commands:
550 550  
551 551  ==== Choose Device Type (RS485 or TTL) ====
... ... @@ -851,13 +851,13 @@
851 851  
852 852  
853 853  
854 -1.
925 +1.
855 855  11. Buttons
856 856  
857 857  |**Button**|**Feature**
858 858  |**RST**|Reboot RS485-BL
859 859  
860 -1.
931 +1.
861 861  11. +3V3 Output
862 862  
863 863  RS485-BL has a Controllable +3V3 output, user can use this output to power external sensor.
... ... @@ -875,7 +875,7 @@
875 875  By default, the AT+3V3T=0. This is a special case, means the +3V3 output is always on at any time
876 876  
877 877  
878 -1.
949 +1.
879 879  11. +5V Output
880 880  
881 881  RS485-BL has a Controllable +5V output, user can use this output to power external sensor.
... ... @@ -895,13 +895,13 @@
895 895  
896 896  
897 897  
898 -1.
969 +1.
899 899  11. LEDs
900 900  
901 901  |**LEDs**|**Feature**
902 902  |**LED1**|Blink when device transmit a packet.
903 903  
904 -1.
975 +1.
905 905  11. Switch Jumper
906 906  
907 907  |**Switch Jumper**|**Feature**
... ... @@ -947,7 +947,7 @@
947 947  
948 948  
949 949  
950 -1.
1021 +1.
951 951  11. Common AT Command Sequence
952 952  111. Multi-channel ABP mode (Use with SX1301/LG308)
953 953  
... ... @@ -966,8 +966,8 @@
966 966  
967 967  ATZ
968 968  
969 -1.
970 -11.
1040 +1.
1041 +11.
971 971  111. Single-channel ABP mode (Use with LG01/LG02)
972 972  
973 973  AT+FDR   Reset Parameters to Factory Default, Keys Reserve
... ... @@ -1042,7 +1042,7 @@
1042 1042  [[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]]
1043 1043  
1044 1044  
1045 -1.
1116 +1.
1046 1046  11. How to change the LoRa Frequency Bands/Region?
1047 1047  
1048 1048  User can follow the introduction for [[how to upgrade image>>path:#upgrade_image]]. When download the images, choose the required image file for download.
... ... @@ -1049,7 +1049,7 @@
1049 1049  
1050 1050  
1051 1051  
1052 -1.
1123 +1.
1053 1053  11. How many RS485-Slave can RS485-BL connects?
1054 1054  
1055 1055  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]].
... ... @@ -1066,7 +1066,7 @@
1066 1066  
1067 1067  
1068 1068  
1069 -1.
1140 +1.
1070 1070  11. Why I can’t join TTN V3 in US915 /AU915 bands?
1071 1071  
1072 1072  It might about the channels mapping. Please see for detail.
image-20220602153621-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -23.4 KB
Content
image-20220602153621-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -22.2 KB
Content
image-20220602153621-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -22.3 KB
Content
image-20220602155039-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -24.6 KB
Content

Applications

Navigation

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