Summary

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

Details

Page properties

Content

...	...	@@ -22,6 +22,7 @@
22	22
23	23
24	24
	25	+
25	25	= 2. How it works =
26	26
27	27
...	...	@@ -78,8 +78,6 @@
78	78	* **SNR**: 3030 3030 3030 3546 = 0x0000 005F = 95, need to divide 10 so SNR is 9.5
79	79	* **Payload**: 0xcc0c 0b63 0266 017f ff7f ff00
80	80
81		-
82		-
83	83	(% class="box" %)
84	84	(((
85	85	(% 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:
...	...	@@ -139,23 +139,19 @@
139	139	=== 2.2.2 How to Decode My End Node ===
140	140
141	141
142		-**1.** Configure the ABP keys for your end node in the gateway. enable ABP decode in Web UI
	141	+1/ Configure the ABP keys for your end node in the gateway. enable ABP decode in Web UI
143	143
144		-**2. **Don't choose MQTT service, use LoRaWAN.
	143	+2/ Don't choose MQTT service, use LoRaWAN.
145	145
146		-**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
	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
147	147
148		-**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:
	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:
149	149
150	150	{{{/etc/lora/decoder/Dragino_LHT65 END_NODE_DEV_ADDR
151	151	}}}
152	152
153		-**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.
	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. Some notice:
154	154
155		-
156		-(% style="color:red" %)
157		-**Some notice:**
158		-
159	159	* RSSI and SNR are added when gateway receive the packet, so there is always this field.
160	160	* If you rename the file, please make it executable.
161	161	* See this link for lua.bit module: [[http:~~/~~/luaforge.net/projects/bit/>>url:http://luaforge.net/projects/bit/]]
...	...	@@ -165,7 +165,6 @@
165	165
166	166
167	167
168		-
169	169	== 2.2 Downstream ==
170	170
171	171
...	...	@@ -199,7 +199,6 @@
199	199
200	200
201	201
202		-
203	203	(% style="color:blue" %)**Completely exmaple:**
204	204
205	205	* **Old version:** echo 018193F4,imme,hex,0101 > /var/iot/push/test
...	...	@@ -206,8 +206,6 @@
206	206	* **New version:** echo 018193F4,imme,hex,0101,20,1,SF12,923300000,2 > /var/iot/push/test
207	207
208	208
209		-
210		-
211	211	(% style="color:#037691" %)**Downstream Frequency**
212	212
213	213	The LG308 will use the RX2 window info to send the downstream payload, use the default LoRaWAN settings, as below:
...	...	@@ -222,8 +222,6 @@
222	222	* RU864: 869.1Mhz, SF12 BW125
223	223
224	224
225		-
226		-
227	227	(% style="color:#037691" %)**Examples:**
228	228
229	229	(% class="box" %)
...	...	@@ -230,19 +230,25 @@
230	230	(((
231	231	we can use echo command to create files in LG308 for downstream.
232	232	root@dragino-1d25dc:~~# echo 2602111D,time,hex,12345678 > /var/iot/push/test
	222	+)))
233	233
234		-
	224	+(% class="box" %)
	225	+(((
235	235	**1)** From logread -f of gateway, we can see it has been added as pedning.
236	236	lora_pkt_fwd[4286]: INFO~~ [DNLK]Looking file : test
237	237	lora_pkt_fwd[4286]: INFO~~ [DNLK]devaddr:2602111D, txmode:time, pdfm:hex, size:4, payload1:4Vx,payload_hex:77C1BB90
238	238	lora_pkt_fwd[4286]: INFO~~ [DNLK] DNLINK PENDING!(1 elems).
	230	+)))
239	239
240		-
	232	+(% class="box" %)
	233	+(((
241	241	**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
	237	+)))
244	244
245		-
	239	+(% class="box" %)
	240	+(((
246	246	**3)** and the end node will got:
247	247	[5764825]~*~*~*~** UpLinkCounter= 98 ~*~*~*~**
248	248	[5764827]TX on freq 905300000 Hz at DR 0
...	...	@@ -255,8 +255,10 @@
255	255	Rssi= -41
256	256	Receive data
257	257	(% style="color:#037691" %)**2:12345678**  (%%) ~-~-> Hex
	253	+)))
258	258
259		-
	255	+(% class="box" %)
	256	+(((
260	260	**4) **If we use the command "echo 2602111D,time,txt,12345678 > /var/iot/push/test" for downstream, the end node will got:
261	261	[5955877]~*~*~*~** UpLinkCounter= 102 ~*~*~*~**
262	262	[5955879]TX on freq 904100000 Hz at DR 0
...	...	@@ -315,7 +315,6 @@
315	315	#  whether the Device 2 has been changed.//
316	316	)))
317	317
318		-
319	319	**~1. Input keys**
320	320
321	321	[[image:image-20220527162450-3.png]]
...	...	@@ -325,7 +325,6 @@
325	325
326	326	**2. Make sure the LPS8 and LT use the same frequency bands, choose EU868 in this test.**
327	327
328		-
329	329	**3. Choose Built-in server**
330	330
331	331	[[image:image-20220527162518-4.png]]