Last modified by Xiaoling on 2023/04/20 18:14
<
From version < 21.4 >
edited by Xiaoling
on 2023/04/20 18:11
To version < 14.5 >
edited by Xiaoling
on 2022/06/01 11:12
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,16 +1,13 @@
1 -**Table of Contents:**
1 + **Contents:**
2 2  
3 3  {{toc/}}
4 4  
5 5  
6 -
7 7  = 1. Introduction =
8 8  
9 -
10 10  The Dragino LoRaWAN gateway can commuicate with LoRaWAN ABP End Node without the need of LoRaWAN server. It can be used in some cases such as:
11 11  
12 12  * No internet connection.
13 -
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  
16 16  (((
... ... @@ -17,14 +17,12 @@
17 17  The basic of this feature is the decoding of (% style="color:red" %)**LoRaWAN ABP End Node**(%%). Requirements:
18 18  )))
19 19  
20 -* LoRaWAN End Node in ABP mode. Make sure your end node works in this mode. End node most are default set to OTAA mode
17 +1. LoRaWAN End Node in ABP mode. Make sure your end node works in this mode. End node most are default set to OTAA mode
18 +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]]
19 +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/]](%%)**
21 21  
22 -* 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]]
23 23  
24 -* 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/]](%%)**
25 25  
26 -
27 -
28 28  = 2. How it works =
29 29  
30 30  
... ... @@ -35,44 +35,35 @@
35 35  
36 36  (% class="box infomessage" %)
37 37  (((
38 -**AT+NWKSKEY=72 32 63 95 dd 8f e2 b2 13 66 e4 35 93 8f 55 df
33 +AT+NWKSKEY=72 32 63 95 dd 8f e2 b2 13 66 e4 35 93 8f 55 df
39 39  AT+APPSKEY=b3 17 f8 14 7a 43 27 8a 6a 31 c4 47 3d 55 5d 33
40 -AT+DADDR=2602111D**
35 +AT+DADDR=2602111D
41 41  )))
42 42  
43 43  (((
44 44  and we have the LG308 works and US915 band and support ABP decryption. User can input these keys in LG308 so the LG308 can communicate with LGT92.
45 -
46 -
47 47  )))
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 58  == 2.1 Upstream ==
59 59  
60 -
61 61  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.
62 62  
63 63  (((
64 -We can see the log of LG308 to know this packet arrive.
65 -
66 -
54 +We can see the log of LG308 to know this packet arrive
67 67  )))
68 68  
69 69  [[image:image-20220527161149-2.png]]
70 70  
59 +LG308 log by "logread -f" command
71 71  
72 -LG308 log by "(% style="color:red" %)**logread -f**" (%%)command
73 73  
74 -
75 -
76 76  The data of End Node is stored in the file /var/iot/channels/2602111D. We can use hexdump command to check it.
77 77  
78 78  (% class="box" %)
... ... @@ -83,12 +83,10 @@
83 83  000001c
84 84  )))
85 85  
86 -* **RSSI**: 4646 4646 4646 3946 = 0xFFFF FF9F : So RSSI = (0xFFFF FF9F - 0x100000000) = -97
72 +* RSSI: 4646 4646 4646 3946 = 0xFFFF FF9F : So RSSI = (0xFFFF FF9F - 0x100000000) = -97
73 +* SNR: 3030 3030 3030 3546 = 0x0000 005F = 95, need to divide 10 so SNR is 9.5
74 +* Payload: 0xcc0c 0b63 0266 017f ff7f ff00
87 87  
88 -* **SNR**: 3030 3030 3030 3546 = 0x0000 005F = 95, need to divide 10 so SNR is 9.5
89 -
90 -* **Payload**: 0xcc0c 0b63 0266 017f ff7f ff00
91 -
92 92  (% class="box" %)
93 93  (((
94 94  (% 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:
... ... @@ -99,16 +99,14 @@
99 99  000001c
100 100  )))
101 101  
102 -
103 103  (% class="box" %)
104 104  (((
105 -(% 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.
88 +(% style="color:#037691" %)**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.
106 106  )))
107 107  
108 108  
109 109  === 2.2.1 Decode Method ===
110 110  
111 -
112 112  The decode methods: (% style="color:#037691" %)**ASCII String, Decode_LHT65**(%%) doesn't affect how the sensor data is stored, they are to define how should the sensor data to be sent.
113 113  
114 114  For example we have a LHT65 , works in ABP mode and gateway successful get the data, which are:
... ... @@ -121,7 +121,6 @@
121 121  000001c
122 122  )))
123 123  
124 -
125 125  If we choose ASCII decoder, the MQTT process will send out with mqtt-data:
126 126  
127 127  (% class="box" %)
... ... @@ -131,7 +131,6 @@
131 131  Sun Sep 27 04:33:16 2020 user.notice root: [IoT.MQTT]:mqtt_data[-m]: (% style="color:#037691" %)**ffffffe700000048ccd17fff7fff017fff7fff00**
132 132  )))
133 133  
134 -
135 135  If we choose Decode_LHT65, the MQTT process will send out with mqtt-data
136 136  
137 137  (% class="box" %)
... ... @@ -147,41 +147,29 @@
147 147  
148 148  === 2.2.2 How to Decode My End Node ===
149 149  
130 +1/ Configure the ABP keys for your end node in the gateway. enable ABP decode in Web UI
150 150  
151 -**1.** Configure the ABP keys for your end node in the gateway. enable ABP decode in Web UI
132 +2/ Don't choose MQTT service, use LoRaWAN.
152 152  
153 -**2. **Don't choose MQTT service, use LoRaWAN.
134 +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
154 154  
155 -**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
136 +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:
156 156  
157 -**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:
158 -
159 159  {{{/etc/lora/decoder/Dragino_LHT65 END_NODE_DEV_ADDR
160 160  }}}
161 161  
162 -**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.
141 +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:
163 163  
164 -
165 -(% style="color:red" %)
166 -**Some notice:**
167 -
168 168  * RSSI and SNR are added when gateway receive the packet, so there is always this field.
169 -
170 170  * If you rename the file, please make it executable.
171 -
172 172  * See this link for lua.bit module: [[http:~~/~~/luaforge.net/projects/bit/>>url:http://luaforge.net/projects/bit/]]
173 -
174 174  * Lua json module: [[http:~~/~~/json.luaforge.net/>>url:http://json.luaforge.net/]]
175 -
176 176  * the last line return is what will be used for MQTT
177 -
178 178  * User can use other language ,not limited to Lua, just make sure the return is what you want to send.
179 179  
180 180  
181 -
182 182  == 2.2 Downstream ==
183 183  
184 -
185 185  In LG308, we can create a file in the directory /var/iot/push for downstream purpose. We recommend using each command to generate this file. This file will be used for transmission and auto-deleted after used
186 186  
187 187  The file should use below format:
... ... @@ -188,68 +188,46 @@
188 188  
189 189  (% style="color:#037691" %)**dev_addr,imme/time,txt/hex,payload**
190 190  
159 +Since fimware > Dragino-v2 lgw-5.4.1608518541 . Support more option
191 191  
192 -Since fimware > [[Dragino lgw~~-~~-build-v5.4.1668567157>>https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LG308-LG301/Firmware/Release/]] . Support more option
161 +(% style="color:#037691" %)**dev_addr,imme/time,txt/hex,payload,txpw,txbw,SF,frequency,rxwindow**
193 193  
194 -(% style="color:#037691" %)**dev_addr,imme/time,txt/hex,payload,txpw,txbw,SF,frequency,rxwindow,Fport**
195 -
196 -* **dev_addr:** Inptu the device address
197 -
198 -* **imme/time:**
163 +* dev_addr: Inptu the device address
164 +* imme/time:
199 199  ** imme: send downstream immediately,For Class C end node.
200 200  ** time: send downstream after receive device's uplink. For Class A end node
201 -
202 -* **txt/hex:**
167 +* txt/hex:
203 203  ** txt: send payload in ASCII
204 204  ** hex: send payload in HEX
205 -
206 -* **payload: **payload to be sent, payload lenght should match the LoRaWAN protocol requirement.
207 -
208 -* **txpw:** Transmit Power. example: 20
209 -
210 -* **txbw:** bandwidth:
170 +* payload: payload to be sent, payload lenght should match the LoRaWAN protocol requirement.
171 +* txpw: Transmit Power. example: 20
172 +* txbw: bandwidth:
211 211  ** 1: 500 kHz
212 212  ** 2: 250 kHz
213 213  ** 3: 125 kHz
214 214  ** 4: 62.5 kHz
215 -* **SF:** Spreading Factor : SF7/SF8/SF9/SF10/SF11/SF12
177 +* SF: Spreading Factor : SF7/SF8/SF9/SF10/SF11/SF12
178 +* Frequency: Transmit Frequency: example: 923300000
179 +* rxwindow: transmit on Rx1Window or Rx2Window.
216 216  
217 -* **Frequency:** Transmit Frequency: example: 923300000
181 +Completely exmaple:
218 218  
219 -* **rxwindow:** transmit on Rx1Window or Rx2Window.
183 +* Old version: echo 018193F4,imme,hex,0101 > /var/iot/push/test
184 +* New version: echo 018193F4,imme,hex,0101,20,1,SF12,923300000,2 > /var/iot/push/test
220 220  
221 -* **Fport: **Transmit port,example:8
186 +(% style="color:#037691" %)**Downstream Frequency**
222 222  
223 -
224 -(% style="color:blue" %)**Completely exmaple:**
225 -
226 -* **Old version:** echo 018193F4,imme,hex,0101 > /var/iot/push/test
227 -
228 -* **New version:** echo 018193F4,imme,hex,0101,20,1,SF12,923300000,2,8 > /var/iot/push/test
229 -
230 -
231 -Downstream(% style="color:#037691" %)** Frequency:**
232 -
233 233  The LG308 will use the RX2 window info to send the downstream payload, use the default LoRaWAN settings, as below:
234 234  
235 235  * EU868: 869.525Mhz, DR0(SF12BW125)
236 -
237 237  * US915: 923.3Mhz, SF12 BW500
238 -
239 239  * CN470: 505.3Mhz, SF12 BW125
240 -
241 241  * AU915: 923.3Mhz, SF12 BW500
242 -
243 243  * AS923: 923.2Mhz, SF10 BW125
244 -
245 245  * KR920: 921.9Mhz, SF12 BW125
246 -
247 247  * IN865: 866.55Mhz, SF10 BW125
248 -
249 249  * RU864: 869.1Mhz, SF12 BW125
250 250  
251 -
252 -
253 253  (% style="color:#037691" %)**Examples:**
254 254  
255 255  (% class="box" %)
... ... @@ -256,20 +256,26 @@
256 256  (((
257 257  we can use echo command to create files in LG308 for downstream.
258 258  root@dragino-1d25dc:~~# echo 2602111D,time,hex,12345678 > /var/iot/push/test
205 +)))
259 259  
260 -
261 -**1)** From logread -f of gateway, we can see it has been added as pedning.
207 +(% class="box" %)
208 +(((
209 +1) From logread -f of gateway, we can see it has been added as pedning.
262 262  lora_pkt_fwd[4286]: INFO~~ [DNLK]Looking file : test
263 263  lora_pkt_fwd[4286]: INFO~~ [DNLK]devaddr:2602111D, txmode:time, pdfm:hex, size:4, payload1:4Vx,payload_hex:77C1BB90
264 264  lora_pkt_fwd[4286]: INFO~~ [DNLK] DNLINK PENDING!(1 elems).
213 +)))
265 265  
266 -
267 -**2)** When there is an upstrea from end node, this downstream will be sent and shows:
215 +(% class="box" %)
216 +(((
217 +2) When there is an upstrea from end node, this downstream will be sent and shows:
268 268  lora_pkt_fwd[4286]: INFO: tx_start_delay=1497 (1497.000000) - (1497, bw_delay=0.000000, notch_delay=0.000000)
269 269  lora_pkt_fwd[4286]: [LGWSEND]lgw_send done: count_us=3537314420, freq=923300000, size=17
220 +)))
270 270  
271 -
272 -**3)** and the end node will got:
222 +(% class="box" %)
223 +(((
224 +3) and the end node will got:
273 273  [5764825]~*~*~*~** UpLinkCounter= 98 ~*~*~*~**
274 274  [5764827]TX on freq 905300000 Hz at DR 0
275 275  Update Interval: 60000 ms
... ... @@ -281,9 +281,11 @@
281 281  Rssi= -41
282 282  Receive data
283 283  (% style="color:#037691" %)**2:12345678**  (%%) ~-~-> Hex
236 +)))
284 284  
285 -
286 -**4) **If we use the command "echo 2602111D,time,txt,12345678 > /var/iot/push/test" for downstream, the end node will got:
238 +(% class="box" %)
239 +(((
240 +4) If we use the command "echo 2602111D,time,txt,12345678 > /var/iot/push/test" for downstream, the end node will got:
287 287  [5955877]~*~*~*~** UpLinkCounter= 102 ~*~*~*~**
288 288  [5955879]TX on freq 904100000 Hz at DR 0
289 289  Update Interval: 60000 ms
... ... @@ -300,12 +300,11 @@
300 300  
301 301  = 3. Example 1: Communicate with LT-22222-L =
302 302  
303 -
304 304  Script can be download from: [[Example Script 1>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/customized_script/&file=talk_to_lt-22222-l_v0.1.sh]]
305 305  
306 306  (% class="box" %)
307 307  (((
308 -//#!/bin/sh
261 +#!/bin/sh
309 309  # This scripts shows how to use LPS8/LG308/DLOS8 to communicate with two LoRaWAN End Nodes, without the use of internet or LoRaWAN server
310 310  #
311 311  # Hardware Prepare:
... ... @@ -338,51 +338,41 @@
338 338  #  Device1: DI1: ON, DI2: ON , DO1: ON,  DO2: ON
339 339  #  Device2: DI1: OFF, DI2: OFF , DO1: ON,  DO2: ON
340 340  #  So if a person is in the Device 1 location, he can check if the DO LED match DI LEDs on Device 1 to confirm
341 -#  whether the Device 2 has been changed.//
294 +#  whether the Device 2 has been changed.
342 342  )))
343 343  
297 +~1. Input keys
344 344  
345 -(% style="color:blue" %)**1. Input keys**
346 -
347 -
348 348  [[image:image-20220527162450-3.png]]
349 349  
350 350  Input Keys in LPS8
351 351  
352 352  
304 +2. Make sure the LPS8 and LT use the same frequency bands, choose EU868 in this test.
353 353  
354 -(% style="color:blue" %)**2. Make sure the LPS8 and LT use the same frequency bands, choose EU868 in this test.**
306 +3. Choose Built-in server
355 355  
356 -
357 -(% style="color:blue" %)**3. Choose Built-in server**
358 -
359 -
360 360  [[image:image-20220527162518-4.png]]
361 361  
362 362  Choose Built-in server
363 363  
364 364  
313 +4. Run the script.
365 365  
366 -(% style="color:blue" %)**4. Run the script.**
315 +[[image:image-20220527162552-5.png]]
367 367  
368 -
369 -[[image:image-20220722115213-2.png]]
370 -
371 371  Run the script
372 372  
373 373  
320 +5. Output:
374 374  
375 -(% style="color:blue" %)**5. Output:**
322 +[[image:image-20220527162619-6.png]]
376 376  
377 -
378 -[[image:image-20220722115133-1.png]]
379 -
380 380  Output from LPS8
381 381  
382 382  
383 383  = 4. Example 2: Communicate to TCP Server =
384 384  
385 -
386 386  [[image:image-20220527162648-7.png]]
387 387  
388 388  Network Structure
... ... @@ -390,13 +390,12 @@
390 390  
391 391  Full instruction video inlcude how to write scripts to fit server needed is here:
392 392  
336 +
393 393  (% style="color:#037691" %)**Video Instruction**(%%): **[[https:~~/~~/youtu.be/-nevW6U2TsE>>url:https://youtu.be/-nevW6U2TsE]]**
394 394  
395 -(% style="display:none" %) (%%)
396 396  
397 397  (% style="color:red" %)**Note: Firmware version must be higher than lgw-5.4.1607519907**
398 398  
399 -
400 400  Assume we already set up ABP keys in the gateway:
401 401  
402 402  [[image:image-20220527162852-8.png]]
... ... @@ -404,10 +404,8 @@
404 404  Input Keys in LPS8
405 405  
406 406  
349 +run socket tool in PC
407 407  
408 -(% style="color:blue" %)**run socket tool in PC**
409 -
410 -
411 411  [[image:image-20220527163028-9.png]]
412 412  
413 413  
... ... @@ -414,22 +414,17 @@
414 414  Socket tool
415 415  
416 416  
357 +Input Server address and port
417 417  
418 -(% style="color:blue" %)**Input Server address and port**
419 -
420 -
421 421  [[image:image-20220527163106-10.png]]
422 422  
423 423  Input Server address and port
424 424  
425 425  
364 +See value receive in socket tool. :
426 426  
427 -(% style="color:blue" %)**See value receive in socket tool:**
366 +[[image:image-20220527163144-11.png]]
428 428  
429 -
430 -[[image:image-20220527163144-11.png||height="502" width="1371"]]
431 -
432 432  value receive in socket tool
433 433  
434 -
435 435  If user want to modify the TCP connection method. He can refer: [[https:~~/~~/github.com/dragino/dragino-packages/blob/lg02/haserl-ui/root/usr/bin/tcp_process.sh>>url:https://github.com/dragino/dragino-packages/blob/lg02/haserl-ui/root/usr/bin/tcp_process.sh]]. Same script is on /usr/bin of gateway.
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-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0