Version 6.36.00
- Tony LeBlanc
Version 6.36.00 Update Log
Released 24 March 2014
(includes changes made since 6.35.00)
Device Interfaces
When viewing the device log file on a device session, the log file can now be saved to a file (in addition to being viewed and being emailed to support) (version 6.35.01).
The digital interface with ProFit has been changed to accept ENGMASK in the LMS file and, if specified, to pass that through to devices (version 6.35.02).
Labels FLATA and FLATB have been added to the VCA interface to support older equipment. FLATA is treated equivalent to CRIB, and FLATB is equivalent to ELLH (version 6.35.03).
If using a GerberCoburn DTL generator for digital jobs, setting the “Model Override” field on the “Other” tab of the device setup will cause the label SDFMODE to be sent to the device immediately following the LDPATH label, for digital jobs only. In addition to setting the “Model Override” field to “DTL”, the lab should also set the SDFMODE to the appropriate value for ftp, in each digital lens style that will be manufactured on the DTL generator (version 6.35.04).
OMICS now supports non-equiangular and shelf data, required for modern edgers such as the ES-Curve. Both shelf data and non-equiangular data are typically provided by the frame vendor or created by means of a program such as the National Optronics Frame Editor, and imported into OMICS (see the section on Trace Importing in this document) (version 6.36.00).
The number of devices in a device session has been increased from 18 to 40 (primarily for TCP/IP sessions). In addition, if OMICS receives a TCP/IP request from a device with an IP that is not in the device table, an entry for that IP will be created automatically with default settings (version 6.36.00).
Creating VCA Output File
To enable third-party systems to easily retrieve the results of calculations of OMICS jobs, a "file" device is supported.
When active, OMICS will create a file for each order, each time an order is entered, received, or calculations are done for the job. The file will be created in a subfolder "DEVFILE" under the root OMICS folder. For example, if OMICS is installed in C:\OMICS, then the VCA device output files will be created in C:\OMICS\DEVFILES
There are two steps to activate this feature in OMICS. First, on the Device tab under System Parameters, the option "Create device file" must be checked:
Then a device session must be set up for the file interface, similar to the following:
The file device interface has all the options available in any VCA interface.
An LDI file is used to determine what labels should be included in the output file, as is used with the Rx-Server interface and interfaces with digital calculators. To modify the labels included in the output file, click the "View/Edit LDI file" button.
If the LDI file does not already exist, you will be prompted to create it:
If the file already exists, you will be able to modify the contents:
Any VCA label may be included in the LDI file, and such data will be included in the VCA output files. Note that for trace data, only format 1 TRCFMT data is supported in a file.
Sample:
File DEVFILE\12340008.VCA, using the LDI file above, would be created as follows:
REQ=LDS
JOB=12340008
DO=B
LNAM=SINGLE VISION;SINGLE VISION
SPH=+02.00;+02.50
CYL=-01.00;-01.25
AX=115;085
PRVA=000;000
PRVM=+00.00;+00.00
DBL=16.0
IPD=31.00;31.00
OCHT=22.05;22.05
SEGHT=0;0
BLKD=58.00;58.00
RNGH=07.00;07.00
FCSGUP=+00.0;+00.0
FCSGIN=+04.8;+04.8
ADD=0.00;0.00
FBOCIN=+04.80;+04.80
FBOCUP=+00.00;+00.00
LMATTYPE=2;2
HBOX=55.6;55.7
VBOX=44.1;44.0
FED=56.5;56.4
ELLH=65.0;65.0
DIA=70.0;70.0
LIND=1.586;1.586
TIND=1.530;1.530
FRNT=+06.34;+06.34
BACK=-06.25;-06.25
BCTHK=07.6;07.6
MBASE=06.25;06.25
MINCTR=+01.50;+01.50
MINEDG=+01.30;+01.23
PANTO=?;?
ZTILT=+11.20;+11.20
BVD=?;?
MINTHKCD=00.00;00.00
GBASEX=-04.62;-04.16
GCROSX=-05.52;-05.29
LMATID=1;1
LTYP=SV;SV
PTOK=0
AVAL=+09.51;+09.51
SVAL=+04.88;+04.81
GAX=115;085
GBASE=-04.62;-04.16
GCROS=-05.52;-05.29
SBBCIN=+00.00;+00.00
SBBCUP=+00.00;+00.00
SDEPTH=+00.00;+00.00
THKA=?;?
THKP=02.54;02.44
THNA=?;?
THNP=01.30;01.20
LDPATH=?
GTHK=+03.10;+03.00
KPRVA=342;185
KPRVM=00.00;00.00
TRCFMT=1;100;E;R;D
R=2692;2733;2781;2827;2867;2899;2916;2915;2890;2848;2794;2730
R=2660;2590;2525;2464;2409;2362;2321;2289;2262;2239;2222;2213
R=2206;2203;2207;2221;2241;2265;2292;2330;2374;2429;2487;2555
R=2629;2705;2782;2857;2923;2962;2979;2977;2957;2922;2877;2831
R=2793;2757;2729;2709;2693;2686;2683;2684;2693;2707;2721;2734
R=2739;2733;2713;2674;2625;2568;2505;2450;2398;2352;2311;2276
R=2249;2227;2213;2201;2193;2197;2204;2216;2235;2256;2281;2308
R=2334;2362;2388;2411;2437;2455;2475;2492;2504;2514;2526;2543
R=2563;2588;2618;2653
TRCFMT=1;100;E;L;D
R=2724;2753;2790;2830;2873;2919;2955;2975;2979;2963;2919;2858
R=2787;2712;2637;2561;2496;2439;2383;2338;2298;2265;2239;2217
R=2203;2193;2189;2190;2197;2212;2232;2260;2294;2335;2385;2442
R=2503;2569;2641;2715;2785;2841;2886;2911;2918;2903;2871;2829
R=2786;2743;2703;2668;2634;2604;2580;2563;2549;2536;2524;2510
R=2495;2477;2457;2434;2409;2383;2355;2329;2301;2274;2250;2229
R=2213;2202;2195;2197;2203;2217;2237;2263;2296;2337;2386;2434
R=2491;2553;2615;2665;2700;2722;2732;2729;2714;2698;2687;2679
R=2675;2675;2684;2700
Trace Importing
Traces can now be imported from VCA-formatted files. This can be done manually when creating trace records, or can be done automatically by allowing the Remote Processor to import trace data files automatically.
The trace file to be imported must contain valid trace data, consisting of at least TRCFMT and R records. Optional information such as frame type, edge type (bevel, rimless or groove), pin bevel, and device-specific information (such as for ES-Curve tool selection) may exist in the file. If traces are being imported automatically, the file must also contain at least FMFR, FRAM, and EYESIZ. A sample file representing a 60mm circle with drill points might look like:
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(etc)
Manual Trace Import
When creating a new frame trace record in OMICS, 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 OMICS 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:\OMICS60\OMICSTX folder, then frame files should be placed into the C:\OMICS60\OMICSTX\Frame folder.
The Remote processor will automatically pole 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.
ART or Nucleo Blocker
When using an ART or Nucleo blocker, the preferred method of inducing prism is to generate up to 2 degrees of prism first, and block the remainder. To accomplish this, a new field has been added to the Blocking tab of the device setup. Any prism in “Generator prism” will be removed from prism required, and only any remaining prism blocked. If the remaining prism is greater than the “Blocker maximum prism” (on the same tab), then an error will be sent to the blocker, as more prism is required than the equipment can handle (version 6.36.00).
ART and Nucleo block selection can be done in addition to another blocking method set on the Blocking tab in System Parameters. For example, if blocking option “7” (dynamic block selection) is used, the lab can choose to print ART or Nucleo block selection as well, on the work ticket. The job can then be blocked on either the “regular” blocker or the ART/Nucleo, without the job needing to be changed. On the system parameters screen, the additional blocking is set:
The work ticket will then reflect both blocking methods:
Order Entry
When trying to e-mail an invoice and the system variable, Transmission Level, was set to anything other than "Never Transfer the orders", the transfer window would be displayed but the invoice was never e-mailed. This has been corrected (version 6.36.00).
XFD Files
OMGND.XFD
OMFREE.XFD
----------
OMGND.XFD - Added new fields:
GND-GEN-PRISM
GND-ALLOW-UNEQUIANGULAR-TRC
GND-ALLOW-SHELF-DATA
OMFREE.XFD - Added new fields:
WS-FREE-FTP-SW
WS-FREE-FTP-URL
WS-FREE-FTP-USER
WS-FREE-FTP-PASSWORD
WS-FREE-FTP-LDS-FOLDER
WS-FREE-FTP-LMS-FOLDER