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 < 82.1 >
edited by Xiaoling
on 2022/05/26 14:04
>
Change comment: Uploaded new attachment "image-20220526140420-23.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -1,9 +1,8 @@
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  
9 9  == 1.1 Introduction ==
... ... @@ -51,7 +51,6 @@
51 51  Put Gateway ID
52 52  
53 53  
54 -
55 55  [[image:image-20220526134759-3.png]]
56 56  
57 57  Choose Frequency Band
... ... @@ -296,7 +296,6 @@
296 296  
297 297  [[image:image-20220526140044-18.png]]
298 298  
299 -
300 300  == 4.2 Step2 ==
301 301  
302 302  (((
... ... @@ -305,23 +305,20 @@
305 305  )))
306 306  )))
307 307  
308 -[[image:image-20220526140132-19.png]]
305 +[[image:image-20220525090920-18.png]]
309 309  
310 -
311 311  == 4.3 Step3 ==
312 312  
313 313  Add APP EUI in the application:
314 314  
315 -[[image:image-20220526140205-20.png]]
311 +[[image:image-20220525091022-19.png]]
316 316  
317 -
318 318  == 4.4 Step4 ==
319 319  
320 320  Add APP KEY and DEV EUI:
321 321  
322 -[[image:image-20220526140251-21.png]]
317 +[[image:image-20220525091128-20.png]]
323 323  
324 -
325 325  = 5. TTN V3 integrated into MQTT server =
326 326  
327 327  == 5.1 Introduction ==
... ... @@ -329,8 +329,6 @@
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 -
333 -
334 334  )))
335 335  )))
336 336  
... ... @@ -354,12 +354,12 @@
354 354  )))
355 355  )))
356 356  
357 -[[image:image-20220526140347-22.png]]
349 +[[image:image-20220525091251-22.png]]
358 358  
359 359  Fill in the username and password into MQTT.
360 360  
361 361  
362 -[[image:image-20220526140420-23.png]]
354 +[[image:image-20220525091333-23.png]]
363 363  
364 364  The Application Server publishes uplink traffic on the following topics:
365 365  
... ... @@ -382,7 +382,7 @@
382 382  )))
383 383  )))
384 384  
385 -[[image:image-20220526140452-24.png]]
377 +[[image:image-20220525091430-24.png]]
386 386  
387 387  (((
388 388  (((
... ... @@ -390,7 +390,7 @@
390 390  )))
391 391  )))
392 392  
393 -[[image:image-20220526140708-25.png]]
385 +[[image:image-20220525091458-25.png]]
394 394  
395 395  (((
396 396  (((
... ... @@ -410,7 +410,7 @@
410 410  )))
411 411  )))
412 412  
413 -[[image:image-20220526140856-26.png]]
405 +[[image:image-20220525091618-27.png]]
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:
... ... @@ -420,9 +420,8 @@
420 420  **Note**: Use this handy tool to convert hexadecimal to base64.
421 421  )))
422 422  
423 -[[image:image-20220526140936-27.png]]
415 +[[image:image-20220525091702-28.png]]
424 424  
425 -
426 426  == 5.3 Send Downlink message ==
427 427  
428 428  (((
... ... @@ -437,18 +437,16 @@
437 437  Downlink command:01 00 00 5A
438 438  )))
439 439  
440 -[[image:image-20220526141021-28.png]]
431 +[[image:image-20220525091752-29.png]]
441 441  
442 442  downlink
443 443  
444 -
445 445  After sending, you can view it in live data.
446 446  
447 -[[image:image-20220526141052-29.png]]
437 +[[image:image-20220525091816-30.png]]
448 448  
449 449  downlink
450 450  
451 -
452 452  (((
453 453  When downlink is successfully sent, the downlink information can be received on the serial port.
454 454  )))
... ... @@ -457,11 +457,10 @@
457 457  **Note**: If the downlink byte sent is longer, the number of bytes will be displayed.
458 458  )))
459 459  
460 -[[image:image-20220526141116-30.png]]
449 +[[image:image-20220525091855-31.png]]
461 461  
462 462  downlink
463 463  
464 -
465 465  (((
466 466  (((
467 467  If you want to get a successful reply to send downlink in TTN v3. You need to set the response level.
... ... @@ -486,11 +486,10 @@
486 486  )))
487 487  )))
488 488  
489 -[[image:image-20220526141149-31.png]]
477 +[[image:image-20220525091925-32.png]]
490 490  
491 491  downlink
492 492  
493 -
494 494  = 6. Request Remote Support =
495 495  
496 496  (((
... ... @@ -509,7 +509,7 @@
509 509  * If the device is sending join request to server?
510 510  * What frequency the device is sending?
511 511  
512 -[[image:image-20220526141308-33.png]]
499 +[[image:image-20220525092012-33.png]]
513 513  
514 514  Console Output from End device to see the transmit frequency
515 515  
... ... @@ -517,12 +517,10 @@
517 517  
518 518  * Is the device in OTAA mode or ABP mode? **AT+NJM=1** (OTAA mode), **AT+NJM=0** (ABP mode)
519 519  
520 -[[image:image-20220526141612-36.png]]
507 +[[image:image-20220525092043-34.png]]
521 521  
522 -
523 523  Console Output from End device to see the transmit frequency
524 524  
525 -
526 526  **2. Gateway packet traffic in gateway web or ssh. we can check:**
527 527  
528 528  * (((
... ... @@ -532,7 +532,7 @@
532 532  If the gateway gets the Join Accept message from server and transmit it via LoRa?
533 533  )))
534 534  
535 -[[image:image-20220526141739-37.png]]
520 +[[image:image-20220525092124-35.png]]
536 536  
537 537  Console Output from Gateway to see packets between end node and server.
538 538  
... ... @@ -549,16 +549,15 @@
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.
550 550  )))
551 551  
552 -[[image:image-20220526141823-38.png||height="501" width="1144"]]
537 +[[image:image-20220525092157-36.png]]
553 553  
554 554  The Traffic for the End node in the server, use TTNv3 as example
555 555  
556 556  
557 -[[image:image-20220526141917-39.png]]
542 +[[image:image-20220525092231-37.png]]
558 558  
559 559  The Traffic for the End node in the server, use TTNv3 as example
560 560  
561 -
562 562  **4. Data Page in LoRaWAN server**
563 563  
564 564  (((
... ... @@ -566,7 +566,7 @@
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  
569 -[[image:image-20220526141956-40.png]]
553 +[[image:image-20220525092546-1.png]]
570 570  )))
571 571  )))
572 572  )))
... ... @@ -573,7 +573,6 @@
573 573  
574 574  The data for the end device set in server
575 575  
560 +[[image:image-20220525092430-40.png]]
576 576  
577 -[[image:image-20220526142033-41.png]]
578 -
579 579  Check if OTAA Keys match the keys in device
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