January 2013 - Bluetooth-dev

CoreBluetooth cancelPeripheralConnection in background
by Long LI 29 Jan '13

29 Jan '13

Hi In my app when it enter background, after 10 minutes, fire cancelPeripheralConnection to disconnect in background. but, my BLE accessory can't got the disconnect event until my app go back Foreground. WHY? any suggest. Best Regards Long LI _______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev(a)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(a)lists.apple.com

1 0

Re: About CoreBluetooth disconnect behavior
by Etan Kissling 29 Jan '13

29 Jan '13

Khaos, I can confirm disconnect delays of about 1-3s under the final iOS 6.1 version. Seems that it is intended and we can remove "remote disconnect" workarounds. Etan On 29.12.2012, at 14:25, Khaos Tian <khaos.tian(a)gmail.com> wrote: > Hi, > > On iOS 6.1 beta 4 I noticed that after I called > cancelPeripheralConnection: the connection between iDevice and > peripheral closed in about 1~2s. > > Is that Apple finally decided to remove the 30s disconnect delay in iOS 6.1? > > Best Wishes, > Khaos Tian > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Bluetooth-dev mailing list (Bluetooth-dev(a)lists.apple.com) > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/bluetooth-dev/kissling%40oberon.ch > > This email sent to kissling(a)oberon.ch _______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev(a)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(a)lists.apple.com

1 0

Re: Use 2 central Manager
by Bob Frankel 28 Jan '13

28 Jan '13

Samuel, as you noticed, CBPeripherals cannot be shared between CBCentralManager. Therefore, an approach with multiple CBCentralManager cannot work at all in the case where you want to connect to a new unknown peripheral, as for such peripherals, the UUID is null. You cannot use this UUID for comparison purposes like you proposed in your code comment. For the CBPeripheralManager, the documentation actually tells that only one instance should be used at any time: /*! * @class CBPeripheralManager * * @discussion Entry point to the peripheral role. Commands should only be issued when its state is <code>CBPeripheralManagerStatePoweredOn</code>. * The use of more than one <code>CBPeripheralManager</code> at a time is not supported and may result in undefined behavior. * */ NS_CLASS_AVAILABLE(NA, 6_0) CB_EXTERN_CLASS @interface CBPeripheralManager : NSObject { @package id<CBPeripheralManagerDelegate> _delegate; CBPeripheralManagerState _state; BOOL _advertising; } Conclusion: - Multiple CBCentralManager instances cannot work in all cases. You also noticed that even standard cases don't work well. - Multiple CBPeripheralManager instances are documented to fail. I assume that you want to plug multiple delegates in a single CBCentralManager instance (to split logic for connecting and discovering). - One solution is to send your CBCentralManager instance between your viewControllers, and change the delegate on each view transition. - Another solution is to use NSNotificationCenter to send local broadcasts of the CoreBluetooth events. Just plug a new object in as the CBCentralManager's delegate that handles the forwarding, and listen to these events in your observing viewControllers. Etan On 28.01.2013, at 10:51, Alpwise iOS Dev mailto:alpwiseiosdev@alpwise.com wrote: Hi, thanks for the reply. I fixed my code and used only one CM. As Apple permit to create multiple instance of CM, i was thinking that was possible. But like you say it's a disaster. Cheers, Samuel Le 25 janv. 2013 à 16:09, András Kövi a écrit : When I tried that, the results were disastrous. Start a request on one manager and receive the callback on the other... It's possible that I messed up something but not very likely. However, the things you describe are easily handleable by one CM. Why would you use two? I suggest you try to optimize your use case for one CM. Note: The CBPeripheral is an internal object and it is connected to the CentralManager. You shouldn't suppose anything on the lifecycle of the CBPeriperal or its values. However, you start a connection to it, then you must keep the reference as long as the connection is alive, otherwise you'll get a warning that the peripheral is being deallocated while it is connected or the CM is trying to connect to it. This is an annoying behavior but we have to live with it. Cheers, Andras 2013/1/25 Alpwise iOS Dev mailto:alpwiseiosdev@alpwise.com Hi, I would use 2 central manager, one to manage the discovery and another to manage the connection. So i need to pass a CBPeripheral discover from a CBCentralManager to another CBCentralManager. Has someone already try that? Here is my example. =============================== -(void)centralManager:(CBCentralManager *)central didDiscoverPeripheral:(CBPeripheral *)peripheral advertisementData:(NSDictionary *)advertisementData RSSI:(NSNumber *)RSSI { // central != _centralManager _peripheralDiscovered = peripheral; [_centralManager connectPeripheral:peripheral options:nil]; } -(void)centralManager:(CBCentralManager *)central didConnectPeripheral:(CBPeripheral *)peripheral { // central == _centralManager // peripheral != _peripheralDiscovered but [peripheral UUID] == [_peripheralDiscovered UUID] } =============================== It seems that a new CBPeripheral is allocated when the central change. It is a normal behavior? Thanks, Samuel. _______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (mailto:Bluetooth-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/bluetooth-dev/allprog%40gmail.com This email sent to mailto:allprog@gmail.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (mailto:Bluetooth-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/bluetooth-dev/kissling%40oberon.ch This email sent to mailto:kissling@oberon.ch _______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (mailto:Bluetooth-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/bluetooth-dev/bfrankel%40emmoco.com This email sent to mailto:bfrankel@emmoco.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev(a)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(a)lists.apple.com

1 0

Re: Use 2 central Manager
by Etan Kissling 28 Jan '13

28 Jan '13

Samuel, as you noticed, CBPeripherals cannot be shared between CBCentralManager. Therefore, an approach with multiple CBCentralManager cannot work at all in the case where you want to connect to a new unknown peripheral, as for such peripherals, the UUID is null. You cannot use this UUID for comparison purposes like you proposed in your code comment. For the CBPeripheralManager, the documentation actually tells that only one instance should be used at any time: /*! * @class CBPeripheralManager * * @discussion Entry point to the peripheral role. Commands should only be issued when its state is <code>CBPeripheralManagerStatePoweredOn</code>. * The use of more than one <code>CBPeripheralManager</code> at a time is not supported and may result in undefined behavior. * */ NS_CLASS_AVAILABLE(NA, 6_0) CB_EXTERN_CLASS @interface CBPeripheralManager : NSObject { @package id<CBPeripheralManagerDelegate> _delegate; CBPeripheralManagerState _state; BOOL _advertising; } Conclusion: - Multiple CBCentralManager instances cannot work in all cases. You also noticed that even standard cases don't work well. - Multiple CBPeripheralManager instances are documented to fail. I assume that you want to plug multiple delegates in a single CBCentralManager instance (to split logic for connecting and discovering). - One solution is to send your CBCentralManager instance between your viewControllers, and change the delegate on each view transition. - Another solution is to use NSNotificationCenter to send local broadcasts of the CoreBluetooth events. Just plug a new object in as the CBCentralManager's delegate that handles the forwarding, and listen to these events in your observing viewControllers. Etan On 28.01.2013, at 10:51, Alpwise iOS Dev <alpwiseiosdev(a)alpwise.com> wrote: > Hi, > > thanks for the reply. I fixed my code and used only one CM. > As Apple permit to create multiple instance of CM, i was thinking that was possible. But like you say it's a disaster. > > Cheers, > Samuel > > Le 25 janv. 2013 à 16:09, András Kövi a écrit : > >> When I tried that, the results were disastrous. Start a request on one manager and receive the callback on the other... It's possible that I messed up something but not very likely. However, the things you describe are easily handleable by one CM. Why would you use two? >> >> I suggest you try to optimize your use case for one CM. >> >> Note: The CBPeripheral is an internal object and it is connected to the CentralManager. You shouldn't suppose anything on the lifecycle of the CBPeriperal or its values. However, you start a connection to it, then you must keep the reference as long as the connection is alive, otherwise you'll get a warning that the peripheral is being deallocated while it is connected or the CM is trying to connect to it. This is an annoying behavior but we have to live with it. >> >> Cheers, >> Andras >> >> >> 2013/1/25 Alpwise iOS Dev <alpwiseiosdev(a)alpwise.com> >> Hi, >> >> I would use 2 central manager, one to manage the discovery and another to manage the connection. >> So i need to pass a CBPeripheral discover from a CBCentralManager to another CBCentralManager. >> >> Has someone already try that? >> >> Here is my example. >> =============================== >> -(void)centralManager:(CBCentralManager *)central didDiscoverPeripheral:(CBPeripheral *)peripheral advertisementData:(NSDictionary *)advertisementData RSSI:(NSNumber *)RSSI >> { >> // central != _centralManager >> _peripheralDiscovered = peripheral; >> [_centralManager connectPeripheral:peripheral options:nil]; >> } >> >> -(void)centralManager:(CBCentralManager *)central didConnectPeripheral:(CBPeripheral *)peripheral >> { >> // central == _centralManager >> // peripheral != _peripheralDiscovered but [peripheral UUID] == [_peripheralDiscovered UUID] >> } >> =============================== >> It seems that a new CBPeripheral is allocated when the central change. It is a normal behavior? >> >> Thanks, >> >> Samuel. >> >> >> >> _______________________________________________ >> Do not post admin requests to the list. They will be ignored. >> Bluetooth-dev mailing list (Bluetooth-dev(a)lists.apple.com) >> Help/Unsubscribe/Update your Subscription: >> https://lists.apple.com/mailman/options/bluetooth-dev/allprog%40gmail.com >> >> This email sent to allprog(a)gmail.com >> >> > > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Bluetooth-dev mailing list (Bluetooth-dev(a)lists.apple.com) > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/bluetooth-dev/kissling%40oberon.ch > > This email sent to kissling(a)oberon.ch _______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev(a)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(a)lists.apple.com

1 0

Re: Anybody coding the CC2540 for use with the iPhone?
by Etan Kissling 28 Jan '13

28 Jan '13

_______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev(a)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(a)lists.apple.com

1 0

Re: Use 2 central Manager
by Alpwise iOS Dev 28 Jan '13

28 Jan '13

_______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev(a)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(a)lists.apple.com

1 0

Re: Anybody coding the CC2540 for use with the iPhone?
by Darren Jones 28 Jan '13

28 Jan '13

_______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev(a)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(a)lists.apple.com

1 0

Re: Anybody coding the CC2540 for use with the iPhone?
by Jeffrey Peng 27 Jan '13

27 Jan '13

_______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev(a)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(a)lists.apple.com

1 0

Anybody coding the CC2540 for use with the iPhone?
by Darren Jones 27 Jan '13

27 Jan '13

_______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev(a)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(a)lists.apple.com

1 0

Re: Use 2 central Manager
by András Kövi 25 Jan '13

25 Jan '13

_______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev(a)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(a)lists.apple.com

1 0