<
From version < 138.3 >
edited by Xiaoling
on 2023/04/21 15:49
To version < 108.9 >
edited by Xiaoling
on 2022/07/23 14:21
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -38,6 +38,7 @@
38 38  )))
39 39  
40 40  
41 +
41 41  = 2.  Semtech UDP =
42 42  
43 43  == 2.1  Step 1. Add the Network-servers ==
... ... @@ -60,6 +60,7 @@
60 60  Add the Network-servers
61 61  
62 62  
64 +
63 63  == 2.2  Step 2. Create Gateway-profiles ==
64 64  
65 65  
... ... @@ -68,6 +68,7 @@
68 68  Create Gateway-profiles
69 69  
70 70  
73 +
71 71  == 2.3  Step 3. Create Service-profiles ==
72 72  
73 73  
... ... @@ -83,6 +83,7 @@
83 83  If the user has completed the preceding steps, proceed to the next step.(% style="display:none" %)
84 84  
85 85  
89 +
86 86  == 2.4  Step 4. Add the gateway ==
87 87  
88 88  
... ... @@ -105,6 +105,7 @@
105 105  Configure the gateway
106 106  
107 107  
112 +
108 108  == 2.5  Step 5. Checking gateway Status ==
109 109  
110 110  
... ... @@ -119,8 +119,10 @@
119 119  gateway Status
120 120  
121 121  
127 +
122 122  = 3.  Gateway Registration for Basics Station =
123 123  
130 +
124 124  == 3.1  Introduction ==
125 125  
126 126  
... ... @@ -134,6 +134,7 @@
134 134  1. LoRaWAN Gateway model: [[LIG16>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/171-lig16.html]], [[LG308>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/140-lg308.html]], [[DLOS8>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/160-dlos8.html]] ,[[LPS8>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/148-lps8.html]]
135 135  1. Firmware version since :[[lgw~~-~~-build-v5.4.1651822913>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Test_Firmware/lgw--build-v5.4.1651822913-20220506-1543/]]
136 136  
144 +
137 137  (% style="color:blue" %)**How to set up chirpStack Basic Station**
138 138  
139 139  Users can check out the ChirpStack Basic Station [[link>>https://www.chirpstack.io/gateway-bridge/backends/basic-station/]] and [[forum>>https://forum.chirpstack.io/search?q=basic%20station]]
... ... @@ -144,6 +144,7 @@
144 144  A gateway that can access the internet normally
145 145  
146 146  
155 +
147 147  == 3.2  Add Gateway ==
148 148  
149 149  
... ... @@ -176,7 +176,7 @@
176 176  == 3.4  Start Station ==
177 177  
178 178  
179 -When the user has finished the configuration, Please click **Sace&Apply** to start station to connect ChirpStack.
188 +When the user has finished the configuration, Please click Sace&Apply to start station to connect ChirpStack
180 180  
181 181  
182 182  == 3.5  Successful Connection ==
... ... @@ -187,6 +187,7 @@
187 187  [[image:image-20220524164448-13.png]]
188 188  
189 189  
199 +
190 190  == 3.6  Trouble Shooting ==
191 191  
192 192  
... ... @@ -200,264 +200,31 @@
200 200  [[image:image-20220531172857-9.png]]
201 201  
202 202  
203 -= 4.  How the gateway connects to Chirpstack v3 via gateway-bridge =
204 204  
214 += 4. Downlink =
205 205  
206 -(% style="color:blue" %)**Below list the support products and Requirements:**
216 +== 4.1 Chirpstack Downlink Note ==
207 207  
208 -1. LoRaWAN Gateway model: [[LIG16>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/171-lig16.html]], [[LG308>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/140-lg308.html]], [[DLOS8>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/160-dlos8.html]] ,[[LPS8>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/148-lps8.html]],[[LPS8N>>url:https://www.dragino.com/products/lora-lorawan-gateway/item/200-lps8n.html]],[[LG308N>>url:https://www.dragino.com/products/lora-lorawan-gateway/item/229-lg308n.html]],[[DLOS8N>>url:https://www.dragino.com/products/lora-lorawan-gateway/item/225-dlos8n.html]]
209 -1. Firmware version since: [[Chirpstack-Bridge-V3.14.6>>https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/Chirpstack-gateway-bridge/Chirpstack-Bridge-V3.14.6-Bridge--build-v5.4.1679487778-20230322-2024/]]
210 210  
211 -(% style="color:blue" %)**How to set up chirpStack Gateway-bridge**
212 -
213 -Users can check out the ChirpStack gateway-bridge v3 [[link>>https://www.chirpstack.io/gateway-bridge/gateway/dragino/]]
214 -
215 -
216 -(% style="color:blue" %)**What do you need to prepare**
217 -
218 -A gateway that can access the internet normally
219 -
220 -
221 -The following example does not have configuration certificates:
222 -
223 -
224 -== 4.1  Configure Packet Forwarder ==
225 -
226 -
227 -In the Dragino gateway web interface, you need to configure the Packet Forwarder so that it forwards its data to the port. localhost:1700 or 127.0.0.1:1700
228 -
229 -* In the (% style="color:blue" %)**LoRaWAN** (%%)menu, click on (% style="color:blue" %)**LoRaWAN ~-~- Semtech UDP**
230 -
231 -* Make sure the following settings are set:
232 -
233 -* **Service Provider:** //~-~-Custom/Private LoRaWAN~-~-//
234 -
235 -* **LoRaWAN Server Address:** //localhost or 127.0.0.1//
236 -
237 -* **Server port for upstream:** //1700//
238 -
239 -* **Server port for downstream:** //1700//
240 -
241 - Click (% style="color:blue" %)**Save & Apply**.
242 -
243 -[[image:image-20221222114220-2.png||height="748" width="931"]]
244 -
245 -
246 -== 4.2  Configuring gateway frequency ==
247 -
248 -
249 -(% style="color:red" %)**Note: Gateway frequencies must match**
250 -
251 -[[image:image-20221222134830-3.png||height="408" width="923"]]
252 -
253 -
254 -== 4.3  Generate and modify the gateway-bridge configuration file ==
255 -
256 -
257 -**1)Generate the gateway-bridge configuration file**
258 -
259 -By default, the configuration file is not up-to-date,so the user needs to rebuild the gateway-bridge configuration file.
260 -
261 -Users need to access the command line of the gateway through SSH,Then type the following command:
262 -
263 -(% class="box infomessage" %)
264 -(((
265 -/opt/chirpstack-gateway-bridge/chirpstack-gateway-bridge configfile > /etc/chirpstack-gateway-bridge/chirpstack-gateway-bridge.toml
266 -)))
267 -
268 -
269 -**2)modify the gateway-bridge configuration file**
270 -
271 -The user needs to modify the server address in line 252 in the configuration file
272 -
273 -(% class="box infomessage" %)
274 -(((
275 -vim /etc/chirpstack-gateway-bridge/chirpstack-gateway-bridge.toml
276 -)))
277 -
278 -[[image:image-20230415165254-1.png||height="583" width="956"]]
279 -
280 -
281 -== 4.4  Debug ==
282 -
283 -
284 -After the above configuration is completed, the user can enter the command to debug the gateway-bridge connection
285 -
286 -(% class="box infomessage" %)
287 -(((
288 -/opt/chirpstack-gateway-bridge/chirpstack-gateway-bridge ~-~-config /etc/chirpstack-gateway-bridge/chirpstack-gateway-bridge.toml
289 -)))
290 -
291 -If the gateway-bridge connection is normal, the debug log displays **"connected to mqtt broker"**.
292 -
293 -[[image:image-20230415170404-2.png]]
294 -
295 -
296 -If the debug log shows "**connection error**", check that the server port or server is correct
297 -
298 -[[image:image-20230415170854-3.png]]
299 -
300 -
301 -More information can be found on the **[[ChirpStack website>>https://www.chirpstack.io/docs/]]**or **[[Forum>>url:https://forum.chirpstack.io/]]**
302 -
303 -
304 -== 4.5  (Re)start and stop gateway-bridge ==
305 -
306 -
307 -Use the following commands to (re)start and stop the ChirpStack Gateway Bridge Service:
308 -
309 -(% class="box infomessage" %)
310 -(((
311 -**# start**
312 -
313 -/etc/init.d/chirpstack-gateway-bridge start
314 -
315 -**# stop**
316 -
317 -/etc/init.d/chirpstack-gateway-bridge stop
318 -
319 -**# restart**
320 -
321 -/etc/init.d/chirpstack-gateway-bridge restart
322 -)))
323 -
324 -
325 -= 5.  How the gateway connects to Chirpstack v4 via gateway-bridge =
326 -
327 -
328 -(% style="color:blue" %)**Below list the support products and Requirements:**
329 -
330 -1. LoRaWAN Gateway model: [[LIG16>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/171-lig16.html]], [[LG308>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/140-lg308.html]], [[DLOS8>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/160-dlos8.html]] ,[[LPS8>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/148-lps8.html]],[[LPS8N>>url:https://www.dragino.com/products/lora-lorawan-gateway/item/200-lps8n.html]],[[LG308N>>url:https://www.dragino.com/products/lora-lorawan-gateway/item/229-lg308n.html]],[[DLOS8N>>url:https://www.dragino.com/products/lora-lorawan-gateway/item/225-dlos8n.html]]
331 -1. Firmware version since: [[Chirpstack-Bridge-V4>>https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/Chirpstack-gateway-bridge/Chirpstack-Bridge-V4--build-v5.4.1670655072-20221210-1452/]]
332 -
333 -(% style="color:blue" %)**How to set up chirpStack Gateway-bridge**
334 -
335 -Users can check out the ChirpStack gateway-bridge v4 [[link>>https://www.chirpstack.io/docs/chirpstack-gateway-bridge/install/dragino.html]]
336 -
337 -
338 -(% style="color:blue" %)**What do you need to prepare**
339 -
340 -A gateway that can access the internet normally
341 -
342 -
343 -== 5.1  Configure Packet Forwarder ==
344 -
345 -
346 -In the Dragino gateway web interface, you need to configure the Packet Forwarder so that it forwards its data to the port. localhost:1700 or 127.0.0.1:1700
347 -
348 -* In the **LoRaWAN** menu, click on **LoRaWAN ~-~- Semtech UDP**
349 -* Make sure the following settings are set:
350 -** **Service Provider:** //~-~-Custom/Private LoRaWAN~-~-//
351 -** **LoRaWAN Server Address:** //localhost or 127.0.0.1//
352 -** **Server port for upstream:** //1700//
353 -** **Server port for downstream:** //1700//
354 -
355 - Click **Save & Apply**.
356 -
357 -[[image:image-20221222114220-2.png||height="748" width="931"]]
358 -
359 -
360 -== 5.2  Configuring gateway frequency ==
361 -
362 -
363 -(% style="color:red" %)**Note: Gateway frequencies must match**
364 -
365 -[[image:image-20221222134830-3.png||height="408" width="923"]]
366 -
367 -
368 -== 5.3  Modify the gateway-bridge configuration file ==
369 -
370 -
371 -Run the gateway command line command to modify the gateway-bridge configuration file:
372 -
373 -(% class="box infomessage" %)
374 -(((
375 -root@dragino-1d27d4:~~#  vim /etc/chirpstack-gateway-bridge/chirpstack-gateway-bridge.toml
376 -)))
377 -
378 -[[image:image-20221222113302-1.png]]
379 -
380 -
381 -[[image:image-20221222140203-4.png||height="875" width="806"]]
382 -
383 -[[image:image-20221230094246-1.png||height="768" width="783"]]
384 -
385 -(% class="wikigeneratedid" id="H" %)
386 -After the modification, run the following command: **/etc/init.d/chirpstack-gateway-bridge restart**
387 -
388 -
389 -== 5.4  (Re)start and stop gateway-bridge ==
390 -
391 -
392 -Use the following commands to (re)start and stop the ChirpStack Gateway Bridge Service:
393 -
394 -(% class="box infomessage" %)
395 -(((
396 -**# start**
397 -
398 -/etc/init.d/chirpstack-gateway-bridge start
399 -
400 -**# stop**
401 -
402 -/etc/init.d/chirpstack-gateway-bridge stop
403 -
404 -**# restart**
405 -
406 -/etc/init.d/chirpstack-gateway-bridge restart
407 -)))
408 -
409 -
410 -== 5.5  Successful Connection ==
411 -
412 -
413 -[[image:image-20221222141754-5.png||height="488" width="1150"]]
414 -
415 -
416 -[[image:image-20221222141830-6.png||height="582" width="1153"]]
417 -
418 -
419 -= 6.  Downlink =
420 -
421 -== 6.1  Convert HEX to Base64 ==
422 -
423 -
424 -(% style="color:red" %)**Note: Chirpstack uses base64 to downlink, the end node user manual provides HEX format of the downlink commands. So user needs to convert the HEX to Base64.**
425 -
426 -**[[Online HEX to Base64 Converter>>https://base64.guru/converter/encode/hex]]:**
427 -
428 -[[image:image-20221010193350-1.png]]
429 -
430 -
431 -
432 -**[[Online Base64 to Hex converter>>https://base64.guru/converter/decode/hex]]**
433 -
434 -[[image:image-20221010193621-2.png]]
435 -
436 -
437 -== 6.2  Chirpstack Downlink Note ==
438 -
439 -
440 440  [[image:image-20220601102543-2.png]]
441 441  
442 -**Convert the data to Base64**
221 +Convert the data to Base64
443 443  
444 -(% style="display:none" %) (%%)
445 445  
224 +[[image:image-20220531173236-10.png]]
446 446  
447 -[[image:image-20220531173236-10.png||height="597" width="1215"]]
226 +Check ChripStack downlink DataRate
448 448  
449 -**Check ChripStack downlink DataRate**
450 450  
451 -
452 -
453 453  [[image:image-20220525101326-11.png]]
454 454  
455 -**Make sure the RX2DR is the same in the end node**
231 +Make sure the RX2DR is the same in the end node
456 456  
457 457  
458 -== 6.3  Loraserver Downlink Note ==
459 459  
235 +== 4.2  Loraserver Downlink Note ==
460 460  
237 +
461 461  User can use MQTT to send downlink payload to ChirpStack to perform downstream to LoRaWAN End
462 462  
463 463  (((
... ... @@ -475,7 +475,7 @@
475 475  [[image:image-20220531173419-11.png]]
476 476  
477 477  (((
478 -**MQTT Connect to ChirpStack**
255 +MQTT Connect to ChirpStack
479 479  
480 480  
481 481  
... ... @@ -502,11 +502,21 @@
502 502  
503 503  [[image:image-20220531173519-12.png]]
504 504  
505 -**MQTT Connect to ChirpStack**
282 +MQTT Connect to ChirpStack
506 506  
507 507  
508 -**If we want to send downstream hex 030101 to end node, the BASE64 payload is AwEB**
285 +(((
286 +(% style="color:red" %)**Note: Chirpstack use base64 to downlink, so need to convert the downlink payload from HEX to base64 [[https:~~/~~/base64.us/>>url:https://base64.us/]]**
287 +)))
509 509  
289 +[[image:image-20220531173601-13.png]]
290 +
291 +Choose to Use Hex for Encode
292 +
293 +
294 +
295 +If we want send downstream hex 030101 to end node, the BASE64 payload is AwEB
296 +
510 510  [[image:image-20220531173658-14.png]]
511 511  
512 512  
... ... @@ -527,15 +527,15 @@
527 527   {
528 528   if(sha1[n] >= 'A' && sha1[n] <= 'Z')
529 529   {
530 - ascv = sha1.charCodeAt( n ) - 55;
317 + ascv = sha1.charCodeAt(n) - 55;
531 531   }
532 532   else if(sha1[n] >= 'a' && sha1[n] <= 'z')
533 533   {
534 - ascv = sha1.charCodeAt( n ) - 87;
321 + ascv = sha1.charCodeAt(n) - 87;
535 535   }
536 536   else
537 537   {
538 - ascv = sha1.charCodeAt( n ) - 48;
325 + ascv = sha1.charCodeAt(n) - 48;
539 539   }
540 540  \\ bit_arr = (bit_arr << 4) | ascv;
541 541   bit_num += 4;
... ... @@ -572,12 +572,13 @@
572 572  )))
573 573  
574 574  
575 -== 6.3  Add the decode function in Chirpstack for the payload ==
576 576  
363 +== 4.3  Add the decode function in Chirpstack for the payload ==
577 577  
365 +
578 578  User enters the payload code according to the steps.
579 579  
580 -[[image:image-20220531173754-15.png||height="474" width="1334"]]
368 +[[image:image-20220531173754-15.png]]
581 581  
582 582  
583 583  [[image:image-20220531173856-16.png]]
... ... @@ -588,9 +588,10 @@
588 588  [[image:image-20220531174046-19.png]]
589 589  
590 590  
591 -= 7.  Multiply Uplink in ChirpStack =
592 592  
380 += 5.  Multiply Uplink in ChirpStack =
593 593  
382 +
594 594  (((
595 595  nbtrans field is the value to determine the re-transmission time for unconfirmed uplink data.
596 596  )))
... ... @@ -601,7 +601,7 @@
601 601  
602 602  )))
603 603  
604 -[[image:image-20220526091912-7.png||height="241" width="1336"]]
393 +[[image:image-20220526091912-7.png]]
605 605  
606 606  
607 607  (((
... ... @@ -626,19 +626,20 @@
626 626  
627 627  
628 628  
629 -**Duplicate transmission in short time**
418 +Duplicate transmission in short time
630 630  
631 -[[image:image-20220601102430-1.png||height="598" width="1319"]]
420 +[[image:image-20220601102430-1.png]]
632 632  
633 633  
634 -== 7.1  Solution ==
635 635  
424 +== 5.1  Solution ==
636 636  
426 +
637 637  This example uses the Windows version as a template, other versions can refer to this. Similiar reference: [[https:~~/~~/confluence.alitecs.de/plugins/servlet/mobile?contentId=79790102#content/view/79790102>>url:https://confluence.alitecs.de/plugins/servlet/mobile?contentId=79790102#content/view/79790102]]
638 638  
639 639  
640 640  (((
641 -(% style="color:blue" %)**1.  Install the GO compilation environment: Download the corresponding version of the Go compiler at [[https:~~/~~/go.dev/dl/>>url:https://go.dev/dl/]] and install it.**
431 +(% style="color:blue" %)**1. Install the GO compilation environment: Download the corresponding version of the Go compiler at [[https:~~/~~/go.dev/dl/>>url:https://go.dev/dl/]] and install it.**
642 642  
643 643  
644 644  )))
... ... @@ -653,7 +653,7 @@
653 653  
654 654  
655 655  (((
656 -(% style="color:blue" %)**2.  Environment variable settings:**
446 +(% style="color:blue" %)**2. Environment variable settings:**
657 657  )))
658 658  
659 659  (((
... ... @@ -678,7 +678,7 @@
678 678  
679 679  
680 680  
681 -(% style="color:blue" %)**3.  Modify the ADR configuration file according to your own needs, adr.setting.go is an example of the ADR configuration file.**
471 +(% style="color:blue" %)**3. Modify the ADR configuration file according to your own needs, adr.setting.go is an example of the ADR configuration file.**
682 682  
683 683  The name of the plugin: Example ADR plugin:
684 684  
... ... @@ -690,7 +690,7 @@
690 690  
691 691  
692 692  
693 -(% style="color:blue" %)**4.  Compile the ADR configuration file and generate the exe file.**
483 +(% style="color:blue" %)**4. Compile the ADR configuration file and generate the exe file.**
694 694  
695 695  1) Create a folder named adr-setting
696 696  
... ... @@ -716,7 +716,7 @@
716 716  
717 717  
718 718  
719 -(% style="color:blue" %)**5.  Add the plugin and run the plugin.**
509 +(% style="color:blue" %)**5. Add the plugin and run the plugin.**
720 720  
721 721  (((
722 722  The exe file generated in the previous step is placed in the same root directory as chirpstack-network-server.toml, and the ADR plugin is added to the toml file. The location of the addition is as follows:
... ... @@ -753,68 +753,16 @@
753 753  Finish.
754 754  
755 755  
756 -= 8.  How to store/get all data traffic for a specific sensor, including raw payload, and uplink/ downlink history. =
757 757  
547 += 6. Trouble Shooting =
758 758  
759 -All data is published to the MQTT topics. if you want to store/get the data, you would have to create an MQTT handler and store the data yourself.
549 +== 6.1 MIC Mismatch or MIC Failed ==
760 760  
761 -This example will be shown how to store/get all the data in two ways:
762 762  
763 -**//1). Chirpstack ~-~-> Node-red//**
764 -
765 -
766 -[[image:image-20221012184501-1.png]]
767 -
768 -
769 -Use MQTT in Nore-red to subscribe to topics published by the chirpstack-application and then continuously write to a file
770 -
771 -[[image:image-20221012174220-2.png]]
772 -
773 -
774 -[[image:image-20221012184655-3.png||height="395" width="1049"]]
775 -
776 -
777 -**Each message is continuously logged to a specified file**
778 -
779 -[[image:image-20221012174352-3.png]]
780 -
781 -
782 -**//2). MQTT  Sub//**
783 -
784 -If you don't want to store the information via node-red, you can get the output via the subscribe command.
785 -
786 -
787 -**If connecting from the same machine, you can use the following command to receive data:**
788 -
789 -(% class="box infomessage" %)
790 790  (((
791 -mosquitto_sub -h localhost -t "application/#" -v
792 -)))
793 -
794 -
795 -**Different host**
796 -
797 -(% class="box infomessage" %)
798 -(((
799 -mosquitto_sub -h IPADDRESS -p 8883 ~-~-insecure ~-~-cafile ca.pem ~-~-cert cert.pem ~-~-key key.pem -t "application/#" -v
800 -)))
801 -
802 -[[image:image-20221012173639-1.png]]
803 -
804 -
805 -= 9.  Trouble Shooting =
806 -
807 -== 9.1  MIC Mismatch or MIC Failed ==
808 -
809 -
810 -(((
811 811  When the device is registered or the device is working normally, the problem of MIC mismatch and MIC failed occurs.
812 812  )))
813 813  
814 814  (((
815 815  Under normal circumstances, users need to change the APPKEY to solve this problem.
816 -
817 -
818 -
819 -
820 820  )))
image-20221010193350-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -42.7 KB
Content
image-20221010193621-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -34.2 KB
Content
image-20221012173639-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoye
Size
... ... @@ -1,1 +1,0 @@
1 -56.2 KB
Content
image-20221012174220-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoye
Size
... ... @@ -1,1 +1,0 @@
1 -14.8 KB
Content
image-20221012174352-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoye
Size
... ... @@ -1,1 +1,0 @@
1 -93.0 KB
Content
image-20221012184501-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoye
Size
... ... @@ -1,1 +1,0 @@
1 -91.3 KB
Content
image-20221012184631-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoye
Size
... ... @@ -1,1 +1,0 @@
1 -32.4 KB
Content
image-20221012184655-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoye
Size
... ... @@ -1,1 +1,0 @@
1 -45.4 KB
Content
image-20221222113302-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -76.3 KB
Content
image-20221222114220-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -64.3 KB
Content
image-20221222134830-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -54.5 KB
Content
image-20221222140203-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -91.4 KB
Content
image-20221222141754-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -179.1 KB
Content
image-20221222141830-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -116.7 KB
Content
image-20221230094246-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -84.9 KB
Content
image-20230415165254-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -67.2 KB
Content
image-20230415170404-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -17.9 KB
Content
image-20230415170854-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -48.4 KB
Content
Copyright ©2010-2022 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0