SIEMENS SIMATIC S5 COM 525 Programming Package for the Communications Processors CP 524 and CP 525 (S5-DOS) Manual Volume 1/2 Order No. 6ES5 998-1DB21 Release 08We have checked the contents of this manual for agreement with the hardware and soltware described, Since deviations cannot be pre- cluded entirely, we cannot guarantee full agreement. However, the data in this manual are reviewed regularly and any necessary correc- tions Included In subsequent editions. Suggestions for improvement are welcomed. Technical data subject to change The reproduction, transmission or use of this document or Its con- tants Is not permitted without express written authority. Offenders will be liable for damages. All rights, including rights created & by patent grant or registration of a utility model or design, are reserved. Copyright Siemens AG 1991 All rights reserved Siemens Aktiengeselischaft 6ES5 998-10B21 Elektronikwerk- Karlsruhe Printed In the Federal Republic of GermanyContents Waming C79000-R8576-C499 Information Suggestions/Corrections Volume 1 1 2 How to Use the Manual C79000-D8576-C499-03 3 CP 525-2 Communications Processor 4 Instructions C79000-B8576-C537-07 CP 524 Communications Processor 5 Instructions C79000-B8576-C538-06 ~ 6 Computer Link with RK 512 7 Users Guide C79000-B8576-C539-08 Event Output and Listing with the PT88/PT89 Printer 8 User's Guide C79000-B8576-C541-05 10 Volume 2 6ES5 998-1DB21 Release 08SIEMENS Warnhinweis Gefahren beim Einsatz sogenannter SIMATIC-kompatibler Baugrup- pen fremder Hersteller "Den Hersteller eines Produktes (hier SIMATIC) trifft die Produktbeobach- tungspflicht, d. h. er mu generell vor Gefahren des Produktes warnen. Diese Produktbeobachtungspflicht wurde von der neueren Rechtssprechung auch auf fremde Zubehrteile erstreckt. Der Hersteller hat danach die Verpflichtung, auch solche Gefahren zu beobachten und zu erkennen, die aus der Verbindung des Produktes mit Produkten anderer Hersteller entstehen. Aus diesem AnlaB sehen wir uns verpflichtet, unsere Kunden, die SIMATIC- Produkte einsetzen, zu warnen, sogenannte SIMATIC-kompatible Baugrup- pen fremder Hersteller als Ersatz- oder Zusatzbaugruppen in das Automatisierungssystem SIMATIC einzusetzen. Unsere Produkte werden einer anspruchsvollen Qualtiatssicherung unterworfen. Uns ist nicht bekannt, ob die fremden Hersteller sogenannter SIMATIC-kompatibler Baugruppen iGberhaupt oder eine annahernd gleichwertige Qualitatssicherung durchfihren. Diese sogenannten SIMATIC-kompatiblen Baugruppen kommen nicht im Einvernehmen mit uns auf den Markt; es gibt keine Empfehlung der Siemens AG, sogenannte SIMATIC-kompatible Baugruppen fremder Hersteller ein- zusetzen. Die Werbung der framden Hersteller sogenannter SIMATIC-kompatibler Baugruppen erweckt irrtumlich den Eindruck, als sei der Inhalt der Werbung in Fachzeitschriften, Katalogen oder Ausstellungen mit uns abgesprochen. Werden sogenannte SIMATIC-kompatible Baugruppen fremder Hersteller mit unserem SIMATIC-Automatisierungssystem verbunden, handelt es sich um einen empfeh- Jungswidrigen Gebrauch unseres Produkts. Wegen der universelfen Vielfalt der Einsatzmglichkeiten unserer SIMATIC-Automatisierungssysteme und der hohen Zahl der weltweit vermarkteten Produkte, kKnnen wir die konkrete Gefahrenanalyse durch diese sogenannten SIMATIC-kompatiblen Baugruppen nicht konkret beschrei- ben. C79000-08563-C702-01 12/89Es geht Uber die tatsachlichen Mglichkeiten des Herstellers hinaus, alle diese sogenannten SIMATIC-kompatiblen Baugruppen in ihrer Wirkung auf unser SIMATIC-Produkt uberprifen zu lassen. Treten Mangel bei der Verwendung von sogenannten SIMATIC-kompatiblen Baugruppen in einem SIMATIC-Automatisie- rungssystem auf, werden wir fur solche Systeme jede Gewahrleistung ablehnen. Im Fall von Produkthaftpflichtschaden verursacht durch den Einsatz von soge- nannten SIMATIC-kompatiblen Baugruppen sind wir nicht haftbar, da wir die An- wender rechtzeitig vor den potentiellen Gefahren der Benutzung sogenannter SIMATIC-kompatibler Baugruppen gewarnt haben. 2 C79000-D8563-C702-01 12/89Warning Risks involved in the use of so-called SIMATIC-compatible modules of non-Siemens manufacture "The manufacturer of a product (SIMATIC in this case) is under the general obligation to give warning of possible risks attached to his product. This obligation has been extended in recent court rulings to include parts supplied by other vendors. Accordingly, the manufacturer is obliged to observe and recognize such hazards as may arise when a product is combined with products of other manufacture. For this reason, we feel obliged to warn our customers who use SIMATIC products not to install so-called SIMATIC-compatible modules of other manufacture in the form of replacement or add-on modules in SIMATIC systems. Our products undergo a strict quality assurance procedure. We have no knowledge as to whether outside manufacturers of so-called SIMATIC-compatible modules have any quality assurance at all or one that is nearly equivalent to ours. These so- called SIMATIC- compatible modules are not marketed in agreement with Siemens; we have never recommended the use of so-called SIMATIC-compatible modules of other manufacture. The advertising of these other manufacturers for so-called SIMATIC-compatible modules wrongly creates the impression that the subject advertised in periodicals, catalogues or at exhibitions had been agreed with us. Where so-called SIMATIC-compatible modules of non-Siemens manufacture are combined with our SIMATIC automation systems, we have a case of our product being used contrary to recommendations. Because of the variety of applications of our SIMATIC automation systems and the large number of these products marketed worldwide, we cannot give a concrete description specifically analyzing the hazards created by these so-called SIMATIC-compatible modules. 79000-D8563-C702-01 12/89It is beyond the manufacturers capabilities to have all these so-called SIMATIC- compatible modules checked for their effect on our SIMATIC products. If the use of so-called SIMATIC-compatible modules leads to defects in a SIMATIC automation system, no warranty for such systems will be given by Siemens. In the event of product liability damages due to the use of so-called SIMATIC- compatible modules, Siemens are not liable since we took timely action in warning users of the potential hazards involved in so-called SIMATIC-compatible modules." 4 C79000-08563-C702-01 12/89Avertissement Risques lis a lutilisation de modules de constructeurs tiers commer- cialiss sous la dsignation de "modules compatibles SIMATIC <Le constructeur dun produit (dans le cas prsent SIMATIC) a !obligation dobserver le produit, cest-a-dire quil est oblig, dune manire gnrale, dattirer l'attention sur les dangers inhrents au produit. Ces derniers temps, la jurisprudence a tendu cette obligation dobservation du produit aux lments accessoires issus de constructeurs tiers. En foi de quoi, le constructeur a aussi lobligation dobserver son produit pour dceler les dangers susceptibles de survenir dans le cadre de l'association de son produit avec des produits de constructeurs tiers. Pour cette raison, nous nous voyons obligs dattirer lattention de nos clients, utilisateurs de produits SIMATIC, sur les risques lis 4 l'utilisation de *modules compatibles SIMATIC de constructeurs tiers a titre de modules de remplacement ou de complment dans les produits de notre systme dautomatisation SIMATIC. Nos produits font l'objet dune assurance qualit trs pousse. Il nous est impossible de savoir si les constructeurs tiers de "modules compatibles SIMATIC mettent en ceuvre un systme qualit et, dans |affirmative, si leurs dispositions dassurance qualit permettent dobtenir le niveau de qualit requis. Les "modules compatibles SIMATIC"ne sont pas commercialiss avec notre consentement : Siemens AG na mis aucune recommandation concernant l'utilisation de "modules compatibles SIMATIC de constructeurs tiers. La publicit des constructeurs tiers de "modules compatibles SIMATIC laisse penser a tort que les textes publicitaires dans les revues, les catalogues ou les expositions ont t convenus avec nous. Lutilisation conjointe de "modules compatibles SIMATIC de constructeurs tiers et de produits de notre systeme dautomatisation SIMATIC constitue un cas d'utilisation de nos produits qui est contraire a nos recommandations. Considrant la grande diversit d'emploi de notre systeme dautomatisation SIMATIC ainsi que limportance du parc mondial des produits installs, il nous est impossible de donner une description concrte de Ianalyse des risques lis a l'emploi des "modules compatibles SIMATIC. C79000-D8563-C702-01 12/89Nous navons pas la possibilit matrielle de procder au contrle de linteraction de notre produit SIMATIC avec les "modules compatibles SIMATIC de constructeurs tiers. Nous rejetons tout appel en garantie pour les vices survenant dans un systeme dautomatisation SIMATIC mettant aussi en ceuvre des "modules compatibles SIMATIC de constructeurs tiers. Nous dclinons toute responsabilit pour les sinistres relevant de la Responsabilit Civile Produits, tant donn que nous avons attir a temps !attention des utilisateurs sur les risques potentiels inhrents a l'utilisation de "modules compatibles SIMATIC de constructeurs tiers. > 6 C79000-08563-C702-01 12/89Safety-Related Guidelines for the User 1 General This manual provides the information required for the intended use of the particular product. The documentation is written for technically qualified personnel such as engineers, programmers or maintenance specialists who have been specially trained and who have the specialized knowledge required in the field of instrumentation and control. A knowledge of the safety instructions and warnings contained in this manual and their appropriate application are prerequisites for safe installation and commissioning as well as safety in operation and maintenance of the product described. Only qualified personnel as defined in section 2 have the specialized knowledge that is necessary to correctly interpret the general guidelines relating to the safety instructions and warnings and implement them in each particular case. : This manual is an inherent part of the scope of supply even if, for logistic reasons, it has to be ordered separately. For the sake of clarity, not all details of all versions of the product are described in the documentation, nor can it cover all conceivable cases regarding installation, operation and maintenance. Should you require further information or face special problems that have not been dealt with in sufficient detail in this documentation, please contact your local Siemens office. We would also point out that the contents of this product documentation shall not become a part of or modify any prior or existing agreement, commitment or legal relationship. The Purchase Agreement contains the complete and exclusive obligations of Siemens. Any statements contained in this documentation do not create new warranties or restrict the existing warranty. 2 Qualified Personnel Persons who are not qualified should not be allowed to handle the equipment/system. Non-compliance with the warnings contained in this manual or appearing on the equipment itself can result in severe personal injury or damage to property. Only qualified personnel should be allowed to work on this equipment/system. Siemens AG 1991 C79000-08576-C336-01Safety-Related Guidelines Qualified persons as referred to in the safety guidelines in this manual as well as on the product itself are defined as follows: e System planning and design engineers who are familiar with the safety concepts of automation equipment; @ Operating personnel who have been trained to work with automation equipment and are conversant with the contents of the manual in as far as it is connected with the actual operation of the plant; @ Commissioning and service personnel who are trained to repair such automation equipment and who are authorized to energize, deenergize, clear, ground and tag circuits, equipment and systems in accordance with established safety practices. 3 Danger Notices The notices and guidelines that follow are intended to ensure personal safety, as well as protecting the product and connected equipment against damage. The safety notices and warnings for protection against loss of life (the users or service personnel) or for protection against damage to property are highlighted in this manual by the terms and pictograms defined here. The terms used in this manual and marked on the equipment itself have the following significance: Danger indicates that death, severe personal injury or substantial property damage will result if proper precautions are not taken. Caution indicates that minor personal injury or property damage can result if proper precautions are not taken. Warning indicates that death, severe personal injury or substantial property damage can result if proper precautions are not taken. Note is an important information about the product, its operation or a part of the manual to which special attention is drawn. Siemens AG 1991 C79000-08576-C336-01Safety-Related Guidelines 4 Proper Usage @ The equipment/system or the system components may only be used for the applications described in the catalog or the technical description, and only in combination with the equipment, components and devices of other manufacturers as far as this is recommended or permitted by Siemens. @ The product described has been developed, manufactured, tested and the documentation compiled in keeping with the relevant safety standards. Consequently. if the described handling instructions and safety guidelines described for planning, installation, proper operation and maintenance are adhered to, the product. under normal conditions, will not be a source of danger to property or life. A Warning e After opening the housing or the protective cover or after opening the system cabinet, certain parts of this equipment/system will be accessible, which could have a dangerously high voitage level. @ Only suitably qualified personnel should be allowed access to this equipment/system. @ These persons must de fully conversant with any potential sources of danger and maintenance measures as set out in this manual. @ tis assumed that this product be transported, stored and installed as intended, and maintained and operated with care to ensure that the product functions correctly and safely. Siemens AG 1991 C79000-08576-C336-01Safety-Related Guidelines 5S Procedures for Maintenance and Repair If measurement or testing work is to be carried out on an active unit, the rules and regulations contained in the "VBG 4.0 Accident prevention regulations of the German employers liability assurance association (Berufsgenossen- schaften) must be observed. Particular attention i Permissible exceptions when working on $s drawn to paragraph 8 live parts". Use only suitable electrical tools. A Warning Repairs to an item of automation equipment may only be carried out by Siemens service personne! or an authorized Siemens repair center. For replacement purposes, use only parts or components that are contained in the Spare parts list or listed in the Spare parts section of this manual. Unauthorized opening of equipment and improper repairs can result in loss of life or severe personal injury as well as substantial property damage Before opening the equipment, always remove the power plug or open the disconnecting switch. Only use the fuse types specified in the technical specifications or the maintenance instructions of this manual. Do not-throw batteries into an open fire and do not Carry Out any soldering work on batteries (danger of explosion). Maximum ambient temperature 100C. Lithium batteries or batteries containing mercury should not be opened or recharged. Make sure that the same type is used when replacing batteries. Batteries and accumulators must be disposed of as classified waste. The following points require attention when using monitors: Improper handling, especially the readjustment of the high voltage or fitting of another tube type can result in excessive X-ray radiation from the unit. The license to operate such a modified unit automatically lapses and the unit must not be operated at all. The information in this manual! is checked regularly for updating and correctness and may be modified without prior notice. The information contained in this manuat is protected by copyright. Photocopying and translation into other languages is not permitted without express permission from Siemens. Siemens AG 1991 C79000-D8576-C336-01Guidelines for Handling Electrostatically Sensitive Devices (ESD) 1 What is ESD? VSLI chips (MOS technology) are used in practically all SIMATIC S5 and TELEPERM M modules. These VLSI components are, by their nature, very sensitive to overvoltages and thus to electrostatic discharge: They are therefore defined as Electrostatically Sensitive Devices "ESD is the abbreviation used internationally. The following warning label on the cabinets, subracks and packing indicates that electrostatically sensitive components have been used and that the modules concerned are susceptible to touch: ESDs can be destroyed by voltage and energy levels which are far below the level perceptible to human beings. Such voltages already occur when a component or a module is touched by a person who has not been electrostatically discharged. Components which have been subjected to such overvoltages cannot. in most cases, be immediately detected as faulty; the fault occurs only after a long period in operation. An electrostatic discharge - of 3500 V can be felt - of 4500 V can be heard - must take place at a minimum of 5000 V to be seen. But just a fraction of this voltage can already damage or destroy an electronic component. Siemens AG C79000-D8076-C339-01ESD Guidelines The typical data of a component can suffer due to damage, overstressing or weakening caused by electrostatic discharge; this can result in temporary fault behavior, e.g. in the case of temperature variations, mechanical shocks, vibrations, change of load. Only the consequent use of protective equipment and careful observance of the precautions for handling such components can effectively prevent functional disturbances and failures of ESD modules. 2 When is a Static Charge Formed? One can never be sure that the human body or the material and tools which one is using are not electrostatically charged. Smail charges of 100 V are very common; these can, however, very quickly rise up to 35 000 V. Examples of static charge: - Watking on a carpet up to 35 000 V - Walking on a PVC flooring up to 12 000 V ~ Sitting on a cushioned chair up to 18 000 V - Plastic desoldering unit upto 8000 V - Plastic coffee cup up to 5000 V ~ Plastic bags up to 000 V - Books, etc. with a plastic binding upto 8000 V 3 Important Protective Measures against Static Charge | Most plastic materials are highly susceptible to static charge and must therefore be kept as far away as possible from ESDs. e Personne! who handle ESDs, the work table and the packing must all be carefully grounded. 2 siamans AG C79000-D8076-C339-01ESD Guidelines 4 Handling of ESD Modules @ One basic rule to be observed is that electronic modules should be touched by hand only if this is necessary for any work to be done on them. Do not touch the component pins or the conductors. @ Touch components only if - the person is grounded at all times by means of a wrist strap or - the person is wearing special anti-static shoes or shoes with a grounding strip. @ Before touching an electronic module, the person concerned must ensure that (s)he is not carrying any static charge. The simplest way is to touch a conductive, grounded item of equipment (e.g. a blank metallic cabinet part, water pipe, etc.) before touching the module. Modules should not be brought into contact with insulating materials or materials which take up a static charge, e.g. plastic foil, insulating table tops, synthetic clothing, etc. Modules should only be placed on conductive surfaces (table with anti-static table top, conductive foam material, anti-static plastic bag, anti-static transport container). @ Modules should not be placed in the vicinity of monitors, TV sets (minimum distance from screen > 10 cm). The diagram on the next page shows the required protective measures against electrostatic discharge. 5 Measurements and Modification to ESD Modules @ Measurements on modules may only be carried out under the following conditions: - the measuring equipment is grounded (e.g. via the PE conductor of the power supply system) or ~ when electrically isolated measuring equipment is used, the probe must be discharged (e.g. by touching the metallic casing of the equipment) before beginning measurements. e@ Only grounded soldering irons may be used. siemens AG C79000-D8076-C339-01 3ESD Guidelines d d b e f f c t a aL. Le 3 aL. \ _ - \ = Sitting position Standing position b d a Conductive flooring \ bs Anti-static table e c Anti-static shoes d Anti-static coat e Grounding wrist strap c f | Grounding connection of f a f the cabinets > \ + Standingsitting position 6 Shipping of ESD Modules Anti-static packing material must always be used for modules and components, e.g. metalized plastic boxes, metal boxes, etc. for storing and dispatch of modules and components. lf the container itself is not conductive, the modules must be wrapped in a conductive material such as conductive foam, anti-static plastic bag, aluminium foil or paper. Normal plastic bags or foils should not be used under any circumstances. For modules with built-in batteries ensure that the conductive packing does not touch or short-circuit the battery connections; if necessary cover the connections with insulating tape or material. 4 Siemens AG C79000-D8076-C339-01Remarks Form Your comments and recommendations will help us to improve the quality and useful- ness of our publications. Please take the first available opportunity to fill out this ques- tionnaire and return it to Siemens. Please do not forget to state the title, order number and release of your manual. Title of Your Manual: .00...........cc cc ccccccsccsssossessscssscsssssssscnsccnsessacesseceessrsecescsscenecesssseesees Order No. of Your Manual: .........0......0cccccccccccccsccccssecseseccressersoees Release: ........... Please give each of the following questions your own personal mark within the range from 1 (very good) to 5 (poor). 1. Dothe contents meet your requirements? Is the information you need easy to find? Does the level of technical detail meet your requirements? 2 3. Is the text easy to understand? 4 5 Please rate the quality of the graphics/tables: Additional comments: ee 8 ee ll el lll ll ee 8 lll le ll lll lll ll eo 8 6 ee ee ll lel lll lll eo 8 ee ee ll el ll lll ll e888 ee ll lw ee ee ll le ll ll lll eee te ll ll ll lll lle ll 78000-V8576-C066-01 1JEOIWIBYOON}Ig 0 uoyVeyodsuel [| Somnxel [7 Jedeg pure ding C] NSE ld [77 jeonneoceweud Cy Se ee ee ew lk kt s0U0Ud i i Of] INOA OWEN INO) 7WwOl-j Fe eee eee UNIO Asauiyoeyy peoujoajouon O JONUOD puke JUEWNSU| C} poor fF} Arauiyoe feo1}9913 [7 FEOIWaYD eanowomny [7] :no{ 0} saydde yey) Ansnpui Aue 4OOYO eseald Aueued jo oyqndey jesepe4 OuNISHEY 1819/-G e9lt 3 nv DY susweis C79000-V8576-C066-01Remarks Form Your comments and recommendations will help us to improve the quality and useful- ness of our publications. Please take the first available opportunity to fill out this ques- tionnaire and return it to Siemens. Please do not forget to state the title, order number and release of your manual. Please give each of the following questions your own personal mark within the range from 1 (very good) to 5 (poor). 1. Dothe contents meet your requirements? 2. Is the information you need easy to find? 3. Is the text easy to understand? 4. Does the level of technical detail meet your requirements? Please rate the quality of the graphics/tables: Additional comments: ee ee tl ll A a a ee 8 ee ee ll ll lll ee He lw ee ke le ll te a e888 el le ll ll ll 79000-V8576-C066-01 1JedlwayooNed 0 uoyepodsues) C Sexe! [] Jade pue ding a ONSEld [J feonnsoeuueyd CT Se ee eee eee :eU0yg eee we wwe ee we tw we th te se)! i ano A ee ee ee ew tw eh th te te soweN ino A wal i 48ND Aauryoey jeoujoajauony 0 JOUOD pue quSLUNSu] [] poo [7] Amuryoey [29110913 |} jeoweyd [7] eAnoWoINY [7 :nof 01 seydde yey; Aysnpur Aue yooyo aSEa{d Auewuar jo aqnday jerepe eynispey 19192-d eokk a inv Dy suewais 79000-V8576-C066-01SIEMENS SIMATIC S5 How to Use the Manual C79000-D8576-C499-03D8576499-01 Contents 1 Things to Remember 2 Where Do I Find This in the Manual? 3 Abbreviations 4 Ordering Data 5 Further Relevant Documentation Page 12 14D8576499-01 1 Things to Remember This manual is intended to help you use the CP 525-2 and CP 524 communications processors as follows: . - for the "Computer link with RK 512" and - for "Event output and logging with the PT88/PT89 printer" Em It is also intended to help you program the associated CP 525 user program with the programming package COM 525. The manual is divided into two parts. GP 525-2 The CP 525-2 is often abbreviated to CP 525. GP 524 The CP 524 can be used just as the CP 525 when you wish to communicate with only one partner. The CP 524 has only ome serial device interface: it has no PG interface. Therefore only EPROM submodules that have been pro- grammed on the PG can be used on the CP 524. The serial device interface of the CP 524 corresponds to the device interface IF 1 on the CP 525. An EPROM submodule pro- grammed for IF 1 can be used both on the CP 525 and CP 524. The CP 524 is not referred to in the parts of this manual; however, almost all the information referring to IF 1 on the CP 525 also applies to the CP 524, except the CP 525 functions available when you are using the PG online (e.g. start, stop, transfer).D8576499-01 You should first develop your user program using a CP 525. You can then connect the PG online and transfer your GP 525 user program directly to a RAM submodule plugged into the CP 525. Then you can carry out the start-up. Any corrections which may be needed can then be carried out quickly. Once you have completed these corrections, you can then program the EPROM for use with the CP 524. IMPORTANT! The CP 525 and CP 524 cammot be used in association with the programmable controller S5-135U/S processor (CPU 921). We wish you every success with your commmications processor!D8576499-02 2 Where Do I Find This in the Manual? This manual COM 525 programming package for the commmications processors CP 524 and CP 525 (S5-DOS) is divided into two parts. Both parts contain a table of contents of the whole manual. Part 1 Section 1 This section is not used Section 2 This section is not used Section 3 Instructions on using the manual These are general instructions that you should bear in mind; this section also includes - abbreviations and their explanations - ordering data - further relevant documentation Section 4 Communications processor CP 525-2 Instructions This is an introductory description; it contains important information about installing and running the module.D8576499-01 Section 5 Section 6 Section 7 Section 8 Coamunications processor CP 524 Instructions This is an introductory description; it contains important information about installing and running the module. This section is not used Computer link with RK 512 User's guide This guide provides the following: - basic facts - important, general information about programming - help in correcting errors in the computer link component Event output and logging with the PT88/P189 printer User's guide This guide provides you with the following: - basic facts - important, general information about programming - help in correcting errors in the logging printerD8576499-01 Part 2 Section 1 Section 2 Section 3 Section 4 Computer link with RK 512 Example of application This is an introduction. When you have worked . through this example you will have generated a CP 525 user program in which all the important func- tions of the computer link are implemented. This section concerns programming the STEP 5 user pro- gram for the CPU. Event output and logging with the PT88/PT89 printer Example of application This is an introduction. When you have worked through this example you will have generated a CP 525 user program in which all the important func- tions of the logging printer are implemented. This section also concerns programming the STEP 5 user program for the CPU. Notes on the operating systems PCP/M-86 and S5-DOS User's guide This is information you should be familiar with before you install the COM 525 programming package. Programming package COM 525 User's guide This is an introductory guide for the programming package COM 525 as follows: - contains all the screen masks output by COM 525 - includes instructions about the entries to be made in the fields of the screen masks.D8576499-01 Section 5 Section 6 Section 7 COM 525 messages Reference manual This is a description of the error messages which are displayed on the screen of your programmer by the COM 525 programming package. PROM 525 User's guide This is an introduction to programming EPROMs as follows: - includes all the screen masks output by PROM 525 - contains information about the entries to be made in the fields of the screen masks. Using the handling blocks Reference manual This reference manual provides an overview of the functions provided by the handling blocks, with particular emphasis on the computer link or the logging printer.D8576499-01 3 Abbreviations A-NR ANZW AS 5126 a S Job number Condition codeword Interface module 512 Bell Field length Condensed print Coordination flag Chained log Computer link Current message log Programming package COM 525 for the communications processors CP 525 and CP 524 Commmications processor Central processing unit Carriage return Data block Data block number left-hand data byte in a data word Right-hand data byte in a data word Data word Expanded data block Expanded print Function block Disk drive First in first out buffer Flag word Flag byte Group inhibit bit Heavy print (data) Handling block Device interface Jumper blockD8576499-01 IAUFPT88 MEP adapter OB PAFE PB PC PG PSEUDO R/W function PSL PT88/PT89 QANF QLAE QTYP QVZ REPTEL RS422-A RS485 R/W function S5-DOS S5 program SML SSNR SYSID SYSTAT TTY U UPDATE SML Procedure LAUFPT88 (Logging printer PT88/PT89 function) Module-EPROM-programming adapter Organization block Condition code byte for parameter assignment errors Program block Programmable controller Programmer PSEUDO READ/WRITE function Process status log PT88/PT89 printer Start address of source Source length = number of pieces of source data Source type = type of data source Timeout Reply telegram EIA standard RS422-A EIA standard RS485 READ/WRITE function Operating system STEP 5 program Sequential message log Interface number Identification area SYSID Error message area of the SYSTAT Current loop signals (20 mA) Underlined Update sequential message log 10D8576499-01 v.24 ZANF ZLAE ZTYP ZVZ V.24 signals Start address of destination Destination length = number of pieces of destination data Destination type = type of data destination Character timeout llD8576499-03 4 Ordering Data Memory submodules for the CP 525-2 and CP 524: EPROM submodules 16 Kwords 32 Kwords 64 Kwords Memory submodules for CP 525-2: RAM submodules 16 Kwords 32 Kwords 64 Kwords 64 Kwords, 377 RAM submodule, buffered Interface modules for the CP 524: V.24 TTY (20 mA) RS422-A/485 Installation guidelines for SIMATIC compact Signalling functions for standard CP's: Compact signalling functions: Programming package COM PMC: 12 Order number 6ES5 373-1AA41 6ES5 373-1AA61 6ES5 373-1AA81 Order number 6ES5 377-OAB21 6ES5 377-0AB31 6ES5 377-0AB41 6ES5 377-0BB41 6ES5 752-0AA22 6ES5 752-0AA12 6ES5 752-O0AA42 devices: C79000-B8576-C252 6ES5 848-7WAOL 6ES5 842-8WA01 6ES5 848-7WEO1 6ES5 848-8WEOL 6ES5 895-4SF21 6ES5 835-4SF21 (7=MS-DOS) (8=PCP/M) (7=MS-DOS) (8=PCP/M) (9=5.25") (3=3.5")D8576499-03 Handling blocks: Order number $5-135U / R processor - 6ES5 842-xCBx0(-~yy) $5-150U 6ES5 844-xCAx0(-yy) 5-155U 6ES5 846-xCA01 Please enquire at your nearest SIEMENS branch or the nearest technical office about the numbers or letters marked x or (-yy). Standard cable connectors Order number CP 525 - PG 6xx (TTY) 6ES5 726-Oxxx0 CP 525/524 - CP 525/524 (TTY) 6ES5 726-1xxx0 CP 525/524 - PROMEA M (TTY) 6ES5 725-8xxx0 CP 525/524 - AS 512 (TTY) 6ES5 726-2xxx0 CP 525/524 - PROMEA R (TTY) 6ES5 726-3xxx0 CP 525/524 - PT88/PT89 (TIY/V.24) 6ES5 726-5xxx0 CP 525/524 - Modem N10 (V.24) 6ES5 726-7xxx0 CP 525/524 - CP 525/524 (V.24) 6ES5 726-8xxx0 CP 525/524 - PROMEA R (V.24) 6ES5 726-4xxx0 CP 524 ~ CP 524 (V.11/RS422-A) 6ES5 725-7xxx0 CP 525 IF2 - PG 7xx 6ES5 734-5xxx0 (xxx = SIMATIC length key) 13D8576499-01 5 Further Relevant Documentation /\/ See the ordering data for the handling blocks /2/ PT88/PT89 printer - description 14SIEMENS Siemens Aktiengesellschaft The reproduction, transmission or use of this document or its contents is not permitted without express written authority. Offenders will be liable for damages. All rights, including rights created by patent grant or registration of a utility model or design, are reserved. Siemens AG 1988 Order No.: 79000-88576-C541 Order from: Gerdtewerk Karlsruhe Printed in the Federal Republic of Germany AG 0689 0,5 AB 198 EnSIEMENS SIMATIC S5 Communications Processor CP 525-2 Instructions C79000-B8576-C537-07Contents Technical Description - Application Mechanical Design Serial Device Interface Dual-port RAM, Interface to the CPU Memory Submodules Hardware Clock Technical Data PRR PREP NAW PE WHE Installation nN Slots in the Programmable Controller Plugging in and Removing the CP 525-2 Installation Guidelines NUNN Wh w Operation Controls and Displays Operating Modes Status Displays Jumper Settings .l Module Address/Interface Number .2 Enabling/Disabling IPC Flags -3 Settings of the Device Interfaces 4 Permanent Jumper Settings WwW WW & WwW Ww Ww FPP HE PWN Ee 4 Setting up the Hardware 5 Pin Assignments 5.1 Backplane Connector 1 5.2 Backplane Connector 2 5.3 Memory Submodule Interface 5.4 Device Interface 1 (IF 1) 5.5 Device Interface 2 (IF 2) 16 16 17 17 18 18 19 19 20 21 23 26 28 29 30 30 31 32 33 34DAKHAAAAHARA KAA NN SW DN moO oO Standard Cable Connectors Connection Connection Connection Connection Connection Connection Connection Connection Connection Connection CP 525 CP 525/524 GP 525/524 CP 525/524 CP 525/524 CP 525/524 CP 525/524 CP 525/524 CP 525/524 CP 525, 1F2 - PG 6xx (TTY) - CP 525/524 (TTY) - PROMEA M (TTY) - AS 512 (TTY) - PROMEA R (TTY) - PT88/PT89 (TTY/V. 24) - Modem N10 (V.24) - CP 525/524 (V.24) - PROMEA R (V.24) - PG 7xx (TTY) ii 35 35 36 36 37 38 39 40 40 41 42B8576537-04 Communications Processor CP 525-2 1 Technical Description 1.1 Application The commmications processor CP 525-2 can be used in the pro- grammable controllers of the SIMATIC 5 U range (S5-115U, S$5-135U, S5-150U and $5-155U). Note that the CP 525-2 cannot be used in conjunction with the S5-1350 / S processor. Using the commmications processor CP 525-2 and the accompanying programming package COM 525 you can accomplish the following: - log process states and messages originating in the process and/or - link your programmable controller with other programmable controllers or computers By connecting the printer PT88/PT89, you can log process states and messages. The communications processor CP 525-2 initiates the compilation of message texts and their output on the printer. If the programmable controller (PC) is part of an automation network, it can exchange data with one or more programmable controllers or with a central process computer (computer link). These tasks are also carried out independently by the CP 525-2. The data exchange between the GP 525-2 and the central processor (CPU) of the programmable controller is restricted to a minimm. Only the variable data (current process values) is exchanged between the CPU and the CP 525-2. The CP 525-2 has its owm memory for invariable data, which you program using the programming package COM 525. :BBD /6537-04 Communications Processor CP 525-2 GP 525-2: - listing process statuses and messages originating in the pro- cess ~ linking programmable controllers with each other or with compu- ters STEPS BASICPACKAGE Programmingpackage forPG COM 525 0 Q Programmer Li @g.PG635 . 9 PG 675 PG PG GSE : STEPS ~ fs User program userprogram / . for CP 525-2 Programmabie controller * eg. S5-115U $5-135U $5-150U $5-155U SIMATIC $5 SIMATIC S5 SICOMP Printer with with and other AS512 CP 525 computers PT88/PT89 The communications processor CP 525-2 can be plugged into the s5 programmable controllers of the U range. By using a programmer (PG) and the programming package COM 525, you can write your user program for the CP 525-2 (e.g. message texts to be output on the PT88/PT89 printer). Once written, this user program is stored either in an EPROM submodule or in a RAM submodule. If you decide to store it in the RAM submodule, connect the PG to device interface 2 of the CP 525-2 and transfer the user program for the CP 525-2 to the RAM submodule. This submodule must already be plugged into the memory submodule receptacle of the CP 525-2.B8576537-04 Communications Processor CP 525-2 You also program your STEP 5 user program for the CPU on the PG using the STEP 5 BASIC PACKAGE. The following devices can be connected directly to the CP 525-2: - other programmable controllers ~ central computer - the PT88/PT89 printer With the CP 524 and with special drivers you can comect other manufacturers equipment to your programmable controller (e.g. computers, printers or intelligent subsystems). For more information about special drivers contact your nearest Siemens branch or technical office.DOI/0D5/-US Communications Processor CP 525-2 1.2 Mechanical Design CP 25-2 (View from front) Receptacle for memory submodule: RAM: 16, 32 or 64 Kwords x EPROM: 16, 32 or 64 ) Kwords Mode selector LED display for device interface 1 Device interface 1 (IF 1) TTY or V.24 LED display for device interface 2 Device interface 2 (IF 2} TTY or V.24 TTY interface for programming the CP 525 with the PG **): when programming the 64 Kword memory submodule on the PG you need an adapter (MEP adapter), since a different programming voltage is required for EPROMs of the type 27256.B65 /653/-03 Communications Processor CP 525-2 On its front panel, the communications processor has two 25-pin female Cannon connectors with serial device interfaces for connecting devices (printer PT88/PT89, other programmable con- trollers or central computers). Instead of these devices, device interface 2 (IF 2) can also be used to connect the programmer (PG). Each of the device interfaces has an LED display. Using the mode selector he following operating mcdes can be selected: ~ RUN ~ STOP = PGR (no jobs will be processed) The function of the switch setting STOP is identical with that of PGR. The memory submodule for the user program is plugged into the submodule receptacle. You can use either EPROM submodules or RAM submodules. The connection to the $5 bus in the PC frame is established via two 48-pin backplane comnectors. 1.3 Serial Device Interfaces Transmission via both device interfaces is serial and asynchro- nous. Both loop current (TTY) and V.24 signals ar available on the two device interfaces. The loop current (20 mA) can be supplied by both the CP 525-2 and from the partner device. Only the end which provides the current is non-floating. The CP supplies the current (20 mA) via jumpers in the connector of the device interface. The 24 V required for generating loop current is taken from the PC bus. With a closed circuit, a current of 20 mA must flow ( logical 1) if the line current circuit is functioning correctly. When the current is interrupted, logical 0 results.B8576537-03 Communications Precessor CP 525.2 The CCITT recommendations V.24/V.28 apply for the V.24 signals. A logical zero is a voltage greater than +3 V; a logical 1 a volt- age less than -3 V. The foregoing technical details are irrelevant if you use the standard cable connectors to connect the PT88/PT89 printer, other programmable controllers or certain computers. These connectors are designed for V.24 or TIY signals (see Section 6). When you write the user program with the COM 535 programming package you decide the following: - which partner is to be linked on which interface - which settings are required for the transmission parameters (transmission rate, freme format) For further details refer to the user's guide for the COM 525 programming package. 1.4 Dual-port RAM, Interface to the CPU The data exchange between the GP 525-2 and the CPU is restricted to a minimm. Only the variable data (current process values) is exchanged between the CPU and the CP. The CP 525-2 has its own user memory for invariable data, e.g., message texts. Data is exchanged between the CPU and the CP 525-2 using a common memory area: the dual-port RAM. The dual-port RAM is on the CP 525-2 and is similar to a mailbox. The GP 525-2 and CPU can leave messages (data, requests, etc.) for each other in this mailbox.B8576537-03 Communications Processor GP 525-2 The CPU of the PC always acts as master for data exchange. The CP 525-2 mist "wait to be asked" by the CPU whether it wants to transfer data. This polling function is carried out by standard function blocks ("handling blocks") in the CPU. These are the same handling blocks that are used by other communications. processors. The actual exchange of data between the CPU and CP 525-2 is also managed by handling blocks. For more details, refer to the de- * seription "Using the handling blocks" in this manual. <-----+------- CPU ----------- > <-------- CP 525-2 ---------- > | $5 bus User | memory _ Device | interface Handling Dual- 1 blocks port Data = <=>] RAM o> (Standard function Device blocks) | interface -__ 2B8576537-03 Communications Precessor CP 525-2 The dual-port RAM of the CP 525-2 is structured a: follows: Addresses Dec, Hex. 61952 F200 F220 F240 F260 F280 F2A0 F2c0 62176 F2E0 62207 F2FF 62464 F400 F7EF 65279 FEFF Area: Dual-port RAM FY 0 FY 31 FY 32 FY 63 FY 64 FY 95 FY 96 FY 127 FY 128 FY 159 FY 160 FY 191 FY 192 FY 223 FY 224 FY 255 RS area (2) page (3) page RI area RI area for IF 1 for IF 2 (4) vector (5) vector register register interface interface number number Comment (1) Ipc flag area (2048 flags) meee System data area for controlling/monitoring the data exchange one page is available for each device interface Interface area for job data A vector register is assigned to each page This diagram is explained on the following page.B8576537-03 Communications Processor CP 525-2 (1) Interprocessor commmication (IPC) flag area: IPC flags are defined as follows: - IPC flags are part of the flag area of a CPU or - if they are specified as IPC output bytes (in terms of the computer link) they are part of the dual-port RAM of the CP 525-2. These IPC flags are also called coordination flags. IPG flags are required because they are used as follows: - for the cyclic exchange of data between CPUs in bytes - for the data exchange between CPUs and the CP 525-2. The IPC flag area in the dual-port RAM of the CP 525-2 is responsible for this function. The IPC flag area in the CP 525-2 covers 256 IPC flag bytes (2048 IPC flags). With the computer link and RK 512 the IPC flags (coordination flags) can be used to inhibit and enable the data exchange bet- ween the CPU and CP. By inhibiting this exchange, you can prevent data that has not yet been evaluated from being overwritten. These IPC flags must be designated as output flag bytes. For further details see the user's guide for the computer link with RK 512. When you are using the printer PT88/PT89, you do not need the IPC flags. The IPC flags are transferred once per STEP 5 program cycle between the flag area of the CPU and the IPC flag area of the CP 525-2 (similar to the process image for digita? inputs and outputs). To prevent multiple addressing when using several CPs or CPs and a coordinator in one PC, you must divide the IPC flags into groups (jumper settings see 3.4.2). This also applies if there is more than one CPU in a PC.B8576537-04 Communications Processor GP 525-2 Note: S5-115U: the IPC flags must be listed in DBl as IPC output flags. $5-1350: S5-155U: the IPC flags must be entered as IPC output flags in the DBl of each CPU. This is also the case when only one CPU is being used along with a CP 525-2. 5-1500: since the IPC flags are in a different address area, the function block FB TRANSFER handles the cyclic exchange of IPC flags between the CPU and CP. The IPC flags must be specified when the block is called. The block call must be at the end of the cycle of your STEP 5 progran. (2)G) Data transfer area (page) Each device interface of the CP 525-2 has its own page assigned to it. This means that each CP 525-2 used in a programmable controller has two pages. The page is the area within the dual-port RAM in which data is exchanged between the CP 525-2 and the CPU. This data may, e.g., be numerical values, to be logged on the printer. In addition, the programmable controller can also transfer system mes- Sages to the CP 525-2 via the page. (4)(5) Vector register - interface number The pages of all the CPs in a PC are in the same address area. To ensure that only the required page is addressed when data are exchanged, each page can only be addressed by its interface muber. This is between 0 and 255 and is set on the CP by means of jumpers. Each page has a vector register allocated to it. The vector registers of all the CPs have the same address. 10B8576537-03 Commmications Processor CP 525-2 If one of the two pages of a particular CP is to be addressed by the CPU (e.g., to transfer data to the CP 525-2), the CPU writes the interface number of the required page in all the vector registers available. Each CP compares the contents of the vector register with its own two interface numbers. If the CP recognizes that the number matches an interface number, the required page is enabled for data transfer. This function is carried out automat- ically by handling blocks. Since the interface numbers of the CP 525-2 can only be set in pairs, you set the even interface mmber of IF 1 on the CP 525-2. The interface number of IF 2 is automatically set with the next higher number (for more details see 3.4.1 Module address/inter- face number). second CP 525-2 first CP 525-2 Example with 2 CPs Page 1 Page 2 Page 1 Page 2 | all pages are in the same address Seale Inter- Inter- Tnter- Inter- numbers between 0 face face face face and 255 set with number number number number jumpexs on the CP e.g. "2"| e.g. "3" e.g. "4" e.g. "5" Vector Vector Vector Vector all vector registers register; register register| register] are in the same address area 11589/653 /-03 Communications Processor CP 525-2 1.5 Memory Submodules The memory submodule of the CP 525-2 contains your CP 525 user program. The user program includes the following: - the specific programs for the device interfaces ("interpreters and procedures"). These programs decide which function (compu- ter link or printer) is carried out via which interface on the GP - the "actual" user program, i.e. , the message texts for the logging printer and/or the telegram parameters for the computer link The interpreters and procedures of the two interfaces require a total of 8 Rwords (2 x 4 Kwords) in the memory submodule, regar- dless of whether one or both interfaces are being used. The CP 525-2 also stores a user data manager for each interface in the memory submodule. This manager is dynamic, i.e., it grows with the number of items of user data ; per interface it can be a maximum of 4 Kwords long. Computer link with RK 512: per interface a maximum 1 Kword is re- quired for the telegram parameters. A 16 Kword Mewory submodule is adequate for one computer Link per CP 525-2 interface Printer PT88/PT89: the available memory space depends on the ca- pacity of the memory subniodule and on whether one or two inter- faces are being used. You can use either EPROM submodules or RAM submodules. When it is plugged in, the RAM is battery-backed via the backplane bus of the programmable controller. VIMPORTANT!: if the RAM submodule is unplugged from the CP 525-2 or the CP is disconnectei from the PC, the user program stored in the RAM is lost!!! 12B8576537-05 Communications Processor CP 525-2 The following memory submodules are available for the CP 525-2: EPROM submodules 16 Kwords 32 Kwords 64 Kwords When you are programming this submodule on the PG, you must use an adapter (MEP adapter), since a different programming voltage is required for EPROMs of the type 27256. RAM submodules 16 Kwords 32 Kwords 64 Kwords In the CP 525-2, you may also use the buffered 377 RAM submodule (64 Kwords). The order numbers for these submodules can be found in the order- ing data in this manual. If you wish to use both interfaces the following submodules can be used: IF1 and IF2 16 Kw 32 Kw 64 Kw submodule submodule submodule PT88/PT89 / PT88/PT89 no yes yes PT88/PT89 / CL yes yes yes CL / PT88/PT89 yes yes yes CL / CL yes yes yes PT88/PT89 - printer PI88/PI89 CL - computer link with RK 512 If you only require one interface you can use all the memory submodules for the printer and the computer Link. 13B8576537-07 Communications Processor CP 525-2 1.6 Hardware Clock In contrast to the CP 524 (software clock) the CP 525 has a battery-backed hardware clock to display the date and time. Leap years and changes of year are automatically taken into ac- count by the software of the CP. Even if the CP 525 is switched off (for up to 1 year), with data supported only by the battery back-up, changes of year and leap years are taken into account when it is switched on again. As soon as the CP 525-2 module has been plugged into the pro- grammable controller, the clock starts running with the settings: January lst, 0.00 hours. The year is set at random. Further details about the hardware clock can be found in the users guide "Computer link with RK 512" or in the users guide "GP 525: signalling and listing with the PT88/PT89 printer" (CP 525: reading and writing the date and time). The hardware clock is accurate to +/- 50 ppm, i.e. +/- 4.3 seconds per day. 14B8576537-07 1.7 Technical Data Degree of protection according to DIN 40050 and TEC 144 Perm. ambient temperature during operation during transport and storage Humidity class DIN 40040 Operating altitude Power supply Current input 5 V Current input 24 V Back-up voltage Back-up current (at 60C and without RAM submodule) Transmission procedure Transmission rate Transmission cable Transmission link TTY Transmission link V24 Design dimensions (W x H x D) backplane connector (packaging system) Weight Communications Processor CP 525-2. IPOO 0c to 55 -40 to +70C code letter F up to 3,500 m above sea level 5 V +/- 5%; 24 V for current sources 2.1 A max; 1.8 A measured statically 60 mA min. 2.7 V 140 yA max. asynchronous, procedures can be loaded via PG 110 to 19200 bps with TITY max. 9600 bps shielded 4-wire cable with braided shield and metal connector: earthing required both ends max. 1 km at 9600 bps max. 20 m 20.32 mm x 160 mm x 233.4 mm ES 902 / row 2, 48-pin approx. 0.4 kg 15B8576537-04 Commmications Processor CP 525-2 2 Installation 2.1 Slots in the Programmable Controller The CP 525-2 can be plugged into the following programmable controllers (fan required): $5-1150 with subrack CR 700-2 Slot number $5-1150 with subrack ER 701-3 0 1 2 3 4 5 6 The interface modules 304 and 314 are required $5-1150 with subrack CR 700-3: 0 1 2 3 4 5 The interface modules 304 and 314 are required Fan required $5-1350 11 19 27 35 43 51 59 67 With the CP 525-2, no coordination processor is required if only one CPU is used. $5-1500 3 11 19 107 | 115 | 123 | 131 | 139 | 147 Further details about your programmable controller can be found in the appropriate manual. 16B8576537-06 Communications Processor CP 525-2 $5-1550 19 35] 43{ 51] 59 75} 83] 91} 99)107)115/123/131]139)147 The CP 525-2 can be plugged into the following expansion wit (fan required): EU 1850 19) 27} 35) 43) 51] 59] 67; 75) 83) 91] 99/107]115]123/1311139 The interface modules 304 and 314 are required. 2.2 Plugging in and Removing the CP 525-2 Do not remove or plug in the CP 525-2 when the power is on! This also applies when you are replacing the memory submodule! 2.3 Installation Guidelines The connecting cable between the CP 525-2 and a partner device must be a cable with a shield earthed at both ends and with metal connectors. The standard cable comnectors listed in the catalog and in Section 6 meet these requirements. The shield must make large area contact with the casing of the metal connector (not on pin 7). If the partner device does not have a metal comector, the cable shield must make large area contact with ground. If there is a large difference in ground potential between the CP 525-2 and the partner device, a poten- tial equalizing cable should be included. The cable should be kept away from thyristor drives and power cables carrying more than 500 V. Further information about installation can be found in the "Installation guidelines for SIMATIC compact devices" (see ordering data). 17B8576537-03 Communications Processor CP 525-2 3 Operation 3-1 Controls and Displays CP 625-2 (View from front) RUN STOP Mode selector PGR LED display for device interface 1 LED display for device interface 2 18B8576537-03 Communications Precessor CP 525-2 3.2 Operating Modes Mode selector RUN The processor runs in the normal operating mode, the user functions which have been progremmed are processed. The LEDs are not lit (: LEDs are lit, see 3.3) STOP = PGR No jobs are processed. The function of the switch position "STOP" is identical with that of "PGR". The LEDs are lit. 3.3 Status Displays Each interface has a red LED display. If the LED display of a device interface is lit, one of the following has occurred: - device driver and procedure for the interface not loaded - mode selector switched to STOP/PGR - following the loading of the user program, drive and procedure, no CP 525-2 cold restart was carried out CP 525-2 still in start-up phase following a power failure (takes max. 10 s) - "serious" error recognized during start-up (e.g., wrong memory submodule; submodule type not permitted). 19B8576537-03 Communications Processor CP 525-2 3.4 Jumper Settings The diagram below shows the position of the jumper blocks on the module. Adjustments need to be made only on JB 16 / JB 25 / JB 51. The jumpers on the remaining jumper blocks are set in the factory and should not be changed. eer in SSE He Memory submodule EPROM or RAM ~ BQOATOMSZOO vMH JB16 ogg Module address j oov0gc0nn cooo0cnn rest pmper 4 a nadeoing UIE OI JB51 mode veseont! IP HD) up 2s signals IPC fiag area HII fil M6 \F 1 _ as O IF2 DOAOMZZOO v!8E. IF... = Device interface .., JB... = jumper block ... 20B8576537-03 Communications Processor CP 525-2 3.4.1 Module Address / Interface Number As described in 1.4, the data is transferred via the page area of the dual-port RAM. Each of the two device interfaces of the CP 525-2 has its own page and is allocated its own interface number (values from 0 to 255). You specify the interface numbers by setting the module address of the GP 525-2 at JB 16. For example, if you select the module address "0", (no jumpers inserted), then device interface 1 (IF 1) has the interface number "0". Device interface 2 CIF 2) is automatically assigned the next higher number - interface number sje. IF 1 IF 2 Page 1 Page 2 Module address > Interface number Interface number e.g. "0" plus 1 = e.g. "1" (only even numbers allowed) YIMPORTANT! The jumper setting is binary. Only even numbers can be selected for IF 1; IF 2 is then automatically assigned the next higher odd number. Note: to ensure that the CPU addresses the CP correctly, you must specify the same interface number (parameter SSNR) when assigning parameters to the handling blocks as that set on the CP. 21B8576537-03 Communications Pri cessor CP 525-2 Jumper block no. 16: 1615 141312 11 lu 9 Jumper Value 6 09 0 6000 8-9 irrelevant 20 9 0 000 000 7-10 2 gi 12345678 6-11 4 22 5-12 8 23 4-13 16 24 3-14 32 2 Jumper open: 0 x 2 =0 2-15 64 26 Jumper inserted: 1 x 2 1-16 128 Q! Example: selected interface number equals 12 1615 1413121110 9 | 123 4567 8 o 09 0 0 98 o oO 0 0000 o 0 12 decimal = 0x29+0x2)+1%2741%2340%24+0x240x26+0%27 Jumpers 6-11 and 5-12 are inserted; the other jumpers remain open. The upper device interface (i.e. IF 1) now has interface number 12 and the lower device interface therefore automatically has address 13, 22B8576537-03 Communications Precessor CP 525-2 3.4.2 Enabling/Disabling IPC Flags As described in 1.4 and in the user's guide "Computer link with RK 512" you can enable or inhibit the data transfer between the CPU and CP 525-2 by using the IPC flags. These IPC flags must be specified as output flags; in this situation the term "coordin- ation flag" can be used instead of the term IPC flag. The printer PT88/PI89 does not require any IPC flegs. A total of 256 IPC flag bytes are available in the programmable controller (2048 IPC flags). In multiprocessor operat:.on, IPC flags are a means of exchanging data between the processors. If several CP 525-2s or several GPUs (in the S5-135U) are installed in the programmable control- ler the IPC flags must be divided up among the CPs and the coor- dinator (see also instructions for the $5-135U). The IPC flags must then be enabled on the modules by means of jumpers. On the CP 525-2 there are eight jumpers available at jumper block 25. With the appropriate jumper setting on this block, 32 contiguous IPG flag bytes can be enabled or disabled. 23B8576537-03 Communications Processor CP 525-2 Jumper block no. 25: 8 7654321 Jumper IPG flag byte 000000 60 8- 9 0... 31 000000 7-10 32... 63 6-11 64... 95 91011 12 13 14 15 16 5-12 96 .. 127 4-13 128 .. 159 3-14 160 .. 192 2-15 192 .. 223 1-16 224 .. 255 Jumper inserted: the corresponding IPC flag bytes are enabled. NIMPORTANT!: the corresponding IPC flag bytes must also be entered in the DBls of the CPUs in the $5-135U and 115U! These can then be addressed as flags in the STEP 5 program. 24B8576537-03 Communications Pre zessor CP 525-2 The following is an example of the distribution of IPC flags between two CP 525-2s and one coordinator with the $5-135U: Coordinator first GPU second GPU first second CP 525-2 CP 525-2 DB1 _ DBL 0..31 8, 12 32,35,61 IPC IPC 32..63 output output flag flag 64. .255 bytes bytes 64 64 IPc IPc output | input flag flag byte byte This example specifies that the first CPU coordinates the data exchange with the first CP 525-2 via one (or several) bits of the IPC flag bytes 8 and 12. Therefore the area 0 to 31 is enabled on the first CP 525-2. (An area of 32 contiguous IPC flags must always be enabled or disabled). Jumper 8-9 is inserted on jumper block 25. In DBl of the irst CPU, you must enter bytes 8 and 12 as IPC output flag bytes. In the same way the second CPU coordinates the data exchange with the second CP 525-2 via iPC flags 32, 35, 61. On the second GP 525-2 the area 32 to 63 must therefore be enabled (jumper 7-10 inserted). You must then enter the bytes 32, 35 and 61 as IPC output flags in DBl of the second CPU. Since the IPC flag area :xists only once in each PC, only the IPC flags 64 to 255 can be used for other purposes. In this example we selected the IPC flag 64 for CPU - CPU commmication (IPC output flag in DBl of the first CPU - IPC input flag in DB1 of the second CPU). The area which contains byte 64 must therefore also be enabled in the coordinator. 25B8576537-03 Communications Processor CP 525-2 3.4.3 Settings of the Device Interfaces Each device interface has both 20 mA current loop signals and V.24 signals. According to CCITT, control signals are required for V.24. The evaluation of the control signals depends on the device procedure installed. The jumpers are set at the factory so that the signals are not evaluated by the procedure software. This setting means that all devices intended for connection to the CP 525-2 can be oper: ted, The control signals are as follows: Pin 6 Data set ready DSR 5 Clear to send cTS On each device interface one of these Signals can be used (as required). The factory setting of the jumpers is as follow: 16 151413121110 9 | 123 45 67 8 ml o o 3 | | ] Jumper block 10. 51 0 26B8576537-03 Communications Processor CP 525-2 The significance of the -umpers is as follows: Device interface 1: 8- 9 inserted and 7-10 open 7-10 inserted and 8- 9 open 6-11 inserted 6-11 open 5-12 open 5-12 inserted Device interface 2: 4-13 inserted and 3-14 open 3-14 inserted and 4-13 onen 2-15 inserted 2-15 open 1-16 open 1-16 inserted uot DSR (pin 6) selected CIS (pin 5) selected CIS/DSR input not used the signal selected with jumpers 8- 9 and 7-10 can be evaluated by the software the signal is inverted for evaluation the signal is evaluated directly DSR (pin 6) selected CIS (pin 5) selected CIS/DSR input not used the signal selected with jumpers 4- 13 and 3-14 can be evaluated by the software the signal is inverted for evaluation the signal is evaluated directly 27B8576537-03 Communications Processor CP 525-2 3.4.4 Permanent Jumper Settings The following jumpers are. set in the factory and saist not be changed: 1615 1413121110 9 0 Oo [| | o 0 0 123 45 67 8 Jumper block no. 17 oo 1615 1413121110 9 00 [| | o 0 0 1234567 8 o 0o 0 | Jumper block no. 23 Cm oO o 0 90 16 151413121110 9 Jumper block no. 34 o_o Ooo 12345 67 8 28B8576537-03 Communications Processor CP 525-2 4 Setting up the Hardware When installing the GP 525-2 module, follow the checklist below: 1. Check the jumper setting on the module according to 3.4. 2. Insert a memory submodule in the CP submodule receptacle. 3. Plug the CP 525-2 module into one of the permitted slots in your device. The power supply must be switched off (see 2.1). 4. Connect the partner device (e.g. PT88/PT89) and the CP 525-2 (see Section 6). 5. Check the position of the mode selector on the GP 525-2. It must be switched to "RUN", to allow data exchange with the partner device. 6. Make the correct settings at the partner device. These settings can be found in the user's guide "Computer link with RK 512" and "Printer PT88/PI89" in the section describing installation. Make sure that the parameters required for transmission (data rate, parity, stop bit, character length) are the same in both the partner device ani the CP 525-2. 7. Switch on the power supply to your CP. Both LED displays on the front of the CP 525-2 light up. The operating system carries out a self-test. The LED of the device interface being started goes out if n> error has been detected and you have done one of the folloving: ~ plugged a programmed EPROM into the CP (device driver and transmission procedure must be programmed for each device interface) -transferred your user program from the PG to the RAM plugged into the CP 525-2 and have then carried out a cold restart. 29BBD /653/-03 Communications Processor CP 525-2 5 Pin Assignments 5.1 Backplane Connector 1 d b z 2 Ground +5 V 4 U BAT 6 ADB 12 ADB 0 /CPKL 8 | ADB 13 ADB 1 /MEMR 10 ADB 14 ADB 2 /MEMW 12 ADB 15 ADB 3 /RDY 14 ADB 4 DB O 16 ADB 5 DB 1 18 ADB 6 DB 2 20 ADB 7 DB 3 22 ADB 8 DB 4 24 ADB 9 DB 5 26 ADB 10 DB 6 28 | /DSI ADB 11 DB 7 30 BASP 32 Ground 30BOD/OIS/-US Communications Processor CP 525-2 5.2 Backplane Connector 2 Ground +5 V 10 12 14 16 /BAU 18 20 /HOLDA /DMAFA 22 /STOPPA 24 GEP 26 28 30 GROUND 24V 32 Ground +24V 31B85 /653/-U3 Communications Processor CP 525-2 5.3 Memory Submodule Interface c b a 1 ADB 12 Ground +5 V 2 ADB 0 ADB 1 ADB 2 3 ADB 3 ADB 4 ADB 5 4 ADB 6 ADB 7 ADB 8 5 ADB 9 ADB 10 ADB 11 6 ADB 13 ADB 14 /BD 7 /WR DB O DB 1 8 DB 2 DB 3 DB 4 9 DB 5 DB 6 DB 7 10 DB O DB 1 DB 2 11 DB 3 DB 4 DB 5 12 DB 6 DB 7 Ki 13 /CS /CS K2 14 /cs /cS K3 15 UCMOS PSW K4 16 +5 V Ground K5 32B8576537-03 Commmications Processor CP 525-2 5.4 Device Interface 1 (IF 1) Pin Auwnp 10 ll 12 13 14 15 16 17 18 19 20 21 22 23 24 25 Designation ground (G,.) transmitter TXD V24 IF1 receiver RXD V24 IF1 clear to send CTS V24 IF1 data set ready DSR V24 IF1; receiver must be converted from CTS to DSR with jumper. TTLOV not used not used transmitter (+) TTY IF not used current source (+) 20 mA receiver (+) TITY IF1 receiver (-) TITY IFl not used current source u(+) 20 mA not used not used transmitter (-) TTY IF1 not used current source (.) 20 mA not used not used current source (-) 20 mA not used 33B8576537-03 Communications Processor CP 525-2 5.5 Device Interface 2 (IF 2) * Pin AmMwWDh 10 ll - 12 13 15 16 - 17 - 18 19 20 21 22 23 24 25 Designation ground (G,,) transmitter TXD V24 IF2 receiver RXD V24 IF2 clear to send CTS V24 IF2 data set ready DSR V24 IF2; receiver must be converted from CTS to DSR with a jumper. TILOV not used receiver (+) PG TIY transmitter (+) TITY IF2 not used current source (+) 20 mA receiver (+) TTY IF2 receiver (-) TIY IF2 not used current source (+) 20 mA not used receiver (-) PG TTY transmitter (-) TITY IF2 not used current source (-) 20 mA not used transmitter (+) PG TTY current source (-) 20 mA transmitter (-) PG TTY 34B8576537-07 Communications Processor CP 525-2 6 Standard Cable Connectors For the most common connections between devices there are stand- ard cable connectors available (see ordering data). 6.1 Connection CP 525 - PG 6xx (TTY) The cable can only be connected at the lower jack of the CP 525. CP 525 PG _ rT TTT 7] | | +AxD +20mA Acca % rm x $22 +12v | ws ~% Receiver | ; | - | NY tal ! \-RxD +TxD | 1 10 | ., | 1; | ; {Transmitters | | i, | -TxD | 4,12 | Py a) r [-20mAj jee 42V | | Lj Ij | | ston Neo sae | | | | +AxD | YT 6 | | ; | yt , ; ; iver vA | oat! latxp aco | |, Rlece 7 | | N , tT TT SK Transmitter | a5! ! txp -20ma | | te 42 V | YY? yi yy Shield 4 124,25 | | Casing Gex ct TT TH | ee 7 Ki li IF | 4 | la | | | | | | to ___43 [ap le cet Transmission | | rate setting | 35B8576537-04 Communications Processor CP 525-2 6.2 Connection CP 525/524 - cp 525/524 (TTY) CP 525/524 CP 525/524 13) a. +RxD -TxD A 19 i i . \ i Receiver | i \ | Transmitters 7 141; |-Rxb +TxD | | f10 i } 2ti} |-20ma \ eoma Roe spay aL + 24VG0 12 +20MA QmA 21 101} j4txD RxD 14 (Transmitter | Receiver 191 \_/-Txp +AxD | / {13 A 4 Ww Shield YT 4 Casing Gex am _|_ Casing Gex 6-3 Connection CP 525/524 PROMEA M (TTY) CP 525/524: PROMEAM +5VQO.. Transmitter ) 7 13) 7, +RxD +8 A 17 i {| i | \ Receiver tai | \-Axo ; s/| ' ey 10 +TxD +E 15 > G)-~ +5V SK Transmitter 191! }-TxD -E 14 j i \ | | Receiver 77 1 v Shield vi -12V Casing Gex aa _L_ Casing 36DOD/OD5/-US Communications Precessor CP 525-2 6-4 Connection CP 525/524 ~- AS 512cC (TTY) CP 525/524 AS 512 (ee ewe a a a a te ee ae ~ 191 -+RKD -TD Atta oT Pr X Receiver {i } | \ | Transmitter \{47 14]; '-Ryo +TxD fj $h 2 ri t [+20mA j 5 + 24V i 1 | -20mA 17 j 1 . i. soma ~ if 420m + 24V (3 -20mAl {14s wy J 4+nD [-PxD | i115 1 ro tot , \ Tranemiter id i it Receiver x4 ig! | | -tp +PxD_ | fi 3 vey Shield . Casing Gex ot Te PO""L Casing as p23 -. 2a 124 | Device 912 identifier b 25 i 13 - ee ee te re ee et ee ee ere ae cee ne ae Note: to generate a current loop the AS 512 must be supplied with 24 V via the AMP connectors on the front panel, 37bBD/055/-U3 Communications Precessor CP 525-2 6.5 Connection CP 525/524 PROMEA R (TTY) CP 525/524 PROMEA R ee 16! h +20mA + 24VCO4_f, 131} 4 +RxD eceiver |i fom 1 RF R i {~RxD +THD 4 114 ! \ \Transmitter 5 47 24 20mA TxD i ! L it 12 +20mA [i \ + 24V-CD i | 10 +TxD i i ; | Transmitter j i i 4 19!) 1} TxD +RKD] } 4g i : 1 i i | | Receiver a 21! | | -20mA -RxD jf jt ay YY shina YY 8 | Casing Gex _[- { ft ane me ee om cee arne wee ee ere sree pe mee en wane a a ee ee a el 38B8> /0537-U3 Communications Processor CP 525-2 6.6 Connection CP 525/524 PT88/PT89 (TTY /V.24) CP 525/524 PT 88/89 Ce ee ee eee ee en . i- Se 13 A +RxD +20mA A jel +24V * i 1 i RF Receiver i \ Rxd +t | 1 it8 | + | Transmitter) 47 ! : . 20mA 10 +TxD +20m 40 4 24V Transmitter Sh 191 ~TxD +RxD 9 . Receiver 44 5 cTs Busy 25 -O-- oO Receiver Transmitter a7 3 RxD TxD 2 1 i ' ! ! . Transmitter i Receiver f>>0 2 i TH RxD 143 a, i 1 : uae fe 1, Shield 14 Casing Gex [ }-$----- ~~ ~~" | Casing me ee ee oes cee re re ee J . - Note: The cable is designed for both TTY and V.24 signals. It can therefore be used regardless of the type of interface used in the printer. With the CP 524, make sure that you use the same interface type as in the printer. 39B8576537-05 Comminications Processor CP 525-2 6.7 Connection CP 525/524 - Modem N10 (V.24) CP 525/524 Modem N10 Receiver Transmitter 3! \ RPO RDO Sy qt i. p48 a oe i | i Transmitter | | | Receiver 21 | no RD; ile iF L 7h | \iqz ,/ 7 +L 1 \ Shield 1 + Casing Gex LL Le RTS 4 cTs 5 6.8 Connection CP 525/524 CP 525/524 (V.24) CP525/524 CP 525/524 Receiver Transmitter ie 31 7, RO Rw Ap 2 | ry o<f- Transmitter | Receiver Poa nol ifs fb 7 dia LV Shield Vio CasingGex [7 | Casing Gex 40B8576537-03 Communications Processor CP 525-2 6.9 Connection CP 525/524 ~- PROMEA R (V.24) CP 525/524 PROMEA R Fe a ee Ee 1 Receiver Transmitter | a! ow RxD TxD n~ Ig q7 i 7 o<}- ! fj ij ; ; Transinitter i i Receiver > 2i} TxD RxD) 338 can \ 3 \? I 7 f Shield 45 ! Casing Gex ott I 14s) | Le eae ee ee Fr J 41B8576537-07 Commmications Processor CP 525-2 6.10 Connection CP 525, IF2 - PG 7xx (TTY) ~.CP3525,F2 0 PG IxX 21 : ' ' oo "9 | va , 18. "4. RxD TxD O's *1gTransmitter : : Receiver ' | po yo, +RxD 120mA * 1 ee . fy 330 19 , 7 oe ' S4 +24 . : +TxD 330 +420 mA, : , \, Transmitter, + moe \ : 25, * TxD 4RxD 9 \ ' f Shield ' Casing Lt -- be ee be ee ee fee 1 Casing 42SIEMENS Siemens Aktiengesellschaft The reproduction, transmission or use of this document or its contents is not permitted without express written authority. Oftenders will be liable for damages. All rights, including rights created by patent grant or registration of a utility model or design, are reserved. Siemens AG 1988 Order No.. C7$000-88576-C537 Order from: Ger&tewerk Karlsruhe Printed in the Federal Republic of Germany AG 06890.5 AB 46 EnSIEMENS SIMATIC S5 Communications Processor CP 524 Instructions C79000-B8576-C538-06Contents 1 Technical Description 1 1.1 Application 1 1.2 Mechanical Design 3 1.3 Serial Device Interface 4 1.3.1 V.24 Module 5 1.3.2 TYY Module 8 1.3.3 RS422-A/485 Module 10 1.4 Dual-port RAM: Interface to the CPU 13 1.5 Memory Submodules 19 1.6 Technical Data 20 2 Installation 22 2.1 Slots in the Programmable Controller 22 2.2 Plugging in and Removing the CP 524 24 2.3 Installation Guidelines 24 3 Operation 25 3.1 Controls and Displays 25 3.2 Operating Modes 26 3.3 Status Displays 26 3.4 Jumper Settings 27 3.4.1 Module Address/Interface Number 31 3.4.2 Enabling/Disabling IPC Flags 32 3.4.3 Jumpers on the V.24 Module 35 3.4.4 Jumpers on the TITY module 36 3.4.5 Jumpers on the RS422-A/485 Module 37 4 Setting up the Hardware 40 5 Pin Assignments 41DADNDAAAAA a WO ODWNIAHAU LS WH bf Standard Cable Comectors Connection CP 524/525 Comnection CP 524/525 Connection CP 524/525 Cormection CP 524/525 Connection CP 524/525 Connection CP 524/525 Connection CP 524/525 Connection CP 524/525 Connection CP 524 - - CP 524/525 (TTY) - PROMEA M (TTY) - AS 512C (TTY) - PROMEA R (TTY) ~- Modem N1LO (V.24) - GP 524/525 (V.24) - PROMEA R (V.24) - PT 88/PT 89 (TTY/V.24) P 524 (RS422-A or V.11) di 45 46 47 47 49 50B8576538/4 Communications Processor CP 524 1 Technical Description 1.1 Application The communications processor CP 524 can be used in the program- mable controllers of the SIMATIC 5 U range (S5-115U, S5-135U, 85-1500 and S5 155U). Note that it cannot be used in conjunction with the S5-1350 / S processor. Using the communications processor CP 524 and the accompanying programming package COM 525 you can perform the following functions: - logging process statuses and Messages from the process and/or - Link your programmble controller to other programmable controllers or computers. In association with the PT 88/89 printer ~ process statuses and messages can be logged. The commmications processor CP 524 initiates the preparation of messages to be output on the printer. If the programmable controller (PC) is part of an automation network, it can - exchange data with one or more programmable controllers or with a supervisory process computer (computer link). The CP 524 performs these tasks independently. The data exchange between the CP 524 and the central processor (CPU) of the programmable controller is restricted to a mininun. Only the variable data (current process values) are exchanged between the CPU and the CP 524. The CP 524 has its own memory for invariable data, which you program using the software package COM 525.B8576538/4 Communications Processor CP 524 Note: With the CP 524 and with special drivers you can connect other manufacturers equipment to your programmable controller (e.g. computers, printers or intelligent subsystems). For more information about special drivers contact your nearest Siemens branch or technical office.B8576538/4 Communications Processor CP 524 1.2 Mechanical Design CP 524 (View from front) Receptacle for memory submodule EPROM: 16, 32, or 64 *) Kwords RUN STOP Mode selector oO oO LED displays IF1 iF2 +. Deviceinterface *): when programming the 64 Kword memory submodule on the pro- grammer, you need an adapter (MEP adapter), since a different programming voltage is required for EPROMs of the type 27256. The CP 524 has one device interface: the interface module is plugged into the lower receptacle of the CP 524. You can select a V.24, TTY or RS422-A/485 interface.BB5/6538/4 Communications Processor CP 524 The mode selector is used to select the operating mode "RUN" or "STOP", More detailed information on the two LED displays can be found in 3.1 "Controls and displays". The memory submodule containing your CP 524 user program is | plugged into the upper receptacle of the CP 524. In the CP 524, only EPROM submodules can be used. These must first be programmed with the programmer using the programming package COM 525. The connection to the S5 bus in the PC frame is established via two 48-pin backplane connectors. 1.3 Serial Device Interface The serial device interface is plugged into the CP 524 and se- cured by means of two screws. The following interface modules are available: TITY module V.24 module BS422-A/485 module Connecting the CP 524 to the partner device is made easier by using standard cable connectors (see also Section 6). If you do not wish to use these standard cables, note the pin assignment of the interface module in 1.3.1, 1.3.2 or 1.3.3.B8576538/4 Communications Processor CP 524 The following standard cable comectors are available: CP 524 connected Module in CP 524: Interconnection in to: CP 524: transmitter, receiver CP 524 TTY - module active, passive GP 525 TTY - module active, passive AS 512 TTY - module passive, passive PROMEA M TTY - module passive, passive PROMEA R TITY - module active, active Modem N10 V.24 - module CP 524 V.24 - module PROMEA R V.24 - module PT 88/89 TIY module passive, passive PT 88/89 V.24 module CP 524 RS422/A-485 module 5 The order numbers can be found in the ordering data section of this manual. When you write your CP 524 user program using the programming package COM 525 on the programmer, you set the transmission parameters (transmission speed, frame format). 1.3.1 V.24 Module The V.24 interface module not only has lines for transmitting and receiving but also has a series of control and signal lines in accordance with the CCITT recommendations V.24/V.28. For the computer link with RK 512 and the PT 88/89 printer these control signals are, however, not required and do not need to be connected. If you want to prepare your own cable connectors, remember that unused inputs may have to be connected to open circuit potential on other devices. For more information refer to the appropriate manuals and the CCITT recommendations V.24 or v.28.B8576538/4 Communications Processor CP 524 The following diagram shows the basic intercomection of V.24 interfaces. In the example only the transmit and receive lines are connected. With V.24 signals, logical 0 is a voltage greater than +3 V; logical 1 is less than -3 V. Device 1 Device 2 GND GND RxD TxD TxD RxD Shield ShieldB8576538/4 Communications Processor CP 524 The following figure shows the pin assignment of the 25-pin female Cammon connector on the front panel of the V.24 module: 25-pin female connector Pin no. 102 /csp }___77 104 / RxD L< 3 103 /TD Ls 2 105 / RTS F> 4 106 / cis }-< 5 108.2/ DTR |}>. 20 107 / DSR L-< 6 111 L> 23 125 /RT }< 22 109 / DCD }-< 8 141 / PS3 }> 18 142 / PML }< 25 113 p> 324 only for synchronous data transfer 114 / TxC -< 15 (not available with standard jumper 115 / Rx }< 17 settings) 102 Shield} 1 ( <> Arrow shows direction of signal) Signal numbering is according to CCITT recommendation V.24, sig- nal designation is according to internationally accepted abbre- viations (RS 232 C).B8576538/4 Communications Processor CP 524 The position and significance of the jumpers on the V.24 module can be found in 3.4 in these instructions. When you program your CP 524 user program using the programming package COM 525, you specify the setting of the transmission parameters (transmission rate, frame format). 1.3.2 TYY Module The TTY module is equipped with a transmitter and receiver for 20 mA current loop signals. The current loop itself can be sup- plied both by the CP 524 and the partner device. Only the end which supplies the current is non-floating. The CP supplies the current (20 mA) via jumpers in the front connector. The 24 V required for generating the current loop are taken from the PC bus. With a closed circuit, a current of 20 mA must flow (logical 1) if the line current circuit is functioning correctly. When the current is interrupted logical 0. results. The following diagram shows the intercomection of current loop signals. Device 1 Device 2 - + TRANS- RECEIVER MITTER + - + - CURRENT |}. GROUND (CHASSIS 24V SOURCE ( ) onactive device _+ arrows show direction of flowB8576538/4 Communications Processor CP 524 The following figure shows the pin assignment of the 25-pin female Cannon connector on the front panel of the TTY module: 25-pin female connector pin no. + pH<- 13 Receiver H> 14 + i-<- 10 Transmitter p 19 + Current source j> 16 Receiver (20 mA) p<- 2. + Current source p>- 12 Transmitter (20 mA) men DG Ground _ 24V 24 V + intern extern -+ 9 Ju3 321 Current generation Shield } ]. ( <> Arrows show direction of signal flow)B8576538/4 Commmications Processor CP 524 The position and significance of the jumpers on the TTY module can be found in 3.4 in these instructions. You set the parameters for the data transmission (data rate, parity, stop bits) using the programming package COM 525 on the PG. A maximm data rate of 9600 bps is possible with the TTY module. 1.3.3 BS422-A/485 Module The RS422-A/485 module can be used in the computer Link to transfer data in full or in half duplex. The jumper settings can be found in Section 3.4. In half duplex operation, you cannot use the standard procedures 3964 and 3964R. In this case, you must use special drivers. The RS422-A/485 module can also be used with the logging printer PT88/PT89, there are, however, no standard cable commectors available. The RS422-A/485 module electrically isolates the interface signals from the power supply. The electrical characteristics of the RS422-A/485 module are as follows: - in full duplex mode: according to the EIA standard RS422-A (CCITT recommendation V.11) - in half duplex mode: according to the EIA standard RS485. The difference between the two standards is that only one transmitter may be available with the EIA standard RS422-A, whereas several transmitters and receivers are permitted with the EIA standard RS485. In half duplex mode, the data exchange can only take place via the two-wire line R. Apart from the transmit and receive lines, the RS422-A/485 module is equipped with a series of control and monitoring lines according to the CCITT recommendation X.24 and ISO 8481. For the computer link and the logging printer PT88/PT89, these control and monitoring signals are not required and do not need to be comected. 10B8576538/6 Communications Processor CP 524 In the following examples, only transmit and receive lines are connected. The following applies to signals according to the EIA standard RS422-A (V.11) and EIA standard RS485: - logic 0 (ON) corresponds to V, > Vz V4 = greater than +3 V - logic 1 (OFF) corresponds to Vv, < Vg Vp = smaller than -3 V. Basic. wiring of the interface in full duplex mode: Device 1 Device 2 GND GND R(A) < T(A) R(B) < T(B) T(A) > R(A) T(B) > R(B) Shield Shield (< > signal direction) Basic wiring of the interface in half duplex mode: Device 1 Device 2 GND GND R(A) <> R(A) R(B) <> R(B) Shield Shield (< > signal direction) Caution: Do not connect the shield with the GND. Otherwise the electrical isolation is disabled. 11B8576538/4 Communications Processor CP 524 The following diagram shows the pin assignment of the 15-pin Cannon connector in the front panel of the RS422-A/485 module: 15-pin female connector Pin number GND f--_ 8 R(A) f-_<>____ 4 R(B) }<> 111) TA) [>. 2 TB) [>. 9 c(A) }>._ 3 c(B) =} _>____ 10 I(A) < 5 IB) }+~~< 12 B(A) j|<>__ 7 BiB) }<>14__ 2) S(A) }< 6 s(B) |< 13 x(B) |} < 15-3) Shield }-____ 1 (<> signal direction) Signal designation according to CCITT recommendation X.24 1) If you operate the interface in full duplex, data can only be received on this 2-wire Line. In half duplex, data can be received and transmitted. 12B8576538/4 Commmications Processor CP 524 2) This signal can be connected either as an input or output (see jumper settings). 3) This signal can only be used when signal B is used as an output. In this case, the line X(A) is comected to the frame and not to the interface. The position and use of the jumpers on the RS422-A/485 module can be found in Section 3.4. When programming your CP 524 user program using the COM 525 programming package, you select the required transmission parameters (transmission speed, character frame). 1.4 Dual-port RAM: Interface to the CPU Data is exchanged between the CPU and the CP 524 via a common memory area: the dual-port RAM. The dual-port RAM is on the CP 524 and is similar to a mailbox. The CP 524 and CPU can leave messages (data, requests etc.) for each other in this mailbox. The CPU of the PC always acts as master for data exchange. The CP 524 mst "wait to be asked" by the CPU whether it wants to transfer data. This polling function is carried out by standard function blocks (handling blocks") in the CPU. These are the same handling blocks that are used by other commmications processors. 13B8576538/4 Commummications Processor GP 524 The actual exchange of data between the CPU and CP 524 is also managed by handling blocks. For more details, refer to the de- scription "Using the handling blocks" in this manual. <------+----- CPU ----------- > <en-nnn eee GP 524 ---------- > | S5 bus User | memory Handling | Dual- Device blocks port interface (Standard function blocks) | 14B8576538/4 Communications Processor CP 524 The dual-port RAM of the CP 524 is structured as follows: Addresses Area: Dual-port RAM Comment Dec. Hex. 61952 F200 FY O - FY 31 F220 FY 32 - FY 63 F240 FY 64 - Fy 95 F260 FY 96 - FY 127 (1) IPC flag area F280 FY 128 - Fy 159 (2048 flags) F2A0 FY 160 - Fy 191 F2c0 FY 192 - FY 223 62176 F2EO FY 224 - Fy 255 62207 F2FF -~ see er ee System data area for RS - area controlling/monitoring the data exchange ee 62464 F400 one page is available (2) page for the device interface RI area for device Interface area for interface job data F7FF : -~---- - - 65279 FEFF | (3) vector register A vector register is assigned to each page interface number This diagram is explained on the following page. 15B8576538/4 Communications Processor CP 524 (1) Interprocessor commmication (IPC) flag area IPC flags are defined as one of the following: ~ IPG flags may be part of the flag area of a CPU. ~ If they are specified as IPC output bytes (in terms of the computer link), they are part of the dual-port RAM of the CP 524. These IPC flags are also called coordination flags. IPC flags are needed because of the following: - IPG flags are used for the cyclic exchange of data between CPUs in bytes. - They can also be used for the data exchange between CPUs and the CP 524. The IPC flag area in the dual-port RAM of the CP 524 is responsible for this function. The IPC flag area in the CP 524 covers 256 IPC flag bytes (2048 IPC flags). With the computer link and RK 512, the IPC flags (coordination flags) can be used to inhibit and enable the data exchange be- tween the CPU and CP. By inhibiting this exchange, you can prevent data that has not yet been evaluated from being over- written. These IPC flags must be designated as output flag bytes. For further details, see the users guide for the computer Link with RK 512. The IPC flags are not used, if you are working with the PT88/PT89 logging printer. The IPC flags are transferred once per STEP 5 program cycle between the flag area of the CPU and the IPC flag area of the CP 524 (similar to the process image for digital inputs and outputs). To prevent multiple addressing when you are using several CPs or CPs and a coordinator in one PC, you must divide the IPC flags into groups (jumper settings see 3.4.2). This also applies if there is more than one CPU in a PC. 16B8576538/4 Communications Processor CP 524 Note; 5-115U: the IPC flags must be listed in DBL as IPC output flags. S5-135U: the IPC flags must be entered as IPC output flags in the DBl of each CPU. This also applies when only one CPU is being used along with a CP 524. S5-150U: since the IPC flags are in a different address area, the function block FB TRANSFER handles the cyclic ex- change of IPC flags between the CPU and CP. The IPC flags must be specified when the block is called. The block call must be at the end of the cycle of your STEP 5 progran. S5 155U: the IPC flags must be entered in DBl of the CPU as output flags. This is also the case when only one CPU and one CP 524 are being used. (2) Data transfer area (page) The device interface of the CP 524 has a page assigned to it. The page is the area within the dual-port RAM in which the data are exchanged between the CP 524 and CPU. (3) Vector register ~ interface muamber The pages of all the CPs in a PC are in the same address area. To ensure that only the required page is addressed when. data is exchanged, each page can only be addressed by using its interface number. This is between 0 and 255 and is set on the CP by means of jumpers. The page has a vector register allocated to it. The vector regis- ters of all the CPs have the same address. If the page of a particular CP is to be addressed by the CPU (e.g., to transfer data to the CP 524) the CPU writes the interface number of the required page in all the vector registers available. Each CP compares the contents of the vector register 17B8576538/4 Communications Processor CP 524 with its own interface number. If the CP recognizes that the number which has been entered matches its interface number the required page is enabled for data transfer. This function is carried out automatically by data handling blocks. first CP 524 second CP 524 Vector register ree eee Interface number e.g. "13" Vector register 18 Example with two CPs all pages are in the same address area numbers between 0 and 255 set with jumpers on the CP all vector registers have the same address ce ee eeB8576538/4 Communications Processor CP 524 1.5 Memory Submodules The memory submodule of the CP 524 contains your CP 524 user program, which includes the following: - the specific programs for the device interface ("interpreter and procedure"). These programs determine which fumction (computer link or printer) is performed. - the "actual" user program, i.e., the messages for the printer and/or telegram parameters for the computer link. The interpreter and procedure require a total of 8 Kwords in the memory module. The CP also sets up a manager for the user data in the module. This' manager is dynamic, i.e. it grows with the nun- ber of user data. It can occupy a maximm of 4 Kwords. For the computer link with RK 512 a maximm of 1 Kword is required. To operate a computer link a 16 Kword EPROM module is required. For the PI 88/PT 89, the required memory space depends on the size of your user progam. Only EPROM submodules can be used in the CP 524, since (in con- trast to the CP 525) there is no interface to the programmer required to load the software in the RAM. The following memory submodules are available for the CP 524: EPROM submodules 16 Kwords 32 Kwords 64 Kwords When programming this submodule on the PG you must use an adapter (MEP adapt- er), since a different programming voltage is required for EPROMs of the type 27256. The order numbers for these submodules can be found in the ordering data section of this manual. 19B8576538/6 1.6 Technical Data Degree of protection according to DIN 40050 and IEC 144 Perm. ambient temperature during operation during transport and storage Humidity class (DIN 40040) Operating altitude Power supply Current input 5 V CP 524 TTY module V.24 module RS422-A/485 module Current input 24 V TTY module Transmission procedure Transmission rate Transmission cable Transmission link TTY Transmission link V24 Transmission link RS422/A-485 Communications Processor CP 524 IP00 0c to 55 -40C to +70C code letter F up to 3,500 m above sea level 5 V +/- 5%; 24 V +25%/-15% 15A 0.8 A, measured statically 0.1 A, measured statically 0.2 A, measured statically 0.5 A, measured statically 60 mA asynchronous, exchangeable procedures 110 to 19200 bps with TTY max. 9600 bps shielded 4-wire cable with braided shield and metal connector: earthing required both ends max. 1 km at 9600 bps max, 20 m max. 1200 m 20B8576538/4 Design dimensions (W x H x D) backplane connector (packaging system) Weight Communications Processor CP 524 20.32 mm x 160 mm x 233.4 mm ES 902 / xow 2, 48-pin approx. 0.4 kg 21B8576538/4 Communications Processor CP 524 2 Installation 2-1 Slots in the Programmable Controller The CP 524 can be plugged into the following programmable con- trollers (fan required): 85-1150 with subrack CR 700-2 Slot mumber 85-1150 with subrack ER 701-3 Slot number 0 1 2 3 4 5 6 The interface modules 304 and 314 are required 85-1150 with subrack CR 700-3 Slot number 0 1 2 3 4 5 The interface modules 304 and 314 are required S5-1350 Slot number 11 19 27 35 43 51 59 67 With the CP 524, no coordination processor is required if only one CPU is used. $5-1500 Slot number 3 11 19 107 | 115 | 123 | 131 | 139 | 147 22B8576538/4 Communications Processor CP 524 $5-155U Slot number 19 | 27 | 35 | 43 { 51 115] 123] 131] 139] 147 Further details about your programmable controller can be found in the appropriate manual. The GP 524 can be plugged into the following expansion unit (fan required): EU 1850 Slot number 19] 27] 35] 43) 51] 59] 67] 75] 83] 91] 99}1071115]123 131}139 The interface modules 304 and 314 are required. 2-2 Plugging in and Removing the CP 524 The CP 524 must not be removed or plugged in when the power is on! This also applies when replacing the submodules! 23B8576538/4 Communications Processor CP 524 2.3 Installation Guidelines The connecting cable between the CP 524 and a partner device must be a cable with a shield earthed at both ends and with metal connectors. The standard cable connectors listed in the catalog and in Section 6 meet these requirements. The shield must make large area contact with the casing of the metal connector (not on pin 7). If the partner device does not have a metal comector, the cable shield must make large area contact with ground. If there is a large difference in ground potential between the CP 524 and the partner device, a potential equalizing cable should be included. The cable should be kept away from interfering a.c. power controller cables, thyristor drives and power cables carrying more than 500 V. Further information about installation can be found in the "In- stallation guidelines for SIMATIC compact devices" (see ordering data). 24B8576538/4 Communications Processor CP 524 3 Operation 3-1 Controls and Displays CP 524 RUN STOP Modeselector oO oO \F1 iF2 LEDdisplays 25B8576538/4 Communications Processor CP 524 3.2 Operating Modes Mode selector RUN The processor runs in the normal operating mode, the user functions which have been programmed are processed. The LEDs are not lit (if LEDs are lit, see 3.3) STOP No jobs are processed. The LED IFl is lit. 3.3 Status Displays If the LED Ifl is lit, one of the following has occurred: ~ device driver and procedure not loaded - mode selector switched to STOP - GP 524 still in start-up phase following a power failure (takes max. 10 s) ~ serious error recognized during start-up (e.g., incorrect memory submodule - submodule type not permitted). If the LED IF2 is lit, one of the following has occurred: - serious error recognized during start-up (e.g., incorrect memory submodule - submodule type not permitted) - GP 524 still in start-up phase following a power failure (takes max. 10 s) 26B8576538/4 Communications Processor CP 524 3.4 Jumper Settings The jumpers on the interface modules (V.24, TTY and RS422/A-485) and on the CP 524 are preset in the factory. You can use this setting to operate the CP 524 and the interface modules imme- diately (if only one communications processor is used in the PC). The interface number is then 0. All the IPC flags are enabled. To change the interface number (module address) on the CP 524 or enable/inhibit IPC flags, make the appropriate jumper settings. For more information refer to 3.4.1 and 3.4.2. V.24 Module: Jumpersettings as supplied FRONT CONNECTOR, 25 - PIN Jdu7 Backplane connector 27B8576538/4 Communications Processor GP 524 TYY-Module: Jumpersettings as supplied FRONT CONNECTOR, 25 - PIN Backplane connector 28B8576538/6 Communications Processor CP 524 RS422-A/485-Module: Jumper settings as supplied FRONT CONNECTOR, 15 - PIN Backplane connector 29B8576538/4 Commmications Processor CP 524 CP 524: factory jumper settings 6 PEER Ju 10 @,2,1 seen) 62) JB 52 Memory submodule receptacle 1 ! Faem) | &* Jus 2 lo Jug a8 JB 53 Testjumpers lfeoeeoeag 3] Ju5 (1,2,3) oem Jui (32,1) o Ju2 (1,2,3) Cees eid nena Soeaety Shane Osy interface module receptacle oes Ju7 (1,2.3) Oca Ju6 (3,2,1) oes Ju4 (1,2,3) eaabiain Ah ie 8d IF = interface Ju... = jumper... JB 30 . = jumper block... VDontomZzaZzZoo 38 RPDVDOAOMSZOO tw8B8576538/4 Communications Processor GP 524 3.4.1 Module Address/Interface Number As described in 1.4 the data is transferred via the pages of the dual-port RAM. The page is assigned an interface number ranging from 0 to 255. With the CP 524, the interface number is identical with the module address. The module address (interface number) is set in binary on the CP 524 at jumper block JB53. Note: to ensure that the CPU addresses the CP correctly, you must specify the same interface number (parameter SSNR) when assigning parameters to the handling blocks that is set on the CP. Jumper block J53: 16 15 1413121110 9 Jumper Value 000~CC0OUdUCUCUCOWCOUlCOD 8-9 1 2 00 0 0 0 0 8 Oo 7-10 2 gi 12345678 6-11 4 22 5-12 8 23 4-13 16 24 3-14 32 23 Jumper open: 0 x 2" = 0 2-15 64 26 Jumper inserted: 1 x 2" 1-16 128 2? 31B8576538/4 Commmications Processor CP 524 Example: selected interface number equals 12. 1615 1413121110 9 | 123 45 67 8 0 0 0 0 90 o oO o 0 0 9090 oOo 0 12 decimal = 0%2940x2141%2741%2340x24+0x24+0x2940x27 Jumpers 6-11 and 5-12 are inserted, the other jumpers remain open. 3.4.2 Enabling/Disabling IPC Flags As described in 1.4 and in the user's guide "Computer link with RK 512" you can enable or inhibit the data transfer between the CFU and GP 524 by using the IPC flags. These IPC flags must be designated as output flag bytes. In this situation, the term coordination flag" can also be used instead of IPC flag. A total of 256 IPC flag bytes are available (2048 IPC flags). No IPC flags are used with the PI 88/89 printer. In miltiprocessor operation, IPC flags allow the exchange of data between the processors. If several CP 524s or several CPUs (in the S5-135U) are installed in the programmable controller, the IPC flags must be divided up among the CPs and the coor- dinator (see also instructions for the $5-135U). The IPC flags must then be enabled on the modules by means of jumpers. On the CP 524 there are eight jumpers available at location JB52. By appropriate jumper setting at this location, 32 contiguous IPC flag bytes can be enabled or disabled. 32B8576538/4 Jumper block JB52: 8 765 43 241 oo 09 0 0 CO Oo o 09 0 0 86 08 06 Jumper inserted: the corresponding IPC flag bytes are enabled. 10 11 12 13 14 15 16 Commmications Processor GP 524 Jumper 8- 9 7-10 6-11 5-12 4-13 3-14 2-15 1-16 IPC flag byte QO... 31 32... 63 64... 95 96 .. 127 128 .. 159 160 .. 191 192 .. 223 224... 255 TIMPORTANT!: the corresponding IPC flag bytes must also be entered in the DBls of the CPUs in the $5-135U and 115U! These can then be addressed as flags in the STEP 5 program. 33B8576538/4 Communications Processor CP 524 The following example shows the distribution of IPC flags between two CP 524s and one coordinator with the S5-135U: Coordinator first CPU second CPU first second CP 524 CP 524 DB1 DB1 0..31 8, 12 32,35,61 IPG Tec 32..63 output output flag flag 64, .255 bytes bytes 64 64 IPC IPG output input flag flag byte byte This example specifies that the first CPU "coordinates" the data exchange with the first CP 524 via one (or several) bits of the IPC flag bytes 8 and 12. Therefore the area 0 to 31 is enabled on the first CP 524. (An area of 32 contiguous IPC flags must always be enabled or disabled!). Jumper 8-9 is inserted on JB 52. In DB1 of the first CPU, you must enter bytes 8 and 12 as IPC output flag bytes. In the same way the second CPU coordinates the data exchange with the second CP 524 via IPC flags 32, 35, 61. On the second CP 524, area 32 to 63 must therefore be enabled (jumper 7-10 inserted). You must then enter bytes 32, 35 and 61 as IPC output flags in DBL of the second CPU. Since the IPC flag area exists only once in each PC, only IPC flags 64 to 255 can be used for other purposes. This example uses Ipc flag 64 for CPU - CPU communication (IPC output flag in DBl of the first CPU - IPC input flag in DB1 of the second CPU). The area which contains byte 64 must therefore also be enabled in the coordinator, 34B8576538/4 Commmications Processor CP 524 3.4.3 Jumpers on the V.24 Module Jumpers Jul and Ju2 determine whether the internal clock pulse of the CP 524 is used as the transmit and receive clock pulse on the CP 524 or whether the pulse is supplied by the line . 1 2 3 Jul oo Oo o oo Ju8 oo oOo o Oo Ju2 oo oOo o Oo Ju4 oo oO Receive clock pulse internal Receive clock pulse from line Receive clock pulse = transmit pulse Receive clock pulse depends on Jul Transmit clock pulse internal Transmit clock pulse from line Transmit clock pulse of CP 524 connected to line 113 (pin 24) Transmit clock pulse not supplied by CP 524 With jumpers Ju3 and Ju5, the polarity of the transmitted and received data can be reversed as follows: Ju3 oo Oo Ju5 oo Oo Transmitted data with normal polarity Transmitted data negated Received data with normal polarity Received data negated With jumper Ju6, all V.24 receivers can be connected so that all the signals are in the positive voltage range as follows: 1 2 #3 Jub oo o All received signals must have the v.24 signal level. oo All received signals can be in the positive voltage range 35B8576538/4 Communications Processor CP 524 With jumper Ju9, CTS can be permanently at open circuit potential or switched through from the front plug as follows: 1 2 3 Jud oo o CTS at open circuit potential o o---o CTS at pin 5 3.4.4 Jumpers on the TIY Module With jumpers Jul and Ju2, the polarity of the transmitted or received data can be reversed as follows: Jul oo o Transmitted data negated o o--o Transmitted data with normal polarity Ju2 oo o Received data with normal polarity o oO--o Received data negated With jumper Ju3, the 24 V source voltage for generating the current loop can be reconnected as follows: Ju3 oo o 24 V supplied by pin 9 of the front connector o oo 24 V supplied by backplane connector (internally) Ju4 oo o Receive clock pulse from transmit pulse o oo Receive clock pulse supplied by CP 524. 36B8576538/4 Communications Processor CP 524 3.4.5 Jumpers on the RS422-A/485 module The jumper X3 is used to switch over the data direction on the two-wire line R. 1 2 3 x3 oo o Setting for full duplex mode. Data can only be received on the two-wire line R. x3 o o-o Setting for half duplex mode. With the signal /RTS, data can either be transmitted or received on the two- wire line R. /RTS = O --> transmit /RTS = 1 --> receive Using the jumper 4 you can apply either the signal /PS3 or the be) internal transmit clock pulse (TxCint) to the two-wire Line B, providing that the two-wire output B is set as an input by jumpers X8 and X9. 1 2 3 X4 oo o Signal /PS3 can be transmitted on the two-wire line B. X4 o o-o The internal transmit clock pulse TxCint can be sent on the two-wire line B. With jumper X5 you can use a clock pulse transmitted on the two- wire line S as the receive clock pulse. x5 (on) Clock pulse at input S is not used as receive clock pulse. x5 oo Clock pulse at input S is used as the receive clock pulse. 37B8576538/4 Commmications Processor CP 524 With jumpers X6 and X7 you can select the transmit and receive clock pulse. 1 2 3 oo 0 o oo o OooO o oo oo Oo ooO Oo o oo oo Oo The internal transmit clock pulse (TxCint) is used as transmit and receive clock pulse. The internal transmit clock pulse (TxCint) is used as the transmit clock pulse and is used as the receive clock pulse. The clock pulse transmitted via the two-wire line S is used as the transmit clock pulse and the internal receive clock pulse used as the receive clock pulse. The clock pulse transmitted via the two-wire line S is used as the transmit clock pulse, the internal receive clock pulse (RxCint) is used as the receive clock pulse. The jumpers X4, X5, X6 and X7 can be used for synchronous transmission with clock pulse control according to the DIN draft ISO 8481. The two-wire line B (designation X according to ISO 8481) must be set as an output by jumpers X8 and X9. 4 x5 X6 x7 1 2 3 o oo oo o o 0 o o oo The internal transmit clock pulse (TxCint) is used as the transmit clock pulse. The internal clock pulse is simultaneously transmitted on the two-wire line B. 38B8576538/4 Communications Processor CP 524 With jumpers XB and X9 you can set the two-wire line B as an input or ouptut. 12 3 4 x8 oo oo Two-wire line B is comected as x9 oo o--O an output. The line X(B) can be used as an input. X(A) is connected to frame. X8 o Ooo o Two-wire line B is comnected as x9 o ooO o an input. The line X(B) cannot be used, With jumpers X10 and X11 you can suppress the control signal on the two-wire line R for recognizing the break status. X10 o Oo No control signal on the two-wire x11 o o line R - recognition of the break status cannot be guaranteed. X10 oo Two-wire line R has the control x11 oo signal, the break status will be recognized. 39B8576538/4 Commmications Processor CP 524 4 Setting up the Hardware When setting up the CP 524 module follow the checklist below: 1. Check the jumper setting on the module according to 3.4. 2. Insert a programmed EPROM submodule in the receptacle. 3. Insert an interface module in the receptacle. Check the jumper setting according to 3.4. The interface module must be secured by the two screws. 4. Plug the CP 524 module into one of the permitted slots in your device (see 2.1). The power supply must be switched off. 5. Connect the partner device to the CP 524 (see Section 6). 6. Check the position of the mode selector on the CP 524. It must be switched to "RUN", to data exchange with the partner de- vice. 7. Make the correct settings at the partner device. These settings can be found in the user's guide "Computer link with RK 512" and "Event output and logging with the PT 88/PT 89 printer" in the sections describing installation. Make sure that the parameters required for transmission (data rate, parity, stop bit, character length) are the same in both the partner device and the CP 524. 8. Switch on the power supply to your PC. Both LED displays on the front of the CP 524 light up. The operating system carries out a self-test. The LEDs go out if no error has been detected and if the device driver and transmission procedure for the serial device interface are present in the EPROM. 40B8576538/4 Commmications Processor CP 524 5 Pin Assignments Backplane connector 1 Backplane connector 2 d b z d b z 2 OV +5V 2 OV +5V 4 _ 4 6 | ADB 12] ADB O] CPKL 6 8 | ADB 13] ADB 1] MEMR 8 10 | ADB 14] ADB 2} MEMW 10 12 | ADB 15] ADB 3] RDY 12 14 ADB 4{ DB 0 14 16 ADB 5] DB 1 16 18 ADB 6] DB 2 18 20 ADB 7] DB 3 20 22 ADB 8] DB 4 22 STOPPA 24 ADB 9] DB 5 24 26 ADB 10} DB 6 26 28 ADB 11] DB 7 28 30 30 M24 Vi M24V 32 ov 32 OV + 24V 41B8576538/4 Memory submodule connector Communications Processor CP 524 c b a 1 | SADB 12 M +5V 2 | SADB O SADB 1 | SADB 2 3 | SADB 3 SADB 4 | SADB 5 4 | SADB 6 SADB 7 | SADB 8 5 | SADB 9 SADB 10 | SADB 11 6 | SADB 13 SADB 14 | OE 7 | WRITE SDB 8 SDB 9 8 | SDB 10 SDB 11 SDB 12 9 | SDB 13 SDB 14 SDB 15 10 | SDB O SDB 1 SDB 2 11 {| SDB 3 SDB 4 SDB 5 12 | SDB 6 SDB 7 Kl 13 | cS 1 cs 3 | K2 14 | cs 2 cS 4 K 3 15 | ucMOS +5 V | Psw K4 167, +597 M K 5 42B8576538/4 Communications Processor CP 524 Interface module connector c b a 1 21M M M 3]),+5V +5V +5V 4 | SSK1 Pil RxD 5 | SSK 2 Ps 3 TxD 6 | SSK 3 HUE cts 7 RIS 8 DSR 9 DIR 10 DCD 11 RI 12 TxC 13 TxC Int 14 RxD RxC 15 | M24 V M24V RxC Int. 16 | + 24 V +24 V +24V 43B8576538/4 Communications Processor CP 524 6 Standard Cable Connectors For the most common connections between devices there are stand- ard cable connectors available (see ordering data). 6.1 Connection CP 524/525 - cP 524/525 (TTY) CP 525/524 CP 525/524 13] +PD TxD, {19 7 7 7 NS +. Receiver | | Transit > 7 141 j_|-AxpD +TxD_j | {10 : r 21j{ -20mA .2omal 2p osy + 24Vqco 124} }-20ma omaj__| {21 1 _ 10}} /+TmD | ~ \Axp 14 S ( Transmnitey Receiver 19) \_/-Txp +FxD 13 Z 1 Shield of 4 Casing Gex SL _| CasingGexB8576538/4 Commmications Processor CP 524 6.2 Connection CP 524/525 PROMEA M (TTY) CP 525/524 PROMEAM +5V_D_, Transmitter ? 7 13 iy +RxD +S fy 7 i | \ Receiver tat | RxD 5s 1 -12V 10 +TxD +E 18 - CO +5V S 6 Transmitter 19 -TxD -E 14 : i \ | \ | Receiver 77 jy Shield -12V CasingGex [ _L. Casing 45B8576538/4 Commmications Processor CP 524 6.3 Connection CP 524/525 - AS 512C (TTY) CP 525/524 AS 512 13), +RxD TxD, }44 \ & Receiver ii i 4 | Transmitter N~ 14); 4 -RxD +1xD | ii2 [+20 mA | 5 +24 | -20 mA 17 foi ae | | +20 mA +24V , 4 -20 mA 18 10 | | 4 TxD RxD ris _L , { | 1 | . \ Transmitter |} | I Receiver 7 19) \ i -TxD +pxD_ | J ia 1} iy Shield vi CasingGex =| | Casing p23 , [244 | 124 | Device 12 | identifier at + 138 - Note: to generate a current loop the AS 512 must be supplied with 24 V via the AMP comectors on the front panel. 46B8576538/5 Communications Processor CP 524 6.4 Connection CP 524/525 ~ PROMEA R (TTY) CP 525/524 PROMEAR 16], +20mA + 24V@ hr 13) J | +RxD Sw Receiver || 14 -RxD +TxD jy [14 [| Transmitter 37 24i{ |2oma -tTxo} {17 LL 12!| |+20ma + 24VCo- tol] [4+TxD SK Transmitter , 191 | |-TxD +PXD 9 i t i 1 ij iver 21 | | -20ma -RxD | fi 4 Receive eZ La Shield 45 CasingGex _[" ~L 6-5 Connection CP 524/525 - Modem N10 (V.24) CP 525/524 ModemN10 Receiver Transmitter Ir 3) RO Ory js A Ate of Transmitter | {1 Receiver > 2i| |mo RD} | FL mit a ay Yi Shield yf 4 -L Casing Gex LL LL AS 4 ews fs 47B8576538/4 Communications Processor CP 524 6.6 Connection CP 524/525 CP 524/525 (V.24) CP 525/524 CP 525/524 Receiver Transmitter _d or 3 TD i \ 2 | Transmitter | ti Receiver 2 RO! fis iT >e ' if {p 7 1 fi? -L Shield Wi ot CasingGex [7 1. Casing Gex 6.7 Connection CP 524/525 - PROMEA R (V.24) CP 525/524 PROMEAR Receiver -_ Transmitter TF 3 a oN 3 fF Pte Transmitter 2 | Receiver >o aii RO; ij8 va 7) Shietd \y' hts CasingGex [- L 48B8576538/4 Communications Processor CP 524 6.8 Connection CP 524/525 - PT 88/PT 89 (TTY/V.24) CP 525/524 PT 88/89 13 ~ +RxD +20mMA ~ $24 : t ae CQD- + 24V Sy Receiver | | i P| 141 jf 4 -RxD +TxD f 18 Transmit 2 , i ; 101 | +TxD +20mA' 10 - CO +24V (Transmitter 19 -TxD +AXxD 9 Receiver 47 Oumo cTs Busy 25 Receiver ao 1 Transmitter iT 3 i xD fi 2 i* } o<f- Transmitter ii Receiver Poo pe ne | ep 7if Lilz + LJ +, V Shield Yo iy + Casing Gex Lf " . _| Casing A ee ee eee eee J Note: The cable is designed for both TTY and V.24 signals. It can therefore be used regardless of the type of interface used in the printer. With the CP 524, make sure that you use the same interface type as in the printer. 49B8576538/4 Communications Processor CP 524 6.9 Connection CP 524 CP 524 (RS422-A or V. 11) CP 524 CP 524 ag fi T re) fh ja iy Pye i | Pid afi (8) RO) i big Transmitter | Receiver 4 RA) TOA) 2 <i " R() 18) 9 q Receiver ; | Transmitter ig e i! si Ligs IY veo io Shield 1 ody f en @--0 . } CasingGex amian wuis Casing Gex Siemens Aktiengeselischaft The repreduction, transmission or use of this Order No.: C79000-88576-C538-05 document or its contents is not permitted Cpr without express written authority, Order trom: Gerdtewerk Karlsruhe Offenders will be liable for damages. All Printed in the Federal Republic of Germany rights, including rights created by patent grant or registration of a utility model or AG 0689 0.5 ABS4En design, are reserved. siemens AG 1988SIEMENS SIMATIC S5 Computer Link with RK 512 Users Guide C79000-B8576-C539-08Contents 1 Functions 1.1 Transmitting Data (SEND Job) 1.2 Fetching Data (FETCH Job) 2 Programming the Functions 2.1 User Memory of the CP 525 2.1.1 Memory Requirements of the Job Block 2.2 Assigning Parameters to the Job Block for the CP 525 2.3 Assigning Parameters to the Interpreter and Procedure 2.4 Parameters for the Handling Blocks 2.5 Example of a Complete Parameter Set 2.6 Job Tables 3 Settings and Start-up Settings on the CP 525 -l Jumper Settings 3.1 3.1.1 3.1.2 Setting Interpreters and Procedures 3.2 Settings on the Partner 3.3 Start-up Routine 3.3.1 Routine Following Power-up 3.3.2 SYNCHRON Job from the CPU 3.3.3 Mode Selector Settings RUN/STOP/PGR 3.3.4 Transferring from the PG 4 How Is Data Transferred? 4.1 Telegram Level 4.1.1 Sending Data 4.1.2 Fetching Data 4.2 Quasi Full Duplex Operation 12 12 13 17 18 21 26 38 38 38 38 38 39 39 39 41 42 45 48 51 54w NVORHODNMP PPE PE VA awunuwuuwwn SSDS SI SI sd AUR WH 8.1 8.2 8.3 UbpoUndE ME whe Procedures Procedure 3964 Procedure Data Transmitting with the 3964 Procedure Receiving with the 3964 Procedure Initialization Conflict Procedure Errors 3964R Procedure Procedure Data Transmitting with the 3964R Procedure Receiving with the 3964R Procedure Initialization Conflict Procedure Errors Multiprocessor Operation Special Jobs Carried out by the CPU PSEUDO READ/WRITE Function Reading the Error Message Area of the SYSTAT Resetting (Clearing) the Error Message Area Reading the Whole SYSTAT Reading the SYSID CP 525: Reading and Writing the Date and Time Error Handling Error Messages for SYSTAT, ANZW and REPTEL Arranged According to the Numbers for ANZW Error Messages for SYSTAT, ANZW and REPTEL Arranged According to the Numbers for SYSTAT Error Messages for SYSTAT and REPTEL Arranged According to the Numbers for REPTEL Time Measurements ~ Processing a DIRECT Job Li 55 55 55 57 59 60 61 63 63 65 67 68 69 71 72 72 81 85 85 87 90 94 100 124 162 176B8576539~-04 Computer Link with RK 512 1 Functions In automation engineering data must often be exchanged - between programmble controllers or - between a programmble controller and a central process com- puter The data exchange can be implemented using the commmications processor CP 525 with its interpreter RK 512 and the procedures 3964 or 3964R. This means that you can link the following programmable control- lers; - the programmable controllers of the SIMATIC S5 U range (115U, 135U, 150U, 1550) with each other - the programmable controllers S5-110S, S5-130w, S5-150A/K, S5-150S (if they are equipped with an AS 512C module) with the PCs, S5-115U, S5-135U, S5-150U and S5 1550 Note that the CP 525 cannot be used with the S5-1350/S processor.B8576539-03 Computer Link with RK 512 The RK 512 interpreter uses the same message format as the interface module AS 512C in SIMATIC S5. The data is exchanged via a point-to-point link as shown in the following diagram. CPU CP 525 PC 1 GPU GP 525 PC 2 The exchange of data can be carried out in two ways as follows: @ Programmable controller PC 1 can transmit data on its own "initiative" to programmable controller PC 2. In this case CPU 1 must call a "SEND job on its "own" CP 525. e PC 1 can fetch data on its own "initiative" from PC 2. In this case CPU 1 must call a FETCH job" on its "own" CP 525. In the same way, PC 2 can also transmit data to or fetch data from PC 1. Remember that per CP interface a maximum of 10 jobs (SEND and FEICH jobs) can be processed "simultaneously". A new job can be started only when one of the 10 jobs has been terminated with or without errors.B8576539-04 Computer Link with RK 512 The interaction during data exchange between programmable con- troller 1 and 2 is shown in the following diagram. PG Ll ______ PC 2 STEP 5 CP 525 CP 525 STEP 5 user user user user program program program program CPU CP 525 GP 525 CPU Proce- >| Proce- dure dure f f V V _ S5- _- S5- Han- Bus Inter- Inter- Bus Han- dling |<===> |preter preter |<=>/| dling blocks blocks i i i u I 1 4 u Job Job Data block block Data Data handling blocks (HDBs) in the STEP 5 user program on the CPU transfer the data from the CPU to the CP 525 and vice-versa. HDBs also initiate the jobs to be executed - a SEND job (send data) or a FETCH job (fetch data). The HDB is assigned a job number under which the corresponding job is stored in the job block on the CP 525. All the jobs together are known as the job block.B8576539-03 Computer Link with RK 512 The job block on the CP 525 contains all specifications regarding the destination or source of the data in the other PC. The data handling block in the CPU contains all the specifi- cations regarding the source or destination of the data in its own PC, To make use of the computer link, you require two programs for each programmable controller as follows: - the STEP 5 user program in the CPU including the HDBs with parameters assigned according to their jobs and ~ the CP 525 user program in the CP 525 including the jobs in the job block and the procedure and interpreter Interpreter: manages the data exchange Procedure: implements the transfer The programming package COM 525 supports you when you are generating the CP 525 user program.B8576539-03 Computer Link with RK 512 1.1 Transmitting Data (SEND Job) The CPU of PC 1 is to send data on its own initiative to the CPU of PC 2 (SEND job). job PG 1 PC 2 CPU CP 525 GP 525 CPU SEND I Proce- Proce- DIRECT N dure >| dure n I lz | I AN A\ [a [| | {i} v __ SEND >|Inter- Inter- RECEIVE ALL ===> | preter preter |=======> | ALL A A {| i lI V Data Job Data source block desti- nation nh = job numberB8576539-03 Computer Link with RK 512 First the HDB SEND DIRECT n (n = job number) is called in the CPU of PC 1. This initiates the call-up of the data from the data source in the CPU of PC 1 by the interpreter of the CP CPC 1). The SEND DIRECT requires the following parameters to be specified: ~ interface number of the CP 525 in PC 1 - the number of the corresponding SEND job on the CP 525 (PC 1) - details of the data source (where the data to be sent is stored in the CPU of PC 1) The data transfer from the CPU to the CP 525 in PC 1 is handled by the HDB SEND ALL. The following parameters are assigned to the SEND job in the job block on the GP 525 of PC 1: - the number of the corresponding SEND DIRECT in the CPU ~ details of the data destination: i.e. where the data is to be stored in the receiver (PC 2) This information is sent to the receiver PC 2 along with the data. No job block is necessary on the CP 525 in PC 2. In the CPU of PC 2, the handling block RECEIVE ALL is called cyclically. This handling block transfers the data received by the CP 525 to the CPU. The RECEIVE ALL is assigned the interface number of the CP 525 plugged into PC 2. (To set the interface number, see the instructions for the CP 525 in this manual).B8576539-03 Computer Link with RK 512 1.2 Fetching Data (FETCH Job) PC 1 is to fetch data on its own initiative from the CPU of Pc 2 (FETCH job).. FETCH job PG 1 PC 2 CPU GP 525 CP 525 CPU FETCH I Proce- |===(1) ===>] Proce- DIRECT N dure | | | {dure n I <=(2) === |r _ Data _ I A N [A [; || lz V V fe > ee Inter- | SEND ALL < preter preter |<======/ ALL {| A A Vv li l Data Job Data destin- block source ation n = job numberB8576539-03 Computer Link with RK 512 The HDB FETCH DIRECT n (n = job number) is called in the CPU of PG 1. It must have the following parameters specified: - interface number of the CP 525 in PC 1 - number of the corresponding FETCH job on CP 525 (PC 1) - information about the data destination (where the data fetched from PC 2 is to be stored in the CPU of PC 1) The FETCH job in the job block on the CP 525 of PC 1 contains information about the location of the data to be fetched from the CPU of PC 2. This information is sent to PC 2 ina request tele- gram (1). No job block is required on the CP 525 of PC 2. The handling block SEND ALL is called cyclically in the CPU of PC 2. This HDB transfers the requested data from the CPU to the CP 525 of PC 2. It is assigned the interface number of the CP 525 in PC 2. Once the requested data (2) is received in the CP 525 of PC 1 it is transferred to the CPU of PC 1. This is performed by the handling block RECEIVE ALL. RECEIVE ALL is only assigned the interface number of this CP 525 and is called up cyclically in the user program. (To set the interface number, see the instruc- tions for the CP 525 in this manual),B8576539-03 Computer Link with RK 512 2 Programming the Functions To use the computer link, you must install two programs as follows: - the STEP 5 user program for the CPU (with handling blocks) - the CP 525 user program for the CP 525 You generate the CP 525 user program using the programming package COM 525. A detailed description of the functions of GOM 525 can be found in the user's guide "Programming package COM 525" in this manual. The STEP 5 user program for the CPU contains the handling block calls. More detailed information concerning the handling blocks in conjunction with the computer link can be found in the descri- ption "Using the handling blocks" in this manual. The next pages provide an overview of the following: ~ the parameters required during programing ~ where these parameters are to be specified (STEP 5 or CPU 525 user program) - the significance of the parameters in a wider context In addition, Section 2.6 contains the job tables that list the v4 permissible combinations of parameters. Use these tables to check whether the transfer you require can be implemented.B8576539-03 Computer Liak with RK 512 When generating the user programs you should proceed as follows: 1. First ask the following questions: ~ with which partners is data to be exchanged? - which device interfaces are the partner devices to be connected to? ~ which data is to be exchanged? - which jobs are required and which handling blocks are needed? 2. Generate the CP 525 user program as follows: ~ assign parameters to the jobs (Section 2.2) - assign parameters to the interpreter and procedure (Section 2.3) - load the job block, interpreter and procedure in the user memory of the CP 525 (RAM or EPROM submodule). PG COM 525 ow Xk} ho ay 4 assign parameters to the jobs assign parameters to the interpreter and procedure i load these in the user memory of the CP 525: either in an EPROM submodule or in a RAM submodule (serial transmission) 10B8576539-03 Computer Link with RK 512 3. Generate the STEP 5 user program for the CPU (Section 2.4) as follows: PG STL FI] F LAD DY] D CSF O71 v assign parameters to the handling blocks i load them in the memory submodule of the CPU: either in an EPROM submodule or in a RAM submodule (serial transmission) 11B8576539-03 Computer Link with RK 512 2.1 User Memory ot the CP 525 You insert either a RAM or an EFROM submodule (see ordering data) in the memory submodule receptacle of the CP 525. The user memory of the CP 525 is divided into two areas: - one area for the interpreter and procedures of the two device interfaces ~ One area for the "actual" user data and their manager 0 Kwords Interpreter and procedure for device interface 1 4 Kwords Interpreter and procedure for device interface 2 8 Kwords available for user data (job block) and their manager up to max. y 1 64 Kwords 2.1.1 Memory Requirements of the Job Block If you operate the computer link on a device interface of the CP, the required job block occupies 1 Kword in the memory module , regardless of how many jobs have been programmed. If the CP is used only for the computer link, a 16 Kword memory submodule is adequate. 12B8576539-06 Computer Link with RK 512 2.2 Assigning Parameters to the Job Block for the CP 525 Using the software package COM 525 you must assign parameters to a job block if your CP 525 is to transmit data to a partner, or fetch data from a partner on its own initiative. A CP is active when it transmits on its own initiative. A CP is passive when it cannot operate on its own initiative; i.e., data can only be sent to it or fetched from it. If a CP is only required to be passive then it needs only an interpreter and procedure (no job block!) in the CP 525 user program. It is assumed throughout this description that a CP is active and its partner passive. The jobs in the job block contain information about the data destination or data source in the partner. A maximm of 189 jobs can be programmed in an active CP 525. When assigning parameters to the job you must specify the following: (1) The job mumber - must match the number specified in the HDB (SEND DIRECT or FETCH DIRECT). The job number can have values ' v4 between 1 and 189. (2) Job type - SEND or FETCH (3) Type of data to be transferred - a SEND job can send data to the following types of destination: data blocks system data absolute addresses extended data blocks 13B8576539-06 Computer Link with RK 512 (4) (3) (6) (7) a FETCH job can fetch data from the following types of source: data blocks flag bytes input bytes output bytes 1/0 bytes timer locations counter locations system data absolute addresses extended data blocks extended I/Os Destination address for SEND or source address for FETCH - limit values depend on the data type. CPU mamber - if a particular CPU is to be addressed by this job, then the range of values is 1 to 4. No specification is made if the partner only has one CPU. DB number - assigned if "data block" or "extended data block" was specified as the type. With a SEND job this is the destination data block, with a FETCH job it is the source data block. Coordination flag (CF) - specified if the source or destination is a data block or an extended data block Notes on coordination flags: In conjunction with the computer link, the term "IPC flag" can be replaced by coordination flag". Using coordination flags you can enable or inhibit the data ex- change between the CPU and CP. 14BBD /653Y9-U3 Computer Liak with RK 512 In the SEND or FETCH telegram the byte and bit number of the coordination flag are transferred to the partner, which then evaluates them. This prevents as yet unprocessed data from being overwritten or read. The partner device then sends a reply message with an error number to the active CP 525. You can write the STEP 5 user program in the CPU of the active CP so that it evaluates the received error number and repeats the SEND or FETCH message later. For more information on coordination flags refer to the section in the instructions for the CP 525 ("Enabling/ disabling IPC flags"). The coordination flags must first be enabled by means of jumpers on the module. In some PCs the coordinaticn flags must be defined as output IPC flags in DB 1. Coordination flags with the link CP 525 ---> AS 512 If the CP 525 sends a telegram that contains not only data but also the byte and bit number of a coordination flag, the AS 512 (as passive partner) sets the corresponding flag to "1" when this message is received. The data is accepted or read. mumber for a coordination flag to the AS 512C, the latter recog- nizes that the flag is already set. The data transfer/reception is disabled. The AS 512C sends a reply telegram with an error number to the active CP. In the active PC an error number is indicated in the condition codeword. If the the HDB is called again (SEND DIRECT or FETCH DIRECT) the telegram is sent again. If the CP 525 sends another telegram with the same byte and bit ca In the passive PC (with the AS 512C) the coordination flag must be reset by the STEP 5 program after the first telegram has been processed or when new data is ready to be fetched. The exchange of data is then once again enabled. 15B8576539-03 Computer Link with RK 512 The range of values of the coordination flags is zs follows: byte number 0 to 223 bit number Oto 7 or no specification Coordination flags with the link CP 525 ---> cp 525 If the CP receives a telegram with the byte and bit number of the coordination flag, it chucks whether the coordination flag with this number is set. If it is, the CP rejects the exchange of data with the active CP by means of a reply telegram with an error number. The data that has been sent is not tranferred to the CPU or is ignored by the CPU. If the coordination flag has already been reset when the telegram is received the data exchange takes place. With the last data transfer between the CPU and CP 525, the byte number of the coordination flag is indicated in the condition codeword of the SEND ALL or RECEIVE ALL. (The number of data transfers depends on the number of items of data transferred and the field length for the data transfer - see parameter (field _Length BLGR for the 'SYNCHRON' HDB). This byte number can be evaluated by the STEP 5 program and the appropriate coordination flag is then set. To allow the coordination flag to be evaluated by the passive CP, the byte number must be in the range between 1 and 223. 16B8576539-04 Computer Link with RK 512 2.3 Assigning Parameters to the Interpreter and Procedure Each CP interface being used requires an interpreter and proce- dure in the CP 525 user memory. For the computer Link these are as follows: - interpreter RK 512 - procedure 3964 or 39648 The interpreter requires no parameters. You must specify the following for the procedure: Data rate 19200 bps (*) 9600 bps 4800 bps 2400 bps 1200 bps 600 bps 300 bps 150 bps em (*) 19200 bps are only allowed if you use the V.24 interface with the CP 525/CP 524 or the RS422-A/485 interface with the CP 524. In this case you can only load and operate one interface with the CP 525. Priority If both devices want to place a telegram on the transmission line simultaneously, one device must back off. The CP with the higher priority transmits its telegram first and the partner with lower priority, transmits its telegram second.. You can select the following: higher priority lower priority 17B8576539-03 Computer Lirk with RK 512 Other parameters The following parameters are fixed for the 3964 and 3964R procedures: : - character length in bits: 8 ~ parity: even - number of stop bits in bits: 1 2.4 Parameters for the Handling Blocks To start a SEND job, you must call the SEND DIREC HDB in the STEP 5 user program. For a FETCH job you call the FETCH DIRECT HDB. The following parameters must be specified: (1) Interface number (SSNR) Every CP (or IP) in the PC is allocated one or more interface numbers. The SSNR is set by means of jumpers on the module. The CP 525 has two interface numbers. The even munber addresses device interface 1; the next higher odd number addresses device interface 2. Range of values: 0 to 255 More details can be found in the instructions for the CP 525 in this manual. (2) Job number (A-NR) Every job (SEND DIRECT/FETCH DIRECT) is assigned a number that must match the number of the corresponding job in the user memory of the CP 525. Range of values: 1 to 189 18B8576539-06 Computer Link with RK 512 (3) Source type (QTYP) with SEND DIRECT or Dest. type (ZTYP) with FETCH DIRECT The following source types can be sent with SEND DIRECT: data blocks DB flag bytes FY input bytes IB output bytes QB I/0 bytes PB timer locations TB counter locations GB system data RS absolute addresses AS extended data blocks DX extended I/0s OB The following destination types are possible when receiving (FETCH DIRECT): data blocks DB system data RS absolute addresses AS extended data blocks DX (4) Data block meber (DBNR) If you selected a data block or an extended data block as the source or destination type, you enter the number of the data block here. Range of values: 3 to 255 (5) Source start address (QANF) with SEND DIRECT or Dest. start address (ZANF) with FETCH DIRECT The range of values permitted depends on the data type. 1) previously PB 2) previously OB (6) Source length (QLAE) with SEND DIRECT or Dest. length (ZLAE) with FETCH DIRECT 19553 /b95Y-US Computer Tink with RK 512 (6) Source length (QLAE) with SEND DIRECT or Dest. length (ZLAE) with FETCH DIRECT You enter the number of items of data to be transferred. Whether this is specified in bytes or words depends on the data type (3); e.g., flags are specified in bytes, data blocks in words. The range of values permissible also depends on the data type and is listed in the job tables in Section 2.6. (7) Other parameters are the condition codeword ANZW and the parameter assignment error byte PAFE. These indicete whether a data transfer was performed sucessfully or whether errors occurred. For more details see the description "Using the han- dling blocks" in this manual. 20B8276539-03 Computer link with RK 512 s 2-5 Example of a Complete Parameter Set Task I: SEND job Ten data words from data block 20 (DB20) starting at data word 10 (DW1O) are to be transferred from PC 1 to PC 2 an be entered in data block 5 (DB5) starting at data word 1 (DW1). Make sure that PC 1 and PC 2 are each equipped with a CP 525, In PC 1 you require the following: - the SEND DIRECT HDB, which triggers the job. It must have the following parameters assigned: SSNR 0 interface number is 0 A-NR 1 job mumber is 1 ANZW Fw12 condition codeword is flag word 12 QTYP DB source is a data block DBNR 20 with number 20 and QANF 10 with the start address 10 QLAE 10 10 data words will be sent PAFE FY11 FY11 is selected for parameter assignment errors ca - the SEND ALL HDB that iransfers the data from the PC to the CP must also be called. It requires the following parameters: SSNR Q interface number is 0 A-NR 0 ALL function is selected ANZW FW16 condition codeword is FW16 PAFE FY19 FY19 is selected for parameter * assignment errors Note: the condition codeword of the ALL job must be different from the ANZW for SEND DIRECT, since other information is written to it. 21B8576539-03 Computer Link with RK 512 Before beginning with the programming read the description "Using the handling blocks" in this manual to find the form in which these parameters must be specified. For the CP in PC 1 you require the following: - one job in the job block job number 1 number as for EDB parameters job SEND send has been selected job type DB dest. is a data block dest. word address 1 with start address 1 CPU number - only one GPU exists DB no. 5 the dest. DB no. is 5 coordination flags - coordination flags are not being used - the interpreter RK 512 and the procedure (e.g., 3964). For the procedure you must set the following: data rate 9600 bps data rate for this example priority low optional 22B8576539-08 Computer Link with RK 512 In PG 2 you require the following: - the RECEIVE AIL HDB, which transfers the data and enters the following in the destination DB: interface number is 0 SSNR 0 job number is 0 A-NR 0 ALL function is selected ANZW FW6 condition codeword is FW 6 PAFE FY4 FY4 is selected for parameter assignment errors For the CP in PC 2 you require the following: - mo job block, as long as no active jobs are called up in PC 2 (SEND DIRECT, FETCH DIRECT). ~ the interpreter RK 512 and the procedure 3964 for this CP. Set the following: data rate 9600 bps data rate for this example priority higher 23B8576539-08 Task II: FETCH job Computer Link with RK 512 Six flag bytes starting at FY7 are to be fetched from PC 2. These bytes are to be written into data block 20 starting at data word 30 in PC 1. A FETCH job is therefore programmed in PC 1. In PC 1 you require the following: - the call for the FETCH DIRECT HDB SSNR A-NR ANZW ZTYP DBNR ZANF ZLAE PAFE FW34 DB 20 30 FY33 to trigger the job: as for task I job number here is 2 condition codes in FW34 destination is a DB with no. 20 and start address 30 fetch 6 bytes = 3 words parameter assignment errors - the RECEIVE ALL HDB to receive the data fetched: SSNR A-NR ANZW PAFE FW27 FY26 interface number is 0 job number is 0 ALL function is selected condition codeword in FW27 parameter assignment errors in FY26 24B8576539-08 Computer Link with RK 512 For the CP in PC 1 you require the following: - the job with the number 2 as follows: job number 2 job FETCH job type flags source byte address 7 CPU no. - DB no. - coordination flags - the interpreter and procedure are available if you carried out task number as for HDB source is the flag area from byte 7 only one CPU present no parameter possible no parameter possible already programmed and I: 9600 bps low data rate priority In PC 2 you require the following: -a ALL HDB as follows, which t its CP: SSNR 0 A-NR 0 ANZW FW40 PAFE FY39 25 ransfers the flag bytes to interface number is 0 job number is 0 ALL function is selected FW40 is selected as ANZW FY39 selected for parameter assignment errorsB8576539-06 Computer Link with RK 512 For the CP in PC 2 you require the following: - no job block, however, interpreter and procedure (if not already available from task I). For the procedure you need the following: data rate 9600 bps priority higher 2.6 Job Tables The following tables contain all the transferable data types and their parameter assignments in the HDB and in the job block. Specifications regarding the addresses depend on the PC and are not always the same for different types. This is particularly important with absolute addresses. Also refer to the documentation for your specific PC. Because of the wide variety of parameters, each table is spread over two pages. Remember that the two tables are, in fact, one. 1. Transmit data: SEND As the source, all data types stored on the partner in a destination DB or DX (exception AS/RS) can be used. The parameter QLAE (source length) represents a number of bytes, if the source area is organised in bytes; if not, it represents a number of words. If 0 is specified there will be no exchange of tele- grams. Be careful with odd numbers of bytes; since the destination area is a DB or DK, only full words can be stored there. If the partner is a CP 525, it writes Os to the right-hand data byte (DR) if it receives an odd number of bytes. 26B85 /6539-03 Computer Iink with RK 512 Notes on the table On the right-hand side there are three columns with specifica- tions for the telegram header. These specifications need to be taken into account only if you are using a device of a different make as the partner, and you are implementing the commmications software yourself; or if you wish to monitor the data exchange on the line with an interfare test device (FOXPG). The specifica- tions refer to the contents of bytes 3 to 8 in the header of the SEND telegram. Explanation of the abbreviations: parameter assignment of .he HDB QTYP source type DBNR data block number QANF = source start address QLAE source Length ot Hl parameter assignment in COM 525 Z-Typ = destination type Z-DB = data block number of the destination 2-Adr = destination start address CF-poss. = coordination flags possible? vA header, bytes = telegram header of the data transmission on the line 27B8576539-08 Computer Link with RK 512 Source, Dest., Param. assignment of HDB in PC 1 Send from to PC 2 PC 1 QTYP DBNR QANF QLAE Data block Data block DB 3-255 | 0-2047 1-2048 Ext. DB Data block DX 3-255 | 0-2047 1-2048 Flags Data block FY irrel.| 0-255 1-256 Inputs Data block IB irrel.| 0-127 1-128 Outputs Data block QB irrel.{ 0-127 1-128 Counters 115U| Data block cB irrel.]| 0-127 1-128 Counters 135U/ Data block CB irrel.| 0-127 1-128 Counters 150U] Data block CB irrel.| 0-255 1-256 Timers 115U | Data block TB irrel. 0-127 1-128 Timers 135U | Data block TB irrel.| 0-127 1-128 Timers 150U | Data block TB irrel.| 0-255 1-256 I/Os Data block PY irrel.| 0-255 1-256 Sy-Adr.135U | Sys. addr. RS irrel.| 0-255 1-256 Sy-Adr.150U | Sys. addr. RS irrel. 0-511 1-512 Abs. addr. Abs. addr. AS irrel.| 0-+32767} 1-32767 -32768 ext. I/Os Data block OB irrel.| 0-255 1-256 only for PC 150U 28B8576539-03 Computer Link with RK 512 Param. assign. in COM 525 in PC 1H Telegram header, bytes 3/4 5/6 7/8 Z-Typ | Z-DB | Z-Adr | CF. poss. comm. {Z-DB/Z-Adr|Num. in DB 3-255 | 0-255 yes ++ AD DB/DW Words DB 3-255 | 0-255 yes ry =AX DB/DW Words DB 3-255 | 0-255 yes HH 6AM DB/DW Bytes DB 3-255 | 0-255 yes + AE DB/DW Bytes DB 3-255 | 0-255 yes Ht 6 AA DB/DW Bytes DB 3-255 | 0-255 yes H+ 6 AZ DB/DW Words DB 3-255 | 0-255 yes ++ 6 AZ DB/DW Words DB 3-255 | 0-255 yes H+ 6 AZ DB/DW Words DB 3-255 }| 0-255 yes ++ AT DB/DW Words DB 3-255 | 0-255 yes ++ 6O AT. DB/DW Words DB 3-255 | 0-255 yes ++ AT DB/DW Words DB 3-255 | 0-255 yes ++ AP DB/DW Bytes RS | 0-255 no 7 AB Address Words RS | 0-511 |. no +} AB | Address Words AS |0-65535 no H+} 6 AS Address Words DB 3-255 | 0-255 yes rt 6=6AQ DB/DW Byte 29B8576539-06 Computer Link with RK 512 Source, Dest., Param. assignment of HDB in PC 1 Send from to PG 2 Pol QTyP DBNR QANF QLAE Data block Ext. DB DB 3-255 | 0-2047 1-2048 Ext. DB Ext. DB DX 3-255 | 0-2047 1-2048 Flags Ext. DB FY irrel.]| 0-255 1-256 Inputs Ext. DB IB irrel.| 0-127 1-128 Outputs Ext. DB QB irrel.] 0-127 1-128 Counters 115U; Ext. DB cB irrel.| 0-127 1-128 Counters 135U] Ext. DB cB irrel.} 0-127 1-128 Counters 1500} Ext. DB CB irrel.} 0-255 1-256 Timers 115U Ext. DB TB irrel.| 0-127 1-128 Timers 135U Ext. DB TB irrel.| 0-127 1-128 Timers 1500 Ext. DB TB irrel.| 0-255 1-256 I/Os Ext. DB PB irrel.| 0-255 1-256 ext. 1/0s Ext. DB OB irrel.| 0-255 1-256 only for PC 1500 30B8576539-06 Computer Link with RK 512 Param. assign. in COM 525 in PC 1} Telegram header, bytes 3/4 5/6 7/8 Z-Typ | Z-DB Z-Adr | CF. poss.}} comm. |Z-DB/Z-Adr|Num. in DX 3-255 | 0-255 yes ++ OD DX/DW Words DX 3-255 | 0-255 yes +t =6OX DX/DW Words DX 3-255 | 0-255 yes ++ OM DX/DW Bytes Dx 3-255 | 0-255 yes Lt OE DX/DW Bytes DX 3-255 | 0-255 yes ++ 600A DX/DW Bytes DX 3-255 | 0-255 yes H+ OZ DX/DW Words DX 3-255 | 0-255 yes Ht OZ DX/DW Words DX 3-255 | 0-255 yes H+ |Z DX/DW Words Dx 3-255 | 0-255 yes ry OT DX/DW Words DX 3-255 | 0-255 yes ++ OT DX/DW Words DX 3-255 | 0-255 yes ++ 6OOT DX/DW Words DX 3-255 | 0-255 yes ++ =6OP DX/DW Bytes DX 3-255 | 0-255 yes ++ = 0Q DX/DW Byte 31B8576539-06 Computer Link with RK 512 32B8576539-06 Computer Link with RK 512 2. Fetch data: FETCH All data types can be specified as the source in the partner PC. The destination in the HDB can only be a data block or an extended data block (exception RS/AS). The destination length (ZLAE) can be specified only in words. If, for example, 5 input bytes are to be fetched, "3" = three words = six bytes must be specified in the HDB. If 0 is specified there is no telegram exchange. Notes on the table On the right-hand side there are three columns with specifica- tions for the telegram header. These specifications need to be taken into accowt only if you are using a device of a different make as the partner, and you are implementing the communications software yourself; or if you wish to monitor the data exchange on the line with an interface test device (FOXPG). The specifica- tions refer to the contents of bytes 3 to 8 in the header of the FETCH telegram. Explanation of the abbreviations: parameter assignment of the HDB ZTYP = destination type DBNR = data block number ZANE = destination start address ZLAE = destination length parameter assignment in COM 525 Q-Typ = source type Q-DB = data block number of the source Q-Adr = source start address CF-poss. = coordination flags possible? telegram header of the data header, bytes transmission on the line 33B8576539-03 Computer Link with RK 512 Source: Dest. : Param. assignment in HDB in PC 1 fetch from in PC 1 PG 2 ZTYP DBNR ZANF ZLAE Data block Data block DB 3-255 | 0-2047 1-2048 Ext. DB Data block DB 3-255 | 0-2047 1-2048 Flags Data block DB 3-255 | 0-2047 1-128 Inputs Data block DB 3-255 | 0-2047 1-64 Outputs Data block DB 3-255 | 0-2047 1-64 Couters 1150} Data block DB 3-255 | 0-2047 1-128 Counters 1350] Data block DB 3-255 | 0-2047 1-128 Counters 150U] Data block DB 3-255 | 0-2047 1-256 Timers 115U | Data block DB 3-255 | 0-2047 1-128 Timers 135U | Data block DB 3-255 | 0-2047 1-128 Timers 150U | Data block DB 3-255 | 0-2047 1-256 1/0s Data block DB 3-255 | 0-2047 1-128 Sys .Ad.135U | Sys. addr. RS irrel | 0-255 1-256 Sys.Ad.150U | Sys. addr. RS irrel.| 0-511 1-512 Abs. addr. Abs. addr. 4S irrel.] 0-+32767} 1-32767 115 U -32768 Abs. addr. Abs. addr. AS irrel.| 0-+32767| 1-32767 1350/1500 ~32768 ext. I/Os Data block DB 3-255 | 0-2047 1-128 only for S5-1500 34B8576539-03 Computer Link with RK 512 Param. assign. in COM 525 in PC 1}} Telegram header, bytes Q-Typ Q-DB Q-Adr |CF poss.}4 3/4 5/6 7/8 ++ Comm. 1Q-DB/Q-Adr|Num. in Data bl.} 0-255 | 0-255 yes +} =6ED DB/DW Words Ext. DB | 0-255 | 0-255 yes f} EX DX/DW Words Flag | 0-254 no +} EM |byte addr.! Bytes Input | 0-126 no ++ EE [byte addr.| Bytes Output | 0-126 no ++ EA J|byte addr.| Bytes Counter | | 0-127 no + EZ {Couter no| Words Counter {| | 0-127 no +} EZ {Counter no} Words Counter {| | 0-255 no r+ EZ {Counter no] Words Timer | 0-127 no 4 ET Timer no.{ Words Timer | 0-127 no +} =6OET Timer no.| Words Timer | 0-255 no +} ET Timer no.| Words r/o | 0-254 no ++ EP I/O addx.}| Bytes Sys. dat.| | 0-255 no ++ EB Sys.addr.| Words Sys. dat.}| | 0-511 no + =6CEB Sys.addr.| Words Abs. addr| ]0-65534] no ++ ES Abs.addr.] Words Abs. addr} [0-65535]| no ++ =6ES Abs.addr.| Words ext. I/O | ~ | 0-254 no ++ 6EQ I/O addr.| Byte 35B8576539-06 Computer Link with RK 512 Source: Dest.: Param. assignment in HDB in PC 1 fetch from in PC 1 PG 2 ZTYP DBNR ZANF ZLAE Data block Ext. DB DX 3-255 | 0-2047 1-2048 Ext. DB Ext. DB DX 3-255 | 0-2047 1-2048 Flags Ext. DB DX 3-255 | 0-2047 1-128 Inputs Ext. DB DX 3-255 | 0-2047 1-64 Outputs Ext. DB DX 3-255 | 0-2047 1-64 Counters 1150} Ext. DB DX 3-255 | 0-2047 1-128 Counters 135U] Ext. DB DX 3-255 | 0-2047 1-128 Counters 150U] Ext. DB DX 3-255 | 0-2047 1-256 Timers 115U Ext. DB DX 3-255 | 0-2047 1-128 Timers 1350 Ext. DB Dx 3-255 | 0-2047 1-128 Timers 1500 Ext. DB DX 3-255 | 0-2047 1-256 I/os Ext. DB DX 3-255 | 0-2047 1-128 ext. I/Os Ext. DB DX 3-255 | 0-2047 1-128 only for 5-1500 36B8576539-06 Computer Link with RK 512 Param. assign. in COM 525 in PC 1/4 Telegram header, bytes Q-Typ Q-DB Q-Adr [CF poss. 3/4 5/6 7/8 4 Conm. {Q-DB/Q-Adr Num. in Data bl.] 0-255 | 0-255 yes ++ ED DB/DW Words Ext. DB | 0-255 | 0-255 yes +} EX DX/DW Words Flag | 0-254 no ry EM |byte addr.| Bytes Input | 0-126 no +] EE [byte addr.| Bytes Output w | 0-126 no Ht EA |byte addr.j Bytes Counter | ~ | 0-127 no ++ EZ [Counter no] Words Counter | - | 0-127 no 4 EZ {Counter no! Words Gounter | - | 0-255 no r+} EZ {Counter no] Words Timer | 0-127 no ++ 6 ET Timer no.j Words Timer | 0-127 no +} =ET Timer no.| Words Timer | 0-255 no ++ 6OET Timer no.| Words 1/o | 0-254 no H+ 6EP I/O addr.| Bytes ext. I/0 | ~ | 0-254 no 4 =6EQ I/O addr.| Byte 37B8576539-03 Computer Link with the RK 512 3 Settings and Start-up Chapter 3 contains information about the following: ~ settings on the CP 525 - settings on the partner - start-up routines 3.1 Settings on the CP 525 3.1.1 Jumper Settings As described in the instructions for the CP 525 in this manual, you must set jumpers on the CP 525 (to assign interface numbers and enable the interprocessor commmication (IPC) flags). No jumper settings are required for interpreters and procedures. 3.1.2 Setting Interpreters and Procedures No settings are required on the interpreter RK 512; it is simply loaded in the CP 525. You set the data rate, transmission format and priority for the procedure when programming the CP 525 user program with COM 525. The permissible values can be found in Section 2.3. 3.2 Settings on the Partner If the partner is also a CP 525 the settings are as described in Section 3.1. 38B8576539-03 Computer Link with the RK 512 If your data exchange is performed with an AS 512C interface module, you must set the required priority and data rate (see instructions AS 512C). If the partner is a PROMEA or a DUST 3964 the settings can also be found in the corresponding instructions. 3.3 Start-up Routine 3.3.1 Routine Following Power-up After you switch on the power supply the two LEDs on the front panel of the CP 525 light up. The CP 525 now checks the following: - the RAM and EPROM are functional - the interpreter and procedure are present and complete in the memory submodule Following the start-up phase which takes approximately two seconds, the LEDs of the loaded interfaces go off. If the selector is switched to STOP/PGR or a hardware error has been recognized the LEDs remain lit. Following the start-up phase, the CP 525 expects the SYNCHRON job from the CPU. 3.3.2 SYNCHRON Job from the CPU The SYNCHRON job is initiated after the start-up phase The SYNCHRON HDB is required for handling the SEND, FETCH, RECEIVE jobs so that the length of the fields for the data transfer between the CPU and CP 525 is established. The SYNCHRON HDB is usually called in the STEP 5 user program in organization blocks 0B20, OB21 and OB22. 39B8576539-03 Computer Link with the RK 512 When the SYNCHRON job runs without errors, the CP is ready to process jobs (SEND, FETCH, RECEIVE) from the CPU and from the partner. Possible reactions before SYNCHRON runs are as follows: - the partner sends a telegram before the SYNCHRON job has run; the CP sends a reply telegram containing the error number 24H. 4FH is entered in the error message area of the SYSTAT. Jobs sent from the CPU (except SYNCHRON) before SYNCHRON has run are handled as follows: ~ they are rejected with "not ready" (error message number 81H in the PAFE byte of the corresponding job). A new SYNCHRON job is received by a functional interface: (e.g., the reset switch on the CPU has been pressed) If a partner job is being processed it is be aborted with a reply telegram containing the error number 2AH. The corresponding error number in the error message area of the SYSTAT is 4FH. Partner jobs are then ignored until the CP 525 has gone through its cold restart routine. If a PC job is being processed, it is terminated with the error number 7H in the condition codeword. The error number 16H is entered in the error area of the SYSTAT. If SYNCHRON runs without errors, the job statuses (and therefore the condition codewords) of all jobs are cleared. The error number 7H, is therefore no longer visible. The entries in SYSTAT are retained. If SYNCHRON runs with errors, all the PC jobs set to "running" during the cold restart phase are also terminated with the error number 7H. (16H is again entered in SYSTAT). New PC jobs (except for SYNCHRON) are then blocked by the "not ready" message (number 81H in the PAFE byte of the corresponding job). 40B8576539-03 Computer Link with the RK 512 Note: Aborting a PC job by means of SYNCHRON can also cause a further error status. Reason: if a job is stopped immediately, this fact cannot be signalled to the partner. The partner still expects follow-on telegrams connected with the current job. It therefore interprets the first telegram following SYNCHRON as a follow-on telegram. The partner, however, recognizes that it is not a follow-on telegram associated with the current job and answers with a reply telegram with the number 36H. This causes the first job following the SYNCHRON to be aborted with the error number CH in the condition codeword. The number 37H is entered in SYSTAT. 3.3.3 Mode Selector Settings RUN/STOP/PGR The settings of the mode selector on the front panel of the CP 525 are as follows: o RON from the partner (if a SYNCHRON job was performed without errors). The RK 512 interpreter processes jobs arriving from the CPU and The LEDs of the loaded interfaces on the front panel of the CP 525 are no longer lit. STOP or PGR These settings are identical. They are used to stop the transmis- sion of data on the serial transmission line. Any jobs arriving are rejected with an error message. - PG jobs (SEND/FETCH) are terminated with the error number CH in the condition codeword. The error number 27H is written in SYSTAT. - Partner jobs are rejected with a reply telegram containing the error number 2AH. The number 4EH is entered in SYSTAT. 41B8576539-03 Computer Link with the RK 512 Switching the mode selector from RUN to STOP/PGR If a job is currently being executed it will be completed, i.e., without an error message! Depending on the number of items of data to be transmitted, it may take some time before the STOP/PGR state is reached. This state is shown by the LEDs on the front panel. Switching the mode selector from STOP/PGR to BUN The interpreter once again begins processing jobs. The LED on the front panel goes off (only if the interpreter and procedure are loaded). The CP 525 does not go through a cold restart when the mode selector position is changed. Exception If part or all of the interface has just been loaded or reloaded (transfer from PG) the interface requires a cold restart. In this case, switching the selector position from STOP/PGR to RUN brings about a cold restart, or you can press the key "cold restart" on the PG. The selector on the PC must be set to RUN. 3.3.4 Transferring from the PG If the transfer of the interpreter or procedure or job block is initiated at the PG, the software of the CP 525 goes to the wait state. In the wait state the LED of the corresponding interface is lit on the front panel. The transfer is started only when the program to be transferred is different from the program already loaded in the CP 525. For this reason the PG first reads the program in the CP and compares the two programs byte by byte. The position of the mode selector is irrelevant for this transfer. 42B8576539-03 Computer Link with the RK 512 Before the software of the CP 525 goes to the wait status, the job currently being processed by the partner and CFU is completed without an error message. Depending on the number of items of data to be transmitted, it may therefore take some time before the wait status is actually adopted. During the wait status no jobs sent by the partner (partner jobs) can be processed. The procedure does not react to charac- ters arriving via the serial interface. During the wait status the LEDs on the front panel are lit. During the wait status the CP 525 also rejects any jobs from its own CPU (PC jobs), instead "overload" is indicated. This is recognized by the error number 91H in the PAFE byte of the job affected. In rare cases, a PC job might be completed (terminated with error) before the PAFE error message (number 6H in the condition codeword and 11H in SYSTAT). In this case the PC was unable to recognize the overload early enough. Following the transfer, the software remains in the wait status until you initiate a cold restart on the interface, either with the cold restart" key on the PG, or by switching the mode selec- tor on the CP from STOP/PGR to RUN. Following the cold restart the LEDs on the front panel go off if the transferred program is correct and complete. Following the vA transfer, a SYNCHRON job is no longer required. 43B8576539-04 Computer Link with the RK 512 4 How is Data Transferred? The data transfer between the partners takes place on the following three levels: 1, Telegram level The interpreters of the two CP 525s exchange data in the form of fixed telegrams. The interpreter of the CP 525 (1) sends the interpreter of the CP 525 (2) a command telegram. CP 525 (2) answers with a reply telegram. 2. Procedure level The telegrams are changed into a particular format and integrated into the handshaking. 3. Hardware level. The hardware level covers the physical conditions of the data transfer. The CP 525/CP 524 can operate either with TTY (current loop 20 mA) or with a voltage level V.24. The front connectors are designed for both types of signal. In addition, the RS422- 4/485 module can be used in the CP 524. CP 525 (1) CP 525 (2) Data Data Telegram level Interpreter Interpreter | | Procedure level Procedure Procedure | | Hardware level V.24/TTY V.24/TTYB8576539-03 Computer Link with the RK 512 4.1 Telegram Level The following sections provide detailed information about the telegram level. The various telegrams are defined as follows: CP 525 (1) sends a command telegram to CP 525 (2). CP 525 (2) sends a reply telegram to CP 525 (1). Command telegrams are either telegrams (send data) or FETCH telegrams (fetch data). With SEND telegrams the passive partner sends a reply telegram without data, With FETCH telegrams the passive partner sends a reply telegram with data. If the volume of data exceeds 128 bytes then a follow-on telepram is sent. 45B8576539-06 Computer Link with RK 512 Structure and contents of a command telegram (SEND telepram/FETCH telegram A SEND telegram consists of a telegram header and data. A FEICH telegram consists only of the telegram header. The telegram header is made up of 10 bytes and contains (in a SEND telegram) details of the data destination; (in a FETCH telegram) details of the data source. Byte 1 2 3 4 5 6 7 8 9 10 high low [high low 00H | OOH (FFH) command fdest./source| number CPU no. /CF Significance of the bytes: 1 : telegram identifier (00H or FFH with foll. com. tels) 2 : telegram identifier (00H) 3 : command, SEND ('A'tor O) or FETCH ('E') 4 ; command type, i.e. type of data to be transferred 'D' = data block 'X' = extended DB E* = input bytes A' = output bytes 'M' = flag bytes 'P' = 1/0 bytes 'Z' = counter locations 'T = timer locations 'S' = absolute addresses 'B' = system addresses 'Q' = extended I/Os 5 and 6: destination address for SEND or source address for FETCH, e.g.: byte 5 = DB no. and byte 6 = DW no. 7 and 8: number of pieces of information data to be transferred, depending on the type in bytes or in words 9: byte number of the coordination flag. If no CF is specified, this contains FFH 10: bits 0 to 3: bit number of the coordination flag (CF) If no CF is specified, FH is entered bits 4 to 7: CPU number, a number from 1 to 4. If no GPU number is specified, but rather a coordina- tion flag, this contains 0H. If no CPU no. and no CF is specified, byte 10 contains FFH. In both cases all GPUs are possible at the partner. 46B8576539-03 Computer Link with RK 512 The letters specified in bytes 3 and 4 are ASCII characters. The telegram header of the follow-on command telegram includes only bytes 1 to 4. After the command telegram is transferred, the interpreter ex- pects a reply telegram from the partner within the monitoring time. The length of the monitoring time depends on the data rate, i.e. the baud rate. Table of monitoring times in the CP 525: 19200 - 1200 bps = approx. 5 seconds 600 bps = approx. 7 " 300 bps = approx. 10 150 bps = approx. 15 110 bps = approx. 20 Tolerance: +/- 500 ms Structure and contents of the reply telegram The reply telegram consists of four bytes and contains informa- tion about the processing of the job. Byte 1 2 3 4 OOH / FFH 00H OOH error number Significance of the bytes is as follows: 1: telegram identifier (00H or FFH for follow-on reply telegrams) 2: telegram identifier (00H) 3: contains 00H 4: error number of the partner (see Chapter 8, Error handling). 47B8576539-03 Computer Link with RK 512 4.1.1 Sending Data job: CP 525 (1) sends data to GP 525 (2). CP 525 (1) CP 525 (2) interpreter <=> procedure procedure <=> interpreter telegram > (telegram header + data) <= Reply telegram without data follow-on telera => <== follow-on reply telegram without data Follow-on SEND telegrams and follow-on reply telegrams are sent when the volume of information data exceeds 128 bytes. 48B8576539-03 Sequence of events for a SEND telegram: CP 525 (1) STX <- DLE lst byte 2nd byte 3rd byte 4th byte 5th byte 6th byte 7th byte 8th byte 9th byte 10th byte 1lth byte 12th byte " telegram header data Xth byte DLE EK <_ DLE <- STX DLE < lst byte < 2nd byte <. 3rd byte < 4th byte < DLE < ETX DLE reply telegram Computer Link with RK 512 CP 525 (2) 02H > 10H 00H _ 00H _> 41H _ 44H __> OAH > 01H > 00H _> 32H ___ FFH (byte) > FFH (bit) -> _> > > 10H _> 03H > 10H - 02H 10H > OOH _ OOH OOH _ 00H _ 10H 03H 10H > start character pos. acknowl. SEND command data block type dest. e.g.: DB1O DW1 mumber " e.g.: no CF all CPUs lst data byte 2nd data byte " w 50 DW n w w " nth data byte end identifier Ui Lid pos. acknowl. within 5 sec start character pos. acknowl. error number end identifier pos. acknowl. The characters marked * are added to the data field with the telegram header during the transfer by the 3964 procedure. 49B8576539-03 Computer Link with RK 512 The telegram exchange for a SEND telegram without errors and with a length less than 129 bytes is completed (the fourth byte in the reply telegram does not contain an error number). Follow-on teleprans A follow-on SEND telegram is started if the volume of data to be sent exceeds 128 bytes. The sequence of events corresponds to the SEND telegram. cP 525 (1) CP 525 (2) STX 02H *-> start character < DLE 10H *- pos.acknowl. ___ lst byte FFH > follow-on tel.id. follow-on 2nd byte 00H > tele. header 3rd byte 41H > command: SEND 4th byte 44H > type: data block - 5th byte > 129th data byte - 6th byte > 130th data byte data ee ti > " wt eee Uf > ty " Xth byte > nth data byte DLE 10H *> end identifier ER 03H > " " < DIE 10H * pos. acknowl. within 5 sec < STK 02H % start character DIE 10H *> pos. acknowl. __. < lst byte FFH fol. reptel id. follow-on <- 2nd byte 00H reptel < 3rd byte 00H < 4th byte 00H error message < DIE 10H * end identifier <- EIX 03H " " DLE 10H *> pos. acknowl. Another follow-on SEND telegram is started if there are more than 256 bytes to be transferred. 50B8576539-03 Computer Link with RK 512 4.1.2 Fetching Data FETCH job: CP 525 (1) requests data from CP 525 (2). CP 525 (1) ; CP 525 (2) interpreter <=> procedure procedure <=> interpreter (telegram header) < Reply telegram with data if error no data Follow-on FETCH telerraa > < Follow-on reply telegram with data == if error no data Follow-on FETCH telegrams and follow-on reply telegrams with data are sent only if the volume of information data exceeds 128 bytes. vd If there is an error number # 0 in the 4th byte of the reply telegram, then no data will be added. 51B8576539-03 Computer Link with RK 512 Sequence of events for a FETCH telegram: (request telegram) GP 525 (1) STIX <- DIE lst byte 2nd byte telegram 3rd byte header 4th byte 5th byte 6th byte 7th byte 8th byte 9th byte 10th byte DLE EIX < DIE < Sx ~ DIE < Ist byte reply < 2nd byte telegram <. 3rd byte < 4th byte < 5th byte < 6th byte < 7th byte data " " < Xth byte < DIE < ETX DLE 02H 10H 00H 00H 45H 44H 64H 64H 00H 32H OAH 17H 10H 03H 10H 02H 10H OOH OOH OOH 00H 10H 03H 10H CP 525 (2) *> start character *% pos. acknowl. > _ > command: FETCH > type: data block > source: DB1OO " DWLOO > number: " 50 DW (byte) ~> CF = F 10.7 (bit) only CPU 1 *> end identifier > 7 vw ___ _ *. start character *->pos. acknowl. error number lst data byte 2nd data byte 3rd data byte A " HTT wt " " Ld nth data byte *-- end identifier x *%>pos. acknowl. This is the sequence of events for a FETCH telegram without errors and with a length of less than 129 bytes. 52B8576539-03 Gomputer Link with RK 512 If more than 128 bytes are requested, these are automatically fetched in one or more follow-on telegrams. Follow-on FEICH telegram with follow-on reply telegram: follow-on tele. header follow-on reptel data GP 525 (1) SIX <- DIE lst byte 2nd byte - 3rd byte 4th byte DLE EIX <- DIE < STIX DIE < lst byte < 2nd byte < 3rd byte <. 4th byte < 5th byte <- 6th byte " " " < Xth byte < DLE < ETX DLE 02H 10H 00H 45H 44H 10H 03H 10H 02H 10H 00H 00H 00H 10H 03H 10H CP 525 (2) *> start character * pos. acknowl. > fol. on tele. id. _> > command: FETCH > type: data block *%> end identifier > * pos. acknowl. * start character *-> pos. acknowl. fol. rep. id. error number 129th data byte 130th data byte tt ww fil w " Li nth data byte * end identifier * w " *> pos. acknowl. Another follow-on FETCH telegram is started if the volume of information data exceeds 256 bytes. 53B8576539-03 Computer Link with RK 512 4.2 Quasi Full Duplex Operation Full duplex means that telegrams can normally be sent at any time, except in the following situation: - CP 525 (1) must not send information data, when CP 525 (2) is sending information data. - GP 525 (1) must wait until the telegram is completed with <DLE><ETX> from CP 525 (2) and <DLE from CP 525 (1). Under certain circumstances, (if both CPs wish to send), a SEND telegram can be transferred by the partner before the reply telegram; for example, if a SEND telegram from the partner has been entered in the output buffer of CP 525 (1) before the reply telegram. In the following example, the follow-on reply telegram (*) for the first SEND telegram is sent only after the telegram of the partner. Example of a possible telegram exchange: CP 525 (1) CP 525 (2) SEND telegram < reply telegram ist follow-on SEND telegram > <== SEND telegram of partner < lst follow-on reply telegram === (%) 2nd follow-on SEND telegram ===> < 2nd follow-on reply telegram === 54B8576539-03 Computer Link with the RK 512 5 Procedures Section 5 contains information about the procedures 3964 and 3964R. 5.1 Procedure 3964 5.1.1 Procedure Data The procedure 3964 controls the flow of data between your pro- grammable controller and the partner, e.g., a central process com-puter, another CP 525 or an AS 512C. In the CP 525, the interpreter transfers the data to be sent into output buffers for the procedure. The procedure sends this data along with the transmission protocol 3964 to the partner; if necessary repeats the transmission, and signals non-recoverable errors to the in- terpreter. Data from the partner are stored in input buffers. If the data is received without errors, it is transferred to the interpreter for further processing. The 3964 procedure is an asynchronous, bit serial transfer proce- dure. The transmission rate both sending and receiving must be vA the same on the CP 525 and on the partner (asynchronous because there are no timing circuits between the two devices). Control and information characters are transmitted on the link. To ensure that every character is recognized by the receiver and to allow the transmission to be checked for errors, the charac- ters are encapsulated by other bits. 55B8576539-04 Computer Link with the RK 512 The order of the bits is as follows: SA } IO | Il | I2 | 13 | 14 | 15 | r6 | 17 | PA | So SA = start bit I* = information bit no. PA = parity bit SO = stop bit The control characters for the 3964 procedure are taken from the DIN standard 66003 for the 7-bit code. However, the character length used is 8-bit (bit 7 = 0). There is no code prescribed for the information characters (code transparency). You can set the following procedure parameters when writing the CP 525 user program with COM 525: Data rate The speed of the data transmission is specified in bps. You can select the following values: 19200 bps * 9600 bps 4800 bps 2400 bps 1200 bps 600 bps 300 bps 150 bps 110 bps (*) 19200 bps are only allowed if you use the V.24 interface with the CP 525/CP 524 or the RS422-A/485 interface with the CP 524. In this case you can only load and operate ome interface with the CP 525 since the maximm sum of the data rates is also 19200 bps. 56B8576539-03 Computer Link with the RK 512 o Priority To resolve initialization conflicts, you can set the priority of the CP 525. At the partner the opposite priority must be set. You can choose between the following: higher priority lower priority The following are fixed for the 3964 procedure: character length: 8 bits number of stop bits: 1 parity bit, i.e., checking for even parity 5.1.2 Transmitting with the 3964 Procedure To establish the link, the 3964 procedure sends the control character STX. If the partner replies within the time allowed of 550 ms (i.e., no QVZ = timeout) the procedure starts the trans- mission. If the partner answers with NAK, any other character (except DLE) or if there is a timeout, then the attempt to estab- lish a link has failed. After a total of six unsuccessful attempts, the procedure gives up, signals the interpreter that ri there is an error establishing the link, and sends the character NAK to the partner. If the link is successfully established, the information data in the current output buffer is sent to the partner at the selected data rate. The partner monitors the time between the characters as it receives them. The time between two characters must not exceed the character delay time of 220 ms (ZVZ = character time- out). Each DLE character found in the buffer is sent as two DLE charac- ters (DLE doubling), i.e., the data (10H) is sent twice. 57B8576539-03 Computer Link with the RK 512 After sending the contents of the buffer, the procedure adds the characters DLE and EIX as end identifier and waits for an acknow- ledgement. If the partner sends the character DLE within the time allowed (QVZ), the data field was received without errors. If the partner replies with NAK, any other character (except DLE), a corrupted character, or if there is a timeout, the procedure begins again with the link establishment STX. After a total of six unsuccessful attempts to send the data field, the procedure breaks off the attempt, signals the error to the interpreter and sends NAK to the partner. If, while data is being transmitted, the partner sends the char- acter NAK, the procedure breaks off the field and repeats it as previously described. If any other character is received, the procedure waits for the character delay time (ZVZ) to elapse and then sends NAK to reset the partner. Then the procedure begins the transmission again with the link establishment STx. Example of a data exchange without errors: CP 525 Partner procedure 3964 (e.g. AS 512 C) STX > < DLE lst character > . > > . > nth character > DLE > EX - > < DLE 58B8576539-03 Computer Link with the RK 512 5.1.3 Receiving with the 3964 Procedure In the idle state, i.e., when there is no send job to be process- ed, the 3964 procedure waits for the link to be established by the partner. If the procedure receives any character (except STX) while in the idle state, it waits until the character delay time (ZVZ) has elapsed and then sends a NAK character. The error is signalled to the interpreter. If the procedure receives the character STK and if it has an empty input buffer available, it answers with DLE. The characters then received are entered in the input buffer. If two DLE charac- ters are received in succession, only one DLE character is en- tered in the input buffer. If the input buffer is full before the partner has started to terminate the link, the full buffer is transferred to the interpreter and the next characters arriving are entered in the second input buffer. After each character received, the procedure waits for the next character to arrive within the character delay time. If there is a character timeout, the NAK character is sent to the partner and the error signalled to the interpreter. If the procedure recognizes the character sequence DLE ETX, it stops receiving and sends DIE to the partner to indicate that the field was received without errors (or NAK with errors). The pro- cedure transfers the contents of the input buffer to the inter- preter and returns to the idle state. If there is no empty input buffer available when the link is established with STX, a waiting time of 400 ms is started. If, after this time has elapsed, there is still no empty input buf- fer, the error is signalled to the interpreter. The procedure sends a NAK character and returns to the idle state. If an input buffer becomes available, the procedure sends the DLE character and receives the data as described above. 59B8576539-03 Computer Link with the RK 512 If transmission errors occur during the reception (characters lost, frame error, parity error), reception is continued until the link is terminated and then NAK is sent to the partner. Then a repetition is expected. If the field camot be received without errors after six attempts, or the repetition or repetitions by the partner do not take place within a waiting time of 4 s, the 3964 procedure stops receiving and signals the error to the interpreter. Example of a data exchange without errors: CP 525 Partner procedure 3964 (e.g. AS 512 GC) < STX DLE > < lst character < : < . < . < nth character < DLE < ETX DLE > 5.1.4 Initialization Conflict Tf a device receives a send request (SIX character) from its partner and does not answer within the acknowledgement delay time QVZ with DLE or NAK, but also sends the character STK, there is an initialization conflict. Both devices are attempting to carry out a send job. The device with the lower priority desists and answers with the DLE character. The device with the higher prior- ity sends its data as described above. After the link has been terminated the lower priority device can then run its send job. 60B8576539-03 Computer Link with the RK 512 You set the "priority" parameter when writing the CP 525 user program with COM 525 in the ASSIGN PROC. PARA. mask. Remember that one device must be assigned higher, and one lower priority. Example of resolving an initialzation conflict: CP 525 Partner procedure 3964 (e.g. AS 512 C) lower priority higher priority STX ~~_______-> STX A DLE --_-________> lst character nth character DLE ETX AAAAAA DLE --__-____> sx __-____> <___---_~. DIE The procedure recognizes errors caused by the partner's reacting incorrectly, and errors caused by disturbances on the line. 5.1.5 Procedure Errors In both cases an attempt is made to send or receive the data field correctly. The first repetition is signalled to the inter- preter. If the data field cannot be sent or received within the maximum number of repetitions (or a new error occurs), the proce- dure breaks off the transmission or reception. It signals a specific error number to the interpreter for the first error detected and then goes to the idle state. 61B8576539-03 Computer Link with the RK 512 The interpreter enters the error number received from the proce- dure in the error message area of the SYSTAT. The significance of the individual error mmbers can be found in the error tables in Section 8. If the error occurs during transmission for a PC job, the job status also has an error entry. If you find that there is often an entry for send or receive repetitions in the error message area of the SYSTAT, but it does not have an exact error number, you can assume sporadic dis- turbances of the data exchange. These disturbances are compen- sated by the number of repetitions. You should check the trans- mission line for sources of interference, since the effective data rate and reliability of transmission are reduced by large numbers of repetitions. The cause of the problem could also be incorrect reaction by the partner. Note that a link to an AS 512C module using a higher data rate occasionally causes repetitions. Note: - If there is a BREAK on the receive line, the BREAK error number is signalled to the interpreter immediately. No repetitions are started. The error signal remains active until the problem is eliminated. ~ When transmission errors are detected (lost character, frame error, parity error), the same mumber is signalled, regardless of whether the error was detected when a data field was trans- mitted or received. The error is, however, signalled only when the repetitions are unsuccessful. If the corrupted character is received while the procedure is in the idle state, the error number is signalled to the interpreter immediately to indicate serious interference on the transmission line. 62B8576539-03 Computer Link with RK 512 5.2 3964R Procedure 5.2.1 Procedure Data The procedure 3964R controls the flow of data between your pro- grammable controller and the partner, e.g., a central process com-puter, another CP 525, or an AS 512G. In the GP 525, the interpreter transfers the data to be sent into output buffers for the procedure. The procedure sends this data along with the transmission protocol 3964R to the partner; if necessary repeats the transmission, and signals non-recoverable errors to the in- terpreter. Data from the partner is stored in input buffers. If the data is received without errors, it is transferred to the interpreter for further processing. The 3964R procedure is an asynchronous, bit serial transfer pro- cedure. The transmission rate both sending and receiving must be the same on the CP 525 and on the partner (asynchronous because there are no timing circuits between the two devices). Control and information characters are transmitted on the Link. To ensure that every character is recognized by the receiver and to allow the transmission to be checked for errors, the charac- ters are encapsulated by further bits. The order of the bits is as follows: SA | I0 | Il | I2 | I3 | 14 | I5 | 16 | 17 }] PA | so SA = start bit I* = information bit no. PA = parity bit SO = stop bit 63B8576539-04 Computer Link with RK 512 The control characters for the 3964R procedure are taken from the DIN standard 66003 for the 7-bit code. However, the character length used is 8-bit (bit 7 = 0). At the end of each data field a block check character (BCC) is added for data protection. The block check character BCC is the even longitudinal parity of the information bits of all data bytes of a field that has been sent or received. The characters begin with the first byte of informa- tion data following the establishment of the link and finish with the DLE ETX character when the link is terminated. No code is prescribed for the information characters (code transparency). The following procedure parameters can be set when writing the CP 525 user program with COM 525: Data rate The speed of the data transmission is specified in bps. You can select the following values: 19200 bps * 9600 bps 4800 bps 2400 bps 1200 bps 600 bps 300 bps 150 bps 110 bps (*) 19200 bps are only allowed if you use the V.24 interface with the CP 525/CP 524 or the RS422-A/485 interface with the CP 524. In this case you can only load and operate one interface with the GP 525 ince the maximm sum of the data rates is also 19200 bps. 64B8576539-03 Computer Link with RK 512 Priority To resolve initialization conflicts you can set the priority of the CP 525. At the partner the opposite priority must be set. You can choose between the following: higher priority lower priority The following are fixed for the 3964R procedure: character length: 8 bits number of stop bits: 1 parity bit, i.e., checking for even parity 5.2.2 Transmitting with the 39648 Procedure To establish the link, the 3964R procedure sends the control character STK. If the partner replies within the time allowed of 2000 ms (i.e., no QVZ = timeout), the procedure starts the trans- mission. If the partner answers with NAK, any other character (except DLE) or if there is a timeout, then the attempt to estab- lish a link has failed. After a total of six unsuccessful attempts, the procedure gives up, signals the interpreter that there is an error establishing the link, and sends the character NAK to the partner. If the link is successfully established, the information data in the current output buffer is sent to the partner at the selected data rate. The partner monitors the time between the characters as it receives them. The time between two characters must not exceed the character delay time of 220 ms (ZVZ = character time- out). Each DLE character found in the buffer is sent as two DLE charac- ters (DIE doubling), f.e., the data (10H) is sent twice. 65B8576539-03 Computer Link with RK 512 After sending the contents of the buffer, the procedure adds the characters DLE ETX and BCC as end identifier and waits for an acknowledgement. If the partner sends the character DLE within the time allowed (QVZ), the data field was received without errors. If the partner replies with NAK, any other character (except DLE), a corrupted character, or if there is a timeout, the procedure begins the Link establishment again with STX. After a total of six wsuccessful attempts to send the data field, the procedure breaks off the attempt, signals the error to the inter- preter and sends NAK to the partner. If, while data is being transmitted, the partner sends the char- acter NAK, the procedure breaks off the field and repeats it as previously described. If any other character is received, the procedure waits for the character delay time (ZVZ) to elapse and then sends NAK to reset the partner. Then the procedure begins the transmission again with the link establishment STX. Example of a data exchange without errors: CP 525 Partner procedure 3964R (e.g. AS 512 C) STX > < DLE lst character > . > . > . > nth character > DLE > ETX > BCC > < DLE 66B8576539-03 Computer Link with RK 512 5.2.3 Receiving with the 39642 Procedure In the idle state, i.e., when there is no send job to be process- ed, the 3964R procedure waits for the link to be established by the partner. If the procedure receives any character (except STX) while in the idle state, it waits until the character delay time (ZVZ) has elapsed and then sends a NAK character. The error is signalled to the interpreter. If the procedure receives the character STIX and if it has an empty input buffer available, it answers with DLE. The characters then received are entered in the input buffer. If two DLE charac- ters are received in succession, only one DLE character is en- tered in the input buffer. If the input buffer is full before the partner has started to terminate the link, the full buffer is transferred to the interpreter and the next characters arriving are entered in the second input buffer. After each character received, the procedure waits for the next character to arrive within the character delay time. If there is a character timeout, the NAK character is sent to the partner and the error signalled to the interpreter. If the procedure recognizes the character sequence DLE ETX and BCC, it stops receiving. It compares the received block check character BCC with the longitudinal parity calculated internally. If the block check character is correct and no other errors have occurred during reception, the procedure sends DLE. The procedure transfers the input buffer to the interpreter and returns to the idle state. If the BCC does not correspond, NAK is sent to the partner. Then a repetition is expected. If the block cannot be received without errors following six attempts or if the repeti- tion by the partner does not take place within the waiting time of 4 s, the 3964R procedure breaks off the reception and signals the error to the interpreter. If transmission errors occur during the reception (characters lost, frame error, parity error), reception is continued wmtil the link is terminated and then NAK is sent to the partner. Then a repetition is expected as previously described. 67B8576539-03 Computer Link with RK 512 Example of a data exchange without errors: CP 525 Partner procedure 3964R (e.g. AS 512c) < STX DLE > < lst character < < < . < nth character < DLE < ETX < BCC DLE > 5.2.4 Initialization Conflict If a device receives a send request (STX character) from its partner and does not answer within the acknowledgement delay time QVZ with DLE or NAK, but also sends the character STX, there is an initialization conflict. Both devices are attempting to per- form a send job. The device with the lower priority desists and answers with the DLE character. The device with the higher prior- ity sends its data as previously described. After the Link has been terminated, the lower priority device can then mm its send job. The priority parameter is set when you are writing the CP 525 user program with COM 525 in the ASSIGN PROC. PARA. mask. Remember that one device must be assigned higher, and one lower, priority. 68B8576539-03 Computer Link with RK 512 Example of resolving an initialization conflict: CP 525 Partner procedure 3964R (e.g. AS 512C) lower priority higher priority sk __________> <___ Sx DLE ________> < lst character < < . < nth character < DIE < ETX < BCC DIE ___________> six _-_____> <___________- DLE 5.2.5 Procedure Errors The procedure recognizes errors caused by the partner reacting incorrectly, and errors caused by disturbances on the line. In both cases an attempt is made to send or receive the data field correctly. The first repetition is signalled to the inter- preter. If the data field cannot be sent or received within the maximm number of repetitions (or a new error occurs), the proce- dure breaks off the transmission or reception. It signals a specific error number to the interpreter for the first error detected and then goes to the idle state. 69B8576539-03 Computer Link with RK 512 The interpreter enters the error number received from the proce- dure in the error message area of the SYSTAT. The significance of the individual error numbers can be found in the error tables in Section 8. If the error took place during transmission for a PC job, the job status also has an error entry. If you find that there is often an entry for send or receive repetitions in the error message area of the SYSTAT, but there is no exact error number, you can assume sporadic disturbances of the data exchange. This is, however, compensated by the number of repetitions. In this case you should check the transmission line for sources of interference, since the effective data rate and reliability of transmission is reduced by large numbers of repet- itions. The cause of the problem could also be incorrect reaction by the partner. Note that a link to an AS 512C module using a higher data rate occasionally causes repetitions. Note: - If there is a BREAK on the receive line, the BREAK error number is signalled to the interpreter immediately. No repetitions are started. The error signal remains active until the problem is eliminated. - When transmission errors are detected (lost character, frame error, parity error) the same number is signalled, regardless of whether the error was detected when a data field was trans- mitted or received. The error is only signalled when the repet- itions are unsuccessful. If the corrupted character is received while the procedure is in the idle state, the error number is signalled to the interpreter immediately to indicate serious interference on the transmission line. 70B8576539-03 Computer Link with RK 512 6 Multiprocessor Operation Compared with single processor operation, multiprocessor oper- ation requires even more that the programming of the individual CPUs (STEP 5 user programs) and of the CP 525 (CP 525 user programs) is carefully matched. The more complex the application, the greater the care that must be taken to ensure the numbers of the individual CPUs are cor- rectly specified in the CP 525 user program. T IMPORTANT! If several CPUs are to supply jobs to only one interface of a CP 525, the STEP 5 user programs of these CPUs must be coordinated. Remember that a maximum of 10 jobs can be processed simultaneous- ly on one interface. If an eleventh job is initiated, it is rejected with an error number in the PAFE byte. Another job can be initiated only when one of the ten jobs has been completed with or without errors. CPU the you should design the STEP 5 user programs so that at any one time only ome CPU can start one of these jobs. All other CPUs must wait until this job is signalled as "completed" (with or without errors). If jobs with the same job number are programmed on more than one For more information on specific jobs see the corresponding sections in this user's guide. 71B8576539-03 Computer Link with RK 512 7 Special Jobs Carried out by the CPU Section 7 contains information about the following: - the PSEUDO READ/WRITE function ~ the error message area of the SYSTAT - the identification area SYSID - the reading and writing of the date and time 7-1 PSEUDO READ/WRITE Function The READ/WRITE function (R/W function) with which you are famil- iar as a user of the handling blocks must not be used in comec- tion with the CP 525. This is true for the following reasons: - This R/W function does not allow the specification of a coordination flag and the CPU number. - It overwrites part of the data area in the dual-port RAM of the CP 525, which currently contains data to be transmitted. Therefore a PSEUDO B/W function is used, based essentially on the function and structure of the kriown R/W fumction. The pseudo B/W function means that you can act as follows: ~ can change source and/or destination specifications of a job dynamically while the program is ruming - do not have to change source and/or destination specifications of a job dynamically while the program is running - do not have to change source and/or destination specifications of a job dynamically while the program is running - do not have to program this job with COM 525 All the parameters for the source and destination are stored in a data block (DB) or extended data block (DX). The job numbers 190 to 199 are reserved for the PSEUDO READ/WRITE function. 72B8576539-03 Computer Link with RK 512 A SEND job with the pseudo R/W function is started by one of the following HDBs: SEND DIRECT 190 to SEND DIRECT 199 The pseudo R/W job is entered in the internal job queue of the CP 525 just as other direct jobs. When the job is processed the CP 525 uses the SEND ALL HDB to request the specified data block (or extended data block) with the assigned parameters and checks the source and destination parameters specified in it. If these are within the permitted limits, the CP 525 requests the first source data by means of a second SEND ALL HDB and then processes the SEND job as usual. 73B8576539-03 Computer Link with RK 512 PROGRAMMABLE CONTROLLER 1 jPROGRAMMABLE een Rprocessor | | Central processor CPU CP 525 . CP 525 CPU SEND |: | proce- |! |] PROCE- Gobno. : : + > 190-199) |: DURE per | DURE rf BMOOQA~"D4 SEND |: I WNTeR- |: | InTER- || [| RECEIVE ALL = 1 PRETER |! :| PRETER F *) DT = DATA TRANSMISSION Fig. 1 WRITE fimction 74B8576539-03 Computer Link with RK 512 A FETCH job with the PSEUDO R/W function is started by one of the following HDBs: FETCH DIRECT 190 to FETCH DIRECT 199 As with the SEND job, the CPU fetches the specified data block using SEND ALL and evaluates the source/destination parameters. Then the FETCH telegram is sent to the partner. Once the data is received from the partner, the RECEIVE ALL HDB enters it in the specified destination. In contrast to normal direct jobs, the PSEUDO R/W function re- quires an additional exchange of data between the CPU and CP. This data exchange is handled by the SEND ALL, which transfers the source/destination parameters to the CP 525. 75B8576539-03 Computer Link with RK 512 PROGRAMMABLE CONTROLLER 1 PROGRAMMABLE CONTROLLER 2 R processor | I Central processor CPU CP25 CP 525 CPU FETCH || '|PROCE- |: _||PROCE- foarte || [DURE [or] DURE ; BmMaAd~" Bw SEND :|_Gobna. 0) Vv ft LUINTER. 1: INTER |) ES : : iT SEND *) DT = DATA TRANSMISSION Fig. 2 READ function 76B8576539-03 Computer Link with RK 512 The following pages show the structure of the data block with the source/destination parameters (parameter data block). The form and order are those you see on the PG. The letters x and y are variables. You must replace them with values. The addresses of the data are relative to the start address QANF, which is specified in the HDB. 77B8576539-06 Computer Link with RK 512 1.) Structure of the parameter data block for SEND DIRECT 190 to QANF + 0: KS= x 2; KF= x} 3 KF= x; 4 KS= xx 8: KY= xX, Yy3 SEND DIRECT 199 ;source type (in own PC) value range: = DB,DX,CB,TB,RS,AS,FY,QB IB, PB,OB mot: XX,RW,NN ;source data block number value range:y= 3 to 255 for source type DB/DX irrelevant for other source types ;source start address value range:x= dependent on source type and PC type (see job table in Section 2.6) ;source length value range:x= dependent on source type and PC type (see job table Section 2.6) ;dest. type (for partner) value range:xx=DB,RS,AS,DX dependent on source type (see job tables in Section 2.6) ;dest. data block number value range:y= 3 to 255 for dest. type DB or DX irrelevant for other dest. types sdest. start address value range:x= dependent on dest. type and PC type (see job tables in Section 2.6) 3(dest. length) irrelevant!! value range:x= any ;coord. flags (dependent on dest. type) value range:x= 0 to 255: byte number y= Oto 7: bit number no coord. flags: x=255, y=255 !1! ;CPU no. for partner value range:x= 1 to 4 or x= 0 for PC's with only one CPU 78B8576539-06 Computer Link with RK 512 2.) Structure of the parameter data block for FETCH DIRECT 190 to FETCH DIRECT 199 ZANF + QO: KS= xx ysource type (in partner) value range: = DB,DX,CB,TB,RS,AS,FY,QB IB, PB,OB mot: XX,RW,NN 1: KY= 0, YY; ;source data bl. no. for source type DB, DX value range:y= 3 to 255 for source type DB/DX irrelevant for other source types 2: KF= x ssource start address value range:x= dependent on source type and PC type (see job table in Section 2.6) 3: KF= x3 ;Csource length) irrelevant!! value range:x= any 4: KS= xx ;dest. type (in own PC) value range:xx=DB,RS,AS, DX dependent on source type (see job tables in Section 2.6) 5: KY= 0, Y; 3;dest. data block number value range:y= 3 to 255 for dest. type DB or DX irrelevant for other 7 dest. types 6: KF= x3 ;dest. start address value range:x= dependent on dest. type and PC type (see job tables in Section 2.6) 7: KFe= x: sdest. Length value range:x= dependent on dest. type and PG type (see job table Section 2.6) 8: KY= x, Y3 ;coord. flags (dependent on dest. type) value range:x= 0 to 255: byte number y= Oto 7: bit number no coord. flags: x=255, y=255 !1! 9; KF= x3 ;CPU no. for partner value range:x= 1 to 4 or x= 0 for PG's with only one CPU 79B8576539-01 Computer Link with RK 512 Transmissions of possibilities can be seen in the job table in Section 2.6, For SEND DIRECT 190 to 199 the data source is in your own PC. You must specify the source length in the parameter data block Center this in bytes if the QTYP is a byte area). The specification of the dest. length (ZLAE) is unnecessary. All specifications of the data destination refer to the partner, With FETCH DIRECT 190 to 199 the data destination is in your own PC. Therefore the specification of the length ZLAE in the parameter data block is vital. Any specification of the parameter QLAE is not evaluated. All the parameters involving the data source refer to the partner. The jobs SEND DIRECT 190 to 199 and FETCH 190 to 199 are called in the STEP 5 program just as "normal" jobs with "JU". In the specifications in the block : QTYP/ZTYP, DB no., QANF/ZANF, QLAE/ZLAE, you name your data block with the RW parameters. The specification of QLAE/ZLAE is unnecessary since the CP 525 always reads 10 data words (with SEND ALL). If no more than 10 jobs are reported as running simultaneously, the pseudo R/W jobs can be called mixed in with normal SEND and FETCH jobs. If more than 10 jobs are called, the initiation of the jobs must be interlocked. Since each job number can be assigned only once, it is not possible to activate a SEND DIRECT 190 and a FETCH DIRECT 190 at the same time. If the SEND DIRECT job 190 is set to runing in the condition codeword, no other job with the mmber 190 (e.g., FETCH 190) can be started until SEND DIRECT 190 is completed with or without errors. 80B8576539-01 Computer Link with RK 512 7.2 Reading the Error Message Area of the SYSTAT The error message area of the SYSTAT is a data area in the dual- port RAM of the CP 525. After the CP 525 recognizes an error, it enters the corresponding error number in the error message area of the SYSTAT. You decide how the CPU is to react in your STEP 5 user program on the CPU. The CPU reads the error message area of the SYSTAT for the speci- fied CP interface by means of the job RECEIVE DIRECT 200 The area in the CPU (destination area) to which the error message area of the SYSTAT is to be transferred, is fixed when you assign parameters to RECEIVE DIRECT 200. These parameters should be a data block. The destination length must be at least two words. RECEIVE DIRECT 200 is executed only when an error number is entered in the error message area of the SYSTAT, since only then is the bit "RECEIVE - job ready" set in the ANZW (bit 0). Note: in some cases (e.g., if no SYNCHRON has been run or if start-up errors have occurred in the CP 525), the error message area cannot be read by RECEIVE DIRECT 200 (cf. note in Section 7.4 Reading the whole SYSTAT). 81B8576539-0O1 Computer Link with RK 512 Structure of the destination area: If error numbers are entered in the error message area they are located (after they have been read by RECEIVE DIRECT 200) in the selected area in the CPU (e.g., in the data block). Bit 7 6 5 4 3 2 1 40 Byte 0 (DLO) . - {e,o]B]R 1 (DRO) Error number 1 2 (DLL) Error number 2 3 (DR1) Error number 3 This diagram is explained on the following page. 82B8576539-03 Computer Link with RK 512 Byte | Bit Status | Significance byte O}bit 3 0 no error in SYSTAT (not following (C) executed RECEIVE DIRECT 200) 1 error entered in SYSTAT note: this bit is always set if there is an error entry - i.e., use this bit to check whether data was transferred with RECEIVE DIRECT 200 bit 2 0 no error overflow (max. 3 error (O) entries) 1 error overflow (more than 3 errors) bit 1 0 no BREAK currently on the interface (B) 1 BREAK on the interface note: bit 1 shows only the instantan- eous status and does not always mean an error. The error status BREAK is determined only by the error number in DRO, DLL and DRL. The current BREAK status can only be indicated if the interpreter and procedure are loaded and have been started. bit 0 unnecessary for computer Link @) bit 7, 6, 5, 4 unnecessary byte 1 error number 1 byte 2 error number 2 byte 3 error number 3 00 = no error For more information on error messages refer to Section 8. 83B8576539-03 Computer Link with RK 512 Example of a command sequence within a STEP 5 user program for the CPU 992 (R processor) / S5-135U: ae ee Oo F1.0 ; to initiate the reading out from SYSTAT :ON F1.0 3 result of logic operation must be "1" :JU FB121 NAME; RECEIVE ; data transfer only in error entry SSNR: KYO,0 3 interface number 0 A-NR: KY0,200 > Lixed job number for reading SYSTAT ANZW: FW1O ZTYP: KSDB DBNR: KY0,10 ; dest. for error numbers is DB10 ZANF: KF+1 ; from data word 1 ZLAE: KF+2 3; 2 data words PAFE: FY5 :G DB1O :<AN D 1.11 > test bit 3 of group byte :JCG =M001 ; jump if no error entered ze > error evaluation :J0 FB124 ; am error was entered, i.e., the SYSTAT NAME: RESET ; register on the CP 525 should be reset SSNR: KYO,0 ; with RESET DIRECT 200 (see following A-NR: KYO,200 pages) PAFE: FY6 7G ~=6 DB10 5 reset error entry in DB :L = KHOO0O T Dwi 7T =DWw2 MOOL]:. etc. :BE 84B8576539-03 Computer Link with RK 512 7.3 Resetting (Clearing) the Error Message Area The CPU resets the error message area of the SYSTAT (based on interface numbers) with the job RESET DIRECT 200 All the entries are then cleared except the BREAK bit (B). !IMPORTANT!: the error message area of the SYSTAT is not cleared by a SYNCHRON call. The CP 525 can enter up to three error numbers in the error message area. More errors cannot be signalled unless the "old" entries have been cleared. Therefore the error message area must be reset in good time by a RESET DIRECT 200. The destination area in the CPU must also be reset. 7.4 Reading the Whole SYSTAT In addition to the reading of the error message area of the SYSTAT, the entire SYSTAT of the CP can be read by means of the vA job RECEIVE DIRECT 221 The area read then contains the error messages for both inter- faces (in bytes 4 to 10). This job can be executed only if there are no error numbers entered. A destination length greater than or equal to 16 bytes (8 words) is necessary. Note: in some cases (e.g. no SYNCHRON executed, or error during the start-up of the CP 525) the SYSTAT carmot be read by means of RECEIVE DIRECT 221. It must then be read directly from the dual- port RAM (from address F660H onwards). 85B8576539-03 Computer Link with RK 512 The area transferred with this job is structured as follows: Bit 7 | 6 | 5 | 4 | 3 | 2 | 1 0 Byte 0 irrelevant | RUN | STOP 1 irrelevant 2 sion of life" 3 irrelevant PGR 4 | 2 | 02 | 32 | R2 | #1 | o1 | 3a | Ru 5 error mumber 1 IFl 6 error number 2 IF1 7 error mmber 3 IF1 8 error number 1 IF2 9 error number 2 IF2 10 . error number 3 IF2 11 12 reserved 13 14 15 The individual bits or bytes have the following significance: - RON =1 mode selector switched to RUN - STOP = 1 mode selector switched to STOP - PGR =1 mode selector switched to PGR "Sign of life", this byte is incremented by 8 at regular inter- vals on the CP 86B8576539-03 Computer Link with RK 512 ~ Bytes 4 to 10: cover the error message area for both interfaces (see Section 7.2 - Reading the error message area of the SYSTAT). - Error message area for IF1: bytes 5 to 7 and byte 4 (bits 0 to 3) ~ Error message area for IF2: bytes 8 to 10 and byte 4 (bits 4 to 7) 7.5 Reading the SYSID An identification area is specified on each CP 525. Information is written into the identification area SYSID of the CP 525; i.e., you can find information about the following: - module - memory submodule - interface assignment - issue/version of the loaded software etc. The CPU can read the SYSID of the CP 525 by means of the job RECEIVE DIRECT 223 This is possible if the field length is greater than or equal to 128 bytes; i.e., the BLGR parameter in the SYNCHRON is KY 0,4 / KY 0,5 / KY 0,6. A destination length greater than or equal to 128 bytes is also necessary. If the field length is less than 128 bytes the message "completed with errors" and the error number 7 are entered in the status byte and the number 1E in the error message area of the SYSTAT. The SYSID area is not then transferred. Note: the SYSID can also be read directly from the dual-port RAM, L.e., without handling blocks (from address F680H onwards). For more information refer to the manual for your PC. 87B8576539-03 Computer Link with RK 512 Structure of the identification area SYSID The SYSID contains a number of parameters which identify the CP. Each parameter is completed with carriage return (CR = ODH) that is also counted in the byte specification. Parameters not assigned consist simply of CR. Some parameters have a different significance depending on the memory submodule types. All the parameters are represented in ASCII. With the CP 525 these parameters are structured as follows: Parameter Byte Description 0 0 to 9 Mem. submodule identifier/capacity: EPROM: e.g. for order number 6ES5373-0AA41 shown as:373-OAA41 RAM: memory capacity of the submod. RAM xxxKw e.g. XXX = 64 10 to 18 Module identifier: CP 525-2 / CP 524 19 to 21 Version of the CP firmware 22 to 41 Plant designation from mem. submodule: EPROM: designation of programmed plant RAM: xeplaced by space (20H) 42 to 50 Generated on: EPROM: date of EPROM- programming RAM: replaced by space (20H) 5 to 9 51 to 55 Not used with CP 525/cP 524 10 56 to 64 PROM 525 - version: PROM 525 = programming program for EPROM submodules EPROM: PROM 525 - version RAM: replaced by space (20H) 88B8576539-03 Interface 1 Computer Link with RK 512 Parameter Byte Description Example 11 65 to 67 component type RK 12 68 to 76 interpreter name (*) RK512 13 77 to 79 interpreter version mm 14 80 to 88 procedure name (*) P3964R 15 89 to 91 procedure version m Interface 2 Parameter Byte Description Example 16 92 to 94 component type PT 17 95 to 103 interpreter name (*) PT88 18 104 to 106 interpreter version mm 19 107 to 115 procedure name (*) LAUFPT88 20 116 to 118 procedure version mm 119 end identifier ETX (03H) mm = version number * = name of interpreter and procedure correspond to the designations in the COM library .If the interface is not assigned, the parameters specific to the interface are replaced by spaces (20H). 89B8576539-08 Computer Link with RK 512 7.6 CP 525: Reading and Writing the Date and Time A GP 525 must be designated either time master or time slave. Time slave: after powering up the CP reacts at first as a time slave. It can update its own date and time, however, the CPU cannot read them. Time master: the master provides the system time; i.e., the mas- ter must make this available at any time. To synchronize the CPs (at regular intervals or when certain events occur) the CPU reads the system time from the time master and sets all the time slaves to this time. This relieves the time slaves of unnec- essary updating tasks. The GPU can set the date and time on a CP 525 at any time. It can, however, only read the date and time of a CP 525 that is designated as time master. Note: The CP 524 does not have a hardware clock. When using the CP 524, the software clock is not updated or buffered if the PLC is set to STOP or the mains voltage is switched off. Thus, the CP 524 clock must be updated when the CPU is restarted (cold restart). 90B8576539-03 Computer Link with RK 512 The date/time area transferred during writing or reading is structured as follows: Byte Significance 0 bit 0: master id. 1 = master 0 = slave 1 0 2 ho /ro0 3 s 4 min 5 h 6 day 7 month 8 year aa In a word transfer byte, 0 corresponds to the left half of the first data word; byte 1 the right half of the first data word. The date and time are coded in BCD. The accuracy of the clock is 1h S. This means that the position 7100 s in byte 2 of the date/time area is always 0. When the time is written, the /100 s is not accepted. 91B8576539-03 Computer Link with RK 512 The job number 218 is fixed on the CP 525 for the jobs "read / write date and time". SEND DIRECT 218 Using this job, the CPU declares the CP as master or slave. At the same time the CPU can also transfer the date and time to the CP. Whether the CPU transfers the date and time depends on the source length specified (QLAE = length of the data to be transferred). QLIAE = 1 word The GP 525 is declared as master/slave by means of the contents of bit 0 (least significant bit) in the first byte; master: bit 0=1 / slave: bit 0 = 0. During the start-up or in a warm restart of the CPU, the SEND DIRECT 218 with QLAE = 1 and master bit = 1 for the CP that is to be master must be called up. The date and time on the CP 525 are not changed by QLAE = 1. QLAE = 5 words The CP is declared as master/slave by means of the master identi- fier and the date and time are transferred. Remember to set the master identifier when transferring the time to a master which is to remain as master. Also remember that the date and time are only adopted by the CP during the handshake (synchronization via inputs or after reading a different clock). Note: the source area from which the data is transferred to the CP should be a data block. 92B8576539-03 Computer Link with RK 512 Note: The GP 525 can be declared as time master on one or both inter- faces. The date and time can only be read on the interface on which the CP was declared as master. If the CP is declared as master.on an interface and then as slave on the other interface, the CP becomes a time slave on both interfaces. For example, the following situation occurs: when the date/time from the first interface is read, the error number 1F is entered in SYSTAT. When reading from the second interface the handshake is not performed, since the bit "RECEIVE - job ready" in the ANZW (bit 0) is not set. No error message is output. A SYNCHRON does not influence the master-slave fimction. RECEIVE DIRECT 218 By means of this job the CPU can read the date and time from the CP (if the CP has already been declared time master with SEND DIRECT 218. The destination length must be five words. The destination area should be a data block. Note: the data read only has meaning if the date and time have been set at least once since the module was plugged in (with SEND DIRECT 218, length: five words). 93B8576539-03 Computer Link with RK 512 8 Error Handling Errors occurring while the computer link is in operation, may have been caused at various points. If the CP detects the errors, they are signalled to the CPU with as much detail as possible. The way in which the CPU then reacts is decided by your STEP 5 user program on the CPU (for more details see Section 7). For example you can have the following: - an error message output on the printer PI88/PT89 (either via another CP 525 or via the same CP 525 using the other inter- face) - the error displayed as messages on a monitor (e.g. with the CP 526) - the job repeated The error is signalled by the following: - an error number in the PAFE byte of the handling block CL.) - an error mmber in the condition codeword ANZW of the handling block (2.) ~ an error number in the error message area of the SYSTAT 3.) - the CP 525 signals an error to the partner by an error number in the reply telegram in REPTEL 4.) 1. The error mubers in the PAFE byte of the handling block (HDB) The PAFE byte is a parameter you specify when calling an HDB. In the PAFE byte, the handling blocks indicate when serious errors occur in connection with a CP or when parameters have been speci- fied incorrectly. A detailed description of PAFE byte error messages can be found in the description "Using the handling blocks" in this manual. 94B8576539-03 Computer Link with RK 512 If you receive a PAFE error number, this means that the data exchange between the CPU and CP either was not started or was aborted after several unsuccessful attempts. In the following exceptional cases the error numbers 91H and C1H can mean that a serious error has occurred: - after a program section is transferred from the PG to the CP 525 - if coordination flags have been used incorrectly LIMPORTANT!: if these situations occur on your system you should first repeat the corresponding job. 2. The error mmbers in the condition codeword ANZW The condition codeword ANZW is also a parameter you specify when calling an HDB. With direct jobs (SEND DIRECT, FETCH DIRECT, RECEIVE DIRECT), ANZW indicates whether the job is running or was completed. If the job was terminated with an error, an error number is entered in bits 8 to 11 in the ANZW. Bit 3 is also set: "job terminated with error". PIMPORTANT!: an error number is only entered in ANZW if the error occurred during the processing of a DIRECT job! Since only four bits are available for the error numbers in ANZW, one error number normally indicates one of several error states. Owing to the limited number of error numbers the ANZW is suitable for evaluation by the STEP 5 user program. 95B8576539-03 Computer Link with RK 512 The errors are distinguished by the various sources of error as follows: No. for ANZW Source 1 to 5 parameter assignment error recognised by the CPU of the PC and signalled to the CP 6 error in data exchange between CPU and CP detected by CP 7 job cannot be carried out, error in job parameters 9,A,B,C,D error during the execution of a job, caused by incorrect reaction or error messages from the partner E, F error in data exchange between CP 525 and partner Descriptions of the errors can be found in the tables on the following pages. Note: a status byte is reserved in the dual-port RAM for each of the possible jobs. If the CP detects an error in comnection with a DIRECT job, it writes the error mumber and the bit "job tern- inated with error" in the status byte of the corresponding job in the dual-port RAM. To. have the job status shown in the condition codeword one of the following must occur: - the CONTROL HDB in the STEP 5 program must be called with the corresponding job number in the cycle (0B1) - the DIRECT job (SEND DIRECT) must be called with the command JU and RLO=0. See also the description "Using the handling blocks" in this manual. 96B8576539-03 Computer Link with RK 512 3. The error mumbers in the error message area of the SYSTAT The error message area of the SYSTAT is a data area in the dual- port RAM; the CPU reads this area using the special job RECEIVE DIRECT 200. For each interface the error message area of the SYSTAT includes three error message bytes and an additional status byte. A detailed description can be found in Section 7 "Special jobs carried out by the CPU". All errors recognized by the CP are entered in the error message area of the SYSTAT. If the error occurs in connection with a DIRECT job, an error number is also entered in the condition codeword. If the error occurs in comection with a partner job, an error number is transferred in the reply telegram to the partner. The error entry in the SYSTAT is so detailed that it is particu- larly suitable for exact error analysis during commissioning. A programmed evaluation of individual error numbers is also possible. Remember that not only serious errors are entered in the SYSTAT. For example, an entry is made in SYSTAT when the pro- cedure repeats parts of the telegram exchange. A repetition is not an error but simply points to minor problems in the telegram exchange that can be corrected by repetitions. The special job RECEIVE DIRECT 200 should be called up in OB1 to read the error message area in the SYSTAT during the comnission- ing phase. You can recognize the occurrence of errors when bit 0 in the ANZW of the RECEIVE DIRECT 200 is set to 1 by the CP and the error numbers are then copied into the data block specified as a parameter. If a programmer is connected to the CPU of the PC, you can display the errors directly on the monitor in the operating mode "STATUS variable" or "CONTROL variable". To clear the error entries in the SYSTAT, call the special job RESET DIRECT 200 (for more details see Section 7). 97B8576539-03 Computer Link with RK 512 The errors are distinguished by the various error sources as follows: No. for SYSTAT | Source 1 to 6 parameter assignment errors detected by the CPU of the PC, and signalled to the CP 10 to 14 errors in the data exchange between CPU and GP detected by the CP 15 to 1F system errors at the beginning of the job processing 20 to 2F errors in the processing of a PC job, detected by the CP 30 to 3A errors in the processing of a PC job, detected by the partner and signalled to the GP by means of an error number in the reply telegram 40 to 53 errors during the processing of a partner job, recognised by the cP 5E to 5F reception of an uninterpretable telegram BO to B8 error in data exchange between PG and CP CO to CA hardware error on the module DO to FF error in the data exchange between CP and partner 98B8576539-03 Computer Link with RK 512 4. Error mimbers in reply telegrams If an error occurs in connection with a SEND or FETCH telegram from the partner, an error mmber is entered in the fourth byte of the reply telegram. The partner job is then terminated. Note: The numbers of the error messages are specified as hexadecimal values. The following tables contain a detailed description of the error numbers - arranged according to the numbers for ANZW arranged according to the numbers for SYSTAT - arranged according to the numbers for REPTEL and how you can remedy the problen. . The tables generally contain three colums with error numbers (no. for ANZW/SYSTAT/REPTEL). The error numbers in the second and third colums correspond to the number in the first column. Note that error numbers in ANZW and REPTEL are entered only if vi the job is running at the time when the error occurs. For example: Case 1: an interference pulse is generated on the transmission line during a break in transmission; the procedure recog- nizes a corrupted character. It therefore generates the error code FEH which is entered in SYSTAT. The ANZW is not changed since the error did not occur during the actual transmission. Case 2: the interference pulse occurs while a PC job is being sent and the repetitions do not succeed in achieving an error-free transfer; an error number (EH) is entered in the ANZW as well as the entry (FEH) in the SYSTAT. 99B8576539-03 Computer Link with RK 512 8.1 Error Messages for SYSTAT, ANZW and REPTEL Arranged According to the Numbers for ANZW No. for ANZW No. for SYSTAT No. for REPTEL Description 3H 4H 01H 02H 03H O4H 05H OAH 14H OCH 148 OcH OAH OCH Parameter assignment errors detected by the CPU of the PC, and signalled by the CP a) Source/dest. type (e.g. ext. DB) illegal area (start address, length) illegal (negative value) DB/DX not present or illegal (e.g. DBO, DB1, DX0) or other data type not present or illegal DB/DX too short: (start address + length > area or area too short with other data type (start address + length > area d) Access to area not possible for user: e.g. hardware memory too small or I/O module not plugged in e) Wrong condition codeword: group message for all errors attributable to this ANZW 6H 06H OAH Error code from the CPU to the CP, which the CP cannot interpret 100B8576539-03 Computer Link with RK 512 Remedy ~ Check parameter assignment on CPU and CP and if necessary correct or - Partner has illegal parameters in the telegram header Find the permissible data types in the job tables (Section 2.6). - Check parameter assignment on CPU and CP, if necessary set up block ~ Partner has wrong parameters in the telegram header Find the permissible data types in the job tables (Section 2.6). ere mee mee eee meee eee eet eee ee ee ee eee ~- Check parameter assignment on GPU and CP if necessary check block/area or ~ Partner has wrong parameters in the telegram header were weer remem eee eee meee ee ee eee - Check parameter assignment on GPU and CP or ~ Partner has wrong parameters in the telegram header Find the permissible start addresses and lengths in the job tables (Section 2.6) Check whether condition codeword is valid. Evaluate PAFE in handling block ( STEP 5 user program). 101B8576539-03 Computer Link with RK 512 No. for , No. for ,; No. for ANZW SYSTAT REPTEL | Description Errors detected by CP during data exchange between CPU and CP: 6H 10H OAH a) Timeout for handshake on CP 11H b) ALL job without request or direct job despite overload 12H c) Wrong sequence for handshake by CPU 13H d) Unknown job type or illegal job munber for direct job 14H e) Illegal acknowledgement from CPU during handshake 102B8576539-03 Gomputer Link with RK 512 Remedy Check whether RECEIVE ALL or SEND ALL are called in your STEP 5 program; evaluate the PAFE in the handling block. eee ecm mm mee cm mee wee neers ere cm mm eee erm eee see Check STEP 5 program, e.g., errors in handling block (Message also possible after transfer from PG to CP). erm eee eee eee ew oe meee ere em eee ee ee eee ee am mre meme ner cee eee eee es eee Check STEP 5 program. 103B8576539-03 No. for ANZW No. for SYSTAT No. for REPTEL Computer Link with RK 512 Description 15H 16H oe oe 17H LFH eee System errors at start of job processing: a) Number of direct jobs which can be processed simultaneously too large for CP 524/CP 525 eee ee ere ee Current job was terminated with error status when CP was cold restarted (power on) or cold restarted from PG Area is masked by STEP 5 program (bit 7 in ANZW = 1) Field length for "read SYSID" (RECEIVE DIRECT 223) too small fe memes mms ere res eee ee "Read date/time" (RECEIVE DIRECT 218) illegal, CP is set as time slave 104B8576539-03 Computer Link with RK 512 Remedy Modify STEP 5 program so that maximum 10 direct jobs run simultaneously. There is no remedy with power on. When cold restarting the CP from the PG, you should make sure that no more CPU jobs are running before writing to an interface. The SYNCHRON HDB clears the job statuses in the dual-port-RAM but not the SYSTAT entry. For SYNCHRON the field length should be greater than or equal to 128 bytes or do without "Read SYSID" (data is nevertheless available in the dual-port RAM). Before reading the date/time, the CP must be designated as master - this then applies to this module. Check whether the CP on the other interface has been set to master. vi 105B8576539-03 No. for ANZW No. for SYSTAT No. from REPTEL Computer Link with RK 512 Description 7H 20H 21H 22H 23H 24H ~ ee ee 25H 26H eee eee Parameter ass. errors in the STEP 5 prog. detected by the CP (e.g. in the pseudo B/W parameters) or job block (CP 525 user program) a) No parameters were stored in the CP 525 user program for this direct job (under this job number) Error in data type (DB, OB...): - unknown data type or - data type not allowed (e.g. ext. DB) or - data type not allowed in HDB parameters in connection with data type in the job block (CP 525 user program) Start address specified too high for required data type or start address or DB/DX no. too low Coordination flags not allowed with this data type or wrong bit number specified mee ee e) CPU number specified too high in pseudo R/W parameters ) Transmission length > 64 Kbytes too long for CP 525 g) Length of telegram header too great or length too great for type specified (in own PC) 106B8576539-03 Computer Link with RK 512 Remedy Create parameters for this job with COM 525 or select other job number. meee eee eee eee os ee ee Find the permissible data types and their combinations in the job tables (Section 2.6). Find the permissible start addresses and DB/DX nos. in the job tables (Section 2.6) that can be specified in the CP 525 user program or STEP 5 program (with pseudo R/W parameters). Coordination flags are not permissible for all data types (see Section 2.6). Check whether the bit number (0 to 7) has been specified correctly when using the pseudo R/W function. soe ee ne ete me meee ee es ee omens we ome meee ene ete ee ewes ae ee eee, If necessary split the job into several jobs with smaller lengths. cee ee ee meme ee ee ee ee ee Find the permissible lengths in the job tables (Section 2.6) that can be specified in the HDB or for the pseudo R/W parameters. If necessary split the job into several jobs with smaller lengths. : 107B8576539-03 Computer Link with RK 512 No. for , No. for , No. for ANZW SYSTAT REPTEL | Description If the partner detects an error when processing a job from another device, it sends a reply telegram back to the CP 525 with the error mumber in the 4th byte. The CP generates a no. for SYSTAT and No.from| for ANZW from this: REPTEL 9H 30H 32H a) DB / DX disabled by coordination flags No.from]| b) Hardware (DMA) error at the REPTEL partner or with CP 525 as partner: AH 31H OAH ~ source/dest. type illegal - OF memory error in partner PC ~ or error in handshake between CP/CPU in partner or - partner PC is in STOP state No.from| c) Memory access error at partner REPTEL (memory not present) 32H OCH with CP 525 as partner: ~ wrong area for condition code- word or - data area does not exist (except DB/DX) or ~ data area too small (except DB/DX) -.-4 meee see wm yee ee ees 108B8576539-03 Computer Link with RK 512 Remedy In the partner program after processing the Last transmission data reset the coordination flags. In the STEP 5 program repeat the job! em nee me eee eee cee wets eerste meme cm em eee ee ee ee - Check whether the partner can transfer the required data type. - Check partner's hardware configuration. , - Switch mode selector at partner PC to RUN. mm ete em eet cee mee ee me eee cee eee ee te es eee Check whether the required data area exists on the partner and whether it is long enough, or check the COM 525 job block or the pseudo R/W parameters. Check the length specified in the HDB. oe ree mmm cams eee eee meet terre mee eee eee ewe ee ee 109B8576539-03 No. for , No. for ANZW SYSTAT No. from REPTEL Computer Link with RK 512 Description AH 33H 14H d) DB/DX access error at partner (DB/DX does not exist or too short) with CP 525 as partner: - DB/DX does not exist or ~ DB/DX too short or - DB/DX no. illegal BH 24H 2BH 2CH 2DH Errors in reply telegram from partner, detected by CP a) Error in format of reply telegram received: first byte not OOH or FFH b) Reply telegram received after FETCH job has too many data c) Reply telegram received after FETCH job has too few data ae rem meee ns te cre ry tne ee eee d) Reply telegram received after SEND job arrived with data 110B8576539-03 Computer Link with RK 512 Remedy Check whether the required data block exists on the partner and whether it is long enough; or check the job block (CP 525 user program); or check the pseudo R/W parameters (STEP 5 user program). Check the length specified in the HDB. Verify incorrect reaction of partner if necessary with an interface test device ('FOXPG') tapped into the transmission Line. wee ee ewe me ee emma Verify incorrect reaction of partner if necessary with an interface test device ('FOXPG') tapped into the transmission line. eee renee mee ee ee Verify incorrect reaction of partner if necessary with an interface test device ('FOXPG') tapped into the transmission line. me eaten mm mmm ecm meee eee ee Verify incorrect reaction of partner if necessary with an interface test device ('FOXPG') tapped into the transmission line. 111B8576539-03 No, for ANZW No. for SYSTAT No. from Computer Link with RK 512 Description BH 34H 35H 36H 39H 3AH 16H 34H ee 12H 77H If the partner detects an error when processing a job from another device, it sends a reply telegram back to the GP 525 with the error number in the 4th byte. The CP generates a no. for SYSTAT and for ANZW from this: a) Errors in the telegram header, detected by partner: first command letter in header wrong ors eee em meee cee nee b) Error in telegram header: second command letter in header wrong woe mee ee ee c) Partner detects wrong telegram length (total length) ome emer ee ewes rete eee, d) Partner signals "system command illegal" e) Unknown error number received in reply telegram 5FH 34H A correct telegram with a length > 128 bytes was received. The telegram could not be interpreted. The job being processed is aborted. 112B8576539-03 Computer Link with RK 512 Remedy Check whether the error is being caused by a disturbance or an incorrect reaction of the partner. Verify with an interface test device ('FOXPG') tapped into the transmission Line. Check whether the error is being caused by a disturbance or an incorrect reaction of the partner. Verify with an interface test device ('FOXPG') tapped into the transmission line. fee mee mete eee eee cee eee meee ee Check whether the error is being caused by a disturbance or an incorrect. reaction of the partner. Verify with an interface test device ('FOXPG') tapped into the transmission line. me eine mete tate cee mmm mee me ee ee wm mm we re ee ee eee Incorrect reaction by partner; the CP 525 never outputs a system command. meee mee eee eee eee eee ee we Check whether the error is being caused by a disturbance or an incorrect reaction of the partner. Verify with an interface test device ('FOXPG') tapped into the transmission line. Verify incorrect reaction of partner if necessary with an inter- face test device ('FOXPG') tapped into the transmission line. 113B8576539-03 No. for ANZW No, for SYSTAT Computer Link with RK 512 No. from REPTEL | Description CH 27H Selector on STOP/PGR during PC job 29H 37H oe ee Errors in the reply telegram from the partner, detected by the CP: a) Synchron error by partner, since - reply telegram arrived, though no job running or ~ the (follow-on) FETCH telegram has not yet been sent or - a follow-on reply telegram was received after a FETCH telegram was sent or - a reply telegram was received after a follow-on FETCH telegram was sent If the partner detects an error when processing a job from another device, it sends a reply telegran back to the CP 525 with the error number in the 4th byte. The CP generates a no. for SYSTAT and for AN@W from this: 36H a) Partner detects synchron error - | order of telegrams is wrong 114B8576539-03 Gomputer Link with RK 512 Remedy Switch the selector to RUN This error can be signalled following a cold restart at your PC or at the partner. It is a normal reaction during start-up; you do not need to do anything. During normal operation the error can also occur as a result of older error statuses that were detected by the partner. Otherwise you can assume that the partner is reacting incorrectly. It is possible that the error will not occur with jobs < 128 bytes. mee eee eee eee eee This error can be signalled during a cold restart at your PC or Le at the partner. It is a normal reaction during start-up; you do not need to do anything. During normal operation the error can also occur as a result of older error statuses that were detected by the partner. Otherwise you can assume that the partner is reacting incorrectly. 115B8576539-03 Computer Link with RK 512 No. for , No. for , No.from ANZW SYSTAT REPIEL | Description CH 38H 2AH b) Up to now there has been no cold restart at the partner. with CP 525 as partner: Since the power up no "SYNCHRON" HDB has run or the mode sel- ector is switched to STOP/PGR. DH 2FH No reply telegram came from the partner within the monitoring time after a FETCH telegram was sent. 116B8576539-03 Computer Link with RK 512 Remedy Carry out a cold restsrt at the partner PC or switch the selector on the CP to RUN. Is the partner a very slow device? This error is often indicated as the result of an older error. For example, procedure receive errors (FOH to FFH) can be indi- cated after a FETCH telegram has been sent because the reply telegram could not be received owing to a disturbance > there is a timeout. This error can sometimes occur when a cold restart has been carried out at the partner before it could reply to the last FETCH telegram received. 117B8576539-03 Computer Link with RK 512 No. for , No. for . ANZW SYSTAT Description Errors in data exchange CP <> partner: EH Errors detected by the procedure during ElH E2H the sending of a telegram and signalled to the interpreter: a) Errors during the link establishment - after STX was sent, NAK or some other character (except DLE or STK) was received or - the reply came too soon or ~ an initialization conflict has occurred b) Timeout (QVZ): after sending STX the partner did not reply within the acknowledgement time mre emt erm meme ene te ee ee 118B8576539-03 Computer Link with RK 512 Remedy Verify incorrect reaction of partner if necessary with an interface test device ('FOXPG') tapped into the transmission line. Partner is too slow or not ready to receive or there is a line break. Verify incorrect reaction of partner if necessary with an interface test device ('FOXPG') tapped into the transmission line. 119B8576539-03 No. for ANZW No. for SYSTAT Computer Link with RK 512 Description EH E3H E4H E5H c) Aborted by partner: during transmission one or more charac- ters were received from the partner (incl. NAK) ee meee eee eee ee ewe ee d) Errors at end of link: - the telegram was rejected at the end by the partner with NAK or some other character (except DLE) or ~ the acknowledgement character was received too soon e) Timeout at end of Link: after link termination with DLE ETX no reply was received from the partner within the QVZ time Transmission error: a transmission error (parity error, stop bit error, overflow error) was detected. If this occurred during transmission or reception, repetitions will be started. If a corrupted character is received in the idle state, the error is signalled immediately to ensure that disturbances on the line are detected as early as possible. 120B8576539-03 Computer Link with RK 512 Remedy - Check whether the partner is also indicating an error, it is possible that not all the data sent have arrived (e.g., break in the line) or - Partner is reacting incorrectly. Verify this if necessary with an interface test device ('FOXPG') tapped into the transmission line. meee eee ee - Check whether the partner is also indicating an error; it is possible that serious disturbances have occurred or - Partner is reacting incorrectly. Verify this if necessary with an interface test device ('FOXPG') tapped into the transmission line. oom mecca - Partner is too slow or has a fault. Verify incorrect reaction of partner if necessary with an interface test device ('FOXPG') tapped into the transmission line. ~ Disturbances on the line result in repetitions of the telegram and threfore reduce the actual data throughput. The chance of an undetected error increases. Change the configuration or 7 re-lay the cable. . - Gheck whether the data rates, parity and number of stop bits are the same at both devices. 121B8576539-03 Computer Link with RK 512 No. for , No. for ANZW SYSTAT Description FH FFH BREAK The communication cable (receiver cable) to the partner has a break. This error number is repeated until the fault is cleared. 122B8576539-03 Computer Link with RK 512 Remedy Re-establish the conection between the devices or switch on the partner. Check whether the current flows in TIY operation. 123B8576539-03 Computer Link with RK 512 8.2 Error Messages for SYSTAT, ANZW and REPTEL Arranged According to the Numbers for SYSTAT No. for SYSTAT No. for ANZW No. for REPTEL Description 01H 02H 03H 04H 05H 06H 2H 3H 4H ee eee 5H 6H OAH 14H OCH 14H OCH OAH OCH OAH Parameter assignment errors recognized by the CPU of the PC and signalled to the CP: a) Source/dest. type (e.g. ext. DB) illegal area (start address, length) illegal (negative value) DB/DX not present or illegal (e.g. DBO, DB1, DX0) or other data type not present or illegal eee eee a ee DB/DX too short: (start address + length > area or area too short with other data type (start address + length > area Access to area not possible for user: e.g., hardware memory too small or I/O module not plugged in omen ee mee cm mene mee ee Wrong condition codeword: group message for all errors attributable to this ANZW emma ene meme eee Error code from the CPU to the CP that the CP camot interpret 124B8576539-03 Computer Link with RK 512 Remedy - Check parameter assignment on CPU and CP and if necessary correct or . - Partner has illegal parameters in the telegram header Find the permissible data types in the job tables (Section 2.6). - Check parameter assignment on CPU and CP; if necessary set up block - Partner has wrong parameters in the telegram header Find the permissible data types in the job tables (Section 2.6). te me meee ree ee ees see eee - Check parameter assignment on CPU and CP if necessary check block/area or - Partner has wrong parameters in the telegram header owns mem meme emma meen eee mere eee eee eee - Check parameter assignment on CPU and CP or - Partner has wrong parameters in the telegram header Find the permissible start addresses and lengths in the job tables (Section 2.6). ee eee mee rere mre eee eee ee Check whether condition codeword is valid. Evaluate PAFE in handling block ( STEP 5 user program). 125B8576539-03 No. for SYSTAT No. for No. for ANZW REPTEL Computer Link with RK 512 Description 10H 11H 12H 13H 14h 6H 6H 6H eee 6H 6H Errors detected by CP during data exchange between CPU and CP: a) Timeout for handshake on CP b) ALL job without request or direct job despite overload c) Wrong sequence for handshake by CFU d) Unknown job type or illegal job number for direct job ne eee ee ee ee ee ee e) Illegal acknowledgement from CPU during handshake 15H 16H 17H 1EH 1FH oe ee System errors at start of job Processing: a) Number of direct jobs that can be processed simultaneously too large for CP 524/cP 525 b) Current job was terminated with error status when CP was cold restarted (power on) or cold restarted from PG c) Area is masked by STEP 5 program (bit 7 in AN2W = 1) d) Field length for "Read SYSID" (RECEIVE DIRECT 223) too small e) "Read date/time" (RECEIVE DIRECT 218) illegal, CP is set as time slave 126B8576539-03 Computer Link with RK 512 Remedy Check whether RECEIVE ALL or SEND ALL are called in your STEP 5 program; evaluate the PAFE in the handling block ee wre ome cme meee eet oem sere emma mee meme ee Check STEP 5 program, e.g., errors in handling block (Message also possible after transfer from PG to CP). wees meee wee renee eee eee eer eee ee eee ee eee ree re ere meme ee eee ee Check STEP 5 program, e.g., incorrect parameters for handling block. cme ewe ewe ee wee wee wee ewe wee ee mn mm ome tee ome wee tee tree Check STEP 5 program. Modify STEP 5 program so that maximm 10 direct jobs rm simultaneously. There is no remedy with power on. When cold restarting the CP La from the PG you make sure that no more CPU jobs are running before writing to an interface. The SYNCHRON HDB clears the job statuses in the dual-port RAM, but not the SYSTAT entry. meee eee meee eee mee eee ee cee ee rere rete meme ce ewer mere meme ees ee eee me For SYNCHRON the block size should be greater than or equal to 128 bytes or do without "Read SYSID" (data are nevertheless available in the dual-port RAM). ~ this then applies to this module; check whether the CP on the other interface has been set to slave. 127B8576539-03 No. for SYSTAT No. for ANZW No. from Computer Link with RK 512 Description 20H 21H 22H 23H 24H 26H Parameter ass. errors in the STEP 5 prog. detected by the CP (e.g. in the pseudo B/W parameters) or job block (CP 525 user program) a) No parameters were entered in the CP 525 user program for this direct job (under this job number) Error in data type (DB, OB...): ~ unknown data type or - data type not allowed (e.g. ext. DB) or - data type not allowed in HDB parameters in connection with data type in the job block (CP 525 user program) me eee ee ee ee re eee Start address specified too high for required data type or start address or DB/DX no. too low Coordination flags not allowed with this data type or wrong bit number specified e) CFU number specified too high with pseudo R/W parameters ) Transmission length > 64 Kbytes too long for CP 525 g) Length of telegram header too great or length too great for type specified (in own PC) 128B8576539-03 Gomputer Link with RK 512 Remedy Create parameters for this job with COM 525 or select other job number. Find the permissible data types and their combinations in the job tables (Section 2.6). ets reese ere ee eee ee eee Find the permissible start addresses and DB/DX nos. in the job tables (Section 2.6), which can be specified in the CP 525 user program or STEP 5 program (with pseudo R/W parameters). ee Coordination flags are not permissible for all data types (see Section 2.6). Check whether the bit number (0 to 7) has been specified correctly when the pseudo R/W function is used. If necessary, split the job into several jobs with smaller lengths. mw eee eee eee eee Find the permissible lengths in the job tables (Section 2.6) to be specified in the HDB or for the pseudo R/W parameters. If necessary split the job into several jobs with smaller lengths. 129B8576539-03 No. for SYSTAT No. for ANZW No. in Computer Link with RK 512 Description 27H CH Selector on STOP/PGR during PC job 28H Error when sending a command telegram. A corresponding procedure error mumber was entered in SYSTAT immediately before (see error numbers EO to E5 and F8 to FF). 29H oe ee 2BH 2CH 2DH BH BH oe oe oe BH eee BH ee me oe oo oy Errors in the reply telegram from the partner, detected by the CP: a) Synchron error by partner, since ~ reply telegram arrived, though no job running or - the (follow-on) FETCH telegram has not yet been sent or ~ a follow-on reply telegram was received after a FETCH telegram was sent or - a reply telegram was received after a follow-on FETCH telegram was sent b) Error in format of reply telegram received: first byte not OOH or FFH fo shy owe mm ine me cme mee eet ee ee ese em eet c) Reply telegram received after FETCH job has too many data d) Reply telegram received after FEICH job has too few data e) Reply telegram received after SEND job arrived with data 130B8576539-03 Computer Link with RK 512 Remedy Switch the selector to RUN. See remedy for previous procedure error number. This error can be signalled following a cold restart at your PC, with long telegrams, or at the partner. It is a normal. reaction during start-up; you do not need to do anything. During normal operation the error can also occur as a result of older error statuses that were detected only by the partner. Otherwise you can assume that the partner is reacting incorrectly. It is possible that the error will not occur with jobs < 128 bytes. ee meee ee ee eee eee meee ee meee ee ee Verify incorrect reaction of partner if necessary with an inter- face test device (FOXPG') tapped into the transmission line. Verify incorrect reaction of partner if necessary with an inter- face test device ('FOXBG') tapped into the transmission Line. Verify incorrect reaction of partner if necessary with an inter- face test device ('FOXPG') tapped into the transmission line. Verify incorrect reaction of partner if necessary with an inter- face test device (FOXPG') tapped into the transmission Line. 131No. from REPTEL Computer Link with RK 512 Description When processing a PC job: Errors in transfer/reception of data via the dual-port-RAM > handshaking error with the CPU. A more detailed error number was entered immediately before in systat (error numbers 1 to 5 and 10, 14, 16, 17 - see previous pages) No reply telegram came from the partner within the monitoring time after sending a FETCH telegram. B8576539-03 No. for , No. for SYSTAT ANZW 2EH 2FH DH 30H 9H 31H AH 32H OAH ---- If the partner detects an error when processing a job from another device, it sends a reply telegram back to the CP 525 with the error member in the 4th byte. The CP generates a no. for SYSTAT and for ANZ from this: a) DB / DX disabled by coordination flags b) Hardware (DMA) error at the partner or with CP 525 as partner: ~ source/dest. type illegal - OY Memory error in partner PC - or error in handshake between CP/CPU at partner or - partner PC is in STOP state mma erm rm ee a re eee ee 132B8576539-03 Computer Link with RK 512 Remedy See the remedy for the preceding error number. Is the partner a very slow device? This error is often indicated as the result of an older error. For example, procedure receive errors (FOH to FFH) can be indicated after a FETCH telegram has been sent because the reply telegram could not be received owing to a disturbance > there is a timeout. This error can sometimes occur when a cold restart has been carried out at the partner before it could reply to the last FETCH telegram received. In the partner program: after processing the last transmission data reset the coordination flags. In the STEP 5 program: repeat the job. wore ee eee mmr mm meee eee ee eee ese - Check whether partner can transfer the required data type - Check partner's hardware configuration - Switch mode selector at partner PC to RUN 133B8576539-03 No. for No. for ANZW No. from Computer Link with RK 512 Description 32H 33H 34H 35H 36H 37H AH BH = BH OCH 14H 16H 10H 34H ae eee 36H c) Memory access error at partner (memory not present) with CP 525 as partner: - wrong area for condition code- word or - data area does not exist (except DB/DX) or - data area too small (except DB/DX) fm cn eee ime ates eee DB/DX access error at partner (DB/DX does not exist or too short) with CP 525 as partner: - DB/DX does not exist or - DB/DX too short or - DB/DK no. illegal Errors in the telegram header, detected by partner: first command letter in header wrong mmm eee Error in telegram header: second command letter in header wrong fomiwe mmm meee weer esate yee Partner detects wrong telegram length (total length) Partner detects synchron error - order of telegrams is wrong ----bL- ee L k - 134B8576539-03 Computer Link with RK 512 Remedy Check whether the required data area exists on the partner and whether it is long enough; or check the job block (CP 525 user program); or the pseudo R/W parameters (STEP 5 user program). Check the length specified in the HDB. eee eee meee emer eee ee ee eee eee ee Check whether the required data block exists on the partner and whether it is long enough; or check the job block (CP 525 user program); or the pseudo R/W parameters (STEP 5 user program). Check the length specified in the HDB. Check whether the error is being caused by disturbances or incorrect reaction of the partner. Verify with an interface test device ('FOXPG') tapped into the transmission line. men mem arm mmm eet ee em eee Check whether the error is being caused by disturbances or incorrect reaction of the partner. Verify with an interface test device ('FOXPG') tapped into the transmission line. come ree were me eee ree eee tee ee ee Check whether the error is being caused by disturbances or incorrect reaction of the partner. Verify with an interface test device ('FOXPG') tapped into the transmission line. This error can be signalled during a cold restart at your PC or at the partner. It is a normal reaction during start-up; you do not need to do anything. During normal operation the error can also occur as a result of older error statuses that were detected only by the partner. Otherwise you can assume that the partner is reacting incorrectly. ee ee ee mee eee eee ee ey eee mee 135B8576539-03 No. for SYSTAT No. for ANZW No. from REPTEL Computer Link with RK 512 Description 38H CH BH BH 12H owe ee ee ??7H i) Up to now there has been no cold restart at the partner. with CP 525 as partner: since the power up no "SYNCHRON" HDB has run or the mode selector is switched to STOP/PGR. j) Partner signals "system command illegal" k) Unknown error number received in reply telegram 136B8576539-03 Computer Link with RK 512 Remedy Carry out a cold restart at the partner PC or switch the selector on the CP to RUN. ee eee ee meee eee eee meee eee eee ee ee This is an incorrect reaction by partner, the CP 525 never out- puts a system command. ree ee se eae Check whether the error is being caused by disturbances or incorrect reaction of the partner. Verify with an interface test device ('FOXPG') tapped into the transmission line. 137B8576539-06 No. for SYSTAT No. for ANZW No. for Computer Link with RK 512 Description 40H 41H 42H 43H 44H 10H 16H 16H 10H 10H Error in the command telegram of the partner. A reply telegram is sent to the partner with the specified error no. in the 4th byte.. a) Error in lst command byte not OOH or FFH b) Error in 3rd command byte: command letter is not "A" or "0" or E" or "xX" c) Error in 3rd command byte in follow-on telegram: command letter not as in lst command telegram d) Error in 4th command byte: command letter wrong e) Error in 4th command byte in follow-on telegram: command letter not as in first command | telegram 138B8576539-03 Computer Link with RK 512 Remedy For more information on command telegrams, see Section 4 in this user's guide. Basic format error in partner's header. Verify incorrect reaction of partner if necessary with an interface test device ('FOXPG') tapped into the transmission line. ene oe memes mee meee ewe ese ee nee me me mee ae Basic format error in partner's header. Verify incorrect reaction of partner if necessary with an interface test device ('FOXPG') Basic format error in partner's header. Verify incorrect reaction of partner if necessary with an interface test device ('FOXPG') tapped into the transmission line. Basic format error in partner's header or a command combination is requested, which is not allowed with the CP525. Check the permissible commands in the appropriate tables (Section 2.6) Verify incorrect reaction of partner if necessary with an inter- face test device (FOXPG') tapped into the transmission line. Basic format error in partner's header. Verify incorrect reaction of partner if necessary with an interface test device (FOXPG') tapped into the transmission line. em cm mere tee eee ee eee ee 139B8576539-03 No. for SYSTAT No, for ANZW No. for REPTEL Computer Link with RK 512 Description 45H 46H wwe ow 47H 48H ne oe 49H 4BH 4DH 14H OCH 34H we ee oe OCH mo OCH a 12H 34H 34H 34H ) Error in 5th command byte: DB/DK no. illegal (e.g. 00) g) Error in 5th command byte: start address too high h) Error in 7th + 8th com. bytes: specified length too high 1) Error in 9th + 10th comm. bytes: coordination flag cannot be specified with this data type or the bit number of the coor- ination flag is too high (perm. value range 0 to 7) meee yj) Error in 10th command byte: CPU no. too high (permitted values 0,1,2,3,4,F) ome eee ete erm re me ee eee ee 1) Send telegram was longer than expected, i.e., more data was received (poss. with follow-on telegrams) than indicated in the telegram header m) Send telegram was too short or < 128 bytes; i.e. less data received (poss. with follow-on telegrams) than indicated in the telegram header n) Fetch telegram received with information data. 140B8576539-03 Computer Link with RK 512 Remedy Find the permissible DB/DX numbers in the job tables (Section 2.6). 2.6). ee em eee wre eee ee re eee ee ee Basic error in partner's header structure. Find the in the job tables (Section 2.6) when coordination flags are allowed. cane emer em meee eee ee teem ee mee mes os oom ee ee ed meme eee eee weer eeee eeeeeeme Must be corrected at partner 141B8576539-03 No. for SYSTAT No. for ANZW No. for REPTEL Computer Link with RK 512 Description 4EH _ = = 4FH 50H 51H 36H Other errors when processing the partner job a) CP has received command telegram, while mode selector was set to STOP/PGR perme ome cme ee mere meee b) Command telegram was received, although the CPU of the PC has not run a "SYNCHRON" HDB pees awe ee mee cee cee ee c) Error sending the (follow-on) reply telegram, a corresponding procedure error number was entered in SYSTAT immediately before (error numbers EO to E5, F8 to FF) femme treme ee mee d) - synchron error by partner, new (follow-on) command telegram arrived, although previous (follow-on) reply telegram had not been sent by CP 525 "or - a normal command telegram was received, although a follow-on command telegram was expected or - a follow-on command telegram arrived, although a command telegram was expected *) The CP has not yet been synchronized. The SYSTAT cannot be read by the handling blocks. These error messages must be read direct from the dual-port RAM. (Structure from address F660H as for read SYSTAT"), 142B8576539-03 Computer Link with RK 512 Remedy Switch mode selector on the CP to RUN In the STEP 5 program, "SYNCHRON" calls must be programmed in the start-up organization blocks (0B20, 0B21, OB22). Following this a cold restart must be carried out (the PAFE byte in the SYNCHRON HDB may have to be evaluated). ere em ome me mee tee meee nee care eee tem eee meet emt cme ene eee ems mem mam ms oe me, See remedy for error number entered immediately before in SYSTAT (SYSTAT no. EO to E5 and F8 to FF). CN A eA ee This error can be signalled following a cold restart at your PC if long telegrams are to be sent or during a cold restart at the partner. This is a normal reaction during start-up; you do not need to do anything. During normal operation the error can also occur as a result of older error statuses which were only detect- ed by the partner. Otherwise you can assume that the partner is reacting incorrectly. It is possible that the error will not occur with jobs less than 128 bytes. 143B8576539-03 No. for SYSTAT No. for ANZW No. for REPTEL Computer Link with RK 512 Description 52H 32H DB/DX disabled by coordination flags 53H When processing a partner job: errors during transfer/reception of data via the dual-port RAM; hand- shake error with the CPU of the PC; a more detailed error number was entered in SYSTAT immediately before (Error numbers 1 to 5 and 10, 14, 16 - mumber for REPTEL - see previous pages). SEH A correct telegram with a length less than the header length in the (follow-on) command telegram was received (< length 4 with follow-on telegrams or reply telegrams; < length 10 with command telegrams). The telegram is ignored. Jobs currently running are not aborted. 5SFH 34H A correct telegram with a length > 128 bytes was received. The telegram could not be evaluated. The job being processed is aborted. 144B8576539-03 Computer Link with RK 512 Remedy In your own STEP 5 program: reset the coordination flags again after processing the last transmitted data. In the partner program: repeat the job When starting up for the first time, make sure that the coordina- tion flags are distributed on the individual processors, CPs, IPs and the coordinator, the jumper settings are correct and the coordination flags used in the start-up OBs (0B20, 0B21, 0B22) are reset (see also instructions CP 524/CP 525). See remedy for the error number entered immediately before in SYSTAT. Verify the incorrect reaction of the partner, if necessary, with Zz an interface test device ('FOXPG') tapped into the transmission line. Verify the incorrect reaction of the partner, if necessary. with an interface test device ('FOXPG') tapped into the transmission line. 145B8576539- No. for SYSTAT 03 No. on PG Computer Link with RK 512 Description BOH B1lH B2H B3H Err. 722 transfer error Error messages when sending a telegram from the CP to the Fe: a) Link establishment with STK was either not acknowledged by the PG within 300 ms acknowledgement monitoring time) or was not acknowledged with DLE ACK or DLE NAK b) Transmission (CP -> PG) was aborted by PG - with NAK mee ec ee ee eee ee ee c) The link termination with DLE ETX was acknowledged by the PG with DLE NAK me em remem ee mee ee ee d) The link termination with DLE ETX was not acknowledged by the PG with DLE ACK or DLE NAK within 300 ms (acknowledgement monitoring time). B4H Err. 722 transfer error Error messages when receiving a telegram from the Fe: a) Transfer error when receiving (CP aborts with DLE NAR). For further information see the description "COM 525 messages" in this manual. 146B8576539-03 Computer Link with RK 512 Remedy - Check cable - Load COM 525 - Hardware error at PG or CP eee eee ee ee mere ee remem wremwmeteesee eee eeeee - Check cable - Load COM 525 ~ Hardware error at PG or CP Repeat transfer (otherwise: see BOH) 147Computer Link with RK 512 B8576539-03 No. for , No. on SYSTAT PG Description Errors carrying out a job from the PG: B5H_ {IF.007 a) A function is to be carried out which is CP funct. unknown to the CP 525 or there is a trans- unknown fer error in the exchange of telegrams B6H {ERR. 709 [| b) The user memory of the CP 525 is full cP memory full B7H |ERR. 027 | c) The write access by the PG camot be EPROM carried out, because there is no RAM sub- plugged module plugged in as the user memory of in the CP 525 (either EPROM or no submodule plugged in) B8H [ERR. 721 | d) The mode selector on the CP is set to CP switch "STOP" or "PGR" (during cold restart from set to the PG) "STOP" 148B8576539-03 Computer Link with RK 512 Remedy COM 525 loaded? Repeat, transfer meer ee eee ee ee ee - Plug in submodule with greater capacity - Erase unnecessary module files on the CP ee nee meee ee ee re ee ee Switch mode selector on the CP to "RUN" 149B8576539-03 No. for SYSTAT No. for ANZW Computer Link with RK 512 Description con? ___ = ClH C2H C3H can? C5H cen) c7H*) Hardware errors on the module: a) Error testing the module's operating system EPROM eee eee ee eee wee ee ) Error in memory submodule while program is ruming g) EPROM memory submodule empty or contents unknown h) Applies only to CP 524: interpreter not permitted for this CP *); These errors are signalled only on interface 1. The CP was not. synchronized, the data cannot be read by the handling block. These error messages must then be read directly from the dual- port RAM (structure from address F660H onwards as for "read SYSTAT"). 150B8576539-03 Computer Link with RK 512 Remedy Wrong or defective operating system EPROM Replace EPROM. orm em eee eee eee ee eee ee crm mmm ee eee cee mem eee ee ee eee meee eee meme cee eee nme me me mee mes mn eee mms tem emt ee et eee ee eee re ee eee eee ~ Use permitted submodule type - Submodule or submodule controller defect emcee eee mee meee meme ett eee rere wwe mew et oe - Check whether this is the correct EPROM module - Check whether module is programmed With submodules which are programmed for the CP 525-2 and used in the CP 524, this error number appears if interface 1 is not programmed. come ere meee eee ee rm erm tte eee ee ee ee ee ee 151B8576539-03 Computer Link with RK 512 No. for , No. for SYSTAT ANZW Description cau) - i) Only applies to CP 524: interface module (identifier) unknown or module not plugged in C9H - j) Interface not loaded can? - k) Memory submodule not plugged into CP *) : These errors are only signalled on interface 1. The CP was not synchronized, the data cannot be read by the handling block. These error messages must then be read directly from the dual- port RAM (structure from address F660H onwards as for "read SYSTAT"). 152B8576539-03 Computer Link with RK 512 Remedy - Check whether correct module, if "yes": module defect - Check whether module plugged in correctly mee meee ces mmm nme ete mmm eee eee eee eee eee Load interface if necessary Caution: the entry in SYSTAT is not cleared by loading the interface, but only by RESET DIRECT 200 Check whether submodule is plugged in; if "yes": submodule defect (or submodule controller defect) - replace submodule 153B8576539-03 No. for SYSTAT No. for ANZW Computer Link with RK 512 Description DOH Incompatible procedure - interpreter: procedure and interpreter on the GP 525 cannot work together. EOH ElH E2H oe Errors in data exchange CP <> partner: 1. Errors detected by the procedure during the sending of a telegram and signalled to the interpreter: a) The first repetition has been sent: - when sending a telegram an error was recognised or - the partner requests a repetition by means of a negative acknowledgement character (NAK) b) Errors during the link establishment - after SIX was sent, NAK or any other character (except DLE or STX) was received or - the reply came too soon or - an initialization conflict has occurred c) Timeout (QVZ): after sending STX the partner did not reply within the acknowledgement time ome meer ee ee 154B8576539-03 Computer Link with RK 512 Remedy Check procedure/interpreter on the CP 525 and if necessary replace. A repetition is not an error. It can, however, point to distur- bances on the transmission line or to an incorrect reaction by the partner. If, after the maximm member of repetitions, the telegram could not be transferred, an error number is signalled that describes the error which occurred first. Note: when coupled to an AS 512C module the AS 512C module sometimes xequests a repetition owing to overload at high data rates. ee wee eee ee eee ee ee ee rere eee eee oe Verify incorrect reaction of partner if necessary with an interface test device ('FOXPG') tapped into the transmission line. Partner is too slow or not ready to receive or there is a line break. Verify incorrect reaction of partner if necessary with an interface test device ('FOXPG') tapped into the transmission line. cee cae ems meme ee eee eee meee amc meme mim ements, came ee eos ees 155Computer Link with RK 512 Description B8576539-03 No. for , No. for SYSTAT ANZW E3H EY E4H EH E5H EH FOH - ew ee d) Aborted by partner: during transmission one or more charac- ters were received from the partner (incl. NAK) re eee mee ee ee ee ee e) Errors at end of link: - the telegram was rejected at the end by the partner with NAK or some other character (except DLE) or - the acknowledgement character was received too soon ) Timeout at end of link: after Link termination with DLE ETX no reply was received from the partner within the QVZ time 2. Errors occurring when a telegram is received, detected by the procedure and signalled to the interpreter: a) Expecting the first repetition: when receiving a telegram an error was detected and the CP 525 requested a repetition by sending a negative acknowledgement (NAR). ce me ome mmr eee ee 156B8576539-03 Computer Link with RK 512 Remedy - Check whether the partner is also indicating an error; it is possible that not all the data sent has arrived (e.g. break in the line) or - partner is reacting incorrectly. Verify this, if necessary, with an interface test device ('FOXPG') tapped into the trans- mission line. ee - Check whether the partner is also indicating an error; it is possible that serious disturbances have occurred or - partner is reacting incorrectly. Verify this, if necessary with an interface test device ('FOXPG') tapped into the transmission line. - Partner is too slow or has a fault. Verify incorrect reaction of partner if necessary with an interface test device ('FOXPG') tapped into the transmission line. mee eee eee A repetition is not an error. It can, however, point to distur- 7 bances on the transmission line or to an incorrect reaction by the partner. If, after the maximum mmber of repetitions, the telegram could not be transferred, an error nusber is signalled which describes the error which occurred first. 157B8576539-07 No. for SYSTAT No. for ANZW Description F1lH F2H F3H F4H F5H b) Errors during link termination: - in the idle state one or more characters (except NAK or STX) were received or - following reception of STX the partner sent further characters without waiting for the reply DLE c) Logical error while receiving: after receiving DLE a further character was received (except DLE, ETB, ETX) d) Character timeout (ZVZ): ~- two successive characters were not received within the ZVZ or - during link establishment the 1st character after DLE was not received within the ZVZ e) Block check character (BCC) error: the value of the BCC calculated internally does not agree with the one received from the partner at the end of the Link (only with 3964R procedure) ) Block monitoring time has expired. After a command telegram was sent no reply tele- gram was received from the partner within the monitoring time. meee eee 158B8576539-07 Remedy Verify incorrect reaction of partner if necessary with an inter- face test device ('FOXPG) tapped into the transmission line. Check whether the partner always doubles DLE in the telegram header and in the data string or terminates the link with DLE ETX. Verify incorrect reaction of partner, if necessary with an interface test device (FOXPG) tapped into the transmission line. eae Partner is too slow or has a fault. Verify this if necessary with an interface test device ('FOXPG) tapped into the transmission line. : cme eee ee Check whether the connection is badly affected by interference; if so, error codes FE are sometimes obtained. Verify incorrect reaction of partner if necessary with an interface test device ('FOXPG) tapped into the transmission line. meee eee Assign the same repetition amount of parameters to the partner as to the CP. Verify incorrect reaction of partner if necessary with an interface test device (FOXPG) tapped into the transmission line. 159B8576539-03 No. for No. for Computer Link with RK 512 Description F6H F8H f) There is no free receive buffer available: after receiving STX there was no empty receive buffer available for the procedure during link establishment and during a further waiting period eee ere eee cre meer meme rm emcee meee eee ee Wrong end identifier (ETB) was received: a received telegram was completed with the end identifier ETB. The telegram is ignored, the job being processed is not aborted Transmission error: a transmission error (parity error, stop bit error, overflow error) was . detected. If this occurred during transmission or reception repetitions will be started. If a corrupted character is received in the idle state, the error is signalled immediately to ensure that disturbances on the line are detected as early as possible. BREAK The commmication cable (receiver cable) to the partner has a break. This error number will be repeated until the fault is cleared. 160B8576539-03 Computer Link with RK 512 Remedy This error can only occur if the transmission is extremely badly disturbed because of short term overload of the RK 512 interpreter. Correct the problem by changing the system configur- ation or re-laying the cables. ee mmm eee eee ee wee tte eee ee tee eee ee Modify the partner since RK 512 does not recognise the data control character ETB. Disturbances on the line result in repetitions of the telegram and therefore reduce the actual data throughput. The chance of an undetected error increases. Change the configuration or re-lay the cable. Check whether the data rates, parity and number of stop bits are the same at both devices. L7 Re-establish the connection between the devices or switch on the partmer. Check whether the current flows in TIY operation. 161B8576539-03 Computer Link with RK 512 8.3 Error Messages for SYSTAT and REPTEL Arranged According to Numbers for REPTEL No. for REPTEL No. for SYSTAT Description OAH 01H 04H 06H Parameter assignment errors detected by the CPU of the PC and signalled to the CP: a) Source/dest. type (e.g. ext. DB) not permissible area (start address, length) not permis- sible (negative value) re ee mere eee eee ee b) Access to area not possible for user: e.g. hardware memory to small or 1/0 module not plugged in eae eee ee Exror indication from the CPU to the CP, which the CP cannot interpret 10H Errors detected by the CP during data ex- change between CPU and CP: a) Monitoring time for handshake elapsed on CP 162B8576539-03 Computer Link with RK 512 Remedy - Check parameter assignment on CPU and CP and if nec. correct or ~ Partner has illegal parameters in the telegram header Find the permissible data types in the job tables (Section 2.6). - Check parameter assignment on CPU and CP or - Partner has wrong parameters in the telegram header Find the permissible start addresses and lengths in the job tables (Section 2.6). Evaluate PAFE in handling block (STEP 5 user program). Check whether RECEIVE ALL or SEND ALL is called in your STEP 5 7 program; evaluate PAFE in the handling block. 163B8576539-03 Computer Link with RK 512 No. for , No. for REPTEL SYSTAT Description Parameter assignment errors detected by the CPU of the CP and signalled to the CP: OCH 02H a) Data type does not exist or not permissible 03H b) Area too short (start address + Length) > area 164B8576539-03 Computer Link with RK 512 Remedy - Check parameter assignment of CPU and CP, if nec. set up block - Partner has wrong parameters in telegram header Find the permissible data types in the job tables (Section 2.6). wen - Check parameter assignment on CPU and GP; if necessary check block/area or ~ Partner has incorrect parameters in telegram header 165B8576539-03 No. for REPTEL No. for SYSTAT Computer Link with RK 512 Description OCH 46H 48H 49H Errors in the command telegram of the part- ner; reply telegram is sent to the partner with the specified error number in the 4th byte a) Error in 5th command byte: start address too high b) Error in 9th + 10th command byte: specifying a coordination flag is not per- missible with this data type or the bit number of the coordination flag is too high (permitted value range 0 to 7) c) Error in 10th command byte: CPU no. too large (permitted value range 0,1,2,3,4,F) 166B8576539-03 Computer Link with RK 512 Remedy Find the permissible start addresses in the job tables (Section 2.6). mew ee meen mm ese eee eee Basic format error in the partner header. Find in the job tables (Section 2.6) when a coordination flag is permissible. Basic format error in the partner header. 167B8576539~-03 Computer Link with RK 512 No. for , No. for REPTEL SYSTAT Description 10H 40H d) Error in 1st command byte: is not OOH or FFH 43H e) Error in 4th command byte: command letter wrong 44H f) Error in 4th command byte in follow-on telegram: command letter not as in the ist command telegram 168B8576539-03 Computer Link with RK 512 Remedy Basic format error in the partner header. Verify the incorrect reaction of the partner if necessary with an interface test device ('FOXPG') tapped into the transmission line. Basic format error in the partner header or a combination of commands was requested which is not allowed with the CP 525. Find the permissible commands in the command tables (Section 2.6). Verify the incorrect reaction of the partner if necessary with an interface test device ('FOXPG') tapped into the transmission line. Basic format error in the partner header. Verify the incorrect reaction of the partner if necessary with an interface test device ('FOXPG') tapped into the transmission line. 169B8576539-06 Computer Link with RK 512 No. for , No. for REPTEL | SYSTAT Description 12H 4AH g) System command "XM" not permissible Parameter assigneent errors detected by the CPU of the PC and and signalled to the CP: 14H 02H a) DB/DX not present or illegal (e.g. DBO, DB1, DX0) 03H b) DB/DX too short: (start address + length > area Errors in the command telegram from the part- ner. A reply telegram is sent to the partmer with the error no. in the 4th byte: 45H a) Error in 5th command byte: DB/DX no. illegal (e.g. 00) 16H 41H | b) Error in 3rd command byte: command letter is not "A" or "E" or "X" or "ng" 42H c) Error in 3rd command byte of a follow-on telegram: lst command letter not as in the ist command telegram 170B8576539-03 Computer Link with RK 512 Remedy System command is only meaningful for AS 512 - Check parameter assignment on CPU and CP, if necessary set up block or - Partner has wrong parameters in the telegram header Find the permissible data types in the job tables (Section 2.6). - Check parameter assignment on CPU and CP if necessary check block/area or - Partner has wrong parameters in the telegram header Find the permissible DB/DX numbers in the job tables (Section 2.6) ewes enema eee meee eee eee mete ems oe ee Basic format error in the partner header. Verify the incorrect reaction of the partner if necessary with an interface test device (FOXPG') tapped into the transmission line. Basic format error in the partner header. Verify the incorrect reaction of the partner if necessary with an interface test device ('FOXPG') tapped into the transmission line. 171B8576539-03 Computer Link with RK 512 No. for , No. for REPTEL SYSTAT Description Other errors during the processing of the partner job 2AH 4EH a) CP has received command telegram, while mode selector was set to STOP/PGR 4FH b) Command telegram was received, however, the CPU of the PC has not yet run the "SYNCHRON" HDB 32H 52H DB/DK disabled by coordination flags Errors in command telegram of the partner. A reply telegram is sent to the partner with the specified error in the 4th byte. 34H 47H a) Error in 7th + 8th command byte: length specified too great 4BH b) Send telegram was longer than expected, i.e. more data were received (possible with follow-on telegrams) than were indi- cated in the telegram header. em mmm eee eee ee ee ee 172B8576539-03 Computer Link with RK 512 Remedy Switch the mode selector to RUN. eee meee mre meme ete eee eee eee In the STEP 5 program, "SYNCHRON calls must be programmed in the start-up organization blocks (0B20, OB21, 0B22). Following this a cold restart must be carried out (the PAFE byte in the SYNCHRON HDB may have to be evaluated). In your own STEP 5 program: reset the coordination flags again after processing the last tranmission data In the partner program: repeat the job When starting up for the first time, make sure that the coordina- tion flags are distributed on the individual processors, CPs, IPs and the coordinator; that the jumper settings are correct; and that the coordination flags used in the start-up OBs (OB20, 0B21, 0B22) are reset (see also instructions CP 524/CP 525). Find the permissible lengths in the job tables (Section 2.6). mee rrr eee eee cee eee ee ee eee eee mom meee eee eee eee 173B8576539-03 Computer Link with RK 512 No. for , No. for REPTEL SYSTAT Description 34H 4CH c) Send telegram was too short or < 128 bytes , i.e. less data were received (possible with follow-on telegrams) than were indicated in the telegram header 4DH d) Fetch telegram received with information data 5FH A correct telegram with a length > 128 bytes was received. The telegram cannot be evaluat- ed. The job will be aborted. Other errors during processing of the partner job: , 36H 51H a) - synchron error on the partner, since a new (follow-on) command telegram ar- rived, although the previous (follow-on) reply telegram had not been sent by the CP 525 or - a normal command telegram was received although a follow-on command telegram was expected or ~ a follow-on command telegram arrived, | although a command telegram was expected 174B8576539-03 Computer Link with RK 512 Remedy Carry out correction on the partner. Carry out correction on the partner. Verify the incorrect reaction of the partner if necessary with an interface test device ('FOXPG') tapped into the transmission line. This error can be signalled following a cold restart at your PC if long telegrams are to be sent or during a cold restart at the partner. This is a normal reaction during start-up; you do not need to do anything. During normal operation the error can also occur as a result of older error statuses were detected only by the partner. Otherwise you can assume that the partner is reacting incorrectly. It is possible that the error will not occur with jobs less than 128 7 bytes. 175B8576539-06 Computer Link with RK 512 9 Time Measurement ~ Processing a DIRECT Job The results of these time measurements for a SEND DIRECT job are examples of the processing times for DIRECT jobs. Two S5 135Us, each with a CP 922 and a CP 525 were used for the time measurement. The interpreter RK 512 and procedure 3964 (low priority) are loaded in the CP 525 of PC 1 on IF 1. The interface IF 2 is not progranmed. A SEND job is programmed in the job block. The interpreter RK 512 and procedure 3964 (high priority) are loaded in the passive CP 525 of PG 2 on IF 2. The interface IF 2 is not programmed. No job is programmed in the job block. The following times are measured: - from initiation of the SEND DIRECT job in Pc 1 (the bit "job running" is set) ~ to the end of the job in PC 1 (the bit "job finished without error" is set. 176