1. Process-data-communication with the MV4- Touch-Panel Info-sheet Info_2 Recipe-Handling First all Tags which are used for a recipe have to be defined and assigned to a block !!! Select Recipe-ShortCut draw a rectagle and doubble-klick on it Window “Recipe“ appears Define the name of the recipe-object e.g. „RecObj1“ Define the number of recipe-entries : e.g. “ 6 “ (means 6 different recipes in this recipe-object ) Change into tab „Recipe Tags“ and assign the different tag to this recipe OK Edit recipe-values on the PCMCIA-card with EXCEL After a download of a project to the PCMCIA-card with the download-option „Include Recipe Data“ in the subdirectory DATA a file with the extension „*.TAB“ will be generated on the card. This file can be opened and processed by EXCEL. All teh different recipe-values can be entered in EXCEL. After that the file has to be saved again on the PCMCIA-card as „TAB-File“. The MV4 now can read this recipe and it will be loaded into the MV4 aber rebooting the Touch-Panel. Note: When using recipes, a handshake between the plc and the MV4 is necessary. For that reason, the „Control- and Staus-Block“ have to be assigned to marker- addresses. In the plc-program you have to program the handshake (see next page). Page 1/2 08.03.2000 / Info_2.PPT

2. Process-data-communication with the MV4- Touch-Panel Info-sheet Info_2 Special data block types Galileo automatically generates 3 data blocks per slot (i.e. per PLC) of the following type with every project: · Control · Status · Read Time/Date These data blocks contain system variables with a wide range of functions. These blocks cannot be deleted. However, it is not necessary to assign any of these data blocks if none of them are required. Control data block The control data block and the status data block contains 8 data words (16 data bytes) with functions that are described below. The block size is reduced accordingly if the selected PLC supports a maximum of 8 data bytes per data block or even only 4. In this case the functions of the higher data words are omitted. The control data block is always polled irrespective of the mask currently displayed, and is always assigned the priority of a "fast" data block ("Polling Rate"). The individual command bits of the control data block should not be set statically since this would cause the functions to be continuously repeated (see "Initiating functions from the PLC"). The status data block is sent every second to the PLC if there is no change. When there is a change, however, the block is sent directly (event-triggered). The individual status bits are normally used for handling the control bit in the control data block (see "Initiating functions from the PLC"). Some examples of status-bits : Change Mask (Bit 12 in 1st Dataword) Number of the destination mask(2nd Dataword) Read Datablock Time/date and set MV4-Clock(Bit 10 in 1st Dataword) Send Date/Time to PLC (Bit 11 i 1st Dataword) Refresh block with Error-Texts (Bit 7 in 1st Dataword) Refresh block with Warning-Texts (Bits 6 in 1st Dataword) Refresh block with Message-Texts (Bits 5 in 1st Dataword) Reading a recipe (Bit 6 in 3rd Dataword) Changing a recipe (Bit 7 in 3rd Dataword) Reload all blocks with PLC-Text (Bit 11 in 3rd Dataword) Handshake with the PLC Page 1/2

3. Process-data-communication with the MV4- Touch-Panel Info-sheet Info_2 Initiating functions from the PLC Handshake with the PLC Page 2/2 Set Control-Bit of the Control Data in the PLC As soon as the GRS has detected the Control-Bit, this is copied to the Status-Block to the PLC As soon as the Status-Bit is detected in the PLC, the PLC has to reset the Control-Bit. As soon as the GRS has executed the function, the Stutus-Bit is reset by the GRS. Transfer to MV4 Transfer to PLC PLC MV4 PLC MV4 PLC Example of a PLC-Program for initiating a mask-change: VAR Control_MV4 AT %MW0.0.0.50 : ARRAY [ 1.. 8 ] OF WORD ; Status_MV4 AT %MW0.0.0.70 : ARRAY [ 1.. 8 ] OF WORD ; MaskNo AT %IB0.0.0.0 : BYTE ; MaskChange AT %I0.0.0.1.0 : BOOL ; END_VAR LDMask No BYTE_TO_WORD STControl_MV4 [ 2 ] LDMask Change SControl_MV4 [ 1 ]. 12 LDControl_MV4 [ 1 ]. 12 ANDStatus_MV4 [ 1 ]. 12 RControl_MV4 [ 1 ]. 12 2nd Dataword 1st Dataword Bit 12