Im5 76
Im5 76
SINUMERIK 840D/840Di/810D
2 Start-Up................................................................................................................................... IM5/2-11
2.1 Setting the fixed IP address of the PCU in the TCU network ............................................... IM5/2-12
2.2 Installing the "PCU Base Software Thin Client" ................................................................... IM5/2-14
A Appendix ...............................................................................................................................IM5/A-55
1 Introduction
1
1.1 Description .................................................................................. IM5/1-4
1.1 Description
The Thin Client Unit (TCU) for distributed installation allows the spatial separation
of SINUMERIK operator panel fronts (OP/TP) and SINUMERIK PCUs and the
connection of up to four operator panel fronts to a PCU with one TCU each. The
user interface of one PCU is reproduced on several OPs with one TCU each. So all
TCUs show the same display. Operator actions can only be performed on one TCU
at a time. This TCU then has the operator focus.
The PCU can also have its own OP connected to it.
This permits a configuration where the PCU is located in the switching cabinet and
the TCU used for operation is spatially separated.
An example of a distributed configuration with 1 PCU and 4 TCUs is shown in the
following illustration.
MCP
Ethernet
Up to 4
OP/TP
+ TCU
MCP SINUMERIK
840D
1.2 Requirements
To operate a TCU together with a PCU the following requirements must be met:
• PCU 50/70 ≥ 1.2 GHz with Windows XP
• BIOS version ≥ 02.03.09
• PCU base software ≥ 07.04.00.00
• If HMI Advanced is used: HMI Advanced software ≥ 06.04.19
• A second Ethernet card if the PCU is also to be used for connecting the TCU to
a company network.
• If the PCU is to be operated without a operator panel front, monitors and an
additional keyboard will also be required for:
Initial installation of the software required for TCU operation
Diagnostics when the PCU does not boot
Insertion of a spare hard disk (alternatively, an external hard disk can also be
used.)
• Assembly and cabling of the entire system according to one of the permissible
configurations described in Chapter "Configuration options"
1.3 Constraints
When operating a TCU together with a PCU the following constraints apply:
• No more than four TCUs may be activated at any one time on a PCU.
• All OPs – including any OP that is connected directly to the PCU as well as the
OPs connected to the TCUs – must have the same screen resolution.
• If PCU applications requiring the properties of the hardware support to
implement graphic output (e.g., OpenGL or DirectX) are to be visualized on the
TCU, the hardware support for graphic output must be disabled on the PCU.
• Depth-of-color selection is limited to 16-bit setting.
• Distributed memory media connected to the TCU via USB cannot be used. Nor
can a CF card be used on the TCU.
• If a PC keyboard is connected to the TCU, it cannot be guaranteed that all
special keys, e.g., multimedia keys, will be transmitted to the software on the
PCU.
• You must use PLC block FB9 for automatic switchover of a machine control
panel when changing the focus. For this, FB9 must be parameterized and
called up by the PLC user program (see /FB1/ Description of Functions Basic
Machine, PLC Basic Program (P3)). Automatic switchover of the machine
control panels used when changing the focus can only be performed in
conjunction with HMI Advanced.
• Machine control panels connected via a PROFIBUS network are not supported
for switchover.
• Switchover of TCU via PLC: The function, which supports switchover disable
on a TCU, is described in chapter "Switchover disable".
The free software listed below can be used with the "Thin Client PCU Base
Software" product:
Name License File name
Ultra@VNC GPL See gpl.txt
Winpcap BSD style See bsd-style.txt
DHCP-Svr Win GPL See gpl.txt
Tftp (Win) BSD See bsd.txt
Tftp (Linux) BSD See bsd.txt
Tsort (Linux) BSD See bsd.txt
libz Zlib license See zlib.txt
FTP (Win) GPL See gpl.txt
Linux-Kernel GPL See gpl.txt
Bootloader GPL See gpl.txt
libc LGPL See lgpl.txt
Busybox GPL See gpl.txt
The licensing texts for the free software used in the “PCU Base Software Thin
Client” product can be found in Appendix A.
These programs have been developed by third parties. If you wish to use free
software as well as the program sequence provided by Siemens, please contact
the originators or other copyright holders for this software in order to apply for
usage rights (in observance of the appropriate licensing conditions).
You can obtain the source text for the free software, along with the associated
licensing texts and copyright endorsements, from your SIEMENS sales
representative for up to three years after purchasing this product.
Please read the licensing provisions for this software before installing or using it.
If you received this software on a CD marked “Trial Version” or with software for
which you have a license, the software may only be used for test and validation
purposes, in accordance with the enclosed Trial License conditions. In this respect,
programs, software, libraries, etc., must be installed on your computer. We strongly
recommend, therefore, that these programs are installed on a stand-alone
computer or on a computer, which is not used in the production process or for
storing important data, due to the risk of existing files being changed or overwritten.
We can accept no responsibility for damage and/or loss of data resulting from the
installation of this software, or from non-observance of this warning.
All other use of this software is only permitted if you have purchased a valid license
from Siemens. If you do not possess a valid license, which can be proved by
presentation of the relevant Certificate of License/Software Product Certificate,
please terminate this installation and contact Siemens immediately, in order to
avoid any claims for compensation.
The free software contained in this product, which is not part of the program
sequence provided by Siemens, is used at your own risk, i.e., no warranty claims
may be made against Siemens.
The licensing conditions listed contain notes regarding the warranties offered by
the originators or copyright holders of the free software. Siemens will also accept
no warranty claims if a product defect is or could be the result of modifications
made to the programs or their configurations by you.
SIEMENS does not offer technical support for this product if you are using it in
conjunction with modified software.
Notice
Use directory E:\TCU\SERVICES "read-only".
Only change the configuration files below path: F:\TCU\SERVICES.
F:\TCU\SERVICES\TCU_HWS\ETC\
File: TCU_HWS.CONF
Entry: interface 192.168.214.1 #IP address of PCU in
TCU network
Entry: pcu_name "main operator panel" #PCU identifier, as
displayed for this PCU
in the selection/
switchover dialog box
on the TCU. Maximum
length: 40 characters
default no name (="")
F:\TCU\SERVICES\UDHCPD\ETC\
File: UDHCPD.CONF
Entry: # Start and end of the IP address
# range used by the DHCP server for the TCU network
start 192.168.214.2
end 192.168.214.250
F:\TCU\SERVICES\BETAFTPD\ETC\
File: BETAFTPD.CONF
Entry: interface 192.168.214.1 #IP address of PCU in
TCU network
F:\TCU\SERVICES\NETKIT-TFTPD\ETC\
File: NETKIT-TFTPD.CONF
Entry: interface 192.168.214.1 #IP address of PCU in
TCU network
F:\TCU\SERVICES\
File: TCU.INI (response during focus-change time intervals)
Entry: In file TCU.INI, the response to focus change can be set in the TCUs.
The following setting options are available:
[VNCServer]
# VETO MODE
# VetoMode enabled:
# VNC server notifies the HMI regie before another
# panel gets the focus.
# VetoMode disabled:
# Focus timeout mode enabled (implicitly; see FOCUS TIMEOUT)
# (0=DISABLE, 1=ENABLE)
VetoMode=1
# ALARMBOXTIMEOUT
# specifies the time period (in sec) the message box is shown
# (i.e., is operable) in the case of VetoMode=1; no meaning
# else
AlarmBoxTimeOut=5
# FOCUS TIMEOUT
# Guaranteed time period (in sec) a panel can hold the
# focus at least before another panel can get the focus.
# The time period starts from the moment the panel has
# gained the focus.
FocusTimeout=10
VetoMode = 1
When focus is requested by another OP the operator with the focus can prevent
the focus from changing by acknowledging an alarm (120011), i.e., the operator
can keep the operator focus with this veto right. The alarm can be acknowledged
during a time interval defined in "AlarmBoxTimeout". If no action is performed
during this time, the focus changes to the requesting TCU.
VetoMode = 0
The time interval set in "FocusTimeout" has a disabling effect and will only allow a
focus change to take place again when it has expired.
F:\TCU\SERVICES\FTP_TCUS\
The content of directory FTP_TCUS is generated automatically. You must insert
the files marked bold if you change the configuration.
TCUx\
COMMON\
TCU\
MCPADDR\
6 (empty file with the address of the MCP for this
OP (of this TCU) as the name;
Default setting is "6"; i.e., a file called
"6", which corresponds to the standard machine
control panel address for MPI)
In directory FTP_TCUS, a file is automatically created with the MAC address of the
TCU as its file name to identify each TCU. The sole content of the file is the
assigned TCU name ("TCUx" in the above example).
If it is possible to switch the TCU to several different PCUs in a TCU network, enter
those PCUs in file CONFIGU in subdirectory COMMON\TCU.
2
2 Start-Up
2.1 Setting the fixed IP address of the PCU in the TCU network ... IM5/2-12
This chapter describes the procedure for installing the TCU. Depending on the
configuration of your system (number of TCUs, PCUs, and NCUs) there may be
some special aspects of installation. So before you perform installation you should
not only read this chapter but also refer to the relevant section in chapter
"Configuration options".
2.1 Setting the fixed IP address of the PCU in the TCU network
You must define a fixed network address for each PCU in the TCU network.
Note
Before you start installation consider carefully what you will require each IP
address for and observe the following:
• Recommended address range for the TCU network is 192.168.214.1 – 254
with subnet mask 255.255.255.0.
• The IP addresses of the PCUs must be different whereas the subnet masks
must be identical.
Example
3 PCUs are connected in the TCU network.
Procedure
1. Select the following on the PCU in Windows service mode: "Start" "Settings"
"Network Connections".
The "Network Connections" window opens.
2. Double-click on the interface you want to parameterize – here the interface to
be used for connecting the TCU or TCU network (Local Area Connection).
The "Local Area Connection Properties" window opens.
3. On the "General" tab card, select "Internet Protocol (TCP/IP)" and click the
"Properties" button.
IP address 192.168.214.1
If you have set fixed IP address 192.168.214.1 with subnet mask 255.255.255.0 for
the PCU, installation will be performed automatically. Addresses 192.168.214.2 –
250 are reserved for the TCUs in the TCU network. Addresses 192.168.214.251 –
254 remain free.
Other IP address
If the PCU has two Ethernet cards and you have not set the recommended fixed IP
address 192.168.214.1 with subnet mask 255.255.255.0 for either of the cards, the
"Choose Network Card" window opens.
2. Select the Ethernet card for which you have set the fixed IP address for the
TCU network.
The "IP Address" window then appears.
The default values of the parameters depend on the previously set IP address of
the PCU and have the following meaning:
• Interface
IP address of the PCU in the TCU network
• IP lease block start
Beginning of the IP address range for the TCUs in the TCU network
Notice
This address must be different from the IP address of the PCU and of all PCUs in
the TCU network (parameter "Interface").
Note
If you do not occupy the entire possible address range, you will be able to
connect a PG with a fixed IP address from this unused address range to the TCU
network when using a switch for the TCU network.
• Subnet mask
Mask for the TCU sub-network
Note
The last 3 parameters must have the same settings for all PCUs.
2. Mark DHCP server "hmisvr_PCU_udhcp", press the right mouse button, and
select "Properties".
The "hmisvr_PCU_udhcp Properties (Local Computer)" window opens.
3. On tab card "General", select "Disabled" from list box "Startup type" and
confirm with "OK".
The DHCP server is deactivated.
4. In the same way, deactivate the two services "hmisvr_PCU_betaftpd" and
"hmisvr_PCU_netkit-tftpd".
These two services are no longer required when you deactivate the DHCP
server.
FTP_TCUS
TCUx
COMMON
TCU
MCPADDR
6 (empty file with the address of the MCP for
this OP (this TCU) as the name;
Standard default setting is "6"; i.e., a file
called "6", which corresponds to the default
machine control panel address for
MPI).
CONFIG
SYSTEM
MACADDR ("TCUx")
If a PCU or TCU has no MCP you must set one of the two following options:
• MCP address = 0 or no entry
The machine control panel does not switch over after a focus change, the
same machine control panel remains active.
• MCP address = 255
If the operator focus is passed to this PCU/TCU the previous machine control
panel is deactivated. At this moment there is no active machine control panel.
1. Enter the PCUs that are connected to the TCU network on the PCU with the
active DHCP server in file
F:\TCU\SERVICES\FTP_TCUS\TCUx\COMMON\TCU\CONFIG.
Observe the following syntax:
VNCServer=IP_Address:Session_Number:Password
Example The TCU network has 2 PCUs with IP addresses 192.168.214.1 and
192.168.214.251.
VNCServer=192.168.214.1:0:password
VNCServer=192.168.214.251:0:password
Note
The TCU connects up with the first PCU listed in the CONFIG file when it boots.
2. On every PCU in the TCU network, enter a name for the PCU in file
F:\TCU\SERVICES\TCU_HWS\ETC\TCU_HWS.CONF.
1. If necessary, limit the address range for the TCUs so that an IP address
remains free for the PG (see chapter "Changes after installation and start-up",
section "Changing the address range of the TCUs").
2. Set a fixed IP address for the PG with the same subnet mask as for the PCU
on the PG under Windows (Start Settings Control Panel Network
Connections).
For more detailed information see chapter "Setting the fixed IP address of the
PCU in the TCU network".
File: F:\TCU\SERVICES\TCU_HWS\ETC\TCU_HWS.CONF
Entry: interface 167.142.117.8
File: F:\TCU\SERVICES\NETKIT-TFTPD\ETC\NETKIT-TFTPD.CONF
Entry: interface 167.142.117.8
File: F:\TCU\SERVICES\BETAFTPD\ETC\BETAFTPD.CONF
Entry: interface 167.142.117.8
File: F:\TCU\SERVICES\UDHCPD\ETC\UDHCPD.CONF
Entry: interface 167.142.117.8
Entry: start 167.142.117.9
Entry: end 167,142,117,250
Entry: siaddr 167.142.117.8
Entry: option subnet 255.255.255.0
File: F:\TCU\SERVICES\UDHCPD\ETC\UDHCPD.CONF
Entry: start 167.142.117.9
Entry: end 167,142,117,250
The rejected user authorization request leads to a message being output in the
user response line of the HMI, in the form of a checkback signal for the requester.
The message disappears after five seconds.
The control bits and control information for this function are stored in the m:n data
interface of the PLC. In terms of m:n, this function can be operated separately for
the currently overridden HMIs in both m:n online interfaces (DB19.DBW120 ff for
HMI1 and DB19.DBW130 ff for HMI2). If a system is not running an m:n, only the
first m:n online interface is used for this function.
The PLC m:n online interface is expanded so that byte DB19.DBB118 is still added
to the first interface and byte DB19.DBB119 to the second. These bytes acquire
the index of the active TCU (of the active OP) for the appropriate HMI. The byte is
called TCU_INDEX. The appropriate HMI uses the TCU index configured for the
active TCU to describe the TCU_INDEX byte (see section “Configuring”).
The HMI assigns the configured index of the TCU or PCU whose OP currently
possesses user authorization in the shadow grouping to the TCU_INDEX field. If
no OP is active, a value of 0 is entered in TCU_INDEX.
If no TCU index is configured for the active TCU (active OP), the value 255 =
undefined is presented as the TCU index. This means that the values of 0 and 255
may not be configured as the TCU index.
Configuring
The TCU index and machine control panel address are configured on the PCU. A
TCUINDEX directory, containing an empty file named after the index, is created
relative to the TCU directory for each TCU (TCUx) or, in the case of a directly
connected OP, for the PCU itself:
FTP_TCUS
TCUx
COMMON
TCU
MCPADDR
6 (Empty file named after the address of the
MCP for this OP (this TCU); default setting is
“6”, so this file is called “6”, which
corresponds to the default machine control
panel address on the MPI.)
TCUINDEX\
8 (Empty file named after the index to be
assigned to this OP (this TCU); there is no
default setting, the directory and file must be
created manually for the "switchover
disable" function.)
The file structure for managing the TCU index is not created automatically, but
must be created for the “switchover disable” function.
Note
The switchover disable only relates to changing the user authorization on the
OPs in a shadowing grouping on a PCU. Active switching from one OP to
another PCU is not prevented.
Special features
• Even if switchover disable is set, the TCU_INDEX field value may change in
the PLC. This is the case if:
− The OP in possession of the user authorization is actively switched to
another PCU. Depending on whether another TCU takes on the user
authorization or no TCU is currently active, either the index of the TCU
(as when user authorizations are switched over) or the PCU itself (if its
directly connected OP becomes active) is entered.
This may also be the value 255, if no TCU index is available for the OP.
0 is entered if an OP is no longer available in the shadow grouping.
− An m:n switchover is in progress. The HMI of the incoming PCU
deactivates the HMI, which is active on it. An OP from the shadow
grouping of the new (incoming) PCU must receive the user authorization.
The TCU index of this OP is entered in the TCU_INDEX field.
− A PCU is disconnected from a NCK/PLC in the context of m:n. No HMI
and, therefore, no OP with operator focus is then available on the exited
NCK/PLC. This is signaled independently of a switchover disable by
entering the value 0 into the TCU_INDEX field.
• If a TCU is actively switched over to another PCU, it can be deactivated there,
i.e., it does not obtain the user authorization, if a switchover disable is set for
the destination PCU.
• With an m:n PCU switchover, i.e., the PCU is switched to another NCK and,
therefore, to another PLC, the PCU takes on the switchover disable settings of
that PLC.
• The m:n interlock options on the PLC side have priority over the TCU
switchover disable, so that a set TCU switchover disable cannot prevent an
m:n switchover. If necessary, the m:n interference options should be
synchronized here with those for the TCU in the PLC. It may, for example, be
practical to set or remove the m:n displacement disable simultaneously with
the TCU switchover disable.
Notes
3
3 Configuration Options
The various configurations for operating a TCU on a PCU are described in this
chapter. Included in this description are m:n configurations of control unit
management of SINUMERIK powerline, which can provide the basis for operation
with the TCU. The m:n functionality is configured on the PCUs for each relevant
HMI in the usual way. No changes result from operation with the TCU.
t:(m:n)
Colors:
The brackets express how the PCUs are operated on the NCUs. The expression
(m:1) means that there are m PCUs each of which is assigned its own NCU.
Consequently (m:n) means that m PCUs can be connected via n NCUs according
to the rules of control unit management.
Hardware requirements
• Crossover Ethernet cable for direct connection of the TCU to the PCU
Options/restrictions
• Connection of the PCU to a company network not possible
• Connection of a PG via Ethernet to the PCU not possible
Hardware requirements
• Crossover Ethernet cable for direct connection of the TCU to the PCU
Options/restrictions
• Connection of the PCU to a company network not possible
• Connection of a PG via Ethernet to the PCU not possible
• Only one NCU (to which the PCU is connected) can be operated and visualized
at any one time
Startup
• Operation of the PCU at n NCUs is conventionally configured in file
NETNAMES.INI on the PCU.
Hardware requirements
• Normal, straight Ethernet cable for connecting the TCU and PCUs to the TCU
network
• Switch via which the 1 TCU and m PCUs are connected
Options/restrictions
• Connection of the PCU to a company network not possible
• Connection of a PG via Ethernet to the PCU in the TCU network is possible
• Only one NCU (to which the selected PCU is connected) can be operated and
visualized at any one time
• TCU can be switched to the various PCUs
• Possible configurations: See "Setting the address of the MCP"
Hardware requirements
• Normal, straight Ethernet cable for connecting the TCUs and PCU to the TCU
network
• Switch via which the t TCU and 1 PCU are connected
Options/restrictions
• Connection of the PCU to a company network not possible
• Connection of a PG via Ethernet to the PCU in the TCU network is possible
• All TCUs show the same display
FTP_TCUS
PCU
COMMON
TCU
MCPADDR
6
SYSTEM
TCU1
COMMON
TCU
MCPADDR
7
SYSTEM
TCU2
COMMON
TCU
MCPADDR
8
SYSTEM
TCU3
COMMON
TCU
MCPADDR
9
SYSTEM
TCU4
COMMON
TCU
MCPADDR
10
SYSTEM
MACADDR ("TCU1")
MACADDR ("TCU2")
MACADDR ("TCU3")
MACADDR ("TCU4")
Hardware requirements
• Normal, straight Ethernet cable for connecting the TCUs and PCU to the TCU
network
• Switch via which the t TCU and 1 PCU are connected
Options/restrictions
• Connection of the PCU to a company network not possible
• Connection of a PG via Ethernet to the PCU in the TCU network is possible
• All TCUs show the same display
• Every NCU can be operated and visualized with m:n operation on the PCU from
every TCU via PCU
Startup
• Settings for the TCU network: see Section "t:(1:1) without company network"
• Operation of the PCU at n NCUs is conventionally configured in file
NETNAMES.INI on the PCU.
Configuration option 2:
Connections of the TCU network and connections of the company network are
routed through a joint switch.
Condition: The address range used for the TCU network does not collide with the
company network. (Autonomous sub-network for TCU network is set up
automatically.)
Hardware requirements
• Additional Ethernet card for PCU
• Crossover Ethernet cable for direct connection of the TCU to the PCU
• Normal, straight Ethernet cable for connecting the PCU to the company network
• For configuration 2:
Crossed Ethernet cable (crossover) between switch and company network
Options/restrictions
• Connection of the PCU to a company network possible
• Connection of a PG via Ethernet to the PCU in the TCU network (configuration
option 2) or company network (configuration option 1) is possible
• It is possible to extend configuration option 1 by integrating the PCUs of several
1:(1:1) systems into the company network. Each of the 1:(1:1) systems must be
configured separately.
Startup
• If you want to integrate several 1:(1:1) systems (or their PCUs) into the
company network you must configure each system separately. Each of the
systems can be configured identically.
Configuration option 2:
Connections of the TCU network and connections of the company network are
routed through a joint switch.
Condition: The address range used for the TCU network does not collide with the
company network. (Autonomous sub-network for TCU network is set up
automatically.)
Hardware requirements
• Additional Ethernet card for PCU
• Crossover Ethernet cable for direct connection of the TCU to the PCU
• Normal, straight Ethernet cable for connecting the PCU to the company network
• For configuration option 2:
Crossed Ethernet cable (crossover) between switch and company network
Options/restrictions
• Connection of the PCU to a company network possible
• Connection of a PG via Ethernet to the PCU in the TCU network or company
network is possible
• Only one NCU (to which the PCU is connected) can be operated and visualized
at any one time
• It is possible to extend configuration option 1 by integrating the PCUs of several
1:(1:n) systems into the company network. Each of the 1:(1:n) systems must be
configured separately.
Startup
• Operation of the PCU at n NCUs is conventionally configured in file
NETNAMES.INI on the PCU.
• If you want to integrate several 1:(1:n) systems (or their PCUs) into the
company network you must configure each system separately. Each of the
systems can be configured identically.
Configuration option 2:
Connections of the TCU network and connections of the company network are
routed through a joint switch.
Condition: The address range used for the TCU network does not collide with the
company network. (Autonomous sub-network for TCU network is set up
automatically.)
Hardware requirements
• One additional Ethernet card per PCU
• One switch per TCU network
• For each PCU, two normal, straight Ethernet cables for connecting the PCU to
the TCU network and company network
• For each TCU, one normal, straight Ethernet cable for connecting the TCU to
the TCU network
• For configuration option 2:
Crossed Ethernet cable (crossover) between switch and company network
Options/restrictions
• Connection of the PCU to a company network possible
• Connection of a PG via Ethernet to the PCU in the TCU network or company
network is possible
• Additional 1:(m:1) configurations can be connected to the company network
simply by means of a separate switch for each TCU network (physical
separation of the TCU networks from each other and physical separation of the
TCU networks from the company network).
• Only one NCU (to which the selected PCU is connected) can be operated and
visualized at any one time
• TCU can be switched to the various PCUs
Startup
• Settings for the TCU network: see Section "1:(m:1) without company network"
• If you want to integrate several 1:(m:1) systems (or their PCUs) into the
company network you must configure each system separately. Each of the
systems can be configured identically.
Configuration option 2:
Connections of the TCU network and connections of the company network are
routed through a joint switch.
Condition: The address range used for the TCU network does not collide with the
company network. (Autonomous sub-network for TCU network is set up
automatically.)
Hardware requirements
• One additional Ethernet card per PCU
• One switch per TCU network
• For each PCU, two normal, straight Ethernet cables for connecting the PCU to
the TCU network and company network
• For each TCU, one normal, straight Ethernet cable for connecting the TCU to
the TCU network
• For configuration option 2:
Crossed Ethernet cable (crossover) between switch and company network
Options/restrictions
• Connection of the PCU to a company network possible
• Connection of a PG via Ethernet to the PCU in the TCU network or company
network is possible
• Additional t:(1:1) configurations can be connected to the company network
simply by means of a separate switch for each TCU network (physical
separation of the TCU networks from each other and physical separation of the
TCU networks from the company network).
Startup
• Settings for the TCU network: see Section "t:(1:1) without company network"
• If you want to integrate several t:(1:1) systems (or their PCUs) into the company
network you must configure each system separately. Each of the systems can
be configured identically.
Configuration option 2:
Connections of the TCU network and connections of the company network are
routed through a joint switch.
Condition: The address range used for the TCU network does not collide with the
company network. (Autonomous sub-network for TCU network is set up
automatically.)
Hardware requirements
• One additional Ethernet card per PCU
• One switch per TCU network
• For each PCU, two normal, straight Ethernet cables for connecting the PCU to
the TCU network and company network
• For each TCU, one normal, straight Ethernet cable for connecting the TCU to
the TCU network
• For configuration option 2:
Crossed Ethernet cable (crossover) between switch and company network
Options/restrictions
• All TCUs show the same display
• Connection of the PCU to a company network possible
• Connection of a PG via Ethernet to the PCU in the TCU network or company
network is possible
• Every NCU can be operated and visualized with m:n operation on the PCU from
every TCU via PCU
• Additional t:(1:n) configurations can be connected to the company network
simply by means of a separate switch for each TCU network (physical
separation of the TCU networks from each other and physical separation of the
TCU networks from the company network).
Startup
• Settings for the TCU network: see Section "t:(1:n) without company network"
• Operation of the PCU at n NCUs is conventionally configured in file
NETNAMES.INI on the PCU.
• If you want to integrate several t:(1:n) systems (or their PCUs) into the company
network you must configure each system separately. Each of the systems can
be configured identically.
4 Operation
4
4.1 Operation while booting ............................................................ IM5/4-50
4.1.1 Boot messages...................................................................... IM5/4-50
4.1.2 Diagnostics window ............................................................... IM5/4-50
4.1.3 Calling up the SINUMERIK desktop...................................... IM5/4-53
4.1.4 Calling up the Service menu.................................................. IM5/4-53
Note
The functions "F1" to "F8" referred to in this chapter are selected with the
horizontal softkeys on the OP. If you want to select "F7", for example, you must
press horizontal softkey 7.
IP address
You can see the current boot phase in the third line. Below that you are told
whether you can call up information via "F1" if a fault occurs.
Function Effect
F1 Display detailed Information
F8 Reboot the TCU
Function Effect
F1 Display detailed Information
Notice
These operator input sequence steps must only be carried out by qualified
personnel.
You can operate the HMI-Advanced software on the OP of the TCU in exactly the
same way as you do on the OP connected directly to the PCU. All keys have the
same functions as on the directly connected OP.
There are merely the following differences:
Requesting the operator focus
If the key is pressed on a TCU without the operator focus the action merely
requests the operator focus. That means this key is not evaluated by HMI
Advanced.
The settings for the right to veto are made in file F:\TCU\SERVICES\TCU.INI and
only take effect if HMI Advanced is installed on the PCU.
Selecting a PCU
If connection options have been set for a TCU in the CONFIG file to several
different PCUs, key combination "Recall" + "Menu select" (corresponds to the F9 +
F10 key combination on an external keyboard) opens the "VNC Starter" window on
the TCU. In that window, the operator can select the PCU to which a connection is
to be established with the horizontal softkeys.
Key combination "Recall" + "Menu select" is not evaluated by HMI Advanced.
Note
The “Touchware” program, which is available with Windows XP, is deactivated on
the TCU.
A
A Appendix
Preamble
The licenses for most software are designed to take away your freedom to share
and change it. By contrast, the GNU General Public License is intended to
guarantee your freedom to share and change free software--to make sure the
software is free for all its users. This General Public License applies to most of the
Free Software Foundation's software and to any other program whose authors
commit to using it. (Some other Free Software Foundation software is covered by
the GNU Library General Public License instead.) You can apply it to your
programs, too.
When we speak of free software, we are referring to freedom, not price. Our
General Public Licenses are designed to make sure that you have the freedom to
distribute copies of free software (and charge for this service if you wish), that you
receive source code or can get it if you want it, that you can change the software or
use pieces of it in new free programs; and that you know you can do these things.
To protect your rights, we need to make restrictions that forbid anyone to deny you
these rights or to ask you to surrender the rights. These restrictions translate to
certain responsibilities for you if you distribute copies of the software, or if you
modify it.
For example, if you distribute copies of such a program, whether gratis or for a fee,
you must give the recipients all the rights that you have. You must make sure that
they, too, receive or can get the source code. And you must show them these
terms so they know their rights.
We protect your rights with two steps: (1) copyright the software, and (2) offer you
this license which gives you legal permission to copy, distribute and/or modify the
software.
Also, for each author's protection and ours, we want to make certain that everyone
understands that there is no warranty for this free software.
If the software is modified by someone else and passed on, we want its recipients
to know that what they have is not the original, so that any problems introduced by
others will not reflect on the original authors' reputations.
Finally, any free program is threatened constantly by software patents. We wish to
avoid the danger that redistributors of a free program will individually obtain patent
licenses, in effect making the program proprietary. To prevent this, we have made
it clear that any patent must be licensed for everyone's free use or not licensed at
all.
The precise terms and conditions for copying, distribution and modification follow.
0. This License applies to any program or other work which contains a notice
placed by the copyright holder saying it may be distributed under the terms of this
General Public License. The "Program", below, refers to any such program or
work, and a "work based on the Program" means either the Program or any
derivative work under copyright law: that is to say, a work containing the Program
or a portion of it, either verbatim or with modifications and/or translated into another
language. (Hereinafter, translation is included without limitation in the term
"modification".) Each licensee is addressed as "you". Activities other than copying,
distribution and modification are not covered by this License; they are outside its
scope. The act of running the Program is not restricted, and the output from the
Program is covered only if its contents constitute a work based on the Program
(independent of having been made by running the Program). Whether that is true
depends on what the Program does.
1. You may copy and distribute verbatim copies of the Program's source code as
you receive it, in any medium, provided that you conspicuously and appropriately
publish on each copy an appropriate copyright notice and disclaimer of warranty;
keep intact all the notices that refer to this License and to the absence of any
warranty; and give any other recipients of the Program a copy of this License along
with the Program. You may charge a fee for the physical act of transferring a copy,
and you may at your option offer warranty protection in exchange for a fee.
2. You may modify your copy or copies of the Program or any portion of it, thus
forming a work based on the Program, and copy and distribute such modifications
or work under the terms of Chapter 1 above, provided that you also meet all of
these conditions:
a) You must cause the modified files to carry prominent notices stating that you
changed the files and the date of any change.
b) You must cause any work that you distribute or publish, that in whole or in part
contains or is derived from the Program or any part thereof, to be licensed as a
whole at no charge to all third parties under the terms of this License.
c) If the modified program normally reads commands interactively when run, you
must cause it, when started running for such interactive use in the most ordinary
way, to print or display an announcement including an appropriate copyright notice
and a notice that there is no warranty (or else, saying that you provide a warranty)
and that users may redistribute the program under these conditions, and telling the
user how to view a copy of this License. (Exception: if the Program itself is
interactive but does not normally print such an announcement, your work based on
the Program is not required to print an announcement.) These requirements apply
to the modified work as a whole.
If identifiable sections of that work are not derived from the Program, and can be
reasonably considered independent and separate works in themselves, then this
License, and its terms, do not apply to those sections when you distribute them as
separate works. But when you distribute the same sections as part of a whole
which is a work based on the Program, the distribution of the whole must be on the
terms of this License, whose permissions for other licensees extend to the entire
whole, and thus to each and every part regardless of who wrote it. Thus, it is not
the intent of this section to claim rights or contest your rights to work written entirely
by you; rather, the intent is to exercise the right to control the distribution of
derivative or collective works based on the Program.
In addition, mere aggregation of another work not based on the Program with the
Program (or with a work based on the Program) on a volume of a storage or
distribution medium does not bring the other work under the scope of this License.
3. You may copy and distribute the Program (or a work based on it, under Section
2) in object code or executable form under the terms of Chapters 1 and 2 above
provided that you also do one of the following:
a) Accompany it with the complete corresponding machine-readable source code,
which must be distributed under the terms of Chapters 1 and 2 above on a medium
customarily used for software interchange; or,
b) party, for a charge no more than your cost of physically performing source
distribution, a complete machine-readable copy of the corresponding source code,
to be distributed under the terms of Chapters 1 and 2 above on a medium
customarily used for software interchange; or,
c) Accompany it with the information you received as to the offer to distribute
corresponding source code. (This alternative is allowed only for non-commercial
distribution and only if you received the program in object code or executable form
with such an offer, in accord with SubChapter b above.)
The source code for a work means the preferred form of the work for making
modifications to it. For an executable work, complete source code means all the
source code for all modules it contains, plus any associated interface definition
files, plus the scripts used to control compilation and installation of the executable.
However, as a special exception, the source code distributed need not include
anything that is normally distributed (in either source or binary form) with the major
components (compiler, kernel, and so on) of the operating system on which the
executable runs, unless that component itself accompanies the executable. If
distribution of executable or object code is made by offering access to copy from a
designated place, then offering equivalent access to copy the source code from the
same place counts as distribution of the source code, even though third parties are
not compelled to copy the source along with the object code.
4. You may not copy, modify, sublicense, or distribute the Program except as
expressly provided under this License. Any attempt otherwise to copy, modify,
sublicense or distribute the Program is void, and will automatically terminate your
rights under this License. However, parties who have received copies, or rights,
from you under this License will not have their licenses terminated so long as such
parties remain in full compliance.
5. You are not required to accept this License, since you have not signed it.
However, nothing else grants you permission to modify or distribute the Program or
its derivative works. These actions are prohibited by law if you do not accept this
License. Therefore, by modifying or distributing the Program (or any work based on
the Program), you indicate your acceptance of this License to do so, and all its
terms and conditions for copying, distributing or modifying the Program or works
based on it.
6. Each time you redistribute the Program (or any work based on the Program), the
recipient automatically receives a license from the original licensor to copy,
distribute or modify the Program subject to these terms and conditions. You may
not impose any further restrictions on the recipients' exercise of the rights granted
herein. You are not responsible for enforcing compliance by third parties to this
License.
7. If, as a consequence of a court judgment or allegation of patent infringement or
for any other reason (not limited to patent issues), conditions are imposed on you
(whether by court order, agreement or otherwise) that contradict the conditions of
this License, they do not excuse you from the conditions of this License. If you
cannot distribute so as to satisfy simultaneously your obligations under this License
and any other pertinent obligations, then as a consequence you may not distribute
the Program at all. For example, if a patent license would not permit royalty free
redistribution of the Program by all those who receive copies directly or indirectly
through you, then the only way you could satisfy both it and this License would be
to refrain entirely from distribution of the Program. If any portion of this section is
held invalid or unenforceable under any particular circumstance, the balance of the
section is intended to apply and the section as a whole is intended to apply in other
circumstances. It is not the purpose of this section to induce you to infringe any
patents or other property right claims or to contest validity of any such claims; this
section has the sole purpose of protecting the integrity of the free software
distribution system, which is implemented by public license practices. Many people
have made generous contributions to the wide range of software distributed
through that system in reliance on consistent application of that system; it is up to
the author/donor to decide if he or she is willing to distribute software through any
other system and a licensee cannot impose that choice. This section is intended to
make thoroughly clear what is believed to be a consequence of the rest of this
License.
9. The Free Software Foundation may publish revised and/or new versions of the
General Public License from time to time. Such new versions will be similar in spirit
to the present version, but may differ in detail to address new problems or
concerns. Each version is given a distinguishing version number. If the Program
specifies a version number of this License which applies to it and "any later
version", you have the option of following the terms and conditions either of that
version or of any later version published by the Free Software Foundation. If the
Program does not specify a version number of this License, you may choose any
version ever published by the Free Software Foundation.
10. If you wish to incorporate parts of the Program into other free programs whose
distribution conditions are different, write to the author to ask for permission. For
software which is copyrighted by the Free Software Foundation, write to the Free
Software Foundation; we sometimes make exceptions for this. Our decision will be
guided by the two goals of preserving the free status of all derivatives of our free
software and of promoting the sharing and reuse of software generally.
NO WARRANTY
This program is distributed in the hope that it will be useful, but WITHOUT ANY
WARRANTY; without even the implied warranty of MERCHANTABILITY or
FITNESS FOR A PARTICULAR PURPOSE.
See the GNU General Public License for more details.
You should have received a copy of the GNU General Public License along with
this program; if not, write to the Free Software Foundation, Inc., 59 Temple Place,
Suite 330, Boston, MA 02111-1307 USA
Also add information on how to contact you by electronic and paper mail.
If the program is interactive, make it output a short notice like this when it starts in
an interactive mode: Gnomovision version 69, Copyright (C) year name of author
Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show
w'. This is free software, and you are welcome to redistribute it under certain
conditions; type `show c' for details. The hypothetical commands `show w' and
`show c' should show the appropriate parts of the General Public License.
Of course, the commands you use may be called something other than `show w'
and `show c'; they could even be mouse-clicks or menu items--whatever suits your
program. You should also get your employer (if you work as a programmer) or your
school, if any, to sign a "copyright disclaimer" for the program, if necessary. Here is
a sample; alter the names:
This General Public License does not permit incorporating your program into
proprietary programs. If your program is a subroutine library, you may consider it
more useful to permit linking proprietary applications with the library. If this is what
you want to do, use the GNU Library General Public License instead of this
License.
Preamble
The licenses for most software are designed to take away your freedom to share
and change it. By contrast, the GNU General Public Licenses are intended to
guarantee your freedom to share and change free software--to make sure the
software is free for all its users.
This license, the Lesser General Public License, applies to some specially
designated software packages--typically libraries--of the Free Software Foundation
and other authors who decide to use it. You can use it too, but we suggest you first
think carefully about whether this license or the ordinary General Public License is
the better strategy to use in any particular case, based on the explanations below.
When we speak of free software, we are referring to freedom of use, not price. Our
General Public Licenses are designed to make sure that you have the freedom to
distribute copies of free software (and charge for this service if you wish); that you
receive source code or can get it if you want it; that you can change the software
and use pieces of it in new free programs; and that you are informed that you can
do these things.
To protect your rights, we need to make restrictions that forbid distributors to deny
you these rights or to ask you to surrender these rights.
These restrictions translate to certain responsibilities for you if you distribute copies
of the library or if you modify it.
For example, if you distribute copies of the library, whether gratis or for a fee, you
must give the recipients all the rights that we gave you. You must make sure that
they, too, receive or can get the source code. If you link other code with the library,
you must provide complete object files to the recipients, so that they can relink
them with the library after making changes to the library and recompiling it. And
you must show them these terms so they know their rights.
We protect your rights with a two-step method: (1) we copyright the library, and (2)
we offer you this license, which gives you legal permission to copy, distribute
and/or modify the library.
To protect each distributor, we want to make it very clear that there is no warranty
for the free library. Also, if the library is modified by someone else and passed on,
the recipients should know that what they have is not the original version, so that
the original author's reputation will not be affected by problems that might be
introduced by others.
Finally, software patents pose a constant threat to the existence of any free
program. We wish to make sure that a company cannot effectively restrict the
users of a free program by obtaining a restrictive license from a patent holder.
Therefore, we insist that any patent license obtained for a version of the library
must be consistent with the full freedom of use specified in this license.
Most GNU software, including some libraries, is covered by the ordinary GNU
General Public License. This license, the GNU Lesser General Public License,
applies to certain designated libraries, and is quite different from the ordinary
General Public License. We use this license for certain libraries in order to permit
linking those libraries into non-free programs.
When a program is linked with a library, whether statically or using a shared library,
the combination of the two is legally speaking a combined work, a derivative of the
original library. The ordinary General Public License therefore permits such linking
only if the entire combination fits its criteria of freedom. The Lesser General Public
License permits more lax criteria for linking other code with the library.
We call this license the "Lesser" General Public License because it does less to
protect the user's freedom than the ordinary General Public License. It also
provides other free software developers Less of an advantage over competing non-
free programs. These disadvantages are the reason we use the ordinary General
Public License for many libraries. However, the Lesser license provides
advantages in certain special circumstances.
For example, on rare occasions, there may be a special need to encourage the
widest possible use of a certain library, so that it becomes a de-facto standard. To
achieve this, non-free programs must be allowed to use the library. A more
frequent case is that a free library does the same job as widely used non-free
libraries. In this case, there is little to gain by limiting the free library to free software
only, so we use the Lesser General Public License.
Although the Lesser General Public License is Less protective of the users'
freedom, it does ensure that the user of a program that is linked with the Library
has the freedom and the wherewithal to run that program using a modified version
of the Library.
The precise terms and conditions for copying, distribution and modification follow.
Pay close attention to the difference between a "work based on the library" and a
"work that uses the library". The former contains code derived from the library,
whereas the latter must be combined with the library in order to run.
0. This License Agreement applies to any software library or other program which
contains a notice placed by the copyright holder or other authorized party saying it
may be distributed under the terms of this Lesser General Public License (also
called "this License"). Each licensee is addressed as "you".
The "Library", below, refers to any such software library or work which has been
distributed under these terms. A "work based on the Library" means either the
Library or any derivative work under copyright law: that is to say, a work containing
the Library or a portion of it, either verbatim or with modifications and/or translated
straightforwardly into another language. (Hereinafter, translation is included without
limitation in the term "modification".)
"Source code" for a work means the preferred form of the work for making
modifications to it. For a library, complete source code means all the source code
for all modules it contains, plus any associated interface definition files, plus the
scripts used to control compilation and installation of the library.
Activities other than copying, distribution and modification are not covered by this
License; they are outside its scope. The act of running a program using the Library
is not restricted, and output from such a program is covered only if its contents
constitute a work based on the Library (independent of the use of the Library in a
tool for writing it). Whether that is true depends on what the Library does and what
the program that uses the Library does.
1. You may copy and distribute verbatim copies of the Library's complete source
code as you receive it, in any medium, provided that you conspicuously and
appropriately publish on each copy an appropriate copyright notice and disclaimer
of warranty; keep intact all the notices that refer to this License and to the absence
of any warranty; and distribute a copy of this License along with the Library.
You may charge a fee for the physical act of transferring a copy, and you may at
your option offer warranty protection in exchange for a fee.
2. You may modify your copy or copies of the Library or any portion of it, thus
forming a work based on the Library, and copy and distribute such modifications or
work under the terms of Chapter 1 above, provided that you also meet all of these
conditions:
(For example, a function in a library to compute square roots has a purpose that is
entirely well-defined independent of the application. Therefore, Section 2d requires
that any application-supplied function or table used by this function must be
optional: if the application does not supply it, the square root function must still
compute square roots.)
Thus, it is not the intent of this section to claim rights or contest your rights to work
written entirely by you; rather, the intent is to exercise the right to control the
distribution of derivative or collective works based on the Library.
In addition, mere aggregation of another work not based on the Library with the
Library (or with a work based on the Library) on a volume of a storage or
distribution medium does not bring the other work under the scope of this License.
3. You may opt to apply the terms of the ordinary GNU General Public License
instead of this License to a given copy of the Library. To do this, you must alter all
the notices that refer to this License, so that they refer to the ordinary GNU General
Public License, version 2, instead of to this License. (If a newer version than
version 2 of the ordinary GNU General Public License has appeared, then you can
specify that vers ion instead if you wish.) Do not make any other change in these
notices.
Once this change is made in a given copy, it is irreversible for that copy, so the
ordinary GNU General Public License applies to all subsequent copies and
derivative works made from that copy.
This option is useful when you wish to copy part of the code of the Library into a
program that is not a library.
4. You may copy and distribute the Library (or a portion or derivative of it, under
Chapter 2) in object code or executable form under the terms of Chapters 1 and 2
above provided that you accompany it with the complete corresponding machine-
readable source code, which must be distributed under the terms of Chapters 1
and 2 above on a medium customarily used for software interchange.
However, linking a "work that uses the Library" with the Library creates an
executable that is a derivative of the Library (because it contains portions of the
Library), rather than a "work that uses the library". The executable is therefore
covered by this License. Chapter 6 states terms for distribution of such
executables.
When a "work that uses the Library" uses material from a header file that is part of
the Library, the object code for the work may be a derivative work of the Library
even though the source code is not. Whether this is true is especially significant if
the work can be linked without the Library, or if the work is itself a library. The
threshold for this to be true is not precisely defined by law.
If such an object file uses only numerical parameters, data structure layouts and
accessors, and small macros and small inline functions (ten lines or less in length),
then the use of the object file is unrestricted, regardless of whether it is legally a
derivative work. (Executables containing this object code plus portions of the
Library will still fall under Chapter 6.)
Otherwise, if the work is a derivative of the Library, you may distribute the object
code for the work under the terms of Chapter 6. Any executables containing that
work also fall under Chapter 6, whether or not they are linked directly with the
Library itself.
6. As an exception to the Chapters above, you may also combine or link a "work
that uses the Library" with the Library to produce a work containing portions of the
Library, and distribute that work under terms of your choice, provided that the terms
permit modification of the work for the customer's own use and reverse engineering
for debugging such modifications.
You must give prominent notice with each copy of the work that the Library is used
in it and that the Library and its use are covered by this License. You must supply a
copy of this License.
If the work during execution displays copyright notices, you must include the
copyright notice for the Library among them, as well as a reference directing the
user to the copy of this License. Also, you must do one of these things:
For an executable, the required form of the "work that uses the Library" must
include any data and utility programs needed for reproducing the executable from
it. However, as a special exception, the materials to be distributed need not include
anything that is normally distributed (in either source or binary form) with the major
components (compiler, kernel, and so on) of the operating system on which the
executable runs, unless that component itself accompanies the executable.
It may happen that this requirement contradicts the license restrictions of other
proprietary libraries that do not normally accompany the operating system. Such a
contradiction means you cannot use both them and the Library together in an
executable that you distribute.
7. You may place library facilities that are a work based on the Library side-by-side
in a single library together with other library facilities not covered by this License,
and distribute such a combined library, provided that the separate distribution of
the work based on the Library and of the other library facilities is otherwise
permitted, and provided that you do these two things:
8. You may not copy, modify, sublicense, link with, or distribute the Library except
as expressly provided under this License. Any attempt otherwise to copy, modify,
sublicense, link with, or distribute the Library is void, and will automatically
terminate your rights under this License. However, parties who have received
copies, or rights, from you under this License will not have their licenses terminated
so long as such parties remain in full compliance.
9. You are not required to accept this License, since you have not signed it.
However, nothing else grants you permission to modify or distribute the Library or
its derivative works. These actions are prohibited by law if you do not accept this
License. Therefore, by modifying or distributing the Library (or any work based on
the Library), you indicate your acceptance of this License to do so, and all its terms
and conditions for copying, distributing or modifying the Library or works based on
it.
10. Each time you redistribute the Library (or any work based on the Library), the
recipient automatically receives a license from the original licensor to copy,
distribute, link with or modify the Library subject to these terms and conditions. You
may not impose any further restrictions on the recipients' exercise of the rights
granted herein. You are not responsible for enforcing compliance by third parties
with this License.
If any portion of this section is held invalid or unenforceable under any particular
circumstance, the balance of the section is intended to apply, and the section as a
whole is intended to apply in other circumstances.
It is not the purpose of this section to induce you to infringe any patents or other
property right claims or to contest validity of any such claims; this section has the
sole purpose of protecting the integrity of the free software distribution system
which is implemented by public license practices. Many people have made
generous contributions to the wide range of software distributed through that
system in reliance on consistent application of that system; it is up to the
author/donor to decide if he or she is willing to distribute software through any other
system and a licensee cannot impose that choice.
12. If the distribution and/or use of the Library is restricted in certain countries
either by patents or by copyrighted interfaces, the original copyright holder who
places the Library under this License may add an explicit geographical distribution
limitation excluding those countries, so that distribution is permitted only in or
among countries not thus excluded. In such case, this License incorporates the
limitation as if written in the body of this License.
13. The Free Software Foundation may publish revised and/or new versions of the
Lesser General Public License from time to time. Such new versions will be similar
in spirit to the present version, but may differ in detail to address new problems or
concerns.
14. If you wish to incorporate parts of the Library into other free programs whose
distribution conditions are incompatible with these, write to the author to ask for
permission. For software which is copyrighted by the Free Software Foundation,
write to the Free Software Foundation; we sometimes make exceptions for this.
Our decision will be guided by the two goals of preserving the free status of all
derivatives of our free software and of promoting the sharing and reuse of software
generally.
NO WARRANTY
If you develop a new library, and you want it to be of the greatest possible use to
the public, we recommend making it free software that everyone can redistribute
and change. You can do so by permitting redistribution under these terms (or,
alternatively, under the terms of the ordinary General Public License).
To apply these terms, attach the following notices to the library. It is safest to attach
them to the start of each source file to most effectively convey the exclusion of
warranty; and each file should have at least the "copyright" line and a pointer to
where the full notice is found.
<one line to give the library's name and a brief idea of what it does.>
Copyright (C) <year> <name of author>
This library is free software; you can redistribute it and/or modify it under the terms
of the GNU Lesser General Public License as published by the Free Software
Foundation; either version 2 of the License, or (at your option) any later version.
This library is distributed in the hope that it will be useful, but WITHOUT ANY
WARRANTY; without even the implied warranty of MERCHANTABILITY or
FITNESS FOR A PARTICULAR PURPOSE. See the GNU Lesser General Public
License for more details.
You should have received a copy of the GNU Lesser General Public License along
with this library; if not, write to the Free Software Foundation, Inc., 59 Temple
Place, Suite 330, Boston, MA 02111-1307 USA
Also add information on how to contact you by electronic and paper mail. You
should also get your employer (if you work as a programmer) or your school, if any,
to sign a "copyright disclaimer" for the library, if necessary. Here is a sample; alter
the names:
Yoyodyne, Inc., hereby disclaims all copyright interest in the library `Frob' (a library
for tweaking knobs) written by James Random Hacker.
<signature of Ty Coon>, 1 April 1990
Ty Coon, President of Vice
Redistribution and use in source and binary forms, with or without modification, are
permitted provided that the following conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of
conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list
of conditions and the following disclaimer in the documentation and/or other
materials provided with the distribution.
3. Neither the name of the Politecnico di Torino nor the names of its contributors
may be used to endorse or promote products derived from this software without
specific prior written permission.
Permission is granted to anyone to use this software for any purpose, including
commercial applications, and to alter it and redistribute it freely, subject to the
following restrictions:
1. The origin of this software must not be misrepresented; you must not claim that
you wrote the original software. If you use this software in a product, an
acknowledgment in the product documentation would be appreciated but is not
required.
2. Altered source versions must be plainly marked as such, and must not be
misrepresented as being the original software.
3. This notice may not be removed or altered from any source distribution.
I Index
I
A F
E n .....................................................IM5/3-26
Name
Ethernet card PCU ............................................IM5/2-18
Additional.................................... IM5/3-34 TCU ............................................IM5/2-17
Integrated ................................... IM5/3-34 NETNAMES.INI .............................IM5/3-28
O SINUMERIK Desktop.....................IM5/4-53
Switchover disable .........................IM5/2-21
Operation
While booting ............................. IM5/4-50
T
Operator actions
During operation......................... IM5/4-54
Operator focus........................ IM5/1-4, 4-54 t ......................................................IM5/3-26
TCU.................................................. IM5/1-4
Deletion from the TCU network ..IM5/2-20
P MAC address ..............................IM5/1-10
Name ..........................................IM5/2-17
PCU TCU network .................................... IM5/1-4
Deletion from the TCU network.. IM5/2-20
IP address .................................. IM5/2-12
U
Name.......................................... IM5/2-18
Selection..................................... IM5/4-54
USB.................................................. IM5/1-5
PG
Connection ................................. IM5/2-19
IP address .................................. IM5/2-19 V