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

Summary

Details

Page properties
Content
... ... @@ -1,46 +1,50 @@
1 - **Contents:**
1 +**Table of Contents:**
2 2  
3 3  {{toc/}}
4 4  
5 5  
6 +
6 6  = 1. Introduction =
7 7  
9 +
8 8  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:
9 9  
10 10  * 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 +* 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]]).
12 12  
13 13  (((
14 -
15 -The basic of this feature is the decoding of **LoRaWAN ABP End Node**. Requirements:
16 +The basic of this feature is the decoding of (% style="color:red" %)**LoRaWAN ABP End Node**(%%). Requirements:
16 16  )))
17 17  
18 18  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
19 19  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]]
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/]]
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/]](%%)**
21 21  
22 22  
23 23  = 2. How it works =
24 24  
25 25  
26 -**Video Instruction**: [[https:~~/~~/youtu.be/ZBjXwmp7rwM>>url:https://youtu.be/ZBjXwmp7rwM]]
27 +(% style="color:#037691" %)**Video Instruction**(%%): **[[https:~~/~~/youtu.be/ZBjXwmp7rwM>>url:https://youtu.be/ZBjXwmp7rwM]]**
27 27  
29 +
28 28  Assume we have the LoRaWAN tracker LGT92 which works in ABP mode and US915 band. It has below keys:
29 29  
30 30  (% class="box infomessage" %)
31 31  (((
32 -AT+NWKSKEY=72 32 63 95 dd 8f e2 b2 13 66 e4 35 93 8f 55 df
34 +**AT+NWKSKEY=72 32 63 95 dd 8f e2 b2 13 66 e4 35 93 8f 55 df
33 33  AT+APPSKEY=b3 17 f8 14 7a 43 27 8a 6a 31 c4 47 3d 55 5d 33
34 -AT+DADDR=2602111D
36 +AT+DADDR=2602111D**
35 35  )))
36 36  
37 37  (((
38 38  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 +
39 39  )))
40 40  
41 41  We need to input above keys in LG308 and enable ABP decryption.
42 42  
43 -[[image:https://wiki.dragino.com/images/thumb/5/55/LG308_MQTT_1.png/600px-LG308_MQTT_1.png||height="329" width="600"]]
47 +[[image:image-20220527161119-1.png]]
44 44  
45 45  Input the ABP keys in LG308
46 46  
... ... @@ -47,6 +47,7 @@
47 47  
48 48  == 2.1 Upstream ==
49 49  
54 +
50 50  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.
51 51  
52 52  (((
... ... @@ -53,9 +53,9 @@
53 53  We can see the log of LG308 to know this packet arrive
54 54  )))
55 55  
56 -[[image:https://wiki.dragino.com/images/thumb/1/16/ABP_DECODE_2.png/600px-ABP_DECODE_2.png||height="205" width="600"]]
61 +[[image:image-20220527161149-2.png]]
57 57  
58 -LG308 log by "logread -f" command
63 +LG308 log by "(% style="color:red" %)**logread -f**" (%%)command
59 59  
60 60  
61 61  The data of End Node is stored in the file /var/iot/channels/2602111D. We can use hexdump command to check it.
... ... @@ -63,19 +63,19 @@
63 63  (% class="box" %)
64 64  (((
65 65  root@dragino-1d25dc:~~# hexdump /var/iot/channels/2602111D
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
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
68 68  000001c
69 69  )))
70 70  
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
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
74 74  
75 75  (% class="box" %)
76 76  (((
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
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
79 79  root@dragino-1d25dc:~~# hexdump /var/iot/channels/2602111D
80 80  0000000 4646 4646 4646 3946 3030 3030 3030 3546
81 81  0000010 6865 6c6c 6f20 776f 726c 6400      ~-~-> Got ASCII code "hello world"    
... ... @@ -84,13 +84,15 @@
84 84  
85 85  (% class="box" %)
86 86  (((
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.
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.
88 88  )))
89 89  
95 +
90 90  === 2.2.1 Decode Method ===
91 91  
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.
93 93  
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 +
94 94  For example we have a LHT65 , works in ABP mode and gateway successful get the data, which are:
95 95  
96 96  (% class="box" %)
... ... @@ -101,6 +101,7 @@
101 101  000001c
102 102  )))
103 103  
111 +
104 104  If we choose ASCII decoder, the MQTT process will send out with mqtt-data:
105 105  
106 106  (% class="box" %)
... ... @@ -107,9 +107,10 @@
107 107  (((
108 108  Sun Sep 27 04:33:16 2020 user.notice root: [IoT.MQTT]:pub_topic[-t]: dragino-1baf44/01826108/data
109 109  Sun Sep 27 04:33:16 2020 user.notice root: [IoT.MQTT]:decoder: ASCII
110 -Sun Sep 27 04:33:16 2020 user.notice root: [IoT.MQTT]:mqtt_data[-m]: ffffffe700000048ccd17fff7fff017fff7fff00
118 +Sun Sep 27 04:33:16 2020 user.notice root: [IoT.MQTT]:mqtt_data[-m]: (% style="color:#037691" %)**ffffffe700000048ccd17fff7fff017fff7fff00**
111 111  )))
112 112  
121 +
113 113  If we choose Decode_LHT65, the MQTT process will send out with mqtt-data
114 114  
115 115  (% class="box" %)
... ... @@ -116,28 +116,34 @@
116 116  (((
117 117  Sun Sep 27 04:36:45 2020 user.notice root: [IoT.MQTT]:pub_topic[-t]: dragino-1baf44/01826108/data
118 118  Sun Sep 27 04:36:45 2020 user.notice root: [IoT.MQTT]:decoder: Dragino_LHT65
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}
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}(%%)**
121 121  )))
122 122  
123 123  Above scripts are store in /etc/lora/decoder/. User can put their scripts here and select it in the UI.
124 124  
125 125  
135 +
126 126  === 2.2.2 How to Decode My End Node ===
127 127  
128 -1/ Configure the ABP keys for your end node in the gateway. enable ABP decode in Web UI
129 129  
130 -2/ Don't choose MQTT service, use LoRaWAN.
139 +**1.** Configure the ABP keys for your end node in the gateway. enable ABP decode in Web UI
131 131  
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
141 +**2. **Don't choose MQTT service, use LoRaWAN.
133 133  
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:
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
135 135  
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 +
136 136  {{{/etc/lora/decoder/Dragino_LHT65 END_NODE_DEV_ADDR
137 137  }}}
138 138  
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:
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.
140 140  
152 +
153 +(% style="color:red" %)
154 +**Some notice:**
155 +
141 141  * RSSI and SNR are added when gateway receive the packet, so there is always this field.
142 142  * If you rename the file, please make it executable.
143 143  * See this link for lua.bit module: [[http:~~/~~/luaforge.net/projects/bit/>>url:http://luaforge.net/projects/bit/]]
... ... @@ -145,46 +145,52 @@
145 145  * the last line return is what will be used for MQTT
146 146  * User can use other language ,not limited to Lua, just make sure the return is what you want to send.
147 147  
163 +
164 +
148 148  == 2.2 Downstream ==
149 149  
167 +
150 150  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
151 151  
152 152  The file should use below format:
153 153  
172 +(% style="color:#037691" %)**dev_addr,imme/time,txt/hex,payload**
154 154  
155 -dev_addr,imme/time,txt/hex,payload
156 -
157 157  Since fimware > Dragino-v2 lgw-5.4.1608518541 . Support more option
158 158  
159 -dev_addr,imme/time,txt/hex,payload,txpw,txbw,SF,frequency,rxwindow
176 +(% style="color:#037691" %)**dev_addr,imme/time,txt/hex,payload,txpw,txbw,SF,frequency,rxwindow**
160 160  
161 -* dev_addr: Inptu the device address
162 -* imme/time:
178 +* **dev_addr:** Inptu the device address
179 +* **imme/time:**
163 163  ** imme: send downstream immediately,For Class C end node.
164 164  ** time: send downstream after receive device's uplink. For Class A end node
165 -* txt/hex:
182 +* **txt/hex:**
166 166  ** txt: send payload in ASCII
167 167  ** hex: send payload in HEX
168 -* payload: payload to be sent, payload lenght should match the LoRaWAN protocol requirement.
169 -* txpw: Transmit Power. example: 20
170 -* txbw: bandwidth:
185 +* **payload: **payload to be sent, payload lenght should match the LoRaWAN protocol requirement.
186 +* **txpw:** Transmit Power. example: 20
187 +* **txbw:** bandwidth:
171 171  ** 1: 500 kHz
172 172  ** 2: 250 kHz
173 173  ** 3: 125 kHz
174 174  ** 4: 62.5 kHz
175 -* SF: Spreading Factor : SF7/SF8/SF9/SF10/SF11/SF12
176 -* Frequency: Transmit Frequency: example: 923300000
177 -* rxwindow: transmit on Rx1Window or Rx2Window.
192 +* **SF:** Spreading Factor : SF7/SF8/SF9/SF10/SF11/SF12
193 +* **Frequency:** Transmit Frequency: example: 923300000
194 +* **rxwindow:** transmit on Rx1Window or Rx2Window.
178 178  
179 179  
180 -Completely exmaple:
181 181  
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
184 184  
199 +(% style="color:blue" %)**Completely exmaple:**
185 185  
186 -Downstream Frequency
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
187 187  
204 +
205 +
206 +
207 +(% style="color:#037691" %)**Downstream Frequency**
208 +
188 188  The LG308 will use the RX2 window info to send the downstream payload, use the default LoRaWAN settings, as below:
189 189  
190 190  * EU868: 869.525Mhz, DR0(SF12BW125)
... ... @@ -197,22 +197,35 @@
197 197  * RU864: 869.1Mhz, SF12 BW125
198 198  
199 199  
200 -Examples:
201 201  
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
204 204  
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).
223 +(% style="color:#037691" %)**Examples:**
209 209  
210 -2) When there is an upstrea from end node, this downstream will be sent and shows:
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:
211 211  lora_pkt_fwd[4286]: INFO: tx_start_delay=1497 (1497.000000) - (1497, bw_delay=0.000000, notch_delay=0.000000)
212 212  lora_pkt_fwd[4286]: [LGWSEND]lgw_send done: count_us=3537314420, freq=923300000, size=17
244 +)))
213 213  
214 -3) and the end node will got:
215 -[5764825]***** UpLinkCounter= 98 *****
246 +(% class="box" %)
247 +(((
248 +**3)** and the end node will got:
249 +[5764825]~*~*~*~** UpLinkCounter= 98 ~*~*~*~**
216 216  [5764827]TX on freq 905300000 Hz at DR 0
217 217  Update Interval: 60000 ms
218 218  [5765202]txDone
... ... @@ -222,11 +222,13 @@
222 222  [5767501]rxDone
223 223  Rssi= -41
224 224  Receive data
225 -2:12345678 --> Hex
226 -}}}
259 +(% style="color:#037691" %)**2:12345678**  (%%) ~-~-> Hex
260 +)))
227 227  
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 *****
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 ~*~*~*~**
230 230  [5955879]TX on freq 904100000 Hz at DR 0
231 231  Update Interval: 60000 ms
232 232  [5956254]txDone
... ... @@ -236,79 +236,88 @@
236 236  [5958595]rxDone
237 237  Rssi= -37
238 238  Receive data
239 -2:3132333435363738 --> ASCII string "12345678"
240 -}}}
275 +(% style="color:#037691" %)**2:3132333435363738**(%%) ~-~-> ASCII string "12345678"
276 +)))
241 241  
278 +
242 242  = 3. Example 1: Communicate with LT-22222-L =
243 243  
281 +
244 244  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]]
245 245  
246 -{{{#!/bin/sh
284 +(% class="box" %)
285 +(((
286 +//#!/bin/sh
247 247  # This scripts shows how to use LPS8/LG308/DLOS8 to communicate with two LoRaWAN End Nodes, without the use of internet or LoRaWAN server
248 248  #
249 -# Hardware Prepare:
250 -# 1. LT-22222-L x 2, both are configured to work in
251 -# a) Class C ;
252 -# b) ABP Mode ;
289 +# Hardware Prepare:
290 +# 1. LT-22222-L x 2, both are configured to work in
291 +#   a) Class C ;
292 +# b) ABP Mode ;
253 253  # c) AT+Mod=1
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
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)
270 270  #
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.}}}
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 +)))
280 280  
281 -~1. Input keys
322 +**~1. Input keys**
282 282  
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"]]
324 +[[image:image-20220527162450-3.png]]
284 284  
285 285  Input Keys in LPS8
286 286  
287 -2. Make sure the LPS8 and LT use the same frequency bands, choose EU868 in this test.
288 288  
289 -3. Choose Built-in server
329 +**2. Make sure the LPS8 and LT use the same frequency bands, choose EU868 in this test.**
290 290  
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"]]
331 +**3. Choose Built-in server**
292 292  
333 +[[image:image-20220527162518-4.png]]
334 +
293 293  Choose Built-in server
294 294  
295 -4. Run the script.
296 296  
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"]]
338 +**4. Run the script.**
298 298  
340 +[[image:image-20220527162552-5.png]]
341 +
299 299  Run the script
300 300  
301 -5. Output:
302 302  
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"]]
345 +**5. Output:**
304 304  
347 +[[image:image-20220527162619-6.png]]
348 +
305 305  Output from LPS8
306 306  
307 307  
308 308  = 4. Example 2: Communicate to TCP Server =
309 309  
310 -[[image:https://wiki.dragino.com/images/thumb/7/75/LPS8_TCP_0.png/600px-LPS8_TCP_0.png||height="370" width="600"]]
311 311  
355 +[[image:image-20220527162648-7.png]]
356 +
312 312  Network Structure
313 313  
314 314  
... ... @@ -315,35 +315,42 @@
315 315  Full instruction video inlcude how to write scripts to fit server needed is here:
316 316  
317 317  
318 -Video Instruction: [[https:~~/~~/youtu.be/-nevW6U2TsE>>url:https://youtu.be/-nevW6U2TsE]]
363 +(% style="color:#037691" %)**Video Instruction**(%%): **[[https:~~/~~/youtu.be/-nevW6U2TsE>>url:https://youtu.be/-nevW6U2TsE]]**
319 319  
320 320  
321 -Note: Firmware version must be higher than lgw-5.4.1607519907
366 +(% style="color:red" %)**Note: Firmware version must be higher than lgw-5.4.1607519907**
322 322  
368 +
323 323  Assume we already set up ABP keys in the gateway:
324 324  
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"]]
371 +[[image:image-20220527162852-8.png]]
326 326  
327 327  Input Keys in LPS8
328 328  
329 -run socket tool in PC
330 330  
331 -[[image:https://wiki.dragino.com/images/thumb/4/4b/LPS8_TCP_2.png/600px-LPS8_TCP_2.png||height="212" width="600"]]
332 332  
377 +**run socket tool in PC**
378 +
379 +[[image:image-20220527163028-9.png]]
380 +
381 +
333 333  Socket tool
334 334  
335 335  
336 -Input Server address and port
337 337  
338 -[[image:https://wiki.dragino.com/images/thumb/c/c6/LPS8_TCP_3.png/600px-LPS8_TCP_3.png||height="306" width="600"]]
386 +**Input Server address and port**
339 339  
388 +[[image:image-20220527163106-10.png]]
389 +
340 340  Input Server address and port
341 341  
342 342  
343 -See value receive in socket tool. :
344 344  
345 -[[image:https://wiki.dragino.com/images/thumb/2/20/LPS8_TCP_4.png/600px-LPS8_TCP_4.png||height="219" width="600"]]
394 +**See value receive in socket tool:**
346 346  
396 +[[image:image-20220527163144-11.png]]
397 +
347 347  value receive in socket tool
348 348  
400 +
349 349  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