nRF8002 possible to broadcast indefinitely?

RE: nRF8002 possible to broadcast indefinitely?

Ole Morten — Mon, 19 Aug 2013 08:34:51 GMT

Please do, and let us know if you have any further problems or questions.

For this question, I'd be happy if you could accept an answer, so that the discussion shows up as solved. :-)

RE: nRF8002 possible to broadcast indefinitely?

Matthias Krebs — Mon, 19 Aug 2013 08:33:02 GMT

Ok thanks for the information. I guess I will have to give the other chipsets a try.

RE: nRF8002 possible to broadcast indefinitely?

Ole Morten — Mon, 19 Aug 2013 07:30:47 GMT

You are right that there is a difference between the advertisement flags used on the nRF8002 when bonded and not. When not bonded, the nRF8002 will advertise with the "Limited discoverable" flag, while when bonded, this will not be there.

It could very well be that the Samsung APIs uses this flag to filter. Unfortunately, if you need the tags to be discoverable from this platform, I'm afraid there isn't much you can do about it, except for using a different tag solution. With both the nRF8001 and the nRF51822, you have full control over the flags used when advertising, so that this can be avoided.

RE: nRF8002 possible to broadcast indefinitely?

Matthias Krebs — Mon, 19 Aug 2013 05:05:37 GMT

I tried the suggested bonding trick. I took the master emulator dongle that came with the DK and used the Master Control Panel 3.4.0 to connect to the nRF8002 tag. I was successful in creating a bond and got the tag into "Connecting" state after disconnecting the master dongle.

However, I do not receive any advertisements while the tag is in connecting state. I use a Samsung Galaxy S3 with the Samsung BLE SDK to scan for BLE devices. I receive advertisements when the tag is in "Bonding" state after startup but not when it's in "Connecting" state.

I use the default configuration from nRFgoStudio, and I am pretty sure the tag goes to connecting state because the LED blinks every 4th second.

Is there a difference between advertisements in Bonding state and in Connecting state, or why is the tag not sending advertisements?

RE: nRF8002 possible to broadcast indefinitely?

Matthias Krebs — Fri, 16 Aug 2013 11:38:16 GMT

Hi, Thank you for the quick reply!

Your suggestion of using a bonding could be an acceptable workaround, because I will use the tags in an experimental setup for some time. I think I will just try the USB master dongle that came with the devkit and see how it works.

RE: nRF8002 possible to broadcast indefinitely?

Ole Morten — Fri, 16 Aug 2013 11:21:14 GMT

In the state called Connecting in the nRFgo Studio's state diagram, the nRF8002 will advertise infinitely. However, to get to this state, you must have a bond with a Central device. In principle, you could do such bonding in the production of your dongle, but if so, you need to take into account that all bond information are lost when the nRF8002 loses power. This means that you'd either have to make sure that never happens, or that the user are able to rebond it with something (preferably something that will not normally be in the location to avoid an actual connection getting established).

It should also be noted that the nRF8002 uses slightly different advertising flags when bonded and not. When not bonded, it will set the "Limited discoverable" flag, but when bonded, it will not use this flag. Some platforms may use this flag to decide whether or not a received advertisement should be propagated to the app or not.

If you instead use an nRF51822 or an nRF8001 with an application processor, this is however not a problem, and you can make a solution that just works, regardless of bonding.

Edit: Clarify the flag usage of the nRF8002.