Skip to Content
Last modified by Mengting Qiu on 2024/04/02 16:44
From version 77.2
edited by Xiaoling
on 2022/07/09 09:05
Change comment: There is no comment for this version
To version 115.2
edited by Xiaoling
on 2022/07/09 16: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,62 +1,59 @@
1 1  (% style="text-align:center" %)
2 -[[image:image-20220709085040-1.png||height="542" width="524"]]
2 +[[image:1657348034241-728.png||height="470" width="470"]]
3 3  
4 4  
5 5  
6 6  
7 7  
8 -**Table of Contents:**
9 9  
10 10  
10 +**Table of Contents:**
11 11  
12 12  
13 13  
14 14  
15 15  
16 +
16 16  = 1.  Introduction =
17 17  
18 -== 1.1 ​ What is NDDS75 Distance Detection Sensor ==
19 +== 1.1 ​ What is N95S31B NB-IoT Sensor Node ==
19 19  
20 20  (((
21 21  
22 22  
23 -(((
24 -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.
25 -\\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.
26 -\\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.
27 -\\NDDS75 supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP** (%%)for different application requirement.
28 -\\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)
29 -\\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.
30 -)))
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*.
31 31  
32 -
33 -)))
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.
34 34  
35 -[[image:1654503236291-817.png]]
28 +N95S31B supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP**(%%) for different application requirement.
36 36  
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).
37 37  
38 -[[image:1657327959271-447.png]]
39 39  
33 +~* make sure you have NB-IoT coverage locally.
40 40  
35 +
36 +)))
41 41  
38 +[[image:1657348284168-431.png]]
39 +
40 +
41 +
42 42  == 1.2 ​ Features ==
43 43  
44 44  
45 45  * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
46 -* Ultra low power consumption
47 -* Distance Detection by Ultrasonic technology
48 -* Flat object range 280mm - 7500mm
49 -* Accuracy: ±(1cm+S*0.3%) (S: Distance)
50 -* Cable Length: 25cm
46 +* Monitor Temperature & Humidity via SHT31
51 51  * AT Commands to change parameters
52 52  * Uplink on periodically
53 53  * Downlink to change configure
54 54  * IP66 Waterproof Enclosure
51 +* Ultra-Low Power consumption
52 +* AT Commands to change parameters
55 55  * Micro SIM card slot for NB-IoT SIM
56 56  * 8500mAh Battery for long term use
57 57  
58 58  
59 -
60 60  == 1.3  Specification ==
61 61  
62 62  
... ... @@ -74,9 +74,9 @@
74 74  * - B20 @H-FDD: 800MHz
75 75  * - B28 @H-FDD: 700MHz
76 76  
77 -
78 78  (% style="color:#037691" %)**Battery:**
79 79  
76 +
80 80  * Li/SOCI2 un-chargeable battery
81 81  * Capacity: 8500mAh
82 82  * Self Discharge: <1% / Year @ 25°C
... ... @@ -84,14 +84,6 @@
84 84  * Max boost current: 2A, 1 second
85 85  
86 86  
87 -(% style="color:#037691" %)**Power Consumption**
88 -
89 -* STOP Mode: 10uA @ 3.3v
90 -* Max transmit power: 350mA@3.3v
91 -
92 -
93 -
94 -
95 95  == ​1.4  Applications ==
96 96  
97 97  * Smart Buildings & Home Automation
... ... @@ -105,26 +105,54 @@
105 105  ​
106 106  
107 107  
108 -
109 109  == 1.5  Pin Definitions ==
110 110  
99 +N95S31B use the mother board from NBSN95 which as below.
111 111  
112 -[[image:1657328609906-564.png]]
101 +[[image:image-20220709144723-1.png]]
113 113  
114 114  
104 +=== 1.5.1 Jumper JP2 ===
115 115  
106 +Power on Device when put this jumper.
116 116  
117 -= 2.  Use NSE01 to communicate with IoT Server =
118 118  
109 +
110 +=== 1.5.2 BOOT MODE / SW1 ===
111 +
112 +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.
113 +
114 +2) Flash: work mode, device starts to work and send out console output for further debug
115 +
116 +
117 +
118 +=== 1.5.3 Reset Button ===
119 +
120 +Press to reboot the device.
121 +
122 +
123 +
124 +=== 1.5.4 LED ===
125 +
126 +It will flash:
127 +
128 +1. When boot the device in flash mode
129 +1. Send an uplink packet
130 +
131 +
132 +
133 += 2.  Use N95S31B to communicate with IoT Server =
134 +
119 119  == 2.1  How it works ==
120 120  
137 +
121 121  (((
122 -The NDDS75 is equipped with a NB-IoT module, the pre-loaded firmware in NDDS75 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 NDDS75.
139 +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.
123 123  )))
124 124  
125 125  
126 126  (((
127 -The diagram below shows the working flow in default firmware of NDDS75:
144 +The diagram below shows the working flow in default firmware of N95S31B:
128 128  )))
129 129  
130 130  (((
... ... @@ -131,7 +131,7 @@
131 131  
132 132  )))
133 133  
134 -[[image:1657328659945-416.png]]
151 +[[image:1657350248151-650.png]]
135 135  
136 136  (((
137 137  
... ... @@ -138,32 +138,45 @@
138 138  )))
139 139  
140 140  
158 +== 2.2 ​ Configure the N95S31B ==
141 141  
142 -== 2.2 ​ Configure the NSE01 ==
143 143  
161 +=== 2.2.1  Power On N95S31B ===
144 144  
163 +
164 +[[image:image-20220709150546-2.png]]
165 +
166 +
145 145  === 2.2.1 Test Requirement ===
146 146  
147 147  
148 -(((
149 -To use NSE01 in your city, make sure meet below requirements:
150 -)))
170 +To use N95S31B in your city, make sure meet below requirements:
151 151  
152 152  * Your local operator has already distributed a NB-IoT Network there.
153 -* The local NB-IoT network used the band that NSE01 supports.
173 +* The local NB-IoT network used the band that N95S31B supports.
154 154  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
155 155  
176 +Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.
177 +
178 +N95S31B supports different communication protocol such as :
179 +
156 156  (((
157 -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
158 -)))
181 +* CoAP  ((% style="color:red" %)120.24.4.116:5683(%%))
182 +* raw UDP  ((% style="color:red" %)120.24.4.116:5601(%%))
183 +* MQTT  ((% style="color:red" %)120.24.4.116:1883(%%))
184 +* TCP  ((% style="color:red" %)120.24.4.116:5600(%%))
159 159  
186 +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.
160 160  
161 -[[image:1657249419225-449.png]]
188 +
189 +)))
162 162  
191 +[[image:1657350625843-586.png]]
163 163  
164 164  
165 -=== 2.2.2 Insert SIM card ===
166 166  
195 +=== 2.2.3  Insert SIM card ===
196 +
167 167  (((
168 168  Insert the NB-IoT Card get from your provider.
169 169  )))
... ... @@ -173,18 +173,19 @@
173 173  )))
174 174  
175 175  
176 -[[image:1657249468462-536.png]]
206 +[[image:1657351240556-536.png]]
177 177  
178 178  
179 179  
180 -=== 2.2.3 Connect USB – TTL to NSE01 to configure it ===
210 +=== 2.2.4  Connect USB – TTL to N95S31B to configure it ===
181 181  
182 182  (((
183 183  (((
184 -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.
214 +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.
185 185  )))
186 186  )))
187 187  
218 +[[image:1657351312545-300.png]]
188 188  
189 189  **Connection:**
190 190  
... ... @@ -204,96 +204,110 @@
204 204  * Flow Control: (% style="color:green" %)**None**
205 205  
206 206  (((
207 -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.
238 +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.
208 208  )))
209 209  
210 -[[image:image-20220708110657-3.png]]
241 +[[image:1657329814315-101.png]]
211 211  
212 212  (((
213 -(% 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/]]
244 +(% 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/]]
214 214  )))
215 215  
216 216  
217 217  
218 -=== 2.2.4 Use CoAP protocol to uplink data ===
249 +=== 2.2.5  Use CoAP protocol to uplink data ===
219 219  
220 220  (% 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/]]
221 221  
222 222  
254 +(((
223 223  **Use below commands:**
256 +)))
224 224  
225 -* (% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
226 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
227 -* (% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
258 +* (((
259 +(% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
260 +)))
261 +* (((
262 +(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
263 +)))
264 +* (((
265 +(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
266 +)))
228 228  
268 +(((
269 +
270 +
229 229  For parameter description, please refer to AT command set
272 +)))
230 230  
231 -[[image:1657249793983-486.png]]
274 +[[image:1657352146020-183.png]]
232 232  
233 233  
234 -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.
277 +(((
278 +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.
279 +)))
235 235  
236 -[[image:1657249831934-534.png]]
281 +[[image:1657352185396-303.png]]
237 237  
238 238  
239 239  
240 -=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
285 +=== 2.2.6  Use UDP protocol to uplink data(Default protocol) ===
241 241  
242 -This feature is supported since firmware version v1.0.1
243 243  
244 -
245 -* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
288 +* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
246 246  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
247 -* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/If the server does not respond, this command is unnecessary
290 +* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/ If the server does not respond, this command is unnecessary
248 248  
249 -[[image:1657249864775-321.png]]
292 +[[image:1657352391268-297.png]]
250 250  
251 251  
252 -[[image:1657249930215-289.png]]
295 +[[image:1657352403317-397.png]]
253 253  
254 254  
255 255  
256 -=== 2.2.6 Use MQTT protocol to uplink data ===
299 +=== 2.2.7  Use MQTT protocol to uplink data ===
257 257  
258 -This feature is supported since firmware version v110
301 +N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption.
259 259  
303 +* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
304 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
305 +* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
306 +* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
307 +* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password of MQTT
308 +* (% style="color:blue" %)**AT+PUBTOPIC=f9527                               **(%%)~/~/Set the sending topic of MQTT
309 +* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527          **(%%) ~/~/Set the subscription topic of MQTT
260 260  
261 -* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
262 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
263 -* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
264 -* (% style="color:blue" %)**AT+UNAME=UNAME                               **(%%)~/~/Set the username of MQTT
265 -* (% style="color:blue" %)**AT+PWD=PWD                                        **(%%)~/~/Set the password of MQTT
266 -* (% style="color:blue" %)**AT+PUBTOPIC=NSE01_PUB                    **(%%)~/~/Set the sending topic of MQTT
267 -* (% style="color:blue" %)**AT+SUBTOPIC=NSE01_SUB          **(%%) ~/~/Set the subscription topic of MQTT
311 +[[image:1657352634421-276.png]]
268 268  
269 -[[image:1657249978444-674.png]]
270 270  
314 +[[image:1657352645687-385.png]]
271 271  
272 -[[image:1657249990869-686.png]]
316 +(((
317 +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.
318 +)))
273 273  
274 274  
275 275  (((
276 -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.
322 +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.
277 277  )))
278 278  
279 279  
280 280  
281 -=== 2.2.7 Use TCP protocol to uplink data ===
327 +=== 2.2.8  Use TCP protocol to uplink data ===
282 282  
283 283  This feature is supported since firmware version v110
284 284  
285 -
286 286  * (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
287 287  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
288 288  
289 -[[image:1657250217799-140.png]]
334 +[[image:1657352898400-901.png]]
290 290  
291 291  
292 -[[image:1657250255956-604.png]]
337 +[[image:1657352914475-252.png]]
293 293  
294 294  
295 295  
296 -=== 2.2.8 Change Update Interval ===
341 +=== 2.2.9  Change Update Interval ===
297 297  
298 298  User can use below command to change the (% style="color:green" %)**uplink interval**.
299 299  
... ... @@ -300,260 +300,200 @@
300 300  * (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
301 301  
302 302  (((
303 -(% style="color:red" %)**NOTE:**
348 +
304 304  )))
305 305  
306 -(((
307 -(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
308 -)))
309 309  
310 310  
311 -
312 312  == 2.3  Uplink Payload ==
313 313  
314 -In this mode, uplink payload includes in total 18 bytes
315 315  
316 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)
317 -|=(% style="width: 60px;" %)(((
318 -**Size(bytes)**
319 -)))|=(% 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**
320 -|(% 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"]]
356 +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.
321 321  
322 -(((
323 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NSE01 uplink data.
324 -)))
325 325  
359 +For example:
326 326  
327 -[[image:image-20220708111918-4.png]]
361 + (% 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.
328 328  
329 329  
330 -The payload is ASCII string, representative same HEX:
364 +The uplink payloads are composed in  ASCII String. For example:
331 331  
332 -0x72403155615900640c7817075e0a8c02f900 where:
366 +0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:
333 333  
334 -* Device ID: 0x 724031556159 = 724031556159
335 -* Version: 0x0064=100=1.0.0
368 +0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes
336 336  
337 -* BAT: 0x0c78 = 3192 mV = 3.192V
338 -* Singal: 0x17 = 23
339 -* Soil Moisture: 0x075e= 1886 = 18.86  %
340 -* Soil Temperature:0x0a8c =2700=27 °C
341 -* Soil Conductivity(EC) = 0x02f9 =761 uS /cm
342 -* Interrupt: 0x00 = 0
343 343  
344 -== 2.4  Payload Explanation and Sensor Interface ==
371 +(% style="color:red" %)**NOTE:**
345 345  
373 +(% style="color:red" %)
374 +1. All modes share the same Payload Explanation from [[HERE>>path:#Payload_Explain]].
375 +1. By default, the device will send an uplink message every 1 hour.
346 346  
347 -=== 2.4.1  Device ID ===
348 348  
349 -(((
350 -By default, the Device ID equal to the last 6 bytes of IMEI.
351 -)))
352 352  
353 -(((
354 -User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
355 -)))
356 356  
357 -(((
358 -**Example:**
359 -)))
380 +=== 2.3.1  Payload Analyze ===
360 360  
361 -(((
362 -AT+DEUI=A84041F15612
363 -)))
382 +N95S31B uplink payload includes in total 21 bytes
364 364  
365 -(((
366 -The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID.
367 -)))
368 368  
385 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
386 +|=(% style="width: 60px;" %)(((
387 +**Size(bytes)**
388 +)))|=(% 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**
389 +|(% 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" %)(((
390 +Reserve/ Same as NBSN95 CFGMOD=1
369 369  
392 +No function here.
393 +)))|(% style="width:77px" %)(((
394 +[[Temperature >>||anchor="H2.4.5A0Distance"]]
370 370  
371 -=== 2.4.2  Version Info ===
396 +By SHT31
397 +)))|(% style="width:80px" %)(((
398 +[[Humidity>>||anchor="H2.4.6A0DigitalInterrupt"]]
372 372  
373 -(((
374 -Specify the software version: 0x64=100, means firmware version 1.00.
400 +By SHT31
375 375  )))
376 376  
377 377  (((
378 -For example: 0x00 64 : this device is NSE01 with firmware version 1.0.0.
379 -)))
380 -
381 -
382 -
383 -=== 2.4.3  Battery Info ===
384 -
385 385  (((
386 -Check the battery voltage for LSE01.
405 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
387 387  )))
388 -
389 -(((
390 -Ex1: 0x0B45 = 2885mV
391 391  )))
392 392  
393 -(((
394 -Ex2: 0x0B49 = 2889mV
395 -)))
396 396  
410 +[[image:1657354294009-643.png]]
397 397  
398 398  
399 -=== 2.4.4  Signal Strength ===
413 +The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where:
400 400  
401 -(((
402 -NB-IoT Network signal Strength.
403 -)))
415 +* Device ID: 0x724031607457 = 724031607457
416 +* Version: 0x006e=110=1.1.0
404 404  
405 -(((
406 -**Ex1: 0x1d = 29**
407 -)))
418 +* BAT: 0x0ccd = 3277 mV = 3.277V
419 +* Signal: 0x1b = 27
420 +* Model: 0x01 = 1
421 +* 0x00dc000ccc= reserve, ignore in N95S31B
422 +* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C
423 +* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh
408 408  
409 409  (((
410 -(% style="color:blue" %)**0**(%%)  -113dBm or less
426 +
411 411  )))
412 412  
413 413  (((
414 -(% style="color:blue" %)**1**(%%)  -111dBm
430 +
415 415  )))
416 416  
417 -(((
418 -(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
419 -)))
420 420  
421 -(((
422 -(% style="color:blue" %)**31**  (%%) -51dBm or greater
423 -)))
434 +=== 2.3.2  Device ID ===
424 424  
425 425  (((
426 -(% style="color:blue" %)**99**   (%%) Not known or not detectable
437 +By default, the Device ID equal to the last 6 bytes of IMEI.
427 427  )))
428 428  
429 -
430 -
431 -=== 2.4.5  Soil Moisture ===
432 -
433 433  (((
434 -(((
435 -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.
441 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
436 436  )))
437 -)))
438 438  
439 439  (((
440 -(((
441 -For example, if the data you get from the register is **__0x05 0xDC__**, the moisture content in the soil is
445 +**Example:**
442 442  )))
443 -)))
444 444  
445 445  (((
446 -
449 +AT+DEUI=A84041F15612
447 447  )))
448 448  
449 449  (((
450 -(% style="color:#4f81bd" %)**05DC(H) = 1500(D) /100 = 15%.**
453 +The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
451 451  )))
452 452  
453 453  
454 454  
455 -=== 2.4.6  Soil Temperature ===
458 +=== 2.3.3  Version Info ===
456 456  
457 -(((
458 -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
459 -)))
460 460  
461 -(((
462 -**Example**:
463 -)))
461 +These bytes include the hardware and software version.
464 464  
465 -(((
466 -If payload is 0105H: ((0x0105 & 0x8000)>>15 === 0),temp = 0105(H)/100 = 2.61 °C
467 -)))
463 +Higher byte: Specify hardware version: always 0x00 for N95S31B
468 468  
469 -(((
470 -If payload is FF7EH: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/100 = -1.29 °C
471 -)))
465 +Lower byte: Specify the software version: 0x6E=110, means firmware version 110
472 472  
473 473  
468 +For example: 0x00 6E: this device is N95S31B with firmware version 110.
474 474  
475 -=== 2.4.7  Soil Conductivity (EC) ===
476 -
477 477  (((
478 -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).
471 +
479 479  )))
480 480  
481 -(((
482 -For example, if the data you get from the register is __**0x00 0xC8**__, the soil conductivity is 00C8(H) = 200(D) = 200 uS/cm.
483 -)))
484 484  
485 -(((
486 -Generally, the EC value of irrigation water is less than 800uS / cm.
487 -)))
475 +=== 2.3.4  Battery Info ===
488 488  
489 489  (((
490 -
478 +Ex1: 0x0B45 = 2885mV
491 491  )))
492 492  
493 493  (((
494 -
482 +Ex2: 0x0B49 = 2889mV
495 495  )))
496 496  
497 -=== 2.4.8  Digital Interrupt ===
498 498  
486 +
487 +=== 2.3.5  Signal Strength ===
488 +
499 499  (((
500 -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.
490 +NB-IoT Network signal Strength.
501 501  )))
502 502  
503 503  (((
504 -The command is:
494 +**Ex1: 0x1d = 29**
505 505  )))
506 506  
507 507  (((
508 -(% 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]])**.**
498 +(% style="color:blue" %)**0**(%%)  -113dBm or less
509 509  )))
510 510  
511 -
512 512  (((
513 -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.
502 +(% style="color:blue" %)**1**(%%)  -111dBm
514 514  )))
515 515  
516 -
517 517  (((
518 -Example:
506 +(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
519 519  )))
520 520  
521 521  (((
522 -0x(00): Normal uplink packet.
510 +(% style="color:blue" %)**31**  (%%) -51dBm or greater
523 523  )))
524 524  
525 525  (((
526 -0x(01): Interrupt Uplink Packet.
514 +(% style="color:blue" %)**99**   (%%) Not known or not detectable
527 527  )))
528 528  
529 529  
530 530  
531 -=== 2.4.9  ​+5V Output ===
519 +=== 2.3.6  Temperature & Humidity ===
532 532  
533 -(((
534 -NSE01 will enable +5V output before all sampling and disable the +5v after all sampling. 
535 -)))
521 +The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server.
536 536  
523 +[[image:image-20220709161741-3.png]]
537 537  
538 -(((
539 -The 5V output time can be controlled by AT Command.
540 -)))
541 541  
542 -(((
543 -(% style="color:blue" %)**AT+5VT=1000**
544 -)))
526 +Convert the read byte to decimal and divide it by ten.
545 545  
546 -(((
547 -Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.
548 -)))
549 549  
529 +**Example:**
550 550  
531 +Temperature:  Read:00ec (H) = 236(D)  Value:  236 /10=23.6℃
551 551  
533 +Humidity:    Read:0295(H)=661(D)    Value:  661 / 10=66.1, So 66.1%
534 +
535 +
536 +
552 552  == 2.5  Downlink Payload ==
553 553  
554 -By default, NSE01 prints the downlink payload to console port.
539 +By default, NDDS75 prints the downlink payload to console port.
555 555  
556 -[[image:image-20220708133731-5.png]]
541 +[[image:image-20220709100028-1.png]]
557 557  
558 558  
559 559  (((
... ... @@ -589,7 +589,7 @@
589 589  )))
590 590  
591 591  (((
592 -If payload = 0x04FF, it will reset the NSE01
577 +If payload = 0x04FF, it will reset the NDDS75
593 593  )))
594 594  
595 595  
... ... @@ -603,76 +603,52 @@
603 603  
604 604  == 2.6  ​LED Indicator ==
605 605  
606 -(((
607 -The NSE01 has an internal LED which is to show the status of different state.
608 608  
592 +The NDDS75 has an internal LED which is to show the status of different state.
609 609  
610 -* 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)
594 +
595 +* When power on, NDDS75 will detect if sensor probe is connected, if probe detected, LED will blink four times. (no blinks in this step is no probe)
611 611  * Then the LED will be on for 1 second means device is boot normally.
612 -* After NSE01 join NB-IoT network. The LED will be ON for 3 seconds.
597 +* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
613 613  * For each uplink probe, LED will be on for 500ms.
614 -)))
615 615  
616 -
617 -
618 -
619 -== 2.7  Installation in Soil ==
620 -
621 -__**Measurement the soil surface**__
622 -
623 623  (((
624 -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]]
601 +
625 625  )))
626 626  
627 -[[image:1657259653666-883.png]] ​
628 628  
629 629  
630 -(((
631 -
606 +== 2.7  ​Firmware Change Log ==
632 632  
608 +
633 633  (((
634 -Dig a hole with diameter > 20CM.
610 +Download URL & Firmware Change log
635 635  )))
636 636  
637 637  (((
638 -Horizontal insert the probe to the soil and fill the hole for long term measurement.
614 +[[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/Firmware/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/Firmware/]]
639 639  )))
640 -)))
641 641  
642 -[[image:1654506665940-119.png]]
643 643  
644 644  (((
645 -
619 +Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
646 646  )))
647 647  
648 648  
649 -== 2.8  ​Firmware Change Log ==
650 650  
624 +== 2.8  ​Battery Analysis ==
651 651  
652 -Download URL & Firmware Change log
626 +=== 2.8.1  ​Battery Type ===
653 653  
654 -[[www.dragino.com/downloads/index.php?dir=NB-IoT/NSE01/Firmware/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/Firmware/]]
655 655  
656 -
657 -Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
658 -
659 -
660 -
661 -== 2.9  ​Battery Analysis ==
662 -
663 -=== 2.9.1  ​Battery Type ===
664 -
665 -
666 666  (((
667 -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.
630 +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.
668 668  )))
669 669  
670 -
671 671  (((
672 672  The battery is designed to last for several years depends on the actually use environment and update interval. 
673 673  )))
674 674  
675 -
676 676  (((
677 677  The battery related documents as below:
678 678  )))
... ... @@ -682,12 +682,12 @@
682 682  * [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
683 683  
684 684  (((
685 -[[image:image-20220708140453-6.png]]
646 +[[image:image-20220709101450-2.png]]
686 686  )))
687 687  
688 688  
689 689  
690 -=== 2.9.2  Power consumption Analyze ===
651 +=== 2.8.2  Power consumption Analyze ===
691 691  
692 692  (((
693 693  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.
... ... @@ -721,11 +721,11 @@
721 721  And the Life expectation in difference case will be shown on the right.
722 722  )))
723 723  
724 -[[image:image-20220708141352-7.jpeg]]
685 +[[image:image-20220709110451-3.png]]
725 725  
726 726  
727 727  
728 -=== 2.9.3  ​Battery Note ===
689 +=== 2.8.3  ​Battery Note ===
729 729  
730 730  (((
731 731  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.
... ... @@ -733,10 +733,10 @@
733 733  
734 734  
735 735  
736 -=== 2.9.4  Replace the battery ===
697 +=== 2.8.4  Replace the battery ===
737 737  
738 738  (((
739 -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).
700 +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).
740 740  )))
741 741  
742 742  
... ... @@ -751,7 +751,7 @@
751 751  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/]] 
752 752  )))
753 753  
754 -[[image:1657261278785-153.png]]
715 +[[image:1657333200519-600.png]]
755 755  
756 756  
757 757  
... ... @@ -759,7 +759,7 @@
759 759  
760 760  == 4.1  Access AT Commands ==
761 761  
762 -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/]]
723 +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/]]
763 763  
764 764  
765 765  AT+<CMD>?  : Help on <CMD>
... ... @@ -847,18 +847,11 @@
847 847  )))
848 848  
849 849  (((
850 -(% style="color:red" %)Notice, NSE01 and LSE01 share the same mother board. They use the same connection and method to update.
811 +(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.
851 851  )))
852 852  
853 853  
854 854  
855 -== 5.2  Can I calibrate NSE01 to different soil types? ==
856 -
857 -(((
858 -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]].
859 -)))
860 -
861 -
862 862  = 6.  Trouble Shooting =
863 863  
864 864  == 6.1  ​Connection problem when uploading firmware ==
... ... @@ -886,7 +886,7 @@
886 886  = 7. ​ Order Info =
887 887  
888 888  
889 -Part Number**:** (% style="color:#4f81bd" %)**NSE01**
843 +Part Number**:** (% style="color:#4f81bd" %)**NSDDS75**
890 890  
891 891  
892 892  (% class="wikigeneratedid" %)
... ... @@ -901,7 +901,7 @@
901 901  
902 902  (% style="color:#037691" %)**Package Includes**:
903 903  
904 -* NSE01 NB-IoT Soil Moisture & EC Sensor x 1
858 +* NSE01 NB-IoT Distance Detect Sensor Node x 1
905 905  * External antenna x 1
906 906  )))
907 907  
... ... @@ -910,8 +910,11 @@
910 910  
911 911  (% style="color:#037691" %)**Dimension and weight**:
912 912  
913 -* Size: 195 x 125 x 55 mm
914 -* Weight:   420g
867 +
868 +* Device Size: 13.0 x 5 x 4.5 cm
869 +* Device Weight: 150g
870 +* Package Size / pcs : 15 x 12x 5.5 cm
871 +* Weight / pcs : 220g
915 915  )))
916 916  
917 917  (((
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-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