Last modified by Xiaoling on 2023/04/20 18:14
<
From version < 1.10 >
edited by Xiaoling
on 2022/05/12 18:08
To version < 1.5 >
edited by Xiaoling
on 2022/05/12 17:52
>
Change comment: There is no comment for this version

Summary

Details

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

Applications

Navigation

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