The measurement of vibration is the most common method of assessing the mechanical status of machinery for condition monitoring purposes. To measure vibration, one or more vibration sensors are coupled to a machine at various locations. The sensors collect vibration data and transmit the vibration data to a remote device for analysis. The sensors may transmit the vibration data through wires. In other embodiments, the sensors may transmit the vibration data wirelessly.
When the sensors transmit the vibration data wirelessly, the sensors may be synchronized together over a radiofrequency (“RF”) network with the remote device. This may enable the sensors to be synchronized to within about 1 millisecond to about 1 second. While this level of synchronization may be satisfactory for some purposes, a more precise level of synchronization between wireless vibration sensors is needed.
A system for monitoring a machine is disclosed. The system includes first and second mobile units. The first mobile unit includes an emitter, a clock in communication with the emitter, and a sensor in communication with the clock. The second mobile unit includes a detector, a clock in communication with the detector, and a sensor in communication with the clock. The detector of the second mobile unit is configured to detect a signal from the emitter of the first mobile unit, and the clocks in the first and second mobile units are configured to be synchronized in response to the detection of the signal.
A method for monitoring a machine is also disclosed. The method includes positioning first and second mobile units such that an emitter of the first mobile unit is in range to communicate with a detector of the second mobile unit. A signal is emitted from the emitter of the first mobile unit that is detected by the detector of the second mobile unit. A clock in the first mobile unit is synchronized with a clock in the second mobile unit using the signal emitted from the emitter of the first mobile unit.
In another embodiment, the method may include connecting a remote device to first and second mobile units. A clock in the first mobile unit is synchronized with a clock in the second mobile unit to a first level of accuracy using a signal from the remote device. The first and second mobile units are positioned such that an emitter of the first mobile unit is in range to communicate with a detector of the second mobile unit. A signal is emitted from the emitter of the first mobile unit that is detected by the detector of the second mobile unit. The clock in the first mobile unit is synchronized with the clock in the second mobile unit to a second level of accuracy using the signal emitted from the emitter of the first mobile unit, wherein the second level of accuracy is greater than the first level of accuracy.
The accompanying drawings, which are incorporated in and constitutes a part of this specification, illustrates an embodiment of the present teachings and together with the description, serves to explain the principles of the present teachings. In the figures:
It should be noted that some details of the figures have been simplified and are drawn to facilitate understanding of the embodiments rather than to maintain strict structural accuracy, detail, and scale.
Reference will now be made in detail to embodiments of the present teachings, examples of which are illustrated in the accompanying drawing. In the drawings, like reference numerals have been used throughout to designate identical elements, where convenient. In the following description, reference is made to the accompanying drawings that form a part of the description, and in which is shown by way of illustration one or more specific example embodiments in which the present teachings may be practiced.
Further, notwithstanding that the numerical ranges and parameters setting forth the broad scope of the disclosure are approximations, the numerical values set forth in the specific examples are reported as precisely as possible. Any numerical value, however, inherently contains certain errors necessarily resulting from the standard deviation found in their respective testing measurements. Moreover, all ranges disclosed herein are to be understood to encompass any and all sub-ranges subsumed therein.
A detector 130 may also be positioned within the body 110. The detector 130 may be configured to receive the signal from the emitter of another mobile unit. In one example, the detector 130 may be a light detector that includes a photodiode or the like that is configured to sense or detect the pulse of light through the opening 112. When operating through the same opening 112, the emitter 120 and the detector 130 may not operate simultaneously. Although shown as operating through the same opening 112 in
In at least one embodiment, a window or filter 114 may be positioned over the opening 112 (i.e., positioned over the emitter 120, the detector 130, or both). The window or filter 114 may be configured to allow light within a predetermined frequency band or wavelength band to pass therethrough while preventing (i.e., filtering) light outside the band(s) from passing therethrough. The emitter 120 may be tuned to transmit light that is within this frequency band or wavelength band. Similarly, the detector 130 may be tuned to detect light that is within this frequency band or wavelength band.
In another example, the emitter 120 may be a sound emitter that is configured to emit a pulse of sound (e.g., a mechanical vibration or chirp), and the detector 130 may be a sound detector that is configured to sense or detect the pulse of sound. The pulse of sound may have the same duration as the pulse of light described above. In yet another example, the emitter 120 may be a RF emitter that is configured to emit a RF pulse, and the detector 130 may be a RF detector that is configured to sense or detect the RF pulse.
The mobile unit 100 may include a connector 140 for connecting to another component. In one example, a charging cable may be connected to the connector 140 to charge a power source (e.g., a battery) inside the body 110. In another example, a data cable may be connected to the connector 140 to transmit data to and/or from a memory in the body 110. In yet another embodiment, the connector 140 may be used to connect a sensor (e.g., a tachometer) to the body 110.
The mobile unit 100 may also include a sensory apparatus or “head” 150 that may be releasably coupled, e.g., mechanically and electrically, with the mobile unit 100 so as to be positionally fixed thereto, receive power therefrom, and provide one or more signals thereto. The sensory head 150 may include, for example, at least one sensor positioned therein, as shown in
In at least one embodiment, the mobile unit 100 may include a power button 160, one or more control buttons 170, and a display screen 180, which may be configured to display data based on the measurements taken using the sensory head 150. In other embodiments, the display screen 180 may be omitted from the mobile unit 100, or may otherwise not display such data.
The mobile unit 100 may also include the sensor 250, which may be positioned within the body 110 or the sensory head 140 (see
The mobile unit 100 may also include an antenna 260 that is configured to transmit and/or receive signals from a remote device. As discussed in more detail below, the signals may include timing/synchronization data, or the signals may include data measured by the sensor 250. In at least one embodiment, the signals may be RF signals.
The mobile unit 100 may also include a timer 270 and a real time clock (“RTC”) 280. The real time clock 280 may keep the date and time. The timer 270 may be used to fine-tune the real time clock 280 during synchronization, as discussed in more detail below. As shown, the emitter 120 and the detector 130 may be in communication with the timer 270.
As shown, the mobile units 100-103 may be coupled to the machine 300 at various locations around the machine 300. The sensory heads 150 (see
A remote device 105 may be in (e.g., wireless) communication with the mobile devices 100-103. The remote device 105 may be a portable electronic device, such as a smartphone, tablet, or laptop computer, or may be another type of specific or general-purpose computing device that is supplied with appropriate software. The remote device 105 may be in wireless communication with the mobile units 100-103, and, in some embodiments, vice versa, via any suitable communications link, such as a wireless link (e.g., BLUETOOTH®, WiFi, WIMAX®, GSM, CDMA, LTE, etc.).
Once connected, the remote device 105 may cause the real time clocks 280 of the mobile units 100-103 to be synchronized to a first level of accuracy using a signal from the remote device 105, as at 404. More particularly, the remote device 105 may transmit a RF signal to the antennas 260 of the mobile units 100-103 that causes the real time clock 280 in each mobile unit (e.g., mobile unit 100) to be synchronized with the clock of the remote device 105 (and with the real time clocks 280 of the other mobile units 101-103). The first level of accuracy may be from about 1 millisecond to about 1 second.
A first one of the mobile units (e.g., mobile unit 100) may then be positioned such that its emitter 120 is in range to communicate with (e.g., faces) the detector 130 of a second one of the mobile units (e.g., mobile unit 101), as at 406. A distance between the emitter 120 of the first mobile unit 100 and the detector 130 of the second mobile unit 101 may be from about 0.1 cm to about 10 cm or more.
The emitter 120 of the first mobile unit 100 may then emit a signal, which may be detected by the detector 130 of the second mobile unit 101, as at 408. For example, the remote device 105 may transmit a RF signal to the first mobile unit 100 causing the first mobile unit 100 to emit the signal. In another example, the user may manually cause the first mobile unit 100 to emit the signal (e.g., by pressing the buttons 170). As discussed above, the signal may be a pulse of light, a sound, a RF signal, or the like.
The real time clocks 280 of the mobile units 100, 101 may then be synchronized to a second level of accuracy using the signal from the emitter 120 of the first mobile unit 100, as at 410. More particularly, the timer 270 of the first mobile unit 100 may be at time T0 when the emitter 120 of the first mobile unit 100 emits the signal. The timer 270 of the first mobile unit 100 may notify the real time clock 280 of the first mobile unit 100 that the signal was emitted at time T0.
The timer 270 of the second mobile unit 101 may be at time T1 when the detector 120 of the second mobile unit 101 detects the signal. The timer 270 of the second mobile unit 101 may notify the real time clock of the second mobile unit 101 that the signal was emitted at time T1. Thus, the timers 270 may be used to synchronize the real time clocks 280 to greater levels of accuracy/precision (e.g., to within T1−T0) than may be achieved through the RF signals described in step 404. The difference between T0 and T1 may be from about 1 nanosecond to about 1 millisecond. For example, the difference may be from about 1 nanosecond to about 10 nanoseconds, about 10 nanoseconds to about 100 nanoseconds, about 100 nanoseconds to about 1 microsecond, about 1 microsecond to about 10 microseconds, about 10 microseconds to about 100 microseconds, or about 100 microseconds to about 1 millisecond. The synchronization process may be iterative, with each successive iteration achieving a greater level of accuracy (e.g., a smaller difference). Once the second mobile unit 101 is synchronized to the first mobile unit 100, the process may be repeated for one or more mobile units (e.g., mobile units 102, 103).
Once the mobile units 100-103 have been synchronized, as described in step 410 above, the mobile units 100-103 may be coupled to the machine 300, as at 412. The mobile units 100-103 may then capture or record data, as at 414. For example, the remote device 105 may transmit RF signals to the mobile units 100-103 causing the mobile units 100-103 to begin capturing data. In another example, the user may manually cause the mobile units 100-103 to begin capturing data (e.g., by pressing the buttons 170). In at least one embodiment, one of the mobile units (e.g., mobile unit 100) may be coupled to a tachometer via the connector 140. The tachometer may measure the speed of rotation of one or more components (e.g., a shaft) inside the machine 300.
The mobile units 100-103 may be single-channel sensors or multi-channel sensors. In one embodiment, the mobile units 100-103 may each be or include a single-channel sensor, and together the mobile units 100-103 may be configured to capture four different channels of synchronous data. For example, the first mobile unit 100 (i.e., the first channel) may be configured to capture shaft rotational speed data, the second mobile unit 101 (i.e., the second channel) may be configured to capture axial acceleration data, the third mobile unit 102 (i.e., the third channel) may be configured to capture inboard acceleration data, and the fourth mobile unit 103 (i.e., the fourth channel) may be configured to capture outboard acceleration data. The data in the different channels may be used to support different analyses such as an operational deflection shape analysis.
Once the data has been captured, the mobile units 100-103 may (e.g., wirelessly) transmit the data to the remote device 105, as at 416. The data may be transmitted to the remote device 105 while the mobile units 100-103 are coupled to the machine 300 or after the mobile units 100-103 have been decoupled from the machine 300. In at least one embodiment, the mobile units 100-103 may wirelessly transmit the data to the remote device 105 substantially in real-time as the data is being captured. Once the data is received by the remote device 105, the data from the different mobile units 100-103 (e.g., channels) may be temporally aligned using time stamps on the data to produce synchronous multi-channel measurements, as at 418. In another embodiment, step 418 may be uploaded to a server and performed in the cloud.
As the mobile units 100-103 are wireless in some embodiments, the mobile units 100-103 may be coupled to a machine that moves (e.g., a crane). In at least one embodiment, when the emitter 120 produces light for synchronization purposes, the emitter 120 may also be used as a flashlight and/or strobe light for machinery analysis. For example, the light may be used to visually “freeze” machinery rotation to determine the speed of the rotation.
While the present teachings have been illustrated with respect to one or more implementations, alterations and/or modifications may be made to the illustrated examples without departing from the spirit and scope of the appended claims. In addition, while a particular feature of the present teachings may have been disclosed with respect to only one of several implementations, such feature may be combined with one or more other features of the other implementations as may be desired and advantageous for any given or particular function. Furthermore, to the extent that the terms “including,” “includes,” “having,” “has,” “with,” or variants thereof are used in either the detailed description and the claims, such terms are intended to be inclusive in a manner similar to the term “comprising.” Further, in the discussion and claims herein, the term “about” indicates that the value listed may be somewhat altered, as long as the alteration does not result in nonconformance of the process or structure to the illustrated embodiment. Finally, “exemplary” indicates the description is used as an example, rather than implying that it is an ideal.
Other embodiments of the present teachings will be apparent to those skilled in the art from consideration of the specification and practice of the present teachings disclosed herein. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the present teachings being indicated by the following claims.
Number | Name | Date | Kind |
---|---|---|---|
4882770 | Miyahira | Nov 1989 | A |
5943634 | Piety | Aug 1999 | A |
5945603 | Shih | Aug 1999 | A |
5965819 | Piety | Oct 1999 | A |
6078874 | Piety | Jun 2000 | A |
6079275 | Komninos | Jun 2000 | A |
6208944 | Franke | Mar 2001 | B1 |
6301514 | Canada | Oct 2001 | B1 |
6347163 | Roustaei | Feb 2002 | B2 |
6489884 | Lamberson | Dec 2002 | B1 |
6513386 | Barclay | Feb 2003 | B2 |
6672168 | Higgins | Jan 2004 | B2 |
6683970 | Satake | Jan 2004 | B1 |
6760677 | Tanizume | Jul 2004 | B2 |
7254504 | Klotz | Aug 2007 | B2 |
7908928 | Vik | Mar 2011 | B2 |
8583792 | Narasimhan | Nov 2013 | B2 |
8590384 | Lotscher | Nov 2013 | B2 |
8622901 | Jain | Jan 2014 | B2 |
8800374 | Sonyey | Aug 2014 | B2 |
20020000126 | Barclay | Jan 2002 | A1 |
20060236771 | Lin | Oct 2006 | A1 |
20070256500 | Vornbrock | Nov 2007 | A1 |
20080105056 | Popescu | May 2008 | A1 |
20090110405 | Lee | Apr 2009 | A1 |
20110279952 | Sonyey | Nov 2011 | A1 |
20120263165 | Zakrzewski | Oct 2012 | A1 |
20140092918 | Jost | Apr 2014 | A1 |
20140301513 | Takahashi | Oct 2014 | A1 |
20150024508 | Horkheimer | Jan 2015 | A1 |
20150065881 | Cho | Mar 2015 | A1 |
20150078140 | Riobo Aboy | Mar 2015 | A1 |
20150217728 | Iwai | Aug 2015 | A1 |
20150250445 | Spiegel | Sep 2015 | A1 |
20150268072 | Fujiwara | Sep 2015 | A1 |
20150283427 | Shibuya | Oct 2015 | A1 |
20150285932 | Nyffenegger | Oct 2015 | A1 |
20150338510 | Pandharipande | Nov 2015 | A1 |
20150350752 | Solomon | Dec 2015 | A1 |
20150355045 | Solomon | Dec 2015 | A1 |
Number | Date | Country |
---|---|---|
2009-77344 | Apr 2009 | JP |
Entry |
---|
Author Unknown, GTI Predictive Technology, web-page: https://www.gtipredictive.com/, accessed Mar. 27, 2015, pp. 1-2. |
Number | Date | Country | |
---|---|---|---|
20160282232 A1 | Sep 2016 | US |