Industrial Electronic Digital Counters

Electronic Counter Frequently Asked Questions

What's the difference between an electronic counter and a panel meter?

A panel meter displays a measured value such as voltage or temperature from a continuous signal. An electronic counter instead processes a pulse train — counting pulses, computing a rate from their timing, or totalizing a running sum — which is a fundamentally different kind of input than the continuous analog signals a meter reads.

What's the difference between totalizing a pulse input and totalizing an analog input?

A pulse input totalizer counts discrete pulses directly, suited to sensors that naturally output pulses (flow meters, encoders). An analog input totalizer instead converts a continuous analog signal (such as a 4-20 mA flow transmitter) into an internal pulse rate before totalizing, which is necessary when the source signal isn't already pulse-based.

What does the rate/totalizer math function configuration do that a basic totalizer can't?

The math function configuration can combine two separate input channels arithmetically — computing their sum, difference, ratio, or product — which is useful for applications comparing two related measurements, such as mixing ratios or inflow versus outflow, rather than simply totalizing one signal on its own.

Why does a batch controller need two relay outputs instead of one?

One relay handles the primary on/off control of the batch (starting and stopping the fill), while the second relay triggers a slow-approach signal shortly before the target is reached, reducing flow rate to improve shutoff accuracy. Using two relays with different trigger points allows for a fast fill followed by a precise, controlled finish.

How does a counter measure AC phase angle and power factor?

The counter times the interval between zero-crossings of two AC signals (typically voltage and current) and derives the phase angle from that timing; power factor is then computed as the cosine of that phase angle. This timing-based approach is why these counters can reach fine resolution — down to about 0.01° at low frequencies.

What is a quadrature encoder, and why does it need a dedicated counter input?

A quadrature encoder outputs two pulse channels offset in phase, which together indicate both position/rate and direction of rotation or travel. A dedicated quadrature input decodes this two-channel relationship (including X1/X2/X4 counting resolution and a zero index pulse) rather than treating it as a single simple pulse stream, which a standard pulse counter input isn't built to interpret correctly.

Can one counter track both rate and total at the same time?

Yes — many configurations can display rate and accumulated total simultaneously from the same input, switchable at the push of a button, rather than being limited to only one function at a time.

What happens to the totalized count if the counter loses power?

Totals are stored in non-volatile memory, so an accumulated count is preserved through a power loss and resumes from where it left off once power is restored, rather than resetting to zero.

Can a counter output its reading to a PLC or SCADA system?

Yes. With the appropriate option board, a counter can retransmit its rate or total as a scaled analog output, trigger relay outputs from configurable setpoints, and communicate digitally over RS-232, RS-485, Modbus RTU, Modbus TCP/IP, or Ethernet.

Electronic Counter Questions From the Field

My totalized count doesn't match what I calculate manually from the process — what should I check?

Confirming the pulse scaling factor configured in the counter matches the actual output of the connected sensor (such as pulses per gallon or pulses per revolution) is the first step, since an incorrect scaling factor produces a total that's proportionally off rather than randomly wrong.

My batch controller overshoots the target every time — what should I check?

Confirming the slow-approach relay's trigger point gives the system enough lead time to actually slow the flow before the final cutoff is the first step, since overshoot is commonly caused by the slow-approach point being set too close to the final target rather than a fault in the counter itself; valve or pump response lag should also be factored into where that point is set.

My rate reading is noisy or jumps around even though the process seems steady — what should I check?

Checking the input's debounce or filtering settings is the standard first step, since a mechanical switch or noisy pulse source can generate extra transitions that a counter interprets as additional pulses; confirming the sensor type matches the input configuration (mechanical contact vs. solid-state) is the next check.

My quadrature encoder reads the correct count but the wrong direction — what should I check?

Confirming the A and B channel wiring hasn't been swapped is the first step, since quadrature direction sensing depends on the phase relationship between the two channels, and reversing them will invert the direction the counter reports even though the count magnitude stays correct.

My counter isn't communicating with my PLC or SCADA system — where should I start?

Verifying the communication protocol, baud rate, and address settings configured in the counter match what the PLC or SCADA system expects is the standard first check, since a mismatch in any one of these will prevent communication even when the physical wiring is correct.

My two-channel math function (ratio or difference) is giving an unexpected result — what should I check?

Confirming both input channels are scaled correctly and that the configured function (sum, difference, ratio, or product) actually matches what the application needs is the first step, since a correctly functioning math operation applied to incorrectly scaled inputs will produce a plausible-looking but wrong result.

My AC phase angle reading drifts or seems unstable at low frequencies — why?

Phase measurement is based on timing between zero-crossings, and at lower frequencies each cycle takes proportionally longer, which can make the measurement more sensitive to small timing variations or waveform distortion; confirming the input signal is clean and free of noise is the standard first check before suspecting the counter.

My relay-based batch cycle sometimes trips early or late compared to other cycles — what should I check?

Confirming the slow-approach and final cutoff setpoints are configured as fixed targets (not accidentally tied to a variable reference) is the first step, since cycle-to-cycle inconsistency often traces to variation in flow rate or valve response time rather than the counter's own setpoint logic.