- No category
advertisement
▼
Scroll to page 2
of 202
CL350 / CL400 / CL500 MMI-MADAP for Programmers and Project Designers Software manual Edition 101 CL350 / CL400 / CL500 MMI-MADAP for Programmers and Project Designers Software manual 1070 072 168-101 (98.04) GB 1997-1998 by Robert Bosch GmbH, Erbach / Germany All rights reserved, including applications for protective rights. Reproduction or distribution by any means subject to our prior written permission. Discretionary charge 30,- DM Contents I 1 1.1 1.2 1.3 1.4 1.5 Safety Instructions..................................................................................................................................... 1-1 Proper use ............................................................................................................................................. 1-1 Qualified personnel................................................................................................................................ 1-2 Safety markings on components ........................................................................................................... 1-3 Safety instructions in this manual .......................................................................................................... 1-4 Safety instructions for the described product......................................................................................... 1-5 2 2.1 Introduction................................................................................................................................................ 2-1 Overview of Functions ........................................................................................................................... 2-2 3 Suitable Controllers ................................................................................................................................... 3-1 4 MMI-MADAP PLC Software ...................................................................................................................... 4-1 4.1 Introduction ............................................................................................................................................ 4-1 4.2 Software Installation .............................................................................................................................. 4-4 4.2.1 Supplied Software .......................................................................................................................... 4-4 4.2.1.1 DISK.FB.MMIMADAP Diskette ................................................................................................... 4-4 4.2.2 Installing MMI-MADAP PLC Software ............................................................................................ 4-6 4.2.3 Linking Standard Symbol File and Standard Modules.................................................................... 4-8 4.2.4 Configuring Com-P and R500P PROFIBUS Cards........................................................................ 4-9 4.2.4.1 Com-P Card................................................................................................................................ 4-9 4.2.4.2 R500P Card ................................................................................................................................ 4-9 4.2.4.3 Installation Procedure ............................................................................................................... 4-10 4.3 PLC Program Components.................................................................................................................. 4-11 4.3.1 Organization Modules................................................................................................................... 4-11 4.3.2 Program Modules ......................................................................................................................... 4-11 4.3.3 Data Modules ............................................................................................................................... 4-12 4.3.4 System Configuration Table for CL500 ........................................................................................ 4-13 4.4 Principal Program Structure................................................................................................................. 4-14 4.5 Process Control ................................................................................................................................... 4-21 4.5.1 Definitions..................................................................................................................................... 4-21 4.5.2 Programming................................................................................................................................ 4-23 4.5.3 Operating Modes.......................................................................................................................... 4-27 4.5.4 Step module ................................................................................................................................. 4-38 4.5.5 Command Output ......................................................................................................................... 4-41 4.5.6 Cascade Data Module .................................................................................................................. 4-43 4.6 Machine Usage.................................................................................................................................... 4-45 4.6.1 Definitions..................................................................................................................................... 4-45 4.6.2 Programming................................................................................................................................ 4-46 4.7 Machine Cycle Times .......................................................................................................................... 4-51 4.7.1 Definitions..................................................................................................................................... 4-51 4.7.2 Programming................................................................................................................................ 4-51 4.8 Decoding BT100 Movement and Function Keys ................................................................................. 4-54 4.8.1 Definitions..................................................................................................................................... 4-54 4.8.2 Programming................................................................................................................................ 4-54 4.9 PROFIBUS-DP Diagnostics Principle.................................................................................................. 4-56 4.9.1 Definitions..................................................................................................................................... 4-56 4.9.2 Programming................................................................................................................................ 4-56 4.10 Operator Terminal Connectivity ........................................................................................................... 4-59 4.10.1 Definitions..................................................................................................................................... 4-59 4.10.2 Programming................................................................................................................................ 4-60 4.11 Processing Fault Diagnostics .............................................................................................................. 4-65 4.11.1 Definitions..................................................................................................................................... 4-65 4.11.2 Programming................................................................................................................................ 4-68 4.11.3 Storing Diagnostic Information ..................................................................................................... 4-69 4.11.4 Processing faults .......................................................................................................................... 4-75 1070 072 168-101 (98.04) GB II 4.12 4.12.1 4.12.2 Contents MMI-MADAP Multidiagnostic Concept................................................................................................. 4-77 Previous Diagnostic Concept ....................................................................................................... 4-77 Multiple Diagnostics...................................................................................................................... 4-78 5 Interfaces – PLC <-> Operator Terminals ................................................................................................. 5-1 5.1 Definition................................................................................................................................................ 5-1 5.2 List of Data Interfaces............................................................................................................................ 5-2 5.3 Description of User Data Interfaces....................................................................................................... 5-3 5.3.1 Data Modules DM1-64 – Cascade Data 1-64................................................................................. 5-3 5.3.2 Data Module DM217 – Machine Cycle Times ................................................................................ 5-4 5.3.3 Data Modules DM 218 & DB219 – Machine Usage ....................................................................... 5-5 5.3.4 Data Modules DM220 & DM221 – DESI-DP Diagnostics............................................................... 5-8 5.3.5 Data Modules – BT 1-4 Communication & Display Data.............................................................. 5-10 5.3.6 Data Modules – BT 1-4 Status Display Data ................................................................................ 5-16 5.3.7 Data Modules – BT 1-4 Movement Blocks ................................................................................... 5-17 5.3.8 Data Modules – BT 1-4 Diagnostic Results.................................................................................. 5-19 5.3.9 Data Module DM253 – I/O Assignment and SC Table ................................................................. 5-21 5.3.10 Machine Usage and PROFIBUS-DP Diagnostics ........................................................................ 5-24 5.3.11 Data Module DM255 – Global Operating Data............................................................................. 5-27 6 MMI-MADAP Operator Terminal ............................................................................................................... 6-1 6.1 Introduction ............................................................................................................................................ 6-1 6.2 System Requirements for MMI-MADAP Operator Terminal .................................................................. 6-2 6.3 Software Installation .............................................................................................................................. 6-3 6.3.1 Supplied Software Files.................................................................................................................. 6-3 6.3.2 MMI-MADAP................................................................................................................................... 6-3 6.3.2.1 Installation diskettes.................................................................................................................... 6-5 6.3.2.2 Installing MMI-MADAP from Set of Diskettes ............................................................................. 6-5 6.3.2.3 Configuring the Operator Terminal ............................................................................................. 6-9 6.3.3 Configuring Diagnostics................................................................................................................ 6-14 6.4 MMI-MADAP Directory Structure......................................................................................................... 6-15 6.5 Definition of MMI-MADAP Data Ranges.............................................................................................. 6-17 6.6 Online Project Design of Standard Functions ...................................................................................... 6-21 6.7 Designing User Screens ...................................................................................................................... 6-22 6.8 MMI-MADAP Merge Function.............................................................................................................. 6-29 6.8.1 Application database .................................................................................................................... 6-29 6.8.2 Screens ........................................................................................................................................ 6-32 6.8.2.1 Procedure for creating user screens......................................................................................... 6-32 6.8.2.2 Definitions ................................................................................................................................. 6-33 6.8.3 Defining Data Ranges .................................................................................................................. 6-33 6.8.3.1 Introduction ............................................................................................................................... 6-33 6.8.3.2 Alarm files ................................................................................................................................. 6-34 6.8.3.3 Math files................................................................................................................................... 6-34 6.8.3.4 Scheduler files .......................................................................................................................... 6-34 6.8.3.5 Trend files ................................................................................................................................. 6-34 6.8.3.6 Report files................................................................................................................................ 6-34 6.8.3.7 Recipe files ............................................................................................................................... 6-35 6.8.4 Communications........................................................................................................................... 6-35 6.8.5 Modifying the Application.............................................................................................................. 6-36 6.9 Screen List and Screen Numbers........................................................................................................ 6-38 6.10 Global Standard Variables................................................................................................................... 6-40 7 7.1 7.2 7.3 7.4 PROFIBUS-FMS Interface ........................................................................................................................ 7-1 Introduction ............................................................................................................................................ 7-1 Communication References .................................................................................................................. 7-2 Communication Objects......................................................................................................................... 7-3 Manipulating User Objects..................................................................................................................... 7-8 1070 072 168-101 (98.04) GB Contents III 8 8.1 8.2 8.3 BUEP19E Interface ................................................................................................................................... 8-1 Introduction ............................................................................................................................................ 8-1 Communication Objects......................................................................................................................... 8-1 Manipulating User Objects..................................................................................................................... 8-5 9 9.1 Appendix ................................................................................................................................................... 9-1 Index ...................................................................................................................................................... 9-1 1070 072 168-101 (98.04) GB IV Contents 1070 072 168-101 (98.04) GB Safety Instructions 1 1-1 Safety Instructions Before you start working with the MMI-MADAP, we recommend that you thoroughly familiarize yourself with the contents of this manual. Keep this manual in a place where it is always accessible to all users. 1.1 Proper use This instruction manual presents a comprehensive set of instructions and information required for the standard operation of the described products. The products described hereunder • were developed, manufactured, tested and documented in accordance with the relevant safety standards. In standard operation, and provided that the specifications and safety instructions relating to the project phase, installation and correct operation of the product are followed, there should arise no risk of danger to personnel or property. • are certified to be in full compliance with the requirements of the • COUNCIL DIRECTIVE 89/336/EEC of May 3rd 1989 on the approximation of the laws of the Member States relating to electromagnetic compatibility, 93/68/EEC (amendments of Directives), and 93/44/EEC (relating to machinery) • COUNCIL DIRECTIVE 73/23/EEC (electrical equipment designed for use within certain voltage limits) • Harmonized standards EN 50081–2 and EN 50082–2 • are designed for operation in an industrial environment (Class A emissions). The following restrictions apply: • No direct connection to the public low–voltage power supply is permitted. • Connection to the medium and/or high–voltage system must be provided via transformer. The following applies for application within a personal residence, in business areas, on retail premises or in a small–industry setting: • Installation in a control cabinet or housing with high shield attenuation. • Cables that exit the screened area must be provided with filtering or screening measures. • The user will be required to obtain a single operating license issued by the appropriate national authority or approval body. In Germany, this is the Federal Institute for Posts and Telecommunications, and/or its local branch offices. ⇒ This is a Class A device. In a residential area, this device may cause radio interference. In such case, the user may be required to introduce suitable countermeasures, and to bear the cost of the same. Proper transport, handling and storage, placement and installation of the product are indispensable prerequisites for its subsequent flawless service and safe operation. 1070 072 168-101 (98.04) GB 1-2 Safety Instructions 1.2 Qualified personnel This instruction manual is designed for specially trained personnel. The relevant requirements are based on the job specifications as outlined by the ZVEI and VDMA professional associations in Germany. Please refer to the following German–Language publication: Weiterbildung in der Automatisierungstechnik Publishers: ZVEI and VDMA Maschinenbau Verlag Postfach 71 08 64 60498 Frankfurt/Germany Interventions in the hardware and software of our products not described in this instruction manual may only be performed by our skilled personnel. Unqualified interventions in the hardware or software or non–compliance with the warnings listed in this instruction manual or indicated on the product may result in serious personal injury or damage to property. Installation and maintenance of the products described hereunder is the exclusive domain of trained electricians as per IEV 826–09–01 (modified) who are familiar with the contents of this manual. Trained electricians are persons of whom the following is true: • They are capable, due to their professional training, skills and expertise, and based upon their knowledge of and familiarity with applicable technical standards, of assessing the work to be carried out, and of recognizing possible dangers. • They possess, subsequent to several years’ experience in a comparable field of endeavour, a level of knowledge and skills that may be deemed commensurate with that attainable in the course of a formal professional education. With regard to the foregoing, please read the information about our comprehensive training program. The professional staff at our training centre will be pleased to provide detailed information. You may contact the centre by telephone at (+49) 6062 78–258. 1070 072 168-101 (98.04) GB Safety Instructions 1.3 Safety markings on components DANGER! High voltage! DANGER! Corrosive battery acid! CAUTION! Electrostatically sensitive components! Disconnect mains power before opening! Lug for connecting PE conductor only! Functional earthing or low–noise earth only! Screened conductor only! 1070 072 168-101 (98.04) GB 1-3 1-4 Safety Instructions 1.4 Safety instructions in this manual DANGEROUS ELECTRICAL VOLTAGE This symbol warns of the presence of a dangerous electrical voltage. Insufficient of lacking compliance with this warning can result in personal injury. DANGER This symbol is used wherever insufficient or lacking observance of this instruction can result in personal injury. CAUTION This symbol is used wherever insufficient or lacking observance of instructions can result in damage to equipment or data files. ⇒ This symbol is used to alert the user to an item of special interest. 1070 072 168-101 (98.04) GB Safety Instructions 1-5 1.5 Safety instructions for the described product DANGER Fatal injury hazard through ineffective Emergency–OFF devices! Emergency–OFF safety devices must remain effective and accessible during all operating modes of the system. The release of functional locks imposed by Emergency–OFF devices must never be allowed to cause an uncontrolled system restart! Before restoring power to the system, test the Emergency–OFF sequence! DANGER Danger to persons and equipment! Test every new program before operating the system! DANGER Retrofits or modifications may interfere with the safety of the products described hereunder! The consequences may be severe personal injury or damage to equipment or the environment. Therefore, any system retrofitting or modification utilizing equipment components from other manufacturers will require express approval by Bosch. DANGEROUS ELECTRICAL VOLTAGE Unless described otherwise, maintenance procedures must always be carried out only while the system is isolated from the power supply. During this process, the system must be blocked to prevent an unauthorized or inadvertent restart. If measuring or testing procedures must be carried out on the active system, these must be carried out by trained electricians. CAUTION Danger to the module! Do not insert or remove the module while the controller is switched ON! This may destroy the module. Prior to inserting or removing the module, switch OFF or remove the power supply module of the controller, external power supply and signal voltage! CAUTION Only Bosch–approved spare parts may be used! 1070 072 168-101 (98.04) GB 1-6 Safety Instructions CAUTION Danger to the module! All ESD protection measures must be observed when using the module! Prevent electrostatic discharges! Observe the following protective measures for electrostatically endangered modules (EEM)! • The Employees responsible for storage, transport and handling must be trained in ESD protection. • EEMs must be stored and transported in the protective packaging specified. • Out of principle, EEMs may be handled only at special ESD work stations equipped for this particular purpose. • Employees, work surfaces and all devices and tools that could come into contact with EEMs must be on the same potential (e.g. earthed). • An approved earthing wrist strap must be worn. It must be connected to the work surface via a cable with integrated 1 MW resistor. • EEMs may under no circumstances come into contact with objects susceptible to accumulating an electrostatic charge. Most items made of plastic belong to this category. • When installing EEMs in or removing them from an electronic device, the power supply of the device must be switched OFF. 1.6 Trademarks All trademarks referring to software that is installed on Bosch products when shipped from the factory represent the property of their respective owners. At the time of shipment from the factory, all installed software is protected by copyright. Software may therefore be duplicated only with the prior permission of the respective manufacturer or copyright owner. MS–DOS and Windows™ are registered trademarks of Microsoft Corporation. PROFIBUS is a registered trademark of the PROFIBUS Nutzerorganisation e.V. (user organization). 1070 072 168-101 (98.04) GB Introduction 2 2-1 Introduction This manual is designed to support the MMI-MADAP software user with all activities related to project design, programming and system start-up. The manual discusses handling procedures for the MMI-MADAP software with regard to the programmable logic controller being used, including the control panel. Due to the additional hardware features and operating functions which go beyond those of a mere control panel, the term operator terminal appears appropriate to describe the BT100 discussed throughout these pages. )LJ%DVH6FUHHQ00,0$'$36RIWZDUH Subjects related to the operation and programming of the MMI-MADAP software are addressed in the supplementary manual indicated below: F BOSCH documentation reference MMI-MADAP for System or Machine Operators — Software Manual 1070 072 168-101 (98.04) GB Part no. 1070 072 167 2-2 Introduction 2.1 Overview of Functions To illustrate the powerful features of the MMI-MADAP software, the implemented functions are listed individually in the following sections. General information and functions featured in each screen • • • • • • • System time and date display Controller ID (user ID) PLC type and central processing unit ID Two permanently displayed alarm lines (message bars) Processing Unit Stopped message Print Screen function Permanently available Help windows Project handling and backup management • • • Multilevel access privileges via password system User-configurable Save, Load and Delet functions Selectable user language Power-up screens providing overview of the machine start prerequisites • • • 6 power-up screens with 32 power-up conditions each Screen titles and function key labels, plus bit variable and text for each power-up condition can be defined on-line on the BT100 operator terminal. Lamp test function User screens for visualization and parameter selection for machines and systems • • • 8 groups with 8 user screens each (total of 64 screens) On the BT100 operator terminal, on-line definition of group titles, function key labels, screen matrix Comfortable editor for screens and variables, with vector graphics and bitmap level, plus access to additional tools, such as alarm system, recipe management, math worksheet, trend functions, protocol/record system, scheduler, Unisoft language, etc. 1070 072 168-101 (98.04) GB Introduction 2-3 Movement screens for manual machine operation and setup • • • • • • • • • • Step-programmable, user-defined manual conditions Movement initiation through activation of step programmed for this movement Diagnostics also for all manual movements 8 groups with 8 movement screens each, each featuring 8 movement pairs: = 1024 movements Definable on-line on BT100: Group titles, screen titles, function key labels, screen matrix, link with user screen For each movement, definable on-line on BT100: cascade/step, movement text, two variables (actuator and end positions), incl. descriptive text The executability of a given movement is indicated on the screen The statuses of the actuators and their end positions are visible on the screen. Immediate motion stop upon release of key Event-controlled movement inhibition centrally possible for all movement screens, and selectively for individual movement screens. Status screens to support start-up and maintenance functions • • • • • • • • • • 1070 072 168-101 (98.04) GB Status display for all PLC operands: I/EI, O/EO, M/SM/S, T/C, DF/DP, all available DMs Data module list of all available DMs Display of equipped system modules Display of version identifiers of relevant function modules Indication of active input/output bytes Information about PLC cycle times and communication interruptions Display of current Time/OM declarations Current PLC warnings / messages / information statuses Setting time and date 2-4 Introduction Machine usage • • • • • • • • Production statistics, current / actual or historical Data recording for 3 work shifts with 6 breaks each Standardized recording parameters for: Machine On Production Fault No Parts Buffer Full Standstill Parts actual /Parts desired Bar graph Overview of production day Overview of individual work shifts Plotting of curves for current or selectable historical period Exportable Trend data Machine cycle times 48 machine cycle times with on-line text definition on the BT100 operator terminal Message systems and protocol record Current messages, long-time protocols, fault statistics • • • • 5 message systems for current messages / alarms: First-value errors in cascade diagnostics PLC system messages PROFIBUS-DP diagnostics Bus and bus station faults * Status messages, 128 (user) * Serial messages, 511 (user) * * = On-line alarm text definition on BT100 Protocol record with selectable life cycles for: First-value errors in cascade diagnostics PLC system messages PROFIBUS-DP diagnostics User messages Display of protocol record for selectable time periods Statistics for first-value errors in cascade diagnostics: Resolution into detailed error patterns Bar graph display of error frequency distribution of most major error patterns 1070 072 168-101 (98.04) GB Introduction 2-5 Diagnostics for rapid error detection and troubleshooting • • • • • • • • Self-teaching diagnostics for process sequences Automatic adoption of symbols, symbol comments, step text and cascade text from PLC project Automatic first-value diagnostics Manual diagnostics of each cascade with the current step Diagnostic display in the form of instruction list (IL) or ladder diagram (LD) PROFIBUS-DP diagnostics, bus and bus station errors Serial message system containing 511 messages, coming / going Parallel message system encompassing 128 statuses Synchronization for automatic restart without control reset 1070 072 168-101 (98.04) GB 2-6 Introduction 1070 072 168-101 (98.04) GB Suitable Controllers 3-1 3 Suitable Controllers Introduction MMI-MADAP comprises a software system capable of controlling the CL350, CL400 and CL500 Bosch-proprietary PLC controllers. Hardware concept with PROFIBUS-FMS networking This is an MMI-MADAP hardware concept that provides for PC control panels to be operated on a CL400 or CL500 (but not CL350) programmable logic controller via a PC PROFIBUS-FMS card, with the respective controller being connected to the PROFIBUS-FMS via the Bosch-proprietary R500P or COM-P interface card. MMI-MADAP is capable of managing, on one CL400 or CL500, up to four operator terminals (per central processing unit). A CL500 can accommodate up to four central processing units. A maximum of eight MMI-MADAP operator terminals can be connected to a single R500P or COM-PPROFIBUS-FMS card. The entire PROFIBUS-FMS management is handled by the MMI-MADAP operator terminals. On the side of the programmable logic controller, no PROFIBUS-FMS software modules are required. 1070 072 168-101 (98.04) GB 3-2 Suitable Controllers Hardware concept as a point-to-point connection with the Bosch BUEP19E transmission protocol This is an MMI-MADAP hardware concept that provides for PC control panels to be operated either via the central processing units and/or the R500 interface card on a Bosch CL350, CL400 or CL500 programmable logic controller. MMI-MADAP is capable of managing, on one CL400 or CL500, up to four operator terminals (per central processing unit). A CL500 can accommodate up to four central processing units. In the case of the CL350, the operator terminal can be connected only to the central processing unit. As it is not possible to install an R500 card, this controller does not permit the use of several operator terminals. Signals generated by hardware operating elements (e.g. Start key switch) can be transferred via the PROFIBUS-DP decentralized bus system. For details about the hardware configuration of PC operating panels, please refer to »System Requirements for MMI-MADAP Operator Terminal « on page 6-2 of this manual. 1070 072 168-101 (98.04) GB Suitable Controllers Hardware concept with PROFIBUS-FMS networking 352),%86)06 352),%86'3 %XV7HUPLQDWLRQ 352),%86'3 7UDQVIHURI ,2LQIRUPDWLRQ 2SHUDWRU7HUPLQDOIRU6\VWHP0DFKLQH 352),%86)06 'DWD([FKDQJH 2SHU7HUPLQDO ⇔3/& 2SHU7HUPLQDO (OHPHQWV ,2 3& ZLWK 'LVSOD\ 00,0$'$3 2SHU7HUPLQDO 2SHUDWRU7HUPLQDOIRU6\VWHP0DFKLQH 2SHU7HUPLQDO (OHPHQWV ,2 3& ZLWK 00,0$'$3 2SHU7HUPLQDO 'LVSOD\ %XV7HUPLQDWLRQ %XV7HUPLQDWLRQ LVDUHJLVWHUHG ,2 ,2 WUDGHPDUNRI 6LHPHQV$* '3,20RGXOHVIRU '3,20RGXOHVIRU 6\VWHP0DFKLQH 6\VWHP0DFKLQH )LJ+DUGZDUH&RQILJXUDWLRQ00,0$'$3ZLWK352),%86)06 1070 072 168-101 (98.04) GB 3-3 3-4 Suitable Controllers 1070 072 168-101 (98.04) GB MMI-MADAP PLC Software 4-1 4 MMI-MADAP PLC Software 4.1 Introduction The MMI-PLC software consists of the following function units: • Control • Operating / Monitoring • Machine usage • Machine cycle time recording The referred function units are capable of standalone operation, and operate independently of each other. Control Performance features: • Control of a maximum of 64 cascades operating in parallel, with up to 128 steps per cascade. • Synchronization of control sequences to current machine status. • Management of system operating modes. • Linear or branched sequence organization. • Command output. Operating / Monitoring Performance features: 1070 072 168-101 (98.04) GB • Execution of 1024 movements directly from operator terminal. • Display of system fault conditions and machine statuses. • Display of PLC errors and fault statuses. • Monitoring and reporting of sequential faults. • Monitoring and reporting of PROFIBUS-DP faults. 4-2 MMI-MADAP PLC Software Machine usage Recording of production data for the following parameters: • Machine On • Production • Fault • Standstill • Buffer Full • No parts • Parts Actual Cycle time recording Recording / logging of 48 machine cycle times. Data interface A number of data modules are defined to serve as the interface between the PLC controller and the operator terminal. Predefined data word ranges are declared as PROFIBUS-FMS objects. These are directly read and/or written to by the operator terminal. 1070 072 168-101 (98.04) GB MMI-MADAP PLC Software 4-3 Differences between PROFI and WinSPS PLC programming software F For the purpose of representing and expressing constants and program modules, this documentation uses the conventions of the PROFI software designed for the programming device. For this reason, they may appear dissimilar when using the WinSPS programming software. Differences in programming and representation of word constants Data type Explanation UINT (unsigned integer) PLC Utility programs PROFI WinSPS Representation Binary / Dual Decimal, Word Decimal, Byte/Byte INT (integer) Hexadecimal Decimal, Word Text, STRING(2) Time value, TVALUE Time value (+time base r) ASCII K00000000 00000000B K11111111 11111111B K00000D - K63535D K000/000 - K255/255 K0000H - KFFFFH K-32768 - K+32767 K-32768D - K+32767D K'AB’ r: 0=10ms, 1=100ms 2=1s, 3=10s 2#0000000000000000 2#1111111111111111 00000 - 65535 not defined in IEC1131 Teil 3 16#0000 - 16#FFFF -32768 - +32767 ‘AB’ T#10ms - T#10230s T#0.r - T#1023.r K0.r - K1023.r Differences in programming and representation of program module calls PLC Utility programs PROFI WinSPS Program module/Function call (IEC1131/3) CM PM CM FC Differences in programming and representation of jump instructions PLC Utility programs PROFI WinSPS Jump instruction Branch destination 1070 072 168-101 (98.04) GB JPx -label -label JPx label: label 4-4 MMI-MADAP PLC Software 4.2 Software Installation 4.2.1 Supplied Software 4.2.1.1 DISK.FB.MMIMADAP Diskette This diskette contains the following software files: Organization modules OM1 Administration module OM2 Definition module OM5 Start-up module, subsequent to Power-ON OM7 Start-up module, subsequent to STOP/RUN OM9 Error module OM18 - OM25 Time-controlled modules 1 through 8 Open program modules (can be displayed and modified) SCHRK1 Kette 1 transition program KETTE1 Call-up for "KETTE" PM and command processing for Kette 1 MMIDESI PROFIBUS_DP_Diagnose call-up module Library modules (can neither be displayed nor modified) MMIMADAP Data processing for screen displays KETTE Control sequence management DIAGMMI Control sequence diagnostics R5INIT R500P initialization BT100DEC BT100 key decoding MMIAUSL Machine usage administration module MMISTAT Statistical data MMISTCK Actual piece counts MMIPROZ Percentage data MMISCHT Work shift information MMILOGIK Logging/recording parameters MMI_TZ Cycle time evaluation for 48 cycle times MMI_T1S Freerunning 1-s cycle MMI_T01S Freerunning 0.1-s cycle DPSTATUS DESI-DP data processing FIFODM1 DESI-DP data processing 1070 072 168-101 (98.04) GB MMI-MADAP PLC Software 4-5 The OM5 and OM7 organization modules (start-up modules) contain the call for the R5INIT standard module. This module is used for initialization of the status utility up to and including version 6 of the R500P module (refer to front panel labelling). This utility generates the CPU Stopped and Communication Failure system messages. Beginning with version 7 of the R500P, the R5INIT module is no longer required. The R5INIT module is supplied on the diskette containing function modules for CL400 / CL500 standard interfaces. If required, it can be ordered as part number 069065. MMI-MADAP Standard symbol file Standard data modules (for WinSPS only) Preconfigured SC table. PROFIBUS-FMS Configuration files for R500P 1070 072 168-101 (98.04) GB 4-6 MMI-MADAP PLC Software 4.2.2 Installing MMI-MADAP PLC Software The diskette labelled DISK.FB.MMIMADAP contains the following directories: • 3URIL636 • 352),%86 (PROFIBUS-FMS files for the R500P). • :LQ636 (PLC files for PROFI software), (PLC files for WinSPS software), $? 352),%86 PROFIBUS configuration files æ &203 for use with CL400 æ&203 for use with CL500 æ53 for use with CL400 æ53 for use with CL500 æ Configuration 1 æ : (ZS0:0BF,ZS1:2BF,ZS2:2BF, ZS3:2BF) æ : æ Configuration 21 æ (ZS0:4BF,ZS1:4BF,ZS2:0BF, ZS3:0BF) æ 3URIL636 3/&ILOHVIRUPROFI æ%26&+%,% Library modules for CL350 / 400 / 500 æ00,0$'$3 ææ6. SC table for CL500 ææ=6 "open" modules for CL500 æ00,0$'$3 æ6. SC tables for CL350 / 400 æ=6 "open" modules for CL350 / 400 æ :LQ636 3/&ILOHVIRUWinSPS %,%&/B Library modules for CL350 / 400 / 500 00,0$'$335&/ 6. SC table for CL500 æ6.B SC tables for CL350 / 400 =6 "open" modules for CL350 /400 /500 )LJ'LUHFWRU\6WUXFWXUHVRQ',6.)%00,0$'$3'LVNHWWH The program modules listed below are supplied in the form of library modules on the diskette labelled DISK.FB.MMIMADAP. They are located in the following library directories: • winsps\bibcl4_5 (WinSPS), and/or • profisps\bosch.bib (PROFI). MMI-MADAP library modules MMIMADAP KETTE Data processing for screen displays Control sequence management DIAGMMI Control sequence diagnostics BT100DEC BT100 key decoding MMIAUSL Machine usage administration 1070 072 168-101 (98.04) GB MMI-MADAP PLC Software MMISTAT Statistical data MMISTCK Actual piece counts MMIPROZ Percentage data MMISCHT Work shift information MMILOGIK Logging/recording parameters MMI_TZ 4-7 Cycle time evaluation for 48 cycle times MMI_T1S Freerunning 1-s cycle MMI_T01S Freerunning 0.1-s cycle DPSTATUS DESI-DP data processing FIFODM1 DESI-DP data processing Please copy these files as required from the diskette to your applicable library directory or directories. .pxl filename extension WinSPS files for CL400 / CL500 .p5l filename extension PROFI files for CL500 .pcl filename extension PROFI files for CL400 As a next step, copy all required files from the applicable directory listed below to the respective project directory: winsps\mmimadap.prj\cl500.500\zs0 (CL500 modules, WinSPS software), profisps\mmimadap.400\zs0 (CL400 modules, PROFI software), OR profisps\mmimadap.500\zs0 (CL500 modules, PROFI software) F If you are using the CL350 or CL400 with the WinSPS software, copy the listed CL500 modules into your project directory. This will cause the modules to be processed automatically upon start-up. F Please be careful to prevent accidental overwriting of files in the project directory that you have created yourself. In the event that you have not yet created a current file for your system co-ordinator (SC table), you can copy the required file from the corresponding directory ending with ...\sk into your current SK project directory. 1070 072 168-101 (98.04) GB 4-8 MMI-MADAP PLC Software 4.2.3 Linking Standard Symbol File and Standard Modules Subsequent to the completed installation, the symbol file will be located in the current project directory. F Filename: Mmimadap.sxs for WinSPS version Filename: Mmimadap.s5s for CL500 PROFI version Filename: Mmimadap.scs for CL400 PROFI version When starting a new project, please use this symbol file. If you are already using a symbol file, enter the module names specified in Section 3.2.1.1 and, if required, the R5INIT module, into your symbol file. If you want to integrate the MMI-MADAP software into an existing project, you will be required to open all data modules named DM230 through DM255, and enter them in the symbol file. If you want to use also the machine usage times and machine cycle time functions, you must open data modules DM217 through DM221 also. In this case, copy the data modules from the standard symbol file into your current symbol file (including comments and default values). F In the case of the WinSPS version, the installation procedures will copy all standard data modules into the current project directory. F Up to and including version 6 of the R500P PROFIBUS-FMS card, the R5INIT module is required for initializing the status utility that generates the CPU Stopped and Communication Failure system messages. Beginning with version 7 of the R500P, the R5INIT module is no longer required. 1070 072 168-101 (98.04) GB MMI-MADAP PLC Software 4-9 4.2.4 Configuring Com-P and R500P PROFIBUS Cards For the purpose of configuring the PROFIBUS-FMS, ready-to-use configuration files are provided on the DISK.FB.MMIMADAP standard diskette. The filenames are as follows: • 001SPS.KBL • 001SPS.OV • XXXSPS.BUS 4.2.4.1 Com-P Card CL400 Controller For use with the CL400, the directory named Com-P.400 contains a fully prepared configuration for 4 operator terminals. CL500 Controller For use with the CL500, the directory named Com-P.500 contains a fully prepared configuration for 4 central processing units with 4 operator terminals each. 4.2.4.2 R500P Card CL500 Controller As the R500P is capable of managing only 100 objects, it is not possible to provide a ready-to-use configuration for the maximum hardware configuration of the MMI-MADAP concept onboard the module. For this reason, various hardware configurations for the CL500 were provided on the MMI-SPS diskette. As a result, configuration files are available for all useful configuration variants (combination between the numbers of operator terminals and central processing units). The different variants are located in 21 different subdirectories. The type of combination contained in a given subdirectory can be directly recognized from the respective directory name. This means that the specified combination of numerals must always be read in pairs, with the first numeral indicating the number of the central processing unit ("ZS number"), and the second numeral indicating the number of operator terminals (BT) assigned to this central processing unit. F 1070 072 168-101 (98.04) GB NOTE: The abbreviations "BT" and "BF" (from the German --> BedienTerminal and Bedienfeld) shall have the meaning of "operator terminal" throughout this manual. 4-10 MMI-MADAP PLC Software Example 1: Directory pathname: r500p.500\02122232 • 02: ZS0 operates 2 BT • : ZS1 operates 2 BT : ZS2 operates 2 BT : ZS3 operates 2 BT Example 2: Directory pathname: r500p.500\03132230 03: ZS0 operates 3 BT : ZS1 operates 3 BT : ZS2 operates 2 BT : ZS3 operates 0 BT CL400 Controller For use with the CL400, the directory named r500p.400 contains a fully prepared configuration for 4 operator terminals. 4.2.4.3 Installation Procedure From the respective directory, e.g. r500p.500\02122232, copy the PROFIBUS files to the applicable project directory, e.g. c:\pg\mmimadap.500\profibus. Use the PROFI programming device software to load the PROFIBUS files into the PLC controller. F Ensure that the R500P is set to PROFIBUS-FMS station address no. "1." F BOSCH documentation reference Communication Module for CL400/CL500 COM-P (Manual) in preparation CL 500/ R500P Computer Module (Manual) No. 1070 072 138 PROFI Programming Software (Manual) No. 1070 072 129 1070 072 168-101 (98.04) GB MMI-MADAP PLC Software 4.3 PLC Program Components 4.3.1 Organization Modules OM1 OM2 Symbolic name OM1 OM2 Function Administration module with program module calls for basic functions Definition module OM5 OM7 OM5 OM7 Start-up module subsequent to Power-ON Start-up module subsequent to STOP/RUN OM9 OM9 Error module OM18 OM19 OM20 OM21 OM22 OM23 OM24 OM25 OM18 OM19 OM20 OM21 OM22 OM23 OM24 OM25 Time-controlled module 1 Time-controlled module 2 Time-controlled module 3 Time-controlled module 4 Time-controlled module 5 Time-controlled module 6 Time-controlled module 7 Time-controlled module 8 )LJ/LVWRI2UJDQL]DWLRQ0RGXOHV 4.3.2 Program Modules PM1 PM100 Symbolic name SCHRK1 KETTE1 Function Kette 1 transition program Call-up of KETTE PM, and command processing for Kette 1 PM200 PM201 PM202 PM203 MMIMADAP KETTE DIAGMMI R5INIT Data processing for screen displays Control sequence management Control sequence diagnostics Initialization of status utility, R500P or COM-P (not required for R500P, version 7 and up) PM205 BT100DEC BT100 key decoding PM207 PM208 PM209 PM210 PM211 PM212 MMIAUSL MMISTAT MMISTCK MMIPROZ MMISCHT MMILOGIK Machine usage administration module Statistical data (Call-up via MMIAUSL) Actual piece counts (Call-up via MMIAUSL) Percentage data (Call-up via MMIAUSL) Work shift information (Call-up via MMIAUSL) Logging/recording parameters (Call-up via MMIAUSL) PM214 PM215 PM216 MMI_TZ MMI_T1S MMI_T01S Cycle time evaluation for 48 cycle times Freerunning 1.0-sec cycle (Call-up via MMI_TZ) Freerunning 0.1-sec cycle (Call-up via MMI_TZ) PM218 PM219 PM220 MMIDESI DPSTATUS FIFODM1 Call-up module for PROFIBUS-DP diagnostics DESI-DP data processing (Call-up via MMIDESI) DESI-DP data processing (Call-up via DPSTATUS) )LJ/LVWRI3URJUDP0RGXOHV 1070 072 168-101 (98.04) GB 4-11 4-12 MMI-MADAP PLC Software 4.3.3 Data Modules DM no. DM 1 : DM 64 DM DM DM DM DM DM DM DM DM DM DM DM DM DM DM DM DM DM DM DM DM DM DM DM DM DM DM DM DM DM DM DM DM DM DM DM DM DM DM 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 241 244 245 246 247 246 249 250 251 252 253 254 255 Name DB_K01 DB_K64 Function Kette 1 cascade information : Kette 64 cascade information R/E R : R Length 100 : 100 Taktzeit Auslast1 Auslast2 DP_Daten DP_Komm Diag_St5 Diag_St6 Diag_St7 Diag_St8 Cycle time recording Machine usage data 1 Machine usage data 2 DESI-DP data DESI-DP communication channel 1 Station 5 diagnostic data (optional) Station 6 diagnostic data (optional) Station 7 diagnostic data (optional) Station 8 diagnostic data (optional) R R R R R R R R R 230 512 512 512 320 512 512 512 512 BF1_DB BF1_Stat BF1_Sper BF1_Anw BF1_Diag BF2_DB BF2_Stat BF2_Sper BF2_Anw BF2_Diag BF3_DB BF3_Stat BF3_Sper BF3_Anw BF3_Diag BF4_DB BF4_Stat BF4_Sper BF4_Anw BF4_Diag BF1_4Anw ResKObj1 ResKObj2 EA_SK AL_DP_D BF_Globa Communication / display data OPD status Movement lock functions Communication DM, 1 Object of 220 bytes Diagnostic result for BT1 = Station 1 Communication / display data Operand status Movement lock functions Communication DM, 1 Object of 220 bytes Diagnostic result for BT2 = Station 2 Communication / display data Operand status Movement lock functions Communication DM, 1 Object of 220 bytes Diagnostic result for BT3 = Station 3 Communication / display data Operand status Movement lock functions Communication DM, 1 Object of 220 bytes Diagnostic result for BT4 = Station 4 DM250 for all BT, 2 objects of 220 bytes ea. Reserved for future communication objects Reserved for future communication objects I/O assignment and SC table Display of machine usage & DP diagnostics DM, valid for all BTs R R R R R R R R R R R R R R R R R R R R R R R R R R 512 512 512 512 512 512 512 512 512 512 512 512 512 512 512 512 512 512 512 512 512 : 512 512 512 )LJ/LVWRI'DWD0RGXOHV 1070 072 168-101 (98.04) GB MMI-MADAP PLC Software 4-13 4.3.4 System Configuration Table for CL500 The system configuration described below comprises a suggestion, the scope of which may be expanded or otherwise modified. With the use of a CL400, all ZS entries will be deleted. NOTE: If the R500P is entered in another row of the list, this will cause the module number to change. As a consequence, the parameterization of the R5INIT standard PM (if in use) must also be suitably adapted in the OM5 and OM7 start-up modules. Module no. Modules In Rack Block Addr. Synch. method Rem. STOP IR module Periph. Addr. 1 2 3 4 5 6 7 8 9 10 ZS510 ZS510 ZS510 ZS510 J N N N 0 8 16 24 00000000 00000000 00000000 00000000 N N N N 0 0 0 0 0 64 128 192 R500P J 40 )LJ6&7DEOH 1070 072 168-101 (98.04) GB I/O EI/EO Length 64 64 64 64 64 64 64 64 4-14 MMI-MADAP PLC Software 4.4 Principal Program Structure OM2 Definitions OM5 R5INIT Start-up subsequent to Power-ON Status utility initialization OM7 Start-up after Stop/Run OM1 Administration module Control ; Cascade calls with ; operating modes CM CM PM1: SchrK1 DM1: DatenK1 KETTE1 Cascade call + KETTE1 KETTE Step program Data module :: command output Sequential control management for KETTE1 for KETTE1 :: :: :: :: :: KETTE64 PM64: SchrK64 DM64: DatenK64 Kette64 Cascade call + command output Step program for KETTE64 Data module for KETTE64 DM233: BF1_Anl1 System-specific communications, BT1 Your P L C :: Program Remaining DM248: BF1_Anl4 PLC program System-specific communications, BT4 DM250: Global System-wide comm., BT1-4 Machine usage, cycle times ; Machine usage CM MMIAUSL MMIAUSL MMILOGIK DM218 Data recording for: MMIPROZ Mach. usage data 1 - Machine On MMISCHT DM219 - Production MMISTAT Mach. usage data 2 - No Parts MMISTCK - Buffer Full - Fault - Piece/parts Count From "MMIDESI" DM254 Display data ; Machine cycle times CM MMI_TZ MMI_TZ Data recording for: DM217 48 Cycle times Cycle time data MMI_T01S MMI_T1S 1070 072 168-101 (98.04) GB MMI-MADAP PLC Software cont’d with OM1 Operating, diagnostics,visualization ; Key decoding CM BT100DEC BT100DEC Key decoding in 1, out 16 ; DESI-DP Diagnostics CM MMIDESI MMIDESI DPSTATUS Parameter process. DP diagnostics DM220 DM221 for DP diagnostics processing DP diagnostic data to DM254 FIFODM1 DP diagnostics DM230-DM232 management Communication and display data for operator terminal 1 DM234: DiagDat ; Operator terminal 1 CM MMIMADAP :: MMIMADAP Cascade diagnostic Data processing data, station 1 für das BT100 :: ; Operator terminal 4 CM MMIMADAP DM245-DM247 DIAGMMI Communication and Diagnostic data processing display data for operator terminal 4 DM249: DiagDat Cascade diagnostic data, station 4 DM253 I/O assignment and SC table DM255 Global data, valid for all BT numbers EP OM9 Error responses OM18-OM25 Time-contr'd modules )LJ00,0$'$36RIWZDUH²2YHUDOO3URJUDP6WUXFWXUH 1070 072 168-101 (98.04) GB 4-15 4-16 MMI-MADAP PLC Software OM2 Definition module The OM1 comprises a system initialization table containing default definitions governing the operation of the PLC. It is essential to note that it is not permitted to insert rows (lines) into or delete rows from the table. Instead, the existing values may be merely modified, i.e., overwritten. Entries enabling recognition of a cycle time error ;DW 2: Initialization flag (entries permitted) ;--------------------------------; Entry 0 = DO NOT verify or execute function ; Entry 1 = Verify or execute function ; DEFW W K0000000000000100bin ; ; ; ; Bit 1 = Check assignment list Bit 2 = Check nominal cycle time (not effective for ZS500 < version 201!!) Bit 9 = Copy data module in data buffer ;DW 5: Maximum cycle time (not effective for ZS500 < version 201!!) ;------------------------------------; Entry to be a multiple of 10 ms time base of K1D and K200D ; 10 ms through 2000 ms) for cycle time monitoring ; Execution of function when bit 1 of DW2 = 1. ; DEFW W K200D ; Entries ensuring time-controlled processing steps ; Definition of time OMs (entries permitted) ; ======================== ; Entries to constitute multipliers of 10 ms basic time of K1D through K65535D ; e.g. K0D = NO time-controlled processing ; K11D = 11 x 10 ms = 110 ms processing time interval ; ;DW 11: Time OM18 ;---------------------------------DEFW W K0D ;DW 12: Time OM19 ;---------------------------------DEFW W K0D ;DW 13: Time OM20 ;---------------------------------DEFW W K0D ;DW 14: Time OM21 ;------------------------DEFW W K0D 1070 072 168-101 (98.04) GB MMI-MADAP PLC Software ;******************************************************************************** ; In the case of the ZS500 < version 201, the time-controlled OMs, i.e., ; OM22 through OM25, must first be released by the program. ;******************************************************************************** ;DW 15: Time OM22 ;--------------------------------DEFW W K0D (for ZS500 < version 201, release by program required) ;DW 16: Time OM23 ;--------------------------------DEFW W K0D (for ZS500 < version 201, release by program required) ;DW 17: Time OM24 ;--------------------------------DEFW W K0D (for ZS500 < version 201, release by program required) ;DW 18: Time OM25 ;----------------------------------DEFW W K0D (for ZS500 < version 201, release by program required) 1070 072 168-101 (98.04) GB 4-17 4-18 MMI-MADAP PLC Software OM5 and OM7 Start-up modules The purpose of the R5INIT module call in the OM5 and OM7 organization modules is to initialize the status utility for the R500P (through version 6, check front panel marking), and to generate the CPU Stopped and Communication Failure system messages for display on the operator terminal. Effective with version 7 of the R500P (refer to front panel marking), the linking of the R5INIT module, and of the OM5 and OM7 is no longer required because the status utility is now supported directly. The OM5 start-up module is processed subsequent to each Power-On, and the OM7 after each STOP/RUN command. As the preprogrammed contents are identical for both modules, they are shown here only once. 2%2%6WDUWXSPRGXOHDIWHU3RZHU2Q6723581 '()[[[[,QLW(UJ DQ\RSHUDQGH[FHSW00 ,QLWLDOL]DWLRQRI53FRPSXWHULQWHUIDFHPRGXOHIRUSURFHVVLQJ WKHVWDWXVXWLOLW\IRUHYDOXDWLQJWKH&386WRSSHGDQG&RPPXQLFDWLRQ )DLOXUHV\VWHPPHVVDJHV 8SRQLQLWLDOL]DWLRQWKHPRGXOHQXPEHUURZQXPEHULQ6&7DEOH RIWKH53PXVWEHVSHFLILHG3DUDPHWHUL]DWLRQLVUHVWULFWHGWR PRGXOHVWKDWDUHSK\VLFDOO\SUHVHQW$PRGXOHWKDWLVQRWSK\VLFDOO\ SUHVHQWPXVWEHUHSUHVHQWHGE\DSDUDPHWHUL]DWLRQRI.))))+ &05,1,7 3:.' 3:.))))+ 3:.))))+ 3:.))))+ 3:.))))+ 3:,QLW(UJ (UURUUHVSRQVH /:,QLW(UJ$ &3/$:.$ -3=,QLWBL2 +/7 ,QLWBL2 53PRGXOHQXPEHUURZRI6&WDEOH 1RPRGXOHSUHVHQW 1RPRGXOHSUHVHQW 1RPRGXOHSUHVHQW 1RPRGXOHSUHVHQW 5HVXOWRILQLWLDOL]DWLRQ 5HDGUHVXOW )DXOWIUHHLQLWLDOL]DWLRQ +DOWRQHUURU DGGLWLRQDODSSOLFDWLRQSURJUDP (0 )LJ2%2%6WDUWXS0RGXOHV 1070 072 168-101 (98.04) GB MMI-MADAP PLC Software 4-19 OM9 Error module The OM9* represents an error module within the PLC. The following program part is required as a standard function: 20'DWDSURFHVVLQJIRUGLVSOD\LQJFDXVHVRI3/&6723FRQGLWLRQV 00,0$'$3(UURUUHWXUQXSRQFRQWUROOHUVWDQGVWLOO '()'%*OREDO'% '()60$GU)HKO$GGUHVVLQJHUURU '()603%SDUD)30SDUDPHWHUHUURU '()60QBH[W%VW1RQH[LVWHQW30ZDVFDOOHG '()60%VW6WDFN0RGXOHVWDFNHUURU '()60$67B8$SSOLFDWLRQVWDFNXQGHUUXQHUURU '()60$67B8H$SSOLFDWLRQVWDFNRYHUUXQHUURU '()606%SDUD)3DUDPHWHUHUURULQV\VWHPFRPPDQGV '()60QR'%1R'0DFWLYHDWWKLVWLPH '()60=\NO=)&\FOHWLPHHUURU '()'636B=B) &0*OREDO'%'% /:636B=B)$' $%$GU)HKO60$GGUHVVLQJHUURU 20%$ $%3%SDUD)6030SDUDPHWHUHUURU 20%$ $%QBH[W%VW601RQH[LVWHQW30ZDVFDOOHG 20%$ $%%VW6WDFN600RGXOHVWDFNHUURU 20%$ $%$67B860$SSOLFDWLRQVWDFNXQGHUUXQHUURU 2%$67B8H60$SSOLFDWLRQVWDFNRYHUUXQHUURU 20%$ $%6%SDUD)603DUDPHWHUHUURULQV\VWHPFRPPDQGV 20%$ $%QR'%601R'0DFWLYHDWWKLVWLPH 20%$ $%=\NO=)60&\FOHWLPHHUURU 20%$ 7:$636B=B)' LIDSSOLFDEOHDGGLWLRQDOHUURUUHVSRQVHSURJUDP (0 )LJ2%(UURU0RGXOH * %26&+GRFXPHQWDWLRQUHIHUHQFH CL400 / CL500 Operations List, Software Manual 1070 072 168-101 (98.04) GB No. 1070 072 127 4-20 MMI-MADAP PLC Software OM18 through OM25 time-controlled processing modules The modules for time-controlled processing are supplied merely in a preparatory condition, and require programming and, if applicable, activation within OM2. 20207LPHFRQWUROOHGPRGXOHV $SSOLFDWLRQSURJUDP (0 )LJ20WKURXJK207LPHFRQWUROOHG0RGXOHV 1070 072 168-101 (98.04) GB MMI-MADAP PLC Software 4-21 4.5 Process Control 4.5.1 Definitions Introduction This section describes the process control management as well as its operating modes, process management and command output. The appropriate sequential control, diagnostics and display program modules are provided. Specifications To guarantee orderly processing sequences and/or unambiguous diagnostic results, the MMI-MADAP software packet shall be subject to the following specifications: Modules The KETTE program module manages up to • 64 process sequences, encompassing • 128 steps each, • with one active step in each cycle. The following are permanently assigned to the referred process sequences: − Program modules PM1 through PM64 as process sequences − Data modules DM1 through DM64 as cascade data modules The respective PM and DM numbers correspond to the cascade numbers. 1070 072 168-101 (98.04) GB 4-22 MMI-MADAP PLC Software Markers Within the marker range, the markers listed below are assigned a permanent function. Symbol BEFA WSB STOEM HALBAUTO WZT_HLT WZT Address M255.0 M255.1 M255.2 M255.4 M255.5 M255.6 UEKONTR M255.7 VERZW M242 Function Assigned to command output Assigned to step-on functions Fault marker; STOEM = LOW indicates fault present Step-on in inching mode even without S+1 transition Wait time halt Wait time statusLOW: Wait time running HIGH: Wait time expired Monitoring time check If UEKONTR = HIGH, expiration of monitoring time will not trigger diagnostics. Branch address (word) Step number within KETTE program module to which branching will take place if WSB = 1bin. )LJ&RQWURO0DUNHU'HILQLWLRQV 1070 072 168-101 (98.04) GB MMI-MADAP PLC Software 4-23 4.5.2 Programming Program structure OM1 Administration module ; Cascade calls with ; operating modes CM CM PM1: SchrK1 DM1: DatenK1 KETTE1 Cascade call + KETTE Step program Data module :: command output Sequential control for KETTE1 for KETTE1 :: :: management :: :: :: Kette64 PM64: SchrK64 DM64: DatenK64 Cascade call + command output Step program for KETTE64 Data module for KETTE64 KETTE64 Kette1 )LJ3URJUDP6WUXFWXUH²6HTXHQWLDO&RQWURO Module call The KETTE cascade sequence management module is called within the KETTE1 through KETTE64 program module and subsequently services the defined cascades. The operating mode information is transferred to the corresponding parameters of the KETTE module. In order to enable the formation of functional cascade groups, it is possible to leave gaps when assembling up cascade data modules. All cascades that are not called up in the OM1 administration module, will be skipped, and processing will continue with the subsequent cascade. In the event that step modules are to be excluded from processing, the associated cascade module must be declared as a comment upon module call. The module call-up is programmed as follows: &0.(77( 3:3%'%&DVFDGHDQG'0QXPEHU≤Q≤ 3:%(752SHUDWLQJPRGHVHOHFWLRQ 3:.8(7LPHYDOXHRIPRQLWRULQJWLPH 3:.:$7LPHYDOXHRIPRQLWRULQJWLPH )LJ0RGXOH&DOOIRU.(77(3URJUDP0RGXOH Refer to Chapter 4, "Interfaces — PLC <–> Operator Terminals," for the following information: Data module contents DM1 through DM64, i.e. DB_K01 - DB_K64: cascade information for KETTE1 through KETTE64 Example The supplied MMI-MADAP standard software contains a programming example for the module call in the form of a network in the OM1 You can copy the example from there into your program. 1070 072 168-101 (98.04) GB 4-24 MMI-MADAP PLC Software Parameter description F Scratch markers must not be used in place of parameters! .(77( P0 W -PB/DB Parameter P0 supplies the KETTE cascade sequence management module with the current cascade number n for the following modules: − Number of SCHRKQ step module − Number of DMQ cascade data module Each processed cascade n utilizes the cascade data module n to store variable data, e.g. current step, monitoring time and wait time. P1 W -BETR Parameter P1 supplies the KETTE module with the operating mode selection. • • • • • • • • • • • • • • • • P1.0 Manual mode P1.1 Inching mode P1.2 Automatic mode P1.3 Start P1.4 S+1 P1.5 Set Step P1.6 Halt acknowledgement P1.7 Reset P1.8 Halt P1.9 Synchronizing P1.10 P1.11 Generate cascade data module P1.12 Step-on condition in same cycle P1.13 P1.14 WSB does not reset command output Fault acknowledgement P1.15 The KETTE program module writes the operating mode data into data word D6 (nnBAWAHL) of the associated cascade data module. In Manual mode, Start and Set Step will be adopted by D6 only subsequent to pressing the movement keys on the operator terminal. F In cascade data modules, MMI-MADAP sets data bit D24.2 (MADAP identifier bit). Thus in Manual mode, the Start operating mode bit on parameter P1.3 will be AND-linked with the MADAP Start operating mode bit D30.3, and only then returned in data word D6 (selected operating mode). 1070 072 168-101 (98.04) GB MMI-MADAP PLC Software P2 W -KUE Parameter P2 supplies the KETTE module with the monitoring time value. This will remain identical for every step unless it is newly defined in the individual steps. The time base is always 100 ms. Thus an example default: • W K20dez P2 will result in a monitoring time of 20 x 100ms = 2 s The maximum monitoring time is 109 minutes. The monitoring time is transferred to data word D20 of the associated cascade data module. P3 W -KWA Parameter P3 supplies the KETTE module with the wait time value. This will remain identical for every step unless it is newly defined in the individual steps. The time base is always 100 ms. Thus an example default: • W K15dez P3 will result in a wait time of 15 x 100ms = 1.5 s The maximum monitoring time is 109 minutes. The wait time is transferred to data word D18 of the associated cascade data module. 1070 072 168-101 (98.04) GB 4-25 4-26 MMI-MADAP PLC Software Register contents Neither the PLC registers A, B, C and D nor the control flags (e.g. RES, Carry) will be retained beyond the module call. Upon returning from the KETTE program module to the calling module, the registers are given the following defined contents: KETTE Reg. A B C D Contents Version number of KETTE module Error codes, if cascade data module not generated No relevance No relevance )LJ.(77(5HJLVWHU&RQWHQWV Error codes in register B Accu B contents FFFFhex Troubleshooting Cascade data module not available 0001hex P0 of KETTE module is 0 0002hex P0 of KETTE module is > 64dez 0004hex Cascade data module too short < 96dez )LJ(UURU&RGHLQ.(77(5HJLVWHU% 1070 072 168-101 (98.04) GB MMI-MADAP PLC Software 4-27 4.5.3 Operating Modes The operating mode is transferred via parameter P0 to the KETTE module, from where it is written into data word D6 of the associated cascade data module. Manual mode/Setup Function Manual operation of steps occurs in accordance with the conditions valid for the manual branch. The step is entered in data word D14 of the associated cascade data module, and adopted as a current step by means of Set Step (D6.5=HIGH) in D12. Command output occurs if the following applies: • The conditions of the manual branch are met (BEFA command output = HIGH and WSB step-on condition = LOW ) AND • The Start (D6.3 ) = HIGH The command output occurs via the data bits of data words D80 through D94 of the associated cascade data module (refer to cascade data module). No step-on will occur. Both the Manual mode and Start bits are set HIGH. In the event that a movement function is effected at the operator terminal, the following will occur automatically: • • • • Activation of cascade number of the associated cascade data module, Entry of step number in data word D14, Set Step (D6.5), Start (D6.3) is set to HIGH. Diagnostics Display in cascade information, H for Manual mode, in the respective cascade. Display of all criteria of manual branch, i.e., either of BEFA command output that was not met, or of WSB step-on branch. Monitoring and wait time values are loaded along with the default values but are not started. No fault message is returned. 1070 072 168-101 (98.04) GB 4-28 MMI-MADAP PLC Software Inching mode/Single-step mode Function Step-by-step processing of steps in accordance with conditions applying to automatic branch. Command output occurs if the following applies: • The conditions of the manual branch are met (BEFA command output = HIGH and WSB step-on condition = LOW ) AND • The Start (D6.3 ) = HIGH The command output occurs via the data bits of data words D80 through D94 of the associated cascade data module (refer to cascade data module). No automatic step-on will occur. With a positive transition on S+1 (P1.4), and WSB step-on condition being met, the advance to the next step will occur. Programming Inching mode bit is set HIGH. When Start = HIGH, the current step will be processed, and a positive transition at S+1 will cause an advance to the next step. Diagnostics Display in cascade information, T for Inching mode, in the respective cascade. Display of all criteria of automatic branch, i.e., either of BEFA command output that was not met, or of WSB step-on branch. Indication of faulty cascade. Monitoring time and wait time elapse on the basis of the default values. 1070 072 168-101 (98.04) GB MMI-MADAP PLC Software 4-29 Semi-automatic mode Function Semi-automatic processing of steps in accordance with conditions applying to automatic branches. Command output occurs if the following applies: • The conditions of the manual branch are met (BEFA command output = HIGH and WSB step-on condition = LOW ) AND • The Start (D6.3 ) = HIGH The command output occurs via the data bits of data words D80 through D94 of the associated cascade data module (refer to cascade data module). Step-on occurs automatically when WSB step-on condition is met, and when -HALBAUTO marker (M255.4) is set. The step-on will end on the step on which the -HALBAUTO marker is = LOW, or when the WSB stepon condition has not been met. With a positive transition on S+1 (P1.4), and with WSB step-on conditions met, the next program sequence will be processed up to the reset HALBAUTO marker. Programming Inching mode bit is set HIGH. When Start = HIGH, the current step will be processed, and a positive transition at S+1 will cause Semi-automatic mode to be started. Diagnostics Display in cascade information, T for Inching mode, in the respective cascade. Display of all criteria of automatic branch, i.e., either of BEFA command output that was not met, or of WSB step-on branch. Indication of faulty cascade. Monitoring time and wait time elapse on the basis of the default values. 1070 072 168-101 (98.04) GB 4-30 MMI-MADAP PLC Software Automatic mode Function Automatic processing of steps in accordance with conditions applying to automatic branch. Command output occurs if the following applies: • The conditions of the manual branch are met (BEFA command output = HIGH and WSB step-on condition = LOW ) AND • The Start (D6.3 ) = HIGH The command output occurs via the data bits of data words D80 through D94 of the associated cascade data module (refer to cascade data module). If WSB step-on condition = HIGH, automatic step-on will occur. Programming Set Automatic mode (D6.2) and Start (D6.3) bits to HIGH. Diagnostics Display in cascade information, A for Automatic mode, in the respective cascade. Display of all criteria of automatic branch, i.e., either of BEFA command output that was not met, or of WSB step-on branch. Indication of faulty cascade. Monitoring time and wait time elapse on the basis of the default values. 1070 072 168-101 (98.04) GB MMI-MADAP PLC Software 4-31 D6, Selected operating mode In addition to the operating modes discussed in the preceding section, data word D6 of the cascade data module contains further operating mode selection information. D6, nnBaWahl This data word is written to via the -BETR (P1) parameter of the KETTE module. D6.0 D6.1 D6.2 D6.3* D6.4 D6.5* D6.6 D6.7 D7.0 D7.1* D7.2 D7.3 D7.4 D7.5 D7.6 D7.7 * Manual mode H Inching mode T Automatic mode A Start s S+1 Set Step Fault acknowledgement Reset r Halt h Synchronization Cascade data module generation No step-on in same cycle WSB does not reset BEFA (Manual mode only) Fault requires acknowledgement Observe bit description )LJ'²6HOHFWHG2SHUDWLQJ0RGH %LWGHVFULSWLRQ D6.0, Manual mode Select Manual mode D6.1, Inching mode Select Inching mode D6.2, Automatic mode Select Automatic mode 1070 072 168-101 (98.04) GB 4-32 MMI-MADAP PLC Software D6.3, Start Start/Command enable The bit is valid for all operating modes, and is statically transferred to parameter P1 of the KETTE module. If Start = LOW, the following actions will occur: • BEFA command output is deleted, • the monitoring time is stopped, and • the wait time continues to elapse. Prior to generating the cascade data modules, and for the purpose of synchronizing in Automatic mode, the Start must be deleted. F In cascade data modules, MMI-MADAP sets data bit D24.2 (MADAP identifier bit). Thus in Manual mode, the Start operating mode bit on parameter P1.3 will be AND-linked with the MADAP Start operating mode bit D30.3, and only then returned in data word D6 (selected operating mode). D6.4, S+1 Executing the next step When in Inching mode, a positive transition of this bit and satisfied WSB step-on condition (WSB = HIGH), the next step will be executed. When in Semi-automatic mode, a positive transition of this bit and satisfied WSB step-on condition (WSB = HIGH), and with -HALBAUTO marker set, the next program sequence will be processed up to the reset -HALBAUTO marker. D6.5, Set step Adopting preselected step number In Manual mode, the step prepared in D14 is adopted into the active step (D12), and then executed. F In cascade data modules, MMI-MADAP sets data bit D24.2 (MADAP identifier bit). Thus in Manual mode, the Set Step operating mode bit on parameter P1.5 will be OR-linked with the MADAP Set Step operating mode bit D30.5, and only then returned in data word D6 (selected operating mode). 1070 072 168-101 (98.04) GB MMI-MADAP PLC Software 4-33 D6.6, Halt acknowledgement Manual error acknowledgement Effective only if D7.7 = HIGH (manual fault acknowledgement). A positive transition on this bit acknowledges a fault (cascade stop) that was triggered by a monitoring time-out or by the reset fault marker. Monitoring and wait time values are loaded along with the default values but are not started. D6.7, Reset Cascade reset If D6.7 = HIGH, the following actions will occur: • • • Deletion of active step, Reinitialization of cascade sequence, Recreation of cascade data module. Subsequent to a Reset, step 1 is prepared. D7.0, Halt Halting cascade processing If the bit is set, the cascade is halted, and the processing of the current step continues. If D7.0 = HIGH, the following will occur: • BEFA command output is returned, • Monitoring and wait times are halted. D7.1, Synchronization Synchronizing cascade This action is possible in manual and Automatic mode. In the case of Automatic mode, D6.3 = LOW will be additionally required. If this bit is set, the KETTE cascade management module will search the cascade for satisfied conditions, and subsequently synchronize the operating mode in accordance with the operating mode. The conditions for an effective synchronization are as follows: • • BEFA command output = HIGH and WSB step-on condition = LOW For all steps for which the synchronization requirements have been met, the corresponding bit in data block D48 through D62 is set. In the event that, in Automatic mode, exactly 1 step is found for which the synchronization conditions are satisfied, this step will be prepared. In the case of AND-links, because the cascades are examined independently of each other, there are limitations to the synchronization to Automatic mode. 1070 072 168-101 (98.04) GB 4-34 MMI-MADAP PLC Software F In cascade data modules, MMI-MADAP sets data bit D24.2 (MADAP identifier bit). Thus in Manual mode, the Synchronization operating mode bit on parameter P1.9 will be OR-linked with the MADAP Synchronization operating mode bit D31.1, and only then returned in data word D6 (selected operating mode). Function description: If a synchronization procedure is initiated via parameter P1.9 or D31.1, and if subsequently the D7.1 = HIGH, the synchronization result of this cascade (D9.1, No Synchronization Possible and/or D9.2, More Than One Synch Step) can already be interpreted. A subsequent synchronization initiation will be interpreted only if the system undergoes another – transition-controlled – LOW-to-HIGH change. D7.3, Learning Generating cascade data module When bit D7.3 is set, subsequent to loading the program, and following a Power-On or Reset command, the KETTE cascade management module will generate the data for the cascade modules. This cascade-specific data is determined on the basis of the corresponding step modules and of the parameterization in the KETTE module. As a prerequisite, D6.3 = LOW must be true. D7.4, Step-on (when using WinSPS control language, D7.4 = 0 must be true!) No step-on in same cycle Automatic mode only • • When D7.4 = LOW is true, only one step will be processed in each cycle. When D7.4 = HIGH is true, and WSB step-on condition is met, the next step will be activated during the same cycle. D7.6, WSB fails to reset BEFA Manual operation only • • When D7.6 = HIGH is true, even a satisfied WSB step-on condition will not reset the corresponding BEFA command output. When D7.6 = LOW is true, a satisfied WSB step-on condition will reset the associated BEFA command output. D7.7, Acknowledgement Fault acknowledgement If this bit is set, an occurring cascade fault must be acknowledged by bit D6.6. With bit D7.7 reset, and WSB step-on condition met, the cascade will auto-acknowledge. 1070 072 168-101 (98.04) GB MMI-MADAP PLC Software 4-35 Priority ranking of operating mode bits In the event that several operating mode bits are simultaneously selected in data word D6 of the cascade data module, the processing will be subject to the following priority ranking: 1. 2. 3. 4. 5. 6. Reset Halt Start Manual Inching Automatic highest priority ↓ ↓ ↓ ↓ lowest priority )LJ2SHUDWLQJ0RGH3ULRULWLHV D8, Confirmed operating mode Subsequent to processing the KETTE proigram module, data word D8 of each cascade data module contains the return confirmation of the operating mode. D8, nnBaMldg D8.0 D8.1 D8.2 D8.3 D8.4 D8.5 D8.6 D8.7 D9.0 D9.1 D9.2 D9.3 D9.4 D9.5 D9.6 D9.7 Manual mode H Inching mode T Automatic mode A Start, all operating modes s Automatic or Inching mode enabled Wait time active Reset, cascade reset r Halt, cascade halted h No synchronization possible More than one step with BEFA = HIGH, synchronizatiCascade data module generated Pulse fault Static fault )LJ'²&RQILUPHG2SHUDWLQJ0RGH Bit description D8.0, Manual mode Cascade is in Manual mode. Display H appears in cascade information of operator terminal. D8.1, Inching mode Cascade is in Inching mode. Display T appears in cascade information of operator terminal. D8.2, Automatic mode Cascade is in Automatic mode. Display A appears in cascade information of operator terminal. 1070 072 168-101 (98.04) GB 4-36 MMI-MADAP PLC Software D8.3, Start Cascade has received the start bit. Display s appears in cascade information of operator terminal. D8.4, Automatic/Inching Cascade is in Automatic or Inching mode. This bit is used to select whether the Manual or Automatic branch is to be processed in the cascade module. If D8.4 = HIGH is true, Automatic or Inching mode is enabled. If D8.4 = LOW is true, Manual mode is enabled. D8.6, Wait time active If this bit is set, this indicates that the wait time for this step has expired. Prior to calling this step, the cascade management module writes the status of this bit into the WZT wait time marker (M255.6), thus making the wait time available to the steps as a diagnosable operand. If the wait time has expired, the query: • A B will return HIGH -WZT D8.7, Reset cascade The cascade is reset, and the active step deleted (subsequent to Reset, D12 = HIGH is true). D9.0, Cascade halted Cascade is in Halt status. This operating mode is activated by: • • • D7.0 = HIGH (Halt) Reset of M255.2 fault marker, OR Fault in Automatic mode, with expired monitoring time (only with manual acknowledgement via D7.7 = HIGH). 1070 072 168-101 (98.04) GB MMI-MADAP PLC Software 4-37 D9.1, No Synchronization Possible In none of the scanned steps, the • BEFA command output = HIGH and • WSB step-on condition = LOW synchronization conditions have been met. D9.2, More Than One Synch Step During synchronization in Automatic mode, more than one step was found in which BEFA = HIGH and WSB = LOW were true. The Auto Continue synchronized start of Automatic mode is not possible. D9.3, Cascade data module generated With D9.3 = HIGH being true, the learning or generating of the data module will be concluded. D9.6, Pulse fault Returns a pulse for a given PLC cycle in the event that a fault was recognized. Fault criteria: • Reset fault marker OR • Monitoring time expired. D9.7, Static fault Returns a static signal upon fault detection (criteria as for D9.6). The bit is reset by: • Fault acknowledgement OR • 1070 072 168-101 (98.04) GB An action subsequent to a change in operating mode (e.g. Set Step in Manual mode). 4-38 MMI-MADAP PLC Software 4.5.4 Step module For each cascade, a -SCHRKn (1 ≤ n ≤ 64) step module is generated. The step module contains, for all controller types: • the jump distributor to the active step AND • a maximum of 128 steps. Step module processing always begins with the jump distributor line belonging to the active step. From here, the jump to the actual step conditions is effected. Only the active step is processed. As a rule, the step consists of 2 independent program parts: • • the Manual part with the manual conditions, and the Automatic part with the Automatic and/or Inching conditions. Both program parts must be individually concluded with an EM end-ofmodule instruction. If the same conditions apply to Manual and Automatic mode, only one part will have to be programmed. Both the Manual and Automatic part are again divide into: • a BEFA command output branch AND • a step-on condition branch An arbitrary number of BEFA command output and WSB step-on branches can be programmed. However, the instruction: = - BEFA and/or = - WSB must be the last instruction in a given branch. When diagnosing processing faults, the display always indicates the first BEFA branch for which the conditions are not met, starting from the start of the step. If conditions for all BEFA branches are met, the first nonsatisfied WSB branch will be displayed. 1070 072 168-101 (98.04) GB MMI-MADAP PLC Software 4-39 5XOHVIRUVWHSSURJUDPPLQJ * * * * * * * * * * Only unconditional jumps may be programmed in the jump distributor! The jump sequence must match the sequence of jump destinations! Nor other instructions are permitted prior to the jump distributor. The jump distributor must contain SP [A] as its first instruction! The jump distributor may not be interrupted by other instructions! Only jump destinations or comments may be inserted between the command SP [A] and the first jump destination. There are no control characters for program segmentation permitted here! The number of jumps in the jump distributor must correspond to the number of scheduled steps! Otherwise, no diagnostics will be possible! A module call from within a -SCHRKn step module is not permitted! The jump distributor and/or the jump destinations in the SCHRKn step module must not be changed with the use of the Replace function! Non-bit instructions (e.g. links and time manipulation) must be programmed at the beginning of the branch. Scratch markers and special markers in step modules may cause unpredictable diagnostic results (wait time, too, is a scratch marker). In the event that different criteria are programmed for the Manual and Automatic branch in a given step, both Manual branch and Automatic branch must be concluded with an EM end-of-module instruction. Example The supplied standard software provides a programming example for the step module for KETTE1. This can be integrated into your own program and modified/expanded to suit your requirements. 1070 072 168-101 (98.04) GB 4-40 MMI-MADAP PLC Software Example of step module structure: -XPSGLVWULEXWRUWRDFWLYHVWHSPDQGDWRU\DWVWDUWRIPRGXOH -3>$@5HDGVDFWLYHVWHSDQGFRPPHQFHVMXPS WRVWHS -36FKULWWWR6WHS -36FKULWWWR6WHS 6FKULWW '()':D=HLW:DLWWLPHYDOXH '()'8H=HLW0RQLWRULQJWLPHYDOXH &KDQJLQJZDLWWLPHIRUWKLVVWHS /:.$VZDLWWLPH:DLWWLPH!0RQLWRULQJWLPH)DXOW 7:$:D=HLW:DLWWLPHGDWDZRUG &KDQJLQJPRQLWRULQJWLPHIRUWKLVVWHS /:.$VPRQLWRULQJWLPH:DLWWLPH!0RQLWWLPH)DXOW 7:$8H=HLW0RQLWRULQJWLPHGDWDZRUG $XWRPDWLFRU,QFKLQJHQDEOHG" /:'$2SHUDWLQJPRGHFRQILUPDWLRQIURP.(77(PRGXOH $%$ -3&$XWRDW$XWRPDWLFFRQGLWLRQVRI6WHS 0DQXDOFRQGLWLRQVIRU6WHS $%.6+%HI(.HWWH6WHS%()$0DQXDOFRQGLWLRQ %%()$0FRPPDQGRXWSXW $%.6+:6%(.HWWH6WHS:6%0DQXDOFRQGLWLRQ %:6%06WHSRQFRQGLWLRQ (0 :6%(0'HILQHGIRUPDOLVPDWHQGRIVWHS $XWR $XWRPDWLFFRQGLWLRQVIRU6WHS 8%.6$%HI(.HWWH6WHS%()$$XWRPDWLFFRQGLWLRQ %%()$0&RPPDQGRXWSXW 8%.6$:6%(.HWWH6WHS:6%$XWRPDWLFFRQGLWLRQ 2%:=70:DLWWLPHPDUNHUVWDWXV %:6%06WHSRQFRQGLWLRQ (0 :6%(0'HILQHGIRUPDOLVPDWHQGRIVWHS 6FKULWW $XWRPDWLFFRQGLWLRQVIRU6WHS $%.6$%HI(.HWWH6WHS%()$$XWRPDWLFFRQGLWLRQ %%()$0&RPPDQGRXWSXW $%.6$:6%(.HWWH6WHS:6%$XWRPDWLFFRQGLWLRQ 2%:=70:DLWWLPHPDUNHUVWDWXV %:6%06WHSRQFRQGLWLRQ (0 :6%(0'HILQHGIRUPDOLVPDWHQGRIVWHS )LJ([DPSOHRI6WHS0RGXOH If a given step is identical with regard to Manual and Automatic mode movements, the operating mode selection may be omitted (as in Step 2 in this example). 1070 072 168-101 (98.04) GB MMI-MADAP PLC Software 4-41 4.5.5 Command Output It makes good sense to arrange the command output immedately following the call-up of the KETTE cascade management module. This purpose is served by the KETTEn module (with 1 ≤ n ≤ 64) which handle the command output subsequent to completed processing of the KETTE cascade management module. This requires the corresponding data word (D80 through D94) for command output to be loaded. When using the KETTE module with version 2.5 and higher, the command output can also handled via data word D16. Example of utilization of data words D80 through D94 Command output for a cascade (KETTE1) containing two steps: 3DUDPHWHUL]DWLRQDQGPRGXOHFDOO '().3%'% '()..8( '()..:$ &0.(77( 3:3%'%&DVFDGHQXPEHU 3:%(752SHUDWLQJPRGH 3:.8(0RQLWRULQJWLPH 3:.:$:DLWWLPH &RPPDQGRXWSXWSURJUDPPLQJ '()'%'%.HWW '()'%()$&RPPDQGH[HFXWLRQELWV6WHSWKUX '()$%()$86&RPPDQGRXWSXW6WHS '()$%()$86&RPPDQGRXWSXW6WHS &0'%.HWW /:%()$$ 6WHS $%$%()$FRPPDQGRXWSXW6WHS %%()$86(QDEOHRXWSXW 6WHS $%$%()$FRPPDQGRXWSXW6WHS %%()$86(QDEOHRXWSXW (0 )LJ&DVFDGH&RPPDQG2XWSXWYLD'DWD:RUGV'WKURXJK' Subsequent to calling the KETTE module, these command output program instructions must be repeated for all active cascades and for all steps in the corresponding KETTE1 through KETTE64 modules. 1070 072 168-101 (98.04) GB 4-42 MMI-MADAP PLC Software The supplied standard software contains a programming example for the cascade management module of Kette1. You can copy this example into your own program, and modify or expand it to suit your requirements. Example of utilization of data word D16 This version is supported by the WinSPS programming device software with SFC, and requires KETTE program module, version 2.5 and higher. Command output for a cascade (KETTE1) containing two steps: 3DUDPHWHUL]DWLRQDQGPRGXOHFDOO '().3%'% '()..8( '()..:$ &0.(77( 3:3%'%&DVFDGHQXPEHU 3:%(752SHUDWLQJPRGH 3:.8(0RQLWRULQJWLPH 3:.:$:DLWWLPH &RPPDQGRXWSXWSURJUDPPLQJ '()'%'%.HWW '()'%()$86*&RPPDQGH[HFXWLRQZRUGIRUDOOVWHSV '()$%()$86&RPPDQGRXWSXW6WHS '()$%()$86&RPPDQGRXWSXW6WHS &0'%.HWW /:%()$86*$ 6WHS &3/$:.$ $%60$ %()$FRPPDQGRXWSXW6WHS %%()$86(QDEOHRXWSXW 6FKULWW 9*/$:.$ $%60$ %()$FRPPDQGRXWSXW6WHS %%()$86(QDEOHRXWSXW (0 )LJ&DVFDGH&RPPDQG2XWSXWYLD'DWD:RUG' 1070 072 168-101 (98.04) GB MMI-MADAP PLC Software 4-43 4.5.6 Cascade Data Module The data modules DM1 through DM64 handle the sequential control, and furnish all data essential to system control. The data module must be created for each step module. Symbol Explanation Data format Entry caused by: K: KETTE M: MMI-MADAP A: USER D00 D02 D04 D06 D08 D10 D12 D14 D16 D18 D20 D22 D24 nnFehler nnKettNr nnSchAnz nnBaWahl nnBaMldg nnSchr-1 nnSchr. nnSchr.S nnBEFA nn-KWA nn-KUE nnINT0 nnINT1 binary decimal decimal binary binary decimal decimal decimal decimal dec. x 100 ms dec. x 100 ms K K K K K K K M K K/A K/A binary M D26 D28 D30 D32 :: D48 :: D62 D64 :: D78 D80 :: D94 nnINT2 nnINT3 nnBa_Ext nnINT4 :: nnSyn16 :: nnSyn128 nnSch16 :: nnSch128 nnBef16 :: nnBef128 Error bits Cascade no. n (1-64) Number of steps in cascade Operating mode selection Confirmed operating mode Step number, preceding step Step number, current step Step number, Set Step Command output for all steps Wait time, actual value Monitoring time, actual value internal use internal use Bit 2 MADAP active bit internal use internal use Operating mode selection for external operator terminals internal use internal use Synchronization steps 1 thru 16 :: Synchronization steps 113 thru 128 Steps 1 thru 16 :: Steps 113 thru 128 Command output, steps 1 through 16 :: Command output, steps 113 thru 128 binary M binary K K K K K K K K K )LJ&DVFDGH'DWD0RGXOH 1070 072 168-101 (98.04) GB binary binary binary binary binary 4-44 MMI-MADAP PLC Software D0 Data word assignment Error and/or Status message 15 Structural fault in cascade module Bit Troubleshooting 14 The structure of the jump distributor fails to correspond to the sequence of programmed steps. Cascade runs correctly but diagnostics are not possible. → Correct cascade structure. Reserved thru 4 3 Jump sequence error 2 Reference list 1 Step module (PM) not available 0 Number of steps too high or zero The first instruction to appear in the step module must be the jump instruction: SP [A] Only jump instruction or comment lines may be inserted between above instruction and the first jump instruction, e.g.: -S1 CAUTION: Program segmentation! → Correct program. The existing module is faulty. → Recompile and load program. The program module PMn assigned to a defined data module DMn is not available. → Ensure linking of required module. Number of steps must be between > 0 and ≤ 128. → Correct program. )LJ(UURU:RUGLQ&DVFDGH'DWD0RGXOH Interpretation of wait time and monitoring time (D18, D20) Upon jump entry into a new step, the KETTE module verifies whether or not the actual values for wait time and monitoring time (D18, D20) were set by the application program. In the case of values unequal zero, these will be interpreted as program lines that are valid for the active step. Otherwise, the time defaults will be taken from parameters P2 and P3 of the KETTE cascade management module. 1070 072 168-101 (98.04) GB MMI-MADAP PLC Software 4-45 4.6 Machine Usage 4.6.1 Definitions Introduction The Machine Usage function is used for recording production data and for creating production statistics. As a contribution to this statistical logging function, the production times for the three-shift operating with 6 work breaks each can be entered directly at the BT100 operator terminal. The data recording utilizes seven standardized recording parameters, as well as logic links. Recording parameters: • • • • • • • Machine On Production Parts Count Fault No Parts Buffer Full Standstill (Daily logging) (Shift-specific and daily logging) (Shift-specific logging) (Daily logging) (Daily logging) (Daily logging) (Daily logging) Actual piece-count logging occurs in terms of absolute numbers as well as in terms of a percentage value of the nominal (or setpoint) piece count. A maximum of 65535 pieces/parts can be counted in a single work-shift period. All other parameter values are logged on a time base and calculated in percentages. The value of 100 % forming the basis is calculated as follows: Effective work time = shift length minus total breaks. This means that production values in excess of 100 % can also occur in the event that the machine continues producing during break times. The recorded data will be stored in the PLC for a period of 14 days. The data for the current day (today) and the previous day (yesterday) is transferred to the BT100 operator terminal, where it will be statistically recorded and evaluated. The time period for which data may be stored on the BT100 can be freely defined by the user, and is limited only by the unit’s hard drive capacity. • • • • • The operator terminal provides the following functions: Bar graph display of recorded data Display of current production day Display of individual work shifts. Curve plotting of current production process or encompassing a definable historic time period • Trend data exportability to standard software applications 1070 072 168-101 (98.04) GB 4-46 MMI-MADAP PLC Software 4.6.2 Programming The Machine Usage function module comprises 6 program modules and 2 data modules. Of the supplied modules, you will only be required to program the call-up and parameterization of the MMIAUSL module. All other modules are merely entered in the module list. Basic modules: • • • • • MMILOGIK MMISTCK MMIPROZ MMISCHT MMISTAT Logical links for recording parameters Parts count recording Percentage recording Work shift data recording Recording statistical data (e.g. calendar date) A special feature is the basic MMILOGIK module. In the event that the logics as supplied do not meet your needs, you can adapt MMILOGIK to your requirements (refer also to the section entitled, "MMILOGIK – Machine usage recording logics" further on in this chapter). Program structure OM1 Administration module ; Machine usage CM MMIAUSL MMIAUSL MMILOGIK DM218 Data recording for: MMIPROZ Machine usage data 1 - Machine On MMISCHT DM219 - Production MMISTAT Machine usage data 2 - No Parts MMISTCK - Buffer full - Fault - Part Count )LJ3URJUDP6WUXFWXUH0DFKLQH8VDJH)XQFWLRQV Refer to Chapter 4, "Interfaces — PLC <–> Operator Terminals," for the following information: Contents of DB218 data module "Auslast1" = Machine usage data 1 Contents of DB219 data module "Auslast2" = Machine usage data 2 Example The supplied standard software contains, for the module call, a programming example in the form of linked program segments in the OM1. You can copy this example from the OM1 into your own program. 1070 072 168-101 (98.04) GB MMI-MADAP PLC Software Module call 3DUDPHWHUL]DWLRQRI00,$86/PDFKLQHXVDJHPRGXOH 3DUDPHWHU37KLVSDUDPHWHUVWRUHVWKHUHFRUGLQJELWVWDWXVHV ZKHUHLQGLYLGXDOELWVKDYHWKHIROORZLQJPHDQLQJ %LW0DFKLQH2Q %LW3URGXFWLRQ %LW1R3DUWV %LW%XIIHU)XOO %LW)DXOW %LWXQXVHG %LW3LHFH&RXQWPDFKLQHF\FOHFRXQWHU %LW'HOHWHDOOUHFRUGHGGDWD 3DUDPHWHU30XOWLSOLHUYDOXHLIPRUHWKDQRQHSLHFHLVSURGXFHG SHUPDFKLQHF\FOHPD[ 7KHJRYHUQLQJORJLFVDUHSURJUDPPHGLQWKHLQWHUQDOO\FDOOHG00,/2*,. PRGXOHDQGFDQEHDGDSWHGWR\RXUV\VWHP ZKLOHUHWDLQLQJWKHVDPHILOHQDPH 3DUDPHWHUV3WKURXJK3GHQRWHEDVLFPRGXOHV DQGVKRXOGQRWEHPRGLILHG 3URFHVVLQJPDFKLQHXVDJHSDUDPHWHUVIRU3 DQG3 '().[[[08/7&RXQWXS[[[SLHFHVSHUPDFKLQHF\FOH '()<<<$86/'$72SHUDQGUHFRUGLQJSDUDPHWHUV 3UHSDUHUHFRUGLQJSDUDPHWHUV &000,$86/ 3%<$86/'$70DFKLQHXVDJHGDWDUHVKDSHGE\VXSSOLHGORJLFV 3%<08/70XOWLSOLHUQSLHFHVPDFKLQHF\FOH 3:00,/2*,.0RGXOHIRUSURFHVVLQJUHFRUGHGGDWD 3:00,67&.0RGXOHIRUUHFRUGLQJSLHFHFRXQWGDWD 3:00,352=0RGXOHIRUUHFRUGLQJSHUFHQWDJHGDWD 3:00,6&+70RGXOHIRUGHILQLQJZRUNVKLIWGDWD 3:00,67$70RGXOHIRUUHFRUGLQJVWDWLVWLFDOGDWDQRPLQDOFRXQW )LJ0RGXOH&DOO00,$86/3URJUDP0RGXOH 1070 072 168-101 (98.04) GB 4-47 4-48 MMI-MADAP PLC Software Parameter description In the DEF lines for the P0 and P1 module parameters preceding the module call, you enter the constants and/or operands that are designated for this function in your program. P0 BY -AUSLDAT Here you enter the operand that contains the recording parameters. The recording parameters are provided by yourself, transformed according to logic supplied by MMILOGIK program module, and subsequently stored. To facilitate recording of each counting pulse, Bit 6, handling the piece count function, must show /2: and/or +,*+ status for at least 4 PLC cycles! Only a /2: byte is permitted as a parameter. The byte is read and transformed, and the result is loaded into the +,*+ byte. This means that the +,*+ byte may not be continued to be used for any other purpose! P1 BY -MULT Here you enter the factor (1-255) by which each piece count pulse (bit 6 of parameter P0) is to be multiplied. This will become effective whenever more than one piece per machine cycle is being produced. P2 W -MMILOGIK Symbolic name of basic module. The entry must not be changed. P3 W -MMISTCK Symbolic name of basic module. The entry must not be changed. P4 W -MMIPROZ Symbolic name of basic module. The entry must not be changed. P5 W -MMISCHT Symbolic name of basic module. The entry must not be changed. P6 W -MMISTAT Symbolic name of basic module. The entry must not be changed. 1070 072 168-101 (98.04) GB MMI-MADAP PLC Software 4-49 Machine usage recording logic MMILOGIK This module transforms the recording parameters applied to parameter P0 (LOW byte of an operand) of the MMIAUSL program module, and loads the result into the free HIGH byte of this operand (refer to description of MMIAUSL, parameter P0). If another logic is to be processed, this module can be modified by yourself as required. Module contents ___ 75$16)250$7,212)0$&+,1(67$786(6,172(1$%/(6)25 5(&25',1*0$&+,1(67$786(6,1$&&25'$1&(:,7+'()$8/7/2*,& 7KLVPRGXOHLVFDOOHGIURPZLWKLQWKH00,$86/PRGXOH 5($'0$&+,1(67$786(6$6',*,7$/,1)250$7,21 'HIDXOWELWV '()00DVFKBH '()03URGXNW '()0NB7HLOH '()03XIIHUBY '()06WRHUXQJ '()006WRH '()00=\NO '()0ORHVFK 5HFRUGLQJELWV '()00$6&+B( '()0352'8.7 '()0.B7(,/( '()038))(5B9 '()0672(581* '()067,//67 '()0678(&. '()0/2(6&+ /:3$,1387,1)250$7,21 7:$0216&5$7&+0$5.(5 __0DFKLQH2Q_ 0$6&+B(0 0DVFKBH 0$6&+B(0DVFKBH0 __3URGXFWLRQ_ 0DVFKBH0 3URGXNW_352'8.70 0DVFKBH_3URGXNW0 NB7HLOH2_3XIIHUBY0 3XIIHUBY2_672(581*0 672(581*2 352'8.7NB7HLOH0 1070 072 168-101 (98.04) GB 4-50 MMI-MADAP PLC Software __)DXOW_ 06WRH06WRH0 6WRHUXQJ2_3URGXNW0 3URGXNW5_672(581*0 __6WRHUXQJ0 __ 6WRHUXQJ___ 3URGXNW64 672(581* __1R3DUWV_ .B7(,/(0 NB7HLOH_0DVFKBH0 0DVFKBH_3URGXNW0 3URGXNW_672(581*0 672(581*2 .B7(,/(NB7HLOH0 __%XIIHU)XOO_ 0DVFKBH0 3XIIHUBY_38))(5B90 0DVFKBH_3URGXNW0 3URGXNW_3XIIHUBY0 672(581*2_672(581*0 NB7HLOH2 38))(5B9NB7HLOH0 __6WDQGVWLOO_ 0DVFKBH0 672(581*2_3URGXNW0 3URGXNW2_67,//670 0DVFKBH 67,//67672(581*0 __3LHFHFRXQWPDFKLQHF\FOHV_ 0=\NO0 0=\NO 678(&.678(&.0 __'HOHWLQJDOOUHFRUGHGYDOXHV_ /2(6&+0 ORHVFK /2(6&+ORHVFK0 __2XWSXWRIWUDQVIRUPHGYDOXHHQGRIPRGXOH_ /:0$/2:%\WH 'HIDXOW+,*+%\WH WUDQVIRUPHGGHIDXOW 7:$3 (1'2)02'8/( (0 )LJ00,/2*,.0RGXOH&RQWHQWV 1070 072 168-101 (98.04) GB MMI-MADAP PLC Software 4-51 4.7 Machine Cycle Times 4.7.1 Definitions The MMI-MADAP software provides you with the power to manage 48 machine cycle times. The timekeeping resolution can be set to either 0.1 or 1.0 sec. The respective measuring times are formed in basic program modules. Measuring and storage of cycle times is handled by data module DM217. The timers T117 (0.1 sec cycle) and T118 (1.0 sec cycle) are used for time determination. You may therefore not used these times. To select the measuring accuracy (resolution), the DM217 data module defines one data bit for each cycle time. The incrementation of times is effected by releasing and disabling of defined start bits. The readings thus determined are transferred to the associated display values via the stop bits. They are subsequently deleted in order to enable the transfer of new measurements. You will be required to manage and control the program-specific treatment of the start and stop bits. 4.7.2 Programming Program structure OM1 Administration module ; Machine cycle times CM MMI_TZ MMI_TZ Data recording for: DB217 48 cycle times Data for cycle times MMI_T01S MMI_T1S )LJ3URJUDP6WUXFWXUH0DFKLQH&\FOH7LPHV Refer to Chapter 4, "Interfaces — PLC <–> Operator Terminals," for the following information: DM217 "Cycle Times" data module contents: Machine cycle times Example The supplied standard software contains the following programming example in the form of linked program segments in the OM1. You can copy this example from the OM1 into your own program, and modify it to suit your requirements. 1070 072 168-101 (98.04) GB 4-52 MMI-MADAP PLC Software Program example This module calls submodules that merely require entry in the module list, and that do not expect any further activities. Submodules: MMI_T01S and MMI_T1S. 0RGXOHIRUF\FOHWLPHPDQDJHPHQW &DQEHXVHGWRJHQHUDWHXSWRF\FOHWLPHV ,QWKHHYHQWWKDWF\FOHWLPHVZLWKDWLPHEDVHRIVHFDQGVHFDUH WREHSURFHVVHGWKHPRGXOHPXVWEHFDOOHGWLPHVZLWKSDUDPHWHU3 GHILQLQJWKHUHFRUGLQJF\FOH&RQWLQJHQWXSRQWKHGHILQLWLRQRI3RQO\ WKRVHWLPHVIRUZKLFKWKHWLPHEDVHELWZDVDSSURSULDWHO\VHWDUHSURFHVVHG 7KHUHFRUGLQJRIDF\FOHWLPHLQFURIPHDVXULQJWLPHLVFRQWUROOHGVWDUWHG DQGRUVWRSSHGE\WKHFRUUHVSRQGLQJVWDUWELW 7KHGLVSOD\RIDF\FOHWLPHLVXSGDWHGE\VHWWLQJWKHDSSURSULDWHVWRSELW ZLWKVLPXOWDQHRXVGHOHWLRQRIWKHPHDVXULQJWLPH &RQWUROOLQJWLPHUHFRUGLQJIRUF\FOHWLPHV&7 &07DNW]HLW 1XPEHURIF\FOHWLPHVWREHSURFHVVHG '()'7=$Q] /:.$3URFHVVF\FOHWLPHV 7:$7=$Q] 7LPHEDVHELWV '()'%DV7LPHEDVHELWVF\FOHWLPHVWKUX /:.+$%LW !&7UHDGVH[DFWO\VHF 7:$%DV%LW !&7UHDGVH[DFWO\VHF 6WDUWELWV '()'6WD6WDUWPHDVXULQJWLPHV&7WKUX '()(6WD6WDUWELW&7 '()(6WD6WDUWELW&7 /:6WD$ $%6WD 20%$ $%6WD 20%$ 7:$6WD 6WRSELWV '()'6WS:ULWHGLVSOD\YDOXHGHOHWHPHDVXULQJWLPH '()(6WS6WRSELW&7 '()(6WS6WRSELW&7 '()0)O)ODQNPDUNHU&7 '()0)O)ODQNPDUNHU&7 GHOHWHF\FOLFDOO\ /:.$ 7:$6WS 1070 072 168-101 (98.04) GB MMI-MADAP PLC Software 8SGDWH&7IRUGLVSOD\ $1%6WS 5%)O $1%6WS 2%)O -3&QRVWS $1%)O 6%)O /:6WS$ 6:0%$ 7:$6WS QRVWS 8SGDWH&7IRUGLVSOD\ $1%6WS 5%)O $1%6WS 2%)O -3&QRVWS $1%)O 6%)O /:6WS$ 6:0%$ 7:$6WS QRVWS '()60ORJ '()60ORJ '()(ORHVFK '()07DNWV '()07DNWV &DOOXSIRUF\FOHWLPHPHDVXUHPHQWVZLWKVHFWLPHEDVH %$00,B7= 3%ORJ&\FOHGHILQLWLRQ V V 3%ORHVFK'HOHWHDOOGLVSOD\DQGPHDVXUHGYDOXHV 3%7DNWV!&\FOHRXWSXWDVSXOVHDVGHILQHGLQ3 3:00,B760RGXOHQDPHIRUF\FOHJHQHUDWLRQVXVHV7 3:00,B760RGXOHQDPHIRUF\FOHJHQHUDWLRQVXVHV7 &DOOXSIRUF\FOHWLPHPHDVXUHPHQWVZLWKVHFWLPHEDVH %$00,B7= 3%ORJ!&\FOHGHILQLWLRQ V V 3%ORHVFK!'HOHWHDOOGLVSOD\DQGPHDVXUHGYDOXHV 3%7DNWV!&\FOHRXWSXWDVSXOVHDVGHILQHGLQ3 3:00,B760RGXOHQDPHIRUF\FOHJHQHUDWLRQVXVHV7 3:00,B760RGXOHQDPHIRUF\FOHJHQHUDWLRQVXVHV7 )LJ3URJUDP([DPSOH0DFKLQH&\FOH7LPHV 1070 072 168-101 (98.04) GB 4-53 4-54 MMI-MADAP PLC Software 4.8 Decoding BT100 Movement and Function Keys 4.8.1 Definitions As the BT100 operator responds to the actuation of a movement or function key by sending an 8-bit code to the PLC, this code must be converted (8 bits in 1 of 16) in order to ensure fault-free operation of the PLC program. 4.8.2 Programming Program structure OM1 Administration module ; Key decoding CM BT100DEC BT100DEC Key decoding in 1 of 16 )LJ3URJUDP6WUXFWXUH.H\'HFRGLQJ Example The supplied standard software contains a programming example in the form of linked program segments in the OM1. You can copy this example from the OM1 into your own program. Module call 'HFRGLQJWKHFRGHVIRU%7PRYHPHQWDQGIXQFWLRQNH\V '();;;7DVW&RGH.H\FRGHIURPWHUPLQDOSDQHO '()<<<%HZ7DVWGHFRGHGPRYHPHQWNH\V '()')NW7DVWGHFRGHGIXQFWLRQNH\V '()'%%)B'%&RPPXQLFDWLRQDQGGLVSOD\GDWDIRU%7 &0%)B'%&RPPXQLFDWLRQDQGGLVSOD\GDWDIRU%7 &0%7'(&%7NH\GHFRGLQJ 3%<7DVW&RGH.H\FRGHIURP%7 3:)NW7DVW!DFWXDWHGIXQFWLRQNH\RI 3:%HZ7DVW!DFWXDWHGPRYHPHQWNH\RI )LJ0RGXOH&DOOIRU%7'(&3URJUDP0RGXOH 1070 072 168-101 (98.04) GB MMI-MADAP PLC Software 4-55 Parameter description In the DEF lines for the module parameters preceding the module call, you can enter the operands that are defined for this function in your program. In the event that you want to operate several operator terminals on a single central processing unit, you will be required to call this module once for each operator terminal (BF). In this case the identifier for the data module assigned to the respective operator terminal must be entered. DEF BA DB230,-BF1_DB -BF1_DB ; Communication/display data ; ... for BF1 DEF BA DB235,-BF2_DB -BF2_DB ; Communication/display data ; ... for BF2 DEF BA DB230,-BF3_DB -BF3_DB ; Communication/display data ; ... for BF3 DEF BA DB230,-BF4_DB -BF4_DB ; Communication/display data ; ... for BF4 P0 BY -TastCode The parameter P0 will be assigned the operand to which the operator terminal will send the encoded 8-bit signal representing the actuation of function and/or movement key. P1 W -FktTast Parameter P1 outputs the decoded function keys (1 of 16). P1 is copied into data word D300 of the data module assigned to the selected operator terminal. This causes any movement to be blocked while a movement screen is being changed. In the context of MMI-MADAP standard software functions, the decoded function keys are not used for any other purpose. NOTE: If you are using another type of decoding module, you must ensure that each actuation of a function key is signalled to data word D300 of the data module that is assigned to the selected operator terminal. Definition for decoding (FK = function key): FK1 = Bit 0 ... FK16 = Bit 15 P2 W -BewTast Parameter P2 contains the decoded movement keys (1 of 16). To effect operator terminal linking, apply the movement keys to input parameter P3 of the MMI-MADAP program module described in the following section. Definition for decoding (MovK = movement key): MovK1 left = Bit 0 ... MovK8 left = Bit 7 MovK1 right = Bit 8 ... MovK8 right = Bit 15 1070 072 168-101 (98.04) GB 4-56 MMI-MADAP PLC Software 4.9 PROFIBUS-DP Diagnostics Principle 4.9.1 Definitions The PROFIBUS-DP provides a variety of diagnostic services among which the classified slave diagnostics represent the most important function. With the use of MMI-MADAP, the service is interpreted, displayed and stored in the protocol record. For this purpose, 3 data modules were defined; two of these handle data acquisition, and one provides display data. The program modules processing the PROFIBUS-DP diagnostics are designated DPSTATUS and FIFODM1. As these are library modules, you do not have to parameterize them. The calling module for the DPSTATUS module is MMIDESI. It processes and transfers the DPSTATUS parameters. 4.9.2 Programming Program structure OM1 Administration module ; DESI-DP-Diagnose CM MMIDESI MMIDESI DPSTATUS DM220 Parameter process. DP Diagnostics DM221 for DP Diagnostics processing DM254 to DB254 DP Diagnostic data FIFODM1 DP Diagnostics management )LJ3URJUDP6WUXFWXUH352),%86'3'LDJQRVWLFV Refer to Chapter 4, ""Interfaces — PLC <–> Operator Terminals," for the following information: DM220 "DP_Daten" data module contents: DESI-DP data DM221 "DP_Komm" data module contents: DESI-DP communication channel 1 DM254 "AL_DP_D" data module contents: Usage display and DPDiagnostics, Example The supplied standard software contains a programming example in the form of linked program segments in the OM1. You can copy this example from the OM1 into your own program. 1070 072 168-101 (98.04) GB MMI-MADAP PLC Software 4-57 Module call 0RGXOHFDOOFRPPXQLFDWLRQPRGXOHIRU%0'3352),%86'3EXVPDVWHU 7KLVPRGXOHKDQGOHVSDUDPHWHUSURFHVVLQJIRU'367$786SURJUDPPRGXOHDQG FRSLHVUHVXOWLQJGLDJQRVWLFGDWDLQWRFRPPXQLFDWLRQREMHFWLQ'0IRU SXUSRVHVRIGLVSOD\DQGVWRUDJHRQWKH00,0$'$3RSHUDWRUWHUPLQDO 'HILQLWLRQV '%&RPPXQLFDWLRQSDUDPHWHUL]DWLRQ '%&RPPXQLFDWLRQGDWD '%IURP'00,GLVSOD\GDWD '()..)$GU &000,'(6, 3:.)$GU(,(2VZLWFKLQJPDWUL[DGGUHVV )LJ0RGXOH&DOO00,'(6,3URJUDP0RGXOH Parameter description In the DEF lines for module parameter P0 preceding the module call, you enter the constant that corresponds to the switching matrix address at which you intend to operate the bus master. P0 W -.)$GU Switching matrix address at which the BM-DP12 is operated. Module contents In contrast to the other MMI-MADAP standard modules, the MMIDESI module is provided on the standard diskette in the form of an open module. Although you will link it to the program, you are not permitted to modify the module contents. 1070 072 168-101 (98.04) GB 4-58 MMI-MADAP PLC Software Major contents of DM254 data module "AL_DP_D": Usage display + DP diagnostics, as per EN 50170, part 2 (DP) D220 Global status Bit 0 Bit 1 Bit 2 Bit 3 Bit 3 Bit 5 Bit 6 Bit 7 Bit 8 Bit 9 Bit 10 Bit 11 Bit 12 Bit 13 Bit 14 Bit 15 : Bus master error : Classified slave diagnostics (MMI-MADAP standard) : System diagnostics : reserved : reserved : DP-Bus STOP by DP bus master : DP-Bus STOP by programming device : DP-Busmaster 1=active, 0=not ready : Slave(s) not reachable via DP bus : Slave(s) report configuration fault : Slave(s) report static diagnostics : Slave(s) report extended diagnostics : Slave(s) not ready for cyclical data exchange : Slave(s) report slave error : reserved : reserved Slave error messages D238.0-D253.7 D254.0-D269.7 D270.0-D285.7 D286.0-D301.7 D302.0-D317.7 D318.0-D333.7 Slaves not reachable Slaves report configuration fault Slaves report static diagnostics Slaves report extended diagnostics Slaves not ready for cyclical data exchange Slaves report slave error These message blocks contain 128 bits each, with the respective LSB being assigned to the programming device (address 0), and the next higher bit assigned to the bus master (address 1). Examples: D238.1 = 1, Bus master not reachable D256.0 = 1, Bus station 17 reports configuration fault D317.3 = 1, Bus station 124 not ready for data exchange 1070 072 168-101 (98.04) GB MMI-MADAP PLC Software 4-59 4.10 Operator Terminal Connectivity The purpose of the operator terminal connectivity module is to handle the communications between the PLC and the BT100 operator terminal. The communication data encompass the functions required for operation, sequential control diagnostics and visualization on the MMI-MADAP operator terminal. 4.10.1 Definitions The operator terminal connectivity module contains the MMIMADAP program module, plus the secondary DIAGMMI program module which does not require user parameterization, as well all data modules for the data interface. Without exception, the MMIMADAP program module is called for each MMI-MADAP operator terminal. Up to four MMI-MADAP operator terminals can be connected to each central processing unit. A cascade range-specific diagnostic routine occurs in conjunction with the DIAGMMI program module, thus facilitating the management of four independent stations per central processing unit. Display data for operator terminal The following data groups are processed for the MMI-MADAP operator terminal: • Power-up conditions • Manual movements with execution messages and execution enable • Status displays for all operands, for PLC configuration, for I/O assignment, for DM list, for PLC module version ID, as well as system date and time. • Machine usage with machine cycle times • Message systems for sequential processing faults, PROFIBUS-DP errors, PLC messages plus user messages. Data interface The data interface between the PLC and the BT100 operator terminal is handled by designated data modules. For a detailed discussion of these data interfaces, refer to Chapter 4, "Data Interfaces – PLC <-> Operator Terminals." 1070 072 168-101 (98.04) GB 4-60 MMI-MADAP PLC Software 4.10.2 Programming Program structure OM1 Administration module Monitoring ; Operator terminal 1 CM MMIMADAP :: ; Operator terminal 4 CM / Operating MMIMADAP DM230-DM232 Data processing for BT100 Communication and display data for operator terminal 1 MMIMADAP DM234: DiagDat Cascade diagnostic DIAGMMI data, station 1 Processing :: diagnostic data DM245-DB247 Communication and display data for operator terminal 4 DM249: DiagDat Cascade diagnostic data, station 4 DM253 I/O Assignment and SC table DM255 Global data valid for all operator terminals )LJ3URJUDP6WUXFWXUH2SHUDWRU7HUPLQDO&RQQHFWLYLW\ Example The supplied standard software contains, for the module call, a programming example in the form of linked program segments in the OM1 administration module. You can copy this example from the OM1 into your own program. 1070 072 168-101 (98.04) GB MMI-MADAP PLC Software 4-61 Module call Scratch markers must not be used in place of parameters! The module call is made from within the OM1 administration module. The module must be called for each MMI MADAP operator terminal. The module call is structured as follows: 0RGXOHFDOOIXQFWLRQPRGXOHIRURSHUDWLRQRIRSHUDWRUWHUPLQDO ,QWKHHYHQWWKDWVHYHUDORSHUDWRUWHUPLQDOVDUHWREHFRQQHFWHGPD[ WKLVPRGXOHPXVWEHFDOOHGIRUHDFKFRQQHFWHGWHUPLQDO '().%)1U '()..HWWB$Q] '()..B6WDUW '()(%7VSHUU &000,0$'$3 3:%)1U2SHUDWRUWHUPLQDOQRVWDUWLQJZLWK7QRJDSV 3:.HWWB$Q]1XPEHURIODVWFDVFDGH 3:.B6WDUW1XPEHURIILUVWFDVFDGH 3:%HZ7DVW0RYHPHQWNH\V+,*+E\WH 5LJKW/2:E\WH /HIW 7 %LW7 %LW 3:',$*00,',$*00,SURJUDPPRGXOH 3:.(77(&DVFDGHPRGXOHIRUYHUVLRQ,'RQO\ 3%%7VSHUU5HPRWHORFNLQJRIPRYHPHQWNH\V )LJ0RGXOH&DOO00,0$'$33URJUDP0RGXOH 1070 072 168-101 (98.04) GB 4-62 MMI-MADAP PLC Software Parameter description In the DEF lines for the module parameters preceding the module call, you can enter the operands that are defined for this function in your program. In the event that you want to operate several operator terminals on a single central processing unit, you will be required to call this module once for each operator terminal (BF). P0 W - BF-Nr1-4 Parameter P0 provides the module with the number of the current MMI-MADAP operator terminal. (Value range: integers 1 - 4, starting with 1, no gaps). The parameter may be assigned a default constant. P1 W -Kett_Anz Parameter P1 provides the module with the last cascade number that is valid for the MMI-MADAP operator terminal in parameter P0. (Value range: integers 1 - 64) The parameter P1/P2 will be required for the cascade-specific diagnostics function. The parameter may be assigned a default constant. P2 W -K_Start Parameter P2 provides the module with the first cascade number that is valid for the MMI-MADAP operator terminal in parameter P0. (Value range: integers 1 - 64) The parameter may be assigned a default constant. P3 W -BewTast Parameter P3 provides the module with the information regarding the 16 movement keys in the MMI-MADAP operator terminal. P3.0 Movement key 1 top left . P3.7 Movement key 8 bottom left P3.8 Movement key 1 top right . P3.15 Movement key 8 bottom right The manual movement keys of the MMI-MADAP operator terminal must be interpreted by the user, and must be made available to the MMI-MADAP module via parameter P3. 1070 072 168-101 (98.04) GB MMI-MADAP PLC Software P4 W -DIAGMMI Parameter P4 provides the module with the symbolic module name of the program module handling the diagnostic function. (Value range: symbolic name, 8 characters) Default name: -DIAGMMI. The symbolic name must be entered in the symbol file. The parameter is transferred as a symbol name. P5 W -KETTE Parameter P5 provides the module with the symbolic module name of the program module handling the sequential control. (Value range: symbolic name, 8 characters) Default name: -KETTE. The symbolic name must be entered in the symbol file. The parameter is transferred as a constant. P6 B -BTsperr Parameter P6 provides the module with a locking instruction for all movement keys. P6.0 = LOW , movement keys enabled, parameter P3 P6.0 = HIGH , movement keys disabled, parameter P3 With the aid of this bit parameter, the user can cause, independent of parameter P3, a centralized movement lock for all manual movement functions. The locked/disabled status is displayed on the MMI-MADAP operator terminal as Code 99. 1070 072 168-101 (98.04) GB 4-63 4-64 MMI-MADAP PLC Software Example Module call for MMIMADAP program module handling operator terminal 1. Cascades 1 through 12 are used for sequential control and diagnostics function. 0RGXOHFDOOIXQFWLRQPRGXOHIRURSHUDWLRQRIRSHUDWRUWHUPLQDO ,QWKHHYHQWWKDWVHYHUDORSHUDWRUWHUPLQDOVDUHWREHFRQQHFWHGPD[ WKLVPRGXOHPXVWEHFDOOHGIRUHDFKFRQQHFWHGWHUPLQDO '()0%HZ7DVW8VHUPDUNHUPRYHPHQWNH\V '().%)1U2SHUDWRUWHUPLQDOQR '()..HWWB$Q]ODVWFDVFDGH '()..B6WDUWILUVWFDVFDGH '()0%7VSHUU8VHUPDUNHUGLVDEOHPRYHPHQWV &000,0$'$3 3:%)1U2SHUDWRUWHUPLQDOQRVWDUWLQJZLWK7QRJDSV 3:.HWWB$Q]1XPEHURIODVWFDVFDGH 3:.B6WDUW1XPEHURIILUVWFDVFDGH 3:%HZ7DVW0RYHPHQWNH\V+,*+E\WH 5LJKW/2:E\WH /HIW 7 %LW7 %LW 3:',$*00,',$*00,SURJUDPPRGXOH 3:.(77(&DVFDGHPRGXOHIRUYHUVLRQ,'RQO\ 3%%7VSHUU5HPRWHORFNLQJRIPRYHPHQWNH\V )LJ0RGXOH&DOO00,0$'$33URJUDP0RGXOH Current data modules: • DM1 through DM12 Cascade data modules • DM230 Operator terminal data, operator terminal 1 • DM231 Status display data, operator terminal 1 • DM232 Movement locks, operator terminal 1 • DM233 User communications, operator terminal 1 • DM234 Diagnostic messages, operator terminal 1 • DM253 I/O assignment abd SC table • DM255 Global operator terminal data 1070 072 168-101 (98.04) GB MMI-MADAP PLC Software 4-65 4.11 Processing Fault Diagnostics 4.11.1 Definitions Introduction The DIAGMMI program module is managed in the MMIMADAP program module, and requires entry in the symbol files by the user. Criteria analysis The DIAGMMI program module is used to monitor a machine that is programmed in accordance with cascade sequencing technology. In the case of a fault, the monitored steps will be checked for non-satisfied step-on conditions. In case of a fault, the first branch for which conditions are not satisfied will be transferred to the diagnostic module as a diagnostic result. The search for the non-satisfied branch begins in the BEFA command output branch. The display of diagnostic results differentiates between Manual and Automatic mode. This diagnostic approach requires the step module structure as described in preceding sections. Diagnosable step-on conditions A given diagnostic step can contain a maximum of 64 step-on conditions for a BEFA command output or WSB step-on branch. If more than 64 step-on conditions are required, BEFA and/or WSB branches can be generated as often as required. 1070 072 168-101 (98.04) GB 4-66 MMI-MADAP PLC Software Programming example: A O . . = B B -Eingang1 -Eingang2 B -BEFA A A . . = B B -BEFA -Eingang3 B -BEFA In this case the diagnostics always investigate the first non-satisfied BEFA and/or WSB branch. The following instructions are permitted for the formation of step-on conditions: Bit instructions • A • O • AN • ON • S • R • = Special instructions • ( • ) • )N • Program segmentation commands (control codes) Permitted operands for link instructions: I O M T C SM Inputs Outputs Markers Times Counters Special markers I0.0 O0.0 M0.0 T0 C0 SM0.0 − − − − − − E63.7 A63.7 M255.7 T127 Z127 SM31.7 1070 072 168-101 (98.04) GB MMI-MADAP PLC Software 4-67 Definition of terms • )LVWYDOXHHUURU A system runs without problems when all cascades contributing to the program sequence (max. 64) are processed without error in Automatic mode. If an error occurs within a cascade, this will be recognized by the controller. As this error happens to be the one processing error to have occurred first in the system, it will be designated the first-value error. • 6HTXHQFHHUURU If a first-value error is present in the system, it may be assumed that additional cascades enter into a fault state. These failures are designated sequence errors. As a rule, sequence errors are of low significance because in most cases the system can be returned to normal operation by remedying the first-value error. Error entry criteria There are two ways in which an error occurrence (error entry) can be triggered in a given cascade: • 0RQLWRULQJWLPH Each step of the cascade performs a specific function. This function may a translate into a physical system movement, and it may also comprise a preparation of additional movements. Each function requires specific execution time which can be measured. The monitoring time function is used to control this time interval, and triggers an error entry in the event of a time overrun. • )DXOWPDUNHU In the case of time-critical faults, e.g. the opening of protective doors, it may not be possible to employ the monitoring time function in a useful manner. In this case, the occurrence of a fault will cause an immediate reset of the fault marker, triggering an instant error entry. 1070 072 168-101 (98.04) GB 4-68 MMI-MADAP PLC Software 4.11.2 Programming As this program module is called from within the MMIMADAP program module, it does not require specific attention on the part of the user. The module call for the program module is structured as follows: &0',$*00, 3%$+'LDJ$XWR'LDJQRVLV0DQXDOGLDJQRVLV 3%+$=ZJ'LDJQRVH0DQXDOEUDQFK$XWREUDQFK 3%<.HWW1U&DVFDGHQRIRU0DQXDOGLDJQRVLV'0[30[ 3%<.HWW$Q]/DVWFDVFDGHIRU$XWRGLDJQRVLV 3%<%DV.HWWH)LUVWFDVFDGHRIVWDWLRQ 3%<'LDJ0OGJ5HWXUQRIPRGXOHPHVVDJHV 3:'LDJ'%1XPEHURI'0LQZKLFKGLDJQRVWLFGDWDLVILOHG 3%<6WDWLRQ6WDWLRQ,'IRUGLVSOD\RQ00, )LJ0RGXOH&DOO',$*00,3URJUDP0RGXOH Description Any station, the cascade group of which is defined by the parameter range P3 to P4, can generate its own first-value error and cause it to be entered in the assigned data module. In the cascade information data, bit 11 is used to identify the Cascade Reports First-value Error message. In manual diagnostics, each cascade can be cursor-selected and subjected to analysis. The only permitted station numbers are numbers 1 through 8. The foregoing enables MMI-MADAP to label its own cascade group with a station number. The MMIMADAP module writes this number (local ID) into data byte D13 of the data module which is addressed by parameter P7. In addition, a data range encompassing 8 words is required, into which the cascade range for each station is entered, stating first and last cascade. D-Addr last cascade first cascade Comment D420 Status, 1 : : D434 Status, 8 The diagnostics module must be called for each cascade. 1070 072 168-101 (98.04) GB MMI-MADAP PLC Software 4-69 4.11.3 Storing Diagnostic Information In the data modules listed below, and optionally in the data modules DM222 through DM225 (substations 5 through 8), information about the current (active) first-value error is automatically stored in a specially designated data range (D0 - D148). • DM234 MMI-MADAP operator terminal 1 (base station 1) • DM239 MMI-MADAP operator terminal 2 (base station 2) • DM244 MMI-MADAP operator terminal 3 (base station 3) • DM249 MMI-MADAP operator terminal 4 (base station 4) The data pertaining to sequence errors occurring in the PLC controller during cascade processing can be queried via the manual diagnostic range (D278 through D438). DW D0 D2 Range D4 of D6 Automatic D8 Diagnostics D10 D12 (First-value D14 message) D16 D18 : D142 D144 D146 D148 D150 : D276 Range D278 of D280 Manual D282 Diagnostics D284 : D410 Station D420 list : D434 D436 D438 Contents, HIGH byte Control flags Day Year Minute Weekday (0 = Sunday) Cascade number Station ID Cascade status 1. Opcode 2. Opcode : 64. Opcode Reserved Reserved Reserved Cascade 1 information : Cascade 64 information Cascade number Stationskennung Cascade status Opcode 1 : Opcode 64 Last cascade, station 1 : Last cascade, station 8 Reserved Reserved Contents, LOW byte Month Hour Second unused Step number Module number Number of messages Step number Module number Number of messages First cascade, station 1 : First cascade, station 8 )LJ'DWD0RGXOH'LDJQRVWLF,QIRUPDWLRQ F 1070 072 168-101 (98.04) GB The data modules up to and including D438 (440 bytes) must be opened. 4-70 MMI-MADAP PLC Software Automatic diagnostic range • &RQWUROIODJV Data word D0 contains the control flags that are managed by MMIMADAP, with individual data bits serving different functions. ' In the event that a first-value error was entered, diagnostic module DIAGMMI sets data bit D0.0 is set HIGH. As soon as the operator terminal signals "Error Stored", the MMIMADAP again sets this bit LOW. This data bit is functionally interdependent with data bit D0.1. ' Data bit D0.1 controls the response to an active first-value error. • ' /2: The first-value error is always entered. If an unacknowledged first-value error is already present in the data module, this will be overwritten by the new first-value error. • ' +,*+ 00,0$'$3GHIDXOWVHWWLQJ A new first-value error can be entered only if the acknowledgement of a preceding first-value error was effected by means of data bit D0.0. If this is not the case, the new first-value error will be discarded. ' If a first-value error is active, data bit D1.0 is set HIGH by the DIAGMMI diagnostic module. If this is not the case, the bit will be reset automatically. 1070 072 168-101 (98.04) GB MMI-MADAP PLC Software 4-71 Diagnostic data In the case of an error the DIAGMMI module automatically enters diagnostic data in the following data words. These are then read by MMI-MADAP and, subsequent to processing for the display, entered in the diagnostics module in the operator terminal. Date format The time and date of an active first-value error are written to data words D2 through D8 in hexadecimal format. Weekdays are coded as follows: • • • • • • • 0hex = Sunday 1hex = Monday 2hex = Tuesday 3hex = Wednesday 4hex = Thursday 5hex = Friday 6hex = Saturday Step number This data byte (D10) stores the step number of the faulty cascade. Cascade number This data byte (D11) stores the cascade number of the faulty cascade. Module number Each cascade is programmed in an associated program module. The number of the program module is stored in data byte D12. It corresponds to both the cascade and to the cascade data module number. Station ID Data byte D13 contains the station ID of the faulty cascade. Number of messages Data byte D14 contrains the number of conditions attached to the active first-value error. The representation uses hexadecimal format. Only the first 64 conditions are stored in the data module. In the event that the BEFA command output or WSB step-on condition branch consists of more than 64 conditions, the number of messages will be set to 65. If the value FFH is returned with this word, this indicates that an illegal instruction was detected in the instruction block that was subject to the diagnostic check. 1070 072 168-101 (98.04) GB 4-72 MMI-MADAP PLC Software Cascade status Data byte D15 indicates the active operating mode of the faulty cascade at the time the first-value error occurred. • • • Bit 0 (value 1hex) = cascade in Manual mode Bit 1 (value 2hex) = cascade in Inching mode Bit 2 (value 4hex) = cascade in Automatikbetrieb Opcode Starting with data word D16, the opcode of the criteria of the faulty branch is stored. Each line of instructions is represented by a data word. The significance of a data word is pointed out below. Command code / link status Bit 15 Z z z z z z z z 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 Opcode Operand + Byte addr. Bit 0-7 Instruction 0 0 0 A 0 0 1 AN 0 1 0 O 0 1 1 ON 1 0 0 S 1 0 1 R 1 1 0 = 1 1 1 0 0 0 ( 1 1 1 0 0 1 O( z 1 1 1 0 1 0 ) z 1 1 1 0 1 1 )N 1 1 1 1 X X Reserved Operand or link status/condition: 1: satisfied; 0: not satisfied )LJ2SFRGH'HILQLWRQIRU2SHUDWRU 1070 072 168-101 (98.04) GB MMI-MADAP PLC Software Operand ID and byte address ranges Bit 15 14 13 12 11 10 9 8 7 6 5 4 Z Instruct. Operand + Byte addr. from 0 0 0 0 0 0 0 0 to 1 1 1 from 0 0 0 0 1 0 0 0 to 1 1 1 from 0 0 0 1 0 0 0 0 to 1 1 1 1 from 0 0 1 0 0 0 0 0 to 0 0 1 1 1 1 1 1 from 0 1 0 0 0 0 0 0 to 1 1 1 1 1 from 0 1 1 0 0 0 0 0 to 1 1 1 1 1 from 1 0 0 0 0 0 0 0 to 1 1 1 1 1 1 1 3 2 1 0 Bit 0-7 0 1 0 1 0 1 0 1 0 1 0 1 0 1 Convention applies also to C and T Example: C 127 is represented as C 15.7 Hex. Mask 0000 0078 0080 00F8 0100 01F8 0200 03F8 0400 05F8 0600 07F8 0800 0FF8 4-73 Operand C: Counter status 128 bytes T: Timer status 128 bytes SM:Special marker Bytes 0-31 I: Inputs Bytes 64-127 Bytes 0-63 O: Outputs Bytes 0-63 M: Markers Bytes 0-255 Subsequent to masking of bits 0-2 and 12-15 )LJ2SFRGH'HILQLWLRQ2SHUDQG,'DQG%\WH$GGUHVV Cascade information structure The first-value error range in the diagnostic module is followed, beginning at D150, by a block containing information about the available cascades. The table below shows the cascade information structure. Bit 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 Z Opmode Step no. 0 0 1 = Manual mode 0 1 0 = Inching mode 1 0 0 = Automatic mode 0 = No first-value errors 1 = Casc. returns first-value error 0 X 1 = Halt 0 1 X = Start 1 0 0 = Reset Cascade status: 0 = fault-free 1 = faulty )LJ&DVFDGH,QIRUPDWLRQLQ'LDJQRVWLF'DWD0RGXOH 1070 072 168-101 (98.04) GB 4-74 MMI-MADAP PLC Software Manual diagnostic range With regard to functional contents, the manual diagnostic range corresponds to that of the automatic diagnostics. However, the date and time of a given entry are not recorded. It starts with the step number in D278. The opcode range starts with data word D284. In the case of the manual diagnostics, a control flag is omitted. If diagnostic messages are active, the value in D282 is higher than zero by the message count. Diagnostic changes can be interpreted only by means of the data word D278 (cascade, step number) and word D282 (number of messages). If the value FFH is returned with data word D282, this indicates that an illegal instruction was detected in the instruction block that was subject to the diagnostic check. 1070 072 168-101 (98.04) GB MMI-MADAP PLC Software 4.11.4 4-75 Processing faults Messages from the DIAGMMI module are entered in data word D22 of the operator terminal data modules. The referred messages comprise error messages that cannot be entered in data word D0 of the cascade data module. The status word has the following significance: Bit 15 14 13 Cause of error Group fault indication not relevant The default first cascade in P4 was defined with a higher number than the last cascade. 12 Data module for cascade not found OR too short. 11 No free storage capacity in data field 10 Step number is too high. 9 Cascade number not permitted with Manual diagnostics. 8 Number of cascades not permitted. Error remedy At least one of the following errors, except bit 0, is active. → Correct parameter settings in DIAGMMI module. The DIAGMMI is attempting to diagnose a cascade but either cannot find the associated data module, or detects that it is incomplete. → Link the data modules of correct length with your program. BOSCH standard modules occupy data field blocks. A total of 12 data field blocks are available to the controller. → Reduce the total number of calls for BOSCH modules. The step number to be diagnosed exceeds 128. A step number in excess of 128 may have been accidentally selected in Manual mode. Parameter P2 of DIAGMMI module is not within permitted range (between 1 and 64). → Change parameter defaults. Parameter P3 of DIAGMMI module has a value in excess of 64. You can only process a maximum of 64 cascades, however. → Change parameter defaults. 1070 072 168-101 (98.04) GB 4-76 MMI-MADAP PLC Software Bit Cause of error 7 Error in system range (System command) 6 Structural fault in cascade jump distributor Error remedy This bit indicates that too many system commands (e.g. LAD and TAD) are being used in the overall PLC system. → Reduce the number of system commands OR arrange the commands in a coordinated sequence. Refer also to the manual CL500 System commands,1070 072 068. The DIAGMMI module has detected a structural fault in the cascade jump distributor. This may be caused by a mismatch between the step sequence in the jump distributor and that in the step program. → In the step module, change the step sequence either in the jump distributor or in the process sequence. 5 not relevant 4 Too many conditions in bramnch to be diagnosed. 3 Illegal instruction in branch to be diagnosed. The maximum number of 64 conditions per BEFA command output or WSB step-on assignment was exceeded. → Separate the branch into several secondary branches. In the BEFA or WSB branch you have used instructions that cannot be diagnosed. You can program these instructions either before or after the respective step branches. → Modify your cascade. 2 not relevant 1 not relevant 0 Warnng: Number of cascades = 0, without group fault indication Parameter P3 of DIAGMMI has the value 0. → Change this value in accordance with your application. )LJ6WDWXV0HVVDJH',$*00,3URJUDP0RGXOH 1070 072 168-101 (98.04) GB MMI-MADAP PLC Software 4-77 4.12 MMI-MADAP Multidiagnostic Concept The functional enhancement of the previous MMI-MADAP diagnostic concept now features the diagnostic procedure in conjunction with logging function and statistics for several stations (operating modes) on a single operator terminal. Prerequisites: • • PROFIBUS COM-P module, part no. 107078590 MMI-MADAP software version 1.3 and higher 4.12.1 Previous Diagnostic Concept Each of the operator terminals BT 1 through 4 manages a cascade range (Station 1 - 4) which, upon calling the MMIMADAP program module from the panel, is written to parameters P1 and P2. Functional description, usung BT1 as an example: The MMIMADA program module prepares the parameters required for calling the DIAGMMI program module, activating thar module with the fixed assignment of BT1 ÇÈ Station 1. For the purpose of display and logging/recording, the operator terminal writes the obtained diagnostic data into the communication data module DM 234. This data is then pikked up by the BT, acknowledged, displayed, and written into the protocol record. Only then can a new first-value error be entered. The operator terminals are subject to the following assignments: BT1 ÇÈ Station 1 communication DM = DM234 BT2 ÇÈ Station 2 communication DM = DM239 BT3 ÇÈ Station 3 communication DM = DM244 BT4 ÇÈ Station 4 communication DM = DM249 1070 072 168-101 (98.04) GB 4-78 MMI-MADAP PLC Software 4.12.2 Multiple Diagnostics The new multiple diagnostics provide a functional extension of the method previously used. This means that the stations labelled 1 through 4 (base stations) continue to point to the operator terminals (BT) 1 through 4. As a new feature however, 4 stations may be defined that may be freely assigned to the base stations. The resulting assignment of substations and of the associated cascade ranges occurs in DM255. As the assignments of cascades to the base stations remain unchanged, they continue to be expressed as parameters of the MMIMADAP program module. This ensures the expansion of the previous diagnostic concept without necessitating any other intervention in the PLC program. Definitions and assignments: For the purpose of diagnosing a ZS central processing unit, 4 additional substations can be assigned to existing base stations that are directly assigned to the 4 operator terminals. The referred 4 substations can be freely distributed to the operator terminals designated 1 through 4, whereby multiple assignments are not permitted. This means that a single operator terminal can operate a maximum of 1 base station plus 4 substations. Multiple diagnostics of stations located on different operator terminals (BT) is not possible. The above definitions provide for the following combinations: • 4 BT are able to diagnose a maximum of 8 stations • 1 BT is able to handle a maximum of 5 stations Definition of station assignments in DB255 Substation mask: Assignment indicating which stations and terminals (in addition to the base station) are handled by the diagnostics. Cascade range: Definition of the cascade range that is assigned to a station. The cascade range of the base station continues to be defined by the MMIMADAP parameters. 1070 072 168-101 (98.04) GB MMI-MADAP PLC Software 4-79 Definition of station assignments in DM255 In the table below, entries made by the operator terminal appear in boldface. No. Sign : : Symbol : Type : ; D156 D158 : D168 D170 EW_KZ1 EW_KZ2 : EW_KZ7 EW_KZ8 Word Word : Word Word ; N N : N N Word Word Word Word ; N N N N D172 D174 D176 D178 EW_St5 EW_St6 EW_St7 EW_St8 BT1StMsk BT2StMsk BT3StMsk BT4StMsk Word Word Word Word ; N N N N D188 MehrBel Word ; N Word Word Word Word ; Word ; Word ; Word Word Word Word : Word N N N N K_Ber5 K_Ber6 K_Ber7 K_Ber8 D198 BT_Teiln D200 D202 D204 D206 D208 : D 510 StatEdit K_Ber1 K_Ber2 K_Ber3 K_Ber4 : : First-value communication counter, station 1-8 Value 500 (approx. 10 sec) acknowledges first value : F : D D : D D First values to operator terminals (BT), station 5-8 Entry: 1:FV active, 2:BT has acknowledged D180 D182 D184 D186 D190 D192 D194 D196 Data field H H H H Station mask assignment / BT 1-4 No multiple bit assignment permitted. Bit0 > Stat5 (DM222) , Bit3 > Stat8 (DM225) 0000 0000 0000 0000 Multiple station assignment HIGH byte = 1:Multiple assignment recognized LOW byte : First multiple assignment to be found B B B B H Substation cascade ranges 5-8 HIGH byte: Last cascade, LOW byte: First cascade Overlaps are possible 0000 0000 0000 0000 BT Diagnostic participant (auxiliary marker) H H H H B Editing screen activated H Operator terminal stations 1-4, cascade ranges N N N N : : N H H H H : H )LJ([WHQGHG'LDJQRVWLF&RQFHSW(QWULHVLQ'0 Functional principle of PLC program: By means of the station masks the MMIMADAP program module determines if multistation mode was selected (D180/ 182/ 184/ 186 ≠ 0) and, in accordance with the information obtained, repeatedly executes the cascade diagnostics for the defined cascade ranges. If it is found that stations were assigned to several operator terminals, the diagnostics will be performed on the base station only. 1070 072 168-101 (98.04) GB 4-80 MMI-MADAP PLC Software Data module assignment and PROFIBUS object management Base stations with fixed assignments to operator terminals 1 - 4 ([LVW BT1 (Stn.1) REM DM234 ([LVW BT2 (Stn.2) REM DM239 ([LVW BT3 (Stn.3) REM DM244 ([LVW BT4 (Stn.4) REM DM249 First-value Diagnostics First-value Diagnostics First-value Diagnostics First-value Diagnostics 28 37 46 55 Cascade information Cascade information Cascade information Cascade information Manual Diagnostics Manual Diagnostics Manual Diagnostics Manual Diagnostics 29 38 Station information 47 Station information 56 Station information Station information Substations for free assignment to base stations (BT) 1 - 4 1HZ REM Stn.5 DM222 First-value Diagnostics 64 1HZ REM Stn.6 DM223 First-value Diagnostics 65 1HZ REM Stn.7 DM224 First-value Diagnostics 66 1HZ REM Stn.8 DM225 First-value Diagnostics 67 Cascade information Cascade information Cascade information Cascade information Manual Diagnostics Manual Diagnostics Manual Diagnostics Manual Diagnostics Station information Station information Station information Station information )LJ'DWD0RGXOH$VVLJQPHQWDQG352),%862EMHFW0DQDJHPHQW 1070 072 168-101 (98.04) GB Interfaces – PLC <-> Operator Terminals 5-1 5 Interfaces – PLC <-> Operator Terminals 5.1 Definition Introduction The entirety of data interfaces for the MMI-MADAP is defined in the form of data modules (DM). Within individual data modules, the defined data ranges differentiate separate user and MMI-MADAP ranges. The term user ranges denotes data interfaces on which the MMI-MADAP operator terminal makes data available to the user, and/or on which the user furnishes data destined for the MMI-MADAP operator terminal. The referred data interfaces handle all communications between user and MMI-MADAP operator terminal. All remaining data ranges are used by MMI-MADAP for exchanging information between the MMI-MADAP program modules and the MMI-MADAP operator terminal. With regard to data interfaces, a differentiation is made between screendependent and screen-independent data ranges. The screen-dependent data ranges are valid only in conjunction with the screen that is currently selected on the MMI-MADAP operator terminal. The screen-independent data ranges are permanently defined. They are thus independent of the screen that is currently selected on the MMIMADAP operator terminal. All data interfaces are managed by the MMI-MADAP operator terminal. The updating of data interfaces with regard to the PLC program is both synchronous and asynchronous. The updating of the user data ranges must be monitored by the user. F The user data interfaces must be read and/or written in a cyclical fashion For the maximum of 4 MMI-MADAP operator terminals, local as well as global data modules are available. The local data modules are designated for the respective corresponding MMI-MADAP operator terminal. The global data modules contain operator terminal data for general use. 1070 072 168-101 (98.04) GB 5-2 Interfaces – PLC <-> Operator Terminals 5.2 List of Data Interfaces DM no. DM 1 Name DB_K01 DM 64 DB_K64 Function Kette 1 cascade information : Kette 64 cascade information DM DM DM DM DM DM DM DM DM DM DM DM DM DM DM DM DM DM DM DM DM DM DM DM DM DM DM DM DM DM DM DM DM DM DM DM DM DM DM Taktzeit Auslast1 Auslast2 DP_Daten DP_Komm Diag_St5 Diag_St6 Diag_St7 Diag_St8 Cycle time recording Machine usage data 1 Machine usage data 2 DESI-DP data DESI-DP communication channel 1 Station 5 diagnostic data (optional) Station 6 diagnostic data (optional) Station 7 diagnostic data (optional) Station 8 diagnostic data (optional) R R R R R R R R R 230 512 512 512 320 512 512 512 512 BF1_DB BF1_Stat BF1_Sper BF1_Anw BF1_Diag BF2_DB BF2_Stat BF2_Sper BF2_Anw BF2_Diag BF3_DB BF3_Stat BF3_Sper BF3_Anw BF3_Diag BF4_DB BF4_Stat BF4_Sper BF4_Anw BF4_Diag BF1_4Anw ResKObj1 ResKObj2 EA_SK AL_DP_D BF_Globa Communication / display data OPD status Movement lock functions Communication DM, 1 Object of 220 bytes Diagnostic result for BT1 = Station 1 Communication / display data Operand status Movement lock functions Communication DM, 1 Object of 220 bytes Diagnostic result for BT2 = Station 2 Communication / display data Operand status Movement lock functions Communication DM, 1 Object of 220 bytes Diagnostic result for BT3 = Station 3 Communication / display data Operand status Movement lock functions Communication DM, 1 Object of 220 bytes Diagnostic result for BT4 = Station 4 DM250 for all BT, 2 objects of 220 bytes ea. Reserved for future communication objects Reserved for future communication objects I/O assignment and SC table Display of machine usage & DP diagnostics DM, valid for all BTs R R R R R R R R R R R R R R R R R R R R R R R R R R 512 512 512 512 512 512 512 512 512 512 512 512 512 512 512 512 512 512 512 512 512 : 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 241 244 245 246 247 246 249 250 251 252 253 254 255 : R/E R R Length 100 : 100 : 512 512 512 )LJ00,0$'$3'DWD0RGXOHV 1070 072 168-101 (98.04) GB Interfaces – PLC <-> Operator Terminals 5-3 5.3 Description of User Data Interfaces 5.3.1 Data Modules DM1-64 – Cascade Data 1-64 Data modules DM1 through DM64 are required for sequential control management, and provide all data essential to system control. An accompanying data module must be generated for each step module. Data module contents DM1 through DM64, "DB_K01" through "DB_K64": cascade information for KETTE1 through KETTE64 Symbol Explanation Data format Entry caused by: K: KETTE M: MMI-MADAP A: User D00 D02 D04 D06 D08 D10 D12 D14 D16 D18 D20 D22 D24 nnFehler nnKettNr nnSchAnz nnBaWahl nnBaMldg nnSchr-1 nnSchr. nnSchr.S nnBEFA nn-KWA nn-KUE nnINT0 nnINT1 binary decimal decimal binary binary decimal decimal decimal decimal dec. x 100 ms dec. x 100 ms K K K K K K K M K K/A K/A binary M D26 D28 D30 D32 :: D48 :: D62 D64 :: D78 D80 :: D94 nnINT2 nnINT3 nnBa_Ext nnINT4 :: nnSyn16 :: nnSyn128 nnSch16 :: nnSch128 nnBef16 :: nnBef128 Error bits Cascade no., n (1-64) Number of steps in cascade Operating mode selection Confirmed operating mode Step number, preceding step Step number, current step Step number, Set Step Command output for all steps Wait time, actual value Monitoring time, actual value internal use internal use Bit 2 MADAP aktive bit intern verwendet intern verwendet Operating mode selection for external operator terminals internal use internal use Synchronization steps 1 thru 16 :: Synchronization steps 113 thru 128 Steps 1 thru 16 :: Steps 113 thru 128 Command output, steps 1 thru 16 :: Command output, steps 113 thru 128 binary M binary K K K K K K K K K binary binary binary binary binary )LJ'DWD0RGXOH&RQWHQWV&DVFDGH'DWD 1070 072 168-101 (98.04) GB 5-4 Interfaces – PLC <-> Operator Terminals 5.3.2 Data Module DM217 – Machine Cycle Times Data module contents, DM217, "Taktzeit" (Cycle Time): machine cycle time recording No. D D D D D D 0 2 : 92 94 96 98 D 100 Symbol Type TZ01 TZ02 ; Word Word : TZ47 TZ48 TZint3 TZint4 TZ_ANZ D 102 D 104 D 106 STA16-01 STA32-17 STA48-33 D 108 D 110 D 112 STP16-01 STP32-17 STP48-33 D 114 D 116 D 118 BAS16-01 BAS32-17 BAS48-33 D 120 D 122 : D 212 D 214 D 216 D 218 D 220 D 222 D 224 D 226 D 228 AE-TZ01 AE-TZ02 N N : F : H H : H H H H : N N N N Number of cycle times to be processed N D Start bits for cycle times N N N B B B Stop bits for cycle times N N N B B B Time base bits for cycle times Recording accuracy: 0 = 0.1 sec; 1 = 1.0 sec N N N B B B Current measured cycle time values N N : Word Word Word Word Word Word Word Word Word Data field Display values for cycle times (TZ) 1-48 Word Word Word Word ; Word ; Word Word Word ; Word Word Word ; ; Word Word Word ; Word Word : AE-TZ47 AE-TZ48 HW_0.1s HW_1s KorrWert TZint5 6LJQ : : N N N N N N N N N H H : H H H H H H H H H )LJ'DWD0RGXOH&RQWHQWV0DFKLQH&\FOH7LPHV 1070 072 168-101 (98.04) GB Interfaces – PLC <-> Operator Terminals 5-5 5.3.3 Data Modules DM 218 & DB219 – Machine Usage Data module contents, DM218 "Auslast1": Machine usage data 1 No. Symbol D 0 D D D D 26 28 30 32 D D D D 58 60 62 64 D D D D 90 92 94 96 D D D D 122 124 126 128 D D D D 154 156 158 160 D D D D 186 188 190 192 D D D D 218 220 222 224 D D D D 250 252 254 256 %S1PrT1 : %S1PrT14 S1Prsec S1Prmin %S2PrT1 : %S2PrT14 S2Prsec S2Prmin %S3PrT1 : %S3PrT14 S3Prsec S3Prmin S1StT1 : S1StT14 S1Mult S1Mzykl S2StT1 : S2StT14 S2Mult S2Mzykl S3StT1 : S3StT14 S3Mult S3Mzykl PrT1 : PrT14 Prsec Prmin JahrT1 : JahrT14 : : : : : : : : MET1 : D D D D 282 284 286 288 D D D D 314 316 318 320 MET14 MEsec MEmin KTT1 : : : N N N N : Word Word Word Word : N N N N : Word Word Word Word : N N N N : Word Word Word Word : N N N N : Word Word Word Word : N N N N : Word Word Word Word : N N N N : : N N N N : : 1070 072 168-101 (98.04) GB : : Word Word Word Word : : N N N F Day 1 (current) Day 14 Seconds Minutes Production, % value, Shift 2 record, Day 1 (current) : Day 14 Current recording time Seconds Minutes Production, % value, Shift 3 record, Day 1 (current) : Day 14 Current recording time Seconds Minutes Piece count actual, Shift 1 record, Day 1 (current) : Day 14 Multiplier (Machine cycles x Multipl. = Pcs. Day 1) Machine cycles Piece count actual, Shift 2 record, Day 1 (current) : Day 14 Multiplier (Machine cycles x Multipl. = Pcs. Day 1) Machine cycles Piece count actual, Shift 3 record, Day 1 (current) : Day 14 Multiplier (Machine cycles x Multipl. = Pcs. Day 1) Machine cycles Production, % value, Daily record, Day 1 (current) : Day 14 Current recording time Seconds Minutes Date recording, Year Day 1 (current) : Day 14 Machine On, % value, Daily record, : Day 1 (current) Day 14 Seconds Minutes No Parts, % value, Daily record, Day 1 (current) : Day 14 Current recording time Seconds Minutes Buffer Full, % value, Daily record, Day 1 (current) : Day 14 Current recording time Seconds Minutes Current recording time N N N N : Word Word Word Production, % value, Shift 1 record, : Current recording time N N N N Word Word Word Word PVT14 PVsec PVmin : : Word Word Word Word : Data field N N N N Word Word Word Word KTT14 KTsec KTmin PVT1 6LJQ N Word Word Word Word : : D 346 D 348 D 350 Type Word D : D D D D : D D D D : D D D D : D D D D : D D D D : D D D D : D D D D : D D D D : D D D D : D D D D : D D D 5-6 Interfaces – PLC <-> Operator Terminals No. Symbol Type D 352 : D 378 D 380 D 382 D 384 : D 410 D 412 D 414 D 416 : D 442 D 444 D 446 D 448 : D 474 D 476 D 478 : D 510 StgT1 Word : StgT14 Stgsec Stgmin SST1 6LJQ N : Word Word Word Word : SST14 SSsec SSmin DTT1 : Word Word Word Word : DTT14 : DMT14 : N N N N : Word Word Word : END124 : : Day 14 Seconds Minutes Stillstand %-Wert Tageserfassung, Day 1 (current) : Day 14 Current recording time Seconds Minutes Date recording - Day, Day 1 (current) : Day 14 Date recording - Month, : N N N : Word F Day 1 (current) Current recording time N N N N Word Word Word Word DMT1 : N N N N Data field Fault, % value, Daily record, : : Day 1 (current) : Day 14 : N D : D D D D : D D D H : H H H D : D D H : H )LJ'DWD0RGXOH&RQWHQWV0DFKLQH8VDJH Data module contents, DM219 "Auslast2": Machine usage data 2 No. D D D D 0 2 4 6 D D D D D D 24 26 28 30 32 34 D D D D D D 52 54 56 58 60 62 D D D D D D 80 82 84 86 88 90 Symbol : : : : D 108 D 110 S1VONH S1VONM S1P1VONH S1P1VONM : S1P6VONH S1P6VONM S1BISH S1BISM S1P1BISH S1P1BISM : S1P6BISH S1P6BISM S2VONH S2VONM S2P1VONH S2P1VONM : S2P6VONH S2P6VONM S2BISH S2BISM S2P1BISH S2P1BISM : S2P6BISH S2P6BISM Type Word Word Word Word 6LJQ : Word Word Word Word Word Word Start of work shift, Shift 1 (from) : (from) Start of break 6, Shift 1 : (from) End of work shift, Shift 1 (to) End of break 1, Shift 1 (to) End of break 6, Shift 1 : (to) : N N N N N N : Word Word Word Word Word Word Start of break 1, Shift 1 : N N N N N N Word Word Word Word Word Word Start of work shift, Shift 2 (from) Start of break 1, Shift 2 (from) Start of break 6, Shift 2 : from) : N N N N N N : Word Word Data field N N N N End of work shift, Shift 2 (to) End of break 1, Shift 2 (to) End of break 6, Shift 2 : (to) : N N F Hour Minute Hour Minute Hour Minute Hour Minute Hour Minute Hour Minute Hour Minute Hour Minute Hour Minute Hour Minute Hour Minute Hour Minute D D D D : D D D D D D : D D D D D D : D D D D D D : D D 1070 072 168-101 (98.04) GB Interfaces – PLC <-> Operator Terminals No. D D D D Symbol 112 114 116 118 : D 136 D 138 D D D D 140 142 144 146 D D D D D D 164 166 168 170 172 174 : Word Word Word Word Word Word S3BISH S3BISM S3P1BISH S3P1BISM : S3P6BISH S3P6BISM SOLL_S1 SOLL_S2 SOLL_S3 ERF_PARA Word Word Word Word : D 194 D 196 D 198 Type S3VONH S3VONM S3P1VONH S3P1VONM : S3P6VONH S3P6VONM : Start of work shift, Shift 3 (from) Start of break 1, Shift 3 (from) N N Start of break 6, Shift 3 : (from) N N N N End of work shift, Shift 3 (to) End of break 1, Shift 3 (to) End of break 6, Shift 3 : (to) : : Word Word Word Word Word Word : N N N N N N : Word Word Word : : N N N : : D 218 D 220 S1P6 100%S1 Word Word N N D 222 D 224 D 226 S2 S2INFO S2P1 Word Word Word N N N : : : S2P6 100%S2 Word Word N N D 250 D 252 D 254 S3 S3INFO S3P1 Word Word Word N N N : : S3P6 100%S3 : D 384 : S1St1S : D D D D 410 412 414 416 442 444 446 448 : D 510 : S3St1S D 474 D 476 D 478 : : S3StT14S : SCHTEND Word Word Word Word : Word Word Word : N N N : Word : Length in minutes Information (bit 0 = Shift active) Break 1, length in minutes : Break 6, length in minutes 100 % = Shift length - Σ breaks D B D : D D : Day 1 (current) : Day 14 Shift 2 setpoint data, Day 1 (current) : Day 14 Shift 3 setpoint data, Day 1 (current) : Day 14 : N )LJ'DWD0RGXOH&RQWHQWV0DFKLQH8VDJH 1070 072 168-101 (98.04) GB : D B D : D D Shift 3: : N N N N Hour Minute D D D D : D D D D D B D B D : D D : : Hour Minute Hour Minute Length in minutes Information (bit 0 = Shift active) Break 1, length in minutes : Break 6, length in minutes 100 % = Shift length - Σ breaks Shift 1 setpoint data, N N N N Hour Minute D D D D : D D Shift 2: : N Word Word Word Word S2St14S : : : S2St1S : N N Word S1St14S : D D D D : Word Word F Hour Minute Hour Minute Nominal/setpoint value, Shift 1 Nominal/setpoint value, Shift 2 Nominal/setpoint value, Shift 3 Active logging parameters: HIGH byte = Default, LOW byte = transformed by logic : Shift 1: Length in minutes Information (bit 0 = Shift active) Break 1, length in minutes : Break 6, length in minutes 100 % = Shift length - Σ breaks : D 246 D 248 D 274 D 276 Data field N N N N : : S1 S1INFO S1P1 6LJQ 5-7 : D : D D D D : D D D D : D H H : H 5-8 Interfaces – PLC <-> Operator Terminals 5.3.4 Data Modules DM220 & DM221 – DESI-DP Diagnostics Data module contents, DM220 "DP_Daten": DESI-DP data 6LJQ No. Symbol Type D D D D D D D D D D D D D D 0 2 4 6 8 10 12 14 16 18 20 22 24 26 KoppAdr AnlaufV 1DB-KK 2DB-KK 3DB-KK 4DB-KK 5DB-KK 6DB-KK 7DB-KK 8DB-KK PrioDB KSD-DB Off-KSD F/Stat D D D D 28 30 32 34 SendOff SendLng RecOff RecLng D 36 DPint : D 510 ; Word ; Word ; Word Word Word Word Word Word Word Word ; ; Word ; ; ; Word ; Word ; Word ; Word Word Word Word ; Word : N F D Control of start-up behaviour & data communications N H DM numbers for communication channels N N N N N N N N D D D D D D D D High-priority communication channel (DM no. from 1DM comm chan. - 8DM comm chan.) N D Communication channel for Auto-execution of classified slave diagnostics (KSD) (DM no. from 1DM comm chan. - 8DM comm chan.) N D DM offset for KSD_DB (classified slave diagnostics) N D Error and status messages N B FIFO parameters N N N N H H H H Up to end of module: internal processing data only N : Word Data field Switching matrix address (BM-DP12 DIP switch) : N : H : H )LJ'DWD0RGXOH&RQWHQWV'(6,B'3'DWD 1070 072 168-101 (98.04) GB Interfaces – PLC <-> Operator Terminals Data module contents, DM221 "DP_Komm": DESI-DP communication channel 1 6LJQ No. Symbol Type Data field D D D D D D D D 0 2 4 6 8 10 12 14 B_St G_St Z/m_s Z/T_h Z/M_W KF_WT E_St S_E_DatL D D D 16 18 20 SDat1 Sdat2 SDat3 D 22 Edat : D 318 D 320 D 322 ; Word ; Word ; Word ; Word ; Word ; Word ; Word ; Word ; Word Word Word ; Word : DIP_Adr ZS_Offs N B Global status N B Minute / Second N H Day / Hour N H Year / Month N H Switching matrix address / Weekday N H Receive status N H Transmit and Receive data length N H Transmit data and commands N N N H H H Receive data up to D318 N : : N H : H Switching matrix address converted to DIP switch N H ZSx I/O address offeset N )LJ'DWD0RGXOH&RQWHQWV'(6,'3&RPPXQLFDWLRQ&KDQQHO 1070 072 168-101 (98.04) GB F Processing status : Word ; Word ; Word 5-9 H 5-10 Interfaces – PLC <-> Operator Terminals 5.3.5 Data Modules – BT 1-4 Communication & Display Data • MMI-MADAP operator terminal 1, DM230 • MMI-MADAP operator terminal 2, DM235 • MMI-MADAP operator terminal 3, DM240 • MMI-MADAP operator terminal 4, DM245 Data ranges: • Screen number, MMI-MADAP operator terminal • Terminal identifier of MMI-MADAP operator terminal • Lamp test user prompt • Cursor position, cascade selected for manual diagnostics • Synchronization mask bits • Command code for cascade/step • Movement keys Screen number, MMI-MADAP operator terminal D0 Word Number of screen on display The number of the screen that is currently displayed on the MMI-MADAP operator terminal is entered in data word D0. Using the screen number, the user is able to determine which data is currently present on the screen-dependent data interfaces, and/or when data may be written to specific screen-dependent data ranges. 1070 072 168-101 (98.04) GB Interfaces – PLC <-> Operator Terminals 5-11 MMI-MADAP operator terminal ID D14 ASCII User-defined terminal ID max. 6 characters through D18 ASCII The designation for the MMI-MADAP operator terminal is entered in ASCII format in data word D14 through D18. In the event that the operator terminal ID is entered by the user, it will be automatically added to the display upon opening the base screen (main menu) on the MMI-MADAP operator terminal. It will subsequently be displayed on each screen. Lamp test user prompt D116 Word Lamp test prompt If a lamp test user prompt is displayed on the MMI-MADAP operator terminal, a 1bin will be entered in data word D116. The user can read this data word and initiate a lamp test. Cursor position, cascade selected for manual diagnostics D118 Word Cursor position for manual diagnostics indicated in diagnostic screen. The cursor position of the cascade selected in the Manual diagnostics screen on the MMI-MADAP operator terminal is entered in data word D118 (value range if selected 1-64dec, otherwise 0). Synchronizing mask bits D120.0 through Bit Synchronization mask bits for Automatic D120.0 (cascade 1) thru 127.7 (cascade 64) D127-.7 Bit Bit = LOW Participation in synchronization Bit = HIGH No participation in synchronization The synchronization mask bits in data words D120 through D126 are read and interpreted by the MMI-MADAP operator terminal. In the event that specific cascades are not to participate in synchronization, they can be masked by the user. 1070 072 168-101 (98.04) GB 5-12 Interfaces – PLC <-> Operator Terminals Operator terminal Live message D154 Word Life cycle counter Starting at 0, this data word counts cyclically upwards. Each time the operator terminal registers in D30 (BF life marker), the counter is flushed. If the counter reaches the value of 2001, this means that the BF has not signalled to D30 for the past 10 seconds, and the counter will stop. You can interpret this value and specify suitable responses to its occurrence. Command code, cascade/step D256 Word HIGH Byte = cascade number through D286 Cascade and step number of current movement screen Word LOW Byte = step number Dependent upon the selected movement screen, the current command code for all of the 16 movement functions is stored by the MMI-MADAP operator terminal in data words D256 through D286. • D256 thru D270: cascade & step no., left half of screen • D272 thru D286: cascade & step no., right half of screen Dependent upon movement screen and movement key, this command code could be manipulated by the user for the purpose of special functions. The number of the movement screen can be interpreted in data word D0. F The data range is valid for all movement screens. Movement keys D292.0 Bit Statuses of the 16 movement keys in the movement screen through LOW Byte = Left half of screen D293.7 HIGH Byte = Right half of screen The movement keys selected in the movement screen of the MMI-MADAP operator terminal are entered in data word D292. Dependent upon the respective movement screen, the movement keys can be interpreted for special functions. The number of the movement screen can be taken from data word D0. F The data range is valid for all movement screens. 1070 072 168-101 (98.04) GB Interfaces – PLC <-> Operator Terminals 5-13 Data module contents, DM230 "BF1_DB": Communication/display data (example of operator terminal 1) 6LJQ No. Symbol Type Data field D 0 D 2 D 4 D 6 D 8 D 10 D 12 1Bild-Nr 1DF-Seg 1DB-Nr 1DB-Laen 1EA_ZS 1Erst_DB 1dirBild D 14 1Anw-K D 20 1KettAnz D 22 1Diag D D 24 26 1DIAG1 1DIAG2 D 28 1SPS-Typ D D 30 32 1BFlebt 1Start_K D 34 1Sec_Lev ; Word ; ; ; Word ; Word ; Word ; ; Word ; Word ; Word ; ASCII ; Word ; Word ; Word Word ; Word ; Word Word F Number of displayed screen N D K-Segm. + upper/lower half f. status DF HBy = upper (1)/ lower (0) DF segment half LBy = K-segment N H Number of DM being processed N D Length of selected DM N D Number of I/O and EI/EO bytes, "local" ZS HIGH byte=EI/EO, LOW byte=I/O N H Number of first linked DM N D Reserved N D User ID Operator terminal 1 Number of cascades (number of last cascade) N N D Return message (error code) from DIAG PM N B Parameters for the DIAG PM, managed internally N N H H PLC Type code code + ZS no with CL5xx (x=1-3) CL350=0350, CL400=0400, CL500=050x, CL51x=150x, CL501=450x Life marker, operator terminal N N N H H H Security Level D 36 D 38 : D 46 D 48 D 50 1BF_Nr 1ASynBer : 1E-Bed1 1E-Bed2 D 52 D 114 1E-Cod1 1E-Cod32 D 116 1LT D 118 D D D D 120 122 124 126 1K-Curs 1A_SynM1 1A_SynM2 1A_SynM3 1A_SynM4 Word ; Word ; Word : Word ; Word ; Word ; Word Word ; Word ; Word ; Word Word Word Word 1070 072 168-101 (98.04) GB N H Operator terminal number N Auto-synch synchronization range N : : N H : H : H Statuses, power-up conditions 1 through 16 N B Statuses, power-up conditions 17 through 32 N B Codes for 32 Power-up conditions indirect bit address N N H H Lamp test Station 1 N H Cursor position, manual diagnostics in Diag. screen N D Synchronization mask bits for Auto N N N N B B B B 5-14 No. D 128 Interfaces – PLC <-> Operator Terminals Symbol 1SynAnf D D D D 130 132 134 136 1BA_Syn1 1BA_Syn2 1BA_Syn3 1BA_Syn4 D D D D 138 140 142 144 1E_Syn1 1E_Syn2 1E_Syn3 1E_Syn4 D D D D 146 148 150 152 1HiB_Syn 1int1 1int2 1int3 D 154 D 156 : D 190 1BFlebtZ 1SynAnst : 1BewB0 D 192 : D 222 1E-End1 : 1E-End16 D 224 : D 254 1E-Akt1 : 1E-Akt16 D 256 : D 286 1E-Bew1 : 1E-Bew16 D 288 D 290 D 292 D 294 D 296 1Endl 1Akt 1Syn 1BewT 1neuBild Type ; ; Word ; Word Word Word Word ; Word Word Word Word ; Word Word Word Word ; Word Word 6LJQ H Operating mode bits for synchronization N N N N B B B B Synchronization results N N N N B B B B Synch auxiliary bits B0=Synch poss.; B1=Auto synch N N N N H H H H BF Life cycle counter N N : : : N 1BewSper : Word ; Word : : N D 300 1FT D D D D D 1DB-Komm 1DB-Stat 1DB-DIAG 1KNr 1KAnz 302 304 306 308 310 H : H 16 Action codes (ind. bit addr.) in Movement screen N : Word ; Word : : N H : H 16 Command codes cascade/step in Movement scrn N : Word ; Word ; Word Word Word Word Word H H : H 16 End pos. codes (ind. bit addr.) in Movement scrn N : : N H : H End position statuses in movement screen HIGH byte = right, LOW byte = left; 1=bit0 N B Action statuses in movement screen HIGH byte = right, LOW byte = left; 1=bit0 N B Synchronization result statuses in movement screen HIGH byte = right, LOW byte = left; 1=bit0 N B Movement key statuses in movement screen HIGH byte = right, LOW byte = left; 1=bit0 N B New movement screen opened (handshake) N Movement lock for active screen D 298 F N Word ; Word Word ; ; Word ; ; Word ; ; Word ; ; Word ; Word Data field Synchronization request from operator terminal Bit0: request, Bit8: was requested N D H H Map of function keys N B N N N N N D D D H H 1070 072 168-101 (98.04) GB Interfaces – PLC <-> Operator Terminals No. D D D D 312 314 316 318 D 320 D 322 D 324 D 326 D 328 D 330 D 332 D 334 D 336 : D 348 D 350 : : : D 462 D 464 : D 476 D 478 D 480 : D 492 D 494 D 496 : D 510 Symbol SynExt 1SynZaeh 1H-lKett 1H-lBew 1OPDKz1 1DBNr1 1DBL1 1ByAdr1 1StFrg1 1AWert1 1SWert1 1OPDKz2 : 1SWert2 : : : 1OPDKz10 : 1SWert10 1OPDKz11 : 1SWert11 1OPDKz12 : 1StFrg Type ; ; Word Word Word Word ; ; Word ; Word ; Word ; Word ; Word ; Word ; Word Word Word : Word Word : : : Word Word : Word Word Word : Word Word Word : Word 6LJQ Data field F Synchronization triggered externally (oper. terminal) w/ "1" in LOW byte; HIGH byte: internal transition bits N N N N H H H H Universal status display, with control line 1 (prepared) Operand identifier N H DM number N H DM length N H Byte address N H Control enable when 1 N H Display value N H Conbtrol value N N N : : : : : : : : : : : : : : N N N N N N N N N N N )LJ'DWD0RGXOH&RQWHQWV&RPPXQLFDWLRQ'LVSOD\'DWD 1070 072 168-101 (98.04) GB 5-15 H H H : H H : : : H H : H H H : H H H : H 5-16 Interfaces – PLC <-> Operator Terminals 5.3.6 Data Modules – BT 1-4 Status Display Data • MMI-MADAP operator terminal 1, DM231 • MMI-MADAP operator terminal 2, DM236 • MMI-MADAP operator terminal 3, DM241 • MMI-MADAP operator terminal 4, DM246 Data ranges: • Data contents of data types selected on MMI-MADAP operator terminal The data modules are used by the MMIMADAP program module to store the statuses and/or data contents of selected data ranges of the status display on the MMI-MADAP operator terminal. The data is read and displayed by the MMI-MADAP operator terminal. Dependent upon selection, the following data ranges are stored in their entirety: • Inputs / Extended input fields • Outputs / Extended output fields • Markers / Special markers • System data range • Times / Counters • Data field / Data buffer • Data modules Data module contents, DM231 "BF1_Stat": Operand status (example of operator terminal 1) 6LJQ No. Symbol Type Data field ; D D 0 2 : D 506 D 508 D 510 Stat_BF1 The statuses of operands selected in operator terminal 1 are deposited here for display purposes. Word Word : N N : Word Word Word F : : N N N H H : H H H )LJ'DWD0RGXOH&RQWHQWV2SHUDQG6WDWXV 1070 072 168-101 (98.04) GB Interfaces – PLC <-> Operator Terminals 5-17 5.3.7 Data Modules – BT 1-4 Movement Blocks • MMI-MADAP operator terminal 1, DM232 • MMI-MADAP operator terminal 2, DM237 • MMI-MADAP operator terminal 3, DM242 • MMI-MADAP operator terminal 4, DM247 Data ranges: • Movement block for a movement screen, with return of blocking code Dependent upon specific events, specific user-selected movement screens can be blocked within the data modules. • D0 = Unused • D1 - D64 = Movement screen 1 through 64 • D65 = Unused How to use the movement blocks: Each movement screen has a data byte permanently assigned to it. Dependent upon specific events, you can write to this data byte a userdesignated number code within the range of 1 to 96. If the movement screen is then opened, the screen will display the following default message: Actions Are Blocked! Code: nn This text may be freely modified by yourself. Permanent messages: Code 97: reserved Code 98: Current Movements Blocked! No active screen number. Upon changing a movement screen group by pressing a function key, this message will be returned until the new screen number is available in the PLC. Code 99: All Movements Blocked! This is a global movement block that is initiated by parameter P6 of the MMIMADAP program module. 1070 072 168-101 (98.04) GB 5-18 Interfaces – PLC <-> Operator Terminals Data module contents, DM232 "BF1_Sperr": Movement blocks, (example of operator terminal 1) 6LJQ No. Symbol Type Data field ; D D D D D 0 2 4 6 8 1Sp01/-1Sp03/02 1Sp05/04 1Sp07/06 1Sp--/08 D D D D D 10 12 14 16 18 1Sp11/-1Sp13/12 1Sp15/14 1Sp17/16 1Sp--/18 D D D D D 20 22 24 26 28 1Sp21/-1Sp23/22 1Sp25/24 1Sp27/26 1Sp--/28 D D D D D 30 32 34 36 38 1Sp31/-1Sp33/32 1Sp35/34 1Sp37/36 1Sp--/38 D D D D D 40 42 44 46 48 1Sp41/-1Sp43/42 1Sp45/44 1Sp47/46 1Sp--/48 D D D D D 50 52 54 56 58 1Sp51/-1Sp53/52 1Sp55/54 1Sp57/56 1Sp--/58 D D D D D 60 62 64 66 68 1Sp61/-1Sp63/62 1Sp65/64 1Sp67/66 1Sp--/68 D D D D D 70 72 74 76 78 1Sp71/-1Sp73/72 1Sp75/74 1Sp77/76 1Sp--/78 D 510 ; Word Word Word Word Word ; Word Word Word Word Word ; Word Word Word Word Word ; Word Word Word Word Word ; Word Word Word Word Word ; Word Word Word Word Word ; Word Word Word Word Word ; Word Word Word Word Word Word F Block of movements in the screens corresponding to the byte no. (0 = free). The following applies to individual movement screen groups: Byte x0 = free; byte x1-x8 = scrn 1-8; byte x9 = free. Example: Value 3 in byte 11 blocks all movements in movement screen group 2, scrn 1. The entered value represents a code that is displayed on the terminal. Bewegungsbildgruppe 1, Bild 1-8 N N N N N H H H H H Movement screen group 2, screens 1-8 N N N N N H H H H H Movement screen group 3, screens 1-8 N N N N N H H H H H Movement screen group 4, screens 1-8 N N N N N H H H H H Movement screen group 5, screens 1-8 N N N N N H H H H H Movement screen group 6, screens 1-8 N N N N N H H H H H Movement screen group 7, screens 1-8 N N N N N H H H H H Movement screen group 8, screens 1-8 N N N N N H H H H H N H )LJ'DWD0RGXOH&RQWHQWV0RYHPHQW%ORFNV 1070 072 168-101 (98.04) GB Interfaces – PLC <-> Operator Terminals 5-19 5.3.8 Data Modules – BT 1-4 Diagnostic Results • DM234 MMI-MADAP operator terminal 1 (base station 1) • DM239 MMI-MADAP operator terminal 2 (base station 2) • DM244 MMI-MADAP operator terminal 3 (base station 3) • DM249 MMI-MADAP operator terminal 4 (base station 4) Also, optional data modules DM222 through DM225 (substations 5-8) Data ranges: • Automatic diagnostics of cascade first-value errors • Manual diagnostics of faulty cascades • Cascade statuses With the aid of the MMIMADAP program module, a cascade rangespecific diagnostic routine can be parameterized. Up to four different cascade ranges can be diagnosed per central processing unit. This facilitates a station-specific diagnostic routine at the operator terminal. F 1070 072 168-101 (98.04) GB For additional information, refer to sections discussing diagnostics and operator terminal connectivity. 5-20 Interfaces – PLC <-> Operator Terminals Data module contents, DM234 "BF1_Diag": Diagnostic results, (example of operator terminal 1) 6LJQ No. Symbol Type Data field D 0 1FLAGS D D D D 2 4 6 8 1TT/MM 1JJ/SS 1MIN/SEK 1WoT/__ D 10 1KNr/SNr D D 12 14 D 1BstNr 1AnzMeld 16 : D 142 1_01ANW : 1_64ANW D 144 D 146 D 148 1EWint1 1EWint2 1EWint3 D 150 : D 218 1K_Inf01 : 1K_Inf35 D 220 : D 276 1K_Inf36 : 1K_Inf64 D 278 D 280 D 282 1K/S-Nr 1Baust 1Z/Anz D 284 : D 410 D 412 H01.ANW : H64.ANW D 420 : D 434 D 436 D 438 1St1 D 440 : D 510 1noKomm : : 1St8 ; ; ; ; Word ; Word Word Word Word ; Word ; Word ; Word ; Word : Word ; Word Word Word ; Word : Word ; Word : Word ; ; ; Word ; Word ; Word ; Word : Word Word ; Word : Word Word Word ; Word : Word F First-value message ================= Control flags From here: Object 1 for PROFIBUS communications N B Date / Time N N N N H H H H Cascade no. / Step no. N H Station number / Step module number N H Number of messages N H Instruction codes 1 - 64 for Auto diagnostics N N H : H N N N H H H : : Cascade information, cascade 1 - 64 N : H : H : N From here: Object 2 for PROFIBUS communications N : : N H : H From here: Manual diagnostics ==================== Cascade number / Step number N H Module type / Module number N H Cascade status / Number of messages N H Instruction codes 1 - 64 for Manual diagnostics N : : N N H : H H Station list, Last cascade / First cascade N : : N N N H : H H H From here: Internal data, no communication data N : : N H : H )LJ'DWD0RGXOH&RQWHQWV'LDJQRVWLF5HVXOWV 1070 072 168-101 (98.04) GB Interfaces – PLC <-> Operator Terminals 5-21 5.3.9 Data Module DM253 – I/O Assignment and SC Table Data ranges: • Display of I/EI and O/EO assignment for up to 4 central processing units. • Display of information about modules located in the PLC module rack. • Version management of standard PLC program modules. The MMIMADAP program module furnishes the E/EI and O/EO assignment, plus all data from the SC table to the MMI-MADAP operator terminal. The data range encompassing data words D380 through D472 is available for standard PLC module version management. Versions management for standard PLC program modules The data range D380 through D422 is reserved for BOSCH-proprietary standard PLC program modules. D380 Word MMI-MADAP version ID D382 ASCII "MMIMADAP" D390 Word D392 ASCII "KETTE" D400 Word D402 ASCII "DIAGMMI" D410 Word D412 ASCII "DPSTATUS" D420 Word D422 ASCII Reserved: Bosch module designation D430 Wort D382 ASCII User module 1, module designation .. .. .. D470 Wort User module 5, version ID D472 ASCII User module 5, module designation KETTE version ID DIAGMMI version ID DPSTATUS version ID Reserved: Bosch version ID User module 1, version ID Version ID: 1070 072 168-101 (98.04) GB • HIGH Byte: Bit 0-3 = leading comma 0-16 • HIGH Byte: Bit 4-7 = intermediate version A-F • LOW Byte: Bit 0-3 = trailing comma 0-16 5-22 Interfaces – PLC <-> Operator Terminals Data module contents, DM253 "EA_SK": I/O assignment and SC table 6LJQ No. Symbol Type Data field D D D D D D D D D D D D D D D D D D D D D D D D D D D D D D D D D D D D D D D D 0 32 34 36 38 40 : 64 66 68 70 72 : 96 98 100 102 104 : 128 130 132 134 136 : 164 166 168 170 : 184 186 188 190 192 194 196 198 200 202 204 206 208 : 350 352 D 354 D 356 D D D D D 358 360 362 364 366 : 0EBel15 0EBel31 0EBel47 0EBel63 1EBel15 : 0ABel15 0ABel31 0ABel47 0ABel63 1ABel15 : 0EZBel15 0EZBel31 0EZBel47 0EZBel63 1EZBel15 : 0AZBel15 0AZBel31 0AZBel47 0AZBel63 1AZBel15 : 0ZS=akt 1ZS=akt 2ZS=akt 3ZS=akt : SysBerA DB-Ziel SK/ZS400 SKVers 1Typ 1PerAdr 1EZ/AZ 1E/A 1BlAdr 1BlAnz 1BGvorh 1Vers 2Typ : 10Vers V-DIAG V-MMI V-KETTE BG-Nr Bild-Nr SKerst HandGlob : ASCII Word Word Word Word Word N N N N N N : Word Word Word Word Word : Central processing unit 1-3: I assignment, bytes 15-63 : Central processing unit 0: O assignment, bytes 0-63 : Central processing unit 1-3: O assignmt., bytes 15-63 : Central processing unit 0: EI assignment, bytes 0-63 : Central processing unit 1-3: EI assignmt., bytes 15-63 : Central processing unit 0: EO assignment, bytes 0-63 N N N N N : Word Word Word Word Word N N N N N : Word Word Word Word Word N N N N N : Word Word Word Word : Central processing unit 1-3: EO assign., bytes 15-63 : N N N N : Word Word Word ASCII ASCII Word Word Word Word Word Word ASCII ASCII : N N N N N N N N N N N N N : ASCII Word ; Word ; Word ; Word Word Word Word Word F internal Central processing unit 0: I assignment, bytes 0-63 : : System coordinator / ZS40x Version Module 1 Type Peripheral address EI/EO assignment I/O assignment Block address Block count (number of blocks) Module in rack Version Modules 2-10 (identical to module 1) : N N B B B B B : B B B B B : B B B B B : B B B B B : H H H H : H H D D D D D D H : H Version ID of "DIAGMMI" program module N H Version ID of "MMIMADAP" program module N H Version ID of "KETTE" program module N N N N N : : : H D D H H : 1070 072 168-101 (98.04) GB Interfaces – PLC <-> Operator Terminals No. D D D D D D D D D D D D D D D D D D D D D D D D 380 382 390 392 400 402 410 412 420 422 430 432 440 442 450 452 460 462 470 472 480 506 508 510 Symbol 0PB_Vers 0PB_Name 1PB_Vers 1PB_Name 2PB_Vers 2PB_Name 3PB_Vers 3PB_Name 4PB_Vers 4PB_Name 5PB_Vers 5PB_Name 6PB_Vers 6PB_Name 7PB_Vers 7PB_Name 8PB_Vers 8PB_Name 9PB_Vers 9PB_Name Type ; Word ASCII Word ASCII Word ASCII Word ASCII Word ASCII Word ASCII Word ASCII Word ASCII Word ASCII Word ASCII Word Word Word Word 6LJQ Data field F Version ID and text for default function modules N N N N N N N N N N N N N N N N N N N N N N N N H MMIMADAP H KETTE H DIAGMMI H MMIAUSL H DPSTATUS H ........ H ........ H ........ H ........ H ........ H H H H )LJ'DWD0RGXOH&RQWHQWV,2$VVLJQPHQWDQG6&7DEOH 1070 072 168-101 (98.04) GB 5-23 5-24 Interfaces – PLC <-> Operator Terminals 5.3.10 Machine Usage and PROFIBUS-DP Diagnostics The data module DM254 provides the data relating to machine usage and PROFIBUS-DP diagnostics for display on the BT100 operator terminal. Data module contents, DM254 "AL_DP_D": Machine usage display & DP-Diagnostics 6LJQ No. Symbol Type Data field D D D D D D 0 2 4 6 8 10 PS1heut PS1gest PS2heut PS2gest PS3heut PS3gest D D D D D D 12 14 16 18 20 22 ISS1heut ISS1gest ISS2heut ISS2gest ISS3heut ISS3gest D D 24 26 P_Theut P_Tgest D D 28 30 Jah_heut Jah_gest D D 32 34 ME_Theut ME_Tgest D D 36 38 kT_Theut kT_Tgest D D 40 42 Pv_Theut Pv_Tgest D D 44 46 St_Theut St_Tgest D D 48 50 Ss_Theut Ss_Tgest D D 52 54 Tag_heut Tag_gest D D 56 58 Mon_heut Mon_gest D D D D D D D 60 62 64 66 68 70 72 SSS1heut SSS1gest SSS2heut SSS2gest SSS3heut SSS3gest : : ; Word Word Word Word Word Word ; Word Word Word Word Word Word ; Word Word ; Word Word ; Word Word ; Word Word ; Word Word ; Word Word ; Word Word ; Word Word ; Word Word ; Word Word Word Word Word Word Word F Shifts – Production N N N N N N D D D D D D Shifts – Actual part/piece counts N N N N N N D D D D D D Days – Production N N D D Date entry – Year N N D D Days – Machine On N N D D Days – No Parts N N D D Days – Buffer Full N N D D Days – Fault N N D D Days – Standstill N N D D Date entry – Day N N D D Date entry – Month N N D D Shifts – Nominal/setpoint part/piece counts N N N N N N N : : : D D D D D D H : 1070 072 168-101 (98.04) GB Interfaces – PLC <-> Operator Terminals No. D 100 D 102 : D 192 D 194 : D 204 D D D D D D 206 208 210 212 214 216 D 218 D 220 D 222 D 224 D 226 D 228 D 230 D 232 D 234 D 236 D D D D D D D D Symbol 01Taktz 02Taktz : 47Taktz 48Taktz : ErfassW S1_100% PS1_akt S2_100% PS2_akt S3_100% PS3_akt Sch1akt BearbSt GlobalSt Zeit_m_s Zeit_T_h Zeit_M_W Zeit_J_K EmpfangS EmpfangL EmpfDatA 238 240 242 244 246 248 250 252 1EmpfD1 1EmpfD2 1EmpfD3 1EmpfD4 1EmpfD5 1EmpfD6 1EmpfD7 1EmpfD8 D 254 D 256 : D 266 D 268 2EmpfD1 2EmpfD2 : 2EmpfD7 2EmpfD8 D 270 D 272 : D 282 D 284 3EmpfD1 3EmpfD2 : 3EmpfD7 3EmpfD8 6LJQ Type ; Word Word N N : : : : : Recorded value before and after LOGIK N N : ; Word ; ; ; Word Word Word Word Word Word ; Word ; ; Word ; Word ; Word ; Word ; Word ; Word ; Word ; Word ; ; Word ; Word Word Word Word Word Word Word Word ; Word Word N H H : H H : B Shift and current production duration Sn_100%: Shift length ./. Sum of all breaks Sn_akt: accrued production length N N N N N N D D D D D D "Shift 1-3 active" message N B From here: PROFIBUS-DP diagnostics Processing status N B Global status N B Minute / Second N H Day / Hour N H Year / Month N H Switching matrix address / Weekday N H Receive status N H Receive length N H Receive data start DP-Diagnostics interpretation mask N H Slave(s) not reachable N N N N N N N N B B B B B B B B One or more slaves report configuration fault N N : Word Word ; Word Word : : N N B B : B B One or more slaves report statistical diagnostics N N : 1070 072 168-101 (98.04) GB F Cycle times, mirrored from DM217 for display Word Word Word Word Data field 5-25 : N N : B B : B B 5-26 No. Interfaces – PLC <-> Operator Terminals Symbol D 286 D 288 : D 298 D 300 4EmpfD1 4EmpfD2 : 4EmpfD7 4EmpfD8 D 302 D 304 : D 314 D 316 5EmpfD1 5EmpfD2 : 5EmpfD7 5EmpfD8 D 318 D 320 : D 330 D 332 6EmpfD1 6EmpfD2 : 6EmpfD7 6EmpfD8 : D 510 : noS_akt Type ; Word Word 6LJQ F N N : Word Word ; Word Word : B B : B B : N N One/more slaves not ready for cyclical data exchange N N : Word Word ; Word Word : B B : B B : N N One or more slaves report slave error N N : Word Word ; : B B : B B : N N : Word Data field One or more slaves report expanded diagnostics : Active shift not to be processed IF # 0 : : D N )LJ'DWD0RGXOH&RQWHQWV0DFKLQH8VDJHDQG'3'LDJQRVWLFV 1070 072 168-101 (98.04) GB Interfaces – PLC <-> Operator Terminals 5-27 5.3.11 Data Module DM255 – Global Operating Data Data ranges: • 511 serial user messages coming/going • 128 parallel user status messages, priority-controlled • List of available data modules • Cycle times, watchdog PLC • Time values of organization modules OM18 thru OM25 • PLC status and error bits • Operator terminal and PLC system times In data module DM255, the MMIMADAP program module provides the above mentioned data ranges – with the exception of serial and parallel messages – for the MMI-MADAP operator terminal. Serial and parallel messages are used to display and manage machine statuses and errors on the MMI-MADAP operator terminal. The messages are generated on the PLC by the user, and are then made available in data module DM255. The messages appear on all operator terminals that are connected to the central processing unit. 6HULDOPHVVDJHVFRPLQJJRLQJ DM255/D0 Serial messages coming/going D0.0-D0.8 Mssage number 1 - 511dec D0.9 Acknowledge all active messages D.10 Message received (from oper. terminal 1) D.11 Message received (from oper. terminal 2) D.12 Message received (from oper. terminal 3) D.13 Message received (from oper. terminal 4) D.14 Message comes D.15 Message goes Serial messages that are coming/going are managed by the user in the PLC program, whereby the transmission of a message is automatically read by the MMI-MADAP operator panel, and the reception is acknowledged. 1070 072 168-101 (98.04) GB 5-28 Interfaces – PLC <-> Operator Terminals Functional principle: Coming messages: • PLC Message number (bit 0-8) entered with coming-bit (bit 14). • Oper. term. Acknowledgement of message reception (bit 10/BF1 - bit 13/BF4). Coming message is entered in "active message record." • PLC • PLC Message number (bit 0-8) entered with going-bit (bit 15). • Oper. term. Acknowledgement of message reception (bit 10/BF1 - bit 13/BF4). Going message writes active message into "historic message record" and deletes it in "active message record." • SPS Once all operator terminals have acknowledged, acknowledgement bits must be deleted. A new message can be transmitted. Going messages: Once all operator terminals have acknowledged, acknowledgement bits must be deleted. A new active message can be acknowledged. Acknowledging all active messages: • • • PLC Entering "all active messages" bit (bit 9). Oper. term. The "all active messages" bit is deleted. Active messages are entered in "historic message record" and deleted from "active message record." PLC A new coming message can be transmitted. 1070 072 168-101 (98.04) GB Interfaces – PLC <-> Operator Terminals 5-29 3DUDOOHOVWDWXVPHVVDJHV D2.0- D17.7 128 Bit parallel status messages As status messages serve only display functions, they are not stored in the operator terminal. The status messages entered by the user are automatically read by the MMI-MADAP operator terminal, and the assigned text messages are displayed. Functional principle: For each status message, one bit is available to the user. D2.0 = HIGH Display status message 1 highest Do not display status message 1 priority = LOW : : D17.7 = HIGH ↓ : Display status message 128 lowest Do not display status message 128 priority = LOW Up to 128 parallel messages can be active at the same time. The MMIMADAP operator terminal imposes a display priority, whereby status message 1 (D2.0) is assigned the highest, and status message 128 (D17.7) the lowest priority. /LVWRIDYDLODEOHGDWDPRGXOHVH D32.0 Bit through D63.7 Data module DM1 through DM255 available / not available Bit The MMIMADAP program module writes the available data modules into the list. For each existing data module, the corresponding bit in the list is set HIGH. The process assigns bit D32.0 to data module DM1 and bit D63.7 to data module DM255. In the PLC, the data module list update is initiated by the trigger pulse (Power-up or restart after STOP/RUN). One-time initiation also occurs upon selecting the base screen, and continuous update inititiation is effected by selecting the DM list on the MMI-MADAP operator terminal. 1070 072 168-101 (98.04) GB 5-30 Interfaces – PLC <-> Operator Terminals 3/&VWDWXVDQGHUURUELWV PLC status bits D86.0 Bit Battery fault D86.1 Bit Outputs disabled D86.2 Bit I/O fixed D86.3 Bit Buffer Full system command D86.4 Bit Free D86.5 Bit Status Message Active D86.6 Bit Free D86.7 Bit Free PLC error bits / PLC in Stop D87.0 Bit Addressing fault D87.1 Bit PM parameter error D87.2 Bit Non-existent PM called D87.3 Bit Module stack fault D87.4 Bit Application stack overrun / underrun D87.5 Bit Parameter instruction, system command D87.6 Bit No data module active D87.7 Bit Cycle time error The MMIMADAP program module enters PLC status and error bits into the data word. The MMI-MADAP operator terminal reads the information and displays it on the MMI-MADAP operator terminal. The user can read the information and utilize it in his program. 1070 072 168-101 (98.04) GB Interfaces – PLC <-> Operator Terminals 5-31 6\VWHPWLPHRQRSHUDWRUWHUPLQDODQG3/& Time on MMI-MADAP operator terminal D96 Word Minute / Second D98 Word Day / Hour D100 Word Year / Month D102 Word Weekday Time on PLC D104 Word Minute / Second D106 Word Day / Hour D108 Word Year / Month D110 Word Weekday If the system time is reset on a MMI-MADAP operator terminal, the terminal will transfer the time into the data module. As a consequence, the MMIMADAP program module synchronizes the PLC system time. Multiple operator terminals respond by cyclically synchronizing to the PLC system time. The user can read the time and/or date and utilize it in his program. 1070 072 168-101 (98.04) GB 5-32 Interfaces – PLC <-> Operator Terminals Data module contents, DM255 "BF_Globa": Data module valid for all operator terminals 6LJQ No. Symbol Type Data field D 0 D D D D D D D D D 2 4 6 8 10 12 14 16 18 : D 30 D D D D D D D D D D D D D D D D 32 34 36 38 40 42 44 46 48 50 52 54 56 58 60 62 D 64 D D 66 68 D D D D D D D D 70 72 74 76 78 80 82 84 D 86 D D D D 88 90 92 94 ; SeriMeld Word ; 1ZustM Word 2ZustM Word 3ZustM Word 4ZustM Word 5ZustM Word 6ZustM Word 7ZustM Word 8ZustM Word Word : : ; Fl_DBL Word ; 1DBL Word 2DBL Word 3DBL Word 4DBL Word 5DBL Word 6DBL Word 7DBL Word 8DBL Word 9DBL Word 10DBL Word 11DBL Word 12DBL Word 13DBL Word 14DBL Word 15DBL Word 16DBL Word ; Zykl_max Word ; Zykl_akt Word ; WatchDog Word ; T-OB18 Word T-OB19 Word T-OB20 Word T-OB21 Word T-OB22 Word T-OB23 Word T-OB24 Word T-OB25 Word ; Z-Bits Word ; EW_BF1 Word EW_BF2 Word EW_BF3 Word EW_BF4 Word F Serial messages, coming / going N D Parallel status messages N N N N N N N N N : : Transition bits for generating data module list upon displaying base screen N B B B B B B B B H : H Data module list, 1=available 0=not available N N N N N N N N N N N N N N N N B B B B B B B B B B B B B B B B Maximally measured cycle time N D Time of last cycle N D Watchdog setting N D Time values for time-controlled processing N N N N N N N N D D D D D D D D PLC status and error bits N B Handshake for diagnostic results N N N N H H H H 1070 072 168-101 (98.04) GB Interfaces – PLC <-> Operator Terminals No. Symbol D 96 D 98 D 100 D 102 BT-m/s BT-T/h BT-J/M BT-WT D D D D SPS-m/s SPS-T/h SPS-J/M SPS-WT 104 106 108 110 D 112 : int1 : D 118 D 120 : Ausl_akt D156 D158 : D168 D170 EW_KZ1 EW_KZ2 : EW_KZ7 EW_KZ8 D172 D174 D176 D178 : EW_St5 EW_St6 EW_St7 EW_St8 Type ; Word Word Word Word ; Word Word Word Word ; ASCII : ; Word Word : ; 6LJQ N N N N System time on PLC N N N N H H H H N : N N : Word Word : Word Word ; N N : N N Word Word Word Word ; N N N N D188 MehrBel Word ; N Word Word Word Word ; Word ; Word ; Word Word Word Word : Word N N N N D200 D202 D204 D206 D208 : D 510 StatEdit K_Ber1 K_Ber2 K_Ber3 K_Ber4 : : First-value communication counter, station 1-8 Value 500 (approx. 10 sec) acknowledges first value : H H : D D : D D H H H H Station mask assignment / BT1-4, Multiple bit assignments not permitted. Bit0 > Stat5 (DM222) , Bit3 > Stat8 (DM225) 0000 0000 0000 0000 Multiple station assignment HIGH byte=1:multiple / LOW byte:1st multiple assignment found B B B B H Substation cascade ranges 5-8, HIGH byte: last cascade, LOW byte: cascade 1, Overlaps are possible 0000 0000 0000 0000 BT_Diagnostics participants (auxiliary marker) H H H H B Editing screen active H Operator terminal cascade ranges 1-4 N N N N : : N )LJ'DWD0RGXOH&RQWHQWV*OREDO'DWD 1070 072 168-101 (98.04) GB : First values (FV) to operator terminals, station 5-8 Entry: 1:FV active, 2:oper. term. has acknowledged N N N N BT_Teiln : Machine usage active Word Word Word Word ; D198 F H H H H BT1StMsk BT2StMsk BT3StMsk BT4StMsk K_Ber5 K_Ber6 K_Ber7 K_Ber8 Data field System time on terminal D180 D182 D184 D186 D190 D192 D194 D196 5-33 H H H H : H 5-34 Interfaces – PLC <-> Operator Terminals 1070 072 168-101 (98.04) GB MMI-MADAP Operator Terminal 6-1 6 MMI-MADAP Operator Terminal 6.1 Introduction Two software modules are available: • • Development module Runtime module The development module facilitates the development of user-defined applications. It also provides for the extension of the existing MMI-MADAP application. The runtime module facilitates the operation, diagnosing and visualization of the system without, however, the option to generate new screens. MMI-MADAP is a software application for facilitating the operation, diagnostics and visualization of machine systems. Direct communication with the connected PLC controller is possible via the PROFIBUS-FMS or via a point-to-point connection. MMI-MADAP provides 64 user screens for the purpose of implementing user-defined visualization and controller functions. The standard software provides the following functions: F • Display of power-up criteria • Execution of movements, • User screens, e.g. system overview • Status and information display of the communicating PLC controller • Display of entire PLC data range • Information regarding machine system via display of status and error text messages that are PLC-controlled • Cascade diagnostics (Visualization: PLC links of first-value and sequence errors). BOSCH documentation reference MMI-MADAP for System or Machine Operators — Software Manual 1070 072 168-101 (98.04) GB Part no. 1070 072 167 6-2 MMI-MADAP Operator Terminal 6.2 System Requirements for MMI-MADAP Operator Terminal System requirements for MMI-MADAP software: PC components Processor Pentium 100 MHz or higher Memory (RAM) 16 MB Disk space 100 MB Additionally, for communication via PROFIBUS: PROFIBUS PC card PB-IF-03 PROFIBOARD, (Softing) CP 5412(A2), Mfg. Siemens F Only the use of the Bosch BT100 operator terminal assures the user of the perfect match between hardware and software! Software Operating system F DOS 6.22 and Microsoft Windows 3.11 The MMI-MADAP software is exclusively designed for use with Microsoft Windows 3.11. 1070 072 168-101 (98.04) GB MMI-MADAP Operator Terminal 6-3 6.3 Software Installation 6.3.1 Supplied Software Files • 00,0$'$3GLVNHWWHV 2SHUDWLQJDQGYLVXDOL]DWLRQV\VWHPIRU%RVFKFRQWUROV\V WHPV • )%00,0$'$3GLVNHWWH )XQFWLRQPRGXOHVDQG352),%86FRQILJXUDWLRQIRUWKH3/& 6.3.2 MMI-MADAP Introduction The CONFIG.SYS and AUTOEXEC.BAT file must be expanded and/or modified. F These two files are normally located in the root directory of drive C:\. Modifications can be made with any ASCII editor. • &21),*6<6ILOH The use of the MMI-MADAP software packet requires the following entries: DEVICE=C:\WINDOWS\HIMEM.SYS DEVICE=C:\DOS\SETVER.EXE DOS=HIGH,UMB FILES=99 DEVICEHIGH=C:\DOS\RAMDRIVE.SYS 160 512 /E In addition, if a PROFIBUS module is to be used, the following modification will be required: DEVICE=C:\DOS\EMM386.EXE NOEMS X=D000-DFFF 1070 072 168-101 (98.04) GB 6-4 MMI-MADAP Operator Terminal • $872(;(&%$7ILOH The use of the MMI-MADAP software packet requires the following entries: PROMPT $P$G CLS PATH C:\WINDOWS;C:\DOS;C:\;C:\MMIMADAP\BIN SET TEMP=C:\DOS ; (NOTE: Please enter the following ; line prior to the installation!!) C:\DOS\SMARTDRV /X D: MD MMIMADAP CD MMIMADAP COPY C:\MMIMADAP\*.DAT D: C: WIN Subsequent to the installation of the MMI-MADAP operator terminal software the files named AUTOEXEC.MMI and CONFIG.MMI will be automatically generated in the C:\ root directory. The referred files contain the above mentioned entries, and can be renamed by the user to AUTOEXEC.BAT and CONFIG.SYS, respectively. The Bosch BT100 operator terminal contains all data in the AUTOEXEC.BAT and CONFIG.SYS files. 1070 072 168-101 (98.04) GB MMI-MADAP Operator Terminal 6-5 6.3.2.1 Installation diskettes The MMI-MADAP software is supplied in the form of a set of diskettes that can be directly installed. However, you can also download the MMI-MADAP software from the Bosch mailbox, and create your own set of installation diskettes. The Bosch mailbox at +49 6062 7217 always provides the current version of the MMI-MADAP software in the MMIMADAP Filebox. 078580.EXE Diskette1 078581.EXE Diskette2 078582.EXE Diskette3 078583.EXE Diskette4 078584.EXE Diskette5 078853.EXE Diskette6 Download these files to the C:\ drive of your computer. Continue by inserting a blank diskette into drive A:\. At the DOS prompt, type the command MD MMIMADAP to create a new directory named A:\MMIMADAP. Type CD MMIMADAP to change to the new directory. Select the .EXE file on C:\078580.EXE. This will cause installation diskette 1 to be created. Use the same procedure for all remaining .EXE files. You have now created the MMI-MADAP set of installation diskettes consisting of 6 diskettes. Please be sure to label the diskettes "MMIMADAP/Disk 1 of 6" through diskettes consisting of 6 diskettes. Please be sure to label the diskettes "MMI-MADAP/Disk 1 of 6" through "MMIMADAP/Disk 6 of 6". 6.3.2.2 Installing MMI-MADAP from Set of Diskettes If you are performing a software upgrade and/or a new MMIMADAP installation, and if applicable, precede the installation by saving your existing MMI-MADAP files under a new name in order to save your individualized definitions. ,QVWDOODWLRQ The installation uses Microsoft Windows 3.1 or 3.11 exclusively. Therefore be sure to begin by starting Windows. Insert Installation Diskette 1 into the disk drive. Run the SETUP.EXE program located in A:\MMIMADAP, e.g. via the File Manager. 1070 072 168-101 (98.04) GB 6-6 MMI-MADAP Operator Terminal The MMI-MADAP Setup window will briefly appear. It contains the version number of the MMI-MADAP software packet that you are using. Please be advised that the windows will appear in a Germanlanguage version only. Wherever required, specific explanations will be given in this manual. In the Setup sign-on window that follows, press Weiter (Continue) to set up your program on the hard disk. (The Weiter button corresponds to the Return or Enter key.) The installation will now commence. 1070 072 168-101 (98.04) GB MMI-MADAP Operator Terminal 6-7 Please follow the user prompt to insert the next diskette when required. 6RIWZDUHSURWHFWLRQ Once the diskette installation has been concluded, you will be asked to select the desired software protection type. In response, press the Alt+TAB key combination until the title UNISOFT PROTECTION MANAGER is highlighted. As a default, the protection type is set to Hardkey protection. Continue by pressing Alt+H to select Hardkey or Alt+S to select Softkey protection. Once this is done, press Alt+C to activate the Check function. If you have changed the protection method, you will be alerted to this change by an appropriate system message. In response to this message, press Return. If a valid license is found, the licensing procedure is hereby concluded. 1070 072 168-101 (98.04) GB 6-8 MMI-MADAP Operator Terminal If a valid license is not found, a window containing an 18-digit Site Key number will open. Write down this number, and send a fax to: Fa. Bosch/Erbach. Attn. Mr. Kuschel, fax no. +49 6062 78 784 (where +49 denotes your access code required to get an outside line, plus the country code for Germany). The fax form named MMIFAX.WRI is located in the MMIMADAP directory of the mailbox. If you are a supplier or subcontractor for system projects, you are advised to ensure prior coordination with your customer regarding this matter. In response to your fax message, you will receive the chargeable secret code, known as the Site Key. Once you have entered the verification number, select the Authorize button, followed by pressing Return again. This activates the text box. Press TAB to move to the OK button, and press Return. To exit the licensing function, press OK. You can reach this button by repeatedly pressing the TAB key. The next window to appear informs you that a copy of both the AUTOEXEC.MMI and CONFIG.MMI files were installed in the main directory, and that the original AUTOEXEC.BAT and CONFIG.SYS files were not modified. Acknowledge this message by pressing Return. Once the licensing procedure has been concluded, the next step will be the configuration of the operator terminal. 1070 072 168-101 (98.04) GB MMI-MADAP Operator Terminal 6-9 6.3.2.3 Configuring the Operator Terminal There exist three different options for establishing communications between the operator terminal and the control unit: • Point-to-point connection, using the Bosch BUEP19E transmission protocol. • PROFIBUS-FMS connection, using the CP5412-A2 hardware module manufactured by Siemens. • PROFIBUS-FMS connection, using the PROFIBOARD hardware module manufactured by Softing Mfg. At this point, the operator terminal configuration procedure provides you with a selection of desired PLC controller connections. %8(3'ULYHU Subsequent to selecting the BUEP driver, enter the interface parameters. These must correspond to the PLC control unit parameters. 1070 072 168-101 (98.04) GB 6-10 MMI-MADAP Operator Terminal PROFIBUS CP5412-A2 and PROFIBOARD modules This procedure requires the desired PROFIBUS station address for the operator terminal to be entered. At the prompt: %LWWHJHEHQ6LHGLH=61XPPHUHLQ, please enter the number of the central processing unit (ZSx ...). This will be a number between 0 and 3. At the prompt: %LWWHJHEHQ6LHGLH00,1XPPHUHLQ, please enter the number of the connected operator terminal. This will be a number between 1 and 4. At the prompt: 8SGDWHRGHU1HXLQVWDOODWLRQGHU352),%86'DWHLHQRGHU $EEUXFK" To select the right driver files, indicate whether this installation is an update of existing software (type 8), or a new installation of the PROFIBUS files (type 1). If you wish to cancel, type ($). Continue by selecting the PROFIBUS files that will be used to configure the system. Once the driver type has been selected, the *.DRV driver files will be loaded. 1HZLQVWDOODWLRQ Typing (1) copies all Bosch-proprietary forms for the selected combination of ZS central processing unit and operator terminal into the destination directory, C:\MMIMADAP\CONFIG. BUEP001.DRV - BUEP050.DRV BOSCH internal SL2A2001.DRV - SL2A2050.DRV BOSCH internal SFMS001.DRV - SFMS050.DRV BOSCH internal BUEP051.DRV - BUEP130.DRV Blank standard forms for the user SL2A2051.DRV - SL2A2130.DRV Blank standard forms for the user SFMS051.DRV - SFMS130.DRV Blank standard forms for the user 1070 072 168-101 (98.04) GB MMI-MADAP Operator Terminal 6-11 8SGDWH Typing (8) copies all Bosch-internal forms for the selected combination of ZS central processing unit and operator terminal (e.g. SL2A2001.DRV - SL2A2050.DRV) into destination directory C:\MMIMADAP\CONFIG. Also, the user forms that are assigned to the operator terminal (SL2A2051.DRV - SL2A2130.DRV or SFMS051.DRV - SFMS130.DRV) are copied from the respective user directory into destination directory C:\MMIMADAP\CONFIG. User directory: C:\PROFIUSE\1 Forms for operator terminal 1, 5, 9, 13 C:\PROFIUSE\2 Forms for operator terminal 2, 6, 10, 14 C:\PROFIUSE\3 Forms for operator terminal 3, 7, 11, 15 C:\PROFIUSE\4 Forms for operator terminal 4, 8, 12, 16 3DFNLQJ Once the installation has been performed correctly, it is an absolute requirement to optimize the database by compacting (packing) the files.. Also, the Setup Info window informs the user that, in case a Siemens CP5412-A2 card is being used, the system must be restarted subsequent to the installation. To start the packing program, press OK. In the Database Pack Utility window, select the PACK button. Once the procedure has ended, select the Close button to exit the program. 1070 072 168-101 (98.04) GB 6-12 MMI-MADAP Operator Terminal 00,0$'$33URJUDPJURXS All MMI-MADAP programs are located in the MMI-MADAP program group. 6WDUWLQJ00,0$'$3 To start the software, double-click the MMIMADAP icon in the MMIMADAP program group window. NOTE: When using the CP5412-A2 PROFIBUS module: To ensure proper operation of the system subsequent to an installation, a restart of the operator terminal will be required. 6WDUWLQJ00,0$'$3DXWRPDWLFDOO\ A restart of the MMI-MADAP operator terminal will cause an automatic restart of the MMI-MADAP application. If you want to prevent this autorestart, a modification of your WIN.INI file will be required. Use an editor to open the file, and remove the entry: • RUN C:\MMIMADAP\BIN\DIAG.EXE This concludes the installation and configuration of the MMI-MADAP software. F The WIN.INI file is normally located in the directory named C:\WINDOWS. Modifications to this file can be made with any ASCII editor. 1070 072 168-101 (98.04) GB MMI-MADAP Operator Terminal 6-13 Starting MMI-MADAP manually In the Windows Program Manager, select the MMI-MADAP directory. Start the MMI-MADAP software by double-clicking the MMIMADAP icon (shown below). Changing operator terminal number after installation In the Windows Program Manager, select the MMI-MADAP directory. Double-click the MMI-Panel Config icon (shown below), and make the required corrections. Licensing operator terminal after installation In the Windows Program Manager, select the MMI-MADAP directory. Double-click the Registration Tool icon (shown below), and make the required corrections. 1070 072 168-101 (98.04) GB 6-14 MMI-MADAP Operator Terminal 6.3.3 Configuring Diagnostics Introduction In order to display diagnostic information about cascades and steps on the MMI-MADAP operator terminal, additional display information will be required. Upon starting the MMI-MADAP application, this information is derived from the project symbol file and the respective cascade modules. The project symbol file and step modules SCHRK1 through SCHRK64 (to the extent available) must be located in the directory C:\MMIMADAP\KETTEN. The names for symbol file and step modules may be freely selected. F Please bear in mind that the symbol file as well as the step modules must have been created with the WinSPS application. Symbol file and step module installation From your current PLC project directory, copy the current version of the project symbol file named xxx.SXS, as well as all step modules named SCHRK1.PXO through SCHRK64.PXO to C:\MMIMADAP\KETTEN (xxx = name of symbol file). as a default, MMI-MADAP expects to see a symbol file bearing the name SYMBOL..SXS. If the name of your file is different, it is recommended that you rename your file accordingly. It is, however, possible to adapt the entry in the DIAG.INI file: SymFile=C:\MMIMADAP\KETTEN\xxx.SXS The DIAG.INI file is located in the C:\WINDOWS directory. 1070 072 168-101 (98.04) GB MMI-MADAP Operator Terminal 6-15 6.4 MMI-MADAP Directory Structure )LJ'LUHFWRU\7UHH00,0$'$32SHUDWRU7HUPLQDO • &?00,0$'$3 This directory contains all PROFIBUS configuration files, plus the generated *.DAT files and other system files. • &?00,0$'$3?$/$50 For each month, the MMI-MADAP software creates an alarm file. All alarm files are held in this directory. • &?00,0$'$3?%,1 This is the directory for the entire basic system, including, for example, all .EXE files. • &?00,0$'$3?&21),* This directory holds all standardization components and associated files. • &?00,0$'$3?'$7$%$6( This is the directory for the MMI-MADAP database. 1070 072 168-101 (98.04) GB 6-16 MMI-MADAP Operator Terminal • &?00,0$'$3?',$*126( All protocol record files generated by the diagnostics function are stored in this directory. • &?00,0$'$3?'59 This directory holds all required driver tools. • &?00,0$'$3?+,/)( The MMI-MADAP packet encompasses an online Help system. The required Help text files are located in this directory. All text files may be modified by the user with the aid of a text editor. • &?00,0$'$3?+67 This directory holds historic trend values used by the application. • &?00,0$'$3?.(77(1 For the purpose of displaying operand text, etc., the diagnostic module requires the cascade files and the symbol files used by the project. These files must be deposited here by the user. • &?00,0$'$3?/$1*8$*( This directory is used only internally for the different national language versions by the basic development and runtime software. • &?00,0$'$3?/,% The UNISOFT development packet supplies existing symbol objects. These are located in this directory. • &?00,0$'$3?6&5((1 All MMI-MADAP screen are stored here. • &?00,0$'$3?6<0%2/ Standard functions created in the development editor can be stored here. • &?00,0$'$3?8&2 This directory is reserved for additional customer objects. (Partially written in C high-level language.) 1070 072 168-101 (98.04) GB MMI-MADAP Operator Terminal 6-17 6.5 Definition of MMI-MADAP Data Ranges Introduction The MMI-MADAP standard software packet defines different data ranges. The term data ranges encompasses the following components: • Online data • Alarms (Alarm files) • Math worksheets (Math files) • Time-controlled processing (Scheduler files) • Trend values (Trend files) • Report outputs (Report files) • Data management (Recipe files) The entirety of data ranges is predefined and partially reserved for the user. F With the exception of the online data, all components are located in the C:\MMIMADAP\CONFIG directory. Online data The MMI-MADAP software enables you to create new definitions while online. These definitions are stored in the form of *.DAT files in the C:\MMIMADAP directory. The respective files can be randomly modified and integrated into new projects. The copy function can be automated through the use of batch files or in the PROJEKT screen of the MMI-MADAP user interface. The online data encompasses the following data groups: 1070 072 168-101 (98.04) GB • Power-up screens: Power-up text, conditions, softkey designations, screen titles, group designations • Movement screens: Power-up text and functions, softkey designations, screen titles, group designations • User screens: softkey designations, screen titles, group designations • Parallel status messages • Serial user messages • Cascade synchronization definitions • Screen assignments: Matrix for movement and user screens 6-18 MMI-MADAP Operator Terminal Alarm files • Definition: The purpose of an alarm is to alert the user to unusual statuses occurring throughout the processing routines. This facilitates the initiation of required remedial procedures. The following alarm files have been defined: Range 1 - 10 11-20 21-30 31-40 41-50 Filename, *.ALR ALARM001 - ALARM010 ALARM011 - ALARM020 ALARM021 - ALARM030 ALARM031 - ALARM040 ALARM041 - ALARM050 Utilizer BOSCH Development Project / 1st user Project / 2nd user Project / 3rd user )LJ/LVWRI'HILQHG$ODUP)LOHV Alarm files 11 through 50 are reserved for the user. Math files • Definition: The purpose of mathematics is the utilization of formulas and functions of the MMI-MADAP software. The following math files have been defined: 5DQJH 1 - 100 101-150 151-200 201-250 251-300 )LOHQDPH0$7 MATH001 - MATH0100 MATH101 - MATH150 MATH151 - MATH200 MATH201 - MATH250 MATH251 - MATH300 8WLOL]HU BOSCH Development Project / 1st user Project / 2nd user Project / 3rd user )LJ/LVWRI'HILQHG0DWK)LOHV The mathematics files 101 through 300 are reserved for the user. 1070 072 168-101 (98.04) GB MMI-MADAP Operator Terminal 6-19 Scheduler files • Definition: The purpose of the scheduler is the initiation of functions in dependency of time intervals, date and calendar functions, and also in the case of value changes of specified variables. The following scheduler files have been defined: 5DQJH 1 2 3 4 5 )LOHQDPH6&+ SCHED001 SCHED002 SCHED003 SCHED004 SCHED005 8WLOL]HU BOSCH Development Project / 1st user Project / 2nd user Project / 3rd user )LJ/LVWRI'HILQHG6FKHGXOHU)LOHV The scheduler files 3 through 5 are reserved for the user. Trend files • Definition: The purpose of the trend files is the generation of online trends and historical trends. The objective of a graphical trend representation is to inform the user about the development of a given process by plotting the values of variables on a curve. The following trend files have been defined: 5DQJH 1 - 50 51-70 71-90 91-110 111-130 )LOHQDPH75' TREND001 - TREND050 TREND051 - TREND070 TREND071 - TREND090 TREND091 - TREND110 TREND111 - TREND130 8WLOL]HU BOSCH Development Project / 1st user Project / 2nd user Project / 3rd user )LJ/LVWRI'HILQHG7UHQG)LOHV The trend files 50 through 130 are reserved for the user. 1070 072 168-101 (98.04) GB 6-20 MMI-MADAP Operator Terminal Report files • Definition: Creating of user-defined reports that can be written to the hard disk or output to a connected printer. The following report files must be defined: 5DQJH )LOHQDPH5(3 ABCDEFGH.REP ABCDEFGH.REP ABCDEFGH.REP ABCDEFGH.REP ABCDEFGH.REP 8WLOL]HU BOSCH Development Project / 1st user Project / 2nd user Project / 3rd user )LJ/LVWRI8VHU'HILQHG5HSRUW)LOHV Each user can use filenames of his choice. The filename extension will always the .REP. In order to prevent dual filename assignments, the users named DEVELOPMENT and PROJECT must precede the filename by an additional identifier. For example: PR1xxx.REP Recipe files • Definition: Exchange of values between the central database and the files located on the hard disk. The following recipe files must be defined: 5DQJH )LOHQDPH5&3 ABCDEFGH.RCP ABCDEFGH.RCP ABCDEFGH.RCP ABCDEFGH.RCP ABCDEFGH.RCP 8WLOL]HU BOSCH Development Project / 1st user Project / 2nd user Project / 3rd user )LJ/LVWRI8VHU'HILQHG5HFLSH)LOHV Each user can assign filenames of his choice. The filename extension will always the .REP. In order to prevent dual filename assignments, the users named DEVELOPMENT and PROJECT must precede the filename by an additional identifier. For example: PR1xxx.RCP 1070 072 168-101 (98.04) GB MMI-MADAP Operator Terminal 6-21 6.6 Online Project Design of Standard Functions The MMI-MADAP user-specific project design function is divided into two areas: • 2QOLQHSURMHFWGHVLJQ (refer also to chapter on online data) and • 8VHUVFUHHQGHVLJQ e.g. System overviews, production data management F The subject of online project design is discussed in detail in the documentation entitled "MMI-MADAP for System or Machine Operators." F The steps involved in designing and configuring user screens are described in detail in the following section. 1070 072 168-101 (98.04) GB 6-22 MMI-MADAP Operator Terminal 6.7 Designing User Screens User screens can be used to indicate system statuses and conditions, and to display them on the MMI-MADAP operator terminal. This section will address the principles of displaying PLC information via user screens. F The design and creation of user screens will require the use of the development software. For detailed information on this subject, please refer to the documentation supplied with the development software. To provide an example, a simple system overview will be designed here. The objective is the graphical representation of all cascade operating modes by means of a colour change, and to display the system status and the produced quantity (part/piece count). )LJ([DPSOHRI6<67(029(59,(:8VHU6FUHHQ 1070 072 168-101 (98.04) GB MMI-MADAP Operator Terminal 6-23 Basic procedure In the design of user screens, the following steps are required: • Activating user level • Opening user screen • Declaring variables • Creating graphical objects • Defining configuration sheet • Testing user screen Activating user level A specific user level is required in order to create user screens. Please activate the required user level. F Please contact the system administrator to obtain the available user names and passwords. In the Windows Program Manager, select the MMI-MADAP directory. Start the Log On/Off software module by double-clicking the Log On/Off icon (shown below). In the Log On dialog box, type the username and password, then select OK to close the application. )LJ([DPSOHRI8VHU/HYHO$FWLYDWLRQ 1070 072 168-101 (98.04) GB 6-24 MMI-MADAP Operator Terminal Opening user screen User screens are composed of two files, i.e., the file providing the background image (ANWXX.SCR), and the file for the user application (APPLXX.SCR). A total of 64 user screens are available. F The default background images are fully configured, and should not be modified by the user. In addition, the user may avail himself of the base screen (filename GRUNDANW.SCR). This screen is called from within the GRUND:SCR screen. In the Windows Program Manager, select the MMI-MADAP directory. Start the Application Builder software module by double-clicking the Application Builder icon (shown below). In the Application Builder, select the Open menu command to open the APPLXX.SCR for creating your applications. (1 < xx < 64.). Declaring variables As a first step, all variables required for the intended application should be declared: In the Application Builder, select the Tools menu command to start the Database Manager. For our system overview we require two variables of the Array Integer16 type. The required variables are defined as follows: • $QODJH (system) for recording and reading PLC statuses, and • $QZ%LOGBDNWLY (User screen1 active) for enabling the read cycle from within the PLC. 1070 072 168-101 (98.04) GB MMI-MADAP Operator Terminal 6-25 )LJ([DPSOHRI'HFODUDWLRQRI9DULDEOHV The AnwBild1_aktiv variable is now assigned a function that will serve to activate the read cycle. In this example, the read cycle on the PLC is to occur cyclically after the user screen has been selected. )LJ([DPSOHRI0DWK6KHHW$VVLJQPHQW 1070 072 168-101 (98.04) GB 6-26 MMI-MADAP Operator Terminal The function assignment is handled in the form of a program sequence in a math sheet. By default, all math sheets are available. The first available user math sheet has the number 150. The Bild_Nr variable used in this example comprises a global Bosch variable. The variable returns the value of the current MMI-MADAP screen. The first user screen has the number 311. F Only in the event that the math sheet contains a value greater than zero in the Execution line, will all math formulae in this configuration sheet be executed. Having applied all variables, close the Database Manager, and return to the Application Builder. Creating graphical objects Once the variable have been declared, the required objects will be created in the application screen, and the variables will be integrated. )LJ([DPSOHRI$SSOLFDWLRQLQ$SSOLFDWLRQ%XLOGHU 1070 072 168-101 (98.04) GB MMI-MADAP Operator Terminal 6-27 Subsequent to defining all objects, the screen should be tested with the use of the Execute (running the application) and Database Spy (assigning variables) menu commands. The procedure is concluded by saving the application, and by terminating the Application Builder. Defining configuration sheet In order to read data from the PLC controller, a Read instruction must be executed via the PROFIBUS-FMS. Read and Write instructions are defined via configuration sheets in the UniSoft Configurator software module. In the Windows Program Manager, select the MMI-MADAP directory. Start the MMI-MADAP PROFIBUS Configurator software module by double-clicking the MMIMADAP Profibus Configuration icon (shown below). In the Configurator, select Open to open a user configuration sheet, or create a new one. )LJ6DPSOH/LVWRI8VHU&RQILJXUDWLRQ6KHHWV In this example, the AnwBild1_aktiv[1] variable is used for the purpose of transfer control. The data is read, beginning with the first data word in the object bearing index number 30. 1070 072 168-101 (98.04) GB 6-28 MMI-MADAP Operator Terminal The data from the PLC controller is saved to the variables named Anlage[1] through Anlage[14]. )LJ([DPSOHRI&RQILJXUDWLRQ6KHHWLQ&RQILJXUDWRU Once the configuration sheet has been configured, it is saved, and the application is terminated. Testing user screen To test your user screen, you will be required to start the MMI-MADAP software, and open your user screen via screen displays. In the Windows Program Manager, select the MMI-MADAP directory. Start the MMI-MADAP software module by double-clicking the MMIMADAP icon (shown below). Continue by selecting the Display button to select the desired user screen. 1070 072 168-101 (98.04) GB MMI-MADAP Operator Terminal 6-29 6.8 MMI-MADAP Merge Function The Merge function facilitates the merging of different applications into a single application.. In this process, four functional units must be considered: F • Application database • Screens • Definitions • Data range definitions (components) In order to work with the Merge function, all other MMI-MADAP modules, such as BGTask, Viewer, etc., must be closed. 6.8.1 Application database The MMI-MADAP software functions are based upon a single database. This database is named TAGL.TXT, and is located in the C:\MMIMADAP\DATABASE directory. Each user creates a new application with the Application Manager. Example: Start the Application Manager. )LJ$SSOLFDWLRQ0DQDJHU,FRQ Select the Create a New Application button. )LJ&UHDWH1HZ$SSOLFDWLRQ%XWWRQ Create a new application which you will name "Anwender" (user). This will create a new directory named C:\Anwender. 1070 072 168-101 (98.04) GB 6-30 MMI-MADAP Operator Terminal )LJ1HZ$SSOLFDWLRQ'LDORJ%R[ In this new application, in the subdirectory named C:\ANWENDER\DATABASE, there is an empty database named TAGL.TXT. F In an MMI-MADAP database, variables may be defined with a unique name only. In order to prevent the merging of applications containing variables with identical names, each user must assign a unique identifier to his variables at the time he creates his application. Example: User in Company A: All names of variables begin with CA_, e.g. CA_variable1, CA_variable2, etc. User in Company B: All names of variables begin with CB_ e.g. CB_variable1, CB_variable2, etc. With the variables thus uniquely identified, the automatic generation of a single database by defining the pathnames for the two source databases is possible. The current project must always be MMI-MADAP (1st database). Select this project with the use of the Project Manager. )LJ6HOHFWLQJDQ$SSOLFDWLRQ Go to the Windows Program Manager, and start the DBMERGE.EXE program. 1070 072 168-101 (98.04) GB MMI-MADAP Operator Terminal 6-31 )LJ'DWDEDVH0HUJH8WLOLW\,FRQ This takes you to the selection of the 2nd database. )LJ6HOHFWLQJQG'DWDEDVH In the File Name text box, type the complete pathname and filename. At this point you can click Open... for quick access to the database. )LJ2SHQLQJ7$*/7;7'DWDEDVH Selecting Merge will cause the contents of the 2nd database to be added to those of the 1st database. )LJ'DWDEDVH0HUJH'LDORJ%R[ 1070 072 168-101 (98.04) GB 6-32 MMI-MADAP Operator Terminal Example of Merge function: 1st Database: C:\MMIMADAP\DATABASE\TAGL.TXT 2nd Database: C:\ANWENDER\DATABASE\TAGL.TXT Result: C:\MMIMADAP\DATABASE\TAGL.TXT Through consistent repetition of this procedure, any number of databases can be merged into a single database. F Mixing variables of the CLASS type is not possible. 6.8.2 Screens In the course of project design with the MMI-MADAP software, the project designer creates his own user screens. These screens must then be added to the default screen repertoire of the MMI-MADAP software. 6.8.2.1 Procedure for creating user screens • Number of user screens Up to 64 user screens can be designed with the use of the development editor for the MMI-MADAP software packet. The predefined user screens are located in the directory named: C:\MMIMADAP\SCREEN • User screen structure Each user screen consists of two partial images. ANW1 background image This image contains the screen title, the softkey rows, all key functions (screen change, etc.), and is used to call the foreground screens named APPL1 through APPL64. F The user is unable to change the background image. APPL1 through APPL64 foreground images These images are used to design the functions for the user screens, such as bar graphs, value entry text boxes, overview screens, etc. Once created, all screens can be copied for further processing into other projects at any time. This means that they will also function in the runtime version of the program. • Screen creation procedure In the Windows Program Manager, select UNISOFT. Open the Application Manager. Use the Select an Application command to select the MMIMADAP.APP file in the C:\MMIMADAP project directory. Start the Application Builder. 1070 072 168-101 (98.04) GB MMI-MADAP Operator Terminal 6-33 Select and edit user screen foreground images named APPL1 through APPL64. Enter the required variables in the existing database. Proceed with the creation of your user screens. 6.8.2.2 Definitions The MMI-MADAP software facilitates the online creation of new definitions, such as movement text, power-up criteria, etc. The respective definitions re stored in the C:\MMIMADAP directory in the form of *.DAT files. These files can be modified as desired, and also copied into new projects. The copying process can be automated by means of batch files. Another option is the use of the Copy command in the PROJEKT window of the MMI-MADAP user interface. 6.8.3 Defining Data Ranges 6.8.3.1 Introduction The MMI-MADAP standard software packet defines the various data ranges: The term data ranges encompasses the following components: F 1070 072 168-101 (98.04) GB • Alarms (Alarm files) • Math worksheets (Math files) • Time-controlled processing (Scheduler files) • Trend values (Trend files) • Report outputs (Report files) • Data management (Recipe files) With the exception of the online data, all components are saved as data files. They are located in the directory named C:\MMIMADAP\CONFIG. All files can be freely copied. 6-34 MMI-MADAP Operator Terminal 6.8.3.2 Alarm files 5DQJH 1 - 10 11-20 21-30 31-40 41-50 )LOHQDPH$/5 ALARM001 - ALARM010 ALARM011 - ALARM020 ALARM021 - ALARM030 ALARM031 - ALARM040 ALARM041 - ALARM050 8WLOL]HU BOSCH Development Project / 1st user Project / 2nd user Project / 3rd user )LOHQDPH0$7 MATH001 - MATH0100 MATH101 - MATH150 MATH151 - MATH200 MATH201 - MATH250 MATH251 - MATH300 8WLOL]HU BOSCH Development Project / 1st user Project / 2nd user Project / 3rd user )LOHQDPH6&+ SCHED001 SCHED002 SCHED003 SCHED004 SCHED005 8WLOL]HU BOSCH Development Project / 1st user Project / 2nd user Project / 3rd user )LOHQDPH75' TREND001 - TREND050 TREND051 - TREND070 TREND071 - TREND090 TREND091 - TREND110 TREND111 - TREND130 8WLOL]HU BOSCH Development Project / 1st user Project / 2nd user Project / 3rd user )LOHQDPH5(3 ABCDEFGH.REP ABCDEFGH.REP ABCDEFGH.REP ABCDEFGH.REP ABCDEFGH.REP 8WLOL]HU BOSCH Development Project / 1st user Project / 2nd user Project / 3rd user 6.8.3.3 Math files 5DQJH 1 - 100 101-150 151-200 201-250 251-300 6.8.3.4 Scheduler files 5DQJH 1 2 3 4 5 6.8.3.5 Trend files 5DQJH 1 - 50 51-70 70-90 91-110 111-130 6.8.3.6 Report files 5DQJH Each user can assign filenames of his choice. The filename extension will always the .REP. In order to prevent dual filename assignments, the users named DEVELOPMENT and PROJECT must precede the filename by an additional identifier. For example: DEVELOPMENT: PROJECT: FA_001, CA_002, etc. FB_001, FB_002, etc. 1070 072 168-101 (98.04) GB MMI-MADAP Operator Terminal 6-35 6.8.3.7 Recipe files 5DQJH )LOHQDPH5&3 ABCDEFGH.RCP ABCDEFGH.RCP ABCDEFGH.RCP ABCDEFGH.RCP ABCDEFGH.RCP 8WLOL]HU BOSCH Development Project / 1st user Project / 2nd user Project / 3rd user Each user can assign filenames of his choice. The filename extension will always the .REP. In order to prevent dual filename assignments, the users named DEVELOPMENT and PROJECT must precede the filename by an additional identifier. For example: DEVELOPMENT: PROJECT: FA_001, CA_002, etc. FB_001, FB_002, etc. 6.8.4 Communications With regard to standardization, the structure of PROFIBUS communications encompasses two partial areas: • MMI-MADAP forms • Communication files Each operator terminal featuring executable MMI-MADAP software requires communication forms. The forms are provided in file form in the C:\MMIMADAP\CONFIG directory. This makes them accessible to any operator terminal with the same name. Possible forms are listed below: • BUEP19E, serial communications • SFMS (Softing), PROFIBUS-FMS communications • SL2A2 (Siemens), PROFIBUS-FMS communications 5DQJH 1 - 100 101-150 151-200 201-250 251-300 1070 072 168-101 (98.04) GB )LOHQDPH'59 *001 - *050 *051 - *070 *071 - *090 *091 - *110 *111 - *130 8WLOL]HU BOSCH Development Project / 1st user Project / 2nd user Project / 3rd user 6-36 MMI-MADAP Operator Terminal 6.8.5 Modifying the Application In normal circumstances the user will create his user screens on a designated development computer. This computer is equipped with the development license (Hardkey dongle). When combining individual files on other operator terminals, the proper functioning of the complete application (Bosch MMI-MADAP + user screens + user database) requires adherence to specific procedural steps. These steps are required because, due to considerations of speed, the access to variables in the individual files, such as screens, math sheets, communications drivers, is effected via internal references. these references must be modified for the entire application. • Merging all user files Modifications to the screens and configuration sheets in accordance with MMI-MADAP defaults can be effected on different development computers. A so-called 0(5*( computer is used to merge the files created on different development computers. • MMI-MADAP development version All development computers, including the MERGE computer, must operate the latest MMI-MADAP software version. The same applies to all operator terminals that will have to process user files. At the time of this writing, this is version 1.13. • Merge procedure On the MERGE computer, the MERGE software module is used to blend the databases from other development computers with the database of the MERGE computer. All screens and configuration files must be copied into the respective directories. F Refer to preceding section. • DBVERSIO.BIN In the C:\MMIMADAP\DATABASE\DBVERSIO.BIN file, the internal references are stored in the form of a number. This number must be manipulated manually. Using ASCII notation, a number is generated in the YDDMM format, where Y: 1 = odd year, 2 = even year DD: 2 numbers represent today’s date MM: 2 numbers represent the current month. 1070 072 168-101 (98.04) GB MMI-MADAP Operator Terminal 6-37 Example: If the merge procedure is completed on 1 January, 1997, the number to be entered in the DBVERSIO.BIN file is 10108. • Database Pack Utility As the next step, the Database Pack Utility is started, followed by selecting the 3$&. command, followed by 237,0,=( (see also description earlier in this chapter). • Merging the files All user files are now compatible for use on the destination computers. • Installing user files on destination computers As a prerequisite for this procedure, the latest version of MMIMADAP software must be installed on all destination computers. At the time of this writing, this is version 1.13. Copy all user files into the respective destination directories. In the C:\MMIMADAP\CONFIG directory, delete all files with the .MAC filename extension. Restart the MMI-MADAP software. 1070 072 168-101 (98.04) GB 6-38 MMI-MADAP Operator Terminal 6.9 Screen List and Screen Numbers All screens feature a screen name and a screen number. The screens are located in file form in the directory named C:\MMIMADAP\SCREEN, and are identified by the .SCR filename extension. The screen number is transferred to the PLC where is can be used for the purpose of selecting user-specific functions. 0RGLILDEOHVFUHHQV The term modifiable screens applies to the screen masks that you are using for system-specific visualization. 6FUHHQ 311-318 321-328 331-338 341-338 351-358 361-368 371-378 381-388 6FUHHQQDPH Appl1-Appl8 Appl9-Appl16 Appl17-Appl24 Appl25-Appl32 Appl33-Appl40 App41-Appl48 Appl49-Appl56 Appl57-Appl64 'HVFULSWLRQ User screen, Group 1 / Screen 1-8 User screen, Group 2 / Screen 1-8 User screen, Group 3 / Screen 1-8 User screen, Group 4 / Screen 1-8 User screen, Group 5 / Screen 1-8 User screen, Group 6 / Screen 1-8 User screen, Group 7 / Screen 1-8 User screen, Group 8 / Screen 1-8 3HUPDQHQWVFUHHQV Permanent screens are those screen masks that contain the MMI-MADAP standard functions, and that are not accessible to the user. 6FUHHQ 1 11 21 22 31 32 110 111 112 113 114 115 116 'HVFULSWLRQ Base screen and secondary definition screens Base screen with initialization Definition, Softkey for Power-up screens Definition, Softkey for Movement screens Definition, Movement screen matrix Definition, Softkey for User screens Definition, User screen matrix Power-up conditions Definition, Power-up conditions Power-up conditions 1 Power-up conditions 2 Power-up conditions 3 Power-up conditions 4 Power-up conditions 5 Power-up conditions 6 1070 072 168-101 (98.04) GB MMI-MADAP Operator Terminal 210 210 211-218 221-228 231-238 241-248 251-258 261-268 271-278 281-288 310 411 412 421 422 431 432 433 441 442 451 452 461 462 481 482 483 611 621 622 661 681 741 711 780 781 511 513 521 522 530 531 540 541 1070 072 168-101 (98.04) GB 6-39 Movement screens Definition, Operand addresses for Movement screens Definition, Movement text and cascades/steps for movement screens Movement screen, Group 1 / Screen 1-8 Movement screen, Group 2 / Screen 1-8 Movement screen, Group 3 / Screen 1-8 Movement screen, Group 4 / Screen 1-8 Movement screen, Group 5 / Screen 1-8 Movement screen, Group 6 / Screen 1-8 Movement screen, Group 7 / Screen 1-8 Movement screen, Group 8 / Screen 1-8 User screens Definition, User screen titles Status displays Inputs Extended inputs Outputs Extended outputs Markers Special markers System range Times Counters Data field Data buffer Data modules Data module list PLC overview, internal messages I/O assignment of connected PLC System configuration of connected PLC Messages Parallel user messages Serial user messages Serial user messages, history Diagnostic record storage PLC data, stored PLC errors Error statistics, First-value errors Diagnostics Cascade diagnostics display Definition, synchronization in Automatic mode Cascade overview Machine usage Display, Machine usage trend Definition, Machine usage trend Display, current machine data Display, historic machine data Definition, Shift times Display, Shift times Definition, Cycle times Display, Cycle times 6-40 MMI-MADAP Operator Terminal 6.10 Global Standard Variables In the user screens, predefined global standard variables can be used. The following variables are available to the user: Name Description Bild_Nr Number of current screen bild Current base screen ZSNr Number of current ZS central processing unit SPS_Typ PLC type and ZS number read LOG0 Logic "0" LOG1 Logic "1" K_Anz Number of cascades BF_Nr Number of operator terminal K_Start Start address = 1st cascade of station PG_Frei_Anw PgUp/PgDn block at "1" PG_Frei_Bew PgUp/PgDn block at "1" AnwenderDef_Bild Definition screen for the user in user screens Kettdar_Frei Enable of cascade overview screen from within diagnostic screen: 1 = enable, 0 = disabled Read-access only is permitted to the listed variables! 1070 072 168-101 (98.04) GB PROFIBUS-FMS Interface 7-1 7 PROFIBUS-FMS Interface 7.1 Introduction The PROFIBUS-FMS employed in this system comprises a highperformance industrial data bus. The purpose of the PROFIBUS-FMS is the facilitation of communications between the MMI-MADAP operator terminals and the PLC controller. In order to assist the user with the use of the PROFIBUS-FMS, the following PROFIBUS-FMS configuration tasks have been predefined for the MMI-MADAP software: • Topology definition, • Creation of communication references, • Creation of communication objects, • Definition of bus parameters, The initialization of communication references and the transfer of communication objects is effected directly from the MMI-MADAP operator terminal. On the PLC side, no special functions are required for PROFIBUS-FMS communications. Freely applicable communication objects are provided for the user. F Additional BOSCH documentation Manual: PROFIBUS for Beginners No. 1070 072 140 Manual: PROFIBUS-Konfigurator No. 1070 072 066 Manual: R500P Computer Interface Module No. 1070 072 138 1070 072 168-101 (98.04) GB 7-2 PROFIBUS-FMS Interface 7.2 Communication References The transfer of communication objects is accomplished by mans of the READ, WRITE and STATUS PROFIBUS-FMS services. To enable these services to accomplish the data transfer, they require a connectionoriented communication reference. During the initialization phase of the MMI-MADAP operator terminal, the communication references are established and monitored by the PCPROFIBUS card. For each MMI-MADAP operator terminal, a communication reference is established with the R500P PLC PROFIBUS card or COM-P card. Each communication reference is assigned a unique index number on both ends. The default index number on the MMI-MADAP operator terminal end is KR2. The standardized KBL files are prepared for 8 MMI-MADAP operator terminals. Communication references R500P or COM-P MMI-MADAP BT 1 PROFIBUS card 2 3 . . 9 MMI-MADAP BT 2 MMI-MADAP BT 8 2 2 2 )LJ00,0$'$353RU&203&RPPXQLFDWLRQ5HIHUHQFHV 1070 072 168-101 (98.04) GB PROFIBUS-FMS Interface 7-3 7.3 Communication Objects A standardized PROFIBUS object configuration is provided for the MMIMADAP software. The user will not be required to create any other objects. From the viewpoint of the user, all PROFIBUS objects comprise data ranges within data modules. For each MMI-MADAP operator terminal, there are eight objects that are non-terminal specific, and nine that are operator terminal-specific. The objects are divided into three categories: • MMI-MADAP objects • User objects • Common-use MMI-MADAP / User objects Data ranges of MMI-MADAP objects are managed by the MMI-MADAP PLC software, and may not be write-accessed by the user. Data ranges of user objects are available to the user for the purpose of communicating with user screens on the MMI-MADAP operator terminal. They must be managed by the user. Data ranges of common-use MMI-MADAP / User objects can be used in conjunction with each other. The data ranges are managed by the MMIMADAP software only dependent upon the screen selected on the MMIMADAP operator terminal. The user may write-access them only while a user screen is selected on the display of the MMI-MADAP operator terminal. 1070 072 168-101 (98.04) GB 7-4 PROFIBUS-FMS Interface PROFIBUS configuration in MMI-MADAP All objects are classified via their index numbers. This means, for example, that the object with index number 20, defined as data range data word D0 through D218, is located in data module DM255. On the MMI-MADAP operator terminal side, the objects are managed in so-called configuration sheets. Each configuration sheet is stored in file form. The identifier for these files is SL2A2xxx.DRV. The time for object update/refresh action is defined in the configuration sheets. On the PLC side, the object update process is coordinated, subsequent to EP (end of program) or STOP (PLC Stop). This means that the data is being refreshed after each PLC cycle. Common-use objects for operator terminals BT 1 - 4: Index Local Addr. DM/D/No.By 20 255/000/220 21 22 23 24 25 26 27 253/000/184 253/184/184 253/368/144 254/000/220 254/220/220 250/000/220 250/220/220 Description Coordination Messages, DM list, System time, PLC statuses I/O assignment; SC table Machine usage and PROFIBUS-DP diagnostics Reserved, users for BT 1-4 EP or STOP EP or STOP EP or STOP EP or STOP EP or STOP EP or STOP EP or STOP EP or STOP )LJ352),%86±&RPPRQ8VH2EMHFWVIRU2SHUDWRU7HUPLQDOV Number of objects used: 8 The objects identified with indexes 26 and 27 represent user objects. These defined data ranges can be managed in the PLC by the user. 1070 072 168-101 (98.04) GB PROFIBUS-FMS Interface 7-5 Objects for operator terminal 1: Index 28 29 30 31 32 33 34 35 36 Local Addr. DM/D/No.By 234/000/220 234/220/220 231/000/184 231/184/184 231/368/184 230/000/118 230/118/202 230/320/192 233/000/220 Description Cascade diagnostics Link index 1, Status / User Link index 2, Status / User Link index 3, Status / User General communication and display data Reserved user object Coordination EP or STOP EP or STOP EP or STOP EP or STOP EP or STOP EP or STOP EP or STOP EP or STOP EP or STOP )LJ352),%86±2EMHFWVIRU%72SHUDWRU7HUPLQDO Number of objects used: 9 The objects with indexes 30 through 32 are common-use MMI-MADAP / User objects, and can be write-accessed by the user only if a user screen was selected on the MMI-MADAP operator terminal. The object with index 36 is a user object. This defined data range can be managed in the PLC by the user. Objects for operator terminal 2: Index 37 38 39 40 41 42 43 44 45 Local Addr. DB/D/No.By 239/000/220 239/220/220 236/000/184 236/184/184 236/368/184 235/000/118 235/118/202 235/320/192 238/000/220 Description Cascade diagnostics Link index 1, Status / User Link index 2, Status / User Link index 3, Status / User General communication and display data Reserved user object Coordination EP or STOP EP or STOP EP or STOP EP or STOP EP or STOP EP or STOP EP or STOP EP or STOP EP or STOP )LJ352),%86±2EMHFWVIRU%72SHUDWRU7HUPLQDO Number of objects used: 9 The objects with indexes 39 through 41 represent common-use MMIMADAP / User objects, and can be write-accessed by the user only if a user screen was selected on the MMI-MADAP operator terminal. The object with index 45 is a user object. This defined data range can be managed in the PLC by the user. 1070 072 168-101 (98.04) GB 7-6 PROFIBUS-FMS Interface Objects for operator terminal 3: Index 46 47 48 49 50 51 52 53 54 Local Addr. DM/D/No.By 244/000/220 244/220/220 241/000/184 241/184/184 241/368/184 240/000/118 240/118/202 240/320/192 243/000/220 Description Coordination Cascade diagnostics Link index 1, Status / User Link index 2, Status / User Link index 3, Status / User General communication and display data Reserved user object EP or STOP EP or STOP EP or STOP EP or STOP EP or STOP EP or STOP EP or STOP EP or STOP EP or STOP )LJ352),%86±2EMHFWVIRU%72SHUDWRU7HUPLQDO Number of objects used: 9 The objects with indexes 48 through 50 represent common-use MMIMADAP / User objects, and can be write-accessed by the user only if a user screen was selected on the MMI-MADAP operator terminal. The object with index 54 is a user object. This defined data range can be managed in the PLC by the user. Objects for operator terminal 4: Index 55 56 57 58 59 60 61 62 63 Local Addr. DM/D/No.By 249/000/220 249/220/220 246/000/184 246/184/184 246/368/184 245/000/118 245/118/202 245/320/192 248/000/220 Description Coordination Cascade diagnostics Link index 1, Status / User Link index 2, Status / User Link index 3, Status / User General communication and display data Reserved user object EP or STOP EP or STOP EP or STOP EP or STOP EP or STOP EP or STOP EP or STOP EP or STOP EP or STOP )LJ352),%86±2EMHFWVIRU%72SHUDWRU7HUPLQDO Number of objects used: 9 The objects with indexes 57 through 59 represent common-use MMIMADAP / User objects, and can be write-accessed by the user only if a user screen was selected on the MMI-MADAP operator terminal. The object with index 63 is a user object. This defined data range can be managed in the PLC by the user. 1070 072 168-101 (98.04) GB PROFIBUS-FMS Interface Objects for extended diagnostics (effective only in conjunction with Com-P PROFIBUS card): Index Local Addr. Description DM/D/AnzBy Cascade diagnostics for station 64 222/000/143 5-8 65 223/000/143 66 224/000/143 67 225/000/143 7-7 Coordination EP or STOP EP or STOP EP or STOP EP or STOP )LJ352),%86±2EMHFWVIRU([WHQGHG'LDJQRVWLFV Table of objects required on R500P or COM-P (with extended diagnostics): Number of objects No. of ZS Basic unit per terminal 1 BT 2 BT 1 8 9 17 26 R500P 2 8 9 34 52 3 8 9 51 78 4 8 9 68 104 Com-P 4 12 9 3 BT 35 70 105 140 4 BT 44 88 132 176 192 )LJ352),%86±1XPEHURI2EMHFWVIRU53RU&203 F The total number of objects to be managed is limited to 100 with the use of the PLC R500P PROFIBUS card, and to 200 with the use of the Com-P. Useful and practical combinations per each R500P PLC PROFIBUS card ZS0 ZS1 ZS2 ZS3 Number of MMI 3 3 2 0 Number of MMI 4 3 1 0 Number of MMI 4 4 0 0 Object total 96 96 88 )LJ3UDFWLFDO00,&RPELQDWLRQVSHU=6&HQWUDO3URFHVVLQJ8QLW 1070 072 168-101 (98.04) GB 7-8 PROFIBUS-FMS Interface 7.4 Manipulating User Objects User objects represent defined data objects within the PLC. The data ranges can be read and write-accessed be the MMI-MADAP operator terminal. For the purpose of transferring user data between PLC and MMI-MADAP operator terminal, a transfer control mechanism must be programmed on the MMI-MADAP terminal side. This is accomplished with the use of defined variables. On the MMI-MADAP operator terminal side, a differentiation is made between the following: • Control variables (transmission control) and • FMS variable (transmission data). The user can integrate the variables in a user screen. This provides to option to effect both data control and data management in a single user screen. All user objects are preconfigured in existing configuration sheets. The generation of variables is accomplished by means of the UNISOFT Application Builder module. The definition of control and extension of configuration sheets is handled with the assistance of the UNISOFT Configurator module. F Both the Application Builder and the Configurator are standard components of the development software. F Documentation reference: Manual: Development Module, Chapter "Application Builder" Manual: Development Module, Chapter "Driver Configuration" 1070 072 168-101 (98.04) GB PROFIBUS-FMS Interface 7-9 Assigning variables In the Windows Program Manager, select the MMI-MADAP directory. Start the Configurator software by double-clicking the MMIMADAP Configuration icon (shown below). In the Configurator, select the OPEN menu command. Select a communication object from the list display of configuration sheets, and select OK. )LJ6DPSOH/LVWRI&XUUHQW&RPPXQLFDWLRQ6KHHWV 1070 072 168-101 (98.04) GB 7-10 PROFIBUS-FMS Interface This opens the selected configuration sheet in which you can define the desired variables. )LJ352),%86)06±([DPSOHRI&RQILJXUDWLRQ6KHHW Variables in display: • SK_READ[0] Control variable • FMS variable, type Unsigned 16, object index 31; EA_SK[0], data word 1 through EA_SK[91], data word 92 Proceed by assigning the defined control and FMS variables to the configuration sheet. Once you have concluded your entries, save and close the configuration sheet, and terminate the Configurator utility program by selecting the Close menu command. 1070 072 168-101 (98.04) GB PROFIBUS-FMS Interface 7-11 Configuration sheet description • 5HDG7ULJJHU This variable used to trigger a Read cycle. Each time this variable changes its value, a cycle is executed, and the listed variables are updated. • (QDEOH5HDG:KHQ,GOH If the variable entered here is larger than 0, a continuous Read cycle is executed while the driver is idle. • 5HDG&RPSOHWH The variable in this field is incremented when the Read cycle is concluded. • 5HDG6WDWXV The variable contained in this field receives an error code from the cycle. • :ULWH7ULJJHU This variable triggers a Write cycle. Each time this variable changes its value, a cycle is executed, and the listed variables are transferred to the PLC. • (QDEOH:ULWHRQ9DULDEOH&KDQJH If the value of the variable entered here exceeds 0, the driver module keeps checking whether a variable in the specified list has changed its value. If this is the case, a Write cycle is triggered, and all changed variables are transferred to the PLC. • :ULWH&RPSOHWH The variable in this field is incremented when the Write cycle is concluded. • :ULWH6WDWXV The variable contained in this field receives an error code from the cycle. 1070 072 168-101 (98.04) GB 7-12 PROFIBUS-FMS Interface 1070 072 168-101 (98.04) GB BUEP19E Interface 8-1 8 BUEP19E Interface 8.1 Introduction The Bosch BUEP19E transmission protocol employed in this system establishes a point-to-point connection between the PLC controller and the MMI-MADAP operator terminal. F Additional BOSCH documentation Manual: R500 Computer Interface Module No. 1070 072 131 8.2 Communication Objects For use of the BUEP19E protocol in conjunction with the MMI-MADAP software, a standardized object configuration is provided. From the viewpoint of the user, all BUEP19E objects comprise data ranges within data modules. For each MMI-MADAP operator terminal, there are eight objects that are non-terminal specific, and nine that are operator terminal-specific. The objects are divided into three categories: • MMI-MADAP objects • User objects (user-defined) • Common-use MMI-MADAP / User objects Data ranges of MMI-MADAP objects are managed by the MMI-MADAP PLC software, and may not be write-accessed by the user. Data ranges of user objects are available to the user for the purpose of communicating with user screens on the MMI-MADAP operator terminal. They must be managed by the user. Data ranges of common-use MMI-MADAP / User objects can be used in conjunction with each other. The data ranges are managed by the MMIMADAP software only dependent upon the screen selected on the MMIMADAP operator terminal. The user may write-access them only while a user screen is selected on the display of the MMI-MADAP operator terminal. 1070 072 168-101 (98.04) GB 8-2 BUEP19E Interface BUEP19E configuration in MMI-MADAP All objects are defined as data ranges contained within data modules. On the MMI-MADAP operator terminal side, the objects are managed in so-called configuration sheets. Each configuration sheet is stored in file form. The identifier for these files is BUEPxxx.DRV. The time for object update/refresh action is defined in the configuration sheets. On the PLC side, the object update process is coordinated, subsequent to EP (end of program) or STOP (PLC Stop). This means that the data is being refreshed after each PLC cycle. Common-use objects for operator terminals 1 - 4: Local Addr. DM/D/No.By 255/000/220 253/000/184 253/184/184 253/368/144 254/000/220 254/220/220 250/000/220 250/220/220 Description Coordination Messages, DM list, System time, PLC statuses I/O assignment; SC table Machine usage and diagnostics Reserved, users for BT 1-4 EP or STOP EP or STOP EP or STOP EP or STOP EP or STOP EP or STOP EP or STOP EP or STOP )LJ%8(3(±&RPPRQ8VH2EMHFWVIRU2SHUDWRU7HUPLQDOV Number of objects used: 8 The objects in data module 250 represent user objects. These defined data ranges can be managed in the PLC by the user. 1070 072 168-101 (98.04) GB BUEP19E Interface 8-3 Objects for operator terminal 1: Local Addr. DM/D/No.By 234/000/220 234/220/220 231/000/184 231/184/184 231/368/184 230/000/118 230/118/202 230/320/192 233/000/220 Description Cascade diagnostics Link index 1, Status / User Link index 2, Status / User Link index 3, Status / User General communication and display data Reserved user object Coordination EP or STOP EP or STOP EP or STOP EP or STOP EP or STOP EP or STOP EP or STOP EP or STOP EP or STOP )LJ%8(3(±2EMHFWVIRU%72SHUDWRU7HUPLQDO Number of objects used: 9 The objects in data module 230 represent common-use MMI-MADAP / User objects, and can be write-accessed by the user only if a user screen was selected on the MMI-MADAP operator terminal. The object in data module 230 is a user object. This defined data range can be managed in the PLC by the user. Objects for operator terminal 2: Local Addr. DM/D/No.By 239/000/220 239/220/220 236/000/184 236/184/184 236/368/184 235/000/118 235/118/202 235/320/192 238/000/220 Description Cascade diagnostics Link index 1, Status / User Link index 2, Status / User Link index 3, Status / User General communication and display data Reserved user object Coordination EP or STOP EP or STOP EP or STOP EP or STOP EP or STOP EP or STOP EP or STOP EP or STOP EP or STOP )LJ%8(3(±2EMHFWVIRU%72SHUDWRU7HUPLQDO Number of objects used: 9 The objects in data module 236 represent common-use MMI-MADAP / User objects, and can be write-accessed by the user only if a user screen was selected on the MMI-MADAP operator terminal. The object in data module 238 is a user object. This defined data range can be managed in the PLC by the user. 1070 072 168-101 (98.04) GB 8-4 BUEP19E Interface Objects for operator terminal 3: Local Addr. DM/D/No.By 244/000/220 244/220/220 241/000/184 241/184/184 241/368/184 240/000/118 240/118/202 240/320/192 243/000/220 Description Coordination Cascade diagnostics Link index 1, Status / User Link index 2, Status / User Link index 3, Status / User General communication and display data Reserved user object EP or STOP EP or STOP EP or STOP EP or STOP EP or STOP EP or STOP EP or STOP EP or STOP EP or STOP )LJ%8(3(±2EMHFWVIRU%72SHUDWRU7HUPLQDO Number of objects used: 9 The objects in data module 241 represent common-use MMI-MADAP / User objects, and can be write-accessed by the user only if a user screen was selected on the MMI-MADAP operator terminal. The object in data module 234 is a user object. This defined data range can be managed in the PLC by the user. Objects for operator terminal 4: Local Addr. DM/D/No.By 249/000/220 249/220/220 246/000/184 246/184/184 246/368/184 245/000/118 245/118/202 245/320/192 248/000/220 Description Coordination Cascade diagnostics Link index 1, Status / User Link index 2, Status / User Link index 3, Status / User General communication and display data Reserved user object EP or STOP EP or STOP EP or STOP EP or STOP EP or STOP EP or STOP EP or STOP EP or STOP EP or STOP )LJ%8(3(±2EMHFWVIRU%72SHUDWRU7HUPLQDO Number of objects used: 9 The objects in data module 246 represent common-use MMI-MADAP / User objects, and can be write-accessed by the user only if a user screen was selected on the MMI-MADAP operator terminal. The object in data module 248 is a user object. This defined data range can be managed in the PLC by the user. 1070 072 168-101 (98.04) GB BUEP19E Interface 8-5 Objects for extended diagnostics: Local Addr. DM/D/No.By 222/000/143 223/000/143 224/000/143 225/000/143 Description Cascade diagnostics for station 5-8 Coordination EP or STOP EP or STOP EP or STOP EP or STOP )LJ%8(3(±2EMHFWVIRU([WHQGHG'LDJQRVWLFV 8.3 Manipulating User Objects User objects represent defined data objects within the PLC. The data ranges can be read and write-accessed be the MMI-MADAP operator terminal. For the purpose of transferring user data between PLC and MMI-MADAP operator terminal, a transfer control mechanism must be programmed on the MMI-MADAP terminal side. This is accomplished with the use of defined variables. On the MMI-MADAP operator terminal side, a differentiation is made between the following: • Control variables (transmission control) and • BUEP19E variable (transmission data). The user can integrate the variables in a user screen. This provides to option to effect both data control and data management in a single user screen. All user objects are preconfigured in existing configuration sheets. The generation of variables is accomplished by means of the UNISOFT Application Builder module. The definition of control and extension of configuration sheets is handled with the assistance of the UNISOFT Configurator module. F Both the Application Builder and the Configurator are standard components of the development software. F Documentation reference: Manual: Development Module, Chapter "Application Builder" Manual: Development Module, Chapter "Driver Configuration" 1070 072 168-101 (98.04) GB 8-6 BUEP19E Interface Assigning variables In the Windows Program Manager, select the MMI-MADAP directory. Start the Configurator software by double-clicking the MMIMADAP Configuration icon (shown below). In the Configurator, select the OPEN menu command. Select a communication object from the list display of configuration sheets, and select OK. )LJ([DPSOHRI/LVWRI&XUUHQW&RPPXQLFDWLRQ6KHHWV 1070 072 168-101 (98.04) GB BUEP19E Interface 8-7 This opens the selected configuration sheet in which you can define the desired variables. )LJ%8(3(±([DPSOHRI&RQILJXUDWLRQ6KHHW Variables in display: • SK_READ[0] Control variable • BUEP19E variable, typ EA_SK[0], data word 1 through EA_SK[91], data word 92 of data module 253 Proceed by assigning the defined control and BUEP19E variables to the configuration sheet. Once you have concluded your entries, save and close the configuration sheet, and terminate the Configurator utility program by selecting the Close menu command. 1070 072 168-101 (98.04) GB 8-8 BUEP19E Interface Configuration sheet description • 5HDG7ULJJHU This variable used to trigger a Read cycle. Each time this variable changes its value, a cycle is executed, and the listed variables are updated. • (QDEOH5HDG:KHQ,GOH If the variable entered here is larger than 0, a continuous Read cycle is executed while the driver is idle. • 5HDG&RPSOHWH The variable in this field is incremented when the Read cycle is concluded. • 5HDG6WDWXV The variable contained in this field receives an error code from the cycle. • :ULWH7ULJJHU This variable triggers a Write cycle. Each time this variable changes its value, a cycle is executed, and the listed variables are transferred to the PLC. • (QDEOH:ULWHRQ9DULDEOH&KDQJH If the value of the variable entered here exceeds 0, the driver module keeps checking whether a variable in the specified list has changed its value. If this is the case, a Write cycle is triggered, and all changed variables are transferred to the PLC. • :ULWH&RPSOHWH The variable in this field is incremented when the Write cycle is concluded. • :ULWH6WDWXV The variable contained in this field receives an error code from the cycle. 1070 072 168-101 (98.04) GB Appendix 9 Appendix 9.1 Index A Acknowledging active messages 5-28 Activating user level 6-23 All Movements Blocked 5-17 Application Builder 7-8, 8-5 Application merging 6-29 Assigning variables 7-9, 8-6 AUTOEXEC.BAT file 6-4 Automatic diagnostics 4-70 Automatic mode 4-30 Automatic step conditions 4-40 Automatic step-on 4-28, 4-30 B Backup management 2-2 BEFA 4-34 Bestimmungsgemäßer Gebrauch 1-1 BT100 Decoding movement & function keys 4-54 BUEP driver 6-9 BUEP19E Common-use objects 8-2 Configuration in MMI-MADAP 8-2 Configuration sheet 8-8 Objects 8-1 Point-to-point connection 6-9 Transmission protocol 3-2 Bus parameters 7-1 C Cascade data module 4-24, 4-43 Cascade information 4-73 Cascade no. 4-43 Changing monitoring time 4-40 Changing wait time 4-40 CL400 Com-P card configuration 4-9 Ready-to-use configuration file 4-10 CL500 Com-P card configuration 4-9 Config table 4-13 R500P card configuration 4-9 Command output 4-38, 4-41 Command output for all steps 4-43 Command output for steps 4-43 Communication and display data 5-10 Communication Failure, system message 4-5, 4-8 Communication objects 7-1, 7-3 Communication reference 7-2 Communication references 7-1 CONFIG.SYS file 6-3 Configuring diagnostics 6-14 Configuring the operator terminal 6-9 Confirmed operating mode 4-35 Control, function unit 4-1 Council Directive relating to electrical equipment for limited voltages 1-1 Council Directive relating to electromagnetic compatibility 1-1 1070 072 168-101 (98.04) GB CPU Stopped, system message 4-5, 4-8 Creating graphical objects 6-26 Current Movements Blocked 5-17 Cycle time recording, function unit 4-2 D Data interface 4-2 Data modules Table 4-12 Database optimization 6-11 Declaring variables 6-24 Defining configuration sheet 6-27 DESI-DP communication channel 5-9 Development module 6-1 Diagnosable step-on conditions 4-65 Diagnostic information 4-69 Diagnostic results 5-19 Diagnostics 2-5, 4-68 Automatic mode 4-30 Inching mode/Single-step mode 4-28 Manual mode 4-27 Processing faults 4-38, 4-65 Semi-automatic mode 4-29 DISK.FB.MMIMADAP 4-4 Directory structure 4-6 DOS 6.22 6-2 E earthing wrist strap 1-6 EEM 1-6 Electrostatically endangered modules 1-6 Emergency-OFF-devices 1-5 Error Bus station 2-5 Cascade diagnostics 2-4 Detection & troubleshooting 2-5 Frequency distribution 2-4 Patterns 2-4 Error bits 4-43 Error codes 4-26 ESD protection 1-6 ESD work stations 1-6 F Fault marker 4-67 First-value error 4-67 First-value message 5-20 Function keys 5-14 Function modules 6-3 I I/O assignment 5-21, 5-22 Inching mode/Single-step mode 4-28 Installation diskettes 6-5 Installing MMI-MADAP 6-5 K KETTE 4-23 9-1 9-2 Appendix KETTE program module 4-21 Ketteninfos 5-20 L Lamp test 5-13 Library modules 4-4 List of data interfaces 5-2 List of data modules 5-29 M Machine cycle times 2-4, 4-51 Machine usage 2-4, 4-45, 5-24 Machine usage data 5-5 Cascade information 5-3 Cycle time recording 5-4 Machine usage recording logic 4-49 Machine usage, function unit 4-2 Manual conditions for step 4-40 Manual diagnostics 4-74, 5-20 Manual machine operation 2-3 Manual mode/Setup 4-27 Markers 4-22 measuring or testing procedures 1-5 Merge function 6-29 Message systems 2-4 Messages Coming 5-28 Messages coming/going 5-27 Messages, going 5-28 Microsoft Windows 6-23 6HH Windows MMIAUSL Program module 4-47 MMI-MADAP Alarm files 6-18 Automatic start 6-12 Data ranges, definition 6-17 Directories 6-15 Manual start 6-13 Math files 6-18 Online data 6-17 Overview of functions 2-2 Program group 6-12 Recipe files 6-20 Report files 6-20 Scheduler files 6-19 Starting the software 6-12 Trend files 6-19 Modifiable screens 6-38 Monitoring time 4-25, 4-67 Monitoring time, actual value 4-43 Movement block 5-17, 5-18 Movement keys 5-14 Movement screen 2-3 Multiple diagnostics 4-77 Multiple station assignment 4-79, 5-33 N New installation 6-5, 6-10 Number of steps 4-43 O OM18 through OM25 time-controlled processing modules 420 OM2 Definition module 4-16 OM5 and OM7 start-up modules 4-18 OM9 Error module 4-19 Open program modules 4-4 Opening user screen 6-24 Operating / Monitoring, function unit 4-1 Operating mode 4-27, 4-31, 4-43 Operating mode selection 4-24, 4-43 Operating system 6-2 Operator terminal Configuring 6-9 Configuring terminal number 6-13 Connectivity 4-59 Interface parameters 6-9 Licensing 6-13 Life marker 5-13 Number 5-13 Number of connected terminal 6-10 PROFIBUS station address 6-10 System requirements 6-2 Organization modules 4-4 Table 4-11 P Packing 6-11 Pentium 100 6-2 Permanent screens 6-38 PLC error bits 5-30 PLC errors 4-1 PLC operands 2-3 PLC status bits 5-30 Point-to-point connection 3-2 Power-up screen 2-2 Priorities, operating mode bits 4-35 Process control 4-21 Processing faults 4-75 PROFI programming software 4-3 PROFIBUS Com-P card 7-7 CONFIG.SYS changes 6-3 Configuration 6-3 Configuration in MMI-MADAP 7-4 Configuration sheet 7-11 Configurator software, starting 6-27 File installation 6-10 Modules 6-10 PROFIBOARD 6-2 R500P interface card 7-2 Standardized object configuration 7-3 Station address 6-10 PROFIBUS files Installation directory 4-10 PROFIBUS-DP Diagnostics 5-24 PROFIBUS-DP Diagnostics 4-56 PROFIBUS-FMS CP5412-A2 card 6-9 Hardware connectivity diagram 3-3 Networking 3-1 Program modules Table 4-11 Program structure 4-14 Project design, standard functions 6-21 Project handling 2-2 Protocol record 2-4 1070 072 168-101 (98.04) GB Appendix Q Qualifiziertes Personal 1-2 R Synchronization triggered externally 5-15 System messages Communication Failure 4-8 CPU Stopped 4-8 System requirements 3-2, 6-2 Rules for step programming 4-39 Runtime module 6-1 S SC table 4-7, 5-21, 5-22 SC Table 4-5, 4-13 Row number 4-18 Scratch markers 4-24 Screen name 6-38 Screen number 5-13, 6-38 Security Level 5-13 Semi-automatic mode 4-29 Sequence error 4-67 Sicherheitshinweise 1-4 Software Installation 6-3 UNISOFT Protection 6-7 Upgrade 6-5 spare parts 1-5 Standard data modules 4-5 Standard symbol file 4-5 Linking with program 4-8 Standard variables 6-40 Starting MMI-MADAP 6-12 Station assignment 4-78 Station masks 4-79, 5-33 Status display data 5-16 Status messages 5-27, 5-29 Status screen 2-3 Status utility 4-5 Step module 4-38 Number 4-24 Structure 4-40 Step number, current step 4-43 Step number, preceding step 4-43 Step number, Set Step 4-43 Step-on 4-34 Step-on condition 4-38 Substation cascade ranges 4-79, 5-33 Suitable controllers CL350 3-1 CL400 3-1 CL500 3-1 Synchronization 4-33 Synchronization step 4-43 1070 072 168-101 (98.04) GB T Testing user screen 6-28 Time on MMI-MADAP operator terminal 5-31 on PLC 5-31 Topology 7-1 Troubleshooting 2-5 Data word 4-44 U Update 6-11 User objects 8-5 User screens Designing 6-22 Purpose overview 2-2 V Version ID 5-21, 5-23 W Wait time 4-25 Wait time, actual value 4-43 Windows Application Builder, starting 6-24 Database Merge Utility 6-30 Log On/Log Off module 6-23 MMI-MADAP Configuration 7-9 MMI-MADAP directory contents 6-15 MMI-MADAP directory tree 6-15 MMI-MADAP Program Group 6-12 MMI-Panel Config utility 6-13 Registration Tool 6-13 Required platforms 3.1 or 3.11 6-2 Starting MMI-MADAP 6-28 UNISOFT Aplication Manager 6-32 WIN.INI file modification 6-12 WinSPS programming software 4-3 WSB 4-34 Z ZS number 6-10 9-3 9-2 Anhang 1070 072 168-101 (98.04) GB 1070 072 168-101 (98.04) GB • HB SP • AT/PLS • Printed in Germany
advertisement
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project