Et200s Profc v30 en

Cover sheet
Communication Block for ET200S FC

and ET200pro FC
ET200S FC / ET200pro FC (FW3.0)
Application Description y June 2010
Applications & Tools

Answers for industry.
Industry Automation and Drives Technologies Service & Support Portal
This article comes from the Internet Service portal of Siemens AG, Industry
Automation and Drives Technologies. You can go directly to the download page of
this document using the following link.
http://support.automation.siemens.com/WW/view/de/46179468
If you have any questions relating to this document then please send them to us at
the following e-mail address:
online-support.automation@siemens.com
Copyright © Siemens AG 2010 All rights reserved
Communication with the frequency converter via FB100

2 V3.0, Article ID: 46179468
Table of contents
Table of contents
1 Warranty and liability ........................................................................................ 4
2 Automation function.......................................................................................... 5
2.1 Overview .............................................................................................5
2.1.1 Demarcation ........................................................................................5
2.1.2 Know-how that is required ...................................................................5
2.2 Description of the core functionality .....................................................6
3 Hardware and software components used ..................................................... 7
4 Function mechanisms of this application....................................................... 8
4.1 Function block ET200_FC_DRIV, FB100 ............................................8
4.1.1 Functionality ........................................................................................8
4.1.2 Schematic FBD representation............................................................8
4.1.3 Input and output parameters................................................................9
4.1.4 Timing behavior when transferring parameters from the converter ....12
4.1.5 Timing behavior for parameterizing errors .........................................13
4.1.6 Alarm and fault signals ......................................................................14
5 Installation........................................................................................................ 17
5.1 Installing the hardware ......................................................................17
5.2 Installing the software........................................................................17
5.3 Installing the application ....................................................................17

6 Commissioning the application ..................................................................... 21
6.1 Preparation........................................................................................21
6.2 Commissioning ..................................................................................21
7 Using the application ...................................................................................... 22
7.1 Overview ...........................................................................................22
7.2 Variable table "Step 1, Control signals" .............................................22
7.3 Variable table "Step 2, Control signals" .............................................24
7.4 Variable table "Step 3, Read parameters" .........................................26
7.5 Variable table "Step 4, Write parameters"..........................................28
8 Differences to FB100 for FW1.x ..................................................................... 30
8.1 Differences for the application options...............................................30
8.2 Differences in the integration and function.........................................30
8.3 Differences for the signals from ET200S_FC.....................................31
9 References ....................................................................................................... 32
9.1 References ........................................................................................32
9.2 Internet links - data ............................................................................32
10 History............................................................................................................... 33

V3.0, Article ID: 46179468 3
1 Warranty and liability
1 Warranty and liability

Note The application examples are not binding and do not claim to be complete
regarding the configuration and equipping as well as possible eventualities. The
application examples do not represent customer-specific solutions. They are only
intended to provide support for typical applications. You are responsible in
ensuring that the described products are correctly used. These application
examples do not relieve you of the responsibility of safely and professionally
using, installing, operating and servicing equipment. When using these
application examples, you recognize that we cannot be made liable for any
damage/claims beyond the liability clause described. We reserve the right to
make changes to these application examples at any time without prior notice. If
there are any deviations between the recommendations provided in this
application example and other Siemens publications - e.g. Catalogs, then the
contents of the other documents have priority.
We do not accept any liability for the information contained in this document.
Claims against us - irrespective of the legal grounds - resulting from the use of the
examples described in this application example, information, programs,
engineering and performance data etc. are completely excluded. Such an
exclusion shall not apply where liability is mandatory e.g. under the German
Product Liability Act involving intent, gross negligence, or injury of life, body or
health, guarantee for the quality of a product, fraudulent concealment of a
deficiency or non-performance. Claims of the purchaser for compensation relating

to non-performance of essential contract obligations shall be limited to foreseeable
damages typically covered by a contract unless intent, willful misconduct or gross
negligence is involved or injury of life, body or health. The above stipulations shall
not change the burden of proof to your detriment.
It is not permissible to transfer or copy these application examples or excerpts of

them without first having prior authorization from Siemens Industry Sector in
writing.

4 V3.0, Article ID: 46179468
2 Automation function
One or several ET200S FC frequency converters (FW 3.0 or higher) or ET200pro
FC are being used in a plant or system. Communication that goes beyond the
standard telegram 1 is to be established using these frequency converters.
2.1 Overview
With the launch of the ET200S FC (FW1.x), a partner block FB100 (V2.2) was also
provided. This partner block can no longer be used for the currently available
ET200S FC (FW 3.0).
A new FB100 (V 3.0) was developed to resolve this problem; this runs from
firmware version V3.0 and higher of the ET200S FC and ET200pro FC. During
development, special emphasis was placed on keeping the differences to the
previous FB100 (V2.2) to a minimum regarding its behavior and how it is
controlled.
2.1.1 Demarcation
The FB100 is released for ET200S FC and ET200pro FC from firmware version
V3.0 and higher. It cannot be used with older firmware versions.
This application does not include a description of how to parameterize the

frequency converter. The precondition to use the application is that the ET200S FC
or ET200pro FC converter has already been commissioned.
2.1.2 Know-how that is required
It is assumed that the reader has basic knowledge about using STEP 7 and the
parameterization of Siemens frequency converters.

V3.0, Article ID: 46179468 5
2.2 Description of the core functionality

• Cyclically transferring standard telegram 1
• Acyclically transferring control and status word 2
• Acyclically reading/writing parameters.
Sequence of the core functionality

Table 2-1
Action Note
1. Cyclically receiving
2. Cyclically sending
3. Cyclically evaluating faults
4. Check whether a new acyclic request is • Check whether a new parameter
possible or necessary and then select request is active and then start.
appropriately. • Check whether changes have been
made to control word 2, that it has
been enabled and transfer is
queued. Start the corresponding
send task.
• If the two previous points have not

taken place, start the read request.
5. If possible, select and send the request.
6. Check whether the request has been
completed
7. If completed, start the query Is first started with a delay of one or
several cycles
8. Evaluate the query
Advantages of this solution

• Simpler data exchange than the previous FB100
• Standardized solution
• Simple to use acyclic services are employed

6 V3.0, Article ID: 46179468
3 Hardware and software components used
3 Hardware and software components used

The application was generated using the following components:
Hardware components
Table 3-1 Structure of the core elements 1
Component Qty. MLFB/Order No. Note
CPU315F-2PN/DP 1 6ES7 315-2FH13-0AB0 With the matching
power supply
IM154-4 PAN HE Cu 1 6ES7 154-4AB10-0AB0
ET200pro F-FC 1 6SL3 235-0TE21-1SB0
Table 3-2 Structure of the core elements 2

IM151-7 F-CPU 1 6ES7 151-7FA01-0AB0 With the matching
power supply
PM-D F Profligate 1 3RK1 903-3BA00
ICU24F 1 6SL3 244-0SA01-1AA1
Standard software components

Table 3-3
STEP 7 1 6ES7810-5CC10-0YA5 License is required
STARTER 1 6SL3072-0AA00-0AG0 Not absolutely
necessary
Example files and projects

The following list includes all files and projects that are used in this example.
Table 3-4
Component Note
ET200_FC.zip <This zip file includes the STEP 7
project.>
ET200S-pro_FC_Deutsch.pdf This document.

V3.0, Article ID: 46179468 7
4 Function mechanisms of this application

4.1 Function block ET200_FC_DRIV, FB100
4.1.1 Functionality
Only the FB100 has to be integrated for commissioning. The FB100 must be called
once for each frequency converter that is to be controlled. The FB100 is assigned
to the frequency converter using the LADDR formal operands.
The block cyclically transfers the process data (standard: Control word 1,
frequency setpoint) from the SIMATIC to the drive taking into account the
consistency conditions. Status word 1 and the actual frequency are cyclically
received (standard).
The acyclic services, which can be used as required, serve to expand the function.
After the start, the function block is in normal cyclic data exchange with the ET
200S FC or ET200pro FC converters.
In conformance with the appropriate STEP7 rules, the function block can be
integrated in one of the following execution levels:
• Cyclic: OB1
• Time-controlled: e.g. OB35
4.1.2 Schematic FBD representation
Fig. 4-1 FBD representation
ET200S_FC_DRIV
WORD LADDR SFC_ERR BOOL
— —
INT FREQ_SET SFC_ERR_RD INT
— —
DWORD CTRL SFC_ERR_WR INT
— —
INT PAR_ADDRESS FREQ INT
— —
BYTE PAR_INDEX STAT DWORD
— —
REAL WRITE_DATA_VALUE ERR_NO_VALID BOOL
— —
BOOL DIRECTION ERR_NO INT
— —
BOOL REQ READ_DATA_VALUE REAL
— —
BOOL PAR_ERR_ACK BUSY BOOL
— —
BOOL CTRL_SRC PAR_ERR BOOL
— —
BOOL OLD_COMP PAR_ERR_NO BYTE
— —
BOOL CTRL2_ACT
—
BOOL STAT2_ACT
—

8 V3.0, Article ID: 46179468
4.1.3 Input and output parameters
Table 4-1 General FB parameters

Parameter Declarat Data Description
ion type
LADDR INPUT WORD Address of the ET 200S FC or ET200pro FC set in HW
Config for data exchange
Format: Hexadecimal,
Example: Configured start address 256 means LADDR =
W#16#100
SFC_ERR OUTPUT BOOL This output is at TRUE, if there is a communication error
in SFC 14/15.
SFC_ERR_RD OUTPUT INT This output contains the error number of the SFC14
SFC_ERR_WR OUTPUT INT This output contains the error number of the SFC15
Table 4-2 Cyclic FB parameters

ion type
FREQ_SET INPUT INT Input for the requested frequency setpoint referred to the
reference frequency (p2000)
Format: Hexadecimal, example: W#16#4000 = 100%
CTRL INPUT DWORD Input for the control words

Format: Hexadecimal,
Example: CTRL = DW#16#0000047E Æ
DW#16#0000047F = start converter (positive signal
edge)
Information:
For bit 10, a value of 1 is always transferred from the
FB100.
Only control word 1 is cyclically transferred. If control
word 2 is also to be transferred (acyclic), then
CTRL2_ACT must be set to TRUE.
If the converter is in the "running" state, then some of the
values of control word 2 cannot be processed. The
following are involved: Ext. Fault, drive data set select
bits 0 and 1 - as well as the switchover between closed-
loop speed and torque control.
FREQ OUTPUT INT This output indicates the value of p2051.1 (the frequency
actual value is the factory setting).
STAT OUTPUT DWORD This output indicates the status word of the converter
format: Binary
Note:
Only status word 1 is cyclically transferred. If status word
2 is also to be transferred (acyclic), then STAT2_ACT
must be set to TRUE.
ERR_NO_VALID OUTPUT BOOL This output is at TRUE, if the function block has received
a valid fault number of the ET 200S FC or ET200pro FC
ERR_NO OUTPUT INT This output indicates the fault number of the ET 200S FC
or ET200pro FC (value of r0947) in the decimal format.
Example: Fault F0090 Æ output 90.
For details on the fault signals, refer to the List Manual
ET 200S FC or ET200pro FC.

V3.0, Article ID: 46179468 9

ion type
Note:
By acknowledging twice, fault memory r0947 is cleared.
This means that if there are several faults, then they are
all reset by acknowledging twice.
Acyclic tasks can be rejected or in some cases cannot be executed in the

! "running" state. This means that it is only permissible to use acyclic
WARNING communication - especially control word 2 - for safety-relevant functions if
additional safety measures are carefully applied. These include, for
example, simultaneously withdrawing OFF2 or 3 - or using Safety
Integrated functions.
Note Read or write access errors are indicated at the FB100 using the outputs
SFC_ERR, SFC_ERR_RD and SFC_ER_WR (using SFC14 and SFC15). The
function of these diagnostics outputs in the FB100 depends on the interface
module IM 151 and the control (CPU) being used
Table 4-3 Asynchronous FB parameters


ion type
PAR_ADDRESS INPUT INT Number of the parameter that is to be read/written to
(see the parameter list of the ET 200S FC or ET200pro
FC).
Input example: for p1082 Æ input 1082

PAR_INDEX INPUT BYTE Number of the parameter index that is to be read/written
to (see the parameter list of the ET 200S FC or
ET200pro FC).
Format: Hexadecimal;
Example: Index 32 means PAR_INDEX = B#16#20
WRITE_DATA_VALUE INPUT REAL Parameter value that should be written
DIRECTION INPUT BOOL 1: Write parameter value
0: Read parameter value
REQ INPUT BOOL Data request. A rising edge starts the data transfer.
READ_DATA_VALUE OUTPUT REAL Read parameter value
BUSY OUTPUT BOOL This output is at TRUE if data is being exchanged
between the function block and the ET 200S FC or
ET200pro FC (sending or receiving).

10 V3.0, Article ID: 46179468
Table 4-4 Message and monitoring parameter errors

ion type
PAR_ERR_ACK INPUT BOOL Acknowledging a parameter error = 1
PAR_ERR OUTPUT BOOL This output is at TRUE if there is a parameter error.
PAR_ERR_NO OUTPUT BYTE This output indicates the error number in the decimal
format.
Example: PAR_ERR_NO = 106
See Table number 4-7, Error numbers, parameterizing
errors
Table 4-5 FB parameters with special functions

ion type
CTRL_SRC INPUT BOOL Select command data set
o Edge from 0 to 1 sets p0810 to 1.
(command data set 2 active)
o Edge from 1 to 0 sets p0810 to 0.
(command data set 1 active)
With the appropriate setting of p0700, the operator
control authority can be switched over from “USS on
RS232" to “Fieldbus" (SIMATIC S7).

OLD_COMP INPUT BOOL If active, several values in status word 1 are changed in
order to obtain the same behavior as for the ET200S with
FW 1.x
See Table 8-1, List of differences.
CTRL2_ACT INPUT BOOL If effective, control word 2 is transferred acyclically.
For a positive edge, all of the values are transferred once
to the converter.
For "true", the values of the individual bits of the STW2
are individually transferred when the state changes.
Note:
Observe the notes and warnings in and below Table 4-2
Cyclic FB parameters.
STAT2_ACT INPUT BOOL If active, status word 2 is continually transferred

acyclically, alternating with other possible acyclic
requests.

V3.0, Article ID: 46179468 11
4.1.4 Timing behavior when transferring parameters from the converter
The timing behavior when parameters are transferred from the converter is shown
in the following diagram.
Fig. 4-2 Transferring parameters to the converter


12 V3.0, Article ID: 46179468
4.1.5 Timing behavior for parameterizing errors
The following diagram shows how parameterizing errors are handled.
Fig. 4-3Parameterizing errors


V3.0, Article ID: 46179468 13
4.1.6 Alarm and fault signals
Communication errors
An SFC_ERR is output if a communication error between the PLC and converter

occurs due to a read or write error.
Table 4-6 Error numbers for SFC_ERR_RD and SFC_ERR_WR

Error No. Description
0000 No error has occurred.
8090 This message is output, if one of these errors occurs:

You have not configured a module for the specified logical basis address,
You have not observed the restriction regarding the length of the consistent
data,
You have not specified the start address in the LADDR parameter in the
hexadecimal notation.
8092 In ANY reference, type data not equal to BYTE has been specified.
Only for S7-400
8093 For the logical address specified under LADDR there is no DP module from
which you can read consistent data.
80A0 (RD) A read access error was identified when accessing the I/O
80A1 (WR) A write access error was identified when accessing the I/O
80B0 Slave failure at the external DP interface
80B1 The length of the specified target area is not equal to the net data length
configured with STEP 7.
80B2 System error at the external DP interface
80B3 System error at the external DP interface
80C0 (RD) The data have still not been read from the module
80C1 (WR) The data of the previous write task on the module have still not been
processed by the module.
80C2 System error at the external DP interface
80Fx System error at the external DP interface
87xy System error at the external DP interface
808x System error at the external DP interface
8xyy General error information

14 V3.0, Article ID: 46179468
Parameterizing error
A parameterizing error is signaled if one of the following input errors has been
made:
• incorrect parameter number
• incorrect index
• illegal value
Table 4-7 Parameter error numbers
Error No. Description

0 Invalid parameter number (PNU), if a PNU is not available.
An attempt was made to change a parameter although a change is inhibited as
p0927 bit 0 = 0.
1 Parameter value cannot be changed, because it involves a monitoring
parameter.
2 Lower or upper value limit exceeded.
3 Incorrect index.
4 No field index.
5 Incorrect data type
6 Setting not permissible (only reset is possible).

7 Under no circumstances can the description element be changed.
11 Closed loop control priority was not assigned.
12 Keyword missing, device parameter: "Access code" and/or "Special parameter
access" are not compatible.
17 Request cannot be executed due to the operating state. Presently, the
converter state does not permit the request.
30 No communication with the PLC within the time limit TIME_OUT_CYCLE. The
parameter value p8451 is too low.
Error number 30 is possible - and is also OK - in the commissioning phase or
directly after the commissioning phase of the PLC and converter.
31 Internal communication error
102 Channel too narrow, only for short channels. The parameterized length of the
PKW area was selected too large due to internal device restrictions. This error
signal can only be displayed in the T100 technology module for the USS
protocol, if this interface accesses parameters of the basis device.
104 Invalid parameter value. This error number is only transferred if the parameter
characteristic value, which is to be transferred, was not assigned to any
function in the device - or the parameter characteristic value at the time of the
change could not be transferred for internal reasons (although the value lies
within the limit values).
106 Request not implemented.
107 Incorrect data transfer sequence from the ET 200S.
108 The control module has not responded to the read/write task from the FB100
within the TIME_OUT_PARA cycle (p8450)

V3.0, Article ID: 46179468 15
Drive fault
Drive faults of the ET 200S FC are output via the “ERR_NO” output of the FB100.
ERR_NO contains the value of r0947.
Note • Output "ERR_NO_VALID of the FB100 should be used to evaluate drive faults for the
plant or system control!
• A table with all of the possible drive faults is provided in the List Manual of the ET
200S FC or ET200pro FC in the Chapter “Alarm and fault signals”.
• A diagnostics alarm for the particular fault can be programmed using the OB82.
• Diagnostic messages, which can initiate a corresponding diagnostics alarm at the
SIMATIC S7, can be activated or deactivated using parameter p8452 "DIA_LOCK".
LED displays (SF) are also enabled or suppressed.

16 V3.0, Article ID: 46179468
5 Installation
5 Installation
5.1 Installing the hardware

Create a system comprising SIMATIC and ET200S FC or ET200pro FC that
complies with the design and configuration rules of the particular devices. Please
refer to the relevant operating instructions for information about this.
Note The safety instructions for the hardware and software being used must always
be carefully observed.
5.2 Installing the software

Table 5-1
No. Action Comment
1 Install STEP7
2 Install STARTER or SIMOTION SCOUT Not absolutely necessary
5.3 Installing the application

Create a new project using SIMATIC Manager.
Create a hardware configuration corresponding to the hardware you are using. For
more detailed information on this topic, please refer to ET200S FC or ET200pro FC
operating instructions in Chapter Configuring/engineering.
In SIMATIC Manager, open the project that matches your configuration using
"File", "Open", "Project examples" and adapt the HW Config supplied for your
particular configuration.
As an alternative, you can also copy the contents of the "Blocks" folder of the
project example into your project.

V3.0, Article ID: 46179468 17
5 Installation
Two configurations are included in the example. The first is for an ET200S FC -
where one IM 151-7 CPU is used as control. The second is for an ET200pro FC,
which communicates with an S7-300 via Profinet. The blocks are the same.
Fig. 5-1 Overview of the blocks
Open the HW Config of your program and read out the start address of the
frequency converter.
Fig. 5-2 Configuration example, ET200pro


18 V3.0, Article ID: 46179468
5 Installation
Fig. 5-3 Configuration example, ET200S

Convert this address into the hexadecimal notation. In the example, an address of
100 HEX is obtained.
Enter this address into your program in the OB1 at the FB100 parameter "LADDR".
Fig. 5-4 Setting the address

V3.0, Article ID: 46179468 19
5 Installation
Save the OB1 and transfer all of the blocks into the CPU.

20 V3.0, Article ID: 46179468
6 Commissioning the application
6 Commissioning the application

6.1 Preparation
Table 6-1
No. Action Comment
1 Generating and loading the HW Config
2 Copy the blocks and variable table into your project. For your own projects, in which the
OBs already exist, it is generally
sufficient to just copy the FB100.
6.2 Commissioning
Table 6-2
No. Action Comment
1 Call the block with the assignment of the DB In the example, located in OB1.
2 Enter the LADDR value. Corresponds to the peripheral See Fig. 5-2 or 5-3
inputs and outputs of the converter as hexadecimal
value.
3 Adapt the remaining inputs and outputs Pre-assigned in the example so that
the variable tables can be used for
controlling and monitoring.
4 Load the blocks to the control.
Table 6-3 Optimizing acyclic communications

No. Action Comment
1 Observe the ERROR_RATE (address 288) in the DBs Without receiving status word 2, the
associated with the FB100. It is updated every 100 error rate increases as an inherent
requests and provides the percentage error during the system characteristic. This is because
last 100 transfers. the sequence of the calls has to be
Errors frequently occur by interrogating values too fast reorganized after acyclic
and too frequently - which results in the tasks being communication has been interrupted.
rejected. In the test mode - in order to improve
Continuous reception of status word 2 must be the results - a clock bit memory (e.g.
activated for optimization (STAT2_ACT = 1). 2s) can be used to continually initiate
The value should lie under 5% - ideally, 0%. that control word 2 is repeatedly sent.
However, in normal operation this is not
permissible as it is possible that there
is not sufficient time to send all
parameters.
2 This value can be influenced by adapting For all block calls on a control, it is
REQ_2_PAUSE_TIME (address 280 in the particular recommended that the same value is
DB). Increasing the pause time reduces the error rate. used - and this value should be
orientated to the highest
ERROR_RATE of all calls.

V3.0, Article ID: 46179468 21
7 Using the application

7.1 Overview
The application example should provide an introduction into the FB100. Using
various variable tables, you should learn how to handle the FB and gain an insight
into the operational sequences of the FB.
Initially, cyclic data transfer is discussed and then acyclic data transfer.
7.2 Variable table "Step 1, Control signals"

The control signals of the ET200S FC or ET200pro FC are supplied in this variable
table via FB100 and the status signals are displayed via the FB100.
Fig. 7-1Variable table 1


22 V3.0, Article ID: 46179468
The variable table is structured as follows:
Upper section (control signals):

You can enter the setpoint frequency via MW2 (FREQ_SET). By entering the HEX
value W#16#4000, the motor rotates with 100 % of the reference frequency, which
is specified via p2000. When entering the value W#16#1000, the motor then
correspondingly rotates with 25 % of the reference frequency.
The motor is started and stopped using MW6 (CTRL). The motor is started by
entering HEX value W#16#047F. The motor is stopped by entering HEX value
W#16#047E.
Center section (status signals):

The actual motor frequency is indicated at MW12 (FREQ). The values should be
interpreted essentially the same as the setpoint frequency, i.e. the value
W#16#4000 corresponds to 100 % of the reference frequency (p2000).
In addition, all of the status signals that FB100 reads out of the ET200S / pro FC
are made available in MD14 (STAT). To provide a better understanding, the most
important status signals (M17.0 to M17.7) that are contained in MD14 (STAT) are
listed below.
Please take any additional status signals from the ET200S FC or ET200pro FC List
Manual, Chapter "Function charts, function chart 4170" .
Lower section (fault signals):

Two types of fault signals are output via the FB100.
M20.1 (ERR_NO_VALID) and MW26 (ERR_NO): M20.1 signals that the ET200S
FC has a fault condition. You can read-out the corresponding fault number via
MW26. For more detailed information on the fault , please refer to the ET200S FC
or ET200pro FC List Manual in Chapter "Faults and alarms".
You can acknowledge these faults using M7.7 (Fault acknowledge). In this case, it
must be observed that if there is more than one fault in the ET200S FC, then the
first acknowledgment command only displays the next fault that is present. All of
the faults in the ET200S FC are only acknowledged with the second
acknowledgment command.
M20.0 (SFC_ERR), MW22 (SFC_ERR_RD) and MW24 (SFC_ERR_WR): M20.0
signals that an error has occurred in the Profibus coupling between the PLC and
the ET200S FC via the standard blocks SFC14 or SFC15.
For more detailed information about the fault/error, please refer to the Table 7-1
Fault numbers for SFC_ERR_RD and SFC_ERR_WR

V3.0, Article ID: 46179468 23
7.3 Variable table "Step 2, Control signals"

This variable table should be seen as a continuation of the previous variable table.
The difference to the previous table is the fact that the control word (MD4) is shown
with a list of the most important control signals. Please take any additional control
signals from the ET200S FC or ET200pro FC List Manual, Chapter "Function
charts, function chart 4150" .
Fig. 7-2Variable table 2

Upper section (control signals):

Just the same as in the previous variable table, you also have the possibility of
entering the setpoint frequency via MW2 (FREQ_SET). By entering the HEX value
W#16#4000, the motor rotates with 100 % of the reference frequency, which is
specified via p2000. When entering the value W#16#1000, the motor then
correspondingly rotates with 25 % of the reference frequency.

24 V3.0, Article ID: 46179468
Control word MD4 (CTRL) is listed in this variable table in the most important
control bits. Below, the function of the control bits used:
• M6.2: From Version V2.2 of the FB100 it is no longer necessary to
set this bit to signal 1. This bit is automatically set by the FB100.
• M7.1 to M7.6: Signal 1 for all control bits - switches the ET200S FC
into the state "Drive ready" (M17.0).
• M7.0: Signal 1 starts the motor. If this control signal is used, control
signals M6.0 (JOG clockwise) and M6.1 (JOG counter-clockwise)
must have a 0 signal.
• M6.3: Setpoint inversion (motor direction of rotation is reversed).
• M6.0 or M6.1: These two control bits control the JOG frequency for
clockwise (p1058) or counter-clockwise (p1059). If these control
signals are used, then M7.0 (ON/OFF1) must have a 0 signal.
Lower section (status signals):

The actual motor frequency is displayed at MW12 (FREQ). The values should be
interpreted essentially the same as the setpoint frequency, i.e. the value
W#16#4000 corresponds to 100 % of the reference frequency (p2000).
In addition, all of the status signals that FB100 reads out of the ET200S or
ET200pro FC are made available in MD14 (STAT). To provide a better
understanding, the most important status signals (M17.0 to M17.7) that are
contained in MD14 are listed below. Please take any additional status signals from
the ET200S FC or ET200pro FC List Manual, Chapter "Function charts, function
chart 4170"

V3.0, Article ID: 46179468 25
7.4 Variable table "Step 3, Read parameters"
The control signals to read the parameters of the ET200S FC or ET200pro FC are
supplied in this variable table via FB100 - and possible error signals when reading
the parameters are displayed.
Fig. 7-3 Variable table 3

Upper section (reading parameters):

MW32 (PAR_ADRESS) is used to specify the number of the parameter and MB34
(PAR_INDEX) the index of the parameter that you wish to read out of the ET200S
FC.
To read parameters, assign a 0 signal to M30.0 (DIRECTION).
Reading is started with a signal edge at M30.1 (REQ). During reading, M30.2
(BUSY) changes from a 0 signal to a 1 signal. Once reading has been completed,
M30.2 (BUSY) changes back to a 0 signal - and the value of the read parameter is
output via MD40 (READ_DATA_VALUE).
Please refer to the ET200S FC or ET200pro FC List Manual, Chapter "Parameter
description" (header line of the parameter, data type, U16 or U32 = DINT, Float =
REAL) for the value format (DINT or REAL).
Fig. 7-4Parameter description of the P1082
Lower section (parameter read/write error):

If, when reading a parameter, an error occurs (e.g. a parameter should be read that
does not exist), then the status of M31.0 (PAR_ERR) changes from a 0 signal to a

26 V3.0, Article ID: 46179468
1 signal. You can then read out the corresponding fault number in MB44
(PAR_ERR_NO). More detailed information on the cause of the error can be
obtained from the error number of Table 7-2 Parameter error numbers
You can acknowledge the error message using M31.1 (PAR_ERR_ACK).

V3.0, Article ID: 46179468 27
7.5 Variable table "Step 4, Write parameters"

The control signals to write the parameters of the ET200S FC or ET200pro FC are
supplied in this variable table via FB100 - and possible error messages when
writing the parameters are displayed.
Fig. 7-5 Variable table 4

Upper section (writing parameters):

MW32 (PAR_ADRESS) is used to specify the number of the parameter and MB34
(PAR_INDEX) the index of the parameter that you wish to write to the ET200S FC
or ET200pro FC.
MD36 (WRITE_DATA_VALUE) is used to specify the value of the parameter to be
written to.
Please refer to the ET200S FC or ET200pro FC List Manual, Chapter "Parameter
description" in the header line of the corresponding parameter from the data type
specification (U16 or U32 = DINT, Float = REAL) for the value format (DINT or
REAL).
Fig. 7-6Parameter description of the P1082
To write parameters, assign a 1 signal to M30.0 (DIRECTION).

28 V3.0, Article ID: 46179468
Writing is started with a signal edge at M30.1 (REQ). During writing, M30.2 (BUSY)
changes from a 0 signal to a 1 signal. Once reading has been completed, M30.2
(BUSY) changes back to a 0 signal.
Lower section (parameter read/write error):

If an error occurs when writing a parameter (e.g. a parameter should be changed
that cannot be changed in the actual operating state of the ET200S FC), then the
status of M31.0 (PAR_ERR) changes from a 0 signal to a 1 signal. You can then
read out the corresponding error number in MB44 (PAR_ERR_NO). More detailed
information on the cause of the error can be obtained from the error number of
Table 7-3 Parameter error numbers
You can acknowledge the error message using M31.1 (PAR_ERR_ACK).

V3.0, Article ID: 46179468 29
8 Differences to FB100 for FW1.x

The following information is for users who have already used FB100 (V2.2) for
ET200S FC with firmware Version V1.x, and who are now changing over to the
new FB100 (V3.0).
8.1 Differences for the application options

The new FB100 can now be used for the ET200S FC (from FW3.0 and higher) and
the ET200pro FC, which is connected via Profinet and Profibus.
8.2 Differences in the integration and function

The new FB100 has three additional formal operands:
• OLD_COMP
• CTRL2_ACT
• STAT2_ACT
The formal operand OLD_COMP is used to increase the compatibility to the
previous FB100 (FW1.x). With this FB, some signals did not comply with the
Profidrive profile.
Formal operands CTRL2_ACT and STAT2_ACT can be used to deactivate acyclic
transfer of control word 2 and status word 2 in order to increase the performance.
In order to obtain compatible behavior to the previous FB100 (FW1.x), both
operands must be pre-assigned a value of 1.
Contrary to the previous block, parts of control word 2 and status word 2 are no
longer used for internal purposes. This means that they are now completely
available.
For the control, it must be observed that the signal for external fault 1 is involved,
which means that it must be set to 1; otherwise, the converter has a fault signal.
Control and status word 2 are now acyclically transferred. This is the reason that
measures were taken to reduce the load on the backplane bus; as a consequence
the response behavior has changed. For control word 2, when changing a bit, only
what has actually been changed is transferred. If no change has occurred - with the
exception of re-initialization using a positive signal edge at CTRL2_ACT - nothing
is transferred.
If STAT2_ACT is activated, if present, the fault signal is updated each time that
status word 2 is called. If STAT2_ACT is not activated, the fault signal is updated
with a positive signal edge of the fault bit - and then subsequently only for
acknowledgment attempts that were not successful.

30 V3.0, Article ID: 46179468
8.3 Differences for the signals from ET200S_FC

Table 8-1 List of differences
Operating state / signal FW 1.x FW 3.0 OLD_COMP

involved active
Driving running Drive ready = 0 Drive ready = 1 Yes

Drive ready to run = 0 Drive ready to run = 1
Drive ready to run Drive ready = 0 Drive ready = 1 Yes
Missing OFF 2 or OFF 3 Drive ready = 1 Drive ready = 0 No
Brake not configured (in all Brake opened = 1 Brake opened = 0 No

operating states)
In the switched-off state Deviation, setpoint/actual Deviation, setpoint/actual No

value = 1 value = 0
Control word 2 - bit 5 f_act <= 2155 f_act = 2155 No
Control word 2 - bit 6 f_act >= setpoint f_act = setpoint No

Braking down to standstill Drive running = 1 Drive running = 0 No

when withdrawing OFF1.
If switched-off Motor clockwise rotation = Motor clockwise rotation = No

last value, operation 1
After jog operation f_act > p1080 f_min = 1 f_act > p1080 f_min = 0 No

V3.0, Article ID: 46179468 31
9 References
9 References
9.1 References
This list in no way complete and only reflects a selection of suitable literature.
Table 9-1
Subject area Title
/1/ STEP7 Automating with STEP7 in STL and SCL
Hans Berger
Publicis MCD Verlag
ISBN 3-89578-113-4
/2/
9.2 Internet links - data

This list in no way complete and only reflects a selection of suitable information.
Table 9-2
Subject area Title
\1\ Reference to the http://support.automation.siemens.com/WW/view/en/46179468

article
\2\ Siemens I IA/DT http://support.automation.siemens.com
Customer Support
\3\ ET200S FC http://support.automation.siemens.com/WW/view/en/26291825
Operating
Instructions
\4\ ET200S FC List http://support.automation.siemens.com/WW/view/en/26493107
Manual
\5\ ET200pro FC http://support.automation.siemens.com/WW/view/en/28561828
Operating
Instructions
\6\ ET200pro FC List http://support.automation.siemens.com/WW/view/en/29443619
Manual
\7\

32 V3.0, Article ID: 46179468
10 History
10 History
Table 10-1
Version Date Change
3.0 15.07.2010 Complete revision of the FB100 to control a ET200S FC and
ET200pro FC with firmware>= V3.0

V3.0, Article ID: 46179468 33

Et200s Profc v30 en

Uploaded by

Copyright:

Available Formats

You might also like

Et200s Profc v30 en

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Et200s Profc v30 en

Uploaded by

Copyright:

Available Formats

Cover sheet

Communication Block for ET200S FC

Application Description y June 2010

Applications & Tools

Communication with the frequency converter via FB100

5.3 Installing the application ....................................................................17

Communication with the frequency converter via FB100

1 Warranty and liability

deficiency or non-performance. Claims of the purchaser for compensation relating

It is not permissible to transfer or copy these application examples or excerpts of

Communication with the frequency converter via FB100

This application does not include a description of how to parameterize the

2.1.2 Know-how that is required

Communication with the frequency converter via FB100

2.2 Description of the core functionality

Sequence of the core functionality

• If the two previous points have not

Advantages of this solution

Communication with the frequency converter via FB100

3 Hardware and software components used

Table 3-2 Structure of the core elements 2

Standard software components

Example files and projects

Communication with the frequency converter via FB100

4 Function mechanisms of this application

4.1.2 Schematic FBD representation

Fig. 4-1 FBD representation

Communication with the frequency converter via FB100

4.1.3 Input and output parameters

Table 4-1 General FB parameters

Table 4-2 Cyclic FB parameters

CTRL INPUT DWORD Input for the control words

Communication with the frequency converter via FB100

Parameter Declarat Data Description

Acyclic tasks can be rejected or in some cases cannot be executed in the

Table 4-3 Asynchronous FB parameters

Parameter Declarat Data Description

Input example: for p1082 Æ input 1082

Communication with the frequency converter via FB100

Table 4-4 Message and monitoring parameter errors

Table 4-5 FB parameters with special functions

RS232" to “Fieldbus" (SIMATIC S7).

STAT2_ACT INPUT BOOL If active, status word 2 is continually transferred

Communication with the frequency converter via FB100

4.1.4 Timing behavior when transferring parameters from the converter

Fig. 4-2 Transferring parameters to the converter

Communication with the frequency converter via FB100

4.1.5 Timing behavior for parameterizing errors

The following diagram shows how parameterizing errors are handled.

Fig. 4-3Parameterizing errors

Communication with the frequency converter via FB100

4.1.6 Alarm and fault signals

An SFC_ERR is output if a communication error between the PLC and converter

Table 4-6 Error numbers for SFC_ERR_RD and SFC_ERR_WR

0000 No error has occurred.

8090 This message is output, if one of these errors occurs:

80B0 Slave failure at the external DP interface

80B2 System error at the external DP interface