I utilize the Global Connections feature to transfer the time data from my PanelView Plus to my ControlLogix, with the Seconds value serving as a watchdog to verify the PV+ functionality and operation of its FactoryTalk View ME application. An unintended consequence is that the FactoryTalk Diagnostics log is being inundated with the Tag Write entry every second, making it difficult to view other important diagnostic information. Is there a way to disable the Tag Write log function, perhaps for a specific tag only? So far, I have only found checkboxes in the Diagnostic List Setup to enable "log messages to printer" for various occurrences. Even after unchecking these options, the FactoryTalk Diagnostics log continues to record the Write event for my "HMI_Watchdog_Seconds" tag, under the "Information" category.
Ken Roach shared his experience using the Global Connections feature to transfer time data from his PanelView Plus to his ControlLogix PLC. By utilizing the Seconds value as a watchdog, he ensures that the PV+ is operational and running its FactoryTalk View ME application. However, a drawback is the frequent appearance of the Tag Write in the FactoryTalk Diagnostics log, overshadowing other important diagnostic information. Is there a way to disable the Tag Write diagnostic log function or restrict it to specific tags only? Despite attempting to modify the Diagnostic List Setup checkboxes to suppress certain log messages, the issue persists with the logging of events related to the "HMI_Watchdog_Seconds" tag. This continuous logging not only affects diagnostic functions but also impacts the Audit Trail by filling it up unnecessarily. I encountered a similar issue and reached out to Rockwell for assistance, but the problem remained unresolved. Adjusting the settings did not yield the desired outcome.
I raised the issue with Rockwell years ago, but it fell on deaf ears.
Thank you for sharing your insights and providing the screenshot. It seems like there have been improvements in the granularity of FTView ME 12 compared to the version I am currently using, v11. I am considering implementing regular List Identity commands via MSG instructions to the PV+ to ensure it is connected and running its communication drivers, even if the runtime visualization application is not operational.
If you are experiencing the same issue, I have found a solution that can help. Editing your project won't solve the issue - you need to access the terminal setup. Navigate to Terminal Settings > Diagnostic Setup > Message Routine > FTView Diagnostic List. Uncheck Operator Info, Engineer Info, and Developer Info. Return to the main menu, Run Application, and your issue should be resolved. This process will also eliminate the display of any other Information category messages in the Diagnostic List. However, for effective debugging and troubleshooting, it's crucial to focus on Warning and Error messages. These will still be visible after making these adjustments. I hope this guide proves to be useful to you!
It seems like you're in a bit of a troubleshooting loop. Unfortunately, to my knowledge, there's currently no direct method to disable the Tag Write log function for a specific tag in FactoryTalk. Due to the nature of the Diagnostics log, it's designed to capture all Write events, which can be cumbersome in your case. However, as a workaround, you could possibly utilize an additional intermediate tag that transfers data at a lower frequency. This way, your Diagnostics log wouldn't be overloaded with high-frequency Write events. Another approach could be to utilize the filtering capabilities of the Diagnostic Setup for better focus on the desired events. I hope this helps!
Unfortunately, there's no direct way to disable logging for a specific tag in FactoryTalk. However, if you're primarily concerned about the influx of messages making it hard to find other diagnostic information, you might consider creating a filtering strategy. You can set up severity-based filters in the Diagnostic Setup window that only display messages above a certain severity level. If you set it high enough, the informational messages pertaining to the tag Write event won't show. Yes, this is more a workaround than a concrete solution, but it might help manage your log more efficiently.
I understand your predicament - it can be quite frustrating when something designed to help instead creates a new issue. Unfortunately, FactoryTalk doesn't currently support a feature to disable logging for specific tags. However, I've found a workaround which might help - try using the EventView Class tool to filter out specific entries you don't want to see. Another option would be to write a script that extracts important diagnostic information, making it easier to view without the constant influx of the Write event. Remember to take regular backups though, just in case.
I totally get how frustrating that can be! Unfortunately, FactoryTalk View doesn't offer a direct way to filter logs for specific tags in the Diagnostics section. One workaround could be to adjust the logging settings for the whole application—reducing the verbosity of general logs could help reduce the clutter. Alternatively, if you're comfortable with scripting, consider writing a custom logging function that captures only the critical events and skips the tag writes altogether. This way, you maintain efficiency without losing important diagnostic information!
It sounds like you're facing a common issue with diagnostic logs when using FactoryTalk. Unfortunately, there isn't a straightforward way to disable logging for specific tags; the settings tend to be more global in nature. One potential workaround could be to adjust the logging level or filter settings to reduce the verbosity of the log entries, although this might also suppress other useful information. Alternatively, have you considered using a different method for your watchdog functionality, like a cyclic timer that posts updates less frequently? That could help mitigate the log flood while still keeping tabs on the system's health.
✅ 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: - You can disable the Tag Write log function by adjusting the Diagnostic List Setup settings. However, specific steps may vary depending on your setup.
Answer: - While the Diagnostic List Setup enables you to control logging for various occurrences, disabling Tag Write entries for a specific tag may require a different approach.
Answer: - If unchecked options in the Diagnostic List Setup are not preventing Tag Write events from being logged, there may be a specific configuration or workaround needed to address this issue effectively.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.