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

Re: Notification could be enabled
by Don Clark 13 Jul '13

13 Jul '13

I'm having a similar problem with iOS 7 (including DP3), except that for me I have a characteristic that has the properties set for Write & Read & Notify, and I can complete the setNotifyValue and the callback, but when I attempt to write to the characteristic I get the error message that you reported. Same code works fine, with the same BLE device, on iOS 6. Here's my error message: 2013-07-09 21:34:22.441 HOBOmobile[229:60b] <MXBLEDevice.m:(1552)> didWriteValueForCharacteristic: error report = Error Domain=CBErrorDomain Code=0 "Unknown error." UserInfo=0x16550980 {NSLocalizedDescription=Unknown error.} So what's the problem? On 6/29/13 3:00 PM, "bluetooth-dev-request(a)lists.apple.com" <bluetooth-dev-request(a)lists.apple.com> wrote: >From: Qinghui Tang <tangqinghui(a)hotmail.com> >To: "bluetooth-dev(a)lists.apple.com" <bluetooth-dev(a)lists.apple.com> >Subject: Notification could be enabled >Message-ID: <BLU162-W6D4B972CB33A57EF3565DB6760(a)phx.gbl> >Content-Type: text/plain; charset="iso-8859-1" > >One of characteristics has the property Write & Read & Notify & >Indicate.When I called setNotifyValue:forCharacteristic, the delegate >functiondidUpdateNotificationStateForCharacteristic was invoked with >error: >Error Domain=CBErrorDomain Code=0 "Unknown error." UserInfo=0x1cdb6760 >{NSLocalizedDescription=Unknown error.} >Therefore, although my peripheral did send notification (observed with TI >smart sniffer),but iOS function didUpdateValueForCharacteristic was never >called. >Anyone got an idea what may cause the failure of enabling notification? > _______________________________________________ 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

MAP profile support
by Sharp, Neil 12 Jul '13

12 Jul '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

Max. no. of concurrent BLE connections
by Anton Lam 12 Jul '13

12 Jul '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: Firmware vs Software Revision Strings in BLE?
by Etan Kissling 10 Jul '13

10 Jul '13

Rick, I'm not sure about the BLE112 module, but the DIS is not a mandatory service (only GATT and ATT are required). The only issue with it is that you have to either implement all of the characteristics, or none. Note that both the "Hardware Revision String" and "Firmware Revision String" are of type utf8s, meaning that you don't have to put a single number there. Which profile are you trying to implement? There's only a few standard profiles yet (http://developer.bluetooth.org/gatt/profiles/Pages/ProfilesHome.aspx) and maybe the one you are trying to implement does not require the Device Information Service to be implemented? Etan On 11.07.2013, at 00:18, Rick Mann <rmann(a)latencyzero.com> wrote: > Thanks. I read that, but it's pretty wide-open to interpretation. We ended up settling on our own demarcation between software and firmware, but it's a silly distinction; there are multiple smaller processors on the peripheral that have their own code, and then there's the main host processor that runs linux (that one's pretty clearly "software"), but which one of the little processors' versions do we choose for "firmware?" > > Anyway, I've decided it's not that critical. > > On Jul 10, 2013, at 15:04 , Etan Kissling <kissling(a)oberon.ch> wrote: > >> Rick, >> >> see the description of the "Device Information Service" for the "Firmware" and "Software Revision String" values: >> >> http://developer.bluetooth.org/TechnologyOverview/Pages/DIS.aspx >> >> • Firmware Revision String - shall represent the firmware revision for the firmware within the device. >> • Software Revision String - shall represent the software revision for the software within the device. >> >> Etan >> >> >> On 10.07.2013, at 00:28, Rick Mann <rmann(a)latencyzero.com> wrote: >> >>> I'm using a BLE112 module within our peripheral. There are two mandatory fields, firmware revision and software revision. What is the intent of these fields? For example, is firmware the version of the software running on the BLE112 module, and software the version of the software running on our peripheral? It seems this is not appropriate (as it highlights the distinction between our peripheral and the BLE112 module within it). >>> >>> Thanks, >>> >>> -- >>> 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/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/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: Firmware vs Software Revision Strings in BLE?
by Rick Mann 10 Jul '13

10 Jul '13

Thanks. I read that, but it's pretty wide-open to interpretation. We ended up settling on our own demarcation between software and firmware, but it's a silly distinction; there are multiple smaller processors on the peripheral that have their own code, and then there's the main host processor that runs linux (that one's pretty clearly "software"), but which one of the little processors' versions do we choose for "firmware?" Anyway, I've decided it's not that critical. On Jul 10, 2013, at 15:04 , Etan Kissling <kissling(a)oberon.ch> wrote: > Rick, > > see the description of the "Device Information Service" for the "Firmware" and "Software Revision String" values: > > http://developer.bluetooth.org/TechnologyOverview/Pages/DIS.aspx > > • Firmware Revision String - shall represent the firmware revision for the firmware within the device. > • Software Revision String - shall represent the software revision for the software within the device. > > Etan > > > On 10.07.2013, at 00:28, Rick Mann <rmann(a)latencyzero.com> wrote: > >> I'm using a BLE112 module within our peripheral. There are two mandatory fields, firmware revision and software revision. What is the intent of these fields? For example, is firmware the version of the software running on the BLE112 module, and software the version of the software running on our peripheral? It seems this is not appropriate (as it highlights the distinction between our peripheral and the BLE112 module within it). >> >> Thanks, >> >> -- >> 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/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/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: Firmware vs Software Revision Strings in BLE?
by Etan Kissling 10 Jul '13

10 Jul '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

Airplane mode breaks CoreBluetooth
by dave-ble＠greylogic.com 10 Jul '13

10 Jul '13

Not sure if anyone has seen the following issue (I did a quick search and didn't see anyone else reporting anything similar). I have found that when CoreBluetooth is globally powered off (via airplane mode) while data is being sent/received from a CBCharacteristic, the Bluetooth stack, for a particular peripheral, can get in a broken state. Once in the broken state and the CoreBluetooth is powered back on, the peripheral that was previously sending/receiving will not be able to discover services or characteristics until the iOS device is power-cycled. Steps to Reproduce: 1. Connect to a BLE peripheral. 2. Discover the BLE peripheral services and characteristics for the desired service. 3. Continuously write values to a particular characteristic while also receiving updated values from the same characteristic. 4. Background app (while it continues doing step 3) and goto the iOS settings and turn Airplane Mode on. 5. Turn Airplane mode off and allow peripheral to be connected again. 6. Once connected try to discover services for the peripheral. 7. The delegate "didDiscoverServices" will never get called. Nothing I can do seems to recover the peripheral. The only thing that works is a power-cycle of the iOS device. _______________________________________________ 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: Bluetooth-dev Digest, Vol 10, Issue 183
by Don Clark 10 Jul '13

10 Jul '13

I'm having a similar problem with iOS 7 (including DP3), except that for me I have a characteristic that has the properties set for Write & Read & Notify, and I can complete the setNotifyValue and the callback, but when I attempt to write to the characteristic I get the error message that you reported. Same code works fine, with the same device, on iOS 6. Here's my error message: 2013-07-09 21:34:22.441 HOBOmobile[229:60b] <MXBLEDevice.m:(1552)> didWriteValueForCharacteristic: error report = Error Domain=CBErrorDomain Code=0 "Unknown error." UserInfo=0x16550980 {NSLocalizedDescription=Unknown error.} On 6/29/13 3:00 PM, "bluetooth-dev-request(a)lists.apple.com" <bluetooth-dev-request(a)lists.apple.com> wrote: >Date: Fri, 28 Jun 2013 16:40:27 -0500 >From: Qinghui Tang <tangqinghui(a)hotmail.com> >To: "bluetooth-dev(a)lists.apple.com" <bluetooth-dev(a)lists.apple.com> >Subject: Notification could be enabled >Message-ID: <BLU162-W6D4B972CB33A57EF3565DB6760(a)phx.gbl> >Content-Type: text/plain; charset="iso-8859-1" > >One of characteristics has the property Write & Read & Notify & >Indicate.When I called setNotifyValue:forCharacteristic, the delegate >functiondidUpdateNotificationStateForCharacteristic was invoked with >error: >Error Domain=CBErrorDomain Code=0 "Unknown error." UserInfo=0x1cdb6760 >{NSLocalizedDescription=Unknown error.} >Therefore, although my peripheral did send notification (observed with TI >smart sniffer),but iOS function didUpdateValueForCharacteristic was never >called. >Anyone got an idea what may cause the failure of enabling notification? > >

1 0

Firmware vs Software Revision Strings in BLE?
by Rick Mann 09 Jul '13

09 Jul '13

I'm using a BLE112 module within our peripheral. There are two mandatory fields, firmware revision and software revision. What is the intent of these fields? For example, is firmware the version of the software running on the BLE112 module, and software the version of the software running on our peripheral? It seems this is not appropriate (as it highlights the distinction between our peripheral and the BLE112 module within it). Thanks, -- 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: MFI for Bluetooth Low Energy Custom Services
by Stefan Damm 09 Jul '13

09 Jul '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