Changes for page Notes for Actility
Last modified by Bei Jinggeng on 2023/05/10 10:18
Change comment:
Uploaded new attachment "image-20230510101636-1.png", version {1}
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 1 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Kilight1 +XWiki.Bei - Content
-
... ... @@ -5,36 +5,35 @@ 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 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 - 32 32 (% style="color:blue" %)**What do you need to prepare** 33 33 34 - //A gateway that can access the internet normally//33 +A gateway that can access the internet normally 35 35 36 36 37 -== **2.2 Step 1. Add Gateway**==36 +== 2.2 Step 1. Add Gateway == 38 38 39 39 40 40 [[image:image-20220531084235-1.png||height="767" width="1332"]] ... ... @@ -55,28 +55,27 @@ 55 55 [[image:image-20220610095043-1.png]] 56 56 57 57 58 -(% style="color:blue" %)** //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".** 59 59 60 60 [[image:image-20220531085325-12.png]] 61 61 62 62 63 63 64 -== **2.3 Step 2. Access the gateway GUI**==63 +== 2.3 Step 2. Access the gateway GUI == 65 65 66 66 67 - //Users need to update the API key and install the Certificate//66 +Users need to update the API key and install the Certificate 68 68 69 69 70 70 [[image:image-20220531084451-4.png||height="683" width="1357"]] 71 71 72 72 72 +== 2.4 Step 3. Configure Station == 73 73 74 -== **2.4 Step 3. Configure Station** == 75 75 75 +Users need to input Server URI, as well as install the CUPS certificate. 76 76 77 -//Users need to input Server URI, as well as install the CUPS certificate.// 78 78 79 - 80 80 (% style="color:blue" %)**Just to clarify.** 81 81 82 82 (% class="box" %) ... ... @@ -93,16 +93,16 @@ 93 93 Configure the gateway 94 94 95 95 96 -== **2.5 Start Station**==94 +== 2.5 Start Station == 97 97 98 98 99 - //When the user has finished the configuration, Please click Sace&Apply to start station to connect Actility Thingpark Enterprise.//97 +When the user has finished the configuration, Please click Sace&Apply to start station to connect Actility Thingpark Enterprise. 100 100 101 101 102 -== **2.6 Successful Connection**==100 +== 2.6 Successful Connection == 103 103 104 104 105 - //If users complete the above steps, which will see the live date in the Actility Thingpark Enterprise.//103 +If users complete the above steps, which will see the live date in the Actility Thingpark Enterprise. 106 106 107 107 108 108 [[image:image-20220531084632-6.png||height="700" width="1403"]] ... ... @@ -115,33 +115,33 @@ 115 115 116 116 117 117 118 -== **2.7 Trouble Shooting**==116 +== 2.7 Trouble Shooting == 119 119 118 +=== 2.7.1 How do users view Basic Station logs and Record logs === 120 120 121 -=== **2.7.1 How do users view Basic Station logs and Record logs** === 122 122 123 - //Users can check the station log on the logread/system log page.//121 +Users can check the station log on the logread/system log page. 124 124 125 125 126 - //Station Log~://124 +**Station Log:** 127 127 128 128 [[image:image-20220531085014-10.png]] 129 129 130 130 131 131 132 - //and recode the station log on the system/Recode log page.//130 +**and recode the station log on the system/Recode log page.** 133 133 134 134 [[image:image-20220531084931-9.png]] 135 135 136 - //Recore Log//134 +**Recore Log** 137 137 138 138 139 -=== **2.7.2 How to solve the problem when "(400) TC credentials not found" is displayed in the log**===137 +=== 2.7.2 How to solve the problem when "(400) TC credentials not found" is displayed in the log === 140 140 141 141 142 142 In this case, the user needs to check whether the Gateway ID matches the UUID on Actility Thingpark. 143 143 144 -In addition, the user needs to regenerate new certificates in ThingPark GUI **(Advanced tab of the Base Station panel)**. 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. 145 145 146 146 [[image:image-20220822085416-2.png]] 147 147 ... ... @@ -151,13 +151,13 @@ 151 151 152 152 153 153 ((( 154 - //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.//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. 155 155 ))) 156 156 157 157 ((( 158 - //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.//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. 159 159 ))) 160 160 161 161 ((( 162 - //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. 163 163 )))
- image-20230510101636-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Bei - Size
-
... ... @@ -1,0 +1,1 @@ 1 +45.6 KB - Content