Enabling and disabling Eddystone beacon slots

[Slay]

With the Eddystone beacon example from the nRF5 SDK v.16.0 I managed to change the beacon data to be sent using es_slot_on_write. This only changes though if this data is written to slot 0 (slot_no parameter of es_slot_on_write). The earlier filled default data is replaced by the new one. I would expect however that if we would write (different) data to some other slot  this slot should also be enabled and be sent by the beacon. When following the code for es_slot_on_write, the slot appears to be enabled in configure_slot, but on the receiving side only the data from slot0 is received every period. Shouldn't the beacon be sending both slots then every interval period (or does it alternate between the slots, still sending 1 frame each period)?

So in short: what do we need to do in extra to make the beacon send data from other slots then slot_0 only? And what would be the way to disable a slot (temporarily)?

[Amanda Hsieh]

Hi, 

This post might help. 

-Amanda H.

[Slay]

Hi Amanda,

Thanks for your reply. I earlier did see this post when looking for answers. Here it is discussed however that the SDK code should be changed for this. I would expect this to be possible without code changes and calling standard library functions. Especially if according to the code the slot is enabled. So maybe SDK-code changes are required, but this would definitely surprise me.

Ruud