LT DIN Rail Digital Transmitter for Batch Controller Analog Input Applications

Batch Controller Analog Input Transmitter Frequently Asked Questions

Why convert the analog signal to a frequency instead of processing it directly?

Converting to frequency lets the batch controller use the same precise, quartz-referenced counting and totalizing logic built into the rest of the LT Series, so an analog 4-20 mA, 0-1 mA, or 0-10V signal gets the same batch-control capability as a native pulse-output flow meter.

How does the slow-approach relay actually reduce batch overshoot?

By switching the fill valve or pump to a lower flow rate as the batch nears its target, the amount of material still in transit when the shutoff signal fires is smaller, so the final overshoot past the target is reduced compared to shutting off abruptly from full flow rate.

Can both relays be reassigned to something other than the standard on/off plus slow-approach configuration?

The default arrangement dedicates one relay to on/off batch control, but the second relay's function (slow-approach or another alarm/control role) is configurable, so it can be adapted to whatever secondary control action a specific installation needs rather than being locked to slow-approach only.

Does choosing 4-20 mA, 0-1 mA, or 0-10V input affect batch accuracy?

No — all three input types feed through the same V-to-F conversion and subsequent counting logic; the choice is determined by which signal type the connected flow transmitter already produces, not by any difference in batch measurement accuracy.

Can this transmitter be used with a differential pressure flow transducer?

Yes, with custom curve linearization on the Extended board correcting for the transducer's characteristic nonlinearity before the signal feeds into the totalizing and rate calculations, since a raw DP signal isn't linearly proportional to flow rate without that correction.

What's the difference between magnetic and solid state relay options for this batch controller?

Magnetic relays handle higher current (8A) directly but have mechanical wear characteristics over repeated cycles, while solid state relays (120 mA) switch faster and have no moving parts, making them better suited to high-cycle-count batch applications at the cost of lower current handling.

Can the programmable delay between batches be skipped entirely for back-to-back fills?

The delay can be set as low as 10 ms, and an external control input can also be used instead of the internal delay timer, so a configuration close to immediate back-to-back cycling is achievable depending on how the fill process itself needs to be sequenced.

Does the second tracked item (grand total or batch count) reset between batches?

No — it's specifically meant to accumulate across multiple batches (as a running grand total or a count of completed batches), while the first tracked item (current batch total) is what resets or counts toward a preset for each individual batch cycle.

Can this transmitter be networked with other batch controllers or transmitters?

Yes — up to 30 LT Transmitters and/or Digital Panel Meters can be daisy-chained on RS485 for LAN integration, or a high-speed Ethernet or WiFi communication board can be used instead for network connectivity.

Batch Controller Analog Input Transmitter Questions From the Field

My batches consistently overshoot the target even with the slow-approach relay configured — what should I check?

Verifying the slow-approach relay actually triggers early enough before the target (rather than too close to the setpoint to meaningfully slow the fill) is the first step, since the timing of when the slow-approach kicks in relative to the target total directly determines how much overshoot reduction it provides.

My batch total reading seems inconsistent with a handheld flow meter reading on the same line — what's the likely cause?

This usually traces to a scaling mismatch between the conditioned analog signal's actual full-scale range and what's configured in the transmitter's V-to-F setup, rather than a fault in either instrument; confirming the transmitter's configured input span matches the flow transmitter's actual output span is the standard check.

My on/off batch relay doesn't shut off exactly at the target total — what should I check?

Confirming the preset target configured in software actually matches the intended batch size, and that the relay is genuinely wired to and configured for the on/off batch control function (rather than the slow-approach function), are the first steps before suspecting a measurement or timing fault.

My batch controller's total drifts over many cycles even though individual batches look correct — why?

Small individual measurement variations that are inconsequential per batch can accumulate into a visible grand total drift over many cycles; if this matters for the application, periodically verifying the grand total against an independent measurement (like a tank level check) helps confirm whether the drift is real or within expected tolerance.

Can noise on the 4-20 mA loop cause a batch to complete early?

Yes — noise superimposed on the analog signal gets converted along with the genuine signal into the internal frequency used for totalizing, so persistent electrical noise can add false accumulation and cause a batch to appear complete before the actual delivered volume reaches the target; checking cable shielding, grounding, and loop wiring quality is the standard remedy.

My custom curve linearization doesn't seem to be correcting the DP transducer's nonlinearity properly — what should I check?

Verifying that the entered data points genuinely span and adequately sample the transducer's actual working range (particularly at the low end, where DP transducers are most nonlinear) is the standard first check, since sparse or narrow-range data points won't adequately correct the curve across the full operating range.

My batch delay timer doesn't seem to match what I configured — what should I check?

Confirming the configured delay's units and magnitude match what's actually intended (since the range spans milliseconds to just under 200 seconds) is the first step, as a value entered in the wrong units or order of magnitude would produce a timing discrepancy that looks like a fault but is really a configuration mismatch.