CC2530: ZNP AF_incoming_MSG

Antonio del Río

Part Number: CC2530

We are updating zigbee stacks on a ZNP based coordinartor as a part of a gateqway. In 2.5.3 Stack everyting is waorking fine. Bou in 2.6.x version I noticed tha AF_INCOMING_MSG is received with "extra fileds" after the data field. Have you noticed that behaviour?

over 2 years ago

0 Antonio del Río over 2 years ago

Intellectual 395 points

Just an example (on the same circunstances)

Older stack:

length = 21, apiId = 0x44 0x81,

full data = 0xfe | 0x15 | 0x44 0x81 | 0x00 0x00 | 0x03 0x04 | 0xe3 0xaa | 0x05 | 0x04 | 0x00 | 0x8d | 0x00 | 0x39 0x45 0x02 0x00 | 0x00 | 0x04 | 0x08 0x01 0x07 0x00 | 0x66,

checksum = 0x66

Newer stack:

length = 24, apiId = 0x44 0x81

full data = 0xfe | 0x18 | 0x44 0x81 | 0x00 0x00 | 0x03 0x04 | 0x3d 0xc3 | 0x05 | 0x04 | 0x00 | 0x96 | 0x00 | 0xd5 0x66 0x0f 0x00 | 0x00 | 0x04 | 0x08 0x01 0x07 0x00 | 0x3d 0xc3 0x1d | 0xe6

checksum = 0xe6

+1 Ryan Brown1 over 2 years ago in reply to Antonio del Río

TI__Guru**** 218837 points

Hi Antonio,

The first two of three bytes are the MAC source address and the last byte is the message radius. This was reflected in updated versions of the MT API.

Regards,
Ryan

0 Antonio del Río over 2 years ago in reply to Ryan Brown1

Intellectual 395 points

Thank you so much, Ryan!

Zigbee & Thread

Zigbee & Thread forum

CC2530: ZNP AF_incoming_MSG