Changes for page Notes for Actility
Last modified by Bei Jinggeng on 2023/05/10 10:18
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 14 removed)
- image-20220524163104-1.png
- image-20220524163206-2.png
- image-20220524163234-3.png
- image-20220524163255-4.png
- image-20220524163334-5.png
- image-20220524163358-6.png
- image-20220524163420-7.png
- image-20220524163455-8.png
- image-20220524163519-9.png
- image-20220524163528-10.png
- image-20220525094736-1.png
- image-20220525094818-2.png
- image-20220525094855-3.png
- image-20220525094925-4.png
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 - Notes forActility1 +Actility ThingPark Enterprise - Content
-
... ... @@ -2,135 +2,110 @@ 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/]] 24 + 28 28 **What do you need to prepare** 29 29 30 - //A gateway that can access the internet normally//27 +A gateway that can access the internet normally 31 31 29 +== 2.2 Step 1. Add Gateway == 32 32 33 - == **2.2 Step1.Gateway**==31 +[[image:https://wiki.dragino.com/images/thumb/e/e5/Add_gateway_1.png/600px-Add_gateway_1.png||height="300" width="600"]] 34 34 35 - [[image:image-20220525094736-1.png]]33 +Add Gateway_1 36 36 37 - 38 38 **The following items need to be configured:** 39 39 40 - (%class="box"%)41 - (((42 - //1.Model **~-~->**ChoosetheModel43 - 2.Name**~-~->**Custom44 - 3.LRR-UUID **~-~->** **0061C0(aways is it)**-Gateway EUI //37 +{{{ 1.Model -->Choose the Model 38 + 2.Name -->Custom 39 + 3.LRR-UUID -->Enter 0061C0-Gateway EUI ,Such as:0016C0-A840411E96744150 40 + 4.RF Region -->Choose the frequency 41 +}}} 45 45 46 -// Such as: **0016C0-A840411E96744150**// 47 -// 4.RF Region **~-~->** Choose the frequency// 48 -))) 43 +[[image:https://wiki.dragino.com/images/thumb/4/4b/Add_gateway_2.png/600px-Add_gateway_2.png||height="432" width="600"]] 49 49 50 - [[image:image-20220525094818-2.png]]45 +Add Gateway_2 51 51 47 +Have need to put in latitude and longitude, and then click **"CREATE"**. 52 52 53 - **//Haveneedto putn latitudeand longitude,andhenclick"CREATE".//**49 +[[image:https://wiki.dragino.com/images/thumb/1/16/Add_gateway_3.png/600px-Add_gateway_3.png||height="491" width="600"]] 54 54 55 - [[image:image-20220525094855-3.png]]51 +Add Gateway_3 56 56 53 +== 2.3 Step 2. Access the gateway GUI == 57 57 55 +User need to update the API key and install the Certificate 58 58 59 - == **2.3 Step2.**==57 +[[image:https://wiki.dragino.com/images/thumb/3/32/Access_gateway_GUI_thingpark.png/600px-Access_gateway_GUI_thingpark.png||height="289" width="600"]] 60 60 59 +Access the gateway GUI 61 61 62 - //Usersneedto updatetheAPI key andinstall theCertificate//61 +== 2.4 Step 3. Configure Station == 63 63 63 +User need to input Server URI, as well as install CUPS certificate. 64 64 65 - [[image:image-20220524163255-4.png]]65 +**just to clarify.** 66 66 67 +{{{ CUPS Server URI --> Server Adress Such as: 68 + CUPS certificate --> Server CA(user can use the button to install the certificate by default) 69 +}}} 67 67 68 - == **2.4Step3.Station**==71 +[[image:https://wiki.dragino.com/images/thumb/6/64/Configure_the_gateway_thingpark.png/600px-Configure_the_gateway_thingpark.png||height="326" width="600"]] 69 69 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-20220524163334-5.png]] 86 - 87 87 Configure the gateway 88 88 75 +== 2.5 Start Station == 89 89 90 - ==**2.5StartStation**==77 +When the user has finished the configuration,Please click Sace&Apply to start station to connect Actility Thingpark Enterprise. 91 91 92 - //Whentheuser hasfinished the configuration, Pleaseclick Sace&Apply tostart stationto connectActility ThingparkEnterprise.//79 +== 2.6 Siccessful Connection == 93 93 94 - ==**2.6 SuccessfulConnection**==81 +If user completes the above steps,which will see live date in the Actility Thingpark Enterprise. 95 95 83 +[[image:https://wiki.dragino.com/images/thumb/b/b4/View_gateway_thingpark.png/600px-View_gateway_thingpark.png||height="297" width="600"]] 96 96 97 - //If users complete theabove steps, whichwill see the live datein the Actility Thingpark Enterprise.//85 +Station live date 98 98 87 +[[image:https://wiki.dragino.com/images/thumb/4/40/Gateway_status_thingpark.png/600px-Gateway_status_thingpark.png||height="285" width="600"]] 99 99 100 - [[image:image-20220524163358-6.png]]89 +Station live date 101 101 91 +== 2.7 Trouble Shooting == 102 102 93 +User can check the station log in the logread/system log page. 103 103 104 -//Station ve date//95 +[[image:https://wiki.dragino.com/images/thumb/7/7c/Station_log_xiao.png/600px-Station_log_xiao.png||height="457" width="600"]] 105 105 106 - [[image:image-20220524163420-7.png]]97 +Station Log 107 107 99 +and recode the station log in the system/Recode log page. 108 108 109 - == **2.7 TroubleShooting**==101 +[[image:https://wiki.dragino.com/images/thumb/5/50/Recore_log_xiao.png/600px-Recore_log_xiao.png||height="147" width="600"]] 110 110 103 +Recore Log 111 111 112 -//Users can check the station log on the logread/system log page.// 113 113 114 114 115 - //Station Log~://107 +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. 116 116 117 - [[image:image-20220524163455-8.png]]109 +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. 118 118 119 - 120 -//and recode the station log on the system/Recode log page.// 121 - 122 -[[image:image-20220524163528-10.png]] 123 - 124 -//Recore Log// 125 - 126 -((( 127 -//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.// 128 -))) 129 - 130 -((( 131 -//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.// 132 -))) 133 - 134 -((( 135 -//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.// 136 -))) 111 +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.
- image-20220524163104-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -33.2 KB - Content
- image-20220524163206-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -45.6 KB - Content
- image-20220524163234-3.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -36.1 KB - Content
- image-20220524163255-4.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -48.4 KB - Content
- image-20220524163334-5.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -55.3 KB - Content
- image-20220524163358-6.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -33.2 KB - Content
- image-20220524163420-7.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -34.7 KB - Content
- 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
- image-20220525094818-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -68.8 KB - Content
- image-20220525094855-3.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -48.1 KB - Content
- image-20220525094925-4.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -73.3 KB - Content