Instead of the usual approach — “assemble the hardware and then write some code”, the idea is to shift focus to a broader role: an engineer-architect.
That’s someone who, starting as a self-sufficient mechatronics mechanic, designs the whole system from the mechanics to the logic of its control at the hardware-software level. Not by endlessly scripting, but by working with algorithmic instructions, building directly on the original mechanical idea.
This feels like a more natural path: moving from mechanics to hardware-software control, based on the system’s functions and capabilities.
So the question is:
- Do you see value in such a role in today’s mechatronics?
- Could this kind of shift in thinking open up new ways of developing automation and robotics?
Top comments (0)