cancel
Showing results for 
Search instead for 
Did you mean: 

NVM saving persistent data

ISLTG
Associate III

Hello,

I copied the logic from the NVM Zigbee examples. 

I notice that the end devices almost periodically calls the persistent data callback to save when I am sending sequential data sequences.

However, this unfortunately causes the end device to sometimes miss the reception of Zigbee data, and in my case, does not call ZbZcl_custom_ls_ServerSendCommandRsp.

The devices end up LOSING connection shortly after saving to persistent data.

Is this intended, and are there any solutions?

Thanks,

11 REPLIES 11
Ouadi
ST Employee

Hello @ISLTG,

I recommend to take a look on zigbee specification to be familiar with Broadcast communication mode, here are some hints :

  • Broadcast Delivery Time:The broadcast delivery time is the required time for a broadcast transaction to be delivered to every device on the network, it can be configured using the ZbNwkSet API with the parameter ZB_NWK_NIB_ID_NetworkBroadcastDeliveryTime.
  • Minimum Interval: The minimum value for this parameter is 3 seconds. This means that broadcast messages cannot be sent at intervals shorter than 3 seconds.

Group addressing using ZB_APSDE_ADDRMODE_GROUP allow to send a message to a group of devices, while the broadcast mode in my example allow sending message to all devices on the network.

Best regards,

Ouadi

 

ISLTG
Associate III

Thanks for all the help @Ouadi

3 seconds is unusable for my application.

Group addressing at 300ms seems to work well enough though...

Hopefully this isn't against recommended practice?

Thanks,