Skip to Content
Last modified by Mengting Qiu on 2024/04/02 16:44
From version 71.1
edited by Xiaoling
on 2022/07/09 08:42
Change comment: There is no comment for this version
To version 115.5
edited by Xiaoling
on 2022/07/09 17:18
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -NDDS75 NB-IoT Distance Detect Sensor User Manual
1 +N95S31B NB-IoT Temperature & Humidity Sensor User Manual
Content
... ... @@ -1,4 +1,5 @@
1 -[[image:image-20220709084207-3.jpeg||height="548" width="548"]]
1 +(% style="text-align:center" %)
2 +[[image:1657348034241-728.png||height="470" width="470"]]
2 2  
3 3  
4 4  
... ... @@ -13,39 +13,35 @@
13 13  
14 14  
15 15  
16 -
17 17  = 1.  Introduction =
18 18  
19 -== 1.1 ​ What is NDDS75 Distance Detection Sensor ==
19 +== 1.1 ​ What is N95S31B NB-IoT Sensor Node ==
20 20  
21 21  (((
22 22  
23 23  
24 -(((
25 -The Dragino NDDS75 is a (% style="color:blue" %)**NB-IoT Distance Detection Sensor**(%%) for Internet of Things solution. It is designed to measure the distance between the sensor and a flat object. The distance detection sensor is a module that uses ultrasonic sensing technology for distance measurement, and temperature compensation is performed internally to improve the reliability of data.
26 -\\The NDDS75 can be applied to scenarios such as horizontal distance measurement, liquid level measurement, parking management system, object proximity and presence detection, intelligent trash can management system, robot obstacle avoidance, automatic control, sewer, bottom water level monitoring, etc. It detects the distance between the measured object and the sensor, and uploads the value via wireless to IoT Server via NB-IoT Network.
27 -\\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.
28 -\\NDDS75 supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP** (%%)for different application requirement.
29 -\\NDDS75 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)
30 -\\To use NDDS75, user needs to check if there is NB-IoT coverage in local area and with the bands NDDS75 supports. If the local operate support it, user needs to get a NB-IoT SIM card from local operator and install NDDS75 to get NB-IoT network connection.
31 -)))
24 +The Dragino N95S31B is a (% style="color:blue" %)**NB-IoT Temperature and Humidity Sensor**(%%) for Internet of Things solution. It is used to measure the (% style="color:blue" %)**surrounding environment temperature and relative air humidity precisely**(%%), and then upload to IoT server via NB-IoT network*.
32 32  
33 -
34 -)))
26 +The temperature & humidity sensor used in N95S31B is SHT31, which is fully calibrated, linearized, and temperature compensated digital output from Sensirion, it provides a strong reliability and long-term stability. The SHT31 is fixed in a (% style="color:blue" %)**waterproof anti-condensation casing **(%%)for long term use.
35 35  
36 -[[image:1654503236291-817.png]]
28 +N95S31B supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP**(%%) for different application requirement.
37 37  
30 +N95S31B is powered by(% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), It is designed for long term use up to several years. (Real-world battery life depends on the use environment, update period. Please check related Power Analyze report).
38 38  
39 -[[image:1657245163077-232.png]]
40 40  
33 +~* make sure you have NB-IoT coverage locally.
41 41  
35 +
36 +)))
42 42  
38 +[[image:1657348284168-431.png]]
39 +
40 +
41 +
43 43  == 1.2 ​ Features ==
44 44  
45 45  * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
46 -* Monitor Soil Moisture
47 -* Monitor Soil Temperature
48 -* Monitor Soil Conductivity
45 +* Monitor Temperature & Humidity via SHT31
49 49  * AT Commands to change parameters
50 50  * Uplink on periodically
51 51  * Downlink to change configure
... ... @@ -55,6 +55,9 @@
55 55  * Micro SIM card slot for NB-IoT SIM
56 56  * 8500mAh Battery for long term use
57 57  
55 +
56 +
57 +
58 58  == 1.3  Specification ==
59 59  
60 60  
... ... @@ -72,75 +72,130 @@
72 72  * - B20 @H-FDD: 800MHz
73 73  * - B28 @H-FDD: 700MHz
74 74  
75 -Probe(% style="color:#037691" %)** Specification:**
75 +(% style="color:#037691" %)**Battery:**
76 76  
77 -Measure Volume: Base on the centra pin of the probe, a cylinder with 7cm diameter and 10cm height.
78 78  
79 -[[image:image-20220708101224-1.png]]
78 +* Li/SOCI2 un-chargeable battery
79 +* Capacity: 8500mAh
80 +* Self Discharge: <1% / Year @ 25°C
81 +* Max continuously current: 130mA
82 +* Max boost current: 2A, 1 second
80 80  
81 81  
82 82  
86 +
83 83  == ​1.4  Applications ==
84 84  
89 +* Smart Buildings & Home Automation
90 +* Logistics and Supply Chain Management
91 +* Smart Metering
85 85  * Smart Agriculture
93 +* Smart Cities
94 +* Smart Factory
86 86  
87 87  (% class="wikigeneratedid" id="H200B1.5FirmwareChangelog" %)
88 88  ​
89 89  
99 +
90 90  == 1.5  Pin Definitions ==
91 91  
102 +N95S31B use the mother board from NBSN95 which as below.
92 92  
93 -[[image:1657246476176-652.png]]
104 +[[image:image-20220709144723-1.png]]
94 94  
95 95  
107 +=== 1.5.1 Jumper JP2 ===
96 96  
97 -= 2.  Use NSE01 to communicate with IoT Server =
109 +Power on Device when put this jumper.
98 98  
111 +
112 +
113 +=== 1.5.2 BOOT MODE / SW1 ===
114 +
115 +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.
116 +
117 +2) Flash: work mode, device starts to work and send out console output for further debug
118 +
119 +
120 +
121 +=== 1.5.3 Reset Button ===
122 +
123 +Press to reboot the device.
124 +
125 +
126 +
127 +=== 1.5.4 LED ===
128 +
129 +It will flash:
130 +
131 +1. When boot the device in flash mode
132 +1. Send an uplink packet
133 +
134 +
135 += 2.  Use N95S31B to communicate with IoT Server =
136 +
99 99  == 2.1  How it works ==
100 100  
101 101  
102 102  (((
103 -The NSE01 is equipped with a NB-IoT module, the pre-loaded firmware in NSE01 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 NSE01.
141 +The N95S31B is equipped with a NB-IoT module, the pre-loaded firmware in N95S31B 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 N95S31B.
104 104  )))
105 105  
106 106  
107 107  (((
108 -The diagram below shows the working flow in default firmware of NSE01:
146 +The diagram below shows the working flow in default firmware of N95S31B:
109 109  )))
110 110  
111 -[[image:image-20220708101605-2.png]]
149 +(((
150 +
151 +)))
112 112  
153 +[[image:1657350248151-650.png]]
154 +
113 113  (((
114 114  
115 115  )))
116 116  
117 117  
160 +== 2.2 ​ Configure the N95S31B ==
118 118  
119 -== 2.2 ​ Configure the NSE01 ==
120 120  
163 +=== 2.2.1  Power On N95S31B ===
121 121  
165 +
166 +[[image:image-20220709150546-2.png]]
167 +
168 +
122 122  === 2.2.1 Test Requirement ===
123 123  
124 124  
125 -(((
126 -To use NSE01 in your city, make sure meet below requirements:
127 -)))
172 +To use N95S31B in your city, make sure meet below requirements:
128 128  
129 129  * Your local operator has already distributed a NB-IoT Network there.
130 -* The local NB-IoT network used the band that NSE01 supports.
175 +* The local NB-IoT network used the band that N95S31B supports.
131 131  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
132 132  
178 +Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.
179 +
180 +N95S31B supports different communication protocol such as :
181 +
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 NSE01 will use CoAP((% style="color:red" %)120.24.4.116:5683)(%%) or raw UDP((% style="color:red" %)120.24.4.116:5601)(%%) or MQTT((% style="color:red" %)120.24.4.116:1883)(%%)or TCP((% style="color:red" %)120.24.4.116:5600)(%%)protocol to send data to the test server
135 -)))
183 +* CoAP  ((% style="color:red" %)120.24.4.116:5683(%%))
184 +* raw UDP  ((% style="color:red" %)120.24.4.116:5601(%%))
185 +* MQTT  ((% style="color:red" %)120.24.4.116:1883(%%))
186 +* TCP  ((% style="color:red" %)120.24.4.116:5600(%%))
136 136  
188 +We will show how to use with each protocol. The IP addresses above are our test server. User need to change to point their corresponding server.
137 137  
138 -[[image:1657249419225-449.png]]
190 +
191 +)))
139 139  
193 +[[image:1657350625843-586.png]]
140 140  
141 141  
142 -=== 2.2.2 Insert SIM card ===
143 143  
197 +=== 2.2.3  Insert SIM card ===
198 +
144 144  (((
145 145  Insert the NB-IoT Card get from your provider.
146 146  )))
... ... @@ -150,18 +150,19 @@
150 150  )))
151 151  
152 152  
153 -[[image:1657249468462-536.png]]
208 +[[image:1657351240556-536.png]]
154 154  
155 155  
156 156  
157 -=== 2.2.3 Connect USB – TTL to NSE01 to configure it ===
212 +=== 2.2.4  Connect USB – TTL to N95S31B to configure it ===
158 158  
159 159  (((
160 160  (((
161 -User need to configure NSE01 via serial port to set the (% style="color:blue" %)**Server Address** / **Uplink Topic** (%%)to define where and how-to uplink packets. NSE01 support AT Commands, user can use a USB to TTL adapter to connect to NSE01 and use AT Commands to configure it, as below.
216 +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.
162 162  )))
163 163  )))
164 164  
220 +[[image:1657351312545-300.png]]
165 165  
166 166  **Connection:**
167 167  
... ... @@ -181,96 +181,110 @@
181 181  * Flow Control: (% style="color:green" %)**None**
182 182  
183 183  (((
184 -Make sure the switch is in FLASH position, then power on device by connecting the jumper on NSE01. NSE01 will output system info once power on as below, we can enter the (% style="color:green" %)**password: 12345678**(%%) to access AT Command input.
240 +Make sure the switch is in FLASH position, then power on device by connecting the jumper on N95S31B. N95S31B will output system info once power on as below, we can enter the (% style="color:green" %)**password: 12345678**(%%) to access AT Command input.
185 185  )))
186 186  
187 -[[image:image-20220708110657-3.png]]
243 +[[image:1657329814315-101.png]]
188 188  
189 189  (((
190 -(% style="color:red" %)Note: the valid AT Commands can be found at: (%%)[[http:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NSE01/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/]]
246 +(% 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/]]
191 191  )))
192 192  
193 193  
194 194  
195 -=== 2.2.4 Use CoAP protocol to uplink data ===
251 +=== 2.2.5  Use CoAP protocol to uplink data ===
196 196  
197 197  (% 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/]]
198 198  
199 199  
256 +(((
200 200  **Use below commands:**
258 +)))
201 201  
202 -* (% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
203 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
204 -* (% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
260 +* (((
261 +(% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
262 +)))
263 +* (((
264 +(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
265 +)))
266 +* (((
267 +(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
268 +)))
205 205  
270 +(((
271 +
272 +
206 206  For parameter description, please refer to AT command set
274 +)))
207 207  
208 -[[image:1657249793983-486.png]]
276 +[[image:1657352146020-183.png]]
209 209  
210 210  
211 -After configure the server address and (% style="color:green" %)**reset the device**(%%) (via AT+ATZ ), NSE01 will start to uplink sensor values to CoAP server.
279 +(((
280 +After configure the server address and (% style="color:green" %)**reset the device**(%%) (via AT+ATZ ), NDDS75 will start to uplink sensor values to CoAP server.
281 +)))
212 212  
213 -[[image:1657249831934-534.png]]
283 +[[image:1657352185396-303.png]]
214 214  
215 215  
216 216  
217 -=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
287 +=== 2.2.6  Use UDP protocol to uplink data(Default protocol) ===
218 218  
219 -This feature is supported since firmware version v1.0.1
220 220  
221 -
222 -* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
290 +* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
223 223  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
224 -* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/If the server does not respond, this command is unnecessary
292 +* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/ If the server does not respond, this command is unnecessary
225 225  
226 -[[image:1657249864775-321.png]]
294 +[[image:1657352391268-297.png]]
227 227  
228 228  
229 -[[image:1657249930215-289.png]]
297 +[[image:1657352403317-397.png]]
230 230  
231 231  
232 232  
233 -=== 2.2.6 Use MQTT protocol to uplink data ===
301 +=== 2.2.7  Use MQTT protocol to uplink data ===
234 234  
235 -This feature is supported since firmware version v110
303 +N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption.
236 236  
305 +* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
306 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
307 +* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
308 +* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
309 +* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password of MQTT
310 +* (% style="color:blue" %)**AT+PUBTOPIC=f9527                               **(%%)~/~/Set the sending topic of MQTT
311 +* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527          **(%%) ~/~/Set the subscription topic of MQTT
237 237  
238 -* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
239 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
240 -* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
241 -* (% style="color:blue" %)**AT+UNAME=UNAME                               **(%%)~/~/Set the username of MQTT
242 -* (% style="color:blue" %)**AT+PWD=PWD                                        **(%%)~/~/Set the password of MQTT
243 -* (% style="color:blue" %)**AT+PUBTOPIC=NSE01_PUB                    **(%%)~/~/Set the sending topic of MQTT
244 -* (% style="color:blue" %)**AT+SUBTOPIC=NSE01_SUB          **(%%) ~/~/Set the subscription topic of MQTT
313 +[[image:1657352634421-276.png]]
245 245  
246 -[[image:1657249978444-674.png]]
247 247  
316 +[[image:1657352645687-385.png]]
248 248  
249 -[[image:1657249990869-686.png]]
318 +(((
319 +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.
320 +)))
250 250  
251 251  
252 252  (((
253 -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.
324 +MQTT protocol has a much high-power consumption compare vs UDP / CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval.
254 254  )))
255 255  
256 256  
257 257  
258 -=== 2.2.7 Use TCP protocol to uplink data ===
329 +=== 2.2.8  Use TCP protocol to uplink data ===
259 259  
260 260  This feature is supported since firmware version v110
261 261  
262 -
263 263  * (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
264 264  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
265 265  
266 -[[image:1657250217799-140.png]]
336 +[[image:1657352898400-901.png]]
267 267  
268 268  
269 -[[image:1657250255956-604.png]]
339 +[[image:1657352914475-252.png]]
270 270  
271 271  
272 272  
273 -=== 2.2.8 Change Update Interval ===
343 +=== 2.2.9  Change Update Interval ===
274 274  
275 275  User can use below command to change the (% style="color:green" %)**uplink interval**.
276 276  
... ... @@ -277,260 +277,199 @@
277 277  * (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
278 278  
279 279  (((
280 -(% style="color:red" %)**NOTE:**
350 +
281 281  )))
282 282  
283 -(((
284 -(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
285 -)))
286 286  
287 287  
288 -
289 289  == 2.3  Uplink Payload ==
290 290  
291 -In this mode, uplink payload includes in total 18 bytes
292 292  
293 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)
294 -|=(% style="width: 60px;" %)(((
295 -**Size(bytes)**
296 -)))|=(% style="width: 50px;" %)**6**|=(% style="width: 25px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 70px;" %)**1**|=(% style="width: 60px;" %)**2**|=(% style="width: 80px;" %)**2**|=(% style="width: 90px;" %)**2**|=(% style="width: 50px;" %)**1**
297 -|(% style="width:97px" %)**Value**|(% style="width:83px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:41px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:123px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:108px" %)[[Soil Moisture>>||anchor="H2.4.5A0SoilMoisture"]]|(% style="width:133px" %)[[Soil Temperature>>||anchor="H2.4.6A0SoilTemperature"]]|(% style="width:159px" %)[[Soil Conductivity(EC)>>||anchor="H2.4.7A0SoilConductivity28EC29"]]|(% style="width:80px" %)[[Interrupt>>||anchor="H2.4.8A0DigitalInterrupt"]]
358 +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.
298 298  
299 -(((
300 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NSE01 uplink data.
301 -)))
302 302  
361 +For example:
303 303  
304 -[[image:image-20220708111918-4.png]]
363 + (% 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.
305 305  
306 306  
307 -The payload is ASCII string, representative same HEX:
366 +The uplink payloads are composed in  ASCII String. For example:
308 308  
309 -0x72403155615900640c7817075e0a8c02f900 where:
368 +0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:
310 310  
311 -* Device ID: 0x 724031556159 = 724031556159
312 -* Version: 0x0064=100=1.0.0
370 +0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes
313 313  
314 -* BAT: 0x0c78 = 3192 mV = 3.192V
315 -* Singal: 0x17 = 23
316 -* Soil Moisture: 0x075e= 1886 = 18.86  %
317 -* Soil Temperature:0x0a8c =2700=27 °C
318 -* Soil Conductivity(EC) = 0x02f9 =761 uS /cm
319 -* Interrupt: 0x00 = 0
320 320  
321 -== 2.4  Payload Explanation and Sensor Interface ==
373 +(% style="color:red" %)**NOTE:**
322 322  
375 +(% style="color:red" %)
376 +1. All modes share the same Payload Explanation from [[HERE>>path:#Payload_Explain]].
377 +1. By default, the device will send an uplink message every 1 hour.
323 323  
324 -=== 2.4.1  Device ID ===
325 325  
326 -(((
327 -By default, the Device ID equal to the last 6 bytes of IMEI.
328 -)))
329 329  
330 -(((
331 -User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
332 -)))
381 +=== 2.3.1  Payload Analyze ===
333 333  
334 -(((
335 -**Example:**
336 -)))
383 +N95S31B uplink payload includes in total 21 bytes
337 337  
338 -(((
339 -AT+DEUI=A84041F15612
340 -)))
341 341  
342 -(((
343 -The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID.
344 -)))
386 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
387 +|=(% style="width: 60px;" %)(((
388 +**Size(bytes)**
389 +)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 80px;" %) |=(% style="width: 99px;" %) |=(% style="width: 77px;" %)**2**|=(% style="width: 60px;" %)**1**
390 +|(% style="width:97px" %)**Value**|(% style="width:83px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:41px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:123px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:123px" %)MOD 0X01|(% style="width:99px" %)(((
391 +Reserve/ Same as NBSN95 CFGMOD=1
345 345  
393 +No function here.
394 +)))|(% style="width:77px" %)(((
395 +[[Temperature >>||anchor="H2.4.5A0Distance"]]
346 346  
397 +By SHT31
398 +)))|(% style="width:80px" %)(((
399 +[[Humidity>>||anchor="H2.4.6A0DigitalInterrupt"]]
347 347  
348 -=== 2.4.2  Version Info ===
349 -
350 -(((
351 -Specify the software version: 0x64=100, means firmware version 1.00.
401 +By SHT31
352 352  )))
353 353  
354 354  (((
355 -For example: 0x00 64 : this device is NSE01 with firmware version 1.0.0.
356 -)))
357 -
358 -
359 -
360 -=== 2.4.3  Battery Info ===
361 -
362 362  (((
363 -Check the battery voltage for LSE01.
406 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
364 364  )))
365 -
366 -(((
367 -Ex1: 0x0B45 = 2885mV
368 368  )))
369 369  
370 -(((
371 -Ex2: 0x0B49 = 2889mV
372 -)))
373 373  
411 +[[image:1657354294009-643.png]]
374 374  
375 375  
376 -=== 2.4.4  Signal Strength ===
414 +The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where:
377 377  
378 -(((
379 -NB-IoT Network signal Strength.
380 -)))
416 +* Device ID: 0x724031607457 = 724031607457
417 +* Version: 0x006e=110=1.1.0
381 381  
382 -(((
383 -**Ex1: 0x1d = 29**
384 -)))
419 +* BAT: 0x0ccd = 3277 mV = 3.277V
420 +* Signal: 0x1b = 27
421 +* Model: 0x01 = 1
422 +* 0x00dc000ccc= reserve, ignore in N95S31B
423 +* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C
424 +* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh
385 385  
386 386  (((
387 -(% style="color:blue" %)**0**(%%)  -113dBm or less
427 +
388 388  )))
389 389  
390 390  (((
391 -(% style="color:blue" %)**1**(%%)  -111dBm
431 +
392 392  )))
393 393  
394 -(((
395 -(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
396 -)))
397 397  
398 -(((
399 -(% style="color:blue" %)**31**  (%%) -51dBm or greater
400 -)))
435 +=== 2.3.2  Device ID ===
401 401  
402 402  (((
403 -(% style="color:blue" %)**99**   (%%) Not known or not detectable
438 +By default, the Device ID equal to the last 6 bytes of IMEI.
404 404  )))
405 405  
406 -
407 -
408 -=== 2.4.5  Soil Moisture ===
409 -
410 410  (((
411 -(((
412 -Get the moisture content of the soil. The value range of the register is 0-10000(Decimal), divide this value by 100 to get the percentage of moisture in the soil.
442 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
413 413  )))
414 -)))
415 415  
416 416  (((
417 -(((
418 -For example, if the data you get from the register is **__0x05 0xDC__**, the moisture content in the soil is
446 +**Example:**
419 419  )))
420 -)))
421 421  
422 422  (((
423 -
450 +AT+DEUI=A84041F15612
424 424  )))
425 425  
426 426  (((
427 -(% style="color:#4f81bd" %)**05DC(H) = 1500(D) /100 = 15%.**
454 +The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
428 428  )))
429 429  
430 430  
431 431  
432 -=== 2.4.6  Soil Temperature ===
459 +=== 2.3.3  Version Info ===
433 433  
434 -(((
435 -Get the temperature in the soil. The value range of the register is -4000 - +800(Decimal), divide this value by 100 to get the temperature in the soil. For example, if the data you get from the register is __**0x09 0xEC**__, the temperature content in the soil is
436 -)))
437 437  
438 -(((
439 -**Example**:
440 -)))
462 +These bytes include the hardware and software version.
441 441  
442 -(((
443 -If payload is 0105H: ((0x0105 & 0x8000)>>15 === 0),temp = 0105(H)/100 = 2.61 °C
444 -)))
464 +Higher byte: Specify hardware version: always 0x00 for N95S31B
445 445  
446 -(((
447 -If payload is FF7EH: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/100 = -1.29 °C
448 -)))
466 +Lower byte: Specify the software version: 0x6E=110, means firmware version 110
449 449  
450 450  
469 +For example: 0x00 6E: this device is N95S31B with firmware version 110.
451 451  
452 -=== 2.4.7  Soil Conductivity (EC) ===
453 -
454 454  (((
455 -Obtain (% style="color:#4f81bd" %)**__soluble salt concentration__**(%%) in soil or (% style="color:#4f81bd" %)**__soluble ion concentration in liquid fertilizer__**(%%) or (% style="color:#4f81bd" %)**__planting medium__**(%%). The value range of the register is 0 - 20000(Decimal)( Can be greater than 20000).
472 +
456 456  )))
457 457  
458 -(((
459 -For example, if the data you get from the register is __**0x00 0xC8**__, the soil conductivity is 00C8(H) = 200(D) = 200 uS/cm.
460 -)))
461 461  
462 -(((
463 -Generally, the EC value of irrigation water is less than 800uS / cm.
464 -)))
476 +=== 2.3.4  Battery Info ===
465 465  
466 466  (((
467 -
479 +Ex1: 0x0B45 = 2885mV
468 468  )))
469 469  
470 470  (((
471 -
483 +Ex2: 0x0B49 = 2889mV
472 472  )))
473 473  
474 -=== 2.4.8  Digital Interrupt ===
475 475  
487 +
488 +=== 2.3.5  Signal Strength ===
489 +
476 476  (((
477 -Digital Interrupt refers to pin (% style="color:blue" %)**GPIO_EXTI**(%%), and there are different trigger methods. When there is a trigger, the NSE01 will send a packet to the server.
491 +NB-IoT Network signal Strength.
478 478  )))
479 479  
480 480  (((
481 -The command is:
495 +**Ex1: 0x1d = 29**
482 482  )))
483 483  
484 484  (((
485 -(% style="color:blue" %)**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]])**.**
499 +(% style="color:blue" %)**0**(%%)  -113dBm or less
486 486  )))
487 487  
488 -
489 489  (((
490 -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.
503 +(% style="color:blue" %)**1**(%%)  -111dBm
491 491  )))
492 492  
493 -
494 494  (((
495 -Example:
507 +(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
496 496  )))
497 497  
498 498  (((
499 -0x(00): Normal uplink packet.
511 +(% style="color:blue" %)**31**  (%%) -51dBm or greater
500 500  )))
501 501  
502 502  (((
503 -0x(01): Interrupt Uplink Packet.
515 +(% style="color:blue" %)**99**   (%%) Not known or not detectable
504 504  )))
505 505  
506 506  
507 507  
508 -=== 2.4.9  ​+5V Output ===
520 +=== 2.3.6  Temperature & Humidity ===
509 509  
510 -(((
511 -NSE01 will enable +5V output before all sampling and disable the +5v after all sampling. 
512 -)))
522 +The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server.
513 513  
524 +[[image:image-20220709161741-3.png]]
514 514  
515 -(((
516 -The 5V output time can be controlled by AT Command.
517 -)))
518 518  
519 -(((
520 -(% style="color:blue" %)**AT+5VT=1000**
521 -)))
527 +Convert the read byte to decimal and divide it by ten.
522 522  
523 -(((
524 -Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.
525 -)))
526 526  
530 +**Example:**
527 527  
532 +Temperature:  Read:00ec (H) = 236(D)  Value:  236 /10=23.6℃
528 528  
534 +Humidity:    Read:0295(H)=661(D)    Value:  661 / 10=66.1, So 66.1%
535 +
536 +
537 +
529 529  == 2.5  Downlink Payload ==
530 530  
531 -By default, NSE01 prints the downlink payload to console port.
540 +By default, NDDS75 prints the downlink payload to console port.
532 532  
533 -[[image:image-20220708133731-5.png]]
542 +[[image:image-20220709100028-1.png]]
534 534  
535 535  
536 536  (((
... ... @@ -566,7 +566,7 @@
566 566  )))
567 567  
568 568  (((
569 -If payload = 0x04FF, it will reset the NSE01
578 +If payload = 0x04FF, it will reset the NDDS75
570 570  )))
571 571  
572 572  
... ... @@ -578,78 +578,19 @@
578 578  
579 579  
580 580  
581 -== 2.6  ​LED Indicator ==
590 +== 2.5  ​Battery Analysis ==
582 582  
583 -(((
584 -The NSE01 has an internal LED which is to show the status of different state.
592 +=== 2.5.1  ​Battery Type ===
585 585  
586 586  
587 -* When power on, NSE01 will detect if sensor probe is connected, if probe detected, LED will blink four times. (no blinks in this step is no probe)
588 -* Then the LED will be on for 1 second means device is boot normally.
589 -* After NSE01 join NB-IoT network. The LED will be ON for 3 seconds.
590 -* For each uplink probe, LED will be on for 500ms.
591 -)))
592 -
593 -
594 -
595 -
596 -== 2.7  Installation in Soil ==
597 -
598 -__**Measurement the soil surface**__
599 -
600 600  (((
601 -Choose the proper measuring position. Avoid the probe to touch rocks or hard things. Split the surface soil according to the measured deep. Keep the measured as original density. Vertical insert the probe into the soil to be measured. Make sure not shake when inserting. [[https:~~/~~/img.alicdn.com/imgextra/i3/2005165265/O1CN010rj9Oh1olPsQxrdUK_!!2005165265.jpg>>url:https://img.alicdn.com/imgextra/i3/2005165265/O1CN010rj9Oh1olPsQxrdUK_!!2005165265.jpg]]
596 +The NDDS75 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.
602 602  )))
603 603  
604 -[[image:1657259653666-883.png]] ​
605 -
606 -
607 607  (((
608 -
609 -
610 -(((
611 -Dig a hole with diameter > 20CM.
612 -)))
613 -
614 -(((
615 -Horizontal insert the probe to the soil and fill the hole for long term measurement.
616 -)))
617 -)))
618 -
619 -[[image:1654506665940-119.png]]
620 -
621 -(((
622 -
623 -)))
624 -
625 -
626 -== 2.8  ​Firmware Change Log ==
627 -
628 -
629 -Download URL & Firmware Change log
630 -
631 -[[www.dragino.com/downloads/index.php?dir=NB-IoT/NSE01/Firmware/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/Firmware/]]
632 -
633 -
634 -Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
635 -
636 -
637 -
638 -== 2.9  ​Battery Analysis ==
639 -
640 -=== 2.9.1  ​Battery Type ===
641 -
642 -
643 -(((
644 -The NSE01 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.
645 -)))
646 -
647 -
648 -(((
649 649  The battery is designed to last for several years depends on the actually use environment and update interval. 
650 650  )))
651 651  
652 -
653 653  (((
654 654  The battery related documents as below:
655 655  )))
... ... @@ -659,12 +659,12 @@
659 659  * [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
660 660  
661 661  (((
662 -[[image:image-20220708140453-6.png]]
612 +[[image:image-20220709101450-2.png]]
663 663  )))
664 664  
665 665  
666 666  
667 -=== 2.9.2  Power consumption Analyze ===
617 +=== 2.8.2  Power consumption Analyze ===
668 668  
669 669  (((
670 670  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.
... ... @@ -698,11 +698,11 @@
698 698  And the Life expectation in difference case will be shown on the right.
699 699  )))
700 700  
701 -[[image:image-20220708141352-7.jpeg]]
651 +[[image:image-20220709110451-3.png]]
702 702  
703 703  
704 704  
705 -=== 2.9.3  ​Battery Note ===
655 +=== 2.8.3  ​Battery Note ===
706 706  
707 707  (((
708 708  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.
... ... @@ -710,10 +710,10 @@
710 710  
711 711  
712 712  
713 -=== 2.9.4  Replace the battery ===
663 +=== 2.8.4  Replace the battery ===
714 714  
715 715  (((
716 -The default battery pack of NSE01 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).
666 +The default battery pack of NDDS75 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).
717 717  )))
718 718  
719 719  
... ... @@ -728,7 +728,7 @@
728 728  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/]] 
729 729  )))
730 730  
731 -[[image:1657261278785-153.png]]
681 +[[image:1657333200519-600.png]]
732 732  
733 733  
734 734  
... ... @@ -736,7 +736,7 @@
736 736  
737 737  == 4.1  Access AT Commands ==
738 738  
739 -See this link for detail: [[http:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NSE01/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/]]
689 +See this link for detail: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/]]
740 740  
741 741  
742 742  AT+<CMD>?  : Help on <CMD>
... ... @@ -824,18 +824,11 @@
824 824  )))
825 825  
826 826  (((
827 -(% style="color:red" %)Notice, NSE01 and LSE01 share the same mother board. They use the same connection and method to update.
777 +(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.
828 828  )))
829 829  
830 830  
831 831  
832 -== 5.2  Can I calibrate NSE01 to different soil types? ==
833 -
834 -(((
835 -NSE01 is calibrated for saline-alkali soil and loamy soil. If users want to use it for other soil, they can calibrate the value in the IoT platform base on the value measured by saline-alkali soil and loamy soil. The formula can be found at [[this link>>https://www.dragino.com/downloads/downloads/LoRa_End_Node/LSE01/Calibrate_to_other_Soil_20220605.pdf]].
836 -)))
837 -
838 -
839 839  = 6.  Trouble Shooting =
840 840  
841 841  == 6.1  ​Connection problem when uploading firmware ==
... ... @@ -863,7 +863,7 @@
863 863  = 7. ​ Order Info =
864 864  
865 865  
866 -Part Number**:** (% style="color:#4f81bd" %)**NSE01**
809 +Part Number**:** (% style="color:#4f81bd" %)**NSDDS75**
867 867  
868 868  
869 869  (% class="wikigeneratedid" %)
... ... @@ -878,7 +878,7 @@
878 878  
879 879  (% style="color:#037691" %)**Package Includes**:
880 880  
881 -* NSE01 NB-IoT Soil Moisture & EC Sensor x 1
824 +* NSE01 NB-IoT Distance Detect Sensor Node x 1
882 882  * External antenna x 1
883 883  )))
884 884  
... ... @@ -887,8 +887,11 @@
887 887  
888 888  (% style="color:#037691" %)**Dimension and weight**:
889 889  
890 -* Size: 195 x 125 x 55 mm
891 -* Weight:   420g
833 +
834 +* Device Size: 13.0 x 5 x 4.5 cm
835 +* Device Weight: 150g
836 +* Package Size / pcs : 15 x 12x 5.5 cm
837 +* Weight / pcs : 220g
892 892  )))
893 893  
894 894  (((
1657327959271-447.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +78.3 KB
Content
1657328609906-564.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +492.6 KB
Content
1657328659945-416.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +78.8 KB
Content
1657328756309-230.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +78.5 KB
Content
1657328884227-504.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +483.6 KB
Content
1657329814315-101.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +85.3 KB
Content
1657330452568-615.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +71.3 KB
Content
1657330472797-498.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +68.9 KB
Content
1657330501006-241.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +119.2 KB
Content
1657330533775-472.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +74.9 KB
Content
1657330723006-866.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +74.1 KB
Content
1657331036973-987.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +83.8 KB
Content
1657332990863-496.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +138.2 KB
Content
1657333200519-600.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +126.1 KB
Content
1657348034241-728.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +127.8 KB
Content
1657348284168-431.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +93.5 KB
Content
1657350248151-650.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +126.1 KB
Content
1657350625843-586.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +93.3 KB
Content
1657351240556-536.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +483.6 KB
Content
1657351312545-300.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +675.8 KB
Content
1657352146020-183.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +264.0 KB
Content
1657352185396-303.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +98.3 KB
Content
1657352391268-297.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +238.0 KB
Content
1657352403317-397.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +547.7 KB
Content
1657352634421-276.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +163.6 KB
Content
1657352645687-385.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +214.7 KB
Content
1657352898400-901.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +144.8 KB
Content
1657352914475-252.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +157.0 KB
Content
1657354294009-643.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +214.7 KB
Content
image-20220709084458-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +199.5 KB
Content
image-20220709085040-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +200.4 KB
Content
image-20220709092052-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +247.3 KB
Content
image-20220709093918-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +42.2 KB
Content
image-20220709093918-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +61.9 KB
Content
image-20220709100028-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +8.8 KB
Content
image-20220709101450-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +138.5 KB
Content
image-20220709110451-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +611.5 KB
Content
image-20220709144723-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +413.1 KB
Content
image-20220709150546-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +333.5 KB
Content
image-20220709161741-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +111.2 KB
Content