Hello Everyone, we are currently in the process of setting up a backup CPU (Q02CPU) for a Mitsubishi PLC. Unfortunately, we are experiencing difficulties in transferring the existing program parameters from the old PLC. We were only able to copy the program itself. After successfully downloading the program to the new backup CPU, we noticed a discrepancy in the output of the Intelligent High-Speed Counter Module QD62E, which is used to measure the engine's RPM. Despite the engine running at 600 RPM, the PLC feedback is only showing 400 RPM. If anyone has insights on why this discrepancy is occurring, we would greatly appreciate your input. Thank you.
Hello everyone, we are currently setting up a backup CPU (Q02CPU) for a Mitsubishi PLC. However, we are facing issues with uploading the existing program parameters from the old PLC. We were only able to copy the program itself. After downloading the program into the new backup CPU, we noticed discrepancies in the output of the Intelligent High-Speed Counter Module QD62E, which is used to measure engine RPM. When the engine runs at 600 RPM, the PLC feedback shows only 400 RPM. We suspect that the high-speed intelligent module's data register is not holding the peak pulse count from the encoder, leading to different RPM readings. We are unsure if any settings on the QD62E card need to be adjusted. Any insights on this issue would be greatly appreciated. Thank you for your assistance.
Have you encountered difficulties uploading PLC parameters and special function module data? This issue may be related to the settings in the QD62E module. Which programming IDE are you currently using - GXDeveloper or GXworks2? In GXworks2, you will find an additional list for special modules on the left-hand side tree. While GXDeveloper doesn't have this feature, there are some settings in the PLC parameters that are similar. It seems that in GXDeveloper, some configurations are done directly in the PLC code, whereas in GXworks2, they can be easily configured within the software.
parky asked why it is not possible to upload PLC parameters and special function module data, mentioning settings in the QD62E. Are you using GXDeveloper or GXworks2 as the programming IDE? In GXworks2, there is an additional list for special modules on the left-hand side tree. On the other hand, GXDeveloper does not have this list, but there are settings in the PLC parameters section. It seems that in GXDeveloper, some configuration is done in the PLC code, which can be handled through configuration in GXWorks2. Thank you for your response. We are currently utilizing GXWorks2.
Sundar4163 mentioned: Thank you for the response. Our team is currently utilizing GXWorks2 software. However, we have encountered an issue when uploading the program and parameters from the PLC to our PC backup file. The PLC parameter information, including data from the QD62E module and other Intelligent modules, is not being transferred properly. We were able to configure data registers in the autorefresh page for the Intelligent function modules, but we are facing challenges with setting up the high-speed settings for the QD62E module. In the program, the QD62E module is utilizing two data registers: 4557 and 4558. As this module only has two channels, we are unable to assign these data register numbers in the autorefresh page due to a duplicate register error message. It seems that there may be an issue with the QD62E settings, leading to incorrect RPM readings. Let's explore further to resolve this discrepancy.
Each channel on the counter card requires 2 data registers, with a 32-bit count register such as D4557 and D4558 for channel 1. To avoid conflicts, it is recommended to assign the second channel to registers like D4559 and D4560. If you encounter any issues, check the tools menu for settings and operations related to the counter card. Please note that I do not currently have a counter card to provide specific details.
It's possible that the discrepancy might be related to the settings of the High-Speed Counter Module QD62E itself rather than the CPU or the transferred PLC program. Every time you set up a PLC, the modules also need to be set-up separately in some cases. I would recommend cross-checking the setup of the QD62E, specifically the Pulse Conversion Factor. Incorrect configuration could likely lead to distorted RPM measurements. In your case, it seems the module is counting fewer pulses than it should, hence the significant drop in RPM readings from the actual. Make sure the interrupt settings are correctly configured as well.
Hi there, it sounds like you've done a solid job of cloning the program to the backup CPU. The discrepancy you're experiencing with the High-Speed Counter Module could likely be due to a difference in scaling between your old and new PLCs. Depending on the programming, it's possible that your old PLC was scaling the RPM measurement input in a certain way that isn't being replicated in the new PLC. I'd suggest checking if there are any scaling factors or equations in your old PLC that haven't been copied across to the new one. Also, ensure the QD62E Module's settings match exactly with the old setup. Good luck!
It sounds like your issue may be originating from differing parameters between your old and new PLCs. While you've managed to copy the program, it's essential to keep in mind that each PLC model may handle its I/O configuration differently, including high-speed counter modules. I'd recommend taking a closer look at the QD62E's configuration on your old PLC and then manually setting those same parameters on your new system. It's probable that the pulse rate of your new PLC isn't aligned with the old one, hence the discrepancy in your RPM display.
It sounds like a frustrating situation! Since you mentioned that you only copied the program and not the parameters, it’s possible that the configuration settings for the QD62E module didn’t get transferred. Double-check the input settings and scaling factors on the new CPU to ensure they match what was set in the old one. Also, make sure to verify any relevant hardware settings or jumpers that might be affecting the counter’s output. It might help to look at any adjustments or calibration that were done previously as well—sometimes small tweaks can lead to such discrepancies. Good luck, and keep us posted on what you find!
✅ 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: - The discrepancy in the output of the QD62E High-Speed Counter Module could be due to configuration settings, wiring issues, or parameter settings that need adjustment. It would be beneficial to review these factors to troubleshoot the problem.
Answer: - To troubleshoot the RPM reading issue, ensure that the Q02CPU backup CPU is properly configured and that the module is set up correctly in the program. Check the wiring connections, calibration settings, and parameters related to the QD62E module to identify and rectify any discrepancies.
Answer: - When setting up a backup CPU for a Mitsubishi PLC, ensure that both the program and the program parameters are transferred correctly. Verify the transfer process and settings to ensure all necessary information is copied accurately to avoid discrepancies in operation.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.