Last modified by Karry Zhuang on 2025/03/06 16:34
<
From version < 32.4 >
edited by Xiaoling
on 2022/06/02 15:24
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
... ... @@ -41,6 +41,7 @@
41 41  
42 42  == 1.2 Specifications ==
43 43  
44 +
44 44  **Hardware System:**
45 45  
46 46  * STM32L072CZT6 MCU
... ... @@ -47,8 +47,6 @@
47 47  * SX1276/78 Wireless Chip 
48 48  * Power Consumption (exclude RS485 device):
49 49  ** Idle: 32mA@12v
50 -
51 -*
52 52  ** 20dB Transmit: 65mA@12v
53 53  
54 54  **Interface for Model:**
... ... @@ -77,6 +77,8 @@
77 77  * Automatic RF Sense and CAD with ultra-fast AFC.
78 78  * Packet engine up to 256 bytes with CRC.
79 79  
79 +
80 +
80 80  == 1.3 Features ==
81 81  
82 82  * LoRaWAN Class A & Class C protocol (default Class C)
... ... @@ -88,6 +88,8 @@
88 88  * Support Modbus protocol
89 89  * Support Interrupt uplink (Since hardware version v1.2)
90 90  
92 +
93 +
91 91  == 1.4 Applications ==
92 92  
93 93  * Smart Buildings & Home Automation
... ... @@ -97,10 +97,13 @@
97 97  * Smart Cities
98 98  * Smart Factory
99 99  
103 +
104 +
100 100  == 1.5 Firmware Change log ==
101 101  
102 102  [[RS485-LN Image files – Download link and Change log>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/]]
103 103  
109 +
104 104  == 1.6 Hardware Change log ==
105 105  
106 106  (((
... ... @@ -108,6 +108,8 @@
108 108  v1.2: Add External Interrupt Pin.
109 109  
110 110  v1.0: Release
117 +
118 +
111 111  )))
112 112  )))
113 113  
... ... @@ -124,6 +124,8 @@
124 124  )))
125 125  
126 126  [[image:1653268091319-405.png]]
135 +
136 +
127 127  )))
128 128  
129 129  = 3. Operation Mode =
... ... @@ -132,6 +132,8 @@
132 132  
133 133  (((
134 134  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 +
135 135  )))
136 136  
137 137  == 3.2 Example to join LoRaWAN network ==
... ... @@ -140,10 +140,15 @@
140 140  
141 141  [[image:1653268155545-638.png||height="334" width="724"]]
142 142  
155 +
143 143  (((
157 +(((
144 144  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 +)))
145 145  
161 +(((
146 146  485A+ and 485B- of the sensor are connected to RS485A and RA485B of RS485-LN respectively.
163 +)))
147 147  
148 148  [[image:1653268227651-549.png||height="592" width="720"]]
149 149  
... ... @@ -195,6 +195,7 @@
195 195  
196 196  [[image:1652953568895-172.png||height="232" width="724"]]
197 197  
215 +
198 198  == 3.3 Configure Commands to read data ==
199 199  
200 200  (((
... ... @@ -204,6 +204,8 @@
204 204  
205 205  (((
206 206  (% 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 +
207 207  )))
208 208  )))
209 209  
... ... @@ -211,19 +211,19 @@
211 211  
212 212  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:
213 213  
214 -(% border="1" style="background-color:#ffffcc; color:green; width:795px" %)
215 -|(((
234 +(% border="1" style="background-color:#ffffcc; color:green; width:782px" %)
235 +|(% style="width:128px" %)(((
216 216  **AT Commands**
217 -)))|(% style="width:285px" %)(((
237 +)))|(% style="width:305px" %)(((
218 218  **Description**
219 -)))|(% style="width:347px" %)(((
239 +)))|(% style="width:346px" %)(((
220 220  **Example**
221 221  )))
222 -|(((
242 +|(% style="width:128px" %)(((
223 223  AT+BAUDR
224 -)))|(% style="width:285px" %)(((
244 +)))|(% style="width:305px" %)(((
225 225  Set the baud rate (for RS485 connection). Default Value is: 9600.
226 -)))|(% style="width:347px" %)(((
246 +)))|(% style="width:346px" %)(((
227 227  (((
228 228  AT+BAUDR=9600
229 229  )))
... ... @@ -232,11 +232,11 @@
232 232  Options: (1200,2400,4800,14400,19200,115200)
233 233  )))
234 234  )))
235 -|(((
255 +|(% style="width:128px" %)(((
236 236  AT+PARITY
237 -)))|(% style="width:285px" %)(((
257 +)))|(% style="width:305px" %)(((
238 238  Set UART parity (for RS485 connection)
239 -)))|(% style="width:347px" %)(((
259 +)))|(% style="width:346px" %)(((
240 240  (((
241 241  AT+PARITY=0
242 242  )))
... ... @@ -245,9 +245,9 @@
245 245  Option: 0: no parity, 1: odd parity, 2: even parity
246 246  )))
247 247  )))
248 -|(((
268 +|(% style="width:128px" %)(((
249 249  AT+STOPBIT
250 -)))|(% style="width:285px" %)(((
270 +)))|(% style="width:305px" %)(((
251 251  (((
252 252  Set serial stopbit (for RS485 connection)
253 253  )))
... ... @@ -255,7 +255,7 @@
255 255  (((
256 256  
257 257  )))
258 -)))|(% style="width:347px" %)(((
278 +)))|(% style="width:346px" %)(((
259 259  (((
260 260  AT+STOPBIT=0 for 1bit
261 261  )))
... ... @@ -269,6 +269,8 @@
269 269  )))
270 270  )))
271 271  
292 +
293 +
272 272  === 3.3.2 Configure sensors ===
273 273  
274 274  (((
... ... @@ -287,80 +287,41 @@
287 287  mm: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
288 288  )))|(% style="width:256px" %)AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
289 289  
290 -=== 3.3.3 Configure read commands for each sampling ===
291 291  
292 -(((
293 -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.
294 -)))
295 295  
296 -(((
297 -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.
298 -)))
314 +=== 3.3.3 Configure read commands for each sampling ===
299 299  
300 300  (((
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 +
301 301  To save the LoRaWAN network bandwidth, we might need to read data from different sensors and combine their valid value into a short payload.
302 -)))
303 303  
304 -(((
305 305  This section describes how to achieve above goals.
306 -)))
307 307  
308 -(((
309 -During each sampling, the RS485-BL can support 15 commands to read sensors. And combine the return to one or several uplink payloads.
310 -)))
323 +During each sampling, the RS485-LN can support 15 commands to read sensors. And combine the return to one or several uplink payloads.
311 311  
312 -(((
313 -**Command from RS485-BL to Sensor:**
314 -)))
315 315  
316 -(((
317 -RS485-BL can send out pre-set max 15 strings via **AT+COMMAD1**, **ATCOMMAND2**,…, to **AT+COMMANDF** . All commands are of same grammar.
318 -)))
326 +**Each RS485 commands include two parts:**
319 319  
320 -(((
321 -**Handle return from sensors to RS485-BL**:
322 -)))
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.
323 323  
324 -(((
325 -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**
326 -)))
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.
327 327  
328 -* (((
329 -**AT+DATACUT**
330 -)))
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
331 331  
332 -(((
333 -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.
334 -)))
334 +**AT+CMDDL1=1000** to send the open time to 1000ms
335 335  
336 -* (((
337 -**AT+SEARCH**
338 -)))
339 339  
340 -(((
341 -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.
342 -)))
343 -
344 -(((
345 -**Define wait timeout:**
346 -)))
347 -
348 -(((
349 -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
350 -)))
351 -
352 -(((
353 353  After we got the valid value from each RS485 commands, we need to combine them together with the command **AT+DATAUP**.
354 -)))
355 355  
356 -**Examples:**
357 357  
358 358  Below are examples for the how above AT Commands works.
359 359  
360 -**AT+COMMANDx : **This command will be sent to RS485/TTL devices during each sampling, Max command length is 14 bytes. The grammar is:
361 361  
362 -(% border="1" class="table-bordered" %)
363 -|(((
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" %)(((
364 364  **AT+COMMANDx=xx xx xx xx xx xx xx xx xx xx xx xx,m**
365 365  
366 366  **xx xx xx xx xx xx xx xx xx xx xx xx: The RS485 command to be sent**
... ... @@ -368,90 +368,40 @@
368 368  **m: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command**
369 369  )))
370 370  
371 -(((
372 372  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.
373 -)))
374 374  
375 -(((
376 -In the RS485-BL, we should use this command AT+COMMAND1=01 03 0B B8 00 02,1 for the same.
377 -)))
356 +In the RS485-LN, we should use this command AT+COMMAND1=01 03 0B B8 00 02,1 for the same.
378 378  
379 -(((
380 -**AT+SEARCHx**: This command defines how to handle the return from AT+COMMANDx.
381 -)))
382 382  
383 -(% border="1" class="table-bordered" %)
384 -|(((
385 -**AT+SEARCHx=aa,xx xx xx xx xx**
386 -
387 -* **aa: 1: prefix match mode; 2: prefix and suffix match mode**
388 -* **xx xx xx xx xx: match string. Max 5 bytes for prefix and 5 bytes for suffix**
389 -
390 -
391 -)))
392 -
393 -**Examples:**
394 -
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 -
397 -If we set AT+SEARCH1=1,1E 56 34.      (max 5 bytes for prefix)
398 -
399 -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**
400 -
401 -[[image:1653269403619-508.png]]
402 -
403 -2. For a return string from AT+COMMAND1:  16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
404 -
405 -If we set AT+SEARCH1=2, 1E 56 34+31 00 49
406 -
407 -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**
408 -
409 -[[image:1653269438444-278.png]]
410 -
411 411  **AT+DATACUTx : **This command defines how to handle the return from AT+COMMANDx, max return length is 45 bytes.
412 412  
413 -|(((
361 +(% border="1" style="background-color:#4bacc6; color:white; width:725px" %)
362 +|(% style="width:722px" %)(((
414 414  **AT+DATACUTx=a,b,c**
415 415  
416 416  * **a: length for the return of AT+COMMAND**
417 417  * **b:1: grab valid value by byte, max 6 bytes. 2: grab valid value by bytes section, max 3 sections.**
418 -* **c: define the position for valid value.  **
367 +* **c: define the position for valid value. **
419 419  )))
420 420  
421 -Examples:
422 422  
371 +**Examples:**
372 +
423 423  * Grab bytes:
424 424  
425 -[[image:1653269551753-223.png||height="311" width="717"]]
375 +[[image:image-20220602153621-1.png]]
426 426  
377 +
427 427  * Grab a section.
428 428  
429 -[[image:1653269568276-930.png||height="325" width="718"]]
380 +[[image:image-20220602153621-2.png]]
430 430  
382 +
431 431  * Grab different sections.
432 432  
433 -[[image:1653269593172-426.png||height="303" width="725"]]
385 +[[image:image-20220602153621-3.png]]
386 +)))
434 434  
435 -(% style="color:red" %)**Note:**
436 -
437 -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.
438 -
439 -Example:
440 -
441 -(% style="color:red" %)AT+COMMAND1=11 01 1E D0,0
442 -
443 -(% style="color:red" %)AT+SEARCH1=1,1E 56 34
444 -
445 -(% style="color:red" %)AT+DATACUT1=0,2,1~~5
446 -
447 -(% style="color:red" %)Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
448 -
449 -(% style="color:red" %)String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49
450 -
451 -(% style="color:red" %)Valid payload after DataCUT command: 2e 30 58 5f 36
452 -
453 -[[image:1653269618463-608.png]]
454 -
455 455  === 3.3.4 Compose the uplink payload ===
456 456  
457 457  (((
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