I am currently using a Micro 820 for a small project, and I am facing a challenge in maintaining the retentive timer's value through power cycles. The controller loses its Elapsed Time (ET) data, making it difficult to resume where it left off. Users input timer values in minutes and seconds on a PanelView 800, facilitated by a User-Defined Function Block (UDFB) that converts DINT to TIME for easy execution. The HMI displays the elapsed timer value thanks to another UDFB that converts TIME to DINT. However, the main issue arises in ensuring that the retentive timer continues from its previous value after a power cycle, as the RTO resets its ET value. Despite my efforts to transfer a value to the timer's ET during the first PLC scan, I have been unsuccesful. I have been attempting to resolve this issue for some time now and am in need of suggestions. Any help would be greatly appreciated.
When configuring the RTO settings, ensure that you select the "Retained" option to preserve current values through power cycles. This will prevent data loss and maintain consistency in your system.
damica1 noted that within the RTO parameters, it is crucial to ensure that the "Retained" checkbox is selected. This feature allows the RTO to maintain its current values even after a power cycle. However, despite checking this box, an issue arises with the ET on the RTO not being retained. According to AB Tech Support and the manual, it seems that the ET cannot be retained. The dilemma occurs when using a timer set for a specific duration. By using a UDFB to transfer two DINT values into a TIME Global Variable and assigning it as the PT of the RTO, complications arise when the power is cycled. The ET on the RTO resets to 0, causing difficulties in accurately displaying the elapsed time on the HMI. This situation is especially frustrating for damica1, who is new to utilizing a Micro 800 series processor. While impressed with the ability to control a drive with a 0-10V output onboard stock, the struggles with the timer logic are unexpected and frustrating. Overall, the challenge lies in ensuring that the ET on the RTO retains its value to accurately display the elapsed time on the HMI, despite power cycles impacting the system. This issue highlights the importance of seamless functionality in automation processes.
I find myself feeling a bit puzzled after reading the help section of CCW Ver11.
It appears that the values you set will be retained even through a power cycle. However, the issue lies with the ET not retaining the value, regardless of whether it is set to be retained or not.
Thank you for sharing that information, I will definitely take note of it. I rely on the RTO for various timing functions, and fortunately, all of our units are equipped with "Battery Backup". This may be the reason why I have not encountered any issues so far, but it's always good to stay vigilant. I will keep an eye out for any potential problems in the future.
✅ 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: Answer: The issue may arise due to the RTO resetting its ET value after a power cycle, causing the controller to lose the timer's data.
Answer: Answer: Users input timer values in minutes and seconds on a PanelView 800, facilitated by a User-Defined Function Block (UDFB) for conversion and display.
Answer: Answer: Efforts to transfer a value to the timer's ET during the first PLC scan have been unsuccessful. Seeking suggestions to resolve this issue effectively.
Answer: Answer: UDFBs are used to convert DINT to TIME for input and TIME to DINT for display on the HMI, providing ease of execution.
Answer: Answer: Any help or suggestions to address the challenge of maintaining the retentive timer's value through power cycles would be greatly appreciated.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.