The short answer
AutomationDirect
AutomationDirect sells controllers direct, at low cost, with programming software that is free to download, and a share of small water and wastewater sites run on them: lift stations, well sites, chemical feed skids, and package plants built by integrators who value the price and the quick delivery. The current families are Productivity, a tag-based controller in stackable and rack forms; Do-more, whose BRX hardware is the current line and whose CPU can also drop into older DirectLOGIC 205 bases; and CLICK, the small address-based controller for a handful of points. DirectLOGIC is the legacy line, still running on many sites and in retirement. All of them speak Modbus, most speak EtherNet/IP, and several support MQTT, so they connect to any SCADA. What they lack is controller redundancy, the depth of the large-vendor ecosystems, and a local distributor; what they offer is a capable controller at a price that changes what a small utility can afford to automate.
Key points
- Productivity, Do-more with BRX, and CLICK are the current families; DirectLOGIC is legacy.
- The programming software for each family is free; keep the installers and the versions with the site records.
- Modbus RTU and TCP throughout; EtherNet/IP and MQTT on the families and models that support them.
- No controller redundancy and no chassis-scale I/O; suited to small and medium sites.
- Support is direct from the manufacturer by phone and online, not through a local distributor.
Families
| Family | Form | Memory model | Notes |
|---|---|---|---|
| Productivity | Stackable and rack-based series of several sizes | Tag-based with structured data | The closest in feel to the large-vendor controllers; the choice for a small plant |
| Do-more with BRX | Stackable controllers with built-in I/O and expansion; a CPU for the older DirectLOGIC 205 base | Named elements with structures; instruction-rich | The current mainstream line; the migration path for DirectLOGIC 205 sites |
| CLICK and CLICK PLUS | Small stackable controller | Address-based with nicknames | A few dozen points; lift stations, well sites, chemical skids; very low cost |
| DirectLOGIC | Bricks and rack systems of several sizes | Address-based | Legacy; parts availability declining; migrate to BRX or Productivity |
Communications
- Modbus RTU on serial ports and Modbus TCP on Ethernet across the families, as master or slave; the register mapping of each family is fixed and documented, and SCADA drivers use it.
- EtherNet/IP adapter and, on some models, scanner support, for drives and I/O from that ecosystem.
- MQTT publish and subscribe on the families that support it, for cloud and broker-based telemetry.
- Remote I/O within each family over Ethernet, for a rack in another panel.
- Serial ports for radios, meters, and drives; the port configuration is in the project.
What they suit
A duplex lift station, a well with a single pump and a chlorinator, a booster station, a chemical feed system, a small package plant: sites with tens of points, a couple of analogs, a drive or two, and a SCADA link over radio or cellular. At that scale a CLICK or a BRX does everything the process needs at a fraction of the cost of a larger controller, and a Productivity system runs a small plant. An integrator who standardizes on the range and builds a site library can deliver consistent small sites quickly. Where the range does not fit is the large plant with hundreds of points and a historian, the process that needs controller redundancy, and the plant whose staff and spares are built around another ecosystem.
Considerations
- Standardize on one family per utility; a mix of CLICK, DirectLOGIC, and Productivity across sites is three sets of software, spares, and habits.
- Keep the software installers and version numbers with the site records; free software is easy to obtain today and not necessarily in ten years.
- Check the listings needed for the panel: the components are listed, and the panel shop still builds to its own listing.
- The SCADA driver: any platform talks Modbus; a driver that knows the family register map by name saves configuration and mistakes.
- The migration path from DirectLOGIC: a Do-more CPU in an existing 205 base keeps the I/O; a new BRX or Productivity system replaces a brick.
- Support hours and the absence of a local integrator relationship unless the utility has one.
On a site visit
- 1
Family and model
From the label; it decides which software and which cable.
- 2
Indicators
Power, run, error, and port activity; the meaning per family in the manual.
- 3
Project backup
Upload with the family software; store the project and note the software version and the firmware.
- 4
Communications
The port settings in the project against the network schedule; the Modbus map the SCADA driver uses.
- 5
Memory retention
Which family uses a battery and which does not; the replacement schedule where it applies.
Frequently asked questions
- Will a large SCADA platform talk to a CLICK?
- Yes, over Modbus TCP or RTU, using the fixed register map of the CLICK, which the manual and most driver libraries provide. Tag names in the SCADA map to those registers.
- Can I keep the DirectLOGIC 205 rack and replace the CPU?
- A Do-more CPU is made for that base and keeps the I/O modules, with a new program in the Do-more software. The old program is converted or rewritten; the wiring stays.
- Is the lack of redundancy a problem for a lift station?
- Not usually; lift stations on any platform run without controller redundancy and rely on backup float control, a spare controller, and the program backup. A treatment process that cannot lose its controller is a different case and a different platform.
- How do I get help at two in the morning?
- The manufacturer support line has published hours, the documentation and forums are online, and the utility either has an integrator on call or trains its own staff. The same is true of every platform; the difference is that there is no distributor engineer to call.
Related topics
- Modbus TCPModbus over Ethernet: what the MBAP header changes, why the CRC disappears, how the unit identifier works, and what does not get easier just because it is on Ethernet.
- Modbus RTUSerial Modbus over RS-485: function codes, register addressing, the off-by-one that catches everyone, and the physical layer details that decide whether a bus is stable.
- Lift Station Backup ControlHow a lift station keeps pumping when the transmitter, the PLC, or the SCADA link is gone: float backup logic, the control transfer relay, redundant-off protection, and how to test it with the controller actually dead.
- Legacy SystemsKeeping older controllers running and planning a migration: the families still found in water plants, the risks that grow each year, software to keep alive, batteries and memory, tested spares, the security problem, and a migration the plant can survive.
- PLC Program BackupsWhat a complete controller backup contains, how often to take one, where to keep it, why the upload from the running controller is not the master, and the verification that turns a folder of files into a recovery plan.
- How to Configure a Modbus ConnectionSet up a Modbus RTU or TCP link between a controller and a device: get the register map, match the physical and protocol settings, build the reads and writes, handle data types and the addressing offset, and verify with a protocol tool before trusting a value.
Direct contact
Have a controls question?
Reach Eric Sullivan directly about anything on this site, a controls or automation topic, or one of his personal projects.