Changes for page Notes for Actility

Last modified by Bei Jinggeng on 2023/05/10 10:18
<
From version < 39.1 >
edited by Kilight Cao
on 2022/06/10 09:55
To version < 47.1 >
edited by Bei Jinggeng
on 2023/05/10 10:16
>
Change comment: Uploaded new attachment "image-20230510101636-1.png", version {1}

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Kilight
1 +XWiki.Bei
Content
... ... @@ -1,4 +1,4 @@
1 - **Contents：**
1 + **Table of** **Contents：**
2 2  
3 3  {{toc/}}
4 4  
... ... @@ -5,46 +5,47 @@
5 5  
6 6  
7 7  
8 -= **1. Actility Thingpark Enterprise** =
8 += 1. Actility Thingpark Enterprise =
9 9  
10 -== **1.1 Introduction** ==
10 +== 1.1 Introduction ==
11 11  
12 -=== **1.1.1 What is Actility Thingpark Enterprise** ===
12 +=== 1.1.1 What is Actility Thingpark Enterprise ===
13 13  
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.//
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 16  
17 17  
18 -= **2. Gateway Registration for Basics Station** =
18 += 2. Gateway Registration for Basics Station =
19 19  
20 -== **2.1 Introduction** ==
20 +== 2.1 Introduction ==
21 21  
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/]]//
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 24  
25 25  
26 -**Below list the support products and Requirements:**
26 +(% style="color:blue" %)**Below list the support products and Requirements:**
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/]]//
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 30  
31 -**What do you need to prepare**
31 +(% style="color:blue" %)**What do you need to prepare**
32 32  
33 -//A gateway that can access the internet normally//
33 +A gateway that can access the internet normally
34 34  
35 35  
36 -== **2.2 Step 1. Add Gateway** ==
36 +== 2.2 Step 1. Add Gateway ==
37 37  
38 +
38 38  [[image:image-20220531084235-1.png||height="767" width="1332"]]
39 39  
40 40  
41 -**The following items need to be configured:**
42 +(% style="color:blue" %)**The following items need to be configured:**
42 42  
43 43  (% class="box" %)
44 44  (((
45 45  // 1.Model               **~-~->** Choose the Model
46 46   2.Name                **~-~->** Custom
47 - 3.LRR-UUID  **~-~->** **0061C0(aways is it)**-Gateway EUI //
48 + 3.LRR-UUID  **~-~->** **0016C0(aways is it)**-Gateway EUI //
48 48  
49 49  // Such as: **0016C0-A840411E96744150**//
50 50  // 4.RF Region  **~-~->** Choose the frequency//
... ... @@ -53,26 +53,29 @@
53 53  [[image:image-20220610095043-1.png]]
54 54  
55 55  
56 -**//Have need to put in latitude and longitude, and then click "CREATE".//**
57 +(% style="color:blue" %)**Have need to put in latitude and longitude, and then click "CREATE".**
57 57  
58 58  [[image:image-20220531085325-12.png]]
59 59  
60 60  
61 -== **2.3 Step 2. Access the gateway GUI** ==
62 62  
63 -//Users need to update the API key and install the Certificate//
63 +== 2.3 Step 2. Access the gateway GUI ==
64 64  
65 65  
66 +Users need to update the API key and install the Certificate
67 +
68 +
66 66  [[image:image-20220531084451-4.png||height="683" width="1357"]]
67 67  
68 68  
69 -== **2.4 Step 3. Configure Station** ==
72 +== 2.4 Step 3. Configure Station ==
70 70  
71 -//Users need to input Server URI, as well as install the CUPS certificate.//
72 72  
75 +Users need to input Server URI, as well as install the CUPS certificate.
73 73  
74 -**Just to clarify.**
75 75  
78 +(% style="color:blue" %)**Just to clarify.**
79 +
76 76  (% class="box" %)
77 77  (((
78 78  //CUPS Server URI **~-~->**  Server Address//
... ... @@ -87,49 +87,71 @@
87 87  Configure the gateway
88 88  
89 89  
90 -== **2.5 Start Station** ==
94 +== 2.5 Start Station ==
91 91  
92 -//When the user has finished the configuration, Please click Sace&Apply to start station to connect Actility Thingpark Enterprise.//
93 93  
97 +When the user has finished the configuration, Please click Sace&Apply to start station to connect Actility Thingpark Enterprise.
94 94  
95 -== **2.6 Successful Connection** ==
96 96  
97 -//If users complete the above steps, which will see the live date in the Actility Thingpark Enterprise.//
100 +== 2.6 Successful Connection ==
98 98  
99 99  
103 +If users complete the above steps, which will see the live date in the Actility Thingpark Enterprise.
104 +
105 +
100 100  [[image:image-20220531084632-6.png||height="700" width="1403"]]
101 101  
102 102  
109 +
103 103  //Station live date//
104 104  
105 105  [[image:image-20220531084747-7.png||height="591" width="1410"]]
106 106  
107 107  
108 -== **2.7 Trouble Shooting** ==
109 109  
110 -//Users can check the station log on the logread/system log page.//
116 +== 2.7 Trouble Shooting ==
111 111  
118 +=== 2.7.1 How do users view Basic Station logs and Record logs ===
112 112  
113 -//Station Log~://
114 114  
121 +Users can check the station log on the logread/system log page.
122 +
123 +
124 +**Station Log:**
125 +
115 115  [[image:image-20220531085014-10.png]]
116 116  
117 117  
118 -//and recode the station log on the system/Recode log page.//
119 119  
130 +**and recode the station log on the system/Recode log page.**
131 +
120 120  [[image:image-20220531084931-9.png]]
121 121  
122 -//Recore Log//
134 +**Recore Log**
123 123  
124 124  
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 +
125 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.//
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.
127 127  )))
128 128  
129 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.//
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.
131 131  )))
132 132  
133 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.//
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.
135 135  )))
image-20220822085346-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +48.0 KB
Content
image-20220822085416-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +23.0 KB
Content
image-20220822091137-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +51.7 KB
Content
image-20220822091229-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Kilight
Size
... ... @@ -1,0 +1,1 @@
1 +50.9 KB
Content
image-20230510101636-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +45.6 KB
Content

Applications

Navigation

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