Changes for page Notes for TTN

Last modified by Mengting Qiu on 2024/08/20 17:29
<
From version < 66.2 >
edited by Xiaoling
on 2022/05/26 13:51
To version < 99.16 >
edited by Xiaoling
on 2022/07/25 09:18
>
Change comment: There is no comment for this version

Summary

Details

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

Applications

Navigation

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