Frame Trace Import

Owned by Pat Gauvin
Last updated: Mar 06, 2019 by Kim Beck
2 min read

Overview

Frame traces that are created by 3rd-party software packages can be imported into Rx-Universe if they are contained in a text file with the appropriate VCA labels.  Frame trace files can be imported manually via the "Frame Tracings" maintenance program, or automatically as a function of the "Remote Order Processor". 

Frame trace files can have any naming convention, with an extension; they should be in a format similar to:

FMFR=LOH
FRAM=CIRCLE60
EYESIZ=60
BEVP=7;7
DBL=16.0
ETYP=2;2
FTYP=3;3
_NOP_BEVA=D;0
_NOP_ROUGH_TOOL=14;14
_NOP_FINISH_TOOL=9;9
GDEPTH=0.50;0.50
GWIDTH=0.50;0.50
DRILLE=R;CR;25.00;10.50;1.40;25.00;10.50;;1;F;;;;
DRILLE=L;CR;-25.00;10.50;1.40;-25.00;10.50;;1;F;;;;
TRCFMT=1;400;E;R;F
R=3000;3000;3000;3000;3000;3000;3000;3000;3000;3000
R=3000;3000;3000;3000;3000;3000;3000;3000;3000;3000

Any VCA label can be included in the frame trace file, including drill points (as above), non-equiangular and shelf data (for edgers such as the ES-Curve).

any label not recognized by Rx-Universe will be saved with the trace, and sent to any device that requests it.  In the above example, the three _NOP labels would be saved in the trace record:


Manual Process

When creating a new frame trace record in Rx-Universe, you can choose to import the frame measurements from a file using the "Import" button.  This button is available (visible) once the name and manufacturer fields have been entered on the "Frame Tracings" tab.


After clicking the "Import" button, select the file to import from the window:


Trying to import a file that does not contain trace information will result in an error:


Once the file has been imported, the fields will be automatically imported.  If the file does not contain the DBL information, it will need to be manually added before the trace can be saved.

Automated Process


As an alternative to importing traces one at a time, the Remote Processor can be used in Rx-Universe to automatically import and create frame trace records.

Frame trace files must be placed into a folder named "Frame", created as a sub-folder of the "Directory for Incoming Orders" contained in the "Remote Order Parameters" screen.   If you wish to keep the a copy of the imported patterns, create another sub-folder called "Frame\Archive".  The frame trace files will be automatically moved to this folder once they are processed with no errors.   If a frame trace file can't be processed, it will be placed in a sub-folder called "Frame\Error". 

To illustrate, if the Remote Processor is set up to process incoming order files in the C:\Rx-Universe\OMICSTX folder, then frame files should be placed into the C:\Rx-Universe\OMICSTX\Frame folder.

The Remote processor will automatically poll the "Frame" folder to see if any frame trace files exist, if any are found, it will process 10 pattern files during its cycle, then re-check for orders to process, then check for more frame trace files.  This cycle continues until the Remote Processor is shut down or paused for the nightly server backups (if activated).

When processing frame files automatically, frame trace file must contain FRAM, FMFR, EYESIZ and BRGSIZ, so that the frame can be saved with the correct naming convention.