Wiki source code of Notes for Actility
Last modified by Bei Jinggeng on 2023/05/10 10:18
Show last authors
author | version | line-number | content |
---|---|---|---|
1 | **Table of** **Contents:** | ||
2 | |||
3 | {{toc/}} | ||
4 | |||
5 | |||
6 | |||
7 | |||
8 | = 1. Actility Thingpark Enterprise = | ||
9 | |||
10 | == 1.1 Introduction == | ||
11 | |||
12 | === 1.1.1 What is Actility Thingpark Enterprise === | ||
13 | |||
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. | ||
16 | |||
17 | |||
18 | = 2. Gateway Registration for Basics Station = | ||
19 | |||
20 | == 2.1 Introduction == | ||
21 | |||
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/]] | ||
24 | |||
25 | |||
26 | (% style="color:blue" %)**Below list the support products and Requirements:** | ||
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/]] | ||
30 | |||
31 | (% style="color:blue" %)**What do you need to prepare** | ||
32 | |||
33 | A gateway that can access the internet normally | ||
34 | |||
35 | |||
36 | == 2.2 Step 1. Add Gateway == | ||
37 | |||
38 | |||
39 | [[image:image-20220531084235-1.png||height="767" width="1332"]] | ||
40 | |||
41 | |||
42 | (% style="color:blue" %)**The following items need to be configured:** | ||
43 | |||
44 | (% class="box" %) | ||
45 | ((( | ||
46 | // 1.Model **~-~->** Choose the Model | ||
47 | 2.Name **~-~->** Custom | ||
48 | 3.LRR-UUID **~-~->** **0016C0(aways is it)**-Gateway EUI // | ||
49 | |||
50 | // Such as: **0016C0-A840411E96744150**// | ||
51 | // 4.RF Region **~-~->** Choose the frequency// | ||
52 | ))) | ||
53 | |||
54 | [[image:image-20220610095043-1.png]] | ||
55 | |||
56 | |||
57 | (% style="color:blue" %)**Have need to put in latitude and longitude, and then click "CREATE".** | ||
58 | |||
59 | [[image:image-20220531085325-12.png]] | ||
60 | |||
61 | |||
62 | |||
63 | == 2.3 Step 2. Access the gateway GUI == | ||
64 | |||
65 | |||
66 | Users need to update the API key and install the Certificate | ||
67 | |||
68 | |||
69 | [[image:image-20220531084451-4.png||height="683" width="1357"]] | ||
70 | |||
71 | |||
72 | == 2.4 Step 3. Configure Station == | ||
73 | |||
74 | |||
75 | Users need to input Server URI, as well as install the CUPS certificate. | ||
76 | |||
77 | |||
78 | (% style="color:blue" %)**Just to clarify.** | ||
79 | |||
80 | (% class="box" %) | ||
81 | ((( | ||
82 | //CUPS Server URI **~-~->** Server Address// | ||
83 | |||
84 | // Such as:[[https:~~/~~/community.thingpark.io:443>>url:https://community.thingpark.io/||style="background-color: rgb(250, 250, 250);"]]// | ||
85 | |||
86 | //CUPS certificate **~-~->** server certificate **(user can use the button to install the certificate by default)**// | ||
87 | ))) | ||
88 | |||
89 | [[image:image-20220531084527-5.png||height="685" width="1370"]] | ||
90 | |||
91 | Configure the gateway | ||
92 | |||
93 | |||
94 | == 2.5 Start Station == | ||
95 | |||
96 | |||
97 | When the user has finished the configuration, Please click Sace&Apply to start station to connect Actility Thingpark Enterprise. | ||
98 | |||
99 | |||
100 | == 2.6 Successful Connection == | ||
101 | |||
102 | |||
103 | If users complete the above steps, which will see the live date in the Actility Thingpark Enterprise. | ||
104 | |||
105 | |||
106 | [[image:image-20220531084632-6.png||height="700" width="1403"]] | ||
107 | |||
108 | |||
109 | |||
110 | //Station live date// | ||
111 | |||
112 | [[image:image-20220531084747-7.png||height="591" width="1410"]] | ||
113 | |||
114 | |||
115 | |||
116 | == 2.7 Trouble Shooting == | ||
117 | |||
118 | === 2.7.1 How do users view Basic Station logs and Record logs === | ||
119 | |||
120 | |||
121 | Users can check the station log on the logread/system log page. | ||
122 | |||
123 | |||
124 | **Station Log:** | ||
125 | |||
126 | [[image:image-20220531085014-10.png]] | ||
127 | |||
128 | |||
129 | |||
130 | **and recode the station log on the system/Recode log page.** | ||
131 | |||
132 | [[image:image-20220531084931-9.png]] | ||
133 | |||
134 | **Recore Log** | ||
135 | |||
136 | |||
137 | === 2.7.2 How to solve the problem when "(400) TC credentials not found" is displayed in the log === | ||
138 | |||
139 | |||
140 | In this case, the user needs to check whether the Gateway ID matches the UUID on Actility Thingpark. | ||
141 | |||
142 | In addition, the user needs to regenerate new certificates in ThingPark GUI **(Advanced tab of the Base Station panel)**, Then wait 2-3 minutes to refresh the ThingPark GUI to see if the gateway is online. | ||
143 | |||
144 | [[image:image-20220822085416-2.png]] | ||
145 | |||
146 | [[image:image-20220822091137-3.png]] | ||
147 | |||
148 | [[image:image-20220822091229-4.png||height="569" width="1267"]] | ||
149 | |||
150 | |||
151 | ((( | ||
152 | 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. | ||
153 | ))) | ||
154 | |||
155 | ((( | ||
156 | 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. | ||
157 | ))) | ||
158 | |||
159 | ((( | ||
160 | 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. | ||
161 | |||
162 | === 2.7.2 When all the parameters of the device are filled in correctly, it still cannot join the network === | ||
163 | |||
164 | You can not choose the preset template and use the general settings to eliminate the interference caused by the preset template | ||
165 | |||
166 | [[image:image-20230510101636-1.png]] | ||
167 | |||
168 | **error** | ||
169 | |||
170 | [[image:image-20230510101714-3.png]] | ||
171 | |||
172 | **right** | ||
173 | ))) |