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

Summary

Details

Page properties
Content
... ... @@ -76,8 +76,6 @@
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 -
81 81  == 1.3 Features ==
82 82  
83 83  * LoRaWAN Class A & Class C protocol (default Class C)
... ... @@ -89,8 +89,6 @@
89 89  * Support Modbus protocol
90 90  * Support Interrupt uplink (Since hardware version v1.2)
91 91  
92 -
93 -
94 94  == 1.4 Applications ==
95 95  
96 96  * Smart Buildings & Home Automation
... ... @@ -100,8 +100,6 @@
100 100  * Smart Cities
101 101  * Smart Factory
102 102  
103 -
104 -
105 105  == 1.5 Firmware Change log ==
106 106  
107 107  [[RS485-LN Image files – Download link and Change log>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/]]
... ... @@ -289,8 +289,6 @@
289 289  )))
290 290  )))
291 291  
292 -
293 -
294 294  === 3.3.2 Configure sensors ===
295 295  
296 296  (((
... ... @@ -309,82 +309,37 @@
309 309  mm: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
310 310  )))|(% style="width:256px" %)AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
311 311  
312 -
313 -
314 314  === 3.3.3 Configure read commands for each sampling ===
315 315  
316 316  (((
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 -)))
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.
319 319  
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 -(((
325 325  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 -)))
327 327  
328 -(((
329 329  This section describes how to achieve above goals.
330 -)))
331 331  
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 -)))
313 +During each sampling, the RS485-LN can support 15 commands to read sensors. And combine the return to one or several uplink payloads.
335 335  
336 -(((
337 -**Command from RS485-BL to Sensor:**
338 -)))
339 339  
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 -)))
316 +**Each RS485 commands include two parts:**
343 343  
344 -(((
345 -**Handle return from sensors to RS485-BL**:
346 -)))
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.
347 347  
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 -)))
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.
351 351  
352 -* (((
353 -**AT+DATACUT**
354 -)))
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
355 355  
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 -)))
359 359  
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 -(((
377 377  After we got the valid value from each RS485 commands, we need to combine them together with the command **AT+DATAUP**.
378 -)))
379 379  
380 -**Examples:**
381 381  
382 382  Below are examples for the how above AT Commands works.
383 383  
384 -**AT+COMMANDx : **This command will be sent to RS485/TTL devices during each sampling, Max command length is 14 bytes. The grammar is:
385 385  
386 -(% border="1" class="table-bordered" %)
387 -|(((
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" %)(((
388 388  **AT+COMMANDx=xx xx xx xx xx xx xx xx xx xx xx xx,m**
389 389  
390 390  **xx xx xx xx xx xx xx xx xx xx xx xx: The RS485 command to be sent**
... ... @@ -392,49 +392,15 @@
392 392  **m: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command**
393 393  )))
394 394  
395 -(((
396 396  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 -)))
398 398  
399 -(((
400 -In the RS485-BL, we should use this command AT+COMMAND1=01 03 0B B8 00 02,1 for the same.
401 -)))
344 +In the RS485-LN, we should use this command AT+COMMAND1=01 03 0B B8 00 02,1 for the same.
402 402  
403 -(((
404 -**AT+SEARCHx**: This command defines how to handle the return from AT+COMMANDx.
405 -)))
406 406  
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 -
435 435  **AT+DATACUTx : **This command defines how to handle the return from AT+COMMANDx, max return length is 45 bytes.
436 436  
437 -|(((
349 +(% border="1" style="background-color:#4bacc6; color:white; width:725px" %)
350 +|(% style="width:722px" %)(((
438 438  **AT+DATACUTx=a,b,c**
439 439  
440 440  * **a: length for the return of AT+COMMAND**
... ... @@ -442,48 +442,37 @@
442 442  * **c: define the position for valid value.  **
443 443  )))
444 444  
445 -Examples:
358 +**Examples:**
446 446  
447 447  * Grab bytes:
448 448  
449 -[[image:1653269551753-223.png||height="311" width="717"]]
362 +[[image:image-20220602153621-1.png]]
450 450  
364 +
451 451  * Grab a section.
452 452  
453 -[[image:1653269568276-930.png||height="325" width="718"]]
367 +[[image:image-20220602153621-2.png]]
454 454  
369 +
455 455  * Grab different sections.
456 456  
457 -[[image:1653269593172-426.png||height="303" width="725"]]
372 +[[image:image-20220602153621-3.png]]
458 458  
459 -(% style="color:red" %)**Note:**
374 +
375 +)))
460 460  
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 -
479 479  === 3.3.4 Compose the uplink payload ===
480 480  
481 481  (((
482 482  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 +
483 483  )))
484 484  
485 485  (((
486 -(% style="color:#4f81bd" %)**Examples: AT+DATAUP=0**
386 +(% style="color:#037691" %)**Examples: AT+DATAUP=0**
387 +
388 +
487 487  )))
488 488  
489 489  (((
... ... @@ -504,8 +504,10 @@
504 504  
505 505  [[image:1653269759169-150.png||height="513" width="716"]]
506 506  
507 -(% style="color:#4f81bd" %)**Examples: AT+DATAUP=1**
508 508  
410 +(% style="color:#037691" %)**Examples: AT+DATAUP=1**
411 +
412 +
509 509  Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**Multiply UPLINKs**.
510 510  
511 511  Final Payload is
... ... @@ -512,138 +512,98 @@
512 512  
513 513  (% style="color:#4f81bd" %)**Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA**
514 514  
515 -1. Battery Info (2 bytes): Battery voltage
516 -1. PAYVER (1 byte): Defined by AT+PAYVER
517 -1. PAYLOAD COUNT (1 byte): Total how many uplinks of this sampling.
518 -1. PAYLOAD# (1 byte): Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT)
519 -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
419 +1. PAYVER: Defined by AT+PAYVER
420 +1. PAYLOAD COUNT: Total how many uplinks of this sampling.
421 +1. PAYLOAD#: Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT)
422 +1. DATA: Valid value: max 8 bytes for each uplink so each uplink <= 11 bytes. For the last uplink, DATA will might less than 8 bytes
520 520  
521 -[[image:1653269916228-732.png||height="433" width="711"]]
424 +[[image:image-20220602155039-4.png]]
522 522  
523 523  
524 -So totally there will be 3 uplinks for this sampling, each uplink includes 6 bytes DATA
427 +So totally there will be 3 uplinks for this sampling, each uplink include 8 bytes DATA
525 525  
526 -DATA1=RETURN1 Valid Value = (% style="background-color:green; color:white" %)20 20 0a 33 90 41
429 +DATA1=RETURN1 Valid Value + the first two of Valid value of RETURN10= **20 20 0a 33 90 41 02 aa**
527 527  
528 -DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10=(% style="background-color:green; color:white" %) 02 aa 05 81 0a 20
431 +DATA2=3^^rd^^ ~~ 10^^th^^ byte of Valid value of RETURN10= **05 81 0a 20 20 20 20 2d**
529 529  
530 -DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 = (% style="background-color:green; color:white" %)20 20 20 2d 30
433 +DATA3=the rest of Valid value of RETURN10= **30**
531 531  
532 -Below are the uplink payloads:
533 533  
534 -[[image:1653270130359-810.png]]
436 +(% style="color:red" %)Notice: In firmware v1.3, the Max bytes has been changed according to the max bytes in different Frequency Bands for lowest SF. As below:
535 535  
438 + ~* For AU915/AS923 bands, if UplinkDwell time=0, max 51 bytes for each uplink.
536 536  
537 -(% style="color:red" %)**Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:**
440 + * For AU915/AS923 bands, if UplinkDwell time=0, max 11 bytes for each uplink.
538 538  
539 - ~* For AU915/AS923 bands, if UplinkDwell time=0, max 51 bytes for each uplink ( so 51 -5 = 46 max valid date)
442 + * For US915 band, max 11 bytes for each uplink.
540 540  
541 - * For AU915/AS923 bands, if UplinkDwell time=1, max 11 bytes for each uplink ( so 11 -5 = 6 max valid date).
444 + ~* For all other bands: max 51 bytes for each uplink.
542 542  
543 - * For US915 band, max 11 bytes for each uplink ( so 11 -5 = 6 max valid date).
544 544  
545 - ~* For all other bands: max 51 bytes for each uplink  ( so 51 -5 = 46 max valid date).
447 +Below are the uplink payloads:
546 546  
449 +[[image:1654157178836-407.png]]
450 +
451 +
547 547  === 3.3.5 Uplink on demand ===
548 548  
549 -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.
454 +Except uplink periodically, RS485-LN is able to uplink on demand. The server send downlink command to RS485-LN and RS485 will uplink data base on the command.
550 550  
551 551  Downlink control command:
552 552  
553 -[[0x08 command>>path:#downlink_08]]: Poll an uplink with current command set in RS485-BL.
458 +**0x08 command**: Poll an uplink with current command set in RS485-LN.
554 554  
555 -[[0xA8 command>>path:#downlink_A8]]: Send a command to RS485-BL and uplink the output from sensors.
460 +**0xA8 command**: Send a command to RS485-LN and uplink the output from sensors.
556 556  
557 557  
558 558  
559 -1.
560 -11.
561 -111. Uplink on Interrupt
464 +=== 3.3.6 Uplink on Interrupt ===
562 562  
563 -Put the interrupt sensor between 3.3v_out and GPIO ext.[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image022.png]]
466 +RS485-LN support external Interrupt uplink since hardware v1.2 release.
564 564  
565 -AT+INTMOD=0  Disable Interrupt
468 +[[image:1654157342174-798.png]]
566 566  
567 -AT+INTMOD=1  Interrupt trigger by rising or falling edge.
470 +Connect the Interrupt pin to RS485-LN INT port and connect the GND pin to V- port. When there is a high voltage (Max 24v) on INT pin. Device will send an uplink packet.
568 568  
569 -AT+INTMOD=2  Interrupt trigger by falling edge. ( Default Value)
570 570  
571 -AT+INTMOD=3  Interrupt trigger by rising edge.
473 +== 3.4 Uplink Payload ==
572 572  
573 -
574 -1.
575 -11. Uplink Payload
576 -
577 -|**Size(bytes)**|**2**|**1**|**Length depends on the return from the commands**
578 -|Value|(((
475 +(% border="1" style="background-color:#4bacc6; color:white; width:734px" %)
476 +|**Size(bytes)**|(% style="width:120px" %)**2**|(% style="width:116px" %)**1**|(% style="width:386px" %)**Length depends on the return from the commands**
477 +|Value|(% style="width:120px" %)(((
579 579  Battery(mV)
580 580  
581 581  &
582 582  
583 583  Interrupt _Flag
584 -)))|(((
483 +)))|(% style="width:116px" %)(((
585 585  PAYLOAD_VER
586 586  
587 587  
588 -)))|If the valid payload is too long and exceed the maximum support payload length in server, server will show payload not provided in the LoRaWAN server.
487 +)))|(% style="width:386px" %)If the valid payload is too long and exceed the maximum support payload length in server, server will show payload not provided in the LoRaWAN server.
589 589  
590 590  Below is the decoder for the first 3 bytes. The rest bytes are dynamic depends on different RS485 sensors.
591 591  
592 592  
593 -function Decoder(bytes, port) {
492 +== 3.5 Configure RS485-BL via AT or Downlink ==
594 594  
595 -~/~/Payload Formats of RS485-BL Deceive
494 +User can configure RS485-LN via AT Commands or LoRaWAN Downlink Commands
596 596  
597 -return {
496 +There are two kinds of Commands:
598 598  
599 - ~/~/Battery,units:V
498 +* (% style="color:#4f81bd" %)**Common Commands**(%%): They should be available for each sensor, such as: change uplink interval, reset device. For firmware v1.3, user can find what common commands it supports: [[End Device AT Commands and Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]]
600 600  
601 - BatV:((bytes[0]<<8 | bytes[1])&0x7fff)/1000,
500 +* (% style="color:#4f81bd" %)**Sensor Related Commands**(%%): These commands are special designed for RS485-LN.  User can see these commands below:
602 602  
603 - ~/~/GPIO_EXTI 
604 604  
605 - EXTI_Trigger:(bytes[0] & 0x80)? "TRUE":"FALSE",
606 606  
607 - ~/~/payload of version
504 +=== 3.5.1 Common Commands ===
608 608  
609 - Pay_ver:bytes[2],
506 +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: [[End Device AT Commands and Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]]
610 610  
611 - };
612 612  
613 - }
509 +=== 3.5.2 Sensor related commands: ===
614 614  
615 -
616 -
617 -
618 -
619 -
620 -
621 -TTN V3 uplink screen shot.
622 -
623 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png]]
624 -
625 -1.
626 -11. Configure RS485-BL via AT or Downlink
627 -
628 -User can configure RS485-BL via [[AT Commands >>path:#_​Using_the_AT]]or LoRaWAN Downlink Commands
629 -
630 -There are two kinds of Commands:
631 -
632 -* **Common Commands**: They should be available for each sensor, 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
633 -
634 -* **Sensor Related Commands**: These commands are special designed for RS485-BL.  User can see these commands below:
635 -
636 -1.
637 -11.
638 -111. Common Commands:
639 -
640 -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]]
641 -
642 -
643 -1.
644 -11.
645 -111. Sensor related commands:
646 -
647 647  ==== Choose Device Type (RS485 or TTL) ====
648 648  
649 649  RS485-BL can connect to either RS485 sensors or TTL sensor. User need to specify what type of sensor need to connect.
1654157178836-407.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +179.9 KB
Content
1654157342174-798.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +31.9 KB
Content
1654158783574-851.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +40.6 KB
Content
image-20220602155039-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +24.6 KB
Content
image-20220602163333-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +48.2 KB
Content

Applications

Navigation

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