Hello Members, We are currently encountering a challenge with the PlantPAx 5 PMTR library in our project. Our bidirectional motor has 2 digital inputs for the forward and reverse limits, however, we are unable to find this functionality in the PMTR block. Additionally, we are unable to access the Operator commands for use in our logic. We need to be able to stop the motor at the forward and reverse limits in operator mode. Are there any solutions available for this issue? Thank you.
I have experience with versions 3 and 4, but I am curious if interlocks can be utilized for the limit switches.
Cheeseface inquired about using interlocks for limit switches in versions 3 & 4. I attempted to implement it, but opted for a one-shot plus approach instead. This decision was made because having interlocks constantly engaged once the limit is reached could potentially lead to the operator restarting the motor prematurely (as it operates on a pulse signal).
Unfortunately, I do not have a P controller to test this out. I am curious about why the interlock block cannot be utilized in this situation. Is it possible to have dual interlocks that combine the forward limit and state with the reverse limit and state using an AND logic gate? This would require the operator to change direction after hitting the interlock, rendering it ineffective. Does this proposal seem reasonable?
It seems like your limit switch may be causing the issue. Why is it acting as a one-shot? If it's still within the set limit, it should remain on. Have you considered latching the limit signals and unlatching them when a reverse motion is detected? As cardosocea recommends, it's beneficial to use separate forward and reverse interlocks. In version 4, utilizing the P_MotorRev with inputs for each direction could be a helpful solution.
I am excited to share a clever solution I discovered! In this setup, test bool and tota serve as simulated limit switches, while tag1 acts as the interlock for a bi-directional motor. This configuration effectively prevents the motor from restarting in the forward direction. I will be conducting further tests with real hardware tomorrow, hoping for successful results. * Keeping my fingers crossed *
Hello, Have you considered using interposing aux contacts mapped to the 'MotorRunningFwd' and 'MotorRunningRev' inputs in the PMTR block? As for operator commands, it's not usually direct but you might be able to make use of the 'Cmd' parameter of the PMTR block. This block works on a higher level of functionality, but with a little creative mapping, it should be possible to link your operator inputs to the 'Cmd' values. However, remember to avoid overlapping command scenario as it may put your system in a state of confusion, leading to unexpected behavior. Good luck!
Hey there, I've encountered the same issue before with the PlantPAx 5 PMTR library. One workaround I found was to use the Overtravel Inputs of the PMTR block to manage the forward and reverse limits respectively. As for the operator commands, once you have an understanding of the specific commands you need to implement, you can use programming techniques to manually set or simulate these commands within the logic. Hope this helps! Let me know if you have other questions.
Hello, It seems you may need to create your own code to get the exact functionality you're after with the PMTR block. In terms of stopping the motor, you might want to use the MotorOff_FB function block to stop the motor at the limits. As for the operator commands, you could try using PV (Process Variables) or tags which are usually integrated into the PLC (Programmable Logic Controller) program. Although I agree it might not be as straightforward as you'd like, you should be able to design custom solutions this way to obtain the level of control you need. Good luck!
Hey there! It sounds like you’re facing a tricky situation with the PMTR library. One option you might consider is creating a custom function block that incorporates the limit input functionality you need. You could use a combination of ladder logic or structured text to check the status of those digital inputs and then implement the stop command based on their states. Additionally, ensure you’ve enabled all necessary function blocks, as sometimes the default configurations may not show all available features. It might also help to check in the documentation for any hidden settings or parameters that could facilitate operator control. Good luck!
✅ 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: The PlantPAx 5 PMTR library may not have built-in functionality for handling bi-directional motor limits with 2 digital inputs for forward and reverse limits. You may need to explore alternative solutions or custom logic to address this issue.
Answer: Answer: The PMTR block in the PlantPAx 5 library may not directly support the specific requirements of managing forward and reverse limits for a bidirectional motor. You may need to consider implementing custom logic or seeking assistance from technical support for a workaround.
Answer: Answer: If you are unable to access the Operator commands for stopping the motor at limits in the PlantPAx 5 PMTR library, you may need to explore other function blocks or develop custom logic to incorporate this functionality into your project. Consider reaching out to the Rockwell Automation support team for guidance on implementing the desired behavior.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.