Last modified by Xiaoling on 2023/04/20 18:14
<
From version < 3.8 >
edited by Xiaoling
on 2022/05/27 16:23
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:
... ... @@ -18,6 +18,7 @@
18 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 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  
23 +
21 21  = 2. How it works =
22 22  
23 23  
... ... @@ -28,13 +28,15 @@
28 28  
29 29  (% class="box infomessage" %)
30 30  (((
31 -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
32 32  AT+APPSKEY=b3 17 f8 14 7a 43 27 8a 6a 31 c4 47 3d 55 5d 33
33 -AT+DADDR=2602111D
36 +AT+DADDR=2602111D**
34 34  )))
35 35  
36 36  (((
37 37  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 +
38 38  )))
39 39  
40 40  We need to input above keys in LG308 and enable ABP decryption.
... ... @@ -46,6 +46,7 @@
46 46  
47 47  == 2.1 Upstream ==
48 48  
54 +
49 49  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.
50 50  
51 51  (((
... ... @@ -54,7 +54,7 @@
54 54  
55 55  [[image:image-20220527161149-2.png]]
56 56  
57 -LG308 log by "logread -f" command
63 +LG308 log by "(% style="color:red" %)**logread -f**" (%%)command
58 58  
59 59  
60 60  The data of End Node is stored in the file /var/iot/channels/2602111D. We can use hexdump command to check it.
... ... @@ -67,9 +67,9 @@
67 67  000001c
68 68  )))
69 69  
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
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
73 73  
74 74  (% class="box" %)
75 75  (((
... ... @@ -83,12 +83,13 @@
83 83  
84 84  (% class="box" %)
85 85  (((
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.
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.
87 87  )))
88 88  
89 89  
90 90  === 2.2.1 Decode Method ===
91 91  
98 +
92 92  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.
93 93  
94 94  For example we have a LHT65 , works in ABP mode and gateway successful get the data, which are:
... ... @@ -101,6 +101,7 @@
101 101  000001c
102 102  )))
103 103  
111 +
104 104  If we choose ASCII decoder, the MQTT process will send out with mqtt-data:
105 105  
106 106  (% class="box" %)
... ... @@ -110,6 +110,7 @@
110 110  Sun Sep 27 04:33:16 2020 user.notice root: [IoT.MQTT]:mqtt_data[-m]: (% style="color:#037691" %)**ffffffe700000048ccd17fff7fff017fff7fff00**
111 111  )))
112 112  
121 +
113 113  If we choose Decode_LHT65, the MQTT process will send out with mqtt-data
114 114  
115 115  (% class="box" %)
... ... @@ -123,21 +123,27 @@
123 123  Above scripts are store in /etc/lora/decoder/. User can put their scripts here and select it in the UI.
124 124  
125 125  
135 +
126 126  === 2.2.2 How to Decode My End Node ===
127 127  
128 -1/ Configure the ABP keys for your end node in the gateway. enable ABP decode in Web UI
129 129  
130 -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
131 131  
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
141 +**2. **Don't choose MQTT service, use LoRaWAN.
133 133  
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:
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
135 135  
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 +
136 136  {{{/etc/lora/decoder/Dragino_LHT65 END_NODE_DEV_ADDR
137 137  }}}
138 138  
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:
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.
140 140  
152 +
153 +(% style="color:red" %)
154 +**Some notice:**
155 +
141 141  * RSSI and SNR are added when gateway receive the packet, so there is always this field.
142 142  * If you rename the file, please make it executable.
143 143  * See this link for lua.bit module: [[http:~~/~~/luaforge.net/projects/bit/>>url:http://luaforge.net/projects/bit/]]
... ... @@ -145,8 +145,11 @@
145 145  * the last line return is what will be used for MQTT
146 146  * User can use other language ,not limited to Lua, just make sure the return is what you want to send.
147 147  
163 +
164 +
148 148  == 2.2 Downstream ==
149 149  
167 +
150 150  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
151 151  
152 152  The file should use below format:
... ... @@ -157,30 +157,29 @@
157 157  
158 158  (% style="color:#037691" %)**dev_addr,imme/time,txt/hex,payload,txpw,txbw,SF,frequency,rxwindow**
159 159  
160 -* dev_addr: Inptu the device address
161 -* imme/time:
178 +* **dev_addr:** Inptu the device address
179 +* **imme/time:**
162 162  ** imme: send downstream immediately,For Class C end node.
163 163  ** time: send downstream after receive device's uplink. For Class A end node
164 -* txt/hex:
182 +* **txt/hex:**
165 165  ** txt: send payload in ASCII
166 166  ** hex: send payload in HEX
167 -* payload: payload to be sent, payload lenght should match the LoRaWAN protocol requirement.
168 -* txpw: Transmit Power. example: 20
169 -* 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:
170 170  ** 1: 500 kHz
171 171  ** 2: 250 kHz
172 172  ** 3: 125 kHz
173 173  ** 4: 62.5 kHz
174 -* SF: Spreading Factor : SF7/SF8/SF9/SF10/SF11/SF12
175 -* Frequency: Transmit Frequency: example: 923300000
176 -* 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.
177 177  
178 -Completely exmaple:
196 +(% style="color:blue" %)**Completely exmaple:**
179 179  
180 -* Old version: echo 018193F4,imme,hex,0101 > /var/iot/push/test
181 -* 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
182 182  
183 -
184 184  (% style="color:#037691" %)**Downstream Frequency**
185 185  
186 186  The LG308 will use the RX2 window info to send the downstream payload, use the default LoRaWAN settings, as below:
... ... @@ -194,7 +194,6 @@
194 194  * IN865: 866.55Mhz, SF10 BW125
195 195  * RU864: 869.1Mhz, SF12 BW125
196 196  
197 -
198 198  (% style="color:#037691" %)**Examples:**
199 199  
200 200  (% class="box" %)
... ... @@ -205,7 +205,7 @@
205 205  
206 206  (% class="box" %)
207 207  (((
208 -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.
209 209  lora_pkt_fwd[4286]: INFO~~ [DNLK]Looking file : test
210 210  lora_pkt_fwd[4286]: INFO~~ [DNLK]devaddr:2602111D, txmode:time, pdfm:hex, size:4, payload1:4Vx,payload_hex:77C1BB90
211 211  lora_pkt_fwd[4286]: INFO~~ [DNLK] DNLINK PENDING!(1 elems).
... ... @@ -213,7 +213,7 @@
213 213  
214 214  (% class="box" %)
215 215  (((
216 -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:
217 217  lora_pkt_fwd[4286]: INFO: tx_start_delay=1497 (1497.000000) - (1497, bw_delay=0.000000, notch_delay=0.000000)
218 218  lora_pkt_fwd[4286]: [LGWSEND]lgw_send done: count_us=3537314420, freq=923300000, size=17
219 219  )))
... ... @@ -220,7 +220,7 @@
220 220  
221 221  (% class="box" %)
222 222  (((
223 -3) and the end node will got:
239 +**3)** and the end node will got:
224 224  [5764825]~*~*~*~** UpLinkCounter= 98 ~*~*~*~**
225 225  [5764827]TX on freq 905300000 Hz at DR 0
226 226  Update Interval: 60000 ms
... ... @@ -236,7 +236,7 @@
236 236  
237 237  (% class="box" %)
238 238  (((
239 -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:
240 240  [5955877]~*~*~*~** UpLinkCounter= 102 ~*~*~*~**
241 241  [5955879]TX on freq 904100000 Hz at DR 0
242 242  Update Interval: 60000 ms
... ... @@ -253,11 +253,12 @@
253 253  
254 254  = 3. Example 1: Communicate with LT-22222-L =
255 255  
272 +
256 256  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]]
257 257  
258 258  (% class="box" %)
259 259  (((
260 -#!/bin/sh
277 +//#!/bin/sh
261 261  # This scripts shows how to use LPS8/LG308/DLOS8 to communicate with two LoRaWAN End Nodes, without the use of internet or LoRaWAN server
262 262  #
263 263  # Hardware Prepare:
... ... @@ -290,40 +290,44 @@
290 290  #  Device1: DI1: ON, DI2: ON , DO1: ON,  DO2: ON
291 291  #  Device2: DI1: OFF, DI2: OFF , DO1: ON,  DO2: ON
292 292  #  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
293 -#  whether the Device 2 has been changed.
310 +#  whether the Device 2 has been changed.//
294 294  )))
295 295  
296 -~1. Input keys
313 +**~1. Input keys**
297 297  
298 -[[image:https://wiki.dragino.com/images/thumb/b/bf/LPS8_LT-22222_1.png/600px-LPS8_LT-22222_1.png||height="335" width="600"]]
315 +[[image:image-20220527162450-3.png]]
299 299  
300 300  Input Keys in LPS8
301 301  
302 -2. Make sure the LPS8 and LT use the same frequency bands, choose EU868 in this test.
303 303  
304 -3. Choose Built-in server
320 +**2. Make sure the LPS8 and LT use the same frequency bands, choose EU868 in this test.**
305 305  
306 -[[image:https://wiki.dragino.com/images/thumb/d/d7/LPS8_LT-22222_2.png/600px-LPS8_LT-22222_2.png||height="264" width="600"]]
322 +**3. Choose Built-in server**
307 307  
324 +[[image:image-20220527162518-4.png]]
325 +
308 308  Choose Built-in server
309 309  
310 -4. Run the script.
311 311  
312 -[[image:https://wiki.dragino.com/images/thumb/3/39/LPS8_LT-22222_3.png/600px-LPS8_LT-22222_3.png||height="389" width="600"]]
329 +**4. Run the script.**
313 313  
331 +[[image:image-20220527162552-5.png]]
332 +
314 314  Run the script
315 315  
316 -5. Output:
317 317  
318 -[[image:https://wiki.dragino.com/images/thumb/f/fe/LPS8_LT-22222_4.png/600px-LPS8_LT-22222_4.png||height="433" width="600"]]
336 +**5. Output:**
319 319  
338 +[[image:image-20220527162619-6.png]]
339 +
320 320  Output from LPS8
321 321  
322 322  
323 323  = 4. Example 2: Communicate to TCP Server =
324 324  
325 -[[image:https://wiki.dragino.com/images/thumb/7/75/LPS8_TCP_0.png/600px-LPS8_TCP_0.png||height="370" width="600"]]
326 326  
346 +[[image:image-20220527162648-7.png]]
347 +
327 327  Network Structure
328 328  
329 329  
... ... @@ -330,34 +330,42 @@
330 330  Full instruction video inlcude how to write scripts to fit server needed is here:
331 331  
332 332  
333 -(% class="mark" %)**Video Instruction**: [[https:~~/~~/youtu.be/-nevW6U2TsE>>url:https://youtu.be/-nevW6U2TsE]]
354 +(% style="color:#037691" %)**Video Instruction**(%%): **[[https:~~/~~/youtu.be/-nevW6U2TsE>>url:https://youtu.be/-nevW6U2TsE]]**
334 334  
335 -(% class="mark" %)**Note: Firmware version must be higher than lgw-5.4.1607519907**
336 336  
357 +(% style="color:red" %)**Note: Firmware version must be higher than lgw-5.4.1607519907**
358 +
359 +
337 337  Assume we already set up ABP keys in the gateway:
338 338  
339 -[[image:https://wiki.dragino.com/images/thumb/b/bf/LPS8_LT-22222_1.png/600px-LPS8_LT-22222_1.png||height="335" width="600"]]
362 +[[image:image-20220527162852-8.png]]
340 340  
341 341  Input Keys in LPS8
342 342  
343 -run socket tool in PC
344 344  
345 -[[image:https://wiki.dragino.com/images/thumb/4/4b/LPS8_TCP_2.png/600px-LPS8_TCP_2.png||height="212" width="600"]]
346 346  
368 +**run socket tool in PC**
369 +
370 +[[image:image-20220527163028-9.png]]
371 +
372 +
347 347  Socket tool
348 348  
349 349  
350 -Input Server address and port
351 351  
352 -[[image:https://wiki.dragino.com/images/thumb/c/c6/LPS8_TCP_3.png/600px-LPS8_TCP_3.png||height="306" width="600"]]
377 +**Input Server address and port**
353 353  
379 +[[image:image-20220527163106-10.png]]
380 +
354 354  Input Server address and port
355 355  
356 356  
357 -See value receive in socket tool. :
358 358  
359 -[[image:https://wiki.dragino.com/images/thumb/2/20/LPS8_TCP_4.png/600px-LPS8_TCP_4.png||height="219" width="600"]]
385 +**See value receive in socket tool:**
360 360  
387 +[[image:image-20220527163144-11.png]]
388 +
361 361  value receive in socket tool
362 362  
391 +
363 363  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-20220527162450-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +125.4 KB
Content
image-20220527162518-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +72.8 KB
Content
image-20220527162552-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +33.6 KB
Content
image-20220527162619-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +41.0 KB
Content
image-20220527162648-7.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +151.7 KB
Content
image-20220527162852-8.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +125.6 KB
Content
image-20220527163028-9.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +32.9 KB
Content
image-20220527163106-10.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +34.5 KB
Content
image-20220527163144-11.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +107.7 KB
Content

Applications

Navigation

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