Last modified by Xiaoling on 2023/04/20 18:14
<
From version < 16.9 >
edited by Xiaoling
on 2022/07/22 11:47
To version < 6.1 >
edited by Xiaoling
on 2022/05/27 16:25
>
Change comment: Uploaded new attachment "image-20220527162552-5.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,13 +75,10 @@
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 -
83 -
84 -
85 85  (% class="box" %)
86 86  (((
87 87  (% 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:
... ... @@ -94,13 +94,12 @@
94 94  
95 95  (% class="box" %)
96 96  (((
97 -(% 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.
98 98  )))
99 99  
100 100  
101 101  === 2.2.1 Decode Method ===
102 102  
103 -
104 104  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.
105 105  
106 106  For example we have a LHT65 , works in ABP mode and gateway successful get the data, which are:
... ... @@ -113,7 +113,6 @@
113 113  000001c
114 114  )))
115 115  
116 -
117 117  If we choose ASCII decoder, the MQTT process will send out with mqtt-data:
118 118  
119 119  (% class="box" %)
... ... @@ -123,7 +123,6 @@
123 123  Sun Sep 27 04:33:16 2020 user.notice root: [IoT.MQTT]:mqtt_data[-m]: (% style="color:#037691" %)**ffffffe700000048ccd17fff7fff017fff7fff00**
124 124  )))
125 125  
126 -
127 127  If we choose Decode_LHT65, the MQTT process will send out with mqtt-data
128 128  
129 129  (% class="box" %)
... ... @@ -137,27 +137,21 @@
137 137  Above scripts are store in /etc/lora/decoder/. User can put their scripts here and select it in the UI.
138 138  
139 139  
140 -
141 141  === 2.2.2 How to Decode My End Node ===
142 142  
128 +1/ Configure the ABP keys for your end node in the gateway. enable ABP decode in Web UI
143 143  
144 -**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.
145 145  
146 -**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
147 147  
148 -**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:
149 149  
150 -**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:
151 -
152 152  {{{/etc/lora/decoder/Dragino_LHT65 END_NODE_DEV_ADDR
153 153  }}}
154 154  
155 -**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:
156 156  
157 -
158 -(% style="color:red" %)
159 -**Some notice:**
160 -
161 161  * RSSI and SNR are added when gateway receive the packet, so there is always this field.
162 162  * If you rename the file, please make it executable.
163 163  * See this link for lua.bit module: [[http:~~/~~/luaforge.net/projects/bit/>>url:http://luaforge.net/projects/bit/]]
... ... @@ -167,11 +167,8 @@
167 167  
168 168  
169 169  
170 -
171 -
172 172  == 2.2 Downstream ==
173 173  
174 -
175 175  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
176 176  
177 177  The file should use below format:
... ... @@ -182,31 +182,30 @@
182 182  
183 183  (% style="color:#037691" %)**dev_addr,imme/time,txt/hex,payload,txpw,txbw,SF,frequency,rxwindow**
184 184  
185 -* **dev_addr:** Inptu the device address
186 -* **imme/time:**
162 +* dev_addr: Inptu the device address
163 +* imme/time:
187 187  ** imme: send downstream immediately,For Class C end node.
188 188  ** time: send downstream after receive device's uplink. For Class A end node
189 -* **txt/hex:**
166 +* txt/hex:
190 190  ** txt: send payload in ASCII
191 191  ** hex: send payload in HEX
192 -* **payload: **payload to be sent, payload lenght should match the LoRaWAN protocol requirement.
193 -* **txpw:** Transmit Power. example: 20
194 -* **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:
195 195  ** 1: 500 kHz
196 196  ** 2: 250 kHz
197 197  ** 3: 125 kHz
198 198  ** 4: 62.5 kHz
199 -* **SF:** Spreading Factor : SF7/SF8/SF9/SF10/SF11/SF12
200 -* **Frequency:** Transmit Frequency: example: 923300000
201 -* **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.
202 202  
180 +Completely exmaple:
203 203  
204 -(% 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
205 205  
206 -* **Old version:** echo 018193F4,imme,hex,0101 > /var/iot/push/test
207 -* **New version:** echo 018193F4,imme,hex,0101,20,1,SF12,923300000,2 > /var/iot/push/test
208 208  
209 -
210 210  (% style="color:#037691" %)**Downstream Frequency**
211 211  
212 212  The LG308 will use the RX2 window info to send the downstream payload, use the default LoRaWAN settings, as below:
... ... @@ -227,20 +227,26 @@
227 227  (((
228 228  we can use echo command to create files in LG308 for downstream.
229 229  root@dragino-1d25dc:~~# echo 2602111D,time,hex,12345678 > /var/iot/push/test
206 +)))
230 230  
231 -
232 -**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.
233 233  lora_pkt_fwd[4286]: INFO~~ [DNLK]Looking file : test
234 234  lora_pkt_fwd[4286]: INFO~~ [DNLK]devaddr:2602111D, txmode:time, pdfm:hex, size:4, payload1:4Vx,payload_hex:77C1BB90
235 235  lora_pkt_fwd[4286]: INFO~~ [DNLK] DNLINK PENDING!(1 elems).
214 +)))
236 236  
237 -
238 -**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:
239 239  lora_pkt_fwd[4286]: INFO: tx_start_delay=1497 (1497.000000) - (1497, bw_delay=0.000000, notch_delay=0.000000)
240 240  lora_pkt_fwd[4286]: [LGWSEND]lgw_send done: count_us=3537314420, freq=923300000, size=17
221 +)))
241 241  
242 -
243 -**3)** and the end node will got:
223 +(% class="box" %)
224 +(((
225 +3) and the end node will got:
244 244  [5764825]~*~*~*~** UpLinkCounter= 98 ~*~*~*~**
245 245  [5764827]TX on freq 905300000 Hz at DR 0
246 246  Update Interval: 60000 ms
... ... @@ -252,9 +252,11 @@
252 252  Rssi= -41
253 253  Receive data
254 254  (% style="color:#037691" %)**2:12345678**  (%%) ~-~-> Hex
237 +)))
255 255  
256 -
257 -**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:
258 258  [5955877]~*~*~*~** UpLinkCounter= 102 ~*~*~*~**
259 259  [5955879]TX on freq 904100000 Hz at DR 0
260 260  Update Interval: 60000 ms
... ... @@ -271,12 +271,11 @@
271 271  
272 272  = 3. Example 1: Communicate with LT-22222-L =
273 273  
274 -
275 275  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]]
276 276  
277 277  (% class="box" %)
278 278  (((
279 -//#!/bin/sh
262 +#!/bin/sh
280 280  # This scripts shows how to use LPS8/LG308/DLOS8 to communicate with two LoRaWAN End Nodes, without the use of internet or LoRaWAN server
281 281  #
282 282  # Hardware Prepare:
... ... @@ -309,46 +309,42 @@
309 309  #  Device1: DI1: ON, DI2: ON , DO1: ON,  DO2: ON
310 310  #  Device2: DI1: OFF, DI2: OFF , DO1: ON,  DO2: ON
311 311  #  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
312 -#  whether the Device 2 has been changed.//
295 +#  whether the Device 2 has been changed.
313 313  )))
314 314  
298 +~1. Input keys
315 315  
316 -**~1. Input keys**
317 -
318 318  [[image:image-20220527162450-3.png]]
319 319  
320 320  Input Keys in LPS8
321 321  
322 322  
323 -**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.
324 324  
307 +3. Choose Built-in server
325 325  
326 -**3. Choose Built-in server**
327 -
328 328  [[image:image-20220527162518-4.png]]
329 329  
330 330  Choose Built-in server
331 331  
332 332  
333 -**4. Run the script.**
314 +4. Run the script.
334 334  
335 -[[image:image-20220527162552-5.png]]
316 +[[image:https://wiki.dragino.com/images/thumb/3/39/LPS8_LT-22222_3.png/600px-LPS8_LT-22222_3.png||height="389" width="600"]]
336 336  
337 337  Run the script
338 338  
320 +5. Output:
339 339  
340 -**5. Output:**
322 +[[image:https://wiki.dragino.com/images/thumb/f/fe/LPS8_LT-22222_4.png/600px-LPS8_LT-22222_4.png||height="433" width="600"]]
341 341  
342 -[[image:image-20220527162619-6.png]]
343 -
344 344  Output from LPS8
345 345  
346 346  
347 347  = 4. Example 2: Communicate to TCP Server =
348 348  
329 +[[image:https://wiki.dragino.com/images/thumb/7/75/LPS8_TCP_0.png/600px-LPS8_TCP_0.png||height="370" width="600"]]
349 349  
350 -[[image:image-20220527162648-7.png]]
351 -
352 352  Network Structure
353 353  
354 354  
... ... @@ -355,42 +355,34 @@
355 355  Full instruction video inlcude how to write scripts to fit server needed is here:
356 356  
357 357  
358 -(% style="color:#037691" %)**Video Instruction**(%%): **[[https:~~/~~/youtu.be/-nevW6U2TsE>>url:https://youtu.be/-nevW6U2TsE]]**
337 +(% class="mark" %)**Video Instruction**: [[https:~~/~~/youtu.be/-nevW6U2TsE>>url:https://youtu.be/-nevW6U2TsE]]
359 359  
339 +(% class="mark" %)**Note: Firmware version must be higher than lgw-5.4.1607519907**
360 360  
361 -(% style="color:red" %)**Note: Firmware version must be higher than lgw-5.4.1607519907**
362 -
363 -
364 364  Assume we already set up ABP keys in the gateway:
365 365  
366 -[[image:image-20220527162852-8.png]]
343 +[[image:https://wiki.dragino.com/images/thumb/b/bf/LPS8_LT-22222_1.png/600px-LPS8_LT-22222_1.png||height="335" width="600"]]
367 367  
368 368  Input Keys in LPS8
369 369  
347 +run socket tool in PC
370 370  
349 +[[image:https://wiki.dragino.com/images/thumb/4/4b/LPS8_TCP_2.png/600px-LPS8_TCP_2.png||height="212" width="600"]]
371 371  
372 -**run socket tool in PC**
373 -
374 -[[image:image-20220527163028-9.png]]
375 -
376 -
377 377  Socket tool
378 378  
379 379  
354 +Input Server address and port
380 380  
381 -**Input Server address and port**
356 +[[image:https://wiki.dragino.com/images/thumb/c/c6/LPS8_TCP_3.png/600px-LPS8_TCP_3.png||height="306" width="600"]]
382 382  
383 -[[image:image-20220527163106-10.png]]
384 -
385 385  Input Server address and port
386 386  
387 387  
361 +See value receive in socket tool. :
388 388  
389 -**See value receive in socket tool:**
363 +[[image:https://wiki.dragino.com/images/thumb/2/20/LPS8_TCP_4.png/600px-LPS8_TCP_4.png||height="219" width="600"]]
390 390  
391 -[[image:image-20220527163144-11.png]]
392 -
393 393  value receive in socket tool
394 394  
395 -
396 396  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-20220527162619-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -41.0 KB
Content
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

Applications

Navigation

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