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

Summary

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 110  Sun Sep 27 04:33:16 2020 user.notice root: [IoT.MQTT]:mqtt_data[-m]: ffffffe700000048ccd17fff7fff017fff7fff00
111 -)))
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 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 120  "EXT":"Temperature Sensor","RSSI":-24,"TempC_SHT":85.0,"SNR":8.2,"ext_sensor":0}
121 -)))
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  
... ... @@ -151,11 +151,12 @@
151 151  
152 152  The file should use below format:
153 153  
154 -(% class="mark" %)**dev_addr,imme/time,txt/hex,payload**
155 155  
138 +dev_addr,imme/time,txt/hex,payload
139 +
156 156  Since fimware > Dragino-v2 lgw-5.4.1608518541 . Support more option
157 157  
158 -(% class="mark" %)**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
159 159  
160 160  * dev_addr: Inptu the device address
161 161  * imme/time:
... ... @@ -175,13 +175,15 @@
175 175  * Frequency: Transmit Frequency: example: 923300000
176 176  * rxwindow: transmit on Rx1Window or Rx2Window.
177 177  
162 +
178 178  Completely exmaple:
179 179  
180 180  * Old version: echo 018193F4,imme,hex,0101 > /var/iot/push/test
181 181  * New version: echo 018193F4,imme,hex,0101,20,1,SF12,923300000,2 > /var/iot/push/test
182 182  
183 -(% class="mark" %)**Downstream Frequency**
184 184  
169 +Downstream Frequency
170 +
185 185  The LG308 will use the RX2 window info to send the downstream payload, use the default LoRaWAN settings, as below:
186 186  
187 187  * EU868: 869.525Mhz, DR0(SF12BW125)
... ... @@ -193,33 +193,23 @@
193 193  * IN865: 866.55Mhz, SF10 BW125
194 194  * RU864: 869.1Mhz, SF12 BW125
195 195  
196 -(% class="mark" %)**Examples:**
197 197  
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 -)))
183 +Examples:
203 203  
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 -)))
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
211 211  
212 -(% class="box" %)
213 -(((
214 -2) When there is an upstrea from end node, this downstream will be sent and shows:
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).
192 +
193 +2) When there is an upstrea from end node, this downstream will be sent and shows:
215 215  lora_pkt_fwd[4286]: INFO: tx_start_delay=1497 (1497.000000) - (1497, bw_delay=0.000000, notch_delay=0.000000)
216 216  lora_pkt_fwd[4286]: [LGWSEND]lgw_send done: count_us=3537314420, freq=923300000, size=17
217 -)))
218 218  
219 -(% class="box" %)
220 -(((
221 -3) and the end node will got:
222 -[5764825]~*~*~*~** UpLinkCounter= 98 ~*~*~*~**
197 +3) and the end node will got:
198 +[5764825]***** UpLinkCounter= 98 *****
223 223  [5764827]TX on freq 905300000 Hz at DR 0
224 224  Update Interval: 60000 ms
225 225  [5765202]txDone
... ... @@ -229,13 +229,11 @@
229 229  [5767501]rxDone
230 230  Rssi= -41
231 231  Receive data
232 -2:12345678    ~-~-> Hex
233 -)))
208 +2:12345678 --> Hex
209 +}}}
234 234  
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 ~*~*~*~**
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 *****
239 239  [5955879]TX on freq 904100000 Hz at DR 0
240 240  Update Interval: 60000 ms
241 241  [5956254]txDone
... ... @@ -245,50 +245,47 @@
245 245  [5958595]rxDone
246 246  Rssi= -37
247 247  Receive data
248 -2:3132333435363738 ~-~-> ASCII string "12345678"
249 -)))
222 +2:3132333435363738 --> ASCII string "12345678"
223 +}}}
250 250  
251 251  = 3. Example 1: Communicate with LT-22222-L =
252 252  
253 253  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]]
254 254  
255 -(% class="box" %)
256 -(((
257 -#!/bin/sh
229 +{{{#!/bin/sh
258 258  # This scripts shows how to use LPS8/LG308/DLOS8 to communicate with two LoRaWAN End Nodes, without the use of internet or LoRaWAN server
259 259  #
260 -# Hardware Prepare:
261 -# 1. LT-22222-L x 2, both are configured to work in
262 -#   a) Class C ;
263 -# 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 ;
264 264  # c) AT+Mod=1
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)
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
270 270  #
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 -)))
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.}}}
292 292  
293 293  ~1. Input keys
294 294  
... ... @@ -327,10 +327,11 @@
327 327  Full instruction video inlcude how to write scripts to fit server needed is here:
328 328  
329 329  
330 -(% 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]]
331 331  
332 -(% class="mark" %)**Note: Firmware version must be higher than lgw-5.4.1607519907**
333 333  
304 +Note: Firmware version must be higher than lgw-5.4.1607519907
305 +
334 334  Assume we already set up ABP keys in the gateway:
335 335  
336 336  [[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

Applications

Navigation

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