Last modified by Xiaoling on 2023/04/20 18:14
<
From version < 16.8 >
edited by Xiaoling
on 2022/07/22 11:46
To version < 1.6 >
edited by Xiaoling
on 2022/05/12 17:52
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,52 +1,40 @@
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 -(((
16 -The basic of this feature is the decoding of (% style="color:red" %)**LoRaWAN ABP End Node**(%%). Requirements:
17 -)))
18 18  
14 +The basic of this feature is the decoding of LoRaWAN ABP End Node. Requirements:
15 +
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/]](%%)**
18 +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]]**
24 +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
28 +{{{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 -)))
30 +AT+DADDR=2602111D
31 +}}}
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]]
37 +[[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]]
48 +[[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
50 +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
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
75 75  000001c
76 -)))
59 +}}}
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
61 +* RSSI: 4646 4646 4646 3946 = 0xFFFF FF9F : So RSSI = (0xFFFF FF9F - 0x100000000) = -97
62 +* SNR: 3030 3030 3030 3546 = 0x0000 005F = 95, need to divide 10 so SNR is 9.5
63 +* 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
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
87 87  0000000 4646 4646 4646 3946 3030 3030 3030 3546
88 -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"
89 89  000001c
90 -)))
72 +}}}
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 -)))
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 +}}}
96 96  
97 -
98 98  === 2.2.1 Decode Method ===
99 99  
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.
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
83 +{{{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         
85 +0000010 ccd1 7fff 7fff 017f ff7f ff00
110 110  000001c
111 -)))
87 +}}}
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
91 +{{{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 -)))
93 +Sun Sep 27 04:33:16 2020 user.notice root: [IoT.MQTT]:mqtt_data[-m]: ffffffe700000048ccd17fff7fff017fff7fff00
94 +}}}
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
98 +{{{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 -)))
100 +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,
101 +"EXT":"Temperature Sensor","RSSI":-24,"TempC_SHT":85.0,"SNR":8.2,"ext_sensor":0}
102 +}}}
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  
109 +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
111 +2/ Don't choose MQTT service, use LoRaWAN.
142 142  
143 -**2. **Don't choose MQTT service, use LoRaWAN.
113 +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
115 +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.
120 +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/]]
... ... @@ -164,43 +164,43 @@
164 164  
165 165  == 2.2 Downstream ==
166 166  
167 -
168 168  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
169 169  
170 170  The file should use below format:
171 171  
172 -(% style="color:#037691" %)**dev_addr,imme/time,txt/hex,payload**
173 173  
136 +dev_addr,imme/time,txt/hex,payload
137 +
174 174  Since fimware > Dragino-v2 lgw-5.4.1608518541 . Support more option
175 175  
176 -(% style="color:#037691" %)**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
177 177  
178 -* **dev_addr:** Inptu the device address
179 -* **imme/time:**
142 +* dev_addr: Inptu the device address
143 +* imme/time:
180 180  ** imme: send downstream immediately,For Class C end node.
181 181  ** time: send downstream after receive device's uplink. For Class A end node
182 -* **txt/hex:**
146 +* txt/hex:
183 183  ** txt: send payload in ASCII
184 184  ** hex: send payload in HEX
185 -* **payload: **payload to be sent, payload lenght should match the LoRaWAN protocol requirement.
186 -* **txpw:** Transmit Power. example: 20
187 -* **txbw:** bandwidth:
149 +* payload: payload to be sent, payload lenght should match the LoRaWAN protocol requirement.
150 +* txpw: Transmit Power. example: 20
151 +* txbw: bandwidth:
188 188  ** 1: 500 kHz
189 189  ** 2: 250 kHz
190 190  ** 3: 125 kHz
191 191  ** 4: 62.5 kHz
192 -* **SF:** Spreading Factor : SF7/SF8/SF9/SF10/SF11/SF12
193 -* **Frequency:** Transmit Frequency: example: 923300000
194 -* **rxwindow:** transmit on Rx1Window or Rx2Window.
156 +* SF: Spreading Factor : SF7/SF8/SF9/SF10/SF11/SF12
157 +* Frequency: Transmit Frequency: example: 923300000
158 +* rxwindow: transmit on Rx1Window or Rx2Window.
195 195  
196 196  
197 -(% style="color:blue" %)**Completely exmaple:**
161 +Completely exmaple:
198 198  
199 -* **Old version:** echo 018193F4,imme,hex,0101 > /var/iot/push/test
200 -* **New version:** echo 018193F4,imme,hex,0101,20,1,SF12,923300000,2 > /var/iot/push/test
163 +* Old version: echo 018193F4,imme,hex,0101 > /var/iot/push/test
164 +* New version: echo 018193F4,imme,hex,0101,20,1,SF12,923300000,2 > /var/iot/push/test
201 201  
202 202  
203 -(% style="color:#037691" %)**Downstream Frequency**
167 +Downstream Frequency
204 204  
205 205  The LG308 will use the RX2 window info to send the downstream payload, use the default LoRaWAN settings, as below:
206 206  
... ... @@ -214,27 +214,22 @@
214 214  * RU864: 869.1Mhz, SF12 BW125
215 215  
216 216  
217 -(% style="color:#037691" %)**Examples:**
181 +Examples:
218 218  
219 -(% class="box" %)
220 -(((
221 -we can use echo command to create files in LG308 for downstream.
222 -root@dragino-1d25dc:~~# echo 2602111D,time,hex,12345678 > /var/iot/push/test
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
223 223  
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).
224 224  
225 -**1)** From logread -f of gateway, we can see it has been added as pedning.
226 -lora_pkt_fwd[4286]: INFO~~ [DNLK]Looking file : test
227 -lora_pkt_fwd[4286]: INFO~~ [DNLK]devaddr:2602111D, txmode:time, pdfm:hex, size:4, payload1:4Vx,payload_hex:77C1BB90
228 -lora_pkt_fwd[4286]: INFO~~ [DNLK] DNLINK PENDING!(1 elems).
229 -
230 -
231 -**2)** When there is an upstrea from end node, this downstream will be sent and shows:
191 +2) When there is an upstrea from end node, this downstream will be sent and shows:
232 232  lora_pkt_fwd[4286]: INFO: tx_start_delay=1497 (1497.000000) - (1497, bw_delay=0.000000, notch_delay=0.000000)
233 233  lora_pkt_fwd[4286]: [LGWSEND]lgw_send done: count_us=3537314420, freq=923300000, size=17
234 234  
235 -
236 -**3)** and the end node will got:
237 -[5764825]~*~*~*~** UpLinkCounter= 98 ~*~*~*~**
195 +3) and the end node will got:
196 +[5764825]***** UpLinkCounter= 98 *****
238 238  [5764827]TX on freq 905300000 Hz at DR 0
239 239  Update Interval: 60000 ms
240 240  [5765202]txDone
... ... @@ -244,11 +244,11 @@
244 244  [5767501]rxDone
245 245  Rssi= -41
246 246  Receive data
247 -(% style="color:#037691" %)**2:12345678**  (%%) ~-~-> Hex
206 +2:12345678 --> Hex
207 +}}}
248 248  
249 -
250 -**4) **If we use the command "echo 2602111D,time,txt,12345678 > /var/iot/push/test" for downstream, the end node will got:
251 -[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 *****
252 252  [5955879]TX on freq 904100000 Hz at DR 0
253 253  Update Interval: 60000 ms
254 254  [5956254]txDone
... ... @@ -258,90 +258,79 @@
258 258  [5958595]rxDone
259 259  Rssi= -37
260 260  Receive data
261 -(% style="color:#037691" %)**2:3132333435363738**(%%) ~-~-> ASCII string "12345678"
262 -)))
220 +2:3132333435363738 --> ASCII string "12345678"
221 +}}}
263 263  
264 -
265 265  = 3. Example 1: Communicate with LT-22222-L =
266 266  
267 -
268 268  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]]
269 269  
270 -(% class="box" %)
271 -(((
272 -//#!/bin/sh
227 +{{{#!/bin/sh
273 273  # This scripts shows how to use LPS8/LG308/DLOS8 to communicate with two LoRaWAN End Nodes, without the use of internet or LoRaWAN server
274 274  #
275 -# Hardware Prepare:
276 -# 1. LT-22222-L x 2, both are configured to work in
277 -#   a) Class C ;
278 -# 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 ;
279 279  # c) AT+Mod=1
280 -# 2. LPS8,
281 -#   a) Firmware version >
282 -#   b) Input the LT-22222-L keys in LPS so LPS8 can talk with them.
283 -#   c) Lorawan server choose built-in
284 -#   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
285 285  #
286 -# How it works?
287 -#   a) Devices 1 sends a uplink payload to LPS8. LPS8 will get the DI1 and DI2 info from the payload
288 -#   b) LPS8 will send a message to Device 2 to set the Device2 DO1 = Device1 DI1, and Device DO2 = Device DI2.
289 -#   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
290 -#   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.
291 -#   ( The purpose of this step is to show that the Device2 has already do the change there).
292 -#
293 -#  For example: If current status of Device1 and Device2 leds shows:
294 -#  Device1: DI1: ON, DI2: ON , DO1: OFF,  DO2: OFF
295 -#  Device2: DI1: OFF, DI2: OFF , DO1: OFF,  DO2: OFF
296 -#
297 -#  Step2  will cause below change:
298 -#  Device1: DI1: ON, DI2: ON , DO1: OFF,  DO2: OFF
299 -#  Device2: DI1: OFF, DI2: OFF , DO1: ON,  DO2: ON
300 -# 
301 -#  Step3 will cause below change:
302 -#  Device1: DI1: ON, DI2: ON , DO1: ON,  DO2: ON
303 -#  Device2: DI1: OFF, DI2: OFF , DO1: ON,  DO2: ON
304 -#  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
305 -#  whether the Device 2 has been changed.//
306 -)))
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.}}}
307 307  
262 +~1. Input keys
308 308  
309 -**~1. Input keys**
264 +[[image:https://wiki.dragino.com/images/thumb/b/bf/LPS8_LT-22222_1.png/600px-LPS8_LT-22222_1.png||height="335" width="600"]]
310 310  
311 -[[image:image-20220527162450-3.png]]
312 -
313 313  Input Keys in LPS8
314 314  
268 +2. Make sure the LPS8 and LT use the same frequency bands, choose EU868 in this test.
315 315  
316 -**2. Make sure the LPS8 and LT use the same frequency bands, choose EU868 in this test.**
270 +3. Choose Built-in server
317 317  
272 +[[image:https://wiki.dragino.com/images/thumb/d/d7/LPS8_LT-22222_2.png/600px-LPS8_LT-22222_2.png||height="264" width="600"]]
318 318  
319 -**3. Choose Built-in server**
320 -
321 -[[image:image-20220527162518-4.png]]
322 -
323 323  Choose Built-in server
324 324  
276 +4. Run the script.
325 325  
326 -**4. Run the script.**
278 +[[image:https://wiki.dragino.com/images/thumb/3/39/LPS8_LT-22222_3.png/600px-LPS8_LT-22222_3.png||height="389" width="600"]]
327 327  
328 -[[image:image-20220527162552-5.png]]
329 -
330 330  Run the script
331 331  
282 +5. Output:
332 332  
333 -**5. Output:**
284 +[[image:https://wiki.dragino.com/images/thumb/f/fe/LPS8_LT-22222_4.png/600px-LPS8_LT-22222_4.png||height="433" width="600"]]
334 334  
335 -[[image:image-20220527162619-6.png]]
336 -
337 337  Output from LPS8
338 338  
339 339  
340 340  = 4. Example 2: Communicate to TCP Server =
341 341  
291 +[[image:https://wiki.dragino.com/images/thumb/7/75/LPS8_TCP_0.png/600px-LPS8_TCP_0.png||height="370" width="600"]]
342 342  
343 -[[image:image-20220527162648-7.png]]
344 -
345 345  Network Structure
346 346  
347 347  
... ... @@ -348,42 +348,35 @@
348 348  Full instruction video inlcude how to write scripts to fit server needed is here:
349 349  
350 350  
351 -(% style="color:#037691" %)**Video Instruction**(%%): **[[https:~~/~~/youtu.be/-nevW6U2TsE>>url:https://youtu.be/-nevW6U2TsE]]**
299 +Video Instruction: [[https:~~/~~/youtu.be/-nevW6U2TsE>>url:https://youtu.be/-nevW6U2TsE]]
352 352  
353 353  
354 -(% style="color:red" %)**Note: Firmware version must be higher than lgw-5.4.1607519907**
302 +Note: Firmware version must be higher than lgw-5.4.1607519907
355 355  
356 -
357 357  Assume we already set up ABP keys in the gateway:
358 358  
359 -[[image:image-20220527162852-8.png]]
306 +[[image:https://wiki.dragino.com/images/thumb/b/bf/LPS8_LT-22222_1.png/600px-LPS8_LT-22222_1.png||height="335" width="600"]]
360 360  
361 361  Input Keys in LPS8
362 362  
310 +run socket tool in PC
363 363  
312 +[[image:https://wiki.dragino.com/images/thumb/4/4b/LPS8_TCP_2.png/600px-LPS8_TCP_2.png||height="212" width="600"]]
364 364  
365 -**run socket tool in PC**
366 -
367 -[[image:image-20220527163028-9.png]]
368 -
369 -
370 370  Socket tool
371 371  
372 372  
317 +Input Server address and port
373 373  
374 -**Input Server address and port**
319 +[[image:https://wiki.dragino.com/images/thumb/c/c6/LPS8_TCP_3.png/600px-LPS8_TCP_3.png||height="306" width="600"]]
375 375  
376 -[[image:image-20220527163106-10.png]]
377 -
378 378  Input Server address and port
379 379  
380 380  
324 +See value receive in socket tool. :
381 381  
382 -**See value receive in socket tool:**
326 +[[image:https://wiki.dragino.com/images/thumb/2/20/LPS8_TCP_4.png/600px-LPS8_TCP_4.png||height="219" width="600"]]
383 383  
384 -[[image:image-20220527163144-11.png]]
385 -
386 386  value receive in socket tool
387 387  
388 -
389 389  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

Applications

Navigation

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