Skip to Content
Last modified by Mengting Qiu on 2024/04/02 16:44
From version 108.1
edited by Xiaoling
on 2022/07/09 15:39
Change comment: Uploaded new attachment "1657352391268-297.png", version {1}
To version 129.35
edited by Xiaoling
on 2023/04/03 16:57
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -9,6 +9,7 @@
9 9  
10 10  **Table of Contents:**
11 11  
12 +{{toc/}}
12 12  
13 13  
14 14  
... ... @@ -21,16 +21,29 @@
21 21  (((
22 22  
23 23  
25 +(((
24 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*.
27 +)))
25 25  
29 +(((
26 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.
31 +)))
27 27  
33 +(((
28 28  N95S31B supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP**(%%) for different application requirement.
35 +)))
29 29  
37 +(((
30 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).
39 +)))
31 31  
41 +(((
42 +
43 +)))
32 32  
45 +(((
33 33  ~* make sure you have NB-IoT coverage locally.
47 +)))
34 34  
35 35  
36 36  )))
... ... @@ -54,7 +54,6 @@
54 54  * 8500mAh Battery for long term use
55 55  
56 56  
57 -
58 58  == 1.3  Specification ==
59 59  
60 60  
... ... @@ -74,7 +74,6 @@
74 74  
75 75  (% style="color:#037691" %)**Battery:**
76 76  
77 -
78 78  * Li/SOCI2 un-chargeable battery
79 79  * Capacity: 8500mAh
80 80  * Self Discharge: <1% / Year @ 25°C
... ... @@ -82,9 +82,9 @@
82 82  * Max boost current: 2A, 1 second
83 83  
84 84  
85 -
86 86  == ​1.4  Applications ==
87 87  
99 +
88 88  * Smart Buildings & Home Automation
89 89  * Logistics and Supply Chain Management
90 90  * Smart Metering
... ... @@ -96,43 +96,49 @@
96 96  ​
97 97  
98 98  
99 -== 1.5  Pin Definitions ==
111 +== 1.5  Pin Definitions & Switch ==
100 100  
113 +
101 101  N95S31B use the mother board from NBSN95 which as below.
102 102  
116 +
103 103  [[image:image-20220709144723-1.png]]
104 104  
105 105  
106 106  === 1.5.1 Jumper JP2 ===
107 107  
122 +
108 108  Power on Device when put this jumper.
109 109  
110 110  
111 -
112 112  === 1.5.2 BOOT MODE / SW1 ===
113 113  
114 -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.
115 115  
116 -2) Flash: work mode, device starts to work and send out console output for further debug
129 +(((
130 +**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.
131 +)))
117 117  
133 +(((
134 +**2) Flash:**  work mode, device starts to work and send out console output for further debug
135 +)))
118 118  
119 119  
120 120  === 1.5.3 Reset Button ===
121 121  
140 +
122 122  Press to reboot the device.
123 123  
124 124  
125 -
126 126  === 1.5.4 LED ===
127 127  
146 +
128 128  It will flash:
129 129  
130 -1. When boot the device in flash mode
131 -1. Send an uplink packet
149 +1.  When boot the device in flash mode
132 132  
151 +2.  Send an uplink packet
133 133  
134 134  
135 -
136 136  = 2.  Use N95S31B to communicate with IoT Server =
137 137  
138 138  == 2.1  How it works ==
... ... @@ -151,7 +151,7 @@
151 151  
152 152  )))
153 153  
154 -[[image:1657350248151-650.png]]
172 +[[image:1657520100595-569.png]]
155 155  
156 156  (((
157 157  
... ... @@ -160,7 +160,6 @@
160 160  
161 161  == 2.2 ​ Configure the N95S31B ==
162 162  
163 -
164 164  === 2.2.1  Power On N95S31B ===
165 165  
166 166  
... ... @@ -167,27 +167,48 @@
167 167  [[image:image-20220709150546-2.png]]
168 168  
169 169  
170 -=== 2.2.1 Test Requirement ===
187 +=== 2.2.2 Test Requirement ===
171 171  
172 172  
190 +(((
173 173  To use N95S31B in your city, make sure meet below requirements:
192 +)))
174 174  
175 -* Your local operator has already distributed a NB-IoT Network there.
176 -* The local NB-IoT network used the band that N95S31B supports.
177 -* Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
194 +* (((
195 +Your local operator has already distributed a NB-IoT Network there.
196 +)))
197 +* (((
198 +The local NB-IoT network used the band that N95S31B supports.
199 +)))
200 +* (((
201 +Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
202 +)))
178 178  
179 -
204 +(((
180 180  Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.
206 +)))
181 181  
208 +(((
182 182  N95S31B supports different communication protocol such as :
210 +)))
183 183  
184 184  (((
185 -* CoAP  ((% style="color:red" %)120.24.4.116:5683(%%))
186 -* raw UDP  ((% style="color:red" %)120.24.4.116:5601(%%))
187 -* MQTT  ((% style="color:red" %)120.24.4.116:1883(%%))
188 -* TCP  ((% style="color:red" %)120.24.4.116:5600(%%))
213 +* (((
214 +CoAP  ((% style="color:red" %)120.24.4.116:5683(%%))
215 +)))
216 +* (((
217 +raw UDP  ((% style="color:red" %)120.24.4.116:5601(%%))
218 +)))
219 +* (((
220 +MQTT  ((% style="color:red" %)120.24.4.116:1883(%%))
221 +)))
222 +* (((
223 +TCP  ((% style="color:red" %)120.24.4.116:5600(%%))
224 +)))
189 189  
226 +(((
190 190  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.
228 +)))
191 191  
192 192  
193 193  )))
... ... @@ -195,9 +195,9 @@
195 195  [[image:1657350625843-586.png]]
196 196  
197 197  
198 -
199 199  === 2.2.3  Insert SIM card ===
200 200  
238 +
201 201  (((
202 202  Insert the NB-IoT Card get from your provider.
203 203  )))
... ... @@ -210,26 +210,29 @@
210 210  [[image:1657351240556-536.png]]
211 211  
212 212  
213 -
214 214  === 2.2.4  Connect USB – TTL to N95S31B to configure it ===
215 215  
253 +
216 216  (((
217 217  (((
218 218  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.
257 +
258 +
219 219  )))
220 220  )))
221 221  
222 222  [[image:1657351312545-300.png]]
223 223  
224 -**Connection:**
225 225  
226 - (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
265 +(% style="color:blue" %)**Connection:**
227 227  
228 - (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD
267 + (% style="background-color:yellow" %)**USB TTL GND <~-~-~-~-> GND**
229 229  
230 - (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD
269 +**~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)**
231 231  
271 +**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)**
232 232  
273 +
233 233  In the PC, use below serial tool settings:
234 234  
235 235  * Baud:  (% style="color:green" %)**9600**
... ... @@ -244,17 +244,18 @@
244 244  
245 245  [[image:1657329814315-101.png]]
246 246  
288 +
247 247  (((
248 -(% 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/]]
290 +(% 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]]**
249 249  )))
250 250  
251 251  
252 -
253 253  === 2.2.5  Use CoAP protocol to uplink data ===
254 254  
255 -(% 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/]]
256 256  
297 +(% 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/]]**
257 257  
299 +
258 258  (((
259 259  **Use below commands:**
260 260  )))
... ... @@ -263,10 +263,10 @@
263 263  (% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
264 264  )))
265 265  * (((
266 -(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
308 +(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
267 267  )))
268 268  * (((
269 -(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
311 +(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/  Set COAP resource path
270 270  )))
271 271  
272 272  (((
... ... @@ -285,7 +285,6 @@
285 285  [[image:1657352185396-303.png]]
286 286  
287 287  
288 -
289 289  === 2.2.6  Use UDP protocol to uplink data(Default protocol) ===
290 290  
291 291  
... ... @@ -293,50 +293,57 @@
293 293  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
294 294  * (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/ If the server does not respond, this command is unnecessary
295 295  
296 -[[image:1657330501006-241.png]]
337 +[[image:1657352391268-297.png]]
297 297  
298 298  
299 -[[image:1657330533775-472.png]]
340 +[[image:1657352403317-397.png]]
300 300  
301 301  
343 +=== 2.2.7  Use MQTT protocol to uplink data ===
302 302  
303 -=== 2.2.6 Use MQTT protocol to uplink data ===
304 304  
346 +N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption.
305 305  
306 -* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
307 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
308 -* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
309 -* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
310 -* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password of MQTT
311 -* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/Set the sending topic of MQTT
312 -* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%) ~/~/Set the subscription topic of MQTT
348 +* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/  Set to use MQTT protocol to uplink
349 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/  Set MQTT server address and port
350 +* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/  Set up the CLIENT of MQTT
351 +* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/  Set the username of MQTT
352 +* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/  Set the password of MQTT
353 +* (% style="color:blue" %)**AT+PUBTOPIC=f9527                               **(%%)~/~/  Set the sending topic of MQTT
354 +* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527          **(%%) ~/~/  Set the subscription topic of MQTT
313 313  
314 -[[image:1657249978444-674.png]]
356 +[[image:1657352634421-276.png]]
315 315  
316 316  
317 -[[image:1657330723006-866.png]]
359 +[[image:1657352645687-385.png]]
318 318  
319 319  
320 320  (((
321 -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.
363 +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.
322 322  )))
323 323  
324 324  
367 +(((
368 +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.
369 +)))
325 325  
326 -=== 2.2.7 Use TCP protocol to uplink data ===
327 327  
372 +=== 2.2.8  Use TCP protocol to uplink data ===
328 328  
374 +
375 +This feature is supported since firmware version v110
376 +
329 329  * (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
330 330  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
331 331  
332 -[[image:image-20220709093918-1.png]]
380 +[[image:1657352898400-901.png]]
333 333  
334 334  
335 -[[image:image-20220709093918-2.png]]
383 +[[image:1657352914475-252.png]]
336 336  
337 337  
386 +=== 2.2.9  Change Update Interval ===
338 338  
339 -=== 2.2.8 Change Update Interval ===
340 340  
341 341  User can use below command to change the (% style="color:green" %)**uplink interval**.
342 342  
... ... @@ -343,164 +343,244 @@
343 343  * (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
344 344  
345 345  (((
346 -(% style="color:red" %)**NOTE:**
394 +
347 347  )))
348 348  
349 349  (((
350 -(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
398 +(% style="color:red" %)**NOTE: Since firmware version is v1.2:**
351 351  )))
352 352  
401 +(((
402 +(% 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).**
403 +)))
353 353  
354 354  
355 355  == 2.3  Uplink Payload ==
356 356  
357 -In this mode, uplink payload includes in total 14 bytes
358 358  
409 +(((
410 +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.
411 +)))
359 359  
360 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
361 -|=(% style="width: 60px;" %)(((
362 -**Size(bytes)**
363 -)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1**
364 -|(% 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"]]
365 365  
366 366  (((
367 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data.
415 +For example:
368 368  )))
369 369  
418 +(((
419 + (% 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.
420 +)))
370 370  
371 -[[image:1657331036973-987.png]]
372 372  
373 373  (((
374 -The payload is ASCII string, representative same HEX:
424 +The uplink payloads are composed in  ASCII String. For example:
375 375  )))
376 376  
377 377  (((
378 -0x72403155615900640c6c19029200 where:
428 +0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:
379 379  )))
380 380  
381 -* (((
382 -Device ID: 0x724031556159 = 724031556159
431 +(((
432 +0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes
383 383  )))
384 -* (((
385 -Version: 0x0064=100=1.0.0
434 +
435 +
436 +(((
437 +(% style="color:red" %)**NOTE:**
386 386  )))
387 387  
388 -* (((
389 -BAT: 0x0c6c = 3180 mV = 3.180V
440 +(% style="color:red" %)
441 +1. (((
442 +**All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].**
390 390  )))
391 -* (((
392 -Signal: 0x19 = 25
393 -)))
394 -* (((
395 -Distance: 0x0292= 658 mm
396 -)))
397 -* (((
398 -Interrupt: 0x00 = 0
444 +1. (((
445 +**By default, the device will send an uplink message every 1 hour.**
399 399  
400 400  
401 -
402 402  
403 403  )))
404 404  
405 -== 2.4  Payload Explanation and Sensor Interface ==
451 +=== 2.3.1  Payload Analyze ===
406 406  
453 +==== 2.3.1.1  Before Firmware v1.2 ====
407 407  
408 -=== 2.4.1  Device ID ===
409 409  
456 +N95S31B uplink payload includes in total 21 bytes
457 +
458 +
459 +(% border="1" style="background-color:#ffffcc; color:green; width:520px" %)
460 +|=(% style="width: 50px;" %)**Size(bytes)**|=(% style="width: 45px;" %)**6**|=(% style="width: 25px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 65px;" %)**1**|=(% style="width: 50px;" %)1|=(% style="width: 120px;" %)5|=(% style="width: 70px;" %)**2**|=(% style="width: 70px;" %)**2**
461 +|(% 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:162px" %)(((
410 410  (((
411 -By default, the Device ID equal to the last 6 bytes of IMEI.
463 +Reserve/ Same as NBSN95 CFGMOD=1
412 412  )))
413 413  
414 414  (((
415 -User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
467 +No function here.
416 416  )))
469 +)))|(% style="width:102px" %)(((
470 +(((
471 +[[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]]
472 +)))
417 417  
418 418  (((
419 -**Example:**
475 +By SHT31
420 420  )))
477 +)))|(% style="width:81px" %)(((
478 +(((
479 +[[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]]
480 +)))
421 421  
422 422  (((
423 -AT+DEUI=A84041F15612
483 +By SHT31
424 424  )))
485 +)))
425 425  
426 426  (((
427 -The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
488 +
489 +
490 +(((
491 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
428 428  )))
493 +)))
429 429  
430 430  
496 +[[image:1657354294009-643.png]]
431 431  
432 -=== 2.4.2  Version Info ===
433 433  
434 -(((
435 -Specify the software version: 0x64=100, means firmware version 1.00.
436 -)))
499 +The payload is ASCII string, representative same HEX: (% style="background-color:yellow" %)**0x724031607457 006e 0ccd 1b 01 00dc000ccc 00e1 0186**
437 437  
438 -(((
439 -For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0.
440 -)))
501 +**where:**
441 441  
503 +* (% style="color:#037691" %)**Device ID:** (%%) 0x724031607457 = 724031607457
442 442  
505 +* (% style="color:#037691" %)**Version: **(%%) 0x006e=110=1.1.0
443 443  
444 -=== 2.4.3  Battery Info ===
507 +* (% style="color:#037691" %)**BAT:**   (%%) 0x0ccd = 3277 mV = 3.277V
445 445  
446 -(((
447 -Ex1: 0x0B45 = 2885mV
448 -)))
509 +* (% style="color:#037691" %)**Signal:** (%%) 0x1b = 27
449 449  
450 -(((
451 -Ex2: 0x0B49 = 2889mV
452 -)))
511 +* (% style="color:#037691" %)**Model:** (%%) 0x01 = 1
453 453  
513 +* (% style="color:#037691" %)**0x00dc000ccc= reserve, ignore in N95S31B**
454 454  
515 +* (% style="color:#037691" %)**Temperature by SHT31:** (%%) 0x00e1 = 225 = 22.5 °C
455 455  
456 -=== 2.4.4  Signal Strength ===
517 +* (% style="color:#037691" %)**Humidity by SHT31:**  (%%) 0x0186 = 390 = 39.0 %rh
457 457  
458 458  (((
459 -NB-IoT Network signal Strength.
460 -)))
520 +
461 461  
462 -(((
463 -**Ex1: 0x1d = 29**
522 +
523 +
464 464  )))
465 465  
526 +==== 2.3.1.2 Since Firmware v1.2 ====
527 +
528 +
529 +In this mode, uplink payload includes 91 bytes in total by default.
530 +
531 +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.
532 +
533 +
534 +(% border="1" style="background-color:#ffffcc; color:green; width:520px" %)
535 +|=(% scope="row" style="width: 50px;" %)**Size(bytes)**|(% style="width:40px" %)**8**|(% style="width:20px" %)**2**|(% style="width:20px" %)**2**|(% style="width:30px" %)**1**|(% style="width:20px" %)**1**|(% style="width:55px" %)**2**|(% style="width:35px" %)**1**|(% style="width:20px" %)**2**|(% style="width:40px" %)**2**|(% style="width:40px" %)**2**|(% style="width:30px" %)**4**|(% style="width:40px" %)**2**|(% style="width:40px" %)**2**|(% style="width:35px" %)**4**
536 +|=(% style="width: 95px;" %)**Value**|(% style="width:82px" %)Device ID|(% style="width:43px" %)Ver|(% style="width:47px" %)BAT|(% style="width:124px" %)Signal Strength|(% style="width:56px" %)MOD|(% style="width:109px" %)TemDS18B20|(% style="width:80px" %)Interrupt|(% style="width:51px" %)ADC|(% style="width:79px" %)SHTTEM|(% style="width:84px" %)SHTHUM|(% style="width:100px" %)Time stamp |(% style="width:76px" %)SHTTEM|(% style="width:81px" %)SHTHUM|(% style="width:121px" %)Time stamp .....
537 +
538 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the N95S31B uplink data.
539 +
540 +
541 +[[image:image-20220908154949-1.png]]
542 +
543 +
544 +The payload is ASCII string, representative same HEX:
545 +
546 +**0x (% style="color:red" %)__f868411056758782__ (% style="color:blue" %)__000c__ (% style="color:green" %)__0d0f__ (% style="color:#00b0f0" %)__0c__ (% style="color:#7030a0" %)__01__ (% style="color:#d60093" %)__0000__ (% style="color:#a14d07" %)__00__ __0030__ (% style="color:#0020b0" %)__0114__ (% style="color:#420042" %)__0231__ (% style="color:#663300" %)__63199d3c__ (%%)__0113023163199d12__ __0113023163199c5e__// //__0112023763199baa__ __0112023263199af6__// //__0111023b631999a7__ **
547 +
548 +**__0112023b631998f3__// //__011202426319983f__ __01110242631996eb__**
549 +
550 +**where:**
551 +
552 +* (% style="color:#037691" %)**Device ID:**(%%) f868411056758782 = f868411056758782
553 +
554 +* (% style="color:#037691" %)**Version:** (%%)0x000c=120=1.2
555 +
556 +* (% style="color:#037691" %)**BAT:**      (%%)0x0d0f = 3343 mV = 3.343V
557 +
558 +* (% style="color:#037691" %)**Singal:**(%%)  0x0c = 12
559 +
560 +* (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
561 +
562 +* (% style="color:#037691" %)**TemDS18B20:**(%%)  0x0000= 0 = 0
563 +
564 +* (% style="color:#037691" %)**Interrupt:**  (%%)0x00= 0
565 +
566 +* (% style="color:#037691" %)**adc:**(%%)  0x0030= 48
567 +
568 +* (% style="color:#037691" %)**SHTTEM:**(%%)  0x0114= 276 = 27.6
569 +
570 +* (% style="color:#037691" %)**SHTHUM:**(%%)  0x0231 =561=56.1%
571 +
572 +* (% style="color:#037691" %)**Time stamp :  **(%%)0x63199d3c =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
573 +
574 +* (% style="color:#037691" %)**SHTTEM,SHTHUM,Time stamp :**(%%)  0113023163199d12
575 +
576 +* (% style="color:#037691" %)**8 sets of recorded data:**(%%)** **SHTTEM,SHTHUM,Time stamp : 0113023163199c5e, .......
577 +
578 +
579 +=== 2.3.2  Device ID ===
580 +
581 +
466 466  (((
467 -(% style="color:blue" %)**0**(%%)  -113dBm or less
583 +By default, the Device ID equal to the last 6 bytes of IMEI.
468 468  )))
469 469  
470 470  (((
471 -(% style="color:blue" %)**1**(%%)  -111dBm
587 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
588 +
589 +
472 472  )))
473 473  
474 474  (((
475 -(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
593 +(% style="color:blue" %)**Example:**
476 476  )))
477 477  
478 478  (((
479 -(% style="color:blue" %)**31**  (%%) -51dBm or greater
597 +AT+DEUI=A84041F15612
480 480  )))
481 481  
482 482  (((
483 -(% style="color:blue" %)**99**   (%%) Not known or not detectable
601 +The Device ID is stored in a none-erase area, Upgrade the firmware or run (% style="color:blue" %)**AT+FDR**(%%) won't erase Device ID.
602 +
603 +
484 484  )))
485 485  
606 +(% style="color:red" %)**NOTE: When the firmware version is v1.2 and later firmware:**
486 486  
487 487  
488 -=== 2.4.5  Distance ===
609 +By default, the Device ID equal to the last 15 bits of IMEI.
489 489  
490 -Get the distance. Flat object range 280mm - 7500mm.
611 +User can use ** (% style="color:blue" %)AT+DEUI(%%)** to set Device ID
491 491  
613 +
614 +(% style="color:blue" %)**Example:**
615 +
616 +AT+DEUI=868411056754138
617 +
618 +
619 +=== 2.3.3  Version Info ===
620 +
621 +
492 492  (((
493 -For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is
623 +These bytes include the hardware and software version.
494 494  )))
495 495  
496 496  (((
497 -(((
498 -(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.**
627 +Higher byte: Specify hardware version: always 0x00 for N95S31B
499 499  )))
500 -)))
501 501  
502 502  (((
503 -
631 +Lower byte: Specify the software version: 0x6E=110, means firmware version 110
504 504  )))
505 505  
506 506  (((
... ... @@ -507,65 +507,81 @@
507 507  
508 508  )))
509 509  
510 -=== 2.4.6  Digital Interrupt ===
511 -
512 512  (((
513 -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.
639 +For example: 0x00 6E: this device is N95S31B with firmware version 110.
514 514  )))
515 515  
516 516  (((
517 -The command is:
643 +
518 518  )))
519 519  
646 +=== 2.3.4  Battery Info ===
647 +
648 +
520 520  (((
521 -(% 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]])**.**
650 +Ex1: 0x0B45 = 2885mV
522 522  )))
523 523  
524 -
525 525  (((
526 -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.
654 +Ex2: 0x0B49 = 2889mV
527 527  )))
528 528  
529 529  
658 +=== 2.3.5  Signal Strength ===
659 +
660 +
530 530  (((
531 -Example:
662 +NB-IoT Network signal Strength.
532 532  )))
533 533  
534 534  (((
535 -0x(00): Normal uplink packet.
666 +**Ex1: 0x1d = 29**
536 536  )))
537 537  
538 538  (((
539 -0x(01): Interrupt Uplink Packet.
670 +(% style="color:blue" %)**0**(%%)  -113dBm or less
540 540  )))
541 541  
542 -
543 -
544 -=== 2.4.7  ​+5V Output ===
545 -
546 546  (((
547 -NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 
674 +(% style="color:blue" %)**1**(%%)  -111dBm
548 548  )))
549 549  
550 -
551 551  (((
552 -The 5V output time can be controlled by AT Command.
678 +(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
553 553  )))
554 554  
555 555  (((
556 -(% style="color:blue" %)**AT+5VT=1000**
682 +(% style="color:blue" %)**31**  (%%) -51dBm or greater
557 557  )))
558 558  
559 559  (((
560 -Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.
686 +(% style="color:blue" %)**99**   (%%) Not known or not detectable
561 561  )))
562 562  
563 563  
690 +=== 2.3.6  Temperature & Humidity ===
564 564  
565 -== 2.5  Downlink Payload ==
566 566  
567 -By default, NDDS75 prints the downlink payload to console port.
693 +The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server.
568 568  
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 +== 2.4  Downlink Payload ==
709 +
710 +
711 +By default, N95S31B prints the downlink payload to console port.
712 +
569 569  [[image:image-20220709100028-1.png]]
570 570  
571 571  
... ... @@ -602,7 +602,7 @@
602 602  )))
603 603  
604 604  (((
605 -If payload = 0x04FF, it will reset the NDDS75
749 +If payload = 0x04FF, it will reset the N95S31B
606 606  )))
607 607  
608 608  
... ... @@ -613,144 +613,99 @@
613 613  )))
614 614  
615 615  
760 +== 2.5  Humidity and Temperature alarm function ==
616 616  
617 -== 2.6  ​LED Indicator ==
618 618  
763 +**~ (% style="color:blue" %)➢ AT Command:(%%)**
619 619  
620 -The NDDS75 has an internal LED which is to show the status of different state.
621 621  
766 +(% style="color:#037691" %)**AT+ SHHUM=min,max**
622 622  
623 -* 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)
624 -* Then the LED will be on for 1 second means device is boot normally.
625 -* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
626 -* For each uplink probe, LED will be on for 500ms.
627 627  
628 -(((
629 -
630 -)))
769 +² When min=0, and max≠0, Alarm higher than max
631 631  
771 +² When min≠0, and max=0, Alarm lower than min
632 632  
773 +² When min≠0 and max≠0, Alarm higher than max or lower than min
633 633  
634 -== 2.7  ​Firmware Change Log ==
635 635  
776 + (% style="color:blue" %)**Example:**
636 636  
637 -(((
638 -Download URL & Firmware Change log
639 -)))
778 +AT+ SHHUM=50,80 ~/~/ Alarm when humidity lower than 50.
640 640  
641 -(((
642 -[[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/]]
643 -)))
644 644  
781 +(% style="color:#037691" %)**AT+ SHTEMP=min,max**
645 645  
646 -(((
647 -Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
648 -)))
783 +² When min=0, and max≠0, Alarm higher than max
649 649  
785 +² When min≠0, and max=0, Alarm lower than min
650 650  
787 +² When min≠0 and max≠0, Alarm higher than max or lower than min
651 651  
652 -== 2.8  ​Battery Analysis ==
653 653  
654 -=== 2.8.1  ​Battery Type ===
790 +**~ (% style="color:blue" %)Example:(%%)**
655 655  
792 +AT+ SHTEMP=20,30 ~/~/ Alarm when temperature lower than 20.
656 656  
657 -(((
658 -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.
659 -)))
660 660  
661 -(((
662 -The battery is designed to last for several years depends on the actually use environment and update interval. 
663 -)))
795 +== 2.6 Set the number of data to be uploaded and the recording time ==
664 664  
665 -(((
666 -The battery related documents as below:
667 -)))
668 668  
669 -* [[Battery Dimension>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
670 -* [[Lithium-Thionyl Chloride Battery datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
671 -* [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
798 +**~ (% style="color:blue" %)➢ AT Command:(%%)**
672 672  
673 -(((
674 -[[image:image-20220709101450-2.png]]
675 -)))
800 +* (% style="color:#037691" %)**AT+TR=900**     (%%)~/~/  The unit is seconds, and the default is to record data once every 900 seconds.( The minimum can be set to 180 seconds)
801 +* (% style="color:#037691" %)**AT+NOUD=8**  (%%)~/~/  The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
676 676  
803 + The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:**
677 677  
805 +[[image:image-20221009001045-1.png||height="726" width="1009"]]
678 678  
679 -=== 2.8.2  Power consumption Analyze ===
680 680  
681 -(((
682 -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.
683 -)))
808 +== 2.7 Read or Clear cached data ==
684 684  
685 685  
686 -(((
687 -Instruction to use as below:
688 -)))
811 +**~ (% style="color:blue" %)➢ AT Command:(%%)**
689 689  
690 -(((
691 -(% 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/]]
692 -)))
813 +* (% style="color:#037691" %)**AT+CDP**  (%%) ~/~/ Read cached data
814 +* (% style="color:#037691" %)**AT+CDP=0** (%%) ~/~/  Clear cached data
693 693  
816 +[[image:image-20220908163102-2.png]]
694 694  
695 -(((
696 -(% style="color:blue" %)**Step 2: **(%%) Open it and choose
697 -)))
698 698  
699 -* (((
700 -Product Model
701 -)))
702 -* (((
703 -Uplink Interval
704 -)))
705 -* (((
706 -Working Mode
707 -)))
819 += 2.8 Battery & Power Consumption =
708 708  
709 -(((
710 -And the Life expectation in difference case will be shown on the right.
711 -)))
712 712  
713 -[[image:image-20220709110451-3.png]]
822 +N95S31B uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace.
714 714  
824 +[[**Battery Info & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] .
715 715  
716 716  
717 -=== 2.8.3  ​Battery Note ===
827 +
718 718  
719 -(((
720 -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.
721 -)))
829 += 3. ​ Access NB-IoT Module =
722 722  
723 723  
724 -
725 -=== 2.8.4  Replace the battery ===
726 -
727 727  (((
728 -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).
729 -)))
730 -
731 -
732 -
733 -= 3. ​ Access NB-IoT Module =
734 -
735 -(((
736 736  Users can directly access the AT command set of the NB-IoT module.
737 737  )))
738 738  
739 739  (((
740 740  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/]] 
838 +
839 +
741 741  )))
742 742  
743 743  [[image:1657333200519-600.png]]
744 744  
745 745  
746 -
747 747  = 4.  Using the AT Commands =
748 748  
749 749  == 4.1  Access AT Commands ==
750 750  
751 -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/]]
752 752  
850 +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]]
753 753  
852 +
754 754  AT+<CMD>?  : Help on <CMD>
755 755  
756 756  AT+<CMD>         : Run <CMD>
... ... @@ -790,7 +790,24 @@
790 790  
791 791  AT+SERVADDR  : Server Address
792 792  
892 +AT+TR      : Get or Set record time
793 793  
894 +AT+APN     : Get or set the APN
895 +
896 +AT+FBAND   : Get or Set whether to automatically modify the frequency band
897 +
898 +AT+DNSCFG  : Get or Set DNS Server
899 +
900 +AT+GETSENSORVALUE   : Returns the current sensor measurement
901 +
902 +AT+NOUD      : Get or Set the number of data to be uploaded
903 +
904 +AT+CDP     : Read or Clear cached data
905 +
906 +AT+SHTEMP: Get or Set alarm of temp
907 +
908 +AT+SHHUM: Get or Set alarm of moisture
909 +
794 794  (% style="color:#037691" %)**COAP Management**      
795 795  
796 796  AT+URI            : Resource parameters
... ... @@ -821,7 +821,6 @@
821 821  AT+PWORD  : Serial Access Password
822 822  
823 823  
824 -
825 825  = ​5.  FAQ =
826 826  
827 827  == 5.1 ​ How to Upgrade Firmware ==
... ... @@ -836,11 +836,14 @@
836 836  )))
837 837  
838 838  (((
839 -(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.
954 +
955 +
956 +(((
957 +(% style="color:red" %)**Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.**
840 840  )))
959 +)))
841 841  
842 842  
843 -
844 844  = 6.  Trouble Shooting =
845 845  
846 846  == 6.1  ​Connection problem when uploading firmware ==
... ... @@ -855,9 +855,9 @@
855 855  
856 856  )))
857 857  
858 -
859 859  == 6.2  AT Command input doesn't work ==
860 860  
978 +
861 861  (((
862 862  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.
863 863  
... ... @@ -864,18 +864,12 @@
864 864  
865 865  )))
866 866  
867 -
868 868  = 7. ​ Order Info =
869 869  
870 870  
871 -Part Number**:** (% style="color:#4f81bd" %)**NSDDS75**
988 +Part Number**:** (% style="color:#4f81bd" %)**N95S31B-YY**
872 872  
873 873  
874 -(% class="wikigeneratedid" %)
875 -(((
876 -
877 -)))
878 -
879 879  = 8.  Packing Info =
880 880  
881 881  (((
... ... @@ -883,7 +883,7 @@
883 883  
884 884  (% style="color:#037691" %)**Package Includes**:
885 885  
886 -* NSE01 NB-IoT Distance Detect Sensor Node x 1
998 +* N95S31B NB-IoT Temperature and Humidity Sensor
887 887  * External antenna x 1
888 888  )))
889 889  
... ... @@ -892,21 +892,24 @@
892 892  
893 893  (% style="color:#037691" %)**Dimension and weight**:
894 894  
895 -
896 896  * Device Size: 13.0 x 5 x 4.5 cm
897 897  * Device Weight: 150g
898 -* Package Size / pcs : 15 x 12x 5.5 cm
899 -* Weight / pcs : 220g
1009 +* Package Size / pcs : 14.0 x 8x 5 cm
1010 +* Weight / pcs : 180g
900 900  )))
901 901  
902 902  (((
903 903  
904 904  
905 -
906 906  
907 907  )))
908 908  
909 909  = 9.  Support =
910 910  
1021 +
911 911  * 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.
912 912  * 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]]
1024 +
1025 +
1026 +
1027 +
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-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
image-20221009001045-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +282.9 KB
Content