I am currently utilizing FactoryTalk ME version 13 and familiar with passing a parameter file once. However, I am curious if it is achievable to pass it twice. The scenario involves multiple I/O racks, each with varying numbers of slots. My idea is to create a Go To button for each rack with a parameter list such as {[PLC]Rack1}, {[PLC]Rack2}, etc. All these buttons would lead to the same display, which would feature a Go To button for each slot within the selected rack. I intended to include another parameter list within these slot Go To buttons, like {[PLC]#1.Slot1} or #1.{[PLC]Slot1}. Nevertheless, I am uncertain about its feasibility as I have not achieved success in this aspect yet.
Are you utilizing parameter files or a simple parameter list in your HMI (Human Machine Interface) setup? I have attempted to use parameter files without involving the Global Connections settings of the HMI and a PLC, but struggled to do so successfully. You have the option to create a parameter file name in a PLC as a literal string and then have the HMI read it from Global Connections\Display\Parameter File. By assigning a string tag in this connection, the HMI will try to load a parameter file with a name that matches the tag's content whenever the screen is refreshed or changes. This approach allows for the use of interlocked buttons instead of GoTo buttons, which would update a numerical reference in the PLC, leading to the creation of a new parameter file name and a screen change incorporating the new parameters. I have delved into the realm of parameters in FTView in the past and found the FTView Studio User Manual to be a valuable resource. If you would like an illustration of the process I described, feel free to message me, and I will try to simplify one of my recent projects and share it with you. Cheers!
Utilizing the parameter list option appears to be a viable solution, as discussed in this thread. However, I have not come across any instances of achieving this solely through the parameter file option.
You can pass parameters using either parameter files or parameter lists from one display to others opened from it. For detailed guidance on parameter passing, refer to the Use parameters and global objects chapter in the FTView Studio ME User Manual.
If I understand correctly, you are looking to create a display that calls a parameter file to show rack options based on a selected goto display. This will utilize the rack number to control other parameters when navigating to another display. I recently implemented a similar feature with a pop-up and sensor bypass list on a machine. To achieve this, I used a Piloted list on the initial screen for display visibility and referenced the same value for subsequent parameters. In your case, create a piloted list selector and assign states to corresponding numbers (e.g. state1 = 1, state2 = 2). Access the value {[PLC]RackDisplayTag} and indicator {#1}, with Remote Access set to 1 using an Always_On tag in the PLC. In the parameter file, assign #1 to Numbers[XX] and define the array size accordingly (e.g. Numbers[1] = 1). When you open the first display, the parameter file will set {[PLC]RackDisplayTag} to the selected value, which can be used for visibility settings. For the next goto display, call another parameter where #1 = {[PLC]RackDisplayTag} and #2 = Numbers[XX], repeating the process for the Slot display. (Please note: apologies for any lack of clarity in my explanation.)
In theory, this setup seems feasible and a commendable effort at streamlining your process. However, FactoryTalk ME, based on my experience, only allows parameter passing once. For your desired setup, a workable solution involving nested displays may be required. You may want to create individual screens for each rack, allowing you to define parameters on a per-rack basis. Then using the global connections feature, you'll need to establish slots that can self-update based on the established parameter conveyed from the rack display screen. Nevertheless, while this does add complexity to your project, it provides the functionality you're aiming for with minimal recurrence in logic.
Based on my understanding of FactoryTalk View ME, you should indeed be able to pass parameters more than once in this way. One potential pitfall could be the placement of your PLC tag. The syntax you've used seems like it should work, but you might want to double-check how you've laid it out. For instance, you might want to try using {[PLC]#1.Slot1} instead of #1.{[PLC]Slot1}. The placement of the rack and slot numbers relative to the PLC tag could be causing issues. Additionally, ensure that the parameters in your target screens are configured to accept these values. 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: - Yes, it is possible to pass parameters multiple times in FactoryTalk ME version 13. The scenario you described involving multiple I/O racks with varying slots and passing parameters to different buttons within the display is achievable.
Answer: - You can create individual Go To buttons for each rack by setting up parameter lists like {[PLC]Rack1}, {[PLC]Rack2}, and so on. These buttons can lead to the same display with further Go To buttons for each slot within the selected rack.
Answer: - To pass parameters to specific slots within an I/O rack, you can utilize additional parameter lists within the Go To buttons for each slot. For example, you can use {[PLC]1.Slot1} or 1.{[PLC]Slot1} to target specific slots within the selected rack.
Answer: - If you are facing difficulties in passing parameters multiple times, ensure that you have configured the parameter lists correctly
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.