1.

2.

3.

Purpose of the chapter or paragraph.

Important information or caution.

Additional information or remark.

1. Presentation

The purpose of this document is to help you for the diagnostic of network trouble.

This document does not explain how to configure the communication. For this part, refer to the network manual.

A communication trouble can come from different ways:

Wrong network configuration,

Bad connection,

Communication fault.

On the drive, several parameters are available in order to help you for the diagnostic:

LEDs are available and give an indication about the communication state,

Monitoring of communication parameters,

Communication fault: error code.

For each network trouble, the first reaction must be to check these 3 points.

2. Profibus DPV0 and DPV1

2.1. Quickly description

2.1.1. Profibus DPV0

With the Profibus DPV0 communication card (VW3 A3 307), data are exchanged according to the master-slave principle. Only the master can initialize communication. The slaves behave like servers responding to requests from masters.

The GSD file (Tele0956.gsd) is unique to the whole Altivar 61/71 ranges. It does not describe drive parameters, just communication information. This file is used by the PLC during configuration phases.

2.1.2. Profibus DPV1

With the Profibus DPV1 communication card (VW3 A3 307 S371), data are exchanged according to the master-slave principle. Only the master can initialize communication. The slaves behave like servers responding to requests from masters.

The GSD file (TELE09CD.gsd) is unique to the whole Altivar 61/71 ranges. It does not describe drive parameters, just communication information. This file is used by the PLC during configuration phases.

2.2. Checking the communication state with drive LEDs

2.2.1. Introduction

The LEDs give you information about the communication state. With this verification, you will know if there is activity or not on the network.

Both Profibus cards (DPV0 and DPV1) have 2 LEDs, status and data exchange, which are visible through the drive cover:

The status of the Profibus (DPV0 and DPV1) card is indicated by the red ST (status) LED.

The status of the Profibus (DPV0 and DPV1) communication link is indicated by the green DX (data exchange) LED.

Red ST LED

(LED 2.1)

Green DX LED

(LED 2.2) Meaning

Corrective actions in the event of malfunction

The card has been configured and its parameters set correctly by the master.

The card is in Idle state, awaiting configuration.

Enter a value between 1 and 126 using the switches on the option card.

The card is in Wait_Prm or Wait_Cfg state.

Check the connection to the Profibus DP bus, start up the PLC and, if the drive has a communication card fault (CnF), reset it.

The card is in (ILF) fault mode. Check the connection between the Profibus

DP card and the drive.

The card is in the "data exchange" state, and error-free data exchange is taking place.

No communication on the bus, no data is being exchanged.

Check the connection to the Profibus DP bus, start up the PLC.

LED state Visual description of the LED state

LED off

LED on

Slow flashing (0.5 s)

Quick flashing (0.1 s)

2.2.2. Points to check in function of the LEDs state

On configuration

Check that the Profibus address on the card is coherent with the master configuration.

Addresses 0 and 1 are usually reserved for the Profibus DP masters and must not be used to configure the Profibus DP address on an Altivar 61/71.

It is not advised to use address 126, which is incompatible with SSA service (Set Slave Address) and with some network configuration softwares (Sycon...).

Do a cycle Power OFF/ON on the drive, in order to validate the communication parameters. In case of separate supply (24 Vdc) with line contactor for example: when an option board is added, the drive must be supplied at least once by the power section. If not, the card can not be recognized and the communication will not work properly.

Check the number of stations on the network: a figure of 32 stations per segment without a repeater, or more than 127 with a repeater.

Check if the baud rate is in accordance with the cable length. The maximum length depends on the baud rate, the cable, the number of loads on the daisy chain, and the network configuration.

Data rate (kbps) 9.6 19.2 93.75 187.5 500 1500 3000 6000 12000

Distance/segment (m) 1200 1200 1000 400 200 100 100 100 100

On environment

Check the perturbation on the network: you can do a measurement of signal with a scope.

Check the type of cable and the length of bus.

Keep the bus away from the power cables (clearance of at least 30 cm).

If it is necessary for power cables to cross each other, be sure they cross at right angles.

Check if the termination resistor is present at each end of the segment.

2.3. Checking the communication map

2.3.1. Introduction

On both Profibus cards (DPV0 and DPV1), the communication map is the same.

On the graphic display terminal, the [1.2 - MONITORING] menu > [COMMUNICATION MAP] submenu can be used to display control-signal diagnostic information between the Altivar 61/71 drive and the Profibus DP master:

In the [COM. SCANNER INPUT MAP] submenu: PZD input values,

In the [COM SCANNER OUTPUT MAP] submenu: PZD output values,

In the [CMD. WORD IMAGE] submenu: command words from all channels,

In the [FREQ. REF. WORD MAP] submenu: frequency targets from all channels.

Displaying the command word

The [Command channel] parameter indicates the active command channel.

The [Cmd value] parameter indicates the hexadecimal value of the command word (CMD) used to control the drive.

The [CMD. WORD IMAGE] submenu is used to display the hexadecimal value of the command word produced by Profibus DPV0 and DPV1.

Displaying the frequency target

The [Channel ref. active] parameter indicates the active target channel.

The [Frequency ref] parameter indicates the value (in 0.1 Hz units) of the frequency target (LFR) used to control the drive.

The [FREQ. REF. WORD MAP] submenu is used to display the value (in 0.1 Hz units) of the speed target produced by Profibus DPV0 and DPV1.

Displaying the status word

The [Status word] parameter indicates the value of the status word (ETA).

Displaying parameters selected by the user

The four [W] parameters indicate the value of the four words selected by the user.

The address and the display format of these parameters can be configured in the [6 - MONITORING CONFIG.] menu > [6.3 - CONFIG. COMM. MAP] submenu.

The value of a monitored word equals "-----" if:

Monitoring has not been activated (address equals W0),

The parameter is protected,

The parameter is not known (e.g. W3200).

2.3.2. Points to check in case of wrong value monitoring

On configuration

Check the request sent by the master.

On environment

In case of wrong value monitoring, the recommendations on environment are the same than those described in the previous part.

Check the perturbation on the network: you can do a measurement of signal with a scope.

Check the type of cable and the length of bus.

Keep the bus away from the power cables (clearance of at least 30 cm).

If it is necessary for power cables to cross each other, be sure they cross at right angles.

Check if the termination resistor is present at each end of the segment.

2.4. Communication fault (CnF)

2.4.1. Introduction

On both Profibus cards (DPV0 and DPV1), the communication fault codes are the same.

Profibus DPV0 and DPV1 communication faults are displayed by the red RD indicator of the Profibus DP card.

In factory settings, a Profibus DPV0 and DPV1 communication fault triggers a resettable drive fault [Com. network] (CnF) and a freewheel stop.

The response of the drive in the event of a Profibus DPV0 and DPV1 communication fault can be changed (refer to the drive user manual):

Drive fault [Com. network] (CnF) (freewheel stop, stop on ramp, fast stop or DC injection stop).

No drive fault (stop, maintain, fallback).

How is detected a communication fault (CnF):

1. After initialization (power up), the drive checks that at least one of the command or target parameters has been written once via Profibus DPV0 and DPV1.

2. Then, if a Profibus DPV0 and DPV1 communication fault occurs, the drive reacts according to the configuration (stop, maintain, fallback...).

The origin of the last Profibus DPV0 and DPV1 communication fault can be displayed by the parameter [Com. network] (CnF):

Value Description of the values of the parameter [Com. network] (CnF)

0 No fault

1 Time out on the reception of the periodic variables addressed to the drive. This time out is adjustable by the network configuration software.

2 Identification error between the Profibus DP card of the drive and the Profibus DP master.

3 Identification error of the Profibus DP card of the drive (hardware problem).

The parameter [Com. network] (CnF) is displayed on the display terminal (graphic only): [1.10 DIAGNOSTICS] (DGT-) menu > [MORE FAULT INFO] (AFI-) submenu.

2.4.2. Points to check in case of communication fault (CnF)

A communication fault (CnF) indicates that the communication has worked properly between the drive and the master and, during the time defined by the time out, a loss of communication has been detected.

On configuration

Check the master state (RUN, stop).

Check if there is no network overload.

Check the time out value (try to increase the value with the network configuration software).

On environment

In case of (CnF), the recommendations on environment are the same than those described in the previous part.

Check the perturbation on the network: you can do a measurement of signal with a scope.

Check the type of cable and the length of bus.

Keep the bus away from the power cables (clearance of at least 30 cm).

If it is necessary for power cables to cross each other, be sure they cross at right angles.

Check if the termination resistor is present at each end of the segment.

2.5. Internal link fault (ILF)

2.5.1. Introduction

The [Option int link] (ILF) fault appears when there are serious problems:

Hardware problem on the Profibus DPV0 and DPV1 cards themselves,

Dialog faults between the option card and the drive.

It is not possible to configure the behavior of the drive in the event of a [Option int link] (ILF) fault, the drive stops in freewheels.

This type of fault cannot be reset.

Two parameters display the origin of the last [Option int link] (ILF) faults:

[Internal link fault 1] (ILF1) displays the error that occurred on option card no. 1 (directly mounted on the drive),

[Internal link fault 2] (ILF2) displays the error that occurred on option card no. 2 (mounted on the option card no. 1).

The parameters [Internal link fault 1] (ILF1) and [Internal link fault 2] (ILF2) are displayed on the display terminal (graphic only): [1.10 DIAGNOSTICS] (DGT-) menu > [MORE FAULT INFO] (AFI-) submenu.

List of the possible values for [Internal link fault 1] (ILF1) and [Internal link fault 2] (ILF2):

Value Description of the values of the parameters [Internal link fault 1] (ILF1) and [Internal link fault 2] (ILF2)

0 No fault

1 Loss of internal communication with the drive

2 Hardware malfunction detected

3 Error in the EEPROM checksum

4 Faulty EEPROM

5 Faulty Flash memory

6 Faulty RAM memory

7 Faulty NVRAM memory

101 Unknown card

102 Dialog faults between the option card and the drive

103 Dialog time out between the option card and the drive

2.5.2. Points to check in case of internal link fault (ILF)

The (ILF) fault appears when there is a communication fault between the option card and the drive.

Information

In case of codes 4 to 7 for [Internal link fault 1] (ILF1) or [Internal link fault 2] (ILF2), it is necessary to change the option board, and return the defect board to RTE (Return for Technical Expertise).

For the other codes, follow the recommendations below.

On configuration

Check if the drive is always supplied by the power part or sometimes the drive is supplied only by the external 24V (in case of line contactor for example). If several drives are supplied by only one external 24V, it could be possible that the external power supply is not enough strong.

Check that no more than 2 option cards (max. permitted) have been installed on the drive.

Check the PIN in connector between the card and the drive.

On environment

Check the perturbation on the network: you can do a measurement of signal with a scope.

Check the type of cable and the length of bus.

Keep the bus away from the power cables (clearance of at least 30 cm).

If it is necessary for power cables to cross each other, be sure they cross at right angles.

Check if the termination resistor is present at each end of the segment.

3. Conclusion Like described before, it can have a lot of causes for communication trouble.

Its the reason why to target the root and reproduce the fault, the points to check explained before are important.

It is necessary to give to the Global Help Desk the most information possible:

The drive version and the Profibus DP board version. It is necessary to precise if its a DPV0 or a DPV1 card (PowerSuite configuration if it is possible).

The network topology (number of slaves, type of master).

The Profibus DP board position (and if there is another option board on the same product).

The state of the LEDs.

If the communication has already worked or never.

When the (CnF) fault trips (unpredictable, after writing request, always after fixed time).

In case of (CnF): the (CnF) fault code.

When the (ILF) fault trips (unpredictable, at drive power ON).

In case of (ILF): the codes (ILF1) and (ILF2).

PresentationProfibus DPV0 and DPV1Quickly descriptionProfibus DPV0Profibus DPV1

Checking the communication state with drive LEDsIntroductionPoints to check in function of the LEDs stateOn configurationOn environment

Checking the communication mapIntroductionDisplaying the command wordDisplaying the frequency targetDisplaying the status wordDisplaying parameters selected by the user

Points to check in case of wrong value monitoringOn configurationOn environment

Communication fault (CnF)IntroductionPoints to check in case of communication fault (CnF)On configurationOn environment

Internal link fault (ILF)IntroductionPoints to check in case of internal link fault (ILF)InformationOn configurationOn environment

Conclusion