Changes for page Notes for TTN

Last modified by Mengting Qiu on 2024/08/20 17:29

From version 99.13
edited by Xiaoling
on 2022/07/25 08:54
Change comment: There is no comment for this version
To version 242.1
edited by Mengting Qiu
on 2024/08/20 17:29
Change comment: Uploaded new attachment "image-20240820172925-5.png", version {1}

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.ting
Content
... ... @@ -6,10 +6,8 @@
6 6  
7 7  = 1. The Things Network-V3 =
8 8  
9 -
10 10  == 1.1  Introduction ==
11 11  
12 -
13 13  === 1.1.1  What is The Things Network ===
14 14  
15 15  
... ... @@ -20,7 +20,6 @@
20 20  (((
21 21  The Things Network runs The Things Stack Community Edition, which is a crowdsourced, open and decentralized LoRaWAN network. This network is a great way to get started testing devices, applications, and integrations, and get familiar with LoRaWAN.
22 22  
23 -
24 24  
25 25  )))
26 26  
... ... @@ -34,7 +34,6 @@
34 34  (((
35 35  Once you have an account,get started by following steps for adding Gateway,Device and Intergrations.
36 36  
37 -
38 38  
39 39  )))
40 40  
... ... @@ -44,40 +44,60 @@
44 44  LoRaWAN Gateway model: Existing Gateway
45 45  
46 46  
47 -
48 48  = 2.  Gateway Registration for Semtech UDP =
49 49  
50 50  
46 +(% style="color:red" %)**Note: Steps 2 and 3 are different connection methods, the user only needs to choose one of them**
47 +
48 +
51 51  == 2.1  Primary LoRaWAN Server ==
52 52  
53 53  
54 -[[image:image-20220526134633-2.png||height="616" width="1323"]]
52 +[[image:image-20220526134633-2.png||_mstalt="430196" height="540" width="1160"]]
55 55  
56 56  Register Gateway
57 57  
58 58  
57 +[[image:image-20231121092510-1.png||height="617" width="1157"]]
59 59  
60 -[[image:image-20220526134826-4.png]]
61 61  
62 62  Put Gateway ID
63 63  
64 64  
63 +[[image:image-20231121092543-2.png||height="613" width="1159"]]
65 65  
66 -[[image:image-20220526134759-3.png]]
67 67  
68 68  Choose Frequency Band
69 69  
70 70  
71 71  
72 -[[image:image-20220526134919-5.png]]
70 +(% style="color:red" %)**Note:**
73 73  
74 -Show Status
72 +DRAGINO - Frequency Plan list  ~-~-~-~-~-~-~-~-~-~-~-~-~-~--  The Thing Network Frequency Plan List
75 75  
74 +AS923-1 (920-923)  (% style="display:none" %) (%%) ~-~-~-~-~-~-~-~-~-~-~-~-~-~--  Asia 920-923 Mhz
76 76  
76 +AS923-1 (923-925)  ~-~-~-~-~-~-~-~-~-~-~-~-~-~--  Asia 915-928 Mhz (AS923 Group 1)with only default channels
77 77  
78 -== 2.2  Secondary LoRaWAN Server ==
78 +AS923-2 (921.4-922.8)  ~-~-~-~-~-~-~-~-~-~-~-~-~-~--  Asia 920-923 Mhz (AS923 Group 2)with only default channels
79 79  
80 +AS923-3 (916.6-918.2)  ~-~-~-~-~-~-~-~-~-~-~-~-~-~--  Asia 915-921 Mhz (AS923 Group 3)with only default channels
80 80  
82 +AS923-4 (917.3-918.7)  ~-~-~-~-~-~-~-~-~-~-~-~-~-~--  Asia 917-920 Mhz (AS923 Group 4)with only default channels
83 +
84 +
85 +[[image:image-20220726134642-1.png||_mstalt="430287" height="344" width="660"]][[image:image-20220726135827-3.png||_mstalt="432978" height="214" width="394"]][[image:image-20220726135759-2.png||_mstalt="433953" height="218" width="554"]]
86 +
87 +[[image:image-20231121092627-3.png||height="617" width="1174"]]
88 +
89 +
90 +[[image:image-20220526134919-5.png||_mstalt="433602"]]
91 +
92 +Show Status
93 +
94 +
95 +== 2.2  Secondary LoRaWAN Server ==
96 +
81 81  === 2.2.1  Introduction ===
82 82  
83 83  
... ... @@ -88,15 +88,14 @@
88 88  
89 89  
90 90  (((
91 -~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]]
107 +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]]
92 92  )))
93 93  
94 94  (((
95 -2. Firmware version since :[[lgw~~-~~-build-v5.4.1644658774>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LIG16/Firmware/Release/]]
111 +2.  Firmware version since :  [[lgw~~-~~-build-v5.4.1644658774>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LIG16/Firmware/Release/]]
96 96  )))
97 97  
98 98  
99 -
100 100  === 2.2.3  Example ===
101 101  
102 102  
... ... @@ -103,39 +103,39 @@
103 103  The following takes Helium as a Secondary LoRaWAN server as an example
104 104  
105 105  
106 -
107 107  === 2.2.4  Step 1: Download and Install the helium gateway-rs ===
108 108  
109 109  
110 -The users is needing to download and install the helium gateway-rs then click the button of Save&Apply
124 +The users is needing to download and install the helium gateway-rs then click the button of (% style="color:blue" %)**Save&Apply.**
111 111  
112 -[[image:image-20220526135049-6.png]]
113 113  
127 +[[image:image-20220526135049-6.png||_mstalt="432432"]]
128 +
114 114  Download and Install gateway-rs
115 115  
116 116  
117 -
118 118  === 2.2.5  Step 2: Back to Semtech UDP page ===
119 119  
120 120  
121 -Back to the page of Semtech UDP check the secondary server settings and click the button of Save&Apply
135 +Back to the page of Semtech UDP check the secondary server settings and click the button of (% style="color:blue" %)**Save&Apply.**
122 122  
123 -​​​​[[image:image-20220526135125-7.png]]
124 124  
138 +​​​​[[image:image-20220526135125-7.png||_mstalt="431106"]]
139 +
125 125  Configuration of helium
126 126  
127 127  
128 -
129 129  = 3.  Gateway Registration for Basics Station =
130 130  
131 -
132 132  == 3.1  Introduction ==
133 133  
134 134  
135 135  (((
136 136  (((
137 -The LoRa Basics™ Station protocol simplifies management of large scale LoRaWAN networks. LoRa Basics™ Station is the preferred way of connecting Gateways to The Things Stack. [[The LoRa Basics Station doc>>url:https://www.thethingsindustries.com/docs/gateways/lora-basics-station/]]
150 +The LoRa Basics™ Station protocol simplifies the management of large-scale LoRaWAN networks. LoRa Basics™ Station is the preferred way of connecting Gateways to The Things Stack. [[The LoRa Basics Station doc>>url:https://www.thethingsindustries.com/docs/gateways/lora-basics-station/]]
138 138  
152 +(% style="color:red" %)**Note: Steps 2 and 3 are different connection methods, the user only needs to choose one of them**
153 +
139 139  
140 140  )))
141 141  )))
... ... @@ -146,20 +146,18 @@
146 146  
147 147  (((
148 148  (((
149 -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]]
164 +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]]
150 150  )))
151 151  
152 152  (((
153 - 2. Firmware version since :[[lgw~~-~~-build-v5.4.1640315898>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/]]
168 + 2.  Firmware version since :  [[lgw~~-~~-build-v5.4.1640315898>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/]]
154 154  
155 -
156 -
157 157  
158 158  )))
159 159  )))
160 160  
161 161  (((
162 -(% style="color:blue" %)**What do you need to prepare**
175 +(% style="color:blue" %)**What do you need to prepare?**
163 163  )))
164 164  
165 165  (((
... ... @@ -166,73 +166,84 @@
166 166  (((
167 167  A gateway that can access the internet normally
168 168  
169 -
170 170  
171 171  )))
172 172  )))
173 173  
174 -== 3.2  Step 1: Add Gateway ==
186 +== 3.2  Step 1: Register Gateway ==
175 175  
176 176  
177 177  (((
178 178  (((
179 -The example for **EU**
191 +(% style="color:blue" %)**The example for**(%%)** the (% style="color:red" %)EU:(%%)**
180 180  )))
181 181  )))
182 182  
183 183  (((
184 184  (((
185 -User can add your gateway into The Things Network V3 according to the previous step
197 +Click the 'Register Gateway' button will get this page to register the gateway from The Thing Network Console gateway page.
198 +
199 +[[image:image-20230728144218-7.png||_mstalt="433290" height="128" width="836"]]
186 186  )))
187 187  )))
188 188  
189 -(((
190 -(((
191 -Following picture is the successful added.
203 +[[image:image-20230728143449-2.png||_mstalt="433108"]]
192 192  
193 -
194 -)))
195 -)))
205 +Register Gateway
196 196  
197 -[[image:image-20220526135316-8.png]]
198 198  
199 -Add Gateway
208 +== 3.3  Step 2: Create the API key ==
200 200  
201 201  
211 +**API Key can be created manually**  ~-~-->  if users forgot to check the check box or switch to basic station mode from the Semtech UDP mode
202 202  
203 -== 3.3  Step 2: Create the API key ==
204 204  
205 205  
206 -user need to create the CUPS API key and LNS API key.
207 207  
216 +**or generate by TTN by checking the check box when registering the gateway** ~-~-->[[image:image-20230728143505-3.png||_mstalt="431132"]]
208 208  
209 -[[image:image-20220526135349-9.png]]
210 210  
211 -Create CUPS API key
219 +=== **1.) Generated by TTH** ===
212 212  
213 213  
222 +Users need to download these two key files and fill them into the gateway's TTN Basics Station configuration,
214 214  
215 -[[image:image-20220526135428-10.png]]
224 +[[image:image-20230728150521-2.png||height="664" width="1019"]]
216 216  
217 -Create LNS API key
218 218  
227 +(% style="color:red" %)**Note:**(%%) The "**Authorization: Bearer** " field should not be entered in the TTN Basics Station configuration of the gateway
219 219  
220 -(% style="color:red" %)**Note : Please copy the API key.**
229 +[[image:image-20230728151807-3.png||height="423" width="1024"]]
221 221  
222 222  
232 +=== **2.) Manually create API KEY: ** ===
223 223  
224 -== 3.4  Step 3: Update the gateway setting ==
225 225  
235 +==== CUPS API KEY ====
226 226  
237 +[[image:image-20220526135349-9.png||_mstalt="434460"]]
238 +
239 +
240 +
241 +==== LNS API KEY ====
242 +
243 +[[image:image-20220526135428-10.png||_mstalt="453791"]]
244 +
245 +
246 +(% style="color:red" %)**Note: If your API is generated by yourself you have to update the key to the gateway setting.**
247 +
248 +
249 +==== Update the gateway setting ====
250 +
251 +
227 227  In the LoRa Basics Station LNS Authentication Key field, paste the API key you generated in the previous step.
228 228  
229 229  
230 -[[image:image-20220526135528-11.png]]
255 +[[image:image-20220526135528-11.png||_mstalt="454480"]]
231 231  
232 232  paste the API key
233 233  
234 234  
235 -
236 236  == 3.5  Step 4: Access the gateway GUI ==
237 237  
238 238  
... ... @@ -239,12 +239,11 @@
239 239  User need to update the API key and install the Certificate
240 240  
241 241  
242 -[[image:image-20220526135601-12.png]]
266 +[[image:image-20220526135601-12.png||_mstalt="452153"]]
243 243  
244 244  Access the gateway GUI
245 245  
246 246  
247 -
248 248  == 3.6  Step 5: Configure Station ==
249 249  
250 250  
... ... @@ -255,18 +255,17 @@
255 255  
256 256  (% class="box" %)
257 257  (((
258 - CUPS Server URI  ~-~->  Server Adress
281 + CUPS Server URI  ~-~->  Server Address, Example: https:~/~/eu1.cloud.thethings.network:443
259 259   CUPS Authorization Key         ~-~->  Server CUPS API Key
260 260   LNS Authorization Key  ~-~->  Server LNS API Key
261 261   CUPS certificate  ~-~->  Server CA(user can use the button to install the certificate by default)
262 262  )))
263 263  
264 -[[image:image-20220526135654-13.png]]
287 +[[image:image-20220526135654-13.png||_mstalt="455169"]]
265 265  
266 266  Congfigure Station
267 267  
268 268  
269 -
270 270  == 3.7  Start Station ==
271 271  
272 272  
... ... @@ -273,42 +273,39 @@
273 273  (((
274 274  When the user has finished the configuration,Please click Sace&Apply to start station to connect The Things Network.
275 275  
276 -
277 277  
278 278  )))
279 279  
280 -== 3.8  Siccessful Connection ==
301 +== 3.8  Successful Connection ==
281 281  
282 282  
283 283  If user completes the above steps,which will see live date in the TTN.
284 284  
285 285  
286 -[[image:image-20220526135734-14.png]]
307 +[[image:image-20220526135734-14.png||_mstalt="455208"]]
287 287  
288 288  Station live date
289 289  
290 290  
291 -
292 292  == 3.9  Trouble Shooting ==
293 293  
294 294  
295 -User can check the station log in the logread/system log page.
315 +User can check the station log in the** (% style="color:blue" %)LogRead ~-~-> System Log (%%)**page.
296 296  
297 297  
298 -[[image:image-20220526135845-15.png]]
318 +[[image:image-20220526135845-15.png||_mstalt="456560"]]
299 299  
300 300  Station Log
301 301  
302 302  
303 303  
304 -and recode the station log in the system/Recode log page.
324 +and recode the station log in the** (% style="color:blue" %)LogRead  ~-~->  Recode Log(%%)** page.
305 305  
306 -[[image:image-20220526135940-16.png]]
326 +[[image:image-20220526135940-16.png||_mstalt="455559"]]
307 307  
308 308  Recore Log
309 309  
310 310  
311 -
312 312  = 4.  Configure node connection to TTNv3 =
313 313  
314 314  
... ... @@ -326,15 +326,15 @@
326 326  
327 327  (((
328 328  (((
329 -We take LES01 as an example.
348 +(% style="color:#037691" %)**We take LES01 as an example.**
330 330  
331 -
332 332  
333 333  )))
334 334  )))
335 335  
336 -== 4.1 Step1 ==
354 +== 4.1  Step 1 ==
337 337  
356 +
338 338  (((
339 339  (((
340 340  Create a device in TTN with the OTAA keys from LSE01.
... ... @@ -353,40 +353,56 @@
353 353  )))
354 354  )))
355 355  
356 -[[image:image-20220526140015-17.png]]
375 +[[image:image-20230221135445-1.png||_mstalt="428714" height="356" width="777"]]
357 357  
358 -[[image:image-20220526140044-18.png]]
377 +First create an application and fill in the custom information in it
359 359  
379 +[[image:image-20230221135520-2.png||_mstalt="427050" height="52" width="974"]]
360 360  
361 -== 4.2 Step2 ==
381 +[[image:image-20230221135810-3.png||_mstalt="428025" height="400" width="638"]]
362 362  
383 +
384 +Add a node device to the application
385 +
386 +
387 +[[image:image-20220526140044-18.png||_mstalt="453648"]]
388 +
389 +
390 +== 4.2  Step 2 ==
391 +
392 +
363 363  (((
364 364  (((
365 365  There are all our nodes in the repository. Users can choose the corresponding brand, model, firmware version and frequency.The decoder and configuration information of the node are pre-configured.Users do not need to configure them.
396 +
397 +[[image:image-20230221164809-2.png||_mstalt="430937" height="525" width="617"]]
366 366  )))
367 367  )))
368 368  
369 -[[image:image-20220526140132-19.png]]
370 370  
402 +== 4.3  Step 3 ==
371 371  
372 -== 4.3 Step3 ==
373 373  
374 374  Add APP EUI in the application:
375 375  
376 -[[image:image-20220526140205-20.png]]
377 377  
408 +[[image:image-20230221140131-4.png||_mstalt="425984" height="569" width="674"]]
378 378  
379 -== 4.4 Step4 ==
380 380  
381 -Add APP KEY and DEV EUI:
411 +== 4.4  Step 4 ==
382 382  
383 -[[image:image-20220526140251-21.png]]
384 384  
414 +**Add APP KEY and DEV EUI:**
385 385  
386 -= 5. TTN V3 integrated into MQTT server =
387 387  
388 -== 5.1 Introduction ==
417 +[[image:image-20230221140448-6.png||_mstalt="430339" height="535" width="647"]]
389 389  
419 +
420 += 5.  TTN V3 integrated into MQTT server =
421 +
422 +== 5.1  Introduction ==
423 +
424 +
390 390  (((
391 391  (((
392 392  The Application Server exposes an MQTT server to work with streaming events. In order to use the MQTT server you need to create a new API key, which will function as connection password. You can also use an existing API key, as long as it has the necessary rights granted.
... ... @@ -395,8 +395,9 @@
395 395  )))
396 396  )))
397 397  
398 -== 5.2 Create device steps at MQTT ==
433 +== 5.2  Create device steps at MQTT ==
399 399  
435 +
400 400  (((
401 401  (((
402 402  The user creates a new API KEY after creating a device on TTN V3.
... ... @@ -412,16 +412,20 @@
412 412  (((
413 413  (((
414 414  Fill in Broker Address and Broker port.
451 +
452 +
415 415  )))
416 416  )))
417 417  
418 -[[image:image-20220526140347-22.png]]
456 +[[image:image-20220526140347-22.png||_mstalt="453700"]]
419 419  
420 420  Fill in the username and password into MQTT.
421 421  
422 422  
423 -[[image:image-20220526140420-23.png]]
424 424  
462 +[[image:image-20220526140420-23.png||_mstalt="451373"]]
463 +
464 +
425 425  The Application Server publishes uplink traffic on the following topics:
426 426  
427 427  (% class="box" %)
... ... @@ -438,13 +438,18 @@
438 438  )))
439 439  
440 440  (((
481 +
482 +
441 441  (((
442 -**Note**: Remember that the format of these topics for The Things Stack Open Source would contain {application id} instead of {application id}@{tenant id}.
484 +(% style="color:red" %)**Note**: **Remember that the format of these topics for The Things Stack Open Source would contain {application id} instead of {application id}@{tenant id}.**
485 +
486 +
443 443  )))
444 444  )))
445 445  
446 -[[image:image-20220526140452-24.png]]
490 +[[image:image-20220526140452-24.png||_mstalt="453401"]]
447 447  
492 +
448 448  (((
449 449  (((
450 450  While you could subscribe to all of these topics separately, for the simplicity of this tutorial we use # to subscribe to all topics, i.e. to receive all uplink traffic.
... ... @@ -451,7 +451,7 @@
451 451  )))
452 452  )))
453 453  
454 -[[image:image-20220526140708-25.png]]
499 +[[image:image-20220526140708-25.png||_mstalt="455117"]]
455 455  
456 456  (((
457 457  (((
... ... @@ -461,7 +461,11 @@
461 461  
462 462  (((
463 463  (((
464 -**Note**: Remember that the format of this topic for The Things Stack Open Source deployment would be v3/{application id}/devices/{device id}/down/push.
509 +
510 +
511 +(% style="color:red" %)**Note**: **Remember that the format of this topic for The Things Stack Open Source deployment would be v3/{application id}/devices/{device id}/down/push.**
512 +
513 +
465 465  )))
466 466  )))
467 467  
... ... @@ -471,21 +471,23 @@
471 471  )))
472 472  )))
473 473  
474 -[[image:image-20220526140856-26.png]]
523 +[[image:image-20220526140856-26.png||_mstalt="456755"]]
475 475  
476 476  (((
477 -To send an unconfirmed downlink message to the device dev1 in application app1 in tenant tenant1 with the hexadecimal payload BE EF on FPort 15 with normal priority, use the topic v3/app1@tenant1/devices/dev1/down/push with the following contents:
478 -)))
526 +To send an unconfirmed downlink message to the device dev1 in application app1 in tenant tenant1 with the hexadecimal payload BE EF on FPort 15 with normal priority, use the topic v3/app1@tenant1/devices/dev1/down/push with the following contents: **vu8=**, which is the Base64 format for Hex BE EF  . **[[HEX to Base64 online converter tool>>https://base64.guru/converter/encode/hex]]**.
479 479  
480 -(((
481 -**Note**: Use this handy tool to convert hexadecimal to base64.
528 +[[image:image-20240325082631-1.png||height="393" width="815"]]
529 +
530 +
531 +Below is the TTN output for this downlink command.
482 482  )))
483 483  
484 -[[image:image-20220526140936-27.png]]
534 +[[image:image-20220526140936-27.png||_mstalt="456794"]]
485 485  
486 486  
487 -== 5.3 Send Downlink message ==
537 +== 5.3  Send Downlink message ==
488 488  
539 +
489 489  (((
490 490  How to configure downlink in TTN V3?
491 491  )))
... ... @@ -495,30 +495,36 @@
495 495  )))
496 496  
497 497  (((
498 -Downlink command:01 00 00 5A
549 +(% style="color:blue" %)**Downlink command: 01 00 00 5A**
550 +
551 +
499 499  )))
500 500  
501 -[[image:image-20220526141021-28.png]]
554 +[[image:image-20220526141021-28.png||_mstalt="452647"]]
502 502  
503 503  downlink
504 504  
505 505  
559 +
506 506  After sending, you can view it in live data.
507 507  
508 -[[image:image-20220526141052-29.png]]
562 +[[image:image-20220526141052-29.png||_mstalt="454337"]]
509 509  
510 510  downlink
511 511  
512 512  
567 +
513 513  (((
514 514  When downlink is successfully sent, the downlink information can be received on the serial port.
515 515  )))
516 516  
517 517  (((
518 -**Note**: If the downlink byte sent is longer, the number of bytes will be displayed.
573 +(% style="color:red" %)**Note**:** If the downlink byte sent is longer, the number of bytes will be displayed.**
574 +
575 +
519 519  )))
520 520  
521 -[[image:image-20220526141116-30.png]]
578 +[[image:image-20220526141116-30.png||_mstalt="451672"]]
522 522  
523 523  downlink
524 524  
... ... @@ -531,13 +531,13 @@
531 531  
532 532  (((
533 533  (((
534 -If the equipment uses CLASS A. You can set **AT+RPL=2** or send the downlink command: **2102**
591 +If the equipment uses (% style="color:blue" %)**CLASS A**(%%). You can set (% style="color:red" %)**AT+RPL=2** (%%)or send the downlink command: (% style="color:red" %)**2102**
535 535  )))
536 536  )))
537 537  
538 538  (((
539 539  (((
540 -If the equipment uses CLASS C. You can set** AT+RPL=4** or send the downlink command: **2104**
597 +If the equipment uses (% style="color:blue" %)**CLASS C**(%%). You can set** (% style="color:red" %)AT+RPL=4(%%)** or send the downlink command: (% style="color:red" %)**2104**
541 541  )))
542 542  )))
543 543  
... ... @@ -544,62 +544,177 @@
544 544  (((
545 545  (((
546 546  When the device successfully receives the downlink, the server will receive a confirmation packet of 00.
604 +
605 +
547 547  )))
548 548  )))
549 549  
550 -[[image:image-20220526141149-31.png]]
609 +[[image:image-20220526141149-31.png||_mstalt="454038"]]
551 551  
552 552  downlink
553 553  
554 554  
555 -= 6. Request Remote Support =
614 += 6.  Route TTN data to Node-Red =
556 556  
616 +
617 +Users can create an MQTT integration by following the steps described in "[[5.TTN V3 Integrated into MQTT Server>>http://wiki.dragino.com/xwiki/bin/view/Main/Notes%20for%20TTN/#H5.A0TTNV3integratedintoMQTTserver||_mstmutation="1"]]"
618 +
619 +
620 +== 6.1  Edit mqtt-broker node ==
621 +
622 +
623 +Users need to configure the TTN MQTT server address and port, Such as:
624 +
625 +(% class="box infomessage" %)
557 557  (((
627 +**Server :** eu1.cloud.thethings.network
628 +
629 +**Port  :** 1883
630 +)))
631 +
632 +[[image:image-20220829160224-187.jpeg||_mstalt="526292" height="569" width="1128"]]
633 +
634 +
635 +**Enter Username and Password**
636 +
637 +[[image:image-20220829164358-188.png||_mstalt="486174" height="570" width="1130"]]
638 +
639 +
640 +== 6.2  Debug ==
641 +
642 +
643 +Users can check logs by adding debug.
644 +
645 +[[image:image-20220829164652-189.png||_mstalt="485472" height="572" width="1134"]]
646 +
647 +
648 +== 6.3  Example: Use Local Server TTN and Node-Red in LPS8v2 ==
649 +
650 +
651 +LPS8v2 includes a local TTN Server and Node-Red. This example shows how to configure LHT65N to use with the local Node-Red server. This example assumes users already have:
652 +
653 +* LHT65N register on LPS8v2 Built-In TTN server already
654 +* The user is able to see the data on the built-in TTN server device page.
655 +
656 +Below are the steps to plot the sensor data on LPS8v2 Node-Red.
657 +
658 +
659 +=== 6.3.1 Link Node-Red to Local TTN ===
660 +
661 +
662 +Users can download the Node-Red decoder from this link and import it into the Node-Red platform:  **[[dragino-end-node-decoder/LHT65N.json (github.com)>>url:https://github.com/dragino/dragino-end-node-decoder/blob/main/Node-RED/LHT65N.json]]**
663 +
664 +For more information on importing Input Flow, check out this link: **[[Import Input Flow for Dragino Sensors>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/#H3.A0ImportInputFlowforDraginoSensors||style="background-color: rgb(255, 255, 255);"]]**
665 +
666 +
667 +After importing the Input Flow is complete, the user needs to edit the MQTT in the node
668 +
669 +
670 +(% style="color:blue" %)**1. Change the Topic**
671 +
672 +
673 +Topic modifies it to the following format:
674 +
675 +**v3/(% style="color:red" %)Application ID(%%)/devices/(% style="color:red" %)End device ID(%%)/up**
676 +
677 +[[image:image-20221018100743-1.png||_mstalt="427739" height="573" width="1120"]](% style="display:none" %)
678 +
679 +
680 +
681 +(% style="color:blue" %)**2. Enter the MQTT configuration information**
682 +
683 +
684 +[[image:image-20221018100947-2.png||_mstalt="430079" height="560" width="1123"]](% style="display:none" %)
685 +
686 +
687 +
688 +[[image:image-20221018101102-3.png||_mstalt="425256" height="580" width="1121"]]
689 +
690 +(% class="wikigeneratedid" %)
691 +(% style="color:blue" %)**Finally, click "Update" and Deploy**
692 +
693 +
694 +(% class="wikigeneratedid" %)
695 +"Connected" indicates that the Link Node-red to Local TTN is normal.
696 +
697 +(% class="wikigeneratedid" %)
698 +[[image:image-20220914140918-5.png||_mstalt="432523" height="602" width="1121"]]
699 +
700 +
701 +=== 6.3.2 Check result. ===
702 +
703 +
704 +Users can check logs by adding debug.
705 +
706 +[[image:image-20220914140841-4.png||_mstalt="430456" height="600" width="1119"]]
707 +
708 +
709 +In addition,Users can access the lps8v2 gateway's built-in as server of **Node-Red Chart UI **via the URL((% style="background-color:yellow" %)__**//http:~/~/<hostname>:1880/ui or http:~/~/<local-IPV4-address>:1880/ui//**__(%%)) in your browser.
710 +
711 +
712 +[[image:image-20220914142021-7.png||_mstalt="429000" height="439" width="1143"]](% style="display:none" %)
713 +
714 +
715 += 7.  Request Remote Support =
716 +
717 +
718 +(((
558 558  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.
559 559  \\If problem not solve, and you need dragino remote support, please follow to this document: [[TTN Support instruction>>url:https://www.dragino.com/downloads/index.php?dir=&file=TTNv3_Support_Guide.pdf]](% style="color:red" %) **If user has checked below steps and still can't solve the problem, please send us (support @ dragino.com) the screenshots for each step to check. They include:**
560 560  )))
561 561  
562 562  * End node is connected to serial port to show the Join frequency and DR. (If possible)
724 +
563 563  * Gateway (from gateway UI) traffic to show the packet got from end node and receive from Server. (If possible)
726 +
564 564  * Gateway traffic (from server UI) to shows the data exchange between gateway and server. (Normally possible)
728 +
565 565  * End Node traffic (from server UI) to shows end node activity in server. (Normally possible)
730 +
566 566  * 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)
567 567  
568 -**~1. End Device Join Screen shot, we can check:**
733 +(% style="color:blue" %)**1. End Device Join Screen shot, we can check:**
569 569  
570 570  * If the device is sending join request to server?
736 +
571 571  * What frequency the device is sending?
572 572  
573 -[[image:image-20220526141308-33.png]]
739 +[[image:image-20220526141308-33.png||_mstalt="453778"]]
574 574  
575 575  Console Output from End device to see the transmit frequency
576 576  
577 -User can run **AT+CFG **command to print configuration information.
578 578  
579 -* Is the device in OTAA mode or ABP mode? **AT+NJM=1** (OTAA mode), **AT+NJM=0** (ABP mode)
744 +User can run (% style="color:blue" %)**AT+CFG **(%%)command to print configuration information.
580 580  
581 -[[image:image-20220526141612-36.png]]
746 +* Is the device in OTAA mode or ABP mode? (% style="color:red" %)**AT+NJM=1** (%%)(OTAA mode), (% style="color:red" %)**AT+NJM=0**(%%) (ABP mode)
582 582  
748 +[[image:image-20220526141612-36.png||_mstalt="454142"]]
583 583  
750 +
584 584  Console Output from End device to see the transmit frequency
585 585  
586 586  
587 -**2. Gateway packet traffic in gateway web or ssh. we can check:**
588 588  
755 +(% style="color:blue" %)**2. Gateway packet traffic in gateway web or ssh. we can check:**
756 +
589 589  * (((
590 590  If the gateway receive the Join request packet from sensor? (If this fail, check if the gateway and sensor works on the match frequency)
591 591  )))
592 592  * (((
593 593  If the gateway gets the Join Accept message from server and transmit it via LoRa?
762 +
763 +
764 +
594 594  )))
595 595  
596 -[[image:image-20220526141739-37.png]]
767 +[[image:image-20220526141739-37.png||_mstalt="457847"]]
597 597  
598 598  Console Output from Gateway to see packets between end node and server.
599 599  
600 600  
601 -**3. Gateway Traffic Page in LoRaWAN Server**
602 602  
773 +(% style="color:blue" %)**3. Gateway Traffic Page in LoRaWAN Server**
774 +
603 603  * (((
604 604  If the Join Request packet arrive the gateway traffic in server? If not, check the internet connection and gateway LoRaWAN server settings.
605 605  )))
... ... @@ -608,26 +608,32 @@
608 608  )))
609 609  * (((
610 610  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.
783 +
784 +
785 +
611 611  )))
612 612  
613 -[[image:image-20220526141823-38.png||height="501" width="1144"]]
788 +[[image:image-20220526141823-38.png||_mstalt="456183" height="501" width="1144"]]
614 614  
615 615  The Traffic for the End node in the server, use TTNv3 as example
616 616  
617 617  
618 -[[image:image-20220526141917-39.png]]
619 619  
794 +[[image:image-20220526141917-39.png||_mstalt="457899"]]
795 +
620 620  The Traffic for the End node in the server, use TTNv3 as example
621 621  
622 622  
623 -**4. Data Page in LoRaWAN server**
624 624  
800 +(% style="color:blue" %)**4. Data Page in LoRaWAN server**
801 +
625 625  (((
626 626  (((
627 627  (((
628 628  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.
629 629  
630 -[[image:image-20220526141956-40.png]]
807 +
808 +[[image:image-20220526141956-40.png||_mstalt="455832"]]
631 631  )))
632 632  )))
633 633  )))
... ... @@ -635,6 +635,182 @@
635 635  The data for the end device set in server
636 636  
637 637  
638 -[[image:image-20220526142033-41.png]]
639 639  
817 +[[image:image-20220526142033-41.png||_mstalt="452036"]]
818 +
640 640  Check if OTAA Keys match the keys in device
820 +
821 +
822 += 8.  FAQ =
823 +
824 +== 8.1 How to import devices keys to TTN. ==
825 +
826 +
827 +**For TTS in LPS8v2**
828 +
829 +Open your application and click the button **Import end devices**
830 +
831 +[[image:image-20230423154012-1.png||_mstalt="426738" height="472" width="755"]]
832 +
833 +
834 +Select the **File format** and upload the file (e.g. or ).devices/jsondevices.csv
835 +
836 +You can specify **Fallback values** for Frequency plan and LoRaWAN and Regional Parameters version, in case the import file does not specify these settings for the device.
837 +
838 +You can also expand the **Advanced claiming and component settings** to set targeted components, and set the claim authentication code to be generated.
839 +
840 +Start the import by clicking the **Import end devices** button.
841 +
842 +[[image:image-20230423154040-2.png||_mstalt="427401" height="470" width="749"]]
843 +
844 +
845 +Wait for the end devices to be successfully imported. In case any device fails, you will see a relevant error message in the console.
846 +
847 +[[image:image-20230423154105-3.png||_mstalt="428467" height="478" width="763"]]
848 +
849 +
850 +If the import was successful, your devices are added to the list of end devices in your application.
851 +
852 +[[image:image-20230423154125-4.png||_mstalt="429481" height="480" width="766"]]
853 +
854 +Devices are now registered on The Things Stack.
855 +
856 +
857 +=== **JSON File Reference** ===
858 +
859 +
860 +The Things Stack allows you to import end devices from V2, ChirpStack and other LoRaWAN networks using a JSON file describing those devices.
861 +
862 +Using JSON file with device descriptions, you can migrate end devices with or without their existing sessions.
863 +
864 +Here is an example of an OTAA device description in the file:devices.json
865 +
866 +{{{{
867 + "ids": {
868 + "device_id": "my-device",
869 + "dev_eui": "0102030405060708",
870 + "join_eui": "0102030405060708"
871 + },
872 + "name": "My Device",
873 + "description": "Living room temperature sensor",
874 + "lorawan_version": "MAC_V1_0_2",
875 + "lorawan_phy_version": "PHY_V1_0_2_REV_B",
876 + "frequency_plan_id": "EU_863_870_TTN",
877 + "supports_join": true,
878 + "root_keys": {
879 + "app_key": {
880 + "key": "01020304050607080102030405060708"
881 + }
882 + }
883 +}
884 +}}}
885 +
886 +Multiple end devices can also be contained in a single file like so:devices.json
887 +
888 +{{{{
889 + /* device 1 */
890 +}
891 +{
892 + /* device 2 */
893 +}
894 +}}}
895 +
896 +The format above is considered by the Console and CLI as a JSON stream, processing one object at a time. For more details in how to use the file
897 +
898 +
899 +=== **CSV File Reference** ===
900 +
901 +
902 +The Things Stack has support for importing end devices from CSV (comma-separated values) files. This is useful when batches of end devices are managed in Microsoft Excel or any other spreadsheet or database that can export to CSV file.
903 +
904 +The CSV import in The Things Stack uses the following settings:
905 +
906 +* Semicolon () as field delimiter. This makes working with Microsoft Excel and other spreadsheets convenient;
907 +
908 +* Header row is required
909 +
910 +* On each row, the same number of fields as on the header line
911 +
912 +* Use quotes to use in a field value;
913 +
914 +* Use double quotes to escape quotes
915 +
916 +* Unknown header columns are permitted and ignored
917 +
918 +* Name and id cannot have capital letters and special characters
919 +
920 +* Example column lorawan_phy_version is not needed
921 +
922 +(% style="display:none" %)
923 +
924 +
925 +
926 +=== **Example** ===
927 +
928 +
929 +Minimal example:
930 +
931 +{{{dev_eui;join_eui;frequency_plan_id;lorawan_version;lorawan_phy_version;app_key
932 +1111111111111111;1111111111111111;EU_863_870_TTN;MAC_V1_0_4;RP002_V1_0_3;11111111111111111111111111111111
933 +2222222222222222;2222222222222222;EU_863_870_TTN;MAC_V1_0_4;RP002_V1_0_3;22222222222222222222222222222222
934 +3333333333333333;3333333333333333;EU_863_870_TTN;MAC_V1_0_4;RP002_V1_0_3;33333333333333333333333333333333
935 +}}}
936 +
937 +All columns for a LoRaWAN 1.0.4 device:
938 +
939 +{{{id;dev_eui;join_eui;name;frequency_plan_id;lorawan_version;lorawan_phy_version;brand_id;model_id;hardware_version;firmware_version;band_id;app_key
940 +test-one;1111111111111111;1111111111111111;Device 1;EU_863_870_TTN;MAC_V1_0_4;RP002_V1_0_3;the-things-industries;generic-node-sensor-edition;1.0.4;1.0;EU_863_870;11111111111111111111111111111111
941 +test-two;2222222222222222;2222222222222222;Device 2;EU_863_870_TTN;MAC_V1_0_4;RP002_V1_0_3;the-things-industries;generic-node-sensor-edition;1.0.4;1.0;EU_863_870;22222222222222222222222222222222
942 +test-three;3333333333333333;3333333333333333;Device 3;EU_863_870_TTN;MAC_V1_0_4;RP002_V1_0_3;the-things-industries;generic-node-sensor-edition;1.0.4;1.0;EU_863_870;33333333333333333333333333333333
943 +}}}
944 +
945 +
946 +(% style="display:none" %) (%%)
947 +
948 +=== **Excel Template** ===
949 +
950 +
951 +[[Download the Excel template>>url:https://www.thethingsindustries.com/docs/getting-started/migrating/tts-end-devices-csv-template.xlsx]]. You can remove all columns that are not required (see above).
952 +
953 +
954 +== 8.2 How to download and analyze End Device's log?(% style="display:none" %) (%%) ==
955 +
956 +
957 +~1. Get information about a single node
958 +
959 +Download this file in the node's live data interface
960 +
961 +[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20of%20Dragino%20LoRaWAN%20Packet%20Analyze%20Tool/WebHome/image-20230928163751-2.png?width=1278&height=506&rev=1.1||alt="image-20230928163751-2.png" height="506" width="1278"]]
962 +
963 +
964 +2. Get information about the entire Application
965 +
966 +Click the "See all activity" button on the main interface of the application
967 +
968 +[[image:image-20231019113039-1.png||height="678" width="1312"]]
969 +
970 +
971 +Download this file in application  live data interface
972 +
973 +[[image:image-20231019113212-4.png||height="567" width="1277"]]
974 +
975 +
976 +After the data collection is completed, you can send this file directly to our technical support personnel for analysis.
977 +
978 +
979 +You can also use the packet analysis tool developed by our company to check it yourself. Please refer to the following [[link>>http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20of%20Dragino%20LoRaWAN%20Packet%20Analyze%20Tool/#H3.ThethingsNetwork]] to use this tool.
980 +
981 +[[image:image-20240117170517-1.png]]
982 +
983 +
984 +
985 += 9. Trouble Shooting. =
986 +
987 +== 9.1 How to solve the problem of MIC Mismatch? ==
988 +
989 +
990 +Please refer to the link below:
991 +
992 +[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/LoRaWAN%20Communication%20Debug/#H9.WhydoIseea22MICMismatch22errormessagefromtheserver3F>>url:http://wiki.dragino.com/xwiki/bin/view/Main/LoRaWAN%20Communication%20Debug/#H9.WhydoIseea22MICMismatch22errormessagefromtheserver3F]]
993 +
994 +
image-20220726134642-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoye
Size
... ... @@ -1,0 +1,1 @@
1 +50.0 KB
Content
image-20220726135759-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoye
Size
... ... @@ -1,0 +1,1 @@
1 +14.5 KB
Content
image-20220726135827-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoye
Size
... ... @@ -1,0 +1,1 @@
1 +14.1 KB
Content
image-20220829153628-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +173.3 KB
Content
image-20220829153716-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +173.6 KB
Content
image-20220829155610-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +79.4 KB
Content
image-20220829160114-4.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160115-5.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160115-6.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160116-7.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160116-8.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160116-9.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160125-41.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160128-57.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160130-65.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160132-77.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160132-78.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160133-81.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160134-86.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160134-90.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160145-146.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160145-147.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160145-148.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160145-149.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160145-150.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160145-151.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160145-152.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160145-153.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160146-154.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160146-155.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160146-156.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160146-157.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160146-158.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160146-159.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160146-160.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160146-161.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160146-162.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160146-163.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160146-164.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160146-165.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160146-166.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160146-167.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160147-168.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160147-169.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160147-170.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160147-171.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160147-172.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160147-173.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160147-174.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160147-175.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160147-176.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160147-177.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160147-178.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160147-179.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160147-180.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160147-181.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160147-182.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160148-183.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160148-184.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160148-185.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160148-186.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829160224-187.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +161.0 KB
Content
image-20220829164358-188.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +176.0 KB
Content
image-20220829164652-189.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +148.8 KB
Content
image-20220913134247-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +23.6 KB
Content
image-20220913153442-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +37.2 KB
Content
image-20220914101543-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +148.7 KB
Content
image-20220914103142-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +174.7 KB
Content
image-20220914103303-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +159.0 KB
Content
image-20220914140841-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +283.8 KB
Content
image-20220914140918-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +284.6 KB
Content
image-20220914141502-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +87.7 KB
Content
image-20220914142021-7.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +81.3 KB
Content
image-20221018100743-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +98.5 KB
Content
image-20221018100947-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +130.6 KB
Content
image-20221018101102-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +90.5 KB
Content
image-20230221135445-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +37.6 KB
Content
image-20230221135520-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +4.4 KB
Content
image-20230221135810-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +33.2 KB
Content
image-20230221140131-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +58.0 KB
Content
image-20230221140327-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +42.7 KB
Content
image-20230221140448-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +42.9 KB
Content
image-20230221164647-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +59.6 KB
Content
image-20230221164809-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +59.9 KB
Content
image-20230423154012-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +140.9 KB
Content
image-20230423154040-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +141.0 KB
Content
image-20230423154105-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +188.5 KB
Content
image-20230423154125-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +102.1 KB
Content
image-20230728143343-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoye
Size
... ... @@ -1,0 +1,1 @@
1 +43.2 KB
Content
image-20230728143449-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoye
Size
... ... @@ -1,0 +1,1 @@
1 +43.2 KB
Content
image-20230728143505-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoye
Size
... ... @@ -1,0 +1,1 @@
1 +16.7 KB
Content
image-20230728144218-7.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoye
Size
... ... @@ -1,0 +1,1 @@
1 +12.7 KB
Content
image-20230728145557-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +53.6 KB
Content
image-20230728150521-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +73.9 KB
Content
image-20230728151807-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +149.0 KB
Content
image-20231019113039-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +71.3 KB
Content
image-20231019113131-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +207.7 KB
Content
image-20231019113137-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +207.7 KB
Content
image-20231019113212-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +168.8 KB
Content
image-20231121092510-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +126.5 KB
Content
image-20231121092543-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +121.0 KB
Content
image-20231121092627-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +125.3 KB
Content
image-20240117170517-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +63.1 KB
Content
image-20240325082631-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +55.9 KB
Content
image-20240325082714-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +55.9 KB
Content
image-20240820171935-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +92.6 KB
Content
image-20240820172327-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +79.9 KB
Content
image-20240820172513-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +45.8 KB
Content
image-20240820172909-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +71.5 KB
Content
image-20240820172925-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +180.7 KB
Content