This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

nRF8002 possible to broadcast indefinitely?

Hi, I am planning to use modules with nRF8002 in an indoor positioning application. The mobile devices that are to be located are continuously scanning for BLE devices and detect the module's advertisements. They do not actively connect, just scan.

My problem is that no matter how I configure the chip, it always advertises for a few minutes and then goes to sleep.

Is it possible to configure the nRF8002 so that it just advertises every 200 ms or so after power-up and never goes to sleep, even if no active connection is made?

Or do I need a more complex chip like the nRF51822?

Thank you for your help.

Parents
  • 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.

Reply
  • 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.

Children
No Data
Related