Summary

• Page properties (1 modified, 0 added, 0 removed)
• Attachments (0 modified, 2 added, 0 removed)
  • image-20220722115133-1.png
  • image-20220722115213-2.png

Details

Page properties

Content

...	...	@@ -138,19 +138,23 @@
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
	141	+**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.
	143	+**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
	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
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:
	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:
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. Some notice:
	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.
153	153
	154	+
	155	+(% style="color:red" %)
	156	+**Some notice:**
	157	+
154	154	* RSSI and SNR are added when gateway receive the packet, so there is always this field.
155	155	* If you rename the file, please make it executable.
156	156	* See this link for lua.bit module: [[http:~~/~~/luaforge.net/projects/bit/>>url:http://luaforge.net/projects/bit/]]
...	...	@@ -159,7 +159,6 @@
159	159	* User can use other language ,not limited to Lua, just make sure the return is what you want to send.
160	160
161	161
162		-
163	163	== 2.2 Downstream ==
164	164
165	165
...	...	@@ -192,7 +192,6 @@
192	192	* **rxwindow:** transmit on Rx1Window or Rx2Window.
193	193
194	194
195		-
196	196	(% style="color:blue" %)**Completely exmaple:**
197	197
198	198	* **Old version:** echo 018193F4,imme,hex,0101 > /var/iot/push/test
...	...	@@ -219,25 +219,19 @@
219	219	(((
220	220	we can use echo command to create files in LG308 for downstream.
221	221	root@dragino-1d25dc:~~# echo 2602111D,time,hex,12345678 > /var/iot/push/test
222		-)))
223	223
224		-(% class="box" %)
225		-(((
	225	+
226	226	**1)** From logread -f of gateway, we can see it has been added as pedning.
227	227	lora_pkt_fwd[4286]: INFO~~ [DNLK]Looking file : test
228	228	lora_pkt_fwd[4286]: INFO~~ [DNLK]devaddr:2602111D, txmode:time, pdfm:hex, size:4, payload1:4Vx,payload_hex:77C1BB90
229	229	lora_pkt_fwd[4286]: INFO~~ [DNLK] DNLINK PENDING!(1 elems).
230		-)))
231	231
232		-(% class="box" %)
233		-(((
	231	+
234	234	**2)** When there is an upstrea from end node, this downstream will be sent and shows:
235	235	lora_pkt_fwd[4286]: INFO: tx_start_delay=1497 (1497.000000) - (1497, bw_delay=0.000000, notch_delay=0.000000)
236	236	lora_pkt_fwd[4286]: [LGWSEND]lgw_send done: count_us=3537314420, freq=923300000, size=17
237		-)))
238	238
239		-(% class="box" %)
240		-(((
	236	+
241	241	**3)** and the end node will got:
242	242	[5764825]~*~*~*~** UpLinkCounter= 98 ~*~*~*~**
243	243	[5764827]TX on freq 905300000 Hz at DR 0
...	...	@@ -250,10 +250,8 @@
250	250	Rssi= -41
251	251	Receive data
252	252	(% style="color:#037691" %)**2:12345678**  (%%) ~-~-> Hex
253		-)))
254	254
255		-(% class="box" %)
256		-(((
	250	+
257	257	**4) **If we use the command "echo 2602111D,time,txt,12345678 > /var/iot/push/test" for downstream, the end node will got:
258	258	[5955877]~*~*~*~** UpLinkCounter= 102 ~*~*~*~**
259	259	[5955879]TX on freq 904100000 Hz at DR 0
...	...	@@ -312,6 +312,7 @@
312	312	#  whether the Device 2 has been changed.//
313	313	)))
314	314
	309	+
315	315	**~1. Input keys**
316	316
317	317	[[image:image-20220527162450-3.png]]
...	...	@@ -321,6 +321,7 @@
321	321
322	322	**2. Make sure the LPS8 and LT use the same frequency bands, choose EU868 in this test.**
323	323
	319	+
324	324	**3. Choose Built-in server**
325	325
326	326	[[image:image-20220527162518-4.png]]
...	...	@@ -330,7 +330,7 @@
330	330
331	331	**4. Run the script.**
332	332
333		-[[image:image-20220527162552-5.png]]
	329	+[[image:image-20220722115213-2.png]]
334	334
335	335	Run the script
336	336
...	...	@@ -337,7 +337,7 @@
337	337
338	338	**5. Output:**
339	339
340		-[[image:image-20220527162619-6.png]]
	336	+[[image:image-20220722115133-1.png]]
341	341
342	342	Output from LPS8
343	343

image-20220722115133-1.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+35.1 KB

Content

image-20220722115213-2.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+27.7 KB

Content