Summary

• Page properties (1 modified, 0 added, 0 removed)
• Attachments (0 modified, 0 added, 3 removed)
  • image-20240717102613-5.png
  • image-20240831154333-1.png
  • image-20240923105725-1.png

Details

Page properties

Content

...	...	@@ -45,7 +45,7 @@
45	45
46	46	**Step 1: Add application**
47	47
48		-[[image:image-20240831154333-1.png||height="553" width="1074"]]
	48	+[[image:image-20230702094608-1.png||height="537" width="1015"]]
49	49
50	50
51	51	**Step 2：Fill name**
...	...	@@ -629,32 +629,6 @@
629	629	[[image:image-20220531174046-19.png]]
630	630
631	631
632		-= 9.  Chirpstack Multicast Configuration =
633		-
634		-
635		-== 9.1  Introduction ==
636		-
637		-ChirpStack has support for creating multicast-groups to which devices can be assigned. When enqueueing a downlink payload for a multicast-group, ChirpStack will analyze which gateways must be used for broadcasting to cover the complete multicast-group. This means that potentially, a single multicast downlink payload will be emitted multiple times.
638		-
639		-Multicast can be used for the following device-classes:
640		-
641		-* Class-B
642		-* Class-C
643		-
644		-== 9.2  Example to configure chirpstack Multicast ==
645		-
646		-
647		-This section illustrates how to configure ChirpStack Multicast. Below is the network structure, we use our LPS8v2 as the LoRaWAN gateway and SN50v3-LB as the LoRaWAN end-node here.
648		-
649		-[[image:image-20240923105725-1.png]]
650		-
651		-The LPS8V2 is already set to connect to Chirpstack. So what we need to do now is only configure register these devices to Chirpstack:
652		-
653		-
654		-=== Step 1. Create the multicast group ===
655		-
656		-
657		-
658	658	= 9.  Multiply Uplink in ChirpStack =
659	659
660	660
...	...	@@ -1025,30 +1025,13 @@
1025	1025
1026	1026	The user can Disable frame-counter validation on the chirpstack node and this warning message will not appear in the logs.
1027	1027
	1002	+[[image:https://qiye.aliyun.com/attachment/downloadex?ri=%2Falimail%2FinternalLinks%2FrefreshToken&o=1&et=normal&ext=png&e=kilight%40dragino.cc&f=008dd83c-c893-43e6-8ad3-731d3b8d7be0&m=2_0%3ADzzzzyNOXCB%24---.YRE7agI&n=image001.png]][[image:image-20240717085339-1.jpeg]]
1028	1028
1029		-The packet is retransmitted because the node device has enabled the acknowledgment uplink packet mode and the node cannot receive the ACK acknowledgment packet delivered by the gateway.
	1004	+[[image:image-20240717090537-2.jpeg||height="589" width="1078"]]
1030	1030
1031	1031
1032		-**The possible reasons are: **
1033		-
1034		-~1. The signal of the node device and the gateway is not good
1035		-
1036		-2. Too many node devices affect the downlink of the gateway
1037		-
1038		-
1039		-[[image:image-20240717085339-1.jpeg]]
1040		-
1041		-
1042		-* **Disable frame-counter validation**
1043		-
1044		-[[image:image-20240717102613-5.png||height="803" width="1211"]]
1045		-
1046		-
1047		-* **Result**
1048		-
1049	1049	[[image:image-20240717092428-4.jpeg]]
1050	1050
1051		-
1052	1052	== 13.4  How to get the log information of the node？ ==
1053	1053
1054	1054

image-20240717102613-5.png

Author

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

Size

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

Content

image-20240831154333-1.png

Author

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

Size

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

Content

image-20240923105725-1.png

Author

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

Size

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

Content