What type of machine are you asking? A machine that measures the wedge and roundness of lenses.
I already wrote software for the machine, and it is in production, but it is fragile and prone to blocking when they do not do something in the correct order. I am trying to come up with a better way to architect it so that it is stable and supported.
Here, fast twenty seconds run down. There are two modes: setup and start. In tuning mode, the operator can manually move any of 6 different engines using one of 6 different switches with instant switching on the control panel. They get everything that they have, then they turn it into an operating mode, load the lens and press. The machine will automatically add three indicators, find the edge of the lens, and then turn the spindle and measure everything around the wedge.
I ended up with a very bad design without a class that raised an event that says when the switch changed state, which switched to it, and what is its new state. Then I do a lot of things to determine what a machine can do. As you can imagine, this is very bad.
Does anyone have any good ideas on how to structure this? I have my own, but I want to hear some of those that may be a little more experienced in developing this type of application.
source
share