Changes for page Notes for Actility
Last modified by Bei Jinggeng on 2023/05/10 10:18
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 4 removed)
Details
- Page properties
-
- Content
-
... ... @@ -2,87 +2,74 @@ 2 2 3 3 {{toc/}} 4 4 5 -= **1. Actility Thingpark Enterprise**=5 += 1. Actility Thingpark Enterprise = 6 6 7 -== **1.1 Introduction**==7 +== 1.1 Introduction == 8 8 9 -=== **1.1.1 What is Actility Thingpark Enterprise**===9 +=== 1.1.1 What is Actility Thingpark Enterprise === 10 10 11 +ThingPark Enterprise is an IoT connectivity management solution allowing to deploy 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. 11 11 12 - //ThingParkEnterpriseisan IoT connectivity management solution allowing to the deployment ofadedicated and fullycontrolled LoRaWAN® network for a fast use case enablement. All components of the network, includingsensors, gateways, and data routing are managed from a unique and easy-to-use userinterface. The ThingPark Enterprise allows full flexibility inthe choice ofgatewaysordevices. It isalso a flexible, scalable, andsecuresolutionallowingto start with a Proof-of-Concept(POC) and scale to full deployments.//13 += 2. Gateway Registration for Basics Station = 13 13 15 +== 2.1 Introduction == 14 14 15 - = **2. GatewayRegistration for Basics Station**=17 +The LoRa Basics™ Station protocol simplifies management of large scale LoRaWAN networks. [[The LoRa Basics Station doc>>url:https://www.thethingsindustries.com/docs/gateways/lora-basics-station/]] 16 16 17 -== **2.1 Introduction** == 18 - 19 - 20 -//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/]]// 21 - 22 - 23 23 **Below list the support products and Requirements:** 24 24 25 -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]]// 26 -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/]]// 21 +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]] 27 27 23 +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 28 29 29 **What do you need to prepare** 30 30 31 - //A gateway that can access the internet normally//27 +A gateway that can access the internet normally 32 32 29 +== 2.2 Step 1. Add Gateway == 33 33 34 -== **2.2 Step 1. Add Gateway** == 35 - 36 36 [[image:image-20220524163104-1.png]] 37 37 33 +Add Gateway_1 38 38 39 - 40 40 **The following items need to be configured:** 41 41 42 42 (% class="box" %) 43 43 ((( 44 -// 1.Model **~-~->** Choose the Model 45 - 2.Name **~-~->** Custom 46 - 3.LRR-UUID **~-~->** **0061C0(aways is it)**-Gateway EUI // 47 - 48 -// Such as: **0016C0-A840411E96744150**// 49 -// 4.RF Region **~-~->** Choose the frequency// 39 + 1.Model **~-~->** Choose the Model 40 + 2.Name **~-~->** Custom 41 + 3.LRR-UUID **~-~->** Enter 0061C0-Gateway EUI ,Such as:0016C0-A840411E96744150 42 + 4.RF Region **~-~->** Choose the frequency 50 50 ))) 51 51 52 52 [[image:image-20220524163206-2.png]] 53 53 47 +Add Gateway_2 54 54 49 +Have need to put in latitude and longitude, and then click **"CREATE"**. 55 55 56 -**//Have need to put in latitude and longitude, and then click "CREATE".//** 57 - 58 58 [[image:image-20220524163234-3.png]] 59 59 53 +Add Gateway_3 60 60 55 +== 2.3 Step 2. Access the gateway GUI == 61 61 62 - ==**2.3Step2.Accessthegateway GUI** ==57 +User need to update the API key and install the Certificate 63 63 64 - 65 -//Users need to update the API key and install the Certificate// 66 - 67 - 68 68 [[image:image-20220524163255-4.png]] 69 69 61 +Access the gateway GUI 70 70 71 -== **2.4 Step 3. Configure Station**==63 +== 2.4 Step 3. Configure Station == 72 72 65 +User need to input Server URI, as well as install CUPS certificate. 73 73 74 - //Users need to input Server URI, aswell as installtheCUPScertificate.//67 +**just to clarify.** 75 75 76 - 77 -**Just to clarify.** 78 - 79 79 (% class="box" %) 80 80 ((( 81 -//CUPS Server URI **~-~->** Server Adress// 82 - 83 -// Such as:[[https:~~/~~/community.thingpark.io:443>>url:https://community.thingpark.io/||style="background-color: rgb(250, 250, 250);"]]// 84 - 85 -//CUPS certificate **~-~->** server certificate **(user can use the button to install the certificate by default)**// 71 +CUPS Server URI **~-~->** Server Adress Such as:[[https:~~/~~/community.thingpark.io:443>>url:https://community.thingpark.io/||style="background-color: rgb(250, 250, 250);"]] 72 +CUPS certificate **~-~->** Server CA(user can use the button to install the certificate by default) 86 86 ))) 87 87 88 88 [[image:image-20220524163334-5.png]] ... ... @@ -89,51 +89,44 @@ 89 89 90 90 Configure the gateway 91 91 79 +== 2.5 Start Station == 92 92 93 - ==**2.5StartStation**==81 +When the user has finished the configuration,Please click Sace&Apply to start station to connect Actility Thingpark Enterprise. 94 94 95 - //Whentheuser hasfinished the configuration, Pleaseclick Sace&Apply tostart stationto connectActility ThingparkEnterprise.//83 +== 2.6 Siccessful Connection == 96 96 97 - ==**2.6 SuccessfulConnection**==85 +If user completes the above steps,which will see live date in the Actility Thingpark Enterprise. 98 98 99 - 100 -//If users complete the above steps, which will see the live date in the Actility Thingpark Enterprise.// 101 - 102 - 103 103 [[image:image-20220524163358-6.png]] 104 104 89 +Station live date 105 105 106 - 107 -//Station live date// 108 - 109 109 [[image:image-20220524163420-7.png]] 110 110 93 +Station live date 111 111 112 -== **2.7 Trouble Shooting**==95 +== 2.7 Trouble Shooting == 113 113 97 +User can check the station log in the logread/system log page. 114 114 115 -// Users canheckthe stationthe logread/systemlogpage.//99 +[[image:https://wiki.dragino.com/images/thumb/7/7c/Station_log_xiao.png/600px-Station_log_xiao.png||height="457" width="600"]] 116 116 101 +Station Log 117 117 118 - //StationLog~://103 +and recode the station log in the system/Recode log page. 119 119 120 -[[image:image -20220524163455-8.png]]105 +[[image:https://wiki.dragino.com/images/thumb/5/50/Recore_log_xiao.png/600px-Recore_log_xiao.png||height="147" width="600"]] 121 121 107 +Recore Log 122 122 123 -//and recode the station log on the system/Recode log page.// 124 - 125 -[[image:image-20220524163528-10.png]] 126 - 127 -//Recore Log// 128 - 129 129 ((( 130 - //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.//110 +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. 131 131 ))) 132 132 133 133 ((( 134 - //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.//114 +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. 135 135 ))) 136 136 137 137 ((( 138 - //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.//118 +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. 139 139 )))
- image-20220524163455-8.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -130.1 KB - Content
- image-20220524163519-9.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -25.0 KB - Content
- image-20220524163528-10.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -25.0 KB - Content
- image-20220525094736-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -51.1 KB - Content