Last modified by Karry Zhuang on 2025/03/06 16:34
<
From version < 32.6 >
edited by Xiaoling
on 2022/06/02 15:25
To version < 35.2 >
edited by Xiaoling
on 2022/06/02 15:44
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -76,6 +76,8 @@
76 76  * Automatic RF Sense and CAD with ultra-fast AFC.
77 77  * Packet engine up to 256 bytes with CRC.
78 78  
79 +
80 +
79 79  == 1.3 Features ==
80 80  
81 81  * LoRaWAN Class A & Class C protocol (default Class C)
... ... @@ -87,6 +87,8 @@
87 87  * Support Modbus protocol
88 88  * Support Interrupt uplink (Since hardware version v1.2)
89 89  
92 +
93 +
90 90  == 1.4 Applications ==
91 91  
92 92  * Smart Buildings & Home Automation
... ... @@ -96,10 +96,13 @@
96 96  * Smart Cities
97 97  * Smart Factory
98 98  
103 +
104 +
99 99  == 1.5 Firmware Change log ==
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  
109 +
103 103  == 1.6 Hardware Change log ==
104 104  
105 105  (((
... ... @@ -107,6 +107,8 @@
107 107  v1.2: Add External Interrupt Pin.
108 108  
109 109  v1.0: Release
117 +
118 +
110 110  )))
111 111  )))
112 112  
... ... @@ -123,6 +123,8 @@
123 123  )))
124 124  
125 125  [[image:1653268091319-405.png]]
135 +
136 +
126 126  )))
127 127  
128 128  = 3. Operation Mode =
... ... @@ -131,6 +131,8 @@
131 131  
132 132  (((
133 133  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.
145 +
146 +
134 134  )))
135 135  
136 136  == 3.2 Example to join LoRaWAN network ==
... ... @@ -139,10 +139,15 @@
139 139  
140 140  [[image:1653268155545-638.png||height="334" width="724"]]
141 141  
155 +
142 142  (((
157 +(((
143 143  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:
159 +)))
144 144  
161 +(((
145 145  485A+ and 485B- of the sensor are connected to RS485A and RA485B of RS485-LN respectively.
163 +)))
146 146  
147 147  [[image:1653268227651-549.png||height="592" width="720"]]
148 148  
... ... @@ -194,6 +194,7 @@
194 194  
195 195  [[image:1652953568895-172.png||height="232" width="724"]]
196 196  
215 +
197 197  == 3.3 Configure Commands to read data ==
198 198  
199 199  (((
... ... @@ -203,6 +203,8 @@
203 203  
204 204  (((
205 205  (% 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
225 +
226 +
206 206  )))
207 207  )))
208 208  
... ... @@ -210,19 +210,19 @@
210 210  
211 211  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:
212 212  
213 -(% border="1" style="background-color:#ffffcc; color:green; width:795px" %)
214 -|(((
234 +(% border="1" style="background-color:#ffffcc; color:green; width:782px" %)
235 +|(% style="width:128px" %)(((
215 215  **AT Commands**
216 -)))|(% style="width:285px" %)(((
237 +)))|(% style="width:305px" %)(((
217 217  **Description**
218 -)))|(% style="width:347px" %)(((
239 +)))|(% style="width:346px" %)(((
219 219  **Example**
220 220  )))
221 -|(((
242 +|(% style="width:128px" %)(((
222 222  AT+BAUDR
223 -)))|(% style="width:285px" %)(((
244 +)))|(% style="width:305px" %)(((
224 224  Set the baud rate (for RS485 connection). Default Value is: 9600.
225 -)))|(% style="width:347px" %)(((
246 +)))|(% style="width:346px" %)(((
226 226  (((
227 227  AT+BAUDR=9600
228 228  )))
... ... @@ -231,11 +231,11 @@
231 231  Options: (1200,2400,4800,14400,19200,115200)
232 232  )))
233 233  )))
234 -|(((
255 +|(% style="width:128px" %)(((
235 235  AT+PARITY
236 -)))|(% style="width:285px" %)(((
257 +)))|(% style="width:305px" %)(((
237 237  Set UART parity (for RS485 connection)
238 -)))|(% style="width:347px" %)(((
259 +)))|(% style="width:346px" %)(((
239 239  (((
240 240  AT+PARITY=0
241 241  )))
... ... @@ -244,9 +244,9 @@
244 244  Option: 0: no parity, 1: odd parity, 2: even parity
245 245  )))
246 246  )))
247 -|(((
268 +|(% style="width:128px" %)(((
248 248  AT+STOPBIT
249 -)))|(% style="width:285px" %)(((
270 +)))|(% style="width:305px" %)(((
250 250  (((
251 251  Set serial stopbit (for RS485 connection)
252 252  )))
... ... @@ -254,7 +254,7 @@
254 254  (((
255 255  
256 256  )))
257 -)))|(% style="width:347px" %)(((
278 +)))|(% style="width:346px" %)(((
258 258  (((
259 259  AT+STOPBIT=0 for 1bit
260 260  )))
... ... @@ -268,6 +268,8 @@
268 268  )))
269 269  )))
270 270  
292 +
293 +
271 271  === 3.3.2 Configure sensors ===
272 272  
273 273  (((
... ... @@ -286,80 +286,41 @@
286 286  mm: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
287 287  )))|(% style="width:256px" %)AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
288 288  
289 -=== 3.3.3 Configure read commands for each sampling ===
290 290  
291 -(((
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 -)))
294 294  
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 -)))
314 +=== 3.3.3 Configure read commands for each sampling ===
298 298  
299 299  (((
317 +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.
318 +
300 300  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 -)))
302 302  
303 -(((
304 304  This section describes how to achieve above goals.
305 -)))
306 306  
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 -)))
323 +During each sampling, the RS485-LN can support 15 commands to read sensors. And combine the return to one or several uplink payloads.
310 310  
311 -(((
312 -**Command from RS485-BL to Sensor:**
313 -)))
314 314  
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 -)))
326 +**Each RS485 commands include two parts:**
318 318  
319 -(((
320 -**Handle return from sensors to RS485-BL**:
321 -)))
328 +~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.
322 322  
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 -)))
330 +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.
326 326  
327 -* (((
328 -**AT+DATACUT**
329 -)))
332 +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
330 330  
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 -)))
334 +**AT+CMDDL1=1000** to send the open time to 1000ms
334 334  
335 -* (((
336 -**AT+SEARCH**
337 -)))
338 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 -(((
352 352  After we got the valid value from each RS485 commands, we need to combine them together with the command **AT+DATAUP**.
353 -)))
354 354  
355 -**Examples:**
356 356  
357 357  Below are examples for the how above AT Commands works.
358 358  
359 -**AT+COMMANDx : **This command will be sent to RS485/TTL devices during each sampling, Max command length is 14 bytes. The grammar is:
360 360  
361 -(% border="1" class="table-bordered" %)
362 -|(((
343 +**AT+COMMANDx : **This command will be sent to RS485 devices during each sampling, Max command length is 14 bytes. The grammar is:
344 +
345 +(% border="1" style="background-color:#4bacc6; color:white; width:499px" %)
346 +|(% style="width:496px" %)(((
363 363  **AT+COMMANDx=xx xx xx xx xx xx xx xx xx xx xx xx,m**
364 364  
365 365  **xx xx xx xx xx xx xx xx xx xx xx xx: The RS485 command to be sent**
... ... @@ -367,90 +367,40 @@
367 367  **m: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command**
368 368  )))
369 369  
370 -(((
371 371  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 -)))
373 373  
374 -(((
375 -In the RS485-BL, we should use this command AT+COMMAND1=01 03 0B B8 00 02,1 for the same.
376 -)))
356 +In the RS485-LN, we should use this command AT+COMMAND1=01 03 0B B8 00 02,1 for the same.
377 377  
378 -(((
379 -**AT+SEARCHx**: This command defines how to handle the return from AT+COMMANDx.
380 -)))
381 381  
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 -
410 410  **AT+DATACUTx : **This command defines how to handle the return from AT+COMMANDx, max return length is 45 bytes.
411 411  
412 -|(((
361 +(% border="1" style="background-color:#4bacc6; color:white; width:725px" %)
362 +|(% style="width:722px" %)(((
413 413  **AT+DATACUTx=a,b,c**
414 414  
415 415  * **a: length for the return of AT+COMMAND**
416 416  * **b:1: grab valid value by byte, max 6 bytes. 2: grab valid value by bytes section, max 3 sections.**
417 -* **c: define the position for valid value.  **
367 +* **c: define the position for valid value. **
418 418  )))
419 419  
420 -Examples:
421 421  
371 +**Examples:**
372 +
422 422  * Grab bytes:
423 423  
424 -[[image:1653269551753-223.png||height="311" width="717"]]
375 +[[image:image-20220602153621-1.png]]
425 425  
377 +
426 426  * Grab a section.
427 427  
428 -[[image:1653269568276-930.png||height="325" width="718"]]
380 +[[image:image-20220602153621-2.png]]
429 429  
382 +
430 430  * Grab different sections.
431 431  
432 -[[image:1653269593172-426.png||height="303" width="725"]]
385 +[[image:image-20220602153621-3.png]]
386 +)))
433 433  
434 -(% style="color:red" %)**Note:**
435 -
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 -
454 454  === 3.3.4 Compose the uplink payload ===
455 455  
456 456  (((
image-20220602153621-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +23.4 KB
Content
image-20220602153621-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +22.2 KB
Content
image-20220602153621-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +22.3 KB
Content

Applications

Navigation

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