Last modified by Xiaoling on 2023/04/20 18:14
<
From version < 19.1 >
edited by Xiaoye
on 2022/08/02 11:54
To version < 16.1 >
edited by Xiaoling
on 2022/07/22 11:33
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoye
1 +XWiki.Xiaoling
Content
... ... @@ -22,6 +22,7 @@
22 22  
23 23  
24 24  
25 +
25 25  = 2. How it works =
26 26  
27 27  
... ... @@ -50,7 +50,6 @@
50 50  Input the ABP keys in LG308
51 51  
52 52  
53 -
54 54  == 2.1 Upstream ==
55 55  
56 56  
... ... @@ -79,7 +79,6 @@
79 79  * **SNR**: 3030 3030 3030 3546 = 0x0000 005F = 95, need to divide 10 so SNR is 9.5
80 80  * **Payload**: 0xcc0c 0b63 0266 017f ff7f ff00
81 81  
82 -
83 83  (% class="box" %)
84 84  (((
85 85  (% 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:
... ... @@ -90,7 +90,6 @@
90 90  000001c
91 91  )))
92 92  
93 -
94 94  (% class="box" %)
95 95  (((
96 96  (% 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.
... ... @@ -97,7 +97,6 @@
97 97  )))
98 98  
99 99  
100 -
101 101  === 2.2.1 Decode Method ===
102 102  
103 103  
... ... @@ -141,23 +141,19 @@
141 141  === 2.2.2 How to Decode My End Node ===
142 142  
143 143  
144 -**1.** Configure the ABP keys for your end node in the gateway. enable ABP decode in Web UI
141 +1/ Configure the ABP keys for your end node in the gateway. enable ABP decode in Web UI
145 145  
146 -**2. **Don't choose MQTT service, use LoRaWAN.
143 +2/ Don't choose MQTT service, use LoRaWAN.
147 147  
148 -**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
145 +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 -**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:
147 +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 152  {{{/etc/lora/decoder/Dragino_LHT65 END_NODE_DEV_ADDR
153 153  }}}
154 154  
155 -**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.
152 +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:
156 156  
157 -
158 -(% style="color:red" %)
159 -**Some notice:**
160 -
161 161  * RSSI and SNR are added when gateway receive the packet, so there is always this field.
162 162  * If you rename the file, please make it executable.
163 163  * See this link for lua.bit module: [[http:~~/~~/luaforge.net/projects/bit/>>url:http://luaforge.net/projects/bit/]]
... ... @@ -198,11 +198,14 @@
198 198  * **Frequency:** Transmit Frequency: example: 923300000
199 199  * **rxwindow:** transmit on Rx1Window or Rx2Window.
200 200  
194 +
195 +
201 201  (% style="color:blue" %)**Completely exmaple:**
202 202  
203 203  * **Old version:** echo 018193F4,imme,hex,0101 > /var/iot/push/test
204 204  * **New version:** echo 018193F4,imme,hex,0101,20,1,SF12,923300000,2 > /var/iot/push/test
205 205  
201 +
206 206  (% style="color:#037691" %)**Downstream Frequency**
207 207  
208 208  The LG308 will use the RX2 window info to send the downstream payload, use the default LoRaWAN settings, as below:
... ... @@ -216,6 +216,7 @@
216 216  * IN865: 866.55Mhz, SF10 BW125
217 217  * RU864: 869.1Mhz, SF12 BW125
218 218  
215 +
219 219  (% style="color:#037691" %)**Examples:**
220 220  
221 221  (% class="box" %)
... ... @@ -222,19 +222,25 @@
222 222  (((
223 223  we can use echo command to create files in LG308 for downstream.
224 224  root@dragino-1d25dc:~~# echo 2602111D,time,hex,12345678 > /var/iot/push/test
222 +)))
225 225  
226 -
224 +(% class="box" %)
225 +(((
227 227  **1)** From logread -f of gateway, we can see it has been added as pedning.
228 228  lora_pkt_fwd[4286]: INFO~~ [DNLK]Looking file : test
229 229  lora_pkt_fwd[4286]: INFO~~ [DNLK]devaddr:2602111D, txmode:time, pdfm:hex, size:4, payload1:4Vx,payload_hex:77C1BB90
230 230  lora_pkt_fwd[4286]: INFO~~ [DNLK] DNLINK PENDING!(1 elems).
230 +)))
231 231  
232 -
232 +(% class="box" %)
233 +(((
233 233  **2)** When there is an upstrea from end node, this downstream will be sent and shows:
234 234  lora_pkt_fwd[4286]: INFO: tx_start_delay=1497 (1497.000000) - (1497, bw_delay=0.000000, notch_delay=0.000000)
235 235  lora_pkt_fwd[4286]: [LGWSEND]lgw_send done: count_us=3537314420, freq=923300000, size=17
237 +)))
236 236  
237 -
239 +(% class="box" %)
240 +(((
238 238  **3)** and the end node will got:
239 239  [5764825]~*~*~*~** UpLinkCounter= 98 ~*~*~*~**
240 240  [5764827]TX on freq 905300000 Hz at DR 0
... ... @@ -247,8 +247,10 @@
247 247  Rssi= -41
248 248  Receive data
249 249  (% style="color:#037691" %)**2:12345678**  (%%) ~-~-> Hex
253 +)))
250 250  
251 -
255 +(% class="box" %)
256 +(((
252 252  **4) **If we use the command "echo 2602111D,time,txt,12345678 > /var/iot/push/test" for downstream, the end node will got:
253 253  [5955877]~*~*~*~** UpLinkCounter= 102 ~*~*~*~**
254 254  [5955879]TX on freq 904100000 Hz at DR 0
... ... @@ -264,7 +264,6 @@
264 264  )))
265 265  
266 266  
267 -
268 268  = 3. Example 1: Communicate with LT-22222-L =
269 269  
270 270  
... ... @@ -308,7 +308,6 @@
308 308  #  whether the Device 2 has been changed.//
309 309  )))
310 310  
311 -
312 312  **~1. Input keys**
313 313  
314 314  [[image:image-20220527162450-3.png]]
... ... @@ -318,7 +318,6 @@
318 318  
319 319  **2. Make sure the LPS8 and LT use the same frequency bands, choose EU868 in this test.**
320 320  
321 -
322 322  **3. Choose Built-in server**
323 323  
324 324  [[image:image-20220527162518-4.png]]
... ... @@ -328,7 +328,7 @@
328 328  
329 329  **4. Run the script.**
330 330  
331 -[[image:image-20220722115213-2.png]]
333 +[[image:image-20220527162552-5.png]]
332 332  
333 333  Run the script
334 334  
... ... @@ -335,12 +335,11 @@
335 335  
336 336  **5. Output:**
337 337  
338 -[[image:image-20220722115133-1.png]]
340 +[[image:image-20220527162619-6.png]]
339 339  
340 340  Output from LPS8
341 341  
342 342  
343 -
344 344  = 4. Example 2: Communicate to TCP Server =
345 345  
346 346  
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