Industrial Electronic Digital Timers

Electronic Timer Frequently Asked Questions

What's the difference between an electronic timer and an electronic counter?

A counter processes a pulse train — counting pulses or computing a rate from their frequency. A timer instead measures duration — the time elapsed between two events, whether that's a single interval, an accumulated total, or a repeating cycle period. Both share the same panel-mount platform, but a counter answers "how many" or "how fast," while a timer answers "how long."

What's the difference between single event timing and accumulated event timing?

Single event timing captures one interval from a start signal to a stop signal, similar to a stopwatch lap. Accumulated event timing instead sums the duration across multiple start/stop cycles into a running total, useful for tracking total run time across repeated on/off periods rather than just one interval.

How is time interval of periodic events different from basic stopwatch timing?

Basic stopwatch timing captures a single, typically non-repeating interval. Periodic event timing is built specifically to measure the duration of a recurring cycle — the time between one occurrence of a repeating event and the next — which is useful for monitoring the rhythm or consistency of an ongoing process rather than a one-off measurement.

What does duty cycle actually measure?

Duty cycle is the proportion of time a signal spends in its "on" state compared to the total cycle time, usually expressed as a percentage. A PWM-driven motor running at 70% duty cycle, for example, is receiving power for 70% of each switching cycle, which the timer calculates directly from the pulse's on-time and off-time.

What is the serial input remote display configuration actually for?

It's a 6-digit display that receives its value over a serial connection (RS-232, RS-485, or Modbus) from another device, rather than measuring a signal itself. It functions as a large, clear remote readout for a value another instrument or controller has already computed, displaying anything from -999,999 to +999,999.

How precise is the timing resolution on these instruments?

Resolution depends on the specific configuration, but single and accumulated event timing on these platforms can resolve intervals down to a fraction of a microsecond, which supports applications ranging from basic process timing to capturing very short, fast events.

Can a timer trigger an alarm or control output based on elapsed time?

Yes, with the appropriate option board. A timer can drive relay outputs from configurable time-based setpoints and retransmit its reading as an analog output, letting it serve as both an indicator and a simple time-based controller.

Can one of these timers replace a lab stopwatch or oscilloscope for event timing?

For many applications, yes — the high-resolution single and accumulated event timing functions are suited to capturing precise durations such as process dynamics or pulsed events, offering a panel-mounted, continuously logged alternative to a handheld stopwatch or a benchtop oscilloscope for that specific measurement task.

Electronic Timer Questions From the Field

My accumulated timer's total doesn't match what I'd expect from counting the cycles manually — what should I check?

Confirming the start and stop trigger conditions (such as signal edge or logic level) are configured to match exactly what the connected sensor or switch actually outputs is the first step, since a mismatch between the expected and actual trigger condition can cause extra or missed start/stop events that accumulate into an incorrect total over time.

My periodic event timer shows a cycle time that seems to drift slightly between readings — is that expected?

Some cycle-to-cycle variation is expected if the actual physical process isn't perfectly consistent, since the timer is accurately reporting real variation in event timing rather than introducing its own error; if the variation seems larger than the process itself should produce, checking for signal noise or a marginal trigger threshold on the input is the standard next step.

My duty cycle reading doesn't match what I'm seeing on a scope — what should I check?

Confirming both instruments are measuring the same point in the circuit and using the same definition of "on" (such as active-high vs. active-low) is the first step, since a duty cycle calculation depends entirely on which signal transitions are being counted as the start and end of the "on" period.

My serial-input remote display shows a frozen or stale value — what should I check?

Confirming the sending device is still actively transmitting on the expected serial protocol and address is the first step, since a remote display configuration shows whatever it last received and has no way to know the data source has stopped updating.

My timer's relay isn't triggering at the time setpoint I configured — what should I check?

Confirming the setpoint value and relay mode (normally open vs. normally closed) are configured as intended is the first step, since a relay that appears not to trigger is often configured correctly but for a different condition than expected.

My single-event timing reading seems to include extra time I didn't expect — what should I check?

Confirming the exact start and stop trigger points match where the physical event actually begins and ends is the first step, since an event timer measures precisely between its configured triggers, and a trigger set slightly before the true start or after the true end will add that extra time into the reading even though the timer itself is functioning correctly.

My accumulated run-time total reset unexpectedly — what should I check?

Confirming whether a manual reset command was issued (through the front panel or a remote command) versus the total simply reaching its maximum display range and rolling over is the first step, since both will show a reset total but point to different causes and different fixes.