Leveraging the eddystone beacon slots API for other beacon formats

[PapaG]

Hi,

I am trying to implement beacon-ing into my existing firmware of different beacon types. I have successfully generated an iBeacon and Eddystone-UID beacon using ble_advertising_advdata_update and packing the data myself. This was just a prototype and needs to scale up to support all eddystone packet types and ibeacon.

I had a look at ble/ble_services/eddystone/nrf_ble_es.* see that it uses a timer based api to trigger and advertise different eddystone beacons at different intervals. This is almost exactly what I need... except that it's not a generic beacon structure.

Is there a way I could modify the ble eddystone API to accept packets of different beacon types? Currently my plan is to pack the data myself and broadcast on my own timer based functionality, but it would be great if I could leverage the existing system.

[PapaG]

I should also mention I want to do

1. Name for discoverability
2. iBeacon
3. Eddystone x beacon
4. Eddystone y beacon
5. Eddystone z beacon

[Hung Bui]

Hi PapaG,

I don't think the Eddy stone Slot library is designed to add customized beacon type in. But you are free to modify the library to add you your own data format. We haven't tried that though.