ABB Drives User’s Manual DeviceNet Adapter Module FDNA-01
DeviceNet Adapter Module FDNA-01 User’s Manual 3AFE68573360 Rev C EN EFFECTIVE: 09.10.2007 © 2007 ABB Oy. All Rights Reserved.
Safety instructions Overview This chapter states the general safety instructions that must be followed when installing and operating the FDNA-01 DeviceNet Adapter module. The material in this chapter must be studied before attempting any work on, or with, the unit. In addition to the safety instructions given below, read the complete safety instructions of the specific drive you are working on.
Safety instructions
Table of contents Safety instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 General safety instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Table of contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Introduction . . . . . . . . . . . . . . . . . .
Electrical installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . General cabling instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DeviceNet connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DeviceNet bus termination . . . . . . . . . . . . . . . . . . . . . . . . . . .
Assembly objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 BASIC SPEED CONTROL assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 BASIC SPEED CONTROL PLUS DRIVE PARAMETERS assembly . . . . 71 EXTENDED SPEED CONTROL assembly . . . . . . . . . . . . . . . . . . . . . . . 74 EXTENDED SPEED CONTROL PLUS DRIVE PARAMETERS assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 LED indications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 Definitions and abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129 Technical data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133 FDNA-01 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Introduction Intended audience The manual is intended for people responsible for installing, commissioning and using an FDNA-01 DeviceNet Adapter module. The reader is expected to have a basic knowledge of electrical fundamentals, electrical wiring practices and how to operate the drive. Before you start It is assumed that the drive is installed and ready to operate before starting the installation of the extension module.
Drive configuration explains how to program the drive before the communication through the adapter module can be started. Master configuration explains how to program the DeviceNet master before communication through the adapter module can be started. Communication profiles describes the communication profiles used in the communication between the DeviceNet network, the FDNA-01 module and the drive. Communication contains a description of the DeviceNet functionality supported by the FDNA-01.
Overview Overview This chapter contains a short description of the DeviceNet standard and the FDNA-01 Adapter module, and a delivery checklist. DeviceNet standard The DeviceNet network has a linear bus topology. Terminating resistors are required on each end of the trunk line. Drop lines as long as 6 metres (20 feet) each are permitted, allowing one or more nodes to be attached. DeviceNet allows branching structures only on drop lines. An example of an allowable topology is shown in Figure 1.
Terminating resistor The DeviceNet network should be terminated at both ends of the trunk cable with a 121 Ω, ¼ W, 1% Metal Film resistor. Connect this resistor between the two signal wires (CAN_H, CAN_L) on the DeviceNet cable. The FDNA-01 DeviceNet Adapter module The FDNA-01 DeviceNet Adapter module is an optional device for ABB drives which enables the connection of the drive to a DeviceNet network. The drive is considered as a slave in the DeviceNet network.
DeviceNet master ABB drive Other slave device Diagnostic LEDs (See chapter Diagnostics) Bus connector X1 (see chapter Electrical installation) Figure 2. The construction of the DeviceNet link and the FDNA-01 Adapter module. Compatibility The FDNA-01 is compatible with all master stations that support the DeviceNet protocol.
Delivery check The option package for the FDNA-01 DeviceNet Adapter module contains: • DeviceNet Adapter module, type FDNA-01 • this manual.
FDNA-01 Quick Start Guide Overview This document presents the steps to take during the start-up of the FDNA-01 DeviceNet Adapter Module. PLC Configuration This is an example on how to set up an Allen-Bradley CompactLogix PLC with a 1769-SDN DeviceNet Scanner to use an ACS350 or ACSM1 equipped with a FDNA-01 fieldbus adapter, using RSNetWorx and RSLogix 5000 to configure and control the network. Slight vendor specific differences may exist when using other programs or master devices.
• Add drive to network in RSNetWorx for DeviceNet. • Configure device MAC address.
FDNA-01 Quick Start Guide
• Configure the DeviceNet Scanner. Add the drive to Scanlist and edit I/O parameters. Select Polled or Change of State/Cyclic. Then enter the input and output sizes of the I/O assemblies that will be used (e.g. for Basic Speed Control Assemblies 20 and 70, each size is set to 4 bytes.). • For convenience, you can also edit the Input and Output memory mappings. By default, the two 16-bit input words are mapped into a single 32-bit double word.
• Download the scanner settings to the device in online mode. • Add your DeviceNet scanner to an RSLogix 5000 project. You should get new Controller Tags Local::I and Local::O. You can use them to access the data as mapped above: Local::O.Data[0] is the Control Word Local::O.Data[1] is the Reference Local::I.Data[0] is the Status Word Local::I.Data[1] is the Actual Value Note: You may need to change the value of Local::O.CommandRegister.
Local::I.CommandRegister.Run to 1. Mechanical and electrical installation • Insert the FDNA-01 into its specified slot in the drive • Fasten the screw • Plug the fieldbus connector into the module Note: It is recommended to set module communication settings (e.g. Baud rate) before connecting it to an active DeviceNet network (see below). Drive configuration Note: Configuring the drive for communication with the module is dependent on the drive type.
Note: The new settings take effect only when the module is powered up the next time or when a 'Fieldbus Adapter parameter refresh' is given (see the drive documentation). Example Configuration: ODVA Basic Speed Control on ACS350 Drive parameter Example setting for ACS350 10.01 EXT1 COMMANDS COMM 11.03 REF1 SELECT COMM 16.01 RUN ENABLE NOT SEL1 16.04 FAULT RESET SEL COMM 98.02 COMM PROT SEL EXT FBA 51.01 FBA TYPE 51.02 MAC ID 51.03 BAUD RATE DEVICENET 2 0 (125 kbit/s) 51.
Example Configuration: ABB Drives Profile w/ Speed and Torque plus Drive Parameters on ACS350. Output Drive Parameters will control Analog Output 1 and Relay Output 1. Input Drive Parameters will read Analog Input 1 (01.20), Current (01.04) and Power (01.06). Drive parameter Example setting for ACS350 10.01 EXT1 COMMANDS COMM 11.03 REF1 SELECT COMM 11.05 REF2 SELECT COMM 14.01 RELAY OUTPUT 1 COMM 15.01 AO1 CONTENT SEL COMM VALUE 1 16.01 RUN ENABLE COMM1 16.04 FAULT RESET SEL COMM 98.
55.01 FBA DATA OUT 1 135 (01.35 COMM VALUE 1) 55.02 FBA DATA OUT 2 134 (01.34 COMM RO WORD) 55.03 - 55.10 FBA DATA OUT 3-10 0 (Unused) 1 The ABB Drives Profile does provide a means to supply a RUN ENABLE signal via DeviceNet. The RUN ENABLE for the drive may be set to COMM or another source (e.g. a digital input). 2 These parameters are ignored when using ABB Drives profile. 3 OUTPUT NUM PARS and INPUT NUM PARS should always be set to 10, except as provided for in the Appendix.
51.08 INPUT INSTANCE 73 (ODVA Extended Speed and Torque Control) 51.09 INPUT NUM PARS 101 51.10 ODVA SPEED SCALE 128 (1 RPM) 51.11 ODVA TORQUE SCALE 1 128 (1 Nm) OUTPUT NUM PARS and INPUT NUM PARS should always be set to 10, except as provided for in the Appendix Scanner: Input and Output sizes are 6 bytes each Example configuration: ABB Drives profile with Speed control with ACSM1 Drive parameter 10.01 EXT1 START FUNC 24.01 SPEED REF1 Example setting for ACSM1 FBA FBA REF1 34.
2 OUTPUT NUM PARS and INPUT NUM PARS should always be set to 10, except as provided for in the Appendix.
FDNA-01 Quick Start Guide
Mechanical installation WARNING! Follow the safety instructions given in this manual and the drive documentation. Mounting The FDNA-01 is to be inserted into its specific position in the drive. The module is held in place with plastic pins and one screw. The screw also provides the earthing of the fieldbus cable shield connected to the module. On installation of the module, the signal and power connection to the drive is made through a 20-pin connector.
Mechanical installation
Electrical installation Overview This chapter contains: • general cabling instructions • instructions for connecting the module to the DeviceNet bus. WARNING! Before installation, switch off the drive power supply. Wait 5 minutes to ensure that the capacitor bank of the drive is discharged. Switch off all dangerous voltages connected from external control circuits to the inputs and outputs of the drive. General cabling instructions Arrange the bus cables as far away from the motor cables as possible.
DeviceNet connection The bus cable is connected to terminal block X1 on the FDNA-01. Terminal block description.
Standard open-style screw connector +24 V Network power supply 0 V 1 2 3 4 5 1 2 3 4 5 VCAN_L SHLD CAN_H V+ FDNA X1 DeviceNet bus termination The FDNA-01 does not provide bus termination.The DeviceNet bus line must be terminated with 121 ohm resistors connected between the CAN_L and CAN_H wires at each end as shown below.
Electrical installation
Drive configuration Overview This chapter gives information on configuring the FDNA-01 DeviceNet Adapter module. DeviceNet connection configuration After the FDNA-01 DeviceNet Adapter module has been mechanically and electrically installed according to the instructions in chapters Mechanical installation and Electrical installation, the drive must be prepared for communication with the module.
FDNA-01 Configuration Parameters - Group 1 Table 3. FDNA-01 Configuration Parameters - Group 1 * Par. no. Parameter name Alternative settings Default setting 1 FBA TYPE (Read-only) DEVICENET 2 MAC ID 0 to 63 63 3 BAUD RATE (0) 125 kbit/s; (1) 250 kbit/s; (2) 500 kbit/s (0) 125 kbit/s 4 DRIVE PROFILE (0) DCU Profile (0) DCU Profile 5 ODVA STOP FUNC (0) Ramp Stop; (1) Coast Stop (0) Ramp Stop 6 OUTPUT INSTANCE See Table 4.
1 FBA TYPE This parameter shows the fieldbus adapter type as detected by the drive. The value cannot be adjusted by the user. If this parameter is undefined, the communication between the drive and the module has not been established. 2 MAC ID Each device on the DeviceNet network must have a unique MAC ID number. This parameter is used to define the MAC ID number for the drive it is connected to. 3 BAUD RATE Sets the baud rate for the DeviceNet interface.
descriptions of assembly instances, see Communication Assembly Objects.
Table 4.
Output Instance Input Instance Default Input Size (bytes) Profile Transparent32 w/Two 822 872 12 Transparent32 Profile Transparent32 w/One plus Drive Parameters 921 971 28 Transparent32 Profile Transparent32 w/Two plus Drive Parameters 922 972 32 Transparent32 Profile Name Note: With ACSM1, when using ODVA AC/DC Drive or ABB Drives profile, make sure that the drive parameter 50.4 FBA REF MODESEL is set to SPEED and 50.5 FBA REF2 MODESEL is set to TORQUE. Table 5.
10 ODVA SPEED SCALE This parameter only applies when using the ODVA AC/DC Drive Profile. Units of reference and actual speeds for ODVA AC/DC Drive profiles are given by the formula below. This parameter does not affect ABB Drives profiles. Note that while a wide range of resolutions may be configured, actual performance will be limited to the performance capabilities of the drive. Speed Unit = RPM X 2(-1 X ODVA Speed Scale Value) Table 6.
11 ODVA TORQUE SCALE This parameter only applies when using the ODVA AC/DC Drive Profile. Units of reference and actual torques for ODVA AC/DC Drive profiles are given by the formula below. This parameter does not affect ABB Drives profiles. Note that while a wide range of resolutions may be configured, actual performance will be limited to the performance capabilities of the drive. (Nm = Newton x Meter) Torque Unit = Nm x 2(-1 X ODVA Torque Scale) Table 7.
FDNA-01 Configuration Parameters - Group 2 (output data) Table 8. FDNA-01 Configuration Parameters - Group 2 Par. no. Parameter name Alternative settings Default setting 1 DATA OUT 1 (master to drive) 0 to 9999 Format: xxyy, where xx = parameter group and yy = parameter index. 0 2 DATA OUT 2 See DATA OUT 1 above. 0 3 DATA OUT 3 See DATA OUT 1 above. 0 4 DATA OUT 4 See DATA OUT 1 above. 0 5 DATA OUT 5 See DATA OUT 1 above. 0 6 DATA OUT 6 See DATA OUT 1 above.
*Actual parameter group number depends on the drive type. E.g. Group#2 equals to parameter Group 55 in ACS350 or group 53 in ACSM1. 2-10 DATA OUT 2 to DATA OUT 10 See DATA OUT 1 above. FDNA-01 Configuration Parameters - Group 3 (Input data) Table 9. FDNA-01 Configuration Parameters - Group 3* Par. no. Parameter name Alternative settings Default setting 1 DATA IN 1 (drive to master) 0 to 9999 Format: xxyy, where xx = parameter group and yy = parameter index. 0 2 DATA IN 2 See DATA IN 1 above.
Parameter numbers are formatted as xxyy, where xx is the parameter group number (1 to 99) and yy is the parameter index within that group (01 to 99). For example, parameter 99.02 would be entered as 9902. *Actual parameter group number depends on the drive type. E.g. Group#3 equals to parameter Group 54 in ACS350 or group 52 in ACSM1. 2-10 DATA IN 2 to DATA IN 10 See DATA IN 1 above. NOTE: The FDNA-01 configuration parameters are 16-bit parameters.
Drive configuration
Master configuration Overview This chapter gives information on configuring the DeviceNet master station for communication through the FDNA-01 DeviceNet Adapter module. Configuring the system After the FDNA-01 DeviceNet Adapter module has been mechanically and electrically installed according to the instructions in previous chapters, and has been initialized by the drive, the master station must be prepared for communication with the module.
Master configuration
Communication profiles Overview This chapter describes the communication profiles used in the communication between the DeviceNet network, the FDNA-01 module, and the drive. Communication profiles Communication profiles are ways of conveying control commands (Control word, Status word, references and actual values) between the master station and the drive. With the FDNA-01 module, the DeviceNet network may employ either the ODVA AC/DC Drive profile or the ABB Drives profile.
FDNA-01 DeviceNet network Drive FDNA-01 profile selection: ODVA AC/DC ODVA AC/DC profile Data conversion DCU profile ABB Drives ABB Drives profile Data conversion *Drive-specific profile (with 16-bit words) Transparent16 *Drive-specific profile (with 32-bit words) Transparent32 DCU profile *To be used if the drive does not support the DCU communication profile.
The ODVA AC/DC Drive Profiles This section briefly describes the ODVA AC/DC Drive Profiles. Additional information can be obtained from www.odva.org. A DeviceNet node is modeled as a collection of abstract objects. Each object represents the interface to and behaviour of a component within the product. The ODVA AC/DC Drive Profiles define a collection of objects suitable for the control of AC and DC drives. Objects supported by the FDNA-01 DeviceNet Adapter are listed in Communications – Class Objects.
ODVA Output Attributes This section briefly describes the instances found in the ODVA AC/DC Drive Profiles output assemblies. Not all attributes listed here will be supported by all output assembly instances. Run Forward & Run Reverse (Control Supervisor Object) These attributes are used to assert run and stop commands to Control Supervisor Object state machine (see “State” below) according to the following table. Table 10.
Scalar Mode When the drive is operating in scalar mode, the FDNA-01 provides the drive with a frequency reference. The ODVA AC/DC Drive Profiles use rpm units for the speed reference. The drive frequency reference is calculated according to Dfr Drive Frequency Reference in Hz Osr ODVA Speed Reference Us ODVA Speed Unit (from Table 6) Mf Motor Nominal Frequency in Hz Mss Motor Synchronous Speed in rpm (not Motor Nominal Speed).
Dsr = Osr × Us = 900 × 0.5rpm = 450rpm Torque Reference (AC/DC Drive Object) This attribute is the torque reference for the drive. The units are scaled by the Torque Scale attribute of the AC/DC Drive Object. See Table 7. for details. The FDNA-01 provides the drive with a torque reference in percent of motor nominal torque. The ODVA AC/DC Drive Profiles use Newton-meter (Nm) units for the torque reference.
ODVA Input Attributes This section briefly describes the instances found in the ODVA AC/DC Drive Profiles input assemblies. Not all attributes listed here will be supported by all input assembly instances. Faulted (Control Supervisor Object) This attribute indicates that the drive has experienced a fault. The fault code may be read from the FaultCode attribute of the Control Supervisor Object.
At Reference (AC/DC Drive Object) This attribute indicates the drive is operating at the specified speed or torque reference. State (Control Supervisor Object) This attribute indicates the current state of the Control Supervisor Object. Table 11. Control Supervisor States.
Non Existent ALM = Alarm DEC = Deceleration FWD = Forward REV = Reverse RDY = Ready Power off Power on Startup ALM=1 Faulted Power on Not Ready DEC=0 ALM=1 Power-on AND RDY Fault Stop Power-on AND not RDY Ready FWD OR REV FaultRst DEC=0 FWD OR REV Enabled Stopping ALM=1 DEC=1 ALM=1 Figure 12. ODVA state transition diagram Speed Actual (AC/DC Drive Object) This attribute indicates the actual speed at which the drive is operating.
Osa ODVA Speed Actual Dfa Drive Frequency Actual in Hz Us ODVA Speed Unit (from Table 6) Mf Motor Nominal Frequency in Hz Mss Motor Synchronous Speed in rpm (not Motor Nominal Speed). Osa = Dfa × Mss Mf × Us For a 4 pole 60 Hz motor (Mss = 1800 rpm) with a unit of 1 rpm and a Drive Frequency Actual or 30 Hz. Osa = Dfa × Mss 30Hz ×1800rpm = = 900 Mf × Us 60Hz × 1rpm Vector Mode When the drive is operating in vector mode, the drive provides the FDNA-01 with a speed actual.
Torque Actual (AC/DC Drive Object) This attribute indicates the actual torque at which the drive is operating. The units are scaled by the Torque Scale attribute of the AC/DC Drive Object. See Table 7. for details. The drive provides the FDNA-01 with a torque actual in percent of Motor Nominal Torque. The ODVA AC/DC Drive Profiles use Newton-meter (Nm) units for the torque actual.
The contents of the Control Word and the Status Word are detailed in Tables 13 and 14 respectively. The drive states are presented in the ABB Drives profile state machine (Figure 15). References References are 16-bit words containing a sign bit and a 15-bit integer. A negative reference (indicating reversed direction of rotation) is formed by calculating the two’s complement from the corresponding positive reference.
Scaling References are scaled as shown below. Note: The values of REF1 MAX and REF2 MAX are set by drive parameters. See the drive documentation for further information.
Actual values Actual values are 16-bit words containing information on the operation of the drive. The functions to be monitored are selected by a drive parameter. Scaling Actual values are scaled as shown below. Note: The values of REF1 MAX and REF2 MAX are set by drive parameters. See the drive documentation for further information.
Table 13. The Control Word for the ABB Drives communication profile. The upper case boldface text refers to the states shown in Figure 15. Bit 0 1 2 3 4 Name Value STATE/Description OFF1_ CONTROL 1 Proceed to READY TO OPERATE. 0 Stop along currently active deceleration ramp. Proceed to OFF1 ACTIVE; proceed to READY TO SWITCH ON unless other interlocks (OFF2, OFF3) are active. OFF2_ CONTROL 1 Continue operation (OFF2 inactive). 0 Emergency OFF, coast to stop.
Bit 5 6 7 Name RAMP_HOLD RAMP_IN_ ZERO RESET Value STATE/Description 1 Enable ramp function. Proceed to RAMP FUNCTION GENERATOR: ACCELERATOR ENABLED. 0 Halt ramping (Ramp Function Generator output held). 1 Normal operation. Proceed to OPERATING. Note: This bit is effective only if the fieldbus interface is set as the source for this signal by drive parameters. 0 Force Ramp Function Generator input to zero. 0=>1 Fault reset if an active fault exists. Proceed to SWITCH-ON INHIBITED.
Table 14. The Status Word for the ABB Drives communication profile. The upper case boldface text refers to the states shown in Figure 15. Bit 0 1 2 3 4 5 6 7 8 9 Name RDY_ON Value STATE/Description 1 READY TO SWITCH ON. 0 NOT READY TO SWITCH ON. 1 READY TO OPERATE. 0 OFF1 ACTIVE. 1 OPERATION ENABLED. 0 OPERATION INHIBITED. 1 FAULT. 0 No fault. 1 OFF2 inactive. 0 OFF2 ACTIVE. 1 OFF3 inactive. 0 OFF3 ACTIVE. SWC_ON_ INHIB 1 SWITCH-ON INHIBITED.
Bit Name 10 ABOVE_ LIMIT 11 12 Value STATE/Description 1 Actual frequency or speed equals or exceeds supervision limit (set by drive parameter). Valid in both directions of rotation. 0 Actual frequency or speed within supervision limit. EXT_CTRL_ LOC 1 External Control Location EXT2 selected. 0 External Control Location EXT1 selected.
SWITCH-ON INHIBITED MAINS OFF Power ON ABB Drives Communication Profile (SW Bit6=1) (CW Bit0=0) NOT READY TO SWITCH ON A B C D CW = Control Word SW = Status Word n = Speed I = Input Current RFG = Ramp Function Generator f = Frequency (SW Bit0=0) (CW=xxxx x1xx xxxx x110) (CW Bit3=0) READY TO SWITCH ON OPERATION INHIBITED (SW Bit0=1) (SW Bit2=0) operation inhibited (CW=xxxx x1xx xxxx x111) READY TO OPERATE from any state OFF1 (CW Bit0=0) OFF1 ACTIVE B C D (SW Bit1=1) (CW=xxxx x1xx xxxx 11
Communication profiles
Communication Overview This chapter describes the DeviceNet communication protocol for the FDNA-01 and the configuration of the scanner. For detailed information on DeviceNet communication, refer to ODVA DeviceNet Specifications Release 2.0. Introduction to DeviceNet DeviceNet is a protocol based on CAN technology. CAN specifies the physical layer interface. DeviceNet specifies the wiring, and the data transfer through CAN.
Assembly objects I/O Assembly Instances may also be referred to as Block Transfer of data. Intelligent devices realizing a Functional Profile, such as the FDNA-01, have several objects. Since it is not possible to transmit more than one object data through a single connection, it is practical and more efficient to group attributes from different objects into a single I/O connection (for example a Polled Connection) using the Assembly object.
BASIC SPEED CONTROL assembly The BASIC SPEED CONTROL assembly is defined by ODVA AC/ DC Drive Profile.
The format of the output assembly is: Instance 120 Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 0 Fault Reset 1 Communication 2 Speed Reference (Low Byte) 3 Speed Reference (High Byte) 4 DATA OUT 1 Value (Low Byte) 5 DATA OUT 1 Value (High Byte) 6 DATA OUT 2 Value (Low Byte) 7 DATA OUT 2 Value (High Byte) 8 DATA OUT 3 Value (Low Byte) 9 DATA OUT 3 Value (High Byte) 10 DATA OUT 4 Value (Low Byte) 11 DATA OUT 4 Value (High Byte) 12 DATA OUT 5 Value (Low Byte) 13 DATA OUT 5 Value (Hi
The format of the input assembly is: Instance 170 Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 0 Running Forward Bit 1 Bit 0 Faulted 1 2 Speed Actual (Low Byte) 3 Speed Actual (High Byte) 4 DATA IN 1 Value (Low Byte) 5 DATA IN 1 Value (High Byte) 6 DATA IN 2 Value (Low Byte) 7 DATA IN 2 Value (High Byte) 8 DATA IN 3 Value (Low Byte) 9 DATA IN 3 Value (High Byte) 10 DATA IN 4 Value (Low Byte) 11 DATA IN 4 Value (High Byte) 12 DATA IN 5 Value (Low Byte) 13 DATA IN 5 Value (High Byte)
EXTENDED SPEED CONTROL assembly The EXTENDED SPEED CONTROL assembly is defined by ODVA AC/DC Drive Profile.
The format of the output assembly is: Instance 121 Byte Bit 7 0 Bit 6 Bit 5 Bit 4 Net Ref Net Ctl Bit 3 Bit 2 Bit 1 Bit 0 Fault Run Run Reset Reverse Forward 1 2 Speed Reference (Low Byte) 3 Speed Reference (High Byte) 4 DATA OUT 1 Value (Low Byte) 5 DATA OUT 1 Value (High Byte) 6 DATA OUT 2 Value (Low Byte) 7 DATA OUT 2 Value (High Byte) 8 DATA OUT 3 Value (Low Byte) 9 DATA OUT 3 Value (High Byte) 10 DATA OUT 4 Value (Low Byte) 11 DATA OUT 4 Value (High Byte) 12 DATA OUT
The format of the input assembly is: Instance 171 Byte Bit 7 Bit 6 Bit 5 Bit 4 0 At Reference 1 Drive State (See Table 11.
BASIC SPEED AND TORQUE CONTROL assembly The BASIC SPEED AND TORQUE CONTROL assembly is defined by the ODVA AC/DC Drive Profile.
The format of the output assembly is: Instance 122 Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 0 Fault Reset 1 2 Speed Reference (Low Byte) 3 Speed Reference (High Byte) 4 Torque Reference (Low Byte) 5 Torque Reference (High Byte) 6 DATA OUT 1 Value (Low Byte) 7 DATA OUT 1 Value (High Byte) 8 DATA OUT 2 Value (Low Byte) 9 DATA OUT 2 Value (High Byte) 10 DATA OUT 3 Value (Low Byte) 11 DATA OUT 3 Value (High Byte) 12 DATA OUT 4 Value (Low Byte) 13 DATA OUT 4 Value (High Byte) 14 DAT
The format of the input assembly is: Instance 172 Byte Bit 7 Bit 6 Bit 5 Bit 4 0 Bit 3 Bit 2 Running Forward Bit 1 Bit 0 Faulted 1 2 Speed Actual (Low Byte) 3 Speed Actual (High Byte) 4 Torque Actual (Low Byte) 5 Torque Actual (High Byte) 6 DATA IN 1 Value (Low Byte) 7 DATA IN 1 Value (High Byte) 8 DATA IN 2 Value (Low Byte) 9 DATA IN 2 Value (High Byte) 10 DATA IN 3 Value (Low Byte) 11 DATA IN 3 Value (High Byte) 12 DATA IN 4 Value (Low Byte) 13 DATA IN 4 Value (High Byt
EXTENDED SPEED AND TORQUE CONTROL assembly The EXTENDED SPEED AND TORQUE CONTROL assembly is defined by the ODVA AC/DC Drive Profile.
The format of the output assembly is: Instance 123 Byte Bit 7 0 Bit 6 Bit 5 Bit 4 NetRef NetCtl Bit 3 Bit 2 Bit 1 Bit 0 Fault Run Run Reset Reverse Forward 1 2 Speed Reference (Low Byte) 3 Speed Reference (High Byte) 4 Torque Reference (Low Byte) 5 Torque Reference (High Byte) 6 DATA OUT 1 Value (Low Byte) 7 DATA OUT 1 Value (High Byte) 8 DATA OUT 2 Value (Low Byte) 9 DATA OUT 2 Value (High Byte) 10 DATA OUT 3 Value (Low Byte) 11 DATA OUT 3 Value (High Byte) 12 DATA OUT 4
The format of the input assembly is: Instance 173 Byte Bit 7 Bit 6 Bit 5 Bit 4 Ref From Net Ctrl From Net Ready Running Reverse 0 At Reference 1 Drive State (See Table 11.
ABB DRIVES PROFILE SET SPEED assembly The ABB DRIVES PROFILE WITH SET SPEED assembly is defined by ABB.
The format of the output assembly is: Instance 901 Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 0 Reset Ramp Ramp Ramp Inhibit Off 3 in Hold Out Opera- Control Zero Zero tion 1 Ext Ctrl Remote Loc Cmd 2 Set Speed (Low Byte) 3 Set Speed (High Byte) 4 DATA OUT 1 Value (Low Byte) 5 DATA OUT 1 Value (High Byte) 6 DATA OUT 2 Value (Low Byte) 7 DATA OUT 2 Value (High Byte) 8 DATA OUT 3 Value (Low Byte) 9 DATA OUT 3 Value (High Byte) 10 DATA OUT 4 Value (Low Byte) 11 DATA OUT 4 Value (
The format of the input assembly is: Instance 951 Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 0 Alarm Swc On Inhib Off 3 Sta Off 2 Sta Tripped Rdy Ref 1 Fieldbus Error 2 Actual Speed (Low Byte) 3 Actual Speed (High Byte) 4 DATA IN 1 Value (Low Byte) 5 DATA IN 1 Value (Low Byte) 6 DATA IN 1 Value (High Byte) 7 DATA IN 2 Value (Low Byte) 8 DATA IN 2 Value (High Byte) 9 DATA IN 3 Value (Low Byte) 10 DATA IN 3 Value (High Byte) 11 DATA IN 4 Value (Low Byte) 12 DATA IN 4 Value
ABB DRIVES PROFILE WITH SET SPEED AND SET TORQUE assembly The ABB DRIVES PROFILE WITH SET SPEED AND SET TORQUE assembly is defined by ABB.
ABB DRIVES PROFILE WITH SET SPEED AND SET TORQUE PLUS DRIVE PARAMETERS assembly The ABB DRIVES PROFILE WITH SET SPEED AND SET TORQUE PLUS DRIVE PARAMETERS assembly, defined by ABB, adds configurable drive parameters to the ABB DRIVES PROFILE WITH SET SPEED AND SET TORQUE of the ABB Drives Profile.
The format of the output assembly is: Instance 902 Byte Bit 7 0 Bit 6 Bit 5 Bit 4 Bit 3 Bit 1 Bit 0 Reset Ramp Ramp Ramp Inhibit Off 3 Off 2 Off 1 in Hold Out Opera- Control Control Control Zero Zero tion 1 Ext Ctrl Remote Loc Cmd 2 Set Speed (Low Byte) 3 Set Speed (High Byte) 4 Set Torque (Low Byte) 5 Set Torque (High Byte) 6 DATA OUT 1 Value (Low Byte) 7 DATA OUT 1 Value (High Byte) 8 DATA OUT 2 Value (Low Byte) 9 DATA OUT 2 Value (High Byte) 10 DATA OUT 3 Value (Low Byte)
The format of the input assembly is: Instance 952 Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 0 Alarm Swc On Inhib Off 3 Sta Off 2 Sta Tripped Rdy Ref 1 Fieldbus Error 2 Actual Speed (Low Byte) 3 Actual Speed (High Byte) 4 Actual Torque (Low Byte) 5 Actual Torque (High Byte) 6 DATA IN 1 Value (Low Byte) 7 DATA IN 1 Value (High Byte) 8 DATA IN 2 Value (Low Byte) 9 DATA IN 2 Value (High Byte) 10 DATA IN 3 Value (Low Byte) 11 DATA IN 3 Value (High Byte) 12 DATA IN 4 Value (Lo
Instance 952 Byte Bit 7 25 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 DATA IN 10 Value (High Byte) TRANSPARENT16 WITH ONE assembly The TRANSPARENT16 WITH ONE assembly, defined by ABB, provides unaltered 16-bit access to the configured drive profile.
TRANSPARENT16 WITH ONE assembly PLUS DRIVE PARAMETERS The TRANSPARENT16 WITH ONE assembly PLUS DRIVE PARAMETERS, defined by ABB, adds configurable drive parameters to the TRANSPARENT16 WITH ONE assembly.
The format of the input assembly is: Instance 961 Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 Communication 0 Drive Profile 16-bit Status Word (Low Byte) 1 Drive Profile 16-bit Status Word (High Byte) 2 Drive Profile 16-bit Actual 1 Word (Low Byte) 3 Drive Profile 16-bit Actual 1 Word (High Byte) 4 DATA IN 1 Value (Low Byte) 5 DATA IN 1 Value (High Byte) 6 DATA IN 2 Value (Low Byte) 7 DATA IN 2 Value (High Byte) 8 DATA IN 3 Value (Low Byte) 9 DATA IN 3 Value (High Byte) 10
TRANSPARENT16 WITH TWO assembly The TRANSPARENT16 WITH TWO assembly, defined by ABB, provides unaltered 16-bit access to the configured drive profile.
The format of the output assembly is: Instance 912 Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 Communication 0 Drive Profile 16-bit Control Word (Low Byte) 1 Drive Profile 16-bit Control Word (High Byte) 2 Drive Profile 16-bit Reference 1 Word (Low Byte) 3 Drive Profile 16-bit Reference 1 Word (High Byte) 4 Drive Profile 16-bit Reference 2 Word (Low Byte) 5 Drive Profile 16-bit Reference 2 Word (High Byte) 6 DATA OUT 1 Value (Low Byte) 7 DATA OUT 1 Value (High Byte) 8 DATA OU
The format of the input assembly is: Instance 962 Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 0 Drive Profile 16-bit Status Word (Low Byte) 1 Drive Profile 16-bit Status Word (High Byte) 2 Drive Profile 16-bit Actual 1 Word (Low Byte) 3 Drive Profile 16-bit Actual 1 Word (High Byte) 4 Drive Profile 16-bit Actual 2 Word (Low Byte) 5 Drive Profile 16-bit Actual 2 Word (High Byte) 6 DATA IN 1 Value (Low Byte) 7 DATA IN 1 Value (High Byte) 8 DATA IN 2 Value (Low Byte) 9 DATA IN 2
TRANSPARENT32 WITH ONE assembly The TRANSPARENT32 WITH ONE assembly, defined by ABB, provides unaltered 32-bit access to the configured drive profile.
The format of the output assembly is: Instance 921 Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 0 Drive Profile 32-bit Control Word (Low Byte) 1 Drive Profile 32-bit Control Word 2 Drive Profile 32-bit Control Word 3 Drive Profile 32-bit Control Word (High Byte) 4 Drive Profile 32-bit Reference 1 Word (Low Byte) 5 Drive Profile 32-bit Reference 1 Word 6 Drive Profile 32-bit Reference 1 Word 7 Drive Profile 32-bit Reference 1 Word (High Byte) 8 DATA OUT 1 Value (Low Byte) 9 DAT
The format of the input assembly is: Instance 971 Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 Communication 0 Drive Profile 32-bit Status Word (Low Byte) 1 Drive Profile 32-bit Status Word 2 Drive Profile 32-bit Status Word 3 Drive Profile 32-bit Status Word (High Byte) 4 Drive Profile 32-bit Actual 1 Word (Low Byte) 5 Drive Profile 32-bit Actual 1 Word (High Byte) 6 Drive Profile 32-bit Actual 1 Word 7 Drive Profile 32-bit Actual 1 Word (High Byte) 8 DATA IN 1 Value (Low Byt
TRANSPARENT32 WITH TWO assembly The TRANSPARENT32 WITH TWO assembly, defined by ABB, provides unaltered 32-bit access to the configured drive profile.
The format of the input assembly is: Instance 872 Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 0 Drive Profile 32-bit Status Word (Low Byte) 1 Drive Profile 32-bit Status Word 2 Drive Profile 32-bit Status Word 3 Drive Profile 32-bit Status Word (High Byte) 4 Drive Profile 32-bit Actual 1 Word (Low Byte) 5 Drive Profile 32-bit Actual 1 Word 6 Drive Profile 32-bit Actual 1 Word 7 Drive Profile 32-bit Actual 1 Word (High Byte) 8 Drive Profile 32-bit Actual 2 Word (Low Byte) 9 D
Instance 922 Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 8 Drive Profile 32-bit Reference 2 Word (Low Byte) 9 Drive Profile 32-bit Reference 2 Word 10 Drive Profile 32-bit Reference 2 Word 11 Drive Profile 32-bit Reference 2 Word (High Byte) 12 DATA OUT 1 Value (Low Byte) 13 DATA OUT 1 Value (High Byte) 14 DATA OUT 2 Value (Low Byte) 15 DATA OUT 2 Value (High Byte) 16 DATA OUT 3 Value (Low Byte) 17 DATA OUT 3 Value (High Byte) 18 DATA OUT 4 Value (Low Byte) 19 DATA OUT 4
The format of the input assembly is: Instance 972 Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 Communication 0 Drive Profile 32-bit Status Word (Low Byte) 1 Drive Profile 32-bit Status Word 2 Drive Profile 32-bit Status Word 3 Drive Profile 32-bit Status Word (High Byte) 4 Drive Profile 32-bit Actual 1 Word (Low Byte) 5 Drive Profile 32-bit Actual 1 Word 6 Drive Profile 32-bit Actual 1 Word 7 Drive Profile 32-bit Actual 1 Word (High Byte) 8 Drive Profile 32-bit Actual 2 Word
Instance 972 Byte Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 29 DATA IN 9 Value (High Byte) 30 DATA IN 10 Value (Low Byte) 31 DATA IN 10 Value (High Byte) Communication
Class objects Legend: Data type UINT8 Unsigned Integer 8 bit UINT16 Unsigned Integer 16 bit SINT16 Signed Integer 16 bit UINT32 Unsigned Integer 32 bit BOOL Boolean value Note: The FDNA-01 DeviceNet Adapter Module is designed to provide DeviceNet communications for a variety of drives with different capabilities. Default, minimum and maximum values for attributes necessarily vary based upon the capabilities of the drive to which the module is attached and are not documented herein.
Class Attributes # Attribute name Services Description Data type 1 Get Revision of the Identity Object Array of UINT8 Revision Instance Attributes # Attribute name Services Description Data type 1 Vendor ID Get Identification of the device vendor.
Revision Revision attribute, which consists of Major and Minor Revisions, identifies the Revision of the item the Identity Object is representing. Status This attribute represents the current status of the entire device. Its value changes as the state of the device changes. The Status attribute is a WORD, with the following bit definitions: Bit(s) Type/Name Definition 0 Owned TRUE indicates the device (or an object within the device) has an owner.
Bit(s) Type/Name 12,13,14,15 Definition Reserved, set to 0. ODVA Serial Number: This attribute is a number used in conjunction with the Vendor ID to form a unique identifier for each device on DeviceNet. The value of this attribute is 02000000h plus the SERNO value from the device label. Product Name: This text string should represent a short description of the product/ product family represented by the product code in attribute 3. State: Represents current state of Identity Object.
DeviceNet Object, Class 03h The DeviceNet Object provides the configuration and status of a DeviceNet port. Each DeviceNet product must support one (and only one) DeviceNet object per physical connection to the DeviceNet communication link.
Master’s MAC ID The range of values is 0…63 and 255 decimal. A value in the range of 0…63 indicates that the Predefined Master/Slave Connection Set is currently allocated, and denotes the MAC ID of the device that performed the allocation. The value 255 means the Predefined Master/Slave Connection set has not been allocated. The Master’s MAC ID attribute is initialized to 255 (FF hex) at device power-up/reset.
Connection Object, Class 05h The Connection Class allocates and manages the internal resources associated with both I/O and Explicit Messaging Connections. The specific instance generated by the Connection Class is referred to as Connection Instance or Connection Object. Table 16.
# Attribute name Services Description Data type 6 Comm Characteristics Get Defines the Message Group(s) across which productions and consumptions are associated in this Connection. UINT8 7 Produced Connection Size Get Maximum number of bytes transmitted across this Connection UINT16 8 Consumed Connection size Get Maximum number of bytes received across this Connection UINT16 9 Expected Packet Rate Get, Set Defines the timing associated with this UINT16 Connection in milliseconds.
Acknowledge Handler Object, Class 2Bh The Acknowledge Handler Object is used to manage the reception of message acknowledgements. This object communicates with a message producing Application Object within the device. The Acknowledge Handler Object notifies the producing application of acknowledge reception, acknowledge timeouts and production retry limit.
Motor Data Object, Class 28h This object serves as a database for motor parameters. Different motor types require different data to describe the motor. For example, AC induction motors do not need field current data like a DC motor to describe the motor.
# Attribute name Services Description Motor type Data type 15 Base Speed Get, Set AC/DC UINT16 Communication Nominal speed at rated frequency from nameplate Units [RPM]
Control Supervisor Object, Class 29h The object models all the management functions for devices within the ‘Hierarchy of Motor Control Devices’. The behaviour of motor control devices is described by the AC/DC-Drive Object, Class 2Ah and the Run/Stop event matrix. See Table 10 and Figure 12.
# Attribute name Services Description 14 Warning Code Get Code word indicating warning present. If UINT16 multiple warnings are present, the lowest code value is displayed. DRIVECOMM codes are reported. See Drive Manual for further information on DRIVECOMM codes.
AC/DC-Drive Object, Class 2Ah This object models the functions specific to an AC or DC Drive. Class Attributes # Attribute Services Description name 1 Revision Get Data type Revision of the DeviceNet Object Class Defi- Array of nition upon which the implementation is UINT8 based Instance Attributes # Attribute name Services Description Data type 3 At Reference Get Frequency arrival BOOL 4 NetRef Get, Set Requests torque or speed reference to be BOOL local or from the network.
Drive Parameter Object, Class 90h With the FDNA-01, drive parameters can also be accessed via Explicit Messaging. Explicit Messaging makes use of objects consisting of three parts, Class, Instance, and Attribute. Note: When using the Drive Parameter Object to update the fieldbus configuration groups take effect only when the module is powered up the next time or when a ‘Fieldbus Adapter parameter refresh’ is given. Class is always 144 (90h).
Fieldbus Configuration Object 91h The Fieldbus Configuration Object allows the user to configure the field bus configuration groups without needing to know the drive specific groups associated with the configuration groups.
Instance #1: FDNA-01 Configuration Parameters Group #1 * # Attribute name Services Description Data type 1 Configuration Group #1 Parameter 1 Get, Set See Drive configuration UINT16 2 Configuration Group #1 Parameter 2 Get, Set See Drive configuration UINT16 3 Configuration Group #1 Parameter 3 Get, Set See Drive configuration UINT16 4 Configuration Group #1 Parameter 4 Get, Set See Drive configuration UINT16 5 Configuration Group #1 Parameter 5 Get, Set See Drive configurati
# Attribute name 17 Configuration Group #1 - Services Description Data type Get, Set See Drive configuration UINT16 Get, Set See Drive configuration UINT16 Get, Set See Drive configuration UINT16 Get, Set See Drive configuration UINT16 Get, Set See Drive configuration UINT16 Get, Set See Drive configuration UINT16 Get, Set See Drive configuration UINT16 Get, Set See Drive configuration UINT16 Get, Set See Drive configuration UINT16 Get, Set See Drive configuration UINT
Instance #2: FDNA-01 Configuration Parameters Group #2 * # Attribute name Services Description Data type 1 Configuration Group #2 Parameter 1 Get, Set See Drive configuration UINT16 2 Configuration Group #2 Parameter 2 Get, Set See Drive configuration UINT16 3 Configuration Group #2 Parameter 3 Get, Set See Drive configuration UINT16 4 Configuration Group #2 Parameter 4 Get, Set See Drive configuration UINT16 5 Configuration Group #2 Parameter 5 Get, Set See Drive configurati
Instance #3: FDNA-01 Configuration Parameters Group #3 * # Attribute name Services Description Data type 1 Configuration Group #3 Parameter 1 Get, Set See Drive configuration UINT16 2 Configuration Group #3 Parameter 2 Get, Set See Drive configuration UINT16 3 Configuration Group #3 Parameter 3 Get, Set See Drive configuration UINT16 4 Configuration Group #3 Parameter 4 Get, Set See Drive configuration UINT16 5 Configuration Group #3 Parameter 5 Get, Set See Drive configurati
Communication
Diagnostics LED indications The FDNA-01 module is equipped with three bicolor diagnostic LEDs. The LEDs are described below. Name Color Function/State HOST Blinking green Establishing communication to host. Green Connection to host OK. Blinking red Communication to host lost temporarily.
Name Color Function/State MODULE Off There is no power applied to the device. Green The device is operating in a normal condition. Flashing green The device needs commissioning due to configuration missing, incomplete or incorrect. The device may be in the Standby state. Flashing red Recoverable fault. Red The device has an unrecoverable fault. This may be cleared by: a Fieldbus Adapter parameter refresh, cycling DeviceNet network power or cycling drive power.
Name Color Function/State NETWORK Off Device is not on-line. – The device has not completed the Dup_MAC_ID test yet. – The device may not be powered, look at Module Status LED. Flashing green Device is on-line but has not connections in the established state. – The device has passed the Dup_MAC_ID test, is on-line, but has no established connections to other nodes. – For a Group 2 Only device it means that this device is not allocated to a master.
Diagnostics
Definitions and abbreviations Change of State/Cyclic Message The Change of State/Cyclic Message is transmitted by either the Master or the Slave. A Change of State/Cyclic Message is directed towards a single specific node (point-to-point). An Acknowledge Message may be returned in response to this message. Communication Module Communication Module is a name for a device (e.g. a fieldbus adapter) through which the drive is connected to an external serial communication network (e.g. a fieldbus).
MAC ID Every node on DeviceNet network has to have a unique identifier. This node number is called MAC ID (Media Access Control ID). FDNA-01 DeviceNet Adapter module The FDNA-01 Adapter module is one of the optional fieldbus adapter modules available for ABB drives. The FDNA-01 is a device through which an ABB drive is connected to a DeviceNet serial communication bus. ODVA ODVA stands for Open DeviceNet Vendor Association.
Scanlist The DeviceNet Scanner communicates with the DeviceNet Slaves in a user-defined order. This order of communication is the scanlist. The scanlist contains a complete list of the Slave nodes and the order in which the Slaves are accessed.
Definitions and abbreviations
Technical data FDNA-01 Enclosure: Mounting: Into the option slot on the drive. Degree of protection: IP20 Ambient conditions: The applicable ambient conditions specified for the drive in its manuals are in effect. Indicators: Three bicolor LEDs (HOST, MODULE, NETWORK) Connectors: • 20-pin connector to drive • Removable 5-pole screw type connector for bus connection (max. 2.
Power supply: Input voltage • From Drive: +3,3V DC (+/- 5%) • From Network: +24V DC nominal (+11V to +30V) Input Current • From Drive: 180 mA typical, 300 mA maximum (+3.3V) • From Network: 20 mA typical, 50 mA maximum (+24V) General: • Estimated min.
Appendix - Varying Number of Drive Parameters Assembly object instances can either be dynamic or static. The FDNA-01 only supports static assembly objects. For each supported assembly, the member list (and implicitly the length in bytes) has been fixed either by the ODVA AC/DC Drive Profiles or ABB. FDNA-01 assemblies that include “plus Drive Parameters" have ten members each reserved for the output or input of drive parameters.
To change the EDS file, copy it to a new file name and open the copy with a text editor. Search for the [IO_Info] section of the file for the appropriate assembly. For example the entry for the Basic Speed Control Input plus Drive Parameters is below. Input7= 24, 0, 0x0005, Length in bytes "Basic Speed Control Input + Drive Parameters", 7, "20 04 24 AA 30 03", "Basic Speed Control Input + Drive Parameters"; The length in bytes needs to be updated to match the value from the table below.
Length in Bytes of Assemblies with Drive Parameters Number of Drive Parameters Assembly 1 2 3 4 5 6 7 8 9 10 120 6 8 10 12 14 16 18 20 22 24 121 6 8 10 12 14 16 18 20 22 24 122 8 10 12 14 16 18 20 22 24 26 123 8 10 12 14 16 18 20 22 24 26 170 6 8 10 12 14 16 18 20 22 24 171 6 8 10 12 14 16 18 20 22 24 172 8 10 12 14 16 18 20 22 24 26 173 8 10 12 14 16 18 20 22 24 26 901 6 8 10 12 14 16 18 20 22 2
Appendix - Varying Number of Drive Parameters
3AFE68573360 REV C EN EFFECTIVE: 09.10.2007 ABB Oy AC Drives P.O. Box 184 FI-00381 HELSINKI FINLAND Telephone +358 10 22 11 Fax +358 10 22 22681 Internet http://www.abb.com ABB Inc.
