Every time a system reads an analog signal at intervals, it is gambling that it is reading fast enough to represent what the signal is really doing between reads. The Nyquist rate is the rule that tells you how fast is fast enough. Sample slower than it, and a fast oscillation does not simply go unrecorded - it reappears in your data disguised as a slow one, an error called aliasing that is far more dangerous than a plain gap because it looks like real data. Understanding Nyquist is what separates picking a sample rate on purpose from picking one by habit.
Nyquist Rate in one line: The Nyquist rate is twice the highest frequency present in a signal, and it is the minimum sample rate needed to capture that signal faithfully. Sampling below it causes aliasing, where fast oscillations fold into false low-frequency artifacts in the data. Avoiding aliasing means either sampling above the Nyquist rate or filtering out the high frequencies before sampling.
The sampling theorem states that to reconstruct a signal without ambiguity you must sample at more than twice the highest frequency the signal contains. If the fastest meaningful oscillation in a pressure or vibration signal repeats, say, ten times per second, you need to sample more than twenty times per second to represent it faithfully. That threshold - twice the highest frequency - is the Nyquist rate, and it is a hard floor, not a suggestion. Below it, information is lost in a way that cannot be undone after the fact.
The intuition is that a wave needs at least two samples per cycle to reveal both that it went up and that it came back down. With fewer than two samples per cycle, the samples you collect are consistent with more than one underlying wave, so the true signal becomes ambiguous. Sampling faster than the Nyquist rate resolves that ambiguity; sampling slower leaves it, and the reconstruction picks the wrong answer with no warning that it did so.
It is worth being precise about what frequency matters. The rule keys off the highest frequency actually present in the signal, not the frequency you care about. A slow flow trend you want to watch might sit on top of fast electrical noise or mechanical vibration, and if that high-frequency content is not removed, it still counts toward the Nyquist requirement. Ignoring the fast content that you think you do not care about is exactly how aliasing sneaks into a measurement of something slow.
Aliasing is what happens when you break the rule, and its defining feature is that the error masquerades as real data. When a signal contains frequencies above half the sample rate, those high frequencies do not vanish; they fold back down and appear at lower frequencies that were never in the original signal. A vibration oscillating faster than your sampling can follow will show up in the record as a slow, smooth wave that looks entirely plausible and is entirely fake.
A common way to picture it is the wagon-wheel effect in film, where fast-spinning spokes appear to rotate slowly or backward because the camera frame rate undersamples them. The same folding happens to any undersampled process signal: a fast pressure pulsation can appear as a slow drift, a real high-frequency vibration can appear as a low-frequency rumble, and each false artifact carries no flag saying it is false. That is what makes aliasing worse than a data gap - a gap is visibly missing, but an alias is confidently wrong.
The consequences reach into decisions. An analyst diagnosing equipment from vibration data could chase a low-frequency fault that does not exist, or a control system reading an aliased pressure could respond to a trend that is an artifact of its own sample timing. Because the aliased signal is indistinguishable from a genuine one once it is in the data, there is no cleanup after the fact. Aliasing has to be prevented at the point of sampling, which is why the choice of sample rate is a real engineering decision and not a default.
There are two defenses, and serious measurements use both. The first is to sample fast enough - above the Nyquist rate for the highest frequency you genuinely need to observe. The second is an anti-alias filter: a low-pass filter placed before the sampler that removes frequencies above half the sample rate so they cannot fold down in the first place. Because you cannot remove aliasing after sampling, the filter has to sit in the signal path ahead of the point where the analog value is digitized.
In field instrumentation and SCADA this shows up as a practical pairing of hardware and configuration. Many transmitters and analog input modules include filtering that limits how fast the signal can change before it is read, which suppresses high-frequency noise that would otherwise alias. When an engineer sets a sampling interval in an RTU or collector, choosing it against the fastest real dynamics of the process - and ensuring high-frequency noise is filtered - is what keeps the archived data honest rather than laced with artifacts.
For a cloud SCADA platform like Merobix, the discipline matters most on fast-changing tags. Slow variables such as a tank level or a daily temperature carry no meaningful high-frequency content and are effectively immune to aliasing at any reasonable sample rate. Pressure pulsations, flow surges, and vibration are where undersampling bites, and there the sample rate has to be chosen against the signal's real bandwidth so that the trends and aggregates built on the stored data reflect the process and not an accident of when it was read.
It is twice the highest frequency contained in a signal, and it is the minimum rate at which you must sample to represent that signal without ambiguity. If the fastest oscillation of interest repeats ten times per second, the Nyquist rate is more than twenty samples per second. Sampling below this threshold loses information that cannot be recovered afterward.
A missing sample is visibly absent, but an alias is a false signal that looks real. When you undersample, high frequencies fold down and appear as lower frequencies that were never in the original signal, indistinguishable from genuine data. An analyst or control system can then act on a trend that is purely an artifact of the sample timing, with no flag warning that it is fake.
Two things together: sample above the Nyquist rate for the fastest real dynamics you need, and place an anti-alias low-pass filter ahead of the sampler to remove frequencies above half the sample rate. The filter must come before digitization because aliasing cannot be undone once the value is sampled. Slow tags are naturally safe; fast pressure, flow, and vibration signals need both defenses.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.