Changes for page RS485-LN – RS485 to LoRaWAN Converter User Manual
Last modified by Xiaoling on 2025/04/23 15:56
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 21 removed)
- 1654157178836-407.png
- 1654157342174-798.png
- 1654158783574-851.png
- 1654159460680-153.png
- 1654160691922-496.png
- 1654162355560-817.png
- 1654162368066-342.png
- 1654162478620-421.png
- 1654162535040-878.png
- image-20220602155039-4.png
- image-20220602163333-5.png
- image-20220602165351-6.png
- image-20220602165351-7.png
- image-20220602171200-8.png
- image-20220602171200-9.png
- image-20220602175638-10.png
- image-20220602175743-11.png
- image-20220602175818-12.png
- image-20220602175848-13.png
- image-20220602175912-14.png
- image-20220606110929-1.png
Details
- Page properties
-
- Content
-
... ... @@ -6,18 +6,12 @@ 6 6 **RS485-LN – RS485 to LoRaWAN Converter User Manual** 7 7 8 8 9 - 10 - 11 11 **Table of Contents:** 12 12 13 -{{toc/}} 14 14 15 15 16 16 17 17 18 - 19 - 20 - 21 21 = 1.Introduction = 22 22 23 23 == 1.1 What is RS485-LN RS485 to LoRaWAN Converter == ... ... @@ -24,33 +24,23 @@ 24 24 25 25 ((( 26 26 ((( 27 -((( 28 28 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. 29 29 ))) 30 -))) 31 31 32 32 ((( 33 -((( 34 34 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. 35 35 ))) 36 -))) 37 37 38 38 ((( 39 -((( 40 40 (% 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. 41 41 ))) 42 -))) 43 43 44 44 ((( 45 -((( 46 46 (% 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 -))) 48 48 49 -((( 50 50 (% 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]] 51 51 ))) 52 52 ))) 53 -))) 54 54 55 55 [[image:1653267211009-519.png||height="419" width="724"]] 56 56 ... ... @@ -90,7 +90,7 @@ 90 90 * Preamble detection. 91 91 * 127 dB Dynamic Range RSSI. 92 92 * Automatic RF Sense and CAD with ultra-fast AFC. 93 -* Packet engine up to 256 bytes with CRC 77 +* Packet engine up to 256 bytes with CRC. 94 94 95 95 == 1.3 Features == 96 96 ... ... @@ -121,13 +121,9 @@ 121 121 122 122 ((( 123 123 ((( 124 -((( 125 125 v1.2: Add External Interrupt Pin. 126 -))) 127 127 128 -((( 129 129 v1.0: Release 130 -))) 131 131 132 132 133 133 ))) ... ... @@ -155,9 +155,7 @@ 155 155 == 3.1 How it works? == 156 156 157 157 ((( 158 -((( 159 159 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. 160 -))) 161 161 162 162 163 163 ))) ... ... @@ -181,7 +181,7 @@ 181 181 [[image:1653268227651-549.png||height="592" width="720"]] 182 182 183 183 ((( 184 -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: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: 185 185 ))) 186 186 187 187 ((( ... ... @@ -233,15 +233,11 @@ 233 233 234 234 ((( 235 235 ((( 236 -((( 237 -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. 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 238 ))) 239 -))) 240 240 241 241 ((( 242 -((( 243 243 (% 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 244 -))) 245 245 246 246 247 247 ))) ... ... @@ -251,19 +251,19 @@ 251 251 252 252 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: 253 253 254 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)255 -| =(% style="width:10px;" %)(((228 +(% border="1" style="background-color:#ffffcc; color:green; width:782px" %) 229 +|(% style="width:128px" %)((( 256 256 **AT Commands** 257 -)))| =(% style="width:190px;" %)(((231 +)))|(% style="width:305px" %)((( 258 258 **Description** 259 -)))| =(% style="width:190px;" %)(((233 +)))|(% style="width:346px" %)((( 260 260 **Example** 261 261 ))) 262 -|(% style="width:1 10px" %)(((236 +|(% style="width:128px" %)((( 263 263 AT+BAUDR 264 -)))|(% style="width: 190px" %)(((238 +)))|(% style="width:305px" %)((( 265 265 Set the baud rate (for RS485 connection). Default Value is: 9600. 266 -)))|(% style="width: 190px" %)(((240 +)))|(% style="width:346px" %)((( 267 267 ((( 268 268 AT+BAUDR=9600 269 269 ))) ... ... @@ -272,11 +272,11 @@ 272 272 Options: (1200,2400,4800,14400,19200,115200) 273 273 ))) 274 274 ))) 275 -|(% style="width:1 10px" %)(((249 +|(% style="width:128px" %)((( 276 276 AT+PARITY 277 -)))|(% style="width: 190px" %)(((251 +)))|(% style="width:305px" %)((( 278 278 Set UART parity (for RS485 connection) 279 -)))|(% style="width: 190px" %)(((253 +)))|(% style="width:346px" %)((( 280 280 ((( 281 281 AT+PARITY=0 282 282 ))) ... ... @@ -285,9 +285,9 @@ 285 285 Option: 0: no parity, 1: odd parity, 2: even parity 286 286 ))) 287 287 ))) 288 -|(% style="width:1 10px" %)(((262 +|(% style="width:128px" %)((( 289 289 AT+STOPBIT 290 -)))|(% style="width: 190px" %)(((264 +)))|(% style="width:305px" %)((( 291 291 ((( 292 292 Set serial stopbit (for RS485 connection) 293 293 ))) ... ... @@ -295,7 +295,7 @@ 295 295 ((( 296 296 297 297 ))) 298 -)))|(% style="width: 190px" %)(((272 +)))|(% style="width:346px" %)((( 299 299 ((( 300 300 AT+STOPBIT=0 for 1bit 301 301 ))) ... ... @@ -317,15 +317,15 @@ 317 317 ))) 318 318 ))) 319 319 320 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)321 -| =(% style="width: 110px;" %)**AT Commands**|=(% style="width:90px;" %)**Description**|=(% style="width:190px;" %)**Example**322 -|AT+CFGDEV|(% style="width:1 10px" %)(((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" %)((( 323 323 This command is used to configure the RS485/TTL devices; they won’t be used during sampling. 324 324 325 325 AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx, 326 326 327 327 mm: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command 328 -)))|(% style="width: 190px" %)AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m302 +)))|(% style="width:256px" %)AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m 329 329 330 330 === 3.3.3 Configure read commands for each sampling === 331 331 ... ... @@ -372,8 +372,8 @@ 372 372 373 373 **AT+DATACUTx : **This command defines how to handle the return from AT+COMMANDx, max return length is 45 bytes. 374 374 375 -(% border="1" style="background-color:#4bacc6; color:white; width:5 10px" %)376 -|(% style="width: 510px" %)(((349 +(% border="1" style="background-color:#4bacc6; color:white; width:725px" %) 350 +|(% style="width:722px" %)((( 377 377 **AT+DATACUTx=a,b,c** 378 378 379 379 * **a: length for the return of AT+COMMAND** ... ... @@ -442,1028 +442,700 @@ 442 442 443 443 (% style="color:#4f81bd" %)**Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA** 444 444 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 445 445 446 -1. PAYVER: Defined by AT+PAYVER 447 -1. PAYLOAD COUNT: Total how many uplinks of this sampling. 448 -1. PAYLOAD#: Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT) 449 -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 425 +[[image:1653269916228-732.png||height="433" width="711"]] 450 450 451 -[[image:image-20220602155039-4.png]] 452 452 428 +So totally there will be 3 uplinks for this sampling, each uplink includes 6 bytes DATA 453 453 454 - Sototally there willbe3uplinksfor thissampling,eachuplinkinclude8bytesDATA430 +DATA1=RETURN1 Valid Value = (% style="background-color:green; color:white" %)20 20 0a 33 90 41 455 455 456 -DATA 1=RETURN1ValidValue +thefirsttwoof Valid value of RETURN10=**20200a33 9041 02aa**432 +DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10=(% style="background-color:green; color:white" %) 02 aa 05 81 0a 20 457 457 458 -DATA 2=3^^rd^^ ~~ 10^^th^^ byte of Valid value of RETURN10=**05 81 0a2020 20 20 2d**434 +DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 = (% style="background-color:green; color:white" %)20 20 20 2d 30 459 459 460 - DATA3=the restof Validvalueof RETURN10= **30**436 +Below are the uplink payloads: 461 461 438 +[[image:1653270130359-810.png]] 462 462 463 -(% 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: 464 464 465 - ~*ForAU915/AS923bands,if UplinkDwelltime=0,max51bytes for eachuplink.441 +(% style="color:red" %)**Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:** 466 466 467 - * 1bytes for each uplink.443 + ~* For AU915/AS923 bands, if UplinkDwell time=0, max 51 bytes for each uplink ( so 51 -5 = 46 max valid date) 468 468 469 - * For U S915 band, max 11 bytes445 + * For AU915/AS923 bands, if UplinkDwell time=1, max 11 bytes for each uplink ( so 11 -5 = 6 max valid date). 470 470 471 - ~*allotherbands:max51 bytes447 + * For US915 band, max 11 bytes for each uplink ( so 11 -5 = 6 max valid date). 472 472 449 + ~* For all other bands: max 51 bytes for each uplink ( so 51 -5 = 46 max valid date). 473 473 474 - Belowarethe uplinkpayloads:451 +=== 3.3.5 Uplink on demand === 475 475 476 - [[image:1654157178836-407.png]]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. 477 477 455 +Downlink control command: 478 478 479 - ===3.3.5 Uplink ondemand===457 +[[0x08 command>>path:#downlink_08]]: Poll an uplink with current command set in RS485-BL. 480 480 481 - Except uplink periodically, RS485-LNis able touplink on demand. The server senddownlink command to RS485-LNandRS485 willuplinkdata base onthecommand.459 +[[0xA8 command>>path:#downlink_A8]]: Send a command to RS485-BL and uplink the output from sensors. 482 482 483 -Downlink control command: 484 484 485 -**0x08 command**: Poll an uplink with current command set in RS485-LN. 486 486 487 -**0xA8 command**: Send a command to RS485-LN and uplink the output from sensors. 463 +1. 464 +11. 465 +111. Uplink on Interrupt 488 488 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]] 489 489 469 +AT+INTMOD=0 Disable Interrupt 490 490 491 -= ==3.3.6 Uplink onInterrupt===471 +AT+INTMOD=1 Interrupt trigger by rising or falling edge. 492 492 493 - RS485-LNsupport externalInterruptuplinksincehardwarev1.2release.473 +AT+INTMOD=2 Interrupt trigger by falling edge. ( Default Value) 494 494 495 - [[image:1654157342174-798.png]]475 +AT+INTMOD=3 Interrupt trigger by rising edge. 496 496 497 -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. 498 498 478 +1. 479 +11. Uplink Payload 499 499 500 -== 3.4 Uplink Payload == 481 +|**Size(bytes)**|**2**|**1**|**Length depends on the return from the commands** 482 +|Value|((( 483 +Battery(mV) 501 501 485 +& 502 502 503 -[[image:image-20220606110929-1.png]] 487 +Interrupt _Flag 488 +)))|((( 489 +PAYLOAD_VER 504 504 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 + 505 505 Below is the decoder for the first 3 bytes. The rest bytes are dynamic depends on different RS485 sensors. 506 506 507 507 508 - == 3.5 Configure RS485-BL viaATorDownlink==497 +function Decoder(bytes, port) { 509 509 510 -((( 511 -User can configure RS485-LN via AT Commands or LoRaWAN Downlink Commands 512 -))) 499 +~/~/Payload Formats of RS485-BL Deceive 513 513 514 -((( 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 + 515 515 There are two kinds of Commands: 516 -))) 517 517 518 -* ((( 519 -(% 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]] 520 -))) 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 521 521 522 -* ((( 523 -(% style="color:#4f81bd" %)**Sensor Related Commands**(%%): These commands are special designed for RS485-LN. User can see these commands below: 524 -))) 538 +* **Sensor Related Commands**: These commands are special designed for RS485-BL. User can see these commands below: 525 525 526 - (((527 - 528 - )))540 +1. 541 +11. 542 +111. Common Commands: 529 529 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]] 530 530 531 -=== 3.5.1 Common Commands === 532 532 533 -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]] 547 +1. 548 +11. 549 +111. Sensor related commands: 534 534 551 +==== Choose Device Type (RS485 or TTL) ==== 535 535 536 - === 3.5.2Sensor relatedcommands===553 +RS485-BL can connect to either RS485 sensors or TTL sensor. User need to specify what type of sensor need to connect. 537 537 538 - Responsefeatureis added tothe server's downlink, a special package with a FPort of 200 will be uploaded immediately after receiving thedata sent by the server.555 +* AT Command 539 539 540 - [[image:image-20220602163333-5.png||height="263"width="1160"]]557 +**AT+MOD=1** ~/~/ Set to support RS485-MODBUS type sensors. User can connect multiply RS485 , Modbus sensors to the A / B pins. 541 541 542 -T hefirstbyte ofthisackage represents whether the configurationissuccessful,00 representsfailure,01 representssuccess.Exceptfor thefirstbyte, theotheristhe previousdownlink. (All commands exceptA8 typecommandsare applicable)559 +**AT+MOD=2** ~/~/ Set to support TTL Level sensors, User can connect one TTL Sensor to the TXD/RXD/GND pins. 543 543 544 544 545 - ===3.5.3 Sensor relatedcommands ===562 +* Downlink Payload 546 546 564 +**0A aa** à same as AT+MOD=aa 547 547 548 548 549 549 550 -==== **RS485 Debug Command**====568 +==== [[RS485 Debug Command>>path:#downlink_A8]] (AT+CFGDEV) ==== 551 551 552 -((( 553 -This command is used to configure the RS485 devices; they won’t be used during sampling. 554 -))) 570 +This command is used to configure the RS485 or TTL sensors; they won’t be used during sampling. 555 555 556 -* ((( 557 -**AT Command** 558 -))) 572 +* AT Command 559 559 560 -(% class="box infomessage" %) 561 -((( 562 -((( 563 -**AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m** 564 -))) 565 -))) 574 +AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m 566 566 567 -((( 568 -m: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command 569 -))) 576 +m: 0: no CRC; 1: add CRC-16/MODBUS in the end of this command. 570 570 571 -* ((( 572 -**Downlink Payload** 573 -))) 574 574 575 -((( 579 + 580 +* Downlink Payload 581 + 576 576 Format: A8 MM NN XX XX XX XX YY 577 -))) 578 578 579 -((( 580 580 Where: 581 -))) 582 582 583 -* ((( 584 -MM: 1: add CRC-16/MODBUS ; 0: no CRC 585 -))) 586 -* ((( 587 -NN: The length of RS485 command 588 -))) 589 -* ((( 590 -XX XX XX XX: RS485 command total NN bytes 591 -))) 592 -* ((( 593 -((( 594 -YY: How many bytes will be uplink from the return of this RS485 command, 595 -))) 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 596 596 597 -* ((( 598 -if YY=0, RS485-LN will execute the downlink command without uplink; 599 -))) 600 -* ((( 601 -if YY>0, RS485-LN will uplink total YY bytes from the output of this RS485 command; Fport=200 602 -))) 603 -* ((( 604 -if YY=FF, RS485-LN will uplink RS485 output with the downlink command content; Fport=200. 605 -))) 606 -))) 591 +**Example 1:** 607 607 608 -((( 609 -**Example 1** ~-~-> Configure without ask for uplink (YY=0) 610 -))) 611 - 612 -((( 613 613 To connect a Modbus Alarm with below commands. 614 -))) 615 615 616 -* ((( 617 -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 -))) 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. 619 619 620 -* ((( 621 -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 -))) 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. 623 623 624 -((( 625 625 So if user want to use downlink command to control to RS485 Alarm, he can use: 626 -))) 627 627 628 -((( 629 -(% style="color:#4f81bd" %)**A8 01 06 0A 05 00 04 00 01 00**(%%): to activate the RS485 Alarm 630 -))) 601 +**A8 01 06 0A 05 00 04 00 01 00**: to activate the RS485 Alarm 631 631 632 -((( 633 -(% style="color:#4f81bd" %)**A8 01 06 0A 05 00 04 00 00 00**(%%): to deactivate the RS485 Alarm 634 -))) 603 +**A8 01 06 0A 05 00 04 00 00 00**: to deactivate the RS485 Alarm 635 635 636 -((( 637 637 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. 638 -))) 639 639 640 -((( 641 - 642 -))) 643 643 644 -((( 645 -**Example 2** ~-~-> Configure with requesting uplink and original downlink command (**YY=FF**) 646 -))) 608 +**Example 2:** 647 647 648 -((( 649 -User in IoT server send a downlink command: (% style="color:#4f81bd" %)**A8 01 06 0A 08 00 04 00 01 YY** 650 -))) 610 +Check TTL Sensor return: 651 651 652 -((( 653 - 654 -))) 612 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image024.png]] 655 655 656 -((( 657 -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: 658 -))) 659 659 660 -((( 661 - **A8** (% style="color:#4f81bd" %)**0A 08 00 04 00 **(% style="color:red" %)**01 06** ** **(% style="color:green" %)**0A 08 00 04 00 00** 662 -))) 663 663 664 -((( 665 - [[image:1654159460680-153.png]] 666 -))) 667 667 617 +==== Set Payload version ==== 668 668 669 - 670 - 671 -==== **Set Payload version** ==== 672 - 673 -((( 674 674 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. 675 -))) 676 676 677 -* ((( 678 -**AT Command:** 679 -))) 621 +* AT Command: 680 680 681 -(% class="box infomessage" %) 682 -((( 683 -((( 684 -**AT+PAYVER: Set PAYVER field = 1** 685 -))) 686 -))) 623 +AT+PAYVER: Set PAYVER field = 1 687 687 688 -* ((( 689 -**Downlink Payload:** 690 -))) 691 691 692 -((( 693 -**0xAE 01** ~-~-> Set PAYVER field = 0x01 694 -))) 626 +* Downlink Payload: 695 695 696 -((( 697 -**0xAE 0F** ~-~-> Set PAYVER field = 0x0F 698 -))) 628 +0xAE 01 à Set PAYVER field = 0x01 699 699 630 +0xAE 0F à Set PAYVER field = 0x0F 700 700 701 701 633 +==== Set RS485 Sampling Commands ==== 702 702 703 - ====**SetRS485 Sampling Commands**====635 +AT+COMMANDx, AT+DATACUTx and AT+SEARCHx 704 704 705 -((( 706 -AT+COMMANDx or AT+DATACUTx 707 -))) 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]]. 708 708 709 -((( 710 -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"]]. 711 -))) 712 712 713 -((( 714 - 715 -))) 640 +* AT Command: 716 716 717 -* ((( 718 -**AT Command:** 719 -))) 642 +AT+COMMANDx: Configure RS485 read command to sensor. 720 720 721 -(% class="box infomessage" %) 722 -((( 723 -((( 724 -**AT+COMMANDx: Configure RS485 read command to sensor.** 725 -))) 726 -))) 644 +AT+DATACUTx: Configure how to handle return from RS485 devices. 727 727 728 -(% class="box infomessage" %) 729 -((( 730 -((( 731 -**AT+DATACUTx: Configure how to handle return from RS485 devices.** 732 -))) 733 -))) 646 +AT+SEARCHx: Configure search command 734 734 735 -((( 736 - 737 -))) 738 738 739 -* ((( 740 -**Downlink Payload:** 741 -))) 649 +* Downlink Payload: 742 742 743 -((( 744 -**0xAF** downlink command can be used to set AT+COMMANDx or AT+DATACUTx. 745 -))) 651 +0xAF downlink command can be used to set AT+COMMANDx or AT+DATACUTx. 746 746 747 -((( 748 -(% style="color:red" %)**Note**(%%): if user use AT+COMMANDx to add a new command, he also need to send AT+DATACUTx downlink. 749 -))) 653 +Note: if user use AT+COMMANDx to add a new command, he also need to send AT+DATACUTx downlink. 750 750 751 -((( 752 752 Format: AF MM NN LL XX XX XX XX YY 753 -))) 754 754 755 -((( 756 756 Where: 757 -))) 758 758 759 -* ((( 760 -MM: the ATCOMMAND or AT+DATACUT to be set. Value from 01 ~~ 0F, 761 -))) 762 -* ((( 763 -NN: 0: no CRC; 1: add CRC-16/MODBUS ; 2: set the AT+DATACUT value. 764 -))) 765 -* ((( 766 -LL: The length of AT+COMMAND or AT+DATACUT command 767 -))) 768 -* ((( 769 -XX XX XX XX: AT+COMMAND or AT+DATACUT command 770 -))) 771 -* ((( 772 -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. 773 -))) 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. 774 774 775 -((( 776 -**Example:** 777 -))) 665 +Example: 778 778 779 -((( 780 -(% 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 781 -))) 667 +**AF 03 01 06 0A 05 00 04 00 01 00**: Same as AT+COMMAND3=0A 05 00 04 00 01,1 782 782 783 -((( 784 -(% 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** 785 -))) 669 +**AF 03 02 06 10 01 05 06 09 0A 00**: Same as AT+DATACUT3=**16**,**1**,**5+6+9+10** 786 786 787 -((( 788 -(% 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** 789 -))) 671 +**AF 03 02 06 0B 02 05 07 08 0A 00**: Same as AT+DATACUT3=**11**,**2**,**5~~7+8~~10** 790 790 791 791 674 +0xAB downlink command can be used for set AT+SEARCHx 792 792 676 +Example: **AB aa 01 03 xx xx xx** (03 here means there are total 3 bytes after 03) So 793 793 794 -==== **Fast command to handle MODBUS device** ==== 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 795 795 796 -((( 797 -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]]. 798 -))) 681 +**AB aa 02 03 xx xx xx 02 yy yy** same as **AT+SEARCHaa=2,xx xx xx+yy yy** 799 799 800 -((( 801 -This command is valid since v1.3 firmware version 802 -))) 803 803 804 -((( 805 -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. 806 -))) 684 +==== Fast command to handle MODBUS device ==== 807 807 808 -((( 809 - 810 -))) 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]]. 811 811 812 -((( 813 -**Example:** 814 -))) 688 +This command is valid since v1.3 firmware version 815 815 816 -* ((( 817 -AT+MBFUN=1 and AT+DATACUT1/AT+DATACUT2 are not configure (0,0,0). So RS485-LN. 818 -))) 819 -* ((( 820 -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. 821 -))) 822 -* ((( 823 -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. 824 -))) 825 825 826 - [[image:image-20220602165351-6.png]]691 +AT+MBFUN has only two value: 827 827 828 - [[image:image-20220602165351-7.png]]693 +* AT+MBFUN=1: Enable Modbus reading. And get response base on the MODBUS return 829 829 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. 830 830 697 +* AT+MBFUN=0: Disable Modbus fast reading. 831 831 699 +Example: 832 832 833 -==== **RS485 command timeout** ==== 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. 834 834 835 -((( 836 -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. 837 -))) 705 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image025.png]] 838 838 839 -((( 840 -Default value: 0, range: 0 ~~ 65 seconds 841 -))) 842 842 843 -* ((( 844 -**AT Command:** 845 -))) 708 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image026.png]] 846 846 847 -(% class="box infomessage" %) 848 -((( 849 -((( 850 -**AT+CMDDLaa=hex(bb cc)*1000** 851 -))) 852 -))) 853 853 854 -((( 855 -**Example:** 856 -))) 711 +* Downlink Commands: 857 857 858 -((( 859 -**AT+CMDDL1=1000** to send the open time to 1000ms 860 -))) 713 +A9 aa -à Same as AT+MBFUN=aa 861 861 862 -((( 863 - 864 -))) 865 865 866 -* ((( 867 -**Downlink Payload:** 868 -))) 716 +==== RS485 command timeout ==== 869 869 870 -((( 871 -**0x AA aa bb cc** 872 -))) 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. 873 873 874 -((( 875 -Same as: AT+CMDDLaa=hex(bb cc)*1000 876 -))) 720 +Default value: 0, range: 0 ~~ 5 seconds 877 877 878 -((( 879 - **Example:** 880 -))) 881 881 882 -((( 883 - 0xAA 01 00 01 ~-~-> Same as **AT+CMDDL1=1000 ms** 884 -))) 723 +* AT Command: 885 885 725 +AT+CMDDLaa=hex(bb cc) 886 886 727 +Example: 887 887 729 +**AT+CMDDL1=1000** to send the open time to 1000ms 888 888 889 -==== **Uplink payload mode** ==== 890 890 891 -((( 892 -Define to use one uplink or multiple uplinks for the sampling. 893 -))) 732 +* Downlink Payload: 894 894 895 -((( 896 -The use of this command please see: [[Compose Uplink payload>>||anchor="H3.3.4Composetheuplinkpayload"]] 897 -))) 734 +0x AA aa bb cc 898 898 899 -* ((( 900 -**AT Command:** 901 -))) 736 +Same as: AT+CMDDLaa=hex(bb cc) 902 902 903 -(% class="box infomessage" %) 904 -((( 905 -((( 906 -**AT+DATAUP=0** 907 -))) 908 -))) 738 + Example: 909 909 910 -(% class="box infomessage" %) 911 -((( 912 -((( 913 -**AT+DATAUP=1** 914 -))) 915 -))) 740 + 0xAA 01 03 E8 à Same as **AT+CMDDL1=1000 ms** 916 916 917 -((( 918 - 919 -))) 920 920 921 -* ((( 922 -**Downlink Payload:** 923 -))) 743 +==== [[Uplink>>path:#downlink_A8]] payload mode ==== 924 924 925 -((( 926 -**0xAD 00** **~-~->** Same as AT+DATAUP=0 927 -))) 745 +Define to use one uplink or multiple uplinks for the sampling. 928 928 929 -((( 930 -**0xAD 01** **~-~->** Same as AT+DATAUP=1 931 -))) 747 +The use of this command please see: [[Compose Uplink payload>>path:#DataUP]] 932 932 749 +* AT Command: 933 933 751 +AT+DATAUP=0 934 934 753 +AT+DATAUP=1 935 935 936 -==== **Manually trigger an Uplink** ==== 937 937 938 -((( 939 -Ask device to send an uplink immediately. 940 -))) 756 +* Downlink Payload: 941 941 942 -* ((( 943 -**AT Command:** 944 -))) 758 +0xAD 00 à Same as AT+DATAUP=0 945 945 946 -((( 947 -No AT Command for this, user can press the [[ACT button>>||anchor="H3.7Buttons"]] for 1 second for the same. 948 -))) 760 +0xAD 01 à Same as AT+DATAUP=1 949 949 950 -((( 951 - 952 -))) 953 953 954 -* ((( 955 -**Downlink Payload:** 956 -))) 763 +==== Manually trigger an Uplink ==== 957 957 958 -((( 959 -**0x08 FF**, RS485-LN will immediately send an uplink. 960 -))) 765 +Ask device to send an uplink immediately. 961 961 767 +* Downlink Payload: 962 962 769 +0x08 FF, RS485-BL will immediately send an uplink. 963 963 964 964 965 -==== **Clear RS485 Command**====772 +==== Clear RS485 Command ==== 966 966 967 -((( 968 968 The AT+COMMANDx and AT+DATACUTx settings are stored in special location, user can use below command to clear them. 969 -))) 970 970 971 -* ((( 972 -**AT Command:** 973 -))) 974 974 975 -((( 777 +* AT Command: 778 + 976 976 **AT+CMDEAR=mm,nn** mm: start position of erase ,nn: stop position of erase 977 -))) 978 978 979 -((( 980 980 Etc. AT+CMDEAR=1,10 means erase AT+COMMAND1/AT+DATACUT1 to AT+COMMAND10/AT+DATACUT10 981 -))) 982 982 983 -((( 984 984 Example screen shot after clear all RS485 commands. 985 -))) 986 986 987 -((( 988 - 989 -))) 990 990 991 - (((786 + 992 992 The uplink screen shot is: 993 -))) 994 994 995 -[[image: 1654160691922-496.png]]789 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png]] 996 996 997 997 998 -* ((( 999 -**Downlink Payload:** 1000 -))) 792 +* Downlink Payload: 1001 1001 1002 -((( 1003 -**0x09 aa bb** same as AT+CMDEAR=aa,bb 1004 -))) 794 +0x09 aa bb same as AT+CMDEAR=aa,bb 1005 1005 1006 1006 797 +==== Set Serial Communication Parameters ==== 1007 1007 1008 - 1009 -==== **Set Serial Communication Parameters** ==== 1010 - 1011 -((( 1012 1012 Set the Rs485 serial communication parameters: 1013 -))) 1014 1014 1015 -* ((( 1016 -**AT Command:** 1017 -))) 801 +* AT Command: 1018 1018 1019 -((( 1020 1020 Set Baud Rate: 1021 -))) 1022 1022 1023 -(% class="box infomessage" %) 1024 -((( 1025 -((( 1026 -**AT+BAUDR=9600** ~/~/ Options: (1200,2400,4800,14400,19200,115200) 1027 -))) 1028 -))) 805 +AT+BAUDR=9600 ~/~/ Options: (1200,2400,4800,14400,19200,115200) 1029 1029 1030 -((( 1031 -Set UART Parity 1032 -))) 1033 1033 1034 -(% class="box infomessage" %) 1035 -((( 1036 -((( 1037 -**AT+PARITY=0** ~/~/ Option: 0: no parity, 1: odd parity, 2: even parity 1038 -))) 1039 -))) 808 +Set UART parity 1040 1040 1041 -((( 810 +AT+PARITY=0 ~/~/ Option: 0: no parity, 1: odd parity, 2: even parity 811 + 812 + 1042 1042 Set STOPBIT 1043 -))) 1044 1044 1045 -(% class="box infomessage" %) 1046 -((( 1047 -((( 1048 -**AT+STOPBIT=0** ~/~/ Option: 0 for 1bit; 1 for 1.5 bit ; 2 for 2 bits 1049 -))) 1050 -))) 815 +AT+STOPBIT=0 ~/~/ Option: 0 for 1bit; 1 for 1.5 bit ; 2 for 2 bits 1051 1051 1052 -((( 1053 - 1054 -))) 1055 1055 1056 -* ((( 1057 -**Downlink Payload:** 1058 -))) 818 +* Downlink Payload: 1059 1059 1060 -((( 1061 -**A7 01 aa bb**: Same AT+BAUDR=hex(aa bb)*100 1062 -))) 820 +A7 01 aa bb: Same AT+BAUDR=hex(aa bb)*100 1063 1063 1064 -((( 1065 -**Example:** 1066 -))) 822 +Example: 1067 1067 1068 -* ((( 1069 -A7 01 00 60 same as AT+BAUDR=9600 1070 -))) 1071 -* ((( 1072 -A7 01 04 80 same as AT+BAUDR=115200 1073 -))) 824 +* A7 01 00 60 same as AT+BAUDR=9600 825 +* A7 01 04 80 same as AT+BAUDR=115200 1074 1074 1075 -((( 1076 1076 A7 02 aa: Same as AT+PARITY=aa (aa value: 00 , 01 or 02) 1077 -))) 1078 1078 1079 -((( 1080 1080 A7 03 aa: Same as AT+STOPBIT=aa (aa value: 00 , 01 or 02) 1081 -))) 1082 1082 1083 1083 832 +==== Control output power duration ==== 1084 1084 834 +User can set the output power duration before each sampling. 1085 1085 1086 - ==3.6 Listeningmode for RS485network ==836 +* AT Command: 1087 1087 1088 -((( 1089 -This feature support since firmware v1.4 1090 -))) 838 +Example: 1091 1091 1092 -((( 1093 -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. 1094 -))) 840 +AT+3V3T=1000 ~/~/ 3V3 output power will open 1s before each sampling. 1095 1095 1096 - [[image:image-20220602171200-8.png||height="567"width="1007"]]842 +AT+5VT=1000 ~/~/ +5V output power will open 1s before each sampling. 1097 1097 1098 -((( 1099 -To enable the listening mode, use can run the command AT+RXMODE. 1100 -))) 1101 1101 1102 -((( 1103 - 1104 -))) 845 +* LoRaWAN Downlink Command: 1105 1105 1106 -(% border="1" cellspacing="10" style="background-color:#ffffcc; width:500px" %) 1107 -|=(% style="width: 161px;" %)((( 1108 -**Command example:** 1109 -)))|=(% style="width: 337px;" %)((( 1110 -**Function** 1111 -))) 1112 -|(% style="width:161px" %)((( 1113 -AT+RXMODE=1,10 1114 -)))|(% style="width:337px" %)((( 1115 -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. 1116 -))) 1117 -|(% style="width:161px" %)((( 1118 -AT+RXMODE=2,500 1119 -)))|(% style="width:337px" %)((( 1120 -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 1121 -))) 1122 -|(% style="width:161px" %)((( 1123 -AT+RXMODE=0,0 1124 -)))|(% style="width:337px" %)((( 1125 -Disable listening mode. This is the default settings. 1126 -))) 1127 -|(% style="width:161px" %)((( 1128 - 1129 -)))|(% style="width:337px" %)((( 1130 -A6 aa bb cc same as AT+RXMODE=aa,(bb<<8 | cc) 1131 -))) 847 +07 01 aa bb Same as AT+5VT=(aa bb) 1132 1132 1133 -((( 1134 -**Downlink Command:** 1135 -))) 849 +07 02 aa bb Same as AT+3V3T=(aa bb) 1136 1136 1137 -((( 1138 -**0xA6 aa bb cc ** same as AT+RXMODE=aa,(bb<<8 | cc) 1139 -))) 1140 1140 1141 -((( 1142 - 1143 -))) 1144 1144 1145 -((( 1146 -**Example**: 1147 -))) 1148 1148 1149 -((( 1150 -The RS485-LN is set to AT+RXMODE=2,1000 1151 -))) 854 +1. 855 +11. Buttons 1152 1152 1153 -((( 1154 -There is a two Modbus commands in the RS485 network as below: 1155 -))) 857 +|**Button**|**Feature** 858 +|**RST**|Reboot RS485-BL 1156 1156 1157 -((( 1158 -The Modbus master send a command: (% style="background-color:#ffc000" %)01 03 00 00 00 02 c4 0b 1159 -))) 860 +1. 861 +11. +3V3 Output 1160 1160 1161 -((( 1162 -And Modbus slave reply with: (% style="background-color:green" %)01 03 04 00 00 00 00 fa 33 1163 -))) 863 +RS485-BL has a Controllable +3V3 output, user can use this output to power external sensor. 1164 1164 1165 -((( 1166 -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 1167 -))) 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. 1168 1168 1169 -((( 1170 -[[image:image-20220602171200-9.png]] 1171 -))) 1172 1172 1173 -((( 1174 - 1175 -))) 868 +The +3V3 output time can be controlled by AT Command. 1176 1176 1177 -((( 1178 -(% 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. 1179 -))) 870 +**AT+3V3T=1000** 1180 1180 872 +Means set +3v3 valid time to have 1000ms. So, the real +3v3 output will actually have 1000ms + sampling time for other sensors. 1181 1181 1182 -== 3.7 Buttons == 1183 1183 875 +By default, the AT+3V3T=0. This is a special case, means the +3V3 output is always on at any time 1184 1184 1185 -(% border="1" cellspacing="10" style="background-color:#f7faff; width:400px" %) 1186 -|=(% style="width: 50px;" %)**Button**|=(% style="width: 350px;" %)**Feature** 1187 -|(% style="width:50px" %)**ACT**|(% style="width:350px" %)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** 1188 -|(% style="width:50px" %)**RST**|(% style="width:350px" %)Reboot RS485 1189 -|(% style="width:50px" %)**PRO**|(% style="width:350px" %)Use for upload image, see [[How to Update Image>>||anchor="H6.1Howtoupgradetheimage3F"]] 1190 1190 1191 -== 3.8 LEDs == 878 +1. 879 +11. +5V Output 1192 1192 881 +RS485-BL has a Controllable +5V output, user can use this output to power external sensor. 1193 1193 1194 -(% border="1" cellspacing="10" style="background-color:#f7faff; width:430px" %) 1195 -|=(% style="width: 50px;" %)**LEDs**|=(% style="width: 380px;" %)**Feature** 1196 -|**PWR**|Always on if there is power 1197 -|**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. 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. 1198 1198 1199 1199 1200 - =4.CaseStudy=886 +The 5V output time can be controlled by AT Command. 1201 1201 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]]888 +**AT+5VT=1000** 1203 1203 890 +Means set 5V valid time to have 1000ms. So, the real 5V output will actually have 1000ms + sampling time for other sensors. 1204 1204 1205 -= 5. Use AT Command = 1206 1206 1207 - ==5.1AccessATCommand==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. 1208 1208 1209 -((( 1210 -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. 1211 -))) 1212 1212 1213 -[[image:1654162355560-817.png]] 1214 1214 1215 1215 1216 -((( 1217 -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: 1218 -))) 898 +1. 899 +11. LEDs 1219 1219 1220 -[[image:1654162368066-342.png]] 901 +|**LEDs**|**Feature** 902 +|**LED1**|Blink when device transmit a packet. 1221 1221 904 +1. 905 +11. Switch Jumper 1222 1222 1223 -((( 1224 -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/]] 907 +|**Switch Jumper**|**Feature** 908 +|**SW1**|((( 909 +ISP position: Upgrade firmware via UART 910 + 911 +Flash position: Configure device, check running status. 1225 1225 ))) 913 +|**SW2**|((( 914 +5V position: set to compatible with 5v I/O. 1226 1226 916 +3.3v position: set to compatible with 3.3v I/O., 917 +))) 1227 1227 919 ++3.3V: is always ON 1228 1228 1229 - ==5.2CommonATCommandSequence==921 ++5V: Only open before every sampling. The time is by default, it is AT+5VT=0. Max open time. 5000 ms. 1230 1230 1231 - === 5.2.1Multi-channel ABP mode (UsewithSX1301/LG308) ===923 +1. Case Study 1232 1232 1233 - If device hasnotjoinednetworkyet:925 +User can check this URL for some case studies. 1234 1234 1235 -(% class="box infomessage" %) 1236 -((( 1237 -**AT+FDR** 1238 -))) 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]] 1239 1239 1240 -(% class="box infomessage" %) 1241 -((( 1242 -**AT+NJM=0** 1243 -))) 1244 1244 1245 -(% class="box infomessage" %) 1246 -((( 1247 -**ATZ** 1248 -))) 1249 1249 1250 1250 1251 -If device already joined network: 932 +1. Use AT Command 933 +11. Access AT Command 1252 1252 1253 -(% class="box infomessage" %) 1254 -((( 1255 -**AT+NJM=0** 1256 -))) 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. 1257 1257 1258 -(% class="box infomessage" %) 1259 -((( 1260 -**ATZ** 1261 -))) 937 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image027.png]] 1262 1262 1263 1263 1264 - ===5.5.2Single-channelABPmode(UsewithLG01/LG02)===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: 1265 1265 942 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image028.png]] 1266 1266 1267 -(% style="background-color:#dcdcdc" %)**AT+FDR** (%%) Reset Parameters to Factory Default, Keys Reserve 1268 1268 1269 -(% style="background-color:#dcdcdc" %)**AT+NJM=0 **(%%)Set to ABP mode 1270 1270 1271 - (%style="background-color:#dcdcdc"%)**AT+ADR=0** (%%)SettheAdaptiveDataRateOff946 +More detail AT Command manual can be found at [[AT Command Manual>>path:#AT_COMMAND]] 1272 1272 1273 -(% style="background-color:#dcdcdc" %)**AT+DR=5** (%%)Set Data Rate 1274 1274 1275 -(% style="background-color:#dcdcdc" %)**AT+TDC=60000** (%%) Set transmit interval to 60 seconds 1276 1276 1277 -(% style="background-color:#dcdcdc" %)**AT+CHS=868400000**(%%) Set transmit frequency to 868.4Mhz 950 +1. 951 +11. Common AT Command Sequence 952 +111. Multi-channel ABP mode (Use with SX1301/LG308) 1278 1278 1279 - (%style="background-color:#dcdcdc" %)**AT+RX2FQ=868400000** (%%) SetRX2Frequencyto868.4Mhz (according to theresultfromserver)954 +If device has not joined network yet: 1280 1280 1281 - (% style="background-color:#dcdcdc" %)**AT+RX2DR=5** (%%) Set RX2DR to match the downlink DR from server. see below956 +AT+FDR 1282 1282 1283 - (% 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.958 +AT+NJM=0 1284 1284 1285 - (% style="background-color:#dcdcdc" %)**ATZ** (%%) Reset MCU960 +ATZ 1286 1286 1287 1287 1288 - (%style="color:red"%)**Note:**963 +If device already joined network: 1289 1289 1290 -(% style="color:red" %)1. Make sure the device is set to ABP mode in the IoT Server. 1291 -2. Make sure the LG01/02 gateway RX frequency is exactly the same as AT+CHS setting. 1292 -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. 1293 -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 965 +AT+NJM=0 1294 1294 1295 - [[image:1654162478620-421.png]]967 +ATZ 1296 1296 969 +1. 970 +11. 971 +111. Single-channel ABP mode (Use with LG01/LG02) 1297 1297 1298 - =6.FAQ=973 +AT+FDR Reset Parameters to Factory Default, Keys Reserve 1299 1299 1300 -= =6.1Howtoupgradethe image? ==975 +AT+NJM=0 Set to ABP mode 1301 1301 1302 -((( 1303 -The RS485-LN LoRaWAN Controller is shipped with a 3.5mm cable, the cable is used to upload image to RS485-LN to: 1304 -))) 977 +AT+ADR=0 Set the Adaptive Data Rate Off 1305 1305 1306 -* ((( 1307 -Support new features 1308 -))) 1309 -* ((( 1310 -For bug fix 1311 -))) 1312 -* ((( 1313 -Change LoRaWAN bands. 1314 -))) 979 +AT+DR=5 Set Data Rate 1315 1315 1316 -((( 1317 -Below shows the hardware connection for how to upload an image to RS485-LN: 1318 -))) 981 +AT+TDC=60000 Set transmit interval to 60 seconds 1319 1319 1320 - [[image:1654162535040-878.png]]983 +AT+CHS=868400000 Set transmit frequency to 868.4Mhz 1321 1321 1322 - **Step1:**Download[[flashloader>>url:https://www.st.com/content/st_com/en/products/development-tools/software-development-tools/stm32-software-development-tools/stm32-programmers/flasher-stm32.html]].985 +AT+RX2FQ=868400000 Set RX2Frequency to 868.4Mhz (according to the result from server) 1323 1323 1324 - **Step2**:Downloadthe[[LT Image files>>url:http://www.dragino.com/downloads/index.php?dir=LT_LoRa_IO_Controller/LT33222-L/image/]].987 +AT+RX2DR=5 Set RX2DR to match the downlink DR from server. see below 1325 1325 1326 - **Step3:**Openflashloader;choose thecorrectCOMportto update.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. 1327 1327 1328 -((( 1329 -((( 1330 -(% 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. 1331 -))) 1332 -))) 991 +ATZ Reset MCU 1333 1333 993 +**Note:** 1334 1334 1335 -[[image:image-20220602175818-12.png]] 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 1336 1336 1000 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image029.png]] 1337 1337 1338 -[[image:image-20220602175848-13.png]] 1339 1339 1003 +1. FAQ 1004 +11. How to upgrade the image? 1340 1340 1341 - [[image:image-20220602175912-14.png]]1006 +The RS485-BL LoRaWAN Controller is shipped with a 3.5mm cable, the cable is used to upload image to RS485-BL to: 1342 1342 1008 +* Support new features 1009 +* For bug fix 1010 +* Change LoRaWAN bands. 1343 1343 1344 - **Notice**:In case userhas losttheprogram cable.Usercanhand madeefroma3.5mm cable.The pin mappingis:1012 +Below shows the hardware connection for how to upload an image to RS485-BL: 1345 1345 1346 -[[image:image -20220602175638-10.png]]1014 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image030.png]] 1347 1347 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]]. 1348 1348 1349 - == 6.2Howtochangethe LoRaFrequency Bands/Region?=1018 +**Step2**: Download the [[LT Image files>>url:http://www.dragino.com/downloads/index.php?dir=LT_LoRa_IO_Controller/LT33222-L/image/]]. 1350 1350 1351 - User can followtheintroduction for [[how to upgradeimage>>||anchor="H6.1Howtoupgradetheimage3F"]]. Whendownloadtheimages,choose the requiredimagefile fordownload.1020 +**Step3: **Open flashloader; choose the correct COM port to update. 1352 1352 1353 1353 1354 -== 6.3 How many RS485-Slave can RS485-BL connects? == 1023 +|((( 1024 +HOLD PRO then press the RST button, SYS will be ON, then click next 1025 +))) 1355 1355 1356 -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"]]. 1027 +|((( 1028 +Board detected 1029 +))) 1357 1357 1031 +|((( 1032 + 1033 +))) 1358 1358 1359 - == 6.4 Compatiblequestion toChirpStackandTTILoRaWANserver ? ==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]] 1360 1360 1361 -When user need to use with ChirpStack or TTI. Please set AT+RPL=4. 1362 1362 1363 -Detail info check this link: [[Set Packet Receiving Response Level>>doc:Main.End Device AT Commands and Downlink Command.WebHome||anchor="H7.23SetPacketReceivingResponseLevel"]] 1364 1364 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]] 1365 1365 1366 -= 7. Trouble Shooting = 1367 1367 1368 - == 7.1Downlink doesn’twork,howtoveit? ==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]] 1369 1369 1370 -Please see this link for debug: [[LoRaWAN Communication Debug>>doc:Main.LoRaWAN Communication Debug.WebHome]] 1371 1371 1045 +1. 1046 +11. How to change the LoRa Frequency Bands/Region? 1372 1372 1373 - ==7.2 Why Ican’tjoinTTNV3inUS915/AU915bands?==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. 1374 1374 1375 -It might about the channels mapping. Please see for detail: [[Notice of Frequency band>>doc:Main.LoRaWAN Communication Debug.WebHome||anchor="H2.NoticeofUS9152FCN4702FAU915Frequencyband"]] 1376 1376 1377 1377 1378 -= 8. Order Info = 1052 +1. 1053 +11. How many RS485-Slave can RS485-BL connects? 1379 1379 1380 - (%style="color:blue"%)**PartNumber:RS485-LN-XXX**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]]. 1381 1381 1382 -(% style="color:blue" %)**XXX:** 1383 1383 1384 -* (% style="color:blue" %)**EU433**(%%): frequency bands EU433 1385 -* (% style="color:blue" %)**EU868**(%%): frequency bands EU868 1386 -* (% style="color:blue" %)**KR920**(%%): frequency bands KR920 1387 -* (% style="color:blue" %)**CN470**(%%): frequency bands CN470 1388 -* (% style="color:blue" %)**AS923**(%%): frequency bands AS923 1389 -* (% style="color:blue" %)**AU915**(%%): frequency bands AU915 1390 -* (% style="color:blue" %)**US915**(%%): frequency bands US915 1391 -* (% style="color:blue" %)**IN865**(%%): frequency bands IN865 1392 -* (% style="color:blue" %)**RU864**(%%): frequency bands RU864 1393 -* (% style="color:blue" %)**KZ865**(%%): frequency bands KZ865 1394 1394 1395 -= 9.Packing Info = 1396 1396 1060 +1. Trouble Shooting 1061 +11. Downlink doesn’t work, how to solve it? 1397 1397 1398 - **PackageIncludes**:1063 +Please see this link for debug: 1399 1399 1400 -* RS485-LN x 1 1401 -* Stick Antenna for LoRa RF part x 1 1402 -* Program cable x 1 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]] 1403 1403 1404 -**Dimension and weight**: 1405 1405 1406 -* Device Size: 13.5 x 7 x 3 cm 1407 -* Device Weight: 105g 1408 -* Package Size / pcs : 14.5 x 8 x 5 cm 1409 -* Weight / pcs : 170g 1410 1410 1411 -= 10. FCC Caution for RS485LN-US915 = 1069 +1. 1070 +11. Why I can’t join TTN V3 in US915 /AU915 bands? 1412 1412 1413 -((( 1414 -Any Changes or modifications not expressly approved by the party responsible for compliance could void the user's authority to operate the equipment. 1415 -))) 1072 +It might about the channels mapping. Please see for detail. 1416 1416 1417 -((( 1418 -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. 1419 -))) 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]] 1420 1420 1421 -((( 1422 - 1423 -))) 1424 1424 1425 -((( 1426 -**IMPORTANT NOTE:** 1427 -))) 1428 1428 1429 -((( 1430 -**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: 1431 -))) 1078 +1. Order Info 1432 1432 1433 -((( 1434 -—Reorient or relocate the receiving antenna. 1435 -))) 1080 +**Part Number: RS485-BL-XXX** 1436 1436 1437 -((( 1438 -—Increase the separation between the equipment and receiver. 1439 -))) 1082 +**XXX:** 1440 1440 1441 -((( 1442 -—Connect the equipment into an outlet on a circuit different from that to which the receiver is connected. 1443 -))) 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 1444 1444 1445 -((( 1446 -—Consult the dealer or an experienced radio/TV technician for help. 1447 -))) 1095 +1. Packing Info 1448 1448 1449 -((( 1450 - 1451 -))) 1097 +**Package Includes**: 1452 1452 1453 - (((1454 -* *FCCRadiationExposureStatement:**1455 - )))1099 +* RS485-BL x 1 1100 +* Stick Antenna for LoRa RF part x 1 1101 +* Program cable x 1 1456 1456 1457 -((( 1458 -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. 1459 -))) 1103 +**Dimension and weight**: 1460 1460 1105 +* Device Size: 13.5 x 7 x 3 cm 1106 +* Device Weight: 105g 1107 +* Package Size / pcs : 14.5 x 8 x 5 cm 1108 +* Weight / pcs : 170g 1461 1461 1462 - =11. Support=1110 +1. Support 1463 1463 1464 -* ((( 1465 -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. 1466 -))) 1467 -* ((( 1468 -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]]. 1469 -))) 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 1114 + 1115 +[[support@dragino.com>>url:file:///D:/市场资料/说明书/LoRa/LT系列/support@dragino.com]]
- 1654157178836-407.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -179.9 KB - Content
- 1654157342174-798.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -31.9 KB - Content
- 1654158783574-851.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -40.6 KB - Content
- 1654159460680-153.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -24.9 KB - Content
- 1654160691922-496.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -109.3 KB - Content
- 1654162355560-817.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -670.0 KB - Content
- 1654162368066-342.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -192.9 KB - Content
- 1654162478620-421.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -158.9 KB - Content
- 1654162535040-878.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -670.0 KB - Content
- image-20220602155039-4.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -24.6 KB - Content
- image-20220602163333-5.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -48.2 KB - Content
- image-20220602165351-6.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -10.6 KB - Content
- image-20220602165351-7.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -19.3 KB - Content
- image-20220602171200-8.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -276.1 KB - Content
- image-20220602171200-9.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -10.0 KB - Content
- image-20220602175638-10.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -85.5 KB - Content
- image-20220602175743-11.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -85.5 KB - Content
- image-20220602175818-12.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -102.5 KB - Content
- image-20220602175848-13.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -250.9 KB - Content
- image-20220602175912-14.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -176.1 KB - Content
- image-20220606110929-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -13.9 KB - Content