Last modified by Xiaoling on 2025/04/23 15:56
<
From version < 32.17 >
edited by Xiaoling
on 2022/06/02 15:31
To version < 57.3 >
edited by Xiaoling
on 2022/06/06 08:41
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -74,7 +74,7 @@
74 74  * Preamble detection.
75 75  * 127 dB Dynamic Range RSSI.
76 76  * Automatic RF Sense and CAD with ultra-fast AFC.
77 -* Packet engine up to 256 bytes with CRC.
77 +* Packet engine up to 256 bytes with CRC
78 78  
79 79  
80 80  
... ... @@ -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 -)))
311 +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 -)))
317 +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 -)))
320 +**Each RS485 commands include two parts:**
342 342  
343 -(((
344 -**Handle return from sensors to RS485-BL**:
345 -)))
322 +~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 -)))
324 +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 -)))
326 +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 -|(((
335 +**AT+COMMANDx : **This command will be sent to RS485 devices during each sampling, Max command length is 14 bytes. The grammar is:
336 +
337 +(% border="1" style="background-color:#4bacc6; color:white; width:499px" %)
338 +|(% 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 -)))
348 +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 -|(((
353 +(% border="1" style="background-color:#4bacc6; color:white; width:725px" %)
354 +|(% 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:
362 +**Examples:**
445 445  
446 446  * Grab bytes:
447 447  
448 -[[image:1653269551753-223.png||height="311" width="717"]]
366 +[[image:image-20220602153621-1.png]]
449 449  
368 +
450 450  * Grab a section.
451 451  
452 -[[image:1653269568276-930.png||height="325" width="718"]]
371 +[[image:image-20220602153621-2.png]]
453 453  
373 +
454 454  * Grab different sections.
455 455  
456 -[[image:1653269593172-426.png||height="303" width="725"]]
376 +[[image:image-20220602153621-3.png]]
457 457  
458 -(% style="color:red" %)**Note:**
378 +
379 +)))
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.**
385 +
386 +
482 482  )))
483 483  
484 484  (((
485 -(% style="color:#4f81bd" %)**Examples: AT+DATAUP=0**
390 +(% style="color:#037691" %)**Examples: AT+DATAUP=0**
391 +
392 +
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  
414 +(% style="color:#037691" %)**Examples: AT+DATAUP=1**
415 +
416 +
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,169 +511,122 @@
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
423 +1. PAYVER: Defined by AT+PAYVER
424 +1. PAYLOAD COUNT: Total how many uplinks of this sampling.
425 +1. PAYLOAD#: Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT)
426 +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"]]
428 +[[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
431 +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
433 +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
435 +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
437 +DATA3=the rest of Valid value of RETURN10= **30**
530 530  
531 -Below are the uplink payloads:
532 532  
533 -[[image:1653270130359-810.png]]
440 +(% 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  
442 + ~* 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:**
444 + * 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)
446 + * 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).
448 + ~* 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).
451 +Below are the uplink payloads:
545 545  
453 +[[image:1654157178836-407.png]]
454 +
455 +
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.
458 +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.
462 +**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.
464 +**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
468 +=== 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]]
470 +RS485-LN support external Interrupt uplink since hardware v1.2 release.
563 563  
564 -AT+INTMOD=0  Disable Interrupt
472 +[[image:1654157342174-798.png]]
565 565  
566 -AT+INTMOD=1  Interrupt trigger by rising or falling edge.
474 +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.
477 +== 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|(((
479 +(% border="1" style="background-color:#4bacc6; color:white; width:734px" %)
480 +|**Size(bytes)**|(% style="width:120px" %)**2**|(% style="width:116px" %)**1**|(% style="width:386px" %)**Length depends on the return from the commands**
481 +|Value|(% style="width:120px" %)(((
578 578  Battery(mV)
579 579  
580 580  &
581 581  
582 582  Interrupt _Flag
583 -)))|(((
487 +)))|(% 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.
491 +)))|(% 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) {
496 +== 3.5 Configure RS485-BL via AT or Downlink ==
593 593  
594 -~/~/Payload Formats of RS485-BL Deceive
498 +User can configure RS485-LN via AT Commands or LoRaWAN Downlink Commands
595 595  
596 -return {
597 -
598 - ~/~/Battery,units:V
599 -
600 - BatV:((bytes[0]<<8 | bytes[1])&0x7fff)/1000,
601 -
602 - ~/~/GPIO_EXTI 
603 -
604 - EXTI_Trigger:(bytes[0] & 0x80)? "TRUE":"FALSE",
605 -
606 - ~/~/payload of version
607 -
608 - Pay_ver:bytes[2],
609 -
610 - };
611 -
612 - }
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 629  There are two kinds of Commands:
630 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
502 +* (% 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]]
632 632  
633 -* **Sensor Related Commands**: These commands are special designed for RS485-BL.  User can see these commands below:
504 +* (% style="color:#4f81bd" %)**Sensor Related Commands**(%%): These commands are special designed for RS485-LN.  User can see these commands below:
634 634  
635 -1.
636 -11.
637 -111. Common Commands:
506 +=== 3.5.1 Common Commands ===
638 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]]
508 +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]]
640 640  
641 641  
642 -1.
643 -11.
644 -111. Sensor related commands:
511 +=== 3.5.2 Sensor related commands ===
645 645  
646 -==== Choose Device Type (RS485 or TTL) ====
513 +Response feature is added to the server's downlink, a special package with a FPort of 200 will be uploaded immediately after receiving the data sent by the server.
647 647  
648 -RS485-BL can connect to either RS485 sensors or TTL sensor. User need to specify what type of sensor need to connect.
515 +[[image:image-20220602163333-5.png||height="263" width="1160"]]
649 649  
650 -* AT Command
517 +The first byte of this package represents whether the configuration is successful, 00 represents failure, 01 represents success. Except for the first byte, the other is the previous downlink. (All commands except A8 type commands are applicable)
651 651  
652 -**AT+MOD=1** ~/~/ Set to support RS485-MODBUS type sensors. User can connect multiply RS485 , Modbus sensors to the A / B pins.
653 653  
654 -**AT+MOD=2** ~/~/ Set to support TTL Level sensors, User can connect one TTL Sensor to the TXD/RXD/GND pins.
520 +=== 3.5.3 Sensor related commands ===
655 655  
522 +==== ====
656 656  
657 -* Downlink Payload
524 +==== **RS485 Debug Command** ====
658 658  
659 -**0A aa**     à same as AT+MOD=aa
526 +This command is used to configure the RS485 devices; they won’t be used during sampling.
660 660  
528 +* **AT Command**
661 661  
530 +(% class="box infomessage" %)
531 +(((
532 +**AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m**
533 +)))
662 662  
663 -==== [[RS485 Debug Command>>path:#downlink_A8]] (AT+CFGDEV) ====
535 +m: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
664 664  
665 -This command is used to configure the RS485 or TTL sensors; they won’t be used during sampling.
537 +* **Downlink Payload**
666 666  
667 -* AT Command
668 -
669 -AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
670 -
671 -m: 0: no CRC; 1: add CRC-16/MODBUS in the end of this command.
672 -
673 -
674 -
675 -* Downlink Payload
676 -
677 677  Format: A8 MM NN XX XX XX XX YY
678 678  
679 679  Where:
... ... @@ -681,9 +681,12 @@
681 681  * MM: 1: add CRC-16/MODBUS ; 0: no CRC
682 682  * NN: The length of RS485 command
683 683  * XX XX XX XX: RS485 command total NN bytes
684 -* YY: How many bytes will be uplink from the return of this RS485 command, if YY=0, RS485-BL will execute the downlink command without uplink; if YY>0, RS485-BL will uplink total YY bytes from the output of this RS485 command
546 +* YY: How many bytes will be uplink from the return of this RS485 command,
547 +** if YY=0, RS485-LN will execute the downlink command without uplink;
548 +** if YY>0, RS485-LN will uplink total YY bytes from the output of this RS485 command; Fport=200
549 +** if YY=FF, RS485-LN will uplink RS485 output with the downlink command content; Fport=200.
685 685  
686 -**Example 1:**
551 +**Example 1** ~-~-> Configure without ask for uplink (YY=0)
687 687  
688 688  To connect a Modbus Alarm with below commands.
689 689  
... ... @@ -693,184 +693,191 @@
693 693  
694 694  So if user want to use downlink command to control to RS485 Alarm, he can use:
695 695  
696 -**A8 01 06 0A 05 00 04 00 01 00**: to activate the RS485 Alarm
561 +(% style="color:#4f81bd" %)**A8 01 06 0A 05 00 04 00 01 00**(%%): to activate the RS485 Alarm
697 697  
698 -**A8 01 06 0A 05 00 04 00 00 00**: to deactivate the RS485 Alarm
563 +(% style="color:#4f81bd" %)**A8 01 06 0A 05 00 04 00 00 00**(%%): to deactivate the RS485 Alarm
699 699  
700 700  A8 is type code and 01 means add CRC-16/MODBUS at the end, the 3^^rd^^ byte is 06, means the next 6 bytes are the command to be sent to the RS485 network, the final byte 00 means this command don’t need to acquire output.
701 701  
702 702  
703 -**Example 2:**
568 +**Example 2** ~-~-> Configure with requesting uplink and original downlink command (**YY=FF**)
704 704  
705 -Check TTL Sensor return:
570 +User in IoT server send a downlink command: (% style="color:#4f81bd" %)**A8 01 06 0A 08 00 04 00 01 YY**
706 706  
707 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image024.png]]
708 708  
573 +RS485-LN got this downlink command and send (% style="color:#4f81bd" %)**0A 08 00 04 00 01 **(%%)to Modbus network. One of the RS485 sensor in the network send back Modbus reply **0A 08 00 04 00 00**. RS485-LN get this reply and combine with the original downlink command and uplink. The uplink message is:
709 709  
575 + **A8** (% style="color:#4f81bd" %)**0A 08 00 04 00  **(% style="color:red" %)**01 06** ** **(% style="color:green" %)**0A 08 00 04 00 00**
710 710  
577 + [[image:1654159460680-153.png]]
711 711  
712 -==== Set Payload version ====
713 713  
714 -This is the first byte of the uplink payload. RS485-BL can connect to different sensors. User can set the PAYVER field to tell server how to decode the current payload.
715 715  
716 -* AT Command:
581 +==== **Set Payload version** ====
717 717  
718 -AT+PAYVER: Set PAYVER field = 1
583 +This is the first byte of the uplink payload. RS485-BL can connect to different sensors. User can set the PAYVER field to tell server how to decode the current payload.
719 719  
585 +* **AT Command:**
720 720  
721 -* Downlink Payload:
587 +(% class="box infomessage" %)
588 +(((
589 +**AT+PAYVER: Set PAYVER field = 1**
590 +)))
722 722  
723 -0xAE 01   à Set PAYVER field =  0x01
592 +* **Downlink Payload:**
724 724  
725 -0xAE 0F   à Set PAYVER field =  0x0F
594 +**0xAE 01**  ~-~-> Set PAYVER field =  0x01
726 726  
596 +**0xAE 0F**   ~-~-> Set PAYVER field =  0x0F
727 727  
728 -==== Set RS485 Sampling Commands ====
729 729  
730 -AT+COMMANDx, AT+DATACUTx and AT+SEARCHx
731 731  
732 -These three commands are used to configure how the RS485-BL polling data from Modbus device. Detail of usage please see : [[polling RS485 device>>path:#polling_485]].
600 +==== **Set RS485 Sampling Commands** ====
733 733  
602 +AT+COMMANDx or AT+DATACUTx
734 734  
735 -* AT Command:
604 +These three commands are used to configure how the RS485-LN polling data from Modbus device. Detail of usage please see : [[polling RS485 device>>||anchor="H3.3.3Configurereadcommandsforeachsampling"]].
736 736  
737 -AT+COMMANDx: Configure RS485 read command to sensor.
738 738  
739 -AT+DATACUTx: Configure how to handle return from RS485 devices.
607 +* **AT Command:**
740 740  
741 -AT+SEARCHx: Configure search command
609 +(% class="box infomessage" %)
610 +(((
611 +**AT+COMMANDx: Configure RS485 read command to sensor.**
612 +)))
742 742  
614 +(% class="box infomessage" %)
615 +(((
616 +**AT+DATACUTx: Configure how to handle return from RS485 devices.**
617 +)))
743 743  
744 -* Downlink Payload:
745 745  
746 -0xAF downlink command can be used to set AT+COMMANDx or AT+DATACUTx.
620 +* **Downlink Payload:**
747 747  
748 -Note: if user use AT+COMMANDx to add a new command, he also need to send AT+DATACUTx downlink.
622 +**0xAF** downlink command can be used to set AT+COMMANDx or AT+DATACUTx.
749 749  
624 +(% style="color:red" %)**Note**(%%): if user use AT+COMMANDx to add a new command, he also need to send AT+DATACUTx downlink.
625 +
750 750  Format: AF MM NN LL XX XX XX XX YY
751 751  
752 752  Where:
753 753  
754 754  * MM: the ATCOMMAND or AT+DATACUT to be set. Value from 01 ~~ 0F,
755 -* NN: 0: no CRC; 1: add CRC-16/MODBUS ; 2: set the AT+DATACUT value.
756 -* LL: The length of AT+COMMAND or AT+DATACUT command
631 +* NN:  0: no CRC; 1: add CRC-16/MODBUS ; 2: set the AT+DATACUT value.
632 +* LL:  The length of AT+COMMAND or AT+DATACUT command
757 757  * XX XX XX XX: AT+COMMAND or AT+DATACUT command
758 -* YY: If YY=0, RS485-BL will execute the downlink command without uplink; if YY=1, RS485-BL will execute an uplink after got this command.
634 +* YY:  If YY=0, RS485-BL will execute the downlink command without uplink; if YY=1, RS485-LN will execute an uplink after got this command.
759 759  
760 -Example:
636 +**Example:**
761 761  
762 -**AF 03 01 06 0A 05 00 04 00 01 00**: Same as AT+COMMAND3=0A 05 00 04 00 01,1
638 +(% style="color:#037691" %)**AF 03 01 06 0A 05 00 04 00 01 00**(%%): Same as AT+COMMAND3=0A 05 00 04 00 01,1
763 763  
764 -**AF 03 02 06 10 01 05 06 09 0A 00**: Same as AT+DATACUT3=**16**,**1**,**5+6+9+10**
640 +(% style="color:#037691" %)**AF 03 02 06**(% style="color:orange" %)** 10 **(% style="color:red" %)**01 **(% style="color:green" %)**05 06 09 0A**(% style="color:#037691" %)** 00**(%%): Same as AT+DATACUT3=(% style="color:orange" %)**16**(%%),(% style="color:red" %)**1**(%%),(% style="color:green" %)**5+6+9+10**
765 765  
766 -**AF 03 02 06 0B 02 05 07 08 0A 00**: Same as AT+DATACUT3=**11**,**2**,**5~~7+8~~10**
642 +(% style="color:#037691" %)**AF 03 02 06 **(% style="color:orange" %)**0B**(% style="color:red" %)** 02 **(% style="color:green" %)**05 07 08 0A **(% style="color:#037691" %)**00**(%%): Same as AT+DATACUT3=(% style="color:orange" %)**11**(%%),(% style="color:red" %)**2**(%%),(% style="color:green" %)**5~~7+8~~10**
767 767  
768 768  
769 -0xAB downlink command can be used for set AT+SEARCHx
770 770  
771 -Example: **AB aa 01 03 xx xx xx** (03 here means there are total 3 bytes after 03) So
646 +==== **Fast command to handle MODBUS device** ====
772 772  
773 -* AB aa 01 03 xx xx xx  same as AT+SEARCHaa=1,xx xx xx
774 -* AB aa 02 03 xx xx xx 02 yy yy(03 means there are 3 bytes after 03, they are xx xx xx;02 means there are 2 bytes after 02, they are yy yy) so the commands
775 -
776 -**AB aa 02 03 xx xx xx 02 yy yy**  same as **AT+SEARCHaa=2,xx xx xx+yy yy**
777 -
778 -
779 -==== Fast command to handle MODBUS device ====
780 -
781 781  AT+MBFUN is valid since v1.3 firmware version. The command is for fast configure to read Modbus devices. It is only valid for the devices which follow the [[MODBUS-RTU protocol>>url:https://www.modbustools.com/modbus.html]].
782 782  
783 783  This command is valid since v1.3 firmware version
784 784  
652 +AT+MBFUN can auto read the Modbus function code: 01, 02, 03 or 04. AT+MBFUN has lower priority vs AT+DATACUT command. If AT+DATACUT command is configured, AT+MBFUN will be ignore.
785 785  
786 -AT+MBFUN has only two value:
787 787  
788 -* AT+MBFUN=1: Enable Modbus reading. And get response base on the MODBUS return
655 +**Example:**
789 789  
790 -AT+MBFUN=1, device can auto read the Modbus function code: 01, 02, 03 or 04. AT+MBFUN has lower priority vs AT+DATACUT command. If AT+DATACUT command is configured, AT+MBFUN will be ignore.
791 -
792 -* AT+MBFUN=0: Disable Modbus fast reading.
793 -
794 -Example:
795 -
796 -* AT+MBFUN=1 and AT+DATACUT1/AT+DATACUT2 are not configure (0,0,0).
657 +* AT+MBFUN=1 and AT+DATACUT1/AT+DATACUT2 are not configure (0,0,0). So RS485-LN.
797 797  * AT+COMMAND1= 01 03 00 10 00 08,1 ~-~-> read slave address 01 , function code 03, start address 00 01, quantity of registers 00 08.
798 798  * AT+COMMAND2= 01 02 00 40 00 10,1 ~-~-> read slave address 01 , function code 02, start address 00 40, quantity of inputs 00 10.
799 799  
800 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image025.png]]
661 +[[image:image-20220602165351-6.png]]
801 801  
663 +[[image:image-20220602165351-7.png]]
802 802  
803 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image026.png]]
804 804  
805 805  
806 -* Downlink Commands:
667 +==== **RS485 command timeout** ====
807 807  
808 -A9 aa -à Same as AT+MBFUN=aa
669 +Some Modbus device has slow action to send replies. This command is used to configure the RS485-LN to use longer time to wait for their action.
809 809  
671 +Default value: 0, range:  0 ~~ 65 seconds
810 810  
811 -==== RS485 command timeout ====
673 +* **AT Command:**
812 812  
813 -Some Modbus device has slow action to send replies. This command is used to configure the RS485-BL to use longer time to wait for their action.
675 +(% class="box infomessage" %)
676 +(((
677 +**AT+CMDDLaa=hex(bb cc)*1000**
678 +)))
814 814  
815 -Default value: 0, range:  0 ~~ 5 seconds
680 +**Example:**
816 816  
682 +**AT+CMDDL1=1000** to send the open time to 1000ms
817 817  
818 -* AT Command:
819 819  
820 -AT+CMDDLaa=hex(bb cc)
685 +* **Downlink Payload:**
821 821  
822 -Example:
687 +**0x AA aa bb cc**
823 823  
824 -**AT+CMDDL1=1000** to send the open time to 1000ms
689 +Same as: AT+CMDDLaa=hex(bb cc)*1000
825 825  
691 + **Example:**
826 826  
827 -* Downlink Payload:
693 + 0xAA 01 00 01  ~-~-> Same as **AT+CMDDL1=1000 ms**
828 828  
829 -0x AA aa bb cc
830 830  
831 -Same as: AT+CMDDLaa=hex(bb cc)
832 832  
833 - Example:
697 +==== **Uplink payload mode** ====
834 834  
835 - 0xAA 01 03 E8  à Same as **AT+CMDDL1=1000 ms**
699 +Define to use one uplink or multiple uplinks for the sampling.
836 836  
701 +The use of this command please see: [[Compose Uplink payload>>||anchor="H3.3.4Composetheuplinkpayload"]]
837 837  
838 -==== [[Uplink>>path:#downlink_A8]] payload mode ====
703 +* **AT Command:**
839 839  
840 -Define to use one uplink or multiple uplinks for the sampling.
705 +(% class="box infomessage" %)
706 +(((
707 +**AT+DATAUP=0**
708 +)))
841 841  
842 -The use of this command please see: [[Compose Uplink payload>>path:#DataUP]]
710 +(% class="box infomessage" %)
711 +(((
712 +**AT+DATAUP=1**
713 +)))
843 843  
844 -* AT Command:
845 845  
846 -AT+DATAUP=0
716 +* **Downlink Payload:**
847 847  
848 -AT+DATAUP=1
718 +**0xAD 00**  **~-~->** Same as AT+DATAUP=0
849 849  
720 +**0xAD 01**  **~-~->** Same as AT+DATAUP=1
850 850  
851 -* Downlink Payload:
852 852  
853 -0xAD 00   à Same as AT+DATAUP=0
854 854  
855 -0xAD 01   à Same as AT+DATAUP=1
724 +==== **Manually trigger an Uplink** ====
856 856  
726 +Ask device to send an uplink immediately.
857 857  
858 -==== Manually trigger an Uplink ====
728 +* **AT Command:**
859 859  
860 -Ask device to send an uplink immediately.
730 +No AT Command for this, user can press the [[ACT button>>path:#Button]] for 1 second for the same.
861 861  
862 -* Downlink Payload:
863 863  
864 -0x08 FF, RS485-BL will immediately send an uplink.
733 +* **Downlink Payload:**
865 865  
735 +**0x08 FF**, RS485-LN will immediately send an uplink.
866 866  
867 -==== Clear RS485 Command ====
868 868  
869 -The AT+COMMANDx and AT+DATACUTx settings are stored in special location, user can use below command to clear them.
738 +==== ====
870 870  
740 +==== **Clear RS485 Command** ====
871 871  
872 -* AT Command:
742 +The AT+COMMANDx and AT+DATACUTx settings are stored in special location, user can use below command to clear them.
873 873  
744 +* **AT Command:**
745 +
874 874  **AT+CMDEAR=mm,nn**   mm: start position of erase ,nn: stop position of erase
875 875  
876 876  Etc. AT+CMDEAR=1,10 means erase AT+COMMAND1/AT+DATACUT1 to AT+COMMAND10/AT+DATACUT10
... ... @@ -878,43 +878,50 @@
878 878  Example screen shot after clear all RS485 commands. 
879 879  
880 880  
881 -
882 882  The uplink screen shot is:
883 883  
884 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png]]
755 +[[image:1654160691922-496.png]][[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image001.png]]
885 885  
886 886  
887 -* Downlink Payload:
758 +* **Downlink Payload:**
888 888  
889 -0x09 aa bb same as AT+CMDEAR=aa,bb
760 +**0x09 aa bb** same as AT+CMDEAR=aa,bb
890 890  
891 891  
892 -==== Set Serial Communication Parameters ====
893 893  
764 +==== **Set Serial Communication Parameters** ====
765 +
894 894  Set the Rs485 serial communication parameters:
895 895  
896 -* AT Command:
768 +* **AT Command:**
897 897  
898 898  Set Baud Rate:
899 899  
900 -AT+BAUDR=9600    ~/~/ Options: (1200,2400,4800,14400,19200,115200)
772 +(% class="box infomessage" %)
773 +(((
774 +**AT+BAUDR=9600**    ~/~/ Options: (1200,2400,4800,14400,19200,115200)
775 +)))
901 901  
777 +Set UART Parity
902 902  
903 -Set UART parity
779 +(% class="box infomessage" %)
780 +(((
781 +**AT+PARITY=0**    ~/~/ Option: 0: no parity, 1: odd parity, 2: even parity
782 +)))
904 904  
905 -AT+PARITY=0    ~/~/ Option: 0: no parity, 1: odd parity, 2: even parity
906 -
907 -
908 908  Set STOPBIT
909 909  
910 -AT+STOPBIT=0    ~/~/ Option: 0 for 1bit; 1 for 1.5 bit ; 2 for 2 bits
786 +(% class="box infomessage" %)
787 +(((
788 +**AT+STOPBIT=0**    ~/~/ Option: 0 for 1bit; 1 for 1.5 bit ; 2 for 2 bits
789 +)))
911 911  
912 912  
913 -* Downlink Payload:
792 +* **Downlink Payload:**
914 914  
915 -A7 01 aa bb: Same  AT+BAUDR=hex(aa bb)*100
794 +**A7 01 aa bb**: Same  AT+BAUDR=hex(aa bb)*100
916 916  
917 -Example:
796 +**Example:**
918 918  
919 919  * A7 01 00 60   same as AT+BAUDR=9600
920 920  * A7 01 04 80  same as AT+BAUDR=115200
... ... @@ -924,189 +924,167 @@
924 924  A7 03 aa: Same as  AT+STOPBIT=aa  (aa value: 00 , 01 or 02)
925 925  
926 926  
927 -==== Control output power duration ====
806 +== 3.6 Listening mode for RS485 network ==
928 928  
929 -User can set the output power duration before each sampling.
808 +This feature support since firmware v1.4
930 930  
931 -* AT Command:
810 +RS485-LN supports listening mode, it can listen the RS485 network packets and send them via LoRaWAN uplink. Below is the structure. The blue arrow shows the RS485 network packets to RS485-LN.
932 932  
933 -Example:
812 +[[image:image-20220602171200-8.png||height="567" width="1007"]]
934 934  
935 -AT+3V3T=1000 ~/~/ 3V3 output power will open 1s before each sampling.
814 +To enable the listening mode, use can run the command AT+RXMODE.
936 936  
937 -AT+5VT=1000 ~/~/ +5V output power will open 1s before each sampling.
938 938  
817 +(% border="1" style="background-color:#ffffcc; width:500px" %)
818 +|=(% style="width: 161px;" %)**Command example:**|=(% style="width: 337px;" %)**Function**
819 +|(% style="width:161px" %)AT+RXMODE=1,10 |(% style="width:337px" %)Enable listening mode 1, if RS485-LN has received more than 10 RS485 commands from the network. RS485-LN will send these commands via LoRaWAN uplinks.
820 +|(% style="width:161px" %)AT+RXMODE=2,500|(% style="width:337px" %)Enable listening mode 2, RS485-LN will capture and send a 500ms content once from the first detect of character. Max value is 65535 ms
821 +|(% style="width:161px" %)AT+RXMODE=0,0|(% style="width:337px" %)Disable listening mode. This is the default settings.
822 +|(% style="width:161px" %) |(% style="width:337px" %)A6 aa bb cc  same as AT+RXMODE=aa,(bb<<8 ~| cc)
939 939  
940 -* LoRaWAN Downlink Command:
824 +**Downlink Command:**
941 941  
942 -07 01 aa bb  Same as AT+5VT=(aa bb)
826 +**0xA6 aa bb cc ** same as AT+RXMODE=aa,(bb<<8 | cc)
943 943  
944 -07 02 aa bb  Same as AT+3V3T=(aa bb)
945 945  
829 +**Example**:
946 946  
831 +The RS485-LN is set to AT+RXMODE=2,1000
947 947  
833 +There is a two Modbus commands in the RS485 network as below:
948 948  
949 -1.
950 -11. Buttons
835 +The Modbus master send a command: (% style="background-color:#ffc000" %)01 03 00 00 00 02 c4 0b
951 951  
952 -|**Button**|**Feature**
953 -|**RST**|Reboot RS485-BL
837 +And Modbus slave reply with: (% style="background-color:green" %)01 03 04 00 00 00 00 fa 33
954 954  
955 -1.
956 -11. +3V3 Output
839 +RS485-LN will capture both and send the uplink: (% style="background-color:#ffc000" %)01 03 00 00 00 02 c4 0b  (% style="background-color:green" %)01 03 04 00 00 00 00 fa 33
957 957  
958 -RS485-BL has a Controllable +3V3 output, user can use this output to power external sensor.
841 +[[image:image-20220602171200-9.png]]
959 959  
960 -The +3V3 output will be valid for every sampling. RS485-BL will enable +3V3 output before all sampling and disable the +3V3 after all sampling. 
961 961  
844 +(% style="color:red" %)Notice: Listening mode can work with the default polling mode of RS485-LN. When RS485-LN is in to send the RS485 commands (from AT+COMMANDx), the listening mode will be interrupt for a while.
962 962  
963 -The +3V3 output time can be controlled by AT Command.
964 964  
965 -**AT+3V3T=1000**
847 +== 3.7 Buttons ==
966 966  
967 -Means set +3v3 valid time to have 1000ms. So, the real +3v3 output will actually have 1000ms + sampling time for other sensors.
968 968  
850 +(% border="1" style="background-color:#f7faff; width:500px" %)
851 +|=**Button**|=(% style="width: 1420px;" %)**Feature**
852 +|**ACT**|(% style="width:1420px" %)If RS485 joined in network, press this button for more than 1 second, RS485 will upload a packet, and the SYS LED will give a (% style="color:blue" %)**Blue blink**
853 +|**RST**|(% style="width:1420px" %)Reboot RS485
854 +|**PRO**|(% style="width:1420px" %)Use for upload image, see [[How to Update Image>>path:#upgrade_image]]
969 969  
970 -By default, the AT+3V3T=0. This is a special case, means the +3V3 output is always on at any time
856 +== 3.8 LEDs ==
971 971  
858 +(% border="1" style="background-color:#f7faff; width:500px" %)
859 +|=**LEDs**|=**Feature**
860 +|**PWR**|Always on if there is power
861 +|**SYS**|After device is powered on, the SYS will (% style="color:green" %)**fast blink in GREEN** (%%)for 5 times, means RS485-LN start to join LoRaWAN network. If join success, SYS will be (% style="color:green" %)**on GREEN for 5 seconds**(%%)**. **SYS will (% style="color:green" %)**blink Blue**(%%) on every upload and (% style="color:green" %)**blink Green**(%%) once receive a downlink message.
972 972  
973 -1.
974 -11. +5V Output
863 += 4. Case Study =
975 975  
976 -RS485-BL has a Controllable +5V output, user can use this output to power external sensor.
865 +User can check this URL for some case studies: [[APP RS485 COMMUNICATE WITH SENSORS>>doc:Main.Application Note \: Communicate with Different Sensors ----- RS485-LN RS485-BL.WebHome]]
977 977  
978 -The +5V output will be valid for every sampling. RS485-BL will enable +5V output before all sampling and disable the +5v after all sampling. 
979 979  
868 += 5. Use AT Command =
980 980  
981 -The 5V output time can be controlled by AT Command.
870 +== 5.1 Access AT Command ==
982 982  
983 -**AT+5VT=1000**
872 +RS485-BL supports AT Command set. User can use a USB to TTL adapter plus the 3.5mm Program Cable to connect to RS485-BL to use AT command, as below.
984 984  
985 -Means set 5V valid time to have 1000ms. So, the real 5V output will actually have 1000ms + sampling time for other sensors.
874 +[[image:1654162355560-817.png]]
986 986  
987 987  
988 -By default, the AT+5VT=0. If the external sensor which require 5v and require more time to get stable state, user can use this command to increase the power ON duration for this sensor.
877 +In PC, User needs to set (% style="color:blue" %)**serial tool**(%%)(such as [[putty>>url:https://www.chiark.greenend.org.uk/~~sgtatham/putty/latest.html]], SecureCRT) baud rate to (% style="color:green" %)**9600**(%%) to access to access serial console of RS485-BL. The default password is 123456. Below is the output for reference:
989 989  
879 +[[image:1654162368066-342.png]]
990 990  
991 991  
882 +More detail AT Command manual can be found at [[AT Command Manual>>||anchor="3.5ConfigureRS485-BLviaATorDownlink"]]
992 992  
993 -1.
994 -11. LEDs
995 995  
996 -|**LEDs**|**Feature**
997 -|**LED1**|Blink when device transmit a packet.
885 +== 5.2 Common AT Command Sequence ==
998 998  
999 -1.
1000 -11. Switch Jumper
887 +=== 5.2.1 Multi-channel ABP mode (Use with SX1301/LG308) ===
1001 1001  
1002 -|**Switch Jumper**|**Feature**
1003 -|**SW1**|(((
1004 -ISP position: Upgrade firmware via UART
889 +If device has not joined network yet:
1005 1005  
1006 -Flash position: Configure device, check running status.
891 +(% class="box infomessage" %)
892 +(((
893 +**AT+FDR**
1007 1007  )))
1008 -|**SW2**|(((
1009 -5V position: set to compatible with 5v I/O.
1010 1010  
1011 -3.3v position: set to compatible with 3.3v I/O.,
896 +(% class="box infomessage" %)
897 +(((
898 +**AT+NJM=0**
1012 1012  )))
1013 1013  
1014 -+3.3V: is always ON
901 +(% class="box infomessage" %)
902 +(((
903 +**ATZ**
904 +)))
1015 1015  
1016 -+5V: Only open before every sampling. The time is by default, it is AT+5VT=0.  Max open time. 5000 ms.
1017 1017  
1018 -1. Case Study
907 +If device already joined network:
1019 1019  
1020 -User can check this URL for some case studies.
909 +(% class="box infomessage" %)
910 +(((
911 +**AT+NJM=0**
912 +)))
1021 1021  
1022 -[[http:~~/~~/wiki.dragino.com/index.php?title=APP_RS485_COMMUNICATE_WITH_SENSORS>>url:http://wiki.dragino.com/index.php?title=APP_RS485_COMMUNICATE_WITH_SENSORS]]
914 +(% class="box infomessage" %)
915 +(((
916 +**ATZ**
917 +)))
1023 1023  
1024 1024  
920 +=== 5.5.2 Single-channel ABP mode (Use with LG01/LG02) ===
1025 1025  
1026 1026  
1027 -1. Use AT Command
1028 -11. Access AT Command
923 +(% style="background-color:#dcdcdc" %)**AT+FDR** (%%) Reset Parameters to Factory Default, Keys Reserve
1029 1029  
1030 -RS485-BL supports AT Command set. User can use a USB to TTL adapter plus the 3.5mm Program Cable to connect to RS485-BL to use AT command, as below.
925 +(% style="background-color:#dcdcdc" %)**AT+NJM=0 **(%%)Set to ABP mode
1031 1031  
1032 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image027.png]]
927 +(% style="background-color:#dcdcdc" %)**AT+ADR=0** (%%)Set the Adaptive Data Rate Off
1033 1033  
929 +(% style="background-color:#dcdcdc" %)**AT+DR=5**   (%%)Set Data Rate
1034 1034  
1035 -In PC, User needs to set **serial tool**(such as [[putty>>url:https://www.chiark.greenend.org.uk/~~sgtatham/putty/latest.html]], SecureCRT) baud rate to **9600** to access to access serial console of RS485-BL. The default password is 123456. Below is the output for reference:
931 +(% style="background-color:#dcdcdc" %)**AT+TDC=60000** (%%) Set transmit interval to 60 seconds
1036 1036  
1037 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image028.png]]
933 +(% style="background-color:#dcdcdc" %)**AT+CHS=868400000**(%%) Set transmit frequency to 868.4Mhz
1038 1038  
935 +(% style="background-color:#dcdcdc" %)**AT+RX2FQ=868400000** (%%) Set RX2Frequency to 868.4Mhz (according to the result from server)
1039 1039  
937 +(% style="background-color:#dcdcdc" %)**AT+RX2DR=5**  (%%) Set RX2DR to match the downlink DR from server. see below
1040 1040  
1041 -More detail AT Command manual can be found at [[AT Command Manual>>path:#AT_COMMAND]]
939 +(% style="background-color:#dcdcdc" %)**AT+DADDR=26** (%%) 01 1A F1 Set Device Address to 26 01 1A F1, this ID can be found in the LoRa Server portal.
1042 1042  
941 +(% style="background-color:#dcdcdc" %)**ATZ**       (%%) Reset MCU
1043 1043  
1044 1044  
1045 -1.
1046 -11. Common AT Command Sequence
1047 -111. Multi-channel ABP mode (Use with SX1301/LG308)
944 +(% style="color:red" %)**Note:**
1048 1048  
1049 -If device has not joined network yet:
946 +(% style="color:red" %)1. Make sure the device is set to ABP mode in the IoT Server.
947 +2. Make sure the LG01/02 gateway RX frequency is exactly the same as AT+CHS setting.
948 +3. Make sure SF / bandwidth setting in LG01/LG02 match the settings of AT+DR. refer [[this link>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/&file=LoRaWAN%201.0.3%20Regional%20Parameters.xlsx]] to see what DR means.
949 +4. The command AT+RX2FQ and AT+RX2DR is to let downlink work. to set the correct parameters, user can check the actually downlink parameters to be used. As below. Which shows the RX2FQ should use 868400000 and RX2DR should be 5
1050 1050  
1051 -AT+FDR
951 +[[image:1654162478620-421.png]]
1052 1052  
1053 -AT+NJM=0
1054 1054  
1055 -ATZ
954 += 6. FAQ =
1056 1056  
956 +== 6.1 How to upgrade the image? ==
1057 1057  
1058 -If device already joined network:
958 +The RS485-LN LoRaWAN Controller is shipped with a 3.5mm cable, the cable is used to upload image to RS485-LN to:
1059 1059  
1060 -AT+NJM=0
1061 -
1062 -ATZ
1063 -
1064 -1.
1065 -11.
1066 -111. Single-channel ABP mode (Use with LG01/LG02)
1067 -
1068 -AT+FDR   Reset Parameters to Factory Default, Keys Reserve
1069 -
1070 -AT+NJM=0 Set to ABP mode
1071 -
1072 -AT+ADR=0 Set the Adaptive Data Rate Off
1073 -
1074 -AT+DR=5  Set Data Rate
1075 -
1076 -AT+TDC=60000  Set transmit interval to 60 seconds
1077 -
1078 -AT+CHS=868400000 Set transmit frequency to 868.4Mhz
1079 -
1080 -AT+RX2FQ=868400000 Set RX2Frequency to 868.4Mhz (according to the result from server)
1081 -
1082 -AT+RX2DR=5  Set RX2DR to match the downlink DR from server. see below
1083 -
1084 -AT+DADDR=26 01 1A F1 Set Device Address to 26 01 1A F1, this ID can be found in the LoRa Server portal.
1085 -
1086 -ATZ          Reset MCU
1087 -
1088 -**Note:**
1089 -
1090 -1. Make sure the device is set to ABP mode in the IoT Server.
1091 -1. Make sure the LG01/02 gateway RX frequency is exactly the same as AT+CHS setting.
1092 -1. Make sure SF / bandwidth setting in LG01/LG02 match the settings of AT+DR. refer [[this link>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/&file=LoRaWAN%201.0.3%20Regional%20Parameters.xlsx]] to see what DR means.
1093 -1. The command AT+RX2FQ and AT+RX2DR is to let downlink work. to set the correct parameters, user can check the actually downlink parameters to be used. As below. Which shows the RX2FQ should use 868400000 and RX2DR should be 5
1094 -
1095 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image029.png]]
1096 -
1097 -
1098 -1. FAQ
1099 -11. How to upgrade the image?
1100 -
1101 -The RS485-BL LoRaWAN Controller is shipped with a 3.5mm cable, the cable is used to upload image to RS485-BL to:
1102 -
1103 1103  * Support new features
1104 1104  * For bug fix
1105 1105  * Change LoRaWAN bands.
1106 1106  
1107 -Below shows the hardware connection for how to upload an image to RS485-BL:
964 +Below shows the hardware connection for how to upload an image to RS485-LN:
1108 1108  
1109 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image030.png]]
966 +[[image:1654162535040-878.png]]
1110 1110  
1111 1111  **Step1:** Download [[flash loader>>url:https://www.st.com/content/st_com/en/products/development-tools/software-development-tools/stm32-software-development-tools/stm32-programmers/flasher-stm32.html]].
1112 1112  
... ... @@ -1114,84 +1114,75 @@
1114 1114  
1115 1115  **Step3: **Open flashloader; choose the correct COM port to update.
1116 1116  
974 +(% style="color:blue" %) Hold down the PRO button and then momentarily press the RST reset button and the SYS led will change from OFF to ON, While SYS LED is RED ON, it means the RS485-LN is ready to be program.
1117 1117  
1118 -|(((
1119 -HOLD PRO then press the RST button, SYS will be ON, then click next
1120 -)))
1121 1121  
1122 -|(((
1123 -Board detected
1124 -)))
977 +[[image:image-20220602175818-12.png]]
1125 1125  
1126 -|(((
1127 -
1128 -)))
1129 1129  
1130 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image031.png]] [[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image032.png]]
980 +[[image:image-20220602175848-13.png]]
1131 1131  
1132 1132  
983 +[[image:image-20220602175912-14.png]]
1133 1133  
1134 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image033.png]] [[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image034.png]]
1135 1135  
986 +**Notice**: In case user has lost the program cable. User can hand made one from a 3.5mm cable. The pin mapping is:
1136 1136  
1137 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image035.png]] [[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image036.png]]
988 +[[image:image-20220602175638-10.png]]
1138 1138  
1139 1139  
1140 -1.
1141 -11. How to change the LoRa Frequency Bands/Region?
991 +== 6.2 How to change the LoRa Frequency Bands/Region? ==
1142 1142  
1143 -User can follow the introduction for [[how to upgrade image>>path:#upgrade_image]]. When download the images, choose the required image file for download.
993 +User can follow the introduction for [[how to upgrade image>>||anchor="H6.1Howtoupgradetheimage3F"]]. When download the images, choose the required image file for download.
1144 1144  
1145 1145  
996 +== 6.3 How many RS485-Slave can RS485-BL connects? ==
1146 1146  
1147 -1.
1148 -11. How many RS485-Slave can RS485-BL connects?
998 +The RS485-BL can support max 32 RS485 devices. Each uplink command of RS485-BL can support max 16 different RS485 command. So RS485-BL can support max 16 RS485 devices pre-program in the device for uplink. For other devices no pre-program, user can use the [[downlink message (type code 0xA8) to poll their info>>||anchor="H3.3.3Configurereadcommandsforeachsampling"]].
1149 1149  
1150 -The RS485-BL can support max 32 RS485 devices. Each uplink command of RS485-BL can support max 16 different RS485 command. So RS485-BL can support max 16 RS485 devices pre-program in the device for uplink. For other devices no pre-program, user can use the [[downlink message (type code 0xA8) to poll their info>>path:#downlink_A8]].
1151 1151  
1001 +== 6.4 Compatible question to ChirpStack and TTI LoRaWAN server ? ==
1152 1152  
1003 +When user need to use with ChirpStack or TTI. Please set AT+RPL=4.
1153 1153  
1005 +Detail info check this link: [[Set Packet Receiving Response Level>>doc:Main.End Device AT Commands and Downlink Command.WebHome||anchor="H7.23SetPacketReceivingResponseLevel"]]
1154 1154  
1155 -1. Trouble Shooting     
1156 -11. Downlink doesn’t work, how to solve it?
1157 1157  
1158 -Please see this link for debug:
1008 += 7. Trouble Shooting =
1159 1159  
1160 -[[http:~~/~~/wiki.dragino.com/index.php?title=Main_Page#LoRaWAN_Communication_Debug>>url:http://wiki.dragino.com/index.php?title=Main_Page#LoRaWAN_Communication_Debug]] 
1010 +== 7.1 Downlink doesn’t work, how to solve it? ==
1161 1161  
1012 +Please see this link for debug: [[LoRaWAN Communication Debug>>doc:Main.LoRaWAN Communication Debug.WebHome]]
1162 1162  
1163 1163  
1164 -1.
1165 -11. Why I can’t join TTN V3 in US915 /AU915 bands?
1015 +== 7.2 Why I can’t join TTN V3 in US915 /AU915 bands? ==
1166 1166  
1167 -It might about the channels mapping. Please see for detail.
1017 +It might about the channels mapping. Please see for detail: [[Notice of Frequency band>>doc:Main.LoRaWAN Communication Debug.WebHome||anchor="H2.NoticeofUS9152FCN4702FAU915Frequencyband"]]
1168 1168  
1169 -[[http:~~/~~/wiki.dragino.com/index.php?title=LoRaWAN_Communication_Debug#Notice_of_US915.2FCN470.2FAU915_Frequency_band>>url:http://wiki.dragino.com/index.php?title=LoRaWAN_Communication_Debug#Notice_of_US915.2FCN470.2FAU915_Frequency_band]]
1170 1170  
1020 += 8. Order Info =
1171 1171  
1022 +(% style="color:blue" %)**Part Number: RS485-LN-XXX**
1172 1172  
1173 -1. Order Info
1024 +(% style="color:blue" %)**XXX:**
1174 1174  
1175 -**Part Number: RS485-BL-XXX**
1026 +* (% style="color:blue" %)**EU433**(%%): frequency bands EU433
1027 +* (% style="color:blue" %)**EU868**(%%): frequency bands EU868
1028 +* (% style="color:blue" %)**KR920**(%%): frequency bands KR920
1029 +* (% style="color:blue" %)**CN470**(%%): frequency bands CN470
1030 +* (% style="color:blue" %)**AS923**(%%): frequency bands AS923
1031 +* (% style="color:blue" %)**AU915**(%%): frequency bands AU915
1032 +* (% style="color:blue" %)**US915**(%%): frequency bands US915
1033 +* (% style="color:blue" %)**IN865**(%%): frequency bands IN865
1034 +* (% style="color:blue" %)**RU864**(%%): frequency bands RU864
1035 +* (% style="color:blue" %)**KZ865**(%%): frequency bands KZ865
1176 1176  
1177 -**XXX:**
1037 += 9.Packing Info =
1178 1178  
1179 -* **EU433**: frequency bands EU433
1180 -* **EU868**: frequency bands EU868
1181 -* **KR920**: frequency bands KR920
1182 -* **CN470**: frequency bands CN470
1183 -* **AS923**: frequency bands AS923
1184 -* **AU915**: frequency bands AU915
1185 -* **US915**: frequency bands US915
1186 -* **IN865**: frequency bands IN865
1187 -* **RU864**: frequency bands RU864
1188 -* **KZ865: **frequency bands KZ865
1189 1189  
1190 -1. Packing Info
1191 -
1192 1192  **Package Includes**:
1193 1193  
1194 -* RS485-BL x 1
1042 +* RS485-LN x 1
1195 1195  * Stick Antenna for LoRa RF part x 1
1196 1196  * Program cable x 1
1197 1197  
... ... @@ -1202,9 +1202,32 @@
1202 1202  * Package Size / pcs : 14.5 x 8 x 5 cm
1203 1203  * Weight / pcs : 170g
1204 1204  
1205 -1. Support
1053 += 10. FCC Caution for RS485LN-US915 =
1206 1206  
1207 -* Support is provided Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different timezones we cannot offer live support. However, your questions will be answered as soon as possible in the before-mentioned schedule.
1208 -* Provide as much information as possible regarding your enquiry (product models, accurately describe your problem and steps to replicate it etc) and send a mail to
1055 +Any Changes or modifications not expressly approved by the party responsible for compliance could void the user's authority to operate the equipment.
1209 1209  
1210 -[[support@dragino.com>>url:file:///D:/市场资料/说明书/LoRa/LT系列/support@dragino.com]]
1057 +This device complies with part 15 of the FCC Rules. Operation is subject to the following two conditions: (1) This device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation.
1058 +
1059 +
1060 +**IMPORTANT NOTE:**
1061 +
1062 +**Note: **This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses and can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications. However, there is no guarantee that interference will not occur in a particular installation. If this equipment does cause harmful interference to radio or television reception, which can be determined by turning the equipment off and on, the user is encouraged to try to correct the interference by one or more of the following measures:
1063 +
1064 +—Reorient or relocate the receiving antenna.
1065 +
1066 +—Increase the separation between the equipment and receiver.
1067 +
1068 +—Connect the equipment into an outlet on a circuit different from that to which the receiver is connected.
1069 +
1070 +—Consult the dealer or an experienced radio/TV technician for help.
1071 +
1072 +
1073 +**FCC Radiation Exposure Statement:**
1074 +
1075 +This equipment complies with FCC radiation exposure limits set forth for an uncontrolled environment.This equipment should be installed and operated with minimum distance 20cm between the radiator& your body.
1076 +
1077 +
1078 += 11. Support =
1079 +
1080 +* Support is provided Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different timezones we cannot offer live support. However, your questions will be answered as soon as possible in the before-mentioned schedule.
1081 +* Provide as much information as possible regarding your enquiry (product models, accurately describe your problem and steps to replicate it etc) and send a mail to [[support@dragino.com>>url:file:///D:/市场资料/说明书/LoRa/LT系列/support@dragino.com]].
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
1654159460680-153.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +24.9 KB
Content
1654160691922-496.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +109.3 KB
Content
1654162355560-817.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +670.0 KB
Content
1654162368066-342.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +192.9 KB
Content
1654162478620-421.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +158.9 KB
Content
1654162535040-878.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +670.0 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
image-20220602163333-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +48.2 KB
Content
image-20220602165351-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +10.6 KB
Content
image-20220602165351-7.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +19.3 KB
Content
image-20220602171200-8.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +276.1 KB
Content
image-20220602171200-9.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +10.0 KB
Content
image-20220602175638-10.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +85.5 KB
Content
image-20220602175743-11.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +85.5 KB
Content
image-20220602175818-12.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +102.5 KB
Content
image-20220602175848-13.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +250.9 KB
Content
image-20220602175912-14.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +176.1 KB
Content

Applications

Navigation

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