X-CTU Bug - Frame Generator RF Byte count issue

XBee & XBee Gateway
, , ,
1

Hi,

In debugging my application I created an API TX frame using the frame generator. However I noticed an inconsistency regarding the RF Data byte count.

The RF byte count doesn’t take 0x00 into account when calculating the number of bytes. So in a stream of 99 00 99 00 99 the value should equal 5 bytes, although XCTU only reports 3. However the total byte count for the frame does reflect the correct number of bytes in the frame to be sent. I’m using XCTU V6.3

Does anyone know why this might be? Is it a bug or is there a valid reason for this?

2

Can you provide the entire frame you are issuing to see this issue on?

3

The complete frame is:
7E 00 5D 10 01 00 13 A2 00 40 DD D7 28 37 2D 00 00 AC ED 00 05 73 72 00 0A 4D 65 61 73 75 72 61 6E 74 73 89 1F 5C 87 5F 61 F1 07 02 00 02 4C 00 07 63 75 72 72 65 6E 74 74 00 12 4C 6A 61 76 61 2F 6C 61 6E 67 2F 53 74 72 69 6E 67 3B 4C 00 07 76 6F 6C 74 61 67 65 71 00 7E 00 01 78 70 70 70 49

The payload value is:
AC ED 00 05 73 72 00 0A 4D 65 61 73 75 72 61 6E 74 73 89 1F 5C 87 5F 61 F1 07 02 00 02 4C 00 07 63 75 72 72 65 6E 74 74 00 12 4C 6A 61 76 61 2F 6C 61 6E 67 2F 53 74 72 69 6E 67 3B 4C 00 07 76 6F 6C 74 61 67 65 71 00 7E 00 01 78 70 70 70

XCTU only states that 72 bytes are present in the payload - modifying any 0x00 value increases the payload value

4

I would considered that a bug in the API frame Generator and suggest you use the Chat function to provide this feed back.