Changes for page N95S31B -- NB-IoT Temperature & Humidity Sensor User Manual
Last modified by Mengting Qiu on 2024/04/02 16:44
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 3 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Edwin1 +XWiki.Xiaoling - Content
-
... ... @@ -17,7 +17,6 @@ 17 17 18 18 = 1. Introduction = 19 19 20 - 21 21 == 1.1 What is N95S31B NB-IoT Sensor Node == 22 22 23 23 ((( ... ... @@ -56,7 +56,6 @@ 56 56 57 57 == 1.2 Features == 58 58 59 - 60 60 * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD 61 61 * Monitor Temperature & Humidity via SHT31 62 62 * AT Commands to change parameters ... ... @@ -68,6 +68,9 @@ 68 68 * Micro SIM card slot for NB-IoT SIM 69 69 * 8500mAh Battery for long term use 70 70 69 + 70 + 71 + 71 71 == 1.3 Specification == 72 72 73 73 ... ... @@ -76,6 +76,7 @@ 76 76 * Supply Voltage: 2.1v ~~ 3.6v 77 77 * Operating Temperature: -40 ~~ 85°C 78 78 80 + 79 79 (% style="color:#037691" %)**NB-IoT Spec:** 80 80 81 81 * - B1 @H-FDD: 2100MHz ... ... @@ -85,6 +85,7 @@ 85 85 * - B20 @H-FDD: 800MHz 86 86 * - B28 @H-FDD: 700MHz 87 87 90 + 88 88 (% style="color:#037691" %)**Battery:** 89 89 90 90 * Li/SOCI2 un-chargeable battery ... ... @@ -93,9 +93,11 @@ 93 93 * Max continuously current: 130mA 94 94 * Max boost current: 2A, 1 second 95 95 96 -== 1.4 Applications == 97 97 98 98 101 + 102 +== 1.4 Applications == 103 + 99 99 * Smart Buildings & Home Automation 100 100 * Logistics and Supply Chain Management 101 101 * Smart Metering ... ... @@ -107,20 +107,15 @@ 107 107 108 108 109 109 115 +== 1.5 Pin Definitions == 110 110 111 -== 1.5 Pin Definitions & Switch == 112 - 113 - 114 114 N95S31B use the mother board from NBSN95 which as below. 115 115 116 - 117 117 [[image:image-20220709144723-1.png]] 118 118 119 119 120 - 121 121 === 1.5.1 Jumper JP2 === 122 122 123 - 124 124 Power on Device when put this jumper. 125 125 126 126 ... ... @@ -127,7 +127,6 @@ 127 127 128 128 === 1.5.2 BOOT MODE / SW1 === 129 129 130 - 131 131 ((( 132 132 1) ISP: upgrade mode, device won't have any signal in this mode. but ready for upgrade firmware. LED won't work. Firmware won't run. 133 133 ))) ... ... @@ -140,7 +140,6 @@ 140 140 141 141 === 1.5.3 Reset Button === 142 142 143 - 144 144 Press to reboot the device. 145 145 146 146 ... ... @@ -147,15 +147,16 @@ 147 147 148 148 === 1.5.4 LED === 149 149 150 - 151 151 It will flash: 152 152 153 153 1. When boot the device in flash mode 154 154 1. Send an uplink packet 155 155 156 -= 2. Use N95S31B to communicate with IoT Server = 157 157 158 158 155 + 156 += 2. Use N95S31B to communicate with IoT Server = 157 + 159 159 == 2.1 How it works == 160 160 161 161 ... ... @@ -172,7 +172,7 @@ 172 172 173 173 ))) 174 174 175 -[[image:16575 20100595-569.png]]174 +[[image:1657350248151-650.png]] 176 176 177 177 ((( 178 178 ... ... @@ -188,7 +188,6 @@ 188 188 [[image:image-20220709150546-2.png]] 189 189 190 190 191 - 192 192 === 2.2.1 Test Requirement === 193 193 194 194 ... ... @@ -241,7 +241,6 @@ 241 241 242 242 === 2.2.3 Insert SIM card === 243 243 244 - 245 245 ((( 246 246 Insert the NB-IoT Card get from your provider. 247 247 ))) ... ... @@ -257,18 +257,14 @@ 257 257 258 258 === 2.2.4 Connect USB – TTL to N95S31B to configure it === 259 259 260 - 261 261 ((( 262 262 ((( 263 263 User need to configure N95S31B via serial port to set the (% style="color:blue" %)**Server Address** / **Uplink Topic** (%%)to define where and how-to uplink packets. N95S31B support AT Commands, user can use a USB to TTL adapter to connect to N95S31B and use AT Commands to configure it, as below. 264 - 265 - 266 266 ))) 267 267 ))) 268 268 269 269 [[image:1657351312545-300.png]] 270 270 271 - 272 272 **Connection:** 273 273 274 274 (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND ... ... @@ -292,9 +292,8 @@ 292 292 293 293 [[image:1657329814315-101.png]] 294 294 295 - 296 296 ((( 297 -(% style="color:red" %) **Note: the valid AT Commands can be found at:**(%%)**[[https:~~/~~/www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i~~-~~-AyZcQkoua?dl=0>>https://www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i--AyZcQkoua?dl=0]]**289 +(% style="color:red" %)Note: the valid AT Commands can be found at: (%%)[[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/]] 298 298 ))) 299 299 300 300 ... ... @@ -301,10 +301,9 @@ 301 301 302 302 === 2.2.5 Use CoAP protocol to uplink data === 303 303 296 +(% style="color:red" %)Note: if you don't have CoAP server, you can refer this link to set up one: (%%)[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/>>http://wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/]] 304 304 305 -(% style="color:red" %)**Note: if you don't have CoAP server, you can refer this link to set up one: **(%%)**[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/>>http://wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/]]** 306 306 307 - 308 308 ((( 309 309 **Use below commands:** 310 310 ))) ... ... @@ -352,7 +352,6 @@ 352 352 353 353 === 2.2.7 Use MQTT protocol to uplink data === 354 354 355 - 356 356 N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption. 357 357 358 358 * (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink ... ... @@ -368,7 +368,6 @@ 368 368 369 369 [[image:1657352645687-385.png]] 370 370 371 - 372 372 ((( 373 373 To save battery life, N95S31B will establish a subscription before each uplink and close the subscription 3 seconds after uplink successful. Any downlink commands from server will only arrive during the subscription period. 374 374 ))) ... ... @@ -382,7 +382,6 @@ 382 382 383 383 === 2.2.8 Use TCP protocol to uplink data === 384 384 385 - 386 386 This feature is supported since firmware version v110 387 387 388 388 * (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink ... ... @@ -397,7 +397,6 @@ 397 397 398 398 === 2.2.9 Change Update Interval === 399 399 400 - 401 401 User can use below command to change the (% style="color:green" %)**uplink interval**. 402 402 403 403 * (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s ... ... @@ -406,16 +406,13 @@ 406 406 407 407 ))) 408 408 409 -(% style="color:red" %)**NOTE: Since firmware version is v1.2:** 410 410 411 -**By default, the device will send an uplink message every 2 hours. Each Uplink Include 8 set of records in this 2 hour (15 minute interval / record).** 412 412 413 - 414 414 == 2.3 Uplink Payload == 415 415 416 416 417 417 ((( 418 -N95 S31Bhas different working modesfor the connections of different typesof sensors. This section describes these modes. User can use the AT Command (% style="color:blue" %)**AT+MOD**(%%) to set NBSN95 to different working modes.402 +NBSN95 has different working mode for the connections of different type of sensors. This section describes these modes. User can use the AT Command (% style="color:blue" %)**AT+MOD**(%%) to set NBSN95 to different working modes. 419 419 ))) 420 420 421 421 ... ... @@ -424,7 +424,7 @@ 424 424 ))) 425 425 426 426 ((( 427 - (% style="color:blue" %)**AT+CFGMOD=2 ** (%%)~/~/will set the S31Bto work in MOD=2 distance mode which target to measure distance via Ultrasonic Sensor.411 + (% style="color:blue" %)**AT+CFGMOD=2 ** (%%)~/~/will set the NBSN95 to work in MOD=2 distance mode which target to measure distance via Ultrasonic Sensor. 428 428 ))) 429 429 430 430 ... ... @@ -447,21 +447,17 @@ 447 447 448 448 (% style="color:red" %) 449 449 1. ((( 450 - **All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].**434 +All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]]. 451 451 ))) 452 452 1. ((( 453 -**By default, the device will send an uplink message every 1 hour.** 437 +By default, the device will send an uplink message every 1 hour. 438 +))) 454 454 455 455 456 456 457 - 458 -))) 459 459 460 460 === 2.3.1 Payload Analyze === 461 461 462 - 463 -==== 2.3.1.1 Before Firmware v1.2 ==== 464 - 465 465 N95S31B uplink payload includes in total 21 bytes 466 466 467 467 ... ... @@ -496,8 +496,6 @@ 496 496 ))) 497 497 498 498 ((( 499 - 500 - 501 501 ((( 502 502 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data. 503 503 ))) ... ... @@ -523,40 +523,13 @@ 523 523 524 524 ))) 525 525 526 -==== 2.3.1.2 Since Firmware v1.2 ==== 504 +((( 505 + 506 +))) 527 527 528 -In this mode, uplink payload includes 91 bytes in total by default. 529 529 530 -Each time the device uploads a data package, 8 sets of recorded data will be attached. Up to 32 sets of recorded data can be uploaded. 531 - 532 -|**Size(bytes)**|**8**|2|2|1|1|2|1|2|2|2|4|2|2|4 533 -|**Value**|Device ID|Ver|BAT|Signal Strength|MOD|TemDS18B20|Interrupt|ADC|SHTTEM|SHTHUM|Time stamp |SHTTEM|SHTHUM|Time stamp ..... 534 - 535 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the N95S31B uplink data. 536 - 537 -[[image:image-20220908154949-1.png]] 538 - 539 -The payload is ASCII string, representative same HEX: 540 - 541 -0x(% style="color:red" %)f868411056758782(% style="color:blue" %)000c(% style="color:green" %)0d0f(% style="color:red" %)0c(% style="color:blue" %)01(% style="color:green" %)0000(% style="color:red" %)00**//0030//**(% style="color:blue" %)**//0114//**(% style="color:red" %)**//0231//**(% style="color:green" %)**//63199d3c//**0113023163199d12//**0113023163199c5e**//0112023763199baa//**0112023263199af6**//0111023b631999a7//**0112023b631998f3**//011202426319983f//**01110242631996eb**//(%%) where: 542 - 543 -* (% style="color:red" %) Device ID: f868411056758782 = f868411056758782 544 -* (% style="color:blue" %) Version: 0x000c=120=1.2 545 -* (% style="color:green" %) BAT: 0x0d0f = 3343 mV = 3.343V 546 -* (% style="color:red" %) Singal: 0x0c = 12 547 -* (% style="color:blue" %) Mod: 0x01 = 1 548 -* TemDS18B20: 0x0000= 0 = 0 549 -* (% style="color:green" %)Interrupt: 0x00= 0 550 -* (% style="color:green" %)adc: 0x0030= 48 551 -* SHTTEM: 0x0114= 276 = 27.6 552 -* SHTHUM:0x0231 =561=56.1% 553 -* (% style="color:red" %) Time stamp : 0x6315537b =1662342011 ([[Unix Epoch Time>>url:http://www.epochconverter.com/]]) 554 -* (% style="color:red" %)SHTTEM,SHTHUM,Time stamp : 0113023163199d12 555 -* 8 sets of recorded data: SHTTEM,SHTHUM,Time stamp : //**0113023163199c5e**//,....... 556 - 557 557 === 2.3.2 Device ID === 558 558 559 - 560 560 ((( 561 561 By default, the Device ID equal to the last 6 bytes of IMEI. 562 562 ))) ... ... @@ -575,44 +575,21 @@ 575 575 576 576 ((( 577 577 The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID. 578 - 579 - 580 580 ))) 581 581 582 -(% style="color:red" %)**NOTE:When the firmware version is v1.2 and later firmware:** 583 583 584 584 585 -By default, the Device ID equal to the last 15 bits of IMEI. 586 - 587 -User can use **AT+DEUI** to set Device ID 588 - 589 -**Example:** 590 - 591 -AT+DEUI=868411056754138 592 - 593 - 594 594 === 2.3.3 Version Info === 595 595 596 596 597 -((( 598 598 These bytes include the hardware and software version. 599 -))) 600 600 601 -((( 602 602 Higher byte: Specify hardware version: always 0x00 for N95S31B 603 -))) 604 604 605 -((( 606 606 Lower byte: Specify the software version: 0x6E=110, means firmware version 110 607 -))) 608 608 609 -((( 610 - 611 -))) 612 612 613 -((( 614 614 For example: 0x00 6E: this device is N95S31B with firmware version 110. 615 -))) 616 616 617 617 ((( 618 618 ... ... @@ -621,7 +621,6 @@ 621 621 622 622 === 2.3.4 Battery Info === 623 623 624 - 625 625 ((( 626 626 Ex1: 0x0B45 = 2885mV 627 627 ))) ... ... @@ -634,7 +634,6 @@ 634 634 635 635 === 2.3.5 Signal Strength === 636 636 637 - 638 638 ((( 639 639 NB-IoT Network signal Strength. 640 640 ))) ... ... @@ -667,7 +667,6 @@ 667 667 668 668 === 2.3.6 Temperature & Humidity === 669 669 670 - 671 671 The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server. 672 672 673 673 [[image:image-20220709161741-3.png]] ... ... @@ -686,9 +686,8 @@ 686 686 687 687 == 2.4 Downlink Payload == 688 688 614 +By default, NDDS75 prints the downlink payload to console port. 689 689 690 -By default, N95S31B prints the downlink payload to console port. 691 - 692 692 [[image:image-20220709100028-1.png]] 693 693 694 694 ... ... @@ -725,7 +725,7 @@ 725 725 ))) 726 726 727 727 ((( 728 -If payload = 0x04FF, it will reset the 95S31B652 +If payload = 0x04FF, it will reset the NDDS75 729 729 ))) 730 730 731 731 ... ... @@ -736,59 +736,12 @@ 736 736 ))) 737 737 738 738 739 -== 2.5 Humidity and Temperature alarm function == 740 740 741 - ➢ATCommand:664 +== 2.5 Battery Analysis == 742 742 743 - AT+SHHUM=min,max666 +=== 2.5.1 Battery Type === 744 744 745 -² When min=0, and max≠0, Alarm higher than max 746 746 747 -² When min≠0, and max=0, Alarm lower than min 748 - 749 -² When min≠0 and max≠0, Alarm higher than max or lower than min 750 - 751 -Example: 752 - 753 -AT+ SHHUM=50,80 ~/~/ Alarm when humidity lower than 50. 754 - 755 - 756 -AT+ SHTEMP=min,max 757 - 758 -² When min=0, and max≠0, Alarm higher than max 759 - 760 -² When min≠0, and max=0, Alarm lower than min 761 - 762 -² When min≠0 and max≠0, Alarm higher than max or lower than min 763 - 764 -Example: 765 - 766 -AT+ SHTEMP=20,30 ~/~/ Alarm when temperature lower than 20. 767 - 768 -== 2.6 Set the number of data to be uploaded and the recording time == 769 - 770 -➢ AT Command: 771 - 772 -AT+TR=900 ~/~/The unit is seconds, and the default is to record data once every 900 seconds.( The minimum can be set to 180 seconds) 773 - 774 -AT+NOUD=8 ~/~/The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded. 775 - 776 -== 2.7 Read or Clear cached data == 777 - 778 -➢ AT Command: 779 - 780 -AT+CDP ~/~/ Read cached data 781 - 782 -[[image:image-20220908163102-2.png]] 783 - 784 -AT+CDP=0 ~/~/ Clear cached data 785 - 786 -== 2.8 Battery Analysis == 787 - 788 - 789 -=== 2.8.1 Battery Type === 790 - 791 - 792 792 ((( 793 793 The N95S31B battery is a combination of an 8500mAh Li/SOCI2 Battery and a Super Capacitor. The battery is none-rechargeable battery type with a low discharge rate (<2% per year). This type of battery is commonly used in IoT devices such as water meter. 794 794 ))) ... ... @@ -811,11 +811,10 @@ 811 811 812 812 813 813 814 -=== 2. 8.2 Power consumption Analyze ===691 +=== 2.5.2 Power consumption Analyze === 815 815 816 - 817 817 ((( 818 -The file **DRAGINO_N95S31B-Power-Analyzer.pdf** from [[https:~~/~~/www.dro pbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i~~-~~-AyZcQkoua?dl=0>>https://www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i--AyZcQkoua?dl=0]]694 +The file **DRAGINO_N95S31B-Power-Analyzer.pdf** from [[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/]] describes a detail measurement to analyze the power consumption in different case. User can use it for design guideline for their project. 819 819 ))) 820 820 821 821 ((( ... ... @@ -823,9 +823,8 @@ 823 823 ))) 824 824 825 825 826 -=== 2. 8.3 Battery Note ===702 +=== 2.5.3 Battery Note === 827 827 828 - 829 829 ((( 830 830 The Li-SICO battery is designed for small current / long period application. It is not good to use a high current, short period transmit method. The recommended minimum period for use of this battery is 5 minutes. If you use a shorter period time to uplink data, then the battery life may be decreased. 831 831 ))) ... ... @@ -832,7 +832,7 @@ 832 832 833 833 834 834 835 -=== 2. 8.4 Replace the battery ===710 +=== 2.5.4 Replace the battery === 836 836 837 837 838 838 ((( ... ... @@ -848,7 +848,6 @@ 848 848 849 849 = 3. Access NB-IoT Module = 850 850 851 - 852 852 ((( 853 853 Users can directly access the AT command set of the NB-IoT module. 854 854 ))) ... ... @@ -855,8 +855,6 @@ 855 855 856 856 ((( 857 857 The AT Command set can refer the BC35-G NB-IoT Module AT Command: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=datasheet/other_vendors/BC35-G/>>url:https://www.dragino.com/downloads/index.php?dir=datasheet/other_vendors/BC35-G/]] 858 - 859 - 860 860 ))) 861 861 862 862 [[image:1657333200519-600.png]] ... ... @@ -865,13 +865,11 @@ 865 865 866 866 = 4. Using the AT Commands = 867 867 868 - 869 869 == 4.1 Access AT Commands == 870 870 742 +See NBSN95 AT Command in this link for detail: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN95/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN95/]] 871 871 872 -See NBSN95 AT Command in this link for detail: [[https:~~/~~/www.dropbox.com/sh/jao1xt9kw5r3yq4/AAAMpJkZzExF2JLbRWxGoQ9Na?dl=0>>https://www.dropbox.com/sh/jao1xt9kw5r3yq4/AAAMpJkZzExF2JLbRWxGoQ9Na?dl=0]] 873 873 874 - 875 875 AT+<CMD>? : Help on <CMD> 876 876 877 877 AT+<CMD> : Run <CMD> ... ... @@ -911,24 +911,7 @@ 911 911 912 912 AT+SERVADDR : Server Address 913 913 914 -AT+TR : Get or Set record time 915 915 916 -AT+APN : Get or set the APN 917 - 918 -AT+FBAND : Get or Set whether to automatically modify the frequency band 919 - 920 -AT+DNSCFG : Get or Set DNS Server 921 - 922 -AT+GETSENSORVALUE : Returns the current sensor measurement 923 - 924 -AT+NOUD : Get or Set the number of data to be uploaded 925 - 926 -AT+CDP : Read or Clear cached data 927 - 928 -AT+SHTEMP: Get or Set alarm of temp 929 - 930 -AT+SHHUM: Get or Set alarm of moisture 931 - 932 932 (% style="color:#037691" %)**COAP Management** 933 933 934 934 AT+URI : Resource parameters ... ... @@ -962,7 +962,6 @@ 962 962 963 963 = 5. FAQ = 964 964 965 - 966 966 == 5.1 How to Upgrade Firmware == 967 967 968 968 ... ... @@ -978,7 +978,7 @@ 978 978 979 979 980 980 ((( 981 -(% style="color:red" %) **Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.**833 +(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update. 982 982 ))) 983 983 ))) 984 984 ... ... @@ -986,7 +986,6 @@ 986 986 987 987 = 6. Trouble Shooting = 988 988 989 - 990 990 == 6.1 Connection problem when uploading firmware == 991 991 992 992 ... ... @@ -1002,7 +1002,6 @@ 1002 1002 1003 1003 == 6.2 AT Command input doesn't work == 1004 1004 1005 - 1006 1006 ((( 1007 1007 In the case if user can see the console output but can't type input to the device. Please check if you already include the (% style="color:green" %)**ENTER**(%%) while sending out the command. Some serial tool doesn't send (% style="color:green" %)**ENTER**(%%) while press the send key, user need to add ENTER in their string. 1008 1008 ... ... @@ -1052,6 +1052,5 @@ 1052 1052 1053 1053 = 9. Support = 1054 1054 1055 - 1056 1056 * 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. 1057 1057 * 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:http://../../../../../../D:%5C%E5%B8%82%E5%9C%BA%E8%B5%84%E6%96%99%5C%E8%AF%B4%E6%98%8E%E4%B9%A6%5CLoRa%5CLT%E7%B3%BB%E5%88%97%5Csupport@dragino.com]]
- 1657520100595-569.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -126.1 KB - Content
- image-20220908154949-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.David - Size
-
... ... @@ -1,1 +1,0 @@ 1 -58.5 KB - Content
- image-20220908163102-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.David - Size
-
... ... @@ -1,1 +1,0 @@ 1 -29.7 KB - Content