Wiki source code of Notes for Actility
Show last authors
author | version | line-number | content |
---|---|---|---|
1 | **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 | **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 | **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 | [[image:image-20220531084235-1.png]] | ||
39 | |||
40 | |||
41 | **The following items need to be configured:** | ||
42 | |||
43 | (% class="box" %) | ||
44 | ((( | ||
45 | // 1.Model **~-~->** Choose the Model | ||
46 | 2.Name **~-~->** Custom | ||
47 | 3.LRR-UUID **~-~->** **0061C0(aways is it)**-Gateway EUI // | ||
48 | |||
49 | // Such as: **0016C0-A840411E96744150**// | ||
50 | // 4.RF Region **~-~->** Choose the frequency// | ||
51 | ))) | ||
52 | |||
53 | [[image:image-20220531084316-2.png]] | ||
54 | |||
55 | |||
56 | **//Have need to put in latitude and longitude, and then click "CREATE".//** | ||
57 | |||
58 | [[image:image-20220531084401-3.png]] | ||
59 | |||
60 | |||
61 | == **2.3 Step 2. Access the gateway GUI** == | ||
62 | |||
63 | //Users need to update the API key and install the Certificate// | ||
64 | |||
65 | |||
66 | [[image:image-20220531084451-4.png]] | ||
67 | |||
68 | |||
69 | == **2.4 Step 3. Configure Station** == | ||
70 | |||
71 | //Users need to input Server URI, as well as install the CUPS certificate.// | ||
72 | |||
73 | |||
74 | **Just to clarify.** | ||
75 | |||
76 | (% class="box" %) | ||
77 | ((( | ||
78 | //CUPS Server URI **~-~->** Server Adress// | ||
79 | |||
80 | // Such as:[[https:~~/~~/community.thingpark.io:443>>url:https://community.thingpark.io/||style="background-color: rgb(250, 250, 250);"]]// | ||
81 | |||
82 | //CUPS certificate **~-~->** server certificate **(user can use the button to install the certificate by default)**// | ||
83 | ))) | ||
84 | |||
85 | [[image:image-20220531084527-5.png]] | ||
86 | |||
87 | Configure the gateway | ||
88 | |||
89 | |||
90 | == **2.5 Start Station** == | ||
91 | |||
92 | //When the user has finished the configuration, Please click Sace&Apply to start station to connect Actility Thingpark Enterprise.// | ||
93 | |||
94 | |||
95 | == **2.6 Successful Connection** == | ||
96 | |||
97 | //If users complete the above steps, which will see the live date in the Actility Thingpark Enterprise.// | ||
98 | |||
99 | |||
100 | [[image:image-20220525095038-6.png]] | ||
101 | |||
102 | |||
103 | //Station live date// | ||
104 | |||
105 | [[image:image-20220525095119-7.png]] | ||
106 | |||
107 | |||
108 | == **2.7 Trouble Shooting** == | ||
109 | |||
110 | //Users can check the station log on the logread/system log page.// | ||
111 | |||
112 | |||
113 | //Station Log~:// | ||
114 | |||
115 | [[image:image-20220525095149-8.png]] | ||
116 | |||
117 | |||
118 | //and recode the station log on the system/Recode log page.// | ||
119 | |||
120 | [[image:image-20220524163528-10.png]] | ||
121 | |||
122 | //Recore Log// | ||
123 | |||
124 | |||
125 | ((( | ||
126 | //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.// | ||
127 | ))) | ||
128 | |||
129 | ((( | ||
130 | //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.// | ||
131 | ))) | ||
132 | |||
133 | ((( | ||
134 | //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.// | ||
135 | ))) |