Skip to Content
Last modified by Xiaoling on 2025/07/31 15:09
From version 22.1
edited by Xiaoling
on 2025/07/31 15:07
Change comment: There is no comment for this version
To version 7.2
edited by Xiaoling
on 2022/05/27 16:26
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,30 +1,23 @@
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.
11 +* 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>>url:https://wiki.dragino.com/index.php/MQTT_Forward_Instruction]]).
13 13  
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 -
16 16  (((
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: [[DLOS8N>>url:https://www.dragino.com/products/lora-lorawan-gateway/item/225-dlos8n.html]], [[LPS8N>>url:https://www.dragino.com/products/lora-lorawan-gateway/item/200-lps8n.html]], [[LG308N>>url:https://www.dragino.com/products/lora-lorawan-gateway/item/229-lg308n.html]]
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 -
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
31 +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**
33 +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 -
52 +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  
57 +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
70 +* RSSI: 4646 4646 4646 3946 = 0xFFFF FF9F : So RSSI = (0xFFFF FF9F - 0x100000000) = -97
71 +* SNR: 3030 3030 3030 3546 = 0x0000 005F = 95, need to divide 10 so SNR is 9.5
72 +* 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,17 +99,14 @@
99 99  000001c
100 100  )))
101 101  
102 -
103 -
104 104  (% class="box" %)
105 105  (((
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.
86 +(% 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.
107 107  )))
108 108  
109 109  
110 110  === 2.2.1 Decode Method ===
111 111  
112 -
113 113  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.
114 114  
115 115  For example we have a LHT65 , works in ABP mode and gateway successful get the data, which are:
... ... @@ -122,7 +122,6 @@
122 122  000001c
123 123  )))
124 124  
125 -
126 126  If we choose ASCII decoder, the MQTT process will send out with mqtt-data:
127 127  
128 128  (% class="box" %)
... ... @@ -132,7 +132,6 @@
132 132  Sun Sep 27 04:33:16 2020 user.notice root: [IoT.MQTT]:mqtt_data[-m]: (% style="color:#037691" %)**ffffffe700000048ccd17fff7fff017fff7fff00**
133 133  )))
134 134  
135 -
136 136  If we choose Decode_LHT65, the MQTT process will send out with mqtt-data
137 137  
138 138  (% class="box" %)
... ... @@ -148,34 +148,24 @@
148 148  
149 149  === 2.2.2 How to Decode My End Node ===
150 150  
128 +1/ Configure the ABP keys for your end node in the gateway. enable ABP decode in Web UI
151 151  
152 -**1.** Configure the ABP keys for your end node in the gateway. enable ABP decode in Web UI
130 +2/ Don't choose MQTT service, use LoRaWAN.
153 153  
154 -**2. **Don't choose MQTT service, use LoRaWAN.
132 +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
155 155  
156 -**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
134 +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:
157 157  
158 -**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:
159 -
160 160  {{{/etc/lora/decoder/Dragino_LHT65 END_NODE_DEV_ADDR
161 161  }}}
162 162  
163 -**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.
139 +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:
164 164  
165 -
166 -(% style="color:red" %)
167 -**Some notice:**
168 -
169 169  * RSSI and SNR are added when gateway receive the packet, so there is always this field.
170 -
171 171  * If you rename the file, please make it executable.
172 -
173 173  * See this link for lua.bit module: [[http:~~/~~/luaforge.net/projects/bit/>>url:http://luaforge.net/projects/bit/]]
174 -
175 175  * Lua json module: [[http:~~/~~/json.luaforge.net/>>url:http://json.luaforge.net/]]
176 -
177 177  * the last line return is what will be used for MQTT
178 -
179 179  * User can use other language ,not limited to Lua, just make sure the return is what you want to send.
180 180  
181 181  
... ... @@ -182,7 +182,6 @@
182 182  
183 183  == 2.2 Downstream ==
184 184  
185 -
186 186  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
187 187  
188 188  The file should use below format:
... ... @@ -189,66 +189,48 @@
189 189  
190 190  (% style="color:#037691" %)**dev_addr,imme/time,txt/hex,payload**
191 191  
158 +Since fimware > Dragino-v2 lgw-5.4.1608518541 . Support more option
192 192  
193 -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
160 +(% style="color:#037691" %)**dev_addr,imme/time,txt/hex,payload,txpw,txbw,SF,frequency,rxwindow**
194 194  
195 -(% style="color:#037691" %)**dev_addr,imme/time,txt/hex,payload,txpw,txbw,SF,frequency,rxwindow,Fport**
196 -
197 -* **dev_addr:** Inptu the device address
198 -
199 -* **imme/time:**
162 +* dev_addr: Inptu the device address
163 +* imme/time:
200 200  ** imme: send downstream immediately,For Class C end node.
201 201  ** time: send downstream after receive device's uplink. For Class A end node
202 -
203 -* **txt/hex:**
166 +* txt/hex:
204 204  ** txt: send payload in ASCII
205 205  ** hex: send payload in HEX
206 -
207 -* **payload: **payload to be sent, payload lenght should match the LoRaWAN protocol requirement.
208 -
209 -* **txpw:** Transmit Power. example: 20
210 -
211 -* **txbw:** bandwidth:
169 +* payload: payload to be sent, payload lenght should match the LoRaWAN protocol requirement.
170 +* txpw: Transmit Power. example: 20
171 +* txbw: bandwidth:
212 212  ** 1: 500 kHz
213 213  ** 2: 250 kHz
214 214  ** 3: 125 kHz
215 215  ** 4: 62.5 kHz
216 -* **SF:** Spreading Factor : SF7/SF8/SF9/SF10/SF11/SF12
176 +* SF: Spreading Factor : SF7/SF8/SF9/SF10/SF11/SF12
177 +* Frequency: Transmit Frequency: example: 923300000
178 +* rxwindow: transmit on Rx1Window or Rx2Window.
217 217  
218 -* **Frequency:** Transmit Frequency: example: 923300000
180 +Completely exmaple:
219 219  
220 -* **rxwindow:** transmit on Rx1Window or Rx2Window.
182 +* Old version: echo 018193F4,imme,hex,0101 > /var/iot/push/test
183 +* New version: echo 018193F4,imme,hex,0101,20,1,SF12,923300000,2 > /var/iot/push/test
221 221  
222 -* **Fport: **Transmit port,example:8
223 223  
224 -(% style="color:blue" %)**Completely exmaple:**
186 +(% style="color:#037691" %)**Downstream Frequency**
225 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 -Downstream(% style="color:#037691" %)** Frequency:**
231 -
232 232  The LG308 will use the RX2 window info to send the downstream payload, use the default LoRaWAN settings, as below:
233 233  
234 234  * EU868: 869.525Mhz, DR0(SF12BW125)
235 -
236 236  * US915: 923.3Mhz, SF12 BW500
237 -
238 238  * CN470: 505.3Mhz, SF12 BW125
239 -
240 240  * AU915: 923.3Mhz, SF12 BW500
241 -
242 242  * AS923: 923.2Mhz, SF10 BW125
243 -
244 244  * KR920: 921.9Mhz, SF12 BW125
245 -
246 246  * IN865: 866.55Mhz, SF10 BW125
247 -
248 248  * RU864: 869.1Mhz, SF12 BW125
249 249  
250 250  
251 -
252 252  (% style="color:#037691" %)**Examples:**
253 253  
254 254  (% class="box" %)
... ... @@ -255,20 +255,26 @@
255 255  (((
256 256  we can use echo command to create files in LG308 for downstream.
257 257  root@dragino-1d25dc:~~# echo 2602111D,time,hex,12345678 > /var/iot/push/test
206 +)))
258 258  
259 -
260 -**1)** From logread -f of gateway, we can see it has been added as pedning.
208 +(% class="box" %)
209 +(((
210 +1) From logread -f of gateway, we can see it has been added as pedning.
261 261  lora_pkt_fwd[4286]: INFO~~ [DNLK]Looking file : test
262 262  lora_pkt_fwd[4286]: INFO~~ [DNLK]devaddr:2602111D, txmode:time, pdfm:hex, size:4, payload1:4Vx,payload_hex:77C1BB90
263 263  lora_pkt_fwd[4286]: INFO~~ [DNLK] DNLINK PENDING!(1 elems).
214 +)))
264 264  
265 -
266 -**2)** When there is an upstrea from end node, this downstream will be sent and shows:
216 +(% class="box" %)
217 +(((
218 +2) When there is an upstrea from end node, this downstream will be sent and shows:
267 267  lora_pkt_fwd[4286]: INFO: tx_start_delay=1497 (1497.000000) - (1497, bw_delay=0.000000, notch_delay=0.000000)
268 268  lora_pkt_fwd[4286]: [LGWSEND]lgw_send done: count_us=3537314420, freq=923300000, size=17
221 +)))
269 269  
270 -
271 -**3)** and the end node will got:
223 +(% class="box" %)
224 +(((
225 +3) and the end node will got:
272 272  [5764825]~*~*~*~** UpLinkCounter= 98 ~*~*~*~**
273 273  [5764827]TX on freq 905300000 Hz at DR 0
274 274  Update Interval: 60000 ms
... ... @@ -280,9 +280,11 @@
280 280  Rssi= -41
281 281  Receive data
282 282  (% style="color:#037691" %)**2:12345678**  (%%) ~-~-> Hex
237 +)))
283 283  
284 -
285 -**4) **If we use the command "echo 2602111D,time,txt,12345678 > /var/iot/push/test" for downstream, the end node will got:
239 +(% class="box" %)
240 +(((
241 +4) If we use the command "echo 2602111D,time,txt,12345678 > /var/iot/push/test" for downstream, the end node will got:
286 286  [5955877]~*~*~*~** UpLinkCounter= 102 ~*~*~*~**
287 287  [5955879]TX on freq 904100000 Hz at DR 0
288 288  Update Interval: 60000 ms
... ... @@ -299,12 +299,11 @@
299 299  
300 300  = 3. Example 1: Communicate with LT-22222-L =
301 301  
302 -
303 303  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]]
304 304  
305 305  (% class="box" %)
306 306  (((
307 -//#!/bin/sh
262 +#!/bin/sh
308 308  # This scripts shows how to use LPS8/LG308/DLOS8 to communicate with two LoRaWAN End Nodes, without the use of internet or LoRaWAN server
309 309  #
310 310  # Hardware Prepare:
... ... @@ -337,98 +337,77 @@
337 337  #  Device1: DI1: ON, DI2: ON , DO1: ON,  DO2: ON
338 338  #  Device2: DI1: OFF, DI2: OFF , DO1: ON,  DO2: ON
339 339  #  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
340 -#  whether the Device 2 has been changed.//
295 +#  whether the Device 2 has been changed.
341 341  )))
342 342  
298 +~1. Input keys
343 343  
344 -(% style="color:blue" %)**1. Input keys**
345 -
346 -
347 347  [[image:image-20220527162450-3.png]]
348 348  
349 349  Input Keys in LPS8
350 350  
351 351  
305 +2. Make sure the LPS8 and LT use the same frequency bands, choose EU868 in this test.
352 352  
353 -(% style="color:blue" %)**2. Make sure the LPS8 and LT use the same frequency bands, choose EU868 in this test.**
307 +3. Choose Built-in server
354 354  
355 -
356 -(% style="color:blue" %)**3. Choose Built-in server**
357 -
358 -
359 359  [[image:image-20220527162518-4.png]]
360 360  
361 361  Choose Built-in server
362 362  
363 363  
314 +4. Run the script.
364 364  
365 -(% style="color:blue" %)**4. Run the script.**
316 +[[image:image-20220527162552-5.png]]
366 366  
367 -
368 -[[image:image-20220722115213-2.png]]
369 -
370 370  Run the script
371 371  
372 372  
321 +5. Output:
373 373  
374 -(% style="color:blue" %)**5. Output:**
323 +[[image:image-20220527162619-6.png]]
375 375  
376 -
377 -[[image:image-20220722115133-1.png]]
378 -
379 379  Output from LPS8
380 380  
381 381  
382 382  = 4. Example 2: Communicate to TCP Server =
383 383  
330 +[[image:https://wiki.dragino.com/images/thumb/7/75/LPS8_TCP_0.png/600px-LPS8_TCP_0.png||height="370" width="600"]]
384 384  
385 -[[image:image-20220527162648-7.png]]
386 -
387 387  Network Structure
388 388  
389 389  
390 390  Full instruction video inlcude how to write scripts to fit server needed is here:
391 391  
392 -(% style="color:#037691" %)**Video Instruction**(%%): **[[https:~~/~~/youtu.be/-nevW6U2TsE>>url:https://youtu.be/-nevW6U2TsE]]**
393 393  
394 -(% style="display:none" %) (%%)
338 +(% class="mark" %)**Video Instruction**: [[https:~~/~~/youtu.be/-nevW6U2TsE>>url:https://youtu.be/-nevW6U2TsE]]
395 395  
396 -(% style="color:red" %)**Note: Firmware version must be higher than lgw-5.4.1607519907**
340 +(% class="mark" %)**Note: Firmware version must be higher than lgw-5.4.1607519907**
397 397  
398 -
399 399  Assume we already set up ABP keys in the gateway:
400 400  
401 -[[image:image-20220527162852-8.png]]
344 +[[image:https://wiki.dragino.com/images/thumb/b/bf/LPS8_LT-22222_1.png/600px-LPS8_LT-22222_1.png||height="335" width="600"]]
402 402  
403 403  Input Keys in LPS8
404 404  
348 +run socket tool in PC
405 405  
350 +[[image:https://wiki.dragino.com/images/thumb/4/4b/LPS8_TCP_2.png/600px-LPS8_TCP_2.png||height="212" width="600"]]
406 406  
407 -(% style="color:blue" %)**run socket tool in PC**
408 -
409 -
410 -[[image:image-20220527163028-9.png]]
411 -
412 -
413 413  Socket tool
414 414  
415 415  
355 +Input Server address and port
416 416  
417 -(% style="color:blue" %)**Input Server address and port**
357 +[[image:https://wiki.dragino.com/images/thumb/c/c6/LPS8_TCP_3.png/600px-LPS8_TCP_3.png||height="306" width="600"]]
418 418  
419 -
420 -[[image:image-20220527163106-10.png]]
421 -
422 422  Input Server address and port
423 423  
424 424  
362 +See value receive in socket tool. :
425 425  
426 -(% style="color:blue" %)**See value receive in socket tool:**
364 +[[image:https://wiki.dragino.com/images/thumb/2/20/LPS8_TCP_4.png/600px-LPS8_TCP_4.png||height="219" width="600"]]
427 427  
428 -
429 -[[image:image-20220527163144-11.png||height="502" width="1371"]]
430 -
431 431  value receive in socket tool
432 432  
433 -
434 434  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-20220527162648-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -151.7 KB
Content
image-20220527162852-8.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -125.6 KB
Content
image-20220527163028-9.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -32.9 KB
Content
image-20220527163106-10.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -34.5 KB
Content
image-20220527163144-11.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -107.7 KB
Content
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