AutoComp Functionality: Overview
Measurements are defined and grouped by part in AutoComp 'routines'. The routine defines all characteristics of each measurement in a 'dimension', including the source gage data. A part routine contains all dimensions for a fully measured part, regardless of the number of gages used in the measurement process.
GageData files contain the measurement data from the gages used to measure the part.
Note: AutoComp can be used in demo mode to practice using the interface and functions.
What is a Routine?
A routine (or part routine) is a collection of dimensions and global routine parameters that is used by AutoComp in the gage-compensation cycle. Each dimension in a routine contains the parameters for a specific measurement on a tooled part, associated with a specific gage. As the dimension is tooled, the gage puts out a gage data file.
All measurements marked as “critical” are required to complete a cycle. When all critical dimensions are processed, the current cycle is complete, even if other dimension measurements are missing.
Routines can be automatically loaded and suspended by AutoComp as gage data files are detected. See AutoLoad Routine Value
When AutoComp automatically loads a routine corresponding to a gage data file, it appears on the main AutoComp window.
Note: Only one routine can be loaded at a time.
As routines are suspended and later reloaded, all historical data are preserved. To clear all historical data, manually unload the routine or use run data lifetime parameters.
What Is a Gage Data File?
A gage data file is created by the gage (or gage software application) that measures the part. This gage data file is parsed in AutoComp, based on the dimension information in the PartRoutine.
A routine may use only one gage or it may use many gages, depend- ing on machine tooling needs. AutoComp is able to handle information from many different gages in a given routine.
When more than one gage is used in a routine (multi-gage routine), the dimensions in a routine are not all measured by the same gage. For example, most of the dimensions of a valve body might be measured by a main CMM, but one dimension might be measured by a different wireless gage.
For each dimension, the gage puts out a gage data file containing measurement values. AutoComp detects the gage data files and loads the appropriate routine. The gage data files are parsed by AutoComp definitions called gage converters. Every dimension that is specified in a routine must be associated with a gage converter.
Gage data file names are very important because AutoComp’s ability to select and load the appropriate routine is contingent on the data file name. Specify the gage data file name in a user interface associated with each gage.
How AutoComp Selects and Loads a Routine Automatically
When a part is actually starting to be tooled, AutoComp selects and loads the part routine automatically.
A routine is loaded automatically (and the currently-loaded routine suspended) when AutoComp detects a gage data file in the configured gage folder. AutoComp selects and loads a routine that matches the gage data file, using the following criteria:
- Routine name. Routine names are limited to 64 characters. The complete routine name must be included in the gage data file name. Up to the first 64 characters of the gage data file are extracted to match a routine name.
- If a routine exists whose name matches those characters exactly, it is loaded.
- If there is no exact match, AutoComp attempts to match a routine from 63 characters down to 2. If a match is found, that routine is loaded. If no match is found, the gage file is ignored. Gage data file that have not been processed due to not matching routine names will be deleted on the next Autocomp restart, or they can be deleted by the user in the configuration screen.
- Gage converter name. The gage converter is an AutoComp function that parses the gage data file. Unless all the routine dimensions use the default gage converter, the gage converter name must be appended to the gage data file name in square brackets.
Routine Names
The routine name is important because it is used by AutoComp in selecting and loading gage data files (whose names must include the name of the routine they are associated with, or a portion of the name). Generally, it is a good idea to give the routine a descriptive name (such as “Valvebody”).
Note: AutoComp is not case-sensitive.
A routine is loaded automatically (and the currently loaded routine suspended) when AutoComp detects a gage data file in the con- figured gage folder. AutoComp automatically selects and loads a routine whose name matches the gage data file name.
Note: The routine name does not have to be an exact match, but must contain the beginning portion of the gage data file name.
Gage Data File Names
Each measurement is written to a gage data file, to be parsed by the gage converter definition.
Note: The gage data files and file paths are set outside of AutoComp; this process is not part of the AutoComp system.
The gage data file name has three components:
- All or part of the routine name with which it is associated and optional additional characters
- The gage converter name (in square brackets)
- The file extension.
Routine name in the gage data file name. Gage data files are always named to correspond to a routine name (whether or not it is a multi- gage routine). the entire routine name must be in the file name. Thus, if the routine name is “Valvebody,” then “Valvebody” must be part of the gage data file name. For example, “Valvebody1” or “Valvebody_timestamp” could be part of the name.
Gage converter name. The gage data file name must include the gage converter name in square brackets, unless all included routine dimensions use the default gage converter. If the default gage converter is used for all dimensions, it may be included in the file name, but is not necessary.
File extension.The file extension is gage or gage application-depend- ent.
The format for a gage data file name is:
<Routine Name & optional char(s)><[gage converter name]>.<file ext>
For example:
- A gage data file name where all the dimensions use the default gage converter program could be “Valvebody1.txt,” or "V alvebody_timestamp.dat.”
- In a multi-gage routine, or where a single gage that is not the default is used, the gage data file name could be “Valve- body1[ZEISS].txt,” or “Valvebody_A[MAHR].dat.”
Note: When creating a multi-gage routine, be sure to specify the cor- rect gage converter for each dimension.
CEI_CurrentRoutine Gage Files
If a gage data file matching a defined gage converter file filter and path is seen and named,
CEI_CURRENTROUTINE[GageConverter].file_extension
where:
- CEI_CURRENTROUTINE is the hardcoded filename,
- GageConverter is the defined AutoComp gage converter, and
- file_extension is the gage converter file filter extension,
then that file will be treated as if it is named for the currently loaded routine and is merged into the current cycle. This can lessen the times that file names need to be changed in gage applications. Dimensions are still matched by gage converter name and data file row number.
There is a limit to CEI_CURRENTROUTINE. To send data to a currently loaded routine using the CEI_CURRENTROUTINE func- tionality, the routines gage converters must have file filters using an extension, for example .ext.
The .ext can be any extension, if the CEI_CURRENTROUTINE files will have an extension (.csv, .txt, etc). The gage converter file filter could also be a plain wildcard *, with no extension, if there will be no extension on the CEI_CURRENTROUTINE file.
If no routine is loaded, an error message popup will note the routine is empty and not loaded.
Note: AutoComp uses CEI_CURRENTROUTINE or CEIRTN to send a gage data file to the currently loaded routine. A routine should never be named either CEI_CURRENTROUTINE or CEIRTN or the 'current routine' functionality will not work. Instead, every time a gage data file of either of the above names is detected, the routine of the matching name will be loaded.
Multi-Gage Routine Diagram
The following illustration shows AutoComp functionality for a multi-gage routine (where different dimensions in a routine are measured by different gages).
