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

Summary

Details

Page properties
Content
... ... @@ -1,4 +1,5 @@
1 -**Table of Contents:**
1 +*
2 +** Table of** **Contents:
2 2  
3 3  {{toc/}}
4 4  
... ... @@ -20,10 +20,6 @@
20 20  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]]
21 21  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/]](%%)**
22 22  
23 -
24 -
25 -
26 -
27 27  = 2. How it works =
28 28  
29 29  
... ... @@ -52,7 +52,6 @@
52 52  Input the ABP keys in LG308
53 53  
54 54  
55 -
56 56  == 2.1 Upstream ==
57 57  
58 58  
... ... @@ -81,9 +81,6 @@
81 81  * **SNR**: 3030 3030 3030 3546 = 0x0000 005F = 95, need to divide 10 so SNR is 9.5
82 82  * **Payload**: 0xcc0c 0b63 0266 017f ff7f ff00
83 83  
84 -
85 -
86 -
87 87  (% class="box" %)
88 88  (((
89 89  (% 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:
... ... @@ -94,7 +94,6 @@
94 94  000001c
95 95  )))
96 96  
97 -
98 98  (% class="box" %)
99 99  (((
100 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.
... ... @@ -101,7 +101,6 @@
101 101  )))
102 102  
103 103  
104 -
105 105  === 2.2.1 Decode Method ===
106 106  
107 107  
... ... @@ -141,27 +141,22 @@
141 141  Above scripts are store in /etc/lora/decoder/. User can put their scripts here and select it in the UI.
142 142  
143 143  
144 -
145 145  === 2.2.2 How to Decode My End Node ===
146 146  
147 147  
148 -**1.** Configure the ABP keys for your end node in the gateway. enable ABP decode in Web UI
138 +1/ Configure the ABP keys for your end node in the gateway. enable ABP decode in Web UI
149 149  
150 -**2. **Don't choose MQTT service, use LoRaWAN.
140 +2/ Don't choose MQTT service, use LoRaWAN.
151 151  
152 -**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
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
153 153  
154 -**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:
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:
155 155  
156 156  {{{/etc/lora/decoder/Dragino_LHT65 END_NODE_DEV_ADDR
157 157  }}}
158 158  
159 -**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.
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. Some notice:
160 160  
161 -
162 -(% style="color:red" %)
163 -**Some notice:**
164 -
165 165  * RSSI and SNR are added when gateway receive the packet, so there is always this field.
166 166  * If you rename the file, please make it executable.
167 167  * See this link for lua.bit module: [[http:~~/~~/luaforge.net/projects/bit/>>url:http://luaforge.net/projects/bit/]]
... ... @@ -209,6 +209,7 @@
209 209  * **New version:** echo 018193F4,imme,hex,0101,20,1,SF12,923300000,2 > /var/iot/push/test
210 210  
211 211  
198 +
212 212  (% style="color:#037691" %)**Downstream Frequency**
213 213  
214 214  The LG308 will use the RX2 window info to send the downstream payload, use the default LoRaWAN settings, as below:
... ... @@ -223,6 +223,7 @@
223 223  * RU864: 869.1Mhz, SF12 BW125
224 224  
225 225  
213 +
226 226  (% style="color:#037691" %)**Examples:**
227 227  
228 228  (% class="box" %)
... ... @@ -229,19 +229,25 @@
229 229  (((
230 230  we can use echo command to create files in LG308 for downstream.
231 231  root@dragino-1d25dc:~~# echo 2602111D,time,hex,12345678 > /var/iot/push/test
220 +)))
232 232  
233 -
222 +(% class="box" %)
223 +(((
234 234  **1)** From logread -f of gateway, we can see it has been added as pedning.
235 235  lora_pkt_fwd[4286]: INFO~~ [DNLK]Looking file : test
236 236  lora_pkt_fwd[4286]: INFO~~ [DNLK]devaddr:2602111D, txmode:time, pdfm:hex, size:4, payload1:4Vx,payload_hex:77C1BB90
237 237  lora_pkt_fwd[4286]: INFO~~ [DNLK] DNLINK PENDING!(1 elems).
228 +)))
238 238  
239 -
230 +(% class="box" %)
231 +(((
240 240  **2)** When there is an upstrea from end node, this downstream will be sent and shows:
241 241  lora_pkt_fwd[4286]: INFO: tx_start_delay=1497 (1497.000000) - (1497, bw_delay=0.000000, notch_delay=0.000000)
242 242  lora_pkt_fwd[4286]: [LGWSEND]lgw_send done: count_us=3537314420, freq=923300000, size=17
235 +)))
243 243  
244 -
237 +(% class="box" %)
238 +(((
245 245  **3)** and the end node will got:
246 246  [5764825]~*~*~*~** UpLinkCounter= 98 ~*~*~*~**
247 247  [5764827]TX on freq 905300000 Hz at DR 0
... ... @@ -254,8 +254,10 @@
254 254  Rssi= -41
255 255  Receive data
256 256  (% style="color:#037691" %)**2:12345678**  (%%) ~-~-> Hex
251 +)))
257 257  
258 -
253 +(% class="box" %)
254 +(((
259 259  **4) **If we use the command "echo 2602111D,time,txt,12345678 > /var/iot/push/test" for downstream, the end node will got:
260 260  [5955877]~*~*~*~** UpLinkCounter= 102 ~*~*~*~**
261 261  [5955879]TX on freq 904100000 Hz at DR 0
... ... @@ -271,7 +271,6 @@
271 271  )))
272 272  
273 273  
274 -
275 275  = 3. Example 1: Communicate with LT-22222-L =
276 276  
277 277  
... ... @@ -315,7 +315,6 @@
315 315  #  whether the Device 2 has been changed.//
316 316  )))
317 317  
318 -
319 319  **~1. Input keys**
320 320  
321 321  [[image:image-20220527162450-3.png]]
... ... @@ -325,7 +325,6 @@
325 325  
326 326  **2. Make sure the LPS8 and LT use the same frequency bands, choose EU868 in this test.**
327 327  
328 -
329 329  **3. Choose Built-in server**
330 330  
331 331  [[image:image-20220527162518-4.png]]
... ... @@ -335,7 +335,7 @@
335 335  
336 336  **4. Run the script.**
337 337  
338 -[[image:image-20220722115213-2.png]]
331 +[[image:image-20220527162552-5.png]]
339 339  
340 340  Run the script
341 341  
... ... @@ -342,12 +342,11 @@
342 342  
343 343  **5. Output:**
344 344  
345 -[[image:image-20220722115133-1.png]]
338 +[[image:image-20220527162619-6.png]]
346 346  
347 347  Output from LPS8
348 348  
349 349  
350 -
351 351  = 4. Example 2: Communicate to TCP Server =
352 352  
353 353  
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

Applications

Navigation

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