An OPC client attempts to connect to the GagePort Mitutoyo OPC Server. If the OPC server process does not exist, COM/DCOM services attempt to activate it. Upon successful activation of the OPC server, the OPC client begins interacting with the OPC server to create server, group, and item objects. If the OPC server object is already active, COM/DCOM returns a reference to the OPC server process. Only one OPC server process can exist on a single computer node at a time.
When the last OPC client disconnects from the OPC server, the OPC server will automatically terminate.
In the event that an OPC client does not disconnect gracefully, COM/DCOM garbage collection algorithms will automatically clean the OPC client references (this can take several minutes). Once the references are cleaned up, the OPC server will terminate.
When the GagePort Mitutoyo OPC Server is activated by COM or DCOM, it runs as a resident process that does not interact with the screen. When it is launched by the user (by double clicking on the EXE or shortcut), it runs in interactive mode, providing a User Interface on the screen.
The GagePort Mitutoyo OPC Server must be configured prior to being activated by an OPC client. The server must first be run interactively, the serial ports configured, and the configuration saved to disk (with File>Save As) so the server will know what hardware is attached prior to being activated by an OPC client. During the File>Save operation, the server will prompt the user (yes or no) whether to use this configuration when activated by an OPC client. The user must answer Yes at least once, so a valid configuration file is stored in the registry for use when the server is started by an OPC client.
The Gageport Mitutoyo OPC does not support polled guages. It only works with unsolicited gauges that send their data directly to the serial ports on the server node.
About the GagePort Mitutoyo OPC Server.