Last modified by Xiaoling on 2023/04/20 18:14
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 2 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Kilight1 +XWiki.Xiaoling - Content
-
... ... @@ -1,4 +1,5 @@ 1 -**Table of Contents:** 1 +* 2 +** Table of** **Contents: 2 2 3 3 {{toc/}} 4 4 ... ... @@ -20,7 +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 24 = 2. How it works = 25 25 26 26 ... ... @@ -44,14 +44,11 @@ 44 44 45 45 We need to input above keys in LG308 and enable ABP decryption. 46 46 47 - 48 48 [[image:image-20220527161119-1.png]] 49 49 50 - 51 51 Input the ABP keys in LG308 52 52 53 53 54 - 55 55 == 2.1 Upstream == 56 56 57 57 ... ... @@ -58,18 +58,14 @@ 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 - 58 +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 68 - 69 69 LG308 log by "(% style="color:red" %)**logread -f**" (%%)command 70 70 71 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" %) ... ... @@ -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 UI138 +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_ADDR142 +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/]] ... ... @@ -170,6 +170,7 @@ 170 170 * User can use other language ,not limited to Lua, just make sure the return is what you want to send. 171 171 172 172 159 + 173 173 == 2.2 Downstream == 174 174 175 175 ... ... @@ -179,9 +179,8 @@ 179 179 180 180 (% style="color:#037691" %)**dev_addr,imme/time,txt/hex,payload** 181 181 169 +Since fimware > Dragino-v2 lgw-5.4.1608518541 . Support more option 182 182 183 -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 184 - 185 185 (% style="color:#037691" %)**dev_addr,imme/time,txt/hex,payload,txpw,txbw,SF,frequency,rxwindow** 186 186 187 187 * **dev_addr:** Inptu the device address ... ... @@ -201,16 +201,17 @@ 201 201 * **SF:** Spreading Factor : SF7/SF8/SF9/SF10/SF11/SF12 202 202 * **Frequency:** Transmit Frequency: example: 923300000 203 203 * **rxwindow:** transmit on Rx1Window or Rx2Window. 204 -* **Fport: **Transmit port,example:8 205 205 206 206 207 207 (% style="color:blue" %)**Completely exmaple:** 208 208 209 209 * **Old version:** echo 018193F4,imme,hex,0101 > /var/iot/push/test 210 -* **New version:** echo 018193F4,imme,hex,0101,20,1,SF12,923300000,2 ,2> /var/iot/push/test195 +* **New version:** echo 018193F4,imme,hex,0101,20,1,SF12,923300000,2 > /var/iot/push/test 211 211 212 -(% style="color:#037691" %)**Downstream Frequency:** 213 213 198 + 199 +(% style="color:#037691" %)**Downstream Frequency** 200 + 214 214 The LG308 will use the RX2 window info to send the downstream payload, use the default LoRaWAN settings, as below: 215 215 216 216 * EU868: 869.525Mhz, DR0(SF12BW125) ... ... @@ -222,6 +222,8 @@ 222 222 * IN865: 866.55Mhz, SF10 BW125 223 223 * RU864: 869.1Mhz, SF12 BW125 224 224 212 + 213 + 225 225 (% style="color:#037691" %)**Examples:** 226 226 227 227 (% class="box" %) ... ... @@ -228,19 +228,25 @@ 228 228 ((( 229 229 we can use echo command to create files in LG308 for downstream. 230 230 root@dragino-1d25dc:~~# echo 2602111D,time,hex,12345678 > /var/iot/push/test 220 +))) 231 231 232 - 222 +(% class="box" %) 223 +((( 233 233 **1)** From logread -f of gateway, we can see it has been added as pedning. 234 234 lora_pkt_fwd[4286]: INFO~~ [DNLK]Looking file : test 235 235 lora_pkt_fwd[4286]: INFO~~ [DNLK]devaddr:2602111D, txmode:time, pdfm:hex, size:4, payload1:4Vx,payload_hex:77C1BB90 236 236 lora_pkt_fwd[4286]: INFO~~ [DNLK] DNLINK PENDING!(1 elems). 228 +))) 237 237 238 - 230 +(% class="box" %) 231 +((( 239 239 **2)** When there is an upstrea from end node, this downstream will be sent and shows: 240 240 lora_pkt_fwd[4286]: INFO: tx_start_delay=1497 (1497.000000) - (1497, bw_delay=0.000000, notch_delay=0.000000) 241 241 lora_pkt_fwd[4286]: [LGWSEND]lgw_send done: count_us=3537314420, freq=923300000, size=17 235 +))) 242 242 243 - 237 +(% class="box" %) 238 +((( 244 244 **3)** and the end node will got: 245 245 [5764825]~*~*~*~** UpLinkCounter= 98 ~*~*~*~** 246 246 [5764827]TX on freq 905300000 Hz at DR 0 ... ... @@ -253,8 +253,10 @@ 253 253 Rssi= -41 254 254 Receive data 255 255 (% style="color:#037691" %)**2:12345678** (%%) ~-~-> Hex 251 +))) 256 256 257 - 253 +(% class="box" %) 254 +((( 258 258 **4) **If we use the command "echo 2602111D,time,txt,12345678 > /var/iot/push/test" for downstream, the end node will got: 259 259 [5955877]~*~*~*~** UpLinkCounter= 102 ~*~*~*~** 260 260 [5955879]TX on freq 904100000 Hz at DR 0 ... ... @@ -270,7 +270,6 @@ 270 270 ))) 271 271 272 272 273 - 274 274 = 3. Example 1: Communicate with LT-22222-L = 275 275 276 276 ... ... @@ -314,46 +314,36 @@ 314 314 # whether the Device 2 has been changed.// 315 315 ))) 316 316 313 +**~1. Input keys** 317 317 318 -(% style="color:blue" %)**1. Input keys** 319 - 320 - 321 321 [[image:image-20220527162450-3.png]] 322 322 323 323 Input Keys in LPS8 324 324 325 325 320 +**2. Make sure the LPS8 and LT use the same frequency bands, choose EU868 in this test.** 326 326 327 - (% style="color:blue" %)**2.Make sure the LPS8 and LT use the same frequency bands, chooseEU868inthistest.**322 +**3. Choose Built-in server** 328 328 329 - 330 -(% style="color:blue" %)**3. Choose Built-in server** 331 - 332 - 333 333 [[image:image-20220527162518-4.png]] 334 334 335 335 Choose Built-in server 336 336 337 337 329 +**4. Run the script.** 338 338 339 - (% style="color:blue" %)**4.Run the script.**331 +[[image:image-20220527162552-5.png]] 340 340 341 - 342 -[[image:image-20220722115213-2.png]] 343 - 344 344 Run the script 345 345 346 346 336 +**5. Output:** 347 347 348 - (% style="color:blue" %)**5.Output:**338 +[[image:image-20220527162619-6.png]] 349 349 350 - 351 -[[image:image-20220722115133-1.png]] 352 - 353 353 Output from LPS8 354 354 355 355 356 - 357 357 = 4. Example 2: Communicate to TCP Server = 358 358 359 359 ... ... @@ -379,9 +379,8 @@ 379 379 380 380 381 381 382 - (% style="color:blue" %)**run socket tool in PC**368 +**run socket tool in PC** 383 383 384 - 385 385 [[image:image-20220527163028-9.png]] 386 386 387 387 ... ... @@ -389,9 +389,8 @@ 389 389 390 390 391 391 392 - (% style="color:blue" %)**Input Server address and port**377 +**Input Server address and port** 393 393 394 - 395 395 [[image:image-20220527163106-10.png]] 396 396 397 397 Input Server address and port ... ... @@ -398,9 +398,8 @@ 398 398 399 399 400 400 401 - (% style="color:blue" %)**See value receive in socket tool:**385 +**See value receive in socket tool:** 402 402 403 - 404 404 [[image:image-20220527163144-11.png]] 405 405 406 406 value receive in socket tool
- 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