Wiki source code of Notes for Actility
Last modified by Bei Jinggeng on 2023/05/10 10:18
Hide last authors
author | version | line-number | content |
---|---|---|---|
40.2 | 1 | **Table of** **Contents:** | |
1.2 | 2 | ||
1.1 | 3 | {{toc/}} | |
4 | |||
23.4 | 5 | ||
6 | |||
7 | |||
46.2 | 8 | = 1. Actility Thingpark Enterprise = | |
1.1 | 9 | ||
46.2 | 10 | == 1.1 Introduction == | |
1.1 | 11 | ||
46.2 | 12 | === 1.1.1 What is Actility Thingpark Enterprise === | |
1.1 | 13 | ||
14 | |||
46.2 | 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. | |
1.1 | 16 | ||
17 | |||
46.2 | 18 | = 2. Gateway Registration for Basics Station = | |
1.1 | 19 | ||
46.2 | 20 | == 2.1 Introduction == | |
15.1 | 21 | ||
22 | |||
46.2 | 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/]] | |
15.1 | 24 | ||
25 | |||
40.2 | 26 | (% style="color:blue" %)**Below list the support products and Requirements:** | |
1.1 | 27 | ||
46.2 | 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/]] | ||
1.1 | 30 | ||
40.2 | 31 | (% style="color:blue" %)**What do you need to prepare** | |
1.1 | 32 | ||
46.2 | 33 | A gateway that can access the internet normally | |
1.1 | 34 | ||
35 | |||
46.2 | 36 | == 2.2 Step 1. Add Gateway == | |
15.1 | 37 | ||
40.2 | 38 | ||
35.2 | 39 | [[image:image-20220531084235-1.png||height="767" width="1332"]] | |
1.1 | 40 | ||
1.2 | 41 | ||
40.2 | 42 | (% style="color:blue" %)**The following items need to be configured:** | |
1.2 | 43 | ||
1.4 | 44 | (% class="box" %) | |
45 | ((( | ||
15.1 | 46 | // 1.Model **~-~->** Choose the Model | |
47 | 2.Name **~-~->** Custom | ||
40.1 | 48 | 3.LRR-UUID **~-~->** **0016C0(aways is it)**-Gateway EUI // | |
15.1 | 49 | ||
50 | // Such as: **0016C0-A840411E96744150**// | ||
51 | // 4.RF Region **~-~->** Choose the frequency// | ||
1.4 | 52 | ))) | |
1.2 | 53 | ||
38.1 | 54 | [[image:image-20220610095043-1.png]] | |
1.2 | 55 | ||
56 | |||
46.2 | 57 | (% style="color:blue" %)**Have need to put in latitude and longitude, and then click "CREATE".** | |
15.1 | 58 | ||
36.2 | 59 | [[image:image-20220531085325-12.png]] | |
1.2 | 60 | ||
61 | |||
40.2 | 62 | ||
46.2 | 63 | == 2.3 Step 2. Access the gateway GUI == | |
1.2 | 64 | ||
40.2 | 65 | ||
46.2 | 66 | Users need to update the API key and install the Certificate | |
15.1 | 67 | ||
68 | |||
36.3 | 69 | [[image:image-20220531084451-4.png||height="683" width="1357"]] | |
1.2 | 70 | ||
71 | |||
46.2 | 72 | == 2.4 Step 3. Configure Station == | |
40.2 | 73 | ||
1.2 | 74 | ||
46.2 | 75 | Users need to input Server URI, as well as install the CUPS certificate. | |
40.2 | 76 | ||
1.2 | 77 | ||
40.3 | 78 | (% style="color:blue" %)**Just to clarify.** | |
15.1 | 79 | ||
1.4 | 80 | (% class="box" %) | |
81 | ((( | ||
39.1 | 82 | //CUPS Server URI **~-~->** Server Address// | |
15.1 | 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)**// | ||
1.4 | 87 | ))) | |
1.2 | 88 | ||
36.3 | 89 | [[image:image-20220531084527-5.png||height="685" width="1370"]] | |
1.2 | 90 | ||
91 | Configure the gateway | ||
92 | |||
93 | |||
46.2 | 94 | == 2.5 Start Station == | |
1.2 | 95 | ||
40.2 | 96 | ||
46.2 | 97 | When the user has finished the configuration, Please click Sace&Apply to start station to connect Actility Thingpark Enterprise. | |
1.2 | 98 | ||
23.8 | 99 | ||
46.2 | 100 | == 2.6 Successful Connection == | |
1.2 | 101 | ||
40.2 | 102 | ||
46.2 | 103 | If users complete the above steps, which will see the live date in the Actility Thingpark Enterprise. | |
15.1 | 104 | ||
105 | |||
36.4 | 106 | [[image:image-20220531084632-6.png||height="700" width="1403"]] | |
1.2 | 107 | ||
108 | |||
40.2 | 109 | ||
15.1 | 110 | //Station live date// | |
111 | |||
36.4 | 112 | [[image:image-20220531084747-7.png||height="591" width="1410"]] | |
1.2 | 113 | ||
114 | |||
40.2 | 115 | ||
46.2 | 116 | == 2.7 Trouble Shooting == | |
1.2 | 117 | ||
46.2 | 118 | === 2.7.1 How do users view Basic Station logs and Record logs === | |
40.2 | 119 | ||
45.1 | 120 | ||
46.2 | 121 | Users can check the station log on the logread/system log page. | |
15.1 | 122 | ||
123 | |||
46.2 | 124 | **Station Log:** | |
15.1 | 125 | ||
33.2 | 126 | [[image:image-20220531085014-10.png]] | |
1.2 | 127 | ||
128 | |||
40.2 | 129 | ||
46.2 | 130 | **and recode the station log on the system/Recode log page.** | |
1.2 | 131 | ||
32.2 | 132 | [[image:image-20220531084931-9.png]] | |
1.2 | 133 | ||
46.2 | 134 | **Recore Log** | |
1.2 | 135 | ||
23.11 | 136 | ||
46.2 | 137 | === 2.7.2 How to solve the problem when "(400) TC credentials not found" is displayed in the log === | |
40.2 | 138 | ||
45.1 | 139 | ||
140 | In this case, the user needs to check whether the Gateway ID matches the UUID on Actility Thingpark. | ||
141 | |||
46.1 | 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. | |
45.1 | 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 | |||
1.5 | 151 | ((( | |
46.2 | 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. | |
1.5 | 153 | ))) | |
1.2 | 154 | ||
1.5 | 155 | ((( | |
46.2 | 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. | |
1.5 | 157 | ))) | |
1.2 | 158 | ||
1.5 | 159 | ((( | |
46.2 | 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. | |
50.1 | 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** | ||
1.5 | 173 | ))) |