Last modified by Xiaoling on 2023/04/20 18:14
<
From version < 14.5 >
edited by Xiaoling
on 2022/06/01 11:12
To version < 19.2 >
edited by Xiaoling
on 2022/09/17 16:42
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,15 +1,19 @@
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 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>>MQTT Forward Instruction]]).
12 12  
15 +
16 +
13 13  (((
14 14  The basic of this feature is the decoding of (% style="color:red" %)**LoRaWAN ABP End Node**(%%). Requirements:
15 15  )))
... ... @@ -20,6 +20,7 @@
20 20  
21 21  
22 22  
27 +
23 23  = 2. How it works =
24 24  
25 25  
... ... @@ -30,35 +30,45 @@
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
38 +**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
40 +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.
45 +
46 +
40 40  )))
41 41  
42 42  We need to input above keys in LG308 and enable ABP decryption.
43 43  
51 +
44 44  [[image:image-20220527161119-1.png]]
45 45  
54 +
46 46  Input the ABP keys in LG308
47 47  
48 48  
58 +
49 49  == 2.1 Upstream ==
50 50  
61 +
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  (((
54 -We can see the log of LG308 to know this packet arrive
65 +We can see the log of LG308 to know this packet arrive.
66 +
67 +
55 55  )))
56 56  
57 57  [[image:image-20220527161149-2.png]]
58 58  
59 -LG308 log by "logread -f" command
60 60  
73 +LG308 log by "(% style="color:red" %)**logread -f**" (%%)command
61 61  
75 +
76 +
62 62  The data of End Node is stored in the file /var/iot/channels/2602111D. We can use hexdump command to check it.
63 63  
64 64  (% class="box" %)
... ... @@ -69,10 +69,12 @@
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
87 +* **RSSI**: 4646 4646 4646 3946 = 0xFFFF FF9F : So RSSI = (0xFFFF FF9F - 0x100000000) = -97
88 +* **SNR**: 3030 3030 3030 3546 = 0x0000 005F = 95, need to divide 10 so SNR is 9.5
89 +* **Payload**: 0xcc0c 0b63 0266 017f ff7f ff00
75 75  
91 +
92 +
76 76  (% class="box" %)
77 77  (((
78 78  (% 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:
... ... @@ -83,14 +83,17 @@
83 83  000001c
84 84  )))
85 85  
103 +
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.
106 +(% 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  
110 +
92 92  === 2.2.1 Decode Method ===
93 93  
113 +
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  
126 +
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  
136 +
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  
150 +
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.
154 +**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
156 +**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:
158 +**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  
160 +**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:
161 +
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:
165 +**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  
167 +
168 +(% style="color:red" %)
169 +**Some notice:**
170 +
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/]]
... ... @@ -148,8 +148,11 @@
148 148  * User can use other language ,not limited to Lua, just make sure the return is what you want to send.
149 149  
150 150  
179 +
180 +
151 151  == 2.2 Downstream ==
152 152  
183 +
153 153  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
154 154  
155 155  The file should use below format:
... ... @@ -156,35 +156,40 @@
156 156  
157 157  (% style="color:#037691" %)**dev_addr,imme/time,txt/hex,payload**
158 158  
190 +
159 159  Since fimware > Dragino-v2 lgw-5.4.1608518541 . Support more option
160 160  
161 161  (% style="color:#037691" %)**dev_addr,imme/time,txt/hex,payload,txpw,txbw,SF,frequency,rxwindow**
162 162  
163 -* dev_addr: Inptu the device address
164 -* imme/time:
195 +* **dev_addr:** Inptu the device address
196 +* **imme/time:**
165 165  ** imme: send downstream immediately,For Class C end node.
166 166  ** time: send downstream after receive device's uplink. For Class A end node
167 -* txt/hex:
199 +* **txt/hex:**
168 168  ** txt: send payload in ASCII
169 169  ** hex: send payload in HEX
170 -* payload: payload to be sent, payload lenght should match the LoRaWAN protocol requirement.
171 -* txpw: Transmit Power. example: 20
172 -* txbw: bandwidth:
202 +* **payload: **payload to be sent, payload lenght should match the LoRaWAN protocol requirement.
203 +* **txpw:** Transmit Power. example: 20
204 +* **txbw:** bandwidth:
173 173  ** 1: 500 kHz
174 174  ** 2: 250 kHz
175 175  ** 3: 125 kHz
176 176  ** 4: 62.5 kHz
177 -* SF: Spreading Factor : SF7/SF8/SF9/SF10/SF11/SF12
178 -* Frequency: Transmit Frequency: example: 923300000
179 -* rxwindow: transmit on Rx1Window or Rx2Window.
209 +* **SF:** Spreading Factor : SF7/SF8/SF9/SF10/SF11/SF12
210 +* **Frequency:** Transmit Frequency: example: 923300000
211 +* **rxwindow:** transmit on Rx1Window or Rx2Window.
180 180  
181 -Completely exmaple:
182 182  
183 -* Old version: echo 018193F4,imme,hex,0101 > /var/iot/push/test
184 -* New version: echo 018193F4,imme,hex,0101,20,1,SF12,923300000,2 > /var/iot/push/test
185 185  
186 -(% style="color:#037691" %)**Downstream Frequency**
215 +(% style="color:blue" %)**Completely exmaple:**
187 187  
217 +* **Old version:** echo 018193F4,imme,hex,0101 > /var/iot/push/test
218 +* **New version:** echo 018193F4,imme,hex,0101,20,1,SF12,923300000,2 > /var/iot/push/test
219 +
220 +
221 +
222 +(% style="color:#037691" %)**Downstream Frequency:**
223 +
188 188  The LG308 will use the RX2 window info to send the downstream payload, use the default LoRaWAN settings, as below:
189 189  
190 190  * EU868: 869.525Mhz, DR0(SF12BW125)
... ... @@ -196,6 +196,8 @@
196 196  * IN865: 866.55Mhz, SF10 BW125
197 197  * RU864: 869.1Mhz, SF12 BW125
198 198  
235 +
236 +
199 199  (% style="color:#037691" %)**Examples:**
200 200  
201 201  (% class="box" %)
... ... @@ -202,26 +202,20 @@
202 202  (((
203 203  we can use echo command to create files in LG308 for downstream.
204 204  root@dragino-1d25dc:~~# echo 2602111D,time,hex,12345678 > /var/iot/push/test
205 -)))
206 206  
207 -(% class="box" %)
208 -(((
209 -1) From logread -f of gateway, we can see it has been added as pedning.
244 +
245 +**1)** From logread -f of gateway, we can see it has been added as pedning.
210 210  lora_pkt_fwd[4286]: INFO~~ [DNLK]Looking file : test
211 211  lora_pkt_fwd[4286]: INFO~~ [DNLK]devaddr:2602111D, txmode:time, pdfm:hex, size:4, payload1:4Vx,payload_hex:77C1BB90
212 212  lora_pkt_fwd[4286]: INFO~~ [DNLK] DNLINK PENDING!(1 elems).
213 -)))
214 214  
215 -(% class="box" %)
216 -(((
217 -2) When there is an upstrea from end node, this downstream will be sent and shows:
250 +
251 +**2)** When there is an upstrea from end node, this downstream will be sent and shows:
218 218  lora_pkt_fwd[4286]: INFO: tx_start_delay=1497 (1497.000000) - (1497, bw_delay=0.000000, notch_delay=0.000000)
219 219  lora_pkt_fwd[4286]: [LGWSEND]lgw_send done: count_us=3537314420, freq=923300000, size=17
220 -)))
221 221  
222 -(% class="box" %)
223 -(((
224 -3) and the end node will got:
255 +
256 +**3)** and the end node will got:
225 225  [5764825]~*~*~*~** UpLinkCounter= 98 ~*~*~*~**
226 226  [5764827]TX on freq 905300000 Hz at DR 0
227 227  Update Interval: 60000 ms
... ... @@ -233,11 +233,9 @@
233 233  Rssi= -41
234 234  Receive data
235 235  (% style="color:#037691" %)**2:12345678**  (%%) ~-~-> Hex
236 -)))
237 237  
238 -(% class="box" %)
239 -(((
240 -4) If we use the command "echo 2602111D,time,txt,12345678 > /var/iot/push/test" for downstream, the end node will got:
269 +
270 +**4) **If we use the command "echo 2602111D,time,txt,12345678 > /var/iot/push/test" for downstream, the end node will got:
241 241  [5955877]~*~*~*~** UpLinkCounter= 102 ~*~*~*~**
242 242  [5955879]TX on freq 904100000 Hz at DR 0
243 243  Update Interval: 60000 ms
... ... @@ -252,13 +252,15 @@
252 252  )))
253 253  
254 254  
285 +
255 255  = 3. Example 1: Communicate with LT-22222-L =
256 256  
288 +
257 257  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]]
258 258  
259 259  (% class="box" %)
260 260  (((
261 -#!/bin/sh
293 +//#!/bin/sh
262 262  # This scripts shows how to use LPS8/LG308/DLOS8 to communicate with two LoRaWAN End Nodes, without the use of internet or LoRaWAN server
263 263  #
264 264  # Hardware Prepare:
... ... @@ -291,41 +291,52 @@
291 291  #  Device1: DI1: ON, DI2: ON , DO1: ON,  DO2: ON
292 292  #  Device2: DI1: OFF, DI2: OFF , DO1: ON,  DO2: ON
293 293  #  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
294 -#  whether the Device 2 has been changed.
326 +#  whether the Device 2 has been changed.//
295 295  )))
296 296  
297 -~1. Input keys
298 298  
330 +(% style="color:blue" %)**1. Input keys**
331 +
332 +
299 299  [[image:image-20220527162450-3.png]]
300 300  
301 301  Input Keys in LPS8
302 302  
303 303  
304 -2. Make sure the LPS8 and LT use the same frequency bands, choose EU868 in this test.
305 305  
306 -3. Choose Built-in server
339 +(% style="color:blue" %)**2. Make sure the LPS8 and LT use the same frequency bands, choose EU868 in this test.**
307 307  
341 +
342 +(% style="color:blue" %)**3. Choose Built-in server**
343 +
344 +
308 308  [[image:image-20220527162518-4.png]]
309 309  
310 310  Choose Built-in server
311 311  
312 312  
313 -4. Run the script.
314 314  
315 -[[image:image-20220527162552-5.png]]
351 +(% style="color:blue" %)**4. Run the script.**
316 316  
353 +
354 +[[image:image-20220722115213-2.png]]
355 +
317 317  Run the script
318 318  
319 319  
320 -5. Output:
321 321  
322 -[[image:image-20220527162619-6.png]]
360 +(% style="color:blue" %)**5. Output:**
323 323  
362 +
363 +[[image:image-20220722115133-1.png]]
364 +
324 324  Output from LPS8
325 325  
326 326  
368 +
327 327  = 4. Example 2: Communicate to TCP Server =
328 328  
371 +
329 329  [[image:image-20220527162648-7.png]]
330 330  
331 331  Network Structure
... ... @@ -339,6 +339,7 @@
339 339  
340 340  (% style="color:red" %)**Note: Firmware version must be higher than lgw-5.4.1607519907**
341 341  
385 +
342 342  Assume we already set up ABP keys in the gateway:
343 343  
344 344  [[image:image-20220527162852-8.png]]
... ... @@ -346,8 +346,10 @@
346 346  Input Keys in LPS8
347 347  
348 348  
349 -run socket tool in PC
350 350  
394 +(% style="color:blue" %)**run socket tool in PC**
395 +
396 +
351 351  [[image:image-20220527163028-9.png]]
352 352  
353 353  
... ... @@ -354,17 +354,22 @@
354 354  Socket tool
355 355  
356 356  
357 -Input Server address and port
358 358  
404 +(% style="color:blue" %)**Input Server address and port**
405 +
406 +
359 359  [[image:image-20220527163106-10.png]]
360 360  
361 361  Input Server address and port
362 362  
363 363  
364 -See value receive in socket tool. :
365 365  
413 +(% style="color:blue" %)**See value receive in socket tool:**
414 +
415 +
366 366  [[image:image-20220527163144-11.png]]
367 367  
368 368  value receive in socket tool
369 369  
420 +
370 370  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-20220722115133-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +35.1 KB
Content
image-20220722115213-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +27.7 KB
Content

Applications

Navigation

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