The Problem
Moving from a geometric design to a robot program involves more than exporting a path. Reachability, motion, tooling, controller behaviour, and operator feedback all affect whether that design can become a workable manufacturing process.
My Role
I founded Axis and led its industrial robotics development. The original framework brought parametric robot programming and simulation into Rhino and Grasshopper, keeping the connection between geometry and machine instructions visible to the designer.
The Work
The framework covered target modelling, kinematics, path planning, simulation, collision checking, and controller-specific code generation. My work also included online and offline programming, calibration, and operator interfaces across ABB, KUKA, and Universal Robots workflows.
The development extended beyond geometry into sensors, I/O, production cells, and recovery from faults. That required considering the machine and its operating environment together.
Development Direction
Later work evolved toward a portable .NET core, separate desktop adapters, and a browser interface backed by WebAssembly. This was an evolution of the platform; it should not be read as a claim that every next-generation capability was deployed in production.
What It Shows
Axis connects mathematical and computational methods to physical constraints. The central engineering task is to make those constraints understandable and actionable without obscuring how the system works.