Hello everyone, I hope you're all doing great. I recently upgraded to version 35 on Logix5000 and encountered a problem where the ACC values of timers in a UDT would change unexpectedly. To address this issue, I had to create individual timer tags instead of using UDTs. Have you experienced a similar issue? Share your thoughts below. Thank you!
Are you certain you're not attempting to use the same timer variable for multiple timer blocks?
I am confident that your timers are not behaving randomly; they are executing the instructions you have programmed. Make sure to review COP commands that may be inadvertently transferring data to other parts of your UDT. It is common for incorrect COP lengths to cause seemingly random values to be transferred to neighboring members.
In response to idiotsecant's query about timer variables, I can confirm that the timer in question is not being utilized by any other blocks within the program. It's crucial to ensure each timer variable is only assigned to a single timer block to avoid conflicts or errors.
dmroeder expressed confidence in the reliability of your timers, emphasizing that they operate according to the instructions programmed. To ensure accuracy, check for COP instructions that may mistakenly copy data to other parts of your UDT. Incorrect COP length settings can lead to the appearance of random values being transferred to neighboring members. I share the same high level of confidence in the functionality of the timers and have not identified any conflicting code that may be altering their operation.
During a conversation, JGax mentioned that their confidence level was exceedingly high while troubleshooting a timer element issue within their code. Despite thorough examination, no conflicting code was discovered. They requested to share the code privately for further analysis.
Hi there! I encountered a similar issue when I upgraded to the same version. It initially baffled me because I hadn't made any changes that would affect the ACC values of timers. After some investigation, I found that it's not a bug but rather due to a new feature in version 35, where the timers in the UDT's are treated differently when used in an array. Using individual timer tags, as you're doing, is the workaround I found most effective, too. Hopefully, we see some kind of fix in a future update.
Hi there, I've encountered something similar in version 34 and spent quite some time trying to figure it out. It seems to be a sporadic issue with UDTs and timers. Your workaround is indeed a good one, albeit a bit cumbersome. Another less effortful solution might involve keeping a close eye on your alarms and triggers just in case the values take an inexplicable leap. Rockwell really needs to look into this bug, it's been causing minor headaches for a while now.
Hey there! I haven’t run into that specific issue with v35 yet, but I can see how it would be frustrating working with UDTs for timers. It’s a bummer that you had to revert to individual tags, but sometimes the extra hassle leads to more stability. Have you considered reaching out to Rockwell's support? They might have insights or even workarounds that could help streamline your setup without completely abandoning UDTs.
✅ 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. Question: What is the issue with Timer ACC values changing unexpectedly in Studio5000 V35? Answer: The issue involves Timer ACC values in UDTs changing unexpectedly after upgrading to version 35 on Logix5000.
Answer: Answer: One solution is to create individual timer tags instead of using UDTs to prevent unexpected changes in ACC values.
Answer: Answer: You can share your experiences and thoughts on dealing with Timer ACC value changes in Studio5000 V35 in the discussion thread.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.