Cat.No.
i
ii
NT4S/NT15S/NT18S Programmable Terminal Multi-vendor connections Produced March 1999 iii
iv
OMRON Product References All OMRON products are capitalized in this manual. The word ‘Unit’ is also capitalized when it refers to an OMRON product, regardless of whether or not it appears in the proper name of the product. The abbreviation ‘Ch,’ which appears in some displays and on some OMRON products, often means ‘word’ and is abbreviated ‘Wd’ in documentation in this sense. The abbreviation ‘PC’ means Programmable Controller and is not used as an abbreviation for anything else.
vi
TABLE OF CONTENTS PRECAUTIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 2 3 xiii Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . General Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Safety Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.4 5.5 5.6 5.7 5.8 5.9 5.10 5.11 5.12 5.13 Data Type Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3964 Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message Request of Data . . .
.3 10.4 10.5 10.6 10.7 Protocol Parameters Mitsubishi MelsecA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Parameters of the AJ71C24 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Data Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional Functions. . . . . . . . . . . . . . . . . . . . . . . . . . .
SECTION 16 ABB T200 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16.1 16.2 16.3 16.4 16.5 x 131 General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Technical Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Protocol Parameters ABB T200 . . . . . . . . . . . . . . . . . . . . . . . . . . .
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 to install and operate the NT-series programmable terminal NT4S/NT15S/NT18S.
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) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . This manual The NT4S/NT15S/NT18S can also be connected to other PLC’s then Omron only.
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 Programmable Terminal. You must read this section and understand the information contained before attempting to set up or operate a Programmable Terminal. 1 2 3 Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Precautions 1 Intended Audience This manual is intended for the following personnel, who must also have knowledge 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 systems. N Personnel in charge of installing and connecting FA systems. N Personnel in charge of managing FA systems and facilities.
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 serious injury. CAUTION Indicates information that, if not heeded, could result in relatively serious or minor injury, damage to the product, or faulty operation. Explanation of Symbols This manual uses the following symbols to indicate notes and hazardous situations.
xvi
SECTION 1 Siemens PU (AS511) 1.1 1.2 1.3 1.4 1.5 1.6 1.7 General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Technical Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Protocol Parameters Siemens PU AS511 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Section 1-1 General Information 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 for your Siemens PLC. The operating terminal is connected to the PU (programming unit) interface of the PLC. An additional communications module is not necessary. The data communication on the interface is handled by the PU protocol AS511.
Section 1-2 Technical Description - 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 are detected and, if possible, eliminated by repeating the transmission.
Section 1-4 Data Type Structure 1.3.1 Parameter Maximum Waiting Time for Response This timer indicates the length of time that the operating terminal (master) waits for the 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 must be increased when using a CPU with two PU interfaces (see „Guidance for the employment of CPUs with 2 PU interfaces”). 1.3.
Section 1-4 Data Type Structure All other addresses The count value is interpreted in BCD-code. This allows transfer of this value within the PLC program to the counter by means of the accumulator. This service should be used for indirect write-operations of count values since the values are available in the Siemens conforming format. c) Timer Timer functions consist of a time value and a time base.
Section 1-4 Data Type Structure 1.4.
Section 1-5 Additional Functions 1.5 Additional Functions In addition to the random read and write access to PLC variables, a 11-byte memory area is specified in the application description as a poll area. The location of this memory area can also be specified in the application description. The only marginal conditions regarding this memory area is that the PLC must be able to access in bit-mode and the terminal in byte-mode and the memory area must be contiguous.
Section 1-6 Error Messages 1.6 Error Messages Code 1 2 3 4 E E E E SLAVE NOT READY . . . . . . . . . .Slave not ready PROTOKOL . . . . . . . . . . . . . . . . . . . .Sequence of the packets FRAME . . . . . . . . . . . . . . . . . . . . . . . . .Protocol frame error TIMEOUT. . . . . . . . . . . . . . . . . . . . . . .Timeout error 6 7 8 9 10 E E E E E PARITY. . . . . . . . . . . . . . . . . . . . . . . . .Parity error SEND ABORT . . . . . . . . . . . . . . . . .Send process aborted REC ABORT . . . .
Guidance for the Employment of CPUs with 2 PU Interfaces 1.7 Section 1-7 Guidance for the Employment of CPUs with 2 PU Interfaces CPUs with 2 PU interfaces (e.g. 928B with PU module) are used during system commissioning thus keeping the PU interface available for program debugging. Please note that the interfaces are interacting (see Siemens CPU manual).
SECTION 2 GE Fanuc SNP 2.1 2.2 2.3 2.4 2.5 2.6 General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Protocol Parameters GE Fanuc SNP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2.1 Parameter Maximum Waiting Time for Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2.
Section 2-1 General Information 2.1 General Information The operating terminals allow for a simple connection to every GE FANUC PLC of the 90 series thus making the operating terminals the perfect man-machine-interface for your FANUC PLC. The operating terminal is connected to the Programming and Communications Port of the PLC-CPU. An additional communications module is not necessary. The data communication on the interface is handled by the FANUC-Series 90 protocol (SNP-protocol).
Section 2-2 Protocol Parameters GE Fanuc SNP 2.2 Protocol Parameters GE Fanuc SNP The parameters of the interface SER1 are set to the following values: Baud rate: Parity: Data length: Stopbits: Handshake: 300, 600, 1200, 2400, 4800, 9600, 19200, 38400, 357000, 500000 Baud none, even, odd 5, 6, 7, 8 bits 1, 1.5, 2 No handshake, Hardware, Software The default parameters of the programming software are printed bold. The operating terminal adapts to the default parameters of the SNP protocol.
Section 2-5 Additional Functions 2.4 Data Types User references are bit, byte, or word-structured.
Section 2-6 Error Messages Example: The cyclic data on %R1 Register %R1 %R2 %R3 %R4 %R5 %R6 2.6 High byte Write Coordination Byte Message Channel High byte LED 1 to 4 LED 9 to 12 LED 17 to 20 LED 25 to 28 Low byte Reserved Message Channel Low byte LED 5 to 8 LED 13 to 16 LED 21 to 24 LED 29 to 32 Error Messages Code 1 E SLAVE NOT READY . . . . . . . . . .Slave not ready or incorrect CPU-ID 2 E PROTOKOL . . . . . . . . . . . . . . . . . . . .Sequence of the packets 3 E FRAME . . . . . . . . . . . . . .
SECTION 3 Mitsubishi FX 3.1 3.2 3.3 3.4 3.5 3.6 General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Technical Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Protocol parameters Mitsubishi FX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Section 3-1 General Information 3.1 General Information The operating terminals allow for a simple connection to every Mitsubishi PLC of the FX series thus making the operating terminals the perfect man-machine-interface for your Mitsubishi PLC. The operating terminal is connected to the programming unit interface of the PLC. An additional communications module is not necessary. The data communication on the interface is handled by the Mitsubishi FX protocol.
Section 3-2 Technical Description 3.2 Technical Description The interfacing of the operating terminal to the Mitsubishi-FX Series- PLCs is effected by means of the FX protocol. The FX protocol allows random read and write access to all PLC (programmable logic controller) data. Any byte-structured data types can also be accessed in bitmode. The size of the address area depends on the respective PLC. 3.
Section 3-5 Additional Functions 3.5 Additional Functions In addition to the random write and read access to PLC variables, a memory area comprising 11 or 12 bytes is specified in the application description as cyclic data area. The location of this memory area is specified in the mask definition and must be located on a byte boundary. Only marginal conditions regarding this memory area: - the PLC must be able to access in bit-mode - the memory area must be contiguous.
Section 3-6 Error Messages 3.6 Error Messages Code 1 E SLAVE NOT READY . . . . . . . . . .Slave not ready or incorrect CPU-ID 2 E PROTOKOL . . . . . . . . . . . . . . . . . . . .Sequence of the packets 3 E FRAME . . . . . . . . . . . . . . . . . . . . . . . . .Character frame error 4 E TIMEOUT. . . . . . . . . . . . . . . . . . . . . . .Timeout error 5 E CRC BCC. . . . . . . . . . . . . . . . . . . . . .CRC error 6 E PARITY. . . . . . . . . . . . . . . . . . . . . . . . .Parity error 7 E SEND ABORT . .
SECTION 4 SINEC L1 4.1 4.2 4.3 4.4 4.5 4.6 Protocol Parameters SINEC L1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Data Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.2.1 Data Type Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Section 4 SINEC L1 The operating terminals allow for a simple connection to the Siemens S95 - S155 programmable controllers thus making the operating terminals the perfect manmachine-interface for your Siemens PLC. With the programmable controllers 95U, 100U (CPU 103) and 155U, the operating terminal can be connected to the PU interface of the PLC. An additional communications module is not necessary.
Section 4-1 Protocol Parameters SINEC L1 4.1 Protocol Parameters SINEC L1 To ensure proper communication, the parameters must not be altered. Baud rate: Parity: Data length: Stopbits: Handshake: 9600 Baud even 8 1 no handshake The operating terminal adapts to the default parameters of the SINEC L1 interface. Therefore it is not necessary to modify the interface parameters in the PLC. 4.2 Data Types Random read and write access is possible to any data in the PLC.
Section 4-2 Data Types 4.2.1 Data Type Structure a) Alphanumerical Text Is stored in the memory byte for byte in ascending address order. b) Counter A distinction is made between variables which have been assigned a counter address and variables which have been assigned another PLC address. Counter address When accessing counter addresses, the count value is interpreted in the binary format, the control bits of the counter are masked out.
Section 4-3 Configuring the PLC d) Floating Point Number The data are interpreted in the Siemens floating point format. e) Binary Variables with a Length of 1, 2 or 4 Bytes Data with a length of 2 bytes are interpreted in the PLC-conformal byte order for words. Data with a length of 4 bytes are interpreted in the PLC-conformal byte order for long words. 4.
Error Messages Section 4-4 5 E CRC BCC. . . . . . . . . . . . . . . . . . . . . .Checking of BCC1 or BCC2 has revealed a transmission error. 6 E PARITY. . . . . . . . . . . . . . . . . . . . . . . . .Detection of a parity error. 16 E OVERRUN. . . . . . . . . . . . . . . . . . . . . .The interrupt service routine has not picked up the received characters quickly enough from the SIO. Possible cause for the error: - Programming error in the terminal. 17 E NAK . . . . . . . . . . . . . . . . . . . . . . . . .
Section 4-4 Error Messages 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 terminal does not correspond to 0 (master address). Possible cause for the error: - The SINEC L1 interface in the PLC is not accessed by the function block FB201 exclusively (PLC-application program error). 56 E DATA TYPE . . . . . . . . . . . . . . . . . . .
Section 4-5 SINEC L1-Data Handling Software for S5 115U 4.5.2 Interface to the Application Software The interface to the PLC application software is not of a very complex design. This is due to the fact that the supplied function blocks handle the entire data exchange process with the operating terminal via the send mail box and receive mail box. The function blocks merely need to be executed as described above.
SINEC L1-Data Handling Software for S5 115U 4.5.4 Section 4-5 Communications Function Block FB201 FB201 must be executed by OB1 at cyclic intervals. The handling of the data exchange with the operating terminal is performed entirely by this function block. This process involves that the FB, each time it is being executed, verifies whether a read or write request has been received from the terminal and carries out such a request, if necessary.
SINEC L1 Data Handling Software for S5 135U with CP530 4.6.2 Section 4-6 Interface to the Application Software The interface to the PLC application software is not of a very complex design which is due to the fact that the supplied function blocks handle the entire data exchange process with the operating terminal via the send mail box and receive mail box. The function blocks merely need to be executed as described above.
SINEC L1 Data Handling Software for S5 135U with CP530 4.6.4 Section 4-6 Communications Function Block FB201 FB201 must be executed by OB1 at cyclic intervals. The handling of the data exchange with the operating terminal is performed entirely by this function block. This process involves that the FB, each time it is being executed, verifies whether a read or write request has been received from the terminal and carries out such a request if necessary.
SECTION 5 3964/RK512 5.1 5.2 5.3 5.4 5.5 5.6 5.7 5.8 5.9 5.10 5.11 5.12 5.13 General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Technical Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Protocol parameters 3964/RK512 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Section 5-1 General Information 5.1 General Information Via the serial procedure 3964, the operating terminals can be connected to a programmable controller. The logical part of the 3964 protocol, RK512, is adapted to the communication with a Siemens PLC via a CP525, or compatible, communications processor. The software components of the system are fully adapted to the parameters and marginal conditions of the protocol 3964/ RK512.
Section 5-2 Technical Description 5.2 Technical Description The terminal is always the active partner which either requests data from or sends data 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 function block allows an indirect write-access to all PLC data types. All byte-structured data types can also be accessed in bit-mode.
Section 5-4 Data Type Structure 5.4 Data Type Structure a) Alphanumerical Texts Are stored in the memory byte for byte in ascending address order. b) Counter A distinction is made between variables which have been assigned a counter address and variables which have been assigned another PLC address Counter address When accessing counter addresses, the count value is interpreted in the binary format, the control bits of the counter are masked out.
Section 5-4 Data Type Structure d) Floating Point Number The data are interpreted in the Siemens floating point format. e) Binary Variables with a Length of 1, 2 or 4 Bytes Data with a length of 2 bytes are interpreted in the PLC-conformal byte order for words. Data with a length of 4 bytes are interpreted in the PLC-conformal byte order for long words. 5.4.
Section 5-5 Additional Functions 5.4.2 Special Simatic-Data Formats The following data formats are supported in the editors: KB 0 to 255 Variable in byte-format KF -32768 to +32767 Variable in 16-bit fixed point number-format KH 0000 to FFFF Variable in 4-digit hexadecimal number-format DH 00000000 to FFFFFFFF Variable in 8-digit hexadecimal number-format KC !! to zz (2 ASCII-characters each) Variable represented by 2 characters in ASCII-format KT 000.0 to 999.
Section 5-6 3964 Procedure Access to the PLC occurs via: Byte address Byte address +0 Byte address +1 Byte address +2 Byte address +3 Byte address +4 Byte address +5 Byte address +6 Byte address +7 Byte address +8 Byte address +9 Byte address +10 MB MB12 MB13 MB14 MB15 MB16 MB17 MB18 MB19 MB20 MB21 MB22 Description Write Coordination Byte Message Channel Low byte Message Channel High byte Function Key LED 1 to 4 Function Key LED 5 to 8 Function Key LED 9 to 12 Function Key LED 13 to 16 Function Key LED 1
Section 5-7 Message Request of Data Terminal active partner , , passive partner . STX DLE (NAK) Data DLE ETX BCC (selectable) DLE (NAK) . . . . Please note: If the character 1016 is to be transmitted but not to be evaluated as a DLE, the transmitting device will add another 1016. If the receiving device detects a 1016 (DLE) twice, it will accept 1016 only once and will not evaluate it as a DLE control character. 5.6.
Section 5-7 Message Request of Data 5.7.1 Structure Message Header (10 bytes) Request of Data 1. Byte 2. Byte Function Message identifier 3. Byte Data direction E 4. Byte Command see below 5. Byte 6. Byte 2 Byte Source see below 7. Byte 8. Byte 2 Byte Number of bytes see below 9. Byte 10. Byte 5.7.2 ASCII Hex 00 00 Comment always 00 always 00 45 E = Request Coordination flag number FF indicates no coordination flag bit FF Coord.
Section 5-8 Message Transmission of Data 5.7.3 Coordination Flag A flag bit is specified in the message header which is used by the receiving device to monitor the receipt of data. The monitoring function is deactivated if the value for the coordination flag is FF16, FF16. If a coordination flag is specified, it will be set in the passive partner upon receipt of data. Once this flag has been set, processing of the data received will be initiated.
Section 5-8 Message Transmission of Data 5.8.1 Structure Message Header (10 bytes) Transmission of Data Function ASCII 1. Byte 2. Byte Message identifier 3. Byte 4. Byte Data direction Command 5. Byte 6. Byte 7. Byte 8. Byte 9. Byte 10. Byte A D Hex Comment 00 00 always 00 always 00 41 44 A = Transmission D = Data block 2 Byte Destination Data block Data word 2 Byte number of data Number of words Coordination flag number Coordination flag bit FF indicates without FF Coord.
Section 5-10 Function Block for Siemens 115 U 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 that the settings in the terminal and passive device are in agreement. Part of a program installed in the receiving device, denoted in the PLC as data handling block, will monitor the coordination flag.
Section 5-11 Application Example for CP525 in 115U 5.11 Application Example for CP525 in 115U In this example: The communications data block is DB33 starting at DW0. The coordination flag is M100.3. Flag 50 is to be written to. The coordination flag, also referred to as interprocessor communication flag by Siemens, must be activated on the CP525 via a hardware jumper (see reference material (CP525). In addition, the interprocessor communication flag must be defined in DB1 of the 115U.
Section 5-12 Initialization of Module K43 of EBERLE PLS514 5.12 Initialization of Module K43 of EBERLE PLS514 For communication with the module K43 of an EBERLE PLS 514 the following parameters must be set: For TTY-Interfacing: Baud rate: 9600 Parity: even Data bits: 8 Stop bits: 1 Handshake: no handshake Coordination flag: Spec.
Section 5-12 Initialization of Module K43 of EBERLE PLS514 {Initialisierung des K43 Moduls} **********************************************************} { Programmbaustein: INI.
Section 5-12 Initialization of Module K43 of EBERLE PLS514 { { Kommandodigit. } Das Kommandodigit ist das Digit 3 der Ebene 0.} { Die einzelnen Bits haben folgende Bedeutung.} { { { { { { { { { { { { { { { { { Bit 3 2 1 0} _________________} ! ! ! ! !} ! X ! X ! X ! X !} ! ! ! ! !} ————————} ! ! ! !} ! } ! ! ! 0 = ! 1 ! 1 = ! } ! ! X = !} ! 0 = ! 1 = 0 1 Kein SW-Reset } SW-Reset} Keine Bedeutung} K 43 Betriebsart passiv} K 43 sendet über V.
Section 5-12 Initialization of Module K43 of EBERLE PLS514 L A = INIREG0 DACK %NOP { { Definition des Kommandodigits Digit 3 der Ebene 0} ————————————————————————} { { Einstellen der Datenübertragung zum K 43 auf } Initialisierung-Modus} { Digit 0xx3} { { { { { { { { { { { { { Bit { { 0 1 Kein SW-Reset } SW-Reset} K 43 Betriebsart passiv} K 43 sendet über V.24 TTY} = Initialisierung} = Datenaustausch mit K 43 aktiv} { { { { { Eingabe der Konstanten 00 in das Digit 0xx3 } d.h.
Section 5-12 Initialization of Module K43 of EBERLE PLS514 { d.h. 9600 Baud, Datenformat 8 Bit} LD =D %K 14 Data00 { Digit 0xx1} { —————} { } { Bit 3 2 1 0} { _________________} { ! ! ! ! !} { ! X ! X ! X ! X !} { ! ! ! ! !} { ————————} { ! ! ! !} { ! ! !} { ! ! ! 0 = kein Parity-Bit, keine Prüfung (none)} { ! ! ! 1 = Parität wie Bit 1.1 und 1.
Initialization of Module K43 of EBERLE PLS514 { niedrige Priorität, Protokoll 3964 R aktiv.} LD =D %K 11 Data02 { { Initialisierung der Ebene 1} ===========================} { { { { { { { { Die Initialisierung der Datenbausteine erfolgt im } hexadezimalen Code. Bei der Angabe des entsprechenden} Zeichens wird jede Stelle einzeln eingegeben. } D.h. zwei Halbbytes ergeben ein Zeichen und müssen demzu-} folge in zwei Digits eingetragen werden.} } Initialisierung des 0.
Section 5-12 Initialization of Module K43 of EBERLE PLS514 =D Data17 { { Beenden der Initialisierung} —————————————} SL DAS DAS DAL R INIREG K43_E0 K43_E1 K43_E0 %NOP { { Start der Datenübertragung} ==========================} { { { Nachdem die Initialisierung beendet ist, wird die} Datenübertragung durch setzen des Kommandodigits } freigegeben.
Section 5-12 Initialization of Module K43 of EBERLE PLS514 { durch setzen des Kommandodigits } { Bedeutung des Kommandodigits} { { { { { { { { { { { { { Bit 3 2 1 0} _________________} ! ! ! ! !} ! X ! X ! X ! X !} ! ! ! ! !} ————————} ! ! ! !} ! } ! ! ! 0 = ! 1 ! 1 = ! } ! 0 = ! 1 = { { 56 0 1 Kein SW-Reset } SW-Reset} K 43 Betriebsart passiv} K 43 sendet über V.
Section 5-13 Error Messages 5.13 Error Messages These error messages are displayed on the terminal. Code 1 2 3 4 5 6 7 8 9 10 11 E E E E E E E E E E E SLAVE NOT READY . . . . . . .Slave not ready, no connection PROTOKOL . . . . . . . . . . . . . . . . .Invalid character, no repetition FRAME . . . . . . . . . . . . . . . . . . . . . .Byte frame error, despite repetition TIMEOUT . . . . . . . . . . . . . . . . . . . .Timeout error CRC BCC . . . . . . . . . . . . . . . . . . .
Error Messages Section 5-13 Subcode 10 No connection to PU 12 Start address to high Using coordination flag as data type not allowed. CPU-number to high. 16 Invalid Opcode 20 DB not available.
SECTION 6 Klöckner Moeller SUCOM1 6.1 6.2 6.3 6.4 6.5 6.6 General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Technical Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Protocol Parameters SUCOM1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Section 6-1 General Information 6.1 General Information The operating terminals allow for a simple connection to the Klöckner Moeller PLCs PS 306 and PS 316. The operating terminal is connected to the PU interface of the PLC. The data communication on the interface is handled by the SUCOM1 protocol. The software components of the system are fully adapted to the parameters and marginal conditions of the SUCOM1 protocol.
Section 6-2 Technical Description 6.2 Technical Description The interfacing of the operating terminal to the Klöckner Moeller PLCs is effected by means of the SUCOM1 programming protocol. The SUCOM1 protocol allows random read and write access to all PLC data. All data types can also be accessed in bit-mode. The size of the address area depends on the respective PLC. A read access to the addressed word must occur, before individual bits can be accessed for a write operation.
Section 6-5 Additional Functions 6.5 Additional Functions In addition to the random write and read access to PLC variables, a memory area comprising 12 bytes is specified in the application description as cyclic poll area. Only marginal conditions regarding this memory area that the PLC must be able to access in bit-mode and the memory area must be contiguous. The start address of this memory area must be specified in the mask definition and must be located on a word boundary.
Section 6-6 Error Messages 6.6 Error Messages Code 1 E SLAVE NOT READY . . . . . . . . . .Slave not ready or incorrect CPU-ID 2 E PROTOKOL . . . . . . . . . . . . . . . . . . . .Sequence of the packets 3 E FRAME . . . . . . . . . . . . . . . . . . . . . . . . .Character frame error 4 E TIMEOUT. . . . . . . . . . . . . . . . . . . . . . .Timeout error 5 E CRC BCC. . . . . . . . . . . . . . . . . . . . . .CRC error 6 E PARITY. . . . . . . . . . . . . . . . . . . . . . . . .Parity error 7 E SEND ABORT . .
SECTION 7 Bosch PU Interfacing via BUEP19 7.1 7.2 7.3 7.4 7.5 7.6 General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Technical Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Protocol Parameters BUEP19 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Section 7-1 General Information 7.1 General Information The operating terminals allow for a simple connection to the Bosch PLCs. The operating terminal is connected to the respective PLC-module. The data communication on the interface is handled by the PU protocol BUEP19. Communication is possible with any system implementing the BUEP19 protocol. ZE300 / ZE301 / R300 / R301 / R600. The software components of the system are fully adapted to the parameters and marginal conditions of the PU interface.
Section 7-2 Technical Description 7.2 Technical Description The interfacing of the operating terminal to the Bosch PLCs is effected by means of the 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 bit-mode. The size of the address area depends on the respective PLC. A read access must occur, before individual bits or bytes of a flag word can be accessed for a write operation.
Section 7-4 Data Type Structure 7.4 Data Type Structure a) Alphanumerical Text Is stored in the memory byte for byte in ascending address order. b) Counter The count value is interpreted in binary format. The maximum value is 8191. c) Timer Timer functions consist of a time value and a time base. The terminal operates with imaginary unsigned 4-byte variables, even though the data stored in the PLC comprise only 2 bytes.
Section 7-5 Additional Functions 7.5 Additional Functions In addition to the random write and read access to PLC variables, a memory area comprising 12 bytes is specified in the application description as poll area. The location of this memory area is specified in the application description. Only marginal conditions regarding this memory area are that the PLC must be able to access in bit-mode and the terminal in word-mode and the memory area must be contiguous.
Error Messages Section 7-6 Bosch-specific error messages 50 E QUITTUNG START . . . . . . . . . . . .No communication setup 51 E QUITTUNG OPEN . . . . . . . . . . . . .Incorrect acknowledge signal during communication setup 52 E QUITTUNG DATA. . . . . . . . . . . . . .Incorrect acknowledge signal to transmitted information block 53 E NO RESPONSE WRONG CHAR . . . . . . . . . . . . . . . . . . . . . . . . . . . . .No response message 54 E TIMEOUT NO RESPONSE . . . .
SECTION 8 Bosch PU Interfacing via BUEP19E 8.1 8.2 8.3 8.4 8.5 8.6 General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Technical Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Protocol Parameters BUEP19E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Section 8-2 Technical Description 8.1 General Information The operating terminals allow for a simple connection to the Bosch. The operating terminal is connected to the respective PLC-module. The data communication on the interface is handled by the PU protocol BUEP19E. Communication is possible with any system implementing the BUEP19E protocol. CL200 / CL350 / CL400 / CL500 The software components of the system are fully adapted to the parameters and marginal conditions of the interface.
Section 8-3 Protocol Parameters BUEP19E 8.3 Protocol Parameters BUEP19E The operating terminal adapts to the default parameters of the interface. It is therefore not necessary to modify the interface parameters in the PLC. Baud rate: Parity: Data bits: Stop bits: Handshake: 8.3.1 9600 Baud even 8 1 no handshake Parameter Target Module As a target module you can choose between CL500, CL400 or CL200. 8.3.
Section 8-5 Additional Functions Before writing a timer variable to the PLC, the time value and the smallest possible time base are formed from the terminal-internal unsigned 4-byte value. d) Floating Point Number The data with a length of 4 bytes are interpreted in the IEEE floating point format. e) Binary Variables with a Length of 1, 2 or 4 Bytes Data with a length of 2 bytes are interpreted in the PLC-conformal byte order for words.
Section 8-6 Error Messages The data area comprises a maximum of 6 words or 12 bytes. Example: The cyclic data area is set to DW21 in the programming system 8.
Section 8-6 Error Messages 53 E NO RESPONSE WRONG CHAR . . . . . . . . . . . . . . . . . . . . . . . . . . . . .No response message 54 E TIMEOUT NO RESPONSE . . . .Timeout - no response message 55 E TIMEOUT BLOCKZEIT . . . . . . . . .Timeout - block time period has been exceeded 56 E TIMEOUT QUIT RESPONSE . .Timeout - no acknowledge signal 57 E ABBRUCH SPS . . . . . . . . . . . . . . . .EOT -PLC abort Code 2 Subcode 58 E RECEIVE COUNT. . . . . . . . . . . . . .
Section 8-6 Error Messages Code 4 Subcode 32 The requested data type (Command Code) is not known by the PST 33 Protocol flag not known by the PST 35 The given coordination flag is not known by the PST 37 Parameter identifier in the telegram doesn’t fit to the specified parameters 38 Length of block and topic number of data are different 40 Type of telegram unknown 41 Type of command unknown 58 Start address doesn’t fit to the type of operand (Word at odd address) Possible errors: - Module R500 faulty 59 S
SECTION 9 Allen Bradley - Interfacing via DF1 9.1 9.2 9.3 9.4 9.5 9.7 General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Technical Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Protocol Parameters Allen Bradley . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Section 9-2 Technical Description 9.1 General Information The operating terminals allow for a simple connection to the Allen-Bradley PLCs. The operating terminal is connected to the interface of the respective PLC-module. The data communication on the interface is handled by the DF1 protocol. Communication is possible with any system implementing the DF1 protocol (e.g.: MicroLogix 1000-Series, SLC500 with SLC5/03, SLC500 with SLC5/04, PLC5 and PLC5/250).
Section 9-3 Protocol Parameters Allen Bradley 9.3 Protocol Parameters Allen Bradley The operating terminal adapts to the default parameters of the PU-interface. It is therefore not necessary to modify the interface parameters in the PLC. To ensure proper communication, the parameters must not be altered. Baud rate: Parity: Data bits: Stopbits: Handshake: 9.3.1 600, 1200, 2400, 4800, 9600, 19200, 38400, 375000, 500000 Baud none, even, odd 5, 6, 7, 8 1, 1.
Section 9-5 Additional Functions 9.5 Additional Functions In addition to the random write and read access to PLC variables, a memory area comprising 12 bytes is specified in the mask definition as poll area. The location of this memory area is specified in the mask definition. Only marginal conditions regarding this memory area is that the PLC must be able to access in bit-mode and the terminal in word-mode, and the memory area must be contiguous.
Section 9-7 Error Messages 9.7 Error Messages Code 0 Subcode 0 Code 1 Subcode 1 E SLAVE NOT READY . . . . . . . . . .Slave not ready 2 E PROTOKOL . . . . . . . . . . . . . . . . . . . .Sequence of the packets 3 E FRAME . . . . . . . . . . . . . . . . . . . . . . . . .Character frame error 4 E TIMEOUT. . . . . . . . . . . . . . . . . . . . . . .Timeout error 5 E CRC BCC. . . . . . . . . . . . . . . . . . . . . .CRC error 6 E PARITY. . . . . . . . . . . . . . . . . . . . . . . . .
SECTION 10 Mitsubishi MelsecA 10.1 General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.2 Technical Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10.3 Protocol Parameters Mitsubishi MelsecA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Section 10-2 Technical Description 10.1 General Information The operating terminals allow for a simple connection to every Mitsubishi PLC of the An / AnA series. The operating terminal is connected to the communications module AJ71C24. The software components of the system are fully adapted to the parameters and marginal conditions of the interface. This offers the user the following advantages: - Random write and read access to any data within the PLC.
Section 10-3 Protocol Parameters Mitsubishi MelsecA 10.3 Protocol Parameters Mitsubishi MelsecA The parameters of the interface SER1 are set to the following values: Baud rate: Parity: Data bits: Stopbits: Handshake: 300, 600,1200, 2400, 4800, 9600, 19200, 38400, 357000, 500000 Baud none, even, odd 5, 6, 7, 8 1, 1.5, 2 no handshake, hardware, software The default values of the programming system are printed in bold. 10.3.
Section 10-5 Data Types 10.4.3 DIP Switches The following interface settings must be defined: RS422 / RS485 as forward channel, to which the terminal is connected (if available) Data length 7 bits 19200 Baud Parity check, activated Even parity 1 stop bit Check sum, activated Write access, permitted Resistance for Termination Transmit-line, activated (if available) Resistance for Termination Receive-line, activated (if available) The functions of the DIP switches vary with the respective AJ71C24 model.
Section 10-6 Additional Functions 10.6 Additional Functions In addition to the random write and read access to PLC variables, a memory area comprising 12 bytes is specified in the application description as cyclic data area. This data area must be assigned to an address which can be accessed in wordmode. Therefore, the size of the poll area should comprise an equal number of bytes. Word-structured Memory Mapping The data area comprises a maximum of 12 bytes. Example: Cyclic data starting with D1 10.
Error Messages Section 10-7 53 Protocol error Possible errors: - Mode switch does not correspond to the required protocol format. Correct mode switch. 54 Run-time error Possible errors: - The data received do not conform with the number of stop bits selected. Correct DIP switch. 55 Data overflow Possible errors: - New data were transmitted before the preceding transmission was completed. 56 Character set error Possible errors: - Invalid operand address or requested service not available.
SECTION 11 AEG - PU (KS-Functions) 11.1 11.2 11.3 11.4 General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Technical Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Protocol Parameters AEG-KS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Section 11-1 General Information 11.1 General Information The operating terminals allow for a simple connection to PLCs of the AEG Modicon series. The operating terminal is connected to the interface of the ALU. The data communication on the interface is handled by a protocol which is based on the KS-functions of the Modicon series.
Section 11-2 Technical Description 11.2 Technical Description With the aid of the KS-functions, all PLC data can be accessed in read and writemode as well as in bit, byte, word and double word-mode. The size of the address area depends on the respective PLC and its configuration. 11.3 Protocol Parameters AEG-KS The operating terminal adapts to the default parameters of the interface. It is therefore not necessary to modify the interface parameters in the PLC.
Section 10-5 Additional Functions 11.4.1 Data Types Direct accessing of the following data types is possible: E EB EW ED A AB AW AD M MB MW MD MG input bit input byte input word input double word output output byte output word output double word flag flag byte flag word flag double word flag floating point The size of each area is governed by the configuration of the PLC. T TI TS Z ZI ZS 11.
Section 11-6 Error Messages Byte address Byte address +0 Byte address +1 Byte address +2 Byte address +3 Byte address +4 Byte address +5 Byte address +6 Byte address +7 Byte address +8 Byte address +9 Byte address +10 MB MB21 MB22 MB23 MB24 MB25 MB26 MB27 MB28 MB29 MB30 MB31 Description Write Coordination Byte Message Channel Low-byte Message Channel High-byte Function Key LED 1 to 4 Function Key LED 5 to 8 Function Key LED 9 to 12 Function Key LED 13 to 16 Function Key LED 17 to 20 Function Key LED 21 t
Section 11-6 Error Messages AEG - Specific Error Messages: Code 1 Error from the data transmission-layer Subcode 50 E NO POLL QUIT . . . . . . . . . . . . . . .No acknowledge signal upon polling 51 E NO TELE QUIT. . . . . . . . . . . . . . . .No acknowledge signal upon order-message 52 E NO TELE POLL QUITT . . . . . . .No acknowledge signal upon tele-polling 54 E POLL TIMEOUT. . . . . . . . . . . . . . . .Timeout - no response upon polling 55 E TELE TIMEOUT. . . . . . . . . . . . . . . .
SECTION 12 JETTER PASE/PCOM5 12.1 General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.2 Technical Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.3 Protocol Parameters Jetter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Section 12-2 Technical Description 12.1 General Information The operating terminals allow for a simple connection to every JETTER PASE-E and JETTER PASE-Mikro controller. The operating terminal is connected to the RS232 programming unit interface. The software components of the system are fully adapted to the parameters and marginal conditions of the interface. This offers the user the following advantages: - Random read and write access to any data within the PLC.
Section 12-3 Protocol Parameters Jetter 12.3 Protocol Parameters Jetter The following parameters are set for the protocol PASE/PASE-E: Baud rate: Parity: Data bits: Stop bits: Handshake: 300, 600, 1200, 2400, 4800, 9600, 19200, 38400, 357000, 500000 Baud none, even, odd 5, 6, 7, 8 1, 1.
Section 12-5 Address Input (Number of the Variable) 12.4 Data Types Bit Data Types E input A output M flag Word Data Types R 24-Bit-Signed-Integer-Register or 32-Bit-Real-Register T 24-Bit-Text-Register 12.5 Address Input (Number of the Variable) The upper limit of the address input is dependent on the respective PLC. Therefore, please consult the PLC manual.
Section 12-6 Additional Functions 12.6 Additional Functions Cyclic Poll Area In addition to the random read and write access to PLC variables, a memory area comprising 12 bytes is specified in the application description as cyclic poll area. This data area must be referenced to a 24-Bit-Integer-Register-Variable. This variable represents the starting address of the data area. To avoid problems with the signs, the use of the 24-Bit-Integer-Registers is limited to the lower 2 bytes.
Section 12-7 Error Messages Memory Mapping of the Parallel Message System Example: Status messages starting with register 200, with a size of 6 bytes having been 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 used 12.7 Error Messages Code 1 E SLAVE NOT READY . . . . . . . . .Slave not ready or defective cable 2 E PROTOKOL . . . . . . . . . . . . . . . . . . .
SECTION 13 SUCOM1 - PS4-201 13.1 13.2 13.3 13.4 13.5 13.6 General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Technical Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Protocol Parameters SUCOM1 PS4-201 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Section 13-2 Technical Description 13.1 General Information The operating terminals allow for a simple connection to the Klöckner Moeller PLCs PS 4-201. The operating terminal is connected to the PU interface of the PLC. The data traffic on the interface is handled by the SUCOM1 protocol. The software components of the system are fully adapted to the parameters and marginal conditions of the SUCOM1 protocol.
Section 13-3 Protocol Parameters SUCOM1 PS4-201 13.3 Protocol Parameters SUCOM1 PS4-201 The parameters of the interface SER1 are set to the following values: Baud rate: Data bits: Stop bits: Parity: Handshake: 300, 600, 1200, 2400, 4800, 9600, 19200, 38400, 375000, 500000 Baud 5, 6, 7, 8 1, 1.5, 2 none, even, odd no handshake, hardware, software The default parameters of the programming system are printed in bold. 13.4 13.
Section 13-6 Error Messages 13.6 Error Messages Code 1 2 3 4 5 6 7 8 9 10 12 E E E E E E E E E E E SLAVE NOT READY . . . . . . . . .Slave not ready PROTOKOL . . . . . . . . . . . . . . . . . . .Sequence of the packets FRAME . . . . . . . . . . . . . . . . . . . . . . .Character frame error TIMEOUT . . . . . . . . . . . . . . . . . . . . .Timeout error CRC BCC . . . . . . . . . . . . . . . . . . . .CRC error PARITY . . . . . . . . . . . . . . . . . . . . . . .Parity error SEND ABORT . . . . . . . . . .
SECTION 14 Idec Micro3 14.1 General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.2 Technical Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.3 Protocol Parameters IDEC Micro 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Section 14-2 Technical Description 14.1 General Information The operating terminals can be easily connected to Idec Micro3 controllers. The programming interface is used to connect the operating terminal. Data traffic on the interface is handled by the 1:N protocol. The operating terminal is capable of addressing several controllers simultaneously. The software components of the system are fully adapted to the parameters and marginal conditions of the programming unit (PU) interface.
Section 14-3 Protocol Parameters IDEC Micro 3 14.3 Protocol Parameters IDEC Micro 3 The operating terminal adapts to the default parameters of the PU interface. It is therefore not necessary to adapt the interface parameters in the PLC. To ensure proper connection, do not modify the parameters. Baud rate: Parity: Data bits: Stop bits: Handshake: 300, 600, 1200, 2400, 4800, 9600, 19200, 38400, 375000, 500000 Baud none, odd, even 5, 6, 7, 8 1, 1.5, 2 no handshake, hardware, software 14.3.
Section 14-5 Additional Functions 14.4.1 Data Types Direct user access is possible to the following data types: I Input Bit IB Input Byte IW Input Word Q Output Bit QB Output Byte QW Output Word M Flag Bit MB Flag Byte MW Flag Word R Register Bit RB Register Byte RW Register Word DW Data Register Word TP Timer PRESET value Word Constant or data register no., read-only Use the data register to set the timer TC Timer CURRENT value Word read-only CP Counter PRESET value Word Constant or data register no.
Section 14-6 Error Messages 14.6 Error Messages Code 1 Subcode 1 E SLAVE NOT READY . . . . . . . . .Slave not ready 2 E PROTOKOL . . . . . . . . . . . . . . . . . . .Sequence of the packets 3 E FRAME . . . . . . . . . . . . . . . . . . . . . . .Protocol frame error 4 E TIMEOUT . . . . . . . . . . . . . . . . . . . . .Timeout error 5 E CRC BCC . . . . . . . . . . . . . . . . . . . .CRC error 6 E PARITY . . . . . . . . . . . . . . . . . . . . . . .Parity error 7 E SEND ABORT . . . . . . . . . . . . . . .
SECTION 15 ABB CS31 15.1 General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.2 Technical Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.3 Protocol Parameters ABB CS31 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Section 15-3 Protocol Parameters ABB CS31 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 software components of the system are fully adapted to the parameters and marginal conditions of the programming unit (PU) interface.
Section 15-4 Data Type Structure 15.3.1 Parameter Maximum Waiting Time for Response This parameter indicates the length of time that the operating terminal waits for the response 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 Delay Until Connection Setup This parameter specifies the time the operating terminal waits before initiating communication. Permitted values are in the range of 1000 ms to 65535 ms The default value is 5000 ms.
Section 15-5 Additional Functions 15.4.1 Data Types Direct user access is possible to the following data types: E input bit EW input word A output bit AW output word M flag bit MW flag word MD flag double word KW register word KD register double word The addresses to the left and right of the comma are programmed in the programming software in separate columns. When reading from the PLC, variables that are of the same type and are located in an area of up to 50 bytes are read as a block.
Section 15-6 Error Messages Word address + 0 Bit 15 Bit 14 Bit 13 Bit 12 Bit 11 Bit 10 Bit 9 Bit 8 Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 free free free DDF LM PL RQ ED free free free free free free free free LED8 LED8 Word address + 1 Word address + 2 serial message channel high-byte LED1 LED1 LED2 LED2 LED3 serial message channel low-byte LED3 LED4 LED4 LED5 LED5 LED6 LED6 LED7 LED7 on/off flashing on/off flashing on/off flashing on/off flash
Section 15-6 Error Messages Code 2 Subcode 52 E RECEIVE COUNT . . . . . . . . . . . .Number of received data incorrect. Possible errors: - Check if a variable with an odd number of bytes is read from a word or double-word address in the mask in which the error occurs. 54 E ECHO . . . . . . . . . . . . . . . . . . . . . . . . .Echo received and the transmitted data do not match. 70 E RECEIVE ERROR . . . . . . . . . . . .Unknown error from the PLC.
SECTION 16 ABB T200 16.1 General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16.2 Technical Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16.3 Protocol Parameters ABB T200. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Section 16-2 Technical Description 16.1 General Information Operating terminals can be easily connected to ABB T200 controllers. The programming interface or the communication module is used to connect the operating terminal. Data traffic on the interface is handled by the ASCII plain text protocol. The software components of the system are fully adapted to the parameters and marginal conditions of the PLC interface.
Section 16-3 Protocol Parameters ABB T200 16.3 Protocol Parameters ABB T200 The interface parameters of the operating terminal are adapted to the default parameters of the PU interface. Baud rate: Parity: Data bits: Stop bits: Handshake: 300, 600, 1200, 2400, 4800, 9600, 19200, 38400, 375000, 500000 baud none, even, odd 5, 6, 7, 8 1, 1.5, 2 no handshake, hardware, software The default settings in the programming system are printed in bold. 16.3.
Section 16-4 Data Type Structure The button Default can be used to restore the default values in the table. 16.
Section 16-4 Data Type Structure 16.4.
Section 16-4 Data Type Structure 16.4.3 Additional Functions In addition to the random read and write access to PLC variables, a 12 byte memory area is specified in the application description as a poll area. The only marginal conditions regarding this memory area are that the PLC must be able to access in bit-mode and the terminal in word-mode and the memory area must be contiguous. This poll area must point to the flag word area (MW).
Section 16-5 Error Messages 16.5 Error Messages Code 1 2 3 4 5 6 7 8 9 10 12 15 E E E E E E E E E E E E SLAVE NOT READY . . . . . . . . .Slave not ready PROTOKOL . . . . . . . . . . . . . . . . . . .Sequence of the packets FRAME . . . . . . . . . . . . . . . . . . . . . . .Protocol frame error TIMEOUT . . . . . . . . . . . . . . . . . . . . .Timeout error CRC BCC . . . . . . . . . . . . . . . . . . . .CRC error PARITY . . . . . . . . . . . . . . . . . . . . . . .Parity error SEND ABORT . . . . . . . .
Section 16-5 Error Messages Code 52 E TELEGRAM . . . . . . . . . . . . . . . . . . .
INDEX Symbole 3964 Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 3964/RK512. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 3964 Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 A Additional Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 3964/RK512. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 ABB CS31 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Klöckner Moeller SUCOM1 . . . . . . . . . . . . . . . . . . 64 Mitsubishi FX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Mitsubishi MelsecA . . . . . . . . . . . . . . . . . . . . . . . . . . 92 Siemens PU (AS511) . . . . . . . . . . . . . . . . . . . . . . . . 9 SINEC L1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 SUCOM1 - PS4-201 . . . . . . . . . . . . . . . . . . . . . . . . . 115 Error in the Data Section. . . . . . . . . . . . . . . . . . . . . . . .
PLC-Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 Bosch BUEP19. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 Protocol 3964R - Restrictions . . . . . . . . . . . . . . . . . . 47 3964/RK512. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Protocol parameters 3964/RK512 . . . . . . . . . . . . . . . 38 3964/RK512. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 Protocol Parameters ABB CS31 . . . . . . . . . . . . . .
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 the previous version.
Authorized Distributor: Cat. No. V058-E1-1 Note: Specifications subject to change without notice.
Regional Headquarters OMRON EUROPE B.V. Wegalaan 67-69 NL-2132 JD Hoofddorp The Netherlands Tel: +31 (0)23 56 81 300 Fax: +31 (0)23 56 81 388 Website: www.eu.omron.
