Changes for page Notes for ChirpStack

Last modified by Edwin Chen on 2025/01/30 09:53
<
From version < 108.4 >
edited by Xiaoling
on 2022/07/23 13:54
To version < 133.1 >
edited by Kilight Cao
on 2022/12/30 09:43
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.Kilight
Content
... ... @@ -38,7 +38,6 @@
38 38  )))
39 39  
40 40  
41 -
42 42  = 2.  Semtech UDP =
43 43  
44 44  == 2.1  Step 1. Add the Network-servers ==
... ... @@ -48,12 +48,12 @@
48 48  
49 49  (% class="box" %)
50 50  (((
51 - Windows       ~-~->  Network-server server * : localhost:8000
52 - Linux  ~-~->  Network-server server * : chirpstack-network-server:8000
50 + Windows       ~-~->  Network-server server *  :  localhost:8000
51 + Linux  ~-~->  Network-server server *  :  chirpstack-network-server:8000
53 53  )))
54 54  
55 55  
56 -If the user cannot add network-Servers, re-check the ChirpStack code or the server building process.
55 +(% style="color:red" %)**If the user cannot add network-Servers, re-check the ChirpStack code or the server building process.**
57 57  
58 58  
59 59  [[image:image-20220531171609-1.png]]
... ... @@ -61,8 +61,8 @@
61 61  Add the Network-servers
62 62  
63 63  
63 +== 2.2  Step 2. Create Gateway-profiles ==
64 64  
65 -== 2.2 Step 2. Create Gateway-profiles ==
66 66  
67 67  [[image:image-20220531171651-2.png]]
68 68  
... ... @@ -69,8 +69,9 @@
69 69  Create Gateway-profiles
70 70  
71 71  
72 -== 2.3 Step 3. Create Service-profiles ==
71 +== 2.3  Step 3. Create Service-profiles ==
73 73  
73 +
74 74  [[image:image-20220531171809-3.png]]
75 75  
76 76  Create Service-profiles
... ... @@ -83,29 +83,35 @@
83 83  If the user has completed the preceding steps, proceed to the next step.(% style="display:none" %)
84 84  
85 85  
86 -== 2.4 Step 4. Add the gateway ==
86 +== 2.4  Step 4. Add the gateway ==
87 87  
88 +
88 88  The example gateway id is: a840411e96744150
89 89  
90 90  (((
91 91  (% style="color:red" %)**Note : The Gateway EUI and server addresses must match the ChirpStack configuration.**
93 +
94 +
92 92  )))
93 93  
94 94  [[image:image-20220531171923-4.png]](% style="display:none" %)
95 95  
96 -
97 97  Add the gateway
98 98  
101 +
102 +
99 99  [[image:image-20220531172031-5.png]]
100 100  
101 101  Configure the gateway
102 102  
103 103  
104 -== 2.5 Step 5. Checking gateway Status ==
108 +== 2.5  Step 5. Checking gateway Status ==
105 105  
110 +
106 106  [[image:image-20220531172158-6.png]](% style="display:none" %)
107 107  
108 108  
114 +
109 109  gateway Status
110 110  
111 111  [[image:image-20220531172304-7.png]]
... ... @@ -113,39 +113,45 @@
113 113  gateway Status
114 114  
115 115  
116 -= 3. Gateway Registration for Basics Station =
122 += 3.  Gateway Registration for Basics Station =
117 117  
118 -== 3.1 Introduction ==
124 +== 3.1  Introduction ==
119 119  
126 +
120 120  The [[Semtech Basic Station>>url:https://doc.sm.tc/station/]] backend implements the [[LNS protocol>>url:https://doc.sm.tc/station/tcproto.html]]. It exposes a WebSocket handler to which Basic Station powered gateways can connect.
121 121  
122 122  ChirpStack Open-Source LoRaWAN® Network Server needs to set up a configuration that can use Semtech BasicStation.
123 123  
124 -**Below list the support products and Requirements:**
125 125  
132 +(% style="color:blue" %)**Below list the support products and Requirements:**
133 +
126 126  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]]
127 127  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/]]
128 128  
129 -**How to set up chirpStack Basic Station**
137 +(% style="color:blue" %)**How to set up chirpStack Basic Station**
130 130  
131 131  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]]
132 132  
133 -**What do you need to prepare**
134 134  
142 +(% style="color:blue" %)**What do you need to prepare**
143 +
135 135  A gateway that can access the internet normally
136 136  
137 137  
138 -== 3.2 Add Gateway ==
147 +== 3.2  Add Gateway ==
139 139  
149 +
140 140  [[image:image-20220524164205-10.png]]
141 141  
142 142  
143 -== 3.3 Access the gateway GUI ==
153 +== 3.3  Access the gateway GUI ==
144 144  
155 +
145 145  Access the gateway GUI interface of LoRaWAN~-~->LoRaWAN ~-~- Basic Station
146 146  
147 147  [[image:image-20220524164319-11.png]]
148 148  
160 +
149 149  User need to Choose the ChirpStack/Senet ~-~- Basic Station , input Server URI and Upload the TLS Certificate
150 150  
151 151  (% class="box" %)
... ... @@ -161,20 +161,23 @@
161 161  [[image:image-20220524164341-12.png]]
162 162  
163 163  
164 -== 3.4 Start Station ==
176 +== 3.4  Start Station ==
165 165  
166 -When the user has finished the configuration, Please click Sace&Apply to start station to connect ChirpStack
167 167  
179 +When the user has finished the configuration, Please click **Sace&Apply** to start station to connect ChirpStack.
168 168  
169 -== 3.5 Successful Connection ==
170 170  
182 +== 3.5  Successful Connection ==
183 +
184 +
171 171  If user completes the above steps, which will see live date in the ChirpStack.
172 172  
173 173  [[image:image-20220524164448-13.png]]
174 174  
175 175  
176 -== 3.6 Trouble Shooting ==
190 +== 3.6  Trouble Shooting ==
177 177  
192 +
178 178  User can check the station log in the logread/system log page.
179 179  
180 180  [[image:image-20220531172837-8.png]]
... ... @@ -185,31 +185,146 @@
185 185  [[image:image-20220531172857-9.png]]
186 186  
187 187  
188 -= 4. Downlink =
203 += 4.  How the gateway connects to Chirpstack v4 via gateway-bridge =
189 189  
190 -== 4.1 Chirpstack Downlink Note ==
191 191  
206 +(% style="color:blue" %)**Below list the support products and Requirements:**
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-gateway-bridge>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/Chirpstack-gateway-bridge/]]
210 +
211 +(% style="color:blue" %)**How to set up chirpStack Gateway-bridge**
212 +
213 +Users can check out the ChirpStack gateway-bridge v4 [[link>>https://www.chirpstack.io/docs/chirpstack-gateway-bridge/install/dragino.html]]
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 +== 4.1  Configure Packet Forwarder ==
222 +
223 +
224 +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
225 +
226 +* In the **LoRaWAN** menu, click on **LoRaWAN ~-~- Semtech UDP**
227 +* Make sure the following settings are set:
228 +** **Service Provider:** //~-~-Custom/Private LoRaWAN~-~-//
229 +** **LoRaWAN Server Address:** //localhost or 127.0.0.1//
230 +** **Server port for upstream:** //1700//
231 +** **Server port for downstream:** //1700//
232 +
233 + Click **Save & Apply**.
234 +
235 +[[image:image-20221222114220-2.png||height="748" width="931"]]
236 +
237 +
238 +== 4.2  Configuring gateway frequency ==
239 +
240 +
241 +(% style="color:red" %)**Note: Gateway frequencies must match**
242 +
243 +[[image:image-20221222134830-3.png||height="408" width="923"]]
244 +
245 +
246 +== 4.3  Modify the gateway-bridge configuration file ==
247 +
248 +
249 +Run the gateway command line command to modify the gateway-bridge configuration file:
250 +
251 +(% class="box infomessage" %)
252 +(((
253 +root@dragino-1d27d4:~~#  vim /etc/chirpstack-gateway-bridge/chirpstack-gateway-bridge.toml
254 +)))
255 +
256 +[[image:image-20221222113302-1.png]]
257 +
258 +
259 +[[image:image-20221222140203-4.png||height="875" width="806"]]
260 +
261 +[[image:image-20221230094246-1.png||height="768" width="783"]]
262 +
263 +(% class="wikigeneratedid" id="H" %)
264 +After the modification, run the following command: **/etc/init.d/chirpstack-gateway-bridge restart**
265 +
266 +
267 +== 4.4  (Re)start and stop gateway-bridge ==
268 +
269 +
270 +Use the following commands to (re)start and stop the ChirpStack Gateway Bridge Service:
271 +
272 +(% class="box infomessage" %)
273 +(((
274 +**# start**
275 +
276 +/etc/init.d/chirpstack-gateway-bridge start
277 +
278 +**# stop**
279 +
280 +/etc/init.d/chirpstack-gateway-bridge stop
281 +
282 +**# restart**
283 +
284 +/etc/init.d/chirpstack-gateway-bridge restart
285 +)))
286 +
287 +
288 +== 4.5  Successful Connection ==
289 +
290 +
291 +[[image:image-20221222141754-5.png||height="488" width="1150"]]
292 +
293 +
294 +[[image:image-20221222141830-6.png||height="582" width="1153"]]
295 +
296 +
297 += 5.  Downlink =
298 +
299 +== 5.1  Convert HEX to Base64 ==
300 +
301 +
302 +(% 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.**
303 +
304 +**[[Online HEX to Base64 Converter>>https://base64.guru/converter/encode/hex]]:**
305 +
306 +[[image:image-20221010193350-1.png]]
307 +
308 +
309 +
310 +**[[Online Base64 to Hex converter>>https://base64.guru/converter/decode/hex]]**
311 +
312 +[[image:image-20221010193621-2.png]]
313 +
314 +
315 +== 5.2  Chirpstack Downlink Note ==
316 +
317 +
192 192  [[image:image-20220601102543-2.png]]
193 193  
194 -Convert the data to Base64
320 +**Convert the data to Base64**
195 195  
322 +(% style="display:none" %) (%%)
196 196  
197 -[[image:image-20220531173236-10.png]]
198 198  
199 -Check ChripStack downlink DataRate
325 +[[image:image-20220531173236-10.png||height="597" width="1215"]]
200 200  
327 +**Check ChripStack downlink DataRate**
201 201  
329 +
330 +
202 202  [[image:image-20220525101326-11.png]]
203 203  
204 -Make sure the RX2DR is the same in the end node
333 +**Make sure the RX2DR is the same in the end node**
205 205  
206 206  
207 -== 4.2 Loraserver Downlink Note ==
336 +== 5.3  Loraserver Downlink Note ==
208 208  
338 +
209 209  User can use MQTT to send downlink payload to ChirpStack to perform downstream to LoRaWAN End
210 210  
211 211  (((
212 -Below is examples:
342 +**Below is examples:**
213 213  )))
214 214  
215 215  (% class="box" %)
... ... @@ -223,13 +223,14 @@
223 223  [[image:image-20220531173419-11.png]]
224 224  
225 225  (((
226 -MQTT Connect to ChirpStack
356 +**MQTT Connect to ChirpStack**
227 227  
358 +
228 228  
229 229  )))
230 230  
231 231  (((
232 -After connect
363 +**After connect**
233 233  )))
234 234  
235 235  (% class="box" %)
... ... @@ -249,22 +249,14 @@
249 249  
250 250  [[image:image-20220531173519-12.png]]
251 251  
252 -MQTT Connect to ChirpStack
383 +**MQTT Connect to ChirpStack**
253 253  
254 254  
255 -(((
256 -(% 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/]]
257 -)))
386 +**If we want to send downstream hex 030101 to end node, the BASE64 payload is AwEB**
258 258  
259 -[[image:image-20220531173601-13.png]]
260 -
261 -Choose to Use Hex for Encode
262 -
263 -
264 -If we want send downstream hex 030101 to end node, the BASE64 payload is AwEB
265 -
266 266  [[image:image-20220531173658-14.png]]
267 267  
390 +
268 268  (((
269 269  Downlink payload encode javescript code: 可以在网站上运行以下Javsscript代码：
270 270  )))
... ... @@ -282,15 +282,15 @@
282 282   {
283 283   if(sha1[n] >= 'A' && sha1[n] <= 'Z')
284 284   {
285 - ascv = sha1.charCodeAt(n) - 55;
408 + ascv = sha1.charCodeAt( n ) - 55;
286 286   }
287 287   else if(sha1[n] >= 'a' && sha1[n] <= 'z')
288 288   {
289 - ascv = sha1.charCodeAt(n) - 87;
412 + ascv = sha1.charCodeAt( n ) - 87;
290 290   }
291 291   else
292 292   {
293 - ascv = sha1.charCodeAt(n) - 48;
416 + ascv = sha1.charCodeAt( n ) - 48;
294 294   }
295 295  \\ bit_arr = (bit_arr << 4) | ascv;
296 296   bit_num += 4;
... ... @@ -327,11 +327,12 @@
327 327  )))
328 328  
329 329  
330 -== 4.3 Add the decode function in Chirpstack for the payload ==
453 +== 4.3  Add the decode function in Chirpstack for the payload ==
331 331  
455 +
332 332  User enters the payload code according to the steps.
333 333  
334 -[[image:image-20220531173754-15.png]]
458 +[[image:image-20220531173754-15.png||height="474" width="1334"]]
335 335  
336 336  
337 337  [[image:image-20220531173856-16.png]]
... ... @@ -342,8 +342,9 @@
342 342  [[image:image-20220531174046-19.png]]
343 343  
344 344  
345 -= 5. Multiply Uplink in ChirpStack =
469 += 6.  Multiply Uplink in ChirpStack =
346 346  
471 +
347 347  (((
348 348  nbtrans field is the value to determine the re-transmission time for unconfirmed uplink data.
349 349  )))
... ... @@ -350,12 +350,17 @@
350 350  
351 351  (((
352 352  ChirpStack will auto adjust nbtrans according to uplink rssi. [[link to source>>url:https://github.com/brocaar/chirpstack-network-server/blob/master/internal/adr/adr.go]]
478 +
479 +
353 353  )))
354 354  
355 -[[image:image-20220526091912-7.png]]
482 +[[image:image-20220526091912-7.png||height="241" width="1336"]]
356 356  
484 +
357 357  (((
358 358  nbtrans is a field of ADR message, in unconfirm mode, it tells end node how many time it needs to transmit for every frame.
487 +
488 +
359 359  )))
360 360  
361 361  [[image:image-20220525104359-21.png]]
... ... @@ -362,6 +362,8 @@
362 362  
363 363  (((
364 364  Above behaviour will cause the platform shows below two cases of error:
495 +
496 +
365 365  )))
366 366  
367 367  (((
... ... @@ -371,29 +371,35 @@
371 371  [[image:image-20220525104437-22.png]]
372 372  
373 373  
374 -Duplicate transmission in short time
375 375  
376 -[[image:image-20220601102430-1.png]]
507 +**Duplicate transmission in short time**
377 377  
509 +[[image:image-20220601102430-1.png||height="598" width="1319"]]
378 378  
379 -== 5.1 Solution ==
380 380  
512 +== 6.1  Solution ==
513 +
514 +
381 381  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]]
382 382  
517 +
383 383  (((
384 -~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.
519 +(% 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.**
520 +
521 +
385 385  )))
386 386  
387 387  [[image:image-20220525104532-24.png]]
388 388  
389 389  
390 -installation path:
527 +**installation path:**
391 391  
392 392  [[image:image-20220525104554-25.png]]
393 393  
394 394  
532 +
395 395  (((
396 -2. Environment variable settings:.
534 +(% style="color:blue" %)**2.  Environment variable settings:**
397 397  )))
398 398  
399 399  (((
... ... @@ -401,13 +401,13 @@
401 401  )))
402 402  
403 403  (((
404 -2)Set the variable name GOROOT and the variable value C:\Go\ (installation directory)
542 +2) Set the variable name GOROOT and the variable value C:\Go\ (installation directory)
405 405  )))
406 406  
407 407  [[image:image-20220524165433-33.png]]
408 408  
409 409  
410 -3)Modify the system variable Path and add C:\Go\bin\:
548 +3) Modify the system variable Path and add C:\Go\bin\:
411 411  
412 412  [[image:image-20220524165452-34.png]]
413 413  
... ... @@ -417,8 +417,9 @@
417 417  [[image:image-20220524165517-35.png]]
418 418  
419 419  
420 -3. Modify the ADR configuration file according to your own needs, adr.setting.go is an example of the ADR configuration file.
421 421  
559 +(% 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.**
560 +
422 422  The name of the plugin: Example ADR plugin:
423 423  
424 424  [[image:image-20220524165540-36.png]]
... ... @@ -428,8 +428,9 @@
428 428  [[image:image-20220524165557-37.png]]
429 429  
430 430  
431 -4. Compile the ADR configuration file and generate the exe file.
432 432  
571 +(% style="color:blue" %)**4.  Compile the ADR configuration file and generate the exe file.**
572 +
433 433  1) Create a folder named adr-setting
434 434  
435 435  2) Open the adr-setting folder
... ... @@ -453,8 +453,9 @@
453 453  [[image:image-20220524165623-38.png]]
454 454  
455 455  
456 -5. Add the plugin and run the plugin.
457 457  
597 +(% style="color:blue" %)**5.  Add the plugin and run the plugin.**
598 +
458 458  (((
459 459  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:
460 460  )))
... ... @@ -490,14 +490,68 @@
490 490  Finish.
491 491  
492 492  
493 -= 6. Trouble Shooting =
634 += 7.  How to store/get all data traffic for a specific sensor, including raw payload, and uplink/ downlink history. =
494 494  
495 -== 6.1 MIC Mismatch or MIC Failed ==
496 496  
637 +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.
638 +
639 +This example will be shown how to store/get all the data in two ways:
640 +
641 +**//1). Chirpstack ~-~-> Node-red//**
642 +
643 +
644 +[[image:image-20221012184501-1.png]]
645 +
646 +
647 +Use MQTT in Nore-red to subscribe to topics published by the chirpstack-application and then continuously write to a file
648 +
649 +[[image:image-20221012174220-2.png]]
650 +
651 +
652 +[[image:image-20221012184655-3.png||height="395" width="1049"]]
653 +
654 +
655 +**Each message is continuously logged to a specified file**
656 +
657 +[[image:image-20221012174352-3.png]]
658 +
659 +
660 +**//2). MQTT  Sub//**
661 +
662 +If you don't want to store the information via node-red, you can get the output via the subscribe command.
663 +
664 +
665 +**If connecting from the same machine, you can use the following command to receive data:**
666 +
667 +(% class="box infomessage" %)
497 497  (((
669 +mosquitto_sub -h localhost -t "application/#" -v
670 +)))
671 +
672 +
673 +**Different host**
674 +
675 +(% class="box infomessage" %)
676 +(((
677 +mosquitto_sub -h IPADDRESS -p 8883 ~-~-insecure ~-~-cafile ca.pem ~-~-cert cert.pem ~-~-key key.pem -t "application/#" -v
678 +)))
679 +
680 +[[image:image-20221012173639-1.png]]
681 +
682 +
683 += 8.  Trouble Shooting =
684 +
685 +== 8.1  MIC Mismatch or MIC Failed ==
686 +
687 +
688 +(((
498 498  When the device is registered or the device is working normally, the problem of MIC mismatch and MIC failed occurs.
499 499  )))
500 500  
501 501  (((
502 502  Under normal circumstances, users need to change the APPKEY to solve this problem.
694 +
695 +
696 +
697 +
503 503  )))
image-20221010193350-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +42.7 KB
Content
image-20221010193621-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +34.2 KB
Content
image-20221012173639-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoye
Size
... ... @@ -1,0 +1,1 @@
1 +56.2 KB
Content
image-20221012174220-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoye
Size
... ... @@ -1,0 +1,1 @@
1 +14.8 KB
Content
image-20221012174352-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoye
Size
... ... @@ -1,0 +1,1 @@
1 +93.0 KB
Content
image-20221012184501-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoye
Size
... ... @@ -1,0 +1,1 @@
1 +91.3 KB
Content
image-20221012184631-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoye
Size
... ... @@ -1,0 +1,1 @@
1 +32.4 KB
Content
image-20221012184655-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoye
Size
... ... @@ -1,0 +1,1 @@
1 +45.4 KB
Content
image-20221222113302-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +76.3 KB
Content
image-20221222114220-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +64.3 KB
Content
image-20221222134830-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +54.5 KB
Content
image-20221222140203-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +91.4 KB
Content
image-20221222141754-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +179.1 KB
Content
image-20221222141830-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +116.7 KB
Content
image-20221230094246-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +84.9 KB
Content

Applications

Navigation

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