- DL manuals
- ABB
- Control Unit
- FDNA-01
- User Manual
ABB FDNA-01 User Manual
Summary of FDNA-01
Page 1
Options for abb drives, converters and inverters user’s manual fdna-01 devicenet adapter module.
Page 2
List of related manuals see section related manuals on page 16 ..
Page 3: User’S Manual
6. Start-up user’s manual fdna-01 devicenet adapter module 3afe68573360 rev e en effective: 2012-04-04 © 2012 abb oy all rights reserved. 1. Safety table of contents 4. Mechanical installation 5. Electrical installation.
Page 5: Table of Contents
Table of contents 5 table of contents 1. Safety what this chapter contains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 use of warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 safety in installation . . . . . . . . . . . . . . . . . . . . . . . . ...
Page 6: 6. Start-Up
6 table of contents general cabling instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 connecting the module to the devicenet network . . . . . . . . . . . 30 terminal block description . . . . . . . . . . . . . . . . . . . . . . . . . . 30 connection examples . . . . . . . . . ...
Page 7: 8. Communication Protocol
Table of contents 7 communication profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 odva ac/dc drive profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 odva output attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 run forward & run revers...
Page 8
8 table of contents assembly objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 basic speed control assembly . . . . . . . . . . . . . . . . . . . . . . . 98 basic speed control plus drive parameters assembly . . . . . 99 extended speed control assembly . . . . . . . ...
Page 9: 9. Diagnostics
Table of contents 9 instance attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139 acknowledge handler object, class 2bh . . . . . . . . . . . . . . 141 class attributes (instance #0) . . . . . . . . . . . . . . . . . . . 141 instance attributes (instance #1) . . . . . . . . . . . ....
Page 10: Further Information
10 table of contents further information product and service inquiries . . . . . . . . . . . . . . . . . . . . . . . . . . 167 product training . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167 providing feedback on abb drives manuals . . . . . . . . . . . . . . 167 documen...
Page 11: Safety
Safety 11 1 safety what this chapter contains the chapter presents the warning symbols used in this manual and the safety instructions which you must follow when installing an optional module into a drive, converter or inverter. If ignored, physical injury or death may follow, or damage may occur to...
Page 12: Use Of Warnings
12 safety use of warnings warnings caution you about conditions which can result in serious injury or death and/or damage to the equipment and advise on how to avoid the danger. The following warning symbols are used in this manual: electricity warning warns of hazards from electricity which can cau...
Page 13: Safety In Installation
Safety 13 safety in installation these warnings are intended for all who install an optional module into a drive, converter or inverter. Warning! Ignoring the following instructions can cause physical injury or death, or damage to the equipment. • only qualified electricians are allowed to install a...
Page 14
14 safety.
Page 15: About The Manual
About the manual 15 2 about the manual what this chapter contains this chapter introduces this manual. Applicability this manual applies to the fdna-01 devicenet adapter module (+k451), sw version 0.223 or later. Compatibility the fdna-01 devicenet adapter module is compatible with the following dri...
Page 16: Target Audience
16 about the manual target audience the reader is expected to have a basic knowledge of fieldbus interface, electrical fundamentals, electrical wiring practices and how to operate the drive. Purpose of the manual the manual provides information on installing, commissioning and using an fdna-01 devic...
Page 17: Before You Start
About the manual 17 you can find manuals and other product documents in pdf format on the internet. See section document library on the internet on the inside of the back cover. For manuals not available in the document library, contact your local abb representative. Before you start it is assumed t...
Page 18: Contents
18 about the manual contents the manual consists of the following chapters: • safety presents the safety instructions which you must follow when installing a fieldbus adapter module. • about the manual introduces this manual. • overview of the devicenet network and the fdna-01 module contains a shor...
Page 19
About the manual 19 terms and abbreviations used in this manual general terms and abbreviations term explanation command word see control word. Communication module communication module is a name for a device (eg, a fieldbus adapter) through which the drive is connected to an external communication ...
Page 20
20 about the manual devicenet terms and abbreviations status word 16-bit or 32-bit word from slave to master with bit-coded status messages term explanation change of state/cyclic message change of state/cyclic message is transmitted by either the master or the slave. A change of state/cyclic messag...
Page 21
About the manual 21 odva™ odva stands for open devicenet vendor association. Odva is an independent organization that promotes interoperativity between different manufacturers’ devicenet products. Abb is an associate member at odva. Output in the odva devicenet specification the word ‘output’ is use...
Page 22
22 about the manual.
Page 23: Overview of The Devicenet
Overview of the devicenet network and the fdna-01 module 23 3 overview of the devicenet network and the fdna-01 module what this chapter contains this chapter contains a short description of the devicenet network and the fdna-01 devicenet adapter module. Devicenet network the devicenet network has a...
Page 24
24 overview of the devicenet network and the fdna-01 module example topology of the devicenet link an example of an allowable topology is shown below. Node node node node node tap tap tap tap node node node node node node trunk line terminating resistor drop line.
Page 25
Overview of the devicenet network and the fdna-01 module 25 fdna-01 devicenet adapter module the fdna-01 devicenet adapter module is an optional device for abb drives. It enables the connection of the drive to a devicenet network. The drive is considered a slave in the devicenet network. Through the...
Page 26
26 overview of the devicenet network and the fdna-01 module layout of the adapter module diagnostic leds (see chapter diagnostics ) bus connector x1 (see chapter electrical installation ) mounting screw.
Page 27: Mechanical Installation
Mechanical installation 27 4 mechanical installation what this chapter contains this chapter contains a delivery checklist and instructions on mounting the adapter module. Warning! Follow the safety instructions given in this manual and the drive documentation. Delivery check the option package for ...
Page 28: Mounting The Adapter Module
28 mechanical installation mounting the adapter module the adapter module 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 electrical connection between the module and drive frame for cable shield term...
Page 29: Electrical Installation
Electrical installation 29 5 electrical installation what this chapter contains this chapter contains: • general cabling instructions • instructions on connecting the module to the devicenet network • instructions on switching on the bus termination. Warning! Before installation, switch off the driv...
Page 30: Terminal Block Description
30 electrical installation connecting the module to the devicenet network connect the bus cable to terminal block x1 on the adapter module. Terminal block description connection examples 5-pin micro-style connector: 5-pin mini-style connector: x1 description 1 v- network power supply ground (0v dc) ...
Page 31
Electrical installation 31 standard open-style screw connector: switching on the bus termination the adapter module does not provide bus termination. The devicenet network should be terminated at both ends of the trunk cable with a 121 ohm, ¼ w, 1% metal film resistor. Connect the resistor between t...
Page 32
32 electrical installation.
Page 33: Start-Up
Start-up 33 6 start-up what this chapter contains this chapter contains: • information on configuring the drive for operation with the adapter module • drive-specific instructions on starting up the drive with the adapter module • examples of configuring the master station for communication with the...
Page 34: Drive Configuration
34 start-up drive configuration the following information applies to all drive types compatible with the adapter module, unless otherwise stated. Devicenet connection configuration after the adapter module has been mechanically and electrically installed according to the instructions in chapters mec...
Page 35
Start-up 35 fdna-01 configuration parameters – group a (group 1) note: the actual parameter group number depends on the drive type. Group a (group 1) corresponds to: • parameter group 51 in acs355, acsm1, acs850 and acq810 • parameter group 51 in acs880 if the adapter is installed as fieldbus adapte...
Page 36
36 start-up 04 drive profile defines the communication used between the module and the drive (not fieldbus and module). If a drive supports more than one drive profile, this parameter is used to select the preferred profile. Presently, to use the odva and abb drives profiles, the drive must support ...
Page 37
Start-up 37 06 output instance configures the output assembly instances used by the adapter module. Tables below list the supported assemblies and allowed combinations. For the descriptions of the assembly instances, see section assembly objects on page 98 . 20 acs355: fb par 6 acsm1: fba par6 acs85...
Page 38
38 start-up no. Name/value description default name output instance input instance default input size (bytes) profile (continued) abb drives profile with set speed plus drive parameters 901 951 24 abb drives abb drives profile with set speed and set torque plus drive parameters 902 952 26 abb drives...
Page 39
Start-up 39 note: with acsm1, acq810, acs850 and acs880, when using the odva ac/dc drive or abb drives profile, make sure that drive parameter 50.04 fba ref modesel is set to speed. With acsm1, acs850 and acs880, make sure that 50.05 fba ref2 modesel is set to torque. For alternative values, see col...
Page 40
40 start-up 08 input instance configures the input assembly instances used by the adapter module. See parameter 06 output instance . 70 acs355: fb par 9 acsm1: fba par9 acs850/acq810: fba par9 acs880: input instance for alternative values, see parameter 06 output instance . 09 input num pars see par...
Page 41
Start-up 41 10 odva speed scale defines the speed scale in the odva ac/dc drive profile. Units of reference and actual speeds for the odva ac/dc drive profile are given by the formula below. No effect on the abb drives profiles. Note: while a wide range of resolutions may be configured, the actual p...
Page 42
42 start-up 11 odva torque scale defines the torque scale in the odva ac/dc drive profile. Units of reference and actual torques for the odva ac/dc drive profile are given by the formula below. No effect on the abb drives profiles. Note: while a wide range of resolutions may be configured, the actua...
Page 43
Start-up 43 26 unrecover- able error read-only. Shows information about the cause of an unrecoverable error in the adapter module. Bit field parameter, that is, several status bits can be set at a time. Value 0 indicates that there are no errors. 0 acs355: fb par 26 acsm1: fba par26 acs850/acq810: f...
Page 44
44 start-up 28 par table ver read-only. Displays the parameter table revision of the fieldbus adapter module mapping file stored in the memory of the drive. In format xyz, where x = major revision number y = minor revision number z = correction number or in format axyz, where a = major revision numb...
Page 45
Start-up 45 31 d2fba comm sta read-only. Displays the status of the fieldbus adapter module communication. Note: the value names may vary by drive. 0 = idle acs355: fba status acsm1: d2fba comm sta acs850/acq810/ acs880: d2fba comm sta 0 = idle adapter is not configured. 1 = exec.Init adapter is ini...
Page 46
46 start-up 33 fba appl sw ver read-only. Displays the application program revision of the adapter module in format axyz, where: a = major revision number xy = minor revision numbers z = correction number or letter. Example: 190a = revision 1.90a n/a acs355: fba cpi appl rev acsm1: fba comm appl ver...
Page 47
Start-up 47 fdna-01 configuration parameters – group b (group 2) note: the actual parameter group number depends on the drive type. Group b (group 2) corresponds to: • parameter group 55 in acs355 • parameter group 53 in acsm1, acs850 and acq810 • parameter group 53 in acs880 if the adapter is insta...
Page 48
48 start-up fdna-01 configuration parameters – group c (group 3) note: the actual parameter group number depends on the drive type. Group c (group 3) corresponds to: • parameter group 54 in acs355 • parameter group 52 in acsm1, acs850 and acq810 • parameter group 52 in acs880 if the adapter is insta...
Page 49: Control Locations
Start-up 49 control locations abb drives can receive control information from multiple sources including digital inputs, analog inputs, the drive control panel and a communication module (for example, the adapter module). Abb drives allow the user to separately determine the source for each type of ...
Page 50: Abb Drives Profile
50 start-up 6. Set the relevant drive control parameters to control the drive according to the application. Examples of appropriate values are shown in the tables below. Parameter setting examples – acs355 abb drives profile this example shows how to configure the acs355 drive to use the abb drives ...
Page 51
Start-up 51 5109 fb par 9 (input num pars) 10 must always be set to 10, except as provided in appendix a – varying the number of drive parameters . 5110 fb par 10 (odva speed scale) 128 sets the scaling as 1 rpm for the odva speed reference. 5111 fb par 11 (odva torque scale) 128 sets the scaling as...
Page 52: Odva Ac/dc Drive Profile
52 start-up the start sequence for the parameter example above is given below. Control word: • 47eh (1150 decimal) –> ready to switch on • 47fh (1151 decimal) –> operating (speed mode) or c7fh (3199 decimal) –> operating (torque mode). Odva ac/dc drive profile the following example shows how to conf...
Page 53
Start-up 53 5106 fb par 6 (output instance) 23 selects the odva extended speed and torque control output instance. 5108 fb par 8 (input instance) 73 selects the odva extended speed and torque control input instance. 5110 fb par 10 (odva speed scale) 128 sets the scaling as 1 rpm for the odva speed r...
Page 54: Starting Up Acsm1 Drives
54 start-up note: in this example, digital input di1 has been configured to control whether to use the speed or torque control mode. The start sequence for the parameter example above is given below. Control word: • 0h (0 decimal) –> ready • 1h (1 decimal) –> enabled (running forward) • 2h (2 decima...
Page 55: Abb Drives Profile
Start-up 55 parameter setting examples – acsm1 abb drives profile the following example shows how to configure the acsm1 drive to use the abb drives profile. The used i/o assembly instances are 902 and 952. The table below gives the recommended drive parameter settings. Drive parameter setting for a...
Page 56
56 start-up 52.05 fba data in5 0 dc voltage - lsw 52.06 fba data in6 108 encoder 1 speed - msw 52.07 fba data in7 0 encoder 1 speed - lsw 52.08 fba data in8… 52.10 fba data in10 0 53.01 fba data out1 2503 acceleration time - msw 53.02 fba data out2 0 acceleration time - lsw 53.03 fba data out3 2504 ...
Page 57: Odva Ac/dc Drive Profile
Start-up 57 the start sequence for the parameter example above is given below. Control word: • 47eh (1150 decimal) –> ready to switch on • 47fh (1151 decimal) –> operating (speed mode) or c7fh (3199 decimal) –> operating (torque mode). Odva ac/dc drive profile the following example shows how to conf...
Page 58
58 start-up note: in this example, digital input di1 has been configured to control whether to use the speed or torque control mode. The start sequence for the parameter example above is given below. Control word: • 0h (0 decimal) –> ready • 1h (1 decimal) –> enabled (running forward) • 2h (2 decima...
Page 59
Start-up 59 starting up acs850 and acq810 drives 1. Power up the drive. 2. Enable the communication between the adapter module and the drive by setting parameter 50.01 fba enable to enable. 3. Ensure that 50.04 fb ref1 modesel is set to speed (both acs850 and acq810) and 50.05 fb ref2 modesel is set...
Page 60: Abb Drives Profile
60 start-up parameter setting examples – acs850 and acq810 abb drives profile the following example shows how to configure the acs850 or acq810 drive to use the abb drives profile. The used i/o assembly instances are 902 and 952. The table below gives the recommended drive parameter settings. Drive ...
Page 61
Start-up 61 52.03 fba data in3 105 motor current percent 52.04 fba data in4 107 dc voltage 52.05 fba data in5 0 dc voltage - lsw 52.06 fba data in6 108 encoder1 speed 52.07 fba data in7 0 encoder 1 speed - lsw 52.08 fba data in8… 52.10 fba data in10 0 53.01 fba data out1 2204 acc time 2 53.02 fba da...
Page 62
62 start-up the start sequence for the parameter example above is given below. Control word: • 47eh (1150 decimal) –> ready to switch on • 47fh (1151 decimal) –> operating (speed mode) or c7fh (3199 decimal) –> operating (torque mode in acs850). 12.05 ext2 ctrl mode 2 = torque selects torque as the ...
Page 63: Odva Ac/dc Drive Profile
Start-up 63 odva ac/dc drive profile the following example shows how to configure the acs850 or acq810 drive to use the odva ac/dc drive profile. The used i/o assembly instances are 23 and 73. The table below gives the recommended drive parameter settings. Drive parameter setting for acs850/acq810 d...
Page 64
64 start-up note: for acs850 in this example, digital input di1 has been configured to control whether to use the speed or torque control mode. The start sequence for the parameter example above is given below. Control word: 0h (0 decimal) –> ready 1h (1 decimal) –> enabled (running forward) 2h (2 d...
Page 65: Starting Up Acs880 Drives
Start-up 65 starting up acs880 drives this example sets up the fieldbus adapter installed as fieldbus adapter a. To set up the fieldbus adapter b, perform the same tasks with the corresponding parameters in parameter groups 50, 54, 55, and 56. 1. Power up the drive. 2. Enable the communication betwe...
Page 66
66 start-up the table below gives the recommended drive parameter settings. Drive parameter setting for acs880 drives description 50.01 fba a enable 1 = enable enables communication between drive and adapter module. 50.04 fba a ref1 type 4 = speed selects speed as the fieldbus a reference 1 type. 50...
Page 67: Odva Ac/dc Drive Profile
Start-up 67 the start sequence for the parameter example above is given below. Control word: • 47eh (1150 decimal) –> ready to switch on • 47fh (1151 decimal) –> operating (speed mode) or c7fh (3199 decimal) –> operating (torque mode) odva ac/dc drive profile the following example shows how to confi...
Page 68
68 start-up the table below gives the recommended drive parameter settings. Drive parameter setting for acs880 drives description 50.01 fba a enable 1 = enable enables communication between drive and adapter module. 50.04 fba a ref1 type 4 = speed selects speed as the fieldbus a reference 1 type. 50...
Page 69
Start-up 69 note: in this example, digital input di1 has been configured to control whether to use the speed or torque control mode. The start sequence for the parameter example above is given below. Control word: • 0h (0 decimal) –> ready • 1h (1 decimal) –> enabled (running forward) • 2h (2 decima...
Page 70: Eds Files
70 start-up configuring the master station after the adapter module has been initialized by the drive, the master station must be prepared for communication with the module. An example of an allen-bradley® plc is given below. If you are using another master system, refer to its documentation for mor...
Page 71: Plc
Start-up 71 configuring an allen-bradley ® plc this example shows how to set up an allen-bradley compactlogix plc with a 1769-sdn devicenet scanner to use a drive equipped with a fdna-01 fieldbus adapter, using rsnetworx and rslogix 5000 to configure and control the network. Slight vendor-specific d...
Page 72
72 start-up 3. Configure the device mac address..
Page 73
Start-up 73 4. 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 are used (for example, for basic speed control assemblies 20 and 70, each size is set to 4 byte...
Page 74
74 start-up 5. 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. It is more convenient to map them into separate double words. Output words can be mapped similarly. 6. Download the scanner sett...
Page 75
Start-up 75 7. 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 • loca...
Page 76
76 start-up.
Page 77: Communication Profiles
Communication profiles 77 7 communication profiles what this chapter contains this chapter describes the communication profiles used in the communication between the devicenet network, the adapter module and the drive. Communication profiles communication profiles are ways of conveying control comma...
Page 78
78 communication profiles the figure below illustrates the operation of the profiles: the following sections describe the control word, the status word, references and actual values for the odva ac/dc drive and abb drives communication profiles. Refer to the drive manuals for details on the native p...
Page 79: Odva Ac/dc Drive Profile
Communication profiles 79 odva ac/dc drive profile this section briefly describes the odva ac/dc drive profile. Additional information can be obtained at www.Odva.Org . A devicenet node is modelled as a collection of abstract objects. Each object represents the interface to and behavior of a compone...
Page 80: Run Forward & Run Reverse
80 communication profiles run forward & run reverse (control supervisor object) these attributes are used to assert run and stop commands to the control supervisor object state machine according to the following run/stop event matrix. See state (control supervisor object) on page 60. Fault reset (co...
Page 81
Communication profiles 81 scalar mode when the drive is operating in the scalar mode, the adapter module provides the drive with a frequency reference. The odva ac/dc drive profile uses rpm units for the speed reference. The drive frequency reference is calculated as follows: where for example, for ...
Page 82
82 communication profiles for example, for an odva speed reference of 900 rpm with a unit of 0.5 rpm, the drive speed reference is: 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...
Page 83: Odva Input Attributes
Communication profiles 83 odva input attributes this section briefly describes the instances found in the input assemblies of the odva ac/dc drive profile. Note that all input assembly instances do not support all attributes listed here. Faulted (control supervisor object) this attribute indicates t...
Page 84
84 communication profiles at reference (ac/dc drive object) this attribute indicates that 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. State description state descript...
Page 85
Communication profiles 85 the odva state transition diagram is shown below: non existent startup not ready ready enabled faulted fault stop stopping power off alm=1 alm=1 dec=1 dec=0 power-on and not rdy alm=1 faultrst fwd or rev alm=1 dec=0 power on power on power-on and rdy fwd or rev alm = alarm ...
Page 86
86 communication profiles speed actual (ac/dc drive object) this attribute indicates the actual speed at which the drive is operating. The units are scaled by the speedscale attribute of the ac/dc drive object. See table 4. For details. Scalar mode when the drive is operating in the scalar mode, the...
Page 87
Communication profiles 87 vector mode when the drive is operating in the vector mode, the drive provides the adapter module with a speed actual. The odva ac/dc drive profile uses rpm units for the speed actual. The odva speed actual is calculated as follows: where for example, for a drive speed actu...
Page 88: Control Word Contents
88 communication profiles for example, for a 1000 nm motor nominal torque with a unit of 1 nm and a drive torque actual of 50%, the odva torque actual is: abb drives communication profile control word and status word the control word is the principal means for controlling the drive from a fieldbus s...
Page 89
Communication profiles 89 2 off3_ control 1 continue operation (off3 inactive). 0 emergency stop, stop within time defined with the drive parameter. Proceed to off3 active; proceed to switch-on inhibited. Warning: ensure motor and driven machine can be stopped using this stop mode. 3 inhibit_ operat...
Page 90
90 communication profiles 7 reset 0=>1 fault reset if an active fault exists. Proceed to switch-on inhibited. Note: this bit is effective only if the fieldbus interface is set as the source for this signal by drive parameters. 0 continue normal operation. 8…9 reserved. 10 remote_ cmd 1 fieldbus cont...
Page 91: Status Word Contents
Communication profiles 91 status word contents the table below shows the contents of the status word for the abb drives communication profile. The upper case boldface text refers to the states shown in the state machine on page 93 . Bit name value state/description 0 rdy_on 1 ready to switch on. 0 n...
Page 92
92 communication profiles 10 above_ limit 1 actual frequency or speed equals or exceeds the supervision limit (set by the drive parameter). Valid in both directions of rotation. 0 actual frequency or speed within supervision limit. 11 ext_ctrl_ loc 1 external control location ext2 selected. Note con...
Page 93: State Machine
Communication profiles 93 state machine the state machine for the abb drives communication profile is shown below. Mains off power on (cw bit0=0) (sw bit6=1) (sw bit0=0) from any state (cw=xxxx x 1xx xxxx x110) (sw bit1=1) n(f)=0 / i=0 (sw bit2=0) a b c d (cw bit3=0) operation inhibited off1 (cw bit...
Page 94: References
94 communication profiles references references are 16-bit signed two's complement integers. A negative reference indicates a reverse direction of rotation. Abb drives can receive control information from multiple sources including analogue and digital inputs, the drive control panel and a communica...
Page 95: Actual Values
Communication profiles 95 actual values actual values are 16-bit signed two's complement integers containing information on the operation of the drive. A negative reference indicates a reverse direction of rotation. The functions to be monitored are selected with a drive parameter. Scaling actual va...
Page 96
96 communication profiles.
Page 97: Communication Protocol
Communication protocol 97 8 communication protocol what this chapter contains this chapter describes the devicenet communication protocol for the adapter module and the configuration of the scanner. For detailed information on devicenet communication, refer to odva devicenet specifications release 2...
Page 98: Assembly Objects
98 communication protocol assembly objects i/o assembly instances may also be referred to as block transfer of data. Intelligent devices realizing a functional profile, such as fdna-01, have several objects. Since it is not possible to transmit more than one object data through a single connection, ...
Page 99: Assembly
Communication protocol 99 basic speed control plus drive parameters assembly the basic speed control plus drive parameters assembly, defined by abb, adds configurable drive parameters to the basic speed control assembly of the odva ac/dc drive profile. The format of the output assembly is: instance ...
Page 100
100 communication protocol the format of the input assembly is: 21 data out 9 value (high byte) 22 data out 10 value (low byte) 23 data out 10 value (high byte) instance 170 byte bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 0 running1 (fwd) faulted 1 2 speed actual (low byte) 3 speed actual (high...
Page 101
Communication protocol 101 extended speed control assembly the extended speed control assembly is defined by the odva ac/dc drive profile. The format of the output assembly is: the format of the input assembly is: 20 data in 9 value (low byte) 21 data in 9 value (high byte) 22 data in 10 value (low ...
Page 102: Assembly
102 communication protocol extended speed control plus drive parameters assembly the extended speed control plus drive parameters assembly, defined by abb, adds configurable drive parameters to the extended speed control assembly of the odva ac/dc drive profile. The format of the output assembly is:...
Page 103
Communication protocol 103 the format of the input assembly is: 21 data out 9 value (high byte) 22 data out 10 value (low byte) 23 data out 10 value (high byte) instance 171 byte bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 0 at refer- ence ref from net ctrl from net ready run- ning2 (rev) run- n...
Page 104
104 communication protocol 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: 19 data in 8 value (high byte) 20 data in 9 value (low byte) 21 data in 9 value (high byte) 22 data in 10 v...
Page 105
Communication protocol 105 the format of the input assembly is: basic speed and torque control plus drive parameters assembly the basic speed and torque control plus drive parameters assembly, defined by abb, adds configurable drive parameters to the basic speed and torque control assembly of the od...
Page 106
106 communication protocol the format of the input assembly is: 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 data out 5 value (low byte) 15 data out 5 value (high byte) 16 data out 6 value (low byte) 17 data out 6 va...
Page 107
Communication protocol 107 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 byte) 14 data in 5 value (low byte) 15 ...
Page 108
108 communication protocol 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: the format of the input assembly is: instance 23 byte bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0...
Page 109
Communication protocol 109 extended speed and torque control plus drive parameters assembly the extended speed and torque control plus drive parameters assembly, defined by abb, adds configurable drive parameters to the extended speed and torque control assembly of the odva ac/dc drive profile. The ...
Page 110
110 communication protocol the format of the input assembly is: 21 data out 8 value (high byte) 22 data out 9 value (low byte) 23 data out 9 value (high byte) 24 data out 10 value (low byte) 25 data out 10 value (high byte) instance 173 byte bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 0 at refer...
Page 111
Communication protocol 111 abb drives profile with set speed assembly the abb drives profile with set speed assembly is defined by abb. The format of the output assembly is: 17 data in 6 value (high byte) 18 data in 7 value (low byte) 19 data in 7 value (high byte) 20 data in 8 value (low byte) 21 d...
Page 112
112 communication protocol the format of the input assembly is: abb drives profile with set speed plus drive parameters assembly the abb drives profile with set speed plus drive parameters assembly, defined by abb, adds configurable drive parameters to the abb drives profile with set speed of the ab...
Page 113
Communication protocol 113 the format of the input assembly is: 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 (high byte) 14 data out 6 value (low byte) 15 data out 6 value (high byte) 16 data out 7 va...
Page 114
114 communication protocol 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) 14 data in 6 value (low byte) 15 ...
Page 115: Set Torque Assembly
Communication protocol 115 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. The format of the output assembly is: the format of the input assembly is: instance 802 byte bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1...
Page 116
116 communication protocol 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 o...
Page 117
Communication protocol 117 the format of the input assembly is: 19 data out 7 value (high byte) 20 data out 8 value (low byte) 21 data out 8 value (high byte) 22 data out 9 value (low byte) 23 data out 9 value (high byte) 24 data out 10 value (low byte) 25 data out 10 value (high byte) instance 952 ...
Page 118
118 communication protocol transparent 16 with one assembly the transparent 16 with one assembly, defined by abb, provides unaltered 16-bit access to the configured drive profile. The format of the output assembly is: 14 data in 5 value (low byte) 15 data in 5 value (high byte) 16 data in 6 value (l...
Page 119: Parameters
Communication protocol 119 the format of the input assembly is: transparent 16 with one assembly plus drive parameters the transparent 16 with one assembly plus drive parameters, defined by abb, adds configurable drive parameters to the transparent 16 with one assembly. The format of the output asse...
Page 120
120 communication protocol the format of the input assembly is: 14 data out 6 value (low byte) 15 data out 6 value (high byte) 16 data out 7 value (low byte) 17 data out 7 value (high byte) 18 data out 8 value (low byte) 19 data out 8 value (high byte) 20 data out 9 value (low byte) 21 data out 9 va...
Page 121
Communication protocol 121 transparent 16 with two assembly the transparent 16 with two assembly, defined by abb, provides unaltered 16-bit access to the configured drive profile. The format of the output assembly is: 14 data in 6 value (low byte) 15 data in 6 value (high byte) 16 data in 7 value (l...
Page 122: Parameters
122 communication protocol the format of the input assembly is: transparent 16 with two assembly plus drive parameters the transparent 16 with two assembly plus drive parameters, defined by abb, adds configurable drive parameters to the transparent 16 with two assembly. The format of the output asse...
Page 123
Communication protocol 123 the format of the input assembly is: 12 data out 4 value (low byte) 13 data out 4 value (high byte) 14 data out 5 value (low byte) 15 data out 5 value (high byte) 16 data out 6 value (low byte) 17 data out 6 value (high byte) 18 data out 7 value (low byte) 19 data out 7 va...
Page 124
124 communication protocol 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 byte) 14 data in 5 value (low byte) 15 data in 5 value (high byte) 16 data in 6 value (low byte) 17 data in 6 value (high byte) 18 data in 7 value (low byte)...
Page 125
Communication protocol 125 transparent 32 with one assembly the transparent 32 with one assembly, defined by abb, provides unaltered 32-bit access to the configured drive profile. The format of the output assembly is: the format of the input assembly is: instance 821 byte bit 7 bit 6 bit 5 bit 4 bit...
Page 126: Parameters
126 communication protocol transparent 32 with one assembly plus drive parameters the transparent 32 with one assembly plus drive parameters, defined by abb, adds configurable drive parameters to the transparent 32 with one assembly. The format of the output assembly is: instance 921 byte bit 7 bit ...
Page 127
Communication protocol 127 the format of the input assembly is: 22 data out 8 value (low byte) 23 data out 8 value (high byte) 24 data out 9 value (low byte) 25 data out 9 value (high byte) 26 data out 10 value (low byte) 27 data out 10 value (high byte) instance 971 byte bit 7 bit 6 bit 5 bit 4 bit...
Page 128
128 communication protocol transparent 32 with two assembly the transparent 32 with two assembly, defined by abb, provides unaltered 32-bit access to the configured drive profile. The format of the output assembly is: 18 data in 6 value (low byte) 19 data in 6 value (high byte) 20 data in 7 value (l...
Page 129
Communication protocol 129 the format of the input assembly is: 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) instance 872 byte bit 7 bit 6 bit 5 bit 4 bit 3 bit...
Page 130: Parameters
130 communication protocol transparent 32 with two assembly plus drive parameters the transparent 32 with two assembly plus drive parameters, defined by abb, adds configurable drive parameters to the transparent 32 with two assembly. The format of the output assembly is: instance 922 byte bit 7 bit ...
Page 131
Communication protocol 131 the format of the input assembly is: 22 data out 6 value (low byte) 23 data out 6 value (high byte) 24 data out 7 value (low byte) 25 data out 7 value (high byte) 26 data out 8 value (low byte) 27 data out 8 value (high byte) 28 data out 9 value (low byte) 29 data out 9 va...
Page 132
132 communication protocol 14 data in 2 value (low byte) 15 data in 2 value (high byte) 16 data in 3 value (low byte) 17 data in 3 value (high byte) 18 data in 4 value (low byte) 19 data in 4 value (high byte) 20 data in 5 value (low byte) 21 data in 5 value (high byte) 22 data in 6 value (low byte)...
Page 133: Class Objects
Communication protocol 133 class objects the following table lists the data types used in the class object descriptions of this manual. The table also includes the corresponding data type names of the common industrial protocol (cip) specification. Note: the adapter module is designed to provide dev...
Page 134: Identity Object, Class 01H
134 communication protocol the table below lists the service names of the objects: identity object, class 01h this object provides identification of and general information about the device. Class attributes (instance #0) service name get 0x0e get_attribute_single set 0x10 set_attribute_single set a...
Page 135: Attribute Explanations
Communication protocol 135 instance attributes (instance #1) attribute explanations vendor id vendor ids are managed by the open devicenet vendor association, inc. (odva). The abb vendor id is 46. Device type the list of device types is managed by odva. It is used to identify the device profile that...
Page 136
136 communication protocol 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 that the device (or an obje...
Page 137: Devicenet Object, Class 03H
Communication protocol 137 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 repres...
Page 138: Instance Attributes
138 communication protocol instance attributes the allocation information attribute consists of the following: • allocation choice byte (byte) the allocation choice byte indicates which of the predefined master/slave connections are active (in the configuring, or established state). The allocation c...
Page 139: Class Attributes
Communication protocol 139 the table below shows the connection object states: class attributes instance attributes state description state description 00 nonexistent 03 established 01 configuring 04 timed out 02 waiting for connection id 05 deferred delete # attribute name services description data...
Page 140
140 communication protocol 6 comm char- acteristics 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 maxi...
Page 141
Communication protocol 141 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 a...
Page 142
142 communication protocol 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. Class attributes (...
Page 143
Communication protocol 143 instance attributes (instance #1) control supervisor object, class 29h the object models all the management functions for devices within the ‘hierarchy of motor control devices’. The behavior of motor control devices is described by the ac/dc-drive object, class 2ah and th...
Page 144
144 communication protocol class attributes (instance #0) instance attributes (instance #1) # attribute name services description data type 1 revision get revision of the devicenet object class definition upon which the implementation is based uint8 # attribute name services description data type 3 ...
Page 145
Communication protocol 145 13 fault code get the fault that caused the last transition to the faulted state. Drivecomm codes are reported. See the drive manual for further information on the drivecomm codes. Uint16 14 warning code get code word indicating a warning. If multiple warnings are present,...
Page 146
146 communication protocol ac/dc-drive object, class 2ah this object models the functions specific to an ac or dc drive. Class attributes (instance #0) instance attributes (instance #1) # attribute name services description data type 1 revision get revision of the devicenet object class definition u...
Page 147
Communication protocol 147 drive parameter object, class 90h with 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 fieldbu...
Page 148: Class Attributes
148 communication protocol fieldbus configuration object 91h the fieldbus configuration object allows the user to configure the fieldbus configuration groups without needing to know the drive- specific groups associated with the configuration groups. Note: when using the fieldbus configuration objec...
Page 149
Communication protocol 149 4 configuration group a (group 1) – parameter 4 get, set see 04 drive profile . Uint16 5 configuration group a (group 1) – parameter 5 get, set see 05 odva stop func . Uint16 6 configuration group a (group 1) – parameter 6 get, set see 06 output instance . Uint16 7 configu...
Page 150
150 communication protocol 16 configuration group a (group 1) – parameter 16 get, set see 12 … 25 reserved . Uint16 17 configuration group a (group 1) – parameter 17 get, set see 12 … 25 reserved . Uint16 18 configuration group a (group 1) – parameter 18 get, set see 12 … 25 reserved . Uint16 19 con...
Page 151: Group B (Group 2)
Communication protocol 151 instance #2: fdna-01 configuration parameters group b (group 2) the actual parameter group number depends on the drive type. Group b (group 2) corresponds to • parameter group 55 in acs355 • parameter group 53 in acsm1, acs850 and acq810 • parameter group 53 in acs880 if t...
Page 152: Group C (Group 3)
152 communication protocol instance #3: fdna-01 configuration parameters group c (group 3) the actual parameter group number depends on the drive type. Group c (group 3) corresponds to: • parameter group 54 in acs355 • parameter group 52 in acsm1, acs850 and acq810 • parameter group 52 in acs880 if ...
Page 153
Communication protocol 153 3 configuration group c (group 3) - parameter 3 get, set see 01 data in 1 . Uint16 4 configuration group c (group 3) - parameter 4 get, set see 01 data in 1 . Uint16 5 configuration group c (group 3) - parameter 5 get, set see 01 data in 1 . Uint16 6 configuration group c ...
Page 154
154 communication protocol.
Page 155: Diagnostics
Diagnostics 155 9 diagnostics what this chapter contains this chapter explains how to trace faults with the status leds on the adapter module..
Page 156: Led Indications
156 diagnostics led indications the adapter module is equipped with three diagnostic leds. The leds are described below. Name color function host blinking green establishing communication to host green communication to host ok blinking red communication to host lost temporarily flashing orange, alte...
Page 157
Diagnostics 157 module off there is no power applied to the device. Green device is operating in a normal condition. Flashing green device needs commissioning due to configuration missing, incomplete or incorrect. The device may be in the standby state. Flashing red recoverable fault red device has ...
Page 158
158 diagnostics network off device is not on-line. • device has not completed the dup_mac_id test yet. • device may not be powered. Look at the module status led. Flashing green device is on-line but has no connections in the established state. • device has passed the dup_mac_id test, is on-line, bu...
Page 159: Technical Data
Technical data 159 10 technical data what this chapter contains this chapter contains the technical data of the adapter module and the devicenet link..
Page 160: Fdna-01
160 technical data fdna-01 the figure below shows the enclosure of the adapter module from the front and side. Mounting into the option slot of the drive degree of protection ip20 ambient conditions applicable ambient conditions specified for the drive in its manuals are in effect. Indicators three ...
Page 161: Devicenet Link
Technical data 161 devicenet link power supply input voltage: • from the drive: +3.3 v dc (+/- 5%) • from the network: +24 v dc nominal (+11 v to +30 v) input current: • from the drive: 180 ma typical, 300 ma maximum (+3.3 v) • from the network: 20 ma typical, 50 ma maximum (+24 v) general estimated...
Page 162
162 technical data.
Page 163: Appendix A – Varying The
Appendix a – varying the number of drive parameters 163 11 appendix a – varying the number of drive parameters what this chapter contains this chapter describes how to reduce the number of drive parameter members in fdna-01 assemblies by modifying the eds file. Modification of the eds file assembly ...
Page 164
164 appendix a – varying the number of drive parameters is provided below. For manual configuration, see the documentation for the devicenet master. Note: only one eds file with the same product id can be installed at a time. Changing the eds file changes it for all drives with that product id. In s...
Page 165
Appendix a – varying the number of drive parameters 165 assembly number of drive parameters 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...
Page 166
166 appendix a – varying the number of drive parameters.
Page 167
Further information product and service inquiries address any inquiries about the product to your local abb representative, quoting the type designation and serial number of the unit in question. A listing of abb sales, support and service contacts can be found by navigating to www.Abb.Com/drives an...
Page 168
3afe xx xxxx xx r ev x / e n e ffe ctiv e : x x.X x.Xx xx 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. Automation technologies drives & motors 16250 west glendale drive new berlin, wi 53151 usa telephone 262...