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

Summary

Details

Page properties
Content
... ... @@ -12,8 +12,6 @@
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 -
17 17  (((
18 18  The basic of this feature is the decoding of (% style="color:red" %)**LoRaWAN ABP End Node**(%%). Requirements:
19 19  )))
... ... @@ -48,14 +48,11 @@
48 48  
49 49  We need to input above keys in LG308 and enable ABP decryption.
50 50  
51 -
52 52  [[image:image-20220527161119-1.png]]
53 53  
54 -
55 55  Input the ABP keys in LG308
56 56  
57 57  
58 -
59 59  == 2.1 Upstream ==
60 60  
61 61  
... ... @@ -62,18 +62,14 @@
62 62  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.
63 63  
64 64  (((
65 -We can see the log of LG308 to know this packet arrive.
66 -
67 -
60 +We can see the log of LG308 to know this packet arrive
68 68  )))
69 69  
70 70  [[image:image-20220527161149-2.png]]
71 71  
72 -
73 73  LG308 log by "(% style="color:red" %)**logread -f**" (%%)command
74 74  
75 75  
76 -
77 77  The data of End Node is stored in the file /var/iot/channels/2602111D. We can use hexdump command to check it.
78 78  
79 79  (% class="box" %)
... ... @@ -88,8 +88,6 @@
88 88  * **SNR**: 3030 3030 3030 3546 = 0x0000 005F = 95, need to divide 10 so SNR is 9.5
89 89  * **Payload**: 0xcc0c 0b63 0266 017f ff7f ff00
90 90  
91 -
92 -
93 93  (% class="box" %)
94 94  (((
95 95  (% style="color:red" %)**Notice 1**(%%): The data file stored in LG308 for the end node is bin file. If the end node sends ASCII string to gateway, the output will as below:
... ... @@ -100,7 +100,6 @@
100 100  000001c
101 101  )))
102 102  
103 -
104 104  (% class="box" %)
105 105  (((
106 106  (% 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.
... ... @@ -107,7 +107,6 @@
107 107  )))
108 108  
109 109  
110 -
111 111  === 2.2.1 Decode Method ===
112 112  
113 113  
... ... @@ -151,23 +151,19 @@
151 151  === 2.2.2 How to Decode My End Node ===
152 152  
153 153  
154 -**1.** Configure the ABP keys for your end node in the gateway. enable ABP decode in Web UI
141 +1/ Configure the ABP keys for your end node in the gateway. enable ABP decode in Web UI
155 155  
156 -**2. **Don't choose MQTT service, use LoRaWAN.
143 +2/ Don't choose MQTT service, use LoRaWAN.
157 157  
158 -**3.** When your end node send a message to the gateway, there will be a file store in /var/iot/channels. full path should be /var/iot/channels/END_NODE_DEV_ADDR
145 +3/ When your end node send a message to the gateway, there will be a file store in /var/iot/channels. full path should be /var/iot/channels/END_NODE_DEV_ADDR
159 159  
160 -**4.** Use the /etc/lora/decoder/Dragino_LHT65 as template to decode your payload. This script is written in Lua language. User can manually call this script when you see the data file in /var/iot/channels by running:
147 +4/ Use the /etc/lora/decoder/Dragino_LHT65 as template to decode your payload. This script is written in Lua language. User can manually call this script when you see the data file in /var/iot/channels by running:
161 161  
162 162  {{{/etc/lora/decoder/Dragino_LHT65 END_NODE_DEV_ADDR
163 163  }}}
164 164  
165 -**5.** What you see as output is the MQTT data device will upload, user's end node has different payload compare with LHT65, most properly this file will report with error. User need to modify to match the actual payload.
152 +5/ What you see as output is the MQTT data device will upload, user's end node has different payload compare with LHT65, most properly this file will report with error. User need to modify to match the actual payload. Some notice:
166 166  
167 -
168 -(% style="color:red" %)
169 -**Some notice:**
170 -
171 171  * RSSI and SNR are added when gateway receive the packet, so there is always this field.
172 172  * If you rename the file, please make it executable.
173 173  * See this link for lua.bit module: [[http:~~/~~/luaforge.net/projects/bit/>>url:http://luaforge.net/projects/bit/]]
... ... @@ -177,7 +177,6 @@
177 177  
178 178  
179 179  
180 -
181 181  == 2.2 Downstream ==
182 182  
183 183  
... ... @@ -187,7 +187,6 @@
187 187  
188 188  (% style="color:#037691" %)**dev_addr,imme/time,txt/hex,payload**
189 189  
190 -
191 191  Since fimware > Dragino-v2 lgw-5.4.1608518541 . Support more option
192 192  
193 193  (% style="color:#037691" %)**dev_addr,imme/time,txt/hex,payload,txpw,txbw,SF,frequency,rxwindow**
... ... @@ -218,9 +218,8 @@
218 218  * **New version:** echo 018193F4,imme,hex,0101,20,1,SF12,923300000,2 > /var/iot/push/test
219 219  
220 220  
202 +(% style="color:#037691" %)**Downstream Frequency**
221 221  
222 -(% style="color:#037691" %)**Downstream Frequency:**
223 -
224 224  The LG308 will use the RX2 window info to send the downstream payload, use the default LoRaWAN settings, as below:
225 225  
226 226  * EU868: 869.525Mhz, DR0(SF12BW125)
... ... @@ -233,7 +233,6 @@
233 233  * RU864: 869.1Mhz, SF12 BW125
234 234  
235 235  
236 -
237 237  (% style="color:#037691" %)**Examples:**
238 238  
239 239  (% class="box" %)
... ... @@ -240,19 +240,25 @@
240 240  (((
241 241  we can use echo command to create files in LG308 for downstream.
242 242  root@dragino-1d25dc:~~# echo 2602111D,time,hex,12345678 > /var/iot/push/test
222 +)))
243 243  
244 -
224 +(% class="box" %)
225 +(((
245 245  **1)** From logread -f of gateway, we can see it has been added as pedning.
246 246  lora_pkt_fwd[4286]: INFO~~ [DNLK]Looking file : test
247 247  lora_pkt_fwd[4286]: INFO~~ [DNLK]devaddr:2602111D, txmode:time, pdfm:hex, size:4, payload1:4Vx,payload_hex:77C1BB90
248 248  lora_pkt_fwd[4286]: INFO~~ [DNLK] DNLINK PENDING!(1 elems).
230 +)))
249 249  
250 -
232 +(% class="box" %)
233 +(((
251 251  **2)** When there is an upstrea from end node, this downstream will be sent and shows:
252 252  lora_pkt_fwd[4286]: INFO: tx_start_delay=1497 (1497.000000) - (1497, bw_delay=0.000000, notch_delay=0.000000)
253 253  lora_pkt_fwd[4286]: [LGWSEND]lgw_send done: count_us=3537314420, freq=923300000, size=17
237 +)))
254 254  
255 -
239 +(% class="box" %)
240 +(((
256 256  **3)** and the end node will got:
257 257  [5764825]~*~*~*~** UpLinkCounter= 98 ~*~*~*~**
258 258  [5764827]TX on freq 905300000 Hz at DR 0
... ... @@ -265,8 +265,10 @@
265 265  Rssi= -41
266 266  Receive data
267 267  (% style="color:#037691" %)**2:12345678**  (%%) ~-~-> Hex
253 +)))
268 268  
269 -
255 +(% class="box" %)
256 +(((
270 270  **4) **If we use the command "echo 2602111D,time,txt,12345678 > /var/iot/push/test" for downstream, the end node will got:
271 271  [5955877]~*~*~*~** UpLinkCounter= 102 ~*~*~*~**
272 272  [5955879]TX on freq 904100000 Hz at DR 0
... ... @@ -282,7 +282,6 @@
282 282  )))
283 283  
284 284  
285 -
286 286  = 3. Example 1: Communicate with LT-22222-L =
287 287  
288 288  
... ... @@ -326,46 +326,36 @@
326 326  #  whether the Device 2 has been changed.//
327 327  )))
328 328  
315 +**~1. Input keys**
329 329  
330 -(% style="color:blue" %)**1. Input keys**
331 -
332 -
333 333  [[image:image-20220527162450-3.png]]
334 334  
335 335  Input Keys in LPS8
336 336  
337 337  
322 +**2. Make sure the LPS8 and LT use the same frequency bands, choose EU868 in this test.**
338 338  
339 -(% style="color:blue" %)**2. Make sure the LPS8 and LT use the same frequency bands, choose EU868 in this test.**
324 +**3. Choose Built-in server**
340 340  
341 -
342 -(% style="color:blue" %)**3. Choose Built-in server**
343 -
344 -
345 345  [[image:image-20220527162518-4.png]]
346 346  
347 347  Choose Built-in server
348 348  
349 349  
331 +**4. Run the script.**
350 350  
351 -(% style="color:blue" %)**4. Run the script.**
333 +[[image:image-20220527162552-5.png]]
352 352  
353 -
354 -[[image:image-20220722115213-2.png]]
355 -
356 356  Run the script
357 357  
358 358  
338 +**5. Output:**
359 359  
360 -(% style="color:blue" %)**5. Output:**
340 +[[image:image-20220527162619-6.png]]
361 361  
362 -
363 -[[image:image-20220722115133-1.png]]
364 -
365 365  Output from LPS8
366 366  
367 367  
368 -
369 369  = 4. Example 2: Communicate to TCP Server =
370 370  
371 371  
... ... @@ -391,9 +391,8 @@
391 391  
392 392  
393 393  
394 -(% style="color:blue" %)**run socket tool in PC**
370 +**run socket tool in PC**
395 395  
396 -
397 397  [[image:image-20220527163028-9.png]]
398 398  
399 399  
... ... @@ -401,9 +401,8 @@
401 401  
402 402  
403 403  
404 -(% style="color:blue" %)**Input Server address and port**
379 +**Input Server address and port**
405 405  
406 -
407 407  [[image:image-20220527163106-10.png]]
408 408  
409 409  Input Server address and port
... ... @@ -410,9 +410,8 @@
410 410  
411 411  
412 412  
413 -(% style="color:blue" %)**See value receive in socket tool:**
387 +**See value receive in socket tool:**
414 414  
415 -
416 416  [[image:image-20220527163144-11.png]]
417 417  
418 418  value receive in socket tool
image-20220722115133-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -35.1 KB
Content
image-20220722115213-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -27.7 KB
Content

Applications

Navigation

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