Wiki source code of Notes for TTN

Version 41.1 by Xiaoling on 2022/05/25 09:25
Show last authors
1 **~ Contents：**
2
3 {{toc/}}
4
5
6 = 1. The Things Network-V3 =
7
8 == 1.1 Introduction ==
9
10 === 1.1.1 What is The Things Network ===
11
12 (((
13 The Things Network is a global collaborative Internet of Things ecosystem that creates networks, devices and solutions using LoRaWAN.
14 )))
15
16 (((
17 The Things Network runs The Things Stack Community Edition, which is a crowdsourced, open and decentralized LoRaWAN network. This network is a great way to get started testing devices, applications, and integrations, and get familiar with LoRaWAN.
18 )))
19
20 === 1.1.2 Login or crate an account ===
21
22 (((
23 [[Login or create an account>>url:https://console.cloud.thethings.network/]] to get started with The Things Network and start using The Things Stack Console.
24 )))
25
26 (((
27 Once you have an account,get started by following steps for adding Gateway,Device and Intergrations.
28 )))
29
30 === 1.1.3 List the support products and Requirements ===
31
32 LoRaWAN Gateway model: Existing Gateway
33
34 = 2. Gateway Registration for Semtech UDP =
35
36 == 2.1 Primary LoRaWAN Server ==
37
38 [[image:image-20220525084853-1.png]]
39
40 Register Gateway
41
42
43 [[image:image-20220525084923-2.png]]
44
45 Put Gateway ID
46
47
48 [[image:image-20220525085016-3.png]]
49
50 Choose Frequency Band
51
52
53 [[image:image-20220525085054-4.png]]
54
55 Show Status
56
57 == 2.2 Secondary LoRaWAN Server ==
58
59 === 2.2.1 Introduction ===
60
61 The Dragino gateway has supports the Secondary server settings.
62
63 === 2.2.2 Below list the support products and Requirements: ===
64
65 (((
66 ~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]]
67 )))
68
69 (((
70 2. Firmware version since :[[lgw~~-~~-build-v5.4.1644658774>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LIG16/Firmware/Release/]]
71 )))
72
73 === 2.2.3 Example ===
74
75 The following takes Helium as a Secondary LoRaWAN server as an example,
76
77 === 2.2.4 Step 1: Download and Install the helium gateway-rs ===
78
79 The users is needing to download and install the helium gateway-rs then click the button of Save&Apply
80
81 [[image:image-20220525085117-5.png]]
82
83 Download and Install gateway-rs
84
85 === 2.2.5 Step 2: Back to Semtech UDP page ===
86
87 Back to the page of Semtech UDP check the secondary server settings and click the button of Save&Apply
88
89 [[image:image-20220525085152-6.png]]
90
91 Configuration of helium
92
93 = 3. Gateway Registration for Basics Station =
94
95 == 3.1 Introduction ==
96
97 (((
98 (((
99 The LoRa Basics™ Station protocol simplifies management of large scale LoRaWAN networks. LoRa Basics™ Station is the preferred way of connecting Gateways to The Things Stack. [[The LoRa Basics Station doc>>url:https://www.thethingsindustries.com/docs/gateways/lora-basics-station/]]
100 )))
101 )))
102
103 (((
104 **Below list the support products and Requirements:**
105 )))
106
107 (((
108 (((
109 ~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]]
110 )))
111
112 (((
113 2. Firmware version since :[[lgw~~-~~-build-v5.4.1640315898>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/]]
114 )))
115 )))
116
117 (((
118 **What do you need to prepare**
119 )))
120
121 (((
122 (((
123 A gateway that can access the internet normally
124 )))
125 )))
126
127 == 3.2 Step 1. Add Gateway ==
128
129 (((
130 (((
131 The example for **EU**
132 )))
133 )))
134
135 (((
136 (((
137 User can add your gateway into The Things Network V3 according to the previous step
138 )))
139 )))
140
141 (((
142 (((
143 Following picture is the successful added.
144 )))
145 )))
146
147 [[image:image-20220525085231-7.png]]
148
149 Add Gateway
150
151 == 3.3 Step 2. Create the API key ==
152
153 user need to create the CUPS API key and LNS API key.
154
155 [[image:image-20220525085329-8.png]]
156
157 Create CUPS API key
158
159
160 [[image:image-20220525085414-9.png]]
161
162 Create LNS API key
163
164 (% style="color:red" %)**Note : Please copy the API key.**
165
166 == 3.4 Step 3. Update the gateway setting ==
167
168 In the LoRa Basics Station LNS Authentication Key field, paste the API key you generated in the previous step.
169
170 [[image:image-20220525085441-10.png]]
171
172 paste the API key
173
174 == 3.5 Step 4. Access the gateway GUI ==
175
176 User need to update the API key and install the Certificate
177
178 [[image:image-20220525085522-11.png]]
179
180 Access the gateway GUI
181
182 == 3.6 Step 5. Configure Station ==
183
184 User need to input Server URI, Server CUPS Key and LNS Key, as well as install CUPS certificate.
185
186 **just to clarify.**
187
188 (% class="box" %)
189 (((
190 CUPS Server URI  ~-~-> Server Adress
191 CUPS Authorization Key         ~-~-> Server CUPS API Key
192 LNS Authorization Key  ~-~-> Server LNS API Key
193 CUPS certificate  ~-~-> Server CA(user can use the button to install the certificate by default)
194 )))
195
196 [[image:image-20220525085557-12.png]]
197
198 Congfigure Station
199
200 == 3.7 Start Station ==
201
202 (((
203 When the user has finished the configuration,Please click Sace&Apply to start station to connect The Things Network.
204 )))
205
206 == 3.8 Siccessful Connection ==
207
208 If user completes the above steps,which will see live date in the TTN.
209
210 [[image:image-20220525085636-13.png]]
211
212 Station live date
213
214 == 3.9 Trouble Shooting ==
215
216 User can check the station log in the logread/system log page.
217
218 [[image:image-20220525090622-14.png]]
219
220 Station Log
221
222 and recode the station log in the system/Recode log page.
223
224 [[image:image-20220525090705-15.png]]
225
226 Recore Log
227
228 = 4. Configure node connection to TTNv3 =
229
230 (((
231 (((
232 Following is an example for how to join the TTN v3 LoRaWAN Network.
233 )))
234 )))
235
236 (((
237 (((
238 The gateway is already set up to connect to the TTN network, so we now need to configure the TTNv3 server.
239 )))
240 )))
241
242 (((
243 (((
244 We take LES01 as an example.
245 )))
246 )))
247
248 == 4.1 Step1 ==
249
250 (((
251 (((
252 Create a device in TTN with the OTAA keys from LSE01.
253 )))
254 )))
255
256 (((
257 (((
258 Each LSE01 is shipped with a sticker with the default device EUI as below:
259 )))
260 )))
261
262 (((
263 (((
264 You can enter this key in the LoRaWAN Server portal. Below is TTN screen shot:
265 )))
266 )))
267
268 [[image:image-20220525090739-16.png]]
269
270 [[image:image-20220525090833-17.png]]
271
272 == 4.2 Step2 ==
273
274 (((
275 (((
276 There are all our nodes in the repository. Users can choose the corresponding brand, model, firmware version and frequency.The decoder and configuration information of the node are pre-configured.Users do not need to configure them.
277 )))
278 )))
279
280 [[image:image-20220525090920-18.png]]
281
282 == 4.3 Step3 ==
283
284 Add APP EUI in the application:
285
286 [[image:image-20220525091022-19.png]]
287
288 == 4.4 Step4 ==
289
290 Add APP KEY and DEV EUI:
291
292 [[image:image-20220525091128-20.png]]
293
294 = 5. TTN V3 integrated into MQTT server =
295
296 == 5.1 Introduction ==
297
298 (((
299 (((
300 The Application Server exposes an MQTT server to work with streaming events. In order to use the MQTT server you need to create a new API key, which will function as connection password. You can also use an existing API key, as long as it has the necessary rights granted.
301 )))
302 )))
303
304 == 5.2 Create device steps at MQTT ==
305
306 (((
307 (((
308 The user creates a new API KEY after creating a device on TTN V3.
309 )))
310 )))
311
312 (((
313 (((
314 Then copy the password and open MQTT.fx.
315 )))
316 )))
317
318 (((
319 (((
320 Fill in Broker Address and Broker port.
321 )))
322 )))
323
324 [[image:image-20220525091251-22.png]]
325
326 Fill in the username and password into MQTT.
327
328
329 [[image:image-20220525091333-23.png]]
330
331 The Application Server publishes uplink traffic on the following topics:
332
333 (% class="box" %)
334 (((
335 v3/{application id}@{tenant id}/devices/{device id}/join
336 v3/{application id}@{tenant id}/devices/{device id}/up
337 v3/{application id}@{tenant id}/devices/{device id}/down/queued
338 v3/{application id}@{tenant id}/devices/{device id}/down/sent
339 v3/{application id}@{tenant id}/devices/{device id}/down/ack
340 v3/{application id}@{tenant id}/devices/{device id}/down/nack
341 v3/{application id}@{tenant id}/devices/{device id}/down/failed
342 v3/{application id}@{tenant id}/devices/{device id}/service/data
343 v3/{application id}@{tenant id}/devices/{device id}/location/solved
344 )))
345
346 (((
347 (((
348 **Note**: Remember that the format of these topics for The Things Stack Open Source would contain {application id} instead of {application id}@{tenant id}.
349 )))
350 )))
351
352 [[image:image-20220525091430-24.png]]
353
354 (((
355 (((
356 While you could subscribe to all of these topics separately, for the simplicity of this tutorial we use # to subscribe to all topics, i.e. to receive all uplink traffic.
357 )))
358 )))
359
360 [[image:image-20220525091458-25.png]]
361
362 (((
363 (((
364 Downlinks can be scheduled by publishing the message to the topic v3/{application id}@{tenant id}/devices/{device id}/down/push.
365 )))
366 )))
367
368 (((
369 (((
370 **Note**: Remember that the format of this topic for The Things Stack Open Source deployment would be v3/{application id}/devices/{device id}/down/push.
371 )))
372 )))
373
374 (((
375 (((
376 Instead of /push, you can also use /replace to replace the downlink queue. Replacing with an empty array clears the downlink queue. Example:
377 )))
378 )))
379
380 [[image:image-20220525091618-27.png]]
381
382 (((
383 To send an unconfirmed downlink message to the device dev1 in application app1 in tenant tenant1 with the hexadecimal payload BE EF on FPort 15 with normal priority, use the topic v3/app1@tenant1/devices/dev1/down/push with the following contents:
384 )))
385
386 (((
387 **Note**: Use this handy tool to convert hexadecimal to base64.
388 )))
389
390 [[image:image-20220525091702-28.png]]
391
392 == 5.3 Send Downlink message ==
393
394 (((
395 How to configure downlink in TTN V3?
396 )))
397
398 (((
399 A few examples: set the transmission interval to 90 seconds.
400 )))
401
402 (((
403 Downlink command:01 00 00 5A
404 )))
405
406 [[image:image-20220525091752-29.png]]
407
408 downlink
409
410 After sending, you can view it in live data.
411
412 [[image:image-20220525091816-30.png]]
413
414 downlink
415
416 (((
417 When downlink is successfully sent, the downlink information can be received on the serial port.
418 )))
419
420 (((
421 **Note**: If the downlink byte sent is longer, the number of bytes will be displayed.
422 )))
423
424 [[image:image-20220525091855-31.png]]
425
426 downlink
427
428 (((
429 (((
430 If you want to get a successful reply to send downlink in TTN v3. You need to set the response level.
431 )))
432 )))
433
434 (((
435 (((
436 If the equipment uses CLASS A. You can set **AT+RPL=2** or send the downlink command: **2102**
437 )))
438 )))
439
440 (((
441 (((
442 If the equipment uses CLASS C. You can set** AT+RPL=4** or send the downlink command: **2104**
443 )))
444 )))
445
446 (((
447 (((
448 When the device successfully receives the downlink, the server will receive a confirmation packet of 00.
449 )))
450 )))
451
452 [[image:image-20220525091925-32.png]]
453
454 downlink
455
456 = 6. Request Remote Support =
457
458 (((
459 These pages are useful to check what is wrong on the Join process. Below shows the four steps that we can check the Join Process.
460 \\If problem not solve, and you need dragino remote support, please follow to this document: [[TTN Support instruction>>url:https://www.dragino.com/downloads/index.php?dir=&file=TTNv3_Support_Guide.pdf]](% style="color:red" %) **If user has checked below steps and still can't solve the problem, please send us (support @ dragino.com) the screenshots for each step to check. They include:**
461 )))
462
463 * End node is connected to serial port to show the Join frequency and DR. (If possible)
464 * Gateway (from gateway UI) traffic to show the packet got from end node and receive from Server. (If possible)
465 * Gateway traffic (from server UI) to shows the data exchange between gateway and server. (Normally possible)
466 * End Node traffic (from server UI) to shows end node activity in server. (Normally possible)
467 * End Node Keys screen shot shows in end node and server. so we can check if the keys are correct. (In most case, we found keys doesn't match, especially APP EUI)
468
469 **~1. End Device Join Screen shot, we can check:**
470
471 * If the device is sending join request to server?
472 * What frequency the device is sending?
473
474 [[image:image-20220525092012-33.png]]
475
476 Console Output from End device to see the transmit frequency
477
478 User can run **AT+CFG **command to print configuration information.
479
480 * Is the device in OTAA mode or ABP mode? **AT+NJM=1** (OTAA mode), **AT+NJM=0** (ABP mode)
481
482 [[image:image-20220525092043-34.png]]
483
484 Console Output from End device to see the transmit frequency
485
486 **2. Gateway packet traffic in gateway web or ssh. we can check:**
487
488 * (((
489 If the gateway receive the Join request packet from sensor? (If this fail, check if the gateway and sensor works on the match frequency)
490 )))
491 * (((
492 If the gateway gets the Join Accept message from server and transmit it via LoRa?
493 )))
494
495 [[image:image-20220525092124-35.png]]
496
497 Console Output from Gateway to see packets between end node and server.
498
499
500 **3. Gateway Traffic Page in LoRaWAN Server**
501
502 * (((
503 If the Join Request packet arrive the gateway traffic in server? If not, check the internet connection and gateway LoRaWAN server settings.
504 )))
505 * (((
506 If the server send back a Join Accept for the Join Request? if not, check if the keys from the device match the keys you put in the server, or try to choose a different server route for this end device.
507 )))
508 * (((
509 If the Join Accept message are in correct frequency? If you set the server to use US915 band, and your end node and gateway is EU868, you will see the Join Accept message are in US915 band so no possible to Join success.
510 )))
511
512 [[image:image-20220525092157-36.png]]
513
514 The Traffic for the End node in the server, use TTNv3 as example
515
516
517 [[image:image-20220525092231-37.png]]
518
519 The Traffic for the End node in the server, use TTNv3 as example
520
521 **4. Data Page in LoRaWAN server**
522
523 * (((
524 (((
525 (((
526 If this data page shows the Join Request message from the end node? If not, most properly you have wrong settings in the keys. Keys in the server doesn't match the keys in End Node.
527 )))
528 )))
529 )))
530
531
532 The data for the end device set in server
533
534 [[image:image-20220525092430-40.png]]
535
536 Check if OTAA Keys match the keys in device

Applications

Navigation

Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0