May 2013 - Bluetooth-dev - lists.apple.com

Re: Pairing with an iOS peripheral?
by Andras Kovi 08 May '13

08 May '13

On iOS once secure pairing happened the services and characteristics are cached. This is what many developers on this list complained about recently as it hiders testing. It's interesting that the Mac doesn't behave similarly. Though, I think your way of doing things is fine and robust. Service discovery should be pretty fast (of course depending on the number of artifacts that need to be discovered) But if you need only one service and a characteristic for identification, then it should happen fast for sure. But this statement is based only on the info you shared. You may have requirements that invalidate your approach in which case opening a ticket with Apple seems to be a viable option. Once you figure out the situ, I would highly appreciate your feedback in order to grow the community knowledge. :) Regards, Andras On 2013.05.08., at 21:40, Scott Perry <numist(a)squareup.com> wrote: > In theory (I haven't tested this, but heard it mentioned elsewhere) the UUID of the peripheral should stop rotating when it is securely paired to the central, so you can use that instead of an identifying characteristic (which could potentially leak information that can be used to track your customers). > > Service/characteristic caching will probably never be supported since they are dynamic in nature, even if you promise that yours aren't :) > > On May 8, 2013, at 10:26 AM, William Henderson <william.c.henderson(a)gmail.com> wrote: >> I'm working on a Mac app that talks to an iOS app via Bluetooth LE. The Mac app acts as the central, iOS as the peripheral. Right now, when the Mac app discovers a peripheral it: >> - connects, discovers characteristics/services >> - reads from a certain characteristic that identifies the device >> - decides based on the identity of that device whether or not to do more. >> >> This is a rather slow and error-prone way of doing things, but it is necessary because the iOS device changes peripherals periodically and (AFAIK) there is no way to tell whether a newly discovered peripheral is just a new peripheral from a known device or is coming from another device altogether. I've tried using advertisement data but CBAdvertisementDataManufacturerDataKey is apparently no longer allowed and other data is not consistently received in the peripheral discovery callback (I assume both of these are intentional to protect the user's privacy). >> >> What I am wondering is, does pairing with the device change this at all? In my testing so far it, pairing doesn't seem to gain anything at all – service/characteristic caching doesn't work on the Mac and it doesn't change the behavior of having to reconnect/discover every time the device changes peripherals. Am I missing anything? >> >> Thanks, >> William Henderson >> >> _______________________________________________ >> 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/numist%40squareup.com >> >> This email sent to numist(a)squareup.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/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/site_archiver%40lists… This email sent to site_archiver(a)lists.apple.com

1 0

RE: Connecting to a CC2540 from the Xcode simulator
by Steve Childerley 08 May '13

08 May '13

Hi Charles - I have also abandoned the simulator - the time it was taking manage its idiosyncrasies was greater than any benefits. It cost me a lot of time - first there was the problem of acquiring the correct dongle then the operational issues. I would be interested to know how those still making good use of it have over came the apparent need for continuous resetting. Steve. -----Original Message----- From: bluetooth-dev-bounces+steve=eklektek.com(a)lists.apple.com [mailto:bluetooth-dev-bounces+steve=eklektek.com@lists.apple.com] On Behalf Of Charles Y. Choi Sent: 08 May 2013 20:15 To: bluetooth-dev(a)lists.apple.com Bluetooth Subject: Re: Connecting to a CC2540 from the Xcode simulator FWIW, I've stopped trying to use the iOS simulator. The simulator does not exhibit the level of fidelity to the hardware to make me feel confident of using it for development. Hopefully in the near future this will change, but for now, I develop code on a device. -Charles On May 4, 2013, at 1:41 PM, Peter Watkins <watkipet(a)gmail.com> wrote: > I've now tested the my code and device on actual hardware and on the simulator. Here are my results: > > iOS 6 Simulator: Doesn't connect > iOS5 Simulator: Connects > iOS5 Device: Connects > iOS6 Device: Connects > > So the problem seems to be isolated to the iOS 6 simulator. Odd. > > -Peter _______________________________________________ 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/steve%40eklektek.com This email sent to steve(a)eklektek.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: Pairing with an iOS peripheral?
by Scott Perry 08 May '13

08 May '13

In theory (I haven't tested this, but heard it mentioned elsewhere) the UUID of the peripheral should stop rotating when it is securely paired to the central, so you can use that instead of an identifying characteristic (which could potentially leak information that can be used to track your customers). Service/characteristic caching will probably never be supported since they are dynamic in nature, even if you promise that yours aren't :) On May 8, 2013, at 10:26 AM, William Henderson <william.c.henderson(a)gmail.com> wrote: > I'm working on a Mac app that talks to an iOS app via Bluetooth LE. The Mac app acts as the central, iOS as the peripheral. Right now, when the Mac app discovers a peripheral it: > - connects, discovers characteristics/services > - reads from a certain characteristic that identifies the device > - decides based on the identity of that device whether or not to do more. > > This is a rather slow and error-prone way of doing things, but it is necessary because the iOS device changes peripherals periodically and (AFAIK) there is no way to tell whether a newly discovered peripheral is just a new peripheral from a known device or is coming from another device altogether. I've tried using advertisement data but CBAdvertisementDataManufacturerDataKey is apparently no longer allowed and other data is not consistently received in the peripheral discovery callback (I assume both of these are intentional to protect the user's privacy). > > What I am wondering is, does pairing with the device change this at all? In my testing so far it, pairing doesn't seem to gain anything at all – service/characteristic caching doesn't work on the Mac and it doesn't change the behavior of having to reconnect/discover every time the device changes peripherals. Am I missing anything? > > Thanks, > William Henderson > > _______________________________________________ > 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/numist%40squareup.com > > This email sent to numist(a)squareup.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: Connecting to a CC2540 from the Xcode simulator
by Rick Mann 08 May '13

08 May '13

I'm also having a lot of trouble connecting from the simulator. I've found now I have to frequently perform the "Reset Content and Settings…", which forces the extra step of re-enabling Bluetooth. It's very aggravating. On May 8, 2013, at 11:51 , Peter Watkins <watkipet(a)gmail.com> wrote: > Hi Rick, > > I do stop scanning before I attempt to connect. Are you using the iOS 6 simulator or the iOS 5 one? > > -Peter > > > On Sat, May 4, 2013 at 1:48 PM, Rick Mann <rmann(a)latencyzero.com> wrote: > Be sure to stop scanning before you attempt to connect. I found that although it worked on iPad 3, it did not work in the simulator unless I stopped scanning first. > > Actually, it did connect, but took a very, very long time. > > On May 4, 2013, at 13:41 , Peter Watkins <watkipet(a)gmail.com> wrote: > > > I've now tested the my code and device on actual hardware and on the simulator. Here are my results: > > > > iOS 6 Simulator: Doesn't connect > > iOS5 Simulator: Connects > > iOS5 Device: Connects > > iOS6 Device: Connects > > > > So the problem seems to be isolated to the iOS 6 simulator. Odd. > > > > -Peter > > > > > > On May 1, 2013, at 6:51 PM, Rick Mann <rmann(a)latencyzero.com> wrote: > > > >> I've had some oddness, but it's currently working for me. > >> > >> For yucks, try Reset Content and Settings on the simulator. Maybe BT cached something (it caches aggressively). > >> > >> -- > >> Rick > >> > >> On Apr 28, 2013, at 15:28 , Peter Watkins <watkipet(a)gmail.com> wrote: > >> > >>> I'm developing a Bluetooth Low Energy peripheral for iPhone / iPad. To start with, I'm using TI's CC2540 Development Kit: http://www.ti.com/tool/cc2540dk > >>> > >>> I've followed TN2295 for setting up my Mid 2012 MacBook Air along with a Cirago BTA8000 Bluetooth 4.0 dongle. I've made a sample iOS application that I can run in the simulator. When my application runs, I can scan and see the CC2540 dev kit, but I can't connect to it. In fact, looking at a packet dump, it appears that Core Bluetooth never even attempts to connect: > >>> http://picpaste.com/packet_dump-RObRnY97.gif > >>> (click on the image to get a higher-resolution version). > >>> > >>> > >>> I haven't tried an actual device yet (since we haven't gotten one yet). But time is running out, and I'd like to get this working in the simulator. Has anyone else run into problems connecting to devices (in or out of the simulator)? Any suggestions? I've posted my code below. Even a simple example is a bit long. > >>> > >>> Thanks, > >>> > >>> Peter > >>> > >>> > >>> > >>> =========================== MseiAppDelegate.h =========================== > >>> > >>> #import <UIKit/UIKit.h> > >>> #import <CoreBluetooth/CoreBluetooth.h> > >>> #import <CoreBluetooth/CBService.h> > >>> > >>> @interface MseiAppDelegate : UIResponder <UIApplicationDelegate, CBCentralManagerDelegate> > >>> > >>> @property (strong, nonatomic) UIWindow *window; > >>> > >>> @property (strong, nonatomic) CBCentralManager *centralManager; > >>> @property (strong, nonatomic) CBPeripheral *thePeripheral; > >>> @property (assign, nonatomic) int didDiscoverPeripheralCalls; > >>> > >>> @end > >>> > >>> =========================== MseiAppDelegate.m =========================== > >>> #import "MseiAppDelegate.h" > >>> > >>> > >>> @implementation MseiAppDelegate > >>> > >>> @synthesize didDiscoverPeripheralCalls; > >>> > >>> - (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions > >>> { > >>> self.window = [[UIWindow alloc] initWithFrame:[[UIScreen mainScreen] bounds]]; > >>> // Override point for customization after application launch. > >>> self.window.backgroundColor = [UIColor whiteColor]; > >>> [self.window makeKeyAndVisible]; > >>> > >>> self.didDiscoverPeripheralCalls = 0; > >>> self.centralManager = [[CBCentralManager alloc] initWithDelegate:self queue:nil]; > >>> > >>> return YES; > >>> } > >>> > >>> - (void)centralManager:(CBCentralManager *)central didDiscoverPeripheral:(CBPeripheral *)peripheral advertisementData:(NSDictionary *)advertisementData RSSI:(NSNumber *)RSSI { > >>> printf("didDiscoverPeripheral() call number %d\r\n", didDiscoverPeripheralCalls++); > >>> > >>> NSEnumerator *enumerator = [advertisementData keyEnumerator]; > >>> id key; > >>> while ((key = [enumerator nextObject])){ > >>> NSLog(@"%@ %@", key, [advertisementData objectForKey: key]); > >>> > >>> } > >>> > >>> if (didDiscoverPeripheralCalls < 2) { > >>> return; > >>> } > >>> > >>> _thePeripheral = peripheral; > >>> [central stopScan]; > >>> > >>> NSLog(@"Attemping to connect..."); > >>> [central connectPeripheral:_thePeripheral options:nil]; > >>> } > >>> > >>> - (void)centralManager:(CBCentralManager *)central didConnectPeripheral:(CBPeripheral *)peripheral { > >>> NSLog(@"Connected to a peripheral"); > >>> } > >>> > >>> - (void)centralManager:(CBCentralManager *)central didFailToConnectPeripheral:(CBPeripheral *)peripheral error:(NSError *)error { > >>> NSLog(@"Failed to connect to a peripheral: %@", error); > >>> } > >>> > >>> /*! > >>> * @method centralManagerStateToString: > >>> * > >>> * @param state State to print info of > >>> * > >>> * @discussion centralManagerStateToString prints information text about a given CBCentralManager state > >>> * > >>> */ > >>> - (const char *) centralManagerStateToString: (int)state{ > >>> switch(state) { > >>> case CBCentralManagerStateUnknown: > >>> return "State unknown (CBCentralManagerStateUnknown)"; > >>> case CBCentralManagerStateResetting: > >>> return "State resetting (CBCentralManagerStateUnknown)"; > >>> case CBCentralManagerStateUnsupported: > >>> return "State BLE unsupported (CBCentralManagerStateResetting)"; > >>> case CBCentralManagerStateUnauthorized: > >>> return "State unauthorized (CBCentralManagerStateUnauthorized)"; > >>> case CBCentralManagerStatePoweredOff: > >>> return "State BLE powered off (CBCentralManagerStatePoweredOff)"; > >>> case CBCentralManagerStatePoweredOn: > >>> return "State powered up and ready (CBCentralManagerStatePoweredOn)"; > >>> default: > >>> return "State unknown"; > >>> } > >>> return "Unknown state"; > >>> } > >>> > >>> - (void)centralManagerDidUpdateState:(CBCentralManager *)central { > >>> printf("Status of CoreBluetooth central manager changed %d (%s)\r\n",central.state,[self centralManagerStateToString:central.state]); > >>> if (central.state == CBCentralManagerStatePoweredOn) { > >>> NSLog(@"Started scanning for any peripherals"); > >>> [self.centralManager scanForPeripheralsWithServices:nil options:0]; // Start scanning > >>> } > >>> } > >>> > >>> _______________________________________________ > >>> 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/rmann%40latencyzero.c… > >>> > >>> This email sent to rmann(a)latencyzero.com > >> > >> > >> -- > >> Rick > >> > >> > >> > > > > > -- > Rick > > > > > _______________________________________________ > 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/rmann%40latencyzero.c… > > This email sent to rmann(a)latencyzero.com -- Rick _______________________________________________ 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: Connecting to a CC2540 from the Xcode simulator
by Charles Y. Choi 08 May '13

08 May '13

FWIW, I've stopped trying to use the iOS simulator. The simulator does not exhibit the level of fidelity to the hardware to make me feel confident of using it for development. Hopefully in the near future this will change, but for now, I develop code on a device. -Charles On May 4, 2013, at 1:41 PM, Peter Watkins <watkipet(a)gmail.com> wrote: > I've now tested the my code and device on actual hardware and on the simulator. Here are my results: > > iOS 6 Simulator: Doesn't connect > iOS5 Simulator: Connects > iOS5 Device: Connects > iOS6 Device: Connects > > So the problem seems to be isolated to the iOS 6 simulator. Odd. > > -Peter _______________________________________________ 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: Connecting to a CC2540 from the Xcode simulator
by Peter Watkins 08 May '13

08 May '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

Pairing with an iOS peripheral?
by William Henderson 08 May '13

08 May '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

Simulator still not connecting reliably
by Rick Mann 07 May '13

07 May '13

I've stopped scanning, and I thought that fixed the issue, but the sim once again can't connect to my peripheral. The iPad can always connect. Any other things I can do? -- Rick _______________________________________________ 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: Hello and sharing my CoreBluetooth code
by Charles Y. Choi 07 May '13

07 May '13

Kaelin - I'll be at WWDC (also have a ticket to altWWDC as well) this year. I'm San Francisco local, so if you're near the area it's easy to find me. Also yes, would very much appreciate your help with testing. If there's enough interest, perhaps a meetup during that week is in order. -Charles _______________________________________________ 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

Best File Transfer Profile & Certification Considerations
by Paul Romero 07 May '13

07 May '13

Dear Bluetooth Group: I am addressing the issues in this note to you because the Apple MFI staff and page 21 of the "Bluetooth Design Guidelines for Apple Products" indicated this is the most appropriate forum. The Apple iPhone makes it very convenient for users of our product, the "Controller System", to monitor the health and performance of the product. The way the iPhone is used with the product is described below. We would like your advice on the following issues. (i.e. The issues also apply to the iPad and other IOS platforms.) ISSUES ----------- 0) What Bluetooth profile would be most appropriate for products like the Controller System ? 1) What kind of Bluetooth authentication is needed for the Controller System ? 2) Does the authentication need to be integrated into the Controller System ? 3) How, if at all does this authentication, fit in the MFI program framework ? Controller System Description ----------------------------- The primary function of the Controller System is to handle real-time events. It includes an MCU, USB ports, and uses an off the shelf Bluetooth USB adapter for communications. (i.e. The Bluetooth communications are independent of the other Controller System functionality.) The iPhone is used to monitor the health and performance of the Controller System. It displays data from small ASCII log files it retrieves from the Controller system via a Bluetooth connection it initiates. The techniques and protocols used for file transfer conform to industry and standard committee norms for OS independent data transfer. It is necessary for the functionality to be backwards compatible with previous iPhone and IOS releases. The Controller System is RTOS based but has a Bluetooth stack that interfaces with USB Bluetooth adapters the same way as an MS Windows OS. Best Regards, Paul Romero -- Paul Romero RCOM Communications Software Phone/Fax: (510)339-2628 E-Mail: paulr(a)rcom-software.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