• State Not Answered
  • Locked Locked
  • Replies 9 replies
  • Subscribers 73 subscribers
  • Views 4665 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 106595
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Always connected peripheral

Oleh

What should the connection or other settings be to have a peripheral always connected? It is a bit contradictory for low energy device, however for a lost&found (link-loss and immediate alert services) this is required.

We experience in testing with different connection intervals and latency the tag is disconnected from the phone after some time.

the power_off is not used, so I expected to be always on, instead it enters the advertisement after disconnect.

Could you please suggest or hint on what we are doing wrong? Or share your experience with similar projects.

thank you, cheers Oleh

Parents
  • 0

    Do you have a sniffer available, for example nRF Sniffer? It would be helpful to see what is actually happening on the air. Could you also check the disconnect reason in the BLE_GAP_EVT_DISCONNECTED event? Use the debugger (remember to turn off optimizations, set it to Level 0) and check the value of p_ble_evt->evt.gap_evt.params.disconnected.reason; Are you using our board or a custom board? How are the noise levels in the room?

Reply
  • 0

    Do you have a sniffer available, for example nRF Sniffer? It would be helpful to see what is actually happening on the air. Could you also check the disconnect reason in the BLE_GAP_EVT_DISCONNECTED event? Use the debugger (remember to turn off optimizations, set it to Level 0) and check the value of p_ble_evt->evt.gap_evt.params.disconnected.reason; Are you using our board or a custom board? How are the noise levels in the room?

Children
No Data
Related
Terms of service