【Control】⚠ 02. A Case Where FSM-Based Control Did Not Work

topics: [“control”, “FSM”, “PID”]


Introduction

We examined a control configuration in which
FSM (Finite State Machine)–based supervisory control
was added on top of a discrete-time PID control system.

To state the conclusion upfront:

Under the tested conditions, no clear benefit from FSM control was observed.

This article documents that result and provides brief analysis.


🔧 What Was Done

The evaluated configuration was as follows:

The FSM monitored the following indicators:


🎯 Expected Behavior

Initially, we expected the following:


📉 Actual Results

The observed results were:

At least under the tested setup:

We could not claim that “adding an FSM improved control performance.”


🤔 Discussion

Intersample Disturbances Are Outside the FSM’s Scope

Disturbances occurring between samples
are phenomena that alter system states in continuous time.

Since an FSM can only make decisions at sampling instants, it cannot:

This is not a design mistake, but a structural limitation of FSM-based control.


FSM Silence Is Not Necessarily a Failure

An FSM is not a device that must always react to every situation.

If:

then it is natural for the FSM to remain inactive.

From this perspective, the result can also be interpreted as:

The FSM correctly avoided unnecessary intervention.


🧾 Summary

FSMs and supervisory control are not universal solutions.
Identifying their effective scope is itself part of the design process.


📝 Closing Remarks

Although this is a “case where it did not work,”
the result is still valuable for future design decisions.

For those considering similar architectures,
this may serve as a reminder not to overestimate what FSM-based supervision can achieve.