Hello all, I am currently working on a robotics project that involves setting layers. I am utilizing an HMI screen to utilize the numeric data display for selecting the number of layers and assigning different outputs based on the numbers selected on the screen. This is possible by using Sysmac Studio 1.45 with PLC NX1P2-9B40DT1.
By organizing each layer into a subroutine and triggering it when the HMI number value is appropriate, you can ensure that only the relevant subroutines affect the IO and internal bits or values. Additionally, you can streamline operations by setting specific bits or values to trigger different outputs within a single subroutine, especially when multiple subroutines share similarities but differ in their interaction with various IO.
I concur with I_Automation's suggestion. To enhance clarity, you have the option to create a specific program for each HMI value by leveraging the actual I/O. If the program is not invoked, the outputs will not be affected within that specific routine. Another approach is to utilize internal bits within the routines and then combine them with the corresponding outputs in a cyclic scanning block. This method allows you to easily identify which bit is controlling the outputs when monitoring the block.
On the contrary, I am not a fan of creating individual subroutines for specific variations of a pattern. This approach can be problematic as it may require additional programming whenever a new variation needs to be introduced in the future. Recently, I overhauled a complex PLC5 program by creating 48 different subroutines to accommodate each recipe variation. In my experience with robotic palletizing, I have utilized definition tables to determine the actions to be taken or outputs to be activated based on different patterns and layer counts. This method allows for easy modification and addition of new definitions without the need to create new programming routines. However, if you opt for the conditional subroutine approach, it is crucial to carefully consider when the routine should no longer be called. It is important to note that all outputs, memory, or input/output values will remain unchanged even if the subroutine is not being utilized.
Robertmee emphasized the importance of being cautious when using conditional subroutines to ensure that the routine is deactivated correctly. It is crucial to note that all outputs, memory, and IO will maintain their values even when the subroutine is not in use. To mitigate this, I make it a practice to include a final scan of the subroutine and create a Skip_Bit for it. This final scan is designed to disable all outputs and reset memory bits, set values to 0, and reset timers when needed. When the condition that triggers the subroutine ends, I activate the final scan to ensure everything is properly reset.
In my model railroad layout project, I have implemented conditional subroutines to control various train operations through the HMI interface. Each subroutine is responsible for managing multiple outputs related to track power. To streamline the process, I have created an unconditional subroutine that utilizes an integer value to activate an output. When the integer value is zero, the output is switched off, and when it is non-zero, the output is turned on. This approach centralizes all output controls and allows me to easily identify the source of activation. For example, if Ladder 22, rung 15 needs to activate an output, I input 2215 in the integer. This method greatly helps during debugging to track the origins of output activations. - Mike
Sounds like an interesting project! In my experience, Sysmac Studio is quite efficient when it comes to handling HMI screens. One suggestion I'd give is to focus on creating a well-structured program for your PLC. If your layers selection system is not well-organized, it might lead to confusion and glitches later on. Also, remember to keep your UI intuitive, so that anyone using it could understand the functions readily. Good luck on your venture!
That sounds like an exciting project! Using the HMI to handle layer selection can really streamline the process. Have you considered implementing any type of feedback mechanism to confirm the selected number of layers or if the outputs are functioning as intended? It might add an extra layer of user-friendliness to your system. Good luck with your robotics work!
That sounds like an exciting project! Using an HMI for layer selection opens up a lot of flexibility in how you manage and visualize your data. Have you considered any specific design elements for the HMI to make it user-friendly, especially with multiple outputs? Also, how’s the integration with Sysmac Studio going—any challenges you've faced so far?
✅ 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 control outputs with numeric data from an HMI screen in a robotics project, you can utilize software like Sysmac Studio 1.45 with PLC NX1P2-9B40DT1. By setting up the HMI screen to display numeric data for selecting the number of layers, you can then assign different outputs based on the numbers selected.
Answer: Answer: The HMI screen plays a crucial role in providing a user-friendly interface for selecting numeric data, such as the number of layers in a robotics project. By inputting the desired numeric values on the HMI screen, users can trigger specific outputs based on their selections.
Answer: Answer: To set up numeric data display and output control in Sysmac Studio 1.45 with PLC NX1P2-9B40DT1, you would typically configure the HMI screen to show the numeric options for selecting layers. Then, you can program the logic in the PLC to interpret these inputs and trigger corresponding outputs based on the selected numeric values.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.