Last modified by Xiaoling on 2023/04/20 18:14
<
From version < 18.1 >
edited by Xiaoling
on 2022/07/22 11:52
To version < 19.2 >
edited by Xiaoling
on 2022/09/17 16:42
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -12,6 +12,8 @@
12 12  * No internet connection.
13 13  * User wants to get data forward in gateway and forward to their server base on MQTT/HTTP, etc. (Combine ABP communication method and [[MQTT forward together>>MQTT Forward Instruction]]).
14 14  
15 +
16 +
15 15  (((
16 16  The basic of this feature is the decoding of (% style="color:red" %)**LoRaWAN ABP End Node**(%%). Requirements:
17 17  )))
... ... @@ -22,6 +22,7 @@
22 22  
23 23  
24 24  
27 +
25 25  = 2. How it works =
26 26  
27 27  
... ... @@ -45,11 +45,14 @@
45 45  
46 46  We need to input above keys in LG308 and enable ABP decryption.
47 47  
51 +
48 48  [[image:image-20220527161119-1.png]]
49 49  
54 +
50 50  Input the ABP keys in LG308
51 51  
52 52  
58 +
53 53  == 2.1 Upstream ==
54 54  
55 55  
... ... @@ -56,14 +56,18 @@
56 56  Now when this End Node (Dev Addr=2602111D) send a uplink packet. When this packet arrive LG308, LG308 will decode it and put the decode data on the file /var/iot/channels/2602111D . So we have this data for further process with other applications in LG308.
57 57  
58 58  (((
59 -We can see the log of LG308 to know this packet arrive
65 +We can see the log of LG308 to know this packet arrive.
66 +
67 +
60 60  )))
61 61  
62 62  [[image:image-20220527161149-2.png]]
63 63  
72 +
64 64  LG308 log by "(% style="color:red" %)**logread -f**" (%%)command
65 65  
66 66  
76 +
67 67  The data of End Node is stored in the file /var/iot/channels/2602111D. We can use hexdump command to check it.
68 68  
69 69  (% class="box" %)
... ... @@ -90,6 +90,7 @@
90 90  000001c
91 91  )))
92 92  
103 +
93 93  (% class="box" %)
94 94  (((
95 95  (% style="color:red" %)**Notice 2**(%%): The upstream payload length should match the LoRaWAN length requirement (max length depends on Frequency and DR), otherwise the gateway can't decode the payload.
... ... @@ -96,6 +96,7 @@
96 96  )))
97 97  
98 98  
110 +
99 99  === 2.2.1 Decode Method ===
100 100  
101 101  
... ... @@ -175,6 +175,7 @@
175 175  
176 176  (% style="color:#037691" %)**dev_addr,imme/time,txt/hex,payload**
177 177  
190 +
178 178  Since fimware > Dragino-v2 lgw-5.4.1608518541 . Support more option
179 179  
180 180  (% style="color:#037691" %)**dev_addr,imme/time,txt/hex,payload,txpw,txbw,SF,frequency,rxwindow**
... ... @@ -199,7 +199,6 @@
199 199  
200 200  
201 201  
202 -
203 203  (% style="color:blue" %)**Completely exmaple:**
204 204  
205 205  * **Old version:** echo 018193F4,imme,hex,0101 > /var/iot/push/test
... ... @@ -207,9 +207,8 @@
207 207  
208 208  
209 209  
222 +(% style="color:#037691" %)**Downstream Frequency:**
210 210  
211 -(% style="color:#037691" %)**Downstream Frequency**
212 -
213 213  The LG308 will use the RX2 window info to send the downstream payload, use the default LoRaWAN settings, as below:
214 214  
215 215  * EU868: 869.525Mhz, DR0(SF12BW125)
... ... @@ -223,7 +223,6 @@
223 223  
224 224  
225 225  
226 -
227 227  (% style="color:#037691" %)**Examples:**
228 228  
229 229  (% class="box" %)
... ... @@ -272,6 +272,7 @@
272 272  )))
273 273  
274 274  
285 +
275 275  = 3. Example 1: Communicate with LT-22222-L =
276 276  
277 277  
... ... @@ -316,37 +316,45 @@
316 316  )))
317 317  
318 318  
319 -**~1. Input keys**
330 +(% style="color:blue" %)**1. Input keys**
320 320  
332 +
321 321  [[image:image-20220527162450-3.png]]
322 322  
323 323  Input Keys in LPS8
324 324  
325 325  
326 -**2. Make sure the LPS8 and LT use the same frequency bands, choose EU868 in this test.**
327 327  
339 +(% style="color:blue" %)**2. Make sure the LPS8 and LT use the same frequency bands, choose EU868 in this test.**
328 328  
329 -**3. Choose Built-in server**
330 330  
342 +(% style="color:blue" %)**3. Choose Built-in server**
343 +
344 +
331 331  [[image:image-20220527162518-4.png]]
332 332  
333 333  Choose Built-in server
334 334  
335 335  
336 -**4. Run the script.**
337 337  
338 -[[image:image-20220527162552-5.png]]
351 +(% style="color:blue" %)**4. Run the script.**
339 339  
353 +
354 +[[image:image-20220722115213-2.png]]
355 +
340 340  Run the script
341 341  
342 342  
343 -**5. Output:**
344 344  
345 -[[image:image-20220527162619-6.png]]
360 +(% style="color:blue" %)**5. Output:**
346 346  
362 +
363 +[[image:image-20220722115133-1.png]]
364 +
347 347  Output from LPS8
348 348  
349 349  
368 +
350 350  = 4. Example 2: Communicate to TCP Server =
351 351  
352 352  
... ... @@ -372,8 +372,9 @@
372 372  
373 373  
374 374  
375 -**run socket tool in PC**
394 +(% style="color:blue" %)**run socket tool in PC**
376 376  
396 +
377 377  [[image:image-20220527163028-9.png]]
378 378  
379 379  
... ... @@ -381,8 +381,9 @@
381 381  
382 382  
383 383  
384 -**Input Server address and port**
404 +(% style="color:blue" %)**Input Server address and port**
385 385  
406 +
386 386  [[image:image-20220527163106-10.png]]
387 387  
388 388  Input Server address and port
... ... @@ -389,8 +389,9 @@
389 389  
390 390  
391 391  
392 -**See value receive in socket tool:**
413 +(% style="color:blue" %)**See value receive in socket tool:**
393 393  
415 +
394 394  [[image:image-20220527163144-11.png]]
395 395  
396 396  value receive in socket tool

Applications

Navigation

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