Wiki source code of Notes for Actility

Version 45.1 by Kilight Cao on 2022/08/22 09:15

version	line-number	content
40.2	1	Table of Contents：
1.2	2
1.1	3	{{toc/}}
	4
23.4	5
	6
	7
15.1	8	= 1. Actility Thingpark Enterprise =
1.1	9
15.1	10	== 1.1 Introduction ==
1.1	11
15.1	12	=== 1.1.1 What is Actility Thingpark Enterprise ===
1.1	13
	14
15.1	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.//
1.1	16
	17
15.1	18	= 2. Gateway Registration for Basics Station =
1.1	19
15.1	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
40.2	26	(% style="color:blue" %)Below list the support products and Requirements:
1.1	27
15.1	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/]]//
1.1	30
40.3	31
40.2	32	(% style="color:blue" %)What do you need to prepare
1.1	33
15.1	34	//A gateway that can access the internet normally//
1.1	35
	36
15.1	37	== 2.2 Step 1. Add Gateway ==
	38
40.2	39
35.2	40	[[image:image-20220531084235-1.png\|\|height="767" width="1332"]]
1.1	41
1.2	42
40.2	43	(% style="color:blue" %)The following items need to be configured:
1.2	44
1.4	45	(% class="box" %)
	46	(((
15.1	47	// 1.Model ~-~-> Choose the Model
	48	2.Name ~-~-> Custom
40.1	49	3.LRR-UUID ~-~-> 0016C0(aways is it)-Gateway EUI //
15.1	50
	51	// Such as: 0016C0-A840411E96744150//
	52	// 4.RF Region ~-~-> Choose the frequency//
1.4	53	)))
1.2	54
38.1	55	[[image:image-20220610095043-1.png]]
1.2	56
	57
40.2	58	(% style="color:blue" %)//Have need to put in latitude and longitude, and then click "CREATE".//
15.1	59
36.2	60	[[image:image-20220531085325-12.png]]
1.2	61
	62
40.2	63
15.1	64	== 2.3 Step 2. Access the gateway GUI ==
1.2	65
40.2	66
15.1	67	//Users need to update the API key and install the Certificate//
	68
	69
36.3	70	[[image:image-20220531084451-4.png\|\|height="683" width="1357"]]
1.2	71
	72
40.2	73
15.1	74	== 2.4 Step 3. Configure Station ==
1.2	75
40.2	76
15.1	77	//Users need to input Server URI, as well as install the CUPS certificate.//
1.2	78
15.1	79
40.3	80	(% style="color:blue" %)Just to clarify.
15.1	81
1.4	82	(% class="box" %)
	83	(((
39.1	84	//CUPS Server URI ~-~-> Server Address//
15.1	85
	86	// Such as:[[https:~~/~~/community.thingpark.io:443>>url:https://community.thingpark.io/\|\|style="background-color: rgb(250, 250, 250);"]]//
	87
	88	//CUPS certificate ~-~-> server certificate (user can use the button to install the certificate by default)//
1.4	89	)))
1.2	90
36.3	91	[[image:image-20220531084527-5.png\|\|height="685" width="1370"]]
1.2	92
	93	Configure the gateway
	94
	95
15.1	96	== 2.5 Start Station ==
1.2	97
40.2	98
15.1	99	//When the user has finished the configuration, Please click Sace&Apply to start station to connect Actility Thingpark Enterprise.//
1.2	100
23.8	101
15.1	102	== 2.6 Successful Connection ==
1.2	103
40.2	104
15.1	105	//If users complete the above steps, which will see the live date in the Actility Thingpark Enterprise.//
	106
	107
36.4	108	[[image:image-20220531084632-6.png\|\|height="700" width="1403"]]
1.2	109
	110
40.2	111
15.1	112	//Station live date//
	113
36.4	114	[[image:image-20220531084747-7.png\|\|height="591" width="1410"]]
1.2	115
	116
40.2	117
15.1	118	== 2.7 Trouble Shooting ==
1.2	119
40.2	120
45.1	121	=== 2.7.1 How do users view Basic Station logs and Record logs ===
	122
15.1	123	//Users can check the station log on the logread/system log page.//
	124
	125
	126	//Station Log~://
	127
33.2	128	[[image:image-20220531085014-10.png]]
1.2	129
	130
40.2	131
15.1	132	//and recode the station log on the system/Recode log page.//
1.2	133
32.2	134	[[image:image-20220531084931-9.png]]
1.2	135
15.1	136	//Recore Log//
1.2	137
23.11	138
45.1	139	=== 2.7.2 How to solve the problem when "(400) TC credentials not found" is displayed in the log ===
40.2	140
45.1	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
1.5	153	(((
40.2	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.//
1.5	155	)))
1.2	156
1.5	157	(((
40.2	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.//
1.5	159	)))
1.2	160
1.5	161	(((
15.1	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.//
1.5	163	)))

Wiki source code of Notes for Actility

Applications

Navigation