<
From version < 21.2 >
edited by Xiaoling
on 2023/04/12 15:41
To version < 14.6 >
edited by Xiaoling
on 2022/06/01 11:13
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,12 +1,10 @@
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.
... ... @@ -32,44 +32,35 @@
32 32  
33 33  (% class="box infomessage" %)
34 34  (((
35 -**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
36 36  AT+APPSKEY=b3 17 f8 14 7a 43 27 8a 6a 31 c4 47 3d 55 5d 33
37 -AT+DADDR=2602111D**
35 +AT+DADDR=2602111D
38 38  )))
39 39  
40 40  (((
41 41  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.
42 -
43 -
44 44  )))
45 45  
46 46  We need to input above keys in LG308 and enable ABP decryption.
47 47  
48 -
49 49  [[image:image-20220527161119-1.png]]
50 50  
51 -
52 52  Input the ABP keys in LG308
53 53  
54 54  
55 55  == 2.1 Upstream ==
56 56  
57 -
58 58  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.
59 59  
60 60  (((
61 -We can see the log of LG308 to know this packet arrive.
62 -
63 -
54 +We can see the log of LG308 to know this packet arrive
64 64  )))
65 65  
66 66  [[image:image-20220527161149-2.png]]
67 67  
59 +LG308 log by "logread -f" command
68 68  
69 -LG308 log by "(% style="color:red" %)**logread -f**" (%%)command
70 70  
71 -
72 -
73 73  The data of End Node is stored in the file /var/iot/channels/2602111D. We can use hexdump command to check it.
74 74  
75 75  (% class="box" %)
... ... @@ -80,9 +80,9 @@
80 80  000001c
81 81  )))
82 82  
83 -* **RSSI**: 4646 4646 4646 3946 = 0xFFFF FF9F : So RSSI = (0xFFFF FF9F - 0x100000000) = -97
84 -* **SNR**: 3030 3030 3030 3546 = 0x0000 005F = 95, need to divide 10 so SNR is 9.5
85 -* **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
86 86  
87 87  (% class="box" %)
88 88  (((
... ... @@ -94,16 +94,14 @@
94 94  000001c
95 95  )))
96 96  
97 -
98 98  (% class="box" %)
99 99  (((
100 -(% 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.
101 101  )))
102 102  
103 103  
104 104  === 2.2.1 Decode Method ===
105 105  
106 -
107 107  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.
108 108  
109 109  For example we have a LHT65 , works in ABP mode and gateway successful get the data, which are:
... ... @@ -116,7 +116,6 @@
116 116  000001c
117 117  )))
118 118  
119 -
120 120  If we choose ASCII decoder, the MQTT process will send out with mqtt-data:
121 121  
122 122  (% class="box" %)
... ... @@ -126,7 +126,6 @@
126 126  Sun Sep 27 04:33:16 2020 user.notice root: [IoT.MQTT]:mqtt_data[-m]: (% style="color:#037691" %)**ffffffe700000048ccd17fff7fff017fff7fff00**
127 127  )))
128 128  
129 -
130 130  If we choose Decode_LHT65, the MQTT process will send out with mqtt-data
131 131  
132 132  (% class="box" %)
... ... @@ -142,24 +142,19 @@
142 142  
143 143  === 2.2.2 How to Decode My End Node ===
144 144  
130 +1/ Configure the ABP keys for your end node in the gateway. enable ABP decode in Web UI
145 145  
146 -**1.** Configure the ABP keys for your end node in the gateway. enable ABP decode in Web UI
132 +2/ Don't choose MQTT service, use LoRaWAN.
147 147  
148 -**2. **Don't choose MQTT service, use LoRaWAN.
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
149 149  
150 -**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
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:
151 151  
152 -**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:
153 -
154 154  {{{/etc/lora/decoder/Dragino_LHT65 END_NODE_DEV_ADDR
155 155  }}}
156 156  
157 -**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.
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:
158 158  
159 -
160 -(% style="color:red" %)
161 -**Some notice:**
162 -
163 163  * RSSI and SNR are added when gateway receive the packet, so there is always this field.
164 164  * If you rename the file, please make it executable.
165 165  * See this link for lua.bit module: [[http:~~/~~/luaforge.net/projects/bit/>>url:http://luaforge.net/projects/bit/]]
... ... @@ -168,10 +168,8 @@
168 168  * User can use other language ,not limited to Lua, just make sure the return is what you want to send.
169 169  
170 170  
171 -
172 172  == 2.2 Downstream ==
173 173  
174 -
175 175  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
176 176  
177 177  The file should use below format:
... ... @@ -178,37 +178,36 @@
178 178  
179 179  (% style="color:#037691" %)**dev_addr,imme/time,txt/hex,payload**
180 180  
159 +Since fimware > Dragino-v2 lgw-5.4.1608518541 . Support more option
181 181  
182 -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 +(% style="color:#037691" %)**dev_addr,imme/time,txt/hex,payload,txpw,txbw,SF,frequency,rxwindow**
183 183  
184 -(% style="color:#037691" %)**dev_addr,imme/time,txt/hex,payload,txpw,txbw,SF,frequency,rxwindow,Fport**
185 -
186 -* **dev_addr:** Inptu the device address
187 -* **imme/time:**
163 +* dev_addr: Inptu the device address
164 +* imme/time:
188 188  ** imme: send downstream immediately,For Class C end node.
189 189  ** time: send downstream after receive device's uplink. For Class A end node
190 -* **txt/hex:**
167 +* txt/hex:
191 191  ** txt: send payload in ASCII
192 192  ** hex: send payload in HEX
193 -* **payload: **payload to be sent, payload lenght should match the LoRaWAN protocol requirement.
194 -* **txpw:** Transmit Power. example: 20
195 -* **txbw:** bandwidth:
170 +* payload: payload to be sent, payload lenght should match the LoRaWAN protocol requirement.
171 +* txpw: Transmit Power. example: 20
172 +* txbw: bandwidth:
196 196  ** 1: 500 kHz
197 197  ** 2: 250 kHz
198 198  ** 3: 125 kHz
199 199  ** 4: 62.5 kHz
200 -* **SF:** Spreading Factor : SF7/SF8/SF9/SF10/SF11/SF12
201 -* **Frequency:** Transmit Frequency: example: 923300000
202 -* **rxwindow:** transmit on Rx1Window or Rx2Window.
203 -* **Fport: **Transmit port,example:8
177 +* SF: Spreading Factor : SF7/SF8/SF9/SF10/SF11/SF12
178 +* Frequency: Transmit Frequency: example: 923300000
179 +* rxwindow: transmit on Rx1Window or Rx2Window.
204 204  
205 -(% style="color:blue" %)**Completely exmaple:**
181 +Completely exmaple:
206 206  
207 -* **Old version:** echo 018193F4,imme,hex,0101 > /var/iot/push/test
208 -* **New version:** echo 018193F4,imme,hex,0101,20,1,SF12,923300000,2,8 > /var/iot/push/test
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
209 209  
210 -(% style="color:#037691" %)**Downstream Frequency:**
211 211  
187 +(% style="color:#037691" %)**Downstream Frequency**
188 +
212 212  The LG308 will use the RX2 window info to send the downstream payload, use the default LoRaWAN settings, as below:
213 213  
214 214  * EU868: 869.525Mhz, DR0(SF12BW125)
... ... @@ -220,6 +220,7 @@
220 220  * IN865: 866.55Mhz, SF10 BW125
221 221  * RU864: 869.1Mhz, SF12 BW125
222 222  
200 +
223 223  (% style="color:#037691" %)**Examples:**
224 224  
225 225  (% class="box" %)
... ... @@ -226,20 +226,26 @@
226 226  (((
227 227  we can use echo command to create files in LG308 for downstream.
228 228  root@dragino-1d25dc:~~# echo 2602111D,time,hex,12345678 > /var/iot/push/test
207 +)))
229 229  
230 -
231 -**1)** From logread -f of gateway, we can see it has been added as pedning.
209 +(% class="box" %)
210 +(((
211 +1) From logread -f of gateway, we can see it has been added as pedning.
232 232  lora_pkt_fwd[4286]: INFO~~ [DNLK]Looking file : test
233 233  lora_pkt_fwd[4286]: INFO~~ [DNLK]devaddr:2602111D, txmode:time, pdfm:hex, size:4, payload1:4Vx,payload_hex:77C1BB90
234 234  lora_pkt_fwd[4286]: INFO~~ [DNLK] DNLINK PENDING!(1 elems).
215 +)))
235 235  
236 -
237 -**2)** When there is an upstrea from end node, this downstream will be sent and shows:
217 +(% class="box" %)
218 +(((
219 +2) When there is an upstrea from end node, this downstream will be sent and shows:
238 238  lora_pkt_fwd[4286]: INFO: tx_start_delay=1497 (1497.000000) - (1497, bw_delay=0.000000, notch_delay=0.000000)
239 239  lora_pkt_fwd[4286]: [LGWSEND]lgw_send done: count_us=3537314420, freq=923300000, size=17
222 +)))
240 240  
241 -
242 -**3)** and the end node will got:
224 +(% class="box" %)
225 +(((
226 +3) and the end node will got:
243 243  [5764825]~*~*~*~** UpLinkCounter= 98 ~*~*~*~**
244 244  [5764827]TX on freq 905300000 Hz at DR 0
245 245  Update Interval: 60000 ms
... ... @@ -251,9 +251,11 @@
251 251  Rssi= -41
252 252  Receive data
253 253  (% style="color:#037691" %)**2:12345678**  (%%) ~-~-> Hex
238 +)))
254 254  
255 -
256 -**4) **If we use the command "echo 2602111D,time,txt,12345678 > /var/iot/push/test" for downstream, the end node will got:
240 +(% class="box" %)
241 +(((
242 +4) If we use the command "echo 2602111D,time,txt,12345678 > /var/iot/push/test" for downstream, the end node will got:
257 257  [5955877]~*~*~*~** UpLinkCounter= 102 ~*~*~*~**
258 258  [5955879]TX on freq 904100000 Hz at DR 0
259 259  Update Interval: 60000 ms
... ... @@ -270,12 +270,11 @@
270 270  
271 271  = 3. Example 1: Communicate with LT-22222-L =
272 272  
273 -
274 274  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]]
275 275  
276 276  (% class="box" %)
277 277  (((
278 -//#!/bin/sh
263 +#!/bin/sh
279 279  # This scripts shows how to use LPS8/LG308/DLOS8 to communicate with two LoRaWAN End Nodes, without the use of internet or LoRaWAN server
280 280  #
281 281  # Hardware Prepare:
... ... @@ -308,51 +308,41 @@
308 308  #  Device1: DI1: ON, DI2: ON , DO1: ON,  DO2: ON
309 309  #  Device2: DI1: OFF, DI2: OFF , DO1: ON,  DO2: ON
310 310  #  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
311 -#  whether the Device 2 has been changed.//
296 +#  whether the Device 2 has been changed.
312 312  )))
313 313  
299 +~1. Input keys
314 314  
315 -(% style="color:blue" %)**1. Input keys**
316 -
317 -
318 318  [[image:image-20220527162450-3.png]]
319 319  
320 320  Input Keys in LPS8
321 321  
322 322  
306 +2. Make sure the LPS8 and LT use the same frequency bands, choose EU868 in this test.
323 323  
324 -(% style="color:blue" %)**2. Make sure the LPS8 and LT use the same frequency bands, choose EU868 in this test.**
308 +3. Choose Built-in server
325 325  
326 -
327 -(% style="color:blue" %)**3. Choose Built-in server**
328 -
329 -
330 330  [[image:image-20220527162518-4.png]]
331 331  
332 332  Choose Built-in server
333 333  
334 334  
315 +4. Run the script.
335 335  
336 -(% style="color:blue" %)**4. Run the script.**
317 +[[image:image-20220527162552-5.png]]
337 337  
338 -
339 -[[image:image-20220722115213-2.png]]
340 -
341 341  Run the script
342 342  
343 343  
322 +5. Output:
344 344  
345 -(% style="color:blue" %)**5. Output:**
324 +[[image:image-20220527162619-6.png]]
346 346  
347 -
348 -[[image:image-20220722115133-1.png]]
349 -
350 350  Output from LPS8
351 351  
352 352  
353 353  = 4. Example 2: Communicate to TCP Server =
354 354  
355 -
356 356  [[image:image-20220527162648-7.png]]
357 357  
358 358  Network Structure
... ... @@ -366,7 +366,6 @@
366 366  
367 367  (% style="color:red" %)**Note: Firmware version must be higher than lgw-5.4.1607519907**
368 368  
369 -
370 370  Assume we already set up ABP keys in the gateway:
371 371  
372 372  [[image:image-20220527162852-8.png]]
... ... @@ -374,10 +374,8 @@
374 374  Input Keys in LPS8
375 375  
376 376  
351 +run socket tool in PC
377 377  
378 -(% style="color:blue" %)**run socket tool in PC**
379 -
380 -
381 381  [[image:image-20220527163028-9.png]]
382 382  
383 383  
... ... @@ -384,22 +384,17 @@
384 384  Socket tool
385 385  
386 386  
359 +Input Server address and port
387 387  
388 -(% style="color:blue" %)**Input Server address and port**
389 -
390 -
391 391  [[image:image-20220527163106-10.png]]
392 392  
393 393  Input Server address and port
394 394  
395 395  
366 +See value receive in socket tool. :
396 396  
397 -(% style="color:blue" %)**See value receive in socket tool:**
398 -
399 -
400 400  [[image:image-20220527163144-11.png]]
401 401  
402 402  value receive in socket tool
403 403  
404 -
405 405  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,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