Digital Panel Meters for Batch Controller Pulse Input Applications P/N L80310FR

Batch Controller Pulse Input Digital Panel Meter Frequently Asked Questions

What is a preact (or preset) value, and why does a batch controller need one?

A preact value tells the controller to close the valve or stop the feed before the pulse count reaches the actual target, anticipating the material still in transit between the shutoff signal and the valve physically closing. Without a preact value set correctly, the batch will consistently overshoot the target by roughly the amount of material that flows during the shutoff delay.

What is two-speed (bulk and dribble) fill, and why is it used?

Two-speed fill runs the batch at a fast bulk rate for most of the fill, then switches to a slower dribble rate as the target approaches, reducing the amount of material still in motion when the final shutoff occurs. This significantly improves batch accuracy compared to running a single fast fill rate all the way to the target.

Can the batch controller run more than one output stage, like fast-fill and slow-fill valves?

Yes, many batch controller meters support independent fast-flow and slow-flow relay outputs, triggered at different pulse counts within the same batch, so the controller automatically switches from bulk fill to dribble fill without additional external logic.

Does the meter retain the batch total if power is lost mid-batch?

Many models store the accumulated pulse count in non-volatile memory, so a batch in progress can potentially be resumed rather than lost entirely after a power interruption, though the exact recovery behavior depends on the specific model and how the batch sequence logic is configured.

Can the same meter run repeated batches automatically, or does each batch need to be started manually?

Many batch controller meters support an auto-restart mode where a new batch begins automatically after the previous one completes and resets, which is useful for continuous or high-volume batching operations, in addition to manual start via a pushbutton or external contact.

What kind of pulse input signals can these meters accept for batching?

These meters typically accept the same range of pulse signal types used for flow and rate measurement — proximity switch outputs, magnetic pickups, TTL/CMOS logic, and dry contact closures — with the input configured to match whatever flow meter or sensor is generating the pulses for that batch.

Can the batch target and preact value be changed between batches without reprogramming the meter?

Yes, on most models the batch target and preact value are adjustable parameters that can be changed from the front panel or via communications between batches, rather than requiring a full reconfiguration of the meter each time a different batch size is needed.

Is there a lockout or key-protected reset to prevent an operator from accidentally resetting a batch in progress?

Many batch controllers offer a count-inhibit-until-reset feature or a protected/keyed reset function specifically to prevent an accidental or unauthorized reset from interrupting a batch in progress or corrupting the totalized record.

Can the meter also totalize a running grand total across many individual batches?

Yes, many batch controller meters support a totalizer function alongside the per-batch counter, either incrementing continuously with each batch or accumulating a separate running total, which is useful for tracking full-shift or full-day production alongside individual batch counts.

What alarm and communication options are available for integrating the batch controller into a larger system?

These meters commonly support relay outputs for batch-complete or fault conditions, and serial communications such as RS-232 or RS-485, allowing the batch controller to report status and completion to a PLC or SCADA system rather than operating only as a standalone local device.

Batch Controller Questions From the Field

Why does my batch consistently overshoot the target by roughly the same amount every time?

This is one of the most commonly reported batching issues, and field guidance is clear that it's almost always valve closure delay, not flow meter calibration — between the moment the controller reaches its shutoff count and the valve fully closes, several delays stack up: controller processing time, relay activation time, and the mechanical time for the valve itself to physically close, during which material is still flowing. Increasing the preact (preset) value to shut off earlier, matched to the measured delay, is the standard fix rather than recalibrating the flow meter.

My batch overshoot amount changes depending on how fast the line is running — why isn't it a fixed number?

This is expected and consistent with the valve-delay explanation above — since overshoot is driven by how much material continues flowing during a roughly fixed time delay, a higher flow rate during that same delay window pushes more material through, producing a larger overshoot volume. This is why switching to a slower dribble rate before shutoff, rather than shutting off directly from full flow, meaningfully reduces overshoot.

Why did my batch counter's "done" output stay on even though the accumulated count kept climbing past the target?

This is a documented and often misunderstood behavior in counter logic: many counters do not stop counting once the accumulated value reaches the preset — they simply set a "done" flag and continue counting on every subsequent pulse until an explicit reset is issued. If the batching logic isn't watching for that done condition and acting on it immediately, the accumulator (and therefore the process) can keep going well past the intended target.

Why is my batch counter's cutoff timing inconsistent even though the pulse rate from the flow meter seems steady?

This is commonly traced to the counting or scan logic not keeping up with the pulse rate consistently — if the controller's processing cycle isn't fast enough or consistent enough relative to how quickly pulses are arriving, the exact moment the cutoff action fires can vary slightly from batch to batch. Using a dedicated high-speed counting input, rather than general-purpose scanned logic, for the critical shutoff decision is the standard remedy for tightening this consistency.

How do I figure out the right preact value for my specific system instead of guessing?

The practical field approach is to run a batch with a small, conservative preact value, measure the actual overshoot that results, and then increase the preact by that measured overshoot amount, repeating until the batch lands consistently on target. This empirical tuning approach accounts for the specific combination of valve type, pipe size, and flow rate on that particular system rather than relying on a generic preset number.

Why does my batch total come out slightly different from the target even when both fast-fill and dribble stages seem to be working correctly?

A small residual discrepancy after tuning fast-fill and dribble stages is commonly attributed to remaining valve closure delay at the (much lower) dribble flow rate, mechanical compliance in the system, or minor pulse-count rounding, rather than a fault. Field guidance generally treats a small, consistent residual as something to fine-tune the preact value further against, rather than a sign of a broken component.

Should batch weight or volume targets be locked out from operator changes mid-batch?

Yes — this is a commonly recommended safeguard in batch control system design: allowing an operator to change the target weight or preact value while a batch is actively running can produce unpredictable results, so batch control logic is typically designed to disable target-adjustment controls once a batch has started, only re-enabling them once the batch completes or the system is reset to an empty/idle state.

What's the best way to keep track of multiple materials being added to the same batch without losing track of quantities?

Field discussion on multi-ingredient batching generally emphasizes building a clear data model before writing the control logic — typically an array or table tracking the accumulated weight or volume of each individual material as it's added, rather than trying to track a single combined total, so that each ingredient's contribution to the batch can be verified and reported independently.