Changes for page Notes for TTN

Last modified by Mengting Qiu on 2024/08/20 17:29
<
From version < 82.1 >
edited by Xiaoling
on 2022/05/26 14:04
To version < 99.11 >
edited by Xiaoling
on 2022/07/25 08:52
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,14 +1,18 @@
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 9  
10 -=== 1.1.1 What is The Things Network ===
10 +== 1.1  Introduction ==
11 11  
12 +
13 +=== 1.1.1  What is The Things Network ===
14 +
15 +
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  )))
... ... @@ -16,11 +16,13 @@
16 16  (((
17 17  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.
18 18  
23 +
19 19  
20 20  )))
21 21  
22 -=== 1.1.2 Login or crate an account ===
27 +=== 1.1.2  Login or crate an account ===
23 23  
29 +
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  )))
... ... @@ -28,47 +28,59 @@
28 28  (((
29 29  Once you have an account,get started by following steps for adding Gateway,Device and Intergrations.
30 30  
37 +
31 31  
32 32  )))
33 33  
34 -=== 1.1.3 List the support products and Requirements ===
41 +=== 1.1.3  List the support products and Requirements ===
35 35  
43 +
36 36  LoRaWAN Gateway model: Existing Gateway
37 37  
38 38  
39 -= 2. Gateway Registration for Semtech UDP =
40 40  
41 -== 2.1 Primary LoRaWAN Server ==
48 += 2.  Gateway Registration for Semtech UDP =
42 42  
50 +
51 +== 2.1  Primary LoRaWAN Server ==
52 +
53 +
43 43  [[image:image-20220526134633-2.png||height="616" width="1323"]]
44 44  
45 45  Register Gateway
46 46  
47 47  
59 +
48 48  [[image:image-20220526134826-4.png]]
49 49  
50 50  Put Gateway ID
51 51  
52 52  
65 +
53 53  [[image:image-20220526134759-3.png]]
54 54  
55 55  Choose Frequency Band
56 56  
57 57  
71 +
58 58  [[image:image-20220526134919-5.png]]
59 59  
60 60  Show Status
61 61  
62 62  
63 -== 2.2 Secondary LoRaWAN Server ==
64 64  
65 -=== 2.2.1 Introduction ===
78 +== 2.2  Secondary LoRaWAN Server ==
66 66  
80 +
81 +=== 2.2.1  Introduction ===
82 +
83 +
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: ===
87 +=== 2.2.2  Below list the support products and Requirements: ===
71 71  
89 +
72 72  (((
73 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]]
74 74  )))
... ... @@ -78,13 +78,17 @@
78 78  )))
79 79  
80 80  
81 -=== 2.2.3 Example ===
82 82  
100 +=== 2.2.3  Example ===
101 +
102 +
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 ===
87 87  
107 +=== 2.2.4  Step 1: Download and Install the helium gateway-rs ===
108 +
109 +
88 88  The users is needing to download and install the helium gateway-rs then click the button of Save&Apply
89 89  
90 90  [[image:image-20220526135049-6.png]]
... ... @@ -92,8 +92,10 @@
92 92  Download and Install gateway-rs
93 93  
94 94  
95 -=== 2.2.5 Step 2: Back to Semtech UDP page ===
96 96  
118 +=== 2.2.5  Step 2: Back to Semtech UDP page ===
119 +
120 +
97 97  Back to the page of Semtech UDP check the secondary server settings and click the button of Save&Apply
98 98  
99 99  ​​​​[[image:image-20220526135125-7.png]]
... ... @@ -101,32 +101,41 @@
101 101  Configuration of helium
102 102  
103 103  
104 -= 3. Gateway Registration for Basics Station =
105 105  
106 -== 3.1 Introduction ==
129 += 3.  Gateway Registration for Basics Station =
107 107  
131 +
132 +== 3.1  Introduction ==
133 +
134 +
108 108  (((
109 109  (((
110 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/]]
138 +
139 +
111 111  )))
112 112  )))
113 113  
114 114  (((
115 -**Below list the support products and Requirements:**
144 +(% 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]]
149 +1. LoRaWAN Gateway model: [[LIG16>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/171-lig16.html]], [[LG308>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/140-lg308.html]], [[DLOS8>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/160-dlos8.html]] [[LPS8>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/148-lps8.html]]
121 121  )))
122 122  
123 123  (((
124 124   2. Firmware version since :[[lgw~~-~~-build-v5.4.1640315898>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/]]
154 +
155 +
156 +
157 +
125 125  )))
126 126  )))
127 127  
128 128  (((
129 -**What do you need to prepare**
162 +(% style="color:blue" %)**What do you need to prepare**
130 130  )))
131 131  
132 132  (((
... ... @@ -133,12 +133,14 @@
133 133  (((
134 134  A gateway that can access the internet normally
135 135  
169 +
136 136  
137 137  )))
138 138  )))
139 139  
140 -== 3.2 Step 1. Add Gateway ==
174 +== 3.2  Step 1: Add Gateway ==
141 141  
176 +
142 142  (((
143 143  (((
144 144  The example for **EU**
... ... @@ -154,6 +154,8 @@
154 154  (((
155 155  (((
156 156  Following picture is the successful added.
192 +
193 +
157 157  )))
158 158  )))
159 159  
... ... @@ -162,52 +162,66 @@
162 162  Add Gateway
163 163  
164 164  
165 -== 3.3 Step 2. Create the API key ==
166 166  
203 +== 3.3  Step 2: Create the API key ==
204 +
205 +
167 167  user need to create the CUPS API key and LNS API key.
168 168  
208 +
169 169  [[image:image-20220526135349-9.png]]
170 170  
171 171  Create CUPS API key
172 172  
173 173  
214 +
174 174  [[image:image-20220526135428-10.png]]
175 175  
176 176  Create LNS API key
177 177  
219 +
178 178  (% style="color:red" %)**Note : Please copy the API key.**
179 179  
180 180  
181 -== 3.4 Step 3. Update the gateway setting ==
182 182  
224 +== 3.4  Step 3: Update the gateway setting ==
225 +
226 +
183 183  In the LoRa Basics Station LNS Authentication Key field, paste the API key you generated in the previous step.
184 184  
229 +
185 185  [[image:image-20220526135528-11.png]]
186 186  
187 187  paste the API key
188 188  
189 189  
190 -== 3.5 Step 4. Access the gateway GUI ==
191 191  
236 +== 3.5  Step 4: Access the gateway GUI ==
237 +
238 +
192 192  User need to update the API key and install the Certificate
193 193  
241 +
194 194  [[image:image-20220526135601-12.png]]
195 195  
196 196  Access the gateway GUI
197 197  
198 198  
199 -== 3.6 Step 5. Configure Station ==
200 200  
248 +== 3.6  Step 5: Configure Station ==
249 +
250 +
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  
254 +(% style="color:blue" %)**just to clarify:**
255 +
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)
258 + CUPS Server URI  ~-~->  Server Adress
259 + CUPS Authorization Key         ~-~->  Server CUPS API Key
260 + LNS Authorization Key  ~-~->  Server LNS API Key
261 + CUPS certificate  ~-~->  Server CA(user can use the button to install the certificate by default)
211 211  )))
212 212  
213 213  [[image:image-20220526135654-13.png]]
... ... @@ -294,6 +294,7 @@
294 294  
295 295  [[image:image-20220526140044-18.png]]
296 296  
348 +
297 297  == 4.2 Step2 ==
298 298  
299 299  (((
... ... @@ -302,20 +302,23 @@
302 302  )))
303 303  )))
304 304  
305 -[[image:image-20220525090920-18.png]]
357 +[[image:image-20220526140132-19.png]]
306 306  
359 +
307 307  == 4.3 Step3 ==
308 308  
309 309  Add APP EUI in the application:
310 310  
311 -[[image:image-20220525091022-19.png]]
364 +[[image:image-20220526140205-20.png]]
312 312  
366 +
313 313  == 4.4 Step4 ==
314 314  
315 315  Add APP KEY and DEV EUI:
316 316  
317 -[[image:image-20220525091128-20.png]]
371 +[[image:image-20220526140251-21.png]]
318 318  
373 +
319 319  = 5. TTN V3 integrated into MQTT server =
320 320  
321 321  == 5.1 Introduction ==
... ... @@ -323,6 +323,8 @@
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.
381 +
382 +
326 326  )))
327 327  )))
328 328  
... ... @@ -346,12 +346,12 @@
346 346  )))
347 347  )))
348 348  
349 -[[image:image-20220525091251-22.png]]
406 +[[image:image-20220526140347-22.png]]
350 350  
351 351  Fill in the username and password into MQTT.
352 352  
353 353  
354 -[[image:image-20220525091333-23.png]]
411 +[[image:image-20220526140420-23.png]]
355 355  
356 356  The Application Server publishes uplink traffic on the following topics:
357 357  
... ... @@ -374,7 +374,7 @@
374 374  )))
375 375  )))
376 376  
377 -[[image:image-20220525091430-24.png]]
434 +[[image:image-20220526140452-24.png]]
378 378  
379 379  (((
380 380  (((
... ... @@ -382,7 +382,7 @@
382 382  )))
383 383  )))
384 384  
385 -[[image:image-20220525091458-25.png]]
442 +[[image:image-20220526140708-25.png]]
386 386  
387 387  (((
388 388  (((
... ... @@ -402,7 +402,7 @@
402 402  )))
403 403  )))
404 404  
405 -[[image:image-20220525091618-27.png]]
462 +[[image:image-20220526140856-26.png]]
406 406  
407 407  (((
408 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:
... ... @@ -412,8 +412,9 @@
412 412  **Note**: Use this handy tool to convert hexadecimal to base64.
413 413  )))
414 414  
415 -[[image:image-20220525091702-28.png]]
472 +[[image:image-20220526140936-27.png]]
416 416  
474 +
417 417  == 5.3 Send Downlink message ==
418 418  
419 419  (((
... ... @@ -428,16 +428,18 @@
428 428  Downlink command:01 00 00 5A
429 429  )))
430 430  
431 -[[image:image-20220525091752-29.png]]
489 +[[image:image-20220526141021-28.png]]
432 432  
433 433  downlink
434 434  
493 +
435 435  After sending, you can view it in live data.
436 436  
437 -[[image:image-20220525091816-30.png]]
496 +[[image:image-20220526141052-29.png]]
438 438  
439 439  downlink
440 440  
500 +
441 441  (((
442 442  When downlink is successfully sent, the downlink information can be received on the serial port.
443 443  )))
... ... @@ -446,10 +446,11 @@
446 446  **Note**: If the downlink byte sent is longer, the number of bytes will be displayed.
447 447  )))
448 448  
449 -[[image:image-20220525091855-31.png]]
509 +[[image:image-20220526141116-30.png]]
450 450  
451 451  downlink
452 452  
513 +
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.
... ... @@ -474,10 +474,11 @@
474 474  )))
475 475  )))
476 476  
477 -[[image:image-20220525091925-32.png]]
538 +[[image:image-20220526141149-31.png]]
478 478  
479 479  downlink
480 480  
542 +
481 481  = 6. Request Remote Support =
482 482  
483 483  (((
... ... @@ -496,7 +496,7 @@
496 496  * If the device is sending join request to server?
497 497  * What frequency the device is sending?
498 498  
499 -[[image:image-20220525092012-33.png]]
561 +[[image:image-20220526141308-33.png]]
500 500  
501 501  Console Output from End device to see the transmit frequency
502 502  
... ... @@ -504,10 +504,12 @@
504 504  
505 505  * Is the device in OTAA mode or ABP mode? **AT+NJM=1** (OTAA mode), **AT+NJM=0** (ABP mode)
506 506  
507 -[[image:image-20220525092043-34.png]]
569 +[[image:image-20220526141612-36.png]]
508 508  
571 +
509 509  Console Output from End device to see the transmit frequency
510 510  
574 +
511 511  **2. Gateway packet traffic in gateway web or ssh. we can check:**
512 512  
513 513  * (((
... ... @@ -517,7 +517,7 @@
517 517  If the gateway gets the Join Accept message from server and transmit it via LoRa?
518 518  )))
519 519  
520 -[[image:image-20220525092124-35.png]]
584 +[[image:image-20220526141739-37.png]]
521 521  
522 522  Console Output from Gateway to see packets between end node and server.
523 523  
... ... @@ -534,15 +534,16 @@
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.
535 535  )))
536 536  
537 -[[image:image-20220525092157-36.png]]
601 +[[image:image-20220526141823-38.png||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]]
606 +[[image:image-20220526141917-39.png]]
543 543  
544 544  The Traffic for the End node in the server, use TTNv3 as example
545 545  
610 +
546 546  **4. Data Page in LoRaWAN server**
547 547  
548 548  (((
... ... @@ -550,7 +550,7 @@
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]]
618 +[[image:image-20220526141956-40.png]]
554 554  )))
555 555  )))
556 556  )))
... ... @@ -557,6 +557,7 @@
557 557  
558 558  The data for the end device set in server
559 559  
560 -[[image:image-20220525092430-40.png]]
561 561  
626 +[[image:image-20220526142033-41.png]]
627 +
562 562  Check if OTAA Keys match the keys in device
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

Applications

Navigation

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