Running cCare From the Control Room: Remote Control via the Profinet Module

Automating sensor cleaning and calibration at the measuring point removes a significant manual burden. But the next step is equally valuable: operating that automation from where your operators already sit. If your team is managing a process from a control room, asking them to walk to the line to trigger a clean or check a calibration status is a step backwards, even if the cCare system handles the work once they get there.

With the ProfiNET communication module fitted to the Protos II 4400 multiparameter transmitter, remote control of cCare becomes part of your normal control-system workflow. Cleaning and calibration programs are triggered from the DCS or SCADA, execution steps are visible in real time, and every action lands in the audit trail without anyone leaving the control room.

Where cCare already gets you

If you have not yet read the overview of what cCare does at the measuring point, the short version is this: the system combines a Unical 9000 or Uniclean 900 controller with a Ceramat or SensoGate retractable fitting and the Protos transmitter to automate the full sensor maintenance cycle, cleaning, rinsing, and one- or two-point calibration, on a schedule you define. Nobody needs to be there. The sensor is maintained in place, on time, every time, without manual intervention.

We covered the productivity and margin case for that in detail in our article on how cCare improves productivity, margin and efficiency. What that article does not focus on is what happens when you want to go a step further and bring that automation properly inside the control system, rather than running it on local timers and local panels.

The limitation of local-only operation

cCare on a local schedule is already a substantial improvement over manual calibration. But there are real situations where local-only operation creates friction. If your process runs in campaigns, you want to synchronise maintenance with the campaign boundaries, not have cCare fire mid-run because the clock says so. If an operator sees a measurement behaving oddly during a shift, they want to trigger an unscheduled clean from the control desk, not dispatch someone to the measuring point. And if a cCare run is in progress, the control room needs to know about it, rather than seeing a measurement go offline unexpectedly and raising a false alarm.

None of that is possible if the cCare system has no fieldbus connection to the plant network. The ProfiNET module is what provides it.

The ProfiNET communication module

The PN 4400-095 is a plug-in communications module for the Protos II 4400. Fitted to the transmitter, it makes the Protos a proper node on your ProfiNET network, visible to the PLC or DCS the same way any other field device would be. The Protos also supports Profibus if your plant runs that instead; the principle is identical.

Once the module is in place and the transmitter is integrated into the control system, remote control of cCare becomes available over the fieldbus. Cleaning programs and two-point calibration sequences can be initiated from the control system. As each program runs, the execution steps and status messages are visualised directly in the control system, so operators can see exactly where in the cycle the sensor is, without going anywhere near the line.

The customer handles PLC programming on their side; Knick supplies prepared function blocks to make that integration straightforward rather than asking your automation team to build the interface from scratch.

Operational gains from control-room integration

The practical difference this makes is most visible in plants that run tightly scheduled production. When the control-system operator can trigger a clean and calibration from the HMI at the end of a batch and confirm the sensor is back on a verified calibration before the next batch starts, the workflow is clean and documented. No radio call to a technician, no waiting, no uncertainty about whether maintenance was done.

It also changes how unscheduled maintenance is handled. If a pH trace starts to look suspect, an operator can initiate a cleaning cycle from the control room immediately. If the trace recovers after the clean, the sensor was fouled rather than drifting, and no further action is needed. If it does not recover, the issue is real and needs attention. Either way, the decision is made faster and with less wasted time than if someone had to walk to the point first.

Fewer field visits also means less exposure to difficult or hazardous environments, and it means your skilled technical staff are spending time on problems that actually need them, rather than routine maintenance rounds that the system can handle without them.

Audit trail coverage for remotely triggered runs

Every cCare cleaning and calibration run triggered over ProfiNET is captured in the Protos II 4400 audit trail, exactly as if it had been initiated locally. The Protos audit trail records who initiated the action, when, what the calibration results were, and any configuration changes made alongside it. Records are stamped with date, time and TAG, stored as plain-text UTF-8, and buffered locally on the transmitter against fieldbus interruptions so nothing is lost if the network drops momentarily.

For regulated environments, this is important. A remotely triggered calibration that leaves no record is not a compliant calibration. The ProfiNET integration does not create a gap in the audit trail; it extends the same record-keeping to remote operations that the transmitter already applies to local ones.

How it fits with the broader Protos platform

The ProfiNET module is one of the options that makes the Protos II 4400 modular platform genuinely useful for plant-wide integration, rather than just a sophisticated local transmitter. The same fieldbus connection that carries cCare remote-control commands also carries the calibration log data (CalLog), the audit records, and the live measurement values. You are not running separate bus connections for each function; the transmitter presents all of it through the one ProfiNET node.

That matters for how you specify the system. If remote cCare control is a requirement, the ProfiNET or Profibus module needs to be in the bill of materials from the start. It is not something that can easily be added as an afterthought once the transmitter is installed and the control-system integration is complete.

Working out whether this fits your installation

Remote cCare control over ProfiNET is the right answer for plants where the control room is the natural place to manage analytical loops, where scheduling maintenance around production events matters, and where the audit trail needs to cover remotely initiated actions. It is not necessary for every site: if your measuring points are accessible, your team is comfortable with local operation, and your process does not demand that level of integration, the additional cost and PLC programming effort may not be justified.

The way to work out where your installation sits is to look at how your operators currently interact with your analytical loops, what level of control-system integration your process demands, and whether the fieldbus infrastructure is already in place or would need to be added. At DP-Flow we scope cCare installations with the control-system integration factored in from the beginning, so the module selection and the PLC interface are specified correctly rather than retrofitted. That conversation is worth having before the transmitter is ordered, not after it is on the wall.