Summary

• Page properties (2 modified, 0 added, 0 removed)
• Attachments (0 modified, 0 added, 3 removed)
  • image-20240123150720-1.png
  • image-20240123150943-2.png
  • image-20240123151225-3.png

Details

Page properties

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.ting
	1	+XWiki.Bei

Content

...	...	@@ -214,6 +214,7 @@
214	214
215	215	* This packet must match the DataRate of RX1(RX1DR) or RX2 (RX2DR). (% style="color:red" %)**This is the common fail point, because different lorawan server might use different RX2DR and they don't info End Node via ADR message so cause the mismatch. If this happen, user need to change the RX2DR to the right value in end node. In OTAA, LoRaWAN Server will send the RX2DR setting in Join Accept message so the end node will auto adjust. but ABP uplink doesn't support this auto change.**
216	216
	217	+
217	217	== 5.2 See Debug Info ==
218	218
219	219
...	...	@@ -329,6 +329,7 @@
329	329
330	330	* End Node traffic (from server UI) to shows end node activity in server.
331	331
	333	+
332	332	= 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
333	333
334	334
...	...	@@ -451,25 +451,26 @@
451	451	= 10. Why i got the payload only with "0x00" or "AA~=~="? =
452	452
453	453
454		-(% style="color:blue" %)**Why sensor sends 0x00?**
	456	+(% style="color:blue" %)**Why this happen:**
455	455
456		-For US915, AU915 or AS923 frequencies, the max payload lenght is 11 bytes for DR0. Some times sensor needs to send MAC command to server, because the payload is 11 bytes, The MAC command + Payload will exceed 11 bytes and LoRaWAN server will ignore the uplink. In this case, Sensor will send two uplinks together: one uplink is the payload without MAC command, another uplink is **0x00 payload + MAC Command.**  For the second uplink, in the server side, it will shows the payload is 0x00. Normally, there are several case this will happen.
	458	+For US915, AU915 or AS923 frequencies.It is possible because: .
457	457
458		-**Possible Case 1**:
	460	+When using the frequency mentioned above, the server sometimes adjusts the Data Rate (DR) of the node, because the end node has Adaptive Data Rate (ADR) Enabled.
459	459
460		-Sensor has ADR=1 enable and sensor need to reply server MAC command (ADR request) while sensor has DR=0.
	462	+1.
461	461
	464	+When the server adjusts end node data rate to 0, the maximum payload length is 11 bytes. The server sometimes sends an ADR packet to the end node, and the node will reply to the server after receiving the ADR packet, but the number of payload bytes exceeds the limit, so it will send a normal uplink packet, and following an additional 00 data packet to handle this MAC command response.
462	462
463		-**Possible Case 2:**
	466	+2.
464	464
465		-For the sensor which has Datalog Feature enable, the sensor will send TimeRequest MAC Command to sync the time. This Time Request will be sent once Sensor Join Network and Every 10 days. While they send such command with DR=0, sensor will send this command with 0x00 payload.
	468	+The server downlinks a calibration time package
	469	+This calibration time packet will exceed the byte limit, causing its payload to become 00
466	466
467		-
468	468	(% style="color:blue" %)**How to solve:**
469	469
470	470	Solution:
471	471
472		-~1. Use the decoder to filter out this 0x00 packet. (**Recommand**)
	475	+~1. Use the decoder to filter out this 0x00 packet.
473	473
474	474	2. Data rate changed from DR3 to DR5, increasing upload byte length
475	475	AT+ADR=0

image-20240123150720-1.png

Author

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

Size

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

Content

image-20240123150943-2.png

Author

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

Size

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

Content

image-20240123151225-3.png

Author

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

Size

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

Content