Last modified by Xiaoling on 2023/04/20 18:14
<
From version < 1.9 >
edited by Xiaoling
on 2022/05/12 18:02
To version < 3.6 >
edited by Xiaoling
on 2022/05/27 16:20
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -11,20 +11,19 @@
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 -
15 -The basic of this feature is the decoding of **LoRaWAN ABP End Node**. Requirements:
14 +The basic of this feature is the decoding of (% style="color:red" %)**LoRaWAN ABP End Node**(%%). Requirements:
16 16  )))
17 17  
18 18  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
19 19  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]]
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/]]
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/]](%%)**
21 21  
22 -
23 23  = 2. How it works =
24 24  
25 25  
26 -**Video Instruction**: [[https:~~/~~/youtu.be/ZBjXwmp7rwM>>url:https://youtu.be/ZBjXwmp7rwM]]
24 +(% style="color:#037691" %)**Video Instruction**(%%): **[[https:~~/~~/youtu.be/ZBjXwmp7rwM>>url:https://youtu.be/ZBjXwmp7rwM]]**
27 27  
26 +
28 28  Assume we have the LoRaWAN tracker LGT92 which works in ABP mode and US915 band. It has below keys:
29 29  
30 30  (% class="box infomessage" %)
... ... @@ -40,7 +40,7 @@
40 40  
41 41  We need to input above keys in LG308 and enable ABP decryption.
42 42  
43 -[[image:https://wiki.dragino.com/images/thumb/5/55/LG308_MQTT_1.png/600px-LG308_MQTT_1.png||height="329" width="600"]]
42 +[[image:image-20220527161119-1.png]]
44 44  
45 45  Input the ABP keys in LG308
46 46  
... ... @@ -53,7 +53,7 @@
53 53  We can see the log of LG308 to know this packet arrive
54 54  )))
55 55  
56 -[[image:https://wiki.dragino.com/images/thumb/1/16/ABP_DECODE_2.png/600px-ABP_DECODE_2.png||height="205" width="600"]]
55 +[[image:image-20220527161149-2.png]]
57 57  
58 58  LG308 log by "logread -f" command
59 59  
... ... @@ -63,8 +63,8 @@
63 63  (% class="box" %)
64 64  (((
65 65  root@dragino-1d25dc:~~# hexdump /var/iot/channels/2602111D
66 -0000000 (% class="mark" %)**4646 4646 4646 3946 3030 3030 3030 3546**(%%)      ~-~-> Got RSSI and SNR    
67 -0000010 (% class="mark" %)**cc0c 0b63 0266 017f ff7f ff00 **(%%) ~-~-> Payload
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
68 68  000001c
69 69  )))
70 70  
... ... @@ -74,8 +74,8 @@
74 74  
75 75  (% class="box" %)
76 76  (((
77 -(% class="mark" %)**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:
78 -in LGT92, use **AT+SEND=12**:hello world to send ASCII string
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
79 79  root@dragino-1d25dc:~~# hexdump /var/iot/channels/2602111D
80 80  0000000 4646 4646 4646 3946 3030 3030 3030 3546
81 81  0000010 6865 6c6c 6f20 776f 726c 6400      ~-~-> Got ASCII code "hello world"    
... ... @@ -84,12 +84,13 @@
84 84  
85 85  (% class="box" %)
86 86  (((
87 -(% class="mark" %)**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.
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.
88 88  )))
89 89  
89 +
90 90  === 2.2.1 Decode Method ===
91 91  
92 -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.
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  
94 94  For example we have a LHT65 , works in ABP mode and gateway successful get the data, which are:
95 95  
... ... @@ -107,7 +107,7 @@
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
110 +Sun Sep 27 04:33:16 2020 user.notice root: [IoT.MQTT]:mqtt_data[-m]: (% style="color:#037691" %)**ffffffe700000048ccd17fff7fff017fff7fff00**
111 111  )))
112 112  
113 113  If we choose Decode_LHT65, the MQTT process will send out with mqtt-data
... ... @@ -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}
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 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.
... ... @@ -151,12 +151,11 @@
151 151  
152 152  The file should use below format:
153 153  
154 +**(% style="color:#037691" %)dev_addr,imme/time,txt/hex,payload**
154 154  
155 -dev_addr,imme/time,txt/hex,payload
156 -
157 157  Since fimware > Dragino-v2 lgw-5.4.1608518541 . Support more option
158 158  
159 -dev_addr,imme/time,txt/hex,payload,txpw,txbw,SF,frequency,rxwindow
158 +**(% style="color:#037691" %)dev_addr,imme/time,txt/hex,payload,txpw,txbw,SF,frequency,rxwindow**
160 160  
161 161  * dev_addr: Inptu the device address
162 162  * imme/time:
... ... @@ -176,15 +176,13 @@
176 176  * Frequency: Transmit Frequency: example: 923300000
177 177  * rxwindow: transmit on Rx1Window or Rx2Window.
178 178  
179 -
180 180  Completely exmaple:
181 181  
182 182  * Old version: echo 018193F4,imme,hex,0101 > /var/iot/push/test
183 183  * New version: echo 018193F4,imme,hex,0101,20,1,SF12,923300000,2 > /var/iot/push/test
184 184  
183 +**(% style="color:#037691" %)Downstream Frequency**
185 185  
186 -Downstream Frequency
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  
190 190  * EU868: 869.525Mhz, DR0(SF12BW125)
... ... @@ -196,23 +196,33 @@
196 196  * IN865: 866.55Mhz, SF10 BW125
197 197  * RU864: 869.1Mhz, SF12 BW125
198 198  
196 +(% style="color:#037691" %)**Examples:**
199 199  
200 -Examples:
198 +(% class="box" %)
199 +(((
200 +we can use echo command to create files in LG308 for downstream.
201 +root@dragino-1d25dc:~~# echo 2602111D,time,hex,12345678 > /var/iot/push/test
202 +)))
201 201  
202 -{{{we can use echo command to create files in LG308 for downstream.
203 -root@dragino-1d25dc:~# echo 2602111D,time,hex,12345678 > /var/iot/push/test
204 +(% class="box" %)
205 +(((
206 +1) From logread -f of gateway, we can see it has been added as pedning.
207 +lora_pkt_fwd[4286]: INFO~~ [DNLK]Looking file : test
208 +lora_pkt_fwd[4286]: INFO~~ [DNLK]devaddr:2602111D, txmode:time, pdfm:hex, size:4, payload1:4Vx,payload_hex:77C1BB90
209 +lora_pkt_fwd[4286]: INFO~~ [DNLK] DNLINK PENDING!(1 elems).
210 +)))
204 204  
205 -1) From logread -f of gateway, we can see it has been added as pedning.
206 -lora_pkt_fwd[4286]: INFO~ [DNLK]Looking file : test
207 -lora_pkt_fwd[4286]: INFO~ [DNLK]devaddr:2602111D, txmode:time, pdfm:hex, size:4, payload1:4Vx,payload_hex:77C1BB90
208 -lora_pkt_fwd[4286]: INFO~ [DNLK] DNLINK PENDING!(1 elems).
209 -
210 -2) When there is an upstrea from end node, this downstream will be sent and shows:
212 +(% class="box" %)
213 +(((
214 +2) When there is an upstrea from end node, this downstream will be sent and shows:
211 211  lora_pkt_fwd[4286]: INFO: tx_start_delay=1497 (1497.000000) - (1497, bw_delay=0.000000, notch_delay=0.000000)
212 212  lora_pkt_fwd[4286]: [LGWSEND]lgw_send done: count_us=3537314420, freq=923300000, size=17
217 +)))
213 213  
214 -3) and the end node will got:
215 -[5764825]***** UpLinkCounter= 98 *****
219 +(% class="box" %)
220 +(((
221 +3) and the end node will got:
222 +[5764825]~*~*~*~** UpLinkCounter= 98 ~*~*~*~**
216 216  [5764827]TX on freq 905300000 Hz at DR 0
217 217  Update Interval: 60000 ms
218 218  [5765202]txDone
... ... @@ -222,11 +222,13 @@
222 222  [5767501]rxDone
223 223  Rssi= -41
224 224  Receive data
225 -2:12345678 --> Hex
226 -}}}
232 +2:12345678    ~-~-> Hex
233 +)))
227 227  
228 -{{{4) If we use the command "echo 2602111D,time,txt,12345678 > /var/iot/push/test" for downstream, the end node will got:
229 -[5955877]***** UpLinkCounter= 102 *****
235 +(% class="box" %)
236 +(((
237 +4) If we use the command "echo 2602111D,time,txt,12345678 > /var/iot/push/test" for downstream, the end node will got:
238 +[5955877]~*~*~*~** UpLinkCounter= 102 ~*~*~*~**
230 230  [5955879]TX on freq 904100000 Hz at DR 0
231 231  Update Interval: 60000 ms
232 232  [5956254]txDone
... ... @@ -236,47 +236,50 @@
236 236  [5958595]rxDone
237 237  Rssi= -37
238 238  Receive data
239 -2:3132333435363738 --> ASCII string "12345678"
240 -}}}
248 +2:3132333435363738 ~-~-> ASCII string "12345678"
249 +)))
241 241  
242 242  = 3. Example 1: Communicate with LT-22222-L =
243 243  
244 244  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]]
245 245  
246 -{{{#!/bin/sh
255 +(% class="box" %)
256 +(((
257 +#!/bin/sh
247 247  # This scripts shows how to use LPS8/LG308/DLOS8 to communicate with two LoRaWAN End Nodes, without the use of internet or LoRaWAN server
248 248  #
249 -# Hardware Prepare:
250 -# 1. LT-22222-L x 2, both are configured to work in
251 -# a) Class C ;
252 -# b) ABP Mode ;
260 +# Hardware Prepare:
261 +# 1. LT-22222-L x 2, both are configured to work in
262 +#   a) Class C ;
263 +# b) ABP Mode ;
253 253  # c) AT+Mod=1
254 -# 2. LPS8,
255 -# a) Firmware version >
256 -# b) Input the LT-22222-L keys in LPS so LPS8 can talk with them.
257 -# c) Lorawan server choose built-in
258 -# d) in Custom page, select custom script to point to this script. (put this script in /etc/iot/scripts directory)
259 -#
260 -# How it works?
261 -# a) Devices 1 sends a uplink payload to LPS8. LPS8 will get the DI1 and DI2 info from the payload
262 -# b) LPS8 will send a message to Device 2 to set the Device2 DO1 = Device1 DI1, and Device DO2 = Device DI2.
263 -# 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
264 -# 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.
265 -# ( The purpose of this step is to show that the Device2 has already do the change there).
266 -#
267 -# For example: If current status of Device1 and Device2 leds shows:
268 -# Device1: DI1: ON, DI2: ON , DO1: OFF, DO2: OFF
269 -# Device2: DI1: OFF, DI2: OFF , DO1: OFF, DO2: OFF
265 +# 2. LPS8,
266 +#   a) Firmware version >
267 +#   b) Input the LT-22222-L keys in LPS so LPS8 can talk with them.
268 +#   c) Lorawan server choose built-in
269 +#   d) in Custom page, select custom script to point to this script. (put this script in /etc/iot/scripts directory)
270 270  #
271 -# Step2 will cause below change:
272 -# Device1: DI1: ON, DI2: ON , DO1: OFF, DO2: OFF
273 -# Device2: DI1: OFF, DI2: OFF , DO1: ON, DO2: ON
274 -#
275 -# Step3 will cause below change:
276 -# Device1: DI1: ON, DI2: ON , DO1: ON, DO2: ON
277 -# Device2: DI1: OFF, DI2: OFF , DO1: ON, DO2: ON
278 -# 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
279 -# whether the Device 2 has been changed.}}}
271 +# How it works?
272 +#   a) Devices 1 sends a uplink payload to LPS8. LPS8 will get the DI1 and DI2 info from the payload
273 +#   b) LPS8 will send a message to Device 2 to set the Device2 DO1 = Device1 DI1, and Device DO2 = Device DI2.
274 +#   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
275 +#   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.
276 +#   ( The purpose of this step is to show that the Device2 has already do the change there).
277 +#
278 +#  For example: If current status of Device1 and Device2 leds shows:
279 +#  Device1: DI1: ON, DI2: ON , DO1: OFF,  DO2: OFF
280 +#  Device2: DI1: OFF, DI2: OFF , DO1: OFF,  DO2: OFF
281 +#
282 +#  Step2  will cause below change:
283 +#  Device1: DI1: ON, DI2: ON , DO1: OFF,  DO2: OFF
284 +#  Device2: DI1: OFF, DI2: OFF , DO1: ON,  DO2: ON
285 +# 
286 +#  Step3 will cause below change:
287 +#  Device1: DI1: ON, DI2: ON , DO1: ON,  DO2: ON
288 +#  Device2: DI1: OFF, DI2: OFF , DO1: ON,  DO2: ON
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.
291 +)))
280 280  
281 281  ~1. Input keys
282 282  
... ... @@ -315,11 +315,10 @@
315 315  Full instruction video inlcude how to write scripts to fit server needed is here:
316 316  
317 317  
318 -Video Instruction: [[https:~~/~~/youtu.be/-nevW6U2TsE>>url:https://youtu.be/-nevW6U2TsE]]
330 +(% class="mark" %)**Video Instruction**: [[https:~~/~~/youtu.be/-nevW6U2TsE>>url:https://youtu.be/-nevW6U2TsE]]
319 319  
332 +(% class="mark" %)**Note: Firmware version must be higher than lgw-5.4.1607519907**
320 320  
321 -Note: Firmware version must be higher than lgw-5.4.1607519907
322 -
323 323  Assume we already set up ABP keys in the gateway:
324 324  
325 325  [[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,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +128.8 KB
Content
image-20220527161149-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +103.9 KB
Content

Applications

Navigation

Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0