Hi Will,
I did a quick check but did not see support in the bluetooth5 branch.
I'll work on expanding support in 4.2 for now. You're right, I'm not
planning to do any connected advertising at all, I just want to see how the
chip performs when trying to advertise both eddystone and iBeacon
I would say the bluetooth5 branch is fairly stable but I am not in the best
postiion to comment on it. Furthermore, I am not sure if the multi-advertising
support has been fully added to that branch. If it has been added I would go
ahead and use it as it should be fairly stable.
If you wanted
Hi Will,
Thanks for the quick response. The controller only support on 4.2 makes
sense based on what I found in the source code. (I found some test code
that exercises this, and was trying to build on top of that.)
How stable would you say the bluetooth5 branch is? If I wanted to try this
Hello Gurpreet:
So a few things here:
The multi-advertising support that was added was “vendor specific”, meaning
that it is (or shall I say was) not in the BLE specification at the time the
code was written. Bluetooth 5 adds support for multi-advertising and that
standard support will be
Hi,
I've been playing around with MyNewt and Nimble on the nRF52dk board, and
noticed the recently added support for multiple advertising instances
(MYNEWT-508). (BLE_MULTI_ADV_SUPPORT)
I want to use this to set up interleaved Eddystone and iBeacon
advertisements, but it doesnt look like those
Hi Simon,
On Wed, May 10, 2017 at 12:47:43PM -0700, Simon Ratner wrote:
> Hi dev list,
>
> I may be completely missing this, but is there a gattc API for subscribing
> to notifications on a NOTIFY characteristic exposed by a peer peripheral?
>
> Cheers,
> simon
You subscribe by writing a
Hi dev list,
I may be completely missing this, but is there a gattc API for subscribing
to notifications on a NOTIFY characteristic exposed by a peer peripheral?
Cheers,
simon
Hey Chris,
On Wed, May 3, 2017 at 12:16 PM, Christopher Collins
wrote:
> On Wed, May 03, 2017 at 12:10:28PM -0700, Christopher Collins wrote:
> > On Wed, May 03, 2017 at 10:59:59AM -0700, Pritish Gandhi wrote:
> > > Hi All,
> > > Just wanted to give an update to the