• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 50 subscribers
  • Views 287 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

iOS7 / BLE1.3 Connection Parameter Bug

Kevin Lockwood
Expert 1035 points

Upon connection my firmware detects a GAPROLE_CONNECTED in a callback and sends a GAPRole_SendUpdateParam.  This is to change from the default iOS 30msec connection parameters to an intermediate 157.5msec connection interval.   

 I've noticed during stress testing of my firmware that when connecting and reconnecting quickly with an iPhone,  the GAPRole_SendUpdateParam command seems to occasionally get ignored by the iPhone (10% of the time).  This causes the firmware to stay in the iOS 30msec connection interval which consumes alot of power!  I have not read anything about when Connection Parameter updates are best sent.  Am I sending the GAPRole_SendUpdateParam request too quickly after a connection?  The iPhone does not send any rejection, L2CAP_PARAM_UPDATE_RSP only ever reports SUCCESS in peripheral.c.   I'm am very confused where this problem persists iPhone or F/W.

 

  • 0
    Expert 1035 points

    I had thought I'd I solved the issue by upgrading peripheral.c and peripheral.h to the version in BLE 1.4.  I had to make a few modifications to make it work in the BLE 1.3 Stack.  But it seems the problem still exits.  I would still love it if someone from Ti could comment on this issue in the BLE 1.3 stack,  and/or someone who went thru a similar experience and how you solved it.  Thanks guys

  • 0 in reply to Kevin Lockwood
    Expert 1035 points

    Has anyone seen this issue where a Central ignores a Connection Parameter Update Request?  I know my parameters are acceptable to the Central because under most conditions the link can flawlessly transition between my pre-defined Connection Parameter states.  I only notice this when multiple connection/reconnections take place fairly quickly.  It is particularly more noticeable with an iPhone5.   Are there any steps I can take during rapid connect/reconnect conditions to make sure that requests do not get lost?  As it stands when this error occurs, my iPhone 5 will stay in its default connection parameter of 30msec which will kill batteries fast.  Hopefully someone from Ti can comment.  Thanks guys.

    p.s. I know this isn't a hardware issue as I am testing on the KeyFob dev board. :)