Last modified by Mengting Qiu on 2024/04/02 16:44
<
From version < 97.13 >
edited by Xiaoling
on 2022/07/09 11:36
To version < 125.2 >
edited by Xiaoling
on 2022/09/09 15:51
>
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,10 +1,12 @@
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 +
9 +
8 8  **Table of Contents:**
9 9  
10 10  {{toc/}}
... ... @@ -13,37 +13,42 @@
13 13  
14 14  
15 15  
16 -
17 17  = 1.  Introduction =
18 18  
19 -== 1.1 ​ What is NDDS75 Distance Detection Sensor ==
20 20  
21 +== 1.1 ​ What is N95S31B NB-IoT Sensor Node ==
22 +
21 21  (((
22 22  
23 23  
24 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.
27 +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*.
28 +)))
26 26  
30 +(((
31 +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.
32 +)))
27 27  
28 -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.
34 +(((
35 +N95S31B supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP**(%%) for different application requirement.
36 +)))
29 29  
38 +(((
39 +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).
40 +)))
30 30  
31 -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.
42 +(((
43 +
44 +)))
32 32  
33 -
34 -NDDS75 supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP** (%%)for different application requirement.
35 -
36 -
37 -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)
38 -
39 -
40 -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.
46 +(((
47 +~* make sure you have NB-IoT coverage locally.
41 41  )))
42 42  
43 43  
44 44  )))
45 45  
46 -[[image:1657327959271-447.png]]
53 +[[image:1657348284168-431.png]]
47 47  
48 48  
49 49  
... ... @@ -51,19 +51,18 @@
51 51  
52 52  
53 53  * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
54 -* Ultra low power consumption
55 -* Distance Detection by Ultrasonic technology
56 -* Flat object range 280mm - 7500mm
57 -* Accuracy: ±(1cm+S*0.3%) (S: Distance)
58 -* Cable Length: 25cm
61 +* Monitor Temperature & Humidity via SHT31
59 59  * AT Commands to change parameters
60 60  * Uplink on periodically
61 61  * Downlink to change configure
62 62  * IP66 Waterproof Enclosure
66 +* Ultra-Low Power consumption
67 +* AT Commands to change parameters
63 63  * Micro SIM card slot for NB-IoT SIM
64 64  * 8500mAh Battery for long term use
65 65  
66 66  
72 +
67 67  == 1.3  Specification ==
68 68  
69 69  
... ... @@ -89,14 +89,11 @@
89 89  * Max continuously current: 130mA
90 90  * Max boost current: 2A, 1 second
91 91  
92 -(% style="color:#037691" %)**Power Consumption**
93 93  
94 -* STOP Mode: 10uA @ 3.3v
95 -* Max transmit power: 350mA@3.3v
96 96  
97 -
98 98  == ​1.4  Applications ==
99 99  
102 +
100 100  * Smart Buildings & Home Automation
101 101  * Logistics and Supply Chain Management
102 102  * Smart Metering
... ... @@ -108,24 +108,68 @@
108 108  ​
109 109  
110 110  
111 -== 1.5  Pin Definitions ==
112 112  
113 113  
114 -[[image:1657328609906-564.png]]
116 +== 1.5  Pin Definitions & Switch ==
115 115  
116 116  
119 +N95S31B use the mother board from NBSN95 which as below.
117 117  
118 -= 2.  Use NDDS75 to communicate with IoT Server =
119 119  
122 +[[image:image-20220709144723-1.png]]
123 +
124 +
125 +
126 +=== 1.5.1 Jumper JP2 ===
127 +
128 +
129 +Power on Device when put this jumper.
130 +
131 +
132 +
133 +=== 1.5.2 BOOT MODE / SW1 ===
134 +
135 +
136 +(((
137 +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.
138 +)))
139 +
140 +(((
141 +2) Flash: work mode, device starts to work and send out console output for further debug
142 +)))
143 +
144 +
145 +
146 +=== 1.5.3 Reset Button ===
147 +
148 +
149 +Press to reboot the device.
150 +
151 +
152 +
153 +=== 1.5.4 LED ===
154 +
155 +
156 +It will flash:
157 +
158 +1. When boot the device in flash mode
159 +1. Send an uplink packet
160 +
161 +
162 +
163 += 2.  Use N95S31B to communicate with IoT Server =
164 +
165 +
120 120  == 2.1  How it works ==
121 121  
168 +
122 122  (((
123 -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.
170 +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.
124 124  )))
125 125  
126 126  
127 127  (((
128 -The diagram below shows the working flow in default firmware of NDDS75:
175 +The diagram below shows the working flow in default firmware of N95S31B:
129 129  )))
130 130  
131 131  (((
... ... @@ -132,7 +132,7 @@
132 132  
133 133  )))
134 134  
135 -[[image:1657328659945-416.png]]
182 +[[image:1657520100595-569.png]]
136 136  
137 137  (((
138 138  
... ... @@ -139,30 +139,69 @@
139 139  )))
140 140  
141 141  
142 -== 2.2 ​ Configure the NDDS75 ==
189 +== 2.2 ​ Configure the N95S31B ==
143 143  
144 144  
192 +=== 2.2.1  Power On N95S31B ===
193 +
194 +
195 +[[image:image-20220709150546-2.png]]
196 +
197 +
198 +
145 145  === 2.2.1 Test Requirement ===
146 146  
201 +
147 147  (((
148 -To use NDDS75 in your city, make sure meet below requirements:
203 +To use N95S31B in your city, make sure meet below requirements:
149 149  )))
150 150  
151 -* Your local operator has already distributed a NB-IoT Network there.
152 -* The local NB-IoT network used the band that NSE01 supports.
153 -* Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
206 +* (((
207 +Your local operator has already distributed a NB-IoT Network there.
208 +)))
209 +* (((
210 +The local NB-IoT network used the band that N95S31B supports.
211 +)))
212 +* (((
213 +Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
214 +)))
154 154  
155 155  (((
156 -Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.  The NDDS75 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
217 +Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.
157 157  )))
158 158  
220 +(((
221 +N95S31B supports different communication protocol such as :
222 +)))
159 159  
160 -[[image:1657328756309-230.png]]
224 +(((
225 +* (((
226 +CoAP  ((% style="color:red" %)120.24.4.116:5683(%%))
227 +)))
228 +* (((
229 +raw UDP  ((% style="color:red" %)120.24.4.116:5601(%%))
230 +)))
231 +* (((
232 +MQTT  ((% style="color:red" %)120.24.4.116:1883(%%))
233 +)))
234 +* (((
235 +TCP  ((% style="color:red" %)120.24.4.116:5600(%%))
236 +)))
161 161  
238 +(((
239 +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.
240 +)))
162 162  
242 +
243 +)))
163 163  
164 -=== 2.2.2 Insert SIM card ===
245 +[[image:1657350625843-586.png]]
165 165  
247 +
248 +
249 +=== 2.2.3  Insert SIM card ===
250 +
251 +
166 166  (((
167 167  Insert the NB-IoT Card get from your provider.
168 168  )))
... ... @@ -172,20 +172,24 @@
172 172  )))
173 173  
174 174  
175 -[[image:1657328884227-504.png]]
261 +[[image:1657351240556-536.png]]
176 176  
177 177  
178 178  
179 -=== 2.2.3 Connect USB – TTL to NDDS75 to configure it ===
265 +=== 2.2.4  Connect USB – TTL to N95S31B to configure it ===
180 180  
267 +
181 181  (((
182 182  (((
183 -User need to configure NDDS75 via serial port to set the (% style="color:blue" %)**Server Address** / **Uplink Topic** (%%)to define where and how-to uplink packets. NDDS75 support AT Commands, user can use a USB to TTL adapter to connect to NDDS75 and use AT Commands to configure it, as below.
270 +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.
271 +
272 +
184 184  )))
185 185  )))
186 186  
187 -[[image:image-20220709092052-2.png]]
276 +[[image:1657351312545-300.png]]
188 188  
278 +
189 189  **Connection:**
190 190  
191 191   (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
... ... @@ -204,22 +204,24 @@
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 NDDS75. NDDS75 will output system info once power on as below, we can enter the (% style="color:green" %)**password: 12345678**(%%) to access AT Command input.
297 +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 210  [[image:1657329814315-101.png]]
211 211  
302 +
212 212  (((
213 -(% style="color:red" %)Note: the valid AT Commands can be found at: (%%)[[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/]]
304 +(% style="color:red" %)**Note: the valid AT Commands can be found at:  **(%%)**[[https:~~/~~/www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i~~-~~-AyZcQkoua?dl=0>>https://www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i--AyZcQkoua?dl=0]]**
214 214  )))
215 215  
216 216  
217 217  
218 -=== 2.2.4 Use CoAP protocol to uplink data ===
309 +=== 2.2.5  Use CoAP protocol to uplink data ===
219 219  
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  
312 +(% 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/]]**
222 222  
314 +
223 223  (((
224 224  **Use below commands:**
225 225  )))
... ... @@ -235,10 +235,12 @@
235 235  )))
236 236  
237 237  (((
330 +
331 +
238 238  For parameter description, please refer to AT command set
239 239  )))
240 240  
241 -[[image:1657330452568-615.png]]
335 +[[image:1657352146020-183.png]]
242 242  
243 243  
244 244  (((
... ... @@ -245,11 +245,11 @@
245 245  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.
246 246  )))
247 247  
248 -[[image:1657330472797-498.png]]
342 +[[image:1657352185396-303.png]]
249 249  
250 250  
251 251  
252 -=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
346 +=== 2.2.6  Use UDP protocol to uplink data(Default protocol) ===
253 253  
254 254  
255 255  * (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
... ... @@ -256,109 +256,119 @@
256 256  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
257 257  * (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/ If the server does not respond, this command is unnecessary
258 258  
259 -[[image:1657330501006-241.png]]
353 +[[image:1657352391268-297.png]]
260 260  
261 261  
262 -[[image:1657330533775-472.png]]
356 +[[image:1657352403317-397.png]]
263 263  
264 264  
265 265  
266 -=== 2.2.6 Use MQTT protocol to uplink data ===
360 +=== 2.2.7  Use MQTT protocol to uplink data ===
267 267  
268 268  
363 +N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption.
364 +
269 269  * (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
270 270  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
271 271  * (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
272 272  * (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
273 273  * (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password of MQTT
274 -* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/Set the sending topic of MQTT
275 -* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%) ~/~/Set the subscription topic of MQTT
370 +* (% style="color:blue" %)**AT+PUBTOPIC=f9527                               **(%%)~/~/Set the sending topic of MQTT
371 +* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527          **(%%) ~/~/Set the subscription topic of MQTT
276 276  
277 -[[image:1657249978444-674.png]]
373 +[[image:1657352634421-276.png]]
278 278  
279 279  
280 -[[image:1657330723006-866.png]]
376 +[[image:1657352645687-385.png]]
281 281  
282 282  
283 283  (((
284 -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.
380 +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.
285 285  )))
286 286  
287 287  
384 +(((
385 +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.
386 +)))
288 288  
289 -=== 2.2.7 Use TCP protocol to uplink data ===
290 290  
291 291  
390 +=== 2.2.8  Use TCP protocol to uplink data ===
391 +
392 +
393 +This feature is supported since firmware version v110
394 +
292 292  * (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
293 293  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
294 294  
295 -[[image:image-20220709093918-1.png]]
398 +[[image:1657352898400-901.png]]
296 296  
297 297  
298 -[[image:image-20220709093918-2.png]]
401 +[[image:1657352914475-252.png]]
299 299  
300 300  
301 301  
302 -=== 2.2.8 Change Update Interval ===
405 +=== 2.2.9  Change Update Interval ===
303 303  
407 +
304 304  User can use below command to change the (% style="color:green" %)**uplink interval**.
305 305  
306 306  * (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
307 307  
308 308  (((
309 -(% style="color:red" %)**NOTE:**
413 +
310 310  )))
311 311  
312 312  (((
313 -(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
417 +(% style="color:red" %)**NOTE: Since firmware version is v1.2:**
314 314  )))
315 315  
420 +(((
421 +(% style="color:red" %)**By default, the device will send an uplink message every 2 hours. Each Uplink Include 8 set of records in this 2 hour (15 minute interval / record).**
422 +)))
316 316  
317 317  
425 +
318 318  == 2.3  Uplink Payload ==
319 319  
320 -In this mode, uplink payload includes in total 14 bytes
321 321  
429 +(((
430 +N95S31B has different working modes for the connections of different types 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.
431 +)))
322 322  
323 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)
324 -|=(% style="width: 60px;" %)(((
325 -**Size(bytes)**
326 -)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 80px;" %)**2**|=(% style="width: 60px;" %)**1**
327 -|(% 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:120px" %)[[Distance (unit: mm)>>||anchor="H2.4.5A0Distance"]]|(% style="width:80px" %)[[Interrupt>>||anchor="H2.4.6A0DigitalInterrupt"]]
328 328  
329 329  (((
330 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data.
435 +For example:
331 331  )))
332 332  
438 +(((
439 + (% style="color:blue" %)**AT+CFGMOD=2 ** (%%)~/~/will set the N95S31B to work in MOD=2 distance mode which target to measure distance via Ultrasonic Sensor.
440 +)))
333 333  
334 -[[image:1657331036973-987.png]]
335 335  
336 336  (((
337 -The payload is ASCII string, representative same HEX:
444 +The uplink payloads are composed in  ASCII String. For example:
338 338  )))
339 339  
340 340  (((
341 -0x72403155615900640c6c19029200 where:
448 +0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:
342 342  )))
343 343  
344 -* (((
345 -Device ID: 0x724031556159 = 724031556159
451 +(((
452 +0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes
346 346  )))
347 -* (((
348 -Version: 0x0064=100=1.0.0
454 +
455 +
456 +(((
457 +(% style="color:red" %)**NOTE:**
349 349  )))
350 350  
351 -* (((
352 -BAT: 0x0c6c = 3180 mV = 3.180V
460 +(% style="color:red" %)
461 +1. (((
462 +**All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].**
353 353  )))
354 -* (((
355 -Signal: 0x19 = 25
356 -)))
357 -* (((
358 -Distance: 0x0292= 658 mm
359 -)))
360 -* (((
361 -Interrupt: 0x00 = 0
464 +1. (((
465 +**By default, the device will send an uplink message every 1 hour.**
362 362  
363 363  
364 364  
... ... @@ -365,103 +365,163 @@
365 365  
366 366  )))
367 367  
368 -== 2.4  Payload Explanation and Sensor Interface ==
472 +=== 2.3.1  Payload Analyze ===
369 369  
370 370  
371 -=== 2.4.1  Device ID ===
475 +==== 2.3.1.1  Before Firmware v1.2 ====
372 372  
477 +
478 +N95S31B uplink payload includes in total 21 bytes
479 +
480 +
481 +(% border="2" cellspacing="10" style="background-color:#ffffcc; color:green; width:760px" %)
482 +|=(% style="width: 60px;" %)(((
483 +**Size(bytes)**
484 +)))|=(% style="width: 65px;" %)**6**|=(% style="width: 50px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 75px;" %)**1**|=(% style="width: 59px;" %)1|=(% style="width: 174px;" %)5|=(% style="width: 106px;" %)**2**|=(% style="width: 85px;" %)**2**
485 +|(% style="width:97px" %)**Value**|(% style="width:65px" %)[[Device ID>>||anchor="H2.3.2A0DeviceID"]]|(% style="width:50px" %)[[Ver>>||anchor="H2.3.3A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.3.4A0BatteryInfo"]]|(% style="width:75px" %)[[Signal Strength>>||anchor="H2.3.5A0SignalStrength"]]|(% style="width:59px" %)MOD 0X01|(% style="width:174px" %)(((
373 373  (((
374 -By default, the Device ID equal to the last 6 bytes of IMEI.
487 +Reserve/ Same as NBSN95 CFGMOD=1
375 375  )))
376 376  
377 377  (((
378 -User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
491 +No function here.
379 379  )))
493 +)))|(% style="width:106px" %)(((
494 +(((
495 +[[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]]
496 +)))
380 380  
381 381  (((
382 -**Example:**
499 +By SHT31
383 383  )))
501 +)))|(% style="width:85px" %)(((
502 +(((
503 +[[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]]
504 +)))
384 384  
385 385  (((
386 -AT+DEUI=A84041F15612
507 +By SHT31
387 387  )))
509 +)))
388 388  
389 389  (((
390 -The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
512 +
513 +
514 +(((
515 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
391 391  )))
517 +)))
392 392  
393 393  
520 +[[image:1657354294009-643.png]]
394 394  
395 -=== 2.4.2  Version Info ===
396 396  
397 -(((
398 -Specify the software version: 0x64=100, means firmware version 1.00.
399 -)))
523 +The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where:
400 400  
401 -(((
402 -For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0.
403 -)))
525 +* Device ID:  0x724031607457 = 724031607457
404 404  
527 +* Version:  0x006e=110=1.1.0
405 405  
529 +* BAT:  0x0ccd = 3277 mV = 3.277V
406 406  
407 -=== 2.4.3  Battery Info ===
531 +* Signal:  0x1b = 27
408 408  
409 -(((
410 -Ex1: 0x0B45 = 2885mV
411 -)))
533 +* Model:  0x01 = 1
412 412  
535 +* 0x00dc000ccc= reserve, ignore in N95S31B
536 +
537 +* Temperature by SHT31:  0x00e1 = 225 = 22.5 °C
538 +
539 +* Humidity by SHT31:  0x0186 = 390 = 39.0 %rh
540 +
413 413  (((
414 -Ex2: 0x0B49 = 2889mV
542 +
543 +
544 +
545 +
415 415  )))
416 416  
548 +==== 2.3.1.2 Since Firmware v1.2 ====
417 417  
550 +In this mode, uplink payload includes 91 bytes in total by default.
418 418  
419 -=== 2.4.4  Signal Strength ===
552 +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.
420 420  
421 -(((
422 -NB-IoT Network signal Strength.
423 -)))
554 +|**Size(bytes)**|**8**|2|2|1|1|2|1|2|2|2|4|2|2|4
555 +|**Value**|Device ID|Ver|BAT|Signal Strength|MOD|TemDS18B20|Interrupt|ADC|SHTTEM|SHTHUM|Time stamp |SHTTEM|SHTHUM|Time stamp .....
424 424  
425 -(((
426 -**Ex1: 0x1d = 29**
427 -)))
557 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the N95S31B uplink data.
428 428  
559 +[[image:image-20220908154949-1.png]]
560 +
561 +The payload is ASCII string, representative same HEX:
562 +
563 +0x(% style="color:red" %)f868411056758782(% style="color:blue" %)000c(% style="color:green" %)0d0f(% style="color:red" %)0c(% style="color:blue" %)01(% style="color:green" %)0000(% style="color:red" %)00**//0030//**(% style="color:blue" %)**//0114//**(% style="color:red" %)**//0231//**(% style="color:green" %)**//63199d3c//**0113023163199d12//**0113023163199c5e**//0112023763199baa//**0112023263199af6**//0111023b631999a7//**0112023b631998f3**//011202426319983f//**01110242631996eb**//(%%) where:
564 +
565 +* (% style="color:red" %) Device ID: f868411056758782 = f868411056758782
566 +* (% style="color:blue" %) Version: 0x000c=120=1.2
567 +* (% style="color:green" %) BAT: 0x0d0f = 3343 mV = 3.343V
568 +* (% style="color:red" %) Singal: 0x0c = 12
569 +* (% style="color:blue" %) Mod: 0x01 = 1
570 +* TemDS18B20: 0x0000= 0 = 0
571 +* (% style="color:green" %)Interrupt: 0x00= 0
572 +* (% style="color:green" %)adc: 0x0030= 48
573 +* SHTTEM: 0x0114= 276 = 27.6
574 +* SHTHUM:0x0231 =561=56.1%
575 +* (% style="color:red" %) Time stamp : 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
576 +* (% style="color:red" %)SHTTEM,SHTHUM,Time stamp : 0113023163199d12
577 +* 8 sets of recorded data: SHTTEM,SHTHUM,Time stamp : //**0113023163199c5e**//,.......
578 +
579 +=== 2.3.2  Device ID ===
580 +
581 +
429 429  (((
430 -(% style="color:blue" %)**0**(%%)  -113dBm or less
583 +By default, the Device ID equal to the last 6 bytes of IMEI.
431 431  )))
432 432  
433 433  (((
434 -(% style="color:blue" %)**1**(%%)  -111dBm
587 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
435 435  )))
436 436  
437 437  (((
438 -(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
591 +**Example:**
439 439  )))
440 440  
441 441  (((
442 -(% style="color:blue" %)**31**  (%%) -51dBm or greater
595 +AT+DEUI=A84041F15612
443 443  )))
444 444  
445 445  (((
446 -(% style="color:blue" %)**99**   (%%) Not known or not detectable
599 +The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
600 +
601 +
447 447  )))
448 448  
604 +(% style="color:red" %)**NOTE:When the firmware version is v1.2 and later firmware:**
449 449  
450 450  
451 -=== 2.4.5  Distance ===
607 +By default, the Device ID equal to the last 15 bits of IMEI.
452 452  
453 -Get the distance. Flat object range 280mm - 7500mm.
609 +User can use **AT+DEUI** to set Device ID
454 454  
455 -For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is
611 +**Example:**
456 456  
613 +AT+DEUI=868411056754138
614 +
615 +
616 +=== 2.3.3  Version Info ===
617 +
618 +
457 457  (((
620 +These bytes include the hardware and software version.
621 +)))
622 +
458 458  (((
459 -(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.**
624 +Higher byte: Specify hardware version: always 0x00 for N95S31B
460 460  )))
461 -)))
462 462  
463 463  (((
464 -
628 +Lower byte: Specify the software version: 0x6E=110, means firmware version 110
465 465  )))
466 466  
467 467  (((
... ... @@ -468,65 +468,85 @@
468 468  
469 469  )))
470 470  
471 -=== 2.4.6  Digital Interrupt ===
472 -
473 473  (((
474 -Digital Interrupt refers to pin (% style="color:blue" %)**GPIO_EXTI**(%%), and there are different trigger methods. When there is a trigger, the NDDS75 will send a packet to the server.
636 +For example: 0x00 6E: this device is N95S31B with firmware version 110.
475 475  )))
476 476  
477 477  (((
478 -The command is:
640 +
479 479  )))
480 480  
643 +
644 +=== 2.3.4  Battery Info ===
645 +
646 +
481 481  (((
482 -(% 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]])**.**
648 +Ex1: 0x0B45 = 2885mV
483 483  )))
484 484  
485 -
486 486  (((
487 -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.
652 +Ex2: 0x0B49 = 2889mV
488 488  )))
489 489  
490 490  
656 +
657 +=== 2.3.5  Signal Strength ===
658 +
659 +
491 491  (((
492 -Example:
661 +NB-IoT Network signal Strength.
493 493  )))
494 494  
495 495  (((
496 -0x(00): Normal uplink packet.
665 +**Ex1: 0x1d = 29**
497 497  )))
498 498  
499 499  (((
500 -0x(01): Interrupt Uplink Packet.
669 +(% style="color:blue" %)**0**(%%)  -113dBm or less
501 501  )))
502 502  
503 -
504 -
505 -=== 2.4.7  ​+5V Output ===
506 -
507 507  (((
508 -NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 
673 +(% style="color:blue" %)**1**(%%)  -111dBm
509 509  )))
510 510  
511 -
512 512  (((
513 -The 5V output time can be controlled by AT Command.
677 +(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
514 514  )))
515 515  
516 516  (((
517 -(% style="color:blue" %)**AT+5VT=1000**
681 +(% style="color:blue" %)**31**  (%%) -51dBm or greater
518 518  )))
519 519  
520 520  (((
521 -Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.
685 +(% style="color:blue" %)**99**   (%%) Not known or not detectable
522 522  )))
523 523  
524 524  
525 525  
526 -== 2.5  Downlink Payload ==
690 +=== 2.3.6  Temperature & Humidity ===
527 527  
528 -By default, NDDS75 prints the downlink payload to console port.
529 529  
693 +The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server.
694 +
695 +[[image:image-20220709161741-3.png]]
696 +
697 +
698 +Convert the read byte to decimal and divide it by ten.
699 +
700 +
701 +**Example:**
702 +
703 +Temperature:  Read:00ec (H) = 236(D)  Value:  236 /10=23.6℃
704 +
705 +Humidity:    Read:0295(H)=661(D)    Value:  661 / 10=66.1, So 66.1%
706 +
707 +
708 +
709 +== 2.4  Downlink Payload ==
710 +
711 +
712 +By default, N95S31B prints the downlink payload to console port.
713 +
530 530  [[image:image-20220709100028-1.png]]
531 531  
532 532  
... ... @@ -563,7 +563,7 @@
563 563  )))
564 564  
565 565  (((
566 -If payload = 0x04FF, it will reset the NDDS75
750 +If payload = 0x04FF, it will reset the N95S31B
567 567  )))
568 568  
569 569  
... ... @@ -574,45 +574,61 @@
574 574  )))
575 575  
576 576  
761 +== 2.5 Humidity and Temperature alarm function ==
577 577  
578 -== 2.6  ​LED Indicator ==
763 +➢ AT Command:
579 579  
765 +AT+ SHHUM=min,max
580 580  
581 -The NDDS75 has an internal LED which is to show the status of different state.
767 +² When min=0, and max≠0, Alarm higher than max
582 582  
769 +² When min≠0, and max=0, Alarm lower than min
583 583  
584 -* 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)
585 -* Then the LED will be on for 1 second means device is boot normally.
586 -* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
587 -* For each uplink probe, LED will be on for 500ms.
771 +² When min≠0 and max≠0, Alarm higher than max or lower than min
588 588  
589 -(((
590 -
591 -)))
773 +Example:
592 592  
775 +AT+ SHHUM=50,80 ~/~/ Alarm when humidity lower than 50.
593 593  
594 594  
595 -== 2.7  ​Firmware Change Log ==
778 +AT+ SHTEMP=min,max
596 596  
780 +² When min=0, and max≠0, Alarm higher than max
597 597  
598 -Download URL & Firmware Change log
782 +² When min≠0, and max=0, Alarm lower than min
599 599  
600 -(((
601 -[[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/]]
602 -)))
784 +² When min≠0 and max≠0, Alarm higher than max or lower than min
603 603  
786 +Example:
604 604  
605 -Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
788 +AT+ SHTEMP=20,30 ~/~/ Alarm when temperature lower than 20.
606 606  
790 +== 2.6 Set the number of data to be uploaded and the recording time ==
607 607  
792 +➢ AT Command:
608 608  
794 +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)
795 +
796 +AT+NOUD=8  ~/~/The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
797 +
798 +== 2.7 Read or Clear cached data ==
799 +
800 +➢ AT Command:
801 +
802 +AT+CDP ~/~/ Read cached data
803 +
804 +[[image:image-20220908163102-2.png]]
805 +
806 +AT+CDP=0 ~/~/ Clear cached data
807 +
609 609  == 2.8  ​Battery Analysis ==
610 610  
810 +
611 611  === 2.8.1  ​Battery Type ===
612 612  
613 613  
614 614  (((
615 -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.
815 +The N95S31B battery is a combination of an 8500mAh Li/SOCI2 Battery and a Super Capacitor. The battery is none-rechargeable battery type with a low discharge rate (<2% per year). This type of battery is commonly used in IoT devices such as water meter.
616 616  )))
617 617  
618 618  (((
... ... @@ -635,54 +635,35 @@
635 635  
636 636  === 2.8.2  Power consumption Analyze ===
637 637  
638 -(((
639 -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.
640 -)))
641 641  
642 -
643 643  (((
644 -Instruction to use as below:
840 +The file **DRAGINO_N95S31B-Power-Analyzer.pdf** from [[https:~~/~~/www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i~~-~~-AyZcQkoua?dl=0>>https://www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i--AyZcQkoua?dl=0]] describes a detail measurement to analyze the power consumption in different case. User can use it for design guideline for their project.
645 645  )))
646 646  
647 647  (((
648 -(% style="color:blue" %)**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/]]
844 +
649 649  )))
650 650  
651 651  
652 -(((
653 -(% style="color:blue" %)**Step 2: **(%%) Open it and choose
654 -)))
848 +=== 2.8.3  ​Battery Note ===
655 655  
656 -* (((
657 -Product Model
658 -)))
659 -* (((
660 -Uplink Interval
661 -)))
662 -* (((
663 -Working Mode
664 -)))
665 665  
666 666  (((
667 -And the Life expectation in difference case will be shown on the right.
852 +The Li-SICO battery is designed for small current / long period application. It is not good to use a high current, short period transmit method. The recommended minimum period for use of this battery is 5 minutes. If you use a shorter period time to uplink data, then the battery life may be decreased.
668 668  )))
669 669  
670 -[[image:image-20220709110451-3.png]]
671 671  
672 672  
857 +=== 2.8.4  Replace the battery ===
673 673  
674 -=== 2.8.3  ​Battery Note ===
675 675  
676 676  (((
677 -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.
861 +You can change the battery in the N95S31B.The type of battery is not limited as long as the output is between 3v to 3.6v. On the main board, there is a diode (D1) between the battery and the main circuit. If you need to use a battery with less than 3.3v, please remove the D1 and shortcut the two pads of it so there won't be voltage drop between battery and main board.
678 678  )))
679 679  
680 680  
681 -
682 -=== 2.8.4  Replace the battery ===
683 -
684 684  (((
685 -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).
866 +The default battery pack of N95S31B 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).
686 686  )))
687 687  
688 688  
... ... @@ -689,6 +689,7 @@
689 689  
690 690  = 3. ​ Access NB-IoT Module =
691 691  
873 +
692 692  (((
693 693  Users can directly access the AT command set of the NB-IoT module.
694 694  )))
... ... @@ -695,6 +695,8 @@
695 695  
696 696  (((
697 697  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/]] 
880 +
881 +
698 698  )))
699 699  
700 700  [[image:1657333200519-600.png]]
... ... @@ -703,11 +703,13 @@
703 703  
704 704  = 4.  Using the AT Commands =
705 705  
890 +
706 706  == 4.1  Access AT Commands ==
707 707  
708 -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/]]
709 709  
894 +See NBSN95 AT Command in this link for detail:  [[https:~~/~~/www.dropbox.com/sh/jao1xt9kw5r3yq4/AAAMpJkZzExF2JLbRWxGoQ9Na?dl=0>>https://www.dropbox.com/sh/jao1xt9kw5r3yq4/AAAMpJkZzExF2JLbRWxGoQ9Na?dl=0]]
710 710  
896 +
711 711  AT+<CMD>?  : Help on <CMD>
712 712  
713 713  AT+<CMD>         : Run <CMD>
... ... @@ -747,7 +747,24 @@
747 747  
748 748  AT+SERVADDR  : Server Address
749 749  
936 +AT+TR      : Get or Set record time
750 750  
938 +AT+APN     : Get or set the APN
939 +
940 +AT+FBAND   : Get or Set whether to automatically modify the frequency band
941 +
942 +AT+DNSCFG  : Get or Set DNS Server
943 +
944 +AT+GETSENSORVALUE   : Returns the current sensor measurement
945 +
946 +AT+NOUD      : Get or Set the number of data to be uploaded
947 +
948 +AT+CDP     : Read or Clear cached data
949 +
950 +AT+SHTEMP: Get or Set alarm of temp
951 +
952 +AT+SHHUM: Get or Set alarm of moisture
953 +
751 751  (% style="color:#037691" %)**COAP Management**      
752 752  
753 753  AT+URI            : Resource parameters
... ... @@ -781,6 +781,7 @@
781 781  
782 782  = ​5.  FAQ =
783 783  
987 +
784 784  == 5.1 ​ How to Upgrade Firmware ==
785 785  
786 786  
... ... @@ -793,13 +793,18 @@
793 793  )))
794 794  
795 795  (((
796 -(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.
1000 +
1001 +
1002 +(((
1003 +(% style="color:red" %)**Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.**
797 797  )))
1005 +)))
798 798  
799 799  
800 800  
801 801  = 6.  Trouble Shooting =
802 802  
1011 +
803 803  == 6.1  ​Connection problem when uploading firmware ==
804 804  
805 805  
... ... @@ -815,6 +815,7 @@
815 815  
816 816  == 6.2  AT Command input doesn't work ==
817 817  
1027 +
818 818  (((
819 819  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.
820 820  
... ... @@ -825,7 +825,7 @@
825 825  = 7. ​ Order Info =
826 826  
827 827  
828 -Part Number**:** (% style="color:#4f81bd" %)**NSDDS75**
1038 +Part Number**:** (% style="color:#4f81bd" %)**N95S31B-YY**
829 829  
830 830  
831 831  (% class="wikigeneratedid" %)
... ... @@ -840,7 +840,7 @@
840 840  
841 841  (% style="color:#037691" %)**Package Includes**:
842 842  
843 -* NSE01 NB-IoT Distance Detect Sensor Node x 1
1053 +* N95S31B NB-IoT Temperature and Humidity Sensor
844 844  * External antenna x 1
845 845  )))
846 846  
... ... @@ -849,11 +849,10 @@
849 849  
850 850  (% style="color:#037691" %)**Dimension and weight**:
851 851  
852 -
853 853  * Device Size: 13.0 x 5 x 4.5 cm
854 854  * Device Weight: 150g
855 -* Package Size / pcs : 15 x 12x 5.5 cm
856 -* Weight / pcs : 220g
1064 +* Package Size / pcs : 14.0 x 8x 5 cm
1065 +* Weight / pcs : 180g
857 857  )))
858 858  
859 859  (((
... ... @@ -865,5 +865,6 @@
865 865  
866 866  = 9.  Support =
867 867  
1077 +
868 868  * 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.
869 869  * 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]]
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
1657520100595-569.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +126.1 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
image-20220908154949-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.David
Size
... ... @@ -1,0 +1,1 @@
1 +58.5 KB
Content
image-20220908163102-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.David
Size
... ... @@ -1,0 +1,1 @@
1 +29.7 KB
Content

Applications

Navigation

Copyright ©2010-2022 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0