Rockwell Automation 5730 DriveLogix5730 Controller for PowerFlex 700S Drives with Phase II Control - Manual (Page 207)

Appendix
C
Application Restrictions
Additional Memory
Requirements Revision 15.0 or later may require more memory than previous revisions
(e.g., 10.x, 11.x). To estimate the additional memory that your project may
require, use the following table:
Restrictions This firmware version has these restrictions:
If you have this firmware
revision
(add all that apply):
Then add the following memory requirements to your project:
Which comes from this type of
memory:
Component
Increase per
instance
I/O (base)
Data and Logic
(expansion)
15.x or earlier tag that uses the COORDINATE SYSTEM data type 60 bytes
✔
13.x or earlier program 12 bytes
✔
task 4 bytes
✔
user-defined data type 4 bytes
✔
I/O module 16 bytes
✔
(8 bytes)
✔
(8 bytes)
produced or consumed tag 8 bytes
✔
Restriction: Description:
Forcing is not supported
between the PowerFlex 700S
and DriveLogix The forcing values can be set for the controller inputs and outputs. However, these values will not be used by the
Logix program nor will they be transmitted to the PowerFlex 700S.
Unsupported Motion Commands The following Logix Motion Instructions are not intended for use with DriveLogix and the PowerFlex 700S:
Motion State (for 1756-MO2AE Only)
• MDO (Motion Direct Drive On)
• MDF (Motion Direct Drive Off)
Motion Configuration (for tuning SERCOS cards only)
• MAAT (Motion Apply Axis Tuning)
• MRAT (Motion Run Axis Tuning)
• MAHD (Motion Apply Hookup Diagnostics)
• MRHD (Motion Run Hookup Diagnostics)
Power down banks of local I/O
when the controller is powered
down. When powering down the controller (the host drive), also power down any banks of local I/O modules. Leaving
additional banks of I/O modules powered on may result in major fault code 22 during the power-up process of
the controller.