Preface, Contents Introduction 1 Scope of Functions ProTool/Pro Runtime 2 Product Description 3 User’s Guide Requirements for Commissioning 4 Commissioning ProTool/Pro Runtime 5 Operating ProTool/Pro Runtime 6 Recipes 7 System Messages A SIMATIC HMI Documentation B SIMATIC HMI Glossary, Index 6AV6594–1CA05–2AB0 Release 12/99
Trademarks The registered trademarks of Siemens AG are listed in the Preface. Some of the other designations used in these documents are also registered trademarks; the owner’s rights may be violated if they are used be third parties for their own purposes. Impressum Editor and Publisher: A&D PT1. Copyright Siemens AG 1999 All rights reserved Disclaimer of Liability The reproduction, transmission or use of this document or its contents is not permitted without express written authority.
Preface This manual The ProTool/Pro Runtime User’s Guide is a part of the SIMATIC HMI documentation. It describes: S S S commissioning the ProTool/Pro RT runtime software downloading the configuration operating the configuration The description is applicable for the following Windows-based systems: S S S OP 37/Pro SIMATIC Panel PC FI 25, FI 45, PC 670, PC 670T Standard PC An overview of the entire SIMATIC HMI documentation is provided in Appendix B.
Preface Conventions The following conventions are used in this User’s Guide: VAR_23 Text which appears on the screen is displayed in a typewriter font. This text includes: commands, file names, entries in dialog boxes and system messages. Tag Dialogs, and fields and buttons in the dialogs, appear in italics. File → Edit Series of menu items are linked by arrows. The entire path to the menu item is always specified. F1 Key names are written in a different typeface.
Preface Other support In the case of technical queries, please contact the Siemens representatives in the subsidiaries and branches responsible for your area.
Preface SIMATIC Customer Online Services SIMATIC Customer Support offers comprehensive additional information concerning SIMATIC products through its Online services as follows: S Up-to-date general information is provided – in Internet under http://www.ad.siemens.de/simatic – via the Fax-Polling under 08765–93 02 77 95 00 S Up-to-date product information and downloads for practical use can be found: – in Internet under http://www.ad.siemens.
Contents 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1 2 Scope of Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1 3 Product Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1 4 5 3.1 3.1.1 3.1.2 3.1.3 3.1.4 3.1.5 3.1.6 3.1.7 3.1.
Contents 6 Operating ProTool/Pro Runtime . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1 6.1 General Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1 6.2 Settings for the Runtime Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5 6.3 6.3.1 6.3.2 6.3.3 6.3.4 6.3.5 6.3.6 6.3.7 6.3.8 6.3.9 6.3.10 6.3.11 6.3.12 6.3.13 6.3.14 6.3.15 6.3.16 6.3.17 6.3.
Introduction 1 What is ProTool/Pro? SIMATIC ProTool/Pro is an easy-to-use, high-performance visualization software enabling the visualization of processes and runs under WindowsR 95/98, WindowsR 2000 and WindowsR NT 4.0. Modern automation concepts make great demands on process visualization. In particular, process control in the machine-oriented sector must be able to satisfy the demands made for high-performance and simple control of the processes.
Introduction Authorization If the SIMATIC ProTool/Pro RT runtime software is installed on a standard PC or a SIMATIC Panel PC, the corresponding authorization is required to enable unrestricted operation: PC: The authorization must be ordered separately. SIMATIC Panel PC: The authorization is supplied with the unit. No authorization is necessary for the Operator Panel OP 37/Pro because it is released by means of the hardware.
2 Scope of Functions The table below summarizes the scope of functions offered by ProTool/Pro RT. The values stated are maximum values that can be managed by the operating unit. These values are restricted by the size of the memory.
Scope of Functions Functions Message buffer volatile Capacity 1,024 message events Viewing event/alarm messages 4 Deleting 4 Print 4 Simultaneously queued message events (max.
Scope of Functions Functions Screens S S S S S Prompting Softkey icons 1) Dynamic attributes Show/hide objects TAB sequence Help text Fixed window 4 Limit monitoring Inputs/outputs 4 Conversion functions Inputs/outputs 4 Help text Lines/characters For messages 4 For screens 4 For screen objects Archiving Print functions Password protection S S S S S S S Input field Selection field Button Status button Switches Invisible button Slider controls Messages 4 Tags 4 Print screen 4 Dir
Scope of Functions Functions Communication SIMATIC S5 S S AS511 PROFIBUS–DP 4 4 SIMATIC S7/M7 S S S PPI (S7 protocol) MPI (S7 protocol) PROFIBUS–DP (S7 protocol) S S SIMATIC WinAC from Version 2 OPC (client/server) 4 4 4 4 4 OPC S Client/Server 4 SIMATIC 505 S S NITP PROFIBUS–DP 4 4 Connection to PLCs from other manufacturers Allen Bradley (PLC-5, SLC 500) S S S DF1 DH+ DH485 4 Mitsubishi FX 4 4 4 Telemecanique TSX S S 1) 2) 3) 4) Adjust Uni-Telway 4 4 Not for standard PC and
Product Description 3 Area of use The SIMATIC ProTool/Pro RT runtime software shows its strengths wherever a dedicated hardware visualization configuration has reached its limits. SIMATIC ProTool/Pro RT can run on the following Windows-based systems under WindowsR 95/98, WindowsR 2000 and WindowsR NT 4.0 operating systems: S S S Operator Panel OP 37/Pro SIMATIC Panel PC, e.g.
Product Description The screen object Recipe view enables easy and quick handling of recipes and data records with a minimum of process configuration requirements. A specific system can be mapped in Recipe screens and the user interface individually laid out for editing data records. The configuration software is now even easier to use. Readily available screen objects, e.g.
Product Description 3.1 Brief Description of Various Objects in a Configuration Objects in a configuration A ProTool/Pro project is mainly comprised of screens with which to operate and monitor a machine or plant. It is also possible to configure more objects, such as messages, archives, recipes and scripts. Links are established to the PLC is made by means of tags. The operating unit displays values from the PLC and accepts values entered manually. 3.1.
Product Description Screen object Description Symbolic output field A symbolic output field displays current values from the PLC as plain text. Example Instead of the values 0 and 1 the symbolic output field displays the texts Motor OFF and Motor ON. List box The list box is used to enter a value selected from a list, not physically entered character by character. This enables a motor to be switched on and off using the two entries ON and OFF.
Product Description Screen object Status button Description A Status button is a display and operating element which has one of two states: Touched and Untouched. The states can be indicated by means of text or graphics. The Status button can be configured to be locking (switch function) or non-locking (keying function). Switch A switch serves to enter and display a binary status. It can only be switched on or off.
Product Description Screen object Description Status/Force Status/Force enables direct access to values in the connected PLC (SIMATIC S5 and SIMATIC S7) via the operating unit and to read and write them. PLC operands can be monitored and changed without having to connect an additional programming unit or PC to the PLC. This is particularly useful during the testing and commissioning phase of your configuration.
Product Description 3.1.2 Messages Message classes Messages indicate control-process events and states on the operating unit. ProTool/Pro differentiates between the following message categories: Event Messages indicate a status in the process, for example, Motor ON. Event messages are configured. Alarm Messages indicate an equipment failure, for example, Motor temperature too high. Alarm messages are configured. Alarm messages must be acknowledged due to their critical nature.
Product Description Display messages The events stored in the message buffer can be displayed according to different criteria. The following predefined objects are available for display purposes: Message line (refer to Page 6-12) Message window (refer to Page 6-12) Message page (refer to Page 6-14) Message buffer (refer to Page 6-15) Message view – Message view with full functionality (refer to Page 6-16) – Simple message view with restricted functionality (refer to Page 6-17) 3.1.
Product Description 3.1.4 Functions Purpose The ProTool/Pro CS configuration software provides a range of functions which can be used in a project. Functions serve to: set up the process on a process-specific basis control the process utilize properties of the operating unit define system settings on-line on the operating unit Using functions Functions are linked to objects within the project, e.g. to buttons, keys, fields or screens.
Product Description 3.1.6 Archiving Purpose Different archives can be set up for message events and tags: Message events these relate to arriving, departing and acknowledging in the case of alarm messages Tags these can be assigned to a previously defined archive during configuration. During the process, it is necessary to specify when the value of the tag should be written to the archive. Alternatively, it is possible to specify the name of a file or an existing database for the archives.
Product Description The following example emphasizes the necessary steps when using MS Access: Step 1 Procedure Configuring the archive in ProTool/Pro CS Select the Archive dialog, Settings tab, Database memory location for the archive to be stored in a database. Enter the name in Data Source Name under which the archive should be registered. Enter the size of the archive and select the option FIFO buffer.
Product Description 3.1.7 Protocols Application Protocols are used to document process data and completed production cycles. The ProTool/Pro CS configuration software defines the content and layout of the various protocols and configures the event which should trigger protocol printout. In this way, for example, it is possible to configure a protocol which is printed at the end of a shift in order to document non-production times.
Product Description 3.1.8 Scripts Purpose ProTool/Pro CS provides an interface for scripting with Microsoft Visual Basic Script (VB Script). The VB scripts can be used to extend the configuration software by adding customized functions. VB scripts are used similarly to functions. Documentation The detailed Microsoft documentation on VB scripts is contained within the scope of the ProTool/Pro CS configuration software supplied.
Product Description 3.
Product Description Table 3-1 ProTool/Pro RT connection options, continued OPC 6) S Client/Server Allen Bradley via DF1, DH+ (KF2) and DH485 (KF3) S PLC-5 S SLC 500 Mitsubishi S FX Telemecanique via Adjust and Uni-Telway S TSX 1) Special function block required (see User’s Guide entitled Communication for Windows-based Systems) 2) ProTool/Pro RT is an active node; communication takes place using the S7 protocol 3) Refer to Catalog ST70 4) Only with WindowsR NT 5) Special application required (see Use
Product Description 3-16 ProTool/Pro Runtime User’s Guide Release 12/99
Requirements for Commissioning 4 Which components do you need? The SIMATIC ProTool/Pro CD contains both the configuration software for all operating units and the runtime software to run the configuration. If the configuration should be run on an operating unit without the runtime software being installed at the factory (e.g. PC or SIMATIC Panel PC), both the runtime software and the authorization must have been installed on the system beforehand.
Requirements for Commissioning 4.1 Scope of Delivery Operating units supported SIMATIC ProTool/Pro supports all SIMATIC operating units and Windows-based PCs. These operating units are divided into the following groups: S Text Displays TD 17 S Text-based display operator panels OP 3, OP 5, OP 7, OP 15A, OP 15C, OP 17 S Graphic display operator panels OP 25, OP 27, OP 35, OP 37 S Touch panels TP 27-6, TP 27-10, TP 37 S Windows-based systems – TP 170A, MP 270, OP 37/Pro – SIMATIC Panel PCs, e.g.
Requirements for Commissioning 4.2 System Requirements for PCs Operating system SIMATIC ProTool/Pro RT can be run under the following operating systems: S S S S S MicrosoftR WindowsR 95 with Service Pack 1 (Build 950a) or higher MicrosoftR WindowsR 95 OSR 2 (Build 950b) or higher MicrosoftR WindowsR 98 MicrosoftR WindowsR 2000 MicrosoftR WindowsR NT 4.0 with Service Pack 4 or 5 Note Service Pack 1 must not be installed on a Windows 95R OSR 2 (Build 950b) or higher.
Requirements for Commissioning Hardware The PC hardware must fulfill the following requirements in order to operate the ProTool/Pro RT runtime software: WindowsR 95/98 Minimum Rec. Hardware WindowsR NT 4.0 Minimum Rec.
Requirements for Commissioning 4.3 Electrical Installation Connecting an OP 37/Pro to the PLC The OP 37/Pro is connected to the PLC via the IF1A or IF1B interface. The interface to be used depends on the design (RS232, RS422 or RS485). Table 4-1 indicates which PLC can, in principle, be connected to which interface of the OP 37/Pro. For more detailed information on this, please refer to the OP 37/Pro Equipment Manual.
Requirements for Commissioning Connecting a PC to the PLC The PC is connected to the PLC via one of the interfaces COM1 to COM4. Please refer to the hardware manual provided by the manufacturer for instructions on how to carry out electrical installation of your PC. A communications processor is required to connect the PC to SIMATIC S7. Table 4-2 indicates which communications processors are approved for use with the PC.
Commissioning ProTool/Pro Runtime 5 Initial startup The procedure for commissioning is dependent on whether the operating unit is a ready-to-operate unit with the runtime software installed at the factory (e.g. OP37/Pro, FI 25, FI 45) or a PC on which the runtime software must be installed by the user. S Ready-to-operate SIMATIC operating unit The ready-to-operate SIMATIC operating units are those in which the operating system and ProTool/Pro RT runtime software are fully installed at the factory.
Commissioning ProTool/Pro Runtime Procedure The initial commissioning is organized into three steps. Not all the steps described below are relevant to all the operating units. Step Procedure Operating unit 1 Install and configure the WindowsR operating system (Chapter 5.1) PC 2 Install the ProTool/Pro RT runtime software (Chapter 5.2) PC Download, test and start the project (Chapter 5.
Commissioning ProTool/Pro Runtime 5.1 Installing and Configuring Windows The following instructions describe the procedure for installing and configuring WindowsR. These steps are necessary for the ProTool/Pro RT runtime software to run correctly. Make a note of all the settings so that the runtime software can be run if the operating unit hard disk needs to be replaced for any reason.
Commissioning ProTool/Pro Runtime Step Procedure Define the following settings to enable messages to be printed line by line: For WindowsR95/98: The Forward print jobs to printer option must be set under printer properties. To do this, select the Properties dialog of the printer. Click the Spool Settings button on the Details tab. The dialog Settings for printing in background opens, in which to select the Print directly to the printer option.
Commissioning ProTool/Pro Runtime 5.2 Install ProTool/Pro RT Note Chapter 5.2 is only relevant for operating units in which the runtime software has not been installed at the factory (e.g. PC 670 or PC). 5.2.1 SIMATIC Panel PC 670 and PC 670T Installation All the files required to install the runtime software are already contained in the Backup directory on the operating unit hard disk. An installation CD is not necessary.
Commissioning ProTool/Pro Runtime 5.2.2 PC Without Runtime Software Condition The ProTool/Pro RT runtime software is contained on the SIMATIC ProTool/Pro CD. The runtime software requires a license to be able to run it. This must be ordered separately. If no license has been ordered, ProTool/Pro RT can only run in Demo mode. When running in Demo mode, a message appears at regular intervals stating that the runtime software is not licensed.
Commissioning ProTool/Pro Runtime 5.2.3 Communication Connection to the PLC ProTool/Pro RT supports communication with the PLCs listed in 3.2. Connect the operating unit to the PLC in order that the project can also be tested when connected to the PLC. The simulator can also be started to test the project (Page 5-11). In this case, there is no need for a connection to the PLC.
Commissioning ProTool/Pro Runtime 5.3 Retrofitting a Communication Processor Purpose The steps described below are only necessary if a CP5511 or CP5611 communication processor is retrofitted to enable connection to a SIMATIC S7. Recommended procedure First, install the runtime software before installing the communications processor. Proceed as follows: Step Procedure 1 Install the Runtime software. 2 Switch off the operating unit. 3 Slot in the communications processor.
Commissioning ProTool/Pro Runtime 5.4 Settings for the OP 37/Pro Settings in BIOS Different settings must be defined in the BIOS of the OP 37/Pro, according to the connection used. In the case of serial connections, the corresponding COM interface must be activated. Detailed information on this is provided in the OP 37/Pro Equipment Manual, Communication for Windows-based Systems User’s Guide and in the online help for the ProTool/Pro CS configuration software.
Commissioning ProTool/Pro Runtime Configuration software and runtime software are on the same PC Create the project, for example, under the name Myproject.pdb, and then compile it. Once compilation has been completed, a compiled file with the extension *.fwd is stored in the same directory as the project file (for example, Myproject.fwd). Double-click this file to start the ProTool/Pro RT runtime software with this compiled project.
Commissioning ProTool/Pro Runtime 5.5.2 Simulation of a Project Function The scope of delivery in respect of the ProTool/Pro RT runtime software contains a simulator with which to test the project without a PLC. The simulator is a separate application. It enables the user to test whether the screens, screen objects, messages, etc. which have been configured function correctly. The simulator simulates the PLC and S modifies the values of configured tags in a definable way: e.g.
Commissioning ProTool/Pro Runtime Note S Not all the configured tags are provided in the simulation table. Only referenced tags are available for the simulation, i.e. only those tags used in the project e.g. in a screen object. S Since the simulator can only simulate the project offline, i.e. without a connection to the PLC, the data formats are converted to internal ProTool/Pro CS formats. Therefore, PLC-specific data formats cannot be realized.
Commissioning ProTool/Pro Runtime Operate simulator The following instructions provide a detailed description of the procedures for operating the simulator. Table 5-1 Simulator operation, step-by-step Step Procedure 1 Start the simulator directly from the running configuration software by clicking on the icon depicted or via menu options File → Test → Start Simulator. 2 When the project is simulated for the first time, the simulator is stated with a new, empty simulation table.
Commissioning ProTool/Pro Runtime Table 5-1 Simulator operation, step-by-step, continued Step 6 Procedure Use the Simulation column to specify the manner in which the value of the tag is to be simulated: S Sinus The value of the tag is changed in the form of a sine curve. S Random The value of the tag is changed via a random function. S Incrementation The value of the tag is continuously increased up to a specified maximum value.
Commissioning ProTool/Pro Runtime Example of a simulation The example in Figure 5-2 uses a sine curve to illustrate how the values of a tag are written into the configuration in accordance with the settings in the simulator.
Commissioning ProTool/Pro Runtime 5.6 Starting a Project Running a project in online operation Once a project has been created, there are a number of different options with which to start it. A condition for this is that the compiled project is initially downloaded to the target system in cases where the configuration computer is not simultaneously the target system. S Double-click on the *.fwd file generated. In this way, the ProTool/Pro RT runtime software is started with the selected file.
Commissioning ProTool/Pro Runtime 5.7 Further Downloading Options Set up direct cable connection A direct cable connection between PCs enables the transfer of files from one PC to another. This method of data transfer can also be used to download a compiled project file. A direct cable connection must be set up on both computers to be connected. The parallel cable required for the direct cable connection can be purchased from Siemens.
Commissioning ProTool/Pro Runtime Table 5-2 Step 10 Setting up a direct connection on the runtime PC, continued Procedure Now enable one of the drives or a directory, for example c:\ptproj, so that it can be accessed by the configuration PC. To do this, select the desired directory in the Windows Explorer. Click the right mouse button to open the context menu and select the Enable menu item. Enter an enable name, for example PTProj.
Commissioning ProTool/Pro Runtime Table 5-3 Setting up a direct connection on the configuration PC, continued Step Procedure 8 Use Windows Explorer to link a drive with the directory provided on the runtime PC (e.g. D:\). To do this, select the Explorer menu option Options → Connect Network Drive. In this case, it is possible to connect a drive with a network path enabled on the runtime, e.g. \OP37Pro\PTProj.
Commissioning ProTool/Pro Runtime 5-20 ProTool/Pro Runtime User’s Guide Release 12/99
6 Operating ProTool/Pro Runtime 6.1 General Operation Overview The operation of processes during runtime is dependent on the project created. This chapter only contains general information regarding settings for the runtime software and controlling predefined screen objects. Screen objects provide the user with general system functions. Screen objects can be used in screens implemented in a project and configured according to individual requirements.
Operating ProTool/Pro Runtime S Use the Enter key – to apply values (e.g. in input fields) – to open list boxes S Use the ESCAPE key to cancel input. S Use the Tabulator key to access the next screen object which can be acted upon according to the configured tabulator sequence. By pressing it simultaneously with the SHIFT key, access is made in the reverse sequence. S In order to navigate between screens, for example, the function keys depicted on the right can be assigned functions, e.g.
Operating ProTool/Pro Runtime Table 6-2 Operating Windows via the keyboard, continued Navigation Operating unit Display the properties of the marked element Explorer: Change folders Change display area Activate menu bar Dialogs: Continue to next field Return to previous field Open next tab Open previous tab Call help text Help texts can be configured in ProTool/Pro CS for messages, screens and operable screen objects.
Operating ProTool/Pro Runtime Language change The ProTool/Pro CS configuration software enables a project to be stored in numerous languages. Up to 32 of these editing languages can be loaded on the operating unit at any one time. It is possible to switch between the languages loaded on the operating unit online. Following a language change, all language-dependent texts are displayed in the new language. Language-dependent texts contain, e.g.
Operating ProTool/Pro Runtime 6.2 Settings for the Runtime Software Displaying the configuration on the target system The ProTool/Pro CS configuration software can be used to define how the compiled project is represented during runtime. The project can be displayed in full screen mode or in a window which is smaller than the screen. In full screen mode, the project takes up the entire screen. The screen no longer contains a window and control elements (e.g. buttons).
Operating ProTool/Pro Runtime Cursor control compatibility (not PC) The type of cursor control, e.g. within tabular structured screen objects (message view, recipe view and status/force), can be configured. In this case, select menu option System → Settings in the ProTool/Pro CS configuration software and use the Settings dialog to activate or deactivate the option Cursor Control as with V 5.10.
Operating ProTool/Pro Runtime 6.
Operating ProTool/Pro Runtime 6.3.1 Button Purpose A button is a virtual key on the operating unit screen that can be operated by the mouse or via the touch screen, according to the system. Functions which have been assigned to buttons can be triggered, for example, by the following, configurable events: S S S Clicking Pressing Releasing S Labeling Buttons can be labeled statically or dynamically.
Operating ProTool/Pro Runtime 6.3.2 Status Button Purpose The Status button is an operating and display element with the two states, ON and OFF. Status buttons indicate the status of a device which cannot be determined from the operating unit (e.g. a motor). At the same time, it is also possible to change the status of the device concerned on the operating unit.
Operating ProTool/Pro Runtime 6.3.3 Switches Purpose A switch serves for the input and out of a binary status. It can only be switched on or off. It is linked to a tag to do this. The status OFF corresponds to the value 0 (a logical FALSE) of the tag linked to the switch. All tag values other than zero (a logical TRUE) are interpreted as the status ON.
Operating ProTool/Pro Runtime 6.3.4 List Box Purpose Values are entered in a list box by selection from a list provided (Figure 6-4), not character-by-character. Figure 6-4 List box in opened state (example) Control S Mouse and touch screen Click the mouse pointer in the list box or touch it on the operating unit touch screen. In this case, the selection list opens up immediately. After selecting an element from the list, the selection list is closed and the selected text appears in the list box.
Operating ProTool/Pro Runtime 6.3.5 Message Line Purpose A configured message line is always present, irrespective of the screen selected. The message line displays the last alarm or event message received. Display priorities Alarm messages have priority over event messages. If there are no alarm messages, or they have all been acknowledged, the event messages are displayed. Alarm messages flash to distinguish them from event messages. 6.3.
Operating ProTool/Pro Runtime Significance of the buttons Call help text Use this button to call in the help text configured for the selected message. Edit message Use this button to trigger the function assigned to the Edit Message event for the selected message. Acknowledge alarm messages Use this button to acknowledge an alarm message that has not yet been acknowledged.
Operating ProTool/Pro Runtime 6.3.7 Message Page Purpose The message page displays all queued messages with time stamp. It is possible to configure how the alarm messages are sorted. It is also possible to select whether the latest or oldest message is displayed first. An open message page is constantly updated.
Operating ProTool/Pro Runtime 6.3.8 Message Buffer Purpose The message buffer displays all message events with time stamp. It is possible to configure how the alarm messages are sorted. It is also possible to select whether the latest or oldest message is displayed first. An open message buffer is constantly updated.
Operating ProTool/Pro Runtime 6.3.9 Message View Purpose Specific views of the message buffer (volatile or archive) are defined in the message view. Various filter criteria are available in ProTool/Pro CS for this purpose. Structure The message view (Figure 6-8) displays messages that are queued on the operating unit or still have to be acknowledged. The message view also enables acknowledgement of these messages. Alternatively, the message view can also display a history of message events.
Operating ProTool/Pro Runtime Message categories In order to be able to distinguish between the different message categories, they are marked in the first column of the message view: ! Alarm messages blank Event messages $ System messages S7 S7 messages Column properties When correspondingly configured, the column sequence and sorting within each column can be modified during runtime. 6.3.
Operating ProTool/Pro Runtime 6.3.11 Bar Graph Purpose Bar graphs present a value in the form of a rectangular area. This makes it possible to recognize how far the current value is from the limits or whether a specified setpoint has been reached by a single glance at the operating unit. Bar graphs can be used to display fill levels or quantities, for example.
Operating ProTool/Pro Runtime 6.3.12 Trend Display Purpose The trend display is a particularly clear form of displaying process data in a continuous manner. In the case of processes that only change slowly, the trend display can visualize events that have already occurred and provides access to, and estimate of trends in the process sequence. On the other hand, data issued concerning processes which run quickly can be easily evaluated using this form of trend display.
Operating ProTool/Pro Runtime Button Function Start/Stop update Interrupts updating of the trend display until the button is pressed again. Return to start Jumps back to the start of trend recording. Scroll back Scrolls back one window width. Scroll forward Scrolls forward one window width. Enlarge zoom area Extends the trend display horizontally. Reduce zoom area Compresses the trend display horizontally.
Operating ProTool/Pro Runtime 6.3.13 Slider Control Purpose Use a slider control to enter and display numerical values in analog form. To enter values, move the slider to the required position. When used as a display element, the value is represented by the position of the slider. Function The slider control is linked to a tag. On moving the user-controlled slider, the corresponding value is written to the tag.
Operating ProTool/Pro Runtime 6.3.14 Analog Display Purpose An analog display indicates numerical values as a pointer instrument. Up to three areas can be set up on the instrument dial, each with a different color background. This enables visualizing different operating modes, e.g. normal operation, warning area and danger area. Function The analog display is linked to a tag. When the tag value changes, the pointer position changes correspondingly.
Operating ProTool/Pro Runtime 6.3.15 Date/Time Purpose The screen object Date/Time displays the current values for the time and/or date. If appropriately configured, these details can be changed online. The calendar date and time values are synchronized with the system values of the operating system. The operating unit accesses these values in order, for example, to assign a time stamp to message events. Format The format of the date and time depends on the language currently set.
Operating ProTool/Pro Runtime 6.3.16 Digital/Analog Clock Purpose The digital/analog clock provides the option of displaying the system time in numbers (digital) or as a clock with hands (analog). The digital display also includes the current date. The display format is language dependent. It is based on the format defined by the operating unit operating system. Display The digital/analog clock is purely a display element. This means that the date and time cannot be set using the operating unit.
Operating ProTool/Pro Runtime 6.3.17 Password List Purpose While the system is being configured using ProTool/Pro CS, operating elements can be protected against unauthorized use by means of passwords. In this way, important parameters and settings can only be changed by authorized personnel. Password hierarchy Hierarchically defined password levels from 0 to 9 exist for password protection purposes.
Operating ProTool/Pro Runtime S Configured logout time elapsed If the operating unit is not operated within the period of time configured (logout time), the current password level is automatically reset to 0. S Manual logoff If the function Logoff_user is linked to an operating element in the project, it can be used to reset the current password level to 0.
Operating ProTool/Pro Runtime 6.3.18 Status/Force Purpose The operating unit can be used to access values in the PLC connected (SIMATIC S5 and SIMATIC S7) online, directly, and to read and write them. This means PLC operands can be monitored and changed in a simple manner without having to connect an additional programming unit or PC to the PLC. This option is particularly useful during the testing and commissioning phase of the project.
Operating ProTool/Pro Runtime Table 6-4 Status/Force: Significance of the columns and buttons Column/Button Function Connection Select the PLC whose address range is to be displayed and/or changed. Type, DB Number, Offset, Bit Specify the address in these columns. Data Type, Format The format of the output is defined in these columns. Status Value The operating unit displays the value read from the PLC in this column. Control Value Enter the value to be written to the PLC in this column.
Recipes 7.1 7 Overview Purpose The purpose of recipes is to transfer of quantities of related data together and synchronously from the operating unit to the PLC and back again.
Recipes Principles of operation Using the example of the filing cabinet (Figure 7-1), the two terms Recipe and Data Record should be defined because they are important for subsequent understanding of the process.
Recipes S Recipe Recipes correspond to the individual drawers of the filing cabinet illustrated (e.g. grapefruit or lemon). The reference value fields (tags) belonging to the particular recipe are defined in each drawer. The recipe defines the data structure in ProTool/Pro CS. This structure cannot be subsequently modified on the operating unit. S Data record Data records correspond to the filing cards in the individual drawers of the cabinet (e.g. Drink, Juice and Nectar).
Recipes 7.2 Recipe Configuration Basic procedure The basic steps to configuring a recipe are listed below: 1. Define the structure of the recipe: Assign tags to the recipe structure. These tags are provided with entries from the data records. Define a name for the recipe. This name is used to select the recipe in the project and on the operating unit. 2.
Recipes System limits The table provides an overview of the system limits for recipes according to the units. Elements Target device OP37/Pro PC, Panel PC Number of recipes 255 255 Data records per recipe 5000 1) 5000 1) Total entries 5,000 5,000 Entries per recipe 2,048 2) 1) Dependent on storage medium used. 2) Dependent on the number of licensed power tags. Power tags are tags linked to a process.
Recipes 7.3 Editing Data Records In this chapter This chapter provides information on how to edit data records on operating unit.
Recipes 7.3.1 Recipe View Purpose The recipe view is typically used to edit recipe data records in tabular form. This provides an uncomplicated method of displaying, creating, copying, modifying, deleting and downloading data records. All descriptions on editing data records provided in this Chapter 7.3.1 relate purely to the use of the recipe view. Information on editing data records in recipe screens is provided in Chapter 7.3.2.
Recipes Significance of the operating and display elements No. Function Select recipe If the corresponding function is enabled in ProTool/Pro CS, it is possible to select a configured recipe in this selection field. The number of the selected recipe is displayed to the right of the selection field. This number is only relevant during the configuration. It cannot be modified on the operating unit.
Recipes No. Function Write data record in the PLC This button is used to write the current data record values in the PLC. Key combinations: Status bar The operating unit displays the status of the current operation in this line, e.g. Downloading. Note S If the two options Synchronize Tags and Tags Offline are activated in the project, the values from the table are applied when values in the tables and screens are changed simultaneously.
Recipes Displaying data records Proceed as follows to display data records on the operating unit data medium: Step 1 Select recipe Procedure Step 1 is only possible when recipe selection has been configured. S Select the selection field for the configured recipes (Position 1 in the figure on Page 7-7). S Open the selection field and mark the required recipe in the opened selection list. S Confirm the selection.
Recipes Note The data storage location for the new data record can be configured. The following settings are possible, depending on the destination device: S any path and any drive S internal flash S storage card (PC card) Copying data records In order to copy data records, save them under new names.
Recipes Changing data records Proceed as follows to change existing data records: Step 1 2 Procedure Select recipe and data record S Select the required recipe and the data record to be changed Change values S Change the setpoint value in the table (Position 3 in the as described in Steps 1 and 2 on Page 7-10. figure on Page 7-7). The entry names cannot be edited on the operating unit. 3 Save data record S Press the keyy depicted on the left.
Recipes Renaming data records Proceed as follows to rename existing data records: Step 1 2 Procedure Select recipe and data record S Select the required recipe and the data record to be copied Enter data record name S Enter a new data record name in the selection field for data as described in Steps 1 and 2 on Page 7-10. records (Position 2 in the figure on Page 7-7). S After entering the data record name, the next free data record number is automatically entered on the right.
Recipes Reading data records from the PLC Proceed as follows to update data records in the operating unit working memory with values from the PLC: Step 1 Select recipe Procedure S Select the required recipe, as described in Step 1 on Page 7-10. 2 Read values S Press the keyy depicted on the left. S The current values are read from the PLC and displayed. 3 Edit data records S The data can then be edited, e.g. values modified, saved, downloaded to PLC, etc.
Recipes 7.3.2 Recipe Screens Purpose Recipe screens are typically representations of the system. The screens provide display and operating elements with which to create, save, modify, delete and download data records. Large recipes can be split into several topic-specific screens and clearly displayed, e.g. with graphic elements. Components for editing data records In order to be able to edit data records in recipe screens on the operating unit, the corresponding components, e.g.
Recipes Step Procedure 1 Select a data record. 2 Trigger reading of the selected data record from the storage medium: S With recipe view It is automatically loaded on selecting the data record. S Without recipe view Activate the operating element linked with the Load_Data_Record function. The function parameters must have been set accordingly beforehand. 3 The data of the data record is written to the tags. 4 Edit the tags using the configured input/output fields. 5 Save the modified tags.
Recipes Step 5 Procedure Save the modified tags. S With recipe view Click the Save button. If necessary, you must first specify a new name. S Without recipe view Activate the operating element linked with the Save_Date_Record. The function parameters must previously have been set accordingly. Note When editing data records online, the entered values are transferred to the PLC without synchronization.
Recipes 7.3.4 Import/Export Data Records Purpose When the appropriate features have been configured, data records on the operating unit can be exported as CSV files to the data medium. This feature can be used to edit data records with external tools, e.g. with a spreadsheet program or text editor, and import them on the operating unit again.
Recipes Export/Import all data records in a recipe When appropriately configured, all the data records in a recipe can be imported/exported together. The CSV file for the example on Page 7-3 then appears as follows: Orange;Drink;Juice;Nectar 3;1;2;3 Var_2;90;95;70 Var_3;10;5;30 Var_4;1.5;0.5;1.
Recipes Exporting, editing and importing data records Proceed as follows in order to export data records on the operating unit in a CSV file, edit it using with an external tool (e.g. spreadsheet program or text editor) and mport it back on the operating unit: Step 1 Export data record Procedure S Press the operating element linked with the Export_Data_Records function (e.g. function key or button).
Recipes 7.3.5 Reaction on Changing the Recipe Structure Standard behavior The following section describes the standard behavior of the operating unit when it detects differences between the data record structure stored on the data medium and the recipe structure currently loaded on the operating unit. Load and export data records, and write in the PLC S The data record on the data medium contains additional tags: The values are rejected.
Recipes 7-22 ProTool/Pro Runtime User’s Guide Release 12/99
System Messages A In this chapter This chapter contains a selection of important system messages for Windows-based systems. The table indicates when the messages occur and how they, or their cause, can be cleared. Not every message is relevant for each operating unit. Message number Operating unit system messages can be divided into various categories.
System Messages The message category enables the identification of a general area in which the cause of the fault is to be found. Note System messages are issued in the language currently set on the operating unit. System message parameters The system messages may contain parameters which are not decoded for the user but which are relevant in respect of the cause of an error since they provide a reference to the source code from ProTool/Pro Runtime.
System Messages Number Effect/Cause Remedy 20013 VBScript.dll is not correctly installed. Therefore, no scripts can be executed. Re-install ProTool/Pro RT. 20014 A value is returned by the script function which is not written in any configured return tag. Select the specified script in the configuration. Too many scripts have been triggered in quick succession. If more than 20 scripts are queued to be processed, any subsequent scripts are rejected.
System Messages Number 70011 Effect/Cause The system time could not be modified. This may be due to the following: S an impermissible time was transferred in the PLC job, S the Windows NT user has no user rights Remedy Check the time which is to be set. Under Windows NT: The user executing ProTool/Pro RT must be assigned the rights to modify the system time from Windows NT (administration/user manager, guidelines). to modify the system time.
System Messages Number 80012 Effect/Cause Remedy Archive values are stored in a buffer. If the values are read to the buffer faster than they can be physically written (e.g. using a hard disk), overloading may occur and recording is then stopped. Archive less values. 80013 The overload status no longer applies. Archiving resumes the recording of all values. – 80014 The same action was triggered twice in quick – succession.
System Messages Number 80024 Effect/Cause The function Copy_Archive is configured not to permit copying when the target archive already contains data (Parameter: Write mode). Remedy Modify the function Copy_Archive in the project, if necessary. Before initiating the function, delete the target archive. The archive is not copied. 80025 The copy action is interrupted. – Data written up to this point is retained. Deletion of the target table (if configured) is not executed.
System Messages Number 130002 Effect/Cause The action was not executed. Remedy Close other applications. Delete files no longer required from the hard disk. 140000 Online connection to the PLC has been successfully established. – 140001 Online connection to the PLC has been disconnected. – 140003 No tag updating or writing is executed. Check the connection and whether the PLC is switched on. Check the parameter definitions in the Control Panel using “Set PU/PC interface”. Restart the system.
System Messages Number 140008 Effect/Cause Remedy No tag updating or writing is executed because the configuration data is incorrect: Check the connection and whether the PLC is switched on. The following parameters could not be entered in the registry: Check the parameter definitions in the Control Panel using “Set PU/PC interface”. 0: 1: 2: 3: Restart the system. 4: 5: General errors Incorrect version Profile cannot be entered in the registry. Sub-network type cannot be entered in the registry.
System Messages Number 150000 Effect/Cause No more data is read or written. This can have various causes: S The cable is defective. S The PLC does not respond, is defective, Remedy Check that the cable is plugged in, the PLC is operational, the correct interface is used. Reboot the system if the system message is displayed continuously. etc. S Connection made to the wrong interface. S The system is overloaded.
System Messages Number Effect/Cause Remedy 170003 1) The display of an S7 diagnostics message is not possible. An internal error %2 has been reported. 170004 1) The display of an S7 diagnostics message is – not possible. An internal error with error class %2, error number %3 has been reported. 170007 1) It is not possible to read in the S7 diagnostics – buffer (SZL) because it was terminated with an internal error with error class %2 and error code %3.
System Messages Number 190010 Effect/Cause The tag is described with values too often (e.g. in a loop triggered by a script). Remedy Increase the time interval between the multi-writing tasks. Values are lost because the maximum of 100 event have been stored in the buffer. 190011 There are two causes for this message: S The value entered could not be written to Ensure that the value entered is within the the configured PLC tag because it was either above or below the value range.
System Messages Number Effect/Cause Remedy 200002 Coordination is not executed at present because the address format of the area pointer does not match the internal storage format. – (Internal error) 200003 Coordination can be executed again because the last error status has been eliminated (return to normal operation). – 200004 It is possible that coordination is not executed. – 200005 No more data is read or written. Check that the cable is connected and the PLC is in order.
System Messages Number Effect/Cause Remedy 220004 Communication is terminated and no update is executed because the cable is not connected or is defect etc. Check the connection. 220005 Communication is running. – 220006 The connection is established to the specified PLC via the specified interface. – 220007 The connection to the specified PLC at the specified interface is disconnected.
System Messages Number Effect/Cause Remedy 250000 The tag in the specified line in Status/Control is not updated because the address configured for this tag is not available. Check the set address and then check that the address has been set up in the PLC. 250001 The tag in the specified line in Status/Control is not updated because the PLC type configured for this tag is not available. Check the set address.
System Messages Number 280003 Effect/Cause Remedy A connection is used which requires a function module in the PLC. Check that the cable is plugged in, the PLC is operational, the correct interface is used. The function block does not reply. Reboot the system if the system message is displayed continuously. The remedy is dependent on the error code: 1: The function block must set the COM bit in the response container. 280004 The online connection to the PLC has been interrupted.
System Messages Number 290005 Effect/Cause This message is issued when message number 290002 is triggered more than five times. Remedy Check the value range or type of the variable. In this case, no further individual messages are generated. 290006 The threshold values configured for the tag have been violated by values entered. Observe the configured or current threshold value of the tag. 290007 There is a difference between the source and target structure of the recipe currently being processed.
System Messages Number 290022 Effect/Cause Acknowledgement that downloading of data records from operating unit to PLC has been terminated due to an error. Remedy Check the configuration: S have the tag addresses been set up in the PLC? S does the recipe number exist? S does the data record number exist? S has the function parameters “Overwrite”? 290023 Acknowledgement that downloading of data records from the PLC to the operating unit has started.
System Messages Number 290042 Effect/Cause An attempt was made to execute several downloads/memory functions simultaneously. Remedy Trigger the function again after waiting a short period. The last action was not executed. 290050 Acknowledgement that the exportation of data records has started. – 290051 Acknowledgement that the exportation of data records has been completed successfully. – 290052 Acknowledgement that the exportation of data records has been terminated due to errors.
System Messages Procedure in the case of “internal errors” Please proceed as follows in the case of all system messages related to “internal errors”: 1. Start up the operating unit again. 2. Download the configuration again. 3. Switch the operating unit off, stop the PLC and then restart both. 4. If the error occurs again, please contact the SIMATIC Customer Support. Make reference to the specified error number and message tags.
System Messages A-20 ProTool/Pro Runtime User’s Guide Release 12/99
SIMATIC HMI Documentation B Target groups This manual is part of the SIMATIC HMI documentation.
SIMATIC HMI Documentation Documentation Target Group Content First Steps with ProTool Newcomers This documentation guides you step by step through the configuration of Product Brief S a screen with various objects S changing from one screen to another S a message.
SIMATIC HMI Documentation Documentation Target Group Content Copy Protection Start-up Guide Commissioning engineers, Users The ProTool/Pro Runtime visualization software is a copyright product. This manual contains information on the installation, repair and uninstallation of authorizations. Application Example Newcomers ProTool is supplied with example configurations and the corresponding PLC programs.
SIMATIC HMI Documentation Documentation Target Group Content Communication Programmers Provides information on connecting text-based and graphics displays to the following PLCs: User’s Guide S S S S SIMATIC S5 SIMATIC S7 SIMATIC 500/505 drivers for other PLCs This documentation describes the S configuration and parameters required for connecting the devices to the PLC and the network S user data areas used for exchanging data between operating unit and PLC.
Glossary Acknowledgement Acknowledgement of an alarm message on the operating unit confirms that it has been noted. After acknowledgement, the message disappears from the operating unit. Alarm messages can be acknowledged either on the operating unit or PLC. Alarm messages can be compiled into groups so that several messages can be acknowledged simultaneously. Acknowledgement groups During configuration, several alarm messages can be compiled to form an acknowledgement group.
Glossary Area pointer Defines a memory area in the PLC for data exchange between the PLC and operating unit. Bar graphs Represent values from the PLC as rectangular areas. This is a way of displaying filling levels or workpiece numbers, for example, on the operating unit. Baud rate Rate of speed at which data is downloaded. Baud rate is specified in Bit/s. Blank Switch off or fade out the screen saver.
Glossary Data record Is a recipe containing data. A recipe can be comprised of several data records. When a data record is downloaded, all the assigned data is transferred to the PLC together and synchronously. Display period Defines whether and how long a system message is displayed on the operating unit. Download The transfer of run–capable project data to the operating unit. Connect the operating unit to the configuration computer with a standard cable beforehand.
Glossary Flash memory Programmable memory which can be electrically deleted and written to again segment–by–segment. Function key Key on the operating unit to which a configurable function can be assigned. A function key with a global function assignment always initiates the same function regardless of the screen currently open. A function key with a local function assignment (softkey) can have a different function for each screen. Global tag This is a process tag linked to the PLC.
Glossary Hidden buttons Buttons which are only visible during configuration, not on the operating unit. If hidden buttons are superimposed on components in the process screen, the respective components can be operated by clicking the button with the mouse or pressing them on the touch screen. Icon Pixel graphic of a fixed size, e.g. assigned to a softkey, to identify its function. Input field Enables the user to enter values which are subsequently downloaded to the PLC.
Glossary Message arrival Time at which a message was triggered by the PLC or operating unit. Message buffer Memory area on the operating unit in which message events can be stored in chronological order as they arrive. Event messages and alarm messages are stored in separate message buffers. Message departure Time at which a message was withdrawn by the PLC. Message events These are stored in chronological order in the operating unit message archive.
Glossary Object Is a component part of a screen or message. Depending on the object type, objects serve to display or enter texts and values on the operating unit. Operator Panel Operating unit which can be configured for operating and monitoring machines and systems. Output field Displays current values from the PLC on the operating unit. Password A character string which must be entered on the operating unit before a protected function can be activated. Each password is assigned to a password level.
Glossary PLC job PLC jobs can be used by the PLC to trigger functions on the operating unit, e.g. display a screen. Power–up test Checks the status of the CPU and memory each time the power is switched on. Print screen Printout of a copy of the screen contents. Process screen The display of process values and process progress on the operating unit in the form of screens, which may contain graphics, texts and values.
Glossary Recipe A combination of tags to a fixed data structure. The data structure configured can be assigned data on the operating unit and is then referred to as a data record. The use of recipes ensures that when a data record is downloaded, all the assigned data is transferred to the PLC together and synchronously. Remaining buffer Configurable size of the message buffer.
Glossary Softkey Function key on the operating unit with a local function assignment. The function triggered by a softkey varies according to the screen currently open. Start screen The first screen, which automatically appears after the unit has started up. Status button A status button is a display and operating element with two possible states: ON and OFF, i.e. touched and untouched. Both states can be configured for display with text or graphics, which then label the status button.
Glossary Tag A defined memory location in which values can be read from and written to. This can be performed from the PLC or via the operating unit. Depending on whether the tag is linked to the PLC or not, a distinction is made between “global” tags (process tags) and “local” tags. Trend curve Curve type by which just one curve value is read from the PLC per cycle or trigger resulting in a curve display.
Glossary Glossary-12 ProTool/Pro Runtime User’s Guide Release 12/99
Index A C Accepting, Status/Force, 6-28 Acknowledgement, alarm message, 6-13, 6-16 Acknowledgment groups, alarm message, 2-1 Activate multilanguage support, 5-4 Alarm message buffer, example, 6-15 Alarm message page, 6-14 Alarm messages, 2-1, 3-7, 6-12 acknowledge, 6-13, 6-16 ALARM_S, 3-7 Allen Bradley, 2-4, 3-15 Analog clock, 6-24 Analog display, 3-6, 6-22 Archive, configuring, 3-11 Archive storage CSV file, 3-10 Database, 3-10 Archiving, 2-3, 3-1, 3-10 Area of use, 3-1 Area pointer, simulation, 5-11 Aut
Index Conventions, Date/Time, 6-23 Conversion functions, 2-3 Convert, 3-2 Copy, 3-2 data records, 7-11 Copy protection, 5-6 Create, data record, 7-10 CSV file, 3-10, 7-18, 7-19 Cursor control, compatibility, 6-6 Cursor movement, 6-1 Cycle triggering, 6-19 D Data record change, 7-12 copy, 7-11 create, 7-10 definition, 7-2, 7-3 editing, 7-6 import, 7-21 number, 7-5 renaming, 7-13 save, 7-10 save as, 7-13 Data records deleting, 7-13 display, 7-10 downloading to PLC, 7-14 editing, 7-20 export/import, 7-18 exp
Index Filter criteria, Message display, 6-16 Flash, 7-4, 7-11 Flashing, messages, 6-12 Floppy disk drive, 4-4 Format Date/Time, 6-23 Status/Force, 6-28 Full screen mode, 6-5 Function extensions, 3-1 Function keys, 6-2 Functionality, 1-2, 2-1 Functions, 3-9 Data_Record_DAT_To_PLC, 7-17 Data_Record_PLC_To_DAT, 7-17 Data_Record_PLC_to_Tags, 7-15 Data_Record_Tags_to_PLC, 7-15 Display_event_message_window, 6-13 downloading data records, 7-15 Export_Data_Records, 7-17, 7-18, 7-20 Import_Data_Records, 7-17, 7-18,
Index Lines per message alarm messages, 2-1 event messages, 2-1 List, passwords, 6-26 List box, 3-4, 6-11 Literature, B-1 Local tags, 3-8 Logging in, 6-25 Logging off, 6-25 Login, 6-25 Logoff, 6-25 Logoff_user, function, 6-26 M Management, Password, 6-26 Maximum value, bar graph, 6-18 Message archive, 2-2, 3-7 Message buffer, 2-2, 3-8, 6-15 capacity, 2-2 print, 3-9 Message categories, 6-17 Message category, A-2 Message classes, 3-7 Message events, 2-2, 3-7 Message line, 3-8, 6-12 Message logging, 2-1, 2-2
Index Password protection, 2-3 Passwords, number of, 2-3 PC, connectable PLCs, 4-6 PC card, 7-4, 7-11 PLC connecting, 3-14 Connection, 4-2 simulation, 5-11 PLC jobs, 7-17 PLC operands, 6-27 Pointer instrument, 6-22 Polygon, 3-4 Polyline, 3-4 Positioning, 7-16 Power Tags, 4-1, 7-5 Pressing, event, 6-8, 6-9 Print message buffer, 3-9 Messages, 3-9 protocols, 3-9 Print functions, 2-3 Printing, 3-9 Process tags, 3-8 Process values alarm messages, 2-1 event messages, 2-1 Process visualization software, 1-1 Proce
Index Separator , 7-18 Service Pack, 4-3 Set up direct cable connection, 5-17 Password, 6-26 Set up program icon, 5-16 Settings Date/Time, 6-23 full screen, 6-5 OP37/Pro, 5-9 Runtime software, 6-5 Setup program, 5-5 Shift bit, 5-11 Shift report, 2-3 Show_alarm_message_buffer, Function, 6-15 Show_alarm_message_page, Function, 6-14 Show_event_message_buffer, Function, 6-15 Show_event_message_page, Function, 6-14 SIMATIC HMI documentation, B-1 SIMATIC Panel PC, 1-1 Simple message view, 3-5, 6-17 Simulation ex
Index V VB Script, 2-3, 3-1 VB script, tags, 3-8 Vector graphics, 3-4 View, Password list, 6-26 Virtual key, 6-8 Windows, 1-1 configuring, 5-3 install, 5-3 Windows–based systems, 1-1, 4-2 Writing, data records to PLC, 7-14 Z W WinAC, 2-4, 3-14 ProTool/Pro Runtime User’s Guide Release 12/99 Zoom, trend display, 6-20 Zoom area, enlarge/reduce (trend display), 6-20 Index-7
Index Index-8 ProTool/Pro Runtime User’s Guide Release 12/99
