Wireless camera flash synchronizer system and method

Information

  • Patent Grant
  • 8559804
  • Patent Number
    8,559,804
  • Date Filed
    Tuesday, April 3, 2012
    12 years ago
  • Date Issued
    Tuesday, October 15, 2013
    11 years ago
Abstract
An external device for wirelessly synchronizing a remote device to image acquisition of a camera with switching of a transceiver from receive mode to transmit mode in response to receipt of a first signal by the external device generated after a trigger of the camera is activated. The external device includes a wireless communication functionality and a connector for connecting the external device to a port of the camera providing access to the first signal. The external device includes auto mode switcher for switching the transceiver from a receive mode to a transmit mode. A system including a camera and an external device configured to switch from receive mode to transmit mode in response to a signal from the camera generated after a trigger of the camera is activated.
Description
FIELD OF THE INVENTION

The present invention generally relates to the field of camera flash synchronization. In particular, the present invention is directed to a wireless camera flash synchronizer system and method.


BACKGROUND

Synchronization of a camera flash to the acquisition of an image can be done wirelessly between a camera and a remote flash device or other device requiring synchronization. Typically, prior synchronizers require a user to manually switch the device from a receive mode to a transmit mode utilizing a physical switch on the device. The speed demands imposed by cameras require near instantaneous transmission of a synchronization command to the remote device in order for the remote device to synchronize properly with the camera. Thus, synchronizers are typically manually set in the transmit mode to save the time of switching the synchronizer from a receive mode to a transmit mode upon a need to transmit. This type of setting requires a manual input to the synchronizer. One prior synchronizer, the FlashWizard II manufactured by LPA Design of South Burlington, Vt., includes separate radio circuits for transmitting and receiving (e.g., two separate oscillator elements, one for receive and one for transmit, that are both active at the same time). Having separate radio circuits can add to the cost of the synchronizer and increase power consumption.


SUMMARY OF THE DISCLOSURE

In one embodiment, an external device for wirelessly synchronizing a remote device to image acquisition of a camera is provided. The external device includes a wireless communication functionality having a transmit mode and a receive mode; a first connector for connecting the external device to a port of a camera that provides a connection to a first signal, the first signal generated after a trigger of the camera is activated; and an auto mode switcher for switching the transceiver from the receive mode to the transmit mode in response to receipt of the first signal by the external device via the first connector.


In another embodiment, an external device for wirelessly synchronizing a remote device to image acquisition of a camera is provided. The external device includes a wireless communication functionality having a transmit mode and a receive mode; a first connector for connecting the external device to a port of a camera that provides a connection to a first signal, the first signal generated after a trigger of the camera is activated and including information for synchronizing a remote device to an image acquisition by the camera, the first connector configured to connect to at least one of a hotshoe connector of the camera, a PC synchronization connector of the camera, and a multi-contact accessory port of the camera; and an auto mode switcher for switching the transceiver from the receive mode to the transmit mode in response to receipt of the first signal by the external device via the first connector.


In yet another embodiment, a system for synchronizing a remote device to photographic image acquisition is provided. The system includes a camera having an external port providing access to a first signal, the first signal generated after a trigger of the camera is activated; and a device for connection to the camera, the device including: a wireless communication functionality having a transmit mode and a receive mode; a first connector for connecting the device to the external port of the camera; and an auto mode switcher for switching the transceiver from the receive mode to the transmit mode in response to receipt of the first signal by the device via the first connector.





BRIEF DESCRIPTION OF THE DRAWINGS

For the purpose of illustrating the invention, the drawings show aspects of one or more embodiments of the invention. However, it should be understood that the present invention is not limited to the precise arrangements and instrumentalities shown in the drawings, wherein:



FIG. 1 illustrates one embodiment of a method of wirelessly communicating a camera synchronization to a remote device from a camera body;



FIG. 2 illustrates one embodiment of a wireless camera flash synchronizer; and



FIG. 3 illustrates another embodiment of a wireless camera flash synchronizer.





DETAILED DESCRIPTION

A single oscillator system and method is provided that automatically switches from a receive mode to a transmit mode upon the detection of a synchronization (synch) signal of a camera body.



FIG. 1 illustrates one embodiment of a method 100 of wirelessly communicating a camera synchronization to a remote device from a camera body. At step 105, an oscillator element of a wireless camera flash synchronizer is set to a receive mode. Various embodiments of a wireless camera flash synchronizer are set forth below (e.g., wireless camera flash synchronizer 200, 300 of FIGS. 2 and 3, respectively). A wireless camera flash synchronizer may be physically connected to the camera body in a variety of ways. In one example, a wireless camera flash synchronizer may be connected to a synchronization signal connector of the camera body. Examples of a synchronization signal connector include, but are not limited to, a camera hotshoe, a camera PC connector, a direct wiring to the internal circuitry of the camera body, and any combinations thereof. It should be noted that the term PC connector is well understood to those of ordinary skill to refer to a camera synchronization connector, such as a connector defined by the ISO 519 standard. The “PC” of this term does not refer to a personal computer.


A wireless camera flash synchronizer may include one or more oscillator elements. However, only one of the oscillator elements is utilized in the steps of method 100. For example, in addition to an oscillator element for wireless communication, a synchronizer may include an processing oscillator utilized by a processing element, but not used for wireless communication. An oscillator element may be included in a transceiver circuit. A variety of transceiver circuits suitable for use in a synchronizer according to the present disclosure will be known to those of ordinary skill from the description herein. Example transceiver circuits are discussed below. An oscillator element may include one or more oscillator circuits that are all utilized at a given time for either transmit or receive function. In one example, an oscillator element includes a single oscillator circuit that can be set to one of a wireless mode, including a wireless receive mode and a wireless transmit mode. In another example, an oscillator element includes two or more oscillator circuits that work together and can be set together to one of a wireless mode, including a wireless receive mode and a wireless transmit mode. In either of these examples, the oscillator element does not wirelessly transmit and receive at the same time.


The setting of the oscillator element to a receive mode (e.g., as in step 105) may occur in a variety of ways. In one example, the oscillator element is set to a receive mode as a default mode of the synchronizer (e.g., at power on of the synchronizer). In another example, the oscillator element is manually physically switched (e.g., utilizing a button or other physical switching device on the synchronizer) to a receive mode. In yet another example, the oscillator element is automatically switched to a receive mode after an event occurs, such as after the synchronizer transmits a wireless signal to a remote device. In still another example, a receive frequency coding is loaded into a transceiver having the oscillator element and latching the receive frequency coding into a register utilized by the transceiver for determining a frequency for wireless reception and/or a mode status for the transceiver. In such an example, a receive frequency coding may include one or more bits of data representing a frequency for reception and/or one or more bits of data representing that the transceiver (e.g., and its oscillator element) should be in a receive mode. Example signals that may be received by a synchronizer (e.g., from a remote device) include, but are not limited to, a confirmation of existence of a remote device, a confirmation of flash firing from a remote device, a trigger command to start the image acquisition process of the camera device from a remote trigger (e.g., a trigger in a remote light sensor, a wireless handheld trigger, etc.), and any combinations thereof. Having a synchronizer that can stay in a receive mode until a synch signal is received and then switch to a transmit mode is desirable. In one example, such a synchronizer eliminates the need for a physical transmit/receive control for manual actuation on the synchronizer device


At step 110, a synch signal of the camera body is detected via the synchronization connector of the camera body to which the synchronizer is physically connected. A synch signal is a signal recognized by those skilled in the art. Typically, a synch signal is generated by a camera device after a trigger of the camera is activated and is utilized to synchronize a flash device (or other device) to the acquisition of an image (e.g., the open state of a shutter) by the camera. In one example, a synch signal is generated by a camera device at the point where a first curtain of a shutter reaches a fully open position. In another example, a camera device without a shutter may generate a synch signal at a point at or closely after the beginning of exposure of an exposure element (e.g., a CCD of a digital camera).


There may be a relatively great amount of time between the reception of a trigger to acquire an image (e.g., a trigger command received from a remote trigger or from the trigger of the camera body itself) and actual image acquisition. The receipt of a trigger command and the generation of a synch signal occur at different times in the image acquisition process. A synch signal is typically generated after a trigger command is provided.


At step 115, in response to the detecting of the synch signal, the oscillator element is automatically switched from the receive mode to a transmit mode. An oscillator element may be switched from a receive mode to a transmit mode in a variety of ways that will be understood from the disclosure herein. In one example, a synchronizer, such as one of the exemplary synchronizers discussed below with respect to FIGS. 2 and 3, is configured with appropriate circuitry and/or machine executable instructions for automatically switching an oscillator element to a transmit mode upon detecting a synch signal via a physical connection of the synchronizer to a synchronization connector of a camera body. In another example, a transceiver having an oscillator element is loaded with a transmit frequency coding that may include data for setting an operating mode of the oscillator and/or transceiver. An exemplary transmit frequency coding may include an instruction to the oscillator/transceiver of a frequency of operation for transmission and/or an instruction to the oscillator/transceiver to operate in a transmit mode. Such instructions may include any number of one or more data bits. In yet another example, the loading of a transmit frequency coding occurs before a synch signal is detected (e.g., as in step 110). In still another example, a transmit frequency coding is latched into a register utilized by a transceiver to set an operating mode. In such an example, the latching may occur after the detection of the synch signal (e.g., during step 115).


The time from the point at which a synch signal is generated by a camera device to when a flash (or other remote device) must fire can be very fast. This time may depend on many variables. In one example, a camera device's image acquisition time is limited in part by the length of the opening of an aperture (e.g., time of shutter opening), or other limitation (e.g., programmed image acquisition time of a shutterless digital camera).


In one exemplary embodiment, it may be important to limit the amount of time between a synchronizer detecting a synch signal via a synchronization connector and the synchronizer being switched from receive mode to a transmit mode (e.g., the synchronizer being ready to wirelessly transmit an indicator of the synch signal to a remote device). In one example, being ready to wirelessly transmit a synch signal includes being ready to stably transmit on a particular transmit frequency. Any one of a variety of transmit frequencies may be used for transmission. In one example, a stable frequency state is indicated by a PLL (Phase Lock Loop) of the transceiver reaching a “lock” condition. A PLL lock may be measured when frequency error is sustained at a particular level. In one example, a phase lock may be detected when a frequency error is sustained at less than 20 kHz error. Other measures of frequency stability may be used to indicate that the synchronizer is in a transmit mode.


The time utilized from the detection of a synch signal to the completion of switching to a transmit mode may depend on a variety of factors (e.g., hardware and operating environment) and influence performance of the synchronizer in synchronizing a remote device with image acquisition. In one example, switching to a transmit mode (as in step 115) is completed in about 10 microseconds to about 1 millisecond. Performance of the synchronizer may be increased by decreasing the time necessary to switch to a transmit mode. Other example times for completion of switching to a transmit mode after detection of a synch signal include, but are not limited to, a switch completion time of less than about 1 millisecond, a switch completion time of less than about 500 microseconds, a switch completion time of less than about 200 microseconds, a switch completion time of less than about 100 microseconds, a switch completion time of less than about 20 microseconds, and a switch completion time of less than about 10 microseconds. Other example times for switching to a transmit mode include, but are not limited to, less than 1 millisecond, less than 100 microseconds, and less than 20 microseconds.


At step 120, a synchronization data is wirelessly transmitted from the synchronizer to a remote device. Optionally, after transmission, step 105 may be repeated and the oscillator element may be set again to a receive mode. In one example, this may occur at a predetermined time after the completion of the transmission to the remote device.


A synchronization data may be any information that can be wirelessly transmitted to a remote device to synchronize the remote device with the camera body to which the synchronizer is connected. Examples of synchronization include, but are not limited to, firing a flash at about the time of image acquisition by a camera device (e.g., firing the flash at least for some of the time that a shutter of the camera device is open), instigating image acquisition by a remote camera device in conjunction with the image acquisition of the camera device to which the synchronizer is connected, and any combinations thereof. Examples of synchronization data include, but are not limited to, one or more data elements based on a detected camera body synch signal, one or more data elements that include a detected camera body synch signal, and any combinations thereof.


For the sake of convenience, the present disclosure frequently discusses a remote device that is a flash device. However, it is contemplated that a remote device that may be synchronized by a wireless synchronizer of the present disclosure may include any one or more of a variety of remote devices. Examples of a remote device include, but are not limited to, a flash device, a non-flash lighting device, a remote camera device (e.g., a remote camera device to be synchronized with the operation of the camera body connected to the synchronizer), an exposure meter, and any combinations thereof. Example flash devices include, but are not limited to, an internal flash, external flash, local flash, and a remote flash device. In one example, a flash device may be internal, external, local, and/or remote to the camera device.


Depending on the mode of wireless transmission and the distance to the remote device, an amount of time passes during the transmission of the synchronization data to the remote device. In one example, the remote device (e.g., a flash device) then prepares to fire. In a flash device example, the flash fires over a specific amount of time.



FIG. 2 illustrates one embodiment of a synchronizer 200. Synchronizer 200 includes a transceiver 205 having an oscillator element 210 that has a receive mode and a transmit mode. Oscillator element 210 is configured to allow only one of the receive mode and the transmit mode at a time. Various transceivers suitable for use with a synchronizer of the present disclosure (e.g., synchronizer 200) will be recognized by those skilled in the art from a review of the present disclosure. One example of a transceiver includes a transceiver radio chip, model no. ADF7020-1, available from Analog Devices of Norwood, Mass. Another example of a transceiver includes a transceiver radio chip, model no. ADF7020, also available from Analog Devices. Yet another example of a transceiver includes a transceiver radio chip, model no. CC1100 from ChipCon/TI. Still another example of a transceiver includes a transceiver radio chip, model no CC1110 from ChipCon/TI.


Transceiver 205 may include one or more connectors 215 for communicating with the circuitry of the transceiver. Examples of a connector for communicating with a transceiver include, but are not limited to, a data connector (e.g., for communicating data to a transceiver for wireless transmission and/or for communicating data wirelessly received by a transceiver to a device, such as a processor; communicating instructions to a transceiver, etc.), a clock connector (e.g., for connecting to a clock of a processor), a latch connector (e.g., for receiving a latch instruction from a processor to latch one or more pieces of information), and any combinations thereof. One or more connectors 215 may include any electrical connector medium. In one example, one or more connectors 215 may include printed circuit board traces that connect circuit elements.


Synchronizer 200 also includes one or more synchronization signal connectors 220. As discussed above with respect to method 100 of FIG. 1, a synchronization signal connector is any connector that is configured to connect to a synchronization signal of a camera body (e.g., via a synchronization signal connector of the camera body). Examples of a synchronization signal connector include, but are not limited to, a camera hotshoe, a camera PC connector, a direct wiring to the internal circuitry of the camera body, multi-contact accessory ports that include synchronization signal, and any combinations thereof. Via such a connection, synchronizer 200 may detect a synch signal of camera body 225. Synchronizer 200 is shown as being connected to camera body 225 via a hotshoe connector 230 and synchronization signal connector 220. In such an example, synchronization signal connector 220 is configured to connect with hotshoe connector 230. As part of this configuration, synchronization signal connector 220 may include a male hotshoe assembly sized and shaped to mate with a hotshoe connector, such as hotshoe connector 230. In one example, a male hotshoe assembly may be positioned on and/or within an exterior casing of a synchronizer (e.g., synchronizer 200). It is contemplated that a synchronizer, such as synchronization signal connector 220 may include (e.g., in addition to a hotshoe configuration or as a replacement for a hotshoe configuration as shown in FIG. 2) a configuration that is sized and shaped to connect (directly and/or via a wire) to a PC connector of camera body 225. In one example, a PC connector configuration for synchronization signal connector 220 includes a standard female microphone jack. It is also contemplated that a synchronizer may be shaped and sized to be inserted (in its entirety or in part) within camera body 225. In one such example, synchronization signal connector 220 includes wiring and/or other circuitry for directly connecting synchronizer 200 to internal synchronization circuitry and/or wiring of camera body 225.


Transceiver 205 is in electrical communication with an auto mode switcher 235 via one or more of connectors 215. Auto mode switcher 235 is also electrically connected to synchronization signal connector 220 via connection 240. Auto mode switcher 235 includes circuitry and/or machine executable instructions for automatically switching oscillator 210 and/or transceiver 205 to a transmit mode when a synch signal is detected via synchronization signal connector 220. One exemplary embodiment of such circuitry and one exemplary embodiment of such machine executable instructions are described below with respect to synchronizer 300 of FIG. 3. Other embodiments and variants of such circuitry will be understood by those of ordinary skill from the present disclosure.


Auto mode switcher 235 is shown as being separate from transceiver 205. It is contemplated that all or part of the circuitry and/or machine executable instructions of auto mode switcher 235 may be part of transceiver 205.


Auto mode switcher 235 may be configured to automatically switch oscillator 210 and potentially other components of transceiver 205 from a receive mode to a transmit mode and to capable of transmission of synchronization data to a remote device within a specific amount of time of the detection of a synch signal from camera 225 via synchronization signal connector 220. In one example, auto mode switcher 235 is configured to switch to a transmit mode in less than about 1 millisecond of detection of a synch signal. In another example, auto mode switcher 235 is configured to switch to a transmit mode in less than about 500 microseconds of detection of a synch signal. In yet another example, auto mode switcher 235 is configured to switch to a transmit mode in less than about 200 microseconds of detection of a synch signal. In still another example, auto mode switcher 235 is configured to switch to a transmit mode in less than about 100 microseconds of detection of a synch signal. In still yet another example, auto mode switcher 235 is configured to switch to a transmit mode in less than about 20 microsecond of detection of a synch signal. In a further example, auto mode switcher 235 is configured to switch to a transmit mode in less than about 10 microsecond of detection of a synch signal. Other examples of configurations of auto mode switcher 235 include, but are not limited to, a configuration to switch to a transmit mode in less than 1 millisecond, a configuration to switch to a transmit mode in less than 100 microseconds, and a configuration to switch to a transmit mode in less than 20 microseconds.


In an alternative embodiment, synchronizer 200 may be configured to transmit a signal including information representing synchronization data, to a remote device utilizing a single modulated frequency for each transmission of data to the remote device. In one example, transceiver 205 may be instructed (e.g., via auto mode switcher 235) to utilize a single modulated frequency for a given channel of transmission. In one such example, transceiver 205 operates differently than a radio device utilizing spread spectrum technology. Spread spectrum technology often has inferior performance in sending a synch signal partly because of the time necessary for a spread spectrum technique to resynchronize the radio link with the remote receiver and the significant radio traffic on these spread spectrum bands.



FIG. 3 illustrates another embodiment of a synchronizer 300. Except where indicated, synchronizer 300 and its component elements includes aspects and features that are similar to those of synchronizer 200 of FIG. 2.


Synchronizer 300 includes a transceiver 305 having an oscillator element 310 that has a receive mode and a transmit mode. Oscillator element 310 is configured to allow only one of the receive mode and the transmit mode at a time. Transceiver 305 includes one or more connectors 315 for providing electrical communication to and/or from transceiver 305.


Synchronizer 300 also includes a synchronization signal connector 320. Here synchronization signal connector 320 is shown as a hotshoe connector for connecting to a camera body 325 via a hotshoe synchronization signal connector 330 of camera body 325. When synchronization signal connector 320 is connected to synchronization signal connector 330, it is possible to detect a synch signal of camera 325. Synchronizer 300 may also include a synchronization signal connector 320′. In one example, as shown in FIG. 3, synchronization signal connector 320′ is configured to connect to a PC connector synchronization signal connector 330′ of camera body 325. When synchronization signal connector 320′ is connected to synchronization signal connector 330′, it is possible to detect a synch signal of camera 325.


Transceiver 305 is electrically connected with an auto mode switcher 335 via connector 315. In one example, such an electrical connection may include a connection to one or more of a data connector, a clock connector, and a latch connector (e.g., using circuit board traces as connectors). Auto mode switcher 335 is also in electrical communication with synchronization signal connector 320 via electrical connection 340.


Auto mode switcher 335 may include a processor 345. Example processors include, but are not limited to, a microcontroller, embedded controller, CPU, digital signal processor, and any combinations thereof. In one example, auto mode switcher includes an AVR processor available from Atmel Semiconductor. Processor 345 and auto mode switcher 335 are shown in FIG. 3 as being separate circuit elements from transceiver 305. In an alternate embodiment, either a processor or any other part of auto mode switcher 335 may be combined in a in a single integrated circuit element with a transceiver. Examples of a combination processor and transceiver circuit include, but are not limited to, a CC1100 model chip and a CC1110 model chip both from ChipCon/TI.


Auto mode switcher 335 may also include a memory 350. Memory 350 may be integrated with or separate from auto mode switcher 335. In one example such as that shown in FIG. 3, auto mode switcher 335 includes a processor having a built-in memory. In another example, auto mode switcher 335 includes a processor having a memory that is separate from the processor but part of auto mode switcher 335. In yet another example, auto mode switcher 335 includes a processor that is part of auto mode switcher 335 and that is associated with (e.g., electrically connected with) a memory that is separate from auto mode switcher 335. It is contemplated that multiple memory elements (e.g., memory element 350) may be present in synchronizer 300.


In one example, a memory (e.g., memory 350) includes a machine readable medium. Examples of a machine readable medium include, but are not limited to, a random access memory, a read only memory, a memory drive device, an EPROM, an EEPROM, a compact disc (e.g., read only CD-ROM, writeable CD, re-writable CD, DVD, etc.), a magneto-optical disc and/or card, a flash memory (e.g., a thumb drive), a removable memory (e.g., a memory card, such as an SD-card), and any combinations thereof.


Memory 350 may include instructions 355 for causing a machine (e.g., processor 345) to perform any one of the methodologies of the present disclosure. In one example, memory 350 includes instructions 360 for programming transceiver 305 to a receive mode. Instructions 360 may include a digital receive frequency coding (e.g., a fractional N coding) or other structure representing a receive frequency of operation for a transceiver, such as transceiver 305. In one example, a digital receive frequency coding includes a 32-bit element that may be communicated (e.g., as a signal) to a transceiver to instruct the transceiver of the receive frequency to be utilized. In another example, memory 350 includes instructions 365 for programming transceiver 305 to a transmit mode. Instructions 365 may include a digital transmit frequency coding or other structure representing a transmit frequency of operation for a transceiver, such as transceiver 305. In one example, a digital transmit frequency coding includes a 32-bit element that may be communicated (e.g., as a signal) to a transceiver to instruct the transceiver of the transmit frequency to be utilized.


In one aspect, an instruction for setting a particular frequency for transmit or receive, (e.g., a digital frequency coding) may be provided in a variety of ways. In one example, an instruction for setting a particular frequency is set in one or more tables (e.g., a table stored in a memory, such as memory 350). In another example, an instruction for setting a particular frequency is calculated using an algorithm or other set of instructions (e.g., an algorithm stored in a memory, such as memory 350, and utilized by a processor, such as processor 345). A synchronizer may have an ability to use any number of frequencies for transmit and/or receive modes. In one example, a synchronizer includes instructions for a limited set of frequencies and/or the ability to calculate a limited set of such instructions. In another example, an algorithm provides an ability to determine an unlimited number of instructions for an unlimited number of frequencies. In yet another example, instructions for determining one or more frequencies for transmit and/or receive mode may be upgradeable (e.g., modifiable at a time after initial programming of a particular synchronizer).


In one embodiment, a synchronizer (e.g., synchronizer 300) transmits utilizing oscillator 310 operating on a first frequency and receives utilizing oscillator 310 operating on a second frequency (i.e., oscillator 310 in a receive mode is set at a frequency different from the transmit frequency for oscillator 310, such as in a heterodyne or a superheterodyne transceiver). In one example of such an embodiment, switching from a receive mode to a transmit mode requires instructing the synchronizer which frequency to utilize for transmit mode. A synchronizer may utilize one or more receive oscillator frequencies that are each offset from a corresponding transmit frequency by a set frequency difference. This difference is known as the intermediate frequency. In one example, a set frequency difference is about 200 kiloHertz (kHz). In one such example, to receive at a frequency of 300 MHz, the receive RF oscillator is set 200 kHz below or above the frequency of the signal to be wirelessly received (which is also the transmit frequency). In one aspect, a synchronizer may include one or more settings for instructing the synchronizer to utilize one or more predetermined channels. In such a case, a synchronizer may include a manual or electronic interface for a user to select a given channel of operation. In one example, a synchronizer includes four predetermined channels of operation, each including a frequency for wireless reception and a frequency of transmission (in some cases the same frequency as reception), which in turn determine the oscillator frequencies for transmit mode and receive mode. A given frequency for a channel may be determined by an algorithm or other instruction stored in a memory, such as memory 350. In another example, a synchronizer is configured to utilize a reception/transmission frequency including one or more frequencies between about 344 megahertz (MHz) and about 354 MHz, with channels spaced at about 0.5 MHz intervals and corresponding oscillator frequencies (e.g., frequencies of a transmit mode and a receive mode) offset from each other by about 200 kHz. In yet another example, a synchronizer is configured to utilize a reception/transmission frequency including one or more frequencies between about 433.4 MHz to about 434.4 MHz.


Synchronizer 300 may include an antenna 370. Transceiver 305 is shown in electrical communication with antenna 370 for providing wireless communication to and/or from transceiver 305. A variety of antennae are well known to those of skill in the art. Synchronizer 300 is shown with a module body 375. In one example, antenna 370 is external to module body 375. In another example, antenna 370 is internal to module body 375. In yet another example, antenna 370 is formed contiguously with module body 375.


Upon detecting a synch signal via a synchronization signal connector (e.g., synchronization signal connector 320, 320′), auto mode switcher 335 provides instructions to transceiver 305 and oscillator 310 to switch to a transmit mode. This process may occur in a variety of ways. As discussed above, instructions 365 may include instructions for a transmit frequency coding. Such a coding may also include an instruction that can be interpreted by the circuitry of transceiver 305 to set an operating mode to a transmit mode and use the frequency represented by the transmit frequency coding.


In one example of transceiver 305, transceiver 305 includes one or more configuration registers 380. In one example, transceiver 305 includes a configuration register 380 utilized by transceiver 305 for programming a frequency for transmission and reception. In such an example, instructions representing a frequency for transmission and/or reception (e.g., instructions 355, 360, 365) may be communicated to register 380 from a auto mode switcher 335.


In one embodiment of operation, synchronizer 300 is configured to load (e.g., load via serial connection and/or via serial shifting) an instruction, such as a configuration, for a receive frequency from auto mode switcher (e.g., from memory 350) to transceiver 305. This may occur at any point. In one example, oscillator 310 is set in a default state of a receive mode by shifting an instruction for a receive frequency to transceiver 305 at power on of synchronizer 300. Loading of an instruction for a given frequency may occur over one of the connections 315 (e.g., a data connection). In one example, each bit of an instruction (e.g, a 32-bit instruction) is loaded to a transceiver one at a time (e.g, one per clock cycle). In this example, a loaded instruction in transceiver 305 (e.g., a loaded instruction in register 380) does not set the current active operating mode of transceiver 305 and its oscillator 310. After loading an instruction (e.g., a receive frequency coding) for a receive frequency to transceiver 305, the instruction for the receive frequency is latched into configuration register 380. In one example, a latch instruction is provided from auto mode switcher 335 to transceiver 305 utilizing one of connections 315, such as a latch connection. In this example, once latched the instruction sets the current active operating mode of transceiver 305 and its oscillator 310. As discussed above, receive frequency coding may also include an indicator that transceiver 305 is to set an operating mode of a receive mode.


Switching oscillator 310 and transceiver 305 to a transmit mode may occur by a variety of ways. In one example, after latching of the instruction for the receive frequency into register 380, auto mode switcher 335 loads an instruction for a transmit frequency to transceiver 305 (e.g., loading corresponding data bits to register 380) but does not latch the instruction to register 380, thereby leaving transceiver 305 and oscillator 310 in a receive mode. This preloading may occur at any time prior to detecting a synch signal (e.g., upon receiving a trigger command, such as a trigger command from a trigger 390 of camera body 325). In a preloading example, by pre-loading the instruction for a transmit frequency to transceiver 305, the time required to do so is saved at the time of switching to a transmit mode. When a synch signal is detected via a synchronization signal connector (e.g., synchronization signal connector 320, 320′) from camera body 325, auto mode switcher 335 provides an instruction and/or a connection signal (e.g., an electric pulse) to transceiver 305 to latch the pre-loaded instruction for a transmit frequency to register 380. This switches transceiver 305 and oscillator 310 (and thus synchronizer 300) to a transmit mode. Any additional necessary instructions for switching to and/or from a given receive and/or transmit mode (e.g., a TX bit, an RX bit) may also be communicated to transceiver 305 at the time of switching to a given mode. In one example, this instruction is included as part of the transmit and/or receive frequency coding. In one example, instructions for latching an instruction for a transmit frequency (and any additional instructions necessary for switching to a transmit mode) are communicated to transceiver 305 in direct response to detection of a synch signal by auto mode switcher 335.


In another embodiment, an instruction to transceiver 305 to switch to a transmit mode (e.g., a frequency coding) may be loaded into transceiver 305 (e.g., via loading into register 380 without latching the data to register 380) in larger word lengths than one bit. For example, a 32-bit frequency coding may be loaded to register 380 8-bits per instruction cycle of processor 335. This reduces the time required for loading to approximately 4 instruction cycles plus one instruction cycle to instruct register 380 to latch the values. In such an example, pre-loading of the frequency coding may occur, but is not necessary, prior to detecting a synch signal from camera 325.


It is to be noted that the above described aspects and embodiments may be conveniently implemented using a conventional processing device (e.g., processor 345) programmed according to the teachings of the present specification, as will be apparent to those skilled in the computer art. Appropriate software coding (i.e., instructions) can readily be prepared by skilled programmers based on the teachings of the present disclosure, as will be apparent to those skilled in the software art.


Such instructions may be included on a machine readable medium including stored computer code which is used to program a processing device to perform the disclosed function and process of the present disclosure. Examples of a machine readable medium include, but are not limited to, a random access memory, a read only memory, a memory drive device, an EPROM, an EEPROM, a compact disc (e.g., read only CD-ROM, writeable CD, re-writable CD, DVD, etc.), a magneto-optical disc and/or card, a flash memory (e.g., a thumb drive), a removable memory (e.g., a memory card, such as an SD-card), and any combinations thereof.


Exemplary embodiments have been disclosed above and illustrated in the accompanying drawings. It will be understood by those skilled in the art that various changes, omissions and additions may be made to that which is specifically disclosed herein without departing from the spirit and scope of the present invention.

Claims
  • 1. An external device for wirelessly synchronizing a remote device to image acquisition of a camera, the external device comprising: a wireless communication functionality having a transmit mode and a receive mode;a first connector for connecting the external device to a port of a camera that provides a connection to a first signal, the first signal generated after a trigger of the camera is activated; andan auto mode switcher for switching a transceiver from the receive mode to the transmit mode in response to receipt of the first signal by the external device via the first connector.
  • 2. An external device according to claim 1, wherein the port of the camera is a hotshoe connector.
  • 3. An external device according to claim 1, wherein the port of the camera is a PC flash synchronization connector.
  • 4. An external device according to claim 1, wherein the camera does not have a shutter and the first signal includes information for synchronizing a remote device to image acquisition of an exposure element of the camera.
  • 5. An external device according to claim 1, wherein the camera includes a shutter and the first signal includes information for synchronizing a remote device to image acquisition related to the opening of the shutter of the camera.
  • 6. An external device according to claim 1, wherein the first signal includes information for synchronizing a remote device to an image acquisition by the camera.
  • 7. An external device according to claim 1, wherein the first signal is a synchronization signal.
  • 8. An external device according to claim 1, wherein said auto mode switcher and said wireless communication functionality are configured to commence transmission to the remote device within 100 microseconds of receiving the first signal.
  • 9. An external device according to claim 1, wherein said auto mode switcher and said wireless communication functionality are configured to commence transmission to the remote device within 20 microseconds of receiving the first signal.
  • 10. An external device according to claim 1, wherein the wireless communication functionality includes an oscillator element that is configured to be in only one of the transmit mode and the receive mode at a time.
  • 11. An external device according to claim 1, further comprising a physical switch configured to manually switch the wireless communication functionality to the receive mode.
  • 12. An external device for wirelessly synchronizing a remote device to image acquisition of a camera, the external device comprising: a wireless communication functionality having a transmit mode and a receive mode;a first connector for connecting the external device to a port of a camera that provides a connection to a first signal, the first signal generated after a trigger of the camera is activated and including information for synchronizing a remote device to an image acquisition by the camera, said first connector configured to connect to at least one of a hotshoe connector of the camera, a PC synchronization connector of the camera, and a multi-contact accessory port of the camera; andan auto mode switcher for switching a transceiver from the receive mode to the transmit mode in response to receipt of the first signal by the external device via the first connector.
  • 13. An external device according to claim 12, wherein the camera does not have a shutter and the first signal includes information for synchronizing a remote device to image acquisition of an exposure element of the camera.
  • 14. An external device according to claim 12, wherein the first signal includes information for synchronizing a remote device to image acquisition related to the opening of a shutter of the camera.
  • 15. An external device according to claim 12, wherein said auto mode switcher and said wireless communication functionality are configured to commence transmission to the remote device within 100 microseconds of receiving the first signal.
  • 16. An external device according to claim 12, wherein said auto mode switcher and said wireless communication functionality are configured to commence transmission to the remote device within 20 microseconds of receiving the first signal.
  • 17. An external device according to claim 12, wherein the first signal includes information for synchronizing a remote device to an image acquisition by the camera.
  • 18. An external device according to claim 12, wherein the first signal is a synchronization signal.
  • 19. An external device according to claim 12, wherein the wireless communication functionality includes an oscillator element that is configured to be in only one of the transmit mode and the receive mode at a time.
  • 20. An external device according to claim 12, further comprising a physical switch configured to manually switch the wireless communication functionality to the receive mode.
  • 21. A system for synchronizing a remote device to photographic image acquisition, the system comprising: a camera having an external port providing access to a first signal, the first signal generated after a trigger of the camera is activated; anda device for connection to the camera, the device including: a wireless communication functionality having a transmit mode and a receive mode;a first connector for connecting the device to the external port of the camera; andan auto mode switcher for switching a transceiver from the receive mode to the transmit mode in response to receipt of the first signal by the device via the first connector.
  • 22. A system according to claim 21, further comprising a remote device configured to be synchronized to the camera using a wireless signal received from the wireless communication functionality.
  • 23. A system according to claim 21, further comprising a remote flash device configured to be synchronized to the camera using a wireless signal received from the wireless communication functionality.
  • 24. A system according to claim 21, wherein the external port of the camera is a hotshoe connector.
  • 25. A system according to claim 21, wherein the external port of the camera is a PC flash synchronization connector.
  • 26. A system according to claim 21, wherein the camera does not include a shutter and the first signal includes information for synchronizing a remote device to image acquisition of an exposure element of the camera.
  • 27. A system according to claim 21, wherein the first signal includes information for synchronizing a remote device to image acquisition related to the opening of a shutter of the camera.
  • 28. A system according to claim 21, wherein the first signal includes information for synchronizing a remote device to an image acquisition by the camera.
  • 29. A system according to claim 21, wherein the first signal is a synchronization signal.
  • 30. A system according to claim 21, wherein said auto mode switcher and said wireless communication functionality are configured to commence transmission to the remote device within 100 microseconds of receiving the first signal.
  • 31. A system according to claim 21, wherein said auto mode switcher and said wireless communication functionality are configured to commence transmission to the remote device within 20 microseconds of receiving the first signal.
  • 32. A system according to claim 21, wherein the wireless communication functionality includes an oscillator element that is configured to be in only one of the transmit mode and the receive mode at a time.
  • 33. A system according to claim 21, further comprising a physical switch configured to manually switch the wireless communication functionality to the receive mode.
RELATED APPLICATION DATA

This application is a continuation of U.S. patent application Ser. No. 13/169,413, filed Jun. 27, 2011, and titled “Wireless Camera Flash Synchronizer System and Method,” which is a continuation of U.S. patent application Ser. No. 12/762,811, filed Apr. 19, 2010, and titled “Wireless Camera Flash Synchronizer System and Method,” now U.S. Pat. No. 7,970,267, which is a continuation of U.S. patent application Ser. No. 12/250,914, filed Oct. 14, 2008, and titled “Wireless Camera Flash Synchronizer System and Method,” now U.S. Pat. No. 7,702,228, issued Apr. 20, 2010, which is a continuation of U.S. patent application Ser. No. 11/697,241 filed Apr. 5, 2007, and titled “Wireless Camera Flash Synchronizer System and Method,” now U.S. Pat. No. 7,437,063, issued Oct. 14, 2008, each of which is incorporated by reference herein in its entirety. This application also claims the benefit of priority of U.S. Provisional Patent Application Ser. No. 60/790,355, filed Apr. 7, 2006, and titled “Wireless Camera Flash Synchronizer System and Method, which is incorporated by reference herein in its entirety.

US Referenced Citations (145)
Number Name Date Kind
3039375 Umbach Jun 1962 A
3185056 Gold et al. May 1965 A
3205803 Burgarella et al. Sep 1965 A
3259042 Kagan Jul 1966 A
RE26627 Burgarella et al. Jul 1969 E
3659509 Burgarella May 1972 A
3728947 Harnden et al. Apr 1973 A
3782258 Boekkooi et al. Jan 1974 A
3810214 Malone et al. May 1974 A
4047191 Coppa et al. Sep 1977 A
4194818 Matteson et al. Mar 1980 A
4201434 Tureck May 1980 A
4209244 Sahara et al. Jun 1980 A
4333719 Takami et al. Jun 1982 A
4344680 Ishida et al. Aug 1982 A
4351594 Ishida et al. Sep 1982 A
4355309 Hughey et al. Oct 1982 A
4470804 Geijer et al. Sep 1984 A
4482895 Weinberg Nov 1984 A
4509845 Mizokami Apr 1985 A
4571049 Tsunefuji et al. Feb 1986 A
4573786 Taniguchi et al. Mar 1986 A
4603954 Egawa et al. Aug 1986 A
4636052 Bowsher Jan 1987 A
4643551 Ohmori Feb 1987 A
4693582 Kawamura et al. Sep 1987 A
4740804 Shands Apr 1988 A
4816850 Phillipeaux et al. Mar 1989 A
4816855 Kitaura et al. Mar 1989 A
4884094 Kitaura et al. Nov 1989 A
4988584 Shaper Jan 1991 A
5016037 Taniguchi et al. May 1991 A
5159375 Taniguchi et al. Oct 1992 A
5283610 Sasaki Feb 1994 A
5299012 Tsuruta et al. Mar 1994 A
5359375 Clark Oct 1994 A
5384611 Tsuji et al. Jan 1995 A
5422543 Weinberg Jun 1995 A
5436531 Weinberg Jul 1995 A
5521708 Beretta May 1996 A
5640623 Sasaki Jun 1997 A
5692223 Ichikawa et al. Nov 1997 A
5708833 Kinney et al. Jan 1998 A
5721971 Sasaki Feb 1998 A
5734934 Horinishi et al. Mar 1998 A
5754898 Nakano May 1998 A
5848306 Shono Dec 1998 A
6006039 Steinberg et al. Dec 1999 A
6029013 Larkin et al. Feb 2000 A
6052539 Latorre Apr 2000 A
6088542 Yanai et al. Jul 2000 A
6127940 Weinberg Oct 2000 A
6167199 Fukui Dec 2000 A
6278481 Schmidt Aug 2001 B1
6351610 Numako et al. Feb 2002 B1
6353711 Numako et al. Mar 2002 B1
6366737 Numako et al. Apr 2002 B1
6400907 Izukawa Jun 2002 B1
6404987 Fukui Jun 2002 B1
6430369 Lee et al. Aug 2002 B2
6453154 Haber et al. Sep 2002 B1
6524237 McGowan Feb 2003 B1
6618557 Ziemkowski Sep 2003 B1
6625399 Davis Sep 2003 B1
6683654 Haijima Jan 2004 B1
6718135 Kawasaki et al. Apr 2004 B2
6731952 Schaeffer et al. May 2004 B2
6748165 Ogasawara Jun 2004 B2
6778764 Barghini et al. Aug 2004 B2
6798986 Hagiuda Sep 2004 B2
6941067 Muramatsu Sep 2005 B2
7016603 Clark Mar 2006 B2
7035534 Shih et al. Apr 2006 B2
7133607 Clark Nov 2006 B2
7184658 Squillace Feb 2007 B2
7362965 Clark Apr 2008 B2
7437063 Clark Oct 2008 B2
7446800 Holmes Nov 2008 B2
7463304 Murray Dec 2008 B2
7684692 Kashiyama Mar 2010 B2
7702228 Clark Apr 2010 B2
7714908 Holmes May 2010 B2
7764875 Clark Jul 2010 B2
7775575 Clark Aug 2010 B2
7783188 Clark Aug 2010 B2
7834894 Swanson et al. Nov 2010 B2
7880761 Clark Feb 2011 B2
7885533 Clark Feb 2011 B2
7970267 Clark Jun 2011 B1
8121468 Clark Feb 2012 B2
8130276 Holmes Mar 2012 B2
8134576 Swanson et al. Mar 2012 B2
8180210 Clark May 2012 B2
8326136 Clark Dec 2012 B1
8326140 Clark Dec 2012 B2
8326141 Clark Dec 2012 B1
8331776 Clark Dec 2012 B2
8351774 Clark Jan 2013 B2
20010042149 Ito et al. Nov 2001 A1
20020009296 Shaper et al. Jan 2002 A1
20020013161 Schaeffer et al. Jan 2002 A1
20020067425 Iverson Jun 2002 A1
20020067923 Fujimura Jun 2002 A1
20020127019 Ogasawara Sep 2002 A1
20030128272 Clough et al. Jul 2003 A1
20030133018 Ziemkowski Jul 2003 A1
20030193588 Yuen et al. Oct 2003 A1
20040036774 Nichols et al. Feb 2004 A1
20040101295 Clark May 2004 A1
20050006484 Ito Jan 2005 A1
20050174434 Chang et al. Aug 2005 A1
20060014563 Cheng Jan 2006 A1
20060093341 Clark May 2006 A1
20060216009 Kawamura Sep 2006 A1
20060275024 McNary Dec 2006 A1
20060291016 Ishigami et al. Dec 2006 A1
20070058959 Clark Mar 2007 A1
20070066162 Zheng Mar 2007 A1
20070070206 Clark Mar 2007 A1
20070237510 Clark Oct 2007 A1
20080065137 Boucher et al. Mar 2008 A1
20080065139 Scribner et al. Mar 2008 A1
20080193114 Clark Aug 2008 A1
20080298792 Clark Dec 2008 A1
20080298793 Clark Dec 2008 A1
20090034952 Clark Feb 2009 A1
20090310012 Ueda et al. Dec 2009 A1
20100177212 Holmes Jul 2010 A1
20110123185 Clark May 2011 A1
20110128390 Clark Jun 2011 A1
20110268432 Clark Nov 2011 A1
20120027395 Clark Feb 2012 A1
20120099847 Clark Apr 2012 A1
20120120281 Swanson et al. May 2012 A1
20120127340 Holmes May 2012 A1
20120127361 Clark May 2012 A1
20120140088 Clark Jun 2012 A1
20120148221 Clark Jun 2012 A1
20120194699 Kouno Aug 2012 A1
20120207459 Clark Aug 2012 A1
20120207460 Clark Aug 2012 A1
20120243859 Clark Sep 2012 A1
20130089313 Clark Apr 2013 A1
20130094845 Clark Apr 2013 A1
20130100340 Clark Apr 2013 A1
Foreign Referenced Citations (46)
Number Date Country
2616030 Jan 2013 CA
2007-80020420.4 Jun 2010 CN
2010-10600736.4 Feb 2012 CN
2010-10600736.4 Dec 2012 CN
984320 Aug 1999 EP
0984320 Mar 2000 EP
07760263.9 Jan 2011 EP
07760263.9 Jul 2011 EP
8756458.9 Jul 2011 EP
11177995.5 Dec 2011 EP
11177995.5 Jul 2012 EP
11177995.5 Aug 2012 EP
10741797 Sep 2012 EP
11177997.1 Dec 2012 EP
56-143422 Nov 1981 JP
59-064821 Apr 1984 JP
59-170822 Sep 1984 JP
63-018874 Jan 1988 JP
05-093948 Apr 1993 JP
5093948 Apr 1993 JP
2002-244193 Aug 2002 JP
2002-244193 Aug 2002 JP
2002-318413 Oct 2002 JP
2002318413 Oct 2002 JP
2003-172970 Jun 2003 JP
2003-215672 Jul 2003 JP
2003-325451 Nov 2003 JP
2004-072230 Mar 2004 JP
2006-149935 Jun 2006 JP
2007-067870 Mar 2007 JP
2007067870 Mar 2007 JP
9638925 Dec 1996 WO
PCTUS200337271 May 2004 WO
2007118201 Oct 2007 WO
2008150902 Dec 2008 WO
2008150904 Dec 2008 WO
PCTUS2010024088 Jul 2010 WO
2010093914 Aug 2010 WO
2010093927 Aug 2010 WO
2010093994 Aug 2010 WO
PCTUS2010024108 Sep 2010 WO
PCTUS2010024195 Sep 2010 WO
PCTUS2011044008 Nov 2011 WO
2012009537 Jan 2012 WO
PCTUS2012025915 Jun 2012 WO
2012161772 Nov 2012 WO
Non-Patent Literature Citations (143)
Entry
Pocketwizard MultiMax Transceiver Owner's Manual, by LPA Design, May 2001, pp. 1-55 and “Relay Mode” on p. 40, United States.
Technical Data Sheet for ADF7020-1 Transceiver IC, Analog Devices, Inc., 2005, pp. 1-44.
FlashWizard II Synchronizer, Affidavit of James E. Clark Regarding FlashWizard II Synchronizer.
Notice of First Office Action dated Nov. 8, 2007 in connection to related U.S. Appl. No. 11/697,241.
Response to First Office Action dated Mar. 10, 2008 in connection to related U.S. Appl. No. 11/697,241.
Examiner Interview Summary dated Mar. 24, 2008 in connection to related U.S. Appl. No. 11/697,241.
Notice of Allowance dated Jun. 9, 2008 in connection to related U.S. Appl. No. 11/697,241.
First Office Action dated Jun. 12, 2009 in connection with related U.S. Appl. No. 12/250,914.
Response to First Office Action dated Jun. 29, 2009 in connection with related U.S. Appl. No. 12/250,914.
Terminal Disclaimer dated Oct. 28, 2009 in connection with related U.S. Appl. No. 12/250,914.
Notice of Allowance dated Dec. 3, 2009 in connection with related U.S. Appl. No. 12/250,914.
Office Action dated Dec. 28, 2010 in related U.S. Appl. No. 12/762,611.
Response to Office Action dated Mar. 28, 2011 in related U.S. Appl. No. 12/762,611.
Terminal Disclaimer dated Mar. 28, 2011 in related U.S. Appl. No. 12/762,611.
Notice of Allowance dated Apr. 20, 2011 in related U.S. Appl. No. 12/762,611.
Office Action dated Dec. 20, 2011 in related U.S. Appl. No. 13/169,413, filed Jun. 27, 2011.
Response to Office Action dated Jan. 16, 2012 in related U.S. Appl. No. 13/169,413, filed Jun. 27, 2011.
Notice of Allowance dated Mar. 22, 2012 in related U.S. Appl. No. 13/169,413.
Nikon D2H Review: 1. Introduction: Digital Photography Review, Nikon D2H Review, Dec. 2003, Phil Askey; http://www.dpreview.com/reviews/NikonD2H/; last viewed on Mar. 18, 2008.
Nikon D2H Review: 15. Wireless: Digtal Photography Review, Wireless; http://wwww.dpreview.com/reviews/NikonD2H/page 15.asp; last viewed on Mar. 18, 2008.
Related U.S. Appl. No. 10/306,759, filed Nov. 26, 2002, now U.S. Patent No. 7,016,603.
Related U.S. Appl. No. 11/305,668, filed Dec. 16, 2005, now U.S. Patent No. 7,133,607.
Related U.S. Appl. No. 11/529,203, filed Sep. 27, 2006, now U.S. Patent No. 7,362,965.
Related U.S. Appl. No. 12/104,950, filed Apr. 17, 2008.
Related U.S. Appl. No. 11/490,322, filed Jul. 20, 2006.
Related U.S. Appl. No. 11/697,241, filed Apr. 5, 2007.
Related U.S. Appl. No. 12/129,447, filed May 29, 2008.
Office Action mailed Aug. 29, 2003, in related U.S. Appl. No. 10/306,759, now U.S. Patent No. 7,016,603.
Response to First Office Action dated Dec. 18, 2003, in related U.S. Appl. No. 10/306,759, now U.S. Patent No. 7,016,603.
Examiner Interview Summary dated Dec. 24, 2003, in related U.S. Appl. No. 10/306,759, now U.S. Patent No. 7,016,603.
Final Office Action dated Mar. 27, 2004, in related U.S. Appl. No. 10/306,759, now U.S. Patent No. 7,016,603.
Examiner Interview Summary dated Apr. 15, 2004, in related U.S. Appl. No. 10/306,759, now U.S. Patent No. 7,016,603.
Response to Final Office Action dated Apr. 20, 2004, in related U.S. Appl. No. 10/306,759, now U.S. Patent No. 7,016,603.
Third Office Action dated Aug. 24, 2004, in related U.S. Appl. No. 10/306,759, now U.S. Patent No. 7,016,603.
Request for Continued Examination dated Feb. 18, 2005, in U.S. Appl. No. 10/306,759, filed Nov. 26, 2002, now U.S. Patient No. 7,016,603.
First Office Action after Request for Continued Examination dated Mar. 29, 2005, in related U.S. Appl. No. 10/306,759, now U.S. Patent No. 7,016,603.
Response to First Office Action Request for Continued Examination dated Apr. 14, 2005, in related U.S. Appl. No. 10/306,759, now U.S. Patent No. 7,016,603.
Second Office Action after Request for Continued Examination dated Jun. 29, 2005, in related U.S. Appl. No. 10/306,759, now U.S. Patent No. 7,016,603.
Response to Second Office Action after Request for Continued Examination dated Aug. 25, 2005, in related U.S. Appl. No. 10/306,759, now U.S. Patent No. 7,016,603.
Notice of Allowance dated Sep. 16, 2005, in related U.S. Appl. No. 10/306,759, now U.S. Patent No. 7,016,603.
312 Amendment dated Oct. 10, 2005, in U.S. Appl. No. 10/306,759, filed Nov. 26, 2002, now U.S. Patent No. 7,016,603.
First Office Action dated Mar. 8, 2006, in related U.S. Appl. No. 11/305,668, now U.S. Patent No. 7,133,607.
Response to First Office Action dated Jun. 8, 2006, in related U.S. Appl. No. 11/305,668, now U.S. Patent No. 7,133,607.
Notice of Allowance dated Jun. 30, 2006, in related U.S. Appl. No. 11/305,668, now U.S. Patent No. 7,133,607.
Request for Correction of Letters Patent dated Mar. 29, 2007, in U.S. Patent No. 7,133,607.
Supplemental Response to Request for Clarification by the Examiner dated Jun. 13, 2006, in U.S. Appl. No. 11/305,688, filed Dec. 16, 2005, now U.S. Patent No. 7,133,607.
First Office Action dated Aug. 14, 2007, in related U.S. Appl. No. 11/529,203, now U.S. Patent No. 7,362,965.
Response to First Office Action and Terminal Disclaimer dated Oct. 16, 2007, in related U.S. Appl. No. 11/529,203, now U.S. Patent No. 7,362,965.
Terminal Disclaimer dated Oct. 25, 2007, in related U.S. Appl. No. 11/529,203, now U.S. Patent No. 7,362,965.
Notice of Allowance dated Dec. 14, 2007, in related U.S. Appl. No. 11/529,203, now U.S. Patent No. 7,362,965.
First Office Action dated Oct. 16, 2007 in related U.S. Appl. No. 11/488,491.
International Search Report and Written Opinion mailed Feb. 12, 2008, in International Application No. PCT/US2006/028229.
International Search Report and Written Opinion dated Nov. 9, 2007, in related International Application No. PCT/US2007/66162.
International Search Report and Written Opinion dated May 29, 2007, in related International Application No. PCT/US2008/065139.
International Search Report and Written Opinion dated May 29, 2007, in related International Application No. PCT/US2008/065137.
U.S. Appl. No. 13/735,325, filed Mar. 15, 201, Office Action.
U.S. Appl. No. 13/735,325, filed Mar. 21, 2013, Response to Office Action w/Terminal Disclaimers.
U.S. Appl. No. 13/708,326, filed Mar. 26, 2013, Notice of Allowance.
U.S. Appl. No. 13/208,706, filed Mar. 26, 2013, Response to Office Action.
U.S. Appl. No. 13/016,345, filed Apr. 26, 2013, Restriction Requirement.
U.S. Appl. No. 13/183,046, filed Apr. 29, 2013, Response to Office Action.
ASH Transceiver Impedance Matching; Document Created on Dec. 10, 2001; pp. 1 to 10; http://www.rfm.com/products/apnotes/antennamatch.pdf; last viewed on Dec. 15, 2005.
Canon EOS 40D Usuer's Manual; about Sep. 2007; Canon Corporation.
Declaration of James E. Clark filed on Feb. 18, 2005 in U.S. Appl. No. 10/306,759.
Ken Rockwell; How to Use Nikon Strobes Wirelessly, for Free!; Dec. 17, 2005; http://web.archive.org/web/20051217091704/http://www.kenrockwell.com/nikon/ittlslave.htm; last viewed at Internet archive on Apr. 1, 2010.
Ken Rockwell: Nikon SU-800 Remote Commander; Nov. 1, 2005, http://www.kenrockwell.com/nikon/su800.htm; last viewed on Jul. 18, 2012.
Nikon D2x; Sep. 2004; pp. 1 to 12; Nikon Corporation.
Nikon WT-1 Transmitter User's Manual; around Dec. 2003; Nikon Corporation.
Phil Askey, Nikon D2Hs Preview: 1. Introduction: Digital Photography Review (includes Review of WT-2 Transmitter); Feb. 2005; http://www.dpreview.com/articles/nikond2hs/; last viewed Mar. 14, 2008.
PocketWizard MultiMAX Transceiver New Trigger Control Software Features, by LPA Design, pp. 1 to 6, United States.
Quantum FreeWire Transceiver; Jul. 17, 2005; pp. 1 to 7; http://web.archive.org/web/20050717015832/http://www.qtm.com/wireless/freewire.html; last viewed at Internet Archive on Apr. 25, 2008.
Quantum FreeWire Transceiver; Nov. 15, 2004; pp. 1 to 7; http://web.archive.org/web/20041115093657/http://www.qtm.com/wireless/freewire.html; last viewed at Internet Archive on Apr. 25, 2008.
Quantum FreeWire Transceiver; Oct. 7, 2001; pp. 1 to 6; http://web.archive.org/web/20011007140624/http://www.qtm.com/wireless/freewire.html; last viewed at Internet Archive on Apr. 25, 2008.
Robert Hanashiro; Equipment Corner—News & Notes for all Those Gear-Heads; Nov. 26, 2001; pp. 1 to 3; http://www.sportsshooter.com/news—story.html?id=594; last viewed on Sep. 17, 2002.
U.S. Appl. No. 10/306,759, filed Aug. 29, 2003, Office Action.
U.S. Appl. No. 10/306,759, filed Dec. 18, 2003, Response to Office Action.
U.S. Appl. No. 10/306,759, filed Dec. 24, 2003, Examiner Interview Summary.
U.S. Appl. No. 10/306,759, filed Mar. 27, 2004, Final Office Action.
U.S. Appl. No. 10/306,759, filed Apr. 15, 2004, Examiner Interview Summary.
U.S. Appl. No. 10/306,759, filed Apr. 20, 2004, Response to Final Office Action.
U.S. Appl. No. 10/306,759, filed Aug. 24, 2004, Office Action.
U.S. Appl. No. 10/306,759, filed Feb. 18, 2005, Request for Continued Examination.
U.S. Appl. No. 10/306,759, filed Mar. 29, 2005, Office Action.
U.S. Appl. No. 10/306,759, filed Apr. 14, 2005, Response to Office Action.
U.S. Appl. No. 10/306,759, filed Jun. 29, 2005, Final Office Action.
U.S. Appl. No. 10/306,759, filed Aug. 25, 2005, Response to Final Office Action.
U.S. Appl. No. 10/306,759, filed Sep. 16, 2005, Notice of Allowance.
U.S. Appl. No. 10/306,759, filed Oct. 18, 2005, 312 Amendment.
U.S. Appl. No. 10/306,759, filed Dec. 20, 2005, Response to 312 Amendment.
U.S. Appl. No. 10/306,759, filed Jan. 4, 2006, Response to 312 Amendment.
U.S. Appl. No. 10/306,759, filed Nov. 18, 2006, Certificate of Correction.
U.S. Appl. No. 11/305,668, filed Mar. 8, 2006, Office Action.
U.S. Appl. No. 11/305,668, filed Jun. 8, 2006, Response to Office Action.
U.S. Appl. No. 11/305,668, filed Jun. 13, 2006, Supplemental Response to Request for Clarification by the Examiner.
U.S. Appl. No. 11/305,668, filed Jun. 30, 2006, Notice of Allowance.
U.S. Appl. No. 11/305,668, filed Mar. 29, 2007, Request for Correction of Letters Patent.
U.S. Appl. No. 11/529,203, filed Aug. 14, 2007, Office Action.
U.S. Appl. No. 11/529,203, filed Oct. 16, 2007, Terminal Disclaimer.
U.S. Appl. No. 11/529,203, filed Oct. 16, 2007, Response to Office Action.
U.S. Appl. No. 11/529,203, filed Oct. 25, 2007, Terminal Disclaimer.
U.S. Appl. No. 11/529,203, filed Dec. 14, 2007, Notice of Allowance.
U.S. Appl. No. 12/104,950, filed Dec. 31, 2009, Office Action.
U.S. Appl. No. 12/104,950, filed Feb. 1, 2010, Response to Office Action.
U.S. Appl. No. 13/399,333, filed Jun. 14, 2012, Office Action.
U.S. Appl. No. 11/488/491, filed Oct. 16, 2007, Office Action.
U.S. Appl. No. 13/438,500, filed Jun. 18, 2012, Office Action.
U.S. Appl. No. 13/021,951, filed Nov. 25, 2011, Notice of Allowance.
U.S. Appl. No. 13/021,951, filed Feb. 13, 2012, Withdrawal of Notice of Allowance.
U.S. Appl. No. 13/021,951, filed Feb. 22, 2012, Office Action.
U.S. Appl. No. 13/253,596, filed Nov. 30, 2011, Office Action.
U.S. Appl. No. 13/253,596, filed Feb. 29, 2012, Response to Office Action.
U.S. Appl. No. 13/253,596, filed May 9, 2012, Final Office Action.
U.S. Appl. No. 12/705,052, filed Mar. 27, 2012, Office Action.
U.S. Appl. No. 12/705,052, filed Jun. 27, 2012, Response to Office Action.
U.S. Appl. No. 12/705,096, filed Mar. 12, 2012, Office Action.
U.S. Appl. No. 12/705,096, filed Jun. 12, 2012, Response to Office Action.
U.S. Appl. No. 12/705,164, filed Mar. 29, 2012, Office Action.
U.S. Appl. No. 12/705,164, filed Jun. 29, 2012, Response to Office Action.
U.S. Appl. No. 13/016,345, filed Jan. 28, 2011.
U.S. Appl. No. 13/438,500, filed Apr. 3, 2012.
U.S. Appl. No. 13/021,951, filed Feb. 7, 2011.
U.S. Appl. No. 13/253,596, filed Oct. 5, 2011.
U.S. Appl. No. 13/201,182, filed Aug. 11, 2011.
U.S. Appl. No. 13/201,185, filed Aug. 11, 2011.
U.S. Appl. No. 13/201,281, filed Aug. 12, 2011.
U.S. Appl. No. 13/208,686, filed Aug. 12, 2011.
U.S. Appl. No. 13/208,706, filed Aug. 12, 2011.
U.S. Appl. No. 13/401,175, filed Feb. 21, 2012.
U.S. Appl. No. 12/705,052, filed Feb. 12, 2010.
U.S. Appl. No. 12/705,096, filed Feb. 12, 2010.
U.S. Appl. No. 12/705,164, filed Feb. 12, 2010.
U.S. Appl. No. 12/705,096, filed Aug. 8, 2012, Notice of Allowance.
U.S. Appl. No. 12/705,052, filed Sep. 5, 2012, Notice of Allowance.
U.S. Appl. No. 13/399,333, filed Sep. 14, 2012, Response to Office Action.
U.S. Appl. No. 13/399,333, filed Sep. 14, 2012, Termincal Disclaimers.
U.S. Appl. No. 12/705,164, filed Nov. 29, 2012, RCE.
U.S. Appl. No. 13/208,706, filed Dec. 26, 2012, Office Action.
U.S. Appl. No. 13/208,686, filed Feb. 6, 2013, Office Action.
U.S. Appl. No. 13/183,046, filed Feb. 13, 2013, Office Action.
U.S. Appl. No. 13/708,325, filed Dec. 7, 2012.
U.S. Appl. No. 13/692,515, filed Dec. 3, 2012.
U.S. Appl. No. 13/692,550, filed Dec. 3, 2012.
U.S. Appl. No. 13/735,325, filed Jan. 7, 2013.
Provisional Applications (1)
Number Date Country
60790355 Apr 2006 US
Continuations (4)
Number Date Country
Parent 13169413 Jun 2011 US
Child 13438500 US
Parent 12762811 Apr 2010 US
Child 13169413 US
Parent 12250914 Oct 2008 US
Child 12762811 US
Parent 11697241 Apr 2007 US
Child 12250914 US