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