Changes for page Notes for TTN

Last modified by Mengting Qiu on 2024/08/20 17:29
<
From version < 99.11 >
edited by Xiaoling
on 2022/07/25 08:52
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  
... ... @@ -255,10 +255,10 @@
255 255  
256 256  (% class="box" %)
257 257  (((
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)
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)
262 262  )))
263 263  
264 264  [[image:image-20220526135654-13.png]]
... ... @@ -266,32 +266,41 @@
266 266  Congfigure Station
267 267  
268 268  
269 -== 3.7 Start Station ==
270 270  
271 +== 3.7  Start Station ==
272 +
273 +
271 271  (((
272 272  When the user has finished the configuration,Please click Sace&Apply to start station to connect The Things Network.
273 273  
277 +
274 274  
275 275  )))
276 276  
277 -== 3.8 Siccessful Connection ==
281 +== 3.8  Siccessful Connection ==
278 278  
283 +
279 279  If user completes the above steps,which will see live date in the TTN.
280 280  
286 +
281 281  [[image:image-20220526135734-14.png]]
282 282  
283 283  Station live date
284 284  
285 285  
286 -== 3.9 Trouble Shooting ==
287 287  
293 +== 3.9  Trouble Shooting ==
294 +
295 +
288 288  User can check the station log in the logread/system log page.
289 289  
298 +
290 290  [[image:image-20220526135845-15.png]]
291 291  
292 292  Station Log
293 293  
294 294  
304 +
295 295  and recode the station log in the system/Recode log page.
296 296  
297 297  [[image:image-20220526135940-16.png]]
... ... @@ -299,8 +299,10 @@
299 299  Recore Log
300 300  
301 301  
302 -= 4. Configure node connection to TTNv3 =
303 303  
313 += 4.  Configure node connection to TTNv3 =
314 +
315 +
304 304  (((
305 305  (((
306 306  Following is an example for how to join the TTN v3 LoRaWAN Network.
... ... @@ -317,12 +317,14 @@
317 317  (((
318 318  We take LES01 as an example.
319 319  
332 +
320 320  
321 321  )))
322 322  )))
323 323  
324 -== 4.1 Step1 ==
337 +== 4.1  Step1 ==
325 325  
339 +
326 326  (((
327 327  (((
328 328  Create a device in TTN with the OTAA keys from LSE01.
... ... @@ -346,11 +346,15 @@
346 346  [[image:image-20220526140044-18.png]]
347 347  
348 348  
349 -== 4.2 Step2 ==
350 350  
364 +== 4.2  Step2 ==
365 +
366 +
351 351  (((
352 352  (((
353 353  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 +
354 354  )))
355 355  )))
356 356  
... ... @@ -357,34 +357,45 @@
357 357  [[image:image-20220526140132-19.png]]
358 358  
359 359  
360 -== 4.3 Step3 ==
361 361  
379 +== 4.3  Step3 ==
380 +
381 +
362 362  Add APP EUI in the application:
363 363  
384 +
364 364  [[image:image-20220526140205-20.png]]
365 365  
366 366  
367 -== 4.4 Step4 ==
368 368  
389 +== 4.4  Step4 ==
390 +
391 +
369 369  Add APP KEY and DEV EUI:
370 370  
394 +
371 371  [[image:image-20220526140251-21.png]]
372 372  
373 373  
374 -= 5. TTN V3 integrated into MQTT server =
375 375  
376 -== 5.1 Introduction ==
399 += 5.  TTN V3 integrated into MQTT server =
377 377  
401 +
402 +== 5.1  Introduction ==
403 +
404 +
378 378  (((
379 379  (((
380 380  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 381  
409 +
382 382  
383 383  )))
384 384  )))
385 385  
386 -== 5.2 Create device steps at MQTT ==
414 +== 5.2  Create device steps at MQTT ==
387 387  
416 +
388 388  (((
389 389  (((
390 390  The user creates a new API KEY after creating a device on TTN V3.
... ... @@ -400,6 +400,8 @@
400 400  (((
401 401  (((
402 402  Fill in Broker Address and Broker port.
432 +
433 +
403 403  )))
404 404  )))
405 405  
... ... @@ -408,8 +408,10 @@
408 408  Fill in the username and password into MQTT.
409 409  
410 410  
442 +
411 411  [[image:image-20220526140420-23.png]]
412 412  
445 +
413 413  The Application Server publishes uplink traffic on the following topics:
414 414  
415 415  (% class="box" %)
... ... @@ -426,13 +426,18 @@
426 426  )))
427 427  
428 428  (((
462 +
463 +
429 429  (((
430 -**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 +
431 431  )))
432 432  )))
433 433  
434 434  [[image:image-20220526140452-24.png]]
435 435  
473 +
436 436  (((
437 437  (((
438 438  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.
... ... @@ -449,7 +449,11 @@
449 449  
450 450  (((
451 451  (((
452 -**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 +
453 453  )))
454 454  )))
455 455  
... ... @@ -463,17 +463,23 @@
463 463  
464 464  (((
465 465  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 +
466 466  )))
467 467  
468 468  (((
469 -**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 +
470 470  )))
471 471  
472 472  [[image:image-20220526140936-27.png]]
473 473  
474 474  
475 -== 5.3 Send Downlink message ==
476 476  
522 +== 5.3  Send Downlink message ==
523 +
524 +
477 477  (((
478 478  How to configure downlink in TTN V3?
479 479  )))
... ... @@ -483,7 +483,9 @@
483 483  )))
484 484  
485 485  (((
486 -Downlink command:01 00 00 5A
534 +(% style="color:blue" %)**Downlink command: 01 00 00 5A**
535 +
536 +
487 487  )))
488 488  
489 489  [[image:image-20220526141021-28.png]]
... ... @@ -491,6 +491,7 @@
491 491  downlink
492 492  
493 493  
544 +
494 494  After sending, you can view it in live data.
495 495  
496 496  [[image:image-20220526141052-29.png]]
... ... @@ -498,12 +498,15 @@
498 498  downlink
499 499  
500 500  
552 +
501 501  (((
502 502  When downlink is successfully sent, the downlink information can be received on the serial port.
503 503  )))
504 504  
505 505  (((
506 -**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 +
507 507  )))
508 508  
509 509  [[image:image-20220526141116-30.png]]
... ... @@ -519,13 +519,13 @@
519 519  
520 520  (((
521 521  (((
522 -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**
523 523  )))
524 524  )))
525 525  
526 526  (((
527 527  (((
528 -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**
529 529  )))
530 530  )))
531 531  
... ... @@ -532,6 +532,8 @@
532 532  (((
533 533  (((
534 534  When the device successfully receives the downlink, the server will receive a confirmation packet of 00.
589 +
590 +
535 535  )))
536 536  )))
537 537  
... ... @@ -540,8 +540,10 @@
540 540  downlink
541 541  
542 542  
543 -= 6. Request Remote Support =
544 544  
600 += 6.  Request Remote Support =
601 +
602 +
545 545  (((
546 546  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.
547 547  \\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:**
... ... @@ -553,19 +553,24 @@
553 553  * End Node traffic (from server UI) to shows end node activity in server. (Normally possible)
554 554  * 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)
555 555  
556 -**~1. End Device Join Screen shot, we can check:**
557 557  
615 +(% style="color:blue" %)**1. End Device Join Screen shot, we can check:**
616 +
558 558  * If the device is sending join request to server?
559 559  * What frequency the device is sending?
560 560  
620 +
561 561  [[image:image-20220526141308-33.png]]
562 562  
563 563  Console Output from End device to see the transmit frequency
564 564  
565 -User can run **AT+CFG **command to print configuration information.
566 566  
567 -* 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.
568 568  
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 +
569 569  [[image:image-20220526141612-36.png]]
570 570  
571 571  
... ... @@ -572,13 +572,17 @@
572 572  Console Output from End device to see the transmit frequency
573 573  
574 574  
575 -**2. Gateway packet traffic in gateway web or ssh. we can check:**
576 576  
639 +(% style="color:blue" %)**2. Gateway packet traffic in gateway web or ssh. we can check:**
640 +
577 577  * (((
578 578  If the gateway receive the Join request packet from sensor? (If this fail, check if the gateway and sensor works on the match frequency)
579 579  )))
580 580  * (((
581 581  If the gateway gets the Join Accept message from server and transmit it via LoRa?
646 +
647 +
648 +
582 582  )))
583 583  
584 584  [[image:image-20220526141739-37.png]]
... ... @@ -586,8 +586,9 @@
586 586  Console Output from Gateway to see packets between end node and server.
587 587  
588 588  
589 -**3. Gateway Traffic Page in LoRaWAN Server**
590 590  
657 +(% style="color:blue" %)**3. Gateway Traffic Page in LoRaWAN Server**
658 +
591 591  * (((
592 592  If the Join Request packet arrive the gateway traffic in server? If not, check the internet connection and gateway LoRaWAN server settings.
593 593  )))
... ... @@ -596,6 +596,9 @@
596 596  )))
597 597  * (((
598 598  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 +
599 599  )))
600 600  
601 601  [[image:image-20220526141823-38.png||height="501" width="1144"]]
... ... @@ -603,18 +603,21 @@
603 603  The Traffic for the End node in the server, use TTNv3 as example
604 604  
605 605  
677 +
606 606  [[image:image-20220526141917-39.png]]
607 607  
608 608  The Traffic for the End node in the server, use TTNv3 as example
609 609  
610 610  
611 -**4. Data Page in LoRaWAN server**
612 612  
684 +(% style="color:blue" %)**4. Data Page in LoRaWAN server**
685 +
613 613  (((
614 614  (((
615 615  (((
616 616  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.
617 617  
691 +
618 618  [[image:image-20220526141956-40.png]]
619 619  )))
620 620  )))
... ... @@ -623,6 +623,7 @@
623 623  The data for the end device set in server
624 624  
625 625  
700 +
626 626  [[image:image-20220526142033-41.png]]
627 627  
628 628  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