April 2015 - Bluetooth-dev - lists.apple.com

Re: Connection to Panasonic module Pan1322 fails
by Craig Dooley 16 Apr '15

16 Apr '15

_______________________________________________ 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

Connection to Panasonic module Pan1322 fails
by Moritz Gmelin 16 Apr '15

16 Apr '15

_______________________________________________ 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:Peripheral Not giving back Its data when the command send to it
by Thirumalrao Surisetty 15 Apr '15

15 Apr '15

_______________________________________________ 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: Nordic Semi Bluetooth
by Ramin Firoozye 14 Apr '15

14 Apr '15

_______________________________________________ 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: Nordic Semi Bluetooth
by Roland King 14 Apr '15

14 Apr '15

Have you checked the return value from *all* softdevice API calls you’re making? Are you sure one of them isn’t returning an out-of-memory error? The nordic softdevice (pre-version 8) reserves a certain amount of space for characteristics out of the fixed allocation of RAM it uses, the actual amount is in the documentation. Add more than that you run out of memory in the softdevice, get get an out of memory error from the API call which adds, or starts advertising or later, game over. There exists an option to keep all registered characteristics in user memory and with the 8.0+ SDK you can ask the softdevice to reserve more memory - although it’s still limited. Once you get over a certain number of characteristics you’re better off using your own allocated memory for them. > On 14 Apr 2015, at 09:36, Mahboud Zabetian <mahboud(a)zabetian.com> wrote: > > Hi. I am curious if anyone here has run into an issue where having too many characteristics (12) can cause a Nordic Semi Bluetooth chipset to stop acting as a peripheral. Our hardware team is reporting that they have issues with having all 12 characteristics and reducing to 2 seems to work. They recommend that we create a struct with 6 or so members and expose those two structs as 2 characteristics instead of exposing 12 characteristics. > > I’d rather not, since once you start adding structs, you’ll have to add versioning, while keeping them as separate characteristics can allow the freedom to modify the characteristics more freely, while supporting older characteristics… > > Is there an issue with having too many characteristics? How have you overcome them? If you are using a Nordic implementation and haven’t had this issue, I’d love to hear from you too. > > Thanks. > > Mahboud > _______________________________________________ > 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/rols%40rols.org > > This email sent to rols(a)rols.org _______________________________________________ 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

Nordic Semi Bluetooth
by Mahboud Zabetian 14 Apr '15

14 Apr '15

Hi. I am curious if anyone here has run into an issue where having too many characteristics (12) can cause a Nordic Semi Bluetooth chipset to stop acting as a peripheral. Our hardware team is reporting that they have issues with having all 12 characteristics and reducing to 2 seems to work. They recommend that we create a struct with 6 or so members and expose those two structs as 2 characteristics instead of exposing 12 characteristics. I’d rather not, since once you start adding structs, you’ll have to add versioning, while keeping them as separate characteristics can allow the freedom to modify the characteristics more freely, while supporting older characteristics… Is there an issue with having too many characteristics? How have you overcome them? If you are using a Nordic implementation and haven’t had this issue, I’d love to hear from you too. Thanks. Mahboud _______________________________________________ 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: peripheral callback that it has been discovered
by Craig Dooley 10 Apr '15

10 Apr '15

There is no way for a peripheral to know when it has been discovered. You would need to have a data transaction between the central and peripheral to establish that relationship. - Craig > On Apr 10, 2015, at 9:57 AM, Christopher Becom <cbecom(a)mira.is> wrote: > > Is there a callback method or a way to log when a peripheral has been discovered? I don't mean that a central a subscribed to a characteristic, just when it was initially discovered? > _______________________________________________ > 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/cdooley%40apple.com > > This email sent to cdooley(a)apple.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

peripheral callback that it has been discovered
by Christopher Becom 10 Apr '15

10 Apr '15

_______________________________________________ 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: send data rate more than 32Kbps on ble issue
by Martijn The 08 Apr '15

08 Apr '15

_______________________________________________ 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/karel%40tandd.co.jp This email sent to mailto:karel@tandd.co.jp _______________________________________________ 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: send data rate more than 32Kbps on ble issue
by karel 08 Apr '15

08 Apr '15

Somewhere between Nick> I filed a bug a while back relating to central -> peripheral data transfer,rdar://16419865, ... and Jason> Yep, this is on our //TODO list. I received this: Mailing list removal confirmation notice for mailing list Bluetooth-dev We have received a request from 17.151.62.50 for the removal of your email address,"karel(a)tandd.co.jp" from the bluetooth-dev(a)lists.apple.com mailing list. .... 17.151.62.50 is not my IP address. Maybe there is a bug in the system? Where can I send a bug report? .......................................... I may be terse at times, but someone has to be. I don't know the dates of the rdar submissions, but we all know this very easily solvable problem has been with us over two generations of iOS. Maybe you need a new broom there at Apple. I do value being on this list, because we are waiting for a good moment to implement BLE in some of our products, and keeping track of the issues with the major players is of prime concern. _______________________________________________ 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