skyfox said:
...The two VFD's that I am needing to program are AB's PowerFlex 525 series VFD's...
RSLogix 5000 v20 does not install with a new enough version Drives AOP package which supports the PowerFlex 520 series drives. So at present you cannot, most likely, select the PowerFlex 525 as an option under the I/O Configuration. Installing the latest Drives AOP package, as mentioned previously, will add support for the PowerFlex 523 and 525 drives (Note: the PowerFlex 527 drives are not supported until Studio 5000 Logix Designer v24).
skyfox said:
...Both have embedded Ethernet/IP if I am not mistaken from the documentation that I have read to date....
Yes. The PowerFlex 525 have an Embedded EtherNet/IP module or you can optionally add a dual EtherNet/IP 25-COMM-E2P module. For the Embedded EtherNet/IP module, and with your Drives AOP updated, you should now be able to select a "PowerFlex 525-EENET" drive under your Ethernet adapter in RSLogix 5000 in the I/O Configuration.
skyfox said:
...Motor speeds will be controlled via a 4-20mA signal from the PLC for both motors...
These drives facilitate wiring an Analog Input for speed referencing. Most everything you need to get you started on that is provided in this technote...
576667 - PowerFlex 520 Series Drive: Analog Input Reference 4-20 mA or 0-10V Setup
Access Level: Everyone
(More on the 4-20mA control later...)
skyfox said:
...What I am wanting is the ability to initially program these VFD's using some sort of a software package as opposed to having to manually enter Parameters at each VFD using their respective key pads...
RSLogix 5000 software, and in particular the Module Properties/Drive tab for both drives, will facilitate you in setting up and modifying the full parameter set for these drives.
skyfox said:
...I would like to get status updates, Alarms etc. in to the PLC via the Ethernet/IP interface...
This may be achieved by using the embedded and configurable Datalinks option provided with these drives. Datalinks provide a predefined list of I/O option for users to interact with the drive. The list of Datalinks available is extensive but you may only configure four additional Input and four additional Output Datalinks on top of the default Datalinks -
2 Input (DriveStatus/OutputFreq)
2 Output (LogicCommand/FreqCommand)
The default Input Datalink "DriveStatus" may contain the basic status information you require. If you want to know what alarms are or have been active you can look at Datalinks 7/8/9 - Fault 1/2/3 Code, etc.
skyfox said:
...PLC in turn will display the info on a PV+ HMI, but the HMI will never directly communicate with the VFD and it needs to stay that way...
It would not be normal practice to want or have a PanelView HMI terminal trying to communicate directly with a drive, and it should definitely not be necessary here. The HMI normally interacts indirectly with the drive data via the controller. Once the drive I/O data, via the Datalinks, is being stored in the controller, this data should then available for the HMI to access.
skyfox said:
...The PLC will command the motors to ramp up to speed X. Then about after an hour or so at speed X, it will then command the VFD to ramp the motor up to speed X2 for 1 to 2 hours. Thereafter, it will command the motors to ramp down to 0 rpm. (i.e an off state). This Off state can be two minutes, two hours, two days or two weeks. Then Rinse and repeat as necessary when a new process cycle is needed to be started...
I'm not going to delve into how you will program the above control philosophy, suffice to say, the controller should be well capable of achieving this. If you do have any questions on how you would go about programming it then of course throw them up and someone will advise you, I'm sure.
skyfox said:
...My ultimate goal is to have a software package for programming these VFD's beforehand. Then during operation...use an analog output signal from the PLC to the Poweflex to control motor speeds and receive status updates from the VFD's in to the PLC via the Ethernet/IP Interface...
You probably know which speed referencing method suits this application best. However, I just want to point out to you, in case you are not aware, that you may also command the drive speed reference over the network via the EtherNet/IP link and using the default Output Datalink "FreqCommand". In this case, you would not need to use the 4-20mA controller output.
That is just in case you are "only" using the 4-20mA option as you believe this to be the normal way to do this. If you have a valid reason for using 4-20mA then that is fine too.
Regards,
George