Greetings! I am relatively new to utilizing Bradley software and currently tackling my first project end-to-end. I've encountered a perplexing issue in FTView 8, where I aim to pass a dynamic pointer through a parameter file to avoid duplicating screens. Is it feasible to utilize a string variable as a parameter field and pass the actual string content instead of just the path? My project consists of multiple identical stations with the same equipment and programs. By passing specific station objects as direct tags in the parameter file, I can achieve the desired outcome. However, my goal is to pass the station identifier as a string data type, to dynamically manage the number of stations and reuse screens. While this may seem straightforward, I am still working on finding a solution. Despite searching various forums and the RA knowledgebase, I have yet to come across a similar issue. Any thoughts or suggestions on this matter?
Creating multiple parameter files can greatly streamline your workflow. By utilizing the Goto Button or List Selector, you can easily access the necessary parameters for each station. By organizing your parameter files in Excel and utilizing the search and replace function to customize station numbers, you can generate multiple files with ease. Simply copy and paste the updated files into FT for seamless integration. This method not only saves time but also ensures accuracy and consistency across stations.
In order to ensure consistency across both menu pages accessing certain objects, it is essential to remember at least one parameter. Using a variable as a parameter would help keep all pages directed to the same station. The goal is to pass the variable's value as a parameter, rather than the variable's path. While this should be achievable, the exact method is currently eluding me.
Create localized text labels within the Human Machine Interface (HMI) such as "station1," and then reference these tags in the parameter file. This will streamline the process and improve organization within the system.
I attempted the process again, recalling from my previous attempt. I created a tag named "localtags\station_name" as a retained string, assigned the value "station_1" to it, and then set #1 to equal localtags\station_name. However, when I accessed the global object using this parameter, it passed localtags\station_name instead of the desired value of "station_1". Is there a specific formatting or method to ensure the parameter file recognizes the value of the tag rather than the path to it?
Currently, I am involved in a project that incorporates the following components: The Local Tags, The Parameter File, and The Screen and String Display Tag Hookup. Here are some accompanying screenshots for reference. These elements are integral to the functionality and operation of the project.
Hey there! It sounds like you're diving into some interesting challenges with FTView 8. Passing a string variable as a parameter can definitely be a bit tricky. While FTView is typically set up to work directly with tag paths, I've found that using indirection can help—try creating a string in your parameter file and then reference this string to dynamically access your tags. You may want to explore using Data Structure arrays to hold your station information, which could simplify your implementation and reduce duplication. If all else fails, the community here or reaching out directly to Rockwell support might shed some light specifically tailored to your project setup. Good luck, and keep us updated on your progress!
Hey there! It sounds like you're diving deep into FTView 8—what a challenge! Passing a string as a parameter to dynamically reference your station objects is an interesting approach. In theory, you should be able to pass a string variable, but it often depends on how FTView handles the parameterization for the specific objects you're working with. One workaround could be to create a list or dictionary of your stations and pull the specific tags using an indirect reference. This way, whenever you change the station identifier string, the corresponding screens should update dynamically. I’d also recommend checking out user groups or reaching out to Rockwell support directly; sometimes, they've got insights that aren't widely published. Good luck, and let us know how it goes!
✅ 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: - Yes, it is possible to use a string variable as a parameter field in FTView 8 to pass the actual string content. This approach can help avoid duplicating screens and enable dynamic management of multiple stations.
Answer: - To pass station identifiers as string data types in parameter files, you can directly specify the station objects as tags in the parameter file. This method allows for dynamic station management and screen reuse within your project.
Answer: - If you are encountering difficulties in passing dynamic pointers through parameter files in FTView 8, consider exploring the option of using string data types to pass station identifiers. This approach can enhance flexibility and streamline screen reuse in your project.
Answer: - If you have not yet found a solution to your specific issue, consider reaching out to the Rockwell Automation
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.