Following a power outage, the Current_Time(0) is reading as 568309 instead of 2024. I'm unsure of where the controller is pulling this value from. Any suggestions on troubleshooting this issue?
How can you correctly set the value of Current_Time(0) in your program? Learn the steps to properly initialize Current_Time(0) in your code.
User jeaton noticed that after experiencing a power outage, the Current_Time(0) is showing as 568309 instead of the expected value of 2024. They are unsure where the controller is sourcing this incorrect value from and are seeking suggestions. Is it possible that the controller is retrieving information from an uninitialized memory location following the power outage? Any insights or solutions would be appreciated.
JeremyM inquired about the mechanism for setting Current_Time(0) in a program. It seems to be established within a GSV linked to the WallClockTime class and the LocalDateTime attribute. The origin of these values remains unclear. Is there an internal clock within the controller? Any insights would be appreciated. Thank you.
In the GSV setting, the class is identified as WallClockTime with the attribute name LocalDateTime. The source of these values is currently unknown. Could the controller be equipped with an internal clock? Explore further by right-clicking on the Current_Time tag to cross-reference and determine if it is being controlled externally. Feel free to seek guidance on L35E. Thank you.
What is the data type for the Current_Time variable? Is it DINT[7]? What is the role of the DEST parameter in the GSV instruction? If you deactivate the GSV instruction and manually input 0 into Current_Time[0], will the value of Current_Time[0] be altered?
It sounds like you've got a classic case of a system clock reset! The power outage might have caused your System Real-Time Clock (RTC) to revert to its default settings. This random-looking number, 568309, is most probably the time in seconds since your clock's reference 'Epoch' time. My recommendation would be to reset the clock to your current local time to rectify this. Ensuring a stable power supply can also help prevent such issues in future. If you continue to face issues, it might be helpful to check the battery maintaining the controller's RTC as well.
It sounds like the power outage might have triggered a glitch in your system’s internal clock. Have you tried resetting the controller to its factory settings? If the issue persists after a hard reset, it could be a problem with the controller's internal battery, or a more complex software issue. You might also want to check if there have been reports of similar issues with your particular model, as it could offer a clue on how to solve it.
It seems like the controller might be fetching time in an unformatted Unix timestamp. The Unix timestamp is the number of seconds that have passed since January 1, 1970, at UTC. The large number is simply the number of seconds, and a quick conversion should give us a date closer to our current time. If that's the case, you need to look into the way your system is set to format time. It should be converting the Unix timestamp to a more readable format. Try probing into the system's time formatting or date-time settings.
It sounds like your system may have reset to some default or arbitrary value due to the power outage. I'd suggest initially checking the system's time source. If it's network-synchronized, it could be that the time server is providing an incorrect timestamp. Try manually resetting the time (if your system allows this) and observe if it continues to drift off. If the problem persists, the issue could be more complex, such as a conflict with another system process or even a minor failure on your system's real-time clock battery. Examining system logs might provide more insight into what's going wrong.
✅ 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. Why is my CompactLogix Controller displaying an incorrect time reading after a power outage? - After a power outage, the CompactLogix Controller may display an incorrect time reading due to various reasons such as a loss of synchronization with the system clock or incorrect configuration settings.
Answer: - To troubleshoot the incorrect time reading, you can start by checking the synchronization settings with the system clock, verifying the time zone settings, and ensuring that the controller's internal clock is set correctly.
Answer: - You can try resetting the time on the controller, reconfiguring the time settings, checking for any firmware updates that address time-related issues, and ensuring that the power outage did not cause any hardware damage affecting the timekeeping functionality.
Answer: - The time reading on a CompactLogix Controller is commonly stored in a specific memory location, such as Current_Time(0). Checking this memory location can help identify where the controller is pulling the incorrect time value from.
Answer: - Implementing backup power solutions, regularly
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.