Patent Grant
8612072
The present invention relates to a system for automatically detecting whether at least one of the addresses or instance numbers of a plurality of engine control units of a marine vessel needs to be changed. The system is capable of assigning new instance numbers to engine control units.
Marine engines such as outboard engines are typically provided with engine control units, in this example, engine management modules having a default instance number of, for example, 0. This does not present a problem when the marine vessel only has one outboard engine. However it does present a problem when there are more outboard engines, such as two engines. In these cases a vessel controller of the marine vessel will initially read two engine management modules both having instance numbers of 0. The vessel controller will therefore be inhibited from distinguishing between the two outboard engines.
To deal with this issue of duplicate instance numbers, an external computer is typically used to reset one of the instance numbers. This will typically also require a technician skilled in this specific area of marine technology and skilled in the computer program interfacing involved.
The above-described prior art may suffer a number of disadvantages. For example, external computers may not always be readily available. This is particularly true, for example, in remote locations. Also, using external computers on marine vessels increases the chances of such external computers becoming damaged and/or destroyed by, for example, water spray. External computers may be readily on hand but the required software may not be readily available. Partially impaired or non-functioning computers lead to delays.
A technician skilled in resetting instance numbers for outboard engines oftentimes may not be readily available. Even if such a technician is available, labour costs in resetting instance numbers may increase costs to the user.
It is an object of the present invention to provide, and the present invention does provide, a system disclosed herein for automatically detecting when at least one instance number from a plurality of engine control units of a marine vessel needs to be changed and automatically assigning at least one new, non-duplicate instance number as required.
There is accordingly provided a system for automatically detecting whether at least one of the addresses of a plurality of engine control units of a marine vessel needs to be changed. The system includes a plurality of servo controllers and the plurality of engine control units. Each of the engine control units and has an address and is electronically paired with respective ones of the servo controllers. The system includes a vessel controller in communication with the servo controllers and the engine controllers. The vessel controller commands all servo controllers to switch off their paired engine control unit. The vessel controller then commands in turn each of the servo controllers to switch on its paired one of the engine control units, read the address of its paired one of the engine control units, switch off its paired one of the engine control units, and convey the address back to the vessel controller. The vessel controller then compares the addresses of the engine control units as well as the addresses of the servo controllers. If at least two the addresses of the engine control units or of the servo controllers are duplicates of each other or out of the expected range of addresses, the vessel controller ascertains that at least one of the addresses of the engine control units or of the servo controllers needs to be changed.
There is also provided the above system in combination with a marine vessel. The system includes a plurality of engines paired with respective ones of the engine control units. If at least two engine control units have duplicate addresses, the vessel controller assigns a new address to one of the at least two engine control units having duplicate addresses.
There is further provided a system for operatively assigning identities to a plurality of engines of a marine vessel. The system has a plurality of servo controllers. The system includes a plurality of engine control units each associated with a respective one of the engines and being electronically paired with a respective one of the servo controllers. The system includes a vessel controller in communication with the servo controllers. The vessel controller commands the servo controllers to switch off the engine control units. The vessel controller commands in turn each of the servo controllers to switch on its paired one of the engine control units, assign a set address to its paired one of the engine control units and switch off its paired one of the engine control units. Each set address corresponds to a unique identity. The engines are thus associated with set addresses identifiable to the vessel controller.
According to another aspect, there is provided, in combination, a servo controller for a marine engine and an instance plug. The servo controller has a socket. The instance plug is connectable with the servo controller via the socket. The instance plug contains an address for electronically identifying the servo controller to which it is connected.
There is even further provided a method of automatically detecting whether an instance number associated with one of a first engine control unit and a second engine control unit of a marine vessel needs to be changed. The method uses a vessel controller operatively connected to the first engine control unit and the second engine control unit. The method includes the step of the vessel controller causing both the first engine control unit and the second engine control unit to be switched off. The vessel controller next causes one of the first engine control unit and the second engine control unit to be switched on. The vessel controller causes the instance number of said one of the first engine control unit and the second engine control unit to be read. The vessel controller causes said one of the first engine control unit and the second engine control unit to be switched off. The vessel controller causes the instance number so read to be conveyed to the vessel controller. The method includes the step of the vessel controller causing an other of the first engine control unit and the second engine control unit to be switched on. The vessel controller causes the instance number of said other of the first engine control unit and the second engine control unit to be read. The vessel controller causes said other of the first engine control unit and the second engine control unit to be switched off. The vessel controller causes the instance number of said other of the first engine control unit and the second engine control unit to be conveyed to the vessel controller. The method includes the step of the vessel controller comparing the instance number of the first engine control unit with the instance number of the second engine control unit. If the instance number of the first engine control unit and the instance number of the second engine control unit are duplicates of each other, the vessel controller ascertains that one of the instance number of the first engine control unit and the instance number of the second engine control unit needs to be changed.
There is yet further provided a method of automatically detecting whether at least one instance number associated with at least one of a plurality of engine control units of a marine vessel needs to be changed. The engine control units each have an instance number and are paired with servo controllers. The method uses a vessel controller electronically coupled to the servo controllers in a manner predetermined by the vessel controller. The method includes the step of the vessel controller commanding the servo controllers to switch off the engine control units. The vessel controller commands in turn each of the servo controllers to switch on its paired one of the engine control units, read the instance number of its paired one of the engine control units, switch off its paired one of the engine control units, and convey the instance number back to the vessel controller. The method includes the step of the vessel controller comparing the instance numbers of the engine control units, whereby if at least two said instance numbers of the engine control units are duplicates of each other, the vessel controller ascertains that at least one of the instance numbers of the engine control units needs to be renumbered.
There is further provided a method of assigning identities to a plurality of engine control units of a marine vessel. The engine control units each have an address and each is paired with a respective one of a first servo controller or a second servo controller. The method uses a vessel controller electronically coupled to the first servo controller and the second servo controller, respectively, in a manner predetermined by the vessel controller. The method includes the step of the vessel controller instructing the first servo controller to switch off its peer engine control unit and the second control unit to switch off its peer engine control unit. The method includes the step of the vessel controller instructing the first servo controller to switch on its peer engine control unit, assign an address to its peer engine control unit and then switch off its peer engine control unit. The method includes the step of the vessel controller instructing the second servo controller to switch on its peer engine control unit, assign a further address to its peer engine control unit and then switch off its peer engine control unit.
There is also provided a method of automatically instancing a plurality of engine control units of a marine vessel. The engine control units each have an instance number. The engine control units are paired with servo controllers. A vessel controller is electronically coupled with the servo controllers in a manner predetermined by the vessel controller. The method includes the step of the vessel controller commanding each of the servo controllers to switch off its paired engine control unit. The method includes the step of the vessel controller commanding in turn each of the servo controllers to switch on its paired one of the engine control units, read the instance number of its paired one of the engine control units, switch off its paired one of the engine control units, and convey the instance number back to the vessel controller. The method includes the step of the vessel controller comparing the instance numbers of the engine control units to determine if at least two said instance numbers are duplicates of each other. If at least two said instance numbers are duplicates of each other, the method includes the step of the vessel controller commanding a servo controller associated with one of the engine control units having a duplicate instance number to assign at least one new instance number to its peered engine control unit.
The invention will be more readily understood from the following description of preferred embodiments thereof given, by way of example only, with reference to the accompanying drawings, in which:
Referring to the drawings and first to
The marine vessel 20 has propulsion units, in this example, comprising three engines, in this case, outboard engines 36, 36.1, and 36.2.
The marine vessel 20 has an electronic shift and throttle system 25. Electronic shift and throttle systems per se are known, as for example disclosed in U.S. Pat. No. 7,330,782 to Graham et al., the disclosure in which is incorporated herein by reference.
The system 25 includes a shift and throttle controller, shown in
The electronic shift and throttle system 25 is shown schematically in greater detail in
The system 25 includes a communications link in this example a standard network connection, namely a CANBus 42. These are well-known in the art. The vessel controller 102 is operatively connected to the CANBus 42 via input/output pin 44. While the CANBus network 42 is shown, one skilled in the art will appreciate that dual redundant communication architecture can be used in the system described herein.
The system 25 includes a master ignition switch 46 connected to the CANBus 42 via pin 48. The system 25 includes a power supply, in this example battery 50 operatively connected to the ignition switch 46. Battery 50 supplies CAN power to the entire private CANBus network 42. The system 25 in this example has a gateway 52 connected to the CANBus 42 via pin 54. The private CANBus network 42 of the system 25 interfaces with a public network, in this example a public NMEA2K network 58, via the gateway 52. NMEA2K is a standard for serial data neworking of marine electronic devices on CAN. Information from the system 25 is made available to the public NMEA2K network 58 via the gateway 52. The gateway 52 isolates the system 25 from public messages, but transfers engine data to displays and gauges. The gateway 52 has four analog inputs 56 which can be used to read fuel sender information and broadcast this information on the public network 58. Ignition switch systems, gateways, fuel senders, and interfacing networks per se are known and therefore will not be discussed further.
The system 25 in this example includes five outboard engines 36, 36.1, 36.2, 36.3, and 36.4. Each of the engines has substantially the same components and functions in substantially the same way. Like parts have like numbers, with the addition of “.1” for engine 36.1, “.2” for engine 36.2 and so on.
Engine 36 is labelled ENGINE 0 in
Engine 36 has a servo controller, in this example an electronic servo module (ESM) 62. The acronym ESM is shown in
Electronic servo module 62 is operatively connected to the engine management module 68. As shown in
Referring back to
The vessel controller 25, the electronic servo modules, and the engine management modules are thus communicatively coupled to one another via the CANBus 42. The vessel controller 25, the electronic servo modules, and the engine management modules can pass messages to one another via the CANBus 42 using a predefined protocol, such as the well-known NMEA 2000 protocol. Though CANBus 42 and NMEA 2000 are provided by way of example, it should be understood that the communications link can be any suitable communications link and can employ any suitable communications protocol.
Referring to
A data holder in this example an instance plug 112, containing an address for electronically identifying the electronic servo module, is operatively connectable to the electronic servo module 62. In this example the address of the instance plug 112 is an instance number. The instance plug 112 is received by socket 109 of the electronic servo module 62.
The electronic servo module 62 has a plurality of connectors. Connector 88 connects the electronic servo module 62 to the CANBus 42. Connector 90 enables the engine management module 68 to connect to the CANBus 42. Connectors 92 and 94 are related to trim functions of the engine, the systems for which are known and will not be discussed further. Connector 96 connects the electronic servo module 62 to the shift actuator 64 shown in
Referring now to
Referring to
The vessel controller 102 has inputs and outputs, in this example, collectively in the form of transceiver 110. The transceiver 110 in this example is a CAN transceiver, namely a Philips PCA82C251. The transceiver 110 is coupled to the input/output pin 44 of the CANBus 42. The vessel controller 102 includes a host processor 104, which is preferably an embedded microcontroller. The transceiver 110 is operatively connected to the host processor 104. The transceiver 110 receives and transmits signals, which are in turn sent to the processor 104.
The host processor 104 in this example is an Infineon XC164CS type CPU, though other processors may be used. The host processor 104 hosts control software 105 that controls the vessel controller 102. The host processor 104 may be referred to as part of a command means of the vessel controller 102. According to one aspect, the host process 104 can perform the task of comparing data numbers. The host processor 104 may therefore be referred to as part of a comparing means of the vessel controller 102. According to another aspect, the host processor 104 can operatively assign a new address or instance number to be conveyed and assigned to the engine management module 68. The host processor 104 may therefore be referred to as part of an assigning means of the vessel controller 102.
The vessel controller 102 includes memory, in this example external electrically erasable programmable read-only memory (EEPROM) 106. The external EEPROM 106 in this example is in the form of a microchip 25LC160A. Memory 106 is operatively connected to the host processor 104. The vessel controller 102 provides a clock signal 101 to the external EEPROM that is electrically connected to an output pin 131 of the host processor 104. The vessel controller 102 includes a power supply 108. In this example the power supply 108 is a 12V power supply that is electrically connected to an input pin 109 of the host processor 104 in a manner configured to provide 5V to the host processor 104.
Host processors, control software, memory, and clocks per se are well known to those skilled in the art, as for example disclosed in U.S. Pat. No. 7,330,782, the disclosure of which is incorporated herein by reference. Thus their operation and various components will not be described in great detail.
Still referring to
Referring back to
The electronic servo module 62 has memory, in this example external electrically erasable programmable read-only memory (EEPROM) 116. The external EEPROM 116 in this example is in the form of a microchip 25LC160A. Memory 116 is operatively connected to the processor 114. The instance plug 112, with its instance number, in this example an instance number of 0, is shown connected to the processor 114. Memory 116 receives and stores this instance number of the electronic servo module 62. The electronic servo module 62 provides a clock signal 111 to the external EEPROM that is electrically connected to an output pin 113 of the host processor 114. The electronic servo module 62 includes a power supply 118. Preferably the power supply 118 is a 12V power supply that is electrically connected to an input pin 119 of the processor 114 in a manner configured to provide 5V to the processor 114.
Electronic servo module 62.1 is substantially the same as that described above with the exception that it may have a different instance number. In this example it has an instance number of 1, as determined by its instance plug 112. Also in this example: electronic servo module 62.2 has an instance number of 2; electronic servo module 62.3 has an instance number of 3; and electronic servo module 62.4 has an instance number of 4.
The engine management module 68, shown in
The engine management module 68 includes a power supply 128. Preferably the power supply 128 is a 12V power supply that is electrically connected to an input pin 129 of the processor 124 in a manner configured to provide 5V to the host processor 124.
The engine management module 68 has memory, in this example electrically erasable programmable read-only memory (EEPROM) 126, internal to the processor 129. Memory 126 is operatively connected to the processor 124. The memory 126 stores an address electronically identifying the engine management module 68, in this example an instance number. Engine management module 68 in this example has an initial instance number of 0. Typically engine management modules have instance numbers of 0 because in a large number of applications, a given marine vessel will only have one engine. In this example: engine management module 68.1 has an initial instance number of 0; engine management module 68.2 has an initial instance number of 0; engine management module 68.3 has an initial instance number of 0; and engine management module 68.4 has an initial instance number of 0.
The electronic servo module 62 is operatively connected to the engine management module 68 via a connecting plug, in this example conductor 122 of a printed electric circuit board, as shown in
Referring to
The system 25 as herein disclosed has the ability to automatically set, or reset, all engine management module instance numbers.
Because the system 25 has the ability to perform auto-instancing, that is automatically set all engine management module instance numbers, the system 25 can advantageously ensure that each electronic servo module-engine management module 68 pair is associated with the same instance number. For example, since electronic servo module 62 has an instance number of 0, the system 25 can ensure that engine management module 68 also has an instance number of 0. Since electronic servo module 62.1 has an instance number of 1, the system 25 can change the instance number of engine management module 68.1 to ensure that engine management module 68.1 also has an instance number of 1, and likewise ensure the remaining pairs of electronic servo modules and engine management modules have the same instance numbers.
The operation of the system 25 as it relates to auto-instancing, and as generally outlined above, will now be discussed greater detail.
Referring to
The first step in this process is detecting whether any instance numbers need to be changed. This process 134 is shown generally in
The vessel controller 102 tells each electronic servo module in the system 25 to go into its auto-instancing state. The electronic servo modules enter their auto-instancing states when they receive an “auto-instance init” command from the vessel controller 102. In the auto-instancing state, each electronic servo module stops transmitting its heart beat message on the private CANBus network 42. This inhibits any heartbeat faults from occurring while proceeding. Each electronic servo module ignores shift, throttle, trim, start and stop commands from the control head 28. Each electronic servo module accepts auto-instancing commands from the vessel controller 102.
Next, and referring to
The vessel controller 102 next tells each electronic servo module 62-62.4 in the system 25 to in turn get its peer engine management module instance number. To do so and referring to
The vessel controller 102 next commands the electronic servo module 62.1, which has an instance number in this example of 1, to switch on its switch B+ 136.1 and thereby switch on the engine management module 68.1, as shown in
This process is repeated for the rest of the engines 36.2, 36.3 and 36.4. The vessel controller 102 thus now has information that: electronic servo module 36.2, which in this example has an instance number of 2, is associated with an engine management module 68.2 having an initial instance number of 0; electronic servo module 36.3, which in this example has an instance number of 3, is associated with an engine management module 68.3 having an initial instance number of 0; and electronic servo module 36.4, which in this example has an instance number of 4, is associated with an engine management module 68.4 having an initial instance number of 0.
The vessel controller 102 is not able to distinguish between engine management modules in this case of engine management modules with duplicate instance numbers when all the switches 136 are switched on. This is because, as shown in
Because the vessel controller 102 has detected a situation where there are at least two engine management modules with duplicate instance numbers, the system 25 in its auto-instancing state next proceeds via its controller 102 to assigning at least one new instance number to at least one engine management module. This process 138 is shown generally in
The vessel controller 102 tells each electronic servo module to set its peer engine management module. Each engine management module is initially turned off, as shown in
Next, the vessel controller 102 commands electronic servo module 62.1 to turn on its peer engine management module 68.1 as shown in
The vessel controller 102 next commands electronic servo module 62.2 to turn on its peer engine management module 68.2, as shown in
This process is repeated for the rest of the engines 36.3 and 36.4, with the net result being in this example shown in
After all the engine management module instance numbers have been set, the vessel controller 102 commands all electronic servo modules 62-62.4 to turn their peer engine management modules 68-68.4 back on again, as shown in
The system 25 will automatically start auto-instancing when an electronic servo module is powered-up into a functional system, including the first time it is so powered-up. Referring to
If the instance plug 112 and associated instance number of the electronic servo module 62 match the configured peer engine management module instance value stored in the non-volatile memory 116, the electronic servo module goes to a normal state of operation.
If the instance plug 112 does not match the configured peer engine management module instance value, the electronic servo module goes to an auto-instancing state. The vessel controller 102 and the electronic servo modules enter the auto-instancing state when at least one of the electronic servo modules has an instance plug 112 that does match its configured peer engine management module instance value stored in the non-volatile memory 116. In the auto-instancing state, the electronic servo modules: stop transmitting their heart beat messages on the private CANBus network 42; ignore shift, throttle, trim, start and stop commands from the control head 28; and accept auto-instancing commands from the control head 28 via the vessel controller 102. The auto-instancing process then proceeds as described previously above. When the electronic servo modules receive a command from the control head 28 to terminate the auto-instancing process, they go to their normal state.
The system 25 is also configured to initiate the auto-instancing state and process based on other factors. The system 25 will automatically start auto-instancing when duplicate or out-of-range engine management module instance numbers are detected. The system 25 will also automatically start auto-instancing when an instance plug 112 connected to an electronic servo module has changed.
The system 25 will automatically start auto-instancing when duplicate or out-of-range electronic servo module instance numbers are detected. When electronic servo modules with duplicate instance numbers are detected, the control head 28 via the vessel controller 102 enables one of the duplicate electronic servo modules and disables all the other ones for the current power-up cycle. The vessel controller 102 preferably enables an electronic servo module that has a peer engine management module with an instance number that matches that of the electronic servo module. For example, if there are two electronic servo modules with instance numbers of 0 and their peer engine management modules have instance numbers of 0 and 1, respectively, the electronic servo module with the engine management module having an instant number of 0 will be enabled. If such a situation does not arise, the duplicate electronic servo module that is enabled is selected randomly by the vessel controller 102. According to one example, duplicate electronic servo modules are indicated on the control head 28 by flashing rapidly of a neutral lamp associated with the duplicate engines.
In short, the system 25 automatically detects if there are duplicate electronic servo modules, and if so, the system 25 via the vessel controller 102 disables one of them. The duplicate, disabled electronic servo module is readily reconfigurable by changing the instance plug 112 to an instance plug having a non-duplicate instance number. For example, if the system 25 is a three engine system, with electronic servo module instance numbers of 0, 1 and 2 for each of the three engines, respectively, and the vessel controller 102 detects a fourth engine, with an electronic servo module having an instance number of 0, 1 or 2, the vessel controller 102 disables the fourth engine. The fourth engine can be added to the system by, for example, replacing the instance plug 112 of the fourth engine with an instance plug having an instance number of 3.
Every time the system 25 is powered-up with duplicate electronic servo module 62 instance numbers, the control head 28 stays dark and inactive until auto-instancing completes.
While the control head 28 via the vessel controller 102 is coordinating the auto-instancing sequence, it does not respond to any user inputs. Once the configuration sequence is complete, the control head 28 becomes active. In a preferred embodiment, the following table outlines the amount of time the system 25 needs to perform auto-instancing. During that time, all control head 28 indicators remain dark.
Accordingly to preferred embodiments, for a marine vessel having a single engine 36, auto-instancing will only take a maximum of three seconds. For a marine vessel having two engines, auto-instancing will only take a maximum of six seconds. For a marine vessel having three engines, auto-instancing will only take a maximum of nine seconds. For a marine vessel having four engines, auto-instancing will only take a maximum of twelve seconds. For a marine vessel having five engines, auto-instancing will only take a maximum of fifteen seconds. Accordingly to preferred embodiments, for a marine vessel having no duplicate or out-of-range ESMs 62 and no duplicate or out-of-range EMMs 68, auto-instancing terminates right after all of the addresses of the ESMs 62 and all of the addresses of the EMMs 68 have been received and validated by the vessel controller 102 and will take a maximum of 500 ms.
According to one example, engine management module instance numbers are defined as per the NMEA2K definition, which is a standard for serial data neworking of marine electronic devices on CAN. Preferred engine management module instance numbers for the system 25 are summarized in the table below:
For a system 25 where the marine vessel has one engine, the engine management module 68 will keep its default instance number of 0. For a marine vessel with two engines 36, the system 25 ensures that the engine management module 68 adjacent to the port side 21 has an instance number of 0 and the engine management module 68.1 adjacent to the starboard side 23 is assigned an instance number of 1.
For a marine vessel with three engines, the system 25 according to a preferred embodiment ensures that the engine management module 68 adjacent to the port side 21 has an instance number of 0, the engine management module 68.1 located in the center is assigned an instance number of 1 and the engine management module 68.2 adjacent to the starboard side 23 is assigned an instance number of 2.
For a marine vessel with four engines, the system 25 according to a preferred embodiment ensures that the engine management module 68 adjacent to the port side 21 has an instance number of 0, the engine management module 68.1 located in the port-center position has an instance number of 1, the engine management module 68.2 located in the starboard-center position has an instance number of 2, and the engine management module 68.3 adjacent to the starboard side 23 is assigned an instance number of 3.
For a marine vessel with five engines, the system 25 according to a preferred embodiment ensures that the engine management module 68 adjacent to the port side 21 has an instance number of 0, the engine management module 68.1 located in the port-center position has an instance number of 1, the engine management module 68.2 located in the center position has an instance number of 2, the engine management module 68.3 located in the starboard-center position has an instance number of 3, and the engine management module 68.4 adjacent to the starboard side 23 is assigned an instance number of 4.
The above listed instance numbers and configurations are described as preferred examples, though those skilled in the art will appreciate that other variations of instance number configurations are feasible.
The system 25 as herein described provides the advantage of not requiring an external tool to set up multi engine systems.
The auto-instancing of the system 25 could be initiated by the user on a sequence of key inputs at the control head 28. The auto-instancing of the system 25 could be requested by the engine management modules.
It will be understood by someone skilled in the art that many of the details provided above are by way of example only and are not intended to limit the scope of the invention which is to be determined with reference to the following claims.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5241250 | Nagasawa et al. | Aug 1993 | A |
| 5349644 | Massey et al. | Sep 1994 | A |
| 5551053 | Nadolski et al. | Aug 1996 | A |
| 6216083 | Ulyanov et al. | Apr 2001 | B1 |
| 6273771 | Buckley et al. | Aug 2001 | B1 |
| 6801507 | Humpleman et al. | Oct 2004 | B1 |
| 6859692 | Okuyama | Feb 2005 | B2 |
| 7144283 | Kawase | Dec 2006 | B2 |
| 7184867 | Okuyama | Feb 2007 | B2 |
| 7330782 | Graham et al. | Feb 2008 | B2 |
| 7408950 | Okuyama | Aug 2008 | B2 |
| 7430461 | Michaels | Sep 2008 | B1 |
| 7442101 | Kawase et al. | Oct 2008 | B2 |
| 7444213 | Motose | Oct 2008 | B2 |
| 7559812 | Yamada et al. | Jul 2009 | B2 |
| 7938701 | Ito et al. | May 2011 | B2 |
| 8162703 | Bamba | Apr 2012 | B2 |
| 8229608 | Yamamura et al. | Jul 2012 | B2 |
| 8406944 | Garon et al. | Mar 2013 | B2 |
| 20020077721 | Linn et al. | Jun 2002 | A1 |
| 20030082962 | Kanno | May 2003 | A1 |
| 20030093196 | Okuyama | May 2003 | A1 |
| 20040057450 | Okuyama | Mar 2004 | A1 |
| 20040059478 | Okuyama | Mar 2004 | A1 |
| 20050118896 | Okuyama et al. | Jun 2005 | A1 |
| 20050288833 | Motose | Dec 2005 | A1 |
| 20060009878 | Kobayashi et al. | Jan 2006 | A1 |
| 20060089059 | Kawase | Apr 2006 | A1 |
| 20060089060 | Kawase et al. | Apr 2006 | A1 |
| 20060293807 | Okuyama | Dec 2006 | A1 |
| 20070082566 | Okuyama | Apr 2007 | A1 |
| 20070232162 | Okuyama et al. | Oct 2007 | A1 |
| 20070293102 | Okuyama et al. | Dec 2007 | A1 |
| 20080020656 | Yamada et al. | Jan 2008 | A1 |
| 20080026649 | Ito et al. | Jan 2008 | A1 |
| 20080214069 | Kawanishi et al. | Sep 2008 | A1 |
| 20090261771 | Pearce et al. | Oct 2009 | A1 |
| 20100048068 | Bamba | Feb 2010 | A1 |
| 20100185325 | Kwon | Jul 2010 | A1 |
| 20110136696 | Heiner et al. | Jun 2011 | A1 |
| Number | Date | Country |
|---|---|---|
| 2009026663 | Mar 2009 | WO |
| Number | Date | Country | |
|---|---|---|---|
| 20110196553 A1 | Aug 2011 | US |
