Summary

• Page properties (1 modified, 0 added, 0 removed)
• Attachments (0 modified, 0 added, 1 removed)
  • SN50v3-LB_协议008（AU915）(1).bin

Details

Page properties

Content

...	...	@@ -649,27 +649,21 @@
649	649	[[image:image-20240923105725-1.png]]
650	650
651	651
652		-This example assumes that the user already has the prerequisites:
	652	+This example assumes users already have:
653	653
654		-* (% style="color:blue" %)**SN50v3-LB Software Location:   **(%%)**[[SN50v3-LB_protocol_008(AU915).bin>>attach:https://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/SN50v3-LB/#H3.ConfigureSN50v3-LB2FLS||target="_blank"]] .**Users need to flash them with the firmware support Multicast.
655		-* (% style="color:blue" %)**SN50v3-LB Configure:   **(%%)Enable CLASS C and DISFCNTCHECK(The downlink fcnt is not compared with the fcnt of the node).
	654	+* SN50v3-LB register on ChirpStack server already
	655	+* The user is able to see the data on the ChirpStack server device page.
656	656
657	657	(% class="wikigeneratedid" %)
658		- **AT command:** (% style="color:blue" %)**AT+CLASS=C**
	658	+(% style="color:red" %)**Note: **(%%)SN50v3-LB must enable CLASS C and DISFCNTCHECK(The downlink fcnt is not compared with the fcnt of the node).
659	659
660	660	(% class="wikigeneratedid" %)
661		- (% style="color:blue" %)**AT+DISFCNTCHECK=1**
	661	+AT command: **AT+CLASS=C**
662	662
663	663	(% class="wikigeneratedid" %)
664		-For details on how to configure the SN50v3-LB, please refer to the link:** [[Configure SN50v3-LB>>https://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/SN50v3-LB/#H3.ConfigureSN50v3-LB2FLS]]**
	664	+ **AT+DISFCNTCHECK=1**
665	665
666		-* (% style="color:blue" %)**Chirpstack Configuration: **(%%)LPS8v2 gateway and SN50v3-LB register on ChirpStack server already
667	667
668		-Register LPS8v2 gateway to Chirpstack. See section :[[https:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Notes%20for%20ChirpStack/#H4.A0SemtechUDPforChirpStackv4>>https://wiki.dragino.com/xwiki/bin/view/Main/Notes%20for%20ChirpStack/#H4.A0SemtechUDPforChirpStackv4]]
669		-
670		-Register SN50v3-LB to Chirpstack. See section :[[https:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Notes%20for%20ChirpStack/#H2.A0Nodeusageintroduction>>https://wiki.dragino.com/xwiki/bin/view/Main/Notes%20for%20ChirpStack/#H2.A0Nodeusageintroduction]]
671		-
672		-
673	673	=== Step 1. Create the multicast group ===
674	674
675	675
...	...	@@ -765,7 +765,7 @@
765	765	[[image:image-20240923151814-23.png||height="563" width="1255"]]
766	766
767	767
768		-= 10.  Multiply Uplink in ChirpStack =
	762	+= 9.  Multiply Uplink in ChirpStack =
769	769
770	770
771	771	(((
...	...	@@ -808,7 +808,7 @@
808	808	[[image:image-20220601102430-1.png||height="508" width="1120"]]
809	809
810	810
811		-== 10.1  Solution ==
	805	+== 9.1  Solution ==
812	812
813	813
814	814	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]]
...	...	@@ -927,7 +927,7 @@
927	927	Finish.
928	928
929	929
930		-= 11.  How to store/get all data traffic for a specific sensor, including raw payload, and uplink/ downlink history. =
	924	+= 10.  How to store/get all data traffic for a specific sensor, including raw payload, and uplink/ downlink history. =
931	931
932	932
933	933	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.
...	...	@@ -976,7 +976,7 @@
976	976	[[image:image-20221012173639-1.png||height="273" width="1206"]]
977	977
978	978
979		-= 12.  How to use Chirpstack API to batch register Sensor Node/Gateway in Chistapstack Server =
	973	+= 11.  How to use Chirpstack API to batch register Sensor Node/Gateway in Chistapstack Server =
980	980
981	981	The following example is based on the built-in ChirpStack server for LPS8V2
982	982
...	...	@@ -983,7 +983,7 @@
983	983	[[image:image-20231201174640-1.png||height="584" width="1148"]]
984	984
985	985
986		-== **12.1 Generate API Tokens** ==
	980	+== **11.1 Generate API Tokens** ==
987	987
988	988	Access the built-in chirpstack , click "**API Key**" and "**Add API Key**".
989	989
...	...	@@ -996,7 +996,7 @@
996	996	[[image:image-20231204104802-1.png]]
997	997
998	998
999		-== **12.2 Template file** ==
	993	+== **11.2 Template file** ==
1000	1000
1001	1001
1002	1002	Click on **"Template File Download"**, the user will download a **register.csv** template file,
...	...	@@ -1018,7 +1018,7 @@
1018	1018
1019	1019
1020	1020
1021		-== **12.3 Batch Register** ==
	1015	+== **11.3 Batch Register** ==
1022	1022
1023	1023	[[image:image-20231204113136-11.png||height="362" width="1062"]]
1024	1024
...	...	@@ -1031,7 +1031,7 @@
1031	1031
1032	1032
1033	1033
1034		-= 13.  Example: Use Local Server ChirpStack and Node-Red in LPS8v2 =
	1028	+= 12.  Example: Use Local Server ChirpStack and Node-Red in LPS8v2 =
1035	1035
1036	1036
1037	1037	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:
...	...	@@ -1042,7 +1042,7 @@
1042	1042	Below are the steps to plot the sensor data on LPS8v2 Node-Red.
1043	1043
1044	1044
1045		-== 13.1 Link Node-Red to Local ChirpStack ==
	1039	+== 12.1 Link Node-Red to Local ChirpStack ==
1046	1046
1047	1047
1048	1048	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"]]**
...	...	@@ -1076,7 +1076,7 @@
1076	1076	[[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"]]
1077	1077
1078	1078
1079		-== 13.2 Check result. ==
	1073	+== 12.2 Check result. ==
1080	1080
1081	1081
1082	1082	Users can check logs by adding debug.
...	...	@@ -1086,9 +1086,9 @@
1086	1086	[[image:image-20230529150923-1.png||height="424" width="1118"]]
1087	1087
1088	1088
1089		-= 14.  Trouble Shooting =
	1083	+= 13.  Trouble Shooting =
1090	1090
1091		-== 14.1  MIC Mismatch or MIC Failed ==
	1085	+== 13.1  MIC Mismatch or MIC Failed ==
1092	1092
1093	1093
1094	1094	(((
...	...	@@ -1099,7 +1099,7 @@
1099	1099	Under normal circumstances, users need to change the APPKEY to solve this problem.
1100	1100
1101	1101
1102		-== 14.2  The node is very close to the gateway, but the signal is poor ==
	1096	+== 13.2  The node is very close to the gateway, but the signal is poor ==
1103	1103
1104	1104
1105	1105	If you are using US915 or AU915, you found the frequency points of different subband ranges in your uplink
...	...	@@ -1128,7 +1128,7 @@
1128	1128	**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]]**
1129	1129
1130	1130
1131		-== 14.3  ChirpStackv4 node device displays "UPLINK_F_CNT_RETRANSMISSION" ==
	1125	+== 13.3  ChirpStackv4 node device displays "UPLINK_F_CNT_RETRANSMISSION" ==
1132	1132
1133	1133
1134	1134	This is because the node's packets are retransmitted, and the Fcnt of these packets is the same.
...	...	@@ -1159,7 +1159,7 @@
1159	1159	[[image:image-20240717092428-4.jpeg]]
1160	1160
1161	1161
1162		-== 14.4  How to get the log information of the node？ ==
	1156	+== 13.4  How to get the log information of the node？ ==
1163	1163
1164	1164
1165	1165	~1. Get information about a single node.

SN50v3-LB_协议008（AU915）(1).bin

Author

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

Size

...	...	@@ -1,1 +1,0 @@
1		-89.2 KB

Content