Skip to Content

Changes for page Notes for TTN

Last modified by Xiaoling on 2025/08/04 14:58
From version 181.1
edited by Kilight Cao
on 2022/09/14 14:15
Change comment: Uploaded new attachment "image-20220914141502-6.png", version {1}
To version 199.2
edited by Xiaoling
on 2023/03/09 15:23
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Kilight
1 +XWiki.Xiaoling
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  
... ... @@ -93,10 +93,8 @@
93 93  Show Status
94 94  
95 95  
96 -
97 97  == 2.2  Secondary LoRaWAN Server ==
98 98  
99 -
100 100  === 2.2.1  Introduction ===
101 101  
102 102  
... ... @@ -103,7 +103,6 @@
103 103  The Dragino gateway has supports the Secondary server settings.
104 104  
105 105  
106 -
107 107  === 2.2.2  Below list the support products and Requirements: ===
108 108  
109 109  
... ... @@ -116,7 +116,6 @@
116 116  )))
117 117  
118 118  
119 -
120 120  === 2.2.3  Example ===
121 121  
122 122  
... ... @@ -123,7 +123,6 @@
123 123  The following takes Helium as a Secondary LoRaWAN server as an example
124 124  
125 125  
126 -
127 127  === 2.2.4  Step 1: Download and Install the helium gateway-rs ===
128 128  
129 129  
... ... @@ -135,7 +135,6 @@
135 135  Download and Install gateway-rs
136 136  
137 137  
138 -
139 139  === 2.2.5  Step 2: Back to Semtech UDP page ===
140 140  
141 141  
... ... @@ -147,17 +147,17 @@
147 147  Configuration of helium
148 148  
149 149  
150 -
151 151  = 3.  Gateway Registration for Basics Station =
152 152  
153 -
154 154  == 3.1  Introduction ==
155 155  
156 156  
157 157  (((
158 158  (((
159 -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/]]
160 160  
151 +(% style="color:red" %)**Note: Steps 2 and 3 are different connection methods, the user only needs to choose one of them**
152 +
161 161  
162 162  )))
163 163  )))
... ... @@ -186,7 +186,6 @@
186 186  (((
187 187  A gateway that can access the internet normally
188 188  
189 -
190 190  
191 191  )))
192 192  )))
... ... @@ -219,7 +219,6 @@
219 219  Add Gateway
220 220  
221 221  
222 -
223 223  == 3.3  Step 2: Create the API key ==
224 224  
225 225  
... ... @@ -237,10 +237,9 @@
237 237  Create LNS API key
238 238  
239 239  
240 -(% style="color:red" %)**Note : Please copy the API key.**
230 +(% style="color:red" %)**Note: Please copy the API key.**
241 241  
242 242  
243 -
244 244  == 3.4  Step 3: Update the gateway setting ==
245 245  
246 246  
... ... @@ -252,7 +252,6 @@
252 252  paste the API key
253 253  
254 254  
255 -
256 256  == 3.5  Step 4: Access the gateway GUI ==
257 257  
258 258  
... ... @@ -264,7 +264,6 @@
264 264  Access the gateway GUI
265 265  
266 266  
267 -
268 268  == 3.6  Step 5: Configure Station ==
269 269  
270 270  
... ... @@ -286,7 +286,6 @@
286 286  Congfigure Station
287 287  
288 288  
289 -
290 290  == 3.7  Start Station ==
291 291  
292 292  
... ... @@ -293,7 +293,6 @@
293 293  (((
294 294  When the user has finished the configuration,Please click Sace&Apply to start station to connect The Things Network.
295 295  
296 -
297 297  
298 298  )))
299 299  
... ... @@ -308,7 +308,6 @@
308 308  Station live date
309 309  
310 310  
311 -
312 312  == 3.9  Trouble Shooting ==
313 313  
314 314  
... ... @@ -328,7 +328,6 @@
328 328  Recore Log
329 329  
330 330  
331 -
332 332  = 4.  Configure node connection to TTNv3 =
333 333  
334 334  
... ... @@ -348,7 +348,6 @@
348 348  (((
349 349  (% style="color:#037691" %)**We take LES01 as an example.**
350 350  
351 -
352 352  
353 353  )))
354 354  )))
... ... @@ -374,13 +374,21 @@
374 374  )))
375 375  )))
376 376  
377 -[[image:image-20220526140015-17.png]]
359 +[[image:image-20230221135445-1.png||height="356" width="777"]]
378 378  
361 +First create an application and fill in the custom information in it
379 379  
380 -[[image:image-20220526140044-18.png]]
363 +[[image:image-20230221135520-2.png||height="52" width="974"]]
381 381  
365 +[[image:image-20230221135810-3.png||height="400" width="638"]]
382 382  
383 383  
368 +Add a node device to the application
369 +
370 +
371 +[[image:image-20220526140044-18.png]]
372 +
373 +
384 384  == 4.2  Step 2 ==
385 385  
386 386  
... ... @@ -388,14 +388,11 @@
388 388  (((
389 389  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.
390 390  
391 -
381 +[[image:image-20230221164809-2.png||height="525" width="617"]]
392 392  )))
393 393  )))
394 394  
395 -[[image:image-20220526140132-19.png]]
396 396  
397 -
398 -
399 399  == 4.3  Step 3 ==
400 400  
401 401  
... ... @@ -402,10 +402,9 @@
402 402  Add APP EUI in the application:
403 403  
404 404  
405 -[[image:image-20220526140205-20.png]]
392 +[[image:image-20230221140131-4.png||height="569" width="674"]]
406 406  
407 407  
408 -
409 409  == 4.4  Step 4 ==
410 410  
411 411  
... ... @@ -412,13 +412,11 @@
412 412  **Add APP KEY and DEV EUI:**
413 413  
414 414  
415 -[[image:image-20220526140251-21.png]]
401 +[[image:image-20230221140448-6.png||height="535" width="647"]]
416 416  
417 417  
418 -
419 419  = 5.  TTN V3 integrated into MQTT server =
420 420  
421 -
422 422  == 5.1  Introduction ==
423 423  
424 424  
... ... @@ -426,7 +426,6 @@
426 426  (((
427 427  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 428  
429 -
430 430  
431 431  )))
432 432  )))
... ... @@ -538,7 +538,6 @@
538 538  [[image:image-20220526140936-27.png]]
539 539  
540 540  
541 -
542 542  == 5.3  Send Downlink message ==
543 543  
544 544  
... ... @@ -642,7 +642,6 @@
642 642  [[image:image-20220829164358-188.png||height="570" width="1130"]]
643 643  
644 644  
645 -
646 646  == 6.2  Debug ==
647 647  
648 648  
... ... @@ -651,7 +651,6 @@
651 651  [[image:image-20220829164652-189.png||height="572" width="1134"]]
652 652  
653 653  
654 -
655 655  == 6.3  Example: Use Local Server TTN and Node-Red in LPS8v2 ==
656 656  
657 657  
... ... @@ -663,7 +663,6 @@
663 663  Below are the steps to plot the sensor data on LPS8v2 Node-Red.
664 664  
665 665  
666 -
667 667  === 6.3.1  Link Node-Red to Local TTN ===
668 668  
669 669  
... ... @@ -675,28 +675,51 @@
675 675  After importing the Input Flow is complete, the user needs to edit the MQTT in the node
676 676  
677 677  
678 -**~1. Change the Topic**
657 +(% style="color:blue" %)**1. Change the Topic**
679 679  
680 680  
681 681  Topic modifies it to the following format:
682 682  
683 -**v3/(% style="color:red" %)Application ID(%%)@ttn/devices/(% style="color:red" %)End device ID(%%)/up**
662 +**v3/(% style="color:red" %)Application ID(%%)/devices/(% style="color:red" %)End device ID(%%)/up**
684 684  
685 -[[image:image-20220914101543-1.png||height="632" width="1134"]]
664 +[[image:image-20221018100743-1.png]]
686 686  
687 687  
688 -2.
689 689  
690 -[[image:image-20220914103142-2.png]]
668 +(% style="color:blue" %)**2. Enter the MQTT configuration information**
691 691  
692 692  
693 -[[image:image-20220914103303-3.png]]
671 +[[image:image-20221018100947-2.png]]
694 694  
695 -=== 6.3.3 Check result. ===
696 696  
697 697  
675 +[[image:image-20221018101102-3.png]]
698 698  
677 +(% class="wikigeneratedid" %)
678 +(% style="color:blue" %)**Finally, click "Update" and Deploy**
699 699  
680 +
681 +(% class="wikigeneratedid" %)
682 +"Connected" indicates that the Link Node-red to Local TTN is normal.
683 +
684 +(% class="wikigeneratedid" %)
685 +[[image:image-20220914140918-5.png||height="602" width="1121"]]
686 +
687 +
688 +=== 6.3.2 Check result. ===
689 +
690 +
691 +Users can check logs by adding debug.
692 +
693 +[[image:image-20220914140841-4.png||height="600" width="1119"]]
694 +
695 +
696 +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.
697 +
698 +
699 +[[image:image-20220914142021-7.png||height="517" width="1346"]]
700 +
701 +
700 700  = 7.  Request Remote Support =
701 701  
702 702  
... ... @@ -711,7 +711,6 @@
711 711  * End Node traffic (from server UI) to shows end node activity in server. (Normally possible)
712 712  * 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)
713 713  
714 -
715 715  (% style="color:blue" %)**1. End Device Join Screen shot, we can check:**
716 716  
717 717  * If the device is sending join request to server?
... ... @@ -799,3 +799,4 @@
799 799  
800 800  Check if OTAA Keys match the keys in device
801 801  
803 +
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