Last modified by Mengting Qiu on 2024/04/30 14:27
<
From version < 22.1 >
edited by Edwin Chen
on 2022/05/16 23:17
To version < 51.1 >
edited by Edwin Chen
on 2022/05/23 00:18
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -82,6 +82,426 @@
82 82  |**Pressing ACT for more than 3s**|Active Device|green led will fast blink 5 times, LHT65N will enter working mode and start to JOIN LoRaWAN network. green led will solid turn on for 5 seconds after join in network.
83 83  |**Fast press ACT 5 times**|Deactivate Device|red led will solid on for 5 seconds. This means LHT65N is in Deep Sleep Mode.
84 84  
85 +== Example to join LoRaWAN network ==
86 +
87 +(% class="wikigeneratedid" %)
88 +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.
89 +
90 +(% class="wikigeneratedid" %)
91 +[[image:image-20220522232442-1.png||height="387" width="648"]]
92 +
93 +Assume the LPS8N is already set to connect to [[TTN V3 network>>url:https://eu1.cloud.thethings.network]], So it provides network coverage for LHT65N. Next we need to add the LHT65N device in TTN V3:
94 +
95 +
96 +=== **Step 1**: Create Device n TTN ===
97 +
98 +Create a device in TTN V3 with the OTAA keys from LHT65N.
99 +
100 +Each LHT65N is shipped with a sticker with its device EUI, APP Key and APP EUI as below:
101 +
102 +[[image:image-20220522232812-2.png||height="219" width="279"]]
103 +
104 +User can enter these keys in the LoRaWAN Server portal. Below is TTN V3 screenshot:
105 +
106 +Add APP EUI in the application.
107 +
108 +[[image:image-20220522232916-3.png]]
109 +
110 +
111 +[[image:image-20220522232932-4.png]]
112 +
113 +
114 +[[image:image-20220522232954-5.png]]
115 +
116 +Note: LHT65N use same payload as LHT65.
117 +
118 +[[image:image-20220522233026-6.png]]
119 +
120 +
121 +Input APP EUI,  APP KEY and DEV EUI:
122 +
123 +[[image:image-20220522233118-7.png]]
124 +
125 +
126 +=== Step 2: Activate LHT65N by pressing the ACT button for more than 5 seconds. ===
127 +
128 +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.
129 +
130 +[[image:image-20220522233300-8.png]]
131 +
132 +
133 +== Uplink Payload: ==
134 +
135 +The uplink payload includes totally 11 bytes. Uplink packets use FPORT=2 and(% class="mark" %) every 20 minutes(%%) send one uplink by default.
136 +
137 +After each uplink, the (% class="mark" %)BLUE LED(%%) will blink once.
138 +
139 +
140 +(% style="width:572px" %)
141 +|(% style="width:106px" %)**Size(bytes)**|(% style="width:71px" %)**2**|(% style="width:128px" %)**2**|(% style="width:103px" %)**2**|(% style="width:72px" %)**1**|(% style="width:89px" %)**4**
142 +|(% style="width:106px" %)**Value**|(% style="width:71px" %)[[BAT>>path:#Battery]]|(% style="width:128px" %)(((
143 +[[Built-In>>path:#SHT20_Temperature]]
144 +
145 +[[Temperature>>path:#SHT20_Temperature]]
146 +)))|(% style="width:103px" %)(((
147 +[[Built-in>>path:#SHT20_Humidity]]
148 +
149 +[[Humidity>>path:#SHT20_Humidity]]
150 +)))|(% style="width:72px" %)[[Ext>>path:#Extension_Sensor]] #|(% style="width:89px" %)[[Ext value>>path:#Extension_sensor_value]]
151 +
152 +* The First 6 bytes: has fix meanings for every LHT65N.
153 +* The 7th byte (EXT #): defines the external sensor model.
154 +* The 8^^th^^ ~~ 11^^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.)
155 +
156 +=== Decoder in TTN V3 ===
157 +
158 +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.
159 +
160 +Below is the position to put the decoder and LHT65N decoder can be download from here:
161 +
162 +[[https:~~/~~/www.dropbox.com/sh/r2i3zlhsyrpavla/AAB1sZw3mdT0K7XjpHCITt13a?dl=0 >>https://www.dropbox.com/sh/r2i3zlhsyrpavla/AAB1sZw3mdT0K7XjpHCITt13a?dl=0]]
163 +
164 +[[image:image-20220522234118-10.png]]
165 +
166 +
167 +=== BAT-Battery Info ===
168 +
169 +These two bytes of BAT include the battery state and the actually voltage
170 +
171 +(% style="width:646px" %)
172 +|Bit(bit)|(% style="width:272px" %)[15:14]|(% style="width:214px" %)[13:0]
173 +|Value|(% style="width:272px" %)(((
174 +BAT Status
175 +
176 +00(b): Ultra Low ( BAT <= 2.50v)
177 +
178 +01(b): Low  (2.50v <=BAT <= 2.55v)
179 +
180 +10(b): OK   (2.55v <= BAT <=2.65v)
181 +
182 +11(b): Good   (BAT >= 2.65v)
183 +)))|(% style="width:214px" %)Actually BAT voltage
184 +
185 +[[image:image-20220522235639-1.png]]
186 +
187 +Check the battery voltage for LHT65N.
188 +
189 +* BAT status=(0Xcba4>>14)&0xFF=11(B)，very good
190 +* Battery Voltage =0xCBF6&0x3FFF=0x0BA4=2980mV
191 +
192 +=== Built-in Temperature ===
193 +
194 +[[image:image-20220522235639-2.png]]
195 +
196 +* Temperature:  0x0ABB/100=27.47℃
197 +
198 +[[image:image-20220522235639-3.png]]
199 +
200 +* Temperature:  (0xF5C6-65536)/100=-26.18℃
201 +
202 +=== Built-in Humidity ===
203 +
204 +[[image:image-20220522235639-4.png]]
205 +
206 +* Humidity:    0x025C/10=60.4%
207 +
208 +=== Ext # ===
209 +
210 +Bytes for External Sensor:
211 +
212 +(% style="width:624px" %)
213 +|(% style="width:139px" %)**EXT # Value**|(% style="width:484px" %)**External Sensor Type**
214 +|(% style="width:139px" %)0x01|(% style="width:484px" %)Sensor E3, Temperature Sensor
215 +|(% style="width:139px" %)0x09|(% style="width:484px" %)Sensor E3, Temperature Sensor, Datalog Mod
216 +
217 +=== Ext value ===
218 +
219 +==== Ext~=1, E3 Temperature Sensor ====
220 +
221 +[[image:image-20220522235639-5.png]]
222 +
223 +
224 +* DS18B20 temp=0x0ADD/100=27.81℃
225 +
226 +The last 2 bytes of data are meaningless
227 +
228 +
229 +
230 +[[image:image-20220522235639-6.png]]
231 +
232 +* External temperature= (0xF54F-65536)/100=-27.37℃
233 +
234 +The last 2 bytes of data are meaningless
235 +
236 +
237 +If the external sensor is 0x01, and there is no external temperature connected. The temperature will be set to 7FFF which is 327.67℃
238 +
239 +
240 +==== Ext~=9, E3 sensor with Unix Timestamp ====
241 +
242 +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:
243 +
244 +
245 +(% style="width:697px" %)
246 +|(% style="width:96px" %)**Size(bytes)**|(% style="width:164px" %)**2**|(% style="width:104px" %)**2**|(% style="width:106px" %)**2**|(% style="width:108px" %)**1**|(% style="width:116px" %)**4**
247 +|(% style="width:96px" %)**Value**|(% style="width:164px" %)[[External temperature>>path:#DS18b20_value]]|(% style="width:104px" %)(((
248 +[[Built-In>>path:#SHT20_Temperature]]
249 +
250 +[[Temperature>>path:#SHT20_Temperature]]
251 +)))|(% style="width:106px" %)(((
252 +[[BAT Status &>>path:#BAT_Humidity]]
253 +
254 +[[Built-in>>path:#BAT_Humidity]]
255 +
256 +[[Humidity>>path:#BAT_Humidity]]
257 +)))|(% style="width:108px" %)[[Status & Ext>>path:#Status_EXT]]|(% style="width:116px" %)(((
258 +[[Unix>>path:#Unix_Time_Stamp]]
259 +
260 +[[Time Stamp>>path:#Unix_Time_Stamp]]
261 +)))
262 +
263 +* **Battery status & **[[(% class="wikiinternallink wikiinternallink" %)**Built-in Humidity**>>path:#SHT20_Humidity]]
264 +
265 +(% style="width:587px" %)
266 +|Bit(bit)|(% style="width:280px" %)[15:14]|(% style="width:136px" %)[11:0]
267 +|Value|(% style="width:280px" %)(((
268 +BAT Status
269 +
270 +00(b): Ultra Low ( BAT <= 2.50v)
271 +
272 +01(b): Low  (2.50v <=BAT <= 2.55v)
273 +
274 +10(b): OK   (2.55v <= BAT <=2.65v)
275 +
276 +11(b): Good   (BAT >= 2.65v)
277 +)))|(% style="width:136px" %)(((
278 +[[Built-in Humidity>>path:#SHT20_Humidity]]
279 +
280 +
281 +)))
282 +
283 +* **Status & Ext Byte**
284 +
285 +(% style="width:732px" %)
286 +|(% style="width:128px" %)**Bits**|(% style="width:102px" %)**7**|(% style="width:145px" %)**6**|(% style="width:117px" %)**5**|(% style="width:147px" %)**4**|(% style="width:90px" %)**[3:0]**
287 +|(% style="width:128px" %)**Status & Ext**|(% style="width:102px" %)Not Defined|(% style="width:145px" %)Poll Message Flag|(% style="width:117px" %)Sync time OK|(% style="width:147px" %)Unix Time Request|(% style="width:90px" %)(((
288 +Ext:
289 +
290 +0b(1001)
291 +)))
292 +
293 +* Poll Message Flag: 1: This message is a poll message reply, 0: means this is a normal uplink.
294 +* 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.
295 +* 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)
296 +
297 +== Show data on Datacake ==
298 +
299 +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:
300 +
301 +
302 +**Step 1**: Be sure that your device is programmed and properly connected to the LoRaWAN network.
303 +
304 +**Step 2**: Configure your Application to forward data to Datacake you will need to add integration. Go to TTN V3 Console ~-~-> Applications ~-~-> Integrations ~-~-> Add Integrations.
305 +
306 +
307 +Add Datacake:
308 +
309 +[[image:image-20220523000825-7.png||height="262" width="583"]]
310 +
311 +
312 +Select default key as Access Key:
313 +
314 +[[image:image-20220523000825-8.png||height="453" width="406"]]
315 +
316 +
317 +In Datacake console ([[https:~~/~~/datacake.co/>>url:https://datacake.co/]]) , add LHT65 device.
318 +
319 +[[image:image-20220523000825-9.png||height="366" width="392"]]
320 +
321 +
322 +
323 +[[image:image-20220523000825-10.png||height="432" width="762"]]
324 +
325 +
326 +== Datalog Feature ==
327 +
328 +This feature is always enabled. When user wants to retrieve the sensor value, he can send a poll command from the IoT platform to ask LHT65N to send the value in the required time slot.
329 +
330 +=== Unix TimeStamp ===
331 +
332 +LHT65N uses Unix TimeStamp format based on
333 +
334 +[[image:image-20220523001219-11.png||height="97" width="627"]]
335 +
336 +
337 +User can get this time from link:  [[https:~~/~~/www.epochconverter.com/>>url:https://www.epochconverter.com/]] :
338 +
339 +Below is the converter example
340 +
341 +[[image:image-20220523001219-12.png||height="353" width="853"]]
342 +
343 +So, we can use AT+TIMESTAMP=1611889405 or downlink 3060137afd00 to set the current time 2021 – Jan ~-~- 29 Friday 03:03:25
344 +
345 +
346 +=== Set Device Time ===
347 +
348 +There are two ways to set device’s time:
349 +
350 +**~1. Through LoRaWAN MAC Command (Default settings)**
351 +
352 +User need to set SYNCMOD=1 to enable sync time via MAC command.
353 +
354 +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).
355 +
356 +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.
357 +
358 +
359 +**2. Manually Set Time**
360 +
361 +User needs to set SYNCMOD=0 to manual time, otherwise, the user set time will be overwritten by the time set by the server.
362 +
363 +
364 +=== Poll sensor value ===
365 +
366 +User can poll sensor value based on timestamps from the server. Below is the downlink command.
367 +
368 +
369 +(% style="width:454px" %)
370 +|(% style="width:69px" %)1byte|(% style="width:129px" %)4bytes|(% style="width:134px" %)4bytes|(% style="width:119px" %)1byte
371 +|(% style="width:69px" %)31|(% style="width:129px" %)Timestamp start|(% style="width:134px" %)Timestamp end|(% style="width:119px" %)Uplink Interval
372 +
373 +
374 +Timestamp start and Timestamp end use Unix TimeStamp format as mentioned above. Devices will reply with all data log during this time period, use the uplink interval.
375 +
376 +
377 +For example, downlink command 31 5FC5F350 5FC6 0160 05
378 +
379 +Is to check 2020/12/1 07:40:00 to 2020/12/1 08:40:00’s data
380 +
381 +Uplink Internal =5s，means LHT65N will send one packet every 5s. range 5~~255s.
382 +
383 +
384 +=== Datalog Uplink payload ===
385 +
386 +The Datalog poll reply uplink will use below payload format.
387 +
388 +
389 +Retrieval data payload
390 +
391 +|**Size(bytes)**|**2**|**2**|**2**|**1**|**4**
392 +|**Value**|[[External sensor data>>path:#Extension_sensor_value]]|(((
393 +[[Built-In>>path:#SHT20_Temperature]]
394 +
395 +[[Temperature>>path:#SHT20_Temperature]]
396 +)))|(((
397 +[[Built-in>>path:#SHT20_Humidity]]
398 +
399 +[[Humidity>>path:#SHT20_Humidity]]
400 +)))|[[Poll message flag & Ext>>path:#Poll_EXT]]|(((
401 +[[Unix Time Stamp>>path:#Unix_Time_Stamp]]
402 +
403 +
404 +)))
405 +
406 +
407 +Poll message flag & Ext
408 +
409 +
410 +|**Bits**|**7**|**6**|**5**|**4**|**[3:0]**
411 +|**Status & Ext**|Not Defined|Poll Message Flag|Sync time OK|Unix Time Request|(((
412 +Ext:
413 +
414 +0b(1001)
415 +)))
416 +
417 +
418 +Poll Message Flag: 1: This message is a poll message reply.
419 +
420 +* Poll Message Flag is set to 1.
421 +* Each data entry is 11 bytes, to save airtime and battery, devices will send max bytes according to the current DR and Frequency bands.
422 +
423 +For example, in US915 band, the max payload for different DR is:
424 +
425 +a)      DR0: max is 11 bytes so one entry of data
426 +
427 +b)      DR1: max is 53 bytes so devices will upload 4 entries of data (total 44 bytes)
428 +
429 +c)      DR2: total payload includes 11 entries of data
430 +
431 +d)      DR3: total payload includes 22 entries of data.
432 +
433 +If devise doesn’t have any data in the polling time. Device will uplink 11 bytes of 0   
434 +
435 +
436 +**Example:**
437 +
438 +If LHT65N has below data inside Flash:
439 +
440 +Flash Addr   |Unix Time | Ext | BAT voltage|  Value                  
441 +
442 +80196E0 21/1/19 04:27:03 1 3145 sht_temp=22.00 sht_hum=32.6 ds_temp=327.67
443 +
444 +80196F0 21/1/19 04:28:57 1 3145 sht_temp=21.90 sht_hum=33.1 ds_temp=327.67
445 +
446 +8019700 21/1/19 04:30:30 1 3145 sht_temp=21.81 sht_hum=33.4 ds_temp=327.67
447 +
448 +8019710 21/1/19 04:40:30 1 3145 sht_temp=21.65 sht_hum=33.7 ds_temp=327.67
449 +
450 +8019720 21/1/19 04:50:30 1 3147 sht_temp=21.55 sht_hum=34.1 ds_temp=327.67
451 +
452 +8019730 21/1/19 05:00:30 1 3149 sht_temp=21.50 sht_hum=34.1 ds_temp=327.67
453 +
454 +8019740 21/1/19 05:10:30 1 3149 sht_temp=21.43 sht_hum=34.6 ds_temp=327.67
455 +
456 +8019750 21/1/19 05:20:30 1 3151 sht_temp=21.35 sht_hum=34.9 ds_temp=327.67
457 +
458 +
459 +If user sends below downlink command:
460 +
461 +3160065F9760066DA705
462 +
463 + Where : Start time: 60065F97 = time 21/1/19 04:27:03
464 +
465 + Stop time 60066DA7= time 21/1/19 05:27:03
466 +
467 +
468 +LHT65N will uplink this payload.
469 +
470 +[[image:image-20220523001219-13.png]]
471 +
472 +7FFF089801464160065F977FFF088E014B41600660097FFF0885014E41600660667FFF0875015141600662BE7FFF086B015541600665167FFF08660155416006676E7FFF085F015A41600669C67FFF0857015D4160066C1E
473 +
474 +Where the first 11 bytes is for the first entry:
475 +
476 +7FFF089801464160065F97
477 +
478 +Ext sensor data=0x7FFF/100=327.67
479 +
480 +Temp=0x0898/100=22.00
481 +
482 +Hum=0x0146/10=32.6
483 +
484 +poll message flag & Ext=0x41,means reply data,Ext=1
485 +
486 +Unix time is 0x60065F97=1611030423s=21/1/19 04:27:03
487 +
488 +
489 +== Alarm Mode ==
490 +
491 +Alarm mode feature is added since firmware v1.5. When device is in Alarm mode, it will check the built-in sensor temperature in a short interval. If the temperature exceeds the pre-configure range, it will send an uplink immediately.
492 +
493 +
494 +Note: Alarm mode will increase a little big the power consumption, we recommend extending the normal reading time when enabling this feature.
495 +
496 +
497 +AT Commands for Alarm mode:
498 +
499 +**AT+WMOD=1**: Enable/Disable Alarm Mode. (0:Disable, 1: Enable)
500 +
501 +**AT+CITEMP=1**: The interval to check the temperature for Alarm. (Unit: minute)
502 +
503 +
504 +
85 85  == LED Indicator ==
86 86  
87 87  The LHT65N has a triple color LED which for easy shows different stage.
... ... @@ -95,6 +95,7 @@
95 95  * RED LED when an external sensor is not connected
96 96  * For each success downlink, the PURPLE LED will blink once
97 97  
518 +----
98 98  
99 99  == Installation ==
100 100  
image-20220522232442-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +216.4 KB
Content
image-20220522232812-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +73.4 KB
Content
image-20220522232916-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +69.4 KB
Content
image-20220522232932-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +44.5 KB
Content
image-20220522232954-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +53.7 KB
Content
image-20220522233026-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +48.0 KB
Content
image-20220522233118-7.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +57.6 KB
Content
image-20220522233300-8.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +53.9 KB
Content
image-20220522234038-9.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +38.0 KB
Content
image-20220522234118-10.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +66.7 KB
Content
image-20220522235639-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +43.4 KB
Content
image-20220522235639-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +43.4 KB
Content
image-20220522235639-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +3.7 KB
Content
image-20220522235639-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +43.4 KB
Content
image-20220522235639-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +11.3 KB
Content
image-20220522235639-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +3.7 KB
Content
image-20220523000825-10.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +59.3 KB
Content
image-20220523000825-7.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +126.2 KB
Content
image-20220523000825-8.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +27.1 KB
Content
image-20220523000825-9.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +60.7 KB
Content
image-20220523001219-11.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +18.8 KB
Content
image-20220523001219-12.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +86.2 KB
Content
image-20220523001219-13.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +35.6 KB
Content

Applications

Navigation

Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0