<
From version < 18.2 >
edited by Xiaoling
on 2022/07/22 11:52
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,7 +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 24  = 2. How it works =
25 25  
26 26  
... ... @@ -31,15 +31,13 @@
31 31  
32 32  (% class="box infomessage" %)
33 33  (((
34 -**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
35 35  AT+APPSKEY=b3 17 f8 14 7a 43 27 8a 6a 31 c4 47 3d 55 5d 33
36 -AT+DADDR=2602111D**
33 +AT+DADDR=2602111D
37 37  )))
38 38  
39 39  (((
40 40  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 -
43 43  )))
44 44  
45 45  We need to input above keys in LG308 and enable ABP decryption.
... ... @@ -51,7 +51,6 @@
51 51  
52 52  == 2.1 Upstream ==
53 53  
54 -
55 55  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.
56 56  
57 57  (((
... ... @@ -60,7 +60,7 @@
60 60  
61 61  [[image:image-20220527161149-2.png]]
62 62  
63 -LG308 log by "(% style="color:red" %)**logread -f**" (%%)command
57 +LG308 log by "logread -f" command
64 64  
65 65  
66 66  The data of End Node is stored in the file /var/iot/channels/2602111D. We can use hexdump command to check it.
... ... @@ -73,11 +73,10 @@
73 73  000001c
74 74  )))
75 75  
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
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
79 79  
80 -
81 81  (% class="box" %)
82 82  (((
83 83  (% 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:
... ... @@ -90,13 +90,12 @@
90 90  
91 91  (% class="box" %)
92 92  (((
93 -(% 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.
94 94  )))
95 95  
96 96  
97 97  === 2.2.1 Decode Method ===
98 98  
99 -
100 100  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.
101 101  
102 102  For example we have a LHT65 , works in ABP mode and gateway successful get the data, which are:
... ... @@ -109,7 +109,6 @@
109 109  000001c
110 110  )))
111 111  
112 -
113 113  If we choose ASCII decoder, the MQTT process will send out with mqtt-data:
114 114  
115 115  (% class="box" %)
... ... @@ -119,7 +119,6 @@
119 119  Sun Sep 27 04:33:16 2020 user.notice root: [IoT.MQTT]:mqtt_data[-m]: (% style="color:#037691" %)**ffffffe700000048ccd17fff7fff017fff7fff00**
120 120  )))
121 121  
122 -
123 123  If we choose Decode_LHT65, the MQTT process will send out with mqtt-data
124 124  
125 125  (% class="box" %)
... ... @@ -133,27 +133,21 @@
133 133  Above scripts are store in /etc/lora/decoder/. User can put their scripts here and select it in the UI.
134 134  
135 135  
136 -
137 137  === 2.2.2 How to Decode My End Node ===
138 138  
128 +1/ Configure the ABP keys for your end node in the gateway. enable ABP decode in Web UI
139 139  
140 -**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.
141 141  
142 -**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
143 143  
144 -**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:
145 145  
146 -**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:
147 -
148 148  {{{/etc/lora/decoder/Dragino_LHT65 END_NODE_DEV_ADDR
149 149  }}}
150 150  
151 -**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:
152 152  
153 -
154 -(% style="color:red" %)
155 -**Some notice:**
156 -
157 157  * RSSI and SNR are added when gateway receive the packet, so there is always this field.
158 158  * If you rename the file, please make it executable.
159 159  * See this link for lua.bit module: [[http:~~/~~/luaforge.net/projects/bit/>>url:http://luaforge.net/projects/bit/]]
... ... @@ -162,10 +162,8 @@
162 162  * User can use other language ,not limited to Lua, just make sure the return is what you want to send.
163 163  
164 164  
165 -
166 166  == 2.2 Downstream ==
167 167  
168 -
169 169  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
170 170  
171 171  The file should use below format:
... ... @@ -176,33 +176,29 @@
176 176  
177 177  (% style="color:#037691" %)**dev_addr,imme/time,txt/hex,payload,txpw,txbw,SF,frequency,rxwindow**
178 178  
179 -* **dev_addr:** Inptu the device address
180 -* **imme/time:**
161 +* dev_addr: Inptu the device address
162 +* imme/time:
181 181  ** imme: send downstream immediately,For Class C end node.
182 182  ** time: send downstream after receive device's uplink. For Class A end node
183 -* **txt/hex:**
165 +* txt/hex:
184 184  ** txt: send payload in ASCII
185 185  ** hex: send payload in HEX
186 -* **payload: **payload to be sent, payload lenght should match the LoRaWAN protocol requirement.
187 -* **txpw:** Transmit Power. example: 20
188 -* **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:
189 189  ** 1: 500 kHz
190 190  ** 2: 250 kHz
191 191  ** 3: 125 kHz
192 192  ** 4: 62.5 kHz
193 -* **SF:** Spreading Factor : SF7/SF8/SF9/SF10/SF11/SF12
194 -* **Frequency:** Transmit Frequency: example: 923300000
195 -* **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.
196 196  
179 +Completely exmaple:
197 197  
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
198 198  
199 -(% style="color:blue" %)**Completely exmaple:**
200 -
201 -* **Old version:** echo 018193F4,imme,hex,0101 > /var/iot/push/test
202 -* **New version:** echo 018193F4,imme,hex,0101,20,1,SF12,923300000,2 > /var/iot/push/test
203 -
204 -
205 -
206 206  (% style="color:#037691" %)**Downstream Frequency**
207 207  
208 208  The LG308 will use the RX2 window info to send the downstream payload, use the default LoRaWAN settings, as below:
... ... @@ -216,8 +216,6 @@
216 216  * IN865: 866.55Mhz, SF10 BW125
217 217  * RU864: 869.1Mhz, SF12 BW125
218 218  
219 -
220 -
221 221  (% style="color:#037691" %)**Examples:**
222 222  
223 223  (% class="box" %)
... ... @@ -224,20 +224,26 @@
224 224  (((
225 225  we can use echo command to create files in LG308 for downstream.
226 226  root@dragino-1d25dc:~~# echo 2602111D,time,hex,12345678 > /var/iot/push/test
203 +)))
227 227  
228 -
229 -**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.
230 230  lora_pkt_fwd[4286]: INFO~~ [DNLK]Looking file : test
231 231  lora_pkt_fwd[4286]: INFO~~ [DNLK]devaddr:2602111D, txmode:time, pdfm:hex, size:4, payload1:4Vx,payload_hex:77C1BB90
232 232  lora_pkt_fwd[4286]: INFO~~ [DNLK] DNLINK PENDING!(1 elems).
211 +)))
233 233  
234 -
235 -**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:
236 236  lora_pkt_fwd[4286]: INFO: tx_start_delay=1497 (1497.000000) - (1497, bw_delay=0.000000, notch_delay=0.000000)
237 237  lora_pkt_fwd[4286]: [LGWSEND]lgw_send done: count_us=3537314420, freq=923300000, size=17
218 +)))
238 238  
239 -
240 -**3)** and the end node will got:
220 +(% class="box" %)
221 +(((
222 +3) and the end node will got:
241 241  [5764825]~*~*~*~** UpLinkCounter= 98 ~*~*~*~**
242 242  [5764827]TX on freq 905300000 Hz at DR 0
243 243  Update Interval: 60000 ms
... ... @@ -249,9 +249,11 @@
249 249  Rssi= -41
250 250  Receive data
251 251  (% style="color:#037691" %)**2:12345678**  (%%) ~-~-> Hex
234 +)))
252 252  
253 -
254 -**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:
255 255  [5955877]~*~*~*~** UpLinkCounter= 102 ~*~*~*~**
256 256  [5955879]TX on freq 904100000 Hz at DR 0
257 257  Update Interval: 60000 ms
... ... @@ -268,12 +268,11 @@
268 268  
269 269  = 3. Example 1: Communicate with LT-22222-L =
270 270  
271 -
272 272  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]]
273 273  
274 274  (% class="box" %)
275 275  (((
276 -//#!/bin/sh
259 +#!/bin/sh
277 277  # This scripts shows how to use LPS8/LG308/DLOS8 to communicate with two LoRaWAN End Nodes, without the use of internet or LoRaWAN server
278 278  #
279 279  # Hardware Prepare:
... ... @@ -306,37 +306,35 @@
306 306  #  Device1: DI1: ON, DI2: ON , DO1: ON,  DO2: ON
307 307  #  Device2: DI1: OFF, DI2: OFF , DO1: ON,  DO2: ON
308 308  #  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
309 -#  whether the Device 2 has been changed.//
292 +#  whether the Device 2 has been changed.
310 310  )))
311 311  
295 +~1. Input keys
312 312  
313 -**~1. Input keys**
314 -
315 315  [[image:image-20220527162450-3.png]]
316 316  
317 317  Input Keys in LPS8
318 318  
319 319  
320 -**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.
321 321  
304 +3. Choose Built-in server
322 322  
323 -**3. Choose Built-in server**
324 -
325 325  [[image:image-20220527162518-4.png]]
326 326  
327 327  Choose Built-in server
328 328  
329 329  
330 -**4. Run the script.**
311 +4. Run the script.
331 331  
332 -[[image:image-20220722115213-2.png]]
313 +[[image:image-20220527162552-5.png]]
333 333  
334 334  Run the script
335 335  
336 336  
337 -**5. Output:**
318 +5. Output:
338 338  
339 -[[image:image-20220722115133-1.png]]
320 +[[image:image-20220527162619-6.png]]
340 340  
341 341  Output from LPS8
342 342  
... ... @@ -343,7 +343,6 @@
343 343  
344 344  = 4. Example 2: Communicate to TCP Server =
345 345  
346 -
347 347  [[image:image-20220527162648-7.png]]
348 348  
349 349  Network Structure
... ... @@ -357,7 +357,6 @@
357 357  
358 358  (% style="color:red" %)**Note: Firmware version must be higher than lgw-5.4.1607519907**
359 359  
360 -
361 361  Assume we already set up ABP keys in the gateway:
362 362  
363 363  [[image:image-20220527162852-8.png]]
... ... @@ -365,9 +365,8 @@
365 365  Input Keys in LPS8
366 366  
367 367  
347 +run socket tool in PC
368 368  
369 -**run socket tool in PC**
370 -
371 371  [[image:image-20220527163028-9.png]]
372 372  
373 373  
... ... @@ -374,20 +374,17 @@
374 374  Socket tool
375 375  
376 376  
355 +Input Server address and port
377 377  
378 -**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"]]
379 379  
380 -[[image:image-20220527163106-10.png]]
381 -
382 382  Input Server address and port
383 383  
384 384  
362 +See value receive in socket tool. :
385 385  
386 -**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"]]
387 387  
388 -[[image:image-20220527163144-11.png]]
389 -
390 390  value receive in socket tool
391 391  
392 -
393 393  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
Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0