Two ways to test PLC code without the real hardware: software simulators, which add cost and complexity, or having the actual PLC shipped to your desk. Large integrators usually get stuck with simulators since hardware stays on-site, but OEMs and direct buyers can test on real equipment first.
So when you're designing panels, how are you able to, to kind of test your code that you're developing? Because again, you don't have the machine with you, you only have an idea what I/O is going to be, but you don't have a way to get with the hardware.
I got 2 ways to do that. So one way, so the traditional way when I was a systems integrator, like that wasn't working for OEMs, is we can do simulation. of all of our code. And actually, some clients require that you do a full-blown simulation and show them how all of it's going to react. And, but, you know, you pay more for that. But like, that is part of something you could have done upfront if you want. But I am lucky enough that I can just say I want the PLC shipped to me. And so I always have like the hardware on my desk. So that's a— that is a common issue as like a PLC programmer. If you work for a large systems integrator, you're going to have to figure out how to use those simulators because more often than not, they're not going to give you the PLC to have on your desk. If you're the one buying the PLC, I have a lot more control of that. So I can be like, okay, well, I want that shipped here and I'm going to do stuff to it, and then I'll ship it to whoever's, you know, actually putting the panel in when I go, or I'll bring it there myself, um, because I have— and I'll have the controller. But that's kind of the two ways. And if it wasn't shipped to me, I could still do code and I could test it, but I prefer to have— like, I have an entire, um, 13-slot chassis downstairs with an L72 in it, um, and I have all the cards so I can do whatever I want.
