Converting from the Tech80 to the Manual CMM Interface

When you convert from the Tech80 interface to the Manual CMM interface, you must do the following:

Add the ROY-I-MANCMM PCD_Interface.ManualCmm option to your LMS license.

You can leave the Tech80 ROY code option in your license for compatibility with older versions if required.

Set your Portlock for the Online:ManualCMM option.

Portlock supports either an individual interface, or you can program it for All Interfaces.

The All Interfaces option requires Customer Relations Group (CRG) approval. It is required if you want to keep compatibility with older versions of the Tech80 interface.

The installer manages copying and renaming the required dll files, if you include both interfaces in your license, or you have the All Interfaces option set in your Portlock.

When you have multiple interfaces, or you have the All Interfaces option set on your license, service pack updates do not install either of these dll files

* The "xxx" denotes the language code for each language-specific dll file. The number of languages you included when you installed the interface is the number versions of this dll file.

Setting to update are bolded:

<GMS>
    <!--Server listens on this TCP port-->
    <TCPPortNumber>1390</TCPPortNumber>
    <!-- HIDE or SHOW GMServer window -->
    <WINDOW_HIDE_SHOW>SHOW</WINDOW_HIDE_SHOW>
    <!--POLL_TIME poll time of the card (default 250ms)-->
    <POLL_TIME>20</POLL_TIME>
    <HitBeepFrequency>750</HitBeepFrequency>
    <HitBeepDurationMS>300</HitBeepDurationMS>
    <!-- <DEBUG>gm_debug.txt</DEBUG> -->

Set the WINDOW_HIDE_SHOW option to SHOW to set the visibility of the GMServer.exe.

Set the HitBeepFrequency option to 750 or the frequency value of your choice.

The sounds are set to Default in the computer's Settings app so they work within Windows as shown:

In the Interfaces section, locate the Simulator Interface section and add comment delimiters.

Surround the Simulator interface section with comment tags (<! -- -->) as highlighted:

<INTERFACES>
    <!-- INTERFACE SIMULATOR -->
    <!--<Interface>
        <Type>SIMULATOR</Type>
        <Config>Simulator.XML</Config>
        <Dll>GmsSimulator.dll</Dll>
        <Axis number="0">X</Axis>
        <Axis number="1">Y</Axis>
        <Axis number="2">Z</Axis>
        <Axis number="3">W</Axis>
    </Interface>-->

Remove the comment tags from around the XNPCI interface section:

    <!-- INTERFACE XNPCI-->
    <Interface>
        <Type>XNPCI</Type>
        <Config>GMSXNPCI.XML</Config>
        <Dll>XnPCIWrapper.dll</Dll>
        <Axis number="0">X</Axis>
        <Axis number="1">Y</Axis>
        <Axis number="2">Z</Axis>
        <Axis number="3">W</Axis>
    </Interface>

The CSI setting is typically set to 25000 unless the machine has different scales. You can use the entries in the Settings Editor as a reference.

<GmsXnPCI>
    <Card number="0">
        <!-- Scale factor for X axis --> -->
        <X_COUNTS_PER_MM>100000</X_COUNTS_PER_MM>
        <!-- Scale factor for Y axis -->
        <Y_COUNTS_PER_MM>100000</Y_COUNTS_PER_MM>
        <!-- Scale factor for Z axis -->
        <Z_COUNTS_PER_MM>200000</Z_COUNTS_PER_MM>
        <!-- Defines direction of counters for X axis (positive or negative) -->
        <XnCOUNTERDirX>1</XnCOUNTERDirX>
        <!-- Defines direction of counters for Y axis (positive or negative) -->
        <XnCOUNTERDirY>1</XnCOUNTERDirY>
        <!-- Defines direction of counters for Z axis (positive or negative) -->
        <XnCOUNTERDirZ>1</XnCOUNTERDirZ>
        <!-- The following defaults are usually sufficient. Only change when advised by Tech Support. -->
        <!-- Minimum distance between two consecutive hits. Helpful if hardware has false triggers causing multiple hits to be returned on a single hit. Value is in mm. -->
        <HIT_INTERVAL>.500</HIT_INTERVAL>
        <!-- Number of Positions stored in order to properly calculate vector on a hit if not provided by hardware -->
        <POINT_HISTORY>21</POINT_HISTORY>
        <!-- Distance between Positions to store in list that is used to calculate hit vectors if not provided by hardware -->
        <POSITION_SENSITIVITY>0.021</POSITION_SENSITIVITY>
        <!-- What position in Position List to use to calculate hit vectors if not provided by hardware. This will often depend on scale update frequency. -->
        <CAL_VEC_DEPTH>7</CAL_VEC_DEPTH>
        <!-- Set to 'TRUE' if hardware causes false triggers when stationary (e.g. on locking axis) -->
        <PROBE_TRIGGER_ONLY_ON_MOVE>FALSE</PROBE_TRIGGER_ONLY_ON_MOVE>
        <!-- Minimum difference in distance between two positions used to calculate hit vectors if not provided by hardware. -->
        <VECTOR_SENSITIVITY>0.51</VECTOR_SENSITIVITY>
    </Card>
</GmsXnPCI>

Depending on how your folder permissions are set, in order to edit the files, you might need to copy them out of PC-DMIS directory into a temporary folder. When done, save the changes and then copy the files back into the PC-DMIS directory.

You only need to set this Settings Editor value for PC-DMIS version 2022.1 and later. You can use the Tech80 settings for PC-DMIS versions prior to version PC-DMIS 2021.2.