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

Summary

Details

Page properties
Content
... ... @@ -76,8 +76,6 @@
76 76  * Automatic RF Sense and CAD with ultra-fast AFC.
77 77  * Packet engine up to 256 bytes with CRC.
78 78  
79 -
80 -
81 81  == 1.3 Features ==
82 82  
83 83  * LoRaWAN Class A & Class C protocol (default Class C)
... ... @@ -89,8 +89,6 @@
89 89  * Support Modbus protocol
90 90  * Support Interrupt uplink (Since hardware version v1.2)
91 91  
92 -
93 -
94 94  == 1.4 Applications ==
95 95  
96 96  * Smart Buildings & Home Automation
... ... @@ -100,8 +100,6 @@
100 100  * Smart Cities
101 101  * Smart Factory
102 102  
103 -
104 -
105 105  == 1.5 Firmware Change log ==
106 106  
107 107  [[RS485-LN Image files – Download link and Change log>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/]]
... ... @@ -289,8 +289,6 @@
289 289  )))
290 290  )))
291 291  
292 -
293 -
294 294  === 3.3.2 Configure sensors ===
295 295  
296 296  (((
... ... @@ -309,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
322 +3. Some RS485 device might has longer delay on reply, so user can use AT+CMDDL to set the timeout for getting reply after the RS485 command is sent. For example **AT+CMDDL1=1000** to send the open time to 1000ms
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. **
355 +* **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.**
381 +
382 +
394 394  )))
395 395  
396 396  (((
397 -(% style="color:#4f81bd" %)**Examples: AT+DATAUP=0**
386 +(% style="color:#037691" %)**Examples: AT+DATAUP=0**
387 +
388 +
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  
410 +(% style="color:#037691" %)**Examples: AT+DATAUP=1**
411 +
412 +
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,138 +423,98 @@
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
419 +1. PAYVER: Defined by AT+PAYVER
420 +1. PAYLOAD COUNT: Total how many uplinks of this sampling.
421 +1. PAYLOAD#: Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT)
422 +1. DATA: Valid value: max 8 bytes for each uplink so each uplink <= 11 bytes. For the last uplink, DATA will might less than 8 bytes
431 431  
432 -[[image:1653269916228-732.png||height="433" width="711"]]
424 +[[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
427 +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
429 +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
431 +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
433 +DATA3=the rest of Valid value of RETURN10= **30**
442 442  
443 -Below are the uplink payloads:
444 444  
445 -[[image:1653270130359-810.png]]
436 +(% style="color:red" %)Notice: In firmware v1.3, the Max bytes has been changed according to the max bytes in different Frequency Bands for lowest SF. As below:
446 446  
438 + ~* 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:**
440 + * 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)
442 + * 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).
444 + ~* 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).
447 +Below are the uplink payloads:
457 457  
449 +[[image:1654157178836-407.png]]
450 +
451 +
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.
454 +Except uplink periodically, RS485-LN is able to uplink on demand. The server send downlink command to RS485-LN and RS485 will uplink data base on the command.
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.
458 +**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.
460 +**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
464 +=== 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]]
466 +RS485-LN support external Interrupt uplink since hardware v1.2 release.
475 475  
476 -AT+INTMOD=0  Disable Interrupt
468 +[[image:1654157342174-798.png]]
477 477  
478 -AT+INTMOD=1  Interrupt trigger by rising or falling edge.
470 +Connect the Interrupt pin to RS485-LN INT port and connect the GND pin to V- port. When there is a high voltage (Max 24v) on INT pin. Device will send an uplink packet.
479 479  
480 -AT+INTMOD=2  Interrupt trigger by falling edge. ( Default Value)
481 481  
482 -AT+INTMOD=3  Interrupt trigger by rising edge.
473 +== 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|(((
475 +(% border="1" style="background-color:#4bacc6; color:white; width:734px" %)
476 +|**Size(bytes)**|(% style="width:120px" %)**2**|(% style="width:116px" %)**1**|(% style="width:386px" %)**Length depends on the return from the commands**
477 +|Value|(% style="width:120px" %)(((
490 490  Battery(mV)
491 491  
492 492  &
493 493  
494 494  Interrupt _Flag
495 -)))|(((
483 +)))|(% 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.
487 +)))|(% style="width:386px" %)If the valid payload is too long and exceed the maximum support payload length in server, server will show payload not provided in the LoRaWAN server.
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) {
492 +== 3.5 Configure RS485-BL via AT or Downlink ==
505 505  
506 -~/~/Payload Formats of RS485-BL Deceive
494 +User can configure RS485-LN via AT Commands or LoRaWAN Downlink Commands
507 507  
508 -return {
496 +There are two kinds of Commands:
509 509  
510 - ~/~/Battery,units:V
498 +* (% style="color:#4f81bd" %)**Common Commands**(%%): They should be available for each sensor, such as: change uplink interval, reset device. For firmware v1.3, user can find what common commands it supports: [[End Device AT Commands and Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]]
511 511  
512 - BatV:((bytes[0]<<8 | bytes[1])&0x7fff)/1000,
500 +* (% style="color:#4f81bd" %)**Sensor Related Commands**(%%): These commands are special designed for RS485-LN.  User can see these commands below:
513 513  
514 - ~/~/GPIO_EXTI 
515 515  
516 - EXTI_Trigger:(bytes[0] & 0x80)? "TRUE":"FALSE",
517 517  
518 - ~/~/payload of version
504 +=== 3.5.1 Common Commands ===
519 519  
520 - Pay_ver:bytes[2],
506 +They should be available for each of Dragino Sensors, such as: change uplink interval, reset device. For firmware v1.3, user can find what common commands it supports: [[End Device AT Commands and Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]]
521 521  
522 - };
523 523  
524 - }
509 +=== 3.5.2 Sensor related commands: ===
525 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 -There are two kinds of Commands:
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
544 -
545 -* **Sensor Related Commands**: These commands are special designed for RS485-BL.  User can see these commands below:
546 -
547 -1.
548 -11.
549 -111. Common Commands:
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]]
552 -
553 -
554 -1.
555 -11.
556 -111. Sensor related commands:
557 -
558 558  ==== Choose Device Type (RS485 or TTL) ====
559 559  
560 560  RS485-BL can connect to either RS485 sensors or TTL sensor. User need to specify what type of sensor need to connect.
1654157178836-407.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +179.9 KB
Content
1654157342174-798.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +31.9 KB
Content
1654158783574-851.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +40.6 KB
Content
image-20220602155039-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +24.6 KB
Content
image-20220602163333-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +48.2 KB
Content

Applications

Navigation

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