Changes for page LHT65N -- Manual do sensor de temperatura e umidade LoRaWAN

Summary

• Page properties (1 modified, 0 added, 0 removed)
• Attachments (0 modified, 14 added, 0 removed)
  • image-20220623110706-1.png
  • image-20220623110723-2.png
  • image-20220623111949-3.png
  • image-20220623112117-4.png
  • image-20220623113959-5.png
  • image-20220628150112-1.png
  • image-20220628150542-2.png
  • image-20220628150648-3.png
  • image-20220628150714-4.png
  • image-20220628151005-5.png
  • image-20220628151056-6.png
  • image-20220628151143-7.png
  • image-20220703111533-1.png
  • image-20220703111700-2.png

Details

Page properties

Content

...	...	@@ -1,5 +1,5 @@
1	1	(% style="text-align:center" %)
2		-[[image:image-20220613162008-1.png||_mstalt="428142" height="579" width="379"]]
	2	+[[image:image-20220613162008-1.png||_mstalt="428142" height="510" width="334"]]
3	3
4	4
5	5
...	...	@@ -46,6 +46,7 @@
46	46
47	47	== 1.2 Features ==
48	48
	49	+
49	49	* Wall mountable
50	50	* LoRaWAN v1.0.3 Class A protocol
51	51	* Frequency Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915
...	...	@@ -60,6 +60,7 @@
60	60
61	61
62	62
	64	+
63	63	== 1.3 Specification ==
64	64
65	65
...	...	@@ -86,10 +86,12 @@
86	86
87	87
88	88
	91	+
89	89	= 2. Connect LHT65N to IoT Server =
90	90
91	91	== 2.1 How does LHT65N work? ==
92	92
	96	+
93	93	(((
94	94	LHT65N is configured as LoRaWAN OTAA Class A mode by default. Each LHT65N is shipped with a worldwide unique set of OTAA keys. To use LHT65N in a LoRaWAN network, first, we need to put the OTAA keys in LoRaWAN Network Server and then activate LHT65N.
95	95	)))
...	...	@@ -99,8 +99,10 @@
99	99	)))
100	100
101	101
	106	+
102	102	== 2.2 How to Activate LHT65N? ==
103	103
	109	+
104	104	(((
105	105	The LHT65N has two working modes:
106	106	)))
...	...	@@ -125,6 +125,7 @@
125	125
126	126	== 2.3 Example to join LoRaWAN network ==
127	127
	134	+
128	128	(% _msthash="315240" _msttexthash="9205482" _mstvisible="1" class="wikigeneratedid" %)
129	129	This section shows an example of how to join the TTN V3 LoRaWAN IoT server. Use with other LoRaWAN IoT servers is of a similar procedure.
130	130
...	...	@@ -140,6 +140,7 @@
140	140
141	141	=== 2.3.1 Step 1: Create Device n TTN ===
142	142
	150	+
143	143	(((
144	144	Create a device in TTN V3 with the OTAA keys from LHT65N.
145	145	)))
...	...	@@ -164,9 +164,10 @@
164	164	[[image:image-20220522232954-5.png||_mstalt="431847" _mstvisible="3"]]
165	165
166	166
167		-Note: LHT65N use same payload as LHT65.
168	168
	176	+(% style="color:red" %)**Note: LHT65N use same payload as LHT65.**
169	169
	178	+
170	170	[[image:image-20220522233026-6.png||_mstalt="429403" _mstvisible="3"]]
171	171
172	172
...	...	@@ -180,6 +180,7 @@
180	180
181	181	=== 2.3.2 Step 2: Activate LHT65N by pressing the ACT button for more than 5 seconds. ===
182	182
	192	+
183	183	(((
184	184	Use ACT button to activate LHT65N and it will auto-join to the TTN V3 network. After join success, it will start to upload sensor data to TTN V3 and user can see in the panel.
185	185	)))
...	...	@@ -191,6 +191,7 @@
191	191
192	192	== 2.4 Uplink Payload ==
193	193
	204	+
194	194	(((
195	195	The uplink payload includes totally 11 bytes. Uplink packets use FPORT=2 and (% _mstvisible="3" style="color:#4f81bd" %)**every 20 minutes**(%%) send one uplink by default.
196	196	)))
...	...	@@ -265,10 +265,14 @@
265	265
266	266	* The First 6 bytes: has fix meanings for every LHT65N.
267	267	* The 7th byte (EXT #): defines the external sensor model.
268		-* The 8(% _msthash="734578" _msttexthash="21372" _mstvisible="4" %)^^th^^(%%) ~~ 11(% _msthash="734579" _msttexthash="21372" _mstvisible="4" %)^^th^^(%%) byte: the value for external sensor value. The definition is based on external sensor type. (If EXT=0, there won’t be these four bytes.)
	279	+* The 8(% _msthash="734578" _msttexthash="21372" _mstvisible="4" %)^^th^^(%%) ~~ 11(% _msthash="734579" _msttexthash="21372" _mstvisible="4" %)^^th^^(%%) byte: the value for external sensor value. The definition is based on external sensor type. (If EXT=0, there won't be these four bytes.)
269	269
	281	+
	282	+
	283	+
270	270	=== 2.4.1 Decoder in TTN V3 ===
271	271
	286	+
272	272	When the uplink payload arrives TTNv3, it shows HEX format and not friendly to read. We can add LHT65N decoder in TTNv3 for friendly reading.
273	273
274	274	Below is the position to put the decoder and LHT65N decoder can be download from here:
...	...	@@ -284,6 +284,7 @@
284	284
285	285	=== 2.4.2 BAT-Battery Info ===
286	286
	302	+
287	287	These two bytes of BAT include the battery state and the actually voltage
288	288
289	289	[[image:image-20220523152839-18.png||_mstalt="457613" _mstvisible="3"]]
...	...	@@ -297,8 +297,12 @@
297	297	* BAT status=(0Xcba4>>14)&0xFF=11(B)，very good
298	298	* Battery Voltage =0xCBF6&0x3FFF=0x0BA4=2980mV
299	299
	316	+
	317	+
	318	+
300	300	=== 2.4.3 Built-in Temperature ===
301	301
	321	+
302	302	[[image:image-20220522235639-2.png||_mstalt="431756" _mstvisible="3" height="138" width="722"]]
303	303
304	304	* Temperature:  0x0ABB/100=27.47℃
...	...	@@ -307,14 +307,22 @@
307	307
308	308	* Temperature:  (0xF5C6-65536)/100=-26.18℃
309	309
	330	+
	331	+
	332	+
310	310	=== 2.4.4 Built-in Humidity ===
311	311
	335	+
312	312	[[image:image-20220522235639-4.png||_mstalt="432484" _mstvisible="3" height="138" width="722"]]
313	313
314	314	* Humidity:    0x025C/10=60.4%
315	315
	340	+
	341	+
	342	+
316	316	=== 2.4.5 Ext # ===
317	317
	345	+
318	318	Bytes for External Sensor:
319	319
320	320	[[image:image-20220523152822-17.png||_mstalt="454545" _mstvisible="3"]]
...	...	@@ -323,6 +323,7 @@
323	323
324	324	=== 2.4.6 Ext value ===
325	325
	354	+
326	326	==== 2.4.6.1 Ext~=1, E3 Temperature Sensor ====
327	327
328	328
...	...	@@ -346,6 +346,7 @@
346	346
347	347	==== 2.4.6.2 Ext~=9, E3 sensor with Unix Timestamp ====
348	348
	378	+
349	349	(((
350	350	Timestamp mode is designed for LHT65N with E3 probe, it will send the uplink payload with Unix timestamp. With the limitation of 11 bytes (max distance of AU915/US915/AS923 band), the time stamp mode will be lack of BAT voltage field, instead, it shows the battery status. The payload is as below:
351	351	)))
...	...	@@ -459,14 +459,20 @@
459	459
460	460	* (% _msthash="504956" _msttexthash="245037" _mstvisible="4" %)**Status & Ext Byte**
461	461
462		-[[image:image-20220523152434-16.png||_mstalt="453921" _mstvisible="3"]]
	492	+(% border="1" cellspacing="8" style="background-color:#ffffcc; color:green; width:520px" %)
	493	+|(% style="width:60px" %)**Bits**|(% style="width:90px" %)**7**|(% style="width:100px" %)**6**|(% style="width:90px" %)**5**|(% style="width:100px" %)**4**|(% style="width:60px" %)**[3:0]**
	494	+|(% style="width:96px" %)**Status&Ext**|(% style="width:124px" %)None-ACK Flag|(% style="width:146px" %)Poll Message FLAG|(% style="width:109px" %)Sync time OK|(% style="width:143px" %)Unix Time Request|(% style="width:106px" %)Ext: 0b(1001)
463	463
464		-* Poll Message Flag:  1: This message is a poll message reply, 0: means this is a normal uplink.
465		-* Sync time OK:  1: Set time ok，0: N/A. After time SYNC request is sent, LHT65N will set this bit to 0 until got the time stamp from the application server.
466		-* Unix Time Request:  1: Request server downlink Unix time, 0 : N/A. In this mode, LHT65N will set this bit to 1 every 10 days to request a time SYNC. (AT+SYNCMOD to set this)
	496	+* (% style="color:blue" %)**Poll Message Flag**:(%%)  1: This message is a poll message reply, 0: means this is a normal uplink.
	497	+* (% style="color:blue" %)**Sync time OK**: (%%) 1: Set time ok，0: N/A. After time SYNC request is sent, LHT65N will set this bit to 0 until got the time stamp from the application server.
	498	+* (% style="color:blue" %)**Unix Time Request**:(%%)  1: Request server downlink Unix time, 0 : N/A. In this mode, LHT65N will set this bit to 1 every 10 days to request a time SYNC. (AT+SYNCMOD to set this)
467	467
	500	+
	501	+
	502	+
468	468	==== 2.4.6.3 Ext~=6, ADC Sensor (use with E2 Cable) ====
469	469
	505	+
470	470	In this mode, user can connect external ADC sensor to check ADC value. The 3V3_OUT can
471	471
472	472	be used to power the external ADC sensor; user can control the power on time for this
...	...	@@ -475,10 +475,46 @@
475	475
476	476	AT+EXT=6,timeout  (% _msthash="506085" _msttexthash="8782189" _mstvisible="3" style="color:red" %)Time to power this sensor, from 0 ~~ 65535ms
477	477
	514	+For example:
478	478
	516	+AT+EXT=6,1000 will power this sensor for 1000ms before sampling the ADC value.
479	479
	518	+
	519	+Or use **downlink command A2** to set the same.
	520	+
	521	+The measuring range of the node is only about 0.1V to 1.1V The voltage resolution is about 0.24mv.
	522	+
	523	+When the measured output voltage of the sensor is not within the range of 0.1V and 1.1V, the output voltage terminal of the sensor shall be divided The example in the following figure is to reduce the output voltage of the sensor by three times If it is necessary to reduce more times, calculate according to the formula in the figure and connect the corresponding resistance in series.
	524	+
	525	+[[image:image-20220628150112-1.png||height="241" width="285"]]
	526	+
	527	+
	528	+When ADC_IN1 pin is connected to GND or suspended, ADC value is 0
	529	+
	530	+[[image:image-20220628150714-4.png]]
	531	+
	532	+
	533	+When the voltage collected by ADC_IN1 is less than the minimum range, the minimum range will be used as the output; Similarly, when the collected voltage is greater than the maximum range, the maximum range will be used as the output.
	534	+
	535	+1) The minimum range is about 0.1V. Each chip has internal calibration, so this value is close to 0.1V
	536	+
	537	+[[image:image-20220628151005-5.png]]
	538	+
	539	+
	540	+2) The maximum range is about 1.1V. Each chip has internal calibration, so this value is close to 1.1v
	541	+
	542	+[[image:image-20220628151056-6.png]]
	543	+
	544	+
	545	+3) Within range
	546	+
	547	+[[image:image-20220628151143-7.png]]
	548	+
	549	+
	550	+
480	480	== 2.5 Show data on Datacake ==
481	481
	553	+
482	482	(((
483	483	Datacake IoT platform provides a human-friendly interface to show the sensor data, once we have sensor data in TTN V3, we can use Datacake to connect to TTN V3 and see the data in Datacake. Below are the steps:
484	484	)))
...	...	@@ -526,6 +526,7 @@
526	526
527	527	== 2.6 Datalog Feature ==
528	528
	601	+
529	529	(((
530	530	Datalog Feature is to ensure IoT Server can get all sampling data from Sensor even if the LoRaWAN network is down. For each sampling, LHT65N will store the reading for future retrieving purposes. There are two ways for IoT servers to get datalog from LHT65N.
531	531	)))
...	...	@@ -534,11 +534,17 @@
534	534
535	535	=== 2.6.1 Ways to get datalog via LoRaWAN ===
536	536
	610	+
537	537	There are two methods:
538	538
539		-1. IoT Server sends a downlink LoRaWAN command to [[poll the value>>||anchor="H2.6.4Pollsensorvalue"]] for specify time range.
540		-1. Set [[PNACKMD=1>>||anchor="H4.13AutoSendNone-ACKmessages"]], LHT65N will wait for ACK for every uplink, when there is no LoRaWAN network, LHT65N will store the sensor data, and it will send all messages after network recover.
	613	+1. IoT Server sends a downlink LoRaWAN command to [[poll the value>>||anchor="H2.6.4Pollsensorvalue"]] for specifying time range.
	614	+1. Set [[PNACKMD=1>>||anchor="H4.13AutoSendNone-ACKmessages"]], LHT65N will wait for ACK for every uplink, when there is no LoRaWAN network, LHT65N will store the sensor data, and it will send all messages after the network recovery.
541	541
	616	+Below is the typical case for the auto-update datalog feature (Set PNACKMD=1)
	617	+
	618	+[[image:image-20220703111700-2.png||height="381" width="1119"]]
	619	+
	620	+
542	542	=== 2.6.2 Unix TimeStamp ===
543	543
544	544
...	...	@@ -561,25 +561,44 @@
561	561
562	562	=== 2.6.3 Set Device Time ===
563	563
	643	+
	644	+(((
564	564	There are two ways to set device's time:
	646	+)))
565	565
	648	+(((
566	566	**~1. Through LoRaWAN MAC Command (Default settings)**
	650	+)))
567	567
	652	+(((
568	568	User need to set SYNCMOD=1 to enable sync time via MAC command.
	654	+)))
569	569
	656	+(((
570	570	Once LHT65N Joined LoRaWAN network, it will send the MAC command (DeviceTimeReq) and the server will reply with (DeviceTimeAns) to send the current time to LHT65N. If LHT65N fails to get the time from the server, LHT65N will use the internal time and wait for next time request (AT+SYNCTDC to set the time request period, default is 10 days).
	658	+)))
571	571
572		-(% style="color:red" %)Note: LoRaWAN Server need to support LoRaWAN v1.0.3(MAC v1.0.3) or higher to support this MAC command feature, Chirpstack,TTN V3 v3 and loriot support but TTN V3 v2 doesn’t support. If server doesn’t support this command, it will through away uplink packet with this command, so user will lose the packet with time request for TTN V3 v2 if SYNCMOD=1.
	660	+(((
	661	+(% style="color:red" %)**Note: LoRaWAN Server need to support LoRaWAN v1.0.3(MAC v1.0.3) or higher to support this MAC command feature, Chirpstack,TTN V3 v3 and loriot support but TTN V3 v2 doesn't support. If server doesn't support this command, it will through away uplink packet with this command, so user will lose the packet with time request for TTN V3 v2 if SYNCMOD=1.**
	662	+)))
573	573
	664	+(((
	665	+
	666	+)))
574	574
	668	+(((
575	575	**2. Manually Set Time**
	670	+)))
576	576
	672	+(((
577	577	User needs to set SYNCMOD=0 to manual time, otherwise, the user set time will be overwritten by the time set by the server.
	674	+)))
578	578
579	579
580	580
581	581	=== 2.6.4 Poll sensor value ===
582	582
	680	+
583	583	User can poll sensor value based on timestamps from the server. Below is the downlink command.
584	584
585	585	[[image:image-20220523152302-15.png||_mstalt="451581" _mstvisible="3"]]
...	...	@@ -597,6 +597,7 @@
597	597
598	598	=== 2.6.5 Datalog Uplink payload ===
599	599
	698	+
600	600	(% _msthash="315267" _msttexthash="2245087" _mstvisible="1" %)
601	601	The Datalog poll reply uplink will use below payload format.
602	602
...	...	@@ -603,6 +603,9 @@
603	603	(% _mstvisible="1" %)
604	604	(((
605	605	(% _mstvisible="2" %)
	705	+
	706	+
	707	+(% _mstvisible="2" %)
606	606	(% _msthash="506080" _msttexthash="451581" _mstvisible="4" %)**Retrieval data payload**
607	607	)))
608	608
...	...	@@ -741,9 +741,11 @@
741	741	(% _mstvisible="2" %)
742	742	(((
743	743	(% _msthash="736723" _msttexthash="2005003" _mstvisible="3" %)
	846	+(((
744	744	Poll Message Flag: 1: This message is a poll message reply.
745	745	)))
746	746	)))
	850	+)))
747	747
748	748	(% _mstvisible="1" %)
749	749	* (% _mstvisible="3" %)
...	...	@@ -751,17 +751,21 @@
751	751	(% _mstvisible="4" %)
752	752	(((
753	753	(% _msthash="1197157" _msttexthash="561548" _mstvisible="5" %)
	858	+(((
754	754	Poll Message Flag is set to 1.
755	755	)))
756	756	)))
	862	+)))
757	757	* (% _mstvisible="3" %)
758	758	(((
759	759	(% _mstvisible="4" %)
760	760	(((
761	761	(% _msthash="1197158" _msttexthash="9284964" _mstvisible="5" %)
	868	+(((
762	762	Each data entry is 11 bytes, to save airtime and battery, devices will send max bytes according to the current DR and Frequency bands.
763	763	)))
764	764	)))
	872	+)))
765	765
766	766	(% _mstvisible="1" %)
767	767	(((
...	...	@@ -768,12 +768,16 @@
768	768	(% _mstvisible="2" %)
769	769	(((
770	770	(% _msthash="736724" _msttexthash="2242344" _mstvisible="3" %)
	879	+(((
771	771
	881	+)))
772	772
773	773	(% _msthash="736724" _msttexthash="2242344" _mstvisible="3" %)
	884	+(((
774	774	For example, in US915 band, the max payload for different DR is:
775	775	)))
776	776	)))
	888	+)))
777	777
778	778	(% _mstvisible="1" %)
779	779	(((
...	...	@@ -780,9 +780,11 @@
780	780	(% _mstvisible="2" %)
781	781	(((
782	782	(% _msthash="736725" _msttexthash="1065532" _mstvisible="3" %)
	895	+(((
783	783	a) DR0: max is 11 bytes so one entry of data
784	784	)))
785	785	)))
	899	+)))
786	786
787	787	(% _mstvisible="1" %)
788	788	(((
...	...	@@ -789,9 +789,11 @@
789	789	(% _mstvisible="2" %)
790	790	(((
791	791	(% _msthash="736726" _msttexthash="3265665" _mstvisible="3" %)
	906	+(((
792	792	b) DR1: max is 53 bytes so devices will upload 4 entries of data (total 44 bytes)
793	793	)))
794	794	)))
	910	+)))
795	795
796	796	(% _mstvisible="1" %)
797	797	(((
...	...	@@ -798,9 +798,11 @@
798	798	(% _mstvisible="2" %)
799	799	(((
800	800	(% _msthash="736727" _msttexthash="1454115" _mstvisible="3" style="text-align: left;" %)
	917	+(((
801	801	c) DR2: total payload includes 11 entries of data
802	802	)))
803	803	)))
	921	+)))
804	804
805	805	(% _mstvisible="1" %)
806	806	(((
...	...	@@ -807,9 +807,11 @@
807	807	(% _mstvisible="2" %)
808	808	(((
809	809	(% _msthash="736728" _msttexthash="1483924" _mstvisible="3" style="text-align: left;" %)
	928	+(((
810	810	d) DR3: total payload includes 22 entries of data.
811	811	)))
812	812	)))
	932	+)))
813	813
814	814	(% _mstvisible="1" %)
815	815	(((
...	...	@@ -816,9 +816,11 @@
816	816	(% _mstvisible="2" %)
817	817	(((
818	818	(% _msthash="736729" _msttexthash="5848349" _mstvisible="3" style="text-align: left;" %)
	939	+(((
819	819	If devise doesn’t have any data in the polling time. Device will uplink 11 bytes of 0
820	820	)))
821	821	)))
	943	+)))
822	822
823	823
824	824	(% _mstvisible="1" style="text-align: left;" %)
...	...	@@ -845,7 +845,7 @@
845	845	(% _mstvisible="1" %)
846	846	(((
847	847	(% _msthash="506083" _msttexthash="737269" _mstvisible="2" style="text-align: left;" %)
848		- Stop time 60066DA7= time 21/1/19 05:27:(% _msthash="903005" _msttexthash="9672" _mstvisible="2" %)03
	970	+ Stop time 60066DA7= time 21/1/19 05:27:(% _msthash="903005" _msttexthash="9672" _mstvisible="2" %)03
849	849	)))
850	850
851	851	(% _mstvisible="1" %)
...	...	@@ -864,57 +864,106 @@
864	864	[[image:image-20220523001219-13.png||_mstalt="451204" _mstvisible="3" height="421" style="text-align:left" width="727"]]
865	865
866	866	(% _msthash="315271" _msttexthash="12012546" _mstvisible="1" style="text-align: left;" %)
	989	+(((
867	867	7FFF089801464160065F977FFF088E014B41600660097FFF0885014E41600660667FFF0875015141600662BE7FFF086B015541600665167FFF08660155416006676E7FFF085F015A41600669C67FFF0857015D4160066C1E
	991	+)))
868	868
869	869	(% _msthash="315237" _msttexthash="1385839" %)
	994	+(((
870	870	Where the first 11 bytes is for the first entry:
	996	+)))
871	871
872	872	(% _msthash="315238" _msttexthash="274846" %)
	999	+(((
873	873	7FFF089801464160065F97
	1001	+)))
874	874
875	875	(% _msthash="315239" _msttexthash="617435" %)
	1004	+(((
876	876	Ext sensor data=0x7FFF/100=327.67
	1006	+)))
877	877
878	878	(% _msthash="315240" _msttexthash="270543" %)
	1009	+(((
879	879	Temp=0x0898/100=22.00
	1011	+)))
880	880
881	881	(% _msthash="315241" _msttexthash="211783" %)
	1014	+(((
882	882	Hum=0x0146/10=32.6
	1016	+)))
883	883
884	884	(% _msthash="315242" _msttexthash="1569776" %)
	1019	+(((
885	885	poll message flag & Ext=0x41,means reply data,Ext=1
	1021	+)))
886	886
887	887	(% _msthash="315243" _msttexthash="1120509" %)
	1024	+(((
888	888	Unix time is 0x60065F97=1611030423s=21/1/19 04:27:03
	1026	+)))
889	889
890	890
891	891
892	892	== 2.7 Alarm Mode ==
893	893
	1032	+
	1033	+(((
894	894	when the device is in alarm mode, it checks the built-in sensor temperature for a short time. if the temperature exceeds the preconfigured range, it sends an uplink immediately.
	1035	+)))
895	895
896		-(% style="color:red" %)Note: alarm mode adds a little power consumption, and we recommend extending the normal read time when this feature is enabled.
	1037	+(((
	1038	+(% style="color:red" %)**Note: alarm mode adds a little power consumption, and we recommend extending the normal read time when this feature is enabled.**
897	897
	1040	+
	1041	+)))
	1042	+
	1043	+(((
898	898	**AT COMMAND FOR ALARM MODE:**
	1045	+)))
899	899
900	900	(% _mstvisible="1" class="box infomessage" %)
901	901	(((
	1049	+(((
902	902	**AT+WMOD=1**:  Enable/disable alarm mode. (0: Disabled, 1: Enabled)
	1051	+)))
903	903
	1053	+(((
904	904	**AT+CITEMP=1**:  The interval between checking the alarm temperature. (In minutes)
	1055	+)))
905	905
	1057	+(((
906	906	**AT+ARTEMP**:  Gets or sets the alarm range of the internal temperature sensor
	1059	+)))
907	907
	1061	+(((
908	908	**AT+ARTEMP=？ **:  Gets the alarm range of the internal temperature sensor(% _mstvisible="3" style="display:none" %)
	1063	+)))
909	909
	1065	+(((
910	910	**AT+ARTEMP=45,105**:  Set the internal temperature sensor alarm range from 45 to 105.
911	911	)))
	1068	+)))
912	912
	1070	+(% style="color:#4f81bd" %)**Downlink Command: AAXXXXXXXXXXXXXX**
913	913
	1072	+Total bytes: 8 bytes
914	914
	1074	+**Example:**AA0100010001003C
915	915
	1076	+WMOD=01
	1077	+
	1078	+CITEMP=0001
	1079	+
	1080	+TEMPlow=0001
	1081	+
	1082	+TEMPhigh=003C
	1083	+
	1084	+
	1085	+
916	916	== 2.8 LED Indicator ==
917	917
	1088	+
918	918	The LHT65 has a triple color LED which for easy showing different stage .
919	919
920	920	While user press ACT button, the LED will work as per LED status with ACT button.
...	...	@@ -922,12 +922,16 @@
922	922	In a normal working state:
923	923
924	924	* For each uplink, the BLUE LED or RED LED will blink once.
925		- BLUE LED when external sensor is connected.
	1096	+BLUE LED when external sensor is connected.
926	926	* RED LED when external sensor is not connected
927	927	* For each success downlink, the PURPLE LED will blink once
928	928
	1100	+
	1101	+
	1102	+
929	929	== 2.9 installation ==
930	930
	1105	+
931	931	(% _mstvisible="1" %)
932	932	[[image:image-20220516231650-1.png||_mstalt="428597" _mstvisible="3" height="436" width="428"]]
933	933
...	...	@@ -937,10 +937,31 @@
937	937
938	938	== 3.1 E2 Extension Cable ==
939	939
	1115	+
940	940	[[image:image-20220619092222-1.png||height="182" width="188"]][[image:image-20220619092313-2.png||height="182" width="173"]]
941	941
942		-1m long breakout cable for LHT65N
943	943
	1119	+**1m long breakout cable for LHT65N. Features:**
	1120	+
	1121	+* (((
	1122	+Use for AT Command， works for both LHT52/LHT65N
	1123	+)))
	1124	+* (((
	1125	+Update firmware for LHT65N, works for both LHT52/LHT65N
	1126	+)))
	1127	+* (((
	1128	+Supports ADC mode to monitor external ADC
	1129	+)))
	1130	+* (((
	1131	+Supports Interrupt mode
	1132	+)))
	1133	+* (((
	1134	+Exposed All pins from the LHT65N Type-C connector.
	1135	+
	1136	+
	1137	+
	1138	+)))
	1139	+
944	944	[[image:image-20220619092421-3.png||height="371" width="529"]]
945	945
946	946
...	...	@@ -960,34 +960,63 @@
960	960	* Operating Range: -40 ~~ 125 °C
961	961	* Working voltage 2.35v ~~ 5v
962	962
	1159	+
	1160	+
	1161	+
963	963	= 4. Configure LHT65N via AT command or LoRaWAN downlink =
964	964
	1164	+
	1165	+(((
965	965	Use can configure LHT65N via AT Command or LoRaWAN Downlink.
	1167	+)))
966	966
967		-* AT Command Connection: See [[FAQ>>||anchor="H6.FAQ"]].
	1169	+* (((
	1170	+AT Command Connection: See [[FAQ>>||anchor="H6.FAQ"]].
	1171	+)))
968	968
969		-* LoRaWAN Downlink instruction for different platforms: [[IoT LoRaWAN Server>>doc:Main.WebHome]]
	1173	+* (((
	1174	+LoRaWAN Downlink instruction for different platforms: [[IoT LoRaWAN Server>>doc:Main.WebHome]]
	1175	+)))
970	970
	1177	+(((
971	971	There are two kinds of commands to configure LHT65N, they are:
	1179	+)))
972	972
973		-* (% style="color:#4f81bd" %)**General Commands**.
	1181	+* (((
	1182	+(% style="color:#4f81bd" %)**General Commands**.
	1183	+)))
974	974
	1185	+(((
975	975	These commands are to configure:
	1187	+)))
976	976
977		-1. General system settings like: uplink interval.
978		-1. LoRaWAN protocol & radio-related commands.
	1189	+1. (((
	1190	+General system settings like: uplink interval.
	1191	+)))
	1192	+1. (((
	1193	+LoRaWAN protocol & radio-related commands.
	1194	+)))
979	979
	1196	+(((
980	980	They are the same for all Dragino Devices which supports DLWS-005 LoRaWAN Stack(Note~*~*). These commands can be found on the wiki: [[End Device Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]]
	1198	+)))
981	981
982		-* (% style="color:#4f81bd" %)**Commands special design for LHT65N**
	1200	+* (((
	1201	+(% style="color:#4f81bd" %)**Commands special design for LHT65N**
	1202	+)))
983	983
	1204	+(((
984	984	These commands are only valid for LHT65N, as below:
	1206	+)))
985	985
986	986
	1209	+
987	987	== 4.1 Set Transmit Interval Time ==
988	988
	1212	+
989	989	Feature: Change LoRaWAN End Node Transmit Interval.
990	990
	1215	+
991	991	(% style="color:#4f81bd" %)**AT Command: AT+TDC**
992	992
993	993	[[image:image-20220523150701-2.png||_mstalt="427453" _mstvisible="3"]]
...	...	@@ -1003,10 +1003,15 @@
1003	1003
1004	1004	* **Example 2**: Downlink Payload: 0100003C ~/~/ Set Transmit Interval (TDC) = 60 seconds
1005	1005
	1231	+
	1232	+
	1233	+
1006	1006	== 4.2 Set External Sensor Mode ==
1007	1007
	1236	+
1008	1008	Feature: Change External Sensor Mode.
1009	1009
	1239	+
1010	1010	(% style="color:#4f81bd" %)**AT Command: AT+EXT**
1011	1011
1012	1012	[[image:image-20220523150759-3.png||_mstalt="432146" _mstvisible="3"]]
...	...	@@ -1024,8 +1024,12 @@
1024	1024
1025	1025	* 0xA20702003c: Same as AT+SETCNT=60
1026	1026
	1257	+
	1258	+
	1259	+
1027	1027	== 4.3 Enable/Disable uplink Temperature probe ID ==
1028	1028
	1262	+
1029	1029	(((
1030	1030	Feature: If PID is enabled, device will send the temperature probe ID on:
1031	1031	)))
...	...	@@ -1039,6 +1039,8 @@
1039	1039
1040	1040	(((
1041	1041	PID is default set to disable (0)
	1276	+
	1277	+
1042	1042	)))
1043	1043
1044	1044	(% style="color:#4f81bd" %)**AT Command:**
...	...	@@ -1051,10 +1051,15 @@
1051	1051	* **0xA800**  **~-~->** AT+PID=0
1052	1052	* **0xA801**     **~-~->** AT+PID=1
1053	1053
	1290	+
	1291	+
	1292	+
1054	1054	== 4.4 Set Password ==
1055	1055
	1295	+
1056	1056	Feature: Set device password, max 9 digits
1057	1057
	1298	+
1058	1058	(% style="color:#4f81bd" %)**AT Command: AT+PWORD**
1059	1059
1060	1060	[[image:image-20220523151052-5.png||_mstalt="428623" _mstvisible="3"]]
...	...	@@ -1068,8 +1068,10 @@
1068	1068
1069	1069	== 4.5 Quit AT Command ==
1070	1070
	1312	+
1071	1071	Feature: Quit AT Command mode, so user needs to input password again before use AT Commands.
1072	1072
	1315	+
1073	1073	(% style="color:#4f81bd" %)**AT Command: AT+DISAT**
1074	1074
1075	1075	[[image:image-20220523151132-6.png||_mstalt="428649" _mstvisible="3"]]
...	...	@@ -1083,6 +1083,7 @@
1083	1083
1084	1084	== 4.6 Set to sleep mode ==
1085	1085
	1329	+
1086	1086	Feature: Set device to sleep mode
1087	1087
1088	1088	* **AT+Sleep=0**  : Normal working mode, device will sleep and use lower power when there is no LoRa message
...	...	@@ -1097,10 +1097,15 @@
1097	1097
1098	1098	* There is no downlink command to set to Sleep mode.
1099	1099
	1344	+
	1345	+
	1346	+
1100	1100	== 4.7 Set system time ==
1101	1101
	1349	+
1102	1102	Feature: Set system time, unix format. [[See here for format detail.>>||anchor="H2.6.2UnixTimeStamp"]]
1103	1103
	1352	+
1104	1104	(% _msthash="315253" _msttexthash="137488" style="color:#4f81bd" %)**AT Command:**
1105	1105
1106	1106	[[image:image-20220523151253-8.png||_mstalt="430677" _mstvisible="3"]]
...	...	@@ -1114,6 +1114,7 @@
1114	1114
1115	1115	== 4.8 Set Time Sync Mode ==
1116	1116
	1366	+
1117	1117	(((
1118	1118	Feature: Enable/Disable Sync system time via LoRaWAN MAC Command (DeviceTimeReq), LoRaWAN server must support v1.0.3 protocol to reply this command.
1119	1119	)))
...	...	@@ -1120,6 +1120,8 @@
1120	1120
1121	1121	(((
1122	1122	SYNCMOD is set to 1 by default. If user want to set a different time from LoRaWAN server, user need to set this to 0.
	1373	+
	1374	+
1123	1123	)))
1124	1124
1125	1125	(% _msthash="506058" _msttexthash="137488" style="color:#4f81bd" %)**AT Command:**
...	...	@@ -1136,8 +1136,10 @@
1136	1136
1137	1137	== 4.9 Set Time Sync Interval ==
1138	1138
	1391	+
1139	1139	Feature: Define System time sync interval. SYNCTDC default value: 10 days.
1140	1140
	1394	+
1141	1141	(% _msthash="315256" _msttexthash="137488" style="color:#4f81bd" %)**AT Command:**
1142	1142
1143	1143	[[image:image-20220523151411-10.png||_mstalt="449696" _mstvisible="3"]]
...	...	@@ -1151,8 +1151,10 @@
1151	1151
1152	1152	== 4.10 Print data entries base on page. ==
1153	1153
	1408	+
1154	1154	Feature: Print the sector data from start page to stop page (max is 416 pages).
1155	1155
	1411	+
1156	1156	(% _msthash="315258" _msttexthash="264953" style="color:#4f81bd" %)**AT Command: AT+PDTA**
1157	1157
1158	1158	[[image:image-20220523151450-11.png||_mstalt="451035" _mstvisible="3"]]
...	...	@@ -1166,8 +1166,10 @@
1166	1166
1167	1167	== 4.11 Print last few data entries. ==
1168	1168
	1425	+
1169	1169	Feature: Print the last few data entries
1170	1170
	1428	+
1171	1171	(% _msthash="315260" _msttexthash="288522" style="color:#4f81bd" %)**AT Command: AT+PLDTA**
1172	1172
1173	1173	[[image:image-20220523151524-12.png||_mstalt="452101" _mstvisible="3"]]
...	...	@@ -1181,6 +1181,7 @@
1181	1181
1182	1182	== 4.12 Clear Flash Record ==
1183	1183
	1442	+
1184	1184	Feature: Clear flash storage for data log feature.
1185	1185
1186	1186
...	...	@@ -1193,11 +1193,16 @@
1193	1193
1194	1194	* Example: 0xA301 ~/~/Same as AT+CLRDTA
1195	1195
	1455	+
	1456	+
	1457	+
1196	1196	== 4.13 Auto Send None-ACK messages ==
1197	1197
	1460	+
1198	1198	(% _msthash="315394" _msttexthash="51837149" _mstvisible="1" %)
1199	1199	Feature: LHT65N will wait for ACK for each uplink, If LHT65N doesn't get ACK from the IoT server, it will consider the message doesn't arrive server and store it. LHT65N keeps sending messages in normal periodically. Once LHT65N gets ACK from a server, it will consider the network is ok and start to send the not-arrive message.
1200	1200
	1464	+
1201	1201	(% style="color:#4f81bd" %)**AT Command: AT+PNACKMD**
1202	1202
1203	1203	(% _msthash="315396" _msttexthash="734682" _mstvisible="1" %)
...	...	@@ -1211,10 +1211,14 @@
1211	1211
1212	1212	* Example: 0x3401 ~/~/Same as AT+PNACKMD=1
1213	1213
	1478	+
	1479	+
	1480	+
1214	1214	= 5. Battery & How to replace =
1215	1215
1216	1216	== 5.1 Battery Type ==
1217	1217
	1485	+
1218	1218	(((
1219	1219	(((
1220	1220	LHT65N is equipped with a 2400mAH Li-MnO2 (CR17505) battery . The battery is an un-rechargeable battery with low discharge rate targeting for up to 8~~10 years use. This type of battery is commonly used in IoT devices for long-term running, such as water meters.
...	...	@@ -1235,8 +1235,10 @@
1235	1235	The minimum Working Voltage for the LHT65N is ~~ 2.5v. When battery is lower than 2.6v, it is time to change the battery.
1236	1236
1237	1237
	1506	+
1238	1238	== 5.2 Replace Battery ==
1239	1239
	1509	+
1240	1240	LHT65N has two screws on the back, Unscrew them, and changing the battery inside is ok. The battery is a general CR17450 battery. Any brand should be ok.
1241	1241
1242	1242	[[image:image-20220515075440-2.png||_mstalt="429546" _mstvisible="3" height="338" width="272"]][[image:image-20220515075625-3.png||_mstalt="431574" _mstvisible="3" height="193" width="257"]]
...	...	@@ -1244,6 +1244,7 @@
1244	1244
1245	1245	== 5.3 Battery Life Analyze ==
1246	1246
	1517	+
1247	1247	(((
1248	1248	Dragino battery-powered products are all run in Low Power mode. User can check the guideline from this link to calculate the estimated battery life:
1249	1249	[[https:~~/~~/www.dragino.com/downloads/downloads/LoRa_End_Node/Battery_Analyze/DRAGINO_Battery_Life_Guide.pdf>>https://www.dragino.com/downloads/downloads/LoRa_End_Node/Battery_Analyze/DRAGINO_Battery_Life_Guide.pdf]]
...	...	@@ -1261,8 +1261,10 @@
1261	1261
1262	1262	= 6. FAQ =
1263	1263
	1535	+
1264	1264	== 6.1 How to use AT Command? ==
1265	1265
	1538	+
1266	1266	LHT65N supports AT Command set.User can use a USB to TTL adapter plus the Program Cable to connect to LHT65 for using AT command, as below.
1267	1267
1268	1268	[[image:image-20220530085651-1.png||_mstalt="429949"]]
...	...	@@ -1270,16 +1270,11 @@
1270	1270
1271	1271	(% _msthash="506061" _msttexthash="170755" %)**Connection:**
1272	1272
1273		-(% _msthash="506062" _msttexthash="1187732" %)
1274		-**✓ (% style="background-color:yellow" %)USB to TTL GND <~-~->GND(%%)**
	1546	+* (% style="background-color:yellow" %)**USB to TTL GND <~-~->GND**
	1547	+* (% style="background-color:yellow" %)**USB to TTL RXD <~-~-> D+**
	1548	+* (% style="background-color:yellow" %)**USB to TTL TXD <~-~-> A11**
	1549	+* (% style="background-color:yellow" %)**USB to TTL 3.3V <~-~-> D-**
1275	1275
1276		-(% _msthash="506063" _msttexthash="1158313" %)**✓  **(% style="background-color:yellow" %)**USB to TTL RXD <~-~-> D+**
1277		-
1278		-(% _msthash="506064" _msttexthash="1175629" %)**✓  **(% style="background-color:yellow" %)**USB to TTL TXD <~-~-> A11**
1279		-
1280		-(% _msthash="506065" _msttexthash="1164696" %)**✓  **(% style="background-color:yellow" %)**USB to TTL 3.3V <~-~-> D-**
1281		-
1282		-
1283	1283	(((
1284	1284	In PC, User needs to set serial tool(such as [[**putty**>>https://www.chiark.greenend.org.uk/~~sgtatham/putty/latest.html]], SecureCRT) baud rate to (% style="color:green" %)**9600**(%%) to access to access serial console for LHT65N. The AT commands are disable by default and need to enter password (default:(% style="color:green" %)**123456**) (%%)to active it. Timeout to input AT Command is 5 min, after 5-minute, user need to input password again. User can use AT+DISAT command to disable AT command before timeout.
1285	1285	)))
...	...	@@ -1486,40 +1486,43 @@
1486	1486	AT+PID:  Get or set the PID
1487	1487
1488	1488
	1757	+
1489	1489	== 6.2 Where to use AT commands and Downlink commands ==
1490	1490
1491		-(% _msthash="506131" _msttexthash="14585714" %)
1492		-AT commands：
1493	1493
	1761	+**AT commands：**
	1762	+
1494	1494	[[image:image-20220620153708-1.png||height="603" width="723"]]
1495	1495
1496		-(% _msthash="506132" _msttexthash="337922" %)
1497		-Downlink commands:
1498	1498
	1766	+**Downlink commands:**
1499	1499
1500		-(% _msthash="506133" _msttexthash="33046" %)
1501		-**TTN:**
1502	1502
	1769	+
	1770	+(% style="color:blue" %)**TTN:**
	1771	+
1503	1503	[[image:image-20220615092124-2.png||_mstalt="429221" height="649" width="688"]]
1504	1504
1505	1505
1506		-(% _msthash="506134" _msttexthash="11113791" %)
1507		-**Helium：**
1508	1508
	1776	+(% style="color:blue" %)**Helium：**
	1777	+
1509	1509	[[image:image-20220615092551-3.png||_mstalt="430794" height="423" width="835"]]
1510	1510
1511	1511
1512		-(% _msthash="506135" _msttexthash="4159844" %)
1513		-**Chirpstack:The downlink window will not be displayed until the network is accessed**
1514	1514
	1782	+(% style="color:blue" %)**Chirpstack: The downlink window will not be displayed until the network is accessed**
	1783	+
	1784	+
1515	1515	[[image:image-20220615094850-6.png||_mstalt="433082"]]
1516	1516
	1787	+
1517	1517	[[image:image-20220615094904-7.png||_mstalt="433485" height="281" width="911"]]
1518	1518
1519	1519
1520		-(% _msthash="506136" _msttexthash="39286" %)
1521		-**Aws:**
1522	1522
	1792	+(% style="color:blue" %)**Aws:**
	1793	+
1523	1523	[[image:image-20220615092939-4.png||_mstalt="434460" height="448" width="894"]]
1524	1524
1525	1525
...	...	@@ -1526,6 +1526,7 @@
1526	1526
1527	1527	== 6.3 How to change the uplink interval？ ==
1528	1528
	1800	+
1529	1529	[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/How%20to%20set%20the%20transmit%20time%20interval/>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20set%20the%20transmit%20time%20interval/||_msthash="506137" _msttexthash="5712018"]]
1530	1530
1531	1531
...	...	@@ -1532,6 +1532,7 @@
1532	1532
1533	1533	== 6.4 How to use TTL-USB to connect a PC to input AT commands? ==
1534	1534
	1807	+
1535	1535	[[image:image-20220615153355-1.png]]
1536	1536
1537	1537	[[image:1655802313617-381.png]]
...	...	@@ -1589,6 +1589,66 @@
1589	1589
1590	1590
1591	1591
	1865	+== 6.6 Using USB-TYPE-C to connect to the computer using the AT command ==
	1866	+
	1867	+
	1868	+[[image:image-20220623110706-1.png]]
	1869	+
	1870	+
	1871	+[[image:image-20220623112117-4.png||height="459" width="343"]]
	1872	+
	1873	+
	1874	+(((
	1875	+In PC, User needs to set serial tool(such as [[**putty**>>https://www.chiark.greenend.org.uk/~~sgtatham/putty/latest.html]], SecureCRT) baud rate to (% style="color:green" %)**9600** (%%)to access to access serial console for LHT65N. The AT commands are disable by default and need to enter password (default:(% style="color:green" %)**123456**(% style="color:red" %))(%%) to active it. Timeout to input AT Command is 5 min, after 5-minute, user need to input password again. User can use AT+DISAT command to disable AT command before timeout.
	1876	+)))
	1877	+
	1878	+
	1879	+Input password and ATZ to activate LHT65N,As shown below:
	1880	+
	1881	+[[image:image-20220615154519-3.png||height="672" width="807"]]
	1882	+
	1883	+
	1884	+
	1885	+== 6.7 How to use  USB-TYPE-C to connect PC to upgrade firmware? ==
	1886	+
	1887	+
	1888	+[[image:image-20220623110706-1.png]]
	1889	+
	1890	+
	1891	+(% style="color:blue" %)**Step1**(%%): Install TremoProgrammer  first.
	1892	+
	1893	+[[image:image-20220615170542-5.png]]
	1894	+
	1895	+
	1896	+(% style="color:blue" %)**Step2**(%%)：wiring method.(% style="display:none" %)
	1897	+
	1898	+(% _msthash="506146" _msttexthash="52173160" %)
	1899	+First connect the four lines；
	1900	+
	1901	+(% _msthash="506146" _msttexthash="52173160" %)
	1902	+[[image:image-20220623113959-5.png||height="528" width="397"]]
	1903	+
	1904	+(% _msthash="506146" _msttexthash="52173160" %)
	1905	+Press and hold the start key to restart and enter  (% _mstvisible="1" %)bootlaod(%%) mode.
	1906	+
	1907	+
	1908	+(% style="color:blue" %)**Step3：**(%%)Select the device port to be connected, baud rate and bin file to be downloaded.
	1909	+
	1910	+[[image:image-20220615171334-6.png]]
	1911	+
	1912	+
	1913	+Click the (% style="color:blue" %)**start**(%%) button to start the firmware upgrade.
	1914	+
	1915	+
	1916	+When this interface appears, it indicates that the download has been completed.
	1917	+
	1918	+[[image:image-20220620160723-8.png]]
	1919	+
	1920	+
	1921	+Finally,restart reset device again
	1922	+
	1923	+
	1924	+
1592	1592	= 7. Order Info =
1593	1593
1594	1594
...	...	@@ -1616,6 +1616,8 @@
1616	1616
1617	1617	* (% style="color:red" %)**E3**(%%): External Temperature Probe
1618	1618
	1952	+
	1953	+
1619	1619	= 8. Packing Info =
1620	1620
1621	1621
...	...	@@ -1629,12 +1629,18 @@
1629	1629	* Device Size:  10 x 10 x 3.5 cm
1630	1630	* Device Weight: 120.5g
1631	1631
	1967	+
	1968	+
1632	1632	= 9. Reference material =
1633	1633
	1971	+
1634	1634	* [[Datasheet, photos, decoder, firmware>>https://www.dropbox.com/sh/una19zsni308dme/AACOKp6J2RF5TMlKWT5zU3RTa?dl=0||_msthash="504975" _msttexthash="51420512"]]
1635	1635
	1974	+
	1975	+
1636	1636	= 10. FCC Warning =
1637	1637
	1978	+
1638	1638	This device complies with part 15 of the FCC Rules.Operation is subject to the following two conditions:
1639	1639
1640	1640	(1) This device may not cause harmful interference；

image-20220623110706-1.png

Author

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

Size

...	...	@@ -1,0 +1,1 @@
	1	+689.7 KB

Content

image-20220623110723-2.png

Author

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

Size

...	...	@@ -1,0 +1,1 @@
	1	+501.5 KB

Content

image-20220623111949-3.png

Author

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

Size

...	...	@@ -1,0 +1,1 @@
	1	+1.6 MB

Content

image-20220623112117-4.png

Author

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

Size

...	...	@@ -1,0 +1,1 @@
	1	+513.9 KB

Content

image-20220623113959-5.png

Author

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

Size

...	...	@@ -1,0 +1,1 @@
	1	+834.2 KB

Content

image-20220628150112-1.png

Author

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

Size

...	...	@@ -1,0 +1,1 @@
	1	+220.3 KB

Content

image-20220628150542-2.png

Author

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

Size

...	...	@@ -1,0 +1,1 @@
	1	+45.6 KB

Content

image-20220628150648-3.png

Author

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

Size

...	...	@@ -1,0 +1,1 @@
	1	+8.3 KB

Content

image-20220628150714-4.png

Author

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

Size

...	...	@@ -1,0 +1,1 @@
	1	+7.1 KB

Content

image-20220628151005-5.png

Author

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

Size

...	...	@@ -1,0 +1,1 @@
	1	+7.3 KB

Content

image-20220628151056-6.png

Author

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

Size

...	...	@@ -1,0 +1,1 @@
	1	+8.2 KB

Content

image-20220628151143-7.png

Author

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

Size

...	...	@@ -1,0 +1,1 @@
	1	+7.2 KB

Content

image-20220703111533-1.png

Author

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

Size

...	...	@@ -1,0 +1,1 @@
	1	+694.5 KB

Content

image-20220703111700-2.png

Author

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

Size

...	...	@@ -1,0 +1,1 @@
	1	+369.4 KB

Content