February 2014 - Bluetooth-dev

None
by Kevin Tsurutome 22 Feb '14

22 Feb '14

_______________________________________________ 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: Unknown error 1309 in didFailToConnectToPeripheral
by Etan Kissling 22 Feb '14

22 Feb '14

BLE error codes are typically only 1 byte. Seeing a 1309 error code is most likely a CoreBluetooth internal thing (intended or unintended, like uninitialized memory.). I think the best way to get a professional answer to your problem is the apple DTS (costs 49.50$ per ticket - 2 included for free per year). If you use it, it would be cool if you could share their answer to the problem. Otherwise, the least you could do is go to the bug reporter and then hope (most bugs are closed as duplicates of X, but you don’t have permission to view the status of X ;) ). Etan On 19.02.2014, at 19:21, Moe Aboulkheir <moe.aboulkheir(a)gmail.com> wrote: > Hey, > > Long time listener, first time caller. > > I have seen a post or two about 1309, and a couple of SO questions, with no real result, mostly due to lack of information from the asker. To clarify: > > When connecting to a peripheral, didFailToConnectToPeripheral is sometimes passed "Unknown Error: 1309". The aggravating precondition seems to be that either the peripheral or the central is running in the background (with the appropriate UIBackgroundModes key). This error is inevitable with long running background processes and requires turning bluetooth off and on to resolve. > > I have opened a bug with Apple, but have not heard back. > > Take care, > Moe > > More info: > > This happens with peripherals which have previously (sometimes immediately previous) been successfully connected to. The application on both sides of the connection is one which cycles between peripheral and central modes, however I have reproduced this issue with trivial sample code - one peripheral application and a central. The only requirement is repeated reconnections and backgrounding. > > The error object has no description, and nobody on the internet seems to have any information about what the error could mean, even vaguely, let alone how to fix it. I know this error code is used elsewhere to indicate a file position/seek/read error, but that's very little to go on. > _______________________________________________ > 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: Unknown error 1309 in didFailToConnectToPeripheral
by András Kövi 19 Feb '14

19 Feb '14

_______________________________________________ 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

Unknown error 1309 in didFailToConnectToPeripheral
by Moe Aboulkheir 19 Feb '14

19 Feb '14

_______________________________________________ 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: Device Info Characteristics with an OLS425 and Mac OS X
by Ringwald Matthias 18 Feb '14

18 Feb '14

Hi James To get some more information about what goes wrong, you can install the “Hardware Tools for Xcode/Mavericks” from the Apple’s developer pages. It contains the excellent PacketLogger tool to look at the actually ATT protocol data being exchanged with your peripheral. Alternatively, you could also try an air sniffer, like the one that’s part of TI’s CC2540 developer kit. Best Matthias On 17.02.2014, at 20:07, James Snyder <james(a)gsat.us<mailto:james@gsat.us>> wrote: Hi - I’ve recently been working with a connectBlue OLS425 module (http://www.connectblue.com/products/bluetooth-low-energy-products/bluetooth…) with iOS and things have gone mostly smoothly there (aside from connection interval limiting baud rate). However, when I tried to make a port over to Mac OS X, I began noticing some issues on my MacBook Pro Retina, 13-inch, Late 2013 running 10.9.1, mainly that the device info characteristics are not being reported correctly. This happens when writing my own code for connecting to the device and also in LightBlue 1.2. I’m expecting to see 2A24, 2A26, 2A28 & 2A29, but only get: - Connected to device UUID: 8BB05933-69AB-41EE-A87F-475BBD39C72F Named: OLS425 - UUID 2A24 Read Value: 0x636F6E6E656374426C7565 - UUID 2A26 Read Value: 0x4F4C53343235 - UUID 2A29 Read Value: 0x636F6E6E656374426C756500 So the Model Number (2A24) shows almost the same value as Manufacturer Name (2A29) minus a null byte and Firmware revision (2A26) gives what should be in the model number field (2A24). What’s interesting is that I can get correct values for each characteristic by using LightBlue 1.2 running on 10.9.1 in a Parallels VM on the same rMBP with the internal Bluetooth module switched to the VM (though reading values is laggy in that context): - Connected to device UUID: 71C1FDFD-DC8D-4723-8657-2629368C0AEE Named: OLS425 - UUID 2A29 Read Value: 0x636F6E6E656374426C756500 - UUID 2A24 Read Value: 0x4F4C53343235 - UUID 2A26 Read Value: 0x312E332E30203130313337 - UUID 2A28 Read Value: 0x312E332E30203130313337 With gatttool under Linux (in a VM, same Apple internal module allocated to the VM), I get: [ ][78:C5:E5:6D:97:14][LE]> connect 78:C5:E5:6D:97:14 [CON][78:C5:E5:6D:97:14][LE]> char-read-uuid 00002a29-0000-1000-8000-00805f9b34fb handle: 0x0012 value: 63 6f 6e 6e 65 63 74 42 6c 75 65 [CON][78:C5:E5:6D:97:14][LE]> char-read-uuid 00002a24-0000-1000-8000-00805f9b34fb handle: 0x0014 value: 4f 4c 53 34 32 35 [CON][78:C5:E5:6D:97:14][LE]> char-read-uuid 00002a26-0000-1000-8000-00805f9b34fb handle: 0x0016 value: 31 2e 33 2e 30 20 31 30 31 33 37 [CON][78:C5:E5:6D:97:14][LE]> char-read-uuid 00002a28-0000-1000-8000-00805f9b34fb handle: 0x0018 value: 31 2e 33 2e 30 20 31 30 31 33 37 The Linux and VM OS X results seem to be accurate, since the expected displayed values for all of these are: 0x2A29 -> Manufacturer Name -> connectBlue 0x2A24 -> Model number -> OLS425 0x2A26 -> Firmware revision -> 1.3.0 10137 0x2A28 -> Software revision -> 1.3.0 10137 Has anyone run into issues like this before on Mac OS X or know of any solutions or workarounds? One thing that seems like a bit of a clue is the order that the characteristics show up in LightBlue: 2A29, 2A24, 2A26, 2A28 when correct, 2A24, 2A26, 2A29 when incorrect. Also, the vendor (connectBlue) tried using LightBlue 1.2 on a MacBook Air running 10.8.5 and got correct values in that context. Best. James Snyder Global Satellite Engineering Senior Engineer (m) +1.847.644.2322 www.gsat.us<http://www.gsat.us/> _______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev(a)lists.apple.com<mailto:Bluetooth-dev@lists.apple.com>) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/bluetooth-dev/mringwal%40inf.ethz.ch This email sent to mringwal(a)inf.ethz.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: Reconnecting with peripheral
by Etan Kissling 16 Feb '14

16 Feb '14

_______________________________________________ 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: Reconnecting with peripheral
by ponthota viswanath reddy 16 Feb '14

16 Feb '14

_______________________________________________ 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: CLBeacon and CLPeripheral
by Fred Visticot 13 Feb '14

13 Feb '14

Did you check the Estimote SDK ? They provide a wrapper around the CLBeacon (EstimoteBeacon) and this wrapper includes the CLPeripheral object.. The estimote beacons provide a standard iBeacon message + minor/major/other information in a SCAN_REQ / SCAN_RSP The CBCentralManager returns this SCAN_RESP message has a device Information field I had the same solution as you (add minor and major in the SCAN_REQ/SCAN_RSP) message but we must to avoid to have é beacons with the same minor/major… Tx for your help and oner advices are welcome Fred Le 13 Feb 2014 à 21:38, Khaos Tian <khaos.tian(a)gmail.com> a écrit : > There is no way to make a connection between CLBeacon and CBPeripheral if there are lots of beacons around you. > > You can try to file a enhancement report on radar if you really want that. > > Right now the solution I found was set major and minor in Advertising UUID and when CBCentralManager callback with serivceUUID do some identification to find the right beacon I want to connect. > > Best Wishes, > Khaos Tian > >> On Feb 13, 2014, at 12:15 PM, Frederic Visticot <fvisticot(a)gmail.com> wrote: >> >> I need to update the minor / major of the beacon firmware we have developed. (the beacon is implementing a profile to update minor / major) >> >> When user is monitoring for beacons with the LocationManager API, the CLBeacon are returned. >> The pb is that the CLBeacon does not give any information of the lower layer (CoreBluetooth) >> >> How can I do to make the connection to the right beacon using the CoreLocation API with only the information provided by the beacon (minor and major) ? >> >> Is the only solution to add minor/major/proximityUUID in the scanReq/scanResp message ? >> >> >> _______________________________________________ >> 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/khaos.tian%40gmail.com >> >> This email sent to khaos.tian(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: CLBeacon and CLPeripheral
by Khaos Tian 13 Feb '14

13 Feb '14

There is no way to make a connection between CLBeacon and CBPeripheral if there are lots of beacons around you. You can try to file a enhancement report on radar if you really want that. Right now the solution I found was set major and minor in Advertising UUID and when CBCentralManager callback with serivceUUID do some identification to find the right beacon I want to connect. Best Wishes, Khaos Tian > On Feb 13, 2014, at 12:15 PM, Frederic Visticot <fvisticot(a)gmail.com> wrote: > > I need to update the minor / major of the beacon firmware we have developed. (the beacon is implementing a profile to update minor / major) > > When user is monitoring for beacons with the LocationManager API, the CLBeacon are returned. > The pb is that the CLBeacon does not give any information of the lower layer (CoreBluetooth) > > How can I do to make the connection to the right beacon using the CoreLocation API with only the information provided by the beacon (minor and major) ? > > Is the only solution to add minor/major/proximityUUID in the scanReq/scanResp message ? > > > _______________________________________________ > 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/khaos.tian%40gmail.com > > This email sent to khaos.tian(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

CLBeacon and CLPeripheral
by Frederic Visticot 13 Feb '14

13 Feb '14

_______________________________________________ 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