Last modified by Xiaoling on 2023/04/20 18:14
<
From version < 14.4 >
edited by Xiaoling
on 2022/05/31 10:09
To version < 21.5
edited by Xiaoling
on 2023/04/20 18:14
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,13 +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.
13 +
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  
13 13  (((
... ... @@ -14,10 +14,14 @@
14 14  The basic of this feature is the decoding of (% style="color:red" %)**LoRaWAN ABP End Node**(%%). Requirements:
15 15  )))
16 16  
17 -1. LoRaWAN End Node in ABP mode. Make sure your end node works in this mode. End node most are default set to OTAA mode
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 -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 +* LoRaWAN End Node in ABP mode. Make sure your end node works in this mode. End node most are default set to OTAA mode
20 20  
22 +* 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]]
23 +
24 +* 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/]](%%)**
25 +
26 +
27 +
21 21  = 2. How it works =
22 22  
23 23  
... ... @@ -28,35 +28,44 @@
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
38 +**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
40 +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.
45 +
46 +
38 38  )))
39 39  
40 40  We need to input above keys in LG308 and enable ABP decryption.
41 41  
51 +
42 42  [[image:image-20220527161119-1.png]]
43 43  
54 +
44 44  Input the ABP keys in LG308
45 45  
46 46  
47 47  == 2.1 Upstream ==
48 48  
60 +
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  (((
52 -We can see the log of LG308 to know this packet arrive
64 +We can see the log of LG308 to know this packet arrive.
65 +
66 +
53 53  )))
54 54  
55 55  [[image:image-20220527161149-2.png]]
56 56  
57 -LG308 log by "logread -f" command
58 58  
72 +LG308 log by "(% style="color:red" %)**logread -f**" (%%)command
59 59  
74 +
75 +
60 60  The data of End Node is stored in the file /var/iot/channels/2602111D. We can use hexdump command to check it.
61 61  
62 62  (% class="box" %)
... ... @@ -67,10 +67,12 @@
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
86 +* **RSSI**: 4646 4646 4646 3946 = 0xFFFF FF9F : So RSSI = (0xFFFF FF9F - 0x100000000) = -97
73 73  
88 +* **SNR**: 3030 3030 3030 3546 = 0x0000 005F = 95, need to divide 10 so SNR is 9.5
89 +
90 +* **Payload**: 0xcc0c 0b63 0266 017f ff7f ff00
91 +
74 74  (% class="box" %)
75 75  (((
76 76  (% 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:
... ... @@ -81,14 +81,16 @@
81 81  000001c
82 82  )))
83 83  
102 +
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.
105 +(% 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  
111 +
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  
124 +
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  
134 +
113 113  If we choose Decode_LHT65, the MQTT process will send out with mqtt-data
114 114  
115 115  (% class="box" %)
... ... @@ -125,24 +125,34 @@
125 125  
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.
151 +**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
153 +**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:
155 +**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  
157 +**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 +
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:
162 +**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  
164 +
165 +(% style="color:red" %)
166 +**Some notice:**
167 +
141 141  * RSSI and SNR are added when gateway receive the packet, so there is always this field.
169 +
142 142  * If you rename the file, please make it executable.
171 +
143 143  * See this link for lua.bit module: [[http:~~/~~/luaforge.net/projects/bit/>>url:http://luaforge.net/projects/bit/]]
173 +
144 144  * Lua json module: [[http:~~/~~/json.luaforge.net/>>url:http://json.luaforge.net/]]
175 +
145 145  * the last line return is what will be used for MQTT
177 +
146 146  * User can use other language ,not limited to Lua, just make sure the return is what you want to send.
147 147  
148 148  
... ... @@ -149,6 +149,7 @@
149 149  
150 150  == 2.2 Downstream ==
151 151  
184 +
152 152  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
153 153  
154 154  The file should use below format:
... ... @@ -155,46 +155,68 @@
155 155  
156 156  (% style="color:#037691" %)**dev_addr,imme/time,txt/hex,payload**
157 157  
158 -Since fimware > Dragino-v2 lgw-5.4.1608518541 . Support more option
159 159  
160 -(% style="color:#037691" %)**dev_addr,imme/time,txt/hex,payload,txpw,txbw,SF,frequency,rxwindow**
192 +Since fimware > [[Dragino lgw~~-~~-build-v5.4.1668567157>>https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LG308-LG301/Firmware/Release/]] . Support more option
161 161  
162 -* dev_addr: Inptu the device address
163 -* imme/time:
194 +(% style="color:#037691" %)**dev_addr,imme/time,txt/hex,payload,txpw,txbw,SF,frequency,rxwindow,Fport**
195 +
196 +* **dev_addr:** Inptu the device address
197 +
198 +* **imme/time:**
164 164  ** imme: send downstream immediately,For Class C end node.
165 165  ** time: send downstream after receive device's uplink. For Class A end node
166 -* txt/hex:
201 +
202 +* **txt/hex:**
167 167  ** txt: send payload in ASCII
168 168  ** hex: send payload in HEX
169 -* payload: payload to be sent, payload lenght should match the LoRaWAN protocol requirement.
170 -* txpw: Transmit Power. example: 20
171 -* txbw: bandwidth:
205 +
206 +* **payload: **payload to be sent, payload lenght should match the LoRaWAN protocol requirement.
207 +
208 +* **txpw:** Transmit Power. example: 20
209 +
210 +* **txbw:** bandwidth:
172 172  ** 1: 500 kHz
173 173  ** 2: 250 kHz
174 174  ** 3: 125 kHz
175 175  ** 4: 62.5 kHz
176 -* SF: Spreading Factor : SF7/SF8/SF9/SF10/SF11/SF12
177 -* Frequency: Transmit Frequency: example: 923300000
178 -* rxwindow: transmit on Rx1Window or Rx2Window.
215 +* **SF:** Spreading Factor : SF7/SF8/SF9/SF10/SF11/SF12
179 179  
180 -Completely exmaple:
217 +* **Frequency:** Transmit Frequency: example: 923300000
181 181  
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
219 +* **rxwindow:** transmit on Rx1Window or Rx2Window.
184 184  
185 -(% style="color:#037691" %)**Downstream Frequency**
221 +* **Fport: **Transmit port,example:8
186 186  
223 +
224 +(% style="color:blue" %)**Completely exmaple:**
225 +
226 +* **Old version:** echo 018193F4,imme,hex,0101 > /var/iot/push/test
227 +
228 +* **New version:** echo 018193F4,imme,hex,0101,20,1,SF12,923300000,2,8 > /var/iot/push/test
229 +
230 +
231 +Downstream(% style="color:#037691" %)** Frequency:**
232 +
187 187  The LG308 will use the RX2 window info to send the downstream payload, use the default LoRaWAN settings, as below:
188 188  
189 189  * EU868: 869.525Mhz, DR0(SF12BW125)
236 +
190 190  * US915: 923.3Mhz, SF12 BW500
238 +
191 191  * CN470: 505.3Mhz, SF12 BW125
240 +
192 192  * AU915: 923.3Mhz, SF12 BW500
242 +
193 193  * AS923: 923.2Mhz, SF10 BW125
244 +
194 194  * KR920: 921.9Mhz, SF12 BW125
246 +
195 195  * IN865: 866.55Mhz, SF10 BW125
248 +
196 196  * RU864: 869.1Mhz, SF12 BW125
197 197  
251 +
252 +
198 198  (% style="color:#037691" %)**Examples:**
199 199  
200 200  (% class="box" %)
... ... @@ -201,26 +201,20 @@
201 201  (((
202 202  we can use echo command to create files in LG308 for downstream.
203 203  root@dragino-1d25dc:~~# echo 2602111D,time,hex,12345678 > /var/iot/push/test
204 -)))
205 205  
206 -(% class="box" %)
207 -(((
208 -1) From logread -f of gateway, we can see it has been added as pedning.
260 +
261 +**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).
212 -)))
213 213  
214 -(% class="box" %)
215 -(((
216 -2) When there is an upstrea from end node, this downstream will be sent and shows:
266 +
267 +**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 -)))
220 220  
221 -(% class="box" %)
222 -(((
223 -3) and the end node will got:
271 +
272 +**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
... ... @@ -232,11 +232,9 @@
232 232  Rssi= -41
233 233  Receive data
234 234  (% style="color:#037691" %)**2:12345678**  (%%) ~-~-> Hex
235 -)))
236 236  
237 -(% class="box" %)
238 -(((
239 -4) If we use the command "echo 2602111D,time,txt,12345678 > /var/iot/push/test" for downstream, the end node will got:
285 +
286 +**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  
303 +
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
308 +//#!/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,41 +290,51 @@
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.
341 +#  whether the Device 2 has been changed.//
294 294  )))
295 295  
296 -~1. Input keys
297 297  
345 +(% style="color:blue" %)**1. Input keys**
346 +
347 +
298 298  [[image:image-20220527162450-3.png]]
299 299  
300 300  Input Keys in LPS8
301 301  
302 302  
303 -2. Make sure the LPS8 and LT use the same frequency bands, choose EU868 in this test.
304 304  
305 -3. Choose Built-in server
354 +(% style="color:blue" %)**2. Make sure the LPS8 and LT use the same frequency bands, choose EU868 in this test.**
306 306  
356 +
357 +(% style="color:blue" %)**3. Choose Built-in server**
358 +
359 +
307 307  [[image:image-20220527162518-4.png]]
308 308  
309 309  Choose Built-in server
310 310  
311 311  
312 -4. Run the script.
313 313  
314 -[[image:image-20220527162552-5.png]]
366 +(% style="color:blue" %)**4. Run the script.**
315 315  
368 +
369 +[[image:image-20220722115213-2.png]]
370 +
316 316  Run the script
317 317  
318 318  
319 -5. Output:
320 320  
321 -[[image:image-20220527162619-6.png]]
375 +(% style="color:blue" %)**5. Output:**
322 322  
377 +
378 +[[image:image-20220722115133-1.png]]
379 +
323 323  Output from LPS8
324 324  
325 325  
326 326  = 4. Example 2: Communicate to TCP Server =
327 327  
385 +
328 328  [[image:image-20220527162648-7.png]]
329 329  
330 330  Network Structure
... ... @@ -332,12 +332,13 @@
332 332  
333 333  Full instruction video inlcude how to write scripts to fit server needed is here:
334 334  
335 -
336 336  (% style="color:#037691" %)**Video Instruction**(%%): **[[https:~~/~~/youtu.be/-nevW6U2TsE>>url:https://youtu.be/-nevW6U2TsE]]**
337 337  
395 +(% style="display:none" %) (%%)
338 338  
339 339  (% style="color:red" %)**Note: Firmware version must be higher than lgw-5.4.1607519907**
340 340  
399 +
341 341  Assume we already set up ABP keys in the gateway:
342 342  
343 343  [[image:image-20220527162852-8.png]]
... ... @@ -345,8 +345,10 @@
345 345  Input Keys in LPS8
346 346  
347 347  
348 -run socket tool in PC
349 349  
408 +(% style="color:blue" %)**run socket tool in PC**
409 +
410 +
350 350  [[image:image-20220527163028-9.png]]
351 351  
352 352  
... ... @@ -353,17 +353,22 @@
353 353  Socket tool
354 354  
355 355  
356 -Input Server address and port
357 357  
418 +(% style="color:blue" %)**Input Server address and port**
419 +
420 +
358 358  [[image:image-20220527163106-10.png]]
359 359  
360 360  Input Server address and port
361 361  
362 362  
363 -See value receive in socket tool. :
364 364  
365 -[[image:image-20220527163144-11.png]]
427 +(% style="color:blue" %)**See value receive in socket tool:**
366 366  
429 +
430 +[[image:image-20220527163144-11.png||height="502" width="1371"]]
431 +
367 367  value receive in socket tool
368 368  
434 +
369 369  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