Last modified by Xiaoling on 2023/04/20 18:14
<
From version < 16.7 >
edited by Xiaoling
on 2022/07/22 11:46
To version < 8.1 >
edited by Xiaoling
on 2022/05/27 16:26
>
Change comment: Uploaded new attachment "image-20220527162648-7.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:
... ... @@ -30,15 +30,13 @@
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
31 +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**
33 +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.
40 -
41 -
42 42  )))
43 43  
44 44  We need to input above keys in LG308 and enable ABP decryption.
... ... @@ -50,7 +50,6 @@
50 50  
51 51  == 2.1 Upstream ==
52 52  
53 -
54 54  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.
55 55  
56 56  (((
... ... @@ -59,7 +59,7 @@
59 59  
60 60  [[image:image-20220527161149-2.png]]
61 61  
62 -LG308 log by "(% style="color:red" %)**logread -f**" (%%)command
57 +LG308 log by "logread -f" command
63 63  
64 64  
65 65  The data of End Node is stored in the file /var/iot/channels/2602111D. We can use hexdump command to check it.
... ... @@ -72,9 +72,9 @@
72 72  000001c
73 73  )))
74 74  
75 -* **RSSI**: 4646 4646 4646 3946 = 0xFFFF FF9F : So RSSI = (0xFFFF FF9F - 0x100000000) = -97
76 -* **SNR**: 3030 3030 3030 3546 = 0x0000 005F = 95, need to divide 10 so SNR is 9.5
77 -* **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
78 78  
79 79  (% class="box" %)
80 80  (((
... ... @@ -88,13 +88,12 @@
88 88  
89 89  (% class="box" %)
90 90  (((
91 -(% 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.
92 92  )))
93 93  
94 94  
95 95  === 2.2.1 Decode Method ===
96 96  
97 -
98 98  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.
99 99  
100 100  For example we have a LHT65 , works in ABP mode and gateway successful get the data, which are:
... ... @@ -107,7 +107,6 @@
107 107  000001c
108 108  )))
109 109  
110 -
111 111  If we choose ASCII decoder, the MQTT process will send out with mqtt-data:
112 112  
113 113  (% class="box" %)
... ... @@ -117,7 +117,6 @@
117 117  Sun Sep 27 04:33:16 2020 user.notice root: [IoT.MQTT]:mqtt_data[-m]: (% style="color:#037691" %)**ffffffe700000048ccd17fff7fff017fff7fff00**
118 118  )))
119 119  
120 -
121 121  If we choose Decode_LHT65, the MQTT process will send out with mqtt-data
122 122  
123 123  (% class="box" %)
... ... @@ -131,27 +131,21 @@
131 131  Above scripts are store in /etc/lora/decoder/. User can put their scripts here and select it in the UI.
132 132  
133 133  
134 -
135 135  === 2.2.2 How to Decode My End Node ===
136 136  
128 +1/ Configure the ABP keys for your end node in the gateway. enable ABP decode in Web UI
137 137  
138 -**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.
139 139  
140 -**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
141 141  
142 -**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:
143 143  
144 -**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 -
146 146  {{{/etc/lora/decoder/Dragino_LHT65 END_NODE_DEV_ADDR
147 147  }}}
148 148  
149 -**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:
150 150  
151 -
152 -(% style="color:red" %)
153 -**Some notice:**
154 -
155 155  * RSSI and SNR are added when gateway receive the packet, so there is always this field.
156 156  * If you rename the file, please make it executable.
157 157  * See this link for lua.bit module: [[http:~~/~~/luaforge.net/projects/bit/>>url:http://luaforge.net/projects/bit/]]
... ... @@ -160,9 +160,9 @@
160 160  * User can use other language ,not limited to Lua, just make sure the return is what you want to send.
161 161  
162 162  
149 +
163 163  == 2.2 Downstream ==
164 164  
165 -
166 166  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
167 167  
168 168  The file should use below format:
... ... @@ -173,33 +173,30 @@
173 173  
174 174  (% style="color:#037691" %)**dev_addr,imme/time,txt/hex,payload,txpw,txbw,SF,frequency,rxwindow**
175 175  
176 -* **dev_addr:** Inptu the device address
177 -* **imme/time:**
162 +* dev_addr: Inptu the device address
163 +* imme/time:
178 178  ** imme: send downstream immediately,For Class C end node.
179 179  ** time: send downstream after receive device's uplink. For Class A end node
180 -* **txt/hex:**
166 +* txt/hex:
181 181  ** txt: send payload in ASCII
182 182  ** hex: send payload in HEX
183 -* **payload: **payload to be sent, payload lenght should match the LoRaWAN protocol requirement.
184 -* **txpw:** Transmit Power. example: 20
185 -* **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:
186 186  ** 1: 500 kHz
187 187  ** 2: 250 kHz
188 188  ** 3: 125 kHz
189 189  ** 4: 62.5 kHz
190 -* **SF:** Spreading Factor : SF7/SF8/SF9/SF10/SF11/SF12
191 -* **Frequency:** Transmit Frequency: example: 923300000
192 -* **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.
193 193  
180 +Completely exmaple:
194 194  
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
195 195  
196 -(% style="color:blue" %)**Completely exmaple:**
197 197  
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
200 -
201 -
202 -
203 203  (% style="color:#037691" %)**Downstream Frequency**
204 204  
205 205  The LG308 will use the RX2 window info to send the downstream payload, use the default LoRaWAN settings, as below:
... ... @@ -214,7 +214,6 @@
214 214  * RU864: 869.1Mhz, SF12 BW125
215 215  
216 216  
217 -
218 218  (% style="color:#037691" %)**Examples:**
219 219  
220 220  (% class="box" %)
... ... @@ -221,20 +221,26 @@
221 221  (((
222 222  we can use echo command to create files in LG308 for downstream.
223 223  root@dragino-1d25dc:~~# echo 2602111D,time,hex,12345678 > /var/iot/push/test
206 +)))
224 224  
225 -
226 -**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.
227 227  lora_pkt_fwd[4286]: INFO~~ [DNLK]Looking file : test
228 228  lora_pkt_fwd[4286]: INFO~~ [DNLK]devaddr:2602111D, txmode:time, pdfm:hex, size:4, payload1:4Vx,payload_hex:77C1BB90
229 229  lora_pkt_fwd[4286]: INFO~~ [DNLK] DNLINK PENDING!(1 elems).
214 +)))
230 230  
231 -
232 -**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:
233 233  lora_pkt_fwd[4286]: INFO: tx_start_delay=1497 (1497.000000) - (1497, bw_delay=0.000000, notch_delay=0.000000)
234 234  lora_pkt_fwd[4286]: [LGWSEND]lgw_send done: count_us=3537314420, freq=923300000, size=17
221 +)))
235 235  
236 -
237 -**3)** and the end node will got:
223 +(% class="box" %)
224 +(((
225 +3) and the end node will got:
238 238  [5764825]~*~*~*~** UpLinkCounter= 98 ~*~*~*~**
239 239  [5764827]TX on freq 905300000 Hz at DR 0
240 240  Update Interval: 60000 ms
... ... @@ -246,9 +246,11 @@
246 246  Rssi= -41
247 247  Receive data
248 248  (% style="color:#037691" %)**2:12345678**  (%%) ~-~-> Hex
237 +)))
249 249  
250 -
251 -**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:
252 252  [5955877]~*~*~*~** UpLinkCounter= 102 ~*~*~*~**
253 253  [5955879]TX on freq 904100000 Hz at DR 0
254 254  Update Interval: 60000 ms
... ... @@ -265,12 +265,11 @@
265 265  
266 266  = 3. Example 1: Communicate with LT-22222-L =
267 267  
268 -
269 269  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]]
270 270  
271 271  (% class="box" %)
272 272  (((
273 -//#!/bin/sh
262 +#!/bin/sh
274 274  # This scripts shows how to use LPS8/LG308/DLOS8 to communicate with two LoRaWAN End Nodes, without the use of internet or LoRaWAN server
275 275  #
276 276  # Hardware Prepare:
... ... @@ -303,28 +303,26 @@
303 303  #  Device1: DI1: ON, DI2: ON , DO1: ON,  DO2: ON
304 304  #  Device2: DI1: OFF, DI2: OFF , DO1: ON,  DO2: ON
305 305  #  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
306 -#  whether the Device 2 has been changed.//
295 +#  whether the Device 2 has been changed.
307 307  )))
308 308  
298 +~1. Input keys
309 309  
310 -**~1. Input keys**
311 -
312 312  [[image:image-20220527162450-3.png]]
313 313  
314 314  Input Keys in LPS8
315 315  
316 316  
317 -**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.
318 318  
307 +3. Choose Built-in server
319 319  
320 -**3. Choose Built-in server**
321 -
322 322  [[image:image-20220527162518-4.png]]
323 323  
324 324  Choose Built-in server
325 325  
326 326  
327 -**4. Run the script.**
314 +4. Run the script.
328 328  
329 329  [[image:image-20220527162552-5.png]]
330 330  
... ... @@ -331,7 +331,7 @@
331 331  Run the script
332 332  
333 333  
334 -**5. Output:**
321 +5. Output:
335 335  
336 336  [[image:image-20220527162619-6.png]]
337 337  
... ... @@ -340,9 +340,8 @@
340 340  
341 341  = 4. Example 2: Communicate to TCP Server =
342 342  
330 +[[image:https://wiki.dragino.com/images/thumb/7/75/LPS8_TCP_0.png/600px-LPS8_TCP_0.png||height="370" width="600"]]
343 343  
344 -[[image:image-20220527162648-7.png]]
345 -
346 346  Network Structure
347 347  
348 348  
... ... @@ -349,42 +349,34 @@
349 349  Full instruction video inlcude how to write scripts to fit server needed is here:
350 350  
351 351  
352 -(% style="color:#037691" %)**Video Instruction**(%%): **[[https:~~/~~/youtu.be/-nevW6U2TsE>>url:https://youtu.be/-nevW6U2TsE]]**
338 +(% class="mark" %)**Video Instruction**: [[https:~~/~~/youtu.be/-nevW6U2TsE>>url:https://youtu.be/-nevW6U2TsE]]
353 353  
340 +(% class="mark" %)**Note: Firmware version must be higher than lgw-5.4.1607519907**
354 354  
355 -(% style="color:red" %)**Note: Firmware version must be higher than lgw-5.4.1607519907**
356 -
357 -
358 358  Assume we already set up ABP keys in the gateway:
359 359  
360 -[[image:image-20220527162852-8.png]]
344 +[[image:https://wiki.dragino.com/images/thumb/b/bf/LPS8_LT-22222_1.png/600px-LPS8_LT-22222_1.png||height="335" width="600"]]
361 361  
362 362  Input Keys in LPS8
363 363  
348 +run socket tool in PC
364 364  
350 +[[image:https://wiki.dragino.com/images/thumb/4/4b/LPS8_TCP_2.png/600px-LPS8_TCP_2.png||height="212" width="600"]]
365 365  
366 -**run socket tool in PC**
367 -
368 -[[image:image-20220527163028-9.png]]
369 -
370 -
371 371  Socket tool
372 372  
373 373  
355 +Input Server address and port
374 374  
375 -**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"]]
376 376  
377 -[[image:image-20220527163106-10.png]]
378 -
379 379  Input Server address and port
380 380  
381 381  
362 +See value receive in socket tool. :
382 382  
383 -**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"]]
384 384  
385 -[[image:image-20220527163144-11.png]]
386 -
387 387  value receive in socket tool
388 388  
389 -
390 390  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-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