Last modified by Karry Zhuang on 2025/03/06 16:34
<
From version < 35.6 >
edited by Xiaoling
on 2022/06/02 15:49
To version < 33.1 >
edited by Xiaoling
on 2022/06/02 15:36
>
Change comment: Uploaded new attachment "image-20220602153621-1.png", version {1}

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,6 +96,8 @@
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/]]
... ... @@ -283,6 +283,8 @@
283 283  )))
284 284  )))
285 285  
292 +
293 +
286 286  === 3.3.2 Configure sensors ===
287 287  
288 288  (((
... ... @@ -301,37 +301,82 @@
301 301  mm: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
302 302  )))|(% style="width:256px" %)AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
303 303  
312 +
313 +
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.
317 +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.
318 +)))
308 308  
320 +(((
321 +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.
322 +)))
323 +
324 +(((
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.
326 +)))
310 310  
328 +(((
311 311  This section describes how to achieve above goals.
330 +)))
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.
332 +(((
333 +During each sampling, the RS485-BL can support 15 commands to read sensors. And combine the return to one or several uplink payloads.
334 +)))
314 314  
336 +(((
337 +**Command from RS485-BL to Sensor:**
338 +)))
315 315  
316 -**Each RS485 commands include two parts:**
340 +(((
341 +RS485-BL can send out pre-set max 15 strings via **AT+COMMAD1**, **ATCOMMAND2**,…, to **AT+COMMANDF** . All commands are of same grammar.
342 +)))
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.
344 +(((
345 +**Handle return from sensors to RS485-BL**:
346 +)))
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.
348 +(((
349 +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**
350 +)))
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
352 +* (((
353 +**AT+DATACUT**
354 +)))
323 323  
356 +(((
357 +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.
358 +)))
324 324  
360 +* (((
361 +**AT+SEARCH**
362 +)))
363 +
364 +(((
365 +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.
366 +)))
367 +
368 +(((
369 +**Define wait timeout:**
370 +)))
371 +
372 +(((
373 +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
374 +)))
375 +
376 +(((
325 325  After we got the valid value from each RS485 commands, we need to combine them together with the command **AT+DATAUP**.
378 +)))
326 326  
380 +**Examples:**
327 327  
328 328  Below are examples for the how above AT Commands works.
329 329  
384 +**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" %)(((
386 +(% border="1" class="table-bordered" %)
387 +|(((
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  
395 +(((
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.
397 +)))
343 343  
344 -In the RS485-LN, we should use this command AT+COMMAND1=01 03 0B B8 00 02,1 for the same.
399 +(((
400 +In the RS485-BL, we should use this command AT+COMMAND1=01 03 0B B8 00 02,1 for the same.
401 +)))
345 345  
403 +(((
404 +**AT+SEARCHx**: This command defines how to handle the return from AT+COMMANDx.
405 +)))
346 346  
407 +(% border="1" class="table-bordered" %)
408 +|(((
409 +**AT+SEARCHx=aa,xx xx xx xx xx**
410 +
411 +* **aa: 1: prefix match mode; 2: prefix and suffix match mode**
412 +* **xx xx xx xx xx: match string. Max 5 bytes for prefix and 5 bytes for suffix**
413 +
414 +
415 +)))
416 +
417 +**Examples:**
418 +
419 +~1. For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
420 +
421 +If we set AT+SEARCH1=1,1E 56 34.      (max 5 bytes for prefix)
422 +
423 +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**
424 +
425 +[[image:1653269403619-508.png]]
426 +
427 +2. For a return string from AT+COMMAND1:  16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
428 +
429 +If we set AT+SEARCH1=2, 1E 56 34+31 00 49
430 +
431 +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**
432 +
433 +[[image:1653269438444-278.png]]
434 +
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" %)(((
437 +|(((
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:**
445 +Examples:
359 359  
360 360  * Grab bytes:
361 361  
362 -[[image:image-20220602153621-1.png]]
449 +[[image:1653269551753-223.png||height="311" width="717"]]
363 363  
364 -
365 365  * Grab a section.
366 366  
367 -[[image:image-20220602153621-2.png]]
453 +[[image:1653269568276-930.png||height="325" width="718"]]
368 368  
369 -
370 370  * Grab different sections.
371 371  
372 -[[image:image-20220602153621-3.png]]
457 +[[image:1653269593172-426.png||height="303" width="725"]]
373 373  
374 -
375 -)))
459 +(% style="color:red" %)**Note:**
376 376  
461 +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.
462 +
463 +Example:
464 +
465 +(% style="color:red" %)AT+COMMAND1=11 01 1E D0,0
466 +
467 +(% style="color:red" %)AT+SEARCH1=1,1E 56 34
468 +
469 +(% style="color:red" %)AT+DATACUT1=0,2,1~~5
470 +
471 +(% style="color:red" %)Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
472 +
473 +(% style="color:red" %)String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49
474 +
475 +(% style="color:red" %)Valid payload after DataCUT command: 2e 30 58 5f 36
476 +
477 +[[image:1653269618463-608.png]]
478 +
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 -
486 +(% 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  
507 +(% 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
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

Applications

Navigation

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