User Manual

Tips for Integrating with an OPC client
6
Possible difficulties in integrating an OPC client
74
Building Technologies A6V10062407_a_en
Fire Safety & Security Products 30.06.2013
6.4.2.1 Changing the auto start setting
1. Open the services menu (Start > Programs > Administrative Tools > Services or
Start > Settings > Control Panel > Administrative Tools > Services)
2. Select DixieSystem Supervisor.
3. Right-click DixieSystem Supervisor to display the Properties pop-up window.
4. Select the Automatic in the Startup type drop-down menu in the General tab.
Note: Once you have manually set auto start through Microsoft Services, this
behaviour should stop.
6.4.2.2 OPC Client and MK8000 are not communicating
Verify that the name of the server is SBT.MK8000.
When using OPC software to access remote OPC servers across the network, you
may encounter two DCOM security-related problems:
Browsing of OPC servers on a remote computer may fail due to the DCOM
settings.
Access to your remote OPC server may be denied due to the settings of DCOM.
Machine set-up tips:
Both Client and Server machines should be within the same network Domain or
Workgroup.
On a workgroup network all users who will have access to the OPC server must
belong to this workgroup.
On a workgroup network, on the servers and clients an account with the same
username/password combination must be created.
Check DCOM settings according to the next section.
6.4.2.3 Modifying DCOM settings
OPC security is based on the Microsoft Distributed Component Object Model (DCOM),
which may affect access to all DCOM-based Windows applications. Therefore, the
default security settings that you select for the OPC server, FEP, and Client machines
will affect all DCOM-based applications, regardless of whether they are part of OPC or
not.
Setting up a DCOM connection between two computers means setting up the stations
so that they have permission to access each other. This is a two-way street. The client
must have permissions to access the machine with the OPC server and vice versa. If
you don't have permissions set both ways, then the machines will not communicate
correctly. There are three major types of permissions:
Access
Launch
Configuration