Wiki source code of Notes for ChirpStack
Show last authors
author | version | line-number | content |
---|---|---|---|
1 | **~ Contents:** | ||
2 | |||
3 | {{toc/}} | ||
4 | |||
5 | = 1. Introduction = | ||
6 | |||
7 | (% style="color:black" %)The ChirpStack open-source LoRaWAN Network Server stack provides open-source components for LoRaWAN networks And the Chirpstack supports the users in building a private LoRaWAN Server. For more info please refer to this [[link>>url:https://www.chirpstack.io/]] | ||
8 | |||
9 | ((( | ||
10 | (% style="color:black" %)The dragino gateway can connect the ChirpStack server via Semtech UDP or Semtech Basic Station. | ||
11 | ))) | ||
12 | |||
13 | **Prerequisite** | ||
14 | |||
15 | 1) Have a Chirstack Server. | ||
16 | |||
17 | [[image:image-20220525100058-1.png]] | ||
18 | |||
19 | ChirpStack home page | ||
20 | |||
21 | |||
22 | 2) Gateway model support | ||
23 | |||
24 | (% class="box" %) | ||
25 | ((( | ||
26 | ((( | ||
27 | Semtech UDP : **All Model** | ||
28 | Basic Station : , , | ||
29 | **Note** : the firmware needs > if use the Bais station | ||
30 | ))) | ||
31 | ))) | ||
32 | |||
33 | = 2. Semtech UDP = | ||
34 | |||
35 | == 2.1 Step 1. Add the Network-servers == | ||
36 | |||
37 | The network-Servers address varies depending on the ChirpStack server setup environment | ||
38 | |||
39 | (% class="box" %) | ||
40 | ((( | ||
41 | Windows ~-~->Network-server server * : localhost:8000 | ||
42 | Linux ~-~->Network-server server * : chirpstack-network-server:8000 | ||
43 | ))) | ||
44 | |||
45 | If the user cannot add network-Servers, re-check the ChirpStack code or the server building process. | ||
46 | |||
47 | [[image:image-20220525100158-2.png]] | ||
48 | |||
49 | Add the Network-servers | ||
50 | |||
51 | == 2.2 Step 2. Create Gateway-profiles == | ||
52 | |||
53 | [[image:image-20220525100255-3.png]] | ||
54 | |||
55 | Create Gateway-profiles | ||
56 | |||
57 | == 2.3 Step 3. Create Service-profiles == | ||
58 | |||
59 | [[image:image-20220525100322-4.png]] | ||
60 | |||
61 | Create Service-profiles | ||
62 | |||
63 | In Step 3. Create Service-profiles, the above parameters can be set. If necessary, you can set them by yourself. This is only an example. | ||
64 | |||
65 | (% style="color:red" %)**Note : Before add the gateway, the user needs to complete the preceding three steps.** | ||
66 | |||
67 | If the user has completed the preceding steps, proceed to the next step. | ||
68 | |||
69 | == 2.4 Step 4. Add the gateway == | ||
70 | |||
71 | The example gateway id is: a840411e96744150 | ||
72 | |||
73 | ((( | ||
74 | (% style="color:red" %)**Note : The Gateway EUI and server addresses must match the ChirpStack configuration.** | ||
75 | ))) | ||
76 | |||
77 | [[image:image-20220525100350-5.png]] | ||
78 | |||
79 | Add the gateway | ||
80 | |||
81 | [[image:image-20220525100417-6.png]] | ||
82 | |||
83 | Configure the gateway | ||
84 | |||
85 | == 2.5 Step 5. Checking gateway Status == | ||
86 | |||
87 | [[image:image-20220525100448-7.png]] | ||
88 | |||
89 | gateway Status | ||
90 | |||
91 | [[image:image-20220525100516-8.png]] | ||
92 | |||
93 | gateway Status | ||
94 | |||
95 | = 3. Gateway Registration for Basics Station = | ||
96 | |||
97 | == Introduction == | ||
98 | |||
99 | 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. | ||
100 | |||
101 | ChirpStack Open-Source LoRaWAN® Network Server needs to set up a configuration that can use Semtech BasicStation. | ||
102 | |||
103 | **Below list the support products and Requirements:** | ||
104 | |||
105 | 1. LoRaWAN Gateway model: [[LIG16>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/171-lig16.html]], [[LG308>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/140-lg308.html]], [[DLOS8>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/160-dlos8.html]] ,[[LPS8>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/148-lps8.html]] | ||
106 | 1. Firmware version since :[[lgw~~-~~-build-v5.4.1651822913>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Test_Firmware/lgw--build-v5.4.1651822913-20220506-1543/]] | ||
107 | |||
108 | **How to set up chirpStack Basic Station** | ||
109 | |||
110 | Users can check out the ChirpStack Basic Station [[link>>https://www.chirpstack.io/gateway-bridge/backends/basic-station/]] and [[forum>>https://forum.chirpstack.io/search?q=basic%20station]] | ||
111 | |||
112 | **What do you need to prepare** | ||
113 | |||
114 | A gateway that can access the internet normally | ||
115 | |||
116 | == 3.1 Add Gateway == | ||
117 | |||
118 | [[image:image-20220524164205-10.png]] | ||
119 | |||
120 | == 3.2 Access the gateway GUI == | ||
121 | |||
122 | Access the gateway GUI interface of LoRaWAN~-~->LoRaWAN ~-~- Basic Station | ||
123 | |||
124 | [[image:image-20220524164319-11.png]] | ||
125 | |||
126 | User need to Choose the ChirpStack/Senet ~-~- Basic Station , input Server URI and Upload the TLS Certificate | ||
127 | |||
128 | (% class="box" %) | ||
129 | ((( | ||
130 | Service Provider ~-~-> Choose the ChirpStack/Senet ~-~- Basic Station | ||
131 | |||
132 | LNS URI ~-~-> Enter the LNS URI address, For example : wss:~/~/xxxx.chirpstack.com:433 or ws:~/~/xxxx.chirpstack.com:3001 | ||
133 | |||
134 | LNS TLS trust ~-~-> Upload the TLS Certificate | ||
135 | ))) | ||
136 | |||
137 | (% class="wikigeneratedid" %) | ||
138 | [[image:image-20220524164341-12.png]] | ||
139 | |||
140 | == 3.3 Start Station == | ||
141 | |||
142 | When the user has finished the configuration, Please click Sace&Apply to start station to connect ChirpStack | ||
143 | |||
144 | == 3.4 Successful Connection == | ||
145 | |||
146 | If user completes the above steps, which will see live date in the ChirpStack. | ||
147 | |||
148 | [[image:image-20220524164448-13.png]] | ||
149 | |||
150 | == 3.5 Trouble Shooting == | ||
151 | |||
152 | User can check the station log in the logread/system log page. | ||
153 | |||
154 | [[image:image-20220524164514-14.png]] | ||
155 | |||
156 | and recode the station log in the system/Recode log page. | ||
157 | |||
158 | [[image:image-20220524164541-15.png]] | ||
159 | |||
160 | = 4. Downlink = | ||
161 | |||
162 | == 4.1 Chirpstack Downlink Note == | ||
163 | |||
164 | [[image:image-20220525101223-9.png]] | ||
165 | |||
166 | Convert the data to Base64 | ||
167 | |||
168 | [[image:image-20220525101247-10.png]] | ||
169 | |||
170 | Check ChripStack downlink DataRate | ||
171 | |||
172 | [[image:image-20220524164724-18.png]] | ||
173 | |||
174 | Make sure the RX2DR is the same in the end node | ||
175 | |||
176 | == 4.2 Loraserver Downlink Note == | ||
177 | |||
178 | User can use MQTT to send downlink payload to ChirpStack to perform downstream to LoRaWAN End | ||
179 | |||
180 | ((( | ||
181 | Below is examples: | ||
182 | ))) | ||
183 | |||
184 | (% class="box" %) | ||
185 | ((( | ||
186 | Connect to your server via MQTT: | ||
187 | MQTT Client ID: Any | ||
188 | Protocol:mqtt/tcp Server IP:loraserver_ip:1883 | ||
189 | User name: User name Password: password | ||
190 | ))) | ||
191 | |||
192 | [[image:image-20220524164806-19.png]] | ||
193 | |||
194 | ((( | ||
195 | MQTT Connect to ChirpStack | ||
196 | ))) | ||
197 | |||
198 | ((( | ||
199 | After connect | ||
200 | ))) | ||
201 | |||
202 | (% class="box" %) | ||
203 | ((( | ||
204 | Subscribe : Format:application/ID/device/ Device EUI/rx | ||
205 | Example: application/7/device/00aedb3da649cb23/rx | ||
206 | ))) | ||
207 | |||
208 | (% class="box" %) | ||
209 | ((( | ||
210 | Publish: | ||
211 | Format: Top: application/ID/device/ Device EUI/tx | ||
212 | Payload: {"confirmed":true or false,"fPort":XX,"data":"xxxx"} | ||
213 | Example: Top: application/7/device/00aedb3da649cb23/tx | ||
214 | Payload: {"confirmed":true,"fPort":2,"data":"AwEB"} | ||
215 | ))) | ||
216 | |||
217 | [[image:image-20220524164829-20.png]] | ||
218 | |||
219 | MQTT Connect to ChirpStack | ||
220 | |||
221 | ((( | ||
222 | (% style="color:red" %)Note: Chirpstack use base64 to downlink, so need to convert the downlink payload from HEX to base64 [[https:~~/~~/base64.us/>>url:https://base64.us/]] | ||
223 | ))) | ||
224 | |||
225 | [[image:image-20220524164849-21.png]] | ||
226 | |||
227 | Choose to Use Hex for Encode | ||
228 | |||
229 | If we want send downstream hex 030101 to end node, the BASE64 payload is AwEB | ||
230 | |||
231 | [[image:image-20220524164907-22.png]] | ||
232 | |||
233 | ((( | ||
234 | Downlink payload encode javescript code: 可以在网站上运行以下Javsscript代码: | ||
235 | ))) | ||
236 | |||
237 | (% class="box" %) | ||
238 | ((( | ||
239 | function sha1_to_base64(sha1) | ||
240 | { | ||
241 | var digits="ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789+/"; | ||
242 | var base64_rep = ""; | ||
243 | var cnt = 0; | ||
244 | var bit_arr = 0; | ||
245 | var bit_num = 0; | ||
246 | \\ for(var n = 0; n < sha1.length; ++n) | ||
247 | { | ||
248 | if(sha1[n] >= 'A' && sha1[n] <= 'Z') | ||
249 | { | ||
250 | ascv = sha1.charCodeAt(n) - 55; | ||
251 | } | ||
252 | else if(sha1[n] >= 'a' && sha1[n] <= 'z') | ||
253 | { | ||
254 | ascv = sha1.charCodeAt(n) - 87; | ||
255 | } | ||
256 | else | ||
257 | { | ||
258 | ascv = sha1.charCodeAt(n) - 48; | ||
259 | } | ||
260 | \\ bit_arr = (bit_arr << 4) | ascv; | ||
261 | bit_num += 4; | ||
262 | if(bit_num >= 6) | ||
263 | { | ||
264 | bit_num -= 6; | ||
265 | base64_rep += digits[bit_arr >>> bit_num]; | ||
266 | bit_arr &= ~~(-1 << bit_num); | ||
267 | } | ||
268 | } | ||
269 | \\ if(bit_num > 0) | ||
270 | { | ||
271 | bit_arr <<= 6 - bit_num; | ||
272 | base64_rep += digits[bit_arr]; | ||
273 | } | ||
274 | \\ var padding = base64_rep.length % 4; | ||
275 | \\ if(padding > 0) | ||
276 | { | ||
277 | for(var n = 0; n < 4 - padding; ++n) | ||
278 | { | ||
279 | base64_rep += "="; | ||
280 | } | ||
281 | } | ||
282 | return base64_rep; | ||
283 | } | ||
284 | \\console.log(sha1_to_base64("data")); | ||
285 | \\data is downlink payload required by end node. | ||
286 | e.g console.log(sha1_to_base64("030101")); | ||
287 | result: AwEB | ||
288 | AwEB is the 0x030101's base 64 Encode. | ||
289 | \\e.g console.log(sha1_to_base64("030000")); | ||
290 | result: AwAA | ||
291 | AwAA is 0x030000's base 64 Encode. | ||
292 | ))) | ||
293 | |||
294 | == 4.3 Add the decode function in Chirpstack for the payload == | ||
295 | |||
296 | User enters the payload code according to the steps. | ||
297 | |||
298 | [[image:image-20220524165001-23.png]] | ||
299 | |||
300 | [[image:image-20220524165028-24.png]] | ||
301 | |||
302 | [[image:image-20220524165100-25.png]] | ||
303 | |||
304 | [[image:image-20220524165116-26.png]] | ||
305 | |||
306 | = 5. Multiply Uplink in ChirpStack = | ||
307 | |||
308 | ((( | ||
309 | nbtrans field is the value to determine the re-transmission time for unconfirmed uplink data. | ||
310 | ))) | ||
311 | |||
312 | ((( | ||
313 | ChirpStack will auto adjust nbtrans according to uplink rssi. [[link to source>>url:https://github.com/brocaar/chirpstack-network-server/blob/master/internal/adr/adr.go]] | ||
314 | ))) | ||
315 | |||
316 | [[image:image-20220524165141-27.png]] | ||
317 | |||
318 | ((( | ||
319 | nbtrans is a field of ADR message, in unconfirm mode, it tells end node how many time it needs to transmit for every frame. | ||
320 | ))) | ||
321 | |||
322 | [[image:image-20220524165158-28.png]] | ||
323 | |||
324 | ((( | ||
325 | Above behaviour will cause the platform shows below two cases of error: | ||
326 | ))) | ||
327 | |||
328 | ((( | ||
329 | Error of duplicate Frame Counter | ||
330 | ))) | ||
331 | |||
332 | [[image:image-20220524165301-29.png]] | ||
333 | |||
334 | Duplicate transmission in short time | ||
335 | |||
336 | [[image:image-20220524165319-30.png]] | ||
337 | |||
338 | == 5.1 Solution == | ||
339 | |||
340 | 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]] | ||
341 | |||
342 | ((( | ||
343 | ~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. | ||
344 | ))) | ||
345 | |||
346 | [[image:image-20220524165339-31.png]] | ||
347 | |||
348 | installation path: | ||
349 | |||
350 | [[image:image-20220524165400-32.png]] | ||
351 | |||
352 | ((( | ||
353 | 2. Environment variable settings:. | ||
354 | ))) | ||
355 | |||
356 | ((( | ||
357 | 1) Open Computer -> Properties -> Advanced System Settings -> Environment Variables and add a "new" system variable: | ||
358 | ))) | ||
359 | |||
360 | ((( | ||
361 | 2)Set the variable name GOROOT and the variable value C:\Go\ (installation directory) | ||
362 | ))) | ||
363 | |||
364 | [[image:image-20220524165433-33.png]] | ||
365 | |||
366 | 3)Modify the system variable Path and add C:\Go\bin\: | ||
367 | |||
368 | [[image:image-20220524165452-34.png]] | ||
369 | |||
370 | User variable setting file generation directory: D:\go: | ||
371 | |||
372 | [[image:image-20220524165517-35.png]] | ||
373 | |||
374 | 3. Modify the ADR configuration file according to your own needs, adr.setting.go is an example of the ADR configuration file. | ||
375 | |||
376 | The name of the plugin: Example ADR plugin: | ||
377 | |||
378 | [[image:image-20220524165540-36.png]] | ||
379 | |||
380 | Set Nbtrans: Nbtrans=1 (Nbtrans is the number of retransmissions, if it is 1, no retransmission, it is recommended to be 1). To enable it, you need to uncomment. | ||
381 | |||
382 | [[image:image-20220524165557-37.png]] | ||
383 | |||
384 | 4. Compile the ADR configuration file and generate the exe file. | ||
385 | |||
386 | 1) Create a folder named adr-setting | ||
387 | |||
388 | 2) Open the adr-setting folder | ||
389 | |||
390 | 3) Put adr.setting.go in this folder. | ||
391 | |||
392 | 4) Open the computer cmd and run the following commands in sequencecd adr-setting | ||
393 | |||
394 | go mod init adr-setting | ||
395 | |||
396 | go get github.com/brocaar/chirpstack-network-server/v3/adr | ||
397 | |||
398 | go get github.com/hashicorp/go-plugin | ||
399 | |||
400 | go get adr-setting | ||
401 | |||
402 | go build | ||
403 | |||
404 | 5) Finally generate this file: | ||
405 | |||
406 | [[image:image-20220524165623-38.png]] | ||
407 | |||
408 | 5. Add the plugin and run the plugin. | ||
409 | |||
410 | ((( | ||
411 | The exe file generated in the previous step is placed in the same root directory as chirpstack-network-server.toml, and the ADR plugin is added to the toml file. The location of the addition is as follows: | ||
412 | ))) | ||
413 | |||
414 | [[image:image-20220524165641-39.png]] | ||
415 | |||
416 | ((( | ||
417 | ((( | ||
418 | For example: adr_plugins=[“adr-setting”] | ||
419 | ))) | ||
420 | ))) | ||
421 | |||
422 | * ((( | ||
423 | ((( | ||
424 | Adding a single plugin format is adr_plugins=["filename"] | ||
425 | ))) | ||
426 | ))) | ||
427 | |||
428 | * ((( | ||
429 | ((( | ||
430 | Adding multiple plugins The format is adr_plugins=["file name 1", "file name 2",...] | ||
431 | ))) | ||
432 | ))) | ||
433 | |||
434 | ((( | ||
435 | ((( | ||
436 | Finally, re-run chirpstack-network-server.exe, and then select the plugin you just compiled in Device-profiles, | ||
437 | ))) | ||
438 | ))) | ||
439 | |||
440 | [[image:image-20220524165659-40.png]] | ||
441 | |||
442 | Finish. | ||
443 | |||
444 | = 6. Trouble Shooting = | ||
445 | |||
446 | == 6.1 MIC Mismatch or MIC Failed == | ||
447 | |||
448 | ((( | ||
449 | When the device is registered or the device is working normally, the problem of MIC mismatch and MIC failed occurs. | ||
450 | ))) | ||
451 | |||
452 | ((( | ||
453 | Under normal circumstances, users need to change the APPKEY to solve this problem. | ||
454 | ))) |