Changes for page Notes for TTN

Last modified by Mengting Qiu on 2024/08/20 17:29
<
From version < 99.8 >
edited by Xiaoling
on 2022/07/25 08:39
To version < 99.17 >
edited by Xiaoling
on 2022/07/25 09:19
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -6,10 +6,13 @@
6 6  
7 7  = 1. The Things Network-V3 =
8 8  
9 -== 1.1 Introduction ==
10 10  
11 -=== 1.1.1 What is The Things Network ===
10 +== 1.1  Introduction ==
12 12  
12 +
13 +=== 1.1.1  What is The Things Network ===
14 +
15 +
13 13  (((
14 14  The Things Network is a global collaborative Internet of Things ecosystem that creates networks, devices and solutions using LoRaWAN.
15 15  )))
... ... @@ -17,11 +17,13 @@
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 19  
23 +
20 20  
21 21  )))
22 22  
23 -=== 1.1.2 Login or crate an account ===
27 +=== 1.1.2  Login or crate an account ===
24 24  
29 +
25 25  (((
26 26  [[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.
27 27  )))
... ... @@ -29,23 +29,29 @@
29 29  (((
30 30  Once you have an account,get started by following steps for adding Gateway,Device and Intergrations.
31 31  
37 +
32 32  
33 33  )))
34 34  
35 -=== 1.1.3 List the support products and Requirements ===
41 +=== 1.1.3  List the support products and Requirements ===
36 36  
43 +
37 37  LoRaWAN Gateway model: Existing Gateway
38 38  
39 39  
40 -= 2. Gateway Registration for Semtech UDP =
41 41  
42 -== 2.1 Primary LoRaWAN Server ==
48 += 2.  Gateway Registration for Semtech UDP =
43 43  
50 +
51 +== 2.1  Primary LoRaWAN Server ==
52 +
53 +
44 44  [[image:image-20220526134633-2.png||height="616" width="1323"]]
45 45  
46 46  Register Gateway
47 47  
48 48  
59 +
49 49  [[image:image-20220526134826-4.png]]
50 50  
51 51  Put Gateway ID
... ... @@ -57,45 +57,58 @@
57 57  Choose Frequency Band
58 58  
59 59  
71 +
60 60  [[image:image-20220526134919-5.png]]
61 61  
62 62  Show Status
63 63  
64 64  
65 -== 2.2 Secondary LoRaWAN Server ==
66 66  
67 -=== 2.2.1 Introduction ===
78 +== 2.2  Secondary LoRaWAN Server ==
68 68  
80 +
81 +=== 2.2.1  Introduction ===
82 +
83 +
69 69  The Dragino gateway has supports the Secondary server settings.
70 70  
71 71  
72 -=== 2.2.2 Below list the support products and Requirements: ===
73 73  
88 +=== 2.2.2  Below list the support products and Requirements: ===
89 +
90 +
74 74  (((
75 -~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 +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]]
76 76  )))
77 77  
78 78  (((
79 -2. Firmware version since :[[lgw~~-~~-build-v5.4.1644658774>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LIG16/Firmware/Release/]]
96 +2.  Firmware version since :  [[lgw~~-~~-build-v5.4.1644658774>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LIG16/Firmware/Release/]]
80 80  )))
81 81  
82 82  
83 -=== 2.2.3 Example ===
84 84  
101 +=== 2.2.3  Example ===
102 +
103 +
85 85  The following takes Helium as a Secondary LoRaWAN server as an example
86 86  
87 87  
88 -=== 2.2.4 Step 1: Download and Install the helium gateway-rs ===
89 89  
108 +=== 2.2.4  Step 1: Download and Install the helium gateway-rs ===
109 +
110 +
90 90  The users is needing to download and install the helium gateway-rs then click the button of Save&Apply
91 91  
113 +
92 92  [[image:image-20220526135049-6.png]]
93 93  
94 94  Download and Install gateway-rs
95 95  
96 96  
97 -=== 2.2.5 Step 2: Back to Semtech UDP page ===
98 98  
120 +=== 2.2.5  Step 2: Back to Semtech UDP page ===
121 +
122 +
99 99  Back to the page of Semtech UDP check the secondary server settings and click the button of Save&Apply
100 100  
101 101  ​​​​[[image:image-20220526135125-7.png]]
... ... @@ -103,32 +103,41 @@
103 103  Configuration of helium
104 104  
105 105  
106 -= 3. Gateway Registration for Basics Station =
107 107  
108 -== 3.1 Introduction ==
131 += 3.  Gateway Registration for Basics Station =
109 109  
133 +
134 +== 3.1  Introduction ==
135 +
136 +
110 110  (((
111 111  (((
112 112  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/]]
140 +
141 +
113 113  )))
114 114  )))
115 115  
116 116  (((
117 -**Below list the support products and Requirements:**
146 +(% style="color:blue" %)**Below list the support products and Requirements:**
118 118  )))
119 119  
120 120  (((
121 121  (((
122 - ~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]]
151 +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]]
123 123  )))
124 124  
125 125  (((
126 126   2. Firmware version since :[[lgw~~-~~-build-v5.4.1640315898>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/]]
156 +
157 +
158 +
159 +
127 127  )))
128 128  )))
129 129  
130 130  (((
131 -**What do you need to prepare**
164 +(% style="color:blue" %)**What do you need to prepare**
132 132  )))
133 133  
134 134  (((
... ... @@ -135,12 +135,14 @@
135 135  (((
136 136  A gateway that can access the internet normally
137 137  
171 +
138 138  
139 139  )))
140 140  )))
141 141  
142 -== 3.2 Step 1. Add Gateway ==
176 +== 3.2  Step 1: Add Gateway ==
143 143  
178 +
144 144  (((
145 145  (((
146 146  The example for **EU**
... ... @@ -156,6 +156,8 @@
156 156  (((
157 157  (((
158 158  Following picture is the successful added.
194 +
195 +
159 159  )))
160 160  )))
161 161  
... ... @@ -164,52 +164,66 @@
164 164  Add Gateway
165 165  
166 166  
167 -== 3.3 Step 2. Create the API key ==
168 168  
205 +== 3.3  Step 2: Create the API key ==
206 +
207 +
169 169  user need to create the CUPS API key and LNS API key.
170 170  
210 +
171 171  [[image:image-20220526135349-9.png]]
172 172  
173 173  Create CUPS API key
174 174  
175 175  
216 +
176 176  [[image:image-20220526135428-10.png]]
177 177  
178 178  Create LNS API key
179 179  
221 +
180 180  (% style="color:red" %)**Note : Please copy the API key.**
181 181  
182 182  
183 -== 3.4 Step 3. Update the gateway setting ==
184 184  
226 +== 3.4  Step 3: Update the gateway setting ==
227 +
228 +
185 185  In the LoRa Basics Station LNS Authentication Key field, paste the API key you generated in the previous step.
186 186  
231 +
187 187  [[image:image-20220526135528-11.png]]
188 188  
189 189  paste the API key
190 190  
191 191  
192 -== 3.5 Step 4. Access the gateway GUI ==
193 193  
238 +== 3.5  Step 4: Access the gateway GUI ==
239 +
240 +
194 194  User need to update the API key and install the Certificate
195 195  
243 +
196 196  [[image:image-20220526135601-12.png]]
197 197  
198 198  Access the gateway GUI
199 199  
200 200  
201 -== 3.6 Step 5. Configure Station ==
202 202  
250 +== 3.6  Step 5: Configure Station ==
251 +
252 +
203 203  User need to input Server URI, Server CUPS Key and LNS Key, as well as install CUPS certificate.
204 204  
205 -**just to clarify.**
206 206  
256 +(% style="color:blue" %)**just to clarify:**
257 +
207 207  (% class="box" %)
208 208  (((
209 - CUPS Server URI  ~-~-> Server Adress
210 - CUPS Authorization Key         ~-~-> Server CUPS API Key
211 - LNS Authorization Key  ~-~-> Server LNS API Key
212 - CUPS certificate  ~-~-> Server CA(user can use the button to install the certificate by default)
260 + CUPS Server URI  ~-~->  Server Adress
261 + CUPS Authorization Key         ~-~->  Server CUPS API Key
262 + LNS Authorization Key  ~-~->  Server LNS API Key
263 + CUPS certificate  ~-~->  Server CA(user can use the button to install the certificate by default)
213 213  )))
214 214  
215 215  [[image:image-20220526135654-13.png]]
... ... @@ -217,32 +217,41 @@
217 217  Congfigure Station
218 218  
219 219  
220 -== 3.7 Start Station ==
221 221  
272 +== 3.7  Start Station ==
273 +
274 +
222 222  (((
223 223  When the user has finished the configuration,Please click Sace&Apply to start station to connect The Things Network.
224 224  
278 +
225 225  
226 226  )))
227 227  
228 -== 3.8 Siccessful Connection ==
282 +== 3.8  Siccessful Connection ==
229 229  
284 +
230 230  If user completes the above steps,which will see live date in the TTN.
231 231  
287 +
232 232  [[image:image-20220526135734-14.png]]
233 233  
234 234  Station live date
235 235  
236 236  
237 -== 3.9 Trouble Shooting ==
238 238  
294 +== 3.9  Trouble Shooting ==
295 +
296 +
239 239  User can check the station log in the logread/system log page.
240 240  
299 +
241 241  [[image:image-20220526135845-15.png]]
242 242  
243 243  Station Log
244 244  
245 245  
305 +
246 246  and recode the station log in the system/Recode log page.
247 247  
248 248  [[image:image-20220526135940-16.png]]
... ... @@ -250,8 +250,10 @@
250 250  Recore Log
251 251  
252 252  
253 -= 4. Configure node connection to TTNv3 =
254 254  
314 += 4.  Configure node connection to TTNv3 =
315 +
316 +
255 255  (((
256 256  (((
257 257  Following is an example for how to join the TTN v3 LoRaWAN Network.
... ... @@ -268,12 +268,14 @@
268 268  (((
269 269  We take LES01 as an example.
270 270  
333 +
271 271  
272 272  )))
273 273  )))
274 274  
275 -== 4.1 Step1 ==
338 +== 4.1  Step1 ==
276 276  
340 +
277 277  (((
278 278  (((
279 279  Create a device in TTN with the OTAA keys from LSE01.
... ... @@ -297,11 +297,15 @@
297 297  [[image:image-20220526140044-18.png]]
298 298  
299 299  
300 -== 4.2 Step2 ==
301 301  
365 +== 4.2  Step2 ==
366 +
367 +
302 302  (((
303 303  (((
304 304  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.
371 +
372 +
305 305  )))
306 306  )))
307 307  
... ... @@ -308,34 +308,45 @@
308 308  [[image:image-20220526140132-19.png]]
309 309  
310 310  
311 -== 4.3 Step3 ==
312 312  
380 +== 4.3  Step3 ==
381 +
382 +
313 313  Add APP EUI in the application:
314 314  
385 +
315 315  [[image:image-20220526140205-20.png]]
316 316  
317 317  
318 -== 4.4 Step4 ==
319 319  
390 +== 4.4  Step4 ==
391 +
392 +
320 320  Add APP KEY and DEV EUI:
321 321  
395 +
322 322  [[image:image-20220526140251-21.png]]
323 323  
324 324  
325 -= 5. TTN V3 integrated into MQTT server =
326 326  
327 -== 5.1 Introduction ==
400 += 5.  TTN V3 integrated into MQTT server =
328 328  
402 +
403 +== 5.1  Introduction ==
404 +
405 +
329 329  (((
330 330  (((
331 331  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.
332 332  
410 +
333 333  
334 334  )))
335 335  )))
336 336  
337 -== 5.2 Create device steps at MQTT ==
415 +== 5.2  Create device steps at MQTT ==
338 338  
417 +
339 339  (((
340 340  (((
341 341  The user creates a new API KEY after creating a device on TTN V3.
... ... @@ -351,6 +351,8 @@
351 351  (((
352 352  (((
353 353  Fill in Broker Address and Broker port.
433 +
434 +
354 354  )))
355 355  )))
356 356  
... ... @@ -359,8 +359,10 @@
359 359  Fill in the username and password into MQTT.
360 360  
361 361  
443 +
362 362  [[image:image-20220526140420-23.png]]
363 363  
446 +
364 364  The Application Server publishes uplink traffic on the following topics:
365 365  
366 366  (% class="box" %)
... ... @@ -377,13 +377,18 @@
377 377  )))
378 378  
379 379  (((
463 +
464 +
380 380  (((
381 -**Note**: Remember that the format of these topics for The Things Stack Open Source would contain {application id} instead of {application id}@{tenant id}.
466 +(% 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}.**
467 +
468 +
382 382  )))
383 383  )))
384 384  
385 385  [[image:image-20220526140452-24.png]]
386 386  
474 +
387 387  (((
388 388  (((
389 389  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.
... ... @@ -400,7 +400,11 @@
400 400  
401 401  (((
402 402  (((
403 -**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.
491 +
492 +
493 +(% 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.**
494 +
495 +
404 404  )))
405 405  )))
406 406  
... ... @@ -414,17 +414,23 @@
414 414  
415 415  (((
416 416  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:
509 +
510 +
417 417  )))
418 418  
419 419  (((
420 -**Note**: Use this handy tool to convert hexadecimal to base64.
514 +(% style="color:red" %)**Note**: **Use this handy tool to convert hexadecimal to base64.**
515 +
516 +
421 421  )))
422 422  
423 423  [[image:image-20220526140936-27.png]]
424 424  
425 425  
426 -== 5.3 Send Downlink message ==
427 427  
523 +== 5.3  Send Downlink message ==
524 +
525 +
428 428  (((
429 429  How to configure downlink in TTN V3?
430 430  )))
... ... @@ -434,7 +434,9 @@
434 434  )))
435 435  
436 436  (((
437 -Downlink command:01 00 00 5A
535 +(% style="color:blue" %)**Downlink command: 01 00 00 5A**
536 +
537 +
438 438  )))
439 439  
440 440  [[image:image-20220526141021-28.png]]
... ... @@ -442,6 +442,7 @@
442 442  downlink
443 443  
444 444  
545 +
445 445  After sending, you can view it in live data.
446 446  
447 447  [[image:image-20220526141052-29.png]]
... ... @@ -449,12 +449,15 @@
449 449  downlink
450 450  
451 451  
553 +
452 452  (((
453 453  When downlink is successfully sent, the downlink information can be received on the serial port.
454 454  )))
455 455  
456 456  (((
457 -**Note**: If the downlink byte sent is longer, the number of bytes will be displayed.
559 +(% style="color:red" %)**Note**:** If the downlink byte sent is longer, the number of bytes will be displayed.**
560 +
561 +
458 458  )))
459 459  
460 460  [[image:image-20220526141116-30.png]]
... ... @@ -470,13 +470,13 @@
470 470  
471 471  (((
472 472  (((
473 -If the equipment uses CLASS A. You can set **AT+RPL=2** or send the downlink command: **2102**
577 +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**
474 474  )))
475 475  )))
476 476  
477 477  (((
478 478  (((
479 -If the equipment uses CLASS C. You can set** AT+RPL=4** or send the downlink command: **2104**
583 +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**
480 480  )))
481 481  )))
482 482  
... ... @@ -483,6 +483,8 @@
483 483  (((
484 484  (((
485 485  When the device successfully receives the downlink, the server will receive a confirmation packet of 00.
590 +
591 +
486 486  )))
487 487  )))
488 488  
... ... @@ -491,8 +491,10 @@
491 491  downlink
492 492  
493 493  
494 -= 6. Request Remote Support =
495 495  
601 += 6.  Request Remote Support =
602 +
603 +
496 496  (((
497 497  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.
498 498  \\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:**
... ... @@ -504,19 +504,24 @@
504 504  * End Node traffic (from server UI) to shows end node activity in server. (Normally possible)
505 505  * 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)
506 506  
507 -**~1. End Device Join Screen shot, we can check:**
508 508  
616 +(% style="color:blue" %)**1. End Device Join Screen shot, we can check:**
617 +
509 509  * If the device is sending join request to server?
510 510  * What frequency the device is sending?
511 511  
621 +
512 512  [[image:image-20220526141308-33.png]]
513 513  
514 514  Console Output from End device to see the transmit frequency
515 515  
516 -User can run **AT+CFG **command to print configuration information.
517 517  
518 -* Is the device in OTAA mode or ABP mode? **AT+NJM=1** (OTAA mode), **AT+NJM=0** (ABP mode)
627 +User can run (% style="color:blue" %)**AT+CFG **(%%)command to print configuration information.
519 519  
629 +* 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)
630 +
631 +
632 +
520 520  [[image:image-20220526141612-36.png]]
521 521  
522 522  
... ... @@ -523,13 +523,17 @@
523 523  Console Output from End device to see the transmit frequency
524 524  
525 525  
526 -**2. Gateway packet traffic in gateway web or ssh. we can check:**
527 527  
640 +(% style="color:blue" %)**2. Gateway packet traffic in gateway web or ssh. we can check:**
641 +
528 528  * (((
529 529  If the gateway receive the Join request packet from sensor? (If this fail, check if the gateway and sensor works on the match frequency)
530 530  )))
531 531  * (((
532 532  If the gateway gets the Join Accept message from server and transmit it via LoRa?
647 +
648 +
649 +
533 533  )))
534 534  
535 535  [[image:image-20220526141739-37.png]]
... ... @@ -537,8 +537,9 @@
537 537  Console Output from Gateway to see packets between end node and server.
538 538  
539 539  
540 -**3. Gateway Traffic Page in LoRaWAN Server**
541 541  
658 +(% style="color:blue" %)**3. Gateway Traffic Page in LoRaWAN Server**
659 +
542 542  * (((
543 543  If the Join Request packet arrive the gateway traffic in server? If not, check the internet connection and gateway LoRaWAN server settings.
544 544  )))
... ... @@ -547,6 +547,9 @@
547 547  )))
548 548  * (((
549 549  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.
668 +
669 +
670 +
550 550  )))
551 551  
552 552  [[image:image-20220526141823-38.png||height="501" width="1144"]]
... ... @@ -554,18 +554,21 @@
554 554  The Traffic for the End node in the server, use TTNv3 as example
555 555  
556 556  
678 +
557 557  [[image:image-20220526141917-39.png]]
558 558  
559 559  The Traffic for the End node in the server, use TTNv3 as example
560 560  
561 561  
562 -**4. Data Page in LoRaWAN server**
563 563  
685 +(% style="color:blue" %)**4. Data Page in LoRaWAN server**
686 +
564 564  (((
565 565  (((
566 566  (((
567 567  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.
568 568  
692 +
569 569  [[image:image-20220526141956-40.png]]
570 570  )))
571 571  )))
... ... @@ -574,6 +574,7 @@
574 574  The data for the end device set in server
575 575  
576 576  
701 +
577 577  [[image:image-20220526142033-41.png]]
578 578  
579 579  Check if OTAA Keys match the keys in device

Applications

Navigation

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