Sorry forgot about the problem Posted 18 Dec You need to be a member in order to leave a comment. Register a new account. With this in mind, Ci Technologies suggest that an OPC Server should handle the case where an access path is not specified. 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.
|Date Added:||26 April 2008|
|File Size:||14.79 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
As I said earlier these settings worked for OUR project in version 6. While the exception reporting nature between the Citect OPC Client and the Server reduces or negates this concern at this point, performance may still be degraded at two places: I am listing the configurations, hope those who are familiar can verify it for me thanks.
Citect does not allow the cliejt to specify access paths for items.
Posted 18 Dec It can automatically scan and find devices if you want it to, and that takes a lot of the configuration out of the way. Posted 24 Dec Hi All, I am new to Citect 7.
Citect SCADA OPC-UA Client Driver – now available!
It’s available as a free 30 day demo here: This will signifcantly load the network and have a corresponding affect on the performance of the Citect system as a whole. How does this affect the performance in Citect? Share this post Link to post Share on other clkent. OPC Explorer is freely downloadable http: Sorry forgot about the problem Question What is OPC?
By using tag names to access the value of a tag, Citect cannot logically ‘block’ several requests into one request and so the overhead cannot be eliminated.
Sign In Sign Citcet. This measured time is usually insignificant compared with the actual response time from the PLC. OPC Explorer is not a replacement for Citect, it’s just used for testing.
Question Do the ‘Response times’ shown in the Citect kernel eg. 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.
Question The OPC specification uses tag names rather than physical addressing to request the value of a tag. This is because Citect has no control over whether the OPC Server optimises requests to the device in the most efficient manner.
As Citect cannot block individual requests when using tag names to access the tags values, each Citect Client will request each tag individually across the network.
That the OPC Server can connect to the end devices.
Citect OPC Client Connecting
Then check the Citect. See this web site for further information: Wow, that’s an ambiguous error.
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. Posted 19 Dec Sign in Already have an account? You could use it to connect to the OPC Server and verify: I ‘m sorry this is a bit vague but I havn’t used version 7 and I believe that it is very different as far as OPC is concerned to previous versions.
I am not familiar with ver 7. Register a new account.