Skip to Content
Last modified by Xiaoling on 2025/04/23 15:56
From version 32.10
edited by Xiaoling
on 2022/06/02 15:26
Change comment: There is no comment for this version
To version 57.9
edited by Xiaoling
on 2022/06/06 08:58
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 ==
... ... @@ -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.
83 +* Packet engine up to 256 bytes with CRC
78 78  
79 79  
80 80  
... ... @@ -132,6 +132,8 @@
132 132  )))
133 133  
134 134  [[image:1653268091319-405.png]]
141 +
142 +
135 135  )))
136 136  
137 137  = 3. Operation Mode =
... ... @@ -140,6 +140,8 @@
140 140  
141 141  (((
142 142  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.
151 +
152 +
143 143  )))
144 144  
145 145  == 3.2 Example to join LoRaWAN network ==
... ... @@ -148,15 +148,20 @@
148 148  
149 149  [[image:1653268155545-638.png||height="334" width="724"]]
150 150  
161 +
151 151  (((
163 +(((
152 152  The RS485-LN in this example connected to two RS485 devices for demonstration, user can connect to other RS485 devices via the same method. The connection is as below:
165 +)))
153 153  
167 +(((
154 154  485A+ and 485B- of the sensor are connected to RS485A and RA485B of RS485-LN respectively.
169 +)))
155 155  
156 156  [[image:1653268227651-549.png||height="592" width="720"]]
157 157  
158 158  (((
159 -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:
174 +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:
160 160  )))
161 161  
162 162  (((
... ... @@ -203,6 +203,7 @@
203 203  
204 204  [[image:1652953568895-172.png||height="232" width="724"]]
205 205  
221 +
206 206  == 3.3 Configure Commands to read data ==
207 207  
208 208  (((
... ... @@ -212,6 +212,8 @@
212 212  
213 213  (((
214 214  (% style="color:red" %)Note: below description and commands are for firmware version >v1.1, if you have firmware version v1.0. Please check the [[user manual v1.0>>url:http://www.dragino.com/downloads/index.php?dir=RS485-LN/&file=RS485-LN_UserManual_v1.0.1.pdf]] or upgrade the firmware to v1.1
231 +
232 +
215 215  )))
216 216  )))
217 217  
... ... @@ -219,19 +219,19 @@
219 219  
220 220  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:
221 221  
222 -(% border="1" style="background-color:#ffffcc; color:green; width:795px" %)
223 -|(((
240 +(% border="1" style="background-color:#ffffcc; color:green; width:782px" %)
241 +|(% style="width:128px" %)(((
224 224  **AT Commands**
225 -)))|(% style="width:285px" %)(((
243 +)))|(% style="width:305px" %)(((
226 226  **Description**
227 -)))|(% style="width:347px" %)(((
245 +)))|(% style="width:346px" %)(((
228 228  **Example**
229 229  )))
230 -|(((
248 +|(% style="width:128px" %)(((
231 231  AT+BAUDR
232 -)))|(% style="width:285px" %)(((
250 +)))|(% style="width:305px" %)(((
233 233  Set the baud rate (for RS485 connection). Default Value is: 9600.
234 -)))|(% style="width:347px" %)(((
252 +)))|(% style="width:346px" %)(((
235 235  (((
236 236  AT+BAUDR=9600
237 237  )))
... ... @@ -240,11 +240,11 @@
240 240  Options: (1200,2400,4800,14400,19200,115200)
241 241  )))
242 242  )))
243 -|(((
261 +|(% style="width:128px" %)(((
244 244  AT+PARITY
245 -)))|(% style="width:285px" %)(((
263 +)))|(% style="width:305px" %)(((
246 246  Set UART parity (for RS485 connection)
247 -)))|(% style="width:347px" %)(((
265 +)))|(% style="width:346px" %)(((
248 248  (((
249 249  AT+PARITY=0
250 250  )))
... ... @@ -253,9 +253,9 @@
253 253  Option: 0: no parity, 1: odd parity, 2: even parity
254 254  )))
255 255  )))
256 -|(((
274 +|(% style="width:128px" %)(((
257 257  AT+STOPBIT
258 -)))|(% style="width:285px" %)(((
276 +)))|(% style="width:305px" %)(((
259 259  (((
260 260  Set serial stopbit (for RS485 connection)
261 261  )))
... ... @@ -263,7 +263,7 @@
263 263  (((
264 264  
265 265  )))
266 -)))|(% style="width:347px" %)(((
284 +)))|(% style="width:346px" %)(((
267 267  (((
268 268  AT+STOPBIT=0 for 1bit
269 269  )))
... ... @@ -298,77 +298,34 @@
298 298  === 3.3.3 Configure read commands for each sampling ===
299 299  
300 300  (((
301 -RS485-BL is a battery powered device; it will sleep most of time. And wake up on each period and read RS485 / TTL sensor data and uplink.
302 -)))
319 +During each sampling, we need confirm what commands we need to send to the RS485 sensors to read data. After the RS485 sensors send back the value, it normally include some bytes and we only need a few from them for a shorten payload.
303 303  
304 -(((
305 -During each sampling, we need to confirm what commands we need to send to the sensors to read data. After the RS485/TTL sensors send back the value, it normally includes some bytes and we only need a few from them for a shorten payload.
306 -)))
307 -
308 -(((
309 309  To save the LoRaWAN network bandwidth, we might need to read data from different sensors and combine their valid value into a short payload.
310 -)))
311 311  
312 -(((
313 313  This section describes how to achieve above goals.
314 -)))
315 315  
316 -(((
317 -During each sampling, the RS485-BL can support 15 commands to read sensors. And combine the return to one or several uplink payloads.
318 -)))
325 +During each sampling, the RS485-LN can support 15 commands to read sensors. And combine the return to one or several uplink payloads.
319 319  
320 -(((
321 -**Command from RS485-BL to Sensor:**
322 -)))
323 323  
324 -(((
325 -RS485-BL can send out pre-set max 15 strings via **AT+COMMAD1**, **ATCOMMAND2**,…, to **AT+COMMANDF** . All commands are of same grammar.
326 -)))
328 +**Each RS485 commands include two parts:**
327 327  
328 -(((
329 -**Handle return from sensors to RS485-BL**:
330 -)))
330 +~1. What commands RS485-LN will send to the RS485 sensors. There are total 15 commands from **AT+COMMAD1**, **ATCOMMAND2**,…, to **AT+COMMANDF**. All commands are of same grammar.
331 331  
332 -(((
333 -After RS485-BL send out a string to sensor, RS485-BL will wait for the return from RS485 or TTL sensor. And user can specify how to handle the return, by **AT+DATACUT or AT+SEARCH commands**
334 -)))
332 +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.
335 335  
336 -* (((
337 -**AT+DATACUT**
338 -)))
334 +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
339 339  
340 -(((
341 -When the return value from sensor have fix length and we know which position the valid value we should get, we can use AT+DATACUT command.
342 -)))
343 343  
344 -* (((
345 -**AT+SEARCH**
346 -)))
347 -
348 -(((
349 -When the return value from sensor is dynamic length and we are not sure which bytes the valid data is, instead, we know what value the valid value following. We can use AT+SEARCH to search the valid value in the return string.
350 -)))
351 -
352 -(((
353 -**Define wait timeout:**
354 -)))
355 -
356 -(((
357 -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
358 -)))
359 -
360 -(((
361 361  After we got the valid value from each RS485 commands, we need to combine them together with the command **AT+DATAUP**.
362 -)))
363 363  
364 -**Examples:**
365 365  
366 366  Below are examples for the how above AT Commands works.
367 367  
368 -**AT+COMMANDx : **This command will be sent to RS485/TTL devices during each sampling, Max command length is 14 bytes. The grammar is:
369 369  
370 -(% border="1" class="table-bordered" %)
371 -|(((
343 +**AT+COMMANDx : **This command will be sent to RS485 devices during each sampling, Max command length is 14 bytes. The grammar is:
344 +
345 +(% border="1" style="background-color:#4bacc6; color:white; width:499px" %)
346 +|(% style="width:496px" %)(((
372 372  **AT+COMMANDx=xx xx xx xx xx xx xx xx xx xx xx xx,m**
373 373  
374 374  **xx xx xx xx xx xx xx xx xx xx xx xx: The RS485 command to be sent**
... ... @@ -376,49 +376,15 @@
376 376  **m: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command**
377 377  )))
378 378  
379 -(((
380 380  For example, if we have a RS485 sensor. The command to get sensor value is: 01 03 0B B8 00 02 46 0A. Where 01 03 0B B8 00 02 is the Modbus command to read the register 0B B8 where stored the sensor value. The 46 0A is the CRC-16/MODBUS which calculate manually.
381 -)))
382 382  
383 -(((
384 -In the RS485-BL, we should use this command AT+COMMAND1=01 03 0B B8 00 02,1 for the same.
385 -)))
356 +In the RS485-LN, we should use this command AT+COMMAND1=01 03 0B B8 00 02,1 for the same.
386 386  
387 -(((
388 -**AT+SEARCHx**: This command defines how to handle the return from AT+COMMANDx.
389 -)))
390 390  
391 -(% border="1" class="table-bordered" %)
392 -|(((
393 -**AT+SEARCHx=aa,xx xx xx xx xx**
394 -
395 -* **aa: 1: prefix match mode; 2: prefix and suffix match mode**
396 -* **xx xx xx xx xx: match string. Max 5 bytes for prefix and 5 bytes for suffix**
397 -
398 -
399 -)))
400 -
401 -**Examples:**
402 -
403 -~1. For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
404 -
405 -If we set AT+SEARCH1=1,1E 56 34.      (max 5 bytes for prefix)
406 -
407 -The valid data will be all bytes after 1E 56 34 , so it is (% style="background-color:yellow" %)** 2e 30 58 5f 36 41 30 31 00 49**
408 -
409 -[[image:1653269403619-508.png]]
410 -
411 -2. For a return string from AT+COMMAND1:  16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
412 -
413 -If we set AT+SEARCH1=2, 1E 56 34+31 00 49
414 -
415 -Device will search the bytes between 1E 56 34 and 31 00 49. So it is (% style="background-color:yellow" %)** 2e 30 58 5f 36 41 30**
416 -
417 -[[image:1653269438444-278.png]]
418 -
419 419  **AT+DATACUTx : **This command defines how to handle the return from AT+COMMANDx, max return length is 45 bytes.
420 420  
421 -|(((
361 +(% border="1" style="background-color:#4bacc6; color:white; width:725px" %)
362 +|(% style="width:722px" %)(((
422 422  **AT+DATACUTx=a,b,c**
423 423  
424 424  * **a: length for the return of AT+COMMAND**
... ... @@ -426,48 +426,37 @@
426 426  * **c: define the position for valid value.  **
427 427  )))
428 428  
429 -Examples:
370 +**Examples:**
430 430  
431 431  * Grab bytes:
432 432  
433 -[[image:1653269551753-223.png||height="311" width="717"]]
374 +[[image:image-20220602153621-1.png]]
434 434  
376 +
435 435  * Grab a section.
436 436  
437 -[[image:1653269568276-930.png||height="325" width="718"]]
379 +[[image:image-20220602153621-2.png]]
438 438  
381 +
439 439  * Grab different sections.
440 440  
441 -[[image:1653269593172-426.png||height="303" width="725"]]
384 +[[image:image-20220602153621-3.png]]
442 442  
443 -(% style="color:red" %)**Note:**
386 +
387 +)))
444 444  
445 -AT+SEARCHx and AT+DATACUTx can be used together, if both commands are set, RS485-BL will first process AT+SEARCHx on the return string and get a temporary string, and then process AT+DATACUTx on this temporary string to get the final payload. In this case, AT+DATACUTx need to set to format AT+DATACUTx=0,xx,xx where the return bytes set to 0.
446 -
447 -Example:
448 -
449 -(% style="color:red" %)AT+COMMAND1=11 01 1E D0,0
450 -
451 -(% style="color:red" %)AT+SEARCH1=1,1E 56 34
452 -
453 -(% style="color:red" %)AT+DATACUT1=0,2,1~~5
454 -
455 -(% style="color:red" %)Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
456 -
457 -(% style="color:red" %)String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49
458 -
459 -(% style="color:red" %)Valid payload after DataCUT command: 2e 30 58 5f 36
460 -
461 -[[image:1653269618463-608.png]]
462 -
463 463  === 3.3.4 Compose the uplink payload ===
464 464  
465 465  (((
466 466  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.**
393 +
394 +
467 467  )))
468 468  
469 469  (((
470 -(% style="color:#4f81bd" %)**Examples: AT+DATAUP=0**
398 +(% style="color:#037691" %)**Examples: AT+DATAUP=0**
399 +
400 +
471 471  )))
472 472  
473 473  (((
... ... @@ -488,8 +488,10 @@
488 488  
489 489  [[image:1653269759169-150.png||height="513" width="716"]]
490 490  
491 -(% style="color:#4f81bd" %)**Examples: AT+DATAUP=1**
492 492  
422 +(% style="color:#037691" %)**Examples: AT+DATAUP=1**
423 +
424 +
493 493  Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**Multiply UPLINKs**.
494 494  
495 495  Final Payload is
... ... @@ -496,169 +496,124 @@
496 496  
497 497  (% style="color:#4f81bd" %)**Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA**
498 498  
499 -1. Battery Info (2 bytes): Battery voltage
500 -1. PAYVER (1 byte): Defined by AT+PAYVER
501 -1. PAYLOAD COUNT (1 byte): Total how many uplinks of this sampling.
502 -1. PAYLOAD# (1 byte): Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT)
503 -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
431 +1. PAYVER: Defined by AT+PAYVER
432 +1. PAYLOAD COUNT: Total how many uplinks of this sampling.
433 +1. PAYLOAD#: Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT)
434 +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
504 504  
505 -[[image:1653269916228-732.png||height="433" width="711"]]
436 +[[image:image-20220602155039-4.png]]
506 506  
507 507  
508 -So totally there will be 3 uplinks for this sampling, each uplink includes 6 bytes DATA
439 +So totally there will be 3 uplinks for this sampling, each uplink include 8 bytes DATA
509 509  
510 -DATA1=RETURN1 Valid Value = (% style="background-color:green; color:white" %)20 20 0a 33 90 41
441 +DATA1=RETURN1 Valid Value + the first two of Valid value of RETURN10= **20 20 0a 33 90 41 02 aa**
511 511  
512 -DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10=(% style="background-color:green; color:white" %) 02 aa 05 81 0a 20
443 +DATA2=3^^rd^^ ~~ 10^^th^^ byte of Valid value of RETURN10= **05 81 0a 20 20 20 20 2d**
513 513  
514 -DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 = (% style="background-color:green; color:white" %)20 20 20 2d 30
445 +DATA3=the rest of Valid value of RETURN10= **30**
515 515  
516 -Below are the uplink payloads:
517 517  
518 -[[image:1653270130359-810.png]]
448 +(% 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:
519 519  
450 + ~* For AU915/AS923 bands, if UplinkDwell time=0, max 51 bytes for each uplink.
520 520  
521 -(% style="color:red" %)**Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:**
452 + * For AU915/AS923 bands, if UplinkDwell time=0, max 11 bytes for each uplink.
522 522  
523 - ~* For AU915/AS923 bands, if UplinkDwell time=0, max 51 bytes for each uplink ( so 51 -5 = 46 max valid date)
454 + * For US915 band, max 11 bytes for each uplink.
524 524  
525 - * For AU915/AS923 bands, if UplinkDwell time=1, max 11 bytes for each uplink ( so 11 -5 = 6 max valid date).
456 + ~* For all other bands: max 51 bytes for each uplink.
526 526  
527 - * For US915 band, max 11 bytes for each uplink ( so 11 -5 = 6 max valid date).
528 528  
529 - ~* For all other bands: max 51 bytes for each uplink  ( so 51 -5 = 46 max valid date).
459 +Below are the uplink payloads:
530 530  
461 +[[image:1654157178836-407.png]]
462 +
463 +
531 531  === 3.3.5 Uplink on demand ===
532 532  
533 -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.
466 +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.
534 534  
535 535  Downlink control command:
536 536  
537 -[[0x08 command>>path:#downlink_08]]: Poll an uplink with current command set in RS485-BL.
470 +**0x08 command**: Poll an uplink with current command set in RS485-LN.
538 538  
539 -[[0xA8 command>>path:#downlink_A8]]: Send a command to RS485-BL and uplink the output from sensors.
472 +**0xA8 command**: Send a command to RS485-LN and uplink the output from sensors.
540 540  
541 541  
542 542  
543 -1.
544 -11.
545 -111. Uplink on Interrupt
476 +=== 3.3.6 Uplink on Interrupt ===
546 546  
547 -Put the interrupt sensor between 3.3v_out and GPIO ext.[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image022.png]]
478 +RS485-LN support external Interrupt uplink since hardware v1.2 release.
548 548  
549 -AT+INTMOD=0  Disable Interrupt
480 +[[image:1654157342174-798.png]]
550 550  
551 -AT+INTMOD=1  Interrupt trigger by rising or falling edge.
482 +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.
552 552  
553 -AT+INTMOD=2  Interrupt trigger by falling edge. ( Default Value)
554 554  
555 -AT+INTMOD=3  Interrupt trigger by rising edge.
485 +== 3.4 Uplink Payload ==
556 556  
557 -
558 -1.
559 -11. Uplink Payload
560 -
561 -|**Size(bytes)**|**2**|**1**|**Length depends on the return from the commands**
562 -|Value|(((
487 +(% border="1" style="background-color:#4bacc6; color:white; width:734px" %)
488 +|**Size(bytes)**|(% style="width:120px" %)**2**|(% style="width:116px" %)**1**|(% style="width:386px" %)**Length depends on the return from the commands**
489 +|Value|(% style="width:120px" %)(((
563 563  Battery(mV)
564 564  
565 565  &
566 566  
567 567  Interrupt _Flag
568 -)))|(((
495 +)))|(% style="width:116px" %)(((
569 569  PAYLOAD_VER
570 570  
571 571  
572 -)))|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.
499 +)))|(% 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.
573 573  
574 574  Below is the decoder for the first 3 bytes. The rest bytes are dynamic depends on different RS485 sensors.
575 575  
576 576  
577 -function Decoder(bytes, port) {
504 +== 3.5 Configure RS485-BL via AT or Downlink ==
578 578  
579 -~/~/Payload Formats of RS485-BL Deceive
506 +User can configure RS485-LN via AT Commands or LoRaWAN Downlink Commands
580 580  
581 -return {
582 -
583 - ~/~/Battery,units:V
584 -
585 - BatV:((bytes[0]<<8 | bytes[1])&0x7fff)/1000,
586 -
587 - ~/~/GPIO_EXTI 
588 -
589 - EXTI_Trigger:(bytes[0] & 0x80)? "TRUE":"FALSE",
590 -
591 - ~/~/payload of version
592 -
593 - Pay_ver:bytes[2],
594 -
595 - };
596 -
597 - }
598 -
599 -
600 -
601 -
602 -
603 -
604 -
605 -TTN V3 uplink screen shot.
606 -
607 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png]]
608 -
609 -1.
610 -11. Configure RS485-BL via AT or Downlink
611 -
612 -User can configure RS485-BL via [[AT Commands >>path:#_​Using_the_AT]]or LoRaWAN Downlink Commands
613 -
614 614  There are two kinds of Commands:
615 615  
616 -* **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
510 +* (% 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]]
617 617  
618 -* **Sensor Related Commands**: These commands are special designed for RS485-BL.  User can see these commands below:
512 +* (% style="color:#4f81bd" %)**Sensor Related Commands**(%%): These commands are special designed for RS485-LN.  User can see these commands below:
619 619  
620 -1.
621 -11.
622 -111. Common Commands:
514 +=== 3.5.1 Common Commands ===
623 623  
624 -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]]
516 +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]]
625 625  
626 626  
627 -1.
628 -11.
629 -111. Sensor related commands:
519 +=== 3.5.2 Sensor related commands ===
630 630  
631 -==== Choose Device Type (RS485 or TTL) ====
521 +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.
632 632  
633 -RS485-BL can connect to either RS485 sensors or TTL sensor. User need to specify what type of sensor need to connect.
523 +[[image:image-20220602163333-5.png||height="263" width="1160"]]
634 634  
635 -* AT Command
525 +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)
636 636  
637 -**AT+MOD=1** ~/~/ Set to support RS485-MODBUS type sensors. User can connect multiply RS485 , Modbus sensors to the A / B pins.
638 638  
639 -**AT+MOD=2** ~/~/ Set to support TTL Level sensors, User can connect one TTL Sensor to the TXD/RXD/GND pins.
528 +=== 3.5.3 Sensor related commands ===
640 640  
530 +(% class="wikigeneratedid" id="H" %)
531 +
641 641  
642 -* Downlink Payload
643 643  
644 -**0A aa**     à same as AT+MOD=aa
534 +==== **RS485 Debug Command** ====
645 645  
536 +This command is used to configure the RS485 devices; they won’t be used during sampling.
646 646  
538 +* **AT Command**
647 647  
648 -==== [[RS485 Debug Command>>path:#downlink_A8]] (AT+CFGDEV) ====
540 +(% class="box infomessage" %)
541 +(((
542 +**AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m**
543 +)))
649 649  
650 -This command is used to configure the RS485 or TTL sensors; they won’t be used during sampling.
545 +m: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
651 651  
652 -* AT Command
547 +* **Downlink Payload**
653 653  
654 -AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
655 -
656 -m: 0: no CRC; 1: add CRC-16/MODBUS in the end of this command.
657 -
658 -
659 -
660 -* Downlink Payload
661 -
662 662  Format: A8 MM NN XX XX XX XX YY
663 663  
664 664  Where:
... ... @@ -666,9 +666,12 @@
666 666  * MM: 1: add CRC-16/MODBUS ; 0: no CRC
667 667  * NN: The length of RS485 command
668 668  * XX XX XX XX: RS485 command total NN bytes
669 -* 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
556 +* YY: How many bytes will be uplink from the return of this RS485 command,
557 +** if YY=0, RS485-LN will execute the downlink command without uplink;
558 +** if YY>0, RS485-LN will uplink total YY bytes from the output of this RS485 command; Fport=200
559 +** if YY=FF, RS485-LN will uplink RS485 output with the downlink command content; Fport=200.
670 670  
671 -**Example 1:**
561 +**Example 1** ~-~-> Configure without ask for uplink (YY=0)
672 672  
673 673  To connect a Modbus Alarm with below commands.
674 674  
... ... @@ -678,184 +678,191 @@
678 678  
679 679  So if user want to use downlink command to control to RS485 Alarm, he can use:
680 680  
681 -**A8 01 06 0A 05 00 04 00 01 00**: to activate the RS485 Alarm
571 +(% style="color:#4f81bd" %)**A8 01 06 0A 05 00 04 00 01 00**(%%): to activate the RS485 Alarm
682 682  
683 -**A8 01 06 0A 05 00 04 00 00 00**: to deactivate the RS485 Alarm
573 +(% style="color:#4f81bd" %)**A8 01 06 0A 05 00 04 00 00 00**(%%): to deactivate the RS485 Alarm
684 684  
685 685  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.
686 686  
687 687  
688 -**Example 2:**
578 +**Example 2** ~-~-> Configure with requesting uplink and original downlink command (**YY=FF**)
689 689  
690 -Check TTL Sensor return:
580 +User in IoT server send a downlink command: (% style="color:#4f81bd" %)**A8 01 06 0A 08 00 04 00 01 YY**
691 691  
692 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image024.png]]
693 693  
583 +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:
694 694  
585 + **A8** (% style="color:#4f81bd" %)**0A 08 00 04 00  **(% style="color:red" %)**01 06** ** **(% style="color:green" %)**0A 08 00 04 00 00**
695 695  
587 + [[image:1654159460680-153.png]]
696 696  
697 -==== Set Payload version ====
698 698  
699 -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.
700 700  
701 -* AT Command:
591 +==== **Set Payload version** ====
702 702  
703 -AT+PAYVER: Set PAYVER field = 1
593 +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.
704 704  
595 +* **AT Command:**
705 705  
706 -* Downlink Payload:
597 +(% class="box infomessage" %)
598 +(((
599 +**AT+PAYVER: Set PAYVER field = 1**
600 +)))
707 707  
708 -0xAE 01   à Set PAYVER field =  0x01
602 +* **Downlink Payload:**
709 709  
710 -0xAE 0F   à Set PAYVER field =  0x0F
604 +**0xAE 01**  ~-~-> Set PAYVER field =  0x01
711 711  
606 +**0xAE 0F**   ~-~-> Set PAYVER field =  0x0F
712 712  
713 -==== Set RS485 Sampling Commands ====
714 714  
715 -AT+COMMANDx, AT+DATACUTx and AT+SEARCHx
716 716  
717 -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]].
610 +==== **Set RS485 Sampling Commands** ====
718 718  
612 +AT+COMMANDx or AT+DATACUTx
719 719  
720 -* AT Command:
614 +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"]].
721 721  
722 -AT+COMMANDx: Configure RS485 read command to sensor.
723 723  
724 -AT+DATACUTx: Configure how to handle return from RS485 devices.
617 +* **AT Command:**
725 725  
726 -AT+SEARCHx: Configure search command
619 +(% class="box infomessage" %)
620 +(((
621 +**AT+COMMANDx: Configure RS485 read command to sensor.**
622 +)))
727 727  
624 +(% class="box infomessage" %)
625 +(((
626 +**AT+DATACUTx: Configure how to handle return from RS485 devices.**
627 +)))
728 728  
729 -* Downlink Payload:
730 730  
731 -0xAF downlink command can be used to set AT+COMMANDx or AT+DATACUTx.
630 +* **Downlink Payload:**
732 732  
733 -Note: if user use AT+COMMANDx to add a new command, he also need to send AT+DATACUTx downlink.
632 +**0xAF** downlink command can be used to set AT+COMMANDx or AT+DATACUTx.
734 734  
634 +(% style="color:red" %)**Note**(%%): if user use AT+COMMANDx to add a new command, he also need to send AT+DATACUTx downlink.
635 +
735 735  Format: AF MM NN LL XX XX XX XX YY
736 736  
737 737  Where:
738 738  
739 739  * MM: the ATCOMMAND or AT+DATACUT to be set. Value from 01 ~~ 0F,
740 -* NN: 0: no CRC; 1: add CRC-16/MODBUS ; 2: set the AT+DATACUT value.
741 -* LL: The length of AT+COMMAND or AT+DATACUT command
641 +* NN:  0: no CRC; 1: add CRC-16/MODBUS ; 2: set the AT+DATACUT value.
642 +* LL:  The length of AT+COMMAND or AT+DATACUT command
742 742  * XX XX XX XX: AT+COMMAND or AT+DATACUT command
743 -* 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.
644 +* 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.
744 744  
745 -Example:
646 +**Example:**
746 746  
747 -**AF 03 01 06 0A 05 00 04 00 01 00**: Same as AT+COMMAND3=0A 05 00 04 00 01,1
648 +(% 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
748 748  
749 -**AF 03 02 06 10 01 05 06 09 0A 00**: Same as AT+DATACUT3=**16**,**1**,**5+6+9+10**
650 +(% 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**
750 750  
751 -**AF 03 02 06 0B 02 05 07 08 0A 00**: Same as AT+DATACUT3=**11**,**2**,**5~~7+8~~10**
652 +(% 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**
752 752  
753 753  
754 -0xAB downlink command can be used for set AT+SEARCHx
755 755  
756 -Example: **AB aa 01 03 xx xx xx** (03 here means there are total 3 bytes after 03) So
656 +==== **Fast command to handle MODBUS device** ====
757 757  
758 -* AB aa 01 03 xx xx xx  same as AT+SEARCHaa=1,xx xx xx
759 -* 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
760 -
761 -**AB aa 02 03 xx xx xx 02 yy yy**  same as **AT+SEARCHaa=2,xx xx xx+yy yy**
762 -
763 -
764 -==== Fast command to handle MODBUS device ====
765 -
766 766  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]].
767 767  
768 768  This command is valid since v1.3 firmware version
769 769  
662 +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.
770 770  
771 -AT+MBFUN has only two value:
772 772  
773 -* AT+MBFUN=1: Enable Modbus reading. And get response base on the MODBUS return
665 +**Example:**
774 774  
775 -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.
776 -
777 -* AT+MBFUN=0: Disable Modbus fast reading.
778 -
779 -Example:
780 -
781 -* AT+MBFUN=1 and AT+DATACUT1/AT+DATACUT2 are not configure (0,0,0).
667 +* AT+MBFUN=1 and AT+DATACUT1/AT+DATACUT2 are not configure (0,0,0). So RS485-LN.
782 782  * 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.
783 783  * 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.
784 784  
785 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image025.png]]
671 +[[image:image-20220602165351-6.png]]
786 786  
673 +[[image:image-20220602165351-7.png]]
787 787  
788 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image026.png]]
789 789  
790 790  
791 -* Downlink Commands:
677 +==== **RS485 command timeout** ====
792 792  
793 -A9 aa -à Same as AT+MBFUN=aa
679 +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.
794 794  
681 +Default value: 0, range:  0 ~~ 65 seconds
795 795  
796 -==== RS485 command timeout ====
683 +* **AT Command:**
797 797  
798 -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.
685 +(% class="box infomessage" %)
686 +(((
687 +**AT+CMDDLaa=hex(bb cc)*1000**
688 +)))
799 799  
800 -Default value: 0, range:  0 ~~ 5 seconds
690 +**Example:**
801 801  
692 +**AT+CMDDL1=1000** to send the open time to 1000ms
802 802  
803 -* AT Command:
804 804  
805 -AT+CMDDLaa=hex(bb cc)
695 +* **Downlink Payload:**
806 806  
807 -Example:
697 +**0x AA aa bb cc**
808 808  
809 -**AT+CMDDL1=1000** to send the open time to 1000ms
699 +Same as: AT+CMDDLaa=hex(bb cc)*1000
810 810  
701 + **Example:**
811 811  
812 -* Downlink Payload:
703 + 0xAA 01 00 01  ~-~-> Same as **AT+CMDDL1=1000 ms**
813 813  
814 -0x AA aa bb cc
815 815  
816 -Same as: AT+CMDDLaa=hex(bb cc)
817 817  
818 - Example:
707 +==== **Uplink payload mode** ====
819 819  
820 - 0xAA 01 03 E8  à Same as **AT+CMDDL1=1000 ms**
709 +Define to use one uplink or multiple uplinks for the sampling.
821 821  
711 +The use of this command please see: [[Compose Uplink payload>>||anchor="H3.3.4Composetheuplinkpayload"]]
822 822  
823 -==== [[Uplink>>path:#downlink_A8]] payload mode ====
713 +* **AT Command:**
824 824  
825 -Define to use one uplink or multiple uplinks for the sampling.
715 +(% class="box infomessage" %)
716 +(((
717 +**AT+DATAUP=0**
718 +)))
826 826  
827 -The use of this command please see: [[Compose Uplink payload>>path:#DataUP]]
720 +(% class="box infomessage" %)
721 +(((
722 +**AT+DATAUP=1**
723 +)))
828 828  
829 -* AT Command:
830 830  
831 -AT+DATAUP=0
726 +* **Downlink Payload:**
832 832  
833 -AT+DATAUP=1
728 +**0xAD 00**  **~-~->** Same as AT+DATAUP=0
834 834  
730 +**0xAD 01**  **~-~->** Same as AT+DATAUP=1
835 835  
836 -* Downlink Payload:
837 837  
838 -0xAD 00   à Same as AT+DATAUP=0
839 839  
840 -0xAD 01   à Same as AT+DATAUP=1
734 +==== **Manually trigger an Uplink** ====
841 841  
736 +Ask device to send an uplink immediately.
842 842  
843 -==== Manually trigger an Uplink ====
738 +* **AT Command:**
844 844  
845 -Ask device to send an uplink immediately.
740 +No AT Command for this, user can press the [[ACT button>>path:#Button]] for 1 second for the same.
846 846  
847 -* Downlink Payload:
848 848  
849 -0x08 FF, RS485-BL will immediately send an uplink.
743 +* **Downlink Payload:**
850 850  
745 +**0x08 FF**, RS485-LN will immediately send an uplink.
851 851  
852 -==== Clear RS485 Command ====
853 853  
854 -The AT+COMMANDx and AT+DATACUTx settings are stored in special location, user can use below command to clear them.
748 +==== ====
855 855  
750 +==== **Clear RS485 Command** ====
856 856  
857 -* AT Command:
752 +The AT+COMMANDx and AT+DATACUTx settings are stored in special location, user can use below command to clear them.
858 858  
754 +* **AT Command:**
755 +
859 859  **AT+CMDEAR=mm,nn**   mm: start position of erase ,nn: stop position of erase
860 860  
861 861  Etc. AT+CMDEAR=1,10 means erase AT+COMMAND1/AT+DATACUT1 to AT+COMMAND10/AT+DATACUT10
... ... @@ -863,43 +863,50 @@
863 863  Example screen shot after clear all RS485 commands. 
864 864  
865 865  
866 -
867 867  The uplink screen shot is:
868 868  
869 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png]]
765 +[[image:1654160691922-496.png]][[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image001.png]]
870 870  
871 871  
872 -* Downlink Payload:
768 +* **Downlink Payload:**
873 873  
874 -0x09 aa bb same as AT+CMDEAR=aa,bb
770 +**0x09 aa bb** same as AT+CMDEAR=aa,bb
875 875  
876 876  
877 -==== Set Serial Communication Parameters ====
878 878  
774 +==== **Set Serial Communication Parameters** ====
775 +
879 879  Set the Rs485 serial communication parameters:
880 880  
881 -* AT Command:
778 +* **AT Command:**
882 882  
883 883  Set Baud Rate:
884 884  
885 -AT+BAUDR=9600    ~/~/ Options: (1200,2400,4800,14400,19200,115200)
782 +(% class="box infomessage" %)
783 +(((
784 +**AT+BAUDR=9600**    ~/~/ Options: (1200,2400,4800,14400,19200,115200)
785 +)))
886 886  
787 +Set UART Parity
887 887  
888 -Set UART parity
789 +(% class="box infomessage" %)
790 +(((
791 +**AT+PARITY=0**    ~/~/ Option: 0: no parity, 1: odd parity, 2: even parity
792 +)))
889 889  
890 -AT+PARITY=0    ~/~/ Option: 0: no parity, 1: odd parity, 2: even parity
891 -
892 -
893 893  Set STOPBIT
894 894  
895 -AT+STOPBIT=0    ~/~/ Option: 0 for 1bit; 1 for 1.5 bit ; 2 for 2 bits
796 +(% class="box infomessage" %)
797 +(((
798 +**AT+STOPBIT=0**    ~/~/ Option: 0 for 1bit; 1 for 1.5 bit ; 2 for 2 bits
799 +)))
896 896  
897 897  
898 -* Downlink Payload:
802 +* **Downlink Payload:**
899 899  
900 -A7 01 aa bb: Same  AT+BAUDR=hex(aa bb)*100
804 +**A7 01 aa bb**: Same  AT+BAUDR=hex(aa bb)*100
901 901  
902 -Example:
806 +**Example:**
903 903  
904 904  * A7 01 00 60   same as AT+BAUDR=9600
905 905  * A7 01 04 80  same as AT+BAUDR=115200
... ... @@ -909,287 +909,285 @@
909 909  A7 03 aa: Same as  AT+STOPBIT=aa  (aa value: 00 , 01 or 02)
910 910  
911 911  
912 -==== Control output power duration ====
816 +== 3.6 Listening mode for RS485 network ==
913 913  
914 -User can set the output power duration before each sampling.
818 +This feature support since firmware v1.4
915 915  
916 -* AT Command:
820 +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.
917 917  
918 -Example:
822 +[[image:image-20220602171200-8.png||height="567" width="1007"]]
919 919  
920 -AT+3V3T=1000 ~/~/ 3V3 output power will open 1s before each sampling.
824 +To enable the listening mode, use can run the command AT+RXMODE.
921 921  
922 -AT+5VT=1000 ~/~/ +5V output power will open 1s before each sampling.
923 923  
827 +(% border="1" style="background-color:#ffffcc; width:500px" %)
828 +|=(% style="width: 161px;" %)**Command example:**|=(% style="width: 337px;" %)**Function**
829 +|(% 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.
830 +|(% 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
831 +|(% style="width:161px" %)AT+RXMODE=0,0|(% style="width:337px" %)Disable listening mode. This is the default settings.
832 +|(% style="width:161px" %) |(% style="width:337px" %)A6 aa bb cc  same as AT+RXMODE=aa,(bb<<8 ~| cc)
924 924  
925 -* LoRaWAN Downlink Command:
834 +**Downlink Command:**
926 926  
927 -07 01 aa bb  Same as AT+5VT=(aa bb)
836 +**0xA6 aa bb cc ** same as AT+RXMODE=aa,(bb<<8 | cc)
928 928  
929 -07 02 aa bb  Same as AT+3V3T=(aa bb)
930 930  
839 +**Example**:
931 931  
841 +The RS485-LN is set to AT+RXMODE=2,1000
932 932  
843 +There is a two Modbus commands in the RS485 network as below:
933 933  
934 -1.
935 -11. Buttons
845 +The Modbus master send a command: (% style="background-color:#ffc000" %)01 03 00 00 00 02 c4 0b
936 936  
937 -|**Button**|**Feature**
938 -|**RST**|Reboot RS485-BL
847 +And Modbus slave reply with: (% style="background-color:green" %)01 03 04 00 00 00 00 fa 33
939 939  
940 -1.
941 -11. +3V3 Output
849 +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
942 942  
943 -RS485-BL has a Controllable +3V3 output, user can use this output to power external sensor.
851 +[[image:image-20220602171200-9.png]]
944 944  
945 -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. 
946 946  
854 +(% 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.
947 947  
948 -The +3V3 output time can be controlled by AT Command.
949 949  
950 -**AT+3V3T=1000**
857 +== 3.7 Buttons ==
951 951  
952 -Means set +3v3 valid time to have 1000ms. So, the real +3v3 output will actually have 1000ms + sampling time for other sensors.
953 953  
860 +(% border="1" style="background-color:#f7faff; width:500px" %)
861 +|=**Button**|=(% style="width: 1420px;" %)**Feature**
862 +|**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**
863 +|**RST**|(% style="width:1420px" %)Reboot RS485
864 +|**PRO**|(% style="width:1420px" %)Use for upload image, see [[How to Update Image>>path:#upgrade_image]]
954 954  
955 -By default, the AT+3V3T=0. This is a special case, means the +3V3 output is always on at any time
956 956  
957 957  
958 -1.
959 -11. +5V Output
868 +== 3.8 LEDs ==
960 960  
961 -RS485-BL has a Controllable +5V output, user can use this output to power external sensor.
870 +(% border="1" style="background-color:#f7faff; width:500px" %)
871 +|=**LEDs**|=**Feature**
872 +|**PWR**|Always on if there is power
873 +|**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.
962 962  
963 -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. 
964 964  
965 965  
966 -The 5V output time can be controlled by AT Command.
877 += 4. Case Study =
967 967  
968 -**AT+5VT=1000**
879 +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]]
969 969  
970 -Means set 5V valid time to have 1000ms. So, the real 5V output will actually have 1000ms + sampling time for other sensors.
971 971  
882 += 5. Use AT Command =
972 972  
973 -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.
884 +== 5.1 Access AT Command ==
974 974  
886 +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.
975 975  
888 +[[image:1654162355560-817.png]]
976 976  
977 977  
978 -1.
979 -11. LEDs
891 +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:
980 980  
981 -|**LEDs**|**Feature**
982 -|**LED1**|Blink when device transmit a packet.
893 +[[image:1654162368066-342.png]]
983 983  
984 -1.
985 -11. Switch Jumper
986 986  
987 -|**Switch Jumper**|**Feature**
988 -|**SW1**|(((
989 -ISP position: Upgrade firmware via UART
896 +More detail AT Command manual can be found at [[AT Command Manual>>||anchor="3.5ConfigureRS485-BLviaATorDownlink"]]
990 990  
991 -Flash position: Configure device, check running status.
992 -)))
993 -|**SW2**|(((
994 -5V position: set to compatible with 5v I/O.
995 995  
996 -3.3v position: set to compatible with 3.3v I/O.,
997 -)))
899 +== 5.2 Common AT Command Sequence ==
998 998  
999 -+3.3V: is always ON
901 +=== 5.2.1 Multi-channel ABP mode (Use with SX1301/LG308) ===
1000 1000  
1001 -+5V: Only open before every sampling. The time is by default, it is AT+5VT=0.  Max open time. 5000 ms.
903 +If device has not joined network yet:
1002 1002  
1003 -1. Case Study
905 +(% class="box infomessage" %)
906 +(((
907 +**AT+FDR**
908 +)))
1004 1004  
1005 -User can check this URL for some case studies.
910 +(% class="box infomessage" %)
911 +(((
912 +**AT+NJM=0**
913 +)))
1006 1006  
1007 -[[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]]
915 +(% class="box infomessage" %)
916 +(((
917 +**ATZ**
918 +)))
1008 1008  
1009 1009  
921 +If device already joined network:
1010 1010  
923 +(% class="box infomessage" %)
924 +(((
925 +**AT+NJM=0**
926 +)))
1011 1011  
1012 -1. Use AT Command
1013 -11. Access AT Command
928 +(% class="box infomessage" %)
929 +(((
930 +**ATZ**
931 +)))
1014 1014  
1015 -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.
1016 1016  
1017 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image027.png]]
934 +=== 5.5.2 Single-channel ABP mode (Use with LG01/LG02) ===
1018 1018  
1019 1019  
1020 -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:
937 +(% style="background-color:#dcdcdc" %)**AT+FDR** (%%) Reset Parameters to Factory Default, Keys Reserve
1021 1021  
1022 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image028.png]]
939 +(% style="background-color:#dcdcdc" %)**AT+NJM=0 **(%%)Set to ABP mode
1023 1023  
941 +(% style="background-color:#dcdcdc" %)**AT+ADR=0** (%%)Set the Adaptive Data Rate Off
1024 1024  
943 +(% style="background-color:#dcdcdc" %)**AT+DR=5**   (%%)Set Data Rate
1025 1025  
1026 -More detail AT Command manual can be found at [[AT Command Manual>>path:#AT_COMMAND]]
945 +(% style="background-color:#dcdcdc" %)**AT+TDC=60000** (%%) Set transmit interval to 60 seconds
1027 1027  
947 +(% style="background-color:#dcdcdc" %)**AT+CHS=868400000**(%%) Set transmit frequency to 868.4Mhz
1028 1028  
949 +(% style="background-color:#dcdcdc" %)**AT+RX2FQ=868400000** (%%) Set RX2Frequency to 868.4Mhz (according to the result from server)
1029 1029  
1030 -1.
1031 -11. Common AT Command Sequence
1032 -111. Multi-channel ABP mode (Use with SX1301/LG308)
951 +(% style="background-color:#dcdcdc" %)**AT+RX2DR=5**  (%%) Set RX2DR to match the downlink DR from server. see below
1033 1033  
1034 -If device has not joined network yet:
953 +(% 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.
1035 1035  
1036 -AT+FDR
955 +(% style="background-color:#dcdcdc" %)**ATZ**       (%%) Reset MCU
1037 1037  
1038 -AT+NJM=0
1039 1039  
1040 -ATZ
958 +(% style="color:red" %)**Note:**
1041 1041  
960 +(% style="color:red" %)1. Make sure the device is set to ABP mode in the IoT Server.
961 +2. Make sure the LG01/02 gateway RX frequency is exactly the same as AT+CHS setting.
962 +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.
963 +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
1042 1042  
1043 -If device already joined network:
965 +[[image:1654162478620-421.png]]
1044 1044  
1045 -AT+NJM=0
1046 1046  
1047 -ATZ
968 += 6. FAQ =
1048 1048  
1049 -1.
1050 -11.
1051 -111. Single-channel ABP mode (Use with LG01/LG02)
970 +== 6.1 How to upgrade the image? ==
1052 1052  
1053 -AT+FDR   Reset Parameters to Factory Default, Keys Reserve
972 +The RS485-LN LoRaWAN Controller is shipped with a 3.5mm cable, the cable is used to upload image to RS485-LN to:
1054 1054  
1055 -AT+NJM=0 Set to ABP mode
974 +* Support new features
975 +* For bug fix
976 +* Change LoRaWAN bands.
1056 1056  
1057 -AT+ADR=0 Set the Adaptive Data Rate Off
978 +Below shows the hardware connection for how to upload an image to RS485-LN:
1058 1058  
1059 -AT+DR=5  Set Data Rate
980 +[[image:1654162535040-878.png]]
1060 1060  
1061 -AT+TDC=60000  Set transmit interval to 60 seconds
982 +**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]].
1062 1062  
1063 -AT+CHS=868400000 Set transmit frequency to 868.4Mhz
984 +**Step2**: Download the [[LT Image files>>url:http://www.dragino.com/downloads/index.php?dir=LT_LoRa_IO_Controller/LT33222-L/image/]].
1064 1064  
1065 -AT+RX2FQ=868400000 Set RX2Frequency to 868.4Mhz (according to the result from server)
986 +**Step3: **Open flashloader; choose the correct COM port to update.
1066 1066  
1067 -AT+RX2DR=5  Set RX2DR to match the downlink DR from server. see below
988 +(% 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.
1068 1068  
1069 -AT+DADDR=26 01 1A F1 Set Device Address to 26 01 1A F1, this ID can be found in the LoRa Server portal.
1070 1070  
1071 -ATZ          Reset MCU
991 +[[image:image-20220602175818-12.png]]
1072 1072  
1073 -**Note:**
1074 1074  
1075 -1. Make sure the device is set to ABP mode in the IoT Server.
1076 -1. Make sure the LG01/02 gateway RX frequency is exactly the same as AT+CHS setting.
1077 -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.
1078 -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
994 +[[image:image-20220602175848-13.png]]
1079 1079  
1080 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image029.png]]
1081 1081  
997 +[[image:image-20220602175912-14.png]]
1082 1082  
1083 -1. FAQ
1084 -11. How to upgrade the image?
1085 1085  
1086 -The RS485-BL LoRaWAN Controller is shipped with a 3.5mm cable, the cable is used to upload image to RS485-BL to:
1000 +**Notice**: In case user has lost the program cable. User can hand made one from a 3.5mm cable. The pin mapping is:
1087 1087  
1088 -* Support new features
1089 -* For bug fix
1090 -* Change LoRaWAN bands.
1002 +[[image:image-20220602175638-10.png]]
1091 1091  
1092 -Below shows the hardware connection for how to upload an image to RS485-BL:
1093 1093  
1094 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image030.png]]
1005 +== 6.2 How to change the LoRa Frequency Bands/Region? ==
1095 1095  
1096 -**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]].
1007 +User can follow the introduction for [[how to upgrade image>>||anchor="H6.1Howtoupgradetheimage3F"]]. When download the images, choose the required image file for download.
1097 1097  
1098 -**Step2**: Download the [[LT Image files>>url:http://www.dragino.com/downloads/index.php?dir=LT_LoRa_IO_Controller/LT33222-L/image/]].
1099 1099  
1100 -**Step3: **Open flashloader; choose the correct COM port to update.
1010 +== 6.3 How many RS485-Slave can RS485-BL connects? ==
1101 1101  
1012 +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"]].
1102 1102  
1103 -|(((
1104 -HOLD PRO then press the RST button, SYS will be ON, then click next
1105 -)))
1106 1106  
1107 -|(((
1108 -Board detected
1109 -)))
1015 +== 6.4 Compatible question to ChirpStack and TTI LoRaWAN server ? ==
1110 1110  
1111 -|(((
1112 -
1113 -)))
1017 +When user need to use with ChirpStack or TTI. Please set AT+RPL=4.
1114 1114  
1115 -[[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]]
1019 +Detail info check this link: [[Set Packet Receiving Response Level>>doc:Main.End Device AT Commands and Downlink Command.WebHome||anchor="H7.23SetPacketReceivingResponseLevel"]]
1116 1116  
1117 1117  
1022 += 7. Trouble Shooting =
1118 1118  
1119 -[[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]]
1024 +== 7.1 Downlink doesn’t work, how to solve it? ==
1120 1120  
1026 +Please see this link for debug: [[LoRaWAN Communication Debug>>doc:Main.LoRaWAN Communication Debug.WebHome]]
1121 1121  
1122 -[[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]]
1123 1123  
1029 +== 7.2 Why I can’t join TTN V3 in US915 /AU915 bands? ==
1124 1124  
1125 -1.
1126 -11. How to change the LoRa Frequency Bands/Region?
1031 +It might about the channels mapping. Please see for detail: [[Notice of Frequency band>>doc:Main.LoRaWAN Communication Debug.WebHome||anchor="H2.NoticeofUS9152FCN4702FAU915Frequencyband"]]
1127 1127  
1128 -User can follow the introduction for [[how to upgrade image>>path:#upgrade_image]]. When download the images, choose the required image file for download.
1129 1129  
1034 += 8. Order Info =
1130 1130  
1036 +(% style="color:blue" %)**Part Number: RS485-LN-XXX**
1131 1131  
1132 -1.
1133 -11. How many RS485-Slave can RS485-BL connects?
1038 +(% style="color:blue" %)**XXX:**
1134 1134  
1135 -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]].
1040 +* (% style="color:blue" %)**EU433**(%%): frequency bands EU433
1041 +* (% style="color:blue" %)**EU868**(%%): frequency bands EU868
1042 +* (% style="color:blue" %)**KR920**(%%): frequency bands KR920
1043 +* (% style="color:blue" %)**CN470**(%%): frequency bands CN470
1044 +* (% style="color:blue" %)**AS923**(%%): frequency bands AS923
1045 +* (% style="color:blue" %)**AU915**(%%): frequency bands AU915
1046 +* (% style="color:blue" %)**US915**(%%): frequency bands US915
1047 +* (% style="color:blue" %)**IN865**(%%): frequency bands IN865
1048 +* (% style="color:blue" %)**RU864**(%%): frequency bands RU864
1049 +* (% style="color:blue" %)**KZ865**(%%): frequency bands KZ865
1136 1136  
1137 1137  
1138 1138  
1053 += 9.Packing Info =
1139 1139  
1140 -1. Trouble Shooting     
1141 -11. Downlink doesn’t work, how to solve it?
1142 1142  
1143 -Please see this link for debug:
1056 +**Package Includes**:
1144 1144  
1145 -[[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]] 
1058 +* RS485-LN x 1
1059 +* Stick Antenna for LoRa RF part x 1
1060 +* Program cable x 1
1146 1146  
1062 +**Dimension and weight**:
1147 1147  
1064 +* Device Size: 13.5 x 7 x 3 cm
1065 +* Device Weight: 105g
1066 +* Package Size / pcs : 14.5 x 8 x 5 cm
1067 +* Weight / pcs : 170g
1148 1148  
1149 -1.
1150 -11. Why I can’t join TTN V3 in US915 /AU915 bands?
1069 += 10. FCC Caution for RS485LN-US915 =
1151 1151  
1152 -It might about the channels mapping. Please see for detail.
1071 +Any Changes or modifications not expressly approved by the party responsible for compliance could void the user's authority to operate the equipment.
1153 1153  
1154 -[[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]]
1073 +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.
1155 1155  
1156 1156  
1076 +**IMPORTANT NOTE:**
1157 1157  
1158 -1. Order Info
1078 +**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:
1159 1159  
1160 -**Part Number: RS485-BL-XXX**
1080 +—Reorient or relocate the receiving antenna.
1161 1161  
1162 -**XXX:**
1082 +—Increase the separation between the equipment and receiver.
1163 1163  
1164 -* **EU433**: frequency bands EU433
1165 -* **EU868**: frequency bands EU868
1166 -* **KR920**: frequency bands KR920
1167 -* **CN470**: frequency bands CN470
1168 -* **AS923**: frequency bands AS923
1169 -* **AU915**: frequency bands AU915
1170 -* **US915**: frequency bands US915
1171 -* **IN865**: frequency bands IN865
1172 -* **RU864**: frequency bands RU864
1173 -* **KZ865: **frequency bands KZ865
1084 +—Connect the equipment into an outlet on a circuit different from that to which the receiver is connected.
1174 1174  
1175 -1. Packing Info
1086 +—Consult the dealer or an experienced radio/TV technician for help.
1176 1176  
1177 -**Package Includes**:
1178 1178  
1179 -* RS485-BL x 1
1180 -* Stick Antenna for LoRa RF part x 1
1181 -* Program cable x 1
1089 +**FCC Radiation Exposure Statement:**
1182 1182  
1183 -**Dimension and weight**:
1091 +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.
1184 1184  
1185 -* Device Size: 13.5 x 7 x 3 cm
1186 -* Device Weight: 105g
1187 -* Package Size / pcs : 14.5 x 8 x 5 cm
1188 -* Weight / pcs : 170g
1189 1189  
1190 -1. Support
1094 += 11. Support =
1191 1191  
1192 1192  * 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.
1193 -* 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
1194 -
1195 -[[support@dragino.com>>url:file:///D:/市场资料/说明书/LoRa/LT系列/support@dragino.com]]
1097 +* Provide as much information as possible regarding your enquiry (product models, accurately describe your problem and steps to replicate it etc) and send a mail to [[support@dragino.com>>url:file:///D:/市场资料/说明书/LoRa/LT系列/support@dragino.com]].
1654157178836-407.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +179.9 KB
Content
1654157342174-798.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +31.9 KB
Content
1654158783574-851.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +40.6 KB
Content
1654159460680-153.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +24.9 KB
Content
1654160691922-496.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +109.3 KB
Content
1654162355560-817.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +670.0 KB
Content
1654162368066-342.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +192.9 KB
Content
1654162478620-421.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +158.9 KB
Content
1654162535040-878.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +670.0 KB
Content
image-20220602153621-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +23.4 KB
Content
image-20220602153621-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +22.2 KB
Content
image-20220602153621-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +22.3 KB
Content
image-20220602155039-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +24.6 KB
Content
image-20220602163333-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +48.2 KB
Content
image-20220602165351-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +10.6 KB
Content
image-20220602165351-7.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +19.3 KB
Content
image-20220602171200-8.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +276.1 KB
Content
image-20220602171200-9.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +10.0 KB
Content
image-20220602175638-10.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +85.5 KB
Content
image-20220602175743-11.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +85.5 KB
Content
image-20220602175818-12.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +102.5 KB
Content
image-20220602175848-13.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +250.9 KB
Content
image-20220602175912-14.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +176.1 KB
Content