Application about Drive Technology Technology CPUs Compact Documentation Error Messages Technology Template
Warranty, liability and support 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. Warranty, liability and support 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. Copyright 2006 Siemens A&D. It is not permissible to transfer or copy these Application Examples or excerpts of them without first having prior authorization from Siemens A&D in writing. For questions about this document please use the following e-mail address: mailto:csweb@ad.siemens.de V3.0 Issue 09/18/06 2/14
Foreword Foreword The technology template A technology template is a software object or a code block with defined interfaces, which can easily be integrated into other software projects without extra work and which performs a precisely defined task in these projects. Support for the technology template Support services in the scope of the Customer Support can only be provided for the unaltered technology template. If the code is changed, it is no longer possible to provide support for the technology template. Reference to Automation and Drives Service & Support This entry is from the internet application portal of Automation and Drives Service & Support. Clicking the link below directly displays the download page of this document. http://support.automation.siemens.com/ww/view/en/21402122 V3.0 Issue 09/18/06 3/14
Table of Contents Table of Contents 1 Requirements... 5 1.1 Target group... 5 1.2 Objective and purpose of this technology template... 5 1.3 Properties of the Error Messages technology template... 6 1.3.1 Properties considered during the realization... 6 1.3.2 Performance limits of the technology template... 6 1.3.3 Requirements... 6 1.4 Restrictions of the technology template... 7 2 Operating Principle... 7 2.1 Monitoring of technology objects... 7 2.2 Monitoring of technology function blocks... 8 2.3 Display of error messages... 8 3 Operation of the Technology Template... 9 3.1 Integration of the technology template... 9 3.2 Integrating the text libraries into a STEP 7 project... 10 3.2.1 Copying the text libraries to the STEP 7 project... 10 3.2.2 Integrating the text libraries into the HMI... 10 3.3 Block interface... 11 3.3.1 FB 510 ShowErrFB... 11 3.3.2 FB 511 ShowErrDB... 12 4 Error Messages... 13 V3.0 Issue 09/18/06 4/14
Requirements 1 Requirements 1.1 Target group The technology template is intended for all programmers and users of technology CPUs who easily and quickly want to realize an error display for the technology objects and technology function blocks in a technology CPU. 1.2 Objective and purpose of this technology template When operating the technology CPU, states occur repeatedly in which warning and error messages are output by the technology objects of the integrated technology or during the technology function calls. These messages can only be identified by a specific monitoring of the corresponding I/Os in the technology data blocks or at the outputs of the technology function blocks. Figure 1-1 Identification and interpretation of technology error messages? Error Messages technology template Error message + additional information In addition, the displayed warning and error messages are communicated to the user in the form of a hexadecimal error code. An easy and quick interpretation of the warning or error message and the localization of the cause of the error is very difficult via these error codes. The Error Messages technology template can now be used for monitoring error events occurring at technology objects and technology function block calls. If an error occurs, the technology template indicates the cause of the error via a plain-text display and provides additional information for the localization of the cause of the error. V3.0 Issue 09/18/06 5/14
Requirements 1.3 Properties of the Error Messages technology template 1.3.1 Properties considered during the realization The properties listed below were considered during the realization of the template: Monitoring of technology objects The technology data blocks of axes, cam functions, cam switches, measuring inputs and external encoders can be monitored and occurring errors can be displayed in the plain-text display. Monitoring of technology function calls Monitoring of technology function block calls, e.g. FB 401 MC_Power, FB 402 MC_Reset, etc. and indication of occurring error events in the plain-text display. Included warning and error messages For the plain-text display of the warning and error messages the text library of the technology template contains all messages up to version V3.0 of the S7-Technology software package. 1.3.2 Performance limits of the technology template The following performance limits have to be considered when using the Error Messages template: Only one error or warning message Only one error or warning message can be displayed for each technology object and each technology function call. No message archive An archive for storing the occurring error messages does not exist in the Error Messages technology template. If required, the occurring error and warning messages have to be archived by the used display system (e.g. of the STEP 7 function CPU Messages ). 1.3.3 Requirements Operating the Error Messages technology template together with a technology CPU requires that the following system function blocks exist in the controller: SFC 18 ALARM_S For the output of ALARM_S messages SFC 24 TEST_DB For checking data blocks V3.0 Issue 09/18/06 6/14
Operating Principle 1.4 Restrictions of the technology template The following properties were not considered during the realization of the template and consequently exclude an unaltered use of the template in a self-created user program: HMI system must support ALARM_S The Error Messages template can only be used with HMI systems such as WinCC flexible or ProTool/Pro which support the ALARM_S message system. 2 Operating Principle The monitoring of error events and the display of the error messages in the plain-text display by the Error Messages technology template is performed according to the following operating principle: 2.1 Monitoring of technology objects A technology object is monitored with the aid of the function block FB 511 ShowErrDB. Figure 2-1 Monitoring a technology object S7 user program Technology DB Error code TDB_No FB 511 ShowErrDB To monitor a technology object, it is required that the function block ShowErrDB is called once during an OB1 cycle. The technology object is referenced by the number of the technology data block assigned to the technology object. The function block independently monitors the storage location for the error code () included in the technology DB. If an error code is entered by the technology object in this location, this error code is detected by the function block FB 511 ShowErrDB and displayed. V3.0 Issue 09/18/06 7/14
Operating Principle 2.2 Monitoring of technology function blocks A technology function block is monitored with the aid of the function block FB 510 ShowErrFB. Figure 2-2 Monitoring a technology function call S7 user program Technology FB Error Status Error code Error FB 510 ShowErrFB Note To monitor a technology function call, it is required that a ShowErrFB function block is assigned to each technology FB to be monitored. The output signals for the existence of an error and for the error code () are transmitted to ShowErrFB. If a present error is detected via the Error input of FB 510 ShowErrFB, the error code transmitted in the is evaluated and displayed. The error code of a technology function call is only displayed as long as the Execute bit of the PLC-Open block is set to True. If the Execute bit is cleared, the is no longer output and the error is no longer displayed on the display. 2.3 Display of error messages The errors are not only displayed via their error code but two text libraries in the template ensure that occurring error and warning messages can be transferred to a plain-text display. In addition, further information for the localization of the cause of the error is available to the user via an additional text output. V3.0 Issue 09/18/06 8/14
Operation of the Technology Template Figure 2-3 Display of error messages S7 user program Technology FB Technology DB + status Text library = error message ID Text Error Messages technology template Text STEP 7 WinCC flexible ProTool/Pro 3 Operation of the Technology Template 3.1 Integration of the technology template To integrate the Error Messages technology template into a STEP 7 project, it would be best to copy the complete S7 program folder from the archive of the technology template to the STEP 7 project and to distribute the necessary function blocks and the Text Libraries folder from there. To use the function blocks from the technology template, it is required that Assign unique message numbers CPU-wide is activated in the STEP 7 project. Figure 3-1 Activation of the CPU-wide message numbers V3.0 Issue 09/18/06 9/14
Operation of the Technology Template Note Assign unique message numbers CPU-wide also has to be activated in already existing projects. For notes on changing this setting, please refer to the STEP 7 online help. 3.2 Integrating the text libraries into a STEP 7 project 3.2.1 Copying the text libraries to the STEP 7 project The Error Messages technology template includes two text libraries for the plain-text display of the error codes: 317T_ErrorText text library This library includes the error messages corresponding to the error code. 317T_ErrorDescription text library This library includes further error information on the respective error code and notes for locating and correcting the cause of the error. To integrate the text libraries into the STEP 7 project, it is required that the complete Text Libraries folder is copied to the project. 3.2.2 Integrating the text libraries into the HMI To achieve a message display on HMIs, the text libraries have to be integrated into the HMIs. This requires that the HMIs are configured in the STEP 7 project which includes the text libraries to be integrated. A message display via ALARM_S must be set up and configured in the HMI. Integrating the text libraries requires a recompilation of the HMI. Note If the text libraries are changed, the HMI also has to be recompiled to apply the changes to the message display of the user interface. V3.0 Issue 09/18/06 10/14
Operation of the Technology Template 3.3 Block interface 3.3.1 FB 510 ShowErrFB For monitoring the technology function calls by the function block FB 510 ShowErrFB, the following interfaces are available at the block: EventID Error FB 510 ShowErrFB FB_ Table 3-1 Interfaces of FB 510 ShowErrFB Parameter Data type Initial value Description Input parameter EventID DWORD 0 The EventID is used to assign the error message by the ALARM_S message system. It is automatically assigned by STEP 7 when the block is integrated and must not be changed by the user. Error BOOL False This input signals an error. WORD 0 The includes the error code and is the reference to the error message to be displayed. If the Error input is set to True, the is transferred to the message system and a plaintext error message is displayed. Output parameter FB_ INT 0 If an error occurs during error message processing, an error code is output. V3.0 Issue 09/18/06 11/14
Operation of the Technology Template 3.3.2 FB 511 ShowErrDB For monitoring the technology objects by the function block FB 511 ShowErrDB, the following interfaces are available at the block: EventID TDB_Nr IgnoreWarnings FB 511 ShowErrDB FB_ Table 3-2 Interfaces of FB 511 ShowErrDB Parameter Data type Initial value Description Input parameter EventID DWORD 0 The EventID is used to assign the error message by the ALARM_S message system. It is automatically assigned by STEP 7 when the block is integrated and must not be changed by the user. TDB_Nr INT 0 The data block number of the technology object to be monitored or the technology data block assigned to this technology object has to be indicated as a reference. IgnoreWarnings BOOL False If this input is set to True, only error messages of the technology objects are displayed. Warning messages are suppressed. Output parameter FB_ INT 0 If an error occurs during processing the error message, this error is signaled via an error code. V3.0 Issue 09/18/06 12/14
Error Messages 4 Error Messages If an error occurs during processing the error codes in the blocks of the Error Messages technology template, this error is indicated at the FB_ output of the respective function block. The Ref. column indicates the block-internal error source of the function block of the Error Messages template. Table 4-1 Error codes of the Error Messages technology template FB_ Error Ref. Remark 0000 No error --- 0001 Accompanying value too SFC 18 The message is sent. long / no access to user memory 0002 Last free storage space SFC 18 for message acknowledgement is occupied 807F Internal error FB 511 Address of the DB data is outside the permissible address range 8081 Inadmissible EventID SFC 18 The indicated Event ID is outside the permissible range. 8082 No more resources available SFC 18 Loss of messages since the CPU has not enough resources for the generation of 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 identified SFC 18 The signal triggering the error message has the same value during the current and the previous SFC 18 call. V3.0 Issue 09/18/06 13/14
Error Messages FB_ Error Ref. Remark 8085 Invalid EventID SFC 18 The indicated EventID is not registered. 8086 Double SFC call SFC 18 An SFC call for the indicated EventID is already being processed in a lower priority class. 8087 Signal transferred with value 0 SFC 18 The signal triggering the error message had the value 0 during the first call of SFC 18. 8088 Double EventID SFC 18 The indicated EventID is already occupied by another system resource. 80A1 Error in DB number SFC 24 The indicated DB number has the value 0 or exceeds the maximum DB number possible for the CPU. 80B1 DB not available SFC 24 The DB with the indicated number does not exist on the CPU. 80B2 Unlinked DB SFC 24 The DB was created with the keyword UNLINKED. 817F Internal error FB 511 Incorrect data block type detected or data block type is not supported by the template. V3.0 Issue 09/18/06 14/14