Skip to content

Main content

Two Threshold Controller Next State Tool

Evaluate one explicit heating-style hysteresis state: on at or below lower threshold, off at or above upper threshold, retain state between.

Loading tool…

Description

Calculate one two-threshold controller state under an explicit hysteresis rule.

Control terms depend on error sign, units, sample timing, saturation direction and state conventions. Hysteresis retains state between thresholds, while deadband mapping and output clamping describe different operations. A negative loop-sign product or small scalar derivative does not establish closed-loop stability or safe operation.

Calculate one two-threshold controller state under an explicit hysteresis rule.

When to use this tool

Use Two Threshold Controller Next State when you already have previousOn, measuredValue, lowerThreshold, upperThreshold and need to calculate one two-threshold controller state under an explicit hysteresis rule.

How to use the tool and how it works

  1. Enter previousOn, measuredValue, lowerThreshold, upperThreshold. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read nextOn. Inspect nextOn before interpreting the associated values.

Require upperThreshold>lowerThreshold; value<=lower sets on=true, value>=upper sets false, and values strictly between preserve previousOn.1

Input fieldMeaning and unitsAccepted input
previousOnPrevious OnRequired. Boolean.
measuredValueMeasured ValueRequired. Finite number.
lowerThresholdLower ThresholdRequired. Finite number.
upperThresholdUpper ThresholdRequired. Finite number.
Output fieldInterpretationReturned shape
nextOnAt/below lower threshold true; at/above upper false; strictly between retains previousOn.Required. Boolean.
json
{
  "input": {
    "previousOn": false,
    "measuredValue": 2,
    "lowerThreshold": 3,
    "upperThreshold": 7
  },
  "output": {
    "nextOn": true
  }
}

Limitations and assumptions

  • Endpoint policies are inclusive as stated. No plant, timing, actuator, stability, alarm or safe operating range is modeled or selected.
  • Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
  • Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Numeric signed-zero results are exported as zero.

Alternative or Complementary methods

Use a complete plant, controller, actuator and timing model with verified operating constraints for control decisions. Check interactions among saturation, integrator state, gains and delays; individual algebraic terms do not tune a controller or validate system stability or safety.

References

  1. Calculation and input contract: cybernetics/two-threshold-controller-next-state — tool.io

Similar or alternative tools