Skip to Content
Last modified by Xiaoling on 2025/04/23 15:57
From version 29.4
edited by Xiaoling
on 2022/06/01 17:59
Change comment: There is no comment for this version
To version 15.5
edited by Xiaoling
on 2022/05/19 17:52
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -7,7 +7,6 @@
7 7  **RS485-BL – Waterproof RS485 to LoRaWAN Converter User Manual**
8 8  
9 9  
10 -
11 11  **Table of Contents:**
12 12  
13 13  
... ... @@ -14,7 +14,6 @@
14 14  
15 15  
16 16  
17 -
18 18  = 1.Introduction =
19 19  
20 20  == 1.1 What is RS485-BL RS485 to LoRaWAN Converter ==
... ... @@ -305,102 +305,88 @@
305 305  )))
306 306  )))
307 307  
308 -=== 3.3.2 Configure sensors ===
309 309  
310 -(((
311 -Some sensors might need to configure before normal operation. User can configure such sensor via PC or through RS485-BL AT Commands (% style="color:#4f81bd" %)**AT+CFGDEV**.
312 -)))
313 313  
314 -(((
315 -When user issue an (% style="color:#4f81bd" %)**AT+CFGDEV**(%%) command, Each (% style="color:#4f81bd" %)**AT+CFGDEV**(%%) equals to send a command to the RS485 or TTL sensors. This command will only run when user input it and won’t run during each sampling.
316 -)))
317 317  
318 -(% border="1" style="background-color:#ffffcc; color:green; width:806px" %)
319 -|**AT Commands**|(% style="width:418px" %)**Description**|(% style="width:256px" %)**Example**
320 -|AT+CFGDEV|(% style="width:418px" %)(((
309 +1.
310 +11.
311 +111. Configure sensors
312 +
313 +Some sensors might need to configure before normal operation. User can configure such sensor via PC or through RS485-BL AT Commands AT+CFGDEV.
314 +
315 +
316 +When user issue an AT+CFGDEV command, Each AT+CFGDEV equals to send a command to the RS485 or TTL sensors. This command will only run when user input it and won’t run during each sampling.
317 +
318 +|**AT Commands**|**Description**|**Example**
319 +|AT+CFGDEV|(((
321 321  This command is used to configure the RS485/TTL devices; they won’t be used during sampling.
322 322  
323 -AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,
322 +AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
324 324  
325 -mm: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
326 -)))|(% style="width:256px" %)AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
324 +m: 0: no CRC, 1: add CRC-16/MODBUS in the end of this command
325 +)))|AT+CFGDEV=xx xx xx xx xx xx xx xx xx xx xx xx,m
327 327  
328 328  Detail of AT+CFGDEV command see [[AT+CFGDEV detail>>path:#AT_CFGDEV]].
329 329  
330 -=== 3.3.3 Configure read commands for each sampling ===
331 331  
332 -(((
330 +
331 +
332 +
333 +1.
334 +11.
335 +111. Configure read commands for each sampling
336 +
333 333  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.
334 -)))
335 335  
336 -(((
339 +
337 337  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.
338 -)))
339 339  
340 -(((
342 +
341 341  To save the LoRaWAN network bandwidth, we might need to read data from different sensors and combine their valid value into a short payload.
342 -)))
343 343  
344 -(((
345 +
345 345  This section describes how to achieve above goals.
346 -)))
347 347  
348 -(((
348 +
349 349  During each sampling, the RS485-BL can support 15 commands to read sensors. And combine the return to one or several uplink payloads.
350 -)))
351 351  
352 -(((
351 +
353 353  **Command from RS485-BL to Sensor:**
354 -)))
355 355  
356 -(((
357 357  RS485-BL can send out pre-set max 15 strings via **AT+COMMAD1**, **ATCOMMAND2**,…, to **AT+COMMANDF** . All commands are of same grammar.
358 -)))
359 359  
360 -(((
356 +
361 361  **Handle return from sensors to RS485-BL**:
362 -)))
363 363  
364 -(((
365 365  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**
366 -)))
367 367  
368 -* (((
369 -**AT+DATACUT**
370 -)))
371 371  
372 -(((
362 +* **AT+DATACUT**
363 +
373 373  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.
374 -)))
375 375  
376 -* (((
377 -**AT+SEARCH**
378 -)))
379 379  
380 -(((
367 +* **AT+SEARCH**
368 +
381 381  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.
382 -)))
383 383  
384 -(((
371 +
385 385  **Define wait timeout:**
386 -)))
387 387  
388 -(((
389 389  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
390 -)))
391 391  
392 -(((
376 +
393 393  After we got the valid value from each RS485 commands, we need to combine them together with the command **AT+DATAUP**.
394 -)))
395 395  
379 +
396 396  **Examples:**
397 397  
398 398  Below are examples for the how above AT Commands works.
399 399  
384 +
400 400  **AT+COMMANDx : **This command will be sent to RS485/TTL devices during each sampling, Max command length is 14 bytes. The grammar is:
401 401  
402 -(% border="1" class="table-bordered" style="background-color:#4f81bd; color:white; width:501px" %)
403 -|(% style="width:498px" %)(((
387 +|(((
404 404  **AT+COMMANDx=xx xx xx xx xx xx xx xx xx xx xx xx,m**
405 405  
406 406  **xx xx xx xx xx xx xx xx xx xx xx xx: The RS485 command to be sent**
... ... @@ -412,38 +412,41 @@
412 412  
413 413  In the RS485-BL, we should use this command AT+COMMAND1=01 03 0B B8 00 02,1 for the same.
414 414  
399 +
415 415  **AT+SEARCHx**: This command defines how to handle the return from AT+COMMANDx.
416 416  
417 -(% border="1" class="table-bordered" style="background-color:#4f81bd; color:white; width:580px" %)
418 -|(% style="width:577px" %)(((
402 +|(((
419 419  **AT+SEARCHx=aa,xx xx xx xx xx**
420 420  
421 421  * **aa: 1: prefix match mode; 2: prefix and suffix match mode**
422 422  * **xx xx xx xx xx: match string. Max 5 bytes for prefix and 5 bytes for suffix**
407 +
408 +
423 423  )))
424 424  
425 -**Examples:**
411 +Examples:
426 426  
427 427  1. For a return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
428 428  
429 429  If we set AT+SEARCH1=1,1E 56 34.      (max 5 bytes for prefix)
430 430  
431 -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 +The valid data will be all bytes after 1E 56 34 , so it is 2e 30 58 5f 36 41 30 31 00 49
432 432  
433 -[[image:1653271044481-711.png]]
419 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image013.png]]
434 434  
421 +
435 435  1. For a return string from AT+COMMAND1:  16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
436 436  
437 437  If we set AT+SEARCH1=2, 1E 56 34+31 00 49
438 438  
439 -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**
426 +Device will search the bytes between 1E 56 34 and 31 00 49. So it is 2e 30 58 5f 36 41 30
440 440  
441 -[[image:1653271276735-972.png]]
428 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image014.png]]
442 442  
430 +
443 443  **AT+DATACUTx : **This command defines how to handle the return from AT+COMMANDx, max return length is 45 bytes.
444 444  
445 -(% style="background-color:#4f81bd; color:white; width:729px" %)
446 -|(% style="width:726px" %)(((
433 +|(((
447 447  **AT+DATACUTx=a,b,c**
448 448  
449 449  * **a: length for the return of AT+COMMAND**
... ... @@ -455,130 +455,95 @@
455 455  
456 456  * Grab bytes:
457 457  
458 -[[image:1653271581490-837.png||height="313" width="722"]]
445 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image015.png]]
459 459  
460 460  * Grab a section.
461 461  
462 -[[image:1653271648378-342.png||height="326" width="720"]]
449 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image016.png]]
463 463  
464 464  * Grab different sections.
465 465  
466 -[[image:1653271657255-576.png||height="305" width="730"]]
453 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image017.png]]
467 467  
468 -(((
469 -(% style="color:red" %)**Note:**
470 -)))
471 471  
472 -(((
456 +Note:
457 +
473 473  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.
474 -)))
475 475  
476 -(((
477 -**Example:**
478 -)))
460 +Example:
479 479  
480 -(((
481 -(% style="color:red" %)AT+COMMAND1=11 01 1E D0,0
482 -)))
462 +AT+COMMAND1=11 01 1E D0,0
483 483  
484 -(((
485 -(% style="color:red" %)AT+SEARCH1=1,1E 56 34
486 -)))
464 +AT+SEARCH1=1,1E 56 34
487 487  
488 -(((
489 -(% style="color:red" %)AT+DATACUT1=0,2,1~~5
490 -)))
466 +AT+DATACUT1=0,2,1~~5
491 491  
492 -(((
493 -(% style="color:red" %)Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
494 -)))
468 +Return string from AT+COMMAND1: 16 0c 1e 56 34 2e 30 58 5f 36 41 30 31 00 49
495 495  
496 -(((
497 -(% style="color:red" %)String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49
498 -)))
470 +String after SEARCH command: 2e 30 58 5f 36 41 30 31 00 49
499 499  
500 -(((
501 -(% style="color:red" %)Valid payload after DataCUT command: 2e 30 58 5f 36
502 -)))
472 +Valid payload after DataCUT command: 2e 30 58 5f 36
503 503  
504 -[[image:1653271763403-806.png]]
474 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image018.png]]
505 505  
506 -=== 3.3.4 Compose the uplink payload ===
507 507  
508 -(((
477 +
478 +
479 +1.
480 +11.
481 +111. Compose the uplink payload
482 +
509 509  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.**
510 -)))
511 511  
512 -(((
513 -(% style="color:#4f81bd" %)**Examples: AT+DATAUP=0**
514 -)))
515 515  
516 -(((
517 -Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**A SIGNLE UPLINK**.
518 -)))
486 +**Examples: AT+DATAUP=0**
519 519  
520 -(((
488 +Compose the uplink payload with value returns in sequence and send with **A SIGNLE UPLINK**.
489 +
521 521  Final Payload is
522 -)))
523 523  
524 -(((
525 -(% style="color:#4f81bd" %)Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx
526 -)))
492 +Battery Info+PAYVER + VALID Value from RETURN1 + Valid Value from RETURN2 + … + RETURNx
527 527  
528 -(((
529 529  Where PAYVER is defined by AT+PAYVER, below is an example screen shot.
530 -)))
531 531  
532 -[[image:1653272787040-634.png||height="515" width="719"]]
496 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image019.png]]
533 533  
534 -(((
535 -(% style="color:#4f81bd" %)**Examples: AT+DATAUP=1**
536 -)))
537 537  
538 -(((
539 -Compose the uplink payload with value returns in sequence and send with (% style="color:red" %)**Multiply UPLINKs**.
540 -)))
541 541  
542 -(((
500 +**Examples: AT+DATAUP=1**
501 +
502 +Compose the uplink payload with value returns in sequence and send with **Multiply UPLINKs**.
503 +
543 543  Final Payload is
544 -)))
545 545  
546 -(((
547 -(% style="color:#4f81bd" %)Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA
548 -)))
506 +Battery Info+PAYVER + PAYLOAD COUNT + PAYLOAD# + DATA
549 549  
550 -1. (((
551 -Battery Info (2 bytes): Battery voltage
552 -)))
553 -1. (((
554 -PAYVER (1 byte): Defined by AT+PAYVER
555 -)))
556 -1. (((
557 -PAYLOAD COUNT (1 byte): Total how many uplinks of this sampling.
558 -)))
559 -1. (((
560 -PAYLOAD# (1 byte): Number of this uplink. (from 0,1,2,3…,to PAYLOAD COUNT)
561 -)))
562 -1. (((
563 -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
564 -)))
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*!>>path:#max_byte]]) for each uplink so each uplink <= 11 bytes. For the last uplink, DATA will might less than 6 bytes
565 565  
566 -[[image:1653272817147-600.png||height="437" width="717"]]
514 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image020.png]]
567 567  
516 +
568 568  So totally there will be 3 uplinks for this sampling, each uplink includes 6 bytes DATA
569 569  
570 -DATA1=RETURN1 Valid Value = (% style="background-color:#4f81bd; color:white" %) 20 20 0a 33 90 41
519 +DATA1=RETURN1 Valid Value = 20 20 0a 33 90 41
571 571  
572 -DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10= (% style="background-color:#4f81bd; color:white" %)02 aa 05 81 0a 20
521 +DATA2=1^^st^^ ~~ 6^^th^^ byte of Valid value of RETURN10= 02 aa 05 81 0a 20
573 573  
574 -DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 =(% style="background-color:#4f81bd; color:white" %) 20 20 20 2d 30
523 +DATA3=7^^th^^ ~~ 11^^th^^ bytes of Valid value of RETURN10 = 20 20 20 2d 30
575 575  
525 +
526 +
576 576  Below are the uplink payloads:
577 577  
578 -[[image:1653272901032-107.png]]
529 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image021.png]]
579 579  
580 -(% style="color:red" %)Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:
581 581  
532 +Notice: the Max bytes is according to the max support bytes in different Frequency Bands for lowest SF. As below:
533 +
582 582   ~* For AU915/AS923 bands, if UplinkDwell time=0, max 51 bytes for each uplink ( so 51 -5 = 46 max valid date)
583 583  
584 584   * For AU915/AS923 bands, if UplinkDwell time=1, max 11 bytes for each uplink ( so 11 -5 = 6 max valid date).
... ... @@ -587,121 +587,90 @@
587 587  
588 588   ~* For all other bands: max 51 bytes for each uplink  ( so 51 -5 = 46 max valid date).
589 589  
590 -=== 3.3.5 Uplink on demand ===
591 591  
592 -(((
543 +
544 +1.
545 +11.
546 +111. Uplink on demand
547 +
593 593  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.
594 -)))
595 595  
596 -(((
597 597  Downlink control command:
598 -)))
599 599  
600 -(((
601 -**0x08 command**: Poll an uplink with current command set in RS485-BL.
602 -)))
552 +[[0x08 command>>path:#downlink_08]]: Poll an uplink with current command set in RS485-BL.
603 603  
604 -(((
605 -**0xA8 command**: Send a command to RS485-BL and uplink the output from sensors.
606 -)))
554 +[[0xA8 command>>path:#downlink_A8]]: Send a command to RS485-BL and uplink the output from sensors.
607 607  
608 -=== 3.3.6 Uplink on Interrupt ===
609 609  
610 -Put the interrupt sensor between 3.3v_out and GPIO ext.
611 611  
612 -[[image:1653273818896-432.png]]
558 +1.
559 +11.
560 +111. Uplink on Interrupt
613 613  
614 -(((
562 +Put the interrupt sensor between 3.3v_out and GPIO ext.[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image022.png]]
563 +
615 615  AT+INTMOD=0  Disable Interrupt
616 -)))
617 617  
618 -(((
619 619  AT+INTMOD=1  Interrupt trigger by rising or falling edge.
620 -)))
621 621  
622 -(((
623 623  AT+INTMOD=2  Interrupt trigger by falling edge. ( Default Value)
624 -)))
625 625  
626 -(((
627 627  AT+INTMOD=3  Interrupt trigger by rising edge.
628 -)))
629 629  
630 -== 3.4 Uplink Payload ==
631 631  
632 -(% border="1" style="background-color:#4f81bd; color:white; width:850px" %)
633 -|**Size(bytes)**|(% style="width:130px" %)**2**|(% style="width:93px" %)**1**|(% style="width:509px" %)**Length depends on the return from the commands**
634 -|Value|(% style="width:130px" %)(((
635 -(((
573 +1.
574 +11. Uplink Payload
575 +
576 +|**Size(bytes)**|**2**|**1**|**Length depends on the return from the commands**
577 +|Value|(((
636 636  Battery(mV)
637 -)))
638 638  
639 -(((
640 640  &
641 -)))
642 642  
643 -(((
644 644  Interrupt _Flag
645 -)))
646 -)))|(% style="width:93px" %)(((
583 +)))|(((
647 647  PAYLOAD_VER
648 648  
649 649  
650 -)))|(% style="width:509px" %)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.
587 +)))|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.
651 651  
652 652  Below is the decoder for the first 3 bytes. The rest bytes are dynamic depends on different RS485 sensors.
653 653  
654 -(((
591 +
655 655  function Decoder(bytes, port) {
656 -)))
657 657  
658 -(((
659 659  ~/~/Payload Formats of RS485-BL Deceive
660 -)))
661 661  
662 -(((
663 663  return {
664 -)))
665 665  
666 -(((
667 667   ~/~/Battery,units:V
668 -)))
669 669  
670 -(((
671 671   BatV:((bytes[0]<<8 | bytes[1])&0x7fff)/1000,
672 -)))
673 673  
674 -(((
675 675   ~/~/GPIO_EXTI 
676 -)))
677 677  
678 -(((
679 679   EXTI_Trigger:(bytes[0] & 0x80)? "TRUE":"FALSE",
680 -)))
681 681  
682 -(((
683 683   ~/~/payload of version
684 -)))
685 685  
686 -(((
687 687   Pay_ver:bytes[2],
688 -)))
689 689  
690 -(((
691 691   };
692 -)))
693 693  
694 -(((
695 695   }
696 -)))
697 697  
698 -(((
614 +
615 +
616 +
617 +
618 +
619 +
699 699  TTN V3 uplink screen shot.
700 -)))
701 701  
702 -[[image:1653274001211-372.png||height="192" width="732"]]
622 +[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.png]]
703 703  
704 -== 3.5 Configure RS485-BL via AT or Downlink ==
624 +1.
625 +11. Configure RS485-BL via AT or Downlink
705 705  
706 706  User can configure RS485-BL via [[AT Commands >>path:#_​Using_the_AT]]or LoRaWAN Downlink Commands
707 707  
1652954654347-831.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -138.7 KB
Content
1653271044481-711.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -27.8 KB
Content
1653271276735-972.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -26.6 KB
Content
1653271581490-837.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -138.7 KB
Content
1653271648378-342.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -131.4 KB
Content
1653271657255-576.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -142.6 KB
Content
1653271763403-806.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -27.7 KB
Content
1653272787040-634.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -294.0 KB
Content
1653272817147-600.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -143.3 KB
Content
1653272901032-107.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -197.8 KB
Content
1653273818896-432.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -31.6 KB
Content
1653274001211-372.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -91.4 KB
Content