Skip to main content

2 posts tagged with "AI"

Artificial intelligence, including AI coding assistants, and how it changes the way control system software is developed and tested.

View All Tags

Code-First Simulation: Start With the Code, Add What You Need

· 9 min read
Hristo Hristoskov
Founder @ Control Edge AB

Developing control system software involves more than implementing algorithms. Engineers must understand how their software behaves, evaluate different configurations, and verify that changes satisfy the requirements. Yet investigating that behavior can require significant preparation, particularly when simulation depends on building separate models or accessing physical machines. As AI makes producing new implementations faster, the time needed to evaluate them becomes an increasingly important part of development.

Code-first simulation offers a practical starting point: execute the production code, provide the necessary inputs and parameters, and observe its behavior over time. Engineers can compare implementations, explore parameter ranges, and evaluate results against defined criteria. Recorded machine data or physical models can be introduced when the engineering question requires additional context, rather than making them prerequisites for every experiment.

The benefit is a shorter feedback loop between implementation and understanding. Engineers can investigate more alternatives earlier, identify unsuitable configurations before machine testing, and make better use of the time spent with physical equipment and experienced operators. The goal isn't to replace detailed simulation or real-world validation, but to start with the simplest experiment that provides useful engineering evidence.

When AI Writes the Code, What Becomes the Model?

· 7 min read
Hristo Hristoskov
Founder @ Control Edge AB

Picture a mobile machine during testing. An experienced operator makes a movement and notices something immediately. It feels a little too aggressive. Perhaps it overshoots slightly before settling, or the transition does not feel as smooth or predictable as expected. A control system engineer looks at the implementation.

Not long ago, trying another approach could require a significant amount of work: study the problem, modify the algorithm, review the change, compile it, deploy it, find another machine test slot, and ask the operator to reproduce the situation. Now the first part of that process can look quite different. The engineer may ask an AI coding assistant to propose a modification that reduces the overshoot, smooths the transition, or takes a different structural approach. A plausible alternative can appear quickly.

That implementation is not automatically correct. It still needs to be understood, reviewed, and verified. But producing the next candidate may no longer be the slowest part of the loop. AI assistance increasingly extends beyond implementation as well. Tools can help create tests, suggest edge cases, analyze failures, and work with test results. So the interesting change is not simply that we can write code faster. More of the engineering experiment can potentially become faster.