Siemens SIMATIC TIWAY 1 User Manual

Series 500 nim
Hide thumbs Also See for SIMATIC TIWAY 1:
Table of Contents

Advertisement

Quick Links

SIMATIC TIWAY I
Series 500 NIM
User Manual
Order Number: PPX:TIWAY-8110
Manual Assembly Number: 2587871-0054
Fifth Edition

Advertisement

Table of Contents
loading

Summary of Contents for Siemens SIMATIC TIWAY 1

  • Page 1 SIMATIC TIWAY I Series 500 NIM User Manual Order Number: PPX:TIWAY-8110 Manual Assembly Number: 2587871-0054 Fifth Edition...
  • Page 2 All Rights Reserved — Printed in USA Reproduction, transmission, or use of this document or contents is not permitted without express consent of Siemens Energy & Automation, Inc. All rights, including rights created by patent grant or registration of a utility model or design, are reserved.
  • Page 3 MANUAL PUBLICATION HISTORY SIMATIC TIWAY I Series 500 NIM User Manual Order Manual Number: PPX:TIWAY–8110 Refer to this history in all correspondence and/or discussion about this manual. Event Date Description Original Issue 02/84 Original Issue (2704516–0001; 2587872–0001) Second Edition 04/86 Second Edition (2587872–0002) Errata 1 06/86...
  • Page 4 LIST OF EFFECTIVE PAGES Pages Description Pages Description Cover/Copyright Fifth History/Effective Pages Fifth iii — x Fifth 1-1 — 1-7 Fifth 2-1 — 2-16 Fifth 3-1 — 3-18 Fifth 4-1 — 4-64 Fifth A-1 — A-5 Fifth B-1 — B-6 Fifth C-1 —...
  • Page 5: Table Of Contents

    Contents Chapter 1 TIWAY I Overview TIWAY I System Overview ............TIWAY I Options .
  • Page 6 Series 500 NIM Self Tests ............3-14 Power-up Self-Test .
  • Page 7 Write Block Primitive – Code 30 ..........4-39 Write Random Block Primitive –...
  • Page 8 List of Figures 1-1 TIWAY I System Block Diagram ............2-1 NIM Simplified Block Diagram .
  • Page 9 List of Tables 1-1 Primitive Support in NIM Software Releases ......... . 2-1 RS-232-C Connections .
  • Page 10 APPENDIX D — NETWORK EVALUATION FORM contains a TIWAY network evaluation form. You can submit the completed form to Siemens for a free network evaluation. SIMATIC TIWAY I Series 500 NIM User Manual Preface...
  • Page 11 APPENDIX E — SPECIFICATIONS provides general specifications for the Series 500 NIM. APPENDIX F — PRIMITIVE EXAMPLES provides a simple primitive example in normal and extended addressing modes. Related The following publications contain additional information on TIWAY I and Publications TIWAY I compatible products.
  • Page 12 Chapter 1 TIWAY I Overview TIWAY I System Overview ............TIWAY I Options .
  • Page 13: Chapter 1 Tiway I Overview

    TIWAY I is an industrial Local Area Network designed to satisfy today’s factory and plant requirements for data acquisition and control of manufacturing processes. It is a significant enhancement of the Siemens “Local Line,” which has supported the PM550 Programmable Controllers and DS 990 computer products since 1980.
  • Page 14: System Block Diagram

    System components include: Host System Interfaces (including Host Adapters, Gateways, and Network Control Modules) Siemens Programmable Controller Network Interface Modules (NIMs) UNILINKt Secondary Adapters for interfacing non-Siemens products to the TIWAY I Network SIMATIC TIWAY I Series 500 NIM User Manual...
  • Page 15: Tiway I System Block Diagram

    TIWAY I System Overview (continued) Figure 1-1 TIWAY I System Block Diagram TIWAY I Overview SIMATIC TIWAY I Series 500 NIM User Manual...
  • Page 16: Tiway I Universal Command Language, Ucl

    The Series 500 NIM The Series 500 NIM is the TIWAY I Network Interface Module for the Siemens Series 500 Programmable Controllers. See Chapter 3 for a specific listing of controllers supported by the Series 500 NIM. The Series 500 NIM, which occupies two slots of a Series 500 I/O base, provides redundant TIWAY I communication ports.
  • Page 17: Series 500 Nim Features

    Minor software error corrections If the product release level does not appear on the product I.D. label, call the Siemens Technical Services Group at (423) 461–2501 for assistance. They will need the unit serial number to determine the release level.
  • Page 18: Primitive Support In Nim Software Releases

    Table 1-1 provides a complete listing of the primitives and data types supported in each release. Table 1-1 Primitive Support in NIM Software Releases Release 1.1 Releases 2.1 and 2.2 Release 3.0 Primitive TT Types Primitive TT Types Primitive TT Types NOTE: The Primitives listed in Table 1-1 are supported by the NIM.
  • Page 19 Chapter 2 Network Design Considerations TIWAY I Network Configuration ........... Communication Media .
  • Page 20: Tiway I Network Configuration

    NOTE: The proper installation of a communication network requires careful planning and design. If you need assistance, a free site survey is available from Siemens. Simply fill out and return the enclosed “TIWAY I Network Evaluation Form” (Appendix D). Also included with this manual is a “TIWAY I Network Configuration Data Sheet”...
  • Page 21: Nim Block Diagram

    NIM Block Diagram Figure 2-1 is a simplified block diagram of the Series 500 NIM. The media interface blocks are intentionally left unlabeled because the type of media interface depends on which NIM model you are using. The blocks are described as follows.
  • Page 22: Timimg Considerations

    TIWAY I Network Configuration (continued) The basic difference in the NIM models is the configuration of the media interface cards. Examples of the possible application of the different models are as follows: If you want media redundancy for a dedicated line (lease-line) modem, or an RF (short-haul) modem, use PPX:500–5040 which supports RS-232-C/423 on both Port A and Port B.
  • Page 23: Rs-232-C Cable Installation

    RS-232-C Cable Installation The physical layer in TIWAY I provides a modem interface for synchronous or asynchronous modems at data transmission rates up to 115.2K bits per second. The modem interface provides standard signals, as defined in Table 2-1, for control of two-way alternate data transmission using both half and full duplex modems.
  • Page 24: Pin Assignments Of Local Line Connectors

    Local Line Cable Installation The following paragraphs describe Local Line characteristics and installation guidelines. Local Line The TIWAY I Local Line is a physical signaling technique (baseband, Characteristics differential current drive) which operates over shielded, twisted-pair cabling. The Local Line cable may be up to 25,000 feet long, depending on loading and baud rate selection.
  • Page 25: Network Cable

    Network Cable The TIWAY I local line network cable consists of a main cable or spine with droplines or taps for each Secondary. Interrelated network variables having direct influence upon network performance are: Maximum trunk cable length Cable type Tap length Tap spacing Number of Secondaries Maximum baud rates...
  • Page 26: Number Of Local Line Secondaries Versus Cable Length

    Figure 2-2 Number of Local Line Secondaries Versus Cable Length Network Design Considerations SIMATIC TIWAY I Series 500 NIM User Manual...
  • Page 27: Local Line Cable Installation

    Brands other than those listed here will be specified by Siemens upon request. The tap housing, shown in Figure 2-3, is made by Siemens specifically for its Local Line network. The tap housing can be mounted rigidly to a NEMA panel or other enclosure.
  • Page 28: Tap Housing Cable Connections

    Figure 2-3 TIWAY I Tap Housing Tap Housing Cable With the cover removed from the PPX:500–5606 Tap Housing, note that Connections there are three sets of terminals, and that each set is labelled G, W, and B. (See Figure 2-3.) One set of these terminals is for the incoming Local Line twisted pair;...
  • Page 29: Planning Considerations

    Local Line Cable Installation (continued) Planning Some major points to consider during the planning phase of a Local Line Considerations network are as follows: From the start, allow for system growth. This means making provisions for the attachment of additional computing devices by routing cables through all probable areas of future plant expansion.
  • Page 30: Tap Spacing Examples

    Figure 2-4 Tap Spacing Examples 2-12 Network Design Considerations SIMATIC TIWAY I Series 500 NIM User Manual...
  • Page 31: Cable Routing

    Local Line Cable Installation (continued) Cable Routing Cable routing should be planned as if the path between all stations on the network were free of obstructions. Next, modify the first routing to account for obstructions, then calculate the amount of cable needed. CAUTION All local and national electrical and fire codes should be observed when installing wiring.
  • Page 32: Obstructions

    Surface Duct Routing. Surface ducting for network cabling is usually installed along the baseboards or is attached to walls at desktop height. While surface ducting protects cables from both physical and EMI effects, it may also require that network computing devices be positioned near a wall. Obstructions Aside from physical obstructions such as posts, walls, and partitions, electrical interference should also be avoided.
  • Page 33: Local Line Biasing

    Local Line Biasing The TIWAY I Local Line is designed to operate with shielded, twisted-pair cable which has a characteristic impedance of 124 ohms. In certain network configurations, the Local Line must be biased to raise its noise immunity and to prevent oscillations of receivers connected to the line. In all configurations, the Local Line must be properly terminated at both ends of the trunk to prevent an impedance mismatch which could result in signal reflections on the line.
  • Page 34: Terminating The Local Line

    Turn on the bias switch on the unused port to prevent the entry of noise into the NIM. Terminating the The Siemens Local Line must be properly terminated at both ends of the Local Line trunk to prevent a possible impedance mismatch which could result in signal reflections back along the line.
  • Page 35: Terminating The Local Line

    Switch, the bias switch should be moved downward to the ON position. Figure 2-6 Terminating the Local Line NOTE: All Siemens tap housings contain factory-installed terminating resistors. If the Tap Housing is not used to terminate the Local Line, the terminating resistors must be removed when the output cable is attached.
  • Page 36: Chapter 3 Installation

    Chapter 3 Installation General Requirements ............Installing the NIM .
  • Page 37: General Requirements

    560 and 565.) If you cannot determine whether your controller release is compatible with the Series 500 NIM, contact Siemens technical services at (423) 461–2501 for assistance. The communication configurations of all devices attached to the network must match;...
  • Page 38: Installing The Nim

    Installing the NIM This section describes how to mount the NIM in the Series 500 I/O base, connect the communication cables to the NIM, and initialize the system for operation. The programmable controller (P/C) and the programming device should be in place before you install a NIM. Before inserting the NIM into the I/O base, first determine which two adjacent slots that the NIM will occupy.
  • Page 39: Inserting The Module Into The Base

    Inserting the Module into the Base Before using the module, you should decide whether you want to protect it by “keying” the module’s position in the I/O base. As shown in Figure 3-1, keying is accomplished by placing the three keys provided in the right-hand slot of the two slots occupied by the module so that they fit into the notches on the module edge card.
  • Page 40: Installing The Nim In The I/O Base

    Once the keys are in place, orient the module so that the indicators are on the top half of the module. Then, carefully push the module into the I/O base as shown in Figure 3-2. When the module is fully seated in the I/O base, tabs will hold the module in place.
  • Page 41: Setting The Dipswitches

    Setting the Dipswitches As Figure 3-3 illustrates, there are two blocks of dipswitches on the Series 500 NIM. The lower block of eight switches is used to select the NIM’s address on the network. The upper block of ten switches is used to configure the network communication parameters.
  • Page 42: Selecting Network Configuration Parameters

    There are two physical Parameters media types over which TIWAY I communication can occur: Siemens Local Line and RS-232-C. Several dipswitches on the configuration switch block are ignored when operating on the Local Line media. These switches are noted in the following descriptions.
  • Page 43: Nim Switches And Leds

    Setting the Dipswitches (continued) Figure 3-3 NIM Switches and LEDs Installation SIMATIC TIWAY I Series 500 NIM User Manual...
  • Page 44: Network Data Rate Switch Settings

    Configuration switches 1 through 4 (on the configuration switch bank) select the data transmission rate. All devices on the network must be configured to communicate at the same data rate. The data rates corresponding to the switch settings are shown in Table 3-3. For synchronous operation in RS-232-C communication, the rate of data transmission is established by the modem.
  • Page 45 Setting the Dipswitches (continued) Synchronous/Asynchronous Selection. Configuration switch 5 selects synchronous or asynchronous operation for modems. For synchronous modem communication, the NIM receives the transmit and receive timing signals from the modem via transmit signal timing element (DB), and receive signal timing element (DD). If the modem data rate does not match a TIWAY data rate exactly, the data rate select switches should be set to a rate that is the next lower data rate from the modem For example, if a 56,000 bps synchronous modem is used, a data rate of 38,400 bps should be...
  • Page 46: Other Switches

    Lockout/Enable. Configuration switch 9 enables the P/C to “lockout” the NIM during time-critical operations. This function is not needed normally. During lockout, the NIM will not communicate with the P/C. The actual mechanism is as follows: The P/C “sees” the NIM as an 8 channel discrete output module on the I/O portion of the scan.
  • Page 47 Setting the Dipswitches (continued) A successful completion of these tests will leave only the NIM GOOD and PC/NIM COMM GOOD indicators on. If the TEST LED remains on, run the User Initiated Self-Test to determine the source of the error. The reset switch should always be pressed after you change the configuration or address selection dipswitches.
  • Page 48 Local/Remote. When set to remote, this two-position switch enables the NIM to perform write operations to controller memory. In the local position, the NIM cannot write to the controller. In either position, the NIM can monitor P/C memory and mode of operation. The Local Mode will be indicated (after the NIM is brought into the online state) by a flashing Online LED indicator.
  • Page 49: Series 500 Nim Self Tests

    Series 500 NIM Self Tests The three levels of Series 500 NIM self tests available in the NIM are described in the following paragraphs. They are: Power-Up Self-Test Run-Time Self-Test User-Initiated Self-Test Power-up Self-Test The Series 500 executes a Power Up Self-Test in the following cases: Immediately following the application of +5VDC from the I/O base (power-up) as part of its initialization Any time the Reset switch is pressed (See Figure 3-3)
  • Page 50: User-Initiated Self-Test

    Failures detected in the ROM integrity test will cause the NIM GOOD LED to extinguish, and force the NIM into a failed state. In this condition the NIM goes to the Logically Disconnected State (LDS) and will always issue a Disconnect Mode (DM) response to any commands received.
  • Page 51 Series 500 NIM Self Tests (continued) Start of execution of the User-Initiated Self-Test will be signaled by the illumination of the Test Mode LED, with all other LED indicators being extinguished. Then, after approximately ten seconds, all LED indicators will flash on and off for approximately two seconds.
  • Page 52: Module Login Verification

    NIM to be sure it is firmly seated in the slots and enter the appropriate command again. If you still cannot verify the installation, you should contact your local distributor or the Siemens Technical Services Group at 423–461–2501 for further assistance.
  • Page 53: Connecting The Network Cables

    Connecting the Network Cables Network cabling should already be in place before NIM installation is begun. If you need information concerning network cabling, see the SIMATIC TIWAY I Systems Manual (TIWAY–8101). There are two communication ports on the Series 500 NIM, one on the top of the module (Port A) and one on the bottom (Port B).
  • Page 54 Chapter 4 NIM Primitives TIWAY I Primitives ..............Primitive Functions .
  • Page 55: Tiway I Primitives

    TIWAY I Primitives Primitives are high-level commands that allow a user to access like data types in all different Secondaries in the same manner. For example, a Primary can access image register memory in a NIM-equipped 520, 530, 5TI, and PM550 controller with the same command. The purpose of the Primitives is to remove as many differences as possible between the controllers, so that applications programs at the Primary level may treat all TIWAY I Secondaries in the same manner.
  • Page 56: Primitive Functions

    Primitive Functions Primitives serve as the command structure that a TIWAY I Primary uses to access (read or write) information in a TIWAY I Secondary. The Primitives defined in the following paragraphs serve these basic functional needs: To access and retrieve data To ascertain the status and configuration of attached devices To perform control operations on the attached device SIMATIC TIWAY I Series 500 NIM User Manual...
  • Page 57: Primitive Structure And Operation

    Primitive Structure and Operation A Primitive consists of multiple fields that specify the Primitive’s length and function, type and location of data to be accessed, and data to be transferred. In TIWAY I, a Primitive forms the information field of an HDLC Information frame (I) or Unnumbered Information frame (UI) if HDLC operation is selected.
  • Page 58: Basic Primitive Structure

    Figure 4-1 illustrates the basic Primitive structure when HDLC operation is selected. There is a Request Format and a Response Format, as shown. The binary weight of the fields is detailed in Figure 4-2. All field lengths are multiples of 8 bits, which allows for octet testing of data link frames at the data link/media access control layer.
  • Page 59: Primitive Operation And Exceptions

    Primitive Structure and Operation (continued) Figure 4-2 Binary Weight of the Fields Primitive Operation Normal Primitive operation consists of a request and response sequence and Exceptions without exceptions. Exceptions are errors found in the interpretation or execution of a Primitive. Normal Operation The normal operation of a Primitive is for the initiating (Host) station to Procedures...
  • Page 60: Program Transfer Procedures

    Exception when Reading. The device performing the Primitive operation aborts execution of a Primitive when an exception condition is encountered, and returns the reason for the exception. The device requesting the Primitive should evaluate returned message, take appropriate corrective measures, and attempt retransmission of the Primitive. Exceptions when Writing.
  • Page 61 Primitive Structure and Operation (continued) The upload and download formats will always be identical, i.e., data that is received from an upload request will be sent unmodified (in the same order and format) to the attached device during download. You cannot write data or change the attached device operating mode during an upload or download request;...
  • Page 62: Primitive Logical Groups

    Primitive Logical Groups All Siemens TIWAY Primitives fall into logical groups according to their function, as shown in Table 4-1. Each Primitive has a request and a response format. The device initiating the transaction formats a request Primitive, and the device answering the request formats a response Primitive.
  • Page 63: Series 500 Nim Primitive Subset

    Primitive Logical Groups (continued) Series 500 NIM The subset of TIWAY I Primitives supported by the Series 500 NIM is given Primitive Subset in Table 4-2. Future additions to this subset will be announced as they are implemented. Note that each of the following Primitives fits into the general categories listed in Table 4-1.
  • Page 64: Primitive Field Definitions

    Primitive Field Definitions The basic Primitive Request and Response field formats are shown in Figure 4-3. Each of the basic field types shown is described in the following paragraphs. For a detailed explanation of TIWAY Primitives refer to the SIMATIC TIWAY I Systems Manual (PPX:TIWAY–8101). Figure 4-3 Primitive Request and Response Field Format SIMATIC TIWAY I Series 500 NIM User Manual NIM Primitives...
  • Page 65: Primitive Field Symbols

    Primitive Field Definitions (continued) Primitive Field The symbols used in the remainder of this section to denote the different Symbols types of Primitive fields are summarized in Table 4-3. Table 4-3 Summary of Primitive Field Symbols Symbol Description LLLL Length field Primitive code Attached device status Data element types...
  • Page 66: Descriptor Field

    Descriptor Field Within the Descriptor Field (see Figure 4-3) are different fields to define the following: data element types, location or address of a data element, number of data elements to access, and the status of the attached device. The Descriptor Field may contain a single descriptor or multiple descriptors as required by the various Primitives.
  • Page 67: Data Element Types And Formats

    Data Element Types and Formats The data element types (TTs) and their length (in bytes) are defined in Table 4-4. Figure 4-4 through Figure 4-15 show the format of the data elements. Table 4-4 Data Element Types and Formats Length Data Element Type (in bytes) Instruction Memory (L)
  • Page 68 Table 4-4 Basic Data Unit Format (continued) Length Data Element Type (in bytes) ** 26 or 66 Loop Process Variable High Limit ** 27 or 77 Loop Process Variable Low Limit ** 28 or 78 Loop Orange Deviation Alarm ** 29 or 79 Loop Yellow Deviation Alarm ** 2A or 6A Loop Sample Rate...
  • Page 69: Discrete Data Element Format

    Data Element Types and Formats (continued) Table 4-4 Basic Data Unit Format (continued) Length Data Element Type (in bytes) ** 43 or 83 Analog Alarm Sample Rate ** 44 or 84 Analog Alarm Setpoint Analog Alarm Variable Flag* Analog Alarm Control Flag ** 47 or 87 Analog Alarm Error* ** 48 or 88...
  • Page 70: Packed Discrete Data Element Format

    Figure 4-5 Packed Discrete Data Element Format Figure 4-6 Forced Word Data Element Format SIMATIC TIWAY I Series 500 NIM User Manual NIM Primitives 4-17...
  • Page 71: Forced Discrete And Cr Data Element Format

    Data Element Types and Formats (continued) Figure 4-7 Forced Discrete and CR Data Element Format Figure 4-8 Secondary System Status Data Element Format 4-18 NIM Primitives SIMATIC TIWAY I Series 500 NIM User Manual...
  • Page 72: Loop Status Data Element Format

    Figure 4-9 Loop Status Data Element Format SIMATIC TIWAY I Series 500 NIM User Manual NIM Primitives 4-19...
  • Page 73: Loop Control Flag Data Element Format

    Data Element Types and Formats (continued) Figure 4-10 Loop Control Flag Data Element Format 4-20 NIM Primitives SIMATIC TIWAY I Series 500 NIM User Manual...
  • Page 74: Ramp/Soak Status Data Element Format

    Figure 4-11 Ramp/Soak Status Data Element Format Figure 4-12 Loop Mode Data Element Format SIMATIC TIWAY I Series 500 NIM User Manual NIM Primitives 4-21...
  • Page 75: Ramp/Soak Step Data Element Format

    Data Element Types and Formats (continued) Figure 4-13 Ramp/Soak Step Data Element Format Figure 4-14 Analog Alarm Variable Flag Data Element Format 4-22 NIM Primitives SIMATIC TIWAY I Series 500 NIM User Manual...
  • Page 76: Analog Alarm Control Flag Data Element Format

    Figure 4-15 Analog Alarm Control Flag Data Element Format SIMATIC TIWAY I Series 500 NIM User Manual NIM Primitives 4-23...
  • Page 77: Data Element Address Ranges

    Data Element Address Ranges The maximum data element locations (AAAA field) for each data element type / controller combination are provided in Table 4-5. All values in the table are 1-based (first legal value is 1; not zero). Values of zero are not supported.
  • Page 78: Data Element Address Ranges

    Table 4-5 Data Element Address Ranges P/C Type 520– 530– 530– 530– 520C 520C 530C 530C 530C 560– 565– NOTE Data Type 1101 1102 1104 1108 –1101 –1102 –1104 –1108 –1112 1101 1101 L Instruction 1024 2048 4095 8191 2048 4096 8192 12000 8192 8192...
  • Page 79: Data Field Length Restrictions

    Data Field Length Restrictions Table 4-6 and Table 4-7 delineate the maximum length of the data field, in bytes, for Read and Write Primitives. Table 4-6 Maximum Read Primitive Byte Length 4-26 NIM Primitives SIMATIC TIWAY I Series 500 NIM User Manual...
  • Page 80: Maximum Write Primitive Byte Length

    Table 4-7 Maximum Write Primitive Byte Length Table 4-4 Table 4-5 SIMATIC TIWAY I Series 500 NIM User Manual NIM Primitives 4-27...
  • Page 81: Series 500 Nim Primitive Descriptions

    Series 500 NIM Primitive Descriptions The following paragraphs describe the NIM Primitives used in the Series 500 NIM. Refer to Table 4-2 for a complete list of the Primitives supported. Exception Primitive Availability: Releases 1.1, 2.1, 2.2, and 3.0 – Code 00 Primitive 00 allows you to obtain an error status from a Secondary.
  • Page 82 Symbol Value Definition DDDD TT not programmed in attached device. The attached device did not respond properly. The resulting data element location formed by the starting address, plus the number of data elements to access is out of range specified by TT. Communication has not been established with the atttached device.
  • Page 83: Native Primitive - Code

    Series 500 NIM Primitive Descriptions (continued) Native Primitive – Availability: Releases 1.1, 2.1, 2.2 and 3.0 Code 01 The native Primitive 01 allows access to an attached device by using a Task Code which is unique to the specific device addressed. By using 01, a programmer can embed a controller-unique Task Code and can access anything in controller memory, for example, that a VPU can access.
  • Page 84: Status Primitive - Code

    Status Primitive – Availability: Releases 1.1, 2.1, 2.2, and 3.0 Code 02 Primitive 02 is the machine status Primitive. It reports the current operational state of the attached device and NIM in a common format for all types of attached devices. The NIM gets a status update from the attached device every 4 seconds (and immediately when an 02 Primitive is issued).
  • Page 85: Configuration Primitive - Code

    Series 500 NIM Primitive Descriptions (continued) Configuration Availability: Releases 1.1, 2.1, 2.2, and 3.0 Primitive – Code 03 Primitive 03 allows the Primary to identify the types of devices that exist on the network. For example, an 03 response from a 520 P/C would be different from a response from a 5TI P/C.
  • Page 86: Primitive Format Configuration - Code

    Primitive Format Availability: Releases 1.1, and 2.1, 2.2, and 3.0 Configuration – Code 04 Primitive 04 is the format Primitive that allows you to ascertain the maximum length of the Primitive acceptable to the Network Interface Module. The buffer length is returned in number of bytes. Request: LLLL 04 Response: LLLL 04 NNNN MM EE FF GG BB ...
  • Page 87: Packed Native Primitive - Code

    Series 500 NIM Primitive Descriptions (continued) Packed Native Availability: Releases 2.1, 2.2, and 3.0 Primitive – Code 05 Primitive 05 allows one or more device task codes to be executed. Execution is aborted and an exception response returned if an exception occurs during processing.
  • Page 88: Segment Definition - Code

    Segment Definition Availability: Release 3.0 – Code 07 Primitive 07, used with the Program Upload and Download Primitives (58 and 59), obtains the attached device segment definition as an ASCII string. The definitions contain the segment number they represent and relate one-to-one with the MMMM descriptor (starting at bit P) defined in Primitive 58.
  • Page 89: Change State Primitive - Code

    Series 500 NIM Primitive Descriptions (continued) Change State Availability: Releases 1.1, 2.1, 2.2, and 3.0 Primitive – Code 10 This Primitive allows you to change the operational state of TIWAY I Secondaries. For example, you may enter the Run or Program modes with this Primitive.
  • Page 90: Read Block Primitive - Code

    Read Block Availability: Releases 1.1, 2.1, 2.2, and 3.0 Primitive – Code 20 Primitive 20 is a command to read a single contiguous block of data in the Secondary device. Read Block will access contiguous data element locations from a given data element location. Request: LLLL 20 TT NNNN AAAA Symbol Value...
  • Page 91: Read Random Block Primitive - Code

    Series 500 NIM Primitive Descriptions (continued) Read Random Availability: Releases 2.1, 2.2, and 3.0 Block Primitive – Code 21 Primitive 21 is a command to read several random blocks of contiguous memory. Request: LLLL 21 TT NNNN AAAA Symbol Value Definition Data element type NNNN...
  • Page 92: Write Random Block Primitive - Code 31

    Write Block Availability: Releases 1.1, 2.1, 2.2, and 3.0 Primitive – Code 30 Primitive 30 is the Write Block Primitive, which will replace contiguous data element locations from a given data element location with the data specified in the Request. Request: LLLL 30 TT AAAA DD ...
  • Page 93: Block Data Acquisition Primitive Codes 50, 51, And

    Series 500 NIM Primitive Descriptions (continued) Symbol Value Definition Attached device operational status Number of block writes not completed due to error Block numbers not processed due to error CAUTION Blocks not processed due to error (specified by BB) may have been partially written before a failure occurred.
  • Page 94 Symbol Value Definition Block number (1–20 hex) Data element type NNNN Number of locations AAAA Data element location Response: LLLL 50 HH Symbol Value Definition Attached device operational status Gather Block Primitive – Code 51. The Gather Block Primitive specifies which blocks (as defined by the Define Block Primitive 50) will be read.
  • Page 95 Series 500 NIM Primitive Descriptions (continued) Symbol Value Definition Attached device operational status EEEEEEEE EEEEEEEE is a mask as defined by the Request Primtive and DDDD is defined by the data type being accessed. The order of return of the blocks is from the lowest numbered block to the highest.
  • Page 96 Symbol Value Definition Data element type AAAA Data element location Data Response: LLLL 52 HH EEEEEEEE DD ... DD (repeated) Symbol Value Definition Attached device operational status EEEEEEEE EEEEEEEE is a mask as defined by the Request Primitive and DDDD is defined by the data type being accessed.
  • Page 97: Record Data Acquisition Primitive Codes 55, 56, And

    Series 500 NIM Primitive Descriptions (continued) Record Data Availability: Releases 2.1, 2.2, and 3.0 Acquisition Primitive Codes 55, The Record Data Acquisition Primitives allow repetitive collection of 56, and 57 multiple predefined blocks of data. The Define Record Primitive (55) allows multiple blocks of data to be defined as a single record.
  • Page 98 The total byte count of data elements defined by the record(s) must not cause the Gather Record Response to exceed the maximum Primitive frame length. See Table 4-5 and Table 4-6 for the number of bytes in each data type. Response: LLLL 55 HH Symbol Value...
  • Page 99 Series 500 NIM Primitive Descriptions (continued) Write and Gather Record Primitive – Code 57. The Write and Gather Record Primitive specifies which records (as defined with Define Record Primitive 55) will be read. It also allows you to replace any contiguous data element locations.
  • Page 100: Program Upload & Download Primitive Codes 58 And

    Symbol Value Definition Number of records in error Record numbers in error Data records returned without errors NOTE: An exception will be returned if the write portion of this Primitive fails. No data will be returned for records in error or invalid read defintions. Program Upload &...
  • Page 101 Series 500 NIM Primitive Descriptions (continued) Table 4-8 provides a state diagram for the various command/state combinations. Program Load Exception Guidelines. If you receive a data block that is not the block you expect (the sequence number is returned in the primitive response), it is recommended that you try to access the block again.
  • Page 102 The first request also contains the “between response to request” time-out value. This value corresponds to the number of seconds that the attached device will wait for the next upload request. If the time expires, the attached device will exit upload mode. The first response also returns the actual time-out value that will be used, since some attached devices may support a maximum time-out value less than the value requested.
  • Page 103 Series 500 NIM Primitive Descriptions (continued) Upload Response Parameter Descriptions. The basic format of the response is as follows: LLLL 58 HH 00 RRRR MMMM OOOO LLLL 58 HH 01 RRRR YYYY WW ZZ DD ... DD LLLL 58 HH XX RRRR (YYYY may be present on some codes) where: Symbol Value...
  • Page 104 There are four primary forms of the upload primitive. Initiate upload — places the attached device into upload mode. Upload device — sequentially collects all information that defines the operating environment for the attached device. Terminate upload — removes the attached device from the upload mode as soon as the attached device notifies the host that the requested operation is complete.
  • Page 105 Series 500 NIM Primitive Descriptions (continued) Upload Data Request and Response Request: LLLL 58 01 RRRR YYYY Response: LLLL 58 HH 01 RRRR YYYY WW ZZ DD ... DD or LLLL 58 HH 02 RRRR (all data has been transferred) where: Symbol Value...
  • Page 106 If the terminate upload command is issued and the attached device is not in the upload mode, an error response of LLLL 00 58 002C will be returned. This notifies the host that the terminate (02) command code is not valid in the current mode.
  • Page 107 Series 500 NIM Primitive Descriptions (continued) Download Request Parameter Descriptions The basic format of the download request is as follows: LLLL 59 XX ... LLLL 59 00 RRRR MMMM OOOO (may have ASCII format) LLLL 59 01 RRRR YYYY WW ZZ DD ... DD LLLL 59 02 RRRR LLLL 59 03 RRRR where:...
  • Page 108 Download Response Parameter Descriptions The basic format of the response is as follows: LLLL 59 HH 00 RRRR OOOO LLLL 59 HH XX RRRR (YYYY may be present on some XX codes) where: Symbol Value Definition Attached device status Entered download mode Download data was received and valid Download complete Reserved...
  • Page 109 Series 500 NIM Primitive Descriptions (continued) Like the program upload primitive, there are four forms of the download request. Initialize download — places the attached device into download mode and clears any device memory areas that can accept download data Download device —...
  • Page 110 Download Device Request and Response Request: LLLL 59 01 RRRR YYYY WW ZZ DD ... DD Response: LLLL 59 HH 01 RRRR YYYY where: Symbol Value Definition RRRR Host reference field YYYY Download sequence count which is initially set to 0. This field is incremented by one on each subsequent download request.
  • Page 111: Summary Of Primitives

    Series 500 NIM Primitive Descriptions (continued) Download Examples The following pages contain examples of download requests for various conditions. Summary of Table 4-8 summarizes the Series 500 NIM Primitives. Primitives 4-58 NIM Primitives SIMATIC TIWAY I Series 500 NIM User Manual...
  • Page 112: Summary Of Primitives

    Table 4-8 Summary of Primitives Primitive Format SIMATIC TIWAY I Series 500 NIM User Manual NIM Primitives 4-59...
  • Page 113 Series 500 NIM Primitive Descriptions (continued) Table 4-8 Summary of Primitives (continued) Primitive Format 4-60 NIM Primitives SIMATIC TIWAY I Series 500 NIM User Manual...
  • Page 114 Table 4-8 Summary of Primitives (continued) Primitive Format Table 4-9 summarizes the same Primitives listed in Table 4-8, but with extended addressing. SIMATIC TIWAY I Series 500 NIM User Manual NIM Primitives 4-61...
  • Page 115: Summary Of Primitives (Extended Addressing)

    Series 500 NIM Primitive Descriptions (continued) Table 4-9 Summary of Primitives (Extended Addressing) Primitive Format 4-62 NIM Primitives SIMATIC TIWAY I Series 500 NIM User Manual...
  • Page 116 Table 4-9 Summary of Primitives (Extended Addressing) (continued) Primitive Format SIMATIC TIWAY I Series 500 NIM User Manual NIM Primitives 4-63...
  • Page 117 Series 500 NIM Primitive Descriptions (continued) Table 4-9 Summary of Primitives (Extended Addressing) (continued) Primitive Format 4-64 NIM Primitives SIMATIC TIWAY I Series 500 NIM User Manual...
  • Page 118 Appendix A PM550 CIM Requirements Introduction ..............Local Line Length .
  • Page 119: Introduction

    Introduction This appendix discusses biasing and terminating the TIWAY I Local Line for network installations containing CIMs in addition to self-biased and switch-biased devices. PM550 CIM Requirements SIMATIC TIWAY I Series 500 NIM User Manual...
  • Page 120: Local Line Length

    Local Line Length The PM550 CIM supports operation over the Local Line at distances up to 10,000 feet and 9600 baud. Advances in technology have provided line drivers and receivers that support Local Line operation up to 25,000 feet. These new drivers have been incorporated in TIWAY I Conformant devices to support the extended operation.
  • Page 121: Local Line Bias And Termination

    Bias Switch. The CIM is provided with a jumper which allows selection of bias or no bias. The Siemens Local Line must be properly terminated at both ends of the trunk to prevent a possible impedance mismatch that could result in signal reflections back along the line.
  • Page 122: Local Line Bias And Termination

    If more than one CIM is attached to a Local Line, place CIMs at the extreme ends of the Local Line trunk. Install the jumpers provided with the outermost CIMs in accordance with the instructions in the PM550 CIM User’s Manual, Manual Number PM550–1101154–4. This will apply the correct bias to the Local Line to prevent oscillations of the CIM receivers.
  • Page 123: Appendix B Floating Point Numbers

    Appendix B Floating Point Numbers Introduction ..............IBM Format .
  • Page 124: B.1 Introduction

    Introduction The Series 500 NIM allows IBMr excess 64 and IEEE representation of floating point data types (noted in Chapter 4). Floating point formats consist of three parts: the sign bit, the exponent, and the mantissa, or fraction. For both the IBM and the IEEE formats, the sign bit indicates the positive or negative value of the mantissa.
  • Page 125: B.2 Ibm Format

    IBM Format Floating point numbers are stored in memory in two 16-bit words as illustrated in Figure B-1. Before being stored in memory, however, the number is converted to a normalized hexadecimal fraction, a corresponding hexadecimal exponent, and a sign bit. The fraction portion of the IBM number is normalized;...
  • Page 126: Ibm Floating Point Representation

    IBM Format (continued) Figure B-1 IBM Floating Point Representation Floating Point Numbers SIMATIC TIWAY I Series 500 NIM User Manual...
  • Page 127: Ieee Format

    IEEE Format The exponent portion of the IEEE format is similar to the IBM format except that it is 8 bits in length and is biased by 7F16. It is also different in that it represents a power of 2 instead of 16. The exponent for 2) is represented in memory by 7F16.
  • Page 128: Ieee Floating Point Representation

    IEEE Format (continued) Figure B-2 IEEE Floating Point Representation Floating Point Numbers SIMATIC TIWAY I Series 500 NIM User Manual...
  • Page 129: Appendix C Network Configuration Data Sheet

    Appendix C Network Configuration Data Sheet SIMATIC TIWAY I Series 500 NIM User Manual Network Configuration Data Sheet...
  • Page 130 DATA DEFINITION TABLE Date Name Data Starting Number of Record Block Length or Identifier Type Address Elements Number Number (Bytes) Network Configuration Data Sheet SIMATIC TIWAY I Series 500 NIM User Manual...
  • Page 131: Appendix D Network Evaluation Form

    Appendix D Network Evaluation Form If you would like Siemens to evaluate your network requirements, complete and submit the Network Evaluation Form. Siemens Technical Services Group will analyze your requirements and provide you with a network design plan and quote.
  • Page 132 Network Evaluation Form SIMATIC TIWAY I Series 500 NIM User Manual...
  • Page 133: Appendix E Specifications

    Appendix E Specifications Environmental Operating temperature range 0_ to 60_ C (32_ to 140_ F) Specifications Storage temperature range –40_ to 85_ C (–40_ to 185_ F) Operating humidity range 0 to 95% relative humidity Vibration NAVMAT P9492 Power Model 5039: 1.25 watts, –5 VDC; Requirements 8 watts, +5 VDC Model 5040: 0.06 watts, –5 VDC;...
  • Page 134: Appendix F Primitive Examples

    Appendix F Primitive Examples The following TIWAY I Primitive example (which does not include any program transfer capabilities) reads four words of variable memory from a Series 500 controller, starting at memory location 100 (hex = 64). The format for the request would be as follows: Request: LLLL 20 TT NNNN AAAA = 0006 20 01 0004 0064, where: LLLL (Length) = 0006 Primitive Code = 20...
  • Page 135 Response: LLLL A0 HH DDDD DDDD = 000A A0 00 8464 8665 A001 01F4 LLLL (Length) = 000A Primitive Code = A0 (extended address format for Primitive 20) HH (Status) = 00 (unit operational and executing logic) DDDD ... (values read from V-memory) V100 = 846416 V101 = 866516 V102 = A00116...
  • Page 136 Customer Response We would like to know what you think about our user manuals so that we can serve you better. How would you rate the quality of our manuals? Excellent Good Fair Poor Accuracy Organization Clarity Completeness Graphics Examples Overall design Size Index...
  • Page 137 UNITED STATES BUSINESS REPLY MAIL PERMIT NO.3 FIRST CLASS JOHNSON CITY, TN POSTAGE WILL BE PAID BY ADDRESSEE ATTN: Technical Communications M/S 519 SIEMENS ENERGY & AUTOMATION INC. 3000 BILL GARLAND RD P O BOX 1255 JOHNSON CITY TN 37605–1255 FOLD...
  • Page 138 SIMATIC is a registered trademark of Siemens AG. Series 500, PM550, TIWAY, 5TI, and Unilink are trademarks of Siemens Energy & Automation, Inc. Belden is a registered trademark of Belden Wire and Cable Company. IBM is a registered trademark of International Business Machines Corporation.

This manual is also suitable for:

Simatic tiway i series 500 nim

Table of Contents