Profibus DPV 1
Profibus DPV 1
User's manual
Profibus DPv1
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 contain,
nor for any damages resulting from the application or use of the information herein.
The products and options 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 description can in no way be considered contractual.
3
Before you begin
Read and understand these instructions before performing any procedure with this drive.
DANGER
HAZARDOUS VOLTAGE
• Read and understand this manual before installing or operating the drive. Installation, adjustment, 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 in this variable speed drive, including printed wiring boards, operate at line voltage. DO NOT TOUCH.
Use only electrically insulated tools.
• DO NOT touch unshielded components or terminal strip screw connections with voltage present.
• Install and close all covers before applying power or starting and stopping the drive.
CAUTION
DAMAGED EQUIPMENT
Do not operate or install any drive that appears damaged.
Failure to follow this instruction can result in equipment damage.
4
Documentation structure
Installation manual
This manual describes:
• How to assemble the drive
• How to connect the drive
Programming manual
This manual describes:
• The functions
• The parameters
• How to use the drive display terminal (integrated display terminal and graphic display terminal)
Modbus, CANopen, Ethernet, Profibus, INTERBUS, Uni-Telway, FIPIO, Modbus Plus, DeviceNet ...
manuals
These manuals describe:
• Connection to the bus or network
• Configuration of the communication-specific parameters via the integrated display terminal or the graphic display terminal
• Diagnostics
• Software setup
• The communication services specific to the protocol
5
Introduction
Presentation
The Profibus DP communication card (catalog number VW3A A3 307 S371) is used to connect an Altivar 61 / 71 drive to a Profibus DPv1
bus.
• Configuring functions
• Uploading adjustment parameters
• Control-signaling
• Monitoring
• Diagnostics
The card has a 9-pin female SUB-D connector for connection to the Profibus DPv1 bus.
The connector and cable for connection to the Profibus DPv1 bus must be ordered separately.
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
In this manual, hexadecimal values are written as follows: 16#.
6
Hardware setup
Receipt
• Check that the card catalog number marked 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 damaged in transit.
Presentation
1 LEDs
7
Hardware setup
Pin 5 Pin 1
Connection accessories
Example of connection:
Altivar 61 / 71 Altivar 61 / 71
Intermediate
connectors
490 NAD 911 04
8
Hardware setup
Recommendations
• The user can select the data rate from a range of 9.6 kbps to 12 Mbps. This selection, made when starting up the network, applies to all
the bus subscribers.
Data rate (kbps) 9.6 19.2 93.75 187.5 500 1500 3000 6000 12000
Distance/segment (m) 1200 1200 1200 1000 400 200 100 100 100
• The bus ends with a line terminator at each end of the segment.
• Do not connect more than 32 stations per segment without a repeater, or more than 127 with a repeater.
• 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.
9
Configuration
This manual only describes Altivar 61 / 71 mode. To find out about Altivar 58 compatibility mode, refer to the ATV58-58F/ATV71 migration
manual.
10
Configuration
The table below indicates the positions of the switches for all configurable addresses:
0 0000 0000 032 0010 0000 064 0100 0000 096 0110 0000
1 0000 0001 033 0010 0001 065 0100 0001 097 0110 0001
002 0000 0010 034 0010 0010 066 0100 0010 098 0110 0010
003 0000 0011 035 0010 0011 067 0100 0011 099 0110 0011
004 0000 0100 036 0010 0100 068 0100 0100 100 0110 0100
005 0000 0101 037 0010 0101 069 0100 0101 101 0110 0101
006 0000 0110 038 0010 0110 070 0100 0110 102 0110 0110
007 0000 0111 039 0010 0111 071 0100 0111 103 0110 0111
008 0000 1000 040 0010 1000 072 0100 1000 104 0110 1000
009 0000 1001 041 0010 1001 073 0100 1001 105 0110 1001
010 0000 1010 042 0010 1010 074 0100 1010 106 0110 1010
011 0000 1011 043 0010 1011 075 0100 1011 107 0110 1011
012 0000 1100 044 0010 1100 076 0100 1100 108 0110 1100
013 0000 1101 045 0010 1101 077 0100 1101 109 0110 1101
014 0000 1110 046 0010 1110 078 0100 1110 110 0110 1110
015 0000 1111 047 0010 1111 079 0100 1111 111 0110 1111
016 0001 0000 048 0011 0000 080 0101 0000 112 0111 0000
017 0001 0001 049 0011 0001 081 0101 0001 113 0111 0001
018 0001 0010 050 0011 0010 082 0101 0010 114 0111 0010
019 0001 0011 051 0011 0011 083 0101 0011 115 0111 0011
020 0001 0100 052 0011 0100 084 0101 0100 116 0111 0100
021 0001 0101 053 0011 0101 085 0101 0101 117 0111 0101
022 0001 0110 054 0011 0110 086 0101 0110 118 0111 0110
023 0001 0111 055 0011 0111 087 0101 0111 119 0111 0111
024 0001 1000 056 0011 1000 088 0101 1000 120 0111 1000
025 0001 1001 057 0011 1001 089 0101 1001 121 0111 1001
026 0001 1010 058 0011 1010 090 0101 1010 122 0111 1010
027 0001 1011 059 0011 1011 091 0101 1011 123 0111 1011
028 0001 1100 060 0011 1100 092 0101 1100 124 0111 1100
029 0001 1101 061 0011 1101 093 0101 1101 125 0111 1101
030 0001 1110 062 0011 1110 094 0101 1110 126 0111 1110
031 0001 1111 063 0011 1111 095 0101 1111 0111 1111
• Addresses 0 and 1 are usually reserved for the Profibus DPv1 masters and must not be used to configure the Profibus DPv1 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, ...).
Examples:
Address 23
Address 89
The address can be checked via the display terminal (see Diagnostics section).
11
Configuration
Control-signal configuration
There are a number of possible configurations. For more information, refer to the programming and communication parameters manuals.
The configurations below are just some of the possibilities available.
Configuration via the graphic display terminal or the integrated display terminal:
Target 1B is connected to the functions (summing, PID, etc.) that remain active, even after switching.
Configuration via the graphic display terminal or the integrated display terminal:
12
Configuration
Configuration via the graphic display terminal or the integrated display terminal:
Configuration via the graphic display terminal or the integrated display terminal:
13
Configuration
Control in Drivecom profile via Profibus DPv1 and target switching at the terminals
The command comes from Profibus DPv1.
The target comes either from Profibus DPv1 or from the terminals. Input LI5 at the terminals is used to switch the target between Profibus
DPv1 and the terminals.
Control is in Drivecom profile.
Target 1B is connected to the functions (summing, PID, etc.) that remain active, even after switching.
Configuration via the graphic display terminal or the integrated display terminal:
14
Configuration
The 8 periodic output variables are assigned by means of parameters nCA1 to nCA8. They are configured using the graphic display terminal
via the [1.9 - COMMUNICATION] (COM-) menu and [COM. SCANNER OUTPUT] (OCS-) submenu.
Note: [COM. SCANNER OUTPUT] (OCS-) submenu defines the data (parameters nCA1 to nCA8) from the PLC to the drive.
An nCAp parameter with a value of zero does not designate any parameter in the drive. These 8 words are described in the table below:
The 8 periodic input variables are assigned by means of parameters nMA1 to nMA8. They are configured using the graphic display terminal
via the [1.9 - COMMUNICATION] (COM-) menu and [COM. SCANNER INPUT] (ICS-) submenu.
Note: [COM. SCANNER INPUT] (ICS-) submenu defines the data (parameters nMA1 to nMA8) from the drive to the PLC.
An nMAp parameter with a value of zero does not designate any parameter in the drive. These 8 words are described in the table below:
Note:
All modifications to parameters nMA1 ... nMA8 or nCA1 ... nCA8 must be made with the motor stopped.
The master PLC program should be updated to take account of this modification.
15
Configuration
Code Quick
The values of the [Network fault mgt] (CLL) parameter, which trigger 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 stop.
The values of the [Network fault mgt] (CLL) parameter, 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).
Change to fallback speed, maintained as long as the fault persists and the run command has not been
[fallback spd] (LFF) :
removed.
The drive maintains the speed at the time the fault occurred, as long as the fault persists and the run
[Spd maint.] (rLS) :
command has not been removed.
The fallback speed can be configured in the [1.8 – FAULT MANAGEMENT] (FLt-) menu using the [Fallback speed] (LFF)
parameter.
16
Configuration
The selection is made via the [6 - MONITORING CONFIG.] menu ([6.3 - CONFIG. COMM. MAP] submenu).
Each parameter in the range [Address 1 select] ... RDY NET +0.00Hz 0A
[Address 4 select] can be used to select the parameter logic
address. An address at zero is used to disable the function. 6.3 CONFIG. COMM. MAP.
Address 1 select : 3204
In the example given here, the monitored words are:
Format address 1 : Signed
• Parameter 1 = Motor current (LCR): Logic address 3204;
Address 2 select : 3205
signed decimal format
• Parameter 2 = Motor torque (OTR): Logic address W3205; signed Format address 2 : Signed
decimal format
• Parameter 3 = Last fault (LFT): Logic address W7121; hexadecimal Address 3 select : 7121
format
Code Quick
• Disabled parameter: Address W0; default format: Hexadecimal
format Format address 3 : Hex
Address 4 select : 0
Format address 4 : Hex
One of the three display formats below can be assigned to each monitored word:
the value displayed in the [COMMUNICATION MAP] screen will be "-----" (see "Diagnostics" section).
17
Diagnostics
LEDs
The Profibus DPv1 card has two LEDs, ST and DX, visible through the window on the cover of the Altivar 61 / 71:
1.1
1.2 • The status of the Profibus DPv1 card is indicated by the red ST (status) LED: LED 2.1.
1.3
• The status of the Profibus DPv1 communication link is indicated by the green DX (data exchange) LED: LED 2.2.
1.4
1.5
2.1 ST
2.2 DX
2.3
2.4
2.5
The table below gives the meaning of the various states of these two LEDs:
The card is in Idle state, awaiting Enter a value between 1 and 126 using the switches on the option
configuration. card.
The card is in Wait_Prm or Wait_Cfg state. Check the connection to the Profibus DPv1 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 DPv1 card and the
drive.
No communication on the bus, Check the connection to the Profibus DPv1 bus, start up the PLC.
no data is being exchanged.
LED states
18
Diagnostics
Control-signal diagnostics
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 DPv1 master:
19
Diagnostics
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 DPv1:
• Command word CMD3 .......... communication card channel .......... field [Com card cmd.]
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 DPv1:
• Speed target LFR3 .......... Profibus DPv1 channel .......... parameter [Com. card ref.]
The address and display format of these parameters can be configured in the [6 - MONITORING CONFIG.] menu
([6.3 - CONFIG. COMM. MAP] submenu) (see "Configuration" section on page 10).
20
Diagnostics
In this example, only the first two parameters have been configured (default assignment).
[Com Scan In1 val.] = [34343] Status word = 34359 = 16#8637 V Drivecom status "Operation enabled",
reverse operation, speed reached.
[Com Scan In2 val.] = [600] Output speed = 600 V 600 rpm
[Com Scan Out1 val.] = [15] Command word = 15 = 16#000F V "Enable operation" (Run) command
[Com Scan Out2 val.] = [598] Speed target = 600 V 598 rpm
21
Diagnostics
Communication faults
Profibus DPv1 communication faults are displayed by the red RD indicator of the Profibus DPv1 card.
In factory settings, a Profibus 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 DPv1 communication fault can be changed (see "Configuring communication fault
management"):
- Drive fault[Com. network] (CnF) (freewheel stop, stop on ramp, fast stop or DC injection stop).
- No drive fault (stop, maintain, fallback).
The fault management is described in the user’s manual "Communication parameters", chapter "Communication monitoring":
• After initialization (power up), the drive checks that at least one of the command or target parameters has been written once via
Profibus DPv1.
• Then, if a Profibus DPv1 communication fault occurs, the drive reacts according to the configuration (stop, maintain, fallback ...).
The origin of the last Profibus DPv1 communication fault can be displayed by the parameter [Com. network] (CnF) :
The parameter [Com. network] (CnF) is displayed on the display terminal (graphic only): [1.10 DIAGNOSTICS] (DGT-) menu, [MORE
FAULT INFO] (AFI-) submenu.
Card fault
The [Option int link] (ILF) fault appears when there are serious problems:
- Hardware problem on the Profibus DPv1 card itself.
- 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 freewheel.
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 parameter [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.
Value Description of the values of the parameter 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
8 Faulty analog input
9 Faulty analog output
10 Faulty logic input
11 Faulty logic output
101 Unknown card
102 Dialog faults between the option card and the drive
103 Dialog time out between the option card and the drive
22
Software setup of DPv1 messaging
Only the master can initialize communication. The slaves behave like servers responding to requests from masters.
Several masters can coexist on the same bus. In this case, the slave I/O can be read by all the masters. However, a single master has write
access to the outputs. The number of data items exchanged is defined at the time of configuration.
A GSD file contains the configuration information for the Altivar 61 / 71 with Profibus DPv1. This file is used by the PLC during the
configuration phases.
The GSD file is unique to the whole Altivar 61 / 71 range. It does not describe the drive parameters, just the communication information.
This file appears on the CD-ROM supplied with the drive.
The Profibus DPv1 card for Altivar 61 / 71 drives only supports supports types 3, 4, 5 and 8 PPO format (Parameter-Process Data-Object)
cyclic frames.
PPO cyclic frames contain the periodic variables that are used for 2 types of service:
- I/O exchanges (PZD)
- Aperiodic exchanges (PKW) for parameter setting, configuration and diagnostics
PKW aperiodic exchanges are included in the cyclic frames and do not require special frames. An aperiodic exchange is used to read or
write a parameter. The Altivar 61 / 71 PKW service does not conform to Profidrive.
23
Software setup of DPv1 messaging
Step 1: The Profibus DPv1 master must firstly give the slave the modbus offset of the parameter to be read or written:
Step 2 (read): The Profibus DPv1 master must give the length to be read starting from the offset indicated in step 1:
Step 2 (write): The Profibus DPv1 master must give the value to be written at the offset indicated in step 1:
To check what offset has been configured, it is possible to interrogate the slave:
24
Software setup of DPv1 messaging
Read
Write
Read report:
Write report:
25
Software setup of DPv0 messaging
Output PZDs
The first eight bytes contain an aperiodic request (PKW) to write or read a parameter.
The remaining 20 bytes contain the output PZDs (written from the Profibus master), of which only PZD1 to PZD8 are significant.
1 2 3 4 5 6 7 8 9 10 11 12 13 14
PKW PZD1 PZD2 PZD3
PKE 0 R/W PWE NC1 NC2 NC3
15 16 17 18 19 20 21 22 23 24 25 26 27 28
PZD4 PZD5 PZD6 PZD7 PZD8 PZD9 PZD10
NC4 NC5 NC6 NC7 NC8 Not used Not used
PKW request:
PKE Parameter logic address
RIW Request code
0: No request
1: Read
2: Write
PWE For a read request: Not used
For a write request: Parameter value
1 2 3 4 5 6 7 8 9 10 11 12 13 14
PKW PZD1 PZD2 PZD3
PKE 0 R/W PWE Command word Speed target Not used
15 16 17 18 19 20 21 22 23 24 25 26 27 28
PZD4 PZD5 PZD6 PZD7 PZD8 PZD9 PZD10
Not used Not used Not used Not used Not used Not used Not used
26
Software setup of DPv0 messaging
Input PZDs
The first eight bytes contain the response (PKW) to the aperiodic read/write request.
The remaining 20 bytes contain the input PZDs (read mode), of which only PZD1 to PZD8 are significant.
1 2 3 4 5 6 7 8 9 10 11 12 13 14
PKW PZD1 PZD2 PZD3
PKE 0 R/W/N PWE NM1 NM2 NM3
15 16 17 18 19 20 21 22 23 24 25 26 27 28
PZD4 PZD5 PZD6 PZD7 PZD8 PZD9 PZD10
NM4 NM5 NM6 NM7 NM8 Not used Not used
PKW request
PKE Parameter logic address
R/W/N Response code
0: No request
1: Successful read report
2: Successful write report
7: Error report
PWE For a successful request: Parameter value
For an incorrect request:
0: Incorrect address
1: Write access denied
1 2 3 4 5 6 7 8 9 10 11 12 13 14
PKW PZD1 PZD2 PZD3
PKE 0 R/W PWE Status word Output speed Not used
15 16 17 18 19 20 21 22 23 24 25 26 27 28
PZD4 PZD5 PZD6 PZD7 PZD8 PZD9 PZD10
Not used Not used Not used Not used Not used Not used Not used
27
Software setup of DPv0 messaging
Output PKWs
PKE
Parameter logic address
R/W
0: No request
1: Read
2: Write
One-off read and write requests can be triggered continuously while R/W equals 1 or 2.
Note:
Values other than 0, 1 and 2 should not be used. In particular, the values 16#0052 and 16#0057 must not be used, as these are reserved
for compatibility with the Altivar 58/58F.
PWE
If write: Value to be written
Input PKWs
PKE
Copies the output PKE value
R/W/N
0: No request
1: Correct read operation
2: Correct write operation
7: Read or write error
PWE
• If correct read operation: Parameter value. This can be limited by the drive if the maximum value is exceeded by the write operation.
• If there is an error:
0: Incorrect address
1: Write operation refused
Note:
The parameters in the output PZDs should not be changed by the PKW service.
Parameters linked to output PZDs should not be changed by the PKW service.
Example: The speed target and the frequency target.
28
Software setup of DPv0 messaging
Example of aperiodic write operation: Acceleration time ACC (address 9001) = 10 s, unit 0,1s (values in hexadecimal format).
1 2 3 4 5 6 7 8 etc.
23 29 00 02 00 00 00 64 etc.
ACC = 10 s
Write request
The positive response is identical to the write request, aperiodic part (bytes 1 to 8).
1 2 3 4 5 6 7 8 etc.
23 29 00 07 00 00 00 0 etc.
0 (incorrect address)
Negative response
29
Software setup using PL7
In PL7, cyclic exchanges between the Profibus DPv1 master (e.g., TSX Premium PLC + TSX PBY100 module) and the Altivar 61 / 71 take
the form of input words %IWxy.0.k and output words %QWxy.0.k, where "x" = number of the PLC rack and "y" = location of the
Profibus DPv1 module in the PLC rack.
Altivar 61 / 71 Altivar 71
Profibus PL7 output word Profibus PL7 input word
parameter parameter
PKW %QWxy.0 PKE PKW %IWxy.0 PKE
%QWxy.0.1 R/W %IWxy.0.1 R/W/N
%QWxy.0.2 Not used %IWxy.0.2 Not used
%QWxy.0.3 PWE %IWxy.0.3 PWE
PZD1 %QWxy.0.4 NC1 PZD1 %IWxy.0.4 NM1
PZD2 %QWxy.0.5 NC2 PZD2 %IWxy.0.5 NM2
PZD3 %QWxy.0.6 NC3 PZD3 %IWxy.0.6 NM3
PZD4 %QWxy.0.7 NC4 PZD4 %IWxy.0.7 NM4
PZD5 %QWxy.0.8 NC5 PZD5 %IWxy.0.8 NM5
PZD6 %QWxy.0.9 NC6 PZD6 %IWxy.0.9 NM6
PZD7 %QWxy.0.10 NC7 PZD7 %IWxy.0.10 NM7
PZD8 %QWxy.0.11 NC8 PZD8 %IWxy.0.11 NM8
PZD9 %QWxy.0.12 PZD9 %IWxy.0.12
Not used Not used
PZD10 %QWxy.0.13 PZD10 %IWxy.0.13
30
Example with SIMATIC Manager (STEP7)
Configuration example:
In the SIMATIC project:
• Add ATV71-PROFIBUS-DPV1-Modular to the Profibus address configured by the switch of the card.
• Write down the PLC memory address where ATV61 / 71 periodics are mapped (see figure above red circle).
This address area is used to setup DPv1 messaging.
31
Example with SIMATIC Manager (STEP7)
LADR field must correspond to the PLC memory address where ATV61 / 71 periodics are mapped (16#100 corresponds to 256 in decimal).
RECNUM field corresponds to the index (0XE9 ou 0XEA) in accordance with indirect mecanism already described.
32
atv61_71_ProfibusDPv1_EN_V1
2007-11