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
Add support Mazak machines with MS Windows-based controllers without MTConnect:
use case: when we don’t have agent running on a particular machine (either because MTConnect option is not bought by the customer or because the machine is quite old and not MTConnect-enabled);
we need to monitor the light indicator (green: in production; yellow: not in production; red: in alarm state) and based on the lit data, calculate the (approximate) availability and productivity;
we need to monitor Alarm.txt file for changes and process them:
in that file, there is a single line per alarm appended whenever an alarm is raised (from the file itself, we don’t know when an alarm is cleared though);
we could process LBD files in order to get some other data (like rapid override, feedrate override values, currently loaded program name, pieces produced, etc):
note, however, that in my experience, the LBD files are written somewhat irregularly (albeit their is a record every ten seconds);
we need to check the LBD file structure for Win 10 controllers are a few bytes longer (again).
The text was updated successfully, but these errors were encountered:
Add support Mazak machines with MS Windows-based controllers without MTConnect:
green
: in production;yellow
: not in production;red
: in alarm state) and based on the lit data, calculate the (approximate) availability and productivity;Alarm.txt
file for changes and process them:The text was updated successfully, but these errors were encountered: