Changes for page Notes for Actility

Last modified by Bei Jinggeng on 2023/05/10 10:18
<
From version < 13.2 >
edited by Xiaoling
on 2022/05/24 16:35
To version < 17.1 >
edited by Xiaoling
on 2022/05/25 09:48
>
Change comment: Uploaded new attachment "image-20220525094818-2.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -2,74 +2,87 @@
2 2  
3 3  {{toc/}}
4 4  
5 -= 1. Actility Thingpark Enterprise =
5 += **1. Actility Thingpark Enterprise** =
6 6  
7 -== 1.1 Introduction ==
7 +== **1.1 Introduction** ==
8 8  
9 -=== 1.1.1 What is Actility Thingpark Enterprise ===
9 +=== **1.1.1 What is Actility Thingpark Enterprise** ===
10 10  
11 -ThingPark Enterprise is an IoT connectivity management solution allowing to deploy a dedicated and fully controlled LoRaWAN® network for a fast use case enablement. All components of the network, including sensors, gateways and data routing are managed from a unique and easy-to-use user interface. The ThingPark Enterprise allows full flexibility in the choice of gateways or devices. It is also a flexible, scalable and secure solution allowing to start with a Proof-of-Concept (PoC) and scale to full deployments.
12 12  
13 -= 2. Gateway Registration for Basics Station =
12 +//ThingPark Enterprise is an IoT connectivity management solution allowing to the deployment of a dedicated and fully controlled LoRaWAN® network for a fast use case enablement. All components of the network, including sensors, gateways, and data routing are managed from a unique and easy-to-use user interface. The ThingPark Enterprise allows full flexibility in the choice of gateways or devices. It is also a flexible, scalable, and secure solution allowing to start with a Proof-of-Concept (POC) and scale to full deployments.//
14 14  
15 -== 2.1 Introduction ==
16 16  
17 -The LoRa Basics™ Station protocol simplifies management of large scale LoRaWAN networks. [[The LoRa Basics Station doc>>url:https://www.thethingsindustries.com/docs/gateways/lora-basics-station/]]
15 += **2. Gateway Registration for Basics Station** =
18 18  
17 +== **2.1 Introduction** ==
18 +
19 +
20 +//The LoRa Basics™ Station protocol simplifies the management of large-scale LoRaWAN networks. [[The LoRa Basics Station doc>>url:https://www.thethingsindustries.com/docs/gateways/lora-basics-station/]]//
21 +
22 +
19 19  **Below list the support products and Requirements:**
20 20  
21 -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]]
25 +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]]//
26 +1. //Firmware version since:[[lgw~~-~~-build-v5.4.1651822913>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Test_Firmware/lgw--build-v5.4.1651822913-20220506-1543/]]//
22 22  
23 -1. Firmware version since :[[lgw~~-~~-build-v5.4.1651822913>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Test_Firmware/lgw--build-v5.4.1651822913-20220506-1543/]]
24 24  
25 25  **What do you need to prepare**
26 26  
27 -A gateway that can access the internet normally
31 +//A gateway that can access the internet normally//
28 28  
29 -== 2.2 Step 1. Add Gateway ==
30 30  
34 +== **2.2 Step 1. Add Gateway** ==
35 +
31 31  [[image:image-20220524163104-1.png]]
32 32  
33 -Add Gateway_1
34 34  
39 +
35 35  **The following items need to be configured:**
36 36  
37 37  (% class="box" %)
38 38  (((
39 - 1.Model                **~-~->** Choose the Model
40 - 2.Name                 **~-~->** Custom
41 - 3.LRR-UUID  **~-~->** Enter 0061C0-Gateway EUI ,Such as:0016C0-A840411E96744150
42 - 4.RF Region  **~-~->** Choose the frequency
44 +// 1.Model               **~-~->** Choose the Model
45 + 2.Name                **~-~->** Custom
46 + 3.LRR-UUID  **~-~->** **0061C0(aways is it)**-Gateway EUI //
47 +
48 +// Such as: **0016C0-A840411E96744150**//
49 +// 4.RF Region  **~-~->** Choose the frequency//
43 43  )))
44 44  
45 45  [[image:image-20220524163206-2.png]]
46 46  
47 -Add Gateway_2
48 48  
49 -Have need to put in latitude and longitude, and then click **"CREATE"**.
50 50  
56 +**//Have need to put in latitude and longitude, and then click "CREATE".//**
57 +
51 51  [[image:image-20220524163234-3.png]]
52 52  
53 -Add Gateway_3
54 54  
55 -== 2.3 Step 2. Access the gateway GUI ==
56 56  
57 -User need to update the API key and install the Certificate
62 +== **2.3 Step 2. Access the gateway GUI** ==
58 58  
64 +
65 +//Users need to update the API key and install the Certificate//
66 +
67 +
59 59  [[image:image-20220524163255-4.png]]
60 60  
61 -Access the gateway GUI
62 62  
63 -== 2.4 Step 3. Configure Station ==
71 +== **2.4 Step 3. Configure Station** ==
64 64  
65 -User need to input Server URI, as well as install CUPS certificate.
66 66  
67 -**just to clarify.**
74 +//Users need to input Server URI, as well as install the CUPS certificate.//
68 68  
76 +
77 +**Just to clarify.**
78 +
69 69  (% class="box" %)
70 70  (((
71 -CUPS Server URI **~-~->**  Server Adress Such as:[[https:~~/~~/community.thingpark.io:443>>url:https://community.thingpark.io/||style="background-color: rgb(250, 250, 250);"]]
72 -CUPS certificate **~-~->**  Server CA(user can use the button to install the certificate by default)
81 +//CUPS Server URI **~-~->**  Server Adress//
82 +
83 +// Such as:[[https:~~/~~/community.thingpark.io:443>>url:https://community.thingpark.io/||style="background-color: rgb(250, 250, 250);"]]//
84 +
85 +//CUPS certificate **~-~->**  server certificate **(user can use the button to install the certificate by default)**//
73 73  )))
74 74  
75 75  [[image:image-20220524163334-5.png]]
... ... @@ -76,44 +76,51 @@
76 76  
77 77  Configure the gateway
78 78  
79 -== 2.5 Start Station ==
80 80  
81 -When the user has finished the configuration,Please click Sace&Apply to start station to connect Actility Thingpark Enterprise.
93 +== **2.5 Start Station** ==
82 82  
83 -== 2.6 Siccessful Connection ==
95 +//When the user has finished the configuration, Please click Sace&Apply to start station to connect Actility Thingpark Enterprise.//
84 84  
85 -If user completes the above steps,which will see live date in the Actility Thingpark Enterprise.
97 +== **2.6 Successful Connection** ==
86 86  
99 +
100 +//If users complete the above steps, which will see the live date in the Actility Thingpark Enterprise.//
101 +
102 +
87 87  [[image:image-20220524163358-6.png]]
88 88  
89 -Station live date
90 90  
106 +
107 +//Station live date//
108 +
91 91  [[image:image-20220524163420-7.png]]
92 92  
93 -Station live date
94 94  
95 -== 2.7 Trouble Shooting ==
112 +== **2.7 Trouble Shooting** ==
96 96  
97 -User can check the station log in the logread/system log page.
98 98  
115 +//Users can check the station log on the logread/system log page.//
116 +
117 +
118 +//Station Log~://
119 +
99 99  [[image:image-20220524163455-8.png]]
100 100  
101 -Station Log
102 102  
103 -and recode the station log in the system/Recode log page.
123 +//and recode the station log on the system/Recode log page.//
104 104  
105 105  [[image:image-20220524163528-10.png]]
106 106  
107 -Recore Log
127 +//Recore Log//
108 108  
109 109  (((
110 -The reason of fail to join Actility is that our end node use RX2DR=3 for join. this is the default setting for TTN and many LoRaWAN servers.
130 +//The reason of fail to join Actility is that our end node use RX2DR=3 for join. this is the default setting for TTN and many LoRaWAN servers.//
111 111  )))
112 112  
113 113  (((
114 -The Actility use RX2DR=0 for Join, when Actility sends a Join Accept, due to RX2DR different, the end node can not receive the Join Accept message from Actility so keep joining.
134 +//The Actility use RX2DR=0 for Join, when Actility sends a Join Accept, due to RX2DR different, the end node can not receive the Join Accept message from Actility so keep joining.//
115 115  )))
116 116  
117 117  (((
118 -Some of End Nodes already support the change on RX2DR for OTAA join, in this case, use need to write AT+RX2DR=0. Please contact Dragino support for more info if the product doesn't support it.
138 +//Some of End Nodes already support the change on RX2DR for OTAA join, in this case, use need to write AT+RX2DR=0. Please contact Dragino support for more info if the product doesn't support it.//
119 119  )))
image-20220525094736-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +51.1 KB
Content
image-20220525094818-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +68.8 KB
Content

Applications

Navigation

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