Greetings! As a novice in programming, I have multiple inquiries regarding my current project. I am working on a grafcet and encountering issues when running the program, as it seems to halt at a certain point. Could the problem lie in the implementation of the bit M8147? Please excuse any language barriers as my comments are in Portuguese. Your assistance is greatly appreciated. Thank you.
The manual suggests that M8147 is specifically intended for the PLSV or PLSR function. However, it might be worth considering M8340 instead, even though it also only references the PLSV function. The manuals are not entirely clear on this matter. In reality, I have come across one manual that indicates the special registers/bits are slightly different. I am uncertain which is accurate. Personally, I am not fond of the step flag concept and prefer my own system. You may want to refer to this manual, and I vaguely recall using M8029 or a similar lower-order flag for stepping. Visit the following link for more information: https://suport.siriustrading.ro/03.Training/01.PLC/02.FX/1.Manuale/FX%20Family%20-%20Training%20Manual%20(Positioning%20Control)%20%20HIME-SH006-A%20(11.07).pdf
Are you suggesting that the M8029 or M8340 bits might be a better option? Tomorrow, I plan to retest it. I am experimenting with a unique approach to achieve the same results as a simple flag. Thank you for your assistance! How do you improve your programming skills?
The M8029 flag is essential for all function calls. While attempting to use the PLSY function bit without success, I discovered that utilizing the 8029 flag (a low number in the 8000 range) proved effective. In my experience as a systems engineer for over 45 years, I found success by using the Y0 pulse count register D8132. This register keeps track of the pulses Y0 turns on, serving as the current pulse count. By comparing this to the required pulses and resetting the trigger for the pulse function, I was able to proceed to the next step. The attached document provides a quick guide on achieving these functions by loading values into the appropriate registers.
I conducted some tests and found that the M8000 bits did not work as expected. This could be due to the fact that the bits are shared across all function calls. In my test, I utilized the DDRVI function and discovered that the M8147 bit, which is common to all calls, should only be used directly after calling the function. This approach worked successfully when tested on a friend's FX3U clone, which has transistor outputs compared to my relay output FX. By utilizing a sequence register with steps of 10, it becomes easy to insert additional steps without the need to rearrange components. Additionally, the seq variable can be used on an HMI as a multiple text field to display information about the current operation. Each sequence number corresponds to a specific text, allowing the HMI to dynamically display relevant information based on the value in the seq variable.
Once again, I want to express my immense gratitude to Parky for the help provided. I was able to successfully complete the task without any additional components by identifying the missing step 4 in the program. Despite having all the necessary conditions in place, the program skipped from step 3 to step 5, causing the issue. Thank you, Parky, for guiding me through resolving this issue efficiently.
Hello! I'd be more than happy to help. While it's hard to be certain without seeing the code, your issue could very well be related to the implementation of M8147. Sometimes, if the bit isn't properly initialized or manipulated, it can lead to unexpected results, like the program halting. If you could provide some more specific details about the role of M8147 in your programming, or even share a snippet of the code, we could probably offer more tailored advice. Don't worry about the language barrier either, we're all here to learn and share.
Hello! I'd be happy to assist with your programming issue. Bit M8147 could indeed be causing the problem - it really depends on how it's being used in your program. If possible, could you provide some more context or perhaps share a snippet of the code where M8147 is implemented? And don't worry about the language barrier. Coding is a universal language, and if needed, I can use translation tools to better understand your comments.
Hello! It's possible that the issue with your program could stem from the implementation of the bit M8147, but to say definitively, we'd need to take a closer look at the code. Regardless of the language, the concepts of programming remain the same. If you could provide an excerpt of your code around where the system halts, we could potentially troubleshoot the issue together. Don't worry about the language barriers; what's important is that we work to get you past this hurdle.
Olá! I'd be happy to assist. Grafcet can indeed get tricky at times. If your program is halting, there could be an issue with the bit M8147 if it's not set or reset correctly. Inconsistent bit status can potentially cause a program to stop. However, I would also recommend checking other parts of your code, such as whether your transitions and actions are properly defined. Could you perhaps share a small snippet of your code? It would be helpful to see the context in which M8147 is used. Don't worry about the language - I'm comfortable with Portuguese.
✅ 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: Gx Developer is a programming software used for Mitsubishi PLCs (Programmable Logic Controllers) to create, edit, and debug programs.
Answer: In PLC programming, M8147 typically refers to a specific memory bit or register used for storing data or controlling certain functions within the program.
Answer: To troubleshoot issues with the Gx Developer program getting stuck at M8147 implementation, you can check for errors in the programming logic, ensure proper configuration of M8147, and verify that all necessary conditions for the program to progress beyond M8147 are met.
Answer: Language barriers can sometimes make it challenging to accurately describe or understand the issues encountered in PLC programming. It is important to use clear and concise language, along with relevant technical terms, to effectively communicate problems and seek assistance.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.