Rockwell PID to PlantPAx P_PIDE Migration: Equivalent Parameters Chart Needed

Upon closer examination, it appears that the .swm file extension is associated more with a manual command-thinking process. Specifically, it seems to relate to the PCmd_Man command.

• 22-07-2024
• FriedNickman

It sounds like you're really sinking your teeth into this migration project! While I don't have a chart on hand, I remember from my own experience that your list looks pretty comprehensive. However, you might want to check the .Cfg_Report parameter (.Cfg_Report tracks error reporting) if your system uses it. Also bear in mind that actual mapping might depend on specific functions of your PID control, so it might be worthwhile to thoroughly review your PID configuration. I recommend double-checking all the interlocks and limits, since they'll be specifically important when using the PlantPAx P_PIDE. Hope this helps!

• 31-12-2024
• Anthony Lewis

Your migration project sounds fascinating! I've had a couple of similar transitions and one of the things I learned was to not underestimate the importance of thorough commissioning for each PID loop post-migration. Though I don't have a full chart, I'll highlight an area that could be improved: for '.bias' to '.Inp_FF' you should be cautious, it's not a direct match as there could be an offset to consider. Also, I've noticed the parameters '.Cfg_DerivSPAct.dvn' and '.CfgMaxCV.maxo' often require tuning after migration. Hope this aids you and good luck with your project!

• 31-12-2024
• Paul Martinez

Hi there! The transition from standard PID to PlantPAx P_PIDE can indeed be quite intricate. However, I believe that you've identified a significant number of essential parameters already. Your list is quite comprehensive. I'd recommend also considering parameters like .Cfg_AutoState (it affiliates with automatic state setting) and .Inp_TrkSP (related to tracking setpoint). These could have significant influence depending on your system's setup. Keep in mind that the success of your migration is not just about having an exhaustive list, but about understanding the minute implications of each parameter within the context of your system. Hope that helps! Best of luck with your migration project!

• 12-01-2025
• Liam Bennett

Hey there! I'm currently on a similar project and I can definitely understand those uncertainties during the transition. The chart of equivalent parameters you're asking for is quite extensive, but from what I can see, you're doing well in mapping it out. One parameter I noticed that might be worth adding to your list is .Cfg_Override, which correlates with the override function in standard PID terms. Feel free to correct me if I'm wrong. As to the others, I'm not sure if I recall them correctly but I have some notes saved away that might help. I could dig them out and share the info with you. Let's journey this migration project together!

• 12-01-2025
• Olivia Evans

It sounds like you’re making great progress on your migration to PlantPAx P_PIDE! While I don't have a full chart of equivalent parameters on hand, I can share that keeping track of the control strategy is crucial. It might also help to dive into the differences in the way both systems handle specific functions like tuning and fault management; subtle changes in behavior can sometimes lead to larger implications in performance. If you're in touch with anyone from the community or knowledgeable about the documentation, they might also shed light on best practices that can ease the transition. Good luck with the migration!

• 03-03-2025
• Logan Flores