Skip to Content
Last modified by Mengting Qiu on 2025/07/14 09:59
From version 36.1
edited by Xiaoling
on 2022/06/02 15:50
Change comment: Uploaded new attachment "image-20220602155039-4.png", version {1}
To version 58.22
edited by Xiaoling
on 2022/06/06 11:25
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -6,12 +6,18 @@
6 6  **RS485-LN – RS485 to LoRaWAN Converter User Manual**
7 7  
8 8  
9 +
10 +
9 9  **Table of Contents:**
10 10  
13 +{{toc/}}
11 11  
12 12  
13 13  
14 14  
18 +
19 +
20 +
15 15  = 1.Introduction =
16 16  
17 17  == 1.1 What is RS485-LN RS485 to LoRaWAN Converter ==
... ... @@ -18,23 +18,33 @@
18 18  
19 19  (((
20 20  (((
27 +(((
21 21  The Dragino RS485-LN is a (% style="color:blue" %)**RS485 to LoRaWAN Converter**(%%). It converts the RS485 signal into LoRaWAN wireless signal which simplify the IoT installation and reduce the installation/maintaining cost.
22 22  )))
30 +)))
23 23  
24 24  (((
33 +(((
25 25  RS485-LN allows user to (% style="color:blue" %)**monitor / control RS485 devices**(%%) and reach extremely long ranges. It provides ultra-long range spread spectrum communication and high interference immunity whilst minimizing current consumption. It targets professional wireless sensor network applications such as irrigation systems, smart metering, smart cities, smartphone detection, building automation, and so on.
26 26  )))
36 +)))
27 27  
28 28  (((
39 +(((
29 29  (% style="color:blue" %)**For data uplink**(%%), RS485-LN sends user-defined commands to RS485 devices and gets the return from the RS485 devices. RS485-LN will process these returns according to user-define rules to get the final payload and upload to LoRaWAN server.
30 30  )))
42 +)))
31 31  
32 32  (((
45 +(((
33 33  (% style="color:blue" %)**For data downlink**(%%), RS485-LN runs in LoRaWAN Class C. When there downlink commands from LoRaWAN server, RS485-LN will forward the commands from LoRaWAN server to RS485 devices.
47 +)))
34 34  
49 +(((
35 35  (% style="color:blue" %)**Demo Dashboard for RS485-LN**(%%) connect to two energy meters: [[https:~~/~~/app.datacake.de/dashboard/d/58844a26-378d-4c5a-aaf5-b5b5b153447a>>url:https://app.datacake.de/dashboard/d/58844a26-378d-4c5a-aaf5-b5b5b153447a]]
36 36  )))
37 37  )))
53 +)))
38 38  
39 39  [[image:1653267211009-519.png||height="419" width="724"]]
40 40  
... ... @@ -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.
93 +* Packet engine up to 256 bytes with CRC
78 78  
79 79  == 1.3 Features ==
80 80  
... ... @@ -87,6 +87,7 @@
87 87  * Support Modbus protocol
88 88  * Support Interrupt uplink (Since hardware version v1.2)
89 89  
106 +
90 90  == 1.4 Applications ==
91 91  
92 92  * Smart Buildings & Home Automation
... ... @@ -96,6 +96,7 @@
96 96  * Smart Cities
97 97  * Smart Factory
98 98  
116 +
99 99  == 1.5 Firmware Change log ==
100 100  
101 101  [[RS485-LN Image files – Download link and Change log>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/]]
... ... @@ -105,9 +105,13 @@
105 105  
106 106  (((
107 107  (((
126 +(((
108 108  v1.2: Add External Interrupt Pin.
128 +)))
109 109  
130 +(((
110 110  v1.0: Release
132 +)))
111 111  
112 112  
113 113  )))
... ... @@ -135,7 +135,9 @@
135 135  == 3.1 How it works? ==
136 136  
137 137  (((
160 +(((
138 138  The RS485-LN is configured as LoRaWAN OTAA Class C mode by default. It has OTAA keys to join network. To connect a local LoRaWAN network, user just need to input the OTAA keys in the network server and power on the RS485-LN. It will auto join the network via OTAA.
162 +)))
139 139  
140 140  
141 141  )))
... ... @@ -159,7 +159,7 @@
159 159  [[image:1653268227651-549.png||height="592" width="720"]]
160 160  
161 161  (((
162 -The LG308 is already set to connect to [[TTN V3 network >>path:eu1.cloud.thethings.network/]]. So what we need to now is only configure the TTN V3:
186 +The LG308 is already set to connect to [[TTN V3 network >>path:https://www.thethingsnetwork.org/]]. So what we need to now is only configure the TTN V3:
163 163  )))
164 164  
165 165  (((
... ... @@ -211,7 +211,7 @@
211 211  
212 212  (((
213 213  (((
214 -There are plenty of RS485 devices in the market and each device has different command to read the valid data. To support these devices in flexible, RS485-LN supports flexible command set. User can use [[AT Commands>>path:#AT_COMMAND]] or LoRaWAN Downlink Command to configure what commands RS485-LN should send for each sampling and how to handle the return from RS485 devices.
238 +There are plenty of RS485 devices in the market and each device has different command to read the valid data. To support these devices in flexible, RS485-LN supports flexible command set. User can use [[AT Commands>>||anchor="H3.5ConfigureRS485-BLviaATorDownlink"]] or LoRaWAN Downlink Command to configure what commands RS485-LN should send for each sampling and how to handle the return from RS485 devices.
215 215  )))
216 216  
217 217  (((
... ... @@ -225,19 +225,19 @@
225 225  
226 226  To use RS485-LN to read data from RS485 sensors, connect the RS485-LN A/B traces to the sensors. And user need to make sure RS485-LN use the match UART setting to access the sensors. The related commands for UART settings are:
227 227  
228 -(% border="1" style="background-color:#ffffcc; color:green; width:782px" %)
229 -|(% style="width:128px" %)(((
252 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)
253 +|=(% style="width: 110px;" %)(((
230 230  **AT Commands**
231 -)))|(% style="width:305px" %)(((
255 +)))|=(% style="width: 190px;" %)(((
232 232  **Description**
233 -)))|(% style="width:346px" %)(((
257 +)))|=(% style="width: 190px;" %)(((
234 234  **Example**
235 235  )))
236 -|(% style="width:128px" %)(((
260 +|(% style="width:110px" %)(((
237 237  AT+BAUDR
238 -)))|(% style="width:305px" %)(((
262 +)))|(% style="width:190px" %)(((
239 239  Set the baud rate (for RS485 connection). Default Value is: 9600.
240 -)))|(% style="width:346px" %)(((
264 +)))|(% style="width:190px" %)(((
241 241  (((
242 242  AT+BAUDR=9600
243 243  )))
... ... @@ -246,11 +246,11 @@
246 246  Options: (1200,2400,4800,14400,19200,115200)
247 247  )))
248 248  )))
249 -|(% style="width:128px" %)(((
273 +|(% style="width:110px" %)(((
250 250  AT+PARITY
251 -)))|(% style="width:305px" %)(((
275 +)))|(% style="width:190px" %)(((
252 252  Set UART parity (for RS485 connection)
253 -)))|(% style="width:346px" %)(((
277 +)))|(% style="width:190px" %)(((
254 254  (((
255 255  AT+PARITY=0
256 256  )))
... ... @@ -259,9 +259,9 @@
259 259  Option: 0: no parity, 1: odd parity, 2: even parity
260 260  )))
261 261  )))
262 -|(% style="width:128px" %)(((
286 +|(% style="width:110px" %)(((
263 263  AT+STOPBIT
264 -)))|(% style="width:305px" %)(((
288 +)))|(% style="width:190px" %)(((
265 265  (((
266 266  Set serial stopbit (for RS485 connection)
267 267  )))
... ... @@ -269,7 +269,7 @@
269 269  (((
270 270  
271 271  )))
272 -)))|(% style="width:346px" %)(((
296 +)))|(% style="width:190px" %)(((
273 273  (((
274 274  AT+STOPBIT=0 for 1bit
275 275  )))
... ... @@ -283,6 +283,8 @@
283 283  )))
284 284  )))
285 285  
310 +
311 +
286 286  === 3.3.2 Configure sensors ===
287 287  
288 288  (((
... ... @@ -291,16 +291,18 @@
291 291  )))
292 292  )))
293 293  
294 -(% border="1" style="background-color:#ffffcc; color:green; width:806px" %)
295 -|**AT Commands**|(% style="width:418px" %)**Description**|(% style="width:256px" %)**Example**
296 -|AT+CFGDEV|(% style="width:418px" %)(((
320 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)
321 +|=(% style="width: 110px;" %)**AT Commands**|=(% style="width: 190px;" %)**Description**|=(% style="width: 190px;" %)**Example**
322 +|AT+CFGDEV|(% style="width:110px" %)(((
297 297  This command is used to configure the RS485/TTL devices; they won’t be used during sampling.
298 298  
299 299  AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,
300 300  
301 301  mm: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
302 -)))|(% style="width:256px" %)AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
328 +)))|(% style="width:190px" %)AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
303 303  
330 +
331 +
304 304  === 3.3.3 Configure read commands for each sampling ===
305 305  
306 306  (((
... ... @@ -346,8 +346,8 @@
346 346  
347 347  **AT+DATACUTx : **This command defines how to handle the return from AT+COMMANDx, max return length is 45 bytes.
348 348  
349 -(% border="1" style="background-color:#4bacc6; color:white; width:725px" %)
350 -|(% style="width:722px" %)(((
377 +(% border="1" style="background-color:#4bacc6; color:white; width:510px" %)
378 +|(% style="width:510px" %)(((
351 351  **AT+DATACUTx=a,b,c**
352 352  
353 353  * **a: length for the return of AT+COMMAND**
... ... @@ -416,602 +416,863 @@
416 416  
417 417  (% style="color:#4f81bd" %)**Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA**
418 418  
419 -1. Battery Info (2 bytes): Battery voltage
420 -1. PAYVER (1 byte): Defined by AT+PAYVER
421 -1. PAYLOAD COUNT (1 byte): Total how many uplinks of this sampling.
422 -1. PAYLOAD# (1 byte): Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT)
423 -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
424 424  
425 -[[image:1653269916228-732.png||height="433" width="711"]]
448 +1. PAYVER: Defined by AT+PAYVER
449 +1. PAYLOAD COUNT: Total how many uplinks of this sampling.
450 +1. PAYLOAD#: Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT)
451 +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
426 426  
453 +[[image:image-20220602155039-4.png]]
427 427  
428 -So totally there will be 3 uplinks for this sampling, each uplink includes 6 bytes DATA
429 429  
430 -DATA1=RETURN1 Valid Value = (% style="background-color:green; color:white" %)20 20 0a 33 90 41
456 +So totally there will be 3 uplinks for this sampling, each uplink include 8 bytes DATA
431 431  
432 -DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10=(% style="background-color:green; color:white" %) 02 aa 05 81 0a 20
458 +DATA1=RETURN1 Valid Value + the first two of Valid value of RETURN10= **20 20 0a 33 90 41 02 aa**
433 433  
434 -DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 = (% style="background-color:green; color:white" %)20 20 20 2d 30
460 +DATA2=3^^rd^^ ~~ 10^^th^^ byte of Valid value of RETURN10= **05 81 0a 20 20 20 20 2d**
435 435  
436 -Below are the uplink payloads:
462 +DATA3=the rest of Valid value of RETURN10= **30**
437 437  
438 -[[image:1653270130359-810.png]]
439 439  
465 +(% 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:
440 440  
441 -(% style="color:red" %)**Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:**
467 + ~* For AU915/AS923 bands, if UplinkDwell time=0, max 51 bytes for each uplink.
442 442  
443 - ~* For AU915/AS923 bands, if UplinkDwell time=0, max 51 bytes for each uplink ( so 51 -5 = 46 max valid date)
469 + * For AU915/AS923 bands, if UplinkDwell time=0, max 11 bytes for each uplink.
444 444  
445 - * For AU915/AS923 bands, if UplinkDwell time=1, max 11 bytes for each uplink ( so 11 -5 = 6 max valid date).
471 + * For US915 band, max 11 bytes for each uplink.
446 446  
447 - * For US915 band, max 11 bytes for each uplink ( so 11 -5 = 6 max valid date).
473 + ~* For all other bands: max 51 bytes for each uplink.
448 448  
449 - ~* For all other bands: max 51 bytes for each uplink  ( so 51 -5 = 46 max valid date).
450 450  
451 -=== 3.3.5 Uplink on demand ===
476 +Below are the uplink payloads:
452 452  
453 -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.
478 +[[image:1654157178836-407.png]]
454 454  
455 -Downlink control command:
456 456  
457 -[[0x08 command>>path:#downlink_08]]: Poll an uplink with current command set in RS485-BL.
481 +=== 3.3.5 Uplink on demand ===
458 458  
459 -[[0xA8 command>>path:#downlink_A8]]: Send a command to RS485-BL and uplink the output from sensors.
483 +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.
460 460  
485 +Downlink control command:
461 461  
487 +**0x08 command**: Poll an uplink with current command set in RS485-LN.
462 462  
463 -1.
464 -11.
465 -111. Uplink on Interrupt
489 +**0xA8 command**: Send a command to RS485-LN and uplink the output from sensors.
466 466  
467 -Put the interrupt sensor between 3.3v_out and GPIO ext.[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image022.png]]
468 468  
469 -AT+INTMOD=0  Disable Interrupt
470 470  
471 -AT+INTMOD=1  Interrupt trigger by rising or falling edge.
493 +=== 3.3.6 Uplink on Interrupt ===
472 472  
473 -AT+INTMOD=2  Interrupt trigger by falling edge. ( Default Value)
495 +RS485-LN support external Interrupt uplink since hardware v1.2 release.
474 474  
475 -AT+INTMOD=3  Interrupt trigger by rising edge.
497 +[[image:1654157342174-798.png]]
476 476  
499 +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.
477 477  
478 -1.
479 -11. Uplink Payload
480 480  
481 -|**Size(bytes)**|**2**|**1**|**Length depends on the return from the commands**
482 -|Value|(((
483 -Battery(mV)
502 +== 3.4 Uplink Payload ==
484 484  
485 -&
486 486  
487 -Interrupt _Flag
488 -)))|(((
489 -PAYLOAD_VER
505 +[[image:image-20220606110929-1.png]]
490 490  
491 -
492 -)))|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 -
494 494  Below is the decoder for the first 3 bytes. The rest bytes are dynamic depends on different RS485 sensors.
495 495  
496 496  
497 -function Decoder(bytes, port) {
510 +== 3.5 Configure RS485-BL via AT or Downlink ==
498 498  
499 -~/~/Payload Formats of RS485-BL Deceive
512 +(((
513 +User can configure RS485-LN via AT Commands or LoRaWAN Downlink Commands
514 +)))
500 500  
501 -return {
502 -
503 - ~/~/Battery,units:V
504 -
505 - BatV:((bytes[0]<<8 | bytes[1])&0x7fff)/1000,
506 -
507 - ~/~/GPIO_EXTI 
508 -
509 - EXTI_Trigger:(bytes[0] & 0x80)? "TRUE":"FALSE",
510 -
511 - ~/~/payload of version
512 -
513 - Pay_ver:bytes[2],
514 -
515 - };
516 -
517 - }
518 -
519 -
520 -
521 -
522 -
523 -
524 -
525 -TTN V3 uplink screen shot.
526 -
527 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png]]
528 -
529 -1.
530 -11. Configure RS485-BL via AT or Downlink
531 -
532 -User can configure RS485-BL via [[AT Commands >>path:#_​Using_the_AT]]or LoRaWAN Downlink Commands
533 -
516 +(((
534 534  There are two kinds of Commands:
518 +)))
535 535  
536 -* **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
520 +* (((
521 +(% 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: [[AT Commands and Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]]
522 +)))
537 537  
538 -* **Sensor Related Commands**: These commands are special designed for RS485-BL.  User can see these commands below:
524 +* (((
525 +(% style="color:#4f81bd" %)**Sensor Related Commands**(%%): These commands are special designed for RS485-LN.  User can see these commands below:
526 +)))
539 539  
540 -1.
541 -11.
542 -111. Common Commands:
528 +(((
529 +
530 +)))
543 543  
544 -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]]
545 545  
533 +=== 3.5.1 Common Commands ===
546 546  
547 -1.
548 -11.
549 -111. Sensor related commands:
535 +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]]
550 550  
551 -==== Choose Device Type (RS485 or TTL) ====
552 552  
553 -RS485-BL can connect to either RS485 sensors or TTL sensor. User need to specify what type of sensor need to connect.
538 +=== 3.5.2 Sensor related commands ===
554 554  
555 -* AT Command
540 +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.
556 556  
557 -**AT+MOD=1** ~/~/ Set to support RS485-MODBUS type sensors. User can connect multiply RS485 , Modbus sensors to the A / B pins.
542 +[[image:image-20220602163333-5.png||height="263" width="1160"]]
558 558  
559 -**AT+MOD=2** ~/~/ Set to support TTL Level sensors, User can connect one TTL Sensor to the TXD/RXD/GND pins.
544 +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)
560 560  
561 561  
562 -* Downlink Payload
547 +=== 3.5.3 Sensor related commands ===
563 563  
564 -**0A aa**     à same as AT+MOD=aa
565 565  
566 566  
567 567  
568 -==== [[RS485 Debug Command>>path:#downlink_A8]] (AT+CFGDEV) ====
552 +==== **RS485 Debug Command** ====
569 569  
570 -This command is used to configure the RS485 or TTL sensors; they won’t be used during sampling.
554 +(((
555 +This command is used to configure the RS485 devices; they won’t be used during sampling.
556 +)))
571 571  
572 -* AT Command
558 +* (((
559 +**AT Command**
560 +)))
573 573  
574 -AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
562 +(% class="box infomessage" %)
563 +(((
564 +(((
565 +**AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m**
566 +)))
567 +)))
575 575  
576 -m: 0: no CRC; 1: add CRC-16/MODBUS in the end of this command.
569 +(((
570 +m: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
571 +)))
577 577  
573 +* (((
574 +**Downlink Payload**
575 +)))
578 578  
579 -
580 -* Downlink Payload
581 -
577 +(((
582 582  Format: A8 MM NN XX XX XX XX YY
579 +)))
583 583  
581 +(((
584 584  Where:
583 +)))
585 585  
586 -* MM: 1: add CRC-16/MODBUS ; 0: no CRC
587 -* NN: The length of RS485 command
588 -* XX XX XX XX: RS485 command total NN bytes
589 -* 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
585 +* (((
586 +MM: 1: add CRC-16/MODBUS ; 0: no CRC
587 +)))
588 +* (((
589 +NN: The length of RS485 command
590 +)))
591 +* (((
592 +XX XX XX XX: RS485 command total NN bytes
593 +)))
594 +* (((
595 +(((
596 +YY: How many bytes will be uplink from the return of this RS485 command,
597 +)))
590 590  
591 -**Example 1:**
599 +* (((
600 +if YY=0, RS485-LN will execute the downlink command without uplink;
601 +)))
602 +* (((
603 +if YY>0, RS485-LN will uplink total YY bytes from the output of this RS485 command; Fport=200
604 +)))
605 +* (((
606 +if YY=FF, RS485-LN will uplink RS485 output with the downlink command content; Fport=200.
607 +)))
608 +)))
592 592  
610 +(((
611 +**Example 1** ~-~-> Configure without ask for uplink (YY=0)
612 +)))
613 +
614 +(((
593 593  To connect a Modbus Alarm with below commands.
616 +)))
594 594  
595 -* The command to active alarm is: 0A 05 00 04 00 01 4C B0. Where 0A 05 00 04 00 01 is the Modbus command to read the register 00 40 where stored the DI status. The 4C B0 is the CRC-16/MODBUS which calculate manually.
618 +* (((
619 +The command to active alarm is: 0A 05 00 04 00 01 4C B0. Where 0A 05 00 04 00 01 is the Modbus command to read the register 00 40 where stored the DI status. The 4C B0 is the CRC-16/MODBUS which calculate manually.
620 +)))
596 596  
597 -* The command to deactivate alarm is: 0A 05 00 04 00 00 8D 70. Where 0A 05 00 04 00 00 is the Modbus command to read the register 00 40 where stored the DI status. The 8D 70 is the CRC-16/MODBUS which calculate manually.
622 +* (((
623 +The command to deactivate alarm is: 0A 05 00 04 00 00 8D 70. Where 0A 05 00 04 00 00 is the Modbus command to read the register 00 40 where stored the DI status. The 8D 70 is the CRC-16/MODBUS which calculate manually.
624 +)))
598 598  
626 +(((
599 599  So if user want to use downlink command to control to RS485 Alarm, he can use:
628 +)))
600 600  
601 -**A8 01 06 0A 05 00 04 00 01 00**: to activate the RS485 Alarm
630 +(((
631 +(% style="color:#4f81bd" %)**A8 01 06 0A 05 00 04 00 01 00**(%%): to activate the RS485 Alarm
632 +)))
602 602  
603 -**A8 01 06 0A 05 00 04 00 00 00**: to deactivate the RS485 Alarm
634 +(((
635 +(% style="color:#4f81bd" %)**A8 01 06 0A 05 00 04 00 00 00**(%%): to deactivate the RS485 Alarm
636 +)))
604 604  
638 +(((
605 605  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.
640 +)))
606 606  
642 +(((
643 +
644 +)))
607 607  
608 -**Example 2:**
646 +(((
647 +**Example 2** ~-~-> Configure with requesting uplink and original downlink command (**YY=FF**)
648 +)))
609 609  
610 -Check TTL Sensor return:
650 +(((
651 +User in IoT server send a downlink command: (% style="color:#4f81bd" %)**A8 01 06 0A 08 00 04 00 01 YY**
652 +)))
611 611  
612 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image024.png]]
654 +(((
655 +
656 +)))
613 613  
658 +(((
659 +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:
660 +)))
614 614  
662 +(((
663 + **A8** (% style="color:#4f81bd" %)**0A 08 00 04 00  **(% style="color:red" %)**01 06** ** **(% style="color:green" %)**0A 08 00 04 00 00**
664 +)))
615 615  
666 +(((
667 + [[image:1654159460680-153.png]]
668 +)))
616 616  
617 -==== Set Payload version ====
618 618  
671 +
672 +
673 +==== **Set Payload version** ====
674 +
675 +(((
619 619  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.
677 +)))
620 620  
621 -* AT Command:
679 +* (((
680 +**AT Command:**
681 +)))
622 622  
623 -AT+PAYVER: Set PAYVER field = 1
683 +(% class="box infomessage" %)
684 +(((
685 +(((
686 +**AT+PAYVER: Set PAYVER field = 1**
687 +)))
688 +)))
624 624  
690 +* (((
691 +**Downlink Payload:**
692 +)))
625 625  
626 -* Downlink Payload:
694 +(((
695 +**0xAE 01**  ~-~-> Set PAYVER field =  0x01
696 +)))
627 627  
628 -0xAE 01   à Set PAYVER field =  0x01
698 +(((
699 +**0xAE 0F**   ~-~-> Set PAYVER field =  0x0F
700 +)))
629 629  
630 -0xAE 0F   à Set PAYVER field =  0x0F
631 631  
632 632  
633 -==== Set RS485 Sampling Commands ====
634 634  
635 -AT+COMMANDx, AT+DATACUTx and AT+SEARCHx
705 +==== **Set RS485 Sampling Commands** ====
636 636  
637 -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]].
707 +(((
708 +AT+COMMANDx or AT+DATACUTx
709 +)))
638 638  
711 +(((
712 +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"]].
713 +)))
639 639  
640 -* AT Command:
715 +(((
716 +
717 +)))
641 641  
642 -AT+COMMANDx: Configure RS485 read command to sensor.
719 +* (((
720 +**AT Command:**
721 +)))
643 643  
644 -AT+DATACUTx: Configure how to handle return from RS485 devices.
723 +(% class="box infomessage" %)
724 +(((
725 +(((
726 +**AT+COMMANDx: Configure RS485 read command to sensor.**
727 +)))
728 +)))
645 645  
646 -AT+SEARCHx: Configure search command
730 +(% class="box infomessage" %)
731 +(((
732 +(((
733 +**AT+DATACUTx: Configure how to handle return from RS485 devices.**
734 +)))
735 +)))
647 647  
737 +(((
738 +
739 +)))
648 648  
649 -* Downlink Payload:
741 +* (((
742 +**Downlink Payload:**
743 +)))
650 650  
651 -0xAF downlink command can be used to set AT+COMMANDx or AT+DATACUTx.
745 +(((
746 +**0xAF** downlink command can be used to set AT+COMMANDx or AT+DATACUTx.
747 +)))
652 652  
653 -Note: if user use AT+COMMANDx to add a new command, he also need to send AT+DATACUTx downlink.
749 +(((
750 +(% style="color:red" %)**Note**(%%): if user use AT+COMMANDx to add a new command, he also need to send AT+DATACUTx downlink.
751 +)))
654 654  
753 +(((
655 655  Format: AF MM NN LL XX XX XX XX YY
755 +)))
656 656  
757 +(((
657 657  Where:
759 +)))
658 658  
659 -* MM: the ATCOMMAND or AT+DATACUT to be set. Value from 01 ~~ 0F,
660 -* NN: 0: no CRC; 1: add CRC-16/MODBUS ; 2: set the AT+DATACUT value.
661 -* LL: The length of AT+COMMAND or AT+DATACUT command
662 -* XX XX XX XX: AT+COMMAND or AT+DATACUT command
663 -* 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.
761 +* (((
762 +MM: the ATCOMMAND or AT+DATACUT to be set. Value from 01 ~~ 0F,
763 +)))
764 +* (((
765 +NN:  0: no CRC; 1: add CRC-16/MODBUS ; 2: set the AT+DATACUT value.
766 +)))
767 +* (((
768 +LL:  The length of AT+COMMAND or AT+DATACUT command
769 +)))
770 +* (((
771 +XX XX XX XX: AT+COMMAND or AT+DATACUT command
772 +)))
773 +* (((
774 +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.
775 +)))
664 664  
665 -Example:
777 +(((
778 +**Example:**
779 +)))
666 666  
667 -**AF 03 01 06 0A 05 00 04 00 01 00**: Same as AT+COMMAND3=0A 05 00 04 00 01,1
781 +(((
782 +(% 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
783 +)))
668 668  
669 -**AF 03 02 06 10 01 05 06 09 0A 00**: Same as AT+DATACUT3=**16**,**1**,**5+6+9+10**
785 +(((
786 +(% 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**
787 +)))
670 670  
671 -**AF 03 02 06 0B 02 05 07 08 0A 00**: Same as AT+DATACUT3=**11**,**2**,**5~~7+8~~10**
789 +(((
790 +(% 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**
791 +)))
672 672  
673 673  
674 -0xAB downlink command can be used for set AT+SEARCHx
675 675  
676 -Example: **AB aa 01 03 xx xx xx** (03 here means there are total 3 bytes after 03) So
677 677  
678 -* AB aa 01 03 xx xx xx  same as AT+SEARCHaa=1,xx xx xx
679 -* 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
796 +==== **Fast command to handle MODBUS device** ====
680 680  
681 -**AB aa 02 03 xx xx xx 02 yy yy**  same as **AT+SEARCHaa=2,xx xx xx+yy yy**
798 +(((
799 +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]].
800 +)))
682 682  
802 +(((
803 +This command is valid since v1.3 firmware version
804 +)))
683 683  
684 -==== Fast command to handle MODBUS device ====
806 +(((
807 +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.
808 +)))
685 685  
686 -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]].
810 +(((
811 +
812 +)))
687 687  
688 -This command is valid since v1.3 firmware version
814 +(((
815 +**Example:**
816 +)))
689 689  
818 +* (((
819 +AT+MBFUN=1 and AT+DATACUT1/AT+DATACUT2 are not configure (0,0,0). So RS485-LN.
820 +)))
821 +* (((
822 +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.
823 +)))
824 +* (((
825 +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.
826 +)))
690 690  
691 -AT+MBFUN has only two value:
828 +[[image:image-20220602165351-6.png]]
692 692  
693 -* AT+MBFUN=1: Enable Modbus reading. And get response base on the MODBUS return
830 +[[image:image-20220602165351-7.png]]
694 694  
695 -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.
696 696  
697 -* AT+MBFUN=0: Disable Modbus fast reading.
698 698  
699 -Example:
700 700  
701 -* AT+MBFUN=1 and AT+DATACUT1/AT+DATACUT2 are not configure (0,0,0).
702 -* 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.
703 -* 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.
835 +==== **RS485 command timeout** ====
704 704  
705 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image025.png]]
837 +(((
838 +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.
839 +)))
706 706  
841 +(((
842 +Default value: 0, range:  0 ~~ 65 seconds
843 +)))
707 707  
708 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image026.png]]
845 +* (((
846 +**AT Command:**
847 +)))
709 709  
849 +(% class="box infomessage" %)
850 +(((
851 +(((
852 +**AT+CMDDLaa=hex(bb cc)*1000**
853 +)))
854 +)))
710 710  
711 -* Downlink Commands:
856 +(((
857 +**Example:**
858 +)))
712 712  
713 -A9 aa -à Same as AT+MBFUN=aa
860 +(((
861 +**AT+CMDDL1=1000** to send the open time to 1000ms
862 +)))
714 714  
864 +(((
865 +
866 +)))
715 715  
716 -==== RS485 command timeout ====
868 +* (((
869 +**Downlink Payload:**
870 +)))
717 717  
718 -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.
872 +(((
873 +**0x AA aa bb cc**
874 +)))
719 719  
720 -Default value: 0, range:  0 ~~ 5 seconds
876 +(((
877 +Same as: AT+CMDDLaa=hex(bb cc)*1000
878 +)))
721 721  
880 +(((
881 + **Example:**
882 +)))
722 722  
723 -* AT Command:
884 +(((
885 + 0xAA 01 00 01  ~-~-> Same as **AT+CMDDL1=1000 ms**
886 +)))
724 724  
725 -AT+CMDDLaa=hex(bb cc)
726 726  
727 -Example:
728 728  
729 -**AT+CMDDL1=1000** to send the open time to 1000ms
730 730  
891 +==== **Uplink payload mode** ====
731 731  
732 -* Downlink Payload:
893 +(((
894 +Define to use one uplink or multiple uplinks for the sampling.
895 +)))
733 733  
734 -0x AA aa bb cc
897 +(((
898 +The use of this command please see: [[Compose Uplink payload>>||anchor="H3.3.4Composetheuplinkpayload"]]
899 +)))
735 735  
736 -Same as: AT+CMDDLaa=hex(bb cc)
901 +* (((
902 +**AT Command:**
903 +)))
737 737  
738 - Example:
905 +(% class="box infomessage" %)
906 +(((
907 +(((
908 +**AT+DATAUP=0**
909 +)))
910 +)))
739 739  
740 - 0xAA 01 03 E8  à Same as **AT+CMDDL1=1000 ms**
912 +(% class="box infomessage" %)
913 +(((
914 +(((
915 +**AT+DATAUP=1**
916 +)))
917 +)))
741 741  
919 +(((
920 +
921 +)))
742 742  
743 -==== [[Uplink>>path:#downlink_A8]] payload mode ====
923 +* (((
924 +**Downlink Payload:**
925 +)))
744 744  
745 -Define to use one uplink or multiple uplinks for the sampling.
927 +(((
928 +**0xAD 00**  **~-~->** Same as AT+DATAUP=0
929 +)))
746 746  
747 -The use of this command please see: [[Compose Uplink payload>>path:#DataUP]]
931 +(((
932 +**0xAD 01**  **~-~->** Same as AT+DATAUP=1
933 +)))
748 748  
749 -* AT Command:
750 750  
751 -AT+DATAUP=0
752 752  
753 -AT+DATAUP=1
754 754  
938 +==== **Manually trigger an Uplink** ====
755 755  
756 -* Downlink Payload:
940 +(((
941 +Ask device to send an uplink immediately.
942 +)))
757 757  
758 -0xAD 00   à Same as AT+DATAUP=0
944 +* (((
945 +**AT Command:**
946 +)))
759 759  
760 -0xAD 01   à Same as AT+DATAUP=1
948 +(((
949 +No AT Command for this, user can press the [[ACT button>>||anchor="H3.7Buttons"]] for 1 second for the same.
950 +)))
761 761  
952 +(((
953 +
954 +)))
762 762  
763 -==== Manually trigger an Uplink ====
956 +* (((
957 +**Downlink Payload:**
958 +)))
764 764  
765 -Ask device to send an uplink immediately.
960 +(((
961 +**0x08 FF**, RS485-LN will immediately send an uplink.
962 +)))
766 766  
767 -* Downlink Payload:
768 768  
769 -0x08 FF, RS485-BL will immediately send an uplink.
770 770  
771 771  
772 -==== Clear RS485 Command ====
967 +==== **Clear RS485 Command** ====
773 773  
969 +(((
774 774  The AT+COMMANDx and AT+DATACUTx settings are stored in special location, user can use below command to clear them.
971 +)))
775 775  
973 +* (((
974 +**AT Command:**
975 +)))
776 776  
777 -* AT Command:
778 -
977 +(((
779 779  **AT+CMDEAR=mm,nn**   mm: start position of erase ,nn: stop position of erase
979 +)))
780 780  
981 +(((
781 781  Etc. AT+CMDEAR=1,10 means erase AT+COMMAND1/AT+DATACUT1 to AT+COMMAND10/AT+DATACUT10
983 +)))
782 782  
985 +(((
783 783  Example screen shot after clear all RS485 commands. 
987 +)))
784 784  
989 +(((
990 +
991 +)))
785 785  
786 -
993 +(((
787 787  The uplink screen shot is:
995 +)))
788 788  
789 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png]]
997 +[[image:1654160691922-496.png]]
790 790  
791 791  
792 -* Downlink Payload:
1000 +* (((
1001 +**Downlink Payload:**
1002 +)))
793 793  
794 -0x09 aa bb same as AT+CMDEAR=aa,bb
1004 +(((
1005 +**0x09 aa bb** same as AT+CMDEAR=aa,bb
1006 +)))
795 795  
796 796  
797 -==== Set Serial Communication Parameters ====
798 798  
1010 +
1011 +==== **Set Serial Communication Parameters** ====
1012 +
1013 +(((
799 799  Set the Rs485 serial communication parameters:
1015 +)))
800 800  
801 -* AT Command:
1017 +* (((
1018 +**AT Command:**
1019 +)))
802 802  
1021 +(((
803 803  Set Baud Rate:
1023 +)))
804 804  
805 -AT+BAUDR=9600    ~/~/ Options: (1200,2400,4800,14400,19200,115200)
1025 +(% class="box infomessage" %)
1026 +(((
1027 +(((
1028 +**AT+BAUDR=9600**    ~/~/ Options: (1200,2400,4800,14400,19200,115200)
1029 +)))
1030 +)))
806 806  
1032 +(((
1033 +Set UART Parity
1034 +)))
807 807  
808 -Set UART parity
1036 +(% class="box infomessage" %)
1037 +(((
1038 +(((
1039 +**AT+PARITY=0**    ~/~/ Option: 0: no parity, 1: odd parity, 2: even parity
1040 +)))
1041 +)))
809 809  
810 -AT+PARITY=0    ~/~/ Option: 0: no parity, 1: odd parity, 2: even parity
811 -
812 -
1043 +(((
813 813  Set STOPBIT
1045 +)))
814 814  
815 -AT+STOPBIT=0    ~/~/ Option: 0 for 1bit; 1 for 1.5 bit ; 2 for 2 bits
1047 +(% class="box infomessage" %)
1048 +(((
1049 +(((
1050 +**AT+STOPBIT=0**    ~/~/ Option: 0 for 1bit; 1 for 1.5 bit ; 2 for 2 bits
1051 +)))
1052 +)))
816 816  
1054 +(((
1055 +
1056 +)))
817 817  
818 -* Downlink Payload:
1058 +* (((
1059 +**Downlink Payload:**
1060 +)))
819 819  
820 -A7 01 aa bb: Same  AT+BAUDR=hex(aa bb)*100
1062 +(((
1063 +**A7 01 aa bb**: Same  AT+BAUDR=hex(aa bb)*100
1064 +)))
821 821  
822 -Example:
1066 +(((
1067 +**Example:**
1068 +)))
823 823  
824 -* A7 01 00 60   same as AT+BAUDR=9600
825 -* A7 01 04 80  same as AT+BAUDR=115200
1070 +* (((
1071 +A7 01 00 60   same as AT+BAUDR=9600
1072 +)))
1073 +* (((
1074 +A7 01 04 80  same as AT+BAUDR=115200
1075 +)))
826 826  
1077 +(((
827 827  A7 02 aa: Same as  AT+PARITY=aa  (aa value: 00 , 01 or 02)
1079 +)))
828 828  
1081 +(((
829 829  A7 03 aa: Same as  AT+STOPBIT=aa  (aa value: 00 , 01 or 02)
1083 +)))
830 830  
831 831  
832 -==== Control output power duration ====
833 833  
834 -User can set the output power duration before each sampling.
835 835  
836 -* AT Command:
1088 +== 3.6 Listening mode for RS485 network ==
837 837  
838 -Example:
1090 +(((
1091 +This feature support since firmware v1.4
1092 +)))
839 839  
840 -AT+3V3T=1000 ~/~/ 3V3 output power will open 1s before each sampling.
1094 +(((
1095 +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.
1096 +)))
841 841  
842 -AT+5VT=1000 ~/~/ +5V output power will open 1s before each sampling.
1098 +[[image:image-20220602171200-8.png||height="567" width="1007"]]
843 843  
1100 +(((
1101 +To enable the listening mode, use can run the command AT+RXMODE.
1102 +)))
844 844  
845 -* LoRaWAN Downlink Command:
1104 +(((
1105 +
1106 +)))
846 846  
847 -07 01 aa bb  Same as AT+5VT=(aa bb)
1108 +(% border="1" cellspacing="10" style="background-color:#ffffcc; width:500px" %)
1109 +|=(% style="width: 161px;" %)(((
1110 +**Command example:**
1111 +)))|=(% style="width: 337px;" %)(((
1112 +**Function**
1113 +)))
1114 +|(% style="width:161px" %)(((
1115 +AT+RXMODE=1,10
1116 +)))|(% style="width:337px" %)(((
1117 +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.
1118 +)))
1119 +|(% style="width:161px" %)(((
1120 +AT+RXMODE=2,500
1121 +)))|(% style="width:337px" %)(((
1122 +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
1123 +)))
1124 +|(% style="width:161px" %)(((
1125 +AT+RXMODE=0,0
1126 +)))|(% style="width:337px" %)(((
1127 +Disable listening mode. This is the default settings.
1128 +)))
1129 +|(% style="width:161px" %)(((
1130 +
1131 +)))|(% style="width:337px" %)(((
1132 +A6 aa bb cc  same as AT+RXMODE=aa,(bb<<8 | cc)
1133 +)))
848 848  
849 -07 02 aa bb  Same as AT+3V3T=(aa bb)
1135 +(((
1136 +**Downlink Command:**
1137 +)))
850 850  
1139 +(((
1140 +**0xA6 aa bb cc ** same as AT+RXMODE=aa,(bb<<8 | cc)
1141 +)))
851 851  
1143 +(((
1144 +
1145 +)))
852 852  
1147 +(((
1148 +**Example**:
1149 +)))
853 853  
854 -1.
855 -11. Buttons
1151 +(((
1152 +The RS485-LN is set to AT+RXMODE=2,1000
1153 +)))
856 856  
857 -|**Button**|**Feature**
858 -|**RST**|Reboot RS485-BL
1155 +(((
1156 +There is a two Modbus commands in the RS485 network as below:
1157 +)))
859 859  
860 -1.
861 -11. +3V3 Output
1159 +(((
1160 +The Modbus master send a command: (% style="background-color:#ffc000" %)01 03 00 00 00 02 c4 0b
1161 +)))
862 862  
863 -RS485-BL has a Controllable +3V3 output, user can use this output to power external sensor.
1163 +(((
1164 +And Modbus slave reply with: (% style="background-color:green" %)01 03 04 00 00 00 00 fa 33
1165 +)))
864 864  
865 -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. 
1167 +(((
1168 +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
1169 +)))
866 866  
1171 +(((
1172 +[[image:image-20220602171200-9.png]]
1173 +)))
867 867  
868 -The +3V3 output time can be controlled by AT Command.
1175 +(((
1176 +
1177 +)))
869 869  
870 -**AT+3V3T=1000**
1179 +(((
1180 +(% 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.
1181 +)))
871 871  
872 -Means set +3v3 valid time to have 1000ms. So, the real +3v3 output will actually have 1000ms + sampling time for other sensors.
873 873  
1184 +== 3.7 Buttons ==
874 874  
875 -By default, the AT+3V3T=0. This is a special case, means the +3V3 output is always on at any time
876 876  
1187 +(% border="1" style="background-color:#f7faff; width:500px" %)
1188 +|=**Button**|=(% style="width: 1420px;" %)**Feature**
1189 +|**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**
1190 +|**RST**|(% style="width:1420px" %)Reboot RS485
1191 +|**PRO**|(% style="width:1420px" %)Use for upload image, see [[How to Update Image>>||anchor="H6.1Howtoupgradetheimage3F"]]
877 877  
878 -1.
879 -11. +5V Output
1193 +== 3.8 LEDs ==
880 880  
881 -RS485-BL has a Controllable +5V output, user can use this output to power external sensor.
1195 +(% border="1" style="background-color:#f7faff; width:500px" %)
1196 +|=**LEDs**|=**Feature**
1197 +|**PWR**|Always on if there is power
1198 +|**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.
882 882  
883 -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. 
1200 += 4. Case Study =
884 884  
1202 +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]]
885 885  
886 -The 5V output time can be controlled by AT Command.
887 887  
888 -**AT+5VT=1000**
1205 += 5. Use AT Command =
889 889  
890 -Means set 5V valid time to have 1000ms. So, the real 5V output will actually have 1000ms + sampling time for other sensors.
1207 +== 5.1 Access AT Command ==
891 891  
1209 +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.
892 892  
893 -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.
1211 +[[image:1654162355560-817.png]]
894 894  
895 895  
1214 +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:
896 896  
1216 +[[image:1654162368066-342.png]]
897 897  
898 -1.
899 -11. LEDs
900 900  
901 -|**LEDs**|**Feature**
902 -|**LED1**|Blink when device transmit a packet.
1219 +More detail AT Command manual can be found at [[AT Command Manual>>https://www.dragino.com/downloads/index.php?dir=LT_LoRa_IO_Controller/LT33222-L/]]
903 903  
904 -1.
905 -11. Switch Jumper
906 906  
907 -|**Switch Jumper**|**Feature**
908 -|**SW1**|(((
909 -ISP position: Upgrade firmware via UART
1222 +== 5.2 Common AT Command Sequence ==
910 910  
911 -Flash position: Configure device, check running status.
1224 +=== 5.2.1 Multi-channel ABP mode (Use with SX1301/LG308) ===
1225 +
1226 +If device has not joined network yet:
1227 +
1228 +(% class="box infomessage" %)
1229 +(((
1230 +**AT+FDR**
912 912  )))
913 -|**SW2**|(((
914 -5V position: set to compatible with 5v I/O.
915 915  
916 -3.3v position: set to compatible with 3.3v I/O.,
1233 +(% class="box infomessage" %)
1234 +(((
1235 +**AT+NJM=0**
917 917  )))
918 918  
919 -+3.3V: is always ON
1238 +(% class="box infomessage" %)
1239 +(((
1240 +**ATZ**
1241 +)))
920 920  
921 -+5V: Only open before every sampling. The time is by default, it is AT+5VT=0.  Max open time. 5000 ms.
922 922  
923 -1. Case Study
1244 +If device already joined network:
924 924  
925 -User can check this URL for some case studies.
1246 +(% class="box infomessage" %)
1247 +(((
1248 +**AT+NJM=0**
1249 +)))
926 926  
927 -[[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]]
1251 +(% class="box infomessage" %)
1252 +(((
1253 +**ATZ**
1254 +)))
928 928  
929 929  
1257 +=== 5.5.2 Single-channel ABP mode (Use with LG01/LG02) ===
930 930  
931 931  
932 -1. Use AT Command
933 -11. Access AT Command
1260 +(% style="background-color:#dcdcdc" %)**AT+FDR** (%%) Reset Parameters to Factory Default, Keys Reserve
934 934  
935 -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.
1262 +(% style="background-color:#dcdcdc" %)**AT+NJM=0 **(%%)Set to ABP mode
936 936  
937 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image027.png]]
1264 +(% style="background-color:#dcdcdc" %)**AT+ADR=0** (%%)Set the Adaptive Data Rate Off
938 938  
1266 +(% style="background-color:#dcdcdc" %)**AT+DR=5**   (%%)Set Data Rate
939 939  
940 -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:
1268 +(% style="background-color:#dcdcdc" %)**AT+TDC=60000** (%%) Set transmit interval to 60 seconds
941 941  
942 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image028.png]]
1270 +(% style="background-color:#dcdcdc" %)**AT+CHS=868400000**(%%) Set transmit frequency to 868.4Mhz
943 943  
1272 +(% style="background-color:#dcdcdc" %)**AT+RX2FQ=868400000** (%%) Set RX2Frequency to 868.4Mhz (according to the result from server)
944 944  
1274 +(% style="background-color:#dcdcdc" %)**AT+RX2DR=5**  (%%) Set RX2DR to match the downlink DR from server. see below
945 945  
946 -More detail AT Command manual can be found at [[AT Command Manual>>path:#AT_COMMAND]]
1276 +(% 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.
947 947  
1278 +(% style="background-color:#dcdcdc" %)**ATZ**       (%%) Reset MCU
948 948  
949 949  
950 -1.
951 -11. Common AT Command Sequence
952 -111. Multi-channel ABP mode (Use with SX1301/LG308)
1281 +(% style="color:red" %)**Note:**
953 953  
954 -If device has not joined network yet:
1283 +(% style="color:red" %)1. Make sure the device is set to ABP mode in the IoT Server.
1284 +2. Make sure the LG01/02 gateway RX frequency is exactly the same as AT+CHS setting.
1285 +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.
1286 +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
955 955  
956 -AT+FDR
1288 +[[image:1654162478620-421.png]]
957 957  
958 -AT+NJM=0
959 959  
960 -ATZ
1291 += 6. FAQ =
961 961  
1293 +== 6.1 How to upgrade the image? ==
962 962  
963 -If device already joined network:
1295 +The RS485-LN LoRaWAN Controller is shipped with a 3.5mm cable, the cable is used to upload image to RS485-LN to:
964 964  
965 -AT+NJM=0
966 -
967 -ATZ
968 -
969 -1.
970 -11.
971 -111. Single-channel ABP mode (Use with LG01/LG02)
972 -
973 -AT+FDR   Reset Parameters to Factory Default, Keys Reserve
974 -
975 -AT+NJM=0 Set to ABP mode
976 -
977 -AT+ADR=0 Set the Adaptive Data Rate Off
978 -
979 -AT+DR=5  Set Data Rate
980 -
981 -AT+TDC=60000  Set transmit interval to 60 seconds
982 -
983 -AT+CHS=868400000 Set transmit frequency to 868.4Mhz
984 -
985 -AT+RX2FQ=868400000 Set RX2Frequency to 868.4Mhz (according to the result from server)
986 -
987 -AT+RX2DR=5  Set RX2DR to match the downlink DR from server. see below
988 -
989 -AT+DADDR=26 01 1A F1 Set Device Address to 26 01 1A F1, this ID can be found in the LoRa Server portal.
990 -
991 -ATZ          Reset MCU
992 -
993 -**Note:**
994 -
995 -1. Make sure the device is set to ABP mode in the IoT Server.
996 -1. Make sure the LG01/02 gateway RX frequency is exactly the same as AT+CHS setting.
997 -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.
998 -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
999 -
1000 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image029.png]]
1001 -
1002 -
1003 -1. FAQ
1004 -11. How to upgrade the image?
1005 -
1006 -The RS485-BL LoRaWAN Controller is shipped with a 3.5mm cable, the cable is used to upload image to RS485-BL to:
1007 -
1008 1008  * Support new features
1009 1009  * For bug fix
1010 1010  * Change LoRaWAN bands.
1011 1011  
1012 -Below shows the hardware connection for how to upload an image to RS485-BL:
1301 +Below shows the hardware connection for how to upload an image to RS485-LN:
1013 1013  
1014 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image030.png]]
1303 +[[image:1654162535040-878.png]]
1015 1015  
1016 1016  **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]].
1017 1017  
... ... @@ -1019,84 +1019,78 @@
1019 1019  
1020 1020  **Step3: **Open flashloader; choose the correct COM port to update.
1021 1021  
1022 -
1023 -|(((
1024 -HOLD PRO then press the RST button, SYS will be ON, then click next
1311 +(((
1312 +(% 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.
1025 1025  )))
1026 1026  
1027 -|(((
1028 -Board detected
1029 -)))
1030 1030  
1031 -|(((
1032 -
1033 -)))
1316 +[[image:image-20220602175818-12.png]]
1034 1034  
1035 -[[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]]
1036 1036  
1319 +[[image:image-20220602175848-13.png]]
1037 1037  
1038 1038  
1039 -[[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]]
1322 +[[image:image-20220602175912-14.png]]
1040 1040  
1041 1041  
1042 -[[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]]
1325 +**Notice**: In case user has lost the program cable. User can hand made one from a 3.5mm cable. The pin mapping is:
1043 1043  
1327 +[[image:image-20220602175638-10.png]]
1044 1044  
1045 -1.
1046 -11. How to change the LoRa Frequency Bands/Region?
1047 1047  
1048 -User can follow the introduction for [[how to upgrade image>>path:#upgrade_image]]. When download the images, choose the required image file for download.
1330 +== 6.2 How to change the LoRa Frequency Bands/Region? ==
1049 1049  
1332 +User can follow the introduction for [[how to upgrade image>>||anchor="H6.1Howtoupgradetheimage3F"]]. When download the images, choose the required image file for download.
1050 1050  
1051 1051  
1052 -1.
1053 -11. How many RS485-Slave can RS485-BL connects?
1335 +== 6.3 How many RS485-Slave can RS485-BL connects? ==
1054 1054  
1055 -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]].
1337 +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"]].
1056 1056  
1057 1057  
1340 +== 6.4 Compatible question to ChirpStack and TTI LoRaWAN server ? ==
1058 1058  
1342 +When user need to use with ChirpStack or TTI. Please set AT+RPL=4.
1059 1059  
1060 -1. Trouble Shooting     
1061 -11. Downlink doesn’t work, how to solve it?
1344 +Detail info check this link: [[Set Packet Receiving Response Level>>doc:Main.End Device AT Commands and Downlink Command.WebHome||anchor="H7.23SetPacketReceivingResponseLevel"]]
1062 1062  
1063 -Please see this link for debug:
1064 1064  
1065 -[[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]] 
1347 += 7. Trouble Shooting =
1066 1066  
1349 +== 7.1 Downlink doesn’t work, how to solve it? ==
1067 1067  
1351 +Please see this link for debug: [[LoRaWAN Communication Debug>>doc:Main.LoRaWAN Communication Debug.WebHome]]
1068 1068  
1069 -1.
1070 -11. Why I can’t join TTN V3 in US915 /AU915 bands?
1071 1071  
1072 -It might about the channels mapping. Please see for detail.
1354 +== 7.2 Why I can’t join TTN V3 in US915 /AU915 bands? ==
1073 1073  
1074 -[[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]]
1356 +It might about the channels mapping. Please see for detail: [[Notice of Frequency band>>doc:Main.LoRaWAN Communication Debug.WebHome||anchor="H2.NoticeofUS9152FCN4702FAU915Frequencyband"]]
1075 1075  
1076 1076  
1359 += 8. Order Info =
1077 1077  
1078 -1. Order Info
1361 +(% style="color:blue" %)**Part Number: RS485-LN-XXX**
1079 1079  
1080 -**Part Number: RS485-BL-XXX**
1363 +(% style="color:blue" %)**XXX:**
1081 1081  
1082 -**XXX:**
1365 +* (% style="color:blue" %)**EU433**(%%): frequency bands EU433
1366 +* (% style="color:blue" %)**EU868**(%%): frequency bands EU868
1367 +* (% style="color:blue" %)**KR920**(%%): frequency bands KR920
1368 +* (% style="color:blue" %)**CN470**(%%): frequency bands CN470
1369 +* (% style="color:blue" %)**AS923**(%%): frequency bands AS923
1370 +* (% style="color:blue" %)**AU915**(%%): frequency bands AU915
1371 +* (% style="color:blue" %)**US915**(%%): frequency bands US915
1372 +* (% style="color:blue" %)**IN865**(%%): frequency bands IN865
1373 +* (% style="color:blue" %)**RU864**(%%): frequency bands RU864
1374 +* (% style="color:blue" %)**KZ865**(%%): frequency bands KZ865
1083 1083  
1084 -* **EU433**: frequency bands EU433
1085 -* **EU868**: frequency bands EU868
1086 -* **KR920**: frequency bands KR920
1087 -* **CN470**: frequency bands CN470
1088 -* **AS923**: frequency bands AS923
1089 -* **AU915**: frequency bands AU915
1090 -* **US915**: frequency bands US915
1091 -* **IN865**: frequency bands IN865
1092 -* **RU864**: frequency bands RU864
1093 -* **KZ865: **frequency bands KZ865
1094 1094  
1095 -1. Packing Info
1377 += 9.Packing Info =
1096 1096  
1379 +
1097 1097  **Package Includes**:
1098 1098  
1099 -* RS485-BL x 1
1382 +* RS485-LN x 1
1100 1100  * Stick Antenna for LoRa RF part x 1
1101 1101  * Program cable x 1
1102 1102  
... ... @@ -1107,9 +1107,63 @@
1107 1107  * Package Size / pcs : 14.5 x 8 x 5 cm
1108 1108  * Weight / pcs : 170g
1109 1109  
1110 -1. Support
1111 1111  
1112 -* 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.
1113 -* 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
1394 += 10. FCC Caution for RS485LN-US915 =
1114 1114  
1115 -[[support@dragino.com>>url:file:///D:/市场资料/说明书/LoRa/LT系列/support@dragino.com]]
1396 +(((
1397 +Any Changes or modifications not expressly approved by the party responsible for compliance could void the user's authority to operate the equipment.
1398 +)))
1399 +
1400 +(((
1401 +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.
1402 +)))
1403 +
1404 +(((
1405 +
1406 +)))
1407 +
1408 +(((
1409 +**IMPORTANT NOTE:**
1410 +)))
1411 +
1412 +(((
1413 +**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:
1414 +)))
1415 +
1416 +(((
1417 +—Reorient or relocate the receiving antenna.
1418 +)))
1419 +
1420 +(((
1421 +—Increase the separation between the equipment and receiver.
1422 +)))
1423 +
1424 +(((
1425 +—Connect the equipment into an outlet on a circuit different from that to which the receiver is connected.
1426 +)))
1427 +
1428 +(((
1429 +—Consult the dealer or an experienced radio/TV technician for help.
1430 +)))
1431 +
1432 +(((
1433 +
1434 +)))
1435 +
1436 +(((
1437 +**FCC Radiation Exposure Statement:**
1438 +)))
1439 +
1440 +(((
1441 +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.
1442 +)))
1443 +
1444 +
1445 += 11. Support =
1446 +
1447 +* (((
1448 +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.
1449 +)))
1450 +* (((
1451 +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]].
1452 +)))
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-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
image-20220606110929-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +13.9 KB
Content