Datasheet

Page 148 of 161
nRF8001 Product Specification
Revision 1.2
26.8 PipeStatusEvent (0x88)
PipeStatusEvent lists the pipe connection and availability status
26.8.1 Functional description
This event is sent from nRF8001 to the external application controller whenever there is a change in
service pipe availability status.
The
PipeStatusEvent returns two pipe lists in the form of two 64-bit bitmaps:
•
PipesOpen: Available service pipes on which data can be received (or transmitted) without further
action.
•
PipesClosed: Service pipes on which data can be received only after nRF8001 has instructed the
Client (peer device) to send data. These service pipes are opened using the
OpenRemotePipe
command.
See section 20.8 on page 74
for a functional description on pipe availability.
Each bit in the bitmaps corresponds to a service pipe. For the PipesOpen bitmap, a bit is set to ‘1’ indicates
that the service pipe is available, when set to ‘0’ it is unavailable. For the PipesClosed bitmap, a bit is set to
‘1’ indicates that the service pipe requires opening, when set to ‘0’ no action is required.
The service pipes are counted from the first byte starting with the least significant bit.
The following two examples show a bitmap for an open pipe and a closed pipe respectively, see Table 98.
on page 149 for an example of a bitmap returned:
• If
PipesOpen bitmap = 0xFEFF0D0000000800 then the nRF8001 service discovery procedure
execution has not completed and the following service pipes are open; Pipes 1 through 16, 18, 19
and 51.
• If
PipesClosed bitmap = 0x0000821100100000 then service pipes 17, 23, 24, 28 and 44 require
opening.