LTE DIN Rail Digital Transmitters with Ethernet Communication and Analog Outputs for Pulse Totalizer Applications

LTE Pulse Input Totalizer Transmitter Frequently Asked Questions

Does the documented storage of totals in non-volatile memory mean the transmitter continuously writes to that memory during every pulse count?

The page documents totals as being stored in non-volatile memory without detailing the specific write frequency or timing of that storage — this is consistent with periodic or event-driven writes rather than a write occurring on literally every single incoming pulse, since continuous per-pulse writes to non-volatile memory would be unusual practice given typical memory write-cycle endurance considerations, though the page itself doesn't specify the exact write interval.

Why does the documented "Machine ON Time and Utilization" application specifically apply a 100 multiplier to the A/B ratio to get duty cycle percent?

Documented description specifically frames duty cycle as the ratio of switched-AC cycles (Channel A) to total AC-line cycles (Channel B) — since a ratio expressed as a decimal fraction (such as 0.75 for 75% duty cycle) needs to be converted to a percentage for conventional duty-cycle reporting, the documented 100 multiplier is the standard mathematical step converting that raw A/B decimal ratio into the percentage figure operators expect to see displayed.

Does the documented "Up or Down Counting with Preset" application require the Extended main board, or is it available with the Standard board?

Documented description specifically lists this capability under the Extended main board's feature set, distinct from the Standard board's more basic total/rate tracking — the documented requirement for "the dual relay option" alongside this application further indicates it's built on Extended-board-level functionality, consistent with preset-based counting logic requiring the additional processing capability the Extended board provides over the Standard board.

Can the external reset for up/down counting with preset use any available control input, or is the documented three-position screw terminal specifically required?

Documented description specifically states external reset of totals is "via a special three-position screw terminal connector," identifying this as a specific, dedicated hardware connection point; this is consistent with the reset function being tied to that particular physical terminal arrangement rather than being freely assignable to any other general-purpose control input the transmitter may offer.

Does inhibiting Channel A counting via a Channel B input (in the documented up/down totalizing mode) pause the totalizer, or does it also affect the documented rate output?

The page documents this inhibit function specifically in the context of totalizing (accumulated count), without detailing whether a simultaneously active rate output would also be affected — since rate and total are documented elsewhere as distinct, separately trackable outputs (with the Extended board specifically able to display both), an inhibit applied to Channel A's counting is consistent with primarily affecting the accumulating total, though the specific interaction with a concurrently active rate calculation isn't detailed on this page.

Does this LTE Pulse Input Totalizer transmitter's documented Modbus TCP-only protocol limit compatibility compared to the RS232/RS485 LT Series totalizer variant?

Yes — this page documents Modbus TCP specifically as the supported Ethernet Data I/O protocol at digital address 247, while the LT Series serial variant is documented elsewhere as separately supporting Modbus RTU/ASCII and Laurel Custom ASCII; a control system needing a protocol other than Modbus TCP would need to reference the LT Series serial variant rather than this LTE Ethernet variant.

Does the documented custom curve linearization apply only to the totalized value, or can it also correct the rate reading?

Documented description specifically states the Extended version "can transmit scaled rate or total for the same channel at the push of a button, and alarm both the rate and total," and separately notes linearization "extends the working range and accuracy of flow transducers" — since both rate and total are documented as derived from the same underlying linearized signal processing for a given channel, custom curve linearization is documented as improving both the total and the rate reading together, not just one or the other.

Does the documented A/B ratio for combining two totals require both channels to have identical pulse-per-unit scaling factors?

The page documents A/B ratio applied to two totals as helping "assure the proper mixing of components," without stating that both channels must share identical scaling factors — since each channel is documented as independently scalable, the meaningful A/B ratio for a mixing application depends on both channels being correctly and consistently scaled to their own respective physical units (such as gallons for each), rather than requiring the raw, unscaled pulse counts from each channel to use identical scaling.

Does selecting the maximum documented pulse frequency (1 MHz) on Channel A affect the transmitter's documented totalizing accuracy?

The page documents 1 MHz as the maximum input pulse rate without listing a separate, reduced accuracy figure specifically tied to operating at that maximum frequency — the transmitter's documented crystal-timed period measurement approach is consistent with maintaining its stated accuracy across the specified frequency range, though extremely high pulse rates in any counting system can in principle be more sensitive to noise, which is why the page separately documents selectable noise filtering and contact debounce settings.

Does power consumption increase when the transducer excitation output is set to its maximum documented level, and by how much?

Yes — documented specification lists power consumption as "2.5W typical at 24V, 4.0W with max excitation output," directly quantifying the additional power draw when the transducer excitation output is set to its maximum documented level, representing a genuine, specified increase tied to how much excitation current is being supplied to an external sensor.

Totalizer Power-Fail Recovery & Non-Volatile Memory Questions From the Field

What specifically happens to an accumulated flow total during a power failure if a totalizer does NOT use non-volatile memory or a "save" mechanism?

Documented field guidance specifically warns that in some systems, the accumulated value resets on a power cycle unless total values are explicitly persisted to non-volatile memory — for critical applications, documented practice specifically recommends using a save/persist mechanism to write accumulated tags to non-volatile storage precisely to prevent this reset-on-power-loss behavior.

Does a totalizer's non-volatile EEPROM memory typically require an external battery to retain stored totals?

No — documented product descriptions specifically state that parameters and totals are stored in non-volatile EEPROM memory "which doesn't need any external battery," with documented power-fail features automatically saving the total flow reading and resuming from the same value after power is restored, without relying on a battery to bridge the power-off period.

Is there a documented technical reason non-volatile memory devices can encounter difficulty if power is interrupted specifically during a write operation, as opposed to during a read?

Yes — documented technical analysis specifically explains that non-volatile memory data is generally safe during read operations regardless of a power failure, but if power is interrupted during an active write process, some memory cells may end up with unstable, partially-written values; documented analysis further notes that simply checking already-stored values afterward may not reliably indicate where writing should resume, making mid-write power loss a genuinely different and more difficult failure mode than a read-time interruption.

Is there a documented recovery technique for locating a safe restart point in non-volatile memory after a power-loss event during writing?

Yes — one documented patent-level approach specifically describes scanning pages of a memory array to find the first free page after a power loss, marking that page as available, and directing the next write cycle to that specific located page; this documented method is specifically designed to safely resume operation without relying on potentially corrupted data from the interrupted write.

Does frequent non-volatile memory writing for totalizer updates create a documented long-term wear concern, separate from the power-failure issue itself?

Yes — documented technical analysis specifically identifies limited write endurance as an inherent characteristic of non-volatile memory technology, noting that frequent modifications to accumulating data can result in a significant number of writes over a device's service life; documented engineering approaches specifically address this by deferring or batching updates to minimize total non-volatile memory write overhead while still preserving data consistency.

Is there a documented practical example of a networked totalizer device specifically designed to prevent a totalization count from resetting after a power interruption?

Yes — one documented field discussion specifically describes a dedicated pulse-processing device that accumulates and stores the total pulse count (alongside instantaneous flow rate) in Modbus registers, with the pulse count specifically stored in non-volatile memory so the totalization count doesn't return to zero after a power loss, illustrating a genuine, deployed example of this design principle in networked flow totalizing equipment.

Does periodically accumulating flow rate into a running total (rather than counting raw pulses) introduce a documented accuracy tradeoff related to how frequently the accumulation occurs?

Yes — documented field discussion specifically describes this tradeoff using a worked example: accumulating flow rate into a total only once per hour is characterized as "not very good," with the documented recommendation to instead accumulate much more frequently (such as once per second, dividing the hourly rate figure accordingly) to achieve a genuinely accurate running total, illustrating that accumulation frequency itself is a real, quantifiable factor in totalizing accuracy for rate-based (versus raw pulse-count-based) totalizing methods.

Are non-volatile flow totalizers documented as suitable for use in flameproof or explosion-proof industrial enclosures?

Yes — one documented commercial flow totalizer example specifically describes a flameproof-execution model with non-volatile memory, an IP65-rated explosion-proof enclosure, and dual LED digital displays for flow rate and totalized flow, confirming that non-volatile-memory-based totalizing capability is documented as available and deployed even in hazardous-area-rated industrial instrument enclosures.