Changes for page Notes for Actility

Last modified by Bei Jinggeng on 2023/05/10 10:18
<
From version < 45.1 >
edited by Kilight Cao
on 2022/08/22 09:15
To version < 13.3 >
edited by Xiaoling
on 2022/05/24 16:35
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Kilight
1 +XWiki.Xiaoling
Content
... ... @@ -1,163 +1,119 @@
1 - **Table of** **Contents：**
1 + **Contents：**
2 2  
3 3  {{toc/}}
4 4  
5 += 1. Actility Thingpark Enterprise =
5 5  
7 +== 1.1 Introduction ==
6 6  
9 +=== 1.1.1 What is Actility Thingpark Enterprise ===
7 7  
8 -= **1. Actility Thingpark Enterprise** =
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.
9 9  
10 -== **1.1 Introduction** ==
13 += 2. Gateway Registration for Basics Station =
11 11  
12 -=== **1.1.1 What is Actility Thingpark Enterprise** ===
15 +== 2.1 Introduction ==
13 13  
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/]]
14 14  
15 -//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.//
19 +**Below list the support products and Requirements:**
16 16  
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]]
17 17  
18 -= **2. Gateway Registration for Basics Station** =
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/]]
19 19  
20 -== **2.1 Introduction** ==
25 +**What do you need to prepare**
21 21  
27 +A gateway that can access the internet normally
22 22  
23 -//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/]]//
29 +== 2.2 Step 1. Add Gateway ==
24 24  
31 +[[image:image-20220524163104-1.png]]
25 25  
26 -(% style="color:blue" %)**Below list the support products and Requirements:**
33 +Add Gateway_1
27 27  
28 -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]]//
29 -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/]]//
35 +**The following items need to be configured:**
30 30  
31 -
32 -(% style="color:blue" %)**What do you need to prepare**
33 -
34 -//A gateway that can access the internet normally//
35 -
36 -
37 -== **2.2 Step 1. Add Gateway** ==
38 -
39 -
40 -[[image:image-20220531084235-1.png||height="767" width="1332"]]
41 -
42 -
43 -(% style="color:blue" %)**The following items need to be configured:**
44 -
45 45  (% class="box" %)
46 46  (((
47 -// 1.Model               **~-~->** Choose the Model
48 - 2.Name                **~-~->** Custom
49 - 3.LRR-UUID  **~-~->** **0016C0(aways is it)**-Gateway EUI //
50 -
51 -// Such as: **0016C0-A840411E96744150**//
52 -// 4.RF Region  **~-~->** Choose the frequency//
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
53 53  )))
54 54  
55 -[[image:image-20220610095043-1.png]]
45 +[[image:image-20220524163206-2.png]]
56 56  
47 +Add Gateway_2
57 57  
58 -(% style="color:blue" %)**//Have need to put in latitude and longitude, and then click "CREATE".//**
49 +Have need to put in latitude and longitude, and then click **"CREATE"**.
59 59  
60 -[[image:image-20220531085325-12.png]]
51 +[[image:image-20220524163234-3.png]]
61 61  
53 +Add Gateway_3
62 62  
55 +== 2.3 Step 2. Access the gateway GUI ==
63 63  
64 -== **2.3 Step 2. Access the gateway GUI** ==
57 +User need to update the API key and install the Certificate
65 65  
59 +[[image:image-20220524163255-4.png]]
66 66  
67 -//Users need to update the API key and install the Certificate//
61 +Access the gateway GUI
68 68  
63 +== 2.4 Step 3. Configure Station ==
69 69  
70 -[[image:image-20220531084451-4.png||height="683" width="1357"]]
65 +User need to input Server URI, as well as install CUPS certificate.
71 71  
67 +**just to clarify.**
72 72  
73 -
74 -== **2.4 Step 3. Configure Station** ==
75 -
76 -
77 -//Users need to input Server URI, as well as install the CUPS certificate.//
78 -
79 -
80 -(% style="color:blue" %)**Just to clarify.**
81 -
82 82  (% class="box" %)
83 83  (((
84 -//CUPS Server URI **~-~->**  Server Address//
85 -
86 -// Such as:[[https:~~/~~/community.thingpark.io:443>>url:https://community.thingpark.io/||style="background-color: rgb(250, 250, 250);"]]//
87 -
88 -//CUPS certificate **~-~->**  server certificate **(user can use the button to install the certificate by default)**//
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)
89 89  )))
90 90  
91 -[[image:image-20220531084527-5.png||height="685" width="1370"]]
75 +[[image:image-20220524163334-5.png]]
92 92  
93 93  Configure the gateway
94 94  
79 +== 2.5 Start Station ==
95 95  
96 -== **2.5 Start Station** ==
81 +When the user has finished the configuration,Please click Sace&Apply to start station to connect Actility Thingpark Enterprise.
97 97  
83 +== 2.6 Siccessful Connection ==
98 98  
99 -//When the user has finished the configuration, Please click Sace&Apply to start station to connect Actility Thingpark Enterprise.//
85 +If user completes the above steps,which will see live date in the Actility Thingpark Enterprise.
100 100  
87 +[[image:image-20220524163358-6.png]]
101 101  
102 -== **2.6 Successful Connection** ==
89 +Station live date
103 103  
91 +[[image:image-20220524163420-7.png]]
104 104  
105 -//If users complete the above steps, which will see the live date in the Actility Thingpark Enterprise.//
93 +Station live date
106 106  
95 +== 2.7 Trouble Shooting ==
107 107  
108 -[[image:image-20220531084632-6.png||height="700" width="1403"]]
97 +User can check the station log in the logread/system log page.
109 109  
99 +[[image:image-20220524163455-8.png]]
110 110  
101 +Station Log
111 111  
112 -//Station live date//
103 +and recode the station log in the system/Recode log page.
113 113  
114 -[[image:image-20220531084747-7.png||height="591" width="1410"]]
105 +[[image:image-20220524163528-10.png]]
115 115  
107 +Recore Log
116 116  
117 -
118 -== **2.7 Trouble Shooting** ==
119 -
120 -
121 -=== **2.7.1 How do users view Basic Station logs and Record logs** ===
122 -
123 -//Users can check the station log on the logread/system log page.//
124 -
125 -
126 -//Station Log~://
127 -
128 -[[image:image-20220531085014-10.png]]
129 -
130 -
131 -
132 -//and recode the station log on the system/Recode log page.//
133 -
134 -[[image:image-20220531084931-9.png]]
135 -
136 -//Recore Log//
137 -
138 -
139 -=== **2.7.2 How to solve the problem when "(400) TC credentials not found" is displayed in the log** ===
140 -
141 -
142 -In this case, the user needs to check whether the Gateway ID matches the UUID on Actility Thingpark.
143 -
144 -In addition, the user needs to regenerate new certificates in ThingPark GUI **(Advanced tab of the Base Station panel)**.
145 -
146 -[[image:image-20220822085416-2.png]]
147 -
148 -[[image:image-20220822091137-3.png]]
149 -
150 -[[image:image-20220822091229-4.png||height="569" width="1267"]]
151 -
152 -
153 153  (((
154 -//The reason of fail to join Actility is that our end node use (% style="color:blue" %)**RX2DR=3**(%%) for join. this is the default setting for TTN and many LoRaWAN servers.//
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.
155 155  )))
156 156  
157 157  (((
158 -//The Actility use (% style="color:blue" %)**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.//
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.
159 159  )))
160 160  
161 161  (((
162 -//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.//
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.
163 163  )))
image-20220525094736-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -51.1 KB
Content
image-20220525094818-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -68.8 KB
Content
image-20220525094855-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -48.1 KB
Content
image-20220525094925-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -73.3 KB
Content
image-20220525095011-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -83.0 KB
Content
image-20220525095038-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -49.0 KB
Content
image-20220525095119-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -53.3 KB
Content
image-20220525095149-8.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -191.2 KB
Content
image-20220531084235-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -114.6 KB
Content
image-20220531084316-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -53.4 KB
Content
image-20220531084401-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -27.1 KB
Content
image-20220531084451-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -82.8 KB
Content
image-20220531084527-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -83.0 KB
Content
image-20220531084632-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -100.6 KB
Content
image-20220531084747-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -114.1 KB
Content
image-20220531084858-8.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -175.3 KB
Content
image-20220531084931-9.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -36.3 KB
Content
image-20220531085014-10.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -67.7 KB
Content
image-20220531085244-11.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -55.7 KB
Content
image-20220531085325-12.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -29.2 KB
Content
image-20220610095043-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -58.6 KB
Content
image-20220822085346-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -48.0 KB
Content
image-20220822085416-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -23.0 KB
Content
image-20220822091137-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -51.7 KB
Content
image-20220822091229-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Kilight
Size
... ... @@ -1,1 +1,0 @@
1 -50.9 KB
Content

Applications

Navigation

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