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,84 +1,90 @@ 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 = 11 11 12 - == 1.1 WhatisNLMS01 Leaf Moisture Sensor==10 +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. 13 13 12 +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. 14 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. 15 +\\NLMS01 supports different uplink methods include **TCP,MQTT,UDP and CoAP **for different application requirement. 16 +\\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) 17 +\\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 23 +== 1.2 Features == 35 35 36 -== 1.2 Features == 25 +* ((( 26 +NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD 27 +))) 28 +* ((( 29 +Monitor Leaf moisture 30 +))) 37 37 32 +* ((( 33 + Monitor Leaf temperature 34 +))) 38 38 39 -* NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD 40 -* Monitor Leaf moisture 41 -* Monitor Leaf temperature 42 -* Moisture and Temperature alarm function 43 -* Monitor Battery Level 44 -* Uplink on periodically 45 -* Downlink to change configure 46 -* IP66 Waterproof Enclosure 47 -* IP67 rate for the Sensor Probe 48 -* Ultra-Low Power consumption 49 -* AT Commands to change parameters 50 -* Micro SIM card slot for NB-IoT SIM 51 -* 8500mAh Battery for long term use 52 - 53 -((( 54 - 55 - 56 - 36 +* ((( 37 +Moisture and Temperature alarm function 57 57 ))) 39 +* ((( 40 +Monitor Battery Level 41 +))) 42 +* ((( 43 +Uplink on periodically 44 +))) 45 +* ((( 46 +Downlink to change configure 47 +))) 48 +* ((( 49 +IP66 Waterproof Enclosure 50 +))) 51 +* ((( 52 +IP67 rate for the Sensor Probe 53 +))) 54 +* ((( 55 +Ultra-Low Power consumption 56 +))) 57 +* ((( 58 +AT Commands to change parameters 59 +))) 60 +* ((( 61 +Micro SIM card slot for NB-IoT SIM 62 +))) 63 +* ((( 64 +8500mAh Battery for long term use 65 +))) 58 58 59 59 == 1.3 Specification == 60 60 69 +**Common DC Characteristics:** 61 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:**74 +**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 76 +* - B1 @H-FDD: 2100MHz 77 +* - B3 @H-FDD: 1800MHz 78 +* - B8 @H-FDD: 900MHz 79 +* - B5 @H-FDD: 850MHz 80 +* - B20 @H-FDD: 800MHz 81 +* - B28 @H-FDD: 700MHz 75 75 83 +== 1.4 Probe Specification == 76 76 77 -== 1.4 Probe Specification == 78 78 86 +**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:**94 +**Leaf Temperature:** 89 89 90 90 * Range -50℃~80℃ 91 91 * Resolution: 0.1℃ ... ... @@ -93,16 +93,12 @@ 93 93 * IP67 Protection 94 94 * Length: 3.5 meters 95 95 102 +== 1.5 Applications == 96 96 97 -== 1.5 Applications == 98 - 99 - 100 100 * Smart Agriculture 101 101 106 +== 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 **~ ** ... ... @@ -111,20 +111,16 @@ 111 111 112 112 == 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 122 +== **2.2 Configure the NLMS01** == 122 122 123 - ==2.2ConfiguretheNLMS01 ==124 +**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 server132 +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 136 +**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 144 +**2.2.3 Connect USB – TTL to NLMS01 to configure it** 150 150 151 - ===2.2.3Connect USB–TTL to NLMS01 to configure it===146 +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 148 +**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.150 + USB TTL GND <~-~-~-~-> GND 155 155 152 + USB TTL TXD <~-~-~-~-> UART_RXD 156 156 157 - (%style="color:blue"%)**Connection:**154 + 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**158 +* Baud: **9600** 159 +* Data bits:** 8** 160 +* Stop bits: **1** 161 +* Parity: **None** 162 +* 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.164 +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]]166 +[[image:image-20220907171221-8.png]] 177 177 168 +**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]]170 +**2.2.4 Use CoAP protocol to uplink data** 180 180 172 +**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 ===174 +**Use below commands:** 183 183 176 +* **AT+PRO=1** ~/~/ Set to use CoAP protocol to uplink 177 +* **AT+SERVADDR=120.24.4.116,5683 ** ~/~/ to set CoAP server address and port 178 +* **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 184 +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 188 +**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 **(%%)~/~/192 +* **AT+PRO=2 ** ~/~/ Set to use UDP protocol to uplink 193 +* **AT+SERVADDR=120.24.4.116,5601 ** ~/~/ to set UDP server address and port 194 +* **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===202 +**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 **(%%)206 +* **AT+PRO=3 ** ~/~/Set to use MQTT protocol to uplink 207 +* **AT+SERVADDR=120.24.4.116,1883 ** ~/~/Set MQTT server address and port 208 +* **AT+CLIENT=CLIENT ** ~/~/Set up the CLIENT of MQTT 209 +* **AT+UNAME=UNAME **~/~/Set the username of MQTT 210 +* **AT+PWD=PWD **~/~/Set the password of MQTT 211 +* **AT+PUBTOPIC=PUB **~/~/Set the sending topic of MQTT 212 +* **AT+SUBTOPIC=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,109 +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 222 +**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 **(%%)~/~/226 +* **AT+PRO=4 ** ~/~/ Set to use TCP protocol to uplink 227 +* **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 235 +**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)239 +* **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).**241 +**NOTE:** 269 269 243 +**~1. By default, the device will send an uplink message every 2 hour.** 270 270 271 271 == 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 251 +|**Size(bytes)**|**8**|**2**|**2**|1|1|1|2|2|4|2|2|4 252 +|**Value**|Device ID|Ver|BAT|Signal Strength|MOD|Interrupt|Leaf moisture|Leaf Temperature|Time stamp|Leaf Temperature|Leaf moisture|Time stamp ..... 278 278 279 -(% border="1" style="background-color:#ffffcc; color:green; width:520px" %) 280 -|=(% scope="row" style="width: 50px;" %)**Size(bytes)**|(% style="width:40px" %)**8**|(% style="width:20px" %)**2**|(% style="width:20px" %)**2**|(% style="width:60px" %)**1**|(% style="width:20px" %)**1**|(% style="width:40px" %)**1**|(% style="width:40px" %)**2**|(% style="width:50px" %)**2**|(% style="width:50px" %)**4**|(% style="width:50px" %)**2**|(% style="width:40px" %)**2**|(% style="width:40px" %)**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__//(%%)**260 +0xf86841105675413800640c781701000225010b6315537b010b0226631550fb010e022663154d7701110225631549f1011502246315466b01190223631542e5011d022163153f62011e022163153bde011e022163153859 where: 292 292 293 -where: 262 +* Device ID: 0xf868411056754138 = f868411056754138 263 +* Version: 0x0064=100=1.0.0 294 294 295 -* (% style="color:#037691" %)**Device ID:**(%%) 0xf868411056754138 = f868411056754138 265 +* BAT: 0x0c78 = 3192 mV = 3.192V 266 +* Singal: 0x17 = 23 267 +* Mod: 0x01 = 1 268 +* Interrupt: 0x00= 0 269 +* Leaf moisture: 0x0225= 549 = 54.9% 270 +* Leaf Temperature:0x010B =267=26.7 °C 271 +* Time stamp : 0x6315537b =1662342011 272 +* Leaf Temperature, Leaf moisture,Time stamp : 010b0226631550fb 273 +* 8 sets of recorded data: Leaf Temperature, Leaf moisture,Time stamp : 010e022663154d77,....... 296 296 297 -* (% style="color:#037691" %)**Version:**(%%) 0x0064=100=1.0.0 298 - 299 -* (% style="color:#037691" %)**BAT:** (%%)0x0c78 = 3192 mV = 3.192V 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 - 318 318 == 2.4 Payload Explanation and Sensor Interface == 319 319 320 - ===2.4.1 Device ID===277 +**2.4.1 Device ID** 321 321 322 - 323 323 By default, the Device ID equal to the last 15 bits of IMEI. 324 324 325 -User can use (% style="color:#037691" %)**AT+DEUI**(%%)to set Device ID281 +User can use **AT+DEUI** to set Device ID 326 326 283 +**Example:** 327 327 328 -(% style="color:blue" %)**Example**: 329 - 330 330 AT+DEUI=868411056754138 331 331 332 332 The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID. 333 333 289 +**2.4.2 Version Info** 334 334 335 -=== 2.4.2 Version Info === 336 - 337 - 338 338 Specify the software version: 0x64=100, means firmware version 1.00. 339 339 340 340 For example: 0x00 64 : this device is NLMS01 with firmware version 1.0.0. 341 341 295 +**2.4.3 Battery Info** 342 342 343 -=== 2.4.3 Battery Info === 344 - 345 - 346 346 Check the battery voltage for NLMS01. 347 347 348 348 Ex1: 0x0B45 = 2885mV ... ... @@ -349,15 +349,12 @@ 349 349 350 350 Ex2: 0x0B49 = 2889mV 351 351 303 +**2.4.4 Signal Strength** 352 352 353 -=== 2.4.4 Signal Strength === 354 - 355 - 356 356 NB-IoT Network signal Strength. 357 357 307 +**Ex1: 0x1d = 29** 358 358 359 -(% style="color:blue" %)**Ex1: 0x1d = 29** 360 - 361 361 **0** -113dBm or less 362 362 363 363 **1** -111dBm ... ... @@ -368,45 +368,37 @@ 368 368 369 369 **99** Not known or not detectable 370 370 319 +**2.4.5 Leaf** moisture 371 371 372 - ===2.4.5Leaf moisture===321 +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**. 373 373 323 +For example, if the data you get from the register is **__0x05 0xDC__**, the moisture content in the **Leaf** is 374 374 375 - 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.325 +**0229(H) = 549(D) /100 = 54.9.** 376 376 377 - Forexample, ifthedata you get fromtheegister is (% style="color:#037691" %)**__0x05 0xDC__**(%%), the moisturecontent in the (% style="color:#037691" %)**Leaf**(%%) is327 +**2.4.6 Leaf Temperature** 378 378 379 - (%style="color:blue"%)**0229(H)=549(D)/100=54.9.**329 +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 380 380 331 +**Example**: 381 381 382 -=== 2.4.6 Leaf Temperature===333 +If payload is 0105H: ((0x0105 & 0x8000)>>15 === 0),temp = 0105(H)/10 = 26.1 °C 383 383 335 +If payload is FF7EH: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/10 = -12.9 °C 384 384 385 - 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 **(%%)is337 +**2.4.7 Timestamp** 386 386 387 -(% style="color:blue" %)**Example**: 388 - 389 -If payload is **0105H**: ((0x0105 & 0x8000)>>15 === 0),temp = 0105(H)/10 = 26.1 °C 390 - 391 -If payload is **FF7EH**: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/10 = -12.9 °C 392 - 393 - 394 -=== 2.4.7 Timestamp === 395 - 396 - 397 397 Time stamp : 0x6315537b =1662342011 398 398 399 399 Convert Unix timestamp to time 2022-9-5 9:40:11. 400 400 343 +**2.4.8 Digital Interrupt** 401 401 402 - === 2.4.8Digital Interrupt===345 +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. 403 403 404 - 405 -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. 406 - 407 407 The command is: 408 408 409 - (% style="color:blue" %)**AT+INTMOD=3 **(%%)~/~/349 +**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]])**.** 410 410 411 411 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. 412 412 ... ... @@ -416,15 +416,13 @@ 416 416 417 417 0x(01): Interrupt Uplink Packet. 418 418 359 +**2.4.9 +5V Output** 419 419 420 -=== 2.4.9 +5V Output === 421 - 422 - 423 423 NLMS01 will enable +5V output before all sampling and disable the +5v after all sampling. 424 424 425 425 The 5V output time can be controlled by AT Command. 426 426 427 - (% style="color:blue" %)**AT+5VT=1000**365 +**AT+5VT=1000** 428 428 429 429 Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.** ** 430 430 ... ... @@ -431,17 +431,14 @@ 431 431 432 432 == 2.5 Downlink Payload == 433 433 434 - 435 435 By default, NLMS01 prints the downlink payload to console port. 436 436 437 437 [[image:image-20220907171221-18.png]] 438 438 376 +**Examples:** 439 439 440 - (%style="color:blue" %)**Examples:**378 +* **Set TDC** 441 441 442 - 443 -* (% style="color:#037691" %)**Set TDC** 444 - 445 445 If the payload=0100003C, it means set the END Node's TDC to 0x00003C=60(S), while type code is 01. 446 446 447 447 Payload: 01 00 00 1E TDC=30S ... ... @@ -448,22 +448,16 @@ 448 448 449 449 Payload: 01 00 00 3C TDC=60S 450 450 386 +* **Reset** 451 451 452 - 453 -* (% style="color:#037691" %)**Reset** 454 - 455 455 If payload = 0x04FF, it will reset the NLMS01 456 456 390 +* **INTMOD** 457 457 458 - 459 -* (% style="color:#037691" %)**INTMOD** 460 - 461 461 Downlink Payload: 06000003, Set AT+INTMOD=3 462 462 463 - 464 464 == 2.6 LED Indicator == 465 465 466 - 467 467 The NLMS01 has an internal LED which is to show the status of different state. 468 468 469 469 * 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) ... ... @@ -471,23 +471,18 @@ 471 471 * After NLMS01 join NB-IoT network. The LED will be ON for 3 seconds. 472 472 * For each uplink probe, LED will be on for 500ms. 473 473 403 +== 2.7 Installation == 474 474 475 -== 2.7 Installation == 476 - 477 - 478 478 NLMS01 probe has two sides. The side without words are the sense side. Please be ware when install the sensor. 479 479 480 - 481 481 [[image:image-20220907171221-19.png]] 482 482 409 +== 2.8 Moisture and Temperature alarm function == 483 483 484 - ==2.8Moisture and Temperature alarmfunction ==411 +➢ AT Command: 485 485 413 +AT+ HUMALARM =min,max 486 486 487 -(% style="color:blue" %)**➢ AT Command:** 488 - 489 -(% style="color:#037691" %)**AT+ HUMALARM =min,max** 490 - 491 491 ² When min=0, and max≠0, Alarm higher than max 492 492 493 493 ² When min≠0, and max=0, Alarm lower than min ... ... @@ -494,9 +494,8 @@ 494 494 495 495 ² When min≠0 and max≠0, Alarm higher than max or lower than min 496 496 421 +Example: 497 497 498 -(% style="color:blue" %)**Example:** 499 - 500 500 AT+ HUMALARM =50,60 ~/~/ Alarm when moisture lower than 50. 501 501 502 502 AT+ TEMPALARM=min,max ... ... @@ -507,199 +507,196 @@ 507 507 508 508 ² When min≠0 and max≠0, Alarm higher than max or lower than min 509 509 433 +Example: 510 510 511 -(% style="color:blue" %)**Example:** 512 - 513 513 AT+ TEMPALARM=20,30 ~/~/ Alarm when temperature lower than 20. 514 514 515 515 516 -== 2.9 438 +== 2.9 Set the number of data to be uploaded and the recording time == 517 517 440 +➢ AT Command: 518 518 519 - (%style="color:blue"%)**➢ATCommand:**442 +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 520 521 -* (% 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) 522 -* (% 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. 444 +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 - Thediagrambelowexplainstherelationship between TR, NOUD,andTDC more clearly**:**446 +== 2.10 Read or Clear cached data == 525 525 526 - [[image:image-20221009001002-1.png||height="706" width="982"]]448 +➢ AT Command: 527 527 450 +AT+CDP ~/~/ Read cached data 528 528 529 - == 2.10 Read or Clear cached data ==452 +[[image:image-20220907171221-20.png]] 530 530 531 531 532 - (%style="color:blue"%)**➢ AT Command:**455 +AT+CDP=0 ~/~/ Clear cached data 533 533 534 -* (% style="color:#037691" %)**AT+CDP** (%%) ~/~/ Read cached data 535 -* (% style="color:#037691" %)**AT+CDP=0 ** (%%) ~/~/ Clear cached data 536 536 537 - [[image:image-20220907171221-20.png]]458 +== 2.11 Firmware Change Log == 538 538 460 +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 540 - ==2.11FirmwareChange Log==462 +Upgrade Instruction: [[Upgrade Firmware>>path:#H5.1200BHowtoUpgradeFirmware]] 541 541 464 +== 2.12 Battery Analysis == 542 542 543 - Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/qdc3js2iu1vlipx/AACMHI3CvVb8g7YQMrIHY673a?dl=0>>https://www.dropbox.com/sh/qdc3js2iu1vlipx/AACMHI3CvVb8g7YQMrIHY673a?dl=0]]466 +**2.12.1 Battery Type** 544 544 545 - UpgradeInstruction:[[UpgradeFirmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]468 +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. 546 546 470 +The battery is designed to last for several years depends on the actually use environment and update interval. 547 547 548 - ==2.12 Battery& PowerConsumption==472 +The battery related documents as below: 549 549 474 +* [[Battery Dimension>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 475 +* [[Lithium-Thionyl Chloride Battery datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 476 +* [[Lithium-ion Battery-Capacitor datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 550 550 551 - NLMS01 uses ER26500+ SPC1520 battery pack.See below linkfor detail information about the battery info and how to replace.478 +[[image:image-20220907171221-21.png]] 552 552 553 - [[**BatteryInfo &PowerConsumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] .480 +**2.12.2 Power consumption Analyze** 554 554 482 +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 556 - = 3. Access NB-IoTModule=484 +Instruction to use as below: 557 557 486 +**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 - UserscandirectlyaccesstheAT commandset of the NB-IoT module.488 +**Step 2: ** Open it and choose 560 560 561 -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/]] 490 +* Product Model 491 +* Uplink Interval 492 +* Working Mode 562 562 494 +And the Life expectation in difference case will be shown on the right. 563 563 564 -[[image:image-20220907171221-2 3.png]] 496 +[[image:image-20220907171221-22.jpeg]] 565 565 498 +**2.12.3 Battery Note** 566 566 567 - =4.Using theATCommands=500 +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 569 - == 4.1AccessATCommands ==502 +**2.12.4 Replace the battery** 570 570 504 +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 - Seethislinkfor detail: [[https:~~/~~/www.dropbox.com/sh/351dwor6joz8nwh/AADn1BQaAAxLF_QMyU8NkW47a?dl=0>>url:https://www.dropbox.com/sh/351dwor6joz8nwh/AADn1BQaAAxLF_QMyU8NkW47a?dl=0]]506 += 3. Access NB-IoT Module = 573 573 574 -AT +<CMD>?:Helpon<CMD>508 +Users can directly access the AT command set of the NB-IoT module. 575 575 576 -AT +<CMD>:Run<CMD>510 +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>=<value>:Set the value512 +[[image:image-20220907171221-23.png]] 579 579 580 - AT+<CMD>=?:Getthevalue514 += 4. Using the AT Commands = 581 581 516 +**4.1 Access AT Commands** 582 582 583 - (%style="color:#037691" %)**GeneralCommands**518 +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 :Attention520 +AT+<CMD>? : Help on <CMD> 586 586 587 -AT ?:Short Help522 +AT+<CMD> : Run <CMD> 588 588 589 -AT Z:MCUReset524 +AT+<CMD>=<value> : Set the value 590 590 591 -AT+ TDC:ApplicationDataTransmissionInterval526 +AT+<CMD>=? : Get the value 592 592 593 - AT+CFG: Printallconfigurations528 +**General Commands** 594 594 595 -AT +CFGMOD:Workingmodeselection530 +AT : Attention 596 596 597 -AT +INTMOD:Setthetriggerinterruptmode532 +AT? : Short Help 598 598 599 -AT +5VT:Setextendthetimeof5Vpower534 +ATZ : MCU Reset 600 600 601 -AT+ PRO :Chooseagreement536 +AT+TDC : Application Data Transmission Interval 602 602 603 -AT+ RXDL:Extendthesendingandreceivingme538 +AT+CFG : Print all configurations 604 604 605 -AT+ SERVADDR:ServerAddress540 +AT+CFGMOD : Working mode selection 606 606 607 -AT+ APN :Getor set theAPN542 +AT+INTMOD : Set the trigger interrupt mode 608 608 609 -AT+ FBAND :GetorSetwhethertoautomaticallymodifythefrequencyband544 +AT+5VT : Set extend the time of 5V power 610 610 611 -AT+ DNSCFG:GetorSetDNSServer546 +AT+PRO : Choose agreement 612 612 613 -AT+ GETSENSORVALUEReturnsthecurrentsensormeasurement548 +AT+RXDL : Extend the sending and receiving time 614 614 615 -AT+ TR:Get orSetrecordtime"550 +AT+SERVADDR : Server Address 616 616 617 -AT+ NOUD:the numberfdatato beuploaded552 +AT+TR : Get or Set record time" 618 618 619 -AT+CDP : Read or Clear cached data 620 620 621 -AT+ TEMPALARM:alarm of temp555 +AT+NOUD : Get or Set the number of data to be uploaded 622 622 623 -AT+HUMALARM : Get or Set alarm of humidity 624 624 558 +AT+CDP : Read or Clear cached data 625 625 626 -(% style="color:#037691" %)**COAP Management** 627 627 628 -AT+ URI:Resourceparameters561 +AT+TEMPALARM : Get or Set alarm of temp 629 629 563 +AT+HUMALARM : Get or Set alarm of PH 630 630 631 -(% style="color:#037691" %)**UDP Management** 632 632 633 - AT+CFM: Upload confirmationmode(onlyvalid for UDP)566 +**COAP Management** 634 634 568 +AT+URI : Resource parameters 635 635 636 - (% style="color:#037691" %)**MQTTManagement**570 +**UDP Management** 637 637 638 -AT+C LIENT:GetorSetMQTTclient572 +AT+CFM : Upload confirmation mode (only valid for UDP) 639 639 640 - AT+UNAME : Get or Set MQTTUsername574 +**MQTT Management** 641 641 642 -AT+ PWDpassword576 +AT+CLIENT : Get or Set MQTT client 643 643 644 -AT+ PUBTOPIC:Get or Set MQTTpublish topic578 +AT+UNAME : Get or Set MQTT Username 645 645 646 -AT+ SUBTOPIC:ubscription topic580 +AT+PWD : Get or Set MQTT password 647 647 582 +AT+PUBTOPIC : Get or Set MQTT publish topic 648 648 649 - (%style="color:#037691"%)**Information**584 +AT+SUBTOPIC : Get or Set MQTT subscription topic 650 650 651 - AT+FDR : Factory DataReset586 +**Information** 652 652 653 -AT+ PWORD:SerialAccessPassword588 +AT+FDR : Factory Data Reset 654 654 590 +AT+PWORD : Serial Access Password 655 655 656 656 = 5. FAQ = 657 657 658 - ==5.1 How to Upgrade Firmware==594 +**5.1 How to Upgrade Firmware** 659 659 660 - 661 661 User can upgrade the firmware for 1) bug fix, 2) new feature release. 662 662 663 663 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]] 664 664 600 +**Notice, **NLMS01 **and **NLMS01 **share the same mother board. They use the same connection and method to update.** 665 665 666 -(% style="color:red" %)**Notice, NLMS01 and LLMS01 share the same mother board. They use the same connection and method to update.** 667 - 668 - 669 669 = 6. Trouble Shooting = 670 670 671 - ==6.1 Connection problem when uploading firmware==604 +**6.1 Connection problem when uploading firmware** 672 672 673 - 674 674 **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]] 675 675 608 +**6.2 AT Command input doesn't work** 676 676 677 - ==6.2ATCommand input doesn't work==610 +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. 678 678 679 - 680 -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. 681 - 682 - 683 -== 6.3 Not able to connect to NB-IoT network and keep showing "Signal Strength:99". == 684 - 685 - 686 -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]]//**. 687 - 688 - 689 689 = 7. Order Info = 690 690 691 - 692 692 Part Number**:** NLMS01 693 693 694 - 695 695 = 8. Packing Info = 696 696 618 +**Package Includes**: 697 697 698 -(% style="color:#037691" %)**Package Includes:** 699 - 700 700 * NLMS01 NB-IoT Leaf Moisture Sensor x 1 701 701 702 - (% style="color:#037691" %)**Dimension and weight**:622 +**Dimension and weight**: 703 703 704 704 * Device Size: cm 705 705 * Device Weight: g ... ... @@ -706,11 +706,11 @@ 706 706 * Package Size / pcs : cm 707 707 * Weight / pcs : g 708 708 709 - 710 710 = 9. Support = 711 711 712 - 713 713 * 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. 714 714 * 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]] 715 715 716 716 635 + 636 +
- 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