Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -1,4 +1,5 @@
1		-**Table of Contents:**
	1	+*
	2	+** Table of** **Contents:
2	2
3	3	{{toc/}}
4	4
...	...	@@ -20,9 +20,6 @@
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	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/]](%%)**
22	22
23		-
24		-
25		-
26	26	= 2. How it works =
27	27
28	28
...	...	@@ -134,27 +134,22 @@
134	134	Above scripts are store in /etc/lora/decoder/. User can put their scripts here and select it in the UI.
135	135
136	136
137		-
138	138	=== 2.2.2 How to Decode My End Node ===
139	139
140	140
141		-**1.** Configure the ABP keys for your end node in the gateway. enable ABP decode in Web UI
	138	+1/ Configure the ABP keys for your end node in the gateway. enable ABP decode in Web UI
142	142
143		-**2. **Don't choose MQTT service, use LoRaWAN.
	140	+2/ Don't choose MQTT service, use LoRaWAN.
144	144
145		-**3.** When your end node send a message to the gateway, there will be a file store in /var/iot/channels. full path should be /var/iot/channels/END_NODE_DEV_ADDR
	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
146	146
147		-**4.** Use the /etc/lora/decoder/Dragino_LHT65 as template to decode your payload. This script is written in Lua language. User can manually call this script when you see the data file in /var/iot/channels by running:
	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:
148	148
149	149	{{{/etc/lora/decoder/Dragino_LHT65 END_NODE_DEV_ADDR
150	150	}}}
151	151
152		-**5.** What you see as output is the MQTT data device will upload, user's end node has different payload compare with LHT65, most properly this file will report with error. User need to modify to match the actual payload.
	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. Some notice:
153	153
154		-
155		-(% style="color:red" %)
156		-**Some notice:**
157		-
158	158	* RSSI and SNR are added when gateway receive the packet, so there is always this field.
159	159	* If you rename the file, please make it executable.
160	160	* See this link for lua.bit module: [[http:~~/~~/luaforge.net/projects/bit/>>url:http://luaforge.net/projects/bit/]]
...	...	@@ -162,6 +162,8 @@
162	162	* the last line return is what will be used for MQTT
163	163	* User can use other language ,not limited to Lua, just make sure the return is what you want to send.
164	164
	158	+
	159	+
165	165	== 2.2 Downstream ==
166	166
167	167
...	...	@@ -200,6 +200,7 @@
200	200	* **New version:** echo 018193F4,imme,hex,0101,20,1,SF12,923300000,2 > /var/iot/push/test
201	201
202	202
	198	+
203	203	(% style="color:#037691" %)**Downstream Frequency**
204	204
205	205	The LG308 will use the RX2 window info to send the downstream payload, use the default LoRaWAN settings, as below:
...	...	@@ -214,6 +214,7 @@
214	214	* RU864: 869.1Mhz, SF12 BW125
215	215
216	216
	213	+
217	217	(% style="color:#037691" %)**Examples:**
218	218
219	219	(% class="box" %)
...	...	@@ -220,19 +220,25 @@
220	220	(((
221	221	we can use echo command to create files in LG308 for downstream.
222	222	root@dragino-1d25dc:~~# echo 2602111D,time,hex,12345678 > /var/iot/push/test
	220	+)))
223	223
224		-
	222	+(% class="box" %)
	223	+(((
225	225	**1)** From logread -f of gateway, we can see it has been added as pedning.
226	226	lora_pkt_fwd[4286]: INFO~~ [DNLK]Looking file : test
227	227	lora_pkt_fwd[4286]: INFO~~ [DNLK]devaddr:2602111D, txmode:time, pdfm:hex, size:4, payload1:4Vx,payload_hex:77C1BB90
228	228	lora_pkt_fwd[4286]: INFO~~ [DNLK] DNLINK PENDING!(1 elems).
	228	+)))
229	229
230		-
	230	+(% class="box" %)
	231	+(((
231	231	**2)** When there is an upstrea from end node, this downstream will be sent and shows:
232	232	lora_pkt_fwd[4286]: INFO: tx_start_delay=1497 (1497.000000) - (1497, bw_delay=0.000000, notch_delay=0.000000)
233	233	lora_pkt_fwd[4286]: [LGWSEND]lgw_send done: count_us=3537314420, freq=923300000, size=17
	235	+)))
234	234
235		-
	237	+(% class="box" %)
	238	+(((
236	236	**3)** and the end node will got:
237	237	[5764825]~*~*~*~** UpLinkCounter= 98 ~*~*~*~**
238	238	[5764827]TX on freq 905300000 Hz at DR 0
...	...	@@ -245,8 +245,10 @@
245	245	Rssi= -41
246	246	Receive data
247	247	(% style="color:#037691" %)**2:12345678**  (%%) ~-~-> Hex
	251	+)))
248	248
249		-
	253	+(% class="box" %)
	254	+(((
250	250	**4) **If we use the command "echo 2602111D,time,txt,12345678 > /var/iot/push/test" for downstream, the end node will got:
251	251	[5955877]~*~*~*~** UpLinkCounter= 102 ~*~*~*~**
252	252	[5955879]TX on freq 904100000 Hz at DR 0
...	...	@@ -305,7 +305,6 @@
305	305	#  whether the Device 2 has been changed.//
306	306	)))
307	307
308		-
309	309	**~1. Input keys**
310	310
311	311	[[image:image-20220527162450-3.png]]
...	...	@@ -315,7 +315,6 @@
315	315
316	316	**2. Make sure the LPS8 and LT use the same frequency bands, choose EU868 in this test.**
317	317
318		-
319	319	**3. Choose Built-in server**
320	320
321	321	[[image:image-20220527162518-4.png]]