Last modified by Xiaoling on 2023/04/20 18:14
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -1,4 +1,5 @@ 1 -**Table of Contents:** 1 +* 2 +** Table of** **Contents: 2 2 3 3 {{toc/}} 4 4 ... ... @@ -131,27 +131,22 @@ 131 131 Above scripts are store in /etc/lora/decoder/. User can put their scripts here and select it in the UI. 132 132 133 133 134 - 135 135 === 2.2.2 How to Decode My End Node === 136 136 137 137 138 - **1.**Configure the ABP keys for your end node in the gateway. enable ABP decode in Web UI138 +1/ Configure the ABP keys for your end node in the gateway. enable ABP decode in Web UI 139 139 140 - **2.**Don't choose MQTT service, use LoRaWAN.140 +2/ Don't choose MQTT service, use LoRaWAN. 141 141 142 - **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_ADDR142 +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 143 143 144 - **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:144 +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: 145 145 146 146 {{{/etc/lora/decoder/Dragino_LHT65 END_NODE_DEV_ADDR 147 147 }}} 148 148 149 - **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.149 +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: 150 150 151 - 152 -(% style="color:red" %) 153 -**Some notice:** 154 - 155 155 * RSSI and SNR are added when gateway receive the packet, so there is always this field. 156 156 * If you rename the file, please make it executable. 157 157 * See this link for lua.bit module: [[http:~~/~~/luaforge.net/projects/bit/>>url:http://luaforge.net/projects/bit/]] ... ... @@ -160,6 +160,7 @@ 160 160 * User can use other language ,not limited to Lua, just make sure the return is what you want to send. 161 161 162 162 159 + 163 163 == 2.2 Downstream == 164 164 165 165 ... ... @@ -192,7 +192,6 @@ 192 192 * **rxwindow:** transmit on Rx1Window or Rx2Window. 193 193 194 194 195 - 196 196 (% style="color:blue" %)**Completely exmaple:** 197 197 198 198 * **Old version:** echo 018193F4,imme,hex,0101 > /var/iot/push/test ... ... @@ -221,19 +221,25 @@ 221 221 ((( 222 222 we can use echo command to create files in LG308 for downstream. 223 223 root@dragino-1d25dc:~~# echo 2602111D,time,hex,12345678 > /var/iot/push/test 220 +))) 224 224 225 - 222 +(% class="box" %) 223 +((( 226 226 **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). 228 +))) 230 230 231 - 230 +(% class="box" %) 231 +((( 232 232 **2)** When there is an upstrea from end node, this downstream will be sent and shows: 233 233 lora_pkt_fwd[4286]: INFO: tx_start_delay=1497 (1497.000000) - (1497, bw_delay=0.000000, notch_delay=0.000000) 234 234 lora_pkt_fwd[4286]: [LGWSEND]lgw_send done: count_us=3537314420, freq=923300000, size=17 235 +))) 235 235 236 - 237 +(% class="box" %) 238 +((( 237 237 **3)** and the end node will got: 238 238 [5764825]~*~*~*~** UpLinkCounter= 98 ~*~*~*~** 239 239 [5764827]TX on freq 905300000 Hz at DR 0 ... ... @@ -246,8 +246,10 @@ 246 246 Rssi= -41 247 247 Receive data 248 248 (% style="color:#037691" %)**2:12345678** (%%) ~-~-> Hex 251 +))) 249 249 250 - 253 +(% class="box" %) 254 +((( 251 251 **4) **If we use the command "echo 2602111D,time,txt,12345678 > /var/iot/push/test" for downstream, the end node will got: 252 252 [5955877]~*~*~*~** UpLinkCounter= 102 ~*~*~*~** 253 253 [5955879]TX on freq 904100000 Hz at DR 0