Tool/software:
Apologies for the duplicate or follow-up question. I realized I need to clarify some additional observations regarding the guiMonitor TLV outputs.
Observations:
-
When sending:
→ TLV types 1, 7, 6, 9 work correctly.
-
When enabling TLV type 2 (Range Profile) or TLV type 3 (Noise Profile):
→ Even if I do not parse TLV 2/3, the subsequent TLV types appear corrupted. (e.g. 65536, 327680, 566537, and sometimes even 0.)
→ Offset is correctly updated using the TLV header length:
-
When enabling TLV types 4, 5, or 8 (heatmap types):
→ No TLV data or chunks are received at all, parsing never occurs.
Questions:
-
Why do TLV 2/3 corrupt subsequent TLVs even when offsets are handled correctly?
-
Why do heatmap TLVs (4, 5, 8) prevent any TLV data from being received?
-
Are there any known configuration constraints when enabling multiple TLV types simultaneously that could affect TLV output integrity?
Thank you for your guidance.
