Creating an External Geometry Element

Laser Reference Manual

Commands : Opening and Accessing Laser Models : Creating an External Geometry Element

This command creates a new XGEOM element at the current geometry level, and makes it the current element. The current geometry level must be at or below a ZONE. The vendor’s identification string can optionally be supplied (see note below), as can the model identification string. These attributes can also be supplied using separate VENID and MODID commands after the XGEOM has been created.

The vendor identification string should identify the Laser Model server application where the actual point cloud data resides. The model identification string should identify a model within the vendor’s model database.

Once the XGEOM has been created and the attributes set, AVEVA E3D™/Outfitting adds the XGEOM to the display. This happens automatically, both when the full form of the command above 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, and if valid, the XGEOM is made visible and the display is updated. If any attribute(s) are invalid or 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 vendor’s connect string, or the short form that includes just the tag. The former provides all the information necessary to open the Laser Model and add the XGEOM to the display. However, it suffers the drawback that any change to the DLL path (which may happen for example when accessing the database from a different node) or the vendor connect string (which might for example contain embedded username / password information) will cause the 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 the short 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 the association between the tag and the other parameters for the session.

Once an XGEOM element has been created by the NEW command, the spatial occupancy map 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, for example 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 the persistence of the Dabacon REFNO of the clashing XCELL elements. Re-application of the REMAP command will re-assign REFNOs and hence any related clash history will be broken.