(no subject)
Workin' on Saturday.
I'm getting some of the main functionality on my latest application finished up today. In other words, making buttons do stuff and lights light up.
I'm not really a design specialist. I know much more about back end than front end. My MVC is sick, yo. I got so much encapsulation, my façades have façades. My configuration is dynamic based on the machine's IP Address. And so forth. But, there has to be something to look at (I guess).
Today I'm working on diagnostic tools. This is my current goal:
I need to get all the FLAGs to say whether the PLC sees bits being on or off. 1 or 0. A PLC is a low level computer that monitors all kinds of things like robots and assembly mechanisms. In this case, it is monitoring a torque gun, some electric circuits, and some other stuff going on in the machine that is being used to assemble the car parts. As they assemble more parts, the lights will light up on the big screen above.
The diagnostic tools are for us. Well, me mostly. I want to be able to monitor network connectivity, PLC bits, and all kinds of other stuff that can tell me if the application is working properly, and if it isn't, what is wrong where. I don't get to just write this and move on to the next project. I have to support this myself. If anything goes wrong in the future (and things will go wrong) I have to be able to find out where the problem is. Rarely is it with the code, but usually it is a network cable, a stuck PLC, or some other external force.
That about does it for my break. I actually enjoy this kind of thing. Maybe not being in on a Saturday (but I am getting an extra vacation day which is why I'm here), but this part of my job, I love.
I'm getting some of the main functionality on my latest application finished up today. In other words, making buttons do stuff and lights light up.
I'm not really a design specialist. I know much more about back end than front end. My MVC is sick, yo. I got so much encapsulation, my façades have façades. My configuration is dynamic based on the machine's IP Address. And so forth. But, there has to be something to look at (I guess).
Today I'm working on diagnostic tools. This is my current goal:
I need to get all the FLAGs to say whether the PLC sees bits being on or off. 1 or 0. A PLC is a low level computer that monitors all kinds of things like robots and assembly mechanisms. In this case, it is monitoring a torque gun, some electric circuits, and some other stuff going on in the machine that is being used to assemble the car parts. As they assemble more parts, the lights will light up on the big screen above.
The diagnostic tools are for us. Well, me mostly. I want to be able to monitor network connectivity, PLC bits, and all kinds of other stuff that can tell me if the application is working properly, and if it isn't, what is wrong where. I don't get to just write this and move on to the next project. I have to support this myself. If anything goes wrong in the future (and things will go wrong) I have to be able to find out where the problem is. Rarely is it with the code, but usually it is a network cable, a stuck PLC, or some other external force.
That about does it for my break. I actually enjoy this kind of thing. Maybe not being in on a Saturday (but I am getting an extra vacation day which is why I'm here), but this part of my job, I love.