Wiki source code of Notes for Actility

Version 40.3 by Xiaoling on 2022/07/23 09:25

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

Wiki source code of Notes for Actility

Applications

Navigation