Digital Panel Meter for Frequency, Rate, or Period Applications P/N L70126FR

Frequency, Rate & Period Digital Panel Meter Frequently Asked Questions

Why does this specific meter's arithmetic function list include AxB, unlike some other Laureate ratio/draw configurations?

Documented capability on this specific dual-channel counter configuration lists AxB alongside A+B, A-B, A/B, and A/B-1 — this reflects that the Extended counter's full arithmetic function set is available here, whereas other documented Laureate configurations built around ratio and draw specifically may offer only a subset of these functions; confirming the exact function set against the specific board and firmware configuration in use is worth doing when AxB (such as computing power from two channels) is a requirement.

Why does the meter offer nine different minimum-signal ranges instead of one universal input sensitivity?

Documented signal compatibility spans a huge range of source types — from millivolt-level magnetic pickups to multi-volt logic signals — and a single fixed sensitivity threshold couldn't reliably trigger on the smallest signals without also risking false triggering from noise on larger signals; nine selectable ranges let the meter's trigger threshold be matched to the actual signal amplitude of whatever sensor is connected.

What's the practical difference between the noise filter setting (1 MHz/30 kHz/250 Hz) and contact debounce (0/3/50 ms)?

These target different noise sources at different timescales: noise filter is aimed at filtering genuine high-frequency electrical interference on the signal line, while contact debounce specifically addresses the millisecond-scale multiple transitions produced by mechanical switch contacts settling after closure — an application with a mechanical limit switch would typically need debounce enabled, while one with electrically noisy but bounce-free signals relies more on the noise filter.

Does "Time Before Zero Out" affect the gate time used for normal measurement, or is it a separate, independent setting?

It's documented as a separately selectable setting from gate time — gate time controls the timing window used to compute each reading, while Time Before Zero Out specifically indicates loss of signal by zeroing the display if no valid new signal arrives within that separately configured window, rather than continuing to show a stale last reading indefinitely.

Can the peak reading and an arithmetic combination like A/B both be transmitted over the same serial connection simultaneously?

Yes — documented system-level capability specifically states that all signal or alarm data, including peak readings and arithmetic combinations of the two rates, can be transmitted via RS232 or RS485 — a connected data logger or SCADA system can capture multiple derived values from the same physical connection rather than needing separate transmission paths for each.

Does the analog output track the raw Channel A or B reading, or can it be configured to output an arithmetic combination like A-B?

Documented capability specifically states displayed rates can be transmitted as an isolated 4-20 mA or 0-10V analog output — since arithmetic combinations like A-B are among the values the meter can display, and the analog output is described as tracking the displayed rate, this suggests the analog output can track whichever value (raw channel or arithmetic combination) is currently configured for display.

Why is Channel B's maximum frequency (250 kHz) lower than Channel A's (1 MHz)?

This reflects a real hardware asymmetry between the two channels' processing capability — for applications where both connected signals stay comfortably below 250 kHz, this asymmetry rarely matters, but it's worth confirming neither expected signal genuinely needs to exceed 250 kHz if it's being applied to Channel B specifically.

Does entering the XXXXEX scientific notation display mode affect the meter's underlying measurement accuracy?

No — this is documented specifically as a display-range accommodation: once a value exceeds the standard ±999,999 count display range, the meter flashes and switches to a four-digit scientific notation format to keep very large values representable on the six-digit display, without changing the underlying measurement or totalizing accuracy.

Can custom curve linearization be applied to a signal other than a turbine flow meter's nonlinear low end, since that's the documented example?

The documented primary example is specifically turbine flow meter linearization, but the underlying 180-point spline-fit technique is a general-purpose Extended-board capability — any pulse-rate signal with a known nonlinear relationship to the physical quantity being measured could in principle be linearized the same way, not exclusively flow signals.

Does selecting a shorter gate time for faster response come at the cost of measurement accuracy, or just update speed?

Both, to some degree — the inverse-period technique documented here specifically achieves faster update times than conventional pulse-counting meters at a given gate time, but a shorter gate time still averages fewer signal periods overall, so there's a genuine tradeoff between how quickly the display responds to a changing signal and how much averaging smooths out reading-to-reading variation; applications prioritizing fast alarm response over maximum reading stability would choose a shorter gate time, and vice versa.

Magnetic Pickup (Variable Reluctance) Sensor Questions From the Field

Why does a magnetic pickup's output signal change in both amplitude and frequency as speed changes, rather than just frequency?

Documented sensor physics specifically explains this: as a ferrous gear tooth passes the sensor, the changing air gap alters magnetic reluctance, inducing an AC voltage whose frequency is proportional to speed — but the signal's amplitude is also documented as depending on speed itself, along with air gap, target geometry, and target material, meaning both properties shift together rather than frequency alone carrying all the speed information.

Why do magnetic pickups specifically struggle to produce a usable signal at very low rotational speeds?

Documented explanation specifically ties this to the underlying physics: signal amplitude is generated by the rate of change of magnetic flux as a tooth passes, and at very low rotational speeds that rate of change is inherently small, producing a correspondingly weak signal — this is documented as the primary limitation of variable reluctance sensors for reliably detecting very slow movement.

How much does increasing the air gap between a magnetic pickup and the target actually affect the output signal?

Documented guidance specifically states that signal amplitude decreases as air gap increases, with most VR speed sensor applications requiring a fairly tight gap (a documented example cites 0.005" to 0.015") between the sensor tip and the gear tooth — wider gaps are possible, but signal amplitude drops significantly as the gap grows, which is why gap specification is treated as a genuinely critical design parameter, not a minor installation detail.

Can vibration in a real installation cause a magnetic pickup's signal to degrade over time even without any sensor failure?

Yes — documented analysis specifically identifies vibration as capable of loosening the sensor's mounting hardware, which changes the air gap width and correspondingly degrades signal amplitude, even though the sensor itself remains fully functional; this is specifically documented as a reason for periodically verifying signal amplitude in demanding environments like automotive engine compartments.

Is there a way to distinguish signal loss from a widened air gap versus signal loss from an actual sensor winding fault?

Documented patent literature specifically identifies both as real, distinct failure modes producing similar symptoms — attenuated signal amplitude can result either from an air gap that's grown too wide (mechanical cause) or from a partial short-circuit in the sensor's electrical winding (electrical cause), or even a damaged/buckled toothed wheel — meaning amplitude degradation alone doesn't pinpoint which specific failure occurred without further investigation.

Should speed be calculated by counting pulses (frequency) or by measuring the signal's amplitude, given that both change with speed?

Documented practical guidance specifically confirms frequency counting, not amplitude measurement, is the correct approach — speed calculated as (60 × measured frequency) / number of target teeth is the documented standard formula, since frequency has a clean, direct proportional relationship to speed while amplitude is influenced by multiple confounding factors (air gap, target geometry, temperature) that make it unreliable as a standalone speed indicator.

Does a magnetic pickup's output waveform arrive as a clean square wave, or does it need conditioning before a counter can use it?

Documented guidance specifically describes the raw output as an analog, quasi-sinusoidal AC voltage — in most control system integrations, this signal passes through a signal conditioner (commonly a comparator forming clean pulses from the sinusoidal waveform) before a digital counter or controller can reliably count it, rather than the sensor itself producing ready-to-count digital pulses.

Does a magnetic pickup require external power to generate its signal, unlike an NPN/PNP proximity switch?

No — documented sensor classification specifically describes variable reluctance sensors as passive or electromagnetic sensors that don't require an external supply, since the AC voltage is self-generated by the changing magnetic field as the target passes — this differs from active sensor types like NPN/PNP proximity switches, which do require external excitation power to operate.