Last modified by Kilight Cao on 2024/05/18 14:36
<
From version < 116.1 >
edited by Xiaoling
on 2022/07/06 15:53
To version < 133.1 >
edited by Xiaoling
on 2022/07/06 18:20
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -103,8 +103,6 @@
103 103  * Worldwide LTE,UMTS/HSPA+ and GSM/GPRS/EDGE coverage
104 104  * MIMO technology meets demands for data rate and link reliability in modem wireless communication systems
105 105  
106 -
107 -
108 108  == 1.3  Features ==
109 109  
110 110  * Open Source OpenWrt system
... ... @@ -121,8 +121,6 @@
121 121  * Support LoRaWAN basic station.
122 122  * Optional 3G/4G cellular connection
123 123  
124 -
125 -
126 126  == 1.4  Hardware System Structure ==
127 127  
128 128  [[image:1657079015096-949.png]]
... ... @@ -147,6 +147,7 @@
147 147  
148 148  * **ETH LED    **[[image:image-20220706115518-4.png||height="15" width="17"]] :  This LED shows the ETH interface connection status.
149 149  
146 +
150 150  = 2.  Access and Configure LPS8N =
151 151  
152 152  (((
... ... @@ -235,8 +235,6 @@
235 235  * **WiFi Client Mode**
236 236  * **WiFi AP Mode**
237 237  
238 -
239 -
240 240  == 3.2  Use WAN port to access Internet ==
241 241  
242 242  By default, the LPS8N is set to use the WAN port to connect to an upstream network. When you connect the LPS8N's WAN port to an upstream router, LPS8N will get an IP address from the router and have Internet access via the upstream router. The network status can be checked in the (% style="color:#4f81bd" %)**home page**:
... ... @@ -356,15 +356,14 @@
356 356  (% style="color:red" %)**Note: Choose the cluster corresponds to a specific Gateway server address**
357 357  
358 358  
359 -* Europe 1 (% style="color:red" %)corresponding Gateway server address: (% style="color:black" %)eu1.cloud.thethings.network
360 -* North America 1 (% style="color:red" %)corresponding Gateway server address:** **(% style="color:black" %)nam1.cloud.thethings.network
361 -* Australia 1 (% style="color:red" %)corresponding Gateway server address:** **(% style="color:black" %)au1.cloud.thethings.network
362 -* Legacy V2 Console : (% style="color:red" %)TTN v2 shuts down in December 2021
354 +* Europe 1** (% style="color:red" %)corresponding Gateway server address:(%%)**(% style="color:red" %) (% style="color:black" %)eu1.cloud.thethings.network
355 +* North America 1 (% style="color:red" %)**corresponding Gateway server address: **(% style="color:black" %)nam1.cloud.thethings.network
356 +* Australia 1 (% style="color:red" %)**corresponding Gateway server address: **(% style="color:black" %)au1.cloud.thethings.network
357 +* Legacy V2 Console : (% style="color:red" %)**TTN v2 shuts down in December 2021**
363 363  
364 -
365 -
366 366  (% style="color:#4f81bd" %)**Step 4: Create a Gateway**
367 367  
361 +[[image:1657091941182-367.png]]
368 368  
369 369  Click the Gateway icon and then click Add gateway.
370 370  
... ... @@ -371,10 +371,13 @@
371 371  
372 372  Open the following page:
373 373  
374 - [[image:1652422470352-518.png||height="391" width="716"]]
375 375  
376 -[[image:1652422479876-297.png||height="398" width="729"]]
369 + [[image:image-20220706155323-5.png||height="579" width="1060"]]
377 377  
371 +
372 +[[image:image-20220706155323-6.png||height="582" width="1066"]]
373 +
374 +
378 378  (((
379 379  (% style="color:red" %)**Notice: **Gateway Server address must match the gateway configuration, otherwise you will have problem for End Node to join the network.
380 380  )))
... ... @@ -381,16 +381,17 @@
381 381  
382 382  After creating the gateway, you can see the gateway info, as below.
383 383  
384 -[[image:1652422509034-682.png||height="299" width="739"]]
381 +[[image:1657094130908-567.png]](% style="display:none" %)
385 385  
386 -== 4.2 Configure DLOS8N to connect to TTN v3 ==
387 387  
384 +== 4.2  Configure DLOS8N to connect to TTN v3 ==
385 +
388 388  (((
389 -You can now configure the DLOS8N to let it connect to TTN network V3.
387 +You can now configure the LPS8N to let it connect to TTN network V3.
390 390  )))
391 391  
392 392  (((
393 -Make sure your DLOS8N has a working Internet Connection first.
391 +Make sure your LPS8N has a working Internet Connection first.
394 394  )))
395 395  
396 396  (((
... ... @@ -397,31 +397,35 @@
397 397  Choose the right server provider and click (% style="color:#4f81bd" %)**Save&Apply**
398 398  )))
399 399  
400 -[[image:1652422624783-580.png||height="327" width="729"]]
398 +[[image:1657094183213-301.png]]
401 401  
402 402  (% style="color:red" %)**Note: **The server address must match the Gateway server address you choose in TTN V3.
403 403  
402 +
404 404  In the home page, we can see the LoRaWAN connection is ready now.
405 405  
406 -[[image:1652422685063-596.png||height="327" width="729"]]
405 +[[image:1657094202420-798.png]]
407 407  
407 +
408 408  In TTN v3 portal, we can also see the gateway is connected.
409 409  
410 -[[image:1652422703020-955.png||height="343" width="730"]]
410 +[[image:1657094221515-510.png]]
411 411  
412 -== 4.3 Configure frequency ==
413 413  
414 -We also need to set the frequency plan in DLOS8N to match the end node we use, so to receive the LoRaWAN packets from the LoRaWAN sensor.
413 +== 4.3  Configure frequency ==
415 415  
416 -[[image:1652422737399-529.png||height="362" width="737"]]
415 +We also need to set the frequency plan in LPS8N to match the end node we use, so to receive the LoRaWAN packets from the LoRaWAN sensor.
417 417  
417 +[[image:1657094249818-468.png]]
418 418  
419 +
419 419  In logread page, user can check the frequency actually used.
420 420  
421 - [[image:1652422763536-750.png||height="514" width="730"]]
422 + [[image:1657094333704-207.png]]
422 422  
423 -== 4.4 Add a LoRaWAN End Device ==
424 424  
425 +== 4.4  Add a LoRaWAN End Device ==
426 +
425 425  (((
426 426  This section shows how to add a LoRaWAN End device to a LoRaWAN network and see the data from TTN web site.
427 427  )))
... ... @@ -434,6 +434,8 @@
434 434  
435 435  (((
436 436  (% style="color:#4f81bd" %)**Step 1**: (% style="color:black" %)Create a Device definition in TTN v3 with the OTAA keys from the example LT-22222-L IO Controller device.
439 +
440 +
437 437  )))
438 438  
439 439  (((
... ... @@ -448,10 +448,12 @@
448 448  A set of these codes are stored in each device by the manufacturer as the default codes for that particular device. Each device is shipped with a sticker with the default Device EUI as shown below.
449 449  )))
450 450  
451 -[[image:1652422840936-838.png]]
455 +[[image:1657094382177-591.png]]
452 452  
453 453  (((
454 454  (% style="color:red" %)Note: You may be able to change these codes in a device by using a configuration facility on the device e.g. the LT-22222 uses a serial port access and a series of AT commands.  Changing the codes may be necessary in the case where you have to use codes assigned by a LoRa WAN server.
459 +
460 +
455 455  )))
456 456  
457 457  (((
... ... @@ -462,16 +462,19 @@
462 462  Select **Add Application** to open the screen below.
463 463  )))
464 464  
465 -[[image:1652422946999-255.png||height="356" width="744"]]
471 +[[image:1657094417175-831.png]]
466 466  
467 467  Open the **Application **select** Add end device**
468 468  
475 +
469 469  Start Register the end device
470 470  
471 -[[image:1652422975885-591.png||height="359" width="726"]]
478 +[[image:1657094444802-101.png]]
472 472  
473 473  (((
474 474  Select OTAA activation mode
482 +
483 +
475 475  )))
476 476  
477 477  (((
... ... @@ -478,18 +478,22 @@
478 478  The LoRaWAN version for your device should be provided by the manufacturer in a datasheet as LoRaWAN version or LoRaWAN specification. The most commonly used LoRaWAN versions are v1.0.2 and v1.0.3.
479 479  )))
480 480  
481 -[[image:1652422998005-968.png||height="352" width="744"]]
490 +[[image:1657094475730-208.png]]
482 482  
483 483  First, input the End device ID, AppEUI and DevEUI.
484 484  
485 -[[image:1652423022781-339.png||height="365" width="741"]]
486 486  
495 +[[image:1657094646429-966.png]]
496 +
487 487  Secondly, choose the corresponding frequency and LoRaWAN class capabilities.
488 488  
489 -[[image:1652423046741-467.png||height="355" width="736"]]
490 490  
500 +[[image:1657094674045-755.png]]
501 +
491 491  (((
492 492  Finally, Application layer settings input the corresponding AppKey. Before saving the configuration, check that the data matches the device.
504 +
505 +
493 493  )))
494 494  
495 495  (((
... ... @@ -500,36 +500,40 @@
500 500  (% style="color:red" %)Note that it may take some time for the device data to appear in the TTN v3 display.
501 501  )))
502 502  
503 -[[image:1652423277549-324.png||height="273" width="745"]]
516 +[[image:1657094791060-639.png]]
504 504  
505 -= 5. Web Configure Pages =
506 506  
507 -== 5.1 Home ==
519 += 5.  Web Configure Pages =
508 508  
521 +== 5.1  Home ==
522 +
509 509  Shows the system running status.
510 510  
511 -[[image:1652423418568-752.png||height="329" width="724"]]
525 +[[image:1657094893942-726.png]]
512 512  
513 -== 5.2 LoRa Settings ==
514 514  
515 -=== 5.2.1 LoRa ~-~-> LoRa ===
528 +== 5.2  LoRa Settings ==
516 516  
530 +=== 5.2.1  LoRa ~-~-> LoRa ===
531 +
517 517  (((
518 518  This page shows the LoRa Radio Settings. There are a set of default frequency band according to LoRaWAN protocol, and user can customized the band* as well.
519 519  )))
520 520  
521 521  (((
522 -Different DLOS8N hardware version can support different frequency range:
537 +Different LPS8N hardware version can support different frequency range:
523 523  )))
524 524  
525 -* **868**: valid frequency: 863Mhz ~~ 870Mhz. for bands EU868, RU864, IN865 or KZ865.
526 -* **915**: valid frequency: 902Mhz ~~ 928Mhz. for bands US915, AU915, AS923 or KR920
540 +* (% style="color:blue" %)**868**(%%): valid frequency: 863Mhz ~~ 870Mhz. for bands EU868, RU864, IN865 or KZ865.
541 +* (% style="color:blue" %)**915**(%%): valid frequency: 902Mhz ~~ 928Mhz. for bands US915, AU915, AS923 or KR920
527 527  
528 528  (((
529 -After user choose the frequency plan, he can see the actually frequency in used by checking the page **LogRead ~-~-> LoRa Log**
544 +
545 +
546 +After user choose the frequency plan, he can see the actually frequency in used by checking the page (% style="color:green" %)**LogRead ~-~-> LoRa Log**
530 530  )))
531 531  
532 -[[image:1652423554776-574.png||height="380" width="740"]]
549 +[[image:1657094930903-357.png]]
533 533  
534 534  Note *: **[[See this instruction for how to customize frequency band>>doc:Main.How to customized LoRaWAN frequency band.WebHome]]**
535 535  
... ... @@ -536,7 +536,7 @@
536 536  
537 537  === 5.2.2 LoRa ~-~-> ABP Decryption ===
538 538  
539 -The DLOS8N can communicate with LoRaWAN ABP End Node without the need of LoRaWAN server. It can be used in some cases such as:
556 +The LPS8N can communicate with LoRaWAN ABP End Node without the need of LoRaWAN server. It can be used in some cases such as:
540 540  
541 541  * No internet connection.
542 542  * User wants to get data forward in gateway and forward to their server based on MQTT/HTTP, etc. (Combine ABP communication method and [[MQTT forward together>>doc:Main.MQTT Forward Instruction.WebHome]]).
... ... @@ -545,12 +545,13 @@
545 545  Detail of this feature: **[[Communication with ABP End Node>>doc:Main.Communicate with ABP End Node without LoRaWAN Network Server --- LG308.WebHome]]**
546 546  )))
547 547  
548 -[[image:1652423628833-467.png||height="357" width="755"]]
565 +[[image:1657095412271-942.png]]
549 549  
550 -== 5.3 LoRaWAN Settings ==
551 551  
552 -=== 5.3.1 LoRaWAN ~-~-> LoRaWAN ===
568 +== 5.3  LoRaWAN Settings ==
553 553  
570 +=== 5.3.1  LoRaWAN ~-~-> LoRaWAN ===
571 +
554 554  This page is for the connection set up to a general LoRaWAN Network server such as: [[TTN>>url:http://www.thethingsnetwork.org/]], [[ChirpStack>>url:https://www.chirpstack.io/]] etc
555 555  
556 556  [[image:1652423628833-467.png||height="357" width="755"]]
... ... @@ -557,18 +557,21 @@
557 557  
558 558  (% style="color:red" %)**Note:**
559 559  
560 -~*: User can ignore the latitude and longitude settings here, DLOS8N will use the actually value from GPS module.
578 +~*: User can ignore the latitude and longitude settings here, LPS8N will use the actually value from GPS module.
561 561  
562 562  ~**: Packet filter is to drop the unwanted LoRaWAN packet, instruction see here:
563 563  
564 564  **See:** **[[Filter unwanted LoRaWAN packets>>doc:Main.Filter unwanted LoRaWAN packets.WebHome]]**
565 565  
566 -=== 5.3.2 LoRaWAN ~-~-> Amazon AWS-IoT ===
567 567  
585 +=== 5.3.2  LoRaWAN ~-~-> Amazon AWS-IoT ===
586 +
568 568  [[image:1652428499323-384.png||height="275" width="723"]]
569 569  
570 570  (((
571 571  Please see this instruction to know more detail and demo for how to connect to **[[AWS-IoT LoRaWAN Core>>doc:Main.AWS IoT Core for LoRaWAN.WebHome]].**
591 +
592 +
572 572  )))
573 573  
574 574  === 5.3.3 LoRaWAN ~-~-> LORIOT ===
... ... @@ -583,6 +583,7 @@
583 583  
584 584  [[image:1652428648903-878.png||height="266" width="731"]]
585 585  
607 +
586 586  == 5.4 MQTT Settings ==
587 587  
588 588  If end nodes works in ABP mode, user can configure DLOS8N to transfer the data to MQTT broker,
... ... @@ -592,6 +592,7 @@
592 592  
593 593  [[image:1652428705046-212.png||height="417" width="733"]]
594 594  
617 +
595 595  == 5.5 System ==
596 596  
597 597  === 5.5.1 System ~-~-> System Overview ===
1657094130908-567.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +62.3 KB
Content
1657094183213-301.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +83.0 KB
Content
1657094202420-798.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +165.1 KB
Content
1657094221515-510.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +110.1 KB
Content
1657094249818-468.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +128.2 KB
Content
1657094333704-207.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +149.9 KB
Content
1657094382177-591.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +202.7 KB
Content
1657094417175-831.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +43.2 KB
Content
1657094444802-101.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +64.0 KB
Content
1657094475730-208.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +47.0 KB
Content
1657094646429-966.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +60.4 KB
Content
1657094674045-755.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +63.7 KB
Content
1657094791060-639.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +45.9 KB
Content
1657094893942-726.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +185.3 KB
Content
1657094930903-357.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +125.7 KB
Content
1657095412271-942.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +54.2 KB
Content

Applications

Navigation

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