Last modified by Xiaoling on 2023/04/20 18:14
<
From version < 18.3 >
edited by Xiaoling
on 2022/07/22 11:58
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
... ... @@ -1,52 +1,42 @@
1 -**Table of Contents:**
1 + **Contents:**
2 2  
3 3  {{toc/}}
4 4  
5 5  
6 -
7 7  = 1. Introduction =
8 8  
9 -
10 10  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:
11 11  
12 12  * No internet connection.
13 -* 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>>MQTT Forward Instruction]]).
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]]).
14 14  
15 15  (((
16 -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:
17 17  )))
18 18  
19 19  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
20 20  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]]
21 -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/]]
22 22  
23 23  
24 -
25 -
26 26  = 2. How it works =
27 27  
28 28  
29 -(% 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]]
30 30  
31 -
32 32  Assume we have the LoRaWAN tracker LGT92 which works in ABP mode and US915 band. It has below keys:
33 33  
34 -(% class="box infomessage" %)
35 -(((
36 -**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
37 37  AT+APPSKEY=b3 17 f8 14 7a 43 27 8a 6a 31 c4 47 3d 55 5d 33
38 -AT+DADDR=2602111D**
39 -)))
32 +AT+DADDR=2602111D
33 +}}}
40 40  
41 -(((
42 42  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.
43 43  
44 -
45 -)))
46 -
47 47  We need to input above keys in LG308 and enable ABP decryption.
48 48  
49 -[[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"]]
50 50  
51 51  Input the ABP keys in LG308
52 52  
... ... @@ -53,108 +53,84 @@
53 53  
54 54  == 2.1 Upstream ==
55 55  
56 -
57 57  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.
58 58  
59 -(((
60 60  We can see the log of LG308 to know this packet arrive
61 -)))
62 62  
63 -[[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"]]
64 64  
65 -LG308 log by "(% style="color:red" %)**logread -f**" (%%)command
52 +LG308 log by "logread -f" command
66 66  
67 67  
68 68  The data of End Node is stored in the file /var/iot/channels/2602111D. We can use hexdump command to check it.
69 69  
70 -(% class="box" %)
71 -(((
72 -root@dragino-1d25dc:~~# hexdump /var/iot/channels/2602111D
73 -0000000 (% style="color:#037691" %)**4646 4646 4646 3946 3030 3030 3030 3546**(%%)      ~-~-> Got RSSI and SNR    
74 -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
75 75  000001c
76 -)))
61 +}}}
77 77  
78 -* **RSSI**: 4646 4646 4646 3946 = 0xFFFF FF9F : So RSSI = (0xFFFF FF9F - 0x100000000) = -97
79 -* **SNR**: 3030 3030 3030 3546 = 0x0000 005F = 95, need to divide 10 so SNR is 9.5
80 -* **Payload**: 0xcc0c 0b63 0266 017f ff7f ff00
63 +* RSSI: 4646 4646 4646 3946 = 0xFFFF FF9F : So RSSI = (0xFFFF FF9F - 0x100000000) = -97
64 +* SNR: 3030 3030 3030 3546 = 0x0000 005F = 95, need to divide 10 so SNR is 9.5
65 +* Payload: 0xcc0c 0b63 0266 017f ff7f ff00
81 81  
82 -(% class="box" %)
83 -(((
84 -(% 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:
85 -in LGT92, use (% style="color:#037691" %)**AT+SEND=12:hello world** (%%)to send ASCII string
86 -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
87 87  0000000 4646 4646 4646 3946 3030 3030 3030 3546
88 -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"
89 89  000001c
90 -)))
74 +}}}
91 91  
92 -(% class="box" %)
93 -(((
94 -(% style="color:red" %)**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.
95 -)))
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 +}}}
96 96  
97 -
98 98  === 2.2.1 Decode Method ===
99 99  
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.
100 100  
101 -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.
102 -
103 103  For example we have a LHT65 , works in ABP mode and gateway successful get the data, which are:
104 104  
105 -(% class="box" %)
106 -(((
107 -root@dragino-1baf44:~~# hexdump /var/iot/channels/01826108
85 +{{{root@dragino-1baf44:~# hexdump /var/iot/channels/01826108
108 108  0000000 4646 4646 4646 4537 3030 3030 3030 3438
109 -0000010 ccd1 7fff 7fff 017f ff7f ff00         
87 +0000010 ccd1 7fff 7fff 017f ff7f ff00
110 110  000001c
111 -)))
89 +}}}
112 112  
113 -
114 114  If we choose ASCII decoder, the MQTT process will send out with mqtt-data:
115 115  
116 -(% class="box" %)
117 -(((
118 -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
119 119  Sun Sep 27 04:33:16 2020 user.notice root: [IoT.MQTT]:decoder: ASCII
120 -Sun Sep 27 04:33:16 2020 user.notice root: [IoT.MQTT]:mqtt_data[-m]: (% style="color:#037691" %)**ffffffe700000048ccd17fff7fff017fff7fff00**
121 -)))
95 +Sun Sep 27 04:33:16 2020 user.notice root: [IoT.MQTT]:mqtt_data[-m]: ffffffe700000048ccd17fff7fff017fff7fff00
96 +}}}
122 122  
123 -
124 124  If we choose Decode_LHT65, the MQTT process will send out with mqtt-data
125 125  
126 -(% class="box" %)
127 -(((
128 -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
129 129  Sun Sep 27 04:36:45 2020 user.notice root: [IoT.MQTT]:decoder: Dragino_LHT65
130 -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,
131 -"EXT":"Temperature Sensor","RSSI":-24,"TempC_SHT":85.0,"SNR":8.2,"ext_sensor":0}(%%)**
132 -)))
102 +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,
103 +"EXT":"Temperature Sensor","RSSI":-24,"TempC_SHT":85.0,"SNR":8.2,"ext_sensor":0}
104 +}}}
133 133  
134 134  Above scripts are store in /etc/lora/decoder/. User can put their scripts here and select it in the UI.
135 135  
136 136  
137 -
138 138  === 2.2.2 How to Decode My End Node ===
139 139  
111 +1/ Configure the ABP keys for your end node in the gateway. enable ABP decode in Web UI
140 140  
141 -**1.** Configure the ABP keys for your end node in the gateway. enable ABP decode in Web UI
113 +2/ Don't choose MQTT service, use LoRaWAN.
142 142  
143 -**2. **Don't choose MQTT service, use LoRaWAN.
115 +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
144 144  
145 -**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
117 +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:
146 146  
147 -**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:
148 -
149 149  {{{/etc/lora/decoder/Dragino_LHT65 END_NODE_DEV_ADDR
150 150  }}}
151 151  
152 -**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.
122 +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:
153 153  
154 -
155 -(% style="color:red" %)
156 -**Some notice:**
157 -
158 158  * RSSI and SNR are added when gateway receive the packet, so there is always this field.
159 159  * If you rename the file, please make it executable.
160 160  * See this link for lua.bit module: [[http:~~/~~/luaforge.net/projects/bit/>>url:http://luaforge.net/projects/bit/]]
... ... @@ -162,46 +162,45 @@
162 162  * the last line return is what will be used for MQTT
163 163  * User can use other language ,not limited to Lua, just make sure the return is what you want to send.
164 164  
165 -
166 166  == 2.2 Downstream ==
167 167  
168 -
169 169  In LG308, we can create a file in the directory /var/iot/push for downstream purpose. We recommend using each command to generate this file. This file will be used for transmission and auto-deleted after used
170 170  
171 171  The file should use below format:
172 172  
173 -(% style="color:#037691" %)**dev_addr,imme/time,txt/hex,payload**
174 174  
138 +dev_addr,imme/time,txt/hex,payload
139 +
175 175  Since fimware > Dragino-v2 lgw-5.4.1608518541 . Support more option
176 176  
177 -(% style="color:#037691" %)**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
178 178  
179 -* **dev_addr:** Inptu the device address
180 -* **imme/time:**
144 +* dev_addr: Inptu the device address
145 +* imme/time:
181 181  ** imme: send downstream immediately,For Class C end node.
182 182  ** time: send downstream after receive device's uplink. For Class A end node
183 -* **txt/hex:**
148 +* txt/hex:
184 184  ** txt: send payload in ASCII
185 185  ** hex: send payload in HEX
186 -* **payload: **payload to be sent, payload lenght should match the LoRaWAN protocol requirement.
187 -* **txpw:** Transmit Power. example: 20
188 -* **txbw:** bandwidth:
151 +* payload: payload to be sent, payload lenght should match the LoRaWAN protocol requirement.
152 +* txpw: Transmit Power. example: 20
153 +* txbw: bandwidth:
189 189  ** 1: 500 kHz
190 190  ** 2: 250 kHz
191 191  ** 3: 125 kHz
192 192  ** 4: 62.5 kHz
193 -* **SF:** Spreading Factor : SF7/SF8/SF9/SF10/SF11/SF12
194 -* **Frequency:** Transmit Frequency: example: 923300000
195 -* **rxwindow:** transmit on Rx1Window or Rx2Window.
158 +* SF: Spreading Factor : SF7/SF8/SF9/SF10/SF11/SF12
159 +* Frequency: Transmit Frequency: example: 923300000
160 +* rxwindow: transmit on Rx1Window or Rx2Window.
196 196  
197 197  
198 -(% style="color:blue" %)**Completely exmaple:**
163 +Completely exmaple:
199 199  
200 -* **Old version:** echo 018193F4,imme,hex,0101 > /var/iot/push/test
201 -* **New version:** echo 018193F4,imme,hex,0101,20,1,SF12,923300000,2 > /var/iot/push/test
165 +* Old version: echo 018193F4,imme,hex,0101 > /var/iot/push/test
166 +* New version: echo 018193F4,imme,hex,0101,20,1,SF12,923300000,2 > /var/iot/push/test
202 202  
203 203  
204 -(% style="color:#037691" %)**Downstream Frequency**
169 +Downstream Frequency
205 205  
206 206  The LG308 will use the RX2 window info to send the downstream payload, use the default LoRaWAN settings, as below:
207 207  
... ... @@ -215,27 +215,22 @@
215 215  * RU864: 869.1Mhz, SF12 BW125
216 216  
217 217  
218 -(% style="color:#037691" %)**Examples:**
183 +Examples:
219 219  
220 -(% class="box" %)
221 -(((
222 -we can use echo command to create files in LG308 for downstream.
223 -root@dragino-1d25dc:~~# echo 2602111D,time,hex,12345678 > /var/iot/push/test
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
224 224  
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).
225 225  
226 -**1)** From logread -f of gateway, we can see it has been added as pedning.
227 -lora_pkt_fwd[4286]: INFO~~ [DNLK]Looking file : test
228 -lora_pkt_fwd[4286]: INFO~~ [DNLK]devaddr:2602111D, txmode:time, pdfm:hex, size:4, payload1:4Vx,payload_hex:77C1BB90
229 -lora_pkt_fwd[4286]: INFO~~ [DNLK] DNLINK PENDING!(1 elems).
230 -
231 -
232 -**2)** When there is an upstrea from end node, this downstream will be sent and shows:
193 +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  
236 -
237 -**3)** and the end node will got:
238 -[5764825]~*~*~*~** UpLinkCounter= 98 ~*~*~*~**
197 +3) and the end node will got:
198 +[5764825]***** UpLinkCounter= 98 *****
239 239  [5764827]TX on freq 905300000 Hz at DR 0
240 240  Update Interval: 60000 ms
241 241  [5765202]txDone
... ... @@ -245,11 +245,11 @@
245 245  [5767501]rxDone
246 246  Rssi= -41
247 247  Receive data
248 -(% style="color:#037691" %)**2:12345678**  (%%) ~-~-> Hex
208 +2:12345678 --> Hex
209 +}}}
249 249  
250 -
251 -**4) **If we use the command "echo 2602111D,time,txt,12345678 > /var/iot/push/test" for downstream, the end node will got:
252 -[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 *****
253 253  [5955879]TX on freq 904100000 Hz at DR 0
254 254  Update Interval: 60000 ms
255 255  [5956254]txDone
... ... @@ -259,90 +259,79 @@
259 259  [5958595]rxDone
260 260  Rssi= -37
261 261  Receive data
262 -(% style="color:#037691" %)**2:3132333435363738**(%%) ~-~-> ASCII string "12345678"
263 -)))
222 +2:3132333435363738 --> ASCII string "12345678"
223 +}}}
264 264  
265 -
266 266  = 3. Example 1: Communicate with LT-22222-L =
267 267  
268 -
269 269  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]]
270 270  
271 -(% class="box" %)
272 -(((
273 -//#!/bin/sh
229 +{{{#!/bin/sh
274 274  # This scripts shows how to use LPS8/LG308/DLOS8 to communicate with two LoRaWAN End Nodes, without the use of internet or LoRaWAN server
275 275  #
276 -# Hardware Prepare:
277 -# 1. LT-22222-L x 2, both are configured to work in
278 -#   a) Class C ;
279 -# 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 ;
280 280  # c) AT+Mod=1
281 -# 2. LPS8,
282 -#   a) Firmware version >
283 -#   b) Input the LT-22222-L keys in LPS so LPS8 can talk with them.
284 -#   c) Lorawan server choose built-in
285 -#   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
286 286  #
287 -# How it works?
288 -#   a) Devices 1 sends a uplink payload to LPS8. LPS8 will get the DI1 and DI2 info from the payload
289 -#   b) LPS8 will send a message to Device 2 to set the Device2 DO1 = Device1 DI1, and Device DO2 = Device DI2.
290 -#   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
291 -#   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.
292 -#   ( The purpose of this step is to show that the Device2 has already do the change there).
293 -#
294 -#  For example: If current status of Device1 and Device2 leds shows:
295 -#  Device1: DI1: ON, DI2: ON , DO1: OFF,  DO2: OFF
296 -#  Device2: DI1: OFF, DI2: OFF , DO1: OFF,  DO2: OFF
297 -#
298 -#  Step2  will cause below change:
299 -#  Device1: DI1: ON, DI2: ON , DO1: OFF,  DO2: OFF
300 -#  Device2: DI1: OFF, DI2: OFF , DO1: ON,  DO2: ON
301 -# 
302 -#  Step3 will cause below change:
303 -#  Device1: DI1: ON, DI2: ON , DO1: ON,  DO2: ON
304 -#  Device2: DI1: OFF, DI2: OFF , DO1: ON,  DO2: ON
305 -#  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
306 -#  whether the Device 2 has been changed.//
307 -)))
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.}}}
308 308  
264 +~1. Input keys
309 309  
310 -**~1. Input keys**
266 +[[image:https://wiki.dragino.com/images/thumb/b/bf/LPS8_LT-22222_1.png/600px-LPS8_LT-22222_1.png||height="335" width="600"]]
311 311  
312 -[[image:image-20220527162450-3.png]]
313 -
314 314  Input Keys in LPS8
315 315  
270 +2. Make sure the LPS8 and LT use the same frequency bands, choose EU868 in this test.
316 316  
317 -**2. Make sure the LPS8 and LT use the same frequency bands, choose EU868 in this test.**
272 +3. Choose Built-in server
318 318  
274 +[[image:https://wiki.dragino.com/images/thumb/d/d7/LPS8_LT-22222_2.png/600px-LPS8_LT-22222_2.png||height="264" width="600"]]
319 319  
320 -**3. Choose Built-in server**
321 -
322 -[[image:image-20220527162518-4.png]]
323 -
324 324  Choose Built-in server
325 325  
278 +4. Run the script.
326 326  
327 -**4. Run the script.**
280 +[[image:https://wiki.dragino.com/images/thumb/3/39/LPS8_LT-22222_3.png/600px-LPS8_LT-22222_3.png||height="389" width="600"]]
328 328  
329 -[[image:image-20220722115213-2.png]]
330 -
331 331  Run the script
332 332  
284 +5. Output:
333 333  
334 -**5. Output:**
286 +[[image:https://wiki.dragino.com/images/thumb/f/fe/LPS8_LT-22222_4.png/600px-LPS8_LT-22222_4.png||height="433" width="600"]]
335 335  
336 -[[image:image-20220722115133-1.png]]
337 -
338 338  Output from LPS8
339 339  
340 340  
341 341  = 4. Example 2: Communicate to TCP Server =
342 342  
293 +[[image:https://wiki.dragino.com/images/thumb/7/75/LPS8_TCP_0.png/600px-LPS8_TCP_0.png||height="370" width="600"]]
343 343  
344 -[[image:image-20220527162648-7.png]]
345 -
346 346  Network Structure
347 347  
348 348  
... ... @@ -349,42 +349,35 @@
349 349  Full instruction video inlcude how to write scripts to fit server needed is here:
350 350  
351 351  
352 -(% style="color:#037691" %)**Video Instruction**(%%): **[[https:~~/~~/youtu.be/-nevW6U2TsE>>url:https://youtu.be/-nevW6U2TsE]]**
301 +Video Instruction: [[https:~~/~~/youtu.be/-nevW6U2TsE>>url:https://youtu.be/-nevW6U2TsE]]
353 353  
354 354  
355 -(% style="color:red" %)**Note: Firmware version must be higher than lgw-5.4.1607519907**
304 +Note: Firmware version must be higher than lgw-5.4.1607519907
356 356  
357 -
358 358  Assume we already set up ABP keys in the gateway:
359 359  
360 -[[image:image-20220527162852-8.png]]
308 +[[image:https://wiki.dragino.com/images/thumb/b/bf/LPS8_LT-22222_1.png/600px-LPS8_LT-22222_1.png||height="335" width="600"]]
361 361  
362 362  Input Keys in LPS8
363 363  
312 +run socket tool in PC
364 364  
314 +[[image:https://wiki.dragino.com/images/thumb/4/4b/LPS8_TCP_2.png/600px-LPS8_TCP_2.png||height="212" width="600"]]
365 365  
366 -**run socket tool in PC**
367 -
368 -[[image:image-20220527163028-9.png]]
369 -
370 -
371 371  Socket tool
372 372  
373 373  
319 +Input Server address and port
374 374  
375 -**Input Server address and port**
321 +[[image:https://wiki.dragino.com/images/thumb/c/c6/LPS8_TCP_3.png/600px-LPS8_TCP_3.png||height="306" width="600"]]
376 376  
377 -[[image:image-20220527163106-10.png]]
378 -
379 379  Input Server address and port
380 380  
381 381  
326 +See value receive in socket tool. :
382 382  
383 -**See value receive in socket tool:**
328 +[[image:https://wiki.dragino.com/images/thumb/2/20/LPS8_TCP_4.png/600px-LPS8_TCP_4.png||height="219" width="600"]]
384 384  
385 -[[image:image-20220527163144-11.png]]
386 -
387 387  value receive in socket tool
388 388  
389 -
390 390  If user want to modify the TCP connection method. He can refer: [[https:~~/~~/github.com/dragino/dragino-packages/blob/lg02/haserl-ui/root/usr/bin/tcp_process.sh>>url:https://github.com/dragino/dragino-packages/blob/lg02/haserl-ui/root/usr/bin/tcp_process.sh]]. Same script is on /usr/bin of gateway.
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
image-20220527162450-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -125.4 KB
Content
image-20220527162518-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -72.8 KB
Content
image-20220527162552-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -33.6 KB
Content
image-20220527162619-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -41.0 KB
Content
image-20220527162648-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -151.7 KB
Content
image-20220527162852-8.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -125.6 KB
Content
image-20220527163028-9.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -32.9 KB
Content
image-20220527163106-10.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -34.5 KB
Content
image-20220527163144-11.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -107.7 KB
Content
image-20220722115133-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -35.1 KB
Content
image-20220722115213-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -27.7 KB
Content

Applications

Navigation

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