Hi,
I have a question that I believe is an iOS App issue, but I thought I'd ask this forum just to confirm... I have a peripheral BLE device running on a CC2650. After a link is established with a central BLE device, the peripheral would wait 5 minutes, then it would request for the following connection parameters update:
Supervision Timeout = 6 seconds
Max Connection Interval = 900 msec
Min connection Interval = 800 msec
Slave Latency = 1
These parameters satisfies the Apple Bluetooth Design Guidelines, and the peripheral is able to establish a link and stay connected to the BTool, and also to two different iOS BLE Apps: BLE Utility and LightBlue. I even ran it overnight with the iOS BLE Utility App and I see no disconnect whatsoever. However, the iOS team that I'm working with provided me with an iOS BLE App that they wrote, but with this App, the link would stay up for 5 minutes. After issuing the connection parameters, the iOS would then notify the App of a supervision timeout at random times; sometimes it'll happen 30 seconds after the connection parameter update, sometimes 2 minutes. I sniffed out the packets, and I always see that the peripheral is consistently sending empty packets on every effective connection interval.
This seems to me that something is not quite right with the iOS App, but of course my iOS team keeps telling me that my CC2650 is buggy... I'm at a loss as to how I can debug this from the peripheral side. Any suggestions or insights would be greatly appreciated.
Thanks,
Danny
