schneider VW3 A3 309 User Guide

Altivar 61/71

DeviceNet™ card

User’s manual

VW3 A3 309

11/2010

1755877

www.schneider-electric.com

While every precaution has been taken in the preparation of this document, Schneider Electric SA assumes no liability for any omissions or errors it may contai n, nor for any damages resulting from the application or use of the information herein.

The products described in this document may be changed or modified at any time, either from a technical point of view or in the way they are operated. Their de scription can in no way be considered contractual.

Before you begin_____________________________________________________________________________________________ 3 Documentation structure_______________________________________________________________________________________ 4 Introduction_________________________________________________________________________________________________ 5

Presentation _____________________________________________________________________________________________ 5

Notation ______________________________________________ __________________________________________________ 5 Quick start__________________________________________________________________________________________________ 6 Hardware setup _____________________________________________________________________________________________ 7

Receipt _________________________________________________________________________________________________ 7

Hardware description ______________________________________________________________________________________ 7

Installing the card in the drive________________________________________________________________________________ 7

Coding the switches _______________________________________________________________________________________ 8 Wiring to the network ___________________________________________ _____________________________________________ 10

Cable routing practices____________________________________________________________________________________ 10

Wiring the DeviceNet connector_____________________________________________________________ ________________ 10 Configuring by the drive HMI __________________________________________________________________________________ 12

Configuring the control ____________________________________________________________________________________ 12

Configuring the communication scanner ______________________________________________________________________ 17

Configuring the fault management __________________________________ _________________________________________ 19

Configuring monitored parameters___________________________________________________________________________ 20 Configuring by a network tool__________________________________________________________________________________ 21

Network tool ________________________________________________________________________________ ____________ 21

Going online with RSNetWorx ______________________________________________________________________________ 21

Creating an EDS file______________________________________________________________________________________ 21

Configuring the DeviceNet scanner __________________________________________________________________________ 22

Editing parameters of the drive______________________________________________________________________________ 27

Editing objects of the drive _________________________________________________________________________________ 32 Creating a PLC program______________________________________________________________________________________ 35

Using I/O messaging _____________________________________________________________________________________ 35

Using explicit messaging __________________________________________________________________________________ 35 Diagnostics by the drive HMI __________________________________________________________________________________ 36

Checking the node address and the data rate __________________________________________________________________ 36

Signalling LED __________________________________________________________________________________________ 37

Monitoring the control______________________________________________________________________________ _______ 38

Monitoring the communication scanner _______________________________________________________________________ 39

Troubleshooting the communication fault______________________________________________________________________ 40

Troubleshooting the card fault ______________________________________________________________________________ 41 DeviceNet objects___________________________________________________________________________________________ 42

Supported classes _______________________________________________________________________________________ 42

Identity object ___________________________________________________________________________________________ 43

Message router object ____________________________________________________________________________________ 46

DeviceNet object_________________________________________________________________________________________ 47

Assembly object _________________________________________________________________________________________ 49

Connection object________________________________________________________________________________________ 60

Motor data object ________________________________________________________________________________________ 64

Control supervisor object _________________________________________ _________________________________________ 65

AC/DC Drive Object ____________________________ __________________________________________________________ 67

Acknowledge handler object________________________________________________________________________________ 68

Application objects _______________________________________________________________________________________ 69

DeviceNet interface object _________________________________________________________________________________ 70

2 1755877 11/2010

1. Before you begin

Read and understand these instructions before performing any procedure with thi s drive.

DANGER

HAZARDOUS VOLTAGE

• Read and understand the Installation Ma nual before inst alling or op erating the Al tivar 71 drive. Installati on, adjustme nt, repair, and maintenance must be performed by qualified personnel.

• The user is responsible for compliance with all international and national electrical standards in force concerning protective grounding of all equipment.

• Many parts of this variable speed drive, including the printe d circuit cards, operate at the line voltage. DO NOT TOUCH. Use only electrically insulated tools.

• DO NOT touch unshielded components or terminal strip screw connections with voltage prese nt.

• DO NOT short across terminals PA and PC or across the DC bus capacitors.

• Install and close all the covers before applying power or starting and stopping the drive.

• Before servicing the variable speed drive

- Disconnect all power.

- Place a “DO NOT TURN ON” label on the variable speed drive disconnect.

- Lock the disconnect in the open position.

• Disconnect all power including external control power that may be present before servicing the drive. WAIT 15 MINUTES to allow the DC bus capacitors to discharge. Then follow the DC bus voltage measurement procedure given in the Installation Manual to verif y that t he DC vol tage is l ess than 45 VDC. Th e drive LEDs are not accurate indic ators of the absence of DC bus voltage.

Electric shock will result in death or serious injury.

CAUTION

DAMAGED EQUIPMENT

Do not install or operate any drive that appears damaged.

Failure to follow this instruction can result in equipment damage.

1755877 11/2010 3

2. Documentation structure

The following Altivar 61/71 technical documents are available on the Web site www.schneider-electric.com.

b Installation manual

This manual describes:

• How to assemble the drive

• How to connect the drive

b Programming manual

This manual describes:

• The functions

• The parameters

• How to use the drive HMI (integrated HMI and graphic HMI)

b Communication parameters manual

This manual describes:

• The drive parameters with specific information (addresses, formats, etc.) for use via a bus or communication network

• The operating modes specific to communication (state chart)

• The interaction between communication and local control

b Modbus, CANopen®, Ethernet™, Profibus, INTERBUS, Uni-Telway, DeviceNet™, Modbus Plus, Fipio, etc., manuals

These manuals describe:

• Connection to the bus or network

• Configuration of the communication-specific parameters via the integrated HMI or the graphic HMI

• Diagnostics

• Software setup

• The communication services specific to the protocol

b Altivar 58/58F migration manual

This manual describes the differences between the Altivar 71 and the Altivar 58/58F. It explains how to replace an Altivar 58 or 58F, including how to replace drives communicating on a bus or network.

4 1755877 11/2010

3. Introduction

3. 1. Presentation

The DeviceNet communication card (catalog number VW3 A3 309) is used to connect an Altivar 61/71 drive to a DeviceNet network. The communication card has an open-style 5-pin connector for connection to the network. Data exchanges give access to all Altivar 61/71 functions:

• Downloading configuration and adjustment parameters,

• Command,

• Monitoring,

• Diagnostics. DeviceNet cables and connecting accessories must be ordered separately. The graphic display terminal or the integrated display terminal can be used to access numerous functions for communication diagnostics.

Note: All features regarding torque control are not available for ATV61 drives.

3. 2. Notation

Drive terminal displays

The graphic display terminal menus are shown in square brackets. Example: [1.9 COMMUNICATION].

The integrated 7-segment display terminal menus are shown in round brackets. Example: (COM-).

Parameter names are displayed on the graphic display terminal in square brackets. Example: [Fallback speed]

Parameter codes are displayed on the integrated 7-segment display terminal in round brackets. Example: (LFF).

Formats

Hexadecimal values are written as follows: 16# Binary values are written as follows: 2#

Vocabulary

Depending on DeviceNet document and tools, equivalent wordings are used. The table below shows vocabulary used in the present document and other corresponding definitions.

In this document Other Comments

Node address DeviceNet address, MAC ID Data rate Baud rate kbit/s kBPS, kbps, k Setpoint Reference, target Path Object Address Class, instance, attribute

The reader should avoid mixing two terms:

- DeviceNet scanner, which is the master device on the DeviceNet network.

- Communication scanner, which is a function inside the Altivar drive.

Abbreviations

Req. = Required Opt. = Optional

1755877 11/2010 5

4. Quick start

This section is provided to help experienced users quickly start using the DeviceNet card. If you are unsure how to complete a step, refer to the referenced chapter.

Step Refer to 1 Review the safety precautions for the Altivar drive and DeviceNet card. Installation manual 2 Verify that the Altivar drive is properly installed. Installation manual 4 Install the DeviceNet card in the drive.

Verify that the Altivar drive is not powered. Then, dismount the drive cover, mount the card in the drive. Finally mount the cover.

4 Commission the DeviceNet card.

Verify that the Altivar drive is not powered. Set a unique node address and the appropriate data rate using the switches on the card. If desired, you can disable the switches and use parameter settings instead.

5 Connect the drive to the DeviceNet network.

Verify that the Altivar drive is not powered. Then, connect the card to the network using a DeviceNet cable.

6 Apply power to the drive.

The card receives power from the drive. Apply power to the drive. The status indicator should be green.If it flashes red, there is a problem (refer to 10. 2. Signalling LED

7 Configure the drive for your application.

Select the functions and set the parameters as required by your application.

8 Configure the drive behaviour and I/O interface for DeviceNet by the drive HMI.

Choose the suitable assemblies for your application (refer to 7. 1. Conf iguring the control If assemblies 100 or 101 are used, select the commands assigned to the control word (refer

the Programming manual).

Installation manual

5. Hardware setup

6. Wiring to the network

10. Diagnostics by the drive HMI

Programming manual

Communication parameters manual

7. Configuring by the drive HMI

Set the parameters for the following features as requiredby your application:

 Control and setpoint channels (refer to 7. 1. Configuring the control  If assemblies 100 or 101 are used, input and output assignments

(refer to 7. 2. Configuring the communication scanner

 Behaviour on communication fault (refer to 7. 3. Configuring the fault management  The parameters that you would like to monitor by the drive HMI for diagnostics

(refer to 7. 4. Configuring monitored parameters

9 Apply power to the DeviceNet master and other devices on the network.

Verify that the master and network are instal led and fu nction ing in accordance wi th De viceNe t standards, and then apply power to them.

10 Configure the scanner to communicate with the drive.

Use a network tool such as RSNetWorx for Devi ceNet to configure the scanne r on the network. Make sure to:

 Set up the scan list,  Map the drive data to the scan list,  Save your DeviceNet configuration to the scanner and a file.

11 Configure the drive by the network tool.

Set the parameters for the following features as required by your application:

 If the data rate switches (7 and 8) are set to 1, Node address and data rate,  If you do not use default assemblies (100 or 101), select (and configure) assemblies.

12 Create a PLC program

 Control the drive using I/O (assemblies).  Monitor or configure the drive using Explicit Messages.

DeviceNet master manuals (DeviceNet cable system planning and Installation manual ...)

8. 4. Configuring the DeviceNet scanner

8. 5. Editing parameters of the drive

9. Creating a PLC program

DeviceNet master manuals

6 1755877 11/2010

5. Hardware setup

Open-style 5-pin connector

Configuration switches (data rate and node address)

Bicolour LED

5. 1. Receipt

• Check that the card reference printed on the label is the same as that on the delivery note corresponding to the purchase order.

• Remove the option card from its packaging and check that it has not been damag ed in transit.

5. 2. Hardware description

5. 3. Installing the card in the drive

Refer to the Installation manual.

1755877 11/2010 7

5. Hardware setup

Data

rate

Node

address

hight = OFF = 0 low = ON = 1

5. 4. Coding the switches

b Switches description

b Overriding the switches

When switches 7 and 8 are set in position low (ON = 1), the d ata rate and the no de address of the dri ve must be set b y a network tool (refer to 8. Configuring by a network tool). Default values are 125 kbit/s and node address 63.

b Coding the data rate

All devices connected to the DeviceNet network must communicate at the same data rate: 125, 250, or 500 kbit/s. The table below shows the switch settings that configure the DeviceNet data rate on the drive.

Switch 7 Switch 8 Data rate

0 0 125 kbit/s 0 1 250 kbit/s 1 0 500 kbit/s 1 1 The DeviceNet data rate and the node address of the drive must be set by a net work tool.

Any change to the switch setting takes effect at the next power-up.

b Coding the node address

All devices connected to the DeviceNet network must have a unique address, ranging from 0 to 63 (decimal). If the data rate swithes (7 and 8) are both set to 1 (on), the switches 1 to 6 are i gnored an d the nod e address must be set by a network tool

(default value = 63). The table below lists the switch setting for each valid node address.

Any change to the switch setting takes effect at the next power-up.

Node

address

00 00 0000 16 01 0000 32 10 0000 48 11 0000 01 00 0001 17 01 0001 33 10 0001 49 11 0001 02 00 0010 18 01 0010 34 10 0010 50 11 0010 03 00 0011 19 01 0011 35 10 0011 51 11 0011 04 00 0100 20 01 0100 36 10 0100 52 11 0100 05 00 0101 21 01 0101 37 10 0101 53 11 0101 06 00 0110 22 01 0110 38 10 0110 54 11 0110 07 00 0111 23 01 0111 39 10 0111 55 11 0111 08 00 1000 24 01 1000 40 10 1000 56 11 1000 09 00 1001 25 01 1001 41 10 1001 57 11 1001

10 00 1010 26 01 1010 42 10 1010 58 11 1010 11 00 1011 27 01 1011 43 10 1011 59 11 1011 12 00 1100 28 01 1100 44 10 1100 60 11 1100 13 00 1101 29 01 1101 45 10 1101 61 11 1101 14 00 1110 30 01 1110 46 10 1110 62 11 1110 15 00 1111 31 01 1111 47 10 1111 63 11 1111

Switches

12 3456

Node

address

Switches

12 3456

Node

address

Switches

12 3456

Node

address

Switches

12 3456

8 1755877 11/2010

5. Hardware setup

Data rate = 250 kbit/s (switches 7 and 8 = 2#01) Node address = 25 (switches 1 to 6 = 2#01 1001)

Data rate = 500 kbit/s (switches 7 and 8 = 2#10) Node address = 52 (switches 1 to 6 = 2#11 0100)

b Examples

1755877 11/2010 9

6. Wiring to the network

6. 1. Cable routing practices

When wiring Altivar 61/71 drives to a DeviceNet network, follow all wiring practices required by national and local electrical codes. Also observe the following guidelines:

• Avoid areas of high temperature, moisture, vibration, or other mechanical stress.

• Secure the cable where necessary to prevent its weight and the weight of other cables from pulling or twisting the cable.

• Use cable ducts, raceways, or other structures to protect th e cable. Use these structures for signal wiring paths. They must not contain power wiring.

• Avoid sources of electrical interference th at can induce noise into the cabl e. Use the maximum practicable separat ion from such sources.

When planning cable routing within a building, follow these guidelines:

• Maintain a minimum separation of 1 m from the following equipment :

- air conditioners and large blowers,

- elevators and escalators,

- radios and televisions,

- intercom and security systems,

- fluorescent, incandescent, and neon lighting fixtures.

• Maintain a minimum separation of 3 m from the following equipment :

- line and motor power wiring,

- transformers,

- generators,

- alternators.

When wiring in electrical equipment rooms or large electrical equipment line-ups, observe the following guidelines for cable segregation and separation of circuits:

• Use metallic conduit for drive wiring. Do not run control network and power wiring in the same conduit.

• Separate non-metallic conduits or cable trays used to carry power wiring from metallic conduit carrying low-level control network wiring by at least 300 mm.

• Separate metallic conduits carrying power wiring or low-level control network wiring by at least 80 mm.

• Cross the metallic conduits and non-metallic conduits at right angles whenever power and control network wiring cross.

• Attenuate conducted emissions from the dri ve to the line in some installations to p revent interf erence with telecommunicat ion, radio, and sensitive electronic equipment. Such inst ances may require attenua ting filters. Consu lt the Altivar catalog for selection and appli cation of these filters.

6. 2. Wiring the DeviceNet connector

The figures and the table below show the pin-outs of the card connectors. The removable DeviceNet female connector attaches to the network cable.

1234

DeviceNet card male connector Removable DeviceNet female connector

Pin Name Color

1GND Black 2 CAN_L Blue 3SHIELD Bare 4CAN_H White 5V+ Red

Line termination: If the drive is the first or the last device on the DeviceNet net wo rk, a li ne termi nat or (1 21 removable DeviceNet female connector, between pins 2 and 4 (CAN_L and CAN_H).

10 1755877 11/2010

Ω resistor) must be wired on the

6. Wiring to the network

The ODVA standards (Release 2.0) specify 7 types of cables for use in DeviceNet networks:

• Thick cable

• Thin cable

• Flat cable

• Cable I

• Cable II

• Cable IV

• Cable V

The table below lists main specifications of cables. For more information, refer to the ODVA specifications.

Type of cable Data conductor pair size Power conductor pair size Data impedance

Thick cable 18 AWG 15 AWG 120 Thin cable 24 AWG 22 AWG 120 Flat cable 16 AWG 16 AWG 120 Cable I 24 AWG 22 AWG 120 Cable II 18 AWG 15 AWG 120 Cable IV 18 AWG 16 AWG 120 Cable V 18 AWG 16 AWG 120

Ω +/- 10 % (at 1 MHz) Ω +/- 10 % (at 1 MHz) Ω +/- 10 % (at 500 kHz) Ω +/- 10 % (at 1 MHz) Ω +/- 10 % (at 1 MHz) Ω +/- 10 % (at 500 kHz) Ω +/- 10 % (at 500 kHz)

The maximum permissible length of the network cable depends an the data rate and the type of cable.

Type of cable Data rate

125 kbit/s 250 kbit/s 500 kbit/s

Thick cable 500 m (1640 ft) 250 m (820 ft) 100 m (328 ft) Thin cable 100 m (328 ft) 100 m (328 ft) 100 m (328 ft) Flat cable 420 m (1378 ft) 200 m (656 ft) 75 m (246 ft) Cable I 100 m (328 ft) 100 m (328 ft) 100 m (328 ft) Cable II 500 m (1640 ft) 250 m (820 ft) 100 m (328 ft) Cable IV - - Cable V 420 m (1378 ft) 200 m (656 ft) 75 m (246 ft)

For maximum length of the drops refer to table, whatever type of cable:

Data rate Cu m ulat ive dr op Maximum drop

125 kbit/s 156 m (516 ft) 6 m (20 ft) 250 kbit/s 78 m (256 ft) 6 m (20 ft) 500 kbit/s 39 m (128 ft) 6 m (20 ft)

1755877 11/2010 11

7. Configuring by the drive HMI

7. 1. Configuring the control

b Principle

By the configuration of the control, it is possible to decide from what channel the drive receives its commands and setpoint, either permanently or depending on a switching command.

Numerous configurations are possible. For more information, refer to the Programming manual and Communication parameters manual. The following configurations are some of the possibilities available.

M Control with communication scanner

If the default assemblies (100, 101) are selected, all possibilities of Altivar 61/71 drive are available. It is possible to use all profiles and modes of the drive:

- I/O profile,

- Drivecom profiles with separate or non separate mode.

By the configuration of the communication scanner, it is possible to assign any relevant parameter of the drive to the 4 input and 4 output variables of the assemblies. See the input / output interface with the PLC can be fully customised depending on the application.

The use of the communication scanner is als the best way to interface with a "Controller Inside" card.

M Control according to ODVA AC drive profile

The ODVA AC drive profile is activated when one of the following assembl ies is selected:

• 20: Basic speed control output

• 21: Extended speed control output

• 22: Speed and torque control output

• 23: Extended speed and torque control output

• 70: Basic speed control input

• 71: Extended speed control input

• 72: Speed and torque control input

• 73: Extended speed and torque control input

The advantage of using the ODVA drive profile standard is the interchangeability with other brands. The drive must be configured in the Drivecom profile with separate mode.

The DeviceNet card translates the commands, behaviour and monitoring information from of ODVA profi le (on the network) to the Drivecom profile (in the drive).

M Control according to Allen-Bradley® drive profi le

The Allen-Bradley® Drive profile is activated when one of the following assemblies is selected:

• 103: Allen-Bradley® drive output

• 104: Allen-Bradley® drive input

• 105: Allen-Bradley® drive input with parameters

If you need to replace Allen-Bradley® drives, in an existing application, this profile is a good way to minimise the modifications. The drive must be configured in the Drivecom profile with separate mode.

The DeviceNet card translates the commands, behaviour and monitoring information from of Allen-Bradley® drive profile (on the network) to the Drivecom profile (in the drive).

Note 1: If the DeviceNet communication is active while changing a configuration parameter, it will generate an EPF2 fault. Note 2: When changing (CHCF) [Profile], assemblies are set to their default values.

12 1755877 11/2010

7. Configuring by the drive HMI

b Available configurations

M If you use the communication scanner:

• 100: Communication scanner output

• 101: Communication scanner input there is no limitation in the configuration of the control.

The examples below are only possible if you use the communication scanner.

M If you use the ODVA AC drive profile or Allen-Bradley® Drive profile, that is, the assemblies:

• 20: Basic speed control output

• 21: Extended speed control output

• 22: Speed and torque control output

• 23: Extended speed and torque control output

• 70: Basic speed control input

• 71: Extended speed control input

• 72: Speed and torque control input

• 73: Extended speed and torque control input

• 103: Allen-Bradley® drive output

• 104: Allen-Bradley® drive input

• 105: Allen-Bradley® drive input with parameters only some configurations are permitted, they are listed in the table below.

Parameter Permitted value Comment

Profile Drivecom profile separate The run commands are in Drivecom profile,

Setpoint 1 configuration Network card Setpoint 1 comes from DeviceNet. Setpoint 1B configuration Terminals Setpoint 2 comes from terminals (AI1 or AI2). Setpoint 2 configuration Terminals Setpoint 2 comes from terminals (AI1 or AI2). Command 1 configuration Network card Command 1 comes from DeviceNet. Command 2 configuration Terminals Command 2 comes from terminals. Setpoint switching Network card bit 13 Bit 13 of the control word switches the setpoint (1 <-> 1B or 1 <-> 2). Command switching Network card bit 12 Bit 12 of the control word switches the command.

the command and the reference can come from different channels.

Configuration via the graphic display terminal or the integrated display terminal:

Case 1: Setpoint 1B is connected to the functions (Summing, PID, etc) which remain active even after switching.

Menu Parameter Permitted value

[1.6 - COMMAND] (CtL-) [Profile] (CHCF) [Separate] (SEP)

[Ref.1 channel] (Fr1) [Com. card] (nEt) [Ref.1B channel] (Fr1b) [Ref. AI1] (AI1) or [Ref. AI2] (AI2) [Cmd channel 1] (Cd1) [Com. card] (nEt) [Cmd channel 2] (Cd2) [Terminals] (tEr) [Cmd switching] (CCS) [C312] (C312)

[1.7 APPLICATION FUNCT.] (FUn-) [REFERENCE SWITCH.]

Case 2: Setpoint 2 is directly connected to the drive reference limit. If switching is performed, the functions that affect the reference (summing, PID, etc.) are inhibited.

Menu Parameter Permitted value

[1.6 - COMMAND] (CtL-) [1.7 APPLICATION FUNCT.] (FUn-) [REFERENCE SWITCH.]

Note: It is not possible to configure the display terminal as a channel. To switch to the display terminal, use the function force local and assign the parameter [Forced local Ref.] to [HMI] (LCC).

[Ref 1B switching] (rCb) [C313] (C313)

[Profile] (CHCF) [Separate] (SEP) [Ref.1 channel] (Fr1) [Com. card] (nEt) [Ref.2 channel] (Fr2) [Ref. AI1] (AI1) or [Ref. AI2] (AI2) [Cmd channel 1] (Cd1) [Com. card] (nEt) [Cmd channel 2] (Cd2) [Terminals] (tEr) [Cmd switching] (CCS) [C312] (C312) [Ref. 2 switching] (rFC) [C313] (C313)

1755877 11/2010 13

7. Configuring by the drive HMI

b Control via DeviceNet in I/O profile

Note: This configuration can only be used if the communication scanner assemblies (100 and 101) are selected.

The command and the setpoint come from DeviceNet. Control is in I/O profile.

Configure the following parameters:

Parameter Value Comment

Profile I/O profile The run command is simply obtained by bit 0 of the command word. Setpoint 1 configuration Network card The setpoint comes from DeviceNet. Command 1 configuration Network card The command comes from DeviceNet.

Configuration via the graphic display terminal or the integrated display terminal:

Menu Parameter Value

[1.6 - COMMAND] (CtL-) [Profile] (CHCF) [I/O profile] (IO)

[Ref.1 channel] (Fr1) [Com. card] (nEt) [Cmd channel 1] (Cd1) [Com. opt card] (nEt)

b Control via DeviceNet or via the terminals in I/O profile

Note: This configuration can only be used if the communication scanner assemblies (100 and 101) are selected.

The command and the setpoint both come from DeviceNet or the terminals. Input LI5 at the terminals is used to switch between DeviceNet and the terminals. Control is in I/O profile.

Configure the following parameters:

Parameter Value Comment

Profile I/O profile The run command is simply obtained by bit 0 of the control word. Setpoint 1 configuration Network card Setpoint 1 comes from DeviceNet. Setpoint 1B configuration Analog input 1 on the terminals Setpoint 1B comes from input AI1 on the terminals. Setpoint switching Input LI5 Input LI5 switches the setpoint (1 Command 1 configuration Network card Command 1 comes from DeviceNet. Command 2 configuration Terminals Command 2 comes from the terminals. Command switching Input LI5 Input LI5 switches the command.

Note: Setpoint 1B is connected to the functions (Summing, PID, etc) which remain active even after switching. Configuration via the graphic display terminal or the integrated display terminal:

Menu Parameter Value

[1.6 - COMMAND] (CtL-) [Profile] (CHCF) [I/O profile] (IO)

[Ref.1 chan] (Fr1) [Com. card] (nEt) [Cmd channel 1] (Cd1) [Com. card] (nEt) [Cmd channel 2] (Cd2) [Terminals] (tEr) [Cmd switching] (CCS) [LI5] (LI5)

[1.7 APPLICATION FUNCT.] (FUn-) [REFERENCE SWITCH.]

[Ref.1B chan] (Fr1b) [AI1 ref.] (AI1) [Ref 1B switching] (rCb) [LI5] (LI5)

↔1B).

14 1755877 11/2010

7. Configuring by the drive HMI

b Control via DeviceNet in Drivecom profile

Note: This configuration can only be used if the communication scanner assemblies (100 and 101) are selected.

The command and the setpoint come from DeviceNet. Configure the following parameters:

Parameter Value Comment

Profile Separate Drivecom profile The run commands are in Drivecom profi le, the command and the setpoint can

Setpoint 1 configuration Network card The setpoint comes from DeviceNet. Command 1 configuration Network card Command 1 comes from DeviceNet.

Configuration via the graphic display terminal or the integrated display terminal:

Menu Parameter Value

[1.6 - COMMAND] (CtL-) [Profile] (CH CF) [Separate] (SEP)

[Ref.1 chan] (Fr1) [Com. card] (nEt) [Cmd channel 1] (Cd1) [Com. card] (nEt )

come from different channels.

b Control via DeviceNet or the terminals in Drivecom profile

Note: This configuration can only be used if the communication scanner assemblies (100 and 101) are selected.

The command and the setpoint both come from DeviceNet or the terminals. Input LI5 at the terminals is used to switch between DeviceNet and the terminals.

Configure the following parameters:

Parameter Value Comment

Profile Separate Drivecom profile The run commands are in Drivecom profile, the command and the

Setpoint 1 configuration Network card Setpoint 1 comes from DeviceNet. Setpoint 2 configuration Analog input 1 on the terminals Setpoint 2 comes from input AI1 on the terminals. Setpoint switching Input LI5 Input LI5 switches the setpoint (1 Command 1 configuration Network card Command 1 comes from DeviceNet. Command 2 configuration Terminals Command 2 comes from the terminals. Command switching Input LI5 Input LI5 switches the command.

Note: Setpoint 2 is directly connected to the drive ref erence limit. If switching is performed, the functions that af fect the reference (summing, PID, etc) are inhibited.

Configuration via the graphic display terminal or the integrated display terminal:

Menu Parameter Value

[1.6 - COMMAND] (CtL-) [Profile] (CHCF) [Separate] (SEP)

[Ref.1 chan] (Fr1) [Com. card] (nEt) [Ref.2 chan] (Fr2) [AI1 ref.] (AI1) [Ref. 2 switching] (rFC) [LI5] (LI5) [Cmd channel 1] (Cd1) [Com. card] (nEt) [Cmd channel 2] (Cd2) [Terminals] (tEr) [Cmd switching] (CCS) [LI5] (LI5)

setpoint can come from different channels.

↔ 2) and the command.

1755877 11/2010 15

7. Configuring by the drive HMI

b Control in Drivecom profile via DeviceNet and setpoint switching at the terminals

Note: This configuration can only be used if the communication scanner assemblies (100 and 101) are selected.

The command comes from DeviceNet. The setpoint comes either from DeviceNet or from the terminals. I nput LI5 at the terminals is used to switch the setpoint between DeviceNet and the terminals. Control is in Drivecom profile.

Configure the following parameters:

Parameter Value Comment

Profile Separate Drivecom profile The run commands are in Drivecom profile, the command and the

Setpoint 1 configuration Network card Setpoint 1 comes from DeviceNet. Setpoint 1B configuration Analog input 1 on the terminals Setpoint 1B comes from input AI1 on the terminals. Setpoint switching Input LI5 Input LI5 switches the setpoint (1 Command 1 configuration Network card Command 1 comes from DeviceNet. Command switching Channel 1 Channel 1 is the command channel.

Note: Setpoint 1B is connected to the functions (summing, PID, etc) that remain active, even after switching.

setpoint can come from different channels.

↔1B).

Configuration via the graphic display terminal or the integrated display terminal:

Menu Parameter Value

[1.6 - COMMAND] (CtL-) [Profile] (CHCF) [Separate] (SEP)

[Ref.1 chan] (Fr1) [Com. card] (nEt) [Cmd channel 1] (Cd1) [Com. card] (nEt) [Cmd switching] (CCS) [ch1 active] (Cd1)

[1.7 APPLICATION FUNCT.] (FUn-) [REFERENCE SWITCH.]

[Ref.1B chan] (Fr1b) [AI1 ref.] (AI1) [Ref 1B switching] (rCb) [LI5] (LI5)

16 1755877 11/2010

7. Configuring by the drive HMI

7. 2. Configuring the communication scanner

You need to read this chapter only if you use the assemblies 100 or 101 that use the drive communication scanner. The variables exchanged by the output assembly 100 and input assembly 101 are selected by configuring the communication scanner. The 4 output variables are assigned by means of the 4 parameters [Scan. Outp address] (nCAp). They are configured using the graphic

display terminal via the [1.9 - COMMUNICATION] (COM-) menu, [COM. SCANNER OUTPUT] (OCS-) submenu. The 4 input variables of the assembly 101 are assigned by means of the 4 parameters [Scan. Inp address] (nMAp). They are configured

using the graphic display terminal via the [1.9 - COMMUNICATION] (COM-) menu, [COM. SCANNER INPUT] (ICS-) submenu. Enter the logic address of the parameter (see the Communication parameters manual).

If a parameter [Scan. Outp address] (nCAp) or [S can. Inp address] (nMAp) is equal to zero, the corresponding period variable is not used by the drive.

These 8 assignment parameters are described in the tables below:

Parameter name Output assembly 100 Default assignment

[Scan. Out1 address] (nCA1) Bytes 0 and 1 Control word (CMd) [Scan. Out2 address] (nCA2) Bytes 2 and 3 Speed reference (LFrd) [Scan. Out3 address] (nCA3) Bytes 4 and 5 Not used [Scan. Out4 address] (nCA4) Bytes 6 and 7 Not used

[Scan. Out5 address] (nCA5) to [Scan. Out8 address] (nCA8) are not useful for the DeviceNet card.

Parameter name Input assembly 101 Default assignment

[Scan. In1 address] (nMA1) Bytes 0 and 1 Status word (EtA) [Scan. In2 address] (nMA2) Bytes 2 and 3 Output speed (rFrd) [Scan. In3 address] (nMA3) Bytes 4 and 5 Not used [Scan. In4 address] (nMA4) Bytes 6 and 7 Not used

[Scan. In5 address] (nCA5) to [Scan. In8 address] (nCA8) are not useful for the DeviceNet card.

Example of configuration via the graphic display terminal:

RDY NET +0.00Hz 0A RDY NET +0.00Hz 0A

COM. SCANNER INPUT COM. SCANNER OUTPUT Scan. In1 address : 3201 Scan. Out1 address : 8501 Scan. In2 address : 8604 Scan. Out2 address : 8602 Scan. In3 address : 0 Scan. Out3 address : 0 Scan. In4 address : 0 Scan. Out4 address : 0 Scan. In5 address : 0 Scan. Out5 address : 0

Code Quick Code Quick

Scan. In6 address : 0 Scan. Out6 address : 0 Scan. In7 address : 0 Scan. Out7 address : 0 Scan. In8 address : 0 Scan. Out8 address : 0

Note:

All modifications to parameters [Scan. Outp address] (nCAp) or [Scan. Inp address] (nMAp) must be made with the motor stopp ed. The master PLC program should be updated to take account of this modification.

1755877 11/2010 17

7. Configuring by the drive HMI

Example of configuration of communication scanner assemblies 100 and 101

The following output and input variables are to be configured:

Output assembly 100 Parameter assigned Input assembly 101 Parameter assigned

Bytes 0 and 1 Control word (CMd) Bytes 0 and 1 Status word (EtA) Bytes 2 and 3 Speed reference (LFrd) Bytes 2 and 3 Output speed (rFrd) Bytes 4 and 5 Acceleration (ACC) Bytes 4 and 5 Speed reference before ramp (FrHd) Bytes 6 and 7 Deceleration (dEC) Bytes 6 and 7 Logic input map (IL1r)

Configuration settings to be made:

Communication scanner

inputs

[Scan. Out1 address] (nCA1) [Scan. Out2 address] (nCA2) [Scan. Out3 address] (nCA3) [Scan. Out4 address] (nCA4)

Parameter logic address Communication scanner

8501 8602 9001 9002

[Scan. IN1 address] (nMA1) [Scan. IN2 address] (nMA2) [Scan. IN3 address] (nMA3) [Scan. IN4 address] (nMA4)

outputs

Parameter logic address

3201 8604 8605 5202

18 1755877 11/2010

7. Configuring by the drive HMI

7. 3. Configuring the fault management

The DeviceNet card may detect 2 types of faults:

- Communication fault,

- Configuration fault.

The communication fault occurs when there is a time out on control traffi c: COS, cycl ic, polli ng or explic it messaging. In fact ory setting, the communication fault triggers a [Com. network] (CnF) fault.

The configuration fault occurs when:

- ODVA AC drive profile or Allen-Bradley® Drive profile are used (assemblies 20, 21, 22, 23, 70, 71, 72, 73, 103, 104, 105),

- the configuration of the drive control parameters is not correct (refer to 7. 1. Configuring the control),

- a DeviceNet connection is active between the drive and the PLC.

In factory setting, the communication fault triggers a [External fault com.] (EPF2) fault. The response of the drive in the event of a DeviceNet communicati on fault can also be configured.

Configuration can be performed using the graphic display terminal or int egrated display terminal in the [1.8 - FAULT MANAGEMENT] (FLt-) menu:

- For the communication fault, in the [COM. FAULT MANAGEMENT] (CLL-) submenu, via the [Network fault mgt] (CLL) parameter.

- For the configuration fault, in the [EXTERNAL FAULT] (EtF-) submenu, via the [External fault ass.] (EPL) parameter.

RDY NET +0.00Hz 0A

COM. FAULT MANAGEMENT Network fault mgt : Freewheel CANopen fault mgt : Freewheel Modbus fault mgt : Freewheel

Code Quick

The values of the [Network fault mgt] (CLL) or [External fault ass.] (EPL) parameters, which t rigger a drive fault [Com. network] (CnF), are:

Value Meaning

[Freewheel] (YES) Freewheel stop (factory setting) [Ramp stop] (rMP) Stop on ramp [Fast stop] (FSt) Fast stop [DC injection] (dCI ) DC injection sto p

The values of the [Network fault mgt] (CLL) or [External fault ass.] (EPL) parameters, which do not trigger a drive fault, are:

Value Meaning

[Ignore] (nO) Fault ignored [Per STT] (Stt) Stop according to configuration of [Type of stop] (Stt). [fallback spd] (LFF) Switch to fallback speed, maintained as long as the fault is present and the run command is not dis abled.

[Spd maint.]

(rLS)

The drive maintains the speed at the time the fault occurred, as long as the fault persists and the run command has not been removed.

The fallback speed can be configured in t he [1.8 – FAULT MANAGEMENT] (FLt-) menu using the [Fallbac k speed] (LFF) parameter.

1755877 11/2010 19

7. Configuring by the drive HMI

7. 4. Configuring monitored parameters

It is possible to select up to 4 parameters to display their values in the [1.2 - MONITORING] menu ([COMMUNICATION MAP] submenu) on the graphic display terminal.

The selection is made via the [6 – MONITOR CONFIG.] menu ([6.3 - CONFIG. COMM. MAP] submenu).

Each parameter [Address 1 select] ... [Address 4 selec t] can be used to choose the logic address of the parameter. Select an address of zero to disable the function.

In the example given here, the monitored words are:

• Parameter 1 = Motor current (LCr): Logic address 3204; signed decimal format

• Parameter 2 = Motor torque (Otr): logic address 3205; signed decimal format

• Parameter 3 = Last fault occurred (LFt): logic address 7121; hexadecimal format

• Disabled parameter: Address W0; default format: hexadecimal format

RDY NET +0.00Hz 0A

6.3 CONFIG. COMM. MAP. Address 1 select : 3204 FORMAT 1 : Signed Address 2 select : 3205 FORMAT 2 : Signed Address 3 select : 7121

Code Quick

FORMAT 3 : Hex Address 4 select : 0 FORMAT 4 : Hex

One of the three display formats below can be assigned to each monitored word:

Format Range Terminal display

Hexadecimal 0000 ... FFFF [Hex] Signed decimal -32 767 ... 32 767 [Signed] Unsigned decimal 0 ... 65 535 [Unsigned]

20 1755877 11/2010

8. Configuring by a network tool

8. 1. Network tool

RSNetWorx for DeviceNet is a Rockwell® software application that can be used to set up DeviceNet networks and configure connected devices.

RSNetWorx for DeviceNet (version 2.22.18) is used for examples in this manual. Different versions of software may differ in appearance and procedures.

Proper EDS file (A71vp_E.eds) and icone (Altivar_71.ico) for Altivar drives are distrib ute d on the CD-ROM del ive red wi th each dri ve. Th ey are also available on the Internet : www.schneider-electric.com

8. 2. Going online with RSNetWorx

You can view the devices on a DeviceNet network by going online. A device may appear as an unrecognised device if RSNetWorx does not have an EDS file for it.

1 After setting up a driver in RSLinx, start RSNetWorx for DeviceNet. 2 Select Network > Online. If the Browse for Network dialog box appears, RSLi nx has multiple drivers configured.

Select your DeviceNet network, and click OK. A prompt appears.

3 Click OK to go online. The devic es on the network appear in the Configur ation View. You can select Graph, Spreadshee t, or Master/Slave

views. The figure below shows an example network in a Graph view.

8. 3. Creating an EDS file

If the adapter and drive appear as an unrecognized device, create an EDS file for it.

1 Right-click the "Unrecognized Device" icon, and select Register Device in the menu. The EDS Wizard appears. 2 Click Next to display the next step. 3 Select Upload EDS, and then click Next. 4 Type a description (if desired), and then click Next. 5 Under Polled, select Enabled, type 4 in the Input Size and Output Size boxes, and then click Next. RSNetWorx will upload the EDS file

from the deviceNet card.

6 Click Next to display the icon options for the node. We recommend that you use the icon for your product. You can chan ge icons by

clicking Change icon. Proper icon (Altivar_71.ico) is distributed on the CD-ROM delivered with each dri ve. They are also available on the Internet :

www.schneider-electric.com

7 Click Next to view a summary, and then click Next again to accept it. 8 Click Finish to finish the EDS creation. A new icon represents the Altivar drive in the Configuration View.

1755877 11/2010 21

8. Configuring by a network tool

8. 4. Configuring the DeviceNet scanner

b Setting up the scan list

For the scanner to communicate with a drive, the scanner must be configured and the drive's node number must be added to its scan list.

1 Go online with RSNetWorx for DeviceNet. The devices on the network are displayed in the configuration view.

2 Right-click the DeviceNet scanner (node 00) and sel ect Properties. The Scanner Module dialog box appears.

Important: If your scanner is an unrecognized device, you must create an EDS file for it and then configure the scanner. Configure the

scanner using the General and Module tabs. If you need more information, click Help or refer to your scanner documentation.

3 Click the Scanlist tab. A message box prompts you to upload. 4 Click Upload. Data is uploaded from the scanner, and then the Scanlist page appears.

5 Select the Automap on Add box (a check mark will appear). 6 Under Available Devices, select the drive, and then click > (Right Arrow) to add it to the scanlist.

22 1755877 11/2010

+ 50 hidden pages

schneider VW3 A3 309 User Guide

Contents

1. Before you begin

2. Documentation structure

b Installation manual

b Programming manual

b Communication parameters manual

b Modbus, CANopen®, Ethernet™, Profibus, INTERBUS, Uni-Telway, DeviceNet™, Modbus Plus, Fipio, etc., manuals

b Altivar 58/58F migration manual

3. Introduction

3. 1. Presentation

3. 2. Notation

4. Quick start

5. Hardware setup

5. 1. Receipt

5. 2. Hardware description

5. 3. Installing the card in the drive

5. 4. Coding the switches

b Switches description

b Overriding the switches

b Coding the data rate

b Coding the node address

b Examples

6. Wiring to the network

6. 1. Cable routing practices

6. 2. Wiring the DeviceNet connector

7. Configuring by the drive HMI

7. 1. Configuring the control

b Principle

b Available configurations

b Control via DeviceNet in I/O profile

b Control via DeviceNet or via the terminals in I/O profile

b Control via DeviceNet in Drivecom profile

b Control via DeviceNet or the terminals in Drivecom profile

b Control in Drivecom profile via DeviceNet and setpoint switching at the terminals

7. 2. Configuring the communication scanner

7. 3. Configuring the fault management

7. 4. Configuring monitored parameters

8. Configuring by a network tool

8. 1. Network tool

8. 2. Going online with RSNetWorx

8. 3. Creating an EDS file

8. 4. Configuring the DeviceNet scanner

b Setting up the scan list