In PlantPAX v4, we are encountering an issue when trying to navigate to an interlock in FT View SE. Selecting an interlock input results in an error, possibly due to the NavToFaceplate macro appending the topic name incorrectly to the tagname. Despite configuring the interlock tags with or without the topic specified, we are unable to open a P_DIn faceplate. What is the proper method to open the faceplate of the interlock input?
When viewing the "Touch" animation of the base object on the (RA-BAS) Process Interlock Objects display, you will notice the syntax as follows: Code: NavToFaceplate #3$#2.Cfg_NavTag[#102]$ #3 /RP. The parameter #3 is currently set to "Sander," which is derived from parameter #103 in the P_Motor (MV2003) global object parameter values. It is recommended to modify this to at least "[Sander]" and input the link in the P_Intlk config without the path (similar to EStop01). Note: If you have areas (folders) in your FTView Studio structure, the path may require additional adjustments, for example: Code: {/Area01/Data01::[Processor_Shortcut]}.
lmscar12 mentioned that by analyzing the "Touch" animation of the base object in the (RA-BAS) Process Interlock Objects display, you can find the following syntax: Code: NavToFaceplate #3$#2.Cfg_NavTag[#102]$ #3 /RP. Parameter #3 is receiving the value "Sander", which is passed from parameter #103 in the P_Motor (MV2003) global object parameter values. It is recommended to update "Sander" to "[Sander]" at least, and insert the link in the P_Intlk config without the path (similar to EStop01). Additionally, if there are areas (folders) in your FTView Studio structure, a more detailed path would be required, for example: Code: {/Area01/Data01::[Processor_Shortcut]}. The modification provided above successfully resolved the issue. Much appreciated.
It sounds like you're dealing with a tricky issue there! One potential solution could be to double-check your topic configuration in the application settings and ensure that the interlock tags are correctly referenced within the faceplate macros. Sometimes, clearing the NavToFaceplate path and re-entering the correct tag names manually can help too. If the issue persists, reviewing the HMI project settings or looking for specific updates related to PlantPAX v4 could provide clarity, as there might be known bugs or patches that address faceplate navigation issues. Good luck!
✅ 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 might be caused by the NavToFaceplate macro appending the topic name incorrectly to the tagname, leading to issues with opening the faceplate.
Answer: Answer: One troubleshooting step could be to check if the interlock tags are configured with or without the topic specified, as this might affect the ability to open the faceplate.
Answer: Answer: It is important to ensure that the interlock tags are configured correctly, and the NavToFaceplate macro is appending the topic name correctly to the tagname for smooth navigation to the interlock faceplate.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.