Page 3 - ii
Page 4 - iii; Multi-vendor connections
iii NT4S/NT15S/NT18SProgrammable Terminal Multi-vendor connections Produced March 1999
Page 5 - iv
Page 8 - vii; TABLE OF CONTENTS; xiii
vii TABLE OF CONTENTS PRECAUTIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii 1 Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv 2 General Precautions . . . . . . ....
Page 9 - viii
viii 5.4 Data Type Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 5.5 Additional Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ...
Page 10 - ix
ix 10.3 Protocol Parameters Mitsubishi MelsecA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 10.4 Parameters of the AJ71C24 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 10.5 Data Types . . . ...
Page 12 - xi
xi About this Manual: This manual describes how to connect the NT4S, NT15S and NT18S to non Omron PLC’s. Please read this manual carefully and be sure you understand the information provided before attempting toinstall and operate the NT-series programmable terminal NT4S/NT15S/NT18S.
Page 13 - xii; Related Manuals and Their Contents:
xii Related Manuals and Their Contents: The related manuals are listed below. The n symbol at the end of the manual number is the revision history number. [Connecting the NT4S/NT15S/NT18S to PLC’s other than Omron.] N NT4S/NT15S/NT18S Programmable terminal, multi-vendor connections(V058-E1- n ) . . ...
Page 14 - PRECAUTIONS
xiii PRECAUTIONS This section provides general precautions for using the Programmable Terminal. The information contained in this section is important for the safe and reliable application of the ProgrammableTerminal. You must read this section and understand the information contained before attempt...
Page 15 - Precautions; Intended Audience; General Precautions; Safety Precautions
xiv Precautions 1 Intended Audience This manual is intended for the following personnel, who must also have knowl-edge of electrical systems (an electrical engineer or the equivalent). N Personnel in charge of introducing FA systems into production facilities. N Personnel in charge of designing FA s...
Page 16 - xv; Explanation of Symbols
xv Precautions The conventions used and their meanings are presented below. WARNING Indicates information that, if not heeded, could possibly result in loss of life or seri-ous injury. CAUTION Indicates information that, if not heeded, could result in relatively serious or minorinjury, damage to the...
Page 17 - xvi
Page 18 - SECTION 1
1 SECTION 1 Siemens PU (AS511) 1.1 General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 1.2 Technical Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ....
Page 20 - General Information
3 General Information Section 1-1 1.1 General Information The operating terminals can be conveniently connected to the Siemens PLCs S90 -S155 thus making the operating terminals the perfect man-machine-interface foryour Siemens PLC.The operating terminal is connected to the PU (programming unit) int...
Page 21 - Technical Description
4 Technical Description Section 1-2 - No configuration required within the PLC. - The PU protocol is handled entirely by the firmware of the PLC. A PLC program(function blocks, etc.) in the PLC is not required to handle the communication. - The protocol provides error control. Transmission errors ar...
Page 22 - Parameter Maximum Waiting Time for Response; Data Type Structure
5 Data Type Structure Section 1-4 1.3.1 Parameter Maximum Waiting Time for Response This timer indicates the length of time that the operating terminal (master) waits forthe response from the PLC (slave).Permitted values are in the range of 0 ms to 65535 ms.The default value is 500 ms. This value mu...
Page 24 - Data Types
7 Data Type Structure Section 1-4 1.4.1 Data Types Direct accessing of the following data types is possible: E input bits (bit access, read-only) A output bits (bit access) M flag bits (bit access) EB input bytes (byte access, read-only) AB output bytes (byte access) MB flag bytes (byte access) EW i...
Page 25 - Additional Functions
8 Additional Functions Section 1-5 1.5 Additional Functions In addition to the random read and write access to PLC variables, a 11-byte memo-ry area is specified in the application description as a poll area. The location of thismemory area can also be specified in the application description. The o...
Page 26 - Error Messages
9 Error Messages Section 1-6 1.6 Error Messages Code 1 E SLAVE NOT READY . . . . . . . . . .Slave not ready2 E PROTOKOL . . . . . . . . . . . . . . . . . . . .Sequence of the packets3 E FRAME . . . . . . . . . . . . . . . . . . . . . . . . .Protocol frame error4 E TIMEOUT . . . . . . . . . . . . . ....
Page 27 - Guidance for the Employment of CPUs with 2 PU Interfaces
10 Guidance for the Employment of CPUs with 2 PU Interfaces Section 1-7 1.7 Guidance for the Employment of CPUs with 2 PUInterfaces CPUs with 2 PU interfaces (e.g. 928B with PU module) are used during systemcommissioning thus keeping the PU interface available for program debugging. Please note that...
Page 31 - Protocol Parameters GE Fanuc SNP; Configuring the PLC
14 Protocol Parameters GE Fanuc SNP Section 2-2 2.2 Protocol Parameters GE Fanuc SNP The parameters of the interface SER1 are set to the following values: Baud rate: 300, 600, 1200, 2400, 4800, 9600, 19200, 38400, 357000,500000 Baud Parity: none, even, odd Data length: 5, 6, 7, 8 bits Stopbits: 1, 1...
Page 42 - SINEC L1; Section 4
25 SINEC L1 Section 4 The operating terminals allow for a simple connection to the Siemens S95 - S155programmable controllers thus making the operating terminals the perfect man-machine-interface for your Siemens PLC. With the programmable controllers 95U, 100U (CPU 103) and 155U, the operatingtermi...
Page 43 - Protocol Parameters SINEC L1
26 Protocol Parameters SINEC L1 Section 4-1 4.1 Protocol Parameters SINEC L1 To ensure proper communication, the parameters must not be altered. Baud rate: 9600 Baud Parity: even Data length: 8 Stopbits: 1 Handshake: no handshake The operating terminal adapts to the default parameters of the SINEC L...
Page 45 - Status Data Area
28 Configuring the PLC Section 4-3 d) Floating Point NumberThe data are interpreted in the Siemens floating point format. e) Binary Variables with a Length of 1, 2 or 4 BytesData with a length of 2 bytes are interpreted in the PLC-conformal byte order forwords.Data with a length of 4 bytes are inter...
Page 47 - SINEC L1-Data Handling Software for S5 115U; Installation
30 Error Messages Section 4-4 54 E RECV LEN . . . . . . . . . . . . . . . . . . . . .The length of the data received, exceeded 64 bytes. 55 E DEST . . . . . . . . . . . . . . . . . . . . . . . . . . .The destination in the telegram from the PLC to the terminaldoes not correspond to 0 (mas-ter addres...
Page 48 - Interface to the Application Software
31 SINEC L1-Data Handling Software for S5 115U Section 4-5 4.5.2 Interface to the Application Software The interface to the PLC application software is not of a very complex design. Thisis due to the fact that the supplied function blocks handle the entire data exchangeprocess with the operating ter...
Page 49 - Communications Function Block FB201; SINEC L1 Data Handling Software for S5 135U with CP530
32 SINEC L1-Data Handling Software for S5 115U Section 4-5 4.5.4 Communications Function Block FB201 FB201 must be executed by OB1 at cyclic intervals. The handling of the data ex-change with the operating terminal is performed entirely by this function block. Thisprocess involves that the FB, each ...
Page 52 - SECTION 5
35 SECTION 5 3964/RK512 5.1 General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 5.2 Technical Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ....
Page 55 - PLC Configuration
38 Technical Description Section 5-2 5.2 Technical Description The terminal is always the active partner which either requests data from or sendsdata to the partner.Direct read-access is possible to all PLC data.Direct write-access is limited to data blocks only. The installation of the supplied fun...
Page 58 - Special Simatic-Data Formats
41 Additional Functions Section 5-5 5.4.2 Special Simatic-Data Formats The following data formats are supported in the editors:KB 0 to 255Variable in byte-format KF -32768 to +32767Variable in 16-bit fixed point number-format KH 0000 to FFFFVariable in 4-digit hexadecimal number-format DH 00000000 t...
Page 60 - Block Check BCC; Message Request of Data
43 Message Request of Data Section 5-7 Terminal active partner passive partner STX . , DLE (NAK) Data . DLE . ETX . BCC (selectable) . , DLE (NAK) Please note:If the character 10 16 is to be transmitted but not to be evaluated as a DLE, the transmitting device will add another 10 16 . If the receivi...
Page 61 - Structure Message Header (10 bytes) Request of Data
44 Message Request of Data Section 5-7 5.7.1 Structure Message Header (10 bytes) Request of Data Function ASCII Hex Comment 1. Byte Message 00 always 00 2. Byte identifier 00 always 00 3. Byte Data direction E 45 E = Request 4. Byte Command see below 5. Byte 2 Byte see below 6. Byte Source 7. Byte 2...
Page 62 - Coordination Flag; Message Transmission of Data
45 Message Transmission of Data Section 5-8 5.7.3 Coordination Flag A flag bit is specified in the message header which is used by the receiving deviceto monitor the receipt of data.The monitoring function is deactivated if the value for the coordination flag is FF 16 , FF 16 . If a coordination fla...
Page 63 - Structure Message Header (10 bytes) Transmission of Data
46 Message Transmission of Data Section 5-8 5.8.1 Structure Message Header (10 bytes) Transmission of Data Function ASCII Hex Comment 1. Byte Message 00 always 00 2. Byte identifier 00 always 00 3. Byte Data direction A 41 A = Transmission 4. Byte Command D 44 D = Data block 5. Byte 2 Byte Destinati...
Page 64 - Function Block for Siemens 115 U; Protocol 3964R - Restrictions
47 Function Block for Siemens 115 U Section 5-10 A write-access to these data types is principally carried out with a coordination flag.Just like the communications block, the coordination flag must be defined such thatthe settings in the terminal and passive device are in agreement. Part of a progr...
Page 66 - Initialization of Module K43 of EBERLE PLS514
49 Initialization of Module K43 of EBERLE PLS514 Section 5-12 5.12 Initialization of Module K43 of EBERLE PLS514 For communication with the module K43 of an EBERLE PLS 514 the followingparameters must be set: For TTY-Interfacing:Baud rate: 9600 Parity: even Data bits: 8 Stop bits: 1 Handshake: no ha...
Page 85 - Parameter Target Module
68 Technical Description Section 7-2 7.2 Technical Description The interfacing of the operating terminal to the Bosch PLCs is effected by means ofthe BUEP19 PU-protocol. The PU protocol BUEP19 allows random read and write access to all PLC data.Any byte-structured data types can also be accessed in ...
Page 93 - Protocol Parameters BUEP19E; Parameter Block Check
76 Protocol Parameters BUEP19E Section 8-3 8.3 Protocol Parameters BUEP19E The operating terminal adapts to the default parameters of the interface. It is there-fore not necessary to modify the interface parameters in the PLC. Baud rate: 9600 Baud Parity: even Data bits: 8 Stop bits: 1 Handshake: no...
Page 101 - Protocol Parameters Allen Bradley; Parameter Controller Type
84 Protocol Parameters Allen Bradley Section 9-3 9.3 Protocol Parameters Allen Bradley The operating terminal adapts to the default parameters of the PU-interface. It istherefore not necessary to modify the interface parameters in the PLC.To ensure proper communication, the parameters must not be al...
Page 104 - Mitsubishi MelsecA
87 SECTION 10 Mitsubishi MelsecA 10.1 General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 10.2 Technical Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ...
Page 107 - Protocol Parameters Mitsubishi MelsecA; Parameter Maximum Waiting Time for Response
90 Protocol Parameters Mitsubishi MelsecA Section 10-3 10.3 Protocol Parameters Mitsubishi MelsecA The parameters of the interface SER1 are set to the following values: Baud rate: 300, 600,1200, 2400, 4800, 9600, 19200, 38400, 357000,500000 Baud Parity: none, even, odd Data bits: 5, 6, 7, 8 Stopbits...
Page 123 - Protocol Parameters Jetter; Parameter Maximum Waiting Time for Response
106 Protocol Parameters Jetter Section 12-3 12.3 Protocol Parameters Jetter The following parameters are set for the protocol PASE/PASE-E: Baud rate: 300, 600, 1200, 2400, 4800, 9600, 19200, 38400, 357000,500000 Baud Parity: none, even, odd Data bits: 5, 6, 7, 8 Stop bits: 1, 1.5, 2 Handshake: no ha...
Page 125 - KBS
108 Additional Functions Section 12-6 12.6 Additional Functions Cyclic Poll Area In addition to the random read and write access to PLC variables, a memory areacomprising 12 bytes is specified in the application description as cyclic poll area. This data area must be referenced to a 24-Bit-Integer-R...
Page 126 - The high-byte is not used
109 Error Messages Section 12-7 Memory Mapping of the Parallel Message System Example: Status messages starting with register 200, with a size of 6 bytes havingbeen defined High-Byte Mid-Byte Low-Byte 16 8 7 1 Register 200 32 24 23 17 Register 201 48 40 39 33 Register 202 etc. The high-byte is not u...
Page 131 - Protocol Parameters SUCOM1 PS4-201
114 Protocol Parameters SUCOM1 PS4-201 Section 13-3 13.3 Protocol Parameters SUCOM1 PS4-201 The parameters of the interface SER1 are set to the following values: Baud rate: 300, 600, 1200, 2400, 4800, 9600, 19200, 38400, 375000,500000 Baud Data bits: 5, 6, 7, 8 Stop bits: 1, 1.5, 2 Parity: none, eve...
Page 134 - Idec Micro3
117 SECTION 14 Idec Micro3 14.1 General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 14.2 Technical Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ....
Page 137 - Protocol Parameters IDEC Micro 3; Parameter Maximum Waiting Time for Response
120 Protocol Parameters IDEC Micro 3 Section 14-3 14.3 Protocol Parameters IDEC Micro 3 The operating terminal adapts to the default parameters of the PU interface. It istherefore not necessary to adapt the interface parameters in the PLC.To ensure proper connection, do not modify the parameters. Ba...
Page 142 - Protocol Parameters ABB CS31
125 Protocol Parameters ABB CS31 Section 15-3 15.1 General Information The operating terminals can be easily connected to ABB CS31 controllers.The programming interface COM1 is used to connect the operating terminal.Data traffic on the interface is handled by the ASCII plain text protocol. The softw...
Page 143 - Parameter Maximum Waiting Time for Response
126 Data Type Structure Section 15-4 15.3.1 Parameter Maximum Waiting Time for Response This parameter indicates the length of time that the operating terminal waits for theresponse from the PLC.Permitted values are in the range of 1 ms to 65535 ms.The default value is 1000 ms. 15.3.2 Parameter Dela...
Page 151 - Protocol Parameters ABB T200; Parameter Maximum Waiting Time for Response
134 Protocol Parameters ABB T200 Section 16-3 16.3 Protocol Parameters ABB T200 The interface parameters of the operating terminal are adapted to the default para-meters of the PU interface. Baud rate: 300, 600, 1200, 2400, 4800, 9600, 19200, 38400, 375000,500000 baud Parity: none, even, odd Data bi...
Page 158 - INDEX; Symbole
141 INDEX Symbole 3964 Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 3964/RK512. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 3964 Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 A Additional Functions . . . . . . ....
Page 162 - Revision History
Revision History A manual revision code appears as a suffix to the catalog number on the front cover of the manual. Cat. No. V058-E1-1 M Revision code The following table outlines the changes made to the manual during each revision. Page numbers refer to theprevious version. Revision code Date Revis...