Page 29 of 90
CCT24
•
If the remote is linking for the first time or was unsuccessful linking on its last attempt, it will re-
main awake to record the beacon system parameter list.
•
At wakeup, the
WakeLinkTimeout
timer is started. If the remote is unable to acquire link before
this elapses, it goes back to sleep.
•
If the remote receives an acknowledgement for a data packet it has sent (typically an Event
packet, but in theory it could be any other type of message), it starts or resets the
WakeRe-
sponseTime
timer to remain awake.
•
So long as a GPIO for which I/O reporting is enabled for a level trigger remains in its triggered
state, the remote will remain awake.
•
The remote will remain awake while it still has any ARQ attempts left for a queued transmit pack-
et of any type.
•
The remote will remain awake while it is has serial characters in its buffer left to transmit to its
local host.
Sleep functions are controlled by the following registers (see Section 4.2):
•
SleepMode
- enables/disables sleep mode.
•
WakeResponseTime
- sets the amount of time that a remote will wait for a
response after sending an I/O report.
•
WakeLinkTimeout
- sets the maximum time that a remote will spend trying
to acquire it base before giving up.
Sleep is also affected by the following registers associated with I/O reporting:
IO_ReportTrigger,
IO_ReportInterval, ADC_SampleIntvl,
and
GPIO_EdgeTrigger.
The following table indicates how the
status and control pins function on sleeping remotes:
