For the past 15 years, we have been utilizing RED LION HMI for our operations. Recently, we discovered a discrepancy in our log files, with data recorded up until March 22, 2024 at 1:16. However, a new log file was generated on January 1, 1997, and data has been logged with varying timestamps.
Today, a widespread issue affecting all Red Lion HMIs (screens) globally has been identified. This timestamp bug is causing black screens with error messages such as "SOFTWARE EXCEPTION" or "INVALID DATABASE". Restarting the screen usually resolves the issue, but multiple reboots may be necessary in some cases. After restarting, the internal timestamp will reset to 01/01/1997, causing any "LOG" recordings and events to be outdated. It is advised not to attempt to set the time and date manually. Red Lion is actively working on a solution for this issue and updates will be provided as soon as they are available. We apologize for any inconvenience and remain available for support if needed.
After submitting a support request, I received an email from Red Lion Tech Support informing me that they are aware of the issue with the Graphite 15" HMIs experiencing a "Software Exception 0F-2000-57AC-3707" error. Their development team is actively working on a solution and will provide updates as they become available. Despite any inconvenience, they appreciate my patience. Contact for any Red Lion Controls support at www.redlion.net or (877) 432-9908. Regarding the issue, it is suspected that the incorrect time on the alarm history of one unit may be related to Daylight Savings Time (DST) changes, as the units are running an older version of Crimson 3.0. A similar incident occurred with a customer running the latest Crimson 3.1 version, where the HMI clock reverted to 1-1-1997 during a DST change. To prevent future occurrences, I am seeking recommendations from Red Lion Tech Support aside from upgrading to version 3.2. Contact for more information or assistance.
After resolving a clock issue for a customer last week, a new problem has emerged with their logs. The clock is no longer the concern, but now the focus is on troubleshooting the logs.
Sure thing! Take a look at the document I received via email.
Is the Y2K bug making a comeback? Find out more about this potential delay in our latest article. Laugh out loud at the thought of Y2K causing issues in today's technology-driven world.
That's a tricky situation. However, it sounds like the internal clock of your RED LION HMI might have been reset or malfunctioned somehow which caused it to create a new log file with an old timestamp. Check if you've experienced any power outages, spikes, or fluctuations recently. Those can sometimes mess up the internal clock. Moreover, consider updating your systems to the latest firmware and double-check your backup battery. Serious maintenance might be needed if the problem continues.
It sounds like you might be looking at a time-sync issue with your RED LION HMI. There could be a bug in the system causing incorrect timestamp generation. Consider reaching out to Red Lion's technical support or try troubleshooting the problem by making sure your HMI is sync-ed up with the correct time server. Also, check if there was a power outage or a system reset around the time when the new log file was created, as it may lead to such issues.
It sounds like you've encountered a pretty perplexing issue with the log files! It could be worth checking if there's been any recent updates to your firmware or software that might have affected how the logs are generated or timestamped. Sometimes, settings can get altered during updates or maintenance, leading to discrepancies like the one you're seeing. Additionally, it might be helpful to cross-reference data logging intervals to ensure everything is being recorded as expected. Have you noticed any patterns with the discrepancies that might give more insight?
✅ 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: The discrepancy in timestamps could be due to a software glitch, incorrect system settings, or a potential hardware issue. It is essential to investigate these factors to identify the root cause.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.