Every big chapter ends somewhere. This is where Dallas ends for me with miles of overhead conveyor, a burned motor, and a welding hood I hadn't picked up since high school. What two years in one place actually made me.

Every machine that comes into a production line has its own PLC, its own logic, and its own idea of how the world should work. As the system integrator, that's your problem to solve. In this episode, we break down the reality of integrating third-party machines into a line control system. Why fillers are the hardest machines to work with, why Ethernet doesn't actually mean access, and what it took to stop showing up to projects blind. From a bottle jam nobody could see to vendors who just said no, this is the dull work that determines whether a line actually runs.

The filler panel caught fire. It wasn't dramatic,just enough to trip the alarm and send everyone outside to stand in 110 degree Dallas heat. That moment pretty much sums up this entire project. This episode is about bad equipment, impossible expectations, and what you learn when software can't save you.

An experimental filler pushing 210 cartons per minute created one unexpected challenge: merging three lanes of cartons into a single line without collisions.

What looked like a simple control problem became a deep dive into conveyor physics, compounding error, and the limits of mathematical modeling.

In this episode, I tell the story of experimental filling line, the weeks spent chasing a perfect solution, and the lesson every controls engineer eventually learns: real production systems never behave exactly like the model.

Not every successful project looks good while it’s happening.

In this episode, I tell the story of a large gantry-based X-ray inspection system that started in frustration and ended in success. The original design never really existed, the space was brutally constrained, and normal installation methods were off the table from day one.

I talk through why we started from scratch, how a distributed motion system unlocked the design, and how we ultimately assembled the machine using modular construction, furniture dollies, ratchet straps, and a willingness to accept that there were no perfect options.

This is a behind-the-scenes look at the kind of engineering that happens when reality refuses to cooperate.

Music from Pixabay Monument_Music

Early career travel and responsibility often arrive together in controls engineering. In this episode, I talk about what “paying your dues” actually looked like for me, living on site, owning multiple lines too early, and learning the job under constant pressure. This is a story about growth, pride, and the hidden costs of becoming reliable.

Music from Pixabay Monument_Music

Early in my career, I was handed my first real production line and told not to worry, the company had built it before. What I wasn’t given was the code, the standards, or a real starting point.

In this episode, I talk through what happens when “experience” exists only as stories, how abstraction becomes a survival mechanism, and how early habits can quietly turn into long term technical debt. From programming a blank controller in the field to learning hard lessons during first production, this episode is about momentum, responsibility, and figuring things out before you know what good actually looks like.

If you’ve ever been told “we’ve done this before” and then left to invent the structure yourself, this one will feel familiar.

Music from Pixabay Monument_Music

In this first episode of From the Bucket, I tell the story of my very first controls project.

It was a barcode verification system that worked exactly the way it was designed. We deployed it, customers were happy, and nothing broke.

Years later, after feature creep, expansion, and a lot of well-intentioned decisions, it became a system that only a few people could support. And one of those people was me.

This episode isn’t about a dramatic failure or a clean fix. It’s about how control systems really fail. Slowly, quietly, and over time. It’s about abstraction, maintainability, and what happens when early design decisions turn into legacy systems that you have to live with.

If you’ve ever opened up a program that technically works but nobody really understands anymore, this one will probably feel familiar.

Music from Pixabay Monument_Music