After testing each screen individually, I found that the error message "[oxplc]TAH126" only appears when compiling and sending to the PanelView. Even when using a running man, the unresolved tag error persists. Despite thorough searches through every object and data logger file, this elusive tag remains untraceable. As I continue to troubleshoot the issue, I am determined to locate the source of this error that indicates an attempt to access a non-existent PLC tag. If you have any tips on how to pinpoint this issue, please share as I am tirelessly working to resolve it.
Utilize the Application Documenter tool to generate a detailed PDF report of the application. Afterwards, conduct a thorough keyword search within the PDF document. This process will provide valuable insights and information on the application for further analysis and evaluation.
The search function in FactoryTalk View allows users to easily locate specific information within the program interface. You can access this feature by using Ctrl+F or navigating to (top menu) Tools -> Find. The search results will be displayed at the bottom of the search pop-up, from where you can click on the relevant item to be directed to its display page. For a more comprehensive search, consider using the Application Documenter tool. By opening the desired file and navigating to the "Direct Tags" folder, you can utilize Ctrl+F to search through all the tags in the FactoryTalk file. Keep in mind that the find function may not cover HMI Tags, so it is recommended to manually search for them in the "HMI Tags" section of the explorer window. Simply use the "Search For" box located at the bottom left of the window to quickly locate the tag you are looking for.
Thank you for your explanation, @CageFreeBMW. I must admit, I have never utilized the search function before. Surprisingly, despite creating numerous HMI's, I have never encountered a situation where I needed to troubleshoot this type of issue. Upon using the search function, I was unable to locate the tag on any screen. This led me to try out the Application Documenter tool, which I had never used before. I plan to delve deeper into this tool now that I am aware of its capabilities. It was ultimately discovered that the tag was inadvertently hidden in my alarms configuration due to a typo in my spreadsheet used for creating alarms and messages. It was meant to be "TAH246." Your assistance has spared me a significant amount of time and allowed me to rest easier tonight.
I am pleased to assist! I am glad that you were able to locate what you were looking for.
✅ 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 error message "[oxplc]TAH126" typically suggests an attempt to access a non-existent PLC tag within the system.
Answer: Answer: The persistence of the unresolved tag error when compiling and sending to the PanelView could indicate that the issue lies in the interaction between the PLC system and the PanelView.
Answer: Answer: To locate an elusive tag that remains untraceable, it is advisable to conduct thorough searches through every object and data logger file in the system to pinpoint the source of the error.
Answer: Answer: Some tips for troubleshooting and resolving the "[oxplc]TAH126" error could include checking the tag references in the program logic, verifying communication settings between the PLC and PanelView, and ensuring proper configuration of data tags in the system.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.