Scribd
Upload
26 views4 pages

OPC Troubleshooting

Uploaded by

Nazmul Hasan
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
26 views4 pages

OPC Troubleshooting

Uploaded by

Nazmul Hasan
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 4

OPC communication troubleshooting

● username / password of the user running the framework on the HLC server should exist also
on the OPC host
● for troubleshooting, username / password of the user of the OPC host running the OPC server
can be set up on the HLC server and checked if the OPC communication is working
● network configuration likely to affect communication
○ HLC and OPC machines on the same subnet?
○ firewalls on either machine activated? >> Firewalls need to be deactivated
○ machines in a domain or workgroup configuration?

● OPC expert (free tool) should be used for troubleshooting

OPC Expert can be downloaded (also) from the KM/MM hub:


https://sites.google.com/a/holcim.com/cp-kilnmaster-and-millmaster/kilnmaster/km-2-0-
labview/tools

There are several tutorials on how to use OPC Expert available on youtube. See e.g. here:
○ OPC Expert Getting Started
https://www.youtube.com/watch?v=BCYpMJwmUlI
> General introduction about how to use OPC Expert.

○ OPC Expert Troubleshooting


https://www.youtube.com/watch?v=vhXo7Nlcdu8
> More detailed step-by-step guide on how to use OPC Expert for troubleshooting.

In order to run OPC Expert, Microsoft .Net 3.5 Framework has to be installed on the
respective operating system first (i.e. for the troubleshooting as described in the above link on
both the OPC host and the HLC server

● For remote support, provide access to the OPC server (i.e. possibility to connect via RDC either
directly or from the HLC server), submit the following information to rCIP/cCIP:
○ IP address of the OPC host
○ OPC server name
○ username and the password (of the user running the OPC server)
○ make sure RDC is activated on the OPC server

Alternatives

● IO server setup in DSM on HLC server


especially if OPC communication is working with other clients (e.g. OPC Quick Client), but not
with HLC framework or OPC-test tool
● Installation of NI runtime in OPC machine and IO server setup in DSM on OPC machine, then
access from framework to IO server via LabVIEW PSP protocol
> additional NI DSC runtime license required for the OPC server
● OPC tunneller
> potential issue if new tag of the OPC tunneler comes with a question mark (“?”), as this is
interpreted by the datasocket to pass certain parameters
● OPC expert (cf. setup in Ada, see below)

Additional information
OPC expert (alternative)
"Here is some additional info on their specific installation: OPC over DCOM to the HLC projects
does not seem to work directly. This is due to some sort of special condition that Labview requires
for OPC communication. We could not resolve it, so we purchased OPC Expert ($995), which
makes the remote OPC servers available on the local machine, without using a tunneller. It does
not require any additional software to be installed on the OPC servers, as would have been
required with a Matrikon tunnel.
OPC Expert is installed as a service running under the kmadmin user and licensed for the C drive
of the kilnmaster server.

The dedicated server user has been added to administrators group on the OPC server"

NI Networking Error Codes


● http://zone.ni.com/reference/en-XX/help/371361H-01/lverror/tcp_and_udp_error_codes/

Exshaw (Shaun Bennett):


What I ended up doing was installing iFIX on the HLC [server]...I doubt that's the method we want to use
long term. I had a spare read/write license so it made sense. This keeps the OPC connection local to the
HLC and iFIX takes care of communicating natively to the databases.

Comment Ariel Weber


The magic bullet to getting these OPC servers to communicate has been starting the Remote Registry
Service.
Labview Datasocket seems to require this to be running on both computers (HLC Server and the OPC
server it connects to). Might be worth a try in case of other plants having problems with connecting.
As for the remote registry service...the other part of this could require registry changes.

Using regedt32.exe (apparently very important), ensure these keys allow the user Everyone read/write
permissions.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurePipeServers
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurePipeServers\winreg
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurePipeServers\winreg\
AllowedExactPaths
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurePipeServers\winreg\AllowedPaths

also change any other available "controlsets"

HKEY_LOCAL_MACHINE\SYSTEM\ControlSetXXX\Control\SecurePipeServers
HKEY_LOCAL_MACHINE\SYSTEM\ControlSetXXX\Control\SecurePipeServers\winreg
HKEY_LOCAL_MACHINE\SYSTEM\ControlSetXXX\Control\SecurePipeServers\winreg\AllowedExactPaths
HKEY_LOCAL_MACHINE\SYSTEM\ControlSetXXX\Control\SecurePipeServers\winreg\AllowedPaths

You might also like