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

Summary

Details

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

Applications

Navigation

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