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

Summary

Details

Page properties
Content
... ... @@ -1,8 +1,6 @@
1 - **Contents:**
1 +Contents:
2 2  
3 -{{toc/}}
4 4  
5 -
6 6  = 1. Introduction =
7 7  
8 8  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:
... ... @@ -10,32 +10,27 @@
10 10  * No internet connection.
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 -(((
14 -The basic of this feature is the decoding of (% style="color:red" %)**LoRaWAN ABP End Node**(%%). Requirements:
15 -)))
16 16  
12 +The basic of this feature is the decoding of LoRaWAN ABP End Node. Requirements:
13 +
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/]](%%)**
16 +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  
18 +
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]]**
22 +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
26 +{{{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 -)))
29 +}}}
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  
... ... @@ -48,9 +48,7 @@
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 55  [[image:https://wiki.dragino.com/images/thumb/1/16/ABP_DECODE_2.png/600px-ABP_DECODE_2.png||height="205" width="600"]]
56 56  
... ... @@ -59,65 +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 (% class="mark" %)**4646 4646 4646 3946 3030 3030 3030 3546**(%%)      ~-~-> Got RSSI and SNR    
66 -0000010 (% class="mark" %)**cc0c 0b63 0266 017f ff7f ff00 **(%%) ~-~-> Payload
53 +{{{root@dragino-1d25dc:~# hexdump /var/iot/channels/2602111D
54 +0000000 4646 4646 4646 3946 3030 3030 3030 3546 --> Got RSSI and SNR
55 +0000010 cc0c 0b63 0266 017f ff7f ff00 --> Payload
67 67  000001c
68 -)))
57 +}}}
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 -(% 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:
77 -in LGT92, use **AT+SEND=12**:hello world to send ASCII string
78 -root@dragino-1d25dc:~~# hexdump /var/iot/channels/2602111D
63 +
64 +{{{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:
65 +in LGT92, use AT+SEND=12:hello world to send ASCII string
66 +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"    
68 +0000010 6865 6c6c 6f20 776f 726c 6400 --> Got ASCII code "hello world"
81 81  000001c
82 -)))
70 +}}}
83 83  
84 -(% class="box" %)
85 -(((
86 -(% 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.
87 -)))
72 +{{{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.
73 +}}}
88 88  
89 89  === 2.2.1 Decode Method ===
90 90  
91 -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.
77 +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 92  
93 93  For example we have a LHT65 , works in ABP mode and gateway successful get the data, which are:
94 94  
95 -(% class="box" %)
96 -(((
97 -root@dragino-1baf44:~~# hexdump /var/iot/channels/01826108
81 +{{{root@dragino-1baf44:~# hexdump /var/iot/channels/01826108
98 98  0000000 4646 4646 4646 4537 3030 3030 3030 3438
99 -0000010 ccd1 7fff 7fff 017f ff7f ff00         
83 +0000010 ccd1 7fff 7fff 017f ff7f ff00
100 100  000001c
101 -)))
85 +}}}
102 102  
103 103  If we choose ASCII decoder, the MQTT process will send out with mqtt-data:
104 104  
105 -(% class="box" %)
106 -(((
107 -Sun Sep 27 04:33:16 2020 user.notice root: [IoT.MQTT]:pub_topic[-t]: dragino-1baf44/01826108/data
89 +{{{Sun Sep 27 04:33:16 2020 user.notice root: [IoT.MQTT]:pub_topic[-t]: dragino-1baf44/01826108/data
108 108  Sun Sep 27 04:33:16 2020 user.notice root: [IoT.MQTT]:decoder: ASCII
109 109  Sun Sep 27 04:33:16 2020 user.notice root: [IoT.MQTT]:mqtt_data[-m]: ffffffe700000048ccd17fff7fff017fff7fff00
110 -)))
92 +}}}
111 111  
112 112  If we choose Decode_LHT65, the MQTT process will send out with mqtt-data
113 113  
114 -(% class="box" %)
115 -(((
116 -Sun Sep 27 04:36:45 2020 user.notice root: [IoT.MQTT]:pub_topic[-t]: dragino-1baf44/01826108/data
96 +{{{Sun Sep 27 04:36:45 2020 user.notice root: [IoT.MQTT]:pub_topic[-t]: dragino-1baf44/01826108/data
117 117  Sun Sep 27 04:36:45 2020 user.notice root: [IoT.MQTT]:decoder: Dragino_LHT65
118 118  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,
119 119  "EXT":"Temperature Sensor","RSSI":-24,"TempC_SHT":85.0,"SNR":8.2,"ext_sensor":0}
120 -)))
100 +}}}
121 121  
122 122  Above scripts are store in /etc/lora/decoder/. User can put their scripts here and select it in the UI.
123 123  
... ... @@ -150,11 +150,12 @@
150 150  
151 151  The file should use below format:
152 152  
153 -(% class="mark" %)**dev_addr,imme/time,txt/hex,payload**
154 154  
134 +dev_addr,imme/time,txt/hex,payload
135 +
155 155  Since fimware > Dragino-v2 lgw-5.4.1608518541 . Support more option
156 156  
157 -(% class="mark" %)**dev_addr,imme/time,txt/hex,payload,txpw,txbw,SF,frequency,rxwindow**
138 +dev_addr,imme/time,txt/hex,payload,txpw,txbw,SF,frequency,rxwindow
158 158  
159 159  * dev_addr: Inptu the device address
160 160  * imme/time:
... ... @@ -174,13 +174,15 @@
174 174  * Frequency: Transmit Frequency: example: 923300000
175 175  * rxwindow: transmit on Rx1Window or Rx2Window.
176 176  
158 +
177 177  Completely exmaple:
178 178  
179 179  * Old version: echo 018193F4,imme,hex,0101 > /var/iot/push/test
180 180  * New version: echo 018193F4,imme,hex,0101,20,1,SF12,923300000,2 > /var/iot/push/test
181 181  
182 -(% class="mark" %)**Downstream Frequency**
183 183  
165 +Downstream Frequency
166 +
184 184  The LG308 will use the RX2 window info to send the downstream payload, use the default LoRaWAN settings, as below:
185 185  
186 186  * EU868: 869.525Mhz, DR0(SF12BW125)
... ... @@ -192,33 +192,23 @@
192 192  * IN865: 866.55Mhz, SF10 BW125
193 193  * RU864: 869.1Mhz, SF12 BW125
194 194  
195 -(% class="mark" %)**Examples:**
196 196  
197 -(% class="box" %)
198 -(((
199 -we can use echo command to create files in LG308 for downstream.
200 -root@dragino-1d25dc:~~# echo 2602111D,time,hex,12345678 > /var/iot/push/test
201 -)))
179 +Examples:
202 202  
203 -(% class="box" %)
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 -)))
181 +{{{we can use echo command to create files in LG308 for downstream.
182 +root@dragino-1d25dc:~# echo 2602111D,time,hex,12345678 > /var/iot/push/test
210 210  
211 -(% class="box" %)
212 -(((
213 -2) When there is an upstrea from end node, this downstream will be sent and shows:
184 +1) From logread -f of gateway, we can see it has been added as pedning.
185 +lora_pkt_fwd[4286]: INFO~ [DNLK]Looking file : test
186 +lora_pkt_fwd[4286]: INFO~ [DNLK]devaddr:2602111D, txmode:time, pdfm:hex, size:4, payload1:4Vx,payload_hex:77C1BB90
187 +lora_pkt_fwd[4286]: INFO~ [DNLK] DNLINK PENDING!(1 elems).
188 +
189 +2) When there is an upstrea from end node, this downstream will be sent and shows:
214 214  lora_pkt_fwd[4286]: INFO: tx_start_delay=1497 (1497.000000) - (1497, bw_delay=0.000000, notch_delay=0.000000)
215 215  lora_pkt_fwd[4286]: [LGWSEND]lgw_send done: count_us=3537314420, freq=923300000, size=17
216 -)))
217 217  
218 -(% class="box" %)
219 -(((
220 -3) and the end node will got:
221 -[5764825]~*~*~*~** UpLinkCounter= 98 ~*~*~*~**
193 +3) and the end node will got:
194 +[5764825]***** UpLinkCounter= 98 *****
222 222  [5764827]TX on freq 905300000 Hz at DR 0
223 223  Update Interval: 60000 ms
224 224  [5765202]txDone
... ... @@ -228,13 +228,11 @@
228 228  [5767501]rxDone
229 229  Rssi= -41
230 230  Receive data
231 -2:12345678    ~-~-> Hex
232 -)))
204 +2:12345678 --> Hex
205 +}}}
233 233  
234 -(% class="box" %)
235 -(((
236 -4) If we use the command "echo 2602111D,time,txt,12345678 > /var/iot/push/test" for downstream, the end node will got:
237 -[5955877]~*~*~*~** UpLinkCounter= 102 ~*~*~*~**
207 +{{{4) If we use the command "echo 2602111D,time,txt,12345678 > /var/iot/push/test" for downstream, the end node will got:
208 +[5955877]***** UpLinkCounter= 102 *****
238 238  [5955879]TX on freq 904100000 Hz at DR 0
239 239  Update Interval: 60000 ms
240 240  [5956254]txDone
... ... @@ -244,50 +244,47 @@
244 244  [5958595]rxDone
245 245  Rssi= -37
246 246  Receive data
247 -2:3132333435363738 ~-~-> ASCII string "12345678"
248 -)))
218 +2:3132333435363738 --> ASCII string "12345678"
219 +}}}
249 249  
250 250  = 3. Example 1: Communicate with LT-22222-L =
251 251  
252 252  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]]
253 253  
254 -(% class="box" %)
255 -(((
256 -#!/bin/sh
225 +{{{#!/bin/sh
257 257  # This scripts shows how to use LPS8/LG308/DLOS8 to communicate with two LoRaWAN End Nodes, without the use of internet or LoRaWAN server
258 258  #
259 -# Hardware Prepare:
260 -# 1. LT-22222-L x 2, both are configured to work in
261 -#   a) Class C ;
262 -# b) ABP Mode ;
228 +# Hardware Prepare:
229 +# 1. LT-22222-L x 2, both are configured to work in
230 +# a) Class C ;
231 +# b) ABP Mode ;
263 263  # c) AT+Mod=1
264 -# 2. LPS8,
265 -#   a) Firmware version >
266 -#   b) Input the LT-22222-L keys in LPS so LPS8 can talk with them.
267 -#   c) Lorawan server choose built-in
268 -#   d) in Custom page, select custom script to point to this script. (put this script in /etc/iot/scripts directory)
233 +# 2. LPS8,
234 +# a) Firmware version >
235 +# b) Input the LT-22222-L keys in LPS so LPS8 can talk with them.
236 +# c) Lorawan server choose built-in
237 +# d) in Custom page, select custom script to point to this script. (put this script in /etc/iot/scripts directory)
238 +#
239 +# How it works?
240 +# a) Devices 1 sends a uplink payload to LPS8. LPS8 will get the DI1 and DI2 info from the payload
241 +# b) LPS8 will send a message to Device 2 to set the Device2 DO1 = Device1 DI1, and Device DO2 = Device DI2.
242 +# 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
243 +# 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.
244 +# ( The purpose of this step is to show that the Device2 has already do the change there).
245 +#
246 +# For example: If current status of Device1 and Device2 leds shows:
247 +# Device1: DI1: ON, DI2: ON , DO1: OFF, DO2: OFF
248 +# Device2: DI1: OFF, DI2: OFF , DO1: OFF, DO2: OFF
269 269  #
270 -# How it works?
271 -#   a) Devices 1 sends a uplink payload to LPS8. LPS8 will get the DI1 and DI2 info from the payload
272 -#   b) LPS8 will send a message to Device 2 to set the Device2 DO1 = Device1 DI1, and Device DO2 = Device DI2.
273 -#   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
274 -#   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.
275 -#   ( The purpose of this step is to show that the Device2 has already do the change there).
276 -#
277 -#  For example: If current status of Device1 and Device2 leds shows:
278 -#  Device1: DI1: ON, DI2: ON , DO1: OFF,  DO2: OFF
279 -#  Device2: DI1: OFF, DI2: OFF , DO1: OFF,  DO2: OFF
280 -#
281 -#  Step2  will cause below change:
282 -#  Device1: DI1: ON, DI2: ON , DO1: OFF,  DO2: OFF
283 -#  Device2: DI1: OFF, DI2: OFF , DO1: ON,  DO2: ON
284 -# 
285 -#  Step3 will cause below change:
286 -#  Device1: DI1: ON, DI2: ON , DO1: ON,  DO2: ON
287 -#  Device2: DI1: OFF, DI2: OFF , DO1: ON,  DO2: ON
288 -#  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
289 -#  whether the Device 2 has been changed.
290 -)))
250 +# Step2 will cause below change:
251 +# Device1: DI1: ON, DI2: ON , DO1: OFF, DO2: OFF
252 +# Device2: DI1: OFF, DI2: OFF , DO1: ON, DO2: ON
253 +#
254 +# Step3 will cause below change:
255 +# Device1: DI1: ON, DI2: ON , DO1: ON, DO2: ON
256 +# Device2: DI1: OFF, DI2: OFF , DO1: ON, DO2: ON
257 +# 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
258 +# whether the Device 2 has been changed.}}}
291 291  
292 292  ~1. Input keys
293 293  
... ... @@ -326,10 +326,11 @@
326 326  Full instruction video inlcude how to write scripts to fit server needed is here:
327 327  
328 328  
329 -(% class="mark" %)**Video Instruction**: [[https:~~/~~/youtu.be/-nevW6U2TsE>>url:https://youtu.be/-nevW6U2TsE]]
297 +Video Instruction: [[https:~~/~~/youtu.be/-nevW6U2TsE>>url:https://youtu.be/-nevW6U2TsE]]
330 330  
331 -(% class="mark" %)**Note: Firmware version must be higher than lgw-5.4.1607519907**
332 332  
300 +Note: Firmware version must be higher than lgw-5.4.1607519907
301 +
333 333  Assume we already set up ABP keys in the gateway:
334 334  
335 335  [[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

Applications

Navigation

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