Laser Model Interface Reference Manual

7/24/2019 Laser Model Interface Reference Manual

1/18

Laser Model Interface

Reference Manual


2/18

Disclaimer

Information of a technical nature, and particulars of the product and its use, is given by AVEVASolutions Ltd and its subsidiaries without warranty. AVEVA Solutions Ltd and its subsidiaries disclaim

any and all warranties and conditions, expressed or implied, to the fullest extent permitted by law.

Neither the author nor AVEVA Solutions Ltd, or any of its subsidiaries, shall be liable to any person orentity for any actions, claims, loss or damage arising from the use or possession of any information,particulars, or errors in this publication, or any incorrect use of the product, whatsoever.

Copyright

Copyright and all other intellectual property rights in this manual and the associated software, and everypart of it (including source code, object code, any data contained in it, the manual and any otherdocumentation supplied with it) belongs to AVEVA Solutions Ltd or its subsidiaries.

All other rights are reserved to AVEVA Solutions Ltd and its subsidiaries. The information contained in

this document is commercially sensitive, and shall not be copied, reproduced, stored in a retrievalsystem, or transmitted without the prior written permission of AVEVA Solutions Ltd. Where suchpermission is granted, it expressly requires that this Disclaimer and Copyright notice is prominentlydisplayed at the beginning of every copy that is made.

The manual and associated documentation may not be adapted, reproduced, or copied, in any materialor electronic form, without the prior written permission of AVEVA Solutions Ltd. The user may also notreverse engineer, decompile, copy, or adapt the associated software. Neither the whole, nor part of theproduct described in this publication may be incorporated into any third-party software, product,machine, or system without the prior written permission of AVEVA Solutions Ltd, save as permitted bylaw. Any such unauthorised action is strictly prohibited, and may give rise to civil liabilities and criminalprosecution.

The AVEVA products described in this guide are to be installed and operated strictly in accordance withthe terms and conditions of the respective license agreements, and in accordance with the relevantUser Documentation. Unauthorised or unlicensed use of the product is strictly prohibited.

First published September 2007

AVEVA Solutions Ltd, and its subsidiaries

AVEVA Solutions Ltd, High Cross, Madingley Road, Cambridge, CB3 0HB, United Kingdom

Trademarks

AVEVA and Tribon are registered trademarks of AVEVA Solutions Ltd or its subsidiaries. Unauthorised

use of the AVEVA or Tribon trademarks is strictly forbidden.

AVEVA product names are trademarks or registered trademarks of AVEVA Solutions Ltd or itssubsidiaries, registered in the UK, Europe and other countries (worldwide).

The copyright, trade mark rights, or other intellectual property rights in any other product, its name orlogo belongs to its respective owner.

AVEVA Solut ions Ltd


3/18

Laser Model Interface Reference Manual

Contents Page

12.0i


Laser Model Interface

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1

Who Should Use This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1

How the Guide is Organised . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1

Product Compatibi li ty . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1

Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1:1

Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:1

Driver Subcommand - Accessing Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:1

Querying Driver Att ributes and Capabilit ies . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:1

Opening and Accessing Laser Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:3

Creating an External Geometry Element . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:3

Importing Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:4

Using the Vendors Model Browse Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:5Driver Extensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:5

Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:6

Manipulating Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:6

Clash Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:7

Quick Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A:1


4/18

12.0ii



5/18


Introduction

12.01:1

1 Introduction

The Laser Model Interface (LMI) is a separately licensed module for the AVEVA Plant andAVEVA Marine products. Used in conjunction with a supported Laser Model serverapplication, it allows:

the display of Laser Models within PDMS/Outfitting, combined with normal PDMS/Outfitting geometry

clashing calculations between Laser Models and PDMS/Outfitting geometry, anddisplay of the resulting clashing regions

picking of points within Laser Models, and creating tie-in points between LaserModels and geometry

implementation of third party defined extended functionality.

1.1 Who Should Use This Guide

This guide is intended for end users of the Laser Model Interface. It describes thecommands used for accessing Laser Model functionality. It is also intended for IT staff who

are implementing extended Laser Model functionality using PML programming.

Note: The licensing of the Laser Model Interface product is managed by AVEVAs Flexmansecurity system. A separate license key must be obtained from AVEVA for the LaserModel product.

1.2 How the Guide is Organised

Commandsdescribes the new commands within the LMI module, and extensions to existingcommands for handling Laser Models.

1.3 Product CompatibilityIn addition to the Windows operating system, other AVEVA and non-AVEVA products arerequired for the Reference Manual of Laser Model functionality.

For all users:

PDMS/Outfitting

A supported Laser Model package.

1.4 Installation

For an introductory guide and installation information, refer to the appropriate Laser Model

Server Application.


6/18

12.01:2


Introduction


7/18


Commands

12.02:1

2 Commands

All Laser Model commands use the command verb LMI. The following sections detail thevarious sub-commands available.

2.1 Driver Subcommand - Accessing DriversSeveral LMIcommands use the DRIVERsubcommand, for example:

LMI DRI VER abc| c: \ abc\ pr og. dl l | l ogi n=user QUERY API VERSI ON

The string following the driver keyword - the vendors identification string - contains betweenone and three fields separated by bar (|) characters. The fields are, i) a tag string, ii) the fullpath to the driver dynamic link library (DLL) file, and iii) the drivers connect string. Thedrivers connect string can be any string, as required by the vendor company to connect totheir driver, or it can be omitted if the driver requires no special connection information.

Once one LMI DRIVER command has been used, the string can be shortened to just the tagfor all subsequent commands, for example:

LMI DRI VER abc QUERY DRI VERVERSI ON

Or, the DRIVER subcommand can be omitted completely, in which case the command isdirected to the most recently referenced driver:

LMI QUERY DRI VERVERSI ON

2.2 Querying Driver Attributes and Capabil it ies

[ VAR {var }] LMI [ DRI / VER {st r i ng}]

Q/ UERY {API VER/ SI ON | DRI VERVER/ SI ON | BAN/ NER | LAST ERR/ ORMESSAGE | MAX/ I MUM {MOD/ ELS | VI EWS | REGI ONSOFI NT/ EREST | HI GHL/ I GHTREGI ONS | CLASHVOL/ UMES | VI EWQ/ UALI TY {I N/ SI DE | OUT/ SI DE} | VI EWP/ ORT {W/ I DTH | H/ EI GHT}} SUPP/ ORT {FBCLI P/ PI NG | RENDERFAST | LOWRESEVERYWHERE | TESTVOLUMEFAST | TESTGEOMETRYEXACT}}


8/18

12.02:2


Commands

This command connects to, and queries attributes of, the named driver. The result string isreturned in variable {var}, or if this is omitted, output in the command window.

The DRIVER {string} subcommand should be included the first time an LMI command isused for a particular driver, but need not be repeated for subsequent calls to the samedriver. See Driver Subcommand - Accessing Drivers.

The available attributes are:

{var } variable name

{st r i ng} driver name and connection details in the following format,enclosed in single quotes:

{name}[ | {path t o dl l }[ | {vendor s connectstr i ng}] ]

API VERSI ON The version string for the LMI.DRI VERVERSI ON The version string for the driver.

BANNER The driver manufacturers banner text.

LAST ERRORMESSAGE The last error message (or an empty string if no error hasoccurred).

MAXI MUM MODELS The maximum number of models that can be openedsimultaneously (range 1 - unlimited).

MAXI MUM VI EWS The maximum number of views that can be renderedefficiently (range 1 - unlimited). Note: since calls to renderviews are made sequentially, any number of views can berendered, however the rendered images are generally

cached by the vendor software for efficiency, and thiscommand returns the maximum number of views for whichthis caching is supported.

MAXI MUMREGI ONSOFI NTEREST

The maximum number of regions of interest that the driversupports (range 0 - unlimited). Regions of interest defineareas where a higher view quality may be used.

MAXI MUMHI GHLI GHTREGI ONS

The maximum number of highlighted regions that the drivercan support (range 0 - unlimited).

MAXI MUMCLASHVOLUMES

The maximum number of highlighted clash volumes that thedriver can support (range 0 - unlimited).

MAXI MUM

VI EWQUALI TY

The maximum view quality that the driver supports INSIDE

or OUTSIDE the regions of interest (range 1 or higher).MAXI MUM VI EWPORTWI DTH / HEI GHT

The maximum viewport width / height that the driversupports (range 1 - unlimited).

SUPPORTFBCLI PPI NG

Whether the driver supports front and back clipping planes(true or false).

SUPPORTRENDERFAST

Whether the driver supports fast rendering (true or false).

SUPPORTLOWRESEVERYWHERE

Whether the driver supports rendering in low resolutioneverywhere mode (true or false).


9/18


Commands

12.02:3

2.3 Opening and Accessing Laser Models

Laser models are represented in the DESI database by XGEOM (external geometry)elements. The XGEOM element records the reference strings to identify a particular lasermodel and the relevant external laser model server application which manages access tothe detailed point cloud data.

The XGEOM can be used naturally in many existing commands and GUI interactions, forexample, to add or remove point cloud models in the display list and other lists. There arealso some laser model specific commands that apply to XGEOMs. These are listed inManipulating Views.

Below the XGEOM, PDMS/Outfitting also builds up a coarse spatial occupancy map togive PDMS/Outfitting functions some guidance about the distribution of points in the pointcloud model. This map is used, for example, to determine volumetric limits for the lasermodel and to support the internal spatial map used during clash calculations. This map isbuilt up as a hierarchy of XCLTN, XCELS and XCELL elements below the XGEOM. It is notnormally necessary for users to create or access these elements directly.

There are 2 ways to create XGEOMs and the associated spatial occupancy map. You canuse the standard NEW command then generate the spatial occupancy map by command -this approach is covered in Creating an External Geometry Element. Alternatively you canuse the laser model specific import command which will create the XGEOM and the spatial

occupancy map in one go - this is described in Importing Modelsand Using the VendorsModel Browse Dialog.

2.3.1 Creating an External Geometry Element

This command creates a new XGEOM element at the current geometry level, and makes itthe current element. The current geometry level must be at or below a ZONE. The vendorsidentification string can optionally be supplied (see note below), as can the modelidentification string. These attributes can also be supplied using separate VENID andMODID commands after the XGEOM has been created.

The vendor identification string should identify the Laser Model server application where theactual point cloud data resides. The model identification string should identify a model withinthe vendors model database.

SUPPORTTESTVOLUMEFAST

Whether the driver supports a fast (but less accurate)version of volume testing for clashing.

SUPPORTTESTGEOMETRYEXACT

Whether the driver supports testing geometry for clashing atthe exact check level.


10/18

12.02:4


Commands

Once the XGEOM has been created and the attributes set, PDMS/Outfitting adds theXGEOM to the display. This happens automatically, both when the full form of the commandabove is used, and when the attributes are set individually. (It also happens if the value of an

attribute is changed.) At this point, the values of the attributes are checked for validity, andif valid, the XGEOM is made visible and the display is updated. If any attribute(s) are invalidor missing, an error condition results, and the XGEOM is not added to the display.

Note: The vendor identification string format is described in Driver Subcommand -Accessing Drivers. The VENID can be provided as either the long form of the string,specifying the path to the vendor DLL and the vendors connect string, or the shortform that includes just the tag. The former provides all the information necessary toopen the Laser Model and add the XGEOM to the display. However, it suffers thedrawback that any change to the DLL path (which may happen for example whenaccessing the database from a different node) or the vendor connect string (whichmight for example contain embedded username / password information) will causethe load to fail and the XGEOM not to be added to the display. For these reasons, the

short form of the VENID string is preferred. Note, however, that an XGEOM with theshort form VENID string can only be added to the display after another LMI DRIVER{string} command has been used with the long form string, thus setting theassociation between the tag and the other parameters for the session.

Once an XGEOM element has been created by the NEW command, the spatial occupancymap can be built using the command:

LMI REMAP

The XGEOM should be the current element when this command is used.

LMI REMAP can be re-applied if the spatial occupancy map becomes out of date, forexample if the laser model is extended with extra scans. However users of Clash Manager

should be aware that identification of clash details with the laser model relies on thepersistence of the Dabacon REFNO of the clashing XCELL elements. Re-application of theREMAP command will re-assign REFNOs and hence any related clash history will bebroken.

2.3.2 Importing Models

This command creates a new XGEOM element to represent the selected model, and opensthe model in the vendor driver.

The current element must be at or below a ZONE: if at a ZONE, the XGEOM will be createdas the first element in the list; if below a ZONE the XGEOM will be created as the next

element in the ZONE list. The new XGEOM becomes the current element.

LMI [ DRI / VER {st r i ng}] I MPORT {mname}

{st r i ng} driver name and connection details in the following format, enclosed insingle quotes:{name} string}]]

{name}[ | {pat h t o dl l }[ | {vendor s connect st r i ng}] ]

{mname} model name enclosed in single quotes


11/18


Commands

12.02:5

After creating the XGEOM, the following actions occur:

the XGEOMs VENID attribute is set to {string}

the XGEOMs MODID attribute is set to the vendor defined model name (i.e. the namenecessary to access the model in the vendors database without using the browsefunction)

the XGEOMs DATIM attribute is set to the current time

the model is opened in the vendor driver

the spatial map is calculated, and stored below the XGEOM (as XCLTN, XCELS andXCELL elements).

2.3.3 Using the Vendors Model Browse Dialog

The BROWSE form of the IMPORT command (if the vendor supports it) causes thevendors model browse dialog to be displayed, and allows the user to select a model forimport. Once the model is selected and the dialog closed, the import action is exactly the

same as the IMPORT {mname} form of the command described in the section above.

Note: Once the model has been imported with BROWSE, the MODID attribute can bequeried to discover the model name.

2.4 Driver Extensions

This command executes the driver specific command in the named driver. The result string(if any) is returned in variable {var}, or if this is omitted, output in the command window.

LMI [ DRI / VER {st r i ng}] I MPORT BRO/ WSE

{st r i ng} driver name and connection details in the following format, enclosed insingle quotes:

{name}[ | {pat h t o dl l }[ | {vendor s connect st r i ng}] ]

[ VAR {var }] LMI [ DRI / VER {st r i ng}] EXT/ ENSI ON {command}


{st r i ng} driver name and connection details in the following format, enclosed insingle quotes:

{name}[ | {path t o dl l }[ | {vendor s connect st r i ng}] ]

{command} command string enclosed in single quotes


12/18

12.02:6


Commands

2.5 Licensing

This command retrieves the license status of the LMI module. The result string is returned invariable {var}, or if omitted, output in the command window.

2.6 Manipulating ViewsThis section is provisional, as the syntax and functionality of the LMI VIEW commands hasnot yet been finalised. It is possible that these commands may change, or be completelyremoved at a later date, as views are not LMI specific, and an existing syntax exists withinPML to access and manipulate views and view parameters.

This command outputs a summary of the LMI parameters associated with the selected view(or all views, if none selected).

This command sets the view quality inside / outside the regions of interest within the viewspecified (or all views if none specified). The % quality specified is translated as near aspossible to a view quality supported by each vendors software. Where a precise match isnot possible, the view quality is rounded up.

[ VAR {var}] LMI LI C/ ENCED


LMI VI EW DETAI LS

LMI VI EWSET VI EWQ/ UALI TY {i n} {out}

{i n} the view quality inside the regions of interest (%)

{out } the view quality outside the regions of interest (%)

LMI VI EWADD {t ype}

X/ LENGTH {l en} Y/ LENGTH {l en} Z/ LENGTH {l en}AT E/ AST {pos} N/ ORTH {pos} U/ P {pos}

LMI VI EWREM/ OVE {t ype}

VAR {var} LMI VI EW{t ype} {COU/ NT | {n}}

{vi ew} view number

{type} one of:

REGIONSOFI/NTEREST, HIGHL/IGHTREGIONS


13/18


Commands

12.02:7

These commands create, delete and query regions of the type specified, within the viewspecified (or all views if none specified).

The ADD command adds a region, preserving any regions of the same type alreadypresent. The REMOVE command removes all regions of the type specified.

The COUNT subcommand returns the number of regions of the type specified. The {n}subcommand returns the bounds (volume) of the n-th region.

2.7 Clash Testing

This section provides addition options for detecting and displaying clashes betweenprimitives and the external laser model. Before the XGEOM element can be clashed thespatial occupancy map must be up to date, once the map has been built there generally isno need to regenerate it.

DESCLASH LMI [TEST {opt ion} | [DISP/LAY {disp lay}] EXIT

{option} one of:CELLS, EXACT/GEOMETRY{display} one of:CELLS, EXPAND/CELLS {off}, TIGHTBOXES, EXACT/GEOMETRY

The TEST command determines the level the clash test will take place, if CELLS theprimitive will test for clash with the spatial occupancy map only (default). Using theEXACTGEOMETRY option the primitive will be clashed against the spatial occupancy map,if there is a clash then the primitive will be clashed against the laser external model. The useof EXACTGEOMETRY clash will produce a more accurate result however it will take longerto process the data.

The DISPLAY command determines the manner in which the graphical feedback of theclash will be displayed. By default the CELLS display option will be used: if there is a clashthen all points within the spatial occupancy cell will be highlighted as clashing. TheEXPANDCELLS option will highlight points within the spatial occupancy cell expanded bythe additional offset as clashing. The TIGHTBOXES option will highlight points within theoverlap between the spatial occupancy cell and the containment box for the primitive. TheEXACTGEOMETRY option will only highlight the points of the laser model that clash withthe primitive itself: as a result the clash display will normally be obscured by the primitive.

The use of the EXACTGEOMETRY display option may reduce the performance of thedisplay (or initial update of the display).

{l en} a length value

{pos} a position value

{n} index of the item in the list of {type} items


14/18

12.02:8


Commands


15/18


Quick Reference

12.0A:1

A Quick Reference

NEWXGEOM [ / {name}] [ VENI D {i d}] [ MODI D {mi d}]

LMI [ DRI / VER {st r i ng}] I MPORT {BRO/ WSE | {mname}}

LMI REMAP

[ VAR {var }] LMI [ DRI / VER {st r i ng}] Q/ UERY {API VER/ SI ON | DRI VERVER/ SI ON | BAN/ NER | LAST ERR/ ORMESSAGE | MAX/ I MUM {MOD/ ELS | VI EWS | REGI ONSOFI NT/ EREST | HI GHL/ I GHTREGI ONS | CLASHVOL/ UMES |

VI EWQ/ UALI TY {I N/ SI DE | OUT/ SI DE} | VI EWP/ ORT {W/ I DTH | H/ EI GHT}} SUPP/ ORT {FBCLI P/ PI NG | RENDERFAST | LOWRESEVERYWHERE | TESTVOLUMEFAST | TESTGEOMETRYEXACT}}

[ VAR {var }] LMI LI C/ ENCED

[ VAR {var}] LMI [ DRI / VER {st r i ng}] EXT/ ENSI ON {command}

LMI VI EWDETAI LS

LMI VI EWSET VI EWQ/ UALI TY {i n} {out}

LMI VI EWADD {t ype} X/ LENGTH {l en} Y/ LENGTH {l en} Z/ LENGTH {l en} AT E/ AST {pos} N/ ORTH {pos} U/ P {pos}

LMI VI EWREM/ OVE {t ype}

VAR {var } LMI VI EW{type} {COU/ NT | {i dx}}


16/18

12.0A:2


Quick Reference


17/18

Index

12.0Index page 1


Symbols

{in}. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:6{len}. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:7{n} . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:7{out}. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:6{pos} . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:7{type}. . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:6{view} . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:6

A

Accessing Laser Models . . . . . . . . . . . . . 2:3ADD . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:7APIVERSION . . . . . . . . . . . . . . . . . . . . . 2:2

B

BANNER . . . . . . . . . . . . . . . . . . . . . . . . . 2:2

C

CELLS. . . . . . . . . . . . . . . . . . . . . . . . . . . 2:7Clash Testing . . . . . . . . . . . . . . . . . . . . . 2:7CLASHVOLUMES . . . . . . . . . . . . . . . . . 2:2Commands . . . . . . . . . . . . . . . . . . . . . . . 2:1COUNT . . . . . . . . . . . . . . . . . . . . . . . . . . 2:7

D

DESI . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:3DISPLAY. . . . . . . . . . . . . . . . . . . . . . . . . 2:7Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:1Driver Attributes . . . . . . . . . . . . . . . . . . . 2:1

Driver Extensions . . . . . . . . . . . . . . . . . . 2:5

DRIVERVERSION . . . . . . . . . . . . . . . . . 2:2

E

EXACTGEOMETRY. . . . . . . . . . . . . . . . 2:7EXPANDCELLS . . . . . . . . . . . . . . . . . . . 2:7External Geometry Element . . . . . . . . . . 2:3

FFBCLIPPING . . . . . . . . . . . . . . . . . . . . . 2:2Flexman . . . . . . . . . . . . . . . . . . . . . . . . . 1:1

H

HIGHLIGHTREGIONS . . . . . . . . . . . . . . 2:2

I

Importing Models . . . . . . . . . . . . . . . . . . 2:4Installation . . . . . . . . . . . . . . . . . . . . . . . 1:1

Introduction

. . . . . . . . . . . . . . . . . . . . . . 1:1

L

LAST ERRORMESSAGE . . . . . . . . . . . 2:2Licensing . . . . . . . . . . . . . . . . . . . . . . . . 2:6LMI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:1LOWRESEVERYWHERE . . . . . . . . . . . 2:2

M

Manipulating Views . . . . . . . . . . . . . . . . 2:6MAXIMUM MODELS . . . . . . . . . . . . . . . 2:2

MAXIMUM VIEWPORT . . . . . . . . . . . . . 2:2


18/18


MAXIMUM VIEWS . . . . . . . . . . . . . . . . . 2:2MODID . . . . . . . . . . . . . . . . . . . . . . 2:3, 2:5

O

Opening . . . . . . . . . . . . . . . . . . . . . . . . . 2:3

R

REGIONSOFINTEREST. . . . . . . . . . . . . 2:2REMAP . . . . . . . . . . . . . . . . . . . . . . . . . . 2:4RENDERFAST . . . . . . . . . . . . . . . . . . . . 2:2

T

TEST. . . . . . . . . . . . . . . . . . . . . . . . . . . . 2:7

TESTGEOMETRYEXACT . . . . . . . . . . . 2:3TESTVOLUMEFAST . . . . . . . . . . . . . . . 2:3TIGHTBOXES. . . . . . . . . . . . . . . . . . . . . 2:7

V

VENID . . . . . . . . . . . . . . . . . . . . . . . 2:3, 2:4VIEWQUALITY . . . . . . . . . . . . . . . . . . . . 2:2

X

XCELL. . . . . . . . . . . . . . . . . . . . . . . . . . . 2:3

XCELS

. . . . . . . . . . . . . . . . . . . . . . . . . . 2:3XCLTN . . . . . . . . . . . . . . . . . . . . . . . . . . 2:3XGEOM. . . . . . . . . . . . . . . . . . . . . . 2:3, 2:7

Documents

Laser Model Interface Reference Manual