Changes for page Notes for TTN

Last modified by Mengting Qiu on 2024/08/20 17:29
<
From version < 99.6 >
edited by Xiaoling
on 2022/05/30 14:13
To version < 64.1 >
edited by Xiaoling
on 2022/05/26 13:49
>
Change comment: Uploaded new attachment "image-20220526134919-5.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -3,7 +3,6 @@
3 3  {{toc/}}
4 4  
5 5  
6 -
7 7  = 1. The Things Network-V3 =
8 8  
9 9  == 1.1 Introduction ==
... ... @@ -16,8 +16,6 @@
16 16  
17 17  (((
18 18  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.
19 -
20 -
21 21  )))
22 22  
23 23  === 1.1.2 Login or crate an account ===
... ... @@ -28,8 +28,6 @@
28 28  
29 29  (((
30 30  Once you have an account,get started by following steps for adding Gateway,Device and Intergrations.
31 -
32 -
33 33  )))
34 34  
35 35  === 1.1.3 List the support products and Requirements ===
... ... @@ -36,7 +36,6 @@
36 36  
37 37  LoRaWAN Gateway model: Existing Gateway
38 38  
39 -
40 40  = 2. Gateway Registration for Semtech UDP =
41 41  
42 42  == 2.1 Primary LoRaWAN Server ==
... ... @@ -56,11 +56,10 @@
56 56  Choose Frequency Band
57 57  
58 58  
59 -[[image:image-20220526134919-5.png]]
53 +[[image:image-20220525093308-2.png]]
60 60  
61 61  Show Status
62 62  
63 -
64 64  == 2.2 Secondary LoRaWAN Server ==
65 65  
66 66  === 2.2.1 Introduction ===
... ... @@ -67,7 +67,6 @@
67 67  
68 68  The Dragino gateway has supports the Secondary server settings.
69 69  
70 -
71 71  === 2.2.2 Below list the support products and Requirements: ===
72 72  
73 73  (((
... ... @@ -78,30 +78,26 @@
78 78  2. Firmware version since :[[lgw~~-~~-build-v5.4.1644658774>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LIG16/Firmware/Release/]]
79 79  )))
80 80  
81 -
82 82  === 2.2.3 Example ===
83 83  
84 -The following takes Helium as a Secondary LoRaWAN server as an example
75 +The following takes Helium as a Secondary LoRaWAN server as an example,
85 85  
86 -
87 87  === 2.2.4 Step 1: Download and Install the helium gateway-rs ===
88 88  
89 89  The users is needing to download and install the helium gateway-rs then click the button of Save&Apply
90 90  
91 -[[image:image-20220526135049-6.png]]
81 +[[image:image-20220525093626-7.png]]
92 92  
93 93  Download and Install gateway-rs
94 94  
95 -
96 96  === 2.2.5 Step 2: Back to Semtech UDP page ===
97 97  
98 98  Back to the page of Semtech UDP check the secondary server settings and click the button of Save&Apply
99 99  
100 -​​​​[[image:image-20220526135125-7.png]]
89 +​​​​[[image:image-20220525093929-1.png]]
101 101  
102 102  Configuration of helium
103 103  
104 -
105 105  = 3. Gateway Registration for Basics Station =
106 106  
107 107  == 3.1 Introduction ==
... ... @@ -133,8 +133,6 @@
133 133  (((
134 134  (((
135 135  A gateway that can access the internet normally
136 -
137 -
138 138  )))
139 139  )))
140 140  
... ... @@ -158,45 +158,41 @@
158 158  )))
159 159  )))
160 160  
161 -[[image:image-20220526135316-8.png]]
147 +[[image:image-20220525094010-2.png]]
162 162  
163 163  Add Gateway
164 164  
165 -
166 166  == 3.3 Step 2. Create the API key ==
167 167  
168 168  user need to create the CUPS API key and LNS API key.
169 169  
170 -[[image:image-20220526135349-9.png]]
155 +[[image:image-20220525094115-3.png]]
171 171  
172 172  Create CUPS API key
173 173  
174 174  
175 -[[image:image-20220526135428-10.png]]
160 +[[image:image-20220525094146-4.png]]
176 176  
177 177  Create LNS API key
178 178  
179 179  (% style="color:red" %)**Note : Please copy the API key.**
180 180  
181 -
182 182  == 3.4 Step 3. Update the gateway setting ==
183 183  
184 184  In the LoRa Basics Station LNS Authentication Key field, paste the API key you generated in the previous step.
185 185  
186 -[[image:image-20220526135528-11.png]]
170 +[[image:image-20220525094220-5.png]]
187 187  
188 188  paste the API key
189 189  
190 -
191 191  == 3.5 Step 4. Access the gateway GUI ==
192 192  
193 193  User need to update the API key and install the Certificate
194 194  
195 -[[image:image-20220526135601-12.png]]
178 +[[image:image-20220525094257-6.png]]
196 196  
197 197  Access the gateway GUI
198 198  
199 -
200 200  == 3.6 Step 5. Configure Station ==
201 201  
202 202  User need to input Server URI, Server CUPS Key and LNS Key, as well as install CUPS certificate.
... ... @@ -211,17 +211,14 @@
211 211   CUPS certificate  ~-~-> Server CA(user can use the button to install the certificate by default)
212 212  )))
213 213  
214 -[[image:image-20220526135654-13.png]]
196 +[[image:image-20220525094329-7.png]]
215 215  
216 216  Congfigure Station
217 217  
218 -
219 219  == 3.7 Start Station ==
220 220  
221 221  (((
222 222  When the user has finished the configuration,Please click Sace&Apply to start station to connect The Things Network.
223 -
224 -
225 225  )))
226 226  
227 227  == 3.8 Siccessful Connection ==
... ... @@ -228,27 +228,24 @@
228 228  
229 229  If user completes the above steps,which will see live date in the TTN.
230 230  
231 -[[image:image-20220526135734-14.png]]
210 +[[image:image-20220525094409-8.png]]
232 232  
233 233  Station live date
234 234  
235 -
236 236  == 3.9 Trouble Shooting ==
237 237  
238 238  User can check the station log in the logread/system log page.
239 239  
240 -[[image:image-20220526135845-15.png]]
218 +[[image:image-20220525090622-14.png]]
241 241  
242 242  Station Log
243 243  
244 -
245 245  and recode the station log in the system/Recode log page.
246 246  
247 -[[image:image-20220526135940-16.png]]
224 +[[image:image-20220525090705-15.png]]
248 248  
249 249  Recore Log
250 250  
251 -
252 252  = 4. Configure node connection to TTNv3 =
253 253  
254 254  (((
... ... @@ -266,8 +266,6 @@
266 266  (((
267 267  (((
268 268  We take LES01 as an example.
269 -
270 -
271 271  )))
272 272  )))
273 273  
... ... @@ -291,11 +291,10 @@
291 291  )))
292 292  )))
293 293  
294 -[[image:image-20220526140015-17.png]]
268 +[[image:image-20220525090739-16.png]]
295 295  
296 -[[image:image-20220526140044-18.png]]
270 +[[image:image-20220525090833-17.png]]
297 297  
298 -
299 299  == 4.2 Step2 ==
300 300  
301 301  (((
... ... @@ -304,23 +304,20 @@
304 304  )))
305 305  )))
306 306  
307 -[[image:image-20220526140132-19.png]]
280 +[[image:image-20220525090920-18.png]]
308 308  
309 -
310 310  == 4.3 Step3 ==
311 311  
312 312  Add APP EUI in the application:
313 313  
314 -[[image:image-20220526140205-20.png]]
286 +[[image:image-20220525091022-19.png]]
315 315  
316 -
317 317  == 4.4 Step4 ==
318 318  
319 319  Add APP KEY and DEV EUI:
320 320  
321 -[[image:image-20220526140251-21.png]]
292 +[[image:image-20220525091128-20.png]]
322 322  
323 -
324 324  = 5. TTN V3 integrated into MQTT server =
325 325  
326 326  == 5.1 Introduction ==
... ... @@ -328,8 +328,6 @@
328 328  (((
329 329  (((
330 330  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.
331 -
332 -
333 333  )))
334 334  )))
335 335  
... ... @@ -353,12 +353,12 @@
353 353  )))
354 354  )))
355 355  
356 -[[image:image-20220526140347-22.png]]
324 +[[image:image-20220525091251-22.png]]
357 357  
358 358  Fill in the username and password into MQTT.
359 359  
360 360  
361 -[[image:image-20220526140420-23.png]]
329 +[[image:image-20220525091333-23.png]]
362 362  
363 363  The Application Server publishes uplink traffic on the following topics:
364 364  
... ... @@ -381,7 +381,7 @@
381 381  )))
382 382  )))
383 383  
384 -[[image:image-20220526140452-24.png]]
352 +[[image:image-20220525091430-24.png]]
385 385  
386 386  (((
387 387  (((
... ... @@ -389,7 +389,7 @@
389 389  )))
390 390  )))
391 391  
392 -[[image:image-20220526140708-25.png]]
360 +[[image:image-20220525091458-25.png]]
393 393  
394 394  (((
395 395  (((
... ... @@ -409,7 +409,7 @@
409 409  )))
410 410  )))
411 411  
412 -[[image:image-20220526140856-26.png]]
380 +[[image:image-20220525091618-27.png]]
413 413  
414 414  (((
415 415  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:
... ... @@ -419,9 +419,8 @@
419 419  **Note**: Use this handy tool to convert hexadecimal to base64.
420 420  )))
421 421  
422 -[[image:image-20220526140936-27.png]]
390 +[[image:image-20220525091702-28.png]]
423 423  
424 -
425 425  == 5.3 Send Downlink message ==
426 426  
427 427  (((
... ... @@ -436,18 +436,16 @@
436 436  Downlink command:01 00 00 5A
437 437  )))
438 438  
439 -[[image:image-20220526141021-28.png]]
406 +[[image:image-20220525091752-29.png]]
440 440  
441 441  downlink
442 442  
443 -
444 444  After sending, you can view it in live data.
445 445  
446 -[[image:image-20220526141052-29.png]]
412 +[[image:image-20220525091816-30.png]]
447 447  
448 448  downlink
449 449  
450 -
451 451  (((
452 452  When downlink is successfully sent, the downlink information can be received on the serial port.
453 453  )))
... ... @@ -456,11 +456,10 @@
456 456  **Note**: If the downlink byte sent is longer, the number of bytes will be displayed.
457 457  )))
458 458  
459 -[[image:image-20220526141116-30.png]]
424 +[[image:image-20220525091855-31.png]]
460 460  
461 461  downlink
462 462  
463 -
464 464  (((
465 465  (((
466 466  If you want to get a successful reply to send downlink in TTN v3. You need to set the response level.
... ... @@ -485,11 +485,10 @@
485 485  )))
486 486  )))
487 487  
488 -[[image:image-20220526141149-31.png]]
452 +[[image:image-20220525091925-32.png]]
489 489  
490 490  downlink
491 491  
492 -
493 493  = 6. Request Remote Support =
494 494  
495 495  (((
... ... @@ -508,7 +508,7 @@
508 508  * If the device is sending join request to server?
509 509  * What frequency the device is sending?
510 510  
511 -[[image:image-20220526141308-33.png]]
474 +[[image:image-20220525092012-33.png]]
512 512  
513 513  Console Output from End device to see the transmit frequency
514 514  
... ... @@ -516,12 +516,10 @@
516 516  
517 517  * Is the device in OTAA mode or ABP mode? **AT+NJM=1** (OTAA mode), **AT+NJM=0** (ABP mode)
518 518  
519 -[[image:image-20220526141612-36.png]]
482 +[[image:image-20220525092043-34.png]]
520 520  
521 -
522 522  Console Output from End device to see the transmit frequency
523 523  
524 -
525 525  **2. Gateway packet traffic in gateway web or ssh. we can check:**
526 526  
527 527  * (((
... ... @@ -531,7 +531,7 @@
531 531  If the gateway gets the Join Accept message from server and transmit it via LoRa?
532 532  )))
533 533  
534 -[[image:image-20220526141739-37.png]]
495 +[[image:image-20220525092124-35.png]]
535 535  
536 536  Console Output from Gateway to see packets between end node and server.
537 537  
... ... @@ -548,16 +548,15 @@
548 548  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.
549 549  )))
550 550  
551 -[[image:image-20220526141823-38.png||height="501" width="1144"]]
512 +[[image:image-20220525092157-36.png]]
552 552  
553 553  The Traffic for the End node in the server, use TTNv3 as example
554 554  
555 555  
556 -[[image:image-20220526141917-39.png]]
517 +[[image:image-20220525092231-37.png]]
557 557  
558 558  The Traffic for the End node in the server, use TTNv3 as example
559 559  
560 -
561 561  **4. Data Page in LoRaWAN server**
562 562  
563 563  (((
... ... @@ -565,7 +565,7 @@
565 565  (((
566 566  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.
567 567  
568 -[[image:image-20220526141956-40.png]]
528 +[[image:image-20220525092546-1.png]]
569 569  )))
570 570  )))
571 571  )))
... ... @@ -572,7 +572,6 @@
572 572  
573 573  The data for the end device set in server
574 574  
535 +[[image:image-20220525092430-40.png]]
575 575  
576 -[[image:image-20220526142033-41.png]]
577 -
578 578  Check if OTAA Keys match the keys in device
image-20220526135049-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -79.8 KB
Content
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