Advertise connectable Eddystone slots

RE: Advertise connectable Eddystone slots

run_ar — Fri, 09 Jul 2021 14:36:28 GMT

Hi,

Where does it assert? Can I guess there is a check that the interval should not be to big? Most likely a limitation with eddystone, but as mentioned Eddystone is no longer supported.

RE: Advertise connectable Eddystone slots

Susan_cfx — Thu, 08 Jul 2021 11:38:50 GMT

Hi run,

I tried the sdk 17.0.2, and try to modify other parameters, and then it can advertise connectable eddystone.

and I go back to sdk 17.0.0, do the same modification, it can also advertise connectable eddystone.

if we continute to use sdk17.0.0, do it has any risk ? Actually, We have produced a batch of beacons with the sdk17.0.0.

In addtion, what is the range of MAX_CONN_INTERVAL, if I set to 2000ms, the beacon will raise a fatal error.

Do you have the suggest value for MAX_CONN_INTERVAL for this use case?

Looking forward to your reply, thank you very much.

Best wishes,

Susan

RE: Advertise connectable Eddystone slots

run_ar — Tue, 06 Jul 2021 09:35:04 GMT

Hi,

Eddystone was discontinued by Google in 2018. So not sure how well it will work anymore. Regardless, could you try using the latest SDK revision, 17.0.2?

RE: Advertise connectable Eddystone slots

Susan_cfx — Mon, 05 Jul 2021 10:11:45 GMT

Hi,

I tried to connect the beacon, clicked the connect button in adroid app nRF Connect, the beacon raise an error, as follows,

app: ERROR 18 [NRF_ERROR_CONN_COUNT] at E:\nRF5_SDK_17.0.0_9d13099\components\ble\ble_services\eddystone\es_adv.c:103

it seems sd_ble_gap_adv_start() finction returens this error, after searching in DevZone, this problem still cannot be solved. Can you help analyze the reason? Thank you very much.

Best wishes,

Susan