Last modified by Kilight Cao on 2024/05/18 14:36
<
From version < 117.1 >
edited by Xiaoling
on 2022/07/06 15:55
To version < 128.2 >
edited by Xiaoling
on 2022/07/06 16:04
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -104,7 +104,6 @@
104 104  * MIMO technology meets demands for data rate and link reliability in modem wireless communication systems
105 105  
106 106  
107 -
108 108  == 1.3  Features ==
109 109  
110 110  * Open Source OpenWrt system
... ... @@ -122,7 +122,6 @@
122 122  * Optional 3G/4G cellular connection
123 123  
124 124  
125 -
126 126  == 1.4  Hardware System Structure ==
127 127  
128 128  [[image:1657079015096-949.png]]
... ... @@ -147,6 +147,9 @@
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  
148 +
149 +
150 +
150 150  = 2.  Access and Configure LPS8N =
151 151  
152 152  (((
... ... @@ -236,7 +236,6 @@
236 236  * **WiFi AP Mode**
237 237  
238 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,13 +356,12 @@
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
359 +* Europe 1** (% style="color:red" %)corresponding Gateway server address:(%%)**(% style="color:red" %) (% 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**
363 363  
364 364  
365 -
366 366  (% style="color:#4f81bd" %)**Step 4: Create a Gateway**
367 367  
368 368  [[image:1657091941182-367.png]]
... ... @@ -376,7 +376,7 @@
376 376   [[image:image-20220706155323-5.png||height="579" width="1060"]]
377 377  
378 378  
379 -[[image:image-20220706155323-6.png||height="618" width="1132"]]
378 +[[image:image-20220706155323-6.png||height="582" width="1066"]]
380 380  
381 381  
382 382  (((
... ... @@ -385,16 +385,17 @@
385 385  
386 386  After creating the gateway, you can see the gateway info, as below.
387 387  
388 -[[image:1652422509034-682.png||height="299" width="739"]]
387 +[[image:1657094130908-567.png]](% style="display:none" %)
389 389  
390 -== 4.2 Configure DLOS8N to connect to TTN v3 ==
391 391  
390 +== 4.2  Configure DLOS8N to connect to TTN v3 ==
391 +
392 392  (((
393 -You can now configure the DLOS8N to let it connect to TTN network V3.
393 +You can now configure the LPS8N to let it connect to TTN network V3.
394 394  )))
395 395  
396 396  (((
397 -Make sure your DLOS8N has a working Internet Connection first.
397 +Make sure your LPS8N has a working Internet Connection first.
398 398  )))
399 399  
400 400  (((
... ... @@ -401,31 +401,35 @@
401 401  Choose the right server provider and click (% style="color:#4f81bd" %)**Save&Apply**
402 402  )))
403 403  
404 -[[image:1652422624783-580.png||height="327" width="729"]]
404 +[[image:1657094183213-301.png]]
405 405  
406 406  (% style="color:red" %)**Note: **The server address must match the Gateway server address you choose in TTN V3.
407 407  
408 +
408 408  In the home page, we can see the LoRaWAN connection is ready now.
409 409  
410 -[[image:1652422685063-596.png||height="327" width="729"]]
411 +[[image:1657094202420-798.png]]
411 411  
413 +
412 412  In TTN v3 portal, we can also see the gateway is connected.
413 413  
414 -[[image:1652422703020-955.png||height="343" width="730"]]
416 +[[image:1657094221515-510.png]]
415 415  
416 -== 4.3 Configure frequency ==
417 417  
418 -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.
419 +== 4.3  Configure frequency ==
419 419  
420 -[[image:1652422737399-529.png||height="362" width="737"]]
421 +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.
421 421  
423 +[[image:1657094249818-468.png]]
422 422  
425 +
423 423  In logread page, user can check the frequency actually used.
424 424  
425 - [[image:1652422763536-750.png||height="514" width="730"]]
428 + [[image:1657094333704-207.png]]
426 426  
427 -== 4.4 Add a LoRaWAN End Device ==
428 428  
431 +== 4.4  Add a LoRaWAN End Device ==
432 +
429 429  (((
430 430  This section shows how to add a LoRaWAN End device to a LoRaWAN network and see the data from TTN web site.
431 431  )))
... ... @@ -438,6 +438,8 @@
438 438  
439 439  (((
440 440  (% 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.
445 +
446 +
441 441  )))
442 442  
443 443  (((
... ... @@ -452,10 +452,12 @@
452 452  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.
453 453  )))
454 454  
455 -[[image:1652422840936-838.png]]
461 +[[image:1657094382177-591.png]]
456 456  
457 457  (((
458 458  (% 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.
465 +
466 +
459 459  )))
460 460  
461 461  (((
... ... @@ -466,16 +466,19 @@
466 466  Select **Add Application** to open the screen below.
467 467  )))
468 468  
469 -[[image:1652422946999-255.png||height="356" width="744"]]
477 +[[image:1657094417175-831.png]]
470 470  
471 471  Open the **Application **select** Add end device**
472 472  
481 +
473 473  Start Register the end device
474 474  
475 -[[image:1652422975885-591.png||height="359" width="726"]]
484 +[[image:1657094444802-101.png]]
476 476  
477 477  (((
478 478  Select OTAA activation mode
488 +
489 +
479 479  )))
480 480  
481 481  (((
... ... @@ -482,16 +482,18 @@
482 482  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.
483 483  )))
484 484  
485 -[[image:1652422998005-968.png||height="352" width="744"]]
496 +[[image:1657094475730-208.png]]
486 486  
487 487  First, input the End device ID, AppEUI and DevEUI.
488 488  
489 -[[image:1652423022781-339.png||height="365" width="741"]]
490 490  
501 +[[image:1657094646429-966.png]]
502 +
491 491  Secondly, choose the corresponding frequency and LoRaWAN class capabilities.
492 492  
493 -[[image:1652423046741-467.png||height="355" width="736"]]
494 494  
506 +[[image:1657094674045-755.png]]
507 +
495 495  (((
496 496  Finally, Application layer settings input the corresponding AppKey. Before saving the configuration, check that the data matches the device.
497 497  )))
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

Applications

Navigation

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