“Error Messages” Technology Template - Siemens · If a warning or error message occurs, ... The...

Applications & Tools

Answers for industry.

Cover Sheet

“Error Messages” Technology Template

Technology CPU

Application Description January 2010

2 "Error Messages" Technology Template

V4.1.1, ID Number: 21402122

Co

pyr

igh

t

Sie

me

ns

AG

20

10

All

righ

ts r

ese

rve

d

Industry Automation and Drive Technologies Service & Support Portal

This document is from the Internet service portal of Siemens AG, Industry Automation and Drive Technologies. The link below takes you directly to the download page of this document.

http://support.automation.siemens.com/WW/view/en/21402122

For questions about this document please use the following e-mail address:

[email protected]

http://support.automation.siemens.com/WW/view/en/21402122�

mailto:[email protected]�

"Error Messages" Technology Template V4.1.1, ID Number: 21402122 3

Co

pyr

igh

t

Sie

me

ns

AG

20

10

All

righ

ts r

ese

rve

d

s

SIMATIC "Error Messages" Technology Template

Technology CPU

Technology Template

1

Basics

2

Functional Mechanisms

3

Installation

4

Startup

5

Operation

6

Further Information

7

References

8

History

9

Warranty and liability


V4.1.1, ID Number: 21402122

Co

pyr

igh

t

Sie

me

ns

AG

20

10

All

righ

ts r

ese

rve

d

Warranty and liability Note The application examples are not binding and do not claim to be complete

regarding the circuits shown, equipping and any eventuality. The application examples do not represent customer-specific solutions. They are only intended to provide support for typical applications. You are responsible for 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 Siemens 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 these application examples 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.

Any claims against us – based on whatever legal reason – resulting from the use of the examples, information, programs, engineering and performance data etc. described in this application example shall be excluded. Such an exclusion shall not apply in the case of mandatory liability, e.g. under the German Product Liability Act (“Produkthaftungsgesetz”), in case of intent, gross negligence, or injury of life, body or health, guarantee for the quality of a product, fraudulent concealment of a deficiency or breach of a condition which goes to the root of the contract (“wesentliche Vertragspflichten”). However, claims arising from a breach of a condition which goes to the root of the contract shall be limited to the foreseeable damage which is intrinsic to the contract, unless caused by intent or gross negligence or based on mandatory liability for injury of life, body or health. The above provisions do not imply a change in 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.

Table of Contents


Co

pyr

igh

t

Sie

me

ns

AG

20

10

All

righ

ts r

ese

rve

d

Table of Contents Warranty and liability................................................................................................... 4 1 Technology Template........................................................................................ 7

1.1 Introduction........................................................................................... 7 1.1.1 The technology template...................................................................... 7 1.1.2 Main contents of this technology template........................................... 7 1.1.3 Scope ................................................................................................... 7 1.2 Objective and purpose ......................................................................... 7 1.2.1 Task...................................................................................................... 7 1.2.2 Advantages .......................................................................................... 8 1.3 Possible applications............................................................................ 9 1.3.1 Tasks that can be solved with the technology template....................... 9 1.3.2 Properties ............................................................................................. 9 1.3.3 Restrictions........................................................................................... 9 1.4 Components of the technology template............................................ 10 1.5 Approved hardware and software ...................................................... 10 1.5.1 Hardware components ....................................................................... 10 1.5.2 Software components......................................................................... 11

2 Basics ............................................................................................................... 13 2.1 Functional principle of the technology template................................. 13 2.2 Monitoring a technology object .......................................................... 13 2.3 Monitoring a technology function ....................................................... 14

3 Functional Mechanisms.................................................................................. 15 3.1 The ALARM_S message function ...................................................... 15 3.2 Text libraries....................................................................................... 16 3.3 Associated values of the ALARM_S message function ..................... 16 3.4 Formatting the ALARM_S message texts .......................................... 17 3.4.1 Setting the special object properties .................................................. 17 3.4.2 Formatting the output format for the text messages .......................... 18 3.5 Change language............................................................................... 20 3.5.1 Language versions of the text libraries .............................................. 20 3.5.2 Change language in STEP 7 for the “CPU Messages” function ........ 20 3.5.3 Change language of the HMI in WinCC flexible................................. 21 3.5.4 Formatting the text output for the respective language...................... 21

4 Installation........................................................................................................ 22 4.1 Preparations ....................................................................................... 22 4.1.1 Retrieving the technology template.................................................... 22 4.2 Integration into your application ......................................................... 23 4.2.1 Transferring the complete S7 program folder .................................... 23 4.2.2 Integrating the technology template into your STEP 7 project........... 24 4.2.3 Calling the function blocks ................................................................. 24 4.2.4 Assigning the instance data blocks .................................................... 25 4.3 Integration into the HMI...................................................................... 25

5 Startup .............................................................................................................. 26 5.1 Call environment ................................................................................ 26 5.2 Interfaces............................................................................................ 26 5.2.1 Interfaces of FB 510 “ShowErrFB” ..................................................... 26 5.2.2 Interfaces of FB 511 “ShowErrDB”..................................................... 27 5.3 Warning and error messages............................................................. 28 5.3.1 Signaling error events in the “Error Messages” template................... 28 5.3.2 Warning and error codes at the “ErrorID” output ............................... 28

Table of Contents


V4.1.1, ID Number: 21402122

Co

pyr

igh

t

Sie

me

ns

AG

20

10

All

righ

ts r

ese

rve

d

6 Operation.......................................................................................................... 30 6.1 Monitoring with FB 510 “ShowErrFB”................................................. 30 6.2 Monitoring with FB 511 “ShowErrDB” ................................................ 31 6.3 Error text output using “CPU Messages” ........................................... 32 6.3.1 Settings of the “CPU Messages” function .......................................... 32 6.3.2 Change language............................................................................... 33 6.4 Error text output in WinCC flexible ..................................................... 34 6.5 Test program for the technology template ......................................... 34 6.5.1 Requirements for running the test program ....................................... 34 6.5.2 HMI of the test program...................................................................... 35 6.5.3 Operating the test program ................................................................ 36 6.6 Generating error messages ............................................................... 38 6.6.1 Warning message 0021: Dynamic values are being limited .............. 38 6.6.2 Error message 8014: Approached a software limit switch ................. 39 6.6.3 Error message 8040: The axis / external encoder is not enabled, or

the wrong mode is set ........................................................................ 40 6.6.4 Error message 8074: The leading axis is not configured for

synchronous operation....................................................................... 40 7 Further Information ......................................................................................... 42

7.1 Expanding the text libraries................................................................ 42 7.2 Adding additional language versions ................................................. 42 7.2.1 Setting the display language in Step7................................................ 42 7.2.2 Exporting the text library..................................................................... 43 7.2.3 Opening and editing the exported text library .................................... 44 7.2.4 Importing text library with additional texts .......................................... 44 7.3 Displaying your own messages.......................................................... 45 7.3.1 Display with FB 510 “ShowErrFB”...................................................... 45 7.3.2 Display with FB 511 “ShowErrDB” ..................................................... 45 7.4 Displaying the axis designations in clear text .................................... 46

8 References ....................................................................................................... 47 8.1 References ......................................................................................... 47 8.2 Internet links ....................................................................................... 48

9 History............................................................................................................... 50

1 0BTechnology Template

1.1 9BIntroduction


Co

pyr

igh

t

Sie

me

ns

AG

20

10

All

righ

ts r

ese

rve

d

1 Technology Template

1.1 Introduction

1.1.1 The technology template

A technology template is a software object or a code block with a defined interface that can be easily integrated into other software projects with little overhead and that performs a precisely defined technological task in these projects.

This technology template helps you easily realize a clear text error display for error messages of the integrated technology in the technology CPU. All occurring error texts in German and English are already included in the technology template and can be additionally supplemented by your own messages.

The technology template was developed for application in conjunction with the technology CPU, but it can also be used as an error display with any other CPU supporting the ALARM_S function.

1.1.2 Main contents of this technology template

This technology template deals with the following main points:

Output of clear text error messages via the ALARM_S function

Expansion of the already existing text libraries

Text output formatting using the ALARM_S function

1.1.3 Scope

This technology template does not include a description of …

... the exact processes and sequences on which the ALARM_S function is based.

... the application and use of technology functions and technology objects with the technology CPU.

... the programming of the technology CPU in STEP 7.

Basic knowledge of these topics is assumed.

1.2 Objective and purpose

1.2.1 Task

When operating the technology CPU, states may occur in which warning and error messages are output by the technology objects of the integrated technology or the technology functions in the user program. These messages can only be detected by targeted monitoring of the technology objects or technology functions and indicated to the operator.

If a warning or error message occurs, a hexadecimal error code on the technology object or the technology function is used to inform the user of the cause of the error. However, this makes it difficult to easily and quickly interpret the warning or error message and to locate the cause of the error.


1.2 10BObjective and purpose


V4.1.1, ID Number: 21402122

Co

pyr

igh

t

Sie

me

ns

AG

20

10

All

righ

ts r

ese

rve

d

This “Error Messages” technology template helps the user monitor the desired technology objects and technology functions with regard to warning and error messages and display the occurring events in STEP 7 or on a connected HMI in clear text.

Figure 1-1 Detecting and interpreting technology error messages

Error message

additionalinformation

+

?“Error Messages”

technology template

The “Error Messages” technology template thus enables the user to easily and quickly locate and eliminate the cause of the error.

1.2.2 Advantages

The use of this technology template provides the user with the following advantages:

Fast program generation

With the aid of the “Error Messages” technology template, monitoring technology objects and technology functions with regard to warning and error messages can be implemented easily and quickly. The error codes can be easily displayed in clear text in STEP 7 or the HMI.

Adaptability

The function blocks and text libraries of the “Error Messages” technology template are not protected and can be adapted and expanded by the user if necessary.

It is also possible to supplement user-defined error numbers and error texts in the text libraries included in the delivery and to output them using the message procedure of the technology template.

Immediate readiness for service

The function blocks and text libraries of the “Error Messages” technology template can be applied to a self-created user program simply by copying and are ready for service immediately after calling the function blocks of the “Error Messages” technology template in the user program.


1.3 11BPossible applications


Co

pyr

igh

t

Sie

me

ns

AG

20

10

All

righ

ts r

ese

rve

d

1.3 Possible applications

1.3.1 Tasks that can be solved with the technology template

Using the technology template, the supported technology objects and technology functions can be monitored for error messages and occurring warning and error messages can be quickly displayed.

1.3.2 Properties

The “Error Messages” technology template can be used for clear text display of error codes of the following technology objects and technology functions:

Table 1-1 Supported technology objects and technology functions

Category Technology object / technology function

Axes Real and virtual drive axes, positioning axes and following axes. Electrical and hydraulic axes.

Cams Cams as an interpolation point table and a polynomial definition.

Output cams Position-based cams, switching output cams and time-based cams

Measuring inputs Measuring inputs

External encoders External encoders

Technology functions Technology function blocks from S7 Technology

Note The warning and error messages included in the technology template text library are valid for the technology objects and technology functions of “S7 Technology” up to and including version 4.1.

1.3.3 Restrictions

The following properties were not considered in the implementation of the technology template.

Only one message can be displayed per technology DB/FB Only one error or warning message can be displayed for each technology object and each technology function call.

No archiving of error messages Occurring error messages are not stored in the “Error Messages” technology template. If necessary, the messages have to be archived by the used display system (for example, the “CPU Messages” STEP 7 function).

ALARM_S message system must be supported The “Error Messages” template can only be used with HMI systems, for instance WinCC flexible, that support the ALARM_S message system.


1.4 12BComponents of the technology template


V4.1.1, ID Number: 21402122

Co

pyr

igh

t

Sie

me

ns

AG

20

10

All

righ

ts r

ese

rve

d

1.4 Components of the technology template

The “Error Messages” technology template consists of two function blocks and two text libraries.

Figure 1-2 Components of the “Error Messages” technology template

“Error Messages” technology template

FB 510“ShowErrFB”

Function blocks Text libraries

FB 511“ShowErrDB”

“317T_ErrorText”text library

“317T_ErrorDescription”text library

The function blocks of the technology template can be used independently of one another. They are used to monitor warning and error messages on the technology objects and technology function calls of the integrated technology of the technology CPU.

The text libraries contain the warning and error messages for the hexadecimal ErrorIDs of the integrated technology and additional info texts in clear text. They can be displayed using the “CPU Messages” STEP 7 function or integrated into self-created HMIs.

The warning and error messages and the additional notes on locating and eliminating the causes of errors are available in the text libraries in clear text in German and English.

1.5 Approved hardware and software

1.5.1 Hardware components

Table 1-2 Hardware components

Component No. MLFB / order number Note

CPU 315T-2 DP 1 6ES7315-6TG10-0AB0 or

6ES7315-6TH13-0AB0

Firmware V2.4.1 and higher

The CPU executes the user program and the technological functions.

Micro Memory Card 4MB

1 6ES7953-8LM11-0AA0 The S7 program is stored on the MMC.

Or alternatively:


1.5 13BApproved hardware and software


Co

pyr

igh

t

Sie

me

ns

AG

20

10

All

righ

ts r

ese

rve

d

Table 1-3 Hardware components – alternative


CPU 317T-2 DP 1 6ES7317-6TJ10-0AB0 or

6ES7317-6TK13-0AB0

Firmware V2.4.1 and higher

As an alternative to the CPU 315T-2 DP.

Micro Memory Card 4MB

1 6ES7953-8LM11-0AA0 The S7 program is stored on the MMC.

Note To be able to use the “Error Messages” technology template, the following system function blocks must be available in the controller:

SFC 18 “ALARM_S”: To output ALARM_S messages

SFC 24 “TEST_DB”: To check data blocks

1.5.2 Software components

Standard software components

Table 1-4 Standard software components


STEP 7 1 6ES7810-4CC08-0YA7 Version: V5.4 SP3 HF1

STEP 7 is the basic package for all optional software packages and used for programming the SIMATIC.

S7 Technology 1 6ES7864-1CC30-0YX0 Version: V4.1

Tool for parameterizing and programming the technology objects of the technology CPU.

Software components required for the test program

Table 1-5 Software components required for the test program


WinCC flexible Runtime 1 6AV6613-1FA51-3CA0 Version: 2008

The WinCC flexible Runtime software is required to operate the HMI of the test program.

WinCC flexible 1 6AV6613-0AA51-3CA5 Version: 2008

The WinCC flexible engineering software is required if changes are to be made to the HMI of the test program or if WinCC flexible Runtime is to be regenerated.


1.5 13BApproved hardware and software


V4.1.1, ID Number: 21402122

Co

pyr

igh

t

Sie

me

ns

AG

20

10

All

righ

ts r

ese

rve

d

Sample files and projects

The following list includes all files and archives used in this technology template:

Table 1-6 Files and STEP 7 archives of the technology template

Component Note

21402122_CPU317T_error_meassage_ CODE_v41.zip

This STEP 7 archive contains only the blocks associated with the technology template for integration into a user program.

21402122_CPU317T_error_meassage_ example_CODE_v41.zip

This STEP 7 archive contains both the blocks associated with the technology template for integration into a user program and a test program to check the parameterization options and functions of the technology template.

21402122_CPU31xT_error_meassage_ DOKU_v41_e.pdf

This document.

2 1BBasics

2.1 14BFunctional principle of the technology template


Co

pyr

igh

t

Sie

me

ns

AG

20

10

All

righ

ts r

ese

rve

d

2 Basics

2.1 Functional principle of the technology template

The figure below shows the functional principle of the “Error Messages” technology template:

Figure 2-1 Functional principle of the “Error Messages” technology template

“Error Messages”technology

template

Text library

ErrorID = error text

ID Text

S7 user program

TechnologyFB

TechnologyDB

ErrorID + status

ErrorID

Text

STEP 7

WinCCflexible

The function blocks of the “Error Messages” technology template monitor the technology function calls (technology FB) or the technology objects (technology DB) of the integrated technology. If an error or a warning occurs, the hexadecimal ErrorID is transferred to the ALARM_S message system via the function block. The ALARM_S message system combines the ErrorID with the error text stored in the text library. This error text can then be displayed together with the ErrorID.

The “CPU Messages” function from STEP 7 is available as an output medium for the warning and error messages. In addition, an output object in WinCC flexible for ALARM_S messages can also be integrated into a self-created HMI and the messages can be displayed on this HMI.

2.2 Monitoring a technology object

A technology object is monitored with the aid of the FB 511 “ShowErrDB” function block of the technology template.

Figure 2-2 Monitoring a technology object

S7 user program


TechnologyDB

ErrorID Error code

TDB_Nr

ErrorID

2 1BBasics

2.3 16BMonitoring a technology function


V4.1.1, ID Number: 21402122

Co

pyr

igh

t

Sie

me

ns

AG

20

10

All

righ

ts r

ese

rve

d

To monitor a technology object, the “ShowErrDB” function block of the template has to be called once during an OB1 cycle. Referencing to the technology object is performed using the number of the technology data block assigned to the technology object.

The function block independently monitors the location for the error code (ErrorID) included in the technology DB. If the technology object enters an error code in this location, this code is recognized via FB 511 “ShowErrDB” and displayed.

2.3 Monitoring a technology function

A technology function block is monitored with the aid of the FB 510 “ShowErrFB” function block of the “Error Messages” technology template.

Figure 2-3 Monitoring a technology function call

S7 user program


TechnologyFB

Status Error

ErrorID

Error

ErrorID Error code

To monitor a technology function call, a “ShowErrFB” function block of the technology template must be assigned to each technology FB of the technology CPU that is to be monitored. The output signals for the occurrence of an error and for the error code (ErrorID) are transferred to the function block of the template.

If a pending error is detected by FB 510 “ShowErrFB” via the Error signal, the error code communicated in the ErrorID is evaluated and displayed.

3 2BFunctional Mechanisms

3.1 17BThe ALARM_S message function


Co

pyr

igh

t

Sie

me

ns

AG

20

10

All

righ

ts r

ese

rve

d

3 Functional Mechanisms

3.1 The ALARM_S message function

The generation of messages in this technology template is realized using the SFC 18 “ALARM_S” system function.

This system function has to be called in the user program from a function block that features an input for transferring the EventID. Special attributes must be assigned to this input.

In the STEP 7 program, the EventID designates the message location for the ALARM_S message function. When integrating the function block into the user program in which the SFC 18 “ALARM_S” system function is called, STEP 7 – due to the system attributes – automatically enters the EventID at the block input.

Table 3-1 Assignment of the EventID by STEP 7

STL FBD

FB 510 “ShowErrFB”

FB 511 “ShowErrDB”

To assign the necessary system attributes to the EventID input variable of a newly created function block so that it can be used in conjunction with the SFC 18 “ALARM_S” system function, proceed as follows. These attributes have already been set at the blocks of the technology template.

Table 3-2 Definition of the system attributes

No. Action Remark

1. Open the function block and in the interface table select the EventID input variable.


3.2 18BText libraries


V4.1.1, ID Number: 21402122

Co

pyr

igh

t

Sie

me

ns

AG

20

10

All

righ

ts r

ese

rve

d

2. Use the context menu to open the object properties of this variable.

3. In the Attribute section of the object properties, set the following two attributes: S7_a_type = alarm_s S7_server = alarm_archiv Note: The attributes and values to be set can be taken from the drop-down lists of the setting fields.

Note The use of multi-instance data blocks for the function blocks in which SFC 18 “ALARM_S” is called is not possible since in this case the EventID cannot be automatically assigned by STEP 7 and therefore no reference to this block is possible in the ALARM_S message system.

3.2 Text libraries

The “Error Messages” technology template includes two text libraries for clear text display of error codes:

“317T_ErrorText” text library This library contains the error texts for the relevant error code.

“317T_ErrorDescription” text library This library includes the related error information for the relevant error code and notes on locating and eliminating the cause of the error.

The included text libraries have already been fully prepared with all error texts and related error information for S7 Technology in version 4.1 in German and English.

3.3 Associated values of the ALARM_S message function

With the aid of SFC 18 “ALARM_S”, one associated value from the user program with a maximum length of 12 bytes can be transferred to the ALARM_S message system.


3.4 20BFormatting the ALARM_S message texts


Co

pyr

igh

t

Sie

me

ns

AG

20

10

All

righ

ts r

ese

rve

d

Within the associated value, however, it is possible to transfer several process values up to an overall length of 12 bytes as an array (ARRAY) or a structure (STRUCT).

Figure 3-1 Transfer of several process values in the associated value of SFC 18 “ALARM_S”

The thus transferred process values can then be displayed separately within the alarm message of the ALARM_S message system. The process values are separated via the formatting of the ALARM_S message texts.

3.4 Formatting the ALARM_S message texts

The output format of the text messages is defined via special object properties of the function block in which the call of the SFC 18 “ALARM_S” system function is made.

3.4.1 Setting the special object properties

Table 3-3 Setting the output format of the text messages

No. Action Remark

1. In the SIMATIC Manager, use the context menu of the function block to call the Message... function in Special Object Properties.

2. Enter the desired formatting for the message text (Message text) and the additional information on the error message (Info text) to provide a more precise description of the cause of the error. Use More>> to show an advanced display in which also multi-line texts can be created by inserting line breaks (return). Note: For the input syntax for formatting the message texts, please refer to the next section.




V4.1.1, ID Number: 21402122

Co

pyr

igh

t

Sie

me

ns

AG

20

10

All

righ

ts r

ese

rve

d

3.4.2 Formatting the output format for the text messages

The text messages to be output can be taken from a text library or entered directly in the Message Configuration text line. In the technology template, for example, the word “code” was put in front of the output of the error number.

In addition, process values can be output in the text message directly from the user program, for instance, to output the axis number associated with the warning or error message.

Text message format

The output of a text block from a text library or a process value from the user program must be made in the following format:

@<Number of the process value><element type>%<format>@

Process value number

Via the number of the process value, the respective process value is selected for display from the associated value of the SFC 18 “ALARM_S” function.

Figure 3-2 Selection of the process value

Element type

The element type defines the length of the respective process value within the associated value. The element type must be suitable for the transferred process value so that it can be processed consistently in the message system.

Table 3-4 Possible element types of the process values

Element type Data type Note

Y BYTE

W WORD

X DWORD

I INT

D DINT

B BOOL

C CHAR

R REAL

The total of the byte lengths of the individual data types of the process values must not

exceed the maximum length of the associated value of the SFC 18 “ALARM_S” function of

12 bytes.

Associated value SFC 18

Process value 3

Process value 2

Process value 1




Co

pyr

igh

t

Sie

me

ns

AG

20

10

All

righ

ts r

ese

rve

d

Figure 3-3 Element types of the process values within the associated value

In the above figure, the three transferred process values of the WORD type occupy 6 bytes of the possible 12 bytes of the associated value of SFC 18 “ALARM_S”.

Format

The output of the process value within the message text is defined via the format. The process value can also be interpreted as an index of a text block in a text library. In this case, the text block is output in the message text instead of the process value.

Table 3-5 Possible formats for value output in the message text

Format Description Example

iX Hexadecimal number with i digits 4X

iu Unsigned decimal number with i digits 4u

id Signed decimal number with i digits 4d

ib Binary number with i digits 4b

i.yf Signed fixed-point number with y decimal positions and i total number of digits

4.1f

is String with i characters 4s

t#[text library] Text block from a text library t#317T_ErrorText

Figure 3-4 Formats of the process values for the text output

Ass. value SFC 18 3 x WORD = 3 x 2 bytes = 6 bytes

Message text:Axis @1I%3U@ - Code @2W%4X@ : @2W%t#317T_ErrorText@

Output of the axis number as a 3-digit unsigned decimal number

Output of the ErrorID as a 4-digit

hexadecimal number

Output of the ErrorID as a text block from the

317T_ErrorText text library


3.5 21BChange language


V4.1.1, ID Number: 21402122

Co

pyr

igh

t

Sie

me

ns

AG

20

10

All

righ

ts r

ese

rve

d

3.5 Change language

3.5.1 Language versions of the text libraries

The error and warning messages for clear text output are available in the delivered text libraries in the following languages:

German

English (USA)

To output the clear texts, the language can be changed in STEP 7 or – if change language was configured – in the HMI.

3.5.2 Change language in STEP 7 for the “CPU Messages” function

To change the display language in STEP 7 for the “CPU Messages” function, proceed as follows:

Table 3-6 Changing the display language for “CPU Messages”

No. Action Remark

1. If you have activated the “CPU Messages” function, exit this function by closing the display window.

2. In STEP 7 in the Options section, open the Manage Multilingual Texts list box and select the Change Language… function.

3. Select the desired language and confirm the selection with OK.

4. If the “CPU Messages” function is started after the selection, the error texts are now displayed in the selected language.


3.5 21BChange language


Co

pyr

igh

t

Sie

me

ns

AG

20

10

All

righ

ts r

ese

rve

d

3.5.3 Change language of the HMI in WinCC flexible

The change language in WinCC flexible to change the language online must be configured separately. At this point, only the most important steps will be briefly described. For more detailed information, please refer to the WinCC flexible documentation.

In the Language Settings section in Project Languages, select the desired languages from the list.

In Device Settings and Languages and Fonts, define the order of the selected languages.

In Communication and Tags, define an integer tag for the display language change. This tag is an internal tag; that is why “<internal Tag>” is entered as a Connection. In the tag properties in Events and Change Value, the SetLanguage function is selected with the assignment of the display language tag.

Set a button on the HMI that influences the integer tag for the display language. The language is displayed whose ordinal number in the defined order corresponds to the value of the tag for the display language.

Note An example of the change language in WinCC flexible can be taken from the test program for the use of the “Error Messages” technology template.

3.5.4 Formatting the text output for the respective language

As shown in chapter 3.4.2, the text output must be formatted separately for each configured language.

To do this, proceed as follows:

Table 3-7 Formatting the text output for the respective language

No. Action Remark

1. As described in chapter 3.5.2, select the language version for which you want to configure the text messages.

2. As shown in chapter 3.4.2, enter the desired message text for the selected language version in the special object properties of the function block in which SFC 18 “ALARM_S” is called.

3. Repeat the process for all other configured language versions.

4 3BInstallation

4.1 22BPreparations


V4.1.1, ID Number: 21402122

Co

pyr

igh

t

Sie

me

ns

AG

20

10

All

righ

ts r

ese

rve

d

4 Installation

4.1 Preparations

4.1.1 Retrieving the technology template

The “Error Messages” technology template is delivered as a STEP 7 archive. To be able to use the technology template, this archive first has to be retrieved using STEP 7.

Table 4-1 Retrieving the technology template

No. Action Remark

1. Start the STEP 7 programming environment and in the File section select Retrieve… Select the STEP 7 archive of the template.

2. Select the destination directory for the template. In most cases, the destination suggested by STEP 7 can be used. Use the OK button to start the retrieve action.

3. After successfully retrieving the objects, open the technology template in STEP 7. To do this, select the Yes button.

The “Error Messages” technology template includes an S7 program folder that contains all necessary elements for the use of the technology template.

Figure 4-1 Contents of the technology template

4 3BInstallation

4.2 23BIntegration into your application


Co

pyr

igh

t

Sie

me

ns

AG

20

10

All

righ

ts r

ese

rve

d

4.2 Integration into your application

For easy and quick transfer of the “Error Messages” technology template to your STEP 7 project, you should proceed as described below.

4.2.1 Transferring the complete S7 program folder

Table 4-2 Transferring the S7 program folder

No. Action Remark

1. In STEP 7, select the S7 program folder by clicking on it. In the Edit section, select the Copy function to copy the program folder to the buffer.

2. In STEP 7, create a new project by selecting the New... function in the File section or open an already existing STEP 7 project into which you want to integrate the template.

3. Insert the copied S7 program folder with the elements of the template into the project. Select the root node of the S7 project by clicking on it (first entry in the project structure overview) and in the Edit section select the Paste function.

4. Acknowledge the prompt with OK (apply default settings for CPU-wide message numbers).

4 3BInstallation

4.2 23BIntegration into your application


V4.1.1, ID Number: 21402122

Co

pyr

igh

t

Sie

me

ns

AG

20

10

All

righ

ts r

ese

rve

d

Note In already existing projects, CPU-wide message numbers also have to be enabled. For notes on changing the setting, please refer to the STEP 7 online help.

4.2.2 Integrating the technology template into your STEP 7 project

Table 4-3 Integrating the technology template into your project

No. Action Remark

1. Transferring the libraries: Select the Text Libraries folder and copy this folder to your S7 program folder.

2. Transferring the function blocks: Select all blocks that are available in the template in the Blocks folder and copy these blocks to the block folder of your project.

4.2.3 Calling the function blocks

Once you have transferred all blocks and text libraries supplied with the technology template to your STEP 7 project, you can use the functions provided by the technology template in your user program.

The calls of the function blocks of the “Error Messages” template in the STL and FBD programming languages are shown below as examples:

Table 4-4 Call of the function blocks

STL FBD

FB 510 “ShowErrFB”

FB 511 “ShowErrDB”

4 3BInstallation

4.3 24BIntegration into the HMI


Co

pyr

igh

t

Sie

me

ns

AG

20

10

All

righ

ts r

ese

rve

d

When calling the function blocks and after assigning the instance data blocks, STEP 7 automatically assigns a CPU-wide unique number to each block on the EventID parameter.

Note The CPU-wide unique number automatically assigned by STEP 7 on the EventID parameter must not be changed by the user!

4.2.4 Assigning the instance data blocks

A separate instance data block has to be assigned to each called function block of the “Error Messages” template.

The use of multi-instance data blocks is not possible when using the function blocks from the “Error Messages” template. In this case, the EventID is not automatically assigned by STEP 7 and therefore a reference to the block in the ALARM_S message system is not possible.

4.3 Integration into the HMI

To achieve a message output via HMIs, the text libraries have to be integrated into the HMIs.

This requires that the HMIs be configured in the STEP 7 project that includes the text libraries to be integrated.

A message output via ALARM_S must be set up and configured in the HMI. To integrate the text libraries, the HMI has to be recompiled.

Note When changes are made to the text libraries, the HMI also has to be recompiled to apply the changes to the message display of the user interface.

5 4BStartup

5.1 25BCall environment


V4.1.1, ID Number: 21402122

Co

pyr

igh

t

Sie

me

ns

AG

20

10

All

righ

ts r

ese

rve

d

5 Startup

5.1 Call environment

The blocks of the “Error Messages” technology template have to be called cyclically in the user program. The call of the blocks can be made directly in an OB or within a cyclically processed FB.

Figure 5-1 Call environment of the technology template

Controller

User block

Integratedtechnology

Technologyobjects

Cyclic OB(e.g., OB1,OB35 ...)

PLCopenFB

Technologyobjects

Axes



TechnologyDB

The FB 510 “ShowErrFB” block should be programmed in the respective user block directly after the technology function block to be monitored. This ensures that the user program can be clearly designed and possibly occurring warning and error messages are transferred directly after calling the technology function block.

However, monitoring a technology object via the technology DB with the aid of FB 511 “ShowErrDB” should be programmed at the end of the cyclic OB. The technology object has been influenced via the technology function calls during the OB cycle and the current technology object status can be checked by the block of the “Error Messages” technology template. The individual instances of FB 511 “ShowErrDB” can be called directly in the cyclic OB or within a cyclically called FB that is processed at the end of the OB cycle.

5.2 Interfaces

5.2.1 Interfaces of FB 510 “ShowErrFB”

To monitor the technology function calls by the FB 510 “ShowErrFB” function block, the following interfaces are available at the block:

5 4BStartup

5.2 26BInterfaces


Co

pyr

igh

t

Sie

me

ns

AG

20

10

All

righ

ts r

ese

rve

d

FB 510„ShowErrFB“

EventID

Error

ErrorID

FB_ErrorID

AxisAdditionalData

Table 5-1 Interfaces of FB 510 “ShowErrFB”

Parameter Data type Initial value Description

Input parameter

EventID DWORD DW#16#0 The EventID is used to assign the error message by the ALARM_S message system. It is automatically assigned by STEP 7 when integrating the block and must not be changed by the user.

Error BOOL False A pending error is signaled via this input.

ErrorID WORD W#16#0 The ErrorID contains the error code and forms the reference to the error text to be output. If the Error input has the value True, the ErrorID is transferred to the message system and the error message is displayed in clear text.

Axis INT 0 The axis number is displayed in the message text to assign the warning or error message to an axis.

AdditionalData WORD W#16#0 This additional data is transferred as a third process value in the associated value and can be displayed in the message text. However, the third process value is not yet configured in the message text!

Output parameter

FB_ErrorID INT 0 If an error occurs in the block while processing the error output, an error code is output.

5.2.2 Interfaces of FB 511 “ShowErrDB”

To monitor the technology objects by the FB 511 “ShowErrDB” function block, the following interfaces are available at the block:


EventID

TDB_Nr

IgnoreWarnings

FB_ErrorID

5 4BStartup

5.3 27BWarning and error messages


V4.1.1, ID Number: 21402122

Co

pyr

igh

t

Sie

me

ns

AG

20

10

All

righ

ts r

ese

rve

d

Table 5-2 Interfaces of FB 511 “ShowErrDB”

Parameter Data type Initial value Description

Input parameter

EventID DWORD DW#16#0 The EventID is used to assign the error message by the ALARM_S message system. It is automatically assigned by STEP 7 when integrating the block and must not be changed by the user.

TDB_Nr INT 0 Here the data block number of the technology object to be monitored or the technology data block assigned to it must be specified as a reference. The number entered here is also output as an axis number in the message text to assign the warning or error message.

IgnoreWarnings BOOL False If this input is set to True, only error messages of the technology objects are output. Warning messages are suppressed.

Output parameter

FB_ErrorID INT 0 If an error occurs in the block while processing the error output, this error is signaled here via the error code.

5.3 Warning and error messages

5.3.1 Signaling error events in the “Error Messages” template

If an error occurs when processing the error codes in the “Error Messages” template, this error is displayed at the FB_ErrorID output of the relevant function block via an error code.

5.3.2 Warning and error codes at the “ErrorID” output

The Ref. column indicates the block-internal error source of the function block of the “Error Messages” technology template.

Table 5-3 Error codes of the “Error Messages” technology template

FB_ ErrorID

Error Ref. Remark

0000 No error ---

0001 Associated value too long / no access to user memory

SFC 18 The message is sent

5 4BStartup

5.3 27BWarning and error messages


Co

pyr

igh

t

Sie

me

ns

AG

20

10

All

righ

ts r

ese

rve

d

FB_ ErrorID

Error Ref. Remark

0002 Last free message acknowledgement memory has been used

SFC 18

807F Internal error FB 511 Address of the DB data is outside the permitted range.

8081 EventID non-permissible SFC 18 The specified EventID is outside the permitted range.

8082 Resources exhausted SFC 18 Loss of messages since the CPU has no more resources for generating block-related messages by SFCs.

8083 Signal overflow SFC 18 Loss of messages since the same signal change already exists but could not yet be sent (signal overflow).

8084 No signal change detected SFC 18 The signal triggering the message has the same value for the current and the previous SFC 18 call.

8085 EventID invalid SFC 18 No logon for specified EventID.

8086 Double SFC call SFC 18 An SFC call for the specified EventID is already being processed in a lower priority class.

8087 Signal with value 0 transferred

SFC 18 When SFC 18 was first called, the signal triggering the message had the value 0.

8088 Double EventID SFC 18 The specified EventID is already being used by another system resource.

80A1 Error in DB number SFC 24 The specified DB number has the value 0 or exceeds the maximum DB number possible for the CPU.

80B1 DB does not exist SFC 24 The DB with the specified number does not exist on the CPU.

80B2 Unlinked DB SFC 24 The DB was generated using the keyword UNLINKED.

817F Internal error FB 511 Incorrect data block type detected or data block type is not supported by the template.

6 5BOperation

6.1 28BMonitoring with FB 510 “ShowErrFB”


V4.1.1, ID Number: 21402122

Co

pyr

igh

t

Sie

me

ns

AG

20

10

All

righ

ts r

ese

rve

d

6 Operation

6.1 Monitoring with FB 510 “ShowErrFB”

To monitor technology function calls by the FB 510 “ShowErrFB” block, the FB 510 block has to be programmed after each technology function call to be monitored.

When using this block, it has to be carefully checked which technology function calls are to be monitored since a separate instance data block must be assigned to each block call of FB 510 “ShowErrFB”.

Use during the development phase

To save memory space and to avoid unnecessary CPU load, FB 510 “ShowErrFB” should be used mainly during the development phase of a program.

Parameterization and call errors are primarily output on the technology function calls so that the use of this block should be limited to technology function calls with changing parameterization.

Monitoring of an MC_CamClear in the STL and FBD programming languages is shown below as an example.

Data transfer between the two blocks is performed via the temporary TempError and TempErrorID variables.

Table 6-1 Integration of FB 510 “ShowErrFB”

STL FBD

6 5BOperation

6.2 29BMonitoring with FB 511 “ShowErrDB”


Co

pyr

igh

t

Sie

me

ns

AG

20

10

All

righ

ts r

ese

rve

d

Note In the FBD/LAD programming language, the technology function call and the call of the FB 510 block must be made in different networks.

For the call of the FB 510 block, the best network to be selected is the one after the technology function call.

The STL programming language does not require this separation into different networks.

6.2 Monitoring with FB 511 “ShowErrDB”

To monitor technology objects by FB 511 “ShowErrDB”, one function block call has to be programmed for each technology object to be monitored.

It is recommended that the function block calls for monitoring the technology objects be integrated into a separate network at the end of OB1.

Monitoring of technology objects 2 and 5 in the STL and FBD programming languages is shown below as an example.

Table 6-2 Integration of FB 511 “ShowErrDB”

STL FBD

A separate FB 511 “ShowErrDB” with assigned instance data block is programmed for each technology object. Via the TDB_Nr input, FB 511 “ShowErrDB” is informed of the number of the technology object to be monitored. This number corresponds to the number of the technology data block of the respective technology object.

6 5BOperation

6.3 30BError text output using “CPU Messages”


V4.1.1, ID Number: 21402122

Co

pyr

igh

t

Sie

me

ns

AG

20

10

All

righ

ts r

ese

rve

d

Via the IgnoreWarnings input, the “True” or “False” status can be used to additionally inform the function block of whether warning messages of the technology object are to be output (“False”) or not (“True”).

6.3 Error text output using “CPU Messages”

Using the “CPU Messages” STEP 7 function, the error messages displayed by the function blocks of the technology template can be displayed on the programming unit without additional configuration and programming overhead.

The function can be called in the STEP 7 menu in the PLC section by selecting the CPU Messages... function.

To display the error texts from the “Error Messages” technology template, the “A” column of the CPU on which the “Error Messages” template is executed must be checked in the header of the window of the “CPU Messages” function. The messages received from the “Error Messages” template will then be displayed in the window of the “CPU Messages” function and archived.

Figure 6-1 The “CPU Messages” STEP 7 function

6.3.1 Settings of the “CPU Messages” function

In the window of the “CPU Messages” function, the following settings can be made via the menu in the View section:

Place on Top: When new error messages arrive or when error messages are deleted from the display, the “CPU Messages” window is automatically placed in the foreground or a blinking signal in the taskbar indicates this status.

Display of related information to locate and eliminate the error.

Display of error and warning messages.

Activation of CPU monitoring.

6 5BOperation

6.3 30BError text output using “CPU Messages”


Co

pyr

igh

t

Sie

me

ns

AG

20

10

All

righ

ts r

ese

rve

d

Leave in the Background: The “CPU Messages” function receives the incoming error messages and archives them, but does not indicate incoming and outgoing messages.

Ignore Message: The “CPU Messages” function does not receive messages of the “Error Messages” technology template, it does not display and archive them.

The archive of the “CPU Messages” function can be emptied in the Edit section using the Empty Archive function. In File, the archive entries can be saved using the Export Archive... function.

By selecting the Display Info Text function in the View section, the window for the display of related error information can be activated. A click on the desired error message displays the related error information in this window.

6.3.2 Change language

To change the display language in STEP 7 for the “CPU Messages” function, proceed as follows:

Table 6-3 Changing the display language for “CPU Messages”

No. Action Remark

1. If you have activated the “CPU Messages” function, exit this function by closing the display window.

2. In STEP 7 in the Options section, open the Manage Multilingual Texts list box and select the Change Language… function.

3. Select the desired language and confirm the selection with OK.

4. If the “CPU Messages” function is started after the selection, the error texts are now displayed in the selected language.

6 5BOperation

6.4 31BError text output in WinCC flexible


V4.1.1, ID Number: 21402122

Co

pyr

igh

t

Sie

me

ns

AG

20

10

All

righ

ts r

ese

rve

d

6.4 Error text output in WinCC flexible

Display of the message texts in WinCC flexible requires that an Alarm View be configured and that the ALARM_S message transfer be enabled in Alarm Management Settings Alarm Settings.

For more detailed information, please refer to the WinCC flexible documentation.

6.5 Test program for the technology template

For the first tests before integrating the technology template into a user program, a test program is available that offers the option to extensively test the display of error messages of the technology objects and technology functions using a convenient HMI.

No real machine axes are required for the test program. The program is immediately executable on a technology CPU and the necessary axes are simulated for the test as virtual axes in the controller.

NOTICE The test program is used to familiarize with the principle of operation and the reactions of the technology template.

This program is not intended for use in real machines and thus not released.

The test program is available as an independent STEP 7 archive with all required technology objects and STEP 7 blocks.

6.5.1 Requirements for running the test program

To start up the application example, the following requirements have to be met:

The STEP 7 project of the test program was correctly downloaded to the technology CPU.

The CPU is in RUN.

CPU and programming unit are connected via a Profibus connection with a transmission rate of 12 Mbaud.

NOTICE Before changing the interface speed, you should check the maximum speed of the CP or adapter you are using.

If this maximum speed is not 12 Mbps and if you download the application to the CPU without changes, you can no longer access the CPU!

For this reason, you have to set all MPI busses in the project to the maximum possible baud rate before downloading the application.

6 5BOperation

6.5 32BTest program for the technology template


Co

pyr

igh

t

Sie

me

ns

AG

20

10

All

righ

ts r

ese

rve

d

6.5.2 HMI of the test program

With the aid of the HMI of the test program, two virtual axes can be controlled using jog buttons. It is also possible to transmit a positioning job via which the relevant axis is automatically moved to the selected position.

The two axes of the test program are displayed on the HMI. The axes can be enabled and reset below the respective drive motor with the buttons available in this section. The axis enable is indicated by the green display next to the respective motor. The position and the velocity of the axis are displayed above the motor.

Figure 6-2 HMI of the test program

The enabled software limit switches in the plus and minus direction are displayed at the lower end of the axis. They can be approached using the jog buttons of the axis in the Jog section or by selecting the Move Absolute positioning command.

To synchronize the two axes via gearing, the Axis 1 -> GearIn -> Axis 2 button is available. Synchronous operation coupling of the axes can be requested using this button.

The error and warning messages are output in the top section of the HMI. This is where the messages are output in the message display. Using the ShowErrFB active and ShowErrDB active buttons, the message output for technology function calls and technology objects can be activated. When the buttons are green, the respective message function is activated. Using the Ignore Warnings button, it is additionally possible to suppress the output of warning messages so that only error messages are displayed in the message table.

The language of the error and warning messages can be selected online using the two flags in the top right part of the HMI. The currently active language is displayed with a green frame.

6 5BOperation



V4.1.1, ID Number: 21402122

Co

pyr

igh

t

Sie

me

ns

AG

20

10

All

righ

ts r

ese

rve

d

6.5.3 Operating the test program

The HMI offers the following operating options for the test program:

Figure 6-3 Operating options

The following functions are available to control the display of error messages:

Figure 6-4 Error display

Axis reset

Minus software limit switch

Plus software limit switch

Axis slide

Axis enabled

Axis enable

Position

Velocity Minus

jog button

Coupling of the axes via the MC_GearIn gearing

Change language:

English-German

Activate monitoring of

technology FBs

Activate monitoring of

technology objects

Suppress output of

warnings

Display section for error

messages

6 5BOperation



Co

pyr

igh

t

Sie

me

ns

AG

20

10

All

righ

ts r

ese

rve

d

Sequence of operations of the application example:

Table 6-4 Starting up the application example

No. Action Remark

1. Start the HMI on the programming unit.

2. Select the respective Enable buttons to enable the drives and use the Reset button to reset all errors and warnings of the test program for the relevant drive.

3. The axes can now be moved using the jog buttons. In addition, a positioning job can be started by selecting the desired position from the drop-down list and by starting the job using the Go! button.

4. Finally, the monitoring of the technology function calls and the technology objects has to be enabled using the ShowErrFB active and ShowErrDB active buttons. If the relevant button is displayed in green, monitoring is enabled and occurring error messages are displayed in the display section of the test program.

6 5BOperation

6.6 33BGenerating error messages


V4.1.1, ID Number: 21402122

Co

pyr

igh

t

Sie

me

ns

AG

20

10

All

righ

ts r

ese

rve

d

6.6 Generating error messages

With the aid of the test program, you can deliberately generate error and warning messages on a machine and display them using the “Error Messages” template.

The following error and warning situations can be generated easily and quickly in the test program for the “Error Messages” technology template:

0021: Dynamic values are being limited

8014: Approached a software limit switch

– 0026: Position limited to software limit switch

8040: The axis / external encoder is not enabled, or the wrong mode is set

8074: The leading axis is not configured for synchronous operation

– 804A: The required object interconnection is missing

Additionally occurring error and warning messages are of course also indicated via the “Error Messages” technology template.

Note If, with the aid of the test program, error and warning situations are successively generated in a period of time that is too short, the CPU may go to STOP!

To continue to execute the test program, the CPU must be restarted, i.e. it has to be reset to RUN.

6.6.1 Warning message 0021: Dynamic values are being limited

The axes of the test program are set so that the dynamic values are being permanently limited. Warning message 0021 “Dynamic values are being limited” is thus output for each motion of the axis.

Table 6-5 Generating warning message 0021

No. Action Remark

1. Enable the desired axis by selecting the Enable button.

2. Activate the monitoring of the technology objects or technology data blocks by the “Error Messages” template.

3. Move the axis with the jog function using the Minus or Plus jog buttons or activate a positioning job by selecting a position and using the Go! button.

4. Delete the message when the axis is stopped using the Reset button. Note: The message is only removed from the message display when the monitoring is activated using the ShowErrDB active button.

6 5BOperation



Co

pyr

igh

t

Sie

me

ns

AG

20

10

All

righ

ts r

ese

rve

d

5. You can suppress the output of the warning message when ShowErrDB active is active by activating the Ignore Warnings button.

6.6.2 Error message 8014: Approached a software limit switch

The software limit switch is approached when the yellow sensor at the lower end of the slide reaches the yellow limit switch marking.

Figure 6-5 Approaching software limit switch

Table 6-6 Generating error message 8014

No. Action Remark

1. Enable the desired axis by selecting the Enable button.

2. Activate the monitoring of the technology objects or technology data blocks by the “Error Messages” template.

3. Move the axis with the jog function using the Minus or Plus jog buttons or activate a positioning job by selecting a position behind a software limit switch and using the Go! button.

4. The axis can only be moved after you have deleted the pending error message using the Reset button. Note: The message is only removed from the message display when the monitoring is activated using the ShowErrDB active button.

5. With the jog function move the axis away from the software limit switch in the reverse direction using the Minus or Plus jog buttons or using a positioning job by selecting a position in the reverse direction and using the Go! button.

If necessary, warning message 0026 “Position limited to software limit switch” can be output when approaching a software limit switch via a positioning job before the axis has reached the limit switch.

6 5BOperation



V4.1.1, ID Number: 21402122

Co

pyr

igh

t

Sie

me

ns

AG

20

10

All

righ

ts r

ese

rve

d

The controller detects that the target position of the positioning job is behind the software limit switch and communicates this via warning message 0026 “Position limited to software limit switch”.

6.6.3 Error message 8040: The axis / external encoder is not enabled, or the wrong mode is set

Table 6-7 Generating error message 8040

No. Action Remark

1. Deactivate the enable for both axes using the Enable button.

2. Activate gearing for the two axes of the application example by selecting the Axis1 GearIn Axis2 button. The error message appears.

3. Now deactivate gearing using the Axis1 GearIn Axis2 button and the message disappears.

6.6.4 Error message 8074: The leading axis is not configured for synchronous operation

In the S7T Config configuration tool, the axes of the test program are created in such a way that a coupling option of the axes exists via MC_GearIn whereas the leading axis coupling of the following axis to the leading axis was not activated.

Figure 6-6 Missing coupling between leading axis and following axis in S7T Config

Table 6-8 Generating error messages 8074 and 804A

No. Action Remark

1. Enable both axes of the application example by selecting the Enable button.

2. Activate the monitoring of the technology objects or technology data blocks using the ShowErrDB active button.

6 5BOperation



Co

pyr

igh

t

Sie

me

ns

AG

20

10

All

righ

ts r

ese

rve

d

3. Activate the monitoring of the technology function calls using the ShowErrFB button.

4. Activate gearing for the two axes of the application example by selecting the Axis1 GearIn Axis2 button. Note: Both error messages (code 8074 and 804A) are displayed.

5. Now deactivate gearing using the Axis1 GearIn Axis2 button. Note: Message 804A disappears since the Execute signal of the technology function call is removed by the button.

6. Delete error message 8074 by selecting the Reset button of axis 2.

7 6BFurther Information


V4.1.1, ID Number: 21402122

Co

pyr

igh

t

Sie

me

ns

AG

20

10

All

righ

ts r

ese

rve

d

7 Further Information

7.1 Expanding the text libraries

To expand the text library, call the desired library and add new rows to the text library.

The reference to the respective text for display in the message text is made via the index that is entered in the first column of the text library.

Figure 7-1 Expanding the text library

If the text is to be entered in several languages, the text library first has to be filled in the currently activated language. All other languages then have to be entered by changing the display language or, as described in the following chapters, by exporting and importing the text library.

7.2 Adding additional language versions

7.2.1 Setting the display language in Step7

Before using or editing different language versions of the text libraries, all desired languages first have to be defined in the SIMATIC Manager:



Co

pyr

igh

t

Sie

me

ns

AG

20

10

All

righ

ts r

ese

rve

d

Table 7-1 Setting the display language

No. Action Remark

1. In the SIMATIC Manager in the Options section, select the Display Language... function.

2. Add the desired languages from the list box in the left part of the window to the already existing languages.

7.2.2 Exporting the text library

To be able to translate the already existing texts into the desired and just defined languages, the entire text library must be exported.

Table 7-2 Exporting the text library

No. Action Remark

1. In the SIMATIC Manager in Options and Manage Multilingual Texts, select the Export function.

2. Select the destination directory for storing (Storage Location) the export file and select CSV format (Format). Select the Source Language and additionally the Target Language into which the text library is to be translated.

3. The text library is now exported to the destination directory as a text file in CSV format.



V4.1.1, ID Number: 21402122

Co

pyr

igh

t

Sie

me

ns

AG

20

10

All

righ

ts r

ese

rve

d

7.2.3 Opening and editing the exported text library

For editing, the exported text file in CSV format of the text library can now be opened with Microsoft EXCEL. However, this requires that the Microsoft EXCEL Open dialog box be used.

After opening, each language of the text library is available in a separate column. Newly added languages are preset with the source language text. This text can now be replaced by the translated wording.

Figure 7-2 Opening the exported text library in Microsoft EXCEL

Note When editing the CSV file, change only the texts in the target language column and save the file in CSV format.

The original settings for all other entries and notes must not be changed. Otherwise, problems may occur when importing the CSV file to STEP 7.

7.2.4 Importing text library with additional texts

Table 7-3 Importing text library

No. Action Remark

1. In the STEP 7 Manager in Options and Manage Multilingual Texts, select the Import function.

Source language Target language

The translation can be entered here



Co

pyr

igh

t

Sie

me

ns

AG

20

10

All

righ

ts r

ese

rve

d

2. Select the directory in which the edited CSV file is located and start the data import.

Note An exported text library should only be reimported to the project from which it originates.

7.3 Displaying your own messages

The function blocks of the technology template can also be used to display your own messages by means of the ALARM_S message system.

7.3.1 Display with FB 510 “ShowErrFB”

FB 510 “ShowErrFB” is best suited for the display of your own messages using the “Error Messages” template.

Figure 7-3 Display of your own messages via FB 510 “ShowErrFB”


EventID

Error

ErrorID

FB_ErrorID

AxisAdditionalData

This requires that the index of the desired message be entered at the ErrorID input. When the Error input is set to True, the message – if the message text has already been entered in the text library – is output via the “Error Messages” technology template.

The message disappears from the display when the Error input of FB 510 “ShowErrFB” is reset to False.

7.3.2 Display with FB 511 “ShowErrDB”

Via FB 511 “ShowErrDB”, messages can be displayed that are output via a data block.

Figure 7-4 Display of your own messages via FB 511 “ShowErrDB”


EventID

TDB_Nr

IgnoreWarnings

FB_ErrorID

The number of the data block to be monitored must be entered at the TDB_Nr input. The function block then reads out the DBW 20 data word in the specified



V4.1.1, ID Number: 21402122

Co

pyr

igh

t

Sie

me

ns

AG

20

10

All

righ

ts r

ese

rve

d

data block and determines the data block type from this information. For technology data blocks, the data block type also indicates the technology object type.

The type of the data block also defines the address of the location in the data block from which the error code can be read out.

By default, the “Error Messages” technology template supports the following technology objects:

Table 7-4 Supported TO types (for Technology version 1.0, 2.0, 3.0 and 4.1)

TO type (UDT number) Technology object

V 1.0 V 2.0 V 3.0 V4.1

ErrorID address

DriveAxis 1 13 17 34 DBW 26

PosAxis 2 12 22 31 DBW 26

FollowingAxis 3 11 23 32 DBW 26

ExternalEncoder 4 14 18 36 DBW 26

Cam 5 5 24 33 DBW 22

MeasuringInput 6 6 21 30 DBW 26

OutputCam 7 15 19 35 DBW 22

CamTrack --- --- --- 37 DBW 26

TraceDB 8 8 8 8 Not supported

DeviceDB 10 16 25 25 DBW 26

If self-created data blocks are to be monitored, a type that refers to the correct location of the message index (ErrorID) must be entered in the DBW 20 data word of the data block. It may be necessary to supplement this type in FB 511 “ShowErrDB” accordingly.

7.4 Displaying the axis designations in clear text

In this version of the “Error Messages” technology template, the axis numbers or the numbers of the technology data blocks transferred to the FB 510 “ShowErrFB” and FB 511 “ShowErrDB” blocks are displayed in the message text as integer values.

If the axis designations are to be entered in the message text in clear text, you have to proceed as follows:

Create an additional text library for the axis designations. The index of the text library represents the axis number or the technology data block number of the respective axis.

Enter the relevant axis designations for all existing language versions.

Format the message text in such a way that the newly created text library is accessed for the output of the axis number.

For the exact procedure for generating the additional text library and integrating the clear text output into the message text, please refer to the previous chapters of this documentation.

8 7BReferences


Co

pyr

igh

t

Sie

me

ns

AG

20

10

All

righ

ts r

ese

rve

d

8 References

8.1 References

This list is by no means complete and only presents a selection of related references.

Table 8-1

Topic Title

/1/ STEP 7 Automating with STEP7 in STL and SCL Hans Berger Publicis MCD Verlag ISBN 3-89578-113-4

/2/ STEP 7 SIMATIC – Programming with STEP 7 V5.3 Siemens manual Edition 03/2006 MLFB: 6ES7810-4CA08-8AW1

/3/ STEP 7 SIMATIC – System Software for S7-300/400 System and Standard Functions Siemens Reference Manual Edition 03/2006 MLFB: 6ES7810-4CA08-8AW1

/4/ STEP 7 SIMATIC – Statement List (STL) for S7-300/400 Siemens Reference Manual Edition 03/2006 MLFB: 6ES7810-4CA08-8AW1

/5/ Technology CPU SIMATIC – S7-300 CPU Data: CPU 31xT-2DP Siemens Manual Edition 03/2008 MLFB: A5E01672598-01

/6/ Technology CPU SIMATIC – S7 Technology Siemens Function Manual Edition 03/2008 MLFB: A5E00251797-06

/7/ Technology CPU CPU 317T-2 DP: Controlling a virtual axis Getting Started Edition 03/2008 MLFB: A5E00266283-05

/8/ WinCC flexible SIMATIC HMI – WinCC flexible 2008 User Guide Ausgabe 07/2008 MLFB: A5E01024720-02

/9/ WinCC flexible SIMATIC HMI – WinCC flexible Getting Started for First Time Users Edition 04/2006 MLFB: A5E00279530-03

/10/ WinCC flexible SIMATIC HMI – WinCC flexible Getting Started for Power Users Edition 04/2006 MLFB: A5E00279883-03

8 7BReferences


V4.1.1, ID Number: 21402122

Co

pyr

igh

t

Sie

me

ns

AG

20

10

All

righ

ts r

ese

rve

d

8.2 Internet links

This list is by no means complete and only provides a selection of useful information.

Table 8-2

Topic Title

\1\ Reference to the document


\2\ Siemens Industry Customer Support

http://support.automation.siemens.com/

\3\ Siemens Industry Applications & Tools


\4\ Application examples for the technology CPU (a selection)

Palletizer with Simply Interpolating Axes Based on Cam Discs: http://support.automation.siemens.com/WW/view/en/21062269

Feeder for a Press: http://support.automation.siemens.com/WW/view/en/21363677

Flying Shears with Print-Mark Synchronization Based on Gear Synchronism: http://support.automation.siemens.com/WW/view/en/21063352

Cross Slide / Single Belt Application: http://support.automation.siemens.com/WW/view/en/24094737

Parameterization of the “Gear Synchronization” Technology Function (SyncOp Guide): http://support.automation.siemens.com/WW/view/en/23577545

\5\ Technology templates for the technology CPU (a selection)

Simple 3D Interpolation with Cam Disks: http://support.automation.siemens.com/WW/view/en/21364022

Hydraulics Characteristic: http://support.automation.siemens.com/WW/view/en/27731588

MoveCircle2D: http://support.automation.siemens.com/WW/view/en/26659810

Flying Shears: http://support.automation.siemens.com/WW/view/en/21062270

Moving Axes manually – “MoveJOG”: http://support.automation.siemens.com/WW/view/en/21365191

\6\ FAQs for the technology CPU (a selection)

Applicable encoders for the technology CPU 31xT in conjunction with the SIMODRIVE 611U, MASTERDRIVES MC drive systems http://support.automation.siemens.com/WW/view/en/19968954

Which versions of the S7 Technology option package are available and which SINAMICS S120 drive firmware can you use with which of these versions? http://support.automation.siemens.com/WW/view/en/23411204

How can I display a cam disk of the technology CPU on the HMI using WinCC flexible? http://support.automation.siemens.com/WW/view/en/26680228


http://support.automation.siemens.com/�















8 7BReferences


Co

pyr

igh

t

Sie

me

ns

AG

20

10

All

righ

ts r

ese

rve

d

Topic Title

\7\ Technology CPU manual

http://support.automation.siemens.com Select “Product Support” In the Product Information tree, open the following directories:

Automation Technology

Automation and control systems

Industrial Automation Systems SIMATIC

PLC

Modular Controller SIMATIC S7

S7-300

CPUs Select Manuals/Operating Instructions to open a list with related documents or use the following links:

S7 Technology: http://support.automation.siemens.com/WW/view/en/30119663

CPU manual 31xT-2 DP: http://support.automation.siemens.com/WW/view/en/31265208

\8\ WinCC flexible manual

http://support.automation.siemens.com Select “Product Support” In the Product Information tree, open the following directories:

Automation Technology

Operator control and monitoring systems

HMI Software

HMI System SIMATIC WinCC flexible

SIMATIC WinCC flexible ES Select Manuals/Operating Instructions to open a list with related documents or use the following links:

WinCC flexible manual: http://support.automation.siemens.com/WW/view/en/18796010

Getting Started for First Time Users: http://support.automation.siemens.com/WW/view/en/18660846

Getting Started for Power Users: http://support.automation.siemens.com/WW/view/en/18656980








9 8BHistory


V4.1.1, ID Number: 21402122

Co

pyr

igh

t

Sie

me

ns

AG

20

10

All

righ

ts r

ese

rve

d

9 History

Table 9-1

Version Date Modification

V1.0 First edition

V2.0 01/12/05 Revision of the “Error Messages” technology template:

Integration of the messages for the “S7 Technology” option package up to version 2.0 into the text libraries.

Introduction of the compact documentation.

V3.0 09/18/06 Revision and extension of the “Error Messages” technology template:


Implementation of the test program for the technology template in WinCC flexible.

Modification of the documentation to comply with the changes.

V4.1 02/18/09 Revision and extension of the “Error Messages” technology template:


Implementation of the test program for the technology template in WinCC flexible 2008.


V4.1.1 01/22/10 Revision and extension of the “Error Messages” technology template:

Expansion of the technology template blocks for the axis number display in the message text.


“Error Messages” Technology Template - Siemens · If a warning or error message occurs, ... The...

Documents

Transcript of “Error Messages” Technology Template - Siemens · If a warning or error message occurs, ... The...