Changes for page Notes for TTN

Last modified by Mengting Qiu on 2024/08/20 17:29
<
From version < 99.18 >
edited by Xiaoling
on 2022/07/25 09:19
To version < 67.1 >
edited by Xiaoling
on 2022/05/26 13:53
>
Change comment: Uploaded new attachment "image-20220526135316-8.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -1,18 +1,14 @@
1 -**~ Table of Contents：**
1 +**~ Contents：**
2 2  
3 3  {{toc/}}
4 4  
5 5  
6 -
7 7  = 1. The Things Network-V3 =
8 8  
8 +== 1.1 Introduction ==
9 9  
10 -== 1.1  Introduction ==
10 +=== 1.1.1 What is The Things Network ===
11 11  
12 -
13 -=== 1.1.1  What is The Things Network ===
14 -
15 -
16 16  (((
17 17  The Things Network is a global collaborative Internet of Things ecosystem that creates networks, devices and solutions using LoRaWAN.
18 18  )))
... ... @@ -20,13 +20,11 @@
20 20  (((
21 21  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.
22 22  
23 -
24 24  
25 25  )))
26 26  
27 -=== 1.1.2  Login or crate an account ===
22 +=== 1.1.2 Login or crate an account ===
28 28  
29 -
30 30  (((
31 31  [[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.
32 32  )))
... ... @@ -34,149 +34,114 @@
34 34  (((
35 35  Once you have an account,get started by following steps for adding Gateway,Device and Intergrations.
36 36  
37 -
38 38  
39 39  )))
40 40  
41 -=== 1.1.3  List the support products and Requirements ===
34 +=== 1.1.3 List the support products and Requirements ===
42 42  
43 -
44 44  LoRaWAN Gateway model: Existing Gateway
45 45  
46 46  
39 += 2. Gateway Registration for Semtech UDP =
47 47  
48 -= 2.  Gateway Registration for Semtech UDP =
41 +== 2.1 Primary LoRaWAN Server ==
49 49  
50 -
51 -== 2.1  Primary LoRaWAN Server ==
52 -
53 -
54 54  [[image:image-20220526134633-2.png||height="616" width="1323"]]
55 55  
56 56  Register Gateway
57 57  
58 58  
59 -
60 60  [[image:image-20220526134826-4.png]]
61 61  
62 62  Put Gateway ID
63 63  
64 64  
65 -
66 66  [[image:image-20220526134759-3.png]]
67 67  
68 68  Choose Frequency Band
69 69  
70 70  
71 -
72 72  [[image:image-20220526134919-5.png]]
73 73  
74 74  Show Status
75 75  
76 76  
63 +== 2.2 Secondary LoRaWAN Server ==
77 77  
78 -== 2.2  Secondary LoRaWAN Server ==
65 +=== 2.2.1 Introduction ===
79 79  
80 -
81 -=== 2.2.1  Introduction ===
82 -
83 -
84 84  The Dragino gateway has supports the Secondary server settings.
85 85  
86 86  
70 +=== 2.2.2 Below list the support products and Requirements: ===
87 87  
88 -=== 2.2.2  Below list the support products and Requirements: ===
89 -
90 -
91 91  (((
92 -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]]
73 +~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]]
93 93  )))
94 94  
95 95  (((
96 -2.  Firmware version since :  [[lgw~~-~~-build-v5.4.1644658774>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LIG16/Firmware/Release/]]
77 +2. Firmware version since :[[lgw~~-~~-build-v5.4.1644658774>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LIG16/Firmware/Release/]]
97 97  )))
98 98  
99 99  
81 +=== 2.2.3 Example ===
100 100  
101 -=== 2.2.3  Example ===
102 -
103 -
104 104  The following takes Helium as a Secondary LoRaWAN server as an example
105 105  
106 106  
86 +=== 2.2.4 Step 1: Download and Install the helium gateway-rs ===
107 107  
108 -=== 2.2.4  Step 1: Download and Install the helium gateway-rs ===
109 -
110 -
111 111  The users is needing to download and install the helium gateway-rs then click the button of Save&Apply
112 112  
113 -
114 114  [[image:image-20220526135049-6.png]]
115 115  
116 116  Download and Install gateway-rs
117 117  
118 118  
95 +=== 2.2.5 Step 2: Back to Semtech UDP page ===
119 119  
120 -=== 2.2.5  Step 2: Back to Semtech UDP page ===
121 -
122 -
123 123  Back to the page of Semtech UDP check the secondary server settings and click the button of Save&Apply
124 124  
125 -
126 126  ​​​​[[image:image-20220526135125-7.png]]
127 127  
128 128  Configuration of helium
129 129  
103 += 3. Gateway Registration for Basics Station =
130 130  
105 +== 3.1 Introduction ==
131 131  
132 -= 3.  Gateway Registration for Basics Station =
133 -
134 -
135 -== 3.1  Introduction ==
136 -
137 -
138 138  (((
139 139  (((
140 140  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/]]
141 -
142 -
143 143  )))
144 144  )))
145 145  
146 146  (((
147 -(% style="color:blue" %)**Below list the support products and Requirements:**
114 +**Below list the support products and Requirements:**
148 148  )))
149 149  
150 150  (((
151 151  (((
152 -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]]
119 + ~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]]
153 153  )))
154 154  
155 155  (((
156 156   2. Firmware version since :[[lgw~~-~~-build-v5.4.1640315898>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/]]
157 -
158 -
159 -
160 -
161 161  )))
162 162  )))
163 163  
164 164  (((
165 -(% style="color:blue" %)**What do you need to prepare**
128 +**What do you need to prepare**
166 166  )))
167 167  
168 168  (((
169 169  (((
170 170  A gateway that can access the internet normally
171 -
172 -
173 -
174 174  )))
175 175  )))
176 176  
177 -== 3.2  Step 1: Add Gateway ==
137 +== 3.2 Step 1. Add Gateway ==
178 178  
179 -
180 180  (((
181 181  (((
182 182  The example for **EU**
... ... @@ -192,129 +192,92 @@
192 192  (((
193 193  (((
194 194  Following picture is the successful added.
195 -
196 -
197 197  )))
198 198  )))
199 199  
200 -[[image:image-20220526135316-8.png]]
157 +[[image:image-20220525094010-2.png]]
201 201  
202 202  Add Gateway
203 203  
161 +== 3.3 Step 2. Create the API key ==
204 204  
205 -
206 -== 3.3  Step 2: Create the API key ==
207 -
208 -
209 209  user need to create the CUPS API key and LNS API key.
210 210  
165 +[[image:image-20220525094115-3.png]]
211 211  
212 -[[image:image-20220526135349-9.png]]
213 -
214 214  Create CUPS API key
215 215  
216 216  
170 +[[image:image-20220525094146-4.png]]
217 217  
218 -[[image:image-20220526135428-10.png]]
219 -
220 220  Create LNS API key
221 221  
222 -
223 223  (% style="color:red" %)**Note : Please copy the API key.**
224 224  
176 +== 3.4 Step 3. Update the gateway setting ==
225 225  
226 -
227 -== 3.4  Step 3: Update the gateway setting ==
228 -
229 -
230 230  In the LoRa Basics Station LNS Authentication Key field, paste the API key you generated in the previous step.
231 231  
180 +[[image:image-20220525094220-5.png]]
232 232  
233 -[[image:image-20220526135528-11.png]]
234 -
235 235  paste the API key
236 236  
184 +== 3.5 Step 4. Access the gateway GUI ==
237 237  
238 -
239 -== 3.5  Step 4: Access the gateway GUI ==
240 -
241 -
242 242  User need to update the API key and install the Certificate
243 243  
188 +[[image:image-20220525094257-6.png]]
244 244  
245 -[[image:image-20220526135601-12.png]]
246 -
247 247  Access the gateway GUI
248 248  
192 +== 3.6 Step 5. Configure Station ==
249 249  
250 -
251 -== 3.6  Step 5: Configure Station ==
252 -
253 -
254 254  User need to input Server URI, Server CUPS Key and LNS Key, as well as install CUPS certificate.
255 255  
196 +**just to clarify.**
256 256  
257 -(% style="color:blue" %)**just to clarify:**
258 -
259 259  (% class="box" %)
260 260  (((
261 - CUPS Server URI  ~-~->  Server Adress
262 - CUPS Authorization Key         ~-~->  Server CUPS API Key
263 - LNS Authorization Key  ~-~->  Server LNS API Key
264 - CUPS certificate  ~-~->  Server CA(user can use the button to install the certificate by default)
200 + CUPS Server URI  ~-~-> Server Adress
201 + CUPS Authorization Key         ~-~-> Server CUPS API Key
202 + LNS Authorization Key  ~-~-> Server LNS API Key
203 + CUPS certificate  ~-~-> Server CA(user can use the button to install the certificate by default)
265 265  )))
266 266  
267 -[[image:image-20220526135654-13.png]]
206 +[[image:image-20220525094329-7.png]]
268 268  
269 269  Congfigure Station
270 270  
210 +== 3.7 Start Station ==
271 271  
272 -
273 -== 3.7  Start Station ==
274 -
275 -
276 276  (((
277 277  When the user has finished the configuration,Please click Sace&Apply to start station to connect The Things Network.
278 -
279 -
280 -
281 281  )))
282 282  
283 -== 3.8  Siccessful Connection ==
216 +== 3.8 Siccessful Connection ==
284 284  
285 -
286 286  If user completes the above steps,which will see live date in the TTN.
287 287  
220 +[[image:image-20220525094409-8.png]]
288 288  
289 -[[image:image-20220526135734-14.png]]
290 -
291 291  Station live date
292 292  
224 +== 3.9 Trouble Shooting ==
293 293  
294 -
295 -== 3.9  Trouble Shooting ==
296 -
297 -
298 298  User can check the station log in the logread/system log page.
299 299  
228 +[[image:image-20220525090622-14.png]]
300 300  
301 -[[image:image-20220526135845-15.png]]
302 -
303 303  Station Log
304 304  
305 -
306 -
307 307  and recode the station log in the system/Recode log page.
308 308  
309 -[[image:image-20220526135940-16.png]]
234 +[[image:image-20220525090705-15.png]]
310 310  
311 311  Recore Log
312 312  
238 += 4. Configure node connection to TTNv3 =
313 313  
314 -
315 -= 4.  Configure node connection to TTNv3 =
316 -
317 -
318 318  (((
319 319  (((
320 320  Following is an example for how to join the TTN v3 LoRaWAN Network.
... ... @@ -330,15 +330,11 @@
330 330  (((
331 331  (((
332 332  We take LES01 as an example.
333 -
334 -
335 -
336 336  )))
337 337  )))
338 338  
339 -== 4.1  Step1 ==
258 +== 4.1 Step1 ==
340 340  
341 -
342 342  (((
343 343  (((
344 344  Create a device in TTN with the OTAA keys from LSE01.
... ... @@ -357,65 +357,44 @@
357 357  )))
358 358  )))
359 359  
360 -[[image:image-20220526140015-17.png]]
278 +[[image:image-20220525090739-16.png]]
361 361  
362 -[[image:image-20220526140044-18.png]]
280 +[[image:image-20220525090833-17.png]]
363 363  
282 +== 4.2 Step2 ==
364 364  
365 -
366 -== 4.2  Step2 ==
367 -
368 -
369 369  (((
370 370  (((
371 371  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.
372 -
373 -
374 374  )))
375 375  )))
376 376  
377 -[[image:image-20220526140132-19.png]]
290 +[[image:image-20220525090920-18.png]]
378 378  
292 +== 4.3 Step3 ==
379 379  
380 -
381 -== 4.3  Step3 ==
382 -
383 -
384 384  Add APP EUI in the application:
385 385  
296 +[[image:image-20220525091022-19.png]]
386 386  
387 -[[image:image-20220526140205-20.png]]
298 +== 4.4 Step4 ==
388 388  
389 -
390 -
391 -== 4.4  Step4 ==
392 -
393 -
394 394  Add APP KEY and DEV EUI:
395 395  
302 +[[image:image-20220525091128-20.png]]
396 396  
397 -[[image:image-20220526140251-21.png]]
304 += 5. TTN V3 integrated into MQTT server =
398 398  
306 +== 5.1 Introduction ==
399 399  
400 -
401 -= 5.  TTN V3 integrated into MQTT server =
402 -
403 -
404 -== 5.1  Introduction ==
405 -
406 -
407 407  (((
408 408  (((
409 409  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.
410 -
411 -
412 -
413 413  )))
414 414  )))
415 415  
416 -== 5.2  Create device steps at MQTT ==
314 +== 5.2 Create device steps at MQTT ==
417 417  
418 -
419 419  (((
420 420  (((
421 421  The user creates a new API KEY after creating a device on TTN V3.
... ... @@ -431,20 +431,16 @@
431 431  (((
432 432  (((
433 433  Fill in Broker Address and Broker port.
434 -
435 -
436 436  )))
437 437  )))
438 438  
439 -[[image:image-20220526140347-22.png]]
334 +[[image:image-20220525091251-22.png]]
440 440  
441 441  Fill in the username and password into MQTT.
442 442  
443 443  
339 +[[image:image-20220525091333-23.png]]
444 444  
445 -[[image:image-20220526140420-23.png]]
446 -
447 -
448 448  The Application Server publishes uplink traffic on the following topics:
449 449  
450 450  (% class="box" %)
... ... @@ -461,18 +461,13 @@
461 461  )))
462 462  
463 463  (((
464 -
465 -
466 466  (((
467 -(% style="color:red" %)**Note**: **Remember that the format of these topics for The Things Stack Open Source would contain {application id} instead of {application id}@{tenant id}.**
468 -
469 -
358 +**Note**: Remember that the format of these topics for The Things Stack Open Source would contain {application id} instead of {application id}@{tenant id}.
470 470  )))
471 471  )))
472 472  
473 -[[image:image-20220526140452-24.png]]
362 +[[image:image-20220525091430-24.png]]
474 474  
475 -
476 476  (((
477 477  (((
478 478  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.
... ... @@ -479,7 +479,7 @@
479 479  )))
480 480  )))
481 481  
482 -[[image:image-20220526140708-25.png]]
370 +[[image:image-20220525091458-25.png]]
483 483  
484 484  (((
485 485  (((
... ... @@ -489,11 +489,7 @@
489 489  
490 490  (((
491 491  (((
492 -
493 -
494 -(% style="color:red" %)**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.**
495 -
496 -
380 +**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.
497 497  )))
498 498  )))
499 499  
... ... @@ -503,27 +503,20 @@
503 503  )))
504 504  )))
505 505  
506 -[[image:image-20220526140856-26.png]]
390 +[[image:image-20220525091618-27.png]]
507 507  
508 508  (((
509 509  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:
510 -
511 -
512 512  )))
513 513  
514 514  (((
515 -(% style="color:red" %)**Note**: **Use this handy tool to convert hexadecimal to base64.**
516 -
517 -
397 +**Note**: Use this handy tool to convert hexadecimal to base64.
518 518  )))
519 519  
520 -[[image:image-20220526140936-27.png]]
400 +[[image:image-20220525091702-28.png]]
521 521  
402 +== 5.3 Send Downlink message ==
522 522  
523 -
524 -== 5.3  Send Downlink message ==
525 -
526 -
527 527  (((
528 528  How to configure downlink in TTN V3?
529 529  )))
... ... @@ -533,40 +533,31 @@
533 533  )))
534 534  
535 535  (((
536 -(% style="color:blue" %)**Downlink command: 01 00 00 5A**
537 -
538 -
413 +Downlink command:01 00 00 5A
539 539  )))
540 540  
541 -[[image:image-20220526141021-28.png]]
416 +[[image:image-20220525091752-29.png]]
542 542  
543 543  downlink
544 544  
545 -
546 -
547 547  After sending, you can view it in live data.
548 548  
549 -[[image:image-20220526141052-29.png]]
422 +[[image:image-20220525091816-30.png]]
550 550  
551 551  downlink
552 552  
553 -
554 -
555 555  (((
556 556  When downlink is successfully sent, the downlink information can be received on the serial port.
557 557  )))
558 558  
559 559  (((
560 -(% style="color:red" %)**Note**:** If the downlink byte sent is longer, the number of bytes will be displayed.**
561 -
562 -
431 +**Note**: If the downlink byte sent is longer, the number of bytes will be displayed.
563 563  )))
564 564  
565 -[[image:image-20220526141116-30.png]]
434 +[[image:image-20220525091855-31.png]]
566 566  
567 567  downlink
568 568  
569 -
570 570  (((
571 571  (((
572 572  If you want to get a successful reply to send downlink in TTN v3. You need to set the response level.
... ... @@ -575,13 +575,13 @@
575 575  
576 576  (((
577 577  (((
578 -If the equipment uses (% style="color:blue" %)**CLASS A**(%%). You can set (% style="color:red" %)**AT+RPL=2** (%%)or send the downlink command: (% style="color:red" %)**2102**
446 +If the equipment uses CLASS A. You can set **AT+RPL=2** or send the downlink command: **2102**
579 579  )))
580 580  )))
581 581  
582 582  (((
583 583  (((
584 -If the equipment uses (% style="color:blue" %)**CLASS C**(%%). You can set** (% style="color:red" %)AT+RPL=4(%%)** or send the downlink command: (% style="color:red" %)**2104**
452 +If the equipment uses CLASS C. You can set** AT+RPL=4** or send the downlink command: **2104**
585 585  )))
586 586  )))
587 587  
... ... @@ -588,20 +588,15 @@
588 588  (((
589 589  (((
590 590  When the device successfully receives the downlink, the server will receive a confirmation packet of 00.
591 -
592 -
593 593  )))
594 594  )))
595 595  
596 -[[image:image-20220526141149-31.png]]
462 +[[image:image-20220525091925-32.png]]
597 597  
598 598  downlink
599 599  
466 += 6. Request Remote Support =
600 600  
601 -
602 -= 6.  Request Remote Support =
603 -
604 -
605 605  (((
606 606  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.
607 607  \\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:**
... ... @@ -613,51 +613,39 @@
613 613  * End Node traffic (from server UI) to shows end node activity in server. (Normally possible)
614 614  * 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)
615 615  
479 +**~1. End Device Join Screen shot, we can check:**
616 616  
617 -(% style="color:blue" %)**1. End Device Join Screen shot, we can check:**
618 -
619 619  * If the device is sending join request to server?
620 620  * What frequency the device is sending?
621 621  
484 +[[image:image-20220525092012-33.png]]
622 622  
623 -[[image:image-20220526141308-33.png]]
624 -
625 625  Console Output from End device to see the transmit frequency
626 626  
488 +User can run **AT+CFG **command to print configuration information.
627 627  
628 -User can run (% style="color:blue" %)**AT+CFG **(%%)command to print configuration information.
490 +* Is the device in OTAA mode or ABP mode? **AT+NJM=1** (OTAA mode), **AT+NJM=0** (ABP mode)
629 629  
630 -* Is the device in OTAA mode or ABP mode? (% style="color:red" %)**AT+NJM=1** (%%)(OTAA mode), (% style="color:red" %)**AT+NJM=0**(%%) (ABP mode)
492 +[[image:image-20220525092043-34.png]]
631 631  
632 -
633 -
634 -[[image:image-20220526141612-36.png]]
635 -
636 -
637 637  Console Output from End device to see the transmit frequency
638 638  
496 +**2. Gateway packet traffic in gateway web or ssh. we can check:**
639 639  
640 -
641 -(% style="color:blue" %)**2. Gateway packet traffic in gateway web or ssh. we can check:**
642 -
643 643  * (((
644 644  If the gateway receive the Join request packet from sensor? (If this fail, check if the gateway and sensor works on the match frequency)
645 645  )))
646 646  * (((
647 647  If the gateway gets the Join Accept message from server and transmit it via LoRa?
648 -
649 -
650 -
651 651  )))
652 652  
653 -[[image:image-20220526141739-37.png]]
505 +[[image:image-20220525092124-35.png]]
654 654  
655 655  Console Output from Gateway to see packets between end node and server.
656 656  
657 657  
510 +**3. Gateway Traffic Page in LoRaWAN Server**
658 658  
659 -(% style="color:blue" %)**3. Gateway Traffic Page in LoRaWAN Server**
660 -
661 661  * (((
662 662  If the Join Request packet arrive the gateway traffic in server? If not, check the internet connection and gateway LoRaWAN server settings.
663 663  )))
... ... @@ -666,32 +666,25 @@
666 666  )))
667 667  * (((
668 668  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.
669 -
670 -
671 -
672 672  )))
673 673  
674 -[[image:image-20220526141823-38.png||height="501" width="1144"]]
522 +[[image:image-20220525092157-36.png]]
675 675  
676 676  The Traffic for the End node in the server, use TTNv3 as example
677 677  
678 678  
527 +[[image:image-20220525092231-37.png]]
679 679  
680 -[[image:image-20220526141917-39.png]]
681 -
682 682  The Traffic for the End node in the server, use TTNv3 as example
683 683  
531 +**4. Data Page in LoRaWAN server**
684 684  
685 -
686 -(% style="color:blue" %)**4. Data Page in LoRaWAN server**
687 -
688 688  (((
689 689  (((
690 690  (((
691 691  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.
692 692  
693 -
694 -[[image:image-20220526141956-40.png]]
538 +[[image:image-20220525092546-1.png]]
695 695  )))
696 696  )))
697 697  )))
... ... @@ -698,8 +698,6 @@
698 698  
699 699  The data for the end device set in server
700 700  
545 +[[image:image-20220525092430-40.png]]
701 701  
702 -
703 -[[image:image-20220526142033-41.png]]
704 -
705 705  Check if OTAA Keys match the keys in device
image-20220526135349-9.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -69.4 KB
Content
image-20220526135428-10.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -68.6 KB
Content
image-20220526135528-11.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -104.4 KB
Content
image-20220526135601-12.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -115.2 KB
Content
image-20220526135654-13.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -123.6 KB
Content
image-20220526135734-14.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -122.5 KB
Content
image-20220526135845-15.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -159.3 KB
Content
image-20220526135940-16.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -32.9 KB
Content
image-20220526140015-17.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -24.4 KB
Content
image-20220526140044-18.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -42.0 KB
Content
image-20220526140132-19.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -60.2 KB
Content
image-20220526140205-20.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -77.6 KB
Content
image-20220526140251-21.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -67.9 KB
Content
image-20220526140347-22.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -63.0 KB
Content
image-20220526140420-23.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -77.4 KB
Content
image-20220526140452-24.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -32.4 KB
Content
image-20220526140708-25.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -827.1 KB
Content
image-20220526140856-26.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -114.9 KB
Content
image-20220526140936-27.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -103.1 KB
Content
image-20220526141021-28.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -74.8 KB
Content
image-20220526141052-29.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -84.1 KB
Content
image-20220526141116-30.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -10.1 KB
Content
image-20220526141149-31.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -59.0 KB
Content
image-20220526141236-32.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -114.0 KB
Content
image-20220526141308-33.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -90.1 KB
Content
image-20220526141350-34.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -78.7 KB
Content
image-20220526141612-36.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -78.2 KB
Content
image-20220526141739-37.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -288.0 KB
Content
image-20220526141823-38.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -197.3 KB
Content
image-20220526141917-39.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -154.2 KB
Content
image-20220526141956-40.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -163.5 KB
Content
image-20220526142033-41.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -25.2 KB
Content

Applications

Navigation

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