Experion PKS Allen-Bradley Drive Interface through ControlNet Reference

Transcription

1 Experion PKS Allen-Bradley Drive Interface through ControlNet Reference EPDOC-XXX2-en-500A November 2016 Release 500

2 Document Release Issue Date EPDOC-XXX2-en-500A November 2016 Disclaimer This document contains Honeywell proprietary information. Information contained herein is to be used solely for the purpose submitted, and no part of this document or its contents shall be reproduced, published, or disclosed to a third party without the express permission of Honeywell International Sàrl. While this information is presented in good faith and believed to be accurate, Honeywell disclaims the implied warranties of merchantability and fitness for a purpose and makes no express warranties except as may be stated in its written agreement with and for its customer. In no event is Honeywell liable to anyone for any direct, special, or consequential damages. The information and specifications in this document are subject to change without notice. Copyright Honeywell International Sàrl 2

3 Contents 1 About This Document Allen-Bradley Drive Interface Purpose A-B Drive Interface Library I/O Channel Library Drive Interface Data Flow Model A-B Drive Support and Documentation Legacy SCANport drives support PowerFlex drives support About ControlNet I/O drive data transfer Logic command data Drive status data Analog frequency reference and feedback Datalink parameters Differences between Legacy SCANport and PowerFlex Drives Allen-Bradley Drive Interface Planning and Design General Planning References C200 with A-B Drive Interface Topology A-B Drive Interface Configuration Rules A-B Drive Interface Capacity considerations Allen-Bradley Drive Interface Installation and Upgrades Installation References Firmware Upgrade References for A-B Drive and ControlNet Adapters Allen-Bradley Drive Interface Configuration Configuration Tools for A-B Drive Interface A-B Drive Interface Configuration Data Location and Interaction Configuring CNI Module for Use with A-B Drive Interface About Adding Allen-Bradley DRIVE block to Project PowerFlex drive configuration considerations Creating A-B Drive Interface Block About adding Drive I/O Channel to Control Module DRIVE_INPUT block functional overview DRIVE_OUTPUT block functional overview AOCHANNEL block functional overview for drive interface Adding DRIVE_INPUT block to CM Assigning A-B Drive to Execution Environment Loading configuration data to A-B Drive Allen-Bradley Drive Interface Operation Monitoring Allen-Bradley Drive Interface Functions through Monitoring Tab in Control Builder A-B drive interface block icon appearances About Monitoring/Interacting with given component/block Component/block interaction considerations About Monitoring Allen-Bradley Drive Interface Functions through Station Displays Using Station Detail displays Using Station Event Summary display

4 CONTENTS 7 Allen-Bradley Drive Interface Troubleshooting Isolating Problems Fault Classifications Initial Checks Checking Control Builder error code reference Viewing flash log Viewing release information log Viewing trace log Checking server point build log Checking server point build error log Checking error log Using NetworkTools to capture chassis information Fixing Common Problems Controller switchover Cable fault or loss of power Getting Further Assistance Allen-Bradley drive troubleshooting reference Other troubleshooting sources Guidelines for requesting support Notices

5 1 About This Document This document provides information for planning, installing, configuring, operating, maintaining and troubleshooting hardware components and software function blocks associated with an Allen-Bradley Drive Interface function. Revision history Revision Date Description A November 2016 Initial release of the document. Intended audience This document is intended for personnel who are responsible for integrating an Allen-Bradley Drive Interface through ControlNet media with the Experion system. Prerequisite skills Familiar with working in a Windows operating environment. Familiar with using these Experion applications: Configuration Studio Control Builder Network Tools How to use this guide Choose a topic associated with the task you want to complete on the tree view. This guide covers tasks for planning your installation through troubleshooting considerations. Related Documents For more information about using Control Builder, see: Control Building User's Guide 5

6 1 ABOUT THIS DOCUMENT 6

7 2 Allen-Bradley Drive Interface Purpose The Allen-Bradley Drive Interface (AB_DRIVE_IF) Control Component Library includes function blocks to integrate selected Allen-Bradley drives with Experion control strategies configured through Control Builder. Attention The Allen-Bradley Drive Interface (AB_DRIVE_IF) Library is not supported on the C300 Controller at this time. Related topics A-B Drive Interface Library on page 8 I/O Channel Library on page 9 Drive Interface Data Flow Model on page 10 A-B Drive Support and Documentation on page 11 About ControlNet I/O drive data transfer on page 13 Differences between Legacy SCANport and PowerFlex Drives on page 17 7

8 2 ALLEN-BRADLEY DRIVE INTERFACE PURPOSE 2.1 A-B Drive Interface Library The Library tab in the Experion Control Builder includes the following AB_DRIVE_IF library of I/O Module and I/O Channel type function blocks to support configuration of drive interface components with Experion control strategies. Description Block Name and Icon Legacy SCANport Drives This block represents the 1203-CN1 module and the 1305 AC Drive as one entity. This block represents the 1203-CN1 module and the 1336 Plus II AC Drive as one entity. This block represents the 1203-CN1 module and a generic Legacy SCANport Drive as one entity. The generic drive must support I/O data transfer similar to the 1305 and 1336-PLUS-II drives. The Drive Input I/O Channel block allows the control strategy to use data published by the drive. The Drive Output I/O Channel block allows the control strategy to push data to the drive. PowerFlex Drives This block represents the generic PowerFlex drive and the 20-COMM-C as one entity. The PowerFlex In I/O Channel block allows the control strategy to use data published by the drive. The PowerFlex Out I/O Channel block allows the control strategy to push data to the drive. This block represents the generic PowerFlex drive and the 20-COMM-C as one entity. The 700S In I/O Channel block allows the control strategy to use data published by the drive. The 700S Out I/O Channel block allows the control strategy to push data to the drive. 8

9 2 ALLEN-BRADLEY DRIVE INTERFACE PURPOSE 2.2 I/O Channel Library The Library tab in the Experion Control Builder includes the following IOCHANNEL library of I/O Channel function blocks to support configuration of Series A chassis I/O Module components with Experion control Strategies. Only the AOCHANNEL block is shown since it also can be used with A-B drive interface components. Description Block Name and Icon This block can be used with all the A-B Drive function blocks listed in the previous table. Its output (OP) parameter can be used to write the Analog Speed Reference to the given drive. 9

10 2 ALLEN-BRADLEY DRIVE INTERFACE PURPOSE 2.3 Drive Interface Data Flow Model The following diagram shows how drive data flows through the various components and blocks in the Experion architecture. Figure 1: Typical A-B Drive Data Flow Model 10

11 2 ALLEN-BRADLEY DRIVE INTERFACE PURPOSE 2.4 A-B Drive Support and Documentation Legacy SCANport drives support The Allen-Bradley 1203-CN1 ControlNet communications module serves as the bridge between the Experion control environment and any single SCANport product. The following Allen-Bradley SCANport products are qualified for use with Experion systems: Note Only the 1305 and 1336 Plus II drives have been fully qualified for use with Experion systems. You can use other Allen-Bradley drives at your own Risk. Model Names FW Rev HIM Rev Adapter Rev 1305 Adjustable Frequency AC Drive (Series C) N/A N/A N/A 1336 PLUS II Adjustable Frequency AC Drive 1.07 Series B N/A Build 01 Please refer to the applicable Allen-Bradley documentation for a given device for more information. Allen-Bradley ControlNet (1203-CN1) Communications Module User Manual Allen-Bradley 1305 Adjustable Frequency AC Drive User Manual Allen-Bradley 1336 PLUS II Adjustable Frequency AC Drive User Manual 11

12 2 ALLEN-BRADLEY DRIVE INTERFACE PURPOSE PowerFlex drives support The following Allen-Bradley PowerFlex 7 Class drives are qualified for use with Experion systems: The Allen- Bradley 20-COMM-C communication adapter provides an electronic communications interface between a ControlNet network and a PowerFlex 7-Class drive or any other Allen-Bradley product that supports an internal DPI (Drive Peripheral Interface) adapter. The 20-COMM-C translates the ControlNet messages between Experion Controllers and the PowerFlex drives. Attention Only the PowerFlex 700, 700VC, and 700S drives have been fully qualified for use with Experion systems. You can use other Allen-Bradley drives at your own Risk. Honeywell recommends using Qualified drives in place of Compatible drives wherever possible. You must confirm that the Logic Command and Drive Status bit definitions for the drive match the bit definitions defined in the following Logic command data and Drive Status data sections. Model Names Compatible 1 Qualified 2 FW Rev HIM Rev Adapter Rev PowerFlex70 Yes No N/A N/A N/A PowerFlex700 Yes Yes Series A Series A PowerFlex700H Yes No N/A N/A N/A PowerFlex700L Yes No N/A N/A N/A PowerFlex700VC Yes Yes Series B Series A PowerFlex700S 3 Yes Yes N/A N/A PowerFlex7000 No No N/A N/A N/A Series B Series B 1. Compatible drives implement the same communications protocol described in this document and should function with Experion systems, but have not been fully tested by Honeywell. 2. Qualified drives have been fully tested by Honeywell with firmware versions listed. 3. Only 700S-Phase II drives are compatible. You cannot use 700S-Phase I drives. Please refer to the applicable Allen-Bradley documentation for a given device for more information. Allen-Bradley PowerFlex 70 Adjustable Frequency AC Drive User Manual Allen-Bradley PowerFlex 700 Adjustable Frequency AC Drive User Manual - Series A Allen-Bradley PowerFlex 700 Drive w/vector Control Option Release Notes (Revision 4.006) 12

13 2 ALLEN-BRADLEY DRIVE INTERFACE PURPOSE 2.5 About ControlNet I/O drive data transfer The drive parameter data that can be read from and written to the Experion Controllers is consistent with the data that can be programmed and displayed using PLC's, SLC's, or other logic controllers, as illustrated below. The configuration of the ControlNet communications adapter determines the amount of information that can be transferred. Figure 2: ControlNet I/O Drive Data Transfer Map Logic command data The 16-bit Logic Command word is sent from the Experion Controller through the adapter to the drive. The following table compares the Logic Command Data for different drive types. The Legacy SCANport Drives and all PowerFlex drives, except for the 700S, are basically the same. Bit Table 1: Logic command comparison between Legacy SCANport and PowerFlex Drives Legacy SCANport Drives (1305, 1336-PLUS-II) PowerFlex Drives (except 700S) 0 Stop Stop Stop 1 Start Start Start 2 Jog Jog Jog 1 3 Clear Faults Clear Faults Clear Fault PowerFlex 700S 4 Direction Direction Unipolor Direction 00= No Command 10= Reverse 01= Forward 11= Hold Present Dir 5 Local Local Reserved 6 MOP Incr. MOP Incr. Jog 2 7 Accel Rate Accel Rate Current Limit Stop 13

14 2 ALLEN-BRADLEY DRIVE INTERFACE PURPOSE Bit Legacy SCANport Drives (1305, 1336-PLUS-II) PowerFlex Drives (except 700S) 8 Coast Stop 00= No Command 10=Time 2 01= Time 1 11= Use Present Time 9 Decel Rate Decel Rate Reserved 10 00= No Comman d 01= Time 1 10=Time 2 11= Use Present Time 11 Ref Select Ref Select Spd Ref Sel 000= No Command 001= Ref A Select 010= Ref B Select 011= Preset Freq 3 010= Present Freq 4 101= Preset Freq 5 110= Preset Freq 6 111= Preset Freq 7 15 MOP Decr. MOP Decr. Reserved PowerFlex 700S Please refer to the applicable Allen-Bradley User's Manual for complete details about the communication structures Drive status data The 16-bit Drive Status word is sent from the drive through the adapter to the Experion Controller. Table 2: Drive status data comparison between Legacy SCANport and PowerFlex Drives Bit Legacy SCANport Drives (1305, 1336-PLUS-II) PowerFlex Drives (except 700S) PowerFlex 700S 0 Enabled Ready Active 1 Running Active Running 2 Cmd Dir Cmd Dir Cmd Dir 3 Actual Dir Actual Dir Actual Dir 4 Accel Accel Accel 5 Decel Decel Decel 6 Warning Alarm Jogging 7 Fault Fault Fault 8 At Reference At Speed Alarm 9 Local Local Flash Mode 10 Run Ready 14

15 2 ALLEN-BRADLEY DRIVE INTERFACE PURPOSE Bit 11 At Limit Legacy SCANport Drives (1305, 1336-PLUS-II) PowerFlex Drives (except 700S) 000= Port 0 100= Port 4 001= Port 1 101= Port 5 010= Port 2 110= Reserved 011= Port 3 111= No Local Control 12 Ref Source Ref Source Tach Loss Sw 13 At Zero Spd 14 At Setpt Spd 15 Enable 0000= Ref Auto 0001= Ref B Auto 0010= Preset 2 Auto 0011= Preset 3 Auto 0100= Preset 4 Auto 0101= Preset 5 Auto 0110= Preset 6 Auto 0111= Preset 7 Auto 1000= Term Blk Manual 1001= DPI 1 Manual 1010= DPI 2 Manual 1011= DPI 3 Manual 1100= DPI 4 Manual 1101= DPI 5 Manual 1110= Reserved 1111= Jog Ref PowerFlex 700S Please refer to the applicable Allen-Bradley User's Manual for complete details about the communication structures Analog frequency reference and feedback All Compatible Drives except the PowerFlex 700S The 16-bit Analog Frequency Reference word is sent from the Experion Controller through the communications adapter to the drive. This is the frequency that the drive is commanded to output. This is the same value as the drive's [Freq Command] parameter. The 16-bit Frequency Feedback word is sent from the drive through the communications adapter to the Experion Controller. This is the drive's current output frequency. This is the same value as the drive's [Output Freq] parameter. The valid range for both words is 0 to 32767, where zero corresponds to 0 Hertz and corresponds to the maximum frequency configured for the drive. PowerFlex 700S For the 700S, the Speed Reference and Feedback are 32-bits in size rather than 16-bits as in other A-B drives. The Speed Reference is scaled: 15

16 2 ALLEN-BRADLEY DRIVE INTERFACE PURPOSE The Speed Feedback is scaled: The Motor NP RPM is Motor Nameplate rated RPM (Parameter 4 in 700S drive) Datalink parameters The drives can be configured to send/receive up to eight additional parameters through datalinks. There are four (4) datalinks (A through D) which consist of two (2) parameter data words each, as illustrated below. Figure 3: Typical Datalink Parameter Exchange 16

17 2 ALLEN-BRADLEY DRIVE INTERFACE PURPOSE 2.6 Differences between Legacy SCANport and PowerFlex Drives The following table summarizes the basic functional differences between the Allen-Bradley legacy SCANport drives and the PowerFlex 7 Class drives as integrated in the Experion system. Function/Area Table 3: Legacy SCANport and PowerFlex Drives Comparison Legacy SCANport Drives (1305, 1336-PLUS-II) PowerFlex Drives (except 700S) Communications Adapter 1203-CN1 20-COMM-C 20-COMM-C Drive Status Word Logic Command Word OP Scaling of Reference and Feedback All bits exposed as parameters on input channel block. All bits exposed as parameters on output channel block. The valid range for both words is , where 0 corresponds to 0 Hz and corresponds to the maximum frequency configured for the drive. Datalinks Only 16-bit integer and 16- bit unsigned integer data types are supported. Experion Function Blocks Station Displays Drive IOM blocks PLUS-II GENERIC_DRIVE Drive channel blocks DRIVE_INPUT DRIVE_OUTPUT Default detailed and group displays: sysdtlabda sysdtlabda_fp Same as Legacy SCANport. Same as Legacy SCANport. Same as Legacy SCANport. 70 and 700 support 16-bit integer, 16-bit unsigned integer and 32-bit integer data types. 700VC supports 32-bit integer only. Drive IOM blocks POWERFLEXDRIVE Drive channel blocks POWERFLEX_IN POWERFLEX_OUT Default detailed and group displays: sysdtlabdpfa sysdtlabdpfa_fp PowerFlex 700S Drive 700S supports additional parameters. 700S supports additional parameters. For 700S, the valid range for both words is the Drive's Par 30 [Min Spd Ref Lim] to Par 31 [Max Spd Ref Lim]. These parameters must be configured on the Experion Drive IOM function block. 700S supports 32-bit integer and FLOAT32. Drive IOM blocks 700S Drive channel blocks 700S_IN 700S_OUT Default detailed and group displays: sysdtlabdpf700sa sysdtlabdpf700sa_fp Supported Topology No difference No difference No difference Performance/Capacity No difference No difference No difference 17

18 2 ALLEN-BRADLEY DRIVE INTERFACE PURPOSE 18

19 3 Allen-Bradley Drive Interface Planning and Design Related topics General Planning References on page 20 C200 with A-B Drive Interface Topology on page 21 A-B Drive Interface Configuration Rules on page 23 A-B Drive Interface Capacity considerations on page 24 19

20 3 ALLEN-BRADLEY DRIVE INTERFACE PLANNING AND DESIGN 3.1 General Planning References Refer to the following documents for planning and design details for the Experion system in general and the ControlNet supervisory network. For the sake of brevity, this Guide does not repeat the applicable general guidelines, considerations, cautions, and so on that are covered in these other Guides. Control Hardware Planning Guide Server and Client Planning Guide 20

21 3 ALLEN-BRADLEY DRIVE INTERFACE PLANNING AND DESIGN 3.2 C200 with A-B Drive Interface Topology The following illustrations show typical topologies for integrating an Experion C200 Controller with multiple Allen-Bradley drives and a small system with only one Allen-Bradley drive. See the following configuration rules for special topology considerations. Figure 4: Typical Multiple A-B Drive Interface with Redundant C200 Controller Topology 21

22 3 ALLEN-BRADLEY DRIVE INTERFACE PLANNING AND DESIGN Figure 5: Typical Single A-B Drive Interface with Redundant C200 Controller and Buddy CNI Topology 22

23 3 ALLEN-BRADLEY DRIVE INTERFACE PLANNING AND DESIGN 3.3 A-B Drive Interface Configuration Rules Reference CR_ABD.0 CR_ABD.1 CR_ABD.2 CR_ABD.3 CR_ABD.4 CR_ABD.5 CR_ABD_6 CR_ABD_7 CR_ABD_8 CR_ABD_9 CR_ABD_10 Description Each 1203-CN1 and 20-COMM-C adapter can only be connected to one drive. The 1203-CN1 and 20-COMM-C adapters, and the attached drive must reside on an I/O ControlNet segment that is physically isolated from unscheduled I/O communications. The 1203-CN1 module provides a connection for terminals capable of RS232 serial communications. This port can be used to edit the module's parameter and to upgrade the module's firmware. An Allen- Bradley 1203-SFC serial cable is required to use this port. As pictured, a dedicated computer can be used for configuration operations, or alternatively, an Experion Client Station node can be used for this purpose. The Human Interface Module is used to program the drive and 20-COMM-C adapter as well as to view various operating parameters. ControlNet or FTE is depicted for the supervisory network; however, Ethernet supervisory networks are also possible using non-redundant C200s only. Single or dual media ControlNet configurations are permitted for the I/O Network. A redundant controller configuration is depicted; however, non-redundant configurations are also permitted. The communication adapter 1203-CN1 or 20-COMM-C and the attached drive must reside on an I/O ControlNet segment that is physically isolated from unscheduled I/O communications. For redundant controller configurations, locate the ControlNet moderator outside the redundant chassis pair (RCP) and do not assign the MAC ID 1 to the downlink CNIs. For redundant controller configurations, at least four (4) nodes are required on every ControlNet segment to prevent nodes from becoming lonely during a RCP switchover. If only one A-B Drive is present on the I/O ControlNet segment, then an additional CNI (Buddy) node must be added. The MAC ID 1 should be assigned to the additional CNI. No Buddy CNI is required for non-redundant configurations, which do not require four (4) nodes on the ControlNet segment. 23

24 3 ALLEN-BRADLEY DRIVE INTERFACE PLANNING AND DESIGN 3.4 A-B Drive Interface Capacity considerations Consider the following considerations when planning to include an Allen-Bradley Drive Interface in your Experion system. The C200 Controller supports a maximum of 64 I/O modules. Since each A-B drive uses one connection, each drive has the weight of one I/O Module. This means you can have a maximum of 64 A-B drives. The maximum number of A-B drives per downlink ControlNet Interface module (CNI) is 18. Each Legacy SCANport Drive with 1203-CN1 adapter counts as one I/O Unit. Each PowerFlex Drive with 20-COMM-C adapter counts as one I/O Unit. Each A-B drive must be equipped with a communications adapter and must reside on an isolated I/O network separate from the Series A Chassis or Series H Rail I/O. Each physical I/O ControlNet segment can only support either scheduled or unscheduled communications but not both. This means that more than one downlink CNI can share a physical ControlNet segment only if all I/O on this shared segment uses the same scheduled or unscheduled communications. 24

25 4 Allen-Bradley Drive Interface Installation and Upgrades Related topics Installation References on page 26 Firmware Upgrade References for A-B Drive and ControlNet Adapters on page 27 25

26 4 ALLEN-BRADLEY DRIVE INTERFACE INSTALLATION AND UPGRADES 4.1 Installation References You install the Experion control hardware as outlined in the applicable control hardware documentation included. See the Software Installation Guide to install the latest Experion software. See the applicable Allen-Bradley documentation to install the A-B dive interface components. 26

27 4 ALLEN-BRADLEY DRIVE INTERFACE INSTALLATION AND UPGRADES 4.2 Firmware Upgrade References for A-B Drive and ControlNet Adapters You can use either a HyperTerminal with a 1203-SSS adapter or Allen-Bradley's ControlFLASH, DriveExplorer, or DriveExecutive application across ControlNet to upgrade PowerFlex drives and the 20- COMM-C adapter. You can use a HyperTerminal to upgrade Legacy SCANport drives and the 1203-CN1 adapter. Attention Since certain restrictions and limitations may apply, please refer to Allen-Bradley's technical support for drive specific direction for upgrading firmware. 27

28 4 ALLEN-BRADLEY DRIVE INTERFACE INSTALLATION AND UPGRADES 28

29 5 Allen-Bradley Drive Interface Configuration Related topics Configuration Tools for A-B Drive Interface on page 30 A-B Drive Interface Configuration Data Location and Interaction on page 31 Configuring CNI Module for Use with A-B Drive Interface on page 32 About Adding Allen-Bradley DRIVE block to Project on page 34 About adding Drive I/O Channel to Control Module on page 39 Assigning A-B Drive to Execution Environment on page 46 Loading configuration data to A-B Drive on page 48 29

30 5 ALLEN-BRADLEY DRIVE INTERFACE CONFIGURATION 5.1 Configuration Tools for A-B Drive Interface The following table identifies the tools you need to configure a given component of an A-B Drive Interface strategy. If Component is... Then, Use This Configuration Tool CN1 Adapter 20-COMM-C Adapter Allen-Bradley Drive C200 / CEE CNI A computer running a Windows terminal emulation program such as Hyperterminal. Upon establishing a serial connection with the 1203-CN1, the module's software allows you to edit the 1203-CN1's parameter, view current I/O data, and perform a flash upgrade of the firmware. The Human Interface Module (HIM) allows you to program the drive, view operating parameters, and control certain drive functions. The Human Interface Module (HIM) allows you to program the drive, view operating parameters, and control certain drive functions. The Experion Control Builder is used to configure the drive data used by the control strategy The Experion NetworkTools application is used to configure the ControlNet parameters. 30

31 5 ALLEN-BRADLEY DRIVE INTERFACE CONFIGURATION 5.2 A-B Drive Interface Configuration Data Location and Interaction The following table identifies what configuration data/functions are applicable to the given Allen-Bradley and Experion configuration tools and which functions interact with both tools. CAUTION You must carefully monitor configuration data/functions that are applicable to both Allen-Bradley and Experion configuration tools, so that when a change is made using one tool, a corresponding change is made using the other tool. A-B Drive Configuration Data/ Function Setting ControlNet MAC address Table 4: Configuration Data/Function and Tool Applicability Allen-Bradley HIM or Terminal 1203-CN1 Adapter 20-COMM-C Adapter Applicable Configuration Tool Legacy Drive Block Experion Control Builder PowerFlex Drive Block Channel Blocks No Yes Yes Yes Yes No Enabling Datalinks Yes Yes Yes Yes Yes No Changing the specific parameters to be sent over Datalinks Yes No No No Yes Yes 31

32 5 ALLEN-BRADLEY DRIVE INTERFACE CONFIGURATION 5.3 Configuring CNI Module for Use with A-B Drive Interface You must configure the Keep Object of the CNI module for the isolated I/O ControlNet segment connected to the A-B communications adapter to orchestrate the distribution of new network parameters to all segment nodes. You must have a Security level of at least Engineer to perform this task. You must refer to the following guidelines for configuring the CNI module. The CNI modules must be on a ControlNet that is plugged into a chassis, cabled to the ControlNet, and have unique MAC addresses in order to change their ControlNet parameters, such as. NUT Time, UMAX, SMAX, and so on. The ControlNet parameters are updated for all CNIs on the ControlNet at the same time. After reprogramming the Secondary CNI's ControlNet parameters to match that of the Primary CNI, the Secondary CNI must be power-cycled so that redundant partner compatibility checks are re-attempted. For redundant controller configurations, locate the ControlNet moderator outside the redundant chassis pair (RCP) and do not assign MAC ID 1 to the downlink CNIs. For redundant controller configurations, at least four (4) nodes are required on every ControlNet segment to prevent nodes from becoming lonely during a RCP switchover. If only one A-B Drive is present on the I/O ControlNet segment, then an additional CNI (Buddy) node must be added. The MAC ID 1 should be assigned to the additional CNI. Must configure the CNI module Keeper values as follows: Network Update Time (NUT) = 6250 microseconds Maximum Scheduled Nodes (SMax) = The highest MAC Address of all modules on the I/O ControlNet segment. Please refer to the NetworkTools (NTools) for Chassis Based Components (C200) section in the Control Hardware Troubleshooting and Maintenance Guide for more information about the NTools application. To configure CNI module 1 On the Configuration Explorer tab in Configuration Studio, click Control Strategy and then click Maintain control system firmware to launch Network Tools. 2 Click the OK button to acknowledge the Warning message. 3 Click the Resume button on the toolbar to initiate a network scan. 4 In the Desktop tree, click the required FTEB or CNI icon. Wait for the chassis details to display in the Detail pane. 5 Click the CNI module's graphic representation in the Details pane. The CNI module is the item with the Network Address displayed. 6 Click the Change ControlNet button on the toolbar to display the Keeper Values dialog. 7 Click the Change tab. 8 Confirm, and change if required, the parameter values to match the ones listed below NUT Time SMAX Parameter UMAX 20 Number of Repeaters 0 Cable Length 6250 microseconds Value Highest MAC Address of all modules on the I/O ControlNet segment 1000 (meters) 32

33 5 ALLEN-BRADLEY DRIVE INTERFACE CONFIGURATION Cable Usage Parameter Value A+B (for dual media cable configuration) - or -A (for single media cable configuration) 9 If you are not using fiber optic media, clear the My System uses Fiber Optics option. 10 If you did not change any of the parameter values, click Cancel and continue to step Click the OK button. 12 Click Yes to acknowledge the confirmation messages. Wait for the data transfer to complete. 13 Click OK to acknowledge the completion of the update without errors. 14 If a communications message dialog appears, click OK to acknowledge the message dialog and then click the Pause button on the toolbar to halt the network scan. 15 On the Network Tools menu, click Exit to close the application. 16 This completes the procedure. Go to the next section. 33

34 5 ALLEN-BRADLEY DRIVE INTERFACE CONFIGURATION 5.4 About Adding Allen-Bradley DRIVE block to Project Please refer to the Control Building User s Guide for basic functionality details about calling up, navigating and interacting with the application. Also, be aware that menus, selections, tree views, and configuration forms may vary depending upon the licensed options installed on your system. You can only view I/O Module blocks in the Project tab set for Assignment view. The Assignment view shows the relationship among all blocks while the Containment view only shows templates that contain other templates or Control Modules (CM), Sequential Control Modules (SCM), and basic blocks. To toggle the view, right-click in an open area of the tab window and select Assignment View or Containment View from the list, as applicable. Each A-B Drive I/O module block represents both the communications adapter and the given Allen-Bradley drive as one entity. The A-B Drive blocks are similar to other Chassis I/O module blocks and share many common parameters. The 1305 and 1336-PLUS-II drive blocks represent both the 1203-CN1 communications adapter and their associated hardware devices. The Generic drive blocks represent both the 1203-CN1 communications adapter and any A-B generic drive. The POWERFLEXDRIVE block represents both the 20-COMM-C communications adapter and the PowerFlex drive. The 700S drive block represents both the 20-COMM-C communications adapter and the PowerFlex 700S drive. The A-B Drive I/O module block receives input data from the module consisting of a drive status word, analog frequency feedback, and any optional datalink information. The Drive-Input channel block fetches this data to be used in a control strategy. The A-B Drive I/O module block also receives data from the control strategy through the Drive_Output and Analog Output channel blocks consisting of a logic control word, analog frequency reference, and any optional datalink information. This data is sent to the drive. You make the I/O Channel to I/O Module assignments for A-B drive blocks as you would for other Series A Chassis I/O Module blocks. The following table lists the specific channel numbers and block types used. Channel Number 0 Drive Input Channel 1 Drive Output Channel 2 Analog Output Channel Block Type The IO module function blocks only handle configuration information for datalink enabling from the C200 Controller's perspective. The device must be configured independently using Allen-Bradley configuration tools. You can choose to enable any combination of datalinks A to D. If you enable datalink A, the C200 controller will expect the assembly received from the drive to contain the two parameter values configured for datalink A in both the communications adapter and the drive. The block module name can be up to 16 characters long and must contain at least one letter (A-Z). It must not contain an embedded space or leading space, and dots are allowed in parameter naming only. The item name can be up to 40 characters long and must contain at least one letter (A-Z). It is a name by which an entity is known within the context of the enterprise model. The Item name must be unique among children of the same containment parent in the Enterprise Model Builder hierarchy and should conform to the standard convention for names within the system. The IOM Slot Number (IOMSLOT) field on the Main tab of the configuration form for the A-B Drive IOM block is not used, since the communications adapter sits directly on the ControlNet and not in a chassis slot. Press the F1 key to call up online help for the selected parameter in Control Builder. 34

35 5 ALLEN-BRADLEY DRIVE INTERFACE CONFIGURATION The illustrations used in the following procedure are for example purposes only PowerFlex drive configuration considerations The different PowerFlex drives support different data types. The drive and channel blocks must know the data type of the parameters sent to and from the drive through the datalinks to perform proper data scaling and range checking. Within the Experion Controller, the data types are only configured on the A-B Drive block. The Channel blocks retrieve data type information from the A-B Drive block at run time. See the Control Component Library (CCL) Help for more information about the valid values for data type parameters. The PowerFlex 700S drive operation requires additional Experion Controller configuration for proper scaling of the AOCHANNEL's (AOC) output (OP) parameter. You must set the values of the parameters listed in the following table to match the corresponding PowerFlex 700S parameters. Table 5: PowerFlex 700S Configuration Parameters Experion Parameter Description PowerFlex 700S Parameter MOTORNPRPM Motor Nameplate Rated RPM Par 4 - Motor NP RPM MAXSPDREFLIM Maximum Speed Reference Limit Par 31 - Max Spd Ref Lim MINSPDREFLIM Minimum Speed Reference Limit Par 30 - Min Spd Ref Lim The following illustration and description shows how the parameters influence the scaling. Figure 6: Typical PowerFlex 700S scaling for AOCHANNEL output. If... Then,... AOC.OP = 0.0 Speed Reference is always set to 0. Command Direction is Forward the valid range for Speed Reference is 0 to Par 31 - Max Spd Ref Lim. And, the AOCHANNEL's output (OP) represents the scaled Speed Reference from 0 to 100 where: AOC.OP = 0.0 corresponds to Speed Reference = 0.0, and AOC.OP = corresponds to the Max Spd Ref Lim. 35

36 5 ALLEN-BRADLEY DRIVE INTERFACE CONFIGURATION If... Then,... Command Direction is Reverse AOC.OP = corresponds to the Min Spd Ref Lim where: AOC.OP = 0.0 corresponds to Speed Reference = 0.0, and AOC.OP = corresponds to Min Spd Ref Lim Creating A-B Drive Interface Block The following procedure creates a 1305 drive block for example purposes only. You can easily adapt the procedure to create a 1336 PLUS II, GENERIC, POWERFLEXDRIVE, or 700S drive block instead. 1 On the File menu, Click New > I/O Modules > AB_DRIVE_IF Allen-Bradley AC Drive. Calls up the 1305 block parameters configuration form Main tab with default name entered in the Module Name box, as shown in the following sample illustration. 2 If you want to change the default name, double-click the Module Name box and key in the desired name. Otherwise, go to Step 3. 3 With cursor in the Item Name box and key in the name of the item that this object will be associated with in the Enterprise Model Builder hierarchy. 4 Click the Module Description box and key in the desired descriptive text to be used on displays. 5 Double-click the Remote IO Chassis MAC Address (ULCNBMAC) box and key in the MAC address of the 1203-CN1 communications adapter for this drive. 6 Double-click the ControlNet Module Slot Number (connected to IO Chassis) (DLCNBSLOT) box and key in the number of the slot the downlink CNI module occupies in the C200 Controller chassis. 7 Click the Module Configuration tab to display it. 36

37 5 ALLEN-BRADLEY DRIVE INTERFACE CONFIGURATION 8 Be sure the check box for the Alarming Enabled function is checked, if you want alarm reporting enabled. A blank check box means that the alarm reporting function is disabled. 9 Click the check box(es) for the Datalink(s) A to D that you want to enable, as shown in the following sample illustration. If you are configuring a PowerFlex drive, see the previous PowerFlex drive configuration considerations section for additional configuration details. CAUTION You must be absolutely certain that the datalink configuration you enter on the Module Configuration tab for the drive perfectly matches the configuration of the communications adapter. Failure to do this may result in the inability to establish a connection to the device, inaccurate and faulty data (provided by this block), and unexpected and undesirable behavior of any control strategy using this data. 10 Click the Server History tab to display it. 11 Use this tab to configure desired history parameters and create or edit server scripts. See the Control Building Guide and/or the online help for more information. 12 Click the Server Displays tab to display it. 13 Use this tab to configure parameters associated with Station displays. See the Control Building Guide and/or the online help for more information. The default Point Detail and Group Detail display selections should be as noted below. A-B Drive Type Point Detail Display Group Detail Display Legacy SCANport sysdtlabda sysdtlabda_fp 37

38 5 ALLEN-BRADLEY DRIVE INTERFACE CONFIGURATION A-B Drive Type Point Detail Display Group Detail Display PowerFlex (except 700S) sysdtlabdpfa sysdtlabdpfa_fp PowerFlex 700S sysdtlabdpf700sa sysdtlabdpf700sa_fp 14 Click the Control Confirmation tab to display it. 15 Use this tab to configure parameters for control confirmation associated with the licensed Electronic Signature option. See the Control Building Guide and/or the online help for more information. 16 Click the Identification tab to display it 17 Use this tab to configure parameters associated with the licensed template option. See the Control Building Guide and/or the online help for more information. 18 When you completed entering configuration data, click the OK button to close the configuration form and add the icon for the A-B drive to the Project tab. 19 This completes the procedure. Go to the next section. 38

39 5 ALLEN-BRADLEY DRIVE INTERFACE CONFIGURATION 5.5 About adding Drive I/O Channel to Control Module You can add a DRIVE_INPUT, POWERFLEX_IN, 700S_IN, DRIVE_OUTPUT, POWERFLEX_OUT, 700S_OUT and/or native AOCHANNEL block to a Control Module to support A-B drive I/O communications DRIVE_INPUT block functional overview The DRIVE_INPUT, POWERFLEX_IN, or 700S_IN function block serves as an input channel that fetches real-time data from the given Allen-Bradley drive module function block for use in control strategies. The input data consists of the information within the Drive Status word, Analog Frequency Reference Feedback, and any optional Datalink parameters along with appropriate scaling factors, as shown in the illustration below. Figure 7: Typical DRIVE_INPUT Block A-B Drive Data Exchange DRIVE_OUTPUT block functional overview The DRIVE_OUTPUT, POWERFLEX_OUT, and 700S_OUT function block serve as output channels that send real-time data from control strategies to the given A-B drive module function block. The output data consists of the information within the Logic Control word, as defined in the A-B Drive User Manuals, and any optional Datalink parameters along with appropriate scaling factors, as shown in the illustration below. 39

40 5 ALLEN-BRADLEY DRIVE INTERFACE CONFIGURATION Figure 8: Typical DRIVE_OUTPUT Block A-B Drive Data Exchange AOCHANNEL block functional overview for drive interface The AOCHANNEL function block allows the control strategy to set the Analog Frequency Reference of the associated Allen-Bradley drive, as shown in the illustration below. The AOCHANNEL block's output (OP) parameter is the scaled speed reference between 0 and 100 percent, where 100 percent represents the maximum speed configured on the device. See the Analog frequency reference and feedback on page 15 section for more information. Figure 9: Typical AOCHANNEL Block A-B Drive Data Exchange Using the AOCHANNEL block, provides full back initialization to the control strategy. Any loss of the downstream communication path will assert the AOC's INIT_REQ parameter. A bumpless transition will occur upon restoration of the communication path. 40

41 5 ALLEN-BRADLEY DRIVE INTERFACE CONFIGURATION Attention The AOCHANNEL will NOT request initialization when the Drive is not running. If the Drive is stopped, the AOCHANNEL accepts writes to OP even though the speed reference feedback will not be updated. When the Drive is commanded to start, the OP does NOT back initialize to 0. The current OP value will be sent to the drive and the drive will accelerate based on its configured rates. You can set the output direction for the AOCHANNEL block through the OPTDIR parameter as either DIRECT or REVERSE acting. The default setting is DIRECT. The DIRECT or REVERSE action simply determines if the OP range before conversion is 0 to 100% (DIRECT) or 100 to 0% (REVERSE). Initialization takes reverse output direction into consideration, so that the initialization value is consistent with the OP parameter, which is always ranged from 0 to 100%. In Monitoring mode, you can only change OPTDIR if the control block itself is inactive, which requires Engineer Level access, or unless the assigned control module is in an IDLE state. Any attempt to change OPTDIR for an AOCHANNEL block or PWMCHANNEL block triggers a message indicating the reason that the request was blocked Adding DRIVE_INPUT block to CM The following procedure adds a DRIVE_INPUT block to a CM and assigns a channel to a corresponding A-B drive for example purposes only. You can easily adapt this procedure to apply to POWERFLEX_IN or 700S_IN block as well as a DRIVE_OUTPUT, POWERFLEX_OUT, 700S_OUT, or AOCHANNEL block. Each block is automatically assigned a unique default channel name when it is created. If your system will include multiple IOCHANNEL blocks, you may want to adopt a more structured syntax for naming them. The channel name can be up to 16 characters long and must contain at least one letter (A-Z). It must not contain an embedded space or leading space, and dots are allowed in parameter naming only. The A-B Drive input/output channel blocks execute as dependent blocks at the base period of the Control Module (CM). The Drive input block fetches the most recent input data from the A-B Drive block. The Drive output block sends commands it has received from the control strategy to the associated A-B Drive block The A-B Drive input/output channel blocks support all of the parameters typically associated with I/O Channel blocks, in general, in the Experion system. In addition there are supported parameters that are specific to the A- B Drive input or output block itself. See the Control Component Library (CCL) Help for detailed parameter definitions. All illustrations used in the following procedure are for example purposes only. Prerequisites You have started Configuration Studio and launched the Control Builder application. You have logged on with sufficient privileges to create control strategies using Control Builder. You have added an Allen-Bradley Drive block to the Projecttab. You have created a Control Module in the Projecttab. To add DRIVE_INPUT block to CM 1 In the Project tab, double-click the icon for the Control Module that is to include a DRIVE_INPUT block to open it in the Control Drawing pane, as shown in the following sample illustration. 41

42 5 ALLEN-BRADLEY DRIVE INTERFACE CONFIGURATION 2 In the Library tab, scroll to the AB_DRIVE_IF icon and click the plus sign to expand the tree. 3 Click and drag the icon for the DRIVE_INPUT block to the open CM in the Control Drawing to add the block to the CM, as shown in the following sample illustration. 42

43 5 ALLEN-BRADLEY DRIVE INTERFACE CONFIGURATION 4 Double-click the DRIVE_INPUT block to open its configuration parameters form. 5 Accept the highlighted default Channel Name or key in a new one. 6 Select the Execution Order in CM box and key in the desired number in multiples of 10 to define the execution order of the block in the CM. 7 Click the down arrow in the Module Name box and select the A-B Drive to be associated with this channel. Once the drive is selected, the Module Typeand Channel Numberfields are automatically updated, as shown in the following sample illustration. 43

44 5 ALLEN-BRADLEY DRIVE INTERFACE CONFIGURATION 8 In the Channel Number list box, click the desired drive channel number this channel block is to be assigned to. Channel 0 is the default selection. 9 Click the Assign Channel Block button to assign this channel to the selected drive channel number. The Channel Name field and the Assigned to fields are automatically updated, as shown in the following sample illustration. 10 Click the Datalink Configurationtab to display it. 11 Click cursor in the desired Descriptor (24 char), Drive Units Scale Factor, Minimum, or Maximum range value box and key in applicable data. Repeat as required to fill in all required fields, as shown in the sample illustration below. CAUTION You must be absolutely certain that the datalink configuration you enter on the Datalink Configuration tab of this block perfectly matches the datalink parameters configured in the drive device. You must also be sure that the corresponding datalink is enabled on the Module Configuration tab of the configuration form for the associated A-B Drive block. 44

45 5 ALLEN-BRADLEY DRIVE INTERFACE CONFIGURATION 12 Click the Identification tab to display it 13 Use this tab to configure parameters associated with the licensed template option. See the Control Building Guide and/or the online help for more information. 14 Click the Block Pinstab to display it. 15 Use this tab to configure the pins you want to expose for this block. See the Control Building Guide and/or the online help for more information. 16 Click the Configuration Parameters tab to display it. 17 Use this tab to configure the parameters to be displayed on the block in the Project mode. See the Control Building Guide and/or the online help for more information. 18 Click the Monitoring Parameters tab to display it. 19 Use this tab to configure the parameters to be displayed on the block in the Monitoring mode. See the Control Building Guide and/or the online help for more information. 20 Click the Block Preferences tab to display it. 21 Use this tab to configure the viewing preferences for the block. See the Control Building Guide and/or the online help for more information. 22 If you have a template license, click the Template Defining tab to display it. 23 Use this tab to select which parameters are to be template defining. See the Control Building Guide and/or the online help for more information. 24 When you completed entering configuration data, click the OK button to close the configuration form and save the data. 25 This completes the procedure. Go to the next section. 45

46 5 ALLEN-BRADLEY DRIVE INTERFACE CONFIGURATION 5.6 Assigning A-B Drive to Execution Environment All illustrations used in the following procedure are for example purposes only. Prerequisites You have started Configuration Studio and launched the Control Builder application. You have logged on with sufficient privileges to create control strategies using Control Builder. You have created a C200 Controller block in the Project tab. You have added an A-B Drive Interface block to the Project tab. To assign A-B Drive to CEE 1 On the Edit menu, click Execution Environment Assignment; or click the Execution Environment Assignment button on the toolbar to call up the Execution Environment Assignment dialog, as shown in the sample illustration below. 2 If the IOMs tab is not on display in the Available modules list box, click the tab to display it. Click the A-B Drive Interface module to be assigned to select it. 3 In the Assign To list box, click the CEE block that the A-B Drive is to be assigned to select it. 4 Click the Assign -> button to assign the selected module to the given CEE block. 5 Check that the A-B Drive Interface block now appears in the Assigned Modules list box for the given CEE block, as shown in the sample illustration below. Note that the equal symbol prefix means that the block has been assigned and the down arrow symbol 46

47 5 ALLEN-BRADLEY DRIVE INTERFACE CONFIGURATION prefix means that the block has been loaded to the Controller. 6 Click the Close button to exit the dialog and save the assignments. 7 This completes the procedure. Go to the next section. 47

48 5 ALLEN-BRADLEY DRIVE INTERFACE CONFIGURATION 5.7 Loading configuration data to A-B Drive The following procedure is based on doing an initial load of a block from the Project tab. You can also initiate a re-load of a block from the Monitoring tab. If you change the values of the datalink enabling configuration parameters, a re-load will fail. These parameters can change the sizes of the ASA connection points. If the datalink enabling parameters must be changed, delete the A-B Drive Interface block from the Controller in the Monitoring tab first and then reload the block from the Project tab. All the illustrations used in the procedure are for example purposes only. CAUTION The load operation is still an offline function. The Load Dialog box provides the ability to automatically inactivate a component during a load and then return the component to its active state. Do not use this automatic inactivate/ activate function, if your process cannot tolerate the load disruption and consequent delay in activation. In this case, you must manually toggle the component state through the Monitoring tab in Control Builder. Prerequisites You have started Configuration Studio and launched the Control Builder application. You have logged on with sufficient privileges to create control strategies using Control Builder. You have loaded the Controller and its execution environment. You have assigned the A-B Drive Interface block to the loaded Execution Environment To load A-B Drive block 1 In the Project tab, click the plus signs to expand the tree hierarchy for the Controller, CEE, and I/O icons, as required. 2 Right-click the A-B Drive icon and select Load from the menu to call up the Load dialog. 48

49 5 ALLEN-BRADLEY DRIVE INTERFACE CONFIGURATION Be sure the check box in the Load column is checked. Click the down arrow in the Post Load State column to select another state. Check the check box at the bottom of the dialog to automatically change the state of the A-B Drive to the selected Post Load State after the load is completed. 3 Click the OK button to initiate the load and track progress through the Load Monitor dialog. 4 After load completes, check that the A-B Drive icon now appears in the Monitoring tab tree hierarchy. 5 This completes the procedure. Go to the next section. 49