1. DL manuals
  2. ABB
  3. Control Unit
  4. FENA-01
  5. User Manual

ABB FENA-01 User Manual

Other manuals for FENA-01: Hardware Manual, Protocol Manual
Manual is about: Ethernet adapter module

Summary of FENA-01

  • Page 1

    Options for abb drives, converters and inverters user’s manual fena-01/-11/-21 ethernet adapter module.

  • Page 2

    List of related manuals 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. Drive manuals and guides cod...

  • Page 3: User’S Manual

    Modbus/tcp protocol user’s manual fena-01/-11/-21 ethernet adapter module 3aua0000093568 rev b en effective: 2014-01-29  2014 abb oy all rights reserved. 1. Safety instructions table of contents 4. Mechanical installation 5. Electrical installation ethernet/ip protocol profinet io protocol.

  • Page 5: Table Of Contents

    Table of contents 5 table of contents list of related manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Safety instructions contents of this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 use of warnings . . . . . . . . . . . . . . . . . . . . ....

  • Page 6: 4. Mechanical Installation

    6 table of contents 4. Mechanical installation contents of this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 necessary tools and instructions . . . . . . . . . . . . . . . . . . . . . . . . 39 unpacking and examining the delivery . . . . . . . . . . . . . . . . . . . . 39...

  • Page 7

    Table of contents 7 starting up fieldbus communication for acs850 and acq810 drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 parameter setting examples – acs850 and acq810 . . . . . 73 speed control using the abb drives – enhanced communication pro...

  • Page 8: Ethernet/ip Protocol

    8 table of contents communication profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 abb drives profile - classic . . . . . . . . . . . . . . . . . . . . . . . . . 99 abb drives profile - enhanced . . . . . . . . . . . . . . . . . . . . . 100 transparent 16-bit . . . . . . . ....

  • Page 9

    Table of contents 9 speed control using the odva ac/dc drive profile, extended speed control assembly . . . . . . . . . . . . . . . . 142 starting up fieldbus communication for acs880 and acs580 drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145 parame...

  • Page 10

    10 table of contents state (control supervisor object) . . . . . . . . . . . . . . . . . 167 speed actual (ac/dc drive object) . . . . . . . . . . . . . . . 169 torque actual (ac/dc drive object) . . . . . . . . . . . . . . . 171 abb drives communication profile . . . . . . . . . . . . . . . . . . ....

  • Page 11

    Table of contents 11 transparent 16 with one assembly plus drive parameters 204 transparent 16 with two assembly . . . . . . . . . . . . . . . . . . 206 transparent 16 with two assembly plus drive parameters 207 transparent 32 with one assembly . . . . . . . . . . . . . . . . . . 209 transparent 32 ...

  • Page 12: Profinet Io Protocol

    12 table of contents connection object, class 05h . . . . . . . . . . . . . . . . . . . . . . . 237 class attributes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238 instance attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238 acknowledge handler object, class 2bh ...

  • Page 13

    Table of contents 13 position control using the profidrive communication profile with ppo type 4 . . . . . . . . . . . . . . . . . . . . . . . . 272 speed and torque control using the abb drives communication profile with ppo type 4 . . . . . . . . . . . 276 starting up fieldbus communication for ac...

  • Page 14

    14 table of contents actual values in positioning mode (acsm1 only). . . . . 315 abb drives communication profile . . . . . . . . . . . . . . . . . . . . . . 316 control word and status word . . . . . . . . . . . . . . . . . . . . . . 316 control word contents. . . . . . . . . . . . . . . . . . . . ...

  • Page 15: 18. Technical Data

    Table of contents 15 example 3: reading a profidrive parameter. . . . . . . 347 example 4: configuring the process data written to the drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348 example 5: determining the source of the process data read from the drive . ....

  • Page 16: Further Information

    16 table of contents 20. Appendix b – abb ip configuration tool for fena contents of this chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375 installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375 finding adapter modules in the network . ...

  • Page 17: Safety Instructions

    Safety instructions 17 1 safety instructions contents of this chapter the chapter contains the warning symbols used in this manual and the safety instructions which you must obey when you install or connect an optional module to a drive, converter or inverter. If you ignore the safety instructions, ...

  • Page 18: Use Of Warnings

    18 safety instructions use of warnings warnings tell you about conditions which can cause injury or death, or damage to the equipment. They also tell you how to prevent the danger. The manual uses these warning symbols: electricity warning tells you about hazards from electricity which can cause inj...

  • Page 19: Safety In Installation

    Safety instructions 19 safety in installation these instructions are for all who install or connect an optional module to a drive, converter or inverter and need to open its front cover or door to do the work. Warning! Obey these instructions. If you ignore them, injury or death, or damage to the eq...

  • Page 20

    20 safety instructions.

  • Page 21: Introduction To The Manual

    Introduction to the manual 21 2 introduction to the manual contents of this chapter this chapter introduces this manual. Applicability this manual applies to the fena-01/-11/-21 ethernet adapter module, sw version 3.00 and later. Compatibility drives this table shows the compatibility of the fena ad...

  • Page 22: Protocols

    22 introduction to the manual protocols the fena adapter module is compatible with ethernet standards ieee 802.3 and ieee 802.3u. This table shows the protocols supported by the fena adapter module from sw version 0.290 onwards. This table specifies the clients/masters that are compatible with the s...

  • Page 23: Tools

    Introduction to the manual 23 tools the fena-11/-21 adapter module can be used in the ethernet tool network for acs880 and acs580 drives. The ethernet tool network enables commissioning and monitoring several single drives, or inverter and supply units of a multidrive from a single location by using...

  • Page 24: Contents

    24 introduction to the manual contents the manual consists of the following chapters: • safety instructions gives the safety instructions which you must obey when you install a fieldbus adapter module. • overview of the ethernet network and the fena-01/-11/-21 module contains a short description of ...

  • Page 25: Ethernet/ip Protocol

    Introduction to the manual 25 ethernet/ip protocol • ethernet/ip – start-up presents the steps to take during the start-up of the drive with the adapter module and gives examples of configuring the ethernet/ip client. • ethernet/ip – communication profiles describes the communication profiles used i...

  • Page 26: Terms And Abbreviations

    26 introduction to the manual terms and abbreviations later in this manual, term drive substitutes for string drive/converter/inverter. General terms and abbreviations term explanation command word see control word. Control word 16-bit or 32-bit word from master to slave with bit-coded control signa...

  • Page 27

    Introduction to the manual 27 modbus/tcp terms and abbreviations ethernet/ip terms and abbreviations abbreviation explanation dhcp dynamic host control protocol. A protocol for automating the configuration of ip devices. Dhcp can be used to automatically assign ip addresses and related network infor...

  • Page 28

    28 introduction to the manual profinet io terms and abbreviations i/o assembly selection smart networked devices (like fena) can produce and/or consume more than one i/o value. Typically, they will produce and/or consume one or more i/o value, as well as status and diagnostic information. Each piece...

  • Page 29

    Introduction to the manual 29 gsd file ascii-format device description file in a specified form. Each different slave type on the profinet io network needs to have its own gsd file. Gsd files in profinet io are written in gsdml. Index access reference for objects in profinet io i/o controller contro...

  • Page 30

    30 introduction to the manual the text in italics is the original german term. Abbreviation explanation act actual value istwert dap device access point dp decentralised periphery dezentrale peripherie dp-v0 profinet io extension to the en 50170 standard, providing the basic functionality of dp, inc...

  • Page 31

    Introduction to the manual 31 sow reference sollwert stw control word steuerwort zsw status word zustandswort abbreviation explanation.

  • Page 32

    32 introduction to the manual.

  • Page 33: Overview Of The Ethernet

    Overview of the ethernet network and the fena-01/-11/-21 module 33 3 overview of the ethernet network and the fena-01/-11/- 21 module contents of this chapter this chapter contains a short description of the ethernet network and the fena adapter module. Ethernet network ethernet standards support a ...

  • Page 34

    34 overview of the ethernet network and the fena-01/-11/-21 module example topology of the ethernet link this figure shows an example of an allowable topology for an ethernet network with fena-01/-11. This figure shows an example of an allowable topology for an ethernet network with fena-21. Switch ...

  • Page 35

    Overview of the ethernet network and the fena-01/-11/-21 module 35 fena-01/-11/-21 ethernet adapter module the fena-01/-11/-21 ethernet adapter module is an optional device for abb drives which enables the connection of the drive to an ethernet network. Through the adapter module you can: • give con...

  • Page 36

    36 overview of the ethernet network and the fena-01/-11/-21 module layout of the adapter module this figure shows the layout of fena-01/-11. 4 3 2 no. Description see chapter 1 lock mechanical installation 2 mounting screw mechanical installation 3 connector x1 to ethernet electrical installation 4 ...

  • Page 37

    Overview of the ethernet network and the fena-01/-11/-21 module 37 this figure shows the layout of fena-21. No. Description see chapter 1 lock mechanical installation 2 mounting screw mechanical installation 3 connector x1 to ethernet electrical installation 4 connector x2 for chaining another adapt...

  • Page 38

    38 overview of the ethernet network and the fena-01/-11/-21 module.

  • Page 39: Mechanical Installation

    Mechanical installation 39 4 mechanical installation contents of this chapter this chapter contains a delivery checklist and instructions to install the adapter module. Necessary tools and instructions see the applicable drive hardware manual. Unpacking and examining the delivery 1. Open the option ...

  • Page 40

    40 mechanical installation installing the adapter module warning! Obey the safety instructions. See chapter safety instructions on page 17 . If you ignore the safety instructions, injury or death can occur. The adapter module has a specific position in the drive. Plastic pins, a lock and one screw h...

  • Page 41

    Mechanical installation 41 2. Put the adapter module carefully into its position on the drive. 3. Push in the lock. 4. Tighten the screw. Note: it is necessary to tighten the screw properly to fulfill the emc requirements and to ensure the proper operation of the module. See the applicable drive man...

  • Page 42

    42 mechanical installation.

  • Page 43: Electrical Installation

    Electrical installation 43 5 electrical installation contents of this chapter this chapter contains: • general cabling instructions • instructions on connecting the adapter module to the ethernet network. Warnings warning! Obey the safety instructions. See chapter safety instructions on page 17 . If...

  • Page 44: Network

    44 electrical installation general cabling instructions • arrange the bus cables as far away from the motor cables as possible. • avoid parallel runs. • use bushings at cable entries. Connecting the adapter module to the ethernet network the network cable can be cat5 or higher, and type utp, ftp or ...

  • Page 45: Connection Procedure

    Electrical installation 45 connection procedure 1. Connect the network cable to the rj-45 connector (x1) on the adapter module. 2. If you want to create a daisy chain with fena-21 adapter modules, connect the x2 connector of the first adapter module to x1 on the next adapter module, and so on..

  • Page 46

    46 electrical installation.

  • Page 47: Modbus/tcp Protocol

    Modbus/tcp protocol modbus/tcp – start-up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 modbus/tcp – communication profiles . . . . . . . . . . . . . . . . . . . 85 modbus/tcp – communication protocol . . . . . . . . . . . . . . . . . . 95 modbus/tcp – diagnostics . . . . . . . . ...

  • Page 49: Modbus/tcp – Start-Up

    Modbus/tcp – start-up 49 6 modbus/tcp – start-up contents of this chapter 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 • information on configuring the client for com...

  • Page 50: Drive Configuration

    50 modbus/tcp – start-up drive configuration the information in this section applies to all drive types compatible with the adapter module, unless otherwise stated. Modbus/tcp connection configuration after the adapter module has been mechanically and electrically installed according to the instruct...

  • Page 51

    Modbus/tcp – start-up 51 fena-01/-11-/21 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 and acs580 if the adapter...

  • Page 52

    52 modbus/tcp – start-up 03 comm rate sets the bit rate for the ethernet interface. 0 = auto acs355: fb par 3 acsm1: fba par3 acs850/acq810: fba par3 acs880/acs580: commrate 0 = auto autonegotiate 1 = 100 mbps fd 100 mbps, full duplex 2 = 100 mbps hd 100 mbps, half duplex 3 = 10 mbps fd 10 mbps, ful...

  • Page 53

    Modbus/tcp – start-up 53 08 ip address 4 see parameter 05 ip address 1 . 0 acs355: fb par 8 acsm1: fba par8 acs850/acq810: fba par8 acs880/acs580: ip address 4 0…255 ip address 09 subnet cidr subnet masks are used for splitting networks into smaller networks called subnets. A subnet mask is a 32-bit...

  • Page 54

    54 modbus/tcp – start-up 10 gw address 1 ip gateways connect individual physical ip subnets into a unified ip network. When an ip node needs to communicate with an ip node on another subnet, the ip node sends the data to the ip gateway for forwarding. Parameters 10 … 13 define the four octets of the...

  • Page 55

    Modbus/tcp – start-up 55 19 t16 scale defines the reference multiplier/actual value divisor for the adapter module. The parameter is effective only when the transparent 16 profile is selected and the drive is using the native communication profile (eg, dcu or fba) and a 16-bit transparent reference ...

  • Page 56

    56 modbus/tcp – start-up 21 timeout mode selects which modbus/tcp register accesses reset the timeout counter. 2 = control rw acs355: fb par 21 acsm1: fba par21 acs850/acq810: fba par21 acs880/acs580: timeout mode 0 = none the modbus/tcp timeout feature is disabled. 1 = any message the timeout count...

  • Page 57

    Modbus/tcp – start-up 57 27 fba par refresh validates any changed adapter module configuration parameter settings. After refreshing, the value reverts automatically to 0 = done. Note: this parameter cannot be changed while the drive is running. 0 = done acs355/acsm1: fba par refresh acs850/acq810: f...

  • Page 58

    58 modbus/tcp – start-up 30 mapping file ver read-only. Displays the fieldbus adapter module mapping file revision stored in the memory of the drive in decimal format. N/a acs355: file config rev acsm1: mapping file ver acs850/acq810: mapping file ver acs880/acs580: fba a/b mapping file ver mapping ...

  • Page 59

    Modbus/tcp – start-up 59 32 fba comm sw ver read-only. Displays the common program revision of the adapter module in format axyz, where: a = major revision number xy = minor revision numbers z = correction number or letter. N/a acs355: fba cpi fw rev acsm1: fba comm sw ver acs850/acq810: fba comm sw...

  • Page 60

    60 modbus/tcp – start-up fena-01/-11/-21 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 an...

  • Page 61

    Modbus/tcp – start-up 61 fena-01/-11/-21 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 an...

  • Page 62: Control Locations

    62 modbus/tcp – start-up control locations abb drives can receive control information from multiple sources including digital inputs, analog inputs, the drive control panel and a fieldbus adapter module. Abb drives allow the user to separately determine the source for each type of control informatio...

  • Page 63: Drives

    Modbus/tcp – start-up 63 starting up fieldbus communication for acs355 drives 1. Power up the drive. 2. Enable the communication between the adapter module and the drive with parameter 9802 comm prot sel. 3. Set the module configuration parameters in group 51. • select the communication protocol and...

  • Page 64

    64 modbus/tcp – start-up parameter setting examples – acs355 speed and torque control using the abb drives – enhanced communication profile this example shows how to configure a speed and torque control application that uses the abb drives - enhanced profile. In addition, some application-specific d...

  • Page 65

    Modbus/tcp – start-up 65 5102 fb par 2 (protocol/profile) 1 (= mb/tcp abb e) selects the modbus/tcp protocol and the abb drives - enhanced profile. 5103 fb par 3 (commrate) 0 (= auto) 2) ethernet communication rate is negotiated automatically by the device. 5104 fb par 4 (ip configuration) 0 (= stat...

  • Page 66

    66 modbus/tcp – start-up the start sequence for the parameter example above is given below. Control word: • reset the fieldbus communication fault (if active). • enter 47eh (1150 decimal) –> ready to switch on. • enter 47fh (1151 decimal) –> operating (speed mode) or c7fh (3199 decimal) –> operating...

  • Page 67: Drives

    Modbus/tcp – start-up 67 starting up fieldbus communication for acsm1 drives 1. Power up the drive. 2. Enable the communication between the adapter module and the drive with parameter 50.01 fba enable. 3. With parameter 50.02 comm loss func, select how the drive reacts to a fieldbus communication br...

  • Page 68

    68 modbus/tcp – start-up 7. Define the process data transferred to and from the drive in parameter groups 52 and 53. Note: the adapter module assigns the control word, status word, references 1…2 and actual values 1…2 automatically to modbus registers. Process data groups are not available in the ab...

  • Page 69

    Modbus/tcp – start-up 69 the minimum and maximum 16-bit integer values that can be given through the fieldbus are -32768 and 32767 respectively. The table below gives the recommended drive parameter settings. Output data modbus register input data modbus register control word (4)00001 status word (4...

  • Page 70

    70 modbus/tcp – start-up 51.05 fba par5 (ip address 1) 192 2) first part of the ip address 51.06 fba par6 (ip address 2) 168 2) second part of the ip address 51.07 fba par7 (ip address 3) 0 2) third part of the ip address 51.08 fba par8 (ip address 4) 16 2) last part of the ip address 51.09 fba par9...

  • Page 71

    Modbus/tcp – start-up 71 the start sequence for the parameter example above is given below. Control word: • reset the fieldbus communication fault (if active). • enter 47eh (1150 decimal) –> ready to switch on. • enter 47fh (1151 decimal) –> operating (speed mode) or c7fh (3199 decimal) –> operating...

  • Page 72: And Acq810 Drives

    72 modbus/tcp – start-up starting up fieldbus communication for acs850 and acq810 drives 1. Power up the drive. 2. Enable the communication between the adapter module and the drive with parameter 50.01 fba enable. 3. With parameter 50.02 comm loss func, select how the drive reacts to a fieldbus comm...

  • Page 73: Communication Profile

    Modbus/tcp – start-up 73 7. Define the process data transferred to and from the drive in parameter groups 52 and 53. Note: the adapter module assigns the control word, status word, references 1…2 and actual values 1…2 automatically to modbus registers. Process data groups are not available in the ab...

  • Page 74

    74 modbus/tcp – start-up the minimum and maximum 16-bit integer values that can be given through the fieldbus are -32768 and 32767 respectively. The table below gives the recommended drive parameter settings. Output data modbus register input data modbus register control word (4)00001 status word (4...

  • Page 75

    Modbus/tcp – start-up 75 51.05 fba par5 (ip address 1) 192 2) first part of the ip address 51.06 fba par6 (ip address 2) 168 2) second part of the ip address 51.07 fba par7 (ip address 3) 0 2) third part of the ip address 51.08 fba par8 (ip address 4) 16 2) last part of the ip address 51.09 fba par9...

  • Page 76: And Acs580 Drives

    76 modbus/tcp – start-up the start sequence for the parameter example above is given below. Control word: • reset the fieldbus communication fault (if active). • enter 47eh (1150 decimal) –> ready to switch on. • enter 47fh (1151 decimal) –> operating (speed mode). Starting up fieldbus communication...

  • Page 77

    Modbus/tcp – start-up 77 5. Select application-specific values for the rest of the parameters in group 50, starting from 50.04. Examples of appropriate values are shown in the tables below. 6. Set the module configuration parameters in group 51. • select the communication protocol and profile with p...

  • Page 78: Communication Profile

    78 modbus/tcp – start-up parameter setting examples – acs880 speed control using the abb drives – enhanced communication profile this example shows how to configure a speed control application that uses the abb drives - enhanced profile. In addition, some application-specific data is added to the co...

  • Page 79

    Modbus/tcp – start-up 79 50.03 fba a comm loss t out 3.0 s 2) defines the fieldbus a communication break supervision time. 50.04 fba a ref1 type 4 = speed selects the fieldbus a reference 1 type and scaling. 51.01 fba a type 128 = ethernet 1) displays the type of the fieldbus adapter module. 51.02 p...

  • Page 80

    80 modbus/tcp – start-up the start sequence for the parameter example above is given below. Control word: • reset the fieldbus communication fault (if active). • enter 47eh (1150 decimal) –> ready to switch on. • enter 47fh (1151 decimal) –> operating (speed mode). 20.01 ext1 commands 12 = fieldbus ...

  • Page 81: Communication Profile

    Modbus/tcp – start-up 81 parameter setting examples – acs580 frequency control using the abb drives – enhanced communication profile this example shows how to configure a frequency control application that uses the abb drives - enhanced profile. In addition, some application-specific data is added t...

  • Page 82

    82 modbus/tcp – start-up 50.03 fba a comm loss t out 3.0 s 2) defines the fieldbus a communication break supervision time. 50.04 fba a ref1 type 0 = speed or frequency selects the fieldbus a reference 1 type and scaling. 51.01 fba a type 128 = ethernet 1) displays the type of the fieldbus adapter mo...

  • Page 83

    Modbus/tcp – start-up 83 the start sequence for the parameter example above is given below. Control word: • reset the fieldbus communication fault (if active). • enter 47eh (1150 decimal) –> ready to switch on. • enter 47fh (1151 decimal) –> operating (scalar motor control mode). 20.01 ext1 commands...

  • Page 84: Client Configuration

    84 modbus/tcp – start-up client configuration after the adapter module has been initialized by the drive, you must prepare the client for communication with the module. Due to the large number of different modbus clients, specific instructions cannot be provided here. Refer to the documentation of y...

  • Page 85: Modbus/tcp –

    Modbus/tcp – communication profiles 85 6 modbus/tcp – communication profiles contents of this chapter this chapter describes the communication profiles used in the communication between the modbus/tcp client, the adapter module and the drive. Communication profiles communication profiles are ways of...

  • Page 86

    86 modbus/tcp – communication profiles the figure below illustrates the profile selection: the following sections describe the control word, the status word, references and actual values for the abb drives communication profile. Refer to the drive manuals for details on the native profiles. Fena dri...

  • Page 87: Control Word Contents

    Modbus/tcp – communication profiles 87 abb drives communication profile control word and status word the control word is the principal means for controlling the drive from a fieldbus system. It is sent by the fieldbus client station to the drive through the adapter module. The drive switches between...

  • Page 88

    88 modbus/tcp – communication profiles 3 inhibit_ operation 1 proceed to operation enabled. Note: run enable signal must be active; see drive documentation. If the drive is set to receive the run enable signal from the fieldbus, this bit activates the signal. 0 inhibit operation. Proceed to operatio...

  • Page 89: Status Word Contents

    Modbus/tcp – communication profiles 89 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 91 . 10 remote_ cmd 1 fieldbus control enabled. 0 control w...

  • Page 90

    90 modbus/tcp – communication profiles 7 alarm 1 warning/alarm 0 no warning/alarm 8 at_ setpoint 1 operation. Actual value equals reference (= is within tolerance limits, ie, in speed control, speed error is 10% max. Of nominal motor speed). 0 actual value differs from reference (= is outside tolera...

  • Page 91: State Machine

    Modbus/tcp – communication profiles 91 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...

  • Page 92: References

    92 modbus/tcp – communication profiles 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. Abb drives can receive c...

  • Page 93: Actual Values

    Modbus/tcp – communication profiles 93 actual values actual values are 16-bit words containing information on the operation of the drive. The functions to be monitored are selected with a drive parameter. Scaling actual values are scaled as shown below. Note: the values of ref1 max and ref2 max are ...

  • Page 94

    94 modbus/tcp – communication profiles.

  • Page 95: Modbus/tcp –

    Modbus/tcp – communication protocol 95 6 modbus/tcp – communication protocol contents of this chapter this chapter describes the modbus/tcp communication protocol for the adapter module. Modbus/tcp modbus/tcp is a variant of the modbus family of simple, vendor neutral communication protocols intende...

  • Page 96: Register Addressing

    96 modbus/tcp – communication protocol register addressing the address field of modbus requests for accessing holding registers is 16 bits. This allows the modbus protocol to support addressing of 65536 holding registers. Historically, modbus client devices used 5-digit decimal addresses from 40001 ...

  • Page 97: Identification

    Modbus/tcp – communication protocol 97 encapsulated interface transport / read device identification the adapter module supports the modbus eit/rdi objects shown below. 2bh/0eh encapsulated interface transport / read device identification allows reading identification and other information of the se...

  • Page 98: Exception Codes

    98 modbus/tcp – communication protocol exception codes the adapter module supports the modbus exception codes shown below. Communication profiles modbus is an application layer messaging protocol. It describes how data is transferred between the client and a server, but not the meaning of that data....

  • Page 99

    Modbus/tcp – communication protocol 99 abb drives profile - classic the abb drives profile - classic communication profile provides register mapped access to the control, status, reference and actual values of the abb drives profile in the classic format for backward compatibility. Register address ...

  • Page 100

    100 modbus/tcp – communication protocol abb drives profile - enhanced the abb drives profile - enhanced communication profile provides register mapped access to the control, status, reference and actual values of the abb drives profile. The mapping of the registers has been enhanced to allow writing...

  • Page 101

    Modbus/tcp – communication protocol 101 (4)00060 data in 7 (4)00061 data in 8 (4)00062 data in 9 (4)00063 data in 10 (4)00064 data in 11 (4)00065 data in 12 (4)00101…(4)09999 drive parameter access (16-bit) register address = (4)00000 + 100 × group + index example for drive parameter 3.18: (4)00000 ...

  • Page 102: Transparent 16-Bit

    102 modbus/tcp – communication protocol transparent 16-bit the transparent 16-bit communication profile provides unaltered 16-bit access to the configured drive profile. Register address 1), 2) register data (16-bit) (4)00001 native drive profile control (4)00002 native drive profile reference 1 (4)...

  • Page 103: Transparent 32-Bit

    Modbus/tcp – communication protocol 103 transparent 32-bit the transparent 32-bit communication profile provides unaltered 32-bit access to the configured drive profile. (4)00062 data in 9 (4)00063 data in 10 (4)00064 data in 11 (4)00065 data in 12 (4)00101…(4)09999 drive parameter access (16-bit) r...

  • Page 104

    104 modbus/tcp – communication protocol (4)00004 native drive profile reference 1 - most significant 16-bits (4)00005 native drive profile reference 2 - least significant 16-bits (4)00006 native drive profile reference 2 - most significant 16-bits (4)00007 data out 1 (4)00008 data out 2 (4)00009 dat...

  • Page 105

    Modbus/tcp – communication protocol 105 (4)00059 data in 3 (4)00060 data in 4 (4)00061 data in 5 (4)00062 data in 6 (4)00063 data in 7 (4)00064 data in 8 (4)00065 data in 9 (4)00066 data in 10 (4)00067 data in 11 (4)00068 data in 12 (4)00101…(4)09999 drive parameter access (16-bit) register address ...

  • Page 106

    106 modbus/tcp – communication protocol.

  • Page 107: Modbus/tcp – Diagnostics

    Modbus/tcp – diagnostics 107 9 modbus/tcp – diagnostics contents of this chapter this chapter explains how to trace faults with the status leds on the adapter module when the module is used for modbus/tcp communication. Fault and warning messages for the fault and warning messages concerning the ada...

  • Page 108: Leds

    108 modbus/tcp – diagnostics leds the adapter module is equipped with three bicolor diagnostic leds. The leds are described below. Name color function host blinking green establishing communication to host green connection to host ok blinking red communication to host lost temporarily flashing orang...

  • Page 109

    Modbus/tcp – diagnostics 109 module off there is no power applied to the device. Flashing orange device is attempting to obtain ip configuration from the dhcp server. Orange device is executing duplicate address detection. Flashing green device is waiting for a modbus request. Green device has recei...

  • Page 110

    110 modbus/tcp – diagnostics internal error code registers a modbus query can fail in many ways in the drive. The modbus standard does not specify detailed error descriptions. In addition to the standard error codes, the fena adapter module provides an internal error register area for more detailed ...

  • Page 111

    Modbus/tcp – diagnostics 111 0x71 parameter group ended an attempt to write to multiple parameter groups 0x72 msb is not zero an attempt to write a 16-bit parameter with a 32-register address and the msb bytes are not zero 0x73 lsb query start an attempt to access only the lsb register of the 32-bit...

  • Page 112

    112 modbus/tcp – diagnostics.

  • Page 113: Ethernet/ip Protocol

    Ethernet/ip protocol ethernet/ip – start-up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 ethernet/ip – communication profiles . . . . . . . . . . . . . . . . . . . 159 ethernet/ip – communication protocol . . . . . . . . . . . . . . . . . . . 181 ethernet/ip – diagnostics . . ...

  • Page 115: Ethernet/ip – Start-Up

    Ethernet/ip – start-up 115 6 ethernet/ip – start-up contents of this chapter 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 client for com...

  • Page 116: Drive Configuration

    116 ethernet/ip – start-up drive configuration the information in this section applies to all drive types compatible with the adapter module, unless otherwise stated. Ethernet/ip connection configuration after the adapter module has been mechanically and electrically installed according to the instr...

  • Page 117

    Ethernet/ip – start-up 117 fena-01/-11/-21 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 and acs580 if the adapt...

  • Page 118

    118 ethernet/ip – start-up 03 comm rate sets the bit rate for the ethernet interface. 0 = auto acs355: fb par 3 acsm1: fba par3 acs850/acq810: fba par3 acs880/acs580: commrate 0 = auto autonegotiate 1 = 100 mbps fd 100 mbps, full duplex 2 = 100 mbps hd 100 mbps, half duplex 3 = 10 mbps fd 10 mbps, f...

  • Page 119

    Ethernet/ip – start-up 119 08 ip address 4 see parameter 05 ip address 1 . 0 acs355: fb par 8 acsm1: fba par8 acs850/acq810: fba par8 acs880/acs580: ip address 4 0…255 ip address 09 subnet cidr subnet masks are used for splitting networks into smaller networks called subnets. A subnet mask is a 32-b...

  • Page 120

    120 ethernet/ip – start-up 10 gw address 1 ip gateways connect individual physical ip subnets into a unified ip network. When an ip node needs to communicate with an ip node on another subnet, the ip node sends the data to the ip gateway for forwarding. Parameters 10 … 13 define the four octets of t...

  • Page 121

    Ethernet/ip – start-up 121 19 t16 scale defines the reference multiplier/actual value divisor for the adapter module. The parameter is effective only when the transparent 16 profile is selected and the drive is using the native communication profile (eg, dcu or fba) and a 16-bit transparent referenc...

  • Page 122

    122 ethernet/ip – start-up 20 control timeout defines the control timeout value. The ethernet/ip protocol specifies connection timeout for i/o messaging (class 1) and connected explicit messaging (class 3), but not unconnected explicit messaging. This parameter provides a timeout for unconnected exp...

  • Page 123

    Ethernet/ip – start-up 123 control timeout events: • write of an output assembly object instance • write of control bits (run1, run2, netctrl, netref and faultreset) • write speed reference • write torque reference • reset control supervisor object • write force fault via control supervisor object i...

  • Page 124

    124 ethernet/ip – start-up 22 odva stop function determines how the motor is to be stopped when a stop command is received via ethernet/ip. This parameter only applies to the odva ac/dc drive profile. 0 = ramp acs355: fb par 22 acsm1: fba par22 acs850/acq810: fba par22 acs880/acs580: stop function 0...

  • Page 125

    Ethernet/ip – start-up 125 23 odva speed scale this parameter only applies to the odva ac/dc drive profile. The units of reference and actual speeds for the odva ac/dc drive profile are given by the formula below. Speed unit = rpm × 2 (-1 × odva speed scale value) note: while a wide range of resolut...

  • Page 126

    126 ethernet/ip – start-up 24 odva torque scale this parameter only applies to the odva ac/dc drive profile. The units of reference and actual torques for the odva ac/dc drive profile are given by the formula below. Torque unit = n·m × 2 (-1 × odva torque scale) where: (n·m = newton × meter) note: w...

  • Page 127

    Ethernet/ip – start-up 127 27 fba par refresh validates any changed adapter module configuration parameter settings. After refreshing, the value reverts automatically to 0 = done. Note: this parameter cannot be changed while the drive is running. 0 = done acs355/acsm1: fba par refresh acs850/acq810:...

  • Page 128

    128 ethernet/ip – start-up 30 mapping file ver read-only. Displays the fieldbus adapter module mapping file revision stored in the memory of the drive in decimal format. N/a acs355: file config rev acsm1: mapping file ver acs850/acq810: mapping file ver acs880/acs580: fba a/b mapping file ver mappin...

  • Page 129

    Ethernet/ip – start-up 129 32 fba comm sw ver read-only. Displays the common program revision of the adapter module in format axyz, where: a = major revision number xy = minor revision numbers z = correction number or letter. N/a acs355: fba cpi fw rev acsm1: fba comm sw ver acs850/acq810: fba comm ...

  • Page 130

    130 ethernet/ip – start-up fena-01/-11/-21 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 ...

  • Page 131

    Ethernet/ip – start-up 131 fena-01/-11/-21 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 ...

  • Page 132: Control Locations

    132 ethernet/ip – start-up control locations abb drives can receive control information from multiple sources including digital inputs, analog inputs, the drive control panel and a fieldbus adapter module. Abb drives allow the user to separately determine the source for each type of control informat...

  • Page 133: Drives

    Ethernet/ip – start-up 133 starting up fieldbus communication for acs355 drives 1. Power up the drive. 2. Enable the communication between the adapter module and the drive with parameter 9802 comm prot sel. 3. Set the module configuration parameters in group 51. At the minimum, select the communicat...

  • Page 134

    134 ethernet/ip – start-up parameter setting examples – acs355 speed control using the odva ac/dc drive profile, extended speed control assembly this example shows how to configure a speed control application that uses the odva ac/dc drive profile, extended speed control assembly. In addition, some ...

  • Page 135

    Ethernet/ip – start-up 135 5103 fb par 3 (commrate) 0 (= auto) 2) ethernet communication rate is negotiated automatically by the device. 5104 fb par 4 (ip configuration) 0 (= static ip) 2) configuration will be obtained from parameters 05 ... 13 . 5105 fb par 5 (ip address 1) 192 2) first part of th...

  • Page 136

    136 ethernet/ip – start-up the start sequence for the parameter example above is given below. Control word: • reset the fieldbus communication fault (if active). • enter 0h (0 decimal) –> ready. • enter 1h (1 decimal) –> enabled (running forward) or enter 2h (2 decimal) –> enabled (running reverse)....

  • Page 137: Drives

    Ethernet/ip – start-up 137 starting up fieldbus communication for acsm1 drives 1. Power up the drive. 2. Enable the communication between the adapter module and the drive with parameter 50.01 fba enable. 3. With parameter 50.02 comm loss func, select how the drive reacts to a fieldbus communication ...

  • Page 138

    138 ethernet/ip – start-up 9. 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 – acsm1 speed control using the odva ac/dc drive profile, extended speed control assembl...

  • Page 139

    Ethernet/ip – start-up 139 the table below gives the recommended drive parameter settings. Drive parameter setting for acsm1 drives description 50.01 fba enable enable enables communication between the drive and the fieldbus adapter module. 50.02 comm loss func fault 2) enables fieldbus communicatio...

  • Page 140

    140 ethernet/ip – start-up the start sequence for the parameter example above is given below. Control word: • reset the fieldbus communication fault (if active). • enter 0h (0 decimal) –> ready. • enter 1h (1 decimal) –> enabled (running forward). • enter 2h (2 decimal) –> enabled (running reverse)....

  • Page 141: And Acq810 Drives

    Ethernet/ip – start-up 141 starting up fieldbus communication for acs850 and acq810 drives 1. Power up the drive. 2. Enable the communication between the adapter module and the drive with parameter 50.01 fba enable. 3. With parameter 50.02 comm loss func, select how the drive reacts to a fieldbus co...

  • Page 142

    142 ethernet/ip – start-up 7. Define the process data transferred to and from the drive in parameter groups 52 and 53. Note: the adapter module assigns the control word, status word, references 1…2 and actual values 1…2 automatically to cyclical communication according to the selected assembly insta...

  • Page 143

    Ethernet/ip – start-up 143 the minimum and maximum 16-bit integer values that can be given through the fieldbus are -32768 and 32767 respectively. The table below gives the recommended drive parameter settings. Bytes instance 121 instance 171 0 … 1 control word status word 2 … 3 speed reference spee...

  • Page 144

    144 ethernet/ip – start-up the start sequence for the parameter example above is given below. Control word: • reset the fieldbus communication fault (if active). • enter 0h (0 decimal) –> ready. • enter 1h (1 decimal) –> enabled (running forward). • enter 2h (2 decimal) –> enabled (running reverse)....

  • Page 145: And Acs580 Drives

    Ethernet/ip – start-up 145 starting up fieldbus communication for acs880 and acs580 drives 1. Power up the drive. 2. Enable the communication between the adapter module and the drive by selecting the correct slot number in parameter 50.01 fba a enable. The selection must correspond to the slot where...

  • Page 146

    146 ethernet/ip – start-up 8. Save the valid parameter values to permanent memory with parameter 96.07 parameter save manually. 9. Validate the settings made in parameter groups 51, 52 and 53 with parameter 51.27 fba a par refresh. 10. Set the relevant drive control parameters to control the drive a...

  • Page 147

    Ethernet/ip – start-up 147 the table below gives the recommended drive parameter settings. Drive parameter setting for acs880 /acs580 drives description 50.01 fba a enable 1 = option slot 1 2) enables communication between the drive and the fieldbus adapter module. 50.02 fba a comm loss func 1 = fau...

  • Page 148

    148 ethernet/ip – start-up the start sequence for the parameter example above is given below. Control word: • reset the fieldbus communication fault (if active). • enter 0h (0 decimal) –> ready. • enter 1h (1 decimal) –> enabled (running forward). • enter 2h (2 decimal) –> enabled (running reverse)....

  • Page 149: Configuring The Client

    Ethernet/ip – start-up 149 configuring the client after the adapter module has been initialized by the drive, you must prepare the client for communication with the module. An example of an allen-bradley® plc is given below. If you are using another client system, refer to its documentation for more...

  • Page 150

    150 ethernet/ip – start-up enhanced speed control plus drive parameters 121 171 24 odva ac/dc drive basic speed and torque control plus drive parameters 122 172 26 odva ac/dc drive enhanced speed and torque control plus drive parameters 123 173 26 odva ac/dc drive abb drives profile w/ set speed 1 5...

  • Page 151: Select Connection Method

    Ethernet/ip – start-up 151 select connection method ethernet/ip provides a variety of connection methods to communicate between devices. Not all methods are supported by all devices. Refer to the client documentation to determine which method(s) are supported by the client. Note: the choice of the c...

  • Page 152: Eds Files

    152 ethernet/ip – start-up eds files electronic data sheet (eds) files specify the properties of the device for the ethernet/ip client. The client identifies the device by means of the product code, device type and major revision attributes. To enable the use of different abb drive types on the same...

  • Page 153: Plc

    Ethernet/ip – start-up 153 configuring an allen-bradley ® plc this example shows how to prepare an allen-bradley® control- logix5555™ plc for communication with the adapter module by using the rslogix 5000® software as the configuration tool. 1. Start the rslogix software and open/create an rslogix ...

  • Page 154

    154 ethernet/ip – start-up 3. In the select module window, select ethernet-module..

  • Page 155

    Ethernet/ip – start-up 155 4. Select the input and output assembly instances and the plc i/o memory size to be used. The table below shows the available combinations. The example below uses the odva ac/dc assembly instances 121 and 171. For more information on the input/output assembly instances, se...

  • Page 156

    156 ethernet/ip – start-up 5. Enter the following information. The example below uses odva ac/dc assembly instances 121 and 171. The plc will transmit and receive 12 words. Type a name for the adapter module. Type the input and output assembly instance numbers. Select the sizes of the input and outp...

  • Page 157: 6. Click Ok.

    Ethernet/ip – start-up 157 6. Click ok. The adapter module is now added to the plc i/o. 7. Click the fena module to open the module properties window..

  • Page 158

    158 ethernet/ip – start-up 8. On the connection tab, select the requested packet interval (rpi) for the adapter module i/o communication. 9. Download the new configuration to the plc. The plc is now ready for communication with the adapter module..

  • Page 159: Profiles

    Ethernet/ip – communication profiles 159 11 ethernet/ip – communication profiles contents of this chapter this chapter describes the communication profiles used in the communication between the ethernet/ip client, the adapter module and the drive. Communication profiles communication profiles are wa...

  • Page 160

    160 ethernet/ip – communication profiles the figure below illustrates the profile selection: 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 n...

  • Page 161: Odva Ac/dc Drive Profile

    Ethernet/ip – communication profiles 161 odva ac/dc drive profile this section briefly describes the odva ac/dc drive profile. Additional information is available at www.Odva.Org . An ethernet/ip node is modeled as a collection of abstract objects. Each object represents the interface to and behavio...

  • Page 162: Odva Output Attributes

    162 ethernet/ip – communication profiles odva output attributes this section briefly describes the instances found in the output assemblies of the odva ac/dc drive profile. Note that all output assembly instances do not support all attributes listed here. Run forward & run reverse (control superviso...

  • Page 163

    Ethernet/ip – communication profiles 163 speed reference (ac/dc drive object) this attribute is the speed reference for the drive. The units are scaled by the speed scale attribute of the ac/dc drive object. See parameter 23 odva speed scale for details. Scalar mode when the drive is operating in th...

  • Page 164

    164 ethernet/ip – communication profiles vector mode when the drive is operating in the vector mode, the adapter module provides the drive with a speed reference. The odva ac/dc drive profile uses rpm units for the speed reference. The drive speed reference is calculated as follows: where for exampl...

  • Page 165

    Ethernet/ip – communication profiles 165 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 parameter 24 odva torque scale for details. The adapter module provides the drive wit...

  • Page 166: Odva Input Attributes

    166 ethernet/ip – communication profiles odva input attributes this section briefly describes the instances found in the odva ac/dc drive profile’s input assemblies. Note that all input assembly instances do not support all attributes listed here. Faulted (control supervisor object) this attribute i...

  • Page 167

    Ethernet/ip – communication profiles 167 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...

  • Page 168

    168 ethernet/ip – communication profiles 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 r...

  • Page 169

    Ethernet/ip – communication profiles 169 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 parameter 23 odva speed scale for details. Scalar mode when the drive ...

  • Page 170

    170 ethernet/ip – communication profiles 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 d...

  • Page 171

    Ethernet/ip – communication profiles 171 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 parameter 24 odva torque scale for details. The drive provides the...

  • Page 172: Control Word Contents

    172 ethernet/ip – communication profiles abb drives communication profile control word and status word the control word is the principal means for controlling the drive from a fieldbus system. It is sent by the fieldbus client station to the drive through the adapter module. The drive switches betwe...

  • Page 173

    Ethernet/ip – communication profiles 173 3 inhibit_ operation 1 proceed to operation enabled. Note: run enable signal must be active; see drive documentation. If the drive is set to receive the run enable signal from the fieldbus, this bit activates the signal. 0 inhibit operation. Proceed to operat...

  • Page 174

    174 ethernet/ip – communication profiles 10 remote_ cmd 1 fieldbus control enabled. 0 control word and reference not getting through to the drive, except for cw bits off1, off2 and off3. 11 ext_ctrl_ loc 1 select external control location ext2. Effective if control location parameterized to be selec...

  • Page 175: Status Word Contents

    Ethernet/ip – communication profiles 175 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 177 . Bit name value state/description 0 rdy_on 1 ready t...

  • Page 176

    176 ethernet/ip – communication profiles 10 above_ limit 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 11 ext_ctrl_ loc 1 external control location ext2 selected. No...

  • Page 177: State Machine

    Ethernet/ip – communication profiles 177 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 inhibit...

  • Page 178: References

    178 ethernet/ip – communication profiles 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. Abb drives can receive...

  • Page 179: Actual Values

    Ethernet/ip – communication profiles 179 actual values actual values are 16-bit words containing information on the operation of the drive. The functions to be monitored are selected with a drive parameter. Scaling actual values are scaled as shown below. Note: the values of ref1 max and ref2 max ar...

  • Page 180

    180 ethernet/ip – communication profiles.

  • Page 181: Protocol

    Ethernet/ip – communication protocol 181 12 ethernet/ip – communication protocol contents of this chapter this chapter describes the ethernet/ip communication protocol for the adapter module. Ethernet/ip ethernet/ip is a variant of the common industrial protocol (cip) family of communication protoco...

  • Page 182: Assembly Objects

    182 ethernet/ip – communication protocol object modeling and functional profiles one of the main features of ethernet/ip is object modeling. A group of objects can be described with a functional profile. The fena adapter module realizes the odva ac/dc drive functional profile with additional feature...

  • Page 183: Assembly

    Ethernet/ip – communication protocol 183 the format of the input assembly is: 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 prof...

  • Page 184

    184 ethernet/ip – communication protocol the format of the input assembly is: 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 value (low byte) 17 data out 7 value (high byte) 18 data out 8 value (low byte) 19 data out 8 value (high byte) 2...

  • Page 185

    Ethernet/ip – communication protocol 185 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: 12 data in 5 value (low byte) 13 data in 5 value (high byte) 14 data in 6 value (low byte) 15 data in 6 value...

  • Page 186: Assembly

    186 ethernet/ip – communication protocol the format of the input assembly is: 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 d...

  • Page 187

    Ethernet/ip – communication protocol 187 the format of the input assembly is: 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 value (low byte) 17 data out 7 value (high byte) 1...

  • Page 188

    188 ethernet/ip – communication protocol 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 data in 6 value (high byte) 16 data in 7 value (low byte) 17 data in 7 val...

  • Page 189

    Ethernet/ip – communication protocol 189 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: the format of the input assembly is: instance 22 (odva ac/dc profile) byte bit 7 bit 6 bit 5 ...

  • Page 190: Parameters Assembly

    190 ethernet/ip – communication protocol 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 odva ac/dc drive profile....

  • Page 191

    Ethernet/ip – communication protocol 191 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 172 (odva ac/dc profile) byte bit 7 bit 6 bit 5 bit 4...

  • Page 192

    192 ethernet/ip – 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: 18 data in 7 value (low byte) 19 data in 7 value (high byte) 20 data in 8 value (low by...

  • Page 193: Parameters Assembly

    Ethernet/ip – communication protocol 193 the format of the input assembly is: 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 con...

  • Page 194

    194 ethernet/ip – communication protocol the format of the input assembly is: 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 data out 5 value (low byte) 15 data out 5 value (high byte) 16...

  • Page 195

    Ethernet/ip – communication protocol 195 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 (hi...

  • Page 196

    196 ethernet/ip – communication protocol 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: the format of the input assembly is: instance 1 (abb drives profile) byte bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bi...

  • Page 197: Parameters Assembly

    Ethernet/ip – communication protocol 197 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 abb drives profile. The f...

  • Page 198

    198 ethernet/ip – communication protocol the format of the input assembly is: 19 data out 8 value (high byte) 20 data out 9 value (low byte) 21 data out 9 value (high byte) 22 data out 10 value (low byte) 23 data out 10 value (high byte) instance 151 (abb drives profile) byte bit 7 bit 6 bit 5 bit 4...

  • Page 199: Torque Assembly

    Ethernet/ip – communication protocol 199 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: 16 data in 7 value (low byte) 17 data in 7 value (high byte) 18 data in 8 value (l...

  • Page 200

    200 ethernet/ip – communication protocol the format of the input assembly is: 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...

  • Page 201

    Ethernet/ip – communication protocol 201 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 data out...

  • Page 202

    202 ethernet/ip – communication protocol the format of the input assembly is: instance 152 (abb drives profile) byte bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 0 alarm swc on inhib off 3 sta off 2 sta tripped rdy ref rdy run rdy on 1 field- bus error ext run enable ext ctrl loc above limit remo...

  • Page 203

    Ethernet/ip – communication protocol 203 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: the format of the input assembly is: 24 data in 10 value (low byte) ...

  • Page 204: Parameters

    204 ethernet/ip – communication protocol 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 assembly is: instance 111 (...

  • Page 205

    Ethernet/ip – communication protocol 205 the format of the input assembly is: 22 data out 10 value (low byte) 23 data out 10 value (high byte) instance 161 (transparent 16 profile) 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-b...

  • Page 206

    206 ethernet/ip – communication protocol 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: the format of the input assembly is: 22 data in 10 value (low byte) ...

  • Page 207: Parameters

    Ethernet/ip – communication protocol 207 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 assembly is: instance 112 (...

  • Page 208

    208 ethernet/ip – communication protocol the format of the input assembly is: 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 162 (transparent 16 profile) byte bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 0 d...

  • Page 209

    Ethernet/ip – communication protocol 209 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: 20 data in 8 value (low byte) 21 data in 8 value (high byte) 22 data...

  • Page 210: Parameters

    210 ethernet/ip – communication protocol the format of the input assembly is: 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 t...

  • Page 211

    Ethernet/ip – communication protocol 211 the format of the input assembly is: 10 data out 2 value (low byte) 11 data out 2 value (high byte) 12 data out 3 value (low byte) 13 data out 3 value (high byte) 14 data out 4 value (low byte) 15 data out 4 value (high byte) 16 data out 5 value (low byte) 17...

  • Page 212

    212 ethernet/ip – communication protocol 6 drive profile 32-bit actual 1 word 7 drive profile 32-bit actual 1 word (high byte) 8 data in 1 value (low byte) 9 data in 1 value (high byte) 10 data in 2 value (low byte) 11 data in 2 value (high byte) 12 data in 3 value (low byte) 13 data in 3 value (hig...

  • Page 213

    Ethernet/ip – communication protocol 213 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: the format of the input assembly is: instance 22 (transparent 32 pro...

  • Page 214: Parameters

    214 ethernet/ip – 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: 8 drive profil...

  • Page 215

    Ethernet/ip – communication protocol 215 the format of the input assembly is: 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 value (high byte) 20 data out 5 value (low byte) 21 data out 5 value (high byte) 22 data out 6 value (low byte) 23...

  • Page 216

    216 ethernet/ip – communication protocol 8 drive profile 32-bit actual 2 word (low byte) 9 drive profile 32-bit actual 2 word 10 drive profile 32-bit actual 2 word 11 drive profile 32-bit actual 2 word (high byte) 12 data in 1 value (low byte) 13 data in 1 value (high byte) 14 data in 2 value (low b...

  • Page 217: Class Objects

    Ethernet/ip – communication protocol 217 class objects the following table lists the data types used in the class object descriptions of this manual. Note: the adapter module is designed to provide ethernet/ip communications for a variety of drives with different capabilities. Default, minimum and m...

  • Page 218: Class Attributes (Instance

    218 ethernet/ip – communication protocol identity object, class 01h this object provides identification of and general information about the device. Class attributes (instance #0) instance attributes (instance #1) attribute explanations vendor id vendor ids are managed by the open devicenet vendor a...

  • Page 219

    Ethernet/ip – communication protocol 219 device type the list of device types is managed by odva. It is used to identify the device profile that a particular product is using. Product code every abb drive type or application of the drive has a dedicated product code. The product code is 100 + the va...

  • Page 220

    220 ethernet/ip – communication protocol odva serial number this attribute is a number used in conjunction with the vendor id to form a unique identifier for each device on ethernet/ip. The value of this attribute is 02000000h plus the serno value from the device label. Product name this text string...

  • Page 221: Class Attributes (Instance

    Ethernet/ip – communication protocol 221 motor data object, class 28h the motor data object can only be used if the odva ac/dc drive profile is in use. The object serves as a database for motor parameters. Different motor types require different data to describe the motor. For example, ac induction ...

  • Page 222: Class Attributes (Instance

    222 ethernet/ip – communication protocol control supervisor object, class 29h the control supervisor object can only be used if the odva ac/dc drive profile is in use. The object models all the management functions for devices within the ‘hierarchy of motor control devices’. The behavior of motor co...

  • Page 223

    Ethernet/ip – communication protocol 223 instance attributes (instance #1) # attribute name services description data type 3 run 1 get, set 0 = stop, 1 = run. See the run/stop event matrix on page 162 . Bool 4 run 2 get, set 0 = stop, 1 = run. See the run/stop event matrix on page 162 . Bool 5 net c...

  • Page 224: Class Attributes (Instance

    224 ethernet/ip – communication protocol ac/dc-drive object, class 2ah the ac/dc-drive object can only be used if the odva ac/dc drive profile is in use. The object models the functions specific to an ac or dc drive. Class attributes (instance #0) 14 warning code get code word indicating the warning...

  • Page 225

    Ethernet/ip – communication protocol 225 instance attributes (instance #1) # attribute name services description data type 3 at reference get frequency arrival bool 4 netref get, set requests torque or speed reference to be local or from the network. 0 = set reference not dn control 1 = set referenc...

  • Page 226

    226 ethernet/ip – communication protocol drive parameter object, class 90h with the fena adapter module, 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 you use the drive parame...

  • Page 227: Class Attributes

    Ethernet/ip – communication protocol 227 fieldbus configuration object, class 91h the fieldbus configuration object allows you to configure the fieldbus configuration groups without the need to know the drive- specific groups associated with the configuration groups. Note: when you use the fieldbus ...

  • Page 228

    228 ethernet/ip – communication protocol 4 configuration group a (group 1) - parameter 4 get, set see 04 ip configuration on page 118 . Uint16 5 configuration group a (group 1) - parameter 5 get, set see 05 ip address 1 … 08 ip address 4 . Uint16 6 configuration group a (group 1) - parameter 6 get, ...

  • Page 229

    Ethernet/ip – communication protocol 229 16 configuration group a (group 1) - parameter 16 get, set see 14… 18 reserved on page 120 . Uint16 17 configuration group a (group 1) - parameter 17 get, set see 14… 18 reserved on page 120 . Uint16 18 configuration group a (group 1) - parameter 18 get, set ...

  • Page 230

    230 ethernet/ip – communication protocol 28 configuration group a (group 1) - parameter 28 get see 28 par table ver on page 127 . Uint16 29 configuration group a (group 1) - parameter 29 get see 29 drive type code on page 127 . Uint16 30 configuration group a (group 1) - parameter 30 get see 30 mapp...

  • Page 231: Group B (Group 2)

    Ethernet/ip – communication protocol 231 instance #2: fena-01/-11/-21 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 ...

  • Page 232: Group C (Group 3)

    232 ethernet/ip – communication protocol instance #3: fena-01/-11/-21 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 ...

  • Page 233: Class Attributes (Instance

    Ethernet/ip – communication protocol 233 tcp/ip interface object, class f5h this object provides the mechanism to configure the tcp/ip network interface of the device. Class attributes (instance #0) instance attributes (instance #1) # attribute name services description data type 1 revision get revi...

  • Page 234: Attribute Explanations

    234 ethernet/ip – communication protocol attribute explanations interface status attribute (#1) bits 5 interface configuration get struct of: ip address ip address udint network mask network mask udint gateway address gateway address udint unused udint unused udint default domain name default domain...

  • Page 235

    Ethernet/ip – communication protocol 235 configuration capability attribute (#2) bits 4 mcast pending indicates a pending configuration change in the ttl value and/or mcast config attributes. This bit is set when either the ttl value or mcast config attribute is set, and cleared the next time the de...

  • Page 236: Class Attributes (Instance

    236 ethernet/ip – communication protocol configuration control attribute (#3) bits ethernet link object, class f6h this object maintains link-specific counters and status information for the ethernet communication interface. Class attributes (instance #0) bit name description 0…3 start-up configurat...

  • Page 237

    Ethernet/ip – communication protocol 237 instance attributes (instance #1) connection object, class 05h do not modify this object. This object is only used while establishing the connection between the adapter module and the plc. The connection class allocates and manages the internal resources asso...

  • Page 238: Class Attributes

    238 ethernet/ip – communication protocol class attributes instance attributes # attribute name services description data type 1 revision get revision of the connection object array of uint8 instance number description 1 explicit messaging connection 2 polled i/o connection 4 change-of-state/cyclic i...

  • Page 239

    Ethernet/ip – communication protocol 239 8 con- sumed connec- tion size get maximum number of bytes received across this connection uint16 9 expected packet rate get, set defines the timing associated with this connection in milliseconds. A value of 0 deactivates the associated timers. Uint16 12 wat...

  • Page 240: Class Attributes (Instance

    240 ethernet/ip – communication protocol 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 t...

  • Page 241: Ethernet/ip – Diagnostics

    Ethernet/ip – diagnostics 241 13 ethernet/ip – diagnostics contents of this chapter this chapter explains how to trace faults with the status leds on the adapter module when the module is used for ethernet/ip communication. Fault and warning messages for the fault and warning messages concerning the...

  • Page 242: Leds

    242 ethernet/ip – diagnostics leds the adapter module is equipped with three bicolor diagnostic leds. The leds are described below. Name color function host blinking green establishing communication to host green connection to host ok blinking red communication to host lost temporarily flashing oran...

  • Page 243

    Ethernet/ip – diagnostics 243 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. This may be caused by the adapte...

  • Page 244

    244 ethernet/ip – diagnostics network /net off device is not on-line. • the device has not completed the duplicate address detection yet. • the 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. • the device has...

  • Page 245: Profinet Io Protocol

    Profinet io protocol profinet io – start-up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247 profinet io – communication profiles . . . . . . . . . . . . . . . . . 305 profinet io – communication protocol . . . . . . . . . . . . . . . . 323 profinet io – diagnostics . . . . . . . . . . ...

  • Page 247: Profinet Io – Start-Up

    Profinet io – start-up 247 14 profinet io – start-up contents of this chapter 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 statio...

  • Page 248: Drive Configuration

    248 profinet io – start-up drive configuration the information in this section applies to all drive types compatible with the adapter module, unless otherwise stated. Profinet io connection configuration after the adapter module has been mechanically and electrically installed according to the instr...

  • Page 249

    Profinet io – start-up 249 fena-01/-11/-21 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 and acs580 if the adapt...

  • Page 250

    250 profinet io – start-up 03 comm rate sets the bit rate for the ethernet interface. 0 = auto acs355: fb par 3 acsm1: fba par3 acs850/acq810: fba par3 acs880/acs580: commrate 0 = auto autonegotiate 1 = 100 mbps fd 100 mbps, full duplex 2 = 100 mbps hd 100 mbps, half duplex 3 = 10 mbps fd 10 mbps, f...

  • Page 251

    Profinet io – start-up 251 05 ip address 1 an ip address is assigned to each ip node on a network. An ip address is a 32-bit number that is typically represented in “dotted decimal” notation consisting of four decimal integers, on the range 0…255, separated by periods. Each integer represents the va...

  • Page 252

    252 profinet io – start-up 09 subnet cidr subnet masks are used for splitting networks into smaller networks called subnets. A subnet mask is a 32-bit binary number that splits the ip address into a network address and host address. Subnet masks are typically represented in either dotted decimal not...

  • Page 253

    Profinet io – start-up 253 … … … … 13 gw address 4 see parameter 10 gw address 1 . 0 acs355: fb par 13 acsm1: fba par13 acs850/acq810: fba par13 acs880/acs580: gw address 4 0…255 gw address 14 … 18 reserved these parameters are not used by the adapter module when the module is configured for profine...

  • Page 254

    254 profinet io – start-up 20 telegram type read-only. Indicates the telegram type selected for profinet io communication. The adapter module automatically detects the telegram type defined in the plc. For more information on the supported ppo message types, see section ppo types on page 326 . 0 = u...

  • Page 255

    Profinet io – start-up 255 22 map selection defines the preferred data type of mapped parameters when mapping is done through profidrive parameters. Supported with acs880 and acs580 drives. 1 = 16bit acs355: fb par 22 acsm1: fba par22 acs850/acq810: fba par22 acs880/acs580: map selection 0 = 32bit 3...

  • Page 256

    256 profinet io – start-up 29 drive type code read-only. Displays the drive type code of the fieldbus adapter module mapping file stored in the memory of the drive. N/a acs355: file config id acsm1: drive type code acs850/acq810: drive type code acs880/acs580: fba a/b drive type code drive type code...

  • Page 257

    Profinet io – start-up 257 3 = conf.Err adapter configuration error: the major or minor revision code of the common program revision in the fieldbus adapter module is not the revision required by the module or mapping file upload has failed more than three times. 4 = off-line adapter is off-line. 5 ...

  • Page 258

    258 profinet io – start-up fena-01/-11/-21 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 ...

  • Page 259

    Profinet io – start-up 259 02 data out 2 see parameter 01 data out 1 . 0 or 2 4) 03… 10 data out 3… data out 10 see parameter 01 data out 1 . 0 1) the number of parameters in this group may vary by drive type and drive firmware. 2) 11 (cw 32bit) is the default setting if the transparent 32 profile i...

  • Page 260

    260 profinet io – start-up fena-01/-11/-21 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 ...

  • Page 261

    Profinet io – start-up 261 virtual address area allocation with acsm1 when the profidrive profile or profidrive positioning mode is used with an acsm1 drive, the virtual addresses shown below are recommended. (fba refx mode is selected with drive parameter 50.04/50.05.) the information in the table ...

  • Page 262: Control Locations

    262 profinet io – start-up control locations abb drives can receive control information from multiple sources including digital inputs, analog inputs, the drive control panel and a fieldbus adapter module. Abb drives allow the user to separately determine the source for each type of control informat...

  • Page 263: Drives

    Profinet io – start-up 263 starting up fieldbus communication for acs355 drives 1. Power up the drive. 2. Enable the communication between the adapter module and the drive with parameter 9802 comm prot sel. 3. Set the module configuration parameters in group 51. At the minimum, select the communicat...

  • Page 264: Profile With Ppo Type 4

    264 profinet io – start-up parameter setting examples – acs355 speed control using the profidrive communication profile with ppo type 4 this example shows how to configure a basic speed control application that uses the profidrive profile. In addition, some application-specific data is added to the ...

  • Page 265

    Profinet io – start-up 265 5106 fb par 6 (ip address 2) 168 2) second part of the ip address 5107 fb par 7 (ip address 3) 0 2) third part of the ip address 5108 fb par 8 (ip address 4) 16 2) last part of the ip address 5109 fb par 9 (subnet cidr) 24 2) sets the network mask as 255.255.255.0, allowin...

  • Page 266

    266 profinet io – start-up the start sequence for the parameter example above is given below. Control word: • reset the fieldbus communication fault (if active). • enter 47eh (1150 decimal) –> ready to switch on. • enter 47fh (1151 decimal) –> operating (speed mode). Speed and torque control using t...

  • Page 267

    Profinet io – start-up 267 the table below gives the recommended drive parameter settings. Drive parameter setting for acs355 drives description 9802 comm prot sel 4 = ext fba enables communication between the drive and the fieldbus adapter module. 5101 fba type ethernet 1) displays the type of the ...

  • Page 268

    268 profinet io – start-up the start sequence for the parameter example above is given below. Control word: • reset the fieldbus communication fault (if active). • enter 47eh (1150 decimal) –> ready to switch on. • enter 47fh (1151 decimal) –> operating (speed mode) or c7fh (3199 decimal) –> operati...

  • Page 269: Drives

    Profinet io – start-up 269 starting up fieldbus communication for acsm1 drives 1. Power up the drive. 2. Enable the communication between the adapter module and the drive with parameter 50.01 fba enable. 3. With parameter 50.02 comm loss func, select how the drive reacts to a fieldbus communication ...

  • Page 270: Profile With Ppo Type 4

    270 profinet io – start-up 9. 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 – acsm1 speed control using the profidrive communication profile with ppo type 4 this ex...

  • Page 271

    Profinet io – start-up 271 51.01 fba type ethernet 1) displays the type of the fieldbus adapter module. 51.02 fba par2 (protocol/profile) 10 (= pnio pdrive) selects the profinet io protocol and profidrive profile. 51.03 fba par3 (commrate) 0 (= auto) 2) ethernet communication rate is negotiated auto...

  • Page 272: Profile With Ppo Type 4

    272 profinet io – start-up the start sequence for the parameter example above is given below. Control word: • reset the fieldbus communication fault (if active). • enter 47eh (1150 decimal) –> ready to switch on. • enter 47fh (1151 decimal) –> operating (speed mode). Position control using the profi...

  • Page 273

    Profinet io – start-up 273 50.05 fba ref2 modesel velocity selects the fieldbus reference 2 scaling. 51.01 fba type ethernet 1) displays the type of the fieldbus adapter module. 51.02 fba par2 (protocol/profile) 14 (= pnio pdrivem) selects the profinet io protocol and profidrive positioning mode. 51...

  • Page 274

    274 profinet io – start-up the position set point is scaled as follows: 34.04 ext1 ctrl mode2 homing selects homing control as the control mode 2 for external control location 1. 62.01 homing method can methodxx selects the homing mode. Select the appropriate can method. 62.03 homing start c.False s...

  • Page 275

    Profinet io – start-up 275 the position set point and actual values are scaled with the above example values as follows: example for velocity set point scale: the velocity set point and actual values are scaled with the above example values as follows: pay attention to the following parameters: driv...

  • Page 276

    276 profinet io – start-up the start sequence for the above parameter example is given below: control word: • reset the fieldbus communication fault (if active). • enter 406h (1030 decimal) –> ready to switch on. • enter 40fh (1039 decimal) –> operating. • enter 43fh (1087 decimal) –> operating (do ...

  • Page 277

    Profinet io – start-up 277 the table below gives the recommended drive parameter settings. Drive parameter setting for acsm1 drives description 50.01 fba enable enable enables communication between the drive and the fieldbus adapter module. 50.02 comm loss func fault enables fieldbus communication f...

  • Page 278

    278 profinet io – start-up the start sequence for the parameter example above is given below. Control word: • reset the fieldbus communication fault (if active). • enter 47eh (1150 decimal) –> ready to switch on. • enter 47fh (1151 decimal) –> operating (speed mode) or c7fh (3199 decimal) –> operati...

  • Page 279: And Acq810 Drives

    Profinet io – start-up 279 starting up fieldbus communication for acs850 and acq810 drives 1. Power up the drive. 2. Enable the communication between the adapter module and the drive with parameter 50.01 fba enable. 3. With parameter 50.02 comm loss func, select how the drive reacts to a fieldbus co...

  • Page 280: Profile With Ppo Type 4

    280 profinet io – start-up 7. Define the process data transferred to and from the drive in parameter groups 52 and 53. Note: the adapter module automatically sets the communication profile-specific virtual address for the status word in parameter 52.01 and for the control word in parameter 53.01. 8....

  • Page 281

    Profinet io – start-up 281 the table below gives the recommended drive parameter settings. Drive parameter setting for acs850/acq810 drives description 50.01 fba enable enable enables communication between the drive and the fieldbus adapter module. 50.02 comm loss func fault 2) enables fieldbus comm...

  • Page 282

    282 profinet io – start-up the start sequence for the parameter example above is given below. Control word: • reset the fieldbus communication fault (if active). • enter 47eh (1150 decimal) –> ready to switch on. • enter 47fh (1151 decimal) –> operating (speed mode). 21.01 speed ref1 sel (acs850) 21...

  • Page 283: And Acs580 Drives

    Profinet io – start-up 283 starting up fieldbus communication for acs880 and acs580 drives 1. Power up the drive. 2. Enable the communication between the adapter module and the drive by selecting the correct slot number in parameter 50.01 fba a enable. The selection must correspond to the slot where...

  • Page 284: Profile With Ppo Type 4

    284 profinet io – start-up 7. Define the process data transferred to and from the drive in parameter groups 52 and 53. Note: the adapter module automatically sets the communication profile-specific virtual address for the status word in parameter 52.01 and for the control word in parameter 53.01. 8....

  • Page 285

    Profinet io – start-up 285 the table below gives the recommended drive parameter settings. Drive parameter setting for acs880 drives description 50.01 fba a enable 1 = option slot 1 2) enables communication between the drive and the fieldbus adapter module. 50.04 fba a ref1 type 4 = speed selects th...

  • Page 286: Parameter Setting Examples

    286 profinet io – start-up the start sequence for the parameter example above is given below. Control word: • reset the fieldbus communication fault (if active). • enter 47eh (1150 decimal) –> ready to switch on. • enter 47fh (1151 decimal) –> operating (speed mode). Parameter setting examples – acs...

  • Page 287

    Profinet io – start-up 287 the table below gives the recommended drive parameter settings. Drive parameter setting for acs580 drives description 50.01 fba a enable 1 = option slot 1 2) enables communication between the drive and the fieldbus adapter module. 50.04 fba a ref1 type 0 = speed or frequen...

  • Page 288

    288 profinet io – start-up the start sequence for the parameter example above is given below. Control word: • reset the fieldbus communication fault (if active). • enter 47eh (1150 decimal) –> ready to switch on. • enter 47fh (1151 decimal) –> operating (scalar motor control mode). 20.01 ext1 comman...

  • Page 289: Downloading The Gsd File

    Profinet io – start-up 289 configuring the master station after the adapter module has been initialized by the drive, you must prepare the master station for communication with the module. Examples of an abb ac500 plc and siemens simatic s7 plc are given below. If you are using another master system...

  • Page 290

    290 profinet io – start-up 3. In the window that opens, click install... And browse for the gsd file. 4. Open or create the plc project that is used to control the drive. 5. Add the cm579-pnio profinet master device to the plc project, if necessary. 6. Add the adapter module to the profinet io netwo...

  • Page 291

    Profinet io – start-up 291 8. Define the cm579-pnio master properties, such as the ip address and address settings for slaves. 9. Define the adapter module properties: on the pnio identification tab, select the ip address and subnet mask, and type the station name. Note: use only small letters for t...

  • Page 292: Assign Station Name.

    292 profinet io – start-up 10. Open the plc program. 11. Compile the project and download it to the plc. This is necessary for you to be able to configure the cm579- pnio master device and allow it to scan the network. 12. Return to the cm579-pnio master properties. On the assign station name tab, d...

  • Page 293

    Profinet io – start-up 293 13. Define the i/o module properties: • on the pnio parameters tab, configure the stop mode and control-zero mode functionalities, and define fail safe values for the plc output process data (pzds). • on the pnio module i/o mapping tab, type names for the variables that re...

  • Page 294

    294 profinet io – start-up 14. Open the plc program and create a program that controls the drive. 15. Compile the project and download it to the plc. Note: make sure that the variable names defined for the drive's signals are used in the plc program. Otherwise the communication will not work..

  • Page 295

    Profinet io – start-up 295 configuring a siemens simatic s7 plc this example shows how to configure communication between a siemens simatic s7 plc and the adapter module using simatic manager step 7. Before you start, make sure that you have downloaded the fena gsd file from the document library. 1....

  • Page 296

    296 profinet io – start-up 3. Install the fena gsd file: • on the options menu, select install gsd files. • browse for the gsd file downloaded from the document library and click install..

  • Page 297

    Profinet io – start-up 297 4. Click and drag the fena object from the device catalog to the ethernet (1): profinet-io-system..

  • Page 298

    298 profinet io – start-up 5. Click and drag the pp0 type 7 object to slot 1. Then, double-click fena to open the properties window..

  • Page 299: Device Name Box.

    Profinet io – start-up 299 6. On the general tab, type a name for the adapter module in the device name box. This is the ip address that will be assigned to the adapter module. You can modify the ip address by clicking the ethernet button. The ip address will be assigned by the io controller..

  • Page 300

    300 profinet io – start-up 7. In the hardware configuration, double-click ppo type 7 in slot 1 to open the properties window. 8. On the parameters tab, configure the stop mode and control- zero mode functionality, and define fail safe values for the plc output process data (pzds)..

  • Page 301: Assign Device Name.

    Profinet io – start-up 301 9. Assign the device name (defined in step 6) to the adapter module: • in the hardware configuration, click fena. • on the plc menu, select ethernet, and then select assign device name..

  • Page 302: Name.

    302 profinet io – start-up • click the available device with the correct mac address to which the device name is to be assigned. This will assign the name to the fena adapter module. Then click assign name..

  • Page 303

    Profinet io – start-up 303 10. Download the hardware configuration to the plc. The plc is now ready for communication with the adapter module..

  • Page 304

    304 profinet io – start-up.

  • Page 305: Profinet Io –

    Profinet io – communication profiles 305 15 profinet io – communication profiles contents of this chapter this chapter describes the communication profiles used in the communication between the profinet io master, the adapter module and the drive. Communication profiles communication profiles are wa...

  • Page 306

    306 profinet io – communication profiles the figure below illustrates the profile selection: the following sections describe the control word, the status word, references and actual values for the profidrive and abb drives communication profiles. Refer to the drive manuals for details on the native ...

  • Page 307: Control Word Contents

    Profinet io – communication profiles 307 profidrive communication profile control word and status word the control word (profidrive parameter 967) is the principal means for controlling the drive from a fieldbus system. It is sent by the fieldbus master station to the drive through the adapter modul...

  • Page 308

    308 profinet io – communication profiles 2 off3 1 continue operation (off3 inactive). 0 emergency stop, stop according to fastest possible deceleration mode. Proceed to off3 active; proceed further to switch-on inhibit. Warning: ensure motor and driven machine can be stopped using this stop mode. 3 ...

  • Page 309

    Profinet io – communication profiles 309 6 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. Activate traversing task (0 –> 1). This is a toggle bit; each rising edge of signal enables a trav...

  • Page 310: Status Word Contents

    310 profinet io – communication profiles status word contents the table below shows the contents of the status word for the profidrive communication profile (profidrive parameter 968). The upper case boldface text refers to the states shown in the state machine on page 312 . 15 vendor-specific bit a...

  • Page 311

    Profinet io – communication profiles 311 8 at_setpoint 1 operating. Actual value equals reference value (= is within tolerance limits). 0 actual value differs from reference value (= is outside tolerance limits). 9 remote 1 drive control location: remote 0 drive control location: local 10 1 actual f...

  • Page 312

    312 profinet io – communication profiles state machine for all operating modes the general profidrive state machine for all operating modes is shown below. ‘n=0 or f =0’ and ‘i=0’ and pause expired jogging 1 or 2 off (cw bit8=0 or bit9=0) mains off power on off1 (cw bit0=0) switch-on inhibit (sw bit...

  • Page 313

    Profinet io – communication profiles 313 state machine for the positioning mode the profidrive state machine for the positioning mode is shown below. State condition e f (sw bit10,13=1) (cw bit4,5=1 and cw bit6 edge 0 1) cw= control word sw = status word profidrive state machine for profidrive posi...

  • Page 314: References

    314 profinet io – communication profiles references abb drives can receive control information from multiple sources including analog and digital inputs, the drive control panel and a fieldbus adapter module (for example, fena). To have the drive controlled through profinet, you must select the modu...

  • Page 315: Actual Values

    Profinet io – communication profiles 315 actual values actual values are 16-bit or 32-bit words containing information on the operation of the drive. The functions to be monitored are selected with a drive parameter. Actual values in speed control mode the scaling of 16-bit actual speed values (act ...

  • Page 316: Control Word Contents

    316 profinet io – communication profiles abb drives communication profile control word and status word the control word is the principal means for controlling the drive from a fieldbus system. It is sent by the fieldbus master station to the drive through the adapter module. The drive switches betwe...

  • Page 317

    Profinet io – communication profiles 317 3 inhibit_ operation 1 proceed to operation enabled. Note: run enable signal must be active; see drive documentation. If the drive is set to receive the run enable signal from the fieldbus, this bit activates the signal. 0 inhibit operation. Proceed to operat...

  • Page 318: Status Word Contents

    318 profinet io – communication profiles 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 on page 320 . 10 remote_ cmd 1 fieldbus control enabled 0 control word and reference n...

  • Page 319

    Profinet io – communication profiles 319 7 alarm 1 warning/alarm 0 no warning/alarm 8 at_setpoint 1 operation. Actual value equals reference (= is within tolerance limits, ie, in speed control, speed error is 10% max. Of nominal motor speed). 0 actual value differs from reference (= is outside toler...

  • Page 320: State Machine

    320 profinet io – communication profiles state machine the state machine for the abb drives communication profile is shown below. Power on (cw bit0=0) (sw bit6=1) (sw bit0=0) from any state (cw=xxxx x1xx xxxx x110) (sw bit1=1) n(f)=0 / i=0 (sw bit2=0) a b c d (cw bit3=0) operation inhibited off1 (cw...

  • Page 321: References

    Profinet io – communication profiles 321 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. Abb drives can receive...

  • Page 322: Actual Values

    322 profinet io – communication profiles actual values actual values are 16-bit words containing information on the operation of the drive. The functions to be monitored are selected with a drive parameter. Scaling actual values are scaled as shown below. Note: the values of ref1 max and ref2 max ar...

  • Page 323: Profinet Io –

    Profinet io – communication protocol 323 16 profinet io – communication protocol contents of this chapter this chapter describes the profinet io communication protocol for the adapter module. For detailed information on profinet io communication, refer to profinet specification application layer pro...

  • Page 324

    324 profinet io – communication protocol profinet io uses three different communication channels to exchange data: • the standard udp/ip and tcp/ip channel is used for parameterization and configuration of devices and for acyclic operations. • the real time (rt) channel is used for cyclic data trans...

  • Page 325: Profinet Io In Fena

    Profinet io – communication protocol 325 profinet io in fena when profinet io is selected as the communication protocol, the fena adapter module can employ the abb drives, transparent 16 and transparent 32 communication profiles or the profidrive profile. You can select the profile with a gsd file i...

  • Page 326: Cyclic Message Types

    326 profinet io – communication protocol cyclic message types ppo types out area – data sent from master to slave (control data) in area – data sent from slave to master (actual data) parameter identification: id – parameter identification ind – index for arrays value – parameter value (max. 4 bytes...

  • Page 327: Access Mechanism (Dp-V1)

    Profinet io – communication protocol 327 standard telegram (st) types (dp-v1) note: for the contents of the control word, the status word, references and actual values, see chapter profinet io – communication profiles . Parameter handling using acyclic parameter access mechanism (dp-v1) profinet io ...

  • Page 328: Header And Frame Structures

    328 profinet io – communication protocol header and frame structures profinet io uses the dce rpc (distributed computing environment remote procedure call) protocol for acyclic read and write services. I/o controllers and supervisors take care of formulating most of the request frames. However, it i...

  • Page 329: Errorcode1

    Profinet io – communication protocol 329 errorcode1 the table below lists the errorcode1 with pniorw decoding. Error class meaning error code 0…9 (reserved) 10 (0x0a) application 0 = read error 1 = write error 2 = module failure 3…7 = reserved 8 = version conflict 9 = feature not supported 10…15 = u...

  • Page 330

    330 profinet io – communication protocol dp-v1 read/write request sequence a read/write service on a drive parameter is illustrated below. The messaging employs dp-v1 data units. The profidrive parameter request is included within the dp-v1 request as data. Likewise, the dp-v1 response contains the ...

  • Page 331: Read And Write Blocks

    Profinet io – communication protocol 331 read and write blocks a read block is used in read requests and responses, while a write block is used in write requests and responses. A request consists of unique identifiers for the connection, addressing information and the length of the record data. A re...

  • Page 332: Data Block

    332 profinet io – communication protocol data block the data block contains a profidrive-specific request or response header. The table below shows the contents of the profidrive request. Additional value 1 (response only) field for transferring additional data ui16 additional value 2 (response only...

  • Page 333

    Profinet io – communication protocol 333 parameter index address of the parameter that is being accessed. “0” is allowed by fena. 1…65535 word subindex addresses • the first array element of the parameter or • the beginning of a string access or • the text array or • the description element that is ...

  • Page 334

    334 profinet io – communication protocol the table below shows the contents of the profidrive response. Field(s) description range request reference (mirrored) mirrored from the request. 1…255 response id response from the slave. In case any requested services fail, a “not acknowledged” (nak) respon...

  • Page 335

    Profinet io – communication protocol 335 the table below shows the data types for the format field in the profidrive response. Code type 0x00 (reserved) 0x01…0x36 standard data types 1 boolean (not supported) 2 integer8 (not supported) 3 integer16 4 integer32 5 unsigned8 (not supported) 6 unsigned16...

  • Page 336

    336 profinet io – communication protocol the table below shows the profidrive parameter request error codes . Error # meaning used at 00h impermissible parameter number access to an unavailable parameter 01h parameter value cannot be changed change access to a parameter value that cannot be changed ...

  • Page 337

    Profinet io – communication protocol 337 16h parameter address impermissible illegal value or value that is not supported for the attribute, number of elements, parameter number or sub-index, or a combination 17h illegal format write request: illegal format or format of parameter data that is not su...

  • Page 338: (Siemens S7)

    338 profinet io – communication protocol function blocks for sending dp-v1 messages (siemens s7) in iec 61131-3 compatible systems, function blocks are available for accessing data non-cyclically. In siemens s7, sfb 52 "rdrec" can be used for reading and sfb53 "wrrec" for writing data records as fol...

  • Page 339: Element)

    Profinet io – communication protocol 339 parameter data transfer examples the following examples show how parameter data is transferred using the dp-v1 mechanisms read and write. Note: only the data block part of the request is presented in the examples. See section read and write blocks on page 331...

  • Page 340

    340 profinet io – communication protocol • positive read response to dp-v1 read request: • negative response to profidrive read request: dp header 01 01 b0 2f 08 05 01 01 01 42 01 05 64 dp trailer dp-v1 response profidrive v3 parameter channel dp header 01 01 b0 2f 08 05 01 01 01 42 01 05 64 dp trai...

  • Page 341: (Multi-Parameter)

    Profinet io – communication protocol 341 example 1b: reading 3 drive parameters (multi-parameter) in this example, three parameters (12.04, 20.08 and 30.19) are read using one telegram. • dp-v1 write request (read parameter value): dp header 01 01 b0 2f 16 06 01 01 03 10 01 00 0c 00 04 ••• dp-v1 com...

  • Page 342

    342 profinet io – communication protocol • positive read response to dp-v1 read request: the values 190h (400), 1f4h (500) and 1eh (30) are returned. Dp header 01 01 b0 2f 10 06 01 01 03 42 01 01 90 ••• dp-v1 response profidrive v3 parameter channel ••• 42 01 01 f4 ••• (par. Channel cont’d) ••• 42 0...

  • Page 343: Element)

    Profinet io – communication protocol 343 example 2a: writing a drive parameter (one array element) drive parameters are addressed so that the drive parameter group corresponds to the parameter index (pnu), and the drive parameter number within that group corresponds to the subindex (ind). In the fol...

  • Page 344

    344 profinet io – communication protocol dp header 01 01 b0 2f 04 07 02 01 01 dp trailer dp-v1 response profidrive v3 parameter channel slot number slot number index data length request reference (mirrored) response id drive object id (mirrored) number of parameters.

  • Page 345: (Multi-Parameter)

    Profinet io – communication protocol 345 example 2b: writing 2 drive parameters (multi-parameter) in this example, the values 300 (12ch) and 500 (1f4h) are written to drive parameters 12.02 (0c.02h) and 20.08 (14.08h) respectively using one telegram. Dp header 01 01 b0 2f 14 08 02 01 02 10 01 00 0c ...

  • Page 346

    346 profinet io – communication protocol dp header 01 01 b0 2f 04 08 02 01 02 dp trailer dp-v1 response profidrive v3 parameter channel slot number subslot number index data length request reference (mirrored) response id drive object id (mirrored) number of parameters.

  • Page 347

    Profinet io – communication protocol 347 example 3: reading a profidrive parameter in this example, profidrive parameter 919 (397h) is used to read the device system number of the slave, which is the product code of the drive. • dp-v1 write request (reading a profidrive parameter): • dp-v1 read resp...

  • Page 348

    348 profinet io – communication protocol example 4: configuring the process data written to the drive profidrive parameter 915 (393h) can be used to define which data is written cyclically to a drive parameter as application-specific process data. In the example below, the value of drive parameter 1...

  • Page 349

    Profinet io – communication protocol 349 • dp-v1 read response: subsequently, the contents of pzd3 in each request frame are written to drive parameter 12.06 until a different selection is made. Dp header 01 01 b0 2f 08 0a 01 01 01 42 01 00 68 dp trailer dp-v1 response profidrive v3 parameter channe...

  • Page 350: From The Drive

    350 profinet io – communication protocol example 5: determining the source of the process data read from the drive profidrive parameter 916 (394h) can be used to define which data is read cyclically from the drive as application-specific process data. In the example below, the parameter is used to d...

  • Page 351

    Profinet io – communication protocol 351 • dp-v1 read response: value indicates the source of pzd3 as drive parameter 12.05 (0c.05h). Diagnostic and alarm mechanism the fena adapter module has mechanisms for sending alarms and saving diagnostics data to a fault buffer. An alarm is triggered if the h...

  • Page 352: Alarm Mechanism

    352 profinet io – communication protocol alarm mechanism when a fault situation occurs, the adapter module sends an alarm notification, which the master station has to acknowledge. Alarm notifications can be acknowledged, viewed and handled, for example, with siemens s7 blocks ob82, ob83, ob86 and o...

  • Page 353

    Profinet io – communication protocol 353 0x9004 power electronics 2211, 2281, 2310, 2312, 2340, 2381, 3180, 3181, 3182, 3183, 3184, 3185, 3186, 3187, 3381, 3385, 5400, 5482, 5682, 5692, ff56 0x9005 overtemperature electronic device 4110, 4210, 4212, 4290, 4310, 4313, 4981, 7182, 42f1, 4380 0x9006 ea...

  • Page 354: Fault Buffer Mechanism

    354 profinet io – communication protocol fault buffer mechanism the profidrive profile has a mechanism that can store eight fault situations to profidrive parameters. Fault and diagnostic data, like fault number and fault code, can be accessed simultaneously with only one subindex. The mechanism con...

  • Page 355

    Profinet io – communication protocol 355 the table below illustrates the structure of a fault buffer. The fault buffer consists of two parameters: fault number (pnu 947) and fault code (pnu 945). The rows of the fault buffer are represented by the parameter subindices. Fault messages are entered int...

  • Page 356

    356 profinet io – communication protocol fault situation n-7 0 0 56 0 0 57 0 0 58 0 0 59 0 0 60 0 0 61 0 0 62 0 0 63 pnu947 pnu945 fault number fault code subindex.

  • Page 357: Profinet Io – Diagnostics

    Profinet io – diagnostics 357 17 profinet io – diagnostics contents of this chapter this chapter explains how to trace faults with the status leds on the adapter module when the module is used for profinet io communication. Fault and warning messages for the fault and warning messages concerning the...

  • Page 358: Leds

    358 profinet io – diagnostics leds the adapter module is equipped with three bicolor diagnostic leds. The leds are described below. Name color function host blinking green establishing communication to host green connection to host ok blinking red communication to host lost temporarily flashing oran...

  • Page 359

    Profinet io – diagnostics 359 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. This may be caused by the adapte...

  • Page 360

    360 profinet io – diagnostics network /net off device is not on-line. • the device has not completed the duplicate address detection yet. • the device may not be powered; look at the module status led. Flashing green device is receiving/transmitting on the ethernet. Name color function.

  • Page 361: Technical Data

    Technical data 361 18 technical data contents of this chapter this chapter contains the technical specifications of the adapter module and the ethernet link. Fena-01/-11/-21 the figure below shows the enclosure of the adapter module from the front and side..

  • Page 362: Ethernet Link

    362 technical data ethernet link installation into an option slot on the drive control unit degree of protection ip20 ambient conditions the applicable ambient conditions specified for the drive in its manuals are in effect. Package cardboard. Plastic wrapping: antistatic air bubble sheet (pe). Indi...

  • Page 363: Appendix A – Profidrive

    Appendix a – profidrive parameters and i&m records of profinet io 19 appendix a – profidrive parameters and i&m records of profinet io contents of this chapter this chapter contains: • profidrive parameters of the profinet io communication protocol • telegram and response structures for the i&m (ide...

  • Page 364: Profidrive Parameters

    364 appendix a – profidrive parameters and i&m records of profinet io profidrive parameters par. No. R/w 1) data type description 915 r/w array [12] unsigned16 assignment pzd1 to pzd12 in ppo- write 916 r/w array [12] unsigned16 assignment pzd1 to pzd12 in ppo- read 919 r octet string4 device system...

  • Page 365

    Appendix a – profidrive parameters and i&m records of profinet io 32 – traversing block selection (satzanw) (not supported) unsigned16 33 – actual traversing block (aktsatz) (not supported) unsigned16 34 – target position (tarpos_a) (not supported) signed32 35 – velocity (velocity_a) unsigned32 101…...

  • Page 366

    366 appendix a – profidrive parameters and i&m records of profinet io 929 r unsigned16 selected ppo type value ppo type 1 ppo1 2 ppo2 3 ppo3 4 ppo4 5 ppo5 6 ppo6 7 ppo7 note: this parameter is not available if standard telegram st1 or st2 is selected. 930 r/w unsigned16 selection switch for communic...

  • Page 367

    Appendix a – profidrive parameters and i&m records of profinet io 936 r/w unsigned16 selection switch for control word, bit 14. (see parameter 933 for coding.) 937 r/w unsigned16 selection switch for control word, bit 15. (see parameter 933 for coding.) 939 r/w unsigned16 selection switch for status...

  • Page 368

    368 appendix a – profidrive parameters and i&m records of profinet io 946 r array [n] unsigned16 fault code list. Contains the mapping between drivecom fault codes and channel error types. If you use a drivecom fault code as an index when reading pnu946, the corresponding channel error type is retur...

  • Page 369

    Appendix a – profidrive parameters and i&m records of profinet io 970 r/w unsigned16 load parameter record value description 0 no action 1 restore factory settings the parameter must do a zero-to-one transition and the motor must be stopped. 971 r/w unsigned16 save parameter record value description...

  • Page 370

    370 appendix a – profidrive parameters and i&m records of profinet io 1000 r/w unsigned16 map 16-bit selection 3) . Used to request the data type for mapped parameters if mapping is done with parameter 915 or 916. Value description 1 use 16-bit mapping, if available. 50000 r/w unsigned16 disable ala...

  • Page 371: I&m Records

    Appendix a – profidrive parameters and i&m records of profinet io i&m records i&m (identification & maintenance) records can be read, for example, with the dtm tool. The fena adapter module supports the mandatory i&m0 record as well as the optional i&m1, i&m2, i&m3 and i&m4 records. Call-req-pdu tel...

  • Page 372

    372 appendix a – profidrive parameters and i&m records of profinet io response structure for i&m0 (read-only) response structure for i&m1 (read/write) contents size coding header 10 octets – i&m block manufacturer_id 2 octets 0x1a = abb automation order_id 20 octets for instance, “68469422” for fena...

  • Page 373

    Appendix a – profidrive parameters and i&m records of profinet io response structure for i&m2 (read/write) note: i&m1, i&m2 and i&m3 are blank (0x20) by default. Response structure for i&m3 (read/write) response structure for i&m4 (read/write) note: i&m4 is filled with zeros (0x0) by default. Conten...

  • Page 374

    374 appendix a – profidrive parameters and i&m records of profinet io.

  • Page 375: Appendix B – Abb Ip

    Appendix b – abb ip configuration tool for fena 375 20 appendix b – abb ip configuration tool for fena contents of this chapter this chapter shows how to use the abb ip configuration tool to: • find configured and unconfigured fena adapter modules in the network • rewrite the ip configuration of the...

  • Page 376

    376 appendix b – abb ip configuration tool for fena finding adapter modules in the network 1. Open the abb ip configuration tool. 2. Click the scan button. The fena adapter modules present in the network appear on the results list..

  • Page 377: Modules

    Appendix b – abb ip configuration tool for fena 377 rewriting the ip configuration of adapter modules 1. Scan the network for adapter modules. For instructions, see section finding adapter modules in the network on page 376 . 2. On the results list, click to select the adapter module whose ip config...

  • Page 378

    378 appendix b – abb ip configuration tool for fena 5. To apply the new settings, click the send configuration button. The new current ip address and configured ip address appear on the results list..

  • Page 379: Appendix C – Fena

    Appendix c – fena configuration web pages 379 21 appendix c – fena configuration web pages contents of this chapter this chapter presents the fena configuration web pages. Browser requirements any web browser can be used. Compatibility the web pages work with all drives compatible with the fena adap...

  • Page 380: Logging In

    380 appendix c – fena configuration web pages logging in 1. Open a web browser and type the ip address of the adapter module in the address field. Example: http://192.168.0.24/ 2. Log in with a user name and a password. Default user name: admin. Password: the last six digits of the mac id of the ada...

  • Page 381: Menu Overview

    Appendix c – fena configuration web pages 381 menu overview to navigate on the web pages, use the menu items available: • status • configuration • support • password (only visible when support is clicked)..

  • Page 382: Status Page

    382 appendix c – fena configuration web pages status page the status page shows various version information, as well as the serial number and mac address (mac id) of the adapter module..

  • Page 383: Configuration Page

    Appendix c – fena configuration web pages 383 configuration page on the configuration page, you can modify parameter settings in the configuration parameter groups a (1), b (2) and c (3)..

  • Page 384

    384 appendix c – fena configuration web pages after you have changed any setting in any of the groups, you have to click save and reboot at the bottom of group a to validate the settings..

  • Page 385: Support Page

    Appendix c – fena configuration web pages 385 support page on the support page, you can access documentation related to the adapter module, and the eds and gsdml files. The latest files corresponding to the drive firmware are available through the hyperlinks given below www documentation and downloa...

  • Page 386: Password Page

    386 appendix c – fena configuration web pages password page the password menu item becomes visible only after you have clicked the support menu item..

  • Page 387

    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/searchcha...

  • Page 388: Www.Abb.Com/drives

    Abb oy ac drives abb inc. Automation technologies abb beijing drive systems co. Ltd no 1 block d a-10 jiuxianqiao b contact us www.Abb.Com/drives www.Abb.Com/solar www.Abb.Com/windpower www.Abb.Com/drivespartners 3aua0000093568 rev b (en) 2014-01-29.