Skip to Content

Changes for page Notes for TTN

Last modified by Mengting Qiu on 2024/08/20 17:29
From version 79.1
edited by Xiaoling
on 2022/05/26 14:02
Change comment: Uploaded new attachment "image-20220526140205-20.png", version {1}
To version 243.1
edited by Mengting Qiu
on 2024/08/20 17:29
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.ting
Content
... ... @@ -1,14 +1,16 @@
1 -**~ Contents：**
1 +**~ Table of Contents：**
2 2  
3 3  {{toc/}}
4 4  
5 5  
6 +
6 6  = 1. The Things Network-V3 =
7 7  
8 -== 1.1 Introduction ==
9 +== 1.1  Introduction ==
9 9  
10 -=== 1.1.1 What is The Things Network ===
11 +=== 1.1.1  What is The Things Network ===
11 11  
13 +
12 12  (((
13 13  The Things Network is a global collaborative Internet of Things ecosystem that creates networks, devices and solutions using LoRaWAN.
14 14  )))
... ... @@ -19,8 +19,9 @@
19 19  
20 20  )))
21 21  
22 -=== 1.1.2 Login or crate an account ===
24 +=== 1.1.2  Login or crate an account ===
23 23  
26 +
24 24  (((
25 25  [[Login or create an account>>url:https://console.cloud.thethings.network/]] to get started with The Things Network and start using The Things Stack Console.
26 26  )))
... ... @@ -31,102 +31,145 @@
31 31  
32 32  )))
33 33  
34 -=== 1.1.3 List the support products and Requirements ===
37 +=== 1.1.3  List the support products and Requirements ===
35 35  
39 +
36 36  LoRaWAN Gateway model: Existing Gateway
37 37  
38 38  
39 -= 2. Gateway Registration for Semtech UDP =
43 += 2.  Gateway Registration for Semtech UDP =
40 40  
41 -== 2.1 Primary LoRaWAN Server ==
42 42  
43 -[[image:image-20220526134633-2.png||height="616" width="1323"]]
46 +(% style="color:red" %)**Note: Steps 2 and 3 are different connection methods, the user only needs to choose one of them**
44 44  
48 +
49 +== 2.1  Primary LoRaWAN Server ==
50 +
51 +
52 +[[image:image-20220526134633-2.png||_mstalt="430196" height="540" width="1160"]]
53 +
45 45  Register Gateway
46 46  
47 47  
48 -[[image:image-20220526134826-4.png]]
57 +[[image:image-20231121092510-1.png||height="617" width="1157"]]
49 49  
59 +
50 50  Put Gateway ID
51 51  
52 52  
53 -[[image:image-20220526134759-3.png]]
63 +[[image:image-20231121092543-2.png||height="613" width="1159"]]
54 54  
65 +
55 55  Choose Frequency Band
56 56  
57 57  
58 -[[image:image-20220526134919-5.png]]
59 59  
70 +(% style="color:red" %)**Note:**
71 +
72 +DRAGINO - Frequency Plan list  ~-~-~-~-~-~-~-~-~-~-~-~-~-~--  The Thing Network Frequency Plan List
73 +
74 +AS923-1 (920-923)  (% style="display:none" %) (%%) ~-~-~-~-~-~-~-~-~-~-~-~-~-~--  Asia 920-923 Mhz
75 +
76 +AS923-1 (923-925)  ~-~-~-~-~-~-~-~-~-~-~-~-~-~--  Asia 915-928 Mhz (AS923 Group 1)with only default channels
77 +
78 +AS923-2 (921.4-922.8)  ~-~-~-~-~-~-~-~-~-~-~-~-~-~--  Asia 920-923 Mhz (AS923 Group 2)with only default channels
79 +
80 +AS923-3 (916.6-918.2)  ~-~-~-~-~-~-~-~-~-~-~-~-~-~--  Asia 915-921 Mhz (AS923 Group 3)with only default channels
81 +
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 +
60 60  Show Status
61 61  
62 62  
63 -== 2.2 Secondary LoRaWAN Server ==
95 +== 2.2  Secondary LoRaWAN Server ==
64 64  
65 -=== 2.2.1 Introduction ===
97 +=== 2.2.1  Introduction ===
66 66  
99 +
67 67  The Dragino gateway has supports the Secondary server settings.
68 68  
69 69  
70 -=== 2.2.2 Below list the support products and Requirements: ===
103 +=== 2.2.2  Below list the support products and Requirements: ===
71 71  
105 +
72 72  (((
73 -~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]]
74 74  )))
75 75  
76 76  (((
77 -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/]]
78 78  )))
79 79  
80 80  
81 -=== 2.2.3 Example ===
115 +=== 2.2.3  Example ===
82 82  
117 +
83 83  The following takes Helium as a Secondary LoRaWAN server as an example
84 84  
85 85  
86 -=== 2.2.4 Step 1: Download and Install the helium gateway-rs ===
121 +=== 2.2.4  Step 1: Download and Install the helium gateway-rs ===
87 87  
88 -The users is needing to download and install the helium gateway-rs then click the button of Save&Apply
89 89  
90 -[[image:image-20220526135049-6.png]]
124 +The users is needing to download and install the helium gateway-rs then click the button of (% style="color:blue" %)**Save&Apply.**
91 91  
126 +
127 +[[image:image-20220526135049-6.png||_mstalt="432432"]]
128 +
92 92  Download and Install gateway-rs
93 93  
94 94  
95 -=== 2.2.5 Step 2: Back to Semtech UDP page ===
132 +=== 2.2.5  Step 2: Back to Semtech UDP page ===
96 96  
97 -Back to the page of Semtech UDP check the secondary server settings and click the button of Save&Apply
98 98  
99 -​​​​[[image:image-20220526135125-7.png]]
135 +Back to the page of Semtech UDP check the secondary server settings and click the button of (% style="color:blue" %)**Save&Apply.**
100 100  
137 +
138 +​​​​[[image:image-20220526135125-7.png||_mstalt="431106"]]
139 +
101 101  Configuration of helium
102 102  
103 103  
104 -= 3. Gateway Registration for Basics Station =
143 += 3.  Gateway Registration for Basics Station =
105 105  
106 -== 3.1 Introduction ==
145 +== 3.1  Introduction ==
107 107  
147 +
108 108  (((
109 109  (((
110 -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/]]
151 +
152 +(% style="color:red" %)**Note: Steps 2 and 3 are different connection methods, the user only needs to choose one of them**
153 +
154 +
111 111  )))
112 112  )))
113 113  
114 114  (((
115 -**Below list the support products and Requirements:**
159 +(% style="color:blue" %)**Below list the support products and Requirements:**
116 116  )))
117 117  
118 118  (((
119 119  (((
120 - ~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]]
121 121  )))
122 122  
123 123  (((
124 - 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/]]
169 +
170 +
125 125  )))
126 126  )))
127 127  
128 128  (((
129 -**What do you need to prepare**
175 +(% style="color:blue" %)**What do you need to prepare?**
130 130  )))
131 131  
132 132  (((
... ... @@ -137,86 +137,115 @@
137 137  )))
138 138  )))
139 139  
140 -== 3.2 Step 1. Add Gateway ==
186 +== 3.2  Step 1: Register Gateway ==
141 141  
142 -(((
143 -(((
144 -The example for **EU**
145 -)))
146 -)))
147 147  
148 148  (((
149 149  (((
150 -User can add your gateway into The Things Network V3 according to the previous step
191 +(% style="color:blue" %)**The example for**(%%)** the (% style="color:red" %)EU:(%%)**
151 151  )))
152 152  )))
153 153  
154 154  (((
155 155  (((
156 -Following picture is the successful added.
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"]]
157 157  )))
158 158  )))
159 159  
160 -[[image:image-20220526135316-8.png]]
203 +[[image:image-20230728143449-2.png||_mstalt="433108"]]
161 161  
162 -Add Gateway
205 +Register Gateway
163 163  
164 164  
165 -== 3.3 Step 2. Create the API key ==
208 +== 3.3  Step 2: Create the API key ==
166 166  
167 -user need to create the CUPS API key and LNS API key.
168 168  
169 -[[image:image-20220526135349-9.png]]
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
170 170  
171 -Create CUPS API key
172 172  
173 173  
174 -[[image:image-20220526135428-10.png]]
175 175  
176 -Create LNS API key
216 +**or generate by TTN by checking the check box when registering the gateway** ~-~-->[[image:image-20230728143505-3.png||_mstalt="431132"]]
177 177  
178 -(% style="color:red" %)**Note : Please copy the API key.**
179 179  
219 +=== **1.) Generated by TTH** ===
180 180  
181 -== 3.4 Step 3. Update the gateway setting ==
182 182  
222 +Users need to download these two key files and fill them into the gateway's TTN Basics Station configuration,
223 +
224 +[[image:image-20230728150521-2.png||height="664" width="1019"]]
225 +
226 +
227 +(% style="color:red" %)**Note:**(%%) The "**Authorization: Bearer** " field should not be entered in the TTN Basics Station configuration of the gateway
228 +
229 +[[image:image-20230728151807-3.png||height="423" width="1024"]]
230 +
231 +
232 +=== **2.) Manually create API KEY: ** ===
233 +
234 +
235 +==== CUPS API KEY ====
236 +
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 +
183 183  In the LoRa Basics Station LNS Authentication Key field, paste the API key you generated in the previous step.
184 184  
185 -[[image:image-20220526135528-11.png]]
186 186  
255 +[[image:image-20220526135528-11.png||_mstalt="454480"]]
256 +
187 187  paste the API key
188 188  
189 189  
190 -== 3.5 Step 4. Access the gateway GUI ==
260 +== 3.5  Step 4: Access the gateway GUI ==
191 191  
262 +
192 192  User need to update the API key and install the Certificate
193 193  
194 -[[image:image-20220526135601-12.png]]
195 195  
266 +[[image:image-20220526135601-12.png||_mstalt="452153"]]
267 +
196 196  Access the gateway GUI
197 197  
198 198  
199 -== 3.6 Step 5. Configure Station ==
271 +== 3.6  Step 5: Configure Station ==
200 200  
273 +
201 201  User need to input Server URI, Server CUPS Key and LNS Key, as well as install CUPS certificate.
202 202  
203 -**just to clarify.**
204 204  
277 +(% style="color:blue" %)**just to clarify:**
278 +
205 205  (% class="box" %)
206 206  (((
207 - CUPS Server URI  ~-~-> Server Adress
208 - CUPS Authorization Key         ~-~-> Server CUPS API Key
209 - LNS Authorization Key  ~-~-> Server LNS API Key
210 - CUPS certificate  ~-~-> Server CA(user can use the button to install the certificate by default)
281 + CUPS Server URI  ~-~->  Server Address, Example: https:~/~/eu1.cloud.thethings.network:443
282 + CUPS Authorization Key         ~-~->  Server CUPS API Key
283 + LNS Authorization Key  ~-~->  Server LNS API Key
284 + CUPS certificate  ~-~->  Server CA(user can use the button to install the certificate by default)
211 211  )))
212 212  
213 -[[image:image-20220526135654-13.png]]
287 +[[image:image-20220526135654-13.png||_mstalt="455169"]]
214 214  
215 215  Congfigure Station
216 216  
217 217  
218 -== 3.7 Start Station ==
292 +== 3.7  Start Station ==
219 219  
294 +
220 220  (((
221 221  When the user has finished the configuration,Please click Sace&Apply to start station to connect The Things Network.
222 222  
... ... @@ -223,33 +223,39 @@
223 223  
224 224  )))
225 225  
226 -== 3.8 Siccessful Connection ==
301 +== 3.8  Successful Connection ==
227 227  
303 +
228 228  If user completes the above steps,which will see live date in the TTN.
229 229  
230 -[[image:image-20220526135734-14.png]]
231 231  
307 +[[image:image-20220526135734-14.png||_mstalt="455208"]]
308 +
232 232  Station live date
233 233  
234 234  
235 -== 3.9 Trouble Shooting ==
312 +== 3.9  Trouble Shooting ==
236 236  
237 -User can check the station log in the logread/system log page.
238 238  
239 -[[image:image-20220526135845-15.png]]
315 +User can check the station log in the** (% style="color:blue" %)LogRead ~-~-> System Log (%%)**page.
240 240  
317 +
318 +[[image:image-20220526135845-15.png||_mstalt="456560"]]
319 +
241 241  Station Log
242 242  
243 243  
244 -and recode the station log in the system/Recode log page.
245 245  
246 -[[image:image-20220526135940-16.png]]
324 +and recode the station log in the** (% style="color:blue" %)LogRead  ~-~->  Recode Log(%%)** page.
247 247  
326 +[[image:image-20220526135940-16.png||_mstalt="455559"]]
327 +
248 248  Recore Log
249 249  
250 250  
251 -= 4. Configure node connection to TTNv3 =
331 += 4.  Configure node connection to TTNv3 =
252 252  
333 +
253 253  (((
254 254  (((
255 255  Following is an example for how to join the TTN v3 LoRaWAN Network.
... ... @@ -264,14 +264,15 @@
264 264  
265 265  (((
266 266  (((
267 -We take LES01 as an example.
348 +(% style="color:#037691" %)**We take LES01 as an example.**
268 268  
269 269  
270 270  )))
271 271  )))
272 272  
273 -== 4.1 Step1 ==
354 +== 4.1  Step 1 ==
274 274  
356 +
275 275  (((
276 276  (((
277 277  Create a device in TTN with the OTAA keys from LSE01.
... ... @@ -290,44 +290,67 @@
290 290  )))
291 291  )))
292 292  
293 -[[image:image-20220526140015-17.png]]
375 +[[image:image-20230221135445-1.png||_mstalt="428714" height="356" width="777"]]
294 294  
295 -[[image:image-20220526140044-18.png]]
377 +First create an application and fill in the custom information in it
296 296  
297 -== 4.2 Step2 ==
379 +[[image:image-20230221135520-2.png||_mstalt="427050" height="52" width="974"]]
298 298  
381 +[[image:image-20230221135810-3.png||_mstalt="428025" height="400" width="638"]]
382 +
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 +
299 299  (((
300 300  (((
301 301  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"]]
302 302  )))
303 303  )))
304 304  
305 -[[image:image-20220525090920-18.png]]
306 306  
307 -== 4.3 Step3 ==
402 +== 4.3  Step 3 ==
308 308  
404 +
309 309  Add APP EUI in the application:
310 310  
311 -[[image:image-20220525091022-19.png]]
312 312  
313 -== 4.4 Step4 ==
408 +[[image:image-20230221140131-4.png||_mstalt="425984" height="569" width="674"]]
314 314  
315 -Add APP KEY and DEV EUI:
316 316  
317 -[[image:image-20220525091128-20.png]]
411 +== 4.4  Step 4 ==
318 318  
319 -= 5. TTN V3 integrated into MQTT server =
320 320  
321 -== 5.1 Introduction ==
414 +**Add APP KEY and DEV EUI:**
322 322  
416 +
417 +[[image:image-20230221140448-6.png||_mstalt="430339" height="535" width="647"]]
418 +
419 +
420 += 5.  TTN V3 integrated into MQTT server =
421 +
422 +== 5.1  Introduction ==
423 +
424 +
323 323  (((
324 324  (((
325 325  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.
428 +
429 +
326 326  )))
327 327  )))
328 328  
329 -== 5.2 Create device steps at MQTT ==
433 +== 5.2  Create device steps at MQTT ==
330 330  
435 +
331 331  (((
332 332  (((
333 333  The user creates a new API KEY after creating a device on TTN V3.
... ... @@ -343,16 +343,20 @@
343 343  (((
344 344  (((
345 345  Fill in Broker Address and Broker port.
451 +
452 +
346 346  )))
347 347  )))
348 348  
349 -[[image:image-20220525091251-22.png]]
456 +[[image:image-20220526140347-22.png||_mstalt="453700"]]
350 350  
351 351  Fill in the username and password into MQTT.
352 352  
353 353  
354 -[[image:image-20220525091333-23.png]]
355 355  
462 +[[image:image-20220526140420-23.png||_mstalt="451373"]]
463 +
464 +
356 356  The Application Server publishes uplink traffic on the following topics:
357 357  
358 358  (% class="box" %)
... ... @@ -369,13 +369,18 @@
369 369  )))
370 370  
371 371  (((
481 +
482 +
372 372  (((
373 -**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 +
374 374  )))
375 375  )))
376 376  
377 -[[image:image-20220525091430-24.png]]
490 +[[image:image-20220526140452-24.png||_mstalt="453401"]]
378 378  
492 +
379 379  (((
380 380  (((
381 381  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.
... ... @@ -382,7 +382,7 @@
382 382  )))
383 383  )))
384 384  
385 -[[image:image-20220525091458-25.png]]
499 +[[image:image-20220526140708-25.png||_mstalt="455117"]]
386 386  
387 387  (((
388 388  (((
... ... @@ -392,7 +392,11 @@
392 392  
393 393  (((
394 394  (((
395 -**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 +
396 396  )))
397 397  )))
398 398  
... ... @@ -402,20 +402,23 @@
402 402  )))
403 403  )))
404 404  
405 -[[image:image-20220525091618-27.png]]
523 +[[image:image-20220526140856-26.png||_mstalt="456755"]]
406 406  
407 407  (((
408 -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:
409 -)))
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]]**.
410 410  
411 -(((
412 -**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.
413 413  )))
414 414  
415 -[[image:image-20220525091702-28.png]]
534 +[[image:image-20220526140936-27.png||_mstalt="456794"]]
416 416  
417 -== 5.3 Send Downlink message ==
418 418  
537 +== 5.3  Send Downlink message ==
538 +
539 +
419 419  (((
420 420  How to configure downlink in TTN V3?
421 421  )))
... ... @@ -425,31 +425,40 @@
425 425  )))
426 426  
427 427  (((
428 -Downlink command:01 00 00 5A
549 +(% style="color:blue" %)**Downlink command: 01 00 00 5A**
550 +
551 +
429 429  )))
430 430  
431 -[[image:image-20220525091752-29.png]]
554 +[[image:image-20220526141021-28.png||_mstalt="452647"]]
432 432  
433 433  downlink
434 434  
558 +
559 +
435 435  After sending, you can view it in live data.
436 436  
437 -[[image:image-20220525091816-30.png]]
562 +[[image:image-20220526141052-29.png||_mstalt="454337"]]
438 438  
439 439  downlink
440 440  
566 +
567 +
441 441  (((
442 442  When downlink is successfully sent, the downlink information can be received on the serial port.
443 443  )))
444 444  
445 445  (((
446 -**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 +
447 447  )))
448 448  
449 -[[image:image-20220525091855-31.png]]
578 +[[image:image-20220526141116-30.png||_mstalt="451672"]]
450 450  
451 451  downlink
452 452  
582 +
453 453  (((
454 454  (((
455 455  If you want to get a successful reply to send downlink in TTN v3. You need to set the response level.
... ... @@ -458,13 +458,13 @@
458 458  
459 459  (((
460 460  (((
461 -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**
462 462  )))
463 463  )))
464 464  
465 465  (((
466 466  (((
467 -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**
468 468  )))
469 469  )))
470 470  
... ... @@ -471,59 +471,177 @@
471 471  (((
472 472  (((
473 473  When the device successfully receives the downlink, the server will receive a confirmation packet of 00.
604 +
605 +
474 474  )))
475 475  )))
476 476  
477 -[[image:image-20220525091925-32.png]]
609 +[[image:image-20220526141149-31.png||_mstalt="454038"]]
478 478  
479 479  downlink
480 480  
481 -= 6. Request Remote Support =
482 482  
614 += 6.  Route TTN data to Node-Red =
615 +
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" %)
483 483  (((
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 +(((
484 484  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.
485 485  \\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:**
486 486  )))
487 487  
488 488  * End node is connected to serial port to show the Join frequency and DR. (If possible)
724 +
489 489  * Gateway (from gateway UI) traffic to show the packet got from end node and receive from Server. (If possible)
726 +
490 490  * Gateway traffic (from server UI) to shows the data exchange between gateway and server. (Normally possible)
728 +
491 491  * End Node traffic (from server UI) to shows end node activity in server. (Normally possible)
730 +
492 492  * 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)
493 493  
494 -**~1. End Device Join Screen shot, we can check:**
733 +(% style="color:blue" %)**1. End Device Join Screen shot, we can check:**
495 495  
496 496  * If the device is sending join request to server?
736 +
497 497  * What frequency the device is sending?
498 498  
499 -[[image:image-20220525092012-33.png]]
739 +[[image:image-20220526141308-33.png||_mstalt="453778"]]
500 500  
501 501  Console Output from End device to see the transmit frequency
502 502  
503 -User can run **AT+CFG **command to print configuration information.
504 504  
505 -* 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.
506 506  
507 -[[image:image-20220525092043-34.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)
508 508  
748 +[[image:image-20220526141612-36.png||_mstalt="454142"]]
749 +
750 +
509 509  Console Output from End device to see the transmit frequency
510 510  
511 -**2. Gateway packet traffic in gateway web or ssh. we can check:**
512 512  
754 +
755 +(% style="color:blue" %)**2. Gateway packet traffic in gateway web or ssh. we can check:**
756 +
513 513  * (((
514 514  If the gateway receive the Join request packet from sensor? (If this fail, check if the gateway and sensor works on the match frequency)
515 515  )))
516 516  * (((
517 517  If the gateway gets the Join Accept message from server and transmit it via LoRa?
762 +
763 +
764 +
518 518  )))
519 519  
520 -[[image:image-20220525092124-35.png]]
767 +[[image:image-20220526141739-37.png||_mstalt="457847"]]
521 521  
522 522  Console Output from Gateway to see packets between end node and server.
523 523  
524 524  
525 -**3. Gateway Traffic Page in LoRaWAN Server**
526 526  
773 +(% style="color:blue" %)**3. Gateway Traffic Page in LoRaWAN Server**
774 +
527 527  * (((
528 528  If the Join Request packet arrive the gateway traffic in server? If not, check the internet connection and gateway LoRaWAN server settings.
529 529  )))
... ... @@ -532,25 +532,32 @@
532 532  )))
533 533  * (((
534 534  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 +
535 535  )))
536 536  
537 -[[image:image-20220525092157-36.png]]
788 +[[image:image-20220526141823-38.png||_mstalt="456183" height="501" width="1144"]]
538 538  
539 539  The Traffic for the End node in the server, use TTNv3 as example
540 540  
541 541  
542 -[[image:image-20220525092231-37.png]]
543 543  
794 +[[image:image-20220526141917-39.png||_mstalt="457899"]]
795 +
544 544  The Traffic for the End node in the server, use TTNv3 as example
545 545  
546 -**4. Data Page in LoRaWAN server**
547 547  
799 +
800 +(% style="color:blue" %)**4. Data Page in LoRaWAN server**
801 +
548 548  (((
549 549  (((
550 550  (((
551 551  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.
552 552  
553 -[[image:image-20220525092546-1.png]]
807 +
808 +[[image:image-20220526141956-40.png||_mstalt="455832"]]
554 554  )))
555 555  )))
556 556  )))
... ... @@ -557,6 +557,219 @@
557 557  
558 558  The data for the end device set in server
559 559  
560 -[[image:image-20220525092430-40.png]]
561 561  
816 +
817 +[[image:image-20220526142033-41.png||_mstalt="452036"]]
818 +
562 562  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 +
995 +== 9.2 Why node join succeeds but detailed data cannot be observed in the live data interface? ==
996 +
997 +
998 +The live data interface on the TTN platform is more orientated towards real-time observations, so if you don't click on the observations in time, you will not be able to see the previous details if you click on the interface again after a period of time.
999 +
1000 +TTN has no fixed official explanation for how long this data refreshes, but actual tests show it to be around 10 minutes.
1001 +
1002 +
1003 +Users can see the time of the last activity of a node inside one of the Applications：
1004 +
1005 +[[image:image-20240820171935-1.png||height="714" width="1358"]]
1006 +
1007 +For example:
1008 +
1009 +* After 6 minutes of the last activity, click on the **live data** interface to observe the data.
1010 +
1011 +[[image:image-20240820172327-2.png||height="439" width="1365"]]
1012 +
1013 +* The last activity of a node that has not been clicked for a long time was more than ten minutes ago, and you cannot observe the previous detailed data by clicking on the live data interface at this time.
1014 +
1015 +[[image:image-20240820172513-3.png]]
1016 +
1017 +In addition, if one stays in the LIVE DATA screen for a node, several previous details have been observed. If the node is inactive for a long time to come, and the interface is refreshed at this point, the details of the previously active data may be refreshed and no longer displayed.
1018 +
1019 +
1020 +If the user needs to view the data uplinked from a previous node, the data can be retrieved through the endpoint given by **Storage Integration**. The data can then be distinguished between different nodes based on **device_id**.
1021 +
1022 +[[image:image-20240820172909-4.png||height="524" width="954"]]
1023 +
1024 +
1025 +[[image:image-20240820172925-5.png||height="533" width="1318"]]
1026 +
1027 +
1028 +
1029 +
1030 +
image-20220526140251-21.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +67.9 KB
Content
image-20220526140347-22.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +63.0 KB
Content
image-20220526140420-23.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +77.4 KB
Content
image-20220526140452-24.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +32.4 KB
Content
image-20220526140708-25.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +827.1 KB
Content
image-20220526140856-26.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +114.9 KB
Content
image-20220526140936-27.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +103.1 KB
Content
image-20220526141021-28.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +74.8 KB
Content
image-20220526141052-29.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +84.1 KB
Content
image-20220526141116-30.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +10.1 KB
Content
image-20220526141149-31.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +59.0 KB
Content
image-20220526141236-32.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +114.0 KB
Content
image-20220526141308-33.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +90.1 KB
Content
image-20220526141350-34.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +78.7 KB
Content
image-20220526141612-36.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +78.2 KB
Content
image-20220526141739-37.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +288.0 KB
Content
image-20220526141823-38.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +197.3 KB
Content
image-20220526141917-39.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +154.2 KB
Content
image-20220526141956-40.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +163.5 KB
Content
image-20220526142033-41.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +25.2 KB
Content
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