Changes for page Notes for TTN

Last modified by Mengting Qiu on 2024/08/20 17:29
<
From version < 74.2 >
edited by Xiaoling
on 2022/05/26 13:59
To version < 99.28 >
edited by Xiaoling
on 2022/07/25 09:33
>
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,105 +28,133 @@
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  
88 -The users is needing to download and install the helium gateway-rs then click the button of Save&Apply
108 +=== 2.2.4  Step 1: Download and Install the helium gateway-rs ===
89 89  
110 +
111 +The users is needing to download and install the helium gateway-rs then click the button of (% style="color:blue" %)**Save&Apply.**
112 +
113 +
90 90  [[image:image-20220526135049-6.png]]
91 91  
92 92  Download and Install gateway-rs
93 93  
94 94  
95 -=== 2.2.5 Step 2: Back to Semtech UDP page ===
96 96  
97 -Back to the page of Semtech UDP check the secondary server settings and click the button of Save&Apply
120 +=== 2.2.5  Step 2: Back to Semtech UDP page ===
98 98  
122 +
123 +Back to the page of Semtech UDP check the secondary server settings and click the button of (% style="color:blue" %)**Save&Apply.**
124 +
125 +
99 99  ​​​​[[image:image-20220526135125-7.png]]
100 100  
101 101  Configuration of helium
102 102  
103 103  
104 -= 3. Gateway Registration for Basics Station =
105 105  
106 -== 3.1 Introduction ==
132 += 3.  Gateway Registration for Basics Station =
107 107  
134 +
135 +== 3.1  Introduction ==
136 +
137 +
108 108  (((
109 109  (((
110 110  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 +
111 111  )))
112 112  )))
113 113  
114 114  (((
115 -**Below list the support products and Requirements:**
147 +(% style="color:blue" %)**Below list the support products and Requirements:**
116 116  )))
117 117  
118 118  (((
119 119  (((
120 - ~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]]
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]]
121 121  )))
122 122  
123 123  (((
124 - 2. Firmware version since :[[lgw~~-~~-build-v5.4.1640315898>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/]]
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 +
125 125  )))
126 126  )))
127 127  
128 128  (((
129 -**What do you need to prepare**
163 +(% style="color:blue" %)**What do you need to prepare**
130 130  )))
131 131  
132 132  (((
... ... @@ -133,15 +133,17 @@
133 133  (((
134 134  A gateway that can access the internet normally
135 135  
170 +
136 136  
137 137  )))
138 138  )))
139 139  
140 -== 3.2 Step 1. Add Gateway ==
175 +== 3.2  Step 1: Add Gateway ==
141 141  
177 +
142 142  (((
143 143  (((
144 -The example for **EU**
180 +(% style="color:blue" %)**The example for**(%%)** (% style="color:red" %)EU:(%%)**
145 145  )))
146 146  )))
147 147  
... ... @@ -154,6 +154,8 @@
154 154  (((
155 155  (((
156 156  Following picture is the successful added.
193 +
194 +
157 157  )))
158 158  )))
159 159  
... ... @@ -162,52 +162,66 @@
162 162  Add Gateway
163 163  
164 164  
165 -== 3.3 Step 2. Create the API key ==
166 166  
204 +== 3.3  Step 2: Create the API key ==
205 +
206 +
167 167  user need to create the CUPS API key and LNS API key.
168 168  
209 +
169 169  [[image:image-20220526135349-9.png]]
170 170  
171 171  Create CUPS API key
172 172  
173 173  
215 +
174 174  [[image:image-20220526135428-10.png]]
175 175  
176 176  Create LNS API key
177 177  
220 +
178 178  (% style="color:red" %)**Note : Please copy the API key.**
179 179  
180 180  
181 -== 3.4 Step 3. Update the gateway setting ==
182 182  
225 +== 3.4  Step 3: Update the gateway setting ==
226 +
227 +
183 183  In the LoRa Basics Station LNS Authentication Key field, paste the API key you generated in the previous step.
184 184  
230 +
185 185  [[image:image-20220526135528-11.png]]
186 186  
187 187  paste the API key
188 188  
189 189  
190 -== 3.5 Step 4. Access the gateway GUI ==
191 191  
237 +== 3.5  Step 4: Access the gateway GUI ==
238 +
239 +
192 192  User need to update the API key and install the Certificate
193 193  
242 +
194 194  [[image:image-20220526135601-12.png]]
195 195  
196 196  Access the gateway GUI
197 197  
198 198  
199 -== 3.6 Step 5. Configure Station ==
200 200  
249 +== 3.6  Step 5: Configure Station ==
250 +
251 +
201 201  User need to input Server URI, Server CUPS Key and LNS Key, as well as install CUPS certificate.
202 202  
203 -**just to clarify.**
204 204  
255 +(% style="color:blue" %)**just to clarify:**
256 +
205 205  (% class="box" %)
206 206  (((
207 - CUPS Server URI  ~-~-> Server Adress
208 - CUPS Authorization Key         ~-~-> Server CUPS API Key
209 - LNS Authorization Key  ~-~-> Server LNS API Key
210 - 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)
211 211  )))
212 212  
213 213  [[image:image-20220526135654-13.png]]
... ... @@ -215,39 +215,52 @@
215 215  Congfigure Station
216 216  
217 217  
218 -== 3.7 Start Station ==
219 219  
271 +== 3.7  Start Station ==
272 +
273 +
220 220  (((
221 221  When the user has finished the configuration,Please click Sace&Apply to start station to connect The Things Network.
222 222  
277 +
223 223  
224 224  )))
225 225  
226 -== 3.8 Siccessful Connection ==
281 +== 3.8  Siccessful Connection ==
227 227  
283 +
228 228  If user completes the above steps,which will see live date in the TTN.
229 229  
286 +
230 230  [[image:image-20220526135734-14.png]]
231 231  
232 232  Station live date
233 233  
234 234  
235 -== 3.9 Trouble Shooting ==
236 236  
237 -User can check the station log in the logread/system log page.
293 +== 3.9  Trouble Shooting ==
238 238  
295 +
296 +User can check the station log in the** (% style="color:blue" %)LogRead ~-~-> System Log (%%)**page.
297 +
298 +
239 239  [[image:image-20220526135845-15.png]]
240 240  
241 241  Station Log
242 242  
243 -and recode the station log in the system/Recode log page.
244 244  
245 -[[image:image-20220525090705-15.png]]
246 246  
305 +and recode the station log in the** (% style="color:blue" %)LogRead  ~-~->  Recode Log(%%)** page.
306 +
307 +[[image:image-20220526135940-16.png]]
308 +
247 247  Recore Log
248 248  
249 -= 4. Configure node connection to TTNv3 =
250 250  
312 +
313 += 4.  Configure node connection to TTNv3 =
314 +
315 +
251 251  (((
252 252  (((
253 253  Following is an example for how to join the TTN v3 LoRaWAN Network.
... ... @@ -262,12 +262,16 @@
262 262  
263 263  (((
264 264  (((
265 -We take LES01 as an example.
330 +(% style="color:#037691" %)We take LES01 as an example.
331 +
332 +
333 +
266 266  )))
267 267  )))
268 268  
269 -== 4.1 Step1 ==
337 +== 4.1  Step1 ==
270 270  
339 +
271 271  (((
272 272  (((
273 273  Create a device in TTN with the OTAA keys from LSE01.
... ... @@ -286,44 +286,65 @@
286 286  )))
287 287  )))
288 288  
289 -[[image:image-20220525090739-16.png]]
358 +[[image:image-20220526140015-17.png]]
290 290  
291 -[[image:image-20220525090833-17.png]]
360 +[[image:image-20220526140044-18.png]]
292 292  
293 -== 4.2 Step2 ==
294 294  
363 +
364 +== 4.2  Step2 ==
365 +
366 +
295 295  (((
296 296  (((
297 297  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 +
298 298  )))
299 299  )))
300 300  
301 -[[image:image-20220525090920-18.png]]
375 +[[image:image-20220526140132-19.png]]
302 302  
303 -== 4.3 Step3 ==
304 304  
378 +
379 +== 4.3  Step3 ==
380 +
381 +
305 305  Add APP EUI in the application:
306 306  
307 -[[image:image-20220525091022-19.png]]
308 308  
309 -== 4.4 Step4 ==
385 +[[image:image-20220526140205-20.png]]
310 310  
387 +
388 +
389 +== 4.4  Step4 ==
390 +
391 +
311 311  Add APP KEY and DEV EUI:
312 312  
313 -[[image:image-20220525091128-20.png]]
314 314  
315 -= 5. TTN V3 integrated into MQTT server =
395 +[[image:image-20220526140251-21.png]]
316 316  
317 -== 5.1 Introduction ==
318 318  
398 +
399 += 5.  TTN V3 integrated into MQTT server =
400 +
401 +
402 +== 5.1  Introduction ==
403 +
404 +
319 319  (((
320 320  (((
321 321  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 +
322 322  )))
323 323  )))
324 324  
325 -== 5.2 Create device steps at MQTT ==
414 +== 5.2  Create device steps at MQTT ==
326 326  
416 +
327 327  (((
328 328  (((
329 329  The user creates a new API KEY after creating a device on TTN V3.
... ... @@ -339,16 +339,20 @@
339 339  (((
340 340  (((
341 341  Fill in Broker Address and Broker port.
432 +
433 +
342 342  )))
343 343  )))
344 344  
345 -[[image:image-20220525091251-22.png]]
437 +[[image:image-20220526140347-22.png]]
346 346  
347 347  Fill in the username and password into MQTT.
348 348  
349 349  
350 -[[image:image-20220525091333-23.png]]
351 351  
443 +[[image:image-20220526140420-23.png]]
444 +
445 +
352 352  The Application Server publishes uplink traffic on the following topics:
353 353  
354 354  (% class="box" %)
... ... @@ -365,13 +365,18 @@
365 365  )))
366 366  
367 367  (((
462 +
463 +
368 368  (((
369 -**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 +
370 370  )))
371 371  )))
372 372  
373 -[[image:image-20220525091430-24.png]]
471 +[[image:image-20220526140452-24.png]]
374 374  
473 +
375 375  (((
376 376  (((
377 377  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.
... ... @@ -378,7 +378,7 @@
378 378  )))
379 379  )))
380 380  
381 -[[image:image-20220525091458-25.png]]
480 +[[image:image-20220526140708-25.png]]
382 382  
383 383  (((
384 384  (((
... ... @@ -388,7 +388,11 @@
388 388  
389 389  (((
390 390  (((
391 -**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 +
392 392  )))
393 393  )))
394 394  
... ... @@ -398,20 +398,27 @@
398 398  )))
399 399  )))
400 400  
401 -[[image:image-20220525091618-27.png]]
504 +[[image:image-20220526140856-26.png]]
402 402  
403 403  (((
404 404  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 +
405 405  )))
406 406  
407 407  (((
408 -**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 +
409 409  )))
410 410  
411 -[[image:image-20220525091702-28.png]]
518 +[[image:image-20220526140936-27.png]]
412 412  
413 -== 5.3 Send Downlink message ==
414 414  
521 +
522 +== 5.3  Send Downlink message ==
523 +
524 +
415 415  (((
416 416  How to configure downlink in TTN V3?
417 417  )))
... ... @@ -421,31 +421,40 @@
421 421  )))
422 422  
423 423  (((
424 -Downlink command:01 00 00 5A
534 +(% style="color:blue" %)**Downlink command: 01 00 00 5A**
535 +
536 +
425 425  )))
426 426  
427 -[[image:image-20220525091752-29.png]]
539 +[[image:image-20220526141021-28.png]]
428 428  
429 429  downlink
430 430  
543 +
544 +
431 431  After sending, you can view it in live data.
432 432  
433 -[[image:image-20220525091816-30.png]]
547 +[[image:image-20220526141052-29.png]]
434 434  
435 435  downlink
436 436  
551 +
552 +
437 437  (((
438 438  When downlink is successfully sent, the downlink information can be received on the serial port.
439 439  )))
440 440  
441 441  (((
442 -**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 +
443 443  )))
444 444  
445 -[[image:image-20220525091855-31.png]]
563 +[[image:image-20220526141116-30.png]]
446 446  
447 447  downlink
448 448  
567 +
449 449  (((
450 450  (((
451 451  If you want to get a successful reply to send downlink in TTN v3. You need to set the response level.
... ... @@ -454,13 +454,13 @@
454 454  
455 455  (((
456 456  (((
457 -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**
458 458  )))
459 459  )))
460 460  
461 461  (((
462 462  (((
463 -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**
464 464  )))
465 465  )))
466 466  
... ... @@ -467,15 +467,20 @@
467 467  (((
468 468  (((
469 469  When the device successfully receives the downlink, the server will receive a confirmation packet of 00.
589 +
590 +
470 470  )))
471 471  )))
472 472  
473 -[[image:image-20220525091925-32.png]]
594 +[[image:image-20220526141149-31.png]]
474 474  
475 475  downlink
476 476  
477 -= 6. Request Remote Support =
478 478  
599 +
600 += 6.  Request Remote Support =
601 +
602 +
479 479  (((
480 480  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.
481 481  \\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:**
... ... @@ -487,39 +487,47 @@
487 487  * End Node traffic (from server UI) to shows end node activity in server. (Normally possible)
488 488  * 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)
489 489  
490 -**~1. End Device Join Screen shot, we can check:**
614 +(% style="color:blue" %)**1. End Device Join Screen shot, we can check:**
491 491  
492 492  * If the device is sending join request to server?
493 493  * What frequency the device is sending?
494 494  
495 -[[image:image-20220525092012-33.png]]
619 +[[image:image-20220526141308-33.png]]
496 496  
497 497  Console Output from End device to see the transmit frequency
498 498  
499 -User can run **AT+CFG **command to print configuration information.
500 500  
501 -* Is the device in OTAA mode or ABP mode? **AT+NJM=1** (OTAA mode), **AT+NJM=0** (ABP mode)
624 +User can run (% style="color:blue" %)**AT+CFG **(%%)command to print configuration information.
502 502  
503 -[[image:image-20220525092043-34.png]]
626 +* 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)
504 504  
628 +[[image:image-20220526141612-36.png]]
629 +
630 +
505 505  Console Output from End device to see the transmit frequency
506 506  
507 -**2. Gateway packet traffic in gateway web or ssh. we can check:**
508 508  
634 +
635 +(% style="color:blue" %)**2. Gateway packet traffic in gateway web or ssh. we can check:**
636 +
509 509  * (((
510 510  If the gateway receive the Join request packet from sensor? (If this fail, check if the gateway and sensor works on the match frequency)
511 511  )))
512 512  * (((
513 513  If the gateway gets the Join Accept message from server and transmit it via LoRa?
642 +
643 +
644 +
514 514  )))
515 515  
516 -[[image:image-20220525092124-35.png]]
647 +[[image:image-20220526141739-37.png]]
517 517  
518 518  Console Output from Gateway to see packets between end node and server.
519 519  
520 520  
521 -**3. Gateway Traffic Page in LoRaWAN Server**
522 522  
653 +(% style="color:blue" %)**3. Gateway Traffic Page in LoRaWAN Server**
654 +
523 523  * (((
524 524  If the Join Request packet arrive the gateway traffic in server? If not, check the internet connection and gateway LoRaWAN server settings.
525 525  )))
... ... @@ -528,25 +528,32 @@
528 528  )))
529 529  * (((
530 530  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.
663 +
664 +
665 +
531 531  )))
532 532  
533 -[[image:image-20220525092157-36.png]]
668 +[[image:image-20220526141823-38.png||height="501" width="1144"]]
534 534  
535 535  The Traffic for the End node in the server, use TTNv3 as example
536 536  
537 537  
538 -[[image:image-20220525092231-37.png]]
539 539  
674 +[[image:image-20220526141917-39.png]]
675 +
540 540  The Traffic for the End node in the server, use TTNv3 as example
541 541  
542 -**4. Data Page in LoRaWAN server**
543 543  
679 +
680 +(% style="color:blue" %)**4. Data Page in LoRaWAN server**
681 +
544 544  (((
545 545  (((
546 546  (((
547 547  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.
548 548  
549 -[[image:image-20220525092546-1.png]]
687 +
688 +[[image:image-20220526141956-40.png]]
550 550  )))
551 551  )))
552 552  )))
... ... @@ -553,6 +553,8 @@
553 553  
554 554  The data for the end device set in server
555 555  
556 -[[image:image-20220525092430-40.png]]
557 557  
696 +
697 +[[image:image-20220526142033-41.png]]
698 +
558 558  Check if OTAA Keys match the keys in device
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