Last modified by Xiaoling on 2023/04/20 18:14
<
From version < 14.8 >
edited by Xiaoling
on 2022/07/22 11:32
To version < 14.1 >
edited by Xiaoling
on 2022/05/27 16:33
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,17 +1,14 @@
1 -*
2 -** Table of** **Contents:
1 + **Contents:**
3 3  
4 4  {{toc/}}
5 5  
6 6  
7 -
8 8  = 1. Introduction =
9 9  
10 -
11 11  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:
12 12  
13 13  * No internet connection.
14 -* 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]]).
15 15  
16 16  (((
17 17  The basic of this feature is the decoding of (% style="color:red" %)**LoRaWAN ABP End Node**(%%). Requirements:
... ... @@ -21,6 +21,8 @@
21 21  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]]
22 22  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/]](%%)**
23 23  
21 +
22 +
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
33 +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**
35 +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
59 +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,9 +73,9 @@
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
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
79 79  
80 80  (% class="box" %)
81 81  (((
... ... @@ -89,13 +89,12 @@
89 89  
90 90  (% class="box" %)
91 91  (((
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.
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.
93 93  )))
94 94  
95 95  
96 96  === 2.2.1 Decode Method ===
97 97  
98 -
99 99  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.
100 100  
101 101  For example we have a LHT65 , works in ABP mode and gateway successful get the data, which are:
... ... @@ -108,7 +108,6 @@
108 108  000001c
109 109  )))
110 110  
111 -
112 112  If we choose ASCII decoder, the MQTT process will send out with mqtt-data:
113 113  
114 114  (% class="box" %)
... ... @@ -118,7 +118,6 @@
118 118  Sun Sep 27 04:33:16 2020 user.notice root: [IoT.MQTT]:mqtt_data[-m]: (% style="color:#037691" %)**ffffffe700000048ccd17fff7fff017fff7fff00**
119 119  )))
120 120  
121 -
122 122  If we choose Decode_LHT65, the MQTT process will send out with mqtt-data
123 123  
124 124  (% class="box" %)
... ... @@ -134,7 +134,6 @@
134 134  
135 135  === 2.2.2 How to Decode My End Node ===
136 136  
137 -
138 138  1/ Configure the ABP keys for your end node in the gateway. enable ABP decode in Web UI
139 139  
140 140  2/ Don't choose MQTT service, use LoRaWAN.
... ... @@ -159,7 +159,6 @@
159 159  
160 160  == 2.2 Downstream ==
161 161  
162 -
163 163  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
164 164  
165 165  The file should use below format:
... ... @@ -170,32 +170,29 @@
170 170  
171 171  (% style="color:#037691" %)**dev_addr,imme/time,txt/hex,payload,txpw,txbw,SF,frequency,rxwindow**
172 172  
173 -* **dev_addr:** Inptu the device address
174 -* **imme/time:**
164 +* dev_addr: Inptu the device address
165 +* imme/time:
175 175  ** imme: send downstream immediately,For Class C end node.
176 176  ** time: send downstream after receive device's uplink. For Class A end node
177 -* **txt/hex:**
168 +* txt/hex:
178 178  ** txt: send payload in ASCII
179 179  ** hex: send payload in HEX
180 -* **payload: **payload to be sent, payload lenght should match the LoRaWAN protocol requirement.
181 -* **txpw:** Transmit Power. example: 20
182 -* **txbw:** bandwidth:
171 +* payload: payload to be sent, payload lenght should match the LoRaWAN protocol requirement.
172 +* txpw: Transmit Power. example: 20
173 +* txbw: bandwidth:
183 183  ** 1: 500 kHz
184 184  ** 2: 250 kHz
185 185  ** 3: 125 kHz
186 186  ** 4: 62.5 kHz
187 -* **SF:** Spreading Factor : SF7/SF8/SF9/SF10/SF11/SF12
188 -* **Frequency:** Transmit Frequency: example: 923300000
189 -* **rxwindow:** transmit on Rx1Window or Rx2Window.
178 +* SF: Spreading Factor : SF7/SF8/SF9/SF10/SF11/SF12
179 +* Frequency: Transmit Frequency: example: 923300000
180 +* rxwindow: transmit on Rx1Window or Rx2Window.
190 190  
182 +Completely exmaple:
191 191  
192 -(% style="color:blue" %)**Completely exmaple:**
184 +* Old version: echo 018193F4,imme,hex,0101 > /var/iot/push/test
185 +* New version: echo 018193F4,imme,hex,0101,20,1,SF12,923300000,2 > /var/iot/push/test
193 193  
194 -* **Old version:** echo 018193F4,imme,hex,0101 > /var/iot/push/test
195 -* **New version:** echo 018193F4,imme,hex,0101,20,1,SF12,923300000,2 > /var/iot/push/test
196 -
197 -
198 -
199 199  (% style="color:#037691" %)**Downstream Frequency**
200 200  
201 201  The LG308 will use the RX2 window info to send the downstream payload, use the default LoRaWAN settings, as below:
... ... @@ -209,8 +209,6 @@
209 209  * IN865: 866.55Mhz, SF10 BW125
210 210  * RU864: 869.1Mhz, SF12 BW125
211 211  
212 -
213 -
214 214  (% style="color:#037691" %)**Examples:**
215 215  
216 216  (% class="box" %)
... ... @@ -221,7 +221,7 @@
221 221  
222 222  (% class="box" %)
223 223  (((
224 -**1)** From logread -f of gateway, we can see it has been added as pedning.
210 +1) From logread -f of gateway, we can see it has been added as pedning.
225 225  lora_pkt_fwd[4286]: INFO~~ [DNLK]Looking file : test
226 226  lora_pkt_fwd[4286]: INFO~~ [DNLK]devaddr:2602111D, txmode:time, pdfm:hex, size:4, payload1:4Vx,payload_hex:77C1BB90
227 227  lora_pkt_fwd[4286]: INFO~~ [DNLK] DNLINK PENDING!(1 elems).
... ... @@ -229,7 +229,7 @@
229 229  
230 230  (% class="box" %)
231 231  (((
232 -**2)** When there is an upstrea from end node, this downstream will be sent and shows:
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
235 235  )))
... ... @@ -236,7 +236,7 @@
236 236  
237 237  (% class="box" %)
238 238  (((
239 -**3)** and the end node will got:
225 +3) and the end node will got:
240 240  [5764825]~*~*~*~** UpLinkCounter= 98 ~*~*~*~**
241 241  [5764827]TX on freq 905300000 Hz at DR 0
242 242  Update Interval: 60000 ms
... ... @@ -252,7 +252,7 @@
252 252  
253 253  (% class="box" %)
254 254  (((
255 -**4) **If we use the command "echo 2602111D,time,txt,12345678 > /var/iot/push/test" for downstream, the end node will got:
241 +4) If we use the command "echo 2602111D,time,txt,12345678 > /var/iot/push/test" for downstream, the end node will got:
256 256  [5955877]~*~*~*~** UpLinkCounter= 102 ~*~*~*~**
257 257  [5955879]TX on freq 904100000 Hz at DR 0
258 258  Update Interval: 60000 ms
... ... @@ -269,12 +269,11 @@
269 269  
270 270  = 3. Example 1: Communicate with LT-22222-L =
271 271  
272 -
273 273  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]]
274 274  
275 275  (% class="box" %)
276 276  (((
277 -//#!/bin/sh
262 +#!/bin/sh
278 278  # This scripts shows how to use LPS8/LG308/DLOS8 to communicate with two LoRaWAN End Nodes, without the use of internet or LoRaWAN server
279 279  #
280 280  # Hardware Prepare:
... ... @@ -307,10 +307,10 @@
307 307  #  Device1: DI1: ON, DI2: ON , DO1: ON,  DO2: ON
308 308  #  Device2: DI1: OFF, DI2: OFF , DO1: ON,  DO2: ON
309 309  #  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
310 -#  whether the Device 2 has been changed.//
295 +#  whether the Device 2 has been changed.
311 311  )))
312 312  
313 -**~1. Input keys**
298 +~1. Input keys
314 314  
315 315  [[image:image-20220527162450-3.png]]
316 316  
... ... @@ -317,9 +317,9 @@
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.**
305 +2. Make sure the LPS8 and LT use the same frequency bands, choose EU868 in this test.
321 321  
322 -**3. Choose Built-in server**
307 +3. Choose Built-in server
323 323  
324 324  [[image:image-20220527162518-4.png]]
325 325  
... ... @@ -326,7 +326,7 @@
326 326  Choose Built-in server
327 327  
328 328  
329 -**4. Run the script.**
314 +4. Run the script.
330 330  
331 331  [[image:image-20220527162552-5.png]]
332 332  
... ... @@ -333,7 +333,7 @@
333 333  Run the script
334 334  
335 335  
336 -**5. Output:**
321 +5. Output:
337 337  
338 338  [[image:image-20220527162619-6.png]]
339 339  
... ... @@ -342,7 +342,6 @@
342 342  
343 343  = 4. Example 2: Communicate to TCP Server =
344 344  
345 -
346 346  [[image:image-20220527162648-7.png]]
347 347  
348 348  Network Structure
... ... @@ -356,7 +356,6 @@
356 356  
357 357  (% style="color:red" %)**Note: Firmware version must be higher than lgw-5.4.1607519907**
358 358  
359 -
360 360  Assume we already set up ABP keys in the gateway:
361 361  
362 362  [[image:image-20220527162852-8.png]]
... ... @@ -364,9 +364,8 @@
364 364  Input Keys in LPS8
365 365  
366 366  
350 +run socket tool in PC
367 367  
368 -**run socket tool in PC**
369 -
370 370  [[image:image-20220527163028-9.png]]
371 371  
372 372  
... ... @@ -373,20 +373,17 @@
373 373  Socket tool
374 374  
375 375  
358 +Input Server address and port
376 376  
377 -**Input Server address and port**
378 -
379 379  [[image:image-20220527163106-10.png]]
380 380  
381 381  Input Server address and port
382 382  
383 383  
365 +See value receive in socket tool. :
384 384  
385 -**See value receive in socket tool:**
386 -
387 387  [[image:image-20220527163144-11.png]]
388 388  
389 389  value receive in socket tool
390 390  
391 -
392 392  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.

Applications

Navigation

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