Last modified by Xiaoling on 2023/04/20 18:14
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 9 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -1,14 +1,17 @@ 1 - **Contents:** 1 +* 2 +** Table of** **Contents: 2 2 3 3 {{toc/}} 4 4 5 5 7 + 6 6 = 1. Introduction = 7 7 10 + 8 8 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: 9 9 10 10 * No internet connection. 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 +* 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 Forward Instruction]]). 12 12 13 13 ((( 14 14 The basic of this feature is the decoding of (% style="color:red" %)**LoRaWAN ABP End Node**(%%). Requirements: ... ... @@ -28,13 +28,15 @@ 28 28 29 29 (% class="box infomessage" %) 30 30 ((( 31 -AT+NWKSKEY=72 32 63 95 dd 8f e2 b2 13 66 e4 35 93 8f 55 df 34 +**AT+NWKSKEY=72 32 63 95 dd 8f e2 b2 13 66 e4 35 93 8f 55 df 32 32 AT+APPSKEY=b3 17 f8 14 7a 43 27 8a 6a 31 c4 47 3d 55 5d 33 33 -AT+DADDR=2602111D 36 +AT+DADDR=2602111D** 34 34 ))) 35 35 36 36 ((( 37 37 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. 41 + 42 + 38 38 ))) 39 39 40 40 We need to input above keys in LG308 and enable ABP decryption. ... ... @@ -46,6 +46,7 @@ 46 46 47 47 == 2.1 Upstream == 48 48 54 + 49 49 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. 50 50 51 51 ((( ... ... @@ -54,7 +54,7 @@ 54 54 55 55 [[image:image-20220527161149-2.png]] 56 56 57 -LG308 log by "logread -f" command 63 +LG308 log by "(% style="color:red" %)**logread -f**" (%%)command 58 58 59 59 60 60 The data of End Node is stored in the file /var/iot/channels/2602111D. We can use hexdump command to check it. ... ... @@ -67,14 +67,14 @@ 67 67 000001c 68 68 ))) 69 69 70 -* 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 76 +* **RSSI**: 4646 4646 4646 3946 = 0xFFFF FF9F : So RSSI = (0xFFFF FF9F - 0x100000000) = -97 77 +* **SNR**: 3030 3030 3030 3546 = 0x0000 005F = 95, need to divide 10 so SNR is 9.5 78 +* **Payload**: 0xcc0c 0b63 0266 017f ff7f ff00 73 73 74 74 (% class="box" %) 75 75 ((( 76 76 (% 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: 77 -in LGT92, use **(% style="color:#037691" %)AT+SEND=12:hello world** (%%)to send ASCII string83 +in LGT92, use (% style="color:#037691" %)**AT+SEND=12:hello world** (%%)to send ASCII string 78 78 root@dragino-1d25dc:~~# hexdump /var/iot/channels/2602111D 79 79 0000000 4646 4646 4646 3946 3030 3030 3030 3546 80 80 0000010 6865 6c6c 6f20 776f 726c 6400 ~-~-> Got ASCII code "hello world" ... ... @@ -83,14 +83,15 @@ 83 83 84 84 (% class="box" %) 85 85 ((( 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.92 +(% 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. 87 87 ))) 88 88 89 89 90 90 === 2.2.1 Decode Method === 91 91 92 -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. 93 93 99 +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. 100 + 94 94 For example we have a LHT65 , works in ABP mode and gateway successful get the data, which are: 95 95 96 96 (% class="box" %) ... ... @@ -101,6 +101,7 @@ 101 101 000001c 102 102 ))) 103 103 111 + 104 104 If we choose ASCII decoder, the MQTT process will send out with mqtt-data: 105 105 106 106 (% class="box" %) ... ... @@ -107,9 +107,10 @@ 107 107 ((( 108 108 Sun Sep 27 04:33:16 2020 user.notice root: [IoT.MQTT]:pub_topic[-t]: dragino-1baf44/01826108/data 109 109 Sun Sep 27 04:33:16 2020 user.notice root: [IoT.MQTT]:decoder: ASCII 110 -Sun Sep 27 04:33:16 2020 user.notice root: [IoT.MQTT]:mqtt_data[-m]: ffffffe700000048ccd17fff7fff017fff7fff00 118 +Sun Sep 27 04:33:16 2020 user.notice root: [IoT.MQTT]:mqtt_data[-m]: (% style="color:#037691" %)**ffffffe700000048ccd17fff7fff017fff7fff00** 111 111 ))) 112 112 121 + 113 113 If we choose Decode_LHT65, the MQTT process will send out with mqtt-data 114 114 115 115 (% class="box" %) ... ... @@ -116,8 +116,8 @@ 116 116 ((( 117 117 Sun Sep 27 04:36:45 2020 user.notice root: [IoT.MQTT]:pub_topic[-t]: dragino-1baf44/01826108/data 118 118 Sun Sep 27 04:36:45 2020 user.notice root: [IoT.MQTT]:decoder: Dragino_LHT65 119 -Sun Sep 27 04:36:45 2020 user.notice root: [IoT.MQTT]:mqtt_data[-m]: {"Hum_SHT":32.7,"BatV":3.281,"TempC_DS":32.9, 120 -"EXT":"Temperature Sensor","RSSI":-24,"TempC_SHT":85.0,"SNR":8.2,"ext_sensor":0} 128 +Sun Sep 27 04:36:45 2020 user.notice root: [IoT.MQTT]:mqtt_data[-m]:** (% style="color:#037691" %){"Hum_SHT":32.7,"BatV":3.281,"TempC_DS":32.9, 129 +"EXT":"Temperature Sensor","RSSI":-24,"TempC_SHT":85.0,"SNR":8.2,"ext_sensor":0}(%%)** 121 121 ))) 122 122 123 123 Above scripts are store in /etc/lora/decoder/. User can put their scripts here and select it in the UI. ... ... @@ -125,6 +125,7 @@ 125 125 126 126 === 2.2.2 How to Decode My End Node === 127 127 137 + 128 128 1/ Configure the ABP keys for your end node in the gateway. enable ABP decode in Web UI 129 129 130 130 2/ Don't choose MQTT service, use LoRaWAN. ... ... @@ -145,43 +145,49 @@ 145 145 * the last line return is what will be used for MQTT 146 146 * User can use other language ,not limited to Lua, just make sure the return is what you want to send. 147 147 158 + 159 + 148 148 == 2.2 Downstream == 149 149 162 + 150 150 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 151 151 152 152 The file should use below format: 153 153 154 -(% class="mark" %)**dev_addr,imme/time,txt/hex,payload**167 +(% style="color:#037691" %)**dev_addr,imme/time,txt/hex,payload** 155 155 156 156 Since fimware > Dragino-v2 lgw-5.4.1608518541 . Support more option 157 157 158 -(% class="mark" %)**dev_addr,imme/time,txt/hex,payload,txpw,txbw,SF,frequency,rxwindow**171 +(% style="color:#037691" %)**dev_addr,imme/time,txt/hex,payload,txpw,txbw,SF,frequency,rxwindow** 159 159 160 -* dev_addr: Inptu the device address 161 -* imme/time: 173 +* **dev_addr:** Inptu the device address 174 +* **imme/time:** 162 162 ** imme: send downstream immediately,For Class C end node. 163 163 ** time: send downstream after receive device's uplink. For Class A end node 164 -* txt/hex: 177 +* **txt/hex:** 165 165 ** txt: send payload in ASCII 166 166 ** hex: send payload in HEX 167 -* payload: payload to be sent, payload lenght should match the LoRaWAN protocol requirement. 168 -* txpw: Transmit Power. example: 20 169 -* txbw: bandwidth: 180 +* **payload: **payload to be sent, payload lenght should match the LoRaWAN protocol requirement. 181 +* **txpw:** Transmit Power. example: 20 182 +* **txbw:** bandwidth: 170 170 ** 1: 500 kHz 171 171 ** 2: 250 kHz 172 172 ** 3: 125 kHz 173 173 ** 4: 62.5 kHz 174 -* SF: Spreading Factor : SF7/SF8/SF9/SF10/SF11/SF12 175 -* Frequency: Transmit Frequency: example: 923300000 176 -* rxwindow: transmit on Rx1Window or Rx2Window. 187 +* **SF:** Spreading Factor : SF7/SF8/SF9/SF10/SF11/SF12 188 +* **Frequency:** Transmit Frequency: example: 923300000 189 +* **rxwindow:** transmit on Rx1Window or Rx2Window. 177 177 178 -Completely exmaple: 179 179 180 -* Old version: echo 018193F4,imme,hex,0101 > /var/iot/push/test 181 -* New version: echo 018193F4,imme,hex,0101,20,1,SF12,923300000,2 > /var/iot/push/test 192 +(% style="color:blue" %)**Completely exmaple:** 182 182 183 -(% class="mark" %)**Downstream Frequency** 194 +* **Old version:** echo 018193F4,imme,hex,0101 > /var/iot/push/test 195 +* **New version:** echo 018193F4,imme,hex,0101,20,1,SF12,923300000,2 > /var/iot/push/test 184 184 197 + 198 + 199 +(% style="color:#037691" %)**Downstream Frequency** 200 + 185 185 The LG308 will use the RX2 window info to send the downstream payload, use the default LoRaWAN settings, as below: 186 186 187 187 * EU868: 869.525Mhz, DR0(SF12BW125) ... ... @@ -193,8 +193,10 @@ 193 193 * IN865: 866.55Mhz, SF10 BW125 194 194 * RU864: 869.1Mhz, SF12 BW125 195 195 196 -(% class="mark" %)**Examples:** 197 197 213 + 214 +(% style="color:#037691" %)**Examples:** 215 + 198 198 (% class="box" %) 199 199 ((( 200 200 we can use echo command to create files in LG308 for downstream. ... ... @@ -203,7 +203,7 @@ 203 203 204 204 (% class="box" %) 205 205 ((( 206 -1) From logread -f of gateway, we can see it has been added as pedning. 224 +**1)** From logread -f of gateway, we can see it has been added as pedning. 207 207 lora_pkt_fwd[4286]: INFO~~ [DNLK]Looking file : test 208 208 lora_pkt_fwd[4286]: INFO~~ [DNLK]devaddr:2602111D, txmode:time, pdfm:hex, size:4, payload1:4Vx,payload_hex:77C1BB90 209 209 lora_pkt_fwd[4286]: INFO~~ [DNLK] DNLINK PENDING!(1 elems). ... ... @@ -211,7 +211,7 @@ 211 211 212 212 (% class="box" %) 213 213 ((( 214 -2) When there is an upstrea from end node, this downstream will be sent and shows: 232 +**2)** When there is an upstrea from end node, this downstream will be sent and shows: 215 215 lora_pkt_fwd[4286]: INFO: tx_start_delay=1497 (1497.000000) - (1497, bw_delay=0.000000, notch_delay=0.000000) 216 216 lora_pkt_fwd[4286]: [LGWSEND]lgw_send done: count_us=3537314420, freq=923300000, size=17 217 217 ))) ... ... @@ -218,7 +218,7 @@ 218 218 219 219 (% class="box" %) 220 220 ((( 221 -3) and the end node will got: 239 +**3)** and the end node will got: 222 222 [5764825]~*~*~*~** UpLinkCounter= 98 ~*~*~*~** 223 223 [5764827]TX on freq 905300000 Hz at DR 0 224 224 Update Interval: 60000 ms ... ... @@ -229,12 +229,12 @@ 229 229 [5767501]rxDone 230 230 Rssi= -41 231 231 Receive data 232 -2:12345678 250 +(% style="color:#037691" %)**2:12345678** (%%) ~-~-> Hex 233 233 ))) 234 234 235 235 (% class="box" %) 236 236 ((( 237 -4) If we use the command "echo 2602111D,time,txt,12345678 > /var/iot/push/test" for downstream, the end node will got: 255 +**4) **If we use the command "echo 2602111D,time,txt,12345678 > /var/iot/push/test" for downstream, the end node will got: 238 238 [5955877]~*~*~*~** UpLinkCounter= 102 ~*~*~*~** 239 239 [5955879]TX on freq 904100000 Hz at DR 0 240 240 Update Interval: 60000 ms ... ... @@ -245,16 +245,18 @@ 245 245 [5958595]rxDone 246 246 Rssi= -37 247 247 Receive data 248 -2:3132333435363738 ~-~-> ASCII string "12345678" 266 +(% style="color:#037691" %)**2:3132333435363738**(%%) ~-~-> ASCII string "12345678" 249 249 ))) 250 250 269 + 251 251 = 3. Example 1: Communicate with LT-22222-L = 252 252 272 + 253 253 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]] 254 254 255 255 (% class="box" %) 256 256 ((( 257 -#!/bin/sh 277 +//#!/bin/sh 258 258 # This scripts shows how to use LPS8/LG308/DLOS8 to communicate with two LoRaWAN End Nodes, without the use of internet or LoRaWAN server 259 259 # 260 260 # Hardware Prepare: ... ... @@ -287,40 +287,44 @@ 287 287 # Device1: DI1: ON, DI2: ON , DO1: ON, DO2: ON 288 288 # Device2: DI1: OFF, DI2: OFF , DO1: ON, DO2: ON 289 289 # 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 290 -# whether the Device 2 has been changed. 310 +# whether the Device 2 has been changed.// 291 291 ))) 292 292 293 -~1. Input keys 313 +**~1. Input keys** 294 294 295 -[[image: https://wiki.dragino.com/images/thumb/b/bf/LPS8_LT-22222_1.png/600px-LPS8_LT-22222_1.png||height="335" width="600"]]315 +[[image:image-20220527162450-3.png]] 296 296 297 297 Input Keys in LPS8 298 298 299 -2. Make sure the LPS8 and LT use the same frequency bands, choose EU868 in this test. 300 300 301 - 3.ChooseBuilt-in server320 +**2. Make sure the LPS8 and LT use the same frequency bands, choose EU868 in this test.** 302 302 303 - [[image:https://wiki.dragino.com/images/thumb/d/d7/LPS8_LT-22222_2.png/600px-LPS8_LT-22222_2.png||height="264"width="600"]]322 +**3. Choose Built-in server** 304 304 324 +[[image:image-20220527162518-4.png]] 325 + 305 305 Choose Built-in server 306 306 307 -4. Run the script. 308 308 309 - [[image:https://wiki.dragino.com/images/thumb/3/39/LPS8_LT-22222_3.png/600px-LPS8_LT-22222_3.png||height="389"width="600"]]329 +**4. Run the script.** 310 310 331 +[[image:image-20220527162552-5.png]] 332 + 311 311 Run the script 312 312 313 -5. Output: 314 314 315 - [[image:https://wiki.dragino.com/images/thumb/f/fe/LPS8_LT-22222_4.png/600px-LPS8_LT-22222_4.png||height="433" width="600"]]336 +**5. Output:** 316 316 338 +[[image:image-20220527162619-6.png]] 339 + 317 317 Output from LPS8 318 318 319 319 320 320 = 4. Example 2: Communicate to TCP Server = 321 321 322 -[[image:https://wiki.dragino.com/images/thumb/7/75/LPS8_TCP_0.png/600px-LPS8_TCP_0.png||height="370" width="600"]] 323 323 346 +[[image:image-20220527162648-7.png]] 347 + 324 324 Network Structure 325 325 326 326 ... ... @@ -327,34 +327,42 @@ 327 327 Full instruction video inlcude how to write scripts to fit server needed is here: 328 328 329 329 330 -(% class="mark" %)**Video Instruction**: [[https:~~/~~/youtu.be/-nevW6U2TsE>>url:https://youtu.be/-nevW6U2TsE]]354 +(% style="color:#037691" %)**Video Instruction**(%%): **[[https:~~/~~/youtu.be/-nevW6U2TsE>>url:https://youtu.be/-nevW6U2TsE]]** 331 331 332 -(% class="mark" %)**Note: Firmware version must be higher than lgw-5.4.1607519907** 333 333 357 +(% style="color:red" %)**Note: Firmware version must be higher than lgw-5.4.1607519907** 358 + 359 + 334 334 Assume we already set up ABP keys in the gateway: 335 335 336 -[[image: https://wiki.dragino.com/images/thumb/b/bf/LPS8_LT-22222_1.png/600px-LPS8_LT-22222_1.png||height="335" width="600"]]362 +[[image:image-20220527162852-8.png]] 337 337 338 338 Input Keys in LPS8 339 339 340 -run socket tool in PC 341 341 342 -[[image:https://wiki.dragino.com/images/thumb/4/4b/LPS8_TCP_2.png/600px-LPS8_TCP_2.png||height="212" width="600"]] 343 343 368 +**run socket tool in PC** 369 + 370 +[[image:image-20220527163028-9.png]] 371 + 372 + 344 344 Socket tool 345 345 346 346 347 -Input Server address and port 348 348 349 - [[image:https://wiki.dragino.com/images/thumb/c/c6/LPS8_TCP_3.png/600px-LPS8_TCP_3.png||height="306" width="600"]]377 +**Input Server address and port** 350 350 379 +[[image:image-20220527163106-10.png]] 380 + 351 351 Input Server address and port 352 352 353 353 354 -See value receive in socket tool. : 355 355 356 - [[image:https://wiki.dragino.com/images/thumb/2/20/LPS8_TCP_4.png/600px-LPS8_TCP_4.png||height="219"width="600"]]385 +**See value receive in socket tool:** 357 357 387 +[[image:image-20220527163144-11.png]] 388 + 358 358 value receive in socket tool 359 359 391 + 360 360 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-20220527162450-3.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +125.4 KB - Content
- image-20220527162518-4.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +72.8 KB - Content
- image-20220527162552-5.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +33.6 KB - Content
- image-20220527162619-6.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +41.0 KB - Content
- image-20220527162648-7.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +151.7 KB - Content
- image-20220527162852-8.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +125.6 KB - Content
- image-20220527163028-9.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +32.9 KB - Content
- image-20220527163106-10.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +34.5 KB - Content
- image-20220527163144-11.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +107.7 KB - Content