A setpoint is the single most important number in any control loop: it is the value the operator wants the process to hold. Every regulating device on a facility - a pressure controller, a level controller, a temperature loop - is quietly working to make one measured value equal one setpoint. This guide explains what a setpoint is, how it relates to the measured process variable, and how setpoints are managed and changed remotely in SCADA.
Setpoint in one line: A setpoint (SP) is the target value a control loop is configured to maintain - such as 45 psi or 60% tank level - which the controller continuously compares against the actual measured process variable and adjusts an output to match.
Three quantities define any regulating loop. The setpoint (SP) is the desired value. The process variable (PV) is the actual measured value from a transmitter - the real pressure, level, flow, or temperature right now. The controller output (CV or MV) is the correction the controller sends to a valve, pump, or drive to close the gap. The difference between SP and PV is the error, and the controller's entire job is to drive that error toward zero.
For example, a separator pressure loop might have a setpoint of 45 psi. If the transmitter reads 48 psi, the error is +3 psi, so the controller opens the gas control valve further to bleed pressure down until PV returns to SP. Change the setpoint to 40 psi and the loop simply chases the new target - the mechanism does not change, only the goal.
A setpoint can be entered locally at the controller or HMI, or it can be a remote setpoint written from a supervisory system - a SCADA host, a DCS, or an optimization routine. In oil and gas, remote setpoints let a control room adjust a compressor recycle pressure or a wellhead choke target across many remote sites without dispatching a technician.
Setpoints can also be generated automatically by another loop. In cascade control, the output of an outer (primary) loop becomes the setpoint of an inner (secondary) loop. That is why setpoints are not always fixed numbers typed by a human - they can move continuously as an upstream loop calculates what the downstream loop should target.
The setpoint is the value you want; the process variable is the value you actually have, measured by a transmitter. The controller compares the two and adjusts its output to make the process variable equal the setpoint.
A remote setpoint is a target value written to a controller from a higher-level system - a SCADA host, DCS, or another control loop - rather than typed in locally. It lets operators retune loops at distributed sites from a central control room.
If the controller exposes the setpoint as a writable register or point over a supported protocol such as Modbus or DNP3, a cloud SCADA that supports remote control can read the current setpoint and, with the right permissions, write a new one. Merobix reads and, where enabled, writes such points over Modbus and DNP3.
This page references the protocol specifications published by the organizations below. Editions, product capabilities, and documentation change over time - confirm current requirements and specifications directly with the source.
Last reviewed: July 27, 2026. Merobix is not affiliated with, endorsed by, or sponsored by these organizations; their names are used only to identify the standards and products discussed.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.