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 < 99.16 >
edited by Xiaoling
on 2022/07/25 09:18
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -84,15 +84,16 @@
84 84  The Dragino gateway has supports the Secondary server settings.
85 85  
86 86  
87 +
87 87  === 2.2.2  Below list the support products and Requirements: ===
88 88  
89 89  
90 90  (((
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 +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  )))
93 93  
94 94  (((
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 +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  
98 98  
... ... @@ -135,25 +135,31 @@
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/]]
139 +
140 +
138 138  )))
139 139  )))
140 140  
141 141  (((
142 -**Below list the support products and Requirements:**
145 +(% style="color:blue" %)**Below list the support products and Requirements:**
143 143  )))
144 144  
145 145  (((
146 146  (((
147 - ~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]]
150 +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]]
148 148  )))
149 149  
150 150  (((
151 151   2. Firmware version since :[[lgw~~-~~-build-v5.4.1640315898>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/]]
155 +
156 +
157 +
158 +
152 152  )))
153 153  )))
154 154  
155 155  (((
156 -**What do you need to prepare**
163 +(% style="color:blue" %)**What do you need to prepare**
157 157  )))
158 158  
159 159  (((
... ... @@ -160,12 +160,14 @@
160 160  (((
161 161  A gateway that can access the internet normally
162 162  
170 +
163 163  
164 164  )))
165 165  )))
166 166  
167 -== 3.2 Step 1. Add Gateway ==
175 +== 3.2  Step 1: Add Gateway ==
168 168  
177 +
169 169  (((
170 170  (((
171 171  The example for **EU**
... ... @@ -181,6 +181,8 @@
181 181  (((
182 182  (((
183 183  Following picture is the successful added.
193 +
194 +
184 184  )))
185 185  )))
186 186  
... ... @@ -189,52 +189,66 @@
189 189  Add Gateway
190 190  
191 191  
192 -== 3.3 Step 2. Create the API key ==
193 193  
204 +== 3.3  Step 2: Create the API key ==
205 +
206 +
194 194  user need to create the CUPS API key and LNS API key.
195 195  
209 +
196 196  [[image:image-20220526135349-9.png]]
197 197  
198 198  Create CUPS API key
199 199  
200 200  
215 +
201 201  [[image:image-20220526135428-10.png]]
202 202  
203 203  Create LNS API key
204 204  
220 +
205 205  (% style="color:red" %)**Note : Please copy the API key.**
206 206  
207 207  
208 -== 3.4 Step 3. Update the gateway setting ==
209 209  
225 +== 3.4  Step 3: Update the gateway setting ==
226 +
227 +
210 210  In the LoRa Basics Station LNS Authentication Key field, paste the API key you generated in the previous step.
211 211  
230 +
212 212  [[image:image-20220526135528-11.png]]
213 213  
214 214  paste the API key
215 215  
216 216  
217 -== 3.5 Step 4. Access the gateway GUI ==
218 218  
237 +== 3.5  Step 4: Access the gateway GUI ==
238 +
239 +
219 219  User need to update the API key and install the Certificate
220 220  
242 +
221 221  [[image:image-20220526135601-12.png]]
222 222  
223 223  Access the gateway GUI
224 224  
225 225  
226 -== 3.6 Step 5. Configure Station ==
227 227  
249 +== 3.6  Step 5: Configure Station ==
250 +
251 +
228 228  User need to input Server URI, Server CUPS Key and LNS Key, as well as install CUPS certificate.
229 229  
230 -**just to clarify.**
231 231  
255 +(% style="color:blue" %)**just to clarify:**
256 +
232 232  (% class="box" %)
233 233  (((
234 - CUPS Server URI  ~-~-> Server Adress
235 - CUPS Authorization Key         ~-~-> Server CUPS API Key
236 - LNS Authorization Key  ~-~-> Server LNS API Key
237 - CUPS certificate  ~-~-> Server CA(user can use the button to install the certificate by default)
259 + CUPS Server URI  ~-~->  Server Adress
260 + CUPS Authorization Key         ~-~->  Server CUPS API Key
261 + LNS Authorization Key  ~-~->  Server LNS API Key
262 + CUPS certificate  ~-~->  Server CA(user can use the button to install the certificate by default)
238 238  )))
239 239  
240 240  [[image:image-20220526135654-13.png]]
... ... @@ -242,32 +242,41 @@
242 242  Congfigure Station
243 243  
244 244  
245 -== 3.7 Start Station ==
246 246  
271 +== 3.7  Start Station ==
272 +
273 +
247 247  (((
248 248  When the user has finished the configuration,Please click Sace&Apply to start station to connect The Things Network.
249 249  
277 +
250 250  
251 251  )))
252 252  
253 -== 3.8 Siccessful Connection ==
281 +== 3.8  Siccessful Connection ==
254 254  
283 +
255 255  If user completes the above steps,which will see live date in the TTN.
256 256  
286 +
257 257  [[image:image-20220526135734-14.png]]
258 258  
259 259  Station live date
260 260  
261 261  
262 -== 3.9 Trouble Shooting ==
263 263  
293 +== 3.9  Trouble Shooting ==
294 +
295 +
264 264  User can check the station log in the logread/system log page.
265 265  
298 +
266 266  [[image:image-20220526135845-15.png]]
267 267  
268 268  Station Log
269 269  
270 270  
304 +
271 271  and recode the station log in the system/Recode log page.
272 272  
273 273  [[image:image-20220526135940-16.png]]
... ... @@ -275,8 +275,10 @@
275 275  Recore Log
276 276  
277 277  
278 -= 4. Configure node connection to TTNv3 =
279 279  
313 += 4.  Configure node connection to TTNv3 =
314 +
315 +
280 280  (((
281 281  (((
282 282  Following is an example for how to join the TTN v3 LoRaWAN Network.
... ... @@ -293,12 +293,14 @@
293 293  (((
294 294  We take LES01 as an example.
295 295  
332 +
296 296  
297 297  )))
298 298  )))
299 299  
300 -== 4.1 Step1 ==
337 +== 4.1  Step1 ==
301 301  
339 +
302 302  (((
303 303  (((
304 304  Create a device in TTN with the OTAA keys from LSE01.
... ... @@ -322,11 +322,15 @@
322 322  [[image:image-20220526140044-18.png]]
323 323  
324 324  
325 -== 4.2 Step2 ==
326 326  
364 +== 4.2  Step2 ==
365 +
366 +
327 327  (((
328 328  (((
329 329  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.
370 +
371 +
330 330  )))
331 331  )))
332 332  
... ... @@ -333,34 +333,45 @@
333 333  [[image:image-20220526140132-19.png]]
334 334  
335 335  
336 -== 4.3 Step3 ==
337 337  
379 +== 4.3  Step3 ==
380 +
381 +
338 338  Add APP EUI in the application:
339 339  
384 +
340 340  [[image:image-20220526140205-20.png]]
341 341  
342 342  
343 -== 4.4 Step4 ==
344 344  
389 +== 4.4  Step4 ==
390 +
391 +
345 345  Add APP KEY and DEV EUI:
346 346  
394 +
347 347  [[image:image-20220526140251-21.png]]
348 348  
349 349  
350 -= 5. TTN V3 integrated into MQTT server =
351 351  
352 -== 5.1 Introduction ==
399 += 5.  TTN V3 integrated into MQTT server =
353 353  
401 +
402 +== 5.1  Introduction ==
403 +
404 +
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 357  
409 +
358 358  
359 359  )))
360 360  )))
361 361  
362 -== 5.2 Create device steps at MQTT ==
414 +== 5.2  Create device steps at MQTT ==
363 363  
416 +
364 364  (((
365 365  (((
366 366  The user creates a new API KEY after creating a device on TTN V3.
... ... @@ -376,6 +376,8 @@
376 376  (((
377 377  (((
378 378  Fill in Broker Address and Broker port.
432 +
433 +
379 379  )))
380 380  )))
381 381  
... ... @@ -384,8 +384,10 @@
384 384  Fill in the username and password into MQTT.
385 385  
386 386  
442 +
387 387  [[image:image-20220526140420-23.png]]
388 388  
445 +
389 389  The Application Server publishes uplink traffic on the following topics:
390 390  
391 391  (% class="box" %)
... ... @@ -402,13 +402,18 @@
402 402  )))
403 403  
404 404  (((
462 +
463 +
405 405  (((
406 -**Note**: Remember that the format of these topics for The Things Stack Open Source would contain {application id} instead of {application id}@{tenant id}.
465 +(% 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}.**
466 +
467 +
407 407  )))
408 408  )))
409 409  
410 410  [[image:image-20220526140452-24.png]]
411 411  
473 +
412 412  (((
413 413  (((
414 414  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.
... ... @@ -425,7 +425,11 @@
425 425  
426 426  (((
427 427  (((
428 -**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.
490 +
491 +
492 +(% 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.**
493 +
494 +
429 429  )))
430 430  )))
431 431  
... ... @@ -439,17 +439,23 @@
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:
508 +
509 +
442 442  )))
443 443  
444 444  (((
445 -**Note**: Use this handy tool to convert hexadecimal to base64.
513 +(% style="color:red" %)**Note**: **Use this handy tool to convert hexadecimal to base64.**
514 +
515 +
446 446  )))
447 447  
448 448  [[image:image-20220526140936-27.png]]
449 449  
450 450  
451 -== 5.3 Send Downlink message ==
452 452  
522 +== 5.3  Send Downlink message ==
523 +
524 +
453 453  (((
454 454  How to configure downlink in TTN V3?
455 455  )))
... ... @@ -459,7 +459,9 @@
459 459  )))
460 460  
461 461  (((
462 -Downlink command:01 00 00 5A
534 +(% style="color:blue" %)**Downlink command: 01 00 00 5A**
535 +
536 +
463 463  )))
464 464  
465 465  [[image:image-20220526141021-28.png]]
... ... @@ -467,6 +467,7 @@
467 467  downlink
468 468  
469 469  
544 +
470 470  After sending, you can view it in live data.
471 471  
472 472  [[image:image-20220526141052-29.png]]
... ... @@ -474,12 +474,15 @@
474 474  downlink
475 475  
476 476  
552 +
477 477  (((
478 478  When downlink is successfully sent, the downlink information can be received on the serial port.
479 479  )))
480 480  
481 481  (((
482 -**Note**: If the downlink byte sent is longer, the number of bytes will be displayed.
558 +(% style="color:red" %)**Note**:** If the downlink byte sent is longer, the number of bytes will be displayed.**
559 +
560 +
483 483  )))
484 484  
485 485  [[image:image-20220526141116-30.png]]
... ... @@ -495,13 +495,13 @@
495 495  
496 496  (((
497 497  (((
498 -If the equipment uses CLASS A. You can set **AT+RPL=2** or send the downlink command: **2102**
576 +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**
499 499  )))
500 500  )))
501 501  
502 502  (((
503 503  (((
504 -If the equipment uses CLASS C. You can set** AT+RPL=4** or send the downlink command: **2104**
582 +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**
505 505  )))
506 506  )))
507 507  
... ... @@ -508,6 +508,8 @@
508 508  (((
509 509  (((
510 510  When the device successfully receives the downlink, the server will receive a confirmation packet of 00.
589 +
590 +
511 511  )))
512 512  )))
513 513  
... ... @@ -516,8 +516,10 @@
516 516  downlink
517 517  
518 518  
519 -= 6. Request Remote Support =
520 520  
600 += 6.  Request Remote Support =
601 +
602 +
521 521  (((
522 522  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.
523 523  \\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:**
... ... @@ -529,19 +529,24 @@
529 529  * End Node traffic (from server UI) to shows end node activity in server. (Normally possible)
530 530  * 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)
531 531  
532 -**~1. End Device Join Screen shot, we can check:**
533 533  
615 +(% style="color:blue" %)**1. End Device Join Screen shot, we can check:**
616 +
534 534  * If the device is sending join request to server?
535 535  * What frequency the device is sending?
536 536  
620 +
537 537  [[image:image-20220526141308-33.png]]
538 538  
539 539  Console Output from End device to see the transmit frequency
540 540  
541 -User can run **AT+CFG **command to print configuration information.
542 542  
543 -* Is the device in OTAA mode or ABP mode? **AT+NJM=1** (OTAA mode), **AT+NJM=0** (ABP mode)
626 +User can run (% style="color:blue" %)**AT+CFG **(%%)command to print configuration information.
544 544  
628 +* 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)
629 +
630 +
631 +
545 545  [[image:image-20220526141612-36.png]]
546 546  
547 547  
... ... @@ -548,13 +548,17 @@
548 548  Console Output from End device to see the transmit frequency
549 549  
550 550  
551 -**2. Gateway packet traffic in gateway web or ssh. we can check:**
552 552  
639 +(% style="color:blue" %)**2. Gateway packet traffic in gateway web or ssh. we can check:**
640 +
553 553  * (((
554 554  If the gateway receive the Join request packet from sensor? (If this fail, check if the gateway and sensor works on the match frequency)
555 555  )))
556 556  * (((
557 557  If the gateway gets the Join Accept message from server and transmit it via LoRa?
646 +
647 +
648 +
558 558  )))
559 559  
560 560  [[image:image-20220526141739-37.png]]
... ... @@ -562,8 +562,9 @@
562 562  Console Output from Gateway to see packets between end node and server.
563 563  
564 564  
565 -**3. Gateway Traffic Page in LoRaWAN Server**
566 566  
657 +(% style="color:blue" %)**3. Gateway Traffic Page in LoRaWAN Server**
658 +
567 567  * (((
568 568  If the Join Request packet arrive the gateway traffic in server? If not, check the internet connection and gateway LoRaWAN server settings.
569 569  )))
... ... @@ -572,6 +572,9 @@
572 572  )))
573 573  * (((
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.
667 +
668 +
669 +
575 575  )))
576 576  
577 577  [[image:image-20220526141823-38.png||height="501" width="1144"]]
... ... @@ -579,18 +579,21 @@
579 579  The Traffic for the End node in the server, use TTNv3 as example
580 580  
581 581  
677 +
582 582  [[image:image-20220526141917-39.png]]
583 583  
584 584  The Traffic for the End node in the server, use TTNv3 as example
585 585  
586 586  
587 -**4. Data Page in LoRaWAN server**
588 588  
684 +(% style="color:blue" %)**4. Data Page in LoRaWAN server**
685 +
589 589  (((
590 590  (((
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  
691 +
594 594  [[image:image-20220526141956-40.png]]
595 595  )))
596 596  )))
... ... @@ -599,6 +599,7 @@
599 599  The data for the end device set in server
600 600  
601 601  
700 +
602 602  [[image:image-20220526142033-41.png]]
603 603  
604 604  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