← Latest papers
⚡ electrical engineering

The restrictive conditions to solve LTI Systems by Ordinary Differential Equations

This paper addresses the lack of clarity in standard engineering literature regarding the assumptions and limitations of solving linear time-invariant (LTI) systems via ordinary differential equations by formally defining the necessary input smoothness conditions and establishing a rigorous equivalence between ODEs and state space representations.

Original authors: Alexandre Sanfelici Bazanella, Tristão Garcia

Published 2026-04-10
📖 4 min read☕ Coffee break read

Original authors: Alexandre Sanfelici Bazanella, Tristão Garcia

Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer

Imagine you are trying to predict the future path of a car (the output) based on how you are pressing the gas pedal (the input). In the world of engineering, we usually use a set of rules called Ordinary Differential Equations (ODEs) to make these predictions.

For decades, textbooks have taught us how to solve these equations using a mathematical "magic trick" called the Laplace Transform. It's like a translator that turns a complex, moving puzzle into a simple algebra problem you can solve with a pencil and paper.

The Problem: The "Magic Trick" Breaks Down
The problem is that this magic trick has a very strict rule: Everything must be smooth.

Imagine driving a car. If you gently press the gas, the car speeds up smoothly. The math works perfectly. But what if you slam the gas pedal from "off" to "full" in a split second? Or what if the road suddenly changes from smooth asphalt to a bumpy dirt track? In math terms, this is a discontinuity. The input signal jumps instantly.

When this happens, the standard math formula breaks. It asks for a value at the exact moment of the jump (t=0t=0). But at that exact instant, the value doesn't exist! It's like asking, "How fast is the car going exactly when the light turns green?" Is it 0? Is it 60? The math gets confused, and different textbooks give different, conflicting answers. Some say use the value before the jump; others say use the value after. This leaves students and engineers scratching their heads.

The Solution: The "State Space" GPS
The authors of this paper suggest a better way: stop trying to force the car to follow the broken math rules and instead look at the car's internal state.

Think of the car not just as a point moving on a map, but as a system with internal parts: the engine RPM, the gear position, the fuel pressure. This is called a State Space Representation (SSR).

Here is the magic of this new approach:

  1. The Car is Continuous: Even if you slam the gas pedal (a discontinuous input), the car's internal parts (the engine, the gears) cannot change instantly. They have inertia. They move smoothly.
  2. The Bridge: The authors show that you can translate the confusing "slamming gas" ODE into a smooth "State Space" model. Because the internal state is always smooth, the math never breaks. You can solve the problem easily without worrying about "undefined" moments.

The "Before" and "After" Trick
Once you have this smooth internal model, the authors give us a simple rule to handle the messy jump at the start:

  • The "Previous" Condition (t=0t=0^-): Where the car was just before you slammed the gas.
  • The "First" Condition (t=0+t=0^+): Where the car is just after the gas hits, but before the car has had time to move significantly.

The paper proves a surprising fact: It doesn't matter which one you use, as long as you are consistent.

  • If you know where the car was before the jump, you can plug that into the formula.
  • If you know where the car is immediately after the jump, you can plug that in too.

The math works out the same either way, provided you don't mix them up (like using the "before" position with the "after" input).

The Big Picture
The authors are essentially saying: "Stop trying to solve the problem by staring at the confusing jump. Instead, look at the smooth, continuous machinery underneath it."

By switching from the old, rigid way of looking at equations to the State Space way, we can solve real-world problems (like switching circuits on and off, or sudden impacts) without getting stuck on mathematical technicalities. It turns a "broken" equation into a solvable one by realizing that while the input might jump, the system's memory (its state) flows smoothly through the chaos.

In a Nutshell:

  • Old Way: Try to calculate the speed of a car at the exact nanosecond it crashes into a wall. (Math breaks).
  • New Way: Look at the car's suspension and engine. They react smoothly even if the crash is sudden. Use that smooth reaction to predict the future.
  • Result: We can finally solve these problems clearly, without guessing which "magic number" to use at the moment of the jump.

Drowning in papers in your field?

Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.

Try Digest →