Last modified by Xiaoling on 2023/04/20 18:14
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 6 removed)
Details
- Page properties
-
- Content
-
... ... @@ -11,35 +11,32 @@ 11 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]]). 12 12 13 13 ((( 14 -The basic of this feature is the decoding of (% style="color:red" %)**LoRaWAN ABP End Node**(%%). Requirements: 14 + 15 +The basic of this feature is the decoding of LoRaWAN ABP End Node. Requirements: 15 15 ))) 16 16 17 17 1. LoRaWAN End Node in ABP mode. Make sure your end node works in this mode. End node most are default set to OTAA mode 18 18 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]] 19 -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/]](%%)**20 +1. Firmware version for below instruction:[[Since LG02_LG08~~-~~-build-v5.4.1593400722-20200629-1120>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/]] 20 20 22 + 21 21 = 2. How it works = 22 22 23 23 24 - (% style="color:#037691" %)**Video Instruction**(%%):**[[https:~~/~~/youtu.be/ZBjXwmp7rwM>>url:https://youtu.be/ZBjXwmp7rwM]]**26 +Video Instruction: [[https:~~/~~/youtu.be/ZBjXwmp7rwM>>url:https://youtu.be/ZBjXwmp7rwM]] 25 25 26 - 27 27 Assume we have the LoRaWAN tracker LGT92 which works in ABP mode and US915 band. It has below keys: 28 28 29 -(% class="box infomessage" %) 30 -((( 31 -AT+NWKSKEY=72 32 63 95 dd 8f e2 b2 13 66 e4 35 93 8f 55 df 30 +{{{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 33 AT+DADDR=2602111D 34 - )))33 +}}} 35 35 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. 38 -))) 39 39 40 40 We need to input above keys in LG308 and enable ABP decryption. 41 41 42 -[[image:image -20220527161119-1.png]]39 +[[image:https://wiki.dragino.com/images/thumb/5/55/LG308_MQTT_1.png/600px-LG308_MQTT_1.png||height="329" width="600"]] 43 43 44 44 Input the ABP keys in LG308 45 45 ... ... @@ -48,11 +48,9 @@ 48 48 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 -((( 52 52 We can see the log of LG308 to know this packet arrive 53 -))) 54 54 55 -[[image:image -20220527161149-2.png]]50 +[[image:https://wiki.dragino.com/images/thumb/1/16/ABP_DECODE_2.png/600px-ABP_DECODE_2.png||height="205" width="600"]] 56 56 57 57 LG308 log by "logread -f" command 58 58 ... ... @@ -59,66 +59,54 @@ 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. 61 61 62 -(% class="box" %) 63 -((( 64 -root@dragino-1d25dc:~~# hexdump /var/iot/channels/2602111D 65 -0000000 (% style="color:#037691" %)**4646 4646 4646 3946 3030 3030 3030 3546**(%%) ~-~-> Got RSSI and SNR 66 -0000010 (% style="color:#037691" %)**cc0c 0b63 0266 017f ff7f ff00 **(%%) ~-~-> Payload 57 +{{{root@dragino-1d25dc:~# hexdump /var/iot/channels/2602111D 58 +0000000 4646 4646 4646 3946 3030 3030 3030 3546 --> Got RSSI and SNR 59 +0000010 cc0c 0b63 0266 017f ff7f ff00 --> Payload 67 67 000001c 68 - )))61 +}}} 69 69 70 70 * RSSI: 4646 4646 4646 3946 = 0xFFFF FF9F : So RSSI = (0xFFFF FF9F - 0x100000000) = -97 71 71 * SNR: 3030 3030 3030 3546 = 0x0000 005F = 95, need to divide 10 so SNR is 9.5 72 72 * Payload: 0xcc0c 0b63 0266 017f ff7f ff00 73 73 74 -(% class="box" %) 75 -((( 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 string 78 -root@dragino-1d25dc:~~# hexdump /var/iot/channels/2602111D 67 + 68 +{{{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: 69 +in LGT92, use AT+SEND=12:hello world to send ASCII string 70 +root@dragino-1d25dc:~# hexdump /var/iot/channels/2602111D 79 79 0000000 4646 4646 4646 3946 3030 3030 3030 3546 80 -0000010 6865 6c6c 6f20 776f 726c 6400 ~-~-> Got ASCII code "hello world"72 +0000010 6865 6c6c 6f20 776f 726c 6400 --> Got ASCII code "hello world" 81 81 000001c 82 - )))74 +}}} 83 83 84 -(% class="box" %) 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. 87 -))) 76 +{{{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. 77 +}}} 88 88 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.81 +The decode methods: 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 94 94 For example we have a LHT65 , works in ABP mode and gateway successful get the data, which are: 95 95 96 -(% class="box" %) 97 -((( 98 -root@dragino-1baf44:~~# hexdump /var/iot/channels/01826108 85 +{{{root@dragino-1baf44:~# hexdump /var/iot/channels/01826108 99 99 0000000 4646 4646 4646 4537 3030 3030 3030 3438 100 -0000010 ccd1 7fff 7fff 017f ff7f ff00 87 +0000010 ccd1 7fff 7fff 017f ff7f ff00 101 101 000001c 102 - )))89 +}}} 103 103 104 104 If we choose ASCII decoder, the MQTT process will send out with mqtt-data: 105 105 106 -(% class="box" %) 107 -((( 108 -Sun Sep 27 04:33:16 2020 user.notice root: [IoT.MQTT]:pub_topic[-t]: dragino-1baf44/01826108/data 93 +{{{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]: (% style="color:#037691" %)**ffffffe700000048ccd17fff7fff017fff7fff00**111 - )))95 +Sun Sep 27 04:33:16 2020 user.notice root: [IoT.MQTT]:mqtt_data[-m]: ffffffe700000048ccd17fff7fff017fff7fff00 96 +}}} 112 112 113 113 If we choose Decode_LHT65, the MQTT process will send out with mqtt-data 114 114 115 -(% class="box" %) 116 -((( 117 -Sun Sep 27 04:36:45 2020 user.notice root: [IoT.MQTT]:pub_topic[-t]: dragino-1baf44/01826108/data 100 +{{{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]: **(% style="color:#037691" %){"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} (%%)**121 - )))102 +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, 103 +"EXT":"Temperature Sensor","RSSI":-24,"TempC_SHT":85.0,"SNR":8.2,"ext_sensor":0} 104 +}}} 122 122 123 123 Above scripts are store in /etc/lora/decoder/. User can put their scripts here and select it in the UI. 124 124 ... ... @@ -145,8 +145,6 @@ 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 148 - 149 - 150 150 == 2.2 Downstream == 151 151 152 152 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 ... ... @@ -153,11 +153,12 @@ 153 153 154 154 The file should use below format: 155 155 156 -(% style="color:#037691" %)**dev_addr,imme/time,txt/hex,payload** 157 157 138 +dev_addr,imme/time,txt/hex,payload 139 + 158 158 Since fimware > Dragino-v2 lgw-5.4.1608518541 . Support more option 159 159 160 - (% style="color:#037691" %)**dev_addr,imme/time,txt/hex,payload,txpw,txbw,SF,frequency,rxwindow**142 +dev_addr,imme/time,txt/hex,payload,txpw,txbw,SF,frequency,rxwindow 161 161 162 162 * dev_addr: Inptu the device address 163 163 * imme/time: ... ... @@ -177,6 +177,7 @@ 177 177 * Frequency: Transmit Frequency: example: 923300000 178 178 * rxwindow: transmit on Rx1Window or Rx2Window. 179 179 162 + 180 180 Completely exmaple: 181 181 182 182 * Old version: echo 018193F4,imme,hex,0101 > /var/iot/push/test ... ... @@ -183,7 +183,7 @@ 183 183 * New version: echo 018193F4,imme,hex,0101,20,1,SF12,923300000,2 > /var/iot/push/test 184 184 185 185 186 - (% style="color:#037691" %)**Downstream Frequency**169 +Downstream Frequency 187 187 188 188 The LG308 will use the RX2 window info to send the downstream payload, use the default LoRaWAN settings, as below: 189 189 ... ... @@ -197,33 +197,22 @@ 197 197 * RU864: 869.1Mhz, SF12 BW125 198 198 199 199 200 - (% style="color:#037691" %)**Examples:**183 +Examples: 201 201 202 -(% class="box" %) 203 -((( 204 -we can use echo command to create files in LG308 for downstream. 205 -root@dragino-1d25dc:~~# echo 2602111D,time,hex,12345678 > /var/iot/push/test 206 -))) 185 +{{{we can use echo command to create files in LG308 for downstream. 186 +root@dragino-1d25dc:~# echo 2602111D,time,hex,12345678 > /var/iot/push/test 207 207 208 -(% class="box" %) 209 -((( 210 -1) From logread -f of gateway, we can see it has been added as pedning. 211 -lora_pkt_fwd[4286]: INFO~~ [DNLK]Looking file : test 212 -lora_pkt_fwd[4286]: INFO~~ [DNLK]devaddr:2602111D, txmode:time, pdfm:hex, size:4, payload1:4Vx,payload_hex:77C1BB90 213 -lora_pkt_fwd[4286]: INFO~~ [DNLK] DNLINK PENDING!(1 elems). 214 -))) 188 +1) From logread -f of gateway, we can see it has been added as pedning. 189 +lora_pkt_fwd[4286]: INFO~ [DNLK]Looking file : test 190 +lora_pkt_fwd[4286]: INFO~ [DNLK]devaddr:2602111D, txmode:time, pdfm:hex, size:4, payload1:4Vx,payload_hex:77C1BB90 191 +lora_pkt_fwd[4286]: INFO~ [DNLK] DNLINK PENDING!(1 elems). 215 215 216 -(% class="box" %) 217 -((( 218 -2) When there is an upstrea from end node, this downstream will be sent and shows: 193 +2) When there is an upstrea from end node, this downstream will be sent and shows: 219 219 lora_pkt_fwd[4286]: INFO: tx_start_delay=1497 (1497.000000) - (1497, bw_delay=0.000000, notch_delay=0.000000) 220 220 lora_pkt_fwd[4286]: [LGWSEND]lgw_send done: count_us=3537314420, freq=923300000, size=17 221 -))) 222 222 223 -(% class="box" %) 224 -((( 225 -3) and the end node will got: 226 -[5764825]~*~*~*~** UpLinkCounter= 98 ~*~*~*~** 197 +3) and the end node will got: 198 +[5764825]***** UpLinkCounter= 98 ***** 227 227 [5764827]TX on freq 905300000 Hz at DR 0 228 228 Update Interval: 60000 ms 229 229 [5765202]txDone ... ... @@ -233,13 +233,11 @@ 233 233 [5767501]rxDone 234 234 Rssi= -41 235 235 Receive data 236 - (% style="color:#037691" %)**2:12345678**(%%)~-~-> Hex237 - )))208 +2:12345678 --> Hex 209 +}}} 238 238 239 -(% class="box" %) 240 -((( 241 -4) If we use the command "echo 2602111D,time,txt,12345678 > /var/iot/push/test" for downstream, the end node will got: 242 -[5955877]~*~*~*~** UpLinkCounter= 102 ~*~*~*~** 211 +{{{4) If we use the command "echo 2602111D,time,txt,12345678 > /var/iot/push/test" for downstream, the end node will got: 212 +[5955877]***** UpLinkCounter= 102 ***** 243 243 [5955879]TX on freq 904100000 Hz at DR 0 244 244 Update Interval: 60000 ms 245 245 [5956254]txDone ... ... @@ -249,78 +249,71 @@ 249 249 [5958595]rxDone 250 250 Rssi= -37 251 251 Receive data 252 - (% style="color:#037691" %)**2:3132333435363738**(%%)~-~-> ASCII string "12345678"253 - )))222 +2:3132333435363738 --> ASCII string "12345678" 223 +}}} 254 254 255 - 256 256 = 3. Example 1: Communicate with LT-22222-L = 257 257 258 258 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]] 259 259 260 -(% class="box" %) 261 -((( 262 -#!/bin/sh 229 +{{{#!/bin/sh 263 263 # This scripts shows how to use LPS8/LG308/DLOS8 to communicate with two LoRaWAN End Nodes, without the use of internet or LoRaWAN server 264 264 # 265 -# Hardware Prepare: 266 -# 1. LT-22222-L x 2, both are configured to work in 267 -# 268 -# b) ABP Mode ; 232 +# Hardware Prepare: 233 +# 1. LT-22222-L x 2, both are configured to work in 234 +# a) Class C ; 235 +# b) ABP Mode ; 269 269 # c) AT+Mod=1 270 -# 2. LPS8, 271 -# a) Firmware version > 272 -# b) Input the LT-22222-L keys in LPS so LPS8 can talk with them. 273 -# c) Lorawan server choose built-in 274 -# d) in Custom page, select custom script to point to this script. (put this script in /etc/iot/scripts directory) 237 +# 2. LPS8, 238 +# a) Firmware version > 239 +# b) Input the LT-22222-L keys in LPS so LPS8 can talk with them. 240 +# c) Lorawan server choose built-in 241 +# d) in Custom page, select custom script to point to this script. (put this script in /etc/iot/scripts directory) 242 +# 243 +# How it works? 244 +# a) Devices 1 sends a uplink payload to LPS8. LPS8 will get the DI1 and DI2 info from the payload 245 +# b) LPS8 will send a message to Device 2 to set the Device2 DO1 = Device1 DI1, and Device DO2 = Device DI2. 246 +# c) Device2 will change DO1 and DO2 to according to the message from LPS8, and send back a message to LPS8 with the its DO1 247 +# and DO2 value. LPS8 will ask Device1 to change its DO1 to same as Device 2, and change the DO2 to the same as Device 2. 248 +# ( The purpose of this step is to show that the Device2 has already do the change there). 249 +# 250 +# For example: If current status of Device1 and Device2 leds shows: 251 +# Device1: DI1: ON, DI2: ON , DO1: OFF, DO2: OFF 252 +# Device2: DI1: OFF, DI2: OFF , DO1: OFF, DO2: OFF 275 275 # 276 -# How it works? 277 -# a) Devices 1 sends a uplink payload to LPS8. LPS8 will get the DI1 and DI2 info from the payload 278 -# b) LPS8 will send a message to Device 2 to set the Device2 DO1 = Device1 DI1, and Device DO2 = Device DI2. 279 -# c) Device2 will change DO1 and DO2 to according to the message from LPS8, and send back a message to LPS8 with the its DO1 280 -# and DO2 value. LPS8 will ask Device1 to change its DO1 to same as Device 2, and change the DO2 to the same as Device 2. 281 -# ( The purpose of this step is to show that the Device2 has already do the change there). 282 -# 283 -# For example: If current status of Device1 and Device2 leds shows: 284 -# Device1: DI1: ON, DI2: ON , DO1: OFF, DO2: OFF 285 -# Device2: DI1: OFF, DI2: OFF , DO1: OFF, DO2: OFF 286 -# 287 -# Step2 will cause below change: 288 -# Device1: DI1: ON, DI2: ON , DO1: OFF, DO2: OFF 289 -# Device2: DI1: OFF, DI2: OFF , DO1: ON, DO2: ON 290 -# 291 -# Step3 will cause below change: 292 -# Device1: DI1: ON, DI2: ON , DO1: ON, DO2: ON 293 -# Device2: DI1: OFF, DI2: OFF , DO1: ON, DO2: ON 294 -# 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 295 -# whether the Device 2 has been changed. 296 -))) 254 +# Step2 will cause below change: 255 +# Device1: DI1: ON, DI2: ON , DO1: OFF, DO2: OFF 256 +# Device2: DI1: OFF, DI2: OFF , DO1: ON, DO2: ON 257 +# 258 +# Step3 will cause below change: 259 +# Device1: DI1: ON, DI2: ON , DO1: ON, DO2: ON 260 +# Device2: DI1: OFF, DI2: OFF , DO1: ON, DO2: ON 261 +# 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 262 +# whether the Device 2 has been changed.}}} 297 297 298 298 ~1. Input keys 299 299 300 -[[image:image-2 0220527162450-3.png]]266 +[[image:https://wiki.dragino.com/images/thumb/b/bf/LPS8_LT-22222_1.png/600px-LPS8_LT-22222_1.png||height="335" width="600"]] 301 301 302 302 Input Keys in LPS8 303 303 304 - 305 305 2. Make sure the LPS8 and LT use the same frequency bands, choose EU868 in this test. 306 306 307 307 3. Choose Built-in server 308 308 309 -[[image:image-2 0220527162518-4.png]]274 +[[image:https://wiki.dragino.com/images/thumb/d/d7/LPS8_LT-22222_2.png/600px-LPS8_LT-22222_2.png||height="264" width="600"]] 310 310 311 311 Choose Built-in server 312 312 313 - 314 314 4. Run the script. 315 315 316 -[[image:image-2 0220527162552-5.png]]280 +[[image:https://wiki.dragino.com/images/thumb/3/39/LPS8_LT-22222_3.png/600px-LPS8_LT-22222_3.png||height="389" width="600"]] 317 317 318 318 Run the script 319 319 320 - 321 321 5. Output: 322 322 323 -[[image:image-2 0220527162619-6.png]]286 +[[image:https://wiki.dragino.com/images/thumb/f/fe/LPS8_LT-22222_4.png/600px-LPS8_LT-22222_4.png||height="433" width="600"]] 324 324 325 325 Output from LPS8 326 326 ... ... @@ -335,10 +335,11 @@ 335 335 Full instruction video inlcude how to write scripts to fit server needed is here: 336 336 337 337 338 - (% class="mark" %)**Video Instruction**: [[https:~~/~~/youtu.be/-nevW6U2TsE>>url:https://youtu.be/-nevW6U2TsE]]301 +Video Instruction: [[https:~~/~~/youtu.be/-nevW6U2TsE>>url:https://youtu.be/-nevW6U2TsE]] 339 339 340 -(% class="mark" %)**Note: Firmware version must be higher than lgw-5.4.1607519907** 341 341 304 +Note: Firmware version must be higher than lgw-5.4.1607519907 305 + 342 342 Assume we already set up ABP keys in the gateway: 343 343 344 344 [[image:https://wiki.dragino.com/images/thumb/b/bf/LPS8_LT-22222_1.png/600px-LPS8_LT-22222_1.png||height="335" width="600"]]
- image-20220527161119-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -128.8 KB - Content
- image-20220527161149-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -103.9 KB - Content
- image-20220527162450-3.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -125.4 KB - Content
- image-20220527162518-4.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -72.8 KB - Content
- image-20220527162552-5.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -33.6 KB - Content
- image-20220527162619-6.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -41.0 KB - Content