SIMATIC TI505/TI500 MODNIM User Manual Order Number: PPX:505-8122-1 Manual Assembly Number: 2586546-0083 Original Edition
Copyright 1993 by Siemens Industrial Automation, Inc. All Rights Reserved — Printed in USA Reproduction, transmission or use of this document or contents is not permitted without express consent of Siemens Industrial Automation, Inc. All rights, including rights created by patent grant or registration of a utility model or design, are reserved. Since Siemens Industrial Automation, Inc.
MANUAL PUBLICATION HISTORY SIMATIC TI505/TI500 MODNIM User Manual Order Manual Number: PPX:505-8122-1 Refer to this history in all correspondence and/or discussion about this manual. Event Date Description Original Issue 03/93 Original Issue (2801280–0001), Software Release 3.
LIST OF EFFECTIVE PAGES Pages Cover/Copyright History/Effective Pages iii — ix 1-1 — 1-20 2-1 — 2-39 A-1 — A-4 B-1 — B-2 C-1 — C-3 D-1 — D-6 Index-1 — Index-3 Registration Description Original Original Original Original Original Original Original Original Original Original Original Pages Description
Contents Preface Chapter 1 1.1 1.2 1.3 1.4 1.5 1.6 Installation and Set-up Modbus Communications Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 Modbus Network Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modbus Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transmission Modes . . . . . . . .
1.7 Establishing Communications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-19 Verifying that the MODNIM is Logged into the PLC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Connecting the Network Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Recommended Communication Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Appendix A A.1 A.2 Network Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2 Recommended Communication Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Building Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cable Pinouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
List of Figures Figure 1-1 Figure 1-2 Figure 1-3 Figure 1-4 Figure 1-5 Figure 1-6 Figure 1-7 Figure 1-8 Figure 1-9 Figure 1-10 Figure 1-11 Figure 1-12 Figure 1-13 Figure 1-14 Multidrop and Point-to-point Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Quick Reference Installation Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Address Setting Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 2-28 Figure 2-29 Figure 2-30 Figure 2-31 Figure 2-32 Figure 2-33 Figure 2-34 Figure 2-35 Coil Bit Pattern . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Write Multiple Coils Example — Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Write Multiple Registers Example — Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Write Multiple Registers Example — Response . . . . . . . .
List of Tables Table 1-1 Table 1-2 Table 1-3 Table 1-4 Transmission Mode Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Status of Indicator Lights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Indicator Status after User-Initiated Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Standard Communication Cables . . . . . . . . . . . . . . . . . . . . . . . . .
Preface Purpose of this Manual Related Manuals This manual provides the following information on the Series 505 and Series 500 MODNIM (Modbus Network Interface Module), model numbers PPX:505–5184 and PPX:500–5184. • Basic features of the MODNIM • Installation and configuration • Diagnostic self-testing procedures • Operating instructions • Modbus commands and error responses • MODNIM specifications The following publications contain related information which supplement this manual.
Chapter 1 Installation and Set-up 1.1 1.2 1.3 1.4 1.5 1.6 1.7 Modbus Communications Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 Modbus Network Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modbus Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transmission Modes . . . . . . . . . . . . . .
1.1 Modbus Communications Overview Modbus Network Characteristics The Modbus system is a Local Area Network (LAN) designed to work in an industrial environment. It is a master/slave network in which a number of slave nodes (e.g., Programmable Logic Controllers, or PLCs) are connected to a Master Node, which is a host computer. Modbus Protocol The Modbus protocol determines how messages are passed between the host computer and the secondary nodes. Up to 247 slaves can reside on a single network.
Details of the ASCII and RTU modes of transmission are listed in Table 1-1. Table 1-1 Transmission Mode Characteristics Characteristic ASCII RTU 7 bits hexadecimal (ASCII printable) 8 bits binary Start 1 1 Data 7 8 Stop 1 or 2 1 or 2 Optional Optional LRC CRC Code used: Bits per character: Parity Checksum NOTE: On multidrop networks, the MODNIM requires a commercial modem to connect to the Modbus network, as shown in Figure 1-1.
1.2 Quick Reference Installation Steps General Requirements Procedures In order to install and use the MODNIM module correctly, you must meet the following requirements. • Ensure that you have the appropriate MODNIM model. • The communications configurations of all devices attached to the network must match; i.e., they must all have the same baud rate, stop bits, parity, handshaking, and transmission mode (ASCII or RTU).
Handling the Module Many integrated circuit (IC) devices are susceptible to damage by the discharge of static electricity. Follow the suggestions listed below to reduce the probability of damage to these devices when you are handling this Network Interface module, the PLC, a base controller, or any of the I/O modules. Both the module and the person handling the module should be at the same ground potential. Also, follow these guidelines.
1.3 Setting the Dipswitches Dipswitch Functions The MODNIM module has two blocks of dipswitches. • The block of 8 dipswitches is used to select the MODNIM’s address on the network. • The block of 10 dipswitches is used to configure the network communications parameters. NOTE: The configuration and address switch settings are read only once following a power-up or RESET. Be sure to reset the MODNIM following any change in dipswitch settings or PLC memory configuration.
Selecting Network Configuration Parameters The block of 10 dipswitches is used to configure the network communication parameters, which include data transmission rate, stopbit selection, parity, transmission mode, RTS/CTS handshaking, and output coil mapping. (NOTE: For all Series 500 MODNIM dipswitch settings, see Figure 1-6.) Data Transmission Rate Switches 1 through 4 are used to set the data transmission rate. All devices on the network must be configured to communicate at the same data rate.
Setting the Dipswitches (continued) Series 505 MODNIM MODNIM NIM GOOD — Base power and MODNIM operating status NIM PC GOOD GOOD XMT — Data Transmit indicator ON LINE — Connected to the Modbus network.
Series 500 MODNIM NIM GOOD PC/NIM COMM GOOD ONLINE • Push to reset Reset RECEIVE TRANSMIT Self-Test TEST MODE 1. 2. 3. 4. Local/Remote Select Local control Remove network cables Install Loopback connectors Press Reset and Self-Test together and hold 5 seconds.
1.4 Installing the MODNIM Installing the Series 505 MODNIM in the I/O Base ! WARNING To install the Series 505 MODNIM in the selected slot of the I/O base, follow these steps. To avoid the possibility of personal injury, damage to the module, altering the PLC memory, or causing a PLC fatal error, disconnect power to the base’s power supply and to any modules installed in the base before inserting or removing the MODNIM. 1. Disconnect power to the I/O base. 2.
Network Configuration Network Address 1 0 Baud Rate (19200 shown) 1 2 4 8 16 32 64 128 Network address is determined by the sum of the values of selected switches. (Address 2 shown) Stop bits 2 or 1 Parity OFF/ON Parity ODD/EVEN Mode RTU/ASCII RTS/CTS: OFF/ON C coils/Y outputs Note: D = side of switch to press down.
Installing the MODNIM (continued) Installing the Series 500 MODNIM in the I/O Base You can key the Series 500 MODNIM module to prevent another I/O module from being inserted by mistake into the two slots reserved for the MODNIM module. To do this, insert the three keys provided in the right slot of the two slots occupied by the module so that they fit into the notches in the edge card of the module. (See Figure 1-9.
Once the I/O slot keys are in place, you can insert the module as follows. 1. Set the dipswitches, described in Section 1.3. 2. Position the module so that the front bezel is facing you. 3. Hold the top and bottom of the bezel and carefully slide the module into the slot, pushing it all the way into the base connector. When the module is fully seated in the I/O base, locking tabs will hold the module in place. (See Figure 1-10.
1.5 Switches and Indicator Lights Switches and Buttons The three switches located on the face of the module behind the access door are Reset, Self Test, and Local/Remote, and are described in the following paragraphs. Reset Button The Reset button is a momentary-contact switch which initializes the MODNIM and initiates the power-up self test. When you press Reset, all the indicators turn on for approximately 1 second. Then, all indicators except TEST go off for about 5 seconds.
Status Indicator Lights The MODNIM has six indicator lights (or LEDs) located on the faceplate of the module (see Figure 1-11). These lights indicate the operational or diagnostic status of the module as described below.
1.6 Diagnostic Tests Built-in Diagnostic Tests Power-up Self Test The MODNIM has the following three levels of self tests available. • Power-up Self Tests • Run-time Self Tests • User-initiated Self Tests The MODNIM executes a Power-up Self Test in the following cases. • Immediately after you apply +5 VDC power from the I/O base as part of initialization. • Any time the Reset button is pressed. The Power-up Self Test checks the processor and performs a test of on-board RAM and ROM.
Run-time Self Tests The MODNIM monitors itself continuously during normal operation as follows. • The operating system continuously performs a ROM integrity test as a background process. • The MODNIM periodically verifies that it is capable of communicating with the PLC. • A Watchdog Timer circuit in the MODNIM guards against software lockup. If any failures are detected in the ROM integrity test, the NIM GOOD indicator light turns off and the MODNIM is forced into the failed state.
Diagnostic Tests (continued) User-Initiated Self Test The User-Initiated Self Test performs a complete test of the MODNIM hardware, including the communications ports. To run this test, follow the steps listed below. NOTE: Since this test includes the communications ports, be sure to disconnect the MODNIM from the network. 1. Disconnect network cables from both network ports of the MODNIM. 2. Install the loopback connectors supplied with your module on ports A and B of the MODNIM. 3.
1.7 Establishing Communications Verifying that the MODNIM is Logged into the PLC After installing and configuring the MODNIM, you should verify that the module is properly logged into the PLC I/O map. NOTE: The PLC I/O map is the first thing to check if the PC GOOD (PC/NIM COMM GOOD) indicator light is off. Connect your programming device to the PLC to verify PLC-to-MODNIM module communication by following these steps. 1. Access the Configure I/O function menu, then execute Show. 2.
Establishing Communications (continued) 4. Look at the chart for the number corresponding to the slot occupied by the MODNIM module. If an S or SF (Special Function) and word memory locations (or 8 Ys) appear on this line, the module is registered in the PLC memory. Assign a unique I/O address to the module and execute a Write PC function. You can now begin to communicate with the MODNIM.
Chapter 2 Modbus Commands 2.1 2.2 2.3 2.4 2.5 Modbus Protocol Overview — ASCII Transmission Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2 Modbus Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The ASCII Transmission Frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The Start Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1 Modbus Protocol Overview — ASCII Transmission Mode Modbus Protocol This chapter examines the Modbus protocol for both ASCII and RTU modes of transmission. The MODNIM-supported functions are then described in detail, with examples of requests and responses for each function code. The ASCII Transmission Frame Each frame in the ASCII transmission mode begins with a colon ( : ) and ends with CR LF (Carriage Return/Line Feed), shown in Figure 2-1.
Table 2-1 Modbus Functions Supported Code Type Description 01 Read Coil Status Get current status of a group of coils. 02 Read Input Status Get current status of a group of discrete inputs. 03 Read Holding Register Get current values from holding registers. 04 Read Input Register Get current values from input registers. 05 Force a Single Coil Change the state of a logic coil to On or Off, forced On or forced Off, or unforced.
2.2 Modbus Protocol Overview — RTU Transmission Mode The RTU Transmission Frame The RTU mode determines the start and finish of a message based on a time period of silence (no transmission) equivalent to the time it would take to transmit 3.5 characters at the chosen baud rate. The RTU transmission frame is shown in Figure 2-2. Address Function Data Checksum No data 8 bits 8 bits n x 8 bits 16 bits T1 T2 T3 T1 T2 T3 . . . represents a time of 3.5 characters at given baud rate.
Checksum The checksum needs 16 bits and uses the Cyclic Redundancy Checksum (CRC) method. The calculation of this checksum is described in the Modbus Protocol Reference Manual. Invalid Characters and Messages The MODNIM ignores messages that contain invalid characters. Messages containing the following errors are also ignored.
2.3 Comparing Modbus Functions with TIWAY I Network Commands Modbus Functions vs. TIWAY Commands This section outlines some of the differences between Modbus and TIWAY I network commands. • Whereas Modbus uses Functions Codes, TIWAY I uses Primitives. Primitives differ from Function codes in one important way: primitives use TT-types to allow one primitive to address different types of data. With Modbus a different function code is required for each type of data.
Addressing The MODNIM uses the absolute position of the data for the address. That is, if you want to address the 3066th coil, then that is the address you pass with the command (as hexadecimal value BFA). The maximum address is 65535 (FFFF hex). All current PLCs are within this limit.
2.4 Modbus Function Descriptions Introduction In the descriptions that follow, each function starts on a separate page and includes the TIWAY primitive sent to the secondary in square brackets. For each function, an example of request and response is given. NOTE: As Mode-specific data is not given, each of these examples omits the header ( : ) and tail (CR/LF) of ASCII mode. Code 01 — Read Coil Status ! CAUTION Code 01 enables the user to read the On/Off values of logic coils.
Response: 07 01 01 1A XXXX Checksum (XXXX) Data (1A) Number of bytes (01) Function code (01) Slave address (07) Figure 2-5 Read Coil Status Example — Response The response returns in the data field a single byte (1A) which contains the 1’s or 0’s for the 5 coils, packed out with zeros for the three high bits.
Modbus Function Descriptions (continued) Code 02 — Read Input Status Code 02 allows the application to read a series of discrete inputs. The command includes the start address and the number of points to be read. Addressing is sequential up to the maximum memory size for a particular PLC. The maximum number of inputs that can be addressed with one command is 2000. If more are requested, the whole command will be rejected with an Exception code 03.
The response returns in the data field a single byte (1A) containing the 1’s or 0’s for the 5 discrete inputs, packed out with zeros for the three high bits.
Modbus Function Descriptions (continued) Code 03 — Read Output Registers Code 03 allows you to read the contents of holding registers in the attached secondary device. The data field of this command includes the start address of the registers and the number of registers to be read. Addressing is sequential up to the maximum memory size for a particular PLC. The maximum number of registers that can be addressed with one command is 125.
Code 04 — Read Input Registers Code 04 allows you to read the contents of input registers in the attached PLC. These registers hold the values returned by the I/O devices. The data field of this command includes the start address of the registers and the number of registers to be read. Addressing is sequential up to the maximum memory size for a particular PLC. The maximum number of registers that can be addressed with one command is 125.
Modbus Function Descriptions (continued) Code 05 — Write a Single Coil Code 05 allows a designated coil (discrete output Y or C) to be written. Depending on the code in the data field, it can be changed to On (1) or Off (0), forced On or Off, or unforced. The two-byte codes are the following. FF00 (hex) . . . . . . . 0000 (hex) . . . . . . . . 1100 (hex) . . . . . . . . 2200 (hex) . . . . . . . . 3300 (hex) . . . . . . . .
Response: 07 05 0064 FF00 XXXX Checksum (XXXX) OFF/ON code (FF00 = ON) Coil address (0064) Function code (05) Slave address (07) Figure 2-15 Read Input Register Example — Response The response to Function Code 05 is to return the request as received. In the case of a broadcast request, there is no response.
Modbus Function Descriptions (continued) Code 06 — Write a Single Register Code 06 allows the contents of a holding register to be changed. Addressing is sequential up to the maximum memory size for a particular PLC. This function is limited to integer values contained in V-memory. The MODNIM will also direct any broadcast address (00) to all attached secondaries. [This command is comparable to a TIWAY I request using Primitive 30 and TT-type 01 (Variable memory)].
Code 07 — Read Exception Status Code 07 instructs the MODNIM to read 8 predefined coils within a secondary. This implementation will read the first 8 coils (first 8 Ys or first 8 Cs, depending on the position of the dipswitch) in the discrete image register in a secondary and pack them into one data byte. NOTE: The programmer of a non-Modbus PLC must make certain that the application program running within the PLC will place meaningful data in these locations. This data can reflect status information.
Modbus Function Descriptions (continued) The response shows that 3B (hex) has been returned. If the individual bits are examined, they indicate the status of each bit.
Code 08 — Execute Diagnostics ! WARNING Code 08 enables diagnostic information to be retrieved to conduct network testing. This function does not affect the operation of the PLC, but may have significant effects on the operation of the MODNIM. Where these effects impact upon the operation of the MODNIM, they are described with the details for that diagnostic code.
Modbus Function Descriptions (continued) Table 2-4 details the diagnostic codes supported.
The diagnostics codes supported are described in the following paragraphs. Diagnostic Code — 00 0000 | any data Information frame Diagnostic code When Function Code 08 uses diagnostic code 0000, any data passed in the information field is returned to the host computer by the addressed secondary node without change. The purpose of this command is to determine if the communications are functioning correctly, and may be used in conjunction with diagnostic tests described later.
Modbus Function Descriptions (continued) Diagnostic Code — 02 0002 | 00 00 Information frame Diagnostic code When Function Code 08 uses diagnostic code 0002, the information field may contain any value (00 00 shown). The MODNIM returns a 16-bit word containing diagnostic data about the attached device. The meaning of each bit is given in Table 2-5. Table 2-5 Diagnostic Bits Bit Description 0 O. S. RAM parity error 1 Program RAM parity error 2 O. S.
Diagnostic Code — 03 0003 | Char 00 Information frame Diagnostic code When Function Code 08 uses diagnostic code 0003, the ASCII character given in the information field is then used as the delimiter of an ASCII mode message replacing the standard LF (line feed) character.
Modbus Function Descriptions (continued) Diagnostic Code — 0A 000A | 00 00 Information frame Diagnostic code When Function Code 08 uses diagnostic code 000A and any value in the information field (00 00 shown), all diagnostic registers and counters within the MODNIM will be cleared. This also happens when the power is cycled or the RESET button is pressed. This code has a significant effect on the operation of the MODNIM.
Diagnostic Code — 0C 000C | 00 00 Information frame Diagnostic code When Function Code 08 uses diagnostic code 000C and any value in the information field (00 00 shown), the information field will return the number of checksum errors detected by the MODNIM since the last RESET or power-up. The counter will increment to a value of FFFF (65535) and will then return to zero (0). This code has no effect on the operation of the MODNIM.
Modbus Function Descriptions (continued) Diagnostic Code — 0E 000E | 00 00 Information frame Diagnostic code When Function Code 08 uses diagnostic code 000E and any value in the information field (00 00 shown), the information field will return the number of messages addressed to the MODNIM since the last RESET or power-up. The counter will increment to a value of FFFF (65535) and will then return to zero (0). This code has no effect on the operation of the MODNIM.
Diagnostic Code — 10 0010 | 00 00 Information frame Diagnostic code When Function Code 08 uses diagnostic code 0010 and any value in the information field (00 00 shown), the MODNIM will return 0000 in the information field. This code has no effect on the operation of the MODNIM. This Modbus diagnostic code has no equivalent in Series 500 or Series 505 PLCs. In this application, 0000 is always returned.
Modbus Function Descriptions (continued) Diagnostic Code — 12 0012 | 00 00 Information frame Diagnostic code When Function Code 08 uses diagnostic code 0012 and any value in the information field (00 00 shown), the information field will return the number of character overruns detected by the MODNIM since the last RESET or power-up. This indicates the number of times that characters have arrived faster than the UART can store them without loss.
Diagnostic Code — 14 0014 | 00 00 Information frame Diagnostic code When Function Code 08 uses diagnostic code 0014 and any value in the information field (00 00 shown), the MODNIM will clear the character overrun counter. This command affects the operation of the MODNIM.
Modbus Function Descriptions (continued) Code 11 — Get Comms Event Counter Code 11 returns a 2-byte status word and an associated 2-byte event counter. The status word is defined in the Modbus Protocol Reference Specification as being 0 for no command in progress and FFFF if a previous command is in progress. The status will always be 0 in the MODNIM. The event counter is incremented for every successful message; it is not incremented for exceptions or polls, or for this code or Code 12.
Code 12 — Get Comms Event Log Code 12 returns the same information as Function Code 11 plus a message count and an additional 64-event byte. This means that a 2-byte status word, a 2-byte event counter, a message count, and the most recent 64 events are returned. A buffer records each send or receive operation and overwrites the oldest event with the latest event. No events are recorded for this code or Code 11. The Event Byte types are shown in Table 2-6.
Modbus Function Descriptions (continued) Table 2-6 Event Byte Types Event Byte 2-32 Bit Definitions Slave Bus Receive. Byte stored on receipt of message Bit 0 – Reserved Bit 1 – Set if communications error Bit 2 – Reserved Bit 3 – Reserved Bit 4 – Set if character overrun Bit 5 – Set if in Listen Only mode Bit 6 – Set if Broadcast Bit 7 – 1 Slave Bus Transmit.
Code 15 — Write Multiple Coils Code 15 allows the host computer to write multiple coils. When this command is given, successive coils are changed by an associated bit pattern to the indicated state, where each bit indicates: 1 = ON 0 = OFF Addressing is sequential up to the maximum memory size for a particular secondary. The maximum number of coils that can be addressed with one command is 800. If more are given, the whole command will be rejected with an Exception code 03.
Modbus Function Descriptions (continued) This request is for the secondary node to change the values of 12 (0C hex) coils starting at address 12 (18 decimal) to the states given by the following bit pattern.
Code 16 — Write Multiple Registers Code 16 allows the host computer to write multiple values into successive registers. Addressing is sequential up to the maximum memory size for a particular PLC. The maximum number of registers that can be addressed with one command is 100. If more are given, the whole command will be rejected with an Exception code 03. [This command is equivalent to a TIWAY I request using Primitive 30 with TT-type 01 (Variable memory)].
Modbus Function Descriptions (continued) Code 17 — Report Slave ID Code 17 permits the user to get information from the slave concerning its type, run mode, and other device-dependent data. [This command has no direct equivalent to a TIWAY I request, but elements of this function are contained in Primitives 02 and 03 (Status primitive and Configuration primitive).] The MODNIM returns a number in the Slave ID field determined by the type of PLC connected and responds with the state of the RUN light.
The options for each of the fields in the response are listed in Table 2-7. Table 2-7 Function Code 17 Response Options Option Code Description 20 25 2C 30 3C 35 45 55 60 65 75 SIMATIC TI520 SIMATIC TI525 SIMATIC TI520C SIMATIC TI530 SIMATIC TI530C SIMATIC TI535 SIMATIC TI545 SIMATIC TI555 SIMATIC TI560 SIMATIC TI565 SIMATIC TI575 00 FF OFF ON 00 Operational and performing instruction data type and loop execution (RUN).
2.5 Error Responses Errors such as illegal addressing or failure of communications with a PLC are reported by exception responses. Exception responses replace the expected response to a request and are recognized by the Function Code with the top bit set high (see examples in Figure 2-34 and Figure 2-35). Request: Start Address Function Data LRC EOF Ready 07 01 00000041 AD CR LF Start Address Function Except.
Table 2-8 list the exception responses that apply to the functions supported by the MODNIM. Table 2-8 Exception Responses Code Name Description 01 Illegal Function The function received is not defined for this application [equivalent to SIMATIC TI exception codes 00, 01, 06, 15].
Appendix A Network Cable Communications A.1 A.2 Network Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2 Recommended Communication Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Building Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cable Pinouts . . . . . . . . . . . . . . . . . . .
A.1 Network Cables Recommended Communication Cables Building Cables Cable Pinouts The following cables are available through your Siemens distributor. Cable P/N Description Adapter at Module 2601094–8001 Standard 9-pin null modem 9-pin (F) to 25-pin (M) port adapter VPU200–3605 Standard 25-pin null modem None required If you prefer to build your own 25-pin cable, ensure that the following requirements are met to minimize the possibility of noise interference.
Host (DTE) Series 505 or 500 MODNIM (DTE) Shield 1 14 2 3 4 5 6 1 TD RD RD RTS RTS CTS CTS DSR DSR GND 7 DTR 20 25 8 TD DCD 2 14 3 4 5 6 7 DCD 8 9 9 10 10 11 11 12 12 13 13 20 DTR 25 Figure A-2 MODNIM to Host (with Handshaking) Commercial Modem (DCE) Series 505 or 500 MODNIM (DTE) Shield 1 14 2 3 4 5 6 1 RD TD TD RD RTS RTS CTS CTS DSR DSR GND 7 DTR 20 25 8 DCD 2 14 3 4 5 6 7 DCD 8 9 9 10 10 11 11 12 12 13 13 20 DTR 25 Figure A-3 MODNIM t
A.2 Communications Parameters RS-232-C Pin Assignments The modem interface is a standard Type E DTE configuration as defined in the EIA RS-232-C standard. This interface uses a male 25-pin D-type connector plug on the communication cable. The pin assignments are listed in Table A-1.
Appendix B Exception Codes B.1 Exception Codes Supported by the MODNIM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
B.1 Exception Codes Supported by the MODNIM Table B-1 lists the subset of SIMATIC TI Exception Codes that are mapped to the Modbus exception codes. Table B-1 Exception Codes Exception Code (hex) B-2 Exception Codes Definition 00 The primitive is not implemented. 01 Data type is not defined in the attached device. 02 Data element location is out of range. 06 Device in wrong mode for primitive execution.
Appendix C Specifications C.1 Environmental Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-2 C.2 MODNIM Communications Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
C.1 Environmental Specifications The Series 505 I/O subsystem is tested against some of the most stringent standards in the world. Table C-1 lists specifications that are common to Series 505 I/O devices. Table C-1 Environmental Specifications Operating Temperature 0° to 60°C (32° to 140°F) Storage Temperature –40° to +70°C (–40° to 158°F) Relative Humidity 5% to 95% non-condensing Pollution Degree 2, IEC 664, 664A Vibration Sinusoidal IEC 68-2-6, Test Fc; 0.15 mm, peak-to-peak, 10–57 Hz; 1.
C.2 MODNIM Communications Specifications Table C-2 lists communication and other specifications of the MODNIM.
Appendix D Using the MODASST Program D.1 D.2 D.3 Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-2 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
D.1 Getting Started Overview MODASST is a Configuration and Diagnostic Assistant software program which can be used to help set up and use your MODNIM or TIWAY Gateway product. This program is provided to assist you in configuring the modules and verifying that the module is communicating. The program can also help verify that your MODNIM or TIWAY Gateway is operational when you are installing it.
Running the Program from the Hard Disk To set up this program on your computer’s hard drive, follow these steps. 1. Insert the disk into the appropriate slot in your computer. 2. At the DOS prompt on your machine, type: c: Enter cd\ Enter md\modasst Enter cd\modasst Enter copy a:*.* c:\modasst Enter To run the program on your computer’s hard drive, at the DOS prompt type: c: Enter cd\modasst modasst Enter Enter You will now see the start-up screen. Press Enter to continue.
D.2 Starting Program Operation Setting the Communication Port Options When the program begins, you will be prompted for the communications port number that you wish to use to communicate from your computer to the MODNIM or TIWAY Gateway module. Use the up and down arrows on your keyboard to select the communications port from COM1 to COM4. If you don’t need to set up advanced options for your COM port, press Enter to continue.
D.3 Using Program Options Setup Options Figure D-2 shows the first menu and the sub-menu available after pressing ALT S to choose the Setups option from the top menu. You can also press F10 to access the top menu, and, since Setups is the default, press Enter .
Using Program Options (continued) Find Module Settings The Find Module option is available when you want to communicate with a MODNIM or TIWAY Gateway module and the communications parameters are not known. This selection tries the various parameter combinations until either a successful match of communications parameters is found, or all combinations have been tried.
Index A Address, setting network address, 1-6 Address 0, 2-8 Address 1, 2-8 Address field, 2-2 Addressing, limits, 2-7 ASCII transmission mode, 1-2–1-3, 2-2–2-3 ASCII/RTU mode selection, 1-7 B Baud rate, 1-8, 1-9 Broadcast mode, 1-2, 2-3, 2-14, 2-16, 2-19, 2-31, 2-33, 2-35 Diagnostic bits, 2-22 Diagnostic codes, 2-20–2-29 Diagnostic tests power-up, 1-16 run-time, 1-17 user-initiated, 1-18, D-2–D-6 Dipswitches ASCII/RTU mode selection, 1-7 data transmission rate, 1-7 example setting, 1-11 handshaking selec
Handshaking MODNIM to host, A-3 MODNIM to modem, A-3 Modbus commands function code descriptions, 2-8–2-37 protocol, 2-2–2-7 Help contacting distributor, 1-5 distributor, sales office, ix Modbus functions supported, 2-3 I Modbus manuals, ix Modbus network characteristics, 1-2 Modbus protocol, 1-2 ASCII transmission mode, 1-2–1-3, 2-2–2-3 RTU transmission mode, 1-2–1-3, 2-4–2-5 I/O definition chart, 1-19–1-21 Modbus vs.
Q Quick reference installation, 1-4 Switches function, 1-14 location, 1-8, 1-9 Switches and indicator lights, 1-14–1-15 R Read coil status, 2-8 T Read exception status, 2-17 Technical assistance, ix Read input registers, 2-13 Test button, 1-14 Read input status, 2-10 Test mode LED, 1-15, 1-16, 1-18 Read output registers, 2-12 TISOFT, ix, 1-19 Ready field, 2-3, 2-23 TIWAY primitives, 2-6, C-3 vs.
SIMATIC is a registered trademark of Siemens AG. MODNIM, Series 500, Series 505, 5TI, PM550, PM550C, TISOFT, and TIWAY are trademarks of Siemens Industrial Automation, Inc. Modbus is a trademark of Modicon, Inc. Texas Instruments and TI are registered trademarks of Texas Instruments Incorporated. TI500, TI505, TI520, TI520C, TI530, TI530C, TI525, TI535, TI545, TI555, TI560, TI565, and TI575 are trademarks of Texas Instruments Incorporated.
Customer Registration 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 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 SIEMENS INDUSTRIAL AUTOMATION, INC. 3000 BILL GARLAND RD. P.O.
