The invention relates generally to the field of automation control systems, such as those used in industrial and commercial settings. More particularly, embodiments of the present invention relate to techniques for providing, accessing, configuring, operating, or interfacing with input/output (I/O) devices that are configured for coupling and interaction with an automation controller.
Automation controllers are special purpose computers used for controlling industrial automation and the like. Under the direction of stored programs, a processor of the automation controller examines a series of inputs (e.g., electrical input signals to the automation controller) reflecting the status of a controlled process and changes outputs (e.g., electrical output signals from the automation controller) based on analysis and logic for affecting control of the controlled process. The stored control programs may be continuously executed in a series of execution cycles, executed periodically, or executed based on events. The inputs received by the automation controller from the controlled process and the outputs transmitted by the automation controller to the controlled process are normally passed through one or more I/O devices, which are components of an automation control system that serve as an electrical interface between the automation controller and the controlled process.
Traditional I/O devices typically include a base configured to couple the I/O device with a bus bar or the like, a terminal block for communicatively coupling the I/O device with field devices, and an I/O module that includes circuitry for performing communication functions and/or logic operations. In operation, a traditional I/O device typically communicatively couples with field devices (e.g., sensors and actuators) via terminals of the terminal block such that the I/O device can receive input signals from the field devices and provide output signals to the field devices. In traditional automation control systems, status indicators relating to such input and output signals are typically located on a status display of the I/O module of the I/O device. This allows users to observe the status of aspects of the automation control system by viewing the indicators on the I/O module and correlating the indicators to related devices (e.g., sensors and actuators) based on where the devices attach to the terminal block. Specifically, for example, a correspondence between indicators and terminals may be identified based on address labels. However, these address labels can become obscured by wiring. It is now recognized that it is desirable to provide more efficient and effective techniques for providing status indications on an I/O device.
The present invention addresses shortcomings of traditional I/O devices by aligning status indicators on a terminal block of an I/O device with respective terminals on the terminal block. In certain embodiments, the status indicators are disposed directly adjacent to the respective terminals. For example, status indicators may be positioned above, below, to the left, and/or to the right of the terminals such that there is a direct physical correspondence between the terminals and corresponding indicators. In other embodiments, the status indicators include transparent or translucent portions on a face of the terminal block surrounding terminal points, such that the status indicators are integrated directly within the associated terminals. In certain embodiments, each terminal is associated with more than one status indicator, with each status indicator being disposed adjacent to or integrated directly within the respective terminal.
The status indicators are illuminated by light emitters, such as light emitting diodes (LEDs), that are disposed within a housing of the I/O device. It should be noted that while LEDs are utilized as an example throughout the following discussion, LEDs are merely representative of one embodiment of light emitters that may be utilized in accordance with present techniques. Light pipes, which are also disposed within the housing of the I/O device, function to direct light from the LEDs to the status indicators. In certain embodiments, each of the light pipes is configured to receive light from two or more LEDs and to direct the light to two or more of the status indicators. LED activation circuitry disposed within the housing determines a manner in which to activate the LEDs to illuminate the appropriate status indicators based on inputs and outputs received and transmitted between the I/O device and a controlled process.
In certain embodiments, the status indicators are disposed on a raised section of the terminal block from a front face of the terminal block. Indeed, the raised section may be part of a removable LED indication assembly, which may include the LEDs, light pipes, LED activation circuitry, and other active decision-making elements, and may be removed and inserted into the housing of the terminal block as needed. Furthermore, in certain embodiments, both the raised section and the front face may be sloped to facilitate management of wires connected to the terminal points.
These and other features, aspects, and advantages of the present invention will become better understood when the following detailed description is read with reference to the accompanying drawings in which like characters represent like parts throughout the drawings, wherein:
The process 16 may take many forms and include devices for accomplishing many different and varied purposes. For example, the process 16 may comprise a compressor station, an oil refinery, a batch operation for making food items, a mechanized assembly line, and so forth. Accordingly, the process 16 may comprise a variety of operational components, such as electric motors, valves, actuators, temperature elements, pressure sensors, or a myriad of manufacturing, processing, material handling, and other applications. Further, the process 16 may comprise control and monitoring equipment for regulating process variables through automation and/or observation.
For example, the illustrated process 16 comprises sensors 18 and actuators 20. The sensors 18 may comprise any number of devices adapted to provide information regarding process conditions. The actuators 20 may include any number of devices adapted to perform a mechanical action in response to a signal from a controller (e.g., an automation controller). The sensors 18 and actuators 20 may be utilized to operate process equipment. Indeed, they may be utilized within process loops that are monitored and controlled by the control/monitoring device 14 and/or the HMI 12. Such a process loop may be activated based on process inputs (e.g., input from a sensor 18) or direct operator input received through the HMI 12.
As illustrated, the sensors 18 and actuators 20 are in communication with the control/monitoring device 14 and may be assigned a particular address in the control/monitoring device 14 that is accessible by the HMI 12. As illustrated, the sensors 18 and actuators 20 may communicate with the control/monitoring device 14 via one or more I/O devices 22 coupled to the control/monitoring device 14. The I/O devices 22 may transfer input and output signals between the control/monitoring device 14 and the controlled process 16. The I/O devices 22 may be integrated with the control/monitoring device 14, or may be added or removed via expansion slots, bays or other suitable mechanisms. For example, as described in greater detail below, additional I/O devices 22 may be added to add functionality to the control/monitoring device 14. Indeed, if new sensors 18 or actuators 20 are added to control the process 16, additional I/O devices 22 may be added to accommodate and incorporate the new features functionally with the control/monitoring device 14. The I/O devices 22 serve as an electrical interface to the control/monitoring device 14 and may be located proximate or remote from the control/monitoring device 14, including remote network interfaces to associated systems.
The I/O devices 22 may include input modules that receive signals from input devices such as photo-sensors and proximity switches, output modules that use output signals to energize relays or to start motors, and bidirectional I/O modules, such as motion control modules which can direct motion devices and receive position or speed feedback. In some embodiments, the I/O devices 22 may convert between AC and DC analog signals used by devices on a controlled machine or process and DC logic signals used by the control/monitoring device 14. Additionally, some of the I/O devices 22 may provide digital signals to digital I/O devices and receive digital signals from digital I/O devices. Further, in some embodiments, the I/O devices 22 that are used to control machine devices or process control devices may include local microcomputing capability on an I/O module of the I/O devices 22.
In some embodiments, the I/O devices 22 may be located in close proximity to a portion of the control equipment, and away from the remainder of the control/monitoring device 14. In such embodiments, data may be communicated with remote modules over a common communication link, or network, wherein modules on the network communicate via a standard communications protocol. Many industrial controllers can communicate via network technologies such as Ethernet (e.g., IEEE802.3, TCP/IP, UDP, EtherNet/IP, and so forth), ControlNet, DeviceNet or other network protocols (Foundation Fieldbus (H1 and Fast Ethernet) Modbus TCP, Profibus) and also communicate to higher level computing systems.
As also described in greater detail below, each of the I/O devices 22 includes a base 28 for physically and communicatively connecting the I/O device 22 to the DIN rail 26, the I/O adapter 24 and/or adjacent I/O devices 22. In addition, the base 28 of the I/O device 22 is configured to physically and communicatively connect the I/O device 22 with other I/O devices 22 via the DIN rail 26, field and system electrical contacts as described in greater detail below, base connection features as described in greater detail below, and so forth. In addition, each of the I/O devices 22 includes a terminal block 30 (which, in certain embodiments, may be removable from the base 28) for electrically connecting the I/O device 22 to field devices, such as the sensors 18 and actuators 20 illustrated in
As illustrated, the terminal block 30 includes eight terminals 34 (i.e., channels) for connecting field device wiring to the terminal block 30. Each of the terminals 34 is associated with a particular input to or output from a field device. As illustrated, each terminal 34 includes a terminal opening 36 into which a field wire electrically connected to a field device may be inserted, and an attachment activator (e.g., a terminal screw) 38, which when activated (e.g., tightened) causes a clamp or other electrical wiring connection mechanism within the terminal block 30 to tighten around an end of a field wire that has been inserted into the associated terminal opening 36. As illustrated, each of the terminals 34 terminates at the back of the terminal block 30 with a terminal block connector 40, which may be inserted into terminal block connector openings 42 in the front of a terminal block bay 44 of the base 28 to physically and communicatively connect the terminal block 30 with the base 28. In the illustrated embodiment, each of the terminal block connectors 40 include two opposing electrical prongs 46 that slide around and electrically connect with a single electrical prong (not shown) in the respective terminal block connector opening 42 of the terminal block bay 44 of the base 28. However, in other embodiments, other types of terminal block connectors 40 may be used to electrically connect with mating electrical connectors in the respective terminal block connector opening 42 of the terminal block bay 44 of the base 28.
The I/O module 32 may also be physically and communicatively connected to the base 28 by inserting the I/O module 32 into a mating slot 48 in an I/O module bay 50 of the base 28. When the I/O module 32 is inserted into the slot 48 in the I/O module bay 50 of the base 28, the I/O module 32 becomes electrically coupled to the terminals 34 of the terminal block 30 via internal circuitry within the base 28 that electrically connects the electrical prongs (or other suitable electrical connectors) in the terminal block connector openings 42 to respective electrical outlets 52 in the front of the I/O module bay 50 of the base 28. The electrical outlets 52 for each channel are in turn electrically coupled to the I/O module 32 via respective electrical connectors (not shown) that, in certain embodiments, extend from the back of the I/O module 32. As such, the terminal block 30, the base 28, and the I/O module 32 are all electrically and communicatively coupled together such that signals to and from the field device to which the I/O device 22 is connected are shared between the terminal block 30, the base 28, and the I/O module 32.
In addition, the I/O device 22 may also be electrically coupled to an I/O adapter 24 electrically upstream, and/or other I/O devices 22 electrically upstream or electrically downstream via electrical coupling features of the I/O device 22. In certain embodiments, components that are coupled electrically upstream of the I/O device 22 are components that are on a left side 54 of the I/O device 22 when viewing the I/O device 22 from the front, and components that are electrically coupled downstream of the I/O device 22 are components that are on a right side 56 of the I/O device 22 when viewing the I/O device 22 from the front. However, in other embodiments, the upstream and downstream electrical coupling features may be configured differently.
In certain embodiments, adjacent I/O devices 22 may be physically attached to each other via one or more connection features (e.g., slots) 58 of the base 28 on one of the sides (e.g., the left side 54 of the illustrated embodiment) of the I/O device 22 near the back of the base 28. Mating connection features such as protrusions (not shown) on the opposite side (e.g., the right side 56 of the illustrated embodiment) of the base 28 of the I/O device 22 near the back of the base 28. In certain embodiments, connection features of an I/O device 22 may slide into mating connection features of an adjacent I/O device 22, thereby physically attaching the adjacent I/O devices 22.
When adjacent I/O devices 22 are physically attached to each other, system electrical contacts 60 on the base 28 on one of the sides (e.g., the left side 54 of the illustrated embodiment) align with and are electrically coupled to mating electrical contacts (not shown) on the base 28 on the opposite side (e.g., the right side 56 of the illustrated embodiment) of an adjacent I/O device 22. Similarly, field electrical contacts 62 on the base 28 on one of the sides (e.g., the left side 54 of the illustrated embodiment) align with and are electrically coupled to mating electrical contacts (not shown) on the base 28 on the opposite side (e.g., the right side 56 of the illustrated embodiment) of an adjacent I/O device 22. In the illustrated embodiment, the I/O device 22 includes five system electrical contacts 60 and two field electrical contacts 62. In such an embodiment, system power may be electrically communicated via electrically connected I/O devices 22 and/or the I/O adapter 24 via two of the system electrical contacts 60, while the three other system electrical contacts 60 are used for transmission of data (e.g., relating to signals transmitted to and from the field devices to which the I/O devices 22 are electrically connected) between the electrically connected I/O devices 22 and the I/O adapter 24. In addition, the two field electrical contacts 62 are used to electrically communicate power to the field devices to which the I/O devices 22 are electrically connected. However, it will be understood that the specific number of system electrical contacts 60 and field electrical contacts 62 may vary between implementations depending on the requirements for power and data transmission of the I/O devices 22.
As illustrated, in certain embodiments, the I/O module 32 may include a status display 64 on the front face of the I/O module 32 for displaying operating status information of the I/O module 32, the base 28, and the terminal block 30. The status display 64 may, for example, include status light emitting diodes (LEDs) corresponding to each of the terminals 34 of the terminal block 30. In addition, as described in greater detail below, each of the terminals 34 of the terminal block 30 may be associated with one or more terminal status LED indicators 70 that are directly aligned with (e.g., located adjacent to or integrated directly within) their respective terminals 34. Further, in certain embodiments, once the terminal block 30 and the I/O module 32 are physically and communicatively connected to the base 28 of the I/O device 22, a latch 66 or other fastening device extending from the terminal block 30 may further attach the terminal block 30 to the I/O module 32, thereby providing additional structural support and stabilizing the electrical connections between the terminal block 30, the I/O module 32, and the base 28.
As described above, the status display 64 located on the front face of the I/O module 32, which displays operating status information for the I/O module 32, the base 28, and the terminal block 30 is often located on a front face of the I/O module 32.
More specifically, status indicators may be provided within or adjacent to the terminals 34 of the terminal block 30 of the I/O device 22. As illustrated in
In certain embodiments, and as described throughout herein, red terminal status LED indicators 70 indicate that there are issues with the respective terminals 34, whereas green terminal status LED indicators 70 indicate that there are no (or minimal) issues with the respective terminals 34. However, it will be understood that differently colored terminal status LED indicators 70 may also be used. Indeed, in certain embodiments, more than two colors may be used in the terminal status LED indicators 70, with each color indicating a more severe issue indicator, for example. Additionally, light emission intensity may be employed to provide status levels. As described in greater detail below, LEDs disposed within a housing of the terminal block 30 determine which colors or intensities are activated by the terminal status LED indicators 70. It should be noted that while LEDs are utilized as example light sources in the embodiments described herein, LEDs are merely representative of one type of light source that may be utilized to illuminate the status indicators in accordance with present techniques.
In addition to the I/O statuses of the terminals 34 that may be indicated by the terminal status LED indicators 70 within or adjacent to their respective terminals 34, a system I/O status or statuses of the I/O device 22 may be displayed on the terminal block 30 as well. For example, as illustrated in
For example, in certain embodiments, the device status LED indicator 72 may indicate an issue if a certain number of the terminal status LED indicators 70 indicate an issue. Specifically, for example, the device status LED indicator 72 illustrated in
As illustrated in
As with the embodiment illustrated in
As described above with respect to
As illustrated in
As illustrated in
Furthermore, the embodiments illustrated in
As with the embodiments described above, if there is an issue with the communication of input or output signals between the I/O device 22 and the field device to which the I/O device 22 is connected for any given terminal 34 (i.e., channel), the terminal status LED indicator 70, which is integrated directly into the terminal 34, will indicate the issue by displaying a different color than the terminal status LED indicators 70 for which the respective terminals 34 are operating with no (or minimal) issues. For example, as illustrated in
In addition, while the embodiments illustrated in
It should be noted that all of the features illustrated in
In certain embodiments, each of the LEDs 84 associated with the terminals 34 is associated with a bifurcated light pipe 88 for directing light from the LED 84 to the terminal points to illuminate the terminal status LED indicators 70, 76, 78 that are adjacent to or integrated within the terminals 34, as well as the device status LED indicators 72, which may be located on the terminal block 30 or on the respective I/O module 32 of the I/O device 22. In other words, the bifurcated light pipe 88 may be configured to direct the light to multiple locations depending on the particular configuration of the terminal block 30. For example, as illustrated in
Furthermore, in certain embodiments, the device indicator light pipe loop 96 may be configured to connect with light pipes in the I/O module 32 for directing light, for example, to the terminal status LED indicators 82 on the I/O module 32 illustrated in
As described above, each of the terminals 34 illustrated in
Regardless of the number of LEDs 84 that are associated with each terminal 34, each LED 84 is associated with a segmented, multi-component light pipe 88 for directing light from the LED 84 to its respective terminal point(s), such as the terminal status LED indicators 70, 76, 78 that are adjacent to or integrated within the terminals 34, the device status LED indicators 72 that may either be located on the terminal block 30 or on the respective I/O module 32 of the I/O device 22, and/or the terminal status LED indicators 82 located on the respective I/O module 32 of the I/O device 22. As such, each light pipe 88 is configured to transmit light from one or more inputs (i.e., the LEDs 84) to one or more outputs (e.g., the terminal status LED indicators 70, 76, 78, the device status LED indicators 72, and the terminal status LED indicators 82). For example, as illustrated in
As such, each light pipe 88 is multi-segmented, including light transmission path(s) having a plurality of discrete light pipe sections (e.g., the first and second light pipe segments 90, 94, the terminal indicator light pipe loop 92, the device indicator light pipe loop 96, and so forth). In addition, in certain embodiments, some of the light pipes 88 may include transmission enhancements that help distribute the light through the light pipe 88. For example, as illustrated in
It should also be noted that the embodiments described herein may apply to both removable terminal blocks 30 as well as terminal blocks 30 that are integrated with the base 28 of the I/O device 22. In other words, as described above, the LEDs 84 and the associated light pipes 88 for directing light to the terminal points (e.g., the terminal status LED indicators 70, 76, 78, the device status LED indicators 72, and the terminal status LED indicators 82) of the terminal block 30 and/or the respective I/O module 32 of the I/O device 22 may be disposed within the housing 86 of the terminal block 30. As such, the LEDs 84 and associated light pipes 88 remain integrated within the housing 86 of the terminal block 30 regardless of whether the terminal block 30 is a removable terminal block 30 or integrated with the base 28 of the I/O device 22. Furthermore, as described in greater detail below, the circuitry for activating the LEDs 84 may also be disposed within the housing 86 of the terminal block 30, enabling all of the LED indicator functionality to be modular with respect to the terminal block 30, regardless of whether the terminal block 30 is a removable terminal block 30 or integrated with the base 28 of the I/O device 22. In other embodiments, the circuitry for activating the LEDs 84 may be disposed within the base 28 or the I/O module 32 of the I/O device 22. For example, as described in greater detail below, in certain embodiments, the I/O module 32 may include the LEDs 84 and the associated light pipes 88 for directing light to the terminal points (e.g., the terminal status LED indicators 70, 76, 78, the device status LED indicators 72, and the terminal status LED indicators 82) of the respective terminal block 30 and/or the I/O module 32.
The LEDs 84 that are embedded within the housing 86 of the terminal block 30 may be controlled to enable active LED control of the terminal status LED indicators 70, 76, 78, the device status LED indicators 72, and the terminal status LED indicators 82 described herein. In other words, instead of simply passively passing through signals between the I/O module 22 and the associated field device to activate the LEDs 84 (e.g., by varying the LED brilliance proportional to an on state current of the field device, or simply illuminating the LED 84 based on the presence or absence of a signal), LED activation circuitry 100 disposed within the housing 86 of the terminal block 30 actively determines a manner in which to activate the LEDs 84 that are also disposed within the housing 86 of the terminal block 30. For example, the LED activation circuitry 100 may receive I/O signals transmitted between the I/O device 22 and the associated field device (e.g., through the wires connected to the terminals 34 and the field device), and actively determine how the LEDs 84 should be activated based on the I/O signals. For example, in certain embodiments, the LED activation circuitry 100 may include a processor that executes software stored on a local memory of the LED activation circuitry 100 to determine how to activate the LEDs 84 based on the I/O signals. However, in other embodiments, the LED activation circuitry 100 may include hardware, such as switches, configured to convert the I/O signals into appropriate activation signals that are used to activate the LEDs 84.
Furthermore, because the LEDs 84 are controlled by the LED activation circuitry 100, the information conveyed by the terminal status LED indicators 70, 76, 78, the device status LED indicators 72, and the terminal status LED indicators 82 that are illuminated by the LEDs 84 may vary depending on the specific needs of the terminal block 30, the associated I/O module 32, and/or the I/O device 22 as a whole. For example, the information conveyed by the LEDs 84 may include fault states, on/off states, and so forth. In addition, because of the active transmission of information from the LED activation circuitry 100, in certain embodiments, the LEDs 84 may be multi-color, multi-state (e.g., flashing), and so forth, to convey various levels of frequency of issues, severity of issues, and other information. Moreover, in certain embodiments, the LED activation circuitry 100 may be configured to enable activation of the LEDs 84 to indicate statuses without the field device actually being powered on. Furthermore, the transmission of information from the LED activation circuitry 100 may be via direct connection, wireless, optical, and so forth.
As described above, the terminal status LED indicators 70, 76, 78 are all located proximate to (e.g., adjacent to or directly integrated within) the terminals 34 (i.e., channels) with which the terminal status LED indicators 70, 76, 78 are associated. Additionally, in certain embodiments, the I/O module 32 may include a raised section extending from a lateral side of the I/O module 32. For example,
As also illustrated in
Having the terminal status LED indicators 70 disposed in such a non-orthogonal geometry (e.g., disposed at a vertical distance above the terminal block 30) enables the field wires that are connected to the terminals 34 to be routed between raised sections 102 of adjacent I/O modules 32 without obstructing the view of the terminal status LED indicators 70. In addition, in certain embodiments, the terminal block 30 and/or the raised section 102 may include sloped profiles to further enhance visibility of the terminal status LED indicators 70 as well as facilitate management of the field wires that are connected to the terminals 34. For example,
Returning now to
For example,
In certain embodiments, each of the removable LED indication assemblies 104 may be configured to indicate different levels of diagnostic information. For example, one LED indication assembly 104 may be configured to provide basic status information, such as fault states and connection statuses, whereas another LED indication assembly 104 may be configured to provide basic status information, such as fault states and connection statuses, as well as fault types and causes, measured values, and so forth. Therefore, the removable LED indication assemblies 104 enable various levels of diagnostic troubleshooting without the need to remove the terminal block 30 and/or the field wiring connected to the terminals 34 of the terminal block 30. In certain embodiments, the removable LED indication assemblies 104 may be attached directly to other circuitry within the terminal block 30 and/or the I/O module 32 when inserted into the I/O module 32. However, in other embodiments, the removable LED indication assemblies 104 may communicate with other circuitry within the terminal block 30 and/or the I/O module 32 via wireless data transmission. When wireless data transmission is used, the removable LED indication assemblies 104 may actually be located at other locations remote from their respective I/O module 32 (e.g., in a panel door). As such, the pluggable nature of the removable LED indication assemblies 104 enables a modular design for diagnostics and troubleshooting of the I/O devices 22 described herein.
While only certain features of the invention have been illustrated and described herein, many modifications and changes will occur to those skilled in the art. It is, therefore, to be understood that the appended claims are intended to cover all such modifications and changes as fall within the true spirit of the invention.
This application claims priority of U.S. Provisional Patent Application No. 61/375,587, filed Aug. 20, 2010, which is herein incorporated in its entirety by reference, and of U.S. Provisional Patent Application No. 61/379,894, filed Sep. 3, 2010, which is herein incorporated in its entirety by reference.
Number | Name | Date | Kind |
---|---|---|---|
4038641 | Bouknecht et al. | Jul 1977 | A |
4038642 | Bouknecht et al. | Jul 1977 | A |
4053950 | Bourke et al. | Oct 1977 | A |
4144565 | Bouknecht et al. | Mar 1979 | A |
4217624 | Tuck | Aug 1980 | A |
4833589 | Oshiga et al. | May 1989 | A |
4868669 | Miyazawa | Sep 1989 | A |
5483229 | Tamura et al. | Jan 1996 | A |
5611057 | Pecone et al. | Mar 1997 | A |
5678084 | Hori | Oct 1997 | A |
5716241 | Hennemann et al. | Feb 1998 | A |
5790374 | Wong | Aug 1998 | A |
5912710 | Fujimoto | Jun 1999 | A |
5968146 | Tanaka et al. | Oct 1999 | A |
6027379 | Hohorst | Feb 2000 | A |
6172875 | Suzuki et al. | Jan 2001 | B1 |
6283786 | Margulis et al. | Sep 2001 | B1 |
6425770 | Lostoski et al. | Jul 2002 | B1 |
6446202 | Krivoshein et al. | Sep 2002 | B1 |
6449715 | Krivoshein | Sep 2002 | B1 |
6502956 | Wu | Jan 2003 | B1 |
6621692 | Johnson et al. | Sep 2003 | B1 |
6692132 | Meeker | Feb 2004 | B1 |
6736678 | Yao | May 2004 | B2 |
6738261 | Vier et al. | May 2004 | B2 |
6763398 | Brant et al. | Jul 2004 | B2 |
6775791 | McAfee | Aug 2004 | B2 |
6802737 | Bergner et al. | Oct 2004 | B2 |
6815625 | Leopold et al. | Nov 2004 | B1 |
6862174 | Chien et al. | Mar 2005 | B2 |
6980122 | Novikov | Dec 2005 | B2 |
7297019 | Landis et al. | Nov 2007 | B2 |
7429188 | Wu | Sep 2008 | B2 |
7553044 | Wedell | Jun 2009 | B2 |
7555642 | Gagneraud et al. | Jun 2009 | B2 |
7581053 | Sichner et al. | Aug 2009 | B2 |
7676640 | Chow et al. | Mar 2010 | B2 |
7702831 | Ma et al. | Apr 2010 | B2 |
7952887 | Kosugi et al. | May 2011 | B2 |
8073985 | Ni et al. | Dec 2011 | B1 |
8092060 | Osada | Jan 2012 | B2 |
8174835 | Kim et al. | May 2012 | B2 |
8199511 | Kim et al. | Jun 2012 | B2 |
8274230 | Chiu | Sep 2012 | B2 |
8410364 | Dunwoody et al. | Apr 2013 | B2 |
8411440 | Dunwoody et al. | Apr 2013 | B2 |
8441792 | Dunwoody et al. | May 2013 | B2 |
8493718 | Zhang | Jul 2013 | B2 |
8503183 | Hamilton et al. | Aug 2013 | B2 |
8514585 | Zhang et al. | Aug 2013 | B2 |
8520401 | Tian et al. | Aug 2013 | B2 |
20010047442 | Oomori | Nov 2001 | A1 |
20020072256 | Lostoski et al. | Jun 2002 | A1 |
20020081890 | Obermaier | Jun 2002 | A1 |
20020132504 | Mori et al. | Sep 2002 | A1 |
20030051098 | Brant et al. | Mar 2003 | A1 |
20040206616 | Leopold et al. | Oct 2004 | A1 |
20040207342 | Novikov | Oct 2004 | A1 |
20040207343 | Novikov | Oct 2004 | A1 |
20050040424 | Erchak et al. | Feb 2005 | A1 |
20050051785 | Erchak et al. | Mar 2005 | A1 |
20050059178 | Erchak et al. | Mar 2005 | A1 |
20050059179 | Erchak et al. | Mar 2005 | A1 |
20050063647 | Thornton et al. | Mar 2005 | A1 |
20050127375 | Erchak et al. | Jun 2005 | A1 |
20050219033 | Bortolloni et al. | Oct 2005 | A1 |
20050260884 | Yueh | Nov 2005 | A1 |
20060043391 | Erchak et al. | Mar 2006 | A1 |
20060250210 | Dowil et al. | Nov 2006 | A1 |
20060250223 | Koga et al. | Nov 2006 | A1 |
20070081315 | Mondor et al. | Apr 2007 | A1 |
20070112982 | Sichner et al. | May 2007 | A1 |
20070214487 | Joung | Sep 2007 | A1 |
20070230110 | Starr et al. | Oct 2007 | A1 |
20070252670 | Darr | Nov 2007 | A1 |
20070255938 | Gagneraud et al. | Nov 2007 | A1 |
20070274070 | Wedell | Nov 2007 | A1 |
20080003867 | Wu | Jan 2008 | A1 |
20080005471 | Ma et al. | Jan 2008 | A1 |
20080052452 | Chow et al. | Feb 2008 | A1 |
20080071931 | Chow et al. | Mar 2008 | A1 |
20080071973 | Chow et al. | Mar 2008 | A1 |
20080071974 | Chow et al. | Mar 2008 | A1 |
20080071975 | Chow et al. | Mar 2008 | A1 |
20080071976 | Chow et al. | Mar 2008 | A1 |
20080071977 | Chow et al. | Mar 2008 | A1 |
20080071978 | Chow et al. | Mar 2008 | A1 |
20080082736 | Chow et al. | Apr 2008 | A1 |
20080086631 | Chow et al. | Apr 2008 | A1 |
20080147964 | Chow et al. | Jun 2008 | A1 |
20080177922 | Chow et al. | Jul 2008 | A1 |
20080313388 | Chow et al. | Dec 2008 | A1 |
20080313389 | Chow et al. | Dec 2008 | A1 |
20090204731 | Mulligan et al. | Aug 2009 | A1 |
20100007590 | Chae et al. | Jan 2010 | A1 |
20100082892 | Ma et al. | Apr 2010 | A1 |
20100082893 | Ma et al. | Apr 2010 | A1 |
20100110645 | Campini et al. | May 2010 | A1 |
20100149997 | Law et al. | Jun 2010 | A1 |
20100201278 | Zhao | Aug 2010 | A1 |
20100254096 | Kim et al. | Oct 2010 | A1 |
20100254100 | Kim et al. | Oct 2010 | A1 |
20110032108 | Lavene et al. | Feb 2011 | A1 |
20110226506 | Hamilton et al. | Sep 2011 | A1 |
20110234109 | Chiu | Sep 2011 | A1 |
20120042120 | Ni et al. | Feb 2012 | A1 |
20120146535 | Lee et al. | Jun 2012 | A1 |
Number | Date | Country |
---|---|---|
4038641 | Jun 1991 | DE |
0787218 | Mar 1995 | JP |
Entry |
---|
U.S. Appl. No. 13/214,072, filed Aug. 19, 2011, Molnar. |
U.S. Appl. No. 13/213,921, filed Aug. 19, 2011, Vazach. |
U.S. Appl. No. 13/213,991, filed Aug. 19, 2011, Molnar. |
U.S. Appl. No. 13/213,950, filed Aug. 19, 2011, Wehrle. |
U.S. Appl. No. 13/214,027, filed Aug. 19, 2011, Bodmann. |
U.S. Appl. No. 13/214,035, filed Aug. 19, 2011, Kretschmann. |
Number | Date | Country | |
---|---|---|---|
20120044082 A1 | Feb 2012 | US |
Number | Date | Country | |
---|---|---|---|
61375587 | Aug 2010 | US | |
61379894 | Sep 2010 | US |