! " " # $ %&' ( & )
! DANGER DANGER indicates an imminently hazardous situation that, if not avoided, will result in death or serious injury. DANGER is limited to the most extreme situations. ! WARNING WARNING indicates a potentially hazardous situation that, if not avoided, could result in death or serious injury, and/or property damage. ! CAUTION CAUTION indicates a potentially hazardous situation that, if not avoided, could result in minor or moderate injury, and/or damage to property.
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.
LIST OF EFFECTIVE PAGES Pages Cover/Copyright History/Effective Pages iii — x 1-1 — 1-7 2-1 — 2-16 3-1 — 3-18 4-1 — 4-64 A-1 — A-5 B-1 — B-6 C-1 — C-2 D-1 — D-2 E-1 F-1 — F-2 Registration Description Fifth Fifth Fifth Fifth Fifth Fifth Fifth Fifth Fifth Fifth Fifth Fifth Fifth Fifth Pages Description
Contents Chapter 1 1.1 TIWAY I System Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 TIWAY I Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TIWAY I Universal Command Language, UCL . . . . . . . . . . . .
3.5 Series 500 NIM Self Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14 Power-up Self-Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Run-Time Self-Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . User-Initiated Self-Test . . . . . . . . . . . . . . . . . . . . . . . .
Write Block Primitive – Code 30 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Write Random Block Primitive – Code 31 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Block Data Acquisition Primitive Codes 50, 51, and 52 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Record Data Acquisition Primitive Codes 55, 56, and 57 . . . . . . . . . . . . . . . . . . . . . . . . . . .
List of Figures 1-1 TIWAY I System Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1 2-2 2-3 2-4 2-5 2-6 1-4 NIM Simplified Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Number of Local Line Secondaries Versus Cable Length . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TIWAY I Tap Housing . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
List of Tables 1-1 Primitive Support in NIM Software Releases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7 2-1 RS-232-C Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2 Pin Assignments of Local Line Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5 2-6 3-1 Network Address Selection . . . . . . . . . . . . . . . . . . . . . .
Preface Manual Overview Manual Organization This manual contains the information necessary to install and operate the Series 500 Network Interface Module (NIM). The following information is provided.
Related Publications • 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. The following publications contain additional information on TIWAY I and TIWAY I compatible products. To order these publications, contact your distributor or sales office. If you need assistance in contacting your distributor or sales office in the United States, call 1–800–964–4114.
Chapter 1 TIWAY I Overview 1.1 TIWAY I System Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 TIWAY I Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TIWAY I Universal Command Language, UCL . . . . . . . . . . . . . . .
1.1 TIWAY I System 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. The TIWAY I network provides a reliable and flexible communication architecture.
TIWAY I Options System Block Diagram TIWAY I network products provide a number of user-selectable options. • Baud rates are selectable from 110 baud to 115.2 K baud. • TIWAY I devices can operate with modems in either full or half duplex mode, synchronously or asynchronously. • Both NRZ and NRZI data encoding are available. Figure 1-1 illustrates the basic system block diagram of a TIWAY I Network.
TIWAY I System Overview (continued) ! Figure 1-1 TIWAY I System Block Diagram 1-4 TIWAY I Overview SIMATIC TIWAY I Series 500 NIM User Manual
TIWAY I Universal Command Language, UCL TIWAY I provides a Universal Command Language for all communication on the network. The UCL consists of a set of high-level request/response transactions known as Primitives.
TIWAY I System Overview (continued) Series 500 NIM Features Series 500 NIM Software Releases The Series 500 NIM provides several features which ensure maximum network signal integrity. • Each communication port is provided with a “jabberstop” circuit to disable the port’s transmitter in the event of a communication port failure. Such failures can cause continuous network transmission which would dominate the communication channel. • Built–in self tests guard against failure of the NIM itself.
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.
Chapter 2 Network Design Considerations 2.1 TIWAY I Network Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2 Communication Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NIM Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Timing Considerations . . . . . . . . . . . . . . . . . . . . . . . .
2.1 TIWAY I Network Configuration TIWAY I is a multi-drop communication network which consists of a main trunk cable (the “spine”) and dropline cables. The network can connect up to 254 secondaries (e.g., Series 500 controllers) to a host computer. The Series 500 NIM provides the interface to the network host, enabling the host and the controller to communicate with each other.
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. • Special Function Interface Controller (SFIC) — delivers and receives controller commands. • NIM controller — translates the controller commands and responses.
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: Timimg Considerations • 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.
2.2 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. The modem interface is a standard “Type E” DTE configuration as defined in Section 5 of EIA RS-232-C.
2.3 Local Line Cable Installation The following paragraphs describe Local Line characteristics and installation guidelines. Local Line Characteristics The TIWAY I Local Line is a physical signaling technique (baseband, 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. It uses tap housings to simplify the addition of connections to TIWAY I.
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 Figure 2-2 illustrates the relationship of cable distance to the number of Secondaries for different baud rates for two types of twisted pair cable.
Figure 2-2 Number of Local Line Secondaries Versus Cable Length 2-8 Network Design Considerations SIMATIC TIWAY I Series 500 NIM User Manual
Local Line Cable Installation (continued) As shown in Figure 2-2, when you use Belden 9860 cable (or its equivalent), up to 75 stations can be attached to a network operating at 38K bps and having a spine length of 20,000 feet. At 115.2K bps, the maximum length of a Local Line network having 254 stations is 10,000 feet.
Figure 2-3 TIWAY I Tap Housing Tap Housing Cable Connections With the cover removed from the PPX:500–5606 Tap Housing, note that 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; the center set is for the drop line; and the remaining set is used to connect the Local Line to the following node, or to terminate the Local Line if the Tap Housing is the last one on the network trunk.
Local Line Cable Installation (continued) Planning Considerations Local Line Tap Spacing Some major points to consider during the planning phase of a Local Line 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. • Always make the network flexible enough to allow for rearrangement of plant equipment.
Figure 2-4 Tap Spacing Examples 2-12 Network Design Considerations SIMATIC TIWAY I Series 500 NIM User Manual
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. Failure to observe coding requirements could result in electrical or fire hazards.
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.
2.4 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.
)% ) ) " " %' )% ) ) " " %' )% ) ) " - $ # %'' % )) %# " " % . "/ " $ # *- " $ # *- " - $ # % - $ # % Figure 2-5 Local Line with Two or More Switch-biased NIMs ! CAUTION Excessive noise can enter the NIM if a switch-biased local line interface port is unused, for instance in a case where no redundant local line is installed. Turn on the bias switch on the unused port to prevent the entry of noise into the NIM.
Local Line Biasing (continued) Termination of the Local Line must be at the tap housings at the extreme ends of the network spine, and is accomplished as follows: 1. The factory-installed termination resistors in the tap housing (see Figure 2-6) are left in place in the tap housing which is to be used to terminate the Local Line. 2. If the termination resistors are used and the attached NIM has a Bias Switch, the bias switch should be moved downward to the ON position.
Chapter 3 Installation 3.1 General Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2 3.2 Installing the NIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3 3.3 Inserting the Module into the Base . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4 3.4 Setting the Dipswitches . . . . . . . .
3.1 General Requirements The following requirements must be met in order to install and use a Series 500 NIM: 1. 2. The appropriate NIM configuration should be selected. • 500–5039 (LOCAL LINE/LOCAL LINE) • 500–5040 (RS-232-C/RS-232-C) The programmable controller in which the Series 500 NIM is to be installed must be a model 520, 520C, 530, 530C, 560 or 565 with an I/O base.
3.2 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.
3.3 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. This prevents another I/O module from being mistakenly inserted into the slots reserved for a communication module.
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. To remove the module, pull the tabs away from the module and take it out of the I/O base, being careful not to damage the edgecard.
3.4 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. Note that the switches are numbered from bottom to top. When setting up your NIM, use the configuration data sheet in Appendix C of this manual to record important configuration information.
Table 3-2 Address Examples Selecting Network Configuration Parameters 1 25 203 SW8 Open Open Open SW7 Closed Closed Open SW6 Closed Closed Closed SW5 Closed Open Open SW4 Closed Open Closed SW3 Closed Closed Closed SW2 Closed Closed Open SW1 Closed Closed Open The upper block of ten dipswitches is used in selecting the parameters that define the network communication environment.
Setting the Dipswitches (continued) $ # , #% " # ' # % 0%% $ # "## 0 #% 0%% , % 0%% , % 0%% 68% "9 % " ,%'' % ) " % ) " # #( #% " " /" " " /" # # :8;" %9 )% " ,% #" # % " # # #" # % " " "# #% " "#< ( " "# #% " '% ")' #" # ")' #" # " %/" ,$ -)" % " # )%% - & ")" # )% ) % # %) ( " "# " "# ( ")'*#" # ")' #" # )% ), " %#" )% ), " %#" 8 %$ ,( 9 6: &". ") .< 6=.
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. When setting switches one through four, select a data rate which matches that of the modem exactly.
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).
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: 1. The P/C “sees” the NIM as an 8 channel discrete output module on the I/O portion of the scan. 2. If the P/C is to “lockout” the NIM during a time critical scan, it can set the image register address that corresponds to the 8th output of the module.
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. If a 560/565 is connected to the NIM, you should reset the NIM whenever you reconfigure the controller.
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. The Remote Mode will be indicated by a continuously illuminated online indicator. Local Line Bias.
3.5 Series 500 NIM Self Tests The three levels of Series 500 NIM self tests available in the NIM are described in the following paragraphs.
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. Once the NIM has reached the Normal Operating Mode and fails to communicate with the controller, it reports this to the host computer with an Exception Response.
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. On completion of the test, the Test LED will flash at a 2 HZ rate. A PASS condition will be indicated by the following LED indicators illuminating: 1. NIM GOOD 2. PC/NIM COMM GOOD 3. RECEIVE 4.
3.6 Module Login Verification After the NIM has been installed and configured, you should verify that the NIM is logged into the controller I/O map. This is the first thing you should do if the PC/NIM Comm Good LED is not on. Connect a programming device to the controller to verify controller-module communication. To do this in a 520/530 P/C system with a VPU200–3102, enter AUX 43, which checks all I/O points on a particular base.
3.7 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). Depending on the model you have, these ports accept either an RS-232-C or Local Line connection. Plug the network interface cables into one of these two ports.
Chapter 4 NIM Primitives 4.1 TIWAY I Primitives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2 4.2 Primitive Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3 4.3 Primitive Structure and Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1 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.
4.2 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.
4.3 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. If X.25 operation is selected, the Primitive is contained in the User Data field of an X.25 Data Packet.
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.
Primitive Structure and Operation (continued) ' # - ' " ) ) - - Figure 4-2 Binary Weight of the Fields Primitive Operation and Exceptions Normal Primitive operation consists of a request and response sequence without exceptions. Exceptions are errors found in the interpretation or execution of a Primitive.
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. Exceptions concerning Primitive format, contents, or device state when writing will abort the entire Primitive.
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; however, you can continue to read data. If an attempt is made to write data or change the operating mode, an exception code will be returned.
4.4 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. The TIWAY I Primitive subset is taken from the categories listed in Table 4-1.
Primitive Logical Groups (continued) Series 500 NIM Primitive Subset The subset of TIWAY I Primitives supported by the Series 500 NIM is given 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.
4.5 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).
Primitive Field Definitions (continued) Primitive Field Symbols The symbols used in the remainder of this section to denote the different types of Primitive fields are summarized in Table 4-3.
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. Data Element Types — The length of the data element type descriptor field is eight bits.
4.6 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 Basic Data Unit Format (continued) TT Data Element Type Length (in bytes) ** 26 or 66 Loop Process Variable High Limit 4 ** 27 or 77 Loop Process Variable Low Limit 4 ** 28 or 78 Loop Orange Deviation Alarm 4 ** 29 or 79 Loop Yellow Deviation Alarm 4 ** 2A or 6A Loop Sample Rate 4 ** 2B or 6B Loop Remote Setpoint 4 ** 2C or 6C Loop Output 4 2D Loop Status* 2 2E Loop Control Flags 4 2F Ramp/Soak Status* 2 **30 or 70 Loop Error* 4 **31 or 71 Loop Bias 4 ** 32 o
Data Element Types and Formats (continued) Table 4-4 Basic Data Unit Format (continued) TT Data Element Type Length (in bytes) ** 43 or 83 Analog Alarm Sample Rate 4 ** 44 or 84 Analog Alarm Setpoint 4 45 Analog Alarm Variable Flag* 2 46 Analog Alarm Control Flag 4 ** 47 or 87 Analog Alarm Error* 4 ** 48 or 88 Analog Alarm P.V. High High Alarm 4 ** 49 or 89 Analog Alarm P.V.
## = 1D CD 2 = 86 9 6 ? A 7 4 1 C 2 - ) - F E + ' + / - : 6 % % 3 E ! 3 D 3 G + Figure 4-5 Packed Discrete Data Element Format ## = - = $ 8A 9 H I !
Data Element Types and Formats (continued) ## = -D = -< D 6 < D 6 - 6 ? . : A 7 4 1 C 2 : : : : : > > ! : 6 - % % .
' < ## = ? = ) 8 9 ) - - " ' 0 L & ) % * ) < D 3 + G D 3 + - * ) < D 3 + G D 3 + * " ! < D 3 ! ! + G D 3 ! ! + * / 3 3 < D 3 ! 3 3 3
Data Element Types and Formats (continued) ## = ?" = ) ' 8 9 ) - - "'0 L&) % M #(/$> .
## = ?' = , 8 9J ) - - "'0 * L&) % 3 86 = 9 - * 3 +/+ 8 6 = 9 * * ( G * * , F 8 : * ?449 J #3 + Figure 4-11 Ramp/Soak Status Data Element Format ## = A4 = ) 8 9J - "'0 L&) % = 6 * 0 ( ) : * - = 6 * 0 (#% # : * = 6 * 0
Data Element Types and Formats (continued) ## = A1 = , 86A D """ :::& ## """" N ## C1 - 9 & * 8: = D 6 = 9 ## * "! 8:7 = .
## = 71 = ' 8? 9 ) - - "'0 L&) % #(/$>. ; * / ?:5 - * # E / * 0 ,)%$ * 0 * 0 , )%$*)%$ " * ! ' * * * 3 0 * * ) = : = 6 * > * ( G .
4.7 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.
Table 4-5 Data Element Address Ranges P/C Type Data Type 520– 1101 530– 1102 530– 1104 530– 520C 520C 530C 530C 530C 1108 –1101 –1102 –1104 –1108 –1112 560– 1101 565– 1101 NOTE L Instruction TT = 00 1024 2048 4095 8191 * 1024 2048 4096 8192 12000 8192 8192 B V Variable TT = 01 512 1024 1024 2048 512 1024 2048 4096 5120 2048 2048 B K Constant TT = 02 0 0 0 0 0 0 0 0 0 0 0 A,B Discrete I/O X,Y,X&Y Packed TT = 3,4,6,7 128 1023 1023 1023 1023 1023 1023 1023
4.8 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-7 Maximum Write Primitive Byte Length $ ! F 3 ! E + 8$3 F 9 A: A6 4? 4C ?1C ?14J ?1A ?14JJ ?14 ?1AJ ?16 ?1AJJ Table 4-4 3 3 D Table 4-5 3 F ! + J #3 3 E + ( 3 3 3 < <
4.9 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 – Code 00 Availability: Releases 1.1, 2.1, 2.2, and 3.0 Primitive 00 allows you to obtain an error status from a Secondary.
Symbol Value DDDD 16 TT not programmed in attached device. 17 The attached device did not respond properly. 19 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. 1A Communication has not been established with the atttached device. 1B The store and forward buffer is full and the store and forward message was discarded. 1C Data element field (specified by TT) is improperly formatted.
Series 500 NIM Primitive Descriptions (continued) Native Primitive – Code 01 Availability: Releases 1.1, 2.1, 2.2 and 3.0 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. Request: LLLL 01 DDDD, where DDDD is defined by the task codes of the device being accessed.
Status Primitive – Code 02 Availability: Releases 1.1, 2.1, 2.2, and 3.0 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).
Series 500 NIM Primitive Descriptions (continued) Configuration Primitive – Code 03 Availability: Releases 1.1, 2.1, 2.2, and 3.0 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.
Primitive Format Configuration – Code 04 Availability: Releases 1.1, and 2.1, 2.2, and 3.0 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 ...
Series 500 NIM Primitive Descriptions (continued) Packed Native Primitive – Code 05 Availability: Releases 2.1, 2.2, and 3.0 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. If an exception occurs during execution of any native task code, the error results are returned in the packed native response in the same position as in a normal response. Execution continues in this situation.
Segment Definition – Code 07 Availability: Release 3.0 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. Primarily, this request determines a starting point from which to obtain the definitions.
Series 500 NIM Primitive Descriptions (continued) Change State Primitive – Code 10 Availability: Releases 1.1, 2.1, 2.2, and 3.0 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.
Read Block Primitive – Code 20 Availability: Releases 1.1, 2.1, 2.2, and 3.0 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 TT Definition Data element type NNNN Number of locations AAAA Data element location Response: LLLL 20 HH DD ...
Series 500 NIM Primitive Descriptions (continued) Read Random Block Primitive – Code 21 Availability: Releases 2.1, 2.2, and 3.0 Primitive 21 is a command to read several random blocks of contiguous memory. Request: LLLL 21 TT NNNN AAAA 8 9 Symbol Value TT Definition Data element type NNNN Number of locations AAAA Data element location Response: LLLL 21 HH XX BB DD ...
Write Block Primitive – Code 30 Availability: Releases 1.1, 2.1, 2.2, and 3.0 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 ...
Series 500 NIM Primitive Descriptions (continued) Symbol Value Definition HH Attached device operational status XX Number of block writes not completed due to error BB 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. Valid blocks will complete without returning a Primitive error. Block Data Acquisition Primitive Codes 50, 51, and 52 Availability: Releases 1.1, 2.1, 2.2, and 3.
Symbol Value Definition CC Block number (1–20 hex) TT Data element type NNNN Number of locations AAAA Data element location Response: LLLL 50 HH Symbol Value HH 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. The blocks are specified through a 32-bit mask (EEEEEEEE).
Series 500 NIM Primitive Descriptions (continued) Symbol HH EEEEEEEE DD Value Definition Attached device operational status 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.
Symbol Value TT Definition Data element type AAAA Data element location DD Data Response: LLLL 52 HH EEEEEEEE DD ... DD (repeated) Symbol HH EEEEEEEE DD SIMATIC TIWAY I Series 500 NIM User Manual Value Definition Attached device operational status EEEEEEEE is a mask as defined by the Request Primitive 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.
Series 500 NIM Primitive Descriptions (continued) Record Data Acquisition Primitive Codes 55, 56, and 57 Availability: Releases 2.1, 2.2, and 3.0 The Record Data Acquisition Primitives allow repetitive collection of multiple predefined blocks of data. The Define Record Primitive (55) allows multiple blocks of data to be defined as a single record. The Gather Record Primitive (56) collects the data blocks for the requested records.
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 HH Definition Attached device operational status Gather Record Primitive – Code 56. The Gather Record Primitive specifies which records (as defined by define Record Primitive 55) will be read.
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. The Records are specified by record numbers from 1 to 20 (hex). The total number of bytes returned by the record(s) must not cause the response to exceed the maximum frame length.
Symbol Value Definition XX Number of records in error CC Record numbers in error DD 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 & Download Primitive Codes 58 and 59 Availability: Release 3.0 Primitives 58 and 59 transfer various types of program or configuration data to and from a secondary. All data is transferred by data blocks.
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. If a sequence error is detected, the host can try to request the data as far back as the previous two transactions.
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. Upload Request Parameter Descriptions.
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 HH XX YYYY Attached device status 00 Block upload accepted.
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.
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 YYYY WW Value Definition Upload sequence count which is initially set to 0 and incremented by 1 on each subsequent upload request. The response will contain the same value as was sent to the attached device during the request.
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. Abort Upload Request and Response Request: LLLL 58 03 RRRR Response: LLLL 58 HH 04 RRRR The abort upload command immediately stops the upload request. The command will also return the attached device to the state prior to the request.
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 ...
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 HH XX Definition Attached device status 00 Entered download mode 01 Download data was received and valid 02 Download complete 03 Reserved 04 Download aborted, exited mode 05 Download command (XX) not supported, reamin in download mode.
Series 500 NIM Primitive Descriptions (continued) Like the program upload primitive, there are four forms of the download request.
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. The response will contain the same value as was sent in the request.
Series 500 NIM Primitive Descriptions (continued) Download Examples The following pages contain examples of download requests for various conditions. Summary of Primitives 4-58 NIM Primitives Table 4-8 summarizes the Series 500 NIM Primitives.
Table 4-8 Summary of Primitives Format Primitive "F E 8 9 )))) :: ! E )))) :6 +++ )))) :6 +++ E )))) :? )))) :? "" '' E ! ' E )))) :A )))) :A """" '''' 0000 LLLL &&&& &&&& )))) :7 )))) :7 "" '' 00 -- +++ -- ! E )))) :4 )))) :4 8##9 8% 9 61 +++ 8 9 8
Series 500 NIM Primitive Descriptions (continued) Table 4-8 Summary of Primitives (continued) Primitive $ - Format E )))) A6 ## +++ 8 9 )))) A6 >> -- +++ -8 >> 9 - 0 3 - E )))) 4: ## )))) 4: E )))) 46 """""""" )))) 46 """""""" 8 9 +++ 8 9 $ 0 3 - E )))) 4? """""""" ## )))) 4? """""""" E
Table 4-8 Summary of Primitives (continued) Primitive ( Format E )))) 42 :: %%%% )))) 42 :6 .... +++ )))) 42 :? )))) 42 :A )))) 42 :: %%%% )))) 42 :6 .... $$ ;; +++ 8 9 )))) 42 >> 8.... 9 E )))) 4B :: %%%% )))) 4B :6 ....
Series 500 NIM Primitive Descriptions (continued) Table 4-9 Summary of Primitives (Extended Addressing) Format Primitive "F E 8 9 )))) :: ! E )))) 26 +++ )))) 26 +++ E )))) 2? )))) 2? "" '' E ! ' E )))) 2A )))) 2A """" """" LLLL &&&& &&&& )))) 27 )))) 27 "" '' 00 -- +++ -- ! E )))) 24
Table 4-9 Summary of Primitives (Extended Addressing) (continued) Primitive $ - Format E )))) -6 ## 8 9 )))) -6 >> -- +++ -- +++ 8 >> 9 E )))) : ## )))) : 0 3 - E )))) 6 """""""" )))) 6 """""""" $ 0 3 - E )))) ? """""""" ## )))) ? """""""" - 8 9 +++ 8 9 +++ +++ 8 9 8
Series 500 NIM Primitive Descriptions (continued) Table 4-9 Summary of Primitives (Extended Addressing) (continued) Primitive ( Format E )))) )))) )))) )))) )))) 2 :: %%%% )))) 2 :6 .... $$ ;; 2 :: %%%% 2 :6 .... +++ 2 :? 2 :A +++ 8 9 )))) 2 >> 8....
Appendix A PM550 CIM Requirements A.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2 A.2 Local Line Length . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3 A.3 Local Line Bias and Termination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A.1 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.
A.2 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. However, in networks containing the PM550 CIM, which is not a TIWAY I conformant device, the Local Line length is restricted to 10,000 feet and 9600 baud.
A.3 Local Line Bias and Termination For TIWAY I networks using the Local Line, some devices are provided with a toggle switch to allow selection of bias or no bias for the Local Line. Other devices have self-biasing built in and therefore have no Bias Switch. The CIM is provided with a jumper which allows selection of bias or no bias.
2. 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.
Appendix B Floating Point Numbers B.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2 B.2 IBM Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-3 B.3 IEEE Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
B.1 Introduction The Series 500 NIM allows IBM 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. If the sign bit is set to one, the floating point number is a negative value. If the bit is set to zero, the number is positive.
B.2 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; that is, it is shifted to the left to eliminate leading zeros between the radix point and the first signficant bit.
IBM Format (continued) "> )" < F $ $ 6 $ ? - 6: 6+: :+4 *6+: :+:A6?4 6::+: 766: 7:2: 66: A'2: 7?17 :::: :::: :::: :::: :::: : 6 $ G F ' ? $ ) - - "F 8C 9 82 9 "" D - ) 61 D D "D ' E - ! < - 6: = 8*69 J 61 8""61 * 7: 61 9 J 8 J 61
B.3 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 7F . It is also different in that it represents a power of 2 instead of 16. The exponent for 2 is represented in memory by 7F . Negative exponents are represented by numbers less than 7F . For example, a 2– is represented in the exponent field by by a value of 7E . The exponents may be any value from –7E to +7F (2– to 2 ).
IEEE Format (continued) "> )" < - 6: F $ 6+: :+4 *:+4 :+:A6?4 6::+: A'2: A':: -':: A :: 7? 2 :::: :::: :::: :::: :::: 6 $ ) - - "F 82 9 8C 9 ? $ ) 61 Figure B-2 IEEE Floating Point Representation B-6 Floating Point Numbers SIMATIC TIWAY I Series 500 NIM User Manual
Appendix C Network Configuration Data Sheet ) 0" " ) " ' # % - , 3 ' , F " "#$% & % " " ' # % # # SIMATIC TIWAY I Series 500 NIM User Manual Network Configuration Data Sheet C-1
DATA DEFINITION TABLE Date Name or Identifier C-2 Data Type Network Configuration Data Sheet Starting Address Number of Record Elements Number Block Number Length (Bytes) SIMATIC TIWAY I Series 500 NIM User Manual
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.
# $ . "#$% & "/ )( # % '% J #" %' "M(" #< @@@@,@@@@,@@@@ J ( #% " % .< % # # "< " < #")" % "< 8@@@@@9 @@@@@@@@@ * @@@@@@@@@@@@@@@@@@@@@@ J " % # # "< @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ % "< J% 0 #% %' "M(" #< J ) # % < J % % " % # % (#" < J %0 0 ) 0( 0"< J ) % ") # ) ) M( ) #.
Appendix E Specifications Environmental Specifications Operating temperature range Storage temperature range Operating humidity range Vibration Power Requirements Model 5039: 1.25 watts, –5 VDC; 8 watts, +5 VDC 0 to 60 C (32 to 140 F) –40 to 85 C (–40 to 185 F) 0 to 95% relative humidity NAVMAT P9492 Model 5040: 0.06 watts, –5 VDC; 8 watts, +5 VDC Communications Data Rates 110; 150; 300; 600; 1,200; 2,400; 4,800; 9,600; 19,200; 38,400; 57,600; 115,200 bits per second.
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).
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 ...
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 Would you be interested in giving us more detailed comments about our manuals? Yes! Please send me a questionnaire. No. Thanks anyway.
FOLD NO POSTAGE NECESSARY IF MAILED IN THE UNITED STATES BUSINESS REPLY MAIL FIRST CLASS PERMIT NO.3 JOHNSON CITY, TN POSTAGE WILL BE PAID BY ADDRESSEE ATTN: Technical Communications M/S 519 SIEMENS ENERGY & AUTOMATION INC.
$ $ $ % & $" #' & ! " #
