Last modified by Xiaoling on 2023/04/20 18:14
<
From version < 16.1 >
edited by Xiaoling
on 2022/07/22 11:33
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  )))
... ... @@ -46,11 +46,14 @@
46 46  
47 47  We need to input above keys in LG308 and enable ABP decryption.
48 48  
51 +
49 49  [[image:image-20220527161119-1.png]]
50 50  
54 +
51 51  Input the ABP keys in LG308
52 52  
53 53  
58 +
54 54  == 2.1 Upstream ==
55 55  
56 56  
... ... @@ -57,14 +57,18 @@
57 57  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.
58 58  
59 59  (((
60 -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 +
61 61  )))
62 62  
63 63  [[image:image-20220527161149-2.png]]
64 64  
72 +
65 65  LG308 log by "(% style="color:red" %)**logread -f**" (%%)command
66 66  
67 67  
76 +
68 68  The data of End Node is stored in the file /var/iot/channels/2602111D. We can use hexdump command to check it.
69 69  
70 70  (% class="box" %)
... ... @@ -79,6 +79,8 @@
79 79  * **SNR**: 3030 3030 3030 3546 = 0x0000 005F = 95, need to divide 10 so SNR is 9.5
80 80  * **Payload**: 0xcc0c 0b63 0266 017f ff7f ff00
81 81  
91 +
92 +
82 82  (% class="box" %)
83 83  (((
84 84  (% 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:
... ... @@ -89,6 +89,7 @@
89 89  000001c
90 90  )))
91 91  
103 +
92 92  (% class="box" %)
93 93  (((
94 94  (% 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.
... ... @@ -95,6 +95,7 @@
95 95  )))
96 96  
97 97  
110 +
98 98  === 2.2.1 Decode Method ===
99 99  
100 100  
... ... @@ -138,19 +138,23 @@
138 138  === 2.2.2 How to Decode My End Node ===
139 139  
140 140  
141 -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
142 142  
143 -2/ Don't choose MQTT service, use LoRaWAN.
156 +**2. **Don't choose MQTT service, use LoRaWAN.
144 144  
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
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
146 146  
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:
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:
148 148  
149 149  {{{/etc/lora/decoder/Dragino_LHT65 END_NODE_DEV_ADDR
150 150  }}}
151 151  
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:
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.
153 153  
167 +
168 +(% style="color:red" %)
169 +**Some notice:**
170 +
154 154  * RSSI and SNR are added when gateway receive the packet, so there is always this field.
155 155  * If you rename the file, please make it executable.
156 156  * See this link for lua.bit module: [[http:~~/~~/luaforge.net/projects/bit/>>url:http://luaforge.net/projects/bit/]]
... ... @@ -160,6 +160,7 @@
160 160  
161 161  
162 162  
180 +
163 163  == 2.2 Downstream ==
164 164  
165 165  
... ... @@ -169,6 +169,7 @@
169 169  
170 170  (% style="color:#037691" %)**dev_addr,imme/time,txt/hex,payload**
171 171  
190 +
172 172  Since fimware > Dragino-v2 lgw-5.4.1608518541 . Support more option
173 173  
174 174  (% style="color:#037691" %)**dev_addr,imme/time,txt/hex,payload,txpw,txbw,SF,frequency,rxwindow**
... ... @@ -199,8 +199,9 @@
199 199  * **New version:** echo 018193F4,imme,hex,0101,20,1,SF12,923300000,2 > /var/iot/push/test
200 200  
201 201  
202 -(% style="color:#037691" %)**Downstream Frequency**
203 203  
222 +(% style="color:#037691" %)**Downstream Frequency:**
223 +
204 204  The LG308 will use the RX2 window info to send the downstream payload, use the default LoRaWAN settings, as below:
205 205  
206 206  * EU868: 869.525Mhz, DR0(SF12BW125)
... ... @@ -213,6 +213,7 @@
213 213  * RU864: 869.1Mhz, SF12 BW125
214 214  
215 215  
236 +
216 216  (% style="color:#037691" %)**Examples:**
217 217  
218 218  (% class="box" %)
... ... @@ -219,25 +219,19 @@
219 219  (((
220 220  we can use echo command to create files in LG308 for downstream.
221 221  root@dragino-1d25dc:~~# echo 2602111D,time,hex,12345678 > /var/iot/push/test
222 -)))
223 223  
224 -(% class="box" %)
225 -(((
244 +
226 226  **1)** From logread -f of gateway, we can see it has been added as pedning.
227 227  lora_pkt_fwd[4286]: INFO~~ [DNLK]Looking file : test
228 228  lora_pkt_fwd[4286]: INFO~~ [DNLK]devaddr:2602111D, txmode:time, pdfm:hex, size:4, payload1:4Vx,payload_hex:77C1BB90
229 229  lora_pkt_fwd[4286]: INFO~~ [DNLK] DNLINK PENDING!(1 elems).
230 -)))
231 231  
232 -(% class="box" %)
233 -(((
250 +
234 234  **2)** When there is an upstrea from end node, this downstream will be sent and shows:
235 235  lora_pkt_fwd[4286]: INFO: tx_start_delay=1497 (1497.000000) - (1497, bw_delay=0.000000, notch_delay=0.000000)
236 236  lora_pkt_fwd[4286]: [LGWSEND]lgw_send done: count_us=3537314420, freq=923300000, size=17
237 -)))
238 238  
239 -(% class="box" %)
240 -(((
255 +
241 241  **3)** and the end node will got:
242 242  [5764825]~*~*~*~** UpLinkCounter= 98 ~*~*~*~**
243 243  [5764827]TX on freq 905300000 Hz at DR 0
... ... @@ -250,10 +250,8 @@
250 250  Rssi= -41
251 251  Receive data
252 252  (% style="color:#037691" %)**2:12345678**  (%%) ~-~-> Hex
253 -)))
254 254  
255 -(% class="box" %)
256 -(((
269 +
257 257  **4) **If we use the command "echo 2602111D,time,txt,12345678 > /var/iot/push/test" for downstream, the end node will got:
258 258  [5955877]~*~*~*~** UpLinkCounter= 102 ~*~*~*~**
259 259  [5955879]TX on freq 904100000 Hz at DR 0
... ... @@ -269,6 +269,7 @@
269 269  )))
270 270  
271 271  
285 +
272 272  = 3. Example 1: Communicate with LT-22222-L =
273 273  
274 274  
... ... @@ -312,36 +312,46 @@
312 312  #  whether the Device 2 has been changed.//
313 313  )))
314 314  
315 -**~1. Input keys**
316 316  
330 +(% style="color:blue" %)**1. Input keys**
331 +
332 +
317 317  [[image:image-20220527162450-3.png]]
318 318  
319 319  Input Keys in LPS8
320 320  
321 321  
322 -**2. Make sure the LPS8 and LT use the same frequency bands, choose EU868 in this test.**
323 323  
324 -**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.**
325 325  
341 +
342 +(% style="color:blue" %)**3. Choose Built-in server**
343 +
344 +
326 326  [[image:image-20220527162518-4.png]]
327 327  
328 328  Choose Built-in server
329 329  
330 330  
331 -**4. Run the script.**
332 332  
333 -[[image:image-20220527162552-5.png]]
351 +(% style="color:blue" %)**4. Run the script.**
334 334  
353 +
354 +[[image:image-20220722115213-2.png]]
355 +
335 335  Run the script
336 336  
337 337  
338 -**5. Output:**
339 339  
340 -[[image:image-20220527162619-6.png]]
360 +(% style="color:blue" %)**5. Output:**
341 341  
362 +
363 +[[image:image-20220722115133-1.png]]
364 +
342 342  Output from LPS8
343 343  
344 344  
368 +
345 345  = 4. Example 2: Communicate to TCP Server =
346 346  
347 347  
... ... @@ -367,8 +367,9 @@
367 367  
368 368  
369 369  
370 -**run socket tool in PC**
394 +(% style="color:blue" %)**run socket tool in PC**
371 371  
396 +
372 372  [[image:image-20220527163028-9.png]]
373 373  
374 374  
... ... @@ -376,8 +376,9 @@
376 376  
377 377  
378 378  
379 -**Input Server address and port**
404 +(% style="color:blue" %)**Input Server address and port**
380 380  
406 +
381 381  [[image:image-20220527163106-10.png]]
382 382  
383 383  Input Server address and port
... ... @@ -384,8 +384,9 @@
384 384  
385 385  
386 386  
387 -**See value receive in socket tool:**
413 +(% style="color:blue" %)**See value receive in socket tool:**
388 388  
415 +
389 389  [[image:image-20220527163144-11.png]]
390 390  
391 391  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-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0