Wiki source code of Notes for Actility

Version 40.2 by Xiaoling on 2022/07/23 09:24

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

Wiki source code of Notes for Actility

Applications

Navigation