Controls
Software that drives hardware — motors, hydraulics, actuators.
- Motor, actuator and hydraulic control
- Sensors, feedback and closed-loop behaviour
- Operator interfaces and machine state
- Embedded software on constrained hardware
A good deal of my work has been software that had to move something physical. That’s a different job from software that moves data, and it’s worth saying so plainly, because the difference is where projects get expensive.
The code has to be right about the world
Software driving a motor or a hydraulic valve doesn’t get to be merely self-consistent. It has to be correct about a physical system that is slower than it is, noisier than it is, and wholly indifferent to its assumptions.
A sensor reports something impossible. A command arrives while the previous motion is still settling. An operator holds two inputs at once because nothing said not to. Mass keeps travelling after the signal stops. None of that appears in a unit test, and all of it decides whether the machine is trustworthy.
So the interesting questions are rarely about the language. They’re about what the system does when an input goes missing, what state it fails to, and whether an operator can tell what the machine is about to do before it does it.
The boundary is nobody’s job
On most projects the mechanical side and the software side are different people, and the seam between them belongs to neither. That seam is where the schedule goes.
I work on both sides of it. Having designed and built mechanical parts myself, I’m not guessing at what the hardware will tolerate, and I’d rather go and put a meter on something than file a ticket asking someone else to. That crossover is what I’ve been able to capitalise on repeatedly: being useful across the gap, rather than stopping at the edge of one discipline.
What this looks like in practice
- Driving motors, actuators and hydraulics to defined, repeatable behaviour.
- Reading sensors and closing the loop — position, pressure, temperature, flow.
- Operator interfaces: controls, displays and machine state a person can read at a glance.
- Embedded software where the hardware is constrained and the timing matters.
- Commissioning — being there when it first runs, and fixing what the bench didn’t reveal.
Most useful where a physical system and its software are being developed together, or where something mechanical already exists and has to be made to behave.
Sound like what you need?
Tell me about the problem and I'll tell you honestly whether I can help.