Changes for page Notes for TTN
Last modified by Xiaoling on 2025/08/04 14:58
From version 99.9
edited by Xiaoling
on 2022/07/25 08:44
on 2022/07/25 08:44
Change comment:
There is no comment for this version
To version 220.1
edited by Kilight Cao
on 2023/07/28 15:18
on 2023/07/28 15:18
Change comment:
Uploaded new attachment "image-20230728151807-3.png", version {1}
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 95 added, 0 removed)
- image-20220726134642-1.png
- image-20220726135759-2.png
- image-20220726135827-3.png
- image-20220829153628-1.png
- image-20220829153716-2.png
- image-20220829155610-3.png
- image-20220829160114-4.jpeg
- image-20220829160115-5.jpeg
- image-20220829160115-6.jpeg
- image-20220829160116-7.jpeg
- image-20220829160116-8.jpeg
- image-20220829160116-9.jpeg
- image-20220829160125-41.jpeg
- image-20220829160128-57.jpeg
- image-20220829160130-65.jpeg
- image-20220829160132-77.jpeg
- image-20220829160132-78.jpeg
- image-20220829160133-81.jpeg
- image-20220829160134-86.jpeg
- image-20220829160134-90.jpeg
- image-20220829160145-146.jpeg
- image-20220829160145-147.jpeg
- image-20220829160145-148.jpeg
- image-20220829160145-149.jpeg
- image-20220829160145-150.jpeg
- image-20220829160145-151.jpeg
- image-20220829160145-152.jpeg
- image-20220829160145-153.jpeg
- image-20220829160146-154.jpeg
- image-20220829160146-155.jpeg
- image-20220829160146-156.jpeg
- image-20220829160146-157.jpeg
- image-20220829160146-158.jpeg
- image-20220829160146-159.jpeg
- image-20220829160146-160.jpeg
- image-20220829160146-161.jpeg
- image-20220829160146-162.jpeg
- image-20220829160146-163.jpeg
- image-20220829160146-164.jpeg
- image-20220829160146-165.jpeg
- image-20220829160146-166.jpeg
- image-20220829160146-167.jpeg
- image-20220829160147-168.jpeg
- image-20220829160147-169.jpeg
- image-20220829160147-170.jpeg
- image-20220829160147-171.jpeg
- image-20220829160147-172.jpeg
- image-20220829160147-173.jpeg
- image-20220829160147-174.jpeg
- image-20220829160147-175.jpeg
- image-20220829160147-176.jpeg
- image-20220829160147-177.jpeg
- image-20220829160147-178.jpeg
- image-20220829160147-179.jpeg
- image-20220829160147-180.jpeg
- image-20220829160147-181.jpeg
- image-20220829160147-182.jpeg
- image-20220829160148-183.jpeg
- image-20220829160148-184.jpeg
- image-20220829160148-185.jpeg
- image-20220829160148-186.jpeg
- image-20220829160224-187.jpeg
- image-20220829164358-188.png
- image-20220829164652-189.png
- image-20220913134247-1.png
- image-20220913153442-2.png
- image-20220914101543-1.png
- image-20220914103142-2.png
- image-20220914103303-3.png
- image-20220914140841-4.png
- image-20220914140918-5.png
- image-20220914141502-6.png
- image-20220914142021-7.png
- image-20221018100743-1.png
- image-20221018100947-2.png
- image-20221018101102-3.png
- image-20230221135445-1.png
- image-20230221135520-2.png
- image-20230221135810-3.png
- image-20230221140131-4.png
- image-20230221140327-5.png
- image-20230221140448-6.png
- image-20230221164647-1.png
- image-20230221164809-2.png
- image-20230423154012-1.png
- image-20230423154040-2.png
- image-20230423154105-3.png
- image-20230423154125-4.png
- image-20230728143343-1.png
- image-20230728143449-2.png
- image-20230728143505-3.png
- image-20230728144218-7.png
- image-20230728145557-1.png
- image-20230728150521-2.png
- image-20230728151807-3.png
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Xiaoling1 +XWiki.Kilight - 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,10 +44,12 @@ 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 ... ... @@ -69,15 +69,32 @@ 69 69 70 70 71 71 70 +(% style="color:red" %)**Note:** 71 + 72 +DRAGINO - Frequency Plan list ~-~-~-~-~-~-~-~-~-~-~-~-~-~-- The Thing Network Frequency Plan List 73 + 74 +AS923-1 (920-923) ~-~-~-~-~-~-~-~-~-~-~-~-~-~-- 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||height="344" width="660"]][[image:image-20220726135827-3.png||height="214" width="394"]][[image:image-20220726135759-2.png||height="218" width="554"]] 86 + 87 + 88 + 72 72 [[image:image-20220526134919-5.png]] 73 73 74 74 Show Status 75 75 76 76 77 - 78 78 == 2.2 Secondary LoRaWAN Server == 79 79 80 - 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]]106 +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/]] 110 +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,52 +103,61 @@ 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 123 +The users is needing to download and install the helium gateway-rs then click the button of (% style="color:blue" %)**Save&Apply.** 111 111 125 + 112 112 [[image:image-20220526135049-6.png]] 113 113 114 114 Download and Install gateway-rs 115 115 116 116 117 -=== 2.2.5 Step 2: Back to Semtech UDP page === 131 +=== 2.2.5 Step 2: Back to Semtech UDP page === 118 118 119 -Back to the page of Semtech UDP check the secondary server settings and click the button of Save&Apply 120 120 134 +Back to the page of Semtech UDP check the secondary server settings and click the button of (% style="color:blue" %)**Save&Apply.** 135 + 136 + 121 121 [[image:image-20220526135125-7.png]] 122 122 123 123 Configuration of helium 124 124 125 125 126 -= 3. Gateway Registration for Basics Station = 142 += 3. Gateway Registration for Basics Station = 127 127 128 -== 3.1 Introduction == 144 +== 3.1 Introduction == 129 129 146 + 130 130 ((( 131 131 ((( 132 -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/]] 149 +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/]] 150 + 151 +(% style="color:red" %)**Note: Steps 2 and 3 are different connection methods, the user only needs to choose one of them** 152 + 153 + 133 133 ))) 134 134 ))) 135 135 136 136 ((( 137 -**Below list the support products and Requirements:** 158 +(% style="color:blue" %)**Below list the support products and Requirements:** 138 138 ))) 139 139 140 140 ((( 141 141 ((( 142 - ~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]]163 +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]] 143 143 ))) 144 144 145 145 ((( 146 - 2. Firmware version since :[[lgw~~-~~-build-v5.4.1640315898>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/]] 167 + 2. Firmware version since : [[lgw~~-~~-build-v5.4.1640315898>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/]] 168 + 169 + 147 147 ))) 148 148 ))) 149 149 150 150 ((( 151 -**What do you need to prepare** 174 +(% style="color:blue" %)**What do you need to prepare?** 152 152 ))) 153 153 154 154 ((( ... ... @@ -159,77 +159,98 @@ 159 159 ))) 160 160 ))) 161 161 162 -== 3.2 Step 1 .AddGateway ==185 +== 3.2 Step 1: Register Gateway == 163 163 164 -((( 165 -((( 166 -The example for **EU** 167 -))) 168 -))) 169 169 170 170 ((( 171 171 ((( 172 - Usercan add yourgatewayintoTheThings Network V3accordingto thepreviousstep190 +(% style="color:blue" %)**The example for**(%%)** the (% style="color:red" %)EU:(%%)** 173 173 ))) 174 174 ))) 175 175 176 176 ((( 177 177 ((( 178 -Following picture is the successful added. 196 +Click the 'Register Gateway' button will get this page to register the gateway from The Thing Network Console gateway page. 197 + 198 +[[image:image-20230728144218-7.png||height="128" width="836"]] 179 179 ))) 180 180 ))) 181 181 182 -[[image:image-202 20526135316-8.png]]202 +[[image:image-20230728143449-2.png]] 183 183 184 - AddGateway204 +Register Gateway 185 185 186 186 187 -== 3.3 Step 2 .Create the API key ==207 +== 3.3 Step 2: Create the API key == 188 188 189 -user need to create the CUPS API key and LNS API key. 190 190 210 +**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 211 + 212 + 213 + 214 + 215 +**or generate by TTN by checking the check box when registering the gateway** ~-~-->[[image:image-20230728143505-3.png]] 216 + 217 + 218 +=== **1.) Generated by TTH** === 219 + 220 +=== === 221 + 222 +=== === 223 + 224 +=== **2.) Manually create API KEY: ** === 225 + 226 + 227 +==== CUPS API KEY ==== 228 + 191 191 [[image:image-20220526135349-9.png]] 192 192 193 -Create CUPS API key 194 194 195 195 233 +==== LNS API KEY ==== 234 + 196 196 [[image:image-20220526135428-10.png]] 197 197 198 -Create LNS API key 199 199 200 -(% style="color:red" %)**Note leasecopytheAPIkey.**238 +(% style="color:red" %)**Note: If your API is generated by yourself you have to update the key to the gateway setting.** 201 201 202 202 203 -== 3.4 Step 3.Update the gateway setting ==241 +==== Update the gateway setting ==== 204 204 243 + 205 205 In the LoRa Basics Station LNS Authentication Key field, paste the API key you generated in the previous step. 206 206 246 + 207 207 [[image:image-20220526135528-11.png]] 208 208 209 209 paste the API key 210 210 211 211 212 -== 3.5 Step 4 .Access the gateway GUI ==252 +== 3.5 Step 4: Access the gateway GUI == 213 213 254 + 214 214 User need to update the API key and install the Certificate 215 215 257 + 216 216 [[image:image-20220526135601-12.png]] 217 217 218 218 Access the gateway GUI 219 219 220 220 221 -== 3.6 Step 5 .Configure Station ==263 +== 3.6 Step 5: Configure Station == 222 222 265 + 223 223 User need to input Server URI, Server CUPS Key and LNS Key, as well as install CUPS certificate. 224 224 225 -**just to clarify.** 226 226 269 +(% style="color:blue" %)**just to clarify:** 270 + 227 227 (% class="box" %) 228 228 ((( 229 - CUPS Server URI ~-~-> Server Adress 230 - CUPS Authorization Key ~-~-> Server CUPS API Key 231 - LNS Authorization Key ~-~-> Server LNS API Key 232 - CUPS certificate ~-~-> Server CA(user can use the button to install the certificate by default) 273 + CUPS Server URI ~-~-> Server Adress 274 + CUPS Authorization Key ~-~-> Server CUPS API Key 275 + LNS Authorization Key ~-~-> Server LNS API Key 276 + CUPS certificate ~-~-> Server CA(user can use the button to install the certificate by default) 233 233 ))) 234 234 235 235 [[image:image-20220526135654-13.png]] ... ... @@ -237,8 +237,9 @@ 237 237 Congfigure Station 238 238 239 239 240 -== 3.7 Start Station == 284 +== 3.7 Start Station == 241 241 286 + 242 242 ((( 243 243 When the user has finished the configuration,Please click Sace&Apply to start station to connect The Things Network. 244 244 ... ... @@ -245,33 +245,39 @@ 245 245 246 246 ))) 247 247 248 -== 3.8 Siccessful Connection == 293 +== 3.8 Siccessful Connection == 249 249 295 + 250 250 If user completes the above steps,which will see live date in the TTN. 251 251 298 + 252 252 [[image:image-20220526135734-14.png]] 253 253 254 254 Station live date 255 255 256 256 257 -== 3.9 Trouble Shooting == 304 +== 3.9 Trouble Shooting == 258 258 259 -User can check the station log in the logread/system log page. 260 260 307 +User can check the station log in the** (% style="color:blue" %)LogRead ~-~-> System Log (%%)**page. 308 + 309 + 261 261 [[image:image-20220526135845-15.png]] 262 262 263 263 Station Log 264 264 265 265 266 -and recode the station log in the system/Recode log page. 267 267 316 +and recode the station log in the** (% style="color:blue" %)LogRead ~-~-> Recode Log(%%)** page. 317 + 268 268 [[image:image-20220526135940-16.png]] 269 269 270 270 Recore Log 271 271 272 272 273 -= 4. Configure node connection to TTNv3 = 323 += 4. Configure node connection to TTNv3 = 274 274 325 + 275 275 ((( 276 276 ((( 277 277 Following is an example for how to join the TTN v3 LoRaWAN Network. ... ... @@ -286,14 +286,15 @@ 286 286 287 287 ((( 288 288 ((( 289 -We take LES01 as an example. 340 +(% style="color:#037691" %)**We take LES01 as an example.** 290 290 291 291 292 292 ))) 293 293 ))) 294 294 295 -== 4.1 Step1 == 346 +== 4.1 Step 1 == 296 296 348 + 297 297 ((( 298 298 ((( 299 299 Create a device in TTN with the OTAA keys from LSE01. ... ... @@ -312,40 +312,56 @@ 312 312 ))) 313 313 ))) 314 314 315 -[[image:image-202 20526140015-17.png]]367 +[[image:image-20230221135445-1.png||height="356" width="777"]] 316 316 369 +First create an application and fill in the custom information in it 370 + 371 +[[image:image-20230221135520-2.png||height="52" width="974"]] 372 + 373 +[[image:image-20230221135810-3.png||height="400" width="638"]] 374 + 375 + 376 +Add a node device to the application 377 + 378 + 317 317 [[image:image-20220526140044-18.png]] 318 318 319 319 320 -== 4.2 Step2 == 382 +== 4.2 Step 2 == 321 321 384 + 322 322 ((( 323 323 ((( 324 324 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. 388 + 389 +[[image:image-20230221164809-2.png||height="525" width="617"]] 325 325 ))) 326 326 ))) 327 327 328 -[[image:image-20220526140132-19.png]] 329 329 394 +== 4.3 Step 3 == 330 330 331 -== 4.3 Step3 == 332 332 333 333 Add APP EUI in the application: 334 334 335 -[[image:image-20220526140205-20.png]] 336 336 400 +[[image:image-20230221140131-4.png||height="569" width="674"]] 337 337 338 -== 4.4 Step4 == 339 339 340 - AddAPPKEYandDEV EUI:403 +== 4.4 Step 4 == 341 341 342 -[[image:image-20220526140251-21.png]] 343 343 406 +**Add APP KEY and DEV EUI:** 344 344 345 -= 5. TTN V3 integrated into MQTT server = 346 346 347 - == 5.1Introduction==409 +[[image:image-20230221140448-6.png||height="535" width="647"]] 348 348 411 + 412 += 5. TTN V3 integrated into MQTT server = 413 + 414 +== 5.1 Introduction == 415 + 416 + 349 349 ((( 350 350 ((( 351 351 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. ... ... @@ -354,8 +354,9 @@ 354 354 ))) 355 355 ))) 356 356 357 -== 5.2 Create device steps at MQTT == 425 +== 5.2 Create device steps at MQTT == 358 358 427 + 359 359 ((( 360 360 ((( 361 361 The user creates a new API KEY after creating a device on TTN V3. ... ... @@ -371,6 +371,8 @@ 371 371 ((( 372 372 ((( 373 373 Fill in Broker Address and Broker port. 443 + 444 + 374 374 ))) 375 375 ))) 376 376 ... ... @@ -379,8 +379,10 @@ 379 379 Fill in the username and password into MQTT. 380 380 381 381 453 + 382 382 [[image:image-20220526140420-23.png]] 383 383 456 + 384 384 The Application Server publishes uplink traffic on the following topics: 385 385 386 386 (% class="box" %) ... ... @@ -397,13 +397,18 @@ 397 397 ))) 398 398 399 399 ((( 473 + 474 + 400 400 ((( 401 -**Note**: Remember that the format of these topics for The Things Stack Open Source would contain {application id} instead of {application id}@{tenant id}. 476 +(% 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}.** 477 + 478 + 402 402 ))) 403 403 ))) 404 404 405 405 [[image:image-20220526140452-24.png]] 406 406 484 + 407 407 ((( 408 408 ((( 409 409 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. ... ... @@ -420,7 +420,11 @@ 420 420 421 421 ((( 422 422 ((( 423 -**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. 501 + 502 + 503 +(% 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.** 504 + 505 + 424 424 ))) 425 425 ))) 426 426 ... ... @@ -434,17 +434,22 @@ 434 434 435 435 ((( 436 436 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: 519 + 520 + 437 437 ))) 438 438 439 439 ((( 440 -**Note**: Use this handy tool to convert hexadecimal to base64. 524 +(% style="color:red" %)**Note**: **Use this handy tool to convert hexadecimal to base64.** 525 + 526 + 441 441 ))) 442 442 443 443 [[image:image-20220526140936-27.png]] 444 444 445 445 446 -== 5.3 Send Downlink message == 532 +== 5.3 Send Downlink message == 447 447 534 + 448 448 ((( 449 449 How to configure downlink in TTN V3? 450 450 ))) ... ... @@ -454,7 +454,9 @@ 454 454 ))) 455 455 456 456 ((( 457 -Downlink command:01 00 00 5A 544 +(% style="color:blue" %)**Downlink command: 01 00 00 5A** 545 + 546 + 458 458 ))) 459 459 460 460 [[image:image-20220526141021-28.png]] ... ... @@ -462,6 +462,7 @@ 462 462 downlink 463 463 464 464 554 + 465 465 After sending, you can view it in live data. 466 466 467 467 [[image:image-20220526141052-29.png]] ... ... @@ -469,12 +469,15 @@ 469 469 downlink 470 470 471 471 562 + 472 472 ((( 473 473 When downlink is successfully sent, the downlink information can be received on the serial port. 474 474 ))) 475 475 476 476 ((( 477 -**Note**: If the downlink byte sent is longer, the number of bytes will be displayed. 568 +(% style="color:red" %)**Note**:** If the downlink byte sent is longer, the number of bytes will be displayed.** 569 + 570 + 478 478 ))) 479 479 480 480 [[image:image-20220526141116-30.png]] ... ... @@ -490,13 +490,13 @@ 490 490 491 491 ((( 492 492 ((( 493 -If the equipment uses CLASS A. You can set **AT+RPL=2** or send the downlink command: **2102** 586 +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** 494 494 ))) 495 495 ))) 496 496 497 497 ((( 498 498 ((( 499 -If the equipment uses CLASS C. You can set** AT+RPL=4** or send the downlink command: **2104** 592 +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** 500 500 ))) 501 501 ))) 502 502 ... ... @@ -503,6 +503,8 @@ 503 503 ((( 504 504 ((( 505 505 When the device successfully receives the downlink, the server will receive a confirmation packet of 00. 599 + 600 + 506 506 ))) 507 507 ))) 508 508 ... ... @@ -511,22 +511,129 @@ 511 511 downlink 512 512 513 513 514 -= 6. R equestRemoteSupport=609 += 6. Route TTN data to Node-Red = 515 515 611 + 612 +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]]" 613 + 614 + 615 +== 6.1 Edit mqtt-broker node == 616 + 617 + 618 +Users need to configure the TTN MQTT server address and port, Such as: 619 + 620 +(% class="box infomessage" %) 516 516 ((( 622 +**Server :** eu1.cloud.thethings.network 623 + 624 +**Port :** 1883 625 +))) 626 + 627 +[[image:image-20220829160224-187.jpeg||height="569" width="1128"]] 628 + 629 + 630 +**Enter Username and Password** 631 + 632 +[[image:image-20220829164358-188.png||height="570" width="1130"]] 633 + 634 + 635 +== 6.2 Debug == 636 + 637 + 638 +Users can check logs by adding debug. 639 + 640 +[[image:image-20220829164652-189.png||height="572" width="1134"]] 641 + 642 + 643 +== 6.3 Example: Use Local Server TTN and Node-Red in LPS8v2 == 644 + 645 + 646 +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: 647 + 648 +* LHT65N register on LPS8v2 Built-In TTN server already 649 +* The user is able to see the data on the built-in TTN server device page. 650 + 651 +Below are the steps to plot the sensor data on LPS8v2 Node-Red. 652 + 653 + 654 +=== 6.3.1 Link Node-Red to Local TTN === 655 + 656 + 657 +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]]** 658 + 659 +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);"]]** 660 + 661 + 662 +After importing the Input Flow is complete, the user needs to edit the MQTT in the node 663 + 664 + 665 +(% style="color:blue" %)**1. Change the Topic** 666 + 667 + 668 +Topic modifies it to the following format: 669 + 670 +**v3/(% style="color:red" %)Application ID(%%)/devices/(% style="color:red" %)End device ID(%%)/up** 671 + 672 +[[image:image-20221018100743-1.png]] 673 + 674 + 675 + 676 +(% style="color:blue" %)**2. Enter the MQTT configuration information** 677 + 678 + 679 +[[image:image-20221018100947-2.png]] 680 + 681 + 682 + 683 +[[image:image-20221018101102-3.png]] 684 + 685 +(% class="wikigeneratedid" %) 686 +(% style="color:blue" %)**Finally, click "Update" and Deploy** 687 + 688 + 689 +(% class="wikigeneratedid" %) 690 +"Connected" indicates that the Link Node-red to Local TTN is normal. 691 + 692 +(% class="wikigeneratedid" %) 693 +[[image:image-20220914140918-5.png||height="602" width="1121"]] 694 + 695 + 696 +=== 6.3.2 Check result. === 697 + 698 + 699 +Users can check logs by adding debug. 700 + 701 +[[image:image-20220914140841-4.png||height="600" width="1119"]] 702 + 703 + 704 +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. 705 + 706 + 707 +[[image:image-20220914142021-7.png||height="517" width="1346"]] 708 + 709 + 710 += 7. Request Remote Support = 711 + 712 + 713 +((( 517 517 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. 518 518 \\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:** 519 519 ))) 520 520 521 521 * End node is connected to serial port to show the Join frequency and DR. (If possible) 719 + 522 522 * Gateway (from gateway UI) traffic to show the packet got from end node and receive from Server. (If possible) 721 + 523 523 * Gateway traffic (from server UI) to shows the data exchange between gateway and server. (Normally possible) 723 + 524 524 * End Node traffic (from server UI) to shows end node activity in server. (Normally possible) 725 + 525 525 * 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) 526 526 527 -** ~1. End Device Join Screen shot, we can check:**728 +(% style="color:blue" %)**1. End Device Join Screen shot, we can check:** 528 528 529 529 * If the device is sending join request to server? 731 + 530 530 * What frequency the device is sending? 531 531 532 532 [[image:image-20220526141308-33.png]] ... ... @@ -533,10 +533,11 @@ 533 533 534 534 Console Output from End device to see the transmit frequency 535 535 536 -User can run **AT+CFG **command to print configuration information. 537 537 538 - * IsthedeviceinOTAAmoder ABP mode?**AT+NJM=1**OTAA mode),**AT+NJM=0**(ABPmode)739 +User can run (% style="color:blue" %)**AT+CFG **(%%)command to print configuration information. 539 539 741 +* 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) 742 + 540 540 [[image:image-20220526141612-36.png]] 541 541 542 542 ... ... @@ -543,13 +543,17 @@ 543 543 Console Output from End device to see the transmit frequency 544 544 545 545 546 -**2. Gateway packet traffic in gateway web or ssh. we can check:** 547 547 750 +(% style="color:blue" %)**2. Gateway packet traffic in gateway web or ssh. we can check:** 751 + 548 548 * ((( 549 549 If the gateway receive the Join request packet from sensor? (If this fail, check if the gateway and sensor works on the match frequency) 550 550 ))) 551 551 * ((( 552 552 If the gateway gets the Join Accept message from server and transmit it via LoRa? 757 + 758 + 759 + 553 553 ))) 554 554 555 555 [[image:image-20220526141739-37.png]] ... ... @@ -557,8 +557,9 @@ 557 557 Console Output from Gateway to see packets between end node and server. 558 558 559 559 560 -**3. Gateway Traffic Page in LoRaWAN Server** 561 561 768 +(% style="color:blue" %)**3. Gateway Traffic Page in LoRaWAN Server** 769 + 562 562 * ((( 563 563 If the Join Request packet arrive the gateway traffic in server? If not, check the internet connection and gateway LoRaWAN server settings. 564 564 ))) ... ... @@ -567,6 +567,9 @@ 567 567 ))) 568 568 * ((( 569 569 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. 778 + 779 + 780 + 570 570 ))) 571 571 572 572 [[image:image-20220526141823-38.png||height="501" width="1144"]] ... ... @@ -574,18 +574,21 @@ 574 574 The Traffic for the End node in the server, use TTNv3 as example 575 575 576 576 788 + 577 577 [[image:image-20220526141917-39.png]] 578 578 579 579 The Traffic for the End node in the server, use TTNv3 as example 580 580 581 581 582 -**4. Data Page in LoRaWAN server** 583 583 795 +(% style="color:blue" %)**4. Data Page in LoRaWAN server** 796 + 584 584 ((( 585 585 ((( 586 586 ((( 587 587 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. 588 588 802 + 589 589 [[image:image-20220526141956-40.png]] 590 590 ))) 591 591 ))) ... ... @@ -594,6 +594,152 @@ 594 594 The data for the end device set in server 595 595 596 596 811 + 597 597 [[image:image-20220526142033-41.png]] 598 598 599 599 Check if OTAA Keys match the keys in device 815 + 816 + 817 += 8. FAQ = 818 + 819 +== 8.1 How to import devices keys to server. == 820 + 821 + 822 +**For TTS in LPS8v2** 823 + 824 +Open your application and click the button **Import end devices** 825 + 826 +[[image:image-20230423154012-1.png||height="472" width="755"]] 827 + 828 + 829 +Select the **File format** and upload the file (e.g. or ).devices/jsondevices.csv 830 + 831 +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. 832 + 833 +You can also expand the **Advanced claiming and component settings** to set targeted components, and set the claim authentication code to be generated. 834 + 835 +Start the import by clicking the **Import end devices** button. 836 + 837 +[[image:image-20230423154040-2.png||height="470" width="749"]] 838 + 839 + 840 +Wait for the end devices to be successfully imported. In case any device fails, you will see a relevant error message in the console. 841 + 842 +[[image:image-20230423154105-3.png||height="478" width="763"]] 843 + 844 + 845 +If the import was successful, your devices are added to the list of end devices in your application. 846 + 847 +[[image:image-20230423154125-4.png||height="480" width="766"]] 848 + 849 +Devices are now registered on The Things Stack. 850 + 851 + 852 +=== **JSON File Reference** === 853 + 854 + 855 +The Things Stack allows you to import end devices from V2, ChirpStack and other LoRaWAN networks using a JSON file describing those devices. 856 + 857 +Using JSON file with device descriptions, you can migrate end devices with or without their existing sessions. 858 + 859 +Here is an example of an OTAA device description in the file:devices.json 860 + 861 +{{{{ 862 + "ids": { 863 + "device_id": "my-device", 864 + "dev_eui": "0102030405060708", 865 + "join_eui": "0102030405060708" 866 + }, 867 + "name": "My Device", 868 + "description": "Living room temperature sensor", 869 + "lorawan_version": "MAC_V1_0_2", 870 + "lorawan_phy_version": "PHY_V1_0_2_REV_B", 871 + "frequency_plan_id": "EU_863_870_TTN", 872 + "supports_join": true, 873 + "root_keys": { 874 + "app_key": { 875 + "key": "01020304050607080102030405060708" 876 + } 877 + } 878 +} 879 +}}} 880 + 881 +Multiple end devices can also be contained in a single file like so:devices.json 882 + 883 +{{{{ 884 + /* device 1 */ 885 +} 886 +{ 887 + /* device 2 */ 888 +} 889 +}}} 890 + 891 +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 892 + 893 + 894 +=== **CSV File Reference** === 895 + 896 + 897 +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. 898 + 899 +The CSV import in The Things Stack uses the following settings: 900 + 901 +* Semicolon () as field delimiter. This makes working with Microsoft Excel and other spreadsheets convenient; 902 + 903 +* Header row is required 904 + 905 +* On each row, the same number of fields as on the header line 906 + 907 +* Use quotes to use in a field value; 908 + 909 +* Use double quotes to escape quotes 910 + 911 +* Unknown header columns are permitted and ignored 912 + 913 +* Name and id cannot have capital letters and special characters 914 + 915 +* Example column lorawan_phy_version is not needed 916 + 917 +(% style="display:none" %) 918 + 919 + 920 + 921 +=== **Example** === 922 + 923 + 924 +Minimal example: 925 + 926 +{{{dev_eui;join_eui;frequency_plan_id;lorawan_version;lorawan_phy_version;app_key 927 +1111111111111111;1111111111111111;EU_863_870_TTN;MAC_V1_0_4;RP002_V1_0_3;11111111111111111111111111111111 928 +2222222222222222;2222222222222222;EU_863_870_TTN;MAC_V1_0_4;RP002_V1_0_3;22222222222222222222222222222222 929 +3333333333333333;3333333333333333;EU_863_870_TTN;MAC_V1_0_4;RP002_V1_0_3;33333333333333333333333333333333 930 +}}} 931 + 932 +All columns for a LoRaWAN 1.0.4 device: 933 + 934 +{{{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 935 +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 936 +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 937 +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 938 +}}} 939 + 940 + 941 + 942 +=== **Excel Template** === 943 + 944 + 945 +[[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). 946 + 947 + 948 += 9. Trouble Shooting. = 949 + 950 +== 9.1 How to solve the problem of MIC Mismatch? == 951 + 952 + 953 +Please refer to the link below: 954 + 955 +[[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]] 956 + 957 + 958 + 959 +
- 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