Last modified by Karry Zhuang on 2025/03/06 16:34
<
From version < 32.17 >
edited by Xiaoling
on 2022/06/02 15:31
To version < 39.1 >
edited by Xiaoling
on 2022/06/02 16:33
>
Change comment: Uploaded new attachment "1654158783574-851.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,7 +289,6 @@
289 289  )))
290 290  )))
291 291  
292 -
293 293  === 3.3.2 Configure sensors ===
294 294  
295 295  (((
... ... @@ -308,82 +308,37 @@
308 308  mm: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
309 309  )))|(% style="width:256px" %)AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
310 310  
311 -
312 -
313 313  === 3.3.3 Configure read commands for each sampling ===
314 314  
315 315  (((
316 -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.
317 -)))
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.
318 318  
319 -(((
320 -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.
321 -)))
322 -
323 -(((
324 324  To save the LoRaWAN network bandwidth, we might need to read data from different sensors and combine their valid value into a short payload.
325 -)))
326 326  
327 -(((
328 328  This section describes how to achieve above goals.
329 -)))
330 330  
331 -(((
332 -During each sampling, the RS485-BL can support 15 commands to read sensors. And combine the return to one or several uplink payloads.
333 -)))
313 +During each sampling, the RS485-LN can support 15 commands to read sensors. And combine the return to one or several uplink payloads.
334 334  
335 -(((
336 -**Command from RS485-BL to Sensor:**
337 -)))
338 338  
339 -(((
340 -RS485-BL can send out pre-set max 15 strings via **AT+COMMAD1**, **ATCOMMAND2**,…, to **AT+COMMANDF** . All commands are of same grammar.
341 -)))
316 +**Each RS485 commands include two parts:**
342 342  
343 -(((
344 -**Handle return from sensors to RS485-BL**:
345 -)))
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.
346 346  
347 -(((
348 -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**
349 -)))
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.
350 350  
351 -* (((
352 -**AT+DATACUT**
353 -)))
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
354 354  
355 -(((
356 -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.
357 -)))
358 358  
359 -* (((
360 -**AT+SEARCH**
361 -)))
362 -
363 -(((
364 -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.
365 -)))
366 -
367 -(((
368 -**Define wait timeout:**
369 -)))
370 -
371 -(((
372 -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
373 -)))
374 -
375 -(((
376 376  After we got the valid value from each RS485 commands, we need to combine them together with the command **AT+DATAUP**.
377 -)))
378 378  
379 -**Examples:**
380 380  
381 381  Below are examples for the how above AT Commands works.
382 382  
383 -**AT+COMMANDx : **This command will be sent to RS485/TTL devices during each sampling, Max command length is 14 bytes. The grammar is:
384 384  
385 -(% border="1" class="table-bordered" %)
386 -|(((
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" %)(((
387 387  **AT+COMMANDx=xx xx xx xx xx xx xx xx xx xx xx xx,m**
388 388  
389 389  **xx xx xx xx xx xx xx xx xx xx xx xx: The RS485 command to be sent**
... ... @@ -391,49 +391,15 @@
391 391  **m: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command**
392 392  )))
393 393  
394 -(((
395 395  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.
396 -)))
397 397  
398 -(((
399 -In the RS485-BL, we should use this command AT+COMMAND1=01 03 0B B8 00 02,1 for the same.
400 -)))
344 +In the RS485-LN, we should use this command AT+COMMAND1=01 03 0B B8 00 02,1 for the same.
401 401  
402 -(((
403 -**AT+SEARCHx**: This command defines how to handle the return from AT+COMMANDx.
404 -)))
405 405  
406 -(% border="1" class="table-bordered" %)
407 -|(((
408 -**AT+SEARCHx=aa,xx xx xx xx xx**
409 -
410 -* **aa: 1: prefix match mode; 2: prefix and suffix match mode**
411 -* **xx xx xx xx xx: match string. Max 5 bytes for prefix and 5 bytes for suffix**
412 -
413 -
414 -)))
415 -
416 -**Examples:**
417 -
418 -~1. For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
419 -
420 -If we set AT+SEARCH1=1,1E 56 34.      (max 5 bytes for prefix)
421 -
422 -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**
423 -
424 -[[image:1653269403619-508.png]]
425 -
426 -2. For a return string from AT+COMMAND1:  16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
427 -
428 -If we set AT+SEARCH1=2, 1E 56 34+31 00 49
429 -
430 -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**
431 -
432 -[[image:1653269438444-278.png]]
433 -
434 434  **AT+DATACUTx : **This command defines how to handle the return from AT+COMMANDx, max return length is 45 bytes.
435 435  
436 -|(((
349 +(% border="1" style="background-color:#4bacc6; color:white; width:725px" %)
350 +|(% style="width:722px" %)(((
437 437  **AT+DATACUTx=a,b,c**
438 438  
439 439  * **a: length for the return of AT+COMMAND**
... ... @@ -441,48 +441,37 @@
441 441  * **c: define the position for valid value.  **
442 442  )))
443 443  
444 -Examples:
358 +**Examples:**
445 445  
446 446  * Grab bytes:
447 447  
448 -[[image:1653269551753-223.png||height="311" width="717"]]
362 +[[image:image-20220602153621-1.png]]
449 449  
364 +
450 450  * Grab a section.
451 451  
452 -[[image:1653269568276-930.png||height="325" width="718"]]
367 +[[image:image-20220602153621-2.png]]
453 453  
369 +
454 454  * Grab different sections.
455 455  
456 -[[image:1653269593172-426.png||height="303" width="725"]]
372 +[[image:image-20220602153621-3.png]]
457 457  
458 -(% style="color:red" %)**Note:**
374 +
375 +)))
459 459  
460 -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.
461 -
462 -Example:
463 -
464 -(% style="color:red" %)AT+COMMAND1=11 01 1E D0,0
465 -
466 -(% style="color:red" %)AT+SEARCH1=1,1E 56 34
467 -
468 -(% style="color:red" %)AT+DATACUT1=0,2,1~~5
469 -
470 -(% style="color:red" %)Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
471 -
472 -(% style="color:red" %)String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49
473 -
474 -(% style="color:red" %)Valid payload after DataCUT command: 2e 30 58 5f 36
475 -
476 -[[image:1653269618463-608.png]]
477 -
478 478  === 3.3.4 Compose the uplink payload ===
479 479  
480 480  (((
481 481  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 +
482 482  )))
483 483  
484 484  (((
485 -(% style="color:#4f81bd" %)**Examples: AT+DATAUP=0**
386 +(% style="color:#037691" %)**Examples: AT+DATAUP=0**
387 +
388 +
486 486  )))
487 487  
488 488  (((
... ... @@ -503,8 +503,10 @@
503 503  
504 504  [[image:1653269759169-150.png||height="513" width="716"]]
505 505  
506 -(% style="color:#4f81bd" %)**Examples: AT+DATAUP=1**
507 507  
410 +(% style="color:#037691" %)**Examples: AT+DATAUP=1**
411 +
412 +
508 508  Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**Multiply UPLINKs**.
509 509  
510 510  Final Payload is
... ... @@ -511,138 +511,98 @@
511 511  
512 512  (% style="color:#4f81bd" %)**Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA**
513 513  
514 -1. Battery Info (2 bytes): Battery voltage
515 -1. PAYVER (1 byte): Defined by AT+PAYVER
516 -1. PAYLOAD COUNT (1 byte): Total how many uplinks of this sampling.
517 -1. PAYLOAD# (1 byte): Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT)
518 -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
519 519  
520 -[[image:1653269916228-732.png||height="433" width="711"]]
424 +[[image:image-20220602155039-4.png]]
521 521  
522 522  
523 -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
524 524  
525 -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**
526 526  
527 -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**
528 528  
529 -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**
530 530  
531 -Below are the uplink payloads:
532 532  
533 -[[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:
534 534  
438 + ~* For AU915/AS923 bands, if UplinkDwell time=0, max 51 bytes for each uplink.
535 535  
536 -(% 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.
537 537  
538 - ~* 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.
539 539  
540 - * 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.
541 541  
542 - * For US915 band, max 11 bytes for each uplink ( so 11 -5 = 6 max valid date).
543 543  
544 - ~* For all other bands: max 51 bytes for each uplink  ( so 51 -5 = 46 max valid date).
447 +Below are the uplink payloads:
545 545  
449 +[[image:1654157178836-407.png]]
450 +
451 +
546 546  === 3.3.5 Uplink on demand ===
547 547  
548 -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.
549 549  
550 550  Downlink control command:
551 551  
552 -[[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.
553 553  
554 -[[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.
555 555  
556 556  
557 557  
558 -1.
559 -11.
560 -111. Uplink on Interrupt
464 +=== 3.3.6 Uplink on Interrupt ===
561 561  
562 -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.
563 563  
564 -AT+INTMOD=0  Disable Interrupt
468 +[[image:1654157342174-798.png]]
565 565  
566 -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.
567 567  
568 -AT+INTMOD=2  Interrupt trigger by falling edge. ( Default Value)
569 569  
570 -AT+INTMOD=3  Interrupt trigger by rising edge.
473 +== 3.4 Uplink Payload ==
571 571  
572 -
573 -1.
574 -11. Uplink Payload
575 -
576 -|**Size(bytes)**|**2**|**1**|**Length depends on the return from the commands**
577 -|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" %)(((
578 578  Battery(mV)
579 579  
580 580  &
581 581  
582 582  Interrupt _Flag
583 -)))|(((
483 +)))|(% style="width:116px" %)(((
584 584  PAYLOAD_VER
585 585  
586 586  
587 -)))|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.
588 588  
589 589  Below is the decoder for the first 3 bytes. The rest bytes are dynamic depends on different RS485 sensors.
590 590  
591 591  
592 -function Decoder(bytes, port) {
492 +== 3.5 Configure RS485-BL via AT or Downlink ==
593 593  
594 -~/~/Payload Formats of RS485-BL Deceive
494 +User can configure RS485-LN via AT Commands or LoRaWAN Downlink Commands
595 595  
596 -return {
496 +There are two kinds of Commands:
597 597  
598 - ~/~/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]]
599 599  
600 - 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:
601 601  
602 - ~/~/GPIO_EXTI 
603 603  
604 - EXTI_Trigger:(bytes[0] & 0x80)? "TRUE":"FALSE",
605 605  
606 - ~/~/payload of version
504 +=== 3.5.1 Common Commands ===
607 607  
608 - 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]]
609 609  
610 - };
611 611  
612 - }
509 +=== 3.5.2 Sensor related commands: ===
613 613  
614 -
615 -
616 -
617 -
618 -
619 -
620 -TTN V3 uplink screen shot.
621 -
622 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png]]
623 -
624 -1.
625 -11. Configure RS485-BL via AT or Downlink
626 -
627 -User can configure RS485-BL via [[AT Commands >>path:#_​Using_the_AT]]or LoRaWAN Downlink Commands
628 -
629 -There are two kinds of Commands:
630 -
631 -* **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
632 -
633 -* **Sensor Related Commands**: These commands are special designed for RS485-BL.  User can see these commands below:
634 -
635 -1.
636 -11.
637 -111. Common Commands:
638 -
639 -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]]
640 -
641 -
642 -1.
643 -11.
644 -111. Sensor related commands:
645 -
646 646  ==== Choose Device Type (RS485 or TTL) ====
647 647  
648 648  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-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
image-20220602155039-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +24.6 KB
Content

Applications

Navigation

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