CL400 / CL500 R500 Computer Interface Module Module Description Edition 102
CL400 / CL500 R500 Computer Interface Module Module Description 1070 072 131-102 (96.08) GB 1992-1996 by Robert Bosch GmbH, Erbach / Germany All rights reserved, including applications for protective rights. Reproduction or distribution by any means subject to our prior written permission.
Contents 1 1.1 1.2 1.3 1.4 1.5 I Safety Instructions ..................................................................................................................................... 1-1 Proper use ............................................................................................................................................. 1-1 Qualified personnel................................................................................................................................
II Contents 7.3 7.3.1 Protocol-specific Parameters................................................................................................................. 7-2 Command Type / Operand Type Parameters ................................................................................ 7-2 7.3.1.1 Command Type Parameter ........................................................................................................ 7-3 7.3.1.2 Operand Type Parameter ..............................................
Contents III 9.1 9.2 Introduction ............................................................................................................................................ 9-1 Protocol-specific DIP Switch Settings.................................................................................................... 9-2 9.2.1.1 Protocol End Identifier DIP Switch .............................................................................................. 9-2 9.
IV Contents 1070 072 131-102 (96.
Safety Instructions 1 1-1 Safety Instructions Before you start working with the module / software, we recommend that you thoroughly familiarize yourself with the contents of this manual. Keep this manual in a place where it is always accessible to all users. 1.1 Proper use This instruction manual presents a comprehensive set of instructions and information required for the standard operation of the described products.
1-2 Safety Instructions 1.2 Qualified personnel This instruction manual is designed for specially trained personnel. The relevant requirements are based on the job specifications as outlined by the ZVEI and VDMA professional associations in Germany.
Safety Instructions 1.3 Safety markings on components DANGER! High voltage! DANGER! Corrosive battery acid! CAUTION! Electrostatically sensitive components! Disconnect mains power before opening! Lug for connecting PE conductor only! Functional earthing or low–noise earth only! Screened conductor only! 1070 072 131-102 (96.
1-4 Safety Instructions 1.4 Safety instructions in this manual DANGEROUS ELECTRICAL VOLTAGE This symbol warns of the presence of a dangerous electrical voltage. Insufficient of lacking compliance with this warning can result in personal injury. DANGER This symbol is used wherever insufficient or lacking observance of this instruction can result in personal injury. CAUTION This symbol is used wherever insufficient or lacking observance of instructions can result in damage to equipment or data files.
Safety Instructions 1-5 1.5 Safety instructions for the described product DANGER Fatal injury hazard through ineffective Emergency–OFF devices! Emergency–OFF safety devices must remain effective and accessible during all operating modes of the system.
1-6 Safety Instructions CAUTION Danger to the module! All ESD protection measures must be observed when using the module! Prevent electrostatic discharges! Observe the following protective measures for electrostatically endangered modules (EEM)! • The Employees responsible for storage, transport and handling must be trained in ESD protection. • EEMs must be stored and transported in the protective packaging specified.
Hardware Description 2 2-1 Hardware Description The R500 Computer interface module has two equivalent V.24/20 mA serial interfaces which enable the CL400/CL500 controller to be connected to additional Bosch controllers or other communicating devices. 2.1 Power Supply The R500 does NOT require an external power supply. All required operating voltages are taken from the power supply module of the CL400/CL500 controller. 2.
2-2 2.3 Hardware Description Front Panel V.24/20 mA interface Channel 1 Status display for X31 interface Reset button Status display for X32 interface Channel 0 V.24/20 mA interface Version ID / Labelling field 1070 072 131-102 (96.
Hardware Description 2-3 2.3.1 Status Display There is a status display for each of the two channels on the R500 Computer interface module. The H31 7-segment display is linked to Channel 1. The H32 7-segment display is linked to Channel 0. 2.3.2 Interface Connectors The X31 and X32 interface connectors comprise the V.24/20 mA interfaces (please refer to Page 2-5). These interfaces are used for point-topoint connection to an external device. 2.3.
2-4 2.4 Hardware Description CL400/CL500 Slot Assignments A maximum of 5 R500 Computer interface modules can be operated in one PLC. In GG2, slots 4 through 14 are assigned to the CL400. In GG2/K, slots 4 through 8 are assigned. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 Fig. 2-1 CL400 — Slot assignment, GG2 Basic unit 1 2 3 4 5 6 7 8 Fig. 2-2 CL400 — Slot assignment, GG2/K Basic unit In GG2, slots 5 through 14 are assigned to the CL500. In GG2/K, slots 5 through 8 are assigned.
Hardware Description 2.5 2-5 V.24/20 mA Interface The V.24/20 mA interface is available to the user on Channel 0 and Channel 1. Devices which also have a V.24 or 20 mA interface can be connected to the V.24/20 mA interface. The following protocols are available to the user: 2.
2-6 Hardware Description 2.6.1 R500 Block Address The R500 occupies a block on the CL400/CL500 system bus. The R500 block address is selected by means of the S1 DIP switch. The setting procedure is similar to that used with all other modules belonging to the CL400/CL500 PLC series. 2.6.2 Protocol-specific DIP Switch Settings Protocol-specific settings are implemented on the S2 DIP switch.
Hardware Description 2-7 2.6.3 V.24/20 mA Interface Control Signals The control signals (DTR/DSR) for the V.24/20 mA interface can be queried or not queried by setting the SS8 switch segment SS8 of the S3 and S4 DIP switches. NOTE – SS8 to ON - Control signal query enabled SS8 to OFF - Control signal query disabled 2.6.4 V.24/20 mA Interface Transmission Rate The transmission rate for the V.24/20 mA interface is set with switch segments SS5 through SS7 on the S3 and S4 DIP switches.
2-8 2.6.5.1 Hardware Description V.24 Interface Signal Levels and Pin Assignments The signal levels and connector pin assignments correspond to the VDE Guidelines 2880, Page 2, for programmable logic controllers, process and data interfaces.
Hardware Description 2.6.5.2 2-9 20 mA Interface Signal Levels and Pin Assignments The signal levels and connector pin assignments correspond to the VDE Guidelines 2880, Page 2 for programmable logic controllers, process and data interfaces (limit: max. 27 V blocking voltage). Dependent upon the pin assignment, 20 mA interfaces enable active or passive operation, i.e., with or without power supply.
2-10 Hardware Description 2.6.6 V.24/20 mA Interface Cable Length Specifications The maximum permitted interface cable length depends on the baud rate The following length specifications apply to the twisted-pair, shielded 14 x 0.14 Bosch cable, Bosch no. 910152: Transmission rate Baud rate (bps) 110...4800 9600 19200 V.24 [m] 300 300 100 20 mA [m] 350 300 150 Fig. 2-10 V.
Hardware Description 2.7 2-11 Status Displays There is a status display for each channel of the R500 computer interface module. Channel-specific statuses and fault messages are displayed. The H31 seven-segment display is connected to the X31 interface and the H32 to the X32 interface. 2.7.1 Channel-specific Displays These messages are directly allocated to the corresponding channel and consequently to this protocol. Code . P 0..F Explanation Centralised job is being processed.
2-12 2.8 Hardware Description Protocol Loader The transfer protocols are loaded onto the R500 or R500P by means of the PROFI software. The protocol loader for the R500 or R500P module is located in the loader under the Configuration menu option. The protocols are loaded into the R500 module by the SK500 or the ZS400. The protocols must be filed in the BOSCH.BIB subdirectory. 2.
PLC Interface 3-1 3 PLC Interface The PLC interface provides access to the communications system and requires the following function modules: - R5INIT - R5REQ - R5CON The PLC interface can issue jobs to the R500 (client characteristics of the CL400/CL500). The function modules do not monitor the jobs (time-out). Monitoring is implemented in the R500 firmware. NOTE – If the R500 is operated only as a server, function modules are NOT required. 1070 072 131-102 (96.
3-2 PLC Interface 1070 072 131-102 (96.
R5INIT Initialisation Function Module 4-1 4 R5INIT Initialisation Function Module 4.1 Characteristic Data Characteristic data Module name Block length Call-up length Number of parameters Used markers R5INIT R5INIT 871 words 7 words 6 M230 to M254 Fig. 4-1 R5INIT — Characteristic data The R5INIT initialisation function module creates various tables in the ZS and on the computer interface module and fills them with information which is re-accessed when these modules are communicating.
4-2 R5INIT Initialisation Function Module 4.2 I/O Parameters The R5INIT has 5 input parameters and one output parameter. P0 P1 P2 P3 P4 R5INIT P5 4.2.1 Input Parameters Parameter P0 P1 P2 P3 P4 Att. W W W W W Description Module number of computer interface 0 Module number of computer interface 1 Module number of computer interface 2 Module number of computer interface 3 Module number of computer interface 4 Fig.
R5INIT Initialisation Function Module 4-3 4.2.2 Output Parameter Parameter P5 Att. Description W Result Fig. 4-3 R5INIT — Output parameter This parameter provides the PLC program with the result of the initialisation and signals any faults.
4-4 R5INIT Initialisation Function Module 1070 072 131-102 (96.
R5REQ Function Module 5-1 5 R5REQ Function Module 5.1 Characteristic Data Characteristic data Module name Block length Call-up length Number of parameters Used markers R5REQ R5REQ 1051 words 7 words 6 M230 to M254 Fig. 5-1 R5REQ — Characteristic data . 5.2 I/O Parameters The R5REQ function module has four input and two output parameters. P0 P1 P2 P3 1070 072 131-102 (96.
5-2 R5REQ Function Module 5.2.1 Input Parameters Parameter P0 Att. Description W Data type This parameter specifies the type of data range. A data area of 16 words is reserved for each job for the protocol-specific parameters. Data modules (44H), the data buffer (64H) and the data field (43H) can be used as data ranges. The user must always reserve 16 words per job for the parameters which are specific to the job. Parameter P1 Att.
R5REQ Function Module 5-3 5.2.2 Output Parameters Parameter P4 Att. Description W Fault message Basic status and error codes, which the R5REQ identifies when jobs are issued, are entered in this parameter: • The LOW byte in the P4 contains the status or error code, • The HIGH byte contains a coded recommendation concerning a reaction, or response, to the fault message.
5-4 5.3 R5REQ Function Module Explanations of Parameters in Data Range A parameter field of 16 words must be reserved for each job in the data field DF, data buffer DB or data module DM. The address and offset of this data range are specified with the P0 - P2 parameters for the R5REQ module. A bit which starts with Bit 0 (zero) is assigned to each parameter field in the job bit array JBA and in the result bit array RBA.
R5REQ Function Module 5-5 5.3.1 Protocol-independent Parameters Data word Content HIGH byte PLC response CXN DW0 DW1 DW2 LOW byte Error code Channel number Job number Fig. 5-3 R5REQ — Protocol-independent parameters DW0 The 0 data word returns the result of the job. Whenever the R5REQ module is called up, the result of the job is transferred to the module. The result word is divided into LOW byte (error codes), and HIGH byte (PLC response). The error code and PLC response tables are listed below.
5-6 R5REQ Function Module PLC response (HIGH byte) Code 00H 01H 02H 03H 04H 05H 06H 07H 08H Explanation Job transferred without fault to CXN Call up R5REQ again Modify PLC program Modify protocol parameter Rerun program cycle on R5INIT Rerun program cycle on R5REQ Rerun program cycle on R5CON Reload V.24 protocol Check system configuration Fig. 5-5 R5REQ — PLC response DW1 This word indicates on which R500 and via which channel this job is to be processed.
R5REQ Function Module 5-7 5.3.2 Protocol-dependent Parameters The protocol-dependent parameters are described in Sections BÜP19E (Page Fehler! Textmarke nicht definiert.), BÜP03E (Page Fehler! Textmarke nicht definiert.) and BÜP64 (Page Fehler! Textmarke nicht definiert.). 1070 072 131-102 (96.
5-8 R5REQ Function Module 1070 072 131-102 (96.
R5CON Confirmation Module 6-1 6 R5CON Confirmation Module 6.1 Characteristic Data Characteristic data Module name Block length Call-up length Number of parameters Used markers R5CON R5CON 473 words 6 words 5 M230 to M254 Fig. 6-1 R5CON — Characteristic data The R5CON Confirmation module monitors the centralised jobs. Its function is to return information to the user while the job is processing and after the job has ended.
6-2 6.2 R5CON Confirmation Module I/O Parameters The R5CON confirmation module has two input and three output parameters. P0 R5CON P1 P2 P3 P4 6.2.1 Input Parameters Parameter P0 Att. Description W CXN and channel number This parameter indicates the CXN and the number of the channel on which the corresponding job has been processed. Parameter Att.
R5CON Confirmation Module 6-3 6.2.2 Output Parameters Parameter P2 Att. Description W Job number In this parameter the R5CON writes the job number of the job whose status and error codes are in the P3 and P4 output parameters. If an explicit job number was indicated in P1, this job number is mirrored in the P2. If no job has ended with P1 = FFFFH according to the parameterisation, the value FFFFH is signalled back to P2 as a job number.
6-4 R5CON Confirmation Module The P3 LOW byte supplies a code which aids the user in implementing a suitable procedure should a fault occur (PLC response). This code is not valid until the job has ended. LOW byte 00H 01H 02H 03H 04H 05H 06H 07H 08H 09H 0AH 10H 20H 30H 40H 50H Explanation Fault-free operation Repeat call-up of the R5CON function module Modify PLC program Check and modify job parameters Rerun R5INIT program cycle function module Rerun R5REQ program cycle function module Reserved Reload V.
BUEP19E Protocol 7-1 7 BUEP19E Protocol 7.1 Introduction The BÜP19E transfer protocol (BOSCH Übertragungs-Protokoll) can be loaded into the R500 and R500P computer interface modules. It transfers data by means of a point-to-point connection. As a result, data can be exchanged between two computer interface modules or one computer interface module and a central processing unit or an SK500 module. Data can also be exchanged between a computer interface module and a computer.
7-2 7.2 BUEP19E Protocol Protocol-specific Settings The S2 DIP switch for the BÜP19E protocol has the following function: Switch SS1 SS2 SS3 SS4 SS5 SS6 SS7 SS8 Setting ON OFF ON OFF - Explanation peripheral jobs have priority centralised jobs have priority no function no function no function peripheral jobs have priority centralised jobs have priority no function no function no function Channel 0 0 0 0 1 1 1 1 Fig.
BUEP19E Protocol 7.3.1.1 7-3 Command Type Parameter This parameter indicates the types of commands for the job. There are two types of commands: ‘E’(45H) Input into the RST ‘A’ (41H) Output from the RST The direction of the jobs always refers to the RST, i.e., an output job (41H --> ‘A’) transfers data from the RST to the PST and an input job (45H --> ‘E’) transfers data from the PST to the RST.
7-4 BUEP19E Protocol 7.3.2 RST / PST Command Code Parameter Parameter word Contents High byte RST command code 44H Data module PW5 Example LOW byte PST command code 44H Data module Fig. 7-4 BÜP19E — RST / PST Command code In this parameter the RST command code (hex code of the command) is indicated in the HIGH byte and the PST command code is indicated in the LOW byte. 7.3.3 RST Command Attribute Parameter word PW6 Example Contents RST command attribute 17H Data module 23 Fig.
BUEP19E Protocol 7-5 7.3.6 PST Command Attribute Parameter word PW9 Example Contents PST command attribute AH Data module 10 Fig. 7-8 BÜP19E — PST Command attribute The field index (for field commands) or the control code (for special commands) of the PST command is indicated in the PST command attribute. Refer also to RST command attribute. 7.3.7 PST Address — High Part Parameter word PW10 Example Contents PST address, High part F0H ZS400 Fig.
7-6 BUEP19E Protocol 7.3.9 Data Volume Parameter Parameter word PW12 Example Contents Volume of data (in data types) according to type of operand 28H Volume = 40 Fig. 7-11 BÜP19E — Data volume parameter The volume of data to be transferred, referring to the type of operand, is indicated in the parameter. If the ‘Mask’ type of operand is used, the volume of data should be set to 1. The double length (set mask and reset mask) of the type (e.g.
BUEP19E Protocol 7-7 CL500 controller acting as PST The Central Processing Unit Control command in the CL500 system uses two types of coordination markers: - Process coordination marker (PCM) - from ZS501: Field coordination marker (FCM) and The PCMs are specified as follows: 00 H System STOP status 01 H System RUN status 02 H I/O status 03 H I/O status or STOP 04 H EP 05 H EP or STOP 06 H OM1 07 H OM1 or STOP 0F H No process coordination The FCMs are specified in the special marker
7-8 7.4 BUEP19E Protocol Command Description for Central Processing Units The central processing units differentiate between field commands and special commands. 7.4.1 Field Commands 7.4.1.1 Data Field — 43H Command Command code Command attribute Address, High part Address, Low part Operand type 7.4.1.2 Data Module without Header — 44H Command Command code Command attribute Address, high part Address low part Type of operand 7.4.1.3 Data module without header 44H DM number 0 ...
BUEP19E Protocol 7.4.2 Special Commands 7.4.2.
7-10 7.5 BUEP19E Protocol Fault Messages The BÜP19E protocol generates fault information which is divided into three areas: • PLC response (Byte) • Fault class (Byte) • Error code (Byte) The fault information is filed in the R5CON check-back parameters in the following sequence: P3 parameter High byte Status LOW byte PLC response P4 parameter High byte Fault class LOW byte Error code 7.5.1 Job Status The current status of the job is specified in the Status by the function module.
BUEP19E Protocol 7-11 7.5.2 PLC Response The PLC response should provide the user with information on further procedures.
7-12 BUEP19E Protocol 7.5.4 Error Catalogue Fault information PLC Error class Error code Explanation response 00 00 00 Fault-free job 01 34 05 Protocol cannot be implemented due to an internal protocol fault (RST) - No connection - Faulty connection - Interface hardware not ready - The incoming message cannot be analysed 01 30 02 Memory access fault (RST) Faults occurred when RST memory area was accessed. Data incorrectly read or incompletely written 01 30 03 Wrong memory type (RST).
BUEP19E Protocol Fault information PLC Error class Error code Explanation response 03 32 02 Memory access fault (PST) Faults occurred when RST memory area was accessed: Data incorrectly read or incomplete. 03 32 03 Wrong memory type (PST) The type of access for the addressed PST memory is not permitted (e.g.
7-14 BUEP19E Protocol 1070 072 131-102 (96.
BUEP03E Protocol 8-1 8 BUEP03E Protocol 8.1 Introduction The BÜP03E transfer protocol (BOSCH Übertragungs-Protokoll) handles all communication tasks between the CL500 computer interface module and connected peripheral devices, such as code readers, measuring instruments, positioning controllers, intelligent control panels, printer, terminal, etc. The BÜP03E protocol is loaded onto the R500/R500P module and receives the jobs in the form of commands from the central processing unit.
8-2 8.3 BUEP03E Protocol Explanation of Terms UART Receive buffer: The R500 operating system reads all the characters into this 384-byte buffer via the serial interface. This receive buffer is located on the R500 module. BÜP03E Receive buffer: The BÜP03E reads the characters from the UART receive buffer and writes them to its own BÜP03E receive buffer, the size of which can be selected from 10 to 256 bytes. This receive buffer is located on the R500 module.
BUEP03E Protocol 8-3 Identifier: Three words which are used for determining the address in the DM, DF or DB. The words in detail: 1st word: Field type (44H = DM, 64H = DB, 43H = DF). 2nd word: Field index (DM = 0-255, DB = 0, DF = FFFFH). 3rd word: Field offset (DM = 0-510, DB = 0-510, DF = 0-24 kbyte). Caution: Only the even-numbered byte addresses are permitted. Control text: Text combined with format instructions. 1070 072 131-102 (96.
8-4 8.4 BUEP03E Protocol Transmission Format The non-displaying ASCII characters are used to control the protocols. These control characters, like the other data, are written to memory as hex code by the user. All the data is then output with the Transmit command via the serial interface. The data can be input into the PLC memory either via the PG editor or the PLC program commands. The PG editor only allows the ASCII and hex formats.
BUEP03E Protocol 8.5 8-5 Transmission Sequence 8.5.1 Receiving Characters Two different receive modes can be specified by the Receive Mode command. a) Unrestricted Receive: The user defines a PLC Receive buffer (max. 256 bytes) on the PLC side. When the Receive command activates communication via R5REQ, all characters are received and filed in the BÜP03E Receive buffer until - the monitoring time overflows - or the job is terminated - or the Receive-data length has been reached.
8-6 BUEP03E Protocol 8.5.2 Transmitting Characters There are two modes available: a) Unformatted output: The Transmit command transmits data from a PLC transmit buffer (DM, DF, DB) without conversion by the serial interface. Reformatting is not implemented, i.e., a 0FFH in the memory causes a 0FFH in the line. Using this procedure, the user can easily output self-formulated request and acknowledgement information.
BUEP03E Protocol 8.6 8-7 Receive Buffer 8.6.1 UART Receive Buffer The data received via the serial interface is first filed in the UART Receive buffer. This Receive buffer is designed as a ring buffer and contains a total of 384 characters. This buffer is managed by the R500 operating system. The characters are read into this buffer via the interface, independent of the BÜP03E protocol. The characters are read out character by character from the BÜP03E log and filed in the BÜP03E Receive buffer.
8-8 BUEP03E Protocol 8.6.2 BÜP03E Receive Buffer The Receive command continually copies data from the UART Receive buffer into the BÜP03E Receive buffer. The user can select the size of this BÜP03E Receive buffer by issuing the Receive command via a parameter, however the size must be within the range of 10 to 256 bytes. Otherwise, a fault message is returned and the BÜP03E Receive buffer is not applied.
BUEP03E Protocol 8-9 8.6.3 PLC Receive Buffer The PLC Receive buffer is the same as the BÜP03E Receive buffer. The received data is collected in this buffer and is provided to the user for interpretation. The Data Copy command writes all the data which is in the BÜP03E Receive buffer into the PLC Receive buffer in one cycle. 8.6.
8-10 8.7 BUEP03E Protocol BÜP03E Commands 8.7.1 Command Activation The BÜP03E protocol incorporates several commands which should be activated by the user for communication purposes. The commands are activated by the R5REQ function module. The first parameters (P0 - P2) of the R5REQ function module point to a memory (DM, DF, DB) in which the protocol-specific job parameter list has been filed (see description of R5REQ, Pages Fehler! Textmarke nicht definiert. ff).
BUEP03E Protocol 8-11 8.7.2 Operating Method The BÜP03E protocol provides the user with a number of commands. These commands then execute the jobs which are required for communication. The following commands have been defined: - Start - Receive - Transmit - Reset Receive Buffer - Data Copy - Formatted Output - Receive Mode - Terminate Job Each command is indicated by a job parameter list. All these commands are activated by the R5REQ. The Terminate Job command is provided by the R500 system.
8-12 8.7.2.1 BUEP03E Protocol Interlinking via BÜP03E START Command The associated job parameter lists are filed contiguously one after the other in the PLC memory (DM, DB, DF). Each job parameter list specifies a command (==> job). The sequence of the commands in the PLC memory specify the positions of the commands. Application-specific combinations of the command positions can be stipulated with the Start command.
BUEP03E Protocol 8-13 If a fault occurs (e.g. invalid parameters, system bus fault...), the command chain is terminated immediately and the fault message is returned with the interlinking depth. In order to establish a single communication with a peripheral, the interlinking of the following commands must be indicated with the Start command.
8-14 BUEP03E Protocol 8.7.3 Command Types This section provides a detailed explanation of the BÜP03E commands and their parameters and lists possible application examples. These examples should be regarded as an introduction to the BÜP03E Command Language.. When using the commands, the user should NOT impose unnecessarily high traffic loads on the system bus. High loads can be prevented by skilful use of the commands in program loops and function modules.
BUEP03E Protocol 8.7.3.1 8-15 START Command Description: This command defines the execution sequence of a command chain in the PLC memory (DM, DB, DF) and starts this command chain.
8-16 8.7.3.2 BUEP03E Protocol RECEIVE Command Description: This command enables data to be received without restriction via the interface and written to the indicated buffer. Parameter word PW4 Contents Command identifier - RX (Receive) Parameter word PW5 Contents Monitoring time in 10 ms matrix Maximum selectable time (10 ms * 65535) is approximately 10 min. When 0 (zero) is specified, the time monitor is switched OFF. The monitoring time indicates the maximum time between two characters.
BUEP03E Protocol 8.7.3.3 8-17 TRANSMIT Command Description: This command enables data to be transmitted from the memory to the peripherals via the interface; the data is output without being converted. Parameter word PW4 PW5 PW6 PW7 PW8 Contents Command identifier - TX (Transmit) Field type Identifier Field index on the Field offset command chain Length of the transmit data in bytes Fig. 8-10 BÜP03E — Transmit command parameters Max. possible length is 512 bytes ( = one DM size).
8-18 8.7.3.4 BUEP03E Protocol RESET RECEIVE BUFFER Command Description: This command enables the internal RD and WR pointers of the BÜP03E and UART Receive buffer to be reset. Syntax: As on Page 8-15 in the Start Syntax section. Parameter word PW4 PW5 Contents Command identifier - RS (Reset) 0: Reset UART Receive buffer 1: Reset UART and BÜP03E Receive buffer Fig. 8-11 BÜP03E — Reset Receive Buffer command parameters PW6 - PW16 are reserved. 1070 072 131-102 (96.
BUEP03E Protocol 8.7.3.5 8-19 RECEIVE MODE Command Description: The following modes can be selected with this command: - Start character - End character - Number of BCC - Termination character - Marker number for interlinking depth The selected Receive modes are valid until they are redefined. The Receive modes can be modified within a command chain if the Receive process (Receive command) is inactive.
8-20 BUEP03E Protocol Job parameter list: Parameter word PW5 Contents No. of start characters No. of end characters End characters: 0 : No end condition 1 : One end character 2 : Two end characters Start characters: 0 : No start condition 1 : One start character 2 : Two start characters The start characters may occur in the data flow. If only one end character has been defined, it must NOT occur in the data flow; otherwise the Receive process is terminated.
BUEP03E Protocol Parameter word 8-21 Contents HIGH byte Number of BCC PW8 LOW byte Termination No. of type terminations No.
8-22 8.7.3.6 BUEP03E Protocol DATA COPY Command Description: This command enables the data which has been read into the BÜP03E Receive buffer to be copied from the PLC program into the PLC Receive buffer during the Receive process. If the BÜP03E Receive buffer is not emptied quickly enough with this command, a data loss may occur which is signalled back. If no new characters have arrived after the last "Data copy", the user is informed by a fault message.
BUEP03E Protocol 8-23 8.7.3.7 FORMATTED OUTPUT Command Description: The Formatted Output command enables text, variables or text combined with variables to be output to the printer. This command interprets the control text and associated variables indicated by the parameters (PW5 - PW7). The format instructions have been integrated in the control text and begin with a % character. The characters which do not begin with the % character appear unchanged in the output.
8-24 BUEP03E Protocol A character variable is in the LOW byte of the word. A floating-point number is positioned in memory according to the LowHigh word principle, and is represented with single accuracy. All numbers are displayed from the % character, right or left-justified (see above). A hex number can be displayed with (%#x) or without (%x) leading zeros.
BUEP03E Protocol 8-25 Floating-point numbers The floating-point numbers are represented according to two methods. Internal representation specifies how floating-point numbers have been filed in memory. External representation specifies how floating-point numbers are printed or displayed. These methods of representation are explained below. Examples of external representation: Constants 23.45e6 2.1e-5 -1.23 Value 6 23.45 * 10 -5 2.1 * 10 -1.
8-26 BUEP03E Protocol 8.7.3.8 Terminating Jobs The user has the options, as described below, to naturally conclude or terminate a job. Terminate via R5REQ function module The parameter word (PW3) in the job parameter list has the following structure.
BUEP03E Protocol 8-27 Normal conclusion via start and end characters The start and end characters are specified with the Receive Mode command. If the end character(s) occur in the data flow, the Receive process is concluded normally and is possibly stepped-on in the command chain. Normal conclusion via Receive-data length The length of the data to be received in bytes is specified with the Receive command.
8-28 BUEP03E Protocol 8.7.3.9 Summary of BÜP03E Commands Param. word PW4 PW5 PW6 PW7 Receive RX Monitoring time 0 - 65535 in 10 ms Raster unit Size of the PLC receive buffer 10 bytes - 256 bytes Receive-data length in bytes 1 - 255 0: no length condition Data Copy DC PLC Receive buffer id. Field types 44H=DM, 43H=DF, 64H=DB Field index DM = 0-255 DB = 0, DF = FFFFH Field offset DM = 0-510, DB=0-510 DF=0-24 kbytes Reset Receive Buffer RS Reset Receive buffer 0 = UART 1 = UART + BÜP03E Fig.
BUEP03E Protocol Param. word PW4 PW5 PW6 PW7 PW8 PW9 PW10 Start ST Command chain id. Field types 44H=DM, 43H=DF, 64H=DB Field index DM = 0-255 DB = 0, DF = FFFFH Field offset DM = 0-510, DB=0-510 DF=0-24 kbytes Maximum utilised interlinked parameter list no. 1 - 16 LOW byte: 1st command HIGH byte: 2nd command LOW byte: 3rd command HIGH byte: 4th command ‘’ Fig. 8-15 BÜP03E — Summary of Commands, Part 3 1070 072 131-102 (96.
8-30 BUEP03E Protocol 8.7.4 Examples of BÜP03E Commands The examples illustrate how the interlinked commands implement effective applications. In theory, any command can be interlinked with any other command. However, commands should be interlinked effectively. For example, the Data Copy command can be completely integrated into the command chain following the Receive command. However, the command is not activated during the Receive process.
BUEP03E Protocol 8-31 Example 3: Data should always be received conditionally and then retrieved; the following conditions are defined with the Receive Mode command.
8-32 BUEP03E Protocol Example 4: A simple text combined with variables is sent. DW0 - DW4 = Reserved for R5REQ DW6 = 'FO' Command identifier DW8 = K44H Identifier DW10 = 11 DW12 =0 DW14 bytes. = 50 on control text with variables Estimated length of control text + variables in The control text and variables are in the DM11, commencing from DW0, e.g.
BUEP03E Protocol 8.8 8-33 Checkback Signals and Fault Messages The jobs can be started or terminated with the R5REQ function module. The R5CON function module monitors the issued jobs. If the job has been terminated or terminated, BÜP03E enters the information into the job table on the ZS module via the processed jobs. R5CON reads this information which the user receives in his output parameters (P3, P4).
8-34 BUEP03E Protocol The fault information is written to the R5CON checkback parameters in the following sequence: P3 parameter HIGH byte Status LOW byte PLC response P4 parameter HIGH byte Error class LOW byte Error code 8.8.1 Job Status The current status of the job is specified in the Status by the function module: Status 00H 01H 02H 03H Explanation Job ended fault-free Job written to queue Job processing Job ended with fault(s) Fig. 8-16 BÜP03E — Job status 8.8.
BUEP03E Protocol 8-35 8.8.3 Error Class The error class refers to the generation point of the fault information. The following conventions apply: Error class 00H 30H 31H 40H FFH Explanation Fault-free System bus Operating system BÜP03E fault messages Fault message of the function modules Fig. 8-18 BÜP03E — Error class 8.8.
8-36 BUEP03E Protocol 1070 072 131-102 (96.
BUEP64 Protocol 9-1 9 BUEP64 Protocol 9.1 Introduction A frequent application occurring in automated systems is the data exchange between complex or spatially distributed control systems. This section discusses the BÜP64 protocol (Siemens 3964 / 3964R protocol) which can be loaded into the R500 and R500P computer modules.
9-2 9.2 BUEP64 Protocol Protocol-specific DIP Switch Settings The S2 DIP switch can be defined for the BÜP64 protocol as follows: Switch SS1 SS2 SS3 SS4 SS5 SS6 SS7 SS8 Setting ON OFF ON OFF ON OFF OFF ON OFF ON OFF ON OFF OFF Explanation Peripheral jobs have priority Centralised jobs have priority Protocol 3964 Protocol 3964R Protocol end identifier incl. DLE ETB Protocol end id.
BUEP64 Protocol 9.3 9-3 BÜP64 Transfer Completion Sequence Handling Information is usually transferred according to the following sequence: - The connection is established. Data blocks, max. 128 data bytes, are transferred. Each data block is acknowledged by a subsequent transfer response message. The individual blocks are repeated if transfer faults occur. After transfer of the final data block, the connection enters an idle state.
9-4 BUEP64 Protocol The 3964R protocol is best divided into two levels. Interpreter The Interpreter manages the data exchange, and processes and monitors the centralised or decentralised jobs. It establishes a connection with the PLC, processes the data and ensures that data is transferred in blocks. The Interpreter recognises faults and signals a defective or fault-free data exchange to the PLC. The Interpreter calls up the Transfer Routine with all data required for its functioning.
BUEP64 Protocol 9-5 NAK = Negative Acknowledge, control character, negative response, e.g. if a transfer fault occurs. BWT = Block Wait Time, max. 4 seconds, max. time until a defective block is repeated. High / Low priority = Specifies which device has priority control when an access procedure is occurring. Checksum = Secures the data and is transmitted at the end of each block. The block check character BCC is generated from the parity (*) of the information bits of all data bytes (incl.
9-6 9.4 BUEP64 Protocol SEND Connection Sequence The requesting station (RST) transmits the STX control character to establish the connection. If the peripheral station (PST) responds before the acknowledgement delay time elapses with the DLE character, the RST switches over to Transmit Mode. If the PST responds with the NAK character, with any other character, or if the acknowledgement delay time (ADT) elapses without any response, the connection setup fails.
BUEP64 Protocol 9-7 Transmission of data - Data is usually transmitted in the following sequence: Transmission header + Data Transfer response message more than 128 data bytes Transfer completion sequence Completion sequence response up to max.
9-8 BUEP64 Protocol 9.4.1 Detailed SEND Sequence 9.4.1.1 Message Header and Data STX (start character) DLE (positive acknowledgement) Acknowledgement delay time ADT 3964 -> 550 ms 3964R -> 2000 ms Message header 1st byte 00H 2nd byte 00H 3rd byte Job 4th byte Type 5th byte Destination DM 6th byte Destination addr. 7th byte Number 8th byte Number 9th byte Coordination 10th byte marker Data 11th byte 12th byte 1st data byte 2nd data byte nth byte (max.
BUEP64 Protocol 9.4.1.2 9-9 Response Message A response message is expected after a command message has been issued. Depending on the selected baud rate, the following times must be observed: The monitoring time is dependent on the baud rate (bps). 19200 - 1200 = 5 sec. 600 = 7 sec. 300 = 10 sec. 150 = 15 sec. 110 = 20 sec.
9-10 9.5 BUEP64 Protocol Requesting Data (FETCH) Data is requested in the following sequence: Request message Response message and data if more than 128 data bytes Transfer completion request Transfer response message and data up to max. 512 data bytes Source types Data modules Message header Byte 3,4 Byte 3: 45H -> ‘E’ Byte 4: 44H -> ‘DM’ Destination types Data modules NOTE – Only data modules are transferred ! 1070 072 131-102 (96.
BUEP64 Protocol 9.5.1 Detailed REQUEST Sequence 9.5.1.1 Request Message STX (start character) DLE (positive acknowledgement) Acknowledgement delay time ADT 3964 -> 550 ms 3964R -> 2000 ms Message header 1st byte 00H 2nd byte 00H 3rd byte Job 4th byte Type 5th byte Source DM 6th byte Source DW. 7th byte Number 8th byte Number 9th byte Coordination 10th byte marker DLE (end identifier) ETX (end identifier) BCC (checksum) DLE (positive acknowledgement) Acknowledgement delay time ADT 1070 072 131-102 (96.
9-12 9.5.1.2 BUEP64 Protocol Response Message A response message is expected after a command message has been issued. Depending on the selected baud rate, the following times must be observed: The monitoring time is dependent on the baud rate (bps). 19200 - 1200 = 5 sec. 600 = 7 sec. 300 = 10 sec. 150 = 15 sec. 110 = 20 sec.
BUEP64 Protocol 9.6 9-13 RECEIVE Connection Sequence If there is no centralised job, the Transfer Routine remains in an idle state. If an STX is now received from the peripheral, a response can be implemented with DLE, i.e., ready-to-receive state is displayed if the Receive buffer is empty. (All other characters have an NAK as a consequence and the Transfer Routine remains in an idle state). If the buffer is not ready, another check is implemented after approx.
9-14 9.7 BUEP64 Protocol Initialisation Conflict If a device responds to the start character (STX) by issuing the start character (STX) itself, an initialisation conflict occurs. The device with the low priority resets its transmit job and signals its ready-to-receive state (DLE). The low-priority device executes its transmit job following the receive and connection release procedures.
BUEP64 Protocol 9.9 9-15 Transfer Message Formats 9.9.1 Transmission Header and Data The message header consists of 10 bytes.
9-16 BUEP64 Protocol 9.9.2 Response Message Structure Byte ────────────────────────────────────────────────────── 1 00 Identifier for response message 2 00 3 00 ────────────────────────────────────────────────────── 4 00 Fault number (0 = no fault) ────────────────────────────────────────────────────── 5 DLE end identifier, 6 ETX 7 BCC ────────────────────────────────────────────────────── 9.9.
BUEP64 Protocol 9.10 9-17 Checkback Signals The BÜP64 protocol generates fault information which is divided into three areas: PLC response (byte) Error class (byte) Error code (byte) The fault information is written to the R5CON checkback parameters in the following sequence: P3 parameter HIGH byte Status LOW byte PLC response P4 parameter HIGH byte Error class LOW byte Error code 9.10.
9-18 BUEP64 Protocol 9.10.2 PLC Response The PLC response is intended to provide the user with advice and help on the faults within the fault information.
BUEP64 Protocol 9-19 9.10.3 Error Class The error class refers to the generation point of the fault information. The following conventions apply: Error class 00H 30H 31H 32H 33H 34H FFH Explanation Fault-free System bus Operating system PST job execution RST job execution Protocol sequence Fault message of the function modules Fig. 9-4 BÜP64 — Error class 1070 072 131-102 (96.
9-20 BUEP64 Protocol 9.10.
BUEP64 Protocol PLC response 03 03 03 03 03 03 03 03 03 03 03 03 03 04 04 09 09 20 Fault information Error class Error code Explanation 33 33 33 33 33 33 33 33 33 33 33 33 33 34 34 34 96 B0 B1 D3 D4 D6 D7 D8 ED EC F1 F2 F3 F7 F9 FE 34 FF Length Fig. 9-6 BÜP64 — Fault messages, Part 2 1070 072 131-102 (96.
9-22 9.11 BUEP64 Protocol Job Parameters A job is specified by 16 parameters. Each parameter has a width of 2 bytes. Data ranges of 16 data words each are available for the job parameters; a maximum of 16 jobs can be parameterised for each call-up of the R5REQ. The parameter words PW1...PW3 are protocol-independent and jobspecific parameters; while the parameter words PW4...PW16 contain protocol-specific information.
BUEP64 Protocol 9-23 9.11.1 Protocol-specific Parameters — PW4 through PW16 Data traffic is parameterised by "3964R" for RST and PST via the protocol-specific parameters. The individual parameters are explained below. 9.11.1.1 Command / Operand Type — PW4 The protocol provides the SEND and FETCH commands (PW4 HIGH byte): Parameter word Contents High byte Command type 41H Send PW4 Example LOW byte Operand type 01H Word Fig.
9-24 BUEP64 Protocol 9.11.1.2 RST / PST Command Type — PW5 Parameter word PW5 Example Contents High byte RST command code 44H Data module LOW byte PST command code 44H Data module Fig.
BUEP64 Protocol 9-25 9.11.1.5 RST Address: DM Word Number — PW8 Parameter word PW8 Example Contents RST address 0H Word 0 Fig. 9-12 BÜP64 — RST Address: DM word number Like the parameterisation of the PST DM word number (P10), the RST DM word number is specified in one byte (0,1,2...255) in order not to confuse the user with possibly varying parameter specifications; the word number is converted into the CL500 format (byte address 0, 2, 4 ,6 ....510) within the protocol; 9.11.1.
9-26 BUEP64 Protocol 9.11.1.8 Data Volume — PW12 The PW12 parameter word indicates the volume of data which is to be transferred; the specification refers to the operand type (word) specified in PW4 (LOW byte); a maximum of 256 words can be transferred; Parameter word PW12 Example Contents Volume of data 20H 32 words Fig. 9-15 BÜP64 — Data volume 1070 072 131-102 (96.
BUEP64 Protocol 9-27 9.11.1.9 Coordination Markers — PW13 The function of the coordination markers is to coordinate the execution of a command on the PST. The command is only executed when the corresponding coordination event is "true"; the coordination sequence point or the field coordination marker "1" must therefore be accessed for the CL500 control type; as far as the other specified control types are concerned, the addressed coordination marker must be "1" for execution of a coordinated command.
9-28 BUEP64 Protocol The respondent ZS in the CL500 system is addressed by the ZS (1H-FH) module number which is indicated in the coordination marker. This addressing procedure is based on the Siemens 3964R/3964 Data Transfer Controller specification. The process and field coordination markers, as well as the module number, are linked to the "3964R" coordination marker format according to the following schematic: 15 14 13 8 7 FCM 4 3 Module no.
BUEP64 Protocol 9-29 The following coordination marker bytes for the Siemens controller are proposed for the coordination of central processing units: Coord. marker 00 x 0 .. 7 . . 1F x 0 .. 7 40 x 0 . 5F x 0 80 x 0 .. 7 FF x F Explanation Process and field coordination: - 00 x 0 --> SM16.0 and PCM 0 - 0A x 4 --> SM17.2 and PCM 4 - 1F x 7 --> SM19.7 and PCM 7 Only field coordination: - 40 x 0 --> Special marker SM16.0 - 5F x 0 --> Special marker SM19.7 Only process coordination 0 ..
9-30 BUEP64 Protocol CL300 controller acting as PST The CL300 controller permits a central processing unit to have maximum configuration; it is therefore not necessary to specify the CPU number within the coordination marker. When the Siemens format is observed, the coordination marker has the following appearance: 15 7 Word address 4 3 0 0 Bit number Where: bit number - 0...15 word address - 0...254 word address 0, 2, 4 ...
BUEP64 Protocol 9.12 9-31 Job Parameterisation Examples 9.12.1 SEND Job (CL500 -> CL300) Nine (9) words, beginning with the byte address 26H (word number 13H), are written, without coordination, from the DM17 data module in the ZS500 with block address 10H to the DM35 data module in the ZE301 from byte address 64H (word number 32H). The transfer is processed by Channel 1 of the R500 with the number 2 (CXN2, see R5INIT parameterisation); the job receives job number 4.
9-32 BUEP64 Protocol 9.12.2 FETCH Job (CL500 <- CL300) Thirty-three (33) words, beginning with the byte address 1AH (word number DH, see Chap. 9.2), are read from the DM12 data module in the ZE301 and written, without coordination, to the DM27 data module in the ZS3 with block address 18H from byte address 50H (word number 28H, see Chap. 9.2). The transfer is processed by Channel 0 of the R500 with the number 3 (CXN3 see R5INIT parameterisation). The job receives job number 7.
BUEP64 Protocol 9-33 9.12.3 SEND Job (CL500 -> CL500) Four (4) words, beginning with the byte address 12H (word number 9H), are written, without coordination, from the DM5 data module in the ZS500 with block address 10H to the DM9 data module in the ZS500 with module number 2 from byte address 24H (word number 12H). The transfer is processed by Channel 1 of the R500 with the number 2 (CXN2 see R5INIT parameterisation). The job receives job number 4. The job is parameterised as follows: Param.
9-34 BUEP64 Protocol 1070 072 131-102 (96.
Index 10 Index of Figures Fig. 2-1 CL400 — Slot assignment, GG2 Basic unit ...........................................................................2-4 Fig. 2-2 CL400 — Slot assignment, GG2/K Basic unit........................................................................2-4 Fig. 2-3 CL500 — Slot assignment, GG2 Basic unit ...........................................................................2-4 Fig. 2-4 CL500 — Slot assignment, GG2/K Basic unit...................................................
10-2 Index Fig. 9-3 BÜP64 — PLC response .....................................................................................................9-18 Fig. 9-4 BÜP64 — Error class ...........................................................................................................9-19 Fig. 9-5 BÜP64 — Fault messages, Part 1 .......................................................................................9-20 Fig. 9-6 BÜP64 — Fault messages, Part 2 ..................................................
Index 11 11-1 Index —%— % character, in control text 8-23 —0— 0 (zero) in control text 8-23 —1— 14 x 0.
11-2 Index – REQUEST sequence 9-11 – response message 9-12 – response message structure 9-16 – SEND connection sequence 9-6 – transfer completion sequence handling 9-3 – transfer message formats 9-15 – trasnmission header and data 9-15 BÜP64, Siemens 3964R transmission protocol 2-5 BWT — Block Wait Time 9-5 —C— CDT — Character Delay Time 9-4 Central Processing Unit Control command 7-7, 927 Channel-independent displays 2-11 – code H (hardware) 2-11 P flashes (loading flash memory) 2-11 Channel-specific dis
Index —G— General-purpose control characters 8-4 —H— Hex dump, of data in controller 8-4 Hex format, PG editor 8-4 Hex word 8-4 High / Low priority, of devices during access procedure 9-5 HIGH byte – R5REQ output parameter, PLC response 5-3 HIGH byte, PLC response in result word 5-6 —I— Input into the RST 7-3 Input job 7-3 Input parameter – R5CON module 8-33 computer interface number CXN 6-2 data type 6-2 job number 6-2 – R5REQ module byte offset 5-2 data type 5-2 data type attribute 5-2 job bit array JBA
11-4 Index – connectivity with other BOSCH controllers and extraneous communicating devices 2-1 – DIP switch settings 2-5 – function modules 2-1 – operating software re-initialisation by pressing Reset button 2-3 – power supply 2-1 – precautions against electrostatic discharge (ESD) 2-5 – setting block address 2-6 – specifications 2-12 R500 firmware 3-1 R500 operating system 8-19 R500 Reset procedure 8-19 R5CON confirmation module – functional description 6-1 – I/O parameters 6-2 input parameters 6-2 outp
Index Value, floating-point numbers 8-25 Version ID 2-2 Version modification, identified 2-3 —W— Wildcard character 6-2 Word boundaries 8-4 WR pointer, see Ring buffer 8-2 —X— XO (Exclusive OR) 9-5 1070 072 131-102 (96.
11-6 Index 1070 072 131-102 (96.
1070 072 131-102 (96.
