
US
2014/0097759
A1
recall
the
logged
usage
information
from
memory
316
at
periodic
intervals
(e.g.,
every
hour,
once
a
day,
twice
a
day,
etc.)
and
to
provide
the
logged
usage
information
to
wireless
transceiver
306
at
the
periodic
intervals
for
transmission
back
to
control
computer
252. In
other
embodiments,
control
com
puter
252
(or
another
network
device)
transmits a
request
for
the
logged
information
to
wireless
transceiver
306
and
the
request
is
responded
to
by
wireless
controller
305
by
trans
mitting
back
the
logged
usage
information.
In
a
preferred
embodiment
a
plurality
of
controllers
such
as
controller
204
asynchronously
collect
usage
information
for
their
?xture
and
control
computer
252,
via
request
or via
periodic
trans
mission
of
the
information
by
the
controllers,
gathers
the
usage
information
for
later
use.
[0038]
Wireless
controller
305
may
also
be
con?gured
to
handle
situations
or
events
such
as
transmission
failures,
reception
failures,
and
the
like.
Wireless
controller
305
may
respond
to
such
failures
by,
for
example,
operating
according
to
a
retransmission
scheme
or
another
transmit
failure
miti
gation
scheme.
Wireless
controller
305
may
also
control
any
other
modulating,
demodulating,
coding,
decoding,
routing,
or
other
activities
of
wireless
transceiver
306.
For
example,
controller
204’s
control
logic
(e.g.,
controlled
by
logic
mod
ule
314
and/or
control
circuit
304)
may
periodically
include
making
transmissions
to
other
controllers
in
a
zone,
making
transmissions
to
particular
controllers,
or
otherwise.
Such
transmissions
can be
controlled
by
wireless
controller
305
and
such
control
may
include,
for
example,
maintaining
a
token-based
transmission
system,
synchronizing
clocks
of
the
various
RF
transceivers
or
controllers,
operating
under
a
slot-based
transmission/reception
protocol,
or
otherwise.
[0039]
Referring
still
to
FIG.
3,
sensor
210
may
be an
infrared
sensor,
an
optical
sensor,
a
camera,
a
temperature
sensor,
a
photodiode,
a
carbon
dioxide
sensor,
or
any
other
sensor
con?gured
to
sense
environmental
conditions
such
as
a
lighting
level
or
human
occupancy
of
a
space.
For
example,
in
one
exemplary
embodiment,
sensor
210
is
a
motion
sensor
and
logic
module
314
is
con?gured
to
determine
whether
control
circuit
304
should
change
states
(e.g.,
change
the
state
of
power
relays
R1
and
R2)
based
on
whether
motion
is
detected
by
sensor
210
(e.g.,
detected
motion
reaches
or
exceeds
threshold
value).
In
the
same
or
other
embodiments,
logic
module
314
may
be
con?gured
to
use
the
signal
from
the
sensor
210
to
determine
an
ambient
lighting
level.
Logic
module
314
may
then
determine
whether
to
change
states
based
on
the
ambient
lighting
level.
For
example,
logic
mod
ule
314
may
use
a
condition
such
as
time
of
day
in
addition
to
ambient
lighting
level
to
determine
whether
to
turn the
light
ing
?xture
off or
on.
During
a
critical
time of
the
day
(e.g.,
when
a
staffed
assembly
line
is
moving),
even
if
the
ambient
lighting
level
is
high,
logic
module
314
may
refrain
from
turning
the
lighting
?xture
off.
In
another
embodiment,
by
way
of
further
example,
logic
module
314
is
con?gured
to
provide
a
command
to
control
circuit
304
that
is
con?gured
to
cause
control
circuit
304
to
turn
the
one
or
more
lamps
of
the
?uorescent
lighting
?xture
on
when
logic
module
314
detects
motion
via the
signal
from
sensor
210 and
when
logic
circuit
314
determines
that
the
ambient
lighting
level
is
below
a
threshold
setpoint.
[0040]
Referring
yet
further
to
FIG.
3,
control
circuit
304
is
con?gured
to
prevent
damage
to
lamps
108
or
110
from
manual
or
automatic
control
activities.
Particularly,
control
circuit
304
may
be
con?gured
to
prevent
on/off
cycling
of
sections
102, 104,
106
by
holding
the
lamps
of
the
sections
in
Apr.
10,
2014
an
“on”
state
for
a
prede?ned
period
of
time
(e.g.,
thirty
minutes,
?fteen
minutes,
etc.)
even
after
the
condition
that
caused
the
lamp
to
turn
on
is
no
longer
true.
Accordingly,
if,
for
example,
motion
or
a
low
ambient
lighting
level
causes
control
circuit
304
to
turn
sections
102, 104,
and/or
106
on
but
then
the
motion
and/
or
ambient
lighting
level
suddenly
increases
(a
worker
enters
the
zone
or
the
sun
comes
out),
control
circuit
304
may
keep
the
lamps
on
(even
though
the
‘on’
condition
expired)
for
a
predetermined
period
of time
so
that
the
lamps
are
taken
through
their
preferred
cycle.
Simi
larly,
in
an
alternative
embodiment,
control
circuit
304
may
be
con?gured
to
hold
the
lamp
in
an
“off”
state
for
a
pre
de?ned
period
of
time
since
the
lamp
was
last
turned
off
to
ensure
that
the
lamp
is
given
time
to
cool or
otherwise
settle
after
the
last
“on”
state.
[0041]
Referring
yet
further
to
FIG.
3,
logic
module
314
or
control
circuit
304
may
be
con?gured
to
include
a
re-strike
violation
module
(e.g.,
in
memory
316)
that
is
con?gured
to
prevent
logic
module
314
from
commanding
control
circuit
304
to
cause
the
?uorescent
lamps
to
turn
on
while
a
re-strike
time
is
counted
down.
The
re-strike
time
may
correspond with
a
maximum
cool-down
time
for
the
lamp,
allowing
the
lamp
to
experience
its
preferred
strike-up
cycle
even
if
a
command
to
turn the
lamp
back
on
is
received
at
wireless
transceiver
306. In
other
embodiments,
logic
module
314
or
control
circuit
304
may
be
con?gured
to
prevent
rapid
on/off
switch
ing
due
to
sensed
motion,
another
environmental
condition,
or
a
sensor
or
controller
error.
Logic
module
314
or
control
circuit
304
may
be
con?gured
to,
for
example,
entirely
dis
continue
the
on/off
switching
based
on
inputs
received
from
sensor
210 by
analyzing
the
behavior
of
the
sensor,
the
switching,
and
logged
usage
information.
By
way
of
further
example,
logic
circuit
314
or
control
circuit
304
may
be
con?gured
to
discontinue
the
on/off
switching
based
on
a
determination
that
switching
based
on
the
inputs
from
the
sensor
has
occurred
too
frequently
(e. g.,
exceeding
a
thresh
old
number
of
“on”
switches
within
a
predetermined
amount
of
time,
undesired
switching
based
on
the
time
of
day
or
night,
etc.).
Logic
module
314
or
control
circuit
304
may
be
con
?gured
to
log
or
communicate
such
a
determination.
Using
such
con?gurations,
logic
module
314
and/
or
control
circuit
304
are
con?gured
to
self-diagnose
and
correct
undesirable
behavior
that
would
otherwise
continue
occurring
based
on
the
default,
user,
or
system-con?gured
settings.
[0042]
According
to
one
embodiment,
a
self-diagnostic
feature
would
monitor
the
number
of
times
that
a
?xture
or
device
was
instructed
to
turn
on
(or
off)
based
upon
a
signal
received
from
a
sensor
(e.g.
motion,
ambient
light
level,
etc.).
If
the
number
of
instructions
to
turn
on
(or
off)
exceeded
a
predetermined
limit
during
a
predetermined
time
period,
logic
module
314
and/or
control
circuit
304
could
be
pro
grammed
to
detect
that
the
particular
application
for
the
?x
ture
or
device
is
not
well-suited
to
control
by
such
a
sensor
(e.g.
not
an
optimum
application
for
motion
control
or
ambi
ent
light-based
control,
etc.),
and
would
be
programmed
to
disable
such
a
motion
or
ambient
light
based
control
scheme,
and
report/log
this
action
and
the
basis.
For
example,
if
the
algorithm
is
based
on
more
than
four
instructions
to
turn
on
(or
off)
in
a
24
hour
period,
and
the
number
of
instructions
provided
based
on
signals
from
the
sensor
exceeds
this
limit
within
this
period,
the
particular
sensor-based
control
func
tion
would
be
disabled,
as
not
being
optimally
suited
to
the
application
and
a
noti?cation
would
be
logged
and
provided
to
a
user
or
facility
manager.
Of
course,
the
limit
and
time
Comentarios a estos manuales