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