Hello! I am currently in the process of learning about HMI programming, specifically in relation to creating and managing recipes. After watching a video on this topic, I have been able to implement most of the concepts successfully. However, I am encountering an issue when it comes to selecting a job number and automatically populating a corresponding style number to the PLC for the Robot. In the PLC, I have a designated tag for the Style Number. My goal is to streamline the process by allowing users to select a job number, which will trigger the PLC to input the appropriate style number. The challenge I am facing is that there are 200 jobs with unique style numbers (e.g., Job 1 = Style 1). Currently, when I modify the value for one job, it impacts others as well, leading to overlapping settings. I have attempted to address this by creating multiple data sets, but I am uncertain if this is the correct approach. I am wondering if there is a way to create additional data sets or if I should be approaching this issue differently. If you require further clarification, please feel free to ask. Thank you.
If you're solely updating the {[PLC]Style_Number} tag for your recipe without any additional parameters, consider using a list selector over a recipe selector for better customization.
Can you guide me on the steps to achieve this? Additionally, what are the distinctions between them?
One key distinction is that recipes are designed for handling multiple variables rather than just one tag. While you can utilize a recipe selector in your application, setting it up may require more time and effort. To access the "control list selector," navigate to the advanced tab in the objects menu. Create your list selector and specify the desired number of states in the properties. Assign names and values to each state (e.g. Style 1 value 1, Style 2 value 2, etc.). In the connections tab, consider linking the value to a different tag (such as "style list select") and create another tag as a boolean indicator (e.g. "style select enter"). In your PLC program, use XIC to monitor the "enter" boolean tag, followed by a MOV operation to transfer the list selector value to {[PLC]Style_Number}.
Incorporate your up, down, and enter buttons onto the screen using the objects drop-down menu.
It sounds like you're on the right track by trying to create separate data sets. One solution could be to create an associative array (also known as a dictionary or a hash map, depending on the language you're using). This data structure allows you to store paired values, such as your Job and Style numbers, and easily retrieve one when you know the other. Therefore, when a user selects a job number, your PLC could find the corresponding style number from the array. The advantage of this approach is that it mitigates the issue of overlapping settings since each job-style pair is unique. However, it might vary in different PLC programming languages, so you'd need to check the documentation to see how to implement it in your specific situation.
It sounds like you're on the right track with creating separate data sets to manage the unique job and style number pairs. However, the issue might be stemming from how you're linking or referencing these data sets in your PLC. A possible approach could be using an array data structure, indexed by the job number. This way each style number is associated directly with its corresponding job number, eliminating the risk of unintended value alterations. For best implementation, start by making sure that your PLC supports this kind of data structure.
Hello! I think you're on the right track with creating multiple data sets. Perhaps an array could be useful here to set up a one-to-one mapping between the job numbers and style numbers. If you bind the job number to the index in the array and the corresponding style as the value, this could potentially solve your issue. When a job number is selected, it will correspondingly point to the style number without affecting the others. Just ensure that your array starts at one since your job numbers do. Hope this is helpful and keep us posted on your progress!
Hi there! It sounds like you're on the right track trying to create a connection to streamline your process. One solution might be to use a two-dimensional array to correlate each job number to its unique style number. This way, when a job number is selected, the corresponding style number gets read and transmitted to the PLC, without affecting others. An array should efficiently handle this relationship even with 200+ jobs. Make sure each job has a unique tag and no two jobs share the same tag in the PLC. If necessary, consult your PLC documentation and ensure your programming logic aligns. I hope this suggestion helps!
It sounds like you're on the right track with your HMI and PLC setup, but managing your job and style associations might be better handled with a structured data table or array that correlates job numbers to style numbers. Instead of using individual tags for each job, consider creating a multi-dimensional array or a database that holds all the job-style mappings. This way, when a job number is selected, you can reference the correct index to pull the corresponding style number without overlapping. Additionally, make sure to check your logic for updating values, as it might be tied to a shared tag rather than unique identifiers for each job. This should help streamline the process and keep the settings distinct!
✅ 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: To streamline this process, you can create a mapping system where each job number corresponds to a unique style number. This way, when a user selects a job number, the PLC can automatically input the associated style number without the risk of overlapping settings.
Answer: Answer: To avoid overlapping settings, you should ensure that each job number is linked to a distinct style number. Consider implementing a structured approach, such as using a lookup table or database, to maintain the integrity of the job-to-style number mapping.
Answer: Answer: While creating multiple data sets can be a solution, it may complicate the management of job and style numbers. It's recommended to explore alternative methods like using arrays or structured data types to efficiently handle the relationship between job and style numbers.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.