Wiki source code of Notes for Actility
Version 44.1 by Kilight Cao on 2022/08/22 09:12
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 | |||
32 | |||
33 | (% style="color:blue" %)**What do you need to prepare** | ||
34 | |||
35 | //A gateway that can access the internet normally// | ||
36 | |||
37 | |||
38 | == **2.2 Step 1. Add Gateway** == | ||
39 | |||
40 | |||
41 | [[image:image-20220531084235-1.png||height="767" width="1332"]] | ||
42 | |||
43 | |||
44 | (% style="color:blue" %)**The following items need to be configured:** | ||
45 | |||
46 | (% class="box" %) | ||
47 | ((( | ||
48 | // 1.Model **~-~->** Choose the Model | ||
49 | 2.Name **~-~->** Custom | ||
50 | 3.LRR-UUID **~-~->** **0016C0(aways is it)**-Gateway EUI // | ||
51 | |||
52 | // Such as: **0016C0-A840411E96744150**// | ||
53 | // 4.RF Region **~-~->** Choose the frequency// | ||
54 | ))) | ||
55 | |||
56 | [[image:image-20220610095043-1.png]] | ||
57 | |||
58 | |||
59 | (% style="color:blue" %)**//Have need to put in latitude and longitude, and then click "CREATE".//** | ||
60 | |||
61 | [[image:image-20220531085325-12.png]] | ||
62 | |||
63 | |||
64 | |||
65 | == **2.3 Step 2. Access the gateway GUI** == | ||
66 | |||
67 | |||
68 | //Users need to update the API key and install the Certificate// | ||
69 | |||
70 | |||
71 | [[image:image-20220531084451-4.png||height="683" width="1357"]] | ||
72 | |||
73 | |||
74 | |||
75 | == **2.4 Step 3. Configure Station** == | ||
76 | |||
77 | |||
78 | //Users need to input Server URI, as well as install the CUPS certificate.// | ||
79 | |||
80 | |||
81 | (% style="color:blue" %)**Just to clarify.** | ||
82 | |||
83 | (% class="box" %) | ||
84 | ((( | ||
85 | //CUPS Server URI **~-~->** Server Address// | ||
86 | |||
87 | // Such as:[[https:~~/~~/community.thingpark.io:443>>url:https://community.thingpark.io/||style="background-color: rgb(250, 250, 250);"]]// | ||
88 | |||
89 | //CUPS certificate **~-~->** server certificate **(user can use the button to install the certificate by default)**// | ||
90 | ))) | ||
91 | |||
92 | [[image:image-20220531084527-5.png||height="685" width="1370"]] | ||
93 | |||
94 | Configure the gateway | ||
95 | |||
96 | |||
97 | == **2.5 Start Station** == | ||
98 | |||
99 | |||
100 | //When the user has finished the configuration, Please click Sace&Apply to start station to connect Actility Thingpark Enterprise.// | ||
101 | |||
102 | |||
103 | == **2.6 Successful Connection** == | ||
104 | |||
105 | |||
106 | //If users complete the above steps, which will see the live date in the Actility Thingpark Enterprise.// | ||
107 | |||
108 | |||
109 | [[image:image-20220531084632-6.png||height="700" width="1403"]] | ||
110 | |||
111 | |||
112 | |||
113 | //Station live date// | ||
114 | |||
115 | [[image:image-20220531084747-7.png||height="591" width="1410"]] | ||
116 | |||
117 | |||
118 | |||
119 | == **2.7 Trouble Shooting** == | ||
120 | |||
121 | |||
122 | //Users can check the station log on the logread/system log page.// | ||
123 | |||
124 | |||
125 | //Station Log~:// | ||
126 | |||
127 | [[image:image-20220531085014-10.png]] | ||
128 | |||
129 | |||
130 | |||
131 | //and recode the station log on the system/Recode log page.// | ||
132 | |||
133 | [[image:image-20220531084931-9.png]] | ||
134 | |||
135 | //Recore Log// | ||
136 | |||
137 | |||
138 | |||
139 | ((( | ||
140 | //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.// | ||
141 | ))) | ||
142 | |||
143 | ((( | ||
144 | //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.// | ||
145 | ))) | ||
146 | |||
147 | ((( | ||
148 | //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.// | ||
149 | ))) |