Last modified by Edwin Chen on 2025/01/29 20:30
<
From version < 24.1 >
edited by Xiaoling
on 2022/05/26 16:55
To version < 37.2 >
edited by Xiaoling
on 2022/12/16 10:46
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,14 +1,12 @@
1 -**~ Contents:**
1 +**~ Table of Contents:**
2 2  
3 -(((
4 -
5 -)))
6 -
7 7  {{toc/}}
8 8  
9 9  
10 -= 1. OTAA Join Process Debug =
11 11  
7 += 1.(% style="display:none" %) (%%) OTAA Join Process Debug =
8 +
9 +
12 12  These pages are useful to check what is wrong on the Join process. Below shows the four steps that we can check the Join Process.
13 13  \\**If user has checked below steps and still can't solve the problem, please send us (support @ dragino.com) the sceenshots for each step to check. They include:**
14 14  
... ... @@ -18,18 +18,19 @@
18 18  * End Node traffic (from server UI) to shows end node activity in server. (Normaly possible)
19 19  * End Node Keys screen shot shows in end node and server. so we can check if the keys are correct. (In most case, we found keys doesn't match, especially APP EUI)
20 20  
21 -**~1. End Device Join Screen shot, we can check:**
19 +(% style="color:blue" %)**1. End Device Join Screen shot, we can check:**
22 22  
23 23  * If the device is sending join request to server?
24 24  * What frequency the device is sending?
25 25  
26 -[[image:image-20220526164956-15.png]]
24 +[[image:image-20220526164956-15.png||height="591" width="1153"]]
27 27  
28 28  Console Output from End device to see the transmit frequency
29 29  
30 30  
31 -**2. Gateway packet traffic in gateway web or ssh. we can check:**
32 32  
30 +(% style="color:blue" %)**2. Gateway packet traffic in gateway web or ssh. we can check:**
31 +
33 33  * If the gateway receive the Join request packet from sensor? (If this fail, check if the gateway and sensor works on the match frequency)
34 34  * If the gateway gets the Join Accept message from server and transmit it via LoRa?
35 35  
... ... @@ -38,8 +38,9 @@
38 38  Console Output from Gateway to see packets between end node and server.
39 39  
40 40  
41 -**3. Gateway Traffic Page in LoRaWAN Server**
42 42  
41 +(% style="color:blue" %)**3. Gateway Traffic Page in LoRaWAN Server**
42 +
43 43  * If the Join Request packet arrive the gateway traffic in server? If not, check the internet connection and gateway LoRaWAN server settings.
44 44  * If the server send back a Join Accept for the Join Request? if not, check if the keys from the device match the keys you put in the server, or try to choose a different server route for this end device.
45 45  * If the Join Accept message are in correct frequency? If you set the server to use US915 band, and your end node and gateway is EU868, you will see the Join Accept message are in US915 band so no possible to Join success.
... ... @@ -49,8 +49,9 @@
49 49  The Traffic for the End node in the server, use TTN as example
50 50  
51 51  
52 -**4. Data Page in LoRaWAN server**
53 53  
53 +(% style="color:blue" %)**4. Data Page in LoRaWAN server**
54 +
54 54  * If this data page shows the Join Request message from the end node? If not, most properly you have wrong settings in the keys. Keys in the server doesn't match the keys in End Node.
55 55  
56 56  [[image:image-20220526163704-4.png]]
... ... @@ -57,6 +57,7 @@
57 57  
58 58  The data for the end device set in server
59 59  
61 +
60 60  [[image:image-20220526163732-5.png]]
61 61  
62 62  Check if OTAA Keys match the keys in device
... ... @@ -64,6 +64,7 @@
64 64  
65 65  = 2. Notice of US915/CN470/AU915 Frequency band =
66 66  
69 +
67 67  (((
68 68  If user has problem to work with lorawan server in band US915/AU915/CN470, he can check:
69 69  )))
... ... @@ -102,14 +102,18 @@
102 102  
103 103  US915 Channels
104 104  
108 +
105 105  [[image:image-20220526163926-7.png]]
106 106  
107 107  AU915 Channels
108 108  
113 +
109 109  [[image:image-20220526163941-8.png]]
110 110  
111 111  (((
112 112  CN470 Channels
118 +
119 +
113 113  )))
114 114  
115 115  (((
... ... @@ -120,6 +120,8 @@
120 120  
121 121  (((
122 122  TTN FREQUENCY PLAN
130 +
131 +(% style="display:none" %) (%%)
123 123  )))
124 124  
125 125  (((
... ... @@ -126,22 +126,23 @@
126 126  In dragino end node, user can use AT+CHE command to set what frequencies set the end node will use. The default settings for Dragino end node are preconfigure for TTN server, so use 8~~15 channels, which is **AT+CHE=2**. (AT+CHE=1 for first 8 channels, AT+CHE=2 for second 8 channels.. etc, and AT+CHE=0 for all 72 channels. )
127 127  )))
128 128  
138 +(% style="display:none" %) (%%)
129 129  
130 130  = 3. Why i see data lost/unperiocially uplink data? Even the signal strength is good =
131 131  
142 +
132 132  In this case, we can check if the frequency band matches in End Node, Gateway and LoRaWAN server. A typical case is using US915 in ChirpStack server as below:
133 133  
134 -* **End node** ~-~-> Use Sub-band2 (Channel 8,9,10,11,12,13,14,15) for Dragino Sensor. ADR is also enable, this is the default settings for dragino sensors.
135 -* **Gateway** ~-~-> Use Sub-band2 (Channel 8,9,10,11,12,13,14,15) for Dragino Gateway. this is the default settings for dragino sensors.
136 -* **LoRaWAN server** ~-~-> ChirpStack default installation and use Sub-band1, **enabled_uplink_channels=[0, 1, 2, 3, 4, 5, 6, 7]** in the file chirpstack-network-server.toml.
145 +* (% style="color:blue" %)**End node** (%%) ~-~-> Use Sub-band2 (Channel 8,9,10,11,12,13,14,15) for Dragino Sensor. ADR is also enable, this is the default settings for dragino sensors.
137 137  
147 +* (% style="color:blue" %)**Gateway** (%%) ~-~-> Use Sub-band2 (Channel 8,9,10,11,12,13,14,15) for Dragino Gateway. this is the default settings for dragino sensors.
148 +
149 +* (% style="color:blue" %)**LoRaWAN server**  (%%) ~-~-> ChirpStack default installation and use Sub-band1, **enabled_uplink_channels=[0, 1, 2, 3, 4, 5, 6, 7]** in the file chirpstack-network-server.toml.
150 +
138 138  (((
139 139  When Sensor power on, it will use sub-band2 to join the network, the frequency matches the settings in gateway so all Join Request will be passed to the server for Join. Server will ask the sensor to change to Sub-band1 in the Join Accept downlink message. Sensor will change to sub-band1 for data upload. This cause the sensor and gateway have different frequencies so user see lost of most data or even no data.
140 140  )))
141 141  
142 -(((
143 -
144 -)))
145 145  
146 146  (((
147 147  Use Subband2 as a default subband cause the sensor to have problem to work with the LoRaWAN server which use other subband, and use need to access to the end node to change the subband by console. that is not user frendily,. So since Dragino LoRaWAN Stack version DLS-005(release on end of 2020), we have changed the device to use All Subbands for OTAA join, for example, device will use the first frequency in Sub-Band1 as firt OTAA join packet, then use the first frequency in Sub-Band 2 , then first frequency in sub-band 3, and so on. LoRaWAN server will normally provide the required subband in the OTAA accept process, so end node will know what subband it use after join. If LoRaWAN server doesn't provide subband info in OTAA join, end node will use the subband which join success as the working subband. So the new method cause a longer OTAA Join time but will be compatible with all LoRaWAN server. And new method won't affect the normal uplink after Join Success.
... ... @@ -150,23 +150,16 @@
150 150  
151 151  = 4. Transmision on ABP Mode =
152 152  
163 +
153 153  (((
154 154  In ABP mode, there is a Frame Counter Checks. With this check enabled, the server will only accept the frame with a higher counter. If you reboot the device in ABP mode, the device will start from count 0, so you won't be able to see the frame update in server.
155 155  )))
156 156  
157 157  (((
158 -
159 -)))
160 -
161 -(((
162 162  So in ABP mode, first check if the packet already arrive your gateway, if the packet arrive gatewat but didn't arrive server. Please check if this is the issue.
163 163  )))
164 164  
165 165  (((
166 -
167 -)))
168 -
169 -(((
170 170  To solve this, disable the Frame Counter Check will solve this issue , or reset the frame counter in the device page.
171 171  )))
172 172  
... ... @@ -179,6 +179,7 @@
179 179  
180 180  == 5.1 How it work ==
181 181  
185 +
182 182  LoRaWAN End node will open two receive windows to receive the downstream data. If the downstream packets arrive the end node at these receive windows, the end node will be able to get this packet and process it.
183 183  
184 184  (((
... ... @@ -185,22 +185,30 @@
185 185  Depends on Class A or Class C, the receive windows will be a little difference,
186 186  )))
187 187  
188 -[[image:image-20220526164547-11.png]]
192 +[[image:image-20220531161828-1.png]]
189 189  
190 190  receive windows for Class A and Class C
191 191  
196 +
192 192  Below are the requirement for the End Device to receive the packets.
193 193  
194 194  * The End Device must open the receive windows: RX1 or RX2
200 +
195 195  * The LoRaWAN server must send a downstream packet, and the gateway forward this downstream packet for this end node.
202 +
196 196  * This downstream packet must arrive to the end node while RX1 or RX2 is open.
204 +
197 197  * This packet must match the frequency of the RX1 or RX2 window.
198 -* This packet must match the DataRate of RX1(RX1DR) or RX2 (RX2DR). **This is the common fail point, because different lorawan server might use different RX2DR and they don't info End Node via ADR message so cause the mismatch. If this happen, user need to change the RX2DR to the right value in end node. In OTAA, LoRaWAN Server will send the RX2DR setting in Join Accept message so the end node will auto adjust. but ABP uplink doesn't support this auto change.**
199 199  
207 +* This packet must match the DataRate of RX1(RX1DR) or RX2 (RX2DR). (% style="color:red" %)**This is the common fail point, because different lorawan server might use different RX2DR and they don't info End Node via ADR message so cause the mismatch. If this happen, user need to change the RX2DR to the right value in end node. In OTAA, LoRaWAN Server will send the RX2DR setting in Join Accept message so the end node will auto adjust. but ABP uplink doesn't support this auto change.**
208 +
209 +
210 +
200 200  == 5.2 See Debug Info ==
201 201  
213 +
202 202  (((
203 -**For LoRaWAN Server**
215 +(% style="color:blue" %)**For LoRaWAN Server**
204 204  )))
205 205  
206 206  (((
... ... @@ -229,8 +229,9 @@
229 229  )))
230 230  
231 231  
244 +
232 232  (((
233 -**For LoRaWAN Gateway**
246 +(% style="color:blue" %)**For LoRaWAN Gateway**
234 234  )))
235 235  
236 236  (((
... ... @@ -244,8 +244,9 @@
244 244  )))
245 245  
246 246  
260 +
247 247  (((
248 -**For End Node**
262 +(% style="color:blue" %)**For End Node**
249 249  )))
250 250  
251 251  (((
... ... @@ -253,23 +253,19 @@
253 253  )))
254 254  
255 255  (((
270 +(% style="color:#037691" %)**AT+RX2FQ=869525000**  (%%) **~-~-->**  The RX2 Window frequency
271 +(% style="color:#037691" %)**AT+RX2DR=3**          (%%) **~-~-->**  The RX2 DataRate
272 +(% style="color:#037691" %)**AT+RX1DL=1000**       (%%) ** ~-~-->**  Receive Delay 1
273 +(% style="color:#037691" %)**AT+RX2DL=2000**       (%%) **~-~--> ** Receive Delay 2
274 +
275 +
256 256  
257 257  )))
258 258  
259 259  (((
260 -(% class="box infomessage" %)
261 -(((
262 -AT+RX2FQ=869525000     ~-~--> The RX2 Window frequency
263 -AT+RX2DR=3      ~-~--> The RX2 DataRate
264 -AT+RX1DL=1000   ~-~--> Receive Delay 1
265 -AT+RX2DL=2000   ~-~--> Receive Delay 2
280 +(% style="color:blue" %)**when the device running, we can see below info:**
266 266  )))
267 -)))
268 268  
269 -(((
270 -**when the device running, we can see below info:**
271 -)))
272 -
273 273  {{{ [12502]***** UpLinkCounter= 0 *****
274 274   [12503]TX on freq 868500000 Hz at DR 0
275 275   [13992]txDone
... ... @@ -280,10 +280,12 @@
280 280  
281 281  (((
282 282  
293 +
294 +
283 283  )))
284 284  
285 285  (((
286 -**Another message:**
298 +(% style="color:blue" %)**Another message:**
287 287  )))
288 288  
289 289  {{{ [12502]***** UpLinkCounter= 0 *****
... ... @@ -298,8 +298,9 @@
298 298   1:0012345678}}}
299 299  
300 300  
301 -== 5.3 If problem doesn’t solve ==
313 +== 5.3 If problem doesn't solve ==
302 302  
315 +
303 303  (% style="color:red" %)**If user has checked below steps and still can't solve the problem, please send us (support @ dragino.com) the sceenshots for each step to check. They include:**
304 304  
305 305  * End node console to show the transmit freuqency and DR.
... ... @@ -307,8 +307,11 @@
307 307  * Gateway traffic (from server UI) to shows the data exchange between gateway and server.
308 308  * End Node traffic (from server UI) to shows end node activity in server.
309 309  
323 +
324 +
310 310  = 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
311 311  
327 +
312 312  (((
313 313  In LoRaWAN, the gatewat will use the frequency specify by the server to transmit a packet as downlink purpose. Each Frequency band has different downlink frequency. and the gateway has a frequency range limited to transmit downlink.
314 314  )))
... ... @@ -334,35 +334,31 @@
334 334  
335 335  = 7. Decrypt a LoRaWAN Packet =
336 336  
337 -~1. LHT65 End device configure:
338 338  
339 -(% class="box infomessage" %)
340 -(((
341 -Change to ABP Mode: AT+NJM=0
342 -)))
354 +(% style="color:blue" %)**1. LHT65 End device configure:**
343 343  
344 -(% class="box infomessage" %)
345 -(((
346 -Change to fix frequency: AT+CHS=904900000
347 -)))
356 +**Change to ABP Mode:  AT+NJM=0**
357 +**Change to fix frequency:  AT+CHS=904900000**
358 +**Change to fix DR:  AT+DR=0**
348 348  
349 -(% class="box infomessage" %)
350 -(((
351 -Change to fix DR: AT+DR=0
352 -)))
353 353  
354 -[[image:https://wiki.dragino.com/images/e/e6/Decrypt_a_LoRaWAN_Packet1.jpg||alt="Decrypt a LoRaWAN Packet1.jpg" height="607" width="558"]]
361 +[[image:image-20220526165525-16.png]]
355 355  
356 -2. In LG02 , configure to receive above message
357 357  
358 -[[image:https://wiki.dragino.com/images/c/c3/Decrypt_a_LoRaWAN_Packet2.jpg||alt="Decrypt a LoRaWAN Packet2.jpg" height="337" width="558"]]
359 359  
365 +(% style="color:blue" %)**2. In LG02 , configure to receive above message**
366 +
367 +[[image:image-20220526165612-17.png]]
368 +
369 +
360 360  In LG02 console, we can see the hex receive are:
361 361  
362 -[[image:https://wiki.dragino.com/images/f/f1/Decrypt_a_LoRaWAN_Packet3.jpg||alt="Decrypt a LoRaWAN Packet3.jpg" height="179" width="558"]]
372 +[[image:image-20220526171112-21.png]]
363 363  
364 -3. Decode the info in web
365 365  
375 +
376 +(% style="color:blue" %)**3. Decode the info in web**
377 +
366 366  [[https:~~/~~/lorawan-packet-decoder-0ta6puiniaut.runkit.sh>>url:https://lorawan-packet-decoder-0ta6puiniaut.runkit.sh/]]
367 367  
368 368  Need these three fields:
... ... @@ -373,9 +373,10 @@
373 373  
374 374  AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 11 (End Node App Session Key)
375 375  
388 +
376 376  [[https:~~/~~/lorawan-packet-decoder-0ta6puiniaut.runkit.sh/?data=40c1190126800100024926272bf18bbb6341584e27e23245&nwkskey=00000000000000000000000000000111&appskey=00000000000000000000000000000111>>url:https://lorawan-packet-decoder-0ta6puiniaut.runkit.sh/?data=40c1190126800100024926272bf18bbb6341584e27e23245&nwkskey=00000000000000000000000000000111&appskey=00000000000000000000000000000111]]
377 377  
378 -[[image:https://wiki.dragino.com/images/7/77/Decrypt_a_LoRaWAN_Packet4.png||alt="Decrypt a LoRaWAN Packet4.png" height="390" width="558"]]
391 +[[image:image-20220526171029-20.png]]
379 379  
380 380  (((
381 381   The FRMPayload is the device payload.
... ... @@ -384,12 +384,15 @@
384 384  
385 385  = 8. Why i see uplink 0x00 periodcally on the LHT65 v1.8 firmware =
386 386  
400 +
387 387  Since firmware v1.8, LHT65 will send MAC command to request time, in the case if DR only support max 11 bytes, this MAC command will be bundled to a separate uplink payload with 0x00.
388 388  
403 +
389 389  = 9. Why do I see a "MIC Mismatch" error message from the server? =
390 390  
406 +
391 391  (((
392 -1)If the user receives a "MIC Mismatch" message after registering the node on the server.
408 +1)  If the user receives a "MIC Mismatch" message after registering the node on the server.
393 393  )))
394 394  
395 395  (((
... ... @@ -411,58 +411,121 @@
411 411  * (((
412 412  If a node is registered with multiple servers, it may also cause the "mic mismatch" error.
413 413  
430 +
414 414  
415 415  )))
416 416  
417 417  = 10. Why i got the payload only with "0x00" or "AA~=~="? =
418 418  
419 -* If you are using US915, AU915 and AS923 frequencies.This is normal phenomenon.
420 420  
421 -(((
422 -When using the frequency mentioned above, the server sometimes adjusts the rate of the node, because the node defaults to the adaptive rate.
423 -)))
437 +**Why this happen:**
424 424  
425 -(((
426 -When the server adjusts your node rate to 0, the maximum payload length is 11 bytes. The server sometimes sends an ADR packet to the node,and the node will reply to the server after receiving the ADR packet, but the number of payload bytes exceeds the limit,so it will send a normal uplink packet, and an additional 00 data packet.
427 -)))
439 +For US915, AU915 or AS923 frequencies.It is possible because: .
428 428  
429 -* (((
430 -Solution: Use the decoder to filter out this 00 packet.
431 -)))
432 -* (((
433 -Some node decoders may not have filtering function, or you need decoders of other servers and formats. Please send an email to [[david.huang@dragino.cc>>mailto:david.huang@dragino.cc]]
441 +When using the frequency mentioned above, the server sometimes adjusts the Data Rate (DR) of the node, because the end node has Adaptive Data Rate (ADR) Enabled.
434 434  
443 +When the server adjusts end node data rate to 0, the maximum payload length is 11 bytes. The server sometimes sends an ADR packet to the end node, and the node will reply to the server after receiving the ADR packet, but the number of payload bytes exceeds the limit, so it will send a normal uplink packet, and following an additional 00 data packet to handle this MAC command response.
435 435  
436 -
437 -)))
438 438  
446 +**How to solve:**
447 +
448 +Solution: Use the decoder to filter out this 0x00 packet.
449 +
450 +Some node decoders may not have the filter function, or you need decoders of other servers and formats. Please send an email to [[support@dragino.com>>mailto:support@dragino.com]]
451 +
452 +
439 439  = 11. Why my Dev EUI and APP EUI is 0x000000000000, how to solve? =
440 440  
455 +
456 +(((
441 441  It is possible the keys is erased during upgrading of firmware. and the console output shows below after AT+CFG
458 +)))
442 442  
460 +(((
443 443  AT+APPKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
462 +)))
444 444  
464 +(((
445 445  AT+NWKSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
466 +)))
446 446  
468 +(((
447 447  AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
470 +)))
448 448  
472 +(((
449 449  AT+APPEUI=00 00 00 00 00 00 00 00
474 +)))
450 450  
476 +(((
477 +
478 +)))
451 451  
480 +(((
452 452  You can get the keys from the box sticker or send mail to Dragino Support to check keys with the provided SN number.
482 +)))
453 453  
484 +(((
454 454  You can rewrites the keys by running commands in AT Console
455 455  
456 -For example：
487 +
488 +)))
457 457  
490 +(((
491 +**For example：**
492 +)))
493 +
494 +(((
458 458  AT+APPKEY=85 41 47 20 45 58 28 14 16 82 A0 F0 80 0D DD EE
496 +)))
459 459  
498 +(((
460 460  AT+NWKSKEY=AA CC B0 20 30 45 37 32 14 1E 14 93 E2 3B 20 11
500 +)))
461 461  
502 +(((
462 462  AT+APPSKEY=11 23 02 20 30 20 30 60 80 20 20 30 30 20 10 10
504 +)))
463 463  
506 +(((
464 464  AT+APPEUI=2C 45 47 E3 24 12 23 24
508 +)))
465 465  
510 +(((
466 466  (Any combination of 16 bit codes can be used）
467 467  
468 468  
514 += 12. I set my device is LoRaWAN Class C mode, why i still see Class A after boot? =
515 +)))
516 +
517 +
518 +Class C only refers to status after OTAA Join successfully. The OTAA Join Process will use Class A mode.
519 +
520 +
521 += 13. Why it takes longer time for OTAA joined in US915/CN470/AU915 band? =
522 +
523 +
524 +In US915, AU915 or CN470 frequency band, there are 8 subbands, totally 72 channels. and LoRaWAN server normally use only one sub-band, for example Subband 2 in TTN. The gateway also configured to Subband 2 and cover eight channels in this subband. If the end node transfer data in Subband 2, it will reach to gateway and to the LoRaWAN server. If the end node transfer packets in other subbands, for example subband 1, the packet won't arrive both gateway or LoRaWAN server.
525 +
526 +
527 +In Dragino Sensors old version firmware (before early 2022), the subband is fixed the subband to 2 , but this cause a problem, the end node is hard to use in other subband and need program. So the new logic is as below:
528 +
529 +We have improved this, the end node will use frequency 1 from sub-band1, then frequency 1 from sub-band2, then frequency 1 from sub-band3, etc to process the OTAA join, In this case, In this case, the end node can support LoRaWAN servers with different subbands. To make sure the end node will only transmit the proper sub-band after OTAA Joined successfully, the end node will:
530 +
531 +* (((
532 +Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that subband
533 +)))
534 +* (((
535 +Use the Join successful sub-band if the server doesn't include subband info in the OTAA Join Accept message ( TTN v2 doesn't include)
536 +)))
537 +
538 +This change will make the activation time a littler longer but make sure the device can be used in any subband.
539 +
540 +
541 +Below is a photo to show why it takes longer time for OTAA Join. We can see in 72 channels mode, why it takes more time to join success. If users want to have faster OTAA Join success, he can change default CHE to the subband he use.
542 +
543 +
544 +[[image:image-20221215223215-1.png||height="584" width="1280"]]
545 +
546 +(% class="wikigeneratedid" %)
547 +
image-20220526165612-17.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +116.5 KB
Content
image-20220526165855-18.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +183.7 KB
Content
image-20220526170151-19.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +70.4 KB
Content
image-20220526171029-20.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +70.6 KB
Content
image-20220526171112-21.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +183.8 KB
Content
image-20220531161828-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +98.6 KB
Content
image-20221215223215-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +183.6 KB
Content

Applications

Navigation

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