Last modified by Xiaoling on 2023/04/20 18:14
<
From version < 16.8 >
edited by Xiaoling
on 2022/07/22 11:46
To version < 8.1 >
edited by Xiaoling
on 2022/05/27 16:26
>
Change comment: Uploaded new attachment "image-20220527162648-7.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -1,16 +1,14 @@
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 -* 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]]).
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]]).
14 14  
15 15  (((
16 16  The basic of this feature is the decoding of (% style="color:red" %)**LoRaWAN ABP End Node**(%%). Requirements:
... ... @@ -20,9 +20,6 @@
20 20  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]]
21 21  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/]](%%)**
22 22  
23 -
24 -
25 -
26 26  = 2. How it works =
27 27  
28 28  
... ... @@ -33,15 +33,13 @@
33 33  
34 34  (% class="box infomessage" %)
35 35  (((
36 -**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
37 37  AT+APPSKEY=b3 17 f8 14 7a 43 27 8a 6a 31 c4 47 3d 55 5d 33
38 -AT+DADDR=2602111D**
33 +AT+DADDR=2602111D
39 39  )))
40 40  
41 41  (((
42 42  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.
43 -
44 -
45 45  )))
46 46  
47 47  We need to input above keys in LG308 and enable ABP decryption.
... ... @@ -53,7 +53,6 @@
53 53  
54 54  == 2.1 Upstream ==
55 55  
56 -
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  (((
... ... @@ -62,7 +62,7 @@
62 62  
63 63  [[image:image-20220527161149-2.png]]
64 64  
65 -LG308 log by "(% style="color:red" %)**logread -f**" (%%)command
57 +LG308 log by "logread -f" command
66 66  
67 67  
68 68  The data of End Node is stored in the file /var/iot/channels/2602111D. We can use hexdump command to check it.
... ... @@ -75,9 +75,9 @@
75 75  000001c
76 76  )))
77 77  
78 -* **RSSI**: 4646 4646 4646 3946 = 0xFFFF FF9F : So RSSI = (0xFFFF FF9F - 0x100000000) = -97
79 -* **SNR**: 3030 3030 3030 3546 = 0x0000 005F = 95, need to divide 10 so SNR is 9.5
80 -* **Payload**: 0xcc0c 0b63 0266 017f ff7f ff00
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
81 81  
82 82  (% class="box" %)
83 83  (((
... ... @@ -91,13 +91,12 @@
91 91  
92 92  (% class="box" %)
93 93  (((
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.
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.
95 95  )))
96 96  
97 97  
98 98  === 2.2.1 Decode Method ===
99 99  
100 -
101 101  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.
102 102  
103 103  For example we have a LHT65 , works in ABP mode and gateway successful get the data, which are:
... ... @@ -110,7 +110,6 @@
110 110  000001c
111 111  )))
112 112  
113 -
114 114  If we choose ASCII decoder, the MQTT process will send out with mqtt-data:
115 115  
116 116  (% class="box" %)
... ... @@ -120,7 +120,6 @@
120 120  Sun Sep 27 04:33:16 2020 user.notice root: [IoT.MQTT]:mqtt_data[-m]: (% style="color:#037691" %)**ffffffe700000048ccd17fff7fff017fff7fff00**
121 121  )))
122 122  
123 -
124 124  If we choose Decode_LHT65, the MQTT process will send out with mqtt-data
125 125  
126 126  (% class="box" %)
... ... @@ -134,27 +134,21 @@
134 134  Above scripts are store in /etc/lora/decoder/. User can put their scripts here and select it in the UI.
135 135  
136 136  
137 -
138 138  === 2.2.2 How to Decode My End Node ===
139 139  
128 +1/ Configure the ABP keys for your end node in the gateway. enable ABP decode in Web UI
140 140  
141 -**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.
142 142  
143 -**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
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
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:
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:
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.
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:
153 153  
154 -
155 -(% style="color:red" %)
156 -**Some notice:**
157 -
158 158  * RSSI and SNR are added when gateway receive the packet, so there is always this field.
159 159  * If you rename the file, please make it executable.
160 160  * See this link for lua.bit module: [[http:~~/~~/luaforge.net/projects/bit/>>url:http://luaforge.net/projects/bit/]]
... ... @@ -162,9 +162,10 @@
162 162  * the last line return is what will be used for MQTT
163 163  * User can use other language ,not limited to Lua, just make sure the return is what you want to send.
164 164  
165 -== 2.2 Downstream ==
166 166  
167 167  
150 +== 2.2 Downstream ==
151 +
168 168  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
169 169  
170 170  The file should use below format:
... ... @@ -175,31 +175,30 @@
175 175  
176 176  (% style="color:#037691" %)**dev_addr,imme/time,txt/hex,payload,txpw,txbw,SF,frequency,rxwindow**
177 177  
178 -* **dev_addr:** Inptu the device address
179 -* **imme/time:**
162 +* dev_addr: Inptu the device address
163 +* imme/time:
180 180  ** imme: send downstream immediately,For Class C end node.
181 181  ** time: send downstream after receive device's uplink. For Class A end node
182 -* **txt/hex:**
166 +* txt/hex:
183 183  ** txt: send payload in ASCII
184 184  ** hex: send payload in HEX
185 -* **payload: **payload to be sent, payload lenght should match the LoRaWAN protocol requirement.
186 -* **txpw:** Transmit Power. example: 20
187 -* **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:
188 188  ** 1: 500 kHz
189 189  ** 2: 250 kHz
190 190  ** 3: 125 kHz
191 191  ** 4: 62.5 kHz
192 -* **SF:** Spreading Factor : SF7/SF8/SF9/SF10/SF11/SF12
193 -* **Frequency:** Transmit Frequency: example: 923300000
194 -* **rxwindow:** transmit on Rx1Window or Rx2Window.
176 +* SF: Spreading Factor : SF7/SF8/SF9/SF10/SF11/SF12
177 +* Frequency: Transmit Frequency: example: 923300000
178 +* rxwindow: transmit on Rx1Window or Rx2Window.
195 195  
180 +Completely exmaple:
196 196  
197 -(% style="color:blue" %)**Completely exmaple:**
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
198 198  
199 -* **Old version:** echo 018193F4,imme,hex,0101 > /var/iot/push/test
200 -* **New version:** echo 018193F4,imme,hex,0101,20,1,SF12,923300000,2 > /var/iot/push/test
201 201  
202 -
203 203  (% style="color:#037691" %)**Downstream Frequency**
204 204  
205 205  The LG308 will use the RX2 window info to send the downstream payload, use the default LoRaWAN settings, as below:
... ... @@ -220,20 +220,26 @@
220 220  (((
221 221  we can use echo command to create files in LG308 for downstream.
222 222  root@dragino-1d25dc:~~# echo 2602111D,time,hex,12345678 > /var/iot/push/test
206 +)))
223 223  
224 -
225 -**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.
226 226  lora_pkt_fwd[4286]: INFO~~ [DNLK]Looking file : test
227 227  lora_pkt_fwd[4286]: INFO~~ [DNLK]devaddr:2602111D, txmode:time, pdfm:hex, size:4, payload1:4Vx,payload_hex:77C1BB90
228 228  lora_pkt_fwd[4286]: INFO~~ [DNLK] DNLINK PENDING!(1 elems).
214 +)))
229 229  
230 -
231 -**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:
232 232  lora_pkt_fwd[4286]: INFO: tx_start_delay=1497 (1497.000000) - (1497, bw_delay=0.000000, notch_delay=0.000000)
233 233  lora_pkt_fwd[4286]: [LGWSEND]lgw_send done: count_us=3537314420, freq=923300000, size=17
221 +)))
234 234  
235 -
236 -**3)** and the end node will got:
223 +(% class="box" %)
224 +(((
225 +3) and the end node will got:
237 237  [5764825]~*~*~*~** UpLinkCounter= 98 ~*~*~*~**
238 238  [5764827]TX on freq 905300000 Hz at DR 0
239 239  Update Interval: 60000 ms
... ... @@ -245,9 +245,11 @@
245 245  Rssi= -41
246 246  Receive data
247 247  (% style="color:#037691" %)**2:12345678**  (%%) ~-~-> Hex
237 +)))
248 248  
249 -
250 -**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:
251 251  [5955877]~*~*~*~** UpLinkCounter= 102 ~*~*~*~**
252 252  [5955879]TX on freq 904100000 Hz at DR 0
253 253  Update Interval: 60000 ms
... ... @@ -264,12 +264,11 @@
264 264  
265 265  = 3. Example 1: Communicate with LT-22222-L =
266 266  
267 -
268 268  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]]
269 269  
270 270  (% class="box" %)
271 271  (((
272 -//#!/bin/sh
262 +#!/bin/sh
273 273  # This scripts shows how to use LPS8/LG308/DLOS8 to communicate with two LoRaWAN End Nodes, without the use of internet or LoRaWAN server
274 274  #
275 275  # Hardware Prepare:
... ... @@ -302,28 +302,26 @@
302 302  #  Device1: DI1: ON, DI2: ON , DO1: ON,  DO2: ON
303 303  #  Device2: DI1: OFF, DI2: OFF , DO1: ON,  DO2: ON
304 304  #  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
305 -#  whether the Device 2 has been changed.//
295 +#  whether the Device 2 has been changed.
306 306  )))
307 307  
298 +~1. Input keys
308 308  
309 -**~1. Input keys**
310 -
311 311  [[image:image-20220527162450-3.png]]
312 312  
313 313  Input Keys in LPS8
314 314  
315 315  
316 -**2. Make sure the LPS8 and LT use the same frequency bands, choose EU868 in this test.**
305 +2. Make sure the LPS8 and LT use the same frequency bands, choose EU868 in this test.
317 317  
307 +3. Choose Built-in server
318 318  
319 -**3. Choose Built-in server**
320 -
321 321  [[image:image-20220527162518-4.png]]
322 322  
323 323  Choose Built-in server
324 324  
325 325  
326 -**4. Run the script.**
314 +4. Run the script.
327 327  
328 328  [[image:image-20220527162552-5.png]]
329 329  
... ... @@ -330,7 +330,7 @@
330 330  Run the script
331 331  
332 332  
333 -**5. Output:**
321 +5. Output:
334 334  
335 335  [[image:image-20220527162619-6.png]]
336 336  
... ... @@ -339,9 +339,8 @@
339 339  
340 340  = 4. Example 2: Communicate to TCP Server =
341 341  
330 +[[image:https://wiki.dragino.com/images/thumb/7/75/LPS8_TCP_0.png/600px-LPS8_TCP_0.png||height="370" width="600"]]
342 342  
343 -[[image:image-20220527162648-7.png]]
344 -
345 345  Network Structure
346 346  
347 347  
... ... @@ -348,42 +348,34 @@
348 348  Full instruction video inlcude how to write scripts to fit server needed is here:
349 349  
350 350  
351 -(% style="color:#037691" %)**Video Instruction**(%%): **[[https:~~/~~/youtu.be/-nevW6U2TsE>>url:https://youtu.be/-nevW6U2TsE]]**
338 +(% class="mark" %)**Video Instruction**: [[https:~~/~~/youtu.be/-nevW6U2TsE>>url:https://youtu.be/-nevW6U2TsE]]
352 352  
340 +(% class="mark" %)**Note: Firmware version must be higher than lgw-5.4.1607519907**
353 353  
354 -(% style="color:red" %)**Note: Firmware version must be higher than lgw-5.4.1607519907**
355 -
356 -
357 357  Assume we already set up ABP keys in the gateway:
358 358  
359 -[[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"]]
360 360  
361 361  Input Keys in LPS8
362 362  
348 +run socket tool in PC
363 363  
350 +[[image:https://wiki.dragino.com/images/thumb/4/4b/LPS8_TCP_2.png/600px-LPS8_TCP_2.png||height="212" width="600"]]
364 364  
365 -**run socket tool in PC**
366 -
367 -[[image:image-20220527163028-9.png]]
368 -
369 -
370 370  Socket tool
371 371  
372 372  
355 +Input Server address and port
373 373  
374 -**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"]]
375 375  
376 -[[image:image-20220527163106-10.png]]
377 -
378 378  Input Server address and port
379 379  
380 380  
362 +See value receive in socket tool. :
381 381  
382 -**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"]]
383 383  
384 -[[image:image-20220527163144-11.png]]
385 -
386 386  value receive in socket tool
387 387  
388 -
389 389  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-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

Applications

Navigation

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