Last modified by Xiaoling on 2023/04/20 18:14
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.Xiao ye1 +XWiki.Xiaoling - Content
-
... ... @@ -1,12 +1,10 @@ 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. ... ... @@ -32,15 +32,13 @@ 32 32 33 33 (% class="box infomessage" %) 34 34 ((( 35 - **AT+NWKSKEY=72 32 63 95 dd 8f e2 b2 13 66 e4 35 93 8f 55 df33 +AT+NWKSKEY=72 32 63 95 dd 8f e2 b2 13 66 e4 35 93 8f 55 df 36 36 AT+APPSKEY=b3 17 f8 14 7a 43 27 8a 6a 31 c4 47 3d 55 5d 33 37 -AT+DADDR=2602111D **35 +AT+DADDR=2602111D 38 38 ))) 39 39 40 40 ((( 41 41 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. 42 - 43 - 44 44 ))) 45 45 46 46 We need to input above keys in LG308 and enable ABP decryption. ... ... @@ -50,10 +50,8 @@ 50 50 Input the ABP keys in LG308 51 51 52 52 53 - 54 54 == 2.1 Upstream == 55 55 56 - 57 57 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. 58 58 59 59 ((( ... ... @@ -62,7 +62,7 @@ 62 62 63 63 [[image:image-20220527161149-2.png]] 64 64 65 -LG308 log by " (% style="color:red" %)**logread -f**"(%%)command59 +LG308 log by "logread -f" command 66 66 67 67 68 68 The data of End Node is stored in the file /var/iot/channels/2602111D. We can use hexdump command to check it. ... ... @@ -75,11 +75,10 @@ 75 75 000001c 76 76 ))) 77 77 78 -* **RSSI**: 4646 4646 4646 3946 = 0xFFFF FF9F : So RSSI = (0xFFFF FF9F - 0x100000000) = -9779 -* **SNR**: 3030 3030 3030 3546 = 0x0000 005F = 95, need to divide 10 so SNR is 9.580 -* **Payload**: 0xcc0c 0b63 0266 017f ff7f ff0072 +* RSSI: 4646 4646 4646 3946 = 0xFFFF FF9F : So RSSI = (0xFFFF FF9F - 0x100000000) = -97 73 +* SNR: 3030 3030 3030 3546 = 0x0000 005F = 95, need to divide 10 so SNR is 9.5 74 +* 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,17 +90,14 @@ 90 90 000001c 91 91 ))) 92 92 93 - 94 94 (% class="box" %) 95 95 ((( 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.88 +(% 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. 97 97 ))) 98 98 99 99 100 - 101 101 === 2.2.1 Decode Method === 102 102 103 - 104 104 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. 105 105 106 106 For example we have a LHT65 , works in ABP mode and gateway successful get the data, which are: ... ... @@ -113,7 +113,6 @@ 113 113 000001c 114 114 ))) 115 115 116 - 117 117 If we choose ASCII decoder, the MQTT process will send out with mqtt-data: 118 118 119 119 (% class="box" %) ... ... @@ -123,7 +123,6 @@ 123 123 Sun Sep 27 04:33:16 2020 user.notice root: [IoT.MQTT]:mqtt_data[-m]: (% style="color:#037691" %)**ffffffe700000048ccd17fff7fff017fff7fff00** 124 124 ))) 125 125 126 - 127 127 If we choose Decode_LHT65, the MQTT process will send out with mqtt-data 128 128 129 129 (% class="box" %) ... ... @@ -137,27 +137,21 @@ 137 137 Above scripts are store in /etc/lora/decoder/. User can put their scripts here and select it in the UI. 138 138 139 139 140 - 141 141 === 2.2.2 How to Decode My End Node === 142 142 130 +1/ Configure the ABP keys for your end node in the gateway. enable ABP decode in Web UI 143 143 144 - **1.**ConfiguretheABP keys for yourendnodein thegateway.enable ABP decode inWeb UI132 +2/ Don't choose MQTT service, use LoRaWAN. 145 145 146 - **2.**Don'tchooseMQTTservice,useLoRaWAN.134 +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 147 147 148 - **3.**Whenyourendnodesendamessage tothegateway,therewill beafilestore in/var/iot/channels.fullpath shouldbe /var/iot/channels/END_NODE_DEV_ADDR136 +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: 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: 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.141 +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/]] ... ... @@ -166,10 +166,8 @@ 166 166 * User can use other language ,not limited to Lua, just make sure the return is what you want to send. 167 167 168 168 169 - 170 170 == 2.2 Downstream == 171 171 172 - 173 173 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 174 174 175 175 The file should use below format: ... ... @@ -180,29 +180,30 @@ 180 180 181 181 (% style="color:#037691" %)**dev_addr,imme/time,txt/hex,payload,txpw,txbw,SF,frequency,rxwindow** 182 182 183 -* **dev_addr:**Inptu the device address184 -* **imme/time:**163 +* dev_addr: Inptu the device address 164 +* imme/time: 185 185 ** imme: send downstream immediately,For Class C end node. 186 186 ** time: send downstream after receive device's uplink. For Class A end node 187 -* **txt/hex:**167 +* txt/hex: 188 188 ** txt: send payload in ASCII 189 189 ** hex: send payload in HEX 190 -* **payload:**payload to be sent, payload lenght should match the LoRaWAN protocol requirement.191 -* **txpw:**Transmit Power. example: 20192 -* **txbw:**bandwidth:170 +* payload: payload to be sent, payload lenght should match the LoRaWAN protocol requirement. 171 +* txpw: Transmit Power. example: 20 172 +* txbw: bandwidth: 193 193 ** 1: 500 kHz 194 194 ** 2: 250 kHz 195 195 ** 3: 125 kHz 196 196 ** 4: 62.5 kHz 197 -* **SF:**Spreading Factor : SF7/SF8/SF9/SF10/SF11/SF12198 -* **Frequency:**Transmit Frequency: example: 923300000199 -* **rxwindow:**transmit on Rx1Window or Rx2Window.177 +* SF: Spreading Factor : SF7/SF8/SF9/SF10/SF11/SF12 178 +* Frequency: Transmit Frequency: example: 923300000 179 +* rxwindow: transmit on Rx1Window or Rx2Window. 200 200 201 - (% style="color:blue" %)**Completely exmaple:**181 +Completely exmaple: 202 202 203 -* **Old version:**echo 018193F4,imme,hex,0101 > /var/iot/push/test204 -* **New version:**echo 018193F4,imme,hex,0101,20,1,SF12,923300000,2 > /var/iot/push/test183 +* Old version: echo 018193F4,imme,hex,0101 > /var/iot/push/test 184 +* New version: echo 018193F4,imme,hex,0101,20,1,SF12,923300000,2 > /var/iot/push/test 205 205 186 + 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 200 + 219 219 (% style="color:#037691" %)**Examples:** 220 220 221 221 (% class="box" %) ... ... @@ -222,20 +222,26 @@ 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 207 +))) 225 225 226 - 227 -**1)** From logread -f of gateway, we can see it has been added as pedning. 209 +(% class="box" %) 210 +((( 211 +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). 215 +))) 231 231 232 - 233 -**2)** When there is an upstrea from end node, this downstream will be sent and shows: 217 +(% class="box" %) 218 +((( 219 +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 222 +))) 236 236 237 - 238 -**3)** and the end node will got: 224 +(% class="box" %) 225 +((( 226 +3) and the end node will got: 239 239 [5764825]~*~*~*~** UpLinkCounter= 98 ~*~*~*~** 240 240 [5764827]TX on freq 905300000 Hz at DR 0 241 241 Update Interval: 60000 ms ... ... @@ -247,9 +247,11 @@ 247 247 Rssi= -41 248 248 Receive data 249 249 (% style="color:#037691" %)**2:12345678** (%%) ~-~-> Hex 238 +))) 250 250 251 - 252 -**4) **If we use the command "echo 2602111D,time,txt,12345678 > /var/iot/push/test" for downstream, the end node will got: 240 +(% class="box" %) 241 +((( 242 +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 255 255 Update Interval: 60000 ms ... ... @@ -264,15 +264,13 @@ 264 264 ))) 265 265 266 266 267 - 268 268 = 3. Example 1: Communicate with LT-22222-L = 269 269 270 - 271 271 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]] 272 272 273 273 (% class="box" %) 274 274 ((( 275 - //#!/bin/sh263 +#!/bin/sh 276 276 # This scripts shows how to use LPS8/LG308/DLOS8 to communicate with two LoRaWAN End Nodes, without the use of internet or LoRaWAN server 277 277 # 278 278 # Hardware Prepare: ... ... @@ -305,45 +305,41 @@ 305 305 # Device1: DI1: ON, DI2: ON , DO1: ON, DO2: ON 306 306 # Device2: DI1: OFF, DI2: OFF , DO1: ON, DO2: ON 307 307 # 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 308 -# whether the Device 2 has been changed. //296 +# whether the Device 2 has been changed. 309 309 ))) 310 310 299 +~1. Input keys 311 311 312 -**~1. Input keys** 313 - 314 314 [[image:image-20220527162450-3.png]] 315 315 316 316 Input Keys in LPS8 317 317 318 318 319 - **2. Make sure the LPS8 and LT use the same frequency bands, choose EU868 in this test.**306 +2. Make sure the LPS8 and LT use the same frequency bands, choose EU868 in this test. 320 320 308 +3. Choose Built-in server 321 321 322 -**3. Choose Built-in server** 323 - 324 324 [[image:image-20220527162518-4.png]] 325 325 326 326 Choose Built-in server 327 327 328 328 329 - **4. Run the script.**315 +4. Run the script. 330 330 331 -[[image:image-20220 722115213-2.png]]317 +[[image:image-20220527162552-5.png]] 332 332 333 333 Run the script 334 334 335 335 336 - **5. Output:**322 +5. Output: 337 337 338 -[[image:image-2022072 2115133-1.png]]324 +[[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 - 347 347 [[image:image-20220527162648-7.png]] 348 348 349 349 Network Structure ... ... @@ -357,7 +357,6 @@ 357 357 358 358 (% style="color:red" %)**Note: Firmware version must be higher than lgw-5.4.1607519907** 359 359 360 - 361 361 Assume we already set up ABP keys in the gateway: 362 362 363 363 [[image:image-20220527162852-8.png]] ... ... @@ -365,9 +365,8 @@ 365 365 Input Keys in LPS8 366 366 367 367 351 +run socket tool in PC 368 368 369 -**run socket tool in PC** 370 - 371 371 [[image:image-20220527163028-9.png]] 372 372 373 373 ... ... @@ -374,20 +374,17 @@ 374 374 Socket tool 375 375 376 376 359 +Input Server address and port 377 377 378 -**Input Server address and port** 379 - 380 380 [[image:image-20220527163106-10.png]] 381 381 382 382 Input Server address and port 383 383 384 384 366 +See value receive in socket tool. : 385 385 386 -**See value receive in socket tool:** 387 - 388 388 [[image:image-20220527163144-11.png]] 389 389 390 390 value receive in socket tool 391 391 392 - 393 393 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