Changes for page NLMS01-NB-IoT Leaf Moisture Sensor User Manual
Last modified by Mengting Qiu on 2024/04/02 16:54
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 2 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Xiaoling1 +XWiki.David - Content
-
... ... @@ -1,44 +1,31 @@ 1 -(% style="text-align:center" %) 2 -[[image:image-20220907171221-1.jpeg]] 1 +[[image:image-20220907171221-1.jpeg]] 3 3 4 - 5 5 6 -{{toc/}} 7 7 5 +**~1. Introduction** 8 8 7 +**1.1 What is NLMS01 **Leaf Moisture Sensor 9 9 10 - =1.Introduction=9 +The Dragino NLMS01 is a **NB-IOT Leaf Moisture Sensor** for IoT of Agriculture. It is designed to measure the leaf moisture and temperature, so to send to the platform to analyze the leaf status such as : watering, moisturizing, dew, frozen. The probe is IP67 waterproof. 11 11 12 - ==1.1What isNLMS01 LeafMoistureSensor==11 +NLMS01 detects leaf's** moisture and temperature **use FDR method, it senses the dielectric constant cause by liquid over the leaf surface, and cover the value to leaf moisture. The probe is design in a leaf shape to best simulate the real leaf characterizes. The probe has as density as 15 leaf vein lines per centimeter which make it can senses small drop and more accuracy. 13 13 14 - 15 -((( 16 -The Dragino NLMS01 is a (% style="color:blue" %)**NB-IOT Leaf Moisture Sensor**(%%) for IoT of Agriculture. It is designed to measure the leaf moisture and temperature, so to send to the platform to analyze the leaf status such as : watering, moisturizing, dew, frozen. The probe is IP67 waterproof. 17 - 18 -NLMS01 detects leaf's(% style="color:blue" %)** moisture and temperature use FDR method**(%%), it senses the dielectric constant cause by liquid over the leaf surface, and cover the value to leaf moisture. The probe is design in a leaf shape to best simulate the real leaf characterizes. The probe has as density as 15 leaf vein lines per centimeter which make it can senses small drop and more accuracy. 19 - 20 20 NarrowBand-Internet of Things (NB-IoT) is a standards-based low power wide area (LPWA) technology developed to enable a wide range of new IoT devices and services. NB-IoT significantly improves the power consumption of user devices, system capacity and spectrum efficiency, especially in deep coverage. 14 +\\NLMS01 supports different uplink methods include **TCP,MQTT,UDP and CoAP **for different application requirement. 15 +\\NLMS01 is powered by **8500mAh Li-SOCI2 battery**, It is designed for long term use up to 5 years. (Actually Battery life depends on the use environment, update period & uplink method) 16 +\\To use NLMS01, user needs to check if there is NB-IoT coverage in local area and with the bands NLMS01 supports. If the local operate support it, user needs to get a **NB-IoT SIM card** from local operator and install NLMS01 to get NB-IoT network connection 21 21 22 -NLMS01 supports different uplink methods include (% style="color:blue" %)**TCP,MQTT,UDP and CoAP **(%%)for different application requirement. 23 - 24 -NLMS01 is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), It is designed for long term use up to 5 years. (Actually Battery life depends on the use environment, update period & uplink method). 25 - 26 -To use NLMS01, user needs to check if there is NB-IoT coverage in local area and with the bands NLMS01 supports. If the local operate support it, user needs to get a (% style="color:blue" %)**NB-IoT SIM card**(%%) from local operator and install NLMS01 to get NB-IoT network connection. 27 -))) 28 - 29 - 30 30 [[image:image-20220907171221-2.png]] 31 31 32 - 33 33 [[image:image-20220907171221-3.png]] 34 34 22 +**1.2 Features** 35 35 36 -== 1.2 Features == 37 - 38 - 39 39 * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD 40 40 * Monitor Leaf moisture 41 -* Monitor Leaf temperature 26 + 27 +* Monitor Leaf temperature 28 + 42 42 * Moisture and Temperature alarm function 43 43 * Monitor Battery Level 44 44 * Uplink on periodically ... ... @@ -50,35 +50,27 @@ 50 50 * Micro SIM card slot for NB-IoT SIM 51 51 * 8500mAh Battery for long term use 52 52 53 -((( 54 - 40 +**1.3 Specification** 55 55 56 - 57 -))) 42 +**Common DC Characteristics:** 58 58 59 -== 1.3 Specification == 60 - 61 - 62 -(% style="color:#037691" %)**Common DC Characteristics:** 63 - 64 64 * Supply Voltage: 2.1v ~~ 3.6v 65 65 * Operating Temperature: -40 ~~ 85°C 66 66 67 - (% style="color:#037691" %)**NB-IoT Spec:**47 +**NB-IoT Spec:** 68 68 69 -* B1 @H-FDD: 2100MHz 70 -* B3 @H-FDD: 1800MHz 71 -* B8 @H-FDD: 900MHz 72 -* B5 @H-FDD: 850MHz 73 -* B20 @H-FDD: 800MHz 74 -* B28 @H-FDD: 700MHz 49 +* - B1 @H-FDD: 2100MHz 50 +* - B3 @H-FDD: 1800MHz 51 +* - B8 @H-FDD: 900MHz 52 +* - B5 @H-FDD: 850MHz 53 +* - B20 @H-FDD: 800MHz 54 +* - B28 @H-FDD: 700MHz 75 75 56 +**1.4 Probe Specification** 76 76 77 -== 1.4 Probe Specification == 78 78 59 +**Leaf Moisture: percentage of water drop over total leaf surface** 79 79 80 -(% style="color:#037691" %)**Leaf Moisture: percentage of water drop over total leaf surface** 81 - 82 82 * Range 0-100% 83 83 * Resolution: 0.1% 84 84 * Accuracy: ±3%(0-50%);±6%(>50%) ... ... @@ -85,7 +85,7 @@ 85 85 * IP67 Protection 86 86 * Length: 3.5 meters 87 87 88 - (% style="color:#037691" %)**Leaf Temperature:**67 +**Leaf Temperature:** 89 89 90 90 * Range -50℃~80℃ 91 91 * Resolution: 0.1℃ ... ... @@ -93,38 +93,30 @@ 93 93 * IP67 Protection 94 94 * Length: 3.5 meters 95 95 75 +**~ 1.5 Applications** 96 96 97 -== 1.5 Applications == 98 - 99 - 100 100 * Smart Agriculture 101 101 79 +**1.6 Pin mapping and power on** 102 102 103 -== 1.6 Pin mapping and power on == 104 - 105 - 106 106 [[image:image-20220907171221-4.png]] 107 107 108 108 **~ ** 109 109 110 - =2. Use NLMS01 to communicate with IoT Server=85 +**2. Use NLMS01 to communicate with IoT Server** 111 111 112 - ==2.1 How it works==87 +**2.1 How it works** 113 113 114 - 115 115 The NLMS01 is equipped with a NB-IoT module, the pre-loaded firmware in NLMS01 will get environment data from sensors and send the value to local NB-IoT network via the NB-IoT module. The NB-IoT network will forward this value to IoT server via the protocol defined by NLMS01. 116 116 117 117 The diagram below shows the working flow in default firmware of NLMS01: 118 118 119 - 120 120 [[image:image-20220907171221-5.png]] 121 121 95 +**2.2 Configure the NLMS01** 122 122 123 - ==2.2ConfiguretheNLMS01 ==97 +**2.2.1 Test Requirement** 124 124 125 -=== 2.2.1 Test Requirement === 126 - 127 - 128 128 To use NLMS01 in your city, make sure meet below requirements: 129 129 130 130 * Your local operator has already distributed a NB-IoT Network there. ... ... @@ -131,109 +131,90 @@ 131 131 * The local NB-IoT network used the band that NLMS01 supports. 132 132 * Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 133 133 134 -Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. The NLMS01 will use (%style="color:#037691" %)**CoAP(120.24.4.116:5683)**(%%)or raw(%style="color:#037691" %)**UDP(120.24.4.116:5601)** or(%%)(% style="color:#037691"%)**MQTT(120.24.4.116:1883)**(%%)or(% style="color:#037691" %)**TCP(120.24.4.116:5600)**(%%)protocol to send data to the test server105 +Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. The NLMS01 will use CoAP(120.24.4.116:5683) or raw UDP(120.24.4.116:5601) or MQTT(120.24.4.116:1883)or TCP(120.24.4.116:5600)protocol to send data to the test server 135 135 136 - 137 137 [[image:image-20220907171221-6.png]] 138 138 109 +**2.2.2 Insert SIM card** 139 139 140 -=== 2.2.2 Insert SIM card === 141 - 142 - 143 143 Insert the NB-IoT Card get from your provider. 144 144 145 145 User need to take out the NB-IoT module and insert the SIM card like below: 146 146 147 - 148 148 [[image:image-20220907171221-7.png]] 149 149 117 +**2.2.3 Connect USB – TTL to NLMS01 to configure it** 150 150 151 - ===2.2.3Connect USB–TTL to NLMS01 to configure it===119 +User need to configure NLMS01 via serial port to set the **Server Address** / **Uplink Topic** to define where and how-to uplink packets. NLMS01 support AT Commands, user can use a USB to TTL adapter to connect to NLMS01 and use AT Commands to configure it, as below. 152 152 121 +**Connection:** 153 153 154 - Userneed to configure NLMS01 via serial port to set the (% style="color:#037691" %)**Server Address** / **Uplink Topic** (%%)to define where and how-to uplink packets. NLMS01 support AT Commands, user can use a USBtoTTLadapter to connect toNLMS01anduse AT Commands to configure it, as below.123 + USB TTL GND <~-~-~-~-> GND 155 155 125 + USB TTL TXD <~-~-~-~-> UART_RXD 156 156 157 - (%style="color:blue"%)**Connection:**127 + USB TTL RXD <~-~-~-~-> UART_TXD 158 158 159 -**~ (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND(%%)** 160 - 161 -**~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)** 162 - 163 -**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)** 164 - 165 - 166 166 In the PC, use below serial tool settings: 167 167 168 -* Baud: (% style="color:green" %)**9600**169 -* Data bits:** (% style="color:green" %)8(%%)**170 -* Stop bits: (% style="color:green" %)**1**171 -* Parity: (% style="color:green" %)**None**172 -* Flow Control: (% style="color:green" %)**None**131 +* Baud: **9600** 132 +* Data bits:** 8** 133 +* Stop bits: **1** 134 +* Parity: **None** 135 +* Flow Control: **None** 173 173 174 -Make sure the switch is in FLASH position, then power on device by connecting the jumper on NLMS01. NLMS01 will output system info once power on as below, we can enter the (% style="color:green" %)**password: 12345678**(%%)to access AT Command input.137 +Make sure the switch is in FLASH position, then power on device by connecting the jumper on NLMS01. NLMS01 will output system info once power on as below, we can enter the **password: 12345678** to access AT Command input. 175 175 176 -[[image:image-202209 13090720-1.png]]139 +[[image:image-20220907171221-8.png]] 177 177 141 +**Note: the valid AT Commands can be found at: **[[**https:~~/~~/www.dropbox.com/sh/351dwor6joz8nwh/AADn1BQaAAxLF_QMyU8NkW47a?dl=0**>>url:https://www.dropbox.com/sh/351dwor6joz8nwh/AADn1BQaAAxLF_QMyU8NkW47a?dl=0]] 178 178 179 - (% style="color:red" %)**Note:thevalid AT Commandscan befoundat: **(%%)[[**https:~~/~~/www.dropbox.com/sh/351dwor6joz8nwh/AADn1BQaAAxLF_QMyU8NkW47a?dl=0**>>url:https://www.dropbox.com/sh/351dwor6joz8nwh/AADn1BQaAAxLF_QMyU8NkW47a?dl=0]]143 +**2.2.4 Use CoAP protocol to uplink data** 180 180 145 +**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/**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/]] 181 181 182 - === 2.2.4UseCoAPprotocol to uplinkdata ===147 +**Use below commands:** 183 183 149 +* **AT+PRO=1** ~/~/ Set to use CoAP protocol to uplink 150 +* **AT+SERVADDR=120.24.4.116,5683 ** ~/~/ to set CoAP server address and port 151 +* **AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** ~/~/Set COAP resource path 184 184 185 -(% 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/**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/]] 186 - 187 - 188 -(% style="color:blue" %)**Use below commands:** 189 - 190 -* (% style="color:#037691" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 191 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%) ~/~/ to set CoAP server address and port 192 -* (% style="color:#037691" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/ Set COAP resource path 193 - 194 194 For parameter description, please refer to AT command set 195 195 196 196 [[image:image-20220907171221-9.png]] 197 197 157 +After configure the server address and **reset the device** (via AT+ATZ ), NLMS01 will start to uplink sensor values to CoAP server. 198 198 199 -After configure the server address and (% style="color:#037691" %)**reset the device**(%%) (via AT+ATZ ), NLMS01 will start to uplink sensor values to CoAP server. 200 - 201 201 [[image:image-20220907171221-10.png]] 202 202 161 +**2.2.5 Use UDP protocol to uplink data(Default protocol)** 203 203 204 -=== 2.2.5 Use UDP protocol to uplink data(Default protocol) === 205 - 206 - 207 207 This feature is supported since firmware version v1.0.1 208 208 209 -* (% style="color:#037691" %)**AT+PRO=2 **(%%)~/~/210 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5601(%%)~/~/211 -* (% style="color:#037691" %)**AT+CFM=1 **(%%)~/~/165 +* **AT+PRO=2 ** ~/~/ Set to use UDP protocol to uplink 166 +* **AT+SERVADDR=120.24.4.116,5601 ** ~/~/ to set UDP server address and port 167 +* **AT+CFM=1 ** ~/~/If the server does not respond, this command is unnecessary 212 212 213 213 [[image:image-20220907171221-11.png]] 214 214 215 - 216 216 [[image:image-20220907171221-12.png]] 217 217 218 218 219 219 220 - ===2.2.6 Use MQTT protocol to uplink data===175 +**2.2.6 Use MQTT protocol to uplink data** 221 221 222 - 223 223 This feature is supported since firmware version v110 224 224 225 -* (% style="color:#037691" %)**AT+PRO=3 **(%%)~/~/226 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,1883 **(%%)~/~/227 -* (% style="color:#037691" %)**AT+CLIENT=CLIENT **(%%)~/~/228 -* (% style="color:#037691" %)**AT+UNAME=UNAME **(%%)** **~/~/229 -* (% style="color:#037691" %)**AT+PWD=PWD **(%%)** **~/~/230 -* (% style="color:#037691" %)**AT+PUBTOPIC=PUB **(%%)~/~/231 -* (% style="color:#037691" %)**AT+SUBTOPIC=SUB **(%%)179 +* **AT+PRO=3 ** ~/~/Set to use MQTT protocol to uplink 180 +* **AT+SERVADDR=120.24.4.116,1883 ** ~/~/Set MQTT server address and port 181 +* **AT+CLIENT=CLIENT ** ~/~/Set up the CLIENT of MQTT 182 +* **AT+UNAME=UNAME **~/~/Set the username of MQTT 183 +* **AT+PWD=PWD **~/~/Set the password of MQTT 184 +* **AT+PUBTOPIC=NSE01_PUB **~/~/Set the sending topic of MQTT 185 +* **AT+SUBTOPIC=NSE01_SUB ** ~/~/Set the subscription topic of MQTT 232 232 233 233 [[image:image-20220907171221-13.png]] 234 234 235 - 236 - 237 237 [[image:image-20220907171221-14.png]] 238 238 239 239 ... ... @@ -240,108 +240,81 @@ 240 240 241 241 MQTT protocol has a much higher power consumption compare vs UDP / CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval. 242 242 195 +**2.2.7 Use TCP protocol to uplink data** 243 243 244 -=== 2.2.7 Use TCP protocol to uplink data === 245 - 246 - 247 247 This feature is supported since firmware version v110 248 248 249 -* (% style="color:#037691" %)**AT+PRO=4 **(%%)~/~/250 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600 **(%%)~/~/199 +* **AT+PRO=4 ** ~/~/ Set to use TCP protocol to uplink 200 +* **AT+SERVADDR=120.24.4.116,5600 ** ~/~/ to set TCP server address and port 251 251 252 252 [[image:image-20220907171221-15.png]] 253 253 254 - 255 - 256 256 [[image:image-20220907171221-16.png]] 257 257 258 258 259 259 208 +**2.2.8 Change Update Interval** 260 260 261 -=== 2.2.8 Change Update Interval === 262 - 263 - 264 264 User can use below command to change the **uplink interval**. 265 265 266 -* (% style="color:#037691" %)**AT+TDC=7200 **(%%)~/~/ Set Update Interval to7200s(2 hour)212 +* **AT+TDC=600 ** ~/~/ Set Update Interval to 600s 267 267 268 - (% style="color:red" %)**NOTE:By default, the device will send an uplink message every 2 hour. Each Uplink Include 8 set of records in this 2 hour (15 minute interval / record).**214 +**NOTE:** 269 269 216 +**~1. By default, the device will send an uplink message every 2 hour.** 270 270 271 - ==2.3 Uplink Payload==218 +**2.3 Uplink Payload** 272 272 273 - 274 274 In this mode, uplink payload includes 87 bytes in total by default. 275 275 276 276 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. 277 277 224 +|**Size(bytes)**|**8**|**2**|**2**|**1**|**1**|1|2|2|2|4 225 +|**Value**|Device ID|Ver|BAT|Signal Strength|MOD|Interrupt|Leaf moisture|Leaf Temperature|Soil PH|Time stamp ..... 278 278 279 -(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:520px" %) 280 -|(% style="width:50px;background-color:#D9E2F3;color:#0070C0" %)**Size(bytes)**|(% style="width:40px;background-color:#D9E2F3;color:#0070C0" %)**8**|(% style="width:20px;background-color:#D9E2F3;color:#0070C0" %)**2**|(% style="width:20px;background-color:#D9E2F3;color:#0070C0" %)**2**|(% style="width:50px;background-color:#D9E2F3;color:#0070C0" %)**1**|(% style="width:30px;background-color:#D9E2F3;color:#0070C0" %)**1**|(% style="width:40px;background-color:#D9E2F3;color:#0070C0" %)**1**|(% style="width:40px;background-color:#D9E2F3;color:#0070C0" %)**2**|(% style="width:50px;background-color:#D9E2F3;color:#0070C0" %)**2**|(% style="width:50px;background-color:#D9E2F3;color:#0070C0" %)**4**|(% style="width:50px;background-color:#D9E2F3;color:#0070C0" %)**2**|(% style="width:40px;background-color:#D9E2F3;color:#0070C0" %)**2**|(% style="width:40px;background-color:#D9E2F3;color:#0070C0" %)**4** 281 -|(% style="width:96px" %)Value|(% style="width:82px" %)Device ID|(% style="width:42px" %)Ver|(% style="width:48px" %)BAT|(% style="width:124px" %)Signal Strength|(% style="width:58px" %)MOD|(% style="width:82px" %)Interrupt|(% style="width:113px" %)Leaf moisture|(% style="width:134px" %)Leaf Temperature|(% style="width:100px" %)Time stamp|(% style="width:137px" %)Leaf Temperature|(% style="width:110px" %)Leaf moisture|(% style="width:122px" %)Time stamp ..... 282 - 283 283 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NLMS01 uplink data. 284 284 285 - 286 286 [[image:image-20220907171221-17.png]] 287 287 288 - 289 289 The payload is ASCII string, representative same HEX: 290 290 291 - **0x(% style="color:red" %)__f868411056754138__ (% style="color:blue" %)__0064__ (% style="color:green" %)__0c78__ (% style="color:#00b0f0" %)__17__ (% style="color:#7030a0" %)__01__ (% style="color:#d60093" %)__00__ (% style="color:#a14d07" %)__0225__ (% style="color:#0020b0" %) __010b__ (% style="color:#420042" %)__6315537b__ (% style="color:#663300" %)//__010b0226631550fb__ __010e022663154d77__//(%%)**233 +0xf86841105675413800640c781701000225010b6315537b010b0226631550fb010e022663154d7701110225631549f1011502246315466b01190223631542e5011d022163153f62011e022163153bde011e022163153859 where: 292 292 293 -where: 235 +* Device ID: 0xf868411056754138 = f868411056754138 236 +* Version: 0x0064=100=1.0.0 294 294 295 -* (% style="color:#037691" %)**Device ID:**(%%) 0xf868411056754138 = f868411056754138 238 +* BAT: 0x0c78 = 3192 mV = 3.192V 239 +* Singal: 0x17 = 23 240 +* Mod: 0x01 = 1 241 +* Interrupt: 0x00= 0 242 +* Leaf moisture: 0x0225= 549 = 54.9% 243 +* Leaf Temperature:0x010B =267=26.7 °C 244 +* Time stamp : 0x6315537b =1662342011 245 +* Leaf Temperature, Leaf moisture,Time stamp : 010b0226631550fb 246 +* 8 sets of recorded data: Leaf Temperature, Leaf moisture,Time stamp : 010e022663154d77,....... 296 296 297 -* (% style="color:#037691"%)**Version:**(%%) 0x0064=100=1.0.0248 +**2.4 Payload Explanation and Sensor Interface** 298 298 299 -* (% style="color:#037691" %)**BAT:**(%%)0x0c78= 3192 mV = 3.192V250 +**2.4.1 Device ID** 300 300 301 -* (% style="color:#037691" %)**Singal:**(%%) 0x17 = 23 302 - 303 -* (% style="color:#037691" %)**Mod:**(%%) 0x01 = 1 304 - 305 -* (% style="color:#037691" %)**Interrupt:**(%%) 0x00= 0 306 - 307 -* (% style="color:#037691" %)**Leaf moisture:**(%%) 0x0225= 549 = 54.9% 308 - 309 -* (% style="color:#037691" %)**Leaf Temperature: **(%%)0x010B =267=26.7 °C 310 - 311 -* (% style="color:#037691" %)**Time stamp :** (%%)0x6315537b =1662342011 ([[Unix Epoch Time>>https://www.epochconverter.com/]]) 312 - 313 -* (% style="color:#037691" %)**Leaf Temperature, Leaf moisture,Time stamp : **(%%)010b0226631550fb 314 - 315 -* (% style="color:#037691" %)**8 sets of recorded data: **(%%)Leaf Temperature, Leaf moisture,Time stamp : 010e022663154d77,....... 316 - 317 -== 2.4 Payload Explanation and Sensor Interface == 318 - 319 -=== 2.4.1 Device ID === 320 - 321 - 322 322 By default, the Device ID equal to the last 15 bits of IMEI. 323 323 324 -User can use (% style="color:#037691" %)**AT+DEUI**(%%)to set Device ID254 +User can use **AT+DEUI** to set Device ID 325 325 256 +**Example:** 326 326 327 -(% style="color:blue" %)**Example**: 328 - 329 329 AT+DEUI=868411056754138 330 330 331 331 The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID. 332 332 262 +**2.4.2 Version Info** 333 333 334 -=== 2.4.2 Version Info === 335 - 336 - 337 337 Specify the software version: 0x64=100, means firmware version 1.00. 338 338 339 339 For example: 0x00 64 : this device is NLMS01 with firmware version 1.0.0. 340 340 268 +**2.4.3 Battery Info** 341 341 342 -=== 2.4.3 Battery Info === 343 - 344 - 345 345 Check the battery voltage for NLMS01. 346 346 347 347 Ex1: 0x0B45 = 2885mV ... ... @@ -348,15 +348,12 @@ 348 348 349 349 Ex2: 0x0B49 = 2889mV 350 350 276 +**2.4.4 Signal Strength** 351 351 352 -=== 2.4.4 Signal Strength === 353 - 354 - 355 355 NB-IoT Network signal Strength. 356 356 280 +**Ex1: 0x1d = 29** 357 357 358 -(% style="color:blue" %)**Ex1: 0x1d = 29** 359 - 360 360 **0** -113dBm or less 361 361 362 362 **1** -111dBm ... ... @@ -367,45 +367,37 @@ 367 367 368 368 **99** Not known or not detectable 369 369 292 +**2.4.5 Leaf** moisture 370 370 371 - ===2.4.5Leaf moisture===294 +Get the moisture of the **Leaf**. The value range of the register is 300-1000(Decimal), divide this value by 100 to get the percentage of moisture in the **Leaf**. 372 372 296 +For example, if the data you get from the register is **__0x05 0xDC__**, the moisture content in the **Leaf** is 373 373 374 - Get the moisture of the (% style="color:#037691" %)**Leaf**(%%).Thevalue range of the register is 300-1000(Decimal),divide this value by100toget the percentage of moisture in the Leaf.298 +**0229(H) = 549(D) /100 = 54.9.** 375 375 376 - Forexample, ifthedata you get fromtheegister is (% style="color:#037691" %)**__0x05 0xDC__**(%%), the moisturecontent in the (% style="color:#037691" %)**Leaf**(%%) is300 +**2.4.6 Leaf Temperature** 377 377 378 - (%style="color:blue"%)**0229(H)=549(D)/100=54.9.**302 +Get the temperature in the **Leaf**. The value range of the register is -4000 - +800(Decimal), divide this value by 100 to get the temperature in the **Leaf**. For example, if the data you get from the register is **__0x09 0xEC__**, the temperature content in the **Leaf **is 379 379 304 +**Example**: 380 380 381 -=== 2.4.6 Leaf Temperature===306 +If payload is 0105H: ((0x0105 & 0x8000)>>15 === 0),temp = 0105(H)/10 = 26.1 °C 382 382 308 +If payload is FF7EH: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/10 = -12.9 °C 383 383 384 - Get the temperature in the Leaf. The value range of the register is -4000 - +800(Decimal), dividethisvalue by 100to get the temperature in the Leaf. For example, if the data you get from the register is (% style="color:#037691" %)**__0x09 0xEC__**(%%), the temperature content in the (% style="color:#037691" %)**Leaf **(%%)is310 +**2.4.7 Timestamp** 385 385 386 -(% style="color:blue" %)**Example**: 387 - 388 -If payload is **0105H**: ((0x0105 & 0x8000)>>15 === 0),temp = 0105(H)/10 = 26.1 °C 389 - 390 -If payload is **FF7EH**: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/10 = -12.9 °C 391 - 392 - 393 -=== 2.4.7 Timestamp === 394 - 395 - 396 396 Time stamp : 0x6315537b =1662342011 397 397 398 398 Convert Unix timestamp to time 2022-9-5 9:40:11. 399 399 316 +**2.4.8 Digital Interrupt** 400 400 401 - === 2.4.8Digital Interrupt===318 +Digital Interrupt refers to pin **GPIO_EXTI**, and there are different trigger methods. When there is a trigger, the NLMS01 will send a packet to the server. 402 402 403 - 404 -Digital Interrupt refers to pin (% style="color:#037691" %)**GPIO_EXTI**(%%), and there are different trigger methods. When there is a trigger, the NLMS01 will send a packet to the server. 405 - 406 406 The command is: 407 407 408 - (% style="color:blue" %)**AT+INTMOD=3 **(%%)~/~/322 +**AT+INTMOD=3 ** ~/~/(more info about INMOD please refer [[**AT Command Manual**>>url:https://www.dragino.com/downloads/downloads/NB-IoT/NBSN95/DRAGINO_NBSN95-NB_AT%20Commands_v1.1.0.pdf]])**.** 409 409 410 410 The lower four bits of this data field shows if this packet is generated by interrupt or not. Click here for the hardware and software set up. 411 411 ... ... @@ -415,32 +415,27 @@ 415 415 416 416 0x(01): Interrupt Uplink Packet. 417 417 332 +**2.4.9 +5V Output** 418 418 419 -=== 2.4.9 +5V Output === 420 - 421 - 422 422 NLMS01 will enable +5V output before all sampling and disable the +5v after all sampling. 423 423 424 424 The 5V output time can be controlled by AT Command. 425 425 426 - (% style="color:blue" %)**AT+5VT=1000**338 +**AT+5VT=1000** 427 427 428 428 Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.** ** 429 429 430 430 431 - ==2.5 Downlink Payload==343 +**2.5 Downlink Payload** 432 432 433 - 434 434 By default, NLMS01 prints the downlink payload to console port. 435 435 436 436 [[image:image-20220907171221-18.png]] 437 437 349 +**Examples:** 438 438 439 - (%style="color:blue" %)**Examples:**351 +* **Set TDC** 440 440 441 - 442 -* (% style="color:#037691" %)**Set TDC** 443 - 444 444 If the payload=0100003C, it means set the END Node's TDC to 0x00003C=60(S), while type code is 01. 445 445 446 446 Payload: 01 00 00 1E TDC=30S ... ... @@ -447,22 +447,16 @@ 447 447 448 448 Payload: 01 00 00 3C TDC=60S 449 449 359 +* **Reset** 450 450 451 - 452 -* (% style="color:#037691" %)**Reset** 453 - 454 454 If payload = 0x04FF, it will reset the NLMS01 455 455 363 +* **INTMOD** 456 456 457 - 458 -* (% style="color:#037691" %)**INTMOD** 459 - 460 460 Downlink Payload: 06000003, Set AT+INTMOD=3 461 461 367 +**2.6 LED Indicator** 462 462 463 -== 2.6 LED Indicator == 464 - 465 - 466 466 The NLMS01 has an internal LED which is to show the status of different state. 467 467 468 468 * When power on, NLMS01 will detect if sensor probe is connected, if probe detected, LED will blink four times. (no blinks in this step is no probe) ... ... @@ -470,22 +470,18 @@ 470 470 * After NLMS01 join NB-IoT network. The LED will be ON for 3 seconds. 471 471 * For each uplink probe, LED will be on for 500ms. 472 472 473 - ==2.7==376 +**2.7 Installation** 474 474 475 - 476 476 NLMS01 probe has two sides. The side without words are the sense side. Please be ware when install the sensor. 477 477 478 - 479 479 [[image:image-20220907171221-19.png]] 480 480 382 +**2.8 Moisture and Temperature alarm function** 481 481 482 - ==2.8Moisture and Temperature alarmfunction ==384 +➢ AT Command: 483 483 386 +AT+ HUMALARM =min,max 484 484 485 -(% style="color:blue" %)**➢ AT Command:** 486 - 487 -(% style="color:#037691" %)**AT+ HUMALARM =min,max** 488 - 489 489 ² When min=0, and max≠0, Alarm higher than max 490 490 491 491 ² When min≠0, and max=0, Alarm lower than min ... ... @@ -492,9 +492,8 @@ 492 492 493 493 ² When min≠0 and max≠0, Alarm higher than max or lower than min 494 494 394 +Example: 495 495 496 -(% style="color:blue" %)**Example:** 497 - 498 498 AT+ HUMALARM =50,60 ~/~/ Alarm when moisture lower than 50. 499 499 500 500 AT+ TEMPALARM=min,max ... ... @@ -505,199 +505,197 @@ 505 505 506 506 ² When min≠0 and max≠0, Alarm higher than max or lower than min 507 507 406 +Example: 508 508 509 -(% style="color:blue" %)**Example:** 510 - 511 511 AT+ TEMPALARM=20,30 ~/~/ Alarm when temperature lower than 20. 512 512 513 513 514 - ==2.9==411 +**2.9 Set the number of data to be uploaded and the recording time** 515 515 413 +➢ AT Command: 516 516 517 - (%style="color:blue"%)**➢ATCommand:**415 +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) 518 518 519 -* (% style="color:#037691" %)**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) 520 -* (% style="color:#037691" %)**AT+NOUD=8** (%%)~/~/ The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded. 521 521 522 - The di agram belowexplainsthe relationshipbetweenTR, NOUD,andTDCmore clearly**:**418 +AT+NOUD=8 ~/~/The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded. 523 523 524 - [[image:image-20221009001002-1.png||height="706"width="982"]]420 +**2.10 Read or Clear cached data** 525 525 422 +➢ AT Command: 526 526 527 - == 2.10Reador Clearcached data==424 +AT+CDP ~/~/ Read cached data 528 528 426 +[[image:image-20220907171221-20.png]] 529 529 530 -(% style="color:blue" %)**➢ AT Command:** 531 531 532 -* (% style="color:#037691" %)**AT+CDP** (%%) ~/~/ Read cached data 533 -* (% style="color:#037691" %)**AT+CDP=0 ** (%%) ~/~/ Clear cached data 429 +AT+CDP=0 ~/~/ Clear cached data 534 534 535 -[[image:image-20220907171221-20.png]] 536 536 432 +**2.8 Firmware Change Log** 537 537 538 - ==2.11Firmware ChangeLog434 +Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/1zmcakvbkf24f8x/AACmq2dZ3iRB9F1nVWeEB9Moa?dl=0>>url:https://www.dropbox.com/sh/1zmcakvbkf24f8x/AACmq2dZ3iRB9F1nVWeEB9Moa?dl=0]] 539 539 436 +Upgrade Instruction: [[Upgrade Firmware>>path:#H5.1200BHowtoUpgradeFirmware]] 540 540 541 - DownloadURL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/qdc3js2iu1vlipx/AACMHI3CvVb8g7YQMrIHY673a?dl=0>>https://www.dropbox.com/sh/qdc3js2iu1vlipx/AACMHI3CvVb8g7YQMrIHY673a?dl=0]]438 +**2.9 Battery Analysis** 542 542 543 - UpgradeInstruction: [[UpgradeFirmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]440 +**2.9.1 Battery Type** 544 544 442 +The NLMS01 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. 545 545 546 - ==2.12 Battery&PowerConsumption==444 +The battery is designed to last for several years depends on the actually use environment and update interval. 547 547 446 +The battery related documents as below: 548 548 549 -NLMS01 uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace. 448 +* [[Battery Dimension>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 449 +* [[Lithium-Thionyl Chloride Battery datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 450 +* [[Lithium-ion Battery-Capacitor datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 550 550 551 -[[ **Battery Info & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]].452 +[[image:image-20220907171221-21.png]] 552 552 454 +**2.9.2 Power consumption Analyze** 553 553 554 - =3.AccessNB-IoTModule=456 +Dragino battery powered product are all runs in Low Power mode. We have an update battery calculator which base on the measurement of the real device. User can use this calculator to check the battery life and calculate the battery life if want to use different transmit interval. 555 555 458 +Instruction to use as below: 556 556 557 - Userscan directlyaccessthe ATcommandt of theNB-IoT module.460 +**Step 1: **Downlink the up-to-date DRAGINO_Battery_Life_Prediction_Table.xlsx from: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/]] 558 558 559 - TheATCommandset canrefertheBC35-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/]]462 +**Step 2: ** Open it and choose 560 560 464 +* Product Model 465 +* Uplink Interval 466 +* Working Mode 561 561 562 - [[image:image-20220907171221-23.png]]468 +And the Life expectation in difference case will be shown on the right. 563 563 470 +[[image:image-20220907171221-22.jpeg]] 564 564 565 - = 4.UsingtheAT Commands =472 +**2.9.3 Battery Note** 566 566 567 - ==4.1AccessATCommands==474 +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 transmit LoRa, then the battery life may be decreased. 568 568 476 +**2.9.4 Replace the battery** 569 569 570 - See thislinkfordetail: [[https:~~/~~/www.dropbox.com/sh/351dwor6joz8nwh/AADn1BQaAAxLF_QMyU8NkW47a?dl=0>>url:https://www.dropbox.com/sh/351dwor6joz8nwh/AADn1BQaAAxLF_QMyU8NkW47a?dl=0]]478 +The default battery pack of NLMS01 includes a ER26500 plus super capacitor. If user can't find this pack locally, they can find ER26500 or equivalence without the SPC1520 capacitor, which will also work in most case. The SPC can enlarge the battery life for high frequency use (update period below 5 minutes). 571 571 572 - AT+<CMD>?: Helpon<CMD>480 +**3. Access NB-IoT Module** 573 573 574 -AT +<CMD>:Run<CMD>482 +Users can directly access the AT command set of the NB-IoT module. 575 575 576 -AT +<CMD>=<value>:Setue484 +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/]] 577 577 578 - AT+<CMD>=? : Get the value486 +[[image:image-20220907171221-23.png]] 579 579 488 +**4. Using the AT Commands** 580 580 581 - (% style="color:#037691" %)**GeneralCommands**490 +**4.1 Access AT Commands** 582 582 583 - AT:Attention492 +See this link for detail: [[https:~~/~~/www.dropbox.com/sh/351dwor6joz8nwh/AADn1BQaAAxLF_QMyU8NkW47a?dl=0>>url:https://www.dropbox.com/sh/351dwor6joz8nwh/AADn1BQaAAxLF_QMyU8NkW47a?dl=0]] 584 584 585 -AT? :ShortHelp494 +AT+<CMD>? : Help on <CMD> 586 586 587 -AT Z:MCUReset496 +AT+<CMD> : Run <CMD> 588 588 589 -AT+ TDC:ApplicationDataTransmissionInterval498 +AT+<CMD>=<value> : Set the value 590 590 591 -AT+C FG:Print all configurations500 +AT+<CMD>=? : Get the value 592 592 593 - AT+CFGMOD : Working modeselection502 +**General Commands** 594 594 595 -AT +INTMOD:Setthetrigger interrupt mode504 +AT : Attention 596 596 597 -AT +5VT:Setextendthetimeof5Vpower506 +AT? : Short Help 598 598 599 -AT +PRO :Chooseagreement508 +ATZ : MCU Reset 600 600 601 -AT+ RXDL:Extendthesendingandreceivingtime510 +AT+TDC : Application Data Transmission Interval 602 602 603 -AT+ SERVADDR :ServerAddress512 +AT+CFG : Print all configurations 604 604 605 -AT+ APN:GetorsettheAPN514 +AT+CFGMOD : Working mode selection 606 606 607 -AT+ FBAND :Get orSetwhetherto automaticallymodifythefrequencyband516 +AT+INTMOD : Set the trigger interrupt mode 608 608 609 -AT+ DNSCFG:Getor SetDNSServer518 +AT+5VT : Set extend the time of 5V power 610 610 611 -AT+ GETSENSORVALUE:Returnsthecurrentsensormeasurement520 +AT+PRO : Choose agreement 612 612 613 -AT+ TR:GetorSet recordtime"522 +AT+RXDL : Extend the sending and receiving time 614 614 615 -AT+ NOUD:GetorSetthenumberof data to beuploaded524 +AT+SERVADDR : Server Address 616 616 617 -AT+ CDP:ReadorClearcacheddata526 +AT+TR : Get or Set record time" 618 618 619 -AT+TEMPALARM : Get or Set alarm of temp 620 620 621 -AT+ HUMALARM:alarm ofhumidity529 +AT+NOUD : Get or Set the number of data to be uploaded 622 622 623 623 624 - (%style="color:#037691"%)**COAPManagement**532 +AT+CDP : Read or Clear cached data 625 625 626 -AT+URI : Resource parameters 627 627 535 +AT+TEMPALARM : Get or Set alarm of temp 628 628 629 - (%style="color:#037691"%)**UDPManagement**537 +AT+HUMALARM : Get or Set alarm of PH 630 630 631 -AT+CFM : Upload confirmation mode (only valid for UDP) 632 632 540 +**COAP Management** 633 633 634 - (%style="color:#037691"%)**MQTT Management**542 +AT+URI : Resource parameters 635 635 636 - AT+CLIENT: Get or SetMQTT client544 +**UDP Management** 637 637 638 -AT+ UNAME:GetorSetMQTT Username546 +AT+CFM : Upload confirmation mode (only valid for UDP) 639 639 640 - AT+PWD : Get or SetMQTTpassword548 +**MQTT Management** 641 641 642 -AT+ PUBTOPIC :publishtopic550 +AT+CLIENT : Get or Set MQTT client 643 643 644 -AT+ SUBTOPIC :Get or Set MQTT subscriptiontopic552 +AT+UNAME : Get or Set MQTT Username 645 645 554 +AT+PWD : Get or Set MQTT password 646 646 647 - (%style="color:#037691"%)**Information**556 +AT+PUBTOPIC : Get or Set MQTT publish topic 648 648 649 -AT+ FDR :FactoryDataReset558 +AT+SUBTOPIC : Get or Set MQTT subscription topic 650 650 651 - AT+PWORD : Serial Access Password560 +**Information** 652 652 562 +AT+FDR : Factory Data Reset 653 653 654 - = 5.FAQ=564 +AT+PWORD : Serial Access Password 655 655 656 - ==5.1 How to UpgradeFirmware ==566 +**5. FAQ** 657 657 568 +**5.1 How to Upgrade Firmware** 658 658 659 659 User can upgrade the firmware for 1) bug fix, 2) new feature release. 660 660 661 661 Please see this link for how to upgrade: [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H2.HardwareUpgradeMethodSupportList>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H2.HardwareUpgradeMethodSupportList]] 662 662 574 +**Notice, **NLMS01 **and **NLMS01 **share the same mother board. They use the same connection and method to update.** 663 663 664 - (% style="color:red" %)**Notice,NLMS01and LLMS01 share the same motherboard. Theyuse the same connectionand method to update.**576 +**6. Trouble Shooting** 665 665 578 +**6.1 Connection problem when uploading firmware** 666 666 667 -= 6. Trouble Shooting = 668 - 669 -== 6.1 Connection problem when uploading firmware == 670 - 671 - 672 672 **Please see: **[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H3.3Troubleshooting>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H3.3Troubleshooting]] 673 673 582 +**6.2 AT Command input doesn't work** 674 674 675 - ==6.2ATCommand input doesn't work==584 +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 **ENTER** while sending out the command. Some serial tool doesn't send **ENTER** while press the send key, user need to add ENTER in their string. 676 676 586 +**7. Order Info** 677 677 678 -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. 679 - 680 - 681 -== 6.3 Not able to connect to NB-IoT network and keep showing "Signal Strength:99". == 682 - 683 - 684 -This means sensor is trying to join the NB-IoT network but fail. Please see this link for **//[[trouble shooting for signal strenght:99>>doc:Main.CSQ\:99,99.WebHome]]//**. 685 - 686 - 687 -= 7. Order Info = 688 - 689 - 690 690 Part Number**:** NLMS01 691 691 590 +**8. Packing Info** 692 692 693 - = 8.Packing Info =592 +**Package Includes**: 694 694 695 - 696 -(% style="color:#037691" %)**Package Includes:** 697 - 698 698 * NLMS01 NB-IoT Leaf Moisture Sensor x 1 699 699 700 - (% style="color:#037691" %)**Dimension and weight**:596 +**Dimension and weight**: 701 701 702 702 * Device Size: cm 703 703 * Device Weight: g ... ... @@ -704,10 +704,12 @@ 704 704 * Package Size / pcs : cm 705 705 * Weight / pcs : g 706 706 707 -= 9. Support = 708 708 604 +**9. Support** 709 709 710 710 * 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. 711 711 * 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]] 712 712 713 713 610 + 611 +
- image-20220913090720-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -224.9 KB - Content
- image-20221009001002-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Edwin - Size
-
... ... @@ -1,1 +1,0 @@ 1 -282.9 KB - Content