| Hi Matthew,
to clarify your case: the peripheral (with the CC2540) provides the data to the central (the iOS device). In the simples case the central can read this data on demand, but the peripheral can indicate/notify about changes in the data as well.
For an illustrative example: the peripheral works as a database server where you can read and write the data with the central (accessibility depends on the configuration) In fact, the BLE standard calls the relevant functionality the GATT server.
Hope this clarifies a bit.
Regards, Andras
On 2013.05.06., at 3:07, Matthew Chung < email@hidden> wrote: I've been looking at the documentation for the TI cc2540 and as I understand it, it is saying the peripheral is the slave and receives data from the central. At least from the ios side, it looks like the TI keyfob and TI car example follow the same pattern.
TI docs
Quote from TI docs
"Peripheral – an advertiser that is connectable, and operates as a slave in a single link-layer connection. Central – scans for advertisements and initiates connections; operates as a master in a
single or multiple link-layer connections. "
On the other hand, the wwdc 2012 videos said the peripheral has the data, the central wants the data, and the peripheral sends data to the central. That is also how the btle_transfer example is written. This, however, seems the reverse of how TI's documentation.
I feel like I'm misunderstanding something so if anyone can enlighten me, it would be much appreciated.
(My app is trying to send data from an IOS device to another device which has uses the cc2540.)
-- Regards,
Matthew
|