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

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:
... ... @@ -92,17 +92,14 @@
92 92  000001c
93 93  )))
94 94  
95 -
96 96  (% class="box" %)
97 97  (((
98 -(% 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.
99 99  )))
100 100  
101 101  
102 -
103 103  === 2.2.1 Decode Method ===
104 104  
105 -
106 106  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.
107 107  
108 108  For example we have a LHT65 , works in ABP mode and gateway successful get the data, which are:
... ... @@ -115,7 +115,6 @@
115 115  000001c
116 116  )))
117 117  
118 -
119 119  If we choose ASCII decoder, the MQTT process will send out with mqtt-data:
120 120  
121 121  (% class="box" %)
... ... @@ -125,7 +125,6 @@
125 125  Sun Sep 27 04:33:16 2020 user.notice root: [IoT.MQTT]:mqtt_data[-m]: (% style="color:#037691" %)**ffffffe700000048ccd17fff7fff017fff7fff00**
126 126  )))
127 127  
128 -
129 129  If we choose Decode_LHT65, the MQTT process will send out with mqtt-data
130 130  
131 131  (% class="box" %)
... ... @@ -139,27 +139,21 @@
139 139  Above scripts are store in /etc/lora/decoder/. User can put their scripts here and select it in the UI.
140 140  
141 141  
142 -
143 143  === 2.2.2 How to Decode My End Node ===
144 144  
128 +1/ Configure the ABP keys for your end node in the gateway. enable ABP decode in Web UI
145 145  
146 -**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.
147 147  
148 -**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
149 149  
150 -**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:
151 151  
152 -**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:
153 -
154 154  {{{/etc/lora/decoder/Dragino_LHT65 END_NODE_DEV_ADDR
155 155  }}}
156 156  
157 -**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:
158 158  
159 -
160 -(% style="color:red" %)
161 -**Some notice:**
162 -
163 163  * RSSI and SNR are added when gateway receive the packet, so there is always this field.
164 164  * If you rename the file, please make it executable.
165 165  * See this link for lua.bit module: [[http:~~/~~/luaforge.net/projects/bit/>>url:http://luaforge.net/projects/bit/]]
... ... @@ -170,7 +170,6 @@
170 170  
171 171  == 2.2 Downstream ==
172 172  
173 -
174 174  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
175 175  
176 176  The file should use below format:
... ... @@ -181,31 +181,29 @@
181 181  
182 182  (% style="color:#037691" %)**dev_addr,imme/time,txt/hex,payload,txpw,txbw,SF,frequency,rxwindow**
183 183  
184 -* **dev_addr:** Inptu the device address
185 -* **imme/time:**
161 +* dev_addr: Inptu the device address
162 +* imme/time:
186 186  ** imme: send downstream immediately,For Class C end node.
187 187  ** time: send downstream after receive device's uplink. For Class A end node
188 -* **txt/hex:**
165 +* txt/hex:
189 189  ** txt: send payload in ASCII
190 190  ** hex: send payload in HEX
191 -* **payload: **payload to be sent, payload lenght should match the LoRaWAN protocol requirement.
192 -* **txpw:** Transmit Power. example: 20
193 -* **txbw:** bandwidth:
168 +* payload: payload to be sent, payload lenght should match the LoRaWAN protocol requirement.
169 +* txpw: Transmit Power. example: 20
170 +* txbw: bandwidth:
194 194  ** 1: 500 kHz
195 195  ** 2: 250 kHz
196 196  ** 3: 125 kHz
197 197  ** 4: 62.5 kHz
198 -* **SF:** Spreading Factor : SF7/SF8/SF9/SF10/SF11/SF12
199 -* **Frequency:** Transmit Frequency: example: 923300000
200 -* **rxwindow:** transmit on Rx1Window or Rx2Window.
175 +* SF: Spreading Factor : SF7/SF8/SF9/SF10/SF11/SF12
176 +* Frequency: Transmit Frequency: example: 923300000
177 +* rxwindow: transmit on Rx1Window or Rx2Window.
201 201  
179 +Completely exmaple:
202 202  
203 -(% style="color:blue" %)**Completely exmaple:**
181 +* Old version: echo 018193F4,imme,hex,0101 > /var/iot/push/test
182 +* New version: echo 018193F4,imme,hex,0101,20,1,SF12,923300000,2 > /var/iot/push/test
204 204  
205 -* **Old version:** echo 018193F4,imme,hex,0101 > /var/iot/push/test
206 -* **New version:** echo 018193F4,imme,hex,0101,20,1,SF12,923300000,2 > /var/iot/push/test
207 -
208 -
209 209  (% style="color:#037691" %)**Downstream Frequency**
210 210  
211 211  The LG308 will use the RX2 window info to send the downstream payload, use the default LoRaWAN settings, as below:
... ... @@ -219,7 +219,6 @@
219 219  * IN865: 866.55Mhz, SF10 BW125
220 220  * RU864: 869.1Mhz, SF12 BW125
221 221  
222 -
223 223  (% style="color:#037691" %)**Examples:**
224 224  
225 225  (% class="box" %)
... ... @@ -226,20 +226,26 @@
226 226  (((
227 227  we can use echo command to create files in LG308 for downstream.
228 228  root@dragino-1d25dc:~~# echo 2602111D,time,hex,12345678 > /var/iot/push/test
203 +)))
229 229  
230 -
231 -**1)** From logread -f of gateway, we can see it has been added as pedning.
205 +(% class="box" %)
206 +(((
207 +1) From logread -f of gateway, we can see it has been added as pedning.
232 232  lora_pkt_fwd[4286]: INFO~~ [DNLK]Looking file : test
233 233  lora_pkt_fwd[4286]: INFO~~ [DNLK]devaddr:2602111D, txmode:time, pdfm:hex, size:4, payload1:4Vx,payload_hex:77C1BB90
234 234  lora_pkt_fwd[4286]: INFO~~ [DNLK] DNLINK PENDING!(1 elems).
211 +)))
235 235  
236 -
237 -**2)** When there is an upstrea from end node, this downstream will be sent and shows:
213 +(% class="box" %)
214 +(((
215 +2) When there is an upstrea from end node, this downstream will be sent and shows:
238 238  lora_pkt_fwd[4286]: INFO: tx_start_delay=1497 (1497.000000) - (1497, bw_delay=0.000000, notch_delay=0.000000)
239 239  lora_pkt_fwd[4286]: [LGWSEND]lgw_send done: count_us=3537314420, freq=923300000, size=17
218 +)))
240 240  
241 -
242 -**3)** and the end node will got:
220 +(% class="box" %)
221 +(((
222 +3) and the end node will got:
243 243  [5764825]~*~*~*~** UpLinkCounter= 98 ~*~*~*~**
244 244  [5764827]TX on freq 905300000 Hz at DR 0
245 245  Update Interval: 60000 ms
... ... @@ -251,9 +251,11 @@
251 251  Rssi= -41
252 252  Receive data
253 253  (% style="color:#037691" %)**2:12345678**  (%%) ~-~-> Hex
234 +)))
254 254  
255 -
256 -**4) **If we use the command "echo 2602111D,time,txt,12345678 > /var/iot/push/test" for downstream, the end node will got:
236 +(% class="box" %)
237 +(((
238 +4) If we use the command "echo 2602111D,time,txt,12345678 > /var/iot/push/test" for downstream, the end node will got:
257 257  [5955877]~*~*~*~** UpLinkCounter= 102 ~*~*~*~**
258 258  [5955879]TX on freq 904100000 Hz at DR 0
259 259  Update Interval: 60000 ms
... ... @@ -270,12 +270,11 @@
270 270  
271 271  = 3. Example 1: Communicate with LT-22222-L =
272 272  
273 -
274 274  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]]
275 275  
276 276  (% class="box" %)
277 277  (((
278 -//#!/bin/sh
259 +#!/bin/sh
279 279  # This scripts shows how to use LPS8/LG308/DLOS8 to communicate with two LoRaWAN End Nodes, without the use of internet or LoRaWAN server
280 280  #
281 281  # Hardware Prepare:
... ... @@ -308,37 +308,35 @@
308 308  #  Device1: DI1: ON, DI2: ON , DO1: ON,  DO2: ON
309 309  #  Device2: DI1: OFF, DI2: OFF , DO1: ON,  DO2: ON
310 310  #  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
311 -#  whether the Device 2 has been changed.//
292 +#  whether the Device 2 has been changed.
312 312  )))
313 313  
295 +~1. Input keys
314 314  
315 -**~1. Input keys**
316 -
317 317  [[image:image-20220527162450-3.png]]
318 318  
319 319  Input Keys in LPS8
320 320  
321 321  
322 -**2. Make sure the LPS8 and LT use the same frequency bands, choose EU868 in this test.**
302 +2. Make sure the LPS8 and LT use the same frequency bands, choose EU868 in this test.
323 323  
304 +3. Choose Built-in server
324 324  
325 -**3. Choose Built-in server**
326 -
327 327  [[image:image-20220527162518-4.png]]
328 328  
329 329  Choose Built-in server
330 330  
331 331  
332 -**4. Run the script.**
311 +4. Run the script.
333 333  
334 -[[image:image-20220722115213-2.png]]
313 +[[image:image-20220527162552-5.png]]
335 335  
336 336  Run the script
337 337  
338 338  
339 -**5. Output:**
318 +5. Output:
340 340  
341 -[[image:image-20220722115133-1.png]]
320 +[[image:image-20220527162619-6.png]]
342 342  
343 343  Output from LPS8
344 344  
... ... @@ -345,7 +345,6 @@
345 345  
346 346  = 4. Example 2: Communicate to TCP Server =
347 347  
348 -
349 349  [[image:image-20220527162648-7.png]]
350 350  
351 351  Network Structure
... ... @@ -359,7 +359,6 @@
359 359  
360 360  (% style="color:red" %)**Note: Firmware version must be higher than lgw-5.4.1607519907**
361 361  
362 -
363 363  Assume we already set up ABP keys in the gateway:
364 364  
365 365  [[image:image-20220527162852-8.png]]
... ... @@ -367,9 +367,8 @@
367 367  Input Keys in LPS8
368 368  
369 369  
347 +run socket tool in PC
370 370  
371 -**run socket tool in PC**
372 -
373 373  [[image:image-20220527163028-9.png]]
374 374  
375 375  
... ... @@ -376,20 +376,17 @@
376 376  Socket tool
377 377  
378 378  
355 +Input Server address and port
379 379  
380 -**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"]]
381 381  
382 -[[image:image-20220527163106-10.png]]
383 -
384 384  Input Server address and port
385 385  
386 386  
362 +See value receive in socket tool. :
387 387  
388 -**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"]]
389 389  
390 -[[image:image-20220527163144-11.png]]
391 -
392 392  value receive in socket tool
393 393  
394 -
395 395  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-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

Applications

Navigation

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