Changes for page Notes for TTN

Last modified by Mengting Qiu on 2024/08/20 17:29
<
From version < 1.6 >
edited by Xiaoling
on 2022/05/17 09:09
To version < 49.1 >
edited by Xiaoling
on 2022/05/25 09:35
>
Change comment: Uploaded new attachment "image-20220525093504-6.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -35,22 +35,21 @@
35 35  
36 36  == 2.1 Primary LoRaWAN Server ==
37 37  
38 -[[image:https://wiki.dragino.com/images/thumb/0/0c/TTN_v3_Primary_001.png/600px-TTN_v3_Primary_001.png||height="296" width="600"]]
38 +[[image:image-20220525093339-3.png]]
39 39  
40 40  Register Gateway
41 41  
42 42  
43 -[[image:https://wiki.dragino.com/images/thumb/b/ba/TTN_v3_Primary_002.png/600px-TTN_v3_Primary_002.png||height="283" width="600"]]
43 +[[image:image-20220525093402-4.png]]
44 44  
45 45  Put Gateway ID
46 46  
47 47  
48 -[[image:https://wiki.dragino.com/images/thumb/a/a6/TTN_v3_Primary_003.png/600px-TTN_v3_Primary_003.png||height="279" width="600"]]
49 49  
50 50  Choose Frequency Band
51 51  
52 52  
53 -[[image:https://wiki.dragino.com/images/thumb/4/44/TTN_v3_Primary_004.png/600px-TTN_v3_Primary_004.png||height="350" width="600"]]
52 +[[image:image-20220525093308-2.png]]
54 54  
55 55  Show Status
56 56  
... ... @@ -62,9 +62,13 @@
62 62  
63 63  === 2.2.2 Below list the support products and Requirements: ===
64 64  
65 -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]]
64 +(((
65 +~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 +)))
66 66  
67 -1. Firmware version since :[[lgw~~-~~-build-v5.4.1644658774>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LIG16/Firmware/Release/]]
68 +(((
69 +2. Firmware version since :[[lgw~~-~~-build-v5.4.1644658774>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LIG16/Firmware/Release/]]
70 +)))
68 68  
69 69  === 2.2.3 Example ===
70 70  
... ... @@ -74,7 +74,7 @@
74 74  
75 75  The users is needing to download and install the helium gateway-rs then click the button of Save&Apply
76 76  
77 -[[image:https://wiki.dragino.com/images/thumb/f/f8/Helium_Secondary_001.png/600px-Helium_Secondary_001.png||height="350" width="600"]]
80 +[[image:image-20220525085117-5.png]]
78 78  
79 79  Download and Install gateway-rs
80 80  
... ... @@ -82,7 +82,7 @@
82 82  
83 83  Back to the page of Semtech UDP check the secondary server settings and click the button of Save&Apply
84 84  
85 -[[image:https://wiki.dragino.com/images/thumb/c/c8/Helium_Secondary_002.png/600px-Helium_Secondary_002.png||height="415" width="600"]]
88 +[[image:image-20220525085152-6.png]]
86 86  
87 87  Configuration of helium
88 88  
... ... @@ -123,18 +123,24 @@
123 123  == 3.2 Step 1. Add Gateway ==
124 124  
125 125  (((
129 +(((
126 126  The example for **EU**
127 127  )))
132 +)))
128 128  
129 129  (((
135 +(((
130 130  User can add your gateway into The Things Network V3 according to the previous step
131 131  )))
138 +)))
132 132  
133 133  (((
141 +(((
134 134  Following picture is the successful added.
135 135  )))
144 +)))
136 136  
137 -[[image:https://wiki.dragino.com/images/thumb/5/5f/Add_gateway_1.1.png/600px-Add_gateway_1.1.png||height="397" width="600"]]
146 +[[image:image-20220525085231-7.png]]
138 138  
139 139  Add Gateway
140 140  
... ... @@ -142,22 +142,22 @@
142 142  
143 143  user need to create the CUPS API key and LNS API key.
144 144  
145 -[[image:https://wiki.dragino.com/images/thumb/c/c6/Create_cups_api_key.png/600px-Create_cups_api_key.png||height="394" width="600"]]
154 +[[image:image-20220525085329-8.png]]
146 146  
147 147  Create CUPS API key
148 148  
149 149  
150 -[[image:https://wiki.dragino.com/images/thumb/5/55/Create_lns_api_key.png/600px-Create_lns_api_key.png||height="403" width="600"]]
159 +[[image:image-20220525085414-9.png]]
151 151  
152 152  Create LNS API key
153 153  
154 -**Note : Please copy the API key.**
163 +(% style="color:red" %)**Note : Please copy the API key.**
155 155  
156 156  == 3.4 Step 3. Update the gateway setting ==
157 157  
158 158  In the LoRa Basics Station LNS Authentication Key field, paste the API key you generated in the previous step.
159 159  
160 -[[image:https://wiki.dragino.com/images/thumb/2/2f/Paste_the_lns_API_key.png/600px-Paste_the_lns_API_key.png||height="363" width="600"]]
169 +[[image:image-20220525085441-10.png]]
161 161  
162 162  paste the API key
163 163  
... ... @@ -165,7 +165,7 @@
165 165  
166 166  User need to update the API key and install the Certificate
167 167  
168 -[[image:https://wiki.dragino.com/images/thumb/a/a3/Access_gateway_gui_ttnstation.png/600px-Access_gateway_gui_ttnstation.png||height="354" width="600"]]
177 +[[image:image-20220525085522-11.png]]
169 169  
170 170  Access the gateway GUI
171 171  
... ... @@ -175,13 +175,15 @@
175 175  
176 176  **just to clarify.**
177 177  
178 -{{{ CUPS Server URI --> Server Adress
179 - CUPS Authorization Key --> Server CUPS API Key
180 - LNS Authorization Key --> Server LNS API Key
181 - CUPS certificate --> Server CA(user can use the button to install the certificate by default)
182 -}}}
187 +(% class="box" %)
188 +(((
189 + CUPS Server URI  ~-~-> Server Adress
190 + CUPS Authorization Key         ~-~-> Server CUPS API Key
191 + LNS Authorization Key  ~-~-> Server LNS API Key
192 + CUPS certificate  ~-~-> Server CA(user can use the button to install the certificate by default)
193 +)))
183 183  
184 -[[image:https://wiki.dragino.com/images/thumb/8/8c/Confiure_station_cao.png/600px-Confiure_station_cao.png||height="321" width="600"]]
195 +[[image:image-20220525085557-12.png]]
185 185  
186 186  Congfigure Station
187 187  
... ... @@ -195,7 +195,7 @@
195 195  
196 196  If user completes the above steps,which will see live date in the TTN.
197 197  
198 -[[image:https://wiki.dragino.com/images/thumb/4/49/Station_live_date_cao.png/600px-Station_live_date_cao.png||height="391" width="600"]]
209 +[[image:image-20220525085636-13.png]]
199 199  
200 200  Station live date
201 201  
... ... @@ -203,13 +203,13 @@
203 203  
204 204  User can check the station log in the logread/system log page.
205 205  
206 -[[image:https://wiki.dragino.com/images/thumb/7/7c/Station_log_xiao.png/600px-Station_log_xiao.png||height="457" width="600"]]
217 +[[image:image-20220525090622-14.png]]
207 207  
208 208  Station Log
209 209  
210 210  and recode the station log in the system/Recode log page.
211 211  
212 -[[image:https://wiki.dragino.com/images/thumb/5/50/Recore_log_xiao.png/600px-Recore_log_xiao.png||height="147" width="600"]]
223 +[[image:image-20220525090705-15.png]]
213 213  
214 214  Recore Log
215 215  
... ... @@ -216,54 +216,68 @@
216 216  = 4. Configure node connection to TTNv3 =
217 217  
218 218  (((
230 +(((
219 219  Following is an example for how to join the TTN v3 LoRaWAN Network.
220 220  )))
233 +)))
221 221  
222 222  (((
236 +(((
223 223  The gateway is already set up to connect to the TTN network, so we now need to configure the TTNv3 server.
224 224  )))
239 +)))
225 225  
226 226  (((
242 +(((
227 227  We take LES01 as an example.
228 228  )))
245 +)))
229 229  
230 230  == 4.1 Step1 ==
231 231  
232 232  (((
250 +(((
233 233  Create a device in TTN with the OTAA keys from LSE01.
234 234  )))
253 +)))
235 235  
236 236  (((
256 +(((
237 237  Each LSE01 is shipped with a sticker with the default device EUI as below:
238 238  )))
259 +)))
239 239  
240 240  (((
262 +(((
241 241  You can enter this key in the LoRaWAN Server portal. Below is TTN screen shot:
242 242  )))
265 +)))
243 243  
244 -[[image:https://wiki.dragino.com/images/thumb/c/c7/TTNv3--01.png/600px-TTNv3--01.png||alt="TTNv3--01.png" height="277" width="600"]]
267 +[[image:image-20220525090739-16.png]]
245 245  
246 -[[image:https://wiki.dragino.com/images/thumb/1/17/TTNv3--02.png/600px-TTNv3--02.png||alt="TTNv3--02.png" height="226" width="600"]]
269 +[[image:image-20220525090833-17.png]]
247 247  
248 248  == 4.2 Step2 ==
249 249  
250 250  (((
274 +(((
251 251  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.
252 252  )))
277 +)))
253 253  
254 -[[image:https://wiki.dragino.com/images/thumb/f/fc/TTNv3--03.png/600px-TTNv3--03.png||alt="TTNv3--03.png" height="333" width="600"]]
279 +[[image:image-20220525090920-18.png]]
255 255  
256 256  == 4.3 Step3 ==
257 257  
258 258  Add APP EUI in the application:
259 259  
260 -[[image:https://wiki.dragino.com/images/thumb/9/9f/TTNv3--04.png/600px-TTNv3--04.png||alt="TTNv3--04.png" height="439" width="600"]]
285 +[[image:image-20220525091022-19.png]]
261 261  
262 262  == 4.4 Step4 ==
263 263  
264 264  Add APP KEY and DEV EUI:
265 265  
266 -[[image:https://wiki.dragino.com/images/thumb/a/a4/TTNv3--05.png/600px-TTNv3--05.png||alt="TTNv3--05.png" height="500" width="600"]]
291 +[[image:image-20220525091128-20.png]]
267 267  
268 268  = 5. TTN V3 integrated into MQTT server =
269 269  
... ... @@ -270,33 +270,43 @@
270 270  == 5.1 Introduction ==
271 271  
272 272  (((
298 +(((
273 273  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.
274 274  )))
301 +)))
275 275  
276 276  == 5.2 Create device steps at MQTT ==
277 277  
278 278  (((
306 +(((
279 279  The user creates a new API KEY after creating a device on TTN V3.
280 280  )))
309 +)))
281 281  
282 282  (((
312 +(((
283 283  Then copy the password and open MQTT.fx.
284 284  )))
315 +)))
285 285  
286 286  (((
318 +(((
287 287  Fill in Broker Address and Broker port.
288 288  )))
321 +)))
289 289  
290 -[[image:https://wiki.dragino.com/images/thumb/8/82/V3_MQTT1_.png/600px-V3_MQTT1_.png||alt="V3 MQTT1 .png" height="325" width="600"]]
323 +[[image:image-20220525091251-22.png]]
291 291  
292 292  Fill in the username and password into MQTT.
293 293  
294 294  
295 -[[image:https://wiki.dragino.com/images/thumb/6/6a/V3_MQTT2.png/600px-V3_MQTT2.png||alt="V3 MQTT2.png" height="434" width="600"]]
328 +[[image:image-20220525091333-23.png]]
296 296  
297 297  The Application Server publishes uplink traffic on the following topics:
298 298  
299 -{{{ v3/{application id}@{tenant id}/devices/{device id}/join
332 +(% class="box" %)
333 +(((
334 + v3/{application id}@{tenant id}/devices/{device id}/join
300 300   v3/{application id}@{tenant id}/devices/{device id}/up
301 301   v3/{application id}@{tenant id}/devices/{device id}/down/queued
302 302   v3/{application id}@{tenant id}/devices/{device id}/down/sent
... ... @@ -305,33 +305,43 @@
305 305   v3/{application id}@{tenant id}/devices/{device id}/down/failed
306 306   v3/{application id}@{tenant id}/devices/{device id}/service/data
307 307   v3/{application id}@{tenant id}/devices/{device id}/location/solved
308 -}}}
343 +)))
309 309  
310 310  (((
311 -Note: Remember that the format of these topics for The Things Stack Open Source would contain {application id} instead of {application id}@{tenant id}.
346 +(((
347 +**Note**: Remember that the format of these topics for The Things Stack Open Source would contain {application id} instead of {application id}@{tenant id}.
312 312  )))
349 +)))
313 313  
314 -[[image:https://wiki.dragino.com/images/thumb/d/dc/V3_MQTT3.png/600px-V3_MQTT3.png||alt="V3 MQTT3.png" height="400" width="600"]]
351 +[[image:image-20220525091430-24.png]]
315 315  
316 316  (((
354 +(((
317 317  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.
318 318  )))
357 +)))
319 319  
320 -[[image:https://wiki.dragino.com/images/thumb/e/e8/V3_MQTT4.jpg/600px-V3_MQTT4.jpg||alt="V3 MQTT4.jpg" height="326" width="600"]]
359 +[[image:image-20220525091458-25.png]]
321 321  
322 322  (((
362 +(((
323 323  Downlinks can be scheduled by publishing the message to the topic v3/{application id}@{tenant id}/devices/{device id}/down/push.
324 324  )))
365 +)))
325 325  
326 326  (((
327 -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.
368 +(((
369 +**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.
328 328  )))
371 +)))
329 329  
330 330  (((
374 +(((
331 331  Instead of /push, you can also use /replace to replace the downlink queue. Replacing with an empty array clears the downlink queue. Example:
332 332  )))
377 +)))
333 333  
334 -[[image:https://wiki.dragino.com/images/thumb/e/e8/V3_MQTT5.png/600px-V3_MQTT5.png||alt="V3 MQTT5.png" height="289" width="600"]]
379 +[[image:image-20220525091618-27.png]]
335 335  
336 336  (((
337 337  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:
... ... @@ -338,10 +338,10 @@
338 338  )))
339 339  
340 340  (((
341 -Note: Use this handy tool to convert hexadecimal to base64.
386 +**Note**: Use this handy tool to convert hexadecimal to base64.
342 342  )))
343 343  
344 -[[image:https://wiki.dragino.com/images/thumb/9/9f/V3_MQTT6.png/600px-V3_MQTT6.png||alt="V3 MQTT6.png" height="313" width="600"]]
389 +[[image:image-20220525091702-28.png]]
345 345  
346 346  == 5.3 Send Downlink message ==
347 347  
... ... @@ -357,13 +357,13 @@
357 357  Downlink command:01 00 00 5A
358 358  )))
359 359  
360 -[[image:https://wiki.dragino.com/images/thumb/9/90/Downlink_50.png/600px-Downlink_50.png||height="327" width="600"]]
405 +[[image:image-20220525091752-29.png]]
361 361  
362 362  downlink
363 363  
364 364  After sending, you can view it in live data.
365 365  
366 -[[image:https://wiki.dragino.com/images/thumb/1/15/Downlink_51.png/600px-Downlink_51.png||height="141" width="600"]]
411 +[[image:image-20220525091816-30.png]]
367 367  
368 368  downlink
369 369  
... ... @@ -372,30 +372,38 @@
372 372  )))
373 373  
374 374  (((
375 -Note: If the downlink byte sent is longer, the number of bytes will be displayed.
420 +**Note**: If the downlink byte sent is longer, the number of bytes will be displayed.
376 376  )))
377 377  
378 -[[image:https://wiki.dragino.com/images/thumb/c/c9/Downlink_52.png/600px-Downlink_52.png||height="407" width="600"]]
423 +[[image:image-20220525091855-31.png]]
379 379  
380 380  downlink
381 381  
382 382  (((
428 +(((
383 383  If you want to get a successful reply to send downlink in TTN v3. You need to set the response level.
384 384  )))
431 +)))
385 385  
386 386  (((
387 -If the equipment uses CLASS A. You can set AT+RPL=2 or send the downlink command: 2102
434 +(((
435 +If the equipment uses CLASS A. You can set **AT+RPL=2** or send the downlink command: **2102**
388 388  )))
437 +)))
389 389  
390 390  (((
391 -If the equipment uses CLASS C. You can set AT+RPL=4 or send the downlink command: 2104
440 +(((
441 +If the equipment uses CLASS C. You can set** AT+RPL=4** or send the downlink command: **2104**
392 392  )))
443 +)))
393 393  
394 394  (((
446 +(((
395 395  When the device successfully receives the downlink, the server will receive a confirmation packet of 00.
396 396  )))
449 +)))
397 397  
398 -[[image:https://wiki.dragino.com/images/thumb/d/d9/Downlink_54.png/600px-Downlink_54.png||height="127" width="600"]]
451 +[[image:image-20220525091925-32.png]]
399 399  
400 400  downlink
401 401  
... ... @@ -403,7 +403,7 @@
403 403  
404 404  (((
405 405  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.
406 -\\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]] 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:
459 +\\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:**
407 407  )))
408 408  
409 409  * End node is connected to serial port to show the Join frequency and DR. (If possible)
... ... @@ -412,30 +412,33 @@
412 412  * End Node traffic (from server UI) to shows end node activity in server. (Normally possible)
413 413  * 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)
414 414  
415 -
416 416  **~1. End Device Join Screen shot, we can check:**
417 417  
418 418  * If the device is sending join request to server?
419 419  * What frequency the device is sending?
420 420  
421 -[[image:https://wiki.dragino.com/images/thumb/7/77/LoRaWAN_Communication_Debug1.png/600px-LoRaWAN_Communication_Debug1.png||height="596" width="600"]]
473 +[[image:image-20220525092012-33.png]]
422 422  
423 423  Console Output from End device to see the transmit frequency
424 424  
425 -User can run AT+CFG command to print configuration information.
477 +User can run **AT+CFG **command to print configuration information.
426 426  
427 -* Is the device in OTAA mode or ABP mode? AT+NJM=1 (OTAA mode), AT+NJM=0 (ABP mode)
479 +* Is the device in OTAA mode or ABP mode? **AT+NJM=1** (OTAA mode), **AT+NJM=0** (ABP mode)
428 428  
429 -[[image:https://wiki.dragino.com/images/thumb/c/c5/LoRaWAN_Communication_Debug23.png/600px-LoRaWAN_Communication_Debug23.png||height="514" width="600"]]
481 +[[image:image-20220525092043-34.png]]
430 430  
431 431  Console Output from End device to see the transmit frequency
432 432  
433 433  **2. Gateway packet traffic in gateway web or ssh. we can check:**
434 434  
435 -* If the gateway receive the Join request packet from sensor? (If this fail, check if the gateway and sensor works on the match frequency)
436 -* If the gateway gets the Join Accept message from server and transmit it via LoRa?
487 +* (((
488 +If the gateway receive the Join request packet from sensor? (If this fail, check if the gateway and sensor works on the match frequency)
489 +)))
490 +* (((
491 +If the gateway gets the Join Accept message from server and transmit it via LoRa?
492 +)))
437 437  
438 -[[image:https://wiki.dragino.com/images/thumb/1/1c/OTAA_Join-2.png/600px-OTAA_Join-2.png||height="325" width="600"]]
494 +[[image:image-20220525092124-35.png]]
439 439  
440 440  Console Output from Gateway to see packets between end node and server.
441 441  
... ... @@ -442,29 +442,39 @@
442 442  
443 443  **3. Gateway Traffic Page in LoRaWAN Server**
444 444  
445 -* If the Join Request packet arrive the gateway traffic in server? If not, check the internet connection and gateway LoRaWAN server settings.
446 -* If the server send back a Join Accept for the Join Request? if not, check if the keys from the device match the keys you put in the server, or try to choose a different server route for this end device.
447 -* 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.
501 +* (((
502 +If the Join Request packet arrive the gateway traffic in server? If not, check the internet connection and gateway LoRaWAN server settings.
503 +)))
504 +* (((
505 +If the server send back a Join Accept for the Join Request? if not, check if the keys from the device match the keys you put in the server, or try to choose a different server route for this end device.
506 +)))
507 +* (((
508 +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.
509 +)))
448 448  
449 -[[image:https://wiki.dragino.com/images/thumb/d/da/LoRaWAN_Communication_Debug22.png/600px-LoRaWAN_Communication_Debug22.png||height="268" width="600"]]
511 +[[image:image-20220525092157-36.png]]
450 450  
451 451  The Traffic for the End node in the server, use TTNv3 as example
452 452  
453 453  
454 -[[image:https://wiki.dragino.com/images/thumb/4/4b/LoRaWAN_Communication_Debug3.png/600px-LoRaWAN_Communication_Debug3.png||height="281" width="600"]]
516 +[[image:image-20220525092231-37.png]]
455 455  
456 456  The Traffic for the End node in the server, use TTNv3 as example
457 457  
458 458  **4. Data Page in LoRaWAN server**
459 459  
460 -* (((
522 +(((
523 +(((
524 +(((
461 461  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.
526 +
527 +[[image:image-20220525092546-1.png]]
462 462  )))
529 +)))
530 +)))
463 463  
464 -[[image:https://wiki.dragino.com/images/thumb/9/99/LoRaWAN_Communication_Debug4.png/600px-LoRaWAN_Communication_Debug4.png||height="222" width="600"]]
465 -
466 466  The data for the end device set in server
467 467  
468 -[[image:https://wiki.dragino.com/images/thumb/6/69/LoRaWAN_Communication_Debug5.png/600px-LoRaWAN_Communication_Debug5.png||height="279" width="600"]]
534 +[[image:image-20220525092430-40.png]]
469 469  
470 470  Check if OTAA Keys match the keys in device
image-20220525084853-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +29.3 KB
Content
image-20220525084923-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +55.5 KB
Content
image-20220525085016-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +41.5 KB
Content
image-20220525085054-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +56.1 KB
Content
image-20220525085117-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +61.3 KB
Content
image-20220525085152-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +72.4 KB
Content
image-20220525085231-7.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +50.6 KB
Content
image-20220525085329-8.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +39.7 KB
Content
image-20220525085414-9.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +42.6 KB
Content
image-20220525085441-10.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +45.7 KB
Content
image-20220525085522-11.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +77.0 KB
Content
image-20220525085557-12.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +84.9 KB
Content
image-20220525085636-13.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +72.8 KB
Content
image-20220525090622-14.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +190.9 KB
Content
image-20220525090705-15.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +37.0 KB
Content
image-20220525090739-16.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +21.4 KB
Content
image-20220525090833-17.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +41.9 KB
Content
image-20220525090920-18.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +71.4 KB
Content
image-20220525091022-19.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +90.8 KB
Content
image-20220525091128-20.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +78.0 KB
Content
image-20220525091218-21.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +77.5 KB
Content
image-20220525091251-22.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +75.2 KB
Content
image-20220525091333-23.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +78.4 KB
Content
image-20220525091430-24.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +33.1 KB
Content
image-20220525091458-25.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +319.9 KB
Content
image-20220525091543-26.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +319.9 KB
Content
image-20220525091618-27.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +60.8 KB
Content
image-20220525091702-28.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +140.3 KB
Content
image-20220525091752-29.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +64.0 KB
Content
image-20220525091816-30.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +76.3 KB
Content
image-20220525091855-31.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +10.3 KB
Content
image-20220525091925-32.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +54.8 KB
Content
image-20220525092012-33.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +115.4 KB
Content
image-20220525092043-34.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +125.4 KB
Content
image-20220525092124-35.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +393.2 KB
Content
image-20220525092157-36.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +143.7 KB
Content
image-20220525092231-37.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +131.1 KB
Content
image-20220525092430-40.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +13.9 KB
Content
image-20220525092546-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +117.3 KB
Content
image-20220525092849-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +85.0 KB
Content
image-20220525092915-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +43.8 KB
Content
image-20220525092954-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +64.5 KB
Content
image-20220525093256-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +86.5 KB
Content
image-20220525093308-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +86.5 KB
Content
image-20220525093339-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +43.8 KB
Content
image-20220525093402-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +84.9 KB
Content
image-20220525093504-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +64.5 KB
Content

Applications

Navigation

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