1. Field of the Invention
The present invention relates in general to the fields of laser light amplification and software control systems.
2. Related Art
Laser interlock systems are configured to ensure a laser system operator's safety and/or to protect one or more laser system components from damage. Laser interlock systems typically include electromechanical systems configured to shutdown a laser system when some operational limit has been exceeded. For example, mechanical laser interlock systems may include mechanical relays connected to simple hardwired logic circuits. The mechanical relays are configured to close a shutter or cut power to one or more laser system components within the laser system, thereby shutting down the laser system. For example, a laser interlock system may be configured to activate a mechanical relay configured to disable laser light generation when a system cover is opened.
The simple approach of prior laser interlock systems causes a total shutdown of the laser system. While ensuring safety, the total shutdown has a number of drawbacks. For example, the laser system may need to be warmed up and calibrated again after a total shutdown before the laser system is again operational. There is, therefore, a need for improvements in laser interlock systems.
The present invention comprises, in various embodiments, systems and methods for shutting down a laser system in an intelligent and flexible manner. An intelligent laser interlock system includes a first module comprising hardwired components, and a second module comprising intelligent components configured to execute computing instructions. The hardwired components and the intelligent components are configured to shutdown the laser system to one or more alternative shutdown states in response to one or more interlock signals. These alternative shutdown states include intermediate shutdown states in which parts but not all of the laser system are shutdown.
Various embodiments of the invention include a system comprising an oscillator configured to generate a laser light pulse, an amplifier configured to receive the laser light pulse from the oscillator and amplify the laser light pulse, and a control system comprising an input configured to receive an interlock signal, an integrated circuit configured to select a shutdown state from a plurality of alternative shutdown states based on the interlock signal, and an output configured to place the system in the selected shutdown state.
Various embodiments of the invention include a system comprising a light source configured to generate a laser light pulse, and a control system comprising a hardwired interlock module configured to shutdown a first part of the light source, and an intelligent interlock module configured to shutdown a second part of the light source by executing computing instructions.
Various embodiments of the invention include a method comprising receiving an interlock signal, shutting down a laser system to a first shutdown state responsive to the interlock signal, the first shutdown state being an intermediate shutdown state, analyzing the interlock signal, and shutting down the laser system to a second shutdown state based on the analysis of the interlock signal.
In some embodiments of the present invention, an intelligent laser interlock system is configured to shutdown a laser system to one or more alternative shutdown states in an intelligent manner. The laser system typically includes multiple components, such as an optical oscillator configured to generate a laser light pulse and an optical amplifier configured to amplify the laser light pulse. The alternative shutdown states may include one or more partial shutdown states in which some but not all of the multiple laser system components are shutdown. For example, in some embodiments, one of the one or more intermediate (e.g., partial) shutdown states includes shutting down an optical amplifier but not shutting down an optical oscillator. In some embodiments, establishing a shutdown state includes shutting down one or more components external to the laser system.
In some embodiments, the intelligent laser interlock system is configured to be programmed by an end user or a developer to specify one or more system shutdown processes. The developer can be a vendor, a reseller, an original equipment manufacturer, a systems integrator, an engineer, or an entity that provides the intelligent laser interlock system to the end user. The one or more system shutdown processes include a shutdown sequence specifying an order in which laser system components are to be shutdown and including a shutdown timing specifying a time at which each of the one or more laser system components are to be shutdown in relation to one another. Each of the one or more system shutdown processes is configured to place the laser system into one of the plurality of shutdown states.
In various embodiments, the intelligent laser interlock system is configured to shut down the one or more laser system components in a shutdown sequence starting with one or more downstream components and ending with one or more upstream components. Upstream and downstream are defined with respect to the direction of propagation of the laser beam. For example, those laser system components that are configured to initially generate a laser light pulse are considered to be upstream relative to those components that amplify the generated laser light pulse.
The intelligent laser interlock system includes a hardwired interlock module whose functionality is determined by hardwired electrical connections and optionally simple logic gates. Functionality of the hardwired components is typically fixed and not configurable without rewiring or physically changing circuits. The hardwired interlock module is configured to respond to one or more hardwired interlock triggers by activating relays, shutters, and/or the like. For example, a hardwired interlock trigger may be activated by opening of a system cover. The hardwired interlock module may respond to this hardwired interlock trigger by closing a shutter such that a user is not exposed to laser light.
The intelligent laser interlock system further includes an intelligent interlock module whose functionality is determined by computing instructions. The intelligent interlock module is typically configured to respond to one or more intelligent interlock triggers by executing these computing instructions. The computing instructions may be configured to sequentially shut down components of the laser system in a prescribed order, to shut down the laser system to an intermediate shutdown state responsive to an analysis of the intelligent interlock trigger, to enable and disable various control signals, to operate relays, to operate shutters, and/or the like.
In some embodiments, the intelligent interlock module is configured to be programmed in order to customize a system shutdown process. For example, a user may program the system shutdown process via an external computer system, a software program, or a laser system control panel. Alternatively, a vendor may program the system shutdown process via an external computer system, an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA), a microprocessor, software, or firmware. The computing instructions that the intelligent interlock module is configured to execute may be embodied in firmware, hardware, or software stored on a computer readable medium. The intelligent interlock module may comprise a microprocessor, an integrated circuit, a Field Programmable Gate Array, a programmable logic device, or the like. The intelligent interlock module may also be configured to connect to an external computer system.
An intelligent interlock trigger may be configured to be activated if the temperature of an optical amplifier exceeds a predetermined threshold. In response to this intelligent interlock trigger, the intelligent interlock module may cause a partial shutdown of the optical amplifier module such that the optical amplifier module can cool. This partial shutdown of the optical amplifier may not require shutdown of other system components of the laser system. The intelligent interlock module enables minor anomalous situations requiring a partial shutdown to be efficiently handled while maintaining an operational readiness state in the rest of the laser system.
The control system 108 comprises a plurality of components including control logic 112, optional user inputs 110, an optional external control interface 132, an optional display 116, and optional storage 114. In some embodiments, the control system 108 includes a self-contained computer system, such as a standard commercially available single board computer. Typically, the control system 108 is configured to run a real time operating system along with a laser control software application. In other embodiments, the control system 108 is based on an embedded microcomputer or microcontroller and runs a laser control program. In still other embodiments, the control system 108 is based on an Application Specific Integrated Circuit (ASIC) or a programmed Field Programmable Gate Array (FPGA).
User inputs 110 include controls configured for a user to operate the laser system 100. These controls may be manual or electronic. For example, user inputs 110 may include a keyboard, one or more buttons, a touch screen, a dial, switches, and/or the like. The user inputs 110 are configured for turning a laser beam on, turning the laser beam off, selecting one or more characteristics of the laser beam, and the like.
The display 116 is typically a liquid crystal or light emitting diode display. In various embodiments, the display 116 is configured to display system states, e.g., shutdown states, of the laser system 100 to a user. The system states may include, for example, information regarding repetition rate, component temperature, pulse width, pulse energy, or the like. Shutdown states may also include a list of components that are shutdown, a list of components that are not shutdown, why components were shutdown, a list of interlock triggers, or the like.
External control interface 132 is configured to communicate commands and/or data to or from one or more systems external to laser system 100. For example, external control interface 132 may be configured to communicate with a robot, an external trigger, a remote control, or an external interlock. In some embodiments, external control interface 132 is configured to communicate using a network protocol, such as TCP/IP. In various embodiments, the external control interface 132 includes a hardwired connection such as a single wire, a pair of wires, a USB interface, an Ethernet network interface, a FireWire interface, an RS-232 interface, a GPIB interface, or the like. Alternatively, the external control interface 132 includes a wireless connection such as a WiFi connection, a Bluetooth connection, a ZigBee connection, or the like.
In various embodiments, the external control interface 132 is configured to communicate one or more external interlock control inputs and/or outputs. External interlock control inputs are configured for external control circuitry or external computer systems to activate the intelligent laser interlock system. For example, in some embodiments, a first external interlock control input is configured to receive a hardwired interlock trigger and a second external interlock control input is configured to receive an intelligent interlock trigger. In some embodiments, external interlock control outputs are configured to control external circuitry or computer systems in response to an interlock trigger. For example, an external interlock control output may be used to shutdown an external device in response to an intelligent interlock trigger.
The storage 114 is configured to store operating parameters, logs of events that occur in the laser system 100, snapshots of system states of the laser system 100, and/or the like. For example, in some embodiments, the storage 114 is configured to store a snapshot of the state of laser system 100 at the time an interlock trigger is received. The storage 114 may include volatile memory, non-volatile memory, a hard drive, an optical drive, or the like.
The control logic 112 includes logic configured to execute computing instructions. For example, control logic 112 may include a processor, an application specific integrated circuit, a field programmable gate array, or the like. As is described further herein, the computing instructions executed by the control logic 112 include those used to respond to intelligent interlock triggers. The control logic 112 also includes wiring, comparators, logic gates (e.g., simple NAND, OR, and AND gates), and the like configured to perform hardwired operations. These hardwired operations include those used to respond to hardwired interlock triggers.
The oscillator 106 comprises oscillator logic 122, oscillator electronics 126, oscillator optics 130, and an optional oscillator shutter 136. The control system 108 is configured to communicate with oscillator 106 through one or more connections 120. This communication may include the transmission of control signals and/or commands to the oscillator logic 122, and may include receipt of status information, such as temperature, beam characteristics, beam alignment, error conditions, and interlock triggers from oscillator electronics 126.
The oscillator logic 122 comprises circuitry configured to control and monitor the oscillator 106. For example, in various embodiments, the oscillator logic 122 receives a plurality of command and control data signals from the control system 108 via connections 120 and, in turn, generates appropriate signals to control the oscillator electronics 126. In addition, the oscillator logic 122 typically includes circuitry configured to monitor one or more components of oscillator 106, and provide appropriate signals back to the control system 108 via connections 120. These signals may include interlock triggers and/or data indicative of a state of the oscillator 106. Oscillator logic 122 is coupled to oscillator electronics 126 via connections 124.
The oscillator electronics 126 are configured to supply power to the oscillator optics 130, and may include for example power amplifiers, trigger signals, heater power supplies, laser diode inputs, and/or the like. The oscillator electronics 126 are also configured to generate signals representative of states of oscillator 106. For example, the oscillator electronics 126 may include a temperature sensor and transducer, a flow sensor, a photodetector, a position sensor, and/or the like. The oscillator electronics 126 are optionally configured to control the oscillator shutter 136. The oscillator electronics 126 are coupled to the oscillator optics 130 and the oscillator shutter 136 via connections 128.
The oscillator optics 130 are configured to generate light pulses. These laser light pulses may be characterized by a laser light pulse power, a temporal width, a repetition rate, and a wavelength distribution. The pulse power may be defined as an average optical power present in the laser beam per unit time, or a peak power present in a single light pulse. In some embodiments, the light pulses generated by the oscillator optics 130 are chirped light pulses. The oscillator optics 130 may include a ring laser, an optical oscillator, a Bragg fiber, a pulse stretcher, a fiber optic, an optical pump source, an optical switch, and/or the like.
The oscillator shutter 136 is configured to block optical path 134 such that light pulses generated by the oscillator optics 130 are prevented from reaching the amplifier 104. The oscillator shutter 136 may include a mechanical shutter or an optical switch.
The amplifier 104 is configured to amplify optical pulses received from the oscillator 106 via the optical path 134. Amplifier 104 comprises an amplifier logic 138, an amplifier electronics 142, an amplifier optics 146, an optional external interface 150, and an optional amplifier shutter 148. The control system 108 is configured to communicate data and/or commands to the amplifier logic 138 through connections 118, and is further configured to receive data such as status and error conditions from the amplifier logic 138 through the amplifier connections 118.
The amplifier logic 138 comprises circuitry configured to control and monitor the amplifier 104. For example, in various embodiments, the amplifier logic 138 receives a plurality of command and control data signals from the control system 108 via connections 118 and, in turn, generates appropriate signals to control the amplifier electronics 142. In addition, the amplifier logic 138 typically includes circuitry configured to monitor one or more components of amplifier 104, and provide appropriate signals back to the control system 108 via connections 118. These signals may include interlock triggers and/or data indicative of a state of amplifier 104. The amplifier logic 138 is coupled to the amplifier electronics 142 via connections 140.
The amplifier electronics 142 are configured to supply power to amplifier optics 146, and may include for example power amplifiers, trigger signals, heater power supplies, laser diode inputs, and/or the like. Amplifier electronics 142 are also configured to generate signals representative of states of amplifier 104. For example, amplifier electronics 142 may include a temperature sensor and transducer, a photodetector, a position sensor, and/or the like. Amplifier electronics 142 are optionally configured to control amplifier shutter 148. Amplifier electronics 142 are coupled to amplifier optics 146 and amplifier shutter 148 via connections 144.
The amplifier optics 146 are configured to amplify light pulses received from oscillator optics 130. In some embodiments, the light pulses generated by oscillator optics 130 are chirped light pulses and amplifier optics 146 includes optics, such as a Bragg fiber, configured to temporally compress the amplified pulse. The amplifier optics 146 may include fiber optics, free space optics, a thin film amplifier and/or a fiber amplifier. In various embodiments, the amplified pulse is less than 1 nanosecond, 3 picoseconds, or 900 femtoseconds in width. The amplified pulse is provided as laser beam output 102.
Amplifier shutter 148 is configured to block the laser beam output 102 such that light pulses amplified by amplifier optics 146 do not leave laser system 100. Amplifier shutter 148 may include a mechanical shutter or an optical switch.
In various embodiments, the amplifier 104 is configured to communicate with one or more external systems via the external interface 150. These external systems may include an external interlock, a robot, an external trigger, a remote control, or an external interlock. In various embodiments, the external interface 150 is configured to communicate one or more external interlock control inputs and/or outputs. For example, external interface 150 may be used to communicate a signal from intelligent interlock logic 290 to shutdown an external device, or may receive an intelligent interlock trigger from an external device.
In various embodiments, operation of the laser system 100 is subject to an intelligent interlock system. In some embodiments, the intelligent interlock system is configured to separately shut down oscillator 106 and amplifier 104 in response to hardwired and/or intelligent interlock triggers.
Relative to the hardwired interlock module 210, the intelligent interlock module 220 is typically configured to respond to conditions that require less immediate and/or more variant response. For example, the intelligent interlock module 220 may adjust the electrical power provided by amplifier electronics 142 or a laser pulse repetition rate in response to a temperature measurement.
As is described further herein, in some embodiments, both the hardwired interlock module 210 and the intelligent interlock module 220 are used to respond to the same condition. For example, if the system cover is opened the hardwired interlock module 210 may close the amplifier shutter 148 and the intelligent interlock module 220 may turn off high voltage circuits.
The hardwired interlock module 210 and intelligent interlock module 220 are each responsive to sensors 230. Sensors 230 are configured to detect a condition of laser system 100 such as a temperature, voltage level, coolant flow, position, light pulse characteristic, and/or the like. For example, in various embodiments, sensors 230 include a thermocouple, an analog to digital converter, a flow meter, position sensors, and photodiodes. Sensors 230 are configured to generate an electrical signal, such as a hi-low (e.g, TTL) logic signal, an analog signal, or a multi-bit digital signal. Some of sensors 230 may be dedicated to sending the generated electrical signal to hardwired interlock module 210, some of sensors 230 may be dedicated to sending the generated electrical signal to intelligent interlock module 220, and some of sensors 230 may send electrical signals to both interlock modules. Sensors 230 may be included in any part of laser system 100.
The hardwired interlock module 210 and intelligent interlock module 220 are both configured to control shutdown activators 260. The shutdown activators 260 may include relays configured to break electrical connections, enable/disable signals, analog signals, switchers, mechanical shutters and/or positioners, warning messages, and/or the like. The shutdown activators 260 may also include system control elements such as parts of oscillator logic 122 or amplifier logic 138 configured to control pulse repetition rates or output powers. For example, intelligent interlock module 220 may be configured to respond to a measured temperature by changing a pulse repetition rate.
The hardwired interlock module 210 includes an optional hardwired trigger logic 240 and a hardwired interlock logic 250. The hardwired trigger logic 240 is configured to receive an output of sensors 230 and determine if the output represents a state that requires generation of a hardwired interlock trigger. A hardwired interlock trigger is typically a binary signal (e.g., a hi-low signal) that indicates that an interlock should be activated. The hardwired trigger logic 240 may include simple logic gates, comparators, analog-to-digital converters, and/or the like. For example, in some embodiments, the hardwired trigger logic 240 is configured to receive an analog signal from a member of sensors 230 and to compare this signal to a threshold voltage provided by a hardwired limits 245. A hardwired interlock trigger may then be generated in response to this comparison. In another example, the outputs of several of sensors 230 may be processed through simple logic gates, to generate a hardwired interlock trigger.
Hardwired interlock triggers generated by the hardwired trigger logic 240 are provided to hardwired interlock logic 250. The hardwired trigger logic 240 is optionally in embodiments wherein the output of one of sensors 230 is communicated directly to hardwired interlock logic 250. For example, if sensors 230 generate a binary signal, then this signal may be used directly by hardwired interlock logic 250.
The hardwired interlock logic 250 is typically configured to receive a variety of different hardwired interlock triggers from hardwired trigger logic 240. For example, hardwired interlock logic 250 may be configured to receive different hardwired interlock triggers corresponding to different members of sensors 230. Hardwired interlock logic 250 includes circuits configured for controlling which of shutdown activators 260 are activated by different hardwired trigger logic 240. These circuits optionally include NAND gates, AND gates, OR gates, and/or the like. In some embodiments, hardwired interlock logic 250 includes a direct connection between hardwired trigger logic 240 or sensors 230 and a member of shutdown activators 260.
The communication of hardwired interlock triggers between hardwired trigger logic 240 and hardwired interlock logic 250 may be serial or parallel. In some embodiments, particular hardwired interlock triggers are identified by the electrical connection through which they are received. In some embodiments, there is a separate electrical connector between hardwired trigger logic 240 and hardwired interlock logic 250 for each possible hardwired interlock trigger.
The hardwired interlock logic 250 is optionally further configured to communicate signals to an intelligent interlock logic 290 included in intelligent interlock module 220. These signals are discussed further elsewhere herein.
In addition to intelligent interlock logic 290, intelligent interlock module 220 includes intelligent trigger logic 280. Intelligent trigger logic 280 is configured to receive signals from sensors 230 and determine if an intelligent interlock trigger should be generated. In some embodiments, the intelligent trigger logic 280 includes the same elements and features as the hardwired trigger logic 240. However, intelligent trigger logic 280 may further include a limits memory 285 configured to store electronically programmable thresholds. These electronically programmable thresholds may be configured by writing data to the intelligent trigger logic 280. For example, in some embodiments, the electronically programmable thresholds can be configured by entering data through the user inputs 110 or through external control interface 132.
In some embodiments, hardwired interlock module 210 includes direct electrical connections that connect the output of sensors 230 to shutdown activators 260. These direct electrical connections may be configured to communicate a response as quickly as possible.
The intelligent trigger logic 280 is configured to compare data stored in limits memory 285 with signals received from sensors 230 in order to determine whether or not an intelligent interlock trigger should be generated. The signals received from sensors 230 are optionally digitized prior to this comparison. An intelligent interlock trigger is a signal that indicates that an interlock should be activated. The intelligent interlock trigger may be a binary signal or a set of binary signals (e.g. a set of bits). For example, the intelligent interlock trigger may include one, two or more bytes of data. In one embodiment, the intelligent interlock trigger includes a first byte indicating the identity of the member of sensors 230 whose signal caused the intelligent interlock trigger. Additional bytes may include quantitative information regarding the signal. For example, a second byte may indicate how far a sensed temperature is above a temperature threshold. In some embodiments, intelligent trigger logic 280 is configured to compare received sensor signals with calculated values, such as a calculated calibration value. Some limits may be determined during operation of laser system 100. For example, minimum and maximum pulse energies may be entered by a user.
The intelligent interlock trigger generated by intelligent trigger logic 280 is received by intelligent interlock logic 290. Intelligent interlock logic 290 is configured to respond to the intelligent interlock trigger by executing computing instructions. These computing instructions may be embodied in hardware, firmware, or software stored on a computer readable medium. These computing instructions are also optionally reconfigurable. As such, the operation of intelligent interlock logic 290 can be customized. Intelligent interlock logic 290 optionally includes a processor and memory configured to execute and store computing instructions, respectively.
Because intelligent interlock logic 290 is capable of executing computing instructions, intelligent interlock logic 290 can respond to intelligent interlock triggers with operations that include conditional statements (e.g., IF, WHILE, UNTIL, CASE, etc.) and these statements may be dependent on comparisons (e.g., A>B, A=B, A≠B, etc.). Using these operations, intelligent interlock logic 290 may be configured to respond to an intelligent interlock trigger as a function of a state of the laser system 100. For example, intelligent interlock logic 290 may respond differently to a detected high temperature depending on a current laser pulse repetition rate.
In some embodiments, different responses to an intelligent interlock trigger are enabled as the laser system 100 is brought through a self-test and through a warm-up period. For example, during warm-up, temperatures, electrical conditions and optical parameters may be expected to drift by a greater amount than when the laser system 100 is fully warmed up. Thus, intelligent trigger logic 280 may be configured to use wider limits during the warm-up period and narrower limits following the warm-up period.
In some embodiments, limits used by intelligent trigger logic 280 are dependent on the state of laser system 100. For example, in a continuous pulses mode where pulses are produced nearly continuously at a high repetition rate (e.g., >500 kHz) the average power detected at an optical output sensor would be expected to be nearly constant. Therefore, limits related to an output power are applicable to monitoring system performance. However, in a triggered mode in which one pulse is generated in response to one trigger event, the laser system 100 may be on while there are longer periods between pulses. During these periods, observation of the output power is not indicative of the system performance and limits related to the output power would not be used.
Intelligent interlock logic 290 is optionally further configured to operate shutdown activators 260 so as to shut down laser system 100 to one or more intermediate shutdown states. By bringing laser system 100 to an intermediate shutdown state, rather than completely shutting down laser system 100, it may be possible to restore laser system 100 to a fully operational state more quickly. Intelligent interlock logic 290 is optionally configured to shut down parts of laser system 100 in a variety of alternative orders.
In some embodiments, intelligent interlock logic 290 is configured to shutdown laser system 100 to an intermediate shutdown state in which oscillator optics 130 are being used to generate laser pulses but amplifier optics 146 are not provided with power to amplify the generated laser pulses. In some embodiments, intelligent interlock logic 290 is configured to shut down dangerous parts (e.g., high voltages and high power pulse sources) of the laser system 100 in a first shutdown state, and to shut down safe (e.g., low power) parts of the laser system 100 in a second shutdown state.
In some embodiments, hardwired interlock module 210 is configured to shutdown laser system 100 from a fully operation state to a first intermediate shutdown state, and intelligent interlock module 220 is configured to determine whether or not laser system 100 should be shutdown from the first intermediate shutdown state to a second shutdown state or to a fully shutdown state. For example, in response to a signal from sensors 230, hardwired interlock module 210 may shutdown operation of amplifier 104 and send an interlock trigger from hardwired interlock logic 250 to intelligent interlock logic 290. The shutdown of amplifier 104 is an example of an intermediate shutdown state and is facilitated by the relatively rapid response of hardwired interlock module 210. Intelligent interlock module 220 is configured to respond to the interlock trigger received from hardwired interlock module 210 by identifying a state of laser system 100. This state may include operational characteristics of oscillator 106 as well as information indicating that the operation of amplifier 104 is already shutdown. Based on the received interlock trigger and the determined state, intelligent interlock logic 290 may then determine if the generation of laser pulses using oscillator optics 130 should be shutdown, or if amplifier 104 can be restarted without first shutting down amplifier 104.
In some embodiments, intelligent interlock system 200 is considered to store one or more snapshots of the state of laser system 100. These snapshots may reflect states of laser system 100 before, during, and/or after receipt of an interlock trigger. For example, in some embodiments, control system 108 is configured to periodically store a state of laser system 100 in Storage 114. This state may be updated, for example, every 0.5 or 1.0 seconds. When intelligent interlock trigger or hardwired interlock trigger is generated, control system 108 is configured to preserve (e.g., save) the stored state such that the stored state can be used for later analysis. In some embodiments, control system 108 is configured to store a state of laser system 100 while in an intermediate shutdown state. For example, laser system 100 may be changed from a fully operational state to a first intermediate state by shutting down all or part of amplifier 104. In the first intermediate state, a state of laser system 100 may be saved for later use, and then the laser system 100 may be shutdown from the first intermediate state to a second intermediate shutdown state. Another state of the laser system 100 is optionally saved at the second intermediate shutdown state.
Saved states of laser system 100 are optionally included in event logs exported by control system 108. For example, control system 108 may be configured to include system states and events in a log. This log may be exported through external control interface 132. The events included in the log may comprise, for example, activation and deactivation of components, a number and characteristics of laser pulses produced, interlock triggers, movement of alignment optics, and/or the like.
While hardwired interlock module 210 and intelligent interlock module 220 are illustrated as separate modules in
More specifically, in a receive sensor output step 310 an output of sensors 230 is received by hardwired trigger logic 240. Typically, this output is received through a high speed connection, such as a direct wire. As is described elsewhere herein, the sensor output may include a temperature, a position, a flow, a characteristic of a laser pulse, and/or the like. The sensor output is optionally received by intelligent trigger logic 280 at approximately the same time as hardwired trigger logic 240.
In a generate hardwired trigger step 320, the received sensor output is used to generate a hardwired interlock trigger using hardwired trigger logic 240. In some embodiments, generation of the hardwired interlock trigger includes merely passing the received sensor signal to an output of hardwired trigger logic 240. For example, if the sensor output is a 0V to 5V signal generated by a system cover position sensor, then this signal may be used directly as a hardwired interlock trigger. In some embodiments, generation of the hardwired interlock trigger includes digitizing the received sensor signal, comparing the received sensor signal with a threshold, and/or passing the received sensor signal though simple logic gates. The generated hardwired interlock trigger is passed to hardwired interlock logic 250.
In a process hardwired trigger step 330, the hardwired interlock trigger provided to hardwired interlock logic 250 by hardwired trigger logic 240 is processed in order to control an appropriate member of shutdown activators 260. In some embodiments, a single hardwired interlock trigger may result in activation of more than one of shutdown activators 260. For example, one of shutdown activators 260 may be used to close oscillator shutter 136 while another of shutdown activators 260 may be used to disable part of amplifier electronics 142.
In some embodiments, the processing performed by hardwired interlock logic 250 in process hardwired trigger step 330 includes merely passing a received hardwired interlock trigger to an appropriate shutdown activator. For example, the 0V to 5V output of a system cover position sensor may be passed directly to a shutter control motor. In some embodiments, the hardwired interlock logic 250 is configured to activate several members of shutdown activators 260 in response to one hardwired interlock trigger. In some embodiments, the hardwired interlock 250 is configured to activate one of shutdown activators 260 in response to a logical combination of different hardwired interlock triggers.
Process hardwired trigger step 330 may also include communication of an interlock trigger from hardwired interlock logic 250 to intelligent interlock logic 290. This interlock trigger is treated as an intelligent interlock trigger by intelligent interlock logic 290 as, for example, is further described below with respect to a step 360.
In a shutdown step 340, all or part of laser system 100 is shutdown using one or more members of shutdown activators 260 in response to signals received from hardwired interlock logic 250. In some embodiments, parts of laser system 100 are shut down in a sequence from upstream components to downstream components. For example, amplifier optics 146 may be shut down before oscillator electronics 126. In some embodiments, hardwired interlock module 210 is configured to place laser system 100 in an intermediate shutdown state in which parts of amplifier 104 are shutdown while oscillator electronics 126 and/or oscillator optics 130 are still operational.
In an optional generate intelligent interlock trigger step 350 an intelligent interlock trigger is generated using intelligent trigger logic 280 in response to receiving a signal from one of sensors 230. Generate intelligent interlock trigger step 350 may include comparison of the received signal to a customizable threshold stored in limits memory 285. The generated intelligent interlock trigger may include a multi-bit data. Generate intelligent trigger step 350 is optionally performed in parallel with generate hardwired trigger step 320.
In a process intelligent trigger step 360, an intelligent interlock trigger is processed using intelligent interlock logic 290. The intelligent interlock trigger may be that generated in generate intelligent interlock trigger step 350 and/or an interlock trigger received from hardwired interlock logic in process hardwired trigger step 330. Process intelligent trigger step 360 and/or generate intelligent trigger step 350 are optionally performed in parallel with process hardwired trigger step 330.
The intelligent interlock trigger is processed by executing computing instructions. These computing instructions are optionally user customizable and may be configured to shutdown laser system 100 from a first intermediate shutdown state to another intermediate shutdown state or to a complete shutdown state. In some embodiments, these computing instructions are configured to differentiate between different types of intelligent interlock triggers and determine which intermediate shutdown state the laser system 100 should be placed in based on a determined type.
In some embodiments, the computing instructions are configured to analyze the intelligent interlock trigger and determine if the laser system 100 can be restored to a fully operational state from an intermediate shutdown state. In some embodiments, intelligent interlock logic 290 is configured to determine that an external device should be shut down by sending signals through external control interface 132 or external interface 150. In some embodiments, the computing instructions are configured to save one or more states of laser system 100 or send log information to an external device in response to an intelligent interlock trigger.
In a shutdown step 370, the state of laser system 100 is changed according to the processing of process intelligent trigger step 360. This change may include bringing the laser system 100 from a fully operational state to an intermediate shutdown state, from a first intermediate shutdown state to a second shutdown state, or from an intermediate shutdown to a complete shutdown state.
Specifically, in a receive hardwired trigger step 410 hardwired interlock logic 250 receives and processes a hardwired interlock trigger. This interlock trigger is processed using hardwired logic as is described elsewhere herein. The results of the processing may include sending one or more signals to shutdown activators 260, sending an interlock trigger to intelligent interlock logic 290, saving a state of laser system 100, sending log data to one or more external devices, and/or the like.
In a shutdown step 420, the state of laser system 100 is changed using shutdown activators 260 in response to the processing of the hardwired interlock trigger in receive hardwired trigger step 410. This state change may include shutting down parts of amplifier 104 and/or parts of oscillator 106 in order to reach an intermediate shutdown state.
In a receive intelligent trigger step 430 an intelligent interlock trigger is received and processed by intelligent interlock logic 290. Receive intelligent trigger step 430 is optionally performed in parallel with receive hardwired trigger step 410 and/or shutdown step 420. The intelligent interlock trigger may be received from hardwired interlock logic 250 and/or intelligent trigger logic 280, or from an external device via external interface 150.
The intelligent interlock trigger is processed by executing computing instructions included within intelligent interlock logic 290. As is described elsewhere herein, these computing instructions may be user configurable.
In a shutdown step 440, the state of laser system 100 is changed for a second time based on the processing in receive intelligent trigger step 430. The second change in state may be from a first intermediate shutdown state to a second intermediate shutdown state, from the first intermediate shutdown state to a fully operational state, or from the first intermediate shutdown state to essentially completely shutdown state (e.g., a state in which neither oscillator optics 130 nor amplifier optics 146 are used to generate laser light.)
In an optional store snapshot step 450, one or more snapshots of states of laser system 100 are saved. Store snapshot step 450 may be performed several times in the methods illustrated by
In an optional transmit snapshot step 460, the one or more snapshots stored in step 450 are transmitted from laser system 100 to an external device via external control interface 132. Transmit snapshot step 460 may also include transmitting an event log to the external device.
Several embodiments are specifically illustrated and/or described herein. However, it will be appreciated that modifications and variations are covered by the above teachings and within the scope of the appended claims without departing from the spirit and intended scope thereof. For example, systems and methods of the invention may include more than one of intelligent interlock module 200. One of intelligent interlock module 200 may be used to control more than one amplifier 104. Some laser system components that are described as being disposed within the oscillator 106 may be disposed within the control system 108 or within the amplifier 104 while being configured to perform an essentially similar function. Some laser system components that are described as being disposed within the amplifier 104 may be disposed within the control system 108 or within the oscillator 106 while being configured to perform an essentially similar function. In some embodiments, signals from external control interface 132 and/or external interface 150 are used as inputs to hardwired trigger logic 240 and/or intelligent trigger logic 280, in addition to or as an alternative to signals from sensors 230. The signals from external control interface 132 and external interface 150 may be used to generate hardwired interlock triggers and/or intelligent interlock triggers, as described elsewhere herein.
The embodiments discussed herein are illustrative of the present invention. As these embodiments of the present invention are described with reference to illustrations, various modifications or adaptations of the methods and or specific structures described may become apparent to those skilled in the art. All such modifications, adaptations, or variations that rely upon the teachings of the present invention, and through which these teachings have advanced the art, are considered to be within the spirit and scope of the present invention. Hence, these descriptions and drawings should not be considered in a limiting sense, as it is understood that the present invention is in no way limited to only the embodiments illustrated.
This application claims the benefit of U.S. Provisional Application Ser. No. 60/796,646 entitled “Laser System Software Development Platform,” filed Apr. 26, 2006, which is hereby incorporated herein by reference.
Number | Name | Date | Kind |
---|---|---|---|
2436662 | Norgaard | Feb 1948 | A |
3459960 | Aaland et al. | Aug 1969 | A |
3549256 | Brienza et al. | Dec 1970 | A |
3599019 | Nannichi et al. | Aug 1971 | A |
3602836 | Young | Aug 1971 | A |
3622907 | Tomlinson et al. | Nov 1971 | A |
3626318 | Young | Dec 1971 | A |
3628179 | Cuff | Dec 1971 | A |
3631362 | Almasi et al. | Dec 1971 | A |
3646469 | Buczek et al. | Feb 1972 | A |
3654624 | Becker et al. | Apr 1972 | A |
3696308 | Duffy et al. | Oct 1972 | A |
3735282 | Gans | May 1973 | A |
3806829 | Duston et al. | Apr 1974 | A |
3808549 | Maurer | Apr 1974 | A |
3851267 | Tanner | Nov 1974 | A |
3942127 | Fluhr et al. | Mar 1976 | A |
3963953 | Thornton, Jr. | Jun 1976 | A |
4061427 | Fletcher et al. | Dec 1977 | A |
4194813 | Benjamin et al. | Mar 1980 | A |
4289378 | Remy et al. | Sep 1981 | A |
4389617 | Kurnit | Jun 1983 | A |
4394623 | Kurnit | Jul 1983 | A |
4590598 | O'Harra, II | May 1986 | A |
4622095 | Grobman et al. | Nov 1986 | A |
4655547 | Heritage et al. | Apr 1987 | A |
4673795 | Ortiz, Jr. | Jun 1987 | A |
4718418 | L'Esperance, Jr. | Jan 1988 | A |
4722591 | Haffner | Feb 1988 | A |
4730113 | Edwards et al. | Mar 1988 | A |
4750809 | Kafka et al. | Jun 1988 | A |
4808000 | Pasciak | Feb 1989 | A |
4815079 | Snitzer et al. | Mar 1989 | A |
4824598 | Stokowski | Apr 1989 | A |
4827125 | Goldstein | May 1989 | A |
4829529 | Kafka | May 1989 | A |
4835670 | Adams et al. | May 1989 | A |
4847846 | Sone et al. | Jul 1989 | A |
4848340 | Bille et al. | Jul 1989 | A |
4849036 | Powell et al. | Jul 1989 | A |
4856011 | Shimada et al. | Aug 1989 | A |
4902127 | Byer et al. | Feb 1990 | A |
4907586 | Bille et al. | Mar 1990 | A |
4913520 | Kafka | Apr 1990 | A |
4915757 | Rando | Apr 1990 | A |
4928316 | Heritage et al. | May 1990 | A |
4947398 | Yasuda et al. | Aug 1990 | A |
4950268 | Rink | Aug 1990 | A |
4972423 | Alfano et al. | Nov 1990 | A |
4983034 | Spillman, Jr. | Jan 1991 | A |
4988348 | Bille | Jan 1991 | A |
4994059 | Kosa et al. | Feb 1991 | A |
5010555 | Madey et al. | Apr 1991 | A |
5014290 | Moore et al. | May 1991 | A |
5022042 | Bradley | Jun 1991 | A |
5031236 | Hodgkinson et al. | Jul 1991 | A |
5043991 | Bradley | Aug 1991 | A |
5053171 | Portney et al. | Oct 1991 | A |
5095487 | Meyerhofer et al. | Mar 1992 | A |
5098426 | Sklar et al. | Mar 1992 | A |
5122439 | Miersch et al. | Jun 1992 | A |
5132996 | Moore et al. | Jul 1992 | A |
5146088 | Kingham et al. | Sep 1992 | A |
5154707 | Rink et al. | Oct 1992 | A |
5159402 | Ortiz, Jr. | Oct 1992 | A |
5162643 | Currie | Nov 1992 | A |
5166818 | Chase et al. | Nov 1992 | A |
5187759 | DiGiovanni et al. | Feb 1993 | A |
5204867 | Koschmann | Apr 1993 | A |
5206455 | Williams et al. | Apr 1993 | A |
5237576 | DiGiovanni et al. | Aug 1993 | A |
5255117 | Cushman | Oct 1993 | A |
5265107 | Delfyett, Jr. | Nov 1993 | A |
5267077 | Blonder | Nov 1993 | A |
5278853 | Shirai et al. | Jan 1994 | A |
5291501 | Hanna | Mar 1994 | A |
5293186 | Seden et al. | Mar 1994 | A |
5301347 | Kensky | Apr 1994 | A |
5302835 | Bendett et al. | Apr 1994 | A |
5309453 | Treacy | May 1994 | A |
5313262 | Leonard | May 1994 | A |
5315431 | Masuda et al. | May 1994 | A |
5315436 | Lowenhar et al. | May 1994 | A |
5329398 | Lai et al. | Jul 1994 | A |
5331131 | Opdyke | Jul 1994 | A |
5355383 | Lockard | Oct 1994 | A |
5367143 | White, Jr. | Nov 1994 | A |
5400350 | Galvanauskas | Mar 1995 | A |
5411918 | Keible et al. | May 1995 | A |
5414725 | Fermann et al. | May 1995 | A |
5418809 | August, Jr. et al. | May 1995 | A |
5428471 | McDermott | Jun 1995 | A |
5430572 | DiGiovanni et al. | Jul 1995 | A |
5440573 | Fermann | Aug 1995 | A |
5446813 | Lee et al. | Aug 1995 | A |
5450427 | Fermann et al. | Sep 1995 | A |
5479422 | Fermann et al. | Dec 1995 | A |
5489984 | Hariharan et al. | Feb 1996 | A |
5499134 | Galvanauskas et al. | Mar 1996 | A |
5517043 | Ma et al. | May 1996 | A |
5520679 | Lin | May 1996 | A |
5548098 | Sugawara et al. | Aug 1996 | A |
5572335 | Stevens | Nov 1996 | A |
5572358 | Gabl et al. | Nov 1996 | A |
5585642 | Britton et al. | Dec 1996 | A |
5585652 | Kamasz et al. | Dec 1996 | A |
5585913 | Hariharan et al. | Dec 1996 | A |
5590142 | Shan | Dec 1996 | A |
5592327 | Gabl et al. | Jan 1997 | A |
5596668 | DiGiovanni et al. | Jan 1997 | A |
5602673 | Swan | Feb 1997 | A |
5602677 | Tournois | Feb 1997 | A |
5615043 | Plaessmann et al. | Mar 1997 | A |
5617434 | Tamura et al. | Apr 1997 | A |
5624587 | Otsuki et al. | Apr 1997 | A |
5625544 | Kowshik et al. | Apr 1997 | A |
5627848 | Fermann et al. | May 1997 | A |
5631771 | Swan | May 1997 | A |
5633750 | Nogiwa et al. | May 1997 | A |
5633885 | Galvanauskas et al. | May 1997 | A |
5642447 | Pan et al. | Jun 1997 | A |
5644424 | Backus et al. | Jul 1997 | A |
5651018 | Mehuys et al. | Jul 1997 | A |
5656186 | Mourou et al. | Aug 1997 | A |
5657153 | Endriz et al. | Aug 1997 | A |
5661829 | Zheng | Aug 1997 | A |
5663731 | Theodoras, II et al. | Sep 1997 | A |
5665942 | Williams et al. | Sep 1997 | A |
5666722 | Tamm et al. | Sep 1997 | A |
5670067 | Koide et al. | Sep 1997 | A |
5677769 | Bendett | Oct 1997 | A |
5689361 | Damen et al. | Nov 1997 | A |
5689519 | Fermann et al. | Nov 1997 | A |
5694501 | Alavie et al. | Dec 1997 | A |
5696782 | Harter et al. | Dec 1997 | A |
5701319 | Fermann | Dec 1997 | A |
5703639 | Farrier et al. | Dec 1997 | A |
5708669 | DiGiovanni et al. | Jan 1998 | A |
5710424 | Theodoras, II et al. | Jan 1998 | A |
5720894 | Neev et al. | Feb 1998 | A |
5726855 | Mourou et al. | Mar 1998 | A |
5734762 | Ho et al. | Mar 1998 | A |
5736709 | Neiheisel | Apr 1998 | A |
5739933 | Dembeck et al. | Apr 1998 | A |
5770864 | Dlugos | Jun 1998 | A |
5771253 | Chang-Hasnain et al. | Jun 1998 | A |
5778016 | Sucha et al. | Jul 1998 | A |
5781289 | Sabsabi et al. | Jul 1998 | A |
5788688 | Bauer et al. | Aug 1998 | A |
5790574 | Rieger et al. | Aug 1998 | A |
5815519 | Aoshima et al. | Sep 1998 | A |
5818630 | Fermann et al. | Oct 1998 | A |
5822097 | Tournois | Oct 1998 | A |
5844149 | Akiyoshi et al. | Dec 1998 | A |
5847825 | Alexander | Dec 1998 | A |
5847863 | Galvanauskas et al. | Dec 1998 | A |
5862287 | Stock et al. | Jan 1999 | A |
5862845 | Chin et al. | Jan 1999 | A |
5867304 | Galvanauskas et al. | Feb 1999 | A |
5875408 | Bendett et al. | Feb 1999 | A |
5880823 | Lu | Mar 1999 | A |
5880877 | Fermann et al. | Mar 1999 | A |
5898485 | Nati, Jr. | Apr 1999 | A |
5907157 | Yoshioka et al. | May 1999 | A |
5920668 | Uehara et al. | Jul 1999 | A |
5923686 | Fermann et al. | Jul 1999 | A |
5929430 | Yao et al. | Jul 1999 | A |
5936716 | Pinsukanjana et al. | Aug 1999 | A |
5999847 | Elstrom | Dec 1999 | A |
6014249 | Fermann et al. | Jan 2000 | A |
6016452 | Kasevich | Jan 2000 | A |
6020591 | Harter et al. | Feb 2000 | A |
6034975 | Harter et al. | Mar 2000 | A |
6041020 | Caron et al. | Mar 2000 | A |
6061373 | Brockman et al. | May 2000 | A |
6071276 | Abela | Jun 2000 | A |
6072811 | Fermann et al. | Jun 2000 | A |
6075588 | Pinsukanjana et al. | Jun 2000 | A |
6081369 | Waarts et al. | Jun 2000 | A |
6088153 | Anthon et al. | Jul 2000 | A |
6099522 | Knopp et al. | Aug 2000 | A |
6120857 | Balooch et al. | Sep 2000 | A |
6122097 | Weston et al. | Sep 2000 | A |
6130780 | Joannopoulos et al. | Oct 2000 | A |
6134003 | Tearney et al. | Oct 2000 | A |
6141140 | Kim | Oct 2000 | A |
6151338 | Grubb et al. | Nov 2000 | A |
6154310 | Galvanauskas et al. | Nov 2000 | A |
6156030 | Neev | Dec 2000 | A |
6161543 | Cox et al. | Dec 2000 | A |
6168590 | Neev | Jan 2001 | B1 |
6172611 | Hussain et al. | Jan 2001 | B1 |
6175437 | Diels et al. | Jan 2001 | B1 |
6179421 | Pang | Jan 2001 | B1 |
6181463 | Galvanauskas et al. | Jan 2001 | B1 |
6190380 | Abela | Feb 2001 | B1 |
6198568 | Galvanauskas et al. | Mar 2001 | B1 |
6198766 | Schuppe et al. | Mar 2001 | B1 |
6201914 | Duguay et al. | Mar 2001 | B1 |
6208458 | Galvanauskas et al. | Mar 2001 | B1 |
6246816 | Moore et al. | Jun 2001 | B1 |
6249630 | Stock et al. | Jun 2001 | B1 |
6252892 | Jiang et al. | Jun 2001 | B1 |
6256328 | Delfyett et al. | Jul 2001 | B1 |
6269108 | Tabirian et al. | Jul 2001 | B1 |
6271650 | Massie et al. | Aug 2001 | B1 |
6275250 | Sanders et al. | Aug 2001 | B1 |
6275512 | Fermann | Aug 2001 | B1 |
6281471 | Smart | Aug 2001 | B1 |
6290910 | Chalk | Sep 2001 | B1 |
6303903 | Liu | Oct 2001 | B1 |
6314115 | Delfyett et al. | Nov 2001 | B1 |
6325792 | Swinger et al. | Dec 2001 | B1 |
6327074 | Bass et al. | Dec 2001 | B1 |
6327282 | Hammons et al. | Dec 2001 | B2 |
6330383 | Cai et al. | Dec 2001 | B1 |
6334011 | Galvanauskas et al. | Dec 2001 | B1 |
6335821 | Suzuki et al. | Jan 2002 | B1 |
6340806 | Smart et al. | Jan 2002 | B1 |
RE37585 | Mourou et al. | Mar 2002 | E |
6355908 | Tatah et al. | Mar 2002 | B1 |
6359681 | Housand et al. | Mar 2002 | B1 |
6362454 | Liu | Mar 2002 | B1 |
6365869 | Swain et al. | Apr 2002 | B1 |
6366395 | Drake et al. | Apr 2002 | B1 |
6370171 | Horn et al. | Apr 2002 | B1 |
6370422 | Richards-Kortum et al. | Apr 2002 | B1 |
6396317 | Roller et al. | May 2002 | B1 |
6404944 | Wa et al. | Jun 2002 | B1 |
6407363 | Dunsky et al. | Jun 2002 | B2 |
6418256 | Danziger et al. | Jul 2002 | B1 |
6421169 | Bonnedal et al. | Jul 2002 | B1 |
6433303 | Liu et al. | Aug 2002 | B1 |
6433305 | Liu et al. | Aug 2002 | B1 |
6433760 | Vaissie et al. | Aug 2002 | B1 |
6463314 | Haruna | Oct 2002 | B1 |
6482199 | Neev | Nov 2002 | B1 |
6485413 | Boppart et al. | Nov 2002 | B1 |
6486435 | Beyer et al. | Nov 2002 | B1 |
6501590 | Bass et al. | Dec 2002 | B2 |
6522460 | Bonnedal et al. | Feb 2003 | B2 |
6522674 | Niwano et al. | Feb 2003 | B1 |
6525873 | Gerrish et al. | Feb 2003 | B2 |
6526085 | Vogler et al. | Feb 2003 | B2 |
6526327 | Kar et al. | Feb 2003 | B2 |
6529319 | Youn et al. | Mar 2003 | B2 |
6541731 | Mead et al. | Apr 2003 | B2 |
6547453 | Stummer et al. | Apr 2003 | B1 |
6549547 | Galvanauskas et al. | Apr 2003 | B2 |
6552301 | Herman et al. | Apr 2003 | B2 |
6555781 | Ngoi et al. | Apr 2003 | B2 |
6556733 | Dy et al. | Apr 2003 | B2 |
6567431 | Tabirian et al. | May 2003 | B2 |
6573813 | Joannopoulos et al. | Jun 2003 | B1 |
6574024 | Liu | Jun 2003 | B1 |
6574250 | Sun et al. | Jun 2003 | B2 |
6576917 | Silfvast | Jun 2003 | B1 |
6580553 | Kim et al. | Jun 2003 | B2 |
6587488 | Meissner et al. | Jul 2003 | B1 |
6597497 | Wang et al. | Jul 2003 | B2 |
6603903 | Tong et al. | Aug 2003 | B1 |
6603911 | Fink et al. | Aug 2003 | B2 |
6621040 | Perry et al. | Sep 2003 | B1 |
6621045 | Liu et al. | Sep 2003 | B1 |
6627421 | Unger et al. | Sep 2003 | B1 |
6627844 | Liu et al. | Sep 2003 | B2 |
6642477 | Patel et al. | Nov 2003 | B1 |
6647031 | Delfyett et al. | Nov 2003 | B2 |
6654161 | Bass et al. | Nov 2003 | B2 |
6661816 | Delfyett et al. | Dec 2003 | B2 |
6661820 | Camilleri et al. | Dec 2003 | B1 |
6671298 | Delfyett et al. | Dec 2003 | B1 |
6677552 | Tulloch et al. | Jan 2004 | B1 |
6681079 | Maroney | Jan 2004 | B1 |
6690686 | Delfyett et al. | Feb 2004 | B2 |
6695835 | Furuno et al. | Feb 2004 | B2 |
6696008 | Brandinger | Feb 2004 | B2 |
6697402 | Crawford | Feb 2004 | B2 |
6697408 | Kennedy et al. | Feb 2004 | B2 |
6700094 | Kuntze | Mar 2004 | B1 |
6700698 | Scott | Mar 2004 | B1 |
6706036 | Lai | Mar 2004 | B2 |
6706998 | Cutler | Mar 2004 | B2 |
6710288 | Liu et al. | Mar 2004 | B2 |
6710293 | Liu et al. | Mar 2004 | B2 |
6711334 | Szkopek et al. | Mar 2004 | B2 |
6716475 | Fink et al. | Apr 2004 | B1 |
6720519 | Liu et al. | Apr 2004 | B2 |
6723991 | Sucha et al. | Apr 2004 | B1 |
6727458 | Smart | Apr 2004 | B2 |
6728273 | Perry | Apr 2004 | B2 |
6728439 | Weisberg et al. | Apr 2004 | B2 |
6735229 | Delfyett et al. | May 2004 | B1 |
6735368 | Parker et al. | May 2004 | B2 |
6738144 | Dogariu | May 2004 | B1 |
6738408 | Abedin | May 2004 | B2 |
6744555 | Galvanauskas et al. | Jun 2004 | B2 |
6747795 | Lin et al. | Jun 2004 | B2 |
6749285 | Liu et al. | Jun 2004 | B2 |
6760356 | Erbert et al. | Jul 2004 | B2 |
6774869 | Biocca et al. | Aug 2004 | B2 |
6785445 | Kuroda et al. | Aug 2004 | B2 |
6787733 | Lubatschowski et al. | Sep 2004 | B2 |
6787734 | Liu | Sep 2004 | B2 |
6788864 | Ahmad et al. | Sep 2004 | B2 |
6791060 | Dunsky et al. | Sep 2004 | B2 |
6791071 | Woo et al. | Sep 2004 | B2 |
6795461 | Blair et al. | Sep 2004 | B1 |
6801550 | Snell et al. | Oct 2004 | B1 |
6801551 | Delfyett et al. | Oct 2004 | B1 |
6801557 | Liu | Oct 2004 | B2 |
6803539 | Liu et al. | Oct 2004 | B2 |
6804574 | Liu et al. | Oct 2004 | B2 |
6807353 | Fleming et al. | Oct 2004 | B1 |
6807375 | Dogariu | Oct 2004 | B2 |
6815638 | Liu | Nov 2004 | B2 |
6819694 | Jiang et al. | Nov 2004 | B2 |
6819702 | Sverdlov et al. | Nov 2004 | B2 |
6819837 | Li et al. | Nov 2004 | B2 |
6822251 | Arenberg et al. | Nov 2004 | B1 |
6824540 | Lin | Nov 2004 | B1 |
6829517 | Cheng et al. | Dec 2004 | B2 |
6834134 | Brennan, III et al. | Dec 2004 | B2 |
6878900 | Corkum et al. | Apr 2005 | B2 |
6882772 | Lowery et al. | Apr 2005 | B1 |
6885683 | Fermann et al. | Apr 2005 | B1 |
6887804 | Sun et al. | May 2005 | B2 |
6897405 | Cheng et al. | May 2005 | B2 |
6902561 | Kurtz et al. | Jun 2005 | B2 |
6917631 | Richardson et al. | Jul 2005 | B2 |
6928490 | Bucholz et al. | Aug 2005 | B1 |
6937629 | Perry et al. | Aug 2005 | B2 |
6943359 | Vardeny et al. | Sep 2005 | B2 |
6956680 | Morbieu et al. | Oct 2005 | B2 |
7006730 | Doerr | Feb 2006 | B2 |
7022119 | Hohla | Apr 2006 | B2 |
7031571 | Mihailov et al. | Apr 2006 | B2 |
7068408 | Sakai | Jun 2006 | B2 |
7072101 | Kapteyn et al. | Jul 2006 | B2 |
7088756 | Fermann et al. | Aug 2006 | B2 |
7095772 | Delfyett et al. | Aug 2006 | B1 |
7099549 | Scheuer et al. | Aug 2006 | B2 |
7116688 | Sauter et al. | Oct 2006 | B2 |
7132289 | Kobayashi et al. | Nov 2006 | B2 |
7143769 | Stoltz et al. | Dec 2006 | B2 |
7171074 | DiGiovanni et al. | Jan 2007 | B2 |
7217266 | Anderson et al. | May 2007 | B2 |
7220255 | Lai | May 2007 | B2 |
7233607 | Richardson et al. | Jun 2007 | B2 |
7257302 | Fermann et al. | Aug 2007 | B2 |
7321605 | Albert | Jan 2008 | B2 |
7321713 | Akiyama et al. | Jan 2008 | B2 |
7332234 | Levinson et al. | Feb 2008 | B2 |
7349452 | Brennan, III et al. | Mar 2008 | B2 |
7361171 | Stoltz et al. | Apr 2008 | B2 |
7367969 | Stoltz et al. | May 2008 | B2 |
7444049 | Kim et al. | Oct 2008 | B1 |
7505196 | Nati et al. | Mar 2009 | B2 |
7518788 | Fermann et al. | Apr 2009 | B2 |
7584756 | Zadoyan et al. | Sep 2009 | B2 |
7728967 | Ochiai et al. | Jun 2010 | B2 |
7787175 | Brennan, III et al. | Aug 2010 | B1 |
7822347 | Brennan, III et al. | Oct 2010 | B1 |
20010009250 | Herman et al. | Jul 2001 | A1 |
20010021294 | Cai et al. | Sep 2001 | A1 |
20010046243 | Schie | Nov 2001 | A1 |
20020003130 | Sun et al. | Jan 2002 | A1 |
20020051606 | Takushima et al. | May 2002 | A1 |
20020071454 | Lin | Jun 2002 | A1 |
20020091325 | Ostrovsky | Jul 2002 | A1 |
20020095142 | Ming | Jul 2002 | A1 |
20020097468 | Mecherle et al. | Jul 2002 | A1 |
20020097761 | Sucha et al. | Jul 2002 | A1 |
20020153500 | Fordahl et al. | Oct 2002 | A1 |
20020167581 | Cordingley et al. | Nov 2002 | A1 |
20020167974 | Kennedy et al. | Nov 2002 | A1 |
20020176676 | Johnson et al. | Nov 2002 | A1 |
20020186915 | Yu et al. | Dec 2002 | A1 |
20020191901 | Jensen | Dec 2002 | A1 |
20030011782 | Tanno | Jan 2003 | A1 |
20030031410 | Schnitzer | Feb 2003 | A1 |
20030039442 | Bond et al. | Feb 2003 | A1 |
20030053508 | Dane et al. | Mar 2003 | A1 |
20030055413 | Altshuler et al. | Mar 2003 | A1 |
20030060808 | Wilk | Mar 2003 | A1 |
20030086647 | Willner et al. | May 2003 | A1 |
20030095266 | Detalle et al. | May 2003 | A1 |
20030123496 | Broutin et al. | Jul 2003 | A1 |
20030142705 | Hackel et al. | Jul 2003 | A1 |
20030156605 | Richardson et al. | Aug 2003 | A1 |
20030161365 | Perry et al. | Aug 2003 | A1 |
20030161378 | Zhang et al. | Aug 2003 | A1 |
20030178396 | Naumov et al. | Sep 2003 | A1 |
20030202547 | Fermann et al. | Oct 2003 | A1 |
20030205561 | Iso | Nov 2003 | A1 |
20030214714 | Zheng | Nov 2003 | A1 |
20030223689 | Koch et al. | Dec 2003 | A1 |
20030235381 | Hunt | Dec 2003 | A1 |
20040000942 | Kapteyn et al. | Jan 2004 | A1 |
20040037505 | Morin | Feb 2004 | A1 |
20040042061 | Islam et al. | Mar 2004 | A1 |
20040049552 | Motoyama et al. | Mar 2004 | A1 |
20040101001 | Bergmann et al. | May 2004 | A1 |
20040128081 | Rabitz et al. | Jul 2004 | A1 |
20040134894 | Gu et al. | Jul 2004 | A1 |
20040134896 | Gu et al. | Jul 2004 | A1 |
20040226925 | Gu et al. | Nov 2004 | A1 |
20040231682 | Stoltz et al. | Nov 2004 | A1 |
20040233944 | Dantus et al. | Nov 2004 | A1 |
20040263950 | Fermann et al. | Dec 2004 | A1 |
20050008044 | Fermann et al. | Jan 2005 | A1 |
20050018986 | Argyros et al. | Jan 2005 | A1 |
20050035097 | Stoltz | Feb 2005 | A1 |
20050036527 | Khazaei et al. | Feb 2005 | A1 |
20050038487 | Stoltz | Feb 2005 | A1 |
20050061779 | Blumenfeld et al. | Mar 2005 | A1 |
20050065502 | Stoltz | Mar 2005 | A1 |
20050067388 | Sun et al. | Mar 2005 | A1 |
20050074974 | Stoltz | Apr 2005 | A1 |
20050077275 | Stoltz | Apr 2005 | A1 |
20050105865 | Fermann et al. | May 2005 | A1 |
20050107773 | Bergt et al. | May 2005 | A1 |
20050111073 | Pan et al. | May 2005 | A1 |
20050111500 | Harter et al. | May 2005 | A1 |
20050127049 | Woeste et al. | Jun 2005 | A1 |
20050154380 | DeBenedictis et al. | Jul 2005 | A1 |
20050163426 | Fermann et al. | Jul 2005 | A1 |
20050167405 | Stoltz et al. | Aug 2005 | A1 |
20050171516 | Stoltz et al. | Aug 2005 | A1 |
20050171518 | Stoltz et al. | Aug 2005 | A1 |
20050175280 | Nicholson | Aug 2005 | A1 |
20050177143 | Bullington et al. | Aug 2005 | A1 |
20050195726 | Bullington et al. | Sep 2005 | A1 |
20050213630 | Mielke et al. | Sep 2005 | A1 |
20050215985 | Mielke et al. | Sep 2005 | A1 |
20050218122 | Yamamoto et al. | Oct 2005 | A1 |
20050225846 | Nati et al. | Oct 2005 | A1 |
20050226278 | Gu et al. | Oct 2005 | A1 |
20050226286 | Liu et al. | Oct 2005 | A1 |
20050226287 | Shah et al. | Oct 2005 | A1 |
20050232560 | Knight et al. | Oct 2005 | A1 |
20050238070 | Imeshev et al. | Oct 2005 | A1 |
20050253482 | Kapps et al. | Nov 2005 | A1 |
20050259944 | Anderson et al. | Nov 2005 | A1 |
20050265407 | Braun et al. | Dec 2005 | A1 |
20050271094 | Miller et al. | Dec 2005 | A1 |
20050271340 | Weisberg et al. | Dec 2005 | A1 |
20060016891 | Giebel et al. | Jan 2006 | A1 |
20060030951 | Davlin et al. | Feb 2006 | A1 |
20060050750 | Barty | Mar 2006 | A1 |
20060056480 | Mielke et al. | Mar 2006 | A1 |
20060064079 | Stoltz et al. | Mar 2006 | A1 |
20060067604 | Bull et al. | Mar 2006 | A1 |
20060084957 | Delfyett et al. | Apr 2006 | A1 |
20060093012 | Singh et al. | May 2006 | A1 |
20060093265 | Jia et al. | May 2006 | A1 |
20060120418 | Harter et al. | Jun 2006 | A1 |
20060126679 | Brennan, III et al. | Jun 2006 | A1 |
20060131288 | Sun et al. | Jun 2006 | A1 |
20060187974 | Dantus | Aug 2006 | A1 |
20060209908 | Pedersen et al. | Sep 2006 | A1 |
20060210275 | Vaissie et al. | Sep 2006 | A1 |
20060221449 | Glebov et al. | Oct 2006 | A1 |
20060250025 | Kitagawa et al. | Nov 2006 | A1 |
20060268949 | Gohle et al. | Nov 2006 | A1 |
20070025728 | Nakazawa et al. | Feb 2007 | A1 |
20070047965 | Liu et al. | Mar 2007 | A1 |
20070064304 | Brennan, III | Mar 2007 | A1 |
20070106416 | Griffiths et al. | May 2007 | A1 |
20070196048 | Galvanauskas et al. | Aug 2007 | A1 |
20070229939 | Brown et al. | Oct 2007 | A1 |
20070253455 | Stadler et al. | Nov 2007 | A1 |
20070273960 | Fermann et al. | Nov 2007 | A1 |
20080232407 | Harter et al. | Sep 2008 | A1 |
20090245302 | Baird et al. | Oct 2009 | A1 |
20090273828 | Waarts et al. | Nov 2009 | A1 |
20090297155 | Weiner et al. | Dec 2009 | A1 |
20100118899 | Peng et al. | May 2010 | A1 |
Number | Date | Country |
---|---|---|
214100 | Mar 1987 | EP |
691563 | Jan 1996 | EP |
1462831 | Sep 2004 | EP |
8171103 | Jul 1996 | JP |
11189472 | Jul 1999 | JP |
2003181661 | Jul 2003 | JP |
2003344883 | Dec 2003 | JP |
2005174993 | Jun 2005 | JP |
W09428972 | Dec 1994 | WO |
WO2004105100 | Dec 2004 | WO |
WO2004114473 | Dec 2004 | WO |
WO2005018060 | Feb 2005 | WO |
WO2005018061 | Feb 2005 | WO |
WO2005018062 | Feb 2005 | WO |
WO2005018063 | Feb 2005 | WO |
Number | Date | Country | |
---|---|---|---|
20070253455 A1 | Nov 2007 | US |
Number | Date | Country | |
---|---|---|---|
60796646 | Apr 2006 | US |