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.
It sounds like you might indeed be nearing the tag limit for the OPC server, especially considering the various data types you're using. Cimplicity, to my knowledge, doesn't impose a limit on the tags; rather, it depends on the capacity of your OPC server. You might want to check the documentation of your OPC server to verify its tag limit. Another workaround could be optimizing your tag usage by consolidating related data into arrays or structures, if possible. This could potentially reduce your tag count without losing any necessary data.
Hey there, I've experienced a similar issue with Cimplicity in the past. As far as I'm aware, there's not an absolute limit on tags, but practicality often imposes one. The OPC server might become overwhelmed with too many tags, leading to lag or failure to read new ones. One thing I found useful was to ensure that all unused tags were deleted or disabled, and I also started grouping my tags more efficiently. Reducing tag updates where possible helped as well. Make sure your Rslinx is properly sized too, as it also has its own limitations. You can also try breaking your project into smaller, more manageable pieces if possible.
That's an interesting issue you're facing. There could be several factors contributing to your problem, but I suspect that it may be related to the resource allocation for your Cimplicity project. While I'm not entirely sure of the precise tag limit in Cimplicity, I know it can handle up to around 10,000 tags depending on the available system resources. Given the range of datatypes you’re working with, individual tag requirements may be varying significantly, which could also be a factor. Your best course of action may be to reevaluate resource allocation, optimise your tag distribution more evenly based on their datatype requirements, or possibly break the project into smaller manageable sub-projects. Remember, the quality of the communication/OPC server's performance can also affect the amount of readable tags.
It sounds like you might be hitting a limit with OPC communication in Cimplicity. While I'm not certain of a hard limit on the number of tags, I do know that this can be affected by multiple factors, including memory allocation, network bandwidth, and the configuration of your Rslinx Classic. The datatype of your tags can also play a role, as more complex datatypes require more resources. Try troubleshooting by checking if you have sufficient resources and whether upgrading your hardware or optimizing your OPC server settings could resolve this. If you're still stuck, reach out to GE's tech support as they could provide more specific guidance for Cimplicity.
It sounds like you’re running into some classic limitations with tag handling in Cimplicity and OPC, especially with that number of tags in play. While there isn't a hard limit on tags in general, performance can definitely degrade when you exceed optimal numbers for your setup. It's worth checking the configuration settings in RSLinx, as it might have limitations on how many tags it can efficiently manage at once. Also, consider segmenting your tags into several groups or optimizing the data types being used, as different types can vary in how much overhead they create. Have you looked into increasing the memory allocation for Cimplicity or optimizing your project structure? That might help handle the additional tags better.
It sounds like you're hitting some limitations with either Cimplicity or the OPC driver, especially considering the number of tags you're working with. Cimplicity does have some configuration settings that might affect tag limits, and it's also worth checking if your OPC server has a maximum tag count or memory usage cap. Make sure to optimize how you're organizing your tags too, perhaps by consolidating some data points where possible. Also, freeing up resources on the PLC side can help when scaling out; sometimes, lowering the scan rate or reducing unnecessary data can improve performance. Have you reached out to the support forum or documentation for Cimplicity? They might have specific guidelines or tweaks that could help with your situation.
✅ Work Order Management
✅ Asset Tracking
✅ Preventive Maintenance
✅ Inspection Report
We have received your information. We will share Schedule Demo details on your Mail Id.
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
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.