Last modified by Xiaoling on 2023/04/20 18:14
<
From version < 15.1 >
edited by Xiaoling
on 2022/07/22 11:32
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
... ... @@ -1,5 +1,4 @@
1 -*
2 -** Table of** **Contents:
1 +**Table of Contents:**
3 3  
4 4  {{toc/}}
5 5  
... ... @@ -13,6 +13,8 @@
13 13  * No internet connection.
14 14  * 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]]).
15 15  
15 +
16 +
16 16  (((
17 17  The basic of this feature is the decoding of (% style="color:red" %)**LoRaWAN ABP End Node**(%%). Requirements:
18 18  )))
... ... @@ -21,6 +21,9 @@
21 21  1. LoRaWAN Gateway model: [[LPS8>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/148-lps8.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]] ,[[LIG16>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/171-lig16.html]]
22 22  1. Firmware version for below instruction:**[[(% style="color:purple" %)Since LG02_LG08~~-~~-build-v5.4.1593400722-20200629-1120>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/]](%%)**
23 23  
25 +
26 +
27 +
24 24  = 2. How it works =
25 25  
26 26  
... ... @@ -44,11 +44,14 @@
44 44  
45 45  We need to input above keys in LG308 and enable ABP decryption.
46 46  
51 +
47 47  [[image:image-20220527161119-1.png]]
48 48  
54 +
49 49  Input the ABP keys in LG308
50 50  
51 51  
58 +
52 52  == 2.1 Upstream ==
53 53  
54 54  
... ... @@ -55,14 +55,18 @@
55 55  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.
56 56  
57 57  (((
58 -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 +
59 59  )))
60 60  
61 61  [[image:image-20220527161149-2.png]]
62 62  
72 +
63 63  LG308 log by "(% style="color:red" %)**logread -f**" (%%)command
64 64  
65 65  
76 +
66 66  The data of End Node is stored in the file /var/iot/channels/2602111D. We can use hexdump command to check it.
67 67  
68 68  (% class="box" %)
... ... @@ -77,6 +77,8 @@
77 77  * **SNR**: 3030 3030 3030 3546 = 0x0000 005F = 95, need to divide 10 so SNR is 9.5
78 78  * **Payload**: 0xcc0c 0b63 0266 017f ff7f ff00
79 79  
91 +
92 +
80 80  (% class="box" %)
81 81  (((
82 82  (% 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:
... ... @@ -87,6 +87,7 @@
87 87  000001c
88 88  )))
89 89  
103 +
90 90  (% class="box" %)
91 91  (((
92 92  (% 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.
... ... @@ -93,6 +93,7 @@
93 93  )))
94 94  
95 95  
110 +
96 96  === 2.2.1 Decode Method ===
97 97  
98 98  
... ... @@ -132,22 +132,27 @@
132 132  Above scripts are store in /etc/lora/decoder/. User can put their scripts here and select it in the UI.
133 133  
134 134  
150 +
135 135  === 2.2.2 How to Decode My End Node ===
136 136  
137 137  
138 -1/ Configure the ABP keys for your end node in the gateway. enable ABP decode in Web UI
154 +**1.** Configure the ABP keys for your end node in the gateway. enable ABP decode in Web UI
139 139  
140 -2/ Don't choose MQTT service, use LoRaWAN.
156 +**2. **Don't choose MQTT service, use LoRaWAN.
141 141  
142 -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
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
143 143  
144 -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:
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:
145 145  
146 146  {{{/etc/lora/decoder/Dragino_LHT65 END_NODE_DEV_ADDR
147 147  }}}
148 148  
149 -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:
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.
150 150  
167 +
168 +(% style="color:red" %)
169 +**Some notice:**
170 +
151 151  * RSSI and SNR are added when gateway receive the packet, so there is always this field.
152 152  * If you rename the file, please make it executable.
153 153  * See this link for lua.bit module: [[http:~~/~~/luaforge.net/projects/bit/>>url:http://luaforge.net/projects/bit/]]
... ... @@ -157,6 +157,7 @@
157 157  
158 158  
159 159  
180 +
160 160  == 2.2 Downstream ==
161 161  
162 162  
... ... @@ -166,6 +166,7 @@
166 166  
167 167  (% style="color:#037691" %)**dev_addr,imme/time,txt/hex,payload**
168 168  
190 +
169 169  Since fimware > Dragino-v2 lgw-5.4.1608518541 . Support more option
170 170  
171 171  (% style="color:#037691" %)**dev_addr,imme/time,txt/hex,payload,txpw,txbw,SF,frequency,rxwindow**
... ... @@ -189,6 +189,7 @@
189 189  * **rxwindow:** transmit on Rx1Window or Rx2Window.
190 190  
191 191  
214 +
192 192  (% style="color:blue" %)**Completely exmaple:**
193 193  
194 194  * **Old version:** echo 018193F4,imme,hex,0101 > /var/iot/push/test
... ... @@ -196,7 +196,7 @@
196 196  
197 197  
198 198  
199 -(% style="color:#037691" %)**Downstream Frequency**
222 +(% style="color:#037691" %)**Downstream Frequency:**
200 200  
201 201  The LG308 will use the RX2 window info to send the downstream payload, use the default LoRaWAN settings, as below:
202 202  
... ... @@ -217,25 +217,19 @@
217 217  (((
218 218  we can use echo command to create files in LG308 for downstream.
219 219  root@dragino-1d25dc:~~# echo 2602111D,time,hex,12345678 > /var/iot/push/test
220 -)))
221 221  
222 -(% class="box" %)
223 -(((
244 +
224 224  **1)** From logread -f of gateway, we can see it has been added as pedning.
225 225  lora_pkt_fwd[4286]: INFO~~ [DNLK]Looking file : test
226 226  lora_pkt_fwd[4286]: INFO~~ [DNLK]devaddr:2602111D, txmode:time, pdfm:hex, size:4, payload1:4Vx,payload_hex:77C1BB90
227 227  lora_pkt_fwd[4286]: INFO~~ [DNLK] DNLINK PENDING!(1 elems).
228 -)))
229 229  
230 -(% class="box" %)
231 -(((
250 +
232 232  **2)** When there is an upstrea from end node, this downstream will be sent and shows:
233 233  lora_pkt_fwd[4286]: INFO: tx_start_delay=1497 (1497.000000) - (1497, bw_delay=0.000000, notch_delay=0.000000)
234 234  lora_pkt_fwd[4286]: [LGWSEND]lgw_send done: count_us=3537314420, freq=923300000, size=17
235 -)))
236 236  
237 -(% class="box" %)
238 -(((
255 +
239 239  **3)** and the end node will got:
240 240  [5764825]~*~*~*~** UpLinkCounter= 98 ~*~*~*~**
241 241  [5764827]TX on freq 905300000 Hz at DR 0
... ... @@ -248,10 +248,8 @@
248 248  Rssi= -41
249 249  Receive data
250 250  (% style="color:#037691" %)**2:12345678**  (%%) ~-~-> Hex
251 -)))
252 252  
253 -(% class="box" %)
254 -(((
269 +
255 255  **4) **If we use the command "echo 2602111D,time,txt,12345678 > /var/iot/push/test" for downstream, the end node will got:
256 256  [5955877]~*~*~*~** UpLinkCounter= 102 ~*~*~*~**
257 257  [5955879]TX on freq 904100000 Hz at DR 0
... ... @@ -267,6 +267,7 @@
267 267  )))
268 268  
269 269  
285 +
270 270  = 3. Example 1: Communicate with LT-22222-L =
271 271  
272 272  
... ... @@ -310,36 +310,46 @@
310 310  #  whether the Device 2 has been changed.//
311 311  )))
312 312  
313 -**~1. Input keys**
314 314  
330 +(% style="color:blue" %)**1. Input keys**
331 +
332 +
315 315  [[image:image-20220527162450-3.png]]
316 316  
317 317  Input Keys in LPS8
318 318  
319 319  
320 -**2. Make sure the LPS8 and LT use the same frequency bands, choose EU868 in this test.**
321 321  
322 -**3. Choose Built-in server**
339 +(% style="color:blue" %)**2. Make sure the LPS8 and LT use the same frequency bands, choose EU868 in this test.**
323 323  
341 +
342 +(% style="color:blue" %)**3. Choose Built-in server**
343 +
344 +
324 324  [[image:image-20220527162518-4.png]]
325 325  
326 326  Choose Built-in server
327 327  
328 328  
329 -**4. Run the script.**
330 330  
331 -[[image:image-20220527162552-5.png]]
351 +(% style="color:blue" %)**4. Run the script.**
332 332  
353 +
354 +[[image:image-20220722115213-2.png]]
355 +
333 333  Run the script
334 334  
335 335  
336 -**5. Output:**
337 337  
338 -[[image:image-20220527162619-6.png]]
360 +(% style="color:blue" %)**5. Output:**
339 339  
362 +
363 +[[image:image-20220722115133-1.png]]
364 +
340 340  Output from LPS8
341 341  
342 342  
368 +
343 343  = 4. Example 2: Communicate to TCP Server =
344 344  
345 345  
... ... @@ -365,8 +365,9 @@
365 365  
366 366  
367 367  
368 -**run socket tool in PC**
394 +(% style="color:blue" %)**run socket tool in PC**
369 369  
396 +
370 370  [[image:image-20220527163028-9.png]]
371 371  
372 372  
... ... @@ -374,8 +374,9 @@
374 374  
375 375  
376 376  
377 -**Input Server address and port**
404 +(% style="color:blue" %)**Input Server address and port**
378 378  
406 +
379 379  [[image:image-20220527163106-10.png]]
380 380  
381 381  Input Server address and port
... ... @@ -382,8 +382,9 @@
382 382  
383 383  
384 384  
385 -**See value receive in socket tool:**
413 +(% style="color:blue" %)**See value receive in socket tool:**
386 386  
415 +
387 387  [[image:image-20220527163144-11.png]]
388 388  
389 389  value receive in socket tool
image-20220722115133-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +35.1 KB
Content
image-20220722115213-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +27.7 KB
Content

Applications

Navigation

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