Hello everyone, I am currently facing an issue with my Cimplicity v10 project that has around 7 to 8k tags communicating with an AB PLC through OPC and Rslinx Classic. The problem arises when I start adding more tags to the project, as Cimplicity is unable to read them from the PLC. The tags in my project involve various datatypes such as BOOL, DINT, INT, and REAL. I am wondering if there is a limit on the number of tags allowed for communication through the OPC driver in Cimplicity, as my project functions properly when I reduce the number of tags. Can anyone provide insight on this issue?
Hello Eugene, it's important to note that there is a limit to the number of points you can accumulate. I recommend checking your license to see what the points limit is. I once encountered this issue myself and reached the limit, but was able to resolve it by upgrading my license.
Hello JunQ, thank you for your response. I am currently encountering a recurring issue, as depicted in the attachment provided. The error I am facing is COPCCallback::OnDataChange, which occurs when Cimplicity is browsing tags from my PLC and subsequently marks it as disconnected. Despite searching the manual for a resolution, I have been unable to find any information. Can you provide insight into the meaning of this error?
Hello, I'm experiencing an OPC callback failure, which is a new issue for me. It's important to review the OPC configuration on both the server and Cimplicity. When it comes to OPC communication, it is recommended to use either unsolicited or unsolicited on change points update criteria.
Answer: 1. Is there a limit on the number of tags allowed for communication through the OPC driver in Cimplicity v10? - Yes, there may be a limit on the number of tags that can be communicated through the OPC driver in Cimplicity v10, as increasing the number of tags can lead to communication issues with the PLC.
Answer: - To troubleshoot the tag limit issue, you can try reducing the number of tags in the project to see if communication improves. You can also check for any specific limitations or restrictions mentioned in the Cimplicity v10 documentation regarding tag communication.
Answer: - Common datatypes used in tags for communication with an AB PLC through OPC in Cimplicity v10 include BOOL, DINT, INT, and REAL, among others.
Answer: - Best practices for optimizing tag communication may include organizing tags efficiently, monitoring network traffic, checking for any OPC server limitations, and ensuring compatibility between Cimplicity v10 and the PLC.
Answer: - Ensuring