Last modified by Xiaoling on 2023/04/20 18:14
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 2 removed)
Details
- Page properties
-
- Content
-
... ... @@ -1,19 +1,15 @@ 1 -** Table ofContents:**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. 13 -* 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 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]]). 14 14 15 - 16 - 17 17 ((( 18 18 The basic of this feature is the decoding of (% style="color:red" %)**LoRaWAN ABP End Node**(%%). Requirements: 19 19 ))) ... ... @@ -22,9 +22,6 @@ 22 22 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]] 23 23 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/]](%%)** 24 24 25 - 26 - 27 - 28 28 = 2. How it works = 29 29 30 30 ... ... @@ -35,45 +35,35 @@ 35 35 36 36 (% class="box infomessage" %) 37 37 ((( 38 - **AT+NWKSKEY=72 32 63 95 dd 8f e2 b2 13 66 e4 35 93 8f 55 df31 +AT+NWKSKEY=72 32 63 95 dd 8f e2 b2 13 66 e4 35 93 8f 55 df 39 39 AT+APPSKEY=b3 17 f8 14 7a 43 27 8a 6a 31 c4 47 3d 55 5d 33 40 -AT+DADDR=2602111D **33 +AT+DADDR=2602111D 41 41 ))) 42 42 43 43 ((( 44 44 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. 45 - 46 - 47 47 ))) 48 48 49 49 We need to input above keys in LG308 and enable ABP decryption. 50 50 51 - 52 52 [[image:image-20220527161119-1.png]] 53 53 54 - 55 55 Input the ABP keys in LG308 56 56 57 57 58 - 59 59 == 2.1 Upstream == 60 60 61 - 62 62 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. 63 63 64 64 ((( 65 -We can see the log of LG308 to know this packet arrive. 66 - 67 - 52 +We can see the log of LG308 to know this packet arrive 68 68 ))) 69 69 70 70 [[image:image-20220527161149-2.png]] 71 71 57 +LG308 log by "logread -f" command 72 72 73 -LG308 log by "(% style="color:red" %)**logread -f**" (%%)command 74 74 75 - 76 - 77 77 The data of End Node is stored in the file /var/iot/channels/2602111D. We can use hexdump command to check it. 78 78 79 79 (% class="box" %) ... ... @@ -84,12 +84,10 @@ 84 84 000001c 85 85 ))) 86 86 87 -* **RSSI**: 4646 4646 4646 3946 = 0xFFFF FF9F : So RSSI = (0xFFFF FF9F - 0x100000000) = -9788 -* **SNR**: 3030 3030 3030 3546 = 0x0000 005F = 95, need to divide 10 so SNR is 9.589 -* **Payload**: 0xcc0c 0b63 0266 017f ff7f ff0070 +* RSSI: 4646 4646 4646 3946 = 0xFFFF FF9F : So RSSI = (0xFFFF FF9F - 0x100000000) = -97 71 +* SNR: 3030 3030 3030 3546 = 0x0000 005F = 95, need to divide 10 so SNR is 9.5 72 +* Payload: 0xcc0c 0b63 0266 017f ff7f ff00 90 90 91 - 92 - 93 93 (% class="box" %) 94 94 ((( 95 95 (% 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: ... ... @@ -100,17 +100,14 @@ 100 100 000001c 101 101 ))) 102 102 103 - 104 104 (% class="box" %) 105 105 ((( 106 -(% 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.86 +(% 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. 107 107 ))) 108 108 109 109 110 - 111 111 === 2.2.1 Decode Method === 112 112 113 - 114 114 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. 115 115 116 116 For example we have a LHT65 , works in ABP mode and gateway successful get the data, which are: ... ... @@ -123,7 +123,6 @@ 123 123 000001c 124 124 ))) 125 125 126 - 127 127 If we choose ASCII decoder, the MQTT process will send out with mqtt-data: 128 128 129 129 (% class="box" %) ... ... @@ -133,7 +133,6 @@ 133 133 Sun Sep 27 04:33:16 2020 user.notice root: [IoT.MQTT]:mqtt_data[-m]: (% style="color:#037691" %)**ffffffe700000048ccd17fff7fff017fff7fff00** 134 134 ))) 135 135 136 - 137 137 If we choose Decode_LHT65, the MQTT process will send out with mqtt-data 138 138 139 139 (% class="box" %) ... ... @@ -147,27 +147,21 @@ 147 147 Above scripts are store in /etc/lora/decoder/. User can put their scripts here and select it in the UI. 148 148 149 149 150 - 151 151 === 2.2.2 How to Decode My End Node === 152 152 128 +1/ Configure the ABP keys for your end node in the gateway. enable ABP decode in Web UI 153 153 154 - **1.**ConfiguretheABP keys for yourendnodein thegateway.enable ABP decode inWeb UI130 +2/ Don't choose MQTT service, use LoRaWAN. 155 155 156 - **2.**Don'tchooseMQTTservice,useLoRaWAN.132 +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 157 157 158 - **3.**Whenyourendnodesendamessage tothegateway,therewill beafilestore in/var/iot/channels.fullpath shouldbe /var/iot/channels/END_NODE_DEV_ADDR134 +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: 159 159 160 -**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: 161 - 162 162 {{{/etc/lora/decoder/Dragino_LHT65 END_NODE_DEV_ADDR 163 163 }}} 164 164 165 - **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.139 +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: 166 166 167 - 168 -(% style="color:red" %) 169 -**Some notice:** 170 - 171 171 * RSSI and SNR are added when gateway receive the packet, so there is always this field. 172 172 * If you rename the file, please make it executable. 173 173 * See this link for lua.bit module: [[http:~~/~~/luaforge.net/projects/bit/>>url:http://luaforge.net/projects/bit/]] ... ... @@ -176,11 +176,8 @@ 176 176 * User can use other language ,not limited to Lua, just make sure the return is what you want to send. 177 177 178 178 179 - 180 - 181 181 == 2.2 Downstream == 182 182 183 - 184 184 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 185 185 186 186 The file should use below format: ... ... @@ -187,40 +187,35 @@ 187 187 188 188 (% style="color:#037691" %)**dev_addr,imme/time,txt/hex,payload** 189 189 190 - 191 191 Since fimware > Dragino-v2 lgw-5.4.1608518541 . Support more option 192 192 193 193 (% style="color:#037691" %)**dev_addr,imme/time,txt/hex,payload,txpw,txbw,SF,frequency,rxwindow** 194 194 195 -* **dev_addr:**Inptu the device address196 -* **imme/time:**161 +* dev_addr: Inptu the device address 162 +* imme/time: 197 197 ** imme: send downstream immediately,For Class C end node. 198 198 ** time: send downstream after receive device's uplink. For Class A end node 199 -* **txt/hex:**165 +* txt/hex: 200 200 ** txt: send payload in ASCII 201 201 ** hex: send payload in HEX 202 -* **payload:**payload to be sent, payload lenght should match the LoRaWAN protocol requirement.203 -* **txpw:**Transmit Power. example: 20204 -* **txbw:**bandwidth:168 +* payload: payload to be sent, payload lenght should match the LoRaWAN protocol requirement. 169 +* txpw: Transmit Power. example: 20 170 +* txbw: bandwidth: 205 205 ** 1: 500 kHz 206 206 ** 2: 250 kHz 207 207 ** 3: 125 kHz 208 208 ** 4: 62.5 kHz 209 -* **SF:**Spreading Factor : SF7/SF8/SF9/SF10/SF11/SF12210 -* **Frequency:**Transmit Frequency: example: 923300000211 -* **rxwindow:**transmit on Rx1Window or Rx2Window.175 +* SF: Spreading Factor : SF7/SF8/SF9/SF10/SF11/SF12 176 +* Frequency: Transmit Frequency: example: 923300000 177 +* rxwindow: transmit on Rx1Window or Rx2Window. 212 212 179 +Completely exmaple: 213 213 181 +* Old version: echo 018193F4,imme,hex,0101 > /var/iot/push/test 182 +* New version: echo 018193F4,imme,hex,0101,20,1,SF12,923300000,2 > /var/iot/push/test 214 214 215 -(% style="color: blue" %)**Completelyexmaple:**184 +(% style="color:#037691" %)**Downstream Frequency** 216 216 217 -* **Old version:** echo 018193F4,imme,hex,0101 > /var/iot/push/test 218 -* **New version:** echo 018193F4,imme,hex,0101,20,1,SF12,923300000,2 > /var/iot/push/test 219 - 220 - 221 - 222 -(% style="color:#037691" %)**Downstream Frequency:** 223 - 224 224 The LG308 will use the RX2 window info to send the downstream payload, use the default LoRaWAN settings, as below: 225 225 226 226 * EU868: 869.525Mhz, DR0(SF12BW125) ... ... @@ -232,8 +232,6 @@ 232 232 * IN865: 866.55Mhz, SF10 BW125 233 233 * RU864: 869.1Mhz, SF12 BW125 234 234 235 - 236 - 237 237 (% style="color:#037691" %)**Examples:** 238 238 239 239 (% class="box" %) ... ... @@ -240,20 +240,26 @@ 240 240 ((( 241 241 we can use echo command to create files in LG308 for downstream. 242 242 root@dragino-1d25dc:~~# echo 2602111D,time,hex,12345678 > /var/iot/push/test 203 +))) 243 243 244 - 245 -**1)** From logread -f of gateway, we can see it has been added as pedning. 205 +(% class="box" %) 206 +((( 207 +1) From logread -f of gateway, we can see it has been added as pedning. 246 246 lora_pkt_fwd[4286]: INFO~~ [DNLK]Looking file : test 247 247 lora_pkt_fwd[4286]: INFO~~ [DNLK]devaddr:2602111D, txmode:time, pdfm:hex, size:4, payload1:4Vx,payload_hex:77C1BB90 248 248 lora_pkt_fwd[4286]: INFO~~ [DNLK] DNLINK PENDING!(1 elems). 211 +))) 249 249 250 - 251 -**2)** When there is an upstrea from end node, this downstream will be sent and shows: 213 +(% class="box" %) 214 +((( 215 +2) When there is an upstrea from end node, this downstream will be sent and shows: 252 252 lora_pkt_fwd[4286]: INFO: tx_start_delay=1497 (1497.000000) - (1497, bw_delay=0.000000, notch_delay=0.000000) 253 253 lora_pkt_fwd[4286]: [LGWSEND]lgw_send done: count_us=3537314420, freq=923300000, size=17 218 +))) 254 254 255 - 256 -**3)** and the end node will got: 220 +(% class="box" %) 221 +((( 222 +3) and the end node will got: 257 257 [5764825]~*~*~*~** UpLinkCounter= 98 ~*~*~*~** 258 258 [5764827]TX on freq 905300000 Hz at DR 0 259 259 Update Interval: 60000 ms ... ... @@ -265,9 +265,11 @@ 265 265 Rssi= -41 266 266 Receive data 267 267 (% style="color:#037691" %)**2:12345678** (%%) ~-~-> Hex 234 +))) 268 268 269 - 270 -**4) **If we use the command "echo 2602111D,time,txt,12345678 > /var/iot/push/test" for downstream, the end node will got: 236 +(% class="box" %) 237 +((( 238 +4) If we use the command "echo 2602111D,time,txt,12345678 > /var/iot/push/test" for downstream, the end node will got: 271 271 [5955877]~*~*~*~** UpLinkCounter= 102 ~*~*~*~** 272 272 [5955879]TX on freq 904100000 Hz at DR 0 273 273 Update Interval: 60000 ms ... ... @@ -282,15 +282,13 @@ 282 282 ))) 283 283 284 284 285 - 286 286 = 3. Example 1: Communicate with LT-22222-L = 287 287 288 - 289 289 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]] 290 290 291 291 (% class="box" %) 292 292 ((( 293 - //#!/bin/sh259 +#!/bin/sh 294 294 # This scripts shows how to use LPS8/LG308/DLOS8 to communicate with two LoRaWAN End Nodes, without the use of internet or LoRaWAN server 295 295 # 296 296 # Hardware Prepare: ... ... @@ -323,52 +323,41 @@ 323 323 # Device1: DI1: ON, DI2: ON , DO1: ON, DO2: ON 324 324 # Device2: DI1: OFF, DI2: OFF , DO1: ON, DO2: ON 325 325 # 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 326 -# whether the Device 2 has been changed. //292 +# whether the Device 2 has been changed. 327 327 ))) 328 328 295 +~1. Input keys 329 329 330 -(% style="color:blue" %)**1. Input keys** 331 - 332 - 333 333 [[image:image-20220527162450-3.png]] 334 334 335 335 Input Keys in LPS8 336 336 337 337 302 +2. Make sure the LPS8 and LT use the same frequency bands, choose EU868 in this test. 338 338 339 - (% style="color:blue" %)**2.Make sure the LPS8 and LT use the same frequency bands, chooseEU868inthistest.**304 +3. Choose Built-in server 340 340 341 - 342 -(% style="color:blue" %)**3. Choose Built-in server** 343 - 344 - 345 345 [[image:image-20220527162518-4.png]] 346 346 347 347 Choose Built-in server 348 348 349 349 311 +4. Run the script. 350 350 351 - (% style="color:blue" %)**4.Run the script.**313 +[[image:image-20220527162552-5.png]] 352 352 353 - 354 -[[image:image-20220722115213-2.png]] 355 - 356 356 Run the script 357 357 358 358 318 +5. Output: 359 359 360 - (% style="color:blue" %)**5.Output:**320 +[[image:image-20220527162619-6.png]] 361 361 362 - 363 -[[image:image-20220722115133-1.png]] 364 - 365 365 Output from LPS8 366 366 367 367 368 - 369 369 = 4. Example 2: Communicate to TCP Server = 370 370 371 - 372 372 [[image:image-20220527162648-7.png]] 373 373 374 374 Network Structure ... ... @@ -382,7 +382,6 @@ 382 382 383 383 (% style="color:red" %)**Note: Firmware version must be higher than lgw-5.4.1607519907** 384 384 385 - 386 386 Assume we already set up ABP keys in the gateway: 387 387 388 388 [[image:image-20220527162852-8.png]] ... ... @@ -390,10 +390,8 @@ 390 390 Input Keys in LPS8 391 391 392 392 347 +run socket tool in PC 393 393 394 -(% style="color:blue" %)**run socket tool in PC** 395 - 396 - 397 397 [[image:image-20220527163028-9.png]] 398 398 399 399 ... ... @@ -400,22 +400,17 @@ 400 400 Socket tool 401 401 402 402 355 +Input Server address and port 403 403 404 -(% style="color:blue" %)**Input Server address and port** 405 - 406 - 407 407 [[image:image-20220527163106-10.png]] 408 408 409 409 Input Server address and port 410 410 411 411 362 +See value receive in socket tool. : 412 412 413 -(% style="color:blue" %)**See value receive in socket tool:** 414 - 415 - 416 416 [[image:image-20220527163144-11.png]] 417 417 418 418 value receive in socket tool 419 419 420 - 421 421 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