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, 8 removed)
Details
- Page properties
-
- Content
-
... ... @@ -2,137 +2,118 @@ 2 2 3 3 {{toc/}} 4 4 5 += 1. Actility Thingpark Enterprise = 5 5 7 +== 1.1 Introduction == 6 6 9 +=== 1.1.1 What is Actility Thingpark Enterprise === 7 7 8 - =**1. Actility Thingpark Enterprise**=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. 9 9 10 -= =**1.1Introduction**==13 += 2. Gateway Registration for Basics Station = 11 11 12 -== =**1.1.1Whatis Actility ThingparkEnterprise**===15 +== 2.1 Introduction == 13 13 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/]] 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.// 16 - 17 - 18 -= **2. Gateway Registration for Basics Station** = 19 - 20 -== **2.1 Introduction** == 21 - 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/]]// 24 - 25 - 26 26 **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/]]// 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]] 30 30 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 + 31 31 **What do you need to prepare** 32 32 33 - //A gateway that can access the internet normally//27 +A gateway that can access the internet normally 34 34 29 +== 2.2 Step 1. Add Gateway == 35 35 36 - == **2.2Step1.Add Gateway** ==31 +[[image:image-20220524163104-1.png]] 37 37 38 - [[image:image-20220525094736-1.png]]33 +Add Gateway_1 39 39 40 - 41 41 **The following items need to be configured:** 42 42 43 43 (% class="box" %) 44 44 ((( 45 -// 1.Model **~-~->** Choose the Model 46 - 2.Name **~-~->** Custom 47 - 3.LRR-UUID **~-~->** **0061C0(aways is it)**-Gateway EUI // 48 - 49 -// Such as: **0016C0-A840411E96744150**// 50 -// 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 51 51 ))) 52 52 53 -[[image:image-2022052 5094818-2.png]]45 +[[image:image-20220524163206-2.png]] 54 54 47 +Add Gateway_2 55 55 56 - **//Have need to put in latitude and longitude, and then click "CREATE".//**49 +Have need to put in latitude and longitude, and then click **"CREATE"**. 57 57 58 -[[image:image-2022052 5094855-3.png]]51 +[[image:image-20220524163234-3.png]] 59 59 53 +Add Gateway_3 60 60 61 -== **2.3 Step 2. Access the gateway GUI**==55 +== 2.3 Step 2. Access the gateway GUI == 62 62 57 +User need to update the API key and install the Certificate 63 63 64 - //Users need to update the API key andinstall theCertificate//59 +[[image:image-20220524163255-4.png]] 65 65 61 +Access the gateway GUI 66 66 67 - [[image:image-20220525094925-4.png]]63 +== 2.4 Step 3. Configure Station == 68 68 65 +User need to input Server URI, as well as install CUPS certificate. 69 69 70 - ==**2.4 Step3. ConfigureStation**==67 +**just to clarify.** 71 71 72 - 73 -//Users need to input Server URI, as well as install the CUPS certificate.// 74 - 75 - 76 -**Just to clarify.** 77 - 78 78 (% class="box" %) 79 79 ((( 80 -//CUPS Server URI **~-~->** Server Adress// 81 - 82 -// Such as:[[https:~~/~~/community.thingpark.io:443>>url:https://community.thingpark.io/||style="background-color: rgb(250, 250, 250);"]]// 83 - 84 -//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) 85 85 ))) 86 86 87 -[[image:image-2022052 5095011-5.png]]75 +[[image:image-20220524163334-5.png]] 88 88 89 89 Configure the gateway 90 90 79 +== 2.5 Start Station == 91 91 92 - ==**2.5StartStation**==81 +When the user has finished the configuration,Please click Sace&Apply to start station to connect Actility Thingpark Enterprise. 93 93 94 - //Whentheuser hasfinished the configuration, Pleaseclick Sace&Apply tostart stationto connectActility ThingparkEnterprise.//83 +== 2.6 Siccessful Connection == 95 95 96 - ==**2.6 SuccessfulConnection**==85 +If user completes the above steps,which will see live date in the Actility Thingpark Enterprise. 97 97 87 +[[image:image-20220524163358-6.png]] 98 98 99 - //If users complete theabove steps, whichwill see the live datein the Actility Thingpark Enterprise.//89 +Station live date 100 100 91 +[[image:image-20220524163420-7.png]] 101 101 102 - [[image:image-20220525095038-6.png]]93 +Station live date 103 103 95 +== 2.7 Trouble Shooting == 104 104 97 +User can check the station log in the logread/system log page. 105 105 106 - //Station livedate//99 +[[image:image-20220524163455-8.png]] 107 107 108 - [[image:image-20220525095119-7.png]]101 +Station Log 109 109 103 +and recode the station log in the system/Recode log page. 110 110 111 -== **2.7 Trouble Shooting** == 112 - 113 - 114 -//Users can check the station log on the logread/system log page.// 115 - 116 - 117 -//Station Log~:// 118 - 119 -[[image:image-20220525095149-8.png]] 120 - 121 - 122 -//and recode the station log on the system/Recode log page.// 123 - 124 124 [[image:image-20220524163528-10.png]] 125 125 126 - //Recore Log//107 +Recore Log 127 127 128 128 ((( 129 - //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. 130 130 ))) 131 131 132 132 ((( 133 - //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. 134 134 ))) 135 135 136 136 ((( 137 - //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. 138 138 )))
- 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
- image-20220525095011-5.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -83.0 KB - Content
- image-20220525095038-6.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -49.0 KB - Content
- image-20220525095119-7.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -53.3 KB - Content
- image-20220525095149-8.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -191.2 KB - Content