Changes for page Notes for TTN

Last modified by Mengting Qiu on 2024/08/20 17:29
<
From version < 99.10 >
edited by Xiaoling
on 2022/07/25 08:46
To version < 65.1 >
edited by Xiaoling
on 2022/05/26 13:50
>
Change comment: Uploaded new attachment "image-20220526135049-6.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -1,18 +1,14 @@
1 -**~ Table of Contents：**
1 +**~ Contents：**
2 2  
3 3  {{toc/}}
4 4  
5 5  
6 -
7 7  = 1. The Things Network-V3 =
8 8  
8 +== 1.1 Introduction ==
9 9  
10 -== 1.1  Introduction ==
10 +=== 1.1.1 What is The Things Network ===
11 11  
12 -
13 -=== 1.1.1  What is The Things Network ===
14 -
15 -
16 16  (((
17 17  The Things Network is a global collaborative Internet of Things ecosystem that creates networks, devices and solutions using LoRaWAN.
18 18  )))
... ... @@ -19,14 +19,10 @@
19 19  
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 -
23 -
24 -
25 25  )))
26 26  
27 -=== 1.1.2  Login or crate an account ===
20 +=== 1.1.2 Login or crate an account ===
28 28  
29 -
30 30  (((
31 31  [[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.
32 32  )))
... ... @@ -33,60 +33,43 @@
33 33  
34 34  (((
35 35  Once you have an account,get started by following steps for adding Gateway,Device and Intergrations.
36 -
37 -
38 -
39 39  )))
40 40  
41 -=== 1.1.3  List the support products and Requirements ===
30 +=== 1.1.3 List the support products and Requirements ===
42 42  
43 -
44 44  LoRaWAN Gateway model: Existing Gateway
45 45  
34 += 2. Gateway Registration for Semtech UDP =
46 46  
36 +== 2.1 Primary LoRaWAN Server ==
47 47  
48 -= 2.  Gateway Registration for Semtech UDP =
49 -
50 -
51 -== 2.1  Primary LoRaWAN Server ==
52 -
53 -
54 54  [[image:image-20220526134633-2.png||height="616" width="1323"]]
55 55  
56 56  Register Gateway
57 57  
58 58  
59 -
60 60  [[image:image-20220526134826-4.png]]
61 61  
62 62  Put Gateway ID
63 63  
64 64  
65 -
66 66  [[image:image-20220526134759-3.png]]
67 67  
68 68  Choose Frequency Band
69 69  
70 70  
71 -
72 72  [[image:image-20220526134919-5.png]]
73 73  
74 74  Show Status
75 75  
57 +== 2.2 Secondary LoRaWAN Server ==
76 76  
59 +=== 2.2.1 Introduction ===
77 77  
78 -== 2.2  Secondary LoRaWAN Server ==
79 -
80 -
81 -=== 2.2.1  Introduction ===
82 -
83 -
84 84  The Dragino gateway has supports the Secondary server settings.
85 85  
63 +=== 2.2.2 Below list the support products and Requirements: ===
86 86  
87 -=== 2.2.2  Below list the support products and Requirements: ===
88 -
89 -
90 90  (((
91 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]]
92 92  )))
... ... @@ -95,43 +95,30 @@
95 95  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  
73 +=== 2.2.3 Example ===
98 98  
75 +The following takes Helium as a Secondary LoRaWAN server as an example,
99 99  
100 -=== 2.2.3  Example ===
77 +=== 2.2.4 Step 1: Download and Install the helium gateway-rs ===
101 101  
102 -
103 -The following takes Helium as a Secondary LoRaWAN server as an example
104 -
105 -
106 -
107 -=== 2.2.4  Step 1: Download and Install the helium gateway-rs ===
108 -
109 -
110 110  The users is needing to download and install the helium gateway-rs then click the button of Save&Apply
111 111  
112 -[[image:image-20220526135049-6.png]]
81 +[[image:image-20220525093626-7.png]]
113 113  
114 114  Download and Install gateway-rs
115 115  
85 +=== 2.2.5 Step 2: Back to Semtech UDP page ===
116 116  
117 -
118 -=== 2.2.5  Step 2: Back to Semtech UDP page ===
119 -
120 -
121 121  Back to the page of Semtech UDP check the secondary server settings and click the button of Save&Apply
122 122  
123 -​​​​[[image:image-20220526135125-7.png]]
89 +​​​​[[image:image-20220525093929-1.png]]
124 124  
125 125  Configuration of helium
126 126  
93 += 3. Gateway Registration for Basics Station =
127 127  
95 +== 3.1 Introduction ==
128 128  
129 -= 3.  Gateway Registration for Basics Station =
130 -
131 -
132 -== 3.1  Introduction ==
133 -
134 -
135 135  (((
136 136  (((
137 137  The LoRa Basics™ Station protocol simplifies management of large scale LoRaWAN networks. LoRa Basics™ Station is the preferred way of connecting Gateways to The Things Stack. [[The LoRa Basics Station doc>>url:https://www.thethingsindustries.com/docs/gateways/lora-basics-station/]]
... ... @@ -159,8 +159,6 @@
159 159  (((
160 160  (((
161 161  A gateway that can access the internet normally
162 -
163 -
164 164  )))
165 165  )))
166 166  
... ... @@ -184,45 +184,41 @@
184 184  )))
185 185  )))
186 186  
187 -[[image:image-20220526135316-8.png]]
147 +[[image:image-20220525094010-2.png]]
188 188  
189 189  Add Gateway
190 190  
191 -
192 192  == 3.3 Step 2. Create the API key ==
193 193  
194 194  user need to create the CUPS API key and LNS API key.
195 195  
196 -[[image:image-20220526135349-9.png]]
155 +[[image:image-20220525094115-3.png]]
197 197  
198 198  Create CUPS API key
199 199  
200 200  
201 -[[image:image-20220526135428-10.png]]
160 +[[image:image-20220525094146-4.png]]
202 202  
203 203  Create LNS API key
204 204  
205 205  (% style="color:red" %)**Note : Please copy the API key.**
206 206  
207 -
208 208  == 3.4 Step 3. Update the gateway setting ==
209 209  
210 210  In the LoRa Basics Station LNS Authentication Key field, paste the API key you generated in the previous step.
211 211  
212 -[[image:image-20220526135528-11.png]]
170 +[[image:image-20220525094220-5.png]]
213 213  
214 214  paste the API key
215 215  
216 -
217 217  == 3.5 Step 4. Access the gateway GUI ==
218 218  
219 219  User need to update the API key and install the Certificate
220 220  
221 -[[image:image-20220526135601-12.png]]
178 +[[image:image-20220525094257-6.png]]
222 222  
223 223  Access the gateway GUI
224 224  
225 -
226 226  == 3.6 Step 5. Configure Station ==
227 227  
228 228  User need to input Server URI, Server CUPS Key and LNS Key, as well as install CUPS certificate.
... ... @@ -237,17 +237,14 @@
237 237   CUPS certificate  ~-~-> Server CA(user can use the button to install the certificate by default)
238 238  )))
239 239  
240 -[[image:image-20220526135654-13.png]]
196 +[[image:image-20220525094329-7.png]]
241 241  
242 242  Congfigure Station
243 243  
244 -
245 245  == 3.7 Start Station ==
246 246  
247 247  (((
248 248  When the user has finished the configuration,Please click Sace&Apply to start station to connect The Things Network.
249 -
250 -
251 251  )))
252 252  
253 253  == 3.8 Siccessful Connection ==
... ... @@ -254,27 +254,24 @@
254 254  
255 255  If user completes the above steps,which will see live date in the TTN.
256 256  
257 -[[image:image-20220526135734-14.png]]
210 +[[image:image-20220525094409-8.png]]
258 258  
259 259  Station live date
260 260  
261 -
262 262  == 3.9 Trouble Shooting ==
263 263  
264 264  User can check the station log in the logread/system log page.
265 265  
266 -[[image:image-20220526135845-15.png]]
218 +[[image:image-20220525090622-14.png]]
267 267  
268 268  Station Log
269 269  
270 -
271 271  and recode the station log in the system/Recode log page.
272 272  
273 -[[image:image-20220526135940-16.png]]
224 +[[image:image-20220525090705-15.png]]
274 274  
275 275  Recore Log
276 276  
277 -
278 278  = 4. Configure node connection to TTNv3 =
279 279  
280 280  (((
... ... @@ -292,8 +292,6 @@
292 292  (((
293 293  (((
294 294  We take LES01 as an example.
295 -
296 -
297 297  )))
298 298  )))
299 299  
... ... @@ -317,11 +317,10 @@
317 317  )))
318 318  )))
319 319  
320 -[[image:image-20220526140015-17.png]]
268 +[[image:image-20220525090739-16.png]]
321 321  
322 -[[image:image-20220526140044-18.png]]
270 +[[image:image-20220525090833-17.png]]
323 323  
324 -
325 325  == 4.2 Step2 ==
326 326  
327 327  (((
... ... @@ -330,23 +330,20 @@
330 330  )))
331 331  )))
332 332  
333 -[[image:image-20220526140132-19.png]]
280 +[[image:image-20220525090920-18.png]]
334 334  
335 -
336 336  == 4.3 Step3 ==
337 337  
338 338  Add APP EUI in the application:
339 339  
340 -[[image:image-20220526140205-20.png]]
286 +[[image:image-20220525091022-19.png]]
341 341  
342 -
343 343  == 4.4 Step4 ==
344 344  
345 345  Add APP KEY and DEV EUI:
346 346  
347 -[[image:image-20220526140251-21.png]]
292 +[[image:image-20220525091128-20.png]]
348 348  
349 -
350 350  = 5. TTN V3 integrated into MQTT server =
351 351  
352 352  == 5.1 Introduction ==
... ... @@ -354,8 +354,6 @@
354 354  (((
355 355  (((
356 356  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.
357 -
358 -
359 359  )))
360 360  )))
361 361  
... ... @@ -379,12 +379,12 @@
379 379  )))
380 380  )))
381 381  
382 -[[image:image-20220526140347-22.png]]
324 +[[image:image-20220525091251-22.png]]
383 383  
384 384  Fill in the username and password into MQTT.
385 385  
386 386  
387 -[[image:image-20220526140420-23.png]]
329 +[[image:image-20220525091333-23.png]]
388 388  
389 389  The Application Server publishes uplink traffic on the following topics:
390 390  
... ... @@ -407,7 +407,7 @@
407 407  )))
408 408  )))
409 409  
410 -[[image:image-20220526140452-24.png]]
352 +[[image:image-20220525091430-24.png]]
411 411  
412 412  (((
413 413  (((
... ... @@ -415,7 +415,7 @@
415 415  )))
416 416  )))
417 417  
418 -[[image:image-20220526140708-25.png]]
360 +[[image:image-20220525091458-25.png]]
419 419  
420 420  (((
421 421  (((
... ... @@ -435,7 +435,7 @@
435 435  )))
436 436  )))
437 437  
438 -[[image:image-20220526140856-26.png]]
380 +[[image:image-20220525091618-27.png]]
439 439  
440 440  (((
441 441  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:
... ... @@ -445,9 +445,8 @@
445 445  **Note**: Use this handy tool to convert hexadecimal to base64.
446 446  )))
447 447  
448 -[[image:image-20220526140936-27.png]]
390 +[[image:image-20220525091702-28.png]]
449 449  
450 -
451 451  == 5.3 Send Downlink message ==
452 452  
453 453  (((
... ... @@ -462,18 +462,16 @@
462 462  Downlink command:01 00 00 5A
463 463  )))
464 464  
465 -[[image:image-20220526141021-28.png]]
406 +[[image:image-20220525091752-29.png]]
466 466  
467 467  downlink
468 468  
469 -
470 470  After sending, you can view it in live data.
471 471  
472 -[[image:image-20220526141052-29.png]]
412 +[[image:image-20220525091816-30.png]]
473 473  
474 474  downlink
475 475  
476 -
477 477  (((
478 478  When downlink is successfully sent, the downlink information can be received on the serial port.
479 479  )))
... ... @@ -482,11 +482,10 @@
482 482  **Note**: If the downlink byte sent is longer, the number of bytes will be displayed.
483 483  )))
484 484  
485 -[[image:image-20220526141116-30.png]]
424 +[[image:image-20220525091855-31.png]]
486 486  
487 487  downlink
488 488  
489 -
490 490  (((
491 491  (((
492 492  If you want to get a successful reply to send downlink in TTN v3. You need to set the response level.
... ... @@ -511,11 +511,10 @@
511 511  )))
512 512  )))
513 513  
514 -[[image:image-20220526141149-31.png]]
452 +[[image:image-20220525091925-32.png]]
515 515  
516 516  downlink
517 517  
518 -
519 519  = 6. Request Remote Support =
520 520  
521 521  (((
... ... @@ -534,7 +534,7 @@
534 534  * If the device is sending join request to server?
535 535  * What frequency the device is sending?
536 536  
537 -[[image:image-20220526141308-33.png]]
474 +[[image:image-20220525092012-33.png]]
538 538  
539 539  Console Output from End device to see the transmit frequency
540 540  
... ... @@ -542,12 +542,10 @@
542 542  
543 543  * Is the device in OTAA mode or ABP mode? **AT+NJM=1** (OTAA mode), **AT+NJM=0** (ABP mode)
544 544  
545 -[[image:image-20220526141612-36.png]]
482 +[[image:image-20220525092043-34.png]]
546 546  
547 -
548 548  Console Output from End device to see the transmit frequency
549 549  
550 -
551 551  **2. Gateway packet traffic in gateway web or ssh. we can check:**
552 552  
553 553  * (((
... ... @@ -557,7 +557,7 @@
557 557  If the gateway gets the Join Accept message from server and transmit it via LoRa?
558 558  )))
559 559  
560 -[[image:image-20220526141739-37.png]]
495 +[[image:image-20220525092124-35.png]]
561 561  
562 562  Console Output from Gateway to see packets between end node and server.
563 563  
... ... @@ -574,16 +574,15 @@
574 574  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.
575 575  )))
576 576  
577 -[[image:image-20220526141823-38.png||height="501" width="1144"]]
512 +[[image:image-20220525092157-36.png]]
578 578  
579 579  The Traffic for the End node in the server, use TTNv3 as example
580 580  
581 581  
582 -[[image:image-20220526141917-39.png]]
517 +[[image:image-20220525092231-37.png]]
583 583  
584 584  The Traffic for the End node in the server, use TTNv3 as example
585 585  
586 -
587 587  **4. Data Page in LoRaWAN server**
588 588  
589 589  (((
... ... @@ -591,7 +591,7 @@
591 591  (((
592 592  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.
593 593  
594 -[[image:image-20220526141956-40.png]]
528 +[[image:image-20220525092546-1.png]]
595 595  )))
596 596  )))
597 597  )))
... ... @@ -598,7 +598,6 @@
598 598  
599 599  The data for the end device set in server
600 600  
535 +[[image:image-20220525092430-40.png]]
601 601  
602 -[[image:image-20220526142033-41.png]]
603 -
604 604  Check if OTAA Keys match the keys in device
image-20220526135125-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -85.4 KB
Content
image-20220526135316-8.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -85.1 KB
Content
image-20220526135349-9.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -69.4 KB
Content
image-20220526135428-10.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -68.6 KB
Content
image-20220526135528-11.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -104.4 KB
Content
image-20220526135601-12.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -115.2 KB
Content
image-20220526135654-13.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -123.6 KB
Content
image-20220526135734-14.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -122.5 KB
Content
image-20220526135845-15.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -159.3 KB
Content
image-20220526135940-16.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -32.9 KB
Content
image-20220526140015-17.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -24.4 KB
Content
image-20220526140044-18.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -42.0 KB
Content
image-20220526140132-19.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -60.2 KB
Content
image-20220526140205-20.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -77.6 KB
Content
image-20220526140251-21.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -67.9 KB
Content
image-20220526140347-22.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -63.0 KB
Content
image-20220526140420-23.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -77.4 KB
Content
image-20220526140452-24.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -32.4 KB
Content
image-20220526140708-25.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -827.1 KB
Content
image-20220526140856-26.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -114.9 KB
Content
image-20220526140936-27.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -103.1 KB
Content
image-20220526141021-28.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -74.8 KB
Content
image-20220526141052-29.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -84.1 KB
Content
image-20220526141116-30.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -10.1 KB
Content
image-20220526141149-31.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -59.0 KB
Content
image-20220526141236-32.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -114.0 KB
Content
image-20220526141308-33.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -90.1 KB
Content
image-20220526141350-34.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -78.7 KB
Content
image-20220526141612-36.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -78.2 KB
Content
image-20220526141739-37.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -288.0 KB
Content
image-20220526141823-38.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -197.3 KB
Content
image-20220526141917-39.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -154.2 KB
Content
image-20220526141956-40.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -163.5 KB
Content
image-20220526142033-41.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -25.2 KB
Content

Applications

Navigation

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