U.S. patent application number 13/745121 was filed with the patent office on 2013-06-13 for aircraft led washlight system and method for controlling same.
This patent application is currently assigned to B/E AEROSPACE, INC.. The applicant listed for this patent is B/E AEROSPACE, INC.. Invention is credited to David P. Eckel, Gannon T. Gambeski, Seckin K. Secilmis.
Application Number | 20130147373 13/745121 |
Document ID | / |
Family ID | 42036935 |
Filed Date | 2013-06-13 |
United States Patent
Application |
20130147373 |
Kind Code |
A1 |
Eckel; David P. ; et
al. |
June 13, 2013 |
Aircraft LED Washlight System and Method for Controlling Same
Abstract
A modular area washlight illumination system and method for
operating are provided that comprise an intelligent light module
group that has: one or more light modules, each of which comprises
a plurality of discrete illumination sources; a power supply; and
an intelligent module group controller comprising: a) circuitry
that controls the illumination levels of the illumination sources;
and b) an interface for receiving and sending information. The
system further comprises a system controller that comprises: a) an
attendant control panel serving as a user interface; and b) a
system controller interface that is connected to the module group
controller interface.
Inventors: |
Eckel; David P.; (Fort
Salonga, NY) ; Gambeski; Gannon T.; (Saint James,
NY) ; Secilmis; Seckin K.; (Seaford, NY) |
|
Applicant: |
Name |
City |
State |
Country |
Type |
B/E AEROSPACE, INC.; |
Wellington |
FL |
US |
|
|
Assignee: |
B/E AEROSPACE, INC.
Wellington
FL
|
Family ID: |
42036935 |
Appl. No.: |
13/745121 |
Filed: |
January 18, 2013 |
Related U.S. Patent Documents
|
|
|
|
|
|
Application
Number |
Filing Date |
Patent Number |
|
|
12566146 |
Sep 24, 2009 |
8378595 |
|
|
13745121 |
|
|
|
|
61105506 |
Oct 15, 2008 |
|
|
|
61099713 |
Sep 24, 2008 |
|
|
|
Current U.S.
Class: |
315/185R ;
315/210; 315/294 |
Current CPC
Class: |
B64D 2011/0038 20130101;
H05B 47/165 20200101; H05B 47/18 20200101; Y02B 20/40 20130101;
H05B 47/10 20200101 |
Class at
Publication: |
315/185.R ;
315/294; 315/210 |
International
Class: |
H05B 37/02 20060101
H05B037/02 |
Claims
1. A modular area illumination system, comprising: an intelligent
light module group, comprising: one or more light modules, each of
which comprises a plurality of discrete illumination sources; a
power supply; an intelligent module group controller comprising: a)
circuitry that controls the illumination levels of the illumination
sources; and b) an interface for receiving information; a single
housing, one or more PCBs mounted within the housing; module
circuitry mounted on the one or more PCBs, including the power
supply, within the housing; and a connector portion of the module
directly connected to the module separating the module circuitry
within the housing from circuitry external to the housing.
2. The system according to claim 1, wherein the discrete
illumination sources are light-emitting diodes (LEDs).
3. The system according to claim 1, wherein some or all of the
discrete illumination sources are arranged into illumination source
groups.
4. The system according to claim 3, wherein the illumination
sources are grouped according to at least one of: area zones,
color, and illumination source characteristics.
5. The system according to claim 1, wherein the single housing
comprises a rectangular cross-sectional shape and is sized to
generally correspond to a maximum dimension of the module
circuitry.
6. The system according to claim 1, wherein the power supply is a
switching power supply.
7. The system according to claim 1, wherein the discrete
illumination sources and the module circuitry are mounted on
opposite sides of a planar member within the housing.
8. The system according to claim 1, wherein the group controller
interface is an RS-485 interface.
9. The system according to claim 1, wherein the one or more light
modules are a plurality of light modules.
10. The system according to claim 1, wherein: the single housing
comprises a rectangular cross-sectional shape and is sized to
generally correspond to a maximum dimension of the module
circuitry; and the discrete illumination sources and the module
circuitry are mounted on opposite sides of a planar member within
the housing.
11. The system according to claim 9, wherein the power supply and
module group control are distributed across more than one
module.
12. The system according to claim 1, wherein the light module
comprises a housing, a printed circuit board (PCB) mounted within
the housing, and module circuitry affixed to the PCB.
13. The system according to claim 1, wherein the illumination
sources are at least one of individually addressable and
addressable in groups.
14. The system according to claim 1, wherein at least one of the
module groups and modules are individually addressable by an
external system controller.
15. The system according to claim 1, wherein a plurality of module
groups is organized into addressable lighting regions.
16. The system according to claim 15, wherein the lighting regions
comprise at least: sidewall lighting, ceiling lighting, and direct
lighting.
17. The system according to claim 1, wherein the light modules are
arranged in a series configuration.
18. The system according to claim 1, wherein the light modules are
arranged in a U-shaped arrangement.
19. The system according to claim 1, further comprising: a system
controller that comprises: a) an attendant control panel serving as
a user interface; and b) a system controller interface that is
connected to the module group controller interface.
20. The system according to claim 19, wherein at least one of the
system controller and the module group controller comprises
corrective algorithms and associated memory for storing precise
predetermined correction values to compensate for aging
illumination sources, color shifts, or intensity shifts.
21. The system according to claim 1, wherein the group controller
interface comprises an interface for sending information.
22. The system according to claim 1, wherein the intelligent module
group controller circuitry further controls illumination color.
23. The system according to claim 1, wherein the power supply
comprises a pulse width modulator that controls the power delivered
to the illumination source to vary its intensity.
24. The system according to claim 1, wherein the power supply is a
vertically mounted power supply located at a predefined position on
the one or more PCBs.
25. The system according to claim 1, wherein the module group
comprises: first and second modules; the first module comprising a
front-end connector that carries power and communications signals,
and a rear-end connector that carries power and communication
signals; the second module comprising a front-end connector that
mates with the rear-end connector of the first module to receive at
least one of power and communication signals via the first
module.
26. The system according to claim 25, wherein at least one of the
front-end and rear-end connectors is a jumper board that connects
two PCB boards together.
27. A modular area illumination system, comprising an intelligent
light module group, comprising: one or more light modules, each of
which comprises a plurality of discrete illumination sources; a
power supply; an intelligent module group controller comprising: a)
circuitry that controls the illumination levels of the illumination
sources; and b) an interface for receiving information; wherein the
module group controller comprises corrective algorithms and
associated memory for storing precise predetermined correction
values associated with known variance characteristics over time to
compensate for aging illumination sources, color shifts, or
intensity shifts.
28. The system according to claim 27, wherein the memory further
stores calibration data associated with the one or more light
modules.
29. The system according to claim 28, wherein the calibration data
is related to an exact color wavelength or x, y coordinates on a
color chromaticity diagram.
30. A modular area illumination system, comprising: an intelligent
light module group, comprising: one or more light modules, each of
which comprises a plurality of discrete illumination sources; a
power supply; an intelligent module group controller comprising: a)
circuitry that controls the illumination levels of the illumination
sources; and b) an interface for receiving information; and an
algorithm for assigning a group identifier to the module group,
wherein the module group comprises a data store to hold the group
identifier.
31. A modular area illumination system, comprising: an intelligent
light module group, comprising: one or more light modules, each of
which comprises a plurality of discrete illumination sources; a
power supply; an intelligent module group controller comprising: a)
circuitry that controls the illumination levels of the illumination
sources; and b) an interface for receiving information; and a scene
database having a plurality of scenes that comprises data
associated with level settings of illumination sources to create a
coherent illumination theme among a plurality of the light modules
or groups so that a single scene setting can be used for the
plurality of light modules or groups; wherein a scene has a total
used power calculation associated with it to ensure the scene, when
executed on a light module or light module group does not exceed a
predefined total power threshold.
32. The system according to claim 31, wherein the scenes include:
an entry or exit theme in which a maximum brightness is provided; a
daylight flight theme in which a medium level brightness is
provided; and a nighttime flight them in which a low level
brightness is provided.
33. The system according to claim 31, wherein the system comprises
algorithms that generate smooth transitions between scenes.
34. The system according to claim 33, wherein the transitions are
non-linear.
35. The system according to claim 33, wherein the transitions are
implemented utilizing look-up tables (LUTs) containing transition
brightness values.
36. The system according to claim 31, wherein the scene database
comprises factory set scenes and user defined scenes using a scene
creation tool.
37. The system according to claim 36, wherein the scene creation
tool is integrated with a power management tool to ensure that
power load limits are not exceeded.
38. The system according to claim 31, further comprising
electrically erasable memory into which scene data is loaded.
39. The system according to claim 31, wherein a group module has an
algorithm for receiving and processing a scene change notification
message.
40. The system according to claim 29, wherein the calibration data
is separately related to color matching and white color temperature
matching.
41. The system according to claim 27, wherein the memory further
stores calibration data associated with each discrete illumination
source.
Description
CROSS REFERENCE TO RELATED APPLICATIONS
[0001] The present application is a continuation of U.S. patent
application Ser. No. 12/566,146, filed Sep. 24, 2009, entitled
"Aircraft LED Washlight System and Method for Controlling Same",
which claims the benefit of U.S. Provisional Application No.
61/099,713, filed Sep. 24, 2008, entitled, "Aircraft LED Washlight
System and Method for Controlling Same", and U.S. Provisional
Application No. 61/105,506, filed Oct. 15, 2008, entitled,
"Aircraft LED Washlight System and Method for Controlling Same",
all of which are herein incorporated by reference.
BACKGROUND
[0002] Washlights are used to provide lighting accents generally
via indirect lighting (i.e., an area is illuminated primarily by
light from the illumination source that is reflected off of another
surface). For vehicles in general, and specifically here for
aircraft, washlights can be used to create various moods,
particularly when colored lighting is used.
[0003] Advances in light emitting diode (LED) technology has made
them an ideal source of light where low-powered lighting solutions
are desirable, which is particularly true in aircraft in which
power availability is limited. However, with known systems, a
degree of sophistication is lacking with regard to the full range
of control that is possible with the use of LEDs and light sources
having similar properties.
SUMMARY
[0004] A modular lighting system is thus provided in which modules
and module groups comprising banks of LEDs, which may be of
multiple colors, to create certain lighting and mood effects. The
modules or module groups are intelligent in that they contain
control circuitry to enable efficient control of the lighting.
[0005] Ideally, this modular lighting system can be designed to
take advantage of existing lighting structures, such as
incandescent bulbs or fluorescent bulb and/or fixtures so that the
older systems can be replaced or retrofitted with minimal
disruption and effort.
[0006] The intelligent light module group has: one or more light
modules, each of which comprises a plurality of discrete
illumination sources; a power supply; and an intelligent module
group controller comprising: a) circuitry that controls the
illumination levels of the illumination sources; and b) an
interface for receiving and sending information. The system may
also further comprises a system controller that comprises: a) an
attendant control panel serving as a user interface; and b) a
system controller interface that is connected to the module group
controller interface.
DESCRIPTION OF THE DRAWINGS
[0007] The invention is described below with reference to the
drawings that illustrate various embodiments of the invention.
[0008] FIG. 1A is a block diagram illustrating an exemplary
configuration of lighting system components;
[0009] FIG. 1B is a block diagram illustrating the primary
components of a lighting module group;
[0010] FIG. 1C is a hierarchical tree diagram illustrating the
different levels of lighting;
[0011] FIG. 1D is a block diagram illustrating regional groupings
of modules;
[0012] FIG. 2A is a bottom view of an exemplary lighting
module;
[0013] FIG. 2B is a side cross-sectional view of the lighting
module shown in FIG. 2A;
[0014] FIG. 3A is a pictorial view of an exemplary lighting module
showing its plug assemblies;
[0015] FIG. 3B is a pictorial view of an exemplary lighting module
group;
[0016] FIGS. 4A-C are respective side, top, and perspective views
of an exemplary lighting module group connected in a U-shaped
manner;
[0017] FIG. 5 is a block diagram illustrating various
configurations of lighting module groups;
[0018] FIG. 6 is an exemplary flowchart for scene change using the
ACP; and
[0019] FIG. 7 is a block diagram illustrating an exemplary
connection of LRUs to an RS 485 communications bus.
DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
Overview and Structural Hierarchy
[0020] A modular lighting system is provided in which the modules
or module groups contain an intelligent control. FIG. 1A provides
an exemplar organization of a grouping hierarchy that may be used
in the aircraft lighting system 10. The lighting system may be
broken down into different addressable lighting regions 20 that
could be used on an aircraft. For example, the regions on an
aircraft could include: sidewall lighting, cross-bin lighting, over
wing exit lighting, ceiling lighting, direct lighting, etc. The
regional breakdown of the lighting system allows lighting control
over broad areas of the aircraft.
[0021] Within each of these regions 20, one or more lighting module
groups 60 may be provided. These module groups 60 may be fashioned
as line replaceable units (LRUs) to enable quick assembly,
maintenance, and replacement. For example, one module group 60
could be for the main cabin cross-bin lighting for rows 10-15.
[0022] The aircraft lighting system 10 further comprises a system
controller 30 that can use, e.g., an attendant control panel (ACP)
40 as the primary user interface for attendants controlling the
lighting during a flight (including on-ground parts of a flight),
as well as for maintenance.
[0023] The LED modules in the system are designed to be
interconnected with one another into module groups. The attached
Appendix provides illustrations of the bracketing and cabling that
may be used in order to connect the modules together and to the
existing aircraft structure for mounting.
[0024] The lighting module groups 60 each comprise a power supply
70 that converts the aircraft power into a power usable by the
module group 80, and may comprise a filter 80 for filtering out
harmful noise and other signals. Each module group comprises a
module group controller 90 that can intelligently handle high-level
instructions from the system controller 30 and possibly provide
useful information back to the system controller 30.
[0025] The lighting module group 60 may comprise one or more
lighting modules 110 that each, in turn, comprise a plurality of
LEDs 130 that may be organized in LED groups 120. Note that an
individual LED 130 could belong to more than one group 120. For
example, an LED 130 could be arranged according to one group based
on the manufacturer, and could be arranged in another group based
on its color.
[0026] Note that when the lighting module group 60 comprises a
single lighting module 110, the characteristics (such as power
supply 70, filter 80, and controller 90) can be associated with the
module 110 itself. In other words, the lighting module group 60 and
lighting module 110 could be construed as the same thing when there
is only a single module 110 in the group 60.
[0027] Each module 110 can be designed to comprise one or more of
the following: a) control circuitry 90 for controlling the module
and possibly other attached slave modules 110' in a group 60; b)
power supply circuitry 70 to enable an LED washlight to function
off of, e.g., a 115 VAC, 400 HZ power source. The power supply 70
can, e.g., receive 115 VAC, 400 Hz in and convert it to 28 VDC, 12
VDC, 5 VDC, or whatever DC voltage is typically necessary for LEDs
and electronics to operate. The power supply 70 design is
preferably a switching power supply, but could also be a linear or
other topology with approximately a 75%-85% efficiency and receive
approximately 7.5 W in and provide 5.7 W out to the LED,
microcontroller and other electronics load; and c:) filtering
circuitry 80 to filter incoming power to the modules and ensure
that no problematic harmonic emissions, spikes or other undesirable
power conditions are introduced back onto the aircraft power
bus.
[0028] The LEDs 130 within a module can possibly be controlled
individually, within specific groupings of LEDs 120 within a
module, or collectively (all LEDs in a module). The groupings 120
can comprise arbitrary numbers of LEDs, or can be grouped according
to area zones, color, LED characteristics, or other schemes.
[0029] FIG. 1C shows the overall hierarchical structure in an
exemplary design, although it should be noted that various levels
of the hierarchy do not necessarily need to exist in every
embodiment. FIG. 1D is an exemplary configuration, showing the ACP
40 (discussion of the ACP 40 herein can also infer reference to the
associated system controller 30) that is connected to a number of
regional lighting configurations 20. The ACP 40 can communicate via
ports, such as an RS-485 port, or a networking port using, e.g.,
Ethernet, TCP/IP, etc. FIG. 1D shows that the different lighting
components can be lighting module groups 60 or individual lighting
modules 110 themselves (which could also be construed as a module
group 60 having a single lighting module 110).
[0030] FIG. 2A is a bottom view of an exemplary lighting module
110. As can be seen, individual LEDs 130 A 1.1, 130 A1.4, can be
organized into LED groups (the two noted LEDs belonging to LED
group 120 A1. The LEDs 130 can be identical to each other (in terms
of color or other operational characteristics), or they can be
different. Similarly, the LED groups 120 can be identical to one
another (e.g., 120 A1, 120A2), or can be different from one another
(e.g., 120A1, 120 B1). The LEDs could be arranged in any
configuration. FIG. 2B is a side cross-sectional view of the module
110 shown in FIG. 2A, illustrating an exemplary layout of the
circuit components within the module case. Although FIG. 2B
illustrates the power supply 70, filter 80, and module group
controller 90 being arranged at a particular location on the PCB,
the actual location of the components can be changed based on
engineering design principles. For example, the power supply or
other components could be flipped over on a back plate to
facilitate heat transfer.
[0031] FIG. 3A shows a module 110 configured as a LRU, having a
power plug assembly 112, and a terminating connector 114 that can
be used to join the module 110 with additional modules 110.
[0032] As noted above, the modules 110 may be collected together
into module groups 60, e.g., three modules 110 to a module group
60. FIG. 3B shows a collection of three such modules 110 arranged
as a group 60. FIGS. 4A-C illustrate another arrangement of modules
110 into module groups 60, the modules 110 being arranged in a
U-shaped parallel configuration.
[0033] Although FIGS. 4A-C show individual modules 110 that each
have an extruded housing and are interconnected via plugs. However,
it is also possible that the module groups 60 comprise a common
housing and that the individual modules 110 are implemented as
printed circuit boards within the housing and are joined together
via, e.g., a jumper board, or other form of plug. These designs
facility ease of assembly and ease of repair, and a modular
configuration with housing and mounting brackets permits extremely
easy and efficient installation and removal.
[0034] As is illustrated in FIG. 5, a module group 60, may comprise
all master modules (Configuration 1) that are each externally
connected to an external controller and controlled independently of
one another. Or, (Configuration 2) the group may comprise any
combination of master modules that are directly connected to and
controlled by an external controller and slave modules 110' that
receive communications and control signals through a connected
master module 110.
[0035] Configuration A illustrates a module group 60 in which each
module 110 comprises a power supply 70, a filter 80, and a
controller 90. However, in Configuration B, it can be seen that the
first module 110 only comprises a filter, whereas the second module
110 comprises the power supply 70 and control, and finally, the
third module 110 does not comprise a power supply 70, filter 80, or
controller 90. In this illustration, the third module 110 is a
dummy that just accepts the power and control from a different
module in the group.
[0036] For a module group 60, there can be one power supply 70 per
unit or two power supplies 70 per unit preferably at opposite ends
of the device and also preferably fitting within a washlight
extrusion or within a bracket area at each end of the washlight. If
more power is needed, the power supply 70 can also extend into a
bracket area that connects lighting units together into an
assembly, which can increase the power output capability.
[0037] The LEDs 130 can be fed from one or both power supplies 70
either in a linear array, alternating LEDs 130 or in a U-shaped
array or any combination thereof. These configurations perform
slighting differently when the LEDs 130 are powered up or if one
string of LEDs goes out.
[0038] The two linear strip array approach also allows for light
levels to be increased incrementally and independently which should
help extend the life of the device because each power supply 70
could alternate their operation thus allowing each power supply 70
to run at lower than maximum levels and/or be off for periods of
time to allow the power supply 70 to cool off. The power to a
specific LED 130 can be controlled via modifying the
voltage/current level to the LED or by a scheme such as pulse-width
modulation, etc.
[0039] Also, additional external power supplies 70 that are
preferably located within the bracket area can be added and
controlled in the same manner above thus increasing the overall
power output and life of the device.
[0040] As noted above, the modules 110 themselves or module groups
60 can collectively be controlled by a master or system controller
30. Such a master controller 30 can permit operation of the modules
110 or module groups 60 at a much higher functional level than has
previously been possible.
Use of Scenes
[0041] A very high level of control involves defining various
"scenes" that dictate certain lighting characteristics that can be
applied, e.g., airplane-wide. The use of these high level scenes
can greatly simplify complex lighting control, and can permit,
e.g., a flight attendant, to select a scene from a few basic scenes
to create a particular lighting pattern, using the attendant
control panel (ACP) 40 that is connected to the system/main
controller 30.
[0042] For example, a scene designated "entry/exit" or
"cleaning/maintenance" might designate a maximum level of white
lighting (e.g., 5000 Kelvin), whereas a scene of "daylight
mid-flight" might designate a moderate level of lighting with a
cooler color temperature (e.g., 3000 Kelvin) having more of a
yellow component. A scene of "night-time sleeping" might designate
a very dim blue lighting. In this way, specific predefined scenes
can be used to easily control the cabin lighting. It is possible to
provide an override that would let the specific level for each
color group be manipulated from a user interface of the main
control device.
[0043] The controller 30 itself may have corrective algorithms that
permit precise adjustment of the LEDs 130 and that could, e.g.,
compensate for aging LEDs 130, color shifts, etc., over time.
Similarly, the corrective algorithms could reside in the module
groups 60 or modules 110 themselves.
[0044] Furthermore, when transitioning from one scene, or even
color/level setting, specific algorithms can be implemented to
effect a smooth transition--which is not necessarily a linear
adjustment of each respective color. Thus, to adjust from 100%
brightness to 20% brightness from white to blue, a linear
adjustment might introduce an undesirable red component in the
transition. Thus, in one embodiment, specific look-up tables (LUTs)
can be provided that are used by the controlling processor(s)
(system controller 30, and/or group/module controller 90)
containing the necessary brightness values for properly adjusting
during the transition. The control may be effected using software
algorithms specifically designed for creating scenes and
controlling the transitions.
Power Control
[0045] Furthermore, given certain restrictions on the use of power,
it may be desirable to provide the control circuitry (in the system
30 and or group/module controller 90) with the ability to limit the
overall power consumption to be within some specified limit, and
this limit could vary depending upon the situation of the aircraft.
This permits precise control of the system, even though the
collective power consumption of the system might exceed predefined
limits.
[0046] For example, the lighting system may, when fully engaged in
its brightest configuration, consume 2000 W. However, there may be
a limit imposed on power used in flight of 1000 W, whereas it is
permissible to use the full 2000 W when on the ground and parked.
In this scenario, the controller could ensure that no more than
1000 W is delivered to the lighting system when the plane is in the
air.
[0047] One way to achieve this is to have a database of the power
consumption characteristics for each module 110 associated with the
master control 30. In the event that a request is received that
would exceed the permissible values, the master control 30 could
appropriately reduce the light levels to keep the system under the
necessary limits. For example, if a flight attendant inadvertently
selected the scene "entry/exit" with its maximum lighting
requirement of 2000 W, the master controller could detect that this
is improper and limit the levels to 50% or less so that the 1000 W
cap is maintained.
[0048] Scene developer's software can be provided to ensure that no
scene or mode will exceed a fixed or variable total power
consumption for the entire lighting system 10, a given application
type, LRU or device. The software can automatically regulate the
wattage load and notify the user or programmer, etc., that the
limit is being approached, has been met, or has been exceeded, and
once met will not allow anymore devices to be added.
[0049] Additionally, the controller 30 can have another option to
allow for random and/or identifiable priorities to be set for
lighting applications, LRU's or devices so that a maximum power
will not be exceeded by reducing the total power to selected
applications, thus automatically scaling back the light output on
lower priority applications while allowing more to others.
[0050] This may be linear or employ more complex relationships and
algorithms and weighting factors to each load type. This is
preferably done automatically without user intervention and
displays and memory tables can be used to show and store lookup
values respectively for current draw, wattage consumption, priority
settings, etc., and this information along with the final
configuration can be displayed in the manufacturing equipment, in
field flight attendant panels, etc. This software may be stored in
a master controller 30 or LCD display of the ACP 40 and information
about individual lighting loads as requirements can also be sent
(or preloaded) and stored in the lighting device (module group 60
and/or modules 110) itself, as required.
[0051] Summarizing and providing more detail, an aircraft lighting
system 10 may incorporate numerous modules (modules 110 or groups
60), each comprising a plurality of LEDs 130. In this system 10,
the following attributes can be provided: lights and groupings at
any level (LED 130, LED group 120, module 110, module group 60,
region 20, and whole system 10) can be, but do not need to be,
individually addressable.
[0052] Advantageously, a hierarchy of "groups" or "zones" of lights
and modules are provided in a manner that is easier to control and
that allow the lights to function together. The system 10 can
provide dynamic scenes that change over time, and these scenes can
be simply controlled via control logic 30 associated with the
Attendant Control Panel (ACP) 40.
[0053] In one embodiment, the lighting units (either modules 110 or
module groups 60) as line-replaceable units (LRUs) can be shipped
from the factory with pre-configured scene information already
stored. A base set of scenes, such as those described above, could
be programmed into the modules 110 or groups 60 so that they can be
easily integrated into an existing system. The system 10 can also
comprise a scene creation tool that permits a scene developer to
design their own scenes and transitions between scenes. This could
also be integrated with the power management tool to help ensure
that maximum permitted power is not exceeded, or to help reduce
power consumption costs. Additionally, in one embodiment, multiple
intensities for the same scene can be designated. For example, the
mid-flight scene could be provided in a High/Medium/Low/Night
setting.
[0054] In a preferred embodiment, some system intelligence can be
placed within a scene generation tool of the group 60 controller
90. In such a design, the lighting LRU 60 firmware in the
controller 90 is simple, and the same. The system 10 can be
designed to prohibit updating of the LRU 60 electrically erasable
(E.sup.2) memory in the field (under the design guide that devices
returned to the factory should be in the same configuration they
were when they left). In this scenario, controller communications
are minimized, and a smaller bandwidth can be realized.
[0055] An exemplary LRU E.sup.2 memory layout of scene data is
provided below: (for the purpose of this illustration: High=0,
Med=1, Low=2, Night=3). This assumes, of course, that four
intensity settings will be provided for each scene (thus, all
scenes will actually have four rows worth of data each in the
memory layout), although this number could vary.
[0056] Unused scenes and/or intensity variations can simply have
0's for all light values (ensuring that they are off for that
selection). Not all columns will be used by all light types, but
all will be present on all lighting unit LRU's 60. The lighting LRU
60 type is preferably written to E.sup.2 memory during a final
calibration phase (along with the calibration data), when the unit
is about to leave the production center. A serial number of the
unit can be provided, and its characteristics can be associated and
stored for later reference. The lighting LRU firmware can use the
light type in its E.sup.2 memory in order to determine which values
to use.
[0057] The following table illustrates an exemplary arrangement for
storing a scene table.
TABLE-US-00001 TABLE 1 Exemplary Scene Data Storage Table Green
Blue White #1 White #2 Amber Scene Red Value Value Value Value
Value Value Transition (2 bytes- (2 bytes- (2 bytes- (2 bytes- (2
bytes- (2 bytes- Time Scene # Intensity 10 bits 10 bits 10 bits 10
bits 10 bits 10 bits (millisec; 2 (1 byte) (1 byte) used) used)
used) used) used) used) bytes) 0 0 (High) 0x0RRR 0x0GGG 0x0BBB
0x0WWW 0 0 0x7530 0 1 (Med) 0x0RRr 0x0GGg 0x0BBb 0x0WWw 0 0 0x7530
0 2 (Low) 0x0Rrr 0x0Ggg 0x0Bbb 0x0Www 0 0 0x7530 0 3 (Night) 0x0rRR
0x0gGG 0x0bBB 0x0wWW 0 0 0x7530 . . . . . . . . . . . . . . . . . .
. . . . . . . . . 11 0 (High) 0x0RRR 0x0GGG 0x0BBB 0x0WWW 0 0
0x7530 11 1 (Med) 0x0RRr 0x0GGg 0x0BBb 0x0WWw 0 0 0x7530 11 2 (Low)
0x0Rrr 0x0Ggg 0x0Bbb 0x0Www 0 0 0x7530 11 3 (Night) 0x0rRR 0x0gGG
0x0bBB 0x0wWW 0 0 0x7530
[0058] Utilizing this philosophy, the entire scene table can occupy
approximately 708 bytes of E.sup.2 memory for 12 scenes.
Calibration data may be stored in a similar fashion (as shown by
the sample table below).
TABLE-US-00002 TABLE 2 Exemplary Calibration Data Storage Table
White #1 Intensity Red Bias Green Bias Blue Bias Bias White #2 Bias
Amber Bias (index) (2 bytes) (2 bytes) (2 bytes) (2 bytes) (2
bytes) (2 bytes) 0 (High) 0xRRRR 0xGGGG 0xBBBB 0xWWWW 0 0 1 (Med)
0xRRRr 0xGGGg 0xBBBb 0xWWWw 0 0 2 (Low) 0xRRrr 0xGGgg 0xBBbb 0xWWww
0 0 3 (Night) 0xrrRR 0xggGG 0xbbBB 0xwwWW 0 0
[0059] Thus there can be one bias table entry (calibration offsets)
for each intensity group. For the example shown of four
intensities, the entire table will have four rows (occupy 48
bytes). If required, the bias table could be expanded so that every
built-in scene has its own bias entry.
[0060] The preferred operation is that on LRU 60 power up, the
firmware will load the scene for #0, High intensity and the bias
table values for high into RAM, and attempt to establish
communications over a communication link, such as RS-485 with the
ACP 40. Failure to establish communication with the ACP 40 within a
specified time interval can, e.g., result in this default scene
being activated. This provides a failsafe mode in the event that
the ACP 40 is broken, missing, or non-functional, and will allow
there to be light on board the aircraft. An extra scene can be
provided as the "failsafe" with little impact to memory
requirements. Upon receipt of a valid command from the ACP 40 to
change scene selection or intensity, the appropriate table entries
can be loaded into RAM by the firmware, and the scene transitioning
will start to occur.
[0061] Under this scheme, the ACP 40 does not need to "know"
anything related to the default "canned scenes". It merely sends a
broadcast message on all of its communication (e.g., RS-485) ports
to change to scene # X, with intensity level Y), to elements at the
regional 20, module group 60, or module 120 level. A one-time
correlation can be made in the ACP 40 that, e.g., scene
1=Boarding/Disembark, 2=Safety Video, 3=Taxi/Takeoff/Ascent, etc.,
so that the display activation sends out the correct scene number
to correspond to the data contained in the internal tables. This
simple scheme satisfies all of the requirements for a baseline
system.
Protocol Considerations
[0062] As previously stated, the ACP 40 will not have to do
anything special for an "out of the box" system 10. It can merely
broadcast and repeat (at predetermined intervals) the current scene
number and intensity value. If a particular light type does not
participate in that scene, its table entries will all be 0, and
those lights will remain off.
[0063] The protocol can be configured to allow for BIT/BITE, LRU
Grouping or Zones, Custom Scenes, and Maintenance Modes. The
BIT/BITE sequence is rather simplistic--it is a request for address
status, and a reply. If no reply is received, the fault is
logged/displayed etc. Grouping or Zones preferably occur from the
ACP 40.
[0064] A mechanism may be provided to tell each addressed LRU 60,
110 what group it belongs to (e.g., kept in RAM in the lighting LRU
60, 110). This should be resent by the ACP 40 at each system power
up and on change (assuming the ACP 40 allows for dynamic moving of
zones). The messages sent from the ACP 40 to the lighting LRUs 60,
110 can then incorporate the group number for which the
scene/intensity change is directed. Only lighting LRUs 60, 110 that
have been configured to be a member of that group or zone, will
actually respond to the request for scene change.
[0065] In a preferred embodiment, the minimum packet size is 6
bytes, and the maximum packet size is 256 bytes
[0066] Each scene change initiated at the ACP 40 can result in a
notification message being broadcast to each LRU 60, 110 three
times, spaced a predefined number of milliseconds apart. The ACP 40
can debounce scene selections (consecutive button presses) for,
e.g., predefined number of milliseconds. The ACP 40 can
periodically re-broadcast the current scene selection at predefined
intervals.
[0067] A group value of "ALL" may also be included to force all
lighting units when zones are employed. For the custom scene
portion, the ACP 40 will once again need to be involved, since it
would be undesirable to remove the lighting units and return them
to the factory for addition of new scenes.
[0068] Basically, when the custom scene is selected, the ACP 40 can
use a message to send the custom intensity values to the lighting
LRUs 60, 110. When the lighting LRUs 60, 110 receive these
commands, they then place the data into RAM and begin the scene
transition. Custom scenes do not have to have any bias or
calibration applied to them, since they may not have been developed
at the production facility and calibrated for uniformity.
Maintenance modes can be provided as well.
Scene Generation
[0069] A PC-based scene generation tool can be used as the brains
of the system, and can incorporate any of the compensation
equations for temperature and intensity variations. It is
preferably the place to perform the calibration of LRU's as they
leave the factory, since it can easily compare a database of
expected values to measured ones, and calculate the necessary
biases to achieve the desired results. It can also be used to limit
system physical temperature and current draw. The tables that this
tool may produce can have all of these factors taken into
consideration, and may be what is eventually stored in the
individual lighting LRUs 60, 110.
General Cabin Lighting Communications Protocol
[0070] As noted above, the general cabin lighting system 10 is used
to illuminate the interior cabin of the aircraft. The system 10 may
comprise two main parts, the lighting units (grouped 60 or modules
110) and the ACP 40. The ACP 40 may be used as the main interface
point for cabin attendants and maintenance personnel. It allows
input from users to execute the various cabin lighting scenarios
inside the aircraft cabin. The lighting units 60, 110 are the
physical units installed throughout the aircraft which are used to
illuminate the aircraft cabin to the lighting scenarios
selected.
[0071] The following description of different communication
functions is split into four sections: Normal Operation, Addressing
Operation, Bit/Bite Operation and other Misc Operations that may
occur (loss of communications, decompression, etc.).
Normal Operation:
TABLE-US-00003 [0072] General Command Format: <SOT>
<DEVICE ID> <ADDR> <STATUS> <CMD>
<DATA> <D_TIME> <XOR CHECKSUM> <EOT> Device
IDs: Device ID 9150 Ceiling Wash Lights (RGB + W) <DEVICE ID>
= "A" 0 .times. 41 9150 Sidewall Wash Lights (RGB + W) 9150 Cove
Wash Lights (RGB +W) 9250 Over-Wing Wash Lights (RGB + WW) 9200
Cross-Bin Wash Lights (W + A) <DEVICE ID> = "B" 0 .times. 42
92XX COS Wash Lights (W + A)
[0073] Note that certain lighting units behave identically to the
another family of washlights. For example, the 9250-XXX family of
washlights is virtually identical to the 9150 family of washlights
except for the additional white LEDs that are powered and
controlled by a separate dedicated 6 VDC emergency power line.
[0074] FIG. 6 is a flowchart illustrating normal operation. The
system sits in an idle state and waits until the ACP is actuated
S210. Once activated, it is determined whether a lighting scene is
activated S212; if so the process continues on. The ACP accesses
the lighting database for the scene selected S214, and then parses
the database and begins transmitting to each LRU the intensity and
color commands S216.
[0075] The lighting LRUs receive the command and begin to
transition to the color/intensity received S218. A rebroadcast for
all messages for scene selected S220 may be performed, and the
scene transmission may then be completed S220 once the necessary
rebroadcasting is complete. It should be noted that the ACP 40 and
associated controller 30 can pass information to the LRUs 60, 110
at a very basic level (brightness level, color information, if
possible) to the addresses, e.g., of each individual LED 130. It
could also send information to LED groups 120. At a higher level,
the information regarding which scene should be activated and be
provided as well.
[0076] The communication to and between groups 60, modules 110, the
system controller 30, etc., can be done via an RS-485 multi-drop
bus, which can handle up to 255 devices and at a rate of 115200
bps. An exemplary command is provided below.
[0077] 9150-XXX Ceiling, Sidewall, Cove and Direct Washlights
(RGB+W)
[0078] Protocol
TABLE-US-00004 TABLE 3 Exemplary Protocol Command Format <DEVICE
<XOR <SOT> ID> <ADDR> <CMD> <DATA>
<D_TIME> CHECKSUM> <EOT> Bytes 1 1 1 1 8 2 2 1 Data
0x01 0x41 0x20-0xFF CMD DATA D_TIME ASCII XOR 0x04 XSUM
[0079] CMD Set Description
TABLE-US-00005 <SOT> = 0x01 - Start of Transmission Character
<EOT> = 0x04 - End of Transmission Character
<DEVICE_ID> = 0x41 - The Device ID for the 9150 and 9250
family of wash lights <ADDR> = 0x21 - 0xFF, 0x20 offset + 5
bit address value, MAX possible devices = 222 0x20 = the general
broadcast address. All 9150 family washlights will accept intensity
commands with this address. Intensity Command: <CMD> = "A"
0x41 - The Intensity command changes the intensity of the wash
lights <DATA> = R1, R2, G1, G2, B1, B2, W1, W2 Rx The Red
intensity value is 10 bits wide and split into 2 bytes, R1 and R2.
R1 = 0x20 offset + Most Significant 5 of 10 bits (RED) R2 = 0x20
offset + Least Significant 5 of 10 bits (RED) **R1, R2 = If R1 and
R2 = 0xC0 then the intensity value is to remain unchanged Gx The
Green intensity value is 10 bits wide and split into 2 bytes, G1
and G2. G1 = 0x20 offset + Most Significant 5 of 10 bits (GREEN) G2
= 0x20 offset + Least Significant 5 of 10 bits (GREEN) **G1, G2 =
If G1, G2 = 0xC0 then the intensity value is to remain unchanged Bx
= The Blue intensity value is 10 bits wide and split into 2 bytes,
B1 and B2. B1 = 0x20 offset + Most Significant 5 of 10 bits (BLUE)
B2 = 0x20 offset + Least Significant 5 of 10 bits (BLUE) **B1, B2 =
If B1, B2 = 0xC0 then the intensity value is to remain unchanged Wx
= The White intensity value is 10 bits wide and split into 2 bytes,
W1 and W2 W1 = 0x20 offset + Most Significant 5 of 10 bits (WHITE)
W2 = 0x20 offset + Least Significant 5 of 10 bits (WHITE) **W1, W2
= If W1, W2 = 0xC0 then the intensity value is to remain unchanged
<D_TIME> = D1, D2 Dx The scene transition time <D_TIME>
represents the number of seconds the scene will be transitioning.
It is a 10 bit wide value and split into 2 bytes, D1 and D2. D1 =
0x20 offset + Most Significant 5 of 10 bits D2 = 0x20 offset +
Least Significant 5 of 10 bits
Addressing Operation:
[0080] As noted above, each lighting unit may incorporate an
address. This address helps to identify the location of the
lighting unit in the aircraft. Using a lighting layout of passenger
accommodation (LOPA), an individual could determine the exact
position of the light in the aircraft. Addressing each light makes
the system capable of handling multiple zones of lighting, and also
allows the systems to do built-in test equipment (BITE) testing to
locate faulty LRUs.
[0081] The ACP 40 and associated controller 30 can control
addressing of the washlights. The ACP 40 can use a Token
communications line in addition to the RS485 line to help address
the washlights. Each Washlight LRU may have an RS485 transceiver,
Token-In, and Token-Out Lines.
[0082] The Token Lines may be used to identify which washlight is
currently being addressed. If a washlight's Token-In line is
active, then the washlight is currently being addressed and any
Address Input Messages are intended solely for that device. If the
washlight receives the address input message it can acknowledge the
receipt of an address with an Address ACK Message. This signifies
that addressing is complete for the device and it is time to move
on to the next device. Next, the ACP 40 can pass the token by
sending a Pass Token Command which will allow the next washlight in
the column to be addressed. Once this is received, the currently
addressed washlight will set its Token-Out line active so that the
next sequential washlight can be addressed. In conjunction, the
previous addressed device will set its Token-Out line inactive to
complete addressing operations for the currently addressed
unit.
[0083] FIG. 7 illustrates this addressing. In FIG. 7, the Center
LRU is currently being addressed since its Token-In Line is active
(Pulled to ground) by the previously addressed LRU. The
Specifications for this communication are as follows:
Control Method: RS485 Half-Duplex
[0084] RS485 Transceivers Load: 1/8 Load, Max possible
devices=255
Baud Rate: 115200 bps
Baud Rate Tolerance: .+-.185 bps
[0085] Message Frequency Messages in Address mode should have a 50
ms pause between commands. Token Line V.sub.IH: 4.7 VDC MIN in
respect to the washlights Token Ref Line. Token Line V.sub.IL: 0.3
VDC MAX in respect to the washlights Token Ref Line.
Protocol
TABLE-US-00006 [0086] Command Format <SOT> <ADDR>
<CMD> <XOR CHECKSUM> <EOT> Bytes 1 1 1 2 1 Data
0x01 0x20-0xFF CMD ASCII XOR XSUM 0x04
[0087] CMD Set Description
TABLE-US-00007 <SOT> = 0x01 - Start of Transmission Character
<EOT> = 0x04 - End of Transmission Character <ADDR> =
0x21 - 0xFF, 0x20 offset + 5 bit address value, MAX possible
devices = 222 0x20 = the general broadcast address. And as such is
not used. Address Input Message: <CMD> = "A" 0x41 - This
command sets the washlights address. Address ACK Message:
<CMD> = "B" 0x42 - This command is the acknowledgement
message from the washlight. Pass Token Command: <CMD> = "C"
0x43 - This command tells the washlights to pass the token
[0088] Example Message Format
TABLE-US-00008 ACP sends: Byte 1: 0x01 Byte 2: 0x21 Byte 3: 0x41
Byte 4: 0x33 Byte 5: 0x34 Byte 6: 0x04 Washlight Responds: Byte 1:
0x01 Byte 2: 0x21 Byte 3: 0x42 Byte 4: 0x33 Byte 5: 0x37 Byte 6:
0x04 ACP sends Pass Token Command: Byte 1: 0x01 Byte 2: 0x21 Byte
3: 0x43 Byte 4: 0x33 Byte 5: 0x36 Byte 6: 0x04
Bit Bite Operation
[0089] The ACP 40 with control 30 controls when BIT/BITE is
initiated. The ACP can use the RS485 line to help poll each
washlight in the system to determine if the washlight is still
active. In addition to polling each device the ACP can send out a
lamp test message that will turn on each one of the LEDs on each
LRU so a visual check may also be performed.
[0090] Protocol
TABLE-US-00009 Command Format <SOT> <ADDR> <CMD>
<XOR CHECKSUM> <EOT> Bytes 1 1 1 2 1 Data 0x01
0x20-0xFF CMD ASCII XOR XSUM 0x04
[0091] CMD Set Description
TABLE-US-00010 <SOT> = 0x01 - Start of Transmission Character
<EOT> = 0x04 - End of Transmission Character <ADDR> =
0x21 - 0xFF, 0x20 offset + 5 bit address value, MAX possible
devices = 222 0x20 = the general broadcast address. And as such is
not used BIT/BITE Request: <CMD> = "A" 0x91 - This command
polls the washlight for status. BIT/BITE ACK Message: <CMD> =
"B" 0x92 - This command is the acknowledgement message from the
washlight.
Misc Operations
[0092] A number of miscellaneous operations may also be provided by
the system 10.
[0093] Checksum Calculation:
[0094] A checksum calculation is provided to help insure the
integrity of the transmitted data. The checksum calculation may be
a one byte XOR checksum of all the bytes including the SOT byte to
the last byte before the checksum value. The checksum has a XOR
PRESET of 0x55. After the checksum calculation is completed the
byte is split into the ASCII representation of the value. So if the
value=0xA3, the Checksum values in the message protocol would be
0x41 and 0x33. Below is the C code which does the Xsum calculation
on the message and the method which converts it to binary.
[0095] Decompression Signal:
[0096] The washlights have no direct decompression signal message.
If the ACP receives a decompression signal then the ACP should
simply send a 100% white intensity command to all lighting
units.
[0097] Loss of Communications:
[0098] If an LRU losses communications with the ACP, it may remain
in the last state which it was commanded.
[0099] Device Calibration
[0100] Corrective algorithms and look-up tables may be utilized to
calibrate lighting devices for color matching, white color
temperature matching, matching over various intensities and use of
various LED manufacturers (to accommodate variations between
manufacturers). This can be done at the individual device (LED 130,
LED groups 120), LRU (module 110, module groups 60), subassembly
(module groups 60, regional lighting groups 20) and complete
application (system 10) level. Corrections may be performed and
stored in the lighting devices, LRUs 60, 110 and/or other remote
devices including master controllers 30, etc.
[0101] It has been recognized that lighting devices 130 can change
over time and can change based on usage (power) and environmental
conditions. For example, where a change over the lifetime of an LED
is known, the operation time of a module 110 can be tracked, and
look-up tables can be provided to compensate and adjust for the
change over time. Thus, if an LED was known to fall off to 98%
brightness after 200 hrs. use, the time for the module could be
tracked and at 200 hrs., a new adjustment value could be applied
for that module, or, since it is possible to address LED groups and
even single LEDs, it could be possible to resolve the new
adjustment values down to the single LED level, if desired. By
using look-up tables (LUTs), known variance characteristics of LEDs
over time can be compensated for. As noted previously, these tables
can reside at the system level on the system controller 30, at the
module group/module level on the group controller 90, or could be
shared between the two.
[0102] Similarly, characteristics that vary over temperature could
be similarly provided in LUTs or some other form of database. Thus,
when the modules 110 are ready to ship from the manufacturer, an
initial calibration procedure may be performed to determine the
exact color wavelength or x, y coordinates on a color chromaticity
diagram, and predetermined tables capable of correcting the LEDs as
they age or as they are operated at different temperatures can be
provided prior to shipment of the manufactured device.
[0103] Furthermore, the LUTs or other database parameters could be
fixed, or, preferably, could be updatable so that as new
characteristics of the LEDs is learned, the tables can be adjusted
accordingly. In this way, corrective adjustments based on
temperature and lifetime use of the modules can be provided.
[0104] In one embodiment, calibration can be done via an internal
and/or external optical sensor that accurately reads the color and
intensity information produced by a module 110 or module group 60,
and adjustment information can be determined based on this
feedback. Updated adjustment information can then be provided
directly or indirectly into the lighting device, LRU 60, 110,
master controller 30, etc.
Additional Exemplary Embodiment
[0105] The following describes an additional exemplary embodiment
and communications for an implementation of the system. The ACP is
the main interface point for cabin attendants and maintenance
personnel, and it allows input from users to execute the various
cabin lighting scenarios inside the aircraft cabin as well as
configure address and view BIT information from its LCD touch
screen interface.
[0106] In this embodiment, all lighting LRUs maintain their scene
information locally in the LRU. The ACP is responsible for
commanding the lighting system to the specific scene that has been
selected by the cabin crew. Lighting assemblies have the capability
to receive messages from the ACP via RS485. The lighting assemblies
are individually addressable enabling the ACP to individually
communicate with each lighting assembly, or to communicate with a
group of lighting assemblies. Lighting assemblies also have the
capability of being BIT tested to detect if the assembly is still
communicating with the system. BIT information from the lighting
system can then be viewed on the ACP.
[0107] In this embodiment, the lighting LRUs have the capability to
have sixteen pre-programmed scenes and sixteen re-programmable
scenes. The pre-programmed scenes do not have the ability to be
altered. The reprogrammable scenes can be altered onboard the
aircraft by the ACP without the need to re-work the devices on a
bench. The lighting scenarios are static, and transition at a
variable rate do not to exceed 5 minutes from one scene to another.
In this embodiment, the physical layer requirements are as follows:
[0108] Communication Method: RS485 Multi-drop Bus (2-wire+shield)
[0109] RS485 Signals: RS485A, RS485B and RS485 Shield [0110] RS485
Transceivers Load: 1/8 Load, Max possible LRUs=255 (Physical Limit)
[0111] Baud Rate: 115200 bps [0112] Baud Rate Tolerance: .+-.185
bps [0113] Duplex: Half-Duplex [0114] Token Signals: Token-In,
Token-Out and Token-Ref
[0115] Token Electrical Characteristics:
TABLE-US-00011 DC Characteristics MIN MAX UNIT Token-In V.sub.IH
High-Level Input Voltage 4 5 V V.sub.IL Low-Level Input Voltage GND
0.5 V Token-Out V.sub.OH High-Level Output Voltage 4 5 V V.sub.OL
Low-Level Output Voltage GND 0.5 V
ACP Protocol Requirements
[0116] The ACP is the controlling focus of the lighting system. The
protocol requirements are the timing and transmission guidelines
the ACP in an embodiment of the invention follow for the lighting
system to operate correctly. [0117] 1) Each scene change initiated
at the ACP results in a notification message being broadcast to the
lighting system. This message is repeated 3 times, with each
message spaced 50 ms apart. [0118] 2) The ACP ensures that each
consecutive message sent to the lighting system is no less than 50
ms apart. [0119] 3) The ACP periodically re-broadcasts the current
scene selection at intervals of 10 seconds. [0120] 4) All responses
to the ACP from the lighting LRUs occur within 50 ms. [0121] 5) The
checksum calculation begins and include the <SOT> byte and
continues until <ASCII XOR XSUM> bytes. [0122] 6) Any message
with an unknown <CMD> are discarded. [0123] 7) Any message
with fields containing illegal or unused values for the specific
<CMD> should be discarded. [0124] 8) When an LRU has its
Input Token Signal active, all messages besides an Address
Assignment Message should be discarded.
[0125] Each lighting LRU in this embodiment incorporates an
individual and unique address. This address helps to identify the
location of the lighting LRU in the aircraft. Using a lighting
LOPA, an individual could determine the exact position of the light
in the aircraft. The SCENE SELECTION message allows the ACP to
select a lighting scene for a specific LRU, a Zone of Lights or the
entire aircraft. The scene selection message allows the ACP to
select either preloaded aircraft lighting scenes or customer
specific lighting scenes.
Scene Selection
[0126] Specifications
[0127] Source Device: ACP
[0128] Destination Device Lighting LRUs [0129] 1) The lighting
assemblies ignore any scene selection messages that select a scene
that is not programmed. [0130] 2) Upon system power up, each LRU
should wait for 30 seconds to receive a Scene Selection Message. If
none is received within that time period, the LRU will
automatically transition to 100% White light. [0131] 3) Receipt of
a Scene Selection Message should cancel/terminate any BIT/BITE mode
that may be in progress. [0132] 4) The lighting assemblies should
ignore this message while downloading scenes, or addressing is
taking place.
[0133] Protocol--Scene Selection Message
TABLE-US-00012 Command Format <DEST <XOR <SOT> MODE>
<DEST> <CMD> <DATA> CHECKSUM> <EOT>
Bytes 1 1 1 1 2 2 1 Data 0x01 0x30-0x32 0x20-0xFF 0x20 DATA ASCII
XOR XSUM 0x04
[0134] CMD Set Description
[0135] <SOT>=0x01--Start of Transmission Character
[0136] <EOT>=0x04--End of Transmission Character
[0137] <DEST MODE>=[0x30-0x32]--The destination mode
selection byte
[0138] 0x30=Broadcast Message
[0139] 0x31=Group/Zone Message
[0140] 0x32=Address Message
[0141] <DEST>=[0x20-0xFF] --The Destination Address.
[0142] <DEST MODE>=0x30:
[0143] <DEST>=[0x30]--Don't Care
[0144] <DEST MODE>=0x31:
[0145] <DEST>=[0x31-0xFF] --The zone selection
[0146] <DEST MODE>=0x32:
[0147] <DEST>=[0x21-0xFF] 0x20 offset+address, MAX possible
LRUs=222
[0148] <CMD>=0x20
[0149] <DATA>=2 Bytes <SCENE><INTENSITY>
<SCENE>=Scene Selection byte. Denotes LRU stored scene
information. The ACP can select either standard aircraft scenes or
customer specific scenes by altering the first nibble of this
byte.
[0150] Standard Scenes: 0x30 offset+4 bit scene number. 16 scenes
max
[0151] Customer Specific Scenes: 0xC0 offset+4 bit scene number. 16
scenes max.
[0152] <INTENSITY>[0x31-0x34]--Denotes the relative intensity
setting for the scene selected.
[0153] 0x31=HIGH
[0154] 0x32=MED
[0155] 0x33=LOW
[0156] 0x34=NIGHT
Addressing Operation:
[0157] The ACP controls addressing of the washlights. The ACP can
use the Token Line in addition to the RS485 line to help address
the washlights. In this embodiment, each washlight LRU has an RS485
transceiver, Token-In and Token-Out Lines.
[0158] The token lines are used to identify, which washlight is
currently being addressed. If a washlight's Token-In line is
active, then the washlight is currently being addressed and any
Address Assignment Messages are intended solely for that LRU. If
the washlight receives the address input message it will
acknowledge the receipt of an address with an Address Response
Message. This signifies that addressing is complete for the LRU and
it is time to move on to the next LRU.
[0159] Next, the ACP can pass the token by sending a Pass Token
Command which will allow the next washlight in the column to be
addressed. Once this is received, the currently addressed washlight
will set its Token-Out line active so that the next sequential
washlight can be addressed. In conjunction, the previous addressed
LRU should set its Token-Out line inactive to complete addressing
operations for the currently addressed LRU.
[0160] Protocol--Address Assignment Message
[0161] Specifications
[0162] Source Device: ACP
[0163] Destination Device Lighting LRUs [0164] 1) Addressing
messages are only processed by lighting assemblies whose Token-In
line is active. [0165] 2) ACP asserts its Token-Out line active
before it begins sending the first address assignment message.
[0166] 3) The lighting assemblies are reassigned any time an LRU is
replaced on board the aircraft. [0167] 4) The Token Lines are
considered active when these signals have the voltage potential of
the Token Ref Line(GND).
[0168] Protocol:
TABLE-US-00013 Command Format <DEST <XOR <SOT> MODE>
<DEST> <CMD> <DATA> CHECKSUM> <EOT>
Bytes 1 1 1 1 2 2 1 Data 0x01 0x30-0x32 0x20-0xFF CMD DATA ASCII
XOR 0x04 XSUM
[0169] CMD Set Description
[0170] <SOT>=[0x01]--Start of Transmission Character
[0171] <EOT>=[0x04]--End of Transmission Character
[0172] Address Assignment Message:
[0173] <DEST MODE>=[0x30]--The destination mode selection
byte
[0174] 0x30=Broadcast Message
[0175] <DEST>=[0x30]--The Destination Address.
[0176] <DEST MODE>=0x30:
[0177] <DEST>=[0x30]--Don't Care
[0178] <CMD>=[0x10]--This command sets the washlights
address.
[0179] <DATA>=<Address><Group/Zone>
[0180] <Address>=[0x21-0xFF] 0x20 offset+address, MAX
possible LRUs=222
[0181] <Group/Zone>=[0x30-0xFF]--Group/Zone Assignment
[0182] Protocol--Address Response Message
[0183] Specifications
[0184] Source Device: Addressed Lighting LRU
[0185] Destination Device: ACP [0186] 1) The ACP should exit
"Addressing Mode" after sending an Address Assignment Message
without receiving an Address Response Message within 50 ms. [0187]
2) The ACP should compare the information returned in the Address
Response Message to its internal database, in order to ascertain
that the correct light type is at the address in question. It may
also verify the serial number, hardware version number, and
firmware version number. Any discrepancy in returned information
should stop the addressing mode of the ACP, and alert the operator
to the problem.
[0188] Protocol:
TABLE-US-00014 Command Format <ACK SOT> <CMD>
<DATA> <XOR CHECKSUM> <EOT> B ytes 1 1 62 2 1
Data 0x06 CMD DATA ASCII XOR XSUM 0x04
[0189] CMD Set Description
[0190] <ACK SOT>=[0x06]--Start of Transmission Character
[0191] <EOT>=[0x04]--End of Transmission Character
[0192] Address Response Message:
[0193] <CMD>=[0x1F]--This command is the acknowledgement
message from the washlight.
[0194] <DATA>=<Address><Device ID><Serial
#><Hardware Rev><Firmware Rev>
[0195] <Address>=[0x21-0xFF]--The newly assigned address of
the LRU
[0196] 0x20 offset+address value, MAX possible LRUs=222
[0197] <Device ID>=[0x41-0x43]--The LRU type.
[0198] [0x41]=9100 Direct Lights (W+A)
[0199] [0x42]=9150 Cross-Bin Wash Lights (W+A)
[0200] [0x42]=9150 OS Wash Light (W+A)
[0201] [0x43]=9200 Ceiling Wash Lights (RGB+W)
[0202] [0x43]=9200 Sidewall Wash Lights (RGB+W)
[0203] [0x4]=9200 Cove Wash Light (RGB+W)
[0204] [0x43]=9250 Over-Wing Exit Wash Lights (RGB+WW)
[0205] <Serial #>=20 ASCII bytes denoting LRU Serial Number
(Stored in LRU non-volatile memory)
[0206] <Hardware Rev>=20 ASCII bytes denoting LRU Hardware
Rev (Stored in LRU non-volatile memory)
[0207] <Firmware Rev>=20 ASCII bytes denoting LRU Firmware
Rev Number (Stored in LRU non-volatile memory)
[0208] Protocol--Pass Token Command
[0209] Specifications
[0210] Source Device: ACP
[0211] Destination Device Lighting LRUs
[0212] <Addressing Complete>=0x31 when the last washlight is
being addressed.
[0213] Protocol:
TABLE-US-00015 Command Format <DEST <XOR <SOT> MODE>
<DEST> <CMD> <DATA> CHECKSUM> <EOT>
Bytes 1 1 1 1 1 2 1 Data 0x01 0x30-0x32 0x20-0xFF CMD DATA ASCII
XOR 0x04 XSUM
[0214] CMD Set Description
[0215] <SOT>=[0x01]--Start of Transmission Character
[0216] <EOT>=[0x04]--End of Transmission Character
[0217] Pass Token Command:
[0218] <DEST MODE>=[0x32]--The destination mode selection
byte
[0219] 0x32=Address Message
[0220] <DEST>=[0x20-0xFF]--The Destination Address.
[0221] <DEST MODE>=0x32:
[0222] <DEST>=[0x21-0xFF] 0x20 offset+address, MAX possible
LRUs=222
[0223] <CMD>=[0x11]--This command tells the washlights to
pass the token
[0224] <DATA>=<Addressing Complete>
[0225] <Addressing Complete>=1 byte indicating that
addressing is complete
[0226] [0x30]=Addressing is not complete
[0227] [0x31]=Addressing is complete.
[0228] Example Message Format
TABLE-US-00016 ACP sends: Byte 1: 0x01 Byte 2: 0x10 Byte 3: 0x21
Byte 4: 0x33 Byte 5: 0x35 Byte 6: 0x36 Byte 7: 0x04 Washlight
Responds: Byte 1: 0x01 Byte 2: 0x1F Byte 3: 0x21 Byte 4: 0x41 Byte
5-24: 0x30, 0x30, 0x30, 0x30, 0x30, 0x30, 0x30, 0x30, 0x30, 0x30,
0x30, 0x30, 0x30, 0x30, 0x30, 0x30, 0x30, 0x30, 0x30, 0x30 Byte
25-44: 0x30, 0x30, 0x30, 0x30, 0x30, 0x30, 0x30, 0x30, 0x30, 0x30,
0x30, 0x30, 0x30, 0x30, 0x30, 0x30, 0x30, 0x30, 0x30, 0x30 Byte
45-64: 0x30, 0x30, 0x30, 0x30, 0x30, 0x30, 0x30, 0x30, 0x30, 0x30,
0x30, 0x30, 0x30, 0x30, 0x30, 0x30, 0x30, 0x30, 0x30, 0x30 Byte 65:
0x32 Byte 66: 0x42 Byte 67: 0x04 ACP sends Pass Token Command: Byte
1: 0x01 Byte 2: 0x11 Byte 3: 0x30 Byte 4: 0x30 Byte 5: 0x34 Byte 6:
0x35 Byte 7: 0x04
Bit Bite Operation
[0229] The ACP can control when BIT/BITE is initiated. The ACP can
use, e.g., the RS485 line to poll each washlight in the system to
determine if the washlight is still active. In addition to polling
each LRU, when a washlight receives a BIT request, this sets the
light intensity and colors to a specific level which provide visual
lamp test functionality. All BIT/BITE requests should be processed
and acknowledged from the lighting LRUs within 50 ms.
[0230] Protocol--Bit/Bite Request Message
[0231] Specifications
[0232] Source Device: ACP
[0233] Destination Device Lighting LRUs [0234] 1) Receipt of a
Scene Selection Message cancels/terminates any BIT/BITE mode that
may be in progress. [0235] 2) The lighting assemblies ignore
BIT/BITE messages while downloading scenes, or addressing is taking
place. [0236] 3) The ACP polls each LRU by setting the <DEST
MODE>=0x32 and <DEST> to the destination address of the
lighting LRU currently being polled.
[0237] Protocol
TABLE-US-00017 Command Format <SOT> <DEST MODE>
<DEST> <CMD> <XOR CHECKSUM> <EOT> Bytes 1 1
1 1 2 1 Data 0x01 0x30-0x32 0x20-0xFF 0x30 ASCII XOR 0x04 XSUM
[0238] CMD Set Description
[0239] <SOT>=0x01--Start of Transmission Character
[0240] <EOT>=0x04--End of Transmission Character
[0241] <DEST MODE>=[0x30-0x32]--The destination mode
selection byte
[0242] 0x30=Broadcast Message
[0243] 0x31=Group/Zone Message
[0244] 0x32=Address Message
[0245] <DEST>=[0x30-0xFF]--The Destination Address.
[0246] <DEST MODE>=0x30:
[0247] <DEST>=[0x30]--Don't Care
[0248] <DEST MODE>=0x31:
[0249] <DEST>=[0x31-0xFF]--The zone selection
[0250] <DEST MODE>=0x32:
[0251] <DEST>=[0x21-0xFF] 0x20 offset+address value, MAX
possible LRUs=222
[0252] <CMD>=0x30
[0253] Protocol--Bit/Bite ACK Message
[0254] Specifications
[0255] Source Device: Addressed Lighting LRU
[0256] Destination Device: ACP [0257] 1) If the <DEST
MODE>=0x32 of the BIT/BITE Request message, the LRU responds
with the BIT/BITE ACK message immediately upon receipt of the
BIT/BITE Request message, if the <DEST> of the request
matches the address of the lighting assembly. [0258] 2) The ACP
should receive a BIT/BIT ACK message within 50 ms of sending the
BIT/BITE request message. [0259] 3) If the <DEST MODE>=0x30
of the BIT/BITE Request message, the lighting assemblies each
respond with the BIT/BITE ACK message after delaying for an
interval of 50 milliseconds. Note that the LRU address can be used
as a seed value to determine the length of time each LRU will wait
before transmitting its BIT/BITE ACK message. [0260] 4) If the
<DEST MODE>=0x31 of the BIT/BITE Request message, the
lighting assemblies each respond with the BIT/BITE ACK message
after delaying for an interval of 50 milliseconds. Note that the
LRU address can be used as a seed value to determine the length of
time each LRU will wait before transmitting its BIT/BITE ACK
message. [0261] 5) The ACP should compare the information returned
in the BIT/BITE ACK Message to its internal database, in order to
ascertain that the information in the lighting assembly is correct.
Any discrepancy in returned information should alert the operator
to the problem.
[0262] Protocol:
TABLE-US-00018 Command Format <ACK SOT> <CMD>
<DATA> <XOR CHECKSUM> <EOT> Bytes 1 1 103 2 1
Data 0x06 CMD DATA ASCII XOR XSUM 0x04
[0263] CMD Set Description
[0264] <ACK SOT>=[0x06]--Start of Transmission Character for
ACK messages
[0265] <EOT>=[0x04]--End of Transmission Character
[0266] Address Response Message:
[0267] <CMD>=[0x3F]--This command is the acknowledgement
message from the washlight.
[0268] <DATA>=<Address><Device ID><Serial
#><Hardware Rev><Firmware Rev>
[0269] <B Scene Rev><User Scene Rev><Cal
Flag>
[0270] <Address>=[0x21-0xFF]--The newly assigned address of
the LRU
[0271] 0x20 offset+address value, MAX possible LRUs=222
[0272] <Device ID>=[0x41-0x43]--The LRU type.
[0273] [0x41]=9100 Direct Lights (W+A)
[0274] [0x42]=9150 Cross-Bin Wash Lights (W+A)
[0275] [0x42]=9150 COS Wash Light (W+A)
[0276] [0x43]=9200 Ceiling Wash Lights (RGB+W)
[0277] [0x43]=9200 Sidewall Wash Lights (RGB+W)
[0278] [0x4]=9200 Cove Wash Light (RGB+W)
[0279] [0x43]=9250 Over-Wing Exit Wash Lights (RGB+WW)
[0280] <Serial #>=20 ASCII bytes denoting LRU Serial Number
(Stored in LRU non-volatile memory)
[0281] <Hardware Rev>=20 ASCII bytes denoting LRU Hardware
Rev (Stored in LRU non-volatile memory)
[0282] <Firmware Rev>=20 ASCII bytes denoting LRU Firmware
Rev Number (Stored in LRU non-volatile memory)
[0283] <B Scene Rev>=20 ASCII bytes denoting LRU aircraft
Scenes P/N and Rev Number (Stored in LRU non-volatile memory)
[0284] <User Scene Rev>=20 ASCII bytes denoting LRU User
Scenes P/N and Rev Number (Stored in LRU non-volatile memory)
[0285] <Cal Flag>=1 byte indicating that the washlight is
calibrated
[0286] 0x30=Washlight is not calibrated
[0287] 0x31=Washlight is calibrated
Scene Download Operation
[0288] The Scene Download operation is used to update the locally
stored scenes on the lighting LRUs. The ACP controls when the Scene
Download Operation is initiated. The ACP can use the RS485 line to
help store the scene information into each washlight in the system.
The ACP first sends a SCENE DOWNLOAD REQUEST message to all
washlights in the system. This instructs the washlights to allow
protected EEPROM space to be altered. The ACP can then transmit the
SCENE CONTENT message for each scene. The scene content message
contains the scenes information one scene at a time.
[0289] Once all the new scenes have been transmitted, the ACP can
poll each washlight with a SCENE QUERY REQUEST message. The Scene
query message can ask the washlight if it has received all the
scenes. The washlight replies with a SCENE QUERY REPLY message
notifying the ACP it has received/not received all the information.
If the washlight has received the information, it should commit all
the scene information to non-volatile EEPROM. If the washlight
responds that it has not received all the information, the ACP
should retransmit the SCENE CONTENT message again to all the
washlights and resume re-querying the washlights.
[0290] All SCENE QUERY REQUEST messages should be processed and
acknowledged by the Lighting LRUs within 50 ms.
[0291] Protocol--Scene Download Request
[0292] Specifications
[0293] Source Device: ACP
[0294] Destination Device Lighting LRUs [0295] 1) The lighting
assemblies should ignore BIT/BITE messages while downloading
scenes, or addressing is taking place. [0296] 2) All other scene
download commands should be ignored unless the scene download
request is transmitted. [0297] 3) The scene download request may be
a broadcast message. Every lighting LRU receives this message.
[0298] Protocol
TABLE-US-00019 Command Format <DEST <XOR <SOT> MODE>
<DEST> <CMD> <DATA> CHECKSUM> <EOT>
Bytes 1 1 1 1 22 2 1 Data 0x01 0x30-0x32 0x20-0xFF CMD DATA ASCII
XOR 0x04 XSUM
[0299] CMD Set Description
[0300] <SOT>=0x01--Start of Transmission Character
[0301] <EOT>=0x04--End of Transmission Character
[0302] <DEST MODE>=[0x30]--The destination mode selection
byte
[0303] 0x30=Broadcast Message
[0304] <DEST>=[0x30]--The Destination Address.
[0305] <DEST MODE>=0x30:
[0306] <DEST>=[0x30]--Don't Care
[0307] <CMD>=0x50
[0308] <DATA>=<User Scene Rev><Total Scenes
Num><Empty>
[0309] <User Scene Rev>=20 ASCII bytes denoting LRU User
Scenes P/N and Rev Number (Stored in LRU non-volatile memory)
[0310] <Total Scenes Num>=[0x31-0x40]--The total number of
scenes to be updated from 1 (0x31) to 16 (0x40).
[0311] <Empty>=0x30
[0312] Protocol--SCENE CONTENT MESSAGE
[0313] Specifications
[0314] Source Device: ACP
[0315] Destination Device Lighting LRUs
[0316] The scene content message may be a broadcast message. Every
lighting LRU should receive this message.
[0317] Protocol
TABLE-US-00020 Command Format <DEST <XOR <SOT> MODE>
<DEST> <CMD> <DATA> CHECKSUM> <EOT>
Bytes 1 1 1 1 16 2 1 Data 0x01 0x30-0x32 0x20-0xFF CMD DATA ASCII
XOR 0x04 XSUM
[0318] CMD Set Description
[0319] <SOT>=0x01--Start of Transmission Character
[0320] <EOT>=0x04--End of Transmission Character
[0321] <DEST MODE>=[0x30]--The destination mode selection
byte
[0322] 0x30=Broadcast Message
[0323] <DEST>=[0x30]--The Destination Address.
[0324] <DEST MODE>=0x30:
[0325] <DEST>=[0x30]--Don't Care
[0326] <CMD>=0x51
[0327] <DATA>=S1, R1, R2, G1, G2, B1, B2, W1, W2, E1, E2, A1,
A2, T1, T2
[0328] S1=[0x31-45]--Scene Selection byte. Denotes LRU stored scene
information 0x30 offset+4 bit scene number. 16 scenes max.
[0329] Rx--The Red intensity value is 12 bits wide and split into 2
bytes, R1 and R2.
[0330] R1=0x40 offset+Most Significant 6 of 12 bits (RED)
[0331] R2=0x40 offset+Least Significant 6 of 12 bits (RED)
[0332] Gx--The Green intensity value is 12 bits wide and split into
2 bytes, G1 and G2. G1=0x40 offset+Most Significant 6 of 12 bits
(GREEN)
[0333] G2=0x40 offset+Least Significant 6 of 12 bits (GREEN)
[0334] Bx=The Blue intensity value is 12 bits wide and split into 2
bytes, B1 and B2.
[0335] B1=0x40 offset+Most Significant 6 of 12 bits (BLUE)
[0336] B2=0x40 offset+Least Significant 6 of 12 bits (BLUE)
[0337] Wx=The White intensity value (RGB+W Washlights) is 12 bits
wide and split into 2 bytes, W1 and W2
[0338] W1=0x40 offset+Most Significant 6 of 12 bits (WHITE)
[0339] W2=0x40 offset+Least Significant 6 of 12 bits (WHITE)
[0340] Ex=The White intensity value (W+A Washlights) is 12 bits
wide and split into 2 bytes, E1 and E2
[0341] E1=0x40 offset+Most Significant 6 of 12 bits (WHITE)
[0342] E2=0x40 offset+Least Significant 6 of 12 bits (WHITE)
[0343] Ax=The Amber intensity value is 12 bits wide and split into
2 bytes, A1 and A2
[0344] A1=0x40 offset+Most Significant 6 of 12 bits (AMBER)
[0345] A2=0x40 offset+Least Significant 6 of 12 bits (AMBER)
[0346] Tx--The scene transition time represents the number of
seconds the scene will be transitioning. It is a 12 bit wide value
and split into 2 bytes, T1 and T2.
[0347] T1=0x40 offset+Most Significant 6 of 12 bits
[0348] T2=0x40 offset+Least Significant 6 of 12 bits
[0349] Protocol--Scene Query Request
[0350] Specifications
[0351] Source Device: ACP
[0352] Destination Device: Lighting LRUs [0353] 1) After receiving
the Scene Query Request message, lighting assemblies may resume
normal operation [0354] 2) The ACP can poll each LRU by setting the
<DEST MODE>=0x32 and <DEST> to the destination address
of the lighting LRU currently being polled. [0355] 3) Each lighting
LRU should be queried.
[0356] Protocol
TABLE-US-00021 Command Format <SOT> <DEST MODE>
<DEST> <CMD> <XOR CHECKSUM> <EOT> Bytes 1 1
1 1 2 1 Data 0x01 0x30-0x32 0x20-0xFF CMD ASCII XOR 0x04 XSUM
[0357] CMD Set Description
[0358] <SOT>=0x01--Start of Transmission Character
[0359] <EOT>=0x04--End of Transmission Character
[0360] <DEST MODE>=[0x32]--The destination mode selection
byte
[0361] 0x32=Address Message
[0362] <DEST>=The Destination Address.
[0363] <DEST>=[0x21-0xFF] 0x20 offset+address, MAX possible
LRUs=222
[0364] <CMD>=0x52
[0365] Protocol--Scene Query Reply
[0366] Specifications
[0367] Source Device: Addressed Lighting LRU
[0368] Destination Device: ACP [0369] 1) The ACP should receive a
Scene Query Reply message within 50 ms of sending the Scene Query
Request message. [0370] 2) If a lighting LRU does not respond to
the Scene Query Request, the ACP should alert the operator to the
problem. [0371] 3) The ACP should compare the information returned
in the Scene Query Reply Message to its internal database, in order
to ascertain that the correct information is stored in the lighting
assembly. Any discrepancy in returned information should alert the
operator to the problem.
[0372] Protocol:
TABLE-US-00022 Command Format <ACK <XOR SOT> <CMD>
<DATA> CHECKSUM> <EOT> Bytes 1 1 41 2 1 Data 0x06
CMD DATA ASCII XOR 0x04 XSUM
[0373] CMD Set Description
[0374] <ACK SOT>=[0x06]--Start of Transmission Character for
Ack messages.
[0375] <EOT>=[0x04]--End of Transmission Character
[0376] Scene Query Reply Message:
[0377] <CMD>=[0x5F]--This command is the acknowledgement
message from the washlight.
[0378] <DATA>=<Address><B Scene Rev><User
Scene Rev>
[0379] <Address>=[0x21-0xFF]--The address of the queried
washlight
[0380] 0x20 offset+address value, MAX possible LRUs=222
[0381] <B Scene Rev>=20 ASCII bytes denoting LRU aircraft
Scenes P/N and Rev Number (Stored in LRU non-volatile memory)
[0382] <User Scene Rev>=20 ASCII bytes denoting LRU User
Scenes P/N and Rev Number (Stored in LRU non-volatile memory)
Scene Configuration Database
[0383] The Scene configuration database is the file which stores
the information on custom lighting scenes. This database may be
generated externally using a Cabin Lighting Designer program. The
database comprises, e.g., the 16 scene content messages separated
by ASCII carriage return line feeds.
[0384] Database File Format:
[0385]
<SOT><SCENE1><CR><LF><SCENE2><CR&g-
t;<LF><SCENE3><CR><LF><SCENE4><CR><-
LF>
[0386]
<SCENE5><CR><LF><SCENE6><CR><LF>-
;<SCENE7><CR><LF><SCENE8><CR><LF>
[0387]
<SCENE9><CR><LF><SCENE10><CR><LF&g-
t;<SCENE11><CR><LF><SCENE12><CR><LF>
[0388]
<SCENE13><CR><LF><SCENE14><CR><LF&-
gt;<SCENE15><CR><LF><SCENE16><CR><LF>
[0389] <XSUM>
TABLE-US-00023 Name Bytes Description <SOT> 1 Start of
Transmit: 0x01 <CR> 1 ASCII Carriage Return <LF> 1
ASCII Line Feed <XSUM> 2 XOR checksum. The XSUM is identical
to the communication protocol<SCENEX> =
TABLE-US-00024 Command Format <DEST <XOR <SOT> MODE>
<DEST> <CMD> <DATA> CHECKSUM> <EOT>
Bytes 1 1 1 1 16 2 1 Data 0x01 0x30-0x32 0x20-0xFF CMD DATA ASCII
XOR 0x04 XSUM
[0390] CMD Set Description
[0391] <SOT>=0x01--Start of Transmission Character
[0392] <EOT>=0x04--End of Transmission Character
[0393] <DEST MODE>=[0x30]--The destination mode selection
byte
[0394] 0x30=Broadcast Message
[0395] <DEST>=[0x30]--The Destination Address.
[0396] <DEST MODE>=0x30:
[0397] <DEST>=[0x30]--Don't Care
[0398] <CMD>=0x51
[0399] <DATA>=S1, R1, R2, G1, G2, B1, B2, W1, W2, E1, E2, A1,
A2, T1, T2
[0400] S1=[0x30-3F]--Scene Selection byte. Denotes LRU stored scene
information 0x30 offset+4 bit scene number. 16 scenes max.
[0401] Rx--The Red intensity value is 12 bits wide and split into 2
bytes, R1 and R2.
[0402] R1=0x40 offset+Most Significant 6 of 12 bits (RED)
[0403] R2=0x40 offset+Least Significant 6 of 12 bits (RED)
[0404] Gx--The Green intensity value is 12 bits wide and split into
2 bytes, G1 and G2. G1=0x40 offset+Most Significant 6 of 12 bits
(GREEN)
[0405] G2=0x40 offset+Least Significant 6 of 12 bits (GREEN)
[0406] Bx=The Blue intensity value is 12 bits wide and split into 2
bytes, B1 and B2.
[0407] B1=0x40 offset+Most Significant 6 of 12 bits (BLUE)
B2=0x40 offset+Least Significant 6 of 12 bits (BLUE)
[0408] Wx=The White intensity value (RGB+W Washlights) is 12 bits
wide and split into 2 bytes, W1 and W2
[0409] W1=0x40 offset+Most Significant 6 of 12 bits (WHITE)
[0410] W2=0x40 offset+Least Significant 6 of 12 bits (WHITE)
[0411] Ex=The White intensity value (W+A Washlights) is 12 bits
wide and split into 2 bytes, E1 and E2
[0412] E1=0x40 offset+Most Significant 6 of 12 bits (WHITE)
[0413] E2=0x40 offset+Least Significant 6 of 12 bits (WHITE)
[0414] Ax=The Amber intensity value is 12 bits wide and split into
2 bytes, A1 and A2
[0415] A1=0x40 offset+Most Significant 6 of 12 bits (AMBER)
[0416] A2=0x40 offset+Least Significant 6 of 12 bits (AMBER)
[0417] Tx--The scene transition time represents the number of
seconds the scene is transitioning. It is a 12 bit wide value and
split into 2 bytes, T1 and T2.
[0418] T1=0x40 offset+Most Significant 6 of 12 bits
[0419] T2=0x40 offset+Least Significant 6 of 12 bits
Lighting LOPA Configuration Database
[0420] The lighting LOPA configuration database helps to configure
the exact light layout on the aircraft. It can contain the
descriptions for each lighting LRU, station location as well as
firmware/hardware and database revision information. The database
file format may comprise multiple device types ( ) separated by an
ASCII carriage return and line feed. The ACP can check the validity
of the database with the XSUM calculation at the end of the
file.
[0421] Database File Format:
[0422]
<SOT><DEVICE1><CR><LF><DEVICE2><CR-
><LF><DEVICE3><CR><LF><DEVICE4><CR>-
<LF>
[0423]
<DEVICE5><CR><LF><DEVICE6><CR><LF&-
gt;<DEVICE7><CR><LF> . . .
<DEVICEX><CR><LF>
[0424] <XSUM>
[0425] <SOT>=0x01
[0426] <CR>=ASCII Carriage Return
[0427] <LF>=ASCII Line Feed
[0428] <XSUM>=2 byte XOR XSUM. The XSUM is identical to the
communication protocol
[0429] <DEVICEX>=<Device Type><Device
Address><Comm Port><STA LOC><Device
Description>
TABLE-US-00025 Name Bytes Description <Device 1 The Device Type:
Type> [0x41] = 9100 Direct Lights (W + A) [0x42] = 9150
Cross-Bin Wash Lights (W + A) [0x42] = 9150 COS Wash Light (W + A)
[0x43] = 9200 Ceiling Wash Lights (RGB + W) [0x43] = 9200 Sidewall
Wash Lights (RGB + W) [0x43] = 9200 Cove Wash Light (RGB + W)
[0x43] = 9250 Over-Wing Exit Wash Lights (RGB + WW) <Device 1
The Device Address: [0x21-0xFF] Address> <Comm 1 The Comm
port this Device is on: Port> [0x01] = Comm Port 1 [0x02] = Comm
Port 2 [0x03] = Comm Port 3 [0x04] = Comm Port 4 [0x05] = Comm Port
5 <STA LOC> 5 The ASCII String Description of the Station
location with leading zeros <Dev 40 The ASCII String Description
of the LRU with Description> leading spaces
System Power-Up
[0430] Upon system power up, each LRU can wait for 30 seconds to
receive a Scene Selection Message. If none is received within that
time period, the LRU should automatically transition to 100% White
light or some other default setting.
[0431] Although the above has been described for use as lighting
within an aircraft the invention is not limited and can apply to
other applications as well. The term "aircraft" as used herein is
to be understood as a proxy for any passenger vehicle or any
illuminated area. Similarly, the term LED or light-emitting diode
is to be understood as a proxy for any illumination source that can
be controllable in a manner similar to that described herein.
[0432] The system or systems may be implemented on any general
purpose computer or computers and the components may be implemented
as dedicated applications or in client-server architectures,
including a web-based architecture. Any of the computers may
comprise a processor, a memory for storing program data and
executing it, a permanent storage such as a disk drive, a
communications port for handling communications with external
devices, and user interface devices, including a display, keyboard,
mouse, etc. When software modules are involved, these software
modules may be stored as program instructions executable on the
processor on media such as tape, CD-ROM, etc., where this media can
be read by the computer, stored in the memory, and executed by the
processor.
[0433] For the purposes of promoting an understanding of the
principles of the invention, reference has been made to the
preferred embodiments illustrated in the drawings, and specific
language has been used to describe these embodiments. However, no
limitation of the scope of the invention is intended by this
specific language, and the invention should be construed to
encompass all embodiments that would normally occur to one of
ordinary skill in the art.
[0434] The present invention may be described in terms of
functional block components and various processing steps. Such
functional blocks may be realized by any number of hardware and/or
software components configured to perform the specified functions.
For example, the present invention may employ various integrated
circuit components, e.g., memory elements, processing elements,
logic elements, look-up tables, and the like, which may carry out a
variety of functions under the control of one or more
microprocessors or other control devices. Similarly, where the
elements of the present invention are implemented using software
programming or software elements the invention may be implemented
with any programming or scripting language such as C, C++, Java,
assembler, or the like, with the various algorithms being
implemented with any combination of data structures, objects,
processes, routines or other programming elements. Furthermore, the
present invention could employ any number of conventional
techniques for electronics configuration, signal processing and/or
control, data processing and the like. The word mechanism is used
broadly and is not limited to mechanical or physical embodiments,
but can include software routines in conjunction with processors,
etc.
[0435] The particular implementations shown and described herein
are illustrative examples of the invention and are not intended to
otherwise limit the scope of the invention in any way. For the sake
of brevity, conventional electronics, control systems, software
development and other functional aspects of the systems (and
components of the individual operating components of the systems)
may not be described in detail. Furthermore, the connecting lines,
or connectors shown in the various figures presented are intended
to represent exemplary functional relationships and/or physical or
logical couplings between the various elements. It should be noted
that many alternative or additional functional relationships,
physical connections or logical connections may be present in a
practical device. Moreover, no item or component is essential to
the practice of the invention unless the element is specifically
described as "essential" or "critical".
[0436] The use of the terms "a" and "an" and "the" and similar
referents in the context of describing the invention (especially in
the context of the following claims) are to be construed to cover
both the singular and the plural. Furthermore, recitation of ranges
of values herein are merely intended to serve as a shorthand method
of referring individually to each separate value falling within the
range, unless otherwise indicated herein, and each separate value
is incorporated into the specification as if it were individually
recited herein. Finally, the steps of all methods described herein
can be performed in any suitable order unless otherwise indicated
herein or otherwise clearly contradicted by context.
[0437] Numerous modifications and adaptations will be readily
apparent to those skilled in this art without departing from the
spirit and scope of the present invention.
TABLE OF REFERENCE CHARACTERS
[0438] 10 aircraft lighting system [0439] 20 regional lighting
[0440] 30 aircraft lighting system controller [0441] 40 attendant
control panel (ACP) [0442] 60 intelligent lighting module group
[0443] 70 power supply [0444] 80 filter [0445] 90 module group
controller [0446] 110 module (master module) [0447] 110' slave
module [0448] 112 power plug assembly [0449] 114 terminating
connector [0450] 120 LED group [0451] 130 LED/illumination source
element
* * * * *