Eddystone problems

[Roei]

Hi,

I'm trying to implement Eddystone beacons in my application.

My application is already contains advertisement feature with whitelist.

When I'm trying to use Eddystone example, a lot of thing doesn't work, because a lot of initialization and configuration function from the example are already used in my application, and when trying to run them again, there are a lot of failures.

How can I implement the most basic Eddystone, in addition to my advertisement feature in my application? What is necessary?

Thanks!

[Einar Thorsrud]

Hi,

A full Eddystone beacon is quite complex, and the Eddystone example in the SDK is intended to be used as-is (more like a reference design). Referring to this post I wonder if you need a full Eddystone beacon? Or do would you be happy with a simple beacon similar to iBeacon?

If by the most basic Eddystone you mean just a fixed advertisement packet (just a iBeacon, but with a different format), then you could achieve this by regularly (using an app_timer for instance) reconfiguring the advertiser, switching from connectable advertising with whitelisting etc. to the beacon advertising, and then back again. Doing to in quick succession would make it seem like you are concurrently advertising both types of packets.

[Roei]

Hi, thanks you for your quick response!

I need a simple fixed advertisement packet of Eddystone, which will be recognizable by NRF beacon for Eddystone, for example.

As I already have an infrastructure for advertisement with and without whitelist, I need to advertise in beacon format for a few seconds before my application starts the regular advertisment.

I guess it's just about configuration. But I need some help with that - how can I configure an advertisement of Eddystone, and after that - configure it back to the previous?

Thanks!

[Einar Thorsrud]

Hi,

I see. You can refer to this post, which describes a way to implement this. The post is slightly old, but still valid today.

[Roei]

Hi,

I've noticed that this post is about iBeacon, while I need an Eddystone format. Is that possible?

[Einar Thorsrud]

Whether it is iBeacon or Eddystone is not really relevant if all you want is a simple non-connectable fixed content beacon packet, it is just that the advertising data would be different. Everything in the post I linked to is equally valid in both cases.

[Roei]

OK,

So everything depends on advertising parameters?

I didn't see any special advertising parameters in Eddystone example.

[Einar Thorsrud]

It just depends on the content of the advertisement packet, which you generate yourself. I suggest you refer to the iBeacon example to see how you can hand-write an advertisement packet payload, and then refer to the Eddystone specification. For instance here for a Eddystone-UID frame, if that is what you need(?).