Last modified by Xiaoling on 2023/04/20 18:14
<
From version < 16.3 >
edited by Xiaoling
on 2022/07/22 11:41
To version < 1.8 >
edited by Xiaoling
on 2022/05/12 18:01
>
Change comment: There is no comment for this version

Summary

Details

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