Last modified by Xiaoling on 2023/04/20 18:14
<
From version < 14.1 >
edited by Xiaoling
on 2022/05/27 16:33
To version < 16.2 >
edited by Xiaoling
on 2022/07/22 11:41
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,14 +1,16 @@
1 - **Contents:**
1 +**Table of Contents:**
2 2  
3 3  {{toc/}}
4 4  
5 5  
6 +
6 6  = 1. Introduction =
7 7  
9 +
8 8  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:
9 9  
10 10  * 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 +* 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]]).
12 12  
13 13  (((
14 14  The basic of this feature is the decoding of (% style="color:red" %)**LoRaWAN ABP End Node**(%%). Requirements:
... ... @@ -19,7 +19,6 @@
19 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/]](%%)**
20 20  
21 21  
22 -
23 23  = 2. How it works =
24 24  
25 25  
... ... @@ -30,13 +30,15 @@
30 30  
31 31  (% class="box infomessage" %)
32 32  (((
33 -AT+NWKSKEY=72 32 63 95 dd 8f e2 b2 13 66 e4 35 93 8f 55 df
34 +**AT+NWKSKEY=72 32 63 95 dd 8f e2 b2 13 66 e4 35 93 8f 55 df
34 34  AT+APPSKEY=b3 17 f8 14 7a 43 27 8a 6a 31 c4 47 3d 55 5d 33
35 -AT+DADDR=2602111D
36 +AT+DADDR=2602111D**
36 36  )))
37 37  
38 38  (((
39 39  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.
41 +
42 +
40 40  )))
41 41  
42 42  We need to input above keys in LG308 and enable ABP decryption.
... ... @@ -48,6 +48,7 @@
48 48  
49 49  == 2.1 Upstream ==
50 50  
54 +
51 51  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.
52 52  
53 53  (((
... ... @@ -56,7 +56,7 @@
56 56  
57 57  [[image:image-20220527161149-2.png]]
58 58  
59 -LG308 log by "logread -f" command
63 +LG308 log by "(% style="color:red" %)**logread -f**" (%%)command
60 60  
61 61  
62 62  The data of End Node is stored in the file /var/iot/channels/2602111D. We can use hexdump command to check it.
... ... @@ -69,9 +69,9 @@
69 69  000001c
70 70  )))
71 71  
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
76 +* **RSSI**: 4646 4646 4646 3946 = 0xFFFF FF9F : So RSSI = (0xFFFF FF9F - 0x100000000) = -97
77 +* **SNR**: 3030 3030 3030 3546 = 0x0000 005F = 95, need to divide 10 so SNR is 9.5
78 +* **Payload**: 0xcc0c 0b63 0266 017f ff7f ff00
75 75  
76 76  (% class="box" %)
77 77  (((
... ... @@ -85,12 +85,13 @@
85 85  
86 86  (% class="box" %)
87 87  (((
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.
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.
89 89  )))
90 90  
91 91  
92 92  === 2.2.1 Decode Method ===
93 93  
98 +
94 94  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.
95 95  
96 96  For example we have a LHT65 , works in ABP mode and gateway successful get the data, which are:
... ... @@ -103,6 +103,7 @@
103 103  000001c
104 104  )))
105 105  
111 +
106 106  If we choose ASCII decoder, the MQTT process will send out with mqtt-data:
107 107  
108 108  (% class="box" %)
... ... @@ -112,6 +112,7 @@
112 112  Sun Sep 27 04:33:16 2020 user.notice root: [IoT.MQTT]:mqtt_data[-m]: (% style="color:#037691" %)**ffffffe700000048ccd17fff7fff017fff7fff00**
113 113  )))
114 114  
121 +
115 115  If we choose Decode_LHT65, the MQTT process will send out with mqtt-data
116 116  
117 117  (% class="box" %)
... ... @@ -125,21 +125,27 @@
125 125  Above scripts are store in /etc/lora/decoder/. User can put their scripts here and select it in the UI.
126 126  
127 127  
135 +
128 128  === 2.2.2 How to Decode My End Node ===
129 129  
130 -1/ Configure the ABP keys for your end node in the gateway. enable ABP decode in Web UI
131 131  
132 -2/ Don't choose MQTT service, use LoRaWAN.
139 +**1.** Configure the ABP keys for your end node in the gateway. enable ABP decode in Web UI
133 133  
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
141 +**2. **Don't choose MQTT service, use LoRaWAN.
135 135  
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:
143 +**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
137 137  
145 +**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 +
138 138  {{{/etc/lora/decoder/Dragino_LHT65 END_NODE_DEV_ADDR
139 139  }}}
140 140  
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:
150 +**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.
142 142  
152 +
153 +(% style="color:red" %)
154 +**Some notice:**
155 +
143 143  * RSSI and SNR are added when gateway receive the packet, so there is always this field.
144 144  * If you rename the file, please make it executable.
145 145  * See this link for lua.bit module: [[http:~~/~~/luaforge.net/projects/bit/>>url:http://luaforge.net/projects/bit/]]
... ... @@ -151,6 +151,7 @@
151 151  
152 152  == 2.2 Downstream ==
153 153  
167 +
154 154  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
155 155  
156 156  The file should use below format:
... ... @@ -161,28 +161,28 @@
161 161  
162 162  (% style="color:#037691" %)**dev_addr,imme/time,txt/hex,payload,txpw,txbw,SF,frequency,rxwindow**
163 163  
164 -* dev_addr: Inptu the device address
165 -* imme/time:
178 +* **dev_addr:** Inptu the device address
179 +* **imme/time:**
166 166  ** imme: send downstream immediately,For Class C end node.
167 167  ** time: send downstream after receive device's uplink. For Class A end node
168 -* txt/hex:
182 +* **txt/hex:**
169 169  ** txt: send payload in ASCII
170 170  ** hex: send payload in HEX
171 -* payload: payload to be sent, payload lenght should match the LoRaWAN protocol requirement.
172 -* txpw: Transmit Power. example: 20
173 -* txbw: bandwidth:
185 +* **payload: **payload to be sent, payload lenght should match the LoRaWAN protocol requirement.
186 +* **txpw:** Transmit Power. example: 20
187 +* **txbw:** bandwidth:
174 174  ** 1: 500 kHz
175 175  ** 2: 250 kHz
176 176  ** 3: 125 kHz
177 177  ** 4: 62.5 kHz
178 -* SF: Spreading Factor : SF7/SF8/SF9/SF10/SF11/SF12
179 -* Frequency: Transmit Frequency: example: 923300000
180 -* rxwindow: transmit on Rx1Window or Rx2Window.
192 +* **SF:** Spreading Factor : SF7/SF8/SF9/SF10/SF11/SF12
193 +* **Frequency:** Transmit Frequency: example: 923300000
194 +* **rxwindow:** transmit on Rx1Window or Rx2Window.
181 181  
182 -Completely exmaple:
196 +(% style="color:blue" %)**Completely exmaple:**
183 183  
184 -* Old version: echo 018193F4,imme,hex,0101 > /var/iot/push/test
185 -* New version: echo 018193F4,imme,hex,0101,20,1,SF12,923300000,2 > /var/iot/push/test
198 +* **Old version:** echo 018193F4,imme,hex,0101 > /var/iot/push/test
199 +* **New version:** echo 018193F4,imme,hex,0101,20,1,SF12,923300000,2 > /var/iot/push/test
186 186  
187 187  (% style="color:#037691" %)**Downstream Frequency**
188 188  
... ... @@ -207,7 +207,7 @@
207 207  
208 208  (% class="box" %)
209 209  (((
210 -1) From logread -f of gateway, we can see it has been added as pedning.
224 +**1)** From logread -f of gateway, we can see it has been added as pedning.
211 211  lora_pkt_fwd[4286]: INFO~~ [DNLK]Looking file : test
212 212  lora_pkt_fwd[4286]: INFO~~ [DNLK]devaddr:2602111D, txmode:time, pdfm:hex, size:4, payload1:4Vx,payload_hex:77C1BB90
213 213  lora_pkt_fwd[4286]: INFO~~ [DNLK] DNLINK PENDING!(1 elems).
... ... @@ -215,7 +215,7 @@
215 215  
216 216  (% class="box" %)
217 217  (((
218 -2) When there is an upstrea from end node, this downstream will be sent and shows:
232 +**2)** When there is an upstrea from end node, this downstream will be sent and shows:
219 219  lora_pkt_fwd[4286]: INFO: tx_start_delay=1497 (1497.000000) - (1497, bw_delay=0.000000, notch_delay=0.000000)
220 220  lora_pkt_fwd[4286]: [LGWSEND]lgw_send done: count_us=3537314420, freq=923300000, size=17
221 221  )))
... ... @@ -222,7 +222,7 @@
222 222  
223 223  (% class="box" %)
224 224  (((
225 -3) and the end node will got:
239 +**3)** and the end node will got:
226 226  [5764825]~*~*~*~** UpLinkCounter= 98 ~*~*~*~**
227 227  [5764827]TX on freq 905300000 Hz at DR 0
228 228  Update Interval: 60000 ms
... ... @@ -238,7 +238,7 @@
238 238  
239 239  (% class="box" %)
240 240  (((
241 -4) If we use the command "echo 2602111D,time,txt,12345678 > /var/iot/push/test" for downstream, the end node will got:
255 +**4) **If we use the command "echo 2602111D,time,txt,12345678 > /var/iot/push/test" for downstream, the end node will got:
242 242  [5955877]~*~*~*~** UpLinkCounter= 102 ~*~*~*~**
243 243  [5955879]TX on freq 904100000 Hz at DR 0
244 244  Update Interval: 60000 ms
... ... @@ -255,11 +255,12 @@
255 255  
256 256  = 3. Example 1: Communicate with LT-22222-L =
257 257  
272 +
258 258  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]]
259 259  
260 260  (% class="box" %)
261 261  (((
262 -#!/bin/sh
277 +//#!/bin/sh
263 263  # This scripts shows how to use LPS8/LG308/DLOS8 to communicate with two LoRaWAN End Nodes, without the use of internet or LoRaWAN server
264 264  #
265 265  # Hardware Prepare:
... ... @@ -292,10 +292,10 @@
292 292  #  Device1: DI1: ON, DI2: ON , DO1: ON,  DO2: ON
293 293  #  Device2: DI1: OFF, DI2: OFF , DO1: ON,  DO2: ON
294 294  #  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
295 -#  whether the Device 2 has been changed.
310 +#  whether the Device 2 has been changed.//
296 296  )))
297 297  
298 -~1. Input keys
313 +**~1. Input keys**
299 299  
300 300  [[image:image-20220527162450-3.png]]
301 301  
... ... @@ -302,9 +302,9 @@
302 302  Input Keys in LPS8
303 303  
304 304  
305 -2. Make sure the LPS8 and LT use the same frequency bands, choose EU868 in this test.
320 +**2. Make sure the LPS8 and LT use the same frequency bands, choose EU868 in this test.**
306 306  
307 -3. Choose Built-in server
322 +**3. Choose Built-in server**
308 308  
309 309  [[image:image-20220527162518-4.png]]
310 310  
... ... @@ -311,7 +311,7 @@
311 311  Choose Built-in server
312 312  
313 313  
314 -4. Run the script.
329 +**4. Run the script.**
315 315  
316 316  [[image:image-20220527162552-5.png]]
317 317  
... ... @@ -318,7 +318,7 @@
318 318  Run the script
319 319  
320 320  
321 -5. Output:
336 +**5. Output:**
322 322  
323 323  [[image:image-20220527162619-6.png]]
324 324  
... ... @@ -327,6 +327,7 @@
327 327  
328 328  = 4. Example 2: Communicate to TCP Server =
329 329  
345 +
330 330  [[image:image-20220527162648-7.png]]
331 331  
332 332  Network Structure
... ... @@ -340,6 +340,7 @@
340 340  
341 341  (% style="color:red" %)**Note: Firmware version must be higher than lgw-5.4.1607519907**
342 342  
359 +
343 343  Assume we already set up ABP keys in the gateway:
344 344  
345 345  [[image:image-20220527162852-8.png]]
... ... @@ -347,8 +347,9 @@
347 347  Input Keys in LPS8
348 348  
349 349  
350 -run socket tool in PC
351 351  
368 +**run socket tool in PC**
369 +
352 352  [[image:image-20220527163028-9.png]]
353 353  
354 354  
... ... @@ -355,17 +355,20 @@
355 355  Socket tool
356 356  
357 357  
358 -Input Server address and port
359 359  
377 +**Input Server address and port**
378 +
360 360  [[image:image-20220527163106-10.png]]
361 361  
362 362  Input Server address and port
363 363  
364 364  
365 -See value receive in socket tool. :
366 366  
385 +**See value receive in socket tool:**
386 +
367 367  [[image:image-20220527163144-11.png]]
368 368  
369 369  value receive in socket tool
370 370  
391 +
371 371  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.

Applications

Navigation

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