Summary

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

Details

Page properties

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.Xiaoling
	1	+XWiki.Kilight

Content

...	...	@@ -37,28 +37,24 @@
37	37	)))
38	38	)))
39	39
40		-
41	41	= 2.  Node usage introduction =
42	42
43	43	== 2.1 Register Node ==
44	44
	44	+Step 1: Add application
45	45
46		-**Step 1: Add application**
47		-
48	48	[[image:image-20230702094608-1.png||height="537" width="1015"]]
49	49
	48	+Step 2：Fill name
50	50
51		-**Step 2：Fill name**
52		-
53	53	[[image:image-20230702094852-2.png]]
54	54
	52	+Step4 ：Add device profile
55	55
56		-**Step3 ：Add device profile**
57		-
58	58	[[image:image-20230702095114-4.png||height="448" width="1061"]]
59	59
60	60
61		-**Step4 ：Configure your device profile**
	57	+Step5 ：Configure your device profile
62	62
63	63	[[image:image-20230702095557-5.png||height="648" width="1121"]]
64	64
...	...	@@ -71,21 +71,20 @@
71	71	[[image:image-20230702095827-7.png||height="490" width="1138"]]
72	72
73	73
74		-**Step5 ：add device**
	70	+Step6 ：add device
75	75
76	76	[[image:image-20230702094944-3.png||height="439" width="1153"]]
77	77
78	78
79		-[[image:image-20230702100312-8.png||height="550" width="1106"]]
80	80
	76	+[[image:image-20230702100312-8.png||height="585" width="1176"]]
81	81
82	82	[[image:image-20230702100543-10.png||height="313" width="1099"]]
83	83
84		-
85	85	[[image:image-20230702100930-11.png||height="613" width="1098"]]
86	86
87	87
88		-= 3.  Semtech UDP for ChirpStack v3 =
	83	+= 3.  Semtech UDP =
89	89
90	90	== 3.1  Step 1. Add the Network-servers ==
91	91
...	...	@@ -101,6 +101,7 @@
101	101
102	102	(% style="color:red" %)**If the user cannot add network-Servers, re-check the ChirpStack code or the server building process.**
103	103
	99	+
104	104	[[image:image-20220531171609-1.png||height="638" width="1268"]](% style="display:none" %)
105	105
106	106	Add the Network-servers
...	...	@@ -136,6 +136,8 @@
136	136
137	137	(((
138	138	(% style="color:red" %)**Note : The Gateway EUI and server addresses must match the ChirpStack configuration.**
	135	+
	136	+
139	139	)))
140	140
141	141	[[image:image-20220531171923-4.png||height="745" width="1253"]](% style="display:none" %)
...	...	@@ -143,6 +143,7 @@
143	143	Add the gateway
144	144
145	145
	144	+
146	146	[[image:image-20220531172031-5.png]]
147	147
148	148	Configure the gateway
...	...	@@ -162,26 +162,11 @@
162	162	gateway Status
163	163
164	164
165		-= 4.  Semtech UDP for ChirpStack v4 =
	164	+= 4.  Gateway Registration for Basics Station =
166	166
167		-== 4.1  Step 1. Add the gateway ==
	166	+== 4.1  Introduction ==
168	168
169	169
170		-[[image:image-20230926092907-1.png||height="598" width="1007"]]
171		-
172		-
173		-[[image:image-20230926093057-2.png||height="541" width="1002"]]
174		-
175		-
176		-== 4.2  Step 2. Checking gateway Status ==
177		-
178		-[[image:image-20230926093233-3.png||height="581" width="1018"]]
179		-
180		-= 5.  Gateway Registration for Basics Station =
181		-
182		-== 5.1  Introduction ==
183		-
184		-
185	185	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.
186	186
187	187	ChirpStack Open-Source LoRaWAN® Network Server needs to set up a configuration that can use Semtech BasicStation.
...	...	@@ -202,13 +202,13 @@
202	202	A gateway that can access the internet normally
203	203
204	204
205		-== 5.2  Add Gateway ==
	189	+== 4.2  Add Gateway ==
206	206
207	207
208	208	[[image:image-20220524164205-10.png]]
209	209
210	210
211		-== 5.3  Access the gateway GUI ==
	195	+== 4.3  Access the gateway GUI ==
212	212
213	213
214	214	Access the gateway GUI interface of LoRaWAN~-~->LoRaWAN ~-~- Basic Station
...	...	@@ -231,13 +231,13 @@
231	231	[[image:image-20220524164341-12.png]]
232	232
233	233
234		-== 5.4  Start Station ==
	218	+== 4.4  Start Station ==
235	235
236	236
237	237	When the user has finished the configuration, Please click **Sace&Apply** to start station to connect ChirpStack.
238	238
239	239
240		-== 5.5  Successful Connection ==
	224	+== 4.5  Successful Connection ==
241	241
242	242
243	243	If user completes the above steps, which will see live date in the ChirpStack.
...	...	@@ -245,7 +245,7 @@
245	245	[[image:image-20220524164448-13.png]]
246	246
247	247
248		-== 5.6  Trouble Shooting ==
	232	+== 4.6  Trouble Shooting ==
249	249
250	250
251	251	User can check the station log in the logread/system log page.
...	...	@@ -258,7 +258,7 @@
258	258	[[image:image-20220531172857-9.png]]
259	259
260	260
261		-= 6.  How the gateway connects to Chirpstack v3 via gateway-bridge =
	245	+= 5.  How the gateway connects to Chirpstack v3 via gateway-bridge =
262	262
263	263
264	264	(% style="color:blue" %)**Below list the support products and Requirements:**
...	...	@@ -279,7 +279,7 @@
279	279	The following example does not have configuration certificates:
280	280
281	281
282		-== 6.1  Configure Packet Forwarder ==
	266	+== 5.1  Configure Packet Forwarder ==
283	283
284	284
285	285	In the Dragino gateway web interface, you need to configure the Packet Forwarder so that it forwards its data to the port. localhost:1700 or 127.0.0.1:1700
...	...	@@ -297,7 +297,7 @@
297	297	[[image:image-20221222114220-2.png||height="748" width="931"]]
298	298
299	299
300		-== 6.2  Configuring gateway frequency ==
	284	+== 5.2  Configuring gateway frequency ==
301	301
302	302
303	303	(% style="color:red" %)**Note: Gateway frequencies must match**
...	...	@@ -305,7 +305,7 @@
305	305	[[image:image-20221222134830-3.png||height="408" width="923"]]
306	306
307	307
308		-== 6.3  Generate and modify the gateway-bridge configuration file ==
	292	+== 5.3  Generate and modify the gateway-bridge configuration file ==
309	309
310	310
311	311	**1）Generate the gateway-bridge configuration file**
...	...	@@ -332,7 +332,7 @@
332	332	[[image:image-20230415165254-1.png||height="583" width="956"]]
333	333
334	334
335		-== 6.4  Debug ==
	319	+== 5.4  Debug ==
336	336
337	337
338	338	After the above configuration is completed, the user can enter the command to debug the gateway-bridge connection
...	...	@@ -355,7 +355,7 @@
355	355	More information can be found on the **[[ChirpStack website>>https://www.chirpstack.io/docs/]]**or **[[Forum>>url:https://forum.chirpstack.io/]]**
356	356
357	357
358		-== 6.5  (Re)start and stop gateway-bridge ==
	342	+== 5.5  (Re)start and stop gateway-bridge ==
359	359
360	360
361	361	Use the following commands to (re)start and stop the ChirpStack Gateway Bridge Service:
...	...	@@ -376,7 +376,7 @@
376	376	)))
377	377
378	378
379		-= 7.  How the gateway connects to Chirpstack v4 via gateway-bridge =
	363	+= 6.  How the gateway connects to Chirpstack v4 via gateway-bridge =
380	380
381	381
382	382	(% style="color:blue" %)**Below list the support products and Requirements:**
...	...	@@ -394,7 +394,7 @@
394	394	A gateway that can access the internet normally
395	395
396	396
397		-== 7.1  Configure Packet Forwarder ==
	381	+== 6.1  Configure Packet Forwarder ==
398	398
399	399
400	400	In the Dragino gateway web interface, you need to configure the Packet Forwarder so that it forwards its data to the port. localhost:1700 or 127.0.0.1:1700
...	...	@@ -412,7 +412,7 @@
412	412	[[image:image-20221222114220-2.png||height="748" width="931"]]
413	413
414	414
415		-== 7.2  Configuring gateway frequency ==
	399	+== 6.2  Configuring gateway frequency ==
416	416
417	417
418	418	(% style="color:red" %)**Note: Gateway frequencies must match**
...	...	@@ -420,7 +420,7 @@
420	420	[[image:image-20221222134830-3.png||height="408" width="923"]]
421	421
422	422
423		-== 7.3  Modify the gateway-bridge configuration file ==
	407	+== 6.3  Modify the gateway-bridge configuration file ==
424	424
425	425
426	426	Run the gateway command line command to modify the gateway-bridge configuration file:
...	...	@@ -435,7 +435,6 @@
435	435
436	436	[[image:image-20221222140203-4.png||height="875" width="806"]]
437	437
438		-
439	439	[[image:image-20221230094246-1.png||height="768" width="783"]]
440	440
441	441	(% class="wikigeneratedid" id="H" %)
...	...	@@ -442,7 +442,7 @@
442	442	After the modification, run the following command: **/etc/init.d/chirpstack-gateway-bridge restart**
443	443
444	444
445		-== 7.4  (Re)start and stop gateway-bridge ==
	428	+== 6.4  (Re)start and stop gateway-bridge ==
446	446
447	447
448	448	Use the following commands to (re)start and stop the ChirpStack Gateway Bridge Service:
...	...	@@ -463,7 +463,7 @@
463	463	)))
464	464
465	465
466		-== 7.5  Successful Connection ==
	449	+== 6.5  Successful Connection ==
467	467
468	468
469	469	[[image:image-20221222141754-5.png||height="488" width="1150"]]
...	...	@@ -472,9 +472,9 @@
472	472	[[image:image-20221222141830-6.png||height="582" width="1153"]]
473	473
474	474
475		-= 8.  Downlink =
	458	+= 7.  Downlink =
476	476
477		-== 8.1  Convert HEX to Base64 ==
	460	+== 7.1  Convert HEX to Base64 ==
478	478
479	479
480	480	(% style="color:red" %)**Note: Chirpstack uses base64 to downlink, the end node user manual provides HEX format of the downlink commands. So user needs to convert the HEX to Base64.**
...	...	@@ -490,7 +490,7 @@
490	490	[[image:image-20221010193621-2.png]]
491	491
492	492
493		-== 8.2  Chirpstack Downlink Note ==
	476	+== 7.2  Chirpstack Downlink Note ==
494	494
495	495
496	496	[[image:image-20220601102543-2.png]]
...	...	@@ -511,7 +511,7 @@
511	511	**Make sure the RX2DR is the same in the end node**
512	512
513	513
514		-== 8.3  Loraserver Downlink Note ==
	497	+== 7.3  Loraserver Downlink Note ==
515	515
516	516
517	517	User can use MQTT to send downlink payload to ChirpStack to perform downstream to LoRaWAN End
...	...	@@ -628,7 +628,7 @@
628	628	)))
629	629
630	630
631		-== 8.4  Add the decode function in Chirpstack for the payload ==
	614	+== 7.4  Add the decode function in Chirpstack for the payload ==
632	632
633	633
634	634	User enters the payload code according to the steps.
...	...	@@ -646,7 +646,7 @@
646	646	[[image:image-20220531174046-19.png]]
647	647
648	648
649		-= 9.  Multiply Uplink in ChirpStack =
	632	+= 8.  Multiply Uplink in ChirpStack =
650	650
651	651
652	652	(((
...	...	@@ -686,16 +686,19 @@
686	686
687	687	**Duplicate transmission in short time**
688	688
689		-[[image:image-20220601102430-1.png||height="508" width="1120"]]
	672	+[[image:image-20220601102430-1.png||height="598" width="1319"]]
690	690
691	691
692		-== 9.1  Solution ==
	675	+== 8.1  Solution ==
693	693
694	694
695	695	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]]
696	696
	680	+
697	697	(((
698	698	(% 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.**
	683	+
	684	+
699	699	)))
700	700
701	701	[[image:image-20220525104532-24.png]]
...	...	@@ -808,7 +808,7 @@
808	808	Finish.
809	809
810	810
811		-= 10.  How to store/get all data traffic for a specific sensor, including raw payload, and uplink/ downlink history. =
	797	+= 9.  How to store/get all data traffic for a specific sensor, including raw payload, and uplink/ downlink history. =
812	812
813	813
814	814	All data is published to the MQTT topics. if you want to store/get the data, you would have to create an MQTT handler and store the data yourself.
...	...	@@ -818,7 +818,7 @@
818	818	(% style="color:blue" %)**//1). Chirpstack ~-~-> Node-red//**
819	819
820	820
821		-[[image:image-20221012184501-1.png||height="608" width="1041"]]
	807	+[[image:image-20221012184501-1.png]]
822	822
823	823
824	824	Use MQTT in Nore-red to subscribe to topics published by the chirpstack-application and then continuously write to a file
...	...	@@ -854,12 +854,11 @@
854	854	**mosquitto_sub -h IPADDRESS -p 8883 ~-~-insecure ~-~-cafile ca.pem ~-~-cert cert.pem ~-~-key key.pem -t "application/#" -v**
855	855	)))
856	856
857		-[[image:image-20221012173639-1.png||height="273" width="1206"]]
	843	+[[image:image-20221012173639-1.png]]
858	858
	845	+= 10.  Example: Use Local Server ChirpStack and Node-Red in LPS8v2 =
859	859
860		-= 11.  Example: Use Local Server ChirpStack and Node-Red in LPS8v2 =
861	861
862		-
863	863	LPS8v2 includes a local ChirpStack Server and Node-Red. This example shows how to configure LHT65N to use with the local Node-Red server. This example assumes users already have:
864	864
865	865	* LHT65N register on LPS8v2 Built-In ChirpStack server already
...	...	@@ -868,7 +868,7 @@
868	868	Below are the steps to plot the sensor data on LPS8v2 Node-Red.
869	869
870	870
871		-== 11.1 Link Node-Red to Local ChirpStack ==
	856	+== 10.1 Link Node-Red to Local ChirpStack ==
872	872
873	873
874	874	Users can download the Node-Red decoder from this link and import it into the Node-Red platform:  **[[attach:LHT65N-ChirpStack-node-red.json||target="_blank"]]**
...	...	@@ -895,7 +895,7 @@
895	895	[[image:image-20230527144206-2.png||height="590" width="1136"]]
896	896
897	897
898		-(% style="color:blue" %)**3.** **Finally, click "Update" and Deploy**
	883	+(% style="color:blue" %)3. **Finally, click "Update" and Deploy**
899	899
900	900	"Connected" indicates that the Link Node-red to Local Chirpstack is normal.
901	901
...	...	@@ -902,7 +902,7 @@
902	902	[[image:http://wiki.dragino.com/xwiki/bin/download/Main/Notes%20for%20TTN/WebHome/image-20220914140918-5.png?width=1121&height=602&rev=1.1||alt="image-20220914140918-5.png"]]
903	903
904	904
905		-== 11.2 Check result. ==
	890	+== 10.2 Check result. ==
906	906
907	907
908	908	Users can check logs by adding debug.
...	...	@@ -912,9 +912,9 @@
912	912	[[image:image-20230529150923-1.png||height="424" width="1118"]]
913	913
914	914
915		-= 12.  Trouble Shooting =
	900	+= 11.  Trouble Shooting =
916	916
917		-== 12.1  MIC Mismatch or MIC Failed ==
	902	+== 11.1  MIC Mismatch or MIC Failed ==
918	918
919	919
920	920	(((
...	...	@@ -925,9 +925,8 @@
925	925	Under normal circumstances, users need to change the APPKEY to solve this problem.
926	926
927	927
928		-== 12.2  The node is very close to the gateway, but the signal is poor ==
	913	+== 11.2  The node is very close to the gateway, but the signal is poor ==
929	929
930		-
931	931	If you are using US915 or AU915, you found the frequency points of different subband ranges in your uplink
932	932
933	933	Like that：Both 905.1Mhz and 902.3Mhz appear on uplink
...	...	@@ -951,7 +951,5 @@
951	951
952	952	[[image:image-20230821113618-3.png]]
953	953
954		-**Note: lorawan's protocol link——[[LoRaWAN® Regional Parameters v1.0.3revA (lora-alliance.org)>>url:https://resources.lora-alliance.org/document/lorawan-regional-parameters-v1-0-3reva]]**
955		-
956		-
	938	+Note:lorawan's protocol link——[[LoRaWAN® Regional Parameters v1.0.3revA (lora-alliance.org)>>url:https://resources.lora-alliance.org/document/lorawan-regional-parameters-v1-0-3reva]]
957	957	)))