Send us Fan Mail What if mechanical engineers could automate motors, pneumatic actuators, and testing equipment without needing to write complex code or rely on a dedicated controls engineer? In this episode of Being An Engineer, host Aaron Moncur welcomes two members of the Pipeline Design & Engineering team: Ruben Inzunza, Director of Automation, and Mark Blakey, Senior Mechanical Engineer. Together, they take listeners behind the scenes of Easy Motion, an automation platform developed to simplify motion control and make automated testing more accessible to engineers. The journey wasn't without setbacks. Early versions of Easy Motion encountered hardware limitations, programming challenges, and integration issues that nearly brought development to a halt. Mark and Ruben share how they revisited previous engineering work, combined existing technologies, and collaborated across disciplines to overcome these obstacles. Their experience highlights the importance of rapid prototyping, learning from failure, and creating an environment where engineers feel comfortable experimenting and asking for help. The conversation also explores how Easy Motion is being used in real-world engineering applications, from automated cycle testing to production equipment. One particularly impressive example involves a customer testing solar panel tracking systems. By implementing Easy Motion, the customer reduced a testing process from approximately 10 months to just 2 months - an 80% reduction in testing time. Beyond the technology, this episode offers valuable lessons about engineering teamwork, effective communication, and knowing when to simplify a problem rather than overcomplicate a solution. Whether you're a mechanical engineer exploring automation, a controls engineer looking to streamline development, or an engineering leader trying to improve your team's efficiency, this conversation offers practical insights into building better products and accelerating innovation. Learn more about Pipeline Design & Engineering and explore Easy Motion at https://teampipeline.us/ LINKS: Mark Blakey LinkedIn: https://www.linkedin.com/in/markrblakey/ Ruben Inzunza LinkedIn: https://www.linkedin.com/in/ruben-inzunza-852978110/ Website: https://teampipeline.us/ez-motion/ Subscribe to the show to get notified so you don't miss new episodes every Friday. The Being An Engineer podcast is brought to you by Pipeline Design & Engineering. Pipeline partners with medical & other device engineering teams who need turnkey equipment like cycle test machines, custom test fixtures, automation equipment, assembly jigs, inspection stations and more. You can find us at www.teampipeline.us Watch the show on YouTube: www.youtube.com/@TeamPipelineus
Audio and video play straight from the show's own hosting. PodSubs stores and serves no media.
Transcript
From the show. Tap a time to play from there.
MarkI know there was a, a few different solutions that were getting floated around. What are we gonna do to, uh, I don't know, solve a problem as quickly as possible? So it was mainly what past knowledge can we rely upon is gonna get us out of this? 'Cause we, we don't have a, a time to try a new solution.
AaronHello and welcome to the Being an Engineer podcast. I have two special guests with us today, Ruben Inzunza and Mark Blakey from the team here at Pipeline Design and Engineering. And I thought it would be fun to talk a little bit about a product that we developed a few years back. It's actually been kind of a labor of love for quite a few years, but a few years ago, we finally finished an iteration that works really well, and it's something that we're selling right now. And I think that there are some interesting lessons learned along the way, and it would just be interesting for you all out there in the audience to hear about how we here at Pipeline did a project and developed a product.
AaronMaybe there are some takeaways that you all can learn from and implement into your work. So, uh, we're gonna just dive in here. Um, a co-- in the way of introduction, Ruben is our director of automation, and Mark is one of our senior mechanical engineers here at Pipeline, and they were more or less the power team responsible for at least the current iteration of a product that we call Easy Motion. So Mark, maybe you can summarize for us real quickly what, what is Easy Motion and what was the problem that we were trying to solve when we set out on this journey?
MarkYeah. Well, thanks for having me, Aaron. Uh, Easy Motion is our, uh, attempt to make engineering or automation, uh, accessible to all engineers, uh, especially mechanical engineers like myself that do not have a background in programming or PLCs or, uh, anything of the electrical sort, so that we could just come up with a design and test it and actually automate it to see how it actually works in the real world
AaronYeah, Mark, um, uh, you hit the nail on the head. For engineers that don't have that programming br- background, like such as myself for sure, anything electrical is definitely over my head, and software is the same thing. I, I, I don't do any of it. I don't have any skill set at all in that area. Mechanical design, I'm pretty good, but outside of that, uh, not so much. So we wanted-- and this was kind of a selfish internal desire, right? We wanted to build something that would allow our team to move faster when we had a new automation project come in, and we needed to use a motor to move this actuator and use a pneumatic actuator to do that, and maybe there was a, a couple of, sensors that we had, a proximity switch, something like that.
AaronWe wanted to use that for feedback. How do we string all these t-things together and create some motion really, really quickly? And I remember years ago when we did our first motion project as a company, and this was I think before either one of you got hired, but back in,
Ruben InzunzaIk zou ja
Aaron2018 maybe, so like eight years ago, nine years ago, something like that. remember being shocked at how convoluted it was just to make a motor move. I mean, turning a motor on and off, not that hard, but, like, to do it in any sophisticated way, right, with, with some intention behind it. Move at this speed for this amount of time, then stop. Pause for this amount of time, then reverse the rotational direction and, you know, move at that speed. Very difficult to do without that specialized skill set.
Aaronso anyway, we, we started off down this journey, and actually we had a couple of teams working on this. Originally, there was a, a different team, Jason and, and then kind of, uh, Ryan, who was working on this, and they took it to a, a certain point, and there were a couple of bottlenecks that, that we couldn't quite get past, and we, it-- the project kind of stalled internally. Um, I'm trying to think about what all we, we tried before and, uh, what, what we learned from that previous iteration that we were able to leverage and, and move on to the, like, the current version of it.
AaronUm, there's kind of a story that goes along with that, but Mark and Reuben, do you guys remember looking at the, the last version of Easy Motion that, that sort of worked but not quite, and, um, what, like, what we were able to leverage from that previous system that we now use in the current system?
Ruben InzunzaYeah, it was sort of a, call it two previous efforts that the, the sum of the parts, uh, was, um, I think a greater net benefit, uh, on the first sort of call it dedicated effort for our internal team to develop a system like this. Um, that team really laid the, the foundation on the programming side of, hey, the users should interact with the system like this and And that, I think that's what really got us excited when we-- when that team was working on it, right?
Ruben InzunzaUm, like, oh, yeah, no, I, I can make a thing go on and off, and I can wait for the sensor to, to be high. Um, and then when we started-- tried to scale that a little bit further to, um, you know, that team tackled sort of the pneumatics aspect of it first, and that seemed to have worked well. Uh, but trying to tackle some of the, the motor which is, call it, a lot more hardware dependent, um, that introduced some, some complications. But the, uh, on the Blockly side, I think that that really laid the foundation of this is the look and feel of the thing.
Ruben InzunzaUm, and then almost along the lines of the, the, the selfish internal reason, uh, on the back end of actually controlling our, our hardware, I think, uh, as far as I can remember, other than like the LabJack that-- which is more kinda like physics-y lab type thing, there wasn't-- We hadn't found a great solution for connecting sort of your, your computer when you wanna record data or trigger some things with like a simple script to real-world hardware that uses discrete IO and analog feedback, and then obviously the motor stuff.
Ruben InzunzaUm, but we had a, a, a custom application to do a, a test fixture where, uh, that sort of laid some of the groundwork in specifying the hardware that we eventually ended up using. Um, I think our, our customer enjoyed using that set of hardware. They asked for, uh, basically a, a repeat of the system, and that's where Mark and I really got to work together on that. And even in building that, right, it was a, a precursor to y- to Easy Motion. We didn't even have that in mind at the moment, but it was like, "Hey, this is-- Th-this piece of hardware is really easy to talk to with the software that we're developing for it." Um, you know, it's super compact, it's nice and dense in terms of its IO.
Ruben InzunzaUm, you know, this-- We should keep to the, uh, using this in, you know, in the back of our mind. I think at, at the time, Mark was working on a, uh, a separate project where he had to do all kinds of things to, to handshake with, you know, an Arduino, a Mecademic robot, uh, his PC just to turn a, a glue dispenser on and off and move a robot from A to B. Um, a robot's a little more complicated, but I remember going over to his test bench and it was like, "Dude, it's a, it's a, a bit of a rat's nest here." Um, and he-- And, uh, you're doing such simple things in terms of instructions.
Ruben InzunzaIt's, you know, I'm sure we have our clip somewhere on our website that, you know, we were able to figure it out, but it was just kinda, kinda like to your reaction, Aaron. It was just so complicated to, to do what seemed like simple actions.
AaronYeah, and we should back up just a moment here. For those who maybe aren't very familiar with automation or the different components that go into it, they might be hearing words like IO. What, what the heck does that even mean? So let's start with just, like, a basic fundamental description of some of the, the, the, the core hardware or components that are needed to control motion. So you've got like, you know, motors and pneumatic actuators. Those are pretty common. I think most people understand what those are. But beyond the motor and the, like, the pneumatic actuator, what are some of the core pieces of hardware that have to be strung together and communicate with each other in order to create, uh, even moderately sophisticated motion?
Ruben InzunzaUm, yeah. So I mean, even a mo- you can tell a motor to go, like a stepper motor. It's for the most part on its own dumb, right? You need to, you need to basically check the motors work. Did the motor actually get to where it told you it got to? So that's where you know, hey, a motor with an encoder feedback. So that's another sort of, uh, piece of the pie there. Um, even on pneumatic actuators, which is con- for the most part, consider them on/off or extended retracted. Um, you know, you have a valve, a system that goes with that, with, uh, if it's a dual acting cylinder, then you have, you know, two ports.
Ruben InzunzaUm, but then you also have to check its work. Okay, now I, now I need a sensor on each end to know that, hey, I got to position A, then I got to position B, um, or I didn't get there and something went wrong along the way, and you had to be able to react accordingly, right? To make robust actions. Uh, you can make anything works once or twice, but, uh, if you wanna do higher numbers of cycles, you're gonna run into those, those funky situations. And if it can happen, it will happen if you do it enough times. Uh, so even those… You, you're not… Yeah.
Ruben InzunzaGood
AaronWe've got, um, a, a controller, right? Which is often a, a PLC, programmable logic controller, which is basically a little, like, kind of a industrial computer, kind of. Um, we've got, uh, like, terminal blocks, right, where you make all the electrical connections. There's a power supply. Uh, I/O we talked a little bit about. That stands for inputs and outputs, which are, are, basically you can plug sensors in. There's d-digital sensors, which are just on or off. There's analog sensors, which are more like a, a, a load cell where it's discrete values, right?
AaronIt could be 1.2 pounds or 17.3 pounds. It's not just on, uh, on or off. So you've got all these different components that have to be connected to each other. First of all, you need to have the knowledge to identify which parts are needed in the system, and then you have to go buy them all, and then you have to string them all together. there's some electrical work there. There's general mechanical assembly work involved there. And then even once you have everything together, you have to program it, and if you don't know how to program, then you've spent all this time and money, and now you have to spend quite a bit more time learning at least some basic code to, to create your motion.
AaronSo there are all these steps that, you know, for someone who hasn't done this before, it might, might take them thirty or forty hours just to get to the point where now they can start, uh, writing some code and, and m-m-move… building a simple motion sequence, right? It can take a long time. So we thought, let's simplify all of that and just build something that's pre-integrated so all these parts are already in the, uh, a box, right, that you can just buy off the shelf. You don't have to figure out which parts to buy and which parts to assemble and what parts communicate with what other parts.
AaronIt's all just done, right? It's pre-integrated. And then once it comes to the, the programming aspect, do we make it super, super easy such that anyone can do it? And I think we succeeded there because I taught my, at the time she was nine years old, nine-year-old daughter how to program in Easy Motion, and she picked it up in, like, half an hour and was off to the races creating her own industrial, um, motion with this thing. And I thought, let's see, I didn't plan to do this, but uh, I'm gonna share my screen real quick here the fly And share what the interface looks like.
AaronSo the programming interface is s- it's blocks. It's a visual drag-and-drop logic block. So for those of you who are watching this right now, you can see that we just have these different blocks here. So if I wanted to, like, extend an air cylinder, I just drag this block that says cylinder extend, and I can change from which cylinder, cylinder one or two or three or four, and do I want it to extend or retract? And then I can Control+C, Control+V, put another one over there. And so automatically, uh, you know, after, like, ten seconds, literally here, I have a motion sequence that's gonna, uh, retract a cylinder, and then-- I guess I should change that one to extend a cylinder.
AaronAnd it took almost no time at all. So you can see how, how, how simple it is to program with Easy Motion. So, um, that was the problem that we're trying to solve, right? Because, if, if you've worked in controls or automation before, you probably recognize that it can be costly and time-consuming to do the programming part and the integration part, for that matter. Um, so that was the problem that we were trying to solve, and I, this pretty keenly.
AaronI don't know how well the two of you remember this, but do you remember the situation, the project that we had at Pipeline, without mentioning any customer names, of course, that, uh, like prompted us to restart the Easy Motion project?
Ruben InzunzaI think it was a classic salesman, uh, Aaron.
AaronMay-
Ruben InzunzaPromised a thing
Aarona little
Ruben Inzunzawithout running it by the engineers that had to do the thing. Um, but basically, uh, I think, uh, in the-- It was always in the back of our minds of like, "Hey, there's, there's something there. How do we, how do we pick this up?" Uh, again, is it just using some slightly different hardware that's easier to, to connect on the back end, uh, with the other physical hardware, the, the motors, the terminal blocks, so on and so forth. Um, and man, I remember we, we tried and it seemed like it was promising on paper and that-- But then in execution, we ran into all sorts of problems.
Ruben InzunzaI think we built the entire thing out and went to go test it on the customer's floor, and it was like,"Hey, man, this thing, you know, you need to program this by connecting to it over Wi-Fi," I think is what it was, what that hardware limitation was. And like, our customer's like, "Oh, no, we can't connect any of this over Wi-Fi." It's like, "Oh, shoot, that's right." But like we, we-- I don't think that went into consideration, um, or some of the hardware had like changed and, and the programming, it was just sort of a, a mess of you don't know what you don't know till you're doing the thing.
Ruben InzunzaUm, and I remember it was like, "Oh, man," I think Mark is the one that suggested like, "Hey, what about this other piece of hardware that we've already, uh, interacted with? We know sort of how it works and, and there's a potential path forward." And I think, uh, Mark was given the, the go-ahead to kinda come in and, and, and, and sorta save the day on that particular application of, of coming up with something that, that would satisfy the customer need, um, and sort of be this, this first stepping stone as to what Easy Motion is today.
AaronRight, because we didn't, it, we were looking at a completely different platform, right? We had
Ruben InzunzaMm-hmm
AaronMotion to a certain point, and it, it, like I said before, it mostly worked, but not quite completely. our team always had this in the back of our minds, like, "How could we create something that's easy?" And we found a different set of hardware that already existed. A different company had, had built out kind of an ecosystem of this hardware, which was supposedly plug and play, easy to program. And we thought, "Oh, maybe we could just leverage what someone else has already put together, do a little, uh, uh, and, and, uh, create, you know, what, a, a different embodiment of what we pictured Easy Motion would be." And on paper, like you said, it all worked, right?
AaronIt, or it seemed like it was gonna work. But then once we actually started putting it together, oh, my gosh, there were all these bugs, and the documentation was awful. I think it was a, a Chinese company. Not- nothing against Chinese companies, but we, we couldn't get ahold of anyone for support. There, there kind of, there effectively was no support. And like you said, Reuben, I, I had kinda sold this, this product to a customer of ours thinking that… 'Cause we had done some of the legwork already internally. And i- internally, like, early results were like, "Yeah, this works. We can do it." So great, I, I sold that project to a customer, and then we, like, really got into the details, and it just did not work the way we thought it was gonna work.
AaronJust didn't work at all, really. I remember being super nervous about this, right? Anxiety and thinking, "Oh, I just, I've promised this to one of our best customers, and now it's not working. How are we gonna deliver on this?" Fortunately, they, they did give us a bit of time to figure it out, um, although I never went back to them and it was like, "Hey, it's, it's not working. Sorry, I, I don't know what to do." It wasn't like that. They just, they gave us, you know, uh, a generous amount of time. And internally, I remember sending a message out saying, "Hey, team, uh, I n- need some help brainstorming ideas here.
AaronWhat, what else could we do?" And I think, Reuben, you had come up with, like, an Excel version with maybe some, some drop-downs, and you could, like, select, you know, move motor or something and build kind of a sequence like that. And then Mark came in, and he was like, what about Easy Motion?" And I remember thinking, "Uh, I've spent a lot of money already on Easy Motion, and we never quite got it to, like, work perfectly. I, I, I don't think that's a great idea, Mark." But to Mark's credit, he, he pushed for it and became the champion and was like, "I think I know how to make it work, and I think I can prove it pretty quickly.
AaronLike, give me a day to try this, and let's see what happens." So I said, "Okay, great. I mean, a day, sure. No problem." And then Mark, do you remember what happened at that point and how you proved it, it, it could work?
MarkYeah, I know there was a, a few different solutions that were getting floated around. What are we gonna do to, uh, I don't know, solve a problem as quickly as possible? So it was mainly what past knowledge can we rely upon is gonna get us out of this? 'Cause we, we don't have a, a time to try a new solution. So it was … I don't know how we happened to have the hardware there do it. Maybe it was just on
Ruben InzunzaNo, I think…
Markcontroller
Ruben InzunzaNo, I think you order it off of eBay once you're like, "Hey, why don't we try this thing we did for the, the one testing project?" And you're like, "All right, sure." So, you know, we,
MarkI
Ruben Inzunzawe, were like hardware limited. Yeah. Like a decommissioned machine and like, okay, I guess that works, and yeah
MarkYeah, and then it was kind of a, we've already used some of this hardware over here on this project, and we know that it works and how to interface it. Easy Motion has already kind of created this other user interface for actually programming it. How can we combine the two things together? and then it was, yeah, a lot of just Frankensteining at first of, okay, let's just mash these together to prove it out, and then it, okay, it works. Now let's refine it and actually integrate it, uh, so it works smoother. Um, yeah
AaronGo ahead, sorry
MarkI was gonna say, I don't know what the, what the customer was expecting,'cause yeah, we did have the one solution that went there, and then yeah, there was the ethernet or wifi issues, and it's like, "Okay, let's take it back and rework it." And then we kind of basically delivered something totally different. But they were like, "Whoa, this is, like, a lot smoother and cleaner." I mean, it's not like, yeah, we gave them a bunch of, a pile of garbage. It was definitely an upgrade, uh, on that end of it
AaronYeah. And originally you, you wanted to just prove that you could make the pneumatics work, and the pneumatics had worked pretty well in the previous system. My recollection, let me know if you re- remember this differently, but so you did that pretty quickly, and then you came back and said, "I think I can make motors work as, as well." And that was where I was like, "Hold on. I remember going through
Ruben InzunzaThis story
Aaronfirst iteration, and yeah, n- we got pneumatics working, and that worked pretty well, but it was motors that really tripped us up, and we couldn't quite get that to work." And no, we spent all this time on it. I, I don't, I don't know what else you could do, Mark. We had smart people working on this, and they spent, you know, long time trying to make this work, and it, and it never quite did. And you said, "Give me a day or two just to, to try this. I, I have some ideas. I think I know how to make it work." honestly, I was like, "This is not gonna work, but hey, a, a day or two, sure. If you wanna take a day or two, let's, let's do it." And lo and behold, a day or two later, you came back, and you had the basic functionality of the Easy Motor System working, and I was blown away.
AaronI was so impressed that you had been able to not only make it work but make it work in, like, a day or two. It was fast that you, you turned that around. And I think that you did, like you said, you leveraged some, um, that we had developed previously, right, as part of another build or something
MarkYeah, I mean, I definitely wasn't working on that in a vacuum. Ruben was there helping me figure out the, know, the actual motor specification side of it. And then I was, I guess, working on the, software control user interface side of it based on, the knowledge he was pulling out of the motor controller of like, "Okay, we need to do these commands and this sequence to get things to do X, Y, and Z." And then we kinda just put it together and, yeah, I believe that controller was definitely a eBay purchase from a decommissioned CNC machine or something.
MarkSo I was like, "Oh, well, we've gotta change all these parameters 'cause we don't know what hardware we actually have." So there, there was a little bit of trial and error in that as well, 'cause we just kind of bought a black box and hooked some stuff up to it and hoped it worked.
AaronYeah. And, and we've gone on to build entire systems off of Easy Motion. Mark, you did one, a pretty sophisticated design. This was a machine that, um, I don't know if we can say. Maybe to be safe, I won't say exactly what it does, but uh, it
MarkOr processing paper
Aaronthis
Ruben InzunzaWould scratch foil off of paper is probably the most generic way you can say it
Aaronfoil off paper. Yeah. But it would do that. It would pull a piece of paper. It would singulate a piece of paper at a time, pull it through, uh, remove a, a foil substance, and then there was a light that came on. I think some pictures got taken, and then it would send it out to one of a few different collection bins. And all of that was done with Easy Motion. Like, the final production unit ran on Easy Motion, which, um, I thought was super impressive because it's primarily useful as an R&D tool.
AaronIt's something that allows you to get in and create a motion sequence and test it really, really quickly, and then update that sequence and test it, and then update it again, right, to iterate through really quickly. Um, it certainly can be used for production, but, but the primary use that we've had is kind of in that R&D developmental stage, where you're just ripping through iterations and trials really quickly to see what works and what doesn't.
MarkYeah, I mean, it's a, a huge time saver from the standpoint of you're not building, uh, a control panel from scratch with unknown components, and then you're not building the, the base level logic for controlling that. So you can immediately go from,"Okay, my last bolt is in," to,"Let's test if it's gonna work." And like you just already had programmed in the demo of extend the cylinder, retract the cylinder. Okay, cool, we got motion. doing what we want it to do? And you're-- you immediately get that feedback result and not, "Okay, now let's go and sit down," or you're parallel pathing one person doing programming, one person doing the mechanical, and then you hope you kinda converge at the same time.
MarkIt's-- takes the, "Well, I gotta now sit down and program this for a week," to, okay, within an hour kinda have a system running and know what mechanical changes may need to be changed, um, what worked, what didn't work, uh, how can you change the sequence up to, you know, start optimizing things. it, yeah, it just immediately you start getting the results of automated, especially in the test realm, of automated process control. So it's, you're getting the same process repeatedly over and over, so you don't have the variations of, human interaction, um, whatever other variables you might get in there.
MarkSo it's like, okay, yeah, this works once. Now let's do it 50 times and, and see what happens, and you get the same results or what do you need to change? Um, you quickly iterate through those.
AaronI think one of the biggest inefficiencies in, uh, engineering development work is when you have to transfer the knowledge in your brain to someone else's brain. Like, this especially comes into play when there are different disciplines, maybe a mechanical person and a controls person, for the example that we're talking about right now. And traditionally, the mechanical engineer is not the same person as the controls engineer. So the mechanical person has to tell the controls person, "I want the machine to move in this way. I want it to move to this position, and then pause, and then this gets rotated," and right, this sequence of events.
AaronAnd that takes a lot of time for one person to take all that knowledge from his or her brain and implant it in another person's brain, who is not gonna understand that logic, that information perfectly the first time. It's gonna take a while and a bunch of loops of iteration before they finally kind of converge. So the fact that one person create the motion himself, the, basically the, the mechanical guy or girl can create the motion him or herself without having to transfer that knowledge to someone else is a huge time-saver.
AaronAt least that's what we've found.
Ruben InzunzaI think, uh, call it an unspoken benefit of allowing, you know, say Mark be the, the mechanical designer and the, the programmer on like the R&D side of things, um, is it lets your controls person, you know, it lets you use the Ferrari on the racetrack, the, the dedicated controls person to keep working. You know, maybe it's a big picture thing. Maybe Mark just needs to know,"Hey, I have this live hinge that I need to know if it's gonna fail in the rated cycles." Okay, cool.
Ruben InzunzaI can't move on in my design until I answer that question because I'm gonna commit whatever to that design. He can go out there into the lab, you know, order some parts maybe from McMaster-Carr or whatever, and in a day or so be, be testing the thing that he needs the answer to. Um, he didn't have to rely on the controls engineer to go rack, grab the, the, the test bench PLC, hook it up, make a custom program for the thing. You know, Mark's up and running and, and the other person can continue doing what they're doing when we're designing these, these larger systems.
Ruben InzunzaUm, so it sort of keeps your, uh, resources focused where they are most effective, call it
AaronThat's, that's a great way to, uh, to put that point. Um, there's a project that we did recently where our, our principal controls engineer, our, our Ferrari in Ruben's analogy, had, uh, uh, finished a design and, uh, we needed to know if, um, a hinge would last for a certain number of cycles. And it wasn't really in the scope of work for, for Pipeline to put together a cycle test, rig and, and perform that testing on this hinge.
AaronAnd it would've taken our controls engineer, you know, not a ton of time, but maybe a, a day or two to, like, put all this together and build the controls for it and execute it. And so instead of our controls engineer doing that, we, we give this to our intern, and our intern used Easy Motion to create the, the cycle test motion for this hinge and just, you know, knocked it out. He spent a couple of hours building a simple rig on a bench top, and then hooked up Easy… I think it was Easy Pneumatics he used, and in a, you know, an hour or less, he had this, this, uh, cycle test running, and I think we ran it for like, I don't know, hundreds of thousands of cycles.
AaronAnyway, it, it worked. And so that was, like, a really practical example of how Easy Motion allowed us internally to, to move way faster and use appropriate resources for, uh, the, the scope of work. In, in this case it was outside the scope of work, but we did it anyway to be nice to our customer.
MarkYeah, mean it--
AaronGo
MarkI see, uh, along those lines it's similar to like 3D printing parts nowadays, where you kinda design something that is gonna get machined, machining it takes time. Uh, if you can't do it in-house, you got, you gotta wait for it, it gets costly. But you can 3D print a prototype and you physically have something. Easy Motion kind of fills that gap on the automation side of it of like, well, in the end, you might have this larger automation project that's gonna happen, but you just wanna test something very quickly and easily right now.
MarkYou can use the Easy Motion to do that, you can get your results and know this is gonna work before you've all in on the, the full-scale professional automation side of it.
AaronSo we've talked a little bit about how Easy Motion has benefited us internally. We've built production systems around it. Of course, we don't build all of our production automation around it. It requires the right application. But for the right application, we used it for production. We definitely have benefited from it in our R&D, our process development work. Let's talk a little bit about how it has benefited our customers, because this is our, um, not quite our first product technically, but the first one that has had any legs really.
AaronAnd, uh, there is, uh, one customer in particular who has had tremendous success with the Easy Motion platform. We've even gone on to do some s- uh, customization for their unique and very specific application. And we can talk about this because they've given us permission to do so, thankfully. There are some videos out there in their facility looking at, at what they're doing and how they've used Easy Motion. But, uh, essentially, they, they are testing, uh, solar panel, frames?
AaronWhat do you call them? Solar panel
Ruben InzunzaThey're movers or trackers. They, they, their core, yeah, is the, the solar panel tracking
AaronSo y-you mount these solar panels to, uh, a tracker, a frame basically that rotates and follows the sun, and they need to verify that these things work, that the motion is correct, and they're basically cycle testing these things over and over and over. And they had a legacy system. Well, uh, uh, Ruben, why don't you, like, fill in the details here? What, what were they using? What were the problems that they had? And
Ruben InzunzaYeah. So
Aaronsolve those problems?
Ruben Inzunzathey had the controls team on the actual, like, product side. So these systems out in the field get controlled with a PLC. It's, you know, in a robust industrial system. Um, but, uh, it's a PLC. Um, and then the design team or the controls team on the, the product side took a version of that and kinda, uh, sliced and diced it to make it a, you know, "Hey, now we can run this one test on your floor because the design team keeps…" You know, th- they're trying to weight optimize this bracket or whatever, and we gotta cycle test it to, to the full life of the thing to make sure it survives.
Ruben InzunzaUm, so that's kinda how that started way back when, and then they slowly made more of the same, but it was real rigid. It was the, the controls team kinda drove that, and they're busy doing the controls for the, the, the actual product, right? Um, and you know, the, the test team only had a few, few inputs of like, "Oh, how long should this thing run?" And, "Well, it only ever runs to this one position. We can't make it, you know, change it. Or if we do need to change it, it's, it's real-- gets real complicated and we're editing a bunch of structured texts that, you know, none of them wrote or is maybe commented very well." I just remember, uh, that was, uh, very high on the list of, we don't want it to be like that just 'cause it's been a pain in the butt, um, all these years.
Ruben InzunzaUm, but you know, they, they have, uh, call it a low volume, high mix, uh, sort of tests that they, they need to get through because the design team's constantly, uh, requesting tests to, um, to validate their, the design decisions. Um, but yeah. The, their ask was like, "How do we, how do we morph these tests ever so slightly every single time because we're asked to do something slightly different every time?
Ruben InzunzaUh, we don't have the time or bandwidth internally," quote-unquote,"on the customer side at the testing lab to, to handle all those, those requested changes or even the hardware itself wasn't set up to, to handle. Hey, uh, use this new sensor that we wanna measure this other thing." Pick your favorite, uh, engineering unit. Um, and, and tell me how, how that responds or, or what kind of readings we get there. Um, so yeah, it was a real rigid system that they were working with, and they were making it work.
Ruben InzunzaUm, but they sort of saw the, the value of being able to, to be nimble and, and dynamic in, in the test setup itself.
AaronAnd I remember one of their engineers telling me that it, it, it could take hours just to make a simple, like really simple change. Like change the motor speed from, you know, A to B or, move to a, a different position or something like that. Super simple changes took-- could take hours. And I think their longest test was taking them, like, 10 months, something like that, and it was largely because they couldn't really automate it, at least not fully. They had to shut it down, at night when no one was there because it had to be closely monitored by someone.
AaronThe, the system was so fickle. And once we implemented Easy Motion that, that 10-month test went down to two months, so we were able to reduce their test cycle time by 80%, which… I mean, think about that from a business standpoint. I don't know what, what, you know, uh, what that is in dollars exactly, but you gotta think, if you're saving eight months validating a product and, and getting it to market eight months or 80% quicker than you would have otherwise, that's gotta be a tremendous boon to your revenue as a company.
Ruben InzunzaYeah, it's, uh, there was a transition period in that specific example of, you know, the, our customer sort of only understood the, the tools they were using before, right? And now with Easy Motion, they're, they're getting really creative, right? They're, they're letting the design team, "Hey, now we can test for all these other kinds of situations. We're not just kinda shoehorned into these specific preset tests we've been using," uh, the, the classic just because someone's been doing it that way doesn't make it the right way kind of thing.
Ruben InzunzaUm, so you know, they're, they're getting real creative on how they, they combine some tests and things like that, and it's been, uh, I don't know. To me, it's really exciting to see someone really push Easy Motion to, to, to new boundaries, call it in, in terms of applications.
AaronThat might be the answer right there to this next question I wanted to ask you both. But what, thinking back over the, you know, it's been a few years, several years maybe, of development on this and refinement, what was one of the most satisfying moments for each of you?
Ruben InzunzaI think for me it was the, uh, it was both satisfying and disappointing, I call it. Uh, but hindsight's 20/20. Uh, the, the moment of, "Oh, crap, we can make the motion, the, the motor stuff work," just 'cause I had known, I had, you know, externally, on the internal team I guess, um, had seen the, the struggles of the other team. I was like, "Dude, they, they put in a lot of hard hours to try and get that stuff to work." Uh, and then with Mark and I were kinda collaborating and the, uh, the, the skunks works era of this, uh, project when we were working on it when maybe we shouldn't have been, we had other things to do possibly.
Ruben InzunzaUm, and, and that eureka moment of, "Oh, crap, it totally works. This is awesome. Let's, uh, what else?" Like, like, what's the next step, you know? Just regaining that excitement for this idea that we've all kinda had in the back of our minds. And then you say, "Oh, man, that … Cool, now it works." And then like, "Ah, we spent so much time on some of these other applications where if we had this tool, it would've been so much faster, uh, internally in our development process." Um, so you know, obviously the, the what if questions. Um, but that's been the, the most exciting Part of it for me, it's the knowing I have this tool that I can leverage and others can leverage to, to make the team better and more efficient, right?
AaronHow about you, Mark?
MarkYeah, there, as you mentioned that, there's definitely, uh, that robot program that was mentioned before. I really am like, "Man, I wish I had Easy Motion back then. It would've made that a lot easier." but I think the, the most satisfying thing for me is this, uh, this solar tracking project of getting all the pieces of Easy Motion together, and then seeing, uh, a third party that really is, you know, not drinking our Kool-Aid kinda thing, truly adopt it, and then see, oh, wait a minute, all of these other As you see, like, their, eyes light up as they realize all of these other avenues are there of, "Wait, we can do this now?" Or, "What happens if we do this or this?
MarkCan we try to do this thing?" And then that functionality, and then it's just like, oh, all of a sudden it's like a whole new world that they've kinda walked into. So it's like coming up with the idea, working with the team to kinda get it kinda refined, and then finally, you know, seeing that kinda child go off into the world and, like, start to flourish, is kinda like a, a proud parent moment of like, all right, it's, it's doing its thing, and it's, it's working. It, it is safe. It's out there, and they're, you know, they're thriving kinda deal, so I think that's, uh, that's where I get a lot of joy out of it.
AaronYeah, that's great. Um, y- you mentioned working with the team to develop this. So you and Ruben worked closely on this, and of course, we're, we're standing on the shoulders of giants. We had a couple other team members, Jason and Ryan earlier, who did a lot of the, the foundational work that we were able to leverage at least, um, what's the word I'm looking for? Um, conceptually, uh, a- and more than just conceptually. I mean, uh, I think Jason was the one who first came up with the idea of using this language Blockly as the user interface, which is a language that Google developed, and it's open source.
AaronAnyone can use it. And so we've just kind of, uh, fitted it into the Easy Motion ecosystem. So that's the, the front end that users see, the visual drag and drop, um, environment. And then y- you and-- but you and Ruben are, were the team that kind of took it across the finish line in, in the end. What was that collaboration like between the two of you, and, and why was that partnership important?
MarkUm, well, we, we had worked on a, a system together, that used, I guess as sort of the, our base level building blocks for where we got our end of it um, we really learned, I think, through the, uh, pressures, let's say, of that project and the timeline and the challenges of that, we really learned how to work together well and kind of communicate well as far as,"This is what we're gonna try to do. Let's quickly test that and move on to the next thing," and kinda, we could each do our own thing and kinda quickly spread apart, do a thing, come back together.
MarkSo think through that project, we really came up with a, I don't know, I think a, a procedure or a, I don't know, a way to collaborate very well. So when we, when we went to tackle this part of the project okay, how do we integrate the work that has been done before with stuff that we've done before together, um, it went, I would say, as smooth as it could go. It was almost like we were, uh, thinking the same thoughts a lot of the times, and then each one of us had our own kind of ideas, and we could run it by the other person, and we were speaking the same language the whole time, which was nice.
MarkUm, and then once it kinda, it moved past that into the production sort of realm, were able to get, uh, more mechanical engineering team members involved to design it and build it and assemble it and figure out those challenges with us.
Ruben InzunzaYeah, I think it was, uh… I mean, I think that, that project where we kinda did the groundwork on our end, Mark, I think that was the, the first project we really got to work together, and it was, like, under a bunch of crunch time pressure and customer pressure to get a thing done. I was like, "Oh, man." I was like, "Oh, no." But I think you s- you nailed it. It's, that's where we, we learned how to work with each other. Um, a- and yeah, totally be soundboards for each other's ideas. And I think we're, we're both alike in, in a lot of ways of, "Let's just try the thing. If it fails, it fails. But let's fail fast and, and kinda iterate from there." And I think the Easy Motion development was right along those things.
Ruben InzunzaI remember the, uh, in one of our, um, I guess lab rooms, uh, at our facility, we just kinda took over half of it on the main workbench, and we had all, all kinds of wires running all over the place. But it was like, "All right. Let's, let's make it work fast just to, to answer the question." And then, uh, we got the answer we, we were hoping for in this instance. Sometimes, in the development process, you don't get the answer you're hoping for. Um, but uh, yeah, I think, um, you know, great communication and, and knowing that,"Hey, we can be wrong, and that's okay.
Ruben InzunzaBut together we can kinda take the next step from there and, and figure out how to start trending in the right direction." And I think, yeah, that's, that's been the, the MO in terms of our working relationship, um, on Easy Motion and, and every other project that we've taken on together.
AaronWhat lessons do you think the audience can take from the way that you guys collaborated on this project and apply to their own work to advance R&D or development phase projects? You mentioned communication. W-Was there any, like, specific techniques that you used or even beyond tech, uh, communication, any other lessons learned that other engineers could leverage?
Ruben InzunzaUm, I think, I mean, this is commonplace in pipeline no matter what project you look at, but just being a soundboard, uh, for each other, um, has, has been a great sort of tool. Um, and then I think learning each other's communication styles. I'm, I'm a quite visual person. Mark will, will, you know, always has a, a scratch pad next to him, call it, or his little stack of papers that he likes to sketch on and do things. So I think that learning each other's kinda communication types is, uh, essential.
Ruben InzunzaI mean, I think that that's overall just in life is, is a great, uh, lesson to take away, um, from that. Uh, and you'll be able to more effectively, A, listen to each other, right? Oftentimes, yeah, you talk with somebody, but you may not be listening. Um, and then, B, communicate your own ideas. I mean, you were talking about earlier about the, the inefficiencies of, of transferring ideas from one person's mind to the other and, and, you know, the iteration of that to, to truly get on the same page.
Ruben InzunzaFiguring out how to shorten that cycle is, is key to, to work together and kinda collaborate on this goal and, and sorta knowing what the end goal is, right? That's, I think, something we haven't talked about, which was I think we were very intentional about setting boundaries as to what this thing could and couldn't do. Um, I think on, on previous iterations we're like, "Oh man, that's a not enough constraints," call it, that, you know, we wanted the customer to be able to hook any kind of motor up, any kind of manufacturer, where we're like, "Ah, I think to make this work sort of at least in this first iteration or first generation, let's, let's, let's draw some lines where the customer needs to color in." And we've seen some benefits, right?
Ruben InzunzaWe still give the customer options as to what kind of hardware they can use at, on the, at the end of the day, but, uh, it lets us be, uh, let us concentrate our efforts. We're not, we're not trying to take a, a huge bite out of this, uh, sort of unknown task and, and kinda work our way through it.
AaronYeah, great. Mark, anything to add to that?
MarkYeah, I think, uh, mentioned it, the it's okay to be, uh, incorrect, like trying something. Uh, and I think that is-- that benefits us a lot. Like, just being in a safe environment where you can an idea or try something, it's okay to fail, and it's okay to be incorrect. And then a-along those lines with that, it's okay to ask for help, to go, "I don't know what I'm doing here. How can… Can you help me? That you're better at this than I am.
MarkHelp me out with this." Um, to kinda… That part of it work together really well. Um, and I think it works well inside of Easy and outside of Easy Motion, like just in projects in general, just being able to be, "These are my ideas. I'm gonna throw any sort of spaghetti at the wall," and know that you're not gonna get judged for it one way or the other, that this is what we're doing. We're, we're trying to um, ideation and just, uh… You're never gonna come up with something new if everybody's kinda stuck in their box trying to, be safe, do the same safe thing.
Markgotta… Every car on the road looks the same sort of scenario. Um, you don't, you don't want that. So I think that's where we, we do thrive, is just being able to have ideas and know that we're not gonna get judged for them, even if they're wacky. 'Cause to be honest, everybody's got a wacky idea. I, I don't know if there's an engineer out there that doesn't have a weird side project that they, whether they're working on it or not, they want to. It's in their head. to be able to like communicate that and like just know that, hey, somebody else can give you an idea to help you and go, "Oh man, I never thought of that," and then it becomes a reality
AaronYeah. I love Easy Motion. I think it is so cool. It, it almost feels like a superpower in a way to me. You know, it's like, uh, I can't fly today, but tomorrow all of a sudden with this new thing, now I can fly. Uh, Easy Motion for someone who doesn't have that skill set, can't program, can't create their own automated motion, all of a sudden they can, and it, it, uh, it feels like a superpower. It's definitely the only way I've been able to create any sort of automated motion sequence. Uh, and I'm super grateful to both of you for having the, the, the dream and the persistence to bring this to reality.
AaronUm, what a, what a great product and what a great team to be a part of. It's been a, a, a pleasure watching you guys work on this and develop it to the point that it is now.
Ruben InzunzaIt's been, uh, it's been fun seeing this thing grow and, you know, seeing the, the benefits both externally with our customers and internally. I don't-- It always makes me excited when somebody asks, "Hey, where's the…" You know, we, we keep the two original prototypes for the pneumatics and the, the, the Easy Motor box, um, just 'cause they're butchered and, you know, with our internal test meal, basically. But, uh, you know, we got engineers working on just random projects for customers like, "Hey, where's, where's the thing? How can I, how can I find it?" Right?
Ruben InzunzaAnd now we have, I think, enough team members that are, know about it and, and can leverage it effectively, and it's, uh, another, another tool in the tool belt internally.
AaronAll right. Well, I think we'll wrap it up there. Uh, if any of you listening to this episode want to check it out, just go to our website teampipeline.us. You can even do a demo of the software. You can drag and drop blocks on the screen and create your own motion sequence, see what that user interface actually looks like. There are also a variety of videos that you can watch to get a even greater sense of what E- Easy Motion does and how it works. So we'll wrap it up there. Ruben, Mark, thank you guys so much for hanging out with me today and, and talking about an internal project and, and how we turned it into a success.
Send us Fan Mail Lucas R. Pianegonda is the founder of Gradical, a Switzerland-based consultancy focused on helping medical technology companies make better and more sustainable decisions about plastics. Over the course...
Send us Fan Mail What if AI could help you take a hardware product from concept to production in a fraction of the time? In this episode of Being an Engineer, Aaron Moncur sits down with Ryan Pickens, founder of Pickens...
Send us Fan Mail Ghulam Murtaza is a Controls Project Engineer at Vanderlande with a background spanning industrial automation, robotics, controls, data science, cloud computing, and artificial intelligence. Before...
Send us Fan Mail Eron Flory has built a career around turning difficult engineering problems into real products - and, increasingly, around helping other engineers learn how to do the same. His background crosses custom...
Send us Fan Mail Dr. James Bryant, Ph.D., P.E., is a dynamic force in the engineering and leadership development arenas. With a robust background in civil engineering, James has spent over 20 years leading...