Last modified by Xiaoling on 2023/04/20 18:14
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- 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. ... ... @@ -22,7 +22,6 @@ 22 22 23 23 24 24 25 - 26 26 = 2. How it works = 27 27 28 28 ... ... @@ -33,15 +33,13 @@ 33 33 34 34 (% class="box infomessage" %) 35 35 ((( 36 - **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 37 37 AT+APPSKEY=b3 17 f8 14 7a 43 27 8a 6a 31 c4 47 3d 55 5d 33 38 -AT+DADDR=2602111D **35 +AT+DADDR=2602111D 39 39 ))) 40 40 41 41 ((( 42 42 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. 43 - 44 - 45 45 ))) 46 46 47 47 We need to input above keys in LG308 and enable ABP decryption. ... ... @@ -53,7 +53,6 @@ 53 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,9 +75,9 @@ 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 82 (% class="box" %) 83 83 ((( ... ... @@ -91,13 +91,12 @@ 91 91 92 92 (% class="box" %) 93 93 ((( 94 -(% 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. 95 95 ))) 96 96 97 97 98 98 === 2.2.1 Decode Method === 99 99 100 - 101 101 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. 102 102 103 103 For example we have a LHT65 , works in ABP mode and gateway successful get the data, which are: ... ... @@ -110,7 +110,6 @@ 110 110 000001c 111 111 ))) 112 112 113 - 114 114 If we choose ASCII decoder, the MQTT process will send out with mqtt-data: 115 115 116 116 (% class="box" %) ... ... @@ -120,7 +120,6 @@ 120 120 Sun Sep 27 04:33:16 2020 user.notice root: [IoT.MQTT]:mqtt_data[-m]: (% style="color:#037691" %)**ffffffe700000048ccd17fff7fff017fff7fff00** 121 121 ))) 122 122 123 - 124 124 If we choose Decode_LHT65, the MQTT process will send out with mqtt-data 125 125 126 126 (% class="box" %) ... ... @@ -134,10 +134,8 @@ 134 134 Above scripts are store in /etc/lora/decoder/. User can put their scripts here and select it in the UI. 135 135 136 136 137 - 138 138 === 2.2.2 How to Decode My End Node === 139 139 140 - 141 141 1/ Configure the ABP keys for your end node in the gateway. enable ABP decode in Web UI 142 142 143 143 2/ Don't choose MQTT service, use LoRaWAN. ... ... @@ -159,10 +159,8 @@ 159 159 * User can use other language ,not limited to Lua, just make sure the return is what you want to send. 160 160 161 161 162 - 163 163 == 2.2 Downstream == 164 164 165 - 166 166 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 167 167 168 168 The file should use below format: ... ... @@ -173,32 +173,29 @@ 173 173 174 174 (% style="color:#037691" %)**dev_addr,imme/time,txt/hex,payload,txpw,txbw,SF,frequency,rxwindow** 175 175 176 -* **dev_addr:**Inptu the device address177 -* **imme/time:**163 +* dev_addr: Inptu the device address 164 +* imme/time: 178 178 ** imme: send downstream immediately,For Class C end node. 179 179 ** time: send downstream after receive device's uplink. For Class A end node 180 -* **txt/hex:**167 +* txt/hex: 181 181 ** txt: send payload in ASCII 182 182 ** hex: send payload in HEX 183 -* **payload:**payload to be sent, payload lenght should match the LoRaWAN protocol requirement.184 -* **txpw:**Transmit Power. example: 20185 -* **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: 186 186 ** 1: 500 kHz 187 187 ** 2: 250 kHz 188 188 ** 3: 125 kHz 189 189 ** 4: 62.5 kHz 190 -* **SF:**Spreading Factor : SF7/SF8/SF9/SF10/SF11/SF12191 -* **Frequency:**Transmit Frequency: example: 923300000192 -* **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. 193 193 181 +Completely exmaple: 194 194 183 +* 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 195 195 196 -(% style="color:blue" %)**Completely exmaple:** 197 - 198 -* **Old version:** echo 018193F4,imme,hex,0101 > /var/iot/push/test 199 -* **New version:** echo 018193F4,imme,hex,0101,20,1,SF12,923300000,2 > /var/iot/push/test 200 - 201 - 202 202 (% style="color:#037691" %)**Downstream Frequency** 203 203 204 204 The LG308 will use the RX2 window info to send the downstream payload, use the default LoRaWAN settings, as below: ... ... @@ -212,7 +212,6 @@ 212 212 * IN865: 866.55Mhz, SF10 BW125 213 213 * RU864: 869.1Mhz, SF12 BW125 214 214 215 - 216 216 (% style="color:#037691" %)**Examples:** 217 217 218 218 (% class="box" %) ... ... @@ -223,7 +223,7 @@ 223 223 224 224 (% class="box" %) 225 225 ((( 226 - **1)**From logread -f of gateway, we can see it has been added as pedning.209 +1) From logread -f of gateway, we can see it has been added as pedning. 227 227 lora_pkt_fwd[4286]: INFO~~ [DNLK]Looking file : test 228 228 lora_pkt_fwd[4286]: INFO~~ [DNLK]devaddr:2602111D, txmode:time, pdfm:hex, size:4, payload1:4Vx,payload_hex:77C1BB90 229 229 lora_pkt_fwd[4286]: INFO~~ [DNLK] DNLINK PENDING!(1 elems). ... ... @@ -231,7 +231,7 @@ 231 231 232 232 (% class="box" %) 233 233 ((( 234 - **2)**When there is an upstrea from end node, this downstream will be sent and shows:217 +2) When there is an upstrea from end node, this downstream will be sent and shows: 235 235 lora_pkt_fwd[4286]: INFO: tx_start_delay=1497 (1497.000000) - (1497, bw_delay=0.000000, notch_delay=0.000000) 236 236 lora_pkt_fwd[4286]: [LGWSEND]lgw_send done: count_us=3537314420, freq=923300000, size=17 237 237 ))) ... ... @@ -238,7 +238,7 @@ 238 238 239 239 (% class="box" %) 240 240 ((( 241 - **3)**and the end node will got:224 +3) and the end node will got: 242 242 [5764825]~*~*~*~** UpLinkCounter= 98 ~*~*~*~** 243 243 [5764827]TX on freq 905300000 Hz at DR 0 244 244 Update Interval: 60000 ms ... ... @@ -254,7 +254,7 @@ 254 254 255 255 (% class="box" %) 256 256 ((( 257 - **4)**If we use the command "echo 2602111D,time,txt,12345678 > /var/iot/push/test" for downstream, the end node will got:240 +4) If we use the command "echo 2602111D,time,txt,12345678 > /var/iot/push/test" for downstream, the end node will got: 258 258 [5955877]~*~*~*~** UpLinkCounter= 102 ~*~*~*~** 259 259 [5955879]TX on freq 904100000 Hz at DR 0 260 260 Update Interval: 60000 ms ... ... @@ -271,12 +271,11 @@ 271 271 272 272 = 3. Example 1: Communicate with LT-22222-L = 273 273 274 - 275 275 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]] 276 276 277 277 (% class="box" %) 278 278 ((( 279 - //#!/bin/sh261 +#!/bin/sh 280 280 # This scripts shows how to use LPS8/LG308/DLOS8 to communicate with two LoRaWAN End Nodes, without the use of internet or LoRaWAN server 281 281 # 282 282 # Hardware Prepare: ... ... @@ -309,10 +309,10 @@ 309 309 # Device1: DI1: ON, DI2: ON , DO1: ON, DO2: ON 310 310 # Device2: DI1: OFF, DI2: OFF , DO1: ON, DO2: ON 311 311 # 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 312 -# whether the Device 2 has been changed. //294 +# whether the Device 2 has been changed. 313 313 ))) 314 314 315 - **~1. Input keys**297 +~1. Input keys 316 316 317 317 [[image:image-20220527162450-3.png]] 318 318 ... ... @@ -319,9 +319,9 @@ 319 319 Input Keys in LPS8 320 320 321 321 322 - **2. Make sure the LPS8 and LT use the same frequency bands, choose EU868 in this test.**304 +2. Make sure the LPS8 and LT use the same frequency bands, choose EU868 in this test. 323 323 324 - **3. Choose Built-in server**306 +3. Choose Built-in server 325 325 326 326 [[image:image-20220527162518-4.png]] 327 327 ... ... @@ -328,7 +328,7 @@ 328 328 Choose Built-in server 329 329 330 330 331 - **4. Run the script.**313 +4. Run the script. 332 332 333 333 [[image:image-20220527162552-5.png]] 334 334 ... ... @@ -335,7 +335,7 @@ 335 335 Run the script 336 336 337 337 338 - **5. Output:**320 +5. Output: 339 339 340 340 [[image:image-20220527162619-6.png]] 341 341 ... ... @@ -344,7 +344,6 @@ 344 344 345 345 = 4. Example 2: Communicate to TCP Server = 346 346 347 - 348 348 [[image:image-20220527162648-7.png]] 349 349 350 350 Network Structure ... ... @@ -358,7 +358,6 @@ 358 358 359 359 (% style="color:red" %)**Note: Firmware version must be higher than lgw-5.4.1607519907** 360 360 361 - 362 362 Assume we already set up ABP keys in the gateway: 363 363 364 364 [[image:image-20220527162852-8.png]] ... ... @@ -366,9 +366,8 @@ 366 366 Input Keys in LPS8 367 367 368 368 349 +run socket tool in PC 369 369 370 -**run socket tool in PC** 371 - 372 372 [[image:image-20220527163028-9.png]] 373 373 374 374 ... ... @@ -375,20 +375,17 @@ 375 375 Socket tool 376 376 377 377 357 +Input Server address and port 378 378 379 -**Input Server address and port** 380 - 381 381 [[image:image-20220527163106-10.png]] 382 382 383 383 Input Server address and port 384 384 385 385 364 +See value receive in socket tool. : 386 386 387 -**See value receive in socket tool:** 388 - 389 389 [[image:image-20220527163144-11.png]] 390 390 391 391 value receive in socket tool 392 392 393 - 394 394 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.