The DCS showed the valve at 100% open.
But the flow did not increase.
The pressure did not change.
From the control-room screen, the valve appeared to be doing exactly what it had been asked to do. From the process side, however, nothing seemed to be happening.
This is the kind of situation where one word on the screen can send troubleshooting in the wrong direction.
“OPEN” may mean that an open command was issued.
It may mean that a limit switch was activated.
It may mean that the positioner reported 100%.
Or it may simply be an internal status calculated by the PLC or DCS.
Those are not always the same as confirming that the valve physically opened and changed the process.
When the screen and the process tell different stories, I try to separate three things:
Command. Feedback. Actual movement.
That distinction usually gives the investigation a much clearer starting point.
First, Ask What the Screen Is Actually Showing
The first thing I want to know is what the displayed value represents.
A valve symbol may show “OPEN,” “100%,” or a green status indication, but that information may come from very different sources.
It could be:
- PID controller output
- Analog output command
- Valve-position feedback
- Open limit switch
- Solenoid output status
- PLC sequence status
- A simulated or forced signal
- A calculated HMI indication
The label may look obvious while its source is not.
For example, a controller output of 100% means the control system is requesting full opening. It does not prove that the actuator moved.
An energized digital output means the PLC turned on the output. It does not prove that the relay, solenoid, air circuit, actuator, and valve all responded.
Before following the field wiring, I first confirm the meaning and source of the indication.
A useful question is:
Is this screen showing what the system commanded, or what the valve actually did?
A Command Has a Long Way to Travel
Between the DCS command and the valve movement, several things must happen correctly.
For a pneumatic control valve, the path may include:
- DCS or PLC output
- Analog output card or digital output card
- Interposing relay or isolator
- Fuse and field wiring
- Solenoid valve or I/P converter
- Positioner
- Instrument-air supply
- Actuator
- Valve stem and internal trim
A healthy signal at the beginning of that chain does not confirm healthy operation at the end.
The command can disappear at a blown fuse.
The relay can energize without good contact continuity.
The solenoid coil can receive voltage but fail to shift mechanically.
The positioner can receive the signal but lack enough air pressure.
The actuator can move while the valve stem remains partially stuck.
The troubleshooting question is not simply, “Did the output turn on?”
It is:
How far did the command actually travel?
Feedback Can Also Be Misleading
Position feedback is more useful than command output, but I still do not treat it as absolute proof.
Feedback systems can fail too.
A positioner may report 100% because its calibration is incorrect.
A feedback linkage may be loose or disconnected.
A limit switch may change state before the valve reaches full travel.
The position sensor may follow the actuator while the valve stem or internal trim does not move as expected.
A signal may also remain forced in the PLC or DCS after maintenance or testing.
The displayed feedback can therefore be electrically correct while mechanically misleading.
When possible, I compare:
- Controller command
- Position feedback
- Mechanical position indicator
- Actual stem movement
- Process response
If all five agree, confidence increases.
If one disagrees, that difference becomes the clue.
The Process Is Another Feedback Signal
The control system may say the valve moved.
The field position indicator may also appear to move.
But the process should still provide evidence.
If a valve truly opened, what else should change?
Depending on the application, I may expect:
- Flow to increase
- Upstream pressure to decrease
- Downstream pressure to increase
- Tank level to begin changing
- Temperature to respond
- Pump load to change
- A differential pressure to move
- Sound or vibration around the line to change
The process response is not always immediate. Some systems have significant delay.
But if enough time has passed and none of the related variables move, I become cautious about accepting the indication at face value.
This has become one of my favorite field questions:
If the valve really moved, what other evidence should I be able to see?
It moves the investigation away from one screen and back toward the complete system.
A Simple Example
Imagine that the DCS commands a valve to 100%.
The position feedback also rises to 100%.
But flow remains unchanged.
There are several possible explanations.
The valve may not have physically moved despite the feedback.
The valve may have moved, but the line could be blocked.
An upstream manual valve may be closed.
The differential pressure across the valve may be too low.
The flow transmitter may be giving an incorrect value.
The valve trim may be damaged or disconnected.
The positioner linkage may have moved without full stem travel.
This is why replacing the positioner immediately may not be the best first action.
The issue may be in the valve.
Or the piping.
Or the process.
Or even the measurement being used to judge the result.
One symptom can belong to several systems.
What I Check in the Control Room
Before going to the field, I try to preserve the current condition.
I review:
- Valve command
- Position feedback
- Related flow, pressure, level, or temperature trends
- Interlock and permissive status
- Local/remote mode
- Manual/automatic mode
- Active overrides
- Forced or simulated signals
- Alarm and event history
- Recent logic or configuration changes
I also check whether the value changed suddenly after maintenance, a shutdown, or a control-system modification.
The objective is not to solve everything from the screen.
It is to avoid arriving in the field without understanding what the control system believes is happening.
What I Check in the Field
Once the equipment can be approached safely, I compare the screen with the physical condition.
Depending on the valve and process, that may include:
- Mechanical position indicator
- Stem or actuator movement
- Instrument-air pressure
- Filter-regulator condition
- Air leakage
- Solenoid operation
- Positioner display and alarms
- I/P converter output
- Feedback linkage
- Manual override position
- Upstream and downstream pressure
- Actual process response
I do not begin by adjusting the positioner.
I first try to observe the failure in its existing condition.
Moving, resetting, recalibrating, or manually stroking the valve too early can remove the evidence that explains the problem.
One Detail I Try Not to Miss: Local and Remote Mode
Some of the most confusing valve problems are not failures at all.
The valve or its control station may be in local mode.
A maintenance override may still be active.
The sequence may be waiting for a permissive.
An interlock may be blocking the output.
The DCS may display the requested command even though another layer of logic prevents that command from reaching the field.
These conditions are easy to overlook because the valve itself may be healthy.
The system is simply not allowing it to move.
Before opening junction boxes or replacing devices, I check the operating mode and logic path.
It is usually faster than discovering the same thing after an hour in the field.
My Short Field Checklist
When the DCS says a valve is open but the process disagrees, I work through this list:
- Confirm what the displayed indication actually represents
- Separate command signal from position feedback
- Check local/remote and manual/automatic status
- Review permissives, interlocks, overrides, and forced signals
- Confirm the PLC or DCS output actually changed
- Check the relay, fuse, isolator, and field signal
- Verify instrument-air pressure and tubing condition
- Check the solenoid, I/P converter, and positioner
- Compare feedback with actual stem movement
- Look for mechanical sticking or linkage problems
- Check whether the process produced the expected response
- Review upstream and downstream conditions
- Ask what changed recently
- Preserve trends and evidence before resetting anything
I do not expect every investigation to require every step.
The value of the checklist is that it prevents one screen indication from becoming the whole diagnosis.
What This Experience Keeps Reminding Me
I do not think the lesson is that DCS indications are unreliable.
Most of the time, they are extremely useful.
The lesson is that each indication has a specific meaning and a specific source.
A command proves that the controller requested something.
A feedback signal proves that a device reported something.
The process response tells us whether the action produced the expected result.
Those three pieces of evidence should support each other.
When they do not, that disagreement is not an inconvenience.
It is the beginning of the troubleshooting path.
Final Thought
The DCS can confirm that a signal was generated.
A positioner can report where it believes the valve is.
But the field still has the final vote.
When the screen says “OPEN” and the process says “nothing changed,” I try not to choose one side too quickly.
I compare the command.
I verify the feedback.
I look for actual movement.
Then I ask what the process should have done.
Because a valve indication is evidence from the control system.
The process response is evidence from the field.
And good troubleshooting begins when we notice that the two do not agree.