Summary

• Page properties (1 modified, 0 added, 0 removed)
• Attachments (0 modified, 18 added, 0 removed)
  • 1657350248151-650.png
  • 1657350625843-586.png
  • 1657351240556-536.png
  • 1657351312545-300.png
  • 1657352146020-183.png
  • 1657352185396-303.png
  • 1657352391268-297.png
  • 1657352403317-397.png
  • 1657352634421-276.png
  • 1657352645687-385.png
  • 1657352898400-901.png
  • 1657352914475-252.png
  • 1657354294009-643.png
  • 1657520100595-569.png
  • image-20220709150546-2.png
  • image-20220709161741-3.png
  • image-20220908154949-1.png
  • image-20220908163102-2.png

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

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-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