Summary

• Page properties (2 modified, 0 added, 0 removed)
• Attachments (0 modified, 3 added, 0 removed)
  • 1657520100595-569.png
  • image-20220908154949-1.png
  • image-20220908163102-2.png

Details

Page properties

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.Xiaoling
	1	+XWiki.David

Content

...	...	@@ -17,6 +17,7 @@
17	17
18	18	= 1.  Introduction =
19	19
	20	+
20	20	== 1.1 ​ What is N95S31B NB-IoT Sensor Node ==
21	21
22	22	(((
...	...	@@ -55,6 +55,7 @@
55	55
56	56	== 1.2 ​ Features ==
57	57
	59	+
58	58	* NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
59	59	* Monitor Temperature & Humidity via SHT31
60	60	* AT Commands to change parameters
...	...	@@ -66,9 +66,6 @@
66	66	* Micro SIM card slot for NB-IoT SIM
67	67	* 8500mAh Battery for long term use
68	68
69		-
70		-
71		-
72	72	== 1.3  Specification ==
73	73
74	74
...	...	@@ -77,7 +77,6 @@
77	77	* Supply Voltage: 2.1v ~~ 3.6v
78	78	* Operating Temperature: -40 ~~ 85°C
79	79
80		-
81	81	(% style="color:#037691" %)**NB-IoT Spec:**
82	82
83	83	* - B1 @H-FDD: 2100MHz
...	...	@@ -87,7 +87,6 @@
87	87	* - B20 @H-FDD: 800MHz
88	88	* - B28 @H-FDD: 700MHz
89	89
90		-
91	91	(% style="color:#037691" %)**Battery:**
92	92
93	93	* Li/SOCI2 un-chargeable battery
...	...	@@ -96,11 +96,9 @@
96	96	* Max continuously current: 130mA
97	97	* Max boost current: 2A, 1 second
98	98
99		-
100		-
101		-
102	102	== ​1.4  Applications ==
103	103
	98	+
104	104	* Smart Buildings & Home Automation
105	105	* Logistics and Supply Chain Management
106	106	* Smart Metering
...	...	@@ -112,15 +112,20 @@
112	112	​
113	113
114	114
115		-== 1.5  Pin Definitions ==
116	116
	111	+== 1.5  Pin Definitions & Switch ==
	112	+
	113	+
117	117	N95S31B use the mother board from NBSN95 which as below.
118	118
	116	+
119	119	[[image:image-20220709144723-1.png]]
120	120
121	121
	120	+
122	122	=== 1.5.1 Jumper JP2 ===
123	123
	123	+
124	124	Power on Device when put this jumper.
125	125
126	126
...	...	@@ -127,6 +127,7 @@
127	127
128	128	=== 1.5.2 BOOT MODE / SW1 ===
129	129
	130	+
130	130	(((
131	131	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.
132	132	)))
...	...	@@ -139,6 +139,7 @@
139	139
140	140	=== 1.5.3 Reset Button ===
141	141
	143	+
142	142	Press to reboot the device.
143	143
144	144
...	...	@@ -145,16 +145,15 @@
145	145
146	146	=== 1.5.4 LED ===
147	147
	150	+
148	148	It will flash:
149	149
150	150	1. When boot the device in flash mode
151	151	1. Send an uplink packet
152	152
153		-
154		-
155		-
156	156	= 2.  Use N95S31B to communicate with IoT Server =
157	157
	158	+
158	158	== 2.1  How it works ==
159	159
160	160
...	...	@@ -171,7 +171,7 @@
171	171
172	172	)))
173	173
174		-[[image:1657350248151-650.png]]
	175	+[[image:1657520100595-569.png]]
175	175
176	176	(((
177	177
...	...	@@ -187,6 +187,7 @@
187	187	[[image:image-20220709150546-2.png]]
188	188
189	189
	191	+
190	190	=== 2.2.1 Test Requirement ===
191	191
192	192
...	...	@@ -239,6 +239,7 @@
239	239
240	240	=== 2.2.3  Insert SIM card ===
241	241
	244	+
242	242	(((
243	243	Insert the NB-IoT Card get from your provider.
244	244	)))
...	...	@@ -254,14 +254,18 @@
254	254
255	255	=== 2.2.4  Connect USB – TTL to N95S31B to configure it ===
256	256
	260	+
257	257	(((
258	258	(((
259	259	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	+
260	260	)))
261	261	)))
262	262
263	263	[[image:1657351312545-300.png]]
264	264
	271	+
265	265	**Connection:**
266	266
267	267	(% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
...	...	@@ -285,8 +285,9 @@
285	285
286	286	[[image:1657329814315-101.png]]
287	287
	295	+
288	288	(((
289		-(% 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/]]
	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]]**
290	290	)))
291	291
292	292
...	...	@@ -293,9 +293,10 @@
293	293
294	294	=== 2.2.5  Use CoAP protocol to uplink data ===
295	295
296		-(% 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/]]
297	297
	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/]]**
298	298
	307	+
299	299	(((
300	300	**Use below commands:**
301	301	)))
...	...	@@ -343,6 +343,7 @@
343	343
344	344	=== 2.2.7  Use MQTT protocol to uplink data ===
345	345
	355	+
346	346	N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption.
347	347
348	348	* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
...	...	@@ -358,6 +358,7 @@
358	358
359	359	[[image:1657352645687-385.png]]
360	360
	371	+
361	361	(((
362	362	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.
363	363	)))
...	...	@@ -371,6 +371,7 @@
371	371
372	372	=== 2.2.8  Use TCP protocol to uplink data ===
373	373
	385	+
374	374	This feature is supported since firmware version v110
375	375
376	376	* (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
...	...	@@ -385,6 +385,7 @@
385	385
386	386	=== 2.2.9  Change Update Interval ===
387	387
	400	+
388	388	User can use below command to change the (% style="color:green" %)**uplink interval**.
389	389
390	390	* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
...	...	@@ -393,13 +393,16 @@
393	393
394	394	)))
395	395
	409	+(% style="color:red" %)**NOTE:When the firmware version is v1.2 and later firmware:**
396	396
	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).**
397	397
	413	+
398	398	== 2.3  Uplink Payload ==
399	399
400	400
401	401	(((
402		-NBSN95 has different working mode for the connections of different type of sensors. This section describes these modes. User can use the AT Command (% style="color:blue" %)**AT+MOD**(%%) to set NBSN95 to different working modes.
	418	+N95S31B has different working mode for the connections of different type of sensors. This section describes these modes. User can use the AT Command (% style="color:blue" %)**AT+MOD**(%%) to set NBSN95 to different working modes.
403	403	)))
404	404
405	405
...	...	@@ -408,7 +408,7 @@
408	408	)))
409	409
410	410	(((
411		- (% style="color:blue" %)**AT+CFGMOD=2 ** (%%)~/~/will set the NBSN95 to work in MOD=2 distance mode which target to measure distance via Ultrasonic Sensor.
	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.
412	412	)))
413	413
414	414
...	...	@@ -431,15 +431,19 @@
431	431
432	432	(% style="color:red" %)
433	433	1. (((
434		-All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].
	450	+**All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].**
435	435	)))
436	436	1. (((
437		-By default, the device will send an uplink message every 1 hour.
438		-)))
	453	+**By default, the device will send an uplink message every 1 hour.**
439	439
440	440
	456	+
	457	+
	458	+)))
	459	+
441	441	=== 2.3.1  Payload Analyze ===
442	442
	462	+
443	443	N95S31B uplink payload includes in total 21 bytes
444	444
445	445
...	...	@@ -474,6 +474,8 @@
474	474	)))
475	475
476	476	(((
	497	+
	498	+
477	477	(((
478	478	If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
479	479	)))
...	...	@@ -500,12 +500,41 @@
500	500	)))
501	501
502	502	(((
503		-
	525	+(% style="color:red" %)**NOTE:When the firmware version is v1.2 and later firmware:**
504	504	)))
505	505
	528	+In this mode, uplink payload includes 91 bytes in total by default.
506	506
	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.
	531	+
	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 .....
	534	+
	535	+If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NSE01 uplink data.
	536	+
	537	+[[image:image-20220908154949-1.png]]
	538	+
	539	+The payload is ASCII string, representative same HEX:
	540	+
	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:
	542	+
	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(% style="color:red" %),SHTHUM,Time stamp : //**0113023163199c5e**//,.......
	556	+
507	507	=== 2.3.2  Device ID ===
508	508
	559	+
509	509	(((
510	510	By default, the Device ID equal to the last 6 bytes of IMEI.
511	511	)))
...	...	@@ -524,21 +524,44 @@
524	524
525	525	(((
526	526	The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
	578	+
	579	+
527	527	)))
528	528
	582	+(% style="color:red" %)**NOTE:When the firmware version is v1.2 and later firmware:**
529	529
530	530
	585	+By default, the Device ID equal to the last 15 bits of IMEI.
	586	+
	587	+User can use **AT+DEUI** to set Device ID
	588	+
	589	+**Example:**
	590	+
	591	+AT+DEUI=868411056754138
	592	+
	593	+
531	531	=== 2.3.3  Version Info ===
532	532
533	533
	597	+(((
534	534	These bytes include the hardware and software version.
	599	+)))
535	535
	601	+(((
536	536	Higher byte: Specify hardware version: always 0x00 for N95S31B
	603	+)))
537	537
	605	+(((
538	538	Lower byte: Specify the software version: 0x6E=110, means firmware version 110
	607	+)))
539	539
	609	+(((
	610	+
	611	+)))
540	540
	613	+(((
541	541	For example: 0x00 6E: this device is N95S31B with firmware version 110.
	615	+)))
542	542
543	543	(((
544	544
...	...	@@ -547,6 +547,7 @@
547	547
548	548	=== 2.3.4  Battery Info ===
549	549
	624	+
550	550	(((
551	551	Ex1: 0x0B45 = 2885mV
552	552	)))
...	...	@@ -559,6 +559,7 @@
559	559
560	560	=== 2.3.5  Signal Strength ===
561	561
	637	+
562	562	(((
563	563	NB-IoT Network signal Strength.
564	564	)))
...	...	@@ -591,6 +591,7 @@
591	591
592	592	=== 2.3.6  Temperature & Humidity ===
593	593
	670	+
594	594	The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server.
595	595
596	596	[[image:image-20220709161741-3.png]]
...	...	@@ -609,8 +609,9 @@
609	609
610	610	== 2.4  Downlink Payload ==
611	611
612		-By default, NDDS75 prints the downlink payload to console port.
613	613
	690	+By default, N95S31B prints the downlink payload to console port.
	691	+
614	614	[[image:image-20220709100028-1.png]]
615	615
616	616
...	...	@@ -647,7 +647,7 @@
647	647	)))
648	648
649	649	(((
650		-If payload = 0x04FF, it will reset the NDDS75
	728	+If payload = 0x04FF, it will reset the N95S31B
651	651	)))
652	652
653	653
...	...	@@ -658,12 +658,59 @@
658	658	)))
659	659
660	660
	739	+== 2.5 Humidity and Temperature alarm function ==
661	661
662		-== 2.5  ​Battery Analysis ==
	741	+➢ AT Command:
663	663
664		-=== 2.5.1  ​Battery Type ===
	743	+AT+ SHHUM=min,max
665	665
	745	+² When min=0, and max≠0, Alarm higher than max
666	666
	747	+² When min≠0, and max=0, Alarm lower than min
	748	+
	749	+² When min≠0 and max≠0, Alarm higher than max or lower than min
	750	+
	751	+Example:
	752	+
	753	+AT+ SHHUM=50,80 ~/~/ Alarm when humidity lower than 50.
	754	+
	755	+
	756	+AT+ SHTEMP=min,max
	757	+
	758	+² When min=0, and max≠0, Alarm higher than max
	759	+
	760	+² When min≠0, and max=0, Alarm lower than min
	761	+
	762	+² When min≠0 and max≠0, Alarm higher than max or lower than min
	763	+
	764	+Example:
	765	+
	766	+AT+ SHTEMP=20,30 ~/~/ Alarm when temperature lower than 20.
	767	+
	768	+== 2.6 Set the number of data to be uploaded and the recording time ==
	769	+
	770	+➢ AT Command:
	771	+
	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	+
	786	+== 2.8  ​Battery Analysis ==
	787	+
	788	+
	789	+=== 2.8.1  ​Battery Type ===
	790	+
	791	+
667	667	(((
668	668	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.
669	669	)))
...	...	@@ -686,10 +686,11 @@
686	686
687	687
688	688
689		-=== 2.5.2  Power consumption Analyze ===
	814	+=== 2.8.2  Power consumption Analyze ===
690	690
	816	+
691	691	(((
692		-The file **DRAGINO_N95S31B-Power-Analyzer.pdf** from [[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/]] describes a detail measurement to analyze the power consumption in different case. User can use it for design guideline for their project.
	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.
693	693	)))
694	694
695	695	(((
...	...	@@ -697,8 +697,9 @@
697	697	)))
698	698
699	699
700		-=== 2.5.3  ​Battery Note ===
	826	+=== 2.8.3  ​Battery Note ===
701	701
	828	+
702	702	(((
703	703	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.
704	704	)))
...	...	@@ -705,7 +705,7 @@
705	705
706	706
707	707
708		-=== 2.5.4  Replace the battery ===
	835	+=== 2.8.4  Replace the battery ===
709	709
710	710
711	711	(((
...	...	@@ -721,6 +721,7 @@
721	721
722	722	= 3. ​ Access NB-IoT Module =
723	723
	851	+
724	724	(((
725	725	Users can directly access the AT command set of the NB-IoT module.
726	726	)))
...	...	@@ -727,6 +727,8 @@
727	727
728	728	(((
729	729	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	+
730	730	)))
731	731
732	732	[[image:1657333200519-600.png]]
...	...	@@ -735,11 +735,13 @@
735	735
736	736	= 4.  Using the AT Commands =
737	737
	868	+
738	738	== 4.1  Access AT Commands ==
739	739
740		-See NBSN95 AT Command in this link for detail:  [[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN95/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN95/]]
741	741
	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]]
742	742
	874	+
743	743	AT+<CMD>?  : Help on <CMD>
744	744
745	745	AT+<CMD>         : Run <CMD>
...	...	@@ -779,7 +779,24 @@
779	779
780	780	AT+SERVADDR  : Server Address
781	781
	914	+AT+TR      : Get or Set record time
782	782
	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	+
783	783	(% style="color:#037691" %)**COAP Management**
784	784
785	785	AT+URI            : Resource parameters
...	...	@@ -813,6 +813,7 @@
813	813
814	814	= ​5.  FAQ =
815	815
	965	+
816	816	== 5.1 ​ How to Upgrade Firmware ==
817	817
818	818
...	...	@@ -827,13 +827,16 @@
827	827	(((
828	828
829	829
830		-(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.
	980	+(((
	981	+(% style="color:red" %)**Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.**
831	831	)))
	983	+)))
832	832
833	833
834	834
835	835	= 6.  Trouble Shooting =
836	836
	989	+
837	837	== 6.1  ​Connection problem when uploading firmware ==
838	838
839	839
...	...	@@ -849,6 +849,7 @@
849	849
850	850	== 6.2  AT Command input doesn't work ==
851	851
	1005	+
852	852	(((
853	853	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.
854	854
...	...	@@ -898,5 +898,8 @@
898	898
899	899	= 9.  Support =
900	900
	1055	+
901	901	* 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.
902	902	* 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]]
	1058	+
	1059	+

1657520100595-569.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+126.1 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