Last modified by Xiaoling on 2025/04/23 15:56
<
From version < 35.3 >
edited by Xiaoling
on 2022/06/02 15:44
To version < 57.4 >
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  
... ... @@ -289,8 +289,6 @@
289 289  )))
290 290  )))
291 291  
292 -
293 -
294 294  === 3.3.2 Configure sensors ===
295 295  
296 296  (((
... ... @@ -309,8 +309,6 @@
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  (((
... ... @@ -329,11 +329,9 @@
329 329  
330 330  2. How to get wanted value the from RS485 sensors returns from by 1). There are total 15 AT Commands to handle the return, commands are **AT+DATACUT1**,**AT+DATACUT2**,…, **AT+DATACUTF** corresponding to the commands from 1). All commands are of same grammar.
331 331  
332 -3. Some RS485 device might has longer delay on reply, so user can use AT+CMDDL to set the timeout for getting reply after the RS485 command is sent. For example
328 +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
333 333  
334 -**AT+CMDDL1=1000** to send the open time to 1000ms
335 335  
336 -
337 337  After we got the valid value from each RS485 commands, we need to combine them together with the command **AT+DATAUP**.
338 338  
339 339  
... ... @@ -364,10 +364,9 @@
364 364  
365 365  * **a: length for the return of AT+COMMAND**
366 366  * **b:1: grab valid value by byte, max 6 bytes. 2: grab valid value by bytes section, max 3 sections.**
367 -* **c: define the position for valid value. **
361 +* **c: define the position for valid value.  **
368 368  )))
369 369  
370 -
371 371  **Examples:**
372 372  
373 373  * Grab bytes:
... ... @@ -391,10 +391,14 @@
391 391  
392 392  (((
393 393  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.**
387 +
388 +
394 394  )))
395 395  
396 396  (((
397 -(% style="color:#4f81bd" %)**Examples: AT+DATAUP=0**
392 +(% style="color:#037691" %)**Examples: AT+DATAUP=0**
393 +
394 +
398 398  )))
399 399  
400 400  (((
... ... @@ -415,8 +415,10 @@
415 415  
416 416  [[image:1653269759169-150.png||height="513" width="716"]]
417 417  
418 -(% style="color:#4f81bd" %)**Examples: AT+DATAUP=1**
419 419  
416 +(% style="color:#037691" %)**Examples: AT+DATAUP=1**
417 +
418 +
420 420  Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**Multiply UPLINKs**.
421 421  
422 422  Final Payload is
... ... @@ -423,169 +423,122 @@
423 423  
424 424  (% style="color:#4f81bd" %)**Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA**
425 425  
426 -1. Battery Info (2 bytes): Battery voltage
427 -1. PAYVER (1 byte): Defined by AT+PAYVER
428 -1. PAYLOAD COUNT (1 byte): Total how many uplinks of this sampling.
429 -1. PAYLOAD# (1 byte): Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT)
430 -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
425 +1. PAYVER: Defined by AT+PAYVER
426 +1. PAYLOAD COUNT: Total how many uplinks of this sampling.
427 +1. PAYLOAD#: Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT)
428 +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
431 431  
432 -[[image:1653269916228-732.png||height="433" width="711"]]
430 +[[image:image-20220602155039-4.png]]
433 433  
434 434  
435 -So totally there will be 3 uplinks for this sampling, each uplink includes 6 bytes DATA
433 +So totally there will be 3 uplinks for this sampling, each uplink include 8 bytes DATA
436 436  
437 -DATA1=RETURN1 Valid Value = (% style="background-color:green; color:white" %)20 20 0a 33 90 41
435 +DATA1=RETURN1 Valid Value + the first two of Valid value of RETURN10= **20 20 0a 33 90 41 02 aa**
438 438  
439 -DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10=(% style="background-color:green; color:white" %) 02 aa 05 81 0a 20
437 +DATA2=3^^rd^^ ~~ 10^^th^^ byte of Valid value of RETURN10= **05 81 0a 20 20 20 20 2d**
440 440  
441 -DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 = (% style="background-color:green; color:white" %)20 20 20 2d 30
439 +DATA3=the rest of Valid value of RETURN10= **30**
442 442  
443 -Below are the uplink payloads:
444 444  
445 -[[image:1653270130359-810.png]]
442 +(% 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:
446 446  
444 + ~* For AU915/AS923 bands, if UplinkDwell time=0, max 51 bytes for each uplink.
447 447  
448 -(% style="color:red" %)**Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:**
446 + * For AU915/AS923 bands, if UplinkDwell time=0, max 11 bytes for each uplink.
449 449  
450 - ~* For AU915/AS923 bands, if UplinkDwell time=0, max 51 bytes for each uplink ( so 51 -5 = 46 max valid date)
448 + * For US915 band, max 11 bytes for each uplink.
451 451  
452 - * For AU915/AS923 bands, if UplinkDwell time=1, max 11 bytes for each uplink ( so 11 -5 = 6 max valid date).
450 + ~* For all other bands: max 51 bytes for each uplink.
453 453  
454 - * For US915 band, max 11 bytes for each uplink ( so 11 -5 = 6 max valid date).
455 455  
456 - ~* For all other bands: max 51 bytes for each uplink  ( so 51 -5 = 46 max valid date).
453 +Below are the uplink payloads:
457 457  
455 +[[image:1654157178836-407.png]]
456 +
457 +
458 458  === 3.3.5 Uplink on demand ===
459 459  
460 -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.
460 +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.
461 461  
462 462  Downlink control command:
463 463  
464 -[[0x08 command>>path:#downlink_08]]: Poll an uplink with current command set in RS485-BL.
464 +**0x08 command**: Poll an uplink with current command set in RS485-LN.
465 465  
466 -[[0xA8 command>>path:#downlink_A8]]: Send a command to RS485-BL and uplink the output from sensors.
466 +**0xA8 command**: Send a command to RS485-LN and uplink the output from sensors.
467 467  
468 468  
469 469  
470 -1.
471 -11.
472 -111. Uplink on Interrupt
470 +=== 3.3.6 Uplink on Interrupt ===
473 473  
474 -Put the interrupt sensor between 3.3v_out and GPIO ext.[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image022.png]]
472 +RS485-LN support external Interrupt uplink since hardware v1.2 release.
475 475  
476 -AT+INTMOD=0  Disable Interrupt
474 +[[image:1654157342174-798.png]]
477 477  
478 -AT+INTMOD=1  Interrupt trigger by rising or falling edge.
476 +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.
479 479  
480 -AT+INTMOD=2  Interrupt trigger by falling edge. ( Default Value)
481 481  
482 -AT+INTMOD=3  Interrupt trigger by rising edge.
479 +== 3.4 Uplink Payload ==
483 483  
484 -
485 -1.
486 -11. Uplink Payload
487 -
488 -|**Size(bytes)**|**2**|**1**|**Length depends on the return from the commands**
489 -|Value|(((
481 +(% border="1" style="background-color:#4bacc6; color:white; width:734px" %)
482 +|**Size(bytes)**|(% style="width:120px" %)**2**|(% style="width:116px" %)**1**|(% style="width:386px" %)**Length depends on the return from the commands**
483 +|Value|(% style="width:120px" %)(((
490 490  Battery(mV)
491 491  
492 492  &
493 493  
494 494  Interrupt _Flag
495 -)))|(((
489 +)))|(% style="width:116px" %)(((
496 496  PAYLOAD_VER
497 497  
498 498  
499 -)))|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.
493 +)))|(% 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.
500 500  
501 501  Below is the decoder for the first 3 bytes. The rest bytes are dynamic depends on different RS485 sensors.
502 502  
503 503  
504 -function Decoder(bytes, port) {
498 +== 3.5 Configure RS485-BL via AT or Downlink ==
505 505  
506 -~/~/Payload Formats of RS485-BL Deceive
500 +User can configure RS485-LN via AT Commands or LoRaWAN Downlink Commands
507 507  
508 -return {
509 -
510 - ~/~/Battery,units:V
511 -
512 - BatV:((bytes[0]<<8 | bytes[1])&0x7fff)/1000,
513 -
514 - ~/~/GPIO_EXTI 
515 -
516 - EXTI_Trigger:(bytes[0] & 0x80)? "TRUE":"FALSE",
517 -
518 - ~/~/payload of version
519 -
520 - Pay_ver:bytes[2],
521 -
522 - };
523 -
524 - }
525 -
526 -
527 -
528 -
529 -
530 -
531 -
532 -TTN V3 uplink screen shot.
533 -
534 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png]]
535 -
536 -1.
537 -11. Configure RS485-BL via AT or Downlink
538 -
539 -User can configure RS485-BL via [[AT Commands >>path:#_​Using_the_AT]]or LoRaWAN Downlink Commands
540 -
541 541  There are two kinds of Commands:
542 542  
543 -* **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
504 +* (% 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]]
544 544  
545 -* **Sensor Related Commands**: These commands are special designed for RS485-BL.  User can see these commands below:
506 +* (% style="color:#4f81bd" %)**Sensor Related Commands**(%%): These commands are special designed for RS485-LN.  User can see these commands below:
546 546  
547 -1.
548 -11.
549 -111. Common Commands:
508 +=== 3.5.1 Common Commands ===
550 550  
551 -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]]
510 +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]]
552 552  
553 553  
554 -1.
555 -11.
556 -111. Sensor related commands:
513 +=== 3.5.2 Sensor related commands ===
557 557  
558 -==== Choose Device Type (RS485 or TTL) ====
515 +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.
559 559  
560 -RS485-BL can connect to either RS485 sensors or TTL sensor. User need to specify what type of sensor need to connect.
517 +[[image:image-20220602163333-5.png||height="263" width="1160"]]
561 561  
562 -* AT Command
519 +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)
563 563  
564 -**AT+MOD=1** ~/~/ Set to support RS485-MODBUS type sensors. User can connect multiply RS485 , Modbus sensors to the A / B pins.
565 565  
566 -**AT+MOD=2** ~/~/ Set to support TTL Level sensors, User can connect one TTL Sensor to the TXD/RXD/GND pins.
522 +=== 3.5.3 Sensor related commands ===
567 567  
524 +==== ====
568 568  
569 -* Downlink Payload
526 +==== **RS485 Debug Command** ====
570 570  
571 -**0A aa**     à same as AT+MOD=aa
528 +This command is used to configure the RS485 devices; they won’t be used during sampling.
572 572  
530 +* **AT Command**
573 573  
532 +(% class="box infomessage" %)
533 +(((
534 +**AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m**
535 +)))
574 574  
575 -==== [[RS485 Debug Command>>path:#downlink_A8]] (AT+CFGDEV) ====
537 +m: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
576 576  
577 -This command is used to configure the RS485 or TTL sensors; they won’t be used during sampling.
539 +* **Downlink Payload**
578 578  
579 -* AT Command
580 -
581 -AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
582 -
583 -m: 0: no CRC; 1: add CRC-16/MODBUS in the end of this command.
584 -
585 -
586 -
587 -* Downlink Payload
588 -
589 589  Format: A8 MM NN XX XX XX XX YY
590 590  
591 591  Where:
... ... @@ -593,9 +593,12 @@
593 593  * MM: 1: add CRC-16/MODBUS ; 0: no CRC
594 594  * NN: The length of RS485 command
595 595  * XX XX XX XX: RS485 command total NN bytes
596 -* 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
548 +* YY: How many bytes will be uplink from the return of this RS485 command,
549 +** if YY=0, RS485-LN will execute the downlink command without uplink;
550 +** if YY>0, RS485-LN will uplink total YY bytes from the output of this RS485 command; Fport=200
551 +** if YY=FF, RS485-LN will uplink RS485 output with the downlink command content; Fport=200.
597 597  
598 -**Example 1:**
553 +**Example 1** ~-~-> Configure without ask for uplink (YY=0)
599 599  
600 600  To connect a Modbus Alarm with below commands.
601 601  
... ... @@ -605,184 +605,191 @@
605 605  
606 606  So if user want to use downlink command to control to RS485 Alarm, he can use:
607 607  
608 -**A8 01 06 0A 05 00 04 00 01 00**: to activate the RS485 Alarm
563 +(% style="color:#4f81bd" %)**A8 01 06 0A 05 00 04 00 01 00**(%%): to activate the RS485 Alarm
609 609  
610 -**A8 01 06 0A 05 00 04 00 00 00**: to deactivate the RS485 Alarm
565 +(% style="color:#4f81bd" %)**A8 01 06 0A 05 00 04 00 00 00**(%%): to deactivate the RS485 Alarm
611 611  
612 612  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.
613 613  
614 614  
615 -**Example 2:**
570 +**Example 2** ~-~-> Configure with requesting uplink and original downlink command (**YY=FF**)
616 616  
617 -Check TTL Sensor return:
572 +User in IoT server send a downlink command: (% style="color:#4f81bd" %)**A8 01 06 0A 08 00 04 00 01 YY**
618 618  
619 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image024.png]]
620 620  
575 +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:
621 621  
577 + **A8** (% style="color:#4f81bd" %)**0A 08 00 04 00  **(% style="color:red" %)**01 06** ** **(% style="color:green" %)**0A 08 00 04 00 00**
622 622  
579 + [[image:1654159460680-153.png]]
623 623  
624 -==== Set Payload version ====
625 625  
626 -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.
627 627  
628 -* AT Command:
583 +==== **Set Payload version** ====
629 629  
630 -AT+PAYVER: Set PAYVER field = 1
585 +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.
631 631  
587 +* **AT Command:**
632 632  
633 -* Downlink Payload:
589 +(% class="box infomessage" %)
590 +(((
591 +**AT+PAYVER: Set PAYVER field = 1**
592 +)))
634 634  
635 -0xAE 01   à Set PAYVER field =  0x01
594 +* **Downlink Payload:**
636 636  
637 -0xAE 0F   à Set PAYVER field =  0x0F
596 +**0xAE 01**  ~-~-> Set PAYVER field =  0x01
638 638  
598 +**0xAE 0F**   ~-~-> Set PAYVER field =  0x0F
639 639  
640 -==== Set RS485 Sampling Commands ====
641 641  
642 -AT+COMMANDx, AT+DATACUTx and AT+SEARCHx
643 643  
644 -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]].
602 +==== **Set RS485 Sampling Commands** ====
645 645  
604 +AT+COMMANDx or AT+DATACUTx
646 646  
647 -* AT Command:
606 +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"]].
648 648  
649 -AT+COMMANDx: Configure RS485 read command to sensor.
650 650  
651 -AT+DATACUTx: Configure how to handle return from RS485 devices.
609 +* **AT Command:**
652 652  
653 -AT+SEARCHx: Configure search command
611 +(% class="box infomessage" %)
612 +(((
613 +**AT+COMMANDx: Configure RS485 read command to sensor.**
614 +)))
654 654  
616 +(% class="box infomessage" %)
617 +(((
618 +**AT+DATACUTx: Configure how to handle return from RS485 devices.**
619 +)))
655 655  
656 -* Downlink Payload:
657 657  
658 -0xAF downlink command can be used to set AT+COMMANDx or AT+DATACUTx.
622 +* **Downlink Payload:**
659 659  
660 -Note: if user use AT+COMMANDx to add a new command, he also need to send AT+DATACUTx downlink.
624 +**0xAF** downlink command can be used to set AT+COMMANDx or AT+DATACUTx.
661 661  
626 +(% style="color:red" %)**Note**(%%): if user use AT+COMMANDx to add a new command, he also need to send AT+DATACUTx downlink.
627 +
662 662  Format: AF MM NN LL XX XX XX XX YY
663 663  
664 664  Where:
665 665  
666 666  * MM: the ATCOMMAND or AT+DATACUT to be set. Value from 01 ~~ 0F,
667 -* NN: 0: no CRC; 1: add CRC-16/MODBUS ; 2: set the AT+DATACUT value.
668 -* LL: The length of AT+COMMAND or AT+DATACUT command
633 +* NN:  0: no CRC; 1: add CRC-16/MODBUS ; 2: set the AT+DATACUT value.
634 +* LL:  The length of AT+COMMAND or AT+DATACUT command
669 669  * XX XX XX XX: AT+COMMAND or AT+DATACUT command
670 -* 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.
636 +* 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.
671 671  
672 -Example:
638 +**Example:**
673 673  
674 -**AF 03 01 06 0A 05 00 04 00 01 00**: Same as AT+COMMAND3=0A 05 00 04 00 01,1
640 +(% 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
675 675  
676 -**AF 03 02 06 10 01 05 06 09 0A 00**: Same as AT+DATACUT3=**16**,**1**,**5+6+9+10**
642 +(% 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**
677 677  
678 -**AF 03 02 06 0B 02 05 07 08 0A 00**: Same as AT+DATACUT3=**11**,**2**,**5~~7+8~~10**
644 +(% 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**
679 679  
680 680  
681 -0xAB downlink command can be used for set AT+SEARCHx
682 682  
683 -Example: **AB aa 01 03 xx xx xx** (03 here means there are total 3 bytes after 03) So
648 +==== **Fast command to handle MODBUS device** ====
684 684  
685 -* AB aa 01 03 xx xx xx  same as AT+SEARCHaa=1,xx xx xx
686 -* 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
687 -
688 -**AB aa 02 03 xx xx xx 02 yy yy**  same as **AT+SEARCHaa=2,xx xx xx+yy yy**
689 -
690 -
691 -==== Fast command to handle MODBUS device ====
692 -
693 693  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]].
694 694  
695 695  This command is valid since v1.3 firmware version
696 696  
654 +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.
697 697  
698 -AT+MBFUN has only two value:
699 699  
700 -* AT+MBFUN=1: Enable Modbus reading. And get response base on the MODBUS return
657 +**Example:**
701 701  
702 -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.
703 -
704 -* AT+MBFUN=0: Disable Modbus fast reading.
705 -
706 -Example:
707 -
708 -* AT+MBFUN=1 and AT+DATACUT1/AT+DATACUT2 are not configure (0,0,0).
659 +* AT+MBFUN=1 and AT+DATACUT1/AT+DATACUT2 are not configure (0,0,0). So RS485-LN.
709 709  * 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.
710 710  * 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.
711 711  
712 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image025.png]]
663 +[[image:image-20220602165351-6.png]]
713 713  
665 +[[image:image-20220602165351-7.png]]
714 714  
715 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image026.png]]
716 716  
717 717  
718 -* Downlink Commands:
669 +==== **RS485 command timeout** ====
719 719  
720 -A9 aa -à Same as AT+MBFUN=aa
671 +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.
721 721  
673 +Default value: 0, range:  0 ~~ 65 seconds
722 722  
723 -==== RS485 command timeout ====
675 +* **AT Command:**
724 724  
725 -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.
677 +(% class="box infomessage" %)
678 +(((
679 +**AT+CMDDLaa=hex(bb cc)*1000**
680 +)))
726 726  
727 -Default value: 0, range:  0 ~~ 5 seconds
682 +**Example:**
728 728  
684 +**AT+CMDDL1=1000** to send the open time to 1000ms
729 729  
730 -* AT Command:
731 731  
732 -AT+CMDDLaa=hex(bb cc)
687 +* **Downlink Payload:**
733 733  
734 -Example:
689 +**0x AA aa bb cc**
735 735  
736 -**AT+CMDDL1=1000** to send the open time to 1000ms
691 +Same as: AT+CMDDLaa=hex(bb cc)*1000
737 737  
693 + **Example:**
738 738  
739 -* Downlink Payload:
695 + 0xAA 01 00 01  ~-~-> Same as **AT+CMDDL1=1000 ms**
740 740  
741 -0x AA aa bb cc
742 742  
743 -Same as: AT+CMDDLaa=hex(bb cc)
744 744  
745 - Example:
699 +==== **Uplink payload mode** ====
746 746  
747 - 0xAA 01 03 E8  à Same as **AT+CMDDL1=1000 ms**
701 +Define to use one uplink or multiple uplinks for the sampling.
748 748  
703 +The use of this command please see: [[Compose Uplink payload>>||anchor="H3.3.4Composetheuplinkpayload"]]
749 749  
750 -==== [[Uplink>>path:#downlink_A8]] payload mode ====
705 +* **AT Command:**
751 751  
752 -Define to use one uplink or multiple uplinks for the sampling.
707 +(% class="box infomessage" %)
708 +(((
709 +**AT+DATAUP=0**
710 +)))
753 753  
754 -The use of this command please see: [[Compose Uplink payload>>path:#DataUP]]
712 +(% class="box infomessage" %)
713 +(((
714 +**AT+DATAUP=1**
715 +)))
755 755  
756 -* AT Command:
757 757  
758 -AT+DATAUP=0
718 +* **Downlink Payload:**
759 759  
760 -AT+DATAUP=1
720 +**0xAD 00**  **~-~->** Same as AT+DATAUP=0
761 761  
722 +**0xAD 01**  **~-~->** Same as AT+DATAUP=1
762 762  
763 -* Downlink Payload:
764 764  
765 -0xAD 00   à Same as AT+DATAUP=0
766 766  
767 -0xAD 01   à Same as AT+DATAUP=1
726 +==== **Manually trigger an Uplink** ====
768 768  
728 +Ask device to send an uplink immediately.
769 769  
770 -==== Manually trigger an Uplink ====
730 +* **AT Command:**
771 771  
772 -Ask device to send an uplink immediately.
732 +No AT Command for this, user can press the [[ACT button>>path:#Button]] for 1 second for the same.
773 773  
774 -* Downlink Payload:
775 775  
776 -0x08 FF, RS485-BL will immediately send an uplink.
735 +* **Downlink Payload:**
777 777  
737 +**0x08 FF**, RS485-LN will immediately send an uplink.
778 778  
779 -==== Clear RS485 Command ====
780 780  
781 -The AT+COMMANDx and AT+DATACUTx settings are stored in special location, user can use below command to clear them.
740 +==== ====
782 782  
742 +==== **Clear RS485 Command** ====
783 783  
784 -* AT Command:
744 +The AT+COMMANDx and AT+DATACUTx settings are stored in special location, user can use below command to clear them.
785 785  
746 +* **AT Command:**
747 +
786 786  **AT+CMDEAR=mm,nn**   mm: start position of erase ,nn: stop position of erase
787 787  
788 788  Etc. AT+CMDEAR=1,10 means erase AT+COMMAND1/AT+DATACUT1 to AT+COMMAND10/AT+DATACUT10
... ... @@ -790,43 +790,50 @@
790 790  Example screen shot after clear all RS485 commands. 
791 791  
792 792  
793 -
794 794  The uplink screen shot is:
795 795  
796 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png]]
757 +[[image:1654160691922-496.png]][[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image001.png]]
797 797  
798 798  
799 -* Downlink Payload:
760 +* **Downlink Payload:**
800 800  
801 -0x09 aa bb same as AT+CMDEAR=aa,bb
762 +**0x09 aa bb** same as AT+CMDEAR=aa,bb
802 802  
803 803  
804 -==== Set Serial Communication Parameters ====
805 805  
766 +==== **Set Serial Communication Parameters** ====
767 +
806 806  Set the Rs485 serial communication parameters:
807 807  
808 -* AT Command:
770 +* **AT Command:**
809 809  
810 810  Set Baud Rate:
811 811  
812 -AT+BAUDR=9600    ~/~/ Options: (1200,2400,4800,14400,19200,115200)
774 +(% class="box infomessage" %)
775 +(((
776 +**AT+BAUDR=9600**    ~/~/ Options: (1200,2400,4800,14400,19200,115200)
777 +)))
813 813  
779 +Set UART Parity
814 814  
815 -Set UART parity
781 +(% class="box infomessage" %)
782 +(((
783 +**AT+PARITY=0**    ~/~/ Option: 0: no parity, 1: odd parity, 2: even parity
784 +)))
816 816  
817 -AT+PARITY=0    ~/~/ Option: 0: no parity, 1: odd parity, 2: even parity
818 -
819 -
820 820  Set STOPBIT
821 821  
822 -AT+STOPBIT=0    ~/~/ Option: 0 for 1bit; 1 for 1.5 bit ; 2 for 2 bits
788 +(% class="box infomessage" %)
789 +(((
790 +**AT+STOPBIT=0**    ~/~/ Option: 0 for 1bit; 1 for 1.5 bit ; 2 for 2 bits
791 +)))
823 823  
824 824  
825 -* Downlink Payload:
794 +* **Downlink Payload:**
826 826  
827 -A7 01 aa bb: Same  AT+BAUDR=hex(aa bb)*100
796 +**A7 01 aa bb**: Same  AT+BAUDR=hex(aa bb)*100
828 828  
829 -Example:
798 +**Example:**
830 830  
831 831  * A7 01 00 60   same as AT+BAUDR=9600
832 832  * A7 01 04 80  same as AT+BAUDR=115200
... ... @@ -836,189 +836,167 @@
836 836  A7 03 aa: Same as  AT+STOPBIT=aa  (aa value: 00 , 01 or 02)
837 837  
838 838  
839 -==== Control output power duration ====
808 +== 3.6 Listening mode for RS485 network ==
840 840  
841 -User can set the output power duration before each sampling.
810 +This feature support since firmware v1.4
842 842  
843 -* AT Command:
812 +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.
844 844  
845 -Example:
814 +[[image:image-20220602171200-8.png||height="567" width="1007"]]
846 846  
847 -AT+3V3T=1000 ~/~/ 3V3 output power will open 1s before each sampling.
816 +To enable the listening mode, use can run the command AT+RXMODE.
848 848  
849 -AT+5VT=1000 ~/~/ +5V output power will open 1s before each sampling.
850 850  
819 +(% border="1" style="background-color:#ffffcc; width:500px" %)
820 +|=(% style="width: 161px;" %)**Command example:**|=(% style="width: 337px;" %)**Function**
821 +|(% 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.
822 +|(% 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
823 +|(% style="width:161px" %)AT+RXMODE=0,0|(% style="width:337px" %)Disable listening mode. This is the default settings.
824 +|(% style="width:161px" %) |(% style="width:337px" %)A6 aa bb cc  same as AT+RXMODE=aa,(bb<<8 ~| cc)
851 851  
852 -* LoRaWAN Downlink Command:
826 +**Downlink Command:**
853 853  
854 -07 01 aa bb  Same as AT+5VT=(aa bb)
828 +**0xA6 aa bb cc ** same as AT+RXMODE=aa,(bb<<8 | cc)
855 855  
856 -07 02 aa bb  Same as AT+3V3T=(aa bb)
857 857  
831 +**Example**:
858 858  
833 +The RS485-LN is set to AT+RXMODE=2,1000
859 859  
835 +There is a two Modbus commands in the RS485 network as below:
860 860  
861 -1.
862 -11. Buttons
837 +The Modbus master send a command: (% style="background-color:#ffc000" %)01 03 00 00 00 02 c4 0b
863 863  
864 -|**Button**|**Feature**
865 -|**RST**|Reboot RS485-BL
839 +And Modbus slave reply with: (% style="background-color:green" %)01 03 04 00 00 00 00 fa 33
866 866  
867 -1.
868 -11. +3V3 Output
841 +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
869 869  
870 -RS485-BL has a Controllable +3V3 output, user can use this output to power external sensor.
843 +[[image:image-20220602171200-9.png]]
871 871  
872 -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. 
873 873  
846 +(% 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.
874 874  
875 -The +3V3 output time can be controlled by AT Command.
876 876  
877 -**AT+3V3T=1000**
849 +== 3.7 Buttons ==
878 878  
879 -Means set +3v3 valid time to have 1000ms. So, the real +3v3 output will actually have 1000ms + sampling time for other sensors.
880 880  
852 +(% border="1" style="background-color:#f7faff; width:500px" %)
853 +|=**Button**|=(% style="width: 1420px;" %)**Feature**
854 +|**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**
855 +|**RST**|(% style="width:1420px" %)Reboot RS485
856 +|**PRO**|(% style="width:1420px" %)Use for upload image, see [[How to Update Image>>path:#upgrade_image]]
881 881  
882 -By default, the AT+3V3T=0. This is a special case, means the +3V3 output is always on at any time
858 +== 3.8 LEDs ==
883 883  
860 +(% border="1" style="background-color:#f7faff; width:500px" %)
861 +|=**LEDs**|=**Feature**
862 +|**PWR**|Always on if there is power
863 +|**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.
884 884  
885 -1.
886 -11. +5V Output
865 += 4. Case Study =
887 887  
888 -RS485-BL has a Controllable +5V output, user can use this output to power external sensor.
867 +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]]
889 889  
890 -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. 
891 891  
870 += 5. Use AT Command =
892 892  
893 -The 5V output time can be controlled by AT Command.
872 +== 5.1 Access AT Command ==
894 894  
895 -**AT+5VT=1000**
874 +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.
896 896  
897 -Means set 5V valid time to have 1000ms. So, the real 5V output will actually have 1000ms + sampling time for other sensors.
876 +[[image:1654162355560-817.png]]
898 898  
899 899  
900 -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.
879 +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:
901 901  
881 +[[image:1654162368066-342.png]]
902 902  
903 903  
884 +More detail AT Command manual can be found at [[AT Command Manual>>||anchor="3.5ConfigureRS485-BLviaATorDownlink"]]
904 904  
905 -1.
906 -11. LEDs
907 907  
908 -|**LEDs**|**Feature**
909 -|**LED1**|Blink when device transmit a packet.
887 +== 5.2 Common AT Command Sequence ==
910 910  
911 -1.
912 -11. Switch Jumper
889 +=== 5.2.1 Multi-channel ABP mode (Use with SX1301/LG308) ===
913 913  
914 -|**Switch Jumper**|**Feature**
915 -|**SW1**|(((
916 -ISP position: Upgrade firmware via UART
891 +If device has not joined network yet:
917 917  
918 -Flash position: Configure device, check running status.
893 +(% class="box infomessage" %)
894 +(((
895 +**AT+FDR**
919 919  )))
920 -|**SW2**|(((
921 -5V position: set to compatible with 5v I/O.
922 922  
923 -3.3v position: set to compatible with 3.3v I/O.,
898 +(% class="box infomessage" %)
899 +(((
900 +**AT+NJM=0**
924 924  )))
925 925  
926 -+3.3V: is always ON
903 +(% class="box infomessage" %)
904 +(((
905 +**ATZ**
906 +)))
927 927  
928 -+5V: Only open before every sampling. The time is by default, it is AT+5VT=0.  Max open time. 5000 ms.
929 929  
930 -1. Case Study
909 +If device already joined network:
931 931  
932 -User can check this URL for some case studies.
911 +(% class="box infomessage" %)
912 +(((
913 +**AT+NJM=0**
914 +)))
933 933  
934 -[[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]]
916 +(% class="box infomessage" %)
917 +(((
918 +**ATZ**
919 +)))
935 935  
936 936  
922 +=== 5.5.2 Single-channel ABP mode (Use with LG01/LG02) ===
937 937  
938 938  
939 -1. Use AT Command
940 -11. Access AT Command
925 +(% style="background-color:#dcdcdc" %)**AT+FDR** (%%) Reset Parameters to Factory Default, Keys Reserve
941 941  
942 -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.
927 +(% style="background-color:#dcdcdc" %)**AT+NJM=0 **(%%)Set to ABP mode
943 943  
944 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image027.png]]
929 +(% style="background-color:#dcdcdc" %)**AT+ADR=0** (%%)Set the Adaptive Data Rate Off
945 945  
931 +(% style="background-color:#dcdcdc" %)**AT+DR=5**   (%%)Set Data Rate
946 946  
947 -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:
933 +(% style="background-color:#dcdcdc" %)**AT+TDC=60000** (%%) Set transmit interval to 60 seconds
948 948  
949 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image028.png]]
935 +(% style="background-color:#dcdcdc" %)**AT+CHS=868400000**(%%) Set transmit frequency to 868.4Mhz
950 950  
937 +(% style="background-color:#dcdcdc" %)**AT+RX2FQ=868400000** (%%) Set RX2Frequency to 868.4Mhz (according to the result from server)
951 951  
939 +(% style="background-color:#dcdcdc" %)**AT+RX2DR=5**  (%%) Set RX2DR to match the downlink DR from server. see below
952 952  
953 -More detail AT Command manual can be found at [[AT Command Manual>>path:#AT_COMMAND]]
941 +(% 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.
954 954  
943 +(% style="background-color:#dcdcdc" %)**ATZ**       (%%) Reset MCU
955 955  
956 956  
957 -1.
958 -11. Common AT Command Sequence
959 -111. Multi-channel ABP mode (Use with SX1301/LG308)
946 +(% style="color:red" %)**Note:**
960 960  
961 -If device has not joined network yet:
948 +(% style="color:red" %)1. Make sure the device is set to ABP mode in the IoT Server.
949 +2. Make sure the LG01/02 gateway RX frequency is exactly the same as AT+CHS setting.
950 +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.
951 +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
962 962  
963 -AT+FDR
953 +[[image:1654162478620-421.png]]
964 964  
965 -AT+NJM=0
966 966  
967 -ATZ
956 += 6. FAQ =
968 968  
958 +== 6.1 How to upgrade the image? ==
969 969  
970 -If device already joined network:
960 +The RS485-LN LoRaWAN Controller is shipped with a 3.5mm cable, the cable is used to upload image to RS485-LN to:
971 971  
972 -AT+NJM=0
973 -
974 -ATZ
975 -
976 -1.
977 -11.
978 -111. Single-channel ABP mode (Use with LG01/LG02)
979 -
980 -AT+FDR   Reset Parameters to Factory Default, Keys Reserve
981 -
982 -AT+NJM=0 Set to ABP mode
983 -
984 -AT+ADR=0 Set the Adaptive Data Rate Off
985 -
986 -AT+DR=5  Set Data Rate
987 -
988 -AT+TDC=60000  Set transmit interval to 60 seconds
989 -
990 -AT+CHS=868400000 Set transmit frequency to 868.4Mhz
991 -
992 -AT+RX2FQ=868400000 Set RX2Frequency to 868.4Mhz (according to the result from server)
993 -
994 -AT+RX2DR=5  Set RX2DR to match the downlink DR from server. see below
995 -
996 -AT+DADDR=26 01 1A F1 Set Device Address to 26 01 1A F1, this ID can be found in the LoRa Server portal.
997 -
998 -ATZ          Reset MCU
999 -
1000 -**Note:**
1001 -
1002 -1. Make sure the device is set to ABP mode in the IoT Server.
1003 -1. Make sure the LG01/02 gateway RX frequency is exactly the same as AT+CHS setting.
1004 -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.
1005 -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
1006 -
1007 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image029.png]]
1008 -
1009 -
1010 -1. FAQ
1011 -11. How to upgrade the image?
1012 -
1013 -The RS485-BL LoRaWAN Controller is shipped with a 3.5mm cable, the cable is used to upload image to RS485-BL to:
1014 -
1015 1015  * Support new features
1016 1016  * For bug fix
1017 1017  * Change LoRaWAN bands.
1018 1018  
1019 -Below shows the hardware connection for how to upload an image to RS485-BL:
966 +Below shows the hardware connection for how to upload an image to RS485-LN:
1020 1020  
1021 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image030.png]]
968 +[[image:1654162535040-878.png]]
1022 1022  
1023 1023  **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]].
1024 1024  
... ... @@ -1026,84 +1026,75 @@
1026 1026  
1027 1027  **Step3: **Open flashloader; choose the correct COM port to update.
1028 1028  
976 +(% 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.
1029 1029  
1030 -|(((
1031 -HOLD PRO then press the RST button, SYS will be ON, then click next
1032 -)))
1033 1033  
1034 -|(((
1035 -Board detected
1036 -)))
979 +[[image:image-20220602175818-12.png]]
1037 1037  
1038 -|(((
1039 -
1040 -)))
1041 1041  
1042 -[[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]]
982 +[[image:image-20220602175848-13.png]]
1043 1043  
1044 1044  
985 +[[image:image-20220602175912-14.png]]
1045 1045  
1046 -[[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]]
1047 1047  
988 +**Notice**: In case user has lost the program cable. User can hand made one from a 3.5mm cable. The pin mapping is:
1048 1048  
1049 -[[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]]
990 +[[image:image-20220602175638-10.png]]
1050 1050  
1051 1051  
1052 -1.
1053 -11. How to change the LoRa Frequency Bands/Region?
993 +== 6.2 How to change the LoRa Frequency Bands/Region? ==
1054 1054  
1055 -User can follow the introduction for [[how to upgrade image>>path:#upgrade_image]]. When download the images, choose the required image file for download.
995 +User can follow the introduction for [[how to upgrade image>>||anchor="H6.1Howtoupgradetheimage3F"]]. When download the images, choose the required image file for download.
1056 1056  
1057 1057  
998 +== 6.3 How many RS485-Slave can RS485-BL connects? ==
1058 1058  
1059 -1.
1060 -11. How many RS485-Slave can RS485-BL connects?
1000 +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"]].
1061 1061  
1062 -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]].
1063 1063  
1003 +== 6.4 Compatible question to ChirpStack and TTI LoRaWAN server ? ==
1064 1064  
1005 +When user need to use with ChirpStack or TTI. Please set AT+RPL=4.
1065 1065  
1007 +Detail info check this link: [[Set Packet Receiving Response Level>>doc:Main.End Device AT Commands and Downlink Command.WebHome||anchor="H7.23SetPacketReceivingResponseLevel"]]
1066 1066  
1067 -1. Trouble Shooting     
1068 -11. Downlink doesn’t work, how to solve it?
1069 1069  
1070 -Please see this link for debug:
1010 += 7. Trouble Shooting =
1071 1071  
1072 -[[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]] 
1012 +== 7.1 Downlink doesn’t work, how to solve it? ==
1073 1073  
1014 +Please see this link for debug: [[LoRaWAN Communication Debug>>doc:Main.LoRaWAN Communication Debug.WebHome]]
1074 1074  
1075 1075  
1076 -1.
1077 -11. Why I can’t join TTN V3 in US915 /AU915 bands?
1017 +== 7.2 Why I can’t join TTN V3 in US915 /AU915 bands? ==
1078 1078  
1079 -It might about the channels mapping. Please see for detail.
1019 +It might about the channels mapping. Please see for detail: [[Notice of Frequency band>>doc:Main.LoRaWAN Communication Debug.WebHome||anchor="H2.NoticeofUS9152FCN4702FAU915Frequencyband"]]
1080 1080  
1081 -[[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]]
1082 1082  
1022 += 8. Order Info =
1083 1083  
1024 +(% style="color:blue" %)**Part Number: RS485-LN-XXX**
1084 1084  
1085 -1. Order Info
1026 +(% style="color:blue" %)**XXX:**
1086 1086  
1087 -**Part Number: RS485-BL-XXX**
1028 +* (% style="color:blue" %)**EU433**(%%): frequency bands EU433
1029 +* (% style="color:blue" %)**EU868**(%%): frequency bands EU868
1030 +* (% style="color:blue" %)**KR920**(%%): frequency bands KR920
1031 +* (% style="color:blue" %)**CN470**(%%): frequency bands CN470
1032 +* (% style="color:blue" %)**AS923**(%%): frequency bands AS923
1033 +* (% style="color:blue" %)**AU915**(%%): frequency bands AU915
1034 +* (% style="color:blue" %)**US915**(%%): frequency bands US915
1035 +* (% style="color:blue" %)**IN865**(%%): frequency bands IN865
1036 +* (% style="color:blue" %)**RU864**(%%): frequency bands RU864
1037 +* (% style="color:blue" %)**KZ865**(%%): frequency bands KZ865
1088 1088  
1089 -**XXX:**
1039 += 9.Packing Info =
1090 1090  
1091 -* **EU433**: frequency bands EU433
1092 -* **EU868**: frequency bands EU868
1093 -* **KR920**: frequency bands KR920
1094 -* **CN470**: frequency bands CN470
1095 -* **AS923**: frequency bands AS923
1096 -* **AU915**: frequency bands AU915
1097 -* **US915**: frequency bands US915
1098 -* **IN865**: frequency bands IN865
1099 -* **RU864**: frequency bands RU864
1100 -* **KZ865: **frequency bands KZ865
1101 1101  
1102 -1. Packing Info
1103 -
1104 1104  **Package Includes**:
1105 1105  
1106 -* RS485-BL x 1
1044 +* RS485-LN x 1
1107 1107  * Stick Antenna for LoRa RF part x 1
1108 1108  * Program cable x 1
1109 1109  
... ... @@ -1114,9 +1114,32 @@
1114 1114  * Package Size / pcs : 14.5 x 8 x 5 cm
1115 1115  * Weight / pcs : 170g
1116 1116  
1117 -1. Support
1055 += 10. FCC Caution for RS485LN-US915 =
1118 1118  
1119 -* 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.
1120 -* 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
1057 +Any Changes or modifications not expressly approved by the party responsible for compliance could void the user's authority to operate the equipment.
1121 1121  
1122 -[[support@dragino.com>>url:file:///D:/市场资料/说明书/LoRa/LT系列/support@dragino.com]]
1059 +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.
1060 +
1061 +
1062 +**IMPORTANT NOTE:**
1063 +
1064 +**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:
1065 +
1066 +—Reorient or relocate the receiving antenna.
1067 +
1068 +—Increase the separation between the equipment and receiver.
1069 +
1070 +—Connect the equipment into an outlet on a circuit different from that to which the receiver is connected.
1071 +
1072 +—Consult the dealer or an experienced radio/TV technician for help.
1073 +
1074 +
1075 +**FCC Radiation Exposure Statement:**
1076 +
1077 +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.
1078 +
1079 +
1080 += 11. Support =
1081 +
1082 +* 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.
1083 +* 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-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