Changes for page Notes for TTN

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