Summary

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

Details

Page properties

Content

...	...	@@ -649,21 +649,27 @@
649	649	[[image:image-20240923105725-1.png]]
650	650
651	651
652		-This example assumes users already have:
	652	+This example assumes that the user already has the prerequisites:
653	653
654		-* SN50v3-LB register on ChirpStack server already
655		-* The user is able to see the data on the ChirpStack server device page.
	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).
656	656
657	657	(% class="wikigeneratedid" %)
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).
	658	+ **AT command:** (% style="color:blue" %)**AT+CLASS=C**
659	659
660	660	(% class="wikigeneratedid" %)
661		-AT command: **AT+CLASS=C**
	661	+ (% style="color:blue" %)**AT+DISFCNTCHECK=1**
662	662
663	663	(% class="wikigeneratedid" %)
664		- **AT+DISFCNTCHECK=1**
	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]]**
665	665
	666	+* (% style="color:blue" %)**Chirpstack Configuration: **(%%)LPS8v2 gateway and SN50v3-LB register on ChirpStack server already
666	666
	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	+
667	667	=== Step 1. Create the multicast group ===
668	668
669	669
...	...	@@ -759,7 +759,7 @@
759	759	[[image:image-20240923151814-23.png||height="563" width="1255"]]
760	760
761	761
762		-= 9.  Multiply Uplink in ChirpStack =
	768	+= 10.  Multiply Uplink in ChirpStack =
763	763
764	764
765	765	(((
...	...	@@ -802,7 +802,7 @@
802	802	[[image:image-20220601102430-1.png||height="508" width="1120"]]
803	803
804	804
805		-== 9.1  Solution ==
	811	+== 10.1  Solution ==
806	806
807	807
808	808	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]]
...	...	@@ -921,7 +921,7 @@
921	921	Finish.
922	922
923	923
924		-= 10.  How to store/get all data traffic for a specific sensor, including raw payload, and uplink/ downlink history. =
	930	+= 11.  How to store/get all data traffic for a specific sensor, including raw payload, and uplink/ downlink history. =
925	925
926	926
927	927	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.
...	...	@@ -970,7 +970,7 @@
970	970	[[image:image-20221012173639-1.png||height="273" width="1206"]]
971	971
972	972
973		-= 11.  How to use Chirpstack API to batch register Sensor Node/Gateway in Chistapstack Server =
	979	+= 12.  How to use Chirpstack API to batch register Sensor Node/Gateway in Chistapstack Server =
974	974
975	975	The following example is based on the built-in ChirpStack server for LPS8V2
976	976
...	...	@@ -977,7 +977,7 @@
977	977	[[image:image-20231201174640-1.png||height="584" width="1148"]]
978	978
979	979
980		-== **11.1 Generate API Tokens** ==
	986	+== **12.1 Generate API Tokens** ==
981	981
982	982	Access the built-in chirpstack , click "**API Key**" and "**Add API Key**".
983	983
...	...	@@ -990,7 +990,7 @@
990	990	[[image:image-20231204104802-1.png]]
991	991
992	992
993		-== **11.2 Template file** ==
	999	+== **12.2 Template file** ==
994	994
995	995
996	996	Click on **"Template File Download"**, the user will download a **register.csv** template file,
...	...	@@ -1012,7 +1012,7 @@
1012	1012
1013	1013
1014	1014
1015		-== **11.3 Batch Register** ==
	1021	+== **12.3 Batch Register** ==
1016	1016
1017	1017	[[image:image-20231204113136-11.png||height="362" width="1062"]]
1018	1018
...	...	@@ -1025,7 +1025,7 @@
1025	1025
1026	1026
1027	1027
1028		-= 12.  Example: Use Local Server ChirpStack and Node-Red in LPS8v2 =
	1034	+= 13.  Example: Use Local Server ChirpStack and Node-Red in LPS8v2 =
1029	1029
1030	1030
1031	1031	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:
...	...	@@ -1036,7 +1036,7 @@
1036	1036	Below are the steps to plot the sensor data on LPS8v2 Node-Red.
1037	1037
1038	1038
1039		-== 12.1 Link Node-Red to Local ChirpStack ==
	1045	+== 13.1 Link Node-Red to Local ChirpStack ==
1040	1040
1041	1041
1042	1042	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"]]**
...	...	@@ -1070,7 +1070,7 @@
1070	1070	[[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"]]
1071	1071
1072	1072
1073		-== 12.2 Check result. ==
	1079	+== 13.2 Check result. ==
1074	1074
1075	1075
1076	1076	Users can check logs by adding debug.
...	...	@@ -1080,9 +1080,9 @@
1080	1080	[[image:image-20230529150923-1.png||height="424" width="1118"]]
1081	1081
1082	1082
1083		-= 13.  Trouble Shooting =
	1089	+= 14.  Trouble Shooting =
1084	1084
1085		-== 13.1  MIC Mismatch or MIC Failed ==
	1091	+== 14.1  MIC Mismatch or MIC Failed ==
1086	1086
1087	1087
1088	1088	(((
...	...	@@ -1093,7 +1093,7 @@
1093	1093	Under normal circumstances, users need to change the APPKEY to solve this problem.
1094	1094
1095	1095
1096		-== 13.2  The node is very close to the gateway, but the signal is poor ==
	1102	+== 14.2  The node is very close to the gateway, but the signal is poor ==
1097	1097
1098	1098
1099	1099	If you are using US915 or AU915, you found the frequency points of different subband ranges in your uplink
...	...	@@ -1122,7 +1122,7 @@
1122	1122	**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]]**
1123	1123
1124	1124
1125		-== 13.3  ChirpStackv4 node device displays "UPLINK_F_CNT_RETRANSMISSION" ==
	1131	+== 14.3  ChirpStackv4 node device displays "UPLINK_F_CNT_RETRANSMISSION" ==
1126	1126
1127	1127
1128	1128	This is because the node's packets are retransmitted, and the Fcnt of these packets is the same.
...	...	@@ -1153,7 +1153,7 @@
1153	1153	[[image:image-20240717092428-4.jpeg]]
1154	1154
1155	1155
1156		-== 13.4  How to get the log information of the node？ ==
	1162	+== 14.4  How to get the log information of the node？ ==
1157	1157
1158	1158
1159	1159	~1. Get information about a single node.

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

Author

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

Size

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

Content