SINUMERIK 840/840C

SINUMERIK 880/880 GA2

PLC 135 WB/WB2 Function Blocks
Package 7: Code Carriers, Tool Data with
Address Encoding, Frame Description
Planning Guide 11.92 Edition

Manufacturer Documentation
SINUMERIK 840/840C
SINUMERIK 880/880 GA2
PLC 135 WB/WB2 Function Blocks
Package 7: Code Carriers, Tool Data
with Address Encoding, Frame
Description
Planning Guide

Manufacturer Documentation

Valid for:

Control Software version

SINUMERIK 840 from 2
SINUMERIK 840C 1
SINUMERIK 880 from 4
SINUMERIK 880 GA2 1

November 1992 Edition

SINUMERIK® documentation

Printing history

Brief details of this edition and previous editions are listed below.
The status of each edition is shown by the code in the "Remarks" column.
Status code in ”Remarks” column:

A . . . New documentation
B . . . Unrevised reprint with new Order No.
C . . . Revised edition with new status.
If factual changes have been made on a page since the last edition, this is indicated
by a new edition coding in the header on that page.

Edition Order No. Remarks

12.91 6ZB5 410-0EA02-0AA1 A
11.92 6FC5 197-0AB40-0BP0 C

Other functions not described in this documentation might be

executable in the control. This does not, however, represent an
obligation to supply such functions with a new control or when
servicing.

This publication was produced on the Siemens 5800 Office

System.
Subject to change without prior notice.

The reproduction, transmission or use of this document or its

contents is not permitted without express written authority.
Offenders will be liable for damages. All rights, including rights
created by patent grant or registration of a utility model or
design, are reserved.

© Siemens AG 1991 All Rights Reserved

SINUMERIK 840/840C
SINUMERIK 880/880 GA2
PLC 135 WB/WB2 Function Blocks
Package 7: Code Carriers
Part 1: Tool Data with Address
Encoding
Introduction 1

Address Parameter List 2

FX Data Sheets 3

Block Data for FB Package 7 4

Application 5

Configuring Lists 6
Contents

Page

1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–1

1.1 General remarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–1

1.1.1 List of abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–2
1.1.2 Reference literature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–2
1.2 Tools with data memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–3
1.3 Loading via code carrier FX "BEL-CDTR" . . . . . . . . . . . . . . . . . . . . . . 1–5
1.4 Unloading via code carrier FX "ENT-CDTR" . . . . . . . . . . . . . . . . . . . . 1–10
1.5 Prerequisites and stipulations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–14
1.6 General conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–15
1.7 Interface to the computer link software . . . . . . . . . . . . . . . . . . . . . . . . 1–16
1.8 Machine data words . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–18
1.9 Machine data bits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–20
1.10 Configuring the code carrier requests . . . . . . . . . . . . . . . . . . . . . . . . . 1–21

2 Address Parameter List ................................. 2–1

2.1 General remarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–1

2.2 Structure of the address parameter list . . . . . . . . . . . . . . . . . . . . . . . . 2–1
2.3 Stipulations regarding the address parameter list . . . . . . . . . . . . . . . . . 2–6

3 FX Data Sheets ....................................... 3–1

3.1 Load via code carrier (FX "BEL-CDTR") . . . . . . . . . . . . . . . . . . . . . . . 3–1

3.2 Unloading via code carrier (FX "ENT-CDTR") . . . . . . . . . . . . . . . . . . . 3–10
3.3 Subroutine (FX ”UP-CDTR”) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–16

4 Block Data for FB Package 7 ............................. 4-1

5 Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–1

5.1 General remarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–1

5.2 Machine data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–1
5.2.1 FB machine data for package 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–1
5.2.2 General machine data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–3
5.3 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–4

6 Configuring Lists ...................................... 6–1

11.92 1 Introduction
1.1 General remarks

1 Introduction

1.1 General remarks

The "Code Carriers, Transfer Tool Data with Address Encoding" function block package forms
the basis when using tools equipped with data memory.

The most important features of the "Code Carriers, Transfer Tool Data with Address
Encoding" function block package are:
• Separate link-up facility for code carrier systems via user interfaces.
• Initializable user interface
• Connection of up to 4 read/write stations via serial interfaces
• The encoding station must observe the conventions presented in Part 2 of this manual.
• Use of code carrier chips of any size
One cutting edge is transferred per request; however, the number of useful data bytes per
request/response is restricted to 244*.
• The tool data is defined via the address parameter list and referenced via addresses on
the code carrier chip (address encoding), thus ensuring a flexible record structure on the
chip.
• The standard package handles the interchange of all tool data required for SINUMERIK
840/880 tool management. It can also handle data interchange with the encoding station
for user requests (i.e. requests to write user data to or read user data from the chip), the
user formulating the request and evaluating the requested data.
• The conventions presented in Sections 1.5, 1.6 and 2.3 must be observed!

Note:
The number of NC P memories (P0 to P15 or P0 to P31) supported by package 7 depends on
the SINUMERIK 840/880 tool management (package 1).

_______
* Some code carrier systems are limited to 224 bytes

© Siemens AG 1991 All Rights Reserved 6FC5 197-0AB40-0BP0 1–1

SINUMERIK 840/880 (PJ)
1 Introduction 12.91
1.1.1 List of abbreviations

1.1.1 List of abbreviations

CL Computer link
COM Communications module
(in SINUMERIK 840/840C systems, the COM area is part of the
NC area)
CP Interface module (communications processor)
CT Code carrier
DB Data block
DPR Dual-port RAM
DX DX data block
FB Function block
FX FX function block
I/O buffer Input/output buffer
MPR Multi-port RAM
PLC Programmable logic controller
UI User interface
UI/I User interface/input
UI/O User interface/output

1.1.2 Reference literature

/1/ SINUMERIK 840/840C/880/880 GA2

Package 4 and 5: "Computer Link: Configuring"
/2/ SINUMERIK 840/840C/880/880 GA2
Message Frame Descriptions ”Computer link”
/3/ SINUMERIK 840/840C/880/880 GA2
Package 1 and 2: "Tool Management"

1–2 © Siemens AG 1991 All Rights Reserved 6FC5 197-0AB40-0BP0

SINUMERIK 840/880 (PJ)
12.91 1 Introduction
1.2 Tools with data memory

1.2 Tools with data memory

The figure below shows how to interface a code carrier system to the SINUMERIK 880.
Several read/write heads can be addressed over the code carrier system’s evaluator
(read/write station). The evaluator and the PLC interchange data over the active CP315/373
RS 232 C interface.
When tools with data memory are used, all tool data is read out from the data medium when
the magazine is loaded and transferred to the control over the serial interface. The reverse
takes place when the magazine is unloading, thus enabling archiving of remaining tool life and
other data.

Code COM NC
carrier 20mA
system loop current MPR
RS 232 C interface Active
. Evaluator CP
. 3964R/LSV2
RS 232 C
line procedure
2
PLC1

Digital input

n
Hardware signal for load/unload

Code carrier Read/write head 1 Read/write head n

n = 1-8

Tool

Interfacing a code carrier system

© Siemens AG 1991 All Rights Reserved 6FC5 197-0AB40-0BP0 1–3

SINUMERIK 840/880 (PJ)
1 Introduction 12.91
1.2 Tools with data memory

The following figure provides a rough overview of how data is forwarded from the code carrier
system’s evaluator to the PLC and vice versa.

E.g. host computer E.g. 2nd read/write station

Read/write
Max. 8
station
Read/
Bus interface Active write head
COM module RS 232 C
CP1 CP2
DPR DPR

Hardware signal for

load/unload
COM-TASK

MPR O I
.....
I O

PLC NC
PLC op. system

User interface
Input Output

0..................31 0.................31
UI/I (DB 101) UI/O (DB 102)

DB 128 DB 129

UI UI
Useful data DB useful data DB
input buffer output buffer

DB 127
Status
Standard FBs for DB
loading/unloading via code

DB 126
DB 38 Format
list
NST:RK
aaaaaaaaaaaaaaaaaaaaaa
aaaaaaaaaaaaaaaaaaaaaa
aaaaaaaaaaaaaaaaaaaaaa
aaaaaaaaaaaaaaaaaaaaaa
aaaaaaaaaaaaaaaaaaaaaa
aaaaaaaaaaaaaaaaaaaaaa

n TO
ME-
MORY
Computer Tool
link software management

Digital I/O

n=1-8

Block diagram of the link between PLC and code carrier system

1–4 © Siemens AG 1991 All Rights Reserved 6FC5 197-0AB40-0BP0

SINUMERIK 840/880 (PJ)
11.92 1 Introduction
1.2 Tools with data memory

As can be seen from Figure ”Link between PLC and code carrier system”, the PLC is linked
to a code carrier system evaluator (read/write station) over one of 32 user interfaces (please
refer to the publication entitled "Package 4: Computer Link" for detailed information on the
user interface).
The user must reserve a separate user interface for each read/write station.
The user interface(s) for the read/write station(s) must be specified in the machine data and
configured in DB99 (assignment list) (refer to the section on configurable requests in the
publication entitled "Package 4: Computer Link" for details).

1.3 Loading via code carrier FX "BEL-CDTR"

When a code carrier system is used, FX "BEL-CDTR" organizes the loading procedure.

Explanation of program structure for loading with code carrier:

Case 1

Before initiating the load procedure, the user must decide:

• whether he wants to load only tool data required for SINUMERIK 880 tool management
(FX inputs "B-WZ"=1 and "B-AW"=0)
• whether he wants to load user data before loading the tool management data (FX inputs
"B-ZW"=1 and "B-AW"=1).
• whether he wants wants to load only user data (FX inputs "B-WZ"=0 and "B-AW"=1).

Tool management data:

Using the specifications in the address parameter list, the standard package generates the
"Chip Read" request for the tool management data (one request per cutting edge) and enters
the requested data in the PLC’s magazine table and the NC’s TO memory.

User data:
The user generates the request in a data block whose number is specified in the machine
data. The standard package then requests this data and makes it available in its DB 128 input
buffer (also see Section 3.1).
The load dialog is started via a binary signal. Each loading point has its own read-write head,
and each of the up to 8 read-write heads has its own binary load signal. The signals are
evaluated in the user program and the number of the read-write head (1 to 8) forwarded to
function block FX "BEL-CDTR", together with enable bit "B-WZ" and/or "B-AW".
Since several read/write stations may be connected, the user must decide which of these is to
be used for loading and forward its number (1 to 4) to the "BEL-CDTR" function block. "BEL-
CDTR" uses this number to ascertain the user interface assigned to the encoding station
(refer to Section 1.8, Configuring via machine data).

© Siemens AG 1991 All Rights Reserved 6FC5 197-0AB40-0BP0 1–5

SINUMERIK 840/880 (PJ)
1 Introduction 12.91
1.3 Loading via code carrier FX "BEL-CDTR"

Case 2
The tool to be loaded is at the loading point with the read/write station. The relevant read head
(which is selected via a binary signal) reads out the data over the serial interface allocated to
the corresponding user interface.

Case 3

A) Reading user data

The user generates the "Read" request as per the instructions in "Package 7: Code Car-
rier Requests" and supplies function block FX "BEL-CDTR" with the number of the useful
data DB (source, load) via the machine data.
FX output "ANWB" is set to "1" to inform the user that the requested data has been
received ("ANWB" remains at "1" for one cycle) and that FX "BEL-CDTR" has entered it
in input buffer DB 128. All further evaluation or post-processing of this data is the user’s
responsibility (also refer to Section 3.1).
If the requested data cannot be evaluated within one cycle, the user must copy it from
input buffer DB 128 (beginning data word DW 0) to another data block (i.e. save the data)
to prevent it from being overwritten (e.g. by subsequent tool data) before it can be
evaluated.

1–6 © Siemens AG 1991 All Rights Reserved 6FC5 197-0AB40-0BP0

SINUMERIK 840/880 (PJ)
12.91 1 Introduction
1.3 Loading via code carrier FX ”BEL-CDTR”

COM PLC PLC NC

Computer
User link
software

DB 128
DB 38 DB 126
UI
input Interface
Format
buffer to comp. list
link
software

DB 101/102
FB 145
User
interface Loading via
x code carrier
(x=0 to 31) DB 127
Status
DB 129 DB
UI
output
buffer

Interface
to 880
tool man.

DB's Tool
Standard tool manage- me-
ment FB`s
mory
Current
maga-
zine
contents

UI= User interface

Program structure for LOADING via code carrier

B) Reading the tool data for the first cutting edge

The tool size is computed from the receive data for the first cutting edge. The tool size (FX
output "WZGR") and any status info (8 bits/FX output "ZK-B"; only when defined in the
address parameter list) are forwarded to the user together with an enable bit for a vacant
location search (FX output bit"LP-S"). Function block FX "BEL-CDTR" then waits for an
acknowledgement.
The user can now modify data in the dynamic buffer (DB number in DB 127/DW 47),
e.g. set/reset status bits (refer to the description of FB139 in Package 1 for details on the
structure of the dynamic interface buffers for 880 tool management). Based on the
specified tool size, the user can search for a suitable empty location.

© Siemens AG 1991 All Rights Reserved 6FC5 197-0AB40-0BP0 1–7

SINUMERIK 840/880 (PJ)
1 Introduction 12.91
1.3 Loading via code carrier FX ”BEL-CDTR”

The user must inform FX "BEL-CDTR" as to whether the search was successful (FX in-
puts "F-LP"=0 and "LADE"=1) or not (FX input "F-LP"=1; "LADE" is irrelevant).
A negative acknowledgement ("F-LP"=1) aborts the load procedure and reenables the
user interface. No tool data is entered in tool memory or in the magazine table.
When the acknowledgement is positive, the magazine location into which the tool is to
be loaded must be specified in FX input parameter "PLNR". The tool data for the first
cutting edge is entered at this location in the magazine table and the relevant data in the
NC’s tool offset memory.

Special-purpose tools (type 19, 29, 39)

The tool type for the first cutting edge of a special-purpose tool is 19, 29 or 39 (definition).
Special-purpose tools are tools for which the cutting edge-specific data (such as geometry,
wear, offset and the like) is zero.
A distinction is made between loading with and loading without a host computer:
• In the former case, the tool data (magazine number, magazine location, tool number
and duplo number) is made available to the computer link software over an internal in-
terface and the host computer then takes control of the load procedure. No data is en-
tered in the magazine table or the tool memory.
• In the latter case, only the tool number, the duplo number and the tool status info are
entered in the PLC’s magazine table. Only the tool type (19, 29 or 39) for the first cut-
ting edge is entered in the NC’s tool offset memory.
No further tool data is requested for special-purpose tools.

C) Reading additional cutting edges (if any)

The "Read data for 1st cutting edge" request always reads the number of cutting edges
(must be stored on the code carrier). The "Number of cutting edges" tells FX "BEL-
CDTR" how many requests must be issued to read all cutting edge data (exception:
special-purpose tools of type 19,29,39, for which only the tool data for the first cutting ed-
ge is requested).
The cutting edge-related data for all subsequent cutting edges is entered automatically in
both the PLC’s magazine table and the NC’s tool offset memory.

Case 4
If tool management data was loaded and machine data bit "FLR" (loading/unloading with host
computer) is "1", FX "BEL-CDTR" forwards an enable bit to the computer link software to
transfer the tool data to (in the case of "standard" tools) or from (in the case of special-
purpose tools) the host computer (via internal interface data block DB 38; see Section 1.7).

1–8 © Siemens AG 1991 All Rights Reserved 6FC5 197-0AB40-0BP0

SINUMERIK 840/880 (PJ)
12.91 1 Introduction
1.3 Loading via code carrier FX ”BEL-CDTR”

Case 5
When all tool data has been entered in the PLC’s magazine table and the NC’s tool offset
memory, FX "BEL-CDTR" outputs the "W-IN" signal (tool to magazine).
The user must respond with either a positive acknowledgement (FX input "WZIM" (tool in
magazine), i.e. the tool is in the magazine at the location computed during the vacant location
search) or a negative acknowledgement (FX input "FBEL" (load error); the tool could not be
loaded into the relevant location in the magazine).
If the acknowledgement is positive, FX "BEL-CDTR" terminates without reporting an error
after entering the tool data in the interface data block to the computer link software (an
acknowledgement from the host computer is not awaited).
If the user responds with a negative acknowledgement, the tool data is deleted and FX
"BEL-CDTR" terminates with error.

Case 6
FX output "AKT" is "1" during loading, and is set to "0" when loading has been completed.
When an error occurs, loading is aborted ("AKT" remains at "1" for one PLC cycle before
going to "0") and the function block’s error output ("F") is set to "1", thus enabling the error
to be analyzed as soon as it occurs (i.e. when AKT=1 and F=1).

© Siemens AG 1991 All Rights Reserved 6FC5 197-0AB40-0BP0 1–9

SINUMERIK 840/880 (PJ)
1 Introduction 11.92
1.4 Unloading via code carrier FX "ENT-CDTR"

1.4 Unloading via code carrier FX "ENT-CDTR"

When a code carrier system is used, function block FX "ENT-CDTR" organizes the unload
procedure. Figure 4 shows the program structure for unloading via code carrier.

Case 1
During unloading, the SINUMERIK 880 tool management data and/or user data currently stored
in the NC/PLC is to be written back to the code carrier chip.

Before initiating the unload procedure, the user must decide:

• whether he wants to write only SINUMERIK 880 tool management data (FX inputs "E-WZ"
= 1 and "E-AW"=0)
• whether he wants to write both tool management data and user data (FX inputs "E-
WZ"=1 and "E-AW"=1).
• whether he wants to write only user data (FX inputs "E-WZ" = 0 and "E-AW"=1).

Tool management data:

On the basis of the specifications in the address parameter list, the standard package
generates the "Chip Write" request and copies the tool data from the magazine table and the
tool offset memory to the code carrier chip (one request is issued per cutting edge).

User data:
The user generates the request as described in "Package 7: Code Carrier, Frame Description"
in a data block (see Section 3.2) whose number is specified in the machine data. The standard
package then forwards the data to the encoding station.

1–10 © Siemens AG 1991 All Rights Reserved 6FC5 197-0AB40-0BP0

SINUMERIK 840/880 (PJ)
12.91 1 Introduction
1.4 Unloading via code carrier FX ”ENT-CDTR”

Case 2
The unload dialog is initiated by a positive edge at FX "ENT-CDTR" input "E-WZ" and/or "E-
AW" (e.g. when the operator presses a key at the unloading point). If more than one read/write
station is connected, the user must ascertain which station initiated the dialog and make the
number of that station available to FX "ENT-CDTR".
On the basis of this number, the standard function block can determine which user interface is
assigned to the station (the interface-to-station assignments are specified in the machine data;
see Section 1.8).

COM PLC PLC NC

Computer
User link
software

DB 128
DB 38 DB 126
UI
input Interface Format
buffer to comp. list
link CT
software data

DB 101/102
FX 15
User
interface Unload via
x code carrier
(x=0 to 31) DB 127
Status
DB 129 DB
UI
output
buffer

Interface
to 880
tool
man.
User

DBs TO
Standard tool manage-
ment FBs me-
mory
Current
maga-
zine
contents

UI = User interface

Program structure for UNLOADING via code carrier

© Siemens AG 1991 All Rights Reserved 6FC5 197-0AB40-0BP0 1–11

SINUMERIK 840/880 (PJ)
1 Introduction 12.91
1.4 Unloading via code carrier FX ”ENT-CDTR”

Case 3:

A) Writing user data

On initiation of the unload function, the user specifies the useful data DB (source, unload)
containing the user data to be transferred (1 request, max. 224 bytes); the DB must
conform to the conventions presented in "Package 7: Code Carrier Requests" (also refer
to Section 3.2).
The requested data is entered in the standard package’s DB 128 input buffer, and FX
output "ANWE" (user data) is set to "1" for one cycle. The user can then evaluate the
receive data (including any flags).
If the requested data cannot be evaluated within one cycle, the user must copy it from
input buffer DB128 (beginning data word DW 0) to another data block (i.e. save the data)
to prevent it from being overwritten (e.g. by subsequent tool data).

B) Writing the tool data for the first cutting edge

When the unload function is initiated (positive signal edge at FX input "E-WZ" and/or "E-
AW"), the user must specify the magazine number ("MANR"), the magazine location
("PLNR") and, if required, the status bits to be transferred (8 bits/FX input "ZK-E"; only
when defined in the address parameter list).

Special-purpose tools (type 19, 29, 39):

The tool type for the first cutting edge is 19, 29 or 39 (definition) for special-purpose tools.
Special-purpose tools are tools for which the cutting edge-specific data (such as geometry,
wear, offset and the like) is zero.
In the case of special-purpose tools (type 19, 29 or 39), only the tool number, the duplo
number, the tool type, the tool size and any status bits (FX input "ZK-E") are entered in
the request to the coding station. No other tool data is written to the code carrier chip for
these tools.

C) Writing the tool data for additional cutting edges

If a tool has more than one cutting edge, the data specified for them via the address
parameter list is written to the code carrier chip. This data is transferred to the chip without
any further user action.

Case 4
When tool data was unloaded and machine data bit "FLR" (load/unload with host computer) is
"1", FX "ENT-CDTR" forwards an enable signal to the computer link software over an internal
interface (DB 38); the computer link software forwards the tool data to the host computer.

1–12 © Siemens AG 1991 All Rights Reserved 6FC5 197-0AB40-0BP0

SINUMERIK 840/880 (PJ)
12.91 1 Introduction
1.4 Unloading via code carrier FX ”ENT-CDTR”

Case 5
The user must delete the tool from the tool management’s magazine table when FX output bit
"PLLO" (delete location) is "1" (this bit remains at "1" for one cycle only). The user must
remember that a tool may not be deleted from the magazine table until the host computer has
been informed (the host computer has reset enable bit D24.2 in DB 38, i.e. has acknowledged)
and the tool has actually been removed from the magazine.

Case 6
During unloading, FX output "AKT" (block executing) is "1". When unloading has been
completed, "AKT" goes to "0".
When an error occurs, unloading is aborted ("AKT" remains at "1" for one PLC cycle before
going to "0") and function block error output "F" goes to "1", thus making it possible to
evaluate an error as soon as it occurs (i.e. when AKT=1 and F=1).

© Siemens AG 1991 All Rights Reserved 6FC5 197-0AB40-0BP0 1–13

SINUMERIK 840/880 (PJ)
1 Introduction 11.92
1.5 Prerequisites and stipulations

1.5 Prerequisites and stipulations

1. Separate function blocks are available for loading (FX "BEL- CDTR") and unloading (FX
"ENT-CDTR) via code carrier.
2. SINUMERIK 880 tool management function blocks are required for internal PLC/NC data
transfers.
3. Tool management (magazine DBs) and the "Code Carriers, Transfer Tool Data with
Address Encoding" package must execute in the same PLC.
4. Special-purpose tools (tools whose cutting edge-specific data is not stored on the code
carrier) must be of type 19, 29 or 39 (first cutting edge/definition).
5. A cold restart (RESET) is mandatory following loading of the standard package in order to
allow the package to generate the required data blocks (status data block DB 127 and I/O
buffers DB 128/DB 129).
6. A separate user interface must be reserved for each encoding station, and each such
interface can be used to communicate only with the encoding station to which it has been
assigned.
7. When the code carrier requests are configured, their function numbers must be specified
in the machine data (DB 61, DW90/91) (also refer to Section 1.8).
The user must also allocate the read/write stations to the user interfaces in the machine
data (DB 61, data words DW 92 to DW 95) (see Section 8.1).
8. Address parameter list DB 126 may never be modified during operation.
Exception:
The ”Activation bit string” (DW 0 .. 4) can be manipulated before a write (read) operation
in accordance with the requirements.
9. The actual number of cutting edges must always be stored on the code carrier chip and
defined in address parameter list DB 126; failure to do so will result in a load abort (the
standard FX requires the number of cutting edges).
10. The useful data in a code carrier request/response is restricted to 244 bytes.
11. If a tool has more than one cutting edge, a separate request is required for each.
12. An error-free dialog always entails reading or writing of all cutting edges for a tool.
13. With the aid of the standard package, the user can request user data from the code carrier
station or write user data to the chip.
In this case, the standard package does nothing but handle communications with the
encoding station; the request data must be provided by, and the requested data evaluated
in, the user program. The standard package supplements the request by adding a frame
identification and an error code.
14. Tool size and tool type must be stored on the chip in the format required by the
SINUMERIK 8x0 tool management:
Tool type: 0 to 9, 10 to 19, 20 to 39
Tool size: 2 decades in BCD, the number of half-locations in front of/behind the tool
holder.
15. The address parameter list must conform to the conventions presented in Section 2.3.
16. The functions ”Processing from tool buffer” and ”Processing from load memory” can be
performed both for loading via code carrier and for unloading via code carrier.

1–14 © Siemens AG 1991 All Rights Reserved 6FC5 197-0AB40-0BP0

SINUMERIK 840/880 (PJ)
11.92 1 Introduction
1.6 General conditions

1.6 General conditions

1. The program and data structure permit only one dialog at a time, i.e. either loading or
unloading of a magazine.
2. As long as a dialog is in progress, any attempts to start a new dialog are rejected.
3. The I/O buffers (DB 128/129) and the "code carrier" user interfaces remain reserved until
a dialog has terminated.
4. All user interfaces in the "Load/unload via code carrier" package share a common input
buffer (DB 128) (useful input data DB for interface x) and a common output buffer
(DB 129) (useful output data DB for interface x) for tool data.
5. The following error control facilities have been implemented:
• Watchdog timer for code carrier system dialog (checks whether the code carrier
system’s read/write station responds to a request within a specifiable period of time).
• Errors in code carrier system frames.
• Request errors (incorrect number of "reference" addresses or incorrect identification).
• Tool handling errors flagged by the SINUMERIK 880 tool management.
6. The monitoring time for a load/unload procedure is the same as that for a dialog (the
watchdog monitors the time that elapses between issuance of a request to and receipt of a
response from the code carrier system).
7. Any modifications to input parameters MANR, PLNR (unload), E-WZ, E-AW, B-ZW, B-AW,
LSKP and STAT or to the package-related machine data are ignored once loading or
unloading has begun.
8. Function blocks FX "BEL-CDTR" and FX "ENT-CDTR" can only be used together.
9. FX "BEL-CDTR" must always be invoked before FX "ENT-CDTR" in the user program, as
FX "BEL-CDTR" initializes various parameters and generates the required data blocks on
a cold restart.
10. If bit D23.15 ("host computer available") is set in DB 64 (machine data bit for package 7),
FX14 "BEL-CDTR" and FX15 "ENT-CDTR" check the internal computer link interface (DB
38, data words DW 23 to DW 28; see Section 1.7) to see whether the "Computer Link:
Tool Dialogs" package (package 5) acknowledged a previous request to the host computer
(DB 38, DR 24) by resetting the relevant bit (DR 24). If this was not the case, package 7’s
standard function blocks wait for an acknowledgement from the host computer.
11. If an error (FX output "F" is "1") or power failure occurs during loading, the tool data
already entered in the PLC’s magazine table and the NC’s tool offset memory is erased.

© Siemens AG 1991 All Rights Reserved 6FC5 197-0AB40-0BP0 1–15

SINUMERIK 840/880 (PJ)
1 Einführung 12.91
1.7 Schnittstelle zur Rechnerkopplung

1.7 Interface to the computer link software

When the "Computer Link: Tool Dialogs" standard package (Package 5) is used, DB 38
serves as interface data block between the SINUMERIK 880 system’s "Code Carriers:
Transfer Tool Data with Address EncodiNg" package (Package 7) and the "Computer Link:
Tool DialoGs" package (Package 5).
The "Code Carriers, Transfer Tool Data with Address Encoding" package can use this
interface data block to forward tool data to the computer link software, and thus to the host
computer.

CL/CT interface DB 38

15 14 13 12 11 10 9 8
Byte No. Bit No.
7 6 5 4 3 2 1 0
DL 23

DR 23

DL 24 Loading/
unl. code
carr. in
progress

DR 24 Negative Tool Special-pur- Tool loaded

magazine unloaded pose tool
location no. unloaded

DW 25
Magazine location number Magazine number

DW 26
Tool number (high)

DW 27
Tool number (low)

DW 28
Duplo number

DW 29
Unassigned

DW 30
Unassigned

DW 31
Unassigned

D 24.15 Loading/unloading via code carrier in progress

D 24.0 Tool loaded (tool data goes to host computer)
D 24.1 Special-purpose tool loaded (tool data comes from host computer)
D 24.2 Tool unloaded (tool data goes to host computer)
D 24.7 Magazine location number is negative.

1–16 © Siemens AG 1991 All Rights Reserved 6FC5 197-0AB40-0AP0

SINUMERIK 840/880 (PJ)
11.92 1 Introduction
1.7 Interface to the computer link software

DB 38 (CL/CT interface)

Load (D 24.0)

Set: By the "Load/unload via code carrier" package to inform the host computer or the
user that a tool has been ”loaded”.
Reset: By Package 5 when the host computer has received all relevant information (1).

Special-purp. tool loaded (D 24.1)

Set: By the "Load/unload via code carrier" package when a special-purpose tool was
loaded (i.e. a tool whose cutting-edge specific data is not stored on the code
carrier chip; the host computer
Reset: By Package 5, when loading has been completed. (1)

Tool unloaded (D 24.2)

Set: By the "Load/unload via code carrier" package when a tool was unloaded via code
carrier.
Reset: By Package 5 when the host computer has received all relevant information (1).

Magazine number (DR 25)

Entered by: The "Load/unload via code carrier" package.

Magazine location no. (DL 25)

Entered by: The "Load/unload via code carrier" package.

Tool number (DW 26, 27)

Entered by: The "Load/unload via code carrier" package (for special-purpose tools only).

Duplo number (DW 28)

Entered by: The "Load/unload via code carrier" package (for special-purpose tools only).
In the case of "Tool loaded/unloaded", the data record addressed via the magazine and maga-
zine location numbers is forwarded to the host computer. It is up to the user to make sure that
no changes can be made in the magazine complement until the host computer has received all
relevant information.
The tool number and the duplo number are also evaluated when special-purpose tools are
loaded.
_______
(1) In the event of an error, one of the three error bits in DR 2 is set and the error code entered in DW 4 in
fixed-point notation (by the "Computer link" package), see Page 3-8 ”Error messages”.
Package 5 = Computer Link: Tool Dialogs

© Siemens AG 1991 All Rights Reserved 6FC5 197-0AB40-0BP0 1–17

SINUMERIK 840/880 (PJ)
1 Introduction 12.91
1.8 Machine data words

1.8 Machine data words

The following machine data words must be initialized for the "Code carriers: Transfer tool data
with address encoding" standard function blocks:

DB 61:
DW 90 Function number of the first input request
DW 91 Function number of the first output request
DW 92 Number of the user interface (read/write station 1)
DW 93 Number of the user interface (read/write station 2)
DW 94 Number of the user interface (read/write station 3)
DW 95 Number of the user interface (read/write station 4)

DB 131:
DL 00 WZYK: Amount of tool data transferred per cycle
DR 00 TUE: Watchdog timer
DL 01 DBQB: User data block (source, load)
DR 01 DWQB: User data word (source, load)
DL 02 DBQE: User data block (source, unload)
DR 02 DWQE: User data word (source, unload)

Function numbers for the I/O requests (DW 90, 91):

The user must initialize only the function number for the first input/output request; the function
numbers for subsequent I/O requests are assigned automatically as listed below.
Allocation of function numbers to request identifiers (MD words, DB 61):

DW 90: 1st input request = fct. no. ”n” : R–CB–(–)

2nd input request = fct. no. ”n+1” : T–CE–(–)
3rd input request = fct. no. ”n+2” : T–CB–(F)
4th input request = fct. no. ”n+3” : R–CE–(F)

DW 91: 1st output request = fct. no. ”k” : T–CB–(–)

2nd output request = fct. no. ”k+1” : R–CE–(–)
k, n = numerical values
– = represents a space (blank)

Note carefully:
When configuring these requests, remember that the function numbers of the first input and
first output request must be specified in machine data words DW 90 and DW 91 in data block
DB 61.
All function numbers/identifiers must be configured on the interface module (i.e. the
communications processor) and the user interface must be initialized in DB 99 (assignment
list, Package 4).

1–18 © Siemens AG 1991 All Rights Reserved 6FC5 197-0AB40-0BP0

SINUMERIK 840/880 (PJ)
11.92 1 Introduction
1.8 Machine data words

User interface/subaddress (DW 92 - DW 95)

A subaddress must also be configured on the interface module (also refer to Section 1.10).
A separate user interface must be reserved for each read/write station. Because it is possible
to connect as many as four read/write stations, each must be assigned a station number (1 to
4, ASCII). The station number must be specified as input parameter for the "Load/unload via
code carrier" standard FX function block.
The station numbers are allocated to the user interfaces by machine data in DB 61:

DB 61:
DW 92: No. of the user interface for read/write station 1 (which has the ASCII subaddress "1")
DW 93: No. of the user interface for read/write station 2 (which has the ASCII subaddress "2")
DW 94: No. of the user interface for read/write station 3 (which has the ASCII subaddress "3")
DW 95: No. of the user interface for read/write station 4 (which has the ASCII subaddress "4")

Important note:
A user interface number must be configured in DB 61 for each station number initialized in the
"Code carrier: Transfer tool data with address encoding" standard FX function block.

Machine data words DW 0 to DW 2 in DB 131

These machine data words are discussed in detail in the sections on FX "BEL-CDTR"/FX
"ENT-CDTR" signals (Sections 3.1 and 3.2).

Machine data words

DB 61:
DW 90 = MD No. m+90
DW 91 = MD No. m+91
DW 92 = MD No. m+92
DW 93 = MD No. m+93
DW 94 = MD No. m+94
DW 95 = MD No. m+95
PLC 1: m=2000
PLC 2: m=2100

DB 131:
DW 0 to DW 2 = User must generate and initialize data block on a cold restart (F2.1).

© Siemens AG 1991 All Rights Reserved 6FC5 197-0AB40-0BP0 1–19

SINUMERIK 840/880 (PJ)
1 Introduction 11.92
1.9 Machine data bits

1.9 Machine data bits

The following machine data bits must be initialized for the standard function blocks:

DB 64:
D 23.15 FLR : Host computer available (PLD-MD 70x6.7)(1)
D 23.14 DXQB : User DX (source, load) (PLC-MD 70x6.6)
D 23.13 DXQE : User DX (source, unload) (PLCMD 70x6.5)
These machine data bits are discussed in detail in the sections on FX "BEL-CDTR"/FX "ENT-
CDTR" signals (Sections 3.1 and 3.2).

_______
(1) PLC1: x=4
PLC2: x = 9 (only with SINUMERIK 880/880 GA2)

1–20 © Siemens AG 1991 All Rights Reserved 6FC5 197-0AB40-0BP0

SINUMERIK 840/880 (PJ)
12.91 1 Introduction
1.10 Configuring the code carrier requests

1.10 Configuring the code carrier requests

The code carrier requests are configured on the interface module via input/output lists. Please
refer to the computer link software manuals for detailed configuring information

The following must be observed when configuring code carrier requests:

1. A separate user interface must be reserved for each encoding station; a user interface can
be used to communicate only with the encoding station to which it has been assigned.
2. The code carrier input requests for each user interface must be configured in the input
lists on the interface module as described in Section 1.8. The user interfaces are
distinguished from one another only by their subaddress (the subaddress being an ASCII
number between 1 and 4 which identifies the read/write station assigned to the user
interface).
3. A subaddress must be specified in the interface module’s input lists for each code carrier
request:
Location: (subaddress begins in byte 13)
Length: 1 (byte)
Contents: Number of the read/write station (an ASCII number between 1 and 4, as no
more than four read/write stations can be connected).
Format: ASCII
Value range: 1-4
4. The code carrier output requests need be configured only once in the output list as
described in Section 1.8.
5. Each user interface must be configured in the DB 99 assignment list (refer to Package 4,
"Computer Link", Configurable Requests).

Example:
If two encoding stations are connected, two user interfaces must be reserved (DB 61, DW 92
to DW 95); in logical consequence, the code carrier requests must also be configured twice in
the input list on the interface module (once for each user interface, where each interface has a
different subaddress in the input list (the subaddress being the number of the read/write station
assigned to the user interface, e.g. "1" and "2").

© Siemens AG 1991 All Rights Reserved 6FC5 197-0AB40-0BP0 1–21

SINUMERIK 840/880 (PJ)
11.92 2 Address Parameter List
2.1 General remarks

2 Address Parameter List

2.1 General remarks

The addresses at which the various items of SINUMERIK 880 tool management data are
located on the code carrier chip, as well as the formats in which these data items are to be
read out from the chip, are specified in the so-called "Address parameter list".

2.2 Structure of the address parameter list

The structure of the address parameter list is described in detail below..

Address parameter list for 880 tool management data

DB 126:
DW 0: Bit string for user DBs in the magazine table
DW 1: Bit string P00-P15 for the first cutting edge
DW 2: Bit string reserved - must be 0
DW 3: Bit string P00-P15 for additional cutting edge(s)
DW 4: Bit string reserved - must be 0
DW 5: Reserved
DW 6: Reserved
DW 7: Reserved
DW 8: Reserved
DW 9: Reserved
:

Description:
1. P0-P15=P memory numbers in the NC tool memory.
2. Data words 5 to 9 are reserved for future use.
3. Activation bit string for user DBs in the magazine table (DB 126, DW 0:)
The bits in the string for the user DBs (1 to 7) are evaluated only for the first cutting edge,
and indicate which of the user DBs in the magazine table are to be located for subsequent
evaluation in the data record for the first cutting edge via the address parameter list.

DB 126: DW 0

15 7 6 5 4 3 2 1 0
0 0 0 0 0 0 0 0 0 07 06 05 04 03 02 01

© Siemens AG 1991 All Rights Reserved 6FC5 197-0AB40-0BP0 2–1

SINUMERIK 840/880 (PJ)
2 Address Parameter List 11.92
2.2 Structure of the address parameter list

Bit=1 : User DB available (will be evaluated)

Bit=0 : User DB not available (is not evaluated in the address list and is not included in
the data to/from the encoding station).
01 - 07 : Number of the user DB (1 to 7)
0 : Bit must be zero.

Important note:
The actual number of user DBs to be evaluated must be specified in the machine data.
4. Activation bit string P0 - P15 (DB 126, DW 1/3):
The bits in bit string P0 - P15 for the first cutting edge (DW 1) or the additional cutting
edge(s) (DW 3) indicate which P parameters (tool offset memory) are to be referenced via
the address list in the relevant data records (1st cutting edge, additional cutting edge(s)):

DB 126: DW 1, DW 3

15 0

15 14 13 12 11 10 09 08 07 06 05 04 03 02 01 00

Bit=1 : P parameter available (will be evaluated)

Bit=0 : P parameter not available (is not evaluated in the address list and is not included
in the data from/to the encoding station)
00-15 : P memory number

2–2 © Siemens AG 1991 All Rights Reserved 6FC5 197-0AB40-0BP0

SINUMERIK 840/880 (PJ)
11.92 2 Address Parameter List
2.2 Structure of the address parameter list

Address parameter list for 880 tool management data

DB 126:

DW 10 - 13 Addressing data Tool number

DW 14 - 17 Addressing data Duplo number
DW 18 - 21 Addressing data Tool size
DW 22 - 25 Addressing data Status bits
DW 26 - 29 Addressing data Number of cutting edges
DW 30 - 33 Addressing data User DB 1
DW 34 - 37 Addressing data User DB 2
DW 38 - 41 Addressing data User DB 3
DW 42 - 45 Addressing data User DB 4
DW 46 - 49 Addressing data User DB 5
DW 50 - 53 Addressing data User DB 6
DW 54 - 57 Addressing data User DB 7
DW 58 - 61 – – – Reserved – – –

DW 62 - 65 Addressing data User P0

DW 66 - 69 Addressing data Type P1

DW 70 - 73 Addressing data Geometry 1 P2

DW 74 - 77 Addressing data Geometry 2 P3

DW 78 - 81 Addressing data Geometry 3 P4

DW 82 - 85 Addressing data Offset 1 (dim.) P5

DW 86 - 89 Addressing data Offset 2 (dim.) P6

DW 90 - 93 Addressing data Offset 3 (dim.) P7

DW 94 - 97 Addressing data User P8

DW 98 - 101 Addressing data User P9

DW 102 - 105 Addressing data User P 10

DW 106 - 109 Addressing data User P 11

DW 110 - 113 Addressing data User P 12

DW 114 - 117 Addressing data User P 13

DW 118 - 121 Addressing data User P 14

P... = P number in NC tool memory

DW 10 - 61 : Refers to the PLC’s magazine table
DW 62 - 125 : Refers to the NC’s tool memory

© Siemens AG 1991 All Rights Reserved 6FC5 197-0AB40-0BP0 2–3

SINUMERIK 840/880 (PJ)
2 Address Parameter List 12.91
2.2 Structure of the address parameter list

DB 126

DL DR

Conditionally/unconditionally
DW n : Address length
requested address

DW n+1 : Address (byte 1) Address (byte 2)

DW n+2 : Address (byte 3) Address (byte 4)

DW n+3 : Format identifier Format parameter

n=numerical value

Addressing parameters:
1. Conditionally/unconditionally requested address:
0 = Conditionally requested address:
No error is flagged if the address is not on the chip (read) or cannot be stored on
the chip (write).
1 = Unconditionally requested address:
Error abort if the address is not on the chip (read) or cannot be stored on the chip
(write).
The status of this parameter (0/1) coincides with that of address status bit 3 (refer to
"Package 7: Code Carrier Frame Description").

2. Address length:
One byte, value range 0 - 4
The address length specifies the number of address bytes subsequently defined.

3. Address:
Max. 4 bytes, ASCII format
A distinction is made between upper and lower case letters.

4. Format identifier:
1 byte
5 format identifiers:
– 12H = unsigned binary
– 14H = signed binary
– 31H = unsigned fixed-point BCD
– 33H = signed fixed-point BCD
– 40H = ASCII string

5. Format parameter:
One byte;
Length specification (in bytes) only for formats 12H, 14H and 40H; number of decimal
places (in BCD characters/decades) and length specification (in bytes) for 31H and 33H
formats.

2–4 © Siemens AG 1991 All Rights Reserved 6FC5 197-0AB40-0BP0

SINUMERIK 840/880 (PJ)
12.91 2 Address Parameter List
2.2 Structure of the address parameter list

Description of the parameters in the address parameter list

Address length:
An address length of 0 means that the addressing data does not exist and will not be
evaluated by the standard software.

Format identifier:
The SINUMERIK’s format requirements are passed to the encoding station in a format
identifier. The encoding station formats the data to these specifications before forwarding it to
the SINUMERIK (load) or writing it to the code carrier chip (unload).
The standard package recognizes five format identifiers for the address parameter list. User
data, however, can be edited in all available formats!

• Format identifiers 12H and 14H (unsigned/signed binary):

The value is represented as binary integer. In format 14H (signed binary), the high-value
bit represents the sign of the number (0 for positive, 1 for negative). The format parameter
specifies the length in bytes.
• Format identifiers 31H and 33H (signed/unsigned BCD numbers):
Each value is represented as a fixed-point BCD character. In the case of signed BCD
numbers, the first character is interpreted as the sign. The integer places are separated
from the decimal places by a decimal point. Sign and decimal point are in BCD code as
per the ASCII table. The format parameters specify the number of bytes, including decimal
point and/or sign, and the number of decimal places (in BCD nibbles). The numerical value
has no decimal point if the number of decimal places is defined as zero.
• Format identifier 40H (ASCII string): A string of ASCII characters; in memory, an ASCII
stringis always right-justified. The format parameter specifies the length of the string in by-
tes.

Only format identifiers 12H, 14H, 31H, 33H and 40H may be used to load/unload SINUMERIK
880 tool management data. Any other format would result in an error.
User data, however, can be configured in any available format, and all format identifiers descri-
bed in "Package 7: Code Carrier Frame Description" are permitted. (Information regarding tho-
se format identifiers which have already been implemented must be obtained from the manu-
facturer of the encoding station).

© Siemens AG 1991 All Rights Reserved 6FC5 197-0AB40-0BP0 2–5

SINUMERIK 840/880 (PJ)
2 Address Parameter List 11.92
2.2 Structure of the address parameter list

Format parameter:
The table below shows the structure of the format parameter for the various format identifiers:

Format
Bit 7 - 4 Bit 3 - 0
identifier
12H Zero Number of bytes
14H Zero Number of bytes
31H No. of decimal places Number of bytes
33H No. of decimal places Number of bytes
40H Zero Number of bytes
H = hexadecimal

Address:
Jokers (ASCII "?") can be inserted in an address to represent the number of the cutting edge.
When used, a joker always stands for the number of the cutting edge, regardless of whether
the tool has one or more than one cutting edge.

Example:
Radius r? Radius of first cutting edge (r1),
Radius of second cutting edge (r2), and so on.
Wherever the cutting edge number is to be inserted in the address (e.g. geometry data, offset
data, etc.), a joker (ASCII "?") must be written at the corresponding address position in the
address parameter list.

Note:
Please refer to "Package 7: Code Carrier Frame Description" for a detailed description of the
addressing parameters.

2.3 Stipulations regarding the address parameter list

The symbolic addresses for T number (TN) and duplo addresses (SN) comply with the factory
standards and are therefore limited by the code carrier station to 6 and 4 places respectively.
In order to take advantage of the full number of places provided by the SIN 8x0 tool manage-
ment (8 digit ID No.) the address name must not be ”TN” (e.g. ”IN”).
1. Tool number (T number):
The T number must be on the chip, and is therefore requested "unconditionally"
(error abort if the T number is not on the chip).
According to the factory standards, the T number format is 31H (unsigned BCD), the for-
mat parameter always 03H (3 bytes = 6 places BCD). The address is "TN" (ASCII).
2. Duplo number:
The duplo number must be on the chip, and is therefore requested "unconditionally"
(error abort if the duplo number is not on the chip).
According to the factory standards, the format for the duplo number is 31H (unsigned
BCD), the format parameter always 02H (2 bytes = 4 places BCD). The address is "SN"
(ASCII).
3. Tool size:
The tool size must be on the chip, and is therefore requested "unconditionally"
(error abort if the tool size is not on the chip).
The tool size format is always 31H (unsigned BCD), the format parameter always 01H
(1 byte = 2 places BCD).

2–6 © Siemens AG 1991 All Rights Reserved 6FC5 197-0AB40-0BP0

SINUMERIK 840/880 (PJ)
12.91 2 Address Parameter List
2.3 Stipulations regarding the address parameter list

5. Tool type
Tool size and tool type must be stored on the chip in the format required by the SINUMERIK
880 tool management:
Tool type: 0 - 9, 10 - 19, 20 - 39
Tool size: 2 BCD decades; number of half-locations in front of/behind the tool holder.
6. Number of cutting edges:
The actual number of cutting edges must be on the chip, and is therefore requested "unconditio-
nally" (error abort if the number of cutting edges is not on the chip).
The format is always 31H (unsigned BCD), the format parameter always 91H
(1 byte=2 places BCD). The value range for the number of cutting edges is 1 to 9 (BCD).
7. Formats for 880 tool management data:
Only formats 12H, 14H, 31H, 33H and 40H may be used to load/unload SINUMERIK 880 tool
management data.

Format parameter
Format No. of DW's
No. of Used for:
identifier decimal in DB 126
bytes
places
12H 0 0-2 PLC magazine table 10 - 61

14H 0 0-2 PLC magazine table 10 - 61

31H 0 0-2 PLC magazine table 10 - 61

0-8 0-5 NC tool offset memory 62 - 189

33H 0-8 0-5 NC tool offset memory 62 - 189

40H 0 0-2 PLC magazine table 10 - 61

H = hexadecimal

As can be seen from the table, the P memories (NC tool memory) must always have BCD format
(31H or 33H) in address parameter list DB 126, whereas the tool data from the PLC’s magazine ta-
ble may have only formats 12H, 14H, 31H and 40H (hexadecimal) and are subject to the restrictions
presented in the table (exceptions: tool number, duplo number, tool size, tool type, status and num-
ber of cutting edges must always have format 31H).

Important note:
The preceding conventions and stipulations regarding format identifiers and format parameters must
be observed; failure to do so will result in incorrect formatting. In addition, each value must conform
to the format identifier defined for it (for instance, if a data item from the magazine table is assigned
format identifier 33H, its value may never be FFH).
The "Load/unload via code carrier" function blocks check only to make sure that there is a parame-
ter address list; they do not check the list entries for validity or plausibility (this is the user’s respon-
sibility).

© Siemens AG 1991 All Rights Reserved 6FC5 197-0AB40-0BP0 2–7

SINUMERIK 840/840C/880/880 GA2 (PJ)
12.91 3 FX Data Sheets
3.1 Load via code carrier (FX ”BEL-CDTR”)

3 FX Data Sheets

FX NO. FX IDENT. FX NAME

14 BEL-CDTR Load tool magazine via code carrier

15 ENT-CDTR Unload tool magazine via code carrier
16 UP-CDTR "Code carrier" subroutine

3.1 Load via code carrier (FX ”BEL-CDTR”)

1. Description:
The load dialog is initiated via FX input "B-WZ" and/or "B-AW". FX "BEL-CDTR" requests the
relevant data (SINUMERIK 880 tool management data or user data) from the code carrier
system over the specified user interface.
When loading 880 tool management data, the function block forwards the tool size to the
user together with an enable signal for a vacant location search. When the standard package
receives confirmation that a vacant location has been found, it enters the tool data for all
available cutting edges in the magazine table and the tool offset memory (exception: special-
purpose tools).
When loading special-purpose tools without using a host computer, the standard package
enters only the tool number, the duplo number, the tool status info and the tool size in the
PLC’s magazine table and sets the "Tool not enabled" bit. Only the tool type is entered in the
NC’s tool offset memory.
When loading special-purpose tools using a host computer, the tool data is made available to
the computer link software in an internal interface data block and the host computer takes
control of the load procedure.
When he wants to read user data, the user must generate the read request in a data block
specified in the machine data. FX "BEL-CDTR" then requests the data and enters it in input
buffer DB 128.

Additional specifications:
Lib. no.: E88530-B 5614-A- – –
FBs to be loaded: FX16
DBs to be loaded: DBZW-DBx (DBx = last DB in the table)
DB38
Type of call: Unconditional
DBs to be initialized: DB 126 (address parameter list)
Errors flagged: The following errors are flagged when FX "BEL-CDTR" causes a
system stop:

AKKU1 = FX number = 14
AKKU2 = Error code:
1: No DB 126 address list or address list has incorrect length.

© Siemens AG 1991 All Rights Reserved 6FC5 197-0AB40-0BP0 3–1

SINUMERIK 840/880 (PJ)
3 FX Data Sheets 12.91
3.1 Load via code carrier (FX ”BEL-CDTR”)

Block call:

FX 14: BEL-CDTR

I, BI B-WZ WZGR Q, BY
I, BI B-AW ZK-B Q, BY
I, BI LADE
I, BI F-LP ANWB Q, BI
I, BI WZIM W-IN Q, BI
I, BI FBEL LP-S Q, BI
AKT Q, BI
I, BY MANR F Q, BI
I, W PLNR
I, BY STAT
I, BY LSKP

DB64
D23.15 FLR
D23.14 DXQB
DB131
DL 0 WZYK
DR 0 TUE
DL 1 DBQB
DR 1 DWQB

DB131: Machine data words

DB64: Machine data bits

4. Signal description:

Input signals

B-WZ Load tool data

Trigger signal for loading 880 tool management data specified in the DB126 address parameter
list. The load is triggered on a positive edge (the signal is ignored, however, if a load or
unload dialog is already in progress). The signal state of "B-AW" is also evaluated
("B-AW"=1: Read user data from code carrier chip before reading 880 tool management
data).

B-AW Load user data

Trigger signal for loading user data (data not defined via the address parameter list). The load
is triggered on a positive edge (the signal is ignored, however, if a load or unload dialog is
already in progress). The signal state of "B-ZW" is also evaluated ("B-ZW"=1: Read 880 tool
management data after reading user data).

Lade Tool data loaded

Positive acknowledgement from user indicating that a vacant location has been found; the
appropriate FX parameter must be initialized with a valid magazine location number for loading
the tool data. Before acknowledging, the user can modify data in the tool management’s
dynamic buffer (DB number in DB127/DW47), e.g. set/reset status bits (evaluation of status
info, if any, stored on the code carrier).

3–2 © Siemens AG 1991 All Rights Reserved 6FC5 197-0AB40-0BP0

SINUMERIK 840/880 (PJ)
12.91 3 FX Data Sheets
3.1 Load via code carrier (FX ”BEL-CDTR”)

F-LP Error during vacant location search

Negative acknowledgement from the user: no magazine location available, error during vacant
location search, dialog abort. Once FX "BEL-CDTR" has enabled the vacant location search,
the user can abort the load by setting FX input "F-LP".

WZIM Tool in magazine

When all tool data has been entered in the PLC’s magazine table and the NC’s tool memory,
FX "BEL-CDTR" outputs the "W-IN" signal (tool to magazine). The user can issue a positive
acknowledgement via "WZIM", i.e. the tool is the magazine location found during the vacant
location search; FX "BEL-CDTR" terminates without flagging an error after entering the tool
data in the internal interface data block to the computer link software (no acknowledgement is
awaited from the host computer).

FBEL Load error

After entering all tool data in the PLC’s magazine table and the NC’s tool memory and in the
internal interface data block to the computer link software (no signal is awaited from the host
computer), FX "BEL-CDTR" outputs the "W-IN" signal (tool to magazine). The user can issue
a negative acknowledgement via "FBEL", i.e. the tool could not be loaded into the relevant
location in the magazine; FX "BEL-CDTR" deletes any tool data already entered in the
magazine table and/or the tool memory and terminates with error.

MANR Magazine number

For the option of loading or unloading tools via code carrier into or out of the tool buffer set
(magazine number =0, location number < 0) or into the loading buffer (magazine number =0,
location number > 0).

PLNR Location number

For the option of loading or unloading tools via code carrier into or out of the tool buffer set
(magazine number =0, location number < 0) or into the loading buffer (magazine number =0,
location number > 0).

STAT Station number

Number of the read/write station to be used for loading/unloading (value range: 1 to 4).

LSKP Read/write head

Number of the read/write head (value range: 1 to 8).

Output signals:

WZGR Tool size

Tool size (number of half-locations in front of and behind the tool holder).

Format: 2 BCD decades 7 0

Number of half- behind in front of
locations tool holder

© Siemens AG 1991 All Rights Reserved 6FC5 197-0AB40-0BP0 3–3

SINUMERIK 840/880 (PJ)
3 FX Data Sheets 12.91
3.1 Load via code carrier (FX ”BEL-CDTR”)

ZK-B Load status

The status info, if any, stored on the code carrier chip is forwarded to the user (one byte, and
only when specified in the address parameter list), thus enabling the user to change one or
more tool status bits.

ANWB User data loaded

Any user data that was requested has been loaded. The requested data is made available to
the user in the specified useful data DB/DX for post-processing (ANZW remains at "1" for one
cycle only).

W-IN Tool to magazine

After entering all tool data in the PLC’s magazine table and the NC’s tool memory, FX "BEL-
CDTR" outputs the "W-IN" signal (tool to magazine) and waits for either a positive ("WZIM",
tool in magazine) or negative ("FBEL", load error) acknowledgement.

LP-S Enable vacant location search

Enable (trigger) signal for a vacant location search. The user can search for a suitable empty
location for the tool (depending on the tool size). When FX "BEL-CDTR" has received either a
positive or negative acknowledgement from the user, it resets the enable bit.

AKT Loading in progress

FX "BEL-CDTR" (load) is executing. Any attempts to "load or unload via code carrier" are
ignored as long as AKT is "1".

F Error
An error occurred while FX "BEL-CDTR" was executing. "F" is reset when a new load or
unload dialog is enabled (when "F" goes to "1", "AKT" remains at "1" for one additional cycle
to give the user time to analyze the error). The error code is in data word DW3 in status data
block DB127.

Machine data bits:

FLR Host computer (DB64, D23.15)

1: Loading and unloading using a host computer; tool data is made available to the
computer link package’s function blocks in an internal interface data block (and
thus to the host computer), and a watchdog timer monitors the acknowledge-
ment.
0: No data is forwarded to the host computer.

DXQB DX (source, load) (DB64, D23.14)

This bit indicates whether the user read request is in a DB or a DX data block.
1: DX
0: DB

3–4 © Siemens AG 1991 All Rights Reserved 6FC5 197-0AB40-0BP0

SINUMERIK 840/880 (PJ)
11.92 3 FX Data Sheets
3.1 Load via code carrier (FX ”BEL-CDTR”)

Machine data words:

WZYK Tool data per cycle (DB131, DL0)

Amount of tool data to be processed per cycle. (This MD word allows the user to adapt the
cycle time to suit the prevailing conditions, as the evaluation/formatting of tool data is relatively
time-consuming).

TUE Watchdog timer (DB131, DR0)

Timer for monitoring communications with the encoding system (i.e. time which elapses
between request and response).

DBQB User data block (source, load) (DB131, DL1)

DWQB User data word (source, load) (DB131, DR1)

If the user wants to read user data from the code carrier chip, he must generate the request
himself as per the conventions for "Read" requests (see "Package 7: Code Carrier Frame
Description"). DBQB is the number of the DB/DX containing the read request, DWQB the
number of the first data word (pointer to the useful data length field). FX "BEL-CDTR"
requests the data from the encoding station (the number of bytes of useful data in a request or
response must not exceed 244).

© Siemens AG 1991 All Rights Reserved 6FC5 197-0AB40-0BP0 3–5

SINUMERIK 840/880 (PJ)
 a
aa
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
a
aa
aa
aa
aa
aa a
aa
aa
aa
aa

3–6
aa
aaa
aaaa
aaa
a aa
aaaaa
aaa
a
aaaaaa aaaaa

L.1
aaaaaa aaaaa

NAR
DWQB

Addr.
aaaaaa aaaaa
DBQB:

1 byte

1 byte
a
aa
aa
aa
aa
aa
a a
aa
aa
aa
aa
a

DWQB+6
DWQB+5
aa
aaaaa
aa
a aaaa
aa
a
aaa
aa
aaa aa
aaa
aaa

length
aaaaaa aaaaa

2 bytes
a
aa
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
aaaaaa aaaaa

Useful data
3 FX Data Sheets

No. of addr.
aaaaaa aaaaa

NAT
aaaaaa aaaaa

1 byte
aaaaaa aaaaa

? bytes
Addr. 1
a
aa
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
a
aa
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
a
aa
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
aa
aaaaa
aa
a aaaa
aa
a
a
a
aa
a
aa
a
aa
aaa
a
aa
a
a
aa
a
aa
aaa
a
a
aa
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
a
aa
aa
aa
aa
aa
a a
aa
aa
aa
aa
a

Address block 1
DWQB+1

F1
aaaaa
aa
a aaaa
aa
a
length

2 bytes
aa
aaa
aa
aaa aa
aaa
aaa

2 bytes
a
aa
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
Useful data

a
aa
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
aaaaaa aaaaa
3.1 Load via code carrier (FX ”BEL-CDTR”)

a
aa
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
a
aa
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
a
aa
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
a
aa
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
aaaaa aaaa
Sub-

aa
a aa
a
addr.

1 byte

aa
aaa
aa
aaa aa
aaa
aaa

Addr.

1 byte
1 stat.
aaaaaa aaaaa
DWQB+2

a
aa
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
a
aa
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
aaaaa aaaa

The useful data length must be specified twice:

aa
aaa
aaaa
aaa
a aa
aaaaa
aaa
a
aaaaaa aaaaa
no.

L2
aaaaaa aaaaa
Head

1 byte

aaaaaa aaaaa

Addr.

1 byte
a
aa
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
a
aa
aa
aa
aa
aa
a a
aa
aa
aa
aa
a

© Siemens AG 1991
a
aa
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
a
aa
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
a
aa
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
aaaaa stat. aaaa
Structure: User data block (source, load) ("Read" request)

aa
a aa
a
1 byte

? bytes
Addr. 2
aa
aaa
aa
aaa aa
aaa
aaa
DWQB+3

aaaaaa aaaaa
Identifier

a
aa
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
a
aa
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
aa
aaaaa
aa
a aaaa
aa
a
a
a
aa
a
aa
a
aa
aaa
a
aa
a
a
aa
a
aa
aaa
a
a
aa
aa
aa
aa
aa
a a
aa
aa
aa
aa
a

All Rights Reserved

a
aa
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
aaaaaa aaaaa
F2

data in the request, while the second specification is part of the useful data.
a
aa
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
aaaaaa aaaaa
2 bytes
2 bytes
DWQB+4

Info field

a
aa
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
a
aa
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
aa
aaaaa
aa
a aaaa
aa
a
a
a
aa
a
aa
a
aa
aaa
a
aa
a
a
aa
a
aa
aaa
a
a
aa
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
please refer to "Package 7: Code Carrier, Frame Description" for detailed information.

a
aa
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
aaaaa
aa
a aaaa
aa
a
Res.

1 byte

aa
aaa
aa
aaa aa
aaa
aaa
stat.

aaaaaa aaaaa
1 byte

aaaaaa aaaaa
Addr. 2

aaaaaa aaaaa
Structure as per the conventions described in "Package 7: Code Carrier Frame Description";

In total max. 244 bytes

aaaaa aaaa
The first specification is required by the computer link software but does not appear as useful
aaaaaa
a aaaaa
a

6FC5 197-0AB40-0BP0
SINUMERIK 840/880 (PJ)
11.92
 a
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
a
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
aaaaa aaaaa
11.92

aaaaa aaaaa

DW6
DW5
DW0
aaaaa aaaaa

L.1
aaaaa aaaaa

NAR
aaaaa aaaaa

Addr.

1 byte
1 byte
aaaaa aaaaa
DB 128:
a
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
aa
aaaa
aa
a aaaa
aa
a
aaa
aaa aa
aaa
aaa

length

2 bytes
a
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
aaaaa aaaaa
aaaaa aaaaa Useful data

NAT
aaaaa aaaaa

1 byte
aaaa aaaa

© Siemens AG 1991
No. of addresses

? bytes
Addr. 1
aa
aaaaa
aaa
a aa
aaaaa
aaa
a
a
aa
aa
aa
aa
a a
aa
aa
aa
aa
a

SINUMERIK 840/880 (PJ)

a
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
a
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
DW1

a
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
a
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
a
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
aaaaa aaaaa

F1
aaaa aaaa
length

2 bytes

aa
a aa
a

Address data block 1

2 bytes
aa
aaa
aaa aa
aaa
aaa
aaaaa aaaaa
Useful data

aaaaa aaaaa

All Rights Reserved

a
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
a
aa
aa
aa
aa a
aa
aa
aa
aa
aa
aaaaa
aaa
a aa
aaaaa
aaa
a
a
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
a
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
DW2

a
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
Sub-
addr.

1 byte

aaaaa aaaaa

1 stat
Addr.

1 byte
a
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
a
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
a
aa
aa
aa
aa
a a
aa
aa
aa
aa
a

The useful data length must be specified twice.

aa
aaaa
aa
a aaaa
aa
a
aaa
aaa aa
aaa
aaa
no.

aaaaa aaaaa
Head

aaaaa aaaaa
1 byte

1 byte
aaaaa aaaaa

Data 1
a
aa
aa
aa
aa
a a
aa
aa
aa
aa
a

6FC5 197-0AB40-0BP0
aa
aaaa
aa
a aaaa
aa
a
a
a
aa
a
aa
aaa
a
aa
a
a
aa
a
aa
aaa
a
a
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
DW3

a
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
aaaaa aaaaa
1 byte

a
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
Identifier

a
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
a
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
a
aa
aa
aa
aa a
aa
aa
aa
aa
aa
aaaaa
aaa
a aa
aaaaa
aaa
a
aaaaa aaaaa
please refer to "Package 7: Code Carrier Frame Description" for details.

a
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
aaaaa aaaaa
DW4

aaaaa aaaaa

data in the request, while the second specification is part of the useful data.
aa
aaaa
aa
a aaaa
aa
a
a
a
aa
a
aa
aaa
a
aa
a
a
aa
a
aa
aaa
a
2 bytes

aaaaa aaaaa
Info field

aaaaa aaaaa
with data

a
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
a
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
Structure: Data in input buffer DB 128 (response to "Read user data" request)

a
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
a
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
a
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
aaaa aaaa
. . . . further addresses . . .

aa
aaaaa
aaa
a aa
aaaaa
aaa
a
Res.

aaaaa aaaaa
1 byte

aaaaa aaaaa
Structure as per the conventions described in "Package 7: Code Carrier Frame Description";

aaaaa aaaaa

The first specification is required by the computer link software but does not appear as useful
a
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
aaaa aaaa
3.1 Load via code carrier (FX ”BEL-CDTR”)

aa
a aa
a
3 FX Data Sheets

3–7
In total max. 244 bytes

aa
aaa
aa aa
aaa
aa
aaaaa
a aaaaa
a
3 FX Data Sheets 11.92
3.1 Load via code carrier (FX ”BEL-CDTR”)

Error flags

DB 127:
DR 2 : Error identification bits
DW 3 : Error code in "Load/unload via code carrier" package
DW 4 : Error code in "Computer link" package
Refer to the "Computer Link" package for a list of error codes.

DB 127, DR 2:

1 1 1 1 1 (1)

Error message computer link on loading

Error message computer link on loading special tools
Error message computer link on unloading
Error in FX "ENT-CDTR"
Error in FX "BEL-CDTR"

All other bits are reserved and must not be changed by the user.

_______
(1) These bits remain static ”1”. They must be reset by the user after evaluation.

3–8 © Siemens AG 1991 All Rights Reserved 6FC5 197-0AB40-0BP0

SINUMERIK 840/880 (PJ)
11.92 3 FX Data Sheets
3.1 Load via code carrier (FX ”BEL-CDTR”)

Errors flagged by FX "BEL-CDTR" and FX "ENT-CDTR"

Code Description

1 Errors 1 to 299 are flagged by the encoding

: station (see the Appendix or the code carrier
299 manufacturer’s error list).
300 –––
301 –––
302 Time-out
The encoding station failed to respond to a request
within 30 seconds.
303 Load aborted
FX input "F-LP" was set following a vacant location search.
304 Unload aborted
FX input "FBEL" was set in response to the
acknowledgement request (FX output "W-IN"
305 Five incorrect frames received
Incorrect no. of addresses, incorrect identification.
306 Computer link error (error in DW 4)
The computer link package flagged an error in the user output interface data
block.
307 Address length exceeds 4 bytes
An address length exceeding 4 bytes was detected in the address parameter list
or in the data transferred by the encoding station.
308 Encoding station transferred data in incorrect sequence
309 More than 5 bytes of tool data received
310
: Reserved for future use
320
321 Request issued before preceding request was serviced
322 Illegal command code
323 No such magazine
324 No such magazine location
325 No such cutting edge
326 No. of cutting edges loaded conflicts with setup data
327 Cutting edges not loaded in ascending order
328 Retrofitting: T number/duplo number not found
329 D number already exists or multiple definition
330 Tool memory full (all D numbers already assigned)
331 Abort due to power failure, any data already entered is deleted
332 Plausibility check error
333 Tool size conflicts with specified tool size
334 No new tools added to magazine
335 Reference list incorrect
336 Retroloading in tool buffer not possible
337 D numbers already entered in reference list

Errors 321 to 337 are flagged by the SINUMERIK 880 tool management.

© Siemens AG 1991 All Rights Reserved 6FC5 197-0AB40-0BP0 3–9

SINUMERIK 840/880 (PJ)
3 FX Data Sheets 12.91
3.1 Load via code carrier (FX ”BEL-CDTR”)

Important note:
320 must be subtracted from error codes greater than 337; for a description of the resulting
error codes, please refer to the 880 tool management manual, FB139 "DAT-VERT" (may be
required for 880 tool management expansion!).

Errors flagged by the encoding station:

Errors 1 to 299 are reported by the encoding station.
A distinction is made between the following types of errors:
• "General" errors:
General errors are errors which cannot be attributed to a specific address (such as wrong
read/write head, no communication possible, chip capacity problems and the like).
• "Specific" errors:
These are errors attributable to a specific address. The relevant address is made available
for evaluation in input buffer DB128 (for details on DB128, refer to page 3-6 or 3-14; for
details on the data forwarded to and from the encoding station, refer to "Package 7: Code
Carrier Requests"). In this case, input buffer DB128 contains only the address (data) block
to which the error refers.

3.2 Unloading via code carrier (FX ”ENT-CDTR”)

1. Description:
FX "BEL-CDTR" receives the enable signal when the tool is at the read/write station. Tool data
and/or user data can then be written to the code carrier chip.
In the case of user data, FX "BEL-CDTR" is informed via an input signal and the data made
available to the function block. The function block itself handles only communications with the
encoding station.
In the case of tool data, the data for the various cutting edges is read out and transferred to
the encoding station. The unload procedure is regarded as complete when the read/write
station acknowledges.

2. Additional specifications:
Lib. no.: E88530-B 5615-A- – –
FBs to be loaded: FX14, FX16
DBs to be loaded: DBZW-DBx (DBx = last DB in the table)
DB 38
Type of call: Unconditional
DBs to be initialized: DB 126 (address list)

3–10 © Siemens AG 1991 All Rights Reserved 6FC5 197-0AB40-0P0

SINUMERIK 840/880 (PJ)
12.91 3 FX Data Sheets
3.2 EntladenUnloading via code carrier (FX ”ENT-CDTR”)

3. Block call

FX 15: ENT-CDTR

I, BI E-WZ ANWB Q, BI
I, BI B-WZ PLLO Q, BI
AKT Q, BI
I, BY MANR F Q, BI
I, BY PLNR
I, BY STAT
I, BY LSKP
I, BY ZK-E

DB64
D23.15
D23.13 FLR
DXQE
DB131
DL 0 WZYK
DR 0 TUE
DL 2 DBQE
DR 2 DWQE

DB 131: Machine data words

DB 64: Machine data bits

4. Signal description

Input signals

E-WZ Unload tool data

Enable signal for unloading the relevant 880 tool management data and the tool data specified
via address parameter list DB 126. The positive edge is evaluated (the enable is ignored if a
load or unload dialog is already in progress). The signal state of "E-AW" is also evaluated ("E-
AW"=1 means that user data is to be written to the code carrier chip prior to writing 880 tool
management data).

E-AW Unload user data

Enable signal for unloading user data (i.e. data not defined via the address parameter list). The
positive edge is evaluated (the signal is ignored if a load or unload dialog is already in
progress).
The signal state of "E-ZW" is also evaluated ("E-ZW"=1 means that 880 tool management
data is to be written to the chip after the user data has been written).

MANR Magazine number

For the option of loading or unloading tools via code carrier into or out of the tool buffer set
(magazine number =0, location number < 0) or into the loading buffer (magazine number =0,
location number > 0).

PLNR Location number

For the option of loading or unloading tools via code carrier into or out of the tool buffer set
(magazine number =0, location number < 0) or into the loading buffer (magazine number =0,
location number > 0).

© Siemens AG 1991 All Rights Reserved 6FC5 197-0AB40-0BP0 3–11

SINUMERIK 840/880 (PJ)
3 FX Data Sheets 12.91
3.2 Unloading via code carrier (FX ”ENT-CDTR”)

STAT Station number

Number of the read/write station to be used for loading/unloading (value range: 1 to 4)

LSKP Read-write head

Number of the read-write head (value range: 1 to 8).

ZK-E Unload status

The user can forward the status info stored on the chip, if any, to FX "ENT-CDTR" in a byte
for output to the code carrier chip (possible only in conjunction with the unloading (writing) of
880 tool management data, and then only when "ZK-E" is defined in the address parameter
list).

Output signals

ANWE User data unloaded (written)

User data was written to the chip. The receive data is made available in the standard
package’s DB128 input buffer for post-processing (ANWE is "1" for one cycle only).

PLLO Delete location

Signal to delete the tool in the magazine table (PLLO remains at "1" for one cycle only). The
data is on the code carrier and can be deleted in the tool management’s magazine table.

A tool must not be deleted in the magazine table until the host computer has been in-
formed (when the host computer has reset enable bit D24.2 in DB38, i.e. has ack-
nowledged) and the tool has actually been removed from the magazine.

AKT Unload in progress

FX "ENT-CDTR" (Unload) is executing. As long as AKT is "1", any attempts to load or unload
via code carrier are ignored.

F Error
An error occurred while FX "ENT-CDTR" was executing. "F" is reset when a new load or un-
load dialog is enabled (when an error is detected, i.e. when "F" is set to "1", "AKT" remains
at "1" for one additional cycle to allow the user to analyze the error). The error code is in data
word DW 3 of status data block DB 127.
The error codes are described in detail in FX14 "BEL-CDTR".

Machine data bits:

FLR Host computer (DB 64, D23.15)

1: Loading and unloading; the data is made available to the computer link package’s
function blocks for forwarding to the host computer; the time which elapses
between request and response is monitored by the watchdog timer.
0: Data not forwarded to the host computer.

DXQE DX source, unload (DB 64, D23.13)

This bit indicates whether the user request is in a DB or DX data block.
1: DX data block
0: DB data block

3–12 © Siemens AG 1991 All Rights Reserved 6FC5 197-0AB40-0BP0

SINUMERIK 840/880 (PJ)
11.92 3 FX Data Sheets
3.2 Unloading via code carrier (FX ”ENT-CDTR”)

Machine data words:

WZYK Tool data per cycle (DB 131, DL 0)

Amount of tool data to be processed per cycle (WZYK makes it possible to adapt the cycle
time to suit the obtaining conditions, as the evaluation/formatting of tool data is relatively time-
consuming).

TUE Watchdog timer (DB 131, DR 0)

Timer for monitoring communications with the encoding system (monitors the time that elapses
between request and response).

DBQE User data block (source, unload) (DB 131, DL 2)

DWQE User data word (source, unload) (DB 131, DR 2)

When the user wants to write user data to the code carrier chip, he must generate the request
himself as per the conventions for "Write" requests (refer to "Package 7: Code Carrier Frame
Description"). DBQE is the number of the DB or DX containing the request, DWQW the num-
ber of the first data word (pointer to the useful data length).
FX "ENT-CDTR" forwards the data to the encoding station (the number of useful data bytes in
a request or response must not exceed 244).

© Siemens AG 1991 All Rights Reserved 6FC5 197-0AB40-0BP0 3–13

SINUMERIK 840/880 (PJ)
 a
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
a
aa
aa
aa
aa a
aa
aa
aa
aa
aa
aaaaa
aaa
a aa
aaaaa
aaa
a

3–14
aaaaa aaaaa

L.1
aaaaa aaaaa

NAR
DWQB

Addr.
DBQE:
aaaaa aaaaa

1 byte
1 byte
a
aa
aa
aa
aa
a a
aa
aa
aa
aa
a

DWQE+6
DWQB+5
aa
aaaa
aa
a aaaa
aa
a
aaa
aaa aa
aaa
aaa

length
aaaaa aaaaa

2 bytes
a
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
aaaaa aaaaa

Useful data
3 FX Data Sheets

aaaaa aaaaa

NAT
aaaaa aaaaa

1 byte
aaaaa aaaaa

No. of addresses

? bytes
Addr. 1
a
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
a
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
a
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
aa
aaaa
aa
a aaaa
aa
a
a
a
aa
a
aa
aaa
a
aa
a
a
aa
a
aa
aaa
a
a
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
a
aa
aa
aa
aa
a a
aa
aa
aa
aa
a

F1
DWQB+1

aaaa
aa
a aaaa
aa
a
length

2 bytes

2 bytes

Address data block 1

aa
aaa
aaa aa
aaa
aaa
a
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
Useful data

a
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
a
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
a
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
a
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
3.2 Unloading via code carrier (FX ”ENT-CDTR”)

a
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
a
aa
aa
aa
aa a
aa
aa
aa
aa

stat.
aa
a aa
a

1 byte
aa
aaa
aaa aa
aaa
aaa

Addr. 1
aaaaa aaaaa
DWQB+2

1 byte

a
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
Subaddr.

a
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
aaaa aaaa

The useful data length must be specified twice.

aa
aaaaa
aaa
a aa
aaaaa
aaa
a
a
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
aaaaa aaaaa

Data 1

? bytes
aaaaa aaaaa
no.

aaaaa aaaaa
Head

1 byte

a
aa
aa
aa
aa
a a
aa
aa
aa
aa
a

© Siemens AG 1991
a
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
Description"; please refer to these conventions for details.

a
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
aaaaa aaaaa

data, while the second specification is part of the useful data.

a
aa
aa
aa
aa a
aa
aa
aa
aa
aa
aaaaa
aaa
a aa
aaaaa
aaa
a
DWQB+3

a
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
Structure: User data block (source, unload) ("Write" request)

1 byte

a
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
Identifier

a
aa
aa
aa
aa a
aa
aa
aa
aa
aa
aaaaa
aaa
a aa
aaaaa
aaa
a
a
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
aaaaa aaaaa

All Rights Reserved

a
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
a
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
a
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
DWQB+4

a
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
with data

aaaaa aaaaa
2 bytes

aaaaa aaaaa
Info field

aa
aaaa
aa
a aaaa
aa
a
a
a
aa
a
aa
aaa
a
aa
a
a
aa
a
aa
aaa
a
a
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
a
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
aaaa aaaa
. . . . further addresses . . .

aa
aaaaa
aaa
a aa
aaaaa
aaa
a

The first specification is required by the computer link software but is not part of the useful
a
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
Res.

1 byte

a
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
aaaaa aaaaa
The structure must accord with the conventions presented in "Package 7: Code Carrier Frame

aaaaa aaaaa

6FC5 197-0AB40-0BP0
aaaaa aaaaa

SINUMERIK 840/880 (PJ)

aaaa aaaa
12.91

aaaaa
a aaaaa
a
In total max. 224 bytes
 a
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
a
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
aaaaa aaaaa
12.91

aaaaa aaaaa

DW6
DW5
DW0
aaaaa aaaaa

L.1
aaaaa aaaaa

NAR
aaaaa aaaaa

Addr.

1 byte
1 byte
aaaaa aaaaa
DB 128:
a
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
aa
aaaa
aa
a aaaa
aa
a
aaa
aaa aa
aaa
aaa

length

2 bytes
a
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
aaaaa aaaaa
aaaaa aaaaa Useful data

NAT
aaaaa aaaaa

1 byte
aaaa aaaa

© Siemens AG 1991
No. of addresses

? bytes
Addr. 1
aa
aaaaa
aaa
a aa
aaaaa
aaa
a
a
aa
aa
aa
aa
a a
aa
aa
aa
aa
a

SINUMERIK 840/880 (PJ)

a
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
a
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
DW1

a
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
a
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
a
aa
aa
aa
aa
a a
aa
aa
aa
aa
a

F1
a
aa
aa
aa
aa a
aa
aa
aa
aa
length

2 bytes

2 bytes
aa
a aa
a

Address data block 1

aa
aaa
aaa aa
aaa
aaa
aaaaa aaaaa
Useful data

aaaaa aaaaa

All Rights Reserved

a
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
a
aa
aa
aa
aa a
aa
aa
aa
aa
aa
aaaaa
aaa
a aa
aaaaa
aaa
a
a
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
a
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
DW2

aaaaa aaaaa

stat
aaaaa aaaaa

1 byte
aaaaa aaaaa

Addr. 1
aaaaa aaaaa
1 byte

a
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
Subaddr.

room for it on the chip, it is returned as follows:

a
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
aaaaa aaaaa

The useful data length must be specified twice.

aa
aaaa
aa
a aaaa
aa
a
a
a
aa
a
aa
aaa
a
aa
a
a
aa
a
aa
aaa
a
aaaaa aaaaa

Data 1
aaaaa aaaaa

? bytes
no.

aaaaa aaaaa
Head

aaaaa aaaaa
1 byte

6FC5 197-0AB40-0BP0
aa
aaaa
aa
a aaaa
aa
a
aaa
aaa aa
aaa
aaa
Description"; please refer to these conventions for details.

a
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
DW3

a
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
a
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
a
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
aaaaa aaaaa
1 byte

a
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
Identifier

a
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
aaaa aaaa

data, while the second specification is actually part of the useful data.
aa
aaaaa
aaa
a aa
aaaaa
aaa
a
a
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
a
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
DW4

a
aa
aa
aa
aa a
aa
aa
aa
aa
aa
aaaaa
aaa
a aa
aaaaa
aaa
a
a
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
aaaaa aaaaa
with data
2 bytes

aaaaa aaaaa
Info field

a
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
Structure: Data in input buffer DB128 (response to "Write user data" request)

a
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
a
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
a
aa
aa
aa
aa
a a
aa
aa
aa
aa
a
aaaaa aaaaa
. . . . further addresses . . .

aa
aaaa
aa
a aaaa
aa
a
a
a
aa
a
aa
aaa
a
aa
a
a
aa
a
aa
aaa
a
Res.

aaaaa aaaaa
If data could not be written because it was not on the chip or because there was not enough
1 byte

aaaaa aaaaa

The first specification is required by the computer link software but does not appear as useful
aaaaa aaaaa
The structure must accord with the conventions presented in "Package 7: Code Carrier Frame

a
aa
aa
aa
aa a
aa
aa
aa
aa
3.2 Unloading via code carrier (FX ”ENT-CDTR”)

In total max. 244 bytes

aa
a aa
a
3 FX Data Sheets

3–15
aa
aaa
aaa aa
aaa
aaa
3 FX Data Sheets 12.91
3.3 Subroutine (FX ”UP-CDTR”)

3.3 Subroutine (FX ”UP-CDTR”)

Description
This function block is used as subroutine by both FX "BEL-CDTR" and FX "ENT-CDTR"; both
FXs call FX "UP-CDTR".

2. Additional specifications
Lib. no.: E88530-B 5616-A- – –
FBs to be loaded: None
DBs to be loaded: None
Type of call: "UP-CDTR" is called by both FX "BEL-CDTR" and FX "ENT-CDTR"
DBs to be initialized: DB126 (address list)
Error flags: The following errors are flagged when FX "UP-CDTR" initiates a
system STOP:
AKKU1 = FX number = 16
AKKU2 = Detailed error code
1: Invalid magazine number
2: Invalid station number (1 - 4)
3: Invalid user interface (0 - 31)

3–16 © Siemens AG 1991 All Rights Reserved 6FC5 197-0AB40-0BP0

SINUMERIK 840/880 (PJ)
11.92 4 Block Data for FB Package 7

4 Block Data for FB Package 7

Call DBs used

Length Lib. no. length Execution
Nesting FBs Variables
Block Designation word E88530-B in time
depth called used
(1) (2) words (in ms) Length Length
RAM EPROM
(2) (1) (1)

FX14 BEL-CDTR 1269 5614-

A- – – 19 3 FB11 DB126 190 FW 224-254
FB60 DB127 170
FB89 DB128 128
FB138 DB129 128
FX16

FX15 ENT-CDTR 969 5615-

A- – – 13 3 FX16 DB126 190
FB60 DB127 170 FW224-254
FB138 DB128 128
DB129 129

FX16 UP-CDTR 737 5616-

A- – – 2 2 FB60 FW224-254

_______
1) The block length varies according to the version.
2) The library number varies according to the control type.

© Siemens AG 1991 All Rights Reserved 6FC5 197-0AB40-0BP0 4–1

SINUMERIK 840/880 (PJ)
11.92 5 Application
5.1 General remarks

5 Application

5.1 General remarks

1. Prerequisites:
Package 1 ("SINUMERIK 880 Tool Management") has been loaded into the PLC and
FB139 ("Data distributor for 880 tool management") is invoked unconditionally in every
cycle.
2. Configure requests for "Load/unload via code carrier" (see Sections 1.8 and 1.10).
3. Initialize machine data words (see Section 5.2).
4. Load package 7 ("Code Carriers: Transfer Tool Data with Address Encoding") into the
same PLC as the tool management standard function blocks.
5. Generate and load address parameter list DB126.
6. Initialize FX14 "BEL-CDTR" and FX15 "ENT-CDTR" as per the machine configuration.
7. Link FX14 and FX15 into the user program and execute a cold restart (RESET). Standard
blocks FX14 and FX15 must be invoked unconditionally in every cycle.

5.2 Machine data

5.2.1 FB machine data for package 7

Machine data words:

The following machine data words must be initialized for package 7 (for details, please refer to
Sections 1.8 and 1.10):

PLC MD DB 61 DW Description

:
2x90 90 Function number of the 1st input request
2x91 91 Function number of the 1st output request
2x92 92 User interface number (station 1)
2x93 93 User interface number (station 2)
2x94 94 User interface number (station 3)
2x95 95 User interface number (station 4)
:

x=0 : PLC1
x=1 : PLC2 (only for SINUMERIK 880/880 GA2)

© Siemens AG 1991 All Rights Reserved 6FC5 197-0AB40-0BP0 5–1

SINUMERIK 840/880 (PJ)
5 Application 11.92
5.2.1 FB machine data for package 7

DB131 Description

DL 0 WZYK Amount of tool data per cycle

DR 0 TUE Watchdog timer for dialog
DL 1 DBQB Data block (source, load)
DR 1 DWQB Data word (source, load)
DL 2 DBQE Data block (source, unload)
DR 2 DWQE Data word (source, unload)

Note:
DB131 is used as data block for the machine data words required for package 7. The user
program must generate DB131 and initialize data words 0 - 2 on a cold restart (F2.1).

Machine data bits:

PLC MD DB 64 DW Description

:
m+23 23 Bit 15: Host computer available
Bit 14: DB/DX (source, load)
Bit 13: DB/DX (source, unload)
Bit 12 - 0: Unassigned
:

m = 7000 : PLC1
m = 7050 : PLC2 (only for SINUMERIK 880/880 GA2)

5–2 © Siemens AG 1991 All Rights Reserved 6FC5 197-0AB40-0BP0

SINUMERIK 840/880 (PJ)
11.92 5 Application
5.2.2 General machine data

5.2.2 General machine data

NC MD:

MD 13 Number of P memories (tool offset memory)

MD 210 Number of TO areas
MD 211 TO area 1 beginning D no. = . . .
MD 212 TO area 2 beginning D no. = . . .
MD 213 TO area 3 beginning D no. = . . .
: :
MD 226 TO area 16 beginning D no. = . . .
MD 5018 Bit 6: Activate 1st interface module
MD 5018 Bit 7: Activate 2nd interface module
MD 5038 PLCs
Bit 0: PLC1
Bit 1: PLC2
Bit 2: PLC3
Bit 3: PLC4
Bit 12-0: Unassigned
:

PLC MD:

PLC MD DB 61: DW Description

2x00 0 Start address of tool buffer

2x01 1 No. of DWs in tool buffer
2x02 2 No. of DBs for user data
2x03 3 No. of DBs for reference data
2x04 4 Start address (magazine 1)
2x05 5 Magazine length (in DWs) (magazine 1)
2x06 6 Assigned TO area (magazine 1)
2x07 7 Assigned background magazine (magazine 1)
2x08 8 Start address (magazine 2)
2x09 9 Magazine length (in DWs) (magazine 2)
2x10 10 Assigned TO area (magazine 2)
2x11 11 Assigned background magazine (magazine 2)
: : :
2x64 64 Start address (magazine 16)
2x65 65 Magazine length (in DWs) (magazine 16)
2x66 66 Assigned TO area (magazine 16)
2x67 67 Assigned background magazine (magazine 16)

x = 0 : PLC1
x = 1 : PLC2 (only for SINUMERIK 880/880 GA2)

© Siemens AG 1991 All Rights Reserved 6FC5 197-0AB40-0BP0 5–3

SINUMERIK 840/880 (PJ)
5 Application 12.91
5.3 Example

5.3 Example
Assumptions:
Package 1 in PLC1
Package 7 in PLC1
Package 1: SINUMERIK 880 tool management
Package 7: Code carriers: Transfer tool data with address encoding

Stipulations:
1. Only one encoding station (read/write station) is connected. The user interface number
is 1.
2. There is only one magazine (magazine 1).
3. The user should have the option of reading user data (but no 880 tool management data)
from and writing it to the chip.
The "Read" request is to be generated in DB230, the "Write" request in DB231. These
data blocks are discussed in detail in the following.
The user can read 880 tool management data and/or user data from or write it to the code
carrier chip on a positive signal edge at FX input "B-ZW" and/or "B-AW" or at FX input
"E-ZW" and/or "E-AW".

Example: machine data

NC MD:

MD 13 16 Number of P memories
MD 210 1 Number of TO areas
MD 211 1 TO area1 beginning D no. = 1
MD 212 0 TO area 2 beginning D no. = . . .
: :
MD 226 0 TO area 16 beginning D no. = . . .

MD 5018 01000000 1st interface module is active (e.g. CP 315)

MD 5038 00000001 Bit pattern for PLC1

5–4 © Siemens AG 1991 All Rights Reserved 6FC5 197-0AB40-0BP0

SINUMERIK 840/880 (PJ)
11.92 5 Application
5.3 Example

PLC MD:

MD 2000 4 Start address of tool buffer

MD 2001 10 No. of DWs in tool buffer
MD 2002 7 No. of DBs for user data
MD 2003 4 No. of DBs for reference data
MD 2004 31 Start address (magazine 1)
MD 2005 40 Magazine length (in DWs) (magazine 1)
MD 2006 1 Assigned TO area (magazine 1)
MD 2007 0 Assigned background magazine (magazine 1)
MD 2008 0 Start address (magazine 2)
MD 2009 0 Magazine length (in DWs) (magazine 2)
MD 2010 0 Assigned TO area (magazine 2)
MD 2011 0 Assigned background magazine (magazine 2)
: : :
MD 2090 80 Function no. of 1st input request (package 7)
MD 2091 80 Function no. of 1st output request (package 7)
MD 2092 1 User interface number station 1 (package 7)
MD 2093 0 User interface number station 2 (package 7)
MD 2094 0 User interface number station 3 (package 7)
MD 2095 0 User interface number station 4 (package 7)
MD 7012 xxx1xxxx Bit 4: Magazine 1 not configured
MD 7046 100xxxxx Bit 7: Host computer available
Bit 6: User data (source, load) = DB
Bit 5: User data (source, unload) = DB
DB 131:
DW 0 KY=4, 1 WZYK=4, TUE =1
DW 1 KY=230, 0 DBQB=DB230, beginning DW0
DW 2 KY=231, 0 DBQE=DB231, beginning DW0

Example for configuring code carrier requests

Please refer to the "Planning Guide for the Computer Link Software" for details.
For the example, the following lists must be generated using the CP315 configuring software
(the CP315 is the interface module or serial interface to SINUMERIK 880):

ADDRESS LIST
PD–TYP: CODETR

LPAR Dest./abs. INT.NO. Data block Data word Coord. flag Command
CODE 1 1 1 1 AD

© Siemens AG 1991 All Rights Reserved 6FC5 197-0AB40-0BP0 5–5

SINUMERIK 840/880 (PJ)
5 Application 12.91
5.3 Example

HYBRID LIST

I/O FNO Fct.name Sts Sa Pos Sa L Sa Cont Format name

I 80 R CB 2 13 1 1 CODE CARRIER
I 81 T CI 2 13 1 1 CODE CARRIER
I 82 T CB F 2 13 1 1 CODE CARRIER
I 83 R CI F 2 13 1 1 CODE CARRIER

O 80 T CB 2 13 1 1 CODE CARRIER
O 81 R CI 2 13 1 1 CODE CARRIER

INPUT LIST

MASTER DATA PD_TYP PARAMETERS

Function name : R CB SINUMERIK unit : PLC 1

Function number : 80 Type of request : PROJ
Subaddress pos. : 13 Channel/interface : 1
Subaddress len. : 1 Cycle number : 128
Format name : CODE CARRIER DB/DX address : DB
DW address : 0
Log. destination : PAK 7
Permissible data length : 255

Function name : T CE SINUMERIK unit : PLC 1

Function number : 81 Type of request : PROJ
Subaddress pos. : 13 Channel/interface : 1
Subaddress len. : 1 Cycle number : 128
Format name : CODE CARRIER DB/DX address : DB
DW address : 0
Log. destination : PAK 7
Permissible data length : 255
Function name : T CB F SINUMERIK unit : PLC 1
Function number : 82 Type of request : PROJ
Subaddress pos. : 13 Channel/interface : 1
Subaddress len. : 1 Cycle number : 128
Format name : CODE CARRIER DB/DX address : DB
DW address : 0
Log. destination : PAK 7
Permissible data length : 255
Function name : R CE F SINUMERIK unit : PLC 1
Function number : 83 Type of request : PROJ
Subaddress pos. : 13 Channel/interface : 1
Subaddress len. : 1 Cycle number : 128
Format name : CODE CARRIER DB/DX address : DB
DW address : 0
Log. destination : PAK 7
Permissible data length : 255

5–6 © Siemens AG 1991 All Rights Reserved 6FC5 197-0AB40-0BP0

SINUMERIK 840/880 (PJ)
12.91 5 Application
5.3 Example

OUTPUT LIST

MASTER DATA PD_TYP PARAMETERS

Function name: T CB Repetition flag: 0

Function number: 80 Time inst: 0
Format name: CODE CARRIER Time resp: 0
Function name: R CE Repetition flag: 0
Function number: 81 Time inst: 0
Format name: CODE CARRIER Time resp: 0

Sample UI/log. destination assignment list

DB99:

UI DW-NR. High byte (DL) Low byte (DR)

: : : :
DW 5 P A
DW 6 K 7
UI 1 DW 7 C 0
DW 8 D E
DW 9 11
: : : :

Description:
User interface 1 is configured as follows:
DB 99: DW 5,6: Log. source "PAK7" (ASCII)
DW 7, 8: Log. destination "CODE" (ASCII)
DW 9: Receiver 11 (HEX.)
(e.g. 1st interface module = CP315)

© Siemens AG 1991 All Rights Reserved 6FC5 197-0AB40-0BP0 5–7

SINUMERIK 840/880 (PJ)
5 Application 11.92
5.3 Example

Example: Data description

The code carrier data for the example, the addresses for the various data items and their
formats are listed below:
T number: Requested unconditionally
Address: ”IN”
Format : BCD, fixed-point, unsigned
4 bytes (8 positions)
Duplo number: Requested unconditionally
Address: ”SN”
Format : BCD, fixed-point, unsigned
2 bytes (4 positions)
Tool size: Requested unconditionally
Address: ”P”
Format: BCD, fixed-point, unsigned
1 byte (2 positions; no. of half-locations behind/in front of
holder)
Status info: Requested conditionally
Address: ”V”
Format: BCD, fixed-point, unsigned
1 byte (2 positions)
No. of cutting Requested unconditionally
edges: Address: ”z”
Format: BCD, fixed-point, unsigned
1 byte (2 positions)
Cutting speed: User DB 1
Requested conditionally
Address ”v”
Format: BCD, fixed-point, unsigned
1 byte (2 positions)
Tool type: P memory 01
Requested unconditionally
Address: ”P0”
Format: BCD, fixed-point, unsigned
1 byte (2 positions)
Geometry 1: P memory 02
Requested conditionally
Address: ”d?”
Format: BCD, fixed-point, signed
5 bytes (10 positions, 3 decimal places)
Geometry 2: P memory 03
Requested conditionally
Address: ”l?”
Format: BCD, fixed-point, signed
5 bytes (10 positions, 3 decimal places)
Geometry 3: P memory 04
Requested conditionally
Address: ”r?”
Format: BCD, fixed-point, signed
5 bytes (10 positions, 3 decimal places)

5–8 © Siemens AG 1991 All Rights Reserved 6FC5 197-0AB40-0BP0

SINUMERIK 840/880 (PJ)
11.92 5 Application
5.3 Example

Offset 1: P memory 05
Requested conditionally
Address: ”D0?1”
Format: BCD, fixed-point, signed
4 Bytes (8 positions, 3 decimal places)
Offset 2: P memory 06
Requested conditionally
Address: "L0?1"
Format: BCD, fixed-point, signed
4 bytes (8 positions, 3 decimal places)

Offset 3: P memory 07
Requested conditionally
Address: "R0?1"
Format: BCD, fixed-point, signed
4 bytes (8 positions, 3 decimal places)

Tool life (set): P memory 10

Requested conditionally
Address: "S"
Format: BCD, fixed-point, signed
2 bytes (4 positions)

Tool life
(remaining): P memory 11
Requested conditionally
Address: "R"
Format: BCD, fixed-point, signed
3 bytes (6 positions)

Tool life
(warning limit): P memory 12
Requested conditionally
Address: "W"
Format: BCD, fixed-point, unsigned
2 bytes (4 positions)

Feed: P memory 14
Requested conditionally
Address: "s"
Format: BCD, fixed-point, unsigned
2 bytes (4 positions, 2 decimal places)

© Siemens AG 1991 All Rights Reserved 6FC5 197-0AB40-0BP0 5–9

SINUMERIK 840/880 (PJ)
5 Application 11.92
5.3 Example

Example: Address parameter list

DB126:
General section:
User DB: 7 6 5 4 3 2 1
15 07 06 05 04 03 02 01 00
DW 0: KM 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1
Activation bit string for user DBs 1 to 7

P15 P00
15 14 13 12 11 10 09 08 07 06 05 04 03 02 01 00
DW 1: KM 0 1 0 1 1 1 0 0 1 1 1 1 1 1 1 0
Activation bit string P00 - P15 for the first cutting edge

P15 P00
15 14 13 12 11 10 09 08 07 06 05 04 03 02 01 00
DW 3: KM 0 0 0 0 0 0 0 0 1 1 1 1 1 1 0 0
Activation bit string P0 - P15 for additional cutting edge(s)

DW 2: KH . . . 0 . . . Reserved
DW 4: KH . . . 0 . . . Reserved
DW 5 .. 9: KH . . . 0 . . . Reserved

5–10 © Siemens AG 1991 All Rights Reserved 6FC5 197-0AB40-0BP0

SINUMERIK 840/880 (PJ)
11.92 5 Application
5.3 Example

DW 10 KY ...1... ...2... T number Cond./uncond./ Address length

DW 11 KS ...I... ...N... Address (1) / Address (2)
DW 12 KS ...... ...... Address (3) / Address (4)
DW 13 KH ...31... ...04... Format ident. / Format par.
DW 14 KY ...1... ...2... Duplo number Cond./uncond./ Address length
DW 15 KS ...S... ...N... Address (1) / Address (2)
DW 16 KS ...... ...... Address (3) / Address (4)
DW 17 KH ...31... ...02... Format ident. / Format par.
DW 18 KY ...1... ...1... Tool size Cond./uncond./ Address length
DW 19 KS ...P... ...... Address (1) / Address (2)
DW 20 KS ...... ...... Address (3) / Address (4)
DW 21 KH ...31... ...01... Format ident. / Format par.
DW 22 KY ...0... ...1... Status info Cond./uncond./ Address length
DW 23 KS ...V... ...... Address (1) / Address (2)
DW 24 KS ...... ...... Address (3) / Address (4)
DW 25 KH ...31... ...01... Format ident. / Format par.
DW 26 KY ...1... ...1... No. of cutting edges Cond./uncond./ Address length
DW 27 KS ...z... ...... Address (1) / Address (2)
DW 28 KS ...... ...... Address (3) / Address (4)
DW 29 KH ...31... ...01... Format ident. / Format par.
DW 30 KY ...0... ...1... User DB 1 Cond./uncond./ Address length
DW 31 KS ...v... ...... Address (1) / Address (2)
DW 32 KS ...... ...... Address (3) / Address (4)
DW 33 KH ...31... ...01... Format ident. / Format par.
DW 34 KY ...0... ...0... User DB 2 Cond./uncond./ Address length
DW 35 KS ...... ...... Address (1) / Address (2)
DW 36 KS ...... ...... Address (3) / Address (4)
DW 37 KH ...... ...... Format ident. / Format par.
DW 38 KY ...0... ...0... User DB 3 Cond./uncond./ Address length
DW 39 KS ...... ...... Address (1) / Address (2)
DW 40 KS ...... ...... Address (3) / Address (4)
DW 41 KH ...... ...... Format ident. / Format par.
DW 42 KY ...0... ...0... User DB 4 Cond./uncond./ Address length
DW 43 KS ...... ...... Address (1) / Address (2)
DW 44 KS ...... ...... Address (3) / Address (4)
DW 45 KH ...... ...... Format ident. / Format par.
DW 46 KY ...0... ...0... User DB 5 Cond./uncond./ Address length
DW 47 KS ...... ...... Address (1) / Address (2)
DW 48 KS ...... ...... Address (3) / Address (4)
DW 49 KH ...... ...... Format ident. / Format par.
DW 50 KY ...0... ...0... User DB 6 Cond./uncond./ Address length
DW 51 KS ...... ...... Address (1) / Address (2)
DW 52 KS ...... ...... Address (3) / Address (4)
DW 53 KH ...... ...... Format ident. / Format par.
DW 54 KY ...0... ...0... User DB 7 Cond./uncond./ Address length
DW 55 KS ...... ...... Address (1) / Address (2)
DW 56 KS ...... ...... Address (3) / Address (4)
DW 57 KH ...... ...... Format ident. / Format par.

© Siemens AG 1991 All Rights Reserved 6FC5 197-0AB40-0BP0 5–11

SINUMERIK 840/880 (PJ)
5 Application 12.91
5.3 Example

DW 58 KY ...0... ...0... Reserved Cond./uncond./ Address length

DW 59 KS ...... ...... Address (1) / Address (2)
DW 60 KS ...... ...... Address (3) / Address (4)
DW 61 KH ...... ...... Format ident. / Format par.
DW 62 KY ...0... ...0... User Cond./uncond./ Address length
DW 63 KS ...... ...... (P0) Address (1) / Address (2)
DW 64 KS ...... ...... Address (3) / Address (4)
DW 65 KH ...... ...... Format ident. / Format par.
DW 66 KY ...1... ...2... Type Cond./uncond./ Address length
DW 67 KS ...P... ...0... (P1) Address (1) / Address (2)
DW 68 KS ...... ...... Address (3) / Address (4)
DW 69 KH ...31... ...01... Format ident. / Format par.
DW 70 KY ...0... ...2... Geometry 1 Cond./uncond./ Address length
DW 71 KS ...d... ...?... (P2) Address (1) / Address (2)
DW 72 KS ...... ...... Address (3) / Address (4)
DW 73 KH ...33... ...35... Format ident. / Format par.
DW 74 KY ...0... ...2... Geometry 2 Cond./uncond./ Address length
DW 75 KS ...l... ...?... (P3) Address (1) / Address (2)
DW 76 KS ...... ...... Address (3) / Address (4)
DW 77 KH ...33... ...35... Format ident. / Format par.
DW 78 KY ...0... ...2... Geometry 3 Cond./uncond./ Address length
DW 79 KS ...r... ...?... (P4) Address (1) / Address (2)
DW 80 KS ...... ...... Address (3) / Address (4)
DW 81 KH ...33... ...35... Format ident. / Format par.
DW 82 KY ...0... ...4... Offset 1 (dim.) Cond./uncond./ Address length
DW 83 KS ...D... ...0... (P5) Address (1) / Address (2)
DW 84 KS ...?... ...1... Address (3) / Address (4)
DW 85 KH ...33... ...34... Format ident. / Format par.
DW 86 KY ...0... ...4... Offset 2 (dim.) Cond./uncond./ Address length
DW 87 KS ...L... ...0... (P6) Address (1) / Address (2)
DW 88 KS ...?... ...1... Address (3) / Address (4)
DW 89 KH ...33... ...34... Format ident. / Format par.
DW 90 KY ...0... ...4... Offset 3 (dim.) Cond./uncond./ Address length
DW 91 KS ...R... ...0... (P7) Address (1) / Address (2)
DW 92 KS ...?... ...1... Address (3) / Address (4)
DW 93 KH ...33... ...34... Format ident. / Format par.
DW 94 KY ...0... ...0... Reserved Cond./uncond./ Address length
DW 95 KS ...... ...... (P8) Address (1) / Address (2)
DW 96 KS ...... ...... Address (3) / Address (4)
DW 97 KH ...... ...... Format ident. / Format par.
DW 98 KY ...0... ...0... Reserved Cond./uncond./ Address length
DW 99 KS ...... ...... (P9) Address (1) / Address (2)
DW 100 KS ...... ...... Address (3) / Address (4)
DW 101 KH ...... ...... Format ident. / Format par.
DW 102 KY ...0... ...1... User Cond./uncond./ Address length
DW 103 KS ...S... ...... (P10) Address (1) / Address (2)
DW 104 KS ...... ...... Address (3) / Address (4)
DW 105 KH ...31... ...02... Format ident. / Format par.

5–12 © Siemens AG 1991 All Rights Reserved 6FC5 197-0AB40-0BP0

SINUMERIK 840/880 (PJ)
11.92 5 Application
5.3 Example

DW 106 KY ...0... ...1... User Cond./uncond./ Address length

DW 107 KS ...R... ...... (P11) Address (1) / Address (2)
DW 108 KS ...... ...... Address (3) / Address (4)
DW 109 KH ...33... ...03... Format ident. / Format par.
DW 110 KY ...0... ...1... User Cond./uncond./ Address length
DW 111 KS ...W... ...... (P12) Address (1) / Address (2)
DW 112 KS ...... ...... Address (3) / Address (4)
DW 113 KH ...31... ...02... Format ident. / Format par.
DW 114 KY ...0... ...0... User Cond./uncond./ Address length
DW 115 KS ...... ...... (P13) Address (1) / Address (2)
DW 116 KS ...... ...... Address (3) / Address (4)
DW 117 KH ...... ...... Format ident. / Format par.
DW 118 KY ...0... ...1... User Cond./uncond./ Address length
DW 119 KS ...s... ...... (P14) Address (1) / Address (2)
DW 120 KS ...... ...... Address (3) / Address (4)
DW 121 KH ...31... ...22... Format ident. / Format par.
DW 122 KY ...0... ...0... User Cond./uncond./ Address length
DW 123 KS ...... ...... (P15) Address (1) / Address (2)
DW 124 KS ...... ...... Address (3) / Address (4)
DW 125 KH ...... ...... Format ident. / Format par.

© Siemens AG 1991 All Rights Reserved 6FC5 197-0AB40-0BP0 5–13

SINUMERIK 840/880 (PJ)
5 Application 12.91
5.3 Example

Example: Source data blocks for loading/unloading user data

The "Read" request for user data is in DB230. The request is formulated to read the machine
number and the job number from the code carrier chip.
The "Write" request for user data is in DB231. The request is formulated to write the machine
number and the job number to the code carrier chip.
The structure of these data blocks is described in detail in Sections 3.1 and 3.2 (refer to
"Package 7: Code Carrier Requests" for further details).

Data block structure:

DB230

0: KF=+00020; Length specification for user interface

1: KF=+00020; Length specification for data
2: KH=3101; Subaddress (station "1") / Head number
3: KH=4400; Identifier ”D” / Info field =0
4: KH=0000; Info field=0 / Res. byte =0
5: KH=0002; No. of addr. ”NAR”=0 / No. of addr. ”NAT”
6: KH=014A;
7: KH=3103; Address block 1 (machine number)
8: KH=0001;
9: KH=5131;
10: KH=0400; Address block 2 (job number)
11:

DB231:

0: KF=+00028; Length specification for user interface

1: KF=+00028; Length specification for data
2: KH=3101; Subaddress (station ”1”) / Head number
3: KH=4400; Identifier ”D” / Info field =0
4: KH=0000; Info field=0 / Res.byte =0
5: KH=0002; No. of addr. ”NAR”=0 / No. of addr. ”NAT”
6: KH=014A;
7: KH=3103;
8: KH=0812; Address block 1 (machine number)
9: KH=3456;
10: KH=0151;
11: KH=3104;
12: KH=0812;
13: KH=3456; Address block 2 (job number)
14: KH=7800;
15:

5–14 © Siemens AG 1991 All Rights Reserved 6FC5 197-0AB40-0BP0

SINUMERIK 840/880 (PJ)
12.91 5 Application
5.3 Example

Example: Program
Load/unload tools via code carrier

Signal descriptions:
FY 200: Magazine number
FW 208: Magazine location
FY 202: Number of the encoding station
FY 203: Number of the read/write head
FY 204: Status info for unload

I 14.0: B-WZ (load tool data)

I 14.1: B-AW (load user data)
I 14.2: LADE (load at magazine location)
I 14.3: F-LP (error during vacant location search, abort)
I 14.4: WZIM (tool in magazine)
I 14.5: FBEL (error while loading tool into magazine, abort)
I 14.6: E-WZ (unload tool data)
I 14.7: E-AW (unload user data)

Q 4.0: F (load error)

Q 4.1: F (unload error)
Q 4.2: ANWB (load: receive user data in DB128)
Q 4.3: ANWE (unload: receive user data in DB128)
Q 4.4: LP-S (load: enable signal for vacant location search
Q 4.5: W-IN (load: tool in magazine?)
Q 4.6: PLLO (unload: delete location)

Q 3.0: AKT (loading in progress)

Q 3.1: AKT (unloading in progress)

QB 5: WZGR (load: tool size)

QB 6: ZK-B (load: status info)

© Siemens AG 1991 All Rights Reserved 6FC5 197-0AB40-0BP0 5–15

SINUMERIK 840/880 (PJ)
5 Application 12.91
5.3 Example

Structure of the program for the example:

OB 1
PB 119 FB 139
DAT-VERT

PB 120 FX 14
BEL-CDTR

FX 15
ENT-CDTR

OB 20
PB 121

OB 1
SEGMENT 1
:
: JU PB119 PACKAGE 1: DATA DISTRIBUTOR
: JU PB120 PACKAGE 7: CODE CARRIER
:
: BE

OB 20
SEGMENT 1
:
: JU FB121 INITIALIZE MD/DB131
:
: BE

PB119
SEGMENT 1
:
: JU FB139 DATA DISTRIBUTOR FOR ENTERING
NAME : DAT-VERT DATA IN AND FETCHING DATA FROM
: THE 880 TOOL MANAGEMENT’S
: BE DYNAMIC INTERFACE DBs

5–16 © Siemens AG 1991 All Rights Reserved 6FC5 197-0AB40-0BP0

SINUMERIK 840/880 (PJ)
12.91 5 Application
5.3 Example

PB121
SEGMENT 1
:
: JU FB11 INITIALIZE DB131:
NAME : EINR-DB DB FOR MACHINE DATA WORDS
DBAN : KY 131,1
DWNR : KF +2
DBTY : KS DB
:
: C DB131 MD WORDS:
: L KY 4,1 WZYK=4 (AMOUNT TOOL DATA/CYCLE)
: T DW 0 TUE=1 (TIMER FOR PACKAGE 7)
: L KY 230,0 DBQB=230 (USER DATA DB LOAD)
: T DW 1 DWQB (USER DATA DW LOAD)
: L KY 231,0 DBQE=231 (USER DATA DB UNLOAD)
: T DW 2 DWQE=0 (USER DATA DW UNLOAD)
:
: BE

© Siemens AG 1991 All Rights Reserved 6FC5 197-0AB40-0BP0 5–17

SINUMERIK 840/880 (PJ)
5 Application 12.91
5.3 Example

PB120
SEGMENT 1
:
: L KB 1
: T FY 200 MANR=1
: T FW 208 PLNR=1
: T FY 202 STAT=1
: T FY 203 LSKP=1
: L KB 7
: T FY 204 Z-KE=7
:
: =======================
: DO FX 14 LOAD VIA CODE CARRIER
NAME : BEL-CDTR =======================
B-WZ : I 14.0 LOAD TOOL DATA
B-AW : I 14.1 LOAD USER DATA
LADE : I 14.2 TOOL DATA IN MAGAZINE TABLE
F-LP : I 14.3 ERROR DURING VACANT LOCATION SEARCH
WZIM : I 14.4 TOOL IN MAGAZINE
FBEL : I 14.5 LOAD ERROR
MANR : FY 200 MAGAZINE NUMBER
PLNR : FW 208 MAGAZINE LOCATION NUMBER
STAT : FY 202 NUMBER OF THE ENCODING STATION
LSKP : FY 203 NUMBER OF THE READ/WRITE HEAD
WZGR : QB 5 TOOL SIZE
ZK-B : QB 6 STATUS INFO FOR LOAD
ANWB : Q 4.2 RECEIVE DATA IN DB128
WZ-IN : Q 4.5 TOOL IN MAGAZINE ???
LP-S : Q 4.4 ENABLE FOR VACANT LOCATION SEARCH
AKT : Q 3.0 BLOCK EXECUTING
F : Q 4.0 ERROR
:
:
: =======================
: DO FX 15 UNLOAD VIA CODE CARRIER
NAME : ENT-CDTR =======================
E-WZ : I 14.6 LOAD TOOL DATA
E-AW : I 14.7 UNLOAD USER DATA
MANR : FY 200 MAGAZINE NUMBER
PLNR : FW 208 MAGAZINE LOCATION NUMBER
STAT : FY 202 NUMBER OF THE ENCODING STATION
LSKP : FY 203 NUMBER OF THE READ/WRITE HEAD
ZK-E : FY 204 STATUS INFO FOR UNLOAD
ANWE : Q 4.3 RECEIVE DATA IN DB128
PLLO : Q 4.6 DELETE LOCATION
AKT : Q 3.1 BLOCK EXECUTING
F : Q 4.1 ERROR
:
:
: BE

5–18 © Siemens AG 1991 All Rights Reserved 6FC5 197-0AB40-0BP0

SINUMERIK 840/880 (PJ)
11.92 6 Configuring Lists

6 Configuring Lists

The next several pages contain the configuring data for the address parameter list (based on
the tool data record structure used by Mercedes-Benz): . Among other things, the T number is
addressed via the parameter ”TN” and is limited to 6 places.

Example: Address parameter list CONFIGURING LIST

DB126: DATE: ..........................

PROJECT: ..........................
NAME: ..........................

General section:
User DB: 7 6 5 4 3 2 1
15 07 06 05 04 03 02 01 00
DW 0: KM 0 0 0 0 0 0 0 0 0
Activation bit string for user DBs 1 to 7

P15 P00
15 14 13 12 11 10 09 08 07 06 05 04 03 02 01 00
DW 1: KM
Activation bit string P00 - P15 for first cutting edge

P15 P00
15 14 13 12 11 10 09 08 07 06 05 04 03 02 01 00
DW 3: KM 0 0
Activation bit string P00 - P15 for additional cutting edge(s)

DW 2: KH . . . 0 . . . Reserved
DW 4 .. 9: KH . . . 0 . . . Reserved

© Siemens AG 1991 All Rights Reserved 6FC5 197-0AB40-0BP0 6–1

SINUMERIK 840/880 (PJ)
6 Configuring Lists 12.91

DW 10 KY ...1... ...2... T number Cond./uncond./ Address length

DW 11 KS ...T... ...N... Address (1) / Address (2)
DW 12 KS ...... ...... Address (3) / Address (4)
DW 13 KH ...31... ...03... Format ident. / Format par.
DW 14 KY ...1... ...2... Duplo number Cond./uncond./ Address length
DW 15 KS ...S... ...N... Address (1) / Address (2)
DW 16 KS ...... ...... Address (3) / Address (4)
DW 17 KH ...31... ...02... Format ident. / Format par.
DW 18 KY ...1... ...... Tool size Cond./uncond./ Address length
DW 19 KS ...... ...... Address (1) / Address (2)
DW 20 KS ...... ...... Address (3) / Address (4)
DW 21 KH ...31... ...01... Format ident. / Format par.
DW 22 KY ...... ...... Status info Cond./uncond./ Address length
DW 23 KS ...... ...... Address (1) / Address (2)
DW 24 KS ...... ...... Address (3) / Address (4)
DW 25 KH ...31... ...01... Format ident. / Format par.
DW 26 KY ...1... ...... No. of cutting edges Cond./uncond./ Address length
DW 27 KS ...... ...... Address (1) / Address (2)
DW 28 KS ...... ...... Address (3) / Address (4)
DW 29 KH ...31... ...01... Format ident. / Format par.
DW 30 KY ...... ...... User DB 1 Cond./uncond./ Address length
DW 31 KS ...... ...... Address (1) / Address (2)
DW 32 KS ...... ...... Address (3) / Address (4)
DW 33 KH ...... ...... Format ident. / Format par.
DW 34 KY ...... ...... User DB 2 Cond./uncond./ Address length
DW 35 KS ...... ...... Address (1) / Address (2)
DW 36 KS ...... ...... Address (3) / Address (4)
DW 37 KH ...... ...... Format ident. / Format par.
DW 38 KY ...... ...... User DB 3 Cond./uncond./ Address length
DW 39 KS ...... ...... Address (1) / Address (2)
DW 40 KS ...... ...... Address (3) / Address (4)
DW 41 KH ...... ...... Format ident. / Format par.
DW 42 KY ...... ...... User DB 4 Cond./uncond./ Address length
DW 43 KS ...... ...... Address (1) / Address (2)
DW 44 KS ...... ...... Address (3) / Address (4)
DW 45 KH ...... ...... Format ident. / Format par.
DW 46 KY ...... ...... User DB 5 Cond./uncond./ Address length
DW 47 KS ...... ...... Address (1) / Address (2)
DW 48 KS ...... ...... Address (3) / Address (4)
DW 49 KH ...... ...... Format ident. / Format par.
DW 50 KY ...... ...... User DB 6 Cond./uncond./ Address length
DW 51 KS ...... ...... Address (1) / Address (2)
DW 52 KS ...... ...... Address (3) / Address (4)
DW 53 KH ...... ...... Format ident. / Format par.
DW 54 KY ...... ...... User DB 7 Cond./uncond./ Address length
DW 55 KS ...... ...... Address (1) / Address (2)
DW 56 KS ...... ...... Address (3) / Address (4)
DW 57 KH ...... ...... Format ident. / Format par.

6–2 © Siemens AG 1991 All Rights Reserved 6FC5 197-0AB40-0BP0

SINUMERIK 840/880 (PJ)
12.91 6 Configuring Lists

DW 58 KY ...0... ...0... Reserved Cond./uncond./ Address length

DW 59 KS ...... ...... Address (1) / Address (2)
DW 60 KS ...... ...... Address (3) / Address (4)
DW 61 KH ...... ...... Format ident. / Format par.
DW 62 KY ...... ...... User Cond./uncond./ Address length
DW 63 KS ...... ...... (P0) Address (1) / Address (2)
DW 64 KS ...... ...... Address (3) / Address (4)
DW 65 KH ...... ...... Format ident. / Format par.
DW 66 KY ...1... ...... Type Cond./uncond./ Address length
DW 67 KS ...... ...... (P1) Address (1) / Address (2)
DW 68 KS ...... ...... Address (3) / Address (4)
DW 69 KH ...... ...... Format ident. / Format par.
DW 70 KY ...... ...... Geometry 1 Cond./uncond./ Address length
DW 71 KS ...... ...... (P2) Address (1) / Address (2)
DW 72 KS ...... ...... Address (3) / Address (4)
DW 73 KH ...... ...... Format ident. / Format par.
DW 74 KY ...... ...... Geometry 2 Cond./uncond./ Address length
DW 75 KS ...... ...... (P3) Address (1) / Address (2)
DW 76 KS ...... ...... Address (3) / Address (4)
DW 77 KH ...... ...... Format ident. / Format par.
DW 78 KY ...... ...... Geometry 3 Cond./uncond./ Address length
DW 79 KS ...... ...... (P4) Address (1) / Address (2)
DW 80 KS ...... ...... Address (3) / Address (4)
DW 81 KH ...... ...... Format ident. / Format par.
DW 82 KY ...... ...... Offset 1 (dim.) Cond./uncond./ Address length
DW 83 KS ...... ...... (P5) Address (1) / Address (2)
DW 84 KS ...... ...... Address (3) / Address (4)
DW 85 KH ...... ...... Format ident. / Format par.
DW 86 KY ...... ...... Offset 2 (dim.) Cond./uncond./ Address length
DW 87 KS ...... ...... (P6) Address (1) / Address (2)
DW 88 KS ...... ...... Address (3) / Address (4)
DW 89 KH ...... ...... Format ident. / Format par.
DW 90 KY ...... ...... Offset 3 (dim.) Cond./uncond./ Address length
DW 91 KS ...... ...... (P7) Address (1) / Address (2)
DW 92 KS ...... ...... Address (3) / Address (4)
DW 93 KH ...... ...... Format ident. / Format par.
DW 94 KY ...0... ...0... Reserved Cond./uncond./ Address length
DW 95 KS ...... ...... (P8) Address (1) / Address (2)
DW 96 KS ...... ...... Address (3) / Address (4)
DW 97 KH ...... ...... Format ident. / Format par.
DW 98 KY ...0... ...0... Reserved Cond./uncond./ Address length
DW 99 KS ...... ...... (P9) Address (1) / Address (2)
DW 100 KS ...... ...... Address (3) / Address (4)
DW 101 KH ...... ...... Format ident. / Format par.
DW 102 KY ...... ...... User Cond./uncond./ Address length
DW 103 KS ...... ...... (P10) Address (1) / Address (2)
DW 104 KS ...... ...... Address (3) / Address (4)
DW 105 KH ...... ...... Format ident. / Format par.

© Siemens AG 1991 All Rights Reserved 6FC5 197-0AB40-0BP0 6–3

SINUMERIK 840/880 (PJ)
6 Configuring Lists 11.92

DW 106 KY ...... ...... User Cond./uncond./ Address length

DW 107 KS ...... ...... (P11) Address (1) / Address (2)
DW 108 KS ...... ...... Address (3) / Address (4)
DW 109 KH ...... ...... Format ident. / Format par.
DW 110 KY ...... ...... User Cond./uncond./ Address length
DW 111 KS ...... ...... (P12) Address (1) / Address (2)
DW 112 KS ...... ...... Address (3) / Address (4)
DW 113 KH ...... ...... Format ident. / Format par.
DW 114 KY ...... ...... User Cond./uncond./ Address length
DW 115 KS ...... ...... (P13) Address (1) / Address (2)
DW 116 KS ...... ...... Address (3) / Address (4)
DW 117 KH ...... ...... Format ident. / Format par.
DW 118 KY ...... ...... User Cond./uncond./ Address length
DW 119 KS ...... ...... (P14) Address (1) / Address (2)
DW 120 KS ...... ...... Address (3) / Address (4)
DW 121 KH ...... ...... Format ident. / Format par.
DW 122 KY ...... ...... User Cond./uncond./ Address length
DW 123 KS ...... ...... (P15) Address (1) / Address (2)
DW 124 KS ...... ...... Address (3) / Address (4)
DW 125 KH ...... ...... Format ident. / Format par.

6–4 © Siemens AG 1991 All Rights Reserved 6FC5 197-0AB40-0BP0

SINUMERIK 840/880 (PJ)
SINUMERIK 840/840C
SINUMERIK 880/880 GA2
PLC 135 WB/WB2 Function Blocks
Package 7: Code Carriers
Part 2: Frame Description
Overview 1

Basic Principles 2

Frames 3

Frame Sequences 4

Closing Remarks 5

Appendix 6
12.91 1 Overview

1 Overview

General remarks:
Tool data carriers affixed to the tools or tool holder are used for automatic loading/unloading of
computer-controlled machine tools. Tool-specific information such as geometry data, and
factory-related data such as the machine number, is stored on these data carriers.
Daimler Benz has submitted a proposal to DIN for standardizing data volume, data distribution
and addressing on the data carrier. This proposal is based on the data volume required at
Daimler Benz, and is already being used by Daimler in their automated manufacturing plants.
Data is read from/written to the data carriers via encoding stations, which in turn are connected
over serial interfaces to the CNC. Secure data link protocols are used for data interchange
between encoding station and CNC.

© Siemens AG 1991 All Rights Reserved 6FC5 197-0AB40-0BP0 1–1

SINUMERIK 840/880 (PJ)
12.91 2 Basic Principles
2.1 Data interchange

2 Basic Principles

2.1 Data interchange

The diagram below provides a rough overview of how data is passed from the code carrier
system’s evaluator to the Sinumerik 880 and vice versa.
Data is interchanged over the active RS 232 C (V.24) interface. Please refer to the relevant
computer link software manual(s) for details on configuring the interface module.
The Sinumerik 880 system and the code carrier system interchange data according to specific
rules. In addition to the procedure, the requests/responses must conform to prescribed
conventions.

Max. 8 read/
write heads
.........

Code carrier system

Hardware signal
3964R/LSV2
for load/unload
line procedure

PLC I/O CP
Active RS 232 C
(V.24) interface

Multi-port
RAM

NC COM

2.2 Procedure
The active RS 232 C (V.24) interface assembles the data in the form required by the relevant
procedure. The 3964R or LSV2 procedure is used for the link to the code carrier system.
The data frame consists of a procedure-specific header and the data.
Please refer to the applicable user’s guide for detailed information on the line procedures.

© Siemens AG 1991 All Rights Reserved 6FC5 197-0AB40-0BP0 2–1

SINUMERIK 840/880 (PJ)
2 Basic Principles 11.92
2.3 Frame data

2.3 Frame data

A frame always contains the frame length, the frame identification, an error code and useful
data.
aaaaaaaaaaaaaaaaaaaaaaaaaaaa
aaaaaaaaaaaaaaaaaaaaaaaaaaaa
aaaaaaaaaaaaaaaaaaaaaaaaaaaa
aaaaaaaaaaaaaaaaaaaaaaaaaaaa
aaaaaaaaaaaaaaaaaaaaaaaaaaaa
aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
aaaaaaaaaaaaaaaaaaaaaaaaaaaa
aaaaaaaaaaaaaaaaaaaaaaaaaaaa
aaaaaaaaaaaaaaaaaaaaaaaaaaaa
aaaaaaaaaaaaaaaaaaaaaaaaaaaa
Header Length Frame Error code Useful data
identification
(2 bytes) (8 bytes) (2 bytes) (max. 244* bytes)

2.3.1 Frame length

The frame length in bytes (in hexadecimal format) precedes the frame identification.
The length is computed by adding the number of bytes required for frame identification and
error code (always 10) and the number of bytes of useful data (max. 244* bytes).
A frame may therefore have a maximum length of 254 bytes.

2.3.2 Frame identification

The frame identification always comprises 8 characters (ASCII format).
The characters in the frame identification are described in detail below (also refer to the
"Frames" section in the Sinumerik 880 computer link manual.

Identification characters
a
a
a
a
a
a
aa
a
a
a
a
a
a
a
aa
a
a
a
a
a
a
a
aa
a
a
a
a
a
a
a
aa
a
a
a
a
a
a
a
aa
a
a
a
a
a
a
a
aa
a
a
a
a
a
a
a
aa
a
a
a
a
a
a
a
aa
a
aaaaaa
a
a
a
a
a
a
a
a
aa
a
a
a
a
a
a
aa
a
a
a
a
a
a
aa
a
a
a
a
a
a
aa
a
a
a
a
a
a
aa
a
a
a
a
a
a
aa
a
a
a
a
a
a
aa
a
a
a
a
a
a
aa
1 2 3 4 5 6 7 8
a
a
a
a
a
a
a
aa
a
a
a
a
a
a
aa
a
a
a
a
a
a
aa
a
a
a
a
a
a
aa
a
a
a
a
a
a
aa
a
a
a
a
a
a
aa
a
a
a
a
a
a
aa
a
a
a
a
a
a
aa
a
a
a
a
a
a
a
aa
a
a
a
a
a
a
aa
a
a
a
a
a
a
aa
a
a
a
a
a
a
aa
a
a
a
a
a
a
aa
a
a
a
a
a
a
aa
a
a
a
a
a
a
aa
a
a
a
a
a
a
aa
a
a
a
a
a
a
a
aa
a
a
a
a
a
a
aa
a
a
a
a
a
a
aa
a
a
a
a
a
a
aa
a
a
a
a
a
a
aa
a
a
a
a
a
a
aa
a
a
a
a
a
a
aa
a
a
a
a
a
a
aa
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a
a

Command identifier
Error identifier
Subgroup identifier
Localization identifier

Commmand identifier (characters 1 to 5):

First character:
The first character defines the type of command
C (Command) = Command call
Q (Acknowledgement) = Acknowledgement (request serviced)
P (Prepare) = Prepare request
R (Receive) = Receive request
T (Transmit) = Send request

_______
* Some code carrier systems are limited to 224 bytes.

2–2 © Siemens AG 1991 All Rights Reserved 6FC5 197-0AB40-0BP0

SINUMERIK 840/880 (PJ)
12.91 2 Basic Principles
2.3.2 Frame identification

Error identifier (character 6):

F (Error) = When a request cannot be serviced or contains errors, it is returned to the
transmitter (e.g. the host computer, PLC or code carrier system) with an
"F" in the error identifier field (6th character) and a detailed error code.
Otherwise blank (space)

Subgroup identifier (character 7):

During a dialog, it must be possible to distinguish each frame from every other frame. The
seventh character in the frame identification is a subgroup indicator which enables
differentiation between identical frames passed during the same dialog.

Localization ID (character 8):

The eighth character in the frame identification specifies the mode group. When the mode
group is 0, the frame applies for all mode groups.
In the event of an alarm or interrupt, the eighth character is either a "P" (for PLC interrupt) or
an "N" (for an NC alarm).
Eighth character:
g = Number of the mode group (0 to 8)
N (NC alarms) = Flags an NC alarm
P (PLC interrupts) = Flags a PLC interrupt
Otherwise blank (space)

2.3.3 Error codes

The following conventions apply as regards rejection of frames and error codes:
A spaceholder is reserved in all frames for an error code (fnr). The space for an error code is
located between the frame identification and the useful data, and comprises two bytes (bytes
11 and 12).
The error code is in word format (fixed-point; positive values only; value range 0 to 9999
decimal = 0 to 270F hexadecimal).
An "F" as sixth character in the frame identification identifies an error frame. When a so-called
F frame is transmitted, the error code is entered in one or more specific data areas to enable
error analysis. When the sixth character in the frame identification is a space (or blank), the
error code must always be zero.
Every frame can be returned to the transmitter with an "F" as sixth character in the frame
identification (i.e. frame rejected), but a frame with an "F" identifier is not retransmitted as
error frame.

© Siemens AG 1991 All Rights Reserved 6FC5 197-0AB40-0BP0 2–3

SINUMERIK 840/880 (PJ)
 2 Basic Principles 12.91
2.3.4 Useful data

2.3.4 Useful data

In addition to frame identification and error code, most frames also contain useful data.
The number of bytes of useful data cannot exceed 244. Useful data for package 7 ("Code
Carriers: Transfer Tool Data with Address Encoding") is described in detail in Section 3 of this
manual.

2.3.5 Function numbers for requests

The function blocks for loading and unloading via code carrier require that the function
numbers for the code carrier requests be stored in machine data words (DB61, DW90/91).
Function numbers need be configured only for the first input and the first output request. Each
subsequent input and output request is assigned the next higher function number. A
subaddress must also be configured (see Section 3).

Assignments:
DB61/DW90: 1st input request = function no. ”n”: R_CB__
2nd input request = function no. ”n+1”: T_CE__
3rd input request = function no. ”n+2”: T_CB_F
4th input request = function no. ”n+3”: R_CE_F
DB61/DW91: 1st output request = function no. ”k”: T_CB__
2nd output request = function no. ”k+1”: R_CE__
k and n are numerical values (as per the configuring data on the interface
module)
_ represents a blank or space
a
a
a
a
aaaaaaaaaaaaaaaaaaa
a

a
a
a
a
aaaa
a
a
a
a
a
a

a
a
a
a
a
a
a
a
a
a

a
a
a
a
a
a
a
a
a
a

a
a
a
a
a
When configuring these requests, it is important to make sure that the
a
a
a
a
a

a
a
a
a
a
a
a
aaaaaaaaaaa
a
a
a
a
a
a
a

a
a
a
a
a
a
a
a
a
a
a
a
a
a

a
a
a
a
a
a
a
a
a
a
a
a
a
a

a
a
a
a
a
a
a
a
a
a
a
a
a
a

a
a
a
a
a
a
a
a
a
a
a
a
a
a

a
a
a
a
a
a
a
function numbers of the first input/output request are entered in the
a
a
a
a
a
a
a

a
a
a
a
a
a
a
a
a
a
a
a
a
a

a
a
a
a
a
a
a
a
a
a
a
a
a
a

a
a
a
a
a
a
a
a
a
a
a
a
a
a

a
a
a
a
a
a
a
a
a
a
a
a
a
a

a
a
a
a
a
aaaaa
a
a
a
a
a
a

a
a
a
a
a
machine data DB61, DW90 and DW91 .
a
a
a
a
a

a
a
a
a
a
a
a
a
a
a

a
a
a
a
a
a
a
a
a
a

a
a
a
a
a

2–4 © Siemens AG 1991 All Rights Reserved 6FC5 197-0AB40-0BP0

SINUMERIK 840/880 (PJ)
 1
aaaaaaaaaaaaaaaa aaaaaaaa
aaaaaaaa
3

21
18
aaaaaaaaaaaaaaaa aaaaaaaa

3.1
aaaaaaa

first.

Byte
12.91

aaaaaaaaaaaaaaaa aa
a

Byte

L. 1
Byte
aa
aaa
aa
aa
aa
aaa

Res.
aaaaaaaaaaaaaaaa aaaaaaaa

edge).

Addr.
aaaaaaaa

station.

1 byte
1 byte
aaaaaaaaaaaaaaaa aaaaaaaa
aaaaaaaa

10 bytes
aaaaaaaaaaaaaaaa aaaaaaaa
aaaaaaaaaaaaaaaa aaaaaaa
aa
a

error code
aaaaaaaaaaaaaaaa aa
aaa
aa
aa
aa
aaa
aaaaaaaaaaaaaaaa a
aa
aa
aa
aa
aa
aa
aa
a
aaaaaaaaaaaaaaaa a
aa
aa
aa
aa
aa
aa
aa
a
a
aa
aa
aa
aa
aa
aa
aa
a

© Siemens AG 1991
aaaaaaaaaaaaaaaa aaaaaaaa

Identification and
aaaaaaaa

?
aaaaaaaaaaaaaaaa aaaaaaaa
aaaaaaaa

Addr. 1

SINUMERIK 840/880 (PJ)

aaaaaaaaaaaaaaaa aaaaaaaa
aaaaaaaaaaaaaaaa a
aa
aa
aa
aa
aa
aa
aa
a
aaaaaaa
Frames

aaaaaaaaaaaaaaaa aa
a

19
aa
aaa
aa
aa
aa
aaa

11
aaaaaaaaaaaaaaaa aaaaaaaa
aaaaaaaaaaaaaaaa a
aa
aa
aa
aa
aa
aa
aa
a

F1
NAR
aaaaaaaaaaaaaaaa a
aa
aa
aa
aa
aa
aa
aa
a

1 byte
aaaaaaa

length
aaaaaaaaaaaaaaaa aa aa
a
aaa
aa
aa
aa
aaa

2 bytes
the encoding of the data carrier.

aaaaaaaaaaaaaaaa aaaaaaaa

2 bytes
the data into the relevant format.

aaaaaaaa

Address block 1

All Rights Reserved

aaaaaaaaaaaaaaaa aaaaaaaa
aaaaaaaaaaaaaaaa a
aa
aa
aa
aa
aa
aa
aa
a

Useful data
aaaaaaaaaaaaaaaa a
aa
aa
aa
aa
aa
aa
aa
a
aaaaaaaa

20
aaaaaaaaaaaaaaaa aaaaaaaa
aaaaaaaaaaaaaaaa a
aa
aa
aa
aa
aa
aa
aa
a
aaaaaaaa

stat.
NAT
No. of addr.
aaaaaaaaaaaaaaaa aaaaaaaa
aaaaaaa

1 byte

1 byte
aaaaaaaaaaaaaaaa aa
a

Addr. 1
aa
aaa
aa
aa
aa
aaa

13
aaaaaaaaaaaaaaaa aaaaaaaa
aaaaaaaaaaaaaaaa a
aa
aa
aa
aa
aa
aa
aa
a
aaaaaaaaaaaaaaaa a
aa
aa
aa
aa
aa
aa
aa
a

1 byte
aaaaaaaaaaaaaaaa aa
aaaaaaa
aa
a
aaaaaaaaaaaaaaaa aaa
aa
aa
aa
aaa

Subaddr.

L. 2
aaaaaaaaaaaaaaaa
Format: (not including the frame length specification)

Addr.
aaaaaaaaaaaaaaaa

1 byte

6FC5 197-0AB40-0BP0
aaaaaaaaaaaaaaaa

14
aaaaaaaaaaaaaaaa
aaaaaaaaaaaaaaaa
"Read" request: CNC encoding station

1 byte
aaaaaaaaaaaaaaaa
aaaaaaaaaaaaaaaa

Head no.
aaaaaaaaaaaaaaaa
aaaaaaaaaaaaaaaa

?
aaaaaaaaaaaaaaaa

Addr. 2
15

aaaaaaaaaaaaaaaa
aaaaaaaaaaaaaaaa
aaaaaaaaaaaaaaaa

1 byte
aaaaaaaaaaaaaaaa
Identifier

F2
aaaaaaaaaaaaaaaa
aaaaaaaaaaaaaaaa
aaaaaaaaaaaaaaaa

2 bytes
aaaaaaaaaaaaaaaa
16

Address block 2
aaaaaaaaaaaaaaaa
aaaaaaaaaaaaaaaa
2 byte

aaaaaaaaaaaaaaaa
Info field

aaaaaaaaaaaaaaaa
aaaaaaaaaaaaaaaa

stat-
One cycle is required for each cutting edge (i.e. one request and one response per cutting

aaaaaaaaaaaaaaaa

1 byte
The SINUMERIK processes some tool data in BCD, some in fixed-point, and some in ASCII

Addr. 2
aaaaaaaaaaaaaaaa
format. The objective was to have the encoding station, rather than the SINUMERIK, convert

A dialog was therefore implemented between the SINUMERIK and the encoding station which

aaaaaaaaaaaaaaaa
In all SINUMERIK-encoding station dialogs, the high-order bytes of data words are transmitted
3.1 "Read" request: CNC encoding station

The SINUMERIK always takes the initiative in a dialog by forwarding a request to the encoding
takes into account the SINUMERIK’s data processing and addressing characteristics as well as

aaaaaaaaaaaaaaaa
3 Frames

3–1
aaaaaaaaaaaaaaaa
3 Frames 11.92
3.1 ”Read” request: CNC encoding station

..................................................

Additional address blocks, if any

Identification and error code:

An identifier was defined as per the conventions for the SINUMERIK 850/880 computer link
software (see Section 3.11) which identifies the frame as a "Read" request.
The addresses to which the data is to be read from the code carrier are specified in the useful
data field.

Useful data length: (in bytes)

Specifies the length of the frame in bytes, including the length specification itself, i.e. the
length of the frame, not including the identification and error code fields.
The useful data (not including identification and error code) cannot exceed 244 bytes.
Format: 1 word (hexadecimal)
Note: The high-order byte is transferred first.

Subaddress:
The subaddress is used to identify one of the up to four encoding stations which can be
connected to the SINUMERIK over the CP315/373’s serial interfaces.
Format: 1 byte ASCII
Value range: 1 to 4 (ASCII)
The subaddress must be configured in the input lists on the interface module (CP). If more
than one encoding station is interfaced, the frames for each station must be configured with
the relevant subaddress (subaddress = number of the encoding station, an ASCII value
between 1 and 4) in the input lists on the interface module (also refer to Package 7: "Code
Carriers, Transfer Tool Data with Address Encoding").

Head number:
Each encoding station may be equipped with up to eight read/write heads. The head number
identifies one of the encoding station’s read/write heads.
Format: 1 byte BCD
Value range: 1 to 8

Identifier:
The identifier specifies the tool data record to be used by the encoding station.
Character for tool data record as per DIN proposal: "D"
Format: 1 byte (ASCII)

3–2 © Siemens AG 1991 All Rights Reserved 6FC5 197-0AB40-0BP0

SINUMERIK 840/880 (PJ)
12.91 3 Frames
3.1 ”Read” request: CNC encoding station

Info field:
The 16-bit info field is used to return information on events which require no error frame, as an
error frame would abort the dialog.
The codes are established by the manufacturer of the encoding station!
Format: 2 bytes (hexadecimal)

No. of addr. (number of addresses:

NAT: Number of address format (data) blocks:
This specification refers to the number of addresses in the useful data field in the
"Read" request, i.e. the number of addresses "to be read".
Format: 1 byte (hexadecimal)
NAR: Number of addresses (successfully) processed:
This specification refers to the number of addresses actually read.
Value in "Read" request: 00 (hexadecimal)
Format: 1 byte (hexadecimal)

Reserve:
This byte is held in reserve for future expansion.

Addr. L (address length):

Specifies the length, in bytes, of the address field that follows.
Format: 1 byte (hexadecimal)

Addr. x (address):
The address specification refers to the addresses used in the tool data record as per the
Daimler Benz standardization proposal.
Format: Max. 4 bytes ASCII (for SINUMERIK)

Address status:
Eight-bit address status. For descriptions of the individual bits, please refer to Section 3.8.
Format: 1 byte (bit pattern)

F . . : (Format)
The data format required by the SINUMERIK is forwarded to the encoding station in a format
description field comprising a format identifier and a format parameter (see Section 3.7 for
details).
The encoding station formats the data as per these specifications and forwards it to the
SINUMERIK.
Format: 2 bytes (hexadecimal)

© Siemens AG 1991 All Rights Reserved 6FC5 197-0AB40-0BP0 3–3

SINUMERIK 840/880 (PJ)
 1
aaaaaaaaaaaaaaaa

18

3–4
3.2
aaaaaaaaaaaaaaaa

Byte

Byte
aaaaaaaaaaaaaaaa

Res.
aaaaaaaaaaaaaaaa
3 Frames

aaaaaaaaaaaaaaaa
aaaaaaaaaaaaaaaa
aaaaaaaaaaaaaaaa
a
aa
aa
aa
aa
aa
aa
aa
aa
a
aaaaaaaaaaaaaaaa

21
aaaaaaaaa aaaaaaaaaaaaaaaa

and error code

aaaaaaaa
aa
a aaaaaaaaaaaaaaaa

Byte

L. 2
L. 1
aa
aaa
aa
aa
aa
aa
aaa
aaaaaaaaa aaaaaaaaaaaaaaaa

Addr.
Addr.
a
aa
aa
aa
aa
aa
aa
aa
aa
a aaaaaaaaaaaaaaaa
Frame identification
a
aa
aa
aa
aa
aa
aa
aa
aa
a aaaaaaaaaaaaaaaa
aa
aaaaaaaa
aa
a aaaaaaaaaaaaaaaa
aaa
aa
aa
aa
aa
aaa

19
aaaaaaaaa aaaaaaaaaaaaaaaa
11

a
aa
aa
aa
aa
aa
aa
aa
aa
a aaaaaaaaaaaaaaaa
aaaaaaaaa

NAR
a
aa
aa
aa
aa
aa
aa
aa
aa
a
aaaaaaaaaaaaaaaa
aaaaaaaaa aaaaaaaaaaaaaaaa
length

a
aa
aa
aa
aa
aa
aa
aa
aa
a aaaaaaaaaaaaaaaa
a
aa
aa
aa
aa
aa
aa
aa
aa
a aaaaaaaaaaaaaaaa
aaaaaaaaa

Addr. 2
Addr. 1
a
aa
aa
aa
aa
aa
aa
aa
aa aaaaaaaaaaaaaaaa
Useful data

aa
aaa
aa
aa
aa
aaaa
aaa
a
aaaaaaaaaaaaaaaa
aaaaaaaaa aaaaaaaaaaaaaaaa
20
a
aa
aa
aa
aa
aa
aa
aa
aa
a aaaaaaaaaaaaaaaa

F2
F1
aaaaaaaaa

NAT
aaaaaaaaa aaaaaaaaaaaaaaaa
No. of addr.
aa
aaaaaaaa
aa
a aaaaaaaaaaaaaaaa
aaa
aa
aa
aa
aa
aaa
13

a
aa
aa
aa
aa
aa
aa
aa
aa
a
aaaaaaaaaaaaaaaa
3.2 Response to ”Read” request: encoding station CNC

a
aa
aa
aa
aa
aa
aa
aa
aa
a
aaaaaaaaaaaaaaaa
a
aa
aa
aa
aa
aa
aa
aa
aa
a
aaaaaaaaaaaaaaaa
Format (not including frame length specification):

a
aa
aa
aa
aa
aa
aa
aa
aa
a
aaaaaaaaaaaaaaaa
aaaaaaaa
a
aa
aa
aa
aa
aa
aa
aa
aa
a
Subaddr.

a
aa
aa
aa
aa
aa
aa
aa
aa
a

stat.
stat.
a
aa
aa
aa
aa
aa
aa
aa
aa
aa
a

© Siemens AG 1991
14

aa
aaa
aa
aa
aa
aa
aaa

Addr. 2
Addr. 1
aaaaaaaaa

Address data block 1

aaaaaaaaa

Address data block 2

a
aa
aa
aa
aa
aa
aa
aa
aa
a
a
aa
aa
aa
aa
aa
aa
aa
aa
aa
aaa
aa
aa
aa
aaaa
aaa
a
Head no.

a
aa
aa
aa
aa
aa
aa
aa
aa
a
a
aa
aa
aa
aa
aa
aa
aa
aa
a
aaaaaaaaa

Additional address data blocks, if any

aaaaaaaaa

Data 2
Data 1
15

a
aa
aa
aa
aa
aa
aa
aa
aa
a
fier

a
aa
aa
aa
aa
aa
aa
aa
aa
a
aaaaaaaaa

All Rights Reserved

aaaaaaaaa
Identi-

aaaaaaaaa

................................................
aa
aaaaaaaa
aa
a
a
a
aa
a
aa
a
aa
a
aa
a
aa
a
aa
aaa
a
Response to ”Read” request: encoding station CNC

a
aa
aa
aa
aa
aa
aa
aa
aa
a
a
aa
aa
aa
aa
aa
aa
aa
aa
a
16

aa
aaaaaaaa
aa
a
a
a
aa
a
aa
a
aa
a
aa
a
aa
a
aa
aaa
aaaaaaaaa
a
Info field

6FC5 197-0AB40-0BP0
SINUMERIK 840/880 (PJ)
12.91
12.91 3 Frames
3.2 Response to ”Read” request: encoding station CNC

Frame identification and error code:

The frame identification (see Section 3.11) identifies the frame as a response to a "Read"
request.
The useful data section contains the addresses, format specifications and data.

Useful data length: See 3.1

Subaddress: See 3.1
Head no.: See 3.1
Identifier: See 3.1
Info field: See 3.1
Reserve: See 3.1
Address length: See 3.1
Format: See 3.1
Address status: See 3.1

No. of addr. (number of addresses):

NAT: Number of address format (data) blocks:
This specification refers to the number of address format data blocks in the useful
data field of the "Read" response.
Number of addresses "to be read".
In an error frame: Number of addresses in the frame
Format: 1 byte (hexadecimal)
NAR: Number of address (successfully) processed:
This specification refers to the number of addresses actually read in the "Read"
response.
Format: 1 byte (hexadecimal)

Addr. x : (address)
The address specification refers to the addresses specified in the Daimler Benz
standardization proposal.
Format: Max. 4 bytes ASCII (for SINUMERIK)

Note carefully:
The encoding station must transfer the addresses and the associated data for each cutting
edge in the order in which they appear in the "Read" request.

Example:
If the length, diameter and radius (in that order) were requested in the "Read data for first
cutting edge" request, the data appears in the following order in the response frame:
Length cutting edge 1, diameter cutting edge 1, radius cutting edge 1

© Siemens AG 1991 All Rights Reserved 6FC5 197-0AB40-0BP0 3–5

SINUMERIK 840/880 (PJ)
3 Frames 12.91
3.3 Conventions for "Read"

3.3 Conventions for "Read"

1. Format parameter 00 hexadecimal:
If hexadecimal 00 is specified as format parameter in a "Read" request, the value stored
on the chip must be returned as format parameter in the response (see Section 3.7).
The format type (with/without sign, with/without decimal point) must be observed.

2. Requested data not on chip:

(From the standard package’s point of view: address status bit 2=0; see Section 3.8).
Since it is not known which tool type is in the encoding station when a "Read" request is
issued, all cutting edge-related data must be requested.
If more addresses are requested in the "Read" request than are on the chip, the encoding
station responds in dependence on address status bit 3 (see Section 3.8):

Address status bit 3 = 0 (conditionally requested address):

If the encoding station cannot locate addresses or data on the chip, it returns the address
length, address, format description and address status, but no useful data, for the
requested value, and hexadecimal 00 as the value’s format parameter as response to the
"Read" request..
It also returns a "1" ("invalid data") in address status bit 0 (Section 3.8).
This status is also flagged in the request response in the "Number of addresses" field, i.e.
NAT (number of addresses requested) and NAR (number of addresses read), and in the
"Info field".
The encoding station does not transmit an error frame, as this would abort the dialog. The
CNC can itself decide how to react to the missing data.

Address status bit 3 = 1 (unconditionally requested address):

The encoding station sends an error frame:
• In the case of a "general" error, the encoding station returns all address format (data)
blocks listed in the control’s request.
• In the case of "specific" errors, the encoding station returns only the address format
block that caused the error, i.e. the error frame contains only one address format block
(NAT=1, NAR=0).

3–6 © Siemens AG 1991 All Rights Reserved 6FC5 197-0AB40-0BP0

SINUMERIK 840/880 (PJ)
12.91 3 Frames
3.3 Conventions for "Read"

3. No. of addresses (NAT/NAR):

NAT = Number of following address format (data) blocks
NAR = Number of successfully processed addresses
In both the request and the response, "NAT" contains the number of addresses to be
read on the chip.
"NAR" contains zero in the request and the number of addresses actually read in the
response.
Example:
Six addresses are supposed to be read on the chip, but only five could actually be read
(one of the specified addresses was not on the chip).
Request: Number of addresses: NAT/NAR = 6/0
Response: Number of addresses: NAT/NAR = 6/5

Request/response cycle for "Read from chip":

Situation: All addresses read:
Request NAR = 0; NAT = n
Response NAR = n; NAT = n
Situation: Some addresses read:
Request NAR = 0; NAT = n
Response NAR = 0<m<n; NAT = n
Situation: No addresses read:
Request NAR = 0; NAT = n
Response NAR = 0; NAT = n

4. Format conflict, on-chip data exceeds requested length:

(Refers only to the total length specifications in the format parameter)
If a data item read from the chip is too long (i.e. if the number of bytes (including decimal
point and/or sign) exceeds the total length specified in the format parameter) after
formatting (depends on format type; in formats with decimal places, the "number of
decimal places" specification is always enforced), the encoding station suppresses any
leading zeros in the integer portion of the value before transferring the value in the
specified format.
If the value is still too long after the leading zeros in the integer portion have been
suppressed (format conflict), the encoding station responds on the basis of address status
bit 2 for the address in the "Read" request:

Address status bit 2 = 0:

In the event of a format conflict, the encoding station corrects the length specification in
the format parameter and transfers the value in its true length (after suppressing leading
zeros, if necessary).
The encoding station does not send an error frame because of a format conflict.

© Siemens AG 1991 All Rights Reserved 6FC5 197-0AB40-0BP0 3–7

SINUMERIK 840/880 (PJ)
3 Frames 12.91
3.3 Conventions for "Read"

Address status bit 2 = 1:

In the event of a format conflict, a substitute address data block (comprising address
length, address, format description, address status and date) containing the correct length
is appended to the end of the response frame.
The original address block is returned in the response (address status bit 0 = 1: invalid
date); the associated data consists of an offset to the substitute address data block and,
when necessary, filler characters.
The encoding station does not send an error frame because of a format conflict!
This case is not implemented in the SINUMERIK’s standard software.

5. On-chip data falls short of requested length:

If the number of characters in an on-chip value falls short of the number specified in the
"Read" request’s format parameter (excepting format parameter hexa 00 and format
identifier hex 36.37), the encoding station pads the field (i.e. adds the appropriate filler
characters at the left of the high-value position in a numerical value or at the right of the
sign, depending on the format).

6. Conditional/unconditional read:
Address status bit 3 = 0/1: Conditional/unconditional read
If the encoding station cannot find a conditionally requested address on the chip, it
responds as described under 2., and does not send an error frame.
If the encoding station cannot find an unconditionally requested address on the chip, it
sends an error frame to the SINUMERIK containing only this address format block
(NAT 0 1, NAR = 0).

The encoding station must observe all conventions listed under points 1-6.

3–8 © Siemens AG 1991 All Rights Reserved 6FC5 197-0AB40-0BP0

SINUMERIK 840/880 (PJ)
 1
aaaaaaaaaaaaaaaa

18
3.4

aaaaaaaaaaaaaaaa
Byte
12.91

Byte

Res.
aaaaaaaaaaaaaaaaaaaaaaaa
aaaaaaaaaaaaaaaa
aaaaaaaaaaaaaaaa
aaaaaaaaaaaaaaaa
aaaaaaaaaaaaaaaa
a
aa
aa
aa
aa
aa
aa
aa
a aaaaaaaaaaaaaaaa
aaaaaaaa

21
and error code
a
aa
aa
aa
aa
aa
aa
aa
a
aaaaaaaaaaaaaaaa

© Siemens AG 1991
Byte

L. 2
L. 1
a
aa
aa
aa
aa
aa
aa
aa
a
aaaaaaaaaaaaaaaa

Addr.
Addr.
a
aa
aa
aa
aa
aa
aa
aa
a
aaaaaaaaaaaaaaaa
Frame identification

SINUMERIK 840/880 (PJ)

a
aa
aa
aa
aa
aa
aa
aa
a
aaaaaaaaaaaaaaaa
a
aa
aa
aa
aa
aa
aa
aa aaaaaaaaaaaaaaaa
aa
a aaaaaaaaaaaaaaaa

19
aa
aaa
aa
aa
aa
aaa
11

a
aa
aa
aa
aa
aa
aa
aa
a
aaaaaaaaaaaaaaaa
aaaaaaaa aaaaaaaaaaaaaaaa

NAR
a
aa
aa
aa
aa
aa
aa
aa
a aaaaaaaaaaaaaaaa
aaaaaaa
length

aa
aaa
aa
aa
aaaa
aaa
a
aaaaaaaaaaaaaaaa
a
aa
aa
aa
aa
aa
aa
aa
a
aaaaaaaaaaaaaaaa

All Rights Reserved

aaaaaaaa aaaaaaaaaaaaaaaa

Addr. 2
Addr. 1
a
aa
aa
aa
aa
aa
aa
aa
a aaaaaaaaaaaaaaaa
Useful data

a
aa
aa
aa
aa
aa
aa
aa
a aaaaaaaaaaaaaaaa
aaaaaaaa
20

a
aa
aa
aa
aa
aa
aa
aa
a
aaaaaaaaaaaaaaaa

F2
F1
a
aa
aa
aa
aa
aa
aa
aa
a
aaaaaaaaaaaaaaaa
NAT
No. of addr.

a
aa
aa
aa
aa
aa
aa
aa aaaaaaaaaaaaaaaa
aa
aaa
aa
aa
aaaa
aaa
a
aaaaaaaaaaaaaaaa
13

a
aa
aa
aa
aa
aa
aa
aa
a
aaaaaaaaaaaaaaaa
a
aa
aa
aa
aa
aa
aa
aa
a
aaaaaaaaaaaaaaaa
aaaaaaaa aaaaaaaaaaaaaaaa
Format (not including frame length specification)

aa
aaaaaaa
aa
a aaaaaaaaaaaaaaaa
a
a
aa
a
aa
a
aa
a
aa
a
aa
aaa
a aaaaaaaa
Subaddr.

a
aa
aa
aa
aa
aa
aa
aa
a

stat.
stat.
a
aa
aa
aa
aa
aa
aa
aa
a

6FC5 197-0AB40-0BP0
a
aa
aa
aa
aa
aa
aa
aa
a
14

Addr. 2
Addr. 1
aaaaaaaa

Address data block 2

Address data block 1
a
aa
aa
aa
aa
aa
aa
aa
a
a
aa
aa
aa
aa
aa
aa
aa
a
"Write" request: CNC encoding station

a
aa
aa
aa
aa
aa
aa
aa
aa
aaa
aa
aa
aaaa
aaa
a
Head no.

a
aa
aa
aa
aa
aa
aa
aa
a
a
aa
aa
aa
aa
aa
aa
aa
a

Additional address data blocks, if any

aaaaaaaa

Data 2
Data 1

aaaaaaa
15

aa
aaa
aa
aa
aaaa
aaa
a
a
aa
aa
aa
aa
aa
aa
aa
a
a
aa
aa
aa
aa
aa
aa
aa
a

................................................
a
aa
aa
aa
aa
aa
aa
aa
a
Identifier

a
aa
aa
aa
aa
aa
aa
aa
a
a
aa
aa
aa
aa
aa
aa
aa
a
a
aa
aa
aa
aa
aa
aa
aa
a
aaaaaaaa
16

aa
aaaaaaa
aa
a
aaa
aa
aa
aa
aa
aaaaaaaa
a
Info field
3.4 "Write" request: CNC encoding station
3 Frames

3–9
3 Frames 12.91
3.4 "Write" request: CNC encoding station

Frame identification and error code:

The frame identification identifies the frame as "Write" request.
The useful data portion of the frame contains the addresses, the format specifications and the
data to be written to the code carrier chip.

Useful data length: see 3.1

Subaddress: see 3.1
Head no.: see 3.1
Identifier: see 3.1
Info field: see 3.1
Reserve: see 3.1
Address length: see 3.1
Address: see 3.1
Format: see 3.1
Address status: see 3.1

No. of addr. (number of addresses):

NAT: Number of address format (data) blocks to be written
The NAT refers to the number of address format data blocks in the useful data
section of the "Write" request.
Specifies the number of addresses "to be written".
Format: 1 byte (hexadecimal)
NAR: Number of addresses (successfully) processed:
The NAR refers to the number of addresses actually written to the code carrier chip.
Value in "Write" request: 00 hexadecimal
Format: 1 byte (hexadecimal)

3–10 © Siemens AG 1991 All Rights Reserved 6FC5 197-0AB40-0BP0

SINUMERIK 840/880 (PJ)
 1
aaaaaaaaaaaaaaaaaa

18
3.5

aaaaaaaaaaaaaaaaaa
Byte
12.91

Byte

Res.
aaaaaaaaaaaaaaaaaaaaaaaaaaa
aaaaaaaaaaaaaaaaaa
aaaaaaaaaaaaaaaaaa
aaaaaaaaaaaaaaaaaa
aaaaaaaaaaaaaaaaaa
a
aa
aa
aa
aa
aa
aa
aa
a aaaaaaaaaaaaaaaaaa
aaaaaaaa

21
and error code
a
aa
aa
aa
aa
aa
aa
aa
a
aaaaaaaaaaaaaaaaaa

© Siemens AG 1991
Byte

L. y
L. x
a
aa
aa
aa
aa
aa
aa
aa
a
aaaaaaaaaaaaaaaaaa

Addr.
Addr.
a
aa
aa
aa
aa
aa
aa
aa
a
aaaaaaaaaaaaaaaaaa
Frame identification

SINUMERIK 840/880 (PJ)

a
aa
aa
aa
aa
aa
aa
aa
a
aaaaaaaaaaaaaaaaaa
a
aa
aa
aa
aa
aa
aa
aa aaaaaaaaaaaaaaaaaa
aa
a aaaaaaaaaaaaaaaaaa

19
aa
aaa
aa
aa
aa
aaa
11

a
aa
aa
aa
aa
aa
aa
aa
a
aaaaaaaaaaaaaaaaaa
aaaaaaaa aaaaaaaaaaaaaaaaaa

NAR
a
aa
aa
aa
aa
aa
aa
aa
a aaaaaaaaaaaaaaaaaa
aaaaaaa
length

aa
aaa
aa
aa
aaaa
aaa
a
aaaaaaaaaaaaaaaaaa
a
aa
aa
aa
aa
aa
aa
aa
a
aaaaaaaaaaaaaaaaaa

All Rights Reserved

aaaaaaaa aaaaaaaaaaaaaaaaaa

Addr. y
Addr. x
a
aa
aa
aa
aa
aa
aa
aa
a aaaaaaaaaaaaaaaaaa
Useful data

a
aa
aa
aa
aa
aa
aa
aa
a aaaaaaaaaaaaaaaaaa
aaaaaaaa
20

a
aa
aa
aa
aa
aa
aa
aa
a
aaaaaaaaaaaaaaaaaa

Fy
Fx
a
aa
aa
aa
aa
aa
aa
aa
a
aaaaaaaaaaaaaaaaaa
NAT
No. of addr.

a
aa
aa
aa
aa
aa
aa
aa aaaaaaaaaaaaaaaaaa
aa
aaa
aa
aa
aaaa
aaa
a
aaaaaaaaaaaaaaaaaa
13

a
aa
aa
aa
aa
aa
aa
aa
a
aaaaaaaaaaaaaaaaaa
a
aa
aa
aa
aa
aa
aa
aa
a
aaaaaaaaaaaaaaaaaa
aaaaaaaa aaaaaaaaaaaaaaaaaa
Format (not including frame length specification)

aa
aaaaaaa
aa
a aaaaaaaaaaaaaaaaaa
a
a
aa
a
aa
a
aa
a
aa
a
aa
aaa
a aaaaaaaaa
Subaddr.

a
aa
aa
aa
aa
aa
aa
aa
a

stat.
stat.
a
aa
aa
aa
aa
aa
aa
aa
a

6FC5 197-0AB40-0BP0
a
aa
aa
aa
aa
aa
aa
aa
a
14

Addr. y
Addr. x
aaaaaaaa

Address data block y

Address data block x
a
aa
aa
aa
aa
aa
aa
aa
a
a
aa
aa
aa
aa
aa
aa
aa
a
a
aa
aa
aa
aa
aa
aa
aa
aa
aaa
aa
aa
aaaa
aaa
a
Head no.

a
aa
aa
aa
aa
aa
aa
aa
a
a
aa
aa
aa
aa
aa
aa
aa
a

Additional address data blocks, if any

aaaaaaaa

Data y
Data x
aaaaaaa
15

aa
a
Response to "Write" request: encoding station

aa
aaa
aa
aa
aa
aaa
a
aa
aa
aa
aa
aa
aa
aa
a
a
aa
aa
aa
aa
aa
aa
aa
a

................................................
a
aa
aa
aa
aa
aa
aa
aa
a
Identifier

a
aa
aa
aa
aa
aa
aa
aa
a
aaaaaaaa
CNC

a
aa
aa
aa
aa
aa
aa
aa
a
a
aa
aa
aa
aa
aa
aa
aa
a
16

aa
aaaaaaa
aa
a
aaa
aa
aa
aa
aa
was not sufficient (if it is not an error frame), the data is sent back in the useful data:

aaaaaaaa
a
Info field

3 = 0: conditionally requested address; it is not an error frame or because the chip capacity
If data could not be written, for example, because they are not on the chip (address status bit
3.5 Response to "Write" request: encoding station CNC
3 Frames

3–11
3 Frames 12.91
3.5 Response to "Write" request: encoding station CNC

Frame identification and error code:

The frame identification (see Section 3.8) identifies the frame as a "Write" request.

Useful data length: see 3.1

Subaddress: see 3.1
Head no.: see 3.1
Identifier: see 3.1
Info field: see 3.1
Reserve: see 3.1
Address length: see 3.1
Address: see 3.1
Format: see 3.1
Address status: see 3.1

No. of addr. (number of addresses)

NAT: Number of address format (data) blocks:
The NAT refers to the number of address format data blocks in the useful data
portion of the "Write" response.
Number of addresses that could not be written to the chip.
Format: 1 byte (hexadecimal)
NAR: Number of addresses (successfully) processed:
The NAR refers to the number of addresses actually written to the code carrier chip.
Format: 1 byte (hexadecimal)

3–12 © Siemens AG 1991 All Rights Reserved 6FC5 197-0AB40-0BP0

SINUMERIK 840/880 (PJ)
12.91 3 Frames
3.6 Conventions for "Write"

3.6 Conventions for "Write"

1. More addresses in "Write" request than are on the chip:
The encoding station reacts as follows, in dependence on address status bit 3 (see
Section 1.8), if more addresses are specified in the "Write" request than are on the chip:
Address status bit 3 = 0: (conditionally requested address)
Only the data at addresses already on the chip is overwritten. The number of addresses
on the chip thus remains unchanged, thereby lessening the danger of capacity problems.
The encoding station does not send an error frame (unless there is not enough room on
the chip).
The encoding station returns the address length, address, format description, address
status (bit 0 = 1: invalid data) and the data at the addresses that cannot be written to the
chip.
A code is returned in the "info field", the number of addresses that were not written to the
chip in "number of addresses: NAT", and the number of addresses actually written to the
chip in "number of addresses: NAR". "NAR" also identifies the number of addresses
returned in the response.
Address status bit 3 = 1 (unconditionally requested address):
All addresses are written, regardless of whether they were or were not already on the chip.
The encoding station does not send an error frame (unless there is not enough room on
the chip).
A code is returned in the "info field" to indicate that previously non-existent addresses
(and data) were written to the chip.
Error frame in the event of capacity problems
The error frame for a "Write" request includes the address length, address, format
description, address status (bit 0 = 1: invalid data) and the data for the address that could
not be written to the chip.

2. No error
If no problems occur, the encoding station does not forward an error frame to the
SINUMERIK. The response frame, however, may vary for different situations:
When it was possible to write all data to the chip, the response contains no address data
blocks.
If no addresses with address status bit 3 = 0 (conditionally requested addresses) were
written because they were not on the chip, the encoding station returns their address data
blocks (with address status 0: invalid data).
A code is returned in the info field for evaluation in the SINUMERIK.

© Siemens AG 1991 All Rights Reserved 6FC5 197-0AB40-0BP0 3–13

SINUMERIK 840/880 (PJ)
3 Frames 12.91
3.6 Conventions for "Write"

3. Error frame:
The error frame contains only the address data block for the address that could not be
written to the chip.

4. Number of addresses on the chip:

The number of addresses on the chip does not change if address status bit 3 is zero for
all addresses in the "Write" request.

5. Data length:
The length of the useful data referenced by the addresses can change (i.e. if a data item
is longer than the one already on the chip, it is stored as defined; if it is shorter, the
decision as to how it is to be stored is made by the encoding station).

6. Number of addresses (NAT/NAR):

NAT = Number of address format (data) blocks
NAR = Number of addresses (successfully) processed

Request/response cycle for "Write to chip":

Situation: All addresses written:
Request NAR = 0; NAT = n
Response NAR = n; NAT = 0
Situation: Some addresses written:
Request NAR = 0; NAT = n
Response NAR = 0<m<n; NAT = n-m
Situation: No addresses written:
Request NAR = 0; NAT = n
Response NAR = 0; NAT = n

3–14 © Siemens AG 1991 All Rights Reserved 6FC5 197-0AB40-0BP0

SINUMERIK 840/880 (PJ)
12.91 3 Frames
3.7 Formats

3.7 Formats

The 2-byte "format" field describes the type and length of the data immediately following the
"address status" field. The field is coded in hexadecimal as shown in the table below.
The first byte specifies the format identifier, the second the format parameter.
The high-order byte is transmitted first.

Formats:

Format identifier Format parameter

Type
Bits 15 - 8 Bits 7 - 4 Bits 3 - 0

Unchanged R 00 Max. length of character string

Unchanged L 01 Max. length of character string

Unsigned binary 12 Length of the binary number in bytes

Signed binary 14 Length of the binary number in bytes

Hexa string R 20 Length of the hexa character string

Hexa string L 21 Length of the hexa character string

BCD, fixed-point, no SG, no DP 30 No. of dec. places Number of bytes

BCD, fixed-point, no SG, DP 31 No. of dec. places Number of bytes

BCD, fixed-point, SG, no DP 32 No. of dec. places Number of bytes

BCD, fixed-point, SG, DP 33 No. of dec. places Number of bytes

BCD, floating-point, no SG 34 Number of bytes

BCD, floating-point, SG 35 Number of bytes

BCD, floating-point, no SG 36 Max. number of bytes

BCD, floating-point, no SG 37 Max. number of bytes

ASCII string R 40 Length of the ASCII string

ASCII string L 41 Length of the ASCII string

ASCII digit string R 50 Length of the digit string

ASCII digit string L 51 Length of the digit string

ASCII digits, no SG, no DP 52 No. of dec. places Number of bytes

ASCII digits, no SG, DP 53 No. of dec. places Number of bytes

ASCII digits, SG, no DP 54 No. of dec. places Number of bytes

ACII digits, SG, DP 55 No. of dec. places Number of bytes

© Siemens AG 1991 All Rights Reserved 6FC5 197-0AB40-0BP0 3–15

SINUMERIK 840/880 (PJ)
3 Frames 12.91
3.7 Formats

(The code carrier manufacturer need implement only the format identifiers shown in bold type.
All other format identifiers are optional; information regarding these format identifiers can be
obtained from the code carrier manufacturer).

Abbreviations: DP = Decimal point

SG = Sign

Format descriptions:

Unchanged R/L (00-01H)

Unchanged format, i.e. an ASCII character string is retained in its original form as long as it
does not exceed the maximum length. The format parameter specifies the maximum length in
bytes and indicates whether the string is to be stored right-justified (R) or left-justified (L).
In the response to a Read request, the maximum length is replaced by the actual length.

Signed/unsigned binary (12/14H)

The value is represented in binary format. In signed binary format, the high-order bit is the sign
of the number (0 if positive, 1 if negative).
The format parameter specifies the number of positions in bytes.
Example: Two-byte signed binary number (bit 15=sign)
Bit 15 14 13 12 11 10 09 08 07 06 05 04 03 02 01 00

Hex string R/L (20,21H)

A string of hexadecimal digits whose source string is to be stored right-justified (R) or left-
justified (L). Fill characters are padded with 00.
The format parameter specifies the length of the string in bytes.

BCD, fixed-point (30/31/32/33H)

Each number is represented as BCD character in fixed-point notation, signed or unsigned, with
or without a decimal point. The sign and the decimal point are in BCD code as per the ASCII
table.
Blanks (fill characters) are represented as hexadecimal 0.
Plus = 1011
Minus = 1101
Dec. point = 1110
1 digit = 1 BCD character = 4 bits
The format parameter specifies the number of bytes, including decimal point, sign, fill
characters or fill nibbles, and the number of decimal places (in nibbles).

3–16 © Siemens AG 1991 All Rights Reserved 6FC5 197-0AB40-0BP0

SINUMERIK 840/880 (PJ)
12.91 3 Frames
3.7 Formats

Note carefully:
The "number of decimal places" specification is always enforced:
If there are fewer decimal places on the chip than requested, the low-order positions are
padded with zeros. If there are more decimal places on the chip than requested, the low-order
positions are truncated.
Format type "DP", i.e. with decimal point, means that the value contains a decimal point; the
number of places after the decimal point is specified via the format parameter (e.g.: 123.45
hexadecimal 123E45). If the number of decimal places is zero, the value does not contain a
decimal point (e.g. 1234 is formatted as 1234, not as 1234E).
Format type "no DP", i.e. without decimal point means that the value does not contain a
decimal point; the number of decimal places it specified via the format parameter (e.g. 123.45
hexadecimal 12345).

BCD, floating-point (34/35H)

Each number is represented as a signed or unsigned BCD character in floating-point notation.
The format parameter specifies the actual number of bytes, including decimal point, sign,
fillers or filler nibbles.
Blanks (fillers) are represented as hexadecimal 0.
Plus = 1011
Minus = 1101
Dec. point = 1110
1 digit = 1 BCD character = 4 bits

BCD, floating-point (36/37H)

Each number is represented as a signed or unsigned BCD character in floating-point notation.
The format parameter specifies the actual number of bytes, including decimal point, sign,
fillers or filler nibbles.
Blanks (fillers) are represented as hexadecimal 0.
Plus = 1011
Minus = 1101
Dec. point = 1110
1 digit = 1 BCD character = 4 bits

In a response to a Read request, the maximum length is replaced by the actual length.

ASCII string R/L (40/41H)

String of ASCII characters whose source string is to be stored right-justified (R) or left-justified
(L). Blanks are padded with 30H.
The format parameter specifies the length of the string in bytes.

ASCII string R/L (50/51H)

String of ASCII characters whose source string is to be stored right-justified (R) or left-justified
(L). Blanks are padded with 30H.
The format parameter specifies the length of the string in bytes.

© Siemens AG 1991 All Rights Reserved 6FC5 197-0AB40-0BP0 3–17

SINUMERIK 840/880 (PJ)
3 Frames 12.91
3.7 Formats

ASCII digits, fixed-point (52/53/54/55H)

Each digit is represented as signed or unsigned ASCII character, in fixed-point notation, with or
without a decimal point.
Sign and decimal point are coded as per the ASCII table. Blanks are padded with 30H.
1 digit = 1 ASCII character = 8 bits
The format parameter specifies the number of bytes, including decimal point, sign and blanks,
and the number of decimal places.
The specified number of decimal places is always enforced:
If there are fewer decimal places on the chip than requested, the low-order positions are
padded with 30H. If there are more decimal places on the chip than requested, the low-order
positions are suppressed.

3–18 © Siemens AG 1991 All Rights Reserved 6FC5 197-0AB40-0BP0

SINUMERIK 840/880 (PJ)
12.91 3 Frames
3.8 Address status

3.8 Address status

In both request and response frames, each address has an address status.
The eight bits in the address status byte are described in detail below.

Format of the address status byte:

Bit 7 = 0/1: Unassigned
Bit 6 = 0/1: Unassigned
Bit 5 = 0/1: Unassigned
Bit 4 = 0/1: Unassigned
Bit 3 = 0/1 Action bit:
conditionally/unconditionally requested address
Bit 2 = 0/1: Action bit:
= 0: Format change
In the event of a format conflict or missing data
= 1: No format change
In the event of a format conflict, substitute address data block at end
of string; data always consists of fillers; in substitute address data
block, data consists of offset and fillers.
Bit 1 = 0/1: Reaction bit:
= 0: No format conflict
= 1: Format conflict
Bit 0 = 0/1: Reaction bit:
Data at this address valid/invalid.

Action bit:
This bit represents a request to the encoding station.

Reaction bit:
This bit represents a reaction from the encoding station.

The action bits are set, where applicable, in the request, and are returned unchanged in the
response.

The reaction bits are zero in a request, and contain information from the encoding station in
the response.

© Siemens AG 1991 All Rights Reserved 6FC5 197-0AB40-0BP0 3–19

SINUMERIK 840/880 (PJ)
3 Frames 12.91
3.8 Address status

Action and reaction bits:

Bit 3: Action bit

Conditionally/unconditionally requested address
Bit 3 is an action bit, i.e. appears only in "Read" and "Write" requests.

"Read" request:
In a "Read" request, bit 3 indicates whether the address is to be read conditionally (not
mandatory) or unconditionally (mandatory).
The encoding station’s reaction to this bit is described in detail in Section 3.3, points 2 and 6.

"Write" request:
In a "Write" request, bit 3 indicates whether the address is to be written conditionally (not
mandatory) or unconditionally (mandatory).
The encoding station’s reaction to this bit is described in detail in Section 3.6, point 1.

Bit 2: Action bit

= 0: Format change
= 1: No format change
Bit 2 is an action bit, and appears only in "Read" requests.
If a data item read from the chip is too long (i.e. if the number of bytes, including decimal point
and/or sign, exceeds the total length specified in the associated format parameter) after
formatting (depending on the format; in the case of formats with decimal places, the specified
number of decimal places is always enforced), the encoding station truncates any leading
zeros in the integer portion of the value and transfers the value in the specified format.
If the value is still too long after truncation of leading zeros (format conflict), the encoding
station responds in dependence on address status bit 2 for the address in the "Read" request:

Address status bit 2 = 0:

In the event of a format conflict, the encoding station corrects the format parameter and
transfers the value in its true length (after truncating any leading zeros, if necessary).
The encoding station does not send an error frame.

Address status bit 2 = 1:

In the event of a format conflict (on-chip data longer than requested), the encoding station
appends a substitute address data block (containing address length, address, format
description, address status and data) at the end of the response frame. The original address
block is returned in the response to the "Read" request (address status bit 0 = 1: invalid
data), the associated data comprising an offset to the substitute address block and fillers, if
needed.
The encoding station does not send an error frame.

3–20 © Siemens AG 1991 All Rights Reserved 6FC5 197-0AB40-0BP0

SINUMERIK 840/880 (PJ)
12.91 3 Frames
3.8 Address status

If the address to be read is not on the chip, the encoding station reacts according to address
status bit 2:

Address status bit 2 = 0:

If an address cannot be found on the chip, its format parameter is set to hexadecimal 00
(address status bit 0 = 1: invalid data).

Address status bit 2 = 1:

If an address cannot be located on the chip, its format parameter is left unchanged and the
data consists only of fillers (address status bit 0 = 1: invalid data).

Bit 1: Reaction bit:

= 0: No format conflict
= 1: Format conflict for this address
Bit 1 is a reaction bit, and appears only in a response to a "Read" request.
A format conflict means that the data associated with the address exceeds the total length
(e.g. "number of bytes" for BCD formats) specified in the format parameter after formatting.

Response to "Read" request:

This bit represents the reaction of the encoding station to address status 2 in the event of a
format conflict.
If a format conflict occurs, this bit is set to "1"; the reaction to the format conflict can be
ascertained by scanning address status bit 2 (which is returned unchanged in the response).

Bit 0 = 0/1: Reaction bit:

Valid/invalid data at this address
Bit 0 is a reaction bit, i.e. is relevant only in "Read" requests and in an error frame returned
for a "Read" or "Write" request.

Response to a "Read" request:

The bit indicates whether data was found at the specified address (bit 0 = 0) or not
(bit 0 = 1).

Error frame for a "Read/Write" request:

The bit indicates that it was not possible to read or write the data (bit 0 = 1).

© Siemens AG 1991 All Rights Reserved 6FC5 197-0AB40-0BP0 3–21

SINUMERIK 840/880 (PJ)
3 Frames 12.91
3.9 Conventions and stipulations

3.9 Conventions and stipulations

1. If a BCD string comprises an odd number of nibbles (including sign and decimal point,
where applicable), it must be rounded up for transfer to an even number of nibbles (i.e.
bytes).
Signed BCD numbers may have a filler nibble at the right of the sign (high-value position of
the numerical value).

2. In all BCD formats, the number of bytes always includes the sign (if any), the decimal
point (if any) and all fillers (fill nibble(s)).

3. Signed BCD formats: If the encoding station does not find a sign when it reads from the
chip, it regards the value read as positive and generates binary 1011 as sign before
transferring the value.

4. The standard package on the SINUMERIK requires primarily formats 12H, 14H, 31H, 33H
and 40H.

5. In floating-point numbers (see BCD formats), the decimal point (which is represented as
binary 1110) may be located anywhere within the number, i.e. a floating-point number may
be a full integer, comprise only decimal places, or comprise an integer portion and decimal
places. The location of the decimal point is specified via the format parameter.

6. Address status bit 2 = 0; format change:

Chip addresses without useful data are returned in the response with their address length,
address, format description and address status, and with a format parameter of
hexadecimal 00 (address status: invalid data).

7. The on-chip data length for various addresses may change, depending on the "Write"
requests issued.

8. The decimal place specification is always enforced:

If there are fewer decimal places on the chip than requested, the low-order positions are
padded with zeros. If there are more decimal places on the chip than requested, the low-
order positions are truncated.

9. If an item of data read from the chip is still too long (i.e. if the number of bytes, including
decimal point and/or sign, exceeds the total length specified in the format parameter) after
formatting (in the case of formats with decimal places, for instance, the decimal place
specification is always enforced) and after truncation of any leading zeros, there will be
what is termed a format conflict.

10. In the event of a format conflict, the total length specified for the data item in the format
parameter (e.g. the number of bytes for BCD formats) is sometimes corrected; this is
never done, however, in the case of formats involving decimal places.

3–22 © Siemens AG 1991 All Rights Reserved 6FC5 197-0AB40-0BP0

SINUMERIK 840/880 (PJ)
12.91 3 Frames
3.9 Conventions and stipulations

11. The "number of cutting edges" for a tool must always be on the chip.

12. As of June 3, 1990, the Daimler Benz tool data record includes addresses P0 to P9 for
control-specific parameters. The tool type within the SINUMERIK 880 system must be
specified in one of these parameters.

13. The encoding station may not exceed the total useful data length of 244 bytes (which
begins with the frame identification/error code) per frame.

14. The encoding station echoes the subaddress, head number and identifier from the request
in its response.

15. The following conventions apply to error frames (error code unequal zero) from the
encoding station:
• In the case of "general" errors (errors which cannot be attributed to a specific address
format (data) block in the Read/Write request, such as syntax errors in the code
carrier’s data string), all address format (data) blocks in the control’s request are
returned in the encoding station’s response (error) frame.
• In the case of "specific" errors (errors which can be attributed to a specific address
format (data) block in the Read/Write request, such as format parameter errors,
unconditional read request for a non-existent address, chip capacity problems and the
like), the encoding station returns only the address format (data) block which caused
the error. The error frame thus contains only one address format (data) block.

© Siemens AG 1991 All Rights Reserved 6FC5 197-0AB40-0BP0 3–23

SINUMERIK 840/880 (PJ)
3 Frames 12.91
3.10 Tool ID, tool carrier, equipment

3.10 Tool ID, tool carrier, equipment

The identification number for tools and tool carriers and the identifier for the type of equipment
are not addressed symbolically on the data carrier.
The proposal for communication with the tool encoding station requires, however, that it be
possible, from the SINUMERIK’s point of view, to request and write this data via symbolic
addresses, thus informing the encoding station that it is to process the data.

The following symbolic addresses have been established:

Data description Symbolic address

Identification number (T number) and TN

sister tooling ID (duplo number) SN
Identification number and TN
tool/workpiece carrier ID SN
Equipment BA

The "Identification number and sister tooling ID" and the "Identification number and
tool/workpiece carrier ID" have the same symbolic addresses, as only one identification
number and one ID can be on the chip at any given time.

TN: Integer positions (for tools: identification number = T number)

for the "identification number and sister tooling ID" or for the "tool/workpiece carrier" as
per the Daimler Benz tool data record, position 1.

SN: Decimal places (for tools: duplo number)

for the "identification number and sister tooling ID" or for the "tool/workpiece carrier" as
per the Daimler Benz tool data record, position 1.

3–24 © Siemens AG 1991 All Rights Reserved 6FC5 197-0AB40-0BP0

SINUMERIK 840/880 (PJ)
12.91 3 Frames
3.11 Frame identification and error code

3.11 Frame identification and error code

The frame identification for SINUMERIK frames always comprises 8 ASCII characters
specifying the command and the error code. The following IDs are used for communication
with the tool encoding station (the useful data is described in detail on the following page):

1. Chip read:

"Read" request:
CNC encoding station
T CB fnr: "Read" request
Negative response to "Read" request (error frame):
CNC encoding station
T CB F fnr: Negative response to "Read" request
Positive response to "Read" request:
CNC encoding station
R CB fnr: Positive response to "Read" request

2. Chip write:
"Write " request:
CNC encoding station
R CE fnr: "Write" request
Negative response to "Write" request (error frame):
CNC encoding station
R CE F fnr: Negative response to "Write" request
Positive response to "Write" request:
CNC encoding station
T CE fnr: Positive response to "Write request"

” ” in the identication stands for a blank (space).

Error code:
The error code immediately follows the 8 ASCII characters; it comprises one word, and is in
fixed-point notation.
The error code specifies the cause of error ("F frame").
An error frame ("F frame") always results in a dialog abort!
A list of error codes can be found in the Appendix.

© Siemens AG 1991 All Rights Reserved 6FC5 197-0AB40-0BP0 3–25

SINUMERIK 840/880 (PJ)
12.91 4 Frame Sequences
4.1 Frame sequence for "Read"

4 Frame Sequences

In some cases, more than one frame is required to transfer tool data from the encoding station
to the SINUMERIK. For tools with several cutting edges, for instance, one frame is transferred
for each. In consequence, the encoding station and the SINUMERIK communicate in
request/response cycles called frame sequences; these sequences are described in detail
below.
A sequence, or request/response cycle, always begins with a request from the SINUMERIK to
the encoding station. The encoding station subsequently issues either a positive or negative
acknowledgement, or response.
One frame is required to request or transfer the data for each cutting edge.
In the diagrams for the frame sequences, an arrow indicates the direction. The following
abbreviations are used for the specifications which follow the frame identification and error
code:
FL: Frame length
S: Subaddress
H: Head number
ID: Identifier
I: Info field
R: Reserve
N: Number of addresses

DAT 1: Requested addresses in "Read" request

DAT 2: Addresses and associated data for "Read" (also see Section 3.3)
DAT 3: Error frame data for "Read" (addresses read and addresses not read, e.g. in the
case of unconditional "Read" request; see Section 3.3)
DAT 4: Addresses in "Write" request
DAT 5: Error frame data for "Write" (addresses not written; see Section 3.6)
DAT 6: Data, if any, for "Write" response (also see Section 3.6)

4.1 Frame sequence for "Read"

The frame sequence for ”Read” always begins with a request frame for the 1st cutting edge
sent to the encoding station from the SINUMERIK. The tool data for the 1st cutting edge,
required by the SINUMERIK 880 tool management, and the number of cutting edges are
requested in this frame. The number of cutting edges informs the SINUMERIK 880 how many
request frames are needed in order to read all cutting edges.

© Siemens AG 1991 All Rights Reserved 6FC5 197-0AB40-0BP0 4–1

SINUMERIK 840/880 (PJ)
4 Frame Sequences 12.91
4.1 Frame sequence for "Read"

1. "Read" first cutting edge:

SINUMERIK Encoding station

T CB fnr TL S N K I R A DAT 1 "Read" request
(first cutting edge and number
of cutting edges)

T CB F fnr TL S N K I R A DAT 3 Negative response

to "Read" request (error
frame, abort)

R CB fnr TL S N K I R A DAT 2 Positive response

to "Read" request

2. "Read" additional cutting edges:

SINUMERIK Encoding station

T CB fnr TL S N K I R A DAT 1 "Read" request
(for additional cutting edges)

T CB F fnr TL S N K I R A DAT 3 Negative response

to "Read" request (error
frame, abort)

R CB fnr TL S N K I R A DAT 2 Positive response

to "Read" request

4–2 © Siemens AG 1991 All Rights Reserved 6FC5 197-0AB40-0BP0

SINUMERIK 840/880 (PJ)
12.91 4 Frames
4.2 Frame sequence for "Write"

4.2 Frame sequence for "Write"

The frame sequence for transfer of the tool data to the encoding station ("write" tool data)
always begins with a request from the SINUMERIK to the encoding station. The tool data for
the first cutting edge is transferred in this request/response cycle, the tool data for additional
cutting edges in subsequent cycles.

1. "Write" data for first cutting edge:

SINUMERIK Encoding station

T CB fnr TL S N K I R A DAT 1 "Write" request
(first cutting edge)

T CB F fnr TL S N K I R A DAT 3 Negative response

to "Write" request (error frame,
abort)

R CB fnr TL S N K I R A DAT 2 Positive response

to "Write" request

2. "Write" data for additional cutting edges:

SINUMERIK Encoding station

T CB fnr TL S N K I R A DAT 1 "Write" request
(additional cutting edges)

T CB F fnr TL S N K I R A DAT 3 Negative response

to "Write" request (error
frame, abort)

R CB fnr TL S N K I R A DAT 2 Positive response

to "Write" request

© Siemens AG 1991 All Rights Reserved 6FC5 197-0AB40-0BP0 4–3

SINUMERIK 840/880 (PJ)
12.91 5 Concluding Remarks

5 Concluding Remarks

The conventions and stipulations described in Package 7, "Code Carriers, Transfer Tool Data
with Address Encoding", Section 2.3 apply as regards data formats for loading and unloading
tool data (i.e. permissible formats for the various items of tool data when using the
SINUMERIK standard package).
A list of other available data formats (primarily for reading and writing user data) must be
obtained from the manufacturer of the code carrier system.

© Siemens AG 1991 All Rights Reserved 6FC5 197-0AB40-0BP0 5–1

SINUMERIK 840/880 (PJ)
12.91 6 Appendix

6 Appendix

Error codes: Encoding station

A list of error codes must be obtained from the manufacturer of the encoding station.

Error codes: SINUMERIK 880 standard package

Please refer to Package 7:

"Code Carriers, Tool Data with Address Encoding" / FX14 "BEL-CDTR"

© Siemens AG 1991 All Rights Reserved 6FC5 197-0AB40-0BP0 6–1

SINUMERIK 840/880 (PJ)