Siemens SINUMERIK 840 Planning Manual
  1. Manuals
  2. Brands
  3. Siemens Manuals
  4. Control Unit
  5. SINUMERIK 840
  6. Planning manual

Siemens SINUMERIK 840 Planning Manual

Computer link, general description
Hide thumbs Also See for SINUMERIK 840:
Table of Contents

Advertisement

Quick Links

Download this manual See also: User Manual, Planning Manual
SINUMERIK 840/840C
SINUMERIK 880/880 GA2
Computer Link
General Description
Planning Guide
Manufacturer Documentation
09.95 Edition

Advertisement

Table of Contents
loading

Related Manuals for Siemens SINUMERIK 840

Summary of Contents for Siemens SINUMERIK 840

  • Page 1 SINUMERIK 840/840C SINUMERIK 880/880 GA2 Computer Link General Description Planning Guide 09.95 Edition Manufacturer Documentation...
  • Page 2 SINUMERIK 840/840C SINUMERIK 880/880 GA2 Computer Link General Description Planning Guide Manufacturer Documentation Valid for: Control Software version SINUMERIK 840 from 1 SINUMERIK 840C from 1 SINUMERIK 880 T/M from 3 SINUMERIK 880 GA2 T/M from 1 September 1995 Edition...
  • Page 3 This does not, however, represent an obligation to supply such functions with a new control or when servicing. This publication was produced on the Siemens 5800 Office System. Subject to change without prior notice. The reproduction, transmission or use of this document or its contents is not permitted without express written authority.
  • Page 4 The term ”SINUMERIK 8X0” is used in this description as a short form for ”SINUMERIK 840/880”. Technical information This documentation applies to software version 1 and higher in the case of SINUMERIK 840 and 840C to software version 3 and higher in the case of SINUMERIK 880 GA2 to software version 1.
  • Page 5 General Local Area Networks Interface Modules Message Frames Configuration and Test Abbreviations Appendix...

  • Page 6: Table Of Contents

    Contents Page General ..........1–1 Definition of terms .
  • Page 7 3.4.2 Transparent data exchange ....... . 3–31 3.4.3 AS 512 protocol ........3–34 3.4.4 Communication with SIMATIC S5 systems...
  • Page 8 Test and simulation ........7–11 7.2.1 SINT .

  • Page 9: General

    For SINEC H1 the framework protocol architecture has been implemented using international standards in the transport-oriented layers (1 to 4) and the SINEC-AP1 Siemens standard in the application-oriented layers (5 to 7). 1–1 ©...

  • Page 10: Definition Of Terms

    A computer link can be realised using a bus connection or using one of many serial connections. The following figure shows the SIEMENS computer systems used for CAD, FMS, NC Archive and PPC as well as the RC, NC and PLC systems on a common bus cable. If older systems are to be connected to the bus, e.g.

  • Page 11: Iso Reference Model

    For this reason, the International Standards Organization (ISO) has established a model for communication procedures known as the ISO reference model. 1–3 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)

  • Page 12: Lan

    (opposite: closed networks). 1.1.5 SINEC AP 1 SINEC AP 1 is the Siemens Network Architecture Automation Protocol Version 1, a Siemens automation protocol. It was developed for the integration of the following systems in a factory automation system: •...

  • Page 13: Transport Connection Tpv

    Access to the transport connection is from the application-oriented layers via the transport service access point (TSAP), which has its own unique address (TSAP address). 1–5 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)

  • Page 14: Logical Peer

    One or several logical peers can be served via a TPV transport connection. (When connecting the SINUMERIK 8X0 to the Siemens FMS only one logical peer per transport connection is allowed.) The ”logical peer” is determined by the addressing in the application layer alone in the case of a serial connection.
  • Page 15 4 (TSAP addr.) (TSAP addr) (TSAP transport connection layer 7 log. p.1 log. p.2 log. p.3 NCDAT GLOBA MELDG logical peer Logical peer in bus connection 1–7 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)
  • Page 16 • with AS 512 protocol • with system 800 ID Configuring interface 2: (depends on peripheral device) • with/without AS 512 protocol • with/without system 800 ID 1–8 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)
  • Page 17 "Functional unit synchronization, end-of-work, mode switchover GLOBA" Logical peer 3: "Functional unit alarms, operator interrupt, status message MELDG" Logical peer: PLC1 For the peripheral device: Logical peer: PERI1 (any name may be selected). 1–9 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)

  • Page 18: Local Area Networks

    • coaxial cables, • broad band coaxial cables • fibre optic cables. The bus consists of a common resource, the bus cable, and branches to each station. 2–1 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)

  • Page 19: The Iso Seven Layer Model

    Two scientists would like to exchange their findings. Scientist 1 lives in Japan and speaks Japanese, scientist 2 lives in Spain and speaks Spanish. The two scientists represent layer 3. 2–2 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)
  • Page 20 Scientist 2 layer 3 (Japanese) (Spanish) Translator 1 Translator 2 layer 2 (Japanese/English) (English/Spanish) Post office 1 Post office 2 layer 1 (fax) (fax) 3 layer model 2–3 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)
  • Page 21 Layer Allocation method CSMA/CD IEEE* 802.3 Physical Physical characteristics of Layer the transmission path Yellow Cable * Ethernet Protocol architecture for local area networks according to ISO 2–4 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)
  • Page 22 The function of the transport layer is to provide a universal transport service in cooperation with the services of the lower-level layers. It separates the application-oriented from the transmission-oriented layers. 2–5 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)
  • Page 23 Spanish. However, an intermediate language, for example English, might be chosen, and both the transmitter and the receiver employ an interpreter; the transmitter for Japanese-English and the receiver for English-Spanish". 2–6 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)

  • Page 24: Access Methods

    • A probability factor can be specified with which a message will be transmitted. 2–7 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)

  • Page 25: Sinec H1

    At present there are no uniform international standards for layers 5 to 7 of the OSI model for the NC applications. As a first step to standardization of OSI layers 5 to 7 within the company, Siemens have therefore defined the AP 1 automation protocol. It is suitable for use on all Siemens automation devices.

  • Page 26: Serial Connection

    Larger networks cannot be implemented due to the required number of interfaces per unit increasing considerably. Fault diagnosis is relatively simple since an unambiguous allocation is possible according to communication request and physical implementation. 2–9 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)

  • Page 27: Star Connection

    Internode communication is executed via the master node • Master station is availability bottleneck • Simple diagnostics • Simple to configure • Different transmission media can be used 2–10 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)

  • Page 28: Meshed Network

    High cable cost • Extension costs highly progressive • Very large number of interfaces required per unit • Simple diagnostics • Failsafe • Internode communication is possible 2–11 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)

  • Page 29: Bus And Serial Connections

    Serial Serial Serial Serial interface interface interface interface Read station 1 Read station 2 . . . Read stat. Tool data Tool data Pal. - data 2–12 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)

  • Page 30: Interface Modules

    Message frames can be transmitted between the bus interface and the serial interface module, i.e. the message frames are not processed in the SINUMERIK but are passed from one interface module to the other. 3–1 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)
  • Page 31 CP 373 Double-tier Version 4 CP 315 – Version 5 CP 373 Version 6 CP 315 CP 373 Examples of complements with interface modules for SINUMERIK 880 3–2 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)
  • Page 32 CP 231: bus interface module CP 315: serial interface module (basic board, 1 interface) CP 373: serial interface module (expansion board, 3 interfaces) SINUMERIK 800 rack configuration 3–3 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)
  • Page 33 Number of bus interface modules interfaces interfaces CP 231 CP 315 CP 373 Examples of complements with interface modules for SINUMERIK 840 SYSTEM Slot 4....13 Standard control CP 231: Bus connection CP 315: Serial connection (basic board, 1 SS) CP 373: Serial connection (expansion board, 3 SS) Rack configuration for SINUMERIK 840 3–4...
  • Page 34 AP acknow- ledgement and AP request, should be approx. 30 - 50 ms. AP request (RNMPF...) AP acknowledgement CP231 (to RNMPF...) AP request (TNMPF...) 3–5 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)
  • Page 35 10 Mbit / sec. (SINEC H1) 9600 bits / sec. (programmer interface) 3. Access method CSMA/CD (IEEE 802.3) 4. Protocols ISO-8073 class 4 SINEC AP 1.0 SINEC H1 interface module 3–6 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)

  • Page 36: Interface Modules

    08.89 3 Interface Modules 3.1 Bus interface module Plane 7 SINEC AP1 protocol Network software Interface module hardware CP 231: interface module configuration 3–7 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)

  • Page 37: Serial Interface Modules

    The link between procedure driver and SINUMERIK driver is the device management which in turn must supply or interpret the AS 512 header, if configured. For configuring and test purposes, independent software modules are provided on the CP. 3–8 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)
  • Page 38 Interface b ) LSV 2 c ) XON/XOFF d ) RTS-LINE e) TRANSPARENT 4. Cumulative data rate 19200 baud Basic Expansion board board Active serial interface modules 3–9 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)

  • Page 39: Interface Modules

    LSV2 ..e.g. 3964R Expansion board CP 373 Basic board CP 315 Configuration of the active serial interface modules 3–10 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)

  • Page 40: Communication With The Cp 315

    The procedures can be configured independently of each other for each activated interface. For a detailed description of the procedures see Section 3.3. 3–11 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)

  • Page 41: Requirements For The Use Of "Flexible Communication

    Free message frames with AS 512 protocol without AS 512 protocol The user interface (DB 101/DB 102) in the PLC forms the internal interface for "flexible communication". 3–12 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)

  • Page 42: The Iso 7-Layer Model

    Message frame transfer is completely transparent, i.e. the message frames remain unchanged while being passed on. _______ Extended scope of functions: "Flexible communication" 3–13 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)
  • Page 43 In the given example, two message frames (20H and 40H) must be sent in addition to the actual message traffic. 3–14 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)

  • Page 44: Procedures

    After failed repeated attempts, the number of which is configurable, the driver aborts the process and enters an error message in the exception trace. 3–15 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)

  • Page 45: Appendix

    For more detailed information on data reception using 3964R, initialization conflict, character frames, data protection and monitoring times please refer to the procedure description in the appendix (see Section 9, Appendix). 3–16 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)

  • Page 46: Lsv2 Procedure

    In the text transfer phase, the text is transmitted in the form of a message frame. 3–17 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)
  • Page 47 3–18 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)
  • Page 48 Monitoring times (acknowledgement monitoring time for transmitter/receiver and character delay or character monitoring time) Block length (128 bytes or 256 bytes) Acknowledgement delay (with/without) 3–19 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)

  • Page 49: 3.3.3 Xon/Xoff Procedure

    The station sends an XOFF character even if the interface is not yet assigned. 3–20 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)

  • Page 50: Communication Between "Intelligent" (Equal) Nodes

    The transmission job interrupted by STX is then resumed. Minimum wiring required for the XON/XOFF procedure Transmitter Receiver Signal ground Signal ground 3–21 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)

  • Page 51: Signal Chart For The Xon/Xoff Procedure

    The end identifiers for the input direction can be configured by the user who can decide whether to assign no, one or two end identifiers. 3–22 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)

  • Page 52: Data Output

    (Transmitting station waits for the receiver to transmit the first XON before starting transmission) XON character (Hexadecimal value) XOFF character (Hexadecimal value) Line reservation time (Monitoring time after initialization conflict) 3–23 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)

  • Page 53: Rts-Line (Rts/Cts)

    "without" end identifiers, the expiry of the character monitoring time is used as the end criterion. Transmitter Receiver Signal ground Signal ground Wiring for the RTS-LINE procedure 3–24 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)

  • Page 54: Signal Charts For The Rts/Cts Procedure

    If a new receiving scratch is available, the characters are copied into this scratch and RTS reactivated. Transmitting jobs can also be processed in parallel to this job. 3–25 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)

  • Page 55: 3.3.4.1.2 Data Output

    (Character delay or character monitoring time and device monitoring time) DSR evaluation (Check if connected node is active) Number of end identifiers (Number) Node states equal (Yes/no) 3–26 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)

  • Page 56: Communication Control In The Transparent Mode

    If a serial interface is configured without System 800 identification, the data part of the message frame consists of useful data only. For a detailed description of the message frame data, please refer to Section 6, Message frames. 3–27 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)

  • Page 57: Sinec Ap1 Protocol

    AP application interface. configurable in interfaces with/ewithout AS 512 protocol with/without System 800 identification Max. 244 bytes; when connected to Siemens FMS systems, max. 224 bytes. 3–28 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)
  • Page 58 For further specifications on SINEC AP, please refer to the "SINEC AP manual" (Order no: 6 GK 1972-7AA02-0AA0). 3–29 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)
  • Page 59 DATLG Parameters Useful data Function-oriented protocol elements Management information Control elements Length specifications Identification of the AP application designation (together with TSAP) SINEC AP1 header (system part) 3–30 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)

  • Page 60: Transparent Data Exchange

    The PROTID characterizes the protocol version. For SINEC AP1.0 it is preset with Hex. MPXADR =00 (Multiplex Address) Multiplexing in layer 7 is not used with connection to Siemens FMS systems. COMCLS =04 (Command Class) COMCLS describes global functions;04 means serial transfer.
  • Page 61 Length of message frame data in bytes Identification Error numbers SINUMERIK Messagefra Useful data (max. 244 bytes, with connection to SIEMENS FMS systems max. 224 bytes) Message frame structure for job PDU 3–32 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)
  • Page 62 TASQNR Not used Not used SPARE 0000 PDUREF PDUID PDULG Length of PDU in bytes PARLG 0000 Not used DATLG 0000 Message frame structure of acknowledgement PDU 3–33 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)

  • Page 63: As 512 Protocol

    , i.e. 100 data words • Co-ordination flag configurable The byte and bit address of the respective flag is specified, e.g. 0607 , i.e. flag byte 6 flag bit 7. 3–34 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)
  • Page 64 AP 512 header are explained. ) Transmitting data from other station (PLC) to SINUMERIK 8X0 ) Transmitting data from SINUMERIK 8X0 to the other station (PLC) 3–35 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)
  • Page 65 AD Identification of message frame e.g. 0000 = initial message frame Transmission to SINUMERIK 8X0 Transmission to other station (e.g. PLC) AS 512 action message frame 3–36 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)
  • Page 66 Identification of response message frame 00 00 00 = Response message frame Transmission to SINUMERIK 8X0 Transmission to other station (e.g. PLC) AS 512 response message frame 3–37 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)
  • Page 67 Identification of the subsequent response message frame FF 00 00 = subsequent response message frame Transmission to SINUMERIK 8X0 Transmission to the other station (e.g. PLC) AS 512 subsequent response message frame 3–38 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)
  • Page 68 Furthermore, in the destination field the data word is specified from which the entries are made in the destination data block. In figure "AP 512 action message frame" DB4, DW 8 = 0408 has been entered. 3–39 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)
  • Page 69 The identification field is three bytes long. The entry FF 0000 identifies a subsequent response message frame. • Error number (E.no.) Errors during transmission of the subsequent message frame are indicated in this field. 3–40 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)

  • Page 70: Communication With Simatic S5 Systems

    SINUMERIK 8X0 systems permits the use of different protocols on the application layer. For this purpose, the SINEC Technological Functions (STF) have been defined by Siemens as a common level-7 protocol. The SINEC Technological Functions are fully compatible with ISO 9506 (MMS), parts 1 and 2 with regard to the scope of functions and can thus easily be integrated in MAP 3.0.
  • Page 71 ID 8=1 ID 7: bit 4=1, bit 1=1 ID 8=2 bytes ID 7: bit 4=1, bit 1=1 ID 8=3 ID 7: bit 4=1, bit 3=1 ID 8=4 3–42 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)

  • Page 72: 3.4.4.2 Requirements For The Application Of Stf

    The scope of functions of the CP 231 A "computer link" and PG Remote mode are to a large extent independent of one another. 3–43 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)

  • Page 73: 3.4.5.2 Requirements For The Use Of The Pg Remote Function

    • Hardware requirements: CP 231, any version PG with CP 536, from S5-DOS level 5 • Software requirements: CP 231 firmware release from 3A (Order No. 6FX1840-0BX01-3A) 3–44 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)

  • Page 74: Addressing Lists

    (Ethernet address, TSAP address). Then it sends the message frame to the SINEC H1 bus. 3–45 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)
  • Page 75 AP1.0 SINUMERIK Network sw. Useful data header header header SINEC H1 Network AP1.0 SINUMERIK 101... Useful data header header header Message frame processing using CP 231 A 3–46 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)

  • Page 76: Addressing Lists Of The Serial Interface Module

    The procedure driver informs the connected station that the SINUMERIK want to send a message frame and manages the necessary processes to transmit data at procedure level. 3–47 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)

  • Page 77: For Message Frames With As 512 Protocol And Without Identification

    The device management generates the AS 512 header with the aid of the interface and addressing list and transmits the message frame to the procedure driver, which makes sure that the data is properly transmitted to the connected station. 3–48 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)

  • Page 78: For Message Frames Without As 512 Protocol And Without Identification

    The procedure driver informs the node connected of the request to send and handles the operations necessary for data transmission. 3–49 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)
  • Page 79 SINUMERIK Proc. Proc. data header header CP 315 Useful AS 512 SINUMERIK Procedure Proc. data header header may/may not be configured Message frame processing using CP 315 3–50 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)

  • Page 80: Com

    Pass data to the PLC • Process functions by means of standard routines. The SINUMERIK 880 contains its own COM CPU. The COM area in the SINUMERIK 840 is built into the NC CPU. Multiport RAM Standard routines Connection monitoring...

  • Page 81: Routines

    The "sender location" is required in order to send the response message frame to the interface module from which the initiation message frame came. "Sender location" CP1 - 1st interface module (CP: Communication processor) CP2 - 2nd interface module 4–2 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)
  • Page 82 In the normal mode only the partner node (e.g. production control computer) can initiate the file transfer. • In the special/maintenance mode only the operator at the machine can inititate the transfer Only SINUMERIK 880). 4–3 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)

  • Page 83: Plc

    An outline overview of the PLC is given in figure "PLC structure". User interface Kernel Standard sequences functions PLC basic software Multiport RAM Dual port RAM Interface module Interface module serial PLC structure 5–1 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)
  • Page 84 If a standard message frame is to be output, this is communicated to the PLC in a specific area of the user interface. Then processing and forwarding of the standard message frame is effected automatically by the standard function blocks. 5–2 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)

  • Page 85: User Interfaces

    (DB 101, DB 102) and the input/output buffers in the multiport RAM. DB101 User Buffer interface input input 0-31 DB34 Std.sig. input STEP5 Standard routines Buffer DB102 output DB35 Std.sig. output User interface output 0-31 User interfaces 5–3 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)
  • Page 86 RAM is acknowledged. The user has to release the user interface by resetting the acknowledgement signal after he/she has initiated all necessary responses to the incoming message frame. 5–4 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)
  • Page 87 If the message frame was able to be be sent, the acknowledgement signal output is deleted and the user interface cleared. 5–5 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)

  • Page 88: Standard Functions

    PLC output buffer (in the MPR). Buffer DB 101 input DB 34 Std.sig. input STEP 5 standard Buffer routines DB102 output DB 35 Std.sig. output Transfer of standard message frames 5–6 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)
  • Page 89 1 of the correponding interface module. The following functions are implemented for the tool sessions: • Inquiry of all tools • Inquiry of tools used • Reporting a tool • Random loading/unloading 5–7 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)

  • Page 90: Message Frames

    Useful data _______ configurable in interface list with/without AS 512 protocol with/without System 800 identification max. 244 bytes, when connected to SIEMENS FMS SYSTEM max. 224 bytes 6–1 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)
  • Page 91 Note: For reasons of compatibility a maximum message frame length of 224 bytes must be used with links to Siemens FMS systems or SINUMERIK 850. The maximum message frame length can be set via machine data . In case of larger data volumes, subsequent message frames are sent until all data has been transmitted.

  • Page 92: Identification

    R_WBC for ”load tool with code carrier”. This facilitates an allocation between identification and meaning of the message frame, which is especially advantageous during installation and for debugging. 6–3 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)

  • Page 93: Meaning Of The Characters Used In The Identifications Of

    The identification bytes of "free message frames" are used in a different manner. They are used for communications between the interface module and the user interface but are not transmitted via the link. 6–4 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)
  • Page 94 For the XON/XOFF and RTS-LINE procedures (configuration: node states equal: NO), data input must be initiated by the user via the "DATA START" command. The command requires no useful data. 6–5 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)

  • Page 95: Standard Message Frames

    The tool data is entered through kernel sequences into the corresponding tool memories of the SINUMERIK 8X0 on "random loading". Use of the kernel sequences is only appropriate when the tool management software package is integrated in the SINUMERIK 8X0 system. 6–6 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)

  • Page 96: Configurable Message Frames

    S, K and P: S = Standard message frame K = Message frame of a kernel sequence P = Configurable message frame 6–7 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)
  • Page 97 Event message frames NC alarms on PLC alarms on All alarms off Operator interrupt on Operator interrupt off Status message on Status message off Continuation message ____ 6–8 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)
  • Page 98 Session abort by production control 1) necessary for the kernel sequences that follow Random loading - report loaded tool Tool is loaded ____ Tool is not loaded 6–9 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)
  • Page 99 Production control transmits unloading list to CNC ____ • Acknowledgement from CNC ____ • Production control transmits the last unloading list message frame • Acknowledgement unloading list received in full 6–10 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)
  • Page 100 Message: End of the NC program transmission RNaaa Acknowledgement for final message: negative RNaaaFE Acknowledgement for final message: positive REaaa Abort by CNC TNaaaF Abort by production control RNaaaF 6–11 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)
  • Page 101 RNCLF Abort by production control TNCLFF Abort by CNC RNCLFF Acknowledgement to NC erase program NC erase program successfully executed RNKOM NC erase program not executed RNKOMF 6–12 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)
  • Page 102 Rejection by code carrier system Tool data written on code carrier ____ Rejection by CNC Delete data carrier Delete trigger from data carrier ____ Positive acknowledgement ____ Negative acknowledgement 6–13 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)

  • Page 103: Addressing

    Data word no. The function number is not used for message frames without System 800 identification with a serial interface and therefore has a default value of 0. 6–14 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)
  • Page 104 Protocol Identi- data Network software header fication or procedure Procedure or netw. header in some configurations only Bus or serial connection Addressing _______ only for SINUMERIK 880 6–15 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)

  • Page 105: Configuration And Test

    1, output list 1, format list) and connection- Configuring PC AT oriented lists (list of interfaces, addressing list) for service) PG 750 the serial interface module. 7–1 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)

  • Page 106: Sinec Nm

    SINPS 231 SINEC H1 CP 231 Network SW AP monitor Local l DB SIN driver Test g DB: global data base l DB: local data base Central configuring 7–2 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)

  • Page 107: Sinec Nml

    DB Input Communication file SINPS 231 SINEC H1 Network SW AP monitor Local l DB SIN. driver Test l DB: local data base CP 231 Local configuration 7–3 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)

  • Page 108: Sinps 231

    • • • • Configuration of input list 1 for two message frames of the synchronization session S: Standard P: User, configurable Structure of input list 1 7–4 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)
  • Page 109 - in input list 1 and output list 1. The format list is required for the representation of the useful data which is checked by means of test functions. 7–5 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)

  • Page 110: Sinps 315

    It is stored on the CP 315 basic board. PG 685/PC AT SINPS 315 Input Device AP monitor management Test Local SINUMERIK driver CP 315/373 Configuration of CP 315 7–6 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)
  • Page 111 In output direction the logical partner which is assigned to an interface with the corresponding AS 512 parameters - if configured - serves as search key. Log. partner Interface no. (AS 512 parameter) 7–7 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)
  • Page 112 The figure "Structure of list of interfaces" shows the contents of the block for one interface. 7–8 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)
  • Page 113 Max. number of single message frames 0 / 1/ ..Max. number of subsequent message frames 0 / 1/ ..Structure of the list of interfaces 7–9 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)
  • Page 114 Partner status equal (yes/no) Waiting for 1st. XON: (with/without) XON character (Hex value) XOFF character (Hex value) Hold-off interval (x times 10 ms) Device monitoring time (x times sec.) 7–10 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)

  • Page 115: Test And Simulation

    EPROM system module of the CP 231A or CP 315. Further explanations are available in the following documentation: SINUMERIK 840/880 Planning Guide Computer Link Test software SINT 7–11 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)
  • Page 116 SIM 850-SW SIPRA-H1-SW Computer CP 536 CP 536 SINEC H1 Read out/configure trace buffer PG 685/685T/PC AT with SINT-SW CP 231A SINUMERIK Test configuration for SINEC H1 bus 7–12 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)

  • Page 117: Sint

    The traced data can be printed out. Communication between the PG/PC AT and the interface modules is via the TTY interface of the interface modules. Furthermore, the exception trace entries in the interface modules can be read out with SINT. 7–13 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)

  • Page 118: Sim 850

    The contents of the ring buffer can be stored on a formatted floppy disk. The floppy disk files can also be output on the screen within the FOX PG-M program using a function key or to a printer, e.g. PT 88. 7–14 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)

  • Page 119: Sipra H1 (Sinec Protocol Analyzer)

    For display on the screen the headers of layers 2 to 4 of the OSI seven layer model are represented already decoded. The headers of the other protocol layers and the useful data are displayed both in hexadecimal and in ASCII format. 7–15 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)

  • Page 120: Abbreviations

    Electronic Industries Association Enquiry End of transmission ERRCLS Error Class ERRCOD Error Code End of Text EU interface module Expansion unit interface module File server Central data base 8–1 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)
  • Page 121 Product Planning and Control PROTID Protocol Identifier Configuration service Robot Control ROSCTR Remote Operating Service Control Standard message frame SIMATIC control with STEP 5 language SINEC Communication Processor 8–2 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)
  • Page 122 08.89 8 Abbreviations SGSQNR Segment Sequence Number SINEC Siemens Network Architecture SINEC AP1 Siemens Network Architecture Automation Protocol Version 1 SINEC H1 Communication network of the Siemens programmable controllers SINEC NM SINEC Network Management SINEC NML SINEC Network Management Local...

  • Page 123: Appendix

    If the block cannot be received even after several attempts (value is configurable) without error, the 3964R procedure aborts the reception and reports an error. 9–1 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)
  • Page 124 Then the device with the higher priority sends its data as described above. After release of the connection, the device with the lower priority can execute its transmission task. 9–2 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)
  • Page 125 Example: Procedure in the case of an initialization conflict: CP315 Peripheral unit (lower priority) (high priority) t < timeout DLE (NAK) 1st character 2nd character nth character DLE (NAK) 9–3 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)
  • Page 126 BCC itself is secured using the character parity method and transmitted at the end of the block. All characters of the block except the STX start control character are covered by that procedure. 9–4 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)
  • Page 127 Since, in general, different types of units will communicate with each other, the character delay period can be parameterized. It can be specified in intervals of 10 ms (1 word, max. FF FF). 9–5 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)

  • Page 128: Lsv2 Procedure

    =Text transfer phase (data communication phase) =Request phase 9–6 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)
  • Page 129 By sending STX, the station wishing to send moves into the text transfer phase and becomes a text transmitting station. By receiving STX, the other station also moves into the text transfer phase and becomes a receiving station. 9–7 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)
  • Page 130 08.89 9.2 LSV2 procedure Station wishing to send Station at the other end DLE / 0 DLE / 0 DLE / 0 DLE / 1 Enquiry phase 9–8 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)
  • Page 131 ENQ and the receiving station responds with DLE 1. 9–9 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)
  • Page 132 DLE / STX / TEXT /... DLE / ENQ DLE / 1 DLE / 1 DLE / 1 DLE / 0 DLE / 0 DLE / 0 Text transfer phase 9–10 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)
  • Page 133 (BCC). The block check function is set to zero for STX. In the receiving station, BCC is also computed and compared with the transmitted BCC. 9–11 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)
  • Page 134 In this case the station with the higher priority is allowed to transmit. The station with the higher priority ignores the ENQ received and the other station cancels its request to send and transmits DLE0. 9–12 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)

  • Page 135: Xon/Xoff Procedure

    1st character 2nd character 120th character e.g. printer buffer XOFF full or off-line key pressed t < Device monitoring time 121st character 122nd character nth character (EI) 9–13 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)
  • Page 136 "Data Start" command from COM area 1st character 2nd character 243rd character Receiving XOFF scratch full t < Device monitoring time 244th character 245th character nth character (EI) 9–14 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)
  • Page 137 2nd character 10th character Transmission job receives negative acknowledge- ment; driver is waiting for receiving job t < Line reservation time 1st character 2nd character nth character (EI) 9–15 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)

  • Page 138: Rts-Line Procedure

    10th character CTS inactive RTS inactive Device no longer ready to receive t < Device monitoring time CTS active RTS active 11th character 12th character nth character (EI) 9–16 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)
  • Page 139 CP 315 Peripheral unit RTS-LINE procedure "DATA START" command from COM area RTS active CTS active 1st character 2nd character nth character (EI) RTS inactive CTS inactive 9–17 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)

  • Page 140: Error Coding Of Remote Ap Protocol Processing Systems And Ap Users

    91 H C1 H SGSQNR has permissible value 99 H C1 H Processing aborted due to resources being assigned too long 51 H C1 H APM (remote) in permissible condition 9–18 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)
  • Page 141 Transferred or requested useful data volume too small 9A H 02 H Format of the requested data not in accordance with format agreed 9A H 01 H Data not in accordance with agreement 9–19 © Siemens AG 1989 All Rights Reserved 6FC5 197-0AB20-0BP0 SINUMERIK 840/880 (PJ)

This manual is also suitable for:

Sinumerik 880 ga2 t/mSinumerik 840cSinumerik 880Sinumerik 880 ga2Sinumerik 880 t/m

Table of Contents