Now and then, someone will ask if a Campbell Scientific data logger can be used in place of a PLC (programmable logic controller) or an RTU (remote terminal unit). Admittedly, it is not a simple question to answer. The capabilities of modern PLCs, RTUs, and data loggers often overlap, making it difficult to classify a device strictly as one of the three. To make this less confusing, I will describe these three roles conceptually, as well as how Campbell Scientific data loggers can fill these roles. In addition, I will briefly describe PACs (programmable automation controllers), which you may have heard of.
A data logger is a device that can perform measurements and store time-stamped data. An internal clock is the primary input to determine when to make the measurements. Other criteria, such as a measured value, may trigger the data storage. A user can retrieve logged data from the device, as well as review data from the past.
Our focus has always been to create hardware that can reliably make accurate measurements—even in extreme environments. Because Campbell Scientific data loggers need to operate autonomously without user interaction for extended periods, they run a custom real-time operating system with a flexible programming language. (Please note that data loggers from other manufacturers may not have all the same features.) To avoid confusion, for this discussion, I will simply refer to the CR1000X Measurement and Control Datalogger. The CR1000X possesses an accurate clock, makes reliable analog measurements, logs the data, and is designed for low power consumption.
The focus of a PLC is on operating simple control loops. It reads sensors but only holds the current set of readings. A PLC can make a quick response with a control output. The device must be reliable and operate in a predicable manner. Standardized programming languages for PLCs are logic based. Communication is back to a client, which could be directly to a SCADA computer or to an RTU. Some PLCs are very simple process controllers with one input and one output. Other PLCs are rack-mounted modular installations with hundreds of channels.
The CR1000X often can fill the role of a PLC. Control loops are possible using the CRBasic programming language, meaning that a trained SCADA engineer would need to learn CRBasic and use it instead of the standard PLC languages. The CR1000X is fast enough for many control applications. Some parallel control applications would require more speed.
An RTU reads inputs (such as from sensors), has programmable logic to change outputs based on inputs, and reports back to a client controller. The client controller is traditionally a computer running SCADA (supervisory control and data acquisition) client software. Programming languages for RTUs allow for more flexibility than on a PLC. Typically, an RTU can continue its operation, even in the event of communication loss back to the client. Some RTUs are small integrated units with a few channels, and other RTUs are rack-mounted units with hundreds of channels.
The CR1000X easily fits the role of an RTU. It supports Modbus and DNP3 standard protocols often used for communication to RTUs. One concern, however, is to check the needed signal levels of the sensors and outputs. Industrial applications often use large voltages or current loops for noise immunity. The CR1000X may need TIMs (terminal input modules) or SDMs (synchronous devices for measurement) to fill the application’s needs. Expansion modules, such as SDMs and CDMs (Campbell distributed modules), can increase the number of inputs and outputs.
Some new industrial devices are being classified as PACs. The term basically means a PLC with enough programming capability to take the place of a SCADA PC. With its ability to be a Modbus client device, the CR1000X closely fits the definition of a PAC. The CR1000X, however, lacks the support of other common industrial protocols.
There is a large variety of PLC and RTU models. As such, there is a very large price range. The CR1000X is more affordable than some of these units. What really matters, however, is whether the device you use has the features you need for your application. When you only need a simple process controller, a small PLC is much more affordable than a CR1000X. If you need multiple analog channels and communication flexibility, a CR1000X can be very price competitive.
There are some additional features in Campbell Scientific data loggers not found in traditional PLCs, RTUs, or PACs. These features may solve problems you can't with other devices. Some notable features are low power consumption, remote telemetry options, and greater sensor compatibility. If you encounter a problem you can't solve with a PLC, RTU, or PAC, look into a Campbell data logger.
I hope this article has clarified some of the differences between the various data acquisition and control roles. The CR1000X is a very capable and versatile data logger, able to fill many measurement and control roles. Other Campbell Scientific data loggers, such as the CR300 and CR6, also have this flexibility. Please share below your experience using Campbell Scientific equipment in roles other than just data logging.