FBIC
FBIC
motion control
information system
TDI Ident Connection
SINUMERIK 840D/840Di/810D
System Overview 1
Installation 2
Description of Functions
Parameters 6
Services 7
Starting Services 8
Examples 9
Valid for
Appendix A
Control Software version
Sinumerik 840D/840Di/810D 1
Index I
06.03 Edition
SINUMERIK® Documentation
Printing history
Brief details of this edition and previous editions are listed below.
The status of each edition is indicated by the code in the "Remarks" columns.
Trademarks
SIMATIC®, SIMATIC HMI®, SIMATIC NET®, SIROTEC®, SINUMERIK® and SIMODRIVE® are registered
trademarks of Siemens AG. Other names used in this publication may be trademarks, which, if used by third
parties for their own means, could infringe the rights of their owners.
© Siemens AG, 2003. All rights reserved Subject to change without prior notice
Preface
Target group
This documentation is intended for manufacturers of machine tools with the
SINUMERIK 840D/810D and SIMODRIVE 611D.
Hotline
If you have any questions, please call the hotline:
Please send any questions about the documentation (suggestions for improve-
ment, corrections) to the following fax number or email address:
Fax: ++49-9131-98-2176
Email: [email protected]
Fax form: See the reply form at the end of the document.
! Important
This Installation and Start-Up Guide is valid for:
TDI Ident Connection V1.01
Search aids
For your better orientation, we have provided a list of
· References and an
· Index
in the Appendix.
The following warning notes with varying degrees of severity are used in the documentation:
! Danger
Indicates an imminently hazardous situation which, if not avoided, will result in
death or serious injury or in substantial property damage.
! Warning
Indicates a potentially hazardous situation which, if not avoided, could result in
death or serious injury or in substantial property damage.
! Caution
Used with the safety alert symbol indicates a potentially hazardous situation
which, if not avoided, may result in minor or moderate injury or in property
damage.
Caution
Used without safety alert symbol indicates a potentially hazardous situation
which, if not avoided, may result in property damage.
Notice
Used without the safety alert symbol indicates a potential situation which, if not
avoided, may result in an undesirable result or state.
Additional notices
! Important
Appears in the documentation wherever an important fact has to be taken into
account.
Note
Appears in the documentation wherever further references are made.
Machine manufacturer
This pictorial symbol always appears in this document to indicate that the
machine manufacturer can affect or modify the function described. Never ignore
information provided by the machine manufacturer!
Effectiveness of changes
When changing data (e.g. machine data) please also check their effectiveness
(e.g. after power ON or IMMEDIATELY). For that reason, time and date are always
quoted.
Trademarks
IBM® is a registered trademark of the International Business Corporation.
MS-DOS® and WINDOWS™ are registered trademarks of the Microsoft
Corporation.
n
Contents
9.1 Loading from code carrier via PLC interface ................................ 9-82
I Index.................................................................................................. I-115
1 System Overview
The MCIS is made up of functional packages that are used both in production
planning and directly at the production units. The individual packages are scalable,
functionally harmonized, and can be mixed and matched to meet specific functional
requirements.
Using these packages as part of the production process makes your production
facility an integral part of your IT environment.
The MCIS packages provide a modern solution concept that uses both interna-
tionally accepted technologies in the hardware and worldwide standards in the
software modules, methods, and interfaces. A range of process interfaces provides
ideal support for networking and integration of automation and production
equipment. Standardized interfaces in conjunction with standard software ensure
investment protection and subsequent expandability.
· For a single machine, flexible transfer line, or for an entire machine park
· For highly-automated NC controls like SINUMERIK 810D/840D/840Di or for
controls based on SIMATIC S7
· For integration of tool setting stations or factory-wide tool management
systems such as the TDM of Walter
MCIS TDI uses the right connection concepts and functions to provide a complete
overview of the tools used and maintain a closed tool data circuit in production.
MCIS TDI is a modular system from which you can combine the right modules for
every level of automation.
TDI Planning
Planning the tool requirement on the basis of the current tool inventory.
TDI Overview
Recording of actual tool data, evaluation options via the current tool inventory per
filter and manual modification of actual tool data. (The functions for a unit are
included in the standard license of Transline HMI, Version 3.1 and higher).
TDI Machine
Autonomous, non-networking function package for tool planning and coupling to
the tool setting station for transfer of tool data. (This function is not used in
Transline projects and is therefore not discussed further).
Production level
At the production level, all MCIS TDI modules can be used. On the one hand, the
modules offer integrated interfaces (IFC) for communication with the controls; on
the other, they provide interfaces for collecting all tool data, planning tool deploy-
ment and handling tool data.
Variable user interface design allows user interfaces to run both on a Windows PC
and on the operator panels of the SINUMERIK in standard and Transline HMI Pro
environments.
Based on the existing TDI modules, the server functions enable networking of all
units in such a way that an overview of all tool actual data can be displayed, e.g.
on a master control or on a control system.
Furthermore, the functions can be supplemented by the "TDI Interface Client" (IFC)
for coupling to other systems.
The TDI Cell / Plant functions do not merely provide evaluation and monitoring
functions in the foreman’s or executive offices; they are available network-wide. Its
modular structure permits implementation of small or large systems distributed over
several production areas.
In a network solution of this kind, the TDI HMI module can be used under the TDI
Plant module to install all the functions installed in the system as a user frontend on
further client PCs.
1.2.4 Fundamentals
"TDI Ident Connection" can be used to load/unload tools. The tools can be loaded
from the tool cabinet, from the code carrier or from the master computer in the
NCK. Furthermore, the tools can be unloaded from the NCK to the tool cabinet, to
the code carrier or to the master computer.
In addition, services are avaible for deleting tools from the tool cabinet or exporting
them to a file (or importing them from a file to the tool cabinet). It is also possible to
delete tools in the NCK and update the data on the code carrier.
"TDI Ident Connection" is configured via a PLC link and the service started. The
PLC link is set up via the PLC interface in data block DB19. The structure of the
PLC interface is described in Chapter 4.
The service to be executed is defined by the command code entered in the
interface data block. The meaning of the various command codes is described in
Chapter 5. The services associated with the command codes are explained in
Chapter 7. The parameter values required for the individual services must be
specified in the interface data block; these are described in Chapter 6.
The procedures for calling and acknowledging the service are described in Chap-
ter 8. Chapter 9 uses examples to illustrate how the parameters can be assigned
for the various services.
"TDI Ident Connection" is ready for M:N mode, which means that two controls can
address the PLC interface at the same time.
Communication between "TDI Ident Connection" and the host computer is carried
out via "SINCOM".
PLC link
Programming knowledge of Step 7 is requried for the PLC link, since the "TDI Ident
Connection" communicates via a PLC interface.
The services are configured and started via this interface. Furthermore, the status
of the service and error messages are also provided. The interface is described in
detail in Chapter 4.
ParamTM interface
"TDI Ident Connection" provides a separate COM interface for the standard
software "ParamTM".
This interface allows data to be read/written from/to the codechip of a tool.
2 Installation
The PCU50 provides a link to the Siemens tool management interface (ParamTM)
with HMI-Advanced 06.02.10 and higher.
The values specified for storage space needed refer to the requirements for
®
installation. There should still be enough space for Windows to operate properly.
2.1.1 MMC103
· MMC environment Version 05.03.14 or higher must be installed.
· Approx. 30MB free disk space on drive C:
2.1.2 PCU50
· HMI environment Version 06.00.29 or higher must be installed.
· Approx. 20MB free disk space on drive E:
· Approx. 10MB free disk space on drive F:
If the control is integrated in a network, the installation can also be started from
there.
MMC103
® ®
To install, start Windows in Service mode via the Service menu (Windows with
MMC drivers) and then execute SETUP.EXE on the installation CD.
PCU50
®
Windows is started in Service mode and the contents of the installation CD are
®
copied to the D:\Install directory of the PCU50. Windows is then restarted and
Setup is started automatically during booting.
The installation path is determined automatically and the version of the installed
MMC and HMI environment is checked. If none of the software versions specified
in Section 2.1 is installed, Setup is terminated and an appropriate message issued.
®
9. Install the Microsoft database access components.
10. Install the "TDI Ident Connection" software components and required system
files.
11. Update REGIE.INI in the \Add_on directory.
12. Update the installed INI files.
13. Terminate Setup.
When installation is complete, the entries for the selected reader should be
®
checked in the COMTDS.INI file before shutting down Windows and starting the
MMC or HMI environment.
! Important
On some systems, a system reset may be performed following installation of the
® ®
Microsoft database access components. In this case, Windows must be started
again in Service mode. Setup is then started with the /continue parameter at the
point where installation was interrupted.
Note
When a Setup dialog appears on completion of installation prompting to restart
®
Windows , you should do so. When you confirm this dialog box, Setup automa-
®
tically restarts Windows .
The interface to which the reader is connected is selected after selection of the
code carrier reader if the former is operated via the serial interface. The two serial
interfaces COM1 and COM2 are available for selection (see Fig. 2-2).
If the reader is connected to the PLC via Profibus, for example, a dialog box
appears for selecting the number of readers used (see Fig. 2-3). A separate dialog
box (Fig. 2-4) appears for each reader, in which the PLC data block, the offset and
the number of bytes can be specified. The number of bytes depends on the set-
tings in the Wkonvert.txt file, which must also be installed. If there are more than
one reader, Setup recommends settings in which the data ranges of the individual
readers are continuous in the PLC.
On completion of the Setup routine, you should check the parameters for the
reader in the COMTDS.INI file and correct if necessary. This file is located in
\Add_on\IdentCon\ and should be checked after restart of the MMC or HMI
environment.
3 Configuration
3.1 IdentCon.INI
Configuration of "TDI Ident Connection" takes place via the IdentCon.INI file. This
file is located in the \Add_on directory and can be modified using a text editor, for
example NOTEPAD. It is divided into various sections that contain different entries.
The sections and their entries are described in the table below.
If the services are stopped due to a timeout, use the "TimeOut" entry to specify a
longer time. A timeout can occur if the user fails to acknowledge tool loading. The
default time for services is 300 milliseconds.
The entries "DisablePLCInterface", "MoveToolPLC", "MoveToolFirst" and
"MoveToolCancel" are relevant for linking to the SINUMERIK standard software
"ParamTM". "DisablePLCInterface=true" specifies that the "TDI Ident Connection"
is to be addressed only via "ParamTM" per soft key; the PLC interface for
activating the services by specifying a command code is then deactivated. The
entry "MoveToolPLC=true" is used if the tool has to be transported to the reader
before reading/writing the data from/to the code chip. In this case, "TDI Ident
Connection" uses the "ParamTM" PLC interface to communicate with the PLC
program that performs tool transport. "MoveToolFirst=true" moves the tool to the
code chip prior to reading/writing; otherwise, after reading/writing. If the reader is
connected to the PLC (e.g. Profibus), the entry "MoveToolFirst" has no effect. In
this case, the tool data should be transferred by the PLC program in the interface
DB prior to reading and taken from there after writing. MoveToolCancel=true can
be used to stop waiting for the end of tool motion immediately without generating
the error messages. In this case, the cancel bit (DB19.DBX259.2) is set by "TDI
Ident Connection" in the "ParamTM" PLC interface independently of this entry.
The names of the import and export files for importing and exporting tool data are
made up of the "Prefix" and "Extension" entries and the transfer parameter
"FileIndex". These files are located in the directory specified in "ToolsHome" after
exprt and are read from this directory for import. This directory must already exist,
since it is not created automatically. An export file could be called "Tools_4711.txt"
for example, if the above data are used and specified as "FileIndex 4711".
Normally, the "DataBlocks" need not exist, since "TDI Ident Connection" uses the
data blocks and offsets described in the following chapters per default. These are
set up in the PLC using the STL file supplied (see Section 2.3).
The higher the "LogLevel" entry, the more messages are stored in the log file
IdentCon.Log. This file is used for diagnostics and contains information on incorrect
transfer parameters, for example. In parallel with this log file, the error file
IdentCon.err is created, which contains only error messages.
3.2 TMS.INI
The entries "MergeDBData" and "MergeNCKData" in the "TMS.INI" file can be
used to define whether tool data are to be combined with data from the tool cabinet
or from the NCK (tool list), if these data are not supplied with the tool.
With the default setting, tool data that are not present on the data source (code
carrier, import file or host computer) are preassigned the default data from the
"DefToolDat.txt" data (see Section 3.5).
Furthermore, the entries for loading and unloading place numbers of the loading
magazine made during installation can be changed to the entries for
"LoadPlaceNo" and "UnloadPlaceNo" (see Subsection 2.2.4).
The "Messaging" entry specifies which messages are stored in the protocol file
"TMS.Log". This file is used for diagnostics and contains information on the cause
of an error that occurs. In parallel with this protocol file, the error file "TMS.err" is
created, which contains only error messages. The setting "Messaging=3" also
creates the "TMS.txt" file, which contains the tool data in the familiar NC-$ syntax
that were transferred with the "TDI Ident Connection" services.
Note
For performance reasons, the entry "Messaging =3" should not be used in normal
mode but only for fault diagnostics.
If necessary, the files "TMS.Log", "TMS.sav", "TMS.txt" and "TMSalt.txt" should
be sent to the hotline for diagnostics.
! Important
For correct operation of "TDI Ident Connection", only the entries described in the
table below should be modified.
3.3 COMTDS.INI
The "COMTDS.INI" file contains the parameters for the components that
communicate with the reader. It is split up into sections that can be configured to
match the reader. Not all sections are required for each reader however. This file is
also located in the directory \Add_on\IdentCon.
! Important
This file normally does not have to be modified, since all default settings are
made automatically during installation.
The COM interface to which the reader is connected must also be configured for
this reader.
The COM interface to which the reader is connected must also be configured for
this reader.
Default:
Balluff-V24: PORT = 1
Barcode: PORT = 1
Baud Baudrate for data transmission
0: 300
1: 1200
2: 2400
3: 4800
4: 9600
5: 19200
6: 38400
7: 57600
8: 115200
Default:
Balluff-V24: Baud = 4
Barcode: Baud = 4
DataBits Number of data bits per transferred byte
0: 5 data bits
1: 6 data bits
2: 7 data bits
3: 8 data bits
Default:
Balluff-V24: DataBits = 3
Barcode: DataBits = 3
Parity Specifies the parity checking
0: None
1: Even parity
2: Uneven parity
Default:
Balluff-V24: Parity = 1
Barcode: Parity = 0
Default:
Balluff-V24: StopBits = 0
Barcode: StopBits = 0
FlowControl Specifies the method of data flow control used
0: None
1: Xon/Xoff
2: RTS/CTS
Default:
Balluff-V24: FlowControl = 0
Barcode: FlowControl = 2
The description file can be created as an ASCII file using a standard text editor.
The path and name of the description file is given in the "TMS.INI" file under the
entry "WkonvertFile".
Note
C38 and C39 can only be used as alternatives for C29 and C30
and C40, C41 and C42 can only be used as alternatives for C31, C32 and C34.
Tool user parameters and the new monitoring parameters are now also used for
code carriers. The following new configuration variables are available for the file
"wkonvert.txt":
Data on the code carrier that are not relevant for the tool management but must not
be altered when writing to the code carrier, are marked with a dash ( – ) instead of
the dialog variable in the description file (e.g. data gaps).
Data types
The following data types are defined for dialog variables:
· Integer: Value range –32768 to 32767
· Double: Floating-point double exact
· String: String made up of ASCII characters
Keywords
The code carrier description file is used to assign code carrier data to the dialog
data. This file is an ASCII file, which can be created and edited using a standard
text editor. The code carrier description file is structured line-by-line and each line
denoted by one of the following keywords:
Quotation marks
The single quotation mark (’) marks the beginning of a comment. The characters
that follow are skipped.
Example:
’ This is a comment
Note
This format for the beginning of a comment is used only in the description file for
code carriers. Otherwise, the beginning of a comment is introduced by a semi-
colon (;).
Datalen
DATALEN=CONST | VARIABLE 0x<delimiter>
The following data have a constant (CONST) or a variable (VARIABLE) data
length. Data with variable length are terminated with 0x<delimiter>.
Example:
Item
Item<n>=<line>
<n> := consecutive number of code carrier data, in ascending order from 1 without
gaps
<line> := <(max.) length in bytes> <code carrier data format> <dialog variable>
<code carrier data format> :
<dialog variable> : Assignment of code carrier to dialog data
Example:
BItem1 1 BCD C1
Block
Block<n> <repetition rule>
<n> := consecutive number of block, in ascending order from1 without gaps
<repetition rule> := * Item<n>
A block of data BItem<n> follows (up to the keyword End_Block<n>), which are
stored on the code carrier according to the <repetition rule>.
Note
For block <n> * Item <n>, Item <n> must be defined before block <n>.
Example:
Block1 * Item6 ’ Repeat Block1 according to the value of Item6
End_Block<n>
End_Block
End ID for a data block defined with Block<n>.
The conversion rule for Item<n> or BItem<n> also contains the assignment to
none/one/several dialog variables, if necessary with a conversion that is explained
in detail in this section. The general conversion rule for Item<n> and BItem<n> is
as follows:
(B)Item<n>=<line>
<n> := consecutive number of code carrier data,
in ascending order without gaps
<line> := <(max.) length in bytes><code carrier data format>
<dialogvariable>
Dialog variable
<dialogvariable> := <dvar1>[=(<uv>)] [, <dvar2>[=(<uv>)] [,<dvar3>
[&<dvar4>]=(<uv>)] [, <dvarN>[=(<uv>)]
<dvar> := T<index> | C<index> | –
T = tool data,
C = cutting edge data,
index = index in tool/cutting edge data
– = no assignment to a dialog variable
<dvar1>&<dvar2>=<uv> : conversion rule applies to <dvar1> and <dvar2>
uv := <Tetn>
th
Tetn := n tetrad in byte sequence
Byte1, = Tet1 and Tet2
Byte2, = Tet3 and Tet4
Allocation of the tetrads of code carrier variables (in BCD format) to dialog
variables.
Example:
T5=(Tet1), T6=(Tet2), T7=(Tet3), T8=(Tet4)
If the code carrier has the value 0x1234 for example, dialog variable T5 is assigned
the value 1, dialog variable T8 the value 4.
Example with tool and cutting edge OEM data, and data gaps
Table 3-12 Example
This file contains the data of a default tool with one cutting edge in familiar NC-$
syntax. After installing "TDI Ident Connection", all optional tool data (i.e. all OEM
data, cutting edge monitoring data and local additive offsets) are marked with a
comment character (;) and are thereby deactivated.
So the user should always adapt the contents of "DefToolDat.txt". Remove the
comment characters in front of the relevant optional tool data to match their
number to the existing NCK configuration. The value assigned to these tool data in
the file can also be modified to meet user requirements.
If the number of active optional tool data in DefToolDat.txt exceeds the number of
relevant data configured in the NC, MMC alarms 121005 to 121009 are generated
on start of "TDI Ident Connection".
These alarm numbers are assigned to the individual data groups as follows:
· Alarm No. 121005 – Tool OEM data
· Alarm No. 121006 – Cutting edge OEM data
· Alarm No. 121007 – Cutting edge monitoring data
· Alarm No. 121008 – Cutting edge OEM monitoring data
· Alarm No. 121009 – Cutting edge additive offsets
The texts assigned to these alarms can be defined by the user in the "Alm_xx.com"
files.
If the number of these tool and cutting edge data configured in the NC is greater
than the number of corresponding active data in DefToolDat.txt, partially invalid
negative data values are transferrred to the data target for the services of "TDI
Ident Connection". This enables identification of non-initialized tool data.
! Important
Loading a tool to a magazine that contains invalid data of type Double produces
NC alarm 1019.
4.1 Layout
The "TDI Ident Connection" is addressed and supplied with data via a PLC
interface located in data block DB19 (see Fig. 4-1).
A further area contains the transfer and return parameters for the various services.
In addition, a separate PLC interface is provided for the "ParamTM" interface of the
"TDI Ident Connection". It is used to communicate with a PLC program. The
parameters for this PLC program and the status bits are also located in this area.
During startup of "TDI Ident Connection", the request bit is set to "0" to prevent a
service being started inadvertently, for example if the control is deactivated during
execution of a service.
If the request bit has already been set, it is reset and the error code 0xFFFF written
to the Error_Code word in the PLC.
The parameter values permitted for the individual services may vary and are
therefore specified separately for each service in Chapter 7.
The values for the magazine, magazine place and T number of the tool are only
written to this PLC interface of the "TDI Ident Connection" when writing to the code
carrier (e.g. when unloading the tool with "ParamTM").
5 Command Codes
5.1 Description
Table 5-1 Description of command codes
C code Description
0 Load from code carrier
1 Unload to code carrier
2 Load from tool cabinet
3 Unload to tool cabinet
4 Load from host computer
5 Unload to host computer
6 Unload all tools to tool cabinet
7 Load tool
8 Unload tool
9 Search for empty location
10 Clear tool in NCK
11 Clear tool in database
12 Export tool data
13 Import tool data
14 Update code carrier
15 Read data from code carrier
16 Store tool data in NCK
6 Parameters
6.1 Description
Table 6-1 Description of parameters
Parameter Description
ActiveEnable Transfer of the tool status bit from the database to the NCK
(TRUE) / Hide the status bit during transfer (FALSE)
Channel Channel number
DeleteTool Delete tool after unloading (TRUE) / do not delete (FALSE)
Duplo Duplo number
FileIndex Index of file to be used for import/export. The file name
extended by the index can be specified in the INI file.
Ident Tool name
LoadingPlace Number of load/unload place in loading magazine
LoadTool Load tool after reading (TRUE) / do not load (FALSE)
Magazine Magazine number
MagazinePlace Magazine place number of tool
MagazinePlaceType Magazine place type
NCU_Index Index of the NCU to be addressed for the job. The fol-
lowing values are permissible:
0 à NCU name from IdentCon.INI
1 à NCU1
2 à NCU2
>2 à MachineSwitch
The names for NCU1 and NCU2 are determined from the
NETNAMES.INI file.
Override Overwrite export file (TRUE) / extend (FALSE)
Subtype Subtype or type
TNumber T number
ToolSize_Down Tool size down in half locations
ToolSize_Left Tool size left in half locations
ToolSize_Right Tool size right in half locations
ToolSize_Upper Tool size upper in half locations
ToolState Tool state
Unit Code carrier unit (reader/writer) to be read or written.
Depending on unit: 1..4
7 Services
If the "Magazine" parameter is assigned the value "0", the tool is loaded to the
magazine that has an empty location.
If the value for "MagazinePlace" > 0, an attempt is made to load the tool to this
magazine place.
Transfer parameters
DBW 180 MagazinePlace INT 0...32000 Magazine place number
DBB 188 Channel BYTE 1...127 Channel number
DBB 189 LoadPlace BYTE 1...127 Load place number
DBW 190 Magazine INT 0...32000 Magazine number
DBB 192 Unit BYTE 1...127 Number of reader
DBB 193 NCU_Index BYTE 0...127 Index of NCU
DBX 196.2 LoadTool BOOL TRUE, Load tool after creating?
FALSE
Return parameters
DBW 198 Subtype INT 1...32000 Subtype
DBW 200 Duplo INT 0...32000 Duplo number
DBB 202 Ident String 32 chars Tool identifier
DBW 236 TNumber INT 0...32000 T number
DBW 238 ToolState INT 0...32000 Status of tool
DBW 240 MagazinePlace INT 0...32000 Magazine place type
Type
DBB 242 ToolSize_Upper BYTE 1...127 Tool size upper in half loca-
tions
DBB 243 ToolSize_Down BYTE 1...127 Tool size down in half loca-
tions
DBB 244 ToolSize_Left BYTE 1...127 Tool size left in half locations
DBB 245 ToolSize_Right BYTE 1...127 Tool size right in half locations
DBW 246 Magazine INT 0...32000 Magazine number
DBW 248 MagazinePlace INT 0...32000 Magazine place number
If the "Magazine" parameter is assigned the value 0, the tool is unloaded from any
one of the magazines.
If the "Magazine" and "MagazinePlace" parameters are set > 0", an attempt is
made to unload the tool located at this place. The "Duplo" and "Ident" parameters
are not considered.
The number of the unload place in the unload magazine is used to do this if
"LoadPlace" > 0. If "LoadPlace" = 0 is set, however, the value of the keyword
"UnloadPlaceNo" in the file "TMS.INI" is used as unload place number.
Transfer parameters
DBW 142 Duplo INT 1...32000 Duplo number
DBB 144 Ident String 32 characters Tool identifier
DBW 180 Magazine- INT 0...32000 Magazine place number
Place
DBB 188 Channel BYTE 1...127 Channel number
DBB 189 LoadPlace BYTE 1...127 Unload place number
DBW 190 Magazine INT 0...32000 Magazine number
DBB 192 Unit BYTE 1...127 Number of reader
DBB 193 NCU_Index BYTE 0...127 Index of NCU
DBX 196.3 DeleteTool BOOL TRUE, FALSE Delete tool after unload?
Return parameters
None
This is generally the case when low-cost, read-only code chips are used.
Reads the tool data from the database and creates the tool in the NCK if it does
not already exist. The "Subtype", "Duplo" and "Ident" parameters need not be as-
signed. If "Subtype" and "Duplo" are not assigned, they must be specified as "-1".
"Ident" is specified as a blank string if it is not to be assigned.
If "Subtype", "Ident" or "Duplo" are not assigned uniquely, several tools can be
found in the database.
If several selected tools are to be loaded using this service and the T number is
specified greater than "0", the desired tool number is incremented successively. It
is not checked whether these incremented tool numbers are free in the NCK.
The "TNumber" parameter has no effect if the tool already exists in the tool list.
The "ActiveEnable" parameter defines how the tool status bit "T active" is handled.
If this parameter is set (TRUE), this status bit is taken into the NCK unchanged
from the database. If "ActiveEnable" is FALSE, however, this status bit is hidden on
reading from the database and is therefore not entered as set in the NCK.
If the magazine number is specified as "0", the tool/s is/are loaded to the magazine
that has an empty location if LoadTool is set. The number of the load place in the
unload magazine is used to do this if "LoadPlace" > 0. If "LoadPlace" = 0 is set,
however, the value of the keyword "LoadPlaceNo" in the file "TMS.INI" is used as
load place number.
If the value for "MagazinePlace" > 0, an attempt is made to load the tool to this
magazine place.
The parameters for this service are shown in the table below. Depending on the
parameter value, several tools can be loaded to the NCK from the database at the
same time. An overview of the possible parameters is given in Table 7-4.
Transfer parameters
DBW 140 Subtype INT -1, 1...32000 Subtype
DBW 142 Duplo INT -1...32000 Duplo number
DBB 144 Ident String 32 chars Tool identifier
DBW 178 TNumber INT 0...32000 T number
DBW 180 Magazine- INT 0...32000 Magazine place number
Place
DBB 188 Channel BYTE 1...127Channel number
DBB 189 LoadPlace BYTE 1...127Load place number
DBW 190 Magazine INT 0...32000
Magazine number
DBB 193 NCU_Index BYTE 0...127Index of NCU
DBX 196.0 ActiveEn- BOOL TRUE, FALSE
Hide NCK status bits "T
able active"?
DBX 196.2 LoadTool BOOL TRUE, FALSE Load tool after creating?
Return parameters
DBW 198 Subtype INT 1...32000 Subtype
DBW 200 Duplo INT 0...32000 Duplo number
DBB 202 Ident String 32 chars Tool size identifier
DBW 236 TNumber INT 0...32000 T number
DBW 238 ToolState INT 0...32000 Status of tool
DBW 240 Magazine- INT 0...32000 Magazine place type
PlaceType
DBB 242 ToolSize_ BYTE 1...127 Tool size upper in half
Upper locations
DBB 243 ToolSize_ BYTE 1...127 Tool down in half locations
Down
DBB 244 ToolSize_ BYTE 1...127 Tool size left in half locations
Left
DBB 245 ToolSize_ BYTE 1...127 Tool size right in half locations
Right
DBW 246 Magazine INT 0...32000 Magazine number
DBW 248 Magazine- INT 0...32000 Magazine place number
Place
Table 7-4 Parameter combinations for "Loading from the tool cabinet"
This is generally the case when low-cost, read-only code chips are used.
Unloads the tool identified by "Ident" from the NCK to the tool cabinet. The "NCU",
"Channel", "Ident", "Duplo" and "Magazine" parameters must be assigned.
If the magazine number is specified as "0", the tool is unloaded from any
magazine.
If the value for "MagazinePlace" > 0, an attempt is made to unload the tool from
this magazine place.
The number of the unload place in the unload magazine is used to do this if
"LoadPlace" > 0. If "LoadPlace" = 0 is set, however, the value of the keyword
"UnloadPlaceNo" in the file "TMS.INI" is used as unload place number.
The tool in the NCK is deleted after successful unloading if "DeleteTool" was set.
Transfer parameters
DBW 142 Duplo INT 1...32000 Duplo number
DBB 144 Ident String 32 characters Tool identifier
DBW 180 Magazine- INT 0...32000 Magazine place number
Place
DBB 188 Channel BYTE 1...127 Channel number
DBB 189 LoadPlace BYTE 1...127 Unload place number
DBW 190 Magazine INT 0...32000 Magazine number
DBB 193 NCU_Index BYTE 0...127 Index of NCU
DBX 196.3 DeleteTool BOOL TRUE, FALSE Delete tool after unload?
Return parameters
None
If the magazine number is specified as "0", the tool is loaded to the magazine that
has an empty location if LoadTool is set. The number of the load place in the un-
load magazine is used to do this if "LoadPlace" > 0. If "LoadPlace" = 0 is set,
however, the value of the keyword "LoadPlaceNo" in the file "TMS.INI" is used as
load place number.
If the value for "MagazinePlace" > 0, an attempt is made to load the tool to this
magazine place.
Transfer parameters
DBW 142 Duplo INT 1...32000 Duplo number
DBB 144 Ident String 32 characters Tool identifier
DBW 180 Magazine- INT 0...32000 Magazine place number
Place
Return parameters
DBW 198 Subtype INT 1...32000 Subtype
DBW 200 Duplo INT 0...32000 Duplo number
DBB 202 Ident String 32 characters Tool identifier
DBW 236 TNumber INT 0...32000 T number
DBW 238 ToolState INT 0...32000 Status of tool
DBW 240 Magazine- INT 0...32000 Magazine place type
Place Type
DBB 242 ToolSize_ BYTE 1...127 Tool size upper in half
Upper locations
DBB 243 ToolSize_ BYTE 1...127 Tool size down in half
Down locations
DBB 244 ToolSize_ BYTE 1...127 Tool size left in half
Left locations
DBB 245 ToolSize_ BYTE 1...127 Tool size right in half
Right locations
DBW 246 Magazine INT 0...32000 Magazine number
DBW 248 Magazine- INT 0...32000 Magazine place number
Place
If the magazine number is specified as "0", the tool is unloaded from any magazine
and then deleted if "DeleteTool" is set.
If the value for "MagazinePlace" > 0, an attempt is made to unload the tool from
this magazine place.
The number of the unload place in the unload magazine is used to do this if
"LoadPlace" > 0. If "LoadPlace" = 0 is set, however, the value of the keyword
"UnloadPlaceNo" in the file "TMS.INI" is used as unload place number.
Transfer parameters
DBW 142 Duplo INT 1...32000 Duplo number
DBB 144 Ident String 32 characters Tool identifier
DBW 180 Magazine- INT 0...32000 Magazine place number
Place
DBB 188 Channel BYTE 1...127 Channel number
DBB 189 LoadPlace BYTE 1...127 Unload place number
DBW 190 Magazine INT 0...32000 Magazine number
DBB 193 NCU_Index BYTE 0...127 Index of NCU
DBX 196.3 DeleteTool BOOL TRUE, Delete tool after unload?
FALSE
Return parameters
None
The data of all loaded tools in the specified magazine are read from the NCK and
written to the database. The tools are then unloaded from the magazine and
deleted.
The "NCU_Index", "Channel "and "Magazine" parameters must be assigned.
If the magazine with number "0" is specified, all the loaded tools are unloaded from
all magazines present in the NCK; the spindle magazine is also considered. The
order for unloading corresponds to the order in which the tools were loaded.
Table 7-8 Parameters for "Unloading all tools from tool cabinet"
Transfer parameters
DBB 188 Channel BYTE 1...127 Channel number
DB 190 Magazine INT 0...32000 Magazine number
W
DBB 193 NCU_Index BYTE 0...127 Index of NCU
Return parameters
None
The tool specified by "Channel", "Duplo" and "Ident" is loaded to the tool magazine
specified by "Magazine". "NCU_Index" specifies the NCU.
If "0" is specified as the magazine number, the next free magazine place that can
be used for the tool is located.
If the value for "MagazinePlace" > 0, an attempt is made to load the tool to this
magazine place.
The number of the load place in the unloading magazine is used to do this if
"LoadPlace" > 0. If "LoadPlace" = 0 is set, however, the value of the keyword
"LoadPlaceNo" in the file "TMS.INI" is used as load place number.
Transfer parameters
DBW 142 Duplo INT 1...32000 Duplo number
DBB 144 Ident String 32 characters Tool identifier
DBW 180 Magazine- INT 0...32000 Magazine place number
Place
DBB 188 Channel BYTE 1...127 Channel number
DBB 189 LoadPlace BYTE 1...127 Load place number
DBW 190 Magazine INT 0...32000 Magazine number
DBB 193 NCU_Index BYTE 0...127 Index of NCU
Return parameters
None
If the value for "MagazinePlace" > 0, an attempt is made to unload the tool from
this magazine place.
The number of the unload place in the unload magazine is used to do this if
"LoadPlace" > 0. If "LoadPlace" = 0 is set, however, the value of the keyword
"UnloadPlaceNo" in the file "TMS.INI" is used as unload place number.
Transfer parameters
DBW 142 Duplo INT 1...32000 Duplo number
DBB 144 Ident String 32 characters Tool identifier
DBW 180 MagazinePlace INT 0...32000 Magazine place
number
DBB 188 Channel BYTE 1...127 Channel number
DBB 189 LoadPlace BYTE 1...127 Unload place number
DBW 190 Magazine INT 0...32000 Magazine number
DBB 193 NCU_Index BYTE 0...127 Index of NCU
DBX 196.3 DeleteTool BOOL TRUE, Delete tool after
FALSE unload?
Return parameters
None
When the "TNumber" is specified, the requried tool data are fetched from the tool
list and a free tool place is loacted.
If the magazine is assigned the value "0", the next free tool place is searched for in
all magazines.
Transfer parameters
DBW 142 Duplo INT 1...32000 Duplo number
DBB 144 Ident String 32 characters Tool identifier
DBW 178 TNumber INT 0...32000 T number
DBB 188 Channel BYTE 1...127 Channel number
DBW 190 Magazine INT 0...32000 Magazine number
DBB 193 NCU_Index BYTE 0...127 Index of NCU
Return parameters
DBW 198 Subtype INT 1...32000 Subtype
DBW 200 Duplo INT 0...32000 Duplo number
DBB 202 Ident String 32 characters Tool identifier
DBW 236 TNumber INT 0...32000 T number
DBW 238 ToolState INT 0...32000 Status of tool
DBW 240 MagazinePlace INT 0...32000 Magazine place type
Type
DBB 242 ToolSize_ BYTE 1...127 Tool size upper in half
Upper locations
DBB 243 ToolSize_Down BYTE 1...127 Tool size down in half
locations
DBB 244 ToolSize_Left BYTE 1...127 Tool size left in half
locations
DBB 245 ToolSize_Right BYTE 1...127 Tool size right in half
locations
DBW 246 Magazine INT 0...32000 Magazine number
DBW 248 MagazinePlace INT 0...32000 Magazine place
number
Transfer parameters
DBW 142 Duplo INT 1...32000 Duplo number
DBB 144 Ident String 32 characters Tool identifier
DBW 178 TNumber INT 0...32000 T number
DBB 188 Channel BYTE 1...127 Channel number
DBB 193 NCU_Index BYTE 0...127 Index of NCU
Return parameters
None
The "Subtype", "Ident" and "Duplo" parameters need not be assigned. If "Subtype"
and "Duplo" are not assigned, they must contain the value "-1". "Ident" is specified
as a blank string if no particular tool is to be deleted.
If "Duplo" is not assigned, all tools with the relevant identifier and subtype are de-
leted in the database. If the "Duplo" number is specified as "0", both the master
data and application data are deleted.
If "Duplo" and "Ident" are not specified, all tools of the relevant subtype are deleted
in the cabinet.
If the subtype < 10 and "Duplo" and "Ident" are not assigned, the tool type is de-
leted. For example, all milling tools are deleted for the value "1".
With "Subtype -1", if a blank string is specifed for the identifier and "-1" for the
"Duplo" number, the entire tool cabinet is deleted.
If the subtype is "-1", the identifier a blank string and the "Duplo" number = "0", the
entire tool catalog and tool cabinet are deleted.
Transfer parameters
DBW 140 Subtype INT -1, 1...32000 Subtype
DBW 142 Duplo INT -1...32000 Duplo number
DBB 144 Ident String 32 characters Tool identifier
Return parameters
None
The "Subtype", "Ident" and "Duplo" parameters need not be assigned. If "Subtype"
and "Duplo" are not assigned, they must contain the value "-1". "Ident" is specified
as a blank string if no particular tool is to be exported.
If "Duplo" is not specified, all tools with the relevant identifier and subtype are
exported.
If "Duplo" and "Ident" are not specified, all tools of the relevant subtype are
exported.
If the "Subtype" is less than "10" and "Duplo" and "Ident" are not assigned, the
entire tool type is exported. For example, all mill types are exported if the value
is "1".
If the "Subtype" is less than "10" and "Duplo" and "Ident" are not assigned, the
entire tool type is exported. For example, all mill types are exported if the value
is "1".
All tools in the selected range are saved in the file whose index is specified in
FileIndex. It should be checked whether some of the tools whose data are to be
exported are loaded in the NCK. The current data from the loaded tools are read
from the NCK and updated in the database before these data are written to the file.
Transfer parameters
DBW 140 Subtype INT -1, 1...32000 Subtype
DBW 142 Duplo INT -1...32000 Duplo number
DBB 144 Ident String 32 characters Tool identifier
DBW 194 FileIndex INT 0...32000 File index for export
DBX 196.1 Override BOOL TRUE, FALSE Overwrite file if it exists?
Return parameters
None
Only the index of the file from which the data are to be imported is specifed as
parameter in the file "FileIndex".
The import is only made to the tool cabinet as a rule. If a tool is not yet known in
the database, it is also imported to the catalog.
If tools from those to be imported are already loaded in the NCK, import of the
record for these tools is rejected with an error message and an alarm triggered via
the alarm server. The relevant records are skipped in the import file.
Transfer parameters
DBW 194 FileIndex INT 0...32000 File index for import
Return parameters
None
The data of the tool specified by the "NCU_Index", "Channel", "Duplo", "Ident",
"Magazine" and "MagazinePlace" are read from the NCK and written to the code
carrier of the tool. The code carrier is defined via Unit.
If "0" is transferred for magazine, the tool is searched for in all magazines. If
"MagazinePlace = 0" is also specified, the tool specified with "Duplo" and "Ident" is
only searched for in the tool list.
If the "Magazine" and "MagazinePlace" parameters are set > 0", an attempt is
made to unload the data of the tool located at this place. The "Duplo" and "Ident"
parameters are not considered in this case.
Transfer parameters
DBW 142 Duplo INT 1...32000 Duplo number
DBB 144 Ident String 32 characters Tool identifier
DBW 180 MagazinePlace INT 0...32000 Magazine place
number
DBB 188 Channel BYTE 1...127 Channel number
Return parameters
None
This makes it possible to read the two data of a code chip on which only the
"Duplo" number and tool identifier are stored. The load/unloaded services, for
example, can then be called from the tool cabinet (Sections 7.3 and 7.4).
Table 7-19 Parameters for "Reading data from the code carrier"
Transfer parameters
DBB 192 unit BYTE 1...127 Number of reader
Return parameters
DBW 198 Subtype INT 1...32000 Subtype
DBW 200 Duplo INT 0...32000 Duplo number
DBB 202 Ident String 32 characters Tool identifier
DBW 236 TNumber INT 0...32000 T number
DBW 238 ToolState INT 0...32000 Status of tool
DBW 240 MagazinePlace INT 0...32000 Magazine place type
Type
DBB 242 ToolSize_Upper BYTE 1...127 Tool size upper in half
locations
DBB 243 ToolSize_Down BYTE 1...127 Tool size down in half
locations
DBB 244 ToolSize_Left BYTE 1...127 Tool size left in half
locations
DBB 245 ToolSize_Right BYTE 1...127 Tool size right in half
locations
DBW 246 Magazine INT 0...32000 Magazine number
DBW 248 MagazinePlace INT 0...32000 Magazine place
number
If the "Magazine" parameter is assigned the value "0", the tool is loaded to the
magazine that has an empty location.
If the value for "MagazinePlace" > 0, an attempt is made to load the tool to this
magazine place.
After executing the service, the current tool data are returned in the Return
parameters.
Transfer parameters
DBW 180 MagazinePlace INT 0...32000 Magazine place
number
DBB 188 Channel BYTE 1...127 Channel number
DBB 189 LoadPlace BYTE 1...127 Load place number
DBW 190 Magazine INT 0...32000 Magazine number
DBB 193 NCU_Index BYTE 0...127 Index of NCU
DBX 196.2 LoadTool BOOL TRUE, FALSE Load tool after
creating?
Return parameters
DBW 198 Subtype INT 1...32000 Subtype
DBW 200 Duplo INT 0...32000 Duplo number
DBB 202 Ident String 32 chars Tool identifier
DBW 236 TNumber INT 0...32000 T number
DBW 238 ToolState INT 0...32000 Status of tool
DBW 240 MagazinePlace INT 0...32000 Magazine place type
Type
DBB 242 ToolSize_ BYTE 1...127 Tool size upper in half
Upper locations
DBB 243 ToolSize_Down BYTE 1...127 Tool size down in half
locations
DBB 244 ToolSize_Left BYTE 1...127 Tool size left in half
locations
DBB 245 ToolSize_Right BYTE 1...127 Tool size right in half
locations
DBW 246 Magazine INT 0...32000 Magazine number
DBW 248 MagazinePlace INT 0...32000 Magazine place
number
8 Starting Services
This sequence is illustrated in a pulse diagram in the figure below. It shows the bits
that are set and reset during execution of the service by "TDI Ident Connection".
Setting the request bit (Req) starts the service specified via the command code.
Then the active bit is set to show that the job is being processed. When success-
fully completed, the "Done" bit is set and the "Active" bit reset.
In the event of an error, the "Error" bit is set and an error message written to the
relevant PLC word; the "Active" bit is also reset in this case.
After the PLC has reset the "Request" bit, the "Done" or "Error" is reset again. In
addition, the "Error" word is set ot "0", i.e. the PLC must evaluate the error mes-
sage before resetting the request bit.
! Important
While executing the service, the "Request" bit must not be reset by the PLC. A
reset is only possible when the "Active" bit of "TDI Ident Connection" has been
reset and the "Done" or "Error" bit is set.
9 Examples
9.1 Loading from code carrier via PLC interface ................................ 9-82
The transfer parameter required for this service is shown in Table 9-1. The return
parameter from "TDI Ident Connection" is shown in Table 9-2.
Before executing the service, the PLC writes the value "0" in the command code
byte (C_Code) of the PLC interface in data block DB19. This service is then started
by setting the "Request" bit. If the "Active" bit is reset and the "Done" bit set, the
error byte can be evaluated by the PLC. The "Request" must be reset again. This
sequence is illustrated in Table 9-3.
The transfer parameters required are shown in Table 9-4. This service does not
return any parameters, so there are no new values in the return parameters of the
PLC interface.
Before executing the service, command code "1" must be written to the relevant
PLC byte (C_Code). The procedure for starting the service and further handling is
equivalent to Section 9.1. The sequence is illustrated in Table 9-5.
...acknowledges PI service
...writes error code in the error_code
word of the PLC interface (in event of
error, not equeal to 0)
...sets the done or error bit
(done bit = "1" or error bit = "1")
...resets active bit (active bit = "0")
...waits for end of request (request bit
from 1->0)
...evaluates done and error bits and, if
necessary error_code
...resets request bit
(request bit = "0")
...receives end of request
(request bit = "0")
...resets done and error bits
(done bit = "0" and error bit = "0")
...deletes error code
(error_code word = "0")
...waits for request from PLC
(request bit from 0->1)
: :
Sequence of operations
1 6
MMC.A_ReqMMC1
DB19.DBX250.0
Tool data in DB126
MMC.A_K_Code=0
DB19.DBB251
MMC.E_Active 2
DB19.DBX252.2
2 7
MMC.E_Done
DB19.DBX252.0
3 5
TMLoadlf.IfNo(2)
DB71.DBX0.1
3
TMLoadlf.If(2).Loading
DB71.DBX34.0
4
Acknowledge
FC8
Function triggered by user
Return message from "TDI Ident Connection"
Loading order "TDI Ident Connection" generated via NCK
Acknowledgement for loading order through user
Signal change by PLC basic program
Acknowledgement by user
Resetting of "TDI Ident Connection"
Pulse diagram
1 6
MMC.A_ReqMMC1
DB19.DBX250.0 8
Tool data in DB126
(writes IdenCon)
MMC.A_K_Code=1
DB19.DBB251
MMC.E_Active 2
DB19.DBX252.2
2 7
MMC.E_Done
DB19.DBX252.0
3 5
TMLoadlf.IfNo(2)
DB71.DBX0.1
3
TMLoadlf.If(2).Loading
DB71.DBX34.1
4
Acknowledge
FC8
Function triggered by user
Return messag from "TDI Ident Connection"
Loading order of "TDI Ident Connection" generated via NCK
Acknowledgement for loading order through user
Signal change by PLC basic program
6 Acknowledgement by user
7 Resetting of "TDI Ident Connection"
8 "TDI Ident Connection" reads tool data and writes it in DB
Sequence of operations
Pulse diagram
MMC.E_Read
DB19.DBX259.0 2
Machine: Tool data
from code carrier
3 5
MMC.A_Done
DB19.DBX258.0
2
Tool data in DB126
Softkey "Start"
6 8
TMLoadlf.IfNo(2)
DB71.DBX0.1
6
TMLoadlf.If(2).Loading
DB71.DBX34.0
7
Acknowledge FC8
Sequence of operations
Done
DB19.DBX258.0
Error
DB19.DBX258.1
Req = 0
DB19.DBX256.0
1) is not evaluated by "TDI Ident Connection"
Pulse diagram
MMC.E_Write
DB19.DBX259.0
5
Machine: Write tool
data to code carrier
6 8
MMC.A_Done
DB19.DBX258.0
3
1
TMLoadlf.IfNo(2)
DB71.DBX0.1
1
TMLoadlf.If(2)
Unloading
2
Acknowlegde FC8
A Appendix
Should the error code be displayed in decimal format, it must be converted to the
hexadecimal format in order to be able to find the cause of the error in tables A-1 to
A8.
The error code in "C_CodeError" identifies the command code, where the error
occurred.
The error codes "Error_Code" are formed by a High-Byte and a Low-Byte, which
have different meanings. The High-Byte (XX) identifies the type-of-error group, in
which the error occurred. The Low-Byte (YY) indicates the error cause, which is
responsible for job abortion.
Error cause
01 Error while reading the parameters from DB19
02 Error while calling the internal service
03 Timeout during execution of the service
04 No tool data have been defined so far
05 Error while executing the internal service
... Spare
Error in transfer parameter
10 Subtype
11 Duplo
12 Ident
13 TNumber
14 MagazinePlace
15 MagazinePlaceType
16 ToolSize_Upper
17 ToolSize_Down
18 ToolSize_Left
19 ToolSize_Right
1A Channel
1B Magazine
1C unit
1D NCU_Index
1E FileIndex
1F ActiveEnable
20 Override
21 LoadTool
22 DeleteTool
23 Length of Ident
... Spare
Error cause
71 Check digit error (reading before writing)
72 Comparison error (writing, last page)
73 Non-BCD characters found in written data received
74 Non-BCD characters found on data carrier
75 Unknown command, not from the scope of 'I', 'O'
76 Desired initial address for Code 2 not found
77 The specified length could not be read
78 The specified length could not be written
79 End identifier \264//\264 not found (DB format)
7A End identifier \264//\264 not found. Length not read
7B Unknown identifier in protocol D header
7C Data end identifier '/' not found, data length > 31
7D Address end identifier ',' not found, address length > 31
7E Requested address not found (reading)
7F Format conflict, target field was too short
80 Conditionally requested data were not written
81 Data could not be written because of insufficient space
82 Unconditionally requested data not found (writing)
83 Fixed-code data are too long, format change not possible
84 F24 occurred after F20
85 Address length too large
86 Format parameter error
87 Format ID error
88 Sign error in formats without sign
89 AFA = 0 found (number of following address format blocks)
8A No address or data end identifier found after F20
8B Protocol D is not installed
8C Non-decimal digit found in decimal field
8D Incorrect access to data carrier
8E Data on data carrier incomplete
8F Address error, access to address >= 122 for TDTI256
90 Unknown function identifier for protocol 0
91 Data length error, TZVI response message frame is too short
92 No data carrier available
93 High-frequency error TZVI
94 Syntax error in CISCP command message frame
95 Other T no. on data carrier (CISCP protocol)
96 Write-protected field addressed (CISCP protocol)
B4 TDS station sends too many STX without DLE as response
B5 Message frame collision between control and TDSE
Error cause
00 Connection to required NCU could not be established
05 Reading of NCK configuration failed
0A An invalid channel number was specified in the job
3C An invalid magazine number was specified in the job
3E An invalid magazine place number was specified in the job
3F An invalid cutting edge OEM monitoring parameter number was
specified in the job
41 MMC semaphore for Create/Search tool already assigned
46 The tool indicated with identifier and duplo number could not be
found in the NCK
47 The tool indicated with T number could not be found in the NCK
48 No tools found in the magazine specified
49 No tool has been loaded to the magazine place specified
4A Number of tools found could not be read in the NCK
4B Number of tools found could not be read in the NCK
50 The tool indicated with identifier and duplo number has not been
created in the NCK
55 The tool indicated has already been loaded to the magazine
5A The tool cutting edge with the number specified has not been
created in the NCK
5B The tool cutting edge with the number specified has not been
deleted in the NCK
5C The cutting edge indicated is not available in the NCK
5D Invalid tool cutting edge number
5E The cutting edge indicated exists already in the NCK
5F Tool status could not be read in the NCK
64 MMC semaphore for empty location search already assigned
69 An empty magazine place could not be found in the NCK during
loading
6E Negative acknowledgement for checking of the specified magazine
loading place
73 MMC semaphore for Load/Unload tool already assigned
78 Magazine blocked or not released for loading
7D Tool loading was terminated with an error
82 The magazine number of the tool could not be read in the NCK
87 The tool indicated has not been loaded in the NCK
8C The tool indicated has been loaded in another magazine
8E The tool indicated has been loaded in another magazine place
91 Magazine status could not be read in the NCK
96 Magazine not in loading position or not released for unloading
9B Tool unloading was terminated with an error
A0 The tool could not be deleted in the NCK
Error cause
A5 The tool indicated has been loaded in the NCK! The tool could not
be deleted in the NCK
D2 The tool indicated has been loaded in the NCK! The tool has not
been deleted in the DB
Error cause
00 The tool exists already in the DB but its data cannot be updated
05 The tool exists already in the DB but its OEM data cannot be
updated
0A The cutting edge exists already in the DB but its data cannot be
updated
0F The cutting edge exists already in the DB but its OEM data cannot
be updated
11 The cutting edge exists already in the DB but its OEM monitoring
data cannot be updated
12 The tool has not been entered in the DB! Tool with identical name
and other subtype exists already in the DB
14 No data could be found in the DB for the tool selected
19 No OEM data could be found for the tool read from the DB
1E No cutting edge data could be found in DB for the tool read from the
DB
23 No OEM cutting edge data could be found for the tool read from the
DB
28 No OEM monitoring data could be found for the tool read from the
DB
2D The cutting edge OEM monitoring data specified for the tool is not
available in the NCK
32 The cutting edge OEM monitoring data specified for the tool could
not be read or written in the NCK
Error cause
00 Error during conversion, reading or writing of tool data from the
COM-TDS server
05 No valid tool data available on the COM-TDS server
Error cause
00 Status of the SINCOM server could not be read
05 Data transfer from SINCOM server still active! Job aborted
0A T_DATA_H command could not be executed by the SINCOM
server
0F Status of data transfer could not be set in the NCDDE server
14 Data transfer could not be terminated or was terminated with an
error
19 Tool data file name could not be read or determined on the
SINCOM server
1E Tool data file could not be opened
23 Tool data file is empty
2D No tool data available in the host computer file
32 R_DATA_H command could not be executed by the SINCOM
server
Error cause
00 No file name available for import or export job
05 Tool data file could not be opened
0A Tool data file is empty
0F Tool data file could not be created
14 The tool data file specified exists already and is not empty
19 Writing to tool data file was not possible
Example:
PLC word 140 is composed of the two PLC bytes
140 and 141 and is to be assigned the value 120.
Byte 140: 0
Byte 141: 120
String xx characters Strings occupy xx+2 bytes in the PLC, since the first
two bytes contain the maximum length and the
current length of the string. Therefore, the actual
rd
string commences only with the 3 byte. The
individual characters are stored as ASCII code in
the corresponding bytes.
Example:
"Hello" is to be stored in a string which commences
with PLC byte 144 and has a maximum length of 32
characters. This results in the following byte
assignment:
A.3 Abbreviations
ASCII American Standard Code for Information Interchange
CD Compact Disc
COM Communications
®
COM Component Object Model (Programming Model Microsoft )
DB Data Block
INT Integer
MB Mega Byte
NC Numerical Control
PG Programming Device
TM Tool Management
VB Visual Basic
VC Visual C++
A.4 References
General Documentation
/ST7/ SIMATIC
Products for Totally Integrated Automation und Micro Automation
Catalog ST 70
Order No.: E86060-K4670-A111-A8-7600
/Z/ MOTION-CONNECT
Cable, Connectors & System Components for SIMATIC, SINUMERIK,
Masterdrives und SIMOTION
Catalog NC Z
Order No.: E86060-K4490-A001-B1-7600
Electronic Documentation
User Documentation
Manufacturer/Service Documentation
a) Lists
/LIS/ SINUMERIK 840D/840Di/810D (11.02 Edition)
SIMODRIVE 611D
Lists
Order No.: 6FC5297-6AB70-0BP3
b) Hardware
/ASAL/ SIMODRIVE (06.03 Edition)
Planning Guide General Information for Asynchronous Motors
Order No.: 6SN1197-0AC62-0BP0
Please enter the ID No.: 15257461 in the 'Search' field (top right) and click
on 'go'.
c) Software
/FB1/ SINUMERIK 840D/840Di/810D/FM-NC (11.02 Edition)
Description of Functions Basic Machine (Part 1)
(the various sections are listed below)
Order No.: 6FC5297-6AC20-0BP2
A2 Various Interface Signals
A3 Axis Monitoring, Protection Zones
B1 Continous Path Mode, Exact Stop and Look Ahead
B2 Acceleration
D1 Diagnostic Tools
D2 Interactive Programming
d) Installation
and Start-up
/BS/ SIMODRIVE 611 analog (10.00 Edition)
Description Start-Up Software for Main Spindle and
Ansynchronous Motor Modules Version 3.20
Order No.: 6SN1197-0AA30-0BP1
I Index
M T
wkonvert.txt
Creating the file ..................................3-36
Description file....................................3-36
Examples............................................3-42
n
Siemens AG Corrections
For Publication/Manual:
A&D MC BMS
P.O. Box 3180 Sinumerik 840D/840Di/810D
Phone: __________ /
Fax: ________ /
SINUMERIK
SIROTEC
SINUMERIK SINUMERIK SIMODRIVE SINUMERIK SINUMERIK SINUMERIK SINUMERIK
840D/810D 840D/840Di/ Accessories 840D/810D/ 840D/840Di/ 840D/840Di/ 840D/840Di/
810D/ FM-NC 810D 810D 810D
Program. Guide Operator’s Guide System Overview Configuring Operator Description of Description of
– Short Guide – ManualTurn (HW) *) Components Functions Functions
– Fundamentals *) – Short Guide ManualTurn – 810D (HW) *) – ManualTurn Synchronized
– Advanced *) – ShopMill – 840D – ShopMill Actions
– Cycles – Short Guide ShopMill – ShopTurn
– Measuring Cycles – ShopTurn
– ISO Turning/Milling – Short Guide ShopTurn
Manufacturer/Service Documentation
SINUMERIK
SIMODRIVE SINUMERIK SINUMERIK SINUMERIK SINUMERIK SINUMERIK
611D 840D/840Di/ 840D/840Di/ 840D/810D 840D/810D 840D/810D
840D/810D 810D 810D
Description of Description of Description of Configuring Kit Description of Motion Control Info. System
Functions Functions Functions HMI Embedded Functions – Computer Link
Drive Functions *) – Basic Machine *) Tool Manage- Operator Interface – Tool Data Information System
– Extended Functions ment OP 030 – NC Data Management
– Special Functions – NC Data Transfer
– Tool Data Communication
Manufacturer/Service Documentation
SINUMERIK
SINUMERIK SINUMERIK SINUMERIK SINUMERIK SINUMERIK SIMODRIVE
SIMODRIVE SINUMERIK SIMODRIVE SIMODRIVE SIMODRIVE SIMODRIVE SIROTEC
840D 840D/840Di 840D 840D
810D 611D 611D
611D