• State Not Answered
  • Replies 10 replies
  • Subscribers 63 subscribers
  • Views 4124 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 123818
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Connection problem

Ken

Currently using nordic52832 to develop products that use batteries.

We found that the problem is that when the BLE module is connected successfully, it takes 200ms to send the message.

How can I improve this problem?

We need a very short grip time and turn off the power.

Parents
  • 0

    ...(2/2) if your problem is really between BLE_GAP_EVT_CONNECTED event and some subsequent application data exchange over GATT then you probably have too long connection interval and/or do unnecessary long GATT Service Discovery from GATT Client side (I suppose that runs on GAP Central side). Doing simple BLE radio trace would tell you all the details and you would have clarity in few minutes. Just for your information you don't need to settle down with ~250ms for GATT Service discovery, if you use short interval (which is recommended if you want to save power and both sides support it!) and do it properly (= look only for service(es) you need instead of full enumeration) then you can easily discover your custom service + characteristic + enable notifications through CCCD in less then 70ms (with 7.5ms connection interval), maybe even less.

Reply
  • 0

    ...(2/2) if your problem is really between BLE_GAP_EVT_CONNECTED event and some subsequent application data exchange over GATT then you probably have too long connection interval and/or do unnecessary long GATT Service Discovery from GATT Client side (I suppose that runs on GAP Central side). Doing simple BLE radio trace would tell you all the details and you would have clarity in few minutes. Just for your information you don't need to settle down with ~250ms for GATT Service discovery, if you use short interval (which is recommended if you want to save power and both sides support it!) and do it properly (= look only for service(es) you need instead of full enumeration) then you can easily discover your custom service + characteristic + enable notifications through CCCD in less then 70ms (with 7.5ms connection interval), maybe even less.

Children
No Data
Related