Several SIPOS actuators at one plant developed the same odd behavior: remote operation would sometimes get no response, with no alarm of any kind; and often a single power cycle — switch off, switch on — brought the actuator back to life. "Fixing it by turning the power off" sounds like a joke, but there are solid technical reasons behind it. The discussion distilled the phenomenon into three causes, each backed by plant experience.
The SIPOS manual states it clearly: once the valve position goes outside the 0–100% linear range, the actuator will not move. If the travel setting is slightly off, the actual position may drift beyond the linear range; from there, no remote command will do anything — and a power cycle (or hand-jacking the valve back into the linear range) effectively gives the valve a re-positioning kick, so the actuator works again after re-energizing. That is the most common reason why "one outage fixes it."
Hard-earned advice from peers: zero-point setting on a SIPOS is critical — a sloppy zero sooner or later leaves the range. When setting the end limits, it is safer not to follow the manual's default of "torque-close"; setting "travel-close" per field experience makes out-of-range events far less likely.
Inside a SIPOS, the main board connects to the power supply board through pin connectors; vibration can work them loose over time. Poor contact shows exactly as "intermittent, no alarm, temporarily OK after a reboot." The fix: re-seat and secure the main board, and check the pins for oxidation if necessary.
A complete case from one plant: the valve showed 0%, the remote command was 100%, nothing moved; local inspection found the command LED on the main board flashing continuously while the valve sat still; the mechanical crew ruled out valve sticking; after hand-jacking to 5%, the valve ran smoothly to 100% in remote. The final fix was replacing the power supply board — permanently. Broader experience agrees: SIPOS faults mostly live on the boards, and the power supply board (especially in hot locations) is the weak point.
1. For a silent no-response in remote, first look at the command LED on the main board: if the command arrived but nothing moves, the problem is inside the actuator; if not, chase the signal loop from the DCS;
2. Check whether the position is inside the linear range; hand-jack back into range and see whether it recovers — if it does, re-zero and re-set the travel;
3. Re-seat the main board / power board connectors;
4. If all else fails, replace the power supply board (suspect it first in hot locations);
5. Prevention: set zero and travel carefully with the "travel-close" principle, and re-tighten board connectors periodically.
"Power-cycling fixes it" is not magic: a reboot clears the out-of-range state and resets the boards — it masks the problem, it does not cure it. Treat the power cycle as first aid and the settings as the cure: work through zero, travel, connectors, and the power board, and the fault is gone for good.
