A discharge sample comes back out of specification. The obvious first question, what was the dosing pump actually doing at the time, is often the hardest one to answer. If the pump has no memory of its own operation, the plant is left reconstructing events from operator recollection and whatever paper logs happened to be kept, which is rarely enough to identify whether the pump failed, ran out of chemical, lost power, or was operating exactly as intended and the problem lay elsewhere in the process.
The Gap Between an Incident and an Explanation
Regulators and internal audits generally don’t accept “the pump seemed fine” as an answer. Without a record tied to a timestamp, a plant can’t distinguish between a five-minute power interruption that happened to coincide with a sample, an alarm condition that ran unnoticed for hours, or genuinely correct pump operation that simply wasn’t enough for an unusual influent load. Each of those has a different corrective action, and none of them can be identified after the fact without data.
What the Atlanta Records
The Atlanta control unit maintains an internal alarm log of up to 48 events, each timestamped and viewable directly on the display, ordered by date. The alarm conditions it tracks cover the range of failures that actually cause dosing problems: a level alarm from a chemical tank probe, a remote hold from the Pause input, high motor temperature, abnormal back pressure or load, a power supply fault, an internal communication error, a Modbus watchdog fault, and current or voltage inputs that fall outside the programmed range on mA or V Mode. During any active alarm, the display backlight turns red, so an operator walking past the pump has an immediate visual cue independent of whether they check the log.
Two Layers of Statistics
Alongside the alarm log, the Atlanta separately tracks operating statistics in two forms. Partial statistics, working time, dosed quantity, and power-on count, cover the period since the last manual reset, useful for reviewing a specific interval such as the time since the last service visit. Total statistics cover the same three figures since the device’s first use and cannot be reset, giving a permanent record of the pump’s full operating history regardless of how many times the partial figures have been cleared. Reviewing both together makes it possible to separate a recent short-term issue from a pattern that’s been building over the pump’s entire service life.
Getting the Data Off the Pump
The 48-event log is a fixed local buffer, useful for a quick on-site check, but not a substitute for continuous record-keeping if a compliance programme calls for a longer retention period. The Atlanta’s RS485 Modbus interface exposes the same alarm states and statistics registers to any connected system, so a SCADA platform or PLC can poll and log this data continuously, well beyond what the pump itself can store, and tie it directly into whatever record-keeping system the plant already uses for its discharge consent reporting.
Where This Fits
This matters most at any dosing point where a failure has direct compliance consequences, disinfection ahead of discharge, pH correction, or any chemical addition a discharge consent specifically references. Having a timestamped record of pump condition turns “we’re not sure what happened” into a specific, defensible answer.
Autoflo Technology is the authorised distributor of the Injecta Atlanta series in Malaysia. For help wiring alarm and statistics data into your plant’s monitoring system, contact us at info@autoflotechnology.com.