Control Engineering's Weekly News Question of the Week

09/18/2006


February 27, 2007

QUESTION: Can I automate operation of a high vacuum system?


The pumping system recommended for general use consists of a mechanical foreline pump that holds back atmospheric pressure and a turbomolecular main pump that scavanges the final 0.1% of the gas in the vacuum chamber. A bypass valve allows isolating the main pump while evacuating the vacuum chamber with the mechanical pump.

Essentially any vacuum system can easily be automated. While the details vary depending on the application and the vacuum-pumping technology chosen, there are some general principals.

Vacuum systems generally divide into three regions: 'above the table' vacuum chamber, 'below the table' high vacuum or main pump, and foreline or rough vacuum pump. The vacuum chamber is the business office for the application. For vacuum coating, for example, the vacuum chamber is a bell jar with the evaporation heaters, fixtures, coating measurement equipment, and so forth inside. For an electron microscope, it's the sample chamber, electron optics, etc. Being an air-tight vessel designed to withstand 14.7 psi pressure, it typically has thick walls and often weighs hundreds or thousands of pounds. Since actual people often have to reach inside to set things up, vacuum system designers often mount vacuum chambers on support structures that hold them at a convenient work height.

'Above the table' and 'below the table' are jargon terms that arose because most system designs locate the vacuum pumping equipment conveniently in a cabinet built into the vacuum-chamber support structure. That put the cabinet's top at a perfect height for a benchtop—the 'table.' A large main vacuum valve, which necessarily must be a gate valve or butterfly valve to allow adequate pumping throughput, makes it possible to separate the vacuum chamber from the pumping system. So, really 'above the table' means above the main valve and 'below the table' means downstream of the main valve.

Sensors in a vacuum control system are vacuum gauges, and there are a range of types. Some, such as the Penning cold-cathode ionization gauge, are useful only at high vacuum levels. Others, such as thermocouple gauges, are useful only at rough vacuum levels present in forelines. Since different vacuum pump types also work at different vacuum levels, it's appropriate to match the vacuum gauge type with the vacuum pump evacuating the space it senses.

Vacuum levels are measured by absolute pressure in units called Torricellis (typically abbreviated 'Torr' both when written and spoken), which equal approximately 133 Pascals. So, 10 Torr equals an absolute pressure of 1,330 Pascals (approximately). In the vacuum world, however, 1 Torr is a very high pressure! Oil diffusion pumps shouldn't be operated at over 10-3Torr. Vacuum workers invented more jargon to handle this fact by dropping all but the exponent. A vacuum engineer, therefore, might refer to the 'seven scale,' meaning a vacuum between 3x10-7Torr and 3x10-6Torr.

So, in designing a vacuum system, you generally start with the chamber pressure needed for the application. High vacuum applications generally need vacuums better than 10-5Torr—meaning five scale or 'higher.' Particle beams, for example, are happy on the six scale and are ecstatic if you can maintain seven-scale vacuum. If you can get to the eight scale, you're getting into ultra-high vacuum (UHV) territory. Oil diffusion pumps (augmented with cryogenic 'cold traps') aren't much good above seven scale, though. UHV applications pretty much require turbomolecular pumps or something even more exotic.

Actually, turbomolecular pumps aren't that exotic, anymore. In fact, they've become the first choice for most applications because they can operate at almost any vacuum level from rough to UHV, and are pretty much bullet proof. About the only thing you can do to hurt a turbopump is to drop a screw into it while it's running! For that reason, I recommend turbopumps for any automated system. The ideal pumping system for most applications is a turbopump backed by a mechanical forepump and closed off from the vacuum chamber by a gate valve.

A single stage turbopump is little more than a set of fan blades that rotate at tens of thousands of rpm. At high vacuum levels, gas doesn't flow as a fluid. Gas molecules collide more often with the vacuum walls than with each other. A gas molecule moving through the turbopump in the flow direction can slip between turbopump blades. When moving the other way, however, they're almost sure to hit a blade and bounce back toward the 'right' direction. Stack several turbopump stages together with additional stationary blades in between to prevent swirling, and you've got a really effective pump at high vacuum.

The turbopump will also work like an ordinary fan at high pressure (foreline vacuum or worse), but, like a fan, it can't maintain much of a pressure difference. Too much gas leaks back. So, for high vacuum (or better) work, always use a mechanical backing pump. The mechanical pump is a positive displacement pump that can hold back atmospheric pressure, leaving the turbopump to scavenge out those pesky gas molecules that make up the last thousandth of a Torr. Since turbopumps can stand atmospheric pressure, even though they don't pump it effectively, they can be running whenever the pumping system is active. Generally, I recommend slaving them along with the forepump to a single main 'on' switch.

The main valve allows you to close off the vacuum pumping system when you need to. If, for example, you need to work on the pumping system, having a main valve lets you do so without having to put air in the vacuum chamber as well. Just close it before shutting down the pumps, then do your work, and establish high vacuum below the table before opening it again. It can cut the time needed by a factor of, well, several.

Using a gate valve gives you a throttle as well. At high vacuum, the pumping system throughput is proportional to the inlet area. A gate valve allows you to very nicely control the inlet area. If, for example, your pumping system can get you to the eight scale, but you really need to work in, say, a neon atmosphere on the five scale, you can bleed in a little neon gas and control the pressure by throttling with the gate valve. In fact, you could even automate it with a PID loop!

Fast-acting pneumatically controlled gate valves also make good safety valves. If and when seals fail or glass ports crack, having an automatic system to slam the gate valve closed can prevent that high volume of atmospheric gas from flowing through your pumps, which are not really designed for it, anyway. Since gas tends to adsorb onto vacuum system walls and form bubbles in mechanical pump oil, it's best to keep all vacuum equipment under vacuum as much as possible. Of course, if the system contains cold traps or molecular sieves, high pressure will rapidly contaminate them to uselessness. They'll have to be cleaned and degassed before they can go back into service. The same considerations motivate vacuum engineers to add a bypass line that allows pumping the vacuum chamber down to foreline pressure with the main pump and any cold traps or molecular sieves isolated to prevent contamination. Good practice calls for the main and foreline valves to always be closed before opening the bypass.

So, the basic job of your vacuum control system is to sequence operations so that nothing happens at a pressure higher than recommended. Basic pumping system control consists of all or nothing decisions based on vacuum levels. With this simple turbopump-based system, for example, there are 6 inputs and 5 outputs. The 6 inputs are:

1. Penning high-vacuum gauge (H) reading below setpoint;
2. Thermoucouple gauge (T) reading below setpoint;
3. Main valve (M) open/closed;
4. Foreline valve (F) open/closed;
5. Bypass valve (B) open/closed;
6. Pumps on/off (P).

The 5 outputs are:
1. Activate/deactivate pumps (p);
2. Open/close main valve (m);
3. Open/close bypass valve (b);
4. Open/close foreline valve (f);
5. Start application process (o).

Note that I've listed separate signals for, say, opening valves (activation) and signaling that they're open (response). It is certainly possible to (and many engineers do) use the activation signal as the response signal. This gives me the willies because I don't trust any device to operate just because it's being told to. I like to see a separate sensor that independently confirms the action has taken place. For example, a switch mounted on a gate-valve actuator piston can positively confirm that the valve really did close, rather than jamming part way open. On the other hand, I've not added signals to turn the gauge controllers on or off. Both the Penning and thermocouple gauges can survive being left on at atmospheric pressure for short periods of time, though not indefinitely. Other types of gauges, however, cannot and must be interlocked to de-energize at excessive pressure.

Because all of these sense inputs and actuation outputs are binary signals, you can analyze the control system using Boolean algebra, and implement it using logic gates. Gas flows provide timers for sequencing. There is a Boolean equation for every output and every action. For example, to initially pump the system down from atmospheric pressure:

p=1
m=P*F*(~B)*T
b = (~M)*(~F)*(~T)*P
f = P*(~B)

If I've done my logic correctly, selecting the pump-down sequence will initially turn all of the pumps on (p=1); close the main valve because the thermocouple gauge is not below its set point (T = 0); open the bypass valve (b= 0) because the main and foreline valves are closed (M = F = 0), the thermocouple reads high (T = 0), and the pumps are on; and close the foreline valve for the same reason it closes the main valve.

As the mechanical pump does its job, the thermocouple gauge reading will drop, eventually reaching below its setpoint, at which time the bypass valve closes, which allows the foreline valve to open. Gas floods in from the turbopump, which is still at atmospheric pressure, and prevents the main valve from opening. The bypass valve can't re-open once the foreline valve is open.

As more time passes, the mechanical pump draws the foreline pressure back down to the thermocouple gauge setpoint, at which point conditions are right for the main valve to open. Similar Boolean equations need to be written for other operations, such as returning parts of the system to atmosphere for maintenance.

A final equation (o = H) allows operations in the vacuum chamber to commence only when the high vacuum gauge reads below its setpoint.

For more information about vacuum system control, visit the Control Engineering Website and type 'vacuum' into the search box.

For additional information, visit:
www.hyvac.com/PDFs/Literature/Vacuum%20Chart%20and%20Product%20List.PDF

C.G. Masi , Control Engineering senior editor


February 20, 2007

QUESTION: Why do people say Linux isn't a real-time operating system?

To quote Linux for Embedded and Real-Time Applications , by Doug Abbott:

'General purpose operating systems [such as Linux] are tuned to maximize average throughput even at the expense of latency while real-time operating systems attempt to minimize, and place an upper bound on, latency, sometimes at the expense of average throughput.'

According to Abbot, there are several reasons why control engineers do not consider standard Linux suitable for real-time use:

Coarse-grained synchronization means that kernel system calls are not preemptible. Once a process enters the kernel, it can't be preempted until it's ready to exit the kernel. If an event occurs while the kernel is executing, tough luck! The waiting process can't be scheduled until the currently executing process exits the kernel. Some kernel calls can hold off preemption for tens of milliseconds.

Paging —the process of swapping pages in and out of virtual memory—is, for all practical purposes, unbounded. There is no way to know how long it will take to get a page off a disk drive, and so one can't place an upper bound on the time a process may be delayed due to a page fault.

Fairness in scheduling means that the conventional Linux scheduler does its best to be fair to all processes. It may give the processor to a low priority process that has been waiting a long time, even though a higher priority process is ready to run. Try explaining to your insurance company that your braking system react quickly enoughdidn't work because the CD changer had already been waiting 1.5 seconds to get processor time. Linux was just trying to be fair!

Request reordering is a way Linux tries to make efficient use of hardware by reordering I/O requests from multiple processes.

Batching does not refer to what a married man does when his wife and kids go to Grandma's for the weekend. It's a way Linux has of making more efficient use of resources by scheduling similar processes (such as clearing pages associated with different processes out of virtual memory) together in a batch.

These five characteristics often cause the processor to apparently lock up for short periods of time when doing compute or I/O intensive tasks. Of course, as the old project management rule points out: 'How long a minute is depends on which side of the bathroom door you're standing on.'

In a desktop environment, having the mouse stop responding for a few seconds, then jump rapidly is just an annoyance that users learn to ignore. In a real time environment, such as deploying airbags or responding to throttle inputs, it is unacceptable, or even catastrophic.

In fairness (there's that word again), it is important to point out that standard Linux shares these characteristics more or less with other desktop operating systems, such as the various flavors of Microsoft Windows, and Mac OS X. It is, of course, theoretically possible to modify these OSs to change these characteristics. Since Windows and Mac are proprietary operating systems, this change can only be made by their vendors (Microsoft and Apple). Linux, however, is an open-source operating system, so anyone with the requisite skills can modify the kernel to overcome the software's real-time deficiencies. A number of software developers, such as MontaVista and Lynuxworks have made the effort to market Linux distributions with kernels modified for real-time applications.

It is important to remember, however, that no multitasking system can work in real time in the same sense that single-task engines can. For example, in the early 1980s, I was building system controllers out of logic gates and timers that operated on strict Boolean logic lines. The hardware sat there putting out the result of a Boolean expression based on the logic states of a handful of sensor inputs. (Is the turbopump speed above such-and-such a value?) As soon as all the inputs hit the appropriate states, the output shifted to, say, open a gate valve. No time delays (except for propagation delays in the hardware). No uncertainties. Now, that's real time!

Whenever the controller is multitasking, it has to notice that something's trying to get its attention, check its priority compared to the priorities of other tasks and interrupts, then schedule the task in its little queue. In a sense, that forever takes it out of the realm of real time. As a practical matter, though, it is possible to manage the process so that you're guaranteed a response within a certain time window. In that sense, it is possible for Linux to be 'real time.'

For more information about real time control systems, visit the Control Engineering website.

See also, 'Not your Father's RTOS,' by Hank Hogan in the March 2007 issue of Control Engineering .

For additional information, visit these websites:
www.realtimelinuxfoundation.org
www.mvista.com
www.lynuxworks.com

Source: Abbott, D., Linux for Embedded and Real-Time Applications , 2nd Edition, Elsevier-Newnes, ISBN 978-0-7506-7932-9, 2006.

C.G. Masi , Control Engineering senior editor


February 13, 2007

QUESTION: How do I safely monitor the output of a 25 kV dc power supply?

Measuring high voltages—those well in excess of what transistor-based digital meters can withstand—is a common problem. It becomes especially difficult, however, when voltages begin to exceed 10 kV because these voltages can drive excessive power through most electronic components. Until you learn the trick, you get flames instead of measurments. A 1 MÙ resistor placed across your 24 kV supply, for example, will dissipate 625 W. The trick is to spread the power dissipation over a large number of resistors.


Transistor circuits are happiest when working with only a few volts. Junction transistors can get into trouble at voltages as low as 10 V (although many units can go higher). Field effect transistors (FETs) extend this range about another order of magnitude, but I haven't yet heard of a single-element solid-state device that could make 25 kV comfortably. Higher voltages require series stacks of reverse-biased junctions with grading resistors to control the voltage drop across each junction.

I'll come back to grading resistors later.

Transistorized voltage measuring equipment intended to measure a few hundred volts and beyond use precision voltage dividers to bring the level down to something that a solid-state meter circuit can survive. To measure, say, 1,000 volts with 1% precision, start with a 999 KÙ, 1% resistor and a 1 KÙ, 1% resistor in series across the voltage to be measured.

Be sure to put the 1 KÙ resistor on the low-voltage end.

Connect your measurement circuit across the 1 KW resistor. The voltage it sees will be 1/1,000 of the supply voltage or 1 V.

The current through the divider will be 1,000 V / 1 MÙ = 1 mA. The 1 KÙ resistor will only have to dissipate a measly 1 mW. The 999 KÙ resistor, however, will have to deal with just under a Watt, so a much heftier unit is needed.

This analysis points out the problem that higher voltages present. Jacking the supply voltage by another factor of ten—to 10 kV—would increase the power dissipated in the same resistor to 100 W because the power dissipated in a resistor increases with the square of the voltage.

At 100 W, we're getting into the realm of pricey zero-temperature-coefficient precision power resistors, heat sinks, and forced-air cooling. At 25 kV, we're starting to look at things that will warm your feet nicely on a cold day, thank you

Of course, burning all that power just to measure the output voltage puts a bit of a strain on the power supply. Better to increase the resistances by, say, a factor of 1,000, which drops the power dissipation by that much. (Power varies inversely with the resistance.) You could do that with a chain of ten 100 MÙ resistors in series. That drops the power drawn from the 25 kV supply to 625 mW and the dissipation in each resistor to 62.5 mW. Precision resistors for such an application are readily available.

This brings us back to 'grading resistors' as promised. In high-voltage applications, it is important to control not only the voltage between point A and point B, but the gradient as well. Above, I talked about a series of reverse-biased junctions needed to create high-voltage semiconductor devices. Think about a chain of, say, 100 semiconductor diode junctions, each able to stand off 10 V comfortably. The chain theoretically can stand off 1,000 V, but diode junctions—especially reverse biased ones—exhibit notoriously large variability. While they may be rated at 1take enough to 'punch through' its junction. Should that happen, its resistance would suddenly drop to a low value, shifting the strain to all the others. The diode with the next lowest reverse current would then be in jeopardy. Each time one went, the others would come under increasing strain until the whole chain failed.

To prevent this phenomenon, high-voltage engineers add 'grading resistors' to any structure intended to stand off high voltage. Grading resistors bleed a small amount of current (usually on the order of the expected reverse current) to stabilize stacks of stand-off components, such as reverse-biased diodes, capacitors, and stacked insulators. Each stand-off element has a grading resistor connected across it. When any element tries to take up too much of the voltage drop, the current through its grading resistor limits the voltage drop it can maintain.

When you have a grading resistor chain, of course, the way to monitor the supply voltage is to measure the drop across the grading resistor at the chain's grounded end, and multiply by the number of resistors in the chain. I've used this technique to measure voltages as high as 1.5 MV.

For more information about measurement technology, visit the Control Engineering Website and type 'voltage measurements' into the search box.

For additional information, visit these Websites :
www.hipotronics.com
www.keithley.com
www.fluke.com

C.G. Masi , Control Engineering senior editor


February 6, 2007

QUESTION: How can I convert optical fiber to wireless?


Use wireless networking to report measurement results gathered in a mobile platform back to a stationary base station.

This question refers to measurements taken on a vehicle moving down a long track with measurement data sent back via Modbus on via optical fiber. The system suffers frequent fiber mechanical failures resulting in delays and loss of data.

It is a very good idea to convert any mobile measurement system to wireless when the distance over which the sensing 'vehicle' moves is more than a couple of meters, or when rotations of more than 360° are involved. Tethered systems (where data signals pass over a copper or fiber cable) undergoing repetitive movements just ache to spontaneously disintegrate. Slip rings required to keep rotating systems from winding their cables up are just about the noisiest things known. The advent of cheap, reliable wireless data communications solved both problems. About the only things that I know of that can mess up wireless data communications are metal walls and water. Radio waves at useful frequencies still have trouble getting through both.

There are various form factors available, from short range WiFi networks to satellite-based systems that can carry signals around the globe. Most users, however, can work quite nicely with WiFi and, being based on a consumer-oriented standard, the equipment can be inexpensive.

To create a wireless measurement system, you need some intelligence on the mobile platform carrying the sensors. That intelligence collects data from the sensors and packages it for transmission over a wireless network. Any computing engine capable of carrying a data-acquisition module will do. Many small-footprint embedded computers, such as those available from Kontron in PC/104 format, have analog inputs to connect to sensors and virtually all have PCMCIA or USB ports to connect to data acquisition modules from, say, National Instruments. I have also seen systems based on PDAs. I expect smartphones, like the Palm Treo 650, that combine PDA and cellphone, would work amazingly well—although they would probably eat up free minutes like my dog eats pepperoni pizza.

Vendors, such as Phoenix Contact, provide the required transceivers (often referred to as 'radio sets' or just 'radios') to make the wireless connection between the moving vehicle and the stationary 'base station.' A transceiver includes a radio transmitter and a radio receiver to provide two-way communication. The radio set has intelligence to provide secure coded transmissions. The base station includes a complementary radio set that communicates with a host computer, which stores and processes the data.

The biggest problem is making the choices. A possible starting point is the Phoenix Contact Website, which includes some nice tutorials that may provide more help.

For more information about level wireless measurement technology, visit the Control Engineering Website and type 'wireless LAN' into the search box.

For additional information, visit these Websites :
www.kontron.url
www.ni.com
www.palm.com
www.phoenixcon.com

C.G. Masi , Control Engineering senior editor


January 30, 2007

QUESTION: How can I verify operation of a rotating nozzle in a sealed tank?

discrete control

The microphone output should be white noise amplitude modulated at the nozzle rotation frequency. Source: Control Engineering.

machine control & discrete sensors

Full-wave rectifying the microphone output provides a time-varying dc level mixed with the white noise. Source: Control Engineering.

discrete control

Filtering the rectifier output recovers the modulation envelope riding on top of a dc level. Source: Control Engineering.

machine control & discrete sensors

Running the modulation envelope function through an FFT algorithm produces a spectrum that shows a peak at the nozzle-rotation frequency. Finally, a computer algorithm returns a '1' if there is any frequency bin above a preset threshold (red) and a '0' otherwise. Source: Control Engineering.

This question comes from a pharmaceutical company that uses rotating tank-cleaning nozzles in stainless steel tanks of various sizes. Nozzles are driven by reaction force of the liquid spraying out. In some cases, bearings fail and nozzles fail to turn. When this happens, cleaning effectiveness is drastically reduced. The questioner wants a device to detect the pulsations of a unit that is rotating properly.

The first problem is to pick up the sound. The second is to automatically do something useful with it.

A quick-and-dirty solution to the first problem is:

1. Obtain a small microphone;

2. Tape the microphone outside the tank wall facing outward (away from tank);

3. Connect the microphone to an amplifier and listen for noise as the jet strikes the wall inside the tank as it rotates;

4. Sound should modulate at the nozzle-rotation frequency.

The side of the tank will transmit acoustic signals originating in the tank very effectively to the microphone shell. The whole microphone will move, including the diaphragm. Motion of the vibrating diaphragm against the (relatively) still air is aerodynamically equivalent to moving air vibrating against a still diaphragm. Ergo, you should get really good 'sound' pickup.

There are, of course, contact microphones made especially for picking audio-range vibrations up from solid objects. They have a rod or plunger that directly contacts a pickup (such as a piezoelectric crystal) that converts rod movements into electrical signals.

You could also attach a microelectromechanical (MEMS) accelerometer having sufficient sensitivity and bandwidth to the outside of the tank. The accelerometer will register motion of the tank wall as it vibrates. The amplitude will be the actual tank wall displacement multiplied by the square of the sound frequency (not the nozzle-rotation frequency).

Another method is to put an accelerometer or contact microphone in touch with the pipe supporting the nozzle inside the tank. No matter how nicely the bearings are made or how precisely the nozzle is balanced, you're pretty much guaranteed to hear a hum at the nozzle rotation frequency and/or harmonics. You likely will be able to 'hear' it even where the pipe exits outside the tank. It's important to contact the structure holding the nozzle mechanically. You're unlikely to get anything through the fluid.

Still another method using a MEMS accelerometer assumes that you don't have the washer permanently mounted in the tank, but bring it in through a port when you want to clean the tank. Mount the little accelerometer right on the washer nozzle and report its signal wirelessly. The reason for the wireless connection is to let the nozzle carrying the accelerometer rotate freely without any nasty slip rings. The wireless receiver's antenna would have to be inside the tank to receive a signal, but you should be able to combine it with the pipe or tube carrying the tank-cleaning fluid. When the nozzle rotates, the accelerometer will register the centrifugal force. When it stops, the centrifugal force stops. This requires an accelerometer capable of registering constant loads (in other words a bandwidth from dc to a few hundred Hertz).

The second problem involves data acquisition and analysis. Basically, you need to pick out whatever part of the signal tells you the nozzle is rotating. How to do that depends on which method you use to get the signal.

If you're using the last method (MEMS accelerometer riding on the nozzle), your task is pretty simple. Run the accelerometer output through a dc amplifier to boost its level to 1-10 V. Then, wash it through a low-pass filter with a cutoff frequency of a few Hertz. This will remove most of the noise. If the resulting dc level is above a certain threshold (above the noise but below the normal operating level), you have rotation. If not, then not.

If you are using any of the other pickup methods, there's a lot more work to do. You have an ac output signal that you need to process. Start with an instrumentation amplifier to boost the transducer (microphone or accelerometer) output to between one and 10 V peak audio level.

The audio will be a whooshing sound, as shown in the microphone signal plot, which is basically white noise that has been amplitude modulated at the nozzle rotation frequency. So, you need a detector just like they use for AM radio! It's just a half or full wave rectifier followed by a low-pass filter. The rectifier converts the modulation envelope into a low-frequency ac signal plus a dc average value, and adds that onto the white noise as shown in the rectified signal plot. The low-pass filter removes most of the white noise, leaving a 1-10 V dc output signal that varies to follow the sound amplitude as shown in the envelope function plot.

At this point, you can send the remaining signal into your data acquisition card, which samples the output voltage so many times per second. This sampling rate will vary depending mainly on your data acquisition card, but can usually be set to a few thousand samples per second. Ideally, you'd like the sampling rate to be 3-5 times the rotation frequency, but under no circumstances let if fall below twice the rotation frequency. If it goes below that limit, you get what digital signal processing mavens call 'aliasing,' and you just don't want to go there!The data acquisition card puts out a stream of numbers. Each number represents the average dc level in one of the sample intervals. These numbers go right to the host computer's internal bus. Typically, the data acquisition software will collect these numbers in the computer's memory for later processing.

Now, you've got only one task left. You need to determine the signal strength at the rotation frequency. What I like to do is wash the signal through a fast Fourier transform (FFT) algorithm, which takes the set of numbers and looks for patterns that represent waves at various frequencies, then gives you a plot of amplitude as a function of frequency—a spectrum.

The spectrum should show low-level noise at most frequencies with a peak at the rotation frequency and smaller peaks at the rotation frequency's harmonics. Hopefully, the peaks will be much higher than the noise level.

Finally, you need a program that looks for those peaks. It's a simple threshold algorithm that returns a '1' if it sees a signal bigger than the threshold at any frequency, and a '0' if it doesn't.

In the end, you are left with a TTL-level (transistor transistor logic) electrical signal that is high when the nozzle rotates and low when it doesn't.

For more information about vibration measurement, visit the Control Engineering website at www.controleng.com .

Click here to read 'Basics of Signal Conditioning,' Resource Center, free registration required.

For additional information, visit these websites:
www.source.url

C.G. Masi, Control Engineering Senior Editor, charlie.masi@reedbusiness.com





No comments
The Engineers' Choice Awards highlight some of the best new control, instrumentation and automation products as chosen by...
Each year, a panel of Control Engineering editors and industry expert judges select the System Integrator of the Year Award winners.
Control Engineering Leaders Under 40 identifies and gives recognition to young engineers who...
Learn more about methods used to ensure that the integration between the safety system and the process control...
Adding industrial toughness and reliability to Ethernet eGuide
Technological advances like multiple-in-multiple-out (MIMO) transmitting and receiving
Virtualization advice: 4 ways splitting servers can help manufacturing; Efficient motion controls; Fill the brain drain; Learn from the HART Plant of the Year
Two sides to process safety: Combining human and technical factors in your program; Preparing HMI graphics for migrations; Mechatronics and safety; Engineers' Choice Awards
Detecting security breaches: Forensic invenstigations depend on knowing your networks inside and out; Wireless workers; Opening robotic control; Product exclusive: Robust encoders
The Ask Control Engineering blog covers all aspects of automation, including motors, drives, sensors, motion control, machine control, and embedded systems.
Join this ongoing discussion of machine guarding topics, including solutions assessments, regulatory compliance, gap analysis...
News and comments from Control Engineering process industries editor, Peter Welander.
IMS Research, recently acquired by IHS Inc., is a leading independent supplier of market research and consultancy to the global electronics industry.
This is a blog from the trenches – written by engineers who are implementing and upgrading control systems every day across every industry.
Anthony Baker is a fictitious aggregation of experts from Callisto Integration, providing manufacturing consulting and systems integration.
Integrator Guide

Integrator Guide

Search the online Automation Integrator Guide
 

Create New Listing

Visit the System Integrators page to view past winners of Control Engineering's System Integrator of the Year Award and learn how to enter the competition. You will also find more information on system integrators and Control System Integrators Association.

Case Study Database

Case Study Database

Get more exposure for your case study by uploading it to the Control Engineering case study database, where end-users can identify relevant solutions and explore what the experts are doing to effectively implement a variety of technology and productivity related projects.

These case studies provide examples of how knowledgeable solution providers have used technology, processes and people to create effective and successful implementations in real-world situations. Case studies can be completed by filling out a simple online form where you can outline the project title, abstract, and full story in 1500 words or less; upload photos, videos and a logo.

Click here to visit the Case Study Database and upload your case study.