Changes for page Notes for Actility
Last modified by Bei Jinggeng on 2023/05/10 10:18
Change comment:
Uploaded new attachment "image-20220531085014-10.png", version {1}
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 7 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Kilight1 +XWiki.Xiaoling - Content
-
... ... @@ -1,4 +1,4 @@ 1 - ** Table of** **Contents:**1 + **Contents:** 2 2 3 3 {{toc/}} 4 4 ... ... @@ -23,65 +23,59 @@ 23 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 - (% style="color:blue" %)**Below list the support products and Requirements:**26 +**Below list the support products and Requirements:** 27 27 28 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 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 31 32 -(% style="color:blue" %)**What do you need to prepare** 33 - 34 34 //A gateway that can access the internet normally// 35 35 36 36 37 37 == **2.2 Step 1. Add Gateway** == 38 38 38 +[[image:image-20220531084235-1.png]] 39 39 40 -[[image:image-20220531084235-1.png||height="767" width="1332"]] 41 41 41 +**The following items need to be configured:** 42 42 43 -(% style="color:blue" %)**The following items need to be configured:** 44 - 45 45 (% class="box" %) 46 46 ((( 47 47 // 1.Model **~-~->** Choose the Model 48 48 2.Name **~-~->** Custom 49 - 3.LRR-UUID **~-~->** **00 16C0(aways is it)**-Gateway EUI //47 + 3.LRR-UUID **~-~->** **0061C0(aways is it)**-Gateway EUI // 50 50 51 51 // Such as: **0016C0-A840411E96744150**// 52 52 // 4.RF Region **~-~->** Choose the frequency// 53 53 ))) 54 54 55 -[[image:image-20220 610095043-1.png]]53 +[[image:image-20220531084316-2.png]] 56 56 57 57 58 - (% style="color:blue" %)**//Have need to put in latitude and longitude, and then click "CREATE".//**56 +**//Have need to put in latitude and longitude, and then click "CREATE".//** 59 59 60 -[[image:image-2022053108 5325-12.png]]58 +[[image:image-20220531084401-3.png]] 61 61 62 62 63 - 64 64 == **2.3 Step 2. Access the gateway GUI** == 65 65 66 - 67 67 //Users need to update the API key and install the Certificate// 68 68 69 69 70 -[[image:image-20220531084451-4.png ||height="683" width="1357"]]66 +[[image:image-20220531084451-4.png]] 71 71 72 72 73 - 74 74 == **2.4 Step 3. Configure Station** == 75 75 76 - 77 77 //Users need to input Server URI, as well as install the CUPS certificate.// 78 78 79 79 80 - (% style="color:blue" %)**Just to clarify.**74 +**Just to clarify.** 81 81 82 82 (% class="box" %) 83 83 ((( 84 -//CUPS Server URI **~-~->** Server Ad dress//78 +//CUPS Server URI **~-~->** Server Adress// 85 85 86 86 // Such as:[[https:~~/~~/community.thingpark.io:443>>url:https://community.thingpark.io/||style="background-color: rgb(250, 250, 250);"]]// 87 87 ... ... @@ -88,7 +88,7 @@ 88 88 //CUPS certificate **~-~->** server certificate **(user can use the button to install the certificate by default)**// 89 89 ))) 90 90 91 -[[image:image-20220531084527-5.png ||height="685" width="1370"]]85 +[[image:image-20220531084527-5.png]] 92 92 93 93 Configure the gateway 94 94 ... ... @@ -95,40 +95,32 @@ 95 95 96 96 == **2.5 Start Station** == 97 97 98 - 99 99 //When the user has finished the configuration, Please click Sace&Apply to start station to connect Actility Thingpark Enterprise.// 100 100 101 101 102 102 == **2.6 Successful Connection** == 103 103 104 - 105 105 //If users complete the above steps, which will see the live date in the Actility Thingpark Enterprise.// 106 106 107 107 108 -[[image:image-20220531084632-6.png ||height="700" width="1403"]]100 +[[image:image-20220531084632-6.png]] 109 109 110 110 111 - 112 112 //Station live date// 113 113 114 -[[image:image-20220531084747-7.png ||height="591" width="1410"]]105 +[[image:image-20220531084747-7.png]] 115 115 116 116 117 - 118 118 == **2.7 Trouble Shooting** == 119 119 120 - 121 -=== **2.7.1 How do users view Basic Station logs and Record logs** === 122 - 123 123 //Users can check the station log on the logread/system log page.// 124 124 125 125 126 126 //Station Log~:// 127 127 128 -[[image:image-2022053108 5014-10.png]]115 +[[image:image-20220531084858-8.png]] 129 129 130 130 131 - 132 132 //and recode the station log on the system/Recode log page.// 133 133 134 134 [[image:image-20220531084931-9.png]] ... ... @@ -136,26 +136,12 @@ 136 136 //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** === 140 - 141 - 142 -In this case, the user needs to check whether the Gateway ID matches the UUID on Actility Thingpark. 143 - 144 -In addition, the user needs to regenerate new certificates in ThingPark GUI **(Advanced tab of the Base Station panel)**. 145 - 146 -[[image:image-20220822085416-2.png]] 147 - 148 -[[image:image-20220822091137-3.png]] 149 - 150 -[[image:image-20220822091229-4.png||height="569" width="1267"]] 151 - 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.//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.// 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.//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.// 159 159 ))) 160 160 161 161 (((
- image-20220531085244-11.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -55.7 KB - Content
- image-20220531085325-12.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -29.2 KB - Content
- image-20220610095043-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Kilight - Size
-
... ... @@ -1,1 +1,0 @@ 1 -58.6 KB - Content
- image-20220822085346-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Kilight - Size
-
... ... @@ -1,1 +1,0 @@ 1 -48.0 KB - Content
- image-20220822085416-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Kilight - Size
-
... ... @@ -1,1 +1,0 @@ 1 -23.0 KB - Content
- image-20220822091137-3.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Kilight - Size
-
... ... @@ -1,1 +1,0 @@ 1 -51.7 KB - Content
- image-20220822091229-4.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Kilight - Size
-
... ... @@ -1,1 +1,0 @@ 1 -50.9 KB - Content