The document provides instructions for configuring DeltaV Simulate to communicate with MiMiC via OPC. It involves setting up user permissions on the DeltaV workstation, configuring Windows network security settings, installing and configuring OPC Remote software, and setting up OPC services with the appropriate user account. Troubleshooting tips are provided to check communications if issues arise.
The document provides instructions for configuring DeltaV Simulate to communicate with MiMiC via OPC. It involves setting up user permissions on the DeltaV workstation, configuring Windows network security settings, installing and configuring OPC Remote software, and setting up OPC services with the appropriate user account. Troubleshooting tips are provided to check communications if issues arise.
The document provides instructions for configuring DeltaV Simulate to communicate with MiMiC via OPC. It involves setting up user permissions on the DeltaV workstation, configuring Windows network security settings, installing and configuring OPC Remote software, and setting up OPC services with the appropriate user account. Troubleshooting tips are provided to check communications if issues arise.
The document provides instructions for configuring DeltaV Simulate to communicate with MiMiC via OPC. It involves setting up user permissions on the DeltaV workstation, configuring Windows network security settings, installing and configuring OPC Remote software, and setting up OPC services with the appropriate user account. Troubleshooting tips are provided to check communications if issues arise.
Copyright:
Attribution Non-Commercial (BY-NC)
Available Formats
Download as PDF, TXT or read online from Scribd
Download as pdf or txt
You are on page 1/ 11
15/08/12
OPC setup for MiMiC
DeltaV Simulate OPC Setup Guide
This guide will walk you through the configuration changes necessary to communicate with DeltaV Simulate via OPC. This will require administrator privileges to change the Windows DCOM settings and to install the necessary applications.
DeltaV Workstation Configuration
In order to use OPC, several configuration changes must be made to Windows XP on the DeltaV workstation. These changes are necessary to enable Microsofts Distribute Component Object Model technology on a nonDeltaV node. Note that these changes may alter the security of your DeltaV network. Consult a network or system administrator if there are critical network security issues involved in the necessary changes.
User Configuration The first change that must be made to the DeltaV workstation is to add a user that will enable the MiMiC client to access the DeltaV OPC Server information. Follow the steps below to assign the user-rights to the DeltaV workstation: 1. Login to the DeltaV workstation using an account that has Administrator privileges. 2. Open the DeltaV User Manager application.
3. Using the name and password of the user that will be running the MiMiC client. If you plan on using the DeltaVAdmin account please skip to step 9. Otherwise, make sure that the username and passwords match those on the MiMiC client (and DeltaV) and that the users Account Type has DeltaV Administrator, Windows Desktop Access, and Windows Administrator (at a minimum) are checked:
4. Click on the Advanced tab and check the Password Never Expires box. 5. Click on the Groups tab and grant the new user keys for all of the non-user defined keys as shown in the following: www.mynah.com/webhelp_output/Content/guides/howto_dvopc.htm 2/11
15/08/12
OPC setup for MiMiC
6. Click on the Keys tab and grant the new user keys for all of the non-user defined keys as well as the Groups tab as shown in the following:
7. Follow these steps for each user that will need to access the OPC Server remotely. 8. When the DeltaV User Manager closes, it will warn: the workstation needs to be re-downloaded and the current user will have to log out. Download the DeltaV workstation and re-log onto DeltaV.
This step must be done on the MiMiC and DeltaV workstation(s). 9. From Windows explorer select Tools Folder Options:
10. Select the View Tab and de-select the Use Simple File Sharing option, as shown below.
This allows remote users to be properly identified to the system. With simple file sharing enabled, all remote users log in as guest, which would prevent proper operation of OPC.
When MiMiC is on a separate computer from DeltaV, then OPC Remote is required to be installed. This can be found on either Disk 2 or Disk 4 (depending on DeltaV version). 11. Enter in the name of the Pro or App station that contains the OPC Licensing
12. Next, enter in the DeltaVAdmin password. This password needs to be the same as the DeltaVAdmin password on every DeltaV station. If the user does not know what his DeltaV password is, then the DeltaVadmin password needs to be reset to the same thing on every DeltaV station by running Servpwd. Note: This does not mean you have to use the DeltaVAdmin account on the MiMiC and DeltaV machines, just the DeltaVAdmin account passwords need to match on all machines.
13. Click Start -> Run, then type the command Service.msc, to start the windows services:
14. Right-click on MiMiC OPC Bridge and select Properties:
15. Then on the Log On Tab select This account and type in the Username and password of the account youre currently using for OPC communications, we recommend using the DeltaVAdmin. This must match the account setup in Step 3 on the DeltaV workstation.
20. Make sure the Correct node and the OPC driver is selected. IO Definitions created by the DeltaV FHX Utility will be of the form ControllerName_Driver_IODEF, where ControllerName and Driver are replaced with the correct values.
21. Select the Automatically Initiate Communications When Started? and Log Errors and verify the correct OPC Server. Then Select OK. The "Log Errors" checkbox instructs MiMiC Diagnostics to display any error messages created while the OPC driver is communicating. The Automatically Initiate Communications When Started?" checkbox instructs the simulation engine to begin communications using the specified IO Definition.
22. If everything is setup correctly, the window you see should be similar to the one below. This dialog lists the objects which were downloaded to the simulation engine. If any problems were encountered during the download, they would be indicated here.
If MiMiC cannot read values from DeltaV; can not read outputs when they are written from DeltaV or if an error is given in MiMiC Diagnostics then the following needs to be checked: Map a drive from MiMiC to DeltaV (C:\, D:\ or DVDATA drives). Then map a drive from DeltaV to MiMiC. Verify that modules are assigned to the correct DeltaV node, verify that alarms and events have been assigned to this node too. Verify that the DeltaVAdmin passwords match on all PCs and that the same username and password is being used to log onto all DeltaV and MiMiC PCs. Verify that OPCwatchit, run from the MiMiC computer, can read items from DeltaV. If OPCwatchit fails (server_init failed) then the DeltaV service needs to be stopped and C:\deltav\bin\regall.exe /register needs to be executed and DeltaVAdmin password needs to be re-entered. Verify that the user has logged into FlexLock in DeltaV for any node MiMiC needs to be communicating to. How is the network set up? Verify MiMiC can ping the DeltaV machine and vice-versa. Is this PC on a domain? If the PC is on a domain, try logging onto the local PC and not the domain. Also try moving the PC to a workgroup.
