On Thu, Nov 02, 2017 at 09:10:59AM -0700, will sanfilippo wrote: > Others can correct me if I am wrong but I will attempt to answer some of > these: > > 1. Yes, the current code supports this.
I know the controller supports multiple advertisers, but I don't believe this functionality is accessible through the host API. To do this, you'll need to talk directly to the controller via HCI commands (or augment the host API to do it for you). > 2. Yes, the current code supports this assuming you want to use a different > random address for each advertiser. I think the host lacks support for this as well. > 3. Yes, you can scan 100% of the time. Of course, if you advertise you wont > scan, and if you connect you will not scan during the connection event. > Otherwise, you will be scanning 100% of the time assuming you choose the > proper window and interval (if they are equal you scan 100% of the time). There is no problem with advertising and scanning at the same time, is there? Chris > > > > On Nov 2, 2017, at 8:49 AM, Greg Strange <g...@synapse.com> wrote: > > > > Hi, > > > > We are kicking off a project that will have a number of NRF52840 radios, > > each doing something slightly different. Right now we are trying to decide > > whether we will use the Nordic SDK or mynewt. Some of the things we want to > > do are well within mainstream BLE and should be easy. Some things are a bit > > custom. I've glanced at the mynewt BLE API, but it is not clear whether a > > few of our needs are directly supported without the need for us to get into > > the core code. > > > > Below is a list of a few features we want to support. We'd love to hear > > whether the features are directly supported by the API, or if not, your > > opinions on the how involved it will be for us to add these features. > > > > 1. We'd like a single radio to be advertising multiple advertising packets > > at different intervals. For example, it may be sending an iBeacon like > > packet at 200ms, while also sending an EddyStone like packet at 250ms, > > while also sending some other packet at some other interval. > > > > 2. In case #1, we would also like the option of using a different > > advertising address for each beacon. E.g. the iBeacon advertising address > > could be different than the address in the Eddystone beacon. > > > > 3. We would like a radio to be able to listen for advertisement packets > > 100% of the time. It looks like the API to turn on scanning takes interval > > and window parameters. Can these be set up such that the radio is listening > > 100% of the time? > > > > 4. We'd like to dedicate a single radio to listening for advertisements on > > a single channel. (In fact, we'd like to dedicate three radios, one to each > > channel so that we are listening 100% of the time to each advertisement > > channel.) Is there a way to specify a single advertising channel when > > scanning or listening for advertisements? > > > > Are any of the above supported already in the API? > > > > If not, are we looking at major rework, or simple changes in your opinions? > > > > Thanks for any help > > > > > > *Greg Strange* > > Software Engineering Program Lead > > > > *Synapse Product Development* > > A Cambridge Consultants Company > > mail 1511 6th Ave Suite 400, Seattle, WA 98101 > > direct +1-206-832-1269 ext. 3505 <+1-206-832-1269,3505> | office > > +1-206-381-0898 | mobile +1-206-240-5605 > > g...@synapse.com | https://www.synapse.com > > > > This email and any files transmitted with it are confidential. Unauthorized > > publication, use or dissemination of this email is prohibited. > > Please consider the environment before printing. >
