PCS 91. CEG english. Reg 10402/0401. Version 2/04.01 Systeme Lauer GmbH & Co KG

PCS 91. CEG english Reg 10402/0401 Version 2/04.01 Systeme Lauer GmbH & Co KG

0-2 Systeme Lauer GmbH & Co KG Kelterstr.59 72669 Unterensingen Tel. (07022) 96 60-0 Fax (07022) 96 60-103

PCS 091.12 Technical appendix to manual PCS 091 DESCRIPTION OF THE LOADABLE CGLC100 DRIVER FOR THE PCS 090/095 CONTROL CONSOLE FOR COMMUNICATION WITH A CEGELEC C100 PROGRAMMABLE CONTROLLER Function: DIRECT DRIVER FOR CEGELEC PROGRAMMABLE CONTROLLER C100 Equipment and accessories required: 1. The PCS 090/095 operating console (to which parameters have already been assigned) 2. The PCS 728 connection cable to connect the PCS 090 to the programmable controller using the TTY interface 3. The parameter assignment cable PCS 733 4. This appendix (PCS 091.12) 5. Diskette PCSPRO with CGLC100 driver, version DG0901C10 or higher 6. Diskette CEGELEC with handling block In addition, the following are required (from CEGELEC): 7. A CEGELEC C100 module with CPU 5120 or the like 8. Programming software PR100 or P2.0 for programming the C100 on a PC or a programming console P1 with the appropriate plug-in module. 3 March 1993 Version 4 / 3.93 Systeme Lauer GmbH & Co KG Kelterstr.59 72669 Unterensingen Tel. (07022) 96 60-0 Fax (07022) 96 60-103 0-3

Systeme Lauer GmbH & CoKG Postfach 1465 D-72604 Nürtingen Operator reference manual: PCS 91.CEG Version: 25.04.01 Person responsible: Stefanie Weiß Operating manuals, reference manuals, and software are protected by copyright. All rights remain reserved. The copying, duplication, translation, conversion in the whole or into parts are not permitted. An exception applies to making a copy of the own use. We reserve the right make changes to the reference manual without prior notice. We can not guarantee the accuracy of the programs and data stored on the diskette and the fault-free state of this information. Since diskette represent manipulatable data media, we can only guarantee the physical completeness. The responsibility is limited to a replacement. At any time, we welcome suggestions for improvements and remarks on errors. The agreement also applies to the special appendices to this reference manual. Microsoft, MS, MS DOS, Windows, Windows 95, Windows NT and the Windows logo are either registered trademark or trademarks of the Microsoft Corporation in the USA and/or other countries. SIMATIC and STEP are registered trademarks of the Siemens AG. The remaining designations in this document can be brand names who`s use by parties for their purposes can violate the rights of the owners. 0-4 Systeme Lauer GmbH & Co KG Kelterstr.59 72669 Unterensingen Tel. (07022) 96 60-0 Fax (07022) 96 60-103

Notes for the user Please read the manual before beginning and keep the manual for later use. Target group The manual has been conceived and written for users who are experienced in the use of PCs and automation technology. Typographical conventions [KEY] Keys that are to be pressed by the user are given in square brackets, e.g [CTRL] or [DEL] Courier Courier bold On-screen messages are given in the Courier font, e.g. C:\> Keyboard input to be made by the user are given in Courier bold, e.g. C:\>DIR Italics Names of buttons to be pressed, menus or other on-screen elements and product names are given in italics. Pictograms The manual uses the following pictograms to highlight certain text passages: Danger! Possibly dangerous situation. Injury to persons can be the result. Attention! Possibly dangerous situation. Property damages can be the result. Tips and supplementary notes Systeme Lauer GmbH & Co KG Kelterstr.59 72669 Unterensingen Tel. (07022) 96 60-0 Fax (07022) 96 60-103 0-5

Table of contens Notes for the user 0-5 Table of contens 0-6 Quality and support 0-7 Safety regulations 0-8 Norms 0-9 1 First Start-Up 1-1 1.1 Delimitation...1-1 1.2 Equipment and accessories required...1-1 1.3 To load the CGLC100 Driver in the PCS 090...1-1 1.4 To connect the PCS to the programmable Controller...1-2 1.5 Error elimination...1-2 2 Programmable Controller Handling Software 2-1 2.1 Description of Communication...2-1 2.2 To load the Handling Software...2-2 2.3 Communication Errors...2-3 3 Communication 3-1 3.1 Communication Cable PSC 728:...3-1 4 Print-Out of Handling Software 4-1 0-6 Systeme Lauer GmbH & Co KG Kelterstr.59 72669 Unterensingen Tel. (07022) 96 60-0 Fax (07022) 96 60-103

Quality and support In our company, quality comes first. From the electronics component up to the finished device, the quality assurance test competently and comprehensively. National an internation test standards (ISO, TÜV, Germanischer Lloyd) are the basis. Within 48 hours, every device passes a 100% check and continuous test under worst case conditions at changing temperatures (0...50 C) and test voltages. A guarantee for maximum quality. Our products not only feature a maximum economic efficiency and reliability but also a comprehensive complete service. You not only receive demo devices but we rather make specialists available who support you in person with your first application. Qualified user consultation by competent sales engineers is obvious for us. Our support is for you for the side with advice and deed every day. We set up training programs and technical training for you in our modern training center or alternatively also in your house. Request the curent training catalog. From the consultation up to the user support, from the hotline up to the service, from the reference manual up to the training an all covering and individual service for the entire product line is waiting for you. Whenever you need us, we are there for you: dynamically, creatively and enormously efficiently. With the entire experience of a world-wide successful enterprise. Telephone 07022/9660-132, -231, -230 email support@systeme-lauer.de Web site www.lauer-systeme.net Systeme Lauer Active Area (Download of Software, driver, manuals, Forum...) Systeme Lauer GmbH & Co KG Kelterstr.59 72669 Unterensingen Tel. (07022) 96 60-0 Fax (07022) 96 60-103 0-7

Safety regulations This reference manual contains the most important remarks in order to safely operate the device. This operator s guide, particulary the safety remarks are to be noted byall persons working with the device. Furtherrmore, the rules and regulations for the accident prevention applying to the application location are to be observed. Use as directed. The device is deigned for the application in the industrial area. The device is manufactured to the state of the art and the official safeguarding regulations. Nevertheless, due to the application, dangers or impairments can result to the machine or to material assets. The device meets the requirement of the EMC guidelines and harmonized European standards. Any hardware-related modification of the system can influence the EMC behavior. The device may not be used without special protective measures in the hazardous area and in plants requiring a special monitoring. Do not heat up the buffer batteries. Danger of explosion. Serious burning can be the result. The installation and operation may only be performed by trained personnel. The operating voltage of the device may only be in the specified ranges. You find information on this on the type plate and in the specifications of this reference manual. 0-8 Systeme Lauer GmbH & Co KG Kelterstr.59 72669 Unterensingen Tel. (07022) 96 60-0 Fax (07022) 96 60-103

Norms The device is constructed using up-to-date technologies and fulfils the requirements of the following guidelines and norms: Compliant with the EMC Directive 89/336/EEC and the German law on electro-magnetic compatibility Interference compliant with the generic requirements norm EN 50081-2 and product norm EN 55022: Measurement of the conducted interference voltage as per EN 55022 Measurement of the radiated radio interference field power as per EN 55022 class A Interference immunity in compliance with generic requirements norm EN 50082-2 and product norm EN 61000-6-2: - Electro-static discharge (ESD) as per with EN 61000-4-2 - High-frequency electromagnetic fields as per EN 61000-4-3 and ENV 50204 - Fast transient interference (burst) as per EN 61000-4-4 - Surge voltages as per EN 61000-4-5 - High-frequency conducted fields as per EN 61000-4-6 - Voltage dips and short-term interruptions as per EN 61000-4- 11 The assembly and connection instructions contained in this documentation must be followed. Conformity of this equipment is confirmed by the CE logo. The EC declaration of conformity can be requested from: Systeme Lauer GmbH & Co KG P-O-Box 1465 D-72604 Nürtingen Systeme Lauer GmbH & Co KG Kelterstr.59 72669 Unterensingen Tel. (07022) 96 60-0 Fax (07022) 96 60-103 0-9

1 First Start-Up 1.1 Delimitation The successful parameter assignment of the PCS 090/095, as described in section 3 (PCS 091 manual), is assumed as a precondition. This appendix refers exclusively to the use of the PCS 090/095 together with a C100 programmable controller supplied by CEGELEC. This controller is referred to in the following as the program-mable controller. It is assumed that the user is acquainted with the CEGELEC-specific terminology and how to program the programmable controller with the software. If we refer to the PCS 090 in the following this also applies for the PCS 095. A number with an "H" at the end means hexadecimal form. The supplied example program for the programmable controller is refered to as the handling software. 1.2 Equipment and accessories required To operate a programmable controller with a PCS 090 to which parameters have already been assigned, the following products are required (Systeme Lauer): 1. The PCS 090/095 operating console itself (to which parameters have already been assigned). 2. The PCS 728 connection cable to connect the PCS 090 to the programmable controller using the TTY interface. 3. This appendix (PCS 091.12). 4. Diskette PCS PRO with CGLC100 driver, version DG0901C10 or higher. 5. Diskette CEGELEC with handling block. In addition, the following are required (CEGELEC): 6. A CEGELEC C100 module with CPU 5120 or the like. 7. Programming software PR100 or P2.0 for porgramming the C100 on a PC or a programming console P1 with the appropriate plug-in module 1.3 To load the CGLC100 Driver in the PCS 090 For the configuration of the PCS 090, both the application program with data and a selected driver are transferred. The driver is called "CGLC100.DRV", version DG0901C10 (or higher). The procedure is decribed in the PCS PRO manual. Three variables of the CGLC100 driver can be parameterised: 1) Timeout time AA, 2) Start zone AL and 3) End zone AM The timeout time AA determines the communication monitoring in the PCS. The synchronisation word (word 3) must have been processed by the programmable controller within this time. The value of AA is "number Systeme Lauer GmbH & Co KG Kelterstr.59 72669 Unterensingen Tel. (07022) 96 60-0 Fax (07022) 96 60-103 1-1

1 First Start-Up times 10 ms" and may be between 100 (= 1 second) and 1000 (= 10 seconds). The preset value is 200 (= 2 seconds). If you are using more than 5 zones the timeout time must be set higher both in the PCS and in the programmable controller. Sensible values for the timeout time are obtained using the following formula: Timeout time = number of zones used divided by 3. The minimum timeout time should always be 1.5 seconds, however. Example: 16 zones -> timeout time approx. 5 seconds. Furthermore the driver must be told the position of the data field being used. To do this the first zone used is specified in decimal form in the variable AL and the last zone used in the variable AM. If you do not alter the supplied communication software for the programmable controller, you must enter the value "19" in the driver variable AL and the value "23" in the driver variable AM (corresponds to zone (hex): 13H to 17H and is the default setting). Only if you alter all the words in the communication software with an offset can your specify a different location of the data field in the CGLC100 driver. Always move the data field as a complete block to the geginning of a zone. The values for the driver variable AL may be between 0 and 22 (= zone 0H to 16H) whilst those for AM may be between 1 and 23 (= zone 1H to 17H). A minimum of two zones must be selected, whilst a maximum of 16 zones are possible. Since the baud rate and the interface are fixed DIL 5 on the rear of the PCS 090 has a different meaning than that printed on it. DIL 5 = OFF shows error messages from the driver in French, DIL 5 = ON shows the same messages in English. DIL 6 has no meaning. 1.4 To connect the PCS to the programmable Controller 1. Switch DIL switches 8 and 9 on the rear of the PCS 090 to "OFF". 2. Connect the operating voltage (19-33 V) on the PCS 090. The ERR LED at least must now be lit. 3. Load the handling software CGLC100 into the programmable controller. 4. Connect the programming interface of the programmable controller to the PCS 090 using cable PCS 728. 5. Reset an timeout error on the programmable controller. Now the ERR LED on the PCS 090 must be extinguished. The default text 0 appears on the display of the PCS (see section 2.3) 1.5 Error elimination The following are the most common faults which occur during the first start-up: 1. DIL switch No. 8 is set to ON. If this is set the PCS goes into a diagnosis routine when it is switched on, which is only needed for testing 1-2 Systeme Lauer GmbH & Co KG Kelterstr.59 72669 Unterensingen Tel. (07022) 96 60-0 Fax (07022) 96 60-103

1 First Start-Up purposes. Remedy: Switch the DIL switch to OFF and restart the PCS (by switching off the unit briefly or pressing the RESET key above the DIL switches). 2. In the programmable controller a timeout is signalled via U 0000 = 0 and O 0175 = 1 despite the start of communication. In this case the error is in the connection between the programmable controller and the PCS 090. It is possible that the data fileds in the PCS and programmable controller are different, the cable is defect or an incorrect driver has been loaded in the PCS. If the ERR LED on the PCS is extinguished, access will be made to the data field in the programmable controller in an asynchronous manner. 3. Although the communication is started the following message appears after a short time: >>COMMUNICATION ERROR<< Possible causes for this are as follows: The connection between the programmable controller and the PCS is positioned in a location where there is too much interference, The cable is badly screened, The situation is inadequate, The programmable controller is not set to RUN The communication software in the programmable controller is not processed or is processed incorrectly or too slowly, the following appears in the 2nd line: TOO MANY REPETITIONS or timeout. Check whether the agreed data fields in the programmable controller and PCS are the same and whether the TIMEOUT times are long enough. Instructions for connection the PCS to the programmable controller Place the cable screen for the communication cable on the central earthing points of the control cabinet. Ensure good earth connections to the PCS 090 housing on the one hand and to the programmable controller board on the other. Remember that a copper earth strap offers considerably better HF conductivity than normal interconnecting wires as a result of its larger surface. Avoid the generation of high frequency interference as far as possible since they are very hard to damp. Although there is potential separation between the programmable controller and the PCS by means of optocoupler, it has no effect on rapid transients since even Systeme Lauer GmbH & Co KG Kelterstr.59 72669 Unterensingen Tel. (07022) 96 60-0 Fax (07022) 96 60-103 1-3

1 First Start-Up optocouplers have a coupling capacity (albeit a very low one). Provide clear reference points for the supply voltages. The power pack is potential free in order to make this easier. If the supply voltage carries a high level of interference you are recommended to use a separate power pack for the PCS 090 (24 V, 10 VA). It should have its own interference filter. 0 V can then be connected to the PCS using the protective conductor. The PCS 090 and the communication cable should be at least 200 mm away from interference sources. This particularly applies to inductivities and frequency converters. Ensure that the serial data cables are as fully surrounded by the screen as possible. Use a metallised plug casing which has a highly conductive connection with the cable screen both on the PCS and at the programmable controller side. Ensure that with earthing at both sides an equi-potential bonding cable is fitted with at least 10 times the screen cross section, particularly if the PCS and programmable controller are not connected to the same earthing point (if the PCS and the programmable controller, for example, are located in separate control cabinets). Reason: To prevent transient currents on the cable screen. Note: As from version 201.6 the equipment configuration of the PCS 090/095 may be queried by pressing the Help key if the ERR LED is permanently lit. By pressing Help plus the cursor keys the various driver variables and the driver itself can be displayed. 1-4 Systeme Lauer GmbH & Co KG Kelterstr.59 72669 Unterensingen Tel. (07022) 96 60-0 Fax (07022) 96 60-103

2 Programmable Controller Handling Software 2.1 Description of Communication On the diskette CEGELEC there is the communication block CGLC100 to act as the programmable controller program. This communication program occupies an average of 7 ms in each cycle for pure management work. You must add your data processing time to this time. The maximum cycle time of the programmable controller is 1000 ms. The programmable controller and PCS access an agreed data field as from word 0. The agreement is made using the driver variables AL and AM (see section 1.3). Example: AL = 19, AM = 23. This means that the data field starts at zone 13H and ends at zone 17H. Data word 0 is therefore at W304, data word 2 at W306 and data word 3 at W307. The last data word is therefore data word 79 and is at address W383. This means that the data field is 80 words long. The maximum data word address which you can use for the variable is therefore data word 79. Take this into account when you define your variables. The effective reaction speed between the programmable controller and the PCS 090 depends on the size of the data field used. The reaction speed (eg. from the time when the key on the PCS is pressed to the time when the bit is set in the programmable controller) is approx. 0.35 seconds for 5 zones plus a programmable controller cycle time. If you use more zones the reaction time will be increased correspondingly and with 16 zones (maxi-mum value) it is approx. 1.1 seconds plus one cycle time. The timeout time, in other words the time from the interruption of the communication to the error message appearing on the display of the PCS 090 depends on the size of the data field used. For 5 zones a timeout time of 1.5 seconds is sufficient, with 16 zones the timeout time in the programmable controller program should be set to 5 seconds. The timeout time variable AA for the PCs should be adapted accordingly. For example, for 5 zones this should be 150 (1.5 seconds) whilst for 16 zones it should be around 500 (5 seconds). The access to the agreed data field is synchronised between the programmable controller and the PCS. This means that either the programmable controller or the PCS can access the data field but not both at the same time. The reason for this is that the PCS reads the entire data field from the programmable controller, processes it and writes it back into the programmable controller. This means that all the data which are changed after the PCS reading cycle in the programmable controller will be overwritten by the PCS in its writing cycle. The last action of the writing cycle by the PCS is the entry of a task number into word 3. This results in word 2 and word 3 being different. This shows the programmable controller program that the data field can be processed. After processing the data field, the following program sequence must be observed: Systeme Lauer GmbH & Co KG Kelterstr.59 72669 Unterensingen Tel. (07022) 96 60-0 Fax (07022) 96 60-103 2-1

2 Programmable Controller Handling Software 1. Invert data word 3 2. Move the low byte from word 3 into the high byte 3. Copy word 3 to word 2 By inverting the task number the PCS is told that it can access the data field. The bit markers M 0000 and M 0001, input I 0400 and output O 0715 as well as timer 01 with marker U 0000 are assigned for timeout monitoring. If input I 0400 = 1 the start of communication is possible at any time after a timeout. If I 0400 = 0 the restart is not possible after a communication failure. If, instead of this input, you use a message bit, you can react to a communication failure in your programmable controller program. A communication failure is reported to you in marker bit U 0000 = 0 and output O 0715 = 1. The parallel operation of the PCS and programming unit or PC on the C100 programmable controller is not possible. Therefore you should use our program example to develop the program if at all possible. Data transfer with the controller is made in data packages. Each data package contains a check sum and its content is checked by the programmable controller operating system and by the PCS 090 for possible errors. The PCS and programmable controller communicate via the programming interface of the CPU with the following setting: 19200 baud, 8 bit, even parity, 1 stop bit. The handling software supplied by us is descibed in detail in section 4. 2.2 To load the Handling Software 1. Connect the programmable controller to the PC. 2. Call the PR100 or P2.0 software up on the PC. 3. Load the folder CGLC100. 4. Transfer the program into the programmable controller. 5. Switch the programmable controller to RUN. If you have a P1 programming console, you must enter the software shown in section 4 by hand. You can now connect up the PCS 090. The supplied program may be used as a basis for your programmable controller program. However, you should ensure that the communication program is run exactly once per cycle and the data in the data field are only processed if the programmable controller may have access (in the example: word 306 does not equal word 307). 2-2 Systeme Lauer GmbH & Co KG Kelterstr.59 72669 Unterensingen Tel. (07022) 96 60-0 Fax (07022) 96 60-103

2 Programmable Controller Handling Software 2.3 Communication Errors In the communication between the PCS 090 and the programmable controller, the PCS assumes the function of master. For this communication two criteria must be monitored - if the communication running (-> TIMEOUT, TRANSMISSION ERROR) and is the data processing running in the programmable controller (-> TOO MANY REPETITIONS). TIMEOUT / TRANSMISSION ERROR or ERREUR DE TRANSMISSION The data exchange with the programmable controller is monitored. In the event of an error, an error message will be displayed in the display of the PCS 090 and the ERROR LED will flash. In the background, however, the PCS 090 attempts to re-establish the communication. If it manages to do so the error message will be deleted. A communication failure may be caused by a cable break or a power failure on the programmable controller. High levels of interference with the data may also causes this error. ===== COMMUNICATION ERROR ===== TIMEOUT! TOO MANY REPETITIONS or TROP DE REPETITIONS When the communciation is running a task number is sent by the PCS to the programmable controller in data word 3. It is expected that the data word 3 will be processed within the timeout time. If this is not the case the communication is restarted and "TOO MANY REPETITIONS" is signalled. This message appears after a timeout on the programmable controller side if the handling software is not run any long or data word 3 is not proces-sed. ===== COMMUNICATION ERROR ===== TOO MANY REPETITIONS WRONG DATA FIELD DEFINED or MAUVAIS NUMERO DE ZONE and ACCESS TO NOT DECLARED WORD or MAUVAIS NUMERO DE MOT These message are used to monitor the data field set and may only occur in conjunction with the configuration software PCS 092. If PCS PRO is used the data field is checked before the transfer to the PCS. If these messages should appear the data field is too large, too small or a variable address is not in the agreed data field. Systeme Lauer GmbH & Co KG Kelterstr.59 72669 Unterensingen Tel. (07022) 96 60-0 Fax (07022) 96 60-103 2-3

2 Programmable Controller Handling Software 2-4 Systeme Lauer GmbH & Co KG Kelterstr.59 72669 Unterensingen Tel. (07022) 96 60-0 Fax (07022) 96 60-103

3 Communication 3.1 Communication Cable PSC 728: Connection between PCS 090 and the programmable controller via TTY SCREENING The screen should be connected on both sides to a metallised plug casing. If non-metallised plug casings are used the screen may also be connected to Pin 1; however, this is not recommended as interference may result since the data lines should be covered in full if at all possible by the screen. However, with the double-sided earthing it must be noted that in certain circumstances (as a result of earth potential shifts) an equipotential bonding cable of at least 10 times the cross section of the screen is necessary (reason: bonding currents should not pass through the cable screen if at all possible), particularly if the PCS and programmable controller are not connected to the same earth point. This is the case, for example if the PCS and programmable controller are not located in the same control cabinet. Systeme Lauer GmbH & Co KG Kelterstr.59 72669 Unterensingen Tel. (07022) 96 60-0 Fax (07022) 96 60-103 3-1

3 Communication 3.2 CONFIGURATION CABLE PCS 733 3-2 Systeme Lauer GmbH & Co KG Kelterstr.59 72669 Unterensingen Tel. (07022) 96 60-0 Fax (07022) 96 60-103

3 Communication Systeme Lauer GmbH & Co KG Kelterstr.59 72669 Unterensingen Tel. (07022) 96 60-0 Fax (07022) 96 60-103 3-3

3 Communication Structure of the write cycle PCS PLC - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Initial request ---> MS message (Give write job) <--- ACK Request text buffer <--- with message (data) <--- ACK <--- Completion ACK MB message ACK ---> 3-4 Systeme Lauer GmbH & Co KG Kelterstr.59 72669 Unterensingen Tel. (07022) 96 60-0 Fax (07022) 96 60-103

4 Print-Out of Handling Software In this section sequence 0 is printed out. This contains the initialisation, timeout monitoring and the processing for the data field including an example. For this example it is assumed the zones 13H to 17H are used as the data field. This means that data word 0 is on W302, data word 2 on W306 and data word 3 on W307. The last data word used is data word 79 at address W383. The timeout time has been set to 1.5 seconds. Breakdown of sequence 0: Lines 1, 2 Lines 4-14 Lines 16-29 Lines 31-34 Lines 35-37 Lines 39-95 trigger the initialisation in the 1st cycle. process the timeout monitoring. COFF is a program section which is run during the initialisation process or in the event of a communication failure are reserved for the initialisation process only. process the restart after a communication failure. constitute the processing of the data field including an example. Initialisation Communication failure The initialisation is run in the 1st cycle. The zones used as deleted in the COFF section, assigned prescribed values and the timeout timer is started. Therefore, if you have prescribed values other than those described you can change this in the initialisation as from line 31. The COFF program section is run through once. Further runs are prevented by marker M 0001 = 1. The PCS status must be deleted since it is no longer the current one. Furthermore the data must be prepared in such a way that the PCS is correct after a restart, for example data words 2 and 3 should be deleted and set to the same value. Add other commands to meet your requirements here. If I 0400 = 1 a check is made to find whether data word 3 has been changed by the PCS. If I 0400 = 0 the communication is blocked. Instead of I 0400 you can, of course, also use a marker which you can control from another section of the program. Timeout monitoring The timer T1 is controlled using the market M 0000. If M 0000 in line 4 = 1, the timer is reset. If, however, M 0000 = 0, the timer is running. Therefore, when a new task has arrived from the PCS, M 0000 in line 43 = 1. The status of U 0000 is placed at output O 0715. If U 0000 = 0 or O 0175 = 1, a timeout situation has occurred. In this example the timeout time is 1.5 seconds, in other words it is adequate for 5 zones. Increase the timeout value in line 05 if you are using more zones. Process data field If data word 2 and data word 3 are different (W306 not equal to W307) a new task has been sent by the PCS and the data field may be processed. At this the timeout timer is reset using M 0000 and the COFF run marker M 0001 is deleted. Now follows a section of the example from line 48. This section is only intended as a proposal and has no significance for the function of the driver, but the sequence must always be concluded with inverting and the entry of the task number form line 89. In this example it has been assumed that there is a setpoint value menu No. 1. This is called up by pressing the function key F1 and deleted again by function key F2. F3 calls up all the errors/warnings/instructions in M0 - Systeme Lauer GmbH & Co KG Kelterstr.59 72669 Unterensingen Tel. (07022) 96 60-0 Fax (07022) 96 60-103 4-1

4 Print-Out of Handling Software M15. F4 deletes these message bits. F5 calls up the operating text 6 and F2 deletes it. If you have a variable in this operating text with the address W45 you will be able to see how this is incremented by 1 between 0 and 80. The processing is terminated by inverting W307 and filing it in W306 and W307 and the PCS can read the data field. The data can now no longer be processed in the data field since otherwise the changed data may be lost. 4-2 Systeme Lauer GmbH & Co KG Kelterstr.59 72669 Unterensingen Tel. (07022) 96 60-0 Fax (07022) 96 60-103