Last modified by Xiaoling on 2025/04/23 15:56
<
From version < 57.45 >
edited by Xiaoling
on 2022/06/06 10:13
To version < 32.13 >
edited by Xiaoling
on 2022/06/02 15:26
>
Change comment: There is no comment for this version

Summary

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

Applications

Navigation

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