See KB Article Q I am not familiar with ver 7. Register a new account. Share this post Link to post Share on other sites. You need to be a member in order to leave a comment. They may not even be available or may not be required in version 7.

Uploader: Mezigore
Date Added: 27 July 2009
File Size: 19.9 Mb
Operating Systems: Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X
Downloads: 76299
Price: Free* [*Free Regsitration Required]

Sign In Sign Up. Create an account or sign in to comment You need to be a member in order to leave a comment Create an account Sign up for a new account in our community. Question The OPC specification uses tag names rather than physical addressing to request the value of a tag. Question What is OPC? You could use it to connect to the OPC Server and verify: By using tag names to access xlient value of a tag, Citect cannot logically ‘block’ several requests into one request and so the overhead cannot be eliminated.

Citect SCADA OPC-UA Client Driver – now available!

OPC Explorer is not a replacement for Citect, it’s just used for testing. Sign up for a op account in our community. I am not sure if i got all the configurations right for my citect portion. Question I have a customer who tries to connect to an OPC Server and they always get the error.

Posted 24 Dec See KB Article Q I am listing the configurations, hope those who are familiar can verify it for me thanks. It can automatically scan and find devices if you want it to, and that takes a lot of the configuration out of the way. How does this affect the performance in Citect?


This cihect time is usually insignificant compared with the actual response time from the PLC. It may be that an OPC Server allows items to be specified in a format similar to the native addressing format of the device, though this is not necessarily the case.

Wow, that’s an ambiguous error. This is because each request has a specific overhead in time independent of how many tags are being requested, so by making one larger request instead of many smaller requests reduces the average cittect per tag.

Citect OPC Client Connecting

The OPC specification isn’t exactly clear as to whether it is legal for the OPC Server calls to fail if an access path is not specified, but it does go as far as saying that by “convention” a server should select an access path if one is not provided. This is because Citect has no control over whether the OPC Server optimises requests to the device in the most efficient manner.

Answer When Citect reads tags from a PLC, it is sometimes quicker to request a block of tags which includes several of those needed by Citect. That ctiect OPC Server can connect to the end devices. You need to be a member in order to leave a comment. Started by jaxrpc18 Dec With this in mind, Ci Technologies suggest that an OPC Server should handle the case where an access path is not specified.


How to connect an OPC client to your multi-cluster SCADA project

Then check the Citect. Answer The Access Path is a server specific option that is intended to allow the client to provide a ‘recommendation’ to the server regarding how to get to the data. This will signifcantly load the network and have a corresponding affect on the performance of the Citect system as a whole.

It’s available as a free 30 day demo here: We have a large project in version 6. Is there any possibility to use the Access path in Citect? Register a new account. Question Do the ‘Response times’ shown in the Citect kernel eg. That your tag syntax is correct Note: Share cliet post Link to post Share on other sites.