Académique Documents
Professionnel Documents
Culture Documents
Topic Page
Products Included in Version 4.06 1
Enhancements 2
Module / Device Revision Information 18
Application Notes 18
Products Included in Previous Versions 19
Revision History 24
Products Included in Version There are no new modules in this version of Drives Add-On Profiles software.
4.06
See Products Included in Previous Versions on page 19 for a list of products
included in previous version of Drive Add-On Profiles software.
2
Enhancements This section describes the enhancements provided in this version of software:
NAT is a feature in the 9300-ENA device (and other routers) that provides the
following features and benefits.
• Identically configured machines, with the same
IP addresses, can be connected to and coexist
on a plant-wide Ethernet network.
• Allows OEMs to consistently build machines
that are identically configured.
• Network traffic from devices that are not
translated is blocked from the plant-wide
network. By translating only the devices
needed, the number of IP addresses required
on the plant-wide network can be significantly
reduced.
Example: Machines A, B, and C have devices that use the same IP addresses on
their local networks.
In the previous example, when the personal computer is connected on the NAT
router's uplink interface side, the AOP will use the public IP address assigned to
the Ethernet bridge module by the NAT router. When the AOP sends a message
to the drive, it first goes to the Ethernet bridge module, which then forwards the
message to the drive. Note that if the AOP is offline to the controller, the AOP
cannot communicate to the drive unless the NAT router has assigned the drive a
public IP address, which can then be selected in the RSWho.
When the PC is connected on the NAT router's internal network side, the AOP
can communicate directly to the drive. This will work whether the AOP is online
to the controller or not.
If the controller and drive are connected to opposite sides of a NAT router, the
AOP needs to be configured differently. Check the box labeled ‘Module and
Controller communicate through Network Address Translation (NAT) devices’
on the Port configuration tab in the Module Properties dialog box (as shown in
the example below). This will allow you to set the IP Address on the Port
Configuration tab page (Local / Private Address) to a different value than the IP
Address on the General tab (Plant / Public Address).
This section provides an overview of the new ADC Auditor tool introduced in
the version 4.06 Drives AOP release. This enhancement was added to assist users
with setting up Automatic Device Configuration (ADC) and to identify any
errors or warnings with their setup.
The ADC Setup icon is used to open the ADC Configuration Settings
window. The icon is highlighted (green) to provide a visual indication that
any port on the drive has been configured for ADC.
Best Practice – Do not enable ADC until after you have configured and
commissioned the drive. This eliminates nuisance ADC downloads triggered by
any parameter changes.
Best Practice – Enable and test ADC with one drive prior to enabling it for the
entire Logix system. Any errors or warnings found with the first drive can then be
taken into account when setting up ADC for subsequent drives.
Best Practice – Upload the configuration from the drive to the controller prior
to enabling ADC for that drive. This makes the drive’s configuration in the
project (parameter settings, peripherals, firmware revisions, etc.) match the actual
drive.
A “small” device is one whose entire configuration fits in the ‘Ethernet Forward
Open’ message when a Logix controller connects to it. A “large” device, such as a
PowerFlex® 755 drive, requires multiple messages from the Logix controller to
transfer its configuration. ADC is this additional messaging during connection
with a “large” device.
Selecting the ‘Enable Automatic Device Configuration’ check box enables ADC
for every port. Deselecting the box disables ADC for every port. If the check box
is shaded , there is a combination of selected and deselected ports in the
column.
Selecting the ‘Fail Drive Connection on Peripheral Error’ check box enables
every port to cause the Logix-Drive network I/O connection to fail if there is an
error when configuring a peripheral (port). Deselecting the check box disables
every port from causing the Logix-Drive network I/O connection to fail if there
is an error when configuring a peripheral (port). If the check box is shaded ,
there is a combination of selected and deselected ports in the column.
Best Practice – If ADC is used, deselect the respective ‘Enable Automatic Device
Configuration’ and ‘Fail Drive Connection on Peripheral Error’ check boxes for
“temporary” devices that are not critical to your application, such as HIMs and
serial converters.
The example above also shows all ‘Allow Writes on Port’ check boxes deselected,
except for the embedded EtherNet/IP port (port 13). Deselecting a port
prohibits writes to that port, while reads can still occur. When ADC is enabled,
the Logix controller “owns” the configuration of the drive. Changing drive
configuration settings with a HIM or some other software tool, or via explicit
messaging (MSG instruction) to parameter nonvolatile storage, clears the drive’s
configuration signature and will trigger an ADC download the next time the
controller establishes an EtherNet/IP I/O connection with the drive. Any
changes made outside of Studio 5000 will be lost.
Best Practice – If ADC is used, deselect all port check boxes in ‘Allow Writes on
Port’ except for the embedded EtherNet/IP port (port 13).
Note: The port connected to the Logix controller is always selected and cannot
be changed (is dimmed).
The Connect To Drive dialog box opens, where you select the online drive
associated with the drive in the AOP.
2. Select the drive and click OK.
ATTENTION: The ADC Auditor tests the drive’s configuration settings and ADC setup by
emulating the ADC download process. Configuration settings will be downloaded to the
drive as part of the ADC audit process. The drive must be stopped and in a safe condition
before initiating the audit. Connection to the drive must also be inhibited (check the
‘Inhibit Module’ check box on the Connection tab in the drive AOP) and DeviceLogix
must not be running. Any parameter edits made during this process will not be saved to
the project until OK is clicked on the Automatic Device Configuration Settings dialog
box.
3. On the ADC Auditor Start page, click Start ADC Auditor Analysis to
start the process.
The ADC Auditor begins downloading the configuration to check for any
errors or warnings.
Any errors or warning are shown in the Issues list on the ADC Auditor
Solutions page.
4. Click each issue in the list to see potential solutions to correct the issue and
make any necessary changes.
5. When you have completed making changes, click Recheck ADC at the
bottom of the page to run the ADC Auditor again.
Errors that have been corrected are removed from the List. Any remaining
or new errors are listed.
6. Correct any remaining errors and/or click Finish.
7. Click Close.
When the controller is set for Rem Prog, Rem Run, or Run and the connection
to the drive is not inhibited, ADC will be triggered to download the
configuration to the drive and set the configuration signature. The configuration
signature is checked each time the controller establishes an I/O connection with
the drive and cleared when any write is made to the drive outside of ADC. If the
configuration signature in the drive does not match the configuration signature
in the controller, ADC is triggered and the drive is configured. It is important to
note that ADC occurs the first time the Logix controller connects to the drive
after ADC is enabled or any time parameters are changed via the AOP. This is
necessary to be sure the configuration matches and to generate and write
configuration signatures for each port. Future connections made by the Logix
controller, such as after a reset or power loss, will first check the configuration
signatures to determine if an ADC download is necessary.
If you are viewing Studio 5000 during the ADC process, a yellow triangle
appears next to the drive in the I/O Configuration folder while ADC is
occurring.
You can follow the ADC process by accessing the Connection tab in the AOP
Module Properties dialog box and viewing the Status information in the lower
left-hand corner.
ADC will not trigger again unless there is a mismatch detected in the
configuration signatures when an I/O connection is being established. Possible
causes of a configuration mismatch include the following items.
• A drive fails and is replaced with a new drive.
• Port 1 is not write protected and you change a parameter value using the
HIM.
• You change a parameter value using a drive software tool, such as
Connected Components Workbench, DriveTools SP, or DriveExplorer.
• Changing a drive parameter in the Drive AOP and downloading the
configuration while offline with the controller.
• The Logix program contains an Explicit Message write (MSG instruction)
to parameter non-volatile memory instead of RAM.
• You can now go online with the drive regardless of the presence or absence
of a HIM or serial converter versus the drive in the project. In previous
AOP versions you would have been prohibited from going online if a
mismatch was found
This version of Drive AOP software now supports using DeviceLogix with a
SMC™-50 Solid-state Smart Motor Controllers.
All 600V ratings for PowerFlex 750-Series drives are now supported.
The 22-HIM-A3 version 2.002 missing database issues has been resolved.
Support for the PowerFlex 520-Series drives has been provided for the
22-COMM-E and 22-COMM-C multi-drive mode adapters.
The latest version of Drive Add-On Profiles ship with each release of Studio
5000, starting with version 16. New Drive Add-On Profiles can also release
between Studio 5000 releases and be installed separately.
Before starting installation, be sure that the following applications are closed
(these may appear in the lower right portion of your task bar or system tray):
• Drive database server
Click the expander icon (▲) on your task bar to see hidden icons
To begin the installation of the Drive Add-On Profiles software, extract the zip
file and run Setup.exe.
Updates
For an additional level of technical phone support for installation, configuration, and troubleshooting, we offer
TechConnect support programs. For more information, contact your local distributor or Rockwell Automation
representative, or visit http://www.rockwellautomation.com/support/.
Installation Assistance
If you experience a problem within the first 24 hours of installation, review the information that is contained in this
manual. You can contact Customer Support for initial help in getting your product up and running.
Rockwell Automation tests all of its products to ensure that they are fully operational when shipped from the
manufacturing facility. However, if your product is not functioning and needs to be returned, follow these procedures.
United States Contact your distributor. You must provide a Customer Support case number (call the phone number above to obtain one) to your
distributor to complete the return process.
Outside United States Please contact your local Rockwell Automation representative for the return procedure.
Documentation Feedback
Your comments will help us serve your documentation needs better. If you have any suggestions on how to improve this
document, complete this form, publication RA-DU002, available at http://www.rockwellautomation.com/literature/.
U.S. Allen-Bradley Drives Technical Support - Tel: (1) 262.512.8176, Fax: (1) 262.512.2222, Email: support@drives.ra.rockwell.com, Online: www.ab.com/support/abdrives
Allen-Bradley, Rockwell Software, Rockwell Automation, and TechConnect are trademarks of Rockwell Automation, Inc.
Trademarks not belonging to Rockwell Automation are property of their respective companies.
Rockwell Otomasyon Ticaret A.Ş., Kar Plaza İş Merkezi E Blok Kat:6 34752 İçerenköy, İstanbul, Tel: +90 (216) 5698400