Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -53,7 +53,7 @@
53	53	)))
54	54
55	55
56		-If the user cannot add network-Servers, re-check the ChirpStack code or the server building process.
	56	+(% style="color:red" %)**If the user cannot add network-Servers, re-check the ChirpStack code or the server building process.**
57	57
58	58
59	59	[[image:image-20220531171609-1.png]]
...	...	@@ -62,15 +62,18 @@
62	62
63	63
64	64
65		-== 2.2 Step 2. Create Gateway-profiles ==
	65	+== 2.2  Step 2. Create Gateway-profiles ==
66	66
	67	+
67	67	[[image:image-20220531171651-2.png]]
68	68
69	69	Create Gateway-profiles
70	70
71	71
72		-== 2.3 Step 3. Create Service-profiles ==
73	73
	74	+== 2.3  Step 3. Create Service-profiles ==
	75	+
	76	+
74	74	[[image:image-20220531171809-3.png]]
75	75
76	76	Create Service-profiles
...	...	@@ -83,29 +83,37 @@
83	83	If the user has completed the preceding steps, proceed to the next step.(% style="display:none" %)
84	84
85	85
86		-== 2.4 Step 4. Add the gateway ==
87	87
	90	+== 2.4  Step 4. Add the gateway ==
	91	+
	92	+
88	88	The example gateway id is: a840411e96744150
89	89
90	90	(((
91	91	(% style="color:red" %)**Note : The Gateway EUI and server addresses must match the ChirpStack configuration.**
	97	+
	98	+
92	92	)))
93	93
94	94	[[image:image-20220531171923-4.png]](% style="display:none" %)
95	95
96		-
97	97	Add the gateway
98	98
	105	+
	106	+
99	99	[[image:image-20220531172031-5.png]]
100	100
101	101	Configure the gateway
102	102
103	103
104		-== 2.5 Step 5. Checking gateway Status ==
105	105
	113	+== 2.5  Step 5. Checking gateway Status ==
	114	+
	115	+
106	106	[[image:image-20220531172158-6.png]](% style="display:none" %)
107	107
108	108
	119	+
109	109	gateway Status
110	110
111	111	[[image:image-20220531172304-7.png]]
...	...	@@ -113,39 +113,48 @@
113	113	gateway Status
114	114
115	115
116		-= 3. Gateway Registration for Basics Station =
117	117
118		-== 3.1 Introduction ==
	128	+= 3.  Gateway Registration for Basics Station =
119	119
	130	+
	131	+== 3.1  Introduction ==
	132	+
	133	+
120	120	The [[Semtech Basic Station>>url:https://doc.sm.tc/station/]] backend implements the [[LNS protocol>>url:https://doc.sm.tc/station/tcproto.html]]. It exposes a WebSocket handler to which Basic Station powered gateways can connect.
121	121
122	122	ChirpStack Open-Source LoRaWAN® Network Server needs to set up a configuration that can use Semtech BasicStation.
123	123
124		-**Below list the support products and Requirements:**
125	125
	139	+(% style="color:blue" %)**Below list the support products and Requirements:**
	140	+
126	126	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]]
127	127	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/]]
128	128
129		-**How to set up chirpStack Basic Station**
	144	+(% style="color:blue" %)**How to set up chirpStack Basic Station**
130	130
131	131	Users can check out the ChirpStack Basic Station [[link>>https://www.chirpstack.io/gateway-bridge/backends/basic-station/]] and [[forum>>https://forum.chirpstack.io/search?q=basic%20station]]
132	132
133		-**What do you need to prepare**
134	134
	149	+(% style="color:blue" %)**What do you need to prepare**
	150	+
135	135	A gateway that can access the internet normally
136	136
137	137
138		-== 3.2 Add Gateway ==
139	139
	155	+== 3.2  Add Gateway ==
	156	+
	157	+
140	140	[[image:image-20220524164205-10.png]]
141	141
142	142
143		-== 3.3 Access the gateway GUI ==
	161	+== 3.3  Access the gateway GUI ==
144	144
	163	+
145	145	Access the gateway GUI interface of LoRaWAN~-~->LoRaWAN ~-~- Basic Station
146	146
147	147	[[image:image-20220524164319-11.png]]
148	148
	168	+
149	149	User need to Choose the ChirpStack/Senet ~-~- Basic Station , input Server URI and Upload the TLS Certificate
150	150
151	151	(% class="box" %)
...	...	@@ -161,20 +161,24 @@
161	161	[[image:image-20220524164341-12.png]]
162	162
163	163
164		-== 3.4 Start Station ==
	184	+== 3.4  Start Station ==
165	165
	186	+
166	166	When the user has finished the configuration, Please click Sace&Apply to start station to connect ChirpStack
167	167
168	168
169		-== 3.5 Successful Connection ==
	190	+== 3.5  Successful Connection ==
170	170
	192	+
171	171	If user completes the above steps, which will see live date in the ChirpStack.
172	172
173	173	[[image:image-20220524164448-13.png]]
174	174
175	175
176		-== 3.6 Trouble Shooting ==
177	177
	199	+== 3.6  Trouble Shooting ==
	200	+
	201	+
178	178	User can check the station log in the logread/system log page.
179	179
180	180	[[image:image-20220531172837-8.png]]
...	...	@@ -185,10 +185,12 @@
185	185	[[image:image-20220531172857-9.png]]
186	186
187	187
	212	+
188	188	= 4. Downlink =
189	189
190	190	== 4.1 Chirpstack Downlink Note ==
191	191
	217	+
192	192	[[image:image-20220601102543-2.png]]
193	193
194	194	Convert the data to Base64
...	...	@@ -204,12 +204,14 @@
204	204	Make sure the RX2DR is the same in the end node
205	205
206	206
207		-== 4.2 Loraserver Downlink Note ==
208	208
	234	+== 4.2  Loraserver Downlink Note ==
	235	+
	236	+
209	209	User can use MQTT to send downlink payload to ChirpStack to perform downstream to LoRaWAN End
210	210
211	211	(((
212		-Below is examples:
	240	+**Below is examples:**
213	213	)))
214	214
215	215	(% class="box" %)
...	...	@@ -225,11 +225,12 @@
225	225	(((
226	226	MQTT Connect to ChirpStack
227	227
	256	+
228	228
229	229	)))
230	230
231	231	(((
232		-After connect
	261	+**After connect**
233	233	)))
234	234
235	235	(% class="box" %)
...	...	@@ -253,7 +253,7 @@
253	253
254	254
255	255	(((
256		-(% style="color:red" %)Note: Chirpstack use base64 to downlink, so need to convert the downlink payload from HEX to base64 [[https:~~/~~/base64.us/>>url:https://base64.us/]]
	285	+(% style="color:red" %)**Note: Chirpstack use base64 to downlink, so need to convert the downlink payload from HEX to base64 [[https:~~/~~/base64.us/>>url:https://base64.us/]]**
257	257	)))
258	258
259	259	[[image:image-20220531173601-13.png]]
...	...	@@ -261,10 +261,12 @@
261	261	Choose to Use Hex for Encode
262	262
263	263
	293	+
264	264	If we want send downstream hex 030101 to end node, the BASE64 payload is AwEB
265	265
266	266	[[image:image-20220531173658-14.png]]
267	267
	298	+
268	268	(((
269	269	Downlink payload encode javescript code: 可以在网站上运行以下Javsscript代码：
270	270	)))
...	...	@@ -327,8 +327,10 @@
327	327	)))
328	328
329	329
330		-== 4.3 Add the decode function in Chirpstack for the payload ==
331	331
	362	+== 4.3  Add the decode function in Chirpstack for the payload ==
	363	+
	364	+
332	332	User enters the payload code according to the steps.
333	333
334	334	[[image:image-20220531173754-15.png]]
...	...	@@ -342,8 +342,10 @@
342	342	[[image:image-20220531174046-19.png]]
343	343
344	344
345		-= 5. Multiply Uplink in ChirpStack =
346	346
	379	+= 5.  Multiply Uplink in ChirpStack =
	380	+
	381	+
347	347	(((
348	348	nbtrans field is the value to determine the re-transmission time for unconfirmed uplink data.
349	349	)))
...	...	@@ -350,12 +350,17 @@
350	350
351	351	(((
352	352	ChirpStack will auto adjust nbtrans according to uplink rssi. [[link to source>>url:https://github.com/brocaar/chirpstack-network-server/blob/master/internal/adr/adr.go]]
	388	+
	389	+
353	353	)))
354	354
355	355	[[image:image-20220526091912-7.png]]
356	356
	394	+
357	357	(((
358	358	nbtrans is a field of ADR message, in unconfirm mode, it tells end node how many time it needs to transmit for every frame.
	397	+
	398	+
359	359	)))
360	360
361	361	[[image:image-20220525104359-21.png]]
...	...	@@ -362,6 +362,8 @@
362	362
363	363	(((
364	364	Above behaviour will cause the platform shows below two cases of error:
	405	+
	406	+
365	365	)))
366	366
367	367	(((
...	...	@@ -371,29 +371,36 @@
371	371	[[image:image-20220525104437-22.png]]
372	372
373	373
	416	+
374	374	Duplicate transmission in short time
375	375
376	376	[[image:image-20220601102430-1.png]]
377	377
378	378
379		-== 5.1 Solution ==
380	380
	423	+== 5.1  Solution ==
	424	+
	425	+
381	381	This example uses the Windows version as a template, other versions can refer to this. Similiar reference: [[https:~~/~~/confluence.alitecs.de/plugins/servlet/mobile?contentId=79790102#content/view/79790102>>url:https://confluence.alitecs.de/plugins/servlet/mobile?contentId=79790102#content/view/79790102]]
382	382
	428	+
383	383	(((
384		-~1. Install the GO compilation environment: Download the corresponding version of the Go compiler at [[https:~~/~~/go.dev/dl/>>url:https://go.dev/dl/]] and install it.
	430	+(% style="color:blue" %)**1. Install the GO compilation environment: Download the corresponding version of the Go compiler at [[https:~~/~~/go.dev/dl/>>url:https://go.dev/dl/]] and install it.**
	431	+
	432	+
385	385	)))
386	386
387	387	[[image:image-20220525104532-24.png]]
388	388
389	389
390		-installation path:
	438	+**installation path:**
391	391
392	392	[[image:image-20220525104554-25.png]]
393	393
394	394
	443	+
395	395	(((
396		-2. Environment variable settings:.
	445	+(% style="color:blue" %)**2. Environment variable settings:**
397	397	)))
398	398
399	399	(((
...	...	@@ -401,13 +401,13 @@
401	401	)))
402	402
403	403	(((
404		-2)Set the variable name GOROOT and the variable value C:\Go\ (installation directory)
	453	+2) Set the variable name GOROOT and the variable value C:\Go\ (installation directory)
405	405	)))
406	406
407	407	[[image:image-20220524165433-33.png]]
408	408
409	409
410		-3)Modify the system variable Path and add C:\Go\bin\:
	459	+3) Modify the system variable Path and add C:\Go\bin\:
411	411
412	412	[[image:image-20220524165452-34.png]]
413	413
...	...	@@ -417,8 +417,9 @@
417	417	[[image:image-20220524165517-35.png]]
418	418
419	419
420		-3. Modify the ADR configuration file according to your own needs, adr.setting.go is an example of the ADR configuration file.
421	421
	470	+(% style="color:blue" %)**3. Modify the ADR configuration file according to your own needs, adr.setting.go is an example of the ADR configuration file.**
	471	+
422	422	The name of the plugin: Example ADR plugin:
423	423
424	424	[[image:image-20220524165540-36.png]]
...	...	@@ -428,8 +428,9 @@
428	428	[[image:image-20220524165557-37.png]]
429	429
430	430
431		-4. Compile the ADR configuration file and generate the exe file.
432	432
	482	+(% style="color:blue" %)**4. Compile the ADR configuration file and generate the exe file.**
	483	+
433	433	1) Create a folder named adr-setting
434	434
435	435	2) Open the adr-setting folder
...	...	@@ -453,8 +453,9 @@
453	453	[[image:image-20220524165623-38.png]]
454	454
455	455
456		-5. Add the plugin and run the plugin.
457	457
	508	+(% style="color:blue" %)**5. Add the plugin and run the plugin.**
	509	+
458	458	(((
459	459	The exe file generated in the previous step is placed in the same root directory as chirpstack-network-server.toml, and the ADR plugin is added to the toml file. The location of the addition is as follows:
460	460	)))
...	...	@@ -490,10 +490,12 @@
490	490	Finish.
491	491
492	492
493		-= 6. Trouble Shooting =
494	494
495		-== 6.1 MIC Mismatch or MIC Failed ==
	546	+= 6.  Trouble Shooting =
496	496
	548	+== 6.1  MIC Mismatch or MIC Failed ==
	549	+
	550	+
497	497	(((
498	498	When the device is registered or the device is working normally, the problem of MIC mismatch and MIC failed occurs.
499	499	)))