Looking for guidance on automating recipe selection and uploading in a Mitsubishi GT2507 HMI and FX5U PLC system? The customer now requires a method to select recipes from a list of 200 and upload them to the PLC for sequential execution. Unfortunately, the local Mitsubishi representative has indicated that selecting and uploading recipes directly from the HMI to the PLC is no longer possible due to recent streamlining by Mitsubishi. It seems like the PLC will need to store the recipe system, but the method for referencing and managing recipes through the HMI remains unclear. Are there any resources available that provide examples or white papers on how a PLC can effectively store and manage recipes in this type of system?
The FX5 may not be heavily utilized, but it does offer the option to configure file registers, also known as "R" registers. These file registers can be set to retain memory, provided there is enough memory available for all the recipes. This configuration is typically done in the parameter settings, which differs from the FX2/3 series. While the documentation may be lacking, it is possible to set the R area for latching, allowing for retentive memory storage. The ability to use R registers is essential for creating a simple program that reads and retrieves blocks of data, such as recipes. It is crucial to ensure that all recipes are of the same size and contain the same data structure when utilizing this method. The process of storing and retrieving recipes can be complex, especially when using HMI systems like the GOT. However, by utilizing the PLC to store and retrieve recipes, such as with the Mitsubishi Badged Beijers E series, it is possible to streamline the process. In the case of the FX5, it may be feasible to select recipes on the HMI, download them, and save them onto the PLC. This approach can help reduce the number of recipes needed in the PLC, particularly when dealing with a large quantity of recipes. To implement this process effectively, it is crucial to follow a step-by-step approach. By storing each recipe on the HMI and transferring it to the PLC using pointers and block transfers, it is possible to manage and access a significant number of recipes efficiently. By assigning a pointer to each recipe and incrementing it as new recipes are downloaded, the PLC can control the loading and running of recipes seamlessly. If assistance is needed in setting up this system, providing details on the recipe structure, number of registers, and maximum number of registers per recipe can help in creating a tailored solution. With this information, a comprehensive plan can be developed to showcase the functionality and efficiency of this recipe storage and retrieval system.
Thank you for your response, Parky. You are correct that the R registers can be set to latched through the CPU parameter window, but it seems to require a battery, which we currently do not have. I am wondering if "latched" and "retained" are synonymous. The software is not extensive, so we have D6000 to D8000 (and potentially more) available as retained registers for use. Storing recipes on the HMI could be advantageous, as it may allow customers to use spreadsheets to make adjustments in the future. However, if it simplifies management, it is not necessary for it to be handled through the PLC. Recipe Structure: There will always be 5 items in each recipe, including a unique name and 4 setpoints, all of which are "Floating Point". I envision a scenario where an operator can access a screen on the HMI to input a recipe number, retrieve the unique name and items of the recipe, make changes, and then store them back to the PLC. Subsequently, the PLC can refer to these recipes during the sequence execution by allowing the operator to choose which recipes to run through switches on the HMI. While there may be a more sophisticated approach to achieving this, I am striving to keep it straightforward in my mind. I am puzzled about how the PLC can associate a specific set of setpoints with, for example, Recipe 6. Any guidance on this matter or suggestions regarding which PLC functions to utilize would be greatly valued.
I'm curious, does the table display correctly on your screen? It seems to be a bit off on mine.
Do not worry, I have some code written in R registers that can be implemented in any spare system. On the HMI, you must load the recipe into specific PLC registers, such as D200 to D229. A button on the recipe load screen will then set the value at D0 (the pointer to the first set of recipe registers) to 0. This pointer is multiplied by 30 using a one-shot rising edge function to address the 30 registers needed for the recipe. The data is then block moved from D200 to D229 to R0-R29 using indirect addressing with an array created for the first set of registers. When the button is pressed again, the data from D200 to D229 is moved to R30-R59, and the pointer is incremented for the next recipe. The process repeats for up to 5 recipes, with a need to prevent additional recipe loads once the limit is reached. The multiplication factor for the pointer should be based on the number of recipe variables, with using 30 as a default for simplicity. Furthermore, additional logic is required to manage the transition between recipes during operation and to prevent errors from the operator. It is essential to retrieve and load the recipes sequentially from the store with proper contingency measures in place. If further clarification is needed, feel free to ask for more detailed explanations.
In this system, operators can store up to 5 recipes in the PLC for processing. The operator first loads the recipe to be used into the running recipe area, then selects a recipe from the queue using a button. The process continues by loading the next recipe and selecting another queue button. Once all recipes are in the queue area, the operator can start the system by pressing the start process button. The PLC then moves each recipe into the current recipe area for processing until all recipes in the queue have been completed. This system allows for flexibility in the number of recipes stored, with individual buttons for each queue recipe for easy management. The structure of recipes can be created using UDT's, making it an efficient and user-friendly process. Additionally, storing recipes in the PLC allows for easy access and selection of recipes for processing, eliminating the need for storing a large number of recipes directly in the PLC.
While I can see how Mitsubishi's recent changes could complicate things, integrating the PLC into your recipe system might be more streamlined than you think. You're correct in saying that the PLC will probably need to store the recipes, but the HMI could still function as your interface for selecting and managing them. Consider dividing the different recipe variables into registers in the PLC - this could allow the HMI to reference the particular recipe through its register numeral. And although I don't have any specific white papers to share off the top of my head, I would recommend checking out some of the user forms and technical documents from Mitsubishi Electric's website, as they often have a good variety of system-specific examples there.
It seems to me that Mitsubishi has taken a new direction with their streamline process. While it may look challenging, I do believe it's still manageable. Yes, you will have to store recipes in the PLC, but for managing them through the HMI, I reckon you'd likely work with pointers/index values referencing the recipe on the PLC from the HMI. As for resources, I found some good information in the Mitsubishi Electric FA site on their MELSEC iQ-F series PLC's, specifically the FX5 User's Manual (Data Communication). It outlines the features and parameterization of the PLC's data management and communication systems, which could help you in selecting and managing your recipes from the list. Hope this helps!
✅ 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: - No, the local Mitsubishi representative has indicated that this direct method is no longer possible due to recent streamlining by Mitsubishi.
Answer: - The customer needs to select recipes from a list of 200 for sequential execution.
Answer: - The method for referencing and managing recipes through the HMI remains unclear, but resources like examples or white papers may provide guidance on how a PLC can store and manage recipes in this system.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.