Essilor
Setting Up Essilor Designs
Essilor designs differ from most other vendors in a couple of ways.
First, Essilor selects the donor blank in most cases, and returns the OPC of the blanks to use for a job in the LMS file. This means the design must be set up to indicate that the LDS vendor will do blank selection. This is done by checking the appropriate option on the Digital tab of the lens design setup:
This will disable blank selection in Rx-Universe (Rx-Universe will not even attempt to select donor blanks), including base curve selection. If a particular base curve is desired for a job, this can be entered in the "Base curve" field under Lens Selection; for example, to request a 750-base lens, the entry would be as follows:
Freeblank Designs
Essilor has some designs that allow the lab to select the donor blanks to use, and send the technical data of the blanks to DEO, similar to how other LDS vendors allow almost any donor blank to be used.
These designs are known as "Freeblank" designs in Essilor terminology,
- these designs need to be explicitly identified in Rx-Universe by sending "__FREEBLANK=1" in the LDS request to DEO (note two underscores in the tag). This is done by setting up a VCA over-ride label on the design:
2) the design should NOT be set up as "LDS selects blanks", since the intent is for the LMS to select the blanks.
3) The Essilor LDI file must be
4) The design must be set up with a base curve chart for selection. There are no "suggested" base curve charts from Essilor for Freeblank designs, so the lab is free to use any chart desired. There is a "generic" digital selection chart (84) which the lab may choose to try out. If using this chart, the option "Add add to sphere" should be checked, and the option "LDS selects blanks to use" should NOT be checked. An alias entry will also be required to identify the blanks that should be selected for the freeblank design.
LNAM codes for Essilor
LNAM codes for Essilor designs (freeblank or otherwise) are 6 character codes that identify the design, the material, the color and the coating. Therefore, the LNAM is not set in the lens style itself (since it is different based on material, color and coating), but rather is set in a VCA label table. There are two "standard" Essilor tables maintained for Rx-Universe - table "ESS" for Essilor designs in North America, and table "ESSL" for Essilor designs in Latin America. When setting up the Essilor digital type, the DS record must be set up to reference the appropriate table on the "Other tab": 
The table itself is found under "Devices", "VCA Label Table Settings"; one section looks as follows:
The different combinations of material, design, treatment (coating) and color (tint) have different LNAM values which are sent to DEO.
Device Settings for Essilor
Essilor has the ability to send VC labels with different values for specific devices. This is done in two ways; if done with a PROC record, the value is sent specifically to apply to only one type of device. For example, Essilor may send "PROC=R;GEN;;;LMATID;26", which indicates that LMATID=26 should be sent to a generator (GEN) which requests LMATID. This is standard behaviour for the VC PROC label.
Essilor also sends device-specific data inside of _LDCRYPT blocks. For example, inside the LMS file might be a block defined as:
_LDCRYPT=DEO:VFT;R;395
_ZZENCRYPT=DO=B
(some data)
_/ZZENCRYPT
The data inside the ZZENCRYPT loop can be optionally stored, in Rx-Universe, to be send to a device appropriate according to the DEO label. This data must be selected within Rx-Universe to be saved device-specific; the default behaviour is for all these options to be unchecked:
Each of the different labels (LMATID, LDTYPE, ENGMARK, GAX, etc) can be individually selected (or not). If selected, then the corresponding VC label values will be stored, in Rx-Universe, for that particular device type.
For ENGMARK records, there can be multiple records sent in the main section, as well as in one or more LDCRYPT blocks. For these ENGMARK records, records inside the DEO:VFT block will be sent to any DEV=GEN device; records inside DEO:LASEROPLM3 blocks will be sent to any DEV=ENG device. For ENGMARK inside of other DEO:XXXXX blocks, they will be sent to a device identifying itself as DEV=XXXXX where XXXXX is some device identified (for example, CTA). For ENGMARK records only, the values from any applicable LDCRYPT block will be send IN ADDITION to the ENGMARK records in the main section (in the section of the LMS file outside of the LDCRYPT blocks).
Save device ENGMARK - if checked, then any ENGMARK records sent in the LMS file will be saved and sent to an engraver which requests ENGMARK. Note that ENGMARK is normally a series of records, and not a single record as with most other VCA labels.
Note that for Essilor Digital only, it is possible for Essilor to send different ENGMARK records for different devices, by including ENGMARK records in the LDCRYPT blocks for specific devices. In this case, any ENGMARK records in the main section (outside of any LDCRYPT blocks) will be sent to all devices requesting ENGMARK. ENGMARK records received within a DEO:VFT block will be sent to any GEN device; and ENGMARK records received within a DEO:LASEROPLM3 block will be sent to any ENG device. Any other DEO: value will be sent only to devices of that device type (for example, ENGMARK records received within a DEO:CTA block would be sent to a DEV=VTA device).
Switching To Short Corridor Designs
For many designs, Essilor offers the design in regular and short. The LMS is responsible for switching to the short design if the seg height of the order is < X (usually 18mm), and the add power is <= 3.00D. (If the add is > 3.00, the regular design is used regardless of the seg height).
To accomplish this, even though RX-Universe does not select blanks, the alias file is used to trigger switching between regular and short designs. For example, to set up an alias from Physio Enhanced Azio to Physio Enhanced Azio Short, the lens styles would be set up similar to:
Regular design set up with minimum seg height of 18mm, and maximum add of 3.50
Short design set up with minimum seg height of 14, maximum add power of 3.00
Both styles are set up with the option “LDS selects blanks to use” checked on the Optional tab.
Then set up an alias record from PHEAZ to PHEAZS.
When design PHEAZ is used on an order, OMICS will check the alias file, and will switch to the PHEAZS design if the seg height of the order is < than the minimum specified for the requested design, and if the add power is less than the maximum add power specified on the alias lens style. Multiple alias records can be specified, to allow checking multiple lens styles (ie several corridor lengths).
DLP polishers
DLP-Server
If DLP-Server is being used with Essilor Digital, there are some specific rules that are in effect, beginning in version 6.46.00 of Rx-Universe:
1) For an Essilor Digital job, LAPBASX and LAPCRSX should be expressed in mm and not diopter
2) For any job that is not Essilor Digital, LAPBASX and LAPCRSX should not be sent at all to the DLP. The macros will be selected using GBASEX and GCROSX.
To set this, first, the DLP-Server must be identified as such in the device setup - this is done in the "Device Specific Parameters" on the Digital tab of the device interface:
When an LMS file is received from Essilor, if the LAPBASX and LAPCRSX are expressed in mm, these values will be saved as PROC records, and then sent (only) to a DLP-Server:
If the LAPBASX and LAPCRSX values are sent from Essilor in D, they will be converted to mm when sent to the DLP-Server.
When the DLP-Server requests an Essilor Digital job, the packet will include LAPBASX and LAPCRSX, in addition to GBASEX and GCROSX (assuming all are requested in the initialization by the device):
For a job which is not Essilor Digital, Rx-Universe will suppress the LAPBASX and LAPCRSX labels - with the same INI string as the previous example, 
The LAPBASX and LAPCRSX labels are omitted from the response.
Barcode
If the DLP polishers are used for Essilor digital, in a non-interfaced mode, and the lab wishes to print the DLP barcode on the ticket, this is now possible.
The code for the DLP polisher is returned in the LMS file using the P1PROC label, similar to the following:
This 18-digit number can be scanned on the DLP in order to set the macros for polishing for the job.
To activate the printing of this field on the PCL work ticket, the "conveyor barcode option" must be set, on the Surf2 screen under System Parameters:
When using the "conveyor barcode option", if the P1PROC option is sent in the LMS file, the DLP barcode will be printed on the work ticket, on the right side, above the conveyor barcode: