Changes for page Notes for ChirpStack
Last modified by Edwin Chen on 2025/01/30 09:53
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 3 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -206,12 +206,74 @@ 206 206 [[image:image-20220531172857-9.png]] 207 207 208 208 209 += 4. How the gateway connects to Chirpstack v4 via gateway-bridge = 209 209 210 -= 4. Downlink = 211 211 212 -== 4.1 Con vertHEXtoBase64==212 +== 4.1 Configure Packet Forwarder == 213 213 214 +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 214 214 216 +* In the **LoRaWAN** menu, click on **LoRaWAN ~-~- Semtech UDP** 217 +* Make sure the following settings are set: 218 +** **Service Provider:** //~-~-Custom/Private LoRaWAN~-~-// 219 +** **LoRaWAN Server Address:** //localhost or 127.0.0.1// 220 +** **Server port for upstream:** //1700// 221 +** **Server port for downstream:** //1700// 222 + 223 + Click **Save & Apply**. 224 + 225 +[[image:image-20221222114220-2.png||height="748" width="931"]] 226 + 227 + 228 +== 4.2 Configuring gateway frequency == 229 + 230 +Note: Gateway frequencies must match 231 + 232 +[[image:image-20221222134830-3.png||height="408" width="923"]] 233 + 234 + 235 +== 4.3 Modify the gateway-bridge configuration file == 236 + 237 + 238 +Run the gateway command line command to modify the gateway-bridge configuration file: 239 + 240 +(% class="box infomessage" %) 241 +((( 242 +root@dragino-1d27d4:~~# vim /etc/chirpstack-gateway-bridge/chirpstack-gateway-bridge.toml 243 +))) 244 + 245 +[[image:image-20221222113302-1.png]] 246 + 247 +[[image:image-20221222140203-4.png||height="875" width="806"]] 248 + 249 + 250 +(% class="wikigeneratedid" id="H" %) 251 +After the modification, run the following command: **/etc/init.d/chirpstack-gateway-bridge restart** 252 + 253 +== 4.3 (Re)start and stop gateway-bridge == 254 + 255 +Use the following commands to (re)start and stop the ChirpStack Gateway Bridge Service: 256 + 257 +(% class="box infomessage" %) 258 +((( 259 +**# start** 260 + 261 +/etc/init.d/chirpstack-gateway-bridge start 262 + 263 +**# stop** 264 + 265 +/etc/init.d/chirpstack-gateway-bridge stop 266 + 267 +**# restart** 268 + 269 +/etc/init.d/chirpstack-gateway-bridge restart 270 +))) 271 + 272 += 5. Downlink = 273 + 274 +== 5.1 Convert HEX to Base64 == 275 + 276 + 215 215 (% 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.** 216 216 217 217 **[[Online HEX to Base64 Converter>>https://base64.guru/converter/encode/hex]]:** ... ... @@ -225,7 +225,7 @@ 225 225 [[image:image-20221010193621-2.png]] 226 226 227 227 228 -== 4.2 Chirpstack Downlink Note ==290 +== 5.2 Chirpstack Downlink Note == 229 229 230 230 231 231 [[image:image-20220601102543-2.png]] ... ... @@ -246,7 +246,7 @@ 246 246 **Make sure the RX2DR is the same in the end node** 247 247 248 248 249 -== 4.3 Loraserver Downlink Note ==311 +== 5.3 Loraserver Downlink Note == 250 250 251 251 252 252 User can use MQTT to send downlink payload to ChirpStack to perform downstream to LoRaWAN End ... ... @@ -380,7 +380,7 @@ 380 380 [[image:image-20220531174046-19.png]] 381 381 382 382 383 -= 5. Multiply Uplink in ChirpStack =445 += 6. Multiply Uplink in ChirpStack = 384 384 385 385 386 386 ((( ... ... @@ -424,7 +424,7 @@ 424 424 425 425 426 426 427 -== 5.1 Solution ==489 +== 6.1 Solution == 428 428 429 429 430 430 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]] ... ... @@ -546,7 +546,7 @@ 546 546 Finish. 547 547 548 548 549 -= 6. How to store/get all data traffic for a specific sensor, including raw payload, and uplink/ downlink history.611 += 7. How to store/get all data traffic for a specific sensor, including raw payload, and uplink/ downlink history. = 550 550 551 551 552 552 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. ... ... @@ -595,9 +595,9 @@ 595 595 [[image:image-20221012173639-1.png]] 596 596 597 597 598 -= 7. Trouble Shooting =660 += 8. Trouble Shooting = 599 599 600 -== 7.1 MIC Mismatch or MIC Failed ==662 +== 8.1 MIC Mismatch or MIC Failed == 601 601 602 602 603 603 (((
- image-20221222114220-2.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Kilight - Size
-
... ... @@ -1,0 +1,1 @@ 1 +64.3 KB - Content
- image-20221222134830-3.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Kilight - Size
-
... ... @@ -1,0 +1,1 @@ 1 +54.5 KB - Content
- image-20221222140203-4.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Kilight - Size
-
... ... @@ -1,0 +1,1 @@ 1 +91.4 KB - Content