You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 28, 2018. It is now read-only.
Try and model (in a Python library/package) as much functionality as you would feel is appropriate to perform remote machine monitoring and/or predictive maintenance from the machine tool.
Think about all the parts that could fail and what sort of sensors would be on those parts. Those sensors are providing your program with data.
Thank about what sorts of behavior each of the machine parts has that you would need in your model. This is important if you are trying to simulate some degenerate conditions (for example) that are causing machine component failure or you are trying to train your ML model.
Using class composition instead of class inheritance is a probably a better approach here since part of the machine are a 'has-a' relationship instead of a 'is-a' relationship with
One of the requirements of modeling a physical item is establishing a domain model in your programming language of choice - in this case Python. You do not want to model everything however. That would be a waste of time and it would negatively impact performance for very little insight (or none at all).
Once you have a machine tool library, put that library to use within a simulation engine of your design. This will be a Python module which consumes the package (or packages) that you just created and runs the machine model by accepting an 'ON/OFF' command and several movement commands for the machine's various components (e.g. chuck open/close, steady rest to a specific position, tool change).
The text was updated successfully, but these errors were encountered:
Model the CNC lathe as show in this video: https://www.youtube.com/watch?v=59RymNHME4o
Try and model (in a Python library/package) as much functionality as you would feel is appropriate to perform remote machine monitoring and/or predictive maintenance from the machine tool.
Think about all the parts that could fail and what sort of sensors would be on those parts. Those sensors are providing your program with data.
Thank about what sorts of behavior each of the machine parts has that you would need in your model. This is important if you are trying to simulate some degenerate conditions (for example) that are causing machine component failure or you are trying to train your ML model.
Using class composition instead of class inheritance is a probably a better approach here since part of the machine are a 'has-a' relationship instead of a 'is-a' relationship with
One of the requirements of modeling a physical item is establishing a domain model in your programming language of choice - in this case Python. You do not want to model everything however. That would be a waste of time and it would negatively impact performance for very little insight (or none at all).
Once you have a machine tool library, put that library to use within a simulation engine of your design. This will be a Python module which consumes the package (or packages) that you just created and runs the machine model by accepting an 'ON/OFF' command and several movement commands for the machine's various components (e.g. chuck open/close, steady rest to a specific position, tool change).
The text was updated successfully, but these errors were encountered: