Depth cameras often illuminate a scene with modulated laser light. Measured depth precision improves with increased modulation frequency, increased light power, and increased modulation depth. In many cases, scene illumination consumes a substantial portion of an overall depth camera power budget. Accordingly, it can be appreciated that an efficient, high frequency, high power laser diode driver circuit is a key component in a depth camera.
High power solid state laser diodes emit light power proportional to their junction current. For a high power edge emitting infrared laser diode, a voltage of close to 2V is required. For a laser diode including high powered vertical-cavity surface-emitting lasers (VCSELs) the forward voltage can be as high as 2.8V.
Exemplary prior art current mode laser diode drivers are shown in
An advantage of the prior art current mode laser diode drivers 1004 and 1104 of
A disadvantage of the prior art current mode laser diode drivers 1004 and 1104 of
Laser diode drivers, such as but not limited to those of
A typical solution to this problem is to add an external clamping diode, Dclamp, as shown in
Another problem encountered in laser diode driver circuits for depth cameras is variation in the latency through the driver circuits over process, temperature, and voltage. Uncompensated latency changes will result in significant errors in measured depths. For example, in one configuration, a change in latency of 6 ps can produce a measurement error of ˜1 mm. A high-power driver in a standard configuration will require a large number of buffers to boost the drive current to the desired level. Such buffers will have insertion delay and this delay will vary by much more than 6 ps over process, temperature, and voltage.
The main disadvantages of the prior art current mode laser diode driver circuits of
Disclosed herein are power efficient laser diode drivers, depth camera systems that include such laser diode drivers, and methods for driving laser diodes. In accordance with an embodiment, a laser diode driver is a voltage mode laser diode driver that selectively turns on and off a laser diode. The voltage mode laser diode driver includes an output stage and an active swing controller. The output stage includes an output node configured to be connected to one of the terminals of the laser diode (i.e., the anode terminal or the cathode terminal of the laser diode). The active swing controller is configured to drive the output stage in dependence on a modulation signal.
In accordance with an embodiment, the anode of the laser diode is connected to the voltage output of the power supply and the cathode of the laser diode is connected to the output node of the output stage. In such an embodiment, the output stage, under control of the active swing controller, selectively pulls a voltage level of the output node of the output stage down towards ground, in response to which the laser diode is turned on and emits light. Additionally, the output stage, under control of the active swing controller, selectively pulls the output node of the output stage up towards the voltage level of the voltage output of the power supply, in response to which the laser diode is turned off and does not emit light. Advantageously, the active swing controller drives the output stage in a manner that substantially prevents inductive kickback, which occurs in response to the laser diode being turned from on to off, from boosting the voltage level at the output node of the output stage above the voltage level at the voltage output of the power supply. In accordance with an embodiment, the active swing controller provides a discharge path around the laser diode to shunt a current associated with the inductive kickback that occurs in response to the laser diode being turned from on to off. Additionally, the output stage provides impedance matching that substantially eliminates ringing on the cathode of the laser diode, and more generally the output node of the output stage, while the laser diode is off.
In accordance with an alternative embodiment, the anode of the laser diode is connected to the output node of the output stage and the cathode of the laser diode is connected to ground. In such an embodiment, the output stage, under control of the active swing controller, selectively pulls a voltage level of the output node of the output stage up towards the voltage level at the voltage output of the power supply, in response to which the laser diode is turned on and emits light. Additionally, the output stage, under control of the active swing controller, selectively pulls the output node of the output stage down towards ground, in response to which the laser diode is turned off and does not emit light. Advantageously, the active swing controller drives the output stage in a manner that substantially prevents inductive kickback, which occurs in response to the laser diode being turned from on to off, from pulling the voltage level at the output node of the output stage (and thus, at the anode of the laser diode) below ground. In accordance with an embodiment, the active swing controller provides a discharge path around the laser diode to shunt a current associated with the inductive kickback that occurs in response to the laser diode being turned from on to off. Additionally, the output stage provides impedance matching that substantially eliminates ringing on the anode of the laser diode, and more generally the output node of the output stage, while the laser diode is off.
In accordance with an embodiment, to increase and preferably substantially maximize power efficiency, the voltage mode laser diode driver also includes a power supply controller that adjusts the voltage level of the voltage output of the power supply so that the current that flows through the laser diode when the laser diode is turned on and emitting light is substantially equal to a predetermined desired current. More specifically, the power supply controller can produce a feedback signal that is provided to the power supply in order to adjust the voltage level of the voltage output of the power supply in dependence a drain-to-source voltage of a transistor of the output stage while the laser diode is turned on, wherein the drain-to-source voltage of the transistor of the output stage is indicative of an actual laser diode current while the laser diode is on and emitting light. In a specific embodiment, the feedback signal is produced in dependence on a difference between the drain-to-source voltage of the transistor of the output stage (which is indicative of an actual laser diode current while the laser diode is on and emitting light) and a reference drain-to-source voltage of a reference transistor (which is indicative of a desired laser diode current). Such a desired laser diode current can, for example, be used to achieve a minimum laser power that can be used to obtain depth images having a desired resolution.
In accordance with an embodiment, a depth camera system includes the aforementioned power supply, laser diode and voltage mode laser diode driver, as well as an image pixel detector that detects light originating from the laser diode that has reflected off an object and is incident of the image pixel detector array. Additionally, the depth camera system includes one or more processors that produce depth images in dependence on outputs of the image pixel detector and update an application based on the depth images.
This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter. Furthermore, the claimed subject matter is not limited to implementations that solve any or all disadvantages noted in any part of this disclosure.
Certain embodiments of the present technology disclosed herein are related to laser diode drivers for use with depth cameras, methods for driving laser diodes, and systems that include a depth camera, which can be referred to as depth camera systems. Before providing additional details of such embodiments of the present technology, exemplary details of larger systems with which embodiments of the present technology can be used will first be described.
The computing system 112 may be a computer, a gaming system or console, or the like. According to an example embodiment, the computing system 112 may include hardware components and/or software components such that computing system 112 may be used to execute applications such as gaming applications, non-gaming applications, or the like. In one embodiment, computing system 112 may include a processor such as a standardized processor, a specialized processor, a microprocessor, or the like that may execute instructions stored on a processor readable storage device for performing the processes described herein.
The capture device 120 may include, for example, a camera that may be used to visually monitor one or more users, such as the user 118, such that gestures and/or movements performed by the one or more users may be captured, analyzed, and tracked to perform one or more controls or actions within the application and/or animate an avatar or on-screen character, as will be described in more detail below.
According to one embodiment, the tracking system 100 may be connected to an audiovisual device 116 such as a television, a monitor, a high-definition television (HDTV), or the like that may provide game or application visuals and/or audio to a user such as the user 118. For example, the computing system 112 may include a video adapter such as a graphics card and/or an audio adapter such as a sound card that may provide audiovisual signals associated with the game application, non-game application, or the like. The audiovisual device 116 may receive the audiovisual signals from the computing system 112 and may then output the game or application visuals and/or audio associated with the audiovisual signals to the user 118. According to one embodiment, the audiovisual device 16 may be connected to the computing system 112 via, for example, an S-Video cable, a coaxial cable, an HDMI cable, a DVI cable, a VGA cable, component video cable, but are not limited thereto.
As shown in
In the example depicted in
Other movements by the user 118 may also be interpreted as other controls or actions and/or used to animate the player avatar, such as controls to bob, weave, shuffle, block, jab, or throw a variety of different power punches. Furthermore, some movements may be interpreted as controls that may correspond to actions other than controlling the player avatar 140. For example, in one embodiment, the player may use movements to end, pause, or save a game, select a level, view high scores, communicate with a friend, etc. According to another embodiment, the player may use movements to select the game or other application from a main user interface. Thus, in example embodiments, a full range of motion of the user 118 may be available, used, and analyzed in any suitable manner to interact with an application.
In example embodiments, the human target such as the user 118 may have an object. In such embodiments, the user of an electronic game may be holding the object such that the motions of the player and the object may be used to adjust and/or control parameters of the game. For example, the motion of a player holding a racket may be tracked and utilized for controlling an on-screen racket in an electronic sports game. In another example embodiment, the motion of a player holding an object may be tracked and utilized for controlling an on-screen weapon in an electronic combat game. Objects not held by the user can also be tracked, such as objects thrown, pushed or rolled by the user (or a different user) as well as self-propelled objects. In addition to boxing, other games can also be implemented.
According to other example embodiments, the tracking system 100 may further be used to interpret target movements as operating system and/or application controls that are outside the realm of games. For example, virtually any controllable aspect of an operating system and/or application may be controlled by movements of the target such as the user 118.
As shown in
As shown in
According to another example embodiment, TOF analysis may be used to indirectly determine a physical distance from the capture device 120 to a particular location on the targets or objects by analyzing the intensity of the reflected beam of light over time via various techniques including, for example, shuttered light pulse imaging.
In another example embodiment, the capture device 120 may use a structured light to capture depth information. In such an analysis, patterned light (i.e., light displayed as a known pattern such as grid pattern, a stripe pattern, or different pattern) may be projected onto the scene via, for example, the IR light component 224. Upon striking the surface of one or more targets or objects in the scene, the pattern may become deformed in response. Such a deformation of the pattern may be captured by, for example, the 3-D camera 226 and/or the RGB camera 228 and may then be analyzed to determine a physical distance from the capture device to a particular location on the targets or objects. In some implementations, the IR Light component 224 is displaced from the cameras 226 and 228 so triangulation can be used to determined distance from cameras 226 and 228. In some implementations, the capture device 120 will include a dedicated IR sensor to sense the IR light.
According to another embodiment, the capture device 120 may include two or more physically separated cameras that may view a scene from different angles to obtain visual stereo data that may be resolved to generate depth information. Other types of depth image sensors can also be used to create a depth image.
The capture device 120 may further include a microphone 230, or an array of microphones 230. Each microphone 230 may include a transducer or sensor that may receive and convert sound into an electrical signal. According to one embodiment, the microphone(s) 230 may be used to reduce feedback between the capture device 120 and the computing system 112 in the target recognition, analysis, and tracking system 100. Additionally, the microphone(s) 230 may be used to receive audio signals (e.g., voice commands) that may also be provided by the user to control applications such as game applications, non-game applications, or the like that may be executed by the computing system 112.
In an example embodiment, the capture device 120 may further include a processor 232 that may be in operative communication with the image camera component 222. The processor 232 may include a standardized processor, a specialized processor, a microprocessor, or the like that may execute instructions including, for example, instructions for receiving a depth image, generating the appropriate data format (e.g., frame) and transmitting the data to computing system 112.
The capture device 120 may further include a memory component 234 that may store the instructions that may be executed by the processor 232, images or frames of images captured by the 3-D camera and/or RGB camera, or any other suitable information, images, or the like. According to an example embodiment, the memory component 234 may include random access memory (RAM), read only memory (ROM), cache, Flash memory, a hard disk, or any other suitable storage component. As shown in
As shown in
Computing system 112 includes gestures library 240, structure data 242, depth image processing and object reporting module 244 and application 246. Depth image processing and object reporting module 244 uses the depth images to track motion of objects, such as the user and other objects. To assist in the tracking of the objects, depth image processing and object reporting module 244 uses gestures library 240 and structure data 242.
Structure data 242 includes structural information about objects that may be tracked. For example, a skeletal model of a human may be stored to help understand movements of the user and recognize body parts. Structural information about inanimate objects may also be stored to help recognize those objects and help understand movement.
Gestures library 240 may include a collection of gesture filters, each comprising information concerning a gesture that may be performed by the skeletal model (as the user moves). The data captured by the cameras 226, 228 and the capture device 120 in the form of the skeletal model and movements associated with it may be compared to the gesture filters in the gesture library 240 to identify when a user (as represented by the skeletal model) has performed one or more gestures. Those gestures may be associated with various controls of an application. Thus, the computing system 112 may use the gestures library 240 to interpret movements of the skeletal model and to control application 246 based on the movements. As such, gestures library may be used by depth image processing and object reporting module 244 and application 246.
Application 246 can be a video game, productivity application, etc. In one embodiment, depth image processing and object reporting module 244 will report to application 246 an identification of each object detected and the location of the object for each frame. Application 246 will use that information to update the position or movement of an avatar or other images in the display.
The depth camera 226 is also shown as including a clock signal generator 262, which produces one or more signals that is/are provided to the laser diode driver 260. For example, the clock signal generator can produce a modulation signal that is provided to the laser diode driver 260. The clock signal generator 262 can also provide clock signals to other components of the depth camera. Additionally, the depth camera 226 is shown as including control logic 264 that can control the clock signal generator 262 and/or the laser diode driver 260. The depth camera 226 is also shown as including an image pixel detector 268, readout circuitry 270 and memory 266. The image pixel detector 268 might include, e.g., 320×240 array of image pixel detectors or 512×512 array of image pixel detectors, but is not limited thereto. Each image pixel detector can be, e.g., a complementary metal-oxide-semiconductor (CMOS) sensor or a charged coupled device (CCD) sensor, but is not limited thereto. Depending upon implementation, each image pixel detector can have its own dedicated readout circuit, or readout circuitry can be shared by many image pixel detectors. In accordance with certain embodiments, the components of the depth camera 226 shown within the block 280 are implemented in a single integrated circuit (IC), which can also be referred to as an image sensor chip 280. In accordance with an embodiment, the laser diode driver 260 can be implemented in another chip. Alternatively, the laser diode driver 260 can also be within the image sensor chip 280. The depth camera can include additional components not shown, such as, but not limited to, a phase detector, a variable delay line, and the like.
In accordance with an embodiment, the laser diode driver 260 drives the laser diode 250 in dependence on one or more signals received from the image sensor chip 280 that are produced by or in dependence on the clock signal generator 262. Accordingly, the laser diode driver 260 can include, for example, one or more buffers, a pre-driver and an output stage, but is not limited thereto. The clock signal generator 262 can include, for example, one or more reference clocks and/or voltage controlled oscillators, but is not limited thereto. The clock signal generator 262 can also include, or operate with, a variable delay line and a phase detector. The control logic 264, which can be implemented using logic gate, a microprocessor and/or state machine, but is not limited thereto, can be used to control the clock signal generator 262 and/or the laser diode driver 260. For example, the control logic 264 can access waveform information stored in the memory 266 in order to produce an HF modulated drive signal. The depth camera 226 can includes its own memory 266 and control logic 264, as shown in
In response to being driven by an HF modulated drive signal, the laser diode 250 emits an HF modulated laser beam, which can more generally be referred to as laser light. For an example, a carrier frequency of the HF modulated drive signal and the HF modulated laser light can be in a range from about 3 MHz to many hundreds of MHz, but for illustrative purposes will be assumed to be about 100 MHz. The laser light emitted by the laser diode 250 is transmitted through an optical structure 252, which can include one or more lens and/or other optical element(s), towards a target object (e.g., a user 118). The laser diode 250 and the optical structure 252 can be referred to, collectively, as an optical module 256. In accordance with certain embodiments of the present technology, the laser diode driver 260 is implemented using the embodiments described below with reference to
Assuming that there is a target object within the field of view of the depth camera, a portion of the laser light emitted by the optical module 256 reflects off the target object, passes through an aperture field stop and lens (collectively 272), and is incident on the image pixel detector 268 where an image is formed. In some implementations, each individual image pixel detector of the 268 produces an integration value indicative of a magnitude and a phase of detected HF modulated laser beam originating from the optical module 256 that has reflected off the object and is incident of the image pixel detector. Such integrations values, or more generally time-of-flight (TOF) information, enable distances (Z) to be determined, and collectively, enable depth images to be produced. In certain embodiments, optical energy from the laser diode 250 and detected optical energy signals are synchronized to each other such that a phase difference, and thus a distance Z, can be measured from each image pixel detector. The readout circuitry 270 converts analog integration values generated by the image pixel detector 268 into digital readout signals, which are provided to the microprocessor 264 and/or the memory 266, and which can be used to produce depth images. It is also possible that some other processor can produce the depth images.
A graphics processing unit (GPU) 308 and a video encoder/video codec (coder/decoder) 314 form a video processing pipeline for high speed and high resolution graphics processing. Data is carried from the graphics processing unit 308 to the video encoder/video codec 314 via a bus. The video processing pipeline outputs data to an A/V (audio/video) port 340 for transmission to a television or other display. A memory controller 310 is connected to the GPU 308 to facilitate processor access to various types of memory 312, such as, but not limited to, a RAM (Random Access Memory).
The multimedia console 300 includes an I/O controller 320, a system management controller 322, an audio processing unit 323, a network interface 324, a first USB host controller 326, a second USB controller 328 and a front panel I/O subassembly 330 that are preferably implemented on a module 318. The USB controllers 326 and 328 serve as hosts for peripheral controllers 342(1)-342(2), a wireless adapter 348, and an external memory device 346 (e.g., flash memory, external CD/DVD ROM drive, removable media, etc.). The network interface 324 and/or wireless adapter 348 provide access to a network (e.g., the Internet, home network, etc.) and may be any of a wide variety of various wired or wireless adapter components including an Ethernet card, a modem, a Bluetooth module, a cable modem, and the like.
System memory 343 is provided to store application data that is loaded during the boot process. A media drive 344 is provided and may comprise a DVD/CD drive, Blu-Ray drive, hard disk drive, or other removable media drive, etc. The media drive 344 may be internal or external to the multimedia console 300. Application data may be accessed via the media drive 344 for execution, playback, etc. by the multimedia console 300. The media drive 344 is connected to the I/O controller 320 via a bus, such as a Serial ATA bus or other high speed connection (e.g., IEEE 1394).
The system management controller 322 provides a variety of service functions related to assuring availability of the multimedia console 300. The audio processing unit 323 and an audio codec 332 form a corresponding audio processing pipeline with high fidelity and stereo processing. Audio data is carried between the audio processing unit 323 and the audio codec 332 via a communication link. The audio processing pipeline outputs data to the A/V port 340 for reproduction by an external audio player or device having audio capabilities.
The front panel I/O subassembly 330 supports the functionality of the power button 350 and the eject button 352, as well as any LEDs (light emitting diodes) or other indicators exposed on the outer surface of the multimedia console 300. A system power supply module 336 provides power to the components of the multimedia console 300. A fan 338 cools the circuitry within the multimedia console 300.
The CPU 301, GPU 308, memory controller 310, and various other components within the multimedia console 300 are interconnected via one or more buses, including serial and parallel buses, a memory bus, a peripheral bus, and a processor or local bus using any of a variety of bus architectures. By way of example, such architectures can include a Peripheral Component Interconnects (PCI) bus, PCI-Express bus, etc.
When the multimedia console 300 is powered ON, application data may be loaded from the system memory 343 into memory 312 and/or caches 302, 304 and executed on the CPU 301. The application may present a graphical user interface that provides a consistent user experience when navigating to different media types available on the multimedia console 300. In operation, applications and/or other media contained within the media drive 344 may be launched or played from the media drive 344 to provide additional functionalities to the multimedia console 300.
The multimedia console 300 may be operated as a standalone system by simply connecting the system to a television or other display. In this standalone mode, the multimedia console 300 allows one or more users to interact with the system, watch movies, or listen to music. However, with the integration of broadband connectivity made available through the network interface 324 or the wireless adapter 348, the multimedia console 300 may further be operated as a participant in a larger network community.
When the multimedia console 300 is powered ON, a set amount of hardware resources are reserved for system use by the multimedia console operating system. These resources may include a reservation of memory (e.g., 16 MB), CPU and GPU cycles (e.g., 5%), networking bandwidth (e.g., 8 Kbps), etc. Because these resources are reserved at system boot time, the reserved resources do not exist from the application's view.
In particular, the memory reservation preferably is large enough to contain the launch kernel, concurrent system applications and drivers. The CPU reservation is preferably constant such that if the reserved CPU usage is not used by the system applications, an idle thread will consume any unused cycles.
With regard to the GPU reservation, lightweight messages generated by the system applications (e.g., popups) are displayed by using a GPU interrupt to schedule code to render popup into an overlay. The amount of memory required for an overlay depends on the overlay area size and the overlay preferably scales with screen resolution. Where a full user interface is used by the concurrent system application, it is preferable to use a resolution independent of application resolution. A scaler may be used to set this resolution such that the need to change frequency and cause a TV resynch is eliminated.
After the multimedia console 300 boots and system resources are reserved, concurrent system applications execute to provide system functionalities. The system functionalities are encapsulated in a set of system applications that execute within the reserved system resources described above. The operating system kernel identifies threads that are system application threads versus gaming application threads. The system applications are preferably scheduled to run on the CPU 301 at predetermined times and intervals in order to provide a consistent system resource view to the application. The scheduling is to minimize cache disruption for the gaming application running on the console.
When a concurrent system application requires audio, audio processing is scheduled asynchronously to the gaming application due to time sensitivity. A multimedia console application manager (described below) controls the gaming application audio level (e.g., mute, attenuate) when system applications are active.
Input devices (e.g., controllers 342(1) and 342(2)) are shared by gaming applications and system applications. The input devices are not reserved resources, but are to be switched between system applications and the gaming application such that each will have a focus of the device. The application manager preferably controls the switching of input stream, without knowledge the gaming application's knowledge and a driver maintains state information regarding focus switches. The cameras 226, 228 and capture device 120 may define additional input devices for the console 300 via USB controller 326 or other interface.
Computing system 420 comprises a computer 441, which typically includes a variety of computer readable media. Computer readable media can be any available media that can be accessed by computer 441 and includes both volatile and nonvolatile media, removable and non-removable media. The system memory 422 includes computer storage media in the form of volatile and/or nonvolatile memory such as read only memory (ROM) 423 and random access memory (RAM) 460. A basic input/output system 424 (BIOS), containing the basic routines that help to transfer information between elements within computer 441, such as during start-up, is typically stored in ROM 423. RAM 460 typically contains data and/or program modules that are immediately accessible to and/or presently being operated on by processing unit 459. By way of example, and not limitation,
The computer 441 may also include other removable/non-removable, volatile/nonvolatile computer storage media. By way of example only,
The drives and their associated computer storage media discussed above and illustrated in
The computer 441 may operate in a networked environment using logical connections to one or more remote computers, such as a remote computer 446. The remote computer 446 may be a personal computer, a server, a router, a network PC, a peer device or other common network node, and typically includes many or all of the elements described above relative to the computer 441, although only a memory storage device 447 has been illustrated in
When used in a LAN networking environment, the computer 441 is connected to the LAN 445 through a network interface 437. When used in a WAN networking environment, the computer 441 typically includes a modem 450 or other means for establishing communications over the WAN 449, such as the Internet. The modem 450, which may be internal or external, may be connected to the system bus 421 via the user input interface 436, or other appropriate mechanism. In a networked environment, program modules depicted relative to the computer 441, or portions thereof, may be stored in the remote memory storage device. By way of example, and not limitation,
As explained above, the capture device 120 provides RGB images (also known as color images) and depth images to the computing system 112. The depth image may be a plurality of observed pixels where each observed pixel has an observed depth value. For example, the depth image may include a two-dimensional (2-D) pixel area of the captured scene where each pixel in the 2-D pixel area may have a depth value such as a length or distance in, for example, centimeters, millimeters, or the like of an object in the captured scene from the capture device.
In one embodiment, the depth image may be colorized or grayscale such that different colors or shades of the pixels of the depth image correspond to and/or visually depict different distances of the targets from the capture device 120. Upon receiving the image, one or more high-variance and/or noisy depth values may be removed and/or smoothed from the depth image; portions of missing and/or removed depth information may be filled in and/or reconstructed; and/or any other suitable processing may be performed on the received depth image.
Laser Diode Driver
Additional details of power efficient laser diode drivers, and methods for driving laser diodes, will now be described with reference to
Referring to
In the embodiment of
The pre-driver 720, which can also be referred to as a pre-driver circuit, is shown as including a non-overlapping clock generator 722, a clock tree 724 and a voltage level shifter 726, but is not limited thereto. The pre-driver 720 receives buffered versions of the differential laser drive modulation signals LD_MOD_P, LD_MOD_N from the LVDS buffer 712, and generates differential laser drive modulation signals IN_P, IN_N, which are provided to the active swing controller 730, and also generates and distributes clock signals for other components of the laser diode driver 704. The pre-driver 720 can increase the edge rate of the differential laser drive modulation signals and/or adjust levels of these modulation signals to the appropriate levels for driving the large NMOS device M1 of the main driver 740. The non-overlapping clock generator 722 can generate a non-inverting clock signal and inverting clock signal that respectively transition before a delayed non-inverting clock signal and a delayed inverting clock signal. There can also a delay between transitions of the non-inverting clock signal and the inverting clock signal that can be adjusted to selectively adjust a delay between LD_MOD_P and LD_MOD_N. The clock tree 724 receives the clock signals from the non-overlapping clock generator 722 and distributes the clock signals to other components of the laser diode driver 704. In accordance with specific embodiments, the frequency of the high frequency modulation signal is within the range of 16 MHz to 160 MHz, and in accordance with an embodiment is approximately 150 MHz. The use of other frequencies are also possible, and within the scope of an embodiment. The voltage level shifter 726 shifts the high logic voltage level of the differential laser drive modulation signals LD_MOD_P, LD_MOD_N from a high voltage rail level (Vss) to the voltage level (VL) at the voltage output of the power supply 706, causing the high logic voltage level of the differential laser drive modulation signals IN_P, IN_N to be the voltage level (VL) at the voltage output of the power supply 706. For example, the voltage level shifter 726 may shift the high logic voltage level from about 3.3V to about 2V, which improves the power efficiency of the laser diode driver 704. In an alternative embodiment, the pre-driver 720 does not include a voltage level shifter 321. The differential laser drive modulation signals IN_P, IN_N output by the pre-driver 720 can collectively be referred to as a high frequency modulation signal, or simply as a modulation signal.
In accordance with an embodiment, the pre-driver 720 and the LVDS buffer 714 provide different feedback signals LD_FB_P, LD_FB_N to the image sensor chip 702. This enables the image sensor chip 702, presuming it includes a phase detector, to measure the phase of the high frequency modulation signal for the purpose of maintaining a constant desired phase.
Before describing the active swing controller 730, it is first useful to describe the main driver 740. The main driver 740, which can also be referred to as the output stage 740, is shown as including an NMOS device M1 and a PMOS device M2, which can also be referred to as the output stage transistors M1 and M2. The NMOS device M1 (which is the main driving transistor, and thus may be referred to as the main NMOS device M1) and the PMOS device M2 are selectively turned on and off to selectively pull the voltage level at the MOUT node, to which the cathode of the laser diode 708 is connected, down towards ground or up towards the voltage level VL output by the power supply 706. More specifically, when the NMOS device M1 is turned on (in response to its gate being pulled up) and the PMOS device M2 is turned off (in response to its gate being pulled down), the MOUT node (connected to the cathode of the laser diode 708) is pulled toward ground, which causes a current to flow through the laser diode 708, thereby causing the laser diode 708 to turn on and emit light. When the NMOS device M1 is turned off (in response to its gate being pulled down) and the PMOS device M2 is turned on (in response to its gate being pulled up), the voltage level at the MOUT node (connected to the cathode of the laser diode 708) is pulled up towards the voltage level VL output by the power supply 706, which causes the current to stop flowing through the laser diode 708, thereby causing the laser diode 708 to turn off and not emit light. An advantage of this configuration is that current does not flow through the laser diode 708 when the laser diode 708 is turned off and not emitting light, which contributes to the high efficiency of the laser diode driver 704. Another advantage of this configuration is that there is no current source in series with the main NMOS device M1. This contributes to the high efficiency of the laser diode driver 704, decreases the on-chip voltage drop while current is flowing through the laser diode 708 and saves chip area. In accordance with an embodiment, the main NMOS device M1 is a strong transistor, and the PMOS device M2 is a weak transistor. For example, the width/length ratio of the main NMOS device M1 can be between 10 and 100 times greater (e.g., 80 times greater) than the width/length ratio of the PMOS device M2.
The single-ended voltage mode laser diode driver 704, described with reference to
For the following description, the current that flows through the laser diode 708 can also be referred to as the laser current, the voltage level at the MOUT node can also be referred to as the MOUT voltage, and the voltage level VL at the output of the power supply 706 can also be referred to as the VL voltage or simply as VL. When the laser current is turned off, in response to the NMOS device M1 being turned off, due to Lenz's law inductive kickback from the laser diode 708 will attempt to boost the MOUT voltage (which in this embodiment is the cathode voltage Vk of the laser diode 708) above the voltage level VL output by the power supply 706 (which is above the voltage of one of the laser terminals). This inductive kickback, if not limited or avoided, can damage components of the laser diode driver 704, and can adversely affect how long it takes to turn off of the laser diode 708. Conventionally, as discussed above with reference to
Still referring to
When IN_P goes low (i.e., towards ground) and IN_N goes high (i.e., towards VL, or alternatively towards Vss): the output of the inverter 736 will be high, which turns off the PMOS device M2; the output of the buffer 734 will be high, which turns off the PMOS device M5; and the output of the inverter 732 will be low, which turns off the NMOS device M3 and turns on the PMOS device M4. This turning on of the PMOS device M4 pulls the gate of the main NMOS device M1 up toward the VL voltage, which turns on the main NMOS device M1. As explained above, this causes laser current to flow through the laser diode 708, in response to which the laser diode 708 turns on and emits light. The above cycle can be referred to as the turn-on cycle, since it turns on the laser diode 708. During the turn-on cycle, the gate of the main NMOS device M1 is driven high substantially instantaneously via the very strong PMOS device M4, which can also be referred to as a very strong PMOS gate drive device for the main NMOS device M1. This results in a very fast discharge of a reverse junction capacitance of the laser diode 708 through the main NMOS device M1 to ground and turns on the laser diode 708 very fast, only limited by the inductance time resistance limitation of parasitic inductances between VL, the laser diode, its package and the laser diode driver 704.
When IN_P goes high and IN_N goes low: the output of the inverter 736 will be low, which turns on the PMOS device M2; the output of the buffer 734 will be low, which turns on the PMOS device M5; and the output of the inverter 732 will be high, which turns on the NMOS device M3 and turns off the PMOS device M4. This turning off of the PMOS device M4 pulls the gate of the main NMOS device M1 down toward ground, which turns off the main NMOS device M1. As explained above, this causes laser current to stop flowing through the laser diode 708, in response to which the laser diode 708 turns off and stops emitting light. The above cycle can be referred to as the turn-off cycle, since it turns off the laser diode 708. During the turn-off cycle, the gate of the main NMOS device M1 is discharged slowly via the weak NMOS discharge device M3, and the PMOS diode connect switch M5 is closed, which connects the gate of the main NMOS device M1 to its drain, and thus causes the main NMOS device M1 to be diode-connected. Advantageously, this results in a slow actively controlled discharge of the voltage at the gate of the main NMOS device M1, which keeps the NMOS device M1 on just enough to prevent the MOUT node from spiking above the VL voltage due to Lenz's law. This slow discharge of the voltage at the gate of the main NMOS device M1 continues until currents resulting from inductances of the package, a board (to which the various devices are connected) and laser diode 708 have completely decayed and the main NMOS device M1 is completely turned off.
The PMOS device M2 is a weak switching transistor that is controlled synchronously with the high frequency modulation signal received by the laser diode driver 704 in order to provide a discharge path across the laser diode 708 to shunt the inductive kickback current from the laser diode 708 during the turn-off cycle.
The time between when the main NMOS device M1 is completely tuned off, and when the next turn on cycle begins can be referred to as the off cycle. During the off cycle, the weak PMOS device M2 is turned on, which prevents open circuit ringing that would otherwise occur due to the main NMOS device M1 being turned off. More specifically, the PMOS device M2 functions as an impedance match device to substantially eliminate ringing at the MOUT node during the off cycle. Advantageously, during the off cycle the current flowing from the power supply, through the circuitry including the laser diode driver 704 and the laser diode 708, is substantially less than during the on cycle, which contributes to the high power efficiency of the laser diode driver 704.
In accordance with specific embodiments, the timing associated with turning off and on the main NMOS device M1 and the impedance matching PMOS device M2 is precisely controlled by precisely controlling the timing of the IN_N and IN_P signals using the non-overlapping clock generator 722 and/or the clock tree 724 of the pre-driver 720. In accordance with an embodiment, overlap times during which both the NMOS device M1 and the PMOS device M2 are both turned on are substantially avoided to prevent a high current short between the output of the power supply 706 and ground. Additionally, dead times during which neither the NMOS device M1 nor the PMOS device M2 is turned on are also substantially avoided, because such dead times would allow time for inductive kickback to boost the MOUT voltage above the VL voltage.
In accordance with certain embodiments, the voltage level VL output by the power supply 706 is controlled to provide a substantially minimum amount of voltage required for the laser diode 708 to emit a predetermined desired light power. This regulates the power (and more specifically, the voltage VL) provided to the anode of the laser diode 708 to increase and preferably maximize power efficiency. This is accomplished using the power supply controller 750, which generates a feedback (FB) signal that is used to adjust the voltage level (VL) output by the power supply 706. Additional details of the power supply controller 750, according to an embodiment, will now be described with reference to
Referring to
During a calibration procedure, a digital value is stored in a calibration register 824, wherein the digital value is used to specify a desired current through the laser diode 708. This digital value is converted to a current by a current digital-to-analog converter (DAC) 822, which causes the transistor M6 to produce the reference drain-to-source voltage. A dual fully-differential input differential amplifier 816 determines a difference between the drain-to-source voltage samples produced by the sampler 812 and the reference drain-to-source voltage samples produced by the sampler 814, and outputs a signal indicative of the difference. A multiplexer 846 provides the output of the dual fully-differential input differential amplifier 816, or an amplified, filtered and/or otherwise modified version thereof, to the feedback FB input of the power supply 706 while the laser diode 708 is turned on and emitting light in response to being driven. The multiplexer 846 provides a voltage level produced by the voltage divider 844 to the feedback input of the power supply 706 when the laser diode 708 is turned off and not emitting light.
When the laser diode 708 is turned on and emitting light, a primary feedback loop produces the feedback (FB) signal that is used to adjust the voltage level VL at the voltage output of the power supply 706 to cause the actual laser diode current while the laser diode 708 is on and emitting light to be substantially equal to the desired laser diode current. In accordance with the embodiment shown in
Referring back to
The laser diode driver 704, described with reference to
In accordance with an embodiment, the laser diode driver 704 is a chip that is designed to support a flip chip package. In such a chip, core area pads greatly reduce the need for larger, lossy on-chip metal routes and improve thermal conduction from the on-chip driver circuitry to the printed circuit board (PCB) to which the laser diode driver chip is attached. Preferably, the package for the laser diode driver chip is designed to substantially minimize parasitics and maximize thermal-conduction by placing vertical routes direct from the chips pads through the package to the PCB. This enable the PCB system to deliver substantially optimal power efficiency due to low inductance and low on chip IR drop.
In accordance with an alternative embodiment, the laser diode 708 can be driven using an H-bridge configuration, in which case the main driver (i.e., output stage) would include an additional NMOS device and an additional PMOS device. In other words, an H-bridge output stage would include a pair of NMOS devices and a pair of PMOS devices connected in an H-bridge configuration. When using the H-bridge configuration, when the laser diode 708 is on an emitting light current flows from the power supply 706, through one of the PMOS devices of the output stage, through the laser diode 708, and through one of the NMOS devices of the output stage to ground. The laser diode 708 would be turned off by a reverse bias applied from the power supply, the other one of the PMOS devices and the other one of the NMOS devices of the output stage. The H-bridge configuration can be used to substantially minimize the turnoff time of the laser diode 708 at the expense of additional laser diode driver chip area and additional power relative to the single-ended configuration shown in and described with reference to
Referring back to
The high level flow diagram of
At step 906, the voltage level of the voltage output of the power supply is adjusted so that the current that flows through the laser diode when the laser diode is turned on and emitting light is substantially equal to a predetermined desired current. Step 906 can be performed, e.g., using the power supply controller 750, exemplary described of which were described above with reference to
As indicated at step 908, the voltage level at the one of the terminals of the laser diode is selectively pulled towards a second voltage level, in response to which current stops flowing through the laser diode causing the laser diode to turn off and not emit light. For example, if the anode terminal of the laser diode is connected to the voltage output of a power supply (e.g., 706) and the cathode terminal is connected to an output node of an output stage, then the voltage level at the cathode is pulled towards the voltage level at the voltage output of the power supply, in response to which current stops flowing through the laser diode causing the laser diode to turn off and not emit light. Alternatively, if the cathode terminal of the laser diode is connected to ground and the anode terminal of the laser diode is connected to an output node of an output stage, then a voltage level at the anode of the laser diode can be pulled towards ground, in response to which current stops flowing through the laser diode causing the laser diode to turn off and not emit light. Referring briefly back to
Referring again to
Referring again to
The steps shown in and described with reference to
Embodiments of the present technology have been described above with the aid of functional building blocks illustrating the performance of specified functions and relationships thereof. The boundaries of these functional building blocks have often been defined herein for the convenience of the description. Alternate boundaries can be defined so long as the specified functions and relationships thereof are appropriately performed. Any such alternate boundaries are thus within the scope and spirit of the present technology. For example, it would be possible to combine or separate some of the steps shown in
Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims. It is intended that the scope of the technology be defined by the claims appended hereto.
This application is a divisional application of U.S. patent application Ser. No. 14/078,081, entitled “POWER EFFICIENT LASER DIODE DRIVER CIRCUIT AND METHOD,” filed Nov. 12, 2013, which is incorporated herein by reference.
Number | Name | Date | Kind |
---|---|---|---|
4509130 | Menzies et al. | Apr 1985 | A |
4627620 | Yang | Dec 1986 | A |
4630910 | Ross et al. | Dec 1986 | A |
4645458 | Williams | Feb 1987 | A |
4647792 | Meslener et al. | Mar 1987 | A |
4695953 | Blair et al. | Sep 1987 | A |
4702475 | Elstein et al. | Oct 1987 | A |
4711543 | Blair et al. | Dec 1987 | A |
4751642 | Silva et al. | Jun 1988 | A |
4796997 | Svetkoff et al. | Jan 1989 | A |
4809065 | Harris et al. | Feb 1989 | A |
4817950 | Goo | Apr 1989 | A |
4843568 | Krueger et al. | Jun 1989 | A |
4893183 | Nayar | Jan 1990 | A |
4901362 | Terzian | Feb 1990 | A |
4925189 | Braeunig | May 1990 | A |
5101444 | Wilson et al. | Mar 1992 | A |
5148154 | MacKay et al. | Sep 1992 | A |
5184295 | Mann | Feb 1993 | A |
5229754 | Aoki et al. | Jun 1993 | A |
5229756 | Kosugi et al. | Jul 1993 | A |
5239463 | Blair et al. | Aug 1993 | A |
5239464 | Blair et al. | Aug 1993 | A |
5288078 | Capper et al. | Feb 1994 | A |
5295491 | Gevins | Mar 1994 | A |
5320538 | Baum | Jun 1994 | A |
5347306 | Nitta | Sep 1994 | A |
5385519 | Hsu et al. | Jan 1995 | A |
5405152 | Katanics et al. | Apr 1995 | A |
5417210 | Funda et al. | May 1995 | A |
5423554 | Davis | Jun 1995 | A |
5454043 | Freeman | Sep 1995 | A |
5469740 | French et al. | Nov 1995 | A |
5495576 | Ritchey | Feb 1996 | A |
5516105 | Eisenbrey et al. | May 1996 | A |
5524637 | Erickson et al. | Jun 1996 | A |
5534917 | MacDougall | Jul 1996 | A |
5563988 | Maes et al. | Oct 1996 | A |
5577981 | Jarvik | Nov 1996 | A |
5580249 | Jacobsen et al. | Dec 1996 | A |
5594469 | Freeman et al. | Jan 1997 | A |
5597309 | Riess | Jan 1997 | A |
5616078 | Oh | Apr 1997 | A |
5617312 | Iura et al. | Apr 1997 | A |
5638300 | Johnson | Jun 1997 | A |
5641288 | Laenglein | Jun 1997 | A |
5682196 | Freeman | Oct 1997 | A |
5682229 | Wangler | Oct 1997 | A |
5690582 | Ulrich et al. | Nov 1997 | A |
5703367 | Hashimoto et al. | Dec 1997 | A |
5704837 | Iwasaki et al. | Jan 1998 | A |
5715834 | Bergamasco et al. | Feb 1998 | A |
5748657 | Gaddis | May 1998 | A |
5875108 | Hoffberg et al. | Feb 1999 | A |
5877803 | Wee et al. | Mar 1999 | A |
5913727 | Ahdoot | Jun 1999 | A |
5933125 | Fernie | Aug 1999 | A |
5980256 | Carmein | Nov 1999 | A |
5989157 | Walton | Nov 1999 | A |
5995649 | Marugame | Nov 1999 | A |
6005548 | Latypov et al. | Dec 1999 | A |
6009210 | Kang | Dec 1999 | A |
6054991 | Crane et al. | Apr 2000 | A |
6066075 | Poulton | May 2000 | A |
6072494 | Nguyen | Jun 2000 | A |
6073489 | French et al. | Jun 2000 | A |
6077201 | Cheng et al. | Jun 2000 | A |
6098458 | French et al. | Aug 2000 | A |
6100896 | Strohecker et al. | Aug 2000 | A |
6101289 | Kellner | Aug 2000 | A |
6128003 | Smith et al. | Oct 2000 | A |
6130677 | Kunz | Oct 2000 | A |
6141463 | Covell et al. | Oct 2000 | A |
6147678 | Kumar et al. | Nov 2000 | A |
6152856 | Studor et al. | Nov 2000 | A |
6159100 | Smith | Dec 2000 | A |
6173066 | Peurach et al. | Jan 2001 | B1 |
6181343 | Lyons | Jan 2001 | B1 |
6188777 | Darrell et al. | Feb 2001 | B1 |
6215890 | Matsuo et al. | Apr 2001 | B1 |
6215898 | Woodfill et al. | Apr 2001 | B1 |
6226396 | Marugame | May 2001 | B1 |
6229913 | Nayar et al. | May 2001 | B1 |
6256033 | Nguyen | Jul 2001 | B1 |
6256400 | Takata et al. | Jul 2001 | B1 |
6259714 | Kinbara | Jul 2001 | B1 |
6283860 | Lyons et al. | Sep 2001 | B1 |
6289112 | Jain et al. | Sep 2001 | B1 |
6299308 | Voronka et al. | Oct 2001 | B1 |
6308565 | French et al. | Oct 2001 | B1 |
6316934 | Amorai-Moriya et al. | Nov 2001 | B1 |
6363160 | Bradski et al. | Mar 2002 | B1 |
6384819 | Hunter | May 2002 | B1 |
6411744 | Edwards | Jun 2002 | B1 |
6430997 | French et al. | Aug 2002 | B1 |
6476834 | Doval et al. | Nov 2002 | B1 |
6496598 | Harman | Dec 2002 | B1 |
6503195 | Keller et al. | Jan 2003 | B1 |
6539931 | Trajkovic et al. | Apr 2003 | B2 |
6570555 | Prevost et al. | May 2003 | B1 |
6633294 | Rosenthal et al. | Oct 2003 | B1 |
6640202 | Dietz et al. | Oct 2003 | B1 |
6661918 | Gordon et al. | Dec 2003 | B1 |
6681031 | Cohen et al. | Jan 2004 | B2 |
6714665 | Hanna et al. | Mar 2004 | B1 |
6731799 | Sun et al. | May 2004 | B1 |
6738066 | Nguyen | May 2004 | B1 |
6765726 | French et al. | Jul 2004 | B2 |
6788809 | Grzeszczuk et al. | Sep 2004 | B1 |
6801637 | Voronka et al. | Oct 2004 | B2 |
6873723 | Aucsmith et al. | Mar 2005 | B1 |
6876496 | French et al. | Apr 2005 | B2 |
6937742 | Roberts et al. | Aug 2005 | B2 |
6950534 | Cohen et al. | Sep 2005 | B2 |
7003134 | Covell et al. | Feb 2006 | B1 |
7036094 | Cohen et al. | Apr 2006 | B1 |
7038855 | French et al. | May 2006 | B2 |
7039676 | Day et al. | May 2006 | B1 |
7042440 | Pryor et al. | May 2006 | B2 |
7050606 | Paul et al. | May 2006 | B2 |
7058204 | Hildreth et al. | Jun 2006 | B2 |
7060957 | Lange et al. | Jun 2006 | B2 |
7113918 | Ahmad et al. | Sep 2006 | B1 |
7121946 | Paul et al. | Oct 2006 | B2 |
7170492 | Bell | Jan 2007 | B2 |
7184048 | Hunter | Feb 2007 | B2 |
7202898 | Braun et al. | Apr 2007 | B1 |
7222078 | Abelow | May 2007 | B2 |
7227526 | Hildreth et al. | Jun 2007 | B2 |
7259747 | Bell | Aug 2007 | B2 |
7308112 | Fujimura et al. | Dec 2007 | B2 |
7317836 | Fujimura et al. | Jan 2008 | B2 |
7348963 | Bell | Mar 2008 | B2 |
7359121 | French et al. | Apr 2008 | B2 |
7367887 | Watabe et al. | May 2008 | B2 |
7379563 | Shamaie | May 2008 | B2 |
7379566 | Hildreth | May 2008 | B2 |
7389591 | Jaiswal et al. | Jun 2008 | B2 |
7412077 | Li et al. | Aug 2008 | B2 |
7421093 | Hildreth et al. | Sep 2008 | B2 |
7430312 | Gu | Sep 2008 | B2 |
7436496 | Kawahito | Oct 2008 | B2 |
7450736 | Yang et al. | Nov 2008 | B2 |
7452275 | Kuraishi | Nov 2008 | B2 |
7460690 | Cohen et al. | Dec 2008 | B2 |
7489812 | Fox et al. | Feb 2009 | B2 |
7536032 | Bell | May 2009 | B2 |
7555142 | Hildreth et al. | Jun 2009 | B2 |
7560701 | Oggier et al. | Jul 2009 | B2 |
7570805 | Gu | Aug 2009 | B2 |
7574020 | Shamaie | Aug 2009 | B2 |
7576727 | Bell | Aug 2009 | B2 |
7590262 | Fujimura et al. | Sep 2009 | B2 |
7593552 | Higaki et al. | Sep 2009 | B2 |
7598942 | Underkoffler et al. | Oct 2009 | B2 |
7607509 | Schmiz et al. | Oct 2009 | B2 |
7620202 | Fujimura et al. | Nov 2009 | B2 |
7668340 | Cohen et al. | Feb 2010 | B2 |
7680298 | Roberts et al. | Mar 2010 | B2 |
7683954 | Ichikawa et al. | Mar 2010 | B2 |
7684592 | Paul et al. | Mar 2010 | B2 |
7701439 | Hillis et al. | Apr 2010 | B2 |
7702130 | Im et al. | Apr 2010 | B2 |
7704135 | Harrison, Jr. | Apr 2010 | B2 |
7710391 | Bell et al. | May 2010 | B2 |
7729530 | Antonov et al. | Jun 2010 | B2 |
7746345 | Hunter | Jun 2010 | B2 |
7760182 | Ahmad et al. | Jul 2010 | B2 |
7809167 | Bell | Oct 2010 | B2 |
7834846 | Bell | Nov 2010 | B1 |
7852262 | Namineni et al. | Dec 2010 | B2 |
RE42256 | Edwards | Mar 2011 | E |
7898522 | Hildreth et al. | Mar 2011 | B2 |
8035612 | Bell et al. | Oct 2011 | B2 |
8035614 | Bell et al. | Oct 2011 | B2 |
8035624 | Bell et al. | Oct 2011 | B2 |
8072470 | Marks | Dec 2011 | B2 |
20020071468 | Sandstrom | Jun 2002 | A1 |
20030016711 | Crawford | Jan 2003 | A1 |
20060132183 | Lim | Jun 2006 | A1 |
20080026838 | Dunstan et al. | Jan 2008 | A1 |
20110085576 | Crawford et al. | Apr 2011 | A1 |
20110205522 | Snow | Aug 2011 | A1 |
20120017153 | Matsuda et al. | Jan 2012 | A1 |
20120056982 | Katz | Mar 2012 | A1 |
20130049628 | Kwong | Feb 2013 | A1 |
20150130903 | Thompson et al. | May 2015 | A1 |
Number | Date | Country |
---|---|---|
101254344 | Jun 2010 | CN |
0583061 | Feb 1994 | EP |
2002191 | Feb 1979 | GB |
H03-151679 | Jun 1991 | JP |
08044490 | Feb 1996 | JP |
201316822 | Apr 2013 | TW |
9310708 | Jun 1993 | WO |
9717598 | May 1997 | WO |
9944698 | Sep 1999 | WO |
Entry |
---|
Thompson, Marc T., et al., “High Power Laser Diode Driver Based on Power Converter Technology,” IEEE Transactions on Power Electronics, vol. 12, No. 1, Jan. 1997, 7 pages. |
Koechner, Walter, “Solid State Laser Engineering,” Springer Series in Optical Sciences, retrieved on May 29, 2013, [http://icole.mut.ac.ir/downloads/SC/W06/Solid%20State%20Laser%20Engineering.pdf], 765 pages. |
Tan, Tun S., et al., “Flip-Chip Photodetector for High-Speed Communications Instrumentation,” The Hewlett-Packard Journal, Dec. 1997, 10 pages. |
Gao, Shubo, “New technologies for lead-free flip chip assembly,” Department of Electrical and Electronic Engineering, Imperial College London, retrieved May 29, 2013, [http://www3.imperial.ac.uk/pls/portallive/docs/1/5067986.PDF], 137 pages. |
MOSFETs in ICs⇒Scaling, Leakage and Other Topics, [Hu_cho7v3.fm], Feb. 13, 2009, 32 pages. |
International Search Report and Written Opinion dated dated May 11, 2015, in PCT Application No. PCT/US2014/063617 filed Nov. 3, 2014, 19 Pages. |
Amendment dated Aug. 21, 2015, in PCT Application No. PCT/US2014/063617 filed Nov. 3, 2014, 19 Pages. |
Written Opinion dated Nov. 16, 2015, in PCT Application No. PCT/US2014/063617 filed Nov. 3, 2014. |
Response to Written Opinion filed Jan. 15, 2016, in PCT Application No. PCT/US2014/063617 filed Nov. 3, 2014. |
International Preliminary Report on Patentability Issued in PCT Application No. PCT/US2014/063617 dated Feb. 5, 2016. |
Preliminary Amendment filed Nov. 19, 2015 in U.S. Appl. No. 14/078,081, filed Nov. 12, 2013. |
Restriction dated Apr. 8, 2016 in U.S. Appl. No. 14/078,081, filed Nov. 12, 2013. |
Response to Restriction filed Apr. 14, 2016 in U.S. Appl. No. 14/078,081, filed Nov. 12, 2013. |
Office Action dated May 12, 2016 in U.S. Appl. No. 14/078,081, filed Nov. 12, 2013. |
Response to Office Action filed Jun. 8, 2016 in U.S. Appl. No. 14/078,081, filed Nov. 12, 2013. |
Office Action dated Sep. 23, 2016 in U.S. Appl. No. 14/078,081, filed Nov. 12, 2013. |
Response to Office Action filed Nov. 9, 2016 in U.S. Appl. No. 14/078,081, filed Nov. 12, 2013. |
Notice of Allowance dated Dec. 13, 2016 in U.S. Appl. No. 14/078,081 filed Nov. 12, 2013. |
Kanade et al., “A Stereo Machine for Video-rate Dense Depth Mapping and Its New Applications”, IEEE Computer Society Conference on Computer Vision and Pattern Recognition, 1996, pp. 196-202,The Robotics Institute, Carnegie Mellon University, Pittsburgh, PA. |
Miyagawa et al., “CCD-Based Range Finding Sensor”, Oct. 1997, pp. 1648-1652, vol. 44 No. 10, IEEE Transactions on Electron Devices. |
Rosenhahn et al., “Automatic Human Model Generation”, 2005, pp. 41-48, University of Auckland (CITR), New Zealand. |
Aggarwal et al., “Human Motion Analysis: A Review”, IEEE Nonrigid and Articulated Motion Workshop, 1997, University of Texas at Austin, Austin, TX. |
Shao et al., “An Open System Architecture for a Multimedia and Multimodal User Interface”, Aug. 24, 1998, Japanese Society for Rehabilitation of Persons with Disabilities (JSRPD), Japan. |
Kohler, “Special Topics of Gesture Recognition Applied in Intelligent Home Environments”, In Proceedings of the Gesture Workshop, 1998, pp. 285-296, Germany. |
Kohler, “Vision Based Remote Control in Intelligent Home Environments”, University of Erlangen-Nuremberg/Germany, 1996, pp. 147-154, Germany. |
Kohler, “Technical Details and Ergonomical Aspects of Gesture Recognition applied in Intelligent Home Environments”, 1997, Germany. |
Hasegawa et al., “Human-Scale Haptic Interaction with a Reactive Virtual Human in a Real-Time Physics Simulator”, Jul. 2006, vol. 4, No. 3, Article 6C, ACM Computers in Entertainment, New York, NY. |
Qian et al., “A Gesture-Driven Multimodal Interactive Dance System”, Jun. 2004, pp. 1579-1582, IEEE International Conference on Multimedia and Expo (ICME), Taipei, Taiwan. |
Zhao, “Dressed Human Modeling, Detection, and Parts Localization”, 2001, The Robotics Institute, Carnegie Mellon University, Pittsburgh, PA. |
He, “Generation of Human Body Models”, Apr. 2005, University of Auckland, New Zealand. |
Isard et al., “CONDENSATION—Conditional Density Propagation for Visual Tracking”, 1998, pp. 5-28, International Journal of Computer Vision 29(1), Netherlands. |
Livingston, “Vision-based Tracking with Dynamic Structured Light for Video See-through Augmented Reality”, 1998, University of North Carolina at Chapel Hill, North Carolina, USA. |
Wren et al., “Pfinder: Real-Time Tracking of the Human Body”, MIT Media Laboratory Perceptual Computing Section Technical Report No. 353, Jul. 1997, vol. 19, No. 7, pp. 780-785, IEEE Transactions on Pattern Analysis and Machine Intelligence, Caimbridge, MA. |
Breen et al., “Interactive Occlusion and Collision of Real and Virtual Objects in Augmented Reality”, Technical Report ECRC-95-02, 1995, European Computer-Industry Research Center GmbH, Munich, Germany. |
Freeman et al., “Television Control by Hand Gestures”, Dec. 1994, Mitsubishi Electric Research Laboratories, TR94-24, Caimbridge, MA. |
Hongo et al., “Focus of Attention for Face and Hand Gesture Recognition Using Multiple Cameras”, Mar. 2000, pp. 156-161, 4th IEEE International Conference on Automatic Face and Gesture Recognition, Grenoble, France. |
Pavlovic et al., “Visual Interpretation of Hand Gestures for Human-Computer Interaction: A Review”, Jul. 1997, pp. 677-695, vol. 19, No. 7, IEEE Transactions on Pattern Analysis and Machine Intelligence. |
Azarbayejani et al., “Visually Controlled Graphics”, Jun. 1993, vol. 15, No. 6, IEEE Transactions on Pattern Analysis and Machine Intelligence. |
Granieri et al., “Simulating Humans in VR”, The British Computer Society, Oct. 1994, Academic Press. |
Brogan et al., “Dynamically Simulated Characters in Virtual Environments”, Sep./Oct. 1998, pp. 2-13, vol. 18, Issue 5, IEEE Computer Graphics and Applications. |
Fisher et al., “Virtual Environment Display System”, ACM Workshop on Interactive 3D Graphics, Oct. 1986, Chapel Hill, NC. |
“Virtual High Anxiety”, Tech Update, Aug. 1995, pp. 22. |
Sheridan et al., “Virtual Reality Check”, Technology Review, Oct. 1993, pp. 22-28, vol. 96, No. 7. |
Stevens, “Flights into Virtual Reality Treating Real World Disorders”, The Washington Post, Mar. 27, 1995, Science Psychology, 2 pages. |
“Simulation and Training”, 1994, Division Incorporated. |
English Machine-translation of Japanese Publication No. JP08-044490 published on Feb. 16, 1996. |
“Office Action and Search Report Issued in Taiwan Patent Application No. 103134437”, dated Mar. 15, 2018, 12 Pages. |
Number | Date | Country | |
---|---|---|---|
20170187164 A1 | Jun 2017 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 14078081 | Nov 2013 | US |
Child | 15456786 | US |