Other Parts Discussed in Thread: Z-STACK
I'm running a firmware with "#define MULTICAST_ENABLED FALSE".
To send commands to e.g. group 1 I call afDataRequestExtended with the following parameters:
This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
I'm running a firmware with "#define MULTICAST_ENABLED FALSE".
To send commands to e.g. group 1 I call afDataRequestExtended with the following parameters:
Hey Koen,
A multicast message is sent from a device to a group as a MAC broadcast message: http://dev.ti.com/tirex/content/simplelink_cc13x2_26x2_sdk_4_10_00_78/docs/zigbee/html/zigbee/z-stack-overview.html#multicast-messages
Thus it will not be received by sleepy end devices. You must set RFD_RCVC_ALWAYS_ON to TRUE for ZEDs or use ZR nodes in order to receive these messages. The other option is to send multiple unicast messages to each device.
Regards,
Ryan
Thanks for your answer, as I understand now it's not possible to change the destination to 0xFFFF.
Does that mean the bug is on the ZED side? (as it should have RFD_RCVC_ALWAYS_ON)
I would not say there exists a "bug" since ZEDs are intended to sleep (RFD_RCVC_ALWAYS_ON set to FALSE). With RFD_RCVC_ALWAYS_ON set to TRUE it consumes much more current. Broadcast messages are meant for routing devices (ZC/ZR) for which RFD_RCVC_ALWAYS_ON is already always set to TRUE.
Regards,
Ryan