Hi Mark, What platform are you seeing this on? - Craig On Jul 17, 2012, at 5:42 PM, Mark Palatucci <markmp@gmail.com> wrote:
Hi,
I'm able to support multiple simultaneous slave connections using BLE - but I'm seeing a weird issue in the setup of these connections.
If I set up the connections serially, i.e. I wait until the first connection is established with a didConnectPeripheral before calling connect on the second peripheral, then everything seems to work fine. In fact, it appears I can be do service and characteristic discovery on the first peripheral while I'm waiting for the second connection to be established.
However, if I issue two peripheral connects right after another, before I receive a didConnectPeripheral on the first one, then I *never* receive a didConnectPeripheral for either connection.
So it seems like one connection must return didConnectPeripheral before calling connect on another peripheral.
I'm not sure if this is a bug or a design limitation. Has anyone else seen this issue? Any thoughts from the CoreBluetooth team would be most helpful.
Thanks -Mark
_______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/bluetooth-dev/cdooley%40apple.com
This email sent to cdooley@apple.com
_______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/bluetooth-dev/site_archiver%40lists.... This email sent to site_archiver@lists.apple.com