[CC2562P] Does the AF_INCOMING_MSG Respect the Order of succession?

Luca Vetri

Other Parts Discussed in Thread: Z-STACK

Hi,

Let's say I read attribute Temperature, Occupied Heating Setpoint, On/Off state.

Let's assume the Thermostat fails/delays on the Temperature read, but succeed on the Heating SetPoint one.

Can it happen that I receive the Occupied Heating Setpoint before the temperature or it keeps track in a queue of the succession and will have an error code on the temperature read and after receive the occupied heating setpoint?

over 3 years ago

0 Ryan Brown1 over 3 years ago

TI__Guru**** 218277 points

Hello Luca,

Z-Stack will process incoming AF messages in the order with which they are received, which in your example is to say that the Occupied Heating Setpoint will be processed before the Temperature if it is received first. There is no internal Z-Stack queue which tracks the order of outgoing AF messages and expects their response in that certain sequence. The application can be developed so that the transaction IDs are tracked and further evaluated.

Regards,
Ryan

0 Luca Vetri over 3 years ago in reply to Ryan Brown1

Intellectual 560 points

The TransSeqNumber of AF_INCOMING_MSG is always zero. Any way to change it or assign it a value?

0 Ryan Brown1 over 3 years ago in reply to Luca Vetri

TI__Guru**** 218277 points

This is influenced by the TransId Transaction Sequence Number as part of the ZCL Header stored in the Data field of the outgoing AF_DATA_REQUEST.

Regards,
Ryan

0 Luca Vetri over 3 years ago in reply to Ryan Brown1

Intellectual 560 points

The TransID field of the AF_DATA_REQUEST? Because I did change that one but doesn't seem to change. AF_INCOMING_MSG keep having TransID = 0;

0 Ryan Brown1 over 3 years ago in reply to Luca Vetri

TI__Guru**** 218277 points

I've revised my prior response. The transSeqNum is the second byte of the ZCL frame header if manufacturer codes are not included (determined by the third bit of the frame control byte).

Regards,
Ryan

0 Luca Vetri over 3 years ago in reply to Ryan Brown1

Intellectual 560 points

I put the same value in the ZCL Frame Header and the AF_DATA_REQUEST TransID Field. Maybe this leads to some error? AF_DATA_CONFIRM has the correct Transaction Sequence Number.

0 Ryan Brown1 over 3 years ago in reply to Luca Vetri

TI__Guru**** 218277 points

Please provide terminal and/or sniffer logs of the transaction. From the ZCL 7 Specification:

When a frame is generated as the specified effect on receipt of a previous frame, then it is part of a transaction, and the Transaction Sequence Number SHALL be copied from the previously received frame into the generated frame. This includes a frame that is generated in response to request frame.

You can ask the end device manufacturers whether they support the existing ZCL specification.

Regards,
Ryan

Zigbee & Thread

Zigbee & Thread forum

[CC2562P] Does the AF_INCOMING_MSG Respect the Order of succession?